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,626,116,217 | rust | ICE: malformed `malformed repr(align(N))` | <!--
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
```Rust
trait MyTrait {
#[repr(align)]
fn myfun();
}
```
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
`rustc --version --verbose`:
```
rustc 1.84.0-nightly (759e07f06 2024-10-30)
binary: rustc
commit-hash: 759e07f063fb8e6306ff1bdaeb70af56a878b415
commit-date: 2024-10-30
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```
### Error output
```
<output>
```
<!--
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>
```
warning: trait `MyTrait` is never used
--> a.rs:1:7
|
1 | trait MyTrait {
| ^^^^^^^
|
= note: `#[warn(dead_code)]` on by default
warning: 1 warning emitted
note: no errors encountered even though delayed bugs were created
note: those delayed bugs will now be shown as internal compiler errors
error: internal compiler error: malformed repr(align(N))
--> a.rs:2:12
|
2 | #[repr(align)]
| ^^^^^
|
note: delayed at compiler/rustc_passes/src/check_attr.rs:1932:28
0: <rustc_errors::DiagCtxtInner>::emit_diagnostic
1: <rustc_errors::DiagCtxtHandle>::emit_diagnostic
2: <rustc_span::ErrorGuaranteed as rustc_errors::diagnostic::EmissionGuarantee>::emit_producing_guarantee
3: <rustc_errors::DiagCtxtHandle>::span_delayed_bug::<rustc_span::span_encoding::Span, &str>
4: <rustc_passes::check_attr::CheckAttrVisitor>::check_attributes
5: <rustc_passes::check_attr::CheckAttrVisitor as rustc_hir::intravisit::Visitor>::visit_trait_item
6: rustc_passes::check_attr::check_mod_attrs
7: rustc_query_impl::plumbing::__rust_begin_short_backtrace::<rustc_query_impl::query_impl::check_mod_attrs::dynamic_query::{closure#2}::{closure#0}, rustc_middle::query::erase::Erased<[u8; 0]>>
8: rustc_query_system::query::plumbing::try_execute_query::<rustc_query_impl::DynamicConfig<rustc_query_system::query::caches::DefaultCache<rustc_span::def_id::LocalModDefId, rustc_middle::query::erase::Erased<[u8; 0]>>, false, false, false>, rustc_query_impl::plumbing::QueryCtxt, false>
9: rustc_query_impl::query_impl::check_mod_attrs::get_query_non_incr::__rust_end_short_backtrace
10: <rustc_middle::hir::map::Map>::par_for_each_module::<rustc_interface::passes::run_required_analyses::{closure#0}::{closure#0}::{closure#1}::{closure#0}>::{closure#0}
11: rustc_interface::passes::run_required_analyses
12: rustc_interface::passes::analysis
13: rustc_query_impl::plumbing::__rust_begin_short_backtrace::<rustc_query_impl::query_impl::analysis::dynamic_query::{closure#2}::{closure#0}, rustc_middle::query::erase::Erased<[u8; 1]>>
14: rustc_query_system::query::plumbing::try_execute_query::<rustc_query_impl::DynamicConfig<rustc_query_system::query::caches::SingleCache<rustc_middle::query::erase::Erased<[u8; 1]>>, false, false, false>, rustc_query_impl::plumbing::QueryCtxt, false>
15: rustc_query_impl::query_impl::analysis::get_query_non_incr::__rust_end_short_backtrace
16: rustc_interface::interface::run_compiler::<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}
17: std::sys::backtrace::__rust_begin_short_backtrace::<rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>
18: <<std::thread::Builder>::spawn_unchecked_<rustc_interface::util::run_in_thread_with_globals<rustc_interface::util::run_in_thread_pool_with_globals<rustc_interface::interface::run_compiler<core::result::Result<(), rustc_span::ErrorGuaranteed>, rustc_driver_impl::run_compiler::{closure#0}>::{closure#1}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#0}::{closure#0}, core::result::Result<(), rustc_span::ErrorGuaranteed>>::{closure#1} as core::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
19: std::sys::pal::unix::thread::Thread::new::thread_start
20: <unknown>
21: <unknown>
--> a.rs:2:12
|
2 | #[repr(align)]
| ^^^^^
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 `/tmp/im/rustc-ice-2024-10-31T07_01_17-3418840.txt` to your bug report
note: compiler flags: --crate-type lib
query stack during panic:
end of query stack
```
</p>
</details>
<!-- TRIAGEBOT_START -->
<!-- TRIAGEBOT_ASSIGN_START -->
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"jdonszelmann"}$$TRIAGEBOT_ASSIGN_DATA_END -->
<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END --> | A-attributes,I-ICE,P-low,T-compiler,C-bug,S-bug-has-test,A-repr,A-align | low | Critical |
2,626,127,035 | vscode | Git Source Control: Support keyboard-only staging | <!-- โ ๏ธโ ๏ธ Do Not Delete This! feature_request_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
I have a full keyboard-only workflow; a tiling manager to control windows, shortcuts to switch focus between the editor and terminal, or jump to specific files or lines in files, etc. and I find any contexts where I have to move my hand to my mouse an extreme point of irritation (because I am much much faster than mouse-usage allows)
The git source control tab is a good example of this; there is no reason why there shouldn't be proper keyboard-only support.
I can focus on the source control tab with shift+ctrl+g. I can use my vim-like HJKL arrow keysims to easily go up and down the files. I can press enter/space to look at the diffs.
However, there is no way for me to simply simulate the "+" stage button next to the file. The best I can get is very cumbersome, and not something I want to repeat for 15 files.
a) press tab to focus on the icons, then arrow key to the right twice to get to the + button.
b) open the file, ctrl + a to select all content, then ctrl+shift+p to run the command "stage selected range"
This should be much smoother. Just let me go to a file, review it's content, and press a single key shortcut to decide whether or not to include it in the stage. JJ (jujutsu), and the git interactive clients, let you just press "enter" on the file to stage it before committing.
Proposal:
allow me to create a keyboard-shortcut to stage the file my focus is currently on in the source control tab, AKA for simulating the `+` button. | feature-request,scm | low | Minor |
2,626,215,053 | tensorflow | TensorFlow Stable Delegate Python API | ### Issue type
Support
### Have you reproduced the bug with TensorFlow Nightly?
Yes
### Source
binary
### TensorFlow version
2.16
### Custom code
Yes
### OS platform and distribution
_No response_
### Mobile device
_No response_
### Python version
_No response_
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
_No response_
### GPU model and memory
_No response_
### Current behavior?
TensorFlow Python API currently doesn't support running stable delegates. Are there any workarounds? If not, are there any plans to support this in the future?
### Standalone code to reproduce the issue
```shell
self._model = tf.lite.Interpreter(
model_path=stryolov5.tflite,
experimental_delegates=[delegate.so]
)
```
### Relevant log output
_No response_ | stat:contribution welcome,stat:awaiting tensorflower,type:feature,type:support,comp:lite,TF 2.16 | low | Critical |
2,626,218,830 | react | React Why Not Consider Support Signals | I don't understand why the official team doesn't consider the obvious solution of signal. If subscriptions are cleverly implemented as code snippets that are rewritten as anonymous subcomponents that are remembered and associated with dependencies, it won't go against the sanity of react. Model | Type: Question | low | Major |
2,626,259,519 | pytorch | Improved definition for Hardsigmoid | ### ๐ The feature, motivation and pitch
I was looking at the Hardsigmoid and could not find the origin of the formulation of the PyTorch's implementation of the Hardsigmoid, however, I have mainly seen it in the format $\max(-1, \min(1, \frac{x +1}{2}))$ (https://arxiv.org/pdf/1511.00363v3, https://paperswithcode.com/method/hard-sigmoid, https://stackoverflow.com/questions/35411194/how-is-hard-sigmoid-defined). Would it be possible to add further documentation about where this version was found?
Since it seems like the PyTorch version was just trying to better approximate the original sigmoid function, I was looking into how to best optimize the Hardsigmoid activation function to minimize the error between the two implementations and got the following results:
$$
\begin{align}
y_h &= \alpha x + \frac{1}{2} \\
y_t &= \frac{1}{1 + e^{-x}}
\end{align}
$$
We wish to optimize:
$$
\begin{align}
\int_{0}^{\infty} (y_h - y_t)^2 dx &= -\frac{4 \alpha \left(\pi ^2 \alpha +3\right)+5}{24 \alpha }-2 \alpha \text{Li}_2\left(-e^{\left.\frac{1}{2}\right/\alpha }\right)
\end{align}
$$
(Where $\text{Li}_2\left(\cdot\right)$ represents the polylogarithm function)
From this, getting the derivative:
$$
\begin{align}
\frac{\partial}{\partial \alpha}\left(-\frac{4 \alpha \left(\pi ^2 \alpha +3\right)+5}{24 \alpha }-2 \alpha \text{Li}_2\left(-e^{\left.\frac{1}{2}\right/\alpha }\right)\right) &= \frac{5}{24 \alpha ^2}-\frac{\log \left(e^{\left.\frac{1}{2}\right/\alpha }+1\right)}{\alpha }-2 \text{Li}_2\left(-e^{\left.\frac{1}{2}\right/\alpha }\right)-\frac{\pi ^2}{6}
\end{align}
$$
Where solving for the minimum ends up becoming the problem of finding the root of a univariate transcendental equation and is thus only solvable in a numerical fashion, which gets solved to be $\alpha = 0.1923312226780115801134295966889092989087208992810093155047485229577227369110521531792719079253476632$ with the location where $y_h=1$ would be when $x=\frac{1}{2 \alpha} = 5.199363816628644532311143463905539244263001782697868420503570284299935792120883736036838950460889190$
For the proof, you can verify it using Mathematica:
```mathematica
yt = 1/(1 + Exp[-x])
yh = Max[0, Min[1, (x * \[Alpha] + 1/2)]]
m = Assuming[{Element[\[Alpha], PositiveReals]}, Integrate[(yh - yt)^2, {x, 0, \[Infinity]}]] // FullSimplify
dm = D[m, \[Alpha]] // FullSimplify
s = Solve[dm == 0, \[Alpha], PositiveReals, Assumptions -> {\[Alpha] > 0, \[Alpha] < 1}]
N[s, 100]
N[1/\[Alpha] /. s, 100]
```
This means that the updated activation function should instead be:
$$
\begin{align}
\text{Hardsigmoid}(x) &= \begin{cases}
0 & \text{if } x \leq -\alpha \\
1 & \text{if } x \ge \alpha \\
\alpha x + \frac{1}{2} & \text{otherwise} \\
\end{cases}
\end{align}
$$
Or given the that $\alpha \approx 0.2 = \frac{1}{5}$, so the more optimal version should be:
$$
\begin{align}
\text{Hardsigmoid}(x) &= \begin{cases}
0 & \text{if } x \leq -2.5 \\
1 & \text{if } x \ge 2.5 \\
\frac{x}{5} + \frac{1}{2} & \text{otherwise} \\
\end{cases}
\end{align}
$$
In the case instead, where you want to optimize for only the linear region and minimize just for that you would get the following steps:
$$
\begin{align}
\int_{0}^{\frac{1}{2 \alpha}} (y_h - y_t)^2 dx &= -\frac{\pi ^2 \alpha }{6}+\frac{7}{24 \alpha }-\log \left(e^{\left.\frac{1}{2}\right/\alpha }+1\right)-\frac{1}{2} \tanh \left(\frac{1}{4 \alpha }\right)-2 \alpha \text{Li}_2\left(-e^{\left.\frac{1}{2}\right/\alpha
}\right)
\end{align}
$$
(Where $\text{Li}_2\left(\cdot\right)$ represents the polylogarithm function)
From this, getting the derivative:
$$
\begin{align}
\frac{\partial}{\partial \alpha}\left(-\frac{\pi ^2 \alpha }{6}+\frac{7}{24 \alpha }-\log \left(e^{\left.\frac{1}{2}\right/\alpha }+1\right)-\frac{1}{2} \tanh \left(\frac{1}{4 \alpha }\right)-2 \alpha \text{Li}_2\left(-e^{\left.\frac{1}{2}\right/\alpha
}\right)\right) &= \frac{1}{24} \left(\frac{5-\frac{12}{\left(e^{\left.\frac{1}{2}\right/\alpha }+1\right)^2}}{\alpha ^2}-4 \pi ^2\right)-\frac{\log \left(e^{\left.\frac{1}{2}\right/\alpha }+1\right)}{\alpha }-2
\text{Li}_2\left(-e^{\left.\frac{1}{2}\right/\alpha }\right)
\end{align}
$$
Where solving for the minimum ends up becoming the problem of finding the root of a univariate transcendental equation again and is thus again only solvable in a numerical fashion, which gets solved to be $\alpha = 0.2054970267158964682036128983042348752082936695690816078237062763532105813855967891118081176897595642$ with the location where $y_h=1$ would be when $x=\frac{1}{2 \alpha} = 4.866250456180657743562901938100164679280222850465078977748315073324396050720004715397234973684419269$
The Mathematica proof for this is:
```mathematica
yt = 1/(1 + Exp[-x])
yh = Max[0, Min[1, (x * \[Alpha] + 1/2)]]
m = Assuming[{Element[\[Alpha], PositiveReals]}, Integrate[(yh - yt)^2, {x, 0, 1/(2 \[Alpha])}]] // FullSimplify
dm = D[m, \[Alpha]] // FullSimplify
s = Solve[dm == 0, \[Alpha], PositiveReals, Assumptions -> {\[Alpha] > 0, \[Alpha] < 1}]
N[s, 100]
N[1/\[Alpha] /. s, 100]
```
Where this optimal value also ends up having $\alpha \approx 0.2 = \frac{1}{5}$.
(The different Hardsigmoid functions)
### Alternatives
_No response_
### Additional context
_No response_
cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki | module: nn,triaged | low | Critical |
2,626,265,624 | transformers | RoBERTa is not well implemented for tokenizers with pad_token_id != 1 | ### Feature request
I would like to request that RoBERTa models correctly accept tokenizers with pad_token_id != 1. This problem is inherit from [`fairseq`](https://github.com/facebookresearch/fairseq/blob/ecbf110e1eb43861214b05fa001eff584954f65a/fairseq/utils.py#L266) code.
### Motivation
**Problem Definition**
The current implementation of [Roberta](https://github.com/huggingface/transformers/tree/main/src/transformers/models/roberta) in transformers considers that the tokenizer has pad_token_id = 1:
- In the [TF implementation](https://github.com/huggingface/transformers/blob/405b56269812056d9593869e22b7b264d806cb1e/src/transformers/models/roberta/modeling_tf_roberta.py#L76) the pad token is explicitly set to 1.
- In all the implementations, the class `create_position_ids_from_input_ids` indirectly considers the pad_token_id = 1 in all the classes. ([modeling_roberta.py](https://github.com/huggingface/transformers/blob/9f06fb05059a973048f5865e7e385c9db5d6daa4/src/transformers/models/roberta/modeling_roberta.py#L1682), [modeling_tf_roberta.py](https://github.com/huggingface/transformers/blob/405b56269812056d9593869e22b7b264d806cb1e/src/transformers/models/roberta/modeling_tf_roberta.py#L125) and [modeling_flax_roberta.py](https://github.com/huggingface/transformers/blob/9f06fb05059a973048f5865e7e385c9db5d6daa4/src/transformers/models/roberta/modeling_flax_roberta.py#L73)).
**Motivation**
We have pre-trained a RoBERTa with another tokenizer from scratch and need to slightly change the current implementation to work correctly. The changes are minimal in `create_position_ids_from_input_ids`, we just need to change the `+ padding_idx` terms for `+ 1` terms in the incremental positions. This change will not affect the original implementations of RoBERTa.
### Your contribution
I can submit a PR with the modifications if you agree with the incorporation of this change. | Feature request,Good Difficult Issue | low | Minor |
2,626,266,352 | pytorch | RuntimeError: free_upper_bound + pytorch_used_bytes[device] <= device_total INTERNAL ASSERT FAILED at "../c10/cuda/CUDAMallocAsyncAllocator.cpp":527 | ### ๐ Describe the bug
!!! Exception during processing!!! free_upper_bound + pytorch_used_bytes[device] <= device_total INTERNAL ASSERT FAILED at "../c10/cuda/CUDAMallocAsyncAllocator.cpp":527, please report a bug to PyTorch.
Traceback (most recent call last):
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/execution.py", line 152, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/execution.py", line 82, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/execution.py", line 75, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/custom_nodes/ComfyUI-LivePortraitKJ/nodes.py", line 333, in process
output_video_path, _ = self.pipline.execute(self.args)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/custom_nodes/ComfyUI-LivePortraitKJ/liveportrait/live_portrait_pipeline.py", line 214, in execute
x_s_info = self.live_portrait_wrapper.get_kp_info(I_s)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/custom_nodes/ComfyUI-LivePortraitKJ/liveportrait/live_portrait_wrapper.py", line 132, in get_kp_info
kp_info = self.motion_extractor(x)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/custom_nodes/ComfyUI-LivePortraitKJ/liveportrait/modules/motion_extractor.py", line 34, in forward
out = self.detector(x)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/custom_nodes/ComfyUI-LivePortraitKJ/liveportrait/modules/convnextv2.py", line 120, in forward
x = self.forward_features(x)
File "/opt/conda/lib/python3.9/site-packages/live_photo/ComfyUI/custom_nodes/ComfyUI-LivePortraitKJ/liveportrait/modules/convnextv2.py", line 115, in forward_features
x = self.downsample_layers[i](x)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/container.py", line 217, in forward
input = module(input)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 463, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/opt/conda/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 459, in _conv_forward
return F.conv2d(input, weight, bias, self.stride,
RuntimeError: free_upper_bound + pytorch_used_bytes[device] <= device_total INTERNAL ASSERT FAILED at "../c10/cuda/CUDAMallocAsyncAllocator.cpp":527, please report a bug to PyTorch.
### Versions
PyTorch version: 2.0.0+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A
OS: CentOS Linux 7 (Core) (x86_64)
GCC version: (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Clang version: Could not collect
CMake version: version 3.30.1
Libc version: glibc-2.17
Python version: 3.9.12 (main, Apr 5 2022, 06:56:58) [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-4.19.46-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA L40
Nvidia driver version: 525.125.06
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 112
On-line CPU(s) list: 0-111
Thread(s) per core: 2
Core(s) per socket: 28
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 106
Model name: Intel(R) Xeon(R) Gold 6348 CPU @ 2.60GHz
Stepping: 6
CPU MHz: 3400.000
CPU max MHz: 3500.0000
CPU min MHz: 800.0000
BogoMIPS: 5200.00
Virtualization: VT-x
L1d cache: 48K
L1i cache: 32K
L2 cache: 1280K
L3 cache: 43008K
NUMA node0 CPU(s): 0-27,56-83
NUMA node1 CPU(s): 28-55,84-111
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 pni pclmulqdq dtes64 ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 invpcid_single ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq rdpid md_clear pconfig flush_l1d arch_capabilities
Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] nvidia-cublas-cu11==11.10.3.66
[pip3] nvidia-cuda-cupti-cu11==11.7.101
[pip3] nvidia-cuda-nvrtc-cu11==11.7.99
[pip3] nvidia-cuda-runtime-cu11==11.7.99
[pip3] nvidia-cudnn-cu11==8.5.0.96
[pip3] nvidia-cufft-cu11==10.9.0.58
[pip3] nvidia-curand-cu11==10.2.10.91
[pip3] nvidia-cusolver-cu11==11.4.0.1
[pip3] nvidia-cusparse-cu11==11.7.4.91
[pip3] nvidia-nccl-cu11==2.14.3
[pip3] nvidia-nvtx-cu11==11.7.91
[pip3] onnx==1.17.0
[pip3] onnx2torch==1.5.15
[pip3] onnxruntime==1.16.3
[pip3] onnxruntime-gpu==1.16.3
[pip3] open_clip_torch==2.29.0
[pip3] torch==2.0.0
[pip3] torchaudio==2.0.1
[pip3] torchsde==0.2.6
[pip3] torchvision==0.15.1
[pip3] triton==2.0.0
[conda] numpy 1.26.4 pypi_0 pypi
[conda] nvidia-cublas-cu11 11.10.3.66 pypi_0 pypi
[conda] nvidia-cuda-cupti-cu11 11.7.101 pypi_0 pypi
[conda] nvidia-cuda-nvrtc-cu11 11.7.99 pypi_0 pypi
[conda] nvidia-cuda-runtime-cu11 11.7.99 pypi_0 pypi
[conda] nvidia-cudnn-cu11 8.5.0.96 pypi_0 pypi
[conda] nvidia-cufft-cu11 10.9.0.58 pypi_0 pypi
[conda] nvidia-curand-cu11 10.2.10.91 pypi_0 pypi
[conda] nvidia-cusolver-cu11 11.4.0.1 pypi_0 pypi
[conda] nvidia-cusparse-cu11 11.7.4.91 pypi_0 pypi
[conda] nvidia-nccl-cu11 2.14.3 pypi_0 pypi
[conda] nvidia-nvtx-cu11 11.7.91 pypi_0 pypi
[conda] onnx2torch 1.5.15 pypi_0 pypi
[conda] open-clip-torch 2.29.0 pypi_0 pypi
[conda] torch 2.0.0 pypi_0 pypi
[conda] torchaudio 2.0.1 pypi_0 pypi
[conda] torchsde 0.2.6 pypi_0 pypi
[conda] torchvision 0.15.1 pypi_0 pypi
[conda] triton 2.0.0 pypi_0 pypi
cc @ptrblck @msaroufim | module: cuda,triaged | low | Critical |
2,626,287,707 | godot | `OptionButton` popup does not close properly when requested | ### Tested versions
4.3
### System information
Windows 11
### Issue description
Some of the OptionButton's popup in the editor does not close by a single click, instead an empty popup show up:
### Steps to reproduce
^^
### Minimal reproduction project (MRP)
No need, too easy to reproduce. | bug,topic:gui | low | Critical |
2,626,357,634 | PowerToys | The "Move Newly Created Windows to their last known zone" affects child windows | ### Microsoft PowerToys version
0.85.1
### Installation method
Microsoft Store
### Running as admin
No
### Area(s) with issue?
FancyZones
### Steps to reproduce
1. Check "Move Newly Created Windows to their last known zone"
2. Uncheck "Allow child windows snapping"
3. Open Excel
4. Press control+F to open the Find dialog; it maximizes to fit the current zone Excel is in
5. Same happens to any child Excel window that is sizeable
### โ๏ธ Expected Behavior
I expect child windows of apps to stay in their last known position, as controlled by their parent application, when "Allow child windows snapping" is unchecked.
### โ Actual Behavior
Excel child windows (the ones that are sizeable) snap to the fancyzones grid and hence become very large.
### Other Software
Microsoft Windows 10 Pro 64 bit
Version 10.0.19045
Build 19045
Microsoftยฎ Excelยฎ for Microsoft 365 MSO (Version 2409 Build 16.0.18025.20160) 32-bit | Issue-Bug,Needs-Triage | low | Minor |
2,626,368,416 | opencv | Config opencv support cuda environment | ### System Information
OpenCV version: 4.8.1
Operating System / Platform: ubuntu 22.04
compiler: gcc 11.4.0
Cuda compilation tools, release: 12.6
FFmpeg version: n5.1.4
opencv: 4.8.1
opencv_contrib: 4.8.1
### Detailed description
<img width="452" alt="image" src="https://github.com/user-attachments/assets/8f14571b-267a-4c7d-bc59-c44fe6aaf52d">
<img width="462" alt="image" src="https://github.com/user-attachments/assets/a345cbd6-02fb-4e41-8280-9d1c4be07e48">
<img width="567" alt="image" src="https://github.com/user-attachments/assets/600df4d0-bd5c-4a0b-bfeb-46c847363f4e">
Above was I used the command:
cd opencv
mkdir build
cmake -D WITH_CUDA=ON -D CUDA_TOOLKIT_ROOT_DIR=/usr/local/cuda -D OPENCV_EXTRA_MODULES_PATH=../../opencv_contrib/modules ..
make
### Steps to reproduce
The full process:
git clone https://github.com/opencv/opencv_contrib.git
git clone https://github.com/opencv/opencv.git
cd opencv
mkdir build
cd build
cmake -D WITH_CUDA=ON -D CUDA_TOOLKIT_ROOT_DIR=/usr/local/cuda -D OPENCV_EXTRA_MODULES_PATH=../../opencv_contrib/modules ..
make
### Issue submission checklist
- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc) | bug | low | Major |
2,626,381,230 | flutter | Layout with ListTile -> subtitle -> InputDecorator -> Container (without child) throws RenderBox.size accessed beyond the scope of resize | ### Steps to reproduce
Run Code sample
### Expected results
No console errors
### Actual results
console errors
```
โโโก EXCEPTION CAUGHT BY RENDERING LIBRARY โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
The following assertion was thrown during performLayout():
Assertion failed: file:///opt/flutter/packages/flutter/lib/src/rendering/box.dart:2178:16
sizeAccessAllowed
"RenderBox.size accessed beyond the scope of resize, layout, or permitted parent access. RenderBox
can always access its own size, otherwise, the only object that is allowed to read RenderBox.size is
its parent, if they have said they will. It you hit this assert trying to access a child's size,
pass \"parentUsesSize: true\" to that child's layout() in RenderLimitedBox.performLayout."
```
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
/// Flutter code sample for [ListTile].
void main() => runApp(const ListTileApp());
class ListTileApp extends StatelessWidget {
const ListTileApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp(
theme: ThemeData(useMaterial3: true),
home: const ListTileExample(),
);
}
}
class ListTileExample extends StatelessWidget {
const ListTileExample({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(title: const Text('ListTile Sample')),
body: ListTile(
title: Text(
'One-line ListTile',
),
subtitle: InputDecorator(
decoration: InputDecoration(),
child: Container(),
),
),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
[โ] Flutter (Channel stable, 3.24.3, on macOS 15.0 24A335 darwin-arm64, locale en-US)
โข Flutter version 3.24.3 on channel stable at /Users/vasilich/fvm/versions/3.24.3
โข Upstream repository https://github.com/flutter/flutter.git
โข Framework revision 2663184aa7 (7 weeks ago), 2024-09-11 16:27:48 -0500
โข Engine revision 36335019a8
โข Dart version 3.5.3
โข DevTools version 2.37.3
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
โข Android SDK at /Users/vasilich/Library/Android/sdk
โ cmdline-tools component is missing
Run `path/to/sdkmanager --install "cmdline-tools;latest"`
See https://developer.android.com/studio/command-line for more details.
โ Android license status unknown.
Run `flutter doctor --android-licenses` to accept the SDK licenses.
See https://flutter.dev/to/macos-android-setup for more details.
[โ] Xcode - develop for iOS and macOS (Xcode 16.0)
โข Xcode at /Applications/Xcode.app/Contents/Developer
โข Build 16A242d
โข CocoaPods version 1.15.2
[โ] Chrome - develop for the web
โข Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[โ] Android Studio (version 2024.1)
โข Android Studio at /Applications/Android Studio Koala.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)
[!] Android Studio (version unknown)
โข Android Studio at /Applications/Android Studio Preview.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
โ Unable to determine Android Studio version.
โข Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
[โ] 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)
[โ] IntelliJ IDEA Ultimate Edition (version 2024.2.2)
โข IntelliJ at /Applications/IntelliJ IDEA.app
โข Flutter plugin version 81.1.3
โข Dart plugin version 242.22855.32
[โ] IntelliJ IDEA Community Edition (version 2024.2.2)
โข IntelliJ at /Applications/IntelliJ IDEA CE.app
โข Flutter plugin can be installed from:
๐จ https://plugins.jetbrains.com/plugin/9212-flutter
โข Dart plugin version 242.22855.32
[โ] VS Code (version 1.95.0)
โข VS Code at /Applications/Visual Studio Code.app/Contents
โข Flutter extension version 3.98.0
[โ] Connected device (5 available)
โข vasilich (2) (mobile) โข 00008110-0016359A0A3B801E โข ios โข iOS 18.0.1 22A3370
โข iPhone 16 Pro (mobile) โข D6BB8746-586B-4EB2-99FF-47AA8C6D46E5 โข ios โข com.apple.CoreSimulator.SimRuntime.iOS-18-0 (simulator)
โข macOS (desktop) โข macos โข darwin-arm64 โข macOS 15.0 24A335 darwin-arm64
โข Mac Designed for iPad (desktop) โข mac-designed-for-ipad โข darwin โข macOS 15.0 24A335 darwin-arm64
โข Chrome (web) โข chrome โข web-javascript โข Google Chrome 130.0.6723.70
[โ] Network resources
โข All expected network resources are available.
```
</details>
| framework,f: material design,a: error message,has reproducible steps,P2,workaround available,team-design,triaged-design,found in release: 3.24,found in release: 3.27 | low | Critical |
2,626,425,139 | deno | Only authorize import modules listed in the import map | ## Proposition
Having a way to only authorize dependencies listed in the `imports` block of the `deno.json` file.
## Examples
This example should **NOT** work when I run `deno run -A main.ts` because the dependency is not listed in the `imports` block.
`deno.json`
````json
{
"imports": {}
}
````
`main.ts`
````typescript
import { fib } from "jsr:@phocks/fib"; // Error not listed in deno.json
console.log(fib(3));
````
----
However, that example must work when I run `deno run -A main.ts` because the dependency is listed in the `imports` block.
`deno.json`
````json
{
"imports": {
"fibonacci": "jsr:@phocks/fib"
}
}
````
`main.ts`
````typescript
import { fib } from "fibonacci"; // import from deno.json
console.log(fib(3));
````
| suggestion,install | low | Critical |
2,626,434,435 | vscode | No close icon when Activity Bar Top | <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- ๐ช If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- ๐ฃ Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:
- OS Version:
Steps to Reproduce:
1. Click the Copilot icon on the top bar on the right of the search bar to show the Secondary side bar.
2. Position it on the right side of the editor region
3. You should see there is no icon to close the Copilot Chat view.
| under-discussion,layout,workbench-auxsidebar | low | Critical |
2,626,485,183 | langchain | Windows 11 - langchain_huggingface/sentence-transformers unable to run | ### 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
```
from langchain_huggingface.embeddings import HuggingFaceEmbeddings
model_name = "mixedbread-ai/mxbai-embed-large-v1"
hf_embeddings = HuggingFaceEmbeddings(
model_name=model_name,
)
texts = ["Hello, world!", "How are you?"]
print(hf_embeddings.embed_documents(texts))
```
### Error Message and Stack Trace (if applicable)
```
Traceback (most recent call last):
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\langchain_huggingface\embeddings\huggingface.py", line 52, in __init__
import sentence_transformers # type: ignore[import]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\sentence_transformers\__init__.py", line 10, in <module>
from sentence_transformers.cross_encoder.CrossEncoder import CrossEncoder
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\sentence_transformers\cross_encoder\__init__.py", line 3, in <module>
from .CrossEncoder import CrossEncoder
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\sentence_transformers\cross_encoder\CrossEncoder.py", line 10, in <module>
from torch import Tensor, nn
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\nn\__init__.py", line 1, in <module>
from .modules import * # noqa: F403
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\nn\modules\__init__.py", line 1, in <module>
from .module import Module
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\nn\modules\module.py", line 8, in <module>
from torch._prims_common import DeviceLikeType
ModuleNotFoundError: No module named 'torch._prims_common'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\x\Desktop\Python\huggingface_embeddings\app.py", line 4, in <module>
hf_embeddings = HuggingFaceEmbeddings(
^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\x\AppData\Local\Programs\Python\Python311\Lib\site-packages\langchain_huggingface\embeddings\huggingface.py", line 54, in __init__
raise ImportError(
ImportError: Could not import sentence_transformers python package. Please install it with `pip install sentence-transformers`.
```
### Description
pip install langchain
pip install huggingface_hub
pip install sentence_transformers
pip install langchain_huggingface
All latest versions installed on windows 11 when i run above code to get embeddings i got error stack as posted
BUT on linux works
### System Info
Windows 11 - not working
Linux - working
all packages latests version | ๐ค:bug | low | Critical |
2,626,492,965 | flutter | Flutter 3.24 doesnt support Apple emojis | ### Use case
After upgrading Flutter web app from 3.19.6 to 3.24.0, the emojis I used, stopped looking like Apple ones but Noto.
Which doens't fit into the app UI requirements.
To fix this you can add Apple emojis font to pubspec, but the file size is 180 mb, so it's barely a solution.
Moreover inserting emojis from mac Character Viewer, instanlty making them Noto emojis.
https://github.com/user-attachments/assets/e6b8aafc-b074-417e-997c-19badfe77925
### Proposal
I think Flutter needs either use system emoji font or have a possibility to select which emojis must be used. | c: new feature,engine,platform-web,c: proposal,e: web_canvaskit,P2,team-web,triaged-web | low | Major |
2,626,605,042 | ollama | Easily see latest version | Would it be possible to have the version of the latest version of Ollama on the ollama.com website? So we don't have to click through to Github to find the info. | feature request,ollama.com | low | Minor |
2,626,627,019 | excalidraw | Feature Request: Increase Zoom-Out Ratio for Better Board Overview | **Description:**
I would like to request an enhancement to the zoom functionality of the tool to allow users to zoom out further. This adjustment would make it easier to view the entire board in one frame, especially when working with larger boards.
### Problem
Currently, the maximum zoom-out limit restricts users from seeing the full extent of large boards. This limitation makes navigation and board management cumbersome, as users have to scroll frequently to see different sections of the board.
### Proposed Solution
Increase the zoom-out ratio to enable users to view the entire board on a single screen. This could be done by:
- Allowing an additional level of zoom-out that accommodates larger boards.
- Adding finer control over the zoom scale to adjust according to board size.
### Benefits
- Enhanced user experience by enabling a complete view of large boards.
- Improved efficiency in navigating and managing content on extensive boards.
### Use Cases
- Project managers and team members need to quickly scan large boards without excessive scrolling.
- Users want to see the overall structure of complex boards for planning and collaboration.
### Additional Notes
If any feedback or specific examples would be helpful for development, Iโd be happy to provide more details. | performance โก๏ธ,UX/UI | low | Minor |
2,626,636,293 | next.js | Static indicator shouldn't be shown when searchParams is being used | ### Link to the code that reproduces this issue
https://codesandbox.io/p/devbox/awesome-shockley-46z7c5
### To Reproduce
1. Start the dev server
2. Create a new page and use `searchParams`
```tsx
export default async function Page({
searchParams,
}: {
searchParams: Promise<{a: string}>;
}) {
const sp = await searchParams;
return (
<div>
<p>sp: {sp.a}</p>
</div>
);
}
```
3. Visit the page on the browser and the static indicator should not be shown here since `searchParams` is considered a Dynamic API
Build time:
In the build time process, though, the page is correctly rendered as a dynamic page (the `/sp` route):
<img width="487" alt="image" src="https://github.com/user-attachments/assets/7d6a956f-e018-43e8-a5f0-a4626a617fe0">
### Current vs. Expected behavior
The static indicator should not be shown here since `searchParams` is considered a Dynamic API.
### Provide environment information
```bash
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023
Available memory (MB): 4102
Available CPU cores: 2
Binaries:
Node: 20.9.0
npm: 9.8.1
Yarn: 1.22.19
pnpm: 8.10.2
Relevant Packages:
next: 15.0.3-canary.2 // Latest available version is detected (15.0.3-canary.2).
eslint-config-next: N/A
react: 19.0.0-rc-603e6108-20241029
react-dom: 19.0.0-rc-603e6108-20241029
typescript: 5.3.3
Next.js Config:
output: N/A
```
### Which area(s) are affected? (Select all that apply)
Developer Experience
### Which stage(s) are affected? (Select all that apply)
next dev (local)
### Additional context
_No response_ | bug,linear: next | low | Minor |
2,626,648,751 | vscode | Hover: Consider changing defaults | With the move to a new API in https://github.com/microsoft/vscode/pull/232614, we want to focus on making it easy to use. Previously there was a `placement` type of mouse or element which changed some defaults. The biggest ones are `compact` and `showPointer` which are used essentially by all hovers and all element hovers respectively. Should we change the defaults in `IHoverService`? | debt,workbench-hover | low | Minor |
2,626,755,920 | vscode | No history for new chat window. garbage. Co-Pilot just got a worse. | <!-- โ ๏ธโ ๏ธ Do Not Delete This! bug_report_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- ๐ฎ Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- ๐ Search existing issues to avoid creating duplicates. -->
<!-- ๐งช Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- ๐ก Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- ๐ง Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
<!-- ๐ช If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- ๐ฃ Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:
- OS Version:
Steps to Reproduce:
1.
2.
| info-needed | low | Critical |
2,626,786,078 | flutter | Firefox/Safari: Wrapping TextField widget with PointerInterceptor makes it unresponsive | ### Steps to reproduce
1. Add PointerInterceptor to your packages ```flutter pub add pointer_interceptor```.
2. Wrap TextField widget with PointerInterceptor.
3. Run flutter on Firefox
4. Try to type something in the TextField widget.
### Expected results
You should be able to type.
### Actual results
TextField widget will be completely unresponsive
### Code sample
<details open><summary>Code sample</summary>
```dart
import 'package:flutter/material.dart';
import 'package:pointer_interceptor/pointer_interceptor.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(title: 'Flutter Demo Home Page'),
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key, required this.title});
final String title;
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
title: Text(widget.title),
),
body: Center(
child: PointerInterceptor(
child: const TextField(),
)),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
[Upload media here]
</details>
### Logs
<details open><summary>Logs</summary>
```console
[Paste your logs here]
```
</details>
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
Doctor summary (to see all details, run flutter doctor -v):
[โ] Flutter (Channel stable, 3.24.3, on macOS 15.0.1 24A348 darwin-arm64, locale en-US)
[โ] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[โ] Xcode - develop for iOS and macOS (Xcode 16.0)
[โ] Chrome - develop for the web
[โ] Android Studio (version 2023.3)
[โ] VS Code (version 1.95.0)
[โ] Connected device (5 available)
[โ] Network resources
โข No issues found!
```
</details>
| a: text input,platform-web,package,has reproducible steps,browser: safari-macos,browser: firefox,P2,p: pointer_interceptor,team-web,triaged-web,found in release: 3.24,found in release: 3.27 | low | Minor |
2,626,794,064 | angular | TestBed.flushEffects does not work if the Injector passed to the effect came from a ComponentFixture | ### Which @angular/* package(s) are the source of the bug?
core
### Is this a regression?
Yes
### Description
In Angular 18, I had tests that passed the *Injector* from a *ComponentFixture* down to an *effect* inside a custom signal. When upgrading to Angular 19 these tests broke. Here's a simple example:
```
describe('customSignal', () => {
let fixture: ComponentFixture<unknown>;
let injector: Injector;
beforeEach(() => {
fixture = createFixture();
injector = fixture.componentRef.injector;
});
fit('should do something', () => {
const sut = customSignal(5, { injector });
sut.set(6);
TestBed.flushEffects(); // Used to work in Angular 19.
expect(sut()).toBe(24); // Expectation fails because an update that was supposed to be made by an internal effect didn't occur.
});
});
```
There are several work arounds:
* Create the signal inside runInInjectionContext: `const sut = TestBed.runInInjectionContext(() => customSignal(5));`
* Pass an injected *Injector* to the signal: `const sut = customSignal(5, { inject: TestBed.inject(Injector) });`
* Use `fixture.detectChanges()` instead of `TestBed.flushEffects()`.
### Please provide a link to a minimal reproduction of the bug
https://github.com/DDtMM/angular-signal-generators/blob/f33e82ea46ae3e2160133c67c62503fc2d405c39/projects/signal-generators/src/lib/signals/async-signal.spec.ts#L69
### Please provide the exception or error you saw
The changes that should occur after using `TestBed.flushEffects()` do not occur and my test expectations fail.
### Please provide the environment you discovered this bug in (run `ng version`)
Angular CLI: 19.0.0-rc.0
Node: 20.14.0
Package Manager: npm 10.3.0
OS: win32 x64
Angular: 19.0.0-rc.0
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, ssr
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1900.0-rc.0
@angular-devkit/build-angular 19.0.0-rc.0
@angular-devkit/core 19.0.0-rc.0
@angular-devkit/schematics 19.0.0-rc.0
@angular/cdk 19.0.0-next.10
@schematics/angular 19.0.0-rc.0
ng-packagr 19.0.0-next.7
rxjs 7.8.1
typescript 5.6.3
zone.js 0.15.0
### Anything else?
_No response_ | area: testing,cross-cutting: signals | low | Critical |
2,626,861,892 | go | proposal: iter/sorted: functions on sorted iterators | I propose adding a package of functions that operate on iterators whose values are sorted.
Sorted sequences can arise in a number of ways:
- From a slice that has been sorted.
- From the keys of an ordered map, such as [github.com/google/btree](https://github.com/google/btree) or the one in #60630.
- From an external source, like a database with sorted keys.
- Naturally, as in the line numbers of a file or the times of a monotonic clock.
Common operations on pairs of sorted sequences include merging them into a single sorted sequence, as well as the set operations union, intersection and set difference. I propose a package with these operations, with the API given below.
As is common in packages like `slices`, there are two functions for each operation, one using the natural ordering of a type and one that accepts a comparison function. We could also consider adding functions that operate on the keys of `iter.Seq2`s, bringing along the corresponding values. I don't know if those sequences would arise enough to make that worthwhile. We could reconsider adding the `Seq2` functions if and when we add ordered maps.
## API
```
package sorted
Package sorted provides operations over iterators whose values are sorted.
FUNCTIONS
func Intersect[T cmp.Ordered](s1, s2 iter.Seq[T]) iter.Seq[T]
Intersect returns an iterator over all elements of s1 that are also in s2,
in the same order. Each element of s1 appears only once in the result.
Both s1 and s2 must be sorted.
func IntersectFunc[T any](s1, s2 iter.Seq[T], cmp func(T, T) int) iter.Seq[T]
IntersectFunc returns an iterator over all elements of s1 that are also in
s2, in the same order. Each element of s1 appears only once in the result.
Both s1 and s2 must be sorted according to cmp.
func Merge[T cmp.Ordered](s1, s2 iter.Seq[T]) iter.Seq[T]
Merge returns an iterator over all elements of s1 and s2, in the same order.
Both s1 and s2 must be sorted.
func MergeFunc[T any](s1, s2 iter.Seq[T], cmp func(T, T) int) iter.Seq[T]
MergeFunc returns an iterator over all elements of s1 and s2, in the same
order. Both s1 and s2 must be sorted according to cmp.
func Subtract[T cmp.Ordered](s1, s2 iter.Seq[T]) iter.Seq[T]
Subtract returns an iterator over all elements of s1 that are not in s2,
in the same order. Each element of s1 appears only once in the result.
Both s1 and s2 must be sorted.
func SubtractFunc[T any](s1, s2 iter.Seq[T], cmp func(T, T) int) iter.Seq[T]
SubtractFunc returns an iterator over all elements of s1 that are not in s2,
in the same order. Each element of s1 appears only once in the result.
Both s1 and s2 must be sorted according to cmp.
func Union[T cmp.Ordered](s1, s2 iter.Seq[T]) iter.Seq[T]
Union returns an iterator over all elements of s1 and s2, in the same order.
Each element appears only once in the result. Both s1 and s2 must be sorted.
func UnionFunc[T any](s1, s2 iter.Seq[T], cmp func(T, T) int) iter.Seq[T]
UnionFunc returns an iterator over all elements of s1 and s2, in the same
order. Each element appears only once in the result. Both s1 and s2 must be
sorted according to cmp.
```
There is a working implementation at [github.com/jba/sorted](https://github.com/jba/sorted).
| Proposal | medium | Major |
2,626,868,298 | godot | Program Crashes After Using @tool | ### Tested versions
v4.3.stable.official [77dcf97d8]
### System information
Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU (NVIDIA; 32.0.15.6094) - AMD Ryzen 9 7945HX with Radeon Graphics (32 Threads)
### Issue description
```gdscript
@tool
class_name CharacterModel
extends Node2D
## ่ง่ฒๆจกๅ็ฑป
## ๅฎ็ฐๆจกๅ็ธๅ
ณๅ่ฝ๏ผๅ
ๆฌๅจ็ปๆญๆพ็ญ
const DEFAULT_TEXTURE = preload("res://assets/textures/characters/Main.png")
@onready var animation_loop: AnimationPlayer = $AnimationLoop
@onready var animation_region: AnimationPlayer = $AnimationRegion
@onready var hand_spot: Marker2D = $HandSpot
## ๆจกๅ็ถๆๆไธพ
enum State{
## ้ป่ฎค็ถๆ
IDLE,
## ็งปๅจ็ถๆ
RUNING,
}
## ๆจกๅๆนๅๆไธพ
enum Direction{
UP,
RIGHT,
DOWN,
LEFT,
}
## ๅฝๅๆจกๅ็ๆๅ
@export var direction :Direction = Direction.DOWN:
set(v):
direction=v
update_animation()
## ๅฝๅๆจกๅ็็ถๆ
@export var state :State = State.IDLE:
set(v):
state=v
update_animation()
## ๅฝๅๆจกๅๆไฝฟ็จ็ๅพๅ
@export var texture :Texture = DEFAULT_TEXTURE
## ๅฝๅๆจกๅๆฏๅฆๆฌๆ
@export var is_holding :bool = false:
set(v):
is_holding=v
update_animation()
# ่ทๅๆๅญ็ๆนๅ
var dir_text:
get:
var map=['up','right','down','left']
return map[direction]
func _ready() -> void:
update_animation()
# ๆดๆฐๆจกๅๅจ็ป
func update_animation():
if not is_node_ready():
await ready
animation_loop.play('default')
if state == State.IDLE:
animation_region.play('idle_'+dir_text)
if is_holding:
animation_region.play('holding_'+dir_text)
animation_loop.stop()
if state == State.RUNING:
animation_region.play('move_'+dir_text)
if is_holding:
animation_region.play('holding_'+dir_text)
## ่ทๅๅฝๅๆจกๅๆ็ไฝ็ฝฎ๏ผๆณจๆ๏ผไป
ๅฝis_holdingไธบtrueๆถ๏ผๆกๆ็ฉๅๆๆพๅพๆญฃๅธธ
func get_hand_spot()->Vector2:
return hand_spot.global_position
```
### Steps to reproduce
1ใๅจๅ
ถไปๅบๆฏไธญๅฎไพๅไบๆญคๅบๆฏใ
2ใๅฝๆๅ
ณ้ญๅฝๅๅบๆฏ๏ผๆ่
็นๅป้้กนๅกๅๆขๅฐๅ
ถไปๅบๆฏๆถ๏ผๅนถๆชๅ็ๅบๆฏๅๆข๏ผ่็จๅบ็ดๆฅๅฐฑๅดฉๆบไบ๏ผไนๆฒกๆๆฅ้ๆ็คบใ
Hereโs the translation:
1. **This scene was instantiated in other scenarios.**
2. **When I close the current scene or click the tab to switch to another scene, the scene doesnโt switch; instead, the program crashes directly without any error message.**
### Minimal reproduction project (MRP)
N/A | topic:gdscript,topic:editor,needs work,needs testing | low | Critical |
2,626,881,492 | tensorflow | Thread ID in TensorBoard Profiler Trace Viewer Could Be Negative | ### Issue type
Bug
### Have you reproduced the bug with TensorFlow Nightly?
Yes
### Source
source
### TensorFlow version
tf2.17
### Custom code
No
### OS platform and distribution
Linux Mint 21.2
### Mobile device
_No response_
### Python version
3.11
### Bazel version
6.5.0
### GCC/compiler version
clang 14.0.0
### CUDA/cuDNN version
_No response_
### GPU model and memory
_No response_
### Current behavior?
While using TensorFlow's profiler, I found that some thread IDs displayed in the Trace Viewer are negative. As shown in the image below, thread names such as `tf_Compute/-1030865605`, `tf_data_private_threadpool/-102013...`, etc., have negative thread IDs.
My log file is also attached.
[20241030-161104.zip](https://github.com/user-attachments/files/17587809/20241030-161104.zip)
### Standalone code to reproduce the issue
```shell
(Just the profiler demo code) https://www.tensorflow.org/tensorboard/tensorboard_profiling_keras
```
### Relevant log output
_No response_ | type:bug,awaiting PR merge,2.17 | medium | Critical |
2,626,897,066 | rust | Generic causes other trait implementations of concrete type to be ignored. | I tried this code:
```rust
use rust_decimal::{
// The important thing about this type is that you can do Decimal::from(1).
Decimal,
};
fn this_is_not_generic() {
Decimal::from(1); // This is accepted.
}
fn this_is_indeed_generic<Inp>(inp: Inp)
where
// All I am saying here is that you can convert from Inp to Decimal.
// I am NOT saying that ONLY Inp can be converted to Decimal.
Decimal: From<Inp>
{
Decimal::from(1); // This is rejected. WTF?
}
```
I expected to see this happen: My code is accepted.
Instead, this happened: My code is rejected. More precisely,
```
error[E0308]: mismatched types
--> src/lib.rs:16:19
|
10 | fn this_is_indeed_generic<Inp>(inp: Inp)
| --- expected this type parameter
...
16 | Decimal::from(1); // This is rejected. WTF?
| ------------- ^ expected type parameter `Inp`, found integer
| |
| arguments to this function are incorrect
|
= note: expected type parameter `Inp`
found type `{integer}`
note: associated function defined here
--> /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/convert/mod.rs:585:8
For more information about this error, try `rustc --explain E0308`.
error: could not compile `repro` (lib) due to 1 previous error
```
### Meta
```
$ rustc --version --verbose
rustc 1.80.0 (051478957 2024-07-21)
binary: rustc
commit-hash: 051478957371ee0084a7c0913941d2a8c4757bb9
commit-date: 2024-07-21
host: aarch64-apple-darwin
release: 1.80.0
LLVM version: 18.1.7
```
Behavior on `+nightly`:
```
error[E0308]: mismatched types
--> src/lib.rs:16:19
|
10 | fn this_is_indeed_generic<Inp>(inp: Inp)
| --- expected this type parameter
...
16 | Decimal::from(1); // This is rejected. WTF?
| ------------- ^ expected type parameter `Inp`, found integer
| |
| arguments to this function are incorrect
|
= note: expected type parameter `Inp`
found type `{integer}`
note: associated function defined here
--> /rustc/52fd9983996d9fcfb719749838336be66dee68f9/library/core/src/convert/mod.rs:585:8
For more information about this error, try `rustc --explain E0308`.
error: could not compile `repro` (lib) due to 1 previous error
``` | A-trait-system,T-compiler,C-bug,T-types,WG-trait-system-refactor,E-needs-investigation | low | Critical |
2,626,905,867 | material-ui | [Tooltip] Tooltip persists when its child becomes disabled | ### Steps to reproduce
Link to live example: (https://codesandbox.io/p/sandbox/sleepy-keller-ydzw79
Steps:
1. Use Tab navigation to focus the Icon Buttons (that have the Tooltip).
2. Hit the Enter key, to disable the Icon Button.
3. Use Tab (or Shift + Tab) to navigate again, and you will notice how the Tooltip persists under the disbaled Icon Button, even though it should not.
### Current behavior
The Tooltip remains open when the Icon Button becomes disabled.
### Expected behavior
The Tooltip closes when the Icon Button becomes disabled.
### Context
In a Top App Bar.
### Your environment
```
System:
OS: Windows 10 10.0.19045
Binaries:
Node: 20.18.0 - C:\Program Files\nodejs\node.EXE
npm: 10.8.2 - C:\Program Files\nodejs\npm.CMD
pnpm: Not Found
Browsers:
Chrome: 130.0.6723.70
Edge: Chromium (127.0.2651.74)
npmPackages:
@emotion/react: ^11.13.0 => 11.13.0
@emotion/styled: ^11.13.0 => 11.13.0
@mui/core-downloads-tracker: 6.1.6
@mui/icons-material: ^6.1.6 => 6.1.6
@mui/material: ^6.1.6 => 6.1.6
@mui/private-theming: 6.1.6
@mui/styled-engine: 6.1.6
@mui/system: 6.1.6
@mui/types: 7.2.19
@mui/utils: 6.1.6
@types/react: ^18.3.3 => 18.3.3
react: ^18.3.1 => 18.3.1
react-dom: ^18.3.1 => 18.3.1
typescript: ^5.5.3 => 5.5.3
```
</details>
**Search keywords**: icon button tooltip tab selection focused focus disabled | bug ๐,component: tooltip,package: material-ui,ready to take | low | Major |
2,626,918,223 | ant-design | Card type tab background is incompatible inside of a modal in dark mode | ### Reproduction link
[](https://stackblitz.com/edit/react-jvmudi?file=demo.tsx)
### Steps to reproduce
Render card type tabs in a modal with dark theme
### What is expected?
Tab background color blends well with modal background regardless of theme
### What is actually happening?
The tab background color is different than modal background. I think this is caused by the tabs using `colorBgContainer` token as the the background and it's set to `#141414` in dark mode, while the modal background uses `contentBg` and it's set to `#1f1f1f`
| Environment | Info |
| --- | --- |
| antd | 5.21.6 |
| React | ^18 |
| System | Windows 11 |
| Browser | Chrome 129 |
<!-- generated by ant-design-issue-helper. DO NOT REMOVE --> | Inactive,improvement | low | Minor |
2,626,934,033 | pytorch | [ROCm] [Upstream Triton] Use HIPAttrsDescriptor on ROCm to support emitting buffer operations | These PRs resolved https://github.com/pytorch/pytorch/issues/139179
- https://github.com/pytorch/pytorch/pull/139193 and https://github.com/triton-lang/triton/pull/4888
We need a follow up PR to add support for HIPAttrsDescriptor parameterisation for AttrsDescriptorWrapper to support emitting buffer operations on triton with AMD backend.
### Versions
Triton TOT.
cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @hongxiayang @naromero77amd | module: rocm,triaged | low | Minor |
2,627,007,930 | three.js | Need a Raw Shader solution for WebGPURenderer | ### Description
I need access to certain aspects of 3js like TransformFeedback/Compute with WebGL, To do so I need to run things with WebGPURenderer with forceWebGL set to true. The hitch is that RawShaderMaterial or something like it is no longer supported. This is a requirement because I have almost a decade worth of raw shaders plus, I need a simple way to keep shader code free & portable. TSL isn't a solution when there is a need to work in various webGL/openGL environments, be it shadertoys, pixiJS, babylonjs, godot, etc. I've even grabbed raw glsl code out of the blender project to use in 3js projects.
So far, the furthest I've managed to get TSL to work with raw shaders doesn't really work. Even using uniforms seems broken as even though I gave it a name, it changed its name plus threw it in a UBO of an unknown name instead of a simple uniform. I understand the idea to match how webgpu works, but there should be more control over uniforms in general that is predictable & known without having to output the GLSL code to see what really was created.
I dont know what the final solution should be, just bring back raw shaders for both GLSL & WGSL or provide some nodes that allows just a big text dump containing code, uniforms, attributes, varying. Also be nice to still have easy access to some of the main matrices like model, view & perspective plus cameraPosition was always nice to have around. I do want to use UBOs more but I want it to be optional if possible to better match WebGL / OpenGL shader standards.
As a side note, I even tried to extend nodeMaterial to see if I can hijack the builder to swop out the vertex/fragment shader before they're compiled into a program but that wasn't successful either.
@sunag
```
const uColor = THREE.uniform( new THREE.Color( 0x00ff00 ) );
uColor.name = 'uColor';
const fCode = THREE.code( `
vec4 test2(){
return vec4( 0.0, 1.0, 0.0, 1.0 ); // vec4( uColor, 1.0 );
}
`);
const fMain = THREE.glslFn(`
vec4 vertMain(){
return vec4( 1.0, 0.0, 0.0, 1.0 ); // test2();
}
`, [ fCode, uColor ] );
const mat = new THREE.NodeMaterial();
mat.fragmentNode = fMain();
const geo = new THREE.PlaneGeometry( 1, 1 );
const mesh = new THREE.Mesh( geo, mat );
App.debugMaterial( mesh ).then( sh=>console.log( sh.fragmentShader ) );
```
Outputs
```
layout( std140 ) uniform fragment_object {
vec3 f_uColor;
};
vec4 test2(){
return vec4( 0.0, 1.0, 0.0, 1.0 ); // vec4( uColor, 1.0 );
}
vec4 vertMain ( ){
return vec4( 1.0, 0.0, 0.0, 1.0 ); // test2();
}
layout( location = 0 ) out vec4 fragColor;
void main() {
fragColor = vertMain( );
}
```
### Solution
xxx
### Alternatives
xxx
### Additional context
_No response_ | Suggestion | medium | Critical |
2,627,008,382 | ollama | Support for BGE-Multilingual-Gemma2 | I would be very grateful for the support of the BGE-Multilingual-Gemma2, an LLM-based multilingual embedding model.
https://huggingface.co/BAAI/bge-multilingual-gemma2
| model request | low | Major |
2,627,024,510 | kubernetes | add regression tests for known existing kube-proxy configs | Re the v1alpha2 configuration work, we should add a unit test with a bunch of known kube-proxy invocations taken from our various e2e tests (both config files and command-line options) and what the expected resulting `KubeProxyConfiguration` is, to help us avoid problems with further refactorings.
/assign @aroradaman
/cc @aojea
/sig network
/triage accepted | sig/network,triage/accepted | low | Minor |
2,627,033,645 | next.js | Not working eslintrc.json in Nextjs 15 | ### Link to the code that reproduces this issue
https://github.com/YouJun-IWON/My_Nextjs15
### To Reproduce
1. set .eslintrc.json 2. check page.tsx 3. I don't see error messages for unused variables.
### Current vs. Expected behavior
I expected to see error messages for unused variables. But I can't see any error.
If I install eslint@8.57.0 I can show error in page.tsx code.
### Provide environment information
```bash
{
"name": "prettier-eslint-husky-setting",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev --turbopack",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"next": "15.0.2",
"react": "19.0.0-rc-02c0e824-20241028",
"react-dom": "19.0.0-rc-02c0e824-20241028"
},
"devDependencies": {
"@ianvs/prettier-plugin-sort-imports": "^4.3.1",
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"@typescript-eslint/parser": "^8.12.2",
"eslint": "^9.13.0",
"eslint-config-next": "^15.0.2",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-tailwindcss": "^3.17.5",
"eslint-plugin-unused-imports": "^4.1.4",
"postcss": "^8",
"prettier": "^3.3.3",
"prettier-plugin-tailwindcss": "^0.6.8",
"tailwindcss": "^3.4.1",
"typescript": "^5"
}
}
```
### Which area(s) are affected? (Select all that apply)
create-next-app, Linting
### Which stage(s) are affected? (Select all that apply)
next dev (local)
### Additional context
_No response_ | create-next-app,bug,Linting | low | Critical |
2,627,045,267 | node | Long Major GC events while using external buffers (Video Image Data) | ### Version
v23.1.0
### Platform
```text
23.1.0 Darwin Kernel Version 23.1.0
```
### Subsystem
_No response_
### What steps will reproduce the bug?
I am sharing data from a native node C++ plugin using node-addon-api: return Napi::ArrayBuffer::New(env, frame_->data[i], width*height);
I checked that the memory being accessed from JS was the same as the one from C++ (And can confirm it works as expected).
However, whenever I access this data I get some Major GC events taking more than 100+ms in total.
The memory is freed by the C++ process and there is not any crash or weird behavior apart from this.
The ArrayBuffer is exposed using node-addon-api: InstanceAccessor("data", &Frame::data, nullptr), .
Writing frame.data in javascript causes this events.
node-addon-api uses napi_create_external_buffer when creating a Napi::ArrayBuffer
### How often does it reproduce? Is there a required condition?
This occurs multiple times every 1-2s. Depends on the size of the data and how often is sent from C++ to JS.
### What is the expected behavior? Why is that the expected behavior?
As the memory collection is not handled by the Major GC it should not expend time trying to free this objects.
### What do you see instead?
Major GC trying to collect external buffers and spending more time depending how big this external buffers are.
### Additional information
_No response_ | node-api | low | Critical |
2,627,047,669 | excalidraw | Option to not automatically turn on pen mode when selecting the pen pointerType | I'm glad that pen mode is an option, but I typically want it off, even when drawing with the pen, as it removes the ability to select by clicking and dragging with the mouse. Pen mode seems to automatically be turned on when I select the pen for the first time in a new drawing, despite having "Pen mode" set to never in the appearance and behaviour section of the settings. It would be nice to have an option to stop excalidraw ever turning on pen mode by itself, I only want pen mode to be activated when I turn it on myself manually. | UX/UI,tablet | low | Minor |
2,627,063,071 | storybook | [Bug]: Tags filter UI is filtering "recently opened" results | ### Describe the bug
When search is focused but there is no query, we show "recently opened" stories in the sidebar.
The recently open story IDs are stored in localStorage, meaning that they can correspond to any Storybook running on the port. So to avoid problems, we filter those story IDs down to stories that actually exist in the currently open Storybook.
For some reason, the list of stories that we filter by, is in turn filtered down by the selected tags. So if you have `play-fn` selected but have not recently viewed any `play-fn` stories, the list will be empty and the sidebar will be blank. Unfortunately, this state is pretty easy to hit.
This seems like a bug because we should be checking against ALL stories in the current Storybook and not the list filtered by `play-fn`. If we make this change, it means that it's possible to navigate to a recently viewed story that is NOT showed in the sidebar.
As a related fix, we could also make it so that the currently selected story is ALWAYS shown in the sidebar even if it doesn't match the current set of filters. It could disappear from the sidebar as soon as the user navigates away from the story.
### Reproduction link
N/A
### Reproduction steps
_No response_
### System
any
### Additional context
_No response_ | bug,ui: search,tags,sev:S3 | low | Critical |
2,627,067,102 | react-native | experimental_backgroundImage works incorrect | ### Description
Hi!
I'm testing an experimental way to set a linear-gradient and found some issues. As I've got it, it has the similar syntax as css has and so I can guess that it should work the same.
- [ ] the gradient angle is not the same as in the web
- [ ] the gradient angle depends on element sizes
- [ ] repeating-linear-gradient doesn't work at all
Expected behaviours is:
1) The angle shouldn't have been changed on blocks with different sizes.
2) The result should be the same as on the web.
### Steps to reproduce
1. install the app
2. create two `Views` with different sizes and set up them the same linear-gradient
3. create the same blocks in the web and compare the result
`experimental_backgroundImage: "linear-gradient(45deg, black 9%, red 20%, blue 30%, green 50%, black 90%, transparent)"`
### React Native Version
0.76.1
### Affected Platforms
Runtime - Android, Runtime - iOS
### Output of `npx react-native info`
```text
System:
OS: macOS 15.1
CPU: (8) arm64 Apple M1
Memory: 144.70 MB / 8.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 20.11.1
path: ~/.nvm/versions/node/v20.11.1/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 10.2.4
path: ~/.nvm/versions/node/v20.11.1/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.16.1
path: /Users/pavelauseitsau/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.1
- iOS 18.1
- macOS 15.1
- tvOS 18.1
- visionOS 2.1
- watchOS 11.1
Android SDK: Not Found
IDEs:
Android Studio: 2024.1 AI-241.19072.14.2412.12360217
Xcode:
version: 16.1/16B40
path: /usr/bin/xcodebuild
Languages:
Java:
version: 21.0.5
path: /usr/bin/javac
Ruby:
version: 3.1.2
path: /Users/pavelauseitsau/.rbenv/shims/ruby
npmPackages:
"@react-native-community/cli":
installed: 15.0.0
wanted: 15.0.0
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.76.1
wanted: 0.76.1
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
```
### Stacktrace or Logs
```text
App hasn't been crashing.
```
### Reproducer
-
### Screenshots and Videos
| Resolution: PR Submitted,Component: Image,0.76 | low | Critical |
2,627,100,351 | tauri | [bug] powershell completion for pnpm will overwrite each other | ### Describe the bug
When using pnpm and tauri completions separately, they will overwrite each other (depending on which completion is imported last)
**import tauri after pnpm**
**import pnpm after tauri**
> ๐ without tauri completion
### Reproduction
_No response_
### Expected behavior
_No response_
### Full `tauri info` output
```text
[โ] Environment
- OS: Windows 10.0.26120 x86_64 (X64)
โ WebView2: 130.0.2849.56
โ MSVC: Visual Studio Build Tools 2022
โ 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-pc-windows-msvc (default)
- node: 22.9.0
- pnpm: 9.12.3
- yarn: 1.22.22
- npm: 10.8.3
[-] Packages
- tauri ๐ฆ: 2.0.6
- tauri-build ๐ฆ: 2.0.2
- wry ๐ฆ: 0.46.3
- tao ๐ฆ: 0.30.5
- @tauri-apps/api ๎: 2.0.3
- @tauri-apps/cli ๎: 2.0.5
[-] Plugins
- tauri-plugin-shell ๐ฆ: 2.0.2
- @tauri-apps/plugin-shell ๎: 2.0.1
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
- framework: React
- bundler: Vite
```
### Stack trace
_No response_
### Additional context
_No response_ | type: bug,status: needs triage | low | Critical |
2,627,115,771 | tauri | [feat] support for rendering videos encoded with h265 in macos | ### Describe the problem
https://github.com/mediar-ai/screenpipe/pull/580#issuecomment-2447779203
videos encoded with h265 does not work in tauri `<video>` component (nextjs)
code:
https://github.com/mediar-ai/screenpipe/blob/cb929de6d7df582a0ed228dc359cd873451ea97a/screenpipe-app-tauri/components/video.tsx#L111
### Describe the solution you'd like
it works
or tell me workaround to allow me to install the necessary dependencies for it (assuming some video libs)
### Alternatives considered
asking more questions to chatgpt
### Additional context
_No response_ | type: feature request,platform: macOS | low | Minor |
2,627,121,678 | PowerToys | PowerToys Run plugin VS Code Workspaces stays empty | ### Microsoft PowerToys version
0.85.1
### Installation method
PowerToys auto-update
### Running as admin
No
### Area(s) with issue?
PowerToys Run
### Steps to reproduce
type { to show list
### โ๏ธ Expected Behavior
list of opened workspaces in VS Code
### โ Actual Behavior
Stays empty
### Other Software
_No response_ | Issue-Bug,Needs-Triage | low | Minor |
2,627,127,823 | pytorch | [export] Failure to export Mixtral-8x7B-Instruct-v0.1 | ### ๐ Describe the bug
I'm experiencing an issue exporting the `Mixtral-8x7B` model.
I originally discussed the problem in #130274, but this is more about `torch.export`. My ultimate goal is to go to StableHLO.
It raises the error `error torch._dynamo.exc.Unsupported: hasattr ConstDictVariable to.`
I've seen a similar issue [here](https://github.com/pytorch/pytorch/issues/109502), is this something that we'd need to add a custom handler for?
<details><summary>Script to reproduce problem</summary>
<p>
```python
import torch
import torch.export._trace
import transformers
from torch import bfloat16
from transformers import AutoTokenizer
from torch_xla.stablehlo import exported_program_to_stablehlo
import argparse
def main(model_name):
# Load tokenizer and model
model_name = "mistralai/Mixtral-8x7B-v0.1"
name = model_name.split("/")[-1]
cache_dir = "/models/"
model = model_name
# Load tokenizer and model using the specified cache directory
tokenizer = AutoTokenizer.from_pretrained(model_name, cache_dir=cache_dir)
model = transformers.AutoModelForCausalLM.from_pretrained(
model_name,
trust_remote_code=True,
torch_dtype=bfloat16,
device_map="auto",
cache_dir=cache_dir,
)
model.eval()
base_prompt = "How many hours are in a day?"
base_inputs = tokenizer(base_prompt, return_tensors="pt")
input_ids = base_inputs.input_ids
print("Exporting model using torch export...")
exported = torch.export.export(
model,
(input_ids,),
)
```
</p>
</details>
I also tested with `torch.onnx.export(..., dynamo=True, report=True)` on the latest torch-nightly (`2.6.0.dev20241030+cpu`), I get the following: ([Markdown error report in this gist](https://gist.github.com/Wheest/9078d7d6be240d52fcb77e59258e165f)).
@angelayi @tugsbayasgalan You both have commits to `torch.export`, any recommendations?
### Versions
```
Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] nvidia-cublas-cu12==12.1.3.1
[pip3] nvidia-cuda-cupti-cu12==12.1.105
[pip3] nvidia-cuda-nvrtc-cu12==12.1.105
[pip3] nvidia-cuda-runtime-cu12==12.1.105
[pip3] nvidia-cudnn-cu12==9.1.0.70
[pip3] nvidia-cufft-cu12==11.0.2.54
[pip3] nvidia-curand-cu12==10.3.2.106
[pip3] nvidia-cusolver-cu12==11.4.5.107
[pip3] nvidia-cusparse-cu12==12.1.0.106
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] nvidia-nvjitlink-cu12==12.6.77
[pip3] nvidia-nvtx-cu12==12.1.105
[pip3] onnx==1.17.0
[pip3] onnxscript==0.1.0.dev20241030
[pip3] torch==2.4.1
[pip3] torch-xla==2.4.0
[pip3] torchao==0.3.1
[pip3] torchtune==0.2.1
[pip3] triton==3.0.0
[conda] Could not collect
```
cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 | triaged,oncall: pt2,export-triaged,oncall: export | low | Critical |
2,627,141,112 | bitcoin | Remove libevent as a dependency (HTTP / cli / torcontrol) | ## Immediate advantages
### UNIX domain sockets for JSON-RPC
- Old feature request: https://github.com/bitcoin/bitcoin/issues/5029
- UNIX sockets have been added to [ZMQ](https://github.com/bitcoin/bitcoin/pull/27679) and [Tor proxy](https://github.com/bitcoin/bitcoin/pull/27375) already
- UNIX sockets with libevent [doesn't work](https://github.com/bitcoin/bitcoin/issues/5029#issuecomment-2203469108)
### Remove a dependency
- libevent hasn't had a release since 2020
- The [xz utils backdoor](https://en.wikipedia.org/wiki/XZ_Utils_backdoor) raised some concern among contributors in the [2024/04/18 IRC meeting](https://www.erisian.com.au/bitcoin-core-dev/log-2024-04-18.html#l-198)
## Current libevent usage in the project
See [this report](https://gist.github.com/fjahr/c0c339a4b5021ae815d5bcff42e9fc57) by @fjahr. A few of these have already been addressed, like https://github.com/bitcoin/bitcoin/pull/29904
## Strategies
I am starting by replacing the HTTP server, currently used for both REST and JSON-RPC and implemented with libevent. Nothing is quite ready for review yet but I have:
### https://github.com/pinheadmz/bitcoin/tree/http-netbase-cmake
Still lots of TODOs and new tests to write but works and passes all current tests. In this branch I added a new `http.cpp` module with socket-handling code largely copied from `ConnMan`. This branch needs a lot of clean up before presenting as a PR with clear commits.
### https://github.com/pinheadmz/bitcoin/tree/http-rewrite
This branch I am trying to write much more cleanly for PR presentation. It is based on #30988 by @vasild which cleanly separates the generic socket handling logic from the bitcoin protocol logic. It would be especially useful if there was any more future need for additional servers in bitcoin (such as @Sjors recently withdrawn proposal to add StratumV2: https://github.com/Sjors/bitcoin/pull/68)
## Looking for feedback
1. Is this something worth doing at all?
- We could vendor libevent instead of requiring it as a dependency, and fix UNIX sockets there
- There might be another C++ HTTP library we could import instead. I did shop around a bit but everything I found was just a bit too much.
3. If(1) do we want to share generic sock manager code or have it mostly duplicated between p2p and http? | RPC/REST/ZMQ,P2P | low | Major |
2,627,142,919 | ui | [feat]: Integrate with Next.js 15 <Form> component | ### Feature description
Next 15 has a <Form> component now. We want the features of both.
https://nextjs.org/blog/next-15#form-component
### Affected component/components
Form
### Additional Context
Additional details here...
### 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,627,181,293 | material-ui | [material-ui] Finally add number input component | ### The problem in depth
Can we finally consider adding a NumberField component to MUI?
This type of input is essential in most applications and it is about time this component is properly supported and available in @mui/material package.
According to the docs [here](https://mui.com/material-ui/react-text-field/#type-quot-number-quot), your recommendation is to use the [NumberInput](https://mui.com/base-ui/react-number-input/) component from BaseUI but, in my opinion, it doesn't make much sense installing a package to use a single component. Another point is, NumberInput from base has a different look and feel compared to the material package components. If in a form we use fields from material mixed with the NumberInput from base, it will look weird.
I think what many developers are doing at the moment is to just use the `type="number"` prop and build the logic to parse the value to number on the `onChange` handler. But it seems this should be something that @mui/material package should offer out-of-the-box.
Issue [#19154](https://github.com/mui/material-ui/issues/19154) related to this has been open for almost 5 years but no progress has been made to make this available so I am opening this issue in hope we can move this forward.
Maybe this number input field can be added with a behavior inspired by the NumberInput from BaseUI.
Thanks in advance!
### Your environment
Browser used: Chrome 130.0.6723.91
<details>
<summary>`npx @mui/envinfo`</summary>
```
System:
OS: macOS 15.0.1
Binaries:
Node: 20.4.0 - ~/.nvm/versions/node/v20.4.0/bin/node
npm: 9.7.2 - ~/.nvm/versions/node/v20.4.0/bin/npm
pnpm: 9.12.2 - ~/.nvm/versions/node/v20.4.0/bin/pnpm
Browsers:
Chrome: 130.0.6723.91
Edge: 130.0.2849.56
Safari: 18.0.1
npmPackages:
@emotion/react: 11.11.4 => 11.11.4
@emotion/styled: 11.11.5 => 11.11.5
@mui/icons-material: 6.1.3 => 6.1.3
@mui/lab: 6.0.0-beta.11 => 6.0.0-beta.11
@mui/material: 6.1.3 => 6.1.3
@mui/system: 6.1.3 => 6.1.3
@mui/types: 7.2.18 => 7.2.18
@mui/x-data-grid: 7.19.0 => 7.19.0
@mui/x-data-grid-generator: 7.19.0 => 7.19.0
@mui/x-data-grid-premium: 7.19.0 => 7.19.0
@mui/x-data-grid-pro: 7.19.0 => 7.19.0
@mui/x-date-pickers: 7.19.0 => 7.19.0
@mui/x-date-pickers-pro: 7.19.0 => 7.19.0
@mui/x-license: 7.18.0 => 7.18.0
@mui/x-tree-view: 6.17.0 => 6.17.0
@types/react: 18.3.2 => 18.3.2
react: 18.3.1 => 18.3.1
react-dom: 18.3.1 => 18.3.1
styled-components: 5.3.5 => 5.3.5
typescript: 5.6.3 => 5.6.3
```
</details>
**Search keywords**: type number input field
**Order ID**: 101169
**Search keywords**: | new feature,component: text field,package: material-ui | low | Major |
2,627,207,921 | neovim | ext_popupumenu lacks some highlight attributes for matched text | ### Problem
Noticed that now the matched text is rendered in bold in the Pumenu.
### Expected behavior
It is not possible to reproduce the highlighting of the matched text. ext-uis should at least be able to match the capabilities of the builtin ui ? | enhancement,ui-extensibility | low | Minor |
2,627,248,628 | ollama | Run LLM directly in Golang App without Ollama Server | Hello everyone, I would like to know if it is possible to run an all-minilm LLM model directly in my Golang App without having to make calls to the Ollama Server http://localhost:11434/api
I would like to take a small "all-minilm" model and use the //go:embed model/* to already have the tool embedded in the Golang binary.
The idea would be to simplify the use and infrastructure so as not to need to set up an extra Docker Container or VM, not to mention avoiding network latency.
I would like to use Ollama as a library and import the necessary parts in my Golang App.
I couldn't find any examples, if there is someone more experienced and can help me, I would appreciate it. | feature request | low | Minor |
2,627,268,997 | svelte | Sibling Combinator combined with `:has` can be improperly marked as unused | ### Describe the bug
I've got some complex sibling combinator + `:has` css selectors that match the DOM but are reported as unused by Svelte. Through further testing, it appears that some trivial cases are incorrectly marked as unused.
### Reproduction
1. Open `./packages/svelte/tests/css/samples/has/input.svelte`
2. Add the following code to the bottom of the `style` block
```
x:has(+ c) {
color: green;
}
x:has(~ c) {
color: green;
}
```
Notice that these are valid selectors based on the given DOM structure
3. Run the test. It now fails with 2 `css_unused_selector` errors. I've found that wrapping `c` in `:global()` seems to get rid of the errors, but I'm not sure if that should be required to get this selector working.
### Logs
_No response_
### System Info
```shell
Svelte Version - 5.1.6
```
### Severity
annoyance | css | low | Critical |
2,627,284,960 | material-ui | [material-ui][Menu] Let buttons opening menus have an activated state | ### Summary
If having a couple of buttons, each opening a menu. It is confusing to me which button the menu is connected to as they do not have any visual indication.
### Examples
Material Design has an [Activated state](https://m2.material.io/design/interaction/states.html#activated) which could be used to cover this.
Here is a sandbox with how this could be visualized: https://codesandbox.io/p/sandbox/menu-buttons-activated-state-yfpm57
Images from the sandbox above:
Activated state styling
 
Compared to existing default styling
 
### Motivation
I want to make the connection between the button and the menu easier to understand, this might be useful if there are multiple menus next to each other, especially if they use icons instead of text.
While it is easy to implement in an application using MUI, I think the concept is important enough to warrant including it in MUI itself.
**Search keywords**: button menu activated | new feature,design: material,waiting for ๐,component: menu,component: button | low | Minor |
2,627,297,995 | vscode | terminal history does not work or gets wrong version of fish_history - Linux Snap |
Type: <b>Bug</b>
in snap package rev 173 terminal history no longer works correctly. Reverting to snap rev 172 makes it work again.
In snap rev 173, noticed that on startup vscode copies an obsolete bash_history (instead of the correct ~/.local/share/fish/fish_hitory) file from the home folder and puts its content into ~/snap/code/173/.local/share/fish/fish_history
result no or wrong old terminal history in vscode terminal
VS Code version: Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95, 2024-10-28T20:16:24.561Z)
OS version: Linux x64 6.11.0-9-generic snap
Modes:
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz (16 x 1198)|
|GPU Status|2d_canvas: unavailable_software<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>opengl: disabled_off<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: disabled_software<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: unavailable_software<br>webgl2: unavailable_software<br>webgpu: disabled_off<br>webnn: unavailable_software|
|Load (avg)|1, 1, 1|
|Memory (System)|30.01GB (18.32GB free)|
|Process Argv|--no-sandbox --force-user-env|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu|
|XDG_SESSION_TYPE|wayland|
</details><details><summary>Extensions (18)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-pandoc|Chr|0.4.8
continue|Con|0.8.55
dart-code|Dar|3.100.0
flutter|Dar|3.100.0
vscode-markdownlint|Dav|0.56.0
languagetool-linter|dav|0.24.2
vscode-github-actions|git|0.27.0
caddyfile-support|mat|0.4.0
vscode-docker|ms-|1.29.3
vscode-kubernetes-tools|ms-|1.3.18
remote-containers|ms-|0.388.0
remote-ssh|ms-|0.115.0
remote-ssh-edit|ms-|0.87.0
remote-explorer|ms-|0.4.3
vscode-commons|red|0.0.6
vscode-yaml|red|1.15.0
markdown-preview-enhanced|shd|0.8.14
vscode-gradle|vsc|3.16.4
</details>
<!-- generated by issue reporter --> | bug,linux,snap,regression,terminal-shell-fish | medium | Critical |
2,627,309,772 | next.js | Build failing to complete only in CI | ### Link to the code that reproduces this issue
https://github.com/codecov/codecov-javascript-bundler-plugins/tree/main/integration-tests/test-apps/nextjs
### To Reproduce
We have been unable to reproduce the issue locally, both while attempting to build the app standalone, as well as attempting to run the integration tests locally as well. However, it has been failing consistently in our CI pipeline, while attempting to debug this issue: [Pull Request](https://github.com/codecov/codecov-javascript-bundler-plugins/pull/185).
### Current vs. Expected behavior
Our test application was building fine and passing our integration tests on Next 14:
```
> nextjs@0.1.0 build /home/runner/work/codecov-javascript-bundler-plugins/codecov-javascript-bundler-plugins/integration-tests/test-apps/nextjs
> next build
โ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
โฒ Next.js 14.2.5
Creating an optimized production build ...
[codecov] Detecting CI provider
[codecov] Detected CI provider: GitHub Actions
[codecov] Using commit: 7e994169ed0ed50d070bb2f920342d0968eb04a6
[codecov] Using compareSha: null
[codecov] Attempting to fetch `get-pre-signed-url`, attempt: 1
[codecov] Successfully pre-signed URL fetched
[codecov] Attempting to fetch `upload-stats`, attempt: 1
[codecov] Successfully uploaded stats for bundle: test-nextjs-v14-server-cjs
[codecov] Detecting CI provider
[codecov] Detected CI provider: GitHub Actions
[codecov] Using commit: 7e994169ed0ed50d070bb2f920342d0968eb04a6
[codecov] Using compareSha: null
[codecov] Attempting to fetch `get-pre-signed-url`, attempt: 1
[codecov] Successfully pre-signed URL fetched
[codecov] Attempting to fetch `upload-stats`, attempt: 1
[codecov] Successfully uploaded stats for bundle: test-nextjs-v14-edge-server-array-push
[codecov] Detecting CI provider
[codecov] Detected CI provider: GitHub Actions
[codecov] Using commit: 7e994169ed0ed50d070bb2f920342d0968eb04a6
[codecov] Using compareSha: null
[codecov] Attempting to fetch `get-pre-signed-url`, attempt: 1
[codecov] Successfully pre-signed URL fetched
[codecov] Attempting to fetch `upload-stats`, attempt: 1
[codecov] Successfully uploaded stats for bundle: test-nextjs-v14-client-array-push
โ Compiled successfully
Linting and checking validity of types ...
โ The Next.js plugin was not detected in your ESLint configuration. See https://nextjs.org/docs/basic-features/eslint#migrating-existing-config
Collecting page data ...
Generating static pages (0/5) ...
Generating static pages (1/5)
Generating static pages (2/5)
Generating static pages (3/5)
โ Generating static pages (5/5)
Finalizing page optimization ...
Collecting build traces ...
Route (app) Size First Load JS
โ โ / 5.44 kB 92.5 kB
โ โ /_not-found 872 B 87.9 kB
+ First Load JS shared by all 87 kB
โ chunks/538-5b4d10cffa6c1cf9.js 31.5 kB
โ chunks/7820dfc2-ee432587636317c8.js 53.6 kB
โ other shared chunks (total) 1.86 kB
โ (Static) prerendered as static content
(pass) Generating nextjs stats > 14 > matches the snapshot [22997.23ms]
```
However, after updating to Next 15, and also updating other dependencies (React, etc.) our builds are no longer successful, in turn our tests are timing out:
```
> nextjs@0.1.0 build /home/runner/work/codecov-javascript-bundler-plugins/codecov-javascript-bundler-plugins/integration-tests/test-apps/nextjs
> next build
โ No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Attention: Next.js now collects completely anonymous telemetry regarding usage.
This information is used to shape Next.js' roadmap and prioritize features.
You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
https://nextjs.org/telemetry
โฒ Next.js 15.0.2
Creating an optimized production build ...
[codecov] Detecting CI provider
[codecov] Detected CI provider: GitHub Actions
[codecov] Using commit: 8e34196ab03754139953f22bff547edf44d7621a
[codecov] Using compareSha: 7e994169ed0ed50d070bb2f9203[42](https://github.com/codecov/codecov-javascript-bundler-plugins/actions/runs/11615654479/job/32346786999#step:10:43)d0968eb04a6
[codecov] Attempting to fetch `get-pre-signed-url`, attempt: 1
[codecov] Successfully pre-signed URL fetched
[codecov] Attempting to fetch `upload-stats`, attempt: 1
[codecov] Successfully uploaded stats for bundle: test-nextjs-v15-server-cjs
[codecov] Detecting CI provider
[codecov] Detected CI provider: GitHub Actions
[codecov] Using commit: 8e34196ab03754139953f22bff547edf[44](https://github.com/codecov/codecov-javascript-bundler-plugins/actions/runs/11615654479/job/32346786999#step:10:45)d7621a
[codecov] Using compareSha: 7e994169ed0ed50d070bb2f920342d0968eb04a6
[codecov] Attempting to fetch `get-pre-signed-url`, attempt: 1
[codecov] Successfully pre-signed URL fetched
[codecov] Attempting to fetch `upload-stats`, attempt: 1
[codecov] Successfully uploaded stats for bundle: test-nextjs-v15-edge-server-array-push
[codecov] Detecting CI provider
[codecov] Detected CI provider: GitHub Actions
[codecov] Using commit: 8e34196ab03754139953f22bff5[47](https://github.com/codecov/codecov-javascript-bundler-plugins/actions/runs/11615654479/job/32346786999#step:10:48)edf44d7621a
[codecov] Using compareSha: 7e994169ed0ed50d070bb2f920342d0968eb04a6
[codecov] Attempting to fetch `get-pre-signed-url`, attempt: 1
[codecov] Successfully pre-signed URL fetched
[codecov] Attempting to fetch `upload-stats`, attempt: 1
[codecov] Successfully uploaded stats for bundle: test-nextjs-v15-client-array-push
โ Compiled successfully
Linting and checking validity of types ...
Collecting page data ...
Generating static pages (0/5) ...
Generating static pages (1/5)
Generating static pages (2/5)
Generating static pages (3/5)
โ Generating static pages (5/5)
Finalizing page optimization ...
Collecting build traces ...
Error:
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
at
error: Test "matches the snapshot" timed out after 2[50](https://github.com/codecov/codecov-javascript-bundler-plugins/actions/runs/11615654479/job/32346786999#step:10:51)00ms
```
And occasionally we saw this error appear, however due to the nature of GHA (I believe), we're not able to get the full picture:
### Provide environment information
```bash
Operating System:
Platform: linux
Arch: x64
Version: #26~22.04.1-Ubuntu SMP Thu Jul 11 22:33:04 UTC 2024
Available memory (MB): 15982
Available CPU cores: 4
Binaries:
Node: 18.20.4
npm: 10.7.0
Yarn: 1.22.22
pnpm: 9.12.3
Relevant Packages:
next: 15.0.2 // Latest available version is detected (15.0.2).
eslint-config-next: 14.2.3
react: 19.0.0-rc-02c0e824-20241028
react-dom: 19.0.0-rc-02c0e824-20241028
typescript: 5.3.3
```
### Which area(s) are affected? (Select all that apply)
Not sure
### Which stage(s) are affected? (Select all that apply)
next build (local)
### Additional context
Just to add as well, this build is also failing on Node 20.x. | bug | low | Critical |
2,627,409,318 | rust | WASI unwinding is broken in release | This is target `wasm32-wasip1` with `panic = "unwind"`, running on V8. I tried this code:
```rust
struct Dropper;
impl Drop for Dropper {
fn drop(&mut self) {
let _ = std::panic::catch_unwind(|| {
std::panic::resume_unwind(Box::new(String::from("About to do some nifty corruption")))
});
}
}
fn main() {
let _dropper = Dropper;
panic!("Triggering landing pad");
}
```
I expected to see this happen: a panic message, followed by the process exit.
Instead, this happened:
```
thread 'main' panicked at src/main.rs:13:5:
Triggering landing pad
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:1
RuntimeError: memory access out of bounds
at garbage2-65ce2afe6e737f0d.wasm.dlfree (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[140]:0x7464)
at garbage2-65ce2afe6e737f0d.wasm.free (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[139]:0x70bc)
at garbage2-65ce2afe6e737f0d.wasm.__rdl_dealloc (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[26]:0xe0e)
at garbage2-65ce2afe6e737f0d.wasm.__rust_dealloc (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[14]:0x577)
at garbage2-65ce2afe6e737f0d.wasm._ZN3std2rt19lang_start_internal17hfafca2af8f4e8869E (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[72]:0x2b91)
at garbage2-65ce2afe6e737f0d.wasm.__main_void (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[12]:0x545)
at garbage2-65ce2afe6e737f0d.wasm._start (wasm://wasm/garbage2-65ce2afe6e737f0d.wasm-0003f686:wasm-function[5]:0x297)
at WASI.start (node:wasi:136:7)
at file:///home/purplesyringa/garbage2/wasi.mjs:12:6
Node.js v20.4.0
```
### Meta
`rustc --version --verbose`:
```
rustc 1.84.0-nightly (1e4f10ba6 2024-10-29)
binary: rustc
commit-hash: 1e4f10ba6476e48a42a79b9f846a2d9366525b9e
commit-date: 2024-10-29
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```
`node --version`:
```
v20.4.0
```
Compile with `--release`, run with
```javascript
import { WASI } from "node:wasi";
import { readFile } from "node:fs/promises";
const wasi = new WASI({
version: "preview1",
args: process.argv.slice(2),
env: process.env,
});
const wasm = await WebAssembly.compile(await readFile(process.argv[2]));
const instance = await WebAssembly.instantiate(wasm, wasi.getImportObject());
wasi.start(instance);
```
I'm not sure if this is a rustc bug, an LLVM bug, or a V8 bug, but I thought this might be important to track. | A-LLVM,P-medium,T-compiler,O-wasm,C-bug,T-libs,O-wasi,A-panic,I-miscompile | medium | Critical |
2,627,476,724 | flutter | ci.yaml validation check might unexpectedly fail, failing the PR and autosubmit | This was encountered on dart->engine https://github.com/flutter/engine/pull/56267 resulting in failed roll attempt.
The culprit was identified as github "ci.yaml validation" action being sent out while cocoon was restarting after auto-deploy. | team-infra,P2,triaged-infra | low | Critical |
2,627,539,871 | godot | Editor plugin hooks return immediatly ignoring `await` | ### Tested versions
4.4.dev
### System information
Windows 11 - Vulkan (Forward+)
### Issue description
Coroutines don't work in `EditorPlugin` hooks like:
```gdscript
@tool
extends EditorPlugin
# The project runs immediately and "finished build check" prints after it
func _build() -> bool:
print("awaiting _build")
await get_tree().create_timer(3).timeout
print("finished _build")
return false
```
Other hooks used together with `EditorPlugin` like `EditorExportPlugin._customize_resource` also return immediately ignoring `await`. This makes it impossible to customize resources that depend on threaded features like `NavigationMesh` baking or the render thread.
### Steps to reproduce
Run MRP. Build should not return because `_build()` in "res://addons/plugin/plugin.gd" returns false.
But it runs anyway and "Finished Build" is printed 3 seconds later.
Export MRP. It should print "finished _customize_resource" after exporting.
But it exports immediately and the message is printed 3 seconds later.
### Minimal reproduction project (MRP)
[plugin-await-issue.zip](https://github.com/user-attachments/files/17591683/plugin-await-issue.zip)
| discussion,topic:gdscript,topic:editor,documentation,topic:plugin | low | Minor |
2,627,541,809 | go | cmd/go: TestScript/cover_atomic_pkgall failures | ```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/cover_atomic_pkgall"
```
Issue created automatically to collect these failures.
Example ([log](https://ci.chromium.org/b/8732602684851905153)):
=== RUN TestScript/cover_atomic_pkgall
=== PAUSE TestScript/cover_atomic_pkgall
=== CONT TestScript/cover_atomic_pkgall
script_test.go:139: 2024-10-31T01:45:29Z
script_test.go:141: $WORK=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-997808213/tmpdir2031948626/cover_atomic_pkgall1783398869
script_test.go:163:
PATH=/home/swarming/.swarming/w/ir/x/t/cmd-go-test-997808213/tmpdir2031948626/testbin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/x/w/goroot/bin:/home/swarming/.swarming/w/ir/cache/tools/bin:/home/swarming/.swarming/w/ir/bbagent_utility_packages:/home/swarming/.swarming/w/ir/bbagent_utility_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages:/home/swarming/.swarming/w/ir/cipd_bin_packages/bin:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3:/home/swarming/.swarming/w/ir/cipd_bin_packages/cpython3/bin:/home/swarming/.swarming/w/ir/cache/cipd_client:/home/swarming/.swarming/w/ir/cache/cipd_client/bin:/home/swarming/.swarming/cipd_cache/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOME=/no-home
CCACHE_DISABLE=1
GOARCH=amd64
...
panic: runtime error: slice bounds out of range [:4294972028] with capacity 15336
goroutine 1 gp=0xc000004380 m=0 mp=0x90aac0 [running]:
panic({0x726360?, 0xc0001f6078?})
/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:806 +0x168 fp=0xc00002ebc8 sp=0xc00002eb18 pc=0x4aa5e8
runtime.goPanicSliceAcap(0x10000127c, 0x3be8)
/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:141 +0x74 fp=0xc00002ec08 sp=0xc00002ebc8 pc=0x46f834
internal/coverage/cfile.(*emitState).VisitFuncs(0xc0001c8140, 0xc0001a22b8)
/home/swarming/.swarming/w/ir/x/w/goroot/src/internal/coverage/cfile/emit.go:478 +0x11c8 fp=0xc00002ee88 sp=0xc00002ec08 pc=0x66a368
internal/coverage/encodecounter.(*CoverageDataWriter).writeCounters(0xc0001c6190, {0x781640, 0xc0001c8140}, 0xc0001b4080)
...
runtime.runfinq()
/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mfinal.go:193 +0x145 fp=0xc00007dfe0 sp=0xc00007de20 pc=0x450305
runtime.goexit({})
/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/asm_amd64.s:1700 +0x1 fp=0xc00007dfe8 sp=0xc00007dfe0 pc=0x4b1a01
created by runtime.createfing in goroutine 1
/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mfinal.go:163 +0x3d
FAIL x 0.181s
FAIL
script_test.go:163: FAIL: testdata/script/cover_atomic_pkgall.txt:10: go test -coverpkg=all -race x: exit status 1
--- FAIL: TestScript/cover_atomic_pkgall (77.73s)
โ [watchflakes](https://go.dev/wiki/Watchflakes)
| NeedsInvestigation | low | Critical |
2,627,543,050 | opencv | The dnn Tensorflow parser doesn't support ExpandDims layer with the new dnn engine | ### System Information
OpenCV 5.x
### Detailed description
OpenCV dnn uses nchw layout, Tensorflow uses nhwc layout. When dnn parser handles a tensorflow layer with an axis argument, it should convert the axis from nhwc to ncwh. However the parser doesn't know the number of dimensions of the input tensor, so it runs the shape inference of all previous layers to calculate it. But the new dnn engine doesn't support shape inference when the network is not fully built.
### Steps to reproduce
run Test_TensorFlow_layers.ExpandDims tests
### Issue submission checklist
- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc) | bug | low | Minor |
2,627,547,208 | go | x/build/cmd/relui: shows a misleading prompt that says "immediately run" when scheduling a workflow (i.e., it doesn't run immediately) | When creating a workflow to be executed, relui always shows a prompt that asks:
"This will create and immediately run this workflow. Ready to proceed?"
The "immediately run" part is true whenever the schedule type is "immediately run", but not when the workflow is being scheduled to run at a later date, or on a schedule. In those cases, the workflow doesn't run immediately as the prompt says.
This would be good to fix to reduce confusion. The current logic has a good property that the confirmation prompt is always there as soon as the page loads, without any JavaScript execution delay. We should preserve that property when fixing this.
CC @golang/release. | help wanted,Builders,NeedsInvestigation,Friction | low | Major |
2,627,560,714 | vscode | arrow navigation diff view will go to prev/next cell | 1. enable a11y optimized mode (so that the diff view shows up in the inline chat)
2. create a notebook and have some code in the second cell
3. ask for an edit in the second cell
4. use the arrow keys to scroll through the diff
๐ down arrow will work since it's the last cell, but up arrow will move to the first cell
https://github.com/user-attachments/assets/44b14bb0-8f15-40fa-9948-ae3019a55811
The `list.focusUp` command is sent to the cell list views, since that is the last focused
| bug,accessibility,notebook,inline-chat | low | Minor |
2,627,581,786 | flutter | [path_parsing] Add docs for public APIs | When importing `path_parsing`, I had to add `// ignore`s for public_member_api_docs, because a lot of public APIs were undocumented, and figuring out all the APIs and documenting them was out of scope for the import. We should fix that and remove the `// ignore` so that we are following the best practices that our `analysis_options` are intended to enforce.
(This is also a `pub.dev` score demerit, and it's nice for packages under the `flutter.dev` publisher to set a good example in terms of following the practices we want the ecosystem to adopt.) | package,team-ecosystem,P3,triaged-ecosystem,p: path_parsing | low | Minor |
2,627,590,081 | flutter | [path_parsing] Fix private type in public API violations | When importing `path_parsing`, I had to add `// ignore`s for library_private_types_in_public_api, because refactoring code visibility was out of scope for the import. We should fix that and remove the `// ignore` so that we are following the best practices that our `analysis_options` are intended to enforce.
I suspect that the right fix is to make the things using private types private; technically that would be a breaking change, but since there shouldn't be any way for clients to be using them we might be able to do it as a non-breaking change. We'd want to check [the public packages using it](https://pub.dev/packages?q=dependency%3Apath_parsing) to ensure at least none of them are somehow referencing those symbols.
Alternately we could make the types public. I didn't evaluate how much that adds to our permanent API surface. | package,team-ecosystem,P3,triaged-ecosystem,p: path_parsing | low | Minor |
2,627,603,303 | kubernetes | Declarative defaults should handle cases where a field is feature-gated | Given a non-gated field, I can say `// +default=12345`, which will generate code like:
```
if obj.Field == nil {
var val int64 = 12345
obj.Field = &val
}
````
If I have a feature-gated field, I want the default value ONLY IF allowed by the gate. For example:
pkg/apis/core/v1/defaults.go:
```
if utilfeature.DefaultFeatureGate.Enabled(features.ImageVolume) && obj.Image != nil && obj.Image.PullPolicy == "" {
// PullPolicy defaults to Always if :latest tag is specified, or IfNotPresent otherwise.
_, tag, _, _ := parsers.ParseImageName(obj.Image.Reference)
if tag == "latest" {
obj.Image.PullPolicy = v1.PullAlways
} else {
obj.Image.PullPolicy = v1.PullIfNotPresent
}
}
```
It would be nice if I could say something like:
```
// +default=12345
// +featureGate=MyGateName
Field *int64
```
And have the generator produce:
```
if utilfeature.DefaultFeatureGate.Enabled(features.MyGateName) && obj.Field == nil {
var val int64 = 12345
obj.Field = &val
}
````
xref https://github.com/kubernetes/kubernetes/issues/120847
cc @jpbetz | sig/api-machinery,kind/feature,area/code-generation,triage/accepted | low | Minor |
2,627,628,408 | godot | 2D HDR makes scenes significantly darker | ### Tested versions
Godot 4.3 Stable
### System information
Windows 10 x64, RTX 3060 Ti, Ryzen 5600x
### Issue description
Enabling โHDRโ makes everything (and especially HDRi) significantly darker. I've tried several methods to locate any relevant side of the issue (physical light units, auto exposure, etc). Nothing changes that, it's just right away darker. No screen shaders are applied. It also compresses the image significantly (almost making it look like 6-bit)
### Steps to reproduce
Select 3D scene
Enable 2D HDR
### Minimal reproduction project (MRP)
N/A | bug,topic:rendering,topic:2d | low | Minor |
2,627,640,051 | vscode | Pytest Test Discovery Issue in Multi-root Workspace with Folder-specific Settings | I'm encountering an issue with Pytest test discovery in a multi-root workspace setup in Visual Studio Code. My workspace includes two folders: api and authorizer. Each folder contains its own set of tests within a tests subdirectory.
For each folder, I have a settings.json file located in the .vscode directory with the following configuration:
{
"python.testing.pytestArgs": [
"tests"
],
"python.testing.unittestEnabled": false,
"python.testing.pytestEnabled": true,
"python.envFile": "${workspaceFolder}/tests/dev.env"
}
Despite this setup, when I open the Testing tab in VSCode, the paths to the test files are incorrect. The tests directory is missing from the paths, resulting in errors such as:
CRIT pytest at 'authorizer': Execution of the test "....../authorizer/application/test_authorizer_token.py" failed: Error: Process exited with code 4: ERROR: file or directory not found: ....../authorizer/application/test_authorizer_token.py
The correct path should be:
....../authorizer/tests/application/test_authorizer_token.py
I've ensured that each folder has its own .vscode/settings.json with the correct pytestArgs, and I've tried using absolute paths as well. All extensions and VSCode itself are up to date.
Has anyone experienced a similar issue or have any suggestions on how to resolve this path resolution problem?
Thank you!
| bug,workbench-multiroot,testing,python | low | Critical |
2,627,662,139 | tauri | [bug] Different Path for APK and AAB file after build | ### Different Filepath for android Build
### Reproduction
https://github.com/Algostract/portfolio-shirsendu
### Expected behavior
To have one folder path either universal/release or universalRelease
### Full `tauri info` output
```text
[โ] Environment
- OS: Windows 10.0.22631 x86_64 (X64)
โ WebView2: 130.0.2849.56
โ MSVC: Visual Studio Build Tools 2022
โ 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-pc-windows-msvc (default)
- node: 20.18.0
- pnpm: 9.12.3
- npm: 10.8.2
- deno: deno 2.0.4
[-] Packages
- tauri ๐ฆ: 2.0.6
- tauri-build ๐ฆ: 2.0.2
- wry ๐ฆ: 0.46.3
- tao ๐ฆ: 0.30.3
- @tauri-apps/api ๎: 2.0.3
- @tauri-apps/cli ๎: 2.0.5
[-] Plugins
- tauri-plugin-log ๐ฆ: 2.0.1
- @tauri-apps/plugin-log ๎: not installed!
[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:3000/
- framework: Vue.js (Nuxt)
- bundler: Vite
```
### Stack trace
_No response_
### Additional context
_No response_ | type: feature request,priority: 3 low | low | Critical |
2,627,676,440 | TypeScript | Destructuring into an empty object vs an object with existing properties yields different results | ### ๐ Search Terms
"destructuring", "record"
### ๐ Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ.
### โฏ Playground Link
https://www.typescriptlang.org/play/?ts=5.6.3#code/MYewdgzgLgBATgU1HAJgdQJZQBYGUpwZgDmEAXDAEpIioA80hJANDI0cQHwwC8MA3gF8A3AChRCAB4AHWrFCRYiZOizYAcgFcAtgCMEcclRr12LGGB3643Pv1EwYUggEMACnBDSDUAJ4UABmYHGAA6cOVaVRx8JlJgkSA
### ๐ป Code
This raises a type error:
```ts
const recordWithStrings: Record<string, string> = {};
export const recordWithNumbers: Record<string, number> = {
...recordWithStrings,
};
```
and this doesn't:
```ts
const recordWithStrings: Record<string, string> = {};
export const recordWithNumbers: Record<string, number> = {
extraProperty: 0,
...recordWithStrings,
};
```
Is there a sound reason for that?
### ๐ Actual behavior
The 2nd example doesn't raise a type error.
### ๐ Expected behavior
The 2nd example should raise a type error.
### Additional information about the issue
_No response_ | Bug,Help Wanted | low | Critical |
2,627,724,970 | bitcoin | CI: Improve documentation around replicating CI locally | I've received some feedback that replicating CI jobs locally isn't straightforward. Perhaps the documentation can be improved in this area?
@maflcko I understand you had some improvements in mind? Happy to also work on this. | Brainstorming,Docs,Build system,Tests | low | Minor |
2,627,728,564 | bitcoin | CI: Make failure message easier to spot | Sometimes during a CI failure the actual error message can be buried in a wall of log output and not immediately clear. Ideally it should be obvious why a CI job has failed.
CC @maflcko | Brainstorming,Tests | low | Critical |
2,627,791,051 | transformers | VLMs Processors are not fully consistent in the inputs formats they accept | ### Summary of accepted inputs for image-text-to-text-models
| Model | Uses Image Tokens | Accepts URL | Accepts PIL | Accepts Path | Accepts Non-Nested Batched Images (one per text) | Accepts Nested Images (one per text) | Accepts Nested Images (Multiple images per text, same number for each text) | Accepts Nested Images (Multiple images per text, different number for each text) |
|---|---|---|---|---|---|---|---|---|
| Pix2Struct | โ | โ | โ
| โ | โ
| โ | โ | โ |
| BLIP | โ | โ | โ
| โ | โ
| โ | โ | โ |
| Donut | โ | โ | โ
| โ | โ
| โ | โ | โ |
| UDOP | โ | โ | โ
| โ | โ
| โ | โ | โ |
| GIT | โ | โ | โ
| โ | โ
| โ | โ | โ |
| KOSMOS-2 | โ | โ | โ
| โ | โ
| โ | โ | โ |
| Idefics | โ | โ
| โ
| โ | โ
| โ | โ | โ |
| FUYU | โ | โ | โ
| โ | โ
| โ
| โ | โ |
| Llava | โ
| โ | โ
| โ | โ
| โ | โ | โ |
| VipLlava | โ
| โ | โ
| โ | โ
| โ | โ | โ |
| BLIP2 | โ
| โ | โ
| โ | โ
| โ | โ | โ |
| Qwen2-VL | โ
| โ | โ
| โ | โ
* crash when padding set to True | โ | โ
| โ
|
| Chameleon | โ
| โ | โ
| โ | โ* works when padding manually set to True | โ
| โ
| โ
|
| Pixtral | โ
| โ
| โ
| โ | โ | โ
| โ
| โ |
| Paligemma | โ
| โ | โ
| โ | โ
| โ
| โ
| โ
|
| Llava-Next | โ
| โ | โ
| โ | โ
| โ
| โ
| โ
|
| LLaVA-OneVision | โ
| โ | โ
| โ | โ
| โ
| โ
| โ
|
| Mllama | โ
| โ | โ
| โ | โ
| โ
| โ
| โ
|
| InstructBLIP | โ
| โ | โ
| โ | โ
| โ
| โ
| โ
|
| Idefics2 | โ
| โ
| โ
| โ | โ
| โ
| โ
| โ
|
| Idefics3 | โ
| โ
| โ
| โ | โ
| โ
| โ
| โ
|
### Reproduction
For instance, with these inputs:
```python
import requests
from PIL import Image
image_ny = "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg"
image_chicago = "https://cdn.britannica.com/59/94459-050-DBA42467/Skyline-Chicago.jpg"
url_pokemon = "https://huggingface.co/datasets/sayakpaul/sample-datasets/resolve/main/pokemon.png"
image_pokemon = Image.open(requests.get(url_pokemon, stream=True).raw)
text_batched_image_tokens = [
"<image> <image> Are these the same cities? If not what cities are these?",
"<image> Describe what you see in this image. I see",
]
```
This will crash at the processor level:
```python
from transformers import pipeline
pipe = pipeline(task="image-text-to-text", model="llava-hf/llava-interleave-qwen-0.5b-hf")
pipe(
images=[[image_ny, image_chicago], [image_pokemon]],
text=text_batched_image_tokens,
)
```
But this will work:
```python
from transformers import pipeline
pipe = pipeline(task="image-text-to-text", model="llava-hf/llava-onevision-qwen2-0.5b-ov-hf")
pipe(
images=[[image_ny, image_chicago], [image_pokemon]],
text=text_batched_image_tokens,
)
```
### Expected behavior
Except for model-specific limitations or features, vlms used for similar tasks should accept a similar set of inputs format | bug,Processing | low | Critical |
2,627,796,469 | rust | Tracking issue for release notes of #131477: macOS: Always pass SDK root when linking with `cc`, and pass it via `SDKROOT` env var |
This issue tracks the release notes text for #131477.
### 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, ...)
- [macOS: Always pass SDK root when linking with `cc`, and pass it via `SDKROOT` env var](https://github.com/rust-lang/rust/pull/131477)
````
> [!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 @madsmtm, @nnethercote -- origin issue/PR authors and assignees for starting to draft text
| T-compiler,relnotes,O-apple,relnotes-tracking-issue | low | Minor |
2,627,816,446 | flutter | [impeller] opengles golden tests don't have antialiasing | seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: impeller_Play_AiksTest_FilledEllipsesRenderCorrectly
## metal
## opengles
| P1,e: impeller,team-engine,triaged-engine,e: opengl | medium | Major |
2,627,833,909 | flutter | [impeller] AiksTest_ColorFilterAdvancedBlend is blurry on opengles | seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: AiksTest_ColorFilterAdvancedBlend
Look at the details in the image of the town. They are more crisp on vulkan and metal.
## metal
## opengles
| P2,e: impeller,team-engine,triaged-engine,e: opengl | low | Minor |
2,627,854,024 | flutter | [impeller] AiksTest_ColorMatrixFilterSubpassCollapseOptimization missing outline on opengles | seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: AiksTest_ColorMatrixFilterSubpassCollapseOptimization
## metal
## opengles
| P2,e: impeller,team-engine,triaged-engine,e: opengl | low | Major |
2,627,858,251 | pytorch | Add 'no_type_conversion' flag to register_buffer() | ### ๐ The feature, motivation and pitch
Some modules need to keep float32/float64/float16 constant Tensors (registered as buffers) unaffected by .to(dtype=float16, etc) operations. The most straightforward way to implement that is to add a flag to register_buffer that would mark it as guarded from type conversion (no assumptions on underlying implementation).
### Alternatives
Currently, the only consistent way to keep those constants from being flipped on module type conversion is to declare those Tensors as matching length integers (int32 for float32 etc.) and use cast. Overriding a single module to() does not work as the conversion does not honor module hierarchy so that override would be ignored if to() is invoked by the containing Module.
Using the cast works fine for eager execution, but introduces issues with ONNX export ( see https://github.com/pytorch/pytorch/issues/126921)
### Additional context
_No response_
cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki | module: onnx,triaged | low | Major |
2,627,860,076 | flutter | [impeller] CanRenderSweepGradientManyColorsRepeat has artifact on opengles | seen in dcc8c65eb3d1d43decb52d276b7f29390ea67c9d
test: AiksTest_CanRenderSweepGradientManyColorsRepeat
The artifact is on the north east line radiating from the center of the gradient.
## metal
## opengles
| P2,e: impeller,team-engine,triaged-engine,e: opengl | low | Minor |
2,627,910,104 | flutter | Impeller golden tests (and others?) require developers to manually update the list of goldens | There are a couple of golden mechanisms in the engine that have lists of the expected golden file outputs. At least one of these was created when we discovered that sometimes a golden file might be missing and therefore not checked. This manual check of which files were generated solves that issue, but it seems like we should be able to rely on the golden tests to throw an exception or expectation failure which fails the test if a golden file isn't written (for whatever reason). | team,c: proposal,P2,c: tech-debt,team-engine,triaged-engine | low | Critical |
2,627,913,038 | flutter | ci/format.sh should verify that Impeller golden test list is sorted | Part of the Impeller golden test suite is to verify if the list of generated goldens is complete and it uses the `impeller_golden_tests_output.txt` file to double check the list.
Unfortunately, that check will also fail if the list is complete, but not sorted correctly. We should have `ci/format.sh` check this condition to help developers head these errors off at an early pass. | a: tests,engine,c: proposal,P3,e: impeller,team-engine,triaged-engine | low | Critical |
2,627,920,417 | flutter | building `Profile-ios-Flutter.xcframework` took 40m | Expected time is 16s.
## problem example
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/36781/overview
## positive example
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/36735/overview | team-infra,P2,c: flake,triaged-infra | low | Minor |
2,627,927,208 | flutter | Implement Zones at the framework level (e.g. as a Widget) | ### Use case
Allow coarse-grained management of async requests and dependency injection
Example 1: A user logs in, some widgets create some async requests and other local state, and the user logs out. How do we guarantee that all authenticated async requests and streams are canceled or at least will not interfere with the next user?
Example 2: We can use a top-level error handler to manage async errors at a global level, and asyncGuard https://github.com/flutter/flutter/blob/1050959d198bf6843ab6ec256fa4f58fc7009c57/packages/flutter_tools/lib/src/base/async_guard.dart#L11 on every single await to manage them at a local level, but there is no way to composably manage errors at the subtree level.
Example 3: Flutter DI usually uses the BuildContext for scope, but in complex apps we can see that BuildContexts are not exactly the right abstraction for this purpose, for example for ContextActions whose `invoke` has a nullable BuildContext (https://api.flutter.dev/flutter/widgets/ContextAction/invoke.html), or for example running some asynchronous work before or after navigating away from a screen when a user presses a button or dismisses a Dismissible. The direction of newer frameworks is often to introduce codegen, magical APIs and globals to manage services separately from widget trees. https://pub.dev/packages/scoped_deps shows how to do very simple DI with zones in simple Dart apps, but it does not work in a widget tree context. Nested zones could achieve dynamic scoping while decoupling from small widget lifecycles.
### Proposal
Integrate a Zone() widget into the foundational libraries, such that all the framework's work of a child of a Zone(Widget) takes place in the affiliated (Dart) Zone.
For example, Inherited{Widget/Element} would need to look up the correct zone for its dependents and ensure that their didChangeDependencies() were called in the right zone. | c: new feature,framework,c: proposal,P3,team-framework,triaged-framework | low | Critical |
2,627,937,610 | flutter | Investigate whether Web can listen to "pointermove" events on `_viewTarget` | Since https://github.com/flutter/engine/pull/38477, Web listens to "pointermove" events on `_globalTarget` instead of the standard `_viewTarget` because of the default event capturing behaviors. However, the default web capture behavior might be configurable. We might want to revisit it and possibly simplify the code.
This is an issue for a TODO.
See also: https://github.com/flutter/engine/pull/56075#discussion_r1825222209 | engine,platform-web,a: mouse,P2,team-web,triaged-web | low | Minor |
2,627,962,667 | tensorflow | `tf.linalg.lstsq` producing outputs with large inconsistencies between CPU and GPU with `float32` tensors | ### Issue type
Bug
### Have you reproduced the bug with TensorFlow Nightly?
No
### Source
source
### TensorFlow version
2.18.0
### Custom code
Yes
### OS platform and distribution
Linux Ubuntu 20.04
### Mobile device
_No response_
### Python version
3.10
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
12.3
### GPU model and memory
_No response_
### Current behavior?
Passing tensors of `float32` to 'tf.linalg.lstsq' is producing very different output from CPU and GPU.
### Standalone code to reproduce the issue
[colab](https://colab.research.google.com/drive/1Fyh3HQs39NhGlOLEdzpqPKVkznBe6Fe9?usp=sharing)
```shell
import tensorflow as tf
import numpy as np
A = tf.constant([[[[0.37454012, 0.9507143, 0.7319939, 0.5986585, 0.15601864], [0.15599452, 0.05808361, 0.8661761, 0.601115, 0.7080726,], [0.02058449, 0.96990985, 0.83244264,
0.21233912, 0.18182497], [0.1834045, 0.30424225, 0.52475643, 0.43194503, 0.29122913], [0.6118529, 0.13949387, 0.29214466, 0.36636186, 0.45606998]]]], dtype=tf.float32)
B = tf.constant([[[[0.59241456, 0.04645041], [0.94888556, 0.965632,], [0.684233, 0.4401525,], [
0.9093204, 0.25877997], [0.54671025, 0.18485446]]]], dtype=tf.float32)
with tf.device("/gpu:0"):
output_gpu = tf.linalg.lstsq(A, B)
with tf.device( "/cpu:0"):
output_cpu = tf.linalg.lstsq(A, B)
np.testing.assert_allclose(output_cpu, output_gpu.cpu(), atol=100) # AssertionError
```
### Relevant log output
```shell
AssertionError:
Not equal to tolerance rtol=1e-07, atol=100
Mismatched elements: 2 / 10 (20%)
Max absolute difference: 112.95715
Max relative difference: 0.2963447
x: array([[[[-170.69518 , 28.379017],
[ 164.85085 , -28.04222 ],
[-273.4264 , 46.952198],...
y: array([[[[-241.07059 , 40.25023 ],
[ 232.80626 , -39.505226],
[-386.38354 , 66.00629 ],...
```
| type:bug,comp:ops,TF 2.18 | medium | Critical |
2,627,973,848 | pytorch | CPU support for FlexAttention | # Add CPU Compile Support for Flex Attention
There are two implementations of Flex Attention. An unfused Eager Mode implementation that works on most device and, under torch.compile, Inductor will lower to a Triton template. This Triton template is only supported on CUDA and ROCM devices. We currently don't have any support for CPU backends.
We can either update the lowering to dispatch to a fused CPU implementation or we can look to support this via [Triton-CPU](https://github.com/triton-lang/triton-cpu)
cc @ezyang @chauhang @penguinwu @zou3519 @ydwu4 @bdhirsh @yf225 @Chillee @yanboliang @BoyuanFeng | triaged,oncall: pt2,module: higher order operators,oncall: cpu inductor,module: pt2-dispatcher,module: flex attention | low | Minor |
2,627,975,297 | rust | ICE: `internal compiler error[E0391]: cycle detected when computing function signature of impl` | <!--
[31mICE[0m: Rustc ./a.rs '-Zcrate-attr=feature(cmse_nonsecure_entry) --edition=2018 --crate-type=lib -ooutputfile -Zdump-mir-dir=dir' 'error: internal compiler error[E0391]: cycle detected when computing function signature of `<impl at /tmp/im/a.rs:3:1: 3:10>::test`', 'error: internal compiler error[E0391]: cycle detected when computing function signature of `<impl at /tmp/im/a.rs:3:1: 3:10>::test`'
File: /tmp/im/a.rs
-->
auto-reduced (treereduce-rust):
````rust
//@compile-flags: --edition=2018 --crate-type=lib
#![feature(cmse_nonsecure_entry)]
struct Test;
impl Test {
pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
}
````
original:
````rust
struct Test;
impl Test {
pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {
}
}
````
Version information
````
rustc 1.84.0-nightly (a0d98ff0e 2024-10-31)
binary: rustc
commit-hash: a0d98ff0e5b6e1f2c63fd26f68484792621b235c
commit-date: 2024-10-31
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
````
Command:
`/home/matthias/.rustup/toolchains/master/bin/rustc -Zcrate-attr=feature(cmse_nonsecure_entry) --edition=2018 --crate-type=lib`
<details><summary><strong>Program output</strong></summary>
<p>
```
warning: struct `Test` is never constructed
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:1:8
|
1 | struct Test;
| ^^^^
|
= note: `#[warn(dead_code)]` on by default
warning: associated function `test` is never used
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:57
|
3 | impl Test {
| --------- associated function in this implementation
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^
warning: `extern` fn uses type `str`, which is not FFI-safe
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:67
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^ not FFI-safe
|
= help: consider using `*const u8` and a length instead
= note: string slices have no C equivalent
= note: `#[warn(improper_ctypes_definitions)]` on by default
warning: `extern` fn uses type `impl Future<Output = ()>`, which is not FFI-safe
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not FFI-safe
|
= note: opaque types have no C equivalent
warning: 4 warnings emitted
note: no errors encountered even though delayed bugs were created
note: those delayed bugs will now be shown as internal compiler errors
error: internal compiler error[E0391]: cycle detected when computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: ...which requires computing layout of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
= note: ...which requires normalizing `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
note: ...which requires computing type of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires computing type of opaque `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires type-checking `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires computing the opaque types defined by `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: ...which again requires computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`, completing the cycle
note: cycle used when checking that `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test` is well-formed
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information
note: delayed at compiler/rustc_query_system/src/query/job.rs:596:16 - disabled backtrace
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error: internal compiler error[E0391]: cycle detected when computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: ...which requires computing layout of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
= note: ...which requires normalizing `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
note: ...which requires computing type of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires computing type of opaque `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires type-checking `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: ...which again requires computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`, completing the cycle
note: cycle used when checking that `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test` is well-formed
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information
note: delayed at compiler/rustc_query_system/src/query/job.rs:596:16 - disabled backtrace
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error: internal compiler error[E0391]: cycle detected when computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: ...which requires computing layout of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
= note: ...which requires normalizing `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
note: ...which requires computing type of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires computing type of opaque `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires borrow-checking `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires promoting constants in MIR for `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires checking if `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test` contains FFI-unwind calls...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires building MIR for `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: ...which again requires computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`, completing the cycle
note: cycle used when checking that `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test` is well-formed
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information
note: delayed at compiler/rustc_query_system/src/query/job.rs:596:16 - disabled backtrace
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error: internal compiler error[E0391]: cycle detected when computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: ...which requires computing layout of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
= note: ...which requires normalizing `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
note: ...which requires computing type of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires computing type of opaque `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test::{opaque#0}`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires borrow-checking `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires promoting constants in MIR for `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: ...which requires checking if `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test` contains FFI-unwind calls...
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: ...which again requires computing function signature of `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test`, completing the cycle
note: cycle used when checking that `<impl at /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:3:1: 3:10>::test` is well-formed
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
= note: see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information
note: delayed at compiler/rustc_query_system/src/query/job.rs:596:16 - disabled backtrace
--> /tmp/icemaker_global_tempdir.q2k4BBLCKuN9/rustc_testrunner_tmpdir_reporting.5aASWsrfzxJL/mvce.rs:4:5
|
4 | pub async unsafe extern "C-cmse-nonsecure-entry" fn test(val: &str) {}
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md
note: please make sure that you have updated to the latest nightly
note: rustc 1.84.0-nightly (a0d98ff0e 2024-10-31) running on x86_64-unknown-linux-gnu
note: compiler flags: -Z crate-attr=feature(cmse_nonsecure_entry) --crate-type lib -Z dump-mir-dir=dir
query stack during panic:
end of query stack
```
</p>
</details>
<!--
query stack:
-->
@rustbot label +F-cmse_nonsecure_entry | A-diagnostics,I-ICE,T-compiler,C-bug,F-cmse_nonsecure_entry,S-has-mcve,S-bug-has-test,A-ABI,I-cycle | low | Critical |
2,628,014,032 | pytorch | Graph break due to unsupported builtin torch._C._distributed_c10d.PyCapsule._broadcast_coalesced | ### ๐ Describe the bug
Compiling a whole ddp wrapped model I got this graph break
### Error logs
```python
/opt/conda/lib/python3.11/site-packages/torch/_dynamo/variables/functions.py:743: UserWarning: Graph break due to unsupported builtin torch._C._distributed_c10d.PyCapsule._broadcast_coalesced. This function is either a Python builtin (e.g. _warnings.warn) or a third-party C/C++ Python extension (perhaps created with pybind). If it is a Python builtin, please file an issue on GitHub so the PyTorch team can add support for it and see the next case for a workaround. If it is a third-party C/C++ Python extension, please either wrap it into a PyTorch-understood custom operator (see https://pytorch.org/tutorials/advanced/custom_ops_landing_page.html for more details) or, if it is traceable, use torch.compiler.allow_in_graph.
```
### Minified repro
_No response_
### Versions
nightly
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames | oncall: distributed,triaged,module: ddp,oncall: pt2,module: dynamo,module: graph breaks,pt2d-triage-nov2024 | low | Critical |
2,628,063,246 | godot | Debugger Evaluator format issue on division | ### Tested versions
4.4.dev (since it was added https://github.com/godotengine/godot/pull/97647)
### System information
Windows 10.0.22631 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2070 (NVIDIA; 32.0.15.6603) - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 threads)
### Issue description
When using a forward slash `/` to divide in the REPL expression evaluator, a group header is created holding and separates the operands:
This can be nested as well with multiple `/`.
Also right clicking on a previously evaluated expression to copy it does not work as expected.
Copying `property path` (though it isn't a property) copies `Evaluated/` before the actual expression.
Copying the `value` does not work.
### Steps to reproduce
1. Open the Debugger Evaluator and break on something
2. Enter an expression with `/` to divide some numbers or variables, like `10/2`
### Minimal reproduction project (MRP)
N/A | bug,topic:editor | low | Critical |
2,628,072,200 | pytorch | registering op through function does not work | ### ๐ Describe the bug
a very strange bug:
```python
import torch
from torch.library import Library
def silly_attention(q: torch.Tensor, k: torch.Tensor, v: torch.Tensor,
out: torch.Tensor) -> None:
out.copy_(q)
out += k
out += v
def silly_attention_fake(q: torch.Tensor, k: torch.Tensor, v: torch.Tensor,
out: torch.Tensor) -> None:
return
def direct_register_custom_op(
library_name: str,
op_name: str,
op_func,
mutates_args,
fake_impl = None,
):
schema_str = torch.library.infer_schema(op_func, mutates_args=mutates_args)
my_lib = Library(library_name, "FRAGMENT")
my_lib.define(op_name + schema_str)
my_lib.impl(op_name, op_func, "CUDA")
if fake_impl is not None:
my_lib._register_fake(op_name, fake_impl)
# does not work
direct_register_custom_op(
"silly",
"attention",
silly_attention,
["out"],
silly_attention_fake,
)
# it works
from torch.library import Library
my_lib = Library("silly", "FRAGMENT")
my_lib.define("attention(Tensor q, Tensor k, Tensor v, Tensor(a3!) out) -> ()")
my_lib.impl("attention", silly_attention, "CUDA")
my_lib._register_fake("attention", silly_attention_fake)
print(torch.ops.silly.attention)
```
If I directly run the registration code, it works.
If I call it through a function, it does not work. The op cannot be found.
cc @ezyang @chauhang @penguinwu @zou3519 @bdhirsh @yf225
### Versions
2.5.0+cu124 | triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher | low | Critical |
2,628,073,575 | tensorflow | `tf.math.floormod` not throwing `Integer division by zero` error on GPU for tensor of int64 dtype | ### Issue type
Bug
### Have you reproduced the bug with TensorFlow Nightly?
No
### Source
source
### TensorFlow version
2.18
### Custom code
Yes
### OS platform and distribution
Linux Ubuntu 20.04
### Mobile device
_No response_
### Python version
3.10
### Bazel version
_No response_
### GCC/compiler version
_No response_
### CUDA/cuDNN version
12.3
### GPU model and memory
_No response_
### Current behavior?
Running `tf.math.floormod` with a tensor containing zeroes in the denominator tensor on GPU does not throw a division by zero error when the tensor has a dtype of `int64`.
[colab](https://colab.research.google.com/drive/1e053_hcmu0sHQcMPop-_WZR6ya1bw6dy?usp=sharing)
### Standalone code to reproduce the issue
```shell
import tensorflow as tf
A = tf.constant([[2,2],[2,2]], dtype=tf.int64)
B = tf.constant([[0,0],[0,0]], dtype=tf.int64)
with tf.device("/gpu:0"):
output_gpu = tf.math.floormod(A, B) # No error
print(f"\nGPU: {output_gpu}\n") # GPU: [[2 2] [2 2]]
with tf.device("/cpu:0"):
output_cpu = tf.math.floormod(A, B)
# InvalidArgumentError: Integer division by zero
```
### Relevant log output
```shell
GPU: [[2 2]
[2 2]]
---------------------------------------------------------------------------
InvalidArgumentError Traceback (most recent call last)
<ipython-input-2-ba17e88e7095> in <cell line: 9>()
8
9 with tf.device("/cpu:0"):
---> 10 output_cpu = tf.math.floormod(A, B)
11 # InvalidArgumentError: Integer division by zero
2 frames
/usr/local/lib/python3.10/dist-packages/tensorflow/python/framework/ops.py in raise_from_not_ok_status(e, name)
5981 def raise_from_not_ok_status(e, name) -> NoReturn:
5982 e.message += (" name: " + str(name if name is not None else ""))
-> 5983 raise core._status_to_exception(e) from None # pylint: disable=protected-access
5984
5985
InvalidArgumentError: {{function_node __wrapped__FloorMod_device_/job:localhost/replica:0/task:0/device:CPU:0}} Integer division by zero [Op:FloorMod] name:
```
| stat:awaiting tensorflower,type:bug,comp:ops,TF 2.18 | medium | Critical |
2,628,131,004 | rust | Inlining `-Cinstrument-coverage` code into a uninstrumented crate causes problems | `-Cinstrument-coverage` is a per-crate setting, which makes it possible for instrumented and uninstrumented crates to be mixed during compilation.
This must be supported to some extent, because the standard libraries are built without coverage instrumentation, and instrumenting them would be unwanted in most cases. And we would also like to support instrumenting a project without instrumenting its dependencies, though cargo currently doesn't have a good way to actually set different rustflags for dependencies. Fortunately, inlining uninstrumented code into an instrumented crate mostly works, though in some cases it might end up being unexpectedly instrumented.
The more difficult case is when instrumented code gets inlined into an uninstrumented crate. This is an unusual configuration, but it can occur in practice, e.g. when building doctests as in https://github.com/rust-lang/rust/pull/132395#issuecomment-2449638516. When this happens, two problems can arise:
- Inlined MIR might contain `StatementKind::Coverage` statements, despite the current crate being built without coverage instrumentation. When codegen sees coverage statements, it cannot assume that coverage instrumentation is enabled.
- If the inlined code isn't instrumented, then executing it won't increase coverage counts, despite its original crate having been built with instrumentation.
---
For now, the workaround is to quietly discard any coverage statements that make their way into an uninstrumented crate. This avoids the ICE seen in #132395, but doesn't solve the problem of that code not being instrumented as a result.
| T-compiler,A-code-coverage | low | Minor |
2,628,131,827 | flutter | [Linux] Make FlView an interface | ### Use case
This would allow for some compatibility with existing plugins inside of a custom embedder but on Linux. If a plugin wishes to have access to the GTK side of things, they should check via `GTK_IS_WIDGET(view)`.
### Proposal
1. Make `FlView` an interface
2. Move the existing `FlView` to be a derivative of the interface and call it `FlViewWidget` or something similar.
Implementation can be found here: https://github.com/RossComputerGuy/flutter-engine/commit/32cb2d43cae804846692ace0c17cbceee6c5669b | engine,platform-linux,c: proposal,P3,team-linux,triaged-linux | low | Minor |
2,628,187,396 | pytorch | [Torch TO ONNX BUG] The right shift operation in torch is mapped as a division operation when converted to ONNX. | ### ๐ Describe the bug
The right shift operation in torch is mapped as a "DIV" operation instead of a "SHR" operation when converted to ONNX. This causes some problems when the negative number shifts to the right. For example, shifting -3527 right by 8 bits is not the same as dividing it by 256, especially if the result is truncated.
### Versions
python==3.10.13
torch==2.1.0
onnx==1.16.2 | module: onnx,triaged,onnx-needs-info | low | Critical |
2,628,199,963 | godot | Switching from the Default Keyboard to Num Keyboard Drops Keyboard altogether | ### Tested versions
- Reproducible in Godot Stable v4.2.1
### System information
Windows 11 - Godot 4.2.1 (Developed an app for Android 14)
### Issue description
When switching focus from a textbox using the number keyboard to the default keyboard, the keyboard will drop entirely. The default keyboard should stay up when being switched to.
### Steps to reproduce
Create 2 textboxes
Give one a Number Keyboard (1)
Give two a Default Keyboard (2)
Use a signal like _on_text_changed, or _on_text_submitted
On Android make it so when you submit a value on a number keyboard (1), the default keyboard grabs focus (using grab_focus()) (2)
The keyboard will drop out on Android
### Minimal reproduction project (MRP)
N/A | bug,platform:android,needs testing,topic:input | low | Minor |
2,628,205,015 | vscode | Add title bar context menu entry in full screen to toggle menu bar on windows and linux | <!-- โ ๏ธโ ๏ธ Do Not Delete This! feature_request_template โ ๏ธโ ๏ธ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Describe the feature you'd like. -->
Do not hide the Menu Bar (that includes File, Edit, etc.) when entering fullscreen on Windows. It makes the fullscreen mode quite less usable. I really do like using it through!
| feature-request,linux,windows,titlebar,menus | low | Major |
2,628,226,928 | transformers | Add more configurations to the class LlavaOnevisionConfig. | ### Feature request
I would like to add more flags to configuration class `LlavaOnevisionConfig`, including `spatial_pool_mode`, `newline_position `
### Motivation
[LlavaOnevisionModel](https://huggingface.co/llava-hf/llava-onevision-qwen2-7b-ov-hf) uses the fixed value of `spatial_pool_mode="bilinear"` and `newline_position="one_token"`, so the defined class [LlavaOnevisionConfig](https://github.com/huggingface/transformers/blob/main/src/transformers/models/llava_onevision/configuration_llava_onevision.py#L27C7-L27C27) has omitted the corresponding configurations.
Many of models are trained with the LLaVA-Onevision model using the different flags mentioned above. Incorporating these flags into the configuration file would be highly helpful for developers.
### Your contribution
I can submit a PR with the modifications if you agree with the incorporation of this change. | Feature request | low | Minor |
2,628,231,785 | rust | Array and Vec's Clone specialization is maybe unsound with conditionally Copy types. | Currently, [the `Clone` impl for `[T; N]`](https://github.com/rust-lang/rust/blob/24254efb432739965c50c43c86b2eabbb947a31c/library/core/src/array/mod.rs#L426-L455) uses specialization. If `T` implements `Copy`, then cloning a `[T; N]` will do a memcpy (ignoring `T`'s `Clone` impl). If `T` doesn't implement `Copy`, then it will iterate and call `T`'s `Clone` impl.
However, specialization doesn't look at lifetimes. Therefore, even if `T` implements `Copy` for only some lifetimes, cloning a `[T; N]` will do a memcopy. This is incorrect in the case where `T` actually doesn't implement `Copy`. For example:
```rust
struct Weird<'a>(&'a i32);
impl Clone for Weird<'_> {
fn clone(&self) -> Self {
println!("clone() called");
Weird(self.0)
}
}
impl Copy for Weird<'static> {}
fn main() {
let local = 1;
let _ = [Weird(&local)].clone();
}
```
In the above code, `Weird` only implements `Copy` when its lifetime is `'static`. Therefore, I think that cloning a `[Weird<'a>; 1]` should call the `clone()` method. However, running the above code in either stable (1.82.0) or nightly (`1.84.0-nightly (2024-10-30 759e07f063fb8e6306ff)`) rust doesn't print anything. I believe that this is incorrect.
I am unsure whether or not this can cause UB in purely safe code, (hence the "maybe" in the issue title). But maybe someone else could figure out how to do that?
However, I have written [this code](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=dd3a22edf11e2d48fe48497ba2428eab), which uses unsafe code to implement a `WeirdCow` type whose public API I believe is sound on its own, but can be used in combination with array's Clone specialization to cause use-after-free. Either this `WeirdCow` type is unsound, or the array's Clone implementation is unsound, and I can't figure out which.
@rustbot label +I-unsound | P-medium,T-compiler,I-unsound,A-specialization,C-bug,T-libs,E-needs-investigation | medium | Critical |
2,628,233,496 | rust | rustdoc: Consider adding CCI for the HIR expressions of public constants | When a constant is inlined into another crate, we are forced to always show the evaluated/folded version of the constant. This is because we don't have access to the original HIR in the metadata.
This could be a situation where we can use (https://github.com/rust-lang/rfcs/pull/3662) to store the original expression for public constants (that could potentially be inlined by other crates) so that we don't have the cross-crate issue. Might be applicable to other cross-crate inconsistencies too (though hopefully the type alias one will be resolved by lazy_type_alias).
_Adapted from a post by @camelid in https://github.com/rust-lang/rust/issues/131975#issuecomment-2451225947_
| T-rustdoc,C-enhancement | low | Minor |
2,628,235,165 | PowerToys | [Advanced Paste] Remove clipboard history from main UI if feature turned off | ### Description of the new feature / enhancement
Remove the clipboard history function from Advanced Paste.
### Scenario when this would be used?
Windows has built in clipboard history (win + v) , itโs redundant to reimplement this feature and put it in the pop up.
### Supporting information
_No response_ | Help Wanted,Cost-Small,Product-Advanced Paste | low | Minor |
2,628,237,130 | flutter | [Web] Web app inside WebView is not responding after halfway swiping back gesture on iOS | ### Steps to reproduce
1. Create a web application with three pages
2. Create a native application and use the web_view plug-in to open the web application
3. Enter the web page, slide sideways to return, and then cancel the return
### Expected results
The page is normal
### Actual results
ANR
### Code sample
<details open><summary>Code sample</summary>
```dart
final GoRouter _router = GoRouter(
initialLocation: '/',
routes: <RouteBase>[
GoRoute(
path: '/',
builder: (BuildContext context, GoRouterState state) {
return const MyHomePage();
},
),
GoRoute(
path: 'list',
builder: (BuildContext context, GoRouterState state) {
return const ListPage();
},
),
GoRoute(
path: 'detail',
builder: (BuildContext context, GoRouterState state) {
return const ListPage();
},
),
],
);
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({super.key});
@override
Widget build(BuildContext context) {
return MaterialApp.router(
routerConfig: _router,
);
}
}
class MyHomePage extends StatefulWidget {
const MyHomePage({super.key});
@override
State<MyHomePage> createState() => _MyHomePageState();
}
class _MyHomePageState extends State<MyHomePage> {
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: AppBar(
backgroundColor: Theme.of(context).colorScheme.inversePrimary,
title: Text('Flutter Web Home Page'),
),
body: Center(
child: Column(
mainAxisAlignment: MainAxisAlignment.center,
children: <Widget>[
TextButton(onPressed: (){
Navigator.of(context).push(MaterialPageRoute(builder: (c)=> const ListPage()));
}, child: Text('open web')),
],
),
),
);
}
}
```
</details>
### Screenshots or Video
<details open>
<summary>Screenshots / Video demonstration</summary>
https://github.com/user-attachments/assets/0da16172-0aeb-4cdc-8ae6-088190d99a56
</details>
### Logs
_No response_
### Flutter Doctor output
<details open><summary>Doctor output</summary>
```console
Doctor summary (to see all details, run flutter doctor -v):
[โ] Flutter (Channel stable, 3.24.3, on macOS 14.0 23A344 darwin-arm64 (Rosetta), locale zh-Hans-CN)
[โ] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[โ] Xcode - develop for iOS and macOS (Xcode 15.3)
[โ] Chrome - develop for the web
[โ] Android Studio (version 2023.2)
[โ] VS Code (version 1.94.2)
[โ] Connected device (5 available)
[โ] Network resources
โข No issues found!
```
```console
webview_flutter: 4.1.0
```
</details>
| c: crash,f: routes,a: platform-views,p: webview,platform-web,package,has reproducible steps,P2,team-web,triaged-web,found in release: 3.24,found in release: 3.27 | low | Major |
2,628,315,360 | yt-dlp | [Radiko] Cannot identify radio program to download! - support for premium timefree 30? | ### 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
Japan
### Provide a description that is worded well enough to be understood
i am trying to download the radio program at <https://radiko.jp/#!/ts/BAYFM78/20241024020000>, yt-dlp prints an error saying it cannot identify radio program to download and told me to file a bug here.
### 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', 'https://radiko.jp/#!/ts/BAYFM78/20241024020000']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version nightly@2024.10.31.232951 from yt-dlp/yt-dlp-nightly-builds [a6783a3b9] (pip)
[debug] Python 3.13.0 (CPython arm64 64bit) - macOS-14.4.1-arm64-arm-64bit-Mach-O (OpenSSL 3.4.0 22 Oct 2024)
[debug] exe versions: ffmpeg 7.1 (setts), ffprobe 7.1
[debug] Optional libraries: Cryptodome-3.21.0, brotli-1.1.0, certifi-2024.08.30, mutagen-1.47.0, requests-2.32.3, sqlite3-3.47.0, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version: nightly@2024.10.31.232951 from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date (nightly@2024.10.31.232951 from yt-dlp/yt-dlp-nightly-builds)
[Radiko] Extracting URL: https://radiko.jp/#!/ts/BAYFM78/20241024020000
[Radiko] BAYFM78-20241024020000: Downloading radio program for BAYFM78 station
ERROR: [Radiko] Cannot identify radio program to download!; 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 "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/extractor/common.py", line 742, in extract
ie_result = self._real_extract(url)
File "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/extractor/radiko.py", line 190, in _real_extract
prog, station_program, ft, radio_begin, radio_end = self._find_program(video_id, station, vid_int)
~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/lib/python3.13/site-packages/yt_dlp/extractor/radiko.py", line 116, in _find_program
raise ExtractorError('Cannot identify radio program to download!')
```
| account-needed,geo-blocked,site-bug,patch-available,can-share-account | low | Critical |
2,628,356,742 | svelte | Svelte 5: Unable to monitor state/derived without running the block | ### Describe the bug
On page load, we pass the initial data into the component. Because of this, we don't need to fetch data again when the component is mounted, but if the query params change, we need to trigger a section of code to refetch results.
In Svelte 4, we had something like this (trimmed and simplified but it should be clear): (`$applicationContextStore.params` is just a store that initialized with params from the current URL)
```svelte
<script lang="ts">
export let users: User[]
let params = $applicationContextStore.params
$: fetchData({
url: '/users',
params, // <- updates to this will trigger this call
onSuccess: (newUsers: User[]) => {
users = newUsers
})
})
</script>
<a href="#" on:click={() => {
params = { ...params, sort: 'asc' }
}}>Sort Asc</a>
<a href="#" on:click={() => {
params = { ...params, sort: 'desc' }
}}>Sort Desc</a>
<table>....</table>
```
This worked well. Users were passed in when the component was rendered for the first time. Then if the sorting links were clicked, the params were updated, triggering the fetchData block.
With Svelte 5, there does not appear to be any way to monitor a block of code for state changes without it also first running.
```svelte
<script lang="ts">
interface Props {
users: User[]
}
let { users }: Props = $props()
let params = $state($applicationContextStore.params)
$effect(() => {
fetchData({
url: '/users',
params,
onSuccess: (newUsers: User[]) => {
users = newUsers
})
})
})
</script>
<a href="#" onclick={() => {
params = { ...params, sort: 'asc' }
}}>Sort Asc</a>
<a href="#" onclick={() => {
params = { ...params, sort: 'desc' }
}}>Sort Desc</a>
<table>....</table>
```
The above doesn't work as intended. $derived, $derived.by, $effect, $effect.pre, and onMount all run the code when the component is mounted, which is not what we want, because we are already passing in the initial data. This ends up doubling requests which returns exactly the same data.
What we need is a $track function or something, that doesn't run when component is mounted, but does run when any state vairables in it are run.
On a different note, the migrator is converting it to use legacy/run, which behind the scenes looks like $effect.pre, so the migrator is recommending a change that breaks functionality.
Any ideas/advice?
### Reproduction
See above
### Logs
_No response_
### System Info
```shell
System:
OS: macOS 15.1
CPU: (12) arm64 Apple M3 Pro
Memory: 91.22 MB / 18.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.15.1 - ~/.asdf/installs/nodejs/20.15.1/bin/node
Yarn: 4.3.1 - ~/.asdf/installs/nodejs/20.15.1/bin/yarn
npm: 10.8.2 - ~/.asdf/plugins/nodejs/shims/npm
bun: 1.1.0 - ~/.bun/bin/bun
Browsers:
Chrome: 130.0.6723.92
Safari: 18.1
npmPackages:
svelte: ^5.1.9 => 5.1.9
```
### Severity
blocking an upgrade | awaiting submitter | low | Critical |
2,628,358,574 | kubernetes | SchedulingWhileGated test in scheduler-perf failed but was able to produce results | ### What happened?
While trying to reproduce the Scheduler_perf results from #127180 , I encountered an issue where the SchedulingWhileGated test failed but still produced results.
Iโm running the following code on an Ubuntu 22.04 Linux VM with 4 CPUs, 8GB memory, and a 100GB hard disk, under various configurations.
`make test-integration WHAT=./test/integration/scheduler_perf ETCD_LOGLEVEL=warn KUBE_TEST_VMODULE="''" KUBE_TEST_ARGS="-run=^$$ -benchtime=1ns -bench=BenchmarkPerfScheduling/SchedulingWhileGated/1Node_10000GatedPods"`
I obtained the following results, which show the same trend the PR mentioned, but my tests actually failed. Could you let me know if this outcome is normal at your convenience please?
> QHint enabled master branch vs. this branch : 117 pods/sโ 103pods/s performance decline
> QHint disabled master branch vs. this branch : 92 pods/s โ 123 pods/s performance improve
message generated by executing the code above
```
make[1]: *** [Makefile:192: test] Error 1
make[1]: Leaving directory '/home/xie/go/src/k8s.io/kubernetes'
!!! [1018 05:41:12] Call tree:
!!! [1018 05:41:12] 1: hack/make-rules/test-integration.sh:108 runTests(...)
+++ [1018 05:41:12] Cleaning up etcd
+++ [1018 05:41:13] Integration test cleanup complete
make: *** [Makefile:215: test-integration] Error 1
```
### What did you expect to happen?
Iโd like to know if this is normal behavior. If itโs not, it should be possible to obtain the correct results without the test failing.
### How can we reproduce it (as minimally and precisely as possible)?
Run the following code under the following four configurations.
`make test-integration WHAT=./test/integration/scheduler_perf ETCD_LOGLEVEL=warn KUBE_TEST_VMODULE="''" KUBE_TEST_ARGS="-run=^$$ -benchtime=1ns -bench=BenchmarkPerfScheduling/SchedulingWhileGated/1Node_10000GatedPods"`
I conducted four test cases, and I think each test can generate similar results.
1. Master branch, SchedulerQueueingHints Disable
2. Master branch, SchedulerQueueingHints Enable
3. [#127180](https://github.com/kubernetes/kubernetes/pull/127180) PR branch, SchedulerQueueingHints Disable
4. [#127180](https://github.com/kubernetes/kubernetes/pull/127180) PR branch, SchedulerQueueingHints Enable
### Anything else we need to know?
/sig scheduling
### Kubernetes version
<details>
```console
$ kubectl version
# paste output here
```
</details>
### Cloud provider
<details>
</details>
### OS version
<details>
```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```
</details>
### Install tools
<details>
</details>
### Container runtime (CRI) and version (if applicable)
<details>
</details>
### Related plugins (CNI, CSI, ...) and versions (if applicable)
<details>
</details>
| kind/bug,sig/scheduling,needs-triage | low | Critical |
2,628,396,667 | godot | Using CapsuleShape2D in CollisionShape2D cancels out the collision area when baking NavigationRegion2D | ### Tested versions
Reproducible - v4.3.stable.official [77dcf97d8]
### System information
Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; 32.0.15.6094) - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)
### Issue description
When baking NavigationPolygon, if a CapsuleShape2D is either completely or partially overlapped with a collision area, the overlapping part of the CapsuleShape2D will cancel out the collision area and become part of the navigation polygon. The issue is only happening with CapsuleShape2D, not other shapes.
### Steps to reproduce
1. Create a NavigationRegion2D
2. Under the NavigationRegion2D, create a StaticBody2D with a child CollisionPolygon2D, draw the collision polygon
3. Under the NavigationRegion2D, create another StaticBody2D with a child CollisionShape2D, use CapsuleShape2D as its shape
4. Make the 2 StaticBody2D overlaps
5. Bake NavigationPolygon on NavigationRegion2D
6. Observe that the overlapping part is recognized as a navigation polygon instead of a collision area
### Minimal reproduction project (MRP)
[test-project.zip](https://github.com/user-attachments/files/17596571/test-project.zip)
| bug,topic:navigation,topic:2d | low | Minor |
2,628,396,870 | deno | Resize event on stdout not invoked in TTY on macOS | Version: Deno 2.0.4
macOS: 14.2.1
# Repro steps
1. `deno` in Alacritty
2. `process.stdout.on('resize', () => { console.log(`${process.stdout.columns}x${process.stdout.rows}`) })`
3. Resize Alacritty window
# Expected
Printed console output with the process columns and rows.
# Actual
Nothing happens.
# Additionally
If you run the same `process.stdout.on('resize', () => { console.log(`${process.stdout.columns}x${process.stdout.rows}`) })` in `node` (I'm using v20), then you'll see the expected results.
Also, I've tested in Warp and Terminal TTY apps as well and got the same bug. | bug,node compat | low | Critical |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.