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

Sancho-v1.0.11 #1622

Merged
merged 103 commits into from
Jul 30, 2024
Merged

Sancho-v1.0.11 #1622

merged 103 commits into from
Jul 30, 2024

Conversation

MSzalowski
Copy link
Contributor

No description provided.

j-dyczka and others added 30 commits July 5, 2024 13:58
Fix: gov-action-loader: remove old cardano-cli dependency
In order to facilitate the execution of the resync action in various
environments (development, testing, and staging), the NGINX
authentication configuration has been updated. Previously,
authentication was controlled using a single `NGINX_BASIC_AUTH` secret.
This has now been expanded to include separate authentication secrets
for development (`DEV_NGINX_BASIC_AUTH`), testing
(`TEST_NGINX_BASIC_AUTH`), and staging (`STAGING_NGINX_BASIC_AUTH`),
allowing more granular control and enhanced security in different stages
of deployment.
…uthentication-misconfiguration-in-resync-workflow-for-cardano-node-and-dbsync

[#1567] Resolving NGINX authentication misconfiguration in resync workflow for Cardano Node and DBSync
Fix gov-action-loader dependency, adjust NGINX config for authentication, and add missing PDF test IDs
chore: bump @intersect.mbo/pdf-ui to v0.2.9
…ional

backend: allow using metadata directly from db-sync
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
…on-redirect

[#1413] remove balance check on redirect to GA propose
…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.
@MSzalowski
Copy link
Contributor Author

Thank you @Ryun1 for approval, but this PR needs to be fixed before proceeding with the deployment to staging

@MSzalowski MSzalowski changed the title Sancho-v1.0.10 Sancho-v1.0.11 Jul 30, 2024
@MSzalowski
Copy link
Contributor Author

That check https://github.com/IntersectMBO/govtool/actions/runs/10162188932/job/28102333675?pr=1622 seems to be invalid due to having a bug - reported here

@MSzalowski
Copy link
Contributor Author

https://github.com/IntersectMBO/govtool/actions/runs/10162188926/job/28102333694?pr=1622 - that is most likely failing due to not synced db-sync. Could you please verify that @mesudip?

If those checks are failing not because of the introduced changes, I'll merge that PR to staging without having that checks green

…auth-envs-to-resync-workflow

chore: add missing envs to resync workflow
chore: add missing envs to resync workflow
@MSzalowski MSzalowski merged commit 3990431 into staging Jul 30, 2024
3 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.