sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tensorflow
Issue: Aborted (core dumped) in tf.io.TFRecordWriter
Labels: stat:awaiting tensorflower,type:bug,comp:ops,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I have tested on tensorflow-nightly.
There are five bugs related to `tf.io.TFRecordWriter`. 

BUG 1: `compression_method=3` -> Aborted (core dumped)
Code:
```
import tensorflow as tf
input_data = b'input_data_example'
options = tf.io.TFRecordOptions(compression_type='ZLIB', compression_method=3)
with tf.io.TFRecordWriter('output.tfrecord', options=options) as writer:
    writer.write(input_data)
```

BUG 2: `window_bits=-8` -> Aborted (core dumped)
CODE:
```
import tensorflow as tf
input_data = b'input_data_example'

options = tf.io.TFRecordOptions(
    compression_type='ZLIB',
    window_bits=-8  # negative window_bits
)

with tf.io.TFRecordWriter('output.tfrecord', options=options) as writer:
    writer.write(input_data)
```

BUG3: `compression_level=-9` -> Aborted (core dumped)
CODE:
```
import tensorflow as tf
input_data = b'input_data_example'
options = tf.io.TFRecordOptions(compression_type='ZLIB', compression_level=-9)
with tf.io.TFRecordWriter('output.tfrecord', options=options) as writer:
    writer.write(input_data)
```

BUG 4: `mem_level=-10` -> Aborted (core dumped)
CODE:
```
import tensorflow as tf
input_data = b'input_data_example'
options = tf.io.TFRecordOptions(compression_type='ZLIB', mem_level=-10)
with tf.io.TFRecordWriter('output.tfrecord', options=options) as writer:
    writer.write(input_data)
```

BUG 5: `compression_strategy=-2` -> Aborted (core dumped)
```
import tensorflow as tf

input_data = b'input_data_example'
options = tf.io.TFRecordOptions(compression_type='ZLIB', compression_strategy=-2)
with tf.io.TFRecordWriter('output.tfrecord', options=options) as writer:
    writer.write(input_data)
```

### Standalone code to reproduce the issue

```shell
The reproducible test cases are provided above.
```


### Relevant log output

```shell
All the above codes output `Aborted (core dumped)`.
```
Repository: excalidraw
Issue: Exporting Png Problem
Labels: UX/UI,filesystem

