Skip to content

Debugging in CI, ignore. #505

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

Closed
wants to merge 15 commits into from
Closed

Conversation

zenhack
Copy link
Contributor

@zenhack zenhack commented Apr 16, 2023

I can't reproduce the CI errors in #502 locally, so I'm going to use this PR to debug them in CI. feel free to unsubscribe and ignore; it won't be merged.

zenhack added 3 commits April 11, 2023 22:44
...because fewer special cases are better. This also resolves everything
but the documentation for capnproto#423.

One of the tests had to be reworked a bit because the exact sequence of
messages was a bit different, but still correct.
Per Louis's questions.
@zenhack zenhack marked this pull request as draft April 16, 2023 22:13
zenhack added 12 commits April 16, 2023 18:15
Temporary, for debugging, to see which one we're getting
Harder to parse the output otherwise, though I think these are not real,
in the sense that this field is not accessed concurrently, though the
rest of the object may be.
The error we're getting suggests a nil client; this patch should see if
the client is actually null.
I think this is harmless, because Release() is idempotent, but the call
to rel() already covers this.
@zenhack zenhack closed this May 24, 2023
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.

1 participant