helloadhavan/github_issues huggingface dataset:
Repository: ggml-org/llama.cpp
Pull request: ai : limit runtime of the agent

cont #20810 

- Max runtime for the agent is now 5 min (prevent loops such as https://github.com/ggml-org/llama.cpp/actions/runs/23355930365/job/67946602010#step:3:718)
- Try to workaround https://github.com/anomalyco/opencode/issues/13770 by instructing the agent to narrow-down the search in such cases

Changed files:
filename: .github/workflows/ai-issues.yml
patch: @@ -27,15 +27,15 @@ jobs:
               "bash": {
                 "*": "deny",
                 "gh issue*": "allow",
-                "gh search*": "allow"
+                "gh search issues*": "allow"
               },
               "webfetch": "deny"
             }
         run: |
           rm AGENTS.md
           rm CLAUDE.md
 
-          opencode run -m llama.cpp-dgx/ai-review-issues-find-similar --thinking "A new issue has been created:
+          timeout 5m opencode run -m llama.cpp-dgx/ai-review-issues-find-similar --thinking "A new issue has been created:
 
           Issue number: ${{ github.event.issue.number }}
 
@@ -83,4 +83,5 @@ jobs:
             - Post at most ONE comment combining all findings.
             - If you didn't find issues that are related enough, post nothing.
             - You have access only to the 'gh' CLI tool - don't try to use other tools.
+            - If the output from a tool call is too long, try to limit down the search.
           "
Repository: nodejs/node
Pull request: test_runner: fix passing `expectFailure`


Changed files:
filename: lib/internal/test_runner/test.js
patch: @@ -82,6 +82,7 @@ const kParentAlreadyFinished = 'parentAlreadyFinished';
 const kSubtestsFailed = 'subtestsFailed';
 const kTestCodeFailure = 'testCodeFailure';
 const kTestTimeoutFailure = 'testTimeoutFailure';
+const kExpectedFailure = 'expectedFailure';
 const kHookFailure = 'hookFailed';
 const kDefaultTimeout = null;
 const noop = FunctionPrototype;
