helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: Change commit message for DiffTrain commigs

Previously, the commit message looked something like this in Github: 
<img width="921" alt="Screenshot 2023-02-20 at 13 52 35" src="https://user-images.githubusercontent.com/1733610/220126265-d77931e0-18ac-46a0-bf23-d868f8af17a9.png">

With this change, it will look like:

DiffTrain build for commit db5e6250d4bbb70c5085c58694a2e9c78c3f6371.

Changed files:
filename: .github/workflows/commit_artifacts.yml
patch: @@ -152,8 +152,7 @@ jobs:
           commit_message: |
             ${{ github.event.head_commit.message }}
 
-            DiffTrain build for [${{ github.sha }}](https://github.com/facebook/react/commit/${{ github.sha }})
-            [View git log for this commit](https://github.com/facebook/react/commits/${{ github.sha }})
+            DiffTrain build for commit ${{ github.sha }}.
           branch: builds/facebook-www
           commit_user_name: ${{ github.actor }}
           commit_user_email: ${{ github.actor }}@users.noreply.github.com
Repository: ggml-org/llama.cpp
Pull request: vulkan: skip empty set_rows to avoid invalid API usage

Fixes #14845.

Changed files:
filename: ggml/src/ggml-vulkan/ggml-vulkan.cpp
patch: @@ -7882,6 +7882,13 @@ static void ggml_vk_set_rows(ggml_backend_vk_context * ctx, vk_context& subctx,
     const uint32_t src1_type_size = ggml_type_size(src1->type);
     const uint32_t dst_type_size = ggml_type_size(dst->type);
 
+    // Skip empty skip_rows operations. For most ops the empty check at the start
+    // of ggml_vk_build_graph is sufficient, but set_rows can have a nonempty dst
+    // with empty srcs.
+    if (ggml_is_empty(src0) || ggml_is_empty(src1)) {
+        return;
+    }
+
     ggml_vk_op_f32<vk_op_binary_push_constants>(ctx, subctx, src0, src1, nullptr, dst, GGML_OP_SET_ROWS, {
         (uint32_t)ggml_nelements(src0),
         (uint32_t)src0->ne[0], (uint32_t)src0->ne[1], (uint32_t)src0->ne[2],(uint32_t)src0->ne[3], (uint32_t)src0->nb[0] / src0_type_size, (uint32_t)src0->nb[1] / src0_type_size, (uint32_t)src0->nb[2] / src0_type_size, (uint32_t)src0->nb[3] / src0_type_size,
Repository: vercel/next.js
Pull request: [build-sourcemaps] Only compute codeframe once

We used to eagerly compute the codeframe but then only use it for a single frame.
Now we move computation to a getter i.e. we only compute a codeframe when we actually use it.


Changed files:
filename: packages/next/src/server/patch-error-inspect.ts
patch: @@ -275,12 +275,6 @@ function getSourcemappedFrameIfPossible(
     }
   }
 
-  const sourceContent: string | null =
-    sourceMapConsumer.sourceContentFor(
-      sourcePosition.source,
-      /* returnNullOnMissing */ true
-    ) ?? null
-
   const applicableSourceMap = findApplicableSourceMapPayload(
     frame,
     sourceMapPayload
@@ -321,16 +315,33 @@ function getSourcemappedFrameIfPossible(
     ignored,
   }
 
-  const codeFrame = getOriginalCodeFrame(
-    originalFrame,
-    sourceContent,
-    inspectOptions.colors
-  )
+  /** undefined = not yet computed*/
+  let codeFrame: string | null | undefined
 
-  return {
-    stack: originalFrame,
-    code: codeFrame,
-  }
+  return Object.defineProperty(
+    {
+      stack: originalFrame,
+      code: null,
+    },
+    'code',
+    {
+      get: () => {
+        if (codeFrame === undefined) {
+          const sourceContent: string | null =
+            sourceMapConsumer.sourceContentFor(
+              sourcePosition.source,
+              /* returnNullOnMissing */ true
+            ) ?? null
+          codeFrame = getOriginalCodeFrame(
+            originalFrame,
+            sourceContent,
+            inspectOptions.colors
+          )
+        }
+        return codeFrame
+      },
+    }
+  )
 }
 
 function parseAndSourceMap(
@@ -372,10 +383,10 @@ function parseAndSourceMap(
       )
 
       if (
-        sourcemappedFrame.code !== null &&
         sourceFrame === null &&
         // TODO: Is this the right choice?
-        !sourcemappedFrame.stack.ignored
+        !sourcemappedFrame.stack.ignored &&
+        sourcemappedFrame.code !== null
       ) {
         sourceFrame = sourcemappedFrame.code
       }
Repository: ggml-org/llama.cpp
Pull request: make rope_yarn_log_mul optional for deepseek2

Making this parameter optional allows moonshotai/Moonlight-16B-A3B-Instruct to be used without error.

GGUFs: [https://huggingface.co/gabriellarson/Moonlight-16B-A3B-Instruct-GGUF](https://huggingface.co/gabriellarson/Moonlight-16B-A3B-Instruct-GGUF)


Changed files:
filename: src/llama-hparams.h
patch: @@ -98,7 +98,7 @@ struct llama_hparams {
     float    rope_freq_scale_train;
     float    rope_freq_scale_train_swa;
     uint32_t n_ctx_orig_yarn;
-    float    rope_yarn_log_mul;
+    float    rope_yarn_log_mul = 0.0f;
 
     std::array<int, 4> rope_sections;
 

filename: src/llama-model.cpp
patch: @@ -1369,7 +1369,7 @@ void llama_model::load_hparams(llama_model_loader & ml) {
                     // that have no expert_gating_func model parameter set
                     hparams.expert_gating_func = LLAMA_EXPERT_GATING_FUNC_TYPE_SOFTMAX;
                 }
-                ml.get_key(LLM_KV_ROPE_SCALING_YARN_LOG_MUL, hparams.rope_yarn_log_mul);
+                ml.get_key(LLM_KV_ROPE_SCALING_YARN_LOG_MUL, hparams.rope_yarn_log_mul, false);
 
                 switch (hparams.n_layer) {
                     case 27: type = LLM_TYPE_16B; break;
Repository: nodejs/node
Pull request: tools: remove non-existent file from eslint config

This file no longer exists. It hasn't existed since 02de40246f261355ece1cc044e282db4db60d59b.

Changed files:
filename: eslint.config.mjs
patch: @@ -51,7 +51,6 @@ export default [
       'test/.tmp.*/**',
       'test/addons/??_*',
       'test/fixtures/**',
-      'test/message/esm_display_syntax_error.mjs',
       'tools/github_reporter/**',
       'tools/icu/**',
     ],
Repository: electron/electron
Pull request: fix: `utilityProcess` pid should be `undefined` after exit

Backport of #44677

See that PR for details.


Notes: Fixed an issue where a `utilityProcess` pid would not be `undefined` after exit.

Changed files:
filename: docs/api/utility-process.md
patch: @@ -92,6 +92,8 @@ the child process exits, then the value is `undefined` after the `exit` event is
 ```js
 const child = utilityProcess.fork(path.join(__dirname, 'test.js'))
 
+console.log(child.pid) // undefined
+
 child.on('spawn', () => {
   console.log(child.pid) // Integer
 })
@@ -101,6 +103,8 @@ child.on('exit', () => {
 })
 ```
 
+**Note:** You can use the `pid` to determine if the process is currently running.
+
 #### `child.stdout`
 
 A `NodeJS.ReadableStream | null` that represents the child process's stdout.

filename: shell/browser/api/electron_api_utility_process.cc
patch: @@ -255,6 +255,8 @@ void UtilityProcessWrapper::HandleTermination(uint64_t exit_code) {
 
   if (pid_ != base::kNullProcessId)
     GetAllUtilityProcessWrappers().Remove(pid_);
+
+  pid_ = base::kNullProcessId;
   CloseConnectorPort();
   EmitWithoutEvent("exit", exit_code);
   Unpin();

filename: spec/api-utility-process-spec.ts
patch: @@ -225,13 +225,31 @@ describe('utilityProcess module', () => {
     it('is valid when child process launches successfully', async () => {
       const child = utilityProcess.fork(path.join(fixturesPath, 'empty.js'));
       await once(child, 'spawn');
-      expect(child.pid).to.not.be.null();
+      expect(child).to.have.property('pid').that.is.a('number');
     });
 
     it('is undefined when child process fails to launch', async () => {
       const child = utilityProcess.fork(path.join(fixturesPath, 'does-not-exist.js'));
       expect(child.pid).to.be.undefined();
     });
+
+    it('is undefined before the child process is spawned succesfully', async () => {
+      const child = utilityProcess.fork(path.join(fixturesPath, 'empty.js'));
+      expect(child.pid).to.be.undefined();
+      await once(child, 'spawn');
+      child.kill();
+    });
+
+    it('is undefined when child process is killed', async () => {
+      const child = utilityProcess.fork(path.join(fixturesPath, 'empty.js'));
+      await once(child, 'spawn');
+
+      expect(child).to.have.property('pid').that.is.a('number');
+      expect(child.kill()).to.be.true();
+
+      await once(child, 'exit');
+      expect(child.pid).to.be.undefined();
+    });
   });
 
   describe('stdout property', () => {
Repository: facebook/react
Pull request: add test case for semver major comparisons

…ww.npmjs.com/package/semver-compare, 10.0.0 should be gt than 9.0.0

<!--
  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

According to https://www.npmjs.com/package/semver-compare, one of the important goal of semever-compare is to ensure that 10.0.0 is greater than 9.0.0, so I add this test

## How did you test this change?

yarn test


Changed files:
filename: packages/react-devtools-shared/src/__tests__/utils-test.js
patch: @@ -260,12 +260,14 @@ describe('utils', () => {
       expect(gte('1.2.3', '1.2.1')).toBe(true);
       expect(gte('1.2.1', '1.2.1')).toBe(true);
       expect(gte('1.2.1', '1.2.2')).toBe(false);
+      expect(gte('10.0.0', '9.0.0')).toBe(true);
     });
 
     it('gt should compare versions correctly', () => {
       expect(gt('1.2.3', '1.2.1')).toBe(true);
       expect(gt('1.2.1', '1.2.1')).toBe(false);
       expect(gt('1.2.1', '1.2.2')).toBe(false);
+      expect(gte('10.0.0', '9.0.0')).toBe(true);
     });
   });
 });
Repository: ggml-org/llama.cpp
Pull request: Bug: fix inputs to conv1d in mamba layer of plamo2

This PR fixes the error when launching server with value > 1 for `--parallel` option to run PLaMo2 models.
A wrong reshaping with view func for the input to conv1d is fixed.

Changed files:
filename: src/llama-model.cpp
patch: @@ -15763,6 +15763,7 @@ struct llm_build_plamo2 : public llm_graph_context_mamba {
         cb(zx, "mamba_in_proj", il);
         // {8192, 5, 1, 1} -> {8192, 1, 5, 1}
         zx = ggml_permute(ctx0, zx, 0, 2, 1, 3);
+        zx = ggml_cont(ctx0, zx);
         zx = ggml_reshape_4d(ctx0, zx, head_dim * 2, n_heads, n_seq_tokens, n_seqs);
         cb(zx, "mamba_in_proj_out", il);
 
@@ -15780,7 +15781,6 @@ struct llm_build_plamo2 : public llm_graph_context_mamba {
         // conv1d
         {
             // => {d_conv - 1 + n_seq_tokens, d_inner, n_seqs}
-            x = ggml_view_2d(ctx0, x, d_inner, n_seq_tokens * n_seqs, d_inner * x->nb[0], 0);
             ggml_tensor * conv_x = ggml_concat(ctx0, conv, ggml_transpose(ctx0, x), 0);
             cb(conv_x, "mamba_conv1d_input", il);
Repository: nodejs/node
Pull request: doc: add path aliases typescript doc

Adding path aliases not supported documentation and alternative to TypeScript documentation
<!--
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/typescript.md
patch: @@ -172,14 +172,22 @@ To discourage package authors from publishing packages written in TypeScript,
 Node.js will by default refuse to handle TypeScript files inside folders under
 a `node_modules` path.
 
+### Paths aliases
+
+[`tsconfig` "paths"][] won't be transformed and therefore produce an error. The closest
+feature available is [subpath imports][] with the limitation that they need to start
+with `#`.
+
 [CommonJS]: modules.md
 [ES Modules]: esm.md
 [Full TypeScript support]: #full-typescript-support
 [`--experimental-strip-types`]: cli.md#--experimental-strip-types
 [`--experimental-transform-types`]: cli.md#--experimental-transform-types
+[`tsconfig` "paths"]: https://www.typescriptlang.org/tsconfig/#paths
 [`tsx`]: https://tsx.is/
 [`verbatimModuleSyntax`]: https://www.typescriptlang.org/tsconfig/#verbatimModuleSyntax
 [file extensions are mandatory]: esm.md#mandatory-file-extensions
 [full support]: #full-typescript-support
+[subpath imports]: packages.md#subpath-imports
 [the same way as `.js` files.]: packages.md#determining-module-system
 [type stripping]: #type-stripping
Repository: denoland/deno
Pull request: fix(unstable): don't unwrap optional state in otel

otel global state may not be initialized if otel is not enabled, so bail out instead of panicking.

Fixes: https://github.com/denoland/deno/issues/27272

Changed files:
filename: ext/telemetry/lib.rs
patch: @@ -732,9 +732,9 @@ fn op_otel_instrumentation_scope_enter(
 
 #[op2(fast)]
 fn op_otel_instrumentation_scope_enter_builtin(state: &mut OpState) {
-  state.put(InstrumentationScope(
-    BUILT_IN_INSTRUMENTATION_SCOPE.get().unwrap().clone(),
-  ));
+  if let Some(scope) = BUILT_IN_INSTRUMENTATION_SCOPE.get() {
+    state.put(InstrumentationScope(scope.clone()));
+  }
 }
 
 #[op2(fast)]
@@ -749,6 +749,9 @@ fn op_otel_log(
   let Some(Processors { logs, .. }) = OTEL_PROCESSORS.get() else {
     return;
   };
+  let Some(instrumentation_scope) = BUILT_IN_INSTRUMENTATION_SCOPE.get() else {
+    return;
+  };
 
   // Convert the integer log level that ext/console uses to the corresponding
   // OpenTelemetry log severity.
@@ -776,10 +779,7 @@ fn op_otel_log(
     );
   }
 
-  logs.emit(
-    &mut log_record,
-    BUILT_IN_INSTRUMENTATION_SCOPE.get().unwrap(),
-  );
+  logs.emit(&mut log_record, instrumentation_scope);
 }
 
 fn owned_string<'s>(

filename: ext/telemetry/telemetry.ts
patch: @@ -220,6 +220,7 @@ function submitSpan(
   startTime: number,
   endTime: number,
 ) {
+  if (!TRACING_ENABLED) return;
   if (!(traceFlags & TRACE_FLAG_SAMPLED)) return;
 
   // TODO(@lucacasonato): `resource` is ignored for now, should we implement it?
Repository: facebook/react
Pull request: Update rollup config to use moduleSideEffects

## Summary

In rollup v1.19.4, The "treeshake.pureExternalModules" option is deprecated. The "treeshake.moduleSideEffects" option should be used instead, see https://github.com/rollup/rollup/blob/v1.19.4/src/Graph.ts#L130.

## How did you test this change?

ci green

Changed files:
filename: scripts/rollup/build.js
patch: @@ -564,7 +564,8 @@ async function createBundle(bundle, bundleType) {
   const rollupConfig = {
     input: resolvedEntry,
     treeshake: {
-      pureExternalModules,
+      moduleSideEffects: (id, external) =>
+        !(external && pureExternalModules.includes(id)),
     },
     external(id) {
       const containsThisModule = pkg => id === pkg || id.startsWith(pkg + '/');
Repository: nodejs/node
Pull request: src: provide workaround for container-overflow (issue 55584)

In issue https://github.com/nodejs/node/issues/55584, @codebytere reported a sanitizer error 'container-overflow'. This error happens only on systems where the standard library has been annotated to warn about reads between the std::string's end and the end of the its allocated memory (std::string:capacity). This reads are memory safe but they can also be a sign that there is a real bug. In the instance of issue 55584, it is not a bug, it is a false positive.

In some instances, it is possible to indicate to the compiler that we want to disallow these checks to avoid the false positive, but I could not find documentation on this topic. With some glue code, this PR should work around this issue. It somewhat ugly code. In a future release of simdjson, we will provide a more convenient function that avoids such ugly workaround. *However*, in this instance, I am sure @codebytere wants the sanitizers to turn green as soon as possible, hence this PR and the somewhat ugly code.

A future PR will make the code prettier.

Refs: https://github.com/nodejs/node/issues/55584



Changed files:
filename: src/node_modules.cc
patch: @@ -100,11 +100,23 @@ const BindingData::PackageConfig* BindingData::GetPackageJSON(
   if (ReadFileSync(&package_config.raw_json, path.data()) < 0) {
     return nullptr;
   }
+  // In some systems, std::string is annotated to generate an
+  // AddressSanitizer: container-overflow error when reading beyond the end of
+  // the string even when we are still within the capacity of the string.
+  // https://github.com/google/sanitizers/wiki/AddressSanitizerContainerOverflow
+  // https://github.com/nodejs/node/issues/55584
+  // The next lines are a workaround to avoid this false positive.
+  size_t json_length = package_config.raw_json.size();
+  package_config.raw_json.append(simdjson::SIMDJSON_PADDING, ' ');
+  simdjson::padded_string_view json_view(package_config.raw_json.data(),
+                                         json_length,
+                                         package_config.raw_json.size());
+  // End of workaround
 
   simdjson::ondemand::document document;
   simdjson::ondemand::object main_object;
   simdjson::error_code error =
-      binding_data->json_parser.iterate(package_config.raw_json).get(document);
+      binding_data->json_parser.iterate(json_view).get(document);
 
   const auto throw_invalid_package_config = [error_context, path, realm]() {
     if (error_context == nullptr) {
Repository: denoland/deno
Pull request: fix(ext/node): handle Float16Array in node:v8 module

Closes https://github.com/denoland/deno/issues/26580

Changed files:
filename: ext/node/polyfills/v8.ts
patch: @@ -227,6 +227,7 @@ function arrayBufferViewTypeToIndex(abView: ArrayBufferView) {
   // Index 10 is FastBuffer.
   if (type === "[object BigInt64Array]") return 11;
   if (type === "[object BigUint64Array]") return 12;
+  if (type === "[object Float16Array]") return 13;
   return -1;
 }
 export class DefaultSerializer extends Serializer {
@@ -276,6 +277,7 @@ function arrayBufferViewIndexToType(index: number): any {
   if (index === 10) return Buffer;
   if (index === 11) return BigInt64Array;
   if (index === 12) return BigUint64Array;
+  if (index === 13) return Float16Array;
   return undefined;
 }
Repository: facebook/react
Pull request: Make enableCustomElementPropertySupport a dynamic flag in www build

Turns enableCustomElementPropertySupport into a dynamic flag in the www build so we can turn it on behind a GK.

Changed files:
filename: packages/shared/forks/ReactFeatureFlags.www-dynamic.js
patch: @@ -26,6 +26,8 @@ export const enableUnifiedSyncLane = __VARIANT__;
 export const enableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay =
   __VARIANT__;
 export const enableTransitionTracing = __VARIANT__;
+export const enableCustomElementPropertySupport = __VARIANT__;
+
 // Enable this flag to help with concurrent mode debugging.
 // It logs information to the console about React scheduling, rendering, and commit phases.
 //

filename: packages/shared/forks/ReactFeatureFlags.www.js
patch: @@ -32,6 +32,7 @@ export const {
   enableUnifiedSyncLane,
   enableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay,
   enableTransitionTracing,
+  enableCustomElementPropertySupport,
 } = dynamicFeatureFlags;
 
 // On WWW, __EXPERIMENTAL__ is used for a new modern build.
@@ -100,8 +101,6 @@ export const enableServerContext = true;
 // Some www surfaces are still using this. Remove once they have been migrated.
 export const enableUseMutableSource = true;
 
-export const enableCustomElementPropertySupport = __EXPERIMENTAL__;
-
 export const useModernStrictMode = false;
 export const enableFizzExternalRuntime = true;
Repository: electron/electron
Pull request: build: update appveyor image to latest version

This PR updates appveyor.yml to the latest baked image, e-132.0.6834.0.

Notes: none

Changed files:
filename: appveyor-woa.yml
patch: @@ -29,7 +29,7 @@
 
 version: 1.0.{build}
 build_cloud: electronhq-16-core
-image: e-132.0.6824.0
+image: e-132.0.6834.0
 environment:
   GIT_CACHE_PATH: C:\Users\appveyor\libcc_cache
   ELECTRON_OUT_DIR: Default

filename: appveyor.yml
patch: @@ -29,7 +29,7 @@
 
 version: 1.0.{build}
 build_cloud: electronhq-16-core
-image: e-132.0.6824.0
+image: e-132.0.6834.0
 environment:
   GIT_CACHE_PATH: C:\Users\appveyor\libcc_cache
   ELECTRON_OUT_DIR: Default
Repository: denoland/deno
Pull request: fix(task): do not always kill child on ctrl+c on windows

We don't need to forward the kill signal because ctrl+c events are sent to the process group.

Closes https://github.com/denoland/deno/issues/27266

Changed files:
filename: cli/task_runner.rs
patch: @@ -585,7 +585,13 @@ pub async fn run_future_forwarding_signals<TOutput>(
 
 async fn listen_ctrl_c(kill_signal: KillSignal) {
   while let Ok(()) = tokio::signal::ctrl_c().await {
-    kill_signal.send(deno_task_shell::SignalKind::SIGINT)
+    // On windows, ctrl+c is sent to the process group, so the signal would
+    // have already been sent to the child process. We still want to listen
+    // for ctrl+c here to keep the process alive when receiving it, but no
+    // need to forward the signal because it's already been sent.
+    if !cfg!(windows) {
+      kill_signal.send(deno_task_shell::SignalKind::SIGINT)
+    }
   }
 }