helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: Update README.md, Terminal app "bb7"

Introducing "bb7", an advanced chat bot designed for versatile interactions. Equipped with TTS (Text-to-Speech) capabilities, bb7 enables seamless voice conversations with users. It also supports local Retrieval-Augmented Generation (RAG), allowing for efficient document-based queries and responses, even without cloud dependency.

Changed files:
filename: README.md
patch: @@ -367,6 +367,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Ollama eBook Summary](https://github.com/cognitivetech/ollama-ebook-summary/)
 - [Ollama Mixture of Experts (MOE) in 50 lines of code](https://github.com/rapidarchitect/ollama_moe)
 - [vim-intelligence-bridge](https://github.com/pepo-ec/vim-intelligence-bridge) Simple interaction of "Ollama" with the Vim editor
+- [bb7](https://github.com/drunkwcodes/bb7)
 - [SwollamaCLI](https://github.com/marcusziade/Swollama) bundled with the Swollama Swift package. [Demo](https://github.com/marcusziade/Swollama?tab=readme-ov-file#cli-usage)
 - [aichat](https://github.com/sigoden/aichat) All-in-one LLM CLI tool featuring Shell Assistant, Chat-REPL, RAG, AI tools & agents, with access to OpenAI, Claude, Gemini, Ollama, Groq, and more.
 - [orbiton](https://github.com/xyproto/orbiton) Configuration-free text editor and IDE with support for tab completion with Ollama.
Repository: facebook/react
Pull request: Avoid double logging component render time

This got moved into the functional component and class component case statements here: https://github.com/facebook/react/commit/0de1233fd180969f7ffdfc98151922f2466ceb1f. So that we could separate the error case for class components.

However, due to a faulty rebase this got restored at the top as well. Leading to double component renders being logged.

In the other offscreen reconnect passes we don't do this in each case statement but still once at the top. The reason this doesn't matter is because use the PerformedWork flag and that is only set for function and class components. Although maybe it should be set for expensive DOM components too and then we have to remember this.



Changed files:
filename: packages/react-reconciler/src/ReactFiberCommitWork.js
patch: @@ -3095,25 +3095,6 @@ function commitPassiveMountOnFiber(
   const prevEffectStart = pushComponentEffectStart();
   const prevEffectErrors = pushComponentEffectErrors();
 
-  // If this component rendered in Profiling mode (DEV or in Profiler component) then log its
-  // render time. We do this after the fact in the passive effect to avoid the overhead of this
-  // getting in the way of the render characteristics and avoid the overhead of unwinding
-  // uncommitted renders.
-  if (
-    enableProfilerTimer &&
-    enableComponentPerformanceTrack &&
-    (finishedWork.mode & ProfileMode) !== NoMode &&
-    ((finishedWork.actualStartTime: any): number) > 0 &&
-    (finishedWork.flags & PerformedWork) !== NoFlags
-  ) {
-    logComponentRender(
-      finishedWork,
-      ((finishedWork.actualStartTime: any): number),
-      endTime,
-      inHydratedSubtree,
-    );
-  }
-
   const isViewTransitionEligible = enableViewTransition
     ? includesOnlyViewTransitionEligibleLanes(committedLanes)
     : false;
Repository: nodejs/node
Pull request: src: mark unused private field as such

Refs: https://github.com/nodejs/node/pull/59828


Changed files:
filename: src/node.h
patch: @@ -1462,7 +1462,7 @@ class NODE_EXTERN CallbackScope {
   CallbackScope(CallbackScope&&) = delete;
 
  private:
-  void* resource_storage_global_;
+  [[maybe_unused]] void* reserved_;
   union {
     v8::Local<v8::Object> local;
     v8::Global<v8::Object>* global_ptr;
Repository: facebook/react
Pull request: [ci] Fix param casing


Casing was incorrect.

Tested by running locally with a PAT.

```
$ scripts/release/download-experimental-build.js --commit=2d40460cf768071d3a70b4cdc16075d23ca1ff25
Command failed: gh attestation verify artifacts_combined.zip --repo=facebook/react

Error: failed to fetch attestations from facebook/react: HTTP 404: Not Found (https://api.github.com/repos/facebook/react/attestations/sha256:23d05644f9e49e02cbb441e3932cc4366b261826e58ce222ea249a6b786f0b5f?per_page=30)
`gh attestation verify artifacts_combined.zip --repo=facebook/react` (exited with error code 1)

$ scripts/release/download-experimental-build.js --commit=2d40460cf768071d3a70b4cdc16075d23ca1ff25 --noVerify
⠼ Downloading artifacts from GitHub for commit 2d40460cf768071d3a70b4cdc16075d23ca1ff25)  5%                  0.1m, estimated 1.6m
✓ Downloading artifacts from GitHub for commit 2d40460cf768071d3a70b4cdc16075d23ca1ff25) 9.5 secs
An experimental build has been downloaded!

You can download this build again by running:
  scripts/download-experimental-build.js --commit=2d40460cf768071d3a70b4cdc16075d23ca1ff25
```


Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -487,7 +487,7 @@ jobs:
         #
         # Note that this means that scripts/release/download-experimental-build.js must be run with
         # --no-verify when downloading a build from a fork.
-        if: github.event.pull_request.head.repo.full_name == github.repository
+        if: github.event_name == 'push' && github.ref_name == 'main' || github.event.pull_request.head.repo.full_name == github.repository
         with:
           subject-name: artifacts_combined.zip
           subject-digest: sha256:${{ steps.upload_artifacts_combined.outputs.artifact-digest }}
@@ -818,7 +818,7 @@ jobs:
         # unverified artifact is not used. Additionally this workflow runs in the pull_request
         # trigger so only restricted permissions are available.
         run: |
-          GH_TOKEN=${{ github.token }} scripts/release/download-experimental-build.js --commit=$(git rev-parse ${{ github.event.pull_request.base.sha }}) ${{ (github.event.pull_request.head.repo.full_name != github.repository && '--no-verify') || ''}}
+          GH_TOKEN=${{ github.token }} scripts/release/download-experimental-build.js --commit=$(git rev-parse ${{ github.event.pull_request.base.sha }}) ${{ (github.event.pull_request.head.repo.full_name != github.repository && '--noVerify') || ''}}
           mv ./build ./base-build
       - name: Delete extraneous files
         # TODO: The `download-experimental-build` script copies the npm

filename: scripts/release/download-experimental-build.js
patch: @@ -27,7 +27,7 @@ const argv = yargs.wrap(yargs.terminalWidth()).options({
     demandOption: true,
     type: 'string',
   },
-  'no-verify': {
+  noVerify: {
     describe: 'Skip verification',
     requiresArg: false,
     type: 'boolean',
Repository: facebook/react
Pull request: [ci] Fix incorrect condition


Oops, missed this when I switched it from checking if its a fork to checking if its from this repo.


Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -487,7 +487,7 @@ jobs:
         #
         # Note that this means that scripts/release/download-experimental-build.js must be run with
         # --no-verify when downloading a build from a fork.
-        if: github.event.pull_request.head.repo.full_name != github.repository
+        if: github.event.pull_request.head.repo.full_name == github.repository
         with:
           subject-name: artifacts_combined.zip
           subject-digest: sha256:${{ steps.upload_artifacts_combined.outputs.artifact-digest }}
Repository: electron/electron
Pull request: fix: devtools crashing on Linux in detach mode

#### Description of Change

Closes https://github.com/electron/electron/issues/48430
Refs CL:6633935

Fixes an issue where calling `webContents.openDevTools({ mode: 'detach' })` would cause a crash on Wayland.

#### 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: Fixed an issue where calling `webContents.openDevTools({ mode: 'detach' })` would cause a crash on Wayland.


Changed files:
filename: shell/browser/ui/views/electron_views_delegate.cc
patch: @@ -8,6 +8,7 @@
 
 #include "ui/views/widget/desktop_aura/desktop_native_widget_aura.h"
 #include "ui/views/widget/native_widget_aura.h"
+#include "ui/views/window/default_frame_view.h"
 
 #if BUILDFLAG(IS_LINUX)
 #include "base/environment.h"
@@ -62,7 +63,7 @@ gfx::ImageSkia* ViewsDelegate::GetDefaultWindowIcon() const {
 
 std::unique_ptr<views::FrameView> ViewsDelegate::CreateDefaultFrameView(
     views::Widget* widget) {
-  return nullptr;
+  return std::make_unique<views::DefaultFrameView>(widget);
 }
 
 void ViewsDelegate::OnBeforeWidgetInit(
Repository: ollama/ollama
Pull request: Update README.md, Linux AMD ROCm area

My small contribution for this amazing work here

Changed files:
filename: llama/README.md
patch: @@ -55,7 +55,7 @@ go build -tags avx,cuda .
 
 ### ROCm
 
-Install the [CUDA toolkit v11.3.1](https://developer.nvidia.com/cuda-11-3-1-download-archive):
+Install [ROCm](https://rocm.docs.amd.com/en/latest/).
 
 ```shell
 make ggml_hipblas.so
@@ -77,7 +77,7 @@ go build -tags avx,cuda .
 
 ### ROCm
 
-Install [ROCm 5.7.1](https://rocm.docs.amd.com/en/docs-5.7.1/).
+Install [ROCm](https://rocm.docs.amd.com/en/latest/).
 
 ```shell
 make ggml_hipblas.dll
Repository: vercel/next.js
Pull request: [turbopack] update warning message in the bundle analyzer

Point next/bundle-analyzer users at the new one when running with turbopack

![image.png](https://app.graphite.com/user-attachments/assets/bffb6bfb-102c-468f-914c-ef1794406591.png)



Changed files:
filename: packages/next-bundle-analyzer/index.js
patch: @@ -6,7 +6,9 @@ module.exports =
     }
     if (process.env.TURBOPACK) {
       console.warn(
-        'The Next Bundle Analyzer is not compatible with Turbopack builds yet, no report will be generated.\n\n' +
+        'The Next Bundle Analyzer is not compatible with Turbopack builds, no report will be generated.\n\n' +
+          'Consider trying the new Turbopack analyzer via `next experimental-analyze`.\n\n' +
+          'See https://nextjs.org/docs/app/guides/package-bundling for more information\n\n' +
           'To run this analysis pass the `--webpack` flag to `next build`'
       )
       return nextConfig
Repository: ollama/ollama
Pull request: Update README.md


Changed files:
filename: README.md
patch: @@ -333,6 +333,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [ARGO](https://github.com/xark-argo/argo) (Locally download and run Ollama and Huggingface models with RAG on Mac/Windows/Linux)
 - [G1](https://github.com/bklieger-groq/g1) (Prototype of using prompting strategies to improve the LLM's reasoning through o1-like reasoning chains.)
 - [Ollama App](https://github.com/JHubi1/ollama-app) (Modern and easy-to-use multi-platform client for Ollama)
+- [ollama-chat-app](https://github.com/anan1213095357/ollama-chat-app) (Flutter-based chat app)
 - [Perfect Memory AI](https://www.perfectmemory.ai/) (Productivity AI assists personalized by what you have seen on your screen, heard and said in the meetings)
 - [Hexabot](https://github.com/hexastack/hexabot) (A conversational AI builder)
 - [Reddit Rate](https://github.com/rapidarchitect/reddit_analyzer) (Search and Rate Reddit topics with a weighted summation)
Repository: huggingface/transformers
Pull request: Fix deepspeed sp loss due to missing labels 

# What does this PR do?

This PR fixes `_deepspeed_sp_compute_loss`. [UlyssesSPDataLoaderAdapter](https://github.com/deepspeedai/DeepSpeed/blob/6eb98aaf03419d1a3a608b0955eb3eae5ad2dc27/deepspeed/runtime/sequence_parallel/ulysses_sp.py#L598) took `labels` out from `inputs` while inserting `shift_labels` so it doesn't compute the `loss` at all since we didn't pass `labels` ...

Fixes https://github.com/huggingface/transformers/pull/42444#issuecomment-3639642523

Changed files:
filename: src/transformers/trainer.py
patch: @@ -3943,6 +3943,9 @@ def _deepspeed_sp_compute_loss(self, model, inputs, return_outputs, pc):
         # Both standard transformer models and Liger-patched models handle shift_labels correctly,
         # so we can directly use the computed loss from the model output.
         # See: https://huggingface.co/docs/accelerate/en/concept_guides/sequence_parallelism
+        if "labels" not in inputs and "shift_labels" in inputs:
+            # DeepSpeed SP Dataloader removes "labels" but we need it, otherwise, we won't compute the loss.
+            inputs["labels"] = inputs["shift_labels"]
         outputs = model(**inputs)
         loss = outputs.loss
Repository: vuejs/vue
Pull request: Specify that tags with side-effects will not be parsed.

Where I work, it's not uncommon to come across `<script>` tags in templates that would not be trivial to move into separate files. If Vue will prevent the execution of the contents of these tags, I think the warning should say so. As it is, it reads more like a recommendation than a requirement:

`Templates should only be responsible for mapping the state to the UI. Avoid placing tags with side-effects in your templates, such as <script>`. 

I don't know if the language I've added is best, but it's an example of text that tells the user they should not expect their code to run. Feel free to edit as desired.


Changed files:
filename: src/compiler/parser/index.js
patch: @@ -91,7 +91,7 @@ export function parse (
         process.env.NODE_ENV !== 'production' && warn(
           'Templates should only be responsible for mapping the state to the ' +
           'UI. Avoid placing tags with side-effects in your templates, such as ' +
-          `<${tag}>.`
+          `<${tag}>` + ', as they will not be parsed.'
         )
       }
Repository: electron/electron
Pull request: test: fix types in chromium-spec

#### Description of Change

See https://github.com/electron/electron/actions/runs/19341206364

```
Error: electron/spec/chromium-spec.ts(918,54): error TS7006: Parameter '_wc' implicitly has an 'any' type.
Error: electron/spec/chromium-spec.ts(918,59): error TS7006: Parameter 'permission' implicitly has an 'any' type.
Error: electron/spec/chromium-spec.ts(918,71): error TS7006: Parameter 'callback' implicitly has an 'any' type.
```

#### 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] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [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: none


Changed files:
filename: spec/chromium-spec.ts
patch: @@ -915,7 +915,7 @@ describe('chromium features', () => {
 
           if (action !== 'none') {
             // Make the PermissionRequestHandler behave according to action variable passed for this test
-            testSession.setPermissionRequestHandler((_wc, permission, callback) => {
+            testSession.setPermissionRequestHandler((_wc: Electron.WebContents, permission: string, callback: (allow: boolean) => void) => {
               if (permission === 'geolocation') {
                 if (action === 'allow') callback(true);
                 else if (action === 'deny') callback(false);
Repository: nodejs/node
Pull request: doc: add fullName property to SuiteContext

The fullName property exists on SuiteContext at runtime but was not documented.

Tested to verify behavior:
- Top-level suite: returns suite name
- Nested suite: returns "Parent > Child" format  
- Implementation confirmed in lib/internal/test_runner/test.js (line 495)

Fixes: #60757

Changed files:
filename: doc/api/test.md
patch: @@ -3667,7 +3667,9 @@ the path of the root test file.
 ### `context.fullName`
 
 <!-- YAML
-added: v22.3.0
+added:
+  - v22.3.0
+  - v20.16.0
 -->
 
 The name of the test and each of its ancestors, separated by `>`.
@@ -3970,6 +3972,16 @@ The absolute path of the test file that created the current suite. If a test
 file imports additional modules that generate suites, the imported suites will
 return the path of the root test file.
 
+### `context.fullName`
+
+<!-- YAML
+added:
+  - v22.3.0
+  - v20.16.0
+-->
+
+The name of the suite and each of its ancestors, separated by `>`.
+
 ### `context.name`
 
 <!-- YAML
Repository: facebook/react
Pull request: [ci] Rename other stale branch workflow


Makes it easier to tell what is what
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32692).
* __->__ #32692
* #32691

Changed files:
filename: .github/workflows/shared_cleanup_merged_branch_caches.yml
patch: @@ -1,6 +1,6 @@
 # https://github.com/actions/cache/blob/main/tips-and-workarounds.md#force-deletion-of-caches-overriding-default-cache-eviction-policy
 
-name: (Shared) Cleanup Branch Caches
+name: (Shared) Cleanup Merged Branch Caches
 on:
   pull_request:
     types:
Repository: ollama/ollama
Pull request: fix: typo in wintray messages const

Found small typo in const name

Changed files:
filename: app/tray/wintray/menus.go
patch: @@ -39,7 +39,7 @@ func (t *winTray) UpdateAvailable(ver string) error {
 		if err := t.addOrUpdateMenuItem(updateAvailableMenuID, 0, updateAvailableMenuTitle, true); err != nil {
 			return fmt.Errorf("unable to create menu entries %w", err)
 		}
-		if err := t.addOrUpdateMenuItem(updateMenuID, 0, updateMenutTitle, false); err != nil {
+		if err := t.addOrUpdateMenuItem(updateMenuID, 0, updateMenuTitle, false); err != nil {
 			return fmt.Errorf("unable to create menu entries %w", err)
 		}
 		if err := t.addSeparatorMenuItem(separatorMenuID, 0); err != nil {

filename: app/tray/wintray/messages.go
patch: @@ -10,6 +10,6 @@ const (
 
 	quitMenuTitle            = "Quit Ollama"
 	updateAvailableMenuTitle = "An update is available"
-	updateMenutTitle         = "Restart to update"
+	updateMenuTitle          = "Restart to update"
 	diagLogsMenuTitle        = "View logs"
 )
Repository: huggingface/transformers
Pull request: Add requires_backends to the main init

Fixes https://github.com/huggingface/transformers/issues/42778

Changed files:
filename: docs/source/en/internal/import_utils.md
patch: @@ -97,3 +97,5 @@ You can specify the following operators: `==`, `>`, `>=`, `<`, `<=`, `!=`.
 [[autodoc]] utils.import_utils.define_import_structure
 
 [[autodoc]] utils.import_utils.requires
+
+[[autodoc]] utils.import_utils.requires_backends
\ No newline at end of file

filename: src/transformers/__init__.py
patch: @@ -266,6 +266,7 @@
     ],
     "video_utils": [],
     "utils.kernel_config": ["KernelConfig"],
+    "utils.import_utils": ["requires_backends"],
 }
 
 # tokenizers-backed objects
@@ -750,6 +751,7 @@
     from .utils import is_torch_npu_available as is_torch_npu_available
     from .utils import is_torch_xla_available as is_torch_xla_available
     from .utils import is_torch_xpu_available as is_torch_xpu_available
+    from .utils.import_utils import requires_backends
     from .utils.kernel_config import KernelConfig as KernelConfig
 
     # Quantization config

filename: src/transformers/utils/import_utils.py
patch: @@ -1825,6 +1825,20 @@ def is_training_run_on_sagemaker() -> bool:
 
 
 def requires_backends(obj, backends):
+    """
+    Method that automatically raises in case the specified backends are not available. It is often used during class
+    initialization to ensure the required dependencies are installed:
+
+    ```py
+    requires_backends(self, ["torch"])
+    ```
+
+    The backends should be defined in the `BACKEND_MAPPING` defined in `transformers.utils.import_utils`.
+
+    Args:
+        obj: object to be checked
+        backends: list or tuple of backends to check.
+    """
     if not isinstance(backends, (list, tuple)):
         backends = [backends]
Repository: electron/electron
Pull request: fix: restore window's canHide property on macOS

#### Description of Change

If calling `app.dock?.hide()` and hiding the window, even if the window is restored, window can no longer be hided.
It due to API set canHide property while calling  `app.dock?.hide()`
https://github.com/electron/electron/blob/678fb400fdb465fbfccd77681f32728a5f86e9bd/shell/browser/browser_mac.mm#L531-L532

#### 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] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [x] relevant API documentation, tutorials, and examples are updated and follow the [documentation style guide](https://github.com/electron/electron/blob/main/docs/development/style-guide.md)
- [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: Restored window's canHide property

Changed files:
filename: shell/browser/browser_mac.mm
patch: @@ -543,6 +543,9 @@ LoginItemSettings GetLoginItemSettingsDeprecated() {
   gin_helper::Promise<void> promise(isolate);
   v8::Local<v8::Promise> handle = promise.GetHandle();
 
+  for (auto* const& window : WindowList::GetWindows())
+    [window->GetNativeWindow().GetNativeNSWindow() setCanHide:YES];
+
   BOOL active = [[NSRunningApplication currentApplication] isActive];
   ProcessSerialNumber psn = {0, kCurrentProcess};
   if (active) {
Repository: vuejs/vue
Pull request: replace Firefix with Firefox

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe:

`Firefox has a "watch" function...`, not `Firefix has a "watch" function...`

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [ ] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [ ] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [ ] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**


Changed files:
filename: src/core/util/env.js
patch: @@ -17,7 +17,7 @@ export const isAndroid = UA && UA.indexOf('android') > 0
 export const isIOS = UA && /iphone|ipad|ipod|ios/.test(UA)
 export const isChrome = UA && /chrome\/\d+/.test(UA) && !isEdge
 
-// Firefix has a "watch" function on Object.prototype...
+// Firefox has a "watch" function on Object.prototype...
 export const nativeWatch = ({}).watch
 
 export let supportsPassive = false