id int64 393k 2.82B | repo stringclasses 68
values | title stringlengths 1 936 | body stringlengths 0 256k ⌀ | labels stringlengths 2 508 | priority stringclasses 3
values | severity stringclasses 3
values |
|---|---|---|---|---|---|---|
2,557,758,127 | PowerToys | [Advanced Paste] - Add "Copy by column or zone" | ### Description of the new feature / enhancement
"Copy by Column" acting the same as the actual everyday copy function (being by rows) but vertically, down to the end of the page (not the window). By pointer definibile column start and width.
"Copy by Zone" acts creating a quadrangular zone with the pointer to inscribe a specific portion of text to be copied.
### Scenario when this would be used?
a. extract text from column formatted text e.g. newspapers online to be possibly processed with A.I., and/or pasted and collected in various file types
b. extract text or specific parts of text from data-sheet tables other then (or including) spreadsheets, like texted pdf, rtf, web pages, etc.
### Supporting information
A significant number of publications are formatted by columns, from scholar to technical manuals in every sector, patent documents etc.. Many webpages are too.
Mostly, the sole by-row-copy can't help.
"Copy by Column" can be technically a little variant of the function "Copy by Zone". But from the point of view of the user it makes a big difference in use being able to specify by cursor the to be selected column width only, having the entire text down to the end of the page selected and copied without having to scroll down and then up again for the next column selection and so on. | Needs-Triage | low | Minor |
2,557,760,842 | vscode | Contributing a text editor provider raises warning, even when user selects it as 'workbench.editor.defaultBinaryEditor' | <!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
Contributing a 'CustomTextEditorProvider', to be selected by the user as 'workbench.editor.defaultBinaryEditor' still raises the warning of 'File seems to be binary and cannot be opened as text'
<img width="277" alt="Warning" src="https://github.com/user-attachments/assets/129b30d7-dc1d-4b82-a7a6-962545ff52a6">
**Context:**
We are currently developing a VSCode extension, to parse binaries with objdump and provide the information about the binary. We need the output to be presented in a text editor, not a custom editor as we are contributing a new language model for objdump output. So, mainly we need the output syntax coloring, as document symbols to be provided, which is not possible in the custom editor WebView.
We need a way to bypass the warning, as the user selects the provided custom text editor as the default binary editor.
[Related Discussion](https://github.com/microsoft/vscode-discussions/discussions/1532#discussioncomment-10799293) | bug,help wanted,custom-editors | low | Minor |
2,557,823,850 | transformers | T5 is ExecuTorch compatible | ### Feature request
Enable T5 to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow
### Motivation
See details in #32253
### Your contribution
model enablement | Feature request,ExecuTorch | low | Minor |
2,557,828,676 | transformers | Stable Diffusion is ExecuTorch compatible | ### Feature request
Enable Stable Diffusion to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow
### Motivation
See details in #32253
### Your contribution
Stable Diffusion model enablement | Feature request,ExecuTorch | low | Minor |
2,557,831,037 | transformers | Phi3 is ExecuTorch compatible | ### Feature request
Enable Phi3-mini to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow
### Motivation
See details in #32253
### Your contribution
model enablement | Feature request,ExecuTorch | low | Minor |
2,557,831,669 | PowerToys | [Mouse Without Borders] - refactoring "Common" classes | ### Description of the new feature / enhancement
As a precursor to https://github.com/microsoft/PowerToys/issues/34126 (Integrate Mouse Jump with Mouse Without Borders) I've spoken with @crutkas and @ethanfangg about doing some mechanical refactoring to break the large "Common" class into multiple smaller classes as general maintenance / housekeeping work.
Each "Common.*.cs" partial file will be turned into a separate static class so as to reduce the scope of the private members inside them and make it easier / safer to perform other changes (e.g. integration with Mouse Jump) at a later date.
Changes to each "Common.*.cs" file will be submitted as a separate PR.
### Scenario when this would be used?
No change in functionality - this is a refactoring / maintenance change designed to make some future work easier / safer to implement.
### Supporting information
_No response_ | Idea-Enhancement,Status-In progress,Product-Mouse Without Borders | low | Major |
2,557,833,273 | transformers | Mamba is ExecuTorch compatible | ### Feature request
Enable Mamba to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow
### Motivation
See details in #32253
### Your contribution
Mamba model enablement | Feature request,ExecuTorch | low | Minor |
2,557,841,606 | transformers | Whisper is ExecuTorch compatible | ### Feature request
Enable Whisper to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow
### Motivation
See details in #32253
### Your contribution
TBD | Feature request,ExecuTorch | low | Minor |
2,557,844,550 | bitcoin | Docs: "External signer" documentation is outdated. (plz close if unwanted request) | ### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current behaviour
Specification documents some basic command-line options only.
### Expected behaviour
Including missing flags, at least `--account`, `--chain`, `--stdin`. And in case of `--stdin`, all further stdin-commands and corresponding results.
### Steps to reproduce
N/A
### Relevant log output
N/A
### How did you obtain Bitcoin Core
Other
### What version of Bitcoin Core are you using?
master-ref in repo
### Operating system and version
N/A
### Machine specifications
N/A | Docs | low | Minor |
2,557,855,290 | next.js | Dynamic Modal Interception is Greedy | ### Link to the code that reproduces this issue
https://github.com/khuezy/next-modal-bug
### To Reproduce
1. npm install
2. npm run dev
3. Go to localhost:3000/gallery
4. Click on /gallery/dynamic
5. See dynamic route modal interception
6. Go back
7. Click /gallery/static
8. See that the static route is intercepted when it shouldn't
### Current vs. Expected behavior
Modal Interception intercepts static routes as dynamic.
```
/app
/gallery
/[dynamic]
page.tsx
/static
page.tsx
/@modal
/[dynamic]
page.tsx
```
When linking to `/gallery/static`, the modal interceptor intercepts it as `/gallery/[dynamic]`.
Without "@modal", the `/gallery/static` is processed before the `/gallery/[dynamic] `route. But with "@modal" interception, it is intercepting the `/gallery/static` path as `[dynamic]`
So with that, the expectation of "@modal" route interception is the same. "@modal" should not intercept static routes.
### Provide environment information
```bash
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Available memory (MB): 32768
Available CPU cores: 10
Binaries:
Node: 22.6.0
npm: 10.8.2
Yarn: N/A
pnpm: 9.7.0
Relevant Packages:
next: 15.0.0-canary.173 // Latest available version is detected (15.0.0-canary.173).
eslint-config-next: N/A
react: 18.3.1
react-dom: 18.3.1
typescript: 5.6.2
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
Parallel & Intercepting Routes
### Which stage(s) are affected? (Select all that apply)
next dev (local)
### Additional context
_No response_ | bug,Parallel & Intercepting Routes | low | Critical |
2,557,899,314 | pytorch | [export] int(x.item()) fails only in strict=False | ### 🐛 Describe the bug
Here's a case where strict=True succeeds but strict=False fails.
```python
def test_mul_symint(self):
class M(torch.nn.Module):
def forward(self, x):
return int(x.item())
print(torch.export.export(M(), (torch.tensor(2),))
```
With `strict=True`, we get the following graph:
```
ExportedProgram:
class GraphModule(torch.nn.Module):
def forward(self, x: "i64[]", y: "i64[]"):
# File: /data/users/angelayi/pytorch/moo.py:2677 in forward, code: return int(x.item())
item: "Sym(u0)" = torch.ops.aten.item.default(x); x = None
return (item,)
```
However with `strict=False`, this fails with `GuardOnDataDependentSymNode: Could not extract specialized integer from data-dependent expression u0.` which we have encountered before. The workaround is to rewrite it to `x.to(dtype=torch.int32).item()`.
But it seems like dynamo can now handle this code now? Or is it something within dynamic shapes?
### Versions
main
cc @ezyang @chauhang @penguinwu @bobrenjc93 @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @suo @ydwu4 | triaged,oncall: pt2,module: dynamic shapes,export-triaged,oncall: export | low | Critical |
2,557,902,294 | node | stream: `readable.compose` fails to return a Duplex | The intention of `readable.compose()` is that the method returns the Duplex from the internals/streams/compose function unscathed.
Unfortunately, because it's merged onto `Readable.prototype` as a "stream-returning operator":
https://github.com/nodejs/node/blob/8a3482ec5e4cbba5b4ba3f7d6f83c829612f6976/lib/stream.js#L64-L83
...its return value is passed via `Readable.from()`, clobbering the Duplex into a Readable.
The `.compose()` operator needs specifically to bypass this mechanism.
Refs: #44937 | stream | low | Minor |
2,557,909,634 | go | spec: wrong thing taken as a reference for method value rules | ### What is the URL of the page with the issue?
https://go.dev/ref/spec#Method_values
### What is your user agent?
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36
### Screenshot
### What did you do?
I have read the specification and I think the part related to the behavior (evaluation) of method values is not well written. I tried to write an issue quite thoroughly and step-by-step, while extensively quoting the specification and providing examples. For this reason, there is a bit more text. I didn't want the issue to be misinterpreted or for there to be any confusion about what I'm alluding to.
### What did you see happen?
Selector expression is in the spec explained as the way to select the field or the method with identifier `f` of the value `x`.
> For a [primary expression](https://go.dev/ref/spec#Primary_expressions) x that is not a [package name](https://go.dev/ref/spec#Package_clause), the selector expression
> ```
> x.f
>```
> **denotes the field or method f** of the value x (or sometimes *x; see below). The identifier f is called the (field or method) selector; it must not be the [blank identifier](https://go.dev/ref/spec#Blank_identifier). The type of the selector expression is the type of f. If x is a package name, see the section on [qualified identifiers](https://go.dev/ref/spec#Qualified_identifiers).
According to spec, selection is done by traversing the types of the value `x` and its embedded fields and looking for the method or field with identifier `f`.
> **A selector f may denote a field or method f** of a type T, or it may refer to a field or method f of a nested [embedded field](https://go.dev/ref/spec#Struct_types) of T. The number of embedded fields traversed to reach f is called its depth in T. The depth of a field or method f declared in T is zero. The depth of a field or method f declared in an embedded field A in T is the depth of f in A plus one.
Next, the spec specifies some rules for selectors. The most important for what I'm talking about is the first:
> For a value x of type T or *T where T is not a pointer or interface type, **x.f denotes the field or method** at the shallowest depth in T where there is such an f. If there is not exactly [one f](https://go.dev/ref/spec#Uniqueness_of_identifiers) with shallowest depth, the selector expression is illegal.
Thus, it only talks about selecting ("taking") some concrete method or field `f`. Nothing else than that. Selectors just denote method or field (as bolded in all three cites). Any other logic related to the process of evaluation, creating method sets, implicit dereferencing of `x`, implicit taking address of `x` etc. is, according to the spec, out of scope for the selectors.
Consider the following example:
```
type T0 struct {
x int
}
func (*T0) M0() {}
type T1 struct {
x int
T0
}
func (T1) M1() {}
func (*T1) M2() {}
```
Following are all valid selectors for `x1` of type `T1` and `x2` of type `*T1` (I am talking here only about valid selectors according to the previously cited rule for them):
```
x1.M0
x2.M0
x1.M1
x1.M2
x2.M1
x2.M2
x1.x // from T1
x2.x // from T1
```
Further rules are then applied based on the "context" of the selected (obtained with the selector). Thus:
1. if we select field `x` with either `x1.x` or `x2.x`, then the rules related to the evaluation of the expression denoting identifier of the [variable](https://go.dev/ref/spec#Variables) is considered (since fields of the struct are considered as variables according to spec)
> Structured variables of [array](https://go.dev/ref/spec#Array_types), [slice](https://go.dev/ref/spec#Slice_types), and [struct](https://go.dev/ref/spec#Struct_types) types have elements and fields that may be [addressed](https://go.dev/ref/spec#Address_operators) individually. **Each such element acts like a variable.**
2. if we select method with `x1.M1` and call it `x1.M1()`, then the rules related to [calls](https://go.dev/ref/spec#Calls) are applied:
> A method call x.m() is valid if the [method set](https://go.dev/ref/spec#Method_sets) of (the type of) x contains m and the argument list can be assigned to the parameter list of m. If x is [addressable](https://go.dev/ref/spec#Address_operators) and &x's method set contains m, x.m() is shorthand for (&x).m()
- these rules include implicit dereferencing if the method is in the method set, so `x2.M1()` is shorthand for `(*x2).M1()` and implicit address taking if the receiver is addressable, so `x1.M2()` is shorthand for `(&x1).M2()`)
3. based on selectors, promotions and [method sets](https://go.dev/ref/spec#Method_sets) are defined
4. if we select method with `x1.M1`, then we selected method value and the rules related to the evaluation of the [method value](https://go.dev/ref/spec#Method_sets) are applied
5. and so on...
So, selector just selects/denotes field or method and then the corresponding rules are applied based on further context. For example:
```
type T1 struct{}
func (T1) M1() {}
func (*T1) M2() {}
func R() T1 { return T1{} }
func main() {
R().M1()
R().M2() // error
}
```
In this example, both selector expressions `R().M1` and `R().M2` are valid according to the rule for selectors. Further rules apply because of [method call](https://go.dev/ref/spec#Calls) and then `R().M2()` fails to compile since return value of the function is not addressable (implicit `&R()` is not possible; rule 2).
Now, what I found to be incorrect in the specification.
It states the following for the [method values](https://go.dev/ref/spec#Method_values):
> As with [selectors](https://go.dev/ref/spec#Selectors), a reference to a non-interface method with a value receiver using a pointer will automatically dereference that pointer: pt.Mv is equivalent to (*pt).Mv.
>
> As with [method calls](https://go.dev/ref/spec#Calls), a reference to a non-interface method with a pointer receiver using an addressable value will automatically take the address of that value: t.Mp is equivalent to (&t).Mp.
I agree with the second paragraph, but the first one seems incorrect to me. Selector just selects/denotes some method and then dereference is done "as part of other rules" (for example, if it is method call or method value).
Nowhere in the [selectors](https://go.dev/ref/spec#Selectors) section does it state that `pt.Mv is equivalent to (*pt).Mv`, or looking at the first example, that `x2.M1() is equivalent to (*x2).M1()` and that this implicit dereferencing is done. **It only states that `pt.Mv` (`x2.M1`) denotes a method, and that's it.** Moreover, if we follow this logic of implicitness, then for the second rule we could also reference selectors (instead of calls) as `t.Mp being equivalent to (&t).Mp`, or looking at the first example, `x1.M2() being equivalent to (&x1).M2()`. Here, the address is implicitly taken (just as in the first case where we have implicitly dereferencing).
Whether selectors automatically dereference (or take address) is not stated anywhere (and I think it shouldn't be since they just denote method or field), so selectors can't be used as reference here. Both cases are correct by the rules for the selectors!
### What did you expect to see?
At the end:
> For a [primary expression](https://go.dev/ref/spec#Primary_expressions) x that is not a [package name](https://go.dev/ref/spec#Package_clause), the selector expression
> ```
> x.f
> ```
> **denotes the field or method f** of the value x (or sometimes *x; see below).
> A selector f may **denote a field or method f** of a type T, or it may refer to a field or method f of a nested [embedded field](https://go.dev/ref/spec#Struct_types) of T.
Selectors just select/denote field or method, and what will further happen is part of other rules.
In my opinion, issue could be solved by making the first paragraph also reference "calls" rather than selectors.
Additionally, since selector expression `x.f` where `f` is a field and `x` is a pointer type implicitly dereferences `x` first, it should be noted in [selector section](https://go.dev/ref/spec#Selectors). For example, something as this:
- if the selector expression `x.f` denotes/selects field `f` and `x` is of pointer type, dereferencing is automatically done first, and then the selected field is treated as the [variable](https://go.dev/ref/spec#Variables); if the selector expression `x.f` denotes/selects method `f`, see the [method value](https://go.dev/ref/spec#Method_values). | Documentation | low | Critical |
2,557,922,329 | PowerToys | UTF-8 characters incorrectly displayed | ### Microsoft PowerToys version
0.84.1
### Installation method
GitHub, PowerToys auto-update
### Running as admin
No
### Area(s) with issue?
Peek
### Steps to reproduce
Microsoft PowerToys preview handler is not picking UTF-8 correctly in some cases like in the attached file
[Example.txt](https://github.com/user-attachments/files/17197819/Example.txt)
### ✔️ Expected Behavior
to show:
### ❌ Actual Behavior
It shows:
### Other Software
Everything v1.4.1.1026 as described [HERE](https://www.voidtools.com/forum/viewtopic.php?t=15633) | Issue-Bug,Needs-Triage | low | Minor |
2,557,928,701 | ollama | Capability checking does not consider custom templates | ### What is the issue?
When sending a completion request to a model that supports FIM tasks - e.g Qwen 2.5 Coder 7B base - Ollama rejects the request because the "model does not support insert".
Passing `raw` with the necessary prompt format to the model does work for completion, so the issue is not with the model, it is with Ollamas acceptance of the non-raw prompt.
I found the issue is that the Modelfile template does not contain `{{.Suffix}}` since the instruct version of the same model, which does include suffix does work for completions, in raw mode and otherwise.
Passing a custom template in the request to the base mode however does not work. Ollama gives the same "model does not support insert" error.
The server code shows that only the modelfile template is considered for compatability checking.
### OS
macOS
### GPU
Apple
### CPU
Apple
### Ollama version
0.3.12 | bug | low | Critical |
2,557,940,258 | flutter | [Impeller] App stuck on black screen on launch on Android emulator API 30/33. | ### Steps to reproduce
1. Update Android Studio
2. flutter channel master
3. flutter upgrade
4. Create new app (just a new flutter app)
5. Run Android Emulator API 33
6. Run newly created app
### Expected results
Show default Flutter counter app
### Actual results
Black Screen of ruining my business
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
// This is the theme of your application.
//
// TRY THIS: Try running your application with "flutter run". You'll see
// the application has a purple toolbar. Then, without quitting the app,
// try changing the seedColor in the colorScheme below to Colors.green
// and then invoke "hot reload" (save your changes or press the "hot
// reload" button in a Flutter-supported IDE, or press "r" if you used
// the command line to start the app).
//
// Notice that the counter didn't reset back to zero; the application
// state is not lost during the reload. To reset the state, use hot
// restart instead.
//
// This works for code too, not just values: Most code changes can be
// tested with just a hot reload.
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
),
home: const MyHomePage(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
// This widget is the home page of your application. It is stateful, meaning
// that it has a State object (defined below) that contains fields that affect
// how it looks.
// This class is the configuration for the state. It holds the values (in this
// case the title) provided by the parent (in this case the App widget) and
// used by the build method of the State. Fields in a Widget subclass are
// always marked "final".
final String title;
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
int _counter = 0;
void _incrementCounter() {
setState(() {
// This call to setState tells the Flutter framework that something has
// changed in this State, which causes it to rerun the build method below
// so that the display can reflect the updated values. If we changed
// _counter without calling setState(), then the build method would not be
// called again, and so nothing would appear to happen.
_counter++;
});
}
@override
Widget build(BuildContext context) {
// This method is rerun every time setState is called, for instance as done
// by the _incrementCounter method above.
//
// The Flutter framework has been optimized to make rerunning build methods
// fast, so that you can just rebuild anything that needs updating rather
// than having to individually change instances of widgets.
return Scaffold(
appBar: AppBar(
// TRY THIS: Try changing the color here to a specific color (to
// Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
// change color while the other colors stay the same.
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
// Here we take the value from the MyHomePage object that was created by
// the App.build method, and use it to set our appbar title.
title: Text(widget.title),
),
body: Center(
// Center is a layout widget. It takes a single child and positions it
// in the middle of the parent.
child: Column(
// Column is also a layout widget. It takes a list of children and
// arranges them vertically. By default, it sizes itself to fit its
// children horizontally, and tries to be as tall as its parent.
//
// Column has various properties to control how it sizes itself and
// how it positions its children. Here we use mainAxisAlignment to
// center the children vertically; the main axis here is the vertical
// axis because Columns are vertical (the cross axis would be
// horizontal).
//
// TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
// action in the IDE, or press "p" in the console), to see the
// wireframe for each widget.
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
const Text(
'You have pushed the button this many times:',
),
Text(
'$_counter',
style: Theme.of(context).textTheme.headlineMedium,
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: const Icon(Icons.add),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
Launching lib/main.dart on sdk gphone64 x86 64 in debug mode...
Running Gradle task 'assembleDebug'...
Warning: SDK processing. This version only understands SDK XML versions up to 3 but an SDK XML file of version 4 was encountered. This can happen if you use versions of Android Studio and the command-line tools that were released at different times.
Checking the license for package Android SDK Build-Tools 33.0.1 in /home/gandalf/Android/Sdk/licenses
License for package Android SDK Build-Tools 33.0.1 accepted.
Preparing "Install Android SDK Build-Tools 33.0.1 v.33.0.1".
"Install Android SDK Build-Tools 33.0.1 v.33.0.1" ready.
Installing Android SDK Build-Tools 33.0.1 in /home/gandalf/Android/Sdk/build-tools/33.0.1
"Install Android SDK Build-Tools 33.0.1 v.33.0.1" complete.
"Install Android SDK Build-Tools 33.0.1 v.33.0.1" finished.
✓ Built build/app/outputs/flutter-apk/app-debug.apk
Installing build/app/outputs/flutter-apk/app-debug.apk...
I/flutter ( 7132): [IMPORTANT:flutter/shell/platform/android/android_context_vk_impeller.cc(60)] Using the Impeller rendering backend (Vulkan).
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/android/ahb_texture_source_vk.cc(133)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not allocate device memory for external image : ErrorOutOfDeviceMemory
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_texture_pool_vk.cc(69)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create hardware buffer texture source for swapchain image of size: (1080, 2337)
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/android/ahb_texture_source_vk.cc(133)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not allocate device memory for external image : ErrorOutOfDeviceMemory
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_texture_pool_vk.cc(69)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create hardware buffer texture source for swapchain image of size: (1080, 2337)
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/android/ahb_texture_source_vk.cc(133)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not allocate device memory for external image : ErrorOutOfDeviceMemory
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_texture_pool_vk.cc(69)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create hardware buffer texture source for swapchain image of size: (1080, 2337)
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/android/ahb_texture_source_vk.cc(133)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not allocate device memory for external image : ErrorOutOfDeviceMemory
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_texture_pool_vk.cc(69)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create hardware buffer texture source for swapchain image of size: (1080, 2337)
Debug service listening on ws://127.0.0.1:45215/5jb0aIHUbNQ=/ws
Syncing files to device sdk gphone64 x86 64...
I/silia.aaflutter( 7132): Compiler allocated 4533KB to compile void android.view.ViewRootImpl.performTraversals()
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_swapchain_impl_vk.cc(111)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create AHB texture source.
E/flutter ( 7132): [ERROR:flutter/shell/gpu/gpu_surface_vulkan_impeller.cc(58)] No surface available.
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_swapchain_impl_vk.cc(111)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create AHB texture source.
E/flutter ( 7132): [ERROR:flutter/shell/gpu/gpu_surface_vulkan_impeller.cc(58)] No surface available.
W/Parcel ( 7132): Expecting binder but got null!
E/flutter ( 7132): [ERROR:flutter/impeller/renderer/backend/vulkan/swapchain/ahb/ahb_swapchain_impl_vk.cc(111)] Break on 'ImpellerValidationBreak' to inspect point of failure: Could not create AHB texture source.
E/flutter ( 7132): [ERROR:flutter/shell/gpu/gpu_surface_vulkan_impeller.cc(58)] No surface available.
D/ProfileInstaller( 7132): Installing profile for br.com.xxxxxxx.aaflutter
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel master, 3.26.0-1.0.pre.280, on Linux Mint 21.3 6.8.0-45-generic, locale en_US.UTF-8)
• Flutter version 3.26.0-1.0.pre.280 on channel master at /home/gandalf/development/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision e6c955416d (37 minutes ago), 2024-09-30 20:20:08 -0400
• Engine revision bfb6dddb2b
• Dart version 3.6.0 (build 3.6.0-302.0.dev)
• DevTools version 2.40.0-dev.2
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
• Android SDK at /home/gandalf/Android/Sdk
• Platform android-35, build-tools 35.0.0
• ANDROID_HOME = /home/gandalf/Android/Sdk
• Java binary at: /home/gandalf/development/android-studio/jbr/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
• All Android licenses accepted.
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
• Ubuntu clang version 14.0.0-1ubuntu1.1
• cmake version 3.22.1
• ninja version 1.10.1
• pkg-config version 0.29.2
[✓] Android Studio (version 2024.1)
• Android Studio at /home/gandalf/development/android-studio
• Flutter plugin version 81.0.2
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
[✓] VS Code (version 1.93.1)
• VS Code at /var/lib/flatpak/app/com.visualstudio.code/x86_64/stable/active/files/extra/vscode
• Flutter extension version 3.94.0
[✓] Connected device (2 available)
• sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64 • Android 13 (API 33) (emulator)
• Linux (desktop) • linux • linux-x64 • Linux Mint 21.3 6.8.0-45-generic
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.
```
</details>
| c: regression,e: device-specific,platform-android,engine,P2,e: impeller,team-engine,triaged-engine | low | Critical |
2,557,974,233 | godot | Animated CanvasMaterials in Particles2D do not play nicely together with trails. | ### Tested versions
- Reproducible in: 4.3.stable.mono.official [77dcf97d8]
### System information
Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 Ti (NVIDIA; 32.0.15.6109) - Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 Threads)
### Issue description
When enabling trails, while using `CanvasMaterial` animation the entire particle effect will be stretched vertically.
Example Video:
https://github.com/user-attachments/assets/0cae32cb-185c-4e31-96fc-fbe98acdb59f
It's worth mentioning this does not seem to occur when using `AnimatedTexture` which is now deprecated. When using `AnimatedTexture` it acts in a more expected manner.
### Steps to reproduce
1. Enable trails while using CanvasMaterial animation on a particle effect.
### Minimal reproduction project (MRP)
Effect used from here: https://ragnapixel.itch.io/particle-fx
[ParticleMRP.zip](https://github.com/user-attachments/files/17198115/ParticleMRP.zip) | bug,topic:particles | low | Minor |
2,557,980,708 | pytorch | UserWarning: Graph break due to unsupported builtin time.time | ### 🐛 Describe the bug
Not a bug, just a UserWarning which is ignorable. I'm merely doing as instructed in the warning, that is reporting it as an issue here. Searching past issues didn't find this one.
### Error logs
/usr/lib/python3/dist-packages/torch/_dynamo/variables/functions.py:663: UserWarning: Graph break due to unsupported builtin time.time. This function is either a Python builtin (e.g. _warnings.warn) or a third-party C/C++ Python extension (perhaps created with pybind). If it is a Python builtin, please file an issue on GitHub so the PyTorch team can add support for it and see the next case for a workaround. If it is a third-party C/C++ Python extension, please either wrap it into a PyTorch-understood custom operator (see https://pytorch.org/tutorials/advanced/custom_ops_landing_page.html for more details) or, if it is traceable, use torch.compiler.allow_in_graph.
torch._dynamo.utils.warn_once(msg)
### Minified repro
```
import time
import torch
def debug():
start_time = time.time()
debug = torch.compile(debug)
debug()
```
### Versions
Collecting environment information...
PyTorch version: 2.4.0
Is debug build: False
CUDA used to build PyTorch: 12.4
ROCM used to build PyTorch: N/A
OS: Ubuntu 24.04.1 LTS (x86_64)
GCC version: (Ubuntu 13.2.0-23ubuntu4) 13.2.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.39
Python version: 3.12.3 (main, Sep 11 2024, 14:17:37) [GCC 13.2.0] (64-bit runtime)
Python platform: Linux-6.8.0-45-generic-x86_64-with-glibc2.39
Is CUDA available: True
CUDA runtime version: 12.4.131
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4070 Ti
Nvidia driver version: 550.107.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 12
On-line CPU(s) list: 0-11
Vendor ID: GenuineIntel
Model name: Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz
CPU family: 6
Model: 45
Thread(s) per core: 2
Core(s) per socket: 6
Socket(s): 1
Stepping: 7
CPU(s) scaling MHz: 72%
CPU max MHz: 3800.0000
CPU min MHz: 1200.0000
BogoMIPS: 6403.54
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm epb pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid xsaveopt dtherm ida arat pln pts vnmi md_clear flush_l1d
Virtualization: VT-x
L1d cache: 192 KiB (6 instances)
L1i cache: 192 KiB (6 instances)
L2 cache: 1.5 MiB (6 instances)
L3 cache: 12 MiB (1 instance)
NUMA node(s): 1
NUMA node0 CPU(s): 0-11
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: KVM: Mitigation: VMX disabled
Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Mmio stale data: Unknown: No mitigations
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Retpolines; IBPB conditional; IBRS_FW; STIBP conditional; RSB filling; PBRSB-eIBRS Not affected; BHI Not affected
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] optree==0.12.1
[pip3] pytorch-ranger==0.1.1
[pip3] torch==2.4.0
[pip3] torch-optimizer==0.3.0
[pip3] torchvision==0.19.0
[pip3] triton==3.0.0
[conda] Could not collect
cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec | triaged,oncall: pt2,module: dynamo | low | Critical |
2,557,997,278 | TypeScript | `isolatedModules` does not generate the same code | ### 🔎 Search Terms
isolatedModules
const enum
inlining
generated code
### 🕗 Version & Regression Information
- This is the behavior in every version I tried
### ⏯ Playground Link
https://www.typescriptlang.org/play/?preserveConstEnums=true&module=5&isolatedModules=true&ts=5.7.0-dev.20240930#code/FAYw9gdgzgLgBAUwgVwLZwHJhgZTAQQHcEoxUEBhSWAURXQG9g449yA1AQwBtkEAaZnHwRsACwQAnAPIQEwAL7BlAM2QQQMAJaQ4AEzClyMMVogBzABSxOMBAC5M2PERJlK1GHTQBKRwDcwLT04JhYoQi0YEDE4axhbBB9QoRYQTigEJ1wCYiMPaC96ADo2BC5eB1SWOHBoMG4EYu4wKwByMoq+Np8AbmqWACNJBE4Aa36a2oysrBzXfKpC71RikXEpWSqptOoGppb29ZNNuR7JneHRiaElBSA
### 💻 Code
```ts
const enum NotSoAwesomeConstEnum {
SomeValue,
AnotherOne
}
function dosomething(state: NotSoAwesomeConstEnum): void {
switch (state) {
case NotSoAwesomeConstEnum.SomeValue:
console.log('SomeValue');
break;
case NotSoAwesomeConstEnum.AnotherOne:
console.log('AnotherOne');
break;
}
}
```
### 🙁 Actual behavior
The emitted code is not the same when using `isolatedModules`.
### 🙂 Expected behavior
The emitted code should be the same when using `isolatedModules` as it is described as nothing else but a check
> Setting the isolatedModules flag tells TypeScript to warn you if you write certain code that can’t be correctly interpreted by a single-file transpilation process.
const enum values should be inlined even when using this flag. (Or an error should be emitted).
### Additional information about the issue
From the documentation:
> It does not change the behavior of your code, or otherwise change the behavior of TypeScript’s checking and emitting process.
Which is not true, at least for `const enum` as this prevents inlining.
See the playground link and https://github.com/microsoft/TypeScript/issues/16671#issuecomment-1686858424
| Docs | low | Critical |
2,558,015,809 | godot | Tileset Physics Layer Painting doesn't update moved points | ### Tested versions
- v4.3.stable.official [77dcf97d8]
### System information
Windows 7 (6.1.7601) - GLES3 (Compatibility) - GeForce 8600 GTS () - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 Threads)
### Issue description
When editing physics layers collision shapes zoomed, if you move a point the point is not updated on the tile.
Un-zooming the tile and then re-zooming in shows that changes to points placed were not updated.
After reselecting the tile and re-zooming you can edit points and those edits stick.
Images to show the issue:
First the zoomed tile showing the original points placed:
Next: physics layer with points edited:
Notice that the tile image has not updated its points.
Un-zooming (or un-expanding) at this point will lose those changes in points.
When the tile is reselected and re-expanded then the points can be edited and those changes kept.
### Steps to reproduce
1. Select a tile from a tileset. Make sure there exists a physics layer.
2. Select the physics layer and expand the editor.
3. Select original points to make a polygon.
4. Edit/move the original points.
5. Un-expand the editor.
6. Re-expand the editor and you will notice the edits/moves have been lost.
### Minimal reproduction project (MRP)
No MRP.
| bug,topic:editor,topic:2d | low | Critical |
2,558,039,172 | ollama | Support for Zamba2 | Zamba2 is a really cool model that uses a hybrid Mamba-Transformer system.
https://huggingface.co/Zyphra/Zamba2-2.7B
https://www.zyphra.com/post/zamba2-small
I have been wanting to use this for a while and I would love if ollama could add this model soon. | model request | low | Minor |
2,558,039,573 | vscode | Enable notebook serialization in background thread | See https://github.com/microsoft/vscode/pull/226632 & https://github.com/microsoft/vscode/issues/214040#issuecomment-2371815210
```[tasklist]
### Tasks
- [ ] Enable the setting `ipynb.experimental.serialization`
- [x] Worker serialization in web
```
| debt,notebook,notebook-ipynb,notebook-perf | low | Minor |
2,558,058,877 | flutter | Flutter macOS desktop app freezes after switching applications using Mission Control. | ### Steps to reproduce
1. Create a new Flutter project: flutter create bug.
2. Run the application and switch to another app. Then, reopen the Flutter app using Mission Control.
3. Try this multiple times—you will likely encounter the issue within one or two tries. Also, check out the video I’ve provided, where I’ve recreated the issue. Interestingly, when I maximize the app from the bottom icons, it works fine.
### Expected results
App should not freeze if app opens from Mission Control.
### Actual results
App becomes not responding when it opens from mission control.
Same bug reported on windows but i have tested on windows it works fine. #74797
### Code sample
```
import 'package:flutter/material.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
// This is the theme of your application.
//
// TRY THIS: Try running your application with "flutter run". You'll see
// the application has a purple toolbar. Then, without quitting the app,
// try changing the seedColor in the colorScheme below to Colors.green
// and then invoke "hot reload" (save your changes or press the "hot
// reload" button in a Flutter-supported IDE, or press "r" if you used
// the command line to start the app).
//
// Notice that the counter didn't reset back to zero; the application
// state is not lost during the reload. To reset the state, use hot
// restart instead.
//
// This works for code too, not just values: Most code changes can be
// tested with just a hot reload.
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
),
home: const MyHomePage(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
// This widget is the home page of your application. It is stateful, meaning
// that it has a State object (defined below) that contains fields that affect
// how it looks.
// This class is the configuration for the state. It holds the values (in this
// case the title) provided by the parent (in this case the App widget) and
// used by the build method of the State. Fields in a Widget subclass are
// always marked "final".
final String title;
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
int _counter = 0;
void _incrementCounter() {
setState(() {
// This call to setState tells the Flutter framework that something has
// changed in this State, which causes it to rerun the build method below
// so that the display can reflect the updated values. If we changed
// _counter without calling setState(), then the build method would not be
// called again, and so nothing would appear to happen.
_counter++;
});
}
@override
Widget build(BuildContext context) {
// This method is rerun every time setState is called, for instance as done
// by the _incrementCounter method above.
//
// The Flutter framework has been optimized to make rerunning build methods
// fast, so that you can just rebuild anything that needs updating rather
// than having to individually change instances of widgets.
return Scaffold(
appBar: AppBar(
// TRY THIS: Try changing the color here to a specific color (to
// Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
// change color while the other colors stay the same.
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
// Here we take the value from the MyHomePage object that was created by
// the App.build method, and use it to set our appbar title.
title: Text(widget.title),
),
body: Center(
// Center is a layout widget. It takes a single child and positions it
// in the middle of the parent.
child: Column(
// Column is also a layout widget. It takes a list of children and
// arranges them vertically. By default, it sizes itself to fit its
// children horizontally, and tries to be as tall as its parent.
//
// Column has various properties to control how it sizes itself and
// how it positions its children. Here we use mainAxisAlignment to
// center the children vertically; the main axis here is the vertical
// axis because Columns are vertical (the cross axis would be
// horizontal).
//
// TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
// action in the IDE, or press "p" in the console), to see the
// wireframe for each widget.
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
const Text(
'You have pushed the button this many times:',
),
Text(
'$_counter',
style: Theme.of(context).textTheme.headlineMedium,
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: const Icon(Icons.add),
), // This trailing comma makes auto-formatting nicer for build methods.
);
}
}
```
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
https://github.com/user-attachments/assets/078588c9-a8d0-4fc7-99ce-968b01858d43
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
kirshi@Kirshis-MacBook-Pro ~ % flutter doctor -v
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0 24A335 darwin-x64, locale
en-US)
• Flutter version 3.24.3 on channel stable at
/Users/kirshi/Development/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 2663184aa7 (3 weeks ago), 2024-09-11 16:27:48 -0500
• Engine revision 36335019a8
• Dart version 3.5.3
• DevTools version 2.37.3
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/kirshi/Library/Android/sdk
✗ cmdline-tools component is missing
Run `path/to/sdkmanager --install "cmdline-tools;latest"`
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run `flutter doctor --android-licenses` to accept the SDK licenses.
See https://flutter.dev/to/macos-android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16A242d
• CocoaPods version 1.15.2
[✗] Chrome - develop for the web (Cannot find Chrome executable at
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Android Studio (version 2024.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
17.0.11+0-17.0.11b1207.24-11852314)
[✓] VS Code (version 1.93.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.96.0
[✓] Connected device (1 available)
• macOS (desktop) • macos • darwin-x64 • macOS 15.0 24A335 darwin-x64
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 2 categories.
kirshi@Kirshis-MacBook-Pro ~ %
```
</details>
| platform-mac,a: desktop,P2,team-macos,triaged-macos | low | Critical |
2,558,100,797 | godot | Switching fullscreen mode in Godot 4.3 crashes the entire laptop in Fedora 40 | ### Tested versions
- Latest Godot Engine version for Fedora 40 [v4.3.stable.fedora 77dcf97d8]
### System information
Fedora 40
### Issue description
I followed this tutorial or project in youtube, which was working completely fine in Godot 4.2 (https://www.youtube.com/watch?v=dMYv6InQgno&list=PLcZp9zrMgnmOOQXevC-2CfH67QP3mB4wv - Godot 3 Inventory Tutorial | Modular Inventory).
However, in Godot 4.3 it's an absolute mess regarding the fullscreen mode. For no reason, it's always true, the _emit_changed signal executes three times, with two of them using wrong variables, and the worst part is, when launching the game and switching fullscreen mode about 4 times, the entire laptop crashes. At first all my applications got closed, Brave and Godot, except OBS. I tried it a second time and my entire screen froze, went dark, and said "Booting Fedora 40". It's incredible.
Extra: The project is also printing 15 blank lines for no reason. I don't have any print("") or print() anywhere in the code, it makes no sense. I also get errors about animations not named "", which didn't occur in Godot 4.2 and they don't break the game, but they also make no sense, because function play() from AnimatedSprite2D can accept no name as a parameter. It's just a tiny script I use to autoplay AnimatedSprite2Ds once they are ready.
### Steps to reproduce
Open the MRP, execute the game, click on the settings button and switch fullscreen mode a few times until it crashes your entire pc. I have a live stream video of me going through this whole problem from beginning to end (AT HOUR, MINUTE, SECOND 19:21:30 for the first encounter, and the last seconds of the entire stream for the full crash. The whole fullscreen problem begins at minute 18:50:00): https://www.twitch.tv/videos/2264047277
NOTE: I am working on my game, which is using the Modular Inventory as it is, I have not edited a single line in it. The MRP should suffer the same error, I will test it after posting this in case it crashes my computer again.
### Minimal reproduction project (MRP)
[Modular-Inventory-Part-12-main.zip](https://github.com/user-attachments/files/17198967/Modular-Inventory-Part-12-main.zip)
| bug,platform:linuxbsd,needs testing,crash | low | Critical |
2,558,101,190 | deno | ignoreCase option on URLPattern not working | Version: Deno 1.46.3
Considering the following example looks like Deno is not honoring the `ignoreCase` option in URLPattern.
```typescript
let p = new URLPattern({ pathname: '/test' }, { ignoreCase: true })
p.test('/test', 'http://localhost') // returns true on Deno and Chrome
p.test('/TeSt', 'http://localhost') // returns false on Deno and true on Chrome
```
Is this a bug or expected behavior? | bug,web,ext/url | low | Critical |
2,558,299,689 | storybook | Bug: Elements > Modal> Screen fading issue | ### Describe the bug
1)Elements > Modal> Default > Click on DEFAULT Button Open Modal Without close modal click on other any element (ex - Label,Navbar etc) screen is fade or click on Modal Storys Anyone it will be happened.
**I am unable click or do any functionality**
OR
2) Elements >> Modal> having different Storys so any one story open click on button then open modal without close modal out side any element open that time screen is fade
**I can't click or use any other functionality. **
OR
3) Elements >> Modal> having different Storys so any one story open click on button then open modal without close modal open
Other storys (Static Backdrop Modal, Scrollable Content Modal, Modal Vertically Centered) that time screen is fade
**When work:- That worked perfectly when I refreshed Page**
Expectation: - The screen should not fade when you click on other elements or stories.
### Reproduction link
https://stage-react.raaghu.ai/
### Reproduction steps
1)Elements > Modal> Default > Click on DEFAULT Button Open Modal Without close modal click on other any element (ex - Label,Navbar etc) screen is fade or click on Modal Storys Anyone it will be happened.
**I am unable click or do any functionality**
OR
2) Elements >> Modal> having different Storys so any one story open click on button then open modal without close modal out side any element open that time screen is fade
**I can't click or use any other functionality. **
OR
3) Elements >> Modal> having different Storys so any one story open click on button then open modal without close modal open
Other storys (Static Backdrop Modal, Scrollable Content Modal, Modal Vertically Centered) that time screen is fade
**When work:- That worked perfectly when I refreshed Page**
Expectation: - The screen should not fade when you click on other elements or stories.
### System
```bash
Use this command to latest project
npx storybook@latest init
```
### Additional context
_No response_ | bug,good first issue,ui,sev:S3 | low | Critical |
2,558,310,277 | ollama | Logic in the Error Message Detection llm/status.go | ### What is the issue?
The way the error message is being set in the Write method is a bit problematic. Specifically, the bytes.Cut function only finds the first occurrence of the prefix in the slice, and the error message is built only for that specific occurrence. If there are multiple error messages or prefixes, only the last match will be recorded in w.LastErrMsg.
The current logic doesn't break out of the loop once an error prefix is found. Instead, it continues checking, which is unnecessary once an error has already been detected.
**Improvement**: Add a break to stop after the first error match.
### OS
macOS
### GPU
Apple
### CPU
Apple
### Ollama version
3.1 | bug | low | Critical |
2,558,340,740 | pytorch | Missing librt.so.1, libdl.so.2, libz.so.1 and libpthread.so.0 in PyTorch Source Build (aarch64) | ### 🐛 Describe the bug
I am building PyTorch from source on an aarch64 system and have noticed performance differences of Hugging face models(Bert, resnet etc) when running on 64 threads/cores, compared to the pip-installed version (2.4.0). Upon inspecting the shared libraries linked to libtorch_cpu.so, I found that the pip-installed version links to librt.so.1, libdl.so.2, libz.so.1 and libpthread.so.0, but these libraries are missing in the source build.
I used following method to build:
[[builder/aarch64_linux/aarch64_wheel_ci_build.py at main · pytorch/builder · GitHub](https://github.com/pytorch/builder/blob/main/aarch64_linux/aarch64_wheel_ci_build.py)].
Please help me out to build pytorch similar to pip-installed version including all missing libraries.
### Versions
Collecting environment information...
PyTorch version: 2.4.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.5 LTS (aarch64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.0-1ubuntu1.1
CMake version: version 3.22.1
Libc version: glibc-2.35
Python version: 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-6.8.0-1015-aws-aarch64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 64
On-line CPU(s) list: 0-63
Vendor ID: ARM
Model: 1
Thread(s) per core: 1
Core(s) per cluster: 64
Socket(s): -
Cluster(s): 1
Stepping: r1p1
BogoMIPS: 2100.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng
L1d cache: 4 MiB (64 instances)
L1i cache: 4 MiB (64 instances)
L2 cache: 64 MiB (64 instances)
L3 cache: 32 MiB (1 instance)
NUMA node(s): 1
NUMA node0 CPU(s): 0-63
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; __user pointer sanitization
Vulnerability Spectre v2: Mitigation; CSV2, BHB
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Versions of relevant libraries:
[pip3] numpy==2.1.1
[pip3] torch==2.4.0
[pip3] torchvision==0.19.1
[conda] Could not collect
cc @malfet @seemethere @snadampal @milpuz01 | needs reproduction,module: build,triaged,module: arm | low | Critical |
2,558,379,661 | flutter | Flutter detects animations as disabled on Ubuntu (when they're not) | ### Steps to reproduce
1. Install clean Ubuntu 24.04.1 LTS (latest long-term support version)
1. `flutter create` a new application
2. `flutter run` as a Linux app
3. Notice that there are no animations (such as when tapping a button)
4. Add the following lines to `lib/main.dart`'s `main()` function:
```dart
final binding = WidgetsFlutterBinding.ensureInitialized();
debugPrint('disable_animations=${binding.disableAnimations}');
```
5. Run again on Ubuntu and notice it says `disable_animations=true`. Run anywhere else and it says `disable_animations=false`.
6. Check that animations are _not_ disabled in the system:
### Expected results
App runs according to system settings. (Other apps do show animations.)
### Actual results
Flutter app doesn't detect animations as disabled when they're not.
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
void main() {
final binding = WidgetsFlutterBinding.ensureInitialized();
debugPrint('disable_animations=${binding.disableAnimations}');
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
),
home: const MyHomePage(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
final String title;
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
int _counter = 0;
void _incrementCounter() {
setState(() {
_counter++;
});
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
title: Text(widget.title),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
const Text(
'You have pushed the button this many times:',
),
Text(
'$_counter',
style: Theme.of(context).textTheme.headlineMedium,
),
],
),
),
floatingActionButton: FloatingActionButton(
onPressed: _incrementCounter,
tooltip: 'Increment',
child: const Icon(Icons.add),
),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
Sorry, I don't have time to figure out how to record the screen on Ubuntu right now but there's an old, related issue here: https://github.com/flutter/flutter/issues/116511. That one has the video of an animation going too fast on Linux.
That issue was closed because the user was happy with switching animations on with `gdbus call --session --dest org.freedesktop.portal.Desktop --object-path /org/freedesktop/portal/desktop --method org.freedesktop.portal.Settings.Read org.gnome.desktop.interface enable-animations`. But that only solves the issue on their own computer.
I think the issue is that Flutter detects a different `animations_enabled` setting than the rest of Ubuntu apps. Or maybe Ubuntu just disables animations (at some level) by default and most apps choose to ignore it? In any case, the end result is that Flutter apps look like they were on fast forward on Ubuntu.
This might be an issue on other Linux distros than Ubuntu, but Ubuntu being the most popular makes it bad enough even if it's just Ubuntu.
</details>
### Logs
_No response_
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
flutter doctor -v
[✓] Flutter (Channel stable, 3.24.3, on Ubuntu 24.04.1 LTS 6.8.0-45-generic, locale en_US.UTF-8)
• Flutter version 3.24.3 on channel stable at /home/filip/SDKs/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 2663184aa7 (3 weeks ago), 2024-09-11 16:27:48 -0500
• Engine revision 36335019a8
• Dart version 3.5.3
• DevTools version 2.37.3
[✗] Android toolchain - develop for Android devices
✗ Unable to locate Android SDK.
Install Android Studio from: https://developer.android.com/studio/index.html
On first launch it will assist you in installing the Android SDK components.
(or visit https://flutter.dev/to/linux-android-setup for detailed instructions).
If the Android SDK has been installed to a custom location, please use
`flutter config --android-sdk` to update to that location.
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
• Ubuntu clang version 18.1.3 (1ubuntu1)
• cmake version 3.28.3
• ninja version 1.11.1
• pkg-config version 1.8.1
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/to/linux-android-setup for detailed instructions).
[✓] VS Code (version 1.93.1)
• VS Code at /usr/share/code
• Flutter extension version 3.98.0
[✓] Connected device (1 available)
• Linux (desktop) • linux • linux-x64 • Ubuntu 24.04.1 LTS 6.8.0-45-generic
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 3 categories.
```
</details>
| engine,a: animation,platform-linux,P2,team-linux,triaged-linux | low | Critical |
2,558,386,215 | react-native | Using `contentOffset` causes invalid scroll events to fire when ScrollView is first mounted | ### Description
When using the `contentOffset` prop on ScrollView, we've observed that this causes extra scroll events to fire when the component is mounted. Specifically, it sends an event with the `contentOffset` equal to the value passed to the prop, then sends a second one - if the contentOffset is positive, it's the same value again, and if it's negative, it's 0.
We're trying to use a negative `contentOffset.y` value in conjunction with a paddingTop style so that the scrollview content can be offset from the top a certain distance.
Expected behaviour: no scroll events are fired until the scrollview is actually scrolled
It appears to be iOS only, but I have only tried android on the emulator so I can't be completely certain
### Steps to reproduce
1. Create a ScrollView that has an `onScroll` handler that logs `contentOffset`
2. Add a `contentOffset` of `{ x: 0, y: -100 }`
3. Observe the logs look like this:
```
-100
0
```
### React Native Version
0.74.5
### Affected Platforms
Runtime - iOS
### Output of `npx react-native info`
```text
System:
OS: macOS 15.0
CPU: (8) arm64 Apple M1
Memory: 169.59 MB / 16.00 GB
Shell:
version: 3.7.1
path: /opt/homebrew/bin/fish
Binaries:
Node:
version: 22.5.1
path: /opt/homebrew/bin/node
Yarn:
version: 1.22.22
path: ~/.yarn/bin/yarn
npm:
version: 10.2.5
path: /opt/homebrew/bin/npm
Watchman:
version: 2024.07.29.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.15.2
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.0
- iOS 18.0
- macOS 15.0
- tvOS 18.0
- visionOS 2.0
- watchOS 11.0
Android SDK:
API Levels:
- "33"
- "34"
Build Tools:
- 30.0.3
- 33.0.0
- 33.0.1
- 34.0.0
System Images:
- android-34 | Google APIs ARM 64 v8a
- android-35 | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11330709
Xcode:
version: 16.0/16A242d
path: /usr/bin/xcodebuild
Languages:
Java:
version: 11.0.24
path: /opt/homebrew/opt/openjdk@11/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.74.5
wanted: 0.74.5
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
```
### Stacktrace or Logs
```text
n/a
```
### Reproducer
https://snack.expo.dev/@mozzius/contentoffset-causing-incorrect-scroll-events-repro
### Screenshots and Videos
<img src="https://github.com/user-attachments/assets/a725fc95-a82c-449a-b8d7-44720a533e74" width="200">
| Component: ScrollView,Needs: Triage :mag: | low | Minor |
2,558,393,428 | godot | GPUParticle3D stops rendering in editor under specific circumstances | EDIT: more information as to how to properly reproduce this bug have been discovered, and as such updating the reproduction steps.
### Tested versions
4.4.dev
### System information
Godot v4.4.dev (76a135926) - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon RX 6650 XT (Advanced Micro Devices, Inc.; 31.0.24033.1003) - AMD Ryzen 7 3800X 8-Core Processor (16 threads)
### Issue description
When the Fixed FPS is set to 0 for a GPUParticle3D, the material assigned to it's mesh has billboarding with the keep scale flag enabled, and lastly the ParticleProcessMaterial's Display->Scale setting is set to use a curve which starts with a value of 0, new particles are no longer emitted. Changing between nodes will briefly cause a burst of particles. New particles also seem to spawn while the editor is minimized or briefly whenever a tooltip on any GUI component appears.
Is related to #97621 as the default for a CPUParticle3D's Fixed FPS is 0, so on swapping to a GPUParticle3D, and having a mesh material that has scaled billboarding enabled, the already emitted particles will render as normal but no new particles will be added to the system, which may briefly appear as if the wrong amount of particles are being generated.
### Steps to reproduce
As described above:
- Make a GPUParticle3D node.
- set a quadmesh and create a material for it
- have that material be set to use any of the billboarding options
- enable the keep scale flag.
- In the ParticleProcessMaterial, set the Display scale field to use a curve
- Make the initial value for that scale curve 0
### Minimal reproduction project (MRP)
I have been using the same MRP as was submitted on #97621, which I will include here again.
[New.Compressed.zipped.Folder.zip](https://github.com/user-attachments/files/17201033/New.Compressed.zipped.Folder.zip)
| bug,needs testing,topic:particles | low | Critical |
2,558,395,599 | rust | Box sometimes forgets to drop its allocator when the Box is conditionally initialized. | I tried this code:
```rust
#![feature(allocator_api)]
use std::alloc::{Allocator, AllocError, Layout, Global};
use std::ptr::NonNull;
struct LoudDropAllocator;
unsafe impl Allocator for LoudDropAllocator {
fn allocate(&self, layout: Layout) -> Result<NonNull<[u8]>, AllocError> {
Global.allocate(layout)
}
unsafe fn deallocate(&self, ptr: NonNull<u8>, layout: Layout) {
Global.deallocate(ptr, layout);
}
}
impl Drop for LoudDropAllocator {
fn drop(&mut self) {
println!("dropping allocator...");
}
}
struct HasDrop;
impl Drop for HasDrop {
fn drop(&mut self) {}
}
fn foo() {
println!("foo()");
let b = Box::new_in(HasDrop, LoudDropAllocator);
if true {
drop(*b);
} else {
drop(b);
}
}
fn bar() {
println!("bar()");
let b = Box::new_in(HasDrop, LoudDropAllocator);
if true {
drop(*b);
} else {
// drop(b);
}
}
fn main() {
foo();
bar();
}
```
I expected the program to output:
```
foo()
dropping allocator...
bar()
dropping allocator...
```
Instead it output:
```
foo()
bar()
dropping allocator...
```
Seems like there's something wrong with the drop flags.
Making `HasDrop` not implement `Drop` causes the program to behave as expected.
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
Reproducible on the playground with version `1.83.0-nightly (2024-09-30 fb4aebddd18d258046dd)`
<!-- TRIAGEBOT_START -->
<!-- TRIAGEBOT_ASSIGN_START -->
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"beepster4096"}$$TRIAGEBOT_ASSIGN_DATA_END -->
<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END --> | A-allocators,T-compiler,A-MIR,C-bug,A-box | low | Critical |
2,558,442,723 | ui | [feat]: Update Vaul to the latest release | ### Feature description
Vaul has lots of improvements and bug fixes since version 0.9.0. It would be better to upgrade it to the latest version.
### Affected component/components
Drawer
### Additional Context
_No response_
### Before submitting
- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs | area: request | low | Critical |
2,558,473,763 | material-ui | `useColorScheme` should fail when not called under a `ThemeProvider` | ### Steps to reproduce
Link to live example: https://codesandbox.io/embed/8clfj3?module=/src/Demo.tsx
Try toggling the theme with the two selects
### Current behavior
The first one select box doesn't do anything. There is no feedback to the developer that the first call to `useColorScheme` will never work.
### Expected behavior
The call to `useColorScheme` errors when there is no theme available.
### Context
Potentially what this [user](https://github.com/mui/toolpad/issues/4151#issuecomment-2382839160) ran in to.
Orthogonal issue, but I started from [this example](https://mui.com/material-ui/customization/dark-mode/#toggling-color-mode). It would be more ergonomic if these were radio buttons, or toggle buttons. It halves the amount of clicks necessary to operate the demo.
### Your environment
<details>
<summary><code>npx @mui/envinfo</code></summary>
```
Don't forget to mention which browser you used.
Output from `npx @mui/envinfo` goes here.
```
</details>
**Search keywords**: useColorScheme ThemeProvider | customization: theme | low | Critical |
2,558,572,291 | rust | `&&self` suggestion from compiler | ### Code
```rust
struct SomeStruct;
impl SomeStruct {
fn some_fn(&some_name) {
self
}
}
fn main() {}
```
### Current output
```
error[E0424]: expected value, found module `self`
--> src/main.rs:5:9
|
4 | fn some_fn(&some_name) {
| ------- this function doesn't have a `self` parameter
5 | self
| ^^^^ `self` value is a keyword only available in methods with a `self` parameter
|
help: add a `self` receiver parameter to make the associated `fn` a method
|
4 | fn some_fn(&&self, some_name) {
| ++++++
For more information about this error, try `rustc --explain E0424`.
```
### Desired output
```
error[E0424]: expected value, found module `self`
--> src/main.rs:5:9
|
4 | fn some_fn(&some_name) {
| ------- this function doesn't have a `self` parameter
5 | self
| ^^^^ `self` value is a keyword only available in methods with a `self` parameter
|
help: add a `self` receiver parameter to make the associated `fn` a method
|
4 | fn some_fn(self, &some_name) {
| +++++
For more information about this error, try `rustc --explain E0424`.
```
### Rationale and extra context
Maybe the user forgot to add the `self` parameter in the code. Or maybe they forgot to rename `some_name` to `self` while refactoring the code. Either way, for beginners, the compiler suggesting to use `&&self` instead of `self` or `&self` may be confusing.
### Rust Version
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: aarch64-apple-darwin
release: 1.81.0
LLVM version: 18.1.7 | A-diagnostics,T-compiler | low | Critical |
2,558,589,957 | material-ui | [TextField] aria-live="polite" should be added to input errors | ### Summary
When an input is in the error state and has an helper text there should be an aria-live="polite" attribute so screenreader users will be notified correctly.
### Examples
_No response_
### Motivation
Make the web more accessible
**Search keywords**: aria-live | accessibility,component: text field,platform: windows | low | Critical |
2,558,615,777 | tauri | [bug] `tauri_plugin::Builder` directly modifies the source directory for the plugin that's being built | ### Describe the bug
`tauri_plugin::Builder` [directly modifies the source code of the plugin that's being built to add the permissions autogenerated files](https://github.com/tauri-apps/tauri/blob/60a5aea53db02ae6af325812ab97555f2c013d70/crates/tauri-plugin/src/build/mod.rs#L107). This is actually a bad practice as per https://doc.rust-lang.org/cargo/reference/build-script-examples.html#code-generation:
```
In general, build scripts should not modify any files outside of OUT_DIR. It may seem fine on the first blush, but it does cause problems when you use such crate as a dependency, because there’s an implicit invariant that sources in .cargo/registry should be immutable. cargo won’t allow such scripts when packaging.
```
As a result, building a tauri plugin crate in special environments that protect the source code of crates against writes like nix becomes quite challenging. The build fails with errors of the type:
```
> Checking holochain_metrics v0.3.2
> error: failed to run custom build command for `tauri-plugin-log v2.0.0-rc.2`
>
> Caused by:
> process didn't exit successfully: `/private/tmp/nix-build-hc-pilot-deps-0.1.0.drv-0/tauri-workspace/target/release/build/tauri-plugin-log-4a5a88853b912538/build-script-build` (exit status: 1)
> --- stdout
> cargo:rerun-if-changed=permissions
> cargo:PERMISSION_FILES_PATH=/private/tmp/nix-build-hc-pilot-deps-0.1.0.drv-0/tauri-workspace/target/release/build/tauri-plugin-log-6053c8040f31d660/out/tauri-plugin-log-permission-files
> tauri-plugin: failed to write file: Permission denied (os error 13)
> warning: build failed, waiting for other jobs to finish...
```
Maybe it is enough to just check in all those files in git? Not sure...
### Reproduction
_No response_
### Expected behavior
Plugin crates can be built on a source code protected environment.
### Full `tauri info` output
```text
guillemcordoba@Guillems-Mini end-user-happ % npm run tauri info
> tauri-app@0.0.0 tauri
> tauri info
[✔] Environment
- OS: Mac OS 14.6.1 arm64 (X64)
✔ Xcode Command Line Tools: installed
✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: 1.81-aarch64-apple-darwin (default)
- node: 20.9.0
- pnpm: 9.5.0
- yarn: 1.22.21
- npm: 10.1.0
[-] Packages
- tauri 🦀: 2.0.0-rc.11
- tauri-build 🦀: 2.0.0-rc.10
- wry 🦀: 0.43.1
- tao 🦀: 0.30.0
- tauri-cli 🦀: 2.0.0-rc.16
- @tauri-apps/api : 2.0.0-rc.4
- @tauri-apps/cli : 2.0.0-rc.15
[-] Plugins
- tauri-plugin-log 🦀: 2.0.0-rc.2
- @tauri-apps/plugin-log : not installed!
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../ui/dist
- devUrl: http://localhost:1420/
- framework: Svelte
- bundler: Vite
[-] iOS
- Developer Teams: Guillem Cordoba (ID: 4XN3VLHC68)
```
### Stack trace
_No response_
### Additional context
_No response_ | type: bug,status: needs triage | low | Critical |
2,558,627,517 | deno | Error importing interface in Node project | Version: Deno 2.0.0-rc.9
```
error: Uncaught SyntaxError: The requested module '../../interfaces' does not provide an export named 'IFile'
import { IFile } from '../../interfaces';
```
tried to migrate project from node to deno. Barrel files are not working if they export only types and interfaces.
**Update**
it is not connected to Barrel file, it doesn't work without index.ts
<img width="984" alt="image" src="https://github.com/user-attachments/assets/a41594c1-f9ca-47dd-b7bb-b017b446e92b">
| question | low | Critical |
2,558,641,982 | kubernetes | Listing doesn't fail if a resource of the returned set permafails to transform | ### What happened?
If data transformation suddenly starts failing on a resource from a set that is returned by a List() query, the user is not notified of these failures, but is presented with the latest known version of the resource. That happens even after new, properly readable resources get added and appear in the returned set.
Get() fails correctly on the failing resource.
### What did you expect to happen?
I expected `List()` to notify me about issues reading a resource.
### How can we reproduce it (as minimally and precisely as possible)?
1. run the API server with etcd encryption turned on
2. rewrite your EncryptionConfiguration by replacing the key in the encryption provider
3. wait for the changes to take effect - `Get()` a resource that was previously encrypted until the `Get()` fails with an internal error
4. issue a `List()` request that contains the resource that was previously failing on `Get()`
Alternatively, you can apply the patch from the attachment that adds an integration test and
[0001-list-broken-proof.txt](https://github.com/user-attachments/files/17202520/0001-list-broken-proof.txt)
```
make test-integration WHAT=./test/integration/controlplane/transformation GOFLAGS="-v" KUBE_TEST_ARGS='-run ^TestBrokenTransformations$'
```
### Anything else we need to know?
I wonder if it would be possible to allow `.patch` attachments so that patches don't have to be sent as .txt files.
### Kubernetes version
master
### Cloud provider
irrelevant
### OS version
_No response_
### Install tools
<details>
</details>
### Container runtime (CRI) and version (if applicable)
<details>
</details>
### Related plugins (CNI, CSI, ...) and versions (if applicable)
<details>
</details>
| kind/bug,sig/api-machinery,triage/accepted | low | Critical |
2,558,673,626 | deno | uWebsocket with BYONM does not load native lib on Windows | So how do i get uWebsocket insalled on deno 2.0.0-rc.8 - If at all possible
I do not have any deno experience, just want to try it because nodeJS runs into strange GC issues under high load for that project.
Running `deno install` provides this message
```ps
deno install
error: Error in hyper-express@6.17.2 parsing version requirement for dependency "uWebSockets.js": "github:uNetworking/uWebSockets.js#v20.48.0"
Caused by:
Package specified a dependency outside of npm (github:uNetworking/uWebSockets.js#v20.48.0). Deno does not install these for security reasons. The npm package should be improved to have all its dependencies on npm.
To work around this, you can use a package.json and install the dependencies via `npm install`.
```
But using npm install will install the build for nodeJs.
Resulting in the crash:
```
error: Uncaught (in promise) Error: This version of uWS.js supports only Node.js LTS versions 16, 18 and 20 on (glibc) Linux, macOS and Windows, on Tier 1 platforms (https://github.com/nodejs/node/blob/master/BUILDING.md#platform-list).
TypeError: LoadLibraryExW failed
at file:///C:/Users/.../node_modules/uWebSockets.js/uws.js:22:9
at Object.<anonymous> (file:///C:/Users/.../node_modules/uWebSockets.js/uws.js:24:3)
at Object.<anonymous> (file:///C:/Users/.../node_modules/uWebSockets.js/uws.js:26:4)
at Module._compile (node:module:748:34)
at Object.Module._extensions..js (node:module:767:10)
at Module.load (node:module:665:32)
at Function.Module._load (node:module:537:12)
at Module.require (node:module:684:19)
at require (node:module:808:16)
at Object.<anonymous> (file:///C:/Users/.../node_modules/hyper-express/index.js:4:21)
```
_Originally posted by @BolverBlitz in https://github.com/denoland/deno/issues/25648#issuecomment-2384894168_
| bug,node compat,node native extension | low | Critical |
2,558,691,931 | godot | Self modulate doesnt works on canvas group with enabled y sort | ### Tested versions
reprodusible in godot 4.3 stable
### System information
Windows 10, godot v4.3.stable.official [77dcf97d8]
### Issue description
I have a canvas group that has a child sprite. The canvas has a modified self modulate parameter, which causes the sprite’s color to change. However, when I turn on the y sort on canvas, the sprite no longer changes color.
### Steps to reproduce
1. Create a canvas_group node
2. Add Sprite2D node to it
3. Change self_modulate property on canvas_group (you can see, that sprite2D changed his color)
4. Set y_sort property on canvas_group to True (As a result Sprite2D stop changing his color)
### Minimal reproduction project (MRP)
[YSortProblem.zip](https://github.com/user-attachments/files/17202774/YSortProblem.zip)
| bug,topic:2d | low | Minor |
2,558,708,911 | pytorch | Discrepancy between torch.nn.functional.linear and manual computation with bias under torch.autocast | ### 🐛 Describe the bug
When using torch.autocast with `dtype=torch.float16`, I observed a discrepancy between the outputs of `torch.nn.functional.linear(x, weight, bias)` and the manual computation `(x @ weight.T + bias)`.
```python
batch_size, dim = 32, 2048
device = 'cuda' if torch.cuda.is_available() else 'cpu'
x = torch.rand(batch_size, dim, device=device)
weight = torch.rand(dim, dim, device=device)
bias = torch.rand(dim, device=device)
with torch.autocast(device_type=device, dtype=torch.float16):
linear = torch.nn.functional.linear(x, weight, bias)
manual = (x @ weight.T + bias)
print((linear - manual).abs().max().item()) # 0.505126953125
```
This difference increases linearly with respect to `dim`
[Code to Reproduce the figure](https://gist.github.com/TheoBoyer/714a3355632afa92ae57c4ad2c2e6c9c)
Notably, when removing the bias, both methods produce identical results.
```python
batch_size, dim = 32, 2048
device = 'cuda' if torch.cuda.is_available() else 'cpu'
x = torch.rand(batch_size, dim, device=device)
weight = torch.rand(dim, dim, device=device)
with torch.autocast(device_type=device, dtype=torch.float16):
linear = torch.nn.functional.linear(x, weight)
manual = (x @ weight.T)
print((linear - manual).abs().max().item()) # 0.0
```
### Versions
PyTorch version: 2.4.1+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.0-1ubuntu1.1
CMake version: version 3.30.3
Libc version: glibc-2.35
Python version: 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-6.1.85+-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.2.140
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: Tesla T4
Nvidia driver version: 535.104.05
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.6
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.6
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 46 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) CPU @ 2.20GHz
CPU family: 6
Model: 79
Thread(s) per core: 2
Core(s) per socket: 1
Socket(s): 1
Stepping: 0
BogoMIPS: 4399.99
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch invpcid_single ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap xsaveopt arat md_clear arch_capabilities
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32 KiB (1 instance)
L1i cache: 32 KiB (1 instance)
L2 cache: 256 KiB (1 instance)
L3 cache: 55 MiB (1 instance)
NUMA node(s): 1
NUMA node0 CPU(s): 0,1
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Mitigation; PTE Inversion
Vulnerability Mds: Vulnerable; SMT Host state unknown
Vulnerability Meltdown: Vulnerable
Vulnerability Mmio stale data: Vulnerable
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed: Vulnerable
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers
Vulnerability Spectre v2: Vulnerable; IBPB: disabled; STIBP: disabled; PBRSB-eIBRS: Not affected; BHI: Vulnerable (Syscall hardening enabled)
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Vulnerable
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] optree==0.12.1
[pip3] torch==2.4.1+cu121
[pip3] torchaudio==2.4.1+cu121
[pip3] torchsummary==1.5.1
[pip3] torchvision==0.19.1+cu121
[conda] Could not collect
cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @ptrblck @msaroufim @mcarilli @leslie-fang-intel @jgong5 | module: numerical-stability,module: nn,module: cuda,triaged,module: amp (automated mixed precision) | low | Critical |
2,558,736,855 | deno | `deno test`: show failure output immediately instead of at the very end of test run | When working on a test suite with long running tests it's a bit annoying having to wait until the very end of a test run to see errors, stack traces and more. This means you can't even abort a test run with `CTRL+C`, because then you get no test summary and no information about failures.
<img width="926" alt="Screenshot 2024-10-01 at 11 48 16" src="https://github.com/user-attachments/assets/b1c6ecd2-1685-47b3-9e74-a2598d846f05">
Instead, we should always bring failing test output when a test failed. | suggestion,testing | low | Critical |
2,558,741,716 | PowerToys | smart change language | ### Description of the new feature / enhancement
when you select a sentence you will have the option to change the whole sentences language
### Scenario when this would be used?
when you are write a code for like an hour and when you look at the screen you see you wrote the whole thing in the wrong language .
when you text your friend from the US in English and then you text your other friend from Russia and forgot to change language
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,558,758,981 | next.js | static sites load to slow and extra network request being made when going to that route again | ### Link to the code that reproduces this issue
https://github.com/MariuzM/test__next/tree/main
### To Reproduce
When you click first time on next route it will load fast/instant. but when you click it again it loads abit slowly and also extra network request being made.
### Current vs. Expected behavior
If I'm building static site i don’t need extra network request being made to server, but why is next doing this on 2nd time click?
All this is being deployed on railway.app
### Provide environment information
```bash
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
Available memory (MB): 65536
Available CPU cores: 10
Binaries:
Node: 20.17.0
npm: 10.8.2
Yarn: N/A
pnpm: N/A
Relevant Packages:
next: 15.0.0-rc.0 // Latest available version is detected (15.0.0-rc.0).
eslint-config-next: 15.0.0-rc.0
react: 19.0.0-rc-fb9a90fa48-20240614
react-dom: 19.0.0-rc-fb9a90fa48-20240614
typescript: 5.6.2
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
Performance
### Which stage(s) are affected? (Select all that apply)
Other (Deployed)
### Additional context
_No response_ | bug,Performance | low | Major |
2,558,766,003 | vscode | Wrapped terminal placeholder message looks off | Might be personal preference but when the terminal placeholder message gets wrapped it just looks off to me:
1) second line does not look horizontally aligned with the first
2) I think it would actually be better if we simply do not wrap (but use overflow:elipses rendering style)
I know we also wrap in editor. But I question if that is a good pattern.
| polish,under-discussion,terminal-rendering | low | Minor |
2,558,846,626 | pytorch | `torch._dynamo.config.cache_size_limit` behaviour with DDP | ### 🐛 Describe the bug
When passing from single GPU to multiple GPUs DDP the default `cache_size_limit` is saturated quite quickly as the default 8 limit it is going to be shared against N allocated GPU recompiles.
Is there a way to automatically set a better/safe default for the DDP without requesting the user to manipulate this internal API?
### Versions
nightly
cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @ezyang @chauhang @penguinwu | oncall: distributed,triaged,module: ddp,oncall: pt2,pt2d-triage-nov2024 | low | Critical |
2,558,889,507 | godot | Opening project in editor fails with "Parse Error: Busy." | ### Tested versions
- Reproducible in: v4.3.stable.official [77dcf97d8]
### System information
Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - integrated Intel(R) UHD Graphics (Intel Corporation; 31.0.101.4887) - 13th Gen Intel(R) Core(TM) i5-1345U (12 Threads)
### Issue description
The first time a project is opened in an editor (or after the .godot directory is removed), importing the scenes/scripts fails with:
```
ERROR: Parse Error: Busy. [Resource file res://thing.tscn:6]
at: _parse_node_tag (scene/resources/resource_format_text.cpp:289)
ERROR: Failed loading resource: res://thing.tscn. Make sure resources have been imported by opening the project in the editor at least once.
at: _load (core/io/resource_loader.cpp:283)
```
Closing and opening the same project a second time fixes the issue. The issue appears again if `.godot` directory is removed.
### Steps to reproduce
* Download and unzip the attached sample project.
* Make sure the project is not open in the Godot editor.
* `rm -rf .godot`
* `godot --editor --verbose --headless --import --quit`
* (Or open the project in the editor.)
* Observe the mentioned error in the output.
### Minimal reproduction project (MRP)
[repro2.zip](https://github.com/user-attachments/files/17203878/repro2.zip)
| bug,topic:core,needs testing | low | Critical |
2,558,937,526 | rust | `./x test src/tools/cargo` triggers ~90 test failures on native Windows msvc | Based on a fresh checkout 07f08ffb2db, not caused by #131060 (as the same failures occur also happen with #131060 reverted, just found out accidentally running the cargo tool tests on msvc natively).
Running `./x test src/tools/cargo` on native Windows `x86_64-pc-windows-msvc` with VS 2022, standard development environment (no unusual `PATH` modifications like putting VS 2022 tools; test ran under standard PowerShell; **not** inside MSYS2) leads to ~90 cargo test failures, seemingly have to do with path differences and not finding `link.exe`. [^1]
I presume this is due to some kind of bootstrap difference, because I imagine these all pass for cargo CI. Unless all of our Windows CIs (rust-lang/rust or rust-lang/cargo) all use MSYS2 environments. I have not tried to dig into this.
```
failures:
cargo_add::add_basic::case
cargo_add::add_multiple::case
cargo_add::add_normalized_name_external::case
cargo_add::add_toolchain::case
cargo_add::build::case
cargo_add::cyclic_features::case
cargo_add::default_features::case
cargo_add::dev::case
cargo_add::dev_build_conflict::case
cargo_add::dry_run::case
cargo_add::empty_dep_name::case
cargo_add::features::case
cargo_add::features_empty::case
cargo_add::features_multiple_occurrences::case
cargo_add::features_spaced_values::case
cargo_add::features_unknown::case
cargo_add::features_unknown_no_features::case
cargo_add::git::case
cargo_add::git_branch::case
cargo_add::git_dev::case
cargo_add::git_inferred_name::case
cargo_add::git_conflicts_namever::case
cargo_add::git_inferred_name_multiple::case
cargo_add::git_multiple_packages_features::case
cargo_add::git_normalized_name::case
cargo_add::git_rev::case
cargo_add::git_tag::case
cargo_add::infer_prerelease::case
cargo_add::git_multiple_names::case
cargo_add::invalid_git_name::case
cargo_add::invalid_arg::case
cargo_add::invalid_name_external::case
cargo_add::invalid_path::case
cargo_add::invalid_path_self::case
cargo_add::invalid_target_empty::case
cargo_add::invalid_vers::case
cargo_add::list_features::case
cargo_add::locked_changed::case
cargo_add::multiple_conflicts_with_features::case
cargo_add::no_args::case
cargo_add::no_optional::case
cargo_add::multiple_conflicts_with_rename::case
cargo_add::optional::case
cargo_add::no_default_features::case
cargo_add::namever::case
cargo_add::offline_empty_cache::case
cargo_add::quiet::case
cargo_add::rename::case
cargo_add::target::case
cargo_add::target_cfg::case
cargo_add::vers::case
cargo_info::not_found::case
cargo_info::specify_version_within_ws_and_conflict_with_lockfile::case
cargo_info::specify_version_within_ws_and_match_with_lockfile::case
cargo_info::with_frozen_within_ws::case
cargo_info::with_locked_within_ws::case
cargo_info::within_ws::case
cargo_info::within_ws_with_alternative_registry::case
cargo_init::auto_git::case
cargo_init::explicit_bin_with_git::case
cargo_init::simple_bin::case
cargo_init::simple_git::case
cargo_init::simple_lib::case
cargo_new::inherit_workspace_package_table::case
cargo_new::inherit_workspace_package_table_with_edition::case
cargo_new::inherit_workspace_package_table_with_registry::case
cargo_remove::avoid_empty_tables::case
cargo_remove::build::case
cargo_remove::dev::case
cargo_remove::dry_run::case
cargo_remove::invalid_arg::case
cargo_remove::invalid_dep::case
cargo_remove::invalid_package::case
cargo_remove::invalid_section::case
cargo_remove::invalid_package_multiple::case
cargo_remove::invalid_section_dep::case
cargo_remove::invalid_target::case
cargo_remove::multiple_deps::case
cargo_remove::multiple_dev::case
cargo_remove::no_arg::case
cargo_remove::invalid_target_dep::case
cargo_remove::offline::case
cargo_remove::optional_dep_feature::case
cargo_remove::optional_feature::case
cargo_remove::remove_basic::case
cargo_remove::package::case
cargo_remove::target::case
cargo_remove::target_build::case
cargo_remove::target_dev::case
freshness::lld_is_fresh
test result: FAILED. 3194 passed; 90 failed; 191 ignored; 0 measured; 0 filtered out; finished in 472.08s
```
<details>
<summary>Test failures</summary>
```
failures:
---- cargo_add::add_basic::case stdout ----
thread 'cargo_add::add_basic::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\add_basic\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t582\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::add_multiple::case stdout ----
thread 'cargo_add::add_multiple::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\add_multiple\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t583\\case\\: The system cannot find the path specified.
(os error 3)", backtrace: None }
---- cargo_add::add_normalized_name_external::case stdout ----
thread 'cargo_add::add_normalized_name_external::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\add_normalized_name_external\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t586\\case\\: The system cannot find the
path specified. (os error 3)", backtrace: None }
---- cargo_add::add_toolchain::case stdout ----
thread 'cargo_add::add_toolchain::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\add_toolchain\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t587\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::build::case stdout ----
thread 'cargo_add::build::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\build\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t589\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::cyclic_features::case stdout ----
thread 'cargo_add::cyclic_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\cyclic_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t592\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::default_features::case stdout ----
thread 'cargo_add::default_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\default_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t593\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::dev::case stdout ----
thread 'cargo_add::dev::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\dev\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t602\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::dev_build_conflict::case stdout ----
thread 'cargo_add::dev_build_conflict::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\dev_build_conflict\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t603\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::dry_run::case stdout ----
thread 'cargo_add::dry_run::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\dry_run\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t606\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::empty_dep_name::case stdout ----
thread 'cargo_add::empty_dep_name::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\empty_dep_name\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t607\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::features::case stdout ----
thread 'cargo_add::features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\features\\in to
E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t608\\case\\: The system cannot find the path specified. (os
error 3)", backtrace: None }
---- cargo_add::features_empty::case stdout ----
thread 'cargo_add::features_empty::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\features_empty\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t611\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::features_multiple_occurrences::case stdout ----
thread 'cargo_add::features_multiple_occurrences::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\features_multiple_occurrences\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t613\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::features_spaced_values::case stdout ----
thread 'cargo_add::features_spaced_values::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\features_spaced_values\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t615\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::features_unknown::case stdout ----
thread 'cargo_add::features_unknown::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\features_unknown\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t616\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::features_unknown_no_features::case stdout ----
thread 'cargo_add::features_unknown_no_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\features_unknown_no_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t617\\case\\: The system cannot find the
path specified. (os error 3)", backtrace: None }
---- cargo_add::git::case stdout ----
thread 'cargo_add::git::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t618\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_branch::case stdout ----
thread 'cargo_add::git_branch::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_branch\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t619\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_dev::case stdout ----
thread 'cargo_add::git_dev::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_dev\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t621\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_inferred_name::case stdout ----
thread 'cargo_add::git_inferred_name::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_inferred_name\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t622\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_conflicts_namever::case stdout ----
thread 'cargo_add::git_conflicts_namever::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_conflicts_namever\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t620\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_inferred_name_multiple::case stdout ----
thread 'cargo_add::git_inferred_name_multiple::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_inferred_name_multiple\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t623\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_multiple_packages_features::case stdout ----
thread 'cargo_add::git_multiple_packages_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_multiple_packages_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t625\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_normalized_name::case stdout ----
thread 'cargo_add::git_normalized_name::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_normalized_name\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t626\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_rev::case stdout ----
thread 'cargo_add::git_rev::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_rev\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t628\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_tag::case stdout ----
thread 'cargo_add::git_tag::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_tag\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t629\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::infer_prerelease::case stdout ----
thread 'cargo_add::infer_prerelease::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\infer_prerelease\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t631\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::git_multiple_names::case stdout ----
thread 'cargo_add::git_multiple_names::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\git_multiple_names\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t624\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::invalid_git_name::case stdout ----
thread 'cargo_add::invalid_git_name::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_git_name\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t633\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::invalid_arg::case stdout ----
thread 'cargo_add::invalid_arg::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_arg\\in
to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t632\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::invalid_name_external::case stdout ----
thread 'cargo_add::invalid_name_external::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_name_external\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t638\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::invalid_path::case stdout ----
thread 'cargo_add::invalid_path::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_path\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t639\\case\\: The system cannot find the path specified.
(os error 3)", backtrace: None }
---- cargo_add::invalid_path_self::case stdout ----
thread 'cargo_add::invalid_path_self::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_path_self\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t641\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::invalid_target_empty::case stdout ----
thread 'cargo_add::invalid_target_empty::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_target_empty\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t642\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::invalid_vers::case stdout ----
thread 'cargo_add::invalid_vers::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\invalid_vers\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t643\\case\\: The system cannot find the path specified.
(os error 3)", backtrace: None }
---- cargo_add::list_features::case stdout ----
thread 'cargo_add::list_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\list_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t644\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::locked_changed::case stdout ----
thread 'cargo_add::locked_changed::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\locked_changed\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t647\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::multiple_conflicts_with_features::case stdout ----
thread 'cargo_add::multiple_conflicts_with_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\multiple_conflicts_with_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t652\\case\\: The system cannot find
the path specified. (os error 3)", backtrace: None }
---- cargo_add::no_args::case stdout ----
thread 'cargo_add::no_args::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\no_args\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t655\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::no_optional::case stdout ----
thread 'cargo_add::no_optional::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\no_optional\\in
to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t657\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::multiple_conflicts_with_rename::case stdout ----
thread 'cargo_add::multiple_conflicts_with_rename::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\multiple_conflicts_with_rename\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t653\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::optional::case stdout ----
thread 'cargo_add::optional::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\optional\\in to
E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t660\\case\\: The system cannot find the path specified. (os
error 3)", backtrace: None }
---- cargo_add::no_default_features::case stdout ----
thread 'cargo_add::no_default_features::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\no_default_features\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t656\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::namever::case stdout ----
thread 'cargo_add::namever::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\namever\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t654\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::offline_empty_cache::case stdout ----
thread 'cargo_add::offline_empty_cache::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\offline_empty_cache\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t659\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::quiet::case stdout ----
thread 'cargo_add::quiet::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\quiet\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t710\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::rename::case stdout ----
thread 'cargo_add::rename::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\rename\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t712\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::target::case stdout ----
thread 'cargo_add::target::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\target\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t723\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::target_cfg::case stdout ----
thread 'cargo_add::target_cfg::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\target_cfg\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t724\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_add::vers::case stdout ----
thread 'cargo_add::vers::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_add\\vers\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t726\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_info::not_found::case stdout ----
thread 'cargo_info::not_found::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\not_found\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t816\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_info::specify_version_within_ws_and_conflict_with_lockfile::case stdout ----
thread 'cargo_info::specify_version_within_ws_and_conflict_with_lockfile::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\specify_version_within_ws_and_conflict_with_lockfile\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t824\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_info::specify_version_within_ws_and_match_with_lockfile::case stdout ----
thread 'cargo_info::specify_version_within_ws_and_match_with_lockfile::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\specify_version_within_ws_and_match_with_lockfile\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t825\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
error: test failed, to rerun pass `--test testsuite`
---- cargo_info::with_frozen_within_ws::case stdout ----
thread 'cargo_info::with_frozen_within_ws::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\with_frozen_within_ws\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t829\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_info::with_locked_within_ws::case stdout ----
thread 'cargo_info::with_locked_within_ws::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\with_locked_within_ws\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t831\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_info::within_ws::case stdout ----
thread 'cargo_info::within_ws::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\within_ws\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t835\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_info::within_ws_with_alternative_registry::case stdout ----
thread 'cargo_info::within_ws_with_alternative_registry::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_info\\within_ws_with_alternative_registry\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t837\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_init::auto_git::case stdout ----
thread 'cargo_init::auto_git::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_init\\auto_git\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t840\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_init::explicit_bin_with_git::case stdout ----
thread 'cargo_init::explicit_bin_with_git::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_init\\explicit_bin_with_git\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t853\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_init::simple_bin::case stdout ----
thread 'cargo_init::simple_bin::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_init\\simple_bin\\in
to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t870\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_init::simple_git::case stdout ----
thread 'cargo_init::simple_git::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_init\\simple_git\\in
to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t871\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_init::simple_lib::case stdout ----
thread 'cargo_init::simple_lib::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_init\\simple_lib\\in
to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t874\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_new::inherit_workspace_package_table::case stdout ----
thread 'cargo_new::inherit_workspace_package_table::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_new\\inherit_workspace_package_table\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t895\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_new::inherit_workspace_package_table_with_edition::case stdout ----
thread 'cargo_new::inherit_workspace_package_table_with_edition::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_new\\inherit_workspace_package_table_with_edition\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t896\\case\\: The system
cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_new::inherit_workspace_package_table_with_registry::case stdout ----
thread 'cargo_new::inherit_workspace_package_table_with_registry::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_new\\inherit_workspace_package_table_with_registry\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t897\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::avoid_empty_tables::case stdout ----
thread 'cargo_remove::avoid_empty_tables::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\avoid_empty_tables\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t905\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::build::case stdout ----
thread 'cargo_remove::build::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\build\\in to
E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t906\\case\\: The system cannot find the path specified. (os
error 3)", backtrace: None }
---- cargo_remove::dev::case stdout ----
thread 'cargo_remove::dev::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\dev\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t907\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::dry_run::case stdout ----
thread 'cargo_remove::dry_run::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\dry_run\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t908\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_arg::case stdout ----
thread 'cargo_remove::invalid_arg::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_arg\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t914\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_dep::case stdout ----
thread 'cargo_remove::invalid_dep::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_dep\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t915\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_package::case stdout ----
thread 'cargo_remove::invalid_package::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_package\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t916\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_section::case stdout ----
thread 'cargo_remove::invalid_section::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_section\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t918\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_package_multiple::case stdout ----
thread 'cargo_remove::invalid_package_multiple::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_package_multiple\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t917\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_section_dep::case stdout ----
thread 'cargo_remove::invalid_section_dep::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_section_dep\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t919\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_target::case stdout ----
thread 'cargo_remove::invalid_target::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_target\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t920\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::multiple_deps::case stdout ----
thread 'cargo_remove::multiple_deps::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\multiple_deps\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t922\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::multiple_dev::case stdout ----
thread 'cargo_remove::multiple_dev::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\multiple_dev\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t923\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::no_arg::case stdout ----
thread 'cargo_remove::no_arg::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\no_arg\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t924\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::invalid_target_dep::case stdout ----
thread 'cargo_remove::invalid_target_dep::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\invalid_target_dep\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t921\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::offline::case stdout ----
thread 'cargo_remove::offline::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\offline\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t925\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::optional_dep_feature::case stdout ----
thread 'cargo_remove::optional_dep_feature::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\optional_dep_feature\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t926\\case\\: The system cannot find the path
specified. (os error 3)", backtrace: None }
---- cargo_remove::optional_feature::case stdout ----
thread 'cargo_remove::optional_feature::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\optional_feature\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t928\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::remove_basic::case stdout ----
thread 'cargo_remove::remove_basic::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\remove_basic\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t930\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::package::case stdout ----
thread 'cargo_remove::package::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\package\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t929\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::target::case stdout ----
thread 'cargo_remove::target::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\target\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t932\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::target_build::case stdout ----
thread 'cargo_remove::target_build::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\target_build\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t933\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- cargo_remove::target_dev::case stdout ----
thread 'cargo_remove::target_dev::case' panicked at E:\Repos\rust\src\tools\cargo\crates\cargo-test-support\src\lib.rs:377:76:
called `Result::unwrap()` on an `Err` value: Error { inner: "Failed to copy E:\\Repos\\rust\\src\\tools\\cargo\\tests\\testsuite\\cargo_remove\\target_dev\\in to E:\\Repos\\rust\\build\\x86_64-pc-windows-msvc\\stage1-tools\\x86_64-pc-windows-msvc\\tmp\\cit\\t934\\case\\: The system cannot find the path specified. (os error 3)", backtrace: None }
---- freshness::lld_is_fresh stdout ----
running `E:\Repos\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\release\cargo.exe build`
thread 'freshness::lld_is_fresh' panicked at tests\testsuite\freshness.rs:2786:22:
test failed running `E:\Repos\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\release\cargo.exe build`
error: process exited with code 101 (expected 0)
--- stdout
--- stderr
Compiling foo v0.1.0 (E:\Repos\rust\build\x86_64-pc-windows-msvc\stage1-tools\x86_64-pc-windows-msvc\tmp\cit\t1507\foo)
error: linker `rust-lld` not found
|
= note: program not found
note: the msvc targets depend on the msvc linker but `link.exe` was not found
note: please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option.
note: VS Code is a different product, and is not sufficient.
error: could not compile `foo` (lib) due to 1 previous error
failures:
cargo_add::add_basic::case
cargo_add::add_multiple::case
cargo_add::add_normalized_name_external::case
cargo_add::add_toolchain::case
cargo_add::build::case
cargo_add::cyclic_features::case
cargo_add::default_features::case
cargo_add::dev::case
cargo_add::dev_build_conflict::case
cargo_add::dry_run::case
cargo_add::empty_dep_name::case
cargo_add::features::case
cargo_add::features_empty::case
cargo_add::features_multiple_occurrences::case
cargo_add::features_spaced_values::case
cargo_add::features_unknown::case
cargo_add::features_unknown_no_features::case
cargo_add::git::case
cargo_add::git_branch::case
cargo_add::git_dev::case
cargo_add::git_inferred_name::case
cargo_add::git_conflicts_namever::case
cargo_add::git_inferred_name_multiple::case
cargo_add::git_multiple_packages_features::case
cargo_add::git_normalized_name::case
cargo_add::git_rev::case
cargo_add::git_tag::case
cargo_add::infer_prerelease::case
cargo_add::git_multiple_names::case
cargo_add::invalid_git_name::case
cargo_add::invalid_arg::case
cargo_add::invalid_name_external::case
cargo_add::invalid_path::case
cargo_add::invalid_path_self::case
cargo_add::invalid_target_empty::case
cargo_add::invalid_vers::case
cargo_add::list_features::case
cargo_add::locked_changed::case
cargo_add::multiple_conflicts_with_features::case
cargo_add::no_args::case
cargo_add::no_optional::case
cargo_add::multiple_conflicts_with_rename::case
cargo_add::optional::case
cargo_add::no_default_features::case
cargo_add::namever::case
cargo_add::offline_empty_cache::case
cargo_add::quiet::case
cargo_add::rename::case
cargo_add::target::case
cargo_add::target_cfg::case
cargo_add::vers::case
cargo_info::not_found::case
cargo_info::specify_version_within_ws_and_conflict_with_lockfile::case
cargo_info::specify_version_within_ws_and_match_with_lockfile::case
cargo_info::with_frozen_within_ws::case
cargo_info::with_locked_within_ws::case
cargo_info::within_ws::case
cargo_info::within_ws_with_alternative_registry::case
cargo_init::auto_git::case
cargo_init::explicit_bin_with_git::case
cargo_init::simple_bin::case
cargo_init::simple_git::case
cargo_init::simple_lib::case
cargo_new::inherit_workspace_package_table::case
cargo_new::inherit_workspace_package_table_with_edition::case
cargo_new::inherit_workspace_package_table_with_registry::case
cargo_remove::avoid_empty_tables::case
cargo_remove::build::case
cargo_remove::dev::case
cargo_remove::dry_run::case
cargo_remove::invalid_arg::case
cargo_remove::invalid_dep::case
cargo_remove::invalid_package::case
cargo_remove::invalid_section::case
cargo_remove::invalid_package_multiple::case
cargo_remove::invalid_section_dep::case
cargo_remove::invalid_target::case
cargo_remove::multiple_deps::case
cargo_remove::multiple_dev::case
cargo_remove::no_arg::case
cargo_remove::invalid_target_dep::case
cargo_remove::offline::case
cargo_remove::optional_dep_feature::case
cargo_remove::optional_feature::case
cargo_remove::remove_basic::case
cargo_remove::package::case
cargo_remove::target::case
cargo_remove::target_build::case
cargo_remove::target_dev::case
freshness::lld_is_fresh
test result: FAILED. 3194 passed; 90 failed; 191 ignored; 0 measured; 0 filtered out; finished in 472.08s
```
</details>
[^1]: Note that I can run compiletest-managed test suites just fine (outside of debuginfo due to debugger shenanigans) modulo remaining run-make tests that use `Makefile`s. | A-testsuite,O-windows-msvc,T-bootstrap,T-cargo,C-bug | low | Critical |
2,559,002,414 | rust | Tracking Issue for default-visibility | This is a tracking issue for `default-visibility`, which allows setting the visibility of symbols when building a shared object / dylib.
MCP: https://github.com/rust-lang/compiler-team/issues/782
### About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.
### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->
- [ ] Implement the flag as `-Z default-visibility`
- [ ] Stabilize as `-C default-visibility`
### Unresolved Questions
- [ ] Are we happy with the naming of the flag and its options?
- [ ] What should the default be?
### Implementation history
* https://github.com/rust-lang/rust/pull/130005 | C-tracking-issue | low | Critical |
2,559,037,975 | flutter | Routing unencodes encoded hashes in the URL, producing in an incorrect URL | ### Steps to reproduce
I'm trying to track down a bug in DevTools where values on the querystring get lost. It happens when a value is a hex colour (`#ffffff`) that contains a hash. The hash is correctly encoded initially, but Flutter seems to update the URL with an unencoded version in a way that results in `window.location.href` being incorrect (because the string after the hash is treated as a client-side fragement and not part of the querystring value).
While it might be better if DevTools could avoid reading `window.location` directly, this feels like incorrect behaviour (for example trying to bookmark the URL or similar would use an incorrect URL).
To reproduce:
- Navigate to an app that has an encoded hash in a querystring value (for example `http://localhost:49774/home?a=ccc%23ddd`)
- Print the value of `window.location.href` (or check it in the browser address bar) as the app is loading before routing is initialized
- Print the value of `window.location.href` (or check it in the browser address bar) after the app has loaded/routing has initialized
### Expected results
The value of `window.location.href` should not change to unescape the hash. This changes the meaning of the URL:
```
/home?a=b%23c // This means "a" has the value of "b#c"
/home?a=b#c // This means "a" has the value of "b" and there is a client-side fragment "#c"
```
### Actual results
The hash in the URL is unescaped, resulting in a different (incorrect) URL. Bookmarking this, or reading the value with `window.location.href` will produce invalid results.
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'dart:html';
import 'dart:async';
import 'dart:collection';
import 'package:flutter_web_plugins/url_strategy.dart';
import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';
void main() {
usePathUrlStrategy();
runApp(const MainApp());
}
final routerDelegate = MyRouterDelegate();
final routeInfromationParser = MyRouteInformationParser();
class MainApp extends StatelessWidget {
const MainApp({super.key});
void printCurrentUrlInfo() {
print('The current window.location.href is ${window.location.href}');
var paramValue = Uri.parse(window.location.href).queryParameters['a'];
print('The current query parameter "a" is ${paramValue}');
}
@override
Widget build(BuildContext context) {
printCurrentUrlInfo();
Future.delayed(const Duration(seconds: 1))
.then((_) => printCurrentUrlInfo());
return MaterialApp.router(
builder: (context, child) => child!,
routerDelegate: routerDelegate,
routeInformationParser: routeInfromationParser,
);
}
}
class MyRouteConfiguration {
MyRouteConfiguration(this.page, this.params);
final String page;
final Map<String, String?> params;
}
class MyRouteInformationParser
extends RouteInformationParser<MyRouteConfiguration> {
@override
Future<MyRouteConfiguration> parseRouteInformation(
RouteInformation routeInformation,
) async {
var uri = routeInformation.uri;
// Paths start with /
final page = uri.path.isNotEmpty ? uri.path.substring(1) : '';
final configuration = MyRouteConfiguration(page, uri.queryParameters);
return SynchronousFuture<MyRouteConfiguration>(configuration);
}
@override
RouteInformation restoreRouteInformation(
MyRouteConfiguration configuration,
) {
return RouteInformation(
uri: Uri(
// Paths must always start with /
path: '/${configuration.page}',
queryParameters: configuration.params,
));
}
}
class MyRouterDelegate extends RouterDelegate<MyRouteConfiguration>
with ChangeNotifier, PopNavigatorRouterDelegateMixin<MyRouteConfiguration> {
MyRouterDelegate() : navigatorKey = GlobalKey<NavigatorState>();
static MyRouterDelegate of(BuildContext context) =>
Router.of(context).routerDelegate as MyRouterDelegate;
@override
final GlobalKey<NavigatorState> navigatorKey;
final _routes = ListQueue<MyRouteConfiguration>();
@override
MyRouteConfiguration? get currentConfiguration => _routes.lastOrNull;
@override
Widget build(BuildContext context) {
final uri1 = Uri(path: '/home', queryParameters: {'a': 'bbb'});
final uri2 = Uri(path: '/home', queryParameters: {'a': 'ccc#ddd'});
return Navigator(
key: navigatorKey,
pages: [
MaterialPage(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: [
Text('Open DevTools console!'),
for (var uri in [uri1, uri2])
TextButton(
onPressed: () => window.location.href = uri.toString(),
child: Text('Load page as $uri'),
),
],
),
),
],
onDidRemovePage: (_) {
if (_routes.length <= 1) return;
_routes.removeLast();
notifyListeners();
},
);
}
@override
Future<void> setNewRoutePath(MyRouteConfiguration configuration) async {
_routes
..clear()
..add(configuration);
notifyListeners();
return SynchronousFuture<void>(null);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
https://github.com/user-attachments/assets/2268bd45-361c-4736-b5f0-a742b31f4e5e
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[!] Flutter (Channel master, 3.26.0-1.0.pre.232, on Microsoft Windows [Version 10.0.22631.4169], locale en-GB)
• Flutter version 3.26.0-1.0.pre.232 on channel master at D:\Dev\Google\Flutter\Flutter main
! Warning: `dart` on your path resolves to D:\Tools\Dart\Stable\bin\dart.exe, which is not inside your current Flutter SDK checkout at
D:\Dev\Google\Flutter\Flutter main. Consider adding D:\Dev\Google\Flutter\Flutter main\bin to the front of your path.
• Upstream repository git@github.com:DanTup/flutter.git
• FLUTTER_GIT_URL = git@github.com:DanTup/flutter.git
• Framework revision f7b363929d (5 days ago), 2024-09-26 08:04:29 -0400
• Engine revision 6328a0597b
• Dart version 3.6.0 (build 3.6.0-279.0.dev)
• DevTools version 2.40.0-dev.1
• If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and
upgrades.
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0-rc3)
• Android SDK at C:\Users\danny\AppData\Local\Android\sdk
• Platform android-35, build-tools 35.0.0-rc3
• Java binary at: C:\Program Files\Android\Android Studio\jbr\bin\java
• Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[✓] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.10.5)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.10.35122.118
• Windows 10 SDK version 10.0.22621.0
[✓] Android Studio (version 2023.2)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.9+0--11185874)
[✓] VS Code (version 1.93.1)
• VS Code at C:\Users\danny\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.99.20240930
[✓] VS Code (version 1.93.0-insider)
• VS Code at C:\Users\danny\AppData\Local\Programs\Microsoft VS Code Insiders
• Flutter extension version 3.95.20240801
[✓] Connected device (3 available)
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.22631.4169]
• Chrome (web) • chrome • web-javascript • Google Chrome 129.0.6668.70
• Edge (web) • edge • web-javascript • Microsoft Edge 127.0.2651.86
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.
```
</details>
| framework,f: routes,has reproducible steps,P2,team-framework,triaged-framework,found in release: 3.24,found in release: 3.26 | low | Critical |
2,559,107,309 | bitcoin | Having qt(@6) breaks build for qt@5 on macOS 15.0 and 13.7 | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
Building bitcoin-qt produces a flood of errors:
```
In file included from /Users/sjors/dev/bitcoin/src/qt/csvmodelwriter.cpp:5:
In file included from /Users/sjors/dev/bitcoin/src/qt/csvmodelwriter.h:8:
In file included from /usr/local/opt/qt@5/lib/QtCore.framework/Headers/QList:1:
In file included from /usr/local/opt/qt@5/lib/QtCore.framework/Headers/qlist.h:48:
/usr/local/include/QtCore/qvector.h:20:32: error: no template named 'QMutableListIterator'
20 | using QMutableVectorIterator = QMutableListIterator<T>;
| ^
/usr/local/include/QtCore/qvector.h:22:25: error: no template named 'QListIterator'
22 | using QVectorIterator = QListIterator<T>;
| ^
```
Building with `depends` works fine (qt 5.15.14).
Homebrew is still at version 5.15.13. I don't know if 5.15.14 fixes something, or if there's another reason why depends works but homebrew doesn't. There's currently no open PR to bump homebrew's version, an earlier attempt was abandoned: https://github.com/Homebrew/homebrew-core/pull/172934
I'm not sure when this started happening. E.g. the commit 338bc2cd261ba3daf7fb494f8cb4a534762e292c which introduced cmake has the same issue.
I though perhaps it's a change in macOS itself. But I also tried on macOS 13.7 Ventura, with Xcode 15.2 which gives me similar errors.
Another possibility could be recent homebrew qt change: https://github.com/Homebrew/homebrew-core/commits/master/Formula/q/qt%405.rb
### Expected behaviour
To build `bitcoin-qt`.
### Steps to reproduce
Install qt@5 via homebrew, 5.15.13 is the latest version.
```
cmake -B build -DBUILD_GUI=ON
```
### Relevant log output
_No response_
### How did you obtain Bitcoin Core
Compiled from source
### What version of Bitcoin Core are you using?
master@fc642c33ef28829eda0119a0fe39fd9bc4b84051
### Operating system and version
macOS 15.0
### Machine specifications
_No response_ | macOS,Build system | low | Critical |
2,559,191,861 | ollama | GPU Tesla at 100% and ollama don't work, is hung | ### What is the issue?
I have just set up my Debian 12 Linux server. I installed Ollama directly using the following command:
curl -fsSL https://ollama.com/install.sh | sh
I did not make any modifications to the service file. I ran the command:
ollama run phi3.5
I typed "hello". The response was good and correct. However, for my second question, it started writing the beginning of a sentence and then displayed "###" (see screenshot).
I ran the nvidia-smi command (see screenshot), and the processor stays at 100%, and Ollama stops responding.
I should mention that my server does not have a graphical interface, and the Nvidia and CUDA drivers are up to date (update, upgrade). I am providing the top command output for CPU and RAM information.
Thank you for your feedback.
### OS
Linux
### GPU
Nvidia
### CPU
Intel
### Ollama version
0.3.12 | bug,nvidia,needs more info | low | Minor |
2,559,255,432 | vscode | Markdown should not split up words in backticks that end in `/` when wrapping | Can we handle this edge case so that folders in backticks prefer not breaking the word?
| markdown,polish,editor-wrapping | low | Minor |
2,559,307,841 | vscode | Walkthrough initial state on 100% display and new user data dir has a tiny scroll bar | 
Reducing this padding before the steps would help this go away:
| polish,getting-started | low | Minor |
2,559,318,163 | vscode | Terminal search highlights update really slowly | * open terminal
* search for transpile
* type `npm run gulp transpile-client-swc`
* insert/remove spaces before "transpile"
* 🐌 the search highlight is very, very slow to update
https://github.com/user-attachments/assets/762c6b19-0821-46c7-ad63-5b97203fedfe
| bug,polish,terminal-find | low | Major |
2,559,318,554 | next.js | `optimizePackageImports` is not working with `react-icons` in dev mode | ### Link to the code that reproduces this issue
https://github.com/FilipiBrabo/nextjs-react-icons
### To Reproduce
1. Start the application with analyze-bundle enabled `ANALYZE=true npm run dev`
2. Go to `localhost:3000` the bundle files should open in your browser
### Current vs. Expected behavior
The current behavior is that all icons from a `react-icon` pack are being included in the final bundle in dev mode.
From the [optimizePackageImports docs](https://nextjs.org/docs/app/api-reference/next-config-js/optimizePackageImports) I expected that `react-icons/*` would be tree shaken both in dev and in prod build.
I've also included a `lucide` icon to see the difference, and noticed that `optimizePackageImports` is working as expected.
These are the bundles generated in dev mode of the application provided. You can see that all `fa`, `bs` and `ai` icons are being included in the final dev bundle.
Client bundle:
Node.js bundle:
### Provide environment information
```bash
Operating System:
Platform: linux
Arch: x64
Version: #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024
Available memory (MB): 32012
Available CPU cores: 16
Binaries:
Node: 18.20.4
npm: 10.7.0
Yarn: N/A
pnpm: 8.15.8
Relevant Packages:
next: 15.0.0-canary.174 // Latest available version is detected (15.0.0-canary.174).
eslint-config-next: N/A
react: 19.0.0-rc-2d16326d-20240930
react-dom: 19.0.0-rc-2d16326d-20240930
typescript: 5.3.3
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
Developer Experience, Performance
### Which stage(s) are affected? (Select all that apply)
next dev (local)
### Additional context
I didn't dig too much deep into this, but these were the things that I've tried:
1. Use `modularizeImports` to replace `react-icons` with `@react-icons/all-files`. You can check it out in the `next.config.js` file.
```js
{
reactStrictMode: true,
modularizeImports: {
"react-icons/fa": {
transform: "@react-icons/all-files/fa/{{ member }}",
},
"react-icons/bs": {
transform: "@react-icons/all-files/bs/{{ member }}",
},
"react-icons/ai": {
transform: "@react-icons/all-files/ai/{{ member }}",
},
},
}
```
2. Specify `react-icons` lib in `optimizePackageImports` config
```js
{
reactStrictMode: true,
experimental: {
optimizePackageImports: [
"react-icons/fa",
"react-icons/bs",
"react-icons/ai",
],
// or
optimizePackageImports: ["react-icons"],
},
}
```
This really affects DX if you have too many icons from different packs being imported.
I'm happy to help in any way to fix this issue, just need a little guidance :sweat_smile: | bug,Performance,linear: next | low | Major |
2,559,348,996 | pytorch | conv2d boundaries | ### 🚀 The feature, motivation and pitch
[torch.nn.functional.conv2d](https://pytorch.org/docs/stable/generated/torch.nn.functional.conv2d.html) (and respective [torch.nn.Conv2d](https://pytorch.org/docs/stable/generated/torch.nn.Conv2d.html)) miss `boundaries` which is implemented on scipy [convolve2d](https://docs.scipy.org/doc/scipy/reference/generated/scipy.signal.convolve2d.html).
Any plans to implement this feature?
cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki | module: nn,triaged,enhancement | low | Minor |
2,559,377,228 | storybook | [Bug]: Storybook and `next-dynamic` not resolving suspense | ### Describe the bug
Creating this issue on behalf of GoodRx. They provided a repro [here](https://github.com/dmytrobondarchukGoodRx/storybook-dynamic), including the steps to reproduce below from their readme for quick reference.
### Reproduction link
https://github.com/dmytrobondarchukGoodRx/storybook-dynamic
### Reproduction steps
## Steps to reproduce
1. Clone the repo
2. Run `yarn`
3. Run `yarn storybook`
or `yarn build-storybook && npx http-server ./storybook-static`
4. Open the provided storybook url and open **NextJs dynamic issue** story folder
There are four stories here:
One is using the default `CheckUserSession` component (**Not dynamic** story) and others use the `next-dynamic` wrapper of that component called `CheckUserSessionDynamic`:
1. **Dynamic** - parent and child components use `fetch` to get data
2. **Dynamic Child Non Async** - child components don't make async calls (mock data)
3. **Dynamic All Aon Async** - child and parent components don't make async calls (mock data)
During each story open the _Network_ tab in browser tools
You will get two behaviors:
### Not dynamic behavior
The page will show one main spinner from the _Story_'s suspense and then shortly a lot of spinners for each post after resolving `/posts` route and will execute each HTTP request once and will show the content in a few seconds
### Dynamic behavior
The page will show only the main spinner from _Story_'s suspense and will keep spaming HTTP calls to `/posts` route from the `<Posts />` component (except **Dynamic All Aon Async** story)
The same behavior was confirmed on prod environment with infinite calls to HTTP endpoint (which was added to check if re-render _(?)_ was happening)
### System
```bash
"@chromatic-com/storybook": "^1.6.1",
"@storybook/addon-essentials": "^8.2.9",
"@storybook/addon-interactions": "^8.2.9",
"@storybook/addon-links": "^8.2.9",
"@storybook/addon-onboarding": "^8.2.9",
"@storybook/addon-styling-webpack": "^1.0.0",
"@storybook/blocks": "^8.2.9",
"@storybook/nextjs": "^8.2.9",
"@storybook/react": "^8.2.9",
"@storybook/test": "^8.2.9",
"storybook": "^8.2.9",
```
### Additional context
_No response_ | bug,help wanted,nextjs | low | Critical |
2,559,384,211 | ollama | Support setting `num_ctx` in openai api via extra query parameter | Hi thanks for the package! It would be great if num_ctx can be set in openai api. It seems openai api allows extra query parameter, and other packages like vllm can make use of it to support custom args. | feature request,api | low | Major |
2,559,395,184 | PowerToys | "Run" component uses already existing Windows keybind, also, searchbar lacks "PowerToys Run" branding of any kind | ### Microsoft PowerToys version
0.84.1
### Installation method
GitHub
### Running as admin
No
### Area(s) with issue?
PowerToys Run
### Steps to reproduce
enable Run component, then switch to any Windows program that is not maximized, press LAlt+Spacebar.
### ✔️ Expected Behavior
The current window's menu should open, so that only "X" must be pressed next to maximize the window without using the mouse (or touchpad) at all.
### ❌ Actual Behavior
Some search bar opened in center of screen, not even having the branding "_PowerToys Run_" anywhere around that new search-bar, making it very hard for new users for even finding out that PowerToys is causing that issue.
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,559,426,904 | pytorch | Select parameters and buffers by pattern (using fnmatch or re) | ### 🚀 The feature, motivation and pitch
I'm working on serializing training configuration, and one sticking point is the definition of the parameter groups in the optimizer. Everything except the parameters are easily serializable.
A simple feature to fix this would be to add a `pattern` option to `_named_members`,` parameters`, `named_parameters`, `buffers`, `named_buffers` in nn.Module.
The standard python libraries [fnmatch](https://docs.python.org/3/library/fnmatch.html) or [re](https://docs.python.org/3/library/re.html) provide simple and familiar ways to create those patterns.
It can be done in a single or couple lines in `_named_members` (see additional context).
All the other functions (` parameters`, `named_parameters`, `buffers`, `named_buffers`) directly depend on `_named_members` .
I'm making this Feature Request before a Pull Request because I'm not familiar with how proposal are managed for pytorch. I can make a Pull Request if this is a good idea.
Example of use:
Using the examples on doc https://pytorch.org/docs/stable/optim.html
The following code is not easily serializable:
```python
optim.SGD([
{'params': model.base.parameters(), 'lr': 1e-2},
{'params': model.classifier.parameters()}
], lr=1e-3, momentum=0.9)
```
But with a pattern (using fnmatch) it is:
```python
optim.SGD([
{'params': model.parameters(pattern="base.*"), 'lr': 1e-2},
{'params': model.parameters(pattern="classifier.*")}
], lr=1e-3, momentum=0.9)
```
And an example of configuration file could be:
```yaml
optimizers:
- class: SGD
params:
- pattern: "base.*"
lr: 1e-2
- pattern: "classifier.*"
lr: 1e-3
momentum: 0.9
```
More complex pattern might not be possible with fnmatch:
```python
bias_params = [p for name, p in self.named_parameters() if 'bias' in name]
others = [p for name, p in self.named_parameters() if 'bias' not in name]
optim.SGD([
{'params': others},
{'params': bias_params, 'weight_decay': 0}
], weight_decay=1e-2, lr=1e-2)
```
But with but is possible with re
```python
optim.SGD([
{'params': model.parameters(pattern=".*(?<!\.bias)")},
{'params': model.parameters(pattern=".*\.bias"), 'weight_decay': 0}
], weight_decay=1e-2, lr=1e-2)
```
With a configuration:
```yaml
optimizers:
- class: SGD
params:
- pattern: '.*(?<!\.bias)'
- pattern: '.*\.bias'
weight_decay: 0
weight_decay: 1e-2
lr: 1e-2
```
Some open questions for me are:
1. Should it be included in pytorch or done externally ?
2. fnmatch or re ?
3. if re, fullmatch or match ?
4. either way, what flags would make sense?
### Alternatives
Possible alternatives
- Overwriting the nn.Module class externally (I'm already doing this)
- Adding filter after the call to named_parameters
- Can be added in new methods of nn.Module rather than named_parameters & co
However it might be quite useful (including in other context than setting an optimizer) it would be a shame not to have this by default.
### Additional context
See [_named_members in nn.Module](https://github.com/pytorch/pytorch/blob/v2.5.0-rc6/torch/nn/modules/module.py#L2591)
Proposal with fnmatch
```python
def _named_members(self, get_members_fn, prefix='', recurse=True, remove_duplicate: bool = True, pattern: Optional[str] = None):
r"""Help yield various names + members of modules."""
memo = set()
modules = self.named_modules(prefix=prefix, remove_duplicate=remove_duplicate) if recurse else [(prefix, self)]
for module_prefix, module in modules:
members = get_members_fn(module)
for k, v in members:
if v is None or v in memo:
continue
if remove_duplicate:
memo.add(v)
name = module_prefix + ('.' if module_prefix else '') + k
if pattern is None or fnmatch.fnmatch(name, pattern): # Added line
yield name, v
```
Proposal with re. I used .fullmatch because it seemed more natural but could be discussed.
```python
def _named_members(self, get_members_fn, prefix='', recurse=True, remove_duplicate: bool = True, pattern: Optional[str] = None):
r"""Help yield various names + members of modules."""
if pattern is not None: # Added line
pattern = re.compile(pattern) # Added line
memo = set()
modules = self.named_modules(prefix=prefix, remove_duplicate=remove_duplicate) if recurse else [(prefix, self)]
for module_prefix, module in modules:
members = get_members_fn(module)
for k, v in members:
if v is None or v in memo:
continue
if remove_duplicate:
memo.add(v)
name = module_prefix + ('.' if module_prefix else '') + k
if pattern is None or pattern.fullmatch(name): # Added line
yield name, v
```
The other functions (`parameters`, `named_parameters`, `buffers` and `named_buffers`) just have to be modified to pass the value of `pattern` forward.
cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @vincentqb @janeyx99 @crcrpar | module: nn,module: optimizer,triaged | low | Minor |
2,559,445,662 | go | unique: `fatal error: getWeakHandle on invalid pointer` with `sbrk=1` | ### Go version
go1.24-0206eb9679, 1.23.1
### Output of `go env` in your module/workspace:
```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/cbrasic/Library/Caches/go-build'
GOENV='/Users/cbrasic/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/cbrasic/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/cbrasic/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/cbrasic/repos/goroot'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/cbrasic/repos/goroot/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='devel go1.24-0206eb9679 Mon Sep 30 19:15:39 2024 +0000'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/Users/cbrasic/Library/Application Support/go/telemetry'
GCCGO='gccgo'
GOARM64='v8.0'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/_n/xv5mgbd173xf6p4vwlq3hmpw0000gp/T/go-build1074858196=/tmp/go-build -gno-record-gcc-switches -fno-common'
```
### What did you do?
I noticed that my go1.23.1 app panics when run with `GODEBUG="sbrk=1"` and tracked it down to `net/netip`, specifically [this line](https://github.com/golang/go/blob/bae2e968e2daadd39c1bdb1221648361d7277ddc/src/net/netip/netip.go#L71). I saw https://github.com/golang/go/issues/69458 and thought this issue might already be fixed so I rebuilt with go master but saw the same issue. Any app that imports `net/netip` will crash when run with `GODEBUG="sbrk=1"`
### What did you see happen?
```
$ cat main.go
package main
import "unique"
type addrDetail struct {
isV6 bool
}
var (
z6noz = unique.Make(addrDetail{isV6: true})
)
func main() {
}
$ go build main.go; GODEBUG="sbrk=1" ./main
fatal error: getWeakHandle on invalid pointer
goroutine 1 gp=0x10b290030 m=0 mp=0x104720320 [running, locked to thread]:
runtime.throw({0x10468f442?, 0x10462a4dc?})
/Users/cbrasic/repos/goroot/src/runtime/panic.go:1069 +0x38 fp=0x1400008cc20 sp=0x1400008cbf0 pc=0x10467f038
runtime.getWeakHandle(0x10b2d5e58)
/Users/cbrasic/repos/goroot/src/runtime/mheap.go:2157 +0x138 fp=0x1400008cc70 sp=0x1400008cc20 pc=0x104642d58
runtime.getOrAddWeakHandle(0x10b2d5e58)
/Users/cbrasic/repos/goroot/src/runtime/mheap.go:2098 +0x20 fp=0x1400008ccc0 sp=0x1400008cc70 pc=0x104642a50
internal/weak.runtime_registerWeakPointer(0x1400008cd01?)
/Users/cbrasic/repos/goroot/src/runtime/mheap.go:2045 +0x1c fp=0x1400008cce0 sp=0x1400008ccc0 pc=0x10467e95c
internal/weak.Make[...](0x10b2d5e58?)
/Users/cbrasic/repos/goroot/src/internal/weak/pointer.go:62 +0x74 fp=0x1400008cd00 sp=0x1400008cce0 pc=0x10468acb4
unique.Make[...].func1()
/Users/cbrasic/repos/goroot/src/unique/handle.go:64 +0xb4 fp=0x1400008cd50 sp=0x1400008cd00 pc=0x10468abe4
unique.Make[...]({0x0})
/Users/cbrasic/repos/goroot/src/unique/handle.go:74 +0x144 fp=0x1400008cdf0 sp=0x1400008cd50 pc=0x10468aab4
main.init()
/Users/cbrasic/repos/test/main.go:10 +0x28 fp=0x1400008ce10 sp=0x1400008cdf0 pc=0x104689828
runtime.doInit1(0x10471c350)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:7303 +0xd4 fp=0x1400008cf40 sp=0x1400008ce10 pc=0x10465fd44
runtime.doInit(...)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:7270
runtime.main()
/Users/cbrasic/repos/goroot/src/runtime/proc.go:254 +0x340 fp=0x1400008cfd0 sp=0x1400008cf40 pc=0x104650790
runtime.goexit({})
/Users/cbrasic/repos/goroot/src/runtime/asm_arm64.s:1223 +0x4 fp=0x1400008cfd0 sp=0x1400008cfd0 pc=0x1046847e4
goroutine 17 gp=0x10b2d52f8 m=nil [force gc (idle)]:
runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:435 +0xc8 fp=0x1400002e790 sp=0x1400002e770 pc=0x10467f118
runtime.goparkunlock(...)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:441
runtime.forcegchelper()
/Users/cbrasic/repos/goroot/src/runtime/proc.go:348 +0xb8 fp=0x1400002e7d0 sp=0x1400002e790 pc=0x104650a28
runtime.goexit({})
/Users/cbrasic/repos/goroot/src/runtime/asm_arm64.s:1223 +0x4 fp=0x1400002e7d0 sp=0x1400002e7d0 pc=0x1046847e4
created by runtime.init.7 in goroutine 1
/Users/cbrasic/repos/goroot/src/runtime/proc.go:336 +0x24
goroutine 18 gp=0x10b2d5548 m=nil [GC sweep wait]:
runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:435 +0xc8 fp=0x1400002ef60 sp=0x1400002ef40 pc=0x10467f118
runtime.goparkunlock(...)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:441
runtime.bgsweep(0x10b2d54c0)
/Users/cbrasic/repos/goroot/src/runtime/mgcsweep.go:277 +0xa0 fp=0x1400002efb0 sp=0x1400002ef60 pc=0x10463cf10
runtime.gcenable.gowrap1()
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:203 +0x28 fp=0x1400002efd0 sp=0x1400002efb0 pc=0x1046310f8
runtime.goexit({})
/Users/cbrasic/repos/goroot/src/runtime/asm_arm64.s:1223 +0x4 fp=0x1400002efd0 sp=0x1400002efd0 pc=0x1046847e4
created by runtime.gcenable in goroutine 1
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:203 +0x6c
goroutine 19 gp=0x10b2d5728 m=nil [GC scavenge wait]:
runtime.gopark(0x10b2d54c0?, 0x1046a8e88?, 0x1?, 0x0?, 0x10b2d5728?)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:435 +0xc8 fp=0x1400002f760 sp=0x1400002f740 pc=0x10467f118
runtime.goparkunlock(...)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:441
runtime.(*scavengerState).park(0x10471fba0)
/Users/cbrasic/repos/goroot/src/runtime/mgcscavenge.go:425 +0x5c fp=0x1400002f790 sp=0x1400002f760 pc=0x10463a9ac
runtime.bgscavenge(0x10b2d54c0)
/Users/cbrasic/repos/goroot/src/runtime/mgcscavenge.go:653 +0x44 fp=0x1400002f7b0 sp=0x1400002f790 pc=0x10463aee4
runtime.gcenable.gowrap2()
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:204 +0x28 fp=0x1400002f7d0 sp=0x1400002f7b0 pc=0x104631098
runtime.goexit({})
/Users/cbrasic/repos/goroot/src/runtime/asm_arm64.s:1223 +0x4 fp=0x1400002f7d0 sp=0x1400002f7d0 pc=0x1046847e4
created by runtime.gcenable in goroutine 1
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:204 +0xac
goroutine 20 gp=0x10b2d5b40 m=nil [chan receive]:
runtime.gopark(0x14000032738?, 0x1046505c4?, 0x38?, 0x27?, 0x0?)
/Users/cbrasic/repos/goroot/src/runtime/proc.go:435 +0xc8 fp=0x140000326f0 sp=0x140000326d0 pc=0x10467f118
runtime.chanrecv(0x10b2d5ac0, 0x0, 0x1)
/Users/cbrasic/repos/goroot/src/runtime/chan.go:640 +0x408 fp=0x14000032770 sp=0x140000326f0 pc=0x104624c88
runtime.chanrecv1(0x104720320?, 0x104650850?)
/Users/cbrasic/repos/goroot/src/runtime/chan.go:490 +0x14 fp=0x140000327a0 sp=0x14000032770 pc=0x104624874
runtime.unique_runtime_registerUniqueMapCleanup.func1(...)
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:1731
runtime.unique_runtime_registerUniqueMapCleanup.gowrap1()
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:1734 +0x3c fp=0x140000327d0 sp=0x140000327a0 pc=0x104633f8c
runtime.goexit({})
/Users/cbrasic/repos/goroot/src/runtime/asm_arm64.s:1223 +0x4 fp=0x140000327d0 sp=0x140000327d0 pc=0x1046847e4
created by unique.runtime_registerUniqueMapCleanup in goroutine 1
/Users/cbrasic/repos/goroot/src/runtime/mgc.go:1729 +0xa0
```
### What did you expect to see?
no crash | NeedsInvestigation,compiler/runtime | low | Critical |
2,559,451,218 | node | build: configure path refactoring broke ICU download on windows | ### Version
main
### Platform
_No response_
### Subsystem
build
### What steps will reproduce the bug?
on windows git bash:
```shell
./configure --with-intl=full-icu --with-icu-source=https://github.com/unicode-org/icu/releases/download/release-76-rc/icu4c-76_1-src.tgz
```
### How often does it reproduce? Is there a required condition?
always
### What is the expected behavior? Why is that the expected behavior?
successful configure
### What do you see instead?
```
Traceback (most recent call last):
File "C:\Users\srl29\src\node\configure", line 28, in <module>
import configure
File "C:\Users\srl29\src\node\configure.py", line 2204, in <module>
configure_intl(output)
File "C:\Users\srl29\src\node\configure.py", line 1939, in configure_intl
elif with_icu_source and Path(icu_full_path).resolve() == Path(with_icu_source).resolve():
File "C:\Users\srl29\.pyenv\pyenv-win\versions\3.9.13\lib\pathlib.py", line 1215, in resolve
s = self._flavour.resolve(self, strict=strict)
File "C:\Users\srl29\.pyenv\pyenv-win\versions\3.9.13\lib\pathlib.py", line 215, in resolve
s = self._ext_to_normal(_getfinalpathname(s))
OSError: [WinError 123] El nombre de archivo, el nombre de directorio o la sintaxis de la etiqueta del volumen no son correctos: 'https:\\github.com\\unicode-org\\icu\\releases\\download\\release-76-rc\\icu4c-76_1-src.tgz'
```
### Additional information
broke in #47581 | build,python,icu | low | Critical |
2,559,482,184 | kubernetes | [Compatibility Version] Resource Lifecycle n+3 | We have prerelease-lifecycle tags that tags the releases when a resource is introduced, deprecated, and removed. With the introduction of compatibility versions, these versions become a bit more tricky.
We currently use binary version to warn kubectl on with deprecation policies and this will need to be fixed to use emulation version: https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/installer.go#L770
Because emulation can be 3 versions less than the binary version, one additional caveat is that we need to keep removed resources an extra 3 releases to be able to fully emulate the range of versions.
A resource available in 1.30, deprecated in 1.33 and removed in 1.36 (per resource lifecycle) must keep the resource in code until 1.39 because a 1.38 cluster can still emulate 1.35 when the resource is still available in the cluster.
One other point of consideration is testing. In the above example, if a resource is still able to be served with an emulation version toggle, it makes sense that tests should be kept. However, the tests will fail if the resource is already removed for the latest emulation version. Upon an API being removed, would we lock the tests to the emulation version before the removal? These would then be removed 3 releases later when the resource is finally able to be removed? We would need to communicate to feature owners not to delete tests and preserve them with a fixed compatibility version. Logically this solves our problems but the chore of bumping the compatibility version will have more nuanced things we need to do. (https://github.com/kubernetes/kubernetes/pull/126977 was already quite involved with pushing removal back one release via `KUBE_APISERVER_SERVE_REMOVED_APIS_FOR_ONE_RELEASE`)
/cc @jpbetz @deads2k @aaron-prindle
/sig api-machinery
/triage accepted
| sig/api-machinery,triage/accepted | low | Major |
2,559,489,547 | deno | Poor dynamic route syntax results in less-than-perfect error message | I've found that if you create a dynamic route in the form of `[:myparam].tsx` rather than `[myparam].tsx` the error message is
```
error: Uncaught (in promise) TypeError: tokenizer error: invalid name; must be at least length 1 (at char 1)
path: new URLPattern({ pathname }),
^
at new URLPattern (ext:deno_url/01_urlpattern.js:190:24)
at UrlPatternRouter.add (https://jsr.io/@fresh/core/2.0.0-alpha.20/src/router.ts:55:15)
at App.#addRoutes (https://jsr.io/@fresh/core/2.0.0-alpha.20/src/app.ts:166:18)
at App.get (https://jsr.io/@fresh/core/2.0.0-alpha.20/src/app.ts:106:27)
at fsRoutes (https://jsr.io/@fresh/core/2.0.0-alpha.20/src/plugins/fs_routes/mod.ts:316:21)
```
If this is sufficient and you aren't interested in more friendly debugging output feel free to close, it isn't all that hard to figure out, but I just hit it twice in a row and figured I'd call it out.
https://github.com/denoland/fresh/blob/b5389f69a384280319d815d6f35dd9743f0738b2/src/router.ts#L55 | bug,ext/url | low | Critical |
2,559,497,077 | pytorch | Use SymInt instead of sympy.Expr uniformly in Inductor | ### 🐛 Describe the bug
Sympy passes sympy.Expr around directly but this makes a lot of manipulations annoying. For example,
```
V.graph.sizevars.guard_equals(sympy_product(old_size), sympy_product(new_size))
```
This doesn't install a deferred runtime assert when there are unbacked SymInts. If you had done the equivalent torch._check it would have done so.
Similarly, guard size oblivious has to be spelled specially
```
V.graph.sizevars.shape_env.evaluate_expr(
sympy.Eq(old_size[i], 1), size_oblivious=True
)
```
See also @bdhirsh's recent PR https://github.com/pytorch/pytorch/pull/136670
So how can we do this port? It would be nice to do it incrementally.
* As a start, let's have easy APIs for converting between sympy.Expr and SymInt
* A good start is in lowering.py; specifically, without changing the external facing API, let's write a decorator that wraps sympy.Expr into SymInt on entry to the lowering function, and unwraps them when they exit.
* We also want to change IR nodes so that they accept SymInt instead of sympy.Expr... maybe there can be some intermediate state where they accept either
* More typing in Inductor would help do the porting without having to do a full test suite run...
cc @chauhang @penguinwu @bobrenjc93 @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @zou3519 @jansel
### Versions
main | triaged,oncall: pt2,module: dynamic shapes,module: inductor | low | Critical |
2,559,510,582 | PowerToys | With Keyboard Remapping, source keys are also triggered | ### Microsoft PowerToys version
0.76.2
### Installation method
PowerToys auto-update
### Running as admin
Yes
### Area(s) with issue?
Keyboard Manager
### Steps to reproduce
1. Define any keymaps. e.g.
3. Open Text Editor
4. Type key which was mapped in Step 1
### ✔️ Expected Behavior
Only see target key.
### ❌ Actual Behavior
We see sometimes source keys as well. e.g.
This case I only used "3" key, which I expect to see only "4".
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,559,549,065 | godot | Drag'n'dropping a node onto its parent node in the scene tree selects it in the (2D) Editor, but not the Inspector | ### Tested versions
- Reproducible in 4.3-stable
### System information
Godot v4.3.stable - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) - AMD Ryzen 7 7700X 8-Core Processor (16 Threads)
### Issue description
When a node is selected in the scene tree, this updates the view in the 2D Editor and the Inspector to highlight the node there as well.
Under very specific circumstances, this update does not happen fully. In this case: drag'n'dropping a node onto its parent to put it as the lowest of the children highlights the node to be highlighted in the 2D Editor, but the Inspector does not update accordingly.
### Steps to reproduce
1. Create a scene with a root node and two distinguishable child nodes (eg. a Container with a label and a button)
2. Select the lower node in the scene tree
3. drag the upper node onto its parent in the scene tree
### Minimal reproduction project (MRP)
N/A | bug,topic:editor,topic:2d | low | Minor |
2,559,591,749 | pytorch | Expressions involving Min/Max don't simplify with value ranges information | ### 🐛 Describe the bug
Repro:
```
import torch
torch._dynamo.config.capture_scalar_outputs = True
@torch.compile(fullgraph=True)
def f(x):
x0, x1 = x.tolist()
torch._check(x0 <= 5)
if torch.sym_min(x0, 5) == x0:
return torch.tensor(True)
else:
return torch.tensor(False)
f(torch.tensor([3, 5]))
```
Here, because we know that x0 <= 5, we can simplify Min(x0, 5) to just x0. However, it is a little awkward to actually implement this, because today Sympy expressions don't necessarily have access to the ShapeEnv, so we can't actually put the simplification there. We could add a dedicated simplification algorithm in ShapeEnv.simplify to do this, I guess. I kind of wish I did have access to these ranges inside the Sympy simplification rules though.
This is similar to https://github.com/pytorch/pytorch/issues/125914 but it is in some sense simpler, as no size oblivious is involved (so it would be valid to unconditionally do the simplification here; in the other case, we must not simplify ahead of time and only apply the simplification when a size oblivious test is done.)
### Versions
main
cc @chauhang @penguinwu @bobrenjc93 | triaged,oncall: pt2,module: dynamic shapes | low | Critical |
2,559,599,543 | PowerToys | 快速访问中的工具自定义 | ### Description of the new feature / enhancement
希望能够自定义快速访问中的工具
### Scenario when this would be used?
希望提供自定义此页面中的工具的方式
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,559,603,939 | PowerToys | Icon Management | ### Description of the new feature / enhancement
The feature should permit modification (editing) of program icons that can otherwise not be modified. This feature could further be extended for more detailed control over the details of executables, but primarily, the ability to upload a new image for the icon and a 'recolor' tool for icons would be appreciated.
As an aside, if this feature could be utilized through RDP or ConnectWise remote sessions without needing to install it on a target computer, that'd be amazing. Though I imagine that would be beyond the scope of this feature, if it is even a possibility.
### Scenario when this would be used?
Primarily, I see this utilized in personalization of a client's workspace. However, it also has some use in enterprise environments where there may be multiple variations of the same application that SHOULD have different icons, but utilize a centralized icon instead, leading to confusion.
### Supporting information
Although software that does similar already exists (see Resource Hacker), the software that mimics this capability isn't terribly trustworthy. This limits the spaces in which it can be utilized to a great degree. Having this feature available from a more trustworthy and verifiable source such as PowerToys would be an amazing boon. | Needs-Triage | low | Minor |
2,559,644,491 | PowerToys | Fancy Zones takes over Shift and Shift-lock keys on startup | ### Microsoft PowerToys version
0.84.1
### Installation method
PowerToys auto-update
### Running as admin
Yes
### Area(s) with issue?
FancyZones
### Steps to reproduce
Bootup, attempting to logon to Google Chrome profile, mini browser window pops up for MFA (Duo) logon. Cannot use Shift or Shift-lock key while entering password. Entire screen shows grey 1,2,3 zones. Not sure why this is activating only on the MFA logon prompt, and only with the Shift key. Reboot stops the behavior. Turning off Fancy Zones stops the behavior. Choosing to disable this feature.
### ✔️ Expected Behavior
No intereference. Have been able to logon with no trouble until this past week.
### ❌ Actual Behavior
Entire screen taken over by 1,2,3 zone overlay. Multiple bad password entries are locking out accounts.
### Other Software
Chrome 128, 129 | Issue-Bug,Needs-Triage | low | Minor |
2,559,644,567 | pytorch | [CI] Multiple tests fail with `Host and device pointer dont match with cudaHostRegister` and are being disabled | ### 🐛 Describe the bug
Example failure is e.g. visible in: https://github.com/pytorch/pytorch/issues/136537
which disables `test_graph_optims_Adam_cuda_float32`.
Checking the logs however shows that this error might be a fallout of a previous error:
https://hud.pytorch.org/flakytest?name=test_graph_optims_Adam_cuda_float32&suite=TestCudaOptimsCUDA&limit=100:
```
2024-09-24T16:25:11.4725870Z test_cuda.py::TestCudaAutocast::test_cuda_autocast_deprecated_warning PASSED [0.0125s] [ 82%]
2024-09-24T16:25:11.4729838Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaler_with_preset_grad_scale_in_place_unscale_False_AdamW_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135692 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 83%]
2024-09-24T16:25:11.4735935Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaler_with_preset_grad_scale_in_place_unscale_False_Adam_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135721 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 83%]
2024-09-24T16:25:11.4742040Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaler_with_preset_grad_scale_in_place_unscale_False_SGD_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135783 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 84%]
2024-09-24T16:25:11.4748098Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaler_with_preset_grad_scale_in_place_unscale_True_AdamW_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135829 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 85%]
2024-09-24T16:25:11.4754146Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaler_with_preset_grad_scale_in_place_unscale_True_Adam_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135881 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 85%]
2024-09-24T16:25:11.4760177Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaler_with_preset_grad_scale_in_place_unscale_True_SGD_cuda_float32 SKIPPED [0.0012s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135925 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 86%]
2024-09-24T16:25:11.4764049Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaling_autocast_fused_optimizers_Adagrad_cuda_float32 SKIPPED [0.0020s] (cuda is not supported for fused on Adagrad) [ 86%]
2024-09-24T16:25:11.4768258Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaling_autocast_fused_optimizers_AdamW_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135963 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 87%]
2024-09-24T16:25:11.4774184Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaling_autocast_fused_optimizers_Adam_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/135993 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 87%]
2024-09-24T16:25:11.4780089Z test_cuda.py::TestCudaOptimsCUDA::test_grad_scaling_autocast_fused_optimizers_SGD_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136013 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 88%]
2024-09-24T16:25:11.4785951Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_False_fused_False_AdamW_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136126 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 88%]
2024-09-24T16:25:11.4792299Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_False_fused_False_Adam_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136137 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 89%]
2024-09-24T16:25:11.4798306Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_False_fused_False_SGD_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136176 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 90%]
2024-09-24T16:25:11.4804303Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_False_fused_True_AdamW_cuda_float32 SKIPPED [0.0012s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136230 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 90%]
2024-09-24T16:25:11.4810330Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_False_fused_True_Adam_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136352 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 91%]
2024-09-24T16:25:11.4816211Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_False_fused_True_SGD_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136372 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 91%]
2024-09-24T16:25:11.4822113Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_True_fused_False_AdamW_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136411 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 92%]
2024-09-24T16:25:11.4828147Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_True_fused_False_Adam_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136417 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 92%]
2024-09-24T16:25:11.4834142Z test_cuda.py::TestCudaOptimsCUDA::test_graph_grad_scaling_foreach_True_fused_False_SGD_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136437 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 93%]
2024-09-24T16:25:11.4839819Z test_cuda.py::TestCudaOptimsCUDA::test_graph_optims_ASGD_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136468 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 93%]
2024-09-24T16:25:11.4845421Z test_cuda.py::TestCudaOptimsCUDA::test_graph_optims_Adadelta_cuda_float32 SKIPPED [0.0009s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136506 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 94%]
2024-09-24T16:25:11.4850965Z test_cuda.py::TestCudaOptimsCUDA::test_graph_optims_AdamW_cuda_float32 SKIPPED [0.0012s] (Test is disabled because an issue exists disabling it: https://github.com/pytorch/pytorch/issues/136521 for platform(s) linux. If you're seeing this on your local machine and would like to enable this test, please make sure CI is not set and you are not using the flag --import-disabled-tests.) [ 95%]
2024-09-24T16:25:11.4854417Z test_cuda.py::TestCudaOptimsCUDA::test_graph_optims_Adam_cuda_float32 ('RERUN', {'yellow': True}) [0.2080s] [ 95%]
2024-09-24T16:25:11.4856042Z test_cuda.py::TestCudaOptimsCUDA::test_graph_optims_Adam_cuda_float32 ('RERUN', {'yellow': True}) [0.1982s] [ 95%]
2024-09-24T16:25:11.4857401Z test_cuda.py::TestCudaOptimsCUDA::test_graph_optims_Adam_cuda_float32 FAILED [0.1977s] [ 95%]
2024-09-24T16:25:11.4858128Z
2024-09-24T16:25:11.4858412Z ==================================== RERUNS ====================================
2024-09-24T16:25:11.4859282Z ____________ TestCudaOptimsCUDA.test_graph_optims_Adam_cuda_float32 ____________
2024-09-24T16:25:11.4860066Z Traceback (most recent call last):
2024-09-24T16:25:11.4861384Z File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_comparison.py", line 1232, in not_close_error_metas
2024-09-24T16:25:11.4862541Z pair.compare()
2024-09-24T16:25:11.4863613Z File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_comparison.py", line 711, in compare
2024-09-24T16:25:11.4864708Z self._compare_values(actual, expected)
2024-09-24T16:25:11.4866018Z File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_comparison.py", line 841, in _compare_values
2024-09-24T16:25:11.4867090Z compare_fn(
2024-09-24T16:25:11.4868328Z File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_comparison.py", line 1023, in _compare_regular_values_close
2024-09-24T16:25:11.4869536Z if torch.all(matches):
2024-09-24T16:25:11.4870914Z RuntimeError: Host and device pointer dont match with cudaHostRegister. Please dont use this feature by setting PYTORCH_CUDA_ALLOC_CONF=use_cuda_host_register:False (default)
```
shows multiple tests were already skipped before.
Visiting these shows the same error again; e.g. let's pick the first skipped one:
https://github.com/pytorch/pytorch/issues/135692
showing the same error again.
TL;DR: it seems the `cudaHostRegister` error creeps through CI and disables tests one-by-one blaming unrelated modules.
CC @crcrpar @janeyx99 @malfet
### Versions
Visible in CI, so no specific versions.
cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @seemethere @malfet @pytorch/pytorch-dev-infra | high priority,module: cuda,module: ci,triaged | low | Critical |
2,559,713,571 | kubernetes | Document stability guarantees for API query strings | We support query strings in the API. Do we have any stability guarantees about these? I don't think they are documented - https://kubernetes.io/docs/reference/using-api/deprecation-policy/#deprecating-parts-of-the-api isn't clear on this.
For example, we currently support `GET /api/v1/namespaces/test/pods?watch=1&resourceVersion=42` but could we drop support for `resourceVersion`?
I think the answer is “Heck no!” - but let's get that in writing.
/kind documentation
/sig docs
/wg api-expression | kind/documentation,sig/docs,lifecycle/stale,wg/api-expression,needs-triage | low | Minor |
2,559,719,255 | node | build: vcbuild format-md doesn't hit all the things | ## Summary
`vcbuild.bat format-md` did not reformat `.\doc\contributing\maintaining\maintaining-icu.md`
## Repro
My PR said to run `format-md`, so:
```shell
PS C:\Users\srl29\src\node> .\vcbuild.bat format-md
Running Markdown formatter on docs...
PS C:\Users\srl29\src\node> git status
On branch fix-icu-windows-configure-55214
Your branch is up to date with 'srl295/fix-icu-windows-configure-55214'.
nothing to commit, working tree clean
```
Investigating, found that `format-md` only hits `doc\*.md`.
## Workaround
```shell
PS C:\Users\srl29\src\node> out\release\node.exe .\tools\lint-md\lint-md.mjs --format .\doc\contributing\maintaining\maintaining-icu.md
```
| windows,build | low | Minor |
2,559,732,594 | rust | ICE: `expected int of size 8, but got size 2` | <!--
[31mICE[0m: Rustc ./a.rs '' 'error: internal compiler error: compiler/rustc_middle/src/ty/consts/int.rs:263:13: expected int of size 8, but got size 2', 'error: internal compiler error: compiler/rustc_middle/src/ty/consts/int.rs:263:13: expected int of size 8, but got size 2'
File: /tmp/im/a.rs
-->
auto-reduced (treereduce-rust):
````rust
pub struct Blorb<const N: u16>([String; N]);
pub struct Wrap(Blorb<0>);
pub const fn i(_: Wrap) {}
````
original:
````rust
//@ build-pass
pub(crate) const fn f<T, const N: usize>(_: [std::mem::MaybeUninit<T>; N]) {}
pub struct Blubb<T>(*const T);
pub const fn g<T, const N: usize>(_: [Blubb<T>; N]) {}
pub struct Blorb<const N: u16>([String; N]);
pub const fn h(_: Blorb<0>) {}
pub struct Wrap(Blorb<0>);
pub const fn i(_: Wrap) {}
fn main() {}
````
Version information
````
rustc 1.83.0-nightly (c4f717650 2024-10-01)
binary: rustc
commit-hash: c4f7176501a7d3c19c230b8c9111b2d39142f83a
commit-date: 2024-10-01
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
````
Command:
`/home/matthias/.rustup/toolchains/master/bin/rustc `
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Program output</strong></summary>
<p>
```
error[E0601]: `main` function not found in crate `mvce`
--> /tmp/icemaker_global_tempdir.LKr6KsHYtGSy/rustc_testrunner_tmpdir_reporting.3bKrkGKxt953/mvce.rs:5:27
|
5 | pub const fn i(_: Wrap) {}
| ^ consider adding a `main` function to `/tmp/icemaker_global_tempdir.LKr6KsHYtGSy/rustc_testrunner_tmpdir_reporting.3bKrkGKxt953/mvce.rs`
error: the constant `N` is not of type `usize`
--> /tmp/icemaker_global_tempdir.LKr6KsHYtGSy/rustc_testrunner_tmpdir_reporting.3bKrkGKxt953/mvce.rs:1:32
|
1 | pub struct Blorb<const N: u16>([String; N]);
| ^^^^^^^^^^^ expected `usize`, found `u16`
error: internal compiler error: compiler/rustc_middle/src/ty/consts/int.rs:263:13: expected int of size 8, but got size 2
thread 'rustc' panicked at compiler/rustc_middle/src/ty/consts/int.rs:263:13:
Box<dyn Any>
stack backtrace:
0: 0x7047d26daeda - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::had0a4a07d444c243
1: 0x7047d2e033e6 - core::fmt::write::hfa03780471fd40a1
2: 0x7047d3fbd491 - std::io::Write::write_fmt::he88bb98b829c33b1
3: 0x7047d26dad32 - std::sys::backtrace::BacktraceLock::print::h1e8153a6bf47e7a5
4: 0x7047d26dd251 - std::panicking::default_hook::{{closure}}::h2d7a6dde612f1b16
5: 0x7047d26dd084 - std::panicking::default_hook::ha6ce9de3458bcdda
6: 0x7047d17a486f - std[c1d7bd3f58de7430]::panicking::update_hook::<alloc[29d5ad3c4a91d383]::boxed::Box<rustc_driver_impl[b3d9015aed309aa5]::install_ice_hook::{closure#0}>>::{closure#0}
7: 0x7047d26dd968 - std::panicking::rust_panic_with_hook::haf1d2e00d64b82f1
8: 0x7047d17de321 - std[c1d7bd3f58de7430]::panicking::begin_panic::<rustc_errors[a2cc27f529684419]::ExplicitBug>::{closure#0}
9: 0x7047d17d13c6 - std[c1d7bd3f58de7430]::sys::backtrace::__rust_end_short_backtrace::<std[c1d7bd3f58de7430]::panicking::begin_panic<rustc_errors[a2cc27f529684419]::ExplicitBug>::{closure#0}, !>
10: 0x7047d17ccad9 - std[c1d7bd3f58de7430]::panicking::begin_panic::<rustc_errors[a2cc27f529684419]::ExplicitBug>
11: 0x7047d17e7bb1 - <rustc_errors[a2cc27f529684419]::diagnostic::BugAbort as rustc_errors[a2cc27f529684419]::diagnostic::EmissionGuarantee>::emit_producing_guarantee
12: 0x7047d1e0ba54 - rustc_middle[99056c3c142edfd1]::util::bug::opt_span_bug_fmt::<rustc_span[fbdd09955dfcae25]::span_encoding::Span>::{closure#0}
13: 0x7047d1df17ca - rustc_middle[99056c3c142edfd1]::ty::context::tls::with_opt::<rustc_middle[99056c3c142edfd1]::util::bug::opt_span_bug_fmt<rustc_span[fbdd09955dfcae25]::span_encoding::Span>::{closure#0}, !>::{closure#0}
14: 0x7047d1df165b - rustc_middle[99056c3c142edfd1]::ty::context::tls::with_context_opt::<rustc_middle[99056c3c142edfd1]::ty::context::tls::with_opt<rustc_middle[99056c3c142edfd1]::util::bug::opt_span_bug_fmt<rustc_span[fbdd09955dfcae25]::span_encoding::Span>::{closure#0}, !>::{closure#0}, !>
15: 0x7047cf3cce60 - rustc_middle[99056c3c142edfd1]::util::bug::bug_fmt
16: 0x7047cf94826a - rustc_middle[99056c3c142edfd1]::ty::util::needs_drop_components_with_async
17: 0x7047d31ebeb7 - rustc_ty_utils[7eb78ab09d37383f]::needs_drop::needs_drop_raw
18: 0x7047d31eba8f - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::needs_drop_raw::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 1usize]>>
19: 0x7047d31eaebf - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::DefaultCache<rustc_middle[99056c3c142edfd1]::ty::ParamEnvAnd<rustc_middle[99056c3c142edfd1]::ty::Ty>, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 1usize]>>, false, false, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
20: 0x7047d31eab0e - rustc_query_impl[a128c9efc091a24e]::query_impl::needs_drop_raw::get_query_non_incr::__rust_end_short_backtrace
21: 0x7047d37a04a2 - rustc_mir_build[624742ab29f03d50]::build::mir_build
22: 0x7047d2e04f06 - rustc_mir_transform[72b720a2bb6a9bbb]::mir_built
23: 0x7047d2e04ec9 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::mir_built::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 8usize]>>
24: 0x7047d31a94ba - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::VecCache<rustc_span[fbdd09955dfcae25]::def_id::LocalDefId, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 8usize]>>, false, false, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
25: 0x7047d31a8fcd - rustc_query_impl[a128c9efc091a24e]::query_impl::mir_built::get_query_non_incr::__rust_end_short_backtrace
26: 0x7047cf4dc4e3 - rustc_mir_build[624742ab29f03d50]::check_unsafety::check_unsafety
27: 0x7047d3633fe7 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::check_unsafety::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 0usize]>>
28: 0x7047d3634298 - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::VecCache<rustc_span[fbdd09955dfcae25]::def_id::LocalDefId, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 0usize]>>, false, false, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
29: 0x7047d3633f17 - rustc_query_impl[a128c9efc091a24e]::query_impl::check_unsafety::get_query_non_incr::__rust_end_short_backtrace
30: 0x7047d31a2d47 - rustc_interface[89dec4b9d675c708]::passes::run_required_analyses
31: 0x7047d3b0f51e - rustc_interface[89dec4b9d675c708]::passes::analysis
32: 0x7047d3b0f4f1 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 1usize]>>
33: 0x7047d3c9252e - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::SingleCache<rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 1usize]>>, false, false, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
34: 0x7047d3c9220f - rustc_query_impl[a128c9efc091a24e]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
35: 0x7047d3b1f55e - rustc_interface[89dec4b9d675c708]::interface::run_compiler::<core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>, rustc_driver_impl[b3d9015aed309aa5]::run_compiler::{closure#0}>::{closure#1}
36: 0x7047d3bea350 - std[c1d7bd3f58de7430]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[89dec4b9d675c708]::util::run_in_thread_with_globals<rustc_interface[89dec4b9d675c708]::util::run_in_thread_pool_with_globals<rustc_interface[89dec4b9d675c708]::interface::run_compiler<core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>, rustc_driver_impl[b3d9015aed309aa5]::run_compiler::{closure#0}>::{closure#1}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>
37: 0x7047d3bea9ba - <<std[c1d7bd3f58de7430]::thread::Builder>::spawn_unchecked_<rustc_interface[89dec4b9d675c708]::util::run_in_thread_with_globals<rustc_interface[89dec4b9d675c708]::util::run_in_thread_pool_with_globals<rustc_interface[89dec4b9d675c708]::interface::run_compiler<core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>, rustc_driver_impl[b3d9015aed309aa5]::run_compiler::{closure#0}>::{closure#1}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#1} as core[d0cd706d8d014919]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
38: 0x7047d3beadab - std::sys::pal::unix::thread::Thread::new::thread_start::h6a16a471557e53ce
39: 0x7047d533639d - <unknown>
40: 0x7047d53bb49c - <unknown>
41: 0x0 - <unknown>
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: please make sure that you have updated to the latest nightly
note: rustc 1.83.0-nightly (c4f717650 2024-10-01) running on x86_64-unknown-linux-gnu
query stack during panic:
#0 [needs_drop_raw] computing whether `Wrap` needs drop
#1 [mir_built] building MIR for `i`
end of query stack
error: aborting due to 3 previous errors
For more information about this error, try `rustc --explain E0601`.
```
</p>
</details>
<!--
query stack:
#0 [needs_drop_raw] computing whether `Wrap` needs drop
#1 [mir_built] building MIR for `i`
-->
| I-ICE,T-compiler,C-bug,S-bug-has-test | low | Critical |
2,559,749,371 | rust | ICE: `expected int of size 8, but got size 16` | <!--
[31mICE[0m: Rustc ./o.rs '' 'error: internal compiler error: /rustc/c4f7176501a7d3c19c230b8c9111b2d39142f83a/compiler/rustc_middle/src/ty/consts/int.rs:263:13: expected int of size 8, but got size 16', 'error: internal compiler error: /rustc/c4f7176501a7d3c19c230b8c9111b2d39142f83a/compiler/rustc_middle/src/ty/consts/int.rs:263:13: expected int of size 8, but got size 16'
File: /tmp/im/o.rs
-->
auto-reduced (treereduce-rust):
````rust
struct Struct<const N: i128>(pub [u8; N]);
pub fn function(value: Struct<3>) -> u8 {
value.0[0]
}
````
original:
````rust
pub(in std::vec) struct Struct<const N: i128>(pub [u8; N]);
pub type Alias = Struct<2>;
pub fn function(value: Struct<3>) -> u8 {
value.0[0]
}
````
Version information
````
rustc 1.83.0-nightly (c4f717650 2024-10-01)
binary: rustc
commit-hash: c4f7176501a7d3c19c230b8c9111b2d39142f83a
commit-date: 2024-10-01
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
````
Command:
`/home/matthias/.rustup/toolchains/master/bin/rustc `
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Program output</strong></summary>
<p>
```
error[E0601]: `main` function not found in crate `mvce`
--> /tmp/icemaker_global_tempdir.3gYz1ILWhmcV/rustc_testrunner_tmpdir_reporting.d58vX2lbiZNF/mvce.rs:5:2
|
5 | }
| ^ consider adding a `main` function to `/tmp/icemaker_global_tempdir.3gYz1ILWhmcV/rustc_testrunner_tmpdir_reporting.d58vX2lbiZNF/mvce.rs`
error: the constant `N` is not of type `usize`
--> /tmp/icemaker_global_tempdir.3gYz1ILWhmcV/rustc_testrunner_tmpdir_reporting.d58vX2lbiZNF/mvce.rs:1:34
|
1 | struct Struct<const N: i128>(pub [u8; N]);
| ^^^^^^^ expected `usize`, found `i128`
error: internal compiler error: /rustc/c4f7176501a7d3c19c230b8c9111b2d39142f83a/compiler/rustc_middle/src/ty/consts/int.rs:263:13: expected int of size 8, but got size 16
thread 'rustc' panicked at /rustc/c4f7176501a7d3c19c230b8c9111b2d39142f83a/compiler/rustc_middle/src/ty/consts/int.rs:263:13:
Box<dyn Any>
stack backtrace:
0: 0x77bdb52daeda - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::had0a4a07d444c243
1: 0x77bdb5a033e6 - core::fmt::write::hfa03780471fd40a1
2: 0x77bdb6bbd491 - std::io::Write::write_fmt::he88bb98b829c33b1
3: 0x77bdb52dad32 - std::sys::backtrace::BacktraceLock::print::h1e8153a6bf47e7a5
4: 0x77bdb52dd251 - std::panicking::default_hook::{{closure}}::h2d7a6dde612f1b16
5: 0x77bdb52dd084 - std::panicking::default_hook::ha6ce9de3458bcdda
6: 0x77bdb43a486f - std[c1d7bd3f58de7430]::panicking::update_hook::<alloc[29d5ad3c4a91d383]::boxed::Box<rustc_driver_impl[b3d9015aed309aa5]::install_ice_hook::{closure#0}>>::{closure#0}
7: 0x77bdb52dd968 - std::panicking::rust_panic_with_hook::haf1d2e00d64b82f1
8: 0x77bdb43de321 - std[c1d7bd3f58de7430]::panicking::begin_panic::<rustc_errors[a2cc27f529684419]::ExplicitBug>::{closure#0}
9: 0x77bdb43d13c6 - std[c1d7bd3f58de7430]::sys::backtrace::__rust_end_short_backtrace::<std[c1d7bd3f58de7430]::panicking::begin_panic<rustc_errors[a2cc27f529684419]::ExplicitBug>::{closure#0}, !>
10: 0x77bdb43ccad9 - std[c1d7bd3f58de7430]::panicking::begin_panic::<rustc_errors[a2cc27f529684419]::ExplicitBug>
11: 0x77bdb43e7bb1 - <rustc_errors[a2cc27f529684419]::diagnostic::BugAbort as rustc_errors[a2cc27f529684419]::diagnostic::EmissionGuarantee>::emit_producing_guarantee
12: 0x77bdb4a0ba54 - rustc_middle[99056c3c142edfd1]::util::bug::opt_span_bug_fmt::<rustc_span[fbdd09955dfcae25]::span_encoding::Span>::{closure#0}
13: 0x77bdb49f17ca - rustc_middle[99056c3c142edfd1]::ty::context::tls::with_opt::<rustc_middle[99056c3c142edfd1]::util::bug::opt_span_bug_fmt<rustc_span[fbdd09955dfcae25]::span_encoding::Span>::{closure#0}, !>::{closure#0}
14: 0x77bdb49f165b - rustc_middle[99056c3c142edfd1]::ty::context::tls::with_context_opt::<rustc_middle[99056c3c142edfd1]::ty::context::tls::with_opt<rustc_middle[99056c3c142edfd1]::util::bug::opt_span_bug_fmt<rustc_span[fbdd09955dfcae25]::span_encoding::Span>::{closure#0}, !>::{closure#0}, !>
15: 0x77bdb1fcce60 - rustc_middle[99056c3c142edfd1]::util::bug::bug_fmt
16: 0x77bdb5f805ad - rustc_ty_utils[7eb78ab09d37383f]::layout::layout_of_uncached
17: 0x77bdb5f6e6c6 - rustc_ty_utils[7eb78ab09d37383f]::layout::layout_of
18: 0x77bdb5f6e651 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::layout_of::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 16usize]>>
19: 0x77bdb5f6d8cd - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::DefaultCache<rustc_middle[99056c3c142edfd1]::ty::ParamEnvAnd<rustc_middle[99056c3c142edfd1]::ty::Ty>, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 16usize]>>, false, true, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
20: 0x77bdb5f6d567 - rustc_query_impl[a128c9efc091a24e]::query_impl::layout_of::get_query_non_incr::__rust_end_short_backtrace
21: 0x77bdb5f6c962 - <core[d0cd706d8d014919]::iter::adapters::GenericShunt<core[d0cd706d8d014919]::iter::adapters::by_ref_sized::ByRefSized<core[d0cd706d8d014919]::iter::adapters::map::Map<core[d0cd706d8d014919]::slice::iter::Iter<rustc_middle[99056c3c142edfd1]::ty::VariantDef>, rustc_ty_utils[7eb78ab09d37383f]::layout::layout_of_uncached::{closure#13}>>, core[d0cd706d8d014919]::result::Result<core[d0cd706d8d014919]::convert::Infallible, &rustc_middle[99056c3c142edfd1]::ty::layout::LayoutError>> as core[d0cd706d8d014919]::iter::traits::iterator::Iterator>::next
22: 0x77bdb5f73150 - rustc_ty_utils[7eb78ab09d37383f]::layout::layout_of_uncached
23: 0x77bdb5f6e6c6 - rustc_ty_utils[7eb78ab09d37383f]::layout::layout_of
24: 0x77bdb5f6e651 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::layout_of::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 16usize]>>
25: 0x77bdb5f6d8cd - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::DefaultCache<rustc_middle[99056c3c142edfd1]::ty::ParamEnvAnd<rustc_middle[99056c3c142edfd1]::ty::Ty>, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 16usize]>>, false, true, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
26: 0x77bdb5f6d567 - rustc_query_impl[a128c9efc091a24e]::query_impl::layout_of::get_query_non_incr::__rust_end_short_backtrace
27: 0x77bdb2fa578d - <rustc_mir_transform[72b720a2bb6a9bbb]::known_panics_lint::KnownPanicsLint as rustc_mir_transform[72b720a2bb6a9bbb]::pass_manager::MirLint>::run_lint
28: 0x77bdb5a06d0c - rustc_mir_transform[72b720a2bb6a9bbb]::run_analysis_to_runtime_passes
29: 0x77bdb62bc48e - rustc_mir_transform[72b720a2bb6a9bbb]::mir_drops_elaborated_and_const_checked
30: 0x77bdb62bbdd1 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::mir_drops_elaborated_and_const_checked::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 8usize]>>
31: 0x77bdb5da94ba - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::VecCache<rustc_span[fbdd09955dfcae25]::def_id::LocalDefId, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 8usize]>>, false, false, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
32: 0x77bdb5da8e65 - rustc_query_impl[a128c9efc091a24e]::query_impl::mir_drops_elaborated_and_const_checked::get_query_non_incr::__rust_end_short_backtrace
33: 0x77bdb5da30a4 - rustc_interface[89dec4b9d675c708]::passes::run_required_analyses
34: 0x77bdb670f51e - rustc_interface[89dec4b9d675c708]::passes::analysis
35: 0x77bdb670f4f1 - rustc_query_impl[a128c9efc091a24e]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[a128c9efc091a24e]::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 1usize]>>
36: 0x77bdb689252e - rustc_query_system[a5b010e784c9cc4f]::query::plumbing::try_execute_query::<rustc_query_impl[a128c9efc091a24e]::DynamicConfig<rustc_query_system[a5b010e784c9cc4f]::query::caches::SingleCache<rustc_middle[99056c3c142edfd1]::query::erase::Erased<[u8; 1usize]>>, false, false, false>, rustc_query_impl[a128c9efc091a24e]::plumbing::QueryCtxt, false>
37: 0x77bdb689220f - rustc_query_impl[a128c9efc091a24e]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
38: 0x77bdb671f55e - rustc_interface[89dec4b9d675c708]::interface::run_compiler::<core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>, rustc_driver_impl[b3d9015aed309aa5]::run_compiler::{closure#0}>::{closure#1}
39: 0x77bdb67ea350 - std[c1d7bd3f58de7430]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[89dec4b9d675c708]::util::run_in_thread_with_globals<rustc_interface[89dec4b9d675c708]::util::run_in_thread_pool_with_globals<rustc_interface[89dec4b9d675c708]::interface::run_compiler<core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>, rustc_driver_impl[b3d9015aed309aa5]::run_compiler::{closure#0}>::{closure#1}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>
40: 0x77bdb67ea9ba - <<std[c1d7bd3f58de7430]::thread::Builder>::spawn_unchecked_<rustc_interface[89dec4b9d675c708]::util::run_in_thread_with_globals<rustc_interface[89dec4b9d675c708]::util::run_in_thread_pool_with_globals<rustc_interface[89dec4b9d675c708]::interface::run_compiler<core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>, rustc_driver_impl[b3d9015aed309aa5]::run_compiler::{closure#0}>::{closure#1}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[d0cd706d8d014919]::result::Result<(), rustc_span[fbdd09955dfcae25]::ErrorGuaranteed>>::{closure#1} as core[d0cd706d8d014919]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
41: 0x77bdb67eadab - std::sys::pal::unix::thread::Thread::new::thread_start::h6a16a471557e53ce
42: 0x77bdb7e5c39d - <unknown>
43: 0x77bdb7ee149c - <unknown>
44: 0x0 - <unknown>
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: please make sure that you have updated to the latest nightly
note: rustc 1.83.0-nightly (c4f717650 2024-10-01) running on x86_64-unknown-linux-gnu
query stack during panic:
#0 [layout_of] computing layout of `[u8; 3]`
#1 [layout_of] computing layout of `Struct<3>`
end of query stack
error: aborting due to 3 previous errors
For more information about this error, try `rustc --explain E0601`.
```
</p>
</details>
<!--
query stack:
#0 [layout_of] computing layout of `[u8; 3]`
#1 [layout_of] computing layout of `Struct<3>`
-->
| I-ICE,T-compiler,C-bug,S-bug-has-test | low | Critical |
2,559,763,093 | godot | Glow behaving weirdly when the color is set by multiplication and the items superposed. | ### Tested versions
v4.3.stable.official [77dcf97d8]
### System information
Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - integrated Intel(R) HD Graphics 520 (Intel Corporation; 31.0.101.2115) - Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (4 Threads)
### Issue description
When you set 2 objects color by using multiplication ( Exple : `Color(1., 0., 0.) * 10` instead of `Color(10., 0., 0.)`) and then superpose them, the glow effect is glitched in the zone of superposition.
### Steps to reproduce
1. Add 2 `Sprite2D` to the scene
2. Set both modulate color as `Color(1., 0., 0.) * 5` by code
3. Superpose them.
### Minimal reproduction project (MRP)
[bloomissue.zip](https://github.com/user-attachments/files/17213357/bloomissue.zip)
| discussion,topic:gdscript,topic:rendering | low | Minor |
2,559,769,287 | tensorflow | Jit-compiling `tf.while_loop` inside `tf.vectorized_map` raises `InvalidArgumentError` | ### Issue type
Bug
### Have you reproduced the bug with TensorFlow Nightly?
Yes
### Source
binary
### TensorFlow version
v2.17.0
### Custom code
Yes
### OS platform and distribution
Colab
### Mobile device
_No response_
### Python version
_No response_
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
_No response_
### GPU model and memory
_No response_
### Current behavior?
MRE
-------
The following mock-up of `cumsum` attempts to JIT compile a `tf.vectorized_map`ped function containing a `tf.scan`:
```python
import tensorflow as tf
def cumsum(xs):
return tf.scan(
lambda a, x: a + x, elems=xs
)
@tf.function(jit_compile=True)
def vec_cumsum(xs):
return tf.vectorized_map(cumsum, elems=xs)
xs_batched = tf.reshape(tf.range(30), (3, 10))
vec_cumsum(xs_batched)
```
__Expected behaviour__: `vec_cumsum(xs_batched)` returns a batch of cumulative sums.
__Actual behaviour__: Even though all data structures are known statically at JIT compile time, an InvalidArgumentError is raised with "No registered 'TensorListReserve'". The fault is clearly related to `tf.scan`'s use of `tf.while_loop`, as a (longer) example using naked `tf.while_loop(..., max_iterations=n)` will confirm.
In JAX, it is possible to jit-compile a `vmap`ped function containing a `lax.while_loop` indicating that this is possible in HLO. It seems the `tf.function(jit_compile=True)` machinery may be mis-transpiling to HLO somehow.
May be related to #73367 also involving `tf.vectorized_map` and `tf.while_loop` (albeit with reversed scope)?
### Standalone code to reproduce the issue
```shell
Colab MRE: https://colab.research.google.com/drive/1bmq1t3PdtebCSlNd0t-iEFrXX7Q0qqZp?usp=sharing
```
### Relevant log output
```shell
---------------------------------------------------------------------------
InvalidArgumentError Traceback (most recent call last)
<ipython-input-4-26ea491cd046> in <cell line: 13>()
11
12 # Fails with "No registered 'TensorListReserve'""
---> 13 vec_cumsum(xs_batched)
1 frames
/usr/local/lib/python3.10/dist-packages/tensorflow/python/eager/execute.py in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
51 try:
52 ctx.ensure_initialized()
---> 53 tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
54 inputs, attrs, num_outputs)
55 except core._NotOkStatusException as e:
InvalidArgumentError: Detected unsupported operations when trying to compile graph __inference_vec_cumsum_462[_XlaMustCompile=true,config_proto=13561319589895757934,executor_type=11160318154034397263] on XLA_CPU_JIT: TensorListReserve (No registered 'TensorListReserve' OpKernel for XLA_CPU_JIT devices compatible with node {{function_node __inference_while_fn_428}}{{node while_init/TensorArrayV2_4}}
(OpKernel was found, but attributes didn't match) Requested Attributes: element_dtype=DT_VARIANT, shape_type=DT_INT32){{function_node __inference_while_fn_428}}{{node while_init/TensorArrayV2_4}}
```
| stat:awaiting tensorflower,type:bug,comp:apis,comp:ops,2.17 | medium | Critical |
2,559,779,306 | godot | Double-click to rename in scene tree sometimes renames without double-click | ### Tested versions
Reproducible in 4.3-stable
### System information
Godot v4.3.stable - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) - AMD Ryzen 7 7700X 8-Core Processor (16 Threads)
### Issue description
When selecting multiple items in the scene tree, there are two methods I'm aware of:
- click, shift+click, and
- hold ctrl, click click click
(also the combination of both, but let's not get ahead of ourselves)
The latter puts the last clicked node in focus, while the former puts the highest node in focus.
Double clicking a node opens the rename-popup(?). The way this appears to be implemented is by just checking whether the clicked node was already in focus,
(with some safeguards that trip when another part of the UI is clicked or the cursor is moved over the 2D/3D Editor.)
and not whether a double-click action was performed.
This bug causes clicking the focused node in a multi-selection to open the rename-popup, even when it was single clicked and not double clicked.
Put differently: Shift+click select then click behaves differently for the highest item in the scene tree selection vs others.
### Steps to reproduce
Method A:
1. have some nodes in your scene.
2. click one in the scene tree
3. wait a while, move your mouse around, shift+tab into another application, shift+tab back
4. click the node again
Method B:
1. have some nodes in your scene
2. click something in the 2D/3D Editor
3. shift+click a lower node in the scene tree
4. click the node from step 2 in the scene tree
### Minimal reproduction project (MRP)
N/A | bug,topic:editor,topic:input | low | Critical |
2,559,783,666 | godot | Moving platforms and CharacterBody2Ds are a bit buggy | ### Tested versions
4.3
### System information
Godot v4.3.stable - Windows 10.0.19044 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 (NVIDIA; 31.0.15.3770) - Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz (12 Threads)
### Issue description
When putting a CharacterBody2D onto a moving platform, it doesn't stay perfectly on it, instead lagging behind.
### Steps to reproduce
-Make the default player controller, complete with nodes to have a working 2D character
-Make any type of moving platform (it has to be moving rather quickly)
-Stand on it
https://github.com/user-attachments/assets/552ff634-9dcb-4205-856a-21082a645016
### Minimal reproduction project (MRP)
[newGameProject.zip](https://github.com/user-attachments/files/17213449/newGameProject.zip)
| documentation,topic:physics | low | Critical |
2,559,788,667 | godot | AudioStreamPlayer pitch_scale ignored in Web unless tweened | ### Tested versions
v4.3.stable.official [77dcf97d8]
Chrome and Safari stable on M1 Mac.
Brave on Android.
### System information
Godot v4.3.stable - macOS 13.0.1 - Vulkan (Mobile) - integrated Apple M1 - Apple M1 (8 Threads)
### Issue description
Setting `AudioStreamPlayer.pitch_scale` has no effect on Web. Tweening it causes it to work, including tweening to the same value you just set it to, like
```swift
player.pitch_scale = 1.5 # optional
create_tween().tween_property(player, "pitch_scale", 1.5, .01)
```
`AudioStreamPlayer2D` does not have this bug.
### Steps to reproduce
1. Open attached test project
2. Run in Godot, click each of the buttons. Each causes a normal ding and a high ding.
3. Export to Web and run in a browser (e.g. via Remote Debug), or test at https://sorryrobot.com/pitchey .
Expected behavior:
All buttons play a low ding then a high ding on Web.
Actual behavior:
All buttons work except for the first, which plays 2 normal dings. (This button is setting `.pitch_scale` on an `AudioStreamPlayer` and not tweening.)
### Minimal reproduction project (MRP)
[test.zip](https://github.com/user-attachments/files/17213484/test.zip)
| bug,platform:web,topic:audio | low | Critical |
2,559,863,532 | godot | GDExtension: Static code attempting to manage memory before GDExtension is initialized results in a crash. | ### Tested versions
4.x
### System information
N/A
### Issue description
Applies to anything using GDExtension.
Attempting to initialize objects before GDExtension starts that manage memory (such as String, Dictionary, etc.) would result in a crash.
### Steps to reproduce
```cpp
static Dictionary d; // crash
static String s; // crash
```
### Minimal reproduction project (MRP)
N/A | bug,topic:gdextension | low | Critical |
2,559,937,517 | rust | rust compiler suggests to add lifetime to macro: `#'static[...]` | ### Code
https://github.com/Anatoly03/Netz/tree/bf8c6917b68c70cc0677b540402c4d64707670bc/util-parser
(The token stream generated by the broken macro is logged into the console.)
### Current output
```
error[E0106]: missing lifetime specifier
--> util-parser/tests/whitespace.rs:5:5
|
5 | #[grammar(~)]
| ^ expected named lifetime parameter
|
= help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from
= note: this error originates in the attribute macro `grammar` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static`
|
5 | #'static [grammar(~)]
| +++++++
help: instead, you are more likely to want to return an owned value
|
5 | String
|
```
### Desired output
```
[expand macro code with broken lines displayed]
error[????]: could not compile macro `grammar` due to ... errors
```
### Rationale and extra context
### Other cases
_No response_
### Rust Version
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-apple-darwin
release: 1.81.0
LLVM version: 18.1.7
### Anything else?
_No response_ | A-diagnostics,T-compiler | low | Critical |
2,559,987,707 | opencv | ML_ANN_Params.ActivationFunction fails on Intel Sapphire Rapids | ### System Information
OpenCV version 4.10
Operating system: RHEL 8
Compiler: GCC 8.4.1
### Detailed description
Test fails on Intel Sapphire Rapids but passes on Intel Raptor Lake and Intel Cascade Lake. In both release and debug modes.
```
$ OPENCV_IPP=disabled ./bin/opencv_test_ml --gtest_filter=ML_ANN_Params.ActivationFunction*
CTEST_FULL_OUTPUT
OpenCV version: 4.10.0
OpenCV VCS version: 4.9.0-552-ge4b378abf9
Build type: Debug
Compiler: /usr/bin/c++ (ver 8.4.1)
[ INFO:0@0.003] global registry_parallel.impl.hpp:96 ParallelBackendRegistry core(parallel): Enabled backends(3, sorted by priority): ONETBB(1000); TBB(990); OPENMP(980)
Parallel framework: pthreads (nthreads=96)
CPU features: SSE SSE2 SSE3 *SSE4.1 *SSE4.2 *FP16 *AVX *AVX2 *AVX512-SKX
[ INFO:0@0.003] global ocl.cpp:1185 haveOpenCL Initialize OpenCL runtime...
[ INFO:0@0.004] global ocl.cpp:1191 haveOpenCL OpenCL: found 0 platforms
OpenCL is disabled
TEST: Skip tests with tags: 'mem_6gb', 'verylong', 'debug_verylong'
Note: Google Test filter = ML_ANN_Params.ActivationFunction*
[==========] Running 5 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 5 tests from ML_ANN_Params
[ RUN ] ML_ANN_Params.ActivationFunction/0, where GetParam() = identity
[ OK ] ML_ANN_Params.ActivationFunction/0 (1540 ms)
[ RUN ] ML_ANN_Params.ActivationFunction/1, where GetParam() = sigmoid_sym
/localdisk/eplankin/libraries.performance.ipp.integrations.opencv-src/modules/ml/test/test_ann.cpp:73: Failure
The max difference between matrices "rx" and "ry" is 3.43167 at (1166, 0), which exceeds "1.19209289550781250000000000000000000e-7F", where "rx" at (1166, 0) evaluates to (1.71587), "ry" at (1166, 0) evaluates to (-1.7158), "1.19209289550781250000000000000000000e-7F" evaluates to 1.19209e-07
[ FAILED ] ML_ANN_Params.ActivationFunction/1, where GetParam() = sigmoid_sym (1887 ms)
[ RUN ] ML_ANN_Params.ActivationFunction/2, where GetParam() = gaussian
/localdisk/eplankin/libraries.performance.ipp.integrations.opencv-src/modules/ml/test/test_ann.cpp:73: Failure
The max difference between matrices "rx" and "ry" is 0.988031 at (3586, 0), which exceeds "1.19209289550781250000000000000000000e-7F", where "rx" at (3586, 0) evaluates to (0.998486), "ry" at (3586, 0) evaluates to (0.0104549), "1.19209289550781250000000000000000000e-7F" evaluates to 1.19209e-07
[ FAILED ] ML_ANN_Params.ActivationFunction/2, where GetParam() = gaussian (2180 ms)
[ RUN ] ML_ANN_Params.ActivationFunction/3, where GetParam() = relu
[ OK ] ML_ANN_Params.ActivationFunction/3 (197 ms)
[ RUN ] ML_ANN_Params.ActivationFunction/4, where GetParam() = leakyrelu
/localdisk/eplankin/libraries.performance.ipp.integrations.opencv-src/modules/ml/test/test_ann.cpp:73: Failure
The max difference between matrices "rx" and "ry" is 46.9776 at (4440, 0), which exceeds "1.19209289550781250000000000000000000e-7F", where "rx" at (4440, 0) evaluates to (46.087), "ry" at (4440, 0) evaluates to (-0.890567), "1.19209289550781250000000000000000000e-7F" evaluates to 1.19209e-07
[ FAILED ] ML_ANN_Params.ActivationFunction/4, where GetParam() = leakyrelu (1586 ms)
[----------] 5 tests from ML_ANN_Params (7390 ms total)
[----------] Global test environment tear-down
[==========] 5 tests from 1 test case ran. (7390 ms total)
[ PASSED ] 2 tests.
[ FAILED ] 3 tests, listed below:
[ FAILED ] ML_ANN_Params.ActivationFunction/1, where GetParam() = sigmoid_sym
[ FAILED ] ML_ANN_Params.ActivationFunction/2, where GetParam() = gaussian
[ FAILED ] ML_ANN_Params.ActivationFunction/4, where GetParam() = leakyrelu
3 FAILED TESTS
```
### Steps to reproduce
```
$ cmake CMakeLists.txt -DWITH_IPP=OFF -B.build
$ cd .build && make
$ ./bin/opencv_test_ml --gtest_filter=ML_ANN_Params.ActivationFunction*
```
### Issue submission checklist
- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc) | bug,optimization,category: ml | low | Critical |
2,559,989,634 | rust | ambiguous name when glob importing an enum into a block when variant has same name as enum | <!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->
related: https://github.com/rust-lang/rust/issues/102855
I tried this code:
```rust
enum En {
En
}
mod m {
use super::En;
const _ = {
use En::*;
1
};
}
```
I expected to see this happen: exact path shadows glob import
Instead, this happened: compile error:
```
Compiling playground v0.0.1 (/playground)
error[[E0659]](https://doc.rust-lang.org/nightly/error_codes/E0659.html): `En` is ambiguous
--> src/lib.rs:8:13
|
8 | use En::*;
| ^^ ambiguous name
|
= note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
note: `En` could refer to the variant imported here
--> src/lib.rs:8:13
|
8 | use En::*;
| ^^^^^
= help: consider adding an explicit import of `En` to disambiguate
note: `En` could also refer to the enum imported here
--> src/lib.rs:6:9
|
6 | use super::En;
| ^^^^^^^^^
= help: use `self::En` to refer to this enum unambiguously
error: missing type for `const` item
--> src/lib.rs:7:12
|
7 | const _ = {
| ^ help: provide a type for the constant: `: i32`
For more information about this error, try `rustc --explain E0659`.
error: could not compile `playground` (lib) due to 2 previous errors
```
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
`rustc --version --verbose`:
```
rustc 1.83.0-nightly (2bd1e894e 2024-09-26)
binary: rustc
commit-hash: 2bd1e894efde3b6be857ad345914a3b1cea51def
commit-date: 2024-09-26
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
```
| A-resolve,T-compiler,C-bug | low | Critical |
2,560,007,634 | PowerToys | Daily copy, paste and text manipulation tasks | ### Description of the new feature / enhancement
Hello, :)
_I apologize in advance if this is not the correct way to use this communication channel, as I am completely newbie to Github_
**I would like to suggest implementing a new feature:** quick and easy text manipulation shortcuts for the mouse.
This is a function that can optimize the productivity of all Windows users via Power Toys and those who need more accessibility features.
Just like the **[PopClip (MacOS)](https://www.popclip.app/)** and **[SnipDo (Windows)](https://snipdo-app.com/)** applications, it would be interesting if there was a feature which, after selecting text, quick action buttons would appear for tasks that we frequently and exhaustively do using keyboard shortcuts, such as example, CTRL+C , CTRL+V, CTRL+X, etc.
Currently, there is only one (freemium) app that does this on Windows: SnipDo. However, every month features are removed for monetization reasons (which there is nothing wrong with that). But, it would be interesting to have these same functions for free within Power Toys.
Furthermore, this feature could also be integrated into the advanced paste in future projects.
### Scenario when this would be used?
By every user. Every minute, hour and day.
### Supporting information
This is a small example of how this works through the SnipDo app:
After selecting any text, a small popup appears with shortcut options that we frequently use. | Needs-Triage | low | Minor |
2,560,051,754 | pytorch | Context manager to skip checks inside decompositions | ### 🚀 The feature, motivation and pitch
When calling a decomposition from another decomposition, we might be running checks with `torch._check` when we know that those checks are unnecessary. For eg: using `narrow` in `split_with_sizes` added about `15*N` checks for `N` number of splits, but none of them were necessary. Removing those checks made a good performance improvement as seen in https://github.com/pytorch/pytorch/pull/135728/files.
Does it make sense to have a context manager that makes `torch._check` a no-op?
cc @ezyang @chauhang @penguinwu @bobrenjc93 @SherlockNoMad @amjames
### Alternatives
_No response_
### Additional context
_No response_ | triaged,oncall: pt2,module: dynamic shapes,module: decompositions | low | Major |
2,560,056,514 | rust | rustdoc --json output format contains no doc comments | What's the right way to invoke `rustdoc` so that it outputs in JSON format but also with doc comments?
I'm doing `cargo +nightly rustdoc -- --output-format json -Z unstable-options` and the resulting JSON file has `"docs": null` for all items! 😅
Please let me know how to tell rustdoc to include doc comments 🙂
Thanks 🙏 | T-rustdoc,A-cross-crate-reexports,A-rustdoc-json,S-needs-repro,S-needs-info | low | Major |
2,560,057,547 | godot | More helpful error message for `Condition "!v.is_finite()" is true` | ### Tested versions
- Reproducible in: v4.3.stable (77dcf97d8)
### System information
Godot v4.3.stable (77dcf97d8) - Windows 10.0.22631 - GLES3 (Compatibility) - Intel(R) Iris(R) Xe Graphics (Intel Corporation; 32.0.101.5972) - 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 Threads)
### Issue description
Moving MeshInstance to an infinite or NaN coordinate causes this error
```
E 0:00:02:0077 instance_set_transform: Condition "!v.is_finite()" is true.
<C++ Source> servers/rendering/renderer_scene_cull.cpp:935 @ instance_set_transform()
```
That's great, but it's difficult to understand what does it mean. It would be better if error message read "Infinite coordinate provided to a mesh" or something like that so developers could more easily understand what happened and what do they need to look for in their code (i.e. divisions by zero)
### Steps to reproduce
1. Create a MeshInstance3D
2. Set mesh to Cube
3. Assign a new script to it
```gdscript
extends Node3D
func _ready() -> void:
self.position.x = NAN
```
### Minimal reproduction project (MRP)
N/A | enhancement,topic:rendering,usability | low | Critical |
2,560,060,310 | godot | Highlight outline jumps around on toggle visibility with flexible layout | ### Tested versions
Reproducible in 4.3-stable
### System information
Godot v4.3.stable - Pop!_OS 22.04 LTS - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 580 Series (RADV POLARIS10) - AMD Ryzen 7 7700X 8-Core Processor (16 Threads)
### Issue description
When toggling the visibility of items in a flex layout, in a way that adjusts the size of the enveloping container, the outlines of the items (initially) appear in the wrong place
### Steps to reproduce
Method A:
1. Adjust the 2D editor so the 4 Buttons are centered and big enough to see
2. shift+click all the buttons with text 'A'
3. In the Inspector, toggle CanvasItem>Visibility>visible twice
Method B:
1. Adjust the 2D editor so the 4 Buttons are centered and big enough to see
2. in the scene tree select all the buttons in the HBoxContainer
3. click the visibility icon twice
### Minimal reproduction project (MRP)
[MWE.zip](https://github.com/user-attachments/files/17215355/MWE.zip)
| bug,topic:gui | low | Minor |
2,560,064,677 | neovim | StatusLineNC, Folded, and CursorLine highlights are indistinguishable in default colorscheme | ### Problem
This can make the UI confusing, and difficult to tell what is what at a glance, especially if you have a lot of windows open and/or folded lines.
### Steps to reproduce
Here's an example with the following highlights being displayed right next to each other
1. StatusLineNC
2. Folded
3. CursorLine
<img width="1018" alt="image" src="https://github.com/user-attachments/assets/841d9aee-ecbe-4a84-bbe2-be76a715076b">
### Expected behavior
Here is the same example where the highlights are different making it easier/quicker to tell what is what at a glance:
<img width="1018" alt="image" src="https://github.com/user-attachments/assets/f5ebd4fd-fd36-4690-8f19-919be4706034">
### Nvim version (nvim -v)
NVIM v0.11.0-dev-4005+g69553f7bf5-Homebrew
### Vim (not Nvim) behaves the same?
no, vim 9.1
### Operating system/version
macOS 14.5
### Terminal name/version
kitty 0.36.4
### $TERM environment variable
xterm-kitty
### Installation
homebrew | defaults | low | Major |
2,560,091,815 | pytorch | FSDP2 equivalent of FSDP.summon_full_params contextmanager | ### 🚀 The feature, motivation and pitch
In FSDP1 there is the `FSDP.summon_full_params` [function](https://pytorch.org/docs/stable/fsdp.html#torch.distributed.fsdp.FullyShardedDataParallel.summon_full_params) for wrapping a module with a `contextmanager` within which all sharded parameters are automatically unsharded and modifications to the unsharded tensor are written back to the original shards. The FSDP2 documentation says to use the `DTensor` `full_tensor` API for this but `full_tensor` will only work on an individual tensor rather than recursively unsharding all parameters within a module. Are there plans for introducing a similar API for FSDP2? Or do you recommend any alternative approach?
### Alternatives
_No response_
### Additional context
_No response_
cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @zhaojuanmao @mrshenli @rohan-varma @chauhang | oncall: distributed,module: fsdp | low | Minor |
2,560,098,049 | rust | Tracking Issue for `inherent_str_constructors ` | <!--
Thank you for creating a tracking issue!
Tracking issues are for tracking a feature from implementation to stabilization.
Make sure to include the relevant RFC for the feature if it has one.
If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->
Feature gate: `#![feature(inherent_str_constructors)]`
This is a tracking issue for inherent `str` constructors.
### Public API
* `str::from_utf8`
* `str::from_utf8_mut`
* `str::from_utf8_unchecked`
* `str::from_utf8_unchecked_mut`
### Steps / History
<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->
- [x] ACP: https://github.com/rust-lang/libs-team/issues/398
- [ ] Implementation: #...
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR
<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.
If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:
A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->
### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.
It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->
- None yet.
[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
| T-libs-api,C-tracking-issue | low | Minor |
2,560,114,369 | rust | importing an item into the module it was defined in is described as "multiple definitions" | ### Code
```
pub struct St;
use St;
```
### Current output
```
error[E0255]: the name `St` is defined multiple times
--> src/lib.rs:2:5
|
1 | pub struct St;
| -------------- previous definition of the type `St` here
2 | use St;
| ^^ `St` reimported here
|
= note: `St` must be defined only once in the type namespace of this module
help: you can use `as` to change the binding name of the import
|
2 | use St as OtherSt;
| ++++++++++
warning: unused import: `St`
--> src/lib.rs:2:5
|
2 | use St;
| ^^
|
= note: `#[warn(unused_imports)]` on by default
```
### Desired output
```
error[E0255]: the name `St` is defined multiple times
--> src/lib.rs:2:5
|
1 | pub struct St;
| -------------- previous definition of the type `St` here
2 | use St;
| ^^ `St` reimported here
|
= note: `St` must be defined only once in the type namespace of this module
help: remove the import
|
2 | use St;
| ------
warning: unused import: `St`
--> src/lib.rs:2:5
|
2 | use St;
| ^^
|
= note: `#[warn(unused_imports)]` on by default
```
### Rationale and extra context
_No response_
### Other cases
this should also be handled for circular reimports:
```rust
pub use m::St;
mod m {
pub struct St;
use crate::St;
}
```
### Rust Version
rustc 1.83.0-nightly (2bd1e894e 2024-09-26)
binary: rustc
commit-hash: 2bd1e894efde3b6be857ad345914a3b1cea51def
commit-date: 2024-09-26
host: x86_64-unknown-linux-gnu
release: 1.83.0-nightly
LLVM version: 19.1.0
### Anything else?
_No response_ | A-diagnostics,T-compiler | low | Critical |
2,560,205,342 | PowerToys | PowerToys control panel does not save any settings | ### Microsoft PowerToys version
0.84.1
### Installation method
GitHub
### Running as admin
Yes
### Area(s) with issue?
FancyZones
### Steps to reproduce
It just says access denied. Same thing after running as admin.
### ✔️ Expected Behavior
Settings to save
### ❌ Actual Behavior
No setting seems to be saving, not just fancyzones, everything was not saving, had to edit the json file manually and it works.
### Other Software
_No response_ | Issue-Bug,Product-Settings,Product-FancyZones,Needs-Triage,Needs-Team-Response | low | Minor |
2,560,224,006 | kubernetes | [SidecarContainers] Failed to get proper phase after the node reboot | ### What happened?
If a pod has an init container with restartPolicy "Always" (sidecar), it may lose the pending phase after the node reboot and start the regular containers before initializing the init containers.
/sig node
/priority important-soon
/kind bug
This is similar to https://github.com/kubernetes/kubernetes/issues/126650, but separated as it only affects the pod with restartable init containers.
### What did you expect to happen?
After the node reboot, the remaining pod should start from the pending phase and run the init containers one by one to initialize.
### How can we reproduce it (as minimally and precisely as possible)?
1. Create and initialize the pod with an init container with "Always" container restart policy.
2. Restart the node.
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
```console
$ kubectl version
# paste output here
```
</details>
### Cloud provider
<details>
</details>
### OS version
<details>
```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
</details>
### Install tools
<details>
</details>
### Container runtime (CRI) and version (if applicable)
<details>
</details>
### Related plugins (CNI, CSI, ...) and versions (if applicable)
<details>
</details>
| kind/bug,priority/important-soon,sig/node,triage/accepted | low | Critical |
2,560,229,330 | tensorflow | Tf_lite fails to compile in v2.18.0-rc0 in Ubuntu | ### Issue type
Build/Install
### Have you reproduced the bug with TensorFlow Nightly?
Yes
### Source
source
### TensorFlow version
2.18.0-rc0
### Custom code
No
### OS platform and distribution
ubuntu 22.04, ubuntu 24.04
### Mobile device
_No response_
### Python version
3.10, 3.12
### Bazel version
6.5
### GCC/compiler version
_No response_
### CUDA/cuDNN version
-
### GPU model and memory
-
### Current behavior?
When follow the [normal instructions to build tf_lite](https://ai.google.dev/edge/litert/build/cmake_pip) as indicated, compilation fails, log is attached.
### Standalone code to reproduce the issue
```shell
Follow the normal instructions to build tf_lite as indicated here: https://ai.google.dev/edge/litert/build/cmake_pip
Compilation fails, log is attached.
```
### Relevant log output
Full log:
[ubuntu22.04.log](https://github.com/user-attachments/files/17216590/ubuntu22.04.log)
[ubuntu24.04.log](https://github.com/user-attachments/files/17216593/ubuntu24.04.log)
```
/usr/bin/ranlib libmicrokernels-prod.a
gmake[3]: Leaving directory '/tensorflow/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3.12/cmake_build'
[ 69%] Built target microkernels-prod
gmake[2]: Leaving directory '/tensorflow/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3.12/cmake_build'
gmake[1]: *** [CMakeFiles/Makefile2:1526: CMakeFiles/_pywrap_tensorflow_interpreter_wrapper.dir/rule] Error 2
gmake[1]: Leaving directory '/tensorflow/tensorflow/lite/tools/pip_package/gen/tflite_pip/python3.12/cmake_build'
gmake: *** [Makefile:208: _pywrap_tensorflow_interpreter_wrapper] Error 2
make: *** [Makefile:72: docker-build] Error 2
make: Leaving directory '/home/----/Software/tensorflow-dir/tflite_runtime/tensorflow/tensorflow/lite/tools/pip_package'
```
| stat:awaiting tensorflower,type:build/install,comp:lite,2.17,2.18.rc | low | Critical |
2,560,231,898 | tauri | [feat] [v2] [macOS] Move hidden files/folder out of DMG window's view | ### Describe the problem
This is a low priority request and is same as something discussed in electron-userland/electron-builder#1121. If users have `AppleShowAllFiles` on in Finder, the hidden files/folders in DMG window would show and be placed improperly as the following image shows.
<img width="656" alt="Screenshot 2024-10-02 04 26 49" src="https://github.com/user-attachments/assets/dcf7ccb9-bd52-4cb5-8401-d54f2f947a59">
### Describe the solution you'd like
The intuitive solution would be moving any file/folder with a name starting with a dot to a position out of DMG window by giving larger x value and y value than DMG window's width and height respectively. Electron did this by maintaining a list of hidden files/folders internally. I personally think it is good enough but I am not sure if anyone would want some customization in this. Feel free to share any use case of customization or any alternative solution.
### Alternatives considered
_No response_
### Additional context
_No response_ | type: feature request,platform: macOS | low | Minor |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.