helloadhavan/github_issues huggingface dataset:
Repository: huggingface/transformers
Pull request: Removing extra space in large command for speech-pretraining example

# What does this PR do?

<!--
Adding quotes to the large run command for the speech pretraining example, since it was not being run while copying and pasting. 
-->


## Before submitting
- [✅] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [✅] 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?

cc:
@ArthurZucker


Changed files:
filename: examples/pytorch/speech-pretraining/README.md
patch: @@ -129,7 +129,7 @@ To pre-train `"large-sized"` Wav2Vec2 model, *e.g.* [facebook/wav2vec2-large-lv6
 on [librispeech_asr](https://huggingface.co/datasets/librispeech_asr), the following command can be run:
 
 ```bash
-accelerate launch run_wav2vec2_pretraining_no_trainer.py \ 
+accelerate launch run_wav2vec2_pretraining_no_trainer.py \
 	--dataset_name=librispeech_asr \
 	--dataset_config_names clean clean other \
 	--dataset_split_names train.100 train.360 train.500 \
@@ -141,7 +141,7 @@ accelerate launch run_wav2vec2_pretraining_no_trainer.py \
 	--weight_decay=0.01 \
 	--max_duration_in_seconds=20.0 \
 	--min_duration_in_seconds=2.0 \
-	--model_name_or_path=./ 
+	--model_name_or_path=./ \
 	--logging_steps=1 \
 	--saving_steps=10000 \
 	--per_device_train_batch_size=2 \
Repository: ggml-org/llama.cpp
Pull request: llama.swiftui : add "Done" dismiss button to help view

The commit updates the help view in the llama.swiftui example to use a NavigationView and a Done button to dismiss the help view.

The motivation for this is that without this change there is now way to dimiss the help view.

Changed files:
filename: examples/llama.swiftui/llama.swiftui/UI/ContentView.swift
patch: @@ -124,15 +124,26 @@ struct ContentView: View {
                     }
                 }
             }.sheet(isPresented: $showingHelp) {    // Sheet for help modal
-                VStack(alignment: .leading) {
+                NavigationView {
                     VStack(alignment: .leading) {
-                        Text("1. Make sure the model is in GGUF Format")
-                               .padding()
-                        Text("2. Copy the download link of the quantized model")
-                               .padding()
+                        VStack(alignment: .leading) {
+                            Text("1. Make sure the model is in GGUF Format")
+                                    .padding()
+                            Text("2. Copy the download link of the quantized model")
+                                    .padding()
+                        }
+                        Spacer()
+                    }
+                    .navigationTitle("Help")
+                    .navigationBarTitleDisplayMode(.inline)
+                    .toolbar {
+                        ToolbarItem(placement: .navigationBarTrailing) {
+                            Button("Done") {
+                                showingHelp = false
+                            }
+                        }
                     }
-                    Spacer()
-                   }
+                }
             }
         }
     }
Repository: denoland/deno
Pull request: feat(unstable): add `lint.plugins` to config schema

Not sure what our handling of unstable properties in `deno.json` is. This PR adds it to the config schema.

Changed files:
filename: cli/schemas/config-file.v1.json
patch: @@ -292,6 +292,13 @@
             "type": "string"
           }
         },
+        "plugins": {
+          "type": "array",
+          "description": "UNSTABLE: List of plugins to load. These can be paths, npm or jsr specifiers",
+          "items": {
+            "type": "string"
+          }
+        },
         "rules": {
           "type": "object",
           "properties": {
Repository: electron/electron
Pull request: fix: restore performance of macOS window resizing

As in title, technically an upstream of a discord downstream patch --> https://github.com/discord/electron/commit/a712b6607e77c55b77aa8884e191a00001a697c5

Fixes an ongoing perf issue with window resizing on macOS by reverting an android-only fix in Chromium

Notes: Fixed resizing performance issue on macOS

Changed files:
filename: patches/chromium/.patches
patch: @@ -128,3 +128,4 @@ revert_remove_the_allowaggressivethrottlingwithwebsocket_feature.patch
 fix_activate_background_material_on_windows.patch
 feat_allow_passing_of_objecttemplate_to_objecttemplatebuilder.patch
 chore_remove_check_is_test_on_script_injection_tracker.patch
+fix_restore_original_resize_performance_on_macos.patch

filename: patches/chromium/fix_restore_original_resize_performance_on_macos.patch
patch: @@ -0,0 +1,25 @@
+From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
+From: Samuel Attard <marshallofsound@electronjs.org>
+Date: Tue, 21 Nov 2023 15:03:21 -0800
+Subject: fix: restore original resize performance on macOS
+
+Reverts https://chromium-review.googlesource.com/c/chromium/src/+/3118293 which
+fixed a android only regression but in the process regressed electron window
+resize perf wildly on macOS.
+
+diff --git a/content/browser/renderer_host/render_widget_host_impl.cc b/content/browser/renderer_host/render_widget_host_impl.cc
+index 749ee4641462aec1142f75de9f0459d7e7cf322f..4dcee366b8bd43add1f7e1dbedaf73403dd944cd 100644
+--- a/content/browser/renderer_host/render_widget_host_impl.cc
++++ b/content/browser/renderer_host/render_widget_host_impl.cc
+@@ -2205,9 +2205,8 @@ RenderWidgetHostImpl::GetWidgetInputHandler() {
+ void RenderWidgetHostImpl::NotifyScreenInfoChanged() {
+   // The resize message (which may not happen immediately) will carry with it
+   // the screen info as well as the new size (if the screen has changed scale
+-  // factor). Force sending the new visual properties even if there is one in
+-  // flight to ensure proper IPC ordering for features like the Fullscreen API.
+-  SynchronizeVisualPropertiesIgnoringPendingAck();
++  // factor).
++  SynchronizeVisualProperties();
+ 
+   // The device scale factor will be same for all the views contained by the
+   // primary main frame, so just set it once.
Repository: ggml-org/llama.cpp
Pull request: llama : fix typo in llama_tensor_get_type comment [no ci]


- [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: src/llama.cpp
patch: @@ -15304,7 +15304,7 @@ static ggml_type llama_tensor_get_type(quantize_state_internal & qs, ggml_type n
     const int n_expert = std::max(1, (int)qs.model.hparams.n_expert);
     auto layer_info = [n_expert] (int i_layer, int n_layer, const char * name) {
         if (n_expert > 1) {
-            // Believe it or not, "experts" in the FFN of Mixtral-8x7B are not consecutive, but iccasionally randomly
+            // Believe it or not, "experts" in the FFN of Mixtral-8x7B are not consecutive, but occasionally randomly
             // sprinkled in the model. Hence, simply dividing i_ffn_down by n_expert does not work
             // for getting the current layer as I initially thought, and we need to resort to parsing the
             // tensor name.
Repository: denoland/deno
Pull request: fix(ext/node): expose sqlite changeset constants

https://nodejs.org/api/sqlite.html#sqliteconstants



Changed files:
filename: ext/node/polyfills/sqlite.ts
patch: @@ -2,8 +2,21 @@
 
 import { DatabaseSync } from "ext:core/ops";
 
+export const constants = {
+  SQLITE_CHANGESET_OMIT: 0,
+  SQLITE_CHANGESET_REPLACE: 1,
+  SQLITE_CHANGESET_ABORT: 2,
+
+  SQLITE_CHANGESET_DATA: 1,
+  SQLITE_CHANGESET_NOTFOUND: 2,
+  SQLITE_CHANGESET_CONFLICT: 3,
+  SQLITE_CHANGESET_CONSTRAINT: 4,
+  SQLITE_CHANGESET_FOREIGN_KEY: 5,
+};
+
 export { DatabaseSync };
 
 export default {
+  constants,
   DatabaseSync,
 };

filename: tests/unit_node/sqlite_test.ts
patch: @@ -1,5 +1,5 @@
 // Copyright 2018-2025 the Deno authors. MIT license.
-import { DatabaseSync } from "node:sqlite";
+import sqlite, { DatabaseSync } from "node:sqlite";
 import { assert, assertEquals, assertThrows } from "@std/assert";
 
 const tempDir = Deno.makeTempDirSync();
@@ -173,9 +173,9 @@ Deno.test("[node/sqlite] applyChangeset across databases", () => {
 
   const changeset = session.changeset();
   targetDb.applyChangeset(changeset, {
-    filter(e) {
-      return e === "data";
-    },
+    filter: (e) => e === "data",
+    // @ts-ignore: types are not up to date
+    onConflict: () => sqlite.constants.SQLITE_CHANGESET_ABORT,
   });
 
   const stmt = targetDb.prepare("SELECT * FROM data");
Repository: ggml-org/llama.cpp
Pull request: common : add llama.vim preset for Qwen2.5 Coder

This commit adds a preset for llama.vim to use the default Qwen 2.5 Coder models.
    
The motivation for this change is to make it easier to start a server
suitable to be used with the llama.vim plugin. For example, the server
can be started with a command like the following:
```console
$ llama.vim --fim-qwen-1.5b-default
```

Refs: https://github.com/ggml-org/llama.cpp/issues/10932

Changed files:
filename: common/arg.cpp
patch: @@ -2502,5 +2502,53 @@ common_params_context common_params_parser_init(common_params & params, llama_ex
         }
     ).set_examples({LLAMA_EXAMPLE_EMBEDDING, LLAMA_EXAMPLE_SERVER}));
 
+    add_opt(common_arg(
+        {"--fim-qwen-1.5b-default"},
+        string_format("use default Qwen 2.5 Coder 1.5B (note: can download weights from the internet)"),
+        [](common_params & params) {
+            params.hf_repo = "ggml-org/Qwen2.5-Coder-1.5B-Q8_0-GGUF";
+            params.hf_file = "qwen2.5-coder-1.5b-q8_0.gguf";
+            params.port = 8012;
+            params.n_gpu_layers = 99;
+            params.flash_attn = true;
+            params.n_ubatch = 1024;
+            params.n_batch = 1024;
+            params.n_ctx = 0;
+            params.n_cache_reuse = 256;
+        }
+    ).set_examples({LLAMA_EXAMPLE_SERVER}));
+
+    add_opt(common_arg(
+        {"--fim-qwen-3b-default"},
+        string_format("use default Qwen 2.5 Coder 3B (note: can download weights from the internet)"),
+        [](common_params & params) {
+            params.hf_repo = "ggml-org/Qwen2.5-Coder-3B-Q8_0-GGUF";
+            params.hf_file = "qwen2.5-coder-3b-q8_0.gguf";
+            params.port = 8012;
+            params.n_gpu_layers = 99;
+            params.flash_attn = true;
+            params.n_ubatch = 1024;
+            params.n_batch = 1024;
+            params.n_ctx = 0;
+            params.n_cache_reuse = 256;
+        }
+    ).set_examples({LLAMA_EXAMPLE_SERVER}));
+
+    add_opt(common_arg(
+        {"--fim-qwen-7b-default"},
+        string_format("use default Qwen 2.5 Coder 7B (note: can download weights from the internet)"),
+        [](common_params & params) {
+            params.hf_repo = "ggml-org/Qwen2.5-Coder-7B-Q8_0-GGUF";
+            params.hf_file = "qwen2.5-coder-7b-q8_0.gguf";
+            params.port = 8012;
+            params.n_gpu_layers = 99;
+            params.flash_attn = true;
+            params.n_ubatch = 1024;
+            params.n_batch = 1024;
+            params.n_ctx = 0;
+            params.n_cache_reuse = 256;
+        }
+    ).set_examples({LLAMA_EXAMPLE_SERVER}));
+
     return ctx_arg;
 }
Repository: facebook/react
Pull request: Use content hash for react-native builds

Any commit in React creates an internal RN sync. This PR adds a check to see if a commit makes any change to the renderer and skips the commit. Mostly copies logic from https://github.com/facebook/react/pull/26331

Changed files:
filename: .github/workflows/commit_artifacts.yml
patch: @@ -228,7 +228,16 @@ jobs:
           name: compiled-rn
           path: compiled-rn/
       - run: git status -u
+      - name: Check if only the REVISION file has changed
+        id: check_should_commit
+        run: |
+          if git status --porcelain | grep -qv '/REVISION$'; then
+            echo "should_commit=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "should_commit=false" >> "$GITHUB_OUTPUT"
+          fi
       - name: Commit changes to branch
+        if: steps.check_should_commit.outputs.should_commit == 'true'
         uses: stefanzweifel/git-auto-commit-action@v4
         with:
           commit_message: |

filename: scripts/rollup/build-all-release-channels.js
patch: @@ -177,6 +177,26 @@ function processStable(buildDir) {
     );
   }
 
+  const reactNativeBuildDir = buildDir + '/react-native/implementations/';
+  if (fs.existsSync(reactNativeBuildDir)) {
+    const hash = crypto.createHash('sha1');
+    for (const fileName of fs.readdirSync(reactNativeBuildDir).sort()) {
+      const filePath = reactNativeBuildDir + fileName;
+      const stats = fs.statSync(filePath);
+      if (!stats.isDirectory()) {
+        hash.update(fs.readFileSync(filePath));
+      }
+    }
+    updatePlaceholderReactVersionInCompiledArtifacts(
+      reactNativeBuildDir,
+      ReactVersion +
+        '-' +
+        nextChannelLabel +
+        '-' +
+        hash.digest('hex').slice(0, 8)
+    );
+  }
+
   // Update remaining placeholders with next channel version
   updatePlaceholderReactVersionInCompiledArtifacts(
     buildDir,
Repository: ggml-org/llama.cpp
Pull request: llama : add early return for empty range

This commit adds an early return to the llama_kv_cache_seq_add and llama_kv_cache_seq_div functions.

The motivation for adding this is to avoid looping over the cache when the range is empty. I ran into this when using the self-extend feature in main.cpp.



- [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: src/llama.cpp
patch: @@ -3260,6 +3260,8 @@ static void llama_kv_cache_seq_add(
 
     if (p0 < 0) p0 = 0;
     if (p1 < 0) p1 = std::numeric_limits<llama_pos>::max();
+    // If there is no range then return early to avoid looping over the cache.
+    if (p0 == p1) return;
 
     if (cache.recurrent) {
         // for Mamba-like models, only the pos needs to be shifted
@@ -3304,6 +3306,8 @@ static void llama_kv_cache_seq_div(
                           int   d) {
     if (p0 < 0) p0 = 0;
     if (p1 < 0) p1 = std::numeric_limits<llama_pos>::max();
+    // If there is no range then return early to avoid looping over the cache.
+    if (p0 == p1) return;
 
     if (cache.recurrent) {
         // for Mamba-like models, only the pos needs to be changed
Repository: ggml-org/llama.cpp
Pull request: llama : suppress conversion from 'size_t' to 'int'

This commit updates llm_tokenizer_spm.tokenize to suppress/remove the following warnings that are generated on Windows when using MSVC:

```console
src\llama-vocab.cpp(211,1): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
src\llama-vocab.cpp(517,1): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
```

This is done by adding a cast for the size_t returned from symbols.size(). I believe this is safe as it seems unlikely that symbols, which stores an entry for each UTF8 character, would become larger than INT_MAX.

The motivation for this change is to reduce the number of warnings that are currently generated when building on Windows.



- [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: src/llama-vocab.cpp
patch: @@ -221,7 +221,7 @@ struct llm_tokenizer_spm_session {
         }
 
         // seed the work queue with all possible 2-character tokens.
-        for (size_t i = 1; i < symbols.size(); ++i) {
+        for (int i = 1; i < (int) symbols.size(); ++i) {
             try_add_bigram(i - 1, i);
         }
 
@@ -563,7 +563,7 @@ struct llm_tokenizer_bpe_session {
                 index++;
                 symbols.emplace_back(sym);
             }
-            for (size_t i = 1; i < symbols.size(); ++i) {
+            for (int i = 1; i < (int) symbols.size(); ++i) {
                 add_new_bigram(i - 1, i);
             }
Repository: electron/electron
Pull request: build: update build tools to correct sha

#### Description of Change

- Followup to #44136.  That PR updated build tools to the SHA for https://github.com/electron/build-tools/pull/685, but it should instead point to the SHA of the merged commit, which is what this PR does.

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [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: <!-- 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 -->none


Changed files:
filename: .github/actions/install-build-tools/action.yml
patch: @@ -11,7 +11,7 @@ runs:
         git config --global core.autocrlf false
         git config --global branch.autosetuprebase always
       fi
-      export BUILD_TOOLS_SHA=bf2a839205d569be99e0b23ede5d8a0d5041a777
+      export BUILD_TOOLS_SHA=8246e57791b0af4ae5975eb96f09855f9269b1cd
       npm i -g @electron/build-tools
       e auto-update disable
       if [ "$(expr substr $(uname -s) 1 10)" == "MSYS_NT-10" ]; then
Repository: denoland/deno
Pull request: fix(ext/node): fix twitter-api-v2 compatibility

fixes #27847 

remaining:
- ~~write test~~ Added a test case in npm_smoke_test (internal)

Changed files:
filename: ext/node/polyfills/net.ts
patch: @@ -1168,6 +1168,7 @@ const pkgsNeedsSockInitWorkaround = [
   "@npmcli/agent",
   "npm-check-updates",
   "playwright-core",
+  "twitter-api-v2",
 ];
 
 /**
Repository: vercel/next.js
Pull request: fix: fixed merge driver output, does not expect debugging messages to output on stdout

The git merge driver does not expect debugging messages to output on stdout, and instead requires them to output on stderr. This changes the `console.log` to a `console.error` to account for this requirement.

Changed files:
filename: scripts/merge-errors-json/merge.mjs
patch: @@ -44,7 +44,7 @@ function main() {
     writeJsonSync(currentPath, merged)
 
     const addedCount = Object.keys(merged).length - Object.keys(current).length
-    console.log(
+    console.error(
       `merge-errors-json: added ${addedCount === 1 ? '1 new message' : `${addedCount} new messages`} to errors.json`
     )
     process.exit(0)
Repository: nodejs/node
Pull request: doc: mark type stripping as release candidate

Refs: https://github.com/nodejs/typescript/issues/24

The design of this feature is pretty much stable and we have just been working on bug fixing and aesthetic improvements like error messages.
There is 1 issue open right now, and not many issues opened in general so I feel pretty confident in marking this as release candidate

cc @nodejs/typescript 

Changed files:
filename: doc/api/cli.md
patch: @@ -1154,7 +1154,7 @@ This feature requires `--allow-worker` if used with the [Permission Model][].
 added: v22.7.0
 -->
 
-> Stability: 1.1 - Active development
+> Stability: 1.2 - Release candidate
 
 Enables the transformation of TypeScript-only syntax into JavaScript code.
 Implies `--enable-source-maps`.
@@ -1767,7 +1767,7 @@ changes:
     description: Type stripping is enabled by default.
 -->
 
-> Stability: 1.1 - Active development
+> Stability: 1.2 - Release candidate
 
 Disable experimental type-stripping for TypeScript files.
 For more information, see the [TypeScript type-stripping][] documentation.

filename: doc/api/module.md
patch: @@ -239,7 +239,7 @@ added:
   - v22.13.0
 -->
 
-> Stability: 1.1 - Active development
+> Stability: 1.2 - Release candidate
 
 * `code` {string} The code to strip type annotations from.
 * `options` {Object}

filename: doc/api/process.md
patch: @@ -2056,7 +2056,7 @@ added:
  - v22.10.0
 -->
 
-> Stability: 1.1 - Active development
+> Stability: 1.2 - Release candidate
 
 * {boolean|string}
 

filename: doc/api/typescript.md
patch: @@ -12,7 +12,7 @@ changes:
 
 <!--introduced_in=v22.6.0-->
 
-> Stability: 1.1 - Active development
+> Stability: 1.2 - Release candidate
 
 ## Enabling
Repository: ggml-org/llama.cpp
Pull request: tests : add _CRT_SECURE_NO_WARNINGS for WIN32

This commit adds the compile definition `_CRT_SECURE_NO_WARNINGS` to the root cmake subproject.

The motivation for this is that currently the following warnings are displayed when compiling the tests and common cmake subprojects:
```console
test-llama-grammar.cpp
C:\llama.cpp\src\.\llama.cpp(1406,77): warning C4996: 'strerror':
This function or variable may be unsafe. Consider using strerror_s
instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See
online help for details.
[C:\llama.cpp\build\tests\test-llama-grammar.vcxproj]
...
```

This compile definition is currently set for the `src` subproject and this change moves into the root cmake project so that it is applied to all cmake subprojects.



- [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: CMakeLists.txt
patch: @@ -42,6 +42,10 @@ endif()
 
 option(BUILD_SHARED_LIBS "build shared libraries" ${BUILD_SHARED_LIBS_DEFAULT})
 
+if (WIN32)
+    add_compile_definitions(_CRT_SECURE_NO_WARNINGS)
+endif()
+
 #
 # option list
 #

filename: src/CMakeLists.txt
patch: @@ -1,7 +1,5 @@
 # TODO: should not use this
 if (WIN32)
-    add_compile_definitions(_CRT_SECURE_NO_WARNINGS)
-
     if (BUILD_SHARED_LIBS)
         set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS ON)
     endif()