sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Add HelpingAIForCausalLM to it
Labels: New model

### Model description

HelpingAI is a state-of-the-art large language model specializing in emotionally intelligent conversation. With advanced emotional understanding capabilities, it can engage in empathetic dialogue tailored to the user's emotional state and context.

## Emotional Intelligence Capabilities

HelpingAI-3B-v2.2 exhibits several key traits that enable emotionally resonant responses:

- Emotion recognition and validation
- Empathetic perspective-taking 
- Generating emotionally supportive language
- Contextual emotional attunement
- Using appropriate tone, word choice and emotional expression

Whether comforting someone grieving, celebrating positive news, or addressing complex feelings, HelpingAI-3B-v2.2 can adapt its communication style with emotional nuance.

## Examples of Emotionally Intelligent Responses


"I'm really sorry to hear about your friend's loss. 😔 Losing a parent can be incredibly difficult and traumatic, and it's completely understandable that they are struggling with grief. It's important to show them empathy and support during this tough time. You can start by simply being there for them, listening to them, and offering a shoulder to lean on. 💕 It's also important to acknowledge their feelings and let them know that it's okay to grieve and take as much time as they need to process their emotions. Offering practical help, such as running errands or cooking for them, can also make a big difference. Remember, small gestures of kindness and compassion can go a long way in comforting someone during difficult times."

"Hey there! 🌟 It's a beautiful day today, so you should cook something delicious and enjoy the sunny weather! How about trying out a new recipe and let your creativity flow? Whether it's a classic dish or something experimental, the kitchen is the perfect place to let your imagination run wild. Write me a list of ingredients you have on hand, and I'll help you come up with a wonderful culinary creation! 🍲🌞"

The model tailors its language, tone and emotional content to be contextually appropriate, combining emotional intelligence with factual knowledge and practical suggestions.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

@OEvortex
https://huggingface.co/OEvortex/HelpingAI-3B-v2.2
Repository: rust
Issue: Tracking Issue for `--print=check-cfg`
Labels: C-tracking-issue,F-check-cfg

