helloadhavan/github_issues huggingface dataset:
Repository: huggingface/transformers
Pull request: Delete irrelevant test that sometimes fails

`test_tokenizer_mismatch_warning` is causing errors in `BertJapanese`. This test has been removed in the main tokenizer classes now, and I don't think it tests anything useful anymore. I also remove the skip for it in `test_tokenizer_fast` because there's nothing to skip anymore!

Changed files:
filename: tests/models/bert_japanese/test_tokenization_bert_japanese.py
patch: @@ -19,7 +19,6 @@
 import unittest
 
 from transformers import AutoTokenizer
-from transformers.models.bert.tokenization_bert import BertTokenizer
 from transformers.models.bert_japanese.tokenization_bert_japanese import (
     VOCAB_FILES_NAMES,
     BertJapaneseTokenizer,
@@ -447,25 +446,3 @@ def test_tokenizer_bert_japanese(self):
         EXAMPLE_BERT_JAPANESE_ID = "cl-tohoku/bert-base-japanese"
         tokenizer = AutoTokenizer.from_pretrained(EXAMPLE_BERT_JAPANESE_ID)
         self.assertIsInstance(tokenizer, BertJapaneseTokenizer)
-
-
-class BertTokenizerMismatchTest(unittest.TestCase):
-    def test_tokenizer_mismatch_warning(self):
-        EXAMPLE_BERT_JAPANESE_ID = "cl-tohoku/bert-base-japanese"
-        with self.assertLogs("transformers", level="WARNING") as cm:
-            BertTokenizer.from_pretrained(EXAMPLE_BERT_JAPANESE_ID)
-            self.assertTrue(
-                cm.records[0].message.startswith(
-                    "The tokenizer class you load from this checkpoint is not the same type as the class this function"
-                    " is called from."
-                )
-            )
-        EXAMPLE_BERT_ID = "google-bert/bert-base-cased"
-        with self.assertLogs("transformers", level="WARNING") as cm:
-            BertJapaneseTokenizer.from_pretrained(EXAMPLE_BERT_ID)
-            self.assertTrue(
-                cm.records[0].message.startswith(
-                    "The tokenizer class you load from this checkpoint is not the same type as the class this function"
-                    " is called from."
-                )
-            )

filename: tests/tokenization/test_tokenization_fast.py
patch: @@ -86,12 +86,6 @@ def _create_test_tokenizers(cls):
 
         return paths
 
-    @unittest.skip(
-        "We disable this test for PreTrainedTokenizerFast because it is the only tokenizer that is not linked to any model"
-    )
-    def test_tokenizer_mismatch_warning(self):
-        pass
-
     @unittest.skip(
         "We disable this test for PreTrainedTokenizerFast because it is the only tokenizer that is not linked to any model"
     )
Repository: facebook/react
Pull request: Remove useActionState Hook export from experimental react-server condition

This Hook is not available in RSC environments. This is already the case in stable but not in experimental for some reason. Probably an oversight.


Changed files:
filename: packages/react/src/ReactServer.experimental.development.js
patch: @@ -30,7 +30,6 @@ import {
   useCallback,
   useDebugValue,
   useMemo,
-  useActionState,
   getCacheForType,
 } from './ReactHooks';
 import {forwardRef} from './ReactForwardRef';
@@ -78,7 +77,6 @@ export {
   useCallback,
   useDebugValue,
   useMemo,
-  useActionState,
   version,
   // Experimental
   REACT_SUSPENSE_LIST_TYPE as unstable_SuspenseList,

filename: packages/react/src/ReactServer.experimental.js
patch: @@ -30,7 +30,6 @@ import {
   useCallback,
   useDebugValue,
   useMemo,
-  useActionState,
   getCacheForType,
 } from './ReactHooks';
 import {forwardRef} from './ReactForwardRef';
@@ -77,7 +76,6 @@ export {
   useCallback,
   useDebugValue,
   useMemo,
-  useActionState,
   version,
   // Experimental
   REACT_SUSPENSE_LIST_TYPE as unstable_SuspenseList,
Repository: vuejs/vue
Pull request: Fix hot reload in IE in strict mode

Following a fix for v1 at #4274 for issue #4465

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->


Changed files:
filename: src/platforms/web/runtime/transition-util.js
patch: @@ -27,7 +27,8 @@ if (hasTransition) {
   }
 }
 
-const raf = (inBrowser && window.requestAnimationFrame) || setTimeout
+// binding to window is necessary to make hot reload work in IE in strict mode
+const raf = (inBrowser && window.requestAnimationFrame.bind(window)) || setTimeout
 export function nextFrame (fn: Function) {
   raf(() => {
     raf(fn)
Repository: nodejs/node
Pull request: doc: fix pseudo code in modules.md

The pseudo code involved in the change adds the `node_modules` directories closer and closer to the root directory to `DIRS`. The correct way should be to add it to the end, which is consistent with the actual behavior of Node.

This problem was introduced in f77fe645 of PR #38837.

@Ayase-252 applied a change suggested by @guybedford, although they discovered that the change is wrong in a later conversation, the change was still merged.[^1]

[^1]: https://github.com/nodejs/node/pull/38837#discussion_r641990919

Changed files:
filename: doc/api/modules.md
patch: @@ -414,7 +414,7 @@ NODE_MODULES_PATHS(START)
 4. while I >= 0,
    a. if PARTS[I] = "node_modules", GOTO d.
    b. DIR = path join(PARTS[0 .. I] + "node_modules")
-   c. DIRS = DIR + DIRS
+   c. DIRS = DIRS + DIR
    d. let I = I - 1
 5. return DIRS + GLOBAL_FOLDERS
Repository: electron/electron
Pull request: fix: `trafficLightPosition` incorrect with `customButtonsOnHover`

Backport of #48538

See that PR for details.


Notes: Fixed an issue where `trafficLightPosition` would not be correctly applied when using `titleBarStyle: 'customButtonsOnHover'` on macOS 26.


Changed files:
filename: shell/browser/ui/cocoa/window_buttons_proxy.mm
patch: @@ -176,6 +176,13 @@ - (void)updateButtonsVisibility {
     [button setHidden:hidden];
     [button setNeedsDisplay:YES];
   }
+
+  // On macOS 26, toggling the hidden state of the standard window buttons can
+  // cause AppKit to re-layout the title bar container and reset its frame,
+  // which loses the custom margin adjustments. Re-apply the calculated geometry
+  // after visibility changes to keep the buttons at the specified margin
+  // instead of snapping back to the default until the next manual resize.
+  [self redraw];
 }
 
 // Return the bounds of all 3 buttons.
Repository: vercel/next.js
Pull request: Bump swc

to get https://github.com/swc-project/swc/pull/11324

Changed files:
filename: Cargo.lock
patch: @@ -7172,9 +7172,9 @@ dependencies = [
 
 [[package]]
 name = "swc_core"
-version = "48.0.1"
+version = "48.0.4"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "ac9fecd2de65d40ad1324a727cde1d94034ef4693cb919b18b36395a56825b19"
+checksum = "1e939dc7075a9b2d3e7bbf4abe6ed67b269bf09131e04da00aaa036c0095b03e"
 dependencies = [
  "binding_macros",
  "par-core",
@@ -7666,9 +7666,9 @@ dependencies = [
 
 [[package]]
 name = "swc_ecma_minifier"
-version = "36.0.3"
+version = "36.0.4"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "6e07508fefa4a1aedd7937da5829a49d15553a461b696bb0590705b0abd7416c"
+checksum = "33a8f18102ea39542276af77f0efe27f514fb561c784278d19ba489e2cddf308"
 dependencies = [
  "arrayvec 0.7.6",
  "bitflags 2.9.1",
@@ -7702,9 +7702,9 @@ dependencies = [
 
 [[package]]
 name = "swc_ecma_parser"
-version = "27.0.6"
+version = "27.0.7"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "0d55d5ad2d312b346f0ac295f8948e151943a711247b3652b2872b3a233e683d"
+checksum = "7f1a51af1a92cd4904c073b293e491bbc0918400a45d58227b34c961dd6f52d7"
 dependencies = [
  "bitflags 2.9.1",
  "either",
@@ -7815,9 +7815,9 @@ dependencies = [
 
 [[package]]
 name = "swc_ecma_transforms_base"
-version = "30.0.0"
+version = "30.0.1"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "305080c8ce2a5280549ad9715f958c093686705fa67108d00cb17c7ddf5f1e4a"
+checksum = "250f6f165578ca4fee47bd57585c1b9597c94bf4ea6591df47f2b5fa5b1883fe"
 dependencies = [
  "better_scoped_tls",
  "indexmap 2.9.0",

filename: Cargo.toml
patch: @@ -337,7 +337,7 @@ turbopack-trace-utils = { path = "turbopack/crates/turbopack-trace-utils" }
 turbopack-wasm = { path = "turbopack/crates/turbopack-wasm" }
 
 # SWC crates
-swc_core = { version = "48.0.1", features = [
+swc_core = { version = "48.0.4", features = [
   "ecma_loader_lru",
   "ecma_loader_parking_lot",
   "parallel_rayon",
Repository: facebook/react
Pull request: [compiler] Improve error messages for unhandled terminal and instruction kinds

<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->
Improve the error message, as the value is currently an object instead of a string, which results in it being converted to '[object Object]'.

## How did you test this change?
Already tested locally.
<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->


Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/ReactiveScopes/PrintReactiveFunction.ts
patch: @@ -394,7 +394,10 @@ function writeTerminal(writer: Writer, terminal: ReactiveTerminal): void {
       break;
     }
     default:
-      assertExhaustive(terminal, `Unhandled terminal ${terminal}`);
+      assertExhaustive(
+        terminal,
+        `Unhandled terminal kind \`${(terminal as any).kind}\``,
+      );
   }
 }
 

filename: compiler/packages/babel-plugin-react-compiler/src/TypeInference/InferTypes.ts
patch: @@ -420,7 +420,10 @@ function* generateInstructionTypes(
       break;
     }
     default:
-      assertExhaustive(value, `Unhandled instruction value kind: ${value}`);
+      assertExhaustive(
+        value,
+        `Unhandled instruction value kind: ${(value as any).kind}`,
+      );
   }
 }
Repository: nodejs/node
Pull request: doc: HTTP Module request.reusedSocket documentation sample code error fix

doc: HTTP Module request.reusedSocket documentation sample code has a error, their is no agent variable declared in the sample code but that agent variable is used in the request object, which is really confusing for the reader, from where does the agent variable is taken.

So, fixed the code by adding the agent variable and taking the http.agent initalization.

<!--
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: doc/api/http.md
patch: @@ -1174,6 +1174,7 @@ may run into a 'ECONNRESET' error.
 
 ```mjs
 import http from 'node:http';
+const agent = new http.Agent({ keepAlive: true });
 
 // Server has a 5 seconds keep-alive timeout by default
 http
@@ -1195,6 +1196,7 @@ setInterval(() => {
 
 ```cjs
 const http = require('node:http');
+const agent = new http.Agent({ keepAlive: true });
 
 // Server has a 5 seconds keep-alive timeout by default
 http
Repository: vuejs/vue
Pull request: Fix hot reload in IE in strict mode

Fix #4465

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->


Changed files:
filename: src/transition/transition.js
patch: @@ -32,9 +32,12 @@ const animDurationProp = animationProp + 'Duration'
  * transitions but not raf (e.g. Android 4.2 browser) - since
  * these environments are usually slow, we are giving it a
  * relatively large timeout.
+ * 
+ * Binding to window is necessary to make hot reload work in
+ * IE in strict mode
  */
 
-const raf = inBrowser && window.requestAnimationFrame
+const raf = inBrowser && window.requestAnimationFrame.bind(window)
 const waitForTransitionStart = raf
   /* istanbul ignore next */
   ? function (fn) { raf(function () { raf(fn) }) }
Repository: facebook/react
Pull request: [ci] Fix typo


Oops.


Changed files:
filename: .github/workflows/shared_close_direct_sync_branch_prs.yml
patch: @@ -3,7 +3,7 @@ name: (Shared) Close Direct Sync Branch PRs
 on:
   pull_request:
     branches:
-      - builds/facebook-*
+      - 'builds/facebook-**'
 
 env:
   TZ: /usr/share/zoneinfo/America/Los_Angeles
Repository: ollama/ollama
Pull request: Update README.md

New links: 
Go-CREW and Ollamaclient for Golang

Changed files:
filename: README.md
patch: @@ -302,6 +302,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [LLMStack](https://github.com/trypromptly/LLMStack) (No-code multi-agent framework to build LLM agents and workflows)
 - [BoltAI for Mac](https://boltai.com) (AI Chat Client for Mac)
 - [Harbor](https://github.com/av/harbor) (Containerized LLM Toolkit with Ollama as default backend)
+- [Go-CREW](https://www.jonathanhecl.com/go-crew/) (Powerful Offline RAG in Golang)
 
 ### Terminal
 
@@ -370,6 +371,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Portkey](https://portkey.ai/docs/welcome/integration-guides/ollama)
 - [PromptingTools.jl](https://github.com/svilupp/PromptingTools.jl) with an [example](https://svilupp.github.io/PromptingTools.jl/dev/examples/working_with_ollama)
 - [LlamaScript](https://github.com/Project-Llama/llamascript)
+- [Ollamaclient for Golang](https://github.com/xyproto/ollamaclient)
 
 ### Mobile
Repository: ggml-org/llama.cpp
Pull request: convert : add missing return statement for GraniteMoeModel

This commit adds a missing return statement to the GraniteMoeModel class to fix an issue in the model conversion process.

Resolves: https://github.com/ggml-org/llama.cpp/issues/19201

Changed files:
filename: convert_hf_to_gguf.py
patch: @@ -8806,6 +8806,7 @@ def modify_tensors(self, data_torch: Tensor, name: str, bid: int | None) -> Iter
             gate, up = data_torch.split(ffn_dim, dim=-2)
             yield from ModelBase.modify_tensors(self, gate, self.format_tensor_name(gguf.MODEL_TENSOR.FFN_GATE_EXP, bid), bid)
             yield from ModelBase.modify_tensors(self, up, self.format_tensor_name(gguf.MODEL_TENSOR.FFN_UP_EXP, bid), bid)
+            return
 
         has_experts = bool(self.hparams.get('num_local_experts'))
Repository: nodejs/node
Pull request: doc: add a missing word in api/single-executable-applications.md

There was a missing word in the "Startup snapshot support" section of single-executable-applications.md

<!--
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: doc/api/single-executable-applications.md
patch: @@ -241,11 +241,11 @@ See documentation of the [`sea.getAsset()`][], [`sea.getAssetAsBlob()`][],
 ### Startup snapshot support
 
 The `useSnapshot` field can be used to enable startup snapshot support. In this
-case the `main` script would not be when the final executable is launched.
+case, the `main` script would not be executed when the final executable is launched.
 Instead, it would be run when the single executable application preparation
 blob is generated on the building machine. The generated preparation blob would
 then include a snapshot capturing the states initialized by the `main` script.
-The final executable with the preparation blob injected would deserialize
+The final executable, with the preparation blob injected, would deserialize
 the snapshot at run time.
 
 When `useSnapshot` is true, the main script must invoke the
Repository: ollama/ollama
Pull request: Update faq.md

I found many issues with the error "could not connect to ollama app, is it running?"

If not mention the ownership of the changed model path, many beginners and carfuless developer will failed to start the ollama service, which would cost plenty time on troubleshoting.

Make it clear in FaQ will help developers to save their time.

Changed files:
filename: docs/faq.md
patch: @@ -194,6 +194,8 @@ Refer to the section [above](#how-do-i-configure-ollama-server) for how to set e
 
 If a different directory needs to be used, set the environment variable `OLLAMA_MODELS` to the chosen directory.
 
+> Note: on Linux using the standard installer, the `ollama` user needs read and write access to the specified directory. To assign the directory to the `ollama` user run `sudo chown -R ollama:ollama <directory>`.
+
 Refer to the section [above](#how-do-i-configure-ollama-server) for how to set environment variables on your platform.
 
 ## How can I use Ollama in Visual Studio Code?
Repository: facebook/react
Pull request: [ci] Disallow PRs against builds branch


Our internal build infra relies on a 1:1 mapping between `main` and the 2 build branches. Directly committing changes to those branches breaks that infra.

Adds a simple workflow to leave a comment and decline the PR.


Changed files:
filename: .github/workflows/shared_close_direct_sync_branch_prs.yml
patch: @@ -0,0 +1,37 @@
+name: (Shared) Close Direct Sync Branch PRs
+
+on:
+  pull_request:
+    branches:
+      - builds/facebook-*
+
+env:
+  TZ: /usr/share/zoneinfo/America/Los_Angeles
+  # https://github.com/actions/cache/blob/main/tips-and-workarounds.md#cache-segment-restore-timeout
+  SEGMENT_DOWNLOAD_TIMEOUT_MINS: 1
+
+jobs:
+  close_pr:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Close PR
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const owner = context.repo.owner;
+            const repo = context.repo.repo;
+            const pullNumber = ${{ github.event.number }};
+
+            await github.rest.pulls.createReview({
+              owner,
+              repo,
+              pull_number: pullNumber,
+              body: 'Do not land changes to `${{ github.event.pull_request.base.ref }}`. Please re-open your PR targeting `main` instead.',
+              event: 'REQUEST_CHANGES'
+            });
+            await github.rest.pulls.update({
+              owner,
+              repo,
+              pull_number: pullNumber,
+              state: 'closed'
+            });
Repository: vuejs/vue
Pull request: Updated Android 4 SauceLabs configuration

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->
SauceLabs has sunset all versions of Android prior to 4.4:
https://wiki.saucelabs.com/pages/viewpage.action?pageId=67012495

Let me save you the pain I've endured the past few days, getting my SauceLabs Android 4.2 Selendroid configuration upgraded to Android 4.4 on Appium. *Oh honey child let me save you!* 💋

Changed files:
filename: build/karma.sauce.config.js
patch: @@ -62,10 +62,12 @@ var batches = [
       browserName: 'iphone',
       version: '9.3'
     },
-    sl_android_4_2: {
+    sl_android_4_4: {
       base: 'SauceLabs',
-      browserName: 'android',
-      version: '4.2'
+      browserName: 'Browser',
+      platform: 'Android',
+      version: '4.4',
+      device: 'Android Emulator'
     },
     sl_android_5_1: {
       base: 'SauceLabs',
@@ -88,6 +90,9 @@ module.exports = function (config) {
     sauceLabs: {
       testName: 'Vue.js unit tests',
       recordScreenshots: false,
+      connectOptions: {
+        'no-ssl-bump-domains': 'all' // Ignore SSL error on Android emulator
+      },
       build: process.env.CIRCLE_BUILD_NUM || process.env.SAUCE_BUILD_ID || Date.now()
     },
     // mobile emulators are really slow