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,811,838,719 | ollama | Error Running Mistral Nemo Imported from .safetensors | ### What is the issue?
I encountered an error when attempting to run the Mistral Nemo model imported from `.safetensors`. I intend to run the model on CPU only, even though I have a GPU (see the Modelfile below).
- I am able to run the model converted to `.gguf`.
- However, I would like to import and run directly from `.safetensors` if possible.
### Steps to Reproduce
1. Download model files from [mistralai/Mistral-Nemo-Instruct-2407](https://huggingface.co/mistralai/Mistral-Nemo-Instruct-2407/tree/main).
2. Create a `Modelfile` with the following content:
```
FROM <PATH TO .SAFETENSOR FILES>
PARAMETER num_gpu 0
```
3. Start the ollama server: `ollama serve`
4. Create the model: `ollama create nemo -f Modelfile`
5. Run the model: `ollama run nemo`
- **Error message**: `Error: llama runner process has terminated: error loading model: error loading model hyperparameters: invalid n_rot: 160, expected 128 llama_load_model_from_file: failed to load model`
### OS, GPU, CPU
- OS: Linux fedora 6.12.6
- GPU: Radeon RX 7600 XT
- CPU: AMD Ryzen 7 7700X
- RAM: 64GB
Thank you in advance for the help!
### OS
Linux
### GPU
AMD
### CPU
AMD
### Ollama version
0.5.4 | bug | low | Critical |
2,811,840,282 | neovim | Assertion failed: (v <= 9007199254740991. && v >= -9007199254740991.), function mpack_pack_number, file conv.c, line 113 | `mpack_pack_number()` overflows, steps to reproduce:
```sh
echo "local n = require('test.functional.testnvim')()
it('rpcpack number overflow', function()
n.clear()
n.api.nvim_set_current_win(2^53)
end)" > /tmp/mpackassert_spec.lua
TEST_FILE=/tmp/mpackassert_spec.lua make functionaltest
```
Ref: https://github.com/neovim/neovim/pull/31710#issuecomment-2561275755, https://github.com/neovim/neovim/discussions/32213 | channels-rpc,bug-crash | low | Critical |
2,811,851,545 | vscode | folder does not open or show in explorer(open editors) tab |
Type: <b>Bug</b>
when right clicking a folder to open with vs code nothing happpens and the vs code code application does not respond and when creating a new file it does not allow me to save it and rename it directly when clicked on the new file icon in explorer tab it creates an untitled .txt file which take me extra time and if there is a feature that resolves this issue it is not easy to find. and when running the coomand "npm init " the jason ppackage file does not show in the explorer tab even though it is present in the folder. with multiple i have to open each file separately wasting time
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.22631
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)|
|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.79GB (0.45GB free)|
|Process Argv|--crash-reporter-id f71f8c42-1d6a-469d-bc72-2cb0870b4fef|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (10)</summary>
Extension|Author (truncated)|Version
---|---|---
composer-php-vscode|DEV|1.55.16740
intelli-php-vscode|DEV|0.12.15062
phptools-vscode|DEV|1.55.16740
profiler-php-vscode|DEV|1.55.16740
code-runner|for|0.12.2
cmake-tools|ms-|1.19.52
cpptools|ms-|1.22.11
cpptools-extension-pack|ms-|1.3.0
LiveServer|rit|5.7.9
cmake|twx|0.0.17
(1 theme extensions excluded)
</details><details>
<summary>A/B Experiments</summary>
```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
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
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730
```
</details>
<!-- generated by issue reporter --> | info-needed | low | Critical |
2,811,856,964 | pytorch | Doubt about the actual behavior of handle.wait() in torch.distributed | ### 📚 The doc issue
For `comm_handle.wait()` in the case of async comm, the doc (https://pytorch.org/docs/stable/distributed.html#synchronous-and-asynchronous-collective-operations) says
`In the case of CUDA collectives, will block until the operation has been successfully enqueued onto a CUDA stream and the output can be utilized on the default stream without further synchronization.`
However, I doubt this should be
`the output can be utilized on the stream in which wait() is called`.
### Suggest a potential alternative/fix
I used nsys to profile a snippet to verify that handle.wait() calls `cudaStreamWaitEvent()`. It occured to me that when called in a stream context, the comm output will be synchonrized to be used on that stream. Line 14 in python backtrace is exactly `handle.wait()` followed by elt-wise add, and I think this should ensure the correct output.
```
from torch.multiprocessing import spawn
import torch.distributed as dist
import torch
import os
def test(rank, world_size):
# Code runs on each rank.
dist.init_process_group("nccl", rank=rank, world_size=2)
output = torch.ones((1000, 1000)).cuda(rank)
s = torch.cuda.Stream()
handle = dist.all_reduce(output, async_op=True)
# Wait ensures the operation is enqueued, but not necessarily complete.
# Using result on non-default stream.
with torch.cuda.stream(s):
handle.wait()
# s.wait_stream(torch.cuda.default_stream())
output.add_(100)
if rank == 0:
print(output)
dist.destroy_process_group()
if __name__ == "__main__":
os.environ['MASTER_ADDR'] = 'localhost'
os.environ['MASTER_PORT'] = '29503'
spawn(test, args=(2,), nprocs=2, join=True)
```
## One remaining question:
In the C source code I see [Work::wait](https://github.com/pytorch/pytorch/blob/c6ad08357bf8e766b5220bfb5cbbfdb2a4ec0ca5/torch/csrc/distributed/c10d/Work.cpp#L81) has nothing to do with `cudaStreamWaitEvent`. I searched for `cudaStreamWaitEvent` in the whole codebase and couldn't find anything related to torch.distributed. Would love a explaination of the call stack.
Thanks for your attention.
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o | oncall: distributed | low | Major |
2,811,858,308 | storybook | [Bug]: Regression in test-storybook after upgrading to 8.5.x: Axe is already running error | ### Describe the bug
### Summary
After upgrading to Storybook 8.5.1, I encountered an issue when running `yarn test-storybook` in combination with axe-playwright. Specifically, the test runner throws the following error:
```
page.evaluate: Error: Axe is already running. Use `await axe.run()` to wait for the previous run to finish before starting a new run.
```
This issue occurs when running tests with `--maxWorkers=2` or higher. However, it works fine if I downgrade back to 8.4.7 or if I reduce the number of workers to `--maxWorkers=1` in 8.5.1.
### Environment Details:
- Storybook Version: 8.5.x
- `@storybook/test-runner` Version: Latest (installed alongside Storybook 8.5.1)
- Test Runner Command:
```
yarn test-storybook --url http://127.0.0.1:6006/ --config-dir ./apps/storybook/.storybook --maxWorkers=2
```
- Temporary Solution: Changing `--maxWorkers` to 1 avoids the issue:
```
yarn test-storybook --url http://127.0.0.1:6006/ --config-dir ./apps/storybook/.storybook --maxWorkers=1
```
### Questions:
- Was there a change in how `@storybook/test-runner` or Storybook 8.5.x handles parallel worker processes?
- Is there a way to ensure compatibility with `axe-playwright` when running `test-storybook` with multiple workers?
- Are there any known workarounds or fixes to address this regression?
### Reproduction link
no
### Reproduction steps
I can reproduce this with this code
```bash
yarn concurrently -k -s first -n "SB,TEST" -c "magenta,blue" "yarn http-server dist/storybook/storybook --port 6006 --silent" "yarn wait-on http://127.0.0.1:6006 && yarn test-storybook --config-dir ./apps/storybook/.storybook --maxWorkers=2
```
```tsx
//.storybook/test-runner.ts
import type { TestRunnerConfig } from '@storybook/test-runner';
import { getStoryContext } from '@storybook/test-runner';
import { injectAxe, checkA11y, configureAxe } from 'axe-playwright';
/*
* See https://storybook.js.org/docs/writing-tests/test-runner#test-hook-api
* to learn more about the test-runner hooks API.
*/
const config: TestRunnerConfig = {
async preVisit(page) {
await injectAxe(page);
},
async postVisit(page, context) {
// Get the entire context of a story, including parameters, args, argTypes, etc.
const storyContext = await getStoryContext(page, context);
// Apply story-level a11y rules
await configureAxe(page, {
rules: storyContext.parameters?.a11y?.config?.rules,
});
const element = storyContext.parameters?.a11y?.element ?? 'body';
await checkA11y(page, element, {
detailedReport: true,
detailedReportOptions: {
html: true,
},
});
},
};
export default config;
```
### System
```bash
Storybook Environment Info:
System:
OS: macOS 15.2
CPU: (8) arm64 Apple M1 Pro
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.15.1 - /private/var/folders/4v/rybl0kls7918cw1lzk1120gw0000gp/T/xfs-f358ab08/node
Yarn: 3.6.4 - /private/var/folders/4v/rybl0kls7918cw1lzk1120gw0000gp/T/xfs-f358ab08/yarn <----- active
npm: 10.7.0 - /usr/local/bin/npm
Browsers:
Chrome: 131.0.6778.265
Safari: 18.2
npmPackages:
@storybook/addon-a11y: ^8.5.1 => 8.5.1
@storybook/addon-designs: ^8.0.4 => 8.0.4
@storybook/addon-docs: ^8.5.1 => 8.5.1
@storybook/addon-essentials: ^8.5.1 => 8.5.1
@storybook/addon-interactions: ^8.5.1 => 8.5.1
@storybook/addon-links: ^8.5.1 => 8.5.1
@storybook/addon-themes: ^8.5.1 => 8.5.1
@storybook/blocks: ^8.5.1 => 8.5.1
@storybook/core-server: ^8.5.1 => 8.5.1
@storybook/react: ^8.5.1 => 8.5.1
@storybook/react-vite: ^8.5.1 => 8.5.1
@storybook/test: ^8.5.1 => 8.5.1
@storybook/test-runner: ^0.21.0 => 0.21.0
chromatic: ^11.24.0 => 11.24.0
eslint-plugin-storybook: ^0.11.2 => 0.11.2
storybook: ^8.5.1 => 8.5.1
storybook-addon-pseudo-states: ^4.0.2 => 4.0.2
```
### Additional context
- This issue does not occur when using the Storybook dev server (`yarn storybook`) instead of `http-server`. The same test works fine when pointed to `http://localhost:4400` (the Storybook dev server) with `--maxWorkers=2`.
- I suspect this might be related to how lifecycle events are handled in `@storybook/test-runner` for static vs. dynamic Storybook builds in the 8.5.x release.
- Similar issue https://github.com/storybookjs/storybook/issues/29805#issuecomment-2594439211 | bug,needs reproduction,addon: a11y,test-runner,upgrade:8.5 | low | Critical |
2,811,861,614 | yt-dlp | googlevideo.com web request | ### 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 asking a question and **not** reporting a bug or requesting a feature
- [x] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [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 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 questions **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)
### Please make sure the question is worded well enough to be understood
When looking at the browser developer tool is it the top most googlevideo.com request the latest or is it at the bottom
### 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: ['--config-location', '/data/data/com.termux/files/home/.config/yt-dlp/video/config', 'https://www.youtube.com/watch?v=jdoLvM5iCdQ', '-s']
[debug] | Config "/data/data/com.termux/files/home/.config/yt-dlp/video/config": ['--paths', 'storage/shared/Youtube', '-N', '8', '--retries', '6', '--fragment-retries', '1', '-r', '75K', '--buffer-size', '40K', '--no-resize-buffer', '--socket-timeout', '30', '--sponsorblock-api', 'https://sponsor.ajay.app', '-4', '--cookies', 'storage/shared/Download/cookies1.txt', '--trim-filenames', '183', '--write-thumbnail', '--convert-thumbnails', 'jpg', '--no-mtime', '--sponsorblock-remove', 'sponsor', '--write-description', '--extractor-args', 'youtube:player_client=-ios,mweb,web_creator,-web,-tv,web_safari,-web_embedded,-mweb_music,-web_music;po_token=mweb+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,web+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,web_creator+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,tv+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,web_safari+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,web_embedded+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,mweb_music+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO,web_music+MlsHypOFoTEUBAfyOPOxe4gMsfJiYsLXMj1Z7C9TTJJ115xCndEDrI-lwue0FPQ1d8uenjdEvq_ffY_G6hQKmJjDG0SsknBVMq1RjjVSl0vE4nXMUYJ81PA1KYRO;formats=dashy;skip=translated_subs,hls;comment_sort=top;max_comments=7000,all,7000,500', '--sponsorblock-mark', 'all', '--embed-chapters', '--merge-output-format', 'mkv', '--video-multistreams', '--audio-multistreams', '-S', '+hasaud,vcodec:vp9,vext:mkv', '-f', 'bv*+bv*.2+ba+ba.2/bv*+bv*.2/bv*+ba', '--write-subs', '--write-auto-subs', '--sub-langs', 'en,en-US,en-us,en-gb,en-GB,vi,vi-VN,vi-vn,vi-en-GB,.*-orig', '-P', 'temp:storage/shared/Android/data/com.termux/files', '-o', '%(title).120B %(resolution)s %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s.%(ext)s', '--parse-metadata', '%(title)s:%(meta_title)s', '--parse-metadata', '%(uploader)s:%(artist)s', '--no-embed-info-json', '--replace-in-metadata', 'video:title', ' #.+? ', ' ', '--replace-in-metadata', 'video:title', '^#.+? ', '', '--replace-in-metadata', 'video:title', ' #.+?$', '', '--write-annotations', '--mark-watched', '--no-windows-filenames', '--http-chunk-size', '524288', '--print-to-file', '%(thumbnails_table)+#l', '%(title).120B %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s 0.txt', '--print-to-file', '%(playlist:thumbnails_table)+#l', '%(title).120B %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s 1.txt', '--retry-sleep', 'exp=1:8', '--retry-sleep', 'extractor:exp=1:5', '--retry-sleep', 'fragment:exp=1:20', '--print-to-file', '%(filename)s', '%(title).120B %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s 2.txt', '--print-to-file', '%(formats_table)+#l', '%(title).120B %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s 3.txt', '--print-to-file', '%(comments)+#j', '%(title).120B %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s 4.json', '--print-to-file', '%(duration>%H:%M:%S)+j', '%(title).120B %(id).30B %(uploader).29B %(availability)s %(upload_date>%d/%m/%Y)s 5.json', '--abort-on-unavailable-fragments', '--sleep-subtitles', '3', '--sleep-requests', '1', '--sleep-interval', '5', '--max-sleep-interval', '70', '--verbose', '--write-comments', '--fixup', 'warn', '--embed-metadata', '--remux-video', 'mkv', '--no-check-certificate', '--add-headers', 'Accept:*/*', '--add-headers', 'Accept-Encoding:gzip, deflate', '--add-headers', 'User-Agent:Mozilla/5.0 (X11; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0', '--replace-in-metadata', 'video:title', ' ?[\\U00010000-\\U0010ffff]+', '', '--no-quiet', '--parse-metadata', '%(uploader,channel,creator,artist|null)s:^(?P<uploader>.*?)(?:(?= - Topic)|$)']
[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-nightly-builds [dade5e35c] (zip)
[debug] Python 3.12.8 (CPython aarch64 64bit) - Linux-4.4.248-hadesKernel-v2.0-greatlte-aarch64-with-libc (OpenSSL 3.3.2 3 Sep 2024, libc)
[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.47.2, urllib3-2.3.0, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1837 extractors
[debug] [youtube] Found YouTube account cookies
[youtube] Extracting URL: https://www.youtube.com/watch?v=jdoLvM5iCdQ
[youtube] jdoLvM5iCdQ: Downloading webpage
[youtube] Sleeping 1.0 seconds ...
[youtube] jdoLvM5iCdQ: Downloading mweb player API JSON
[youtube] Sleeping 1.0 seconds ...
[youtube] jdoLvM5iCdQ: Downloading web creator player API JSON
[youtube] Sleeping 1.0 seconds ...
[youtube] jdoLvM5iCdQ: Downloading web safari player API JSON
[debug] [youtube] Extracting signature function js_0b866fa6_110
[debug] Loading youtube-sigfuncs.js_0b866fa6_110 from cache
[debug] Loading youtube-nsig.0b866fa6 from cache
[debug] [youtube] Decrypted nsig VOFSRQfXPZN3PNwG => I43AcU376753yg
[debug] Loading youtube-nsig.0b866fa6 from cache
[debug] [youtube] Decrypted nsig HyXUr5e7fqhZe2jT => Lamn9u14k_6m0w
[debug] [youtube] Extracting signature function js_0b866fa6_106
[debug] Loading youtube-sigfuncs.js_0b866fa6_106 from cache
[youtube] Sleeping 1.0 seconds ...
[youtube] jdoLvM5iCdQ: Marking watched
[youtube] Sleeping 1.0 seconds ...
[youtube] jdoLvM5iCdQ: Marking fully watched
[debug] Sort order given by user: +hasaud, vcodec:vp9, vext:mkv
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, +hasaud, vcodec:vp9(9), vext:mkv(2), quality, res, fps, hdr:12(7), source, channels, acodec, lang, proto, size, br, asr, aext, id
[debug] Searching for '(?P<meta_title>.+)' in '%(title)s'
[MetadataParser] Parsed meta_title from '%(title)s': 'a spiritual breakcore 2025 mix'
[debug] Searching for '(?P<artist>.+)' in '%(uploader)s'
[MetadataParser] Parsed artist from '%(uploader)s': 'machine slvts'
[debug] Searching for '^(?P<uploader>.*?)(?:(?= - Topic)|$)' in '%(uploader,channel,creator,artist|null)s'
[MetadataParser] Parsed uploader from '%(uploader,channel,creator,artist|null)s': 'machine slvts'
[youtube] Sleeping 1.0 seconds ...
[youtube] Downloading comment section API JSON
[youtube] Downloading ~1 comments
[youtube] Sorting comments by top comments
[youtube] Sleeping 1.0 seconds ...
[youtube] Downloading comment API JSON page 1 (0/~1)
[youtube] Extracted 1 comments
[SponsorBlock] Fetching SponsorBlock segments
[debug] SponsorBlock query: https://sponsor.ajay.app/api/skipSegments/096f?service=YouTube&categories=%5B%22intro%22%2C+%22poi_highlight%22%2C+%22sponsor%22%2C+%22music_offtopic%22%2C+%22outro%22%2C+%22chapter%22%2C+%22preview%22%2C+%22filler%22%2C+%22selfpromo%22%2C+%22interaction%22%5D&actionTypes=%5B%22skip%22%2C+%22poi%22%2C+%22chapter%22%5D
[SponsorBlock] No matching segments were found in the SponsorBlock database
[info] jdoLvM5iCdQ: Downloading 1 format(s): 313+271+251+140
[debug] Replacing all ' #.+? ' in title with ' '
[MetadataParser] Did not find ' #.+? ' in title
[debug] Replacing all '^#.+? ' in title with ''
[MetadataParser] Did not find '^#.+? ' in title
[debug] Replacing all ' #.+?$' in title with ''
[MetadataParser] Did not find ' #.+?$' in title
[debug] Replacing all ' ?[\\U00010000-\\U0010ffff]+' in title with ''
[MetadataParser] Did not find ' ?[\\U00010000-\\U0010ffff]+' in title
[info] Writing '%(thumbnails_table)+#l' to: storage/shared/Youtube/a spiritual breakcore 2025 mix jdoLvM5iCdQ machine slvts public 14⧸01⧸2025 0.txt
[info] Writing '%(playlist:thumbnails_table)+#l' to: storage/shared/Youtube/a spiritual breakcore 2025 mix jdoLvM5iCdQ machine slvts public 14⧸01⧸2025 1.txt
[info] Writing '%(filename)s' to: storage/shared/Youtube/a spiritual breakcore 2025 mix jdoLvM5iCdQ machine slvts public 14⧸01⧸2025 2.txt
[info] Writing '%(formats_table)+#l' to: storage/shared/Youtube/a spiritual breakcore 2025 mix jdoLvM5iCdQ machine slvts public 14⧸01⧸2025 3.txt
[info] Writing '%(comments)+#j' to: storage/shared/Youtube/a spiritual breakcore 2025 mix jdoLvM5iCdQ machine slvts public 14⧸01⧸2025 4.json
[info] Writing '%(duration>%H:%M:%S)+j' to: storage/shared/Youtube/a spiritual breakcore 2025 mix jdoLvM5iCdQ machine slvts public 14⧸01⧸2025 5.json
``` | question | low | Critical |
2,811,876,701 | neovim | 'guicursor' color change not working in Simple Terminal (suckless ST) | ## Issue Description
I have NeoVim configured to change the cursor's color depending on the mode. See exert from my configuration in Lua:
```
vim.cmd.highlight({"iCursor", "guibg=#a9b665"}) -- gruvbox green
vim.cmd.highlight({"rCursor", "guibg=#e78a4e"}) -- gruvbox orange
vim.cmd.highlight({"vCursor", "guibg=#ea6962"}) -- gruvbox red
vim.cmd.highlight({"cCursor", "guibg=#7daea3"}) -- gruvbox blue
vim.opt.guicursor = "a:block-Cursor,i:block-iCursor,v:block-vCursor,c-ci-cr:block-cCursor,r:block-rCursor"
```
This works as expected in WezTerm, as does the following simplified test.
However in ST, the cursor color never changes from the terminal set default #f8f8f2.
## Steps to reproduce
`nvim --clean`
`:set termguicolors`
`:highlight Cursor guibg=black`
`:highlight iCursor guibg=green`
`:set guicursor=n-v-c:block-Cursor,i:block-iCursor`
Enter *Insert Mode*
Exit *Insert Mode*
### Expected behavior
Cursor is black in *Normal Mode*, turns green upon entering *Insert Mode*, and returns back to black on exiting *Insert Mode*.
### Actual behavior
Cursor remains a #f8f8f2 colored block throughout, as defined by in ST's config.h:
```
/* special colors */
[256] = "#282a36", /* background */
[257] = "#f8f8f2", /* foreground */
```
## What I tried
### Method A
`TERM=xterm-256color`
Setting $TERM to xterm-256color in ST.
#### Outcome
When preforming the **Steps to reproduce** above, behavior now matches the **Expected behavior**. However, after exiting NeoVim via
`:q` the cursor remains black and all terminal text is colored black too, which should not happen.
### Method B
Looking for a relevant ST patch
#### Outcome
Could not find one.
### Method C
Verify via `printf "\033[31m"` that ST "actually supports termcodes to change the cursor color" [#29498](https://github.com/neovim/neovim/issues/29498#issuecomment-2322500302)
#### Outcome
Terminal text turns red, however cursor color remains #f8f8f2.
### Method A + C
#### Outcome
No change from **Method C Outcome**, cursor still #f8f8f2.
## Thoughts
While the **Outcome** of **Method C** would indicate this is an issue with ST not supporting termcodes for cursor color change, the fact that setting `TERM=xterm-256color`(**Method A**) doesn't affect the outcome of the termcode, while it does affect NeoVim's behavior positivly (cursor changes color), I hope there may be a way to natively enable NeoVim to change ST's cursor color.
## Terminfo
Terminfo section from:
`nvim -V3log` and then `:q`
[log.txt](https://github.com/user-attachments/files/18552252/log.txt)
### Relevant software info
OS: Arch/ Linux 6.12.10-arch1-1 x86_64
`nvim --version`: NVIM v0.10.3 -- installed via `pacman -S neovim`
[ST](https://st.suckless.org/) version: [0.9.2](https://dl.suckless.org/st/st-0.9.2.tar.gz)
_(for reference) WezTerm: 20240203-110809-5046fc22_
### $TERM
$TERM=st-256color
#### Vim (not Nvim) behaves the same?
N/A, **Steps to reproduce** with vim 9.1, `vim -u DEFAULTS` do not working in ST *or* WezTerm | tui | low | Minor |
2,811,896,455 | vscode | blackboxai troubleshooting with workspace | ADD ISSUE DESCRIPTION HERE
Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:134.0) Gecko/20100101 Firefox/134.0
Embedder: unknown
<!-- generated by web issue reporter --> | info-needed,triage-needed | low | Minor |
2,811,903,664 | rust | macOS deployment target defaults differ between rustc, cc-rs and clang | When `MACOSX_DEPLOYMENT_TARGET` is not set, rustc defaults to macOS 10.12 for Intel targets and 11.0 for aarch64 targets:
https://github.com/rust-lang/rust/blob/f85c6de55206dbee5ffedfd821df1503a7b92346/compiler/rustc_codegen_ssa/src/back/apple.rs#L69
https://github.com/rust-lang/rust/blob/f85c6de55206dbee5ffedfd821df1503a7b92346/compiler/rustc_codegen_ssa/src/back/apple.rs#L87
However, this does not match the default behavior for `clang`, which defaults to the selected SDK versions; unless changed otherwise, a C program built with `clang` uses the macOS host version as deployment target. The `cc-rs` crate also defaults to this behavior.
This difference in behavior causes issues when a Rust program has a dependency on a C library and does not set a minimum deployment target: The Rust binary tells the linker to target 10.12 / 11.0, but as the C library requires a higher minimum deployment target, a warning is emitted and the binary ends up targeting the higher version. [This was recently observed with miri](https://github.com/rust-lang/rust/issues/136086), which is built in a macOS 14 GitHub Runner:
```
ld: object file (/Users/runner/work/miri/miri/target/release/deps/libtikv_jemalloc_sys-80d1ddce8807bb5c.rlib[11](buf_writer.pic.o)) was built for newer 'macOS' version (14.5) than being linked (11.0)
```
In this case, miri does not have a deployment target set, so rustc tells the linker to emit a binary targeting 10.12; however, jemalloc-sys built jemalloc using clang's defaults, so it ended up targeting 14.5.
In a perfect world, projects would always set a deployment target and the linker would actually enforce that binaries cannot depend on objects that require a higher minimum macOS version instead of emitting a warning and targeting the higher version; alas, we're stuck with a warning with a not-so-great message. However, as incomprehensible the message may be, it is still indicative of a potential bug, especially if the user told the Rust part to create a binary targeting, say, 11.0, but the project then accidentally pulls in a dependency that targets 13.0 - the resulting binary would be created for 13.0 and might not run on 11.0 at all. Unfortunately, rustc can't not set a default deployment target by itself if the user hasn't specified one - it invokes the linker and has to pass it a deployment version; though it could compute the highest minimum version of all objects files it passes to the linker.
(@madsmtm has indicated wanting to change `cc-rs`'s defaults to match rustc's behavior, so that a Rust program building a C library via `cc` would not run into a deployment target mismatch; without such a change, it's too likely to be a false positive.)
<!-- TRIAGEBOT_START -->
<!-- TRIAGEBOT_ASSIGN_START -->
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"madsmtm"}$$TRIAGEBOT_ASSIGN_DATA_END -->
<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END --> | A-linkage,T-compiler,C-tracking-issue,T-libs,O-apple | low | Critical |
2,811,947,378 | vscode | Relative file link detection in log files | When viewing `.log` files in the editor, absolute file paths will be detected as links, but not relative paths (to either the workspace root or the opened file). Notably this is different in the terminal, where relative paths are clickable without issue, and it would be useful if the detection in `.log` files was similarly flexible.
I am aware that you can insert `file://` at the start and it will be detected in a link, but no log file is going to have this by default, and it doesn't work with line/column numbers regardless.
<!-- ⚠️⚠️ 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
<!-- 🪓 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 11 10.0.22621
Steps to Reproduce:
1. Create a `.log` file
2. Type the relative path and absolute path of a file in the workspace
3. The absolute path will be highlighted and clickable, but not the relative path
| feature-request,output | low | Critical |
2,811,948,373 | stable-diffusion-webui | [Bug]: ControlNet IP-Adapter error（ModuleNotFoundError: No module named 'onnx'） | ### Checklist
- [ ] The issue exists after disabling all extensions
- [x] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [x] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet
### What happened?
After upgrading to the latest version, I started getting an error with the Controlnet IP-Adapter.
ModuleNotFoundError: No module named 'onnx'
It says this and I can't load images. Is there a solution?
After a clean install, I tried running the following code before running [Start Stable-Diffusion]:
!pip install onnx
Then when I run [Start Stable-Diffusion] I get the following error:
ImportError: cannot import name 'mesh_core_cython' from 'insightface.thirdparty.face3d.mesh.cython' (unknown location)
### Steps to reproduce the problem
1. Start the WebUI.
2. txt2img Enable ControlNet
3. Check Pixel Perfect
4. Select IP-Adapter for Control Type
5. Select ip-adapter_face_id_plus for Preprocessor
6. Select ip-adapter-faceid-plus_sd15 for Model
7. Specify image and prompt and run generation
### What should have happened?
It worked fine until January 14, 2025.
### What browsers do you use to access the UI ?
Google Chrome
### Sysinfo
[sysinfo-2025-01-27-01-56.json](https://github.com/user-attachments/files/18552646/sysinfo-2025-01-27-01-56.json)
### Console logs
```Shell
ControlNet preprocessor location: /content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/annotator/downloads
2025-01-27 01:44:52,743 - ControlNet - INFO - ControlNet v1.1.455
Loading weights [1a17bcd93d] from /content/gdrive/MyDrive/sd/stable-diffusion-webui/models/Stable-diffusion/beautifulRealistic_v7.safetensors
2025-01-27 01:44:53,714 - ControlNet - INFO - ControlNet UI callback registered.
Creating model from config: /content/gdrive/MyDrive/sd/stable-diffusion-webui/configs/v1-inference.yaml
Running on public URL: https://6deb096a25f20cdf17.gradio.live
✔ Connected
Startup time: 19.9s (import torch: 8.0s, import gradio: 1.1s, setup paths: 1.6s, initialize shared: 0.2s, other imports: 0.8s, list SD models: 1.8s, load scripts: 2.9s, create ui: 0.8s, gradio launch: 2.0s, add APIs: 0.4s).
Loading VAE weights specified in settings: /content/gdrive/MyDrive/sd/stable-diffusion-webui/models/VAE/vae-ft-mse-840000-ema-pruned.safetensors
Applying attention optimization: xformers... done.
Model loaded in 5.5s (load weights from disk: 0.6s, create model: 1.3s, apply weights to model: 2.4s, load VAE: 0.4s, load textual inversion embeddings: 0.4s, calculate empty prompt: 0.2s).
2025-01-27 01:55:45,799 - ControlNet - INFO - unit_separate = False, style_align = False
2025-01-27 01:55:46,219 - ControlNet - INFO - Loading model: ip-adapter-faceid-plus_sd15 [d86a490f]
2025-01-27 01:55:46,398 - ControlNet - INFO - Loaded state_dict from [/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/models/ip-adapter-faceid-plus_sd15.bin]
2025-01-27 01:55:47,018 - ControlNet - INFO - ControlNet model ip-adapter-faceid-plus_sd15 [d86a490f](ControlModelType.IPAdapter) loaded.
2025-01-27 01:55:47,027 - ControlNet - INFO - Using preprocessor: ip-adapter_face_id_plus
2025-01-27 01:55:47,027 - ControlNet - INFO - preprocessor resolution = 512
*** Error running process: /content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 832, in process
script.process(p, *script_args)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 1228, in process
self.controlnet_hack(p)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 1213, in controlnet_hack
self.controlnet_main_entry(p)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 941, in controlnet_main_entry
controls, hr_controls, additional_maps = get_control(
^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 290, in get_control
controls, hr_controls = list(zip(*[preprocess_input_image(img) for img in optional_tqdm(input_images)]))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 290, in <listcomp>
controls, hr_controls = list(zip(*[preprocess_input_image(img) for img in optional_tqdm(input_images)]))
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 242, in preprocess_input_image
result = preprocessor.cached_call(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/supported_preprocessor.py", line 198, in cached_call
result = self._cached_call(input_image, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/utils.py", line 82, in decorated_func
return cached_func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/utils.py", line 66, in cached_func
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/supported_preprocessor.py", line 211, in _cached_call
return self(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/preprocessor/legacy/legacy_preprocessors.py", line 105, in __call__
result, is_image = self.call_function(
^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/preprocessor/legacy/processor.py", line 768, in face_id_plus
face_embed, _ = g_insight_face_model.run_model(img)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/preprocessor/legacy/processor.py", line 696, in run_model
self.load_model()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/preprocessor/legacy/processor.py", line 686, in load_model
from insightface.app import FaceAnalysis
File "/usr/local/lib/python3.11/dist-packages/insightface/__init__.py", line 16, in <module>
from . import model_zoo
File "/usr/local/lib/python3.11/dist-packages/insightface/model_zoo/__init__.py", line 1, in <module>
from .model_zoo import get_model
File "/usr/local/lib/python3.11/dist-packages/insightface/model_zoo/model_zoo.py", line 11, in <module>
from .arcface_onnx import *
File "/usr/local/lib/python3.11/dist-packages/insightface/model_zoo/arcface_onnx.py", line 10, in <module>
import onnx
ModuleNotFoundError: No module named 'onnx'
---
100% 46/46 [00:03<00:00, 11.95it/s]
```
### Additional information
I downloaded ip-adapter-faceid-plusv2_sd15.bin from the link below.
https://huggingface.co/h94/IP-Adapter-FaceID/tree/main | bug-report | low | Critical |
2,811,951,093 | flutter | Add `BorderRadiusGeometry` Support to `Divider` Widget for Customizable Border Radius | ### Use case
I can't set border radius to divider. this is necessary when you have a thick rounded border and almost all the cases, if you have a thick divider, you might have some corner radius. In this below SS, see that the edges are very sharp and there's no default way to make divider edge's rounded.
<img width="386" alt="Image" src="https://github.com/user-attachments/assets/025987f4-3361-40b2-bdcd-ac1d6cd77bf5" />
this is the code that produces above divider,
```dart
Divider(
indent: 200,
endIndent: 200,
height: 40,
thickness: 5,
color: Colors.grey,
)
```
### Proposal
Add an way to pass the `BorderRadiusGeometry` to the divider as it's used a `Container` to construct the divider. So, this radius geometry value will pass to the Container's `BoxDecoration` field. something like this,
```diff
@override
Widget build(BuildContext context) {
final ThemeData theme = Theme.of(context);
final DividerThemeData dividerTheme = DividerTheme.of(context);
final DividerThemeData defaults =
theme.useMaterial3 ? _DividerDefaultsM3(context) : _DividerDefaultsM2(context);
final double height = this.height ?? dividerTheme.space ?? defaults.space!;
final double thickness = this.thickness ?? dividerTheme.thickness ?? defaults.thickness!;
final double indent = this.indent ?? dividerTheme.indent ?? defaults.indent!;
final double endIndent = this.endIndent ?? dividerTheme.endIndent ?? defaults.endIndent!;
return SizedBox(
height: height,
child: Center(
child: Container(
height: thickness,
margin: EdgeInsetsDirectional.only(start: indent, end: endIndent),
decoration: BoxDecoration(
+ borderRadius: radius,
border: Border(bottom: createBorderSide(context, color: color, width: thickness)),
),
),
),
);
}
``` | c: new feature,framework,c: proposal,team-framework | low | Minor |
2,811,955,693 | terminal | Progress towards next release | Hi there,
I'm new round here, excitedly anticipating the release of 1.22 so I can save snippets of some of the longer commands I run!
Is there a publicly-available place I could view to check to give a coarse idea of how far away release is? Don't mean to bug you guys, but the [roadmap linked from the readme](https://github.com/microsoft/terminal/blob/main/doc/roadmap-2023.md) seems to be missing some recent details,
Many thanks and appreciate all you're doing!
-Ben | Needs-Triage,Needs-Tag-Fix | low | Critical |
2,811,956,609 | vscode | January 2025 Endgame | - *01/27* Code freeze for the endgame
- *01/28* [Endgame starts](https://github.com/Microsoft/vscode/wiki/Development-Process#inside-an-iteration)
- *01/31* Endgame done
- *02/05* Expected release date (this may change)
##### Monday
- [x] Pin endgame issue on GitHub **@connor4312**
- [x] Run [OSS tool](https://github.com/microsoft/vscode-build-tools/tree/main/distro-tools) **@connor4312**
- [x] Update links in the [Endgame notebooks](https://github.com/microsoft/vscode/blob/main/.vscode/notebooks/endgame.github-issues) to point to new milestone **@connor4312**
- [x] Code freeze at 5pm PT, PRs should no longer be accepted to ensure a green build
- [x] Ensure we have a green build on all platforms at 5pm PT
- [ ] [🔖Ensure all closed feature-requests](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+milestone%3A%22January+2025%22+label%3Afeature-request+-label%3Averification-needed+-label%3Aon-testplan+-label%3Averified+-label%3A*duplicate+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger) either have a `verification-needed` or `on-testplan` label
- [x] Create test plan items following the template [here](https://github.com/microsoft/vscode/wiki/Writing-Test-Plan-Items) by 6pm PT
- [x] Remind the team that TPIs should be written so that anyone can test. If this is not feasible, then TPI authors should assign specific testers **@connor4312**
- [x] Update your availability for testing here - https://tools.code.visualstudio.com/team-manifest **team**
- [x] Update availability of testers in vacation (Check OOF section in the Internal Backlog Plan). Double check N/A testers. **@connor4312**
- [x] Remind team that in the event of sickness or overload with TPIs, to inform the endgame champ ASAP so items can be reassigned
- [x] Remind team to go through their fixed issues for the milestone and update repro steps for issues which require more detailed instructions.
- [x] Set up the endgame retrospective to discuss process improvement
- Schedule an endgame restrospective with @connor4312, endgame buddy, and next @connor4312 for late debt week
- [Create the endgame retrospective tracking issue](https://github.com/microsoft/vscode-internalbacklog/issues/new?template=endgame-retrospective.md)
- [x] Set up a standup meeting for Friday to discuss candidates
##### Tuesday
- [x] Test plan items assigned (using https://tools.code.visualstudio.com/test-plan-items)
- Run the tool multiple times to balance load if test items come in later and assignments are already made
- [Assigned to you](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+assignee%3A%40me++label%3Atestplan-item+)
- [x] Test build starts at 7am CET
- [x] Test plan ready by 8am CET
- [x] Remind the team about the priorities
- Tuesday should be dedicated _exclusively_ to testing activities. Our goal is to ensure the completion of all Test Plan Items (TPIs) and subsequently proceed with the verification phase. Fixes or commits should be refrained from unless there are exceptional circumstances such as blocked TPIs or build-related issues. On Tuesday Redmond EOD, only blocked TPIs should remain open with a corresponding label `blocked` and status update comment in the issue.
- [ ] Testing and Verification
- [ ] [🔖Testing](https://github.com/issues?q=is%3Aopen+is%3Aissue+label%3Atestplan-item+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger)
- [ ] [🔖Verification of Bugs Reported by me](https://github.com/issues?q=is%3Aissue%20milestone%3A"January%202025"%20author%3A%40me%20repo%3Amicrosoft%2Fmonaco-editor%20repo%3Amicrosoft%2Fvscode%20repo%3Amicrosoft%2Fvscode-anycode%20repo%3Amicrosoft%2Fvscode-copilot%20repo%3Amicrosoft%2Fvscode-copilot-release%20repo%3Amicrosoft%2Fvscode-dev%20repo%3Amicrosoft%2Fvscode-dev-chrome-launcher%20repo%3Amicrosoft%2Fvscode-emmet-helper%20repo%3Amicrosoft%2Fvscode-extension-telemetry%20repo%3Amicrosoft%2Fvscode-github-issue-notebooks%20repo%3Amicrosoft%2Fvscode-hexeditor%20repo%3Amicrosoft%2Fvscode-internalbacklog%20repo%3Amicrosoft%2Fvscode-js-debug%20repo%3Amicrosoft%2Fvscode-jupyter%20repo%3Amicrosoft%2Fvscode-jupyter-internal%20repo%3Amicrosoft%2Fvscode-l10n%20repo%3Amicrosoft%2Fvscode-livepreview%20repo%3Amicrosoft%2Fvscode-pull-request-github%20repo%3Amicrosoft%2Fvscode-python%20repo%3Amicrosoft%2Fvscode-python-debugger%20repo%3Amicrosoft%2Fvscode-references-view%20repo%3Amicrosoft%2Fvscode-remote-release%20repo%3Amicrosoft%2Fvscode-remote-repositories-github%20repo%3Amicrosoft%2Fvscode-remote-tunnels%20repo%3Amicrosoft%2Fvscode-remotehub%20repo%3Amicrosoft%2Fvscode-settings-sync-server%20repo%3Amicrosoft%2Fvscode-unpkg%20repo%3Amicrosoft%2Fvscode-vsce%20repo%3Amicrosoft%2Fvscode-pylint%20repo%3Amicrosoft%2Fvscode-black-formatter%20repo%3Amicrosoft%2Fvscode-isort%20repo%3Amicrosoft%2Flsprotocol%20repo%3Amicrosoft%2Fvscode-flake8%20repo%3Amicrosoft%2Fvscode-autopep8%20repo%3Amicrosoft%2Fvscode-python-tools-extension-template%20repo%3Amicrosoft%2Fvscode-mypy%20repo%3Amicrosoft%2Fvscode-python-debugger%20-label%3Aiteration-plan%20-label%3Aendgame-plan%20-label%3Atestplan-item%20label%3Abug%20-label%3Aduplicate%20-label%3A*duplicate%20-label%3Ainvalid%20-label%3Aas-designed%20-label%3Aerror-telemetry%20is%3Aclosed%20-label%3Averified%20-label%3Aon-testplan%20)
- [ ] [🔖Verification needed](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Averification-needed+-label%3Averified+is%3Aclosed+-label%3Aon-testplan)
- [ ] [🔖Verification](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Abug+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aas-designed+-label%3Aerror-telemetry+is%3Aclosed+-label%3Averified+-label%3Aon-testplan) (If verification needed is finished)
##### Wednesday
- [ ] [🔖Testing](https://github.com/issues?q=is%3Aopen+is%3Aissue+label%3Atestplan-item+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger)
- These remaining TPIs should be the ones that are currently blocked. Discuss during the standup and redistribute assignments based on the TPI owner and the test coverage. For instance, if a TPI is owned by a member from Zurich and has not undergone sufficient testing, it will be reassigned to one of the Zurich team members.
- [ ] Remind team members to triage issues found in testing and assign major issues that they intend to fix to the current milestone. Remind team to move out or close other open issues/PRs on the milestone that they do not intend to fix this milestone.
- [ ] [🔖Verification needed](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Averification-needed+-label%3Averified+is%3Aclosed+-label%3Aon-testplan)
- [ ] Fixing (self-assigned, milestone assigned)
- [ ] [🔖Verification](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Abug+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aas-designed+-label%3Aerror-telemetry+is%3Aclosed+-label%3Averified+-label%3Aon-testplan)
- [ ] Message team members as needed to add steps to `verification-steps-needed` issues **@connor4312**
##### Thursday
- [ ] Make sure the `insider` build is green **@connor4312**
- [ ] [Disable continuous `insider` builds](https://builds.code.visualstudio.com/builds/insider) and announce in `#release` **@connor4312**
> :loudspeaker: Continuous `insider` builds are now disabled.
- [ ] Fixing (self-assigned, milestone assigned)
- Increased scrutiny sets in due to testing being completed. Fixes pose a much higher risk
- Move open issues/PRs to the next month that can be deferred
- [ ] Emphasize to the team that we want to verify as many issues as we can before the branching time, and ping team members as needed to remind them to add steps to `verification-steps-needed` issues **@connor4312**
- [ ] [🔖Verification needed](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Averification-needed+-label%3Averified+is%3Aclosed+-label%3Aon-testplan)
- [ ] [🔖Verification](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Abug+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aas-designed+-label%3Aerror-telemetry+is%3Aclosed+-label%3Averified+-label%3Aon-testplan)
- [ ] Run `scripts/test-documentation.sh|bat` after compiling the vscode repo, and fix any issues regarding new undocumented colors. Changes made to the vscode-docs repository must be merged to the main branch of that repository for the script to acknowledge them. False positives within the `color` section in `vscode-known-variables.json` can be moved under the `others` section of that file. **@connor4312**
##### Thursday/Friday - Depending on @connor4312 timezone
- [ ] By Thursday EOD (Redmond) or Friday BOD (Zurich), branch from `main` and release **@connor4312**
- [ ] Branch following repositories to `release/<x.y>`
- [ ] vscode
- [ ] vscode-distro
- [ ] vscode-dev
- [ ] Localization: Run [Update VS Code Branch](https://monacotools.visualstudio.com/Monaco/_build?definitionId=369) build with `release/*` as the VS Code Branch parameter (it's the default so you shouldn't have to change anything)
- [ ] Announce `main` is open for business and all issues on the current iteration are candidates and that the candidate release process is to be followed.
- [ ] Build and manually release Insider from release/<x.y> branch for Code
- [ ] Build and manually release Insider from release/<x.y> branch for vscode.dev (if there were vscode.dev candidates)
- [ ] Announce in `#release` **@connor4312**
> :loudspeaker: Extension authors ensure all release branch changes have been published to users, manually building and releasing if necessary.
- [ ] Build but don't release a `stable` build from release/<x.y> branch to ensure stable build is green **@connor4312**
- [ ] Bump up the version in `package.json` on `main` & run `npm i` to bump `package-lock.json` as well. **@connor4312**
- [ ] [Create next milestone](https://github.com/microsoft/vscode/milestones/new) on `microsoft/vscode` repo and ensure that it has a due date. The created milestone and its due date will be automatically synced across our repos. **@connor4312**
##### Friday
- [ ] Only candidate issues are open and assigned to [🔖milestone](https://github.com/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger)
- [ ] All issues [🔖verified](https://github.com/issues?q=is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+-label%3Aiteration-plan+-label%3Aendgame-plan+-label%3Atestplan-item+label%3Abug+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aas-designed+-label%3Aerror-telemetry+is%3Aclosed+-label%3Averified+-label%3Aon-testplan)
- [ ] All open PRs on the milestone [🔖merged or deferred](https://github.com/issues?q=is%3Apr+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger+is%3Aopen)
- [ ] Fix [`candidate` issues](https://github.com/issues?utf8=%E2%9C%93&q=is:open+is:issue+label:candidate+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger) (major bugs only)
- Discuss and get approval in stand up
- Review and merge into `release/<x.y>`
- [Queue new auto-published insiders build](https://monacotools.visualstudio.com/Monaco/_build?definitionId=111) as candidates are merged **@connor4312**
- Author of candidate PR should find verifier
- Satellite modules/npm packages ready, version updated, smoke tested
- [ ] yo generator **@aeschli**
- [ ] js-debug **@connor4312**
- [ ] Debug Adapter Protocol **@connor4312**
- [ ] vscode-debugadapter-node **@connor4312**
- [ ] vscode-test-web **@aeschli**
- [ ] All release notes updated
- release notes are collected in a file named _`v<Major>_<Minor>.md`\_ in this [repo directory](https://github.com/Microsoft/vscode-docs/blob/vnext/release-notes/)
- Release notes screen recording guidance: https://microsoft-my.sharepoint.com/:p:/p/buhollan/Ecg_j89jzlVGtfqWGy7SQBEB_OsuLPZ65jjKRVlo_OdlgA
- [ ] Documentation added or updated
- [ ] [Acknowledge third-party pull requests](https://tools.code.visualstudio.com/acknowledgement) in release notes. **@connor4312**
- [ ] Acknowledge [issue trackers](https://github.com/microsoft/vscode-internalbacklog/wiki/Community-Triage---Credits) from the community **@chrmarti**
- When done fixing/verifying and there are changes since last build at the end of day PT
- [ ] Build and manually release Insider from release/<x.y> for Code **@connor4312**
- [ ] Build and manually release Insider from release/<x.y> for vscode.dev (if there were vscode.dev candidates) **@connor4312**
##### Monday
- [ ] Polish release notes **@ntrogh**
- [ ] Schedule an endgame restrospective with with @connor4312, endgame buddy, and next @connor4312 for this week. [Retrospective template](https://github.com/microsoft/vscode-internalbacklog/blob/main/.github/ISSUE_TEMPLATE/endgame-retrospective.md#L14)
- [ ] Decide whether a [Patch Tuesday release](https://github.com/microsoft/vscode-internalbacklog/wiki/Handling-MSRC-Cases#msrc--patch-tuesday-process) will happen:
- Check the internal iteration plan for scheduled security issues (MSRCs) to determine if a Patch Tuesday release is needed.
- If no Patch Tuesday release is planned, use the [Patch Tuesday E-Mail Template](https://github.com/microsoft/vscode-internalbacklog/wiki/Patch-Tuesday-E-Mail-Template) to let the Updates team ([[email protected]](mailto:[email protected])) know of that fact. Please cc Monacotools on this email as the client patching team has asked us to do so. **@connor4312**
- Otherwise, if a Patch Tuesday release is necessary, start off a [Patch Tuesday Release plan](https://github.com/microsoft/vscode-internalbacklog/wiki/Handling-MSRC-Cases#are-you-endgame-champbuddy) **@connor4312**
- [ ] Remind the team: if they are going to be OOF for more than five days during the next iteration, assign someone to look out for critical issues in their feature areas and fix them if necessary. This helps with bug identification and fixing for recovery releases. **@connor4312**
##### Monday - Wednesday
- [ ] [🔖milestone issues](https://github.com/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22January+2025%22+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger)
- [ ] [🔖candidate issues](https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+label%3Acandidate+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger)
- [ ] Polish release notes **redmond**
- [ ] Fix [`candidate` issues](https://github.com/issues?utf8=%E2%9C%93&q=is:open+is:issue+label:candidate+repo:microsoft/monaco-editor%20repo:microsoft/vscode%20repo:microsoft/vscode-anycode%20repo:microsoft/vscode-copilot%20repo:microsoft/vscode-copilot-release%20repo:microsoft/vscode-dev%20repo:microsoft/vscode-dev-chrome-launcher%20repo:microsoft/vscode-emmet-helper%20repo:microsoft/vscode-extension-telemetry%20repo:microsoft/vscode-github-issue-notebooks%20repo:microsoft/vscode-hexeditor%20repo:microsoft/vscode-internalbacklog%20repo:microsoft/vscode-js-debug%20repo:microsoft/vscode-jupyter%20repo:microsoft/vscode-jupyter-internal%20repo:microsoft/vscode-l10n%20repo:microsoft/vscode-livepreview%20repo:microsoft/vscode-pull-request-github%20repo:microsoft/vscode-python%20repo:microsoft/vscode-python-debugger%20repo:microsoft/vscode-references-view%20repo:microsoft/vscode-remote-release%20repo:microsoft/vscode-remote-repositories-github%20repo:microsoft/vscode-remote-tunnels%20repo:microsoft/vscode-remotehub%20repo:microsoft/vscode-settings-sync-server%20repo:microsoft/vscode-unpkg%20repo:microsoft/vscode-vsce%20repo:microsoft/vscode-pylint%20repo:microsoft/vscode-black-formatter%20repo:microsoft/vscode-isort%20repo:microsoft/lsprotocol%20repo:microsoft/vscode-flake8%20repo:microsoft/vscode-autopep8%20repo:microsoft/vscode-python-tools-extension-template%20repo:microsoft/vscode-mypy%20repo:microsoft/vscode-python-debugger) (major bugs only)
- Discuss and get approval in stand up
- Review and merge into `release/<x.y>`
- [Queue new auto-published insiders build](https://monacotools.visualstudio.com/Monaco/_build?definitionId=111) as candidates are merged **@connor4312**
- Author of candidate PR should find verifier
- [ ] Build but don't release stable for all platforms as new candidate issues come in **@connor4312**
- [ ] Coordinate the official release timing with team and more specifically, team extension authors (ex: Jupyter and Copilot rely on VS Code release) **@connor4312**
> **Note:** The `Insiders` build needs to be in the wild for 24 hours before we can enter the last phase of the endgame, though the sanity testing step alone can happen earlier if there are no new candidates. **@connor4312**
##### Wednesday/Thursday - Expected release day (this may change)
- [ ] Build stable for all platforms **@connor4312**
- [ ] [Sanity Testing](https://github.com/microsoft/vscode/wiki/Sanity-Check)
- [ ] Windows 64 bit **owner**
- [ ] System Installer
- [ ] User Installer
- [ ] Archive
- [ ] Server
- [ ] CLI
- [ ] Windows ARM64 **owner**
- [ ] System Installer
- [ ] User Installer
- [ ] Archive
- [ ] Server
- [ ] CLI
- [ ] macOS Intel **owner**
- [ ] Archive
- [ ] Universal Archive
- [ ] Server
- [ ] CLI
- [ ] macOS ARM64 **owner**
- [ ] Archive
- [ ] Universal Archive
- [ ] Server
- [ ] CLI
- [ ] Linux x64 **owner**
- [ ] Archive
- [ ] DEB
- [ ] RPM
- [ ] Snap
- [ ] Linux Server **owner** _(can be tested from any OS with Docker)_
- [ ] x64
- [ ] ARM32
- [ ] ARM64
- [ ] x64 Alpine
- [ ] ARM64 Alpine
- [ ] Linux CLI **owner** _(can be tested from any OS with Docker)_
- [ ] x64
- [ ] ARM32
- [ ] ARM64
- [ ] x64 Alpine
- [ ] ARM64 Alpine
- [ ] [Publish website](<https://github.com/microsoft/vscode-website?tab=readme-ov-file#publishing-a-website-change)>) **@ntrogh** **@connor4312**
- [ ] Release stable from builds page no later than 11am PT **@connor4312**
- [ ] Trigger the [vscode.dev Deploy pipeline](https://dev.azure.com/monacotools/Monaco/_build?definitionId=276) for `release/x.y` for the `prod` deployment target. Note that there are four deploy approvals needed - one for overall and one per each of the three service regions **@connor4312**
- [ ] Request approval from another team member at the necessary step to deploy the vscode.dev build. **@connor4312**
- [ ] Create an official release **@connor4312**
- [ ] Create a tag (make sure you pull the release branch first): `git tag <x.y.z>`
- [ ] Push the tag: `git push origin <x.y.z>`
- [ ] Create a GitHub release: [Open the GitHub tags](https://github.com/microsoft/vscode/tags), and click far right `... > Create Release`. Use the correct title and description from our release notes. Also change the relative links for the key highlight list items to absolute links [Example](https://github.com/microsoft/vscode/releases/tag/1.39.0)
- [ ] X announcement **@chrisdias**
- [ ] Create and publish next release notes placeholder **@ntrogh**
- [ ] Enable scheduled `insider` builds **@connor4312**
- [ ] Release the latest insiders build based on main from the builds page with all artifacts **@connor4312**
- [ ] [VS Code](https://builds.code.visualstudio.com/builds/insider) (Toggle the checkbox of the build)
- [ ] [vscode.dev](https://dev.azure.com/monacotools/Monaco/_build?definitionId=276) (Run pipeline, change no parameters)
- [ ] [Publish @types/vscode](https://github.com/microsoft/vscode/wiki/Publish-vscode-types) **@connor4312**
- [ ] Close the milestone on [GitHub](https://github.com/microsoft/vscode/milestones) **@connor4312**
| endgame-plan | low | Critical |
2,811,958,419 | ollama | Error: an error was encountered while running the model: unexpected EOF (8x H100, deepseek-r1:671b) | ### What is the issue?
I'm using a server with 8xH100 GPUs, trying to run the deepseek-r1:671b model.
This works for a fair bit, say about 1000-2000 generated tokens, and then it ends with:
`Error: an error was encountered while running the model: unexpected EOF`
I don't quite know how to debug this -- is there a way to get a stack trace of some sort?
What could be causing this error?
Reproduction is pretty simple:
1. spin up a 8xH100 NVL instance (I use Lambda labs and Google gSC)
2. run ollama run deepseek-r1:671b
3. ask two or three questions that each generate more than a small amount of text
4. sudden `Error: an error was encountered while running the model: unexpected EOF` in the middle of generation
`NVIDIA-SMI 550.127.05 Driver Version: 550.127.05 CUDA Version: 12.4`
`Intel(R) Xeon(R) Platinum 8480+`
### OS
Linux
### GPU
Nvidia
### CPU
AMD, Intel
### Ollama version
0.5.7 | bug | low | Critical |
2,811,967,580 | TypeScript | Tsc does not behave correctly when files are moved or deleted | ### 🔎 Search Terms
tsc delete old files
### 🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about tsc not deleting old files properly
### ⏯ Playground Link
_No response_
### 💻 Code
n/a
### 🙁 Actual behavior
Old files that tsc does not clean up can cause problems in a new build.
For example, if i have a file `src/foo.ts`, and then i delete it and replace it with a folder `src/foo/index.ts`, the fact that `dist/src/foo.d.ts` sticks around is a bug. Imports from `./foo` in the src folder will point to the old file that should have been deleted, rather than the new `foo` folder.
This can be worked around with a non-watch build by just saying `rm -rf dist/ && tsc` but that doesn't work for tsc watch, even with the clean option.
### 🙂 Expected behavior
At least for watch mode, but really for non-watch-mode too, there needs to be a way to delete the entire output directory before new output files are emitted. The way it works now is not correct and there's no way around it besides not using watch mode.
### Additional information about the issue
_No response_ | Suggestion,Out of Scope | low | Critical |
2,812,007,544 | ollama | requesting support new model(maybe not new): Qwen2.5-1M | Qwen has released a long context version of Qwen 2.5 on hugging face, hoping to add support:
https://huggingface.co/collections/Qwen/qwen25-1m-679325716327ec07860530ba
| model request | low | Major |
2,812,022,132 | pytorch | support arm architectures in your Docker images on docker hub? ( | ### 🚀 The feature, motivation and pitch
`pytorch` images on Docker Hub are still only available for amd64 architectures. Nvidia/cuda images support both arm64 and amd64. I believe we are seeing more and more devices offering Nvidia GPUs witth ARM cpu architecture, and multi-arch builds are commonplace. It would be great to have pytorch docker images that support these.
Thanks!
### Alternatives
_No response_
### Additional context
_No response_
cc @malfet @snadampal @milpuz01 | triaged,enhancement,module: docker,module: arm | low | Minor |
2,812,075,151 | PowerToys | The Powertoys Run panel background goes wrong | ### Microsoft PowerToys version
0.87.1
### Installation method
PowerToys auto-update
### Running as admin
Yes
### Area(s) with issue?
PowerToys Run
### Steps to reproduce
EDIT: I've noticed I am running Windows 21H2 while several similar issues indicates using 21H2 may cause this problem. Are there any workarounds to solve this instead of updating the system?
I have just updated powertoys from 0.81.0 to 0.87.0 and the Powertoys Run tool seems to have something wrong with the background color.
[PowerToysReport_2025-01-27-12-43-08.zip](https://github.com/user-attachments/files/18553564/PowerToysReport_2025-01-27-12-43-08.zip)
### ✔️ Expected Behavior
The panel background should be white and the characters should be black.
### ❌ Actual Behavior
The panel background color goes wrong and I can't see what is displayed on it.
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,812,077,929 | langchain | Llama-3.2-3B-Instruct failed to use with HuggingfacePipeline because of setting a non-string value as the pad_token | ### Checked other resources
- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).
### Example Code
The following code:
```python
from langchain_community.llms import HuggingFacePipeline
hf = HuggingFacePipeline.from_model_id(
model_id="meta-llama/Llama-3.2-3B-Instruct",
task="text-generation",
pipeline_kwargs={"max_new_tokens": 10},
)
from langchain_core.prompts import PromptTemplate
template = """Question: {question}
Answer: Let's think step by step."""
prompt = PromptTemplate.from_template(template)
chain = prompt | hf
question = "What is electroencephalography?"
print(chain.invoke({"question": question}))
```
### Error Message and Stack Trace (if applicable)
```
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████| 2/2 [00:00<00:00, 2.69it/s]
Traceback (most recent call last):
File "/home/ishi/work/hf_pipeline_sample.py", line 4, in <module>
hf = HuggingFacePipeline.from_model_id(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/ishi/work/langchain/libs/community/langchain_community/llms/huggingface_pipeline.py", line 172, in from_model_id
tokenizer.pad_token_id = model.config.eos_token_id
^^^^^^^^^^^^^^^^^^^^^^
File "/home/ishi/work/.venv/lib/python3.12/site-packages/transformers/tokenization_utils_base.py", line 1077, in __setattr__
raise ValueError(f"Cannot set a non-string value as the {key}")
ValueError: Cannot set a non-string value as the pad_token
```
### Description
I tried to do HuggingfacePipeline of langchain_community with Llama-3.2-3B-Instruct, but the error occured.
I think that it's the same bug as transformers issue [34869](https://github.com/huggingface/transformers/issues/34869).
When I changed /libs/community/langchain_community/llms/huggingface_pipeline.py [L172](https://github.com/langchain-ai/langchain/blob/master/libs/community/langchain_community/llms/huggingface_pipeline.py#L172) as followings, the error didn't occur.
```python
if tokenizer.pad_token_id is None:
if model.config.pad_token_id is not None:
tokenizer.pad_token_id = model.config.pad_token_id
elif model.config.eos_token_id is not None and isinstance(model.config.eos_token_id, int):
tokenizer.pad_token_id = model.config.eos_token_id
elif tokenizer.eos_token_id is not None:
tokenizer.pad_token_id = tokenizer.eos_token_id
else:
tokenizer.add_special_tokens({"pad_token": "[PAD]"})
```
It's the same procedure as [this](https://github.com/huggingface/text-generation-inference/pull/2774) pull request.
### System Info
System Information
------------------
OS: Ubuntu 24.04
Kernel Version: 6.8.0-51-generic
Python Version: 3.12.7
Model: Llama-3.2-3B-Instruct
langchain 0.3.15
langchain-community 0.3.15
langchain-core 0.3.31
transformers 4.47.1
| 🤖:bug | low | Critical |
2,812,091,234 | iptv | Broken: US - Tubi, Four in a Bed 24/7 Channel | ### Broken Links
#EXTINF:-1 tvg-id="",Four in a Bed (1080p)
https://apollo.production-public.tubi.io/live/ac-four-in-a-bed.m3u8
### What happened to the stream?
Not loading
### Notes (optional)
To the best of my knowledge, Tubi lost rights to the TV series as Channel 4 in the UK made a deal with Amazon to carry the series content as of January 1, 2025. As such, Tubi has dropped the 24/7 channel from their lineup and only has a few seasons under contract with Channel 4 UK in their video on demand section. The channel should be removed from the master list as it no longer exists on Tubi servers. Previous link to the content through their live-news server (as a backdoor) is also dead as are seemingly all other non-news channels. That previous link to the content was at https://live-news-manifest.tubi.video/live-news-manifest/csm/extlive/tubiprd01,Four-in-a-Bed.m3u8 . It is unknown at this time if their are any other live tv services running the program as a 24/7 channel.
### Contributing Guide
- [x] I have read [Contributing Guide](https://github.com/iptv-org/iptv/blob/master/CONTRIBUTING.md) | broken stream | low | Critical |
2,812,095,045 | transformers | Transformers is incompatible with flash attention version 2.7.3 | ### System Info
Copy-and-paste the text below in your GitHub issue and FILL OUT the two last points.
- `transformers` version: 4.48.0
- Platform: Linux-5.13.0-35-generic-x86_64-with-glibc2.31
- Python version: 3.10.11
- Huggingface_hub version: 0.27.1
- Safetensors version: 0.5.2
- Accelerate version: 0.29.0
- Accelerate config: not found
- PyTorch version (GPU?): 2.3.1+cu121 (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?: no
- Using GPU in script?: yes
- GPU type: NVIDIA A100-SXM4-80GB
Also
```
python -c 'import flash_attn; print(flash_attn.__version__)'
2.7.3
```
### 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, ...)
- [x] My own task or dataset (give details below)
### Reproduction
The path `/mnt/models/google/gemma2-2b` points to [Google Gemma2 2b model](https://huggingface.co/google/gemma-2-2b) from Huggingface.
```python
import torch
from transformers import AutoTokenizer
from transformers.tokenization_utils import PaddingStrategy
from transformers.models.gemma2 import Gemma2ForCausalLM
def main():
model_path = '/mnt/models/google/gemma2-2b'
tokenizer = AutoTokenizer.from_pretrained(model_path)
model = Gemma2ForCausalLM.from_pretrained(
model_path,
attn_implementation='flash_attention_2',
torch_dtype=torch.bfloat16,
).to('cuda')
texts = ['have a nice day', 'you too']
input_ids = tokenizer(
texts,
return_tensors='pt',
padding_side='left',
truncation=True,
max_length=256,
padding=PaddingStrategy.MAX_LENGTH,
).input_ids.to(model.device)
model.generate(input_ids, max_new_tokens=2)
if __name__ == '__main__':
main()
```
Running this script gives
```python
python reproduce.py
You are attempting to use Flash Attention 2.0 with a model not initialized on GPU. Make sure to move the model to GPU after initializing it on CPU with `model.to('cuda')`.
Loading checkpoint shards: 100%|███████████████████████████████| 3/3 [00:01<00:00, 2.68it/s]
The 'batch_size' attribute of HybridCache is deprecated and will be removed in v4.49. Use the more precisely named 'self.max_batch_size' attribute instead.
Traceback (most recent call last):
File "/my_code/turbo-alignment/reproduce.py", line 31, in <module>
main()
File "/my_code/turbo-alignment/reproduce.py", line 27, in main
model.generate(input_ids, max_new_tokens=2)
File "/usr/local/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/transformers/generation/utils.py", line 2255, in generate
result = self._sample(
File "/usr/local/lib/python3.10/site-packages/transformers/generation/utils.py", line 3254, in _sample
outputs = self(**model_inputs, return_dict=True)
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/transformers/models/gemma2/modeling_gemma2.py", line 842, in forward
outputs = self.model(
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/transformers/models/gemma2/modeling_gemma2.py", line 629, in forward
layer_outputs = decoder_layer(
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/transformers/models/gemma2/modeling_gemma2.py", line 299, in forward
hidden_states, self_attn_weights = self.self_attn(
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
return forward_call(*args, **kwargs)
File "/usr/local/lib/python3.10/site-packages/transformers/models/gemma2/modeling_gemma2.py", line 236, in forward
attn_output, attn_weights = attention_interface(
File "/usr/local/lib/python3.10/site-packages/transformers/integrations/flash_attention.py", line 50, in flash_attention_forward
attn_output = _flash_attention_forward(
File "/usr/local/lib/python3.10/site-packages/transformers/modeling_flash_attention_utils.py", line 305, in _flash_attention_forward
query_states, key_states, value_states, indices_q, cu_seq_lens, max_seq_lens = _upad_input(
File "/usr/local/lib/python3.10/site-packages/transformers/modeling_flash_attention_utils.py", line 124, in _upad_input
query_layer, indices_q, cu_seqlens_q, max_seqlen_in_batch_q = unpad_input(query_layer, attention_mask)
ValueError: too many values to unpack (expected 4)
```
### Expected behavior
Script runs smoothly | bug | low | Critical |
2,812,138,878 | PowerToys | 设置映射之后输入较快的情况下映射会失败 | ### Microsoft PowerToys version
0.87.1
### Installation method
GitHub
### Running as admin
Yes
### Area(s) with issue?
Keyboard Manager
### Steps to reproduce
设置映射之后输入较快的情况下映射会失败
the mapping will fail when i input is relatively fast
alt(left) key is pressed,then i trigger u/i/o if i input slowly it will output 7/8/9,
but when i input swiftly, it maybe output 7/i/9 or 7/8/o
this is my mapping set
\
### ✔️ Expected Behavior
no matter how fast, i hope it will output my mapping set key
### ❌ Actual Behavior
alt(left) key is pressed,then i trigger u/i/o if i input slowly it will output 7/8/9,
but when i input swiftly, it maybe output 7/i/9 or 7/8/o
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Major |
2,812,165,180 | TypeScript | TypeScript inappropriately resolves directory imports in ESM mode, that fail at runtime (in Node, but probably all ESM environments). | ### 🔎 Search Terms
ESM "directory import" "directory imports"
### 🕗 Version & Regression Information
Behaves this way for all versions tested on TSPlayground using module: ES*
Behaves this way in a local project with TS 4 and 5, and module: Node16 (moduleResolution: Node16)
I reviewed the FAQ for entries about directory imports and ESM
### ⏯ Playground Link
[Playground](https://www.typescriptlang.org/play/?target=99&moduleResolution=99&module=7&ts=5.7.3&jsx=0#code/PTAEFsHsBMFcBsCmAuUBRAygJgAxawFAECW4ADpAE4AuoA5MQLQAWAhgG6KOuPTGXcAdtEbhWxQXVAhQAeQDSAOlAAlRAGdI8TutDVIe5olAAiMRJOhEADwo0ANKD7rqwCdBuKAVupLkqtAwsHFw8fAKswqLigsDOruFSMgBi4vC6rLSUsILUpIiKBKDFJaVl5RWVpTIAKhiglBpaOobEuvrS8XH8bsKePvZFVcMjVTKZDTl54MbUzG2gC5GLguys8MTQTvyIAMb6lACei-40BEA)
A repro repository is here: https://github.com/RobertSandiford/ts-esm-dir-import-example
After cloning run `pnpm i && pnpm run dev`
I recommend this over the playground link because you can see the runtime errors.
### 💻 Code
the package `'i-have-a-dir-and-main'` has this file structure:
dist
--index.js
--dir
----index.js
package.json includes:
"type": "module"
"main": "dist/index.js"
An importing project may look like this. This compiles but fails at runtime:
```ts
import 'i-have-a-dir-and-main' // OK. Resolves to the "main" export, dist/index.js
import 'i-have-a-dir-and-main/dist/dir' // Fails at runtime.
// TS resolves this to /dist/dir/index.js,
// at runtime this is an invalid directory import
```
### 🙁 Actual behavior
TS resolves the import `'i-have-a-dir-and-main/dist/dir'` to `i-have-a-dir-and-main/dist/dir/index.js`, but this is not valid in ESM. Directory imports are not permitted (outside of exceptions like a node legacy behaviour flag)
```
Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import 'C:\xxx\ts-dir-import-repro\node_modules\i-have-a-dir-and-main\dist\dir' is not supported resolving ES modules imported from C:\xxx\ts-dir-import-repro\dist\index.js
Did you mean to import "i-have-a-dir-and-main/dist/dir/index.js"?
at finalizeResolution (node:internal/modules/esm/resolve:259:11)
at moduleResolve (node:internal/modules/esm/resolve:933:10)
```
### 🙂 Expected behavior
TSC to fail to resolve the import `'i-have-a-dir-and-main/dist/dir'` when in an ESM mode (import resolution: Node*, type module, or import resolution: ES*) and report an import error. | Needs Investigation | low | Critical |
2,812,178,792 | vscode | I cant paste anything |
Type: <b>Bug</b>
i can copy or cut but i cant paste anyting
VS Code version: Code - OSS 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-17T08:53:36.849Z)
OS version: Linux x64 6.12.10-zen1-1-zen
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2400)|
|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: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off<br>webnn: disabled_off|
|Load (avg)|1, 1, 1|
|Memory (System)|15.49GB (10.96GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|garuda-hyprland|
|XDG_CURRENT_DESKTOP|Hyprland|
|XDG_SESSION_DESKTOP|hyprland|
|XDG_SESSION_TYPE|wayland|
</details><details><summary>Extensions (3)</summary>
Extension|Author (truncated)|Version
---|---|---
tailwind-documentation|alf|0.1.15
vscode-tailwindcss|bra|0.10.2
five-server|yan|0.3.2
</details>
<!-- generated by issue reporter --> | info-needed | low | Critical |
2,812,188,723 | godot | GradientTexture1D/2D changed signal emitted before texture updating which causes issue in certain case | ### Tested versions
Reproducible in 4.4.dev
### System information
Linux - Godot 4.4.dev
### Issue description
GradientTexture2D/1D emit changed signal before its texture actually updates, which causes issues in certain case that can't update texture by listen its changed signal. The issue was found in #102028.
### Steps to reproduce
The issue occurs if you draw gradient texture in a viewport and only update once.
Attach the follow script to a Node2D, assign a GradientTexture2D/GradientTexture1D to the texture property, then the texture display incorrectly and doesn't update after changing its gradient, unless reload the scene. Instead, assigning a NoiseTexture2D to the texture works well.
```gdscript
@tool
extends Node2D
class_name TestNode2D
@export var texture: Texture2D:
set(value):
if texture != null:
texture.changed.disconnect(queue_redraw)
texture = value
if texture != null:
texture.changed.connect(queue_redraw)
queue_redraw()
@export var bg_color: Color = Color.WHITE:
set(value):
bg_color = value
queue_redraw()
var size: Vector2i = Vector2i(512, 512)
var vp: RID = RenderingServer.viewport_create()
var vp_canvas: RID = RenderingServer.canvas_create()
var vp_ci: RID = RenderingServer.canvas_item_create()
var update_pending: bool = false
var vp_texture: RID
func _init() -> void:
RenderingServer.viewport_attach_canvas(vp, vp_canvas)
RenderingServer.canvas_item_set_parent(vp_ci, vp_canvas)
RenderingServer.viewport_set_update_mode(vp, RenderingServer.VIEWPORT_UPDATE_ALWAYS)
RenderingServer.viewport_set_size(vp, size.x, size.y)
vp_texture = RenderingServer.viewport_get_texture(vp)
func _draw() -> void:
RenderingServer.canvas_item_clear(vp_ci)
RenderingServer.canvas_item_add_rect(vp_ci, Rect2(Vector2.ZERO, size), bg_color)
if texture != null:
RenderingServer.canvas_item_add_texture_rect(vp_ci, Rect2(Vector2.ZERO, size), texture.get_rid())
RenderingServer.viewport_set_active(vp, true)
RenderingServer.force_draw(false)
RenderingServer.viewport_set_active(vp, false)
RenderingServer.canvas_item_add_texture_rect(get_canvas_item(), Rect2(Vector2.ZERO, size), vp_texture)
```
### Minimal reproduction project (MRP)
N/A | bug,topic:core | low | Minor |
2,812,194,085 | PowerToys | crash bug when attempting to Restart PowerToys as administrator | ### Microsoft PowerToys version
0.87.1
### Installation method
PowerToys auto-update
### Running as admin
No
### Area(s) with issue?
Settings, General
### Steps to reproduce
1. Use Windows Search to find and start PowerToys
2. Click "open settings" under the Welcome message.
3. In the new window that opens, click the upper left hamburger icon and select "General"
4. Scroll down to "Administrator mode" and click the "Restart PowerToys as administrator"
5. Observe that PowerToys crashes almost immediately after clicking.
### ✔️ Expected Behavior
Expectation was for PowerToys to cue my admin login screen, as it typical does when I restart it as admin. After I enter my login info, PowerToys is normally running in admin mode.
### ❌ Actual Behavior
When I hit "Restart PowerToys as administrator" the cursor becomes a windows-wait/blue circle of death briefly before PowerToys completely and abruptly crashes and disappears. I verified in task manager that PowerToys is no longer running after this. I've repeatedly tried to restart PowerToys as admin without success.
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Critical |
2,812,211,867 | neovim | b:undo_ftplugin unmapping fails when filetype is changed from help set via modeline | ### Problem
If a file has a modeline `vim:ft=help`, changing filetype raises E31 errors:
```
Error detected while processing FileType Autocommands for "*"..function <SNR>1_LoadFTPlugin[2]..modelines[1]..FileType Autocommands for "*"..function <SNR>1_LoadFTPlugin:
line 2:
E31: No such mapping
E31: No such mapping
```
which must come from https://github.com/neovim/neovim/blob/c7d4a77ff9040c8b242f9d12a98472fe6217328c/runtime/ftplugin/help.lua#L85
This does not occur when ft is set to help but not by modeline.
### Steps to reproduce
```
echo 'vim:ft=help' | nvim --clean -
:set ft=
```
### Expected behavior
E31 is not issued.
### Nvim version (nvim -v)
v0.11.0-dev-c7d4a77ff904
### Vim (not Nvim) behaves the same?
no, vim 9.1.1043
### Operating system/version
EndeavourOS
### Terminal name/version
GNOME Terminal 3.54.3 using VTE 0.78.3 +BIDI +GNUTLS +ICU +SYSTEMD
### $TERM environment variable
xterm-256color
### Installation
build from repo | runtime,complexity:low,filetype | low | Critical |
2,812,215,888 | electron | [Bug] `context-menu` event not working on top part of window on macOS | ### 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
32.2.8
### What operating system(s) are you using?
macOS
### Operating System Version
Tested on macOS Sequoia 15.0 & macOS Sonoma 14.6.1
### What arch are you using?
arm64 (including Apple Silicon)
### Last Known Working Electron version
32.2.6
### Expected Behavior
When right clicking the `context-menu` event should work on all parts of the application window, as it does in version 32.2.6 and prior! (Have not tested version 32.2.7)
### Actual Behavior
The `context-menu` event only triggers in about the bottom 20-30% of the application, and never in the top half of the application. Resizing the window to the bottom of the screen will make the event trigger as expected always.
So right clicking the exact same place inside my application leaves different results: if the part of the application window I try to right click is positioned at the top part of the screen it never works, but moving/resizing the window towards the bottom of the screen and right clicking the exact same place properly triggers the event! This leaves me to believe that this must be an Electron issue, and not an issue on my side, also that it started to happen right after I updated Electron.
### Testcase Gist URL
_No response_
### Additional Information
This commit might be related, but not sure: https://github.com/electron/electron/commit/3007f859dad930ae80bafffc6042a146a45e4e4d | platform/macOS,component/menu,bug :beetle:,32-x-y | low | Critical |
2,812,223,635 | tauri | [bug] : infinite run macos release build for async main | ### Describe the bug
```
48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
[2025-01-27][14:53:48][INFO][tauri::manager] app::emit; event=EventName("log://log")
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> app::emit;
[2025-01-27][14:53:48][DEBUG][tracing::span] emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> emit::run;
[2025-01-27][14:53:48][DEBUG][tracing::span] window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] -> window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span] -- window::emit::serialize;
[2025-01-27][14:53:48][TRACE][tracing::span::active] <- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- emit::run;
[2025-01-27][14:53:48][TRACE][tracing::span] -- app::emit;
^C[2025-01-27][14:53:48][TRACE][tracing::span::active] <- app::emit;
```
### Reproduction
Rel #12513
```
#[cfg_attr(mobile, tauri::mobile_entry_point)]
pub async fn run() {
```
```
#[tokio::main]
async fn main() {
app_lib::run().await;
}
```
### Expected behavior
_No response_
### Full `tauri info` output
```text
Using patch:
tauri = { git = "https://github.com/tauri-apps/tauri", branch = "fix/async-panic" }
```
### Stack trace
```text
```
### Additional context
_No response_ | type: bug,status: needs triage | low | Critical |
2,812,232,921 | transformers | AttributeError: 'dict' object has no attribute '_attn_implementation_internal' | ### System Info
```
ForCausalLM.from_pretrained(model_path, attn_implementation='flash_attention_2')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/miniconda3/lib/python3.12/site-packages/transformers/modeling_utils.py", line 4084, in from_pretrained
config = cls._autoset_attn_implementation(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/miniconda3/lib/python3.12/site-packages/transformers/modeling_utils.py", line 1516, in _autoset_attn_implementation
sub_config._attn_implementation_internal = curr_attn_implementation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'dict' object has no attribute '_attn_implementation_internal'
```
Loading from a saved_pretrained model got error.
### Who can help?
_No response_
### Information
- [x] The official example scripts
- [x] My own modified scripts
### Tasks
- [x] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [x] My own task or dataset (give details below)
### Reproduction
ef
### Expected behavior
ef | bug | low | Critical |
2,812,269,390 | ollama | Deepseek-R1 671B - Segmentation Fault Bug | ### What is the issue?
Hi,
I've been using the Deepseek-R1 671B model from Ollama on my 8x H100 machine and keep running into a segmentation fault, I've noticed that the frequency of the segfault happens the larger the context becomes.
I'm using the latest Ollama release.
Hardware Specs:
- 8x H100 - 80GB SXM
- Xeon Platinum 8468 (160c)
- Micron 7450 ssd
- 1548gb of ram
- OS is ubuntu 22.04
- CUDA: 12.6
- NVIDIA driver: 560.35.05
Happy to test params or gather more data, I'm having a hard time working around this. The distilled models like the deepseek llama 70B work just fine.
[server.err.log](https://github.com/user-attachments/files/18554764/server.err.log)
Any advice is appreciated.
### OS
Linux
### GPU
Nvidia
### CPU
Intel
### Ollama version
0.5.7 | bug | low | Critical |
2,812,271,848 | material-ui | ClassName generator not working with Next.js App router | ### Steps to reproduce
Steps:
1. Open this link to live example: [click here](https://codesandbox.io/p/live/e997598e-b472-4343-addd-c9e77da9a9af)
2. npm run dev
3. Open the devtools and inspect the element tree
### Current behavior
All the class names stay unchanged:
### Expected behavior
All class names should be transformed by the ClassNameGenerator.
### Context
I also tried to import the 'init-cls.ts' as a client script, but that only affects the client side, and the server side is just doing nothing.
I'm following this doc: https://mui.com/material-ui/experimental-api/classname-generator/
### Your environment
System:
OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
Binaries:
Node: 20.9.0 - /usr/local/bin/node
npm: 9.8.1 - /usr/local/bin/npm
pnpm: 8.10.2 - /usr/local/share/npm-global/bin/pnpm
Browsers:
Chrome: Not Found
npmPackages:
@emotion/react: latest => 11.11.1
@emotion/styled: latest => 11.11.0
@mui/core-downloads-tracker: 6.0.0
@mui/icons-material: latest => 6.0.0
@mui/material: latest => 6.0.0
@mui/material-nextjs: latest => 6.0.0
@mui/private-theming: 6.0.0
@mui/styled-engine: 6.0.0
@mui/system: 6.0.0
@mui/types: 7.2.16
@mui/utils: 6.0.0
@types/react: ^19.0.0 => 19.0.2
react: ^19.0.0 => 19.0.0
react-dom: ^19.0.0 => 19.0.0
typescript: latest => 5.1.6
**Search keywords**: next, nextjs, app, classname, styles, experimental, css, class | package: system,status: waiting for maintainer,nextjs | low | Minor |
2,812,351,061 | puppeteer | [Feature]: Support navigation history for the current page | ### Feature description
Description:
I would like to get the navigation history for the current page.
Proposed Solution:
CDP supports the ability to navigation history for the current page [Page.getNavigationHistory](https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-getNavigationHistory) It will be nice to have this feature exposed in Puppeteer.
| feature | low | Minor |
2,812,378,962 | yt-dlp | [FranceTVSite] Unable to extract video ID / francetv france.tv | ### 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)
- [ ] 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
France
### Provide a description that is worded well enough to be understood
Today, trying to use yt-dlp on France TV URLs doesn't work:
```
$ ~/yt-dlp/yt-dlp --restrict-filenames https://www.france.tv/france-3/l-epopee-des-vignerons/3843847-emission-du-mercredi-7-septembre-2022.html
[FranceTVSite] Extracting URL: https://www.france.tv/france-3/l-epopee-des-vignerons/3843847-emission-du-mercredi-7-septembre-2022.html
[FranceTVSite] 3843847-emission-du-mercredi-7-septembre-2022: Downloading webpage
ERROR: [FranceTVSite] 3843847-emission-du-mercredi-7-septembre-2022: Unable to extract video ID; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
$ ~/yt-dlp/yt-dlp --restrict-filenames https://www.france.tv/documentaires/documentaires-art-et-culture/6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier.html
[FranceTVSite] Extracting URL: https://www.france.tv/documentaires/documentaires-art-et-culture/6837847-une-journee-extra-ordina...l-opera-garnier.html
[FranceTVSite] 6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier: Downloading webpage
ERROR: [FranceTVSite] 6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier: Unable to extract video ID; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
```
### 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', '--restrict-filenames', 'https://www.france.tv/documentaires/documentaires-art-et-culture/6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier.html']
[debug] Encodings: locale ISO-8859-1, fs iso8859-1, pref ISO-8859-1, out iso8859-1, error iso8859-1, screen iso8859-1
[debug] yt-dlp version [email protected] from yt-dlp/yt-dlp [3b4531934] (zip)
[debug] Lazy loading extractors is disabled
[debug] Python 3.12.8 (CPython x86_64 64bit) - Linux-6.12.11-amd64-x86_64-with-glibc2.40 (OpenSSL 3.4.0 22 Oct 2024, glibc 2.40)
[debug] exe versions: ffmpeg 7.1 (fdk,setts), ffprobe 7.1
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.12.14, mutagen-1.47.0, requests-2.32.3, secretstorage-3.3.3, sqlite3-3.46.1, urllib3-2.3.0, websockets-14.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1839 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)
[FranceTVSite] Extracting URL: https://www.france.tv/documentaires/documentaires-art-et-culture/6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier.html
[FranceTVSite] 6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier: Downloading webpage
ERROR: [FranceTVSite] 6837847-une-journee-extra-ordinaire-24h-a-l-opera-garnier: Unable to extract video ID; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
File "/home/dw/yt-dlp/yt-dlp/yt_dlp/extractor/common.py", line 742, in extract
ie_result = self._real_extract(url)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/dw/yt-dlp/yt-dlp/yt_dlp/extractor/francetv.py", line 349, in _real_extract
video_id = self._html_search_regex(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/dw/yt-dlp/yt-dlp/yt_dlp/extractor/common.py", line 1382, in _html_search_regex
res = self._search_regex(pattern, string, name, default, fatal, flags, group)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/dw/yt-dlp/yt-dlp/yt_dlp/extractor/common.py", line 1346, in _search_regex
raise RegexNotFoundError(f'Unable to extract {_name}')
``` | geo-blocked,site-bug,patch-available | low | Critical |
2,812,402,277 | excalidraw | Bug: Add Link feature changed my redicrect to link | My original link: `https://www.u-nas.com/xcart/cart.php?target=product&product_id=17640`
Excalidraw saves: `https://www.u-nas.com/xcart/cart.php?target=product&amp;product_id=17640`
#### Reproduce step
1. Create a random block
2. ADD link
3. Paste the above original link and add
4. Redirected link has included `amp;` and is incorrect | bug,Hyperlinks | low | Critical |
2,812,405,135 | godot | Menu options are not detected correctly. | ### Tested versions
v4.4.beta1.official [d33da79d3]
### System information
w10 64
### Issue description
When moving the cursor over menu options that have additional sub-options appearing automatically in a small menu to the right, the main menu options are not properly detected as the cursor moves over them.
As shown in the video, the cursor is positioned over an option, but an additional movement is required for the menu to detect the cursor's position and highlight the intended option.
https://github.com/user-attachments/assets/b92fe306-5aec-4280-bf7a-f61a56f12f64
### Steps to reproduce
See the video
### Minimal reproduction project (MRP)
... | bug,topic:editor,topic:gui | low | Minor |
2,812,469,011 | tauri | [bug] App::cleanup_before_exit() can crash if not run on main thread | ### Describe the bug
If an app has some resources that need to be cleaned up and the OS requires them to be cleaned up on main thread then calling `cleanup_before_exit()` from a worker thread may cause a crash.
I observed this crash reliably with a tray icon app on MacOS, see crash backtrace below.
### Reproduction
I don't have a minimal repro but you can look at my [fix](https://github.com/openscopeproject/TrguiNG/commit/79beca8ee08eb4b9b0f9eda060d3373f0f9fbf5b) for this issue for my app and if you compile the parent commit the issue will reproduce.
### Expected behavior
Any cleanup that should happen on main thread should be handled on main thread inside the `cleanup_before_exit()` method
### Full `tauri info` output
```text
[✔] Environment
- OS: Mac OS 12.6.5 x86_64 (X64)
✔ Xcode Command Line Tools: installed
✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-x86_64-apple-darwin (default)
- node: 18.16.1
- yarn: 1.22.19
- npm: 9.5.1
[-] Packages
- tauri 🦀: 2.2.5
- tauri-build 🦀: 2.0.5
- wry 🦀: 0.48.1
- tao 🦀: 0.31.1
- @tauri-apps/api : 2.2.0
- @tauri-apps/cli : 2.2.7
[-] Plugins
- tauri-plugin-cli 🦀: 2.2.0
- @tauri-apps/plugin-cli : 2.2.0
- tauri-plugin-fs 🦀: 2.2.0
- @tauri-apps/plugin-fs : 2.2.0
- tauri-plugin-notification 🦀: 2.2.1
- @tauri-apps/plugin-notification : 2.2.1
- tauri-plugin-dialog 🦀: 2.2.0
- @tauri-apps/plugin-dialog : 2.2.0
- tauri-plugin-clipboard-manager 🦀: 2.2.0
- @tauri-apps/plugin-clipboard-manager : 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:8080/
- framework: React
- bundler: Webpack
```
### Stack trace
```text
Stack:(
0 CoreAutoLayout 0x00007ff810af0939 _AssertAutoLayoutOnAllowedThreadsOnly + 202
1 CoreAutoLayout 0x00007ff810af0cb8 -[NSISEngine withBehaviors:performModifications:] + 25
2 AppKit 0x00007ff80b94b7eb -[NSView(NSConstraintBasedLayout) _withAutomaticEngineOptimizationDisabled:] + 59
3 AppKit 0x00007ff80b9547a0 -[NSView _setSuperview:] + 427
4 AppKit 0x00007ff80b97a6fd -[NSView removeFromSuperview] + 140
5 trguing 0x000000010c3a8790 _ZN59_$LT$$LP$$RP$$u20$as$u20$objc2..encode..EncodeArguments$GT$8__invoke17hb7a6c4bf884c5499E + 48
6 trguing 0x000000010c3a4930 _ZN5objc27runtime16message_receiver18msg_send_primitive4send17hdc096b39f28b4a85E + 48
7 trguing 0x000000010c3ac19a _ZN5objc27runtime16message_receiver15MessageReceiver12send_message28_$u7b$$u7b$closure$u7d$$u7d$17hf963d757138bbd8dE + 42
8 trguing 0x000000010c3a2165 _ZN115_$LT$core..panic..unwind_safe..AssertUnwindSafe$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$$LP$$RP$$GT$$GT$9call_once17hf510c43f9825693eE + 21
9 trguing 0x000000010c388abc _ZN5objc29exception5catch28_$u7b$$u7b$closure$u7d$$u7d$17h6001a24d09e7b206E + 28
10 trguing 0x000000010c3851d1 _ZN5objc29exception10try_no_ret24try_objc_execute_closure17hf89e6beb1fa1b5eaE + 97
11 trguing 0x000000010c3d043e rust_objc_sys_0_3_try_catch_exception + 30
12 trguing 0x000000010c37f9aa _ZN5objc29exception10try_no_ret17h3755cd8e77b9aeb3E + 202
13 trguing 0x000000010c3874fc _ZN5objc29exception5catch17hd88fd32da641a5e9E + 60
14 trguing 0x000000010c3921e6 _ZN5objc27runtime16message_receiver15MessageReceiver12send_message17h891939fda8d344f0E + 198
15 trguing 0x000000010c36e98a _ZN5objc215__macro_helpers8msg_send7MsgSend12send_message17haf987ba6b13894b2E + 154
16 trguing 0x000000010c36f51b _ZN13objc2_app_kit9generated8__NSView6NSView19removeFromSuperview17h176a96d531be7d45E + 59
17 trguing 0x000000010c2018b9 _ZN9tray_icon13platform_impl8platform8TrayIcon6remove17h8de954157eb3f2cbE + 265
18 trguing 0x000000010c2029b1 _ZN86_$LT$tray_icon..platform_impl..platform..TrayIcon$u20$as$u20$core..ops..drop..Drop$GT$4drop17h2ed453f407fca991E + 17
19 trguing 0x000000010c20ce35 _ZN4core3ptr65drop_in_place$LT$tray_icon..platform_impl..platform..TrayIcon$GT$17h3964376b9c17c46eE + 21
20 trguing 0x000000010c20d401 _ZN4core3ptr95drop_in_place$LT$core..cell..UnsafeCell$LT$tray_icon..platform_impl..platform..TrayIcon$GT$$GT$17h0097c275dbf2f21aE + 17
21 trguing 0x000000010c20d305 _ZN4core3ptr92drop_in_place$LT$core..cell..RefCell$LT$tray_icon..platform_impl..platform..TrayIcon$GT$$GT$17h7deeef8a3e7ccc49E + 21
22 trguing 0x000000010c050453 _ZN68_$LT$alloc..rc..Rc$LT$T$C$A$GT$$u20$as$u20$core..ops..drop..Drop$GT$4drop17h4743926d18d28cb2E + 211
23 trguing 0x000000010c036fd1 _ZN4core3ptr113drop_in_place$LT$alloc..rc..Rc$LT$core..cell..RefCell$LT$tray_icon..platform_impl..platform..TrayIcon$GT$$GT$$GT$17h6c4380a792eb9331E + 17
24 trguing 0x000000010c03e651 _ZN4core3ptr40drop_in_place$LT$tray_icon..TrayIcon$GT$17heec8ccdf7c3f286bE + 65
25 trguing 0x000000010c03e8ce _ZN4core3ptr42drop_in_place$LT$tauri..tray..TrayIcon$GT$17hd3f1732453dbbf5dE + 78
26 trguing 0x000000010c03f779 _ZN4core3ptr52drop_in_place$LT$$u5b$tauri..tray..TrayIcon$u5d$$GT$17h8e99aae541cdc0a1E + 73
27 trguing 0x000000010b0e0c68 _ZN5alloc3vec16Vec$LT$T$C$A$GT$5clear17h0fa9eea50f73cab6E + 104
28 trguing 0x000000010a9fd1e2 _ZN5tauri3app18AppHandle$LT$R$GT$19cleanup_before_exit17h50af6d8232cabda3E + 274
29 trguing 0x000000010aaa8a93 _ZN7trguing5setup28_$u7b$$u7b$closure$u7d$$u7d$28_$u7b$$u7b$closure$u7d$$u7d$17he70420d5c4f79ff7E + 83
30 trguing 0x000000010c05c9ac _ZN86_$LT$alloc..boxed..Box$LT$F$C$A$GT$$u20$as$u20$core..ops..function..Fn$LT$Args$GT$$GT$4call17h76d182de2ec98565E + 60
31 trguing 0x000000010c03244b _ZN5tauri5event8listener9Listeners11emit_filter17hd4abbe1e1fc223f7E + 875
32 trguing 0x000000010c032668 _ZN5tauri5event8listener9Listeners4emit17h893afe9e4fb3b155E + 40
33 trguing 0x000000010b812f3b _ZN5tauri7manager19AppManager$LT$R$GT$4emit17h279bc9e7619f313cE + 923
34 trguing 0x000000010aa00936 _ZN5tauri7Emitter4emit17hf913b73e54776162E + 374
35 trguing 0x000000010b707711 _ZN5tauri5event6plugin4emit28_$u7b$$u7b$closure$u7d$$u7d$17hee67980034de4fa3E + 385
36 trguing 0x000000010b7073fc _ZN53_$LT$F$u20$as$u20$futures_core..future..TryFuture$GT$8try_poll17hb989c87d179643cbE + 28
37 trguing 0x000000010b35c3ac _ZN117_$LT$futures_util..future..try_future..into_future..IntoFuture$LT$Fut$GT$$u20$as$u20$core..future..future..Future$GT$4poll17h270432a3f7d0ef32E + 60
38 trguing 0x000000010b798a6a _ZN102_$LT$futures_util..future..future..map..Map$LT$Fut$C$F$GT$$u20$as$u20$core..future..future..Future$GT$4poll17hf95a0dafefd0da89E + 154
39 trguing 0x000000010b6950fc _ZN97_$LT$futures_util..future..future..Map$LT$Fut$C$F$GT$$u20$as$u20$core..future..future..Future$GT$4poll17hbc52fd8862f22ddbE + 60
40 trguing 0x000000010abee11c _ZN104_$LT$futures_util..future..try_future..MapErr$LT$Fut$C$F$GT$$u20$as$u20$core..future..future..Future$GT$4poll17h68c6988be6b94473E + 60
41 trguing 0x000000010abf1d9c _ZN105_$LT$futures_util..future..try_future..ErrInto$LT$Fut$C$E$GT$$u20$as$u20$core..future..future..Future$GT$4poll17hd7e73990ba7abdbcE + 60
42 trguing 0x000000010b77434a _ZN102_$LT$futures_util..future..future..map..Map$LT$Fut$C$F$GT$$u20$as$u20$core..future..future..Future$GT$4poll17h370b86799ba3dbf3E + 154
43 trguing 0x000000010b6966dc _ZN97_$LT$futures_util..future..future..Map$LT$Fut$C$F$GT$$u20$as$u20$core..future..future..Future$GT$4poll17hfb0b631433a2b2e7E + 60
44 trguing 0x000000010b7094fa _ZN5tauri5event6plugin4init28_$u7b$$u7b$closure$u7d$$u7d$28_$u7b$$u7b$closure$u7d$$u7d$17h95e530e6d2e47d85E + 2250
45 trguing 0x000000010b0a1e88 _ZN5tauri3ipc23InvokeResolver$LT$R$GT$24respond_async_serialized28_$u7b$$u7b$closure$u7d$$u7d$17h748908d6d392be44E + 440
46 trguing 0x000000010b22bebd _ZN72_$LT$core..pin..Pin$LT$P$GT$$u20$as$u20$core..future..future..Future$GT$4poll17h8b9c41a90f5d48ccE + 45
47 trguing 0x000000010b488d95 _ZN5tokio7runtime4task4core17Core$LT$T$C$S$GT$4poll28_$u7b$$u7b$closure$u7d$$u7d$17h479b44755168375eE + 101
48 trguing 0x000000010b4620f8 _ZN5tokio7runtime4task4core17Core$LT$T$C$S$GT$4poll17h12d1f0ffdb97e551E + 56
49 trguing 0x000000010acf1927 _ZN5tokio7runtime4task7harness11poll_future28_$u7b$$u7b$closure$u7d$$u7d$17h8e87e26b3af877adE + 71
50 trguing 0x000000010aa6ce72 _ZN115_$LT$core..panic..unwind_safe..AssertUnwindSafe$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$$LP$$RP$$GT$$GT$9call_once17h25631f19413a1046E + 34
51 trguing 0x000000010b85a446 _ZN3std9panicking3try7do_call17h977e37b7e86a4b95E + 54
52 trguing 0x000000010b2fbe7d __rust_try + 29
53 trguing 0x000000010b2a5662 _ZN3std5panic12catch_unwind17h54d4d0d6388cad96E + 82
54 trguing 0x000000010aca6f63 _ZN5tokio7runtime4task7harness11poll_future17h6ff009252dd4782bE + 115
55 trguing 0x000000010ad30a36 _ZN5tokio7runtime4task7harness20Harness$LT$T$C$S$GT$10poll_inner17hdb57e410d500cde9E + 134
56 trguing 0x000000010adae255 _ZN5tokio7runtime4task7harness20Harness$LT$T$C$S$GT$4poll17he993eac640135ce2E + 21
57 trguing 0x000000010b5bf29d _ZN5tokio7runtime4task3raw4poll17h9b1724ff8c73c760E + 29
58 trguing 0x000000010c31f6f6 _ZN5tokio7runtime4task3raw7RawTask4poll17hc4cbd9c33b85ce7fE + 38
59 trguing 0x000000010c316dd2 _ZN5tokio7runtime4task22LocalNotified$LT$S$GT$3run17h527060227f42cb1aE + 34
60 trguing 0x000000010c30d1e9 _ZN5tokio7runtime9scheduler12multi_thread6worker7Context8run_task28_$u7b$$u7b$closure$u7d$$u7d$17h68e0216e3454e97aE + 57
61 trguing 0x000000010c30d0ab _ZN5tokio7runtime9scheduler12multi_thread6worker7Context8run_task17he2e4fc4cefeefc18E + 827
62 trguing 0x000000010c30c949 _ZN5tokio7runtime9scheduler12multi_thread6worker7Context3run17h51b91dfaaf93a40fE + 585
63 trguing 0x000000010c30c660 _ZN5tokio7runtime9scheduler12multi_thread6worker3run28_$u7b$$u7b$closure$u7d$$u7d$28_$u7b$$u7b$closure$u7d$$u7d$17h66c6aaeb1f03b2bcE + 96
64 trguing 0x000000010c32a175 _ZN5tokio7runtime7context6scoped15Scoped$LT$T$GT$3set17hf02214323105a8bdE + 133
65 trguing 0x000000010c2f62bb _ZN5tokio7runtime7context13set_scheduler28_$u7b$$u7b$closure$u7d$$u7d$17h6c0fab7fa03d6bb4E + 43
66 trguing 0x000000010c339776 _ZN3std6thread5local17LocalKey$LT$T$GT$8try_with17he680abde8c5f2b17E + 214
67 trguing 0x000000010c338101 _ZN3std6thread5local17LocalKey$LT$T$GT$4with17h92815f48b3b9200cE + 17
68 trguing 0x000000010c2f6230 _ZN5tokio7runtime7context13set_scheduler17h91834690cea337f9E + 48
69 trguing 0x000000010c30c593 _ZN5tokio7runtime9scheduler12multi_thread6worker3run28_$u7b$$u7b$closure$u7d$$u7d$17h2c0c2de76fcae1e7E + 355
70 trguing 0x000000010c3018dc _ZN5tokio7runtime7context7runtime13enter_runtime17hecb05cda0e891aa3E + 220
71 trguing 0x000000010c30c381 _ZN5tokio7runtime9scheduler12multi_thread6worker3run17h473ebf6192cf7077E + 561
72 trguing 0x000000010c30c141 _ZN5tokio7runtime9scheduler12multi_thread6worker6Launch6launch28_$u7b$$u7b$closure$u7d$$u7d$17h240a92828f8f2eebE + 17
73 trguing 0x000000010c310d06 _ZN102_$LT$tokio..runtime..blocking..task..BlockingTask$LT$T$GT$$u20$as$u20$core..future..future..Future$GT$4poll17h50b3c0da6b35e124E + 118
74 trguing 0x000000010c3355f5 _ZN5tokio7runtime4task4core17Core$LT$T$C$S$GT$4poll28_$u7b$$u7b$closure$u7d$$u7d$17h9ebd142f9a68f1bcE + 101
75 trguing 0x000000010c335448 _ZN5tokio7runtime4task4core17Core$LT$T$C$S$GT$4poll17h028d064f1fe32cecE + 56
76 trguing 0x000000010c3240a7 _ZN5tokio7runtime4task7harness11poll_future28_$u7b$$u7b$closure$u7d$$u7d$17h2cb6ea2397ecf6adE + 71
77 trguing 0x000000010c309002 _ZN115_$LT$core..panic..unwind_safe..AssertUnwindSafe$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$$LP$$RP$$GT$$GT$9call_once17h15f1ba179fe00350E + 34
78 trguing 0x000000010c309456 _ZN3std9panicking3try7do_call17h622591ede7e60a9fE + 54
79 trguing 0x000000010c2f6acd __rust_try + 29
80 trguing 0x000000010c2f42a2 _ZN3std5panic12catch_unwind17h83ed0f2beec2733fE + 82
81 trguing 0x000000010c323c73 _ZN5tokio7runtime4task7harness11poll_future17h43f235a405c3a5ceE + 115
82 trguing 0x000000010c322b26 _ZN5tokio7runtime4task7harness20Harness$LT$T$C$S$GT$10poll_inner17h8cf936f8e139f599E + 134
83 trguing 0x000000010c322875 _ZN5tokio7runtime4task7harness20Harness$LT$T$C$S$GT$4poll17h665caef9dcba709aE + 21
84 trguing 0x000000010c31f97d _ZN5tokio7runtime4task3raw4poll17h5b198bbea979f154E + 29
85 trguing 0x000000010c31f6f6 _ZN5tokio7runtime4task3raw7RawTask4poll17hc4cbd9c33b85ce7fE + 38
86 trguing 0x000000010c316e7e _ZN5tokio7runtime4task20UnownedTask$LT$S$GT$3run17h2e1a2de2296f5c4fE + 46
87 trguing 0x000000010c2e9799 _ZN5tokio7runtime8blocking4pool4Task3run17h7522f86b1aa8256cE + 25
88 trguing 0x000000010c2eb8a0 _ZN5tokio7runtime8blocking4pool5Inner3run17hd4f1ce091573ea00E + 496
89 trguing 0x000000010c2eb626 _ZN5tokio7runtime8blocking4pool7Spawner12spawn_thread28_$u7b$$u7b$closure$u7d$$u7d$17hb28d0044f4837a81E + 134
90 trguing 0x000000010c2f3f6d _ZN3std3sys9backtrace28__rust_begin_short_backtrace17h352dd52abadcc8f7E + 13
91 trguing 0x000000010c32d160 _ZN3std6thread7Builder16spawn_unchecked_28_$u7b$$u7b$closure$u7d$$u7d$28_$u7b$$u7b$closure$u7d$$u7d$17h8641cc4f11ea9683E + 48
92 trguing 0x000000010c3090c0 _ZN115_$LT$core..panic..unwind_safe..AssertUnwindSafe$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$$LP$$RP$$GT$$GT$9call_once17h8a64eb289fe9f6d8E + 48
93 trguing 0x000000010c3096e0 _ZN3std9panicking3try7do_call17hf9cdee01075319c9E + 64
94 trguing 0x000000010c330d0d __rust_try + 29
95 trguing 0x000000010c32cdb3 _ZN3std6thread7Builder16spawn_unchecked_28_$u7b$$u7b$closure$u7d$$u7d$17h6df6f05e1f6d265eE + 755
96 trguing 0x000000010c2d7d11 _ZN4core3ops8function6FnOnce40call_once$u7b$$u7b$vtable.shim$u7d$$u7d$17h3d1aaa82df38aa73E + 17
97 trguing 0x000000010c85d6bb _ZN3std3sys3pal4unix6thread6Thread3new12thread_start17hcd19cc58b6db093aE + 43
98 libsystem_pthread.dylib 0x00007ff808efb4e1 _pthread_start + 125
99 libsystem_pthread.dylib 0x00007ff808ef6f6b thread_start + 15
)
thread 'tokio-runtime-worker' panicked at library/core/src/panicking.rs:221:5:
panic in a function that cannot unwind
stack backtrace:
0: rust_begin_unwind
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:665:5
1: core::panicking::panic_nounwind_fmt::runtime
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panicking.rs:112:18
2: core::panicking::panic_nounwind_fmt
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panicking.rs:122:5
3: core::panicking::panic_nounwind
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panicking.rs:221:5
4: core::panicking::panic_cannot_unwind
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panicking.rs:309:5
5: objc2::exception::try_no_ret::try_objc_execute_closure
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc2-0.5.2/src/exception.rs:196:9
6: rust_objc_sys_0_3_try_catch_exception
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc-sys-0.3.5/extern/exception.m:14:9
7: objc2::exception::try_no_ret
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc2-0.5.2/src/exception.rs:232:28
8: objc2::exception::catch
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc2-0.5.2/src/exception.rs:291:27
9: objc2::runtime::message_receiver::MessageReceiver::send_message
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc2-0.5.2/src/runtime/message_receiver.rs:25:15
10: objc2::__macro_helpers::msg_send::MsgSend::send_message
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc2-0.5.2/src/__macro_helpers/msg_send.rs:27:31
11: objc2_app_kit::generated::__NSView::NSView::removeFromSuperview
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/objc2-0.5.2/src/macros/extern_methods.rs:247:14
12: tray_icon::platform_impl::platform::TrayIcon::remove
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tray-icon-0.19.2/src/platform_impl/macos/mod.rs:106:17
13: <tray_icon::platform_impl::platform::TrayIcon as core::ops::drop::Drop>::drop
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tray-icon-0.19.2/src/platform_impl/macos/mod.rs:258:9
14: core::ptr::drop_in_place<tray_icon::platform_impl::platform::TrayIcon>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
15: core::ptr::drop_in_place<core::cell::UnsafeCell<tray_icon::platform_impl::platform::TrayIcon>>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
16: core::ptr::drop_in_place<core::cell::RefCell<tray_icon::platform_impl::platform::TrayIcon>>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
17: <alloc::rc::Rc<T,A> as core::ops::drop::Drop>::drop
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/rc.rs:2222:17
18: core::ptr::drop_in_place<alloc::rc::Rc<core::cell::RefCell<tray_icon::platform_impl::platform::TrayIcon>>>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
19: core::ptr::drop_in_place<tray_icon::TrayIcon>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
20: core::ptr::drop_in_place<tauri::tray::TrayIcon>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
21: core::ptr::drop_in_place<[tauri::tray::TrayIcon]>
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/ptr/mod.rs:542:1
22: alloc::vec::Vec<T,A>::clear
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/vec/mod.rs:2243:13
23: tauri::app::AppHandle<R>::cleanup_before_exit
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/app.rs:888:9
24: trguing::setup::{{closure}}::{{closure}}
at ./src/main.rs:149:13
25: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/alloc/src/boxed.rs:2084:9
26: tauri::event::listener::Listeners::emit_filter
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/event/listener.rs:204:13
27: tauri::event::listener::Listeners::emit
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/event/listener.rs:219:5
28: tauri::manager::AppManager<R>::emit
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/manager/mod.rs:558:5
29: tauri::Emitter::emit
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/lib.rs:943:5
30: tauri::event::plugin::emit::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/event/plugin.rs:64:3
31: <F as futures_core::future::TryFuture>::try_poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-core-0.3.31/src/future.rs:92:9
32: <futures_util::future::try_future::into_future::IntoFuture<Fut> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/future/try_future/into_future.rs:34:9
33: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/future/future/map.rs:55:37
34: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/lib.rs:86:13
35: <futures_util::future::try_future::MapErr<Fut,F> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/lib.rs:86:13
36: <futures_util::future::try_future::ErrInto<Fut,E> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/lib.rs:86:13
37: <futures_util::future::future::map::Map<Fut,F> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/future/future/map.rs:55:37
38: <futures_util::future::future::Map<Fut,F> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.31/src/lib.rs:86:13
39: tauri::event::plugin::init::{{closure}}::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/event/plugin.rs:58:1
40: tauri::ipc::InvokeResolver<R>::respond_async_serialized::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-2.2.5/src/ipc/mod.rs:343:33
41: <core::pin::Pin<P> as core::future::future::Future>::poll
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/future/future.rs:123:9
42: tokio::runtime::task::core::Core<T,S>::poll::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/core.rs:331:17
43: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/loom/std/unsafe_cell.rs:16:9
44: tokio::runtime::task::core::Core<T,S>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/core.rs:320:13
45: tokio::runtime::task::harness::poll_future::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:532:19
46: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panic/unwind_safe.rs:272:9
47: std::panicking::try::do_call
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:557:40
48: ___rust_try
49: std::panicking::try
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:521:19
50: std::panic::catch_unwind
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panic.rs:350:14
51: tokio::runtime::task::harness::poll_future
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:520:18
52: tokio::runtime::task::harness::Harness<T,S>::poll_inner
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:209:27
53: tokio::runtime::task::harness::Harness<T,S>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:154:15
54: tokio::runtime::task::raw::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/raw.rs:271:5
55: tokio::runtime::task::raw::RawTask::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/raw.rs:201:18
56: tokio::runtime::task::LocalNotified<S>::run
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/mod.rs:449:9
57: tokio::runtime::scheduler::multi_thread::worker::Context::run_task::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:596:13
58: tokio::runtime::coop::with_budget
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/coop.rs:107:5
59: tokio::runtime::coop::budget
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/coop.rs:73:5
60: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:595:9
61: tokio::runtime::scheduler::multi_thread::worker::Context::run
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:546:24
62: tokio::runtime::scheduler::multi_thread::worker::run::{{closure}}::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:511:21
63: tokio::runtime::context::scoped::Scoped<T>::set
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/context/scoped.rs:40:9
64: tokio::runtime::context::set_scheduler::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/context.rs:180:26
65: std::thread::local::LocalKey<T>::try_with
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/thread/local.rs:283:12
66: std::thread::local::LocalKey<T>::with
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/thread/local.rs:260:9
67: tokio::runtime::context::set_scheduler
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/context.rs:180:9
68: tokio::runtime::scheduler::multi_thread::worker::run::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:506:9
69: tokio::runtime::context::runtime::enter_runtime
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/context/runtime.rs:65:16
70: tokio::runtime::scheduler::multi_thread::worker::run
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:498:5
71: tokio::runtime::scheduler::multi_thread::worker::Launch::launch::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/scheduler/multi_thread/worker.rs:464:45
72: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/blocking/task.rs:42:21
73: tokio::runtime::task::core::Core<T,S>::poll::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/core.rs:331:17
74: tokio::loom::std::unsafe_cell::UnsafeCell<T>::with_mut
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/loom/std/unsafe_cell.rs:16:9
75: tokio::runtime::task::core::Core<T,S>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/core.rs:320:13
76: tokio::runtime::task::harness::poll_future::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:532:19
77: <core::panic::unwind_safe::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/panic/unwind_safe.rs:272:9
78: std::panicking::try::do_call
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:557:40
79: ___rust_try
80: std::panicking::try
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panicking.rs:521:19
81: std::panic::catch_unwind
at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/std/src/panic.rs:350:14
82: tokio::runtime::task::harness::poll_future
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:520:18
83: tokio::runtime::task::harness::Harness<T,S>::poll_inner
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:209:27
84: tokio::runtime::task::harness::Harness<T,S>::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/harness.rs:154:15
85: tokio::runtime::task::raw::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/raw.rs:271:5
86: tokio::runtime::task::raw::RawTask::poll
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/raw.rs:201:18
87: tokio::runtime::task::UnownedTask<S>::run
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/task/mod.rs:486:9
88: tokio::runtime::blocking::pool::Task::run
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/blocking/pool.rs:161:9
89: tokio::runtime::blocking::pool::Inner::run
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/blocking/pool.rs:511:17
90: tokio::runtime::blocking::pool::Spawner::spawn_thread::{{closure}}
at /Users/quick/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-1.43.0/src/runtime/blocking/pool.rs:469:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread caused non-unwinding panic. aborting.
```
### Additional context
_No response_ | type: bug,priority: 1 high,platform: macOS,status: needs triage | low | Critical |
2,812,476,728 | angular | Components sourcemap not resolved when using sub-paths | ### Which @angular/* package(s) are the source of the bug?
Don't known / other
### Is this a regression?
Yes
### Description
While using Angular SSR, the dev server is trying to fetch .component.css.map file from an API server instead of Angular server, resulting in 404 error and crashes Node JS server.
This issue occurs when you add custom styles to a component's stylesheet while also having HTTP client enabled. I have included a demo project that has two components - an Index component and a TodoDetail component. A simple CSS styling is included in the index.component.css file. The TodoDetail component makes a HTTP request to an external API using HttpClient service. While on the TodoDetail page, refresh the browser and clear browser cache, then return back to index page by clicking on the back button on the browser, depending whether you have `provideExperimentalZonelessChangeDetection` enabled or not, your dev node js SSR server should either crash or show HttpErrorResponse containing 404 Not Found error.
A demo project is uploaded to github [Acme Todo](https://github.com/rabikr/acme)
## To reproduce the error
1. Run the local dev server by running the command `ng serve`.
2. Open Chrome, navigate to home page.
3. Open Chrome dev tool, go to network tab, select `Disable cache`.
4. On the home page, click any one of the link.
5. Refresh the page while on the todo detail view page. This is clear the cache.
6. Return back to the previous page using the back button.
7. Check server node js logs, it shows the dev server is trying to fetch .component.css.map file from the API server instead of Angular dev server.
### Please provide a link to a minimal reproduction of the bug
https://github.com/rabikr/acme
### Please provide the exception or error you saw
```true
ERROR HttpErrorResponse {
headers: _HttpHeaders {
headers: Map(25) {
'access-control-allow-credentials' => [Array],
'age' => [Array],
'alt-svc' => [Array],
'cache-control' => [Array],
'cf-cache-status' => [Array],
'cf-ray' => [Array],
'connection' => [Array],
'content-length' => [Array],
'content-type' => [Array],
'date' => [Array],
'etag' => [Array],
'expires' => [Array],
'nel' => [Array],
'pragma' => [Array],
'report-to' => [Array],
'reporting-endpoints' => [Array],
'server' => [Array],
'server-timing' => [Array],
'vary' => [Array],
'via' => [Array],
'x-content-type-options' => [Array],
'x-powered-by' => [Array],
'x-ratelimit-limit' => [Array],
'x-ratelimit-remaining' => [Array],
'x-ratelimit-reset' => [Array]
},
normalizedNames: Map(25) {
'access-control-allow-credentials' => 'access-control-allow-credentials',
'age' => 'age',
'alt-svc' => 'alt-svc',
'cache-control' => 'cache-control',
'cf-cache-status' => 'cf-cache-status',
'cf-ray' => 'cf-ray',
'connection' => 'connection',
'content-length' => 'content-length',
'content-type' => 'content-type',
'date' => 'date',
'etag' => 'etag',
'expires' => 'expires',
'nel' => 'nel',
'pragma' => 'pragma',
'report-to' => 'report-to',
'reporting-endpoints' => 'reporting-endpoints',
'server' => 'server',
'server-timing' => 'server-timing',
'vary' => 'vary',
'via' => 'via',
'x-content-type-options' => 'x-content-type-options',
'x-powered-by' => 'x-powered-by',
'x-ratelimit-limit' => 'x-ratelimit-limit',
'x-ratelimit-remaining' => 'x-ratelimit-remaining',
'x-ratelimit-reset' => 'x-ratelimit-reset'
},
lazyInit: undefined,
lazyUpdate: null
},
status: 404,
statusText: 'Not Found',
url: 'https://jsonplaceholder.typicode.com/todos/index.component.css.map',
ok: false,
type: undefined,
name: 'HttpErrorResponse',
message: 'Http failure response for https://jsonplaceholder.typicode.com/todos/index.component.css.map: 404 Not Found',
error: {}
}
```
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular CLI: 19.1.4
Node: 22.12.0
Package Manager: npm 11.0.0
OS: win32 x64
Angular: 19.1.3
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1901.4
@angular-devkit/build-angular 19.1.4
@angular-devkit/core 19.1.4
@angular-devkit/schematics 19.1.4
@angular/cli 19.1.4
@angular/ssr 19.1.4
@schematics/angular 19.1.4
rxjs 7.8.1
typescript 5.7.3
zone.js 0.15.0
```
### Anything else?
_No response_ | area: core,core: stylesheets | low | Critical |
2,812,486,439 | ollama | Error fetching ANY model locally | ### What is the issue?
This is the Error message that I am getting:
pulling manifest
pulling 6e9f90f02bb3... 0% ▕ ▏ 0 B/9.0 GB
Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/6e/6e9f90f02bb3b39b59e81916e8cfce9deb45aeaeb9a54a5be4414486b907dc1e/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250127%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20250127T091701Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=1afc1dcb356baf92d38344324c5f1504f216d4c77efb000442698708739d0298": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host
the command I am using:
`ollama pull <model-name>`
I have also tried using:
`ollama run <model-name>`
Any Model that I want to fetch locally, throws this error. How to fix it? I believe, I have installed OLLAMA properly.
Please tell me how to resolve it.
### OS
Windows
### GPU
Nvidia
### CPU
Intel
### Ollama version
0.5.4 | bug,networking | low | Critical |
2,812,498,411 | flutter | Execution failed for task ':app:compileFlutterBuildDebug'. | ### Steps to reproduce
1. flutter run
### Expected results
The app should launch normally.
If I use flutter clean, flutter pub get and then flutter run the app launches fine.
### Actual results
The app crashes immediately
### Code sample
`none`
### Screenshots or Video
_No response_
### Logs
[flutter-run-logs.txt](https://github.com/user-attachments/files/18556086/flutter-run-logs.txt)
### Flutter Doctor output
[flutter-doctor-logs.txt](https://github.com/user-attachments/files/18556084/flutter-doctor-logs.txt) | in triage | low | Critical |
2,812,517,050 | rust | Heavy usage of TLS causes stack overflow | i wrote a dynamic library which uses `tracing`, which internally uses `std`s TLS implemention.
On unix, when I repeatedly load and then unload my library, eventually (after maybe 10 to 20 iterations) the program encounters a stack overflow.
After some research I found that this was due to the following flow:
`pthread_key_create` is called when TLS is initialized each time my library is loaded and my `tracing` logger is used.
`pthread_key_delete` is never called, there is no cleanup in this area.
Eventually `pthread_key_create` returns `EAGAIN`, which causes a panic.
Within the panic, the number of panics for the thread is tracked using TLS so when `increase` is called, we encounter a new panic (due to `EAGAIN`), which in turn will panic for the same reason.
We enter an endless loop of panics which eventually triggers a stack overflow. | A-thread-locals,C-bug,T-libs,A-panic | low | Minor |
2,812,529,913 | flutter | pairwiseCompare produces confusing 'Which: has <null> which is not <null> at index null' on Type mismatch | ### Steps to reproduce
1. Add test from code sample to any flutter project
2. run test
### Expected results
Should not use <null> in place of actual values and omit misleading `index null` message.
Another small nit: there is a double space before the second `<null>`.
### Actual results
```
[...]
Expected: pairwise ['a']
Actual: [1]
Which: has <null> which is not <null> at index null
type 'int' is not a subtype of type 'String' in type cast at #0 _PairwiseCompare.typedMatches (package:matcher/src/iterable_matchers.dart:266:44)
[...]
```
### Code sample
<details open><summary>Code sample</summary>
```dart
test('throws has <null> which is not description <null> at index null', () {
expect([1], pairwiseCompare(['a'], (String a, String b) => a == b, ''));
});
```
</details>
### Logs
<details><summary>Logs</summary>
```console
derdilla@dilladesk ~/code/ff_bug % flutter test
00:01 +0: throws has <null> which is not description <null> at index null
#0 FeatureMatcher.describeMismatch (package:matcher/src/feature_matcher.dart:23:22)
#1 _expect.<anonymous closure> (package:matcher/src/expect/expect.dart:81:13)
#2 _expect (package:matcher/src/expect/expect.dart:144:17)
#3 expect (package:matcher/src/expect/expect.dart:56:3)
#4 expect (package:flutter_test/src/widget_tester.dart:480:18)
#5 main.<anonymous closure> (file:///home/derdilla/code/ff_bug/test/widget_test.dart:5:5)
#6 Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:215:19)
<asynchronous suspension>
#7 Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:213:7)
<asynchronous suspension>
#8 Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:258:9)
<asynchronous suspension>
00:01 +0 -1: throws has <null> which is not description <null> at index null [E]
Expected: pairwise ['a']
Actual: [1]
Which: has <null> which is not <null> at index null
type 'int' is not a subtype of type 'String' in type cast at #0 _PairwiseCompare.typedMatches (package:matcher/src/iterable_matchers.dart:266:44)
#1 FeatureMatcher.matches (package:matcher/src/feature_matcher.dart:16:42)
#2 _expect (package:matcher/src/expect/expect.dart:138:30)
#3 expect (package:matcher/src/expect/expect.dart:56:3)
#4 expect (package:flutter_test/src/widget_tester.dart:480:18)
#5 main.<anonymous closure> (file:///home/derdilla/code/ff_bug/test/widget_test.dart:5:5)
#6 Declarer.test.<anonymous closure>.<anonymous closure> (package:test_api/src/backend/declarer.dart:215:19)
<asynchronous suspension>
#7 Declarer.test.<anonymous closure> (package:test_api/src/backend/declarer.dart:213:7)
<asynchronous suspension>
#8 Invoker._waitForOutstandingCallbacks.<anonymous closure> (package:test_api/src/backend/invoker.dart:258:9)
<asynchronous suspension>
package:matcher expect
package:flutter_test/src/widget_tester.dart 480:18 expect
test/widget_test.dart 5:5 main.<fn>
To run this test again: /home/derdilla/.local/flutter/bin/cache/dart-sdk/bin/dart test /home/derdilla/code/ff_bug/test/widget_test.dart -p vm --plain-name 'throws has <null> which is not description <null> at index null'
00:01 +0 -1: Some tests failed.
```
</details>
### Flutter Doctor output
<details><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.27.3, on Arch Linux 6.12.10-zen1-1-zen, locale en_US.UTF-8)
• Flutter version 3.27.3 on channel stable at /home/derdilla/.local/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (6 days ago), 2025-01-21 10:32:23 -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 /home/derdilla/.android
• Platform android-35, build-tools 35.0.1
• ANDROID_HOME = /home/derdilla/.android
• Java binary at: /sbin/java
• Java version OpenJDK Runtime Environment (build 21.0.6+7)
• All Android licenses accepted.
[✓] Chrome - develop for the web
• CHROME_EXECUTABLE = /sbin/chromium
[✓] Linux toolchain - develop for Linux desktop
• clang version 19.1.7
• cmake version 3.31.5
• ninja version 1.12.1
• pkg-config version 2.3.0
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/to/linux-android-setup for detailed instructions).
[✓] IntelliJ IDEA Ultimate Edition (version 2024.3)
• IntelliJ at /home/derdilla/.local/share/JetBrains/Toolbox/apps/intellij-idea-ultimate
• Flutter plugin version 83.0.4
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
[✓] Connected device (2 available)
• Linux (desktop) • linux • linux-x64 • Arch Linux 6.12.10-zen1-1-zen
• Chrome (web) • chrome • web-javascript • Chromium 132.0.6834.110 Arch Linux
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.
flutter doctor -v 4.65s user 0.58s system 188% cpu 2.770 total
```
</details>
| waiting for customer response,in triage | low | Critical |
2,812,534,440 | pytorch | Add `sharding strategy` for `torch.distributed.tensor.parallel.ParallelStyle` with `inference_mode` | ### 🚀 The feature, motivation and pitch
When using tensor parallel and `with torch.inference_mode()`, any `torch.distributed.tensor.parallel.ParallelStyle` layers, we have:
`aten.mm.default: got mixed torch.Tensor and DTensor, need to convert all torch.Tensor to DTensor before calling distributed operators!`.
With `transformers == 4.48` and `torch==2.5.1`
```python
import torch
from transformers import LlamaConfig, LlamaModel
import os
model_id = "meta-llama/Meta-Llama-3-8B-Instruct"
bs = 1
seqlen = 4096
# Get distributed settings
rank = int(os.environ["RANK"])
world_size = int(os.environ["WORLD_SIZE"])
# Initialize distributed
device = torch.device(f"cuda:{rank}")
torch.distributed.init_process_group("nccl", device_id=device)
device_mesh = torch.distributed.init_device_mesh("cuda", (world_size,))
# Get model config
config = LlamaConfig.from_pretrained(model_id)
config.hidden_size = 2048
config.attention_bias = False
# Instantiate model
with device:
model = LlamaModel(config).to(dtype=torch.float16)
model.eval()
model.tensor_parallel(device_mesh)
inputs = torch.randint(config.vocab_size, (bs, seqlen), device=device)
# Test compile
with torch.inference_mode():
out = model(inputs)
```
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @tianyu-l @XilunWu @albanD as we talked about this
### Alternatives
_No response_
### Additional context
_No response_ | oncall: distributed,triaged,module: dtensor | low | Minor |
2,812,541,502 | pytorch | Add correct `__repr__` for parallel distributed modules | ### 🚀 The feature, motivation and pitch
Sorry if this is a duplicated, but instantiating a `transformers` and paralellizing will print the same model, which is unintuitive.
```python
import torch
import os
from transformers import LlamaConfig, LlamaModel
model_id = "meta-llama/Meta-Llama-3-8B-Instruct"
bs = 1
seqlen = 4096
# Get distributed settings
rank = int(os.environ["RANK"])
world_size = int(os.environ["WORLD_SIZE"])
# Initialize distributed
device = torch.device(f"cuda:{rank}")
torch.distributed.init_process_group("nccl", device_id=device)
device_mesh = torch.distributed.init_device_mesh("cuda", (world_size,))
# Get model config
config = LlamaConfig.from_pretrained(model_id)
config.hidden_size = 2048
config.attention_bias = False
# Instantiate model
with device:
model = LlamaModel(config).to(dtype=torch.float16)
model.eval()
# Tensor Parallel
if world_size > 1:
model.tensor_parallel(device_mesh)
print(model)
```
should IMO print `ColumParallel(...., device_mesh = [0,1])` etc
### Alternatives
_No response_
### Additional context
_No response_
cc @chauhang @penguinwu | oncall: pt2 | low | Minor |
2,812,600,332 | vscode | explorer: cannot duplicate last saved version of unsaved file |
Type: <b>Bug</b>
1. Save a file.
1. Edit it without saving it.
1. In the VSCode file explorer, click on this file, copy and paste it in the same folder (ctrl-c, ctrl-v).
1. The copy has the same content as the unsaved file, not the content of the last saved version of the file!
This is a problem because the saved state is often a critical reference point for creating backups or comparisons.
VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.19045
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz (4 x 2592)|
|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.76GB (1.30GB free)|
|Process Argv|--disable-extensions --crash-reporter-id dcf1a538-7ced-4334-a13e-401517f8220e|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>
```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyonecf:30548226
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
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730
```
</details>
<!-- generated by issue reporter --> | feature-request,file-explorer | low | Critical |
2,812,613,660 | ant-design | In Menu, if there is `extra` and text doesn't fit in width, `extra` isn't visible at all | ### Reproduction link
[https://codepen.io/rakleed/pen/EaYGWeL?editors=001](https://codepen.io/rakleed/pen/EaYGWeL?editors=001)
### Steps to reproduce
1. `label` should be longer than the maximum menu width.
2. You need to add `extra`.
### What is expected?
`extra` is visible, and the text is reduced using an ellipsis.
### What is actually happening?
`extra` is not visible, and the text is not shortened.
| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18.3.1 |
| System | macOS 15.2 |
| Browser | Chrome 132 |
---
Probably you should wrap `label` in `<span>`, and add `overflow: hidden; text-overflow: ellipsis;` to it.
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | unconfirmed | low | Minor |
2,812,619,963 | storybook | [Bug]: strange Manager.js path that run infinitely in background | ### Describe the bug
in my project
https://design.copromatic.com/
when you check your console nav you can see many error runs in background with strange url.
i didn't found any relative issues.
https://design.copromatic.com/sb-preview/sb-addons/essentials-backgrounds-5/sb-addons/storybook-core-core-server-presets-0/sb-addons/essentials-viewport-6/sb-addons/links-1/manager-bundle.js
when i run in local with
> npx http-server ./storybook-static
There is no errors
I use
storybook 8.5.1
vite 6.0.11
cloudflare pages
### Reproduction link
https://design.copromatic.com/
### Reproduction steps
_No response_
### System
```bash
npx storybook@latest info
Storybook Environment Info:
System:
OS: macOS 14.5
CPU: (8) arm64 Apple M1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node
npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm <----- active
pnpm: 9.11.0 - /opt/homebrew/bin/pnpm
Browsers:
Chrome: 132.0.6834.110
Safari: 17.5
npmPackages:
@storybook/addon-essentials: ^8.5.1 => 8.5.1
@storybook/addon-interactions: ^8.5.1 => 8.5.1
@storybook/addon-links: ^8.5.1 => 8.5.1
@storybook/addon-mdx-gfm: ^8.5.1 => 8.5.1
@storybook/addon-storysource: ^8.5.1 => 8.5.1
@storybook/blocks: ^8.5.1 => 8.5.1
@storybook/manager-api: ^8.5.1 => 8.5.1
@storybook/test: ^8.5.1 => 8.5.1
@storybook/theming: ^8.5.1 => 8.5.1
@storybook/vue3: ^8.5.1 => 8.5.1
@storybook/vue3-vite: ^8.5.1 => 8.5.1
storybook: ^8.5.1 => 8.5.1
storybook-version: ^0.1.2 => 0.1.2
storybook-vue3-router: ^5.0.0 => 5.0.0
```
### Additional context
_No response_ | bug,compatibility with other tools,build-storybook | low | Critical |
2,812,638,286 | react | Bug: | React version: 19.0.0
My code is not shown in the error stack. How can I know what caused the error?
```
Uncaught Error: Objects are not valid as a React child (found: object with keys {message, data, description}). If you meant to render a collection of children, use an array instead.
React 11
throwOnInvalidObjectType
reconcileChildFibersImpl
createChildReconciler
reconcileChildren
beginWork
runWithFiberInDEV
performUnitOfWork
workLoopSync
renderRootSync
performWorkOnRoot
performWorkOnRootViaSchedulerTask
performWorkUntilDeadline scheduler.development.js:44
js scheduler.development.js:219
js scheduler.development.js:364
__require chunk-DC5AMYBS.js:9
js index.js:6
__require chunk-DC5AMYBS.js:9
React 2
js
js
__require chunk-DC5AMYBS.js:9
js React
__require chunk-DC5AMYBS.js:9
<anonymous> react-dom_client.js:17892
react-dom-client.development.js:4446:12
React 11
throwOnInvalidObjectType
reconcileChildFibersImpl
createChildReconciler
reconcileChildren
beginWork
runWithFiberInDEV
performUnitOfWork
workLoopSync
renderRootSync
performWorkOnRoot
performWorkOnRootViaSchedulerTask
performWorkUntilDeadline scheduler.development.js:44
(Async: EventHandlerNonNull)
js scheduler.development.js:219
js scheduler.development.js:364
__require chunk-DC5AMYBS.js:9
js index.js:6
__require chunk-DC5AMYBS.js:9
React 2
js
js
__require chunk-DC5AMYBS.js:9
js React
__require chunk-DC5AMYBS.js:9
<anonymous> react-dom_client.js:17892
```
I have more than 75 thousand lines of code in my React app. How can I find where is the problem in my code? | Status: Unconfirmed | medium | Critical |
2,812,651,993 | flutter | [webview_flutter] WebView inside indexedStack on IOS does not load content until the tab becomes visible | ### What package does this bug report belong to?
webview_flutter
### What target platforms are you seeing this bug on?
iOS
### 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"
cupertino_icons:
dependency: "direct main"
description:
name: cupertino_icons
sha256: ba631d1c7f7bef6b729a622b7b752645a2d076dba9976925b8f25725a30e1ee6
url: "https://pub.dev"
source: hosted
version: "1.0.8"
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"
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"
vm_service:
dependency: transitive
description:
name: vm_service
sha256: f6be3ed8bd01289b34d679c2b62226f63c0e69f9fd2e50a6b3c1c729a961041b
url: "https://pub.dev"
source: hosted
version: "14.3.0"
webview_flutter:
dependency: "direct main"
description:
name: webview_flutter
sha256: "889a0a678e7c793c308c68739996227c9661590605e70b1f6cf6b9a6634f7aec"
url: "https://pub.dev"
source: hosted
version: "4.10.0"
webview_flutter_android:
dependency: transitive
description:
name: webview_flutter_android
sha256: "3d535126f7244871542b2f0b0fcf94629c9a14883250461f9abe1a6644c1c379"
url: "https://pub.dev"
source: hosted
version: "4.2.0"
webview_flutter_platform_interface:
dependency: transitive
description:
name: webview_flutter_platform_interface
sha256: d937581d6e558908d7ae3dc1989c4f87b786891ab47bb9df7de548a151779d8d
url: "https://pub.dev"
source: hosted
version: "2.10.0"
webview_flutter_wkwebview:
dependency: transitive
description:
name: webview_flutter_wkwebview
sha256: "4adc14ea9a770cc9e2c8f1ac734536bd40e82615bd0fa6b94be10982de656cc7"
url: "https://pub.dev"
source: hosted
version: "3.17.0"
sdks:
dart: ">=3.6.1 <4.0.0"
flutter: ">=3.24.0"
```
</details>
### Steps to reproduce
1. run the app on ios real device or simulator.
2. wait for a 2 to 3 seconds after "page finished" log shown in the console
3. click on settings tab
4. first a white screen shown and after that webview content is shown.
5. if you wait longer like around 10 to 15 seconds. sometimes "reloading in 2 seconds" text appear on real ios device. i tested it on ipad mini 6 and got that issue for the DIFC site link.
### Expected results
like android, the webview should be preloaded in the background.
### Actual results
a white screen comes up for a second and then webview content shows. sometimes i am also getting a text on a white screen "reloading in 2 seconds...." and after that webviewController reloads the page again and in the logs "page finished" logs twice.
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
useMaterial3: true,
),
home: const MyHomePage(),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key});
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
int currentSelectedIndex = 0;
@override
Widget build(BuildContext context) {
return Scaffold(
body: IndexedStack(
index: currentSelectedIndex,
children: const [
Center(child: Text('Home')),
Center(child: MyWebViewScreen()),
Center(child: Text('Profile')),
],
),
bottomNavigationBar: BottomNavigationBar(
currentIndex: currentSelectedIndex,
onTap: (index) {
setState(() {
currentSelectedIndex = index;
});
},
items: const [
BottomNavigationBarItem(
icon: Icon(Icons.home),
label: 'Home',
),
BottomNavigationBarItem(
icon: Icon(Icons.settings),
label: 'Settings',
),
BottomNavigationBarItem(
icon: Icon(Icons.person),
label: 'Profile',
),
],
),
);
}
}
class MyWebViewScreen extends StatefulWidget {
const MyWebViewScreen({super.key});
@override
State<MyWebViewScreen> createState() => _MyWebViewScreenState();
}
class _MyWebViewScreenState extends State<MyWebViewScreen> {
late final WebViewController controller;
@override
void initState() {
super.initState();
controller = WebViewController()
..setJavaScriptMode(JavaScriptMode.unrestricted);
controller.setNavigationDelegate(
NavigationDelegate(
onPageStarted: (url) {},
onPageFinished: (url) {
print("page finished");
},
),
);
/*
https://map.abuzz.tech/amap/embedex.php?site=TDM_&searchUI=true&servicesList=true&poiUI=true&pathUI=true&hover=true&lazyld=false&mobile=true
https://map.abuzz.tech/amap/map.php?site=AVENUES_KW&device=KW-AVENUES-01&from=_114897_11515_0&to=_81656_32726_500&lang=EN
*/
controller.loadRequest(Uri.parse(
"https://map.abuzz.tech/amap/embedex.php?site=DIFC_"));
}
@override
Widget build(BuildContext context) {
return Scaffold(
body: WebViewWidget(controller: controller),
);
}
}
```
</details>
### Screenshots or Videos
<details open>
<summary>Screenshots / Video demonstration</summary>
https://github.com/user-attachments/assets/2cd50831-0fa2-40c1-b57e-7c01a6d322f5
https://github.com/user-attachments/assets/e9a2ec4a-f463-4ac0-8d43-3d9892dae836
https://github.com/user-attachments/assets/f0cfec18-d198-49b5-bbf2-456288d7d547
<img width="821" alt="Image" src="https://github.com/user-attachments/assets/a67186eb-49ad-4dac-afa7-861a8a65575d" />
https://github.com/user-attachments/assets/48137c14-9fca-4859-b047-9f48badee4d6
https://github.com/user-attachments/assets/fe3958db-0477-4f9a-b2e8-8c73b805c9cc
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.27.3, on macOS 15.1.1 24B91 darwin-arm64, locale en-AE)
• Flutter version 3.27.3 on channel stable at /opt/homebrew/Caskroom/flutter/2.10.4/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (6 days ago), 2025-01-21 10:32:23 -0800
• Engine revision e672b006cb
• Dart version 3.6.1
• DevTools version 2.40.2
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/abubakarnawaz/Library/Android/sdk
• Platform android-35, build-tools 34.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
• 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.14.3
[✓] 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.3+-79915917-b509.11)
[✓] VS Code (version 1.96.4)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (4 available)
• Abu Bakar’s iPad mini (mobile) • 00008110-00062D081AA2401E • ios • iOS 18.2.1 22C161
• macOS (desktop) • macos • darwin-arm64 • macOS 15.1.1 24B91
darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 15.1.1 24B91
darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome
132.0.6834.110
[✓] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| waiting for customer response,in triage | low | Critical |
2,812,658,044 | transformers | Convert RT-DETR model to coreml | Hello,
I am currently working on an iOS application that requires object detection functionality, and I’m interested in using the RT-DETR model for this purpose. I would like to ask if anyone has experience or knows of a way to transfer the RT-DETR model into the CoreML format to be used on iOS devices.
Thank you in advance! | Vision | low | Major |
2,812,661,670 | ollama | Add an ability to inject env variables to modelfile system message. | Hi All.
I`ve realized that that there is no way to make ollama models to know current date and time if it runs on ms windows. So I believe that would be useful if there would be possibility to use OS variables in the modelfile. Especially for date and time it would be better if model could obtain that data dynamically, just when it needed.
Use case: model could answer what date and time it is. | feature request | low | Minor |
2,812,683,841 | PowerToys | the FN lock function disabled | ### Microsoft PowerToys version
0.87.1
### Installation method
Microsoft Store
### Running as admin
Yes
### Area(s) with issue?
Keyboard Manager
### Steps to reproduce
After using the keyboard mapping, the FN lock function of the computer itself will be disabled.
### ✔️ Expected Behavior
Maintain the original FN function or provide FN mapping.
### ❌ Actual Behavior
_No response_
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,812,688,362 | vscode | Asset creation in cosmos db can fail after publishing | Build link https://monacotools.visualstudio.com/Monaco/_build/results?buildId=314603&view=logs&j=43b54640-f671-5524-8f7b-714d77229de9&t=7f630ceb-a7eb-52db-66b5-c361c37b9f4e
`vscode_client_win32_x64_archive` asset creation failed with
```
[vscode_client_win32_x64_archive] Deleting blob https://vscodeesrp.blob.core.windows.net/staging/6b601934-aa74-40f2-a610-a13b99cb8c0f
[vscode_client_win32_x64_archive] Deleted blob successfully
TypeError: fetch failed
at node:internal/deps/undici/undici:13392:13
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async ESRPReleaseService.getReleaseStatus (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:225:21)
at async ESRPReleaseService.createRelease (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:137:39)
at async D:\a\_work\1\s\build\azure-pipelines\common\publish.js:543:13
at async withLease (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:500:32)
at async processArtifact (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:532:5)
at async main (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:578:9) {
[cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: api.esrp.microsoft.com:443, timeout: 10000ms)
at onConnectTimeout (node:internal/deps/undici/undici:2599:28)
at Immediate._onImmediate (node:internal/deps/undici/undici:2568:35)
at process.processImmediate (node:internal/timers:483:21) {
code: 'UND_ERR_CONNECT_TIMEOUT'
}
}
[vscode_client_win32_x64_archive] Error: [vscode_client_win32_x64_archive] Worker stopped with exit code 1
at Worker.<anonymous> (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:647:32)
at Worker.emit (node:events:518:28)
at [kOnExit] (node:internal/worker:315:10)
at Worker.<computed>.onexit (node:internal/worker:229:20)
Error: Some artifacts failed to publish
at main (D:\a\_work\1\s\build\azure-pipelines\common\publish.js:674:15)
``` | vscode-build,engineering | low | Critical |
2,812,715,059 | go | x/vuln: false negative for GO-2024-3321 | ### Go version
go1.23.5
### Output of `go env` in your module/workspace:
```shell
GO111MODULE=''
GOARCH='amd64'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOOS='linux'
GOROOT='/usr/local/go'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.5'
GODEBUG=''
GOTELEMETRY='local'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='0'
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 -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build753288169=/tmp/go-build -gno-record-gcc-switches
```
### What did you do?
Ran govulncheck on the sample code below (https://pkg.go.dev/golang.org/x/crypto/ssh#ServerConn example, with a `fmt.Println` added):
```go
package main
import (
"fmt"
"log"
"net"
"os"
"sync"
"golang.org/x/crypto/ssh"
"golang.org/x/crypto/ssh/terminal"
)
func main() {
// Public key authentication is done by comparing
// the public key of a received connection
// with the entries in the authorized_keys file.
authorizedKeysBytes, err := os.ReadFile("authorized_keys")
if err != nil {
log.Fatalf("Failed to load authorized_keys, err: %v", err)
}
authorizedKeysMap := map[string]bool{}
for len(authorizedKeysBytes) > 0 {
pubKey, _, _, rest, err := ssh.ParseAuthorizedKey(authorizedKeysBytes)
if err != nil {
log.Fatal(err)
}
authorizedKeysMap[string(pubKey.Marshal())] = true
authorizedKeysBytes = rest
}
// An SSH server is represented by a ServerConfig, which holds
// certificate details and handles authentication of ServerConns.
config := &ssh.ServerConfig{
// Remove to disable public key auth.
PublicKeyCallback: func(c ssh.ConnMetadata, pubKey ssh.PublicKey) (*ssh.Permissions, error) { // <<< Affected by the CVE and called
fmt.Printf("received key: %s\n", ssh.FingerprintSHA256(pubKey))
if authorizedKeysMap[string(pubKey.Marshal())] {
return &ssh.Permissions{
// Record the public key used for authentication.
Extensions: map[string]string{
"pubkey-fp": ssh.FingerprintSHA256(pubKey),
},
}, nil
}
return nil, fmt.Errorf("unknown public key for %q", c.User())
},
}
privateBytes, err := os.ReadFile("hostkey")
if err != nil {
log.Fatal("Failed to load private key: ", err)
}
private, err := ssh.ParsePrivateKey(privateBytes)
if err != nil {
log.Fatal("Failed to parse private key: ", err)
}
config.AddHostKey(private)
// Once a ServerConfig has been configured, connections can be
// accepted.
listener, err := net.Listen("tcp", "0.0.0.0:2022")
if err != nil {
log.Fatal("failed to listen for connection: ", err)
}
nConn, err := listener.Accept()
if err != nil {
log.Fatal("failed to accept incoming connection: ", err)
}
// Before use, a handshake must be performed on the incoming
// net.Conn.
conn, chans, reqs, err := ssh.NewServerConn(nConn, config)
if err != nil {
log.Fatal("failed to handshake: ", err)
}
log.Printf("logged in with key %s", conn.Permissions.Extensions["pubkey-fp"])
}
```
### What did you see happen?
Program output (when connected to using the Linux SSH client):
```
$ go run .
received key: SHA256:bh9pEcEmRfexTHJqZk263fTJCGqwiZarIV7B8fWwif8
received key: SHA256:QxTUMyd5Rwm9eoBoasz9yyTj4rm7K5dUOJ0oQvp6Y4w
2025/01/25 09:05:56 logged in with key SHA256:QxTUMyd5Rwm9eoBoasz9yyTj4rm7K5dUOJ0oQvp6Y4w
```
govulncheck output:
```
Fetching vulnerabilities from the database...
Checking the code against the vulnerabilities...
The package pattern matched the following root package:
cve-2024-45337.test/F001/bin
Govulncheck scanned the following 4 modules and the go1.23.5 standard library:
cve-2024-45337.test/F001/bin
golang.org/x/[email protected]
golang.org/x/[email protected]
golang.org/x/[email protected]
=== Symbol Results ===
No vulnerabilities found.
=== Package Results ===
Vulnerability #1: GO-2024-3321
Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in
golang.org/x/crypto
More info: https://pkg.go.dev/vuln/GO-2024-3321
Module: golang.org/x/crypto
Found in: golang.org/x/[email protected]
Fixed in: golang.org/x/[email protected]
=== Module Results ===
No other vulnerabilities found.
Your code is affected by 0 vulnerabilities.
This scan also found 1 vulnerability in packages you import and 0
vulnerabilities in modules you require, but your code doesn't appear to call
these vulnerabilities.
```
### What did you expect to see?
The sample code is vulnerable to GO-2024-3321, as far as I can tell:
- uses golang.org/x/crypto v0.30.0
- serves SSH connections via ssh.NewServerConn and specifies a PublickeyCallback
Whilst the sample program does not misuse the callback, it potentially could. Based on the OSV record, the govulncheck seeks to determine whether ServerConfig.PublickeyCallback is executed (or reachable from main via call graph analysis). It clearly is but the report states otherwise. | NeedsInvestigation,vulncheck or vulndb | low | Critical |
2,812,717,265 | angular | Improve error message `Cannot resolve type entity ${entity} to {symbol|declaration}` | ### Command
build
### Description
I’m talking about this error, for instance, which people seem to encounter somewhat often [1–5]:
```
$ ng build
⠋ Generating browser application bundles (phase: building)...
✔ Browser application bundle generation complete.
./src/main.ts - Error: Module build failed (from ./node_modules/@ngtools/webpack/src/ivy/index.js):
Error: Cannot resolve type entity i7.BusifiableButtonComponent to symbol
```
This error message is not very actionable.
[1] https://stackoverflow.com/questions/71675705/error-cannot-resolve-type-entity-i10-bidimodule-to-symbol-while-building-angula
[2] https://github.com/primefaces/primeng/issues/11581
[3] https://github.com/valor-software/ngx-bootstrap/issues/6662
[4] https://github.com/angular/angular/issues/46441
[5] https://onthecode.co.uk/blog/error-cannot-resolve-type-entity-i3-dialogmodule-to-symbol
### Describe the solution you'd like
The issue seems to always be related to a transitive dependency not being found. *If* that is the true meaning of the error, I suggest rewording the error message to reflect that. I don’t know how much information is available at this point. My dreamed-of error message would be something like this (drawing inspiration from [JoostK’s comment](https://github.com/angular/angular/issues/46441#issuecomment-1161376788)):
> The type ${entity} could not be found. It seems to be a transitive dependency via this import chain:
> (root project) → (dependency) → (dependency) → ${entity}.
> This typically happens when a library is linked from another directory tree, where the necessary dependencies are not in a location the compiler can find, for instance when there is no corresponding node_modules directory from within that tree.
> Make sure that the library’s properly declares its dependencies and that they are installed.
> If it is due to symbolic links, then setting `projects.${project}.architect.build.options.preserveSymlinks: true` in the angular.json file may help. Otherwise, explicit path mappings for the unresolved dependency may also help.
At the very least, the file that imports the unresolvable entity should be displayed, again as suggested by [JoostK](https://github.com/angular/angular/issues/52520#issuecomment-1794326712).
### Describe alternatives you've considered
_No response_ | area: packaging,area: compiler | low | Critical |
2,812,755,485 | kubernetes | k8s deployment remove duplicate `tolerations` but not `affinity` | ### What happened?
If we create a deployment with duplicate toleration the pod spec doesn't reflect the duplicate values, but the same doesn't happen to duplicate node affinities,
Deployment tolerations:
```
tolerations:
- effect: NoSchedule
key: "key1"
operator: Equal
value: "true"
- effect: NoSchedule
key: "key1"
operator: Equal
value: "true"
```
Pod tolerations:
```
tolerations:
- effect: NoSchedule
key: "key1"
operator: Equal
value: "true"
```
Deployment Affinity == Pod affinity :
```
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: "key1"
operator: Exists
- key: "key1"
operator: Exists
- matchExpressions:
- key: "key1"
operator: Exists
- key: "key1"
operator: Exists
```
### What did you expect to happen?
Desired affinity:
```
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: "key1"
operator: Exists
```
### How can we reproduce it (as minimally and precisely as possible)?
Create a normal deployment with placements(tolerations and affinity)
### Anything else we need to know?
_No response_
### Kubernetes version
k8s.io/api v0.31.2
<details>
```console
$ kubectl version
# paste output here
```
</details>
### Cloud provider
<details>
</details>
### OS version
<details>
```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
</details>
### Install tools
<details>
</details>
### Container runtime (CRI) and version (if applicable)
<details>
</details>
### Related plugins (CNI, CSI, ...) and versions (if applicable)
<details>
</details>
| kind/bug,sig/apps,needs-triage | low | Minor |
2,812,762,084 | TypeScript | On magic disappearance of fields in the wild | ### 🔎 Search Terms
anonymous class this any
### 🕗 Version & Regression Information
I was unable to test this on prior versions because there is no tool to check for it online
### ⏯ Playground Link
https://www.typescriptlang.org/play/?#code/MYewdgzgLgBAhjAvDMBTA7jYAbOEIwDeMEq2AZkjFABYCWEA3DAL6MBQokI2qAdNhABzABRw+pCkkTI4ASg6dw0GIJAAHKmkw48BQuxhGSZSsloMOxmDSoBGK8djJtWXPiKHrx28gBMjt7UVJLkgazsbOwA9NEwAAoAThqoiVAAnjAA5FBZMAAmIKgEYCCwqAAeDLBK3LwCwiJq6nxQre2+MjB+CkA
### 💻 Code
```ts
const a = new class { self = this; };
console.log(a.self === a);
const loop = new class {
self = this;
h = 1;
t = new class {
h = 2;
t = self;
}
};
// Property 't' does not exist
console.log(loop.t.t.t.h === 2);
```
### 🙁 Actual behavior
Property 't' does not exist
### 🙂 Expected behavior
No type error
### Additional information about the issue
_No response_ | Working as Intended | low | Critical |
2,812,768,685 | PowerToys | Host File Editor - comment line - position of additional content Top | Bottom | (New) Remain as is | ### Description of the new feature / enhancement
Add one more option to remain the comments as is to the position of additional content. We may use it as a comment or grouping of the records.
### Scenario when this would be used?
updating the host file. It is either move the comments to top or bottom.
### Supporting information
_No response_ | Needs-Triage | low | Minor |
2,812,801,543 | storybook | [Bug]: Next.js Link component causes navigation to a non-existent page in stories | ### Describe the bug
When using the `Link` component from Next.js 15 within an `appDirectory` configuration, the component behavior is not properly overridden. This leads to navigating directly to nonexistent pages after clicking the link.
This behavior does not occur with Next.js 14.
### Reproduction link
https://stackblitz.com/edit/github-6hzs76ok?file=src%2Fstories%2FHeader.tsx
### Reproduction steps
1. Go to the above link
2. Go to a story of the Header component
3. Click the link on the header, and the preview will crush
### System
```bash
Storybook Environment Info:
System:
OS: Linux 5.0 undefined
CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Shell: 1.0 - /bin/jsh
Binaries:
Node: 18.20.3 - /usr/local/bin/node
Yarn: 1.22.19 - /usr/local/bin/yarn
npm: 10.2.3 - /usr/local/bin/npm <----- active
pnpm: 8.15.6 - /usr/local/bin/pnpm
npmPackages:
@storybook/addon-essentials: ^8.6.0-alpha.2 => 8.6.0-alpha.2
@storybook/addon-interactions: ^8.6.0-alpha.2 => 8.6.0-alpha.2
@storybook/addon-onboarding: ^8.6.0-alpha.2 => 8.6.0-alpha.2
@storybook/blocks: ^8.6.0-alpha.2 => 8.6.0-alpha.2
@storybook/nextjs: ^8.6.0-alpha.2 => 8.6.0-alpha.2
@storybook/react: ^8.6.0-alpha.2 => 8.6.0-alpha.2
@storybook/test: ^8.6.0-alpha.2 => 8.6.0-alpha.2
storybook: ^8.6.0-alpha.2 => 8.6.0-alpha.2
```
### Additional context
[Proper behavior with Next.js 14](https://stackblitz.com/edit/github-scn3vgkf?file=src%2Fstories%2FHeader.tsx,src%2Fstories%2FHeader.stories.ts&preset=node) | bug,nextjs | low | Critical |
2,812,813,974 | ui | [feat]: Catergory Bar in Charts | ### Feature description
Tremor UI offers a chart type called Category Bar, which we previously used in our product.
However, when we transitioned to Shadcn Chart, we noticed that this specific chart type is not available.
I wanted to check if there’s a possible workaround using the current bar chart component in Shadcn to replicate the functionality and appearance of the Category Bar from Tremor UI.
Let me know if this is feasible or if there are alternative approaches we can explore.
### Affected component/components
Charts
### Additional Context
https://tremor.so/charts
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues and PRs | area: request | low | Minor |
2,812,815,816 | TypeScript | constraint of type parameter should make effect in method declaration | ### 🔎 Search Terms
"constraint", "method declaration"
### 🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "A method and a function property of the same type behave differently"
### ⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.8.0-dev.20250127#code/JYOwLgpgTgZghgYwgAgIIB4AqA+ZBvAKGWRgHtT0BVZCAD0hABMBnZHACloC5lKBKHnBABPAgF8CBGAFcQCMMFIgSABnZweGZmCigA5tgA0yAEab0IaQFsT0bH3xFip5AF5kcZAHovyZgAtSaQAbRmQoCAAHUigwGigoGNNpOMQwaThg4OFkEFIwADpJZ1MCslJ2AEYHH2RZZiCmcUkgA
### 💻 Code
```ts
interface A<T> {
foo<U extends T>(x: U): any
}
function f0(a: A<string>, b: A<number>) {
b = a // should report error but actually not.
b.foo(1) // unsound
}
```
### 🙁 Actual behavior
check success
### 🙂 Expected behavior
`b = a` report `number` cannot assign to `string`.
### Additional information about the issue
_No response_ | Duplicate | low | Critical |
2,812,834,292 | kubernetes | [Flaking Test][sig-storage] E2eNode Suite.[It] [sig-storage] Projected configMap should be consumable from pods in volume [NodeConformance] [Conformance] | ### Which jobs are flaking?
master-blocking
- ci-crio-cgroupv2-node-e2e-conformance
### Which tests are flaking?
E2eNode Suite: [It] [sig-storage] Projected configMap should be consumable from pods in volume [NodeConformance] [Conformance]
[prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv2-node-e2e-conformance/1883037768964116480)
[triage](https://storage.googleapis.com/k8s-triage/index.html?test=Projected%20configMap%20should%20be%20consumable%20from%20pods%20in%20volume%20&xjob=e2e-kops)
### Since when has it been flaking?
[1/12/2025, 11:10:18 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/e2e-ci-kubernetes-e2e-al2023-aws-conformance-aws-cni-canary/1878625531155451904)
[1/13/2025, 12:54:13 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-kind-conformance-parallel-ipv6/1878651451689930752)
[1/13/2025, 10:14:19 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/e2e-ci-kubernetes-e2e-al2023-aws-conformance-aws-cni/1878973829569581056)
[1/16/2025, 1:23:49 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-containerd/1879745924599648256)
[1/23/2025, 7:06:57 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/e2e-ci-kubernetes-e2e-al2023-aws-conformance-cilium-canary/1882369358223642624)
[1/24/2025, 1:27:04 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-containerd/1882645933334728704)
[1/25/2025, 3:24:18 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv2-node-e2e-conformance/1883037768964116480)
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv2-node-e2e-conformance
### Reason for failure (if possible)
```
{ failed [FAILED] expected pod "pod-projected-configmaps-1fcad3d8-8e2c-487f-9ac5-bfb8ed4fd2de" success: Told to stop trying after 4.022s.
pod "pod-projected-configmaps-1fcad3d8-8e2c-487f-9ac5-bfb8ed4fd2de" failed with status:
<v1.PodStatus>:
conditions:
- lastProbeTime: null
lastTransitionTime: "2025-01-25T06:42:06Z"
status: "False"
type: PodReadyToStartContainers
- lastProbeTime: null
lastTransitionTime: "2025-01-25T06:42:03Z"
status: "True"
type: Initialized
- lastProbeTime: null
lastTransitionTime: "2025-01-25T06:42:03Z"
reason: PodFailed
status: "False"
type: Ready
- lastProbeTime: null
lastTransitionTime: "2025-01-25T06:42:03Z"
reason: PodFailed
status: "False"
type: ContainersReady
- lastProbeTime: null
lastTransitionTime: "2025-01-25T06:42:03Z"
status: "True"
type: PodScheduled
containerStatuses:
- containerID: cri-o://12d3bdb5b2382e5b30c55639310647305d8ad42e20d6ac844350b4fc8935e3bf
image: registry.k8s.io/e2e-test-images/agnhost:2.53
imageID: registry.k8s.io/e2e-test-images/agnhost@sha256:1c5d47ecd9c4fca235ec0eeb9af0c39d8dd981ae703805a1f23676a9bf47c3bb
lastState: {}
name: agnhost-container
ready: false
restartCount: 0
started: false
state:
terminated:
containerID: cri-o://12d3bdb5b2382e5b30c55639310647305d8ad42e20d6ac844350b4fc8935e3bf
exitCode: 255
finishedAt: "2025-01-25T06:42:04Z"
reason: Error
startedAt: "2025-01-25T06:42:03Z"
volumeMounts:
- mountPath: /etc/projected-configmap-volume
name: projected-configmap-volume
readOnly: true
recursiveReadOnly: Disabled
hostIP: 10.138.0.14
hostIPs:
- ip: 10.138.0.14
phase: Failed
podIP: 10.85.0.23
podIPs:
- ip: 10.85.0.23
qosClass: BestEffort
startTime: "2025-01-25T06:42:03Z"
In [It] at: k8s.io/kubernetes/test/e2e/framework/pod/output/output.go:282 @ 01/25/25 06:42:07.087
}
```
### Anything else we need to know?
N/A
### Relevant SIG(s)
/sig storage
cc: @kubernetes/release-team-release-signal | sig/storage,kind/flake,needs-triage | low | Critical |
2,812,853,221 | material-ui | CardActionArea does not comply with the HTML5 specification | ### Steps to reproduce
Steps:
1. Open this link to live example: [(MUI Card Docs)](https://mui.com/material-ui/react-card/#primary-action)
2. Open developer tools
3. Make sure that tag `<div>` is placed inside a tag `<button>`, which does not comply to HTML5's specification
Problem:
http://www.w3.org/TR/2012/WD-html5-20120329/the-button-element.html#the-button-element says that a `<button>` must contain only Phrasing content. Phrasing content is defined as including `<span>` but not `<div>`.
### Current behavior
`<CardActionArea>` when rendered becomes a `<button>` tag. If you add anything inside of it, e.g. `<CardContent>` or `<Box>`, it will happen that after rendering, you'll end up with a `<button>` tag, that has `<div>` inside of it.
### Expected behavior
All components from MUI should follow HTML5's validation rules, including `<CardActionArea>`.
### Context
I was using MUI's `<Card>` component, which had a `<CardActionArea>` component inside of it, with child components, such as `<CardHeader>` and `<CardContent>`, then I published my website to the server and tried to check for any HTML validation errors on https://validator.w3.org, which showed me errors related to `<Card>` component from MUI.
### Your environment
<details>
<summary><code>npx @mui/envinfo</code></summary>
```
System:
OS: Windows 11 10.0.22631
Binaries:
Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
npm: 9.6.6 - C:\Program Files\nodejs\npm.CMD
pnpm: Not Found
Browsers:
Chrome: Not Found
Edge: Chromium (127.0.2651.74)
npmPackages:
@emotion/react: ^11.13.3 => 11.14.0
@emotion/styled: ^11.13.0 => 11.14.0
@mui/base: 5.0.0-beta.69
@mui/core-downloads-tracker: 6.4.1
@mui/icons-material: ^6.1.3 => 6.4.1
@mui/lab: ^6.0.0-beta.22 => 6.0.0-beta.24
@mui/material: ^6.1.3 => 6.4.1
@mui/private-theming: 6.4.1
@mui/styled-engine: 6.4.0
@mui/system: 6.4.1
@mui/types: 7.2.21
@mui/utils: 6.4.1
@types/react: ^18.3.11 => 18.3.18
react: ^18.3.1 => 18.3.1
react-dom: ^18.3.1 => 18.3.1
typescript: ^5.7.3 => 5.7.3
```
</details>
**Search keywords**: W3C CardActionArea Card HTML5 SEO | component: card,status: waiting for maintainer | low | Critical |
2,812,857,983 | rust | Tracking issue for release notes of #136127: Allow `*const W<dyn A> -> *const dyn A` ptr cast |
This issue tracks the release notes text for #136127.
### 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, ...)
- [Allow `*const W<dyn A> -> *const dyn A` ptr cast](https://github.com/rust-lang/rust/pull/136127)
````
> [!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 @WaffleLapkin -- origin issue/PR authors and assignees for starting to draft text
| relnotes,needs-triage,relnotes-tracking-issue | low | Minor |
2,812,867,034 | react | [Compiler Bug]: Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client. This can happen if a SSR-ed Client Component used | ### What kind of issue is this?
- [x] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [x] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)
### Link to repro
https://github.com/egorBezmen/next15-styled-components
### Repro steps
1) npm install
2) npm run dev
3) open [localhost](http://localhost:3000)
<img width="1512" alt="Image" src="https://github.com/user-attachments/assets/53f68d57-6c50-4cf7-baf5-5aaf7ac4a7a6" />
https://github.com/vercel/next.js/tree/canary/examples/with-styled-components
I deployed the template project and enabled the option react-compiler
codesandbox - https://codesandbox.io/p/github/egorBezmen/next15-styled-components/main?import=true
### How often does this bug happen?
Every time
### What version of React are you using?
18.3.1 / 19.0.0
### What version of React Compiler are you using?
19.0.0-beta-27714ef-20250124 | Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler | medium | Critical |
2,812,870,399 | vscode | Test: Electron 34 update | Refs: https://github.com/microsoft/vscode/issues/237437
- [ ] macOS @osortega
- [ ] linux @joshspicer
- [x] windows @lszomoru
Complexity: 3
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23238839%0A%0A&assignees=deepak1556)
---
We plan to promote Electron 34 in the February 2025 milestone to insiders. The following tests cover some of the common UI bits that don't have smoke tests. You can download the nightly explorations builds from [here](https://builds.code.visualstudio.com/builds/exploration?released=true&dev=true) for testing.
**Testing:**
* **macOS:**
* Enable Native Tabs (via settings: `window.nativeTabs: true`)
- Ensure native tabs are enabled in the system preferences (System Preferences > General > Prefer tabs: "always":)
- Launch application
- Try opening new window from either command line (code-exploration <path-to-project>) or from the menu entry (Cmd + Shift + N)
- Verify new window is launched as a new tab in the active instance of the application window is focused when starting from command line
- open the code exploration application from finder or dock
- open external terminal
- run code-exploration
- make sure the new window is put to foreground
* Font rendering with non-default family name
- Download and install `Inconsolata ExtraBold` from [font](https://fonts.google.com/specimen/Inconsolata)
- In the editor set `"editor.fontFamily": "Inconsolata ExtraBold"`
- Confirm that the font applies and compare it with insiders
* **windows:**
* verify maximize and restore operations work as expected when OS task bar is auto-hidden for custom titlebar
* Verify titlebar is not clipped off when exiting fullscreen
- Maximize VS Code window
- Press F11 or Ctrl+K Z twice to enter/exit full screen.
- Verify titlebar is not cropped
* **linux:**
* Verify clicking on native menu does not crash the application
- Switch to native title bar `"window.titleBarStyle": "native"`
- Click on any of the menu options `File`, `Edit` etc
* **All OS:**
* Check out the `electron-34.x.y` branch locally and verify you can run out of sources, set a breakpoint and debug using the VS Code launch configurations and VS Code debugger | testplan-item | low | Critical |
2,812,872,165 | flutter | iOS Testflight tester creates Segmentation fault in app | ### Steps to reproduce
Unknown. The testflight tester was spamming buttons in the app trying stuff out and we couldn't find out what caused it. The tester also doesn't remember what action he was doing specifically when it happened.
### Expected results
Of course we would expect the app to keep running and don't crash. regardless of UI conditions I would expect the app to handle it .
### Actual results
The app instantly crashed at some point and a iOS crash dialog was given with the option to share the details with the developer. That will be the crash log that I will attach to this issue.
### 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>
[Crashlog.crash](https://pastebin.com/ANjpvjN3)
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[✓] Flutter (Channel stable, 3.27.3, on macOS 15.2 24C101 darwin-arm64, locale en-US)
• Flutter version 3.27.3 on channel stable at /Users/bertus/Development/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (6 days ago), 2025-01-21 10:32:23 -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.0)
• Android SDK at /Users/bertus/Library/Android/sdk
• Platform android-35, build-tools 35.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
• 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.16.2
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2024.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.11+0-17.0.11b1207.24-11852314)
[✓] VS Code (version 1.96.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.102.0
[✓] Connected device (5 available)
• Noot Noot (mobile) • 00008130-001E748224C1401C • ios • iOS 18.2.1 22C161
• iPhone 16 Pro Max (mobile) • 946AB3E4-8A89-45B0-B86D-39829B9FAF20 • ios • com.apple.CoreSimulator.SimRuntime.iOS-18-2 (simulator)
• macOS (desktop) • macos • darwin-arm64 • macOS 15.2 24C101 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 15.2 24C101 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.267
[✓] Network resources
• All expected network resources are available.
• No issues found!
```
</details>
| in triage | low | Critical |
2,812,880,343 | PowerToys | [Mouse Crosshairs] Implement "Gliding cursor" accessibility feature | ### Description of the new feature / enhancement
A gliding cursor allows someone who can only operate a single switch (or few) to interact with Windows. As a minimum, a single switch (e.g. by using the Microsoft Adaptive Accessories) can be connected to a pc and by sequentially pressing that switch the user can select a target on the screen by combing a "X" and "Y" coordinate on the desktop. This is achieved by having two moving lines running across the desktop, one running left to right, the other top to bottom. To start, the user initiates a vertical line movement by clicking the switch associated with this feature. The line starts running left to right and when the desired position is reached the user clicks again to lock that position vertically. A second, horizonal, line starts running across the desktop top to bottom. When the desired position for that line is reached, the user clicks the switch once more to create an exact position on the desktop at which the feature will perform a selection (single/double mouse click).
The existing Crosshair functionality in the Mouse utilities already offers quite a lot of the required properties. The idea would be to implement this new tool as an extension of that "Mouse Pointer Crosshairs" feature.
This is a very popular, existing feature in iOS. Hereby a video showing the feature in use:
https://youtu.be/HBo2BZ-Zzwg?si=ctQXnRakhxv8HfTZ&t=115/
### Scenario when this would be used?
This scenario would be used by developers/(power) users that have a mobility related accessibility requirement.
### Supporting information
See video for an already well-proven scenario in iOS. It's a reoccurring ask to have a way to control Windows with a single switch. In the future this feature could be further extended to support multiple switches in case the user is able to work with more than a single switch. However, the implementation described above provides a basic implementation.
https://github.com/user-attachments/assets/7716cb34-7678-40a8-9803-0daeed229b24 | Needs-Triage,Product-Mouse Utilities | low | Minor |
2,812,902,377 | vscode | Ability to associate esoteric extensions with existing file types | <!-- ⚠️⚠️ 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. -->
It would be nice if there was an ability to “map” extensions with an existing file type, similarly the way you can map extensions to a language using the `files.associations` configuration option.
For example, I like to do some retro programming of PlayStation 1 games. The PlayStation 1 had its own native file formats, such as:
* `STR` for streaming data (videos)
* `TIM` for textured images
* `VB`/`VH` for audio samples
Given these are highly specific, they just show a default “text file” icon in the Explorer. It would nice if we could get a configuration option to indicate what type of files they are, though. Something like:
```json
"files.types": {
"str": "video",
"tim": "image",
"vb": "audio",
"vh": "audio"
}
```
I did look into this, but it seems the current way to address this is to create a custom extension. This seems impractical, due to:
* The huge barrier to creating an extension in the first place.
* It’s only a small number of file extensions I’m interested in.
* I have to bundle an existing file icon theme’s icons into _my_ extension, which is inefficient for less than half a dozen file types.
I’m not asking for these file types to be _supported_ by the Visual Studio Code editor, but just think it would be a nice quality of life improvement to be able to tell Code what type of files they are so they get an appropriate icon. For example, the Explorer shows a speaker icon for `*.mp3` files and a play icon for `*.mp4` files in the Explorer, despite Code not being able to open and play MP3 and MP4 files out of the box. | triage-needed | low | Minor |
2,812,903,740 | storybook | [Bug]: Global CSS bleeds between preloaded stories | ### Describe the bug
Storybook’s preloading mechanism currently preloads the first story in a story file when the Storybook instance is initialized. Additionally, hovering over other stories triggers their preloading. However, this functionality has introduced an issue where global CSS (non-modularized styles) from preloaded stories persists and bleeds into the current story, leading to unintended style conflicts.
### Reproduction link
-
### Reproduction steps
1. Create a Storybook with two stories. The second one should import a css file with global CSS (e.g. background: red)
2. Visit the first story and now hover over the second one. -> CSS of the preloading bleeds into the first one
### System
```bash
-
```
### Additional context
_No response_ | bug | low | Critical |
2,812,907,126 | kubernetes | [Flaking Test] [sig-node] E2eNode Suite.[It] [sig-node] [NodeConformance] Containers Lifecycle when Running a pod with init containers and regular containers | ### Which jobs are flaking?
master-blocking
- ci-crio-cgroupv2-node-e2e-conformance
### Which tests are flaking?
E2eNode Suite.[It] [sig-node] [NodeConformance] Containers Lifecycle when Running a pod with init containers and regular containers, restartPolicy=Never when A regular container has a PreStop hook when A regular container fails a liveness probe when a pod is terminating because its liveness probe fails should continue running liveness probes for restartable init containers and restart them while in preStop [NodeConformance]
[prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1883458293720944640)
[triage](https://storage.googleapis.com/k8s-triage/index.html?test=Containers%20Lifecycle%20when%20Running%20a%20pod%20with%20init%20containers%20and%20regular%20containers%2C%20restartPolicy%3DNever%20when%20A%20regular%20container%20has%20a%20PreStop%20hook%20when%20A%20regular%20container%20fails%20a%20liveness%20probe%20when%20a%20pod%20is%20terminating%20because%20its%20liveness%20probe%20fails%20should%20continue%20running%20liveness%20probes%20for%20restartable%20init%20containers%20and%20restart%20them%20while%20in%20preStop&xjob=e2e-kops)
### Since when has it been flaking?
[1878741797895671808 1/13/2025, 6:52:56 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1878741797895671808)
[1879195290896961536 1/14/2025, 12:54:56 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1879195290896961536)
[1880873097419034624 1/19/2025, 4:01:58 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1880873097419034624)
[1881916482472906752 1/22/2025, 1:07:59 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1881916482472906752)
[1882868904884178944 1/24/2025, 4:12:44 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1882868904884178944)
[1883458293720944640 1/26/2025, 7:14:44 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1883458293720944640)
### Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv2-node-e2e-conformance
### Reason for failure (if possible)
```
{ failed [FAILED] Expected an error to have occurred. Got:
<nil>: nil
In [It] at: k8s.io/kubernetes/test/e2e_node/container_lifecycle_test.go:941 @ 01/26/25 10:32:58.877
}
```
### Anything else we need to know?
N/A
### Relevant SIG(s)
/sig node
cc: @kubernetes/release-team-release-signal | sig/node,kind/flake,needs-triage | low | Critical |
2,812,945,973 | rust | Tracking Issue for short backtraces in the default panic hook | This is a tracking issue for short backtraces in the default panic hook (https://github.com/rust-lang/compiler-team/issues/818). See [previous Zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/233931-t-compiler.2Fmajor-changes/topic/Use.20debuginfo.20for.20short.20backtrace.20printing.20compiler-tea.2E.2E.2E).
### 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
#### Compile-time
- [ ] Parse, validate, and emit the new `#[rustc_{skip,start,end}_short_backtrace]` attributes in rustc itself (https://github.com/rust-lang/rust/pull/134831). Currently blocked on everything else.
- [ ] Extend LLVM to emit the appropriate debuginfo (https://github.com/llvm/llvm-project/pull/123683)
- [ ] Waiting on [pre-RFC](https://discourse.llvm.org/t/adding-short-backtrace-debuginfo/84187)
- [ ] Extend rustc_codegen_cranelift to emit the appropriate debuginfo (https://github.com/rust-lang/rust/pull/134831). Blocked.
- [ ] Extend rustc_codegen_gcc to emit the appropriate debuginfo. Waiting on me or Antoyo to implement it.
#### Runtime
- [ ] Extend either addr2line or gimli to give backtrace-rs a way to find the appropriate debuginfo (https://github.com/gimli-rs/gimli/pull/756). Waiting on me to rework the API in response to review comments.
- [ ] Update backtrace-rs to pass the debuginfo through to libstd (https://github.com/rust-lang/backtrace-rs/pull/693). Waiting on the gimli PR and for me to have time to debug this on macOS.
- [ ] Update the default panic hook to use the debuginfo (https://github.com/rust-lang/rust/pull/134831). Blocked on everything else.
[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
- How should we represent the debuginfo at runtime? The current three-state enum doesn't allow both marking a frame as the end of a push/pop pair while also omitting it in the backtrace. **NOTE: please leave comments about this on [LLVM discourse](https://discourse.llvm.org/t/adding-short-backtrace-debuginfo/84187/7), not on this issue.**
- How can we extend this to PDB? Right now it only works for DWARF. Possibly we can [use `llvm.codeview.annotation`](https://rust-lang.zulipchat.com/#narrow/stream/317568-t-compiler.2Fwg-debugging/topic/extend.20PDB.3F)?
### Implementation history
See above.
@rustbot label T-compiler T-libs A-runtime A-backtrace A-debuginfo | A-runtime,A-debuginfo,T-compiler,C-tracking-issue,T-libs,A-backtrace | low | Critical |
2,812,953,521 | flutter | Flutter commands no longer work if a branch is cloned with `--single-branch` | ### Steps to reproduce
I have a GitHub action for cloning Flutter to run tests. The test run on various different branches but to save time/space only the branch being tested is cloned (the other branches run in different jobs) using `--single-branch`.
This used to work fine, but recently has stopped working because Flutter assumes it can access `origin/master`.
To repro:
1. Run `git clone --single-branch --branch beta https://github.com/flutter/flutter` to clone the beta branch without all others
2. Run `./flutter_beta/bin/flutter doctor`
### Expected results
`flutter doctor` should run successfully.
### Actual results
```
PS D:\Temp> ./flutter_beta/bin/flutter doctor
fatal: Not a valid object name origin/master
Error: Unable to determine engine version...
```
### Code sample
N/A
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
</details>
### Logs
<details open><summary>Logs</summary>
Unable to get any verbose logs:
```console
PS D:\Temp> ./flutter_beta/bin/flutter doctor -v
fatal: Not a valid object name origin/master
Error: Unable to determine engine version...
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
Unable to run:
```console
PS D:\Temp> ./flutter_beta/bin/flutter doctor -v
fatal: Not a valid object name origin/master
Error: Unable to determine engine version...
```
</details>
| team-infra,monorepo | low | Critical |
2,812,960,489 | godot | Tool Script get_string_size() Discrepancy for "♯" Between Editor Inspection and Scene Execution | ### Tested versions
Godot v4.4.beta1
### System information
Windows 11 (build 22631) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2050 (NVIDIA; 32.0.15.6109) - 12th Gen Intel(R) Core(TM) i5-12500H (16 threads)
### Issue description
When a `@tool` script calls get_theme_default_font().get_string_size("♯"), it returns correct metrics (16.0, 23.0) during editor inspection (with script actively running as a tool), but shows reduced width (7.0, 23.0) during scene execution (via Play Scene button or exported build). Regular characters (e.g., "A","C","B") remain consistent across both modes.
### Steps to reproduce
```gdscript
@tool
extends Control
func _process(delta: float) -> void:
var special_char_size = get_theme_default_font().get_string_size("♯", HORIZONTAL_ALIGNMENT_CENTER)
var regular_char_size = get_theme_default_font().get_string_size("ACB", HORIZONTAL_ALIGNMENT_CENTER)
print("Font metrics - Special: %s %s | Regular: %s" % [
get_theme_default_font().font_name,
special_char_size,
regular_char_size
])
```
Editor (Output example: Open Sans SemiBold (16.0, 23.0) | (32.0, 23.0))
Runtime (Example: Open Sans SemiBold (7.0, 23.0) | (32.0, 23.0))
### Minimal reproduction project (MRP)
N/A | topic:editor,needs testing,topic:gui | low | Minor |
2,812,963,695 | storybook | [Bug]: addon-storysource doesn't display the full source when using Vite | ### Describe the bug
I am using storybook v8.5.1. When using Vite as a framework and this addon - @storybook/addon-storysource I am not able to see the the full source code.
This is similar to https://github.com/storybookjs/storybook/issues/29478, and the issue was fixed in https://github.com/storybookjs/storybook/pull/29669, but this only seems to have fixed it for webpack as framework and not Vite.
<p>Using Vite:</p>
<img src="https://github.com/user-attachments/assets/d52376fc-ad6c-492b-9ea3-f9a6b74dcf62" width="300" height="300" alt="Using Vite" title="Using Vite" />
<p>Using Webpack:</p>
<img src="https://github.com/user-attachments/assets/bcc42547-ed53-4476-94ef-e74e0711a3af" width="300" height="300" alt="Using Webpack" title="Using Webpack" />
Storybook Version : ^8.5.1
### Reproduction link
https://stackblitz.com/edit/github-h25xa6-fqssm5jb?file=package.json
### Reproduction steps
1. To see the results of using webpack, go to .storybook/main.ts
2. Uncomment the commented lines and remove "@storybook/react-vite" from the framework config.
### System
```bash
System:
OS: Windows 11 10.0.26100
CPU: (12) x64 Intel(R) Core(TM) 7 150U
Binaries:
Node: 20.12.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
npm: 10.5.1 - C:\Program Files\nodejs\npm.CMD <----- active
pnpm: 9.6.0 - ~\AppData\Roaming\npm\pnpm.CMD
Browsers:
Edge: Chromium (132.0.2957.115)
npmPackages:
@storybook/addon-essentials: ^8.5.1 => 8.5.1
@storybook/addon-interactions: ^8.5.1 => 8.5.1
@storybook/addon-onboarding: ^8.5.1 => 8.5.1
@storybook/addon-storysource: ^8.5.1 => 8.5.1
@storybook/addon-webpack5-compiler-swc: ^2.0.0 => 2.0.0
@storybook/blocks: ^8.5.1 => 8.5.1
@storybook/react: ^8.5.1 => 8.5.1
@storybook/react-vite: ^8.5.1 => 8.5.1
@storybook/react-webpack5: ^8.5.1 => 8.5.1
@storybook/test: ^8.5.1 => 8.5.1
eslint-plugin-storybook: ^0.11.2 => 0.11.2
storybook: ^8.5.1 => 8.5.1
```
### Additional context
_No response_ | bug,needs triage | low | Critical |
2,812,997,362 | rust | PowerPC linker warning: `bss-plt forced due to {name}.o` | Originally noted in https://github.com/rust-lang/rust/issues/136096#issuecomment-2615051447 when building `libc`, PowerPC can emit the following linker warning:
```text
warning: linker stderr: /usr/lib/gcc-cross/powerpc-linux-gnu/13/../../../../powerpc-linux-gnu/bin/ld: bss-plt forced due to /checkout/target/powerpc-unknown-linux-gnu/debug/deps/const_fn-5906628da0f5d31e.2bjw3mlsf69tu9e94ehzuvs4u.rcgu.o
```
I also noticed this previously in `compiler_builtins` https://github.com/rust-lang/compiler-builtins/pull/667.
https://sourceware.org/binutils/docs/ld/PowerPC-ELF32.html says the following:
> --bss-plt
> Current PowerPC GCC accepts a ‘-msecure-plt’ option that generates code capable of using a newer PLT and GOT layout that has the security advantage of no executable section ever needing to be writable and no writable section ever being executable. PowerPC ld will generate this layout, including stubs to access the PLT, if all input files (including startup and static libraries) were compiled with ‘-msecure-plt’. ‘--bss-plt’ forces the old BSS PLT (and GOT layout) which can give slightly better performance.
>
> --secure-plt
> ld will use the new PLT and GOT layout if it is linking new ‘-fpic’ or ‘-fPIC’ code, but does not do so automatically when linking non-PIC code. This option requests the new PLT and GOT layout. A warning will be given if some object file requires the old style BSS PLT.
It sounds like `secure-plt` is the default but something about our object files forces a fallback to `bss-plt`.
<!-- TRIAGEBOT_START -->
<!-- TRIAGEBOT_ASSIGN_START -->
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"taiki-e"}$$TRIAGEBOT_ASSIGN_DATA_END -->
<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END --> | T-compiler,O-PowerPC,C-bug,O-linux-gnu,A-linkers,L-linker_messages | low | Critical |
2,813,022,635 | go | google.golang.org/protobuf: TestIntegration/Go1.23.0/LazyDecoding failures | ```
#!watchflakes
default <- pkg == "google.golang.org/protobuf" && test == "TestIntegration/Go1.23.0/LazyDecoding"
```
Issue created automatically to collect these failures.
Example ([log](https://ci.chromium.org/b/8724857908926834257)):
=== RUN TestIntegration/Go1.23.0/LazyDecoding
integration_test.go:148: executing (go1.23.0 test ./proto -test_lazy_unmarshal): exit status 1
--- FAIL: TestHasExtensionNoAlloc (0.00s)
--- FAIL: TestHasExtensionNoAlloc/Eager (0.00s)
extension_test.go:157: proto.HasExtension should not allocate, but allocated 1.00x per run
FAIL
FAIL google.golang.org/protobuf/proto 0.179s
FAIL
--- FAIL: TestIntegration/Go1.23.0/LazyDecoding (5.61s)
— [watchflakes](https://go.dev/wiki/Watchflakes)
| NeedsInvestigation | low | Critical |
2,813,022,834 | flutter | crash in ios | ```
version=3.6.1 (stable) (Tue Jan 7 09:50:00 2025 -0800) on "ios_arm64"
pid=39791, thread=32771, isolate_group=main(0x116c72800), isolate=main(0x110549000)
os=ios, arch=arm64, comp=no, sim=no
isolate_instructions=11777b5a0, vm_instructions=11777b5a0
fp=16b9efb80, sp=16b9efb60, pc=1181cd87c
pc 0x00000001181cd87c fp 0x000000016b9efb80 Dart_DumpNativeStackTrace+0x18
pc 0x0000000117d7eed0 fp 0x000000016b9efba0 dart::Assert::Fail(char const*, ...) const+0x30
pc 0x0000000117eb509c fp 0x000000016b9f0000 dart::OSThread::Start(char const*, void (*)(unsigned long), unsigned long)+0xf8
pc 0x0000000117f48050 fp 0x000000016b9f0460 dart::ThreadPool::RunImpl(std::_fl::unique_ptr<dart::ThreadPool::Task, std::_fl::default_delete<dart::ThreadPool::Task>>)+0x100
pc 0x0000000117e2cd08 fp 0x000000016b9f04a0 dart::NativeMessageHandler::PostMessage(std::_fl::unique_ptr<dart::Message, std::_fl::default_delete<dart::Message>>, bool)+0x60
pc 0x0000000117eb70e8 fp 0x000000016b9f04d0 dart::PortMap::PostMessage(std::_fl::unique_ptr<dart::Message, std::_fl::default_delete<dart::Message>>, bool)+0x9c
pc 0x00000001181cd914 fp 0x000000016b9f09d0 dart::PostCObjectHelper(long long, _Dart_CObject*)+0x78
pc 0x0000000117d030e0 fp 0x000000016b9f0b90 dart::bin::CertificateVerificationCallback(ssl_st*, unsigned char*)+0x428
pc 0x0000000117ccf33c fp 0x000000016b9f0be0 bssl::ssl_verify_peer_cert(bssl::SSL_HANDSHAKE*)+0x5c
pc 0x0000000117cd0c2c fp 0x000000016b9f0f40 bssl::ssl_client_handshake(bssl::SSL_HANDSHAKE*)+0x990
pc 0x0000000117cdeaa8 fp 0x000000016b9f0fc0 SSL_do_handshake+0x1dc
pc 0x0000000117cf9148 fp 0x000000016b9f0ff0 dart::bin::SSLFilter::Handshake(long long)+0x20
pc 0x0000000117cf9278 fp 0x000000016b9f1020 dart::bin::Builtin_SecureSocket_Handshake(_Dart_NativeArguments*)+0x50
pc 0x0000000117e2c648 fp 0x000000016b9f1090 dart::NativeEntry::AutoScopeNativeCallWrapperNoStackCheck(_Dart_NativeArguments*, void (*)(_Dart_NativeArguments*))+0x198
pc 0x000000011a5037f0 fp 0x000000016b9f10d0 Unknown symbol
pc 0x000000013f6a3678 fp 0x000000016b9f1118 Unknown symbol
pc 0x000000015132c780 fp 0x000000016b9f11c8 Unknown symbol
pc 0x000000013f6a2e54 fp 0x000000016b9f1238 Unknown symbol
pc 0x000000014f0c8880 fp 0x000000016b9f12e8 Unknown symbol
pc 0x000000014f0a22a4 fp 0x000000016b9f1330 Unknown symbol
pc 0x000000014f0929a8 fp 0x000000016b9f13c8 Unknown symbol
pc 0x000000014d9a9250 fp 0x000000016b9f1420 Unknown symbol
pc 0x000000014d99f0c8 fp 0x000000016b9f14b0 Unknown symbol
pc 0x000000014d9a7040 fp 0x000000016b9f1530 Unknown symbol
pc 0x000000014d9a3054 fp 0x000000016b9f1598 Unknown symbol
pc 0x0000000145a03920 fp 0x000000016b9f15f0 Unknown symbol
pc 0x000000014f0cc0fc fp 0x000000016b9f1628 Unknown symbol
pc 0x000000011a50d4e0 fp 0x000000016b9f1658 Unknown symbol
pc 0x000000014f0a22a4 fp 0x000000016b9f16a0 Unknown symbol
pc 0x000000014f0929a8 fp 0x000000016b9f1738 Unknown symbol
pc 0x000000014d9a9250 fp 0x000000016b9f1790 Unknown symbol
pc 0x000000014d99f0c8 fp 0x000000016b9f1820 Unknown symbol
pc 0x000000014d9a7040 fp 0x000000016b9f18a0 Unknown symbol
pc 0x000000014d9a3054 fp 0x000000016b9f1908 Unknown symbol
pc 0x0000000145a03920 fp 0x000000016b9f1960 Unknown symbol
pc 0x000000014f0bedd0 fp 0x000000016b9f1998 Unknown symbol
pc 0x000000014f0afb1c fp 0x000000016b9f1a38 Unknown symbol
pc 0x000000014f0a8d4c fp 0x000000016b9f1a88 Unknown symbol
pc 0x000000014f0834ac fp 0x000000016b9f1b38 Unknown symbol
pc 0x000000014f0af2f0 fp 0x000000016b9f1b70 Unknown symbol
pc 0x000000014f0c8048 fp 0x000000016b9f1bd8 Unknown symbol
pc 0x000000014f0b19c4 fp 0x000000016b9f1c00 Unknown symbol
pc 0x000000011a503af4 fp 0x000000016b9f1cd0 Unknown symbol
pc 0x0000000117dcda98 fp 0x000000016b9f1d60 dart::DartEntry::InvokeFunction(dart::Function const&, dart::Array const&, dart::Array const&)+0x210
pc 0x00000001181c7304 fp 0x000000016b9f1e70 Dart_InvokeClosure+0x4f4
pc 0x0000000117d1dd4c fp 0x000000016b9f1f00 tonic::DartMicrotaskQueue::RunMicrotasks()+0xd4
pc 0x00000001177f3b00 fp 0x000000016b9f1fe0 fml::MessageLoopImpl::FlushTasks(fml::FlushType)+0x3ec
pc 0x00000001177f7ac4 fp 0x000000016b9f2000 fml::MessageLoopDarwin::OnTimerFire(__CFRunLoopTimer*, fml::MessageLoopDarwin*)+0x20
pc 0x000000018d4d6894 fp 0x000000016b9f2010 <redacted>+0x20
pc 0x824880018d4d6538 fp 0x000000016b9f20d0 <redacted>+0x82488000000003f4
pc 0x0b0e00018d4d608c fp 0x000000016b9f2130 <redacted>+0xb0e000000000120
pc 0x8e4780018d4753b4 fp 0x000000016b9f2ea0 <redacted>+0x8e47800000000740
pc 0x8d6c00018d474830 fp 0x000000016b9f2f30 CFRunLoopRunSpecific+0x8d6c00000000024c
pc 0x14720001177f7bb0 fp 0x000000016b9f2f70 fml::MessageLoopDarwin::Run()+0x1472000000000058
pc 0x00000001177f6cb0 fp 0x000000016b9f2fa0 std::_fl::__function::__func<fml::Thread::Thread(std::_fl::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0, std::_fl::allocator<fml::Thread::Thread(std::_fl::function<void (fml::Thread::ThreadConfig const&)> const&, fml::Thread::ThreadConfig const&)::$_0>, void ()>::operator()()+0xb4
pc 0x00000001177f69c0 fp 0x000000016b9f2fc0 fml::ThreadHandle::ThreadHandle(std::_fl::function<void ()>&&)::$_0::__invoke(void*)+0x24
pc 0x00000002159a937c fp 0x000000016b9f2fe0 _pthread_start+0x88
-- End of DumpStackTrace
pc 0x0000000000000000 fp 0x000000016b9f10d0 sp 0x0000000000000000 [Stub] CallAutoScopeNative
pc 0x000000013f6a3678 fp 0x000000016b9f1118 sp 0x000000016b9f10e0 [Unoptimized] _SecureFilterImpl@15069316._handshake@15069316
pc 0x000000015132c780 fp 0x000000016b9f11c8 sp 0x000000016b9f1128 [Optimized] [email protected]
pc 0x000000013f6a2e54 fp 0x000000016b9f1238 sp 0x000000016b9f11d8 [Unoptimized] _RawSecureSocket@15069316._secureHandshake@15069316
pc 0x000000014f0c8880 fp 0x000000016b9f12e8 sp 0x000000016b9f1248 [Optimized] _RawSecureSocket@15069316._tryFilter@15069316
pc 0x000000014f0a22a4 fp 0x000000016b9f1330 sp 0x000000016b9f12f8 [Optimized] _SuspendState@[email protected]
pc 0x000000014f0929a8 fp 0x000000016b9f13c8 sp 0x000000016b9f1340 [Optimized] _rootRunUnary@5048458
pc 0x000000014d9a9250 fp 0x000000016b9f1420 sp 0x000000016b9f13d8 [Optimized] _rootRunUnary@5048458
pc 0x000000014d99f0c8 fp 0x000000016b9f14b0 sp 0x000000016b9f1430 [Optimized] [email protected]
pc 0x000000014d9a7040 fp 0x000000016b9f1530 sp 0x000000016b9f14c0 [Optimized] _Future@[email protected]
pc 0x000000014d9a3054 fp 0x000000016b9f1598 sp 0x000000016b9f1540 [Optimized] _Future@5048458._propagateToListeners@5048458
pc 0x0000000145a03920 fp 0x000000016b9f15f0 sp 0x000000016b9f15a8 [Optimized] _Future@5048458._completeWithValue@5048458
pc 0x000000014f0cc0fc fp 0x000000016b9f1628 sp 0x000000016b9f1600 [Optimized] _SuspendState@5048458._returnAsyncNotFuture@5048458
pc 0x000000011a50d4e0 fp 0x000000016b9f1658 sp 0x000000016b9f1638 [Stub] ReturnAsyncNotFuture
pc 0x000000014f0a22a4 fp 0x000000016b9f16a0 sp 0x000000016b9f1668 [Optimized] _SuspendState@[email protected]
pc 0x000000014f0929a8 fp 0x000000016b9f1738 sp 0x000000016b9f16b0 [Optimized] _rootRunUnary@5048458
pc 0x000000014d9a9250 fp 0x000000016b9f1790 sp 0x000000016b9f1748 [Optimized] _rootRunUnary@5048458
pc 0x000000014d99f0c8 fp 0x000000016b9f1820 sp 0x000000016b9f17a0 [Optimized] [email protected]
pc 0x000000014d9a7040 fp 0x000000016b9f18a0 sp 0x000000016b9f1830 [Optimized] _Future@[email protected]
pc 0x000000014d9a3054 fp 0x000000016b9f1908 sp 0x000000016b9f18b0 [Optimized] _Future@5048458._propagateToListeners@5048458
pc 0x0000000145a03920 fp 0x000000016b9f1960 sp 0x000000016b9f1918 [Optimized] _Future@5048458._completeWithValue@5048458
pc 0x000000014f0bedd0 fp 0x000000016b9f1998 sp 0x000000016b9f1970 [Optimized] _Future@5048458._asyncCompleteWithValue@5048458.<anonymous closure>
pc 0x000000014f0afb1c fp 0x000000016b9f1a38 sp 0x000000016b9f19a8 [Optimized] _rootRun@5048458
pc 0x000000014f0a8d4c fp 0x000000016b9f1a88 sp 0x000000016b9f1a48 [Optimized] _rootRun@5048458
pc 0x000000014f0834ac fp 0x000000016b9f1b38 sp 0x000000016b9f1a98 [Optimized] [email protected]
pc 0x000000014f0af2f0 fp 0x000000016b9f1b70 sp 0x000000016b9f1b48 [Optimized] [email protected].<anonymous closure>
pc 0x000000014f0c8048 fp 0x000000016b9f1bd8 sp 0x000000016b9f1b80 [Optimized] _startMicrotaskLoop@5048458
pc 0x000000014f0b19c4 fp 0x000000016b9f1c00 sp 0x000000016b9f1be8 [Optimized] _startMicrotaskLoop@5048458
pc 0x000000011a503af4 fp 0x000000016b9f1cd0 sp 0x000000016b9f1c10 [Stub] InvokeDartCode
```
flutter doctor -v
[✓] Flutter (Channel stable, 3.27.3, on macOS 15.2 24C101 darwin-arm64, locale en-IN)
• Flutter version 3.27.3 on channel stable at /Users/sahilyadav/Devlopment/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision c519ee916e (6 days ago), 2025-01-21 10:32:23 -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.0)
• Android SDK at /Users/sahilyadav/Library/Android/sdk
• Platform android-35, build-tools 35.0.0
• Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
• 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.16.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.3+-79915917-b509.11)
[✓] VS Code (version 1.96.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] VS Code (version 1.96.4)
• VS Code at /Applications/Visual Studio Code 2.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (4 available)
• Sahil’s iPhone (mobile) • 00008120-001208492632201E • ios • iOS 18.1.1 22B91
• macOS (desktop) • macos • darwin-arm64 • macOS 15.2 24C101 darwin-arm64
• Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin • macOS 15.2 24C101 darwin-arm64
• Chrome (web) • chrome • web-javascript • Google Chrome 131.0.6778.265
! Error: Browsing on the local area network for Nitin’s 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)
[✓] Network resources
• All expected network resources are available.
• No issues found! | waiting for customer response,in triage | low | Critical |
2,813,058,678 | rust | Linker error on `rustc 1.86.0-nightly (f85c6de55 2025-01-26)` when cross compiling to aarch64-unknown-linux-musl | <!--
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.
-->
This got caught in CI: https://github.com/VorpalBlade/chezmoi_modify_manager/actions/runs/12986156450/job/36212410530?pr=199
```
error: linker stderr: + set -euo pipefail
+ main /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crt1.o /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crti.o /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtbegin.o /tmp/rustc0hitcJ/symbols.o /target/aarch64-unknown-linux-musl/debug/deps/chezmoi_modify_manager-275fe4f1229fe0b5.chezmoi_modify_manager.bf3b72a79421d7fe-cgu.0.rcgu.o /target/aarch64-unknown-linux-musl/debug/deps/chezmoi_modify_manager-275fe4f1229fe0b5.6fob8bpx2xd6fn8sx491p6kj1.rcgu.o -Wl,--as-needed -Wl,-Bstatic /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libtest-11282d3042c776ef.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libgetopts-8e527476f1f9fe91.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libunicode_width-313605a911a9091b.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_std_workspace_std-51da7124742587ac.rlib /target/aarch64-unknown-linux-musl/debug/deps/libenv_logger-88d34597e58a95df.rlib /target/aarch64-unknown-linux-musl/debug/deps/libenv_filter-6dd72dd7771b7fdc.rlib /target/aarch64-unknown-linux-musl/debug/deps/libchezmoi_modify_manager-6bff196573e59d99.rlib /target/aarch64-unknown-linux-musl/debug/deps/librpassword-c244550bd340835c.rlib /target/aarch64-unknown-linux-musl/debug/deps/librtoolbox-a629d113d4b65b60.rlib /target/aarch64-unknown-linux-musl/debug/deps/libglob-a4478ddc7a4dcec7.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwhich-fa7324817b67b6d3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libenv_home-a25dd0e8ef8bcf6f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libduct-adf2213d5d5c2b0e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libos_pipe-c16c1d25fca50dc3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libshared_child-0d6f611a3b58452c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libself_update-27a42f63f4b4511a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtar-59d3c56eab515de1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libxattr-ecd9991e4541268e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfiletime-2e7bd2a5e9fda504.rlib /target/aarch64-unknown-linux-musl/debug/deps/libflate2-64dfe788273a6bb1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libminiz_oxide-35b9f9542b66ae06.rlib /target/aarch64-unknown-linux-musl/debug/deps/libadler2-d7cf2809abdf611c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcrc32fast-98bceea7851cb9af.rlib /target/aarch64-unknown-linux-musl/debug/deps/liburlencoding-1c24d421f27fcd94.rlib /target/aarch64-unknown-linux-musl/debug/deps/libquick_xml-a50e3cc405bb1a6c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libreqwest-1e0df6c61f891001.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbase64-f5dc79f2814d476c.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustls_pemfile-55a38c5af4c8a1ef.rlib /target/aarch64-unknown-linux-musl/debug/deps/libipnet-8f0fecddb7d7970f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhyper_rustls-f8b366625087ccc6.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwebpki_roots-02c812fa8e028280.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtokio_rustls-c5d51910b465f306.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustls-012f8dc40b3a3e05.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwebpki-330065566b272c41.rlib /target/aarch64-unknown-linux-musl/debug/deps/libring-4c24cc3629d3466d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libspin-99e2a721fd934565.rlib /target/aarch64-unknown-linux-musl/debug/deps/libuntrusted-b5c0d0504706005e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzeroize-2ddffe546160833f.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustls_pki_types-2ed44ac81a624647.rlib /target/aarch64-unknown-linux-musl/debug/deps/libserde_urlencoded-63126f7e8facd2ea.rlib /target/aarch64-unknown-linux-musl/debug/deps/libserde_json-fea65d703100598e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libryu-26c3d660cf6e0be8.rlib /target/aarch64-unknown-linux-musl/debug/deps/libserde-988728016363ee90.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtower-a18f9d43a3523709.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsync_wrapper-2fb303f6a1d598c3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtower_layer-2416d81df265434d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhyper_util-f30cf0b40d60be4a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtower_service-88c6c59d0d8d0b64.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhyper-311870162ca34c30.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwant-5d14bb1a02d97be2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtry_lock-713799e847adb393.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttparse-0a55bda6cb9c150c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libh2-9854a4f9aacb26cb.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtracing-35ef49265900271b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtracing_core-c400556172631c50.rlib /target/aarch64-unknown-linux-musl/debug/deps/libindexmap-d96e06ddc09ddd70.rlib /target/aarch64-unknown-linux-musl/debug/deps/libequivalent-6b18beb2376b7663.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhashbrown-d35e156a772522a2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libatomic_waker-ec119f4bf762f683.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtokio_util-36db6b551552763f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_channel-b040ed76df724254.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtokio-e752437702e71926.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsocket2-89fe9cda98a6e624.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmio-183e147343a75a0a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttp_body_util-a2509902d0e281fe.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttp_body-c5617f705fbd7516.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_util-e388f8b098262c8c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_io-04316109944f8785.rlib /target/aarch64-unknown-linux-musl/debug/deps/libslab-ec17825b8c5e64d0.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpin_project_lite-1ec7c40ff6bd1c69.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_sink-fe06589f9d096f97.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_task-fcd6e91835f13596.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpin_utils-5ae43a724a1a4586.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_core-0e0518818326709b.rlib /target/aarch64-unknown-linux-musl/debug/deps/liburl-c9c17ed6acf24b47.rlib /target/aarch64-unknown-linux-musl/debug/deps/libidna-fa0e8c6d8b591e88.rlib /target/aarch64-unknown-linux-musl/debug/deps/libidna_adapter-3f7e433ae93d8aa3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_normalizer-c215d3739752bd97.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_normalizer_data-9338dbfbc9f04a58.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwrite16-d0d06f96f2c4eae5.rlib /target/aarch64-unknown-linux-musl/debug/deps/libutf8_iter-b7dedb7b5954d701.rlib /target/aarch64-unknown-linux-musl/debug/deps/libutf16_iter-663db2246e41f6c0.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsmallvec-40c35139d7277050.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_properties-6bc4d605ad418160.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_properties_data-5a76001dc44a3259.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_locid_transform-6f6d139b351d2665.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_locid_transform_data-2c97e2da407d4c0c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_collections-5fc88492990936ad.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_provider-20ebb20ddb59b380.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_locid-bb9ab788ff2d5ffd.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblitemap-88236c9a046e7939.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtinystr-adc4405d2f83a93b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzerovec-fe19fb5b5024a1f7.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwriteable-526d295315c33404.rlib /target/aarch64-unknown-linux-musl/debug/deps/libyoke-aa436aa723ebef47.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzerofrom-a1d33568cadc8d47.rlib /target/aarch64-unknown-linux-musl/debug/deps/libstable_deref_trait-dd4f1e3dab203d37.rlib /target/aarch64-unknown-linux-musl/debug/deps/libform_urlencoded-778cfd10439c3fd8.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpercent_encoding-bd6fd8050ca738ac.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttp-6dc7762fd73534ab.rlib /target/aarch64-unknown-linux-musl/debug/deps/libitoa-6a132b9c42273f48.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbytes-ed56f1f75b5d8e94.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfnv-d4a440f237839fae.rlib /target/aarch64-unknown-linux-musl/debug/deps/libindicatif-9cb95163f2199643.rlib /target/aarch64-unknown-linux-musl/debug/deps/libportable_atomic-e422ea85c9e06e1e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnumber_prefix-3830a3467ebae53e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libconsole-5937a745d923dc03.rlib /target/aarch64-unknown-linux-musl/debug/deps/libunicode_width-46380feb0c6d652c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libself_replace-50855f7e704fdc78.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtempfile-c3f8aa6ff2f6318e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfastrand-e1f677de8d996655.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustix-745502aa14383bf9.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbitflags-5b5fa851c43f2de5.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblinux_raw_sys-3d98cb974913b37b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmedic-1f299f646e450e46.rlib /target/aarch64-unknown-linux-musl/debug/deps/libos_info-6f9369e29fa20e38.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustc_version_runtime-92267d77ca178f81.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustc_version-3b4f12fa64defc48.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsemver-0ca1b6f959189493.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstream-12e26d093e2d6d15.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstyle_query-8366fef9b2f1f512.rlib /target/aarch64-unknown-linux-musl/debug/deps/libis_terminal_polyfill-6086d127fd034c07.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcolorchoice-8f6a567228987a9e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstyle_parse-d3aa862edcdf6ddd.rlib /target/aarch64-unknown-linux-musl/debug/deps/libutf8parse-94fe25f5e4d26e74.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwinnow-71e44a3d66cb6c94.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbpaf-d6ecd04ff03ca419.rlib /target/aarch64-unknown-linux-musl/debug/deps/libstrum-d2c2cc07633fa35f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcamino-240010a150d297ea.rlib /target/aarch64-unknown-linux-musl/debug/deps/libini_merge-52ab85ca85eb1ef6.rlib /target/aarch64-unknown-linux-musl/debug/deps/libitertools-3c8527668571ec4b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libeither-a2b9de06f0a56f05.rlib /target/aarch64-unknown-linux-musl/debug/deps/libouroboros-264d51e0c72d09da.rlib /target/aarch64-unknown-linux-musl/debug/deps/libstatic_assertions-c74f30991327ff10.rlib /target/aarch64-unknown-linux-musl/debug/deps/libaliasable-572be80c3f3ff2da.rlib /target/aarch64-unknown-linux-musl/debug/deps/libini_roundtrip-e8d137cd6ce71cc5.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblending_iterator-58230891528f9b4f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnever_say_never-55a96afe923a1039.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpolonius_the_crab-a01b5919e7ccefbb.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnougat-829734d7456b9571.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmacro_rules_attribute-46ac49feca6adfe5.rlib /target/aarch64-unknown-linux-musl/debug/deps/libextension_traits-33afce3e1aa770f2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libext_trait-213552b320c5385e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libthiserror-ec1fcbea570b3243.rlib /target/aarch64-unknown-linux-musl/debug/deps/libregex-c0ee670603ccb95e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libregex_automata-5fd96d6e825bf0c3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libaho_corasick-3bffd0c92b45293d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmemchr-ab793e75fbc54f0b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libregex_syntax-659ff22dceda8f90.rlib /target/aarch64-unknown-linux-musl/debug/deps/libkeyring-fb7c9ecb4c1865be.rlib /target/aarch64-unknown-linux-musl/debug/deps/libdbus_secret_service-d38404207989c5fc.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhkdf-9350d8ce9f1e7fa0.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhmac-a358f4a7505f8e9e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcbc-92fcd10693769a82.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsha2-e6fe4e03187d6bce.rlib /target/aarch64-unknown-linux-musl/debug/deps/libdigest-a792e9026af77ff4.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsubtle-aa3de43f154737a4.rlib /target/aarch64-unknown-linux-musl/debug/deps/libblock_buffer-72ce4c5eb41870b1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libaes-6c8d044cc003e830.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcipher-62c8019d9f8622f7.rlib /target/aarch64-unknown-linux-musl/debug/deps/libinout-0658cf488eea7e6a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libblock_padding-4e21384ff123a9bb.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcrypto_common-5167b4d4ac3fb04a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libgeneric_array-b7906a2a7fe0d58c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtypenum-8daeda8cbfa84696.rlib /target/aarch64-unknown-linux-musl/debug/deps/librand-435fe3c152519f0a.rlib /target/aarch64-unknown-linux-musl/debug/deps/librand_chacha-20be8b414650cb1c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libppv_lite86-ae96af5e2607448b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzerocopy-24d899fd50e1ac8d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbyteorder-0b5a5c794d083300.rlib /target/aarch64-unknown-linux-musl/debug/deps/librand_core-9fd4b0ace0bd6a38.rlib /target/aarch64-unknown-linux-musl/debug/deps/libgetrandom-f21781e69f2f755e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcfg_if-4a318d861e34f94d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libonce_cell-2db2770449d8844c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum-40259aae8a0878a2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_iter-f796fe290659c4a9.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_rational-2a82ee1074b330b1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_complex-9920f58ef444b188.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_bigint-470feafa43549581.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_integer-b2a3f5b9cc632d8d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_traits-c8606e28f9c98dd5.rlib /target/aarch64-unknown-linux-musl/debug/deps/libdbus-ad4d8f6f4fe3b33c.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblibdbus_sys-42fdcef9424c8aef.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblibc-4d0c8946abb01eaf.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblog-5e23d4f97dca19ef.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanyhow-cfb0614503c9d9e4.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstyle-4f2e0a4a19cfe229.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libstd-9718529b8680bd70.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libpanic_unwind-06a6c2bb8c172984.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libobject-706e4140205f2d08.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libmemchr-1d4c45527ffdf09e.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libaddr2line-3e8bc0bbf1156b83.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libgimli-92078d541747f11e.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_demangle-762bd95cbc8709ff.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libstd_detect-ceb4f47aa1ce47b6.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libhashbrown-d46b80bb6875b239.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_std_workspace_alloc-79a590269cf755a2.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libminiz_oxide-b9b6bfc6ccbb29c9.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libadler2-eadbe3b34ffc75ee.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libunwind-1198514678926da6.rlib -lunwind /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libcfg_if-60c2ca99e9b4a67c.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/liblibc-193e8a1580174b61.rlib -lc /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/liballoc-1e351afdc31d47ab.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_std_workspace_core-d6bdaed43cd20054.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libcore-bdd240dcce2d3de9.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libcompiler_builtins-48e6901ebc037f01.rlib -Wl,-Bdynamic -Wl,--eh-frame-hdr -Wl,-z,noexecstack -nostartfiles -L /target/aarch64-unknown-linux-musl/debug/build/libdbus-sys-fc211b9d0ad45396/out -L /target/aarch64-unknown-linux-musl/debug/build/libdbus-sys-fc211b9d0ad45396/out -L /target/aarch64-unknown-linux-musl/debug/build/ring-20c0247aaec7d7ef/out -L /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained -L /rust/lib/rustlib/aarch64-unknown-linux-musl/lib -o /target/aarch64-unknown-linux-musl/debug/deps/chezmoi_modify_manager-275fe4f1229fe0b5 -Wl,--gc-sections -static -no-pie -Wl,-z,relro,-z,now -nodefaultlibs -Wl,--compress-debug-sections=zlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtend.o /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtn.o
+ local release=
++ rustc -Vv
++ cut -d : -f2
++ grep '^release:'
+ release=' 1.86.0-nightly'
+ local minor=
++ echo ' 1.86.0-nightly'
++ cut -d . -f2
+ minor=86
+ (( minor >= 48 ))
+ aarch64-linux-musl-gcc /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crt1.o /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crti.o /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtbegin.o /tmp/rustc0hitcJ/symbols.o /target/aarch64-unknown-linux-musl/debug/deps/chezmoi_modify_manager-275fe4f1229fe0b5.chezmoi_modify_manager.bf3b72a79421d7fe-cgu.0.rcgu.o /target/aarch64-unknown-linux-musl/debug/deps/chezmoi_modify_manager-275fe4f1229fe0b5.6fob8bpx2xd6fn8sx491p6kj1.rcgu.o -Wl,--as-needed -Wl,-Bstatic /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libtest-11282d3042c776ef.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libgetopts-8e527476f1f9fe91.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libunicode_width-313605a911a9091b.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_std_workspace_std-51da7124742587ac.rlib /target/aarch64-unknown-linux-musl/debug/deps/libenv_logger-88d34597e58a95df.rlib /target/aarch64-unknown-linux-musl/debug/deps/libenv_filter-6dd72dd7771b7fdc.rlib /target/aarch64-unknown-linux-musl/debug/deps/libchezmoi_modify_manager-6bff196573e59d99.rlib /target/aarch64-unknown-linux-musl/debug/deps/librpassword-c244550bd340835c.rlib /target/aarch64-unknown-linux-musl/debug/deps/librtoolbox-a629d113d4b65b60.rlib /target/aarch64-unknown-linux-musl/debug/deps/libglob-a4478ddc7a4dcec7.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwhich-fa7324817b67b6d3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libenv_home-a25dd0e8ef8bcf6f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libduct-adf2213d5d5c2b0e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libos_pipe-c16c1d25fca50dc3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libshared_child-0d6f611a3b58452c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libself_update-27a42f63f4b4511a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtar-59d3c56eab515de1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libxattr-ecd9991e4541268e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfiletime-2e7bd2a5e9fda504.rlib /target/aarch64-unknown-linux-musl/debug/deps/libflate2-64dfe788273a6bb1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libminiz_oxide-35b9f9542b66ae06.rlib /target/aarch64-unknown-linux-musl/debug/deps/libadler2-d7cf2809abdf611c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcrc32fast-98bceea7851cb9af.rlib /target/aarch64-unknown-linux-musl/debug/deps/liburlencoding-1c24d421f27fcd94.rlib /target/aarch64-unknown-linux-musl/debug/deps/libquick_xml-a50e3cc405bb1a6c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libreqwest-1e0df6c61f891001.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbase64-f5dc79f2814d476c.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustls_pemfile-55a38c5af4c8a1ef.rlib /target/aarch64-unknown-linux-musl/debug/deps/libipnet-8f0fecddb7d7970f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhyper_rustls-f8b366625087ccc6.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwebpki_roots-02c812fa8e028280.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtokio_rustls-c5d51910b465f306.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustls-012f8dc40b3a3e05.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwebpki-330065566b272c41.rlib /target/aarch64-unknown-linux-musl/debug/deps/libring-4c24cc3629d3466d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libspin-99e2a721fd934565.rlib /target/aarch64-unknown-linux-musl/debug/deps/libuntrusted-b5c0d0504706005e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzeroize-2ddffe546160833f.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustls_pki_types-2ed44ac81a624647.rlib /target/aarch64-unknown-linux-musl/debug/deps/libserde_urlencoded-63126f7e8facd2ea.rlib /target/aarch64-unknown-linux-musl/debug/deps/libserde_json-fea65d703100598e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libryu-26c3d660cf6e0be8.rlib /target/aarch64-unknown-linux-musl/debug/deps/libserde-988728016363ee90.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtower-a18f9d43a3523709.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsync_wrapper-2fb303f6a1d598c3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtower_layer-2416d81df265434d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhyper_util-f30cf0b40d60be4a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtower_service-88c6c59d0d8d0b64.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhyper-311870162ca34c30.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwant-5d14bb1a02d97be2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtry_lock-713799e847adb393.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttparse-0a55bda6cb9c150c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libh2-9854a4f9aacb26cb.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtracing-35ef49265900271b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtracing_core-c400556172631c50.rlib /target/aarch64-unknown-linux-musl/debug/deps/libindexmap-d96e06ddc09ddd70.rlib /target/aarch64-unknown-linux-musl/debug/deps/libequivalent-6b18beb2376b7663.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhashbrown-d35e156a772522a2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libatomic_waker-ec119f4bf762f683.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtokio_util-36db6b551552763f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_channel-b040ed76df724254.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtokio-e752437702e71926.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsocket2-89fe9cda98a6e624.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmio-183e147343a75a0a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttp_body_util-a2509902d0e281fe.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttp_body-c5617f705fbd7516.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_util-e388f8b098262c8c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_io-04316109944f8785.rlib /target/aarch64-unknown-linux-musl/debug/deps/libslab-ec17825b8c5e64d0.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpin_project_lite-1ec7c40ff6bd1c69.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_sink-fe06589f9d096f97.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_task-fcd6e91835f13596.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpin_utils-5ae43a724a1a4586.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfutures_core-0e0518818326709b.rlib /target/aarch64-unknown-linux-musl/debug/deps/liburl-c9c17ed6acf24b47.rlib /target/aarch64-unknown-linux-musl/debug/deps/libidna-fa0e8c6d8b591e88.rlib /target/aarch64-unknown-linux-musl/debug/deps/libidna_adapter-3f7e433ae93d8aa3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_normalizer-c215d3739752bd97.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_normalizer_data-9338dbfbc9f04a58.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwrite16-d0d06f96f2c4eae5.rlib /target/aarch64-unknown-linux-musl/debug/deps/libutf8_iter-b7dedb7b5954d701.rlib /target/aarch64-unknown-linux-musl/debug/deps/libutf16_iter-663db2246e41f6c0.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsmallvec-40c35139d7277050.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_properties-6bc4d605ad418160.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_properties_data-5a76001dc44a3259.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_locid_transform-6f6d139b351d2665.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_locid_transform_data-2c97e2da407d4c0c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_collections-5fc88492990936ad.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_provider-20ebb20ddb59b380.rlib /target/aarch64-unknown-linux-musl/debug/deps/libicu_locid-bb9ab788ff2d5ffd.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblitemap-88236c9a046e7939.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtinystr-adc4405d2f83a93b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzerovec-fe19fb5b5024a1f7.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwriteable-526d295315c33404.rlib /target/aarch64-unknown-linux-musl/debug/deps/libyoke-aa436aa723ebef47.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzerofrom-a1d33568cadc8d47.rlib /target/aarch64-unknown-linux-musl/debug/deps/libstable_deref_trait-dd4f1e3dab203d37.rlib /target/aarch64-unknown-linux-musl/debug/deps/libform_urlencoded-778cfd10439c3fd8.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpercent_encoding-bd6fd8050ca738ac.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhttp-6dc7762fd73534ab.rlib /target/aarch64-unknown-linux-musl/debug/deps/libitoa-6a132b9c42273f48.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbytes-ed56f1f75b5d8e94.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfnv-d4a440f237839fae.rlib /target/aarch64-unknown-linux-musl/debug/deps/libindicatif-9cb95163f2199643.rlib /target/aarch64-unknown-linux-musl/debug/deps/libportable_atomic-e422ea85c9e06e1e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnumber_prefix-3830a3467ebae53e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libconsole-5937a745d923dc03.rlib /target/aarch64-unknown-linux-musl/debug/deps/libunicode_width-46380feb0c6d652c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libself_replace-50855f7e704fdc78.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtempfile-c3f8aa6ff2f6318e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libfastrand-e1f677de8d996655.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustix-745502aa14383bf9.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbitflags-5b5fa851c43f2de5.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblinux_raw_sys-3d98cb974913b37b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmedic-1f299f646e450e46.rlib /target/aarch64-unknown-linux-musl/debug/deps/libos_info-6f9369e29fa20e38.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustc_version_runtime-92267d77ca178f81.rlib /target/aarch64-unknown-linux-musl/debug/deps/librustc_version-3b4f12fa64defc48.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsemver-0ca1b6f959189493.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstream-12e26d093e2d6d15.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstyle_query-8366fef9b2f1f512.rlib /target/aarch64-unknown-linux-musl/debug/deps/libis_terminal_polyfill-6086d127fd034c07.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcolorchoice-8f6a567228987a9e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstyle_parse-d3aa862edcdf6ddd.rlib /target/aarch64-unknown-linux-musl/debug/deps/libutf8parse-94fe25f5e4d26e74.rlib /target/aarch64-unknown-linux-musl/debug/deps/libwinnow-71e44a3d66cb6c94.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbpaf-d6ecd04ff03ca419.rlib /target/aarch64-unknown-linux-musl/debug/deps/libstrum-d2c2cc07633fa35f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcamino-240010a150d297ea.rlib /target/aarch64-unknown-linux-musl/debug/deps/libini_merge-52ab85ca85eb1ef6.rlib /target/aarch64-unknown-linux-musl/debug/deps/libitertools-3c8527668571ec4b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libeither-a2b9de06f0a56f05.rlib /target/aarch64-unknown-linux-musl/debug/deps/libouroboros-264d51e0c72d09da.rlib /target/aarch64-unknown-linux-musl/debug/deps/libstatic_assertions-c74f30991327ff10.rlib /target/aarch64-unknown-linux-musl/debug/deps/libaliasable-572be80c3f3ff2da.rlib /target/aarch64-unknown-linux-musl/debug/deps/libini_roundtrip-e8d137cd6ce71cc5.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblending_iterator-58230891528f9b4f.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnever_say_never-55a96afe923a1039.rlib /target/aarch64-unknown-linux-musl/debug/deps/libpolonius_the_crab-a01b5919e7ccefbb.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnougat-829734d7456b9571.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmacro_rules_attribute-46ac49feca6adfe5.rlib /target/aarch64-unknown-linux-musl/debug/deps/libextension_traits-33afce3e1aa770f2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libext_trait-213552b320c5385e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libthiserror-ec1fcbea570b3243.rlib /target/aarch64-unknown-linux-musl/debug/deps/libregex-c0ee670603ccb95e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libregex_automata-5fd96d6e825bf0c3.rlib /target/aarch64-unknown-linux-musl/debug/deps/libaho_corasick-3bffd0c92b45293d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libmemchr-ab793e75fbc54f0b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libregex_syntax-659ff22dceda8f90.rlib /target/aarch64-unknown-linux-musl/debug/deps/libkeyring-fb7c9ecb4c1865be.rlib /target/aarch64-unknown-linux-musl/debug/deps/libdbus_secret_service-d38404207989c5fc.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhkdf-9350d8ce9f1e7fa0.rlib /target/aarch64-unknown-linux-musl/debug/deps/libhmac-a358f4a7505f8e9e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcbc-92fcd10693769a82.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsha2-e6fe4e03187d6bce.rlib /target/aarch64-unknown-linux-musl/debug/deps/libdigest-a792e9026af77ff4.rlib /target/aarch64-unknown-linux-musl/debug/deps/libsubtle-aa3de43f154737a4.rlib /target/aarch64-unknown-linux-musl/debug/deps/libblock_buffer-72ce4c5eb41870b1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libaes-6c8d044cc003e830.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcipher-62c8019d9f8622f7.rlib /target/aarch64-unknown-linux-musl/debug/deps/libinout-0658cf488eea7e6a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libblock_padding-4e21384ff123a9bb.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcrypto_common-5167b4d4ac3fb04a.rlib /target/aarch64-unknown-linux-musl/debug/deps/libgeneric_array-b7906a2a7fe0d58c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libtypenum-8daeda8cbfa84696.rlib /target/aarch64-unknown-linux-musl/debug/deps/librand-435fe3c152519f0a.rlib /target/aarch64-unknown-linux-musl/debug/deps/librand_chacha-20be8b414650cb1c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libppv_lite86-ae96af5e2607448b.rlib /target/aarch64-unknown-linux-musl/debug/deps/libzerocopy-24d899fd50e1ac8d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libbyteorder-0b5a5c794d083300.rlib /target/aarch64-unknown-linux-musl/debug/deps/librand_core-9fd4b0ace0bd6a38.rlib /target/aarch64-unknown-linux-musl/debug/deps/libgetrandom-f21781e69f2f755e.rlib /target/aarch64-unknown-linux-musl/debug/deps/libcfg_if-4a318d861e34f94d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libonce_cell-2db2770449d8844c.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum-40259aae8a0878a2.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_iter-f796fe290659c4a9.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_rational-2a82ee1074b330b1.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_complex-9920f58ef444b188.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_bigint-470feafa43549581.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_integer-b2a3f5b9cc632d8d.rlib /target/aarch64-unknown-linux-musl/debug/deps/libnum_traits-c8606e28f9c98dd5.rlib /target/aarch64-unknown-linux-musl/debug/deps/libdbus-ad4d8f6f4fe3b33c.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblibdbus_sys-42fdcef9424c8aef.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblibc-4d0c8946abb01eaf.rlib /target/aarch64-unknown-linux-musl/debug/deps/liblog-5e23d4f97dca19ef.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanyhow-cfb0614503c9d9e4.rlib /target/aarch64-unknown-linux-musl/debug/deps/libanstyle-4f2e0a4a19cfe229.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libstd-9718529b8680bd70.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libpanic_unwind-06a6c2bb8c172984.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libobject-706e4140205f2d08.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libmemchr-1d4c45527ffdf09e.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libaddr2line-3e8bc0bbf1156b83.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libgimli-92078d541747f11e.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_demangle-762bd95cbc8709ff.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libstd_detect-ceb4f47aa1ce47b6.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libhashbrown-d46b80bb6875b239.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_std_workspace_alloc-79a590269cf755a2.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libminiz_oxide-b9b6bfc6ccbb29c9.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libadler2-eadbe3b34ffc75ee.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libunwind-1198514678926da6.rlib -lunwind /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libcfg_if-60c2ca99e9b4a67c.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/liblibc-193e8a1580174b61.rlib -lc /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/liballoc-1e351afdc31d47ab.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/librustc_std_workspace_core-d6bdaed43cd20054.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libcore-bdd240dcce2d3de9.rlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/libcompiler_builtins-48e6901ebc037f01.rlib -Wl,-Bdynamic -Wl,--eh-frame-hdr -Wl,-z,noexecstack -nostartfiles -L /target/aarch64-unknown-linux-musl/debug/build/libdbus-sys-fc211b9d0ad45396/out -L /target/aarch64-unknown-linux-musl/debug/build/libdbus-sys-fc211b9d0ad45396/out -L /target/aarch64-unknown-linux-musl/debug/build/ring-20c0247aaec7d7ef/out -L /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained -L /rust/lib/rustlib/aarch64-unknown-linux-musl/lib -o /target/aarch64-unknown-linux-musl/debug/deps/chezmoi_modify_manager-275fe4f1229fe0b5 -Wl,--gc-sections -static -no-pie -Wl,-z,relro,-z,now -nodefaultlibs -Wl,--compress-debug-sections=zlib /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtend.o /rust/lib/rustlib/aarch64-unknown-linux-musl/lib/self-contained/crtn.o
|
= note: `-D linker-messages` implied by `-D warnings`
= help: to override `-D warnings` add `#[allow(linker_messages)]`
error: could not compile `chezmoi_modify_manager` (bin "chezmoi_modify_manager" test) due to 1 previous error
```
I can't actually see where it says the actual linker error or warning though? Also stable works fine. I use [cross](https://github.com/cross-rs/cross) for building.
I expected to see this happen: Linking should succeed, or if it doesn't, and rustc blames the linker, the **actual linker error/warning should be visible**
Instead, this happened: *Very confusing error message, with no actual error or warning?*
### 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.86.0-nightly (f85c6de55 2025-01-26)
(Sorry, I don't have output of --verbose in CI, I could add that if needed though.)
```
<!--
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-linkage,C-discussion,L-linker_messages | low | Critical |
2,813,060,341 | yt-dlp | [NOSNLArticle] ERROR: An extractor error has occurred. (caused by KeyError('items')) nos.nl | ### 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
Netherlands
### Provide a description that is worded well enough to be understood
```
yt-dlp https://nos.nl/nieuwsuur/video/2553262-drugscrimineel-bolle-jos-verschijnt-in-video
[NOSNLArticle] Extracting URL: https://nos.nl/nieuwsuur/video/2553262-drugscrimineel-bolle-jos-verschijnt-in-video
[NOSNLArticle] drugscrimineel-bolle-jos-verschijnt-in-video: Downloading webpage
ERROR: An extractor error has occurred. (caused by KeyError('items')); please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
```
Notice the `nieuwsuur/` path. URL is apparently not recognized correctly by the extractor.
https://nos.nl/video/2553262-drugscrimineel-bolle-jos-verschijnt-in-video _does_ work correctly.
### 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 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 [3b4531934] (pip)
[debug] Python 3.12.3 (CPython x86_64 64bit) - Linux-6.8.0-51-generic-x86_64-with-glibc2.39 (OpenSSL 3.0.13 30 Jan 2024, glibc 2.39)
[debug] exe versions: ffmpeg 6.1.1 (setts), ffprobe 6.1.1
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.12.14, curl_cffi-0.7.1, mutagen-1.47.0, requests-2.32.3, sqlite3-3.45.1, urllib3-2.3.0, websockets-14.2
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1839 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)
``` | site-bug,triage | low | Critical |
2,813,060,811 | tailwindcss | Not able to install tailwindcss v4.0 | when i started the dev server i face following issue
failed to load config from D:\internship\sample-test\vite.config.js
Error: The specified module could not be found.
\\?\D:\internship\sample-test\node_modules\@tailwindcss\oxide-win32-x64-msvc\tailwindcss-oxide.win32-x64-msvc.node
at Module._extensions..node (node:internal/modules/cjs/loader:1586:18)
at Module.load (node:internal/modules/cjs/loader:1288:32)
at Module._load (node:internal/modules/cjs/loader:1104:12)
at Module.require (node:internal/modules/cjs/loader:1311:19)
at require (node:internal/modules/helpers:179:18)
at Object.<anonymous> (D:\internship\sample-test\node_modules\@tailwindcss\oxide\index.js:72:29)
at Module._compile (node:internal/modules/cjs/loader:1469:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
at Module.load (node:internal/modules/cjs/loader:1288:32)
at Module._load (node:internal/modules/cjs/loader:1104:12)
**Steps to Reproduce:**
1. Clone the repository [https://github.com/prathamaaaaa/sample-react-vite-app](url).
2. Install dependencies using npm install or yarn install.
3. Try running the development server with npm run dev or yarn dev.
**Expected Behavior:**
The development server should start without errors.
**Actual Behavior:**
The error message about the missing module tailwindcss-oxide.win32-x64-msvc.node appears, and the server fails to start.
**Environment:**
OS: (e.g., Windows 10)
Node.js version: (e.g., 20.18.2)
Tailwind CSS version: (@tailwindcss/vite: ^4.0.0)
Vite version: (6.0.5)
**Possible Causes:**
The error may be due to the missing native module required by Tailwind CSS's oxide package.
**Attachments:**
Error logs: this already mention above.
Configuration files such as vite.config.js or tailwind.config.js.
Steps or code to reproduce if possible (such as your package.json dependencies).
_**here is the content of vite.config.js**_
import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import tailwindcss from '@tailwindcss/postcss';
import autoprefixer from 'autoprefixer';
// https://vite.dev/config/
export default defineConfig({
plugins: [react(), tailwindcss(), autoprefixer()],
})
**_here is the package.json content_**
{
"name": "sample-test",
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
"dev": "vite",
"build": "vite build",
"lint": "eslint .",
"preview": "vite preview"
},
"dependencies": {
"react": "^18.3.1",
"react-dom": "^18.3.1"
},
"devDependencies": {
"@eslint/js": "^9.17.0",
"@tailwindcss/postcss": "^4.0.0",
"@tailwindcss/vite": "^4.0.0",
"@types/react": "^18.3.18",
"@types/react-dom": "^18.3.5",
"@vitejs/plugin-react": "^4.3.4",
"autoprefixer": "^10.4.20",
"eslint": "^9.17.0",
"eslint-plugin-react": "^7.37.2",
"eslint-plugin-react-hooks": "^5.0.0",
"eslint-plugin-react-refresh": "^0.4.16",
"globals": "^15.14.0",
"vite": "^6.0.5"
}
}
_Originally posted by @prathamaaaaa in https://github.com/tailwindlabs/tailwindcss/discussions/15914_ | needs reproduction | low | Critical |
2,813,117,013 | kubernetes | Service with selector does not create all required endpoints, when a POD has multiple containers with a matching named port. | ### What happened?
I have a Deployment which creates POD's containing two containers, each container has a named port "grpc-service" on a different port to avoid conflicts. I want a k8s service to connect to these grpc services in a round-robin fashion and also be able to use the k8s API to retrieve the list of endpoints. I attempt to do this by creating a simple service, with a label selector that matches the container, and names the target-port. However when I scale the deployment only one of the containers is matched to the service, I was expecting both containers to be matched resulting in two endpoints for each POD instance.
The generated endpoint looks like this, when the deployment is scaled to two replica's (I've trimmed out the targetRef's to keep it brief):
```
kind: Endpoints
apiVersion: v1
metadata:
name: grpc-test-service
annotations:
endpoints.kubernetes.io/last-change-trigger-time: '2025-01-27T11:55:15Z'
subsets:
- addresses:
- ip: 10.245.0.71
- ip: 10.245.2.91
ports:
- name: grpc
port: 8080
protocol: TCP
```
### What did you expect to happen?
I expected the resultant endpoint to look like this (i.e. giving 4 endpoints):
```
apiVersion: v1
kind: Endpoints
metadata:
name: grpc-test-service
subsets:
- addresses:
- ip: 10.245.0.124
- ip: 10.245.2.121
ports:
- port: 8080
name: grpc
protocol: TCP
- addresses:
- ip: 10.245.0.124
- ip: 10.245.2.121
ports:
- port: 8081
name: grpc
protocol: TCP
```
### How can we reproduce it (as minimally and precisely as possible)?
To create my test set-up the following yaml can be used (note that for the example I'm using nginx, however in practise I have different containers, which provide the same gRPC services).
```
apiVersion: v1
kind: Service
metadata:
name: grpc-test-service
spec:
type: LoadBalancer
ports:
- port: 5000
name: grpc
targetPort: grpc-server
selector:
app: grpc-test-server
---
apiVersion: v1
kind: ConfigMap
metadata:
name: nginx-config-site1
data:
nginx.conf: |
events {
}
http {
server {
listen 8080;
location / {
return 200 "Hello world! I'm site 1";
}
}
}
---
apiVersion: v1
kind: ConfigMap
metadata:
name: nginx-config-site2
data:
nginx.conf: |
events {
}
http {
server {
listen 8081;
location / {
return 200 "Hello world! I'm site 2";
}
}
}
---
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: grpc-test-server
name: grpc-test-server
name: grpc-test-server
spec:
replicas: 2
selector:
matchLabels:
app: grpc-test-server
name: grpc-test-server
template:
metadata:
labels:
app: grpc-test-server
name: grpc-test-server
name: grpc-test-server
spec:
containers:
- name: grpc-server-1
image: nginx
imagePullPolicy: Always
ports:
- name: grpc-server
containerPort: 8080
protocol: TCP
volumeMounts:
- name: config-site1
mountPath: /etc/nginx/
- name: grpc-server-2
image: nginx
imagePullPolicy: Always
ports:
- name: grpc-server
containerPort: 8081
protocol: TCP
volumeMounts:
- name: config-site2
mountPath: /etc/nginx/
volumes:
- name: config-site1
configMap:
name: nginx-config-site1
items:
- key: nginx.conf
path: nginx.conf
- name: config-site2
configMap:
name: nginx-config-site2
items:
- key: nginx.conf
path: nginx.conf
```
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
```console
$ kubectl version
Warning: Use tokens from the TokenRequest API or manually created secret-based tokens instead of auto-generated secret-based tokens.
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.5", GitCommit:"aea7bbadd2fc0cd689de94a54e5b7b758869d691", GitTreeState:"clean", BuildDate:"2021-09-15T21:10:45Z", GoVersion:"go1.16.8", Compiler:"gc
", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"32", GitVersion:"v1.32.0", GitCommit:"70d3cc986aa8221cd1dfb1121852688902d3bf53", GitTreeState:"clean", BuildDate:"2024-12-11T17:59:15Z", GoVersion:"go1.23.3", Compiler:"gc
", Platform:"linux/amd64"}
WARNING: version difference between client (1.21) and server (1.32) exceeds the supported minor version skew of +/-1
```
</details>
### Cloud provider
<details>
None, an on Premise setup
</details>
### OS version
<details>
```console
# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
$ uname -a
Linux bmk8s-hermes 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
</details>
### Install tools
<details>
</details>
### Container runtime (CRI) and version (if applicable)
<details>
</details>
### Related plugins (CNI, CSI, ...) and versions (if applicable)
<details>
</details>
| kind/bug,sig/network,needs-triage | low | Critical |
2,813,142,448 | pytorch | [export] Fail fast on pytorch with `aoti_load_package` | ### 🐛 Describe the bug
When we use
`aoti_compile_and_package` for GPU and then on another instance we use `aoti_load_package` without GPU it is failing internally at:
https://github.com/triton-lang/triton/blob/main/python/triton/runtime/driver.py#L8
As the message is a bit ambiguous
`raise RuntimeError(f"{len(actives)} active drivers ({actives}). There should only be one.")`
Can we fast and safely fail in pytorch with a more user friendly message instead of triton internals?
### Versions
nightly
cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 | oncall: pt2,export-triaged,oncall: export | low | Critical |
2,813,148,919 | langchain | Assertions not executed in test_stream_error_callback | ### Checked other resources
- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).
### Example Code
N/A
### Error Message and Stack Trace (if applicable)
_No response_
### Description
`test_stream_error_callback` has test code which is not executed.
```python
async def test_stream_error_callback() -> None:
message = "test"
def eval_response(callback: BaseFakeCallbackHandler, i: int) -> None:
assert callback.errors == 1
assert len(callback.errors_args) == 1
llm_result: LLMResult = callback.errors_args[0]["kwargs"]["response"]
if i == 0:
assert llm_result.generations == []
else:
assert llm_result.generations[0][0].text == message[:i]
for i in range(2):
llm = FakeListChatModel(
responses=[message],
error_on_chunk_number=i,
)
with pytest.raises(FakeListChatModelError):
cb_async = FakeAsyncCallbackHandler()
async for _ in llm.astream("Dummy message", callbacks=[cb_async]):
pass
# !!! The code below is not executed
eval_response(cb_async, i)
cb_sync = FakeCallbackHandler()
for _ in llm.stream("Dumy message", callbacks=[cb_sync]):
pass
eval_response(cb_sync, i)
```
when `llm.astream` is called it raises `FakeListChatModelError` and exits the `with` section without executing `eval_response` and the sync test.
This was detected when applying ruff rule PT012. See https://github.com/langchain-ai/langchain/pull/29381.
### System Info
N/A | 🤖:bug | low | Critical |
2,813,152,435 | ui | [bug]: Shadcn not recognising tailwind.config.js file from React+Vite project | ### Describe the bug
I have all configuration for tailwind and other stuff
and tailwind is working in my project still this error.
### Affected component/components
Installation Problem
### How to reproduce
S D:\shop-manage-react\shop-manage> npx shadcn@latest init
✔ Preflight checks.
✔ Verifying framework. Found Vite.
✖ Validating Tailwind CSS.
✔ Validating import alias.
No Tailwind CSS configuration found at D:\shop-manage-react\shop-manage.
It is likely you do not have Tailwind CSS installed or have an invalid configuration.
Install Tailwind CSS then try again.
Visit https://tailwindcss.com/docs/guides/vite to get started.
### Codesandbox/StackBlitz link
_No response_
### Logs
```bash
```
### System Info
```bash
{
"name": "shop-manage",
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
"dev": "vite",
"build": "vite build",
"lint": "eslint .",
"preview": "vite preview"
},
"dependencies": {
"@tailwindcss/vite": "^4.0.0",
"axios": "^1.7.9",
"js-cookie": "^3.0.5",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"react-router-dom": "^7.1.3"
},
"devDependencies": {
"@eslint/js": "^9.17.0",
"@types/node": "^22.10.10",
"@types/react": "^18.3.18",
"@types/react-dom": "^18.3.5",
"@vitejs/plugin-react": "^4.3.4",
"autoprefixer": "^10.4.20",
"eslint": "^9.17.0",
"eslint-plugin-react": "^7.37.2",
"eslint-plugin-react-hooks": "^5.0.0",
"eslint-plugin-react-refresh": "^0.4.16",
"globals": "^15.14.0",
"postcss": "^8.5.1",
"tailwindcss": "^4.0.0",
"vite": "^6.0.5"
}
}
```
### Before submitting
- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues | bug | low | Critical |
2,813,158,600 | vscode | Test compound logs and filtering in Output view | Refs: #237974 #237829 #237432
- [x] Mac @Tyriar
- [x] Win @bpasero
- [ ] Linux @TylerLeonhardt
Complexity: 5
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23238846%0A%0A&assignees=sandy081)
---
### Filtering
You can now filter the content in the Output view.
- Open any output view say `Git`
- Test filtering the content in the output view and make sure it is working as expected
- Filter by Log Level
- Filter by Category - Category of the log line is defined after the log level in square brackets.
- Filter by Text
### Compound Output View
You can now view multiple logs in a single compound output view. VS Code already has OOB some compound output views: Window, Shared & Telemetry. You can also create one by selecting existing.
- Open Window log in Output View and set log level to Trace from `gear` icon next to the dropdown
- Go to extensions view and run some searches to Marketplace
- Validate that the network logs appear in the Window output
- Validate that the filter dropdown shows Network category. Note that other categories available in the dropdown are logs composed into this view.
- Test filtering (follows steps from above) in the Window output view is working as expected
- Test creating a custom compound log using the action `Add Compound Log...` available in the overflow menu of the Output view.
- Test that the created compound log view is showing the data from all the logs you selected
- Test that the filtering this compound log view is working as expected
- Test that you can open the compound log in an editor or in an aux window using the actions available in the overflow menu
### Export & Import
You can now export and import the logs using the actions available in the overflow menu of the Output view
- Test **Save Output As...** and **Export Logs...** actions in the overflow menu are working as expected
- Import these exported logs using **Import Log...** action and test the log is imported correctly.
- Test that the filtering the imported log is working as expected | testplan-item | low | Minor |
2,813,165,440 | tauri | [bug] iOS LaunchScreen storyboard ignored | ### Describe the bug
```
warning: “View Controller“ is unreachable because it has no entry points, and no identifier for runtime access via -[UIStoryboard instantiateViewControllerWithIdentifier:].
```
Getting this warning when initializing and running (dev + release) my tauri v2 app. Any changes to the LaunchScreen.storyboard are ignored.
### Reproduction
1. Add labels or any other static info to the LaunchScreen storyboard in the xcode project
2. Build the app, pay attention to the startup
3. In the short time when launch story board should be visible one can only see the white screen
### Expected behavior
Changes to the story board should be picked up in debug and release builds.
### Full `tauri info` output
```text
[✔] Environment
- OS: Mac OS 15.1.1 arm64 (X64)
✔ Xcode Command Line Tools: installed
✔ rustc: 1.83.0 (90b35a623 2024-11-26)
✔ cargo: 1.83.0 (5ffbef321 2024-10-29)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-aarch64-apple-darwin (default)
- node: 20.12.2
- yarn: 4.4.1
- npm: 10.5.0
[-] Packages
- tauri 🦀: 2.1.1
- tauri-build 🦀: 2.0.3
- wry 🦀: 0.47.2
- tao 🦀: 0.30.8
- @tauri-apps/api : 2.0.0-beta.11 (outdated, latest: 2.2.0)
- @tauri-apps/cli : 2.1.0 (outdated, latest: 2.2.7)
[-] Plugins
- tauri-plugin-fs 🦀: 2.2.0
- @tauri-apps/plugin-fs : not installed!
- tauri-plugin-log 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#83b65072695477a595026fe3b035e2f669fc188b (2.2.0)
- @tauri-apps/plugin-log : 2.0.0-rc.1 (outdated, latest: 2.2.0)
- tauri-plugin-shell 🦀: 2.2.0
- @tauri-apps/plugin-shell : 2.2.0
- tauri-plugin-dialog 🦀: 2.2.0
- @tauri-apps/plugin-dialog : not installed!
- tauri-plugin-updater 🦀: 2.3.0
- @tauri-apps/plugin-updater : 2.0.0 (outdated, latest: 2.3.1)
- tauri-plugin-store 🦀: 2.2.0
- @tauri-apps/plugin-store : 2.2.0
- tauri-plugin-process 🦀: 2.2.0
- @tauri-apps/plugin-process : 2.2.0
- tauri-plugin-os 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#83b65072695477a595026fe3b035e2f669fc188b (2.2.0)
- @tauri-apps/plugin-os : 2.0.0-beta.3 (outdated, latest: 2.2.0)
- tauri-plugin-positioner 🦀: git+https://github.com/tauri-apps/plugins-workspace?branch=v2#83b65072695477a595026fe3b035e2f669fc188b (2.2.0)
- @tauri-apps/plugin-positioner : not installed!
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
- framework: SolidJS
- bundler: Vite
[-] iOS
- Developer Teams: Snowstorm Inc. (ID: FXX28NQXMK), Timur Amirov (ID: C8A8ALV8K5)
```
### Stack trace
```text
```
### Additional context
Easiest way to fix is to add `initialViewController="Y6W-OH-hqX"` to the storyboard template. | type: bug,status: needs triage | low | Critical |
2,813,172,283 | vscode | Editor GPU: Scrolling through long comment causes noticeable lag | From https://github.com/microsoft/vscode/issues/221145#issuecomment-2612075061
https://github.com/paritytech/polkadot-sdk/blob/e9393a9afc3b33cc2d01b7820a8f186434196758/substrate/frame/nis/src/lib.rs#L1-L75 | bug,editor-gpu | low | Minor |
2,813,184,929 | kubernetes | [Flaking Test] [sig-network] LoadBalancers ExternalTrafficPolicy: Local [Feature:LoadBalancer] [Slow] should only target nodes with endpoints | ### Which jobs are flaking?
master-informing
- gce-master-scale-correctness
### Which tests are flaking?
Kubernetes e2e suite: [It] [sig-network] LoadBalancers ExternalTrafficPolicy: Local [Feature:LoadBalancer] [Slow] should only target nodes with endpoints.
[Prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-scale-correctness/1883560971318857728)
[Triage](https://storage.googleapis.com/k8s-triage/index.html?test=should%20only%20target%20nodes%20with%20endpoints)
### Since when has it been flaking?
- [Jan 26, 10:31 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-gce-scale-correctness/1883560971318857728)
### Testgrid link
https://testgrid.k8s.io/sig-release-master-informing#gce-master-scale-correctness
### Reason for failure (if possible)
```
{ failed [FAILED] timed out waiting for service "external-local-nodes" to have a load balancer: context deadline exceeded
In [It] at: k8s.io/kubernetes/test/e2e/network/loadbalancer.go:1094 @ 01/26/25 18:39:43.152
}
```
### Anything else we need to know?
_No response_
### Relevant SIG(s)
/sig network
cc: @kubernetes/release-team-release-signal | sig/network,kind/flake,needs-triage | low | Critical |
2,813,214,653 | transformers | ForSequenceClassification models assume right-padding | We have `ForSequenceClassification` variants for several of our CLMs, and this line is commonly copied between them:
`sequence_lengths = torch.eq(input_ids, self.config.pad_token_id).int().argmax(-1) - 1`
However, this line assumes **right-padding**, because it treats the length of the sequence as the number of tokens before the first pad token (when multiple values have the max value, then `argmax` returns the first index with that value).
If we have left-padding instead, then this will break because it will compute a sequence length of -1. This was reported as a bug in Gemma [here](https://github.com/huggingface/transformers/issues/30004), but it likely affects other models as well.
`tokenizer.padding_side` is probably not accessible to the model, because it is stored in `tokenizer_config` and not `config`. As a result, I think the solution here will have to be rewriting this code so that it can handle either left- or right-padding. | bug | low | Critical |
2,813,227,367 | vscode | Test: GitHub - hover details provider | Refs: https://github.com/microsoft/vscode/issues/237436
- [x] anyOS @legomushroom
- [x] anyOS @sandy081
Complexity: 4
[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23238852%0A%0A&assignees=lszomoru)
---
This milestone we have enabled extensions (ex: GitHub) to enrich the commit hover that is shown in the Timeline view, Source Control Graph view and git blame. The GitHub extension is resolving issue/PR links as well as provides the commit author avatar.
### Prerequisites
* Install latest version of VS Code Insiders
* Enable the following settings:
* `github.showAvatar`
* `git.blame.editorDecoration.enabled`
* `git.blame.statusBarItem.enabled`
### Timeline view
* Open a folder/workspace that contains a git repository hosted on GitHub. A perfect candidate is the `microsoft/vscode` repository as all commits into `main` are being done using the pull request workflow.
* Open a file, and open the Timeline view
* Ensure that the "Git History" items are shown in the Timeline view
* Hover over various "Git History" items
* Confirm that issue/PR links appear as links in the hover
* Confirm that clicking the link opens the correct artifact in the browser
* Confirm that the commit author avatar is being rendered
### Source Control Graph view
* Open a folder/workspace that contains a git repository hosted on GitHub. A perfect candidate is the `microsoft/vscode` repository as all commits into `main` are being done using the pull request workflow.
* Open the Source Control Graph view
* Hover over various history items in the graph
* Confirm that issue/PR links appear as links in the hover
* Confirm that clicking the link opens the correct artifact in the browser
* Confirm that the commit author avatar is being rendered
### Git Blame
* Open a folder/workspace that contains a git repository hosted on GitHub. A perfect candidate is the `microsoft/vscode` repository as all commits into `main` are being done using the pull request workflow.
* Open a file and navigate around the file
* Hover over the editor decoration
* Confirm that issue/PR links appear as links in the hover
* Confirm that clicking the link opens the correct artifact in the browser
* Confirm that the commit author avatar is being rendered
* Hover over the status bar item
* Confirm that issue/PR links appear as links in the hover
* Confirm that clicking the link opens the correct artifact in the browser
* Confirm that the commit author avatar is being rendered
### Non-GitHub Repository
* Open a folder/workspace that contains a git repository not hosted on GitHub (you can either open a repository hosted on Azure Repos, or run `git init` to create a repository that has not been published to a remote)
* Add a new file, add contents to it, and create a commit with a message that contains a string that looks like an issue/PR reference (ex: #12345)
* Open the Timeline view, and hover over the "Git History" item
* Confirm that the `#12345` string is not rendered as a link
* Confirm that the user avatar is not being rendered
* Open the Source Control Graph view, and hover over the history item
* Confirm that the `#12345` string is not rendered as a link
* Confirm that the user avatar is not being rendered
* Open the file, navigate around the file to reveal the git blame editor decoration and status bar item
* Hover over the editor decoration
* Confirm that the `#12345` string is not rendered as a link
* Confirm that the user avatar is not being rendered
* Hover over the status bar item
* Confirm that the `#12345` string is not rendered as a link
* Confirm that the user avatar is not being rendered
### Avatar setting
* Open a folder/workspace that contains a git repository hosted on GitHub. A perfect candidate is the `microsoft/vscode` repository as all commits into `main` are being done using the pull request workflow.
* Open the settings editor and disable the `github.showAvatar` setting
* Open the Timeline view, and hover over the "Git History" item
* Confirm that the commit author avatar is not shown
* Open the Source Control Graph view, and hover over the history item
* Confirm that the commit author avatar is not shown
* Open the file, navigate around the file to reveal the git blame editor decoration and status bar item
* Hover over the editor decoration
* Confirm that the commit author avatar is not shown
* Hover over the status bar item
* Confirm that the commit author avatar is not shown | testplan-item | low | Minor |
2,813,236,767 | kubernetes | hack/local-up-cluster.sh fails with emulation version needs to be greater or equal to 1.31 | ### What happened?
Tried to create local Kubernetes cluster using hack/local-up-cluster.sh script but the api-server fails to come up.
### What did you expect to happen?
Successfully create a local Kubernetes cluster.
### How can we reproduce it (as minimally and precisely as possible)?
1. Clone the Kubernetes repository
```
https://github.com/kubernetes/kubernetes.git
```
2. Run the local cluster create script
```
./hack/local-up-cluster.sh
```
[Install the missing dependencies reported by the script]
3. Error
```
2025/01/27 20:08:25 [INFO] received CSR
2025/01/27 20:08:25 [INFO] generating key: rsa-2048
2025/01/27 20:08:25 [INFO] encoded CSR
2025/01/27 20:08:25 [INFO] signed certificate with serial number xxxxxxxxx
Waiting for apiserver to come up
!!! [0127 20:09:29] Timed out waiting for apiserver: to answer at https://127.0.0.1:6443/healthz; tried 60 waiting 1 between each
check apiserver logs: /tmp/kube-apiserver.log
Cleaning up...
```
4. API server Log
```
$ cat /tmp/kube-apiserver.log
I0127 20:08:28.017237 63752 flags.go:64] FLAG: --v="3"
I0127 20:08:28.017240 63752 flags.go:64] FLAG: --version="false"
I0127 20:08:28.017243 63752 flags.go:64] FLAG: --vmodule=""
I0127 20:08:28.017246 63752 flags.go:64] FLAG: --watch-cache="true"
I0127 20:08:28.017248 63752 flags.go:64] FLAG: --watch-cache-sizes="[]"
W0127 20:08:28.017278 63752 registry.go:256] calling componentGlobalsRegistry.AddFlags more than once, the registry will be set by the latest flags
E0127 20:08:28.017662 63752 run.go:72] "command failed" err="emulation version needs to be greater or equal to 1.31, got 1.23.0-alpha.1.24689"
```
### Anything else we need to know?
_No response_
### Kubernetes version
<details>
```console
$ kubectl version
Client Version: v1.31.2
Kustomize Version: v5.4.2
The connection to the server 127.0.0.1:62205 was refused - did you specify the right host or port?
```
</details>
### Cloud provider
<details>
</details>
### OS version
<details>
```console
# On mac
Darwin KMacBook-Pro.local 24.1.0 Darwin Kernel Version 24.1.0
</details>
### Install tools
<details>
</details>
### Container runtime (CRI) and version (if applicable)
<details>
containerd
</details>
### Related plugins (CNI, CSI, ...) and versions (if applicable)
<details>
</details>
| kind/bug,sig/testing,sig/release,needs-triage | low | Critical |
2,813,256,319 | pytorch | [Performance] `tensordot` has substantial overhead | ### 🐛 Describe the bug
`torch.tensordot(A, B)` is ~50% slower than `torch.dot(A.flatten(), B.flatten())` for matrices of size≤512 on GPU, and on CPU it is even slower than `torch.trace(A.T @ B)` until n=1024.
## Why this matters
A common mistake is to compute a quantity expressed in a math textbook / paper like $\text{trace}(A^T B)$ naively how it is written, which is $O(n^3)$, when it could be computed as $\langle A \mid B \rangle_{F} = \sum_{ij} A_{ij}B_{ij}$ which is $O(n^2)$. (The former computes all off-diagonal entries of the matrix product, which are irrelevant for the trace).
This would make a good lint rule, but the most natural implementation of the Frobenius inner product, which is `tensordot`, has this huge overhead and so should be currently avoided for small matrices.
## Expectation
`tensordot(A, B)` should not be substantially slower than `torch.dot(A.flatten(), B.flatten())`.
## References:
- https://github.com/numpy/numpy/issues/25713
- https://github.com/astral-sh/ruff/issues/9664
- Code: https://gist.github.com/randolf-scholz/9b166ff6b112820d123037448369a0b7
### Versions
<details>
Collecting environment information...
PyTorch version: 2.5.1+cu124
Is debug build: False
CUDA used to build PyTorch: 12.4
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.5 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.0-1ubuntu1.1
CMake version: version 3.31.2
Libc version: glibc-2.35
Python version: 3.12.8 (main, Dec 4 2024, 08:54:12) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-6.8.0-51-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.8.61
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3060
Nvidia driver version: 570.86.10
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_cnn.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_graph.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_heuristic.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops.so.9.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.7
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.7
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 39 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 16
On-line CPU(s) list: 0-15
Vendor ID: GenuineIntel
Model name: 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
CPU family: 6
Model: 141
Thread(s) per core: 2
Core(s) per socket: 8
Socket(s): 1
Stepping: 1
CPU max MHz: 4800,0000
CPU min MHz: 800,0000
BogoMIPS: 4992.00
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l2 cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq rdpid movdiri movdir64b fsrm avx512_vp2intersect md_clear ibt flush_l1d arch_capabilities
Virtualization: VT-x
L1d cache: 384 KiB (8 instances)
L1i cache: 256 KiB (8 instances)
L2 cache: 10 MiB (8 instances)
L3 cache: 24 MiB (1 instance)
NUMA node(s): 1
NUMA node0 CPU(s): 0-15
Vulnerability Gather data sampling: Mitigation; Microcode
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI SW loop, KVM SW loop
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Versions of relevant libraries:
[pip3] mypy==1.14.1
[pip3] mypy-extensions==1.0.0
[pip3] numpy==2.2.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-nccl-cu12==2.21.5
[pip3] nvidia-nvjitlink-cu12==12.4.127
[pip3] nvidia-nvtx-cu12==12.4.127
[pip3] torch==2.5.1
[pip3] torchinfo==1.8.0
[pip3] triton==3.1.0
[conda] Could not collect
</details>
cc @msaroufim @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano | module: performance,module: linear algebra | low | Critical |
2,813,260,159 | go | runtime: reportZombies throws "found pointer to free object" in sweeper | ```
#!stacks
"reportZombies:+34" && "runtime.goexit"
```
Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).
This stack `Ytavxw` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2025-01-25.json):
- `crash/crash`
- [`runtime.throw:+9`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/panic.go;l=1067)
- [`runtime.(*mspan).reportZombies:+34`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=890)
- [`runtime.(*sweepLocked).sweep:+160`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=658)
- [`runtime.sweepone:+37`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=389)
- [`runtime.bgsweep:+28`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgcsweep.go;l=298)
- [`runtime.gcenable.gowrap1:+0`](https://cs.opensource.google/go/go/+/go1.23.4:src/runtime/mgc.go;l=204)
- `runtime.goexit:+0`
```
golang.org/x/tools/[email protected] go1.23.4 linux/amd64 vscode (1)
```
@prattmic | NeedsInvestigation,Tools,gopls/telemetry-wins,BugReport | low | Critical |
2,813,288,830 | rust | Rustc crashes at compiler/rustc_middle/src/ty/instance.rs, caused by assertion `left matches right` failed | <!--
Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->
### Code
Note that if we remove the first line `#![feature(min_generic_const_args)]`, the panic disappeares.
```Rust
#![feature(min_generic_const_args)]
struct U;
struct S<const N: U>()
where
S<{ U }>:;
fn main() {}
```
### 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.86.0-nightly (f85c6de55 2025-01-26)
binary: rustc
commit-hash: f85c6de55206dbee5ffedfd821df1503a7b92346
commit-date: 2025-01-26
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
```
### Error output
```
arning: the feature `min_generic_const_args` is incomplete and may not be safe to use and/or cause compiler crashes
--> 1.rs:1:12
|
1 | #![feature(min_generic_const_args)]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #132980 <https://github.com/rust-lang/rust/issues/132980> for more information
= note: `#[warn(incomplete_features)]` on by default
thread 'rustc' panicked at compiler/rustc_middle/src/ty/instance.rs:531:9:
assertion `left matches right` failed: `Instance::try_resolve` should only be used to resolve instances of functions, statics, and consts; to resolve associated types, use `try_normalize_erasing_regions`.
left: Ctor(Struct, Const)
right: DefKind::Fn | DefKind::AssocFn | DefKind::Const | DefKind::AssocConst |
DefKind::AnonConst | DefKind::InlineConst | DefKind::Static { .. } |
DefKind::Ctor(_, CtorKind::Fn) | DefKind::Closure |
DefKind::SyntheticCoroutineBody
stack backtrace:
0: 0x7fa280d3c210 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hec9bc6463e252640
1: 0x7fa2815acee6 - core::fmt::write::h962cad0079919c7e
2: 0x7fa2824aac51 - std::io::Write::write_fmt::h081e59591f35f868
3: 0x7fa280d3c072 - std::sys::backtrace::BacktraceLock::print::he0deffbd85e9a2c5
4: 0x7fa280d3e4f2 - std::panicking::default_hook::{{closure}}::h99776b3a5456e866
5: 0x7fa280d3e37a - std::panicking::default_hook::hcad38b9ed4b5517d
6: 0x7fa27fef3279 - std[cc940dec3ff43b12]::panicking::update_hook::<alloc[5f7a888829935c2b]::boxed::Box<rustc_driver_impl[af2bdb3744899392]::install_ice_hook::{closure#1}>>::{closure#0}
7: 0x7fa280d3f073 - std::panicking::rust_panic_with_hook::hbfeeff1ab3569ba1
8: 0x7fa280d3ed6a - std::panicking::begin_panic_handler::{{closure}}::h32c93c4f5d28ab99
9: 0x7fa280d3c6e9 - std::sys::backtrace::__rust_end_short_backtrace::h1884c239824d44f7
10: 0x7fa280d3ea2d - rust_begin_unwind
11: 0x7fa27d9d1bd0 - core::panicking::panic_fmt::he58927c3c03479ba
12: 0x7fa27f915586 - core::panicking::assert_failed_inner::hfb3c935e17727acd
13: 0x7fa28049b942 - core[c1de5c9ad145c0db]::panicking::assert_matches_failed::<rustc_hir[2d8a80fbfdaaf69c]::def::DefKind>
14: 0x7fa2817a1f93 - <rustc_middle[ea35cf57050946b4]::ty::instance::Instance>::try_resolve
15: 0x7fa282284cf1 - <rustc_middle[ea35cf57050946b4]::ty::context::TyCtxt>::const_eval_resolve_for_typeck
16: 0x7fa282284a77 - rustc_trait_selection[9f2c8c71993b8584]::traits::try_evaluate_const
17: 0x7fa282284513 - <rustc_trait_selection[9f2c8c71993b8584]::traits::normalize::AssocTypeNormalizer as rustc_type_ir[de1b3d84f3386c16]::fold::TypeFolder<rustc_middle[ea35cf57050946b4]::ty::context::TyCtxt>>::fold_const
18: 0x7fa281dd0361 - <rustc_trait_selection[9f2c8c71993b8584]::traits::normalize::AssocTypeNormalizer as rustc_type_ir[de1b3d84f3386c16]::fold::FallibleTypeFolder<rustc_middle[ea35cf57050946b4]::ty::context::TyCtxt>>::try_fold_binder::<rustc_type_ir[de1b3d84f3386c16]::predicate_kind::PredicateKind<rustc_middle[ea35cf57050946b4]::ty::context::TyCtxt>>
19: 0x7fa2819bcdb8 - rustc_trait_selection[9f2c8c71993b8584]::traits::normalize::normalize_with_depth_to::<rustc_middle[ea35cf57050946b4]::ty::predicate::Predicate>
20: 0x7fa2819bbb57 - rustc_trait_selection[9f2c8c71993b8584]::traits::wf::clause_obligations
21: 0x7fa2819c0388 - rustc_hir_analysis[ce12ae6d63b57b8a]::check::wfcheck::check_where_clauses
22: 0x7fa281bd5e00 - rustc_hir_analysis[ce12ae6d63b57b8a]::check::wfcheck::check_type_defn
23: 0x7fa281bcf821 - rustc_hir_analysis[ce12ae6d63b57b8a]::check::wfcheck::check_well_formed
24: 0x7fa281bce247 - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::check_well_formed::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>>
25: 0x7fa281bcdce9 - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_data_structures[aef26e4d10f0fc6d]::vec_cache::VecCache<rustc_span[d5a27b28009c9e0]::def_id::LocalDefId, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>, rustc_query_system[b5c6449b7ccd2566]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
26: 0x7fa281bcd746 - rustc_query_impl[52b9445d4dcf70be]::query_impl::check_well_formed::get_query_non_incr::__rust_end_short_backtrace
27: 0x7fa281bcb36c - rustc_hir_analysis[ce12ae6d63b57b8a]::check::wfcheck::check_mod_type_wf
28: 0x7fa281bcb18b - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::check_mod_type_wf::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>>
29: 0x7fa2824b2ac8 - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_query_system[b5c6449b7ccd2566]::query::caches::DefaultCache<rustc_span[d5a27b28009c9e0]::def_id::LocalModDefId, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
30: 0x7fa2824b2870 - rustc_query_impl[52b9445d4dcf70be]::query_impl::check_mod_type_wf::get_query_non_incr::__rust_end_short_backtrace
31: 0x7fa2819371e6 - rustc_hir_analysis[ce12ae6d63b57b8a]::check_crate
32: 0x7fa281933aa2 - rustc_interface[d0d5d02e7a56d74f]::passes::run_required_analyses
33: 0x7fa2824a635e - rustc_interface[d0d5d02e7a56d74f]::passes::analysis
34: 0x7fa2824a632f - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 0usize]>>
35: 0x7fa282493315 - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_query_system[b5c6449b7ccd2566]::query::caches::SingleCache<rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 0usize]>>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
36: 0x7fa28249304e - rustc_query_impl[52b9445d4dcf70be]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
37: 0x7fa2824b9429 - rustc_interface[d0d5d02e7a56d74f]::passes::create_and_enter_global_ctxt::<core[c1de5c9ad145c0db]::option::Option<rustc_interface[d0d5d02e7a56d74f]::queries::Linker>, rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
38: 0x7fa282504213 - rustc_interface[d0d5d02e7a56d74f]::interface::run_compiler::<(), rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}>::{closure#1}
39: 0x7fa282400eb5 - std[cc940dec3ff43b12]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_with_globals<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_pool_with_globals<rustc_interface[d0d5d02e7a56d74f]::interface::run_compiler<(), rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>
40: 0x7fa282400b99 - <<std[cc940dec3ff43b12]::thread::Builder>::spawn_unchecked_<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_with_globals<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_pool_with_globals<rustc_interface[d0d5d02e7a56d74f]::interface::run_compiler<(), rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core[c1de5c9ad145c0db]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
41: 0x7fa28240032b - std::sys::pal::unix::thread::Thread::new::thread_start::hb22e947f5885a296
42: 0x7fa27c756609 - start_thread
at /build/glibc-LcI20x/glibc-2.31/nptl/pthread_create.c:477:8
43: 0x7fa27c67b353 - clone
at /build/glibc-LcI20x/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95:0
44: 0x0 - <unknown>
error: the compiler unexpectedly panicked. this is a bug.
```
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Backtrace</strong></summary>
<p>
```
<backtrace>
```
</p>
</details>
| I-ICE,T-compiler,C-bug,needs-triage | low | Critical |
2,813,304,217 | rust | Rustc crashes at `compiler/rustc_hir_analysis/src/hir_ty_lowering/mod.rs:2156:17` | <!--
Thank you for finding an Internal Compiler Error! 🧊 If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.
http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/
-->
### Code
Maybe related to #136138. Similarly, if we remove the first line `#!feature(min_generic_const_args)]`, the panic disappears.
However, the stack trace is totally different.
```Rust
#![feature(min_generic_const_args)]
static A: u32 = 0;
struct Foo<const N: u32>;
const B: Foo<{ A }> = Foo;
fn main() {}
```
### 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.86.0-nightly (f85c6de55 2025-01-26)
binary: rustc
commit-hash: f85c6de55206dbee5ffedfd821df1503a7b92346
commit-date: 2025-01-26
host: x86_64-unknown-linux-gnu
release: 1.86.0-nightly
LLVM version: 19.1.7
```
### Error output
```
warning: the feature `min_generic_const_args` is incomplete and may not be safe to use and/or cause compiler crashes
--> 2.rs:1:12
|
1 | #![feature(min_generic_const_args)]
| ^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #132980 <https://github.com/rust-lang/rust/issues/132980> for more information
= note: `#[warn(incomplete_features)]` on by default
error: internal compiler error: compiler/rustc_hir_analysis/src/hir_ty_lowering/mod.rs:2156:17: use of bare `static` ConstArgKind::Path's not yet supported
--> 2.rs:4:16
|
4 | const B: Foo<{ A }> = Foo;
| ^
thread 'rustc' panicked at compiler/rustc_hir_analysis/src/hir_ty_lowering/mod.rs:2156:17:
Box<dyn Any>
stack backtrace:
0: 0x7fe42260a210 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::hec9bc6463e252640
1: 0x7fe422e7aee6 - core::fmt::write::h962cad0079919c7e
2: 0x7fe423d78c51 - std::io::Write::write_fmt::h081e59591f35f868
3: 0x7fe42260a072 - std::sys::backtrace::BacktraceLock::print::he0deffbd85e9a2c5
4: 0x7fe42260c4f2 - std::panicking::default_hook::{{closure}}::h99776b3a5456e866
5: 0x7fe42260c37a - std::panicking::default_hook::hcad38b9ed4b5517d
6: 0x7fe4217c1279 - std[cc940dec3ff43b12]::panicking::update_hook::<alloc[5f7a888829935c2b]::boxed::Box<rustc_driver_impl[af2bdb3744899392]::install_ice_hook::{closure#1}>>::{closure#0}
7: 0x7fe42260d073 - std::panicking::rust_panic_with_hook::hbfeeff1ab3569ba1
8: 0x7fe4217fbf41 - std[cc940dec3ff43b12]::panicking::begin_panic::<rustc_errors[b2f066873e334d61]::ExplicitBug>::{closure#0}
9: 0x7fe4217f0e46 - std[cc940dec3ff43b12]::sys::backtrace::__rust_end_short_backtrace::<std[cc940dec3ff43b12]::panicking::begin_panic<rustc_errors[b2f066873e334d61]::ExplicitBug>::{closure#0}, !>
10: 0x7fe4217f0e33 - std[cc940dec3ff43b12]::panicking::begin_panic::<rustc_errors[b2f066873e334d61]::ExplicitBug>
11: 0x7fe421805e71 - <rustc_errors[b2f066873e334d61]::diagnostic::BugAbort as rustc_errors[b2f066873e334d61]::diagnostic::EmissionGuarantee>::emit_producing_guarantee
12: 0x7fe421d63bdc - <rustc_errors[b2f066873e334d61]::DiagCtxtHandle>::span_bug::<rustc_span[d5a27b28009c9e0]::span_encoding::Span, alloc[5f7a888829935c2b]::string::String>
13: 0x7fe421de62d7 - rustc_middle[ea35cf57050946b4]::util::bug::opt_span_bug_fmt::<rustc_span[d5a27b28009c9e0]::span_encoding::Span>::{closure#0}
14: 0x7fe421dcf34a - rustc_middle[ea35cf57050946b4]::ty::context::tls::with_opt::<rustc_middle[ea35cf57050946b4]::util::bug::opt_span_bug_fmt<rustc_span[d5a27b28009c9e0]::span_encoding::Span>::{closure#0}, !>::{closure#0}
15: 0x7fe421dcf1db - rustc_middle[ea35cf57050946b4]::ty::context::tls::with_context_opt::<rustc_middle[ea35cf57050946b4]::ty::context::tls::with_opt<rustc_middle[ea35cf57050946b4]::util::bug::opt_span_bug_fmt<rustc_span[d5a27b28009c9e0]::span_encoding::Span>::{closure#0}, !>::{closure#0}, !>
16: 0x7fe42080d097 - rustc_middle[ea35cf57050946b4]::util::bug::span_bug_fmt::<rustc_span[d5a27b28009c9e0]::span_encoding::Span>
17: 0x7fe4248251c9 - <dyn rustc_hir_analysis[ce12ae6d63b57b8a]::hir_ty_lowering::HirTyLowerer>::lower_const_arg.cold
18: 0x7fe4237fafc6 - <dyn rustc_hir_analysis[ce12ae6d63b57b8a]::hir_ty_lowering::HirTyLowerer>::lower_path
19: 0x7fe4237f56e0 - <dyn rustc_hir_analysis[ce12ae6d63b57b8a]::hir_ty_lowering::HirTyLowerer>::lower_ty
20: 0x7fe42319cefe - rustc_hir_analysis[ce12ae6d63b57b8a]::collect::type_of::type_of
21: 0x7fe4231985fe - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::type_of::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 8usize]>>
22: 0x7fe42319739f - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_query_system[b5c6449b7ccd2566]::query::caches::DefIdCache<rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 8usize]>>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
23: 0x7fe423196f2b - rustc_query_impl[52b9445d4dcf70be]::query_impl::type_of::get_query_non_incr::__rust_end_short_backtrace
24: 0x7fe4234939a3 - <rustc_hir_analysis[ce12ae6d63b57b8a]::collect::CollectItemTypesVisitor as rustc_hir[2d8a80fbfdaaf69c]::intravisit::Visitor>::visit_item
25: 0x7fe42349c42d - rustc_hir_analysis[ce12ae6d63b57b8a]::check::wfcheck::check_well_formed
26: 0x7fe42349c247 - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::check_well_formed::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>>
27: 0x7fe42349bce9 - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_data_structures[aef26e4d10f0fc6d]::vec_cache::VecCache<rustc_span[d5a27b28009c9e0]::def_id::LocalDefId, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>, rustc_query_system[b5c6449b7ccd2566]::dep_graph::graph::DepNodeIndex>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
28: 0x7fe42349b746 - rustc_query_impl[52b9445d4dcf70be]::query_impl::check_well_formed::get_query_non_incr::__rust_end_short_backtrace
29: 0x7fe42349936c - rustc_hir_analysis[ce12ae6d63b57b8a]::check::wfcheck::check_mod_type_wf
30: 0x7fe42349918b - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::check_mod_type_wf::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>>
31: 0x7fe423d80ac8 - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_query_system[b5c6449b7ccd2566]::query::caches::DefaultCache<rustc_span[d5a27b28009c9e0]::def_id::LocalModDefId, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 1usize]>>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
32: 0x7fe423d80870 - rustc_query_impl[52b9445d4dcf70be]::query_impl::check_mod_type_wf::get_query_non_incr::__rust_end_short_backtrace
33: 0x7fe4232051e6 - rustc_hir_analysis[ce12ae6d63b57b8a]::check_crate
34: 0x7fe423201aa2 - rustc_interface[d0d5d02e7a56d74f]::passes::run_required_analyses
35: 0x7fe423d7435e - rustc_interface[d0d5d02e7a56d74f]::passes::analysis
36: 0x7fe423d7432f - rustc_query_impl[52b9445d4dcf70be]::plumbing::__rust_begin_short_backtrace::<rustc_query_impl[52b9445d4dcf70be]::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 0usize]>>
37: 0x7fe423d61315 - rustc_query_system[b5c6449b7ccd2566]::query::plumbing::try_execute_query::<rustc_query_impl[52b9445d4dcf70be]::DynamicConfig<rustc_query_system[b5c6449b7ccd2566]::query::caches::SingleCache<rustc_middle[ea35cf57050946b4]::query::erase::Erased<[u8; 0usize]>>, false, false, false>, rustc_query_impl[52b9445d4dcf70be]::plumbing::QueryCtxt, false>
38: 0x7fe423d6104e - rustc_query_impl[52b9445d4dcf70be]::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
39: 0x7fe423d87429 - rustc_interface[d0d5d02e7a56d74f]::passes::create_and_enter_global_ctxt::<core[c1de5c9ad145c0db]::option::Option<rustc_interface[d0d5d02e7a56d74f]::queries::Linker>, rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}::{closure#2}>::{closure#2}::{closure#0}
40: 0x7fe423dd2213 - rustc_interface[d0d5d02e7a56d74f]::interface::run_compiler::<(), rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}>::{closure#1}
41: 0x7fe423cceeb5 - std[cc940dec3ff43b12]::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_with_globals<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_pool_with_globals<rustc_interface[d0d5d02e7a56d74f]::interface::run_compiler<(), rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>
42: 0x7fe423cceb99 - <<std[cc940dec3ff43b12]::thread::Builder>::spawn_unchecked_<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_with_globals<rustc_interface[d0d5d02e7a56d74f]::util::run_in_thread_pool_with_globals<rustc_interface[d0d5d02e7a56d74f]::interface::run_compiler<(), rustc_driver_impl[af2bdb3744899392]::run_compiler::{closure#0}>::{closure#1}, ()>::{closure#0}, ()>::{closure#0}::{closure#0}, ()>::{closure#1} as core[c1de5c9ad145c0db]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
43: 0x7fe423cce32b - std::sys::pal::unix::thread::Thread::new::thread_start::hb22e947f5885a296
44: 0x7fe41e024609 - start_thread
at /build/glibc-LcI20x/glibc-2.31/nptl/pthread_create.c:477:8
45: 0x7fe41df49353 - clone
at /build/glibc-LcI20x/glibc-2.31/misc/../sysdeps/unix/sysv/linux/x86_64/clone.S:95:0
46: 0x0 - <unknown>
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: please make sure that you have updated to the latest nightly
note: please attach the file at `/home/nightwish/workspace/compiler/rust_test/2025-01-23/rustc-ice-2025-01-27T15_11_58-25723.txt` to your bug report
query stack during panic:
#0 [type_of] computing type of `B`
#1 [check_well_formed] checking that `B` is well-formed
... and 2 other queries... use `env RUST_BACKTRACE=1` to see the full query stack
error: aborting due to 1 previous error; 1 warning emitted
```
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary><strong>Backtrace</strong></summary>
<p>
```
<backtrace>
```
</p>
</details>
| I-ICE,T-compiler,C-bug,F-min_generic_const_args | low | Critical |
2,813,321,214 | rust | Suggested fix for "cannot find macro `...` in this scope" does not compile | I tried this code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a095133990477eb48c9b42343e5593f4
I expected to see this happen: Using a suggestion "just works".
Instead, this happened: Unexpected and even more confusing error message caused because of #98291.
### Meta
Tested on playground with `1.84.0` (stable) and `1.86.0-nightly (2025-01-26 f85c6de55206dbee5ffe)`. | C-bug,needs-triage | low | Critical |
2,813,335,428 | pytorch | "AssertionError: Guard check failed" on PyTorch nightlies after 2025-01-22 when running torchao tests | ### 🐛 Describe the bug
Running the following command introduces an assertion error on recent versions of PyTorch nightlies:
```
// run a test in torchao repo
// test source code: https://github.com/pytorch/ao/blob/main/test/prototype/test_smoothquant.py
> pytest test/prototype/test_smoothquant.py -s -x
...
if not output_graph.export:
if not self.guard_manager.check(output_graph.local_scope):
reasons = get_guard_fail_reason_helper(
self.guard_manager, # type: ignore[arg-type]
output_graph.local_scope,
CompileContext.current_compile_id(),
)
> raise AssertionError(f"Guard check failed: {reasons}")
E AssertionError: Guard check failed: 0/0: ___check_metadata_139942440334048_c0/0
E
E
E You can suppress this exception and fall back to eager by setting:
E import torch._dynamo
E torch._dynamo.config.suppress_errors = True
```
Full output: https://gist.github.com/vkuzo/b50ac59aa0936fd072250d7544aaa2a9
The nightly from `20250122` does not have this failure, but the nightlies from `20250123` and after do.
### Versions
https://gist.github.com/vkuzo/ddcaa43948a96cf63e58fb71fbdcbf68
cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @amjames | high priority,oncall: pt2,module: dynamo | low | Critical |
2,813,336,086 | vscode | Editor GPU: Ghost text is regular foreground color | Example:
 | bug,editor-gpu | low | Minor |
Subsets and Splits