helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: Remove unused Server.responseCache

This appears to have been moved into the `RouteModule`

https://github.com/vercel/next.js/issues/80189

Changed files:
filename: packages/next/src/server/base-server.ts
patch: @@ -17,10 +17,7 @@ import type {
   RenderOptsPartial as AppRenderOptsPartial,
   ServerOnInstrumentationRequestError,
 } from './app-render/types'
-import type {
-  ServerComponentsHmrCache,
-  ResponseCacheBase,
-} from './response-cache'
+import type { ServerComponentsHmrCache } from './response-cache'
 import type { UrlWithParsedQuery } from 'url'
 import {
   NormalizeError,
@@ -329,7 +326,6 @@ export default abstract class Server<
   protected interceptionRoutePatterns: RegExp[]
   protected nextFontManifest?: DeepReadonly<NextFontManifest>
   protected instrumentation: InstrumentationModule | undefined
-  private readonly responseCache: ResponseCacheBase
 
   protected abstract getPublicDir(): string
   protected abstract getHasStaticDir(): boolean
@@ -396,10 +392,6 @@ export default abstract class Server<
     requestHeaders: Record<string, undefined | string | string[]>
   }): Promise<import('./lib/incremental-cache').IncrementalCache>
 
-  protected abstract getResponseCache(options: {
-    dev: boolean
-  }): ResponseCacheBase
-
   protected getServerComponentsHmrCache():
     | ServerComponentsHmrCache
     | undefined {
@@ -569,7 +561,6 @@ export default abstract class Server<
     void this.matchers.reload()
 
     this.setAssetPrefix(assetPrefix)
-    this.responseCache = this.getResponseCache({ dev })
   }
 
   protected reloadMatchers() {

filename: packages/next/src/server/next-server.ts
patch: @@ -525,10 +525,6 @@ export default class NextNodeServer extends BaseServer<
     })
   }
 
-  protected getResponseCache() {
-    return new ResponseCache(this.minimalMode)
-  }
-
   protected getPublicDir(): string {
     return join(/* turbopackIgnore: true */ this.dir, CLIENT_PUBLIC_FILES_PATH)
   }
Repository: vuejs/vue
Pull request: Support Vue.delete(arr, index) in TypeScript definitions

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe: TypeScript Definition Update

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**
Vue 2.2.0 added support for Vue.delete(arr, index). This updates the TypeScript definition to allow that.
Refs: https://github.com/vuejs/vue/releases/tag/v2.2.0


