-
Notifications
You must be signed in to change notification settings - Fork 9
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
sancho-v1.0.10 #1589
Merged
Merged
sancho-v1.0.10 #1589
Conversation
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
chore: bump @intersect.mbo/pdf-ui to v0.2.9
…ional backend: allow using metadata directly from db-sync
list-proposals: fix SQL
…form [#1583] fix: fix frontend build
Bumped the versions of Cardano Node and Cardano DB Sync in the development environment to ensure compatibility with the latest features and fixes. Updated the `docker-compose.node+dbsync.yml` file to use `cardano-node:9.0.0-sancho` and `cardano-db-sync:sancho-5.1.0`. This change addresses the need to stay current with upstream improvements and ensures that our development environment remains in line with the latest network protocols.
Upgraded the Cardano Node to version 9.0.0-sancho and Cardano DB Sync to sancho-5.1.0 in the `scripts/govtool/Makefile`. This adjustment ensures compatibility with the latest network protocols and incorporates recent fixes and features. This change is essential for maintaining synchronicity with the updated Cardano protocol and supports upcoming governance functionalities. This commit paves the way for further testing in staging environments, aiming to confirm stability and prevent any major issues or downtime in the beta environment.
Added new inputs and environment variables to the resync workflow to reflect the configuration used in the deployment workflow. This includes enabling the proposal discussion forum, forcing rebuild of Docker images, and additional environment variables for Grafana, Google Analytics, and Sentry integrations. This ensures consistency between workflows and supports a smooth update process for Cardano Node and DB Sync versions in various environments.
…ync-to-version-sancho-5-1-0 [#1538] Chore: Bump DB-Sync to version `sancho-5-1-0`
[#1583] fix: add missing dependency @babel/preset-react
[#1472] Bump CSL version to 12.0.0-beta.2
chore: bump version v1.0.9
MSzalowski
requested review from
placek,
adgud,
jankun4,
Sworzen1,
JanJaroszczak and
Ryun1
as code owners
July 16, 2024 14:32
placek
approved these changes
Jul 16, 2024
…ptions In reference to the user story regarding Sentry reporting killed threads by the timeout manager on the Haskell backend, improved the exception handling logic. The modifications particularly focus on recognizing and skipping the `TimeoutThread` and `ConnectionClosedByPeer` exceptions to prevent unnecessary error reports in Sentry. This should align the actual behavior more closely with the expected outcome by filtering out specific known exceptions that do not require investigation. Updated dependencies in the `vva-be.cabal` to include the `time-manager` package for handling the new exception types.
Updated the custom entrypoint script for the Cardano DB Sync container to include advanced configuration capabilities. Changes were made to `scripts/govtool/custom-cardano-db-sync.entrypoint.sh` to set up necessary environment variables, handle PostgreSQL authentication via a `pgpass` file, and include the path to `db-sync-config.json`. The `scripts/govtool/Makefile` and `scripts/govtool/config/templates/docker-compose.yml.tpl` files were adjusted to support these changes by implementing new build and deployment targets for the custom Cardano DB Sync image and updating the Docker Compose template. These changes ensure the DBSync process uses the correct settings, allowing it to adapt to future updates and ensuring better synchronization with the Cardano blockchain.
…-genesis-to-dbsync-configuration [#1464] Enable future genesis in DBSync config
…s-connection-options chore: provide more postgres connection options
* fix(#1417): handle thread killed by timeout manager exception
…hrows-500-after-resync-on-db-sync-510-and-node-900 fix(#1612): Fix connection to the metadata-validation service
…-error fix: fix indentation syntax error in Metadata.hs
…edirect [#1117] redirect to private drep directory url
…fter-connect [#1442] Add redirect to dashboard cards after connect
…lowing-the-cip-100-standard fix(#1582): Add support for CIP-100 on vote metadata
Co-authored-by: Ryan <44342099+Ryun1@users.noreply.github.com> Signed-off-by: Michał Szałowski <michal.szalowski@gmail.com>
…inputs-selection fix(wallet): fix inputs selection with the change config
PR bumping version to 1.0.10: #1620 |
chore: bump GovTool version to v1.0.10
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.