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,797,066,899 | angular | Add link to Language Service page from the Installation page | ### Describe the problem that you experienced
It would be helpful to have a blurb somewhere on the Installation page of the documentation with a recommendation to setup the Language Service extension and a link to that page of the documentation. For new Angular developers, this is the first place they will come to learn how to setup a new project and get going. The Language Service page is way further down in the documentation and a new developer could potentially spend a very long time without this critical editor extension until they finally stumble upon that page. This should be highlighted at the very start of their journey.
### Enter the URL of the topic with the problem
https://angular.dev/installation
### Describe what you were looking for in the documentation
_No response_
### Describe the actions that led you to experience the problem
_No response_
### Describe what you want to experience that would fix the problem
_No response_
### Add a screenshot if that helps illustrate the problem
_No response_
### If this problem caused an exception or error, please paste it here
```true
```
### If the problem is browser-specific, please specify the device, OS, browser, and version
```true
```
### Provide any additional information here in as much as detail as you can
```true
``` | help wanted,good first issue,area: docs | low | Critical |
2,797,069,134 | yt-dlp | toutiao.com support | ### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [x] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field
### Checklist
- [x] I'm requesting a site-specific feature
- [x] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [x] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [x] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [x] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [x] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required
### Region
China/USA
### Example URLs
https://www.toutiao.com/video/7459390066381554239/
### Provide a description that is worded well enough to be understood
```
% yt-dlp https://www.toutiao.com/video/7459390066381554239/
[generic] Extracting URL: https://www.toutiao.com/video/7459390066381554239/
[generic] 7459390066381554239: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] 7459390066381554239: Extracting information
ERROR: Unsupported URL: https://www.toutiao.com/video/7459390066381554239/
```
### Provide verbose output that clearly demonstrates the problem
- [x] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [x] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below
### Complete Verbose Output
```shell
% yt-dlp -vU https://www.toutiao.com/video/7459390066381554239/
[debug] Command-line config: ['-vU', 'https://www.toutiao.com/video/7459390066381554239/']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version [email protected] from yt-dlp/yt-dlp [c8541f8b1] (pip)
[debug] Python 3.13.1 (CPython arm64 64bit) - macOS-15.1-arm64-arm-64bit-Mach-O (OpenSSL 3.4.0 22 Oct 2024)
[debug] exe versions: ffmpeg 7.1 (setts), ffprobe 7.1
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.12.14, mutagen-1.47.0, requests-2.32.3, sqlite3-3.48.0, urllib3-2.3.0, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: [email protected] from yt-dlp/yt-dlp
yt-dlp is up to date ([email protected] from yt-dlp/yt-dlp)
[generic] Extracting URL: https://www.toutiao.com/video/7459390066381554239/
[generic] 7459390066381554239: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] 7459390066381554239: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://www.toutiao.com/video/7459390066381554239/
Traceback (most recent call last):
File "/opt/homebrew/Cellar/yt-dlp/2025.1.15/libexec/lib/python3.13/site-packages/yt_dlp/YoutubeDL.py", line 1637, in wrapper
return func(self, *args, **kwargs)
File "/opt/homebrew/Cellar/yt-dlp/2025.1.15/libexec/lib/python3.13/site-packages/yt_dlp/YoutubeDL.py", line 1772, in __extract_info
ie_result = ie.extract(url)
File "/opt/homebrew/Cellar/yt-dlp/2025.1.15/libexec/lib/python3.13/site-packages/yt_dlp/extractor/common.py", line 742, in extract
ie_result = self._real_extract(url)
File "/opt/homebrew/Cellar/yt-dlp/2025.1.15/libexec/lib/python3.13/site-packages/yt_dlp/extractor/generic.py", line 2553, in _real_extract
raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://www.toutiao.com/video/7459390066381554239/
``` | site-enhancement,triage | low | Critical |
2,797,071,994 | ui | [bug]: Github Button Link Hierarchy | ### Describe the bug
In the main website, when trying to press github button to go to the github, only the icon is clickable, the button iself isn't.
### Affected component/components
Button
### How to reproduce
1. Go to https://ui.shadcn.com
2. Try to click on Github link, not the icon.
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
```
### System Info
```bash
-
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,797,073,663 | rust | Tracking issue for release notes of #133951: Make the wasm_c_abi future compat warning a hard error |
This issue tracks the release notes text for #133951.
### Steps
- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.
### Release notes text
The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).
````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Make the wasm_c_abi future compat warning a hard error](https://github.com/rust-lang/rust/pull/133951)
````
> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*
### Release blog section
If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*
````markdown
````
cc @bjorn3, @workingjubilee -- origin issue/PR authors and assignees for starting to draft text
| T-lang,relnotes,O-wasm,A-ABI,needs-triage,relnotes-tracking-issue | low | Critical |
2,797,082,780 | rust | Tracking issue for release notes of #134276: fully de-stabilize all custom inner attributes |
This issue tracks the release notes text for #134276.
### Steps
- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.
### Release notes text
The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).
````markdown
# Language
- [stop accepting `#![test]` and `#![rustfmt::skip]` in more places than intended](https://github.com/rust-lang/rust/pull/134276)
````
> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*
### Release blog section
If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*
````markdown
````
cc @RalfJung, @SparrowLii -- origin issue/PR authors and assignees for starting to draft text
| T-lang,relnotes,needs-triage,relnotes-tracking-issue | low | Minor |
2,797,082,806 | rust | Tracking issue for release notes of #125087: Optimize `Seek::stream_len` impl for `File` |
This issue tracks the release notes text for #125087.
### Steps
- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.
### Release notes text
The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).
````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Optimize `Seek::stream_len` impl for `File`](https://github.com/rust-lang/rust/pull/125087)
````
> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*
### Release blog section
If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*
````markdown
````
cc @tbu-, @ChrisDenton -- origin issue/PR authors and assignees for starting to draft text
| O-windows,relnotes,T-libs,O-unix,needs-triage,O-wasi,O-hermit,O-solid,relnotes-tracking-issue | low | Minor |
2,797,085,119 | react-native | some TouchableOpacity isn't working on IOS 0.76 | ### Description
After upgrading from 0.73 to 0.76, I found that some TouchableOpacity could not be clicked, so I made a minimize buggy demo code, which just depend on react-native, no 3rd libs
### Steps to reproduce
1. npx @react-native-community/cli@latest init TouchableOpacityDemo
2. cd ios && bundle exec pod install
3. modify App.tsx
```
import * as React from "react";
import {
StyleSheet,
TouchableOpacity,
ScrollView,
Alert,
View,
Text,
Image,
} from "react-native";
const styles = StyleSheet.create({
text: {
color: "#FFF",
fontSize: 16,
},
icons: {
display: "flex",
flexDirection: "row",
justifyContent: "space-evenly",
paddingVertical: 5,
alignSelf: "stretch",
backgroundColor: "#FFF",
},
title: { fontSize: 18, flexWrap: "wrap", color: "#000" },
});
const App = ({ }) => {
return (
<ScrollView
style={{ flex: 1, backgroundColor: '#808000' }}
contentContainerStyle={{
flexDirection: "row",
flexWrap: "wrap",
justifyContent: "space-evenly",
}}
>
<View
style={{
width: 150,
display: "flex",
justifyContent: "space-between",
alignItems: "center",
marginTop: 10,
}}
>
<TouchableOpacity style={{ width: 150, height: "100%", backgroundColor: '#CC0' }} onPress={() => {
Alert.alert('cover click');
}}>
<Image source={{ uri: 'https://placehold.jp/3d4070/ffffff/150x150.png' }} style={{ height: 150 }} />
</TouchableOpacity>
<View style={styles.icons}>
<TouchableOpacity style={{ width: 20, height: "100%", backgroundColor: '#C00' }} onPress={() => {
Alert.alert('A click');
}}><Text>A</Text></TouchableOpacity>
<TouchableOpacity style={{ width: 20, height: "100%", backgroundColor: '#C00' }} onPress={() => {
Alert.alert('B click');
}}><Text>B</Text></TouchableOpacity>
<TouchableOpacity style={{ width: 20, height: "100%", backgroundColor: '#C00' }} onPress={() => {
Alert.alert('C click');
}}><Text>C</Text></TouchableOpacity>
</View>
</View>
</ScrollView>
);
};
export default App;
```
4. yarn ios
5. you can see the image can click but the buttons A/B/C can not click
6. if change `height: "100%"` to `height: 150` in line 47 the buttons A/B/C can click again
### React Native Version
0.76.6
### Affected Platforms
Runtime - iOS
### Output of `npx react-native info`
```text
System:
OS: macOS 15.2
CPU: (10) arm64 Apple M4
Memory: 139.52 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.11.0
path: ~/.nvm/versions/node/v22.11.0/bin/node
Yarn:
version: 4.6.0
path: ~/.nvm/versions/node/v22.11.0/bin/yarn
npm:
version: 10.9.0
path: ~/.nvm/versions/node/v22.11.0/bin/npm
Watchman:
version: 2024.12.02.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.16.2
path: /opt/homebrew/lib/ruby/gems/3.4.0/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.2
- iOS 18.2
- macOS 15.2
- tvOS 18.2
- visionOS 2.2
- watchOS 11.2
Android SDK: Not Found
IDEs:
Android Studio: 2024.2 AI-242.23726.103.2422.12816248
Xcode:
version: 16.2/16C5032a
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.10
path: /Users/iwater/.sdkman/candidates/java/current/bin/javac
Ruby:
version: 3.4.1
path: /opt/homebrew/opt/ruby/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 15.0.1
wanted: 15.0.1
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.76.6
wanted: 0.76.6
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
```
### Stacktrace or Logs
```text
no
```
### Reproducer
https://github.com/iwater/TouchableOpacityDemo
### Screenshots and Videos
 | Platform: iOS,Issue: Author Provided Repro,Resolution: PR Submitted,Component: TouchableOpacity,Type: New Architecture | low | Critical |
2,797,091,394 | vscode | Allow scm.diffDecorationsGutterWidth to take values between 1 and 9, not just 1 and 5 | <!-- ⚠️⚠️ 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. -->
`scm.diffDecorationsGutterWidth` currently takes values between 1 and 5.
I would like it to take values between 1 and 9 (I like my gutters **fat**). | feature-request,ux,scm | low | Minor |
2,797,091,771 | rust | Tracking Issue for raw-dylib on ELF | This is a tracking issue for raw-dylib on ELF (no RFC, extending [RFC 2627](https://rust-lang.github.io/rfcs/2627-raw-dylib-kind.html))
The feature gate for the issue is `#![feature(raw_dylib_elf)]`.
`raw-dylib` on ELF links against a generated stub shared object, allowing linking against libraries that are not present on the host system, for example for cross-compilation scenarios.
### 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.
-->
- [x] Initial implementation (#135695)
- [ ] Wider Testing
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])
[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/main/nightly-style-procedure.md
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide
### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->
- [ ] How to deal with symbol versioning?
### Implementation history
<!--
Include a list of all the PRs that were involved in implementing the feature.
-->
- Initial implementation: #135695
| T-compiler,C-tracking-issue | low | Critical |
2,797,098,134 | yt-dlp | [XiaoHongShu] add H.265/HEVC extraction | ### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [x] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field
### Checklist
- [x] I'm requesting a site-specific feature
- [x] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [x] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [x] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [x] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [x] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required
### Region
Global
### Example URLs
https://www.xiaohongshu.com/explore/676ccedd000000000900d4c7?xsec_token=ABl8MasLC9VFpJwsLb3pHTYMetZWyCyL29364bw6B3sKM=&xsec_source=pc_feed
### Provide a description that is worded well enough to be understood
The platform provides H.265/HEVC encodes for popular videos (example URL is a random video from the home page that has an H.265/HEVC encode available at "https://sns-video-ak.xhscdn.com/stream/1/110/4/01e76cc9b322080a010370039401096085_4.mp4", but yt-dlp currently only finds/extracts the H.264/AVC video stream.
audio stream seems to be the same VBR 56 kbps 44.1 Khz HE-AAC audio track that's used for the H.264/AVC video stream.
### Provide verbose output that clearly demonstrates the problem
- [x] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [x] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [x] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below
### Complete Verbose Output
```shell
R:\>yt-dlp -vU -F https://www.xiaohongshu.com/explore/676ccedd000000000900d4c7?xsec_token=ABl8MasLC9VFpJwsLb3pHTYMetZWyCyL29364bw6B3sKM=&xsec_source=pc_feed
[debug] Command-line config: ['-vU', '-F', 'https://www.xiaohongshu.com/explore/676ccedd000000000900d4c7?xsec_token=ABl8MasLC9VFpJwsLb3pHTYMetZWyCyL29364bw6B3sKM=']
[debug] Portable config "C:\Program Files (x86)\yt-dlp\yt-dlp.conf": ['-S', 'res,vcodec:av1']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version [email protected] from yt-dlp/yt-dlp [c8541f8b1] (win_exe)
[debug] Python 3.10.11 (CPython AMD64 64bit) - Windows-10-10.0.22631-SP0 (OpenSSL 1.1.1t 7 Feb 2023)
[debug] exe versions: ffmpeg git-2024-10-01-7151081-ffmpeg-windows-build-helpers (fdk,setts)
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.12.14, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32.3, sqlite3-3.40.1, urllib3-2.3.0, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: [email protected] from yt-dlp/yt-dlp
yt-dlp is up to date ([email protected] from yt-dlp/yt-dlp)
[XiaoHongShu] Extracting URL: https://www.xiaohongshu.com/explore/676ccedd000000000900d4c7?xsec_token=ABl8MasLC9VFpJwsLb3pHTYMetZWyCyL29364bw6B3sKM=
[XiaoHongShu] 676ccedd000000000900d4c7: Downloading webpage
[debug] Sort order given by user: res, vcodec:av1
[debug] Formats sorted by: hasvid, ie_pref, res, vcodec:av1(11), lang, quality, fps, hdr:12(7), channels, acodec, size, br, asr, proto, vext, aext, hasaud, source, id
[info] Available formats for 676ccedd000000000900d4c7:
ID EXT RESOLUTION FPS CH │ FILESIZE TBR PROTO │ VCODEC VBR ACODEC ABR
───────────────────────────────────────────────────────────────────────────────────
0 mp4 720x1280 30 2 │ 37.54MiB 3804724k http │ h264 3742971k aac 56116k
1 mp4 720x1280 30 2 │ 37.54MiB 3804724k http │ h264 3742971k aac 56116k
"xsec_source" non è riconosciuto come comando interno o esterno,
un programma eseguibile o un file batch.
``` | site-enhancement,triage | low | Critical |
2,797,104,222 | PowerToys | Enhancements to Screen Corners, Touchpad Gestures, Touchscreen Actions, Bluetooth Communications Detail, App Power Consumption Analysis, and Customizable Taskbar | ### Description of the new feature / enhancement
**Screen Corners Shortcuts:** Implement hot corners functionality similar to what is available in Linux and macOS. For example, moving the pointer to the upper left corner would trigger the same shortcut as the Windows + Tab combination, displaying all open apps in a mosaic view for easy selection. Another example would be the lower right corner, which would show the desktop.
**Touchpad Gestures:** Enable configurable multi-finger gestures on the touchpad. In Windows 11, currently, it’s not possible to configure actions for 2, 3, or 4 finger swipes, only allowing cross movement. In macOS, this is customizable, and in Linux, there are several useful gestures available, such as circular movements for scrolling.
**Touchscreen Actions:** Introduce similar multi-finger gestures and shortcuts for the touchscreen that are available for the touchpad with 2, 3, and 4 fingers. Additional new gestures could be added, similar to iOS/iPadOS, for quickly closing applications or displaying all open ones depending on the starting area of the movement.
**Bluetooth Communications Detail:** Create an app to display detailed information about Bluetooth communications, including signal strength, power consumption, and audio codec in use. This would be extremely useful for ensuring proper device configuration and identifying issues, similar to what is available in macOS developer tools by using Alt-click on the Bluetooth icon, or in Linux via CLI.
**App Power Consumption Analysis:** Develop an app that details power consumption in milliwatts (mW) per app and the total consumption. This would be immensely helpful in identifying resource-hungry or poorly optimized applications, such as those using the dedicated GPU instead of the CPU. This app could be integrated with Process Explorer and potentially allow limiting app power consumption, similar to Linux's Powertop.
**Customizable Taskbar:** Allow for a highly customizable taskbar to simplify the workflow and maintain a clean workspace, similar to what is available on Windows Server. Users should have the option to remove unnecessary features like news, social media, and other distractions that consume resources. Additionally, enable the taskbar to be positioned at the top, sides, or bottom of the screen. This flexibility is particularly useful for users managing multiple remote desktop sessions, preventing confusion by differentiating taskbar positions. Also, in tablet mode, it would be beneficial to have the option to position the taskbar above the on-screen keyboard, a feature that has disappeared in Windows 11. An option to enable a "Focus Mode" that removes all added features intended for domestic use and allows full customization of the taskbar position would be incredibly useful.
### Scenario when this would be used?
These enhancements would be invaluable for power users who rely on efficient navigation and workflow management.
- **Screen Corners Shortcuts:** Enhancing productivity by quickly accessing open applications or the desktop without needing to use keyboard shortcuts or other manual steps.
- **Touchpad Gestures:** Allowing for a more seamless and customizable user experience, making multitasking more intuitive and efficient, especially for users transitioning from macOS or Linux who are accustomed to these gestures.
- **Touchscreen Actions:** Improving the usability of touchscreen devices by offering more intuitive controls and gestures similar to those on iOS/iPadOS, which can speed up tasks and provide a more integrated experience.
- **Bluetooth Communications Detail:** Assisting in the proper configuration of Bluetooth devices by providing detailed information about signal strength, power consumption, and audio codec, helping users identify and solve connectivity issues.
- **App Power Consumption Analysis:** Enabling users to monitor and manage the power consumption of individual applications, identifying resource-heavy or poorly optimized software, and potentially allowing users to limit power usage, extending the battery life of portable devices.
- **Customizable Taskbar:** Streamlining workflows by allowing users to customize the taskbar to remove distractions and save resources, such as news and social media, which are often unnecessary in a professional environment. Providing the ability to place the taskbar at the top, sides, or bottom of the screen is extremely useful for users who manage multiple remote desktop sessions. This prevents confusion by enabling distinct taskbar placements for each session. In tablet mode, restoring the option to position the taskbar above the on-screen keyboard would greatly improve usability. Adding a "Focus Mode" would further enhance productivity by eliminating distractions and allowing users to concentrate on their tasks.
### Supporting information
Thank you very much for considering my suggestions. I truly adore PowerToys and have been using them for years. They have been an essential part of my workflow, greatly enhancing my productivity and user experience. I am excited about the potential improvements and am grateful for the continuous innovation and dedication to making these tools even more powerful and versatile. | Needs-Triage | low | Minor |
2,797,123,821 | pytorch | The latest PyTorch XPU wheel 2.7.0.dev20250117+xpu does not work on Windows | Steps:
```
# This installs 2.7.0.dev20250117+xpu
pip install torch --index-url https://download.pytorch.org/whl/nightly/xpu
python -c 'import torch;print(torch.__version__)'
```
Result:
```
OSError: [WinError 126] The specified module could not be found. Error loading "C:\.venv\lib\site-packages\torch\lib\shm.dll" or one of its dependencies.
```
The last known wheel that worked is `2.7.0.dev20250110+xpu`:
```
# This installs 2.7.0.dev20250110+xpu
pip install torch --index-url https://download.pytorch.org/whl/nightly/xpu
python -c 'import torch;print(torch.__version__)'
```
Result:
```
2.7.0.dev20250110+xpu
```
cc @seemethere @malfet @osalpekar @atalman @peterjc123 @mszhanyi @skyline75489 @nbcsm @iremyux @Blackhex @gujinghui @EikanWang @fengyuan14 @guangyey | module: binaries,module: windows,triaged,module: xpu | low | Critical |
2,797,130,359 | deno | Deno panic while using ```Object.prototype.set``` and ```Deno.Command``` together | Version: Deno 2.1.5
Hello,
I want to report a Deno panic caused by using ```Object.prototype.set``` and ```Deno.Command``` together. It can reproduced by running the following code snippet:
```javascript
var data = "data";
Object.prototype.set = function (value) {
data = value;
};
(async function () {
let cmd = new Deno.Command("pwd");
let { code, stdout, stderr } = await cmd.output();
})();
```
Deno output:
```
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: windows x86_64
Version: 2.1.5
Args: ["C:\\Users\\.deno\\bin\\deno.exe", "run", ".\\panic.js"]
thread 'main' panicked at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\deno_core-0.330.0\error.rs:305:7:
Custom error class must have a builder registered: Uncaught TypeError: Invalid property descriptor. Cannot both specify accessors and a value or writable attribute, #<Object>
stack backtrace:
0: 0x7ff668296d25 - node_api_get_module_file_name
1: 0x7ff666c53bd9 - uv_mutex_destroy
2: 0x7ff6682723d7 - node_api_get_module_file_name
3: 0x7ff66829a5e1 - node_api_get_module_file_name
4: 0x7ff66829a14d - node_api_get_module_file_name
5: 0x7ff666acd19f - uv_mutex_destroy
6: 0x7ff66829b10b - node_api_get_module_file_name
7: 0x7ff66829afb6 - node_api_get_module_file_name
8: 0x7ff66829af0f - node_api_get_module_file_name
9: 0x7ff66829aef6 - node_api_get_module_file_name
10: 0x7ff669d8caa4 - CrashForExceptionInNonABICompliantCodeRange
11: 0x7ff669d91c67 - CrashForExceptionInNonABICompliantCodeRange
12: 0x7ff666de2591 - uv_mutex_destroy
13: 0x7ff66780dfc7 - node_api_get_module_file_name
14: 0x7ff66780d4b7 - node_api_get_module_file_name
15: 0x1ed3170f686 - <unknown>
16: 0x1ed3170d85e - <unknown>
17: 0x1ed3170d85e - <unknown>
18: 0x1ed3170d85e - <unknown>
19: 0x1ed3170d85e - <unknown>
20: 0x1ed3170d85e - <unknown>
21: 0x1ed3175368b - <unknown>
22: 0x1ed3170b45c - <unknown>
23: 0x1ed3170afaf - <unknown>
24: 0x7ff6687b5208 - node_api_get_module_file_name
25: 0x7ff6687b5de5 - node_api_get_module_file_name
26: 0x7ff6687b5f43 - node_api_get_module_file_name
27: 0x7ff6687bda41 - node_api_get_module_file_name
28: 0x7ff6687bd190 - node_api_get_module_file_name
29: 0x7ff6687bcb0f - node_api_get_module_file_name
30: 0x7ff6687b699c - node_api_get_module_file_name
31: 0x7ff66863d3ad - node_api_get_module_file_name
32: 0x7ff668629080 - node_api_get_module_file_name
33: 0x7ff666eb7c90 - uv_mutex_destroy
34: 0x7ff666192ab3 - uv_mutex_destroy
35: 0x7ff666a9eb3c - uv_mutex_destroy
36: 0x7ff666a9cbae - uv_mutex_destroy
37: 0x7ff666a3618c - uv_mutex_destroy
38: 0x7ff666ac87fc - uv_mutex_destroy
39: 0x7ff6662ed16b - uv_mutex_destroy
40: 0x7ff666b77fa5 - uv_mutex_destroy
41: 0x7ff666499528 - uv_mutex_destroy
42: 0x7ff666acf421 - uv_mutex_destroy
43: 0x7ff6662c0cc6 - uv_mutex_destroy
44: 0x7ff666b78087 - uv_mutex_destroy
45: 0x7ff669d2753c - CrashForExceptionInNonABICompliantCodeRange
46: 0x7ff9a9abe8d7 - BaseThreadInitThunk
47: 0x7ff9aa41fbcc - RtlUserThreadStart
```
Platform:
Microsoft Windows NT 10.0.26100.0 x64 | windows | low | Critical |
2,797,135,025 | rust | Type inference issues with well specified trait function call | <!--
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.
-->
While debugging a recent build failure in diesel I noticed that type inference fails in situation where the type is fully specified. I've build the following minimal example for this:
```rust
#[derive(Debug)]
struct Error;
trait FromSql<ST, DB>: Sized {
fn from_sql(bytes: &[u8]) -> Result<Self, Error>;
}
struct UuidST;
struct Integer;
struct Pg;
#[derive(Debug, PartialEq)]
struct Uuid;
struct OtherType;
// remove this rather unrelated impl to fix the compilation
impl PartialEq<OtherType> for Uuid {
fn eq(&self, other: &OtherType) -> bool {
false
}
}
impl FromSql<UuidST, Pg> for Uuid {
fn from_sql(bytes: &[u8]) -> Result<Self, Error> {
todo!()
}
}
impl FromSql<Integer, Pg> for i32 {
fn from_sql(bytes: &[u8]) -> Result<Self, Error> {
todo!()
}
}
fn main() {
let input = &[];
let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
assert_eq!(Uuid, out);
}
```
This fails to compile with the following error:
```
error[[E0790]](https://doc.rust-lang.org/nightly/error_codes/E0790.html): cannot call associated function on trait without specifying the corresponding `impl` type
--> src/main.rs:43:15
|
7 | fn from_sql(bytes: &[u8]) -> Result<Self, Error>;
| ------------------------------------------------- `FromSql::from_sql` defined here
...
43 | let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot call associated function of trait
|
help: use a fully-qualified path to one of the available implementations
|
43 - let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
43 + let out = <Uuid as FromSql<UuidST, Pg>>::from_sql(input).unwrap();
|
43 - let out = FromSql::<UuidST, Pg>::from_sql(input).unwrap();
43 + let out = <i32 as FromSql<UuidST, Pg>>::from_sql(input).unwrap();
|
```
This seems to be caused by the additional `PartialEq` implementation that breaks inferring the type of the `out` variable. For me it looks strange that rustc cannot infer that there is only a single possible impl that fulfills the given constraints, so it should be possible to infer the correct type here.
(Also even if that's desired behavior the suggestion is definitively off, as the second variant (that with `i32 as FromSql<UuidST, Pg>` would result in a compilation error.
Playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=1a20f58b8678382f922f0006217bbf60
Related: https://github.com/uuid-rs/uuid/issues/787
`rustc --version --verbose`:
```
Build using the Nightly version: 1.86.0-nightly
(2025-01-17 6067b36314ab5eb2eb47)
```
| A-diagnostics,T-compiler,A-inference,A-suggestion-diagnostics | low | Critical |
2,797,140,920 | next.js | dynamic route, dynamicIO, mdx, notFound => NEXT_HTTP_ERROR_FALLBACK;404 | ### Link to the code that reproduces this issue
https://github.com/volfadar/next-bug
### To Reproduce
1. bun install
2. bun dev
3. go to "http://localhost:3000/lecture/marketing/intro"
### Current vs. Expected behavior
Simply, it should not throw an error `NEXT_HTTP_ERROR_FALLBACK;404` because I already have a `not-found.tsx`.
### Provide environment information
```bash
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Home Single Language
Available memory (MB): 16087
Available CPU cores: 8
Binaries:
Node: 20.11.1
npm: 10.2.4
Yarn: 1.22.22
pnpm: 9.0.2
Relevant Packages:
next: 15.2.0-canary.15 // Latest available version is detected (15.2.0-canary.15).
eslint-config-next: N/A
react: 19.0.0
react-dom: 19.0.0
typescript: 5.7.3
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
dynamicIO, Turbopack, TypeScript, Markdown (MDX)
### Which stage(s) are affected? (Select all that apply)
next dev (local)
### Additional context
_No response_ | TypeScript,Turbopack,Markdown (MDX),dynamicIO | low | Critical |
2,797,140,990 | godot | Follow system theme causes config file churn | ### Tested versions
4.3.stable.arch_linux
### System information
Godot v4.3.stable unknown - Arch Linux #1 SMP PREEMPT_DYNAMIC Fri, 10 Jan 2025 00:39:41 +0000 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3080 (nvidia; 565.77) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)
### Issue description
I have godot's theme set to "Follow System Theme". I also commit `~/.config/godot/editor_settings-4.3.tres` in my dotfiles, to synchronize changes across devices.
The issue is that whenever I toggle my system theme, godot changes a bunch of fields in the config file. For ease of use across machines, the config should reflect more persistent options, not things that frequently change due to outside influence like the system theme changing. That is, it would be nice if the config just stored "Use System Theme" as a setting instead of changing all these each time the system theme changes:
```diff
-interface/theme/preset = "Light"
-interface/theme/base_color = Color(0.9, 0.9, 0.9, 1)
-interface/theme/accent_color = Color(0.18, 0.5, 1, 1)
-interface/theme/contrast = -0.06
+interface/theme/base_color = Color(0.21, 0.24, 0.29, 1)
+interface/theme/accent_color = Color(0.44, 0.73, 0.98, 1)
+interface/theme/contrast = 0.3
filesystem/import/blender/blender_path = "/usr/bin//blender"
filesystem/import/blender/rpc_port = 0
-text_editor/theme/highlighting/symbol_color = Color(0, 0, 0.61, 1)
-text_editor/theme/highlighting/keyword_color = Color(0.9, 0.135, 0.51, 1)
-text_editor/theme/highlighting/control_flow_keyword_color = Color(0.743, 0.12, 0.8, 1)
-text_editor/theme/highlighting/base_type_color = Color(0, 0.6, 0.2, 1)
-text_editor/theme/highlighting/engine_type_color = Color(0.11, 0.55, 0.4, 1)
-text_editor/theme/highlighting/user_type_color = Color(0.18, 0.45, 0.4, 1)
-text_editor/theme/highlighting/comment_color = Color(0.08, 0.08, 0.08, 0.5)
-text_editor/theme/highlighting/doc_comment_color = Color(0.15, 0.15, 0.4, 0.7)
-text_editor/theme/highlighting/string_color = Color(0.6, 0.42, 0, 1)
-text_editor/theme/highlighting/background_color = Color(1, 1, 1, 1)
-text_editor/theme/highlighting/completion_background_color = Color(0.981, 0.981, 0.981, 1)
-text_editor/theme/highlighting/completion_selected_color = Color(0, 0, 0, 0.07)
-text_editor/theme/highlighting/completion_existing_color = Color(0, 0, 0, 0.14)
-text_editor/theme/highlighting/completion_scroll_color = Color(0, 0, 0, 0.29)
-text_editor/theme/highlighting/completion_scroll_hovered_color = Color(0, 0, 0, 0.4)
-text_editor/theme/highlighting/completion_font_color = Color(0.225, 0.225, 0.225, 1)
-text_editor/theme/highlighting/text_color = Color(0.225, 0.225, 0.225, 1)
-text_editor/theme/highlighting/line_number_color = Color(0.225, 0.225, 0.225, 0.5)
-text_editor/theme/highlighting/safe_line_number_color = Color(0, 0.4, 0, 0.75)
-text_editor/theme/highlighting/caret_color = Color(0, 0, 0, 1)
-text_editor/theme/highlighting/caret_background_color = Color(1, 1, 1, 1)
-text_editor/theme/highlighting/selection_color = Color(0.18, 0.5, 1, 0.4)
-text_editor/theme/highlighting/brace_mismatch_color = Color(1, 0.08, 0, 1)
-text_editor/theme/highlighting/current_line_color = Color(0, 0, 0, 0.07)
-text_editor/theme/highlighting/line_length_guideline_color = Color(0.981, 0.981, 0.981, 1)
-text_editor/theme/highlighting/word_highlighted_color = Color(0, 0, 0, 0.07)
-text_editor/theme/highlighting/number_color = Color(0, 0.55, 0.28, 1)
-text_editor/theme/highlighting/function_color = Color(0, 0.225, 0.9, 1)
-text_editor/theme/highlighting/member_variable_color = Color(0, 0.4, 0.68, 1)
-text_editor/theme/highlighting/mark_color = Color(0.8, 0.22, 0.22, 0.3)
-text_editor/theme/highlighting/breakpoint_color = Color(1, 0.27, 0.2, 1)
-text_editor/theme/highlighting/code_folding_color = Color(0, 0, 0, 0.27)
-text_editor/theme/highlighting/search_result_color = Color(0, 0, 0, 0.07)
-text_editor/theme/highlighting/search_result_border_color = Color(0, 0.4, 1, 0.38)
+text_editor/theme/highlighting/symbol_color = Color(0.67, 0.79, 1, 1)
+text_editor/theme/highlighting/keyword_color = Color(1, 0.44, 0.52, 1)
+text_editor/theme/highlighting/control_flow_keyword_color = Color(1, 0.55, 0.8, 1)
+text_editor/theme/highlighting/base_type_color = Color(0.26, 1, 0.76, 1)
+text_editor/theme/highlighting/engine_type_color = Color(0.56, 1, 0.86, 1)
+text_editor/theme/highlighting/user_type_color = Color(0.78, 1, 0.93, 1)
+text_editor/theme/highlighting/comment_color = Color(0.8025, 0.81, 0.8225, 0.5)
+text_editor/theme/highlighting/doc_comment_color = Color(0.6, 0.7, 0.8, 0.8)
+text_editor/theme/highlighting/string_color = Color(1, 0.93, 0.63, 1)
+text_editor/theme/highlighting/background_color = Color(0.1155, 0.132, 0.1595, 1)
+text_editor/theme/highlighting/completion_background_color = Color(0.21, 0.24, 0.29, 1)
+text_editor/theme/highlighting/completion_selected_color = Color(1, 1, 1, 0.07)
+text_editor/theme/highlighting/completion_existing_color = Color(1, 1, 1, 0.14)
+text_editor/theme/highlighting/completion_font_color = Color(0.8025, 0.81, 0.8225, 1)
+text_editor/theme/highlighting/text_color = Color(0.8025, 0.81, 0.8225, 1)
+text_editor/theme/highlighting/line_number_color = Color(0.8025, 0.81, 0.8225, 0.5)
+text_editor/theme/highlighting/safe_line_number_color = Color(0.8025, 0.972, 0.8225, 0.75)
+text_editor/theme/highlighting/caret_color = Color(1, 1, 1, 1)
+text_editor/theme/highlighting/selection_color = Color(0.44, 0.73, 0.98, 0.4)
+text_editor/theme/highlighting/brace_mismatch_color = Color(1, 0.47, 0.42, 1)
+text_editor/theme/highlighting/current_line_color = Color(1, 1, 1, 0.07)
+text_editor/theme/highlighting/line_length_guideline_color = Color(0.21, 0.24, 0.29, 1)
+text_editor/theme/highlighting/word_highlighted_color = Color(1, 1, 1, 0.07)
+text_editor/theme/highlighting/number_color = Color(0.63, 1, 0.88, 1)
+text_editor/theme/highlighting/function_color = Color(0.34, 0.7, 1, 1)
+text_editor/theme/highlighting/member_variable_color = Color(0.736, 0.88, 1, 1)
+text_editor/theme/highlighting/mark_color = Color(1, 0.47, 0.42, 0.3)
+text_editor/theme/highlighting/breakpoint_color = Color(1, 0.47, 0.42, 1)
+text_editor/theme/highlighting/code_folding_color = Color(1, 1, 1, 0.27)
+text_editor/theme/highlighting/search_result_color = Color(1, 1, 1, 0.07)
text_editor/behavior/files/trim_trailing_whitespace_on_save = true
text_editor/behavior/files/auto_reload_scripts_on_external_change = true
run/platforms/linuxbsd/prefer_wayland = true
```
### Steps to reproduce
1. Open godot and set "Follow System Theme" in the editor settings.
2. Commit `~/.config/godot` in a git repository.
3. Change your system theme from light->dark
4. Run `git diff` in the repository
### Minimal reproduction project (MRP)
N/A | enhancement,discussion,topic:editor,usability | low | Minor |
2,797,143,370 | transformers | Issue: Error with _eos_token_tensor when using Generator with GenerationMixin | ### System Info
e-readability-summarization/src/inference$ python run_2.py
Traceback (most recent call last):
File "/home/surenoobster/Documents/project/src/inference/run_2.py", line 87, in <module>
output = generator.generate(
^^^^^^^^^^^^^^^^^^^
File "/home/surenoobster/anaconda3/lib/python3.12/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/home/surenoobster/Documents/project/src/inference/generation_2.py", line 572, in generate
stopping_criteria = self.model._get_stopping_criteria(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/surenoobster/anaconda3/lib/python3.12/site-packages/transformers/generation/utils.py", line 1126, in _get_stopping_criteria
if generation_config._eos_token_tensor is not None:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'GenerationConfig' object has no attribute '_eos_token_tensor'
### Who can help?
_No response_
### Information
- [ ] The official example scripts
- [x] My own modified scripts
### Tasks
- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)
### Reproduction
I'm not able to get it , getting problem with device
### Expected behavior
The Generator should initialize the required token tensors correctly to ensure compatibility with GenerationMixin and avoid errors. | bug | low | Critical |
2,797,148,695 | flutter | Assertion failed: (reconstituted == accumulator), function setFixup64, file OutputFile.cpp | ### Steps to reproduce
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Assertion failed: (reconstituted == accumulator), function setFixup64, file OutputFile.cpp, line 2975.
Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)
### Expected results
The Aplication should run in iOS on flutter run command
### Actual results
Getting ErrorL
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Assertion failed: (reconstituted == accumulator), function setFixup64, file OutputFile.cpp, line 2975.
Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)
### Code sample
<details open><summary>Code sample</summary>
```dart
[Paste your code here]
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[Paste your output here]
```
</details>
| waiting for customer response,in triage | low | Critical |
2,797,157,007 | godot | Project manager window dissappear when launching from Hyprland, but works fine from VSCode | ### Tested versions
Reproductible in 7b1ed520b and #99119
Not reproductible in `4.3` branch
### System information
Godot v4.4.beta (7b1ed520b) - CachyOS Linux #1 SMP PREEMPT_DYNAMIC Thu, 09 Jan 2025 20:57:06 +0000 on Wayland - X11 display driver, Multi-window, 1 monitor - Vulkan (Forward+) - integrated AMD Radeon Graphics (RADV GFX1103_R1) (Radeon 780M) - AMD Eng Sample (16 threads) (Ryzen 7 8845HS)
### Issue description
Recently I tried to compile the #99119 PR on my new mini PC with CachyOS and Hyprland. Compilation went successful, but for some reason project manager window just dissappear after the loading screen (even when launching it from the Editor by executing the binary with the `--editor` flag and pressing the "Quit to Project List" button). Then I tried to compile `master` (which is currently `7b1ed52`) and the result was the same. The same issue applies to precompiled binary of the [4.4 Beta 1](https://godotengine.org/article/dev-snapshot-godot-4-4-beta-1/#downloads).
Then I tried to debug it from VSCode. I created `launch.json` file, launched the executable and, surprisingly, the project manager appears on my screen. Then I tried to execute it from the GNOME shell, which also was successful.
Also, I figured out that enabling "Prefer Wayland" in the Editor settings fixes the bug.
For me, it looks more like a Hyprland and/or XWayland issue, but why is it reproductible only in 4.4 then? And why can it be so easily fixed by just launching the Godot Project Manager from VSCode? Maybe it also can be fixed by Godot itself?
P.S. I recompiled again, but this time it doesn't work correctly even from VSCode.
### Steps to reproduce
1. Download or compile 4.4
2. Launch it NOT from VSCode.
### Minimal reproduction project (MRP)
No project needed. | bug,platform:linuxbsd,needs testing,regression | low | Critical |
2,797,163,217 | deno | deno --init serve: `http://0.0.0.0:8000` does not work with Safari | Version: Deno 2.1.6 (and 2.1.4)
I tried to create and run a new project on my ARM Mac:
`deno --init serve`
When I pasted `http://0.0.0.0:8000/` into Safari, I just got "about:blank".
I discovered it works correctly on Chrome.
Surprisingly, `http://127.0.0.1:8000` (and `localhost`) work on Safari. Would it make more sense to tell people that? | bug,good first issue,serve | low | Minor |
2,797,165,384 | next.js | Browser back button fails after navigation with URL anchor fragment | ### Link to the code that reproduces this issue
https://github.com/sgarrity/nextjs-anchor-link-testcase
### To Reproduce
1. Run the simple create-next-app example at https://github.com/sgarrity/nextjs-anchor-link-testcase
2. Click on the "Anchor Example" link (or manually add a `#example` fragment at the end of the home page URL
3. Click the "Go to Foobar" link (to /foobar)
4. Click the browser Back button
### Current vs. Expected behavior
Note how the URL shows the home URL with the fragment (`http://localhost:3000/#anchor`) but the Foobar (`/foobar`) page is still rendered in the browser, not the home page as intended.
### Provide environment information
```bash
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.2.0: Fri Dec 6 19:01:59 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6000
Available memory (MB): 32768
Available CPU cores: 10
Binaries:
Node: 20.11.1
npm: 10.2.4
Yarn: 1.22.22
pnpm: 9.15.4
Relevant Packages:
next: 15.1.5 // Latest available version is detected (15.1.5).
eslint-config-next: N/A
react: 19.0.0
react-dom: 19.0.0
typescript: N/A
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
Not sure, create-next-app
### Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
### Additional context
If I replace the example anchor fragment link with a next/link `Link` component instead of a stock <a> tag, the browser back button works as intended. However, someone could always end up on a page with a URL fragment already there from an external link beyond your controle. | create-next-app | low | Minor |
2,797,168,509 | godot | Godot Editor stopped with exit code: 134 | ### Tested versions
- Reproducible in: 4.4beta1, 4.4dev7 and probably previous versions.
- I don't know if it's a problem specific to version 4.4, because I'm using it since the first alpha came out and in the meantime I switched to a different OS. I don't remember if it was happening even before on Windows 11.
### System information
Godot v4.4.beta1 - Ubuntu 24.04.1 LTS 24.04 on Wayland - X11 display driver, Multi-window, 2 monitors - OpenGL 3 (Compatibility) - Mesa Intel(R) Xe Graphics (TGL GT2) - 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 threads)
### Issue description
My editor has been crashing all of a sudden for a while now. I don't know what's causing it or what could be causing it, it seems pretty random.
I don't even know what version it started with and if it started only when I started using the Linux version (I switched to Ubuntu 24.04 about a month ago).
This is what the terminal prints to me:
```
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.4.beta1.official (d33da79d3f8fe84be2521d25b9ba8e440cf25a88)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x45320) [0x7d5820845320] (??:0)
[2] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x4c0c050] (??:0)
[3] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x1c924c1] (??:0)
[4] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x4cbc60d] (??:0)
[5] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x46c7f64] (??:0)
[6] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x2904acc] (??:0)
[7] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x51aaee] (??:0)
[8] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x4208d3] (??:0)
[9] /lib/x86_64-linux-gnu/libc.so.6(+0x2a1ca) [0x7d582082a1ca] (??:0)
[10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x8b) [0x7d582082a28b] (??:0)
[11] /home/stef/Desktop/Dev/Godot/Godot_v4.4-beta1_linux.x86_64() [0x44347a] (??:0)
-- END OF BACKTRACE --
================================================================
Aborted (core dumped)
Godot Editor stopped with exit code: 134
```
As you can see the error isn't telling me anything.
### Steps to reproduce
I don't know the steps to reproduce, it happens randomly while I'm in the Godot editor.
### Minimal reproduction project (MRP)
I don't think it's releated to the project. Maybe to the version or the OS. | bug,crash | low | Critical |
2,797,173,596 | ant-design | DatePicker does not allow manual clear | ### Reproduction link
[https://ant.design/components/date-picker](https://ant.design/components/date-picker)
### Steps to reproduce
- Choose a date
- Select the input date string and try to remove it with the remove key
### What is expected?
- `onChange` should be triggered
- It should work exactly behave like pressing the clear button
### What is actually happening?
- `onChange` in NOT triggered
- it is not possible to remove the value manually
- the date is re-appearing after removing it manually
https://github.com/user-attachments/assets/19ec0c05-d6a6-4aa1-aad4-725e22626770
| Environment | Info |
| --- | --- |
| antd | 5.23.1 |
| React | 18.2.0 |
| System | Windows 11 |
| Browser | Latest Chrome |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | unconfirmed | low | Minor |
2,797,189,207 | yt-dlp | YT m4a audio DASH stream download corruption | ### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [x] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field
### Checklist
- [x] I'm reporting that yt-dlp is broken on a **supported** site
- [x] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [x] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [x] I've checked that all URLs and arguments with special characters are [properly quoted or escaped](https://github.com/yt-dlp/yt-dlp/wiki/FAQ#video-url-contains-an-ampersand--and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command)
- [x] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [x] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [x] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required
### Region
US
### Provide a description that is worded well enough to be understood
For a certain period of time after a YouTube live stream ends, the m4a audio is only available as a DASH stream. It eventually gets processed into HTTP. This means it's not really possible to provide a url with a DASH stream. It needs to be caught by monitoring a live stream and downloading the m4a audio DASH stream right after it ends. I don't have a url that currently repros.
The recent regression (which could be a YT change) is that such downloads end up exactly half the expected length and when played (e.g. VLC) are silent.
### Provide verbose output that clearly demonstrates the problem
- [x] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [x] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below
### Complete Verbose Output
```shell
[debug] Command-line config: ['-vU']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version [email protected] from yt-dlp/yt-dlp-nightly-builds [164368610] (pip)
[debug] Python 3.13.1 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 3.0.15 3 Sep 2024)
[debug] exe versions: ffmpeg 5.1.2-full_build-www.gyan.dev (setts), ffprobe 5.1.2-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, mutagen-1.47.0, requests-2.32.3, sqlite3-3.45.3, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version: [email protected] from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date ([email protected] from yt-dlp/yt-dlp-nightly-builds)
``` | external issue,site-bug,site:youtube,core:downloader | medium | Critical |
2,797,190,333 | godot | Metal rendering driver fails to run on Apple's software Metal implementation (paravirtual device) | ### Tested versions
- Reproducible in: 4.4.beta https://github.com/godotengine/godot/commit/7b1ed520bdcca21d36e25e2094802b9b33dae2c6
### System information
GitHub Actions
### Issue description
The Metal rendering driver fails to run on Apple's software Metal implementation (paravirtual device):
```
Metal 3.1 - Forward+ - Using Device #0: Apple - Apple Paravirtual device (Apple5)
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[AppleParavirtDevice newArgumentEncoderWithLayout:]: unrecognized selector sent to instance 0x15186e800'
*** First throw call stack:
(
0 CoreFoundation 0x000000019c1722cc __exceptionPreprocess + 176
1 libobjc.A.dylib 0x000000019bc56158 objc_exception_throw + 60
2 CoreFoundation 0x000000019c224568 -[NSObject(NSObject) __retain_OA] + 0
3 AppleParavirtGPUMetalIOGPUFamily 0x0000000114fb0f5c doUncompressedBlit + 11180
4 Metal 0x00000001a643cec4 -[_MTLDevice newArgumentEncoderWithArguments:structType:] + 136
5 godot.macos.editor.universal 0x00000001048b74b0 _ZN9DirAccess15_create_builtinI13DirAccessUnixEE3RefIS_Ev + 3011780
6 godot.macos.editor.universal 0x0000000107161a68 _ZN17RendererSceneCull8Instance18dependency_deletedERK3RIDP17DependencyTracker + 165848
7 godot.macos.editor.universal 0x000000010730b378 _ZN22RendererCanvasRenderRD22_create_material_funcsEPN10RendererRD15MaterialStorage10ShaderDataE + 98132
8 godot.macos.editor.universal 0x0000000107db8fd8 _ZNK6Object22can_translate_messagesEv + 265940
9 godot.macos.editor.universal 0x0000000107db9bb4 _ZNK6Object22can_translate_messagesEv + 268976
10 godot.macos.editor.universal 0x000000010777b3ec _ZN7ClassDB7creatorIN9core_bind14EngineDebuggerEEEP6Objectb + 35228
11 godot.macos.editor.universal 0x000000010777b7d0 _ZN7ClassDB7creatorIN9core_bind14EngineDebuggerEEEP6Objectb + 36224
12 libsystem_pthread.dylib 0x000000019c01df94 _pthread_start + 136
13 libsystem_pthread.dylib 0x000000019c018d34 thread_start + 8
)
libc++abi: terminating due to uncaught exception of type NSException
```
This is most likely because the GPU exposed via paravirtualization is only Apple5, but we need a newer GPU. See also https://github.com/JuliaGPU/Metal.jl/issues/309. While it's unlikely we can cater to the Apple5 GPU, we should exit with a proper error message (one that refers to the paravirtualized device not being supported) instead of crashing.
For context, I'm looking to run the Metal renderer on CI so we can check for visual regressions. I have this working on Vulkan/OpenGL on Linux already using llvmpipe, and on D3D12 on Windows using WARP (the official software implementation of Direct3D).
This is the command line I'm using on CI as part of https://github.com/Calinou/godot/tree/ci-check-visual-regressions:
```bash
godot --audio-driver Dummy --path tests/visual_regressions --rendering-driver metal --rendering-method forward_plus -- --save-results
```
cc @stuartcarnie
### Steps to reproduce
- Try running a Godot project with `--rendering-driver metal` on a headless platform with no GPU (e.g. GitHub Actions). Do not use the `--headless` flag at the same time.
### Minimal reproduction project (MRP)
N/A | bug,platform:macos,topic:rendering,crash | low | Critical |
2,797,193,615 | deno | Add support for zstd response encoding | Deno currently supports gzip and brotli response encoding/compression. It would be great if it could also support zstd - with zstd > br > gz being the preference. 73% of browsers now support zstd.
https://caniuse.com/zstd | web,serve | low | Minor |
2,797,196,938 | deno | Support compression on text/event-stream | Currently Deno [compresses responses](https://docs.deno.com/deploy/api/compression/) based on [this database](https://github.com/jshttp/mime-db/blob/master/db.json) of content types. It doesn't include text/event-stream, which is very commonly used for Server-Sent Events (which is really just a normal http response with text/string content of a specific format).
Ive successfully compressed event-stream responses with Caddy with its normal [compression encoding directive](https://caddyserver.com/docs/caddyfile/directives/encode). Nothing fancy needs to happen to make this work.
It would be great if Deno could support this as well, so that we don't need to implement it in the application or use a proxy like Caddy. | suggestion,help wanted,serve | low | Minor |
2,797,198,316 | rust | DW_AT_name is always (indirect string, offset: 0x0) | <!--
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.
-->
I tried this code:
```
~/tmp main
$ git clone --branch polkavm-test-data --depth 1 https://github.com/paritytech/polkavm.git
Cloning into 'polkavm'...
remote: Enumerating objects: 973, done.
remote: Counting objects: 100% (973/973), done.
remote: Compressing objects: 100% (558/558), done.
remote: Total 973 (delta 398), reused 755 (delta 377), pack-reused 0 (from 0)
Receiving objects: 100% (973/973), 26.85 MiB | 25.41 MiB/s, done.
Resolving deltas: 100% (398/398), done.
~/tmp main
$ cd polkavm
~/tmp/polkavm polkavm-test-data
$ cargo b -p polkavm-test-data &> build.log.txt || echo FAILED
~/tmp/polkavm polkavm-test-data*
$ rz-bin -d ./guest-programs/target/riscv64emac-unknown-none-polkavm/no-lto/test-blob|grep DW_AT_name|tail
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
DW_AT_name [DW_FORM_strp] : (indirect string, .debug_str+0x0): cap
$ ls crates/polkavm-linker/*.json
crates/polkavm-linker/riscv32emac-unknown-none-polkavm.json
crates/polkavm-linker/riscv64emac-unknown-none-polkavm.json
```
Remarks:
- An issue resembling of this: https://groups.google.com/g/llvm-dev/c/gwF2kzODNzc/m/gJPon-QYAgAJ
- The original issue: https://github.com/paritytech/polkavm/issues/208
- Wanted to query upstream because the issue is so weird after tweaking this many weeks.
I expected to see this happen: names in DWARF should point to different strings.
Instead, this happened: all point to the same string at offset zero.
### 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.75.0 (82e1608df 2023-12-21)
binary: rustc
commit-hash: 82e1608dfa6e0b5569232559e3d385fea5a93112
commit-date: 2023-12-21
host: x86_64-unknown-linux-gnu
release: 1.75.0
LLVM version: 17.0.6
```
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>
```
<backtrace>
```
</p>
</details>
| A-debuginfo,T-compiler,C-bug,requires-custom-config,S-needs-repro | low | Critical |
2,797,202,380 | electron | dialog openFile does not select multiple directories in Linux, when using 'openDirectory' and 'multiSelections' | ### Preflight Checklist
- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.
### Electron Version
34.0.0
### What operating system(s) are you using?
Ubuntu
### Operating System Version
Ubuntu 24.04
### What arch are you using?
x64
### Last Known Working Electron version
_No response_
### Expected Behavior
When opening a dialog with `dialog.showOpenDialog(mainWindow, {properties: 'openDirectory','multiSelections})`, after selecting multiple folders, the result.filePaths array should have multiple strings, each representing the full path for each selected folder.
### Actual Behavior
When opening a dialog with `dialog.showOpenDialog(mainWindow, {properties: 'openDirectory','multiSelections})`, the dialog opens and allows to select multiple folders, but the result object (result.filePaths) only contains one element (sometimes the first or the last selection)
### Testcase Gist URL
_No response_
### Additional Information
_No response_ | platform/linux,bug :beetle:,component/dialog,status/confirmed,34-x-y | low | Critical |
2,797,209,113 | vscode | Terminal Info box overlaps with terminal icon |
Type: <b>Bug</b>
Terminal Info box overlaps with terminal icon
When you over over the terminal name the terminal info box overlaps which in making it impossible to right click the terminal
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 5600G with Radeon Graphics (12 x 3893)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.83GB (17.15GB free)|
|Process Argv|--crash-reporter-id b5795235-6152-413c-a73a-a09ec6ec7ceb|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (76)</summary>
Extension|Author (truncated)|Version
---|---|---
better-comments|aar|3.0.2
a-file-icon-vscode|ato|2.0.1
ruff|cha|2025.2.0
vscode-innosetup|cho|1.9.3
githistory|don|0.6.20
python-environment-manager|don|1.2.7
python-extension-pack|don|1.7.0
vscode-html-css|ecm|2.0.12
prettier-vscode|esb|11.0.0
codespaces|Git|1.17.3
copilot|Git|1.257.0
copilot-chat|Git|0.23.2
remotehub|Git|0.64.0
vscode-github-actions|git|0.27.0
vscode-pull-request-github|Git|0.102.0
vscode-test-explorer|hbe|2.22.1
mc-datapack|HuJ|0.0.5
nbpreviewer|jit|1.2.2
vsc-python-indent|Kev|1.19.0
vscord|Leo|5.2.13
mcjson|Lev|0.4.1
vscode-python-test-adapter|lit|0.8.2
mgcb-editor|man|0.0.6
replit|mas|0.0.3
vscode-docker|ms-|1.29.3
csdevkit|ms-|1.15.34
csharp|ms-|2.61.28
vscode-dotnet-runtime|ms-|2.2.5
black-formatter|ms-|2024.4.0
debugpy|ms-|2024.14.0
isort|ms-|2023.10.1
pylint|ms-|2024.0.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2024.11.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
remote-containers|ms-|0.394.0
remote-ssh|ms-|0.116.1
remote-ssh-edit|ms-|0.87.0
remote-wsl|ms-|0.88.5
vscode-remote-extensionpack|ms-|0.26.0
azure-repos|ms-|0.40.0
cmake-tools|ms-|1.19.52
cpptools|ms-|1.23.3
cpptools-extension-pack|ms-|1.3.0
makefile-tools|ms-|0.11.13
remote-explorer|ms-|0.4.3
remote-repositories|ms-|0.42.0
remote-server|ms-|1.5.2
test-adapter-converter|ms-|0.2.1
vscode-typescript-next|ms-|5.8.20250117
vsliveshare|ms-|1.0.5948
autodocstring|njp|0.6.1
cold-python-theme|npa|1.12.0
pico-w-go|pau|4.2.1
git-log--graph|phi|0.1.23
monogame|r88|0.0.2
fabric8-analytics|red|0.9.5
java|red|1.38.0
vscode-yaml|red|1.15.0
hacknet-vscode|Sma|1.3.1
mcscript|Ste|0.0.3
cmake|twx|0.0.17
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-dependency|vsc|0.24.1
vscode-java-pack|vsc|0.29.0
vscode-java-test|vsc|0.43.0
vscode-maven|vsc|0.44.0
JavaScriptSnippets|xab|1.8.0
material-theme|zhu|3.17.7
(13 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
390bf810:31215807
6074i472:31201624
dwoutputs:31217127
```
</details>
<!-- generated by issue reporter --> | bug,terminal-tabs | low | Critical |
2,797,214,852 | godot | Canvas Items Stretch Scale Mode breaks Unicode Fonts | ### Tested versions
Reproducible in 4.3dev
### System information
Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 32.0.15.6070) - Intel(R) Core(TM) Ultra 7 155H (22 Threads)
### Issue description
Some unicode text doesn't render when you fullscreen or when you change the content scale factor and if you have `display/window/stretch/mode` set to `canvas_items`.
I'm providing a simple self-contained reproducible below. I basically just have a button with two play symbols `▶️▶️` and a font size of 18 pts that when you toggle fullscreen the 2nd play button will disappear.
When you go back to Windowed mode, it will appear again, no issues.
Display resolution tested: 2560x1600
Game target hud/window size: 1920x1200
Font size of Unicode text: 18 pts
**Project settings stretch mode**: `canvas_items`
### Steps to reproduce
N/A (see below, press toggle fullscreen in example)
### Minimal reproduction project (MRP)
Here is a zip of the self-contained tscn file I made to repro it as explained above.
[unicode_test.zip](https://github.com/user-attachments/files/18466210/unicode_test.zip)
NOTE: Be sure to change project settings stretch mode to `canvas_items`. | bug,topic:gui | low | Minor |
2,797,215,927 | pytorch | Pytorch matmul for nested 4D tensors in jagged layout doesn't work | ### 🐛 Describe the bug
Why this code doesn't work, even though is suggested to use the jagged layout:
```python
x = torch.nested.nested_tensor([torch.randn(4, 100, 16),
torch.randn(4, 150, 16)], layout=torch.jagged)
y = torch.nested.nested_tensor([torch.randn(4, 16, 100),
torch.randn(4, 16, 150)], layout=torch.jagged)
v = torch.matmul(x, y)
```
reporting this error:
```bash
RuntimeError: matmul(): not supported between inputs of shapes (2, 4, j1, 16) and torch.Size([2, 4, 16, j2])
```
Instead with the strided layout works perfectly?
The "j1" and "j2" suggests a wrong arrangement of the tensors?
Thank you to everyone!
### Versions
PyTorch version: 2.6.0+cu124
Is debug build: False
CUDA used to build PyTorch: 12.4
OS: Ubuntu 24.04.1 LTS (x86_64)
GCC version: (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.39
Python version: 3.9.21 (main, Dec 4 2024, 08:53:34) [GCC 13.2.0] (64-bit runtime)
Versions of relevant libraries:
[pip3] numpy==2.0.2
[pip3] nvidia-cublas-cu12==12.4.5.8
[pip3] nvidia-cuda-cupti-cu12==12.4.127
[pip3] nvidia-cuda-nvrtc-cu12==12.4.127
[pip3] nvidia-cuda-runtime-cu12==12.4.127
[pip3] nvidia-cudnn-cu12==9.1.0.70
[pip3] nvidia-cufft-cu12==11.2.1.3
[pip3] nvidia-curand-cu12==10.3.5.147
[pip3] nvidia-cusolver-cu12==11.6.1.9
[pip3] nvidia-cusparse-cu12==12.3.1.170
[pip3] nvidia-cusparselt-cu12==0.6.2
[pip3] nvidia-nccl-cu12==2.21.5
[pip3] nvidia-nvjitlink-cu12==12.4.127
[pip3] nvidia-nvtx-cu12==12.4.127
[pip3] pytorch-lightning==2.5.0.post0
[pip3] torch==2.6.0+cu124
[pip3] torchmetrics==1.6.1
[pip3] triton==3.2.0
[conda] Could not collect
cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ | triaged,module: nestedtensor | low | Critical |
2,797,222,120 | flutter | Different deeplinking url between onGenerateInitialRoutes and onGenerateRoute | ### Steps to reproduce
1. Run the code sample
2. Run this command to test deeplink.
```shell
adb shell 'am start -a android.intent.action.VIEW \
-c android.intent.category.BROWSABLE \
-d "https://example.com/test"' \
com.example.test
```
3. Note the printed value of `onGenerateRoute` method
4. Stop the app
5. Run `flutter logs`
6. Run this command again
```shell
adb shell 'am start -a android.intent.action.VIEW \
-c android.intent.category.BROWSABLE \
-d "https://example.com/test"' \
com.example.test
```
7. Note the printed value by `onGenerateInitialRoutes` method
### Expected results
The two printed values should be the same
### Actual results
The two values are different. `onGenerateInitialRoutes` keeps all the url `https://example.com/test` while `onGenerateRoute` keeps only the path `/test`.
### Code sample
<details open><summary>main.dart</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) {
final route = MaterialPageRoute(builder: (context) => Text('Page'));
return MaterialApp(
title: 'Example',
onGenerateRoute: (settings) {
print(settings.name);
return route;
},
onGenerateInitialRoutes: (intitialRoute) {
print(intitialRoute);
return [route];
},
);
}
}
```
</details>
<details open><summary>AndroidManifest.xml</summary>
```xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
<application
android:label="test"
android:name="${applicationName}"
android:icon="@mipmap/ic_launcher">
<activity
android:name=".MainActivity"
android:exported="true"
android:launchMode="singleTop"
android:taskAffinity=""
android:theme="@style/LaunchTheme"
android:configChanges="orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode"
android:hardwareAccelerated="true"
android:windowSoftInputMode="adjustResize">
<!-- Specifies an Android theme to apply to this Activity as soon as
the Android process has started. This theme is visible to the user
while the Flutter UI initializes. After that, this theme continues
to determine the Window background behind the Flutter UI. -->
<meta-data
android:name="io.flutter.embedding.android.NormalTheme"
android:resource="@style/NormalTheme"
/>
<intent-filter>
<action android:name="android.intent.action.MAIN"/>
<category android:name="android.intent.category.LAUNCHER"/>
</intent-filter>
<intent-filter android:autoVerify="true">
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="https" android:host="example.com" />
</intent-filter>
</activity>
<!-- Don't delete the meta-data below.
This is used by the Flutter tool to generate GeneratedPluginRegistrant.java -->
<meta-data
android:name="flutterEmbedding"
android:value="2" />
</application>
<!-- Required to query activities that can process text, see:
https://developer.android.com/training/package-visibility and
https://developer.android.com/reference/android/content/Intent#ACTION_PROCESS_TEXT.
In particular, this is used by the Flutter engine in io.flutter.plugin.text.ProcessTextPlugin. -->
<queries>
<intent>
<action android:name="android.intent.action.PROCESS_TEXT"/>
<data android:mimeType="text/plain"/>
</intent>
</queries>
</manifest>
```
</details>
### Flutter Version
Flutter version 3.28.0-0.1.pre on channel beta
| framework,f: routes,has reproducible steps,P3,team-framework,triaged-framework,found in release: 3.27,found in release: 3.28 | low | Minor |
2,797,235,963 | bitcoin | `generateblock` RPC Not Collecting Transaction Fees | ### Is there an existing issue for this?
- [x] I have searched the existing issues
### Current behaviour
The `generateblock` RPC does not properly collect transaction fees when creating a block. Instead of including the fees in the block reward, the block is created with only the block subsidy, leaving out the fees from transactions included in the block.
### Expected behaviour
The block reward should include both the block subsidy and the transaction fees from all transactions included in the block.
### Steps to reproduce
1. Start a Bitcoin Core node in regtest mode.
2. Generate 101 blocks to fund a wallet.
3. Create a transaction with a fee.
4. Call the `generateblock` RPC with the transaction above.
5. Inspect the resulting block to confirm that the block reward does not include the fee.
### Relevant log output
```
$ bitcoin-cli -regtest getblock 05fe640f818d46b9ba931d8f4179562a0d042008abe4b9ed98072d0bca449f30 2`
```
```json
{
"hash": "05fe640f818d46b9ba931d8f4179562a0d042008abe4b9ed98072d0bca449f30",
"confirmations": 1,
"height": 102,
"version": 536870912,
"versionHex": "20000000",
"merkleroot": "ac0b08a969181b07d5d08a1dedce2aeeea2d30f050b837cd4a90b73846875ecc",
"time": 1737237217,
"mediantime": 1737237198,
"nonce": 5,
"bits": "207fffff",
"difficulty": 4.656542373906925e-10,
"chainwork": "00000000000000000000000000000000000000000000000000000000000000ce",
"nTx": 2,
"previousblockhash": "38a851e21e26dc54159198e8eda06c0fb94debb1316dd504b74bb5114f9273fe",
"strippedsize": 295,
"size": 440,
"weight": 1325,
"tx": [
{
"txid": "065d28a4a15b90fc052b613e5db7540f1e5164159ca17fe88f27cfdb857c811d",
"hash": "ad545fbff90d4ddf126dc835bec6f50fc51a7e72c6b6c9f16bf240e464d68810",
"version": 2,
"size": 168,
"vsize": 141,
"weight": 564,
"locktime": 0,
"vin": [
{
"coinbase": "016600",
"txinwitness": [
"0000000000000000000000000000000000000000000000000000000000000000"
],
"sequence": 4294967295
}
],
"vout": [
{
"value": 50.00000000,
"n": 0,
"scriptPubKey": {
"asm": "0 a41424b6995beeaef7cbc9a4ebcf91b71793983d",
"desc": "addr(bcrt1q5s2zfd5et0h2aa7texjwhnu3kute8xpaqgz39r)#qxc0s854",
"hex": "0014a41424b6995beeaef7cbc9a4ebcf91b71793983d",
"address": "bcrt1q5s2zfd5et0h2aa7texjwhnu3kute8xpaqgz39r",
"type": "witness_v0_keyhash"
}
},
{
"value": 0.00000000,
"n": 1,
"scriptPubKey": {
"asm": "OP_RETURN aa21a9ed3dde4089261cfff17418209ef46ed64df4d49543df0daeafc6fc41ce09766229",
"desc": "raw(6a24aa21a9ed3dde4089261cfff17418209ef46ed64df4d49543df0daeafc6fc41ce09766229)#hu88gsq4",
"hex": "6a24aa21a9ed3dde4089261cfff17418209ef46ed64df4d49543df0daeafc6fc41ce09766229",
"type": "nulldata"
}
}
],
"hex": "020000000001010000000000000000000000000000000000000000000000000000000000000000ffffffff03016600ffffffff0200f2052a01000000160014a41424b6995beeaef7cbc9a4ebcf91b71793983d0000000000000000266a24aa21a9ed3dde4089261cfff17418209ef46ed64df4d49543df0daeafc6fc41ce097662290120000000000000000000000000000000000000000000000000000000000000000000000000"
},
{
"txid": "f66ffdec54562ec07aac05c2c25d91937a0059ffebf802705be31f59be76f3e9",
"hash": "567df936509935ee19841e9b717668cb6d419eeaba41f9c05ab0351a56c3293f",
"version": 2,
"size": 191,
"vsize": 110,
"weight": 437,
"locktime": 0,
"vin": [
{
"txid": "f5dc14e8b10b94b038ce9d6a789a12e3428e5acfd07de7ea461762f6c23f267e",
"vout": 0,
"scriptSig": {
"asm": "",
"hex": ""
},
"txinwitness": [
"304402206b532fdf2ca4111872a8c8c322ab68e21e079253862c3c95cf86d18efcdb143d022039514e377cbac97c3ec1459aec7c9584a56c1c527588600c0435483c7b96535c01",
"03fc3c5d0caa493055f57d5f3098b42555543a5219519ab90a22b20ddea49f1515"
],
"sequence": 4294967293
}
],
"vout": [
{
"value": 39.99998900,
"n": 0,
"scriptPubKey": {
"asm": "0 a41424b6995beeaef7cbc9a4ebcf91b71793983d",
"desc": "addr(bcrt1q5s2zfd5et0h2aa7texjwhnu3kute8xpaqgz39r)#qxc0s854",
"hex": "0014a41424b6995beeaef7cbc9a4ebcf91b71793983d",
"address": "bcrt1q5s2zfd5et0h2aa7texjwhnu3kute8xpaqgz39r",
"type": "witness_v0_keyhash"
}
}
],
"fee": 10.00001100,
"hex": "020000000001017e263fc2f6621746eae77dd0cf5a8e42e3129a786a9dce38b0940bb1e814dcf50000000000fdffffff01b4236bee00000000160014a41424b6995beeaef7cbc9a4ebcf91b71793983d0247304402206b532fdf2ca4111872a8c8c322ab68e21e079253862c3c95cf86d18efcdb143d022039514e377cbac97c3ec1459aec7c9584a56c1c527588600c0435483c7b96535c012103fc3c5d0caa493055f57d5f3098b42555543a5219519ab90a22b20ddea49f151500000000"
}
]
}
```
### How did you obtain Bitcoin Core
Compiled from source
### What version of Bitcoin Core are you using?
Bitcoin Core daemon version v28.99.0-ae69fc37e4ff
### Operating system and version
Ubuntu 24.04.1 LTS
### Machine specifications
_No response_ | Tests | low | Minor |
2,797,284,725 | yt-dlp | shiey.com website support | ### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE
- [x] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field
### Checklist
- [x] I'm reporting a new site support request
- [x] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [x] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [x] I've checked that none of provided URLs [violate any copyrights](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#is-the-website-primarily-used-for-piracy) or contain any [DRM](https://en.wikipedia.org/wiki/Digital_rights_management) to the best of my knowledge
- [x] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [x] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [x] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and am willing to share it if required
### Region
Cyprus
### Example URLs
https://www.shiey.com/videos/v/sneak-mission-to-modern-nuclear-bunker-complex
https://www.shiey.com/videos
https://www.shiey.com/videos/not-on-youtube
### Provide a description that is worded well enough to be understood
Add support for Shiey, a very famous YouTuber that YouTube hates and deletes all his videos. Maybe his website will be shut down one day... It's important to be able to download all these videos.
_(Also, they are very calming for some...!)_
Please and thank you.
### Provide verbose output that clearly demonstrates the problem
- [x] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [x] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below
### Complete Verbose Output
```shell
% yt-dlp -vU https://www.shiey.com/videos/v/sneak-mission-to-modern-nuclear-bunker-complex
[debug] Command-line config: ['-vU', 'https://www.shiey.com/videos/v/sneak-mission-to-modern-nuclear-bunker-complex']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version [email protected] from yt-dlp/yt-dlp [c8541f8b1] (pip)
[debug] Python 3.13.1 (CPython arm64 64bit) - macOS-15.3-arm64-arm-64bit-Mach-O (OpenSSL 3.4.0 22 Oct 2024)
[debug] exe versions: ffmpeg 7.1 (setts), ffprobe 7.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.12.14, mutagen-1.47.0, requests-2.32.3, sqlite3-3.48.0, urllib3-2.3.0, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: [email protected] from yt-dlp/yt-dlp
yt-dlp is up to date ([email protected] from yt-dlp/yt-dlp)
[generic] Extracting URL: https://www.shiey.com/videos/v/sneak-mission-to-modern-nuclear-bunker-complex
[generic] sneak-mission-to-modern-nuclear-bunker-complex: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] sneak-mission-to-modern-nuclear-bunker-complex: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://www.shiey.com/videos/v/sneak-mission-to-modern-nuclear-bunker-complex
Traceback (most recent call last):
File "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/YoutubeDL.py", line 1637, in wrapper
return func(self, *args, **kwargs)
File "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/YoutubeDL.py", line 1772, in __extract_info
ie_result = ie.extract(url)
File "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/extractor/common.py", line 742, in extract
ie_result = self._real_extract(url)
File "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/extractor/generic.py", line 2553, in _real_extract
raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://www.shiey.com/videos/v/sneak-mission-to-modern-nuclear-bunker-complex
``` | site-request | low | Critical |
2,797,293,153 | ollama | Downloading models slowing down the whole internet network | ### What is the issue?
I noticed that whenever I am downloading a model through `ollama run <model-name>` the internet slows down significantly, not only on the device downloading the model, but also over my network.
I am wondering if this issue is due to an issue in my network, or something due to an issue in the software itself.
### OS
Linux
### GPU
Nvidia
### CPU
Intel
### Ollama version
0.5.5 | bug | low | Major |
2,797,304,948 | godot | [4.4] SpriteFrames Editor, FPS display is incomplete | ### Tested versions
Godot 4.4 dev 4 - Godot 4.4 beta 1
### System information
Godot v4.4.beta (7b1ed520b) - Windows 10 - Multi-window
### Issue description
### Steps to reproduce
new resource, SpriteFrames
switch the bottom panel [SpriteFrames]
change fps
### Minimal reproduction project (MRP)
null | bug,topic:editor,needs testing,regression,topic:animation | low | Minor |
2,797,304,974 | storybook | [Bug]: Upgrade fails with `npx storybook@latest upgrade` | ### Describe the bug
Trying to upgrade from `v8.4.7` to `v8.5.0` and get this error. Something is wrong with dependecnies. There is already closed similar issue (#29169).
```bash
$ npx storybook@latest upgrade
WARN An issue occurred while trying to find dependencies metadata using npm.
╭───────────────────────────────────────────────────────────────╮
│ │
│ Upgrading Storybook from version 0.0.0 to version 8.5.0.. │
│ │
╰───────────────────────────────────────────────────────────────╯
info Checking for upgrade blockers...
No blockers found.
info Updating dependencies in package.json..
Installing dependencies...
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: @storybook/[email protected]
npm ERR! node_modules/@storybook/react
npm ERR! dev @storybook/react@"^8.5.0" from the root project
npm ERR! @storybook/react@"8.4.7" from @storybook/[email protected]
npm ERR! node_modules/@storybook/react-vite
npm ERR! dev @storybook/react-vite@"^8.5.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev @storybook/react@"^8.5.0" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @storybook/[email protected]
npm ERR! node_modules/@storybook/test
npm ERR! peerOptional @storybook/test@"8.5.0" from @storybook/[email protected]
npm ERR! node_modules/@storybook/react
npm ERR! dev @storybook/react@"^8.5.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
```
### Reproduction link
https://stackblitz.com/edit/vitejs-vite-izegxbtn
### Reproduction steps
_No response_
### System
```bash
$ npx storybook@latest info
Storybook Environment Info:
System:
OS: Windows 11 10.0.26100
CPU: (24) x64 AMD Ryzen 9 3900XT 12-Core Processor
Binaries:
Node: 22.10.0 - C:\Program Files\nodejs\node.EXE
npm: 9.7.2 - C:\Program Files\nodejs\npm.CMD <----- active
Browsers:
Edge: Chromium (131.0.2903.86)
npmPackages:
@storybook/addon-essentials: ^8.4.7 => 8.4.7
@storybook/addon-interactions: ^8.4.7 => 8.4.7
@storybook/addon-onboarding: ^8.4.7 => 8.4.7
@storybook/blocks: ^8.4.7 => 8.4.7
@storybook/react: ^8.4.7 => 8.4.7
@storybook/react-vite: ^8.4.7 => 8.4.7
@storybook/test: ^8.4.7 => 8.4.7
eslint-plugin-storybook: ^0.11.0 => 0.11.0
storybook: ^8.4.7 => 8.4.7
```
### Additional context
_No response_ | bug,npm,sev:S2,upgrade:8.5 | low | Critical |
2,797,310,504 | vscode | When opening the terminal (default: powershell), VScode Insider crashes. |
Type: <b>Bug</b>
When opening the terminal (default: powershell), VScode Insider crashes.
VScode 1.96.4 (stable available in the Windows App Store) does not have this problem. I am reporting this so that this problem does not spread to the stable version as has happened other times when I failed to report bugs in non-stable versions.
VS Code version: Code - Insiders 1.97.0-insider (c594d55bae90276d174cea4ddf2901694d4ebb3e, 2025-01-14T05:04:07.371Z)
OS version: Windows_NT x64 10.0.19045
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz (4 x 2494)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: unavailable_off<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: unavailable_off<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.88GB (3.49GB free)|
|Process Argv|--crash-reporter-id fb9a1b5c-0944-436c-87e8-516ed48c0fe2|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (22)</summary>
Extension|Author (truncated)|Version
---|---|---
laravel-extra-intellisense|ami|0.7.1
vscode-intelephense-client|bme|1.12.6
devdb|dam|2.0.1
intelli-php-vscode|DEV|0.12.15062
profiler-php-vscode|DEV|1.55.16685
copilot|Git|1.257.1319
copilot-chat|Git|0.24.2025011702
geminicodeassist|goo|2.24.0
vscode-docker|ms-|1.29.3
vscode-dotnet-runtime|ms-|2.2.5
debugpy|ms-|2024.15.2025011702
python|ms-|2024.23.2025011501
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2024.11.0
remote-ssh|ms-|0.116.1
remote-ssh-edit|ms-|0.87.0
remote-wsl|ms-|0.88.5
vscode-remote-extensionpack|ms-|0.26.0
cordova-tools|msj|2.7.0
autodocstring|njp|0.6.1
vscode-gradle|vsc|3.16.2024111106
php-debug|xde|1.35.0
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vscod805cf:30301675
vsaa593:30376534
py29gd2263:31024238
vscaac:30438845
c4g48928:30535728
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupyter:31046869
2f103344:31071589
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
c3hdf307:31184662
6074i472:31201624
dwoutputs:31217127
8did9651:31218798
```
</details>
<!-- generated by issue reporter --> | info-needed,terminal | low | Critical |
2,797,316,640 | godot | RenderingServer::environment_set_fog_depth isn't exposed to the Godot API | ### Tested versions
4.4-dev7
### System information
Godot v4.4.dev7 - Windows 10 (build 19045) - Single-window, 1 monitor - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4050 Laptop GPU (NVIDIA; 32.0.15.6070) - 13th Gen Intel(R) Core(TM) i5-13500HX (20 threads)
### Issue description
I'm using RenderingServer to handle an Environment in my game instead of using the Resource directly.
I use depth fog, so I was confused on how to set the `fog_depth_end` and `fog_depth_begin` properties inside RenderingServer.
I couldn't find it, so I looked inside environment.h to see what it was doing.
```cpp
void Environment::_update_fog_depth() {
RS::get_singleton()->environment_set_fog_depth(
environment,
fog_depth_curve,
fog_depth_begin,
fog_depth_end);
}
```
It uses ```environment_set_fog_depth```, which isn't exposed, making it impossible to set fog depth by using RenderingServer, making what I need to do impossible.
### Steps to reproduce
Search documentation for environment_set_fog_depth
https://docs.godotengine.org/en/latest/classes/class_renderingserver.html
See it isn't exposed
### Minimal reproduction project (MRP)
n/a | feature proposal,topic:rendering,topic:3d | low | Minor |
2,797,329,957 | PowerToys | Hide mouse at screen edge is still bugged | ### Microsoft PowerToys version
v0.87.1
### Installation method
Microsoft Store
### Running as admin
Yes
### Area(s) with issue?
Mouse Without Borders
### Steps to reproduce
When moving the mouse from right to left and vice versa. The mouse still can show on the mouse out of the hide mouse on screen edge.
It's very annoying and it keeps returning regardless.
### ✔️ Expected Behavior
I expected to not see the mouse on the other screen at all regradless going from right to left and vice versa.
### ❌ Actual Behavior
The mouse still shows on top of the screen edge even when it was hiding it still shows up.
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Critical |
2,797,357,765 | vscode | Trying to bootstrap extensions into a portable and user/system installations into VSCode |
Type: <b>Bug</b>
I am unclear if this is a bug and is probably just an issue of not trulyy understanding the process. In the 1.96 release notes there was a section about bootstrapping extensions into VSCode. I followed those steps but the editor did not silently install the extensions that were placed in the folder as directed. I have tried to do this for both a portable version as well as user and system installations. Can I get some clearer guidance on this path? We are building a customized VSCode installer for a group of blind and low vision students and we are highly customizing the environment, shipping extensions, adding key bindings and more. I am trying to avoid shippiing an entire extensions folder but would rather just proviide the market place files and have VSCode bootstrap them into their build.
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26120
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 Microsoft Surface (R) Edition (12 x 2196)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.45GB (0.47GB free)|
|Process Argv|--crash-reporter-id 5a524437-3f52-4db4-af12-3ac13392aa4b|
|Screen Reader|yes|
|VM|0%|
</details><details><summary>Extensions (34)</summary>
Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.5.0
vscode-intelephense-client|bme|1.12.6
vscode-innosetup|cho|1.9.3
vscode-markdownlint|Dav|0.58.2
prettier-vscode|esb|11.0.0
copilot|Git|1.257.0
copilot-chat|Git|0.23.2
vscode-pull-request-github|Git|0.102.0
vscode-htmlhint|HTM|1.0.5
file-history|Jef|1.0.0
vscode-dotnet-runtime|ms-|2.2.5
vscode-edge-devtools|ms-|2.1.6
black-formatter|ms-|2024.4.0
debugpy|ms-|2024.14.0
pylint|ms-|2024.0.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
vscode-python-envs|ms-|0.1.2025011501
remote-ssh|ms-|0.116.1
remote-ssh-edit|ms-|0.87.0
live-server|ms-|0.4.15
powershell|ms-|2024.4.0
remote-explorer|ms-|0.4.3
vscode-copilot-vision|ms-|0.1.1
vscode-speech|ms-|0.12.1
vsliveshare|ms-|1.0.5948
pytest-runner|pam|0.0.10
LiveServer|rit|5.7.9
partial-diff|ryu|1.4.3
markdown-preview-enhanced|shd|0.8.15
code-spell-checker|str|4.0.34
gitdoc|vsl|0.2.3
markdown-all-in-one|yzh|3.6.2
zen-mode-on-startup|zen|0.0.1
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
```
</details>
<!-- generated by issue reporter --> | info-needed | low | Critical |
2,797,359,862 | PowerToys | Calculator subtractions have odd behaviors, often resulting in results displaying billionths when unnecessary and potentially incorrect. | ### Microsoft PowerToys version
0.87.1
### Installation method
GitHub
### Running as admin
Yes
### Area(s) with issue?
PowerToys Run
### Steps to reproduce
Open the PowerToys Run prompt and perform a subtraction with the first number being a float.
Not sure how exactly to word when it occurs, but it seems to occur when the result is randomly between 10^1 or 10^2 smaller than the original.
Example 1: =1189390.24-1183760.67
Example 2: =123456789.01-123456789.00
Example 3: =100000.01-90000
Example 4: =100000.01-90001
Example 5: =1000.01-990
Example 6: =1000.01-991
### ✔️ Expected Behavior
Example 1: =1189390.24-1183760.67 should return 5629.57
Example 2: =123456789.01-123456789.00 should return 0.01
Example 3: =100000.01-90000 should return 10000.01
Example 4: =100000.01-90001 should return 9999.01
Example 5: =1000.01-990 should return 10.01
Example 6: =1000.01-991 should return 9.01
### ❌ Actual Behavior
Example 1: =1189390.24-1183760.67 returns 5629.5700000001
Example 2: =123456789.01-123456789.00 returns 0.0100000054
Example 3: =100000.01-90000 returns 10000.01
Example 4: =100000.01-90001 returns 9999.0100000000
Example 5: =1000.01-990 returns 10.01
Example 6: =1000.01-991 returns 9.0100000000
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,797,393,292 | opencv | cv2.minAreaRect and cv2.boxPoints angle is not clear in documentation | Are the rotation angles specified by the cv2.minAreaRect and cv2.boxPoints clockwise or counterclockwise? Where can I see the definition code for these two functions? | category: documentation | low | Minor |
2,797,395,009 | rust | Infinite/long backtrace on i686 under Wine | I'm not sure where to file this bug, but it affects Rust more than other languages for reasons explained below, so let's at least make this visible here.
I tried running this code:
```rust
fn main() {
panic!("Hello, world!");
}
```
with `RUST_BACKTRACE=full` under Wine.
I expected to see this happen: a short backtrace.
Instead, this happened: an infinite backtrace on i686-pc-windows-msvc and a finite, but longer than necessary, repetitive, and clearly wrong backtrace on i686-pc-windows-gnu.
This might not seem like much (does anyone use `RUST_BACKTRACE=full` in production?), but Rust forces a full backtrace on double panic, so panics in destructors effectively hang the process instead of aborting it. Beautiful.
I think it's fair to say that this is likely a Wine bug, however, I think it's also possible that LLVM generates wrong SEH frames, which Windows handles correctly only by chance. As a workaround, we might want to somewhat limit the backtrace length even on double panic?
### Meta
`rustc --version --verbose`:
```
rustc 1.86.0-nightly (419b3e2d3 2025-01-15)
binary: rustc
commit-hash: 419b3e2d3e350822550eee0e82eeded4d324d584
commit-date: 2025-01-15
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.6
```
`wine --version`: `wine-9.22 (Staging)`
I'm cross-compiling for Windows with cargo-xwin for MSVC ABI and cross for GNU ABI:
- `XWIN_ARCH=x86 RUST_BACKTRACE=full cargo xwin run --target i686-pc-windows-msvc`
- `RUST_BACKTRACE=full cross run --target i686-pc-windows-gnu`
...but I have checked that the problem can be reproduced with executables built natively on Windows.
<details><summary><code>RUST_BACKTRACE=full</code> backtrace on MSVC</summary>
<p>
```
thread 'main' panicked at src/main.rs:10:5:
Hello, world!
stack backtrace:
0024:fixme:dbghelp:i386_stack_walk new PC=833875c0 different from Eip=40b4ab
0: 0x40b4ab - fmt
1: 0x40b4ab - core::fmt::write
[the above lines repeated endlessly, with nothing but the frame depth changing]
```
</p>
</details>
<details><summary><code>RUST_BACKTRACE=full</code> backtrace on GNU</summary>
<p>
```
thread 'main' panicked at src/main.rs:10:5:
Hello, world!
stack backtrace:
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp:elf_search_auxv can't find symbol in module
015c:fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x33 at debug_info(abbrev:014D0610,symt:011EE5A0) in ctx(011E05E0,L"cringe")
015c:fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x33 at debug_info(abbrev:014D0610,symt:011EE620) in ctx(011E05E0,L"cringe")
015c:fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x33 at debug_info(abbrev:014D0610,symt:011EE720) in ctx(011E05E0,L"cringe")
015c:fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x33 at debug_info(abbrev:014D0610,symt:025000B8) in ctx(011E05E0,L"cringe")
015c:fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x33 at debug_info(abbrev:014D0610,symt:02500138) in ctx(011E05E0,L"cringe")
015c:fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x33 at debug_info(abbrev:014D0610,symt:02500238) in ctx(011E05E0,L"cringe")
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
0: 0x48406b - core::fmt::rt::Argument::fmt::h8360d965bd1e2b6e
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\fmt/rt.rs:177:76
1: 0x48406b - core::fmt::write::hd923a73d9d161bb0
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\fmt/mod.rs:1440:21
2: 0x48406b - core::fmt::rt::Argument::fmt::h8360d965bd1e2b6e
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\fmt/rt.rs:177:76
3: 0x48406b - core::fmt::write::hd923a73d9d161bb0
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\fmt/mod.rs:1440:21
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
4: 0x434015 - std::io::Write::write_fmt::had1d59cd6160ac1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src\io/mod.rs:1887:15
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
5: 0x43dd85 - std::sys::backtrace::BacktraceLock::print::hd49d4d80db29b827
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src\sys/backtrace.rs:42:9
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
6: 0x440387 - std::panicking::default_hook::{{closure}}::hd20fad6770713ea0
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:298:22
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
7: 0x4401d0 - std::panicking::default_hook::h1a8c8518394b8a18
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:325:9
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
8: 0x440df5 - std::panicking::rust_panic_with_hook::h9da62b45b00ce8e2
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:831:13
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
9: 0x440b84 - std::panicking::begin_panic_handler::{{closure}}::h2f73c259c0a62ae3
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:697:13
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
10: 0x43e8ab - std::sys::backtrace::__rust_end_short_backtrace::h8d127ac41d00cbaf
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src\sys/backtrace.rs:168:18
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
11: 0x4408ae - rust_begin_unwind
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:695:5
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
12: 0x4806f1 - core::panicking::panic_fmt::hffd0c350f3e911e2
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src/panicking.rs:75:14
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
13: 0x40166f - cringe::main::he8e076d3e00c6e43
at /home/purplesyringa/cringe/src/main.rs:10:5
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
14: 0x401809 - core::ops::function::FnOnce::call_once::hab1ff5b455ae04c6
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584\library\core\src\ops\function.rs:250:5
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
15: 0x401791 - std::sys::backtrace::__rust_begin_short_backtrace::hf837e3a1102d85cf
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584\library\std\src\sys\backtrace.rs:152:18
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
16: 0x401773 - std::rt::lang_start::{{closure}}::h0ed424ef8b484891
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584\library\std\src\rt.rs:194:18
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
17: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
18: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
19: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
20: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
21: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
22: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
23: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
24: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
25: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
26: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
27: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
28: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
29: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
30: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
31: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
32: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
33: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
34: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
35: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
36: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
37: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
38: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
39: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
40: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
41: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
42: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
43: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
44: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
45: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
46: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
47: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
48: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
49: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
50: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
51: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
52: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
53: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
54: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
55: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
56: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
57: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
58: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
59: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
60: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
61: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
62: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
63: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
64: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
65: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
66: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
67: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
68: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
69: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
70: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
71: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
72: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
73: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
74: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
75: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
76: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
77: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
78: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
79: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
80: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
81: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
82: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
83: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
84: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
85: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
86: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
87: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
88: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
89: 0x426745 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::h8eb84feb54c9cb1d
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\core\src\ops/function.rs:284:13
90: 0x426745 - std::panicking::try::do_call::hfdc2187cea17d7ae
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
91: 0x426745 - std::panicking::try::h906cdc33b1ce235a
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
92: 0x426745 - std::panic::catch_unwind::he80bb62fbfbcf0ee
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
93: 0x426745 - std::rt::lang_start_internal::{{closure}}::h66a7d6bdfa5b0443
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:163:24
94: 0x426745 - std::panicking::try::do_call::hbe592467235de060
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:587:40
95: 0x426745 - std::panicking::try::h887ebabf70af544c
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panicking.rs:550:19
96: 0x426745 - std::panic::catch_unwind::he0bcf444777fac47
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/panic.rs:358:14
97: 0x426745 - std::rt::lang_start_internal::hf4c77c5234ec0509
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584/library\std\src/rt.rs:159:5
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
98: 0x40174b - std::rt::lang_start::h59c4269b4dacd45e
at /rustc/419b3e2d3e350822550eee0e82eeded4d324d584\library\std\src\rt.rs:193:5
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
99: 0x4016ae - _main
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
100: 0x401386 - __tmainCRTStartup
at ./build/i686-w64-mingw32-i686-w64-mingw32-crt/./mingw-w64-crt/crt/crtexe.c:339:15
015c:fixme:dbghelp_dwarf:parse_cie_details unknown CIE version 20 at 019E5928
101: 0x785194c0 - @BaseThreadInitThunk@12
102: 0x786c9aa3 - _call_thread_func_wrapper
103: 0x786caef2 - call_thread_func
at /usr/src/packages/BUILD/dlls/ntdll/signal_i386.c:603:9
```
</p>
</details>
@rustbot label +A-backtrace +A-debuginfo +A-panic +A-runtime +E-needs-investigation +O-windows +O-x86_32 +T-compiler | A-runtime,O-windows,A-debuginfo,T-compiler,C-bug,A-panic,O-x86_32,A-backtrace,E-needs-investigation | low | Critical |
2,797,396,049 | ui | [bug]: Authentication and Login both have the exact same blocks | ### Describe the bug
All the blocks in both menus are duplicated, I think the login menu should be removed
Can you please assign this to me I will remove the login menu and the route from there
### Affected component/components
None
### How to reproduce
visit https://ui.shadcn.com/blocks/authentication
and
https://ui.shadcn.com/blocks/login
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
```
### System Info
```bash
All Browsers
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,797,400,746 | rust | ICE: "failed to resolve instance for type", apparently caused by generic parameter inference | ### Code
Playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=c29a73a6b88b2ef3d327766daee94e1d
This example is a little large (213 lines), but it's also an error I can work around pretty easily so I'm not too worried about it.
To fix it, it seems like you can just change the impl at line 88,
```rust
impl<const A: usize, const B: usize, O> VarCmp<Var<B>> for Var<A>
where
Const<A>: ToUInt,
Const<B>: ToUInt,
U<A>: Cmp<U<B>, Output=O>,
{
type Output = O;
}
```
to use a more explicit path:
```rust
impl<const A: usize, const B: usize> VarCmp<Var<B>> for Var<A>
where
Const<A>: ToUInt,
Const<B>: ToUInt,
U<A>: Cmp<U<B>>,
{
type Output = <U<A> as Cmp<U<B>>>::Output;
}
```
(Fixed version: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=748b532ef879333714976bf96b904fcd)
For reference, this system is meant to order & group `Var<N>` types (e.g. `Var<0> + Var<1> + Var<0> -> Sum<Sum<Var<0>, Var<0>>, Var<1>>`).
### 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.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-pc-windows-msvc
release: 1.84.0
LLVM version: 19.1.5
```
This error also occurred in 1.83.0 stable, but updating to 1.84.0 didn't seem to change anything.
### Error output
```
error: internal compiler error: compiler\rustc_middle\src\ty\instance.rs:581:21: failed to resolve instance for <Sum<Sum<Var<0>, Var<0>>, Sum<Sum<Var<1>, Sum<Var<1>, Var<1>>>, Sum<Var<2>, Var<2>>>> as Add<Sum<Var<0>, Sum<Sum<Var<1>, Var<1>>, Var<2>>>>>::add
--> src\lib.rs:212:23
|
212 | assert_eq!(y + z, z + y);
| ^^^^^
thread 'rustc' panicked at compiler\rustc_middle\src\ty\instance.rs:581:21:
Box<dyn Any>
```
<details><summary><strong>Backtrace</strong></summary>
<p>
```
stack backtrace:
0: 0x7ffa23abba41 - std::backtrace_rs::backtrace::dbghelp64::trace
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\..\..\backtrace\src\backtrace\dbghelp64.rs:91
1: 0x7ffa23abba41 - std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\..\..\backtrace\src\backtrace\mod.rs:66
2: 0x7ffa23abba41 - std::sys::backtrace::_print_fmt
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\sys\backtrace.rs:66
3: 0x7ffa23abba41 - std::sys::backtrace::impl$0::print::impl$0::fmt
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\sys\backtrace.rs:39
4: 0x7ffa23aedd1a - core::fmt::rt::Argument::fmt
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/core\src\fmt\rt.rs:177
5: 0x7ffa23aedd1a - core::fmt::write
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/core\src\fmt\mod.rs:1189
6: 0x7ffa23ab1de7 - std::io::Write::write_fmt<std::sys::pal::windows::stdio::Stderr>
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\io\mod.rs:1884
7: 0x7ffa23abb885 - std::sys::backtrace::BacktraceLock::print
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\sys\backtrace.rs:42
8: 0x7ffa23abe7a3 - std::panicking::default_hook::closure$1
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\panicking.rs:268
9: 0x7ffa23abe582 - std::panicking::default_hook
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\panicking.rs:295
10: 0x7ffa2509ab1e - strncpy
11: 0x7ffa23abeee2 - alloc::boxed::impl$30::call
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/alloc\src\boxed.rs:1986
12: 0x7ffa23abeee2 - std::panicking::rust_panic_with_hook
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\panicking.rs:809
13: 0x7ffa2688b993 - <rustc_hir_pretty[ab0fe6e31331acdd]::State>::print_variant
14: 0x7ffa2687d999 - <rustc_hir_pretty[ab0fe6e31331acdd]::State>::print_variant
15: 0x7ffa2687d958 - <rustc_hir_pretty[ab0fe6e31331acdd]::State>::print_variant
16: 0x7ffa268993c5 - <rustc_errors[3bd8408db383e9c9]::diagnostic::BugAbort as rustc_errors[3bd8408db383e9c9]::diagnostic::EmissionGuarantee>::emit_producing_guarantee
17: 0x7ffa266ee57f - ar_archive_writer[5ad4fe434effa9d8]::object_reader::get_member_alignment
18: 0x7ffa267a0f36 - rustc_middle[87d6ac0499a2eaf7]::util::bug::bug_fmt
19: 0x7ffa267818bd - <rustc_middle[87d6ac0499a2eaf7]::ty::consts::Const>::to_valtree
20: 0x7ffa267816d6 - <rustc_middle[87d6ac0499a2eaf7]::ty::consts::Const>::to_valtree
21: 0x7ffa267a0e69 - rustc_middle[87d6ac0499a2eaf7]::util::bug::bug_fmt
22: 0x7ffa24ee608c - <rustc_middle[87d6ac0499a2eaf7]::ty::instance::Instance>::expect_resolve
23: 0x7ffa23e6c637 - <rustc_monomorphize[85a23766e536164]::collector::MirUsedCollector as rustc_middle[87d6ac0499a2eaf7]::mir::visit::Visitor>::visit_terminator
24: 0x7ffa23e770a9 - rustc_monomorphize[85a23766e536164]::collector::items_of_instance
25: 0x7ffa24840ee7 - rustc_query_impl[8be1416e77d742ed]::plumbing::query_key_hash_verify_all
26: 0x7ffa247784db - rustc_ty_utils[4902e6e6aecd2893]::ty::self_ty_of_trait_impl_enabling_order_dep_trait_object_hack
27: 0x7ffa24853bed - rustc_query_impl[8be1416e77d742ed]::plumbing::query_key_hash_verify_all
28: 0x7ffa23e997f4 - rustc_monomorphize[85a23766e536164]::polymorphize::unused_generic_params
29: 0x7ffa23e96624 - rustc_monomorphize[85a23766e536164]::polymorphize::unused_generic_params
30: 0x7ffa23e96f82 - rustc_monomorphize[85a23766e536164]::polymorphize::unused_generic_params
31: 0x7ffa23e96f82 - rustc_monomorphize[85a23766e536164]::polymorphize::unused_generic_params
32: 0x7ffa23e8d616 - rustc_monomorphize[85a23766e536164]::partitioning::collect_and_partition_mono_items
33: 0x7ffa236b8007 - rustc_ty_utils[4902e6e6aecd2893]::ty::adt_sized_constraint
34: 0x7ffa2369e9fd - rustc_ty_utils[4902e6e6aecd2893]::ty::adt_sized_constraint
35: 0x7ffa235c568f - rustc_ty_utils[4902e6e6aecd2893]::ty::adt_sized_constraint
36: 0x7ffa236dd2ee - rustc_query_impl[8be1416e77d742ed]::query_system
37: 0x7ffa20bb29bb - <rustc_codegen_llvm[85ae7dac9399dd6b]::LlvmCodegenBackend as rustc_codegen_ssa[ce0820b527006769]::traits::backend::CodegenBackend>::codegen_crate
38: 0x7ffa20b13073 - <rustc_interface[c014954558e9d384]::queries::Linker>::codegen_and_build_linker
39: 0x7ffa20ac74bd - _rust_alloc_error_handler
40: 0x7ffa20ac2fcf - _rust_alloc_error_handler
41: 0x7ffa20accfc5 - _rust_alloc_error_handler
42: 0x7ffa23ad0bad - alloc::boxed::impl$28::call_once
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/alloc\src\boxed.rs:1972
43: 0x7ffa23ad0bad - alloc::boxed::impl$28::call_once
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/alloc\src\boxed.rs:1972
44: 0x7ffa23ad0bad - std::sys::pal::windows::thread::impl$0::new::thread_start
at /rustc/9fc6b43126469e3858e2fe86cafb4f0fd5068869\library/std\src\sys\pal\windows\thread.rs:55
45: 0x7ffa9f687374 - BaseThreadInitThunk
46: 0x7ffaa03bcc91 - RtlUserThreadStart
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: rustc 1.84.0 (9fc6b4312 2025-01-07) running on x86_64-pc-windows-msvc
note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental=[REDACTED]
note: some of the compiler flags provided by cargo are hidden
query stack during panic:
#0 [items_of_instance] collecting items used by `test`
#1 [collect_and_partition_mono_items] collect_and_partition_mono_items
end of query stack
```
</p>
</details>
| I-ICE,T-compiler,C-bug | low | Critical |
2,797,431,608 | storybook | [Bug]: (vitest integration) `test.include` should not be ignored | ### Describe the bug
About removing `test.include` [here](https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-test-indexing-behavior-of-storybookexperimental-addon-test-is-changed),
One drawback is then user can't run non-storybook tests. i.e. user may have test in `.test.ts` which uses `import { render } from 'vitest-browser-react'` to write unit tests. Those needs to be included by Vitest in `test.include`.
I believe many users will be on the same boat as they migrate their existing projects to use Storybook to replace current tests.
### Reproduction link
https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-test-indexing-behavior-of-storybookexperimental-addon-test-is-changed
### Reproduction steps
It is described in the migration guide: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-test-indexing-behavior-of-storybookexperimental-addon-test-is-changed
### System
```bash
Storybook Environment Info:
System:
OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 20.18.0 - /run/user/1000/fnm_multishells/720_1737231505770/bin/node
npm: 10.8.2 - /run/user/1000/fnm_multishells/720_1737231505770/bin/npm
pnpm: 9.12.2 - /run/user/1000/fnm_multishells/720_1737231505770/bin/pnpm <----- active
```
### Additional context
_No response_ | bug,addon: test | low | Critical |
2,797,456,157 | vscode | Go To Definition opens file in preview mode instead of normal window | <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
Yes, but you need at least one language extension such as C# to get the Go To Definition function.
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.96.4
- OS Version: Windows 10 build 19045
Steps to Reproduce:
1. Right click a class that is defined in a different file that is not already open, then click Go To Definition (or CTRL + click the class).
Expected:
File will open in a new window in normal mode
Actual:
File opens in preview mode and will be replaced the next time you use Go To Definition or open another file in preview mode.
Additional info:
The [documentation ](https://code.visualstudio.com/docs/getstarted/userinterface#_preview-mode )states that Preview Mode is supposed to be used in two instances: when single clicking a file in the file explorer, or when opening it from the Quick Open if the `workbench.editor.enablePreviewFromQuickOpen` setting is set to true. It does not mention Go To Definition and there is no setting to control it.
Suggested fix:
Add a setting to control whether or not Go To Definition opens in preview mode.
| feature-request | low | Critical |
2,797,475,074 | tensorflow | Unable to install TensorFlow: No matching distribution found for TensorFlow! | ### Issue type
Build/Install
### Have you reproduced the bug with TensorFlow Nightly?
No
### Source
source
### TensorFlow version
tf 2.8
### Custom code
Yes
### OS platform and distribution
Windows 10
### Mobile device
_No response_
### Python version
3.13
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
_No response_
### GPU model and memory
_No response_
### Current behavior?
I expected to install TensorFlow
### Standalone code to reproduce the issue
Can't install TensorFlow with pip
```shell
> pip install tensorflow
ERROR: Could not find a version that satisfies the requirement tensorflow (from versions: none)
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python.exe -m pip install --upgrade pip
ERROR: No matching distribution found for tensorflow
```
Pls help
### Relevant log output
```shell
``` | stat:awaiting response,type:build/install,type:support,TF 2.8 | low | Critical |
2,797,475,339 | godot | Baking a lightmap on a scene that already has a lightmap causes crash | ### Tested versions
- first found in godot 4.3.1 [90f21a35c]
### System information
Fedora 41 - Godot 4.3[90d21a35c]
### Issue description
when baking a lightmap when another lightmap is already assigned to a LightmapGI node causes a crash
```
ERROR: Trying to unreference a SafeRefCount which is already zero is wrong and a symptom of it being misused.
Upon a SafeRefCount reaching zero any object whose lifetime is tied to it, as well as the ref count itself, must be destroyed.
Moreover, to guarantee that, no multiple threads should be racing to do the final unreferencing to zero.
at: _check_unref_safety (./core/templates/safe_refcount.h:187)
================================================================
handle_crash: Program crashed with signal 4
Engine version: Godot Engine v4.3.1.rc.custom_build (90f21a35c71107d2afe95a3875bb761ba2170d90)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib64/libc.so.6(+0x1a090) [0x7fd01fd9a090] (??:0)
[2] RefCounted::unreference() (/home/jwoon/Documents/GodotTemplates/godot/./core/templates/safe_refcount.h:187 (discriminator 2))
[3] Ref<LightmapGIData>::unref() (/home/jwoon/Documents/GodotTemplates/godot/./core/object/ref_counted.h:209 (discriminator 1))
[4] Ref<LightmapGIData>::ref(Ref<LightmapGIData> const&) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/ref_counted.h:65)
[5] LightmapGI::set_light_data(Ref<LightmapGIData> const&) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/ref_counted.h:117)
[6] LightmapGI::bake(Node*, String, bool (*)(float, String const&, void*, bool), void*) (/home/jwoon/Documents/GodotTemplates/godot/./scene/3d/lightmap_gi.cpp:1346)
[7] LightmapGIEditorPlugin::_bake_select_file(String const&) (/home/jwoon/Documents/GodotTemplates/godot/./editor/plugins/lightmap_gi_editor_plugin.cpp:71 (discriminator 4))
[8] void call_with_variant_args_helper<LightmapGIEditorPlugin, String const&, 0ul>(LightmapGIEditorPlugin*, void (LightmapGIEditorPlugin::*)(String const&), Variant const**, Callable::CallError&, IndexSequence<0ul>) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:304 (discriminator 6))
[9] void call_with_variant_args<LightmapGIEditorPlugin, String const&>(LightmapGIEditorPlugin*, void (LightmapGIEditorPlugin::*)(String const&), Variant const**, int, Callable::CallError&) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:418)
[10] CallableCustomMethodPointer<LightmapGIEditorPlugin, String const&>::call(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/object/callable_method_pointer.h:103)
[11] Callable::callp(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/callable.cpp:57)
[12] Object::emit_signalp(StringName const&, Variant const**, int) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/object.cpp:1190)
[13] Node::emit_signalp(StringName const&, Variant const**, int) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/node.cpp:3899)
[14] Error Object::emit_signal<String>(StringName const&, String) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/object.h:936)
[15] EditorFileDialog::_save_confirm_pressed() (/home/jwoon/Documents/GodotTemplates/godot/./editor/gui/editor_file_dialog.cpp:402 (discriminator 4))
[16] void call_with_variant_args_helper<EditorFileDialog>(EditorFileDialog*, void (EditorFileDialog::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:304 (discriminator 4))
[17] void call_with_variant_args<EditorFileDialog>(EditorFileDialog*, void (EditorFileDialog::*)(), Variant const**, int, Callable::CallError&) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:418)
[18] CallableCustomMethodPointer<EditorFileDialog>::call(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/object/callable_method_pointer.h:103)
[19] Callable::callp(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/callable.cpp:57)
[20] Object::emit_signalp(StringName const&, Variant const**, int) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/object.cpp:1190)
[21] Node::emit_signalp(StringName const&, Variant const**, int) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/node.cpp:3899)
[22] Error Object::emit_signal<>(StringName const&) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/object.h:936)
[23] AcceptDialog::_ok_pressed() (/home/jwoon/Documents/GodotTemplates/godot/./scene/gui/dialogs.cpp:137 (discriminator 1))
[24] void call_with_variant_args_helper<AcceptDialog>(AcceptDialog*, void (AcceptDialog::*)(), Variant const**, Callable::CallError&, IndexSequence<>) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:304 (discriminator 4))
[25] void call_with_variant_args<AcceptDialog>(AcceptDialog*, void (AcceptDialog::*)(), Variant const**, int, Callable::CallError&) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:418)
[26] CallableCustomMethodPointer<AcceptDialog>::call(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/object/callable_method_pointer.h:103)
[27] Callable::callp(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/callable.cpp:57)
[28] Object::emit_signalp(StringName const&, Variant const**, int) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/object.cpp:1190)
[29] Node::emit_signalp(StringName const&, Variant const**, int) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/node.cpp:3899)
[30] Error Object::emit_signal<>(StringName const&) (/home/jwoon/Documents/GodotTemplates/godot/./core/object/object.h:936)
[31] BaseButton::_pressed() (/home/jwoon/Documents/GodotTemplates/godot/./scene/gui/base_button.cpp:137 (discriminator 1))
[32] BaseButton::on_action_event(Ref<InputEvent>) (/home/jwoon/Documents/GodotTemplates/godot/./scene/gui/base_button.cpp:171)
[33] BaseButton::gui_input(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/./scene/gui/base_button.cpp:68 (discriminator 2))
[34] Control::_call_gui_input(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/./scene/gui/control.cpp:1830)
[35] Viewport::_gui_call_input(Control*, Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/viewport.cpp:1568)
[36] Viewport::_gui_input_event(Ref<InputEvent>) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/viewport.cpp:1837 (discriminator 8))
[37] Viewport::push_input(Ref<InputEvent> const&, bool) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/viewport.cpp:3259 (discriminator 2))
[38] Window::_window_input(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/window.cpp:1680)
[39] Viewport::_sub_windows_forward_input(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/viewport.cpp:2986)
[40] Viewport::push_input(Ref<InputEvent> const&, bool) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/viewport.cpp:3243 (discriminator 2))
[41] Window::_window_input(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/./scene/main/window.cpp:1680)
[42] void call_with_variant_args_helper<Window, Ref<InputEvent> const&, 0ul>(Window*, void (Window::*)(Ref<InputEvent> const&), Variant const**, Callable::CallError&, IndexSequence<0ul>) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:304 (discriminator 6))
[43] void call_with_variant_args<Window, Ref<InputEvent> const&>(Window*, void (Window::*)(Ref<InputEvent> const&), Variant const**, int, Callable::CallError&) (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/binder_common.h:418)
[44] CallableCustomMethodPointer<Window, Ref<InputEvent> const&>::call(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/object/callable_method_pointer.h:103)
[45] Callable::callp(Variant const**, int, Variant&, Callable::CallError&) const (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/callable.cpp:57)
[46] Variant Callable::call<Ref<InputEvent> >(Ref<InputEvent>) const (/home/jwoon/Documents/GodotTemplates/godot/./core/variant/variant.h:875)
[47] DisplayServerWayland::_dispatch_input_event(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/platform/linuxbsd/wayland/display_server_wayland.cpp:95 (discriminator 2))
[48] DisplayServerWayland::dispatch_input_events(Ref<InputEvent> const&) (/home/jwoon/Documents/GodotTemplates/godot/platform/linuxbsd/wayland/display_server_wayland.cpp:89 (discriminator 1))
[49] Input::_parse_input_event_impl(Ref<InputEvent> const&, bool) (/home/jwoon/Documents/GodotTemplates/godot/./core/input/input.cpp:774)
[50] Input::flush_buffered_events() (/home/jwoon/Documents/GodotTemplates/godot/./core/input/input.cpp:1055)
[51] DisplayServerWayland::process_events() (/home/jwoon/Documents/GodotTemplates/godot/platform/linuxbsd/wayland/display_server_wayland.cpp:1254 (discriminator 1))
[52] OS_LinuxBSD::run() (/home/jwoon/Documents/GodotTemplates/godot/platform/linuxbsd/os_linuxbsd.cpp:958 (discriminator 1))
[53] /mnt/Forerunner/SteamLibrary/steamapps/common/Godot Engine/godot.x11.opt.tools.64(main+0x2b3) [0x55ed9299921c] (/home/jwoon/Documents/GodotTemplates/godot/platform/linuxbsd/godot_linuxbsd.cpp:85)
[54] /lib64/libc.so.6(+0x3248) [0x7fd01fd83248] (??:0)
[55] /lib64/libc.so.6(__libc_start_main+0x8b) [0x7fd01fd8330b] (??:0)
[56] /mnt/Forerunner/SteamLibrary/steamapps/common/Godot Engine/godot.x11.opt.tools.64(_start+0x25) [0x55ed92998ea5] (??:?)
-- END OF BACKTRACE --
================================================================
```
### Steps to reproduce
-place a light into a scene
-bake the lightmap once
-bake it again without first removing the lightmap data resource from the lightmapGI
### Minimal reproduction project (MRP)
N/A | bug,topic:rendering,crash,topic:3d | low | Critical |
2,797,476,080 | pytorch | empty_cache does not work for CUDAPluggableAllocator + MemPool | ### 🐛 Describe the bug
I'm trying to use `CUDAPluggableAllocator`, following https://pytorch.org/docs/stable/notes/cuda.html#using-custom-memory-allocators-for-cuda . However, it has a critical limitation, that `torch.cuda.memory.change_current_allocator` needs to be called before any allocation, and we cannot switch the allocator.
Following @syed-ahmed 's suggestion, I'm trying to use `CUDAPluggableAllocator` with `MemPool`, and it seems to work, in the sense that I can switch between allocators. However, I find that, in this way, the pool never returns memory to the underlying allocator.
Here is a simple demonstration code snippet:
```python
import torch
import torch.utils.cpp_extension
cpp_sources = """
// save as alloc.cc
// compile with g++ alloc.cc -o alloc.so -I/usr/local/cuda/include -shared -fPIC
#include <sys/types.h>
#include <cuda_runtime_api.h>
#include <iostream>
// Compile with g++ alloc.cc -o alloc.so -I/usr/local/cuda/include -shared -fPIC
extern "C" {
void* my_malloc(ssize_t size, int device, cudaStream_t stream) {
void *ptr;
cudaMalloc(&ptr, size);
std::cout<<"C side: alloc "<<ptr<< " " <<size<<std::endl;
return ptr;
}
void my_free(void* ptr, ssize_t size, int device, cudaStream_t stream) {
std::cout<<"C side: free "<<ptr<< " "<<size<<std::endl;
cudaFree(ptr);
}
// hack: add this placeholder function to let PyTorch generate module extension template
at::Tensor sin_add(at::Tensor x, at::Tensor y) {
return x.sin() + y.sin();
}
}
"""
module = torch.utils.cpp_extension.load_inline("alloc", cpp_sources, with_cuda=True, functions=['sin_add'])
so_file = module.__file__
def f():
new_alloc = torch.cuda.memory.CUDAPluggableAllocator(
so_file, 'my_malloc', 'my_free')
with torch.cuda.use_mem_pool(torch.cuda.MemPool(new_alloc._allocator)):
for factor in (1024, 1024 ** 2):
print(f"Allocate {60 * factor} bytes of memory on the GPU from Python")
data = torch.empty((60, factor), dtype=torch.uint8, device="cuda")
print(f"Free {60 * factor} bytes of memory on the GPU from Python")
del data
print("Python side: memory is released")
print(f"Allocate {70 * factor} bytes of memory on the GPU from Python")
data = torch.empty((70, factor), dtype=torch.uint8, device="cuda")
print(f"Free {70 * factor} bytes of memory on the GPU from Python")
del data
print("Python side: memory is released")
# torch.cuda.empty_cache() here will error: RuntimeError: captures_underway.empty() INTERNAL ASSERT FAILED at "../c10/cuda/CUDACachingAllocator.cpp":2967, please report a bug to PyTorch.
# torch.cuda.empty_cache() here does not take effect.
f()
import gc
gc.collect()
```
Running the code, we can see that `C side: alloc ` is called properly. However, `C side: free ` is never called.
In addition, if I call `torch.cuda.empty_cache()` inside `with torch.cuda.use_mem_pool`, it will trigger an assertion error.
Ultimately, my goal is to switch between `CUDAPluggableAllocator` and the default allocator, and also `empty_cache` for the `CUDAPluggableAllocator`.
### Versions
PyTorch 2.5.1+cu124
cc @ptrblck @msaroufim @eqy | module: cuda,triaged | low | Critical |
2,797,485,959 | vscode | add python extension in vscode | <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.96.4
- OS Version: linux mint cinnamon
Steps to Reproduce:
1. can not install python extension in vscode
| info-needed | low | Critical |
2,797,487,933 | flutter | Why Localizations.localOf(context).toLanguageTag() returns me incorrect value for some languages? | ### Steps to reproduce
There are not many more steps, just switch the language in app settings and print the `Localizations.locale (context).toLanguageTag().toLowerCase()`, then check the result.
Please check the video on my real device; the language code is at the bottom of the settings page. I tested these languages:
|language|expected|actual|correct?|
|:-|:-|:-|:-|
|en-gb|en-gb|en-gb|✅|
|en-nz|en-nz|en-nz|✅|
|en-us|en-us|en-au|❌|
|zh-cn|zh-cn|zh-cn|✅|
|zh-tw|zh-tw|zh-cn|❌|
Flutter 3.24.3
Dart 3.5.3
DevTools 2.37.3
### Expected results
en-us and zh-tw
### Actual results
en-au and zh-cn
### Code sample
```dart
import 'package:flutter/material.dart';
class LanguageHelper {
static String getLocaleString(BuildContext context) {
return Localizations.localeOf(context).toLanguageTag().toLowerCase();
}
}
```
```dart
Text('language code: ${LanguageHelper.getLocaleString(context)}'),
```
### Screenshots or Video
https://github.com/user-attachments/assets/d4125ebc-d020-4153-922e-1a52b32948fa
### Logs
_No response_
### Flutter Doctor output
```shell
➜ henhaoji git:(HMA-104) ✗ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.2 24C101 darwin-x64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.96.4)
[✓] Connected device (5 available)
[✓] Network resources
• No issues found!
``` | waiting for customer response,in triage | low | Minor |
2,797,489,255 | go | cmd/compile: storing zero value into interface should not allocate | ### Go version
go1.23.5
### Output of `go env` in your module/workspace:
```shell
GOARCH=amd64
GOOS=linux
```
### What did you do?
[I ran this benchmark](https://go.dev/play/p/F3rn8fxe40U):
```go
var sinkAny any
func BenchmarkInterfaceAny(b *testing.B) {
b.ReportAllocs()
for range b.N {
sinkAny = tar.Header{}
}
}
var sinkValue reflect.Value
func BenchmarkReflectValue(b *testing.B) {
b.ReportAllocs()
for range b.N {
sinkValue = reflect.Zero(reflect.TypeFor[tar.Header]())
}
}
```
### What did you see happen?
I saw these results:
```
BenchmarkInterfaceAny 31895619 43.36 ns/op 224 B/op 1 allocs/op
BenchmarkReflectValue 401489182 3.021 ns/op 0 B/op 0 allocs/op
```
### What did you expect to see?
I expected to see zero allocations in both cases.
In #33136, we optimized `reflect.Zero` to use a zero buffer of sufficient size to back the zero value of most types.
It seems to me that we could do the same trick for the non-reflect equivalent of storing a zero value into an interface value, where the data pointer in the interface value points to some shared zero buffer. This can be done in two ways:
1. Dynamically check whether the value being stored into an interface is the zero value
2. Statically detect when the value being stored into the interface value is identically equivalent to the zero value
Of course in both cases, you'll need to be careful since we're talking about a stricter definition of "zero" where the memory is equivalent to be all zeros. | Performance,NeedsInvestigation,compiler/runtime,BugReport | low | Major |
2,797,489,781 | rust | `#[thread_local]` alignment broken on Windows, GNU ABI | I tried this code:
```rust
#![feature(thread_local)]
#[repr(align(256))]
struct HighAlignment(u8);
#[thread_local]
static EXAMPLE1: HighAlignment = const { HighAlignment(0) };
#[thread_local]
static EXAMPLE2: HighAlignment = const { HighAlignment(0) };
#[thread_local]
static EXAMPLE3: HighAlignment = const { HighAlignment(0) };
fn main() {
println!(
"{:?}, {:?}, {:?}",
&EXAMPLE1 as *const HighAlignment,
&EXAMPLE2 as *const HighAlignment,
&EXAMPLE3 as *const HighAlignment
);
}
```
I expected to see this happen: three `0x100`-aligned pointers.
Instead, this happened: *metal pipe falling*
- x86_64, GNU ABI, real Windows: `0x1f39e953850, 0x1f39e953950, 0x1f39e953a50` (unaligned)
- x86_64, MSVC ABI, real Windows: `0x1c287893900, 0x1c287893a00, 0x1c287893b00` (aligned)
- i686, GNU ABI, real Windows: `0xf9a5f8, 0xf9a6f8, 0xf9a7f8` (unaligned)
- i686, MSVC ABI, real Windows: `0x6d2f00, 0x6d3000, 0x6d3100` (aligned)
- x86_64, GNU ABI, Wine: `0x232c80, 0x232d80, 0x232e80` (unaligned)
- x86_64, MSVC ABI, Wine: `0x1320e0, 0x1321e0, 0x1322e0` (unaligned)
- i686, GNU ABI, Wine: `0x341f28, 0x342028, 0x342128` (unaligned)
- i686, MSVC ABI, Wine: `0x34f010, 0x34f110, 0x34f210` (unaligned)
So either this affects all of Windows and I just got lucky twice, or this is two bugs in a trenchcoat, one affecting GNU ABI and another one in Wine. Not sure which.
Notably, checking mixed-alignment thread locals, like `u8, u8, u128, u128, u128`, shows that the variables are correctly aligned with respect to each other within TLS, but the TLS base itself seems to be unaligned.
Tentatively marking as `I-unsound` because of unaligned references bad, feel free to retag.
### Meta
`rustc --version --verbose`:
```
rustc 1.86.0-nightly (419b3e2d3 2025-01-15)
binary: rustc
commit-hash: 419b3e2d3e350822550eee0e82eeded4d324d584
commit-date: 2025-01-15
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.6
```
`wine --version`: `wine-9.22 (Staging)`
Tracking issue for visibility: #29594
| T-compiler,O-windows-gnu,I-unsound,A-thread-locals,C-bug,requires-nightly,F-thread_local | medium | Critical |
2,797,490,629 | PowerToys | FancyZones - Open Outlook several times with different parameters on different monitors | ### Microsoft PowerToys version
0.87.1
### Installation method
Microsoft Store
### Running as admin
Yes
### Area(s) with issue?
FancyZones
### Steps to reproduce
I would like to open Outlook with several parameters. For example:
- Outlook Mails on the left monitor
- Outlook calendar on the middle monitor
- Outlook tasks on the right monitor
I can start this with the following commands:
- “C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE” /select outlook:Inbox
- “C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE” /select outlook:calendar
- “C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE” /select outlook:Tasks
Unfortunately, FancyZones does not remember the parameters of the program. This means that all windows always open on the same monitor.
Can this be fixed?
### ✔️ Expected Behavior
_No response_
### ❌ Actual Behavior
_No response_
### Other Software
Office 365 - Outlook | Issue-Bug,Needs-Triage | low | Minor |
2,797,508,800 | transformers | Mamba2 doesn't support Multi-GPU training (fast path) | ### System Info
**System Info**
- `transformers` version: 4.46.3
- Platform: Linux-4.18.0-553.27.1.el8_10.x86_64-x86_64-with-glibc2.28
- Python version: 3.9.20
- Huggingface_hub version: 0.26.2
- Safetensors version: 0.4.5
- Accelerate version: 1.2.1
- Accelerate config: not found
- PyTorch version (GPU?): 2.4.0 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using distributed or parallel set-up in script?: parallel
- Using GPU in script?: yes
- GPU type: NVIDIA A100 80GB PCIe
### Who can help?
@ylacombe, @eustlb @muellerzr @SunMarc
### Information
- [ ] The official example scripts
- [x] My own modified scripts
### Tasks
- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [x] My own task or dataset (give details below)
### Reproduction
```python
from datasets import load_dataset
from trl import SFTTrainer, SFTConfig
from transformers import AutoTokenizer, AutoModelForCausalLM, DataCollatorForLanguageModeling
model_id = 'AntonV/mamba2-130m-hf'
dataset_name = 'yelp_review_full'
tokenizer = AutoTokenizer.from_pretrained(model_id)
tokenizer.pad_token = tokenizer.eos_token
tokenizer.padding_side = 'right'
data_collator = DataCollatorForLanguageModeling(tokenizer=tokenizer, mlm=False)
model = AutoModelForCausalLM.from_pretrained(model_id)
dataset = load_dataset(dataset_name, split='train', streaming=True)
train_dataset = dataset
training_args = SFTConfig(
output_dir='./outputs',
num_train_epochs=5,
per_device_train_batch_size=4,
per_device_eval_batch_size=4,
logging_dir='./logs',
learning_rate=2e-3,
save_steps=500,
save_safetensors=False,
max_steps=10000,
report_to='none'
)
trainer = SFTTrainer(
model=model,
processing_class=tokenizer,
data_collator=data_collator,
args=training_args,
train_dataset=train_dataset,
)
trainer.train()
```
### Expected behavior
Hi! When using cuda_kernels_forward in Mamba2 on multiple GPUs the following error appears (full traceback in the end):
```
config.pre_hook({**self.nargs, **kwargs, **config.all_kwargs()})
TypeError: 'NoneType' object is not a mapping ```
```
However, it works just fine when I'm using the slower path, torch_forward.
Do you know how to address this issue?
I'm using SFTTrainer (inherited from Transformers Trainer).
Thanks a lot.
**Traceback**
```
File "/mnt/lbosm1/home/nadavsc/projects/LLMamba/train.py", line 82, in <module>
main()
File "/mnt/lbosm1/home/nadavsc/projects/LLMamba/train.py", line 79, in main
trainer.train()
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/transformers/trainer.py", line 2123, in train
return inner_training_loop(
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/transformers/trainer.py", line 2481, in _inner_training_loop
tr_loss_step = self.training_step(model, inputs, num_items_in_batch)
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/transformers/trainer.py", line 3612, in training_step
self.accelerator.backward(loss, **kwargs)
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/accelerate/accelerator.py", line 2248, in backward
loss.backward(**kwargs)
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/torch/_tensor.py", line 521, in backward
torch.autograd.backward(
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/torch/autograd/__init__.py", line 289, in backward
_engine_run_backward(
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/torch/autograd/graph.py", line 768, in _engine_run_backward
return Variable._execution_engine.run_backward( # Calls into the C++ engine to run the backward pass
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/torch/autograd/function.py", line 306, in apply
return user_fn(self, *args)
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/torch/amp/autocast_mode.py", line 501, in decorate_bwd
return bwd(*args, **kwargs)
File "/mnt/lbosm1/home/nadavsc/projects/LLMamba/mamba_ssm/ops/triton/ssd_combined.py", line 893, in backward
dx, ddt, dA, dB, dC, dD, _, ddt_bias, dinitial_states = _mamba_chunk_scan_combined_bwd(
File "/mnt/lbosm1/home/nadavsc/projects/LLMamba/mamba_ssm/ops/triton/ssd_combined.py", line 414, in _mamba_chunk_scan_combined_bwd
dx, ddt, dD_from_x = _chunk_scan_chunk_state_bwd_dx(x, dt, dA_cumsum, B, CB, dout, dstates, D=D, seq_idx=seq_idx, dx=dx)
File "/mnt/lbosm1/home/nadavsc/projects/LLMamba/mamba_ssm/ops/triton/ssd_combined.py", line 250, in _chunk_scan_chunk_state_bwd_dx
_chunk_scan_chunk_state_bwd_dx_kernel[grid_dx](
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/triton/runtime/jit.py", line 345, in <lambda>
return lambda *args, **kwargs: self.run(grid=grid, warmup=False, *args, **kwargs)
File "/home/nadavsc/LIGHTBITS/envs/ssm/lib/python3.9/site-packages/triton/runtime/autotuner.py", line 170, in run
config.pre_hook({**self.nargs, **kwargs, **config.all_kwargs()})
TypeError: 'NoneType' object is not a mapping | bug | low | Critical |
2,797,509,637 | flutter | cannot build my apk and it always returns build failed | ### Steps to reproduce
1.code an app for your convenience
2.now try to make that code work in another flutter version , it works on web
3. now when trying to build the apk , it shows build failed
app/gradle
```
-------------
plugins {
id "com.android.application"
id "kotlin-android"
id "dev.flutter.flutter-gradle-plugin"
}
android {
namespace = "com.example.service_connect_real"
compileSdk = 34 // Use a fixed SDK version instead of flutter.compileSdkVersion
ndkVersion "25.2.9519653"
compileOptions {
sourceCompatibility = JavaVersion.VERSION_11 // Downgrade to Java 11 for compatibility
targetCompatibility = JavaVersion.VERSION_11
}
kotlinOptions {
jvmTarget = "11"
}
defaultConfig {
applicationId = "com.example.service_connect_real"
minSdk = 21 // Ensure minSdk is at least 21
//noinspection OldTargetApi
targetSdk = 34 // Use a fixed version
versionCode = 1
versionName = "1.0"
}
buildTypes {
release {
signingConfig = signingConfigs.debug
minifyEnabled true
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
}
}
}
dependencies {
implementation 'com.android.tools.build:proguard-annotations:1.5.1'
implementation "androidx.appcompat:appcompat:1.7.0" // Add AppCompat library
implementation "com.google.android.material:material:1.12.0" // Add Material Components
}
flutter {
source = "../.."
}
progaurd-rules.pro file
-------------------------
# Keep Razorpay related classes
-keepclassmembers class * {
@com.razorpay.** *;
}
-keep class com.razorpay.** {*;}
# Keep required annotations
-keepattributes *Annotation*
-dontwarn com.razorpay.**
# Additional rules for payment callbacks
-keepclasseswithmembers class * {
public void onPayment*(...);
}
# Prevent R8 from failing on the missing ProGuard annotations
-dontwarn proguard.annotation.**
```
### Actual results
### Logs
<details open>
<summary>Logs</summary>
```console
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:checkReleaseAarMetadata'.
> Could not resolve all files for configuration ':app:releaseRuntimeClasspath'.
> Could not find com.android.tools.build:proguard-annotations:1.5.1.
Searched in the following locations:
- https://dl.google.com/dl/android/maven2/com/android/tools/build/proguard-annotations/1.5.1/proguard-annotations-1.5.1.pom
- https://repo.maven.apache.org/maven2/com/android/tools/build/proguard-annotations/1.5.1/proguard-annotations-1.5.1.pom
- https://storage.googleapis.com/download.flutter.io/com/android/tools/build/proguard-annotations/1.5.1/proguard-annotations-1.5.1.pom
Required by:
project :app
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
BUILD FAILED in 7s
Running Gradle task 'assembleRelease'... 8.1s
Gradle task assembleRelease failed with exit code 1
```
</details>
### Flutter Doctor output
<details open>
<summary>Doctor output</summary>
```console
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.27.1, on Microsoft Windows [Version 10.0.22621.4317], locale en-IN)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[√] Chrome - develop for the web
[X] Visual Studio - develop Windows apps
X Visual Studio not installed; this is necessary to develop Windows apps.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2024.1)
[√] VS Code (version 1.95.3)
[√] Connected device (3 available)
[√] Network resources
! Doctor found issues in 1 category.
```
</details>
| waiting for customer response,in triage | low | Critical |
2,797,526,168 | rust | ICE: `ConstEvaluatable(UnevaluatedConst .. has escaping bound vars, so it cannot be wrapped in a dummy binder.` | <!--
[31mICE[0m: Rustc ./a.rs '-Zcrate-attr=feature(generic_const_exprs) -ooutputfile -Zdump-mir-dir=dir' 'thread 'rustc' panicked at compiler/rustc_middle/src/ty/predicate.rs:511:26: '`ConstEvaluatable(UnevaluatedConst { def: DefId(0:8 ~ a[5f0f]::S::{constant#0}), args: ['^0.Named(DefId(0:16 ~ a[5f0f]::{extern#0}::lint_me::'_), "'_"), '^1.Named(DefId(0:17 ~ a[5f0f]::{extern#0}::lint_me::'_#1), "'_")] })` has escaping bound vars, so it cannot be wrapped in a dummy binder.'', 'thread 'rustc' panicked at compiler/rustc_middle/src/ty/predicate.rs:511:26: '`ConstEvaluatable(UnevaluatedConst { def: DefId(0:8 ~ a[5f0f]::S::{constant#0}), args: ['^0.Named(DefId(0:16 ~ a[5f0f]::{extern#0}::lint_me::'_), "'_"), '^1.Named(DefId(0:17 ~ a[5f0f]::{extern#0}::lint_me::'_#1), "'_")] })` has escaping bound vars, so it cannot be wrapped in a dummy binder.''
File: /tmp/im/a.rs
-->
auto-reduced (treereduce-rust):
````rust
#![feature(generic_const_exprs)]
type Bar<T> = T;
type S<'l> = [i32; A];
extern "C" {
pub fn lint_me(x: Bar<S<{}>>);
}
````
original:
````rust
// Regression test for issue #119295.
#![feature(type_alias_impl_trait)]
type Bar<T> = T;
type S<'l, 'same_pattern> = [i32; A];
extern "C" {
pub fn lint_me(
x: Bar<
S<
{ //~ ERROR mismatched types
pub type Sum<A, B> = <A as Add<B>>::Output;
//~^ ERROR unconstrained opaque type
},
>,
>,
);
}
fn main() {}
````
Version information
````
rustc 1.86.0-nightly (c62b73272 2025-01-19)
binary: rustc
commit-hash: c62b732724b6beb50a5c73be26d0c5f668504059
commit-date: 2025-01-19
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
````
Possibly related line of code:
https://github.com/rust-lang/rust/blob/c62b732724b6beb50a5c73be26d0c5f668504059/compiler/rustc_middle/src/ty/predicate.rs#L505-L517
Command:
`/home/matthias/.rustup/toolchains/master/bin/rustc -Zcrate-attr=feature(generic_const_exprs)`
<details><summary><strong>Program output</strong></summary>
<p>
```
error[E0425]: cannot find value `A` in this scope
--> /tmp/icemaker_global_tempdir.7oeLQrIl66wL/rustc_testrunner_tmpdir_reporting.YAHMJ2htoVtz/mvce.rs:2:20
|
2 | type S<'l> = [i32; A];
| ^ not found in this scope
warning: the feature `generic_const_exprs` is incomplete and may not be safe to use and/or cause compiler crashes
--> <crate attribute>:1:9
|
1 | feature(generic_const_exprs)
| ^^^^^^^^^^^^^^^^^^^
|
= note: see issue #76560 <https://github.com/rust-lang/rust/issues/76560> for more information
= note: `#[warn(incomplete_features)]` on by default
error[E0601]: `main` function not found in crate `mvce`
--> /tmp/icemaker_global_tempdir.7oeLQrIl66wL/rustc_testrunner_tmpdir_reporting.YAHMJ2htoVtz/mvce.rs:6:2
|
6 | }
| ^ consider adding a `main` function to `/tmp/icemaker_global_tempdir.7oeLQrIl66wL/rustc_testrunner_tmpdir_reporting.YAHMJ2htoVtz/mvce.rs`
error[E0107]: type alias takes 0 generic arguments but 1 generic argument was supplied
--> /tmp/icemaker_global_tempdir.7oeLQrIl66wL/rustc_testrunner_tmpdir_reporting.YAHMJ2htoVtz/mvce.rs:5:27
|
5 | pub fn lint_me(x: Bar<S<{}>>);
| ^ -- help: remove the unnecessary generic argument
| |
| expected 0 generic arguments
|
note: type alias defined here, with 0 generic parameters
--> /tmp/icemaker_global_tempdir.7oeLQrIl66wL/rustc_testrunner_tmpdir_reporting.YAHMJ2htoVtz/mvce.rs:2:6
|
2 | type S<'l> = [i32; A];
| ^
thread 'rustc' panicked at compiler/rustc_middle/src/ty/predicate.rs:511:26:
`ConstEvaluatable(UnevaluatedConst { def: DefId(0:7 ~ mvce[281a]::S::{constant#0}), args: ['^0.Named(DefId(0:11 ~ mvce[281a]::{extern#0}::lint_me::'_), "'_")] })` has escaping bound vars, so it cannot be wrapped in a dummy binder.
stack backtrace:
0: 0x7526136f57fa - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h913b3ba5a3fabe95
1: 0x752613e12da6 - core::fmt::write::hccd409e337a87e20
2: 0x752614d1dd51 - std::io::Write::write_fmt::hb2e39594285880b6
3: 0x7526136f5652 - std::sys::backtrace::BacktraceLock::print::hf55385c23ca0d98c
4: 0x7526136f7ad2 - std::panicking::default_hook::{{closure}}::hf1b1117dfff2dddd
5: 0x7526136f795a - std::panicking::default_hook::h8eb75fbb03af06c8
6: 0x752612855deb - std[3d5eca3a92bc4dab]::panicking::update_hook::<alloc[a0e257928d44e98b]::boxed::Box<rustc_driver_impl[a4e3be7b68e659d1]::install_ice_hook::{closure#1}>>::{closure#0}
7: 0x7526136f8653 - std::panicking::rust_panic_with_hook::hd4e13f60768f5c61
8: 0x7526136f834a - std::panicking::begin_panic_handler::{{closure}}::ha9e43821cab53039
9: 0x7526136f5cc9 - std::sys::backtrace::__rust_end_short_backtrace::h55a888377cfa5bc9
10: 0x7526136f800d - rust_begin_unwind
11: 0x7526103a8ae0 - core::panicking::panic_fmt::hd9c4ffd61cb27733
12: 0x75261590d289 - <rustc_type_ir[6e983793a20e5c26]::binder::Binder<rustc_middle[7889754f33fd8966]::ty::context::TyCtxt, rustc_type_ir[6e983793a20e5c26]::predicate_kind::PredicateKind<rustc_middle[7889754f33fd8966]::ty::context::TyCtxt>>>::dummy.llvm.3867692987603750651.cold
13: 0x752615043438 - <rustc_middle[7889754f33fd8966]::ty::predicate::Clause as rustc_type_ir[6e983793a20e5c26]::upcast::UpcastFrom<rustc_middle[7889754f33fd8966]::ty::context::TyCtxt, rustc_type_ir[6e983793a20e5c26]::predicate_kind::ClauseKind<rustc_middle[7889754f33fd8966]::ty::context::TyCtxt>>>::upcast_from
14: 0x752612a4a1cc - <rustc_hir_analysis[3c8bb58bae5ad588]::collect::predicates_of::const_evaluatable_predicates_of::{closure#0}::ConstCollector as rustc_type_ir[6e983793a20e5c26]::visit::TypeVisitor<rustc_middle[7889754f33fd8966]::ty::context::TyCtxt>>::visit_const
15: 0x752614bbfb7c - rustc_hir_analysis[3c8bb58bae5ad588]::collect::predicates_of::gather_explicit_predicates_of
16: 0x752614bb786f - rustc_query_impl[8699b96174aa9f14]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[8699b96174aa9f14]::query_impl::explicit_predicates_of::dynamic_query::{closure#2}::{closure#0}, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 24usize]>>
17: 0x752614069230 - rustc_query_system[afaedc2be035c28b]::query::plumbing::try_execute_query::<rustc_query_impl[8699b96174aa9f14]::DynamicConfig<rustc_query_system[afaedc2be035c28b]::query::caches::DefIdCache<rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 24usize]>>, false, false, false>, rustc_query_impl[8699b96174aa9f14]::plumbing::QueryCtxt, false>
18: 0x752614068a68 - rustc_query_impl[8699b96174aa9f14]::query_impl::explicit_predicates_of::get_query_non_incr::__rust_end_short_backtrace
19: 0x752614067106 - rustc_hir_analysis[3c8bb58bae5ad588]::collect::predicates_of::predicates_of
20: 0x752614067013 - rustc_query_impl[8699b96174aa9f14]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[8699b96174aa9f14]::query_impl::predicates_of::dynamic_query::{closure#2}::{closure#0}, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 24usize]>>
21: 0x752614069219 - rustc_query_system[afaedc2be035c28b]::query::plumbing::try_execute_query::<rustc_query_impl[8699b96174aa9f14]::DynamicConfig<rustc_query_system[afaedc2be035c28b]::query::caches::DefIdCache<rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 24usize]>>, false, false, false>, rustc_query_impl[8699b96174aa9f14]::plumbing::QueryCtxt, false>
22: 0x752614068968 - rustc_query_impl[8699b96174aa9f14]::query_impl::predicates_of::get_query_non_incr::__rust_end_short_backtrace
23: 0x75261449b2cd - <rustc_hir_analysis[3c8bb58bae5ad588]::collect::CollectItemTypesVisitor as rustc_hir[d75fc7391b460916]::intravisit::Visitor>::visit_item
24: 0x7526144adde5 - rustc_hir_analysis[3c8bb58bae5ad588]::check::wfcheck::check_well_formed
25: 0x7526144adbe3 - rustc_query_impl[8699b96174aa9f14]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[8699b96174aa9f14]::query_impl::check_well_formed::dynamic_query::{closure#2}::{closure#0}, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 1usize]>>
26: 0x7526144ad685 - rustc_query_system[afaedc2be035c28b]::query::plumbing::try_execute_query::<rustc_query_impl[8699b96174aa9f14]::DynamicConfig<rustc_data_structures[f5b7eb2b075db7e5]::vec_cache::VecCache<rustc_span[4d8b97697ec1bb1a]::def_id::LocalDefId, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 1usize]>, rustc_query_system[afaedc2be035c28b]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[8699b96174aa9f14]::plumbing::QueryCtxt, false>
27: 0x7526144ad101 - rustc_query_impl[8699b96174aa9f14]::query_impl::check_well_formed::get_query_non_incr::__rust_end_short_backtrace
28: 0x7526144aa52c - rustc_hir_analysis[3c8bb58bae5ad588]::check::wfcheck::check_mod_type_wf
29: 0x7526144aa34b - rustc_query_impl[8699b96174aa9f14]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[8699b96174aa9f14]::query_impl::check_mod_type_wf::dynamic_query::{closure#2}::{closure#0}, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 1usize]>>
30: 0x752614d5ab88 - rustc_query_system[afaedc2be035c28b]::query::plumbing::try_execute_query::<rustc_query_impl[8699b96174aa9f14]::DynamicConfig<rustc_query_system[afaedc2be035c28b]::query::caches::DefaultCache<rustc_span[4d8b97697ec1bb1a]::def_id::LocalModDefId, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 1usize]>>, false, false, false>, rustc_query_impl[8699b96174aa9f14]::plumbing::QueryCtxt, false>
31: 0x752614d5a930 - rustc_query_impl[8699b96174aa9f14]::query_impl::check_mod_type_wf::get_query_non_incr::__rust_end_short_backtrace
32: 0x7526142449a6 - rustc_hir_analysis[3c8bb58bae5ad588]::check_crate
33: 0x7526142413a2 - rustc_interface[9d7efb036b79b9b4]::passes::run_required_analyses
34: 0x752614d1955e - rustc_interface[9d7efb036b79b9b4]::passes::analysis
35: 0x752614d1952f - rustc_query_impl[8699b96174aa9f14]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[8699b96174aa9f14]::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 0usize]>>
36: 0x752614dd2d95 - rustc_query_system[afaedc2be035c28b]::query::plumbing::try_execute_query::<rustc_query_impl[8699b96174aa9f14]::DynamicConfig<rustc_query_system[afaedc2be035c28b]::query::caches::SingleCache<rustc_middle[7889754f33fd8966]::query::erase::Erased<[u8; 0usize]>>, false, false, false>, rustc_query_impl[8699b96174aa9f14]::plumbing::QueryCtxt, false>
37: 0x752614dd2ace - rustc_query_impl[8699b96174aa9f14]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
38: 0x752614d97129 - rustc_interface[9d7efb036b79b9b4]::passes::create_and_enter_global_ctxt::<core[79ca29a2cb0a3e36]::option::Option<rustc_interface[9d7efb036b79b9b4]::queries::Linker>, rustc_driver_impl[a4e3be7b68e659d1]::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
39: 0x752614d67916 - rustc_interface[9d7efb036b79b9b4]::interface::run_compiler::<(), rustc_driver_impl[a4e3be7b68e659d1]::run_compiler::{closure#0}>::{closure#1}
40: 0x752614c99387 - std[3d5eca3a92bc4dab]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[9d7efb036b79b9b4]::util::run_in_thread_with_globals<rustc_interface[9d7efb036b79b9b4]::util::run_in_thread_pool_with_globals<rustc_interface[9d7efb036b79b9b4]::interface::run_compiler<(), rustc_driver_impl[a4e3be7b68e659d1]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>
41: 0x752614c99059 - <<std[3d5eca3a92bc4dab]::thread::Builder>::spawn_unchecked_<rustc_interface[9d7efb036b79b9b4]::util::run_in_thread_with_globals<rustc_interface[9d7efb036b79b9b4]::util::run_in_thread_pool_with_globals<rustc_interface[9d7efb036b79b9b4]::interface::run_compiler<(), rustc_driver_impl[a4e3be7b68e659d1]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core[79ca29a2cb0a3e36]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
42: 0x752614c987eb - std::sys::pal::unix::thread::Thread::new::thread_start::h634ec41480837481
43: 0x75260f06439d - <unknown>
44: 0x75260f0e949c - <unknown>
45: 0x0 - <unknown>
error: the compiler unexpectedly panicked. this is a bug.
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.86.0-nightly (c62b73272 2025-01-19) running on x86_64-unknown-linux-gnu
note: compiler flags: -Z crate-attr=feature(generic_const_exprs) -Z dump-mir-dir=dir
query stack during panic:
#0 [explicit_predicates_of] computing explicit predicates of `lint_me`
#1 [predicates_of] computing predicates of `lint_me`
#2 [check_well_formed] checking that `` is well-formed
#3 [check_mod_type_wf] checking that types are well-formed in top-level module
#4 [analysis] running analysis passes on this crate
end of query stack
error: aborting due to 3 previous errors; 1 warning emitted
Some errors have detailed explanations: E0107, E0425, E0601.
For more information about an error, try `rustc --explain E0107`.
```
</p>
</details>
<!--
query stack:
`ConstEvaluatable(UnevaluatedConst { def: DefId(0:7 ~ mvce[281a]::S::{constant#0}), args: ['^0.Named(DefId(0:11 ~ mvce[281a]::{extern#0}::lint_me::'_), "'_")] })` has escaping bound vars, so it cannot be wrapped in a dummy binder.
#0 [explicit_predicates_of] computing explicit predicates of `lint_me`
#1 [predicates_of] computing predicates of `lint_me`
#2 [check_well_formed] checking that `` is well-formed
#3 [check_mod_type_wf] checking that types are well-formed in top-level module
#4 [analysis] running analysis passes on this crate
-->
@rustbot label +F-type_alias_impl_trait +F-generic_const_exprs | I-ICE,T-compiler,C-bug,F-generic_const_exprs,S-has-mcve,S-has-bisection | low | Critical |
2,797,550,561 | go | net/http: Client.Timeout doesn't work when receiving a response from an incomplete WebSocket handshake | ### Go version
go version go1.23.4 linux/amd64
### Output of `go env` in your module/workspace:
```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE='pkg.go'
GOMODCACHE='/root/go/pkg/mod'
GOOS='linux'
GOPATH='/root/go'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/linuxbrew/.linuxbrew/Cellar/go/1.23.4/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/home/linuxbrew/.linuxbrew/Cellar/go/1.23.4/libexec/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.4'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/root/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/root/gotests/go.mod'
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 -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build670266472=/tmp/go-build -gno-record-gcc-switches'
```
### What did you do?
I encountered a situation where http.Client.Timeout doesn't work as expected when reading response body from an incomplete/fake WebSocket handshake response. Here's a minimal reproduction:
https://go.dev/play/p/i0mxl_6BaZR
### What did you see happen?
The client appears to be permanently blocked when reading the response body despite having a client timeout set. The timeout doesn't trigger as expected, and the operation hangs indefinitely.
### What did you expect to see?
When reading the response body from an incomplete WebSocket handshake (where server sends handshake headers but no data afterwards), the http.Client.Timeout setting should trigger after the specified timeout duration (5 seconds in this case) while reading the body. | NeedsInvestigation,BugReport | low | Critical |
2,797,557,119 | rust | Add `binary_format` to rustc target specs | There are some places in rustc that need to know the binary format of the target (to generate object files). It would be good to have this as a property on the target spec to avoid needing to have ad-hoc logic for it.
See https://github.com/rust-lang/rust/pull/135695#discussion_r1921122887 | C-cleanup,T-compiler,E-medium,A-target-specs,A-targets | low | Minor |
2,797,559,031 | ollama | Issue with Ollama Model Download: Progress Reverting During Download | ### What is the issue?
While downloading models using `ollama run <model_name>`, the progress often reverts—sometimes after 10-12% or even after 60%. The total download size also decreases before continuing. I've tested different networks but faced the same issue. A few weeks ago, I downloaded models without any problems.
### OS
macOS
### GPU
Apple
### CPU
Apple
### Ollama version
0.5.7 | bug | low | Major |
2,797,559,328 | vscode | The workbench failed to connect to the server (Error: WebSocket close with status code 1006) | ADD ISSUE DESCRIPTION HERE
Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36
Embedder: unknown
<!-- generated by web issue reporter --> | info-needed | low | Critical |
2,797,577,957 | flutter | Text Rendering Issue on Canvas After Flutter Update | ### Steps to reproduce
Dear Flutter Team,
I hope this message finds you well. After updating Flutter to the latest version, I've encountered an issue with text rendering on the canvas in my application. Previously, I used the canvas to display points and lines, with point names rendered as text. However, post-update, when zooming in, the point names appear very faint and are difficult to read; with further zooming, they disappear entirely. but in higher zoom levels there isn't a problem. This problem arose solely after updating Flutter, without any changes to my existing code.
I would appreciate any guidance or solutions you can provide to resolve this issue in the next update.
<img src="https://github.com/user-attachments/assets/a1c2dea6-15b8-44f8-ab9f-d055627244be" width="300" />
<img src="https://github.com/user-attachments/assets/77bddebc-3c32-4f0a-a22d-0b0a22cf3700" width="300" />
<img src="https://github.com/user-attachments/assets/d17f44a7-d9a5-445f-9907-1752a9e5f2c4" width="300" />
### Expected results
<img src="https://github.com/user-attachments/assets/92a2017b-350c-4480-9c4e-a45eb929f8e4" width="300" />
### Actual results
<img src="https://github.com/user-attachments/assets/38a8b0a5-4578-4a55-94db-ce4832cef0ea" width="300" />
<img src="https://github.com/user-attachments/assets/48865dc5-0c6e-45b6-b7be-e8e7991f1848" width="300" />
### Code sample
```dart
@override
void paint(Canvas canvas, Size size) {
canvas.translate(translateX, translateY);
canvas.scale(paintScale);
final ciPaint = Paint()
..color = Colors.black
..strokeWidth = 1 / paintScale
..style = PaintingStyle.stroke;
final pointPaint = Paint()
..strokeWidth = 0.5 / paintScale
..strokeCap = StrokeCap.square;
.
.
.
for (int i = 0; i < points.length; i++) {
if (layersKeys.contains(points[i].layer)) {
if (layers[layersKeys.indexOf(points[i].layer)].visibility) {
pointPaint.color = points[i].selected
? Colors.red
: points[i].key == 'device_name_loc_point'
? orangeColor
: Color(
layers[layersKeys.indexOf(points[i].layer)].colorValue);
canvas.drawCircle(
Offset(points[i].dX, points[i].dY), 5 / paintScale, pointPaint);
TextSpan span = TextSpan(
text: points[i].name!,
style: TextStyle(
color: points[i].key == 'device_name_loc_point'
? orangeColor
: points[i].selected
? Colors.red
: Color(layers[layersKeys.indexOf(points[i].layer)]
.colorValue),
fontSize: 0.2 * cadScale,
),
);
TextPainter tp = TextPainter(
text: span,
textAlign: TextAlign.left,
textDirection: TextDirection.ltr,
);
tp.layout();
double textX = points[i].dX;
double textY = points[i].dY;
canvas.save();
canvas.translate(textX, textY);
tp.paint(canvas, Offset(0.01, 0.01));
canvas.restore();
}
}
}
```
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.27.2, on Microsoft Windows [Version 10.0.19045.5371], locale fa-IR)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Enterprise 2022 17.7.5)
[√] Android Studio (version 2024.2)
[√] Connected device (4 available)
[√] Network resources
| waiting for customer response,in triage | low | Major |
2,797,580,890 | pytorch | CUDA initialization error with vLLM 0.5.4 and PyTorch 2.4.0+cu121 | ### 🐛 Describe the bug
CUDA initialization error in forked subprocesses when using **vLLM 0.5.4 with PyTorch 2.4.0+cu121**. The same code works with vLLM 0.5.0 and PyTorch 2.3.0+cu121, but fails with newer versions (vLLM 0.6.2 with PyTorch 2.5.1+cu121).
**Error Message:**
```
RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
```
**Environment:**
- vLLM: 0.5.4 (Also tested with 0.6.2)
- PyTorch: 2.4.0+cu121 (Also tested with 2.5.1+cu121)
- CUDA: 12.2
- GPU Driver: 535.54.03
- OS: [Add your operating system here]
**Steps to Reproduce:**
1. Install vLLM 0.5.4 and PyTorch 2.4.0+cu121
2. Set the following environment variables:
```bash
export PYTHONMULTIPROCESSING_START_METHOD=spawn
export CUDA_VISIBLE_DEVICES="0,1,2,3,4,5,6,7"
export VLLM_USE_SPAWN=1
export PYTHONPATH="${PYTHONPATH}:/mnt/data/taoshuchang.tsc/IR_RAG/IRM"
export MASTER_PORT=29500
export MASTER_ADDR=localhost
export WORLD_SIZE=$(echo $CUDA_VISIBLE_DEVICES | tr ',' '\n' | wc -l)
export CUDA_DEVICE_ORDER=PCI_BUS_ID
```
3. Run a script that uses vLLM to load a large language model (e.g., LLaMA 3.3-70B)
4. Observe the CUDA initialization error in forked subprocesses
**Additional Context:**
- This issue doesn't occur with vLLM 0.5.0 and PyTorch 2.3.0+cu121
- vLLM 0.5.4 is required to load LLaMA 3.3, which necessitates PyTorch 2.4.0+cu121
**Questions:**
1. Is this a known issue with PyTorch 2.4.0+cu121 and newer versions?
2. Are there any workarounds or configurations to resolve this issue?
3. Is there a compatibility matrix for vLLM, PyTorch, and CUDA versions?
**Attempted Solutions:**
- Tried vLLM 0.6.2 with PyTorch 2.5.1+cu121, but encountered the same error
- Set `PYTHONMULTIPROCESSING_START_METHOD=spawn` as suggested in error message
**Full error trace:**
```
INFO 01-19 03:55:21 config.py:899] Defaulting to use mp for distributed inference
INFO 01-19 03:55:21 llm_engine.py:226] Initializing an LLM engine (v0.6.1.dev238+ge2c6e0a82) with config: model='/mnt/data/taoshuchang.tsc/IR_RAG/ckpt/hotpot_contriever/analyze_merge//hotpot_1doc_other_Meta-Llama-3-70B-Instruct_lr1e5', speculative_config=None, tokenizer='/mnt/data/taoshuchang.tsc/IR_RAG/ckpt/hotpot_contriever/analyze_merge//hotpot_1doc_other_Meta-Llama-3-70B-Instruct_lr1e5', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, override_neuron_config=None, rope_scaling=None, rope_theta=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.bfloat16, max_seq_len=8192, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=8, pipeline_parallel_size=1, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None, collect_model_forward_time=False, collect_model_execute_time=False), seed=0, served_model_name=/mnt/data/taoshuchang.tsc/IR_RAG/ckpt/hotpot_contriever/analyze_merge//hotpot_1doc_other_Meta-Llama-3-70B-Instruct_lr1e5, use_v2_block_manager=False, num_scheduler_steps=1, multi_step_stream_outputs=False, enable_prefix_caching=False, use_async_output_proc=True, use_cached_outputs=False, mm_processor_kwargs=None)
WARNING 01-19 03:55:22 multiproc_gpu_executor.py:53] Reducing Torch parallelism from 32 threads to 1 to avoid unnecessary CPU contention. Set OMP_NUM_THREADS in the external environment to tune this value as needed.
INFO 01-19 03:55:22 custom_cache_manager.py:17] Setting Triton cache manager to: vllm.triton_utils.custom_cache_manager:CustomCacheManager
[1;36m(VllmWorkerProcess pid=305)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
[1;36m(VllmWorkerProcess pid=305)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
[1;36m(VllmWorkerProcess pid=307)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=308)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=306)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=303)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=304)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
[1;36m(VllmWorkerProcess pid=307)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
[1;36m(VllmWorkerProcess pid=308)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
[1;36m(VllmWorkerProcess pid=303)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=306)[0;0m [1;36m(VllmWorkerProcess pid=303)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
[1;36m(VllmWorkerProcess pid=303)[0;0m [1;36m(VllmWorkerProcess pid=306)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
[1;36m(VllmWorkerProcess pid=306)[0;0m [1;36m(VllmWorkerProcess pid=303)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
[1;36m(VllmWorkerProcess pid=306)[0;0m [1;36m(VllmWorkerProcess pid=303)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
[1;36m(VllmWorkerProcess pid=302)[0;0m INFO 01-19 03:55:24 multiproc_worker_utils.py:218] Worker ready; awaiting tasks
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
[1;36m(VllmWorkerProcess pid=304)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] Exception in worker VllmWorkerProcess while processing method init_device: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method, Traceback (most recent call last):
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_worker_utils.py", line 226, in _run_worker_process
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] output = executor(*args, **kwargs)
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] ^^^^^^^^^^^^^^^^^^^^^^^^^
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 166, in init_device
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch.cuda.set_device(self.device)
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 478, in set_device
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] torch._C._cuda_setDevice(device)
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/cuda/__init__.py", line 305, in _lazy_init
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] raise RuntimeError(
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233] RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method
[1;36m(VllmWorkerProcess pid=302)[0;0m ERROR 01-19 03:55:24 multiproc_worker_utils.py:233]
ERROR 01-19 04:05:25 multiproc_worker_utils.py:120] Worker VllmWorkerProcess pid 305 died, exit code: -15
INFO 01-19 04:05:25 multiproc_worker_utils.py:124] Killing local vLLM worker processes
/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/_distutils_hack/__init__.py:54: UserWarning: Reliance on distutils from stdlib is deprecated. Users must rely on setuptools to provide the distutils module. Avoid importing distutils or import setuptools first, and avoid setting SETUPTOOLS_USE_DISTUTILS=stdlib. Register concerns at https://github.com/pypa/setuptools/issues/new?template=distutils-deprecation.yml
warnings.warn(
Traceback (most recent call last):
File "/mnt/data/taoshuchang.tsc/IR_RAG/IRM/inference_new.py", line 299, in <module>
main()
File "/mnt/data/taoshuchang.tsc/IR_RAG/IRM/inference_new.py", line 291, in main
evaluate_retrieval(
File "/mnt/data/taoshuchang.tsc/IR_RAG/IRM/inference_new.py", line 236, in evaluate_retrieval
llm = load_model(model_path, enable_lora=enable_lora)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/IR_RAG/IRM/inference_new.py", line 49, in load_model
llm = LLM(model=model_path, tensor_parallel_size=torch.cuda.device_count(), enable_lora=enable_lora)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/entrypoints/llm.py", line 214, in __init__
self.llm_engine = LLMEngine.from_engine_args(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/engine/llm_engine.py", line 564, in from_engine_args
engine = cls(
^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/engine/llm_engine.py", line 325, in __init__
self.model_executor = executor_class(
^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/distributed_gpu_executor.py", line 26, in __init__
super().__init__(*args, **kwargs)
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/executor_base.py", line 47, in __init__
self._init_executor()
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_gpu_executor.py", line 110, in _init_executor
self._run_workers("init_device")
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/executor/multiproc_gpu_executor.py", line 185, in _run_workers
driver_worker_output = driver_worker_method(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 176, in init_device
init_worker_distributed_environment(self.parallel_config, self.rank,
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/worker/worker.py", line 448, in init_worker_distributed_environment
init_distributed_environment(parallel_config.world_size, rank,
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/vllm/distributed/parallel_state.py", line 946, in init_distributed_environment
torch.distributed.init_process_group(
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/distributed/c10d_logger.py", line 83, in wrapper
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/distributed/c10d_logger.py", line 97, in wrapper
func_return = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/distributed/distributed_c10d.py", line 1520, in init_process_group
store, rank, world_size = next(rendezvous_iterator)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/distributed/rendezvous.py", line 221, in _tcp_rendezvous_handler
store = _create_c10d_store(
^^^^^^^^^^^^^^^^^^^
File "/mnt/data/taoshuchang.tsc/anaconda3/envs/py311llama33/lib/python3.11/site-packages/torch/distributed/rendezvous.py", line 189, in _create_c10d_store
return TCPStore(
^^^^^^^^^
torch.distributed.DistStoreError: Timed out after 601 seconds waiting for clients. 1/8 clients joined.
ERROR conda.cli.main_run:execute(49): `conda run python -u /mnt/data/taoshuchang.tsc/IR_RAG/IRM/inference_new.py --test_data_path /mnt/data/taoshuchang.tsc/IR_RAG/IRM/datasets/hotpot_contriever/hotpot-dev.json --batch_size 4 --model_path /mnt/data/taoshuchang.tsc/IR_RAG/ckpt/hotpot_contriever/analyze_merge//hotpot_1doc_other_Meta-Llama-3-70B-Instruct_lr1e5 --result_save_path /mnt/data/taoshuchang.tsc/IR_RAG/IRM/result/hotpot_contriever/analyze/hotpot_1doc_other_Meta-Llama-3-70B-Instruct_lr1e5.json --batch True` failed. (See above for error)
```
Thank you for your help in resolving this issue.
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o | oncall: distributed | low | Critical |
2,797,591,487 | go | os: ReadDir in freebsd 14.1 can not list if path have chinese char | ### Go version
go 1.21 amd64
### Output of `go env` in your module/workspace:
```shell
no change
```
### What did you do?
OS.ReadDir use Chinese char path.I have test many paths. it is a real bug.
### What did you see happen?
it can not return file and folder.
### What did you expect to see?
return rightly. | OS-FreeBSD,WaitingForInfo,BugReport | medium | Critical |
2,797,594,645 | create-react-app | Error when running npm start after create-react-app | I am encountering an issue when trying to start a new React app using create-react-app. After running the commands below, I get the following error when executing npm start.
```
npx create-react-app client
cd client
npm start
```
The npm start command fails with the following error message:
```
> [email protected] start
> react-scripts start
Cannot find module 'ajv/dist/compile/codegen'
Require stack:
- /home/tanjil/stockmaster/client/node_modules/ajv-keywords/dist/definitions/typeof.js
- /home/tanjil/stockmaster/client/node_modules/ajv-keywords/dist/keywords/typeof.js
- /home/tanjil/stockmaster/client/node_modules/ajv-keywords/dist/keywords/index.js
- /home/tanjil/stockmaster/client/node_modules/ajv-keywords/dist/index.js
- /home/tanjil/stockmaster/client/node_modules/schema-utils/dist/validate.js
- /home/tanjil/stockmaster/client/node_modules/schema-utils/dist/index.js
- /home/tanjil/stockmaster/client/node_modules/webpack-dev-server/lib/Server.js
- /home/tanjil/stockmaster/client/node_modules/react-scripts/scripts/start.js
``` | needs triage,issue: bug report | low | Critical |
2,797,624,871 | PowerToys | Auto-Hide Taskbar Enhanced | ### Description of the new feature / enhancement
Its simple. Makes the taskbar auto-hide only when a window is maximized.
### Scenario when this would be used?
Internet navigation;
Image or video edit software;
Many others.
### Supporting information
Check this out:
https://windhawk.net/mods/taskbar-auto-hide-when-maximized
It's perfect!!! | Needs-Triage | low | Minor |
2,797,628,381 | rust | ICE could not unify `!` with revealed type | <!--
[31mICE[0m: Rustc ./a.rs '--edition=2024 -ooutputfile -Zdump-mir-dir=dir' 'error: internal compiler error: could not unify `!` with revealed type:', 'error: internal compiler error: could not unify `!` with revealed type:'
File: /tmp/im/a.rs
-->
auto-reduced (treereduce-rust):
````rust
//@compile-flags: --edition=2024
fn foo() -> impl ?Future<Output = impl Send> {
()
}
fn main() {}
````
original:
````rust
fn foo() -> impl ?Future<Output = impl Send> {
//~^ ERROR the size for values of type `impl ?Sized` cannot be known at compilation time
()
}
fn main() {}
````
Version information
````
rustc 1.86.0-nightly (678e669cc 2025-01-19)
binary: rustc
commit-hash: 678e669cc4aab51e3c3fff0660d45362fb830ebd
commit-date: 2025-01-19
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
````
Command:
`/home/matthias/.rustup/toolchains/master/bin/rustc --edition=2024`
<details><summary><strong>Program output</strong></summary>
<p>
```
warning: relaxing a default bound only does something for `?Sized`; all other traits are not bound by default
--> /tmp/icemaker_global_tempdir.qzKHRUKhhL4b/rustc_testrunner_tmpdir_reporting.uYhpe96WGOAh/mvce.rs:1:18
|
1 | fn foo() -> impl ?Future<Output = impl Send> {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: function `foo` is never used
--> /tmp/icemaker_global_tempdir.qzKHRUKhhL4b/rustc_testrunner_tmpdir_reporting.uYhpe96WGOAh/mvce.rs:1:4
|
1 | fn foo() -> impl ?Future<Output = impl Send> {
| ^^^
|
= note: `#[warn(dead_code)]` on by default
warning: 2 warnings emitted
note: no errors encountered even though delayed bugs were created
note: those delayed bugs will now be shown as internal compiler errors
error: internal compiler error: could not unify `()` with revealed type:
expected opaque type, found `()`
--> /tmp/icemaker_global_tempdir.qzKHRUKhhL4b/rustc_testrunner_tmpdir_reporting.uYhpe96WGOAh/mvce.rs:1:35
|
1 | fn foo() -> impl ?Future<Output = impl Send> {
| ^^^^^^^^^
|
note: delayed at compiler/rustc_hir_analysis/src/check/check.rs:396:34
0: <rustc_errors::DiagCtxtInner>::emit_diagnostic
1: <rustc_errors::DiagCtxtHandle>::emit_diagnostic
2: <rustc_span::ErrorGuaranteed as rustc_errors::diagnostic::EmissionGuarantee>::emit_producing_guarantee
3: <rustc_errors::DiagCtxtHandle>::span_delayed_bug::<rustc_span::span_encoding::Span, alloc::string::String>
4: rustc_hir_analysis::check::check::check_item_type
5: rustc_hir_analysis::check::wfcheck::check_well_formed
6: rustc_query_impl::plumbing::__rust_begin_short_backtrace::<rustc_query_impl::query_impl::check_well_formed::dynamic_query::{closure#2}::{closure#0}, rustc_middle::query::erase::Erased<[u8; 1]>>
7: rustc_query_system::query::plumbing::try_execute_query::<rustc_query_impl::DynamicConfig<rustc_data_structures::vec_cache::VecCache<rustc_span::def_id::LocalDefId, rustc_middle::query::erase::Erased<[u8; 1]>, rustc_query_system::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl::plumbing::QueryCtxt, false>
8: rustc_query_impl::query_impl::check_well_formed::get_query_non_incr::__rust_end_short_backtrace
9: rustc_middle::query::plumbing::query_ensure_error_guaranteed::<rustc_data_structures::vec_cache::VecCache<rustc_span::def_id::LocalDefId, rustc_middle::query::erase::Erased<[u8; 1]>, rustc_query_system::dep_graph::graph::DepNodeIndex>, ()>
10: rustc_hir_analysis::check::wfcheck::check_mod_type_wf
11: rustc_query_impl::plumbing::__rust_begin_short_backtrace::<rustc_query_impl::query_impl::check_mod_type_wf::dynamic_query::{closure#2}::{closure#0}, rustc_middle::query::erase::Erased<[u8; 1]>>
12: rustc_query_system::query::plumbing::try_execute_query::<rustc_query_impl::DynamicConfig<rustc_query_system::query::caches::DefaultCache<rustc_span::def_id::LocalModDefId, rustc_middle::query::erase::Erased<[u8; 1]>>, false, false, false>, rustc_query_impl::plumbing::QueryCtxt, false>
13: rustc_query_impl::query_impl::check_mod_type_wf::get_query_non_incr::__rust_end_short_backtrace
14: rustc_hir_analysis::check_crate
15: rustc_interface::passes::run_required_analyses
16: rustc_interface::passes::analysis
17: rustc_query_impl::plumbing::__rust_begin_short_backtrace::<rustc_query_impl::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle::query::erase::Erased<[u8; 0]>>
18: rustc_query_system::query::plumbing::try_execute_query::<rustc_query_impl::DynamicConfig<rustc_query_system::query::caches::SingleCache<rustc_middle::query::erase::Erased<[u8; 0]>>, false, false, false>, rustc_query_impl::plumbing::QueryCtxt, false>
19: rustc_query_impl::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
20: rustc_interface::passes::create_and_enter_global_ctxt::<core::option::Option<rustc_interface::queries::Linker>, rustc_driver_impl::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
21: rustc_interface::interface::run_compiler::<(), rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}
22: std::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<(), rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>
23: <<std::thread::Builder>::spawn_unchecked_<rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<(), rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
24: std::sys::pal::unix::thread::Thread::new::thread_start
25: <unknown>
26: <unknown>
--> /tmp/icemaker_global_tempdir.qzKHRUKhhL4b/rustc_testrunner_tmpdir_reporting.uYhpe96WGOAh/mvce.rs:1:35
|
1 | fn foo() -> impl ?Future<Output = impl Send> {
| ^^^^^^^^^
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.86.0-nightly (678e669cc 2025-01-19) running on x86_64-unknown-linux-gnu
note: compiler flags: -Z dump-mir-dir=dir
query stack during panic:
end of query stack
```
</p>
</details>
<!--
query stack:
-->
| I-ICE,P-medium,T-compiler,regression-from-stable-to-stable,A-impl-trait,C-bug,fixed-by-next-solver | low | Critical |
2,797,630,914 | neovim | Shell command not triggering Windows JIT debugger | ### Problem
If I use a shell command (`:!`) or `:term` to launch an EXE that fires an exception, the [Windows JIT debugger](https://learn.microsoft.com/en-us/visualstudio/debugger/debug-using-the-just-in-time-debugger?view=vs-2022) does not launch. If I run the same command from a regular cmd prompt (or if I launch the exe from my desktop), the debugger launches.
- The EXE launches fine if no exceptions fire so I'm not having trouble actually launching the executable
- I tried the same thing in native vim and was not able to reproduce the issue (`:!foo.exe` and starting a `:term` and running `foo.exe`)
Is there a difference in nvim's shell execution or terminal?
### Steps to reproduce
- Have `foo.exe` that triggers an exception
- Run `:!foo.exe` in nvim
### Expected behavior
Windows JIT debugger launches if EXE hits exception.
### Nvim version (nvim -v)
0.10.2
### Vim (not Nvim) behaves the same?
no, vim 9.1.0.0
### Operating system/version
Windows 10
### Terminal name/version
Native command prompt (cmd.exe)
### $TERM environment variable
N/A, using Windows
### Installation
https://github.com/neovim/neovim/blob/master/INSTALL.md#install-from-download | platform:windows,terminal,system | low | Critical |
2,797,632,697 | tauri | [bug] Opening a webview window from Rust on linux fails parsing the url | ### Describe the bug
Sometimes when opening a webview window on Linux from Rust with ``` WebviewUrl::App ``` the window opens but the url of it is ``` Err(InvalidUrl(RelativeUrlWithoutBase)) ```. This causes the window to be empty.
I say sometimes because this problem goes away somewhat randomly. Things that made it disappear are not closing the splash screen and disabling the splash screen.
### Reproduction
Have an new_playlist.html in the public directory ``` {project}/public/new_playlist.html ```.
```
let window_url = "/new_playlist.html";
println!("window url: {}", window_url);
let new_window = tauri::WebviewWindowBuilder::new(
&app,
"new_playlist",
WebviewUrl::App(window_url.into())
).build();
match new_window {
Ok(_window) => {
println!("Window created: {:?}", _window.url());
_window.set_title("New Playlist");
_window.set_size(tauri::LogicalSize::new(200, 200));
_window.show();
},
Err(e) => {
error!("Error creating window {label}: {e}");
return Err(())
},
};
```
### Expected behavior
The url of the window gets recognized correctly and the webview content loads.
### Full `tauri info` output
```text
[✔] Environment
- OS: Manjaro 24.2.1 x86_64 (X64)
✔ webkit2gtk-4.1: 2.46.4
✔ rsvg2: 2.59.2
✔ rustc: 1.84.0 (9fc6b4312 2025-01-07)
✔ cargo: 1.84.0 (66221abde 2024-11-19)
✔ rustup: 1.27.1 (2024-05-07)
✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
- node: 23.3.0
- npm: 10.9.2
[-] Packages
- tauri 🦀: 2.2.3
- tauri-build 🦀: 2.0.5
- wry 🦀: 0.48.1
- tao 🦀: 0.31.1
- tauri-cli 🦀: 2.0.2
- @tauri-apps/api : 2.2.0
- @tauri-apps/cli : 2.0.2 (outdated, latest: 2.2.5)
[-] Plugins
- tauri-plugin-fs 🦀: 2.0.1
- @tauri-apps/plugin-fs : 2.2.0
- tauri-plugin-shell 🦀: 2.2.0
- @tauri-apps/plugin-shell : 2.2.0
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
- framework: React
- bundler: Vite
```
### Stack trace
```text
```
### Additional context
tauri.conf.json
```
{
"$schema": "https://schema.tauri.app/config/2.0.0",
"productName": "test",
"version": "0.1.0",
"identifier": "com.test.app",
"build": {
"beforeDevCommand": "npm run dev",
"devUrl": "http://localhost:1420",
"beforeBuildCommand": "npm run build",
"frontendDist": "../dist"
},
"app": {
"windows": [
{
"title": "app",
"width": 800,
"height": 600
},
{
"width": 400,
"height": 200,
"visible": true,
"decorations": false,
"url": "/splashscreen.html",
"label": "splashscreen"
}
],
"security": {
"csp": null,
"capabilities": ["default"],
"assetProtocol": {
"enable": true,
"scope": [
"*/**"
]
}
}
},
"bundle": {
"active": true,
"targets": "all",
"icon": [
"icons/32x32.png",
"icons/128x128.png",
"icons/[email protected]",
"icons/icon.icns",
"icons/icon.ico"
]
}
}
``` | type: bug,status: needs triage | low | Critical |
2,797,637,658 | tensorflow | Force TF to log GPU memory allocation | ### Issue type
Feature Request
### Have you reproduced the bug with TensorFlow Nightly?
Yes
### Source
binary
### TensorFlow version
2.18.0
### Custom code
No
### OS platform and distribution
Debian 12
### Mobile device
_No response_
### Python version
3.11.2
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
12.2
### GPU model and memory
RTX 3060 12Gb
### Current behavior?
If I ran out of GPU memory I get error saying
`Allocator (GPU_0_bfc) ran out of memory trying to allocate 9.78GiB`
But if allocation succeeded there is no real way to know what the allocator did/doing.. I know that you can use nvidia-smi etc but this is an indirect way to estimate very crudely whats going on.
What I believe would be very beneficial (because I dont know about you guys but I run out of memory so very often and I cant affort 128Gb card) - is to be able to force TF to log every and single one GPU memory allocation.
So I can see whats going on my healthy models and whats in the failing. | stat:awaiting tensorflower,type:feature,comp:gpu | medium | Critical |
2,797,659,079 | godot | Button groups do not return to default state after scene reloads / changing scenes | ### Tested versions
Godot v4.3.stable
### System information
Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti (NVIDIA; 32.0.15.6636) - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)
### Issue description
Given a set of buttons in a button_group (with toggle_mode enabled, allow unpress, and a default selected button with button_pressed enabled) --
If one changes the toggle state of buttons in the group (for example, by selecting another button), then reloads the scene (via get_tree().reload_current_scene() or similar) the button group will retain memory of the last state instead of refreshing to the default state of the scene. Additionally these states will mix:
Scenario:
Button A, B, C (Button A is selected by default)
Select button B
Reload the scene
Button A and Button B both appear in pressed state
### Steps to reproduce
I haven't been able to duplicate this yet in a simple project, but I've had this happen to me on a couple of different projects recently.
Have to manually reset the button groups to default state every time I reload the scene.
### Minimal reproduction project (MRP)
TBD | topic:editor,needs testing,topic:gui | low | Minor |
2,797,660,502 | flutter | Allow specifying `TextField.maxLines` inside a `DropdownMenu` | ### Use case
When `dropdownMenuEntries` are lengthy it might be useful to have a multiline `DropdownMenu`. By default, the text is cut off after the first line.
### Proposal
Allow specifying `TextField.maxLines` from the `DropdownMenu` constructor - this is trivial. | framework,f: material design,c: proposal,P2,team-design,triaged-design | low | Minor |
2,797,673,541 | godot | Node references in typed dictionaries are always null (C# / 4.4 beta 1) | ### Tested versions
- Tested in 4.4 beta 1
### System information
Godot v4.4.beta1.mono - Windows 11 (build 26100) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Ti (NVIDIA; 32.0.15.6636) - 13th Gen Intel(R) Core(TM) i9-13900KF (32 threads)
### Issue description
Assigning Nodes to values in typed dictionaries in the editor results in values always beeing null when running the script
Dictionary in the inspector:
<img width="369" alt="Image" src="https://github.com/user-attachments/assets/e4aeb8ce-7f77-497e-a647-b484dff55860" />
The script (with "Node" as value)
<img width="814" alt="Image" src="https://github.com/user-attachments/assets/8f78ce3f-b1ab-4ee8-a777-2d2f546c3832" />
Even with attached script it is not working
<img width="742" alt="Image" src="https://github.com/user-attachments/assets/98aed88d-4981-42a6-8acd-d3bf9654172d" />
### Steps to reproduce
1. Create a typed dictionary
2. Assign a node to value in the inspector
3. run the script
### Minimal reproduction project (MRP)
[typeddictionaryerror.zip](https://github.com/user-attachments/files/18469238/typeddictionaryerror.zip) | bug,topic:dotnet | low | Critical |
2,797,679,390 | godot | All connected signals are deleted at any time | ### Tested versions
Godot Engine 4.4 beta 1
### System information
Windows 11 24H2
### Issue description
At any time, all signals in the scene are off. This happens at completely random times, and I can't figure out why
It's very sad because I can't reproduce this error, I can't understand why it happens, I can't submit the project where it happens because it's my main project and I can't distribute its open source code.
I only know that this problem was in 4.1, 4.2, 4.3 and 4.4 beta 1 because it has happened many times before and I was just hoping it would be fixed in the future
It's sad because I constantly have to spend a lot of time reconnecting signals
That's all I can say, I'm sorry
### Steps to reproduce
All I can provide: My signals have arguments - string, int
### Minimal reproduction project (MRP)
I can't reproduce it. It happens at random times | bug,topic:editor | low | Critical |
2,797,681,012 | ollama | Add Tool Calling to the Generate Function | It appears from the API documentation and code examples available that tool calling is only possible with chat(). If this capability is feasible to add to generate() it would be much appreciated!
| feature request | low | Minor |
2,797,683,650 | PowerToys | bug | ### Microsoft PowerToys version
0.85.1.0
### Installation method
PowerToys auto-update
### Running as admin
Yes
### Area(s) with issue?
General
### Steps to reproduce
Version: 0.85.1.0
OS Version: Microsoft Windows NT 10.0.27768.0
IntPtr Length: 8
x64: True
Date: 2025/1/20 月 AM 12:18:53
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {デスクトップ構成が無効化されています} デスクトップ構成が無効化されているために、操作を完了できませんでした。 (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Shell.WindowChromeWorker._ExtendGlassFrame()
at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force)
at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
### ✔️ Expected Behavior
_No response_
### ❌ Actual Behavior
_No response_
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Critical |
2,797,683,998 | PowerToys | PowerToys Keyboard Manager Interferes with Gaming | ### Provide a description of requested docs changes
Description:
I have recently installed PowerToys on my Windows system, and I'm experiencing an issue with the Keyboard Manager feature.
The Problem:
Whenever I press any alphabet key followed by the spacebar, the Keyboard Manager unexpectedly inserts special characters. This behavior significantly disrupts gameplay, as it prevents me from performing simultaneous actions like moving and jumping in games, which often require pressing a direction key and the spacebar.
Impact:
This issue renders PowerToys unusable for gaming and creates a frustrating experience. I'm unable to enjoy games as intended due to this unexpected keyboard behavior.
Steps to Reproduce:
* Install PowerToys.
* Enable the Keyboard Manager feature.
* Launch a game that requires simultaneous key presses, such as an action game or platformer.
* Attempt to perform actions that involve pressing an alphabet key and the spacebar simultaneously.
* Observe the unintended insertion of special characters.
Expected Behavior:
The Keyboard Manager should not interfere with standard key combinations, allowing for smooth and uninterrupted gameplay.
System Information:
* Operating System: Windows 11
* PowerToys Version: v0.87.1
* Game Title: Minecraft
Workaround:
Temporarily disabling the Keyboard Manager within PowerToys settings resolves the issue, but this defeats the purpose of using the feature.
Request:
I kindly request that the Microsoft development team investigate this issue and provide a solution. This could involve:
* Bug Fix: Addressing the underlying issue that causes the unexpected character insertion.
* Configuration Option: Adding an option to close this feature for games. Or close it automatically while playing games.
I appreciate your time and attention to this matter.
Sincerely,
Priyansh Sen
[email protected]
I hope this report helps you effectively communicate the issue to Microsoft and find a resolution.
| Issue-Docs,Needs-Triage | low | Critical |
2,797,685,202 | flutter | Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0'], Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by settings file 'settings.gradle' | ### Steps to reproduce
This is a follow-up to https://github.com/flutter/flutter/issues/144751 which still persist:
I created a fresh project, but was immediately warned that my Java version 21 doesn't work for Gradle version 8.3,
and I'm offered to switch to the compatible Gradle version range: 8.4 - 8.7, which I did (I tried both 8.4 and 8.7),
but when I do that, I get the error
```
* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by settings file 'settings.gradle'
```
Please see the full experiment below:
```
mh@mh-mbp flutter % flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.2, on macOS 15.2 24C101 darwin-x64, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.96.4)
[✓] Connected device (4 available)
[✓] Network resources
• No issues found!
mh@mh-mbp flutter % flutter create test && cd test
Creating project test...
Resolving dependencies in `test`...
Downloading packages...
Got dependencies in `test`.
Wrote 130 files.
All done!
You can find general documentation for Flutter at: https://docs.flutter.dev/
Detailed API documentation is available at: https://api.flutter.dev/
If you prefer video documentation, consider: https://www.youtube.com/c/flutterdev
In order to run your application, type:
$ cd test
$ flutter run
Your application code is in test/lib/main.dart.
The configured version of Java detected may conflict with the Gradle version in your new Flutter app.
To keep the default AGP version Gradle version 8.3, download a compatible Java version
(Java 17 <= (Java 17 <= compatible Java version < Java 21) Java version < Java 21). Configure this Java version
globally for Flutter by running:
flutter config --jdk-dir=<JDK_DIRECTORY>
Alternatively, to continue using your configured Java version, update the Gradle
version specified in the following file to a compatible Gradle version (compatible Gradle version range: 8.4 - 8.7):
/Users/mh/flutter/test/android/gradle/wrapper/gradle-wrapper.properties
You may also update the Gradle version used by running
`./gradlew wrapper --gradle-version=<COMPATIBLE_GRADLE_VERSION>`.
See
https://docs.gradle.org/current/userguide/compatibility.html#java for details
on compatible Java/Gradle versions, and see
https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:upgrading_wrapper
for more details on using the Gradle Wrapper command to update the Gradle version
used.
mh@mh-mbp test % nano /Users/mh/flutter/test/android/gradle/wrapper/gradle-wrapper.properties
mh@mh-mbp test % cat /Users/mh/flutter/test/android/gradle/wrapper/gradle-wrapper.properties
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.4-all.zip
mh@mh-mbp test % flutter run
Launching lib/main.dart on Nexus 6P in debug mode...
FAILURE: Build failed with an exception.
* Where:
Settings file '/Users/mh/flutter/test/android/settings.gradle' line: 20
* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by settings file 'settings.gradle'
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
BUILD FAILED in 662ms
Running Gradle task 'assembleDebug'... 1.519ms
Error: Gradle task assembleDebug failed with exit code 1
```
### Expected results
Build should work with Java Version 21 and Android Gradle Plugin 8.4 or 8.7
### Actual results
```
FAILURE: Build failed with an exception.
* Where:
Settings file '/Users/mh/flutter/test/android/settings.gradle' line: 20
* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by settings file 'settings.gradle'
```
### Code sample
<details open><summary>Sample</summary>
```console
flutter create test
```
</details>
### Screenshots or Video
n/a
### Logs
<details open><summary>Logs</summary>
```console
mh@mh-mbp flutter % flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.2, on macOS 15.2 24C101 darwin-x64, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.96.4)
[✓] Connected device (4 available)
[✓] Network resources
• No issues found!
mh@mh-mbp flutter % flutter create test && cd test
Creating project test...
Resolving dependencies in `test`...
Downloading packages...
Got dependencies in `test`.
Wrote 130 files.
All done!
You can find general documentation for Flutter at: https://docs.flutter.dev/
Detailed API documentation is available at: https://api.flutter.dev/
If you prefer video documentation, consider: https://www.youtube.com/c/flutterdev
In order to run your application, type:
$ cd test
$ flutter run
Your application code is in test/lib/main.dart.
The configured version of Java detected may conflict with the Gradle version in your new Flutter app.
To keep the default AGP version Gradle version 8.3, download a compatible Java version
(Java 17 <= (Java 17 <= compatible Java version < Java 21) Java version < Java 21). Configure this Java version
globally for Flutter by running:
flutter config --jdk-dir=<JDK_DIRECTORY>
Alternatively, to continue using your configured Java version, update the Gradle
version specified in the following file to a compatible Gradle version (compatible Gradle version range: 8.4 - 8.7):
/Users/mh/flutter/test/android/gradle/wrapper/gradle-wrapper.properties
You may also update the Gradle version used by running
`./gradlew wrapper --gradle-version=<COMPATIBLE_GRADLE_VERSION>`.
See
https://docs.gradle.org/current/userguide/compatibility.html#java for details
on compatible Java/Gradle versions, and see
https://docs.gradle.org/current/userguide/gradle_wrapper.html#sec:upgrading_wrapper
for more details on using the Gradle Wrapper command to update the Gradle version
used.
mh@mh-mbp test % nano /Users/mh/flutter/test/android/gradle/wrapper/gradle-wrapper.properties
mh@mh-mbp test % cat /Users/mh/flutter/test/android/gradle/wrapper/gradle-wrapper.properties
distributionBase=GRADLE_USER_HOME
distributionPath=wrapper/dists
zipStoreBase=GRADLE_USER_HOME
zipStorePath=wrapper/dists
distributionUrl=https\://services.gradle.org/distributions/gradle-8.4-all.zip
mh@mh-mbp test % flutter run
Launching lib/main.dart on Nexus 6P in debug mode...
FAILURE: Build failed with an exception.
* Where:
Settings file '/Users/mh/flutter/test/android/settings.gradle' line: 20
* What went wrong:
Error resolving plugin [id: 'dev.flutter.flutter-plugin-loader', version: '1.0.0']
> Build was configured to prefer settings repositories over project repositories but repository 'MavenRepo' was added by settings file 'settings.gradle'
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
BUILD FAILED in 662ms
Running Gradle task 'assembleDebug'... 1.519ms
Error: Gradle task assembleDebug failed with exit code 1
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.2, on macOS 15.2 24C101 darwin-x64, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.96.4)
[✓] Connected device (4 available)
[✓] Network resources
• No issues found!
```
verbose:
```
[✓] Flutter (Channel stable, 3.27.2, on macOS 15.2 24C101 darwin-x64, locale de-DE)
• Flutter version 3.27.2 on channel stable at /Users/mh/devtools/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 68415ad1d9 (6 days ago), 2025-01-13 10:22:03 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.1)
• Android SDK at /Users/mh/Library/Android/sdk
• Platform android-35, build-tools 35.0.1
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 21.0.4+-12422083-b607.1)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 16C5032a
• CocoaPods version 1.15.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.2)
• 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 21.0.4+-12422083-b607.1)
[✓] VS Code (version 1.96.4)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (4 available)
[✓] Network resources
• All expected network resources are available.
```
</details>
| waiting for customer response,in triage | low | Critical |
2,797,685,782 | flutter | [tool_crash] RPCError | ## Command
```sh
flutter run
```
## Steps to Reproduce
1. ...
2. ...
3. ...
## Logs
RPCError
```console
```
```console
[32m[✓][39m Flutter (Channel stable, 3.24.0, on macOS 14.5 23F79 darwin-arm64, locale tr-TR)
[32m•[39m Flutter version 3.24.0 on channel stable at /Users/emretufekci/Development/flutter
[32m•[39m Upstream repository https://github.com/flutter/flutter.git
[32m•[39m Framework revision 80c2e84975 (6 months ago), 2024-07-30 23:06:49 +0700
[32m•[39m Engine revision b8800d88be
[32m•[39m Dart version 3.5.0
[32m•[39m DevTools version 2.37.2
[32m[✓][39m Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[32m•[39m Android SDK at /Users/emretufekci/Library/Android/sdk
[32m•[39m Platform android-35, build-tools 35.0.0
[32m•[39m ANDROID_HOME = /Users/emretufekci/Library/Android/sdk
[32m•[39m Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
[32m•[39m Java version OpenJDK Runtime Environment (build 21.0.4+-12422083-b607.1)
[32m•[39m All Android licenses accepted.
[32m[✓][39m Xcode - develop for iOS and macOS (Xcode 15.3)
[32m•[39m Xcode at /Applications/Xcode.app/Contents/Developer
[32m•[39m Build 15E204a
[32m•[39m CocoaPods version 1.16.2
[32m[✓][39m Chrome - develop for the web
[32m•[39m Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[32m[✓][39m Android Studio (version 2024.2)
[32m•[39m Android Studio at /Applications/Android Studio.app/Contents
[32m•[39m Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
[32m•[39m Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
[32m•[39m Java version OpenJDK Runtime Environment (build 21.0.4+-12422083-b607.1)
[32m[✓][39m VS Code (version 1.96.4)
[32m•[39m VS Code at /Applications/Visual Studio Code.app/Contents
[32m•[39m Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[32m[✓][39m Connected device (4 available)
[32m•[39m sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64 • Android 14 (API 34) (emulator)
[32m•[39m macOS (desktop) • macos • darwin-arm64 • macOS 14.5 23F79 darwin-arm64
[32m•[39m Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 14.5 23F79 darwin-arm64
[32m•[39m Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.265
[33m![39m Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
[32m[✓][39m Network resources
[32m•[39m All expected network resources are available.
[32m•[39m No issues found!
```
## Flutter Application Metadata
**Type**: app
**Version**: 1.0.1+8
**Material**: true
**Android X**: false
**Module**: false
**Plugin**: false
**Android package**: null
**iOS bundle identifier**: null
**Creation channel**: main
**Creation framework version**: 76fe247aae53ca3e4ccf444c0dc02669e0b8f19e
### Plugins
awesome_notifications-0.10.0
device_info_plus-11.1.0
firebase_analytics-11.3.3
firebase_analytics_web-0.5.10+2
firebase_core-3.10.0
firebase_core_web-2.19.0
firebase_crashlytics-4.3.0
firebase_messaging-15.1.3
firebase_messaging_web-3.9.2
firebase_performance-0.10.1
firebase_performance_web-0.1.7+6
flutter_native_splash-2.4.2
google_sign_in-6.2.1
google_sign_in_android-6.1.33
google_sign_in_ios-5.7.8
google_sign_in_web-0.12.4+2
in_app_purchase-3.2.0
in_app_purchase_android-0.3.6+11
in_app_purchase_storekit-0.3.18+3
in_app_review-2.0.9
package_info_plus-8.1.0
path_provider-2.1.5
path_provider_android-2.2.12
path_provider_foundation-2.4.0
path_provider_linux-2.2.1
path_provider_windows-2.3.0
permission_handler-11.3.1
permission_handler_android-12.0.13
permission_handler_apple-9.4.5
permission_handler_html-0.1.3+2
permission_handler_windows-0.2.1
shared_preferences-2.3.2
shared_preferences_android-2.3.3
shared_preferences_foundation-2.5.3
shared_preferences_linux-2.4.1
shared_preferences_web-2.4.2
shared_preferences_windows-2.4.1
sign_in_with_apple-6.1.3
sign_in_with_apple_web-2.1.0
url_launcher-6.3.1
url_launcher_android-6.3.14
url_launcher_ios-6.3.1
url_launcher_linux-3.2.0
url_launcher_macos-3.2.1
url_launcher_web-2.3.3
url_launcher_windows-3.1.3
| waiting for customer response,in triage | low | Critical |
2,797,689,488 | transformers | TPU Initialization Error with Transformers in Kaggle TPU VM v3-8 | ### System Info
Title: Persistent TPU Initialization Error on Kaggle with Transformers Library
Issue Description
While running a script using the transformers library in the Kaggle environment with TPU enabled, we consistently encounter a TPU initialization error. Despite verifying all settings and configurations, the error persists. The script runs without issues on GPU, but fails on TPU.
Environment Details
Transformers Version: [Specify the version, e.g., 4.35.0]
PyTorch Version: [Specify the version, e.g., 2.0.1]
TPU Hardware: Kaggle TPU VM v3-8
Python Version: [e.g., 3.10]
Platform: Kaggle
Error Traceback
RuntimeError: Bad StatusOr access: UNKNOWN: TPU initialization failed: open(/dev/accel0): Operation not permitted: Couldn't open device: /dev/accel0; Unable to create Node RegisterInterface for node 0...
Steps to Reproduce
Enable TPU in the Kaggle environment.
Run the following command:
%cd aidiff
%cd improved-diffusion
!ls
!python transformers/examples/pytorch/language-modeling/run_clm.py \
--output_dir=classifier_models/e2e-tgt-tree_e=6_b=10_m=bert-base-uncased_wikitext-103-raw-v1_101_wp_None \
--model_name_or_path=bert-base-uncased \
--tokenizer_name=bert-base-uncased \
--per_device_train_batch_size=10 \
--per_device_eval_batch_size=10 \
--save_steps=50000 \
--num_train_epochs=6 \
--do_train \
--eval_steps=10000 \
--eval_strategy=steps \
--do_eval \
--dataloader_num_workers=4 \
--save_total_limit=1 \
--overwrite_output_dir \
--logging_dir=classifier_models/runs/e2e-tgt-tree_e=6_b=10_m=bert-base-uncased_wikitext-103-raw-v1_101_wp_None \
--block_size=100 \
--disable_tqdm=True \
--model_type=gpt2 \
--gradient_accumulation_steps=1 \
--seed=101 \
--dataset_name=wikitext \
--dataset_config_name=wikitext-103-raw-v1 \
--tpu_num_cores=8 \
--tpu_name=node-1 \
--use_tpu=True
Expected Behavior
The script should run seamlessly with TPU without encountering initialization errors.
Observed Behavior
TPU is correctly detected in the Kaggle environment.
TPU initialization fails with the provided error message.
Switching to GPU resolves the issue, but significantly increases runtime.
Debugging Efforts
Verified TPU configurations and compatibility with Kaggle.
Ensured the required libraries and dependencies are installed and up-to-date.
Performed manual debugging and consulted external resources (e.g., GPT-4).
Confirmed the learning step works perfectly on GPU but fails on TPU.
Current Workaround
Using GPU instead of TPU bypasses the issue but is not an ideal solution due to increased runtime and resource costs.
Request for Assistance
We believe this is a bug or a compatibility issue between the transformers library and Kaggle's TPU environment or a bug in TPU initialization. Any insights, fixes, or guidance to resolve this would be greatly appreciated.
### Who can help?
_No response_
### Information
- [ ] The official example scripts
- [ ] My own modified scripts
### Tasks
- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)
### Reproduction
Reproduction
Kaggle Notebook Link:
The issue occurs when running the script in the Kaggle environment. Here’s the notebook:
[Kaggle Notebook](https://www.kaggle.com/code/mautlej/aidiff)
GitHub Repository:
The repository being used for this implementation is:
[Diffusion-LM GitHub Repository](https://github.com/XiangLi1999/Diffusion-LM)
Steps to reproduce the behavior:
1. Clone the GitHub repository and navigate to the working directory:
```bash
!git clone https://github.com/XiangLi1999/Diffusion-LM.git
%cd Diffusion-LM
!pip install -r requirements.txt
Enable TPU in the Kaggle environment by selecting TPU VM v3-8 in notebook settings.
Run the training script using the following command:
python train_run.py --experiment e2e-tgt-tree --app "--init_emb diffusion_models/diff_roc_pad_rand128_transformer_lr0.0001_0.0_2000_sqrt_Lsimple_h128_s2_d0.1_sd101_xstart_e2e --n_embd 16 --learned_emb yes" --pretrained_model bert-base-uncased --epoch 6 --bsz 10
Expected Behavior: The script should run seamlessly in the Kaggle environment with TPU enabled.
Observed Behavior: The TPU initialization fails with the following error:
RuntimeError: Bad StatusOr access: UNKNOWN: TPU initialization failed: open(/dev/accel0): Operation not permitted: Couldn't open device: /dev/accel0; Unable to create Node RegisterInterface for node 0...
ebugging Efforts:
Verified Kaggle TPU configurations and ensured the TPU VM v3-8 is enabled.
Ensured all dependencies were installed using the requirements.txt file.
Debugged manually and with external resources (e.g., GPT-4) to check compatibility.
Confirmed the script works perfectly on GPU, but the TPU-specific initialization consistently fails.
from transformers import Trainer, TrainingArguments
import torch_xla.core.xla_model as xm
device = xm.xla_device()
training_args = TrainingArguments(
output_dir="./results",
per_device_train_batch_size=10,
num_train_epochs=6,
do_train=True,
evaluation_strategy="steps",
logging_dir="./logs",
)
trainer = Trainer(model=model, args=training_args, train_dataset=train_dataset)
trainer.train()
### Expected behavior
Expected Behavior
The script should execute seamlessly on Kaggle's TPU environment with the following outcomes:
TPU Initialization:
The TPU hardware should initialize successfully without errors.
Training Process:
The training process should begin and complete the specified number of epochs using TPU acceleration.
Performance:
The script should leverage the TPU's computational power, resulting in faster execution compared to GPU.
Output:
The model checkpoints, logs, and results should be saved to the specified directories as per the script's configuration. | bug | low | Critical |
2,797,706,674 | godot | [4.4beta1][Editor] GDScript documentation comments inconsistent behavior (## ) | ### Tested versions
v4.4.beta1.official
### System information
Godot v4.4.beta1 - Windows 11 (build 26100) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (NVIDIA; 32.0.15.6590) - AMD Ryzen 9 7950X 16-Core Processor (32 threads)
### Issue description
In-line gdscript documentation comments with a space following hash symbols are not prompting editor tooltips as suggested in the latest documentation/blog post. It's a little unclear if this was intended behavior, but based on wording I'm pretty sure it's not.
Presumably related to https://github.com/godotengine/godot/pull/91060
eg:
```
##This comment works as expected with a tooltip
new_func() -> void:
## This comment does not provide an in editor tooltip
another_func() -> void:
```
### Steps to reproduce
```
##This comment works as expected with a tooltip
new_func() -> void:
## This comment does not provide an in editor tooltip
another_func() -> void:
```
### Minimal reproduction project (MRP)
```
##This comment works as expected with a tooltip
new_func() -> void:
## This comment does not provide an in editor tooltip
another_func() -> void:
``` | bug,topic:editor,needs testing | low | Minor |
2,797,728,010 | ant-design | Rate 的 tooltips属性和用户体验优化 | ### What problem does this feature solve?
tooltips，应该支持全部的Tooltip props。
还有鼠标在Rate划过的时候：
1、不应该一个一个的出现，应该平滑过度过去，这样体验更好。
2、如果速度过快，不应该不应该不显示，估计是触发了“防抖”。如果上述实现了，那么这个问题可能不复存在。
3、半星最好也支持不同的提示。
### What does the proposed API look like?
和其他的组件中使用tooltip一样，prop全部支持。
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | help wanted | low | Minor |
2,797,737,914 | node | Allow Setting Extension Priority (and Then Not Requiring Extensions in Imports) | ### What is the problem this feature will solve?
In recent years Node has been trading developer convenience for functionality, as several recent changes (eg. https://satanacchio.hashnode.dev/everything-you-need-to-know-about-nodejs-type-stripping#heading-a-predictable-experience) strongly encourage:
```js
import foo from 'foo.js';
```
over:
```js
import foo from 'foo';
```
However, for most devs that's a false trade! We can have convenient (extension-less) imports _and_ have the benefits of the new features.
How?
### What is the feature you are proposing to solve the problem?
```sh
node --prioritizeExtensions=js,jsx,ts,tsx
```
Now, when Node sees:
```js
import foo from 'foo';
```
it will treat it as
```js
import foo from 'foo.js';
```
... unless that fails, in which case it will treat is as:
```js
import foo from 'foo.jsx';
```
... and so on.
### What alternatives have you considered?
Not requiring an argument ... but the dev needs some way to specify "if you see `foo.js` and `foo.ts`, but I said `from foo`, use the `.js` one".
Look, I know three or four extra characters of typing (`.jsx`) may not seem like a lot, but it adds up across dozens of imports in hundreds (or thousands) of files. Please, consider letting us have our extension-less imports back. | feature request | low | Minor |
2,797,748,822 | kubernetes | implement `PreEnqueue` not to start scheduling cycles for pods without necessary PVC created | ref: a question raised at https://github.com/kubernetes/kubernetes/issues/123227#issuecomment-2600929549
So, currently if PVCs for the pod are not-found, VolumeBinding `PreFilter` returns unschedulable.
But, it means that we have to consume 1 scheduling cycle to notice the lack of PVCs.
Technically, we can move this part to `PreEnqueue` so that the pods don't enter the scheduling cycles in the first place if PVCs aren't ready yet. DRA plugin does the similar stuff at `PreEnqueue` actually ([ref](https://github.com/kubernetes/kubernetes/blob/1c32094c03f721cd3dce49c9743f1e7f3e564b13/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources.go)).
(I'm wondering why we haven't done this until now though. Is it just that no one has noticed that we can do this, or is there any specific reasons blocking this improvement? (e.g., perf concern?) Anyways..)
/sig scheduling
/kind feature
/cc @kubernetes/sig-scheduling-misc @carlory | sig/scheduling,kind/feature,needs-triage | medium | Critical |
2,797,749,476 | vscode | macOS titlebar/windowTitle cuts large paths | <!-- ⚠️⚠️ 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. -->
macOS native titlebar missing a lot of available space and so paths are often cut
By default this titlebar only has like the 50% of the full available window space, and the path is usually trim in large paths or paths that also states we are inside a container like in this screenshot.
This should be a configurable option, allowing the user to set up a larger titleBar from 50% to 100% (all available space except the other controls at the very left/right of the window. | bug,titlebar,command-center | low | Minor |
2,797,755,322 | ollama | A new, much more relaxed way to use the Models offered by Ollama ( Sauraya ) |
# Sauraya AI (Ollama Mobile App )
## Introduction
Sauraya is a modern user interface designed to interact with open-source AI models such as Meta's LLama. This application is fully open-source and free, created to provide the benefits of Meta's AI products to a broader audience without the need for setting up resource-intensive local environments. With Sauraya, users simply download the app from [Sauraya.com](https://sauraya.com), install it, and start engaging with Meta's advanced AI models.
Sauraya is free and maintained by the **Opennode Team** ([opennode.tech](https://opennode.tech)).
## Privacy-Focused and Local Storage
Sauraya prioritizes user privacy by storing all conversations locally in an encrypted file accessible on Android at:
```
/android/com.sauraya/database/user-id.sauraya.crypt
```
The conversation file is a lightweight JSON, ensuring minimal storage usage. Upon app launch, file system access will be required.
Sauraya does not collect any user data, focusing solely on confidentiality. Users can perform various actions through the website, such as:
- Executing Python code
- Listening to AI-generated text via text-to-speech
- Renaming conversation titles
- And much more, with future updates to come.
The team works tirelessly to maintain and improve the application.
## Open Source Code
The source code, written in Dart with Flutter, is available on GitHub:
[https://github.com/Donadev56/sauraya-dart](https://github.com/Donadev56/sauraya-dart)
### License
**MIT License**
## Developer
**Devoue-Li-Tchibeni Dona Dieu Talliane**
GitHub: [https://github.com/Donadev56](https://github.com/Donadev56)
Skills: JavaScript, TypeScript, React Native, Next.js, Node.js, Dart, Flutter, Solidity, and more.
## Acknowledgments
We express our gratitude to:
- **Meta** for their LLama 3.2 and LLama 3.1 models, which made Sauraya possible.
- **Ollama.com** for providing well-documented APIs to interact with AI models.
- **The Flutter and Dart teams** for the language and framework enabling the creation of this application.
## Feedback
We welcome all suggestions for improving the project.
---
Best regards,
**The Opennode Team**
Website: [opennode.tech](https://opennode.tech)
| feature request | low | Minor |
2,797,762,894 | Python | AI bot | ### Feature description
u can at an AI bot in this to improve it.
| enhancement | medium | Minor |
2,797,772,243 | vscode | Integrated Terminal Tabs — Vertical vs Horizontal | <!-- ⚠️⚠️ 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. -->
Please allow for swapping the position of these two vertical/horizontal tab displays in the integrated terminal.
I don't like my primary terminal tabs to be vertical. These built-in sections could be listed vertically on the left, with the terminal tabs horizontally.
 | feature-request,terminal-tabs | low | Minor |
2,797,789,191 | neovim | 'background' detection occurs too late, causing colorscheme to load twice | ### Problem
Neovim automatically sets `'background'` based on whether the terminal is in light or dark mode, both on startup and (on nightly) when the terminal's appearance changes. In the latter case, at least on my machine, the automatic setting of the option occurs too late when the terminal is in light mode, meaning:
- Start up Nvim in a light mode terminal with a configured colorscheme
- The `'bg'` option is initially `"dark"` even though the terminal and OS are in light mode
- The configured colorscheme is applied while `'bg'` is still set to `"dark"`. Depending on the implementation of the colorscheme this could mean that it applies designated colors for its dark version.
- The automatic `'bg'` detection kicks in and sets the option to `"light"`.
- Because of the change the colorscheme is reloaded, this time with a `'bg'` value of `"light"` (which again may cause it to apply specific – in this case the correct – colors).
This is obviously bad because it's expensive and unnecessary, but particularly annoying with themes that adapt to the background because it means that there is a flash of dark before the correct colors are loaded.
### Steps to reproduce
1. Create a minimal configuration using `NVIM_APPNAME` (couldn't figure out how to do what needs to be done with just the issue template), with this structure:
```
.
├── colors
│ └── mycolors.lua
└── init.lua
```
Contents of `mycolors.lua`:
```lua
-- a very simple mock colorscheme that follows the background
local bg = vim.o.background
if bg == "dark" then
print("the value of 'bg' is: 'dark', thus applying the dark colors")
vim.api.nvim_set_hl(0, "Normal", {bg = "#000000", fg = "#ffffff"})
elseif bg == "light" then
print("the value of 'bg' is: 'light', thus applying the light colors")
vim.api.nvim_set_hl(0, "Normal", {bg = "#ffffff", fg = "#000000"})
end
vim.g.colors_name = "mycolors"
```
Contents of `init.lua`:
```lua
-- this part is optional:
--vim.api.nvim_create_autocmd("ColorScheme", { callback = function(data)
-- print(vim.inspect(data))
--end})
--vim.api.nvim_create_autocmd("OptionSet", { pattern = "background", callback = function(data)
-- print(vim.inspect(data))
--end})
vim.cmd.colorscheme("mycolors")
```
2. Run `NVIM_APPNAME=<your name> nvim` in a light mode terminal (can reproduce in Kitty and Ghostty). A black flicker will be visible before the background becomes bright white as expected (Because nvim is so fast, this is barely noticable, but with a heavy config full of plugins, it is very noticable).
3. Check `:messages`. The order of the messages will be:
- `the value of 'bg' is: 'dark', thus applying the dark colors`
- `the value of 'bg' is: 'light', thus applying the light colors`
### Expected behavior
The value of `'background'` is determined and set as early as possible so that it does not trigger reloading of the colorscheme.
### Nvim version (nvim -v)
NVIM v0.11.0-dev-6696ea7
### Vim (not Nvim) behaves the same?
no
### Operating system/version
macOS 15.2
### Terminal name/version
Ghostty 1.0.1, kitty 0.39.0
### $TERM environment variable
xterm-ghostty
### Installation
build from repo | documentation,defaults,startup | low | Major |
2,797,793,396 | ui | [bug]: Combobox popover within a Dialog does not have correct styling or animation | ### Describe the bug
Hello,
When I open a Combobox, which is a child of a Dialog, the Command menu opens, however the animation nor the border nor hover styling appears on it. It's just a more basic version of it (see screenshot).
<img width="551" alt="Image" src="https://github.com/user-attachments/assets/0b677a17-2ccc-46b0-b4e7-8f3516f42094" />
Things I've tried:
- Setting `modal=true` prop in the Dialog and Popover.
- Updating Radix libraries.
My relevant dependencies:
```
"dependencies": {
...
"@radix-ui/react-alert-dialog": "^1.1.4",
"@radix-ui/react-avatar": "^1.1.1",
"@radix-ui/react-dialog": "^1.1.4",
"@radix-ui/react-dropdown-menu": "^2.1.2",
"@radix-ui/react-label": "^2.1.0",
"@radix-ui/react-popover": "^1.1.4",
"@radix-ui/react-radio-group": "^1.2.2",
"@radix-ui/react-select": "^2.1.4",
"@radix-ui/react-separator": "^1.1.0",
"@radix-ui/react-slot": "^1.1.1",
"@radix-ui/react-tabs": "^1.1.1",
"@radix-ui/react-toast": "^1.2.4",
"cmdk": "^1.0.0",
....
},
```
Any help would be appreciated.
### Affected component/components
Combobox, popover, command
### How to reproduce
Render a Dialog component with a Combobox within it.
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
```
### System Info
```bash
Mac OS 15.2 Sequoia
Chrome Version 131.0.6778.205 (Official Build) (arm64)
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,797,809,263 | tensorflow | LD_LIBRARY_PATH to set when installing tensorflow[and-cuda] with pip or poetry | ### Issue type
Documentation Feature Request
### Have you reproduced the bug with TensorFlow Nightly?
No
### Source
binary
### TensorFlow version
2.18.0
### Custom code
No
### OS platform and distribution
Linux Fedora 41
### Mobile device
_No response_
### Python version
3.12
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
_No response_
### GPU model and memory
Nvidia RTX 3060
### Current behavior?
Installing `tensorflow[and-cuda]` is very easy and avoid installing cuda packages on our computers. It's then very confortable to be able to drop virtual envs.
But there is a bad behavior.
From scratch:
```bash
rm -rf .venv
mkdir .venv
poetry add "tensorflow[and-cuda]"
# check
poetry run python mytest.py
W0000 00:00:1737317404.258825 10111 gpu_device.cc:2344] Cannot dlopen some GPU libraries. Please make sure the missing libraries mentioned above are installed properly if you would like to use GPU. Follow the guide at https://www.tensorflow.org/install/gpu for how to download and setup the required libraries for your platform.
```
As you can see, no CUDA shared library is loaded.
The solution is to generate the `LD_LIBRARY_PATH` finding directories name of any ".so" files related to "nvidia":
```bash
export LD_LIBRARY_PATH=$(find .venv -name "*.so*" | grep -P "nvidia" | xargs dirname | sort -u | paste -d: -s -)
echo $LD_LIBRARY_PATH
.venv/lib/python3.12/site-packages/nvidia/cublas/lib:.venv/lib/python3.12/site-packages/nvidia/cuda_cupti/lib:.venv/lib/python3.12/site-packages/nvidia/cuda_nvcc/nvvm/lib64:.venv/lib/python3.12/site-packages/nvidia/cuda_nvrtc/lib:.venv/lib/python3.12/site-packages/nvidia/cuda_runtime/lib:.venv/lib/python3.12/site-packages/nvidia/cudnn/lib:.venv/lib/python3.12/site-packages/nvidia/cufft/lib:.venv/lib/python3.12/site-packages/nvidia/curand/lib:.venv/lib/python3.12/site-packages/nvidia/cusolver/lib:.venv/lib/python3.12/site-packages/nvidia/cusparse/lib:.venv/lib/python3.12/site-packages/nvidia/nccl/lib:.venv/lib/python3.12/site-packages/nvidia/nvjitlink/lib
# and now:
poetry run python mytest.py
I0000 00:00:1737317342.317060 9825 gpu_device.cc:2022] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 4169 MB memory: -> device: 0, name: NVIDIA GeForce RTX 3060 Laptop GPU, pci bus id: 0000:01:00.0, compute capability: 8.6
```
I'm not sur if I have to create the issue here or to Nvidia (where?), but it could be interesting to propose this solution for who has the same problem.
### Standalone code to reproduce the issue
```shell
poetry run python -c "import tensorflow;tensorflow.keras.Sequential().compile()"
```
### Relevant log output
```shell
``` | stat:awaiting response,type:feature,type:build/install,type:docs-feature | medium | Critical |
2,797,815,494 | flutter | Video Player is crashing in android emulator. Working fine in android device and iOS emulator. | ### What package does this bug report belong to?
video_player
### What target platforms are you seeing this bug on?
Android
### Have you already upgraded your packages?
Yes
### Dependency versions
<details><summary>pubspec.lock</summary>
```lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
async:
dependency: transitive
description:
name: async
sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
url: "https://pub.dev"
source: hosted
version: "2.11.0"
boolean_selector:
dependency: transitive
description:
name: boolean_selector
sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
url: "https://pub.dev"
source: hosted
version: "2.1.1"
characters:
dependency: transitive
description:
name: characters
sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
url: "https://pub.dev"
source: hosted
version: "1.3.0"
clock:
dependency: transitive
description:
name: clock
sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
url: "https://pub.dev"
source: hosted
version: "1.1.1"
collection:
dependency: transitive
description:
name: collection
sha256: a1ace0a119f20aabc852d165077c036cd864315bd99b7eaa10a60100341941bf
url: "https://pub.dev"
source: hosted
version: "1.19.0"
csslib:
dependency: transitive
description:
name: csslib
sha256: "09bad715f418841f976c77db72d5398dc1253c21fb9c0c7f0b0b985860b2d58e"
url: "https://pub.dev"
source: hosted
version: "1.0.2"
fake_async:
dependency: transitive
description:
name: fake_async
sha256: "511392330127add0b769b75a987850d136345d9227c6b94c96a04cf4a391bf78"
url: "https://pub.dev"
source: hosted
version: "1.3.1"
flutter:
dependency: "direct main"
description: flutter
source: sdk
version: "0.0.0"
flutter_lints:
dependency: "direct dev"
description:
name: flutter_lints
sha256: "5398f14efa795ffb7a33e9b6a08798b26a180edac4ad7db3f231e40f82ce11e1"
url: "https://pub.dev"
source: hosted
version: "5.0.0"
flutter_test:
dependency: "direct dev"
description: flutter
source: sdk
version: "0.0.0"
flutter_web_plugins:
dependency: transitive
description: flutter
source: sdk
version: "0.0.0"
html:
dependency: transitive
description:
name: html
sha256: "1fc58edeaec4307368c60d59b7e15b9d658b57d7f3125098b6294153c75337ec"
url: "https://pub.dev"
source: hosted
version: "0.15.5"
leak_tracker:
dependency: transitive
description:
name: leak_tracker
sha256: "7bb2830ebd849694d1ec25bf1f44582d6ac531a57a365a803a6034ff751d2d06"
url: "https://pub.dev"
source: hosted
version: "10.0.7"
leak_tracker_flutter_testing:
dependency: transitive
description:
name: leak_tracker_flutter_testing
sha256: "9491a714cca3667b60b5c420da8217e6de0d1ba7a5ec322fab01758f6998f379"
url: "https://pub.dev"
source: hosted
version: "3.0.8"
leak_tracker_testing:
dependency: transitive
description:
name: leak_tracker_testing
sha256: "6ba465d5d76e67ddf503e1161d1f4a6bc42306f9d66ca1e8f079a47290fb06d3"
url: "https://pub.dev"
source: hosted
version: "3.0.1"
lints:
dependency: transitive
description:
name: lints
sha256: c35bb79562d980e9a453fc715854e1ed39e24e7d0297a880ef54e17f9874a9d7
url: "https://pub.dev"
source: hosted
version: "5.1.1"
matcher:
dependency: transitive
description:
name: matcher
sha256: d2323aa2060500f906aa31a895b4030b6da3ebdcc5619d14ce1aada65cd161cb
url: "https://pub.dev"
source: hosted
version: "0.12.16+1"
material_color_utilities:
dependency: transitive
description:
name: material_color_utilities
sha256: f7142bb1154231d7ea5f96bc7bde4bda2a0945d2806bb11670e30b850d56bdec
url: "https://pub.dev"
source: hosted
version: "0.11.1"
meta:
dependency: transitive
description:
name: meta
sha256: bdb68674043280c3428e9ec998512fb681678676b3c54e773629ffe74419f8c7
url: "https://pub.dev"
source: hosted
version: "1.15.0"
path:
dependency: transitive
description:
name: path
sha256: "087ce49c3f0dc39180befefc60fdb4acd8f8620e5682fe2476afd0b3688bb4af"
url: "https://pub.dev"
source: hosted
version: "1.9.0"
plugin_platform_interface:
dependency: transitive
description:
name: plugin_platform_interface
sha256: "4820fbfdb9478b1ebae27888254d445073732dae3d6ea81f0b7e06d5dedc3f02"
url: "https://pub.dev"
source: hosted
version: "2.1.8"
sky_engine:
dependency: transitive
description: flutter
source: sdk
version: "0.0.0"
source_span:
dependency: transitive
description:
name: source_span
sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
url: "https://pub.dev"
source: hosted
version: "1.10.0"
stack_trace:
dependency: transitive
description:
name: stack_trace
sha256: "9f47fd3630d76be3ab26f0ee06d213679aa425996925ff3feffdec504931c377"
url: "https://pub.dev"
source: hosted
version: "1.12.0"
stream_channel:
dependency: transitive
description:
name: stream_channel
sha256: ba2aa5d8cc609d96bbb2899c28934f9e1af5cddbd60a827822ea467161eb54e7
url: "https://pub.dev"
source: hosted
version: "2.1.2"
string_scanner:
dependency: transitive
description:
name: string_scanner
sha256: "688af5ed3402a4bde5b3a6c15fd768dbf2621a614950b17f04626c431ab3c4c3"
url: "https://pub.dev"
source: hosted
version: "1.3.0"
term_glyph:
dependency: transitive
description:
name: term_glyph
sha256: a29248a84fbb7c79282b40b8c72a1209db169a2e0542bce341da992fe1bc7e84
url: "https://pub.dev"
source: hosted
version: "1.2.1"
test_api:
dependency: transitive
description:
name: test_api
sha256: "664d3a9a64782fcdeb83ce9c6b39e78fd2971d4e37827b9b06c3aa1edc5e760c"
url: "https://pub.dev"
source: hosted
version: "0.7.3"
vector_math:
dependency: transitive
description:
name: vector_math
sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
url: "https://pub.dev"
source: hosted
version: "2.1.4"
video_player:
dependency: "direct main"
description:
name: video_player
sha256: "4a8c3492d734f7c39c2588a3206707a05ee80cef52e8c7f3b2078d430c84bc17"
url: "https://pub.dev"
source: hosted
version: "2.9.2"
video_player_android:
dependency: transitive
description:
name: video_player_android
sha256: "7018dbcb395e2bca0b9a898e73989e67c0c4a5db269528e1b036ca38bcca0d0b"
url: "https://pub.dev"
source: hosted
version: "2.7.17"
video_player_avfoundation:
dependency: transitive
description:
name: video_player_avfoundation
sha256: "8a4e73a3faf2b13512978a43cf1cdda66feeeb900a0527f1fbfd7b19cf3458d3"
url: "https://pub.dev"
source: hosted
version: "2.6.7"
video_player_platform_interface:
dependency: transitive
description:
name: video_player_platform_interface
sha256: "229d7642ccd9f3dc4aba169609dd6b5f3f443bb4cc15b82f7785fcada5af9bbb"
url: "https://pub.dev"
source: hosted
version: "6.2.3"
video_player_web:
dependency: transitive
description:
name: video_player_web
sha256: "881b375a934d8ebf868c7fb1423b2bfaa393a0a265fa3f733079a86536064a10"
url: "https://pub.dev"
source: hosted
version: "2.3.3"
vm_service:
dependency: transitive
description:
name: vm_service
sha256: f6be3ed8bd01289b34d679c2b62226f63c0e69f9fd2e50a6b3c1c729a961041b
url: "https://pub.dev"
source: hosted
version: "14.3.0"
web:
dependency: transitive
description:
name: web
sha256: cd3543bd5798f6ad290ea73d210f423502e71900302dde696f8bff84bf89a1cb
url: "https://pub.dev"
source: hosted
version: "1.1.0"
sdks:
dart: ">=3.6.0 <4.0.0"
flutter: ">=3.27.0"
```
</details>
### Steps to reproduce
1. Open the application.
2. The app crashes even before the video is loaded.
### Expected results
The video player should not crash in android emulator.
### Actual results
Android emulator crashes as soon as the video player is loaded even before interacting with video_player.
### Code sample
<details open><summary>Code sample</summary>
```dart
(https://github.com/Parixit2411/video_player_test/blob/main/lib/main.dart)
```
##
</details>
### Screenshots or Videos
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[ERR] Error 1 retrieving device properties for sdk gphone16k x86 64:
[ERR] adb.exe: device offline
[ERR] The Android emulator exited with code 1073741845 after startup
[ERR] Android emulator stderr:
[ERR] [22704:22664:20250120,012200.321:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\user\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.2.10.db\attachments\9d09e4c6-dcc9-4048-8b62-0adf9e9ccd7e: The system cannot find the file specified. (2)
[ERR] [4948:10956:20250120,012200.420:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\user\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.2.10.db\attachments\9d09e4c6-dcc9-4048-8b62-0adf9e9ccd7e: The system cannot find the file specified. (2)
[ERR] initialize: Supports id properties, got a vulkan device UUID
[ERR] netsimd I 01-19 19:52:04.639 daemon\src\rust_main.rs:98 - netsim artifacts path: "C:\\Users\\user\\AppData\\Local\\Temp\\netsimd"
[ERR] netsimd I 01-19 19:52:04.639 daemon\src\rust_main.rs:101 - NetsimdArgs {
[ERR] fd_startup_str: None,
[ERR] no_cli_ui: true,
[ERR] no_web_ui: true,
[ERR] pcap: false,
[ERR] disable_address_reuse: false,
[ERR] hci_port: None,
[ERR] connector_instance: None,
[ERR] instance: None,
[ERR] logtostderr: false,
[ERR] dev: false,
[ERR] rust_grpc: false,
[ERR] rust_hostapd: false,
[ERR] rust_slirp: false,
[ERR] vsock: None,
[ERR] config: None,
[ERR] host_dns: Some(
[ERR] "8.8.8.8",
[ERR] ),
[ERR] http_proxy: None,
[ERR] wifi_tap: None,
[ERR] test_beacons: false,
[ERR] no_test_beacons: false,
[ERR] no_shutdown: false,
[ERR] verbose: false,
[ERR] version: false,
[ERR] }
[ERR] pc_memory_init: above 4g size: 40000000
[ERR] NVVM compilation failed: 1
[ERR] [4948:10956:20250120,014234.931:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\user\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.2.10.db\attachments\3deb650c-f2a8-4eaf-8276-f9d3ee21ffc2: The system cannot find the file specified. (2)
[ERR] [4948:10956:20250120,014234.931:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\user\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.2.10.db\attachments\3deb650c-f2a8-4eaf-8276-f9d3ee21ffc2: The system cannot find the file specified. (2)
[ERR] [4948:10956:20250120,014234.940:ERROR filesystem_win.cc:130] GetFileAttributes C:\Users\user\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.2.10.db\attachments\3deb650c-f2a8-4eaf-8276-f9d3ee21ffc2: The system cannot find the file specified. (2)
[ERR] Address these issues and try again.
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[√] Flutter (Channel stable, 3.27.1, on Microsoft Windows [Version 10.0.22631.4751], locale en-IN)
• Flutter version 3.27.1 on channel stable at C:\Flutter\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 17025dd882 (5 weeks ago), 2024-12-17 03:23:09 +0900
• Engine revision cb4b5fff73
• Dart version 3.6.0
• DevTools version 2.40.2
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
• Android SDK at C:\Users\user\AppData\Local\Android\Sdk
• Platform android-35, build-tools 35.0.0
• ANDROID_HOME = C:\Users\user\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio1\jbr\bin\java
• Java version OpenJDK Runtime Environment (build 17.0.10+0--11609105)
• 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.11.4)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.11.35312.102
• Windows 10 SDK version 10.0.22621.0
[!] Android Studio (version 2021.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
X Unable to determine bundled Java version.
• Try updating or re-installing Android Studio.
[√] Android Studio (version 2024.1)
• Android Studio at C:\Program Files\Android\Android Studio1
• 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.10+0--11609105)
[√] VS Code (version 1.96.4)
• VS Code at C:\Users\user\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.102.0
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64 • Microsoft Windows [Version 10.0.22631.4751]
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.265
• Edge (web) • edge • web-javascript • Microsoft Edge 132.0.2957.115
[√] Network resources
• All expected network resources are available.
```
</details>
| in triage | low | Critical |
2,797,827,383 | next.js | `unstable_cache` doesn't serialize non-primitive data types | ### Link to the code that reproduces this issue
https://github.com/devjmetivier/next-unstable-cache-args-serialization
### To Reproduce
1. Open homepage
2. Change sort order with input
3. See request cache behavior
### Current vs. Expected behavior
Cache doesn't work (as expected) because passing arguments to `unstable_cache` of any non-JSON serializable data type (Map, in this example) results in the same deterministic output.
<img width="363" alt="Image" src="https://github.com/user-attachments/assets/2403c912-de84-4cd3-8f1b-7bfa22f535b7" />
### Provide environment information
```bash
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.1.0: Thu Nov 14 18:19:02 PST 2024; root:xnu-11215.41.3~13/RELEASE_ARM64_T8132
Available memory (MB): 32768
Available CPU cores: 10
Binaries:
Node: 22.12.0
npm: 10.9.0
Yarn: 1.22.22
pnpm: 9.15.3
Relevant Packages:
next: 15.2.0-canary.16 // Latest available version is detected (15.2.0-canary.16).
eslint-config-next: N/A
react: 19.0.0
react-dom: 19.0.0
typescript: 5.7.3
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
Runtime, Not sure
### Which stage(s) are affected? (Select all that apply)
next dev (local), next build (local), next start (local), Vercel (Deployed)
### Additional context
I understand that `unstable_cache` is intended to handle any work inside the function, but I'm encountering an issue when passing iterables like Maps and Sets. These data structures aren't serializable, so their contents can't be cached, forcing me to either change the data type or manually serialize/deserialize the values. It would be helpful if unstable_cache could support these types (iterables) more seamlessly.
Here's where I can see these arguments being dealt with in Next.js:
https://github.com/vercel/next.js/blob/3f3f4bc78145e1bb271781aabd595758dd0686a9/packages/next/src/server/web/spec-extension/unstable-cache.ts#L138-L144 | Runtime | low | Minor |
2,797,846,693 | vscode | Allow to overwrite when pasting files instead of adding suffix " copy" | <!-- ⚠️⚠️ 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. -->
When pasting files in 'Folder' view, VS Code automatically renames every file if a file with the same name already exists.
It is very rare in any development situation for names like "ExampleFile copy.txt" to be usable.
It forces developers to always rename those files manually.
There are multiple situations where **overwriting files should be the default action**, such as updating old files with the newest versions.
Currently you need to manually select some files in the folder, delete them, and then paste files from other folder.
It's quite annoying and troublesome.
Obviously there is a risk ov overwriting by accident so VS Code should behave just like any OS do - ask user if he wants to:
1. Overwrite files with the same names
2. Rename pasted files (current default behaviour)
3. Paste only files that are not yet in the folder
4. Cancel pasting
Current VS Code pasting:
1. Copying file with the same name:
2. Pasting that file will rename it with suffix " copy":
Typical paste merging conflict on Windows 10 allows to "Replace files" (overwrite them)
 | info-needed | low | Minor |
2,797,849,199 | godot | Websocket client cuts message after 2^15 bytes | ### Tested versions
- v4.3.stable.official [77dcf97d8]: **ok**
- v4.4.dev1.official [28a72fa43]: **ok**
- v4.4.dev2.official [97ef3c837]: **ok**
- v4.4.dev3.official [f4af8201b]: **ok**
- v4.4.dev4.official [36e6207bb]: **ok**
- v4.4.dev5.official [9e6098432]: **fails**
- v4.4.dev6.official [1f47e4c4e]: **fails**
- v4.4.dev7.official [46c8f8c5c]: **fails**
- v4.4.beta1.official [d33da79d3]: **fails**
### System information
Godot v4.4.beta1 - Windows 11 (build 26100) - Multi-window, 2 monitors - OpenGL 3 (Compatibility) - NVIDIA GeForce GTX 1080 Ti (NVIDIA; 32.0.15.6614) - AMD Ryzen 9 7900X 12-Core Processor (24 threads)
### Issue description
The Godot Websocket client cuts received messages after 2^15 bytes.
This is a regression since `v4.4.dev5`.
### Steps to reproduce
I could **NOT** reproduce the issue with Godot's builtin websocket server (also included in MRP). I provide another websocket server based on Go.
You can either use the devcontainer and run `Launch server` or run `cd server && go run main.go` in the terminal. If not using a devcontainer do `cd server && go mod download && go run main.go` (i can also provide binaries if wished)
The server listens on port `9080` and answers `ping` with `pong` and any other message should be a number, which will then send a message with that many `G`s back.
In Godot just hit run, what messages are sent or received are logged to the output.
### Minimal reproduction project (MRP)
[godot-ws.zip](https://github.com/user-attachments/files/18470551/godot-ws.zip) | bug,topic:network,regression | low | Minor |
2,797,850,335 | ui | [bug]: tabindex of form inputs leaks out to Sheet | ### Describe the bug
When i put a Form inside a Sheet, the Form inputs tabindex leaks out to the Sheet component.
When i put the same form outside the Sheet, tabindex works as intended.
### Affected component/components
Sheet
### How to reproduce
When i put a Form inside a Sheet, the Form inputs tabindex leaks out to the Sheet component.
When i put the same form outside the Sheet, tabindex works as intended.
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
```
### System Info
```bash
Chrome OSX
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,797,852,999 | tensorflow | Cannot use GpuDelegate - java.lang.IllegalArgumentException: Internal error: Cannot create interpreter | Hi, I get "Cannot use GpuDelegate - java.lang.IllegalArgumentException: Internal error: Cannot create interpreter" when attempting to use GpuDelegate
I have seen a couple of issue related to this but all seems to be abandoned. I have created a repo replicating the issue. You can see the config at [https://github.com/NLLAPPS/WhisperOffline/blob/d075a84aa42adc4a05a02ce64b0fcda9416f0e8c/app/src/main/java/com/whispertflite/engine/WhisperEngineJava.java#L114](https://github.com/NLLAPPS/WhisperOffline/blob/d075a84aa42adc4a05a02ce64b0fcda9416f0e8c/app/src/main/java/com/whispertflite/engine/WhisperEngineJava.java#L114)
**System information**
- Android Device information: Samsung S23
- TensorFlow Lite in Play Services SDK version : 16.4.0
- Google Play Services version: 24.50.34
**Standalone code to reproduce the issue**
Clone and run project from [https://github.com/NLLAPPS/WhisperOffline/](https://github.com/NLLAPPS/WhisperOffline/)
**Any other info / logs**
`Created TensorFlow Lite delegate for GPU.
Created interpreter.
Created interpreter.
java.lang.IllegalArgumentException: Internal error: Cannot create interpreter:
at com.google.android.gms.tflite.NativeInterpreterWrapper.createInterpreter(Native Method)
at com.google.android.gms.tflite.NativeInterpreterWrapper.zzs(com.google.android.gms:play-services-tflite-java@@16.4.0:34)
at com.google.android.gms.tflite.NativeInterpreterWrapper.<init>(com.google.android.gms:play-services-tflite-java@@16.4.0:14)
at com.google.android.gms.tflite.zzd.<init>(com.google.android.gms:play-services-tflite-java@@16.4.0:3)
at com.google.android.gms.tflite.InterpreterFactoryImpl.create(com.google.android.gms:play-services-tflite-java@@16.4.0:4)
at org.tensorflow.lite.InterpreterApi.create(InterpreterApi.java:373)
at com.whispertflite.engine.WhisperEngineJava.loadModel(WhisperEngineJava.java:131)
at com.whispertflite.engine.WhisperEngineJava.initialize(WhisperEngineJava.java:44)
at com.whispertflite.asr.WhisperJava.loadModel(WhisperJava.java:72)
at com.whispertflite.asr.WhisperJava.loadModel(WhisperJava.java:67)
at com.whispertflite.MainActivity.initModel(MainActivity.java:247)
at com.whispertflite.MainActivity.lambda$onCreate$3$com-whispertflite-MainActivity(MainActivity.java:155)
at com.whispertflite.MainActivity$$ExternalSyntheticLambda0.run(D8$$SyntheticClass:0)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)`
| comp:lite,TFLiteGpuDelegate | low | Critical |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.