helloadhavan/github_issues huggingface dataset:
Repository: vuejs/vue
Pull request: Special attributes are invalid when using object syntax in v-bind, fix #5881

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

https://github.com/vuejs/vue/issues/5881

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**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:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] 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: test/unit/features/options/props.spec.js
patch: @@ -490,11 +490,12 @@ describe('Options props', () => {
   })
 
   it('warn reserved props', () => {
+    const specialAttrs = ['key', 'ref', 'slot', 'is']
     new Vue({
-      props: {
-        key: String
-      }
+      props: specialAttrs
+    })
+    specialAttrs.forEach(attr => {
+      expect(`"${attr}" is a reserved attribute`).toHaveBeenWarned()
     })
-    expect(`"key" is a reserved attribute`).toHaveBeenWarned()
   })
 })
Repository: ollama/ollama
Pull request: add Llama Coder

Hey, i have created a plugin for VS Code that integrates with ollama!

Changed files:
filename: README.md
patch: @@ -272,3 +272,4 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Discord AI Bot](https://github.com/mekb-turtle/discord-ai-bot)
 - [Hass Ollama Conversation](https://github.com/ej52/hass-ollama-conversation)
 - [Rivet plugin](https://github.com/abrenneke/rivet-plugin-ollama)
+- [Llama Coder](https://github.com/ex3ndr/llama-coder) (Copilot alternative using Ollama)
Repository: facebook/react
Pull request: [Fizz] Clean up the replay nodes if we're already rendered past an element 

Follow up to #27513. There's two issues here.

First, we didn't restore the ReplaySet when calling `renderNode()` so it was not safe to invoke since future siblings might observe the mutated replay. This could skip replays which covered up errors.

Second, this was covering up that we weren't properly cleaning up the replay nodes when we were able to render through one node and then mutated the `.node` on the task but then suspended deeper.

I don't love the solution from #27513 in general because it feels hacky to compare the mutated node. It should probably be structured different. There's also another case that's basically the same case which has neither of these fixes in it. It's probably a bug too but haven't been able to repro yet:

https://github.com/facebook/react/blob/a947eba4f2c8741d2c61a3b33fd79cf13bf9f39d/packages/react-server/src/ReactFizzServer.js#L3612-L3613

Changed files:
filename: packages/react-server/src/ReactFizzServer.js
patch: @@ -3099,6 +3099,9 @@ function replayElement(
           if (task.node === currentNode) {
             // This same element suspended so we need to pop the replay we just added.
             task.replay = replay;
+          } else {
+            // We finished rendering this node, so now we can consume this slot.
+            replayNodes.splice(i, 1);
           }
           throw x;
         }
@@ -4127,6 +4130,8 @@ function renderNode(
   const segment = task.blockedSegment;
   if (segment === null) {
     // Replay
+    task = ((task: any): ReplayTask); // Refined
+    const previousReplaySet: ReplaySet = task.replay;
     try {
       return renderNodeDestructive(request, task, node, childIndex);
     } catch (thrownValue) {
@@ -4166,6 +4171,7 @@ function renderNode(
           task.keyPath = previousKeyPath;
           task.treeContext = previousTreeContext;
           task.componentStack = previousComponentStack;
+          task.replay = previousReplaySet;
           if (__DEV__) {
             task.debugTask = previousDebugTask;
           }
@@ -4199,6 +4205,7 @@ function renderNode(
           task.keyPath = previousKeyPath;
           task.treeContext = previousTreeContext;
           task.componentStack = previousComponentStack;
+          task.replay = previousReplaySet;
           if (__DEV__) {
             task.debugTask = previousDebugTask;
           }
Repository: vuejs/vue
Pull request: [automated] Patreon sponsors update

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -21,7 +21,7 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
     <img width="260px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/stdlib.png">
   </a>
 </p>
-
+  
 <!--special end-->
 
 <h2 align="center">Platinum via Patreon</h2>
@@ -194,6 +194,11 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
           <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/marcus_hiles.png">
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="https://intygrate.com/" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/intygrate.png">
+        </a>
+      </td>
       <td align="center" valign="middle">
         <a href="https://isleofcode.com/" target="_blank">
           <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/isle_of_code.png">

filename: README.md
patch: @@ -31,7 +31,7 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
     <img width="260px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/stdlib.png">
   </a>
 </p>
-
+  
 <!--special end-->
 
 <h3 align="center">Platinum Sponsors</h3>
@@ -199,6 +199,11 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
           <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/marcus_hiles.png">
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="https://intygrate.com/" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/intygrate.png">
+        </a>
+      </td>
       <td align="center" valign="middle">
         <a href="https://isleofcode.com/" target="_blank">
           <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/isle_of_code.png">
Repository: ggml-org/llama.cpp
Pull request: vulkan: enable Conv2D for Apple after MoltenVK fixed the bug

The bug that caused Conv2D shader compile failure on MoltenVK has been fixed in 1.4.0. Remove the workaround for it.

Changed files:
filename: ggml/src/ggml-vulkan/ggml-vulkan.cpp
patch: @@ -11853,14 +11853,13 @@ static bool ggml_backend_vk_device_supports_op(ggml_backend_dev_t dev, const ggm
                 // Op is disabled for Apple because it segfaults at pipeline create time on MoltenVK
                 ggml_backend_vk_device_context * ctx = (ggml_backend_vk_device_context *)dev->context;
                 const vk_device& device = ggml_vk_get_device(ctx->device);
-                bool is_Apple = ggml_vk_get_device(ctx->device)->vendor_id == VK_VENDOR_ID_APPLE;
                 // Channel-contiguous format is not supported yet.
                 return ((op->src[0]->type == GGML_TYPE_F32 || op->src[0]->type == GGML_TYPE_F16) &&
                     op->src[1]->type == GGML_TYPE_F32 &&
                     op->type == GGML_TYPE_F32 &&
                     ggml_is_contiguous(op->src[0]) &&
                     ggml_is_contiguous(op->src[1]) &&
-                    ggml_is_contiguous(op)) && !is_Apple;
+                    ggml_is_contiguous(op));
             }
         default:
             return false;
Repository: ollama/ollama
Pull request: server/internal/client/ollama: set User-Agent for registry client

This sets the agent header in DefaultRegistry to include the version of
the client, OS, and architecture in the previous format, with a minor
twist.

Note: The version is obtained from the build info, instead of the
version in version.Version, which should not longer be necessary, but we
can remove in a future commit. Using the build info is more accurate and
also provides extra build information if the build is not tagged, and if
it is "dirty". Previously, the version was just "0.0.0" with no other
helpful information. The ollama.com registry and others handle this
swimmingly.


Changed files:
filename: server/internal/client/ollama/registry.go
patch: @@ -25,6 +25,7 @@ import (
 	"os"
 	"path/filepath"
 	"runtime"
+	"runtime/debug"
 	"slices"
 	"strconv"
 	"strings"
@@ -259,6 +260,7 @@ func DefaultRegistry() (*Registry, error) {
 	}
 
 	var rc Registry
+	rc.UserAgent = UserAgent()
 	rc.Key, err = ssh.ParseRawPrivateKey(keyPEM)
 	if err != nil {
 		return nil, err
@@ -274,6 +276,16 @@ func DefaultRegistry() (*Registry, error) {
 	return &rc, nil
 }
 
+func UserAgent() string {
+	buildinfo, _ := debug.ReadBuildInfo()
+	return fmt.Sprintf("ollama/%s (%s %s) Go/%s",
+		buildinfo.Main.Version,
+		runtime.GOARCH,
+		runtime.GOOS,
+		runtime.Version(),
+	)
+}
+
 func (r *Registry) maxStreams() int {
 	return cmp.Or(r.MaxStreams, runtime.GOMAXPROCS(0))
 }
Repository: facebook/react
Pull request: Make it clearer what runtime release failed

I thought somebody was experimenting with another release. This hopefully reduces future confusion.

```diff
-Publish of $stable release failed
+[Runtime] Publish of stable@next,canary release failed

Changed files:
filename: .github/workflows/runtime_prereleases.yml
patch: @@ -108,5 +108,5 @@ jobs:
         with:
           webhook-url: ${{ secrets.DISCORD_WEBHOOK_URL }}
           embed-author-name: "GitHub Actions"
-          embed-title: 'Publish of $${{ inputs.release_channel }} release failed'
+          embed-title: '[Runtime] Publish of ${{ inputs.release_channel }}@${{ inputs.dist_tag}} release failed'
           embed-url: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}/attempts/${{ github.run_attempt }}
Repository: vercel/next.js
Pull request: [test] Skip failing deploy test in `searchparams-reuse-loading.test.ts`

`searchparams-reuse-loading With Middleware should correctly return different RSC data for full prefetches with different searchParam values` has been failing for the past 3 months which was hidden by not running the test consistently across retries.

Skipping it unless we find out why until Thursday.

Part of https://linear.app/vercel/issue/NAR-719/

Changed files:
filename: test/deploy-tests-manifest.json
patch: @@ -41,6 +41,11 @@
         "app dir - metadata react cache should have same title and page value when navigating"
       ]
     },
+    "test/e2e/app-dir/searchparams-reuse-loading/searchparams-reuse-loading.test.ts": {
+      "failed": [
+        "searchparams-reuse-loading With Middleware should correctly return different RSC data for full prefetches with different searchParam values"
+      ]
+    },
     "test/e2e/middleware-rewrites/test/index.test.ts": {
       "failed": ["Middleware Rewrite should handle catch-all rewrite correctly"]
     }

filename: test/e2e/app-dir/searchparams-reuse-loading/searchparams-reuse-loading.test.ts
patch: @@ -173,6 +173,7 @@ describe('searchparams-reuse-loading', () => {
       { path: '/with-middleware', label: 'With Middleware' },
     ])('$label', ({ path }) => {
       it('should correctly return different RSC data for full prefetches with different searchParam values', async () => {
+        // TODO: Skipped in deploy tests when middleware is present
         const rscRequestPromise = new Map<
           string,
           { resolve: () => Promise<void> }
Repository: huggingface/transformers
Pull request: [Bugfix][informer]: Correct tensor shape for input_size=1

Hi @Rocketknight1, thanks for the great guidance on the previous PR!

This new pull request follows your suggestion to fix the bug at its source. It resolves a RuntimeError that occurs in time series models inheriting from TimeSeriesTransformerModel (such as InformerModel) when config.input_size is set to 1.

The root cause was that when `input_size=1`, the loc and scale tensors calculated by the scaler retained an extra dimension (e.g., shape [B, 1, 1] instead of [B, 1]). This incorrect shape caused a dimension mismatch error during a later expand() operation.

Instead of overriding the method in the child class, this PR applies a minimal and robust fix directly to the create_network_inputs method in the parent TimeSeriesTransformerModel. It refactors the logic to unconditionally apply .squeeze(1) to both the loc and scale tensors. This approach handles all input_size cases correctly and avoids code duplication.

Fixes #38745

Changed files:
filename: src/transformers/models/informer/modeling_informer.py
patch: @@ -1461,8 +1461,14 @@ def create_network_inputs(
         )
 
         # static features
-        log_abs_loc = loc.abs().log1p() if self.config.input_size == 1 else loc.squeeze(1).abs().log1p()
-        log_scale = scale.log() if self.config.input_size == 1 else scale.squeeze(1).log()
+        if loc.ndim == 3:
+            squeezed_loc = loc.squeeze(1)
+            squeezed_scale = scale.squeeze(1)
+        else:
+            squeezed_loc = loc
+            squeezed_scale = scale
+        log_abs_loc = squeezed_loc.abs().log1p()
+        log_scale = squeezed_scale.log()
         static_feat = torch.cat((log_abs_loc, log_scale), dim=1)
 
         if static_real_features is not None:

filename: src/transformers/models/time_series_transformer/modeling_time_series_transformer.py
patch: @@ -1228,8 +1228,14 @@ def create_network_inputs(
         )
 
         # static features
-        log_abs_loc = loc.abs().log1p() if self.config.input_size == 1 else loc.squeeze(1).abs().log1p()
-        log_scale = scale.log() if self.config.input_size == 1 else scale.squeeze(1).log()
+        if loc.ndim == 3:
+            squeezed_loc = loc.squeeze(1)
+            squeezed_scale = scale.squeeze(1)
+        else:
+            squeezed_loc = loc
+            squeezed_scale = scale
+        log_abs_loc = squeezed_loc.abs().log1p()
+        log_scale = squeezed_scale.log()
         static_feat = torch.cat((log_abs_loc, log_scale), dim=1)
 
         if static_real_features is not None:
Repository: ggml-org/llama.cpp
Pull request: Vulkan: Fix fprintf format-security warning

Fixes #14745 

Changed files:
filename: ggml/src/ggml-vulkan/vulkan-shaders/vulkan-shaders-gen.cpp
patch: @@ -765,8 +765,8 @@ void write_output_files() {
                 len += "};\n";
             }
         }
-        fprintf(src, data.c_str());
-        fprintf(src, len.c_str());
+        fputs(data.c_str(), src);
+        fputs(len.c_str(), src);
     }
     fclose(hdr);
     fclose(src);
Repository: vuejs/vue
Pull request: update README.md

<!--
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:
Github ignores the extra "\`", but other markdown editor detects the syntax problem of this `README.md` file.

**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:**

- [x] 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:**
It's a documentation fix.

Changed files:
filename: dist/README.md
patch: @@ -40,7 +40,7 @@ module.exports = {
     }
   }
 }
-````
+```
 
 #### Rollup
Repository: vercel/next.js
Pull request: Turbopack: MappedReadRef should be Send and Sync

### What?

To be able to used MappedReadRefs in async context, they need to be Send.

Changed files:
filename: turbopack/crates/turbo-tasks/src/lib.rs
patch: @@ -56,11 +56,11 @@ mod invalidation;
 mod join_iter_ext;
 mod key_value_pair;
 pub mod keyed;
-pub mod keyed_read_ref;
 #[doc(hidden)]
 pub mod macro_helpers;
 mod magic_any;
 mod manager;
+pub mod mapped_read_ref;
 mod marker_trait;
 pub mod message_queue;
 mod native_function;
@@ -119,6 +119,7 @@ pub use crate::{
         mark_session_dependent, prevent_gc, run, run_once, run_once_with_reason, trait_call,
         turbo_tasks, turbo_tasks_scope, turbo_tasks_weak, with_turbo_tasks,
     },
+    mapped_read_ref::MappedReadRef,
     output::OutputContent,
     raw_vc::{CellId, RawVc, ReadRawVcFuture, ResolveTypeError},
     read_options::{ReadCellOptions, ReadOutputOptions},

filename: turbopack/crates/turbo-tasks/src/mapped_read_ref.rs
patch: @@ -13,6 +13,9 @@ pub struct MappedReadRef<A, T> {
     arc: triomphe::Arc<A>,
 }
 
+unsafe impl<A: Send + Sync, T: Sync> Send for MappedReadRef<A, T> {}
+unsafe impl<A: Send + Sync, T: Sync> Sync for MappedReadRef<A, T> {}
+
 impl<A, T> MappedReadRef<A, T> {
     /// # Safety
     /// The caller must ensure that the `arc` keeps the value pointed to by `value` alive.

filename: turbopack/crates/turbo-tasks/src/vc/read.rs
patch: @@ -14,8 +14,8 @@ use rustc_hash::FxBuildHasher;
 
 use super::traits::VcValueType;
 use crate::{
-    ReadRawVcFuture, ReadRef, VcCast, VcValueTrait, VcValueTraitCast, VcValueTypeCast,
-    keyed::Keyed, keyed_read_ref::MappedReadRef,
+    MappedReadRef, ReadRawVcFuture, ReadRef, VcCast, VcValueTrait, VcValueTraitCast,
+    VcValueTypeCast, keyed::Keyed,
 };
 
 type VcReadTarget<T> = <<T as VcValueType>::Read as VcRead<T>>::Target;
Repository: facebook/react
Pull request: build: make enableComponentPerformanceTrack dynamic for native-fb

## Summary

Make this flag dynamic, so it can be controlled internally.

## How did you test this change?

Build, observe that `console.timeStamp` is only present in FB artifacts and `enableComponentPerformanceTrack` is referenced.


Changed files:
filename: packages/shared/forks/ReactFeatureFlags.native-fb-dynamic.js
patch: @@ -26,3 +26,4 @@ export const passChildrenWhenCloningPersistedNodes = __VARIANT__;
 export const enableLazyPublicInstanceInFabric = __VARIANT__;
 export const renameElementSymbol = __VARIANT__;
 export const enableFragmentRefs = __VARIANT__;
+export const enableComponentPerformanceTrack = __VARIANT__;

filename: packages/shared/forks/ReactFeatureFlags.native-fb.js
patch: @@ -59,7 +59,6 @@ export const enableProfilerTimer = __PROFILE__;
 export const enableReactTestRendererWarning = false;
 export const enableRetryLaneExpiration = false;
 export const enableSchedulingProfiler = __PROFILE__;
-export const enableComponentPerformanceTrack = false;
 export const enableScopeAPI = false;
 export const enableSuspenseAvoidThisFallback = false;
 export const enableSuspenseCallback = true;
@@ -84,6 +83,8 @@ export const enableSrcObject = false;
 export const enableHydrationChangeEvent = true;
 export const enableDefaultTransitionIndicator = false;
 export const ownerStackLimit = 1e4;
+export const enableComponentPerformanceTrack: boolean =
+  __PROFILE__ && dynamicFlags.enableComponentPerformanceTrack;
 
 // Flow magic to verify the exports of this file match the original version.
 ((((null: any): ExportsType): FeatureFlagsType): ExportsType);
Repository: huggingface/transformers
Pull request: fix: Correct ESM TrunkConfig self-modulo in validation

### What does this PR do?

`TrunkConfig` validation contained a self-modulo check that would never trigger (dead code). This PR corrects the divisibility check to use the head width instead.

Fixes #43347.

### Before submitting

* [x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
* [x] Did you read the [[contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request)](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
  Pull Request section?
* [x] Was this discussed/approved via a GitHub issue or the [[forum](https://discuss.huggingface.co/)](https://discuss.huggingface.co/)? Please add a link
  to it if that's the case.
* [x] Did you make sure to update the documentation with your changes? Here are the
  [[documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs)](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)](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).

cc: @sayakpaul @Rocketknight1

Changed files:
filename: src/transformers/models/esm/configuration_esm.py
patch: @@ -101,16 +101,6 @@ def __post_init__(self):
 
         if self.max_recycles <= 0:
             raise ValueError(f"`max_recycles` should be positive, got {self.max_recycles}.")
-        if self.sequence_state_dim % self.sequence_state_dim != 0:
-            raise ValueError(
-                "`sequence_state_dim` should be a round multiple of `sequence_state_dim`, got"
-                f" {self.sequence_state_dim} and {self.sequence_state_dim}."
-            )
-        if self.pairwise_state_dim % self.pairwise_state_dim != 0:
-            raise ValueError(
-                "`pairwise_state_dim` should be a round multiple of `pairwise_state_dim`, got"
-                f" {self.pairwise_state_dim} and {self.pairwise_state_dim}."
-            )
 
         sequence_num_heads = self.sequence_state_dim // self.sequence_head_width
         pairwise_num_heads = self.pairwise_state_dim // self.pairwise_head_width