@@ -957,6 +958,14 @@ class Test extends AsyncResource {
   }
 
   pass() {
+    if (this.error == null && this.expectFailure === true && !this.skipped) {
+      this.passed = false;
+      this.error = new ERR_TEST_FAILURE(
+        'test was expected to fail but passed',
+        kExpectedFailure,
+      );
+      return;
+    }
     if (this.error !== null) {
       return;
     }

filename: test/parallel/test-runner-expect-error-but-pass.js
patch: @@ -0,0 +1,18 @@
+'use strict';
+const common = require('../common');
+const assert = require('node:assert');
+const { run, test } = require('node:test');
+
+if (!process.env.NODE_TEST_CONTEXT) {
+  const stream = run({ files: [__filename] });
+
+  stream.on('test:pass', common.mustNotCall());
+  stream.on('test:fail', common.mustCall((event) => {
+    assert.strictEqual(event.expectFailure, true);
+    assert.strictEqual(event.details.error.code, 'ERR_TEST_FAILURE');
+    assert.strictEqual(event.details.error.failureType, 'expectedFailure');
+    assert.strictEqual(event.details.error.cause, 'test was expected to fail but passed');
+  }, 1));
+} else {
+  test('passing test', { expectFailure: true }, () => {});
+}

filename: test/parallel/test-runner-expect-error.js
patch: @@ -0,0 +1,15 @@
+'use strict';
+const common = require('../common');
+const assert = require('node:assert');
+const { run, test } = require('node:test');
+
+if (!process.env.NODE_TEST_CONTEXT) {
+  const stream = run({ files: [__filename] });
+
+  stream.on('test:fail', common.mustNotCall());
+  stream.on('test:pass', common.mustCall((event) => {
+    assert.strictEqual(event.expectFailure, true);
+  }, 1));
+} else {
+  test('failing test', { expectFailure: true }, () => assert.fail('should not pass'));
+}
Repository: ollama/ollama
Pull request: Add TinyNotepad to README.md

This PR adds Tiny Notepad, a lightweight, notepad-like interface to chat with local LLMs via Ollama. 

- It’s designed as a simple, distraction-free alternative. 
- The app supports basic note-taking, timestamped logs, and model parameter controls. 
- Built with Tkinter, it runs entirely offline and available via PyPI.

Aims to provide a lightweight easy to run and install interface for ollama.

Changed files:
filename: README.md
patch: @@ -405,6 +405,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Writeopia](https://github.com/Writeopia/Writeopia) (Text editor with integration with Ollama)
 - [AppFlowy](https://github.com/AppFlowy-IO/AppFlowy) (AI collaborative workspace with Ollama, cross-platform and self-hostable)
 - [Lumina](https://github.com/cushydigit/lumina.git) (A lightweight, minimal React.js frontend for interacting with Ollama servers)
+- [Tiny Notepad](https://pypi.org/project/tiny-notepad) (A lightweight, notepad-like interface to chat with ollama available on PyPI)
 
 ### Cloud
Repository: vuejs/vue
Pull request: fix(types): add types for `Vue.util.warn` function

<!--
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)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**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
- [ ] 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:** See https://github.com/vuejs/vue/blob/v2.6.12/src/core/util/debug.js#L18-L26


Changed files:
filename: types/vue.d.ts
patch: @@ -121,6 +121,10 @@ export interface VueConstructor<V extends Vue = Vue> {
 
   observable<T>(obj: T): T;
 
+  util: {
+    warn(msg: string, vm?: InstanceType<VueConstructor>): void;
+  };
+
   config: VueConfiguration;
   version: string;
 }
Repository: ollama/ollama
Pull request: remove special case for gemma3 special vocab

this isn't necessary anymore since the model has these tokens set correctly as special tokens. this may negatively impact other models where 105 and 106 are regular tokens

Changed files:
filename: model/vocabulary.go
patch: @@ -87,9 +87,7 @@ func (v *Vocabulary) Decode(id int32) string {
 func (v *Vocabulary) SpecialVocabulary() []string {
 	v.specialOnce.Do(func() {
 		for i := range v.Values {
-			if slices.Contains([]int{105, 106}, i) {
-				v.special = append(v.special, v.Values[i])
-			} else if v.Types[i] == TOKEN_TYPE_CONTROL {
+			if v.Types[i] == TOKEN_TYPE_CONTROL {
 				v.special = append(v.special, v.Values[i])
 			}
 		}
Repository: facebook/react
Pull request: [DevTools] Always skip 1 frame

Follow up to #34093.

There's an issue where the skipFrames argument isn't part of the cache key so the other parsers that expect skipping one frame might skip zero and show the internal `fakeJSXDEV` callsite. Ideally we should include the skipFrames as part of the cache key but we can also always just skip one.


Changed files:
filename: packages/react-devtools-shared/src/backend/utils/parseStackTrace.js
patch: @@ -284,7 +284,7 @@ export function parseStackTrace(
 export function extractLocationFromOwnerStack(
   error: Error,
 ): ReactFunctionLocation | null {
-  const stackTrace = parseStackTrace(error, 0);
+  const stackTrace = parseStackTrace(error, 1);
   const stack = error.stack;
   if (
     !stack.includes('react_stack_bottom_frame') &&
Repository: vercel/next.js
Pull request: Skip Server Function logging for `'use cache'` functions

Follow-up to #89407.

Disables Server Function logging for `'use cache'` functions called from the client.

The logging output for these Server Functions needs more work to be useful. Currently it shows internal details like `$$RSC_SERVER_CACHE_0` instead of the actual function name, as well as the encoded bound args promise.

Changed files:
filename: packages/next/src/server/app-render/action-handler.ts
patch: @@ -58,6 +58,7 @@ import {
 } from './manifests-singleton'
 import { isNodeNextRequest, isWebNextRequest } from '../base-http/helpers'
 import { normalizeFilePath } from './segment-explorer-path'
+import { extractInfoFromServerReferenceId } from '../../shared/lib/server-reference-info'
 import type { ServerActionLogInfo } from '../dev/server-action-logger'
 import { RedirectStatusCode } from '../../client/components/redirect-status-code'
 import { synchronizeMutableCookies } from '../async-storage/request-store'
@@ -1086,9 +1087,13 @@ export async function handleAction({
 
         // Log server action call in development when enabled
         let logInfo: ServerActionLogInfo | null = null
+        const { type: actionType } = extractInfoFromServerReferenceId(actionId!)
         if (
           process.env.NODE_ENV === 'development' &&
-          ctx.renderOpts.logServerFunctions
+          ctx.renderOpts.logServerFunctions &&
+          // TODO: For now, skip logging for 'use cache' Server Functions as the
+          // output needs more work, or a different approach entirely.
+          actionType !== 'use-cache'
         ) {
           const serverActionsManifest = getServerActionsManifest()
           const runtime = process.env.NEXT_RUNTIME === 'edge' ? 'edge' : 'node'

filename: test/e2e/app-dir/use-cache/use-cache.test.ts
patch: @@ -1419,6 +1419,22 @@ describe('use-cache', () => {
     const numbers = await browser.elementById('numbers').text()
     expect(numbers).toBe(initialNumbers)
   })
+
+  if (isNextDev) {
+    it('should not log "use cache" functions called from client', async () => {
+      const browser = await next.browser('/passed-to-client')
+      const outputIndex = next.cliOutput.length
+
+      await browser.elementByCss('#submit-button').click()
+
+      await retry(() => {
+        const logs = stripAnsi(next.cliOutput.slice(outputIndex))
+        // Should have the POST request but not the function log
+        expect(logs).toContain('POST /passed-to-client')
+        expect(logs).not.toContain('└─ ƒ')
+      })
+    })
+  }
 })
 
 async function getSanitizedLogs(browser: Playwright): Promise<string[]> {
Repository: ollama/ollama
Pull request: Fix lingering Q4_0 help reference


Changed files:
filename: cmd/cmd.go
patch: @@ -1318,7 +1318,7 @@ func NewCLI() *cobra.Command {
 	}
 
 	createCmd.Flags().StringP("file", "f", "", "Name of the Modelfile (default \"Modelfile\"")
-	createCmd.Flags().StringP("quantize", "q", "", "Quantize model to this level (e.g. q4_0)")
+	createCmd.Flags().StringP("quantize", "q", "", "Quantize model to this level (e.g. q4_K_M)")
 
 	showCmd := &cobra.Command{
 		Use:     "show MODEL",
Repository: nodejs/node
Pull request: sqlite: fix segfault SQLTagStore when db handle is garbage collected

Fixes https://github.com/nodejs/node/issues/60448 by changing from a `BaseObjectWeakPtr` to a `BaseObjectPtr`.

A SQLTagStore should keep the database alive.

Changed files:
filename: src/node_sqlite.cc
patch: @@ -2819,6 +2819,7 @@ BaseObjectPtr<SQLTagStore> SQLTagStore::Create(
            .ToLocal(&obj)) {
     return nullptr;
   }
+  obj->SetInternalField(kDatabaseObject, database->object());
   return MakeBaseObject<SQLTagStore>(env, obj, std::move(database), capacity);
 }
 
@@ -2829,9 +2830,8 @@ void SQLTagStore::CapacityGetter(const FunctionCallbackInfo<Value>& args) {
 }
 
 void SQLTagStore::DatabaseGetter(const FunctionCallbackInfo<Value>& args) {
-  SQLTagStore* store;
-  ASSIGN_OR_RETURN_UNWRAP(&store, args.This());
-  args.GetReturnValue().Set(store->database_->object());
+  args.GetReturnValue().Set(
+      args.This()->GetInternalField(kDatabaseObject).As<Value>());
 }
 
 void SQLTagStore::SizeGetter(const FunctionCallbackInfo<Value>& args) {

filename: src/node_sqlite.h
patch: @@ -305,6 +305,11 @@ class Session : public BaseObject {
 
 class SQLTagStore : public BaseObject {
  public:
+  enum InternalFields {
+    kDatabaseObject = BaseObject::kInternalFieldCount,
+    kInternalFieldCount
+  };
+
   SQLTagStore(Environment* env,
               v8::Local<v8::Object> object,
               BaseObjectWeakPtr<DatabaseSync> database,

filename: test/parallel/test-sqlite-template-tag.js
patch: @@ -1,4 +1,6 @@
 'use strict';
+// Flags: --expose-gc
+
 const { skipIfSQLiteMissing } = require('../common');
 skipIfSQLiteMissing();
 
@@ -135,3 +137,35 @@ test('sql error messages are descriptive', () => {
     message: /no such table/i,
   });
 });
+
+test('a tag store keeps the database alive by itself', () => {
+  const sql = new DatabaseSync(':memory:').createTagStore();
+
+  sql.db.exec('CREATE TABLE test (data INTEGER)');
+
+  global.gc();
+
+  // eslint-disable-next-line no-unused-expressions
+  sql.run`INSERT INTO test (data) VALUES (1)`;
+});
+
+test('tag store prevents circular reference leaks', async () => {
+  const { gcUntil } = require('../common/gc');
+
+  const before = process.memoryUsage().heapUsed;
+
+  // Create many SQLTagStore + DatabaseSync pairs with circular references
+  for (let i = 0; i < 1000; i++) {
+    const sql = new DatabaseSync(':memory:').createTagStore();
+    sql.db.exec('CREATE TABLE test (data INTEGER)');
+    // eslint-disable-next-line no-void
+    sql.db.setAuthorizer(() => void sql.db);
+  }
+
+  // GC until memory stabilizes or give up after 20 attempts
+  await gcUntil('tag store leak check', () => {
+    const after = process.memoryUsage().heapUsed;
+    // Memory should not grow significantly (allow 50% margin for noise)
+    return after < before * 1.5;
+  }, 20);
+});
Repository: vuejs/vue
Pull request: fix: pause dep collection during immediate watcher invocation

Close #11942
<!--
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)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe: **Performance improvement**

**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
- [x] 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
- [ ] 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:**


Changed files:
filename: src/core/instance/state.js
patch: @@ -355,11 +355,13 @@ export function stateMixin (Vue: Class<Component>) {
     options.user = true
     const watcher = new Watcher(vm, expOrFn, cb, options)
     if (options.immediate) {
+      pushTarget()
       try {
         cb.call(vm, watcher.value)
       } catch (error) {
         handleError(error, vm, `callback for immediate watcher "${watcher.expression}"`)
       }
+      popTarget()
     }
     return function unwatchFn () {
       watcher.teardown()

filename: test/unit/features/instance/methods-lifecycle.spec.js
patch: @@ -53,6 +53,38 @@ describe('Instance methods lifecycle', () => {
         }
       }).$mount()
     })
+
+    it('Dep.target should be undefined during invocation of child immediate watcher', done => {
+      let calls = 0
+      const childData = { a: 1 }
+      const parentUpdate = jasmine.createSpy()
+      new Vue({
+        template: '<div><my-component></my-component></div>',
+        updated: parentUpdate,
+        components: {
+          myComponent: {
+            template: '<div>{{ a }}</div>',
+            data() {
+              return childData
+            },
+            watch: {
+              anything: {
+                handler() {
+                  ++calls
+                  this.a
+                },
+                immediate: true
+              }
+            }
+          }
+        }
+      }).$mount()
+      expect(calls).toBe(1)
+      childData.a++
+      waitForUpdate(() => {
+        expect(parentUpdate).not.toHaveBeenCalled()
+      }).then(done)
+    })
   })
 
   describe('$destroy', () => {
Repository: vercel/next.js
Pull request: Revert "Fix/zlib mem node"

Reverts vercel/next.js#89099

Apparently this did not solve the other user's memory leak issue: https://github.com/vercel/next.js/issues/89091#issuecomment-3826050800

Changed files:
filename: packages/next/src/server/lib/router-server.ts
patch: @@ -262,12 +262,6 @@ export async function initialize(opts: {
     if (compress) {
       // @ts-expect-error not express req/res
       compress(req, res, () => {})
-
-      // Only on client abort: destroy response so compression streams are cleaned up
-      req.once('aborted', () => {
-        if (res.destroyed || res.writableFinished) return
-        res.destroy()
-      })
     }
     req.on('error', (_err) => {
       // TODO: log socket errors?
Repository: huggingface/transformers
Pull request: Fix `process_bad_commit_report.py`: avoid items to appear in `null` author in the report

# What does this PR do?

The file `utils/process_bad_commit_report.py` tried to get a team member to ping on slack, including someone merged a PR despite they are not the author of that PR.

However, that part was written before we have PR comment CI. After this is implemented, we might have "merged_by" being `None` (i.e. `null`) for a PR comment CI.

The previous condition (before this PR)

> failed_tests = [x for x in failed_tests if x["author"] == author or x["merged_by"] == author]

gave confusing results: 

https://huggingface.co/datasets/hf-internal-testing/transformers_pr_ci/blob/main/2026-01-31/runs/27920-21546006888/ci_results_run_models_gpu/new_failures_with_bad_commit_grouped_by_authors.json

(where some items with `author`, so not flaky ones, appeared in 2 top level keys with one being `null` - coming from the fact of  `x["merged_by"] being null`).

v.s.

https://huggingface.co/datasets/hf-internal-testing/transformers_pr_ci/blob/main/2026-01-31/runs/27924-21550696166/ci_results_run_models_gpu/new_failures_with_bad_commit_grouped_by_authors.json

This PR fixes this confusing.

Changed files:
filename: utils/process_bad_commit_report.py
patch: @@ -105,7 +105,8 @@
             for failed_test in failed_tests:
                 author = failed_test["author"]
 
-                if author not in team_members:
+                # If author is not a team member, and the PR is already merged: change to the one who merged the PR
+                if author not in team_members and failed_test["merged_by"] is not None:
                     author = failed_test["merged_by"]
 
                 if author not in new_data:
@@ -119,7 +120,11 @@
     for author, _data in new_data_full.items():
         for model, model_result in _data.items():
             for device, failed_tests in model_result.items():
-                failed_tests = [x for x in failed_tests if x["author"] == author or x["merged_by"] == author]
+                failed_tests = [
+                    x
+                    for x in failed_tests
+                    if x["author"] == author or (x["merged_by"] is not None and x["merged_by"] == author)
+                ]
                 model_result[device] = failed_tests
             _data[model] = {k: v for k, v in model_result.items() if len(v) > 0}
         new_data_full[author] = {k: v for k, v in _data.items() if len(v) > 0}
Repository: huggingface/transformers
Pull request: Fix `KeyError` in `check_bad_commit.py`

# What does this PR do?

The PR #43628 changed a bit the format of `new_failures.json` and causes the `check_bad_commit.py` may fail.

("single-gpu" is no longer guaranteed to be in the dict)

Changed files:
filename: utils/check_bad_commit.py
patch: @@ -279,7 +279,7 @@ def get_commit_info(commit, pr_number=None):
 
             # TODO: make this script able to deal with both `single-gpu` and `multi-gpu` via a new argument.
             reports[model].pop("multi-gpu", None)
-            failed_tests = reports[model]["single-gpu"]
+            failed_tests = reports[model].get("single-gpu", [])
 
             failed_tests_with_bad_commits = []
             for failure in failed_tests:
Repository: nodejs/node
Pull request: win,tools: use Azure Trusted Signing

This PR finalizes the work on the new signing tool, Azure Trusted Signing. As discussed in [the build issue](https://github.com/nodejs/build/issues/4036), the release CI was set up to work with new tools, and this change moves to using them when building Node.

When this PR lands, the same changes should be applied to all the LTS branches, as they are still released and signed.

cc @nodejs/build 

Refs: https://github.com/nodejs/build/issues/4036

Changed files:
filename: tools/sign.bat
patch: @@ -1,12 +1,29 @@
 @echo off
 
-@REM From December 2023, new certificates use DigiCert cloud HSM service for EV signing.
-@REM They provide a client side app smctl.exe for managing certificates and signing process.
+@REM From June 2025, we started using Azure Trusted Signing for code signing.
 @REM Release CI machines are configured to have it in the PATH so this can be used safely.
-smctl sign -k key_nodejs -i %1
+
+where signtool >nul 2>&1
+if errorlevel 1 (
+    echo signtool not found in PATH.
+    exit /b 1
+)
+
+if "%AZURE_SIGN_DLIB_PATH%"=="" (
+    echo AZURE_SIGN_DLIB_PATH is not set.
+    exit /b 1
+)
+
+if "%AZURE_SIGN_METADATA_PATH%"=="" (
+    echo AZURE_SIGN_METADATA_PATH is not set.
+    exit /b 1
+)
+
+
+signtool sign /tr "http://timestamp.acs.microsoft.com" /td sha256 /fd sha256 /v /dlib %AZURE_SIGN_DLIB_PATH% /dmdf %AZURE_SIGN_METADATA_PATH% %1
 if not ERRORLEVEL 1 (
-    echo Successfully signed %1 using smctl
+    echo Successfully signed %1 using signtool
     exit /b 0
 )
-echo Could not sign %1 using smctl
+echo Could not sign %1 using signtool
 exit /b 1
\ No newline at end of file