helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: use merge base for diff-tree

the diff-tree previously compared the head ref (the latest commit in the PR) against the base ref (the latest commit in the target branch). if the target branch is updated, this comparison will include the new files in the target as well which is wrong.

instead, find and compare the head ref against the merge base of the head and base refs. this should ensure only the changes added in the pr are evaluated

Changed files:
filename: .github/workflows/test.yaml
patch: @@ -31,7 +31,9 @@ jobs:
       - id: changes
         run: |
           changed() {
-            git diff-tree -r --no-commit-id --name-only ${{ github.event.pull_request.base.sha }} ${{ github.event.pull_request.head.sha }} \
+            git diff-tree -r --no-commit-id --name-only \
+              $(git merge-base ${{ github.event.pull_request.base.sha }} ${{ github.event.pull_request.head.sha }}) \
+              ${{ github.event.pull_request.head.sha }} \
               | xargs python3 -c "import sys; print(any([x.startswith('$1') for x in sys.argv[1:]]))"
           }
Repository: nodejs/node
Pull request: lib: optimize writable stream buffer clearing

Improved the `clearBuffer` function in `lib/internal/streams/writable.js` by replacing `buffered.splice(0, i)` with `ArrayPrototypeSlice(buffered, i)`. This change eliminates the O(N) shifting overhead of `splice` when clearing the buffer, especially for large buffers, leading to better CPU utilization and reduced garbage collection overhead.

Profiling before and after the change showed a significant reduction in 10 CPU ticks attributed to the `clearBuffer` function, from 90 ticks to 1 tick.

Changed files:
filename: lib/internal/streams/writable.js
patch: @@ -784,7 +784,7 @@ function clearBuffer(stream, state) {
     if (i === buffered.length) {
       resetBuffer(state);
     } else if (i > 256) {
-      buffered.splice(0, i);
+      state[kBufferedValue] = ArrayPrototypeSlice(buffered, i);
       state.bufferedIndex = 0;
     } else {
       state.bufferedIndex = i;
Repository: vercel/next.js
Pull request: Turbopack: use mmap advise to help the OS preloading

### What?

Help the OS to prefetch file ranges

Closes PACK-5646

Changed files:
filename: turbopack/crates/turbo-persistence/src/static_sorted_file.rs
patch: @@ -109,6 +109,11 @@ impl StaticSortedFile {
         let mmap = unsafe { Mmap::map(&File::open(&path)?)? };
         #[cfg(unix)]
         mmap.advise(memmap2::Advice::Random)?;
+        #[cfg(unix)]
+        {
+            let offset = meta.block_offsets_start(mmap.len());
+            let _ = mmap.advise_range(memmap2::Advice::Sequential, offset, mmap.len() - offset);
+        }
         let file = Self { meta, mmap };
         Ok(file)
     }
@@ -397,6 +402,12 @@ impl StaticSortedFile {
                 self.meta.blocks_start()
             );
         }
+        #[cfg(unix)]
+        let _ = self.mmap.advise_range(
+            memmap2::Advice::Sequential,
+            block_start,
+            block_end - block_start,
+        );
         let uncompressed_length = (&self.mmap[block_start..block_start + 4]).read_u32::<BE>()?;
         let block = &self.mmap[block_start + 4..block_end];
         Ok((uncompressed_length, block))
Repository: denoland/deno
Pull request: fix: ensure binaries distributed in `@deno/...` npm packages are exectuable

Bit of a cleanup more than anything.

Changed files:
filename: .github/workflows/npm_publish.yml
patch: @@ -38,11 +38,14 @@ jobs:
       - name: Build npm packages
         run: ./tools/release/npm/build.ts ${{ inputs.version || '' }}
 
+      - name: Tar npm dist (preserves permissions)
+        run: tar cf tools/release/npm/dist.tar -C tools/release/npm --exclude='node_modules' dist
+
       - name: Upload npm dist artifact
         uses: actions/upload-artifact@v6
         with:
           name: npm-dist
-          path: tools/release/npm/dist
+          path: tools/release/npm/dist.tar
           retention-days: 1
 
   test:
@@ -73,7 +76,10 @@ jobs:
         uses: actions/download-artifact@v6
         with:
           name: npm-dist
-          path: tools/release/npm/dist
+          path: tools/release/npm
+
+      - name: Extract npm dist
+        run: tar xf tools/release/npm/dist.tar -C tools/release/npm
 
       - name: Write Verdaccio config
         run: |
@@ -307,7 +313,10 @@ jobs:
         uses: actions/download-artifact@v6
         with:
           name: npm-dist
-          path: tools/release/npm/dist
+          path: tools/release/npm
+
+      - name: Extract npm dist
+        run: tar xf tools/release/npm/dist.tar -C tools/release/npm
 
       - name: Publish to npm
         run: ./tools/release/npm/build.ts ${{ inputs.version || '' }} --publish-only

filename: tools/release/npm/build.ts
patch: @@ -164,6 +164,10 @@ if (args.publish || args["publish-only"]) {
       continue;
     }
     const pkgDir = scopeDir.join(pkgName);
+    // ensure the binary is executable in the tarball
+    if (pkg.os !== "win32") {
+      await $`chmod +x ${pkgDir.join("deno")}`;
+    }
     await $`cd ${pkgDir} && npm publish --provenance --access public`;
   }
 

