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

Refine logging of migrations and tx ingestion #237

Merged
merged 1 commit into from
Jul 4, 2024

Conversation

2opremio
Copy link
Contributor

@2opremio 2opremio commented Jul 4, 2024

What

Downgrade Tx ingestion logging to Debug (otherwise we flood the logs during the migration)

Make sure we log whenever a migration is applied

Why

Make logs more intuitive and not excessively verbose

Known limitations

N/A

Downgrade Tx ingestion logging to Debug (otherwise we flood the logs during the migration)

Make sure we log whenever a migration is applied
@2opremio
Copy link
Contributor Author

2opremio commented Jul 4, 2024

Integration tests work locally but fail immediately in CI without any logs. My bet is that they are getting killed due to running in parallel.

I will address that in a separate PR.

@2opremio 2opremio merged commit 556d535 into stellar:main Jul 4, 2024
15 of 19 checks passed
@2opremio 2opremio deleted the log-migration-application branch July 4, 2024 01:29
2opremio added a commit to 2opremio/soroban-rpc that referenced this pull request Jul 8, 2024
2opremio added a commit to 2opremio/soroban-rpc that referenced this pull request Jul 8, 2024
I didn't adapt the logic right.

This was hard to debug because, in integration tests, it caused the
daemon to run `d.logger.WithError(err).Fatal("could not build
migrations")`, which in turn runs `os.Exit` which ends the test right
away (without flushing logs etc).

I need to think how to improve this. One option is to
override the `ExitFunc` in logrus with an assertion.
@2opremio 2opremio mentioned this pull request Jul 8, 2024
aditya1702 pushed a commit that referenced this pull request Jul 8, 2024
* Fix typo from #237

I didn't adapt the logic right.

This was hard to debug because, in integration tests, it caused the
daemon to run `d.logger.WithError(err).Fatal("could not build
migrations")`, which in turn runs `os.Exit` which ends the test right
away (without flushing logs etc).

I need to think how to improve this. One option is to
override the `ExitFunc` in logrus with an assertion.

* Add verbosity again to see what's wrong

* Fix the error further

* Revert "Add verbosity again to see what's wrong"

This reverts commit 0be1cd6.
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.

2 participants