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,435,690,118
88,775
compnerd
Please test with following PRs: https://github.com/llvm/llvm-project/pull/197237 @swift-ci please test Windows platform
2026-05-12T23:36:40
2026-05-12T23:36:40
{}
MEMBER
swiftlang
swift
4,435,733,084
89,016
compnerd
@swift-ci please smoke test
2026-05-12T23:45:42
2026-05-12T23:45:42
{}
MEMBER
swiftlang
swift
4,440,465,908
89,039
egorzhdan
> Is it possible for some of these headers to be missing on some of the distros that we support? Yes, some of the old versions of libstdc++ won't have all of these headers available – this is why these headers are not directly listed in the modulemap file, but rather in the automatic modulemap generator that checks ...
2026-05-13T11:29:49
2026-05-13T11:29:49
{}
CONTRIBUTOR
swiftlang
swift
4,441,173,835
89,074
egorzhdan
@swift-ci please smoke test
2026-05-13T12:52:32
2026-05-13T12:52:32
{}
CONTRIBUTOR
swiftlang
swift
4,442,042,279
88,868
charles-zablit
It looks like `symstore.exe` is not installed on the bots.
2026-05-13T14:29:20
2026-05-13T14:29:20
{}
CONTRIBUTOR
swiftlang
swift
4,433,594,906
89,054
compnerd
@swift-ci please smoke test
2026-05-12T18:34:23
2026-05-12T18:34:23
{}
MEMBER
swiftlang
swift
4,436,913,140
88,775
compnerd
Please test with following PRs: https://github.com/llvm/llvm-project/pull/197237 @swift-ci please test Windows platform
2026-05-13T03:33:18
2026-05-13T03:33:18
{}
MEMBER
swiftlang
swift
4,438,479,979
88,883
cvogelbusch
I worked with Patrick on changing the code so it compiles normal again. If you want to see the but you need to use the older version 2.62.
2026-05-13T07:33:10
2026-05-13T07:33:10
{}
NONE
swiftlang
swift
4,443,273,816
88,547
tbkka
@swift-ci Please test Windows
2026-05-13T16:41:28
2026-05-13T16:41:28
{}
CONTRIBUTOR
swiftlang
swift
4,433,613,275
88,041
compnerd
@shahmishal - feel free to re-open and merge if you want to get diagnostics on failures in CI.
2026-05-12T18:36:47
2026-05-12T18:36:47
{}
MEMBER
swiftlang
swift
4,433,815,079
89,056
eeckstein
@swift-ci smoke test
2026-05-12T19:04:41
2026-05-12T19:04:41
{}
CONTRIBUTOR
swiftlang
swift
4,435,074,522
89,061
xedin
@swift-ci please build toolchain macOS
2026-05-12T21:43:05
2026-05-12T21:43:05
{}
CONTRIBUTOR
swiftlang
swift
4,435,182,561
89,057
nkcsgexi
@swift-ci please smoke test https://github.com/swiftlang/llvm-project/pull/12952
2026-05-12T22:03:04
2026-05-12T22:03:04
{}
CONTRIBUTOR
swiftlang
swift
4,435,953,291
88,909
j-hui
@swift-ci please smoke test
2026-05-13T00:29:31
2026-05-13T00:29:31
{}
CONTRIBUTOR
swiftlang
swift
4,436,113,151
89,025
ktoso
17:41:44 Swift(macosx-x86_64) :: SILOptimizer/ownership_liveness_unit.sil
2026-05-13T00:59:49
2026-05-13T00:59:49
{}
CONTRIBUTOR
swiftlang
swift
4,441,338,131
88,918
kovdan01
@eeckstein I would appreciate if you as the code owner can take a quick look at this to ensure that nothing tremendously bad is introduced in this patch. The PR is relatively simple and anyway AutoDiff-specific. I just wanted to ensure that you do not have concerns and objections for merging this (and if you have - ...
2026-05-13T13:11:14
2026-05-13T13:11:14
{}
CONTRIBUTOR
swiftlang
swift
4,441,381,597
89,075
al45tair
@swift-ci Please test
2026-05-13T13:16:28
2026-05-13T13:16:28
{}
CONTRIBUTOR
swiftlang
swift
4,442,753,967
83,616
Xazax-hun
@swift-ci please smoke test
2026-05-13T15:44:58
2026-05-13T15:44:58
{}
CONTRIBUTOR
swiftlang
swift
4,433,388,489
89,051
artemcm
@swift-ci test
2026-05-12T18:11:53
2026-05-12T18:11:53
{}
CONTRIBUTOR
swiftlang
swift
4,435,155,796
89,062
jakepetroules
@swift-ci test
2026-05-12T21:58:21
2026-05-12T21:58:21
{}
CONTRIBUTOR
swiftlang
swift
4,435,733,096
89,065
glessard
@swift-ci please test
2026-05-12T23:45:42
2026-05-12T23:45:42
{}
CONTRIBUTOR
swiftlang
swift
4,435,896,333
89,057
nkcsgexi
https://github.com/swiftlang/llvm-project/pull/12952 @swift-ci please smoke test
2026-05-13T00:19:55
2026-05-13T00:19:55
{}
CONTRIBUTOR
swiftlang
swift
4,438,088,814
89,069
drexin
@swift-ci smoke test
2026-05-13T06:40:14
2026-05-13T06:40:14
{}
CONTRIBUTOR
swiftlang
swift
4,438,851,170
89,049
artemcm
@swift-ci smoke test Windows platform
2026-05-13T08:18:57
2026-05-13T08:18:57
{}
CONTRIBUTOR
swiftlang
swift
4,441,240,500
89,073
hamishknight
Duplicate of #86438
2026-05-13T13:00:09
2026-05-13T13:00:09
{}
CONTRIBUTOR
swiftlang
swift
4,442,952,975
89,061
xedin
@swift-ci please test
2026-05-13T16:06:43
2026-05-13T16:06:43
{}
CONTRIBUTOR
swiftlang
swift
4,433,312,559
89,048
eeckstein
@swift-ci smoke test
2026-05-12T18:00:52
2026-05-12T18:00:52
{}
CONTRIBUTOR
swiftlang
swift
4,436,114,025
89,025
ktoso
@swift-ci please test macOS
2026-05-13T00:59:56
2026-05-13T00:59:56
{}
CONTRIBUTOR
swiftlang
swift
4,433,093,741
89,015
xedin
@swift-ci please test
2026-05-12T17:30:07
2026-05-12T17:30:07
{}
CONTRIBUTOR
swiftlang
swift
4,436,022,819
89,053
atrick
@swift-ci test
2026-05-13T00:42:53
2026-05-13T00:42:53
{}
CONTRIBUTOR
swiftlang
swift
4,436,701,580
89,050
tshortli
@swift-ci please smoke test Windows
2026-05-13T02:45:54
2026-05-13T02:45:54
{}
CONTRIBUTOR
swiftlang
swift
4,439,056,346
89,068
MaxDesiatov
@swift-ci build toolchain
2026-05-13T08:47:05
2026-05-13T08:47:05
{}
CONTRIBUTOR
swiftlang
swift
4,441,517,304
89,053
aidan-hall
@swift-ci smoke test
2026-05-13T13:31:25
2026-05-13T13:31:25
{}
CONTRIBUTOR
swiftlang
swift
4,442,553,417
89,039
egorzhdan
Ugh: ``` /usr/lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/coroutine:334:2: error: "the coroutine header requires -fcoroutines" ```
2026-05-13T15:21:38
2026-05-13T15:21:38
{}
CONTRIBUTOR
swiftlang
swift
4,411,730,002
88,983
atrick
@swift-ci test
2026-05-09T06:31:42
2026-05-09T06:31:42
{}
CONTRIBUTOR
swiftlang
swift
4,412,534,434
88,944
xedin
@swift-ci please smoke test macOS platform
2026-05-09T12:36:11
2026-05-09T12:36:11
{}
CONTRIBUTOR
swiftlang
swift
4,413,091,312
88,907
natecook1000
@swift-ci Please build toolchain macOS platform
2026-05-09T17:15:58
2026-05-09T17:15:58
{}
MEMBER
swiftlang
swift
4,413,149,632
68,296
cobbal
Could this be the same issue as https://github.com/swiftlang/swift-corelibs-foundation/issues/4214 and that cyclic data isn't supported on non-objc platforms?
2026-05-09T17:36:56
2026-05-09T17:36:56
{}
NONE
swiftlang
swift
4,422,061,453
88,248
elsakeirouz
@swift-ci apple silicon benchmark
2026-05-11T15:20:25
2026-05-11T15:20:25
{}
CONTRIBUTOR
swiftlang
swift
4,412,890,608
87,638
NachoSoto
@DougGregor van somebody triage this? 🙏
2026-05-09T15:38:29
2026-05-09T15:38:29
{}
CONTRIBUTOR
swiftlang
swift
4,416,529,063
74,395
NotTheNHK
@ktoso I was just browsing so far, so maybe I misunderstood what this [piece of code](https://github.com/swiftlang/swift/blob/33ae6060115a5a596ecace49c70e8848d3d92ea5/stdlib/public/Concurrency/TaskSleepDuration.swift#L121) does. Now I’m curious and will test it. Edit: The reproducer is still falling and continues to c...
2026-05-10T22:38:14
2026-05-10T22:59:40
{}
CONTRIBUTOR
swiftlang
swift
4,417,749,102
88,753
12ya
> I think the new lines were added purposely for markdown fomatting purposes now it's better formatted and follows line max char limit convention closer
2026-05-11T05:08:28
2026-05-11T05:08:28
{}
CONTRIBUTOR
swiftlang
swift
4,422,140,438
89,008
egorzhdan
@swift-ci please test
2026-05-11T15:29:32
2026-05-11T15:29:32
{}
CONTRIBUTOR
swiftlang
swift
4,422,605,666
88,480
slavapestov
@swift-ci Please smoke test macOS
2026-05-11T16:23:36
2026-05-11T16:23:36
{}
CONTRIBUTOR
swiftlang
swift
4,423,149,125
89,007
mikeash
`swift_slowAlloc` includes the `NULL` check and will give you consistent error handling there, so I'd suggest switching to that.
2026-05-11T17:26:19
2026-05-11T17:26:19
{}
CONTRIBUTOR
swiftlang
swift
4,423,169,117
88,885
gottesmm
Swift Testing fix has landed. Retesting!
2026-05-11T17:29:15
2026-05-11T17:29:15
{}
CONTRIBUTOR
swiftlang
swift
4,423,236,982
88,870
Snowy1803
@swift-ci test
2026-05-11T17:38:06
2026-05-11T17:38:06
{}
MEMBER
swiftlang
swift
4,422,592,812
89,006
tshortli
@swift-ci please test
2026-05-11T16:22:04
2026-05-11T16:22:04
{}
CONTRIBUTOR
swiftlang
swift
4,413,408,267
88,775
compnerd
@swift-ci please test Windows platform
2026-05-09T18:47:33
2026-05-09T18:47:33
{}
MEMBER
swiftlang
swift
4,416,259,019
88,488
al45tair
@swift-ci Please smoke test
2026-05-10T20:22:23
2026-05-10T20:22:23
{}
CONTRIBUTOR
swiftlang
swift
4,416,511,678
83,446
tothambrus11
Related: https://github.com/swiftlang/swift-package-manager/issues/10041 For the time being, I made a simple GitHub action to bundle required DLLs besides the executable when linking dynamically: https://github.com/hylo-lang/swift-windows-dll-bundler/
2026-05-10T22:29:21
2026-05-10T22:41:17
{}
NONE
swiftlang
swift
4,417,725,480
88,979
DougGregor
@swift-ci please smoke test
2026-05-11T05:01:42
2026-05-11T05:01:42
{}
MEMBER
swiftlang
swift
4,419,849,240
88,838
Snowy1803
> Should we have a verifier step that checks whether an alloc_stack has fragments? If SROA is the only pass adding these, it's probably ok to ignore this idea The next PR in line, #88845, completely removes support for having a DIExpr within alloc_stacks
2026-05-11T10:38:33
2026-05-11T10:38:33
{}
MEMBER
swiftlang
swift
4,422,059,860
88,248
elsakeirouz
@swift-ci please test source compatibility release
2026-05-11T15:20:14
2026-05-11T15:20:14
{}
CONTRIBUTOR
swiftlang
swift
4,423,030,923
88,780
susmonteiro
@swift-ci please test windows
2026-05-11T17:11:40
2026-05-11T17:11:40
{}
CONTRIBUTOR
swiftlang
swift
4,413,986,563
88,990
Azoy
@swift-ci please test Windows
2026-05-09T23:55:00
2026-05-09T23:55:00
{}
CONTRIBUTOR
swiftlang
swift
4,416,560,710
88,854
patrykstefanski
@swift-ci please smoke test macOS Platform
2026-05-10T22:55:48
2026-05-10T22:55:48
{}
CONTRIBUTOR
swiftlang
swift
4,418,346,008
88,838
felipepiovezan
@swift-ci smoke test macOS platform
2026-05-11T07:15:16
2026-05-11T07:15:16
{}
CONTRIBUTOR
swiftlang
swift
4,418,604,738
87,871
j-hui
@swift-ci please smoke test
2026-05-11T07:55:51
2026-05-11T07:55:51
{}
CONTRIBUTOR
swiftlang
swift
4,419,429,989
88,998
eeckstein
@swift-ci smoke test
2026-05-11T09:50:35
2026-05-11T09:50:35
{}
CONTRIBUTOR
swiftlang
swift
4,420,645,673
89,002
tshortli
@swift-ci please test source compatibility
2026-05-11T12:24:46
2026-05-11T12:24:46
{}
CONTRIBUTOR
swiftlang
swift
4,421,126,878
88,780
susmonteiro
@swift-ci please smoke test
2026-05-11T13:26:53
2026-05-11T13:26:53
{}
CONTRIBUTOR
swiftlang
swift
4,422,528,842
88,962
Snowy1803
@swift-ci please test
2026-05-11T16:14:40
2026-05-11T16:14:40
{}
MEMBER
swiftlang
swift
4,414,192,745
60,115
Catfish-Man
@swift-ci please apple silicon benchmark
2026-05-10T01:59:37
2026-05-10T01:59:37
{}
CONTRIBUTOR
swiftlang
swift
4,414,234,808
88,826
Jiaxu-Li
@swift-ci please test
2026-05-10T02:22:41
2026-05-10T02:22:41
{}
CONTRIBUTOR
swiftlang
swift
4,415,607,080
88,981
augusto2112
@swift-ci test
2026-05-10T15:07:39
2026-05-10T15:07:39
{}
CONTRIBUTOR
swiftlang
swift
4,420,438,763
88,413
tothambrus11
There is a related issue in https://github.com/SwiftyLab/setup-swift/issues/457 that doesn't see a signature at the place it usually expected and always emits a warning on Windows. Should the signature verification logic be changed? Do you know where signatures are expected to be published?
2026-05-11T11:55:30
2026-05-11T11:56:03
{}
NONE
swiftlang
swift
4,420,873,252
88,890
tshortli
@swift-ci please smoke test macOS
2026-05-11T12:55:17
2026-05-11T12:55:17
{}
CONTRIBUTOR
swiftlang
swift
4,422,058,698
88,248
elsakeirouz
@swift-ci please test
2026-05-11T15:20:07
2026-05-11T15:20:07
{}
CONTRIBUTOR
swiftlang
swift
4,411,790,449
60,115
Catfish-Man
@swift-ci please apple silicon benchmark
2026-05-09T06:57:21
2026-05-09T06:57:21
{}
CONTRIBUTOR
swiftlang
swift
4,412,913,913
88,987
airspeedswift
Looks like this doesn't happen in 6.3, likely caused by the recent pack specialization pass.
2026-05-09T15:49:14
2026-05-09T15:49:14
{}
MEMBER
swiftlang
swift
4,413,243,834
88,990
Azoy
@swift-ci please test
2026-05-09T18:03:58
2026-05-09T18:03:58
{}
CONTRIBUTOR
swiftlang
swift
4,419,888,728
88,996
finagolfin
@swift-ci test windows
2026-05-11T10:42:50
2026-05-11T10:42:50
{}
MEMBER
swiftlang
swift
4,420,096,618
88,683
egorzhdan
@swift-ci please test macOS arm64
2026-05-11T11:08:01
2026-05-11T11:08:01
{}
CONTRIBUTOR
swiftlang
swift
4,412,642,840
88,810
Catfish-Man
@swift-ci please smoke test Windows platform
2026-05-09T13:34:42
2026-05-09T13:34:42
{}
CONTRIBUTOR
swiftlang
swift
4,412,888,704
88,826
hamishknight
@swift-ci please test source compatibility
2026-05-09T15:37:39
2026-05-09T15:37:39
{ "laugh": 1 }
CONTRIBUTOR
swiftlang
swift
4,414,611,290
88,993
xedin
Indeed the problem here is related to the fact that closure in this expression `MyOperation(migrationWork: { })` is `@MainActor` isolated and a recent bug fix exposed a latent bug in OptimizeHopToExecutor pass where hop backs are incorrectly eliminated in this case. We are working on a fix.
2026-05-10T06:20:35
2026-05-10T06:21:25
{ "+1": 1 }
CONTRIBUTOR
swiftlang
swift
4,415,644,510
83,446
tothambrus11
Hi, are there any updates on static linking on Windows? Is there any way I could help? Edit: I found this thread: https://forums.swift.org/t/towards-static-stdlib-support-on-windows/77728 And the following example: https://github.com/compnerd/vigil/blob/main/.github/workflows/release.yml I'll try this, thanks for all...
2026-05-10T15:25:42
2026-05-10T16:11:28
{}
NONE
swiftlang
swift
4,416,560,991
88,854
patrykstefanski
@swift-ci please smoke test Windows Platform
2026-05-10T22:55:57
2026-05-10T22:55:57
{}
CONTRIBUTOR
swiftlang
swift
4,411,718,548
88,980
atrick
@swift-ci test
2026-05-09T06:26:54
2026-05-09T06:26:54
{}
CONTRIBUTOR
swiftlang
swift
4,411,803,742
88,973
Catfish-Man
@swift-ci please test
2026-05-09T07:02:34
2026-05-09T07:02:34
{}
CONTRIBUTOR
swiftlang
swift
4,412,790,562
88,828
airspeedswift
@swift-ci please test
2026-05-09T14:49:37
2026-05-09T14:49:37
{}
MEMBER
swiftlang
swift
4,413,072,198
88,900
xavgru12
@swift-ci smoke test
2026-05-09T17:06:21
2026-05-09T17:06:21
{}
CONTRIBUTOR
swiftlang
swift
4,416,500,949
74,395
ktoso
I wouldn't expect sleep to be fixed, no. Have you confirmed otherwise?
2026-05-10T22:23:26
2026-05-10T22:23:26
{}
CONTRIBUTOR
swiftlang
swift
4,421,325,398
88,993
jamieQ
Here's a slight variation with similar structure that doesn't use an intermediary storage type: ```swift actor MyActor {} extension Actor { nonisolated func perform(_ work: (isolated Self) async -> Void) async { await work(self) } } func bug( _ a: isolated some Actor, _ c: nonisolated(nonsend...
2026-05-11T13:50:31
2026-05-11T13:50:31
{ "+1": 1 }
CONTRIBUTOR
swiftlang
swift
4,411,179,253
88,931
airspeedswift
@swift-ci please smoke test
2026-05-09T02:45:24
2026-05-09T02:45:24
{}
MEMBER
swiftlang
swift
4,412,057,024
88,964
Xazax-hun
@swift-ci please smoke test Windows
2026-05-09T08:37:24
2026-05-09T08:37:24
{}
CONTRIBUTOR
swiftlang
swift
4,413,015,149
81,772
atifdev10
See my [answer](https://forums.swift.org/t/how-to-use-implements-in-a-get-only-property/67158/4) on this.
2026-05-09T16:38:22
2026-05-09T16:38:22
{}
NONE
swiftlang
swift
4,414,907,152
88,474
mlvea
@swift-ci please test
2026-05-10T09:05:56
2026-05-10T09:05:56
{}
NONE
swiftlang
swift
4,416,497,580
74,395
NotTheNHK
@ktoso IIUC, this was fixed in Swift 6.2? We now enqueue on the Task’s current executor and only use the global enqueue as a fallback.
2026-05-10T22:21:41
2026-05-10T22:21:41
{}
CONTRIBUTOR
swiftlang
swift
4,416,663,324
88,979
DougGregor
@swift-ci please smoke test
2026-05-10T23:50:17
2026-05-10T23:50:17
{}
MEMBER
swiftlang
swift
4,417,445,614
88,455
finagolfin
I can reproduce with the latest May 7 trunk snapshot toolchain on macOS: ``` error: compile command failed due to signal 6 (use -v to see invocation) Assertion failed: ((AccessKind == SGFAccessKind::BorrowedObjectRead || AccessKind == SGFAccessKind::BorrowedAddressRead) && "non-borrow component requires an address base...
2026-05-11T03:43:56
2026-05-11T03:43:56
{}
MEMBER
swiftlang
swift
4,418,347,842
88,838
felipepiovezan
@swift-ci test macos platform
2026-05-11T07:15:34
2026-05-11T07:15:34
{}
CONTRIBUTOR
swiftlang
swift
4,422,101,146
89,007
broken-circle
The claimed overflow isn't reachable, since the source and destination sizes are the same expression on consecutive lines: `malloc(name.size())` then `memcpy(_, _, name.size())`.
2026-05-11T15:24:53
2026-05-11T15:24:53
{}
CONTRIBUTOR
swiftlang
swift
4,412,461,497
60,115
Catfish-Man
Looks like xmalloc improved this from ~5x slower to ~2x slower. I should try 1.625x growth again I guess, though iirc there were code size issues there.
2026-05-09T11:56:49
2026-05-09T11:56:49
{}
CONTRIBUTOR
swiftlang
swift
4,413,359,798
87,638
xedin
I will take a look on Monday, thank you!
2026-05-09T18:31:56
2026-05-09T18:31:56
{}
CONTRIBUTOR
swiftlang
swift
4,420,107,542
89,001
al45tair
@swift-ci Please test
2026-05-11T11:09:15
2026-05-11T11:09:15
{}
CONTRIBUTOR
swiftlang
swift
4,420,715,623
88,923
artemcm
https://github.com/swiftlang/swift-syntax/pull/3327 @swift-ci test
2026-05-11T12:33:50
2026-05-11T12:33:50
{}
CONTRIBUTOR
swiftlang
swift
4,421,120,485
89,004
artemcm
@swift-ci smoke test
2026-05-11T13:26:08
2026-05-11T13:26:08
{}
CONTRIBUTOR
swiftlang
swift
4,423,169,781
88,885
gottesmm
@swift-ci test
2026-05-11T17:29:21
2026-05-11T17:29:21
{}
CONTRIBUTOR