Skip to content

Update GitHub issue template #7

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 3, 2020

Conversation

glbrntt
Copy link
Contributor

@glbrntt glbrntt commented Feb 3, 2020

Motivation:

The GitHub issue template asks for the SwiftLog version/commit hash.
This isn't the SwiftLog project.

Modifications:

Replace SwiftLog with SwiftCrypto in the issue template.

Result:

The GitHub issue template is more relevant to the project.

Motivation:

The GitHub issue template asks for the SwiftLog version/commit hash.
This isn't the SwiftLog project.

Modifications:

Replace SwiftLog with SwiftCrypto in the issue template.

Result:

The GitHub issue template is more relevant to the project.
@swift-server-bot
Copy link

Can one of the admins verify this patch?

@glbrntt glbrntt requested a review from Lukasa February 3, 2020 19:26
Copy link
Contributor

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

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

Thanks for the catch!

@Lukasa
Copy link
Contributor

Lukasa commented Feb 3, 2020

@swift-server-bot add to whitelist

@Lukasa Lukasa merged commit fced1f8 into apple:master Feb 3, 2020
rnro pushed a commit to rnro/swift-crypto that referenced this pull request Mar 26, 2025
…apple#7)

### Motivation

Reduce deployment target by 3 versions to gain more adoption.

### Modifications

- Added new deployment targets
- Refactor `invokeSession` method to support iOS 13+
- Update `swift-openapi-runtime` version once changes are done
[there](apple/swift-openapi-runtime#18).

### Result

Deployment target will be reduced by 3 versions.
rnro pushed a commit to rnro/swift-crypto that referenced this pull request Mar 26, 2025
…apple#46)

### Motivation

When running the cancellation tests in a loop, very occasionally there
would be a crash with the following backtrace:

```
#0	0x000000018aa008d4 in objc_opt_respondsToSelector ()
apple#1	0x000000018aea3410 in _outputStreamCallbackFunc ()
apple#2	0x000000018aea3310 in _signalEventSync ()
apple#3	0x000000018aeecdb0 in ___signalEventQueue_block_invoke ()
apple#4	0x000000018abe6cb8 in _dispatch_call_block_and_release ()
apple#5	0x000000018abe8910 in _dispatch_client_callout ()
apple#6	0x000000018abefea4 in _dispatch_lane_serial_drain ()
apple#7	0x000000018abf0a08 in _dispatch_lane_invoke ()
apple#8	0x000000018abfb61c in _dispatch_root_queue_drain_deferred_wlh ()
apple#9	0x000000018abfae90 in _dispatch_workloop_worker_thread ()
apple#10	0x000000018ad96114 in _pthread_wqthread ()
```

This seems to indicate that the output stream is trying to access its
delegate. However, when running with debug logging enabled I can see
that the delegate has already been deinitialized.

This is likely a result of the delegate itself owning the stream and
setting the stream delegate to `self`, which IIUC is an established
pattern. This presents a race in teardown.

### Modifications

This patch sets the output stream delegate to `nil` in the delegate
`deinit`.

### Result

No attempts to call the delegate will happen after it is has been
deinitailzed.

### Test Plan

With this patch, the failing test passes when run an order of magnitude
more times than were required to reliably reproduce the crash without
the patch.
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.

3 participants