Skip to content
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

*: release v1.1.1 #3287

Merged
merged 6 commits into from
Sep 17, 2024
Merged

*: release v1.1.1 #3287

merged 6 commits into from
Sep 17, 2024

Conversation

gsora and others added 5 commits September 16, 2024 15:06
If the "gnosis_block_hotfix" feature flag is enabled, use the Gnosis-compatible representation of the proposal when calculating its hash tree root.  This should fix Gnosis proposals failing due to bad signature.

category: feature
ticket: #3181
feature_flag: gnosis_block_hotfix
* Added `chiado` network spec in addition to the existing `gnosis`.
* Feature `gnosis_block_hotfix` is enabled automatically when gnosis | chiado network is detected.
* When the user explicitly disables `gnosis_block_hotfix` feature, the app just yields warning during startup:

```
Feature gnosis_block_hotfix is required by gnosis/chiado, but explicitly disabled
```

category: feature
ticket: none
feature_flag: gnosis_block_hotfix
- fix test peers on timeout, sometimes it went in the case where the current context is done, but the result of the currently running test wasn't sent to the channel
- fix wrongly named variables

category: test
ticket: none
Fixing flaky test in previous PR #3267 revealed another issue. Fixing that one, which is purely unit test related.

category: test
ticket: none
After #3267 was merged, on `ctx.Done()` we push the latest unfinished test. This causes out of range in the outer function in some ocassions.

category: bug
ticket: none
@github-actions github-actions bot added the branch-release PR or Issue linked to a release branch (not main) label Sep 16, 2024
Copy link

codecov bot commented Sep 16, 2024

Codecov Report

Attention: Patch coverage is 81.08108% with 7 lines in your changes missing coverage. Please review.

Project coverage is 57.67%. Comparing base (a193f84) to head (ad77df8).
Report is 1 commits behind head on main-v1.1.

Files with missing lines Patch % Lines
app/app.go 0.00% 6 Missing ⚠️
cmd/createcluster.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@              Coverage Diff              @@
##           main-v1.1    #3287      +/-   ##
=============================================
- Coverage      57.73%   57.67%   -0.07%     
=============================================
  Files            211      211              
  Lines          30369    30398      +29     
=============================================
- Hits           17535    17532       -3     
- Misses         10950    10980      +30     
- Partials        1884     1886       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Compose tests were failing because of `docker-compose` command hasn't been changed to `docker compose` on some places and the version on top wasn't removed.

category: test
ticket: none
Copy link

sonarcloud bot commented Sep 17, 2024

@pinebit
Copy link
Contributor Author

pinebit commented Sep 17, 2024

Added #3249 to avoid compose tests failure.

@pinebit pinebit added the merge when ready Indicates bulldozer bot may merge when all checks pass label Sep 17, 2024
@obol-bulldozer obol-bulldozer bot merged commit dc848df into main-v1.1 Sep 17, 2024
13 of 14 checks passed
@obol-bulldozer obol-bulldozer bot deleted the pinebit/release-v1.1.1 branch September 17, 2024 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-release PR or Issue linked to a release branch (not main) merge when ready Indicates bulldozer bot may merge when all checks pass
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants