-
Notifications
You must be signed in to change notification settings - Fork 24
Changed config to support V8 envs #152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
8.0.0+001 release - Gnosis gas price fix
Fix blockchain default prices
…tibility V8 - allowance backwards compatibility
…se-allowance-and-demo-fix
…mo-fix Decrease allowance and demo fix
Updated publish finality
| BLOCKCHAIN_IDS.NEUROWEB_MAINNET, | ||
| BLOCKCHAIN_IDS.HARDHAT_1, | ||
| BLOCKCHAIN_IDS.HARDHAT_2, | ||
| ]; |
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.
Bug: Orphaned array expression creates dead code
An array literal is created with blockchain IDs but never assigned to a variable or exported. This appears to be incomplete code that was meant to be NEUROWEB_INCENTIVE_TYPE_CHAINS, matching the equivalent export in constants/constants.js. The array expression evaluates but has no effect, suggesting this was accidentally committed or incompletely implemented.
|
|
||
| - name: Merge v8/develop into Test_Publish_Query | ||
| run: | | ||
| git merge origin/v8/develop --no-edit || echo "Merge failed but continuing" |
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.
Bug: Workflow silently masks merge failures before pushing
The merge command uses || echo "Merge failed but continuing" which causes the step to succeed even when the merge fails. The subsequent push step then executes, but since HEAD hasn't changed (due to the failed merge), nothing meaningful is pushed. The workflow reports success despite failing to actually merge the branches, which could mislead teams into thinking branches are synchronized when they aren't.
…ange-and-only-buffer-multiply percentile 80, bufferPercent multiply
| @@ -0,0 +1 @@ | |||
| PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 | |||
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.
| @@ -0,0 +1,3 @@ | |||
| import { BLOCKCHAIN_IDS } from './constants.js'; | |||
|
|
|||
| export { BLOCKCHAIN_IDS }; | |||
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.
Bug: Public constants export is incomplete
package.json exposes ./constants, but constants/index.js/constants/index.cjs only export BLOCKCHAIN_IDS even though constants/constants.js defines many other configuration constants. This makes dkg.js/constants unusable for expected config values and can break consumers relying on exported constants beyond BLOCKCHAIN_IDS.
Additional Locations (1)
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
| if: github.event.pull_request.merged == true || github.event_name == 'push' | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: Checkout target branch (Test_Publish_Query) | ||
| uses: actions/checkout@v3 | ||
| with: | ||
| ref: Test_Publish_Query | ||
| token: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| - name: Set up Git identity | ||
| run: | | ||
| git config user.name "github-actions[bot]" | ||
| git config user.email "41898282+github-actions[bot]@users.noreply.github.com" | ||
|
|
||
| - name: Fetch latest v8/develop | ||
| run: git fetch origin v8/develop | ||
|
|
||
| - name: Merge v8/develop into Test_Publish_Query | ||
| run: | | ||
| git merge origin/v8/develop --no-edit || echo "Merge failed but continuing" | ||
|
|
||
| - name: Push updated branch | ||
| run: git push origin HEAD:Test_Publish_Query No newline at end of file |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 2 months ago
To fix the issue, an explicit permissions block should be added to either the root of the workflow or to the individual job in the workflow YAML file. Since this workflow pushes commits to a branch (git push) and performs merges, it requires contents: write permission for repository contents (code, branches). The safest and most maintainable fix is to add a permissions block at the root of the YAML file (below name: and before on:), giving contents: write. This immediately clarifies what the workflow can do, prevents privilege escalation should defaults change, and adheres to GitHub's security guidelines.
Implementation Steps:
- Edit
.github/workflows/auto-merge-main-to-Test_Publish_Query.yml. - Insert the following after the
name:line (line 1), before theon:block:permissions: contents: write
-
Copy modified lines R2-R3
| @@ -1,4 +1,6 @@ | ||
| name: Auto Merge v8/develop into Test_Publish_Query | ||
| permissions: | ||
| contents: write | ||
|
|
||
| on: | ||
| push: |
…e keeping create wrapper
Add EIP-1559 gas mode, nonce reservation, and exposed asset creation phases Bump to 8.2.3
add package lock github actions check
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.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| }; | ||
|
|
||
| export const DEFAULT_PROXIMITY_SCORE_FUNCTIONS_PAIR_IDS = { | ||
| development: { 'hardhat1:31337': 2, 'hardhat2:31337': 2, 'otp:2043': 2 }, |
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.
Inconsistent blockchain config between related constants
Medium Severity
DEFAULT_PROXIMITY_SCORE_FUNCTIONS_PAIR_IDS.development includes 'otp:2043': 2, but BLOCKCHAINS.development no longer contains 'otp:2043' (it was removed in this commit). This creates an inconsistency where code looking up proximity score functions for development may expect otp:2043 to be a valid development blockchain, but it won't be found in BLOCKCHAINS.development.
Additional Locations (1)
update package-lock test
…led-without-sufficient-TRAC
…ufficient-TRAC Fix for approve called without sufficient trac
Note
Medium Risk
Touches core configuration/constants (network IDs, contracts, gas defaults) that can affect runtime behavior across environments, and introduces CI automation that may unexpectedly merge or fail builds if misconfigured.
Overview
Updates repository tooling and docs: adds
.env.example, expands.gitignore, tweaksREADME.mdformatting and points the demo link tov8/develop.Refactors configuration/constants for v8 by removing the root
constants.js(CommonJS) and introducingconstants/constants.js(ESM) plusconstants/index.js/constants/index.cjsexports; constants are updated/expanded (new chain IDs, updated RPC/contract addresses, new paranet/gas/fee-related settings, and largerMAX_FILE_SIZE).Adds GitHub Actions workflows to automatically merge
v8/developintoTest_Publish_Queryand to fail CI whenpackage-lock.jsonis missing/out-of-sync vianpm ci --dry-run.Written by Cursor Bugbot for commit b4af128. This will update automatically on new commits. Configure here.