-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #327 from bitfinexcom/staging
Release version to master
- Loading branch information
Showing
4 changed files
with
71 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
name: CI | ||
run-name: 'Run tests: Commit ${{ github.sha }}' | ||
|
||
on: | ||
pull_request: | ||
types: [opened, reopened, edited] | ||
branches: | ||
- master | ||
workflow_dispatch: | ||
|
||
jobs: | ||
linux-test-runner: | ||
name: Linux Test Runner | ||
timeout-minutes: 30 | ||
runs-on: ubuntu-22.04 | ||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v4 | ||
with: | ||
submodules: recursive | ||
- uses: actions/setup-node@v3 | ||
with: | ||
node-version: 18.17.1 | ||
- name: Setup configs | ||
run: | | ||
cp config/common.json.example config/common.json \ | ||
&& cp config/schedule.json.example config/schedule.json \ | ||
&& cp config/service.report.json.example config/service.report.json \ | ||
&& cp config/facs/grc.config.json.example config/facs/grc.config.json \ | ||
&& cp config/facs/grc-slack.config.json.example config/facs/grc-slack.config.json | ||
- name: Install deps | ||
run: npm i | ||
- name: Run tests | ||
run: npm test -- --reporter=json --reporter-option output=test-report.json | ||
- uses: actions/upload-artifact@v3 | ||
if: success() || failure() | ||
with: | ||
name: test-results | ||
path: test-report.json |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
name: 'Test Report' | ||
run-name: 'Test Report: Commit ${{ github.sha }}' | ||
|
||
on: | ||
workflow_run: | ||
workflows: ['CI'] | ||
types: | ||
- completed | ||
|
||
permissions: | ||
contents: read | ||
actions: read | ||
checks: write | ||
|
||
jobs: | ||
web-page-report: | ||
name: Web Page Report | ||
runs-on: ubuntu-22.04 | ||
steps: | ||
- uses: dorny/test-reporter@v1 | ||
id: test-results | ||
with: | ||
artifact: test-results | ||
name: Mocha Tests | ||
path: test-report.json | ||
reporter: mocha-json | ||
- name: Test Report Summary | ||
run: | | ||
echo "### Test Report page is ready! :rocket:" >> $GITHUB_STEP_SUMMARY | ||
echo "And available at the following [Link](${{ steps.test-results.outputs.url_html }})" >> $GITHUB_STEP_SUMMARY |
Submodule bfx-report-ui
updated
44 files
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3f48d50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dear Repository Members,
I apologize for reaching out in this manner and am aware that this might not be the typical way of communication here. However, I am hopeful that @prdn and the rest of the team might notice and acknowledge my message. This is my last chance in seeking assistance.
My colleagues and I have faced a significant issue due to a human error in an Excel file, which led to the wrongful transfer of 130,500.148588 USDT to two incorrect Ethereum addresses. The transactions are linked to these Blockchain Transaction IDs (TXIDs, HASH): 0x8ae3a8bb2420489ae03bce6cc9e5fbfe276436e56859614b3a45f90232141de2 and 0x188988b979d61d2b55f04898c8ab226d8f08fb3bdd83bacc120ddb7dc6e438bf. The funds were mistakenly sent to addresses 0x79EF540F697cF180408Cf9Cd960b0502b344B206 and 0x79EF540F697CF180408cf9cd960B0502b344b207 instead of the intended address 0x79EF540F697CF180408cf9cd960B0502b344b205
We have submitted multiple support tickets (№958241, №264112, and 594233) over the last two months but have not yet received a substantial response or resolution. The situation has been ongoing since May, and the amount in question is substantial for us.
We fully understand that the responsibility for blockchain transactions typically lies with the sender. However, considering that the funds have remained unclaimed for over six months, we are reaching out in hopes of finding a solution. We own the sender's address, have access to it, and can provide the public key to verify our ownership. We are ready to provide any proofs needed, including the private key, to facilitate the resolution of this issue.
I have read about an instance where the technical director of Tether assisted a trader from China in recovering lost USDT, and this gives us hope that our situation might also find a resolution.
We sincerely appreciate any time and consideration you can offer, and are open to any suggestions or steps you might recommend.