Skip to content

Problem: reading out test results #19

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

Merged
merged 1 commit into from
Feb 28, 2025
Merged

Problem: reading out test results #19

merged 1 commit into from
Feb 28, 2025

Conversation

yrashk
Copy link
Contributor

@yrashk yrashk commented Feb 28, 2025

We have to do this manually, parsing notice messages.

Solution: switch to Cloudevents event system

This depends on omni_test 0.2.0

We have to do this manually, parsing notice messages.

Solution: switch to Cloudevents event system

This depends on [omni_test 0.2.0](omnigres/omnigres#814)
var rows *sql.Rows
rows, err = conn.QueryContext(ctx, `select omni_cloudevents.create_notice_publisher(publish_uncommitted => true)`)
if err == nil {
for rows.Next() {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do have this empty loop?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Without it, an error will occur lib/pq#635

@yrashk yrashk merged commit c2d0642 into master Feb 28, 2025
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