helloadhavan/github_issues huggingface dataset:
Repository: denoland/deno
Pull request: fix(cli): add `compilerOptions.lib` examples to config-file.v1.json

<!--
Before submitting a PR, please read https://docs.deno.com/runtime/manual/references/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label.
-->

closes #28222


Changed files:
filename: cli/schemas/config-file.v1.json
patch: @@ -111,7 +111,35 @@
           "uniqueItems": true,
           "default": ["deno.window"],
           "items": {
-            "type": "string"
+            "type": "string",
+            "examples": [
+              "deno.ns",
+              "deno.window",
+              "deno.worker",
+              "deno.unstable",
+              "dom",
+              "dom.iterable",
+              "dom.asynciterable",
+              "webworker",
+              "webworker.importscripts",
+              "webworker.iterable",
+              "webworker.asynciterable",
+              "scripthost",
+              "decorators",
+              "decorators.legacy",
+              "es5",
+              "es2015",
+              "es2016",
+              "es2017",
+              "es2018",
+              "es2019",
+              "es2020",
+              "es2021",
+              "es2022",
+              "es2023",
+              "es2024",
+              "esnext"
+            ]
           },
           "markdownDescription": "Specify a set of bundled library declaration files that describe the target runtime environment.\n\nSee more: https://www.typescriptlang.org/tsconfig#lib"
         },
Repository: denoland/deno
Pull request: fix(core): Fix `create_stack_trace` from empty trace

Fixes https://github.com/denoland/deno/issues/27849