I hope the Excalidraw team is doing well It's not a big problem but it's worth considering
When exporting the diagram as a PNG, a pop-up window appears at the bottom where you can enter the file name. By default, it fills in some dates, which isn't an issue. However, if I change the file name, **it doesn't save as a PNG format** instead, it saves as a **file** format But if I don't modify the file name it saves as a PNG format
Please look into a feature where, when typing something on the board and then moving to another tab the text pointer doesn't maintain its position Sometimes this can be uncomfortable That's all I've experienced.
![Untitled design (1)](https://github.com/excalidraw/excalidraw/assets/93287603/e5563947-0f0c-4ead-80d6-df2bc8d80c60)
Repository: next.js
Issue: "Intercepting routes" feature not working in production
Labels: bug

### Link to the code that reproduces this issue

https://github.com/478732/temp

### To Reproduce

1. Visit [https://resplendent-halva-bdccd9.netlify.app/](https://resplendent-halva-bdccd9.netlify.app/)
2. Click on the text, "Image 1"
3. You will be taken to another page

### Current vs. Expected behavior

**Current behavior**
1. On [https://resplendent-halva-bdccd9.netlify.app/](https://resplendent-halva-bdccd9.netlify.app/) 
2. When you click on the text, "Image 1"
3. You will be taken to another page

**Expected behavior**
1. On [https://resplendent-halva-bdccd9.netlify.app/](https://resplendent-halva-bdccd9.netlify.app/) 
2. When you click on the text, "Image 1"
3. Black box should appear


**Description**

I am trying to make a feature where 

when you click on a specific element, a black box appears.

To make this feature, I am using the "intercepting routes" feature.

It works fine locally, but does not work in production.

Locally, on localhost:3000, when I click on the text "Image 1", a black box appears.

However, in production at https://resplendent-halva-bdccd9.netlify.app/ 

when I click on the text, "Image 1", I am taken to another page (unexpected)

A black box should be appearing.

My code is similar to vercel's nextgram app found at https://github.com/vercel/nextgram


**Video showing problem**

https://github.com/vercel/next.js/assets/136137838/8eeed0fe-550a-4a41-bcee-f96f5c4479f3


### Provide environment information

```bash
- MacOS
- NextJS 14.1
- Google Chrome
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

Other (Deployed)

### Additional context

_No response_
Repository: deno
Issue: `deno compile` custom binaries
Labels: perf,cli,suggestion,compile

Ability for users to compile a custom `denort` binary for their projects. 

### Features to include in the binary. 

Our Node.js compatibility layer takes up 12MB. A user not using this feature should be able to turn it off. 

Initial pass should support "ext/node", this optimization can expand to "ext/webgpu" and "ext/crypto". 

- [ ] #22681 

### ICU modes

The full ICU (default) is 11MB. We should support full-ICU, small-ICU and no-ICU modes.

Initial pass should support no-ICU and full-ICU.

```jsonc
{
  // cargo install deno 
  //  --release 
  //  --bin=denort 
  //  --no-default-features --features='ext-node,small-icu'
  "compile": {
    "features": ["node"],
    "icu": "small",
  }
}
```

```
$ deno compile main.ts
$ du -h ./main
51M ./main
```

### Pros

- Smaller binary and faster startups
- Control over build process, can embed artifacts like Windows app icons.
- Can be used in CI/CD pipelines to produce final release builds.

### Cons

- Depends on cargo and rustc.
- Building deno takes time.
Repository: PowerToys
Issue: Maintain Previously Set Volume Level for Powertoys Peek after Every Reboot
Labels: Idea-Enhancement,Help Wanted,Cost-Small,Product-Peek

### Description of the new feature / enhancement

Each time I boot up my device, powertoys peek's volume keeps resetting to the highest level, meaning I have to preview an image first to get peek to show up in the volume mixer, then take it down to 20% in order to avoid the shocking loudness that comes with previewing a video file first after every reboot.

It would be nice to have peek maintain the previously set volume level even after rebooting.

### Scenario when this would be used?

Manually setting powertoys peek volume level.

### Supporting information

_No response_
Repository: ollama
Issue: Automatic sub-language constraint sections
Labels: feature request

It would be useful if ollama supported automatic, text based, plugin driven grammar sections.

Every time triple quote section is used in text it enters that language mode constraints, for example:

1. "```json" enters json bnf
2. "```json:Foo" enters json bnf + json schema for Foo object
3. "```python" enters python bnf
4. "```quote:documentRef" enters trie based constraints for quotes
5. "```whatever:whatever?" enters whatever
6. final "\n```" pops the mode

Available grammars could be:

1. server/model defined – avoiding network overhead
2. client defined – flexible under client side control (probably much better)

The api for plugin/handler could be:

1. character based – given text from beginning of opening "```foo" input it returns allowed characters, or
2. native model token based – given same input returns list of allowed tokens, or
3. generic suffix text – given same input returns list of allowed, arbitrarily sized completions (so plugin can adopt, ie. for wide fanout it can return list of short strings, ie. single characters, for less fanout it can produce longer output with possible single output optimization where llm doesn't need to be consulted <<if there is single completion allowed, no need to run it though the model at all>>), or
4. optimized trie output – given same input returns 3. in compressed, trie format.

Plugin can internally use whatever strategy it wants to conform to autocompletion interface (BNF, trie based index for document quotes or something else).

Heading can be uri based, ie. "```trie://mydb/docs?id=123" so plugins can register themselves as handlers for specific modes.
Repository: next.js
Issue: Intermittent Text Content Mismatch Error in Chrome on M1 Mac
Labels: bug

### Link to the code that reproduces this issue

https://github.com/RandallRock123/my-app

### To Reproduce

When developing a Next.js application on an M1 MacBook using Chrome (version 122.0.6261.112, arm64), an intermittent error related to text content mismatch is observed. This error occurs roughly 1 out of every 20 page refreshes and seems to be specific to the use of a div element wrapping the page content. Switching the wrapper to a main element appears to mitigate the issue (odd!!!). This behavior is not replicated in Firefox or Safari.

Steps to Reproduce:
1.Create a new Next.js application using npx create-next-app@latest with the default setup on an M1 MacBook.
2.Modify the page.tsx file to:
```

export default function Home() {
  return <div>123</div>; // Triggering error intermittently on refresh
}
```
3.Start the application in development mode (next dev).
4.Refresh the application in Chrome (arm64 version) multiple times (around 20 or more attempts may be needed).
Observe the intermittent warning/error: Warning: Text content did not match. Server: "" Client: "123"

### Current vs. Expected behavior

Expected: Refreshing the browser should not result in a text content mismatch error, regardless of the HTML element used as a wrapper.

Actual: When wrapping the content in a <div>, a text content mismatch error occurs intermittently upon refreshing the page in Chrome on M1 Mac. The error does not occur when using a <main> wrapper or when testing in Firefox or Safari.

### Provide environment information

```bash
Operating System: macOS (M1)
Node.js version: 18.19.0
Chrome version 122.0.6261.112, arm64
Relevant Packages:
    "react": "^18",
    "react-dom": "^18",
    "next": "14.1.3"
```


### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: transformers
Issue: Can we change mistral attention bias=False to bias=config.attention_bias ？
Labels: Feature request

just like llama attention ![image](https://github.com/huggingface/transformers/assets/76865636/f483aa4c-6c8f-40fd-b942-784cf74774cf)
Repository: pytorch
Issue: DISABLED test_pynode_destruction_deadlock (__main__.TestAutogradWithCompiledAutograd)
Labels: module: autograd,module: rocm,triaged,skipped,oncall: pt2,module: compiled autograd

Platforms: asan

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22inductor%2Ftest_compiled_autograd.py%3A%3ATestAutogradWithCompiledAutograd%3A%3Atest_pynode_destruction_deadlock%22%5D)).

This test starts to become flaky in trunk today (March 8th) but the root cause is unclear yet.

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: go
Issue: net/http: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/2ef5b27af849d9ee014fa6810c25d0fdff961d2c)):

    panic: test timed out after 3m0s
    running tests:
    	TestClientCallsCloseOnlyOnce/h1 (2m58s)
    
    goroutine 16432 gp=0xa0001000087efc0 m=13 mp=0xa00010000064408 [running]:
    panic({0x11002b220?, 0xa00010000726030?})
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/runtime/panic.go:778 +0x1bc fp=0xa00010000240ee0 sp=0xa00010000240e20 pc=0x10004286c
    testing.(*M).startAlarm.func1()
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/testing/testing.go:2366 +0x34c fp=0xa00010000240fc0 sp=0xa00010000240ee0 pc=0x10012527c
    runtime.goexit({})
    ...
    bufio.(*Reader).Peek(0xa0001000159c000, 0x1)
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/bufio/bufio.go:148 +0x80 fp=0xa0001000017ad00 sp=0xa0001000017acc8 pc=0x100127330
    net/http.(*persistConn).readLoop(0xa00010000bc6360)
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/net/http/transport.go:2141 +0x1a0 fp=0xa0001000017af98 sp=0xa0001000017ad00 pc=0x100328d90
    net/http.(*Transport).dialConn.gowrap2()
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/net/http/transport.go:1811 +0x4c fp=0xa0001000017afc0 sp=0xa0001000017af98 pc=0x1003273dc
    runtime.goexit({})
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/runtime/asm_ppc64x.s:1018 +0x4 fp=0xa0001000017afc0 sp=0xa0001000017afc0 pc=0x100084884
    created by net/http.(*Transport).dialConn in goroutine 16518
    	/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/src/net/http/transport.go:1811 +0x14b8


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: rust
Issue: Warning during compiler build: Compiler version doesn't include clang or GCC
Labels: T-bootstrap

Running `./x.py check compiler` shows a warning:
```
warning: rustc_llvm@0.0.0: Compiler version doesn't include clang or GCC: "c++" "--version"
```
I think this must have started pretty recently.

FTR, `c++ --version` shows
```
$ c++ --version
c++ (Debian 13.2.0-13) 13.2.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
Repository: next.js
Issue: Root Layout Re-renders on Route Change in SSG(output: export), Causing Loss of Initial Random Data
Labels: bug

### Link to the code that reproduces this issue

https://github.com/Innei/next-ssg-layout-rerender-repro

### To Reproduce

In a Next.js application utilizing Static Site Generation (SSG), the root layout component re-renders upon navigating to a different route. This behavior leads to the loss of initially set random data within the root layout. A specific example of this issue is when a global color is injected into the root layout for the duration of a page visit; the color should persist across route changes. This functionality works as expected in development mode and in builds not outputted with `export`, but fails under SSG.


1. Clone my repo.
2. Inject random data (e.g., a global color) into the root layout component.
3. Navigate between pages/routes.
4. Observe that the global color (or any random data) resets, indicating a re-render of the root layout.


In dev mode: This is expected behavior. When route is changed, the layout color does not change


https://github.com/vercel/next.js/assets/41265413/b19e80a7-3aa0-48a0-b49e-5f0ae0b13ee3


And build with `export`.

https://github.com/vercel/next.js/assets/41265413/dcbecfdb-ddad-4bcc-a59e-529821f6b794


### Current vs. Expected behavior

The initial random data (e.g., a global color) set in the root layout should persist across route changes, similar to its behavior in development mode and non-SSG builds.


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:31:00 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6020
Binaries:
  Node: 20.8.1
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: 8.15.4
Relevant Packages:
  next: 14.1.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

App Router, Static HTML Export (output: "export")

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: transformers
Issue: Add predict_proba method for Autoformer/Informer
Labels: Feature request

### Feature request

Currently, the autoformer and informer does only provide sampled outputs from a probability distribution for future values. However, it would be nice if there would be the possibility to provide the forecasted distribution to the user.

### Motivation

I am currently trying to develop an adapter in sktime that enables the integration of the time series models from the transformers library (https://github.com/sktime/sktime/issues/5790). Since sktime has a `predict_proba` method, I would like to translate the transformers probability distribution into sktime probability distributions. 

### Your contribution

I think there are at least three solutions:
1. Add a new method, e.g., `predict_distribution`, which is returning the distribution object or its parameters.
2. Add a parameter to the `generate` function that controls if the distribution or its parameters are returned. 
3. Always returns the distributions or it's parameters together with the sampled `sequence` in `generate`.

If you are preferring any of these three solutions, I am happy to implement it :)
Repository: TypeScript
Issue: Regression performance compiling types in version 5.4.2
Labels: Needs More Info

### 🔎 Search Terms

"regression", "5.4.2", "performance"

### 🕗 Version & Regression Information

- This changed between versions 5.3.3 and 5.4.2


### ⏯ Playground Link

_No response_

### 💻 Code

Extended diagnostics in version 5.4.2
```bash
Files:                          4294
Lines of Library:              40640
Lines of Definitions:         180807
Lines of TypeScript:          430513
Lines of JavaScript:               0
Lines of JSON:                     0
Lines of Other:                    0
Identifiers:                  591567
Symbols:                     1232510
Types:                       4677381
Instantiations:            395496734
Memory used:                2330550K
Assignability cache size:    3974893
Identity cache size:           14482
Subtype cache size:            37794
Strict subtype cache size:      9374
I/O Read time:                 0.70s
Parse time:                    0.96s
ResolveModule time:            0.58s
ResolveTypeReference time:     0.01s
ResolveLibrary time:           0.01s
Program time:                  2.51s
Bind time:                     0.62s
Check time:                  367.45s
printTime time:                0.00s
Emit time:                     0.00s
Total time:                  370.58s
```

Extended diagnostics in version 5.3.3
```bash
Files:                         4290
Lines of Library:             40241
Lines of Definitions:        180807
Lines of TypeScript:         430513
Lines of JavaScript:              0
Lines of JSON:                    0
Lines of Other:                   0
Identifiers:                 591320
Symbols:                    1234773
Types:                       699200
Instantiations:             2247099
Memory used:               1308962K
Assignability cache size:    223823
Identity cache size:          14479
Subtype cache size:           28353
Strict subtype cache size:     9128
I/O Read time:                0.73s
Parse time:                   1.11s
ResolveModule time:           0.44s
ResolveTypeReference time:    0.01s
ResolveLibrary time:          0.02s
Program time:                 2.60s
Bind time:                    0.76s
Check time:                  13.75s
printTime time:               0.00s
Emit time:                    0.00s
Total time:                  17.11s
```

### 🙁 Actual behavior

The type validation using `tsc --noEmit` increase more than 20 times using the version `5.4.2` comparing with the version `5.3.3`. 

In the CI is always hitting the heap memory limit:
![image](https://github.com/microsoft/TypeScript/assets/23644327/95c713b0-8938-48ac-bd3d-26861eb6d45b)


### 🙂 Expected behavior

I expected the compilation to be equivalent in both versions, but it was more than 20 times slower.

### Additional information about the issue

_No response_
Repository: ollama
Issue: Mamba State Space Models Integration
Labels: model request

There has been a completed merge of mamba model support over at Ilama.ccp, would it be possible to implement these into Ollama as well?

Merged PR: https://github.com/ggerganov/llama.cpp/pull/5328 

Model examples: https://huggingface.co/collections/Q-bert/mamba-65869481595e25821853d20d
Repository: TypeScript
Issue: JavaScript class property becomes `any` without warning when used in a function that is assigned to itself
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

jsdoc class null any

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `any`


### ⏯ Playground Link

https://www.typescriptlang.org/play?strictNullChecks=true&useDefineForClassFields=true&filetype=js#code/KYDwDg9gTgLgBAYwDYEMDOa4DEITgbwCg4S4B6AKguNLgrgAEwUoUBbAgOwFc2AjYFAD8AXzhsUATwEA5XjVIUyCxBE5oYUbghjQAFBOnA5bAJQEVtGAAsAlmgB0h2bzgBeODyRIA3IUukNvYOaMAwALJSLmx6pn60Iv60oRFRxryxFrRWdo7O6RwekTZOKCB6QXlpJnEqiSqU1Nn0TCzsBBpQtpwA5mKdlkoqMCgA1sBoAMqa3T16neb49bQAZriZRNmBuQ4j41MzvRU7+TXxW+RkF9cAenf3D-cAtC9PnniCUNAANOLVrvY4ChOJI6oREkA

### 💻 Code

```js
export class Foo {
    /**
     * @param {number?} maybeNum
     */
    constructor(maybeNum) {
        this.maybeNum = null;

        this.setMaybeNum();
    }

    setMaybeNum() {
        this.maybeNum = Math.max(this.maybeNum);
    }

    /**
     * @param {string} str
     */
    takesString(str) {}

    foo() {
        this.takesString(this.maybeNum);
        //               ^^^^^^^^^^^^^---- no error, maybeNum is any
    }
}
```


### 🙁 Actual behavior

`this.maybeNum` is `any`

### 🙂 Expected behavior

`this.maybeNum` is `number | null` or (since noImplicitAny is set) an error is emitted warning the user that `this.maybeNum` is `any`.

### Additional information about the issue

It seems like the core issue here is this line:
```js
this.maybeNum = Math.max(this.maybeNum);
```
Repository: next.js
Issue:  Fast Refresh had to perform a full reload.
Labels: bug




### To Reproduce

Every time I make a change i get the following error ; 

![Screenshot 2024-03-09 at 14 47 46](https://github.com/vercel/next.js/assets/66960351/31486f02-7717-46c5-9f52-4dcd083e9430)

I know this is an old issue but sill haven't found any solution to it , that is not updating Nextjs.

warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/basic-features/fast-refresh#how-it-works
Error: Aborted because ./node_modules/@swc/helpers/src/_define_property.mjs is not accepted
Update propagation:


### Current vs. Expected behavior

Making changes on the app will get a full reload instead of hot reload,

### Provide environment information

```bash
OS:  macOS
Browser  any;
Version of Next.js: 
  "next": "^12.2.3",
    "react": "^18.2.0",
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

It wont be an option to update nextjs for me