owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
swiftlang | swift | 4,480,211,870 | 88,017 | NotTheNHK | @FranzBusch Do you perhaps have an idea why Windows CI failed? | 2026-05-18T17:33:46 | 2026-05-18T17:33:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,481,329,992 | 86,083 | mikeash | Weird crashes in `swift_task_isCurrentExecutorWithFlagsImpl` usually indicate that something threw an exception through the concurrency runtime, then resumed execution. AppKit will resume execution if an otherwise uncaught exception is thrown on the main thread, so Mac apps that throw exceptions (hitting assertion fail... | 2026-05-18T19:37:18 | 2026-05-18T19:37:18 | {
"rocket": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,482,185,435 | 89,225 | DougGregor | @swift-ci please smoke test | 2026-05-18T21:03:13 | 2026-05-18T21:03:13 | {} | MEMBER |
swiftlang | swift | 4,479,314,597 | 89,208 | gottesmm | @swift-ci test windows platform | 2026-05-18T15:41:10 | 2026-05-18T15:41:10 | {} | CONTRIBUTOR |
swiftlang | swift | 4,481,949,866 | 89,112 | cachemeifyoucan | @swift-ci please test | 2026-05-18T20:39:32 | 2026-05-18T20:39:32 | {} | CONTRIBUTOR |
swiftlang | swift | 4,482,768,689 | 88,634 | atrick | @swift-ci benchmark | 2026-05-18T22:25:54 | 2026-05-18T22:25:54 | {} | CONTRIBUTOR |
swiftlang | swift | 4,484,230,031 | 88,775 | compnerd | @swift-ci please test Windows platform | 2026-05-19T03:50:30 | 2026-05-19T03:50:30 | {} | MEMBER |
swiftlang | swift | 4,485,793,088 | 89,214 | macguru | I can confirm this is fixed in the current `main-snapshot`.
However, stepping through the recent Swift versions with `swiftly`, I was able to re-confirm the issue does _not_ exist in 6.3 or 6.3.1 and has only being introduced in 6.3.2. | 2026-05-19T08:20:51 | 2026-05-19T08:20:51 | {} | NONE |
swiftlang | swift | 4,479,732,451 | 89,218 | carlpeto | @swift-ci please smoke test | 2026-05-18T16:32:52 | 2026-05-18T16:32:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,479,959,290 | 88,568 | xedin | I don't think that change is right, we are back again checking in diagnostics even though we shouldn't be producing a fix if it cannot be diagnosed. | 2026-05-18T17:02:19 | 2026-05-18T17:02:19 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,480,945,265 | 89,213 | natecook1000 | @swift-ci Please smoke test | 2026-05-18T18:58:51 | 2026-05-18T18:58:51 | {} | MEMBER |
swiftlang | swift | 4,482,220,759 | 89,218 | carlpeto | @swift-ci please smoke test | 2026-05-18T21:07:23 | 2026-05-18T21:07:23 | {} | CONTRIBUTOR |
swiftlang | swift | 4,484,406,716 | 89,225 | DougGregor | @swift-ci please smoke test | 2026-05-19T04:32:54 | 2026-05-19T04:32:54 | {} | MEMBER |
swiftlang | swift | 4,487,334,245 | 89,248 | elsakeirouz | @swift-ci please smoke test | 2026-05-19T11:36:37 | 2026-05-19T11:36:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,479,740,893 | 86,083 | xedin | I forgot to mention https://github.com/swiftlang/swift/pull/88157 - 6.3 doesn't have the with*Continuation APIs marked as `nonisolated(nonsending)` so backport is unnecessary in this case. | 2026-05-18T16:34:00 | 2026-05-18T16:34:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,480,053,499 | 89,224 | Snowy1803 | @swift-ci smoke test | 2026-05-18T17:13:40 | 2026-05-18T17:13:40 | {} | MEMBER |
swiftlang | swift | 4,480,325,553 | 89,214 | xedin | This issue has already been fixed on main, please use the latest main toolchain to verify, we are looking into backporting into into 6.3. | 2026-05-18T17:48:14 | 2026-05-18T17:48:14 | {
"hooray": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,482,114,543 | 89,016 | compnerd | @swift-ci please smoke test | 2026-05-18T20:55:45 | 2026-05-18T20:55:45 | {} | MEMBER |
swiftlang | swift | 4,482,688,895 | 89,229 | MaxDesiatov | @swift-ci smoke test | 2026-05-18T22:10:59 | 2026-05-18T22:10:59 | {} | CONTRIBUTOR |
swiftlang | swift | 4,482,715,256 | 89,230 | slavapestov | @swift-ci Please smoke test | 2026-05-18T22:16:02 | 2026-05-18T22:16:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,483,144,615 | 89,185 | shahmishal | @swift-ci test | 2026-05-18T23:34:55 | 2026-05-18T23:34:55 | {} | MEMBER |
swiftlang | swift | 4,486,555,788 | 89,214 | macguru | In fact, the issue was introduced only in the most recent Swift 6.3.2 build bundled with Xcode 26.5.
- 26.5 beta 2: `swift-driver version: 1.148.6 Apple Swift version 6.3.2 (swiftlang-6.3.2.1.103 clang-2100.1.1.101)` **no crash**
- 26.5 beta 3: `swift-driver version: 1.148.6 Apple Swift version 6.3.2 (swiftlang-6.3.2.... | 2026-05-19T09:51:56 | 2026-05-19T09:51:56 | {} | NONE |
swiftlang | swift | 4,479,470,794 | 89,075 | al45tair | @swift-ci Please test | 2026-05-18T16:00:43 | 2026-05-18T16:00:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,481,931,174 | 89,180 | mikeash | @swift-ci please test | 2026-05-18T20:37:49 | 2026-05-18T20:37:49 | {} | CONTRIBUTOR |
swiftlang | swift | 4,481,950,366 | 88,634 | atrick | @swift-ci test | 2026-05-18T20:39:34 | 2026-05-18T20:39:34 | {} | CONTRIBUTOR |
swiftlang | swift | 4,482,590,915 | 89,184 | meg-gupta | @swift-ci apple silicon benchmark | 2026-05-18T21:52:20 | 2026-05-18T21:52:20 | {} | CONTRIBUTOR |
swiftlang | swift | 4,483,076,908 | 89,234 | DataCorrupted | @swift-ci Please test | 2026-05-18T23:19:50 | 2026-05-18T23:19:50 | {} | CONTRIBUTOR |
swiftlang | swift | 4,483,167,368 | 86,268 | Azoy | Looks like there are some failures here:
```
16:58:55 # | [ RUN ] CompactMapValues.DefaultReturnType
16:58:55 # | stderr>>> Swift/NativeDictionary.swift:477: Fatal error
16:58:55 # | stderr>>> CRASHED: SIGTRAP
16:58:55 # | the test crashed unexpectedly
16:58:55 # | [ FAIL ] CompactMapValues.Default... | 2026-05-18T23:38:42 | 2026-05-18T23:38:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,483,312,633 | 89,231 | glessard | @swift-ci please smoke test | 2026-05-19T00:09:51 | 2026-05-19T00:09:51 | {} | CONTRIBUTOR |
swiftlang | swift | 4,486,824,248 | 88,914 | aidan-hall | @swift-ci test | 2026-05-19T10:28:00 | 2026-05-19T10:28:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,479,839,086 | 89,182 | xedin | @swift-ci please test macOS platform | 2026-05-18T16:46:43 | 2026-05-18T16:46:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,479,947,638 | 89,204 | xedin | I think closure being `@concurrent` here is correct based on the rules of `sending` and `@Sendable`. This closure is considered to be a "boundary" and cannot assume isolation of the context since it's being sent when passed to a parameter. | 2026-05-18T17:00:52 | 2026-05-18T17:00:52 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,482,450,205 | 89,167 | slavapestov | @swift-ci Please test Windows | 2026-05-18T21:35:11 | 2026-05-18T21:35:11 | {} | CONTRIBUTOR |
swiftlang | swift | 4,484,570,488 | 88,634 | atrick | @swift-ci apple silicon benchmark | 2026-05-19T05:02:43 | 2026-05-19T05:02:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,473,400 | 88,936 | gottesmm | @swift-ci test windows platform | 2026-05-15T18:53:56 | 2026-05-15T18:53:56 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,701,272 | 88,634 | atrick | @swift-ci test | 2026-05-15T21:13:35 | 2026-05-15T21:13:35 | {} | CONTRIBUTOR |
swiftlang | swift | 4,465,815,851 | 89,192 | DougGregor | @swift-ci please test | 2026-05-16T05:25:48 | 2026-05-16T05:25:48 | {} | MEMBER |
swiftlang | swift | 4,464,827,618 | 88,820 | kavon | @swift-ci test | 2026-05-16T00:48:05 | 2026-05-16T00:48:05 | {} | MEMBER |
swiftlang | swift | 4,465,210,796 | 89,191 | atrick | @swift-ci test | 2026-05-16T02:41:49 | 2026-05-16T02:41:49 | {} | CONTRIBUTOR |
swiftlang | swift | 4,466,482,377 | 88,683 | egorzhdan | @swift-ci please test | 2026-05-16T09:38:24 | 2026-05-16T09:38:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,467,055,919 | 89,032 | RandomHashTags | > [#89116](https://github.com/swiftlang/swift/pull/89116) should fix this. Let me know if you still see the problem once that makes it into a build.
Can confirm, no longer crashes with `main-snapshot-2026-05-15` toolchain. | 2026-05-16T13:56:18 | 2026-05-16T13:56:18 | {} | NONE |
swiftlang | swift | 4,467,840,300 | 89,195 | patrykstefanski | @swift-ci please test | 2026-05-16T19:06:39 | 2026-05-16T19:06:39 | {} | CONTRIBUTOR |
swiftlang | swift | 4,472,171,582 | 89,199 | atrick | @swift-ci test | 2026-05-17T18:58:46 | 2026-05-17T18:58:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,472,510,374 | 89,201 | airspeedswift | @swift-ci please smoke test | 2026-05-17T21:08:47 | 2026-05-17T21:08:47 | {} | MEMBER |
swiftlang | swift | 4,473,791,960 | 89,206 | gottesmm | @swift-ci test | 2026-05-18T02:40:39 | 2026-05-18T02:40:39 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,469,840 | 88,736 | gottesmm | @swift-ci test windows platform | 2026-05-15T18:53:26 | 2026-05-15T18:53:26 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,726,349 | 89,184 | glessard | @swift-ci please smoke test | 2026-05-15T21:18:31 | 2026-05-15T21:18:31 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,797,205 | 88,924 | mikeash | @swift-ci please smoke test | 2026-05-15T21:31:23 | 2026-05-15T21:31:23 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,916,097 | 89,147 | broken-circle | @ktoso @hamishknight Rebased on top of #89126. Please take a look when you get a chance. | 2026-05-15T21:46:21 | 2026-05-15T21:46:21 | {} | CONTRIBUTOR |
swiftlang | swift | 4,464,721,933 | 89,177 | nkcsgexi | @swift-ci please smoke test | 2026-05-16T00:25:38 | 2026-05-16T00:25:38 | {} | CONTRIBUTOR |
swiftlang | swift | 4,465,304,130 | 88,984 | Kartikayy007 | Working on failed test | 2026-05-16T03:04:15 | 2026-05-16T03:04:15 | {} | NONE |
swiftlang | swift | 4,467,214,307 | 37,214 | johnno1962 | Time passes and it is now possible to come up with a viable implementation for this idea in a few days using AI coding agents to a much higher quality than I could ever have come up with https://github.com/ObservedObject/swift/pull/5. I still maintain this new feature could have been delivered without slowing down the ... | 2026-05-16T15:05:55 | 2026-05-16T15:05:55 | {} | CONTRIBUTOR |
swiftlang | swift | 4,472,022,040 | 89,192 | DougGregor | @swift-ci please build Windows toolchain | 2026-05-17T18:09:36 | 2026-05-17T18:09:36 | {} | MEMBER |
swiftlang | swift | 4,462,076,759 | 89,167 | slavapestov | @swift-ci Please test source compatibility | 2026-05-15T18:02:52 | 2026-05-15T18:02:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,464,671,067 | 89,184 | glessard | @swift-ci please test | 2026-05-16T00:14:28 | 2026-05-16T00:14:28 | {} | CONTRIBUTOR |
swiftlang | swift | 4,464,969,381 | 89,188 | glessard | @swift-ci please smoke test | 2026-05-16T01:20:52 | 2026-05-16T01:20:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,467,608,374 | 89,071 | Snowy1803 | @swift-ci test | 2026-05-16T17:27:05 | 2026-05-16T17:27:05 | {} | MEMBER |
swiftlang | swift | 4,470,666,646 | 86,083 | BenRacicot | Thanks @xedin. Glad to hear #88687 is already in release/6.3, that should help any of our hot paths that hit the `OptimizeHopToExecutor` regression directly.
One specific follow-up on the type-checker side: the second crash shape in our report (the @ViewBuilder capture-list closure in NavigationSplitView) looks like a... | 2026-05-17T12:33:03 | 2026-05-17T12:33:03 | {} | NONE |
swiftlang | swift | 4,473,784,837 | 89,205 | gottesmm | @swift-ci smoke test | 2026-05-18T02:38:29 | 2026-05-18T02:38:29 | {} | CONTRIBUTOR |
swiftlang | swift | 4,476,009,294 | 88,547 | tbkka | @swift-ci Please test Linux | 2026-05-18T08:55:45 | 2026-05-18T08:55:45 | {} | CONTRIBUTOR |
swiftlang | swift | 4,478,273,046 | 89,213 | natecook1000 | @swift-ci Please smoke test | 2026-05-18T13:41:02 | 2026-05-18T13:41:02 | {} | MEMBER |
swiftlang | swift | 4,461,891,717 | 89,176 | hamishknight | @swift-ci please test | 2026-05-15T17:33:08 | 2026-05-15T17:33:08 | {} | CONTRIBUTOR |
swiftlang | swift | 4,461,528,515 | 89,173 | jckarter | Thanks! But I think we should remove the bit width altogether from the check. | 2026-05-15T16:33:32 | 2026-05-15T16:33:32 | {} | CONTRIBUTOR |
swiftlang | swift | 4,461,646,630 | 88,568 | xedin | @swift-ci please test | 2026-05-15T16:53:21 | 2026-05-15T16:53:21 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,054,568 | 89,061 | xedin | https://github.com/swiftlang/sourcekit-lsp/pull/2652
@swift-ci please test | 2026-05-15T17:59:23 | 2026-05-15T17:59:23 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,209,253 | 89,168 | slavapestov | @swift-ci Please test | 2026-05-15T18:22:07 | 2026-05-15T18:22:07 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,251,485 | 89,177 | nkcsgexi | @swift-ci please smoke test | 2026-05-15T18:26:00 | 2026-05-15T18:26:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,541,203 | 89,180 | mikeash | @swift-ci please test | 2026-05-15T19:00:50 | 2026-05-15T19:00:50 | {} | CONTRIBUTOR |
swiftlang | swift | 4,464,045,300 | 88,717 | snej | Thanks, that flag worked for me. | 2026-05-15T21:57:49 | 2026-05-15T21:57:49 | {} | NONE |
swiftlang | swift | 4,466,102,446 | 89,156 | j-hui | Windows failures look unrelated. Restarting. | 2026-05-16T07:01:23 | 2026-05-16T07:01:23 | {} | CONTRIBUTOR |
swiftlang | swift | 4,466,102,744 | 89,156 | j-hui | @swift-ci please smoke test windows platform | 2026-05-16T07:01:32 | 2026-05-16T07:01:32 | {} | CONTRIBUTOR |
swiftlang | swift | 4,466,384,202 | 89,131 | vedant1204-bit | I am interested on work on this
| 2026-05-16T08:50:49 | 2026-05-16T08:50:49 | {} | NONE |
swiftlang | swift | 4,467,220,836 | 89,192 | DougGregor | @swift-ci please build toolchain | 2026-05-16T15:08:40 | 2026-05-16T15:08:40 | {} | MEMBER |
swiftlang | swift | 4,475,036,032 | 89,208 | gottesmm | @swift-ci smoke test | 2026-05-18T06:38:06 | 2026-05-18T06:38:06 | {} | CONTRIBUTOR |
swiftlang | swift | 4,472,451,871 | 89,200 | jamieQ | @swift-ci please smoke test | 2026-05-17T20:42:17 | 2026-05-17T20:42:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,478,297,669 | 88,547 | finagolfin | Huh, off-by-one decimal error on wasm:
```
FloatingPointParsing.Decimal Floats
17:28:00 # | check failed at /home/build-user/swift/test/stdlib/ParseFloat16.swift, line 231
17:28:00 # | first: 29191 (of type Swift.UInt16)
17:28:00 # | second: 29190 (of type Swift.UInt16)
17:28:00 # | [ FAIL ]
```
Pingi... | 2026-05-18T13:43:51 | 2026-05-18T13:43:51 | {} | MEMBER |
swiftlang | swift | 4,462,324,953 | 89,159 | AlexsanderDamaceno | @eeckstein could you smoke test again, some tests failed, I did a small fix a my patch | 2026-05-15T18:35:09 | 2026-05-15T18:35:09 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,691,502 | 88,634 | atrick | @swift-ci test | 2026-05-15T21:12:03 | 2026-05-15T21:12:03 | {} | CONTRIBUTOR |
swiftlang | swift | 4,465,023,047 | 89,190 | sepy97 | @swift-ci please smoke test | 2026-05-16T01:42:29 | 2026-05-16T01:42:29 | {} | CONTRIBUTOR |
swiftlang | swift | 4,476,579,104 | 89,123 | aidan-hall | @swift-ci test windows | 2026-05-18T10:05:42 | 2026-05-18T10:05:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,476,703,601 | 89,209 | hamishknight | @swift-ci please test | 2026-05-18T10:21:56 | 2026-05-18T10:21:56 | {} | CONTRIBUTOR |
swiftlang | swift | 4,478,066,199 | 89,212 | susmonteiro | @swift-ci please smoke test | 2026-05-18T13:18:39 | 2026-05-18T13:18:39 | {} | CONTRIBUTOR |
swiftlang | swift | 4,461,861,765 | 89,149 | patrykstefanski | @swift-ci please test | 2026-05-15T17:28:04 | 2026-05-15T17:28:04 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,559,943 | 89,172 | matthewbastien | I spoke with Charles and it looks like this is simply a limitation of `lldb-dap` in Swift 6.3 on Windows.
A change was made in Swift 6.3 that correctly puts `lldb-dap`'s own process output under the `console` category. However, it cannot distinguish between its own output and the debuggee's and so both will end up un... | 2026-05-15T19:02:19 | 2026-05-15T19:02:19 | {} | MEMBER |
swiftlang | swift | 4,463,628,189 | 89,182 | xedin | @swift-ci please test | 2026-05-15T21:04:23 | 2026-05-15T21:04:23 | {} | CONTRIBUTOR |
swiftlang | swift | 4,464,270,043 | 88,984 | xedin | @swift-ci please test | 2026-05-15T22:34:54 | 2026-05-15T22:34:54 | {} | CONTRIBUTOR |
swiftlang | swift | 4,464,588,799 | 89,189 | tshortli | @swift-ci please smoke test | 2026-05-15T23:52:29 | 2026-05-15T23:52:29 | {} | CONTRIBUTOR |
swiftlang | swift | 4,465,641,756 | 88,750 | finagolfin | Closing for lack of response and because this should've been fixed by 6.3.1, please reopen if not. | 2026-05-16T04:48:02 | 2026-05-16T04:48:02 | {} | MEMBER |
swiftlang | swift | 4,471,139,689 | 89,189 | tshortli | @swift-ci please smoke test Windows | 2026-05-17T15:00:45 | 2026-05-17T15:00:45 | {} | CONTRIBUTOR |
swiftlang | swift | 4,472,794,711 | 89,203 | johnno1962 | Sorry, didn't mean to PR this upstream. | 2026-05-17T23:10:02 | 2026-05-17T23:10:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,475,708,215 | 88,465 | MaxDesiatov | > I'm not sure what's intended to be supported here on wasm already?
Everything is intended to be supported. I'm not aware of any limitations that could prevent this proposal from being supported on Wasm. | 2026-05-18T08:15:10 | 2026-05-18T08:15:10 | {} | CONTRIBUTOR |
swiftlang | swift | 4,461,679,477 | 89,175 | mikeash | @swift-ci please test | 2026-05-15T16:58:37 | 2026-05-15T16:58:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,118,913 | 89,014 | NotTheNHK | Hm, interesting. So it was more of a coincidence than something intentional that made them consistent. Perhaps it would be good to call this out more explicitly in the proposal?
I hope we can improve the ergonomics around closure isolation rules in the future. | 2026-05-15T18:09:02 | 2026-05-15T18:09:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,196,433 | 89,160 | jakepetroules | https://github.com/swiftlang/swift-build/pull/1391
@swift-ci smoke test | 2026-05-15T20:13:54 | 2026-05-15T20:13:54 | {} | CONTRIBUTOR |
swiftlang | swift | 4,463,643,850 | 88,568 | xedin | @nadeemnali looks like the new tests you added are crashing with this change. | 2026-05-15T21:06:28 | 2026-05-15T21:06:28 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,471,259,821 | 86,083 | xedin | > (the @ViewBuilder capture-list closure in NavigationSplitView) looks like an exact match for dup https://github.com/swiftlang/swift/issues/87097
We are working on that at the moment.
> Happy to file that as a separate issue with the .ips attached if it'd be useful, rather than continuing to pile observations onto t... | 2026-05-17T15:43:35 | 2026-05-17T15:43:35 | {} | CONTRIBUTOR |
swiftlang | swift | 4,472,755,147 | 89,202 | airspeedswift | @swift-ci please smoke test | 2026-05-17T22:50:57 | 2026-05-17T22:50:57 | {} | MEMBER |
swiftlang | swift | 4,477,805,472 | 88,868 | charles-zablit | @swift-ci please test | 2026-05-18T12:45:38 | 2026-05-18T12:45:38 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,076,184 | 89,167 | slavapestov | @swift-ci Please smoke test | 2026-05-15T18:02:46 | 2026-05-15T18:02:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,462,864,216 | 88,984 | Kartikayy007 | @xedin done. | 2026-05-15T19:39:23 | 2026-05-15T19:39:23 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.