Changed files:
filename: types/test/vue-test.ts
patch: @@ -78,6 +78,7 @@ class Test extends Vue {
     this.set({}, "", "");
     this.set([true, false, true], 1, true);
     this.delete({}, "");
+    this.delete([true, false], 0);
     this.directive("", {bind() {}});
     this.filter("", (value: number) => value);
     this.component("", { data: () => ({}) });

filename: types/vue.d.ts
patch: @@ -84,6 +84,7 @@ export declare class Vue {
   static set<T>(object: Object, key: string, value: T): T;
   static set<T>(array: T[], key: number, value: T): T;
   static delete(object: Object, key: string): void;
+  static delete<T>(array: T[], key: number): void;
 
   static directive(
     id: string,
Repository: nodejs/node
Pull request: tools: remove unsupported `cooldown` from Dependabot config

See https://github.com/nodejs/node/pull/60643/checks?check_run_id=55500510077 for an example of failure. The docs say that `cooldown` is not supported for GitHub Actions update.

Refs: https://docs.github.com/en/code-security/dependabot/working-with-dependabot/dependabot-options-reference#configuration-of-cooldown
<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: .github/dependabot.yml
patch: @@ -6,10 +6,6 @@ updates:
     directory: /
     schedule:
       interval: monthly
-    cooldown:
-      semver-major-days: 5
-      semver-minor-days: 5
-      semver-patch-days: 5
     commit-message:
       prefix: meta
     open-pull-requests-limit: 10
Repository: huggingface/transformers
Pull request: Tiny Clean up `_deps` in setup.py

# What does this PR do?

`dataclasses` comes built-in from `python>=3.7`. So, it can be removed from the `_deps` list as well.


**Un-related** but, I observed that this [splitted_tests.txt](https://github.com/huggingface/transformers/blob/main/splitted_tests.txt) was added in the repo's main directory in this [PR](https://github.com/huggingface/transformers/pull/42168) & It has only 1 line. Maybe that's why test's didn't ran?? https://github.com/huggingface/transformers/pull/42168#issuecomment-3596609989 I am not sure, but flagging it just in case it was committed accidentally.


## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [x] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?
@Rocketknight1 @ArthurZucker @ydshieh 

Changed files:
filename: setup.py
patch: @@ -99,7 +99,6 @@
     "blobfile",
     "codecarbon>=2.8.1",
     "cookiecutter==1.7.3",
-    "dataclasses",
     "datasets>=2.15.0",  # We need either this pin or pyarrow<21.0.0
     "deepspeed>=0.9.3",
     "diffusers",

filename: src/transformers/dependency_versions_table.py
patch: @@ -9,7 +9,6 @@
     "blobfile": "blobfile",
     "codecarbon": "codecarbon>=2.8.1",
     "cookiecutter": "cookiecutter==1.7.3",
-    "dataclasses": "dataclasses",
     "datasets": "datasets>=2.15.0",
     "deepspeed": "deepspeed>=0.9.3",
     "diffusers": "diffusers",
Repository: ollama/ollama
Pull request: Send all images in conversation history

@pdevine I'm not entirely sure what the history of this check was - it sounds like there were previously some models that didn't do well with images in the history. However, it worked well with the models that I tried it on.

Regardless, I don't think the check belongs in the CLI.

Changed files:
filename: cmd/interactive.go
patch: @@ -442,13 +442,6 @@ func generateInteractive(cmd *cobra.Command, opts runOptions) error {
 					return err
 				}
 
-				// clear all previous images for better responses
-				if len(images) > 0 {
-					for i := range opts.Messages {
-						opts.Messages[i].Images = nil
-					}
-				}
-
 				newMessage.Content = msg
 				newMessage.Images = images
 			}
Repository: ggml-org/llama.cpp
Pull request: memory : fix kv cache size for hybrid models

fix #19552

We were incorrectly allocating `-np` times more KV cache for hybrid models.

Changed files:
filename: src/llama-model.cpp
patch: @@ -7965,7 +7965,6 @@ llama_memory_i * llama_model::create_memory(const llama_memory_params & params,
                             cparams.n_seq_max,
                             nullptr);
                 } else if (llm_arch_is_hybrid(arch)) {
-
                     // The main difference between hybrid architectures is the
                     // layer filters, so pick the right one here
                     llama_memory_hybrid::layer_filter_cb filter_attn = nullptr;
@@ -7990,7 +7989,7 @@ llama_memory_i * llama_model::create_memory(const llama_memory_params & params,
                             /* attn_type_v       */ params.type_v,
                             /* attn_v_trans      */ !cparams.flash_attn,
                             /* attn_swa_full     */ params.swa_full,
-                            /* attn_kv_size      */ cparams.n_ctx,
+                            /* attn_kv_size      */ cparams.n_ctx_seq,
                             /* attn_n_ubatch     */ cparams.n_ubatch,
                             /* attn_n_pad        */ 1,
                             /* recurrent_type_r  */ GGML_TYPE_F32,
@@ -8007,7 +8006,7 @@ llama_memory_i * llama_model::create_memory(const llama_memory_params & params,
                             /* attn_type_k       */ params.type_k,
                             /* attn_type_v       */ params.type_v,
                             /* attn_v_trans      */ !cparams.flash_attn,
-                            /* attn_kv_size      */ cparams.n_ctx,
+                            /* attn_kv_size      */ cparams.n_ctx_seq,
                             /* attn_n_pad        */ 1,
                             /* attn_n_swa        */ hparams.n_swa,
                             /* attn_swa_type     */ hparams.swa_type,
Repository: huggingface/transformers
Pull request: [Fix]Integrate LLM generation parameters into the evaluation method

# What does this PR do?
## Phenomenon:
In the Trainer class, the evaluate method does not accept any LLM generation parameters. However, Seq2SeqTrainer inherits from Trainer and overrides the evaluate method. When Seq2SeqTrainer calls Trainer.evaluate, the generation parameters are lost. Subsequently, when Trainer calls the evaluate method again, this results in the loss of the generation parameters.
## What I do:
I added gen_kwargs in Trainer.evaluate, which flexibly allows the passing of generate parameters. Additionally, I modified the call to Trainer.evaluate in Seq2SeqTrainer.evaluate to include the LLM generation parameters.

Changed files:
filename: src/transformers/testing_utils.py
patch: @@ -638,6 +638,9 @@ def require_read_token(test_case):
                 if getattr(attr, "__require_read_token__", False):
                     continue
                 wrapped = require_read_token(attr)
+                if isinstance(inspect.getattr_static(test_case, attr_name), staticmethod):
+                    # Don't accidentally bind staticmethods to `self`
+                    wrapped = staticmethod(wrapped)
                 setattr(test_case, attr_name, wrapped)
         return test_case
     else:
@@ -650,10 +653,6 @@ def wrapper(*args, **kwargs):
                 with patch("huggingface_hub.utils._headers.get_token", return_value=token):
                     return test_case(*args, **kwargs)
             else:  # Allow running locally with the default token env variable
-                # dealing with static/class methods and called by `self.xxx`
-                if "staticmethod" in inspect.getsource(test_case).strip():
-                    if len(args) > 0 and isinstance(args[0], unittest.TestCase):
-                        return test_case(*args[1:], **kwargs)
                 return test_case(*args, **kwargs)
 
         wrapper.__require_read_token__ = True
Repository: ollama/ollama
Pull request: fix vendoring attribute for metal

Add missing metal files to vendoring list

Changed files:
filename: .gitattributes
patch: @@ -6,6 +6,7 @@ llama/**/*.c linguist-vendored
 llama/**/*.cu linguist-vendored
 llama/**/*.cuh linguist-vendored
 llama/**/*.m linguist-vendored
+llama/**/*.metal linguist-vendored
 
 * text=auto
 *.go text eol=lf
Repository: ollama/ollama
Pull request: fix vendoring attribute

Expand out the file extensions for vendored code so git reports the status correctly

e.g.:
```
% git check-attr -a -- ./llama/ggml.c
./llama/ggml.c: text: auto
./llama/ggml.c: linguist-vendored: set
```

Changed files:
filename: .gitattributes
patch: @@ -1,5 +1,11 @@
 llm/ext_server/* linguist-vendored
-llama/**/*.{cpp,hpp,h,c,cu,cuh,m} linguist-vendored
+llama/**/*.cpp linguist-vendored
+llama/**/*.hpp linguist-vendored
+llama/**/*.h linguist-vendored
+llama/**/*.c linguist-vendored
+llama/**/*.cu linguist-vendored
+llama/**/*.cuh linguist-vendored
+llama/**/*.m linguist-vendored
 
 * text=auto
 *.go text eol=lf
Repository: facebook/react
Pull request: [compiler][ez] Add shape for global Object.keys


Add shape / type for global Object.keys. This is useful because
- it has an Effect.Read (not an Effect.Capture) as it cannot alias its argument.
- Object.keys return an array
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/31583).
* __->__ #31583
* #31582

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/Globals.ts
patch: @@ -88,6 +88,21 @@ const UNTYPED_GLOBALS: Set<string> = new Set([
 ]);
 
 const TYPED_GLOBALS: Array<[string, BuiltInType]> = [
+  [
+    'Object',
+    addObject(DEFAULT_SHAPES, 'Object', [
+      [
+        'keys',
+        addFunction(DEFAULT_SHAPES, [], {
+          positionalParams: [Effect.Read],
+          restParam: null,
+          returnType: {kind: 'Object', shapeId: BuiltInArrayId},
+          calleeEffect: Effect.Read,
+          returnValueKind: ValueKind.Mutable,
+        }),
+      ],
+    ]),
+  ],
   [
     'Array',
     addObject(DEFAULT_SHAPES, 'Array', [

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/shapes-object-key.expect.md
patch: @@ -0,0 +1,49 @@
+
+## Input
+
+```javascript
+import {arrayPush} from 'shared-runtime';
+
+function useFoo({a, b}) {
+  const obj = {a};
+  arrayPush(Object.keys(obj), b);
+  return obj;
+}
+export const FIXTURE_ENTRYPOINT = {
+  fn: useFoo,
+  params: [{a: 2, b: 3}],
+};
+
+```
+
+## Code
+
+```javascript
+import { c as _c } from "react/compiler-runtime";
+import { arrayPush } from "shared-runtime";
+
+function useFoo(t0) {
+  const $ = _c(2);
+  const { a, b } = t0;
+  let t1;
+  if ($[0] !== a) {
+    t1 = { a };
+    $[0] = a;
+    $[1] = t1;
+  } else {
+    t1 = $[1];
+  }
+  const obj = t1;
+  arrayPush(Object.keys(obj), b);
+  return obj;
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: useFoo,
+  params: [{ a: 2, b: 3 }],
+};
+
+```
+      
+### Eval output
+(kind: ok) {"a":2}
\ No newline at end of file

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/shapes-object-key.ts
patch: @@ -0,0 +1,11 @@
+import {arrayPush} from 'shared-runtime';
+
+function useFoo({a, b}) {
+  const obj = {a};
+  arrayPush(Object.keys(obj), b);
+  return obj;
+}
+export const FIXTURE_ENTRYPOINT = {
+  fn: useFoo,
+  params: [{a: 2, b: 3}],
+};
Repository: vuejs/vue
Pull request: Warn when not passing props in kebab-case

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [x] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

Hi,

Please see #5145 

This patch adds a warning when user is not passing props in kebab-case mistakenly, for example:

```html
<foo someProp="bar"></foo>
should be
<foo some-prop="bar"></foo>
```

I know this is stated on the guide, but since it's a very common mistake (based on the questions on stackoverflow (see the issue above) [and the](https://forum.vuejs.org/t/unable-to-pass-data-from-parent-to-child-component/1763/1) [forum](https://forum.vuejs.org/t/need-help-with-passing-a-boolean-prop-to-a-comonent/3996/1 )), I think it is worth to add a warning and I believe this will save a lot of people's debugging time and provide a more friendly development experience.

And for the performance, this is not a complex algorithm. It only adds a fews operations (both `toLowerCase` and `hasOwnProperty` are fast enough) in O(n) so I would say the impact on performance is negligible (almost no impact when running unit test on my machine). 

thanks!

Changed files:
filename: src/core/vdom/create-component.js
patch: @@ -286,6 +286,18 @@ function extractProps (data: VNodeData, Ctor: Class<Component>): ?Object {
   if (attrs || props || domProps) {
     for (const key in propOptions) {
       const altKey = hyphenate(key)
+      if (process.env.NODE_ENV !== 'production') {
+        const keyInLowerCase = key.toLowerCase()
+        if (
+          key !== keyInLowerCase &&
+          attrs && attrs.hasOwnProperty(keyInLowerCase)
+        ) {
+          warn(
+            `HTML attributes are case-insensitive. camelCased prop names need ` +
+            `to use their kebab-case equivalents. ${key} should be ${altKey}.`
+          )
+        }
+      }
       checkProp(res, props, key, altKey, true) ||
       checkProp(res, attrs, key, altKey) ||
       checkProp(res, domProps, key, altKey)

filename: test/unit/features/component/component.spec.js
patch: @@ -258,6 +258,25 @@ describe('Component', () => {
     expect(vm.$el.outerHTML).toBe('<ul><li>1</li><li>2</li></ul>')
   })
 
+  it('should warn when not passing props in kebab-case', () => {
+    new Vue({
+      data: {
+        list: [{ a: 1 }, { a: 2 }]
+      },
+      template: '<test :somecollection="list"></test>',
+      components: {
+        test: {
+          template: '<ul><li v-for="item in someCollection">{{item.a}}</li></ul>',
+          props: ['someCollection']
+        }
+      }
+    }).$mount()
+    expect(
+      'HTML attributes are case-insensitive. camelCased prop names need ' +
+      'to use their kebab-case equivalents. someCollection should be some-collection.'
+    ).toHaveBeenWarned()
+  })
+
   it('not found component should not throw', () => {
     expect(function () {
       new Vue({
Repository: nodejs/node
Pull request: tools: update nixpkgs-unstable to 71cf367cc2c168b0c2959835659c38f0a34

This is an automated update of nixpkgs-unstable to ~https://github.com/NixOS/nixpkgs/commit/1d4c88323ac36805d09657d13a5273aea1b~ https://github.com/NixOS/nixpkgs/commit/71cf367cc2c168b0c2959835659c38f0a342f9be (bumped it so we can integrate temporal_capi in a cleaner way in https://github.com/nodejs/node/pull/60701)

Changed files:
filename: tools/nix/pkgs.nix
patch: @@ -1,10 +1,10 @@
 arg:
 let
   repo = "https://github.com/NixOS/nixpkgs";
-  rev = "ffcdcf99d65c61956d882df249a9be53e5902ea5";
+  rev = "71cf367cc2c168b0c2959835659c38f0a342f9be";
   nixpkgs = import (builtins.fetchTarball {
     url = "${repo}/archive/${rev}.tar.gz";
-    sha256 = "09ifrgxin9may5kll1g2fdxixb0k3ipzhfw90mckl17mpbrgaglp";
+    sha256 = "0gqzy7r8jn2f5ymy7ixminbf7yx9dxn8kgiqm1g394x0p1rd1q00";
   }) arg;
 in
 nixpkgs
Repository: ollama/ollama
Pull request: Fix build leakages

The recent change to applying patches leaves the submodule dirty based on "new commits" being present.  This ensures we clean up so the tree no longer reports dirty after a `go generate ./...` run.

The Makefile was being a bit too aggressive in cleaning things up and would result in deleting the placeholder files which someone might accidentally commit.

Changed files:
filename: llama/Makefile
patch: @@ -42,7 +42,7 @@ $(RUNNER_TARGETS):
 	$(MAKE) -f make/Makefile.$@
 
 clean:
-	rm -rf $(BUILD_DIR) $(DIST_RUNNERS) $(PAYLOAD_RUNNERS) $(RUNNERS_PAYLOAD_DIR)
+	rm -rf $(BUILD_DIR) $(DIST_RUNNERS) $(PAYLOAD_RUNNERS)
 
 clean-payload:
 	rm -rf $(addprefix $(RUNNERS_PAYLOAD_DIR)/, $(RUNNER_TARGETS) metal cpu cpu_avx cpu_avx2)

filename: llm/generate/gen_common.sh
patch: @@ -133,13 +133,5 @@ install() {
 
 # Keep the local tree clean after we're done with the build
 cleanup() {
-    (cd ${LLAMACPP_DIR}/ && git checkout CMakeLists.txt)
-
-    if [ -n "$(ls -A ../patches/*.diff)" ]; then
-        for patch in ../patches/*.diff; do
-            for file in $(grep "^+++ " ${patch} | cut -f2 -d' ' | cut -f2- -d/); do
-                (cd ${LLAMACPP_DIR}; git checkout ${file})
-            done
-        done
-    fi
+    git submodule update --force ${LLAMACPP_DIR}
 }
Repository: electron/electron
Pull request: build: use --keep-non-patch flag with git am

Backport of #48797

See that PR for details.


Notes: none <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->


Changed files:
filename: script/lib/git.py
patch: @@ -52,7 +52,8 @@ def get_repo_root(path):
 
 def am(repo, patch_data, threeway=False, directory=None, exclude=None,
     committer_name=None, committer_email=None, keep_cr=True):
-  args = []
+  # --keep-non-patch prevents stripping leading bracketed strings on the subject line
+  args = ['--keep-non-patch']
   if threeway:
     args += ['--3way']
   if directory is not None: