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,399,110,513 | 88,488 | al45tair | @swift-ci Please smoke test | 2026-05-07T16:43:13 | 2026-05-07T16:43:13 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,327,458 | 88,248 | elsakeirouz | @swift-ci please test source compatibility release | 2026-05-07T17:11:41 | 2026-05-07T17:11:41 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,597,288 | 88,930 | egorzhdan | @swift-ci please test | 2026-05-07T17:41:36 | 2026-05-07T17:41:36 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,905,111 | 88,834 | gottesmm | @swift-ci smoke test macOS platform | 2026-05-07T18:19:05 | 2026-05-07T18:19:05 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,685,621 | 88,914 | aidan-hall | @swift-ci smoke benchmark | 2026-05-07T17:51:29 | 2026-05-07T17:51:29 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,741,227 | 88,777 | azarovalex | @eeckstein yeah afaict we def have to cherry pick this, here is the PR: https://github.com/swiftlang/swift/pull/88932
| 2026-05-07T17:57:42 | 2026-05-07T17:57:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,833,373 | 88,914 | aidan-hall | @swift-ci smoke benchmark | 2026-05-07T18:10:07 | 2026-05-07T18:10:07 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,344,059 | 88,911 | kovdan01 | Tagging @asl @JaapWijnen | 2026-05-07T15:09:37 | 2026-05-07T15:09:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,498,546 | 88,688 | Snowy1803 | This breaks tests and doesn't seem to be the right approach | 2026-05-07T15:28:50 | 2026-05-07T15:28:50 | {} | MEMBER |
swiftlang | swift | 4,399,684,551 | 88,914 | aidan-hall | @swift-ci test | 2026-05-07T17:51:22 | 2026-05-07T17:51:22 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,759,245 | 88,896 | tshortli | Preventing new manifestations might be hard to test, but at the very least there are some conditions that caused this instance of the failure that could be reproduced in a test, right? And adding the `ASSERT` seems like a good idea to me | 2026-05-07T18:00:13 | 2026-05-07T18:00:13 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,844,112 | 88,917 | egorzhdan | @swift-ci please test Windows | 2026-05-07T18:11:31 | 2026-05-07T18:11:31 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,457,720 | 88,900 | lorentey | @swift-ci smoke test | 2026-05-07T17:25:19 | 2026-05-07T17:25:19 | {} | MEMBER |
swiftlang | swift | 4,401,586,667 | 88,931 | airspeedswift | @swift-ci please smoke test | 2026-05-07T22:17:47 | 2026-05-07T22:17:47 | {} | MEMBER |
swiftlang | swift | 4,401,693,873 | 87,885 | hnrklssn | I just merged a related change in https://github.com/swiftlang/swift/pull/88621, so I did a bit of digging there and found out that signatures in macro expansions in clang modules don't end up being properly checked. I took the liberty of making some changes to your PR to test it out using a new option I added. I would... | 2026-05-07T22:42:38 | 2026-05-07T22:42:38 | {} | MEMBER |
swiftlang | swift | 4,402,660,111 | 88,943 | hnrklssn | @swift-ci please test windows platform | 2026-05-08T01:53:14 | 2026-05-08T01:53:14 | {} | MEMBER |
swiftlang | swift | 4,399,106,955 | 88,895 | xedin | @swift-ci please test source compatibility release | 2026-05-07T16:42:45 | 2026-05-07T16:42:45 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,325,749 | 88,248 | elsakeirouz | @swift-ci please benchmark | 2026-05-07T17:11:28 | 2026-05-07T17:11:28 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,194,597 | 88,937 | gottesmm | @swift-ci test | 2026-05-07T19:00:24 | 2026-05-07T19:00:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,660,086 | 88,943 | hnrklssn | **CI Failure:** [Swift Test Windows Platform](https://ci-external.swift.org/job/swift-PR-windows/54635/)
**Reason:** Infrastructure error detected
**Type:** Build system error
```
LINK : fatal error LNK1104: cannot open file 'bin\swiftCore.dll'
```
Automatically retriggering CI to verify if this is a transient infras... | 2026-05-08T01:53:13 | 2026-05-08T01:53:13 | {} | MEMBER |
swiftlang | swift | 4,402,917,161 | 88,931 | airspeedswift | @swift-ci please smoke test | 2026-05-08T02:49:31 | 2026-05-08T02:49:31 | {} | MEMBER |
swiftlang | swift | 4,403,031,323 | 88,926 | airspeedswift | fixed `Reflection/typeref_decoding_packs.swift` failure | 2026-05-08T03:18:33 | 2026-05-08T03:18:33 | {} | MEMBER |
swiftlang | swift | 4,398,357,865 | 88,801 | MaxDesiatov | I don't think the updated description answers enough questions someone stumbling upon the issue would pose.
> This enables more compact and concise expressions.
Which expressions? Expressions in Swift code processed by the parser/AST/Sema modules? SIL in the optimizer? LLVM IR in IRGen?
> To be changed throughout t... | 2026-05-07T15:11:20 | 2026-05-07T15:11:20 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,832,615 | 88,914 | aidan-hall | @swift-ci test | 2026-05-07T18:10:00 | 2026-05-07T18:10:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,637,549 | 88,905 | j-hui | Windows:
```
Build timed out (after 120 minutes). Marking the build as aborted.
Build was aborted
```
Hmmm | 2026-05-07T20:02:11 | 2026-05-07T20:02:11 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,799,267 | 88,900 | lorentey | @eeckstein `SILOptimizer/many_struct_properties_scale_test.swift.gyb` seems to be failing in smoke tests | 2026-05-07T20:26:05 | 2026-05-07T20:26:05 | {} | MEMBER |
swiftlang | swift | 4,400,856,491 | 88,940 | iCharlesHu | Please test with following PRs:
https://github.com/swiftlang/swift-installer-scripts/pull/523
https://github.com/swiftlang/swift-foundation-icu/pull/94
@swift-ci please build toolchain Windows platform | 2026-05-07T20:33:37 | 2026-05-07T20:33:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,950,729 | 88,941 | jckarter | @swift-ci Please test | 2026-05-07T20:45:28 | 2026-05-07T20:45:28 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,951,973 | 88,941 | jckarter | PR for main: https://github.com/swiftlang/swift/pull/88726 | 2026-05-07T20:45:39 | 2026-05-07T20:45:39 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,463,404 | 88,943 | hnrklssn | @swift-ci please smoke test | 2026-05-07T21:52:40 | 2026-05-07T21:52:40 | {} | MEMBER |
swiftlang | swift | 4,401,998,763 | 88,820 | kavon | @swift-ci test | 2026-05-07T23:53:40 | 2026-05-07T23:53:40 | {} | MEMBER |
swiftlang | swift | 4,401,826,020 | 88,940 | compnerd | Please test with following PRs:
https://github.com/swiftlang/swift-installer-scripts/pull/523
https://github.com/swiftlang/swift-foundation-icu/pull/94
@swift-ci please build toolchain Windows platform | 2026-05-07T23:09:03 | 2026-05-07T23:09:03 | {} | MEMBER |
swiftlang | swift | 4,401,914,397 | 88,885 | gottesmm | Problem was in swift-testing where they were using the unsafe pattern. It has been fixed on main and they forward to 6.4. So redoing testing. | 2026-05-07T23:30:52 | 2026-05-07T23:30:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,080,559 | 88,944 | xedin | @swift-ci please test | 2026-05-08T00:10:42 | 2026-05-08T00:10:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,102,545 | 88,811 | xedin | @swift-ci please test macOS platform | 2026-05-07T16:42:10 | 2026-05-07T16:42:10 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,849,286 | 88,903 | j-hui | > I'm quite nervous about relying on this invariant going forward. There isn't a guarantee that NameImporter doesn't start using more requests, and if it does, we'll almost certainly run into another reincarnation of the caching issue.
We already discussed this offline, but to recap what I said for some visibility: ... | 2026-05-07T20:32:38 | 2026-05-07T20:35:35 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,925,279 | 88,726 | jckarter | @swift-ci Please test macOS | 2026-05-07T20:41:48 | 2026-05-07T20:41:48 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,989,566 | 88,875 | slavapestov | @swift-ci Please smoke test macOS | 2026-05-07T16:27:55 | 2026-05-07T16:27:55 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,042,916 | 88,942 | tshortli | @swift-ci please test | 2026-05-07T20:54:29 | 2026-05-07T20:54:29 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,083,680 | 88,811 | xedin | @swift-ci please test | 2026-05-08T00:11:28 | 2026-05-08T00:11:28 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,309,543 | 88,922 | kovdan01 | Tagging @asl @JaapWijnen | 2026-05-07T15:05:21 | 2026-05-07T15:05:21 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,447,392 | 88,851 | airspeedswift | @swift-ci please smoke test macOS platform | 2026-05-07T15:22:34 | 2026-05-07T15:22:34 | {} | MEMBER |
swiftlang | swift | 4,398,532,024 | 57,903 | marcomasser | This issue is gone in Swift 6.3.2 (and possibly earlier). | 2026-05-07T15:33:08 | 2026-05-07T15:33:08 | {} | NONE |
swiftlang | swift | 4,398,687,559 | 88,017 | NotTheNHK | @FranzBusch I fixed the documentation and improved the new test I added. The test should now properly test concurrent iteration. Previously, it sometimes resumed too quickly, so the consumers were not enqueued in the consumer queue. It should be simpler to test this kind of concurrent behavior in the future once we can... | 2026-05-07T15:52:37 | 2026-05-07T15:52:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,641,635 | 88,896 | tshortli | Is there no test we can add to verify the fix? | 2026-05-07T17:46:53 | 2026-05-07T17:46:53 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,830,642 | 88,914 | aidan-hall | @swift-ci smoke test | 2026-05-07T18:09:44 | 2026-05-07T18:09:44 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,147,042 | 88,938 | airspeedswift | @swift-ci please smoke test | 2026-05-07T21:06:44 | 2026-05-07T21:06:44 | {} | MEMBER |
swiftlang | swift | 4,402,014,858 | 88,916 | xedin | @swift-ci please smoke test | 2026-05-07T23:57:00 | 2026-05-07T23:57:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,132,095 | 88,908 | hnrklssn | @swift-ci please smoke test | 2026-05-07T16:46:11 | 2026-05-07T16:46:11 | {} | MEMBER |
swiftlang | swift | 4,399,324,922 | 88,248 | elsakeirouz | @swift-ci please test | 2026-05-07T17:11:23 | 2026-05-07T17:11:23 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,537,881 | 88,928 | hnrklssn | @swift-ci please test | 2026-05-07T17:34:22 | 2026-05-07T17:34:22 | {} | MEMBER |
swiftlang | swift | 4,400,484,438 | 88,775 | compnerd | @swift-ci please test Windows platform | 2026-05-07T19:39:35 | 2026-05-07T19:39:35 | {} | MEMBER |
swiftlang | swift | 4,401,223,838 | 88,929 | sepy97 | @swift-ci please smoke test | 2026-05-07T21:17:20 | 2026-05-07T21:17:20 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,683,126 | 87,885 | hnrklssn | @swift-ci please smoke test | 2026-05-07T22:40:04 | 2026-05-07T22:40:04 | {} | MEMBER |
swiftlang | swift | 4,398,465,915 | 88,664 | keith | @swift-ci please test macOS Platform | 2026-05-07T15:24:39 | 2026-05-07T15:24:39 | {} | MEMBER |
swiftlang | swift | 4,398,466,640 | 88,664 | keith | @swift-ci please test Windows Platform | 2026-05-07T15:24:44 | 2026-05-07T15:24:44 | {} | MEMBER |
swiftlang | swift | 4,399,401,008 | 88,904 | airspeedswift | Missing a test for the runtime detection... | 2026-05-07T17:19:48 | 2026-05-07T17:19:48 | {} | MEMBER |
swiftlang | swift | 4,400,726,343 | 88,900 | lorentey | ```
11:36:04
******************** TEST 'Swift-validation(linux-x86_64) :: SILOptimizer/many_struct_properties_scale_test.swift.gyb' FAILED ********************
11:36:04 Exit Code: 0
11:36:04
11:36:04 Command Output (stdout):
11:36:04 --
11:36:04 # RUN: at line 1
11:36:04 /usr/bin/python3.10 /home/build... | 2026-05-07T20:15:21 | 2026-05-07T20:15:21 | {} | MEMBER |
swiftlang | swift | 4,400,745,592 | 88,939 | rjmccall | @swift-ci Please test | 2026-05-07T20:18:17 | 2026-05-07T20:18:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,425,733 | 88,851 | airspeedswift | @swift-ci please test | 2026-05-08T01:11:03 | 2026-05-08T01:11:03 | {} | MEMBER |
swiftlang | swift | 4,399,289,824 | 88,904 | airspeedswift | @swift-ci please smoke test | 2026-05-07T17:07:21 | 2026-05-07T17:07:21 | {} | MEMBER |
swiftlang | swift | 4,400,006,410 | 88,934 | glessard | @swift-ci please smoke test | 2026-05-07T18:33:00 | 2026-05-07T18:33:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,305,680 | 83,073 | Catfish-Man | @swift-ci please test | 2026-05-08T00:56:43 | 2026-05-08T00:56:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,323,550 | 88,342 | Catfish-Man | @swift-ci please test | 2026-05-08T00:59:58 | 2026-05-08T00:59:58 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,727,885 | 88,904 | jckarter | > Just because I'm curious: is there a reason for diagnosing this in IRGen rather than the frontend?
We don't know the sizes of types until IRGen, so we wouldn't be able to enforce a byte-size-based limit any earlier. Perhaps we could diagnose an element size that's statically >4Gi elements.
We can still encounte... | 2026-05-07T15:57:01 | 2026-05-07T15:57:01 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,683,868 | 88,914 | aidan-hall | @swift-ci smoke test | 2026-05-07T17:51:18 | 2026-05-07T17:51:18 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,162,479 | 88,936 | gottesmm | @swift-ci smoke test | 2026-05-07T18:56:28 | 2026-05-07T18:56:28 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,924,988 | 88,938 | airspeedswift | @swift-ci please smoke test linux platform | 2026-05-08T02:51:39 | 2026-05-08T02:51:39 | {} | MEMBER |
swiftlang | swift | 4,403,010,443 | 85,469 | DancecardJK | I have encountered the exact same problem which I think might be related to:
https://github.com/swiftlang/swift/issues/79447
https://github.com/swiftlang/swift/pull/87664
And this issue notes the regression between Xcode 26.3 and Xcode 26.4:
https://github.com/swiftlang/swift-testing/issues/1643 | 2026-05-08T03:13:16 | 2026-05-08T03:24:51 | {} | NONE |
swiftlang | swift | 4,403,198,814 | 88,925 | Kartikayy007 | @AnthonyLatsis ill be working on it. | 2026-05-08T03:58:59 | 2026-05-08T03:58:59 | {} | NONE |
swiftlang | swift | 4,387,002,018 | 88,273 | aidan-hall | @swift-ci test macos | 2026-05-06T10:10:30 | 2026-05-06T10:10:30 | {} | CONTRIBUTOR |
swiftlang | swift | 4,387,045,463 | 88,624 | d-ronnqvist | @swift-ci please test Windows | 2026-05-06T10:17:26 | 2026-05-06T10:17:26 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,323,991 | 88,860 | airspeedswift | @swift-ci please smoke test | 2026-05-06T17:06:07 | 2026-05-06T17:06:07 | {} | MEMBER |
swiftlang | swift | 4,390,413,536 | 88,882 | drexin | Merge after https://github.com/swiftlang/swift/pull/88804 | 2026-05-06T17:20:00 | 2026-05-06T17:20:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,717,844 | 88,811 | xedin | @swift-ci please test source compatibility | 2026-05-06T18:07:34 | 2026-05-06T18:07:34 | {} | CONTRIBUTOR |
swiftlang | swift | 4,391,183,874 | 88,889 | gottesmm | @swift-ci test | 2026-05-06T19:20:12 | 2026-05-06T19:20:12 | {} | CONTRIBUTOR |
swiftlang | swift | 4,391,188,988 | 88,862 | DougGregor | @swift-ci please test | 2026-05-06T19:20:46 | 2026-05-06T19:20:46 | {} | MEMBER |
swiftlang | swift | 4,391,730,470 | 88,890 | tshortli | @swift-ci please smoke test | 2026-05-06T20:13:22 | 2026-05-06T20:13:22 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,780,406 | 83,073 | Catfish-Man | @swift-ci please test | 2026-05-06T22:51:58 | 2026-05-06T22:51:58 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,791,173 | 88,884 | gottesmm | Failure is due to an issue in Swift Testing | 2026-05-06T22:53:57 | 2026-05-06T22:53:57 | {} | CONTRIBUTOR |
swiftlang | swift | 4,387,802,764 | 88,825 | eeckstein | @swift-ci smoke test | 2026-05-06T12:16:00 | 2026-05-06T12:16:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,388,847,650 | 88,247 | artemcm | @swift-ci smoke test | 2026-05-06T14:03:03 | 2026-05-06T14:03:03 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,561,697 | 88,683 | egorzhdan | > "Upcasting foreign reference types" is somewhat underselling what this does. It's modeling inheritance of FRTs as Swift inheritance
Yeap, let me rephrase the title of this PR!
> We have a bunch of code for "mirroring" declarations of C++ base classes into the Swift declarations for their derived classes. I expe... | 2026-05-06T17:43:15 | 2026-05-06T17:43:15 | {} | CONTRIBUTOR |
swiftlang | swift | 4,387,061,085 | 88,838 | Snowy1803 | @swift-ci please test | 2026-05-06T10:19:47 | 2026-05-06T10:19:47 | {} | MEMBER |
swiftlang | swift | 4,388,097,057 | 88,867 | charles-zablit | @swift-ci please smoke test | 2026-05-06T12:46:06 | 2026-05-06T12:46:06 | {} | CONTRIBUTOR |
swiftlang | swift | 4,389,136,960 | 88,873 | airspeedswift | @swift-ci please smoke test | 2026-05-06T14:34:57 | 2026-05-06T14:34:57 | {} | MEMBER |
swiftlang | swift | 4,389,277,388 | 88,874 | Xazax-hun | @swift-ci please test | 2026-05-06T14:51:24 | 2026-05-06T14:51:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,389,961,669 | 88,854 | hnrklssn | I'm confused. Does this currently trigger a warning or not? | 2026-05-06T16:11:36 | 2026-05-06T16:11:36 | {} | MEMBER |
swiftlang | swift | 4,390,500,567 | 88,038 | shahmishal | This change won’t be included in the Swift 6.3.2 release. If it’s important, please contact the release-mangers on forums.swift.org as soon as possible. | 2026-05-06T17:33:46 | 2026-05-06T17:33:46 | {} | MEMBER |
swiftlang | swift | 4,390,606,842 | 88,880 | hnrklssn | This seems to be not an issue with `__counted_by` having an integer literal count expression, but rather that `swift-synthesize-interface` does not trigger the safe overload expansion. Adding this to a swift file should still compile:
```
import CLib
func foo(_ inputs: UnsafeBufferPointer<Element>, _ outputs: UnsafeMu... | 2026-05-06T17:50:22 | 2026-05-06T17:50:22 | {} | MEMBER |
swiftlang | swift | 4,390,772,441 | 88,712 | adrian-prantl | Can you add a comment explaining the -1? | 2026-05-06T18:16:06 | 2026-05-06T18:16:06 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,391,900,346 | 88,847 | meg-gupta | @swift-ci test macOS platform | 2026-05-06T20:33:31 | 2026-05-06T20:33:31 | {} | CONTRIBUTOR |
swiftlang | swift | 4,391,913,663 | 88,882 | drexin | @swift-ci smoke test | 2026-05-06T20:35:00 | 2026-05-06T20:35:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,387,001,608 | 88,273 | aidan-hall | @swift-ci test linux | 2026-05-06T10:10:26 | 2026-05-06T10:10:26 | {} | CONTRIBUTOR |
swiftlang | swift | 4,388,533,635 | 88,847 | meg-gupta | @swift-ci test macOS platform | 2026-05-06T13:29:24 | 2026-05-06T13:29:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,107,036 | 88,878 | gottesmm | @swift-ci test | 2026-05-06T16:33:17 | 2026-05-06T16:33:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,277,209 | 88,804 | drexin | @swift-ci smoke test | 2026-05-06T16:59:02 | 2026-05-06T16:59:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,348,123 | 88,685 | rjmccall | I see, we're matching the signature of a static extension method on `GlobalActor`. Alright. | 2026-05-06T17:09:55 | 2026-05-06T17:09:55 | {} | CONTRIBUTOR |
swiftlang | swift | 4,390,805,876 | 88,854 | patrykstefanski | > I'm confused. Does this currently trigger a warning or not?
Sorry, my commit message says why the warning was happening before. The warning doesn't trigger anymore. | 2026-05-06T18:21:24 | 2026-05-06T18:21:24 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,390,826,355 | 88,854 | patrykstefanski | @swift-ci please smoke test Windows Platform | 2026-05-06T18:24:44 | 2026-05-06T18:24:44 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.