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.

Sign up for GitHub

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

Jump to bottom

New sprint release 2023.01.23 #2735

Closed
harshad16 opened this issue Jan 24, 2023 · 1 comment
Closed

New sprint release 2023.01.23 #2735

harshad16 opened this issue Jan 24, 2023 · 1 comment
Labels
area/release-eng Issues or PRs related to Release Engineering kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshad16
Copy link
Member

Hello, Thoth-station!

This Issue would be used for the current sprint cycle production release.
By the end of the sprint cycle, we will consolidate the information of thoth-station components features upgrade and fixes in this issue.

/kind documentation
/area release-eng
/triage accepted
/priority important-soon
@harshad16 harshad16 added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Jan 24, 2023
@sesheta sesheta added kind/documentation Categorizes issue or PR as related to documentation. area/release-eng Issues or PRs related to Release Engineering triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jan 24, 2023
@harshad16
Copy link
Member Author

we have completed the release for v2023.01.23 🎉 🎊 🥳
With the start of 2023, the team focused on fixing bugs in this sprint.

Fixes

Fix congestion in data ingestion due to kafka consumer
one kafka consumer in the investigator was being used to handle all kafka topics. However as our data ingestion is growing date-to-date, it was causing congestion for the consumer. With the split of topic-based on data ingestion and data services between different consumers per namespace, the issue is now handled.

Solvers failure due to unique constraint violation
Some of the solver workflow runs were failing due to unique constraint violations. The issue was being caused by unique constraints and an update of the table with new data. with the fix of the update function and fixing the SQL table configuration, this is resolved.

Component Updates

Thanks for the amazing work everyone. 💯

@harshad16 harshad16 mentioned this issue Jan 24, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release-eng Issues or PRs related to Release Engineering kind/documentation Categorizes issue or PR as related to documentation. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@harshad16 @sesheta