Changed files:
filename: Cargo.lock
patch: @@ -1562,9 +1562,9 @@ dependencies = [
 
 [[package]]
 name = "deno_core"
-version = "0.333.0"
+version = "0.335.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "2e67f6f874401f3b8fb3e851743c40ee14014648db6685b233b34f783f6959e8"
+checksum = "f921d3e3274fa12b040142ef7b2c98fd8373efd740e033f1ae356339d92349d1"
 dependencies = [
  "anyhow",
  "az",
@@ -2197,9 +2197,9 @@ dependencies = [
 
 [[package]]
 name = "deno_ops"
-version = "0.209.0"
+version = "0.211.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "fbda741ba267a252bad86153d16c859c3a8e1b219b300a1b4f0a2632c0a465cf"
+checksum = "de6a2b9f8acd27eeaa544b76fcb6ebba2fca2cc611a9d283b0c4b9847b37f4e6"
 dependencies = [
  "indexmap 2.3.0",
  "proc-macro-rules",
@@ -7023,9 +7023,9 @@ dependencies = [
 
 [[package]]
 name = "serde_v8"
-version = "0.242.0"
+version = "0.244.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "aa9d64ec1fdc3316cb65ca60ccbb5a3a914f014ccb0b5f71fc9280506fd28247"
+checksum = "4d04ca228b7ff313e5abc358c434605aa8eb37e4e3d19e0929ecc591281649f0"
 dependencies = [
  "deno_error",
  "num-bigint",
@@ -8684,9 +8684,9 @@ dependencies = [
 
 [[package]]
 name = "v8"
-version = "130.0.7"
+version = "130.0.8"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "a511192602f7b435b0a241c1947aa743eb7717f20a9195f4b5e8ed1952e01db1"
+checksum = "be16314fd485983a2a2e001d90a959d6c7c3eb800a2f481b11104f76cd5608cd"
 dependencies = [
  "bindgen",
  "bitflags 2.6.0",

filename: Cargo.toml
patch: @@ -51,7 +51,7 @@ repository = "https://github.com/denoland/deno"
 
 [workspace.dependencies]
 deno_ast = { version = "=0.44.0", features = ["transpiling"] }
-deno_core = { version = "0.333.0" }
+deno_core = { version = "0.335.0" }
 
 deno_bench_util = { version = "0.181.0", path = "./bench_util" }
 deno_config = { version = "=0.47.1", features = ["workspace"] }
Repository: ggml-org/llama.cpp
Pull request: llama : update llama_decode_internal ref [no ci]

This commit updates the comment in llama_kv_cache.h to reflect the change of the function name from `llama_decode_internal` to `llama_decode_impl`.


Changed files:
filename: src/llama-kv-cache.h
patch: @@ -37,7 +37,7 @@ struct llama_kv_cache {
     bool can_shift = false;
 
     // Note: The value of head isn't only used to optimize searching
-    // for a free KV slot. llama_decode_internal also uses it, so it
+    // for a free KV slot. llama_decode_impl also uses it, so it
     // cannot be freely changed after a slot has been allocated.
     uint32_t head = 0;
     uint32_t size = 0;
Repository: electron/electron
Pull request: fix: `session.clearData` `avoidClosingConnections` default to false

#### Description of Change

Fixes #44853.

The `clearData` API uses `kClearDataTypeAll` when the `dataTypes` option is not set. This default value currently includes the `avoidClosingConnections` option, which contradicts that option's default value of `false`. This PR updates the default value (`kClearDataTypeAll`) to respect `avoidClosingConnections`'s default value of `false`.

#### Checklist

- [x] PR description included and stakeholders cc'd
- [x] `npm test` passes
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: The `avoidClosingConnections` option for `session.clearData` now properly defaults to `false` when the `dataTypes` option is not set.


Changed files:
filename: shell/browser/api/electron_api_session.cc
patch: @@ -160,7 +160,8 @@ uint32_t GetQuotaMask(const std::vector<std::string>& quota_types) {
   return quota_mask;
 }
 
-constexpr BrowsingDataRemover::DataType kClearDataTypeAll = ~0ULL;
+constexpr BrowsingDataRemover::DataType kClearDataTypeAll =
+    ~0ULL & ~BrowsingDataRemover::DATA_TYPE_AVOID_CLOSING_CONNECTIONS;
 constexpr BrowsingDataRemover::OriginType kClearOriginTypeAll =
     BrowsingDataRemover::ORIGIN_TYPE_UNPROTECTED_WEB |
     BrowsingDataRemover::ORIGIN_TYPE_PROTECTED_WEB;
Repository: vercel/next.js
Pull request: [devtools] overlay backdrop visibility hidden when not fullscreen

### Why?

The overlay backdrop covers the browser inspector in minimized mode.

Closes NEXT-4567

Changed files:
filename: packages/next/src/next-devtools/dev-overlay/components/devtools-panel/devtools-panel.tsx
patch: @@ -228,10 +228,12 @@ export const DEVTOOLS_PANEL_STYLES = css`
 
   [data-nextjs-devtools-panel-overlay-backdrop] {
     opacity: 0;
+    visibility: hidden;
   }
 
   [data-nextjs-devtools-panel-overlay-backdrop='true'] {
     opacity: 1;
+    visibility: visible;
   }
 
   [data-nextjs-devtools-panel-draggable] {
Repository: facebook/react
Pull request: fix: devtools cannot be closed correctly

<!--
  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 debug-test --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

Fix devtools cannot be shutdown by bridge.shutdown().

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

## How did you test this change?

<!--
  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: packages/react-devtools-shared/src/__tests__/bridge-test.js
patch: @@ -21,6 +21,8 @@ describe('Bridge', () => {
       send: jest.fn(),
     };
     const bridge = new Bridge(wall);
+    const shutdownCallback = jest.fn();
+    bridge.addListener('shutdown', shutdownCallback);
 
     // Check that we're wired up correctly.
     bridge.send('reloadAppForProfiling');
@@ -36,6 +38,7 @@ describe('Bridge', () => {
     expect(wall.send).toHaveBeenCalledWith('update', '1');
     expect(wall.send).toHaveBeenCalledWith('update', '2');
     expect(wall.send).toHaveBeenCalledWith('shutdown');
+    expect(shutdownCallback).toHaveBeenCalledTimes(1);
 
     // Verify that the Bridge doesn't send messages after shutdown.
     jest.spyOn(console, 'warn').mockImplementation(() => {});

filename: packages/react-devtools-shared/src/bridge.js
patch: @@ -334,6 +334,7 @@ class Bridge<
     }
 
     // Queue the shutdown outgoing message for subscribers.
+    this.emit('shutdown');
     this.send('shutdown');
 
     // Mark this bridge as destroyed, i.e. disable its public API.
Repository: electron/electron
Pull request: fix: `session.clearData` `avoidClosingConnections` default to false

Backport of #45187

See that PR for details.


Notes: The `avoidClosingConnections` option for `session.clearData` now properly defaults to `false` when the `dataTypes` option is not set.


Changed files:
filename: shell/browser/api/electron_api_session.cc
patch: @@ -160,7 +160,8 @@ uint32_t GetQuotaMask(const std::vector<std::string>& quota_types) {
   return quota_mask;
 }
 
-constexpr BrowsingDataRemover::DataType kClearDataTypeAll = ~0ULL;
+constexpr BrowsingDataRemover::DataType kClearDataTypeAll =
+    ~0ULL & ~BrowsingDataRemover::DATA_TYPE_AVOID_CLOSING_CONNECTIONS;
 constexpr BrowsingDataRemover::OriginType kClearOriginTypeAll =
     BrowsingDataRemover::ORIGIN_TYPE_UNPROTECTED_WEB |
     BrowsingDataRemover::ORIGIN_TYPE_PROTECTED_WEB;
Repository: ggml-org/llama.cpp
Pull request: ggml : suppress unknown pragma 'GCC' on windows

This commit adds a macro guard to pragma GCC to avoid the following warning on windows:

```console
C:\llama.cpp\ggml\src\ggml-aarch64.c(17,9): warning C4068:
unknown pragma 'GCC' [C:\lama.cpp\build\ggml\src\ggml.vcxproj]
```
----
Is it alright to open pull request for ggml in this repository or is it preferred to do so in the ggml repo?


- [x] I have read the [contributing guidelines](https://github.com/ggerganov/llama.cpp/blob/master/CONTRIBUTING.md)
- Self-reported review complexity:
  - [x] Low
  - [ ] Medium
  - [ ] High


Changed files:
filename: ggml/src/ggml-aarch64.c
patch: @@ -14,7 +14,9 @@
 
 #include "ggml-aarch64.h"
 
+#if defined(__GNUC__)
 #pragma GCC diagnostic ignored "-Woverlength-strings"
+#endif
 
 #define UNUSED GGML_UNUSED
Repository: nodejs/node
Pull request: tools: add release line label when opening release proposal

I had to add it manually in https://github.com/nodejs/node/pull/56310#event-15708312401, let's have the automation do it for us.

<!--
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: tools/actions/create-release.sh
patch: @@ -126,4 +126,4 @@ if (data.errors?.length) {
 console.log(util.inspect(data, { depth: Infinity }));
 EOF
 
-gh pr edit "$PR_URL" --add-label release --add-assignee "$RELEASER"
+gh pr edit "$PR_URL" --add-label release --add-label "v$RELEASE_LINE.x" --add-assignee "$RELEASER"
Repository: huggingface/transformers
Pull request: fix `test_compare_unprocessed_logit_scores`

# What does this PR do?

With #39016, this test

> tests/generation/test_utils.py::GenerationIntegrationTests::test_compare_unprocessed_logit_scores

is failing.

However, the difference is in the range of 1e-7

```
(Pdb) torch.amax(torch.abs(logits_fwd - logits_gen))
tensor(5.9605e-08, device='cuda:0')
```

The test was using `assertListEqual`  which is not good for float numbers.

Changed files:
filename: tests/generation/test_utils.py
patch: @@ -3807,7 +3807,7 @@ def test_compare_unprocessed_logit_scores(self):
         logits_gen = outputs.logits[0][0]
 
         # assert that unprocessed logits from generate() are same as those from modal eval()
-        self.assertListEqual(logits_fwd.tolist(), logits_gen.tolist())
+        torch.testing.assert_allclose(logits_fwd.tolist(), logits_gen.tolist())
 
     def test_return_unprocessed_logit_scores(self):
         # tell model to generate text and return unprocessed/unwarped logit scores
Repository: denoland/deno
Pull request: perf(install): only read initialized file if we care about the tags

Speeds up the caching part of this arbitrary `"nodeModulesDir": "auto"` project by about 22%

We write the tags associated with a given npm package to the `.initialized` file, so that byonm can correctly resolve tags. When setting up the node modules dir, we read that file to see if we need to update the tags.

If we don't have any tags associated with the package though, we can just check for existence (which is a fair bit faster than trying to `open` + `read` a file).

```
❯ hyperfine --warmup 3 "deno check src/**/*.ts" "../deno/target/release-lite/deno check src/**/*.ts"
Benchmark 1: deno check src/**/*.ts
  Time (mean ± σ):     369.9 ms ±   5.5 ms    [User: 286.9 ms, System: 128.9 ms]
  Range (min … max):   361.7 ms … 377.7 ms    10 runs

Benchmark 2: ../deno/target/release-lite/deno check src/**/*.ts
  Time (mean ± σ):     303.5 ms ±   5.9 ms    [User: 210.9 ms, System: 124.5 ms]
  Range (min … max):   292.7 ms … 315.0 ms    10 runs

Summary
  ../deno/target/release-lite/deno check src/**/*.ts ran
    1.22 ± 0.03 times faster than deno check src/**/*.ts
```

Changed files:
filename: cli/npm/installer/local.rs
patch: @@ -279,15 +279,23 @@ async fn sync_resolution_with_fs(
       TagsOutdated,
     }
     let initialized_file = folder_path.join(".initialized");
-    let package_state = std::fs::read_to_string(&initialized_file)
-      .map(|s| {
-        if s != tags {
-          PackageFolderState::TagsOutdated
-        } else {
-          PackageFolderState::UpToDate
-        }
-      })
-      .unwrap_or(PackageFolderState::Uninitialized);
+    let package_state = if tags.is_empty() {
+      if initialized_file.exists() {
+        PackageFolderState::UpToDate
+      } else {
+        PackageFolderState::Uninitialized
+      }
+    } else {
+      std::fs::read_to_string(&initialized_file)
+        .map(|s| {
+          if s != tags {
+            PackageFolderState::TagsOutdated
+          } else {
+            PackageFolderState::UpToDate
+          }
+        })
+        .unwrap_or(PackageFolderState::Uninitialized)
+    };
     if !cache
       .cache_setting()
       .should_use_for_npm_package(&package.id.nv.name)
Repository: vercel/next.js
Pull request: Turbopack builds: Remove canary-gate and add experimental warning

This:
- Removes the Turbopack build canary gate
- Adds a warning that Turbopack build support is experimental.
- Links to the discussion page for feedback

Test Plan: Installed and used in an app. Verified the link is valid.


Closes PACK-4261
Closes PACK-4122

Changed files:
filename: packages/next/src/build/index.ts
patch: @@ -3709,6 +3709,10 @@ export default async function build(
     // Ensure we wait for lockfile patching if present
     await lockfilePatchPromise.cur
 
+    if (isTurbopack && !process.env.__NEXT_TEST_MODE) {
+      warnAboutTurbopackBuilds(loadedConfig)
+    }
+
     // Ensure all traces are flushed before finishing the command
     await flushAllTraces()
     teardownTraceSubscriber()
@@ -3725,3 +3729,25 @@ export default async function build(
     }
   }
 }
+
+function warnAboutTurbopackBuilds(config?: NextConfigComplete) {
+  let warningStr =
+    `Support for Turbopack builds is experimental. ` +
+    bold(
+      `We don't recommend deploying mission-critical applications to production.`
+    )
+  warningStr +=
+    '\n\n- It is expected that your bundle size might be different from `next build` with webpack. This will be improved as we work towards stability.'
+
+  if (!config?.experimental.turbo?.unstablePersistentCaching) {
+    warningStr +=
+      '\n- This build is without disk caching; subsequent builds will become faster when disk caching becomes available.'
+  }
+
+  warningStr +=
+    '\n- When comparing output to webpack builds, make sure to first clear the Next.js cache by deleting the `.next` directory.'
+  warningStr +=
+    '\n\nProvide feedback for Turbopack builds at https://github.com/vercel/next.js/discussions/77721'
+
+  Log.warn(warningStr)
+}

filename: packages/next/src/build/turbopack-build/impl.ts
patch: @@ -19,19 +19,12 @@ import loadConfig from '../../server/config'
 import { hasCustomExportOutput } from '../../export/utils'
 import { Telemetry } from '../../telemetry/storage'
 import { setGlobal } from '../../trace'
-import { isStableBuild, CanaryOnlyError } from '../../shared/lib/canary-only'
 
 export async function turbopackBuild(): Promise<{
   duration: number
   buildTraceContext: undefined
   shutdownPromise: Promise<void>
 }> {
-  if (isStableBuild()) {
-    throw new CanaryOnlyError(
-      'Turbopack builds are only available in canary builds of Next.js.'
-    )
-  }
-
   await validateTurboNextConfig({
     dir: NextBuildContext.dir!,
     isDev: false,
Repository: vercel/next.js
Pull request: Turbopack Build: Fix metadata-edge test

This test is checking if `@vercel/og` gets shared between two routes, it assumed that `next/og` itself (the wrapper code) would also be chunked, but the size limit for Turbopack is slightly larger so it doesn't end up bundling it into a separate chunk. Changed the test to check that `@vercel/og` is correctly chunked.

Closes PACK-4880

Changed files:
filename: test/e2e/app-dir/metadata-edge/index.test.ts
patch: @@ -22,21 +22,26 @@ describe('app dir - Metadata API on the Edge runtime', () => {
           (file) => {
             return next
               .readFileSync(path.join('.next', file))
-              .includes('ImageResponse')
+              .includes('experimental_FigmaImageResponse')
           }
         )
+        expect(pageFilesThatHaveImageResponse).not.toBeEmpty()
 
         const uniqueAnotherFiles = [
           ...new Set<string>(
             middlewareManifest.functions['/another/page'].files
           ),
         ]
+        expect(uniqueAnotherFiles).not.toBeEmpty()
 
         const anotherFilesThatHaveImageResponse = uniqueAnotherFiles.filter(
           (file) => {
-            return next
-              .readFileSync(path.join('.next', file))
-              .includes('ImageResponse')
+            return (
+              next
+                .readFileSync(path.join('.next', file))
+                // This export is not used but it checks if the `@vercel/og` package is shared between the two routes.
+                .includes('experimental_FigmaImageResponse')
+            )
           }
         )
 

filename: test/turbopack-build-tests-manifest.json
patch: @@ -3045,11 +3045,10 @@
   },
   "test/e2e/app-dir/metadata-edge/index.test.ts": {
     "passed": [
-      "app dir - Metadata API on the Edge runtime should render OpenGraph image meta tag correctly"
-    ],
-    "failed": [
+      "app dir - Metadata API on the Edge runtime should render OpenGraph image meta tag correctly",
       "app dir - Metadata API on the Edge runtime OG image route should not bundle `ImageResponse` into the page worker"
     ],
+    "failed": [],
     "pending": [],
     "flakey": [],
     "runtimeError": false