filename: tools/release/npm/install_api.cjs
patch: @@ -45,7 +45,7 @@ module.exports = {
       // into the deno package folder
       hardLinkOrCopy(sourceExecutablePath, targetExecutablePath);
       if (os.platform() !== "win32") {
-        // chomd +x
+        // chmod +x
         chmodX(targetExecutablePath);
       }
       return targetExecutablePath;
@@ -60,21 +60,20 @@ module.exports = {
           err,
         );
       }
-      // use the path found in the specific package
-      try {
-        chmodX(sourceExecutablePath);
-      } catch (_err) {
-        // ignore
-      }
       return sourceExecutablePath;
     }
   },
 };
 
 /** @filePath {string} */
 function chmodX(filePath) {
-  const perms = fs.statSync(filePath).mode;
-  fs.chmodSync(filePath, perms | 0o111);
+  const fd = fs.openSync(filePath, "r");
+  try {
+    const perms = fs.fstatSync(fd).mode;
+    fs.fchmodSync(fd, perms | 0o111);
+  } finally {
+    fs.closeSync(fd);
+  }
 }
 
 function getTarget() {
Repository: ggml-org/llama.cpp
Pull request: ggml : use WARP_SIZE/2 for argmax reduction offset

Currently, `ggml_cuda_argmax` hardcodes the reduction offset start to `16`. While this works for current NVIDIA devices(Warp size 32), it is inconsistent with the reduction patterns in common.cuh and potentially incorrect for future architectures, where the reduction would miss the first steps (offset 32) if wrap sizes are different.
This change aligns `argmax.cu` with the warp_reduce implementations in `common.cuh`, making it more modular

Changed files:
filename: ggml/src/ggml-cuda/argmax.cu
patch: @@ -21,7 +21,7 @@ static __global__ void argmax_f32(const float * __restrict__ x, int32_t * __rest
     }
 
 #pragma unroll
-    for (int offset = 16; offset > 0; offset >>= 1) {
+    for (int offset = WARP_SIZE/2; offset > 0; offset >>= 1) {
         const float val = __shfl_xor_sync(0xFFFFFFFF, maxval, offset, WARP_SIZE);
         const int   col = __shfl_xor_sync(0xFFFFFFFF, argmax, offset, WARP_SIZE);
         if (val > maxval) {
@@ -50,7 +50,7 @@ static __global__ void argmax_f32(const float * __restrict__ x, int32_t * __rest
                 argmax = shared_argmax[lane_id];
             }
 #pragma unroll
-            for (int offset = 16; offset > 0; offset >>= 1) {
+            for (int offset = WARP_SIZE/2; offset > 0; offset >>= 1) {
                 const float val = __shfl_xor_sync(0xFFFFFFFF, maxval, offset, WARP_SIZE);
                 const int   col = __shfl_xor_sync(0xFFFFFFFF, argmax, offset, WARP_SIZE);
                 if (val > maxval) {
Repository: electron/electron
Pull request: fix: crash on source capture with empty thumbnail size

Backport of #47641

See that PR for details.


Notes: Fixed a crash when calling `desktopCapturer.getSources` with an empty thumbnail size.


Changed files:
filename: shell/browser/api/electron_api_desktop_capturer.cc
patch: @@ -233,7 +233,8 @@ DesktopCapturer::DesktopListListener::~DesktopListListener() = default;
 
 void DesktopCapturer::DesktopListListener::OnDelegatedSourceListSelection() {
   if (have_thumbnail_) {
-    std::move(update_callback_).Run();
+    content::GetUIThreadTaskRunner({})->PostTask(FROM_HERE,
+                                                 std::move(update_callback_));
   } else {
     have_selection_ = true;
   }
@@ -246,7 +247,8 @@ void DesktopCapturer::DesktopListListener::OnSourceThumbnailChanged(int index) {
     have_selection_ = false;
 
     // PipeWire returns a single source, so index is not relevant.
-    std::move(update_callback_).Run();
+    content::GetUIThreadTaskRunner({})->PostTask(FROM_HERE,
+                                                 std::move(update_callback_));
   } else {
     have_thumbnail_ = true;
   }
Repository: ollama/ollama
Pull request: .github/workflows: add in-flight cancellations on new push


Changed files:
filename: .github/workflows/test.yaml
patch: @@ -1,5 +1,15 @@
 name: test
 
+concurrency:
+  # For PRs, later CI runs preempt previous ones. e.g. a force push on a PR
+  # cancels running CI jobs and starts all new ones.
+  #
+  # For non-PR pushes, concurrency.group needs to be unique for every distinct
+  # CI run we want to have happen. Use run_id, which in practice means all
+  # non-PR CI runs will be allowed to run without preempting each other.
+  group: ${{ github.workflow }}-$${{ github.pull_request.number || github.run_id }}
+  cancel-in-progress: true
+
 on:
   pull_request:
     paths:
@@ -283,7 +293,6 @@ jobs:
         with:
           go-version-file: go.mod
           cache: true
-      - run: go get
       - run: |
           case ${{ matrix.arch }} in
             amd64) echo ARCH=x86_64 ;;
Repository: facebook/react
Pull request: [flow] Eliminate a few React.Element type that will be synced to react-native

## Summary

Flow will eventually remove the specific `React.Element` type. For most of the code, it can be replaced with `React.MixedElement` or `React.Node`.

When specific react elements are required, it needs to be replaced with either `React$Element` which will trigger a `internal-type` lint error that can be disabled project-wide, or use `ExactReactElement_DEPRECATED`.

Fortunately in this case, this one can be replaced with just `React.MixedElement`.

## How did you test this change?

`flow`

Changed files:
filename: packages/react-native-renderer/src/ReactNativeRenderer.js
patch: @@ -8,7 +8,7 @@
  */
 
 import type {ReactPortal, ReactNodeList} from 'shared/ReactTypes';
-import type {ElementRef, Element, ElementType} from 'react';
+import type {ElementRef, ElementType, MixedElement} from 'react';
 import type {FiberRoot} from 'react-reconciler/src/ReactInternalTypes';
 import type {RenderRootOptions} from './ReactNativeTypes';
 
@@ -117,7 +117,7 @@ function nativeOnCaughtError(
 }
 
 function render(
-  element: Element<ElementType>,
+  element: MixedElement,
   containerTag: number,
   callback: ?() => void,
   options: ?RenderRootOptions,

filename: packages/react-native-renderer/src/ReactNativeTypes.js
patch: @@ -9,7 +9,12 @@
  * @flow strict
  */
 
-import type {ElementRef, ElementType, Element, AbstractComponent} from 'react';
+import type {
+  ElementRef,
+  ElementType,
+  MixedElement,
+  AbstractComponent,
+} from 'react';
 
 export type MeasureOnSuccessCallback = (
   x: number,
@@ -221,7 +226,7 @@ export type ReactNativeType = {
     eventType: string,
   ): void,
   render(
-    element: Element<ElementType>,
+    element: MixedElement,
     containerTag: number,
     callback: ?() => void,
     options: ?RenderRootOptions,
@@ -256,7 +261,7 @@ export type ReactFabricType = {
     eventType: string,
   ): void,
   render(
-    element: Element<ElementType>,
+    element: MixedElement,
     containerTag: number,
     callback: ?() => void,
     concurrentRoot: ?boolean,

filename: packages/react/index.js
patch: @@ -15,6 +15,7 @@ export type AbstractComponent<
 > = React$AbstractComponent<Config, Instance>;
 export type ElementType = React$ElementType;
 export type Element<+C> = React$Element<C>;
+export type MixedElement = React$Element<ElementType>;
 export type Key = React$Key;
 export type Ref<C> = React$Ref<C>;
 export type Node = React$Node;
Repository: nodejs/node
Pull request: doc: update "Type stripping in dependencies" section

The docs state, "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" (emphasis added). This suggests that there's a way to override that default. However, as far as I can tell, there is not.

<!--
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: @@ -206,8 +206,8 @@ are enabled by default.
 ### Type stripping in dependencies
 
 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.
+Node.js refuses to handle TypeScript files inside folders under a `node_modules`
+path.
 
 ### Paths aliases
Repository: vercel/next.js
Pull request: Turbopack: follow-up changes from untracked tracing

### What?

avoid some calls when tracing is not enabled

Closes PACK-5648

Changed files:
filename: turbopack/crates/turbopack-core/src/module_graph/mod.rs
patch: @@ -1698,12 +1698,11 @@ enum SingleModuleGraphBuilderNode {
 
 impl SingleModuleGraphBuilderNode {
     async fn new_module(emit_spans: bool, module: ResolvedVc<Box<dyn Module>>) -> Result<Self> {
-        let ident = module.ident();
         Ok(Self::Module {
             module,
             ident: if emit_spans {
                 // INVALIDATION: we don't need to invalidate when the span name changes
-                Some(ident.to_string().untracked().await?)
+                Some(module.ident_string().untracked().await?)
             } else {
                 None
             },

filename: turbopack/crates/turbopack-core/src/output.rs
patch: @@ -20,8 +20,8 @@ pub trait OutputAsset: Asset {
     /// The identifier of the [OutputAsset] as string. It's expected to be unique and
     /// capture all properties of the [OutputAsset].
     #[turbo_tasks::function]
-    async fn path_string(self: Vc<Self>) -> Result<Vc<RcStr>> {
-        Ok(self.path().resolve().await?.to_string())
+    fn path_string(self: Vc<Self>) -> Vc<RcStr> {
+        self.path().to_string()
     }
 
     /// Other references [OutputAsset]s from this [OutputAsset].
Repository: ggml-org/llama.cpp
Pull request: gguf-py: allow converting multi-tensor models from read-only locations

The problem raises when there is a model with multiple tensor files, the memmap uses `r+` as a default flag which is "read and write" 

https://numpy.org/devdocs/reference/generated/numpy.memmap.html#numpy-memmap

Changed files:
filename: gguf-py/gguf/utility.py
patch: @@ -288,7 +288,7 @@ class LocalTensor:
     data_range: LocalTensorRange
 
     def mmap_bytes(self) -> np.ndarray:
-        return np.memmap(self.data_range.filename, offset=self.data_range.offset, shape=self.data_range.size)
+        return np.memmap(self.data_range.filename, mode='r', offset=self.data_range.offset, shape=self.data_range.size)
 
 
 class SafetensorsLocal:
Repository: ollama/ollama
Pull request: Put back non-avx CPU build for windows


Changed files:
filename: llm/generate/gen_windows.ps1
patch: @@ -340,6 +340,7 @@ if ($($args.count) -eq 0) {
     git_module_setup
     apply_patches
     build_static
+    build_cpu
     build_cpu_avx
     build_cpu_avx2
     build_cuda
Repository: ggml-org/llama.cpp
Pull request: llama-fit-params: force disable mlock

Fixes https://github.com/ggml-org/llama.cpp/issues/18090 .

It seems that (unbeknownst to me) the code is trying to use a memory lock even when memory mapping is disabled which results in a crash. This PR force disables `mlock` for `llama_params_fit`.

Changed files:
filename: src/llama.cpp
patch: @@ -71,8 +71,9 @@ static std::vector<llama_device_memory_data> llama_get_device_memory_data(
     }, &ud);
 
     llama_model_params mparams_copy = *mparams;
-    mparams_copy.no_alloc = true;
-    mparams_copy.use_mmap = false;
+    mparams_copy.no_alloc  = true;
+    mparams_copy.use_mmap  = false;
+    mparams_copy.use_mlock = false;
 
     llama_model * model = llama_model_load_from_file(path_model, mparams_copy);
     if (model == nullptr) {
Repository: facebook/react
Pull request: [compiler] Allow hoisting of destructured variable declarations

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #30699

Summary:
It doesn't seem as though this invariant was necessary

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/BuildHIR.ts
patch: @@ -428,17 +428,6 @@ function lowerStatement(
               loc: id.parentPath.node.loc ?? GeneratedSource,
             });
             continue;
-          } else if (!binding.path.get('id').isIdentifier()) {
-            builder.errors.push({
-              severity: ErrorSeverity.Todo,
-              reason: 'Unsupported variable declaration type for hoisting',
-              description: `variable "${
-                binding.identifier.name
-              }" declared with ${binding.path.get('id').type}`,
-              suggestions: null,
-              loc: id.parentPath.node.loc ?? GeneratedSource,
-            });
-            continue;
           } else if (
             binding.kind !== 'const' &&
             binding.kind !== 'var' &&

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/hoist-destruct.expect.md
patch: @@ -0,0 +1,62 @@
+
+## Input
+
+```javascript
+//@flow
+component Foo() {
+  function foo() {
+    return (
+      <div>
+        {a} {z} {y}
+      </div>
+    );
+  }
+  const [a, {x: z, y = 10}] = [1, {x: 2}];
+  return foo();
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Foo,
+  params: [],
+};
+
+```
+
+## Code
+
+```javascript
+import { c as _c } from "react/compiler-runtime";
+function Foo() {
+  const $ = _c(1);
+  let t0;
+  if ($[0] === Symbol.for("react.memo_cache_sentinel")) {
+    const foo = function foo() {
+      return (
+        <div>
+          {a} {z} {y}
+        </div>
+      );
+    };
+
+    const [t1, t2] = [1, { x: 2 }];
+    const a = t1;
+    const { x: t3, y: t4 } = t2;
+    const z = t3;
+    const y = t4 === undefined ? 10 : t4;
+    t0 = foo();
+    $[0] = t0;
+  } else {
+    t0 = $[0];
+  }
+  return t0;
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Foo,
+  params: [],
+};
+
+```
+      
+### Eval output
+(kind: ok) <div>1 2 10</div>
\ No newline at end of file

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/hoist-destruct.js
patch: @@ -0,0 +1,17 @@
+//@flow
+component Foo() {
+  function foo() {
+    return (
+      <div>
+        {a} {z} {y}
+      </div>
+    );
+  }
+  const [a, {x: z, y = 10}] = [1, {x: 2}];
+  return foo();
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Foo,
+  params: [],
+};
Repository: denoland/deno
Pull request: ci: run ecosystem tests only on weekdays


Changed files:
filename: .github/workflows/ecosystem_compat_test.yml
patch: @@ -2,7 +2,7 @@ name: ecosystem_compat_test
 
 on:
   schedule:
-    - cron: '0 10 * * *'
+    - cron: '0 10 * * 1-5'
   workflow_dispatch:
 
 jobs:
Repository: nodejs/node
Pull request: build: fix 'implicit-function-declaration' on OpenHarmony platform

When I cross-compile Node.js for the OpenHarmony platform, I must add the parameter `-Wno-error=implicit-function-declaration`.

This is my compile script: https://github.com/hqzing/build-ohos-node/blob/main/build.sh

If I don't add this parameter, I will encounter this error:
```log
../deps/uvwasi/src/uvwasi.c:1444:5: error: call to undeclared function 'seekdir'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
 1444 |     seekdir(dir->dir, cookie);
      |     ^
../deps/uvwasi/src/uvwasi.c:1459:14: error: call to undeclared function 'telldir'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
 1459 |       tell = telldir(dir->dir);
      |              ^
2 errors generated.
make[1]: *** [deps/uvwasi/uvwasi.target.mk:100: /root/build-ohos-node/node-v24.2.0/out/Release/obj.target/uvwasi/deps/uvwasi/src/uvwasi.o] Error 1
make[1]: *** Waiting for unfinished jobs....
```

Now that I have identified the root cause, which is the missing macro definition `_GNU_SOURCE` during the build process, I am proposing this PR to fix the issue and eliminate the dependency on `-Wno-error=implicit-function-declaration` parameter.


Changed files:
filename: deps/uvwasi/uvwasi.gyp
patch: @@ -28,7 +28,7 @@
         'include_dirs': ['include']
       },
       'conditions': [
-        [ 'OS=="linux"', {
+        [ 'OS=="linux" or OS=="openharmony"', {
           'defines': [
             '_GNU_SOURCE',
             '_POSIX_C_SOURCE=200112',
Repository: denoland/deno
Pull request: perf(npm): improve decompression speed more

Saw this in a flamegraph. We're going to overwrite it so we don't need to fill with zeroes.

<img width="423" height="199" alt="image" src="https://github.com/user-attachments/assets/fe216eb3-6302-43e8-9b1a-67bf3ea9d164" />


Changed files:
filename: libs/npm_cache/tarball_extract.rs
patch: @@ -103,7 +103,9 @@ fn decompress_gzip(
   if decompressed.try_reserve(size_hint).is_err() {
     return decompress_gzip_streaming(data);
   }
-  decompressed.resize(size_hint, 0);
+  // SAFETY: we reserved `size_hint` bytes above and libdeflate will
+  // write into this buffer, then we truncate to the actual size.
+  unsafe { decompressed.set_len(size_hint) };
   match decompressor.gzip_decompress(data, &mut decompressed) {
     Ok(actual_size) => {
       decompressed.truncate(actual_size);
Repository: ollama/ollama
Pull request: Update windows.md

Fixed a typo

Changed files:
filename: docs/windows.md
patch: @@ -14,7 +14,7 @@ As this is a preview release, you should expect a few bugs here and there.  If
 you run into a problem you can reach out on
 [Discord](https://discord.gg/ollama), or file an 
 [issue](https://github.com/ollama/ollama/issues).
-Logs will often be helpful in dianosing the problem (see
+Logs will often be helpful in diagnosing the problem (see
 [Troubleshooting](#troubleshooting) below)
 
 ## System Requirements