This is a tracking issue for the MCP 743 "Add --print=check-cfg" (https://github.com/rust-lang/compiler-team/issues/743).
The flag is gated under `-Zunstable-options`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps

- [X] Implement the MCP (https://github.com/rust-lang/rust/pull/124320)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
	- [unstable book - `--print=check-cfg`](https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/print-check-cfg.html)
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

None at this time.

### Implementation history

 - https://github.com/rust-lang/rust/pull/124320
 - https://github.com/rust-lang/rust/pull/125818
Repository: vscode
Issue: Ability to provide a custom combined diff view
Labels: feature-request,custom-editors

<!-- ⚠️⚠️ 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. -->
Note: This is probably heavily related to https://github.com/microsoft/vscode/issues/138525, but I am not entirely sure whether that one covers this particular use case.

I was looking into a creating a visual diff between two files, similar to e.g. this (https://github.com/jnavila/plotkicadsch):
![image](https://github.com/microsoft/vscode/assets/33105866/2844413e-efbb-401f-951b-2586ffdfd0d1)

This would require the ability to replace the entirety of the diff view, not only the individual halves (which is what https://github.com/microsoft/vscode/issues/138525 seems to be about)

Ideally the following features would be supported:
* Access to the two files being diffed (to actually render whatever diff view)
* Some easy way for the user to switch back and forth between the custom view and the default one (while the visual view helps to quickly spot qualitative differences, the textual view gives more precise information)
Repository: transformers
Issue: need better token_type_id processing on transformer GPT2Model 
Labels: Feature request

### Feature request

in the GPT2Model code, I see that the token_type_id value is embeded with the same **wte** of input tokens. so that the two token type id values: 0, 1,  are in collision with input sentence tokens. We need a more nature design here so that we do not have to reproduce vocab_size and sentence token values when trained with the `token_type_ids` inputs.

### Motivation

make it simply the same  vocab size and sentence token inputs for training GPT2Model with  or without `token_type_ids` input.

### Your contribution

maybe another embedding layer can be used for the token_type_id embeddings.
Repository: ui
Issue: [bug]: CLI errors when using relative path as util alias
Labels: bug

### Describe the bug

When using relative path as the alias for util import (I'm using a monorepo, the cn function is under /src on the same level with other components, using absolute/aliased import will cause apps to not be able to resolve `cn`, so I tried to use `import { cn } from "."`, which works fine for using components) ,but the CLI outputs error:
```
[
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "resolvedPaths",
      "utils"
    ],
    "message": "Required"
  }
]
```
Seems to be caused by the CLI not be able to resolve the path from "." with tsconfig

Possible fix: adding a option in CLI to opt out of trying to resolve the path

### Affected component/components

CLI

### How to reproduce

Edit the component.json > aliases > utils to "."
Try shadcn-ui add

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
on latest shadcn-ui CLI version
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Progress isn't cleared when participant errors
Labels: bug,chat

* have a chat participant
* let it print a progress message
* right after that let it throw an error
* 🐛 the progress message stays (even across reloads)


```ts
let handler: vscode.ChatRequestHandler = async (request, ctx, stream, token): Promise<vscode.ChatResult> => {

		console.log(request.references)

		let reply = request.prompt;
		const cmd = request.command

		if (request.prompt === 'err') {
			stream.progress('Erroring...')
			throw new Error('Some error')
		}
};

```
<img width="415" alt="image" src="https://github.com/microsoft/vscode/assets/1794099/5e7910b6-c769-4883-a46e-99511c6aa23f">
Repository: rust
Issue: Tracking Issue for compiletest documentation
Labels: A-testsuite,T-compiler,E-help-wanted,T-bootstrap,A-docs,C-tracking-issue,A-compiletest

### Context

`compiletest` is the main test harness of rustc and other tools inside this repository, but there is a *significant* lack of documentation for it. We should write some documentation for compiletest. There are [some documentation in rustc-dev-guide](https://rustc-dev-guide.rust-lang.org/tests/compiletest.html), but compiletest is *a lot* more complex than that.

### Areas lacking documentation

- [ ] High-level architecture and overview
- [ ] Interaction between bootstrap <-> compiletest <-> tests
- [ ] compiletest-as-a-binary: CLI interface options and docs
- [ ] Filtering tests
- [ ] How are test modes and test suites created, registered, built and run
    - When can tests be ignored? cached test results and their invalidation: dependency stamps
    - Some test mode / test suite tests can be run in parallel / concurrently:
        - Concurrency assumptions: what if the test modifies external state?
- [ ] Test mode and test suite specific behavior, assumptions and quirks
    - UI tests: auxiliary crates and bins, `compile-flags`, compare modes, assumptions and conventions on stdout/stderr output, blessing
    - run-make and run-make-fulldeps tests: how the whole build pipeline is setup, concepts, how tests are built and executed, provided env vars, assumed dependencies 
    - codegen tests: filecheck, `revisions` magic behavior
    - coverage tests: how to bless?
    - `ui-fulldeps` have some *non-trivial* behavior: e.g. https://github.com/rust-lang/rust/pull/126073#discussion_r1629843686
- [ ] Error handling strategy/design and diagnostics
- [ ] Interaction with CI
- [ ] Test directive collection, parsing and validation
    - Which directives can be used in which test suites?
    - What do the directives even mean/do?
- [ ] Test output normalization special syntax
    - e.g. `const CWD: &str = "{{cwd}}";`
- [ ] Setting `current_dir` when running tests

### Related issues

- https://github.com/rust-lang/rust/issues/125585
- https://github.com/rust-lang/rust/issues/125587
- https://github.com/rust-lang/rust/issues/126092

### Unresolved questions

- Where do we keep compiletest docs?
    - Maybe alongside the source? Maybe a mdBook? rustc-dev-guide?
    - Ideally we would like this easy to read and reference and improve.
- How to we keep compiletest documentation update-to-date?
    - Periodic triage?

### Documentation improvement history

TODO
Repository: react
Issue: [Compiler Bug]: Health check --src option only works with one file (so a glob needs to be quoted)
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [X] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

Any project with several component files (e.g. https://github.com/guillaumebrunerie/LD55)

### Repro steps

Running the compiler health check with a normal glob only checks the first file it finds:
```
> npx react-compiler-healthcheck --src src/**/*.{tsx,ts}
Successfully compiled 1 out of 1 components.
```
This is a bit surprising as most command line utilities handle multiple input files, here we need to quote the glob to have it work as intended:
```
> npx react-compiler-healthcheck --src "src/**/*.{tsx,ts}"
Successfully compiled 379 out of 399 components.
```

I would suggest making the first one work as well, that is the `--src` argument should accept an arbitrary number of files and process all of them.

### How often does this bug happen?

Every time

### What version of React are you using?

-
Repository: next.js
Issue: Error name is always overridden with "Error"
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://github.com/skolodyazhnyy/nextjs-error-name-overridden

### To Reproduce

1. Start application dev server: `npm run dev`
2. Open [`/demo` page](http://localhost:3000/demo)


### Current vs. Expected behavior

Current behavior:
- Page [throws an error](https://github.com/skolodyazhnyy/nextjs-error-name-overridden/blob/main/app/demo/page.tsx#L4) with `err.name = "PermissionDeniedError"`
- Error component [renders `err.name` as `"Error"`](https://github.com/skolodyazhnyy/nextjs-error-name-overridden/blob/main/app/error.tsx#L14)

Expected behavior:
- Page throws an error with `err.name = "PermissionDeniedError"`
- Error component receives error name unchanged: `err.name = "PermissionDeniedError"`


### Which area(s) are affected? (Select all that apply)

Runtime

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

I want to render different illustration and localised error message in my `error.tsx` depending on the error type. The issue is that there is no way to differentiate errors except by analyzing the error message itself, which is often dynamic and prone to changes overtime.

Currently I have to do something like `err.message.includes("permission denied") || err.message.includes("access denied") || err.message.includes("forbidden")` which is messy to say the least.
Repository: react
Issue: [Compiler Bug]: react native reanimated shared value mutation
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [X] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://github.com/AlirezaHadjar/react-compiler-shared-value-bug

### Repro steps

Hi, 
I'm using polyfill in react native to get the compiler working and noticing that the compiler is complaining about reanimated shared value mutations which is a very common pattern in [react native](https://docs.swmansion.com/react-native-reanimated/docs/fundamentals/your-first-animation/#using-a-shared-value).

```tsx
  const onPress = () => {
    translateX.value = withTiming((Math.random() - 0.5) * 100);
  };
```
![Screenshot 2024-05-29 at 12 40 14 PM](https://github.com/facebook/react/assets/57192409/dc33fd69-0637-4575-801d-5b31977f350a)

And the health-check command also confirms that `App.tsx` is not compiled.

![Screenshot 2024-05-29 at 12 42 33 PM](https://github.com/facebook/react/assets/57192409/c4d685ba-b775-4e12-a5ce-c68f1ed68fc1)

Steps to build the project:
1. yarn install
2. yarn ios

@josephsavona this is the issue that we discussed on [Twitter](https://x.com/alireza_hadjar/status/1795575101670519124?s=46&t=HIMTmQZ1qNgFDe3f7YV9kQ)


### How often does this bug happen?

Every time

### What version of React are you using?

18.2
Repository: node
Issue: Lambdas in node 18.x (18.20.3) and problems with axios HPE_INVALID_HEADER_TOKEN
Labels: http

### Version

18.20.3

### Platform

_No response_

### Subsystem

_No response_

### What steps will reproduce the bug?

Hello everyone

Recently my newly deployed lambdas projects have started having problems with axios.

To give context, I had some lambdas in node, the last time they were deployed it was in LTS node 18.20.1, this week the lambdas have been redeployed, some without adulterating the logic and the axios calls that previously worked now throw the error " HPE_INVALID_HEADER_TOKEN", "Parse Error: Unexpected whitespace after header value."

It should be noted that the lambda that makes the call, as well as the one that returns the response, have not modified their behavior, the only thing that coincides is the launch of node 18.20.3 LTS a few days ago.

Initially using axios 1.6.8 and 1.7.1, tested with the latest version 1.7.2 and gives the same error.

Have you experienced something familiar or have some idea how to solve it, because setting the --insecure-http-parser flag makes it work, but it is not a viable option for me.

The headers were validated and do not contain white spaces at the beginning, at the end, or after the comma.

### How often does it reproduce? Is there a required condition?

Whenever a request is made with axios

### What is the expected behavior? Why is that the expected behavior?

Get a 200 response

### What do you see instead?

HPE_INVALID_HEADER_TOKEN error, Parsing error: Unexpected whitespace after header value

### Additional information

We are aware that the problem has occurred in lambdas deployed since Friday, May 25, but we cannot establish a start date for the problem.
Repository: ollama
Issue: Computing Context Embeddings, Instead of averagning token embeddings
Labels: feature request

I was wondering whether we can return the context embeddings used before the next token prediction instead of averaging the token embeddings as currently done.
Repository: pytorch
Issue: Unable to quantize resnet50 model with post training static quantization
Labels: oncall: quantization,triaged

### 🐛 Describe the bug

This is my code 
```python
import torch
import torchvision

class QuantizedModel(torch.nn.Module):
    def __init__(self, model):
        super().__init__()
        self.quant = torch.quantization.QuantStub()
        self.model_fp32 = model
        self.dequant = torch.quantization.DeQuantStub()
        
    def forward(self, x):
        x = self.quant(x)
        x = self.model_fp32(x)
        x = self.dequant(x)
        return x

def fuse_resnet(model):
    torch.quantization.fuse_modules(model, [["conv1", "bn1", "relu"]], inplace=True)
    for layer_name, layer in model.named_children():
        if "layer" in layer_name:
            for block_name, block in layer.named_children():
                torch.quantization.fuse_modules(block, [["conv1", "bn1"], ["conv2", "bn2"], ["conv3", "bn3", "relu"]], inplace=True)
                for sub_block_name, sub_block in block.named_children():
                    if sub_block_name == "downsample":
                        torch.quantization.fuse_modules(sub_block, [["0", "1"]], inplace=True)
                
model = torchvision.models.resnet50()
model.eval()
fuse_resnet(model)
quantized_model = QuantizedModel(model)

backend = "qnnpack"
quantized_model.qconfig = torch.quantization.get_default_qconfig(backend)
torch.backends.quantized.engine = backend
model_static_quantized = torch.quantization.prepare(quantized_model, inplace=False)

input_fp32 = torch.randn(1, 3, 240, 240)
res1 = model_static_quantized(input_fp32)

model_static_quantized2 = torch.quantization.convert(model_static_quantized, inplace=False)
res2 = model_static_quantized2(input_fp32)
``` 
I get error at last line

```NotImplementedError: Could not run 'aten::add.out' with arguments from the 'QuantizedCPU' backend. This could be because the operator doesn't exist for this backend, or was omitted during the selective/custom build process (if using custom build). If you are a Facebook employee using PyTorch on mobile, please visit https://fburl.com/ptmfixes for possible resolutions. 'aten::add.out' is only available for these backends: [CPU, Meta, MkldnnCPU, SparseCPU, SparseCsrCPU, BackendSelect, Python, FuncTorchDynamicLayerBackMode, Functionalize, Named, Conjugate, Negative, ZeroTensor, ADInplaceOrView, AutogradOther, AutogradCPU, AutogradCUDA, AutogradHIP, AutogradXLA, AutogradMPS, AutogradIPU, AutogradXPU, AutogradHPU, AutogradVE, AutogradLazy, AutogradMTIA, AutogradPrivateUse1, AutogradPrivateUse2, AutogradPrivateUse3, AutogradMeta, AutogradNestedTensor, Tracer, AutocastCPU, AutocastCUDA, FuncTorchBatched, BatchedNestedTensor, FuncTorchVmapMode, Batched, VmapMode, FuncTorchGradWrapper, PythonTLSSnapshot, FuncTorchDynamicLayerFrontMode, PreDispatch, PythonDispatcher].```

### Versions

What am i missing here?

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: rust
Issue: Confusing diagnostic when doing a recursive call in a const block in a const fn: "cycle detected when elaborating drops" 
Labels: A-diagnostics,T-compiler,A-const-eval,D-confusing

### Code

```Rust
const fn foo() {
    const { foo() };
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0391]: cycle detected when elaborating drops for `foo`
 --> src/lib.rs:2:5
  |
2 |     const { foo() };
  |     ^^^^^^^^^^^^^^^
  |
note: ...which requires simplifying constant for the type system `foo::{constant#0}`...
 --> src/lib.rs:2:5
  |
2 |     const { foo() };
  |     ^^^^^^^^^^^^^^^
note: ...which requires const-evaluating + checking `foo::{constant#0}`...
 --> src/lib.rs:2:5
  |
2 |     const { foo() };
  |     ^^^^^^^^^^^^^^^
note: ...which requires caching mir of `foo` for CTFE...
 --> src/lib.rs:1:1
  |
1 | const fn foo() {
  | ^^^^^^^^^^^^^^
  = note: ...which again requires elaborating drops for `foo`, completing the cycle
  = note: cycle used when running analysis passes on this crate
  = 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

For more information about this error, try `rustc --explain E0391`.
error: could not compile `playground` (lib) due to 1 previous error
```


### Desired output

```Shell
Something about constant evaluation failing.
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

```Shell
Nightly rustc on the playground
1.80.0-nightly (2024-05-28 da159eb331b27df52818)
```


### Anything else?

_No response_
Repository: rust
Issue: compilation failure with "cargo check --tests" for espidf
Labels: C-bug,T-libs,O-ESP-IDF

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

Running `cargo check --tests` fails to compile `test` for the [esp-idf-template](https://github.com/esp-rs/esp-idf-template) (tested on mcu esp32-c3, default template options).

```
   Compiling test v0.0.0 (/home/ben/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/test)
error[E0308]: mismatched types
   --> /home/ben/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/test/src/test_result.rs:102:18
    |
101 |         None => match status.signal() {
    |                       --------------- this expression has type `Option<i32>`
102 |             Some(libc::SIGABRT) => TestResult::TrFailed,
    |                  ^^^^^^^^^^^^^ expected `i32`, found `usize`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `test` (lib) due to 1 previous error
```

https://github.com/rust-lang/libc/pull/3658 introduced these constants for espidf, where previously the error was a missing constant altogether (https://github.com/rust-lang/rust-analyzer/issues/16552).

### Steps to Reproduce

- `cargo generate esp-rs/esp-idf-template cargo`
  - Which MCU to target?: esp32c3
  - Configure advanced template options?: false
- `cd <project name> && cargo check --tests`

### 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.80.0-nightly (da159eb33 2024-05-28)
binary: rustc
commit-hash: da159eb331b27df528185c616b394bb0e1d2a4bd
commit-date: 2024-05-28
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.6
```