helloadhavan/github_issues huggingface dataset:
Repository: denoland/deno
Pull request: fix(init): eliminate flickering progress bar

It's nice and smooth after this change (bad warning symbol is fixed in a different pr).


https://github.com/user-attachments/assets/185d9c66-f691-4d55-accc-c18353f6cd4f



Changed files:
filename: cli/factory.rs
patch: @@ -1042,6 +1042,7 @@ impl CliFactory {
       self.maybe_lockfile().await?.cloned(),
       self.npm_installer_if_managed().await?.cloned(),
       npm_resolver.clone(),
+      self.text_only_progress_bar().clone(),
       self.sys(),
       self.create_cli_main_worker_options()?,
       self.root_permissions_container()?.clone(),

filename: cli/worker.rs
patch: @@ -33,6 +33,7 @@ use crate::tools::coverage::CoverageCollector;
 use crate::tools::run::hmr::HmrRunner;
 use crate::util::file_watcher::WatcherCommunicator;
 use crate::util::file_watcher::WatcherRestartMode;
+use crate::util::progress_bar::ProgressBar;
 
 pub type CreateHmrRunnerCb =
   Box<dyn Fn(deno_core::LocalInspectorSession) -> HmrRunner + Send + Sync>;
@@ -318,6 +319,7 @@ pub struct CliMainWorkerFactory {
   maybe_lockfile: Option<Arc<CliLockfile>>,
   npm_installer: Option<Arc<CliNpmInstaller>>,
   npm_resolver: CliNpmResolver,
+  progress_bar: ProgressBar,
   root_permissions: PermissionsContainer,
   shared: Arc<SharedState>,
   sys: CliSys,
@@ -333,6 +335,7 @@ impl CliMainWorkerFactory {
     maybe_lockfile: Option<Arc<CliLockfile>>,
     npm_installer: Option<Arc<CliNpmInstaller>>,
     npm_resolver: CliNpmResolver,
+    progress_bar: ProgressBar,
     sys: CliSys,
     options: CliMainWorkerOptions,
     root_permissions: PermissionsContainer,
@@ -342,6 +345,7 @@ impl CliMainWorkerFactory {
       maybe_lockfile,
       npm_installer,
       npm_resolver,
+      progress_bar,
       root_permissions,
       sys,
       shared: Arc::new(SharedState {
@@ -408,6 +412,7 @@ impl CliMainWorkerFactory {
     {
       Ok(package_ref) => {
         if let Some(npm_installer) = &self.npm_installer {
+          let _clear_guard = self.progress_bar.deferred_keep_initialize_alive();
           let reqs = &[package_ref.req().clone()];
           npm_installer
             .add_package_reqs(
Repository: ollama/ollama
Pull request: fix empty response


Changed files:
filename: llm/ggml_llama.go
patch: @@ -497,8 +497,10 @@ func (llm *llama) Predict(ctx context.Context, prevContext []int, prompt string,
 					return fmt.Errorf("error unmarshaling llm prediction response: %v", err)
 				}
 
-				fn(api.GenerateResponse{Response: p.Content})
-				nextContext.WriteString(p.Content)
+				if p.Content != "" {
+					fn(api.GenerateResponse{Response: p.Content})
+					nextContext.WriteString(p.Content)
+				}
 
 				if p.Stop {
 					embd, err := llm.Encode(ctx, nextContext.String())
Repository: vercel/next.js
Pull request: Turbopack: patch sourcemap crate

The source content was somethings incorrect with scope hoisting on Turbopack:

<img width="2018" height="721" alt="image" src="https://github.com/user-attachments/assets/e2e1bf1c-2a84-4acb-8388-a809670b4902" />

Fix is in https://github.com/swc-project/swc-sourcemap/pull/7

Changed files:
filename: Cargo.lock
patch: @@ -8246,8 +8246,7 @@ dependencies = [
 [[package]]
 name = "swc_sourcemap"
 version = "9.3.3"
-source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "3cd6e0cad02163875258edaf9ae6004e2526be137bdde6a46c540515615949b1"
+source = "git+https://github.com/mischnic/rust-sourcemap.git?branch=mischnic%2Fsource-content-mixup#a11f621393345e87145108da20dffb310b5dbfd4"
 dependencies = [
  "base64-simd 0.8.0",
  "bitvec",

filename: Cargo.toml
patch: @@ -450,3 +450,4 @@ hyper = { git = "https://github.com/bgw/hyper-rs.git", branch = "v1.6.0-with-mac
 mdxjs = { git = "https://github.com/mischnic/mdxjs-rs.git", branch = "swc-core-32" }
 lightningcss = { git = "https://github.com/parcel-bundler/lightningcss.git", branch = "mischnic/bump-browserslist" }
 parcel_selectors = { git = "https://github.com/parcel-bundler/lightningcss.git", branch = "mischnic/bump-browserslist" }
+swc_sourcemap = { git = "https://github.com/mischnic/rust-sourcemap.git", branch = "mischnic/source-content-mixup" }
Repository: ggml-org/llama.cpp
Pull request: devops: add s390x release binaries

This PR introduces the s390x binaries to be released in https://github.com/ggml-org/llama.cpp/releases.

We have to specify a suffix of `z15` for now as the CI used is an IBM z15. IBM z16 and later systems can use the z15 binaries provided but will not get better performance improvements as the instruction set is not optimised for the newer systems.

We also unfortunately do not provide IBM zDNN backend binaries for now because it is only available on IBM z17 and later systems, which our CI is not at that hardware level yet.

Changed files:
filename: .github/workflows/release.yml
patch: @@ -134,6 +134,8 @@ jobs:
         include:
           - build: 'x64'
             os: ubuntu-22.04
+          - build: 's390x-z15' # z15 because our CI runners are on z15
+            os: ubuntu-22.04-s390x
           # GGML_BACKEND_DL and GGML_CPU_ALL_VARIANTS are not currently supported on arm
           # - build: 'arm64'
           #   os: ubuntu-22.04-arm
Repository: denoland/deno
Pull request: fix: do not have duplicate progress bars for post install scripts


Changed files:
filename: cli/factory.rs
patch: @@ -562,10 +562,12 @@ impl CliFactory {
           self.text_only_progress_bar().clone(),
         )),
         match resolver_factory.npm_resolver()?.as_managed() {
-          Some(managed_npm_resolver) => Arc::new(
-            DenoTaskLifeCycleScriptsExecutor::new(managed_npm_resolver.clone()),
-          )
-            as Arc<dyn LifecycleScriptsExecutor>,
+          Some(managed_npm_resolver) => {
+            Arc::new(DenoTaskLifeCycleScriptsExecutor::new(
+              managed_npm_resolver.clone(),
+              self.text_only_progress_bar().clone(),
+            )) as Arc<dyn LifecycleScriptsExecutor>
+          }
           None => Arc::new(NullLifecycleScriptsExecutor),
         },
         self.text_only_progress_bar().clone(),

filename: cli/npm.rs
patch: @@ -275,6 +275,7 @@ pub enum DenoTaskLifecycleScriptsError {
 }
 
 pub struct DenoTaskLifeCycleScriptsExecutor {
+  progress_bar: ProgressBar,
   npm_resolver: ManagedNpmResolverRc<CliSys>,
 }
 
@@ -348,10 +349,7 @@ impl LifecycleScriptsExecutor for DenoTaskLifeCycleScriptsExecutor {
           {
             continue;
           }
-          let pb = ProgressBar::new(
-            crate::util::progress_bar::ProgressBarStyle::TextOnly,
-          );
-          let _guard = pb.update_with_prompt(
+          let _guard = self.progress_bar.update_with_prompt(
             ProgressMessagePrompt::Initialize,
             &format!("{}: running '{script_name}' script", package.id.nv),
           );
@@ -444,8 +442,14 @@ impl LifecycleScriptsExecutor for DenoTaskLifeCycleScriptsExecutor {
 }
 
 impl DenoTaskLifeCycleScriptsExecutor {
-  pub fn new(npm_resolver: ManagedNpmResolverRc<CliSys>) -> Self {
-    Self { npm_resolver }
+  pub fn new(
+    npm_resolver: ManagedNpmResolverRc<CliSys>,
+    progress_bar: ProgressBar,
+  ) -> Self {
+    Self {
+      npm_resolver,
+      progress_bar,
+    }
   }
 
   // take in all (non copy) packages from snapshot,
Repository: nodejs/node
Pull request: doc: add path rules and validation for export targets in package.json

Close #58576

I have added a new section called `# Path Rules and Validation for Export Targets` that goes over the invalid paths that are possible & and their valid counter parts

Changed files:
filename: doc/api/packages.md
patch: @@ -433,6 +433,59 @@ subpaths where possible instead of a separate map entry per package subpath
 export. This also mirrors the requirement of using [the full specifier path][]
 in relative and absolute import specifiers.
 
+#### Path Rules and Validation for Export Targets
+
+When defining paths as targets in the [`"exports"`][] field, Node.js enforces
+several rules to ensure security, predictability, and proper encapsulation.
+Understanding these rules is crucial for authors publishing packages.
+
+##### Targets must be relative URLs
+
+All target paths in the [`"exports"`][] map (the values associated with export
+keys) must be relative URL strings starting with `./`.
+
+```json
+// package.json
+{
+  "name": "my-package",
+  "exports": {
+    ".": "./dist/main.js",          // Correct
+    "./feature": "./lib/feature.js", // Correct
+    // "./origin-relative": "/dist/main.js", // Incorrect: Must start with ./
+    // "./absolute": "file:///dev/null", // Incorrect: Must start with ./
+    // "./outside": "../common/util.js" // Incorrect: Must start with ./
+  }
+}
+```
+
+Reasons for this behavior include:
+
+* **Security:** Prevents exporting arbitrary files from outside the
+  package's own directory.
+* **Encapsulation:** Ensures all exported paths are resolved relative to
+  the package root, making the package self-contained.
+
+##### No path traversal or invalid segments
+
+Export targets must not resolve to a location outside the package's root
+directory. Additionally, path segments like `.` (single dot), `..` (double dot),
+or `node_modules` (and their URL-encoded equivalents) are generally disallowed
+within the `target` string after the initial `./` and in any `subpath` part
+substituted into a target pattern.
+
+```json
+// package.json
+{
+  "name": "my-package",
+  "exports": {
+    // ".": "./dist/../../elsewhere/file.js", // Invalid: path traversal
+    // ".": "././dist/main.js",             // Invalid: contains "." segment
+    // ".": "./dist/../dist/main.js",       // Invalid: contains ".." segment
+    // "./utils/./helper.js": "./utils/helper.js" // Key has invalid segment
+  }
+}
+```
+
 ### Exports sugar
 
 <!-- YAML
Repository: electron/electron
Pull request: fix: leaked `gfx::Canvas` in `AutofillPopupView::OnPaint()`

#### Description of Change

Fix a memory leak in AutofillPopupView.

A `gfx::Canvas` was leaked each time `AutofillPopupView::OnPaint()` was called when the popup view had an `OffscreenViewProxy`.

#### Checklist

- [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 memory leak in AutofillPopupView.

Changed files:
filename: shell/browser/ui/views/autofill_popup_view.cc
patch: @@ -5,6 +5,7 @@
 #include "shell/browser/ui/views/autofill_popup_view.h"
 
 #include <memory>
+#include <optional>
 #include <utility>
 
 #include "base/functional/bind.h"
@@ -237,30 +238,33 @@ void AutofillPopupView::DoUpdateBoundsAndRedrawPopup() {
 void AutofillPopupView::OnPaint(gfx::Canvas* canvas) {
   if (!popup_ || static_cast<size_t>(popup_->line_count()) != children().size())
     return;
-  gfx::Canvas* draw_canvas = canvas;
-  SkBitmap bitmap;
 
-  std::unique_ptr<cc::SkiaPaintCanvas> paint_canvas;
-  if (view_proxy_.get()) {
-    bitmap.allocN32Pixels(popup_->popup_bounds_in_view().width(),
-                          popup_->popup_bounds_in_view().height(), true);
-    paint_canvas = std::make_unique<cc::SkiaPaintCanvas>(bitmap);
-    draw_canvas = new gfx::Canvas(paint_canvas.get(), 1.0);
+  gfx::Rect offscreen_bounds;
+  SkBitmap offscreen_bitmap;
+  std::optional<cc::SkiaPaintCanvas> offscreen_paint_canvas;
+  std::optional<gfx::Canvas> offscreen_draw_canvas;
+  if (view_proxy_) {
+    offscreen_bounds = popup_->popup_bounds_in_view();
+    offscreen_bitmap.allocN32Pixels(offscreen_bounds.width(),
+                                    offscreen_bounds.height(), true);
+    offscreen_paint_canvas.emplace(offscreen_bitmap);
+    offscreen_draw_canvas.emplace(&offscreen_paint_canvas.value(), 1.0);
+    canvas = &offscreen_draw_canvas.value();
   }
 
-  draw_canvas->DrawColor(
+  canvas->DrawColor(
       GetColorProvider()->GetColor(ui::kColorResultsTableNormalBackground));
-  OnPaintBorder(draw_canvas);
+  OnPaintBorder(canvas);
 
   for (int i = 0; i < popup_->line_count(); ++i) {
     gfx::Rect line_rect = popup_->GetRowBounds(i);
 
-    DrawAutofillEntry(draw_canvas, i, line_rect);
+    DrawAutofillEntry(canvas, i, line_rect);
   }
 
-  if (view_proxy_.get()) {
-    view_proxy_->SetBounds(popup_->popup_bounds_in_view());
-    view_proxy_->SetBitmap(bitmap);
+  if (view_proxy_) {
+    view_proxy_->SetBounds(offscreen_bounds);
+    view_proxy_->SetBitmap(offscreen_bitmap);
   }
 }
Repository: facebook/react
Pull request: Guard against legacy context not being supported in DevTools fixture

Legacy context was removed from experimental builds so the default setup would hide important fixtures.

Now it just assumes that any crash within the tree rendering legacy context is due to legacy context not being supported.

I didn't remove the components entirely since this fixture can be used with older versions of React where we would want to check if legacy context still works.
![Screenshot from 2024-03-20 17-09-07](https://github.com/facebook/react/assets/12292047/bd3701f2-2239-46bf-b79e-7f7bd675ab19)




Changed files:
filename: packages/react-devtools-shell/src/app/InspectableElements/Contexts.js
patch: @@ -273,15 +273,46 @@ class ModernClassContextConsumerWithUpdates extends Component<any> {
   }
 }
 
+type LegacyContextState = {
+  supportsLegacyContext: boolean,
+};
+class LegacyContext extends React.Component {
+  state: LegacyContextState = {supportsLegacyContext: true};
+
+  static getDerivedStateFromError(error: any): LegacyContextState {
+    return {supportsLegacyContext: false};
+  }
+
+  componentDidCatch(error: any, info: any) {
+    console.info(
+      'Assuming legacy context is not supported in this React version due to: ',
+      error,
+      info,
+    );
+  }
+
+  render(): React.Node {
+    if (!this.state.supportsLegacyContext) {
+      return <p>This version of React does not support legacy context.</p>;
+    }
+
+    return (
+      <React.Fragment>
+        <LegacyContextProvider>
+          <LegacyContextConsumer />
+        </LegacyContextProvider>
+        <LegacyContextProviderWithUpdates />
+      </React.Fragment>
+    );
+  }
+}
+
 export default function Contexts(): React.Node {
   return (
     <div>
       <h1>Contexts</h1>
       <ul>
-        <LegacyContextProvider>
-          <LegacyContextConsumer />
-        </LegacyContextProvider>
-        <LegacyContextProviderWithUpdates />
+        <LegacyContext />
         <ModernContext.Provider value={contextData}>
           <ModernContext.Consumer>
             {(value: $FlowFixMe) =>
Repository: ggml-org/llama.cpp
Pull request: ci: build Vulkan on Ubuntu with default packages

This PR introduces a GitHub action building the Vulkan backend on Ubuntu using the default distribution packages. The goal is to be closer to the official Debian packaging of ggml and llama.cpp (which will be used by Ubuntu at some point) and also to test against an older, but still in use, version of Vulkan (v1.3).

I am co-maintainer (with @ckastner) of the official Debian packages for ggml and llama.cpp. I have contributed the packaging of the ggml Vulkan backend, and I am therefore following more closely its portability. We regularly face issues  [e.g. 1, 2, 3] on Debian 12/bookworm, which is still widely used, because it is using Vulkan v1.3, as is also the case of Ubuntu 24.04.

As we plan to soon provide backported ggml and llama.cpp packages for bookworm (until August 2026), it would be great if such compatibility issues could be caught directly during llama.cpp development. Otherwise we only notice them when the code gets merged into the ggml repository and when we then update the packages (which can take weeks). 

Moreover, at some point these Debian packages will likely also become the Ubuntu packages, so it would be useful long-term to have a straightforward build based on Ubuntu's Vulkan packages, in addition to the build based on the downloaded latest Vulkan SDK.

Dynamic backend loading and all CPU variants is enabled in this build, as is the case in the official Debian packages, but this could be disabled in order to make the build a bit faster.

[1] https://github.com/ggml-org/llama.cpp/pull/11117
[2] https://github.com/ggml-org/llama.cpp/pull/15939
[3] https://github.com/ggml-org/llama.cpp/pull/16345


Changed files:
filename: .github/workflows/build.yml
patch: @@ -387,6 +387,39 @@ jobs:
           cd build
           ctest -L main --verbose
 
+  ubuntu-24-cmake-vulkan-deb:
+    runs-on: ubuntu-24.04
+
+    steps:
+      - name: Clone
+        id: checkout
+        uses: actions/checkout@v4
+
+      - name: ccache
+        uses: ggml-org/ccache-action@v1.2.16
+        with:
+          key: ubuntu-24-cmake-vulkan-deb
+          evict-old-files: 1d
+
+      - name: Dependencies
+        id: depends
+        run: |
+          sudo apt-get install -y glslc libvulkan-dev libcurl4-openssl-dev
+
+      - name: Configure
+        id: cmake_configure
+        run: |
+          cmake -B build \
+            -DCMAKE_BUILD_TYPE=RelWithDebInfo \
+            -DGGML_BACKEND_DL=ON \
+            -DGGML_CPU_ALL_VARIANTS=ON \
+            -DGGML_VULKAN=ON
+
+      - name: Build
+        id: cmake_build
+        run: |
+          cmake --build build -j $(nproc)
+
   ubuntu-24-cmake-vulkan:
     runs-on: ubuntu-24.04
Repository: ollama/ollama
Pull request: fix num_keep

num_keep calculation is erroneously adding a token which causes the llm to output `\u001c` after truncating

Changed files:
filename: server/routes.go
patch: @@ -117,12 +117,13 @@ func load(ctx context.Context, model *Model, reqOpts map[string]interface{}, ses
 			if err != nil {
 				return err
 			}
+
 			tokensNoSystem, err := llmModel.Encode(ctx, promptNoSystem)
 			if err != nil {
 				return err
 			}
 
-			opts.NumKeep = len(tokensWithSystem) - len(tokensNoSystem) + 1
+			opts.NumKeep = len(tokensWithSystem) - len(tokensNoSystem)
 
 			llmModel.SetOptions(opts)
 		}
Repository: huggingface/transformers
Pull request: Add `chat_template` (`jinja2`) as an extra dependency

# What does this PR do?
This PR adds `chat_template` as an extra dependency. 

`jinja2` is required by [chat_template_utils.py](https://github.com/huggingface/transformers/blob/060b86e21d0460fbd2b6e642d0fbc8f19f679039/src/transformers/utils/chat_template_utils.py#L393C1-L394C1), but it's not declared in setup.py. 

There's been earlier issues on this topic (see #34397 and #35533). 
The reason for not declaring `jinja2` as a dependency is that it's dragged along by `torch`, and [`torch` "always" gets installed anyway](https://github.com/huggingface/transformers/pull/35533#issuecomment-2596031785). 

For inference, it's not a given that `torch` will be installed imho. 
For example the [MAX framework](https://github.com/modular/modular) depends on `transformers`, but not on `torch`. 

For transparency, I work at Modular which develops MAX.

## Before submitting
- [ ] 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),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

@Rocketknight1

Changed files:
filename: setup.py
patch: @@ -337,6 +337,7 @@ def run(self):
 extras["sentencepiece"] = deps_list("sentencepiece", "protobuf")
 extras["tiktoken"] = deps_list("tiktoken", "blobfile")
 extras["mistral-common"] = deps_list("mistral-common[opencv]")
+extras["chat_template"] = deps_list("jinja2")
 extras["testing"] = (
     deps_list(
         "pytest",
@@ -390,6 +391,7 @@ def run(self):
     + extras["video"]
     + extras["num2words"]
     + extras["mistral-common"]
+    + extras["chat_template"]
 )
Repository: denoland/deno
Pull request: fix(npm): do not error on failure to write warned script file

Looked and we already do this for the local npm install.

Kind of annoying to test this one, so not going to bother to.

Closes https://github.com/denoland/deno/issues/30457

Changed files:
filename: libs/npm_installer/global.rs
patch: @@ -222,10 +222,9 @@ impl<TSys: NpmCacheSys> LifecycleScriptsStrategy
     log::warn!("┖─ {}", colors::bold("\"nodeModulesDir\": \"auto\""));
 
     for (package, _) in packages {
-      self.sys.fs_open(
-        self.warned_scripts_file(package),
-        &OpenOptions::new_write(),
-      )?;
+      let _ignore_err = self
+        .sys
+        .fs_open(self.warned_scripts_file(package), &OpenOptions::new_write());
     }
     Ok(())
   }

filename: tests/specs/mod.rs
patch: @@ -129,6 +129,8 @@ struct MultiStepMetaData {
   /// Whether the temporary directory should be symlinked to another path.
   #[serde(default)]
   pub symlinked_temp_dir: bool,
+  #[serde(default)]
+  pub flaky: bool,
   /// The base environment to use for the test.
   #[serde(default)]
   pub base: Option<String>,
@@ -169,6 +171,7 @@ impl SingleTestMetaData {
       base: self.base,
       cwd: None,
       if_cond: self.step.if_cond.clone(),
+      flaky: self.step.flaky,
       temp_dir: self.temp_dir,
       canonicalized_temp_dir: self.canonicalized_temp_dir,
       symlinked_temp_dir: self.symlinked_temp_dir,
@@ -296,18 +299,26 @@ fn run_test_inner(
   cwd: &PathRef,
   diagnostic_logger: Rc<RefCell<Vec<u8>>>,
 ) {
-  let context = test_context_from_metadata(metadata, cwd, diagnostic_logger);
-  for step in metadata
-    .steps
-    .iter()
-    .filter(|s| should_run(s.if_cond.as_deref()))
-  {
-    let run_func = || run_step(step, metadata, cwd, &context);
-    if step.flaky {
-      run_flaky(run_func);
-    } else {
-      run_func();
+  let run_fn = || {
+    let context =
+      test_context_from_metadata(metadata, cwd, diagnostic_logger.clone());
+    for step in metadata
+      .steps
+      .iter()
+      .filter(|s| should_run(s.if_cond.as_deref()))
+    {
+      let run_func = || run_step(step, metadata, cwd, &context);
+      if step.flaky {
+        run_flaky(run_func);
+      } else {
+        run_func();
+      }
     }
+  };
+  if metadata.flaky {
+    run_flaky(run_fn);
+  } else {
+    run_fn();
   }
 }
 

filename: tests/specs/npm/peer_deps_with_copied_folders_and_lockfile/__test__.jsonc
patch: @@ -1,5 +1,6 @@
 {
   "tempDir": true,
+  "flaky": true,
   "steps": [
     {
       "args": "run -A main.ts",

filename: tests/specs/schema.json
patch: @@ -72,6 +72,9 @@
           "canonicalizedTempDir": {
             "type": "boolean"
           },
+          "flaky": {
+            "type": "boolean"
+          },
           "symlinkedTempDir": {
             "type": "boolean"
           },