[arm-storage] Linter Issues to be resolved

Here are the linter issues discovered from the PR https://github.com/Azure/azure-rest-api-specs/pull/1120 which was not related to that PR. Opening this issue for the storage team to act upon.
Executing: autorest -CodeGenerator None -I arm-storage/2016-12-01/swagger/storage.json -JsonValidationMessages true
AutoRest Code Generator
(c) 2017 Microsoft Corporation. https://aka.ms/autorest
[
  {
    "type": "Warning",
    "code": "NonAppJsonTypeWarning",
    "message": "Please make sure that media types other than 'application/json' are supported by your service.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/produces/2",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/produces[2]",
    "id": "S2004",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Error",
    "code": "ListOperationNamingWarning",
    "message": "Since operation 'StorageAccounts_RegenerateKey' response has model definition 'array', it should be of the form \"*_list*\"",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/paths",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/paths",
    "id": "M1003",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Error",
    "code": "OperationsAPIImplementationValidation",
    "message": "Operations API must be implemented for '/providers/Microsoft.Storage/operations'.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/paths",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/paths",
    "id": "M3023",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Error",
    "code": "XmsExamplesProvidedValidation",
    "message": "Please provide x-ms-examples describing minimum/maximum property set for response/request payloads for operations.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/paths",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/paths",
    "id": "M2022",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BodyParametersValidation",
    "message": "A body parameter must be named 'parameters'.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/paths/~1subscriptions~1{subscriptionId}~1providers~1Microsoft.Storage~1checkNameAvailability/post/parameters/1",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/paths/subscriptions/{subscriptionId}/providers/Microsoft.Storage/checkNameAvailability/post/parameters[1]",
    "id": "M2063",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BodyParametersValidation",
    "message": "A body parameter must be named 'parameters'.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/paths/~1subscriptions~1{subscriptionId}~1resourceGroups~1{resourceGroupName}~1providers~1Microsoft.Storage~1storageAccounts~1{accountName}~1regenerateKey/post/parameters/3",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Storage/storageAccounts/{accountName}/regenerateKey/post/parameters[3]",
    "id": "M2063",
    "validationCategory": "SDKViolation",
    "providerNamespace": "Microsoft.Storage",
    "resourceType": "storageAccounts"
  },
  {
    "type": "Warning",
    "code": "DescriptionMissing",
    "message": "'name' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountCheckNameAvailabilityParameters/properties/name",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountCheckNameAvailabilityParameters/properties/name",
    "id": "M4000",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "DescriptionMissing",
    "message": "'type' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountCheckNameAvailabilityParameters/properties/type",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountCheckNameAvailabilityParameters/properties/type",
    "id": "M4000",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BooleanPropertyNotRecommended",
    "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/CheckNameAvailabilityResult/properties/nameAvailable",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/CheckNameAvailabilityResult/properties/nameAvailable",
    "id": "M3018",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BooleanPropertyNotRecommended",
    "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/CustomDomain/properties/useSubDomain",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/CustomDomain/properties/useSubDomain",
    "id": "M3018",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BooleanPropertyNotRecommended",
    "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/EncryptionService/properties/enabled",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/EncryptionService/properties/enabled",
    "id": "M3018",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BooleanPropertyNotRecommended",
    "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountPropertiesCreateParameters/properties/supportsHttpsTrafficOnly",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountPropertiesCreateParameters/properties/supportsHttpsTrafficOnly",
    "id": "M3018",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "DescriptionMissing",
    "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountCreateParameters/properties/properties",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountCreateParameters/properties/properties",
    "id": "M4000",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BooleanPropertyNotRecommended",
    "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountProperties/properties/supportsHttpsTrafficOnly",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountProperties/properties/supportsHttpsTrafficOnly",
    "id": "M3018",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "DescriptionMissing",
    "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccount/properties/properties",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccount/properties/properties",
    "id": "M4000",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "DescriptionMissing",
    "message": "'keyName' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountRegenerateKeyParameters/properties/keyName",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountRegenerateKeyParameters/properties/keyName",
    "id": "M4000",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "BooleanPropertyNotRecommended",
    "message": "Booleans are not descriptive and make them hard to use. Instead use string enums with allowed set of values defined.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountPropertiesUpdateParameters/properties/supportsHttpsTrafficOnly",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountPropertiesUpdateParameters/properties/supportsHttpsTrafficOnly",
    "id": "M3018",
    "validationCategory": "RPCViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Warning",
    "code": "DescriptionMissing",
    "message": "'properties' model/property lacks 'description' property. Consider adding a 'description' element. Accurate description is essential for maintaining reference documentation.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountUpdateParameters/properties/properties",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/definitions/StorageAccountUpdateParameters/properties/properties",
    "id": "M4000",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  },
  {
    "type": "Error",
    "code": "SecurityDefinitionsStructureValidation",
    "message": "A swagger must have security definitions and must adhere to the specific structure.",
    "jsonref": "arm-storage/2016-12-01/swagger/storage.json#/securityDefinitions",
    "json-path": "arm-storage/2016-12-01/swagger/storage.json#/securityDefinitions",
    "id": "M2054",
    "validationCategory": "SDKViolation",
    "providerNamespace": null,
    "resourceType": null
  }
]

Thanks,

Close this item based on @JasonYang-MSFT 's comment "linter validation check in PR already changed from error numbers to error diffs between master and PR branch.


allow custom substrate endpoint

For general substrat-based projects it would be nice if the user could specify the RPC/WS address manually

The polkawallet app was designed to be more user-friendly, so we simplified some functions.
Customed RPC/WS address will not be supported, developers can do that in the polkadot UI polkadot-js/apps.
There are several substrat-based projects will be supported in this App in the future. And we are building this App to be multi-chain supported. You're welcome to contribute 😊.

If my RPC endpoint is not on the supported list, can I open a pull request to add my RPC profile?
Does it take time?


add Dell EMC Unity array support？

add?
https://github.com/equelin/unitymetrics?tab=readme-ov-file

Hi @tqangxl
I think this is outside the scope of this exporter, this is based on Redfish. Also, I do not have access to this hardware, so it would be very difficult for me to implement.


Can't get JsonValue from String returned by JsonValue.toString()

I need to parse JsonValue to String and then parse this String back to JsonValue. JsonReader fails to parse String returned by JsonValue.toString() because of appended name. One way I found so far is to use awkward String manipulations but there clearly should be an easier way.

Example code?

Something like this:
            Json json = new Json();
            json.setUsePrototypes(false);
            JsonValue jsonValue = new JsonReader().parse(json.toJson(new BodyInfo()));
            String jsonString = jsonValue.get("linearVelocity").toString();
            JsonValue anotherValue = new JsonReader().parse(jsonString);

jsonString looks so:
linearVelocity: {
x: 0
y: 0
}

Error occurs on thelast line:
Exception in thread "LWJGL Application" com.badlogic.gdx.utils.SerializationException: Error parsing JSON on line 2 near: x: 0
y: 0
}
	at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:548)
	at com.badlogic.gdx.utils.JsonReader.parse(JsonReader.java:38)

How about JsonValue anotherValue = jsonValue.get("linearVelocity");?

But I need to parse it to String because I use libGDX clipboard for storing information. What I'm actually doing is copying object by parsing it to JSON string, saving this string to clipboard and then pasting this object. I need to know JsonValue name to get a correct class for Json.fromJson(). In my case JsonValue name is the name of the object class.

Try jsonValue.prettyPrint(OutputType.json, 0); instead of toString()

JsonValue.prettyPrint() erases the name but I need to keep it. What is the point of toString() anyway if I can't parse it back to JsonValue?

Object.toString() in Java is generally intended for debug.

In addition:
linearVelocity: {
x: 0
y: 0
}

is not a valid json object, that is why you have this problem.

JsonValue toString does not return JSON. Like most Java toString methods it returns something that tells you about the object. The name and the value or children of the JsonValue object make up most of what the object stores. If you want JSON, you can use prettyPrint as has been mentioned. It is odd that there is no way to get the JsonValue as non-pretty printed JSON, so I will add a toJson method. However, it won't do what you want because it is not possible to emit the name of the object in the JSON. Store it separately or do the string parsing you are doing.


TCNN was not compiled with half-precision support!

Dear @daviddmc,
I use a tool (https://github.com/daviddmc/NeSVoR) that relies on tiny cuda.
However, I get the following error :
RuntimeError: TCNN was not compiled with half-precision support.
How can I compile TCNN with half-precision support ?
CUDA Version: 11.7
NVIDIA TITAN Xp
Thanks!

Hi @LJJson,
It seems that your GPU doesn't support half-precision.
If you are using NeSVoR v0.3.0, you can use single precision (float32) by setting the --single-precision flag in the command.
Run nesvor reconstruct -h for more details.

Dear @daviddmc,
I'm running fine now Thanks for your help.
have a nice day！
liujie


Cannot make :copen work, still shows the normal one

NVIM v0.5.0-dev+1274-gbb3372792
archlinux

Describe the bug
when I do :copen I still see the old one
To Reproduce using nvim -u mini.vim
I cannot test using your mini.vim, it gives some error :O

Steps to reproduce the behavior:

:copen

Expected behavior
I expect to see the floating window with list of quickfixes, but I still see the default one
Screenshots

Additional context
I am sure it's something wrong on my side, I just don't know where..
this is my dotfiles

Look like a git log produced by the fugitive. These items are always lnum = 0 and col = 0. Let me consider how to preview them properly.

So I got  weird case? How can I just open your window? I wanted to see the difference with my eyes

vim /pattern/gj %

Feel free to ask any question here, but allow me to close the issue.


Update external links

Contact Us / Register with the HCA - update to https://www.humancellatlas.org/join-hca/
Guides / Exporting HCA Data to Terra - update to use env
Pipelines / Building Pipelines - add link to Slack.

Recreating in DP.


Update reqs-sys.md

Description

Added info about the requirement for disabling Firewalld

documentation enhancement

Related issues/PRs

adds info about the issue with networking when Firewalld is used as described in issue https://github.com/projectcalico/calico/issues/4382
Todos
Release Note

None required

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR! Just a couple minor comments

OK, I'll change it.

One more minor thing I missed the first time... then good to go. Thanks for the PR!

Fixed.


Optimize label comparisons and remove restrictions on types that can be labels

Objective

Addresses concerns raised by cart in #5366.
Make label comparisons O(1).
More freedom for debug formatting.
Be less prescriptive -- why should everything have to be only a string?

Solution

Require implementers of Label to return a u64 value that distinguishes between labels of the same type.
For formatting, store an &mut Formatter fn pointer.

Smaller stack size than a string slice.
More freedom than a string -- debug formatting can depend on runtime values or be composed generically.
Can be used to uniquely identify an impl, so we don't need to store a TypeId anymore. LabelId is now 16 bytes wide! (down from 24).

The concept of labels not being allowed to hold data now applies only for the derive macro.

Anything that can fit in u64 can get stored on the stack for free.
Anything larger can be boxed -- simple types don't pay for what they don't use.

The base API remains very simple -- complexity is contained to the derive macro.

Examples
Basic labels.
#[derive(SystemLabel)]
enum MyLabel {
    One,
    Two,
}

//
// Derive expands to...

impl SystemLabel for MyLabel {
    fn data(&self) -> u64 {
        match self {
            Self::One => 0,
            Self::Two => 1,
        }
    }
    fn fmt(data: u64, f: &mut fmt::Formatter) -> fmt::Result {
        match data {
            0 => write!(f, "MyLabel::One"),
            1 => write!(f, "MyLabel::Two"),
            _ => unreachable!(),
        }
    }
}

Complex labels require boxing and interning.
#[derive(Clone, PartialEq, Eq, Hash, SystemLabel)]
#[system_label(intern)]
pub struct MyLabel<T>(Vec<T>);

//
// Derive expands to...

use bevy_ecs::label::{Labels, LabelGuard};

// Global label interner for `MyLabel<T>`, for all `T`.
static MAP: Labels = Labels::new();

impl<T: Debug + Clone + Hash + Eq + Send + Sync + 'static> SystemLabel for MyLabel<T> {
    fn data(&self) -> u64 {
        MAP.intern(self)
    }
    fn fmt(idx: u64, f: &mut Formatter) -> fmt::Result {
        write!(f, "{:?}", MAP.get::<Self>(idx)?)
    }
}

// Implementing this trait allows one to call `SystemLabelId::downcast` with this type.
impl<T: ...> LabelDowncast<SystemLabelId> for MyLabel<T> {
    type Output = LabelGuard<'static, Self>;
    fn downcast_from(idx: u64) -> Option<LabelGuard<Self>> {
        // Return a reference to an interned value.
        // The guard type will ultimately get hidden behind an opaque type.
        MAP.get::<Self>(idx)
    }
}

Notes

Label traits are no longer object safe, but this is probably a good thing since it makes it easier to catch obsolete instances of Box<dyn Label>. LabelId should always be used instead.
This PR adds parking_lot as a direct dependency for bevy_ecs. It was already in the dependency tree.

Benchmarks

# of Systems
No deps
% Change
W/ deps
% Change

100
209.07 us
-2.3448%
1.7338 ms
-12.195%

500
797.98 us
-19.103%
55.710 ms
-12.324%

1000
1.4774 ms
+2.7637%
285.49 ms
-7.0926%

Changelog

Removed as_str() and type_id() from label traits.

Added data() and fmt() to label traits.
+Added support for complex label types by heap-allocating them.
Fixed formatting of generics in Label derive macros.

Migration Guide
The Label family of traits (SystemLabel, StageLabel, etc) is no longer object safe. Any use of Box<dyn Label> should be replaced with LabelId - this type serves the same purpose but is Copy and does not usually require allocations. Any use of &dyn Label should be replaced with impl Label if possible, or LabelId if you cannot use generics.
For manual implementers of Label traits, the methods type_id() and as_str() have been removed. Instead, the functions data() and fmt() have been added.
Label::data() returns an integer value that is used to distinguish between labels of the same type. Label::fmt() prints the debug representation of the label to an &mut Formatter, and is passed the result of calling .data().

This PR is now at a point where I'm happy with it. I'll get CI passing once we yeet stringly-typed labels.

On second thought, I realized that I can implement string-labels in this design. This PR is no longer blocked, not sure what that last CI failure is about though.

I've iterated a lot on this PR. In that time, the design and precise motivations have changed considerably and the history has gotten quite messy. I'm going to close this out and open a new PR.


compile with xcode 11 failed

Hi,thanks for your great project.
In my project, I used IGHTMLQuery by Pods(pod 'IGHTMLQuery', '~> 0.9.1'), but compile failed with xcode 11.
I find out IGHTMLQuery project's depends:
 - IGHTMLQuery/Core (0.9.1):
    - CSSSelectorConverter (>= 1.2.0)
        - NUIParse

in NUIParse-NUIPShiftReduceGotoTable.m i got some err:

'name' is unavailable: not available on iOS

We're encountering the same issue. There's a PR open for NUIParse to fix it I believe. We fixed it by adding a #import NUIParse.h, but it would be good to have the Pod fixed properly to avoid forking.


cypress: 10.10.0 -> 12.3.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 10.11.0 with grep in /nix/store/pc46f9jmd6qp8901ks88kvzdgd7b4gsn-cypress-10.11.0
found 10.11.0 in filename of file in /nix/store/pc46f9jmd6qp8901ks88kvzdgd7b4gsn-cypress-10.11.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pc46f9jmd6qp8901ks88kvzdgd7b4gsn-cypress-10.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/31f1ab882af9a33265e793d5da08be843df2bbf9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pc46f9jmd6qp8901ks88kvzdgd7b4gsn-cypress-10.11.0
ls -la /nix/store/pc46f9jmd6qp8901ks88kvzdgd7b4gsn-cypress-10.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 11.0.1 with grep in /nix/store/ih9h9cad8i7z1mzkvlnadb9cny1clzyn-cypress-11.0.1
found 11.0.1 in filename of file in /nix/store/ih9h9cad8i7z1mzkvlnadb9cny1clzyn-cypress-11.0.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ih9h9cad8i7z1mzkvlnadb9cny1clzyn-cypress-11.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/602ee475f8cdc6a50386d372ccebfc58c85cd1a6.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ih9h9cad8i7z1mzkvlnadb9cny1clzyn-cypress-11.0.1
ls -la /nix/store/ih9h9cad8i7z1mzkvlnadb9cny1clzyn-cypress-11.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 11.1.0 with grep in /nix/store/zk4kcl6nbxchh9j3pmlf9x7fm3415zj4-cypress-11.1.0
found 11.1.0 in filename of file in /nix/store/zk4kcl6nbxchh9j3pmlf9x7fm3415zj4-cypress-11.1.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zk4kcl6nbxchh9j3pmlf9x7fm3415zj4-cypress-11.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/50f6bcb9669acf6aaefb008704ba90ef7bd2d866.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zk4kcl6nbxchh9j3pmlf9x7fm3415zj4-cypress-11.1.0
ls -la /nix/store/zk4kcl6nbxchh9j3pmlf9x7fm3415zj4-cypress-11.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 11.2.0 with grep in /nix/store/1a64igf473s9mya5ikq45fcryr96bg07-cypress-11.2.0
found 11.2.0 in filename of file in /nix/store/1a64igf473s9mya5ikq45fcryr96bg07-cypress-11.2.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1a64igf473s9mya5ikq45fcryr96bg07-cypress-11.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/594a6d0af5f1098dfaf665aae102eb3f5bb83c25.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1a64igf473s9mya5ikq45fcryr96bg07-cypress-11.2.0
ls -la /nix/store/1a64igf473s9mya5ikq45fcryr96bg07-cypress-11.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.0.2 with grep in /nix/store/jg0x40mqgs31bv6pbqslv7p0g3h67n19-cypress-12.0.2
found 12.0.2 in filename of file in /nix/store/jg0x40mqgs31bv6pbqslv7p0g3h67n19-cypress-12.0.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jg0x40mqgs31bv6pbqslv7p0g3h67n19-cypress-12.0.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/cf593da12dc04f57b4d666bb5837047741243d9c.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jg0x40mqgs31bv6pbqslv7p0g3h67n19-cypress-12.0.2
ls -la /nix/store/jg0x40mqgs31bv6pbqslv7p0g3h67n19-cypress-12.0.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: "Fast, easy and reliable testing for anything that runs in a browser"
meta.homepage for cypress is: "https://www.cypress.io"
meta.changelog for cypress is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.2.0 with grep in /nix/store/s9pvq60c4gdhn0qdqg044qrjc7sdcvll-cypress-12.2.0
found 12.2.0 in filename of file in /nix/store/s9pvq60c4gdhn0qdqg044qrjc7sdcvll-cypress-12.2.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s9pvq60c4gdhn0qdqg044qrjc7sdcvll-cypress-12.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/5f4a1e8dc0728b04fa44753d1f07a36ea1ea713b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s9pvq60c4gdhn0qdqg044qrjc7sdcvll-cypress-12.2.0
ls -la /nix/store/s9pvq60c4gdhn0qdqg044qrjc7sdcvll-cypress-12.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.3.0 with grep in /nix/store/rm1y4ry53mbzqkqfn09nh5sjgb27miii-cypress-12.3.0
found 12.3.0 in filename of file in /nix/store/rm1y4ry53mbzqkqfn09nh5sjgb27miii-cypress-12.3.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rm1y4ry53mbzqkqfn09nh5sjgb27miii-cypress-12.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/459dd329107093420a61769abb036c4ef5a7b5bb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rm1y4ry53mbzqkqfn09nh5sjgb27miii-cypress-12.3.0
ls -la /nix/store/rm1y4ry53mbzqkqfn09nh5sjgb27miii-cypress-12.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1719

Build is failing

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.4.1 with grep in /nix/store/ivk0d7bk906fk5rg5vakihahq06chfbi-cypress-12.4.1
found 12.4.1 in filename of file in /nix/store/ivk0d7bk906fk5rg5vakihahq06chfbi-cypress-12.4.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ivk0d7bk906fk5rg5vakihahq06chfbi-cypress-12.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/6513b863526e9f1999706852f6be22e176edf6ff.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ivk0d7bk906fk5rg5vakihahq06chfbi-cypress-12.4.1
ls -la /nix/store/ivk0d7bk906fk5rg5vakihahq06chfbi-cypress-12.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.5.0 with grep in /nix/store/4fvyl5zvsdbjk5jh26wkn7nvk69fprlc-cypress-12.5.0
found 12.5.0 in filename of file in /nix/store/4fvyl5zvsdbjk5jh26wkn7nvk69fprlc-cypress-12.5.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4fvyl5zvsdbjk5jh26wkn7nvk69fprlc-cypress-12.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/825ad6f4e10532c8e43fc7089ca14713a38c9650.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4fvyl5zvsdbjk5jh26wkn7nvk69fprlc-cypress-12.5.0
ls -la /nix/store/4fvyl5zvsdbjk5jh26wkn7nvk69fprlc-cypress-12.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.5.1 with grep in /nix/store/g2qn6jwcmajqfprwzd0a516jg3g4phgz-cypress-12.5.1
found 12.5.1 in filename of file in /nix/store/g2qn6jwcmajqfprwzd0a516jg3g4phgz-cypress-12.5.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g2qn6jwcmajqfprwzd0a516jg3g4phgz-cypress-12.5.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/aa7776a4a388b1e50072cd1c47f0ec9555913efb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g2qn6jwcmajqfprwzd0a516jg3g4phgz-cypress-12.5.1
ls -la /nix/store/g2qn6jwcmajqfprwzd0a516jg3g4phgz-cypress-12.5.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.6.0 with grep in /nix/store/h0msrm76wz5gf00hgprmrd3f7lwn8jbd-cypress-12.6.0
found 12.6.0 in filename of file in /nix/store/h0msrm76wz5gf00hgprmrd3f7lwn8jbd-cypress-12.6.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h0msrm76wz5gf00hgprmrd3f7lwn8jbd-cypress-12.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/99e9dd4ec39e5e15f16f48396aa59fc04e2f1f2b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h0msrm76wz5gf00hgprmrd3f7lwn8jbd-cypress-12.6.0
ls -la /nix/store/h0msrm76wz5gf00hgprmrd3f7lwn8jbd-cypress-12.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.7.0 with grep in /nix/store/nawjrl0k4r9sg3ycg4iyq5a8psmxwy7s-cypress-12.7.0
found 12.7.0 in filename of file in /nix/store/nawjrl0k4r9sg3ycg4iyq5a8psmxwy7s-cypress-12.7.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nawjrl0k4r9sg3ycg4iyq5a8psmxwy7s-cypress-12.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/283b835180626f33e6d6d6540dca7962ed5b4aee.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nawjrl0k4r9sg3ycg4iyq5a8psmxwy7s-cypress-12.7.0
ls -la /nix/store/nawjrl0k4r9sg3ycg4iyq5a8psmxwy7s-cypress-12.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Seems to be working fine for me.
The failing test is apparently a timeout. Maybe we can retry it, or maybe there's something preventing it from running in the nix build environment and needs patching out?
cc @thorstenweber83 @mmahut @Craftzman7 ?

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 12.8.1 with grep in /nix/store/9az7kr206x7k7k9dnm1jm6zpw89glzxq-cypress-12.8.1
found 12.8.1 in filename of file in /nix/store/9az7kr206x7k7k9dnm1jm6zpw89glzxq-cypress-12.8.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9az7kr206x7k7k9dnm1jm6zpw89glzxq-cypress-12.8.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/a177521f1418705feb9f35f67783b15797b9dc36.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9az7kr206x7k7k9dnm1jm6zpw89glzxq-cypress-12.8.1
ls -la /nix/store/9az7kr206x7k7k9dnm1jm6zpw89glzxq-cypress-12.8.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 12.9.0 with grep in /nix/store/8h2vbx8d0rqjqbhv0nyk40p3wp3f1d0p-cypress-12.9.0
found 12.9.0 in filename of file in /nix/store/8h2vbx8d0rqjqbhv0nyk40p3wp3f1d0p-cypress-12.9.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8h2vbx8d0rqjqbhv0nyk40p3wp3f1d0p-cypress-12.9.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/243899744ac4521104e85a88d1c38c6fba951b21.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8h2vbx8d0rqjqbhv0nyk40p3wp3f1d0p-cypress-12.9.0
ls -la /nix/store/8h2vbx8d0rqjqbhv0nyk40p3wp3f1d0p-cypress-12.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 12.10.0 with grep in /nix/store/wrn7l8xay7yk3gwp743jnvl0hj6ba6fd-cypress-12.10.0
found 12.10.0 in filename of file in /nix/store/wrn7l8xay7yk3gwp743jnvl0hj6ba6fd-cypress-12.10.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wrn7l8xay7yk3gwp743jnvl0hj6ba6fd-cypress-12.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/6d4d4b8e60c060f7c6829d3a2a0f4ecc9b821df2.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wrn7l8xay7yk3gwp743jnvl0hj6ba6fd-cypress-12.10.0
ls -la /nix/store/wrn7l8xay7yk3gwp743jnvl0hj6ba6fd-cypress-12.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cypress is: Fast, easy and reliable testing for anything that runs in a browser
meta.homepage for cypress is: https://www.cypress.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 12.16.0 with grep in /nix/store/k780j8hd9j51r728rgn1gy361phq87np-cypress-12.16.0
found 12.16.0 in filename of file in /nix/store/k780j8hd9j51r728rgn1gy361phq87np-cypress-12.16.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cypress
polaris
polaris-web

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k780j8hd9j51r728rgn1gy361phq87np-cypress-12.16.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cypress https://github.com/r-ryantm/nixpkgs/archive/f8eabd05010e9e3539ea6007d3ab5ead4e86b90d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k780j8hd9j51r728rgn1gy361phq87np-cypress-12.16.0
ls -la /nix/store/k780j8hd9j51r728rgn1gy361phq87np-cypress-12.16.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cypress
polaris
polaris-web

Maintainer pings
cc @thorstenweber83 @mmahut @Craftzman7 for testing.


Implement get_tx_out_set_info RPC method for Floresta-cli

This commit introduces the get_tx_out_set_info RPC method to the FlorestaRPC trait and its implementation in the JsonRPCClient trait within the rpc.rs file. The get_tx_out_set_info method retrieves statistics about the unspent transaction output (UTXO) set, providing detailed information such as the total amount of coins, the number of transactions, and the disk size.
Changes include:

Addition of the get_tx_out_set_info method to the FlorestaRPC trait.
Implementation of the get_tx_out_set_info method in the JsonRPCClient trait.
Ensuring the method aligns with the existing structure and style of the rpc.rs file.

Hi @Gudnessuche, thanks for contributing. The work done here looks awesome for documentation, but... Im seeing a misconception about "Implementing" get_tx_out_set_info rpc method, isnt implemented at all.
You just declared the function signature inside the FlorestaRPC trait, the actual code for obtaining this information is server-side in florestad/src/json_rpc/server.rs and get_tx_out_set_info isnt implemented server-side... And even if i compile floresta-cli with your changes the get_tx_out_set_info doesnt appear because clap isnt aware of it, so...
Allow me to make the assumption that this PR still incomplete for a review, so it should be marked as a draft PR.
Please, change the description and the title to meet the actual state of your PR.let me recommend some useful source of PR guidelines.
https://www.youtube.com/watch?v=8lGpZkjnkt4&pp=ygUSSG93IHRvIGNyZWF0ZSBhIFBS
https://github.blog/developer-skills/github/how-to-write-the-perfect-pull-request/

I appreciate the feedback @jaoleal
The PR indeed isn't finished, as I haphazardly just did this.
Would go through the resource provided.
But if there's a way of helping speed of the process by assisting, I wouldn't mind as well

But if there's a way of helping speed of the process by assisting, I wouldn't mind as well

Of course! If possible, ill try to help you with my feedbacks as a reviewer so, you can tag me any time and ill appear soon.

The PR indeed isn't finished, as I haphazardly just did this.

Ok, the normal behavior for contributing directly with PRs is, when making a Pull Request, have a description of whats the work in progress or if the work is ready for reviewing, can you edit the descripition of the PR so we can easily know the actual state of your progress ?
Also, please dont include failing commits and squash them as needed...

@Davidson-Souza can you check these PRs

@Gudnessuche I've looked at the others you made, left a comment in one and merged the others.
For this one, I think we first need to keep track of some data that we currently don't. The easier one would be total amount in circulation.  Just adding a new field in chainstate and updating it for satoshis created and destroyed in transactions would suffice.
The harder one would be utxo set hash and size, because we don't have the whole utxo set to copute those.


Linux != Only Ubuntu & Debian

Why
I am tired of seeing every major project on Github simply catered around people on Debian & Ubuntu. Not all of us have systemd or use simple distros like this.

Description
I would be nice to see a setup/install guide that is more universal, rather than saying headscale "depends" upon Ubuntu & Debian. No offense but not everyone on Linux is using those 2 distros only lol....Like seriously, your "manual" install is considered "legacy" and "outdated" ?

Since Headscale is also released as container images, you should be able to run it on any Linux distro supporting an OCI-compatible container runtime (Docker, Podman etc.). Alternatively, you could even compile the Go binary yourself.
If there is something wrong or missing in the docs, people are always welcome to open PRs!

@acidvegas if you want to improve the docs, open a PR.
In any case, I don't think this is in any way an appropriate manner to address the volunteer team of a community project.


chore: bump cypress from 3.1.5 to 3.4.1

CATEGORY
Choose one

[ ] Bug Fix
[ ] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[x] Build / Development Environment
[ ] Documentation

Codecov Report

Merging #8158 into master will increase coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #8158      +/-   ##
=========================================
+ Coverage   66.06%   66.2%   +0.13%
=========================================
  Files         479     479
  Lines       22930   22930
  Branches     2524    2524
=========================================
+ Hits        15148   15180      +32
+ Misses       7648    7616      -32
  Partials      134     134

Impacted Files
Coverage Δ

superset/views/core.py
71.46% <0%> (+0.21%)
:arrow_up:

superset/models/core.py
81.76% <0%> (+0.64%)
:arrow_up:

superset/db_engine_specs/mysql.py
92.15% <0%> (+49.01%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee24539...7bba30e. Read the comment docs.

The cypress package is pretty heavy and it makes Docker images significantly bigger and longer to build.


[Feature]:  Add emoji picker to Rich Text Editor

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Community Request
https://community.appsmith.com/t/emoji-picker-widget/1818/2

Why should this be worked on?
An emoji picker is very common across the board.
 Front conversations

We need to add the Emoticon plugin to the editor
Easy fix

i am interested to have this issue, can you assign me ?

HI @ampatzidhs I have raised a PR for this and it should move into production in the next few days.


$ReadOnlyArray is tainted with assignment of wrong type

This issue was originally found in https://github.com/facebook/flow/pull/7620 PR
/cc @mvitousek
Flow version: 0.102.0
declare function freeze<T>(a: Array<T>): $ReadOnlyArray<T>

const m = freeze([1])
m[0] = 'string' // should only error here

;(m[0]: number) // shouldn't error here, since it is read-only

Expected behavior
Array still has type $ReadOnlyArray<number>
Actual behavior
Array has type $ReadOnlyArray<string | number>

Link to Try-Flow or Github repo: https://flow.org/try/#0CYUwxgNghgTiAEAzArgOzAFwJYHtVLhAC8QAeAFQD4AKKALngEEYYoBPCygSgYBIAlEFGAB5VBDbNWHKgChZYPAGcM8ALbwAvARDEQ1ANoBGALpdZagwAYTW+AHIVMLKgDm9+QG5qlmw1TIagBGIDDm8rJAA

In the example you can replace freeze<T>(a: Array<T>): $ReadOnlyArray<T> with freeze<T>(a: $ReadOnlyArray<T>): $ReadOnlyArray<T> and it won't change anything.
Also it is actually a more general issue, where = on read-only properties changes the type.
const a0 = (['s']: $ReadOnlyArray<*>)
a0[0] = 2 // no errors below if you comment this line
;(a0[0]: string) // should not error
const a01 = (['s']: $ReadOnlyArray<*>)
a01[0] -= 2 // error
;(a01[0]: string) // ok

const a1 = ({ a: 's'}: { +a: * })
a0.a = 2 // error
;(a0.a: string) // should not error
const a11 = Object.freeze({ a: 's' })
a11.a = 2 // error
;(a11.a: string) // should not error

class A2<+T> {
  +v: T
}
class A21<T> extends A2<T> {
  constructor(v: T): void {}
  v: T
}
const a21 = new A21('s')
const a2 = (a21: A2<*>)
a2.v = 33
;(a2.v: string) // should not error

try flow
I guess the behaviour with found errors is not strictly defined and is not in Flow Team priority.

@Bannerets In your second example set you've got a0 where i think you mean a1. :smiley:

This behavior is now expected in the new type inference engine


SASS-1089 - Changed account field in InterestCYAModel to Seq[Interest…

Description
The InterestCYAModel contains a field accounts which has the type Option[Seq[InterestAccountModel]]
The goal is to change this to a Seq[InterestAccountModel] which will simplify the code where we try to access/modify the list of accounts as we will not need to deal with the outer option.
SASS-1089
Checklist PR Reviewer
Before Reviewing

[x]  Have you pulled the branch down?
[x]  Have you assigned yourself to the PR?
[x]  Have you moved the task to “in review” on JIRA?
[ ]  Have you checked to ensure all dependencies are up to date?
[ ]  Have you checked to ensure its been rebased against the current version of master?

Whilst Reviewing

[ ]  Have you run the tests?
[ ]  Have you run the journey tests?
[ ]  Have you looked at the JIRA story to make sure all Acceptance Criteria has been met?

After Reviewing

[ ]  Have you checked for merge conflicts or any changes in the current master that may affect the current pull request? i.e. does it need another rebase?
[ ]  Have you checked to make sure there are no builds in the pipeline before you merge?
[ ]  Have you moved the task to “in pipeline” on Jira?

[x]  Have you rebased against the current version of master?
[x]  Have you checked code coverage isn’t lower than previously?

After PRs been raised

[X]  Have you checked the PR Builder passes?

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

test this please

could we get this rebased please?

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

test this please

could we get this rebased please?

Done 👍

Thank you for submitting a pull request on this HMRC repository. A member of the HMRC team will review your changes and action accordingly.
HMRC reviewer: please reference this runbook for guidance on how to proceed.

test this please


Use Recaptcha in Login Flow after X Failures to Block Brute Force Attacks

We can add unit tests for the helper functions here if that seems necessary, but we can't really functionally test the recaptcha itself by design. It would also break subsequent functional tests if abused. Please review this carefully and let me know what you think. I've tried to document what is happening in the code fairly thoroughly, but I'm happy to add more as necessary. Thanks!

This change is

Okay, I'll look at this closely, please give me some time.
qq: if there is some doubt about a functional test for this, then how would we test this manually?
Previously, xwsxethan (Ethan) wrote…
> #### Use Recaptcha in Login Flow after X Failures to Block Brute Force Attacks
>
> We can add unit tests for the helper functions here if that seems necessary, but we can't really functionally test the recaptcha itself by design. It would also break subsequent functional tests if abused. Please review this carefully and let me know what you think. I've tried to document what is happening in the code fairly thoroughly, but I'm happy to add more as necessary. Thanks!
>
>
>
>
>
>

Review status: 0 of 12 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

The problem with the functional test is passing the recaptcha, since it is by design requiring a human to enter data. If we did trigger recaptcha by attempting successive bad logins, then we have no means (from an automated functional test perspective) to pass recaptcha and actually log in so it's a bit of a chicken and egg scenario. We could wait for the recaptcha to time out and turn off (from exponential backoff), but I'm just not sure how good of an idea that is.
Manually however we can enter the necessary fields to pass a recaptcha challenge. So we can manually fail login several times to trigger recaptcha, then manually perform the recaptcha, and finally login as intended.
Previously, blueandgold (Henry Chang) wrote…
> Okay, I'll look at this closely, please give me some time.
> qq: if there is some doubt about a functional test for this, then how would we test this manually?

Reviewed 12 of 12 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

I'm gonna delete this and make a new PR once this has stabilized since I'm not having to update the standing instance.


Add publish in spi build.gradle

Description
Publish the spi to maven
Test locally by running ./gradlew publishShadowPublicationToStagingRepository

Reference
https://github.com/opensearch-project/alerting/pull/1562
https://github.com/opensearch-project/alerting/pull/1604
https://github.com/opensearch-project/opensearch-plugins/blob/main/BUILDING.md#include-checksums-in-maven-publications
Check List

[x] New functionality includes testing.
[x] New functionality has been documented.
[x] API changes companion pull request created.
[x] Commits are signed per the DCO using --signoff.
[x] Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks @bowenlan-amzn can you please also confirm if there is no change in publishing of the zip file ?
<groupId>org.opensearch.plugin</groupId>
<artifactId>opensearch-index-management</artifactId>
<version><IP_ADDRESS>-SNAPSHOT</version>
<packaging>zip</packaging>

https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/opensearch-index-management/

Thanks @bowenlan-amzn can you please also confirm if there is no change in publishing of the zip file ?
<groupId>org.opensearch.plugin</groupId>
<artifactId>opensearch-index-management</artifactId>
<version><IP_ADDRESS>-SNAPSHOT</version>
<packaging>zip</packaging>

aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/plugin/opensearch-index-management

I run publishPluginZipPublicationToZipStagingRepository, and here's the result, it looks good to me

@prudhvigodithi and a quick question, do we need to backport this to any branch other than 2.x?

Thanks @bowenlan-amzn, ya as long as there no change in publishing of the zip file we should be good, also just 2.x as the gradle custom plugin used opensearch.pluginzip is only available starting 2.x. https://opensearch.org/blog/opensearch-plugin-zips-now-in-maven-repo/
Thank you


win-3 is dead.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
win-3 is dead.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Machine was hung and required to reboot.


Blockquotes markdown not work in documentation description

using:
> This is Blockquotes

not proper rendered , it just render plain text, it should be:

This is Blockquotes

@TangMonk The markdown conversion is done by SwaggerUI library https://github.com/swagger-api/swagger-ui and it uses marked.js https://github.com/chjj/marked. I think this is more of issue to be raised with these modules.
As its not something I can change, I am going to close this issue. Please feel free open it again if you feel the problem is within hapi-swagger

thanks it is a issue with marked https://github.com/chjj/marked/issues/790


Hot reloading no longer works after adding Babel plugin

Description
joelso — Yesterday at 01:54 Hey everyone,  I'm currently trying to understand the Babel plugin as detailed here: https://gluestack.io/ui/docs/production-optimizations/babel-plugin.
Do I have it right that I should add the plugin to my React Native app that is using Gluestack UI to get all performance benefits? I assume yes, but there is this wording in the docs that confuses me a bit (plus I noticed that in the boilerplate project no such babel config is there):
Note: We already provide you with the plugin config for @gluestack-ui/themed. So you have to do minimal configuration to get it working.
Also, after adding it, I've noticed that hot reloading no longer works. Has anyone else encountered this issue, or does anyone have any insights on how to address it? Or is it so that I should not need it/use it while in dev mode only for prod builds?
CodeSandbox/Snack link
No response
Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

gluestack-ui Version
3.3.1
Platform

[ ] Expo
[ ] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

Hey @Gluant101, Thanks for reporting the issue. We'll look into it.

@ankit-tailor any updates on this issues?
P.S. Hot Reload is broken only for gluestack components

Also it looks like that the issue is related only to gluestack props manipulation. Hot reloading for regular props and adding / removing components works fine.
But when I try to change color or set gs-props like px nothing is updated. So something is wrong in visitor.JSXOpeningElement

@Viraj-10 @ankit-tailor
any updates on this issue? It's really hard to develop without hot reload since you spent too much time reloading scenes manually


Update docker-compose-collect.yml

Changed goflow startup syntax to latest.

Hello,
Thanks for the fix. Sorry it took so long to integrate those changes (cf #2). I made an update today that should fix it.


Add foc/search

If you had changed the namespace to FOC/Search it would have also been a different plugin name now ;)

Who knows, over time FOC's search might become de-facto :)

From the looks it sure sounds like it could happen. More objects, less arrays :)


Mouse control is lost from OrbitView

Hello, I realize the OrthographicView and OrbitView are experimental, but maybe this provides a use case to be aware of.

Press the toggle 2D / 3D button.
Actual Result
When deck.DeckGL is initialized with an OrthographicView, the canvas will not respond to mouse events after the view is replaced with an OrbitView.
Expected Result
Mouse events to always be captured in OrbitView.
Reproduce Steps
Changing to  var is3D = false; to initialize with 2D and see the error when in 3D.

@Pessimistress

Works in version 6+


Set python 3.11.6 and corresponding py-numpy for gsi-addon-dev template

Summary
This PR adds<EMAIL_ADDRESS>to the gsi addon environment template. Note the :: is needed to override the require: settings from common/packages.yaml. I chose 3.11.6 because it's listed as preferred in the recipe, and 1.23.4 build with intel whereas various prior and later versions don't work with intel and/or<EMAIL_ADDRESS>I suggest putting this is 1.6.0 release so that the gsi addon environment should work right out of the box.
Testing
Tested building as unchained environment on Hera.
Applications affected
GSi
Systems affected
all systems where gsi-addon-env will be installed
Dependencies
none
Issue(s) addressed
Addresses https://github.com/JCSDA/spack-stack/issues/908
Checklist

[x] This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
[x] These changes have been tested on the affected systems and applications.
[x] All dependency PRs/issues have been resolved and this PR can be merged.

@climbfuji @DavidHuber-NOAA I'm on break for a while starting tomorrow (Dec 20), so if you can verify this and merge if it looks good, that would be much appreciated. Thanks!

@climbfuji @DavidHuber-NOAA I'm on break for a while starting tomorrow (Dec 20), so if you can verify this and merge if it looks good, that would be much appreciated. Thanks!

So the "problem" is that this doesn't build on macOS (at least the slightly older versions). I've spent several days with the spack developers on this and we are nearing a solution. Not really a problem if we don't care for the moment, but needed in the mid-term.
I am currently building a 1.6.0 release candidate on Hercules, how about I use this template for creating the gsi-addon-env for testing?

@climbfuji That works for me.  Thank you!  I am also building a highly pared down version of it on Hera for a quick round of METplus testing.

Yesterday after much debugging I was able to build gsi-addon-env with Python 3.11.2 on my new macOS (Sonoma, apple-clang@15, Intel architecture) except the last mile - met and metplus didn't build (but all the Python dependencies did). On my other mac (Monterey, apple-clang@13, Arm architecture), py-numpy built but was unusable, causing many build failures for downstream Python packages. The spack and numpy developers are investigating the underlying issue (they verified there is one).
Long story short, maybe macOS is never going to be a place for gsi-addon-env because I don't expect that anyone will try to fix the old met/metplus versions on macOS. But having the Python environment issues sorted out on macOS is necessary for updating Python in general in the near future.

While Python 3.11.6 installed successfully on Hera, it failed to install met/9.1.3 failing with an obscure error:
make[4]: Nothing to be done for `install-exec-am'.
 /usr/bin/mkdir -p '/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/envs/gsi-addon/install/intel/2021.5.0/met-9.1.3-w427egk/share/met/map/admin_by_country'
==> Error: Exception occurred in writer daemon!
Traceback (most recent call last):
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 983, in _writer_daemon
    sys.stdout.write(output_line)
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 255, in write
    self.stream.write(data)
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 255, in write
    self.stream.write(data)
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 255, in write
    self.stream.write(data)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 837-838: ordinal not in range(128)
==> Error: ProcessError: Command exited with status -13:
    'make' '-j6' 'install'

The full log file is available here: /scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/cache/build_stage/spack-stage-met-9.1.3-w427egk7fioeuzsfezgpbpcnaxbmbhjg/spack-build-out.txt, though oddly the error is not written to this log, it stops just short of it.

While Python 3.11.6 installed successfully on Hera, it failed to install met/9.1.3 failing with an obscure error:
make[4]: Nothing to be done for `install-exec-am'.
 /usr/bin/mkdir -p '/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/envs/gsi-addon/install/intel/2021.5.0/met-9.1.3-w427egk/share/met/map/admin_by_country'
==> Error: Exception occurred in writer daemon!
Traceback (most recent call last):
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 983, in _writer_daemon
    sys.stdout.write(output_line)
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 255, in write
    self.stream.write(data)
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 255, in write
    self.stream.write(data)
  File "/scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/spack/lib/spack/llnl/util/tty/log.py", line 255, in write
    self.stream.write(data)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 837-838: ordinal not in range(128)
==> Error: ProcessError: Command exited with status -13:
    'make' '-j6' 'install'

The full log file for met is available here: /scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/cache/build_stage/spack-stage-met-9.1.3-w427egk7fioeuzsfezgpbpcnaxbmbhjg/spack-build-out.txt, though oddly the error is not written to this log, it stops just short of it. The log file for the gsi-addon install is available here: /scratch1/NCEPDEV/global/David.Huber/SPACK/spack-stack/envs/gsi-addon/log.install, which includes the error.

Did you use the release/1.6.0 version of spack-stack and spack for that? I was able to install gsi-addon-env successfully using this branch based on the release branches. (on Hercules with GNU and Intel).
Maybe spack clean -a and kick off the remaining install? Also wortth checking what is in your ~/.spack folder

Thanks for the suggestions @climbfuji.  No, I did not try out release/1.6.0.  I will work with that and clean out my ~/.spack.

Also, just to make sure, before you run source setup.sh in the spack-stack directory:
module purge
module use /scratch1/NCEPDEV/jcsda/jedipara/spack-stack/modulefiles
module load miniconda/3.9.12
module load ecflow/5.5.3
module load mysql/8.0.31

@DavidHuber-NOAA Did that work for you? Are you ok with these changes? I am happy to approve and merge if it works for you. Thanks!

@climbfuji Sorry for not getting back.  Yes, it did work and @malloryprow verified that met worked.  Yes, please go ahead and merge.

@climbfuji Sorry for not getting back. Yes, it did work and @malloryprow verified that met worked. Yes, please go ahead and merge.

Thanks very much!


Documentation for Config Creation is 404

Howdy yet again again hohoho :)
In the official documentation there is a link to more in depth detail about configuration files, found here:
https://openbullet.github.io/configs.html

However this link is a 404.
Additionally, I am unable to import an old config.ini files for testing purposes built for old BlackBullet to test my own personal website or websites I am authorized to test by security audit clients. Will there be any planned support for old ini or bbc configuration file import into the new OpenBullet or should I simply recreate configs for now?
Much thanks again, all suggestions and ideas are truly fantastic, I'm hoping to get a firmer grasp on this project so hopefully my questions are not too bothersome.
Enjoy and this time Kampai!
:>

Howdy yet again again hohoho :)
In the official documentation there is a link to more in depth detail about configuration files, found here:
https://openbullet.github.io/configs.html

However this link is a 404.
Additionally, I am unable to import an old config.ini files for testing purposes built for old BlackBullet to test my own personal website or websites I am authorized to test by security audit clients. Will there be any planned support for old ini or bbc configuration file import into the new OpenBullet or should I simply recreate configs for now?
Much thanks again, all suggestions and ideas are truly fantastic, I'm hoping to get a firmer grasp on this project so hopefully my questions are not too bothersome.
Enjoy and this time Kampai!
:>

You can convert .bbc and .ini in blackbullet

Thanks so much, Is there any plan to release the converter? I don't have a licensed copy on my current machine due to an act of god (ex boyfriend, so maybe an act of the devil) but I do have backups of my .ini files. Just to clarify, the conversion is from ini and bbc into (shot in the dark) .loli files? I do have a dear friend with a current licensed copy, is it possible he can convert my configurations for me into the modern OpenBullet format?
Or have I misunderstood? Thanks again for the incredible work :)


Collection id is not always sent for view PaymentSuccessView(CSRFExemptMixin, View):

This causes an exception when is not sent, here i will show an example with credit card payment and its json anwser
{
  "collection_id": ["155448647"],
  "collection_status": ["approved"],
  "payment_id": ["155448647"],
  "status": ["approved"],
  "external_reference": ["orden-5"],
  "payment_type": ["credit_card"],
  "merchant_order_id": ["3125411900"],
  "preference_id": ["-----------"],
  "site_id": ["MLC"],
  "processing_mode": ["aggregator"],
  "merchant_account_id": ["null"]
}

here with debit card:
{
  "payment_id": ["155448647"],
  "payment_status": ["approved"],
  "external_reference": ["orden-4"],
  "payment_method_id": ["webpay"]
}

as we can see collection id is not sent with debit card payment, but payment_id yes and is the same id.
here is the exception :
Internal Server Error: /mercadopago/post_payment/orden-4
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 581, in get_or_create
    return self.get(**kwargs), False
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 435, in get
    raise self.model.DoesNotExist(
django_mercadopago.models.Notification.DoesNotExist: Notification matching query does not exist.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.NotNullViolation: null value in column "resource_id" of relation "mp_notification" violates not-null constraint
DETAIL:  Failing row contains (5, p, null, 2021-09-10 02:35:34.826117+00, 1, unp, 5).

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/usr/local/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view
    return self.dispatch(request, *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper
    return bound_method(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django_mercadopago/views.py", line 45, in dispatch
    return super().dispatch(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch
    return handler(request, *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django_mercadopago/views.py", line 93, in get
    notification, created = _create_notification(
  File "/usr/local/lib/python3.9/site-packages/django_mercadopago/views.py", line 27, in _create_notification
    notification, created = Notification.objects.update_or_create(
  File "/usr/local/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 608, in update_or_create
    obj, created = self.select_for_update().get_or_create(defaults, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 588, in get_or_create
    return self.create(**params), True
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 453, in create
    obj.save(force_insert=True, using=self.db)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/base.py", line 726, in save
    self.save_base(using=using, force_insert=force_insert,
  File "/usr/local/lib/python3.9/site-packages/django/db/models/base.py", line 763, in save_base
    updated = self._save_table(
  File "/usr/local/lib/python3.9/site-packages/django/db/models/base.py", line 868, in _save_table
    results = self._do_insert(cls._base_manager, using, fields, returning_fields, raw)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/base.py", line 906, in _do_insert
    return manager._insert(
  File "/usr/local/lib/python3.9/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 1270, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1416, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/usr/local/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.IntegrityError: null value in column "resource_id" of relation "mp_notification" violates not-null constraint
DETAIL:  Failing row contains (5, p, null, 2021-09-10 02:35:34.826117+00, 1, unp, 5).

Hmmm, odd. I've never seen that happen (after thousands of orders).
"MLC" is "MercadoLibre Colombia", right? I wonder if it's a quirk (or bug?) that's only seen in that region.
I assume these are not the real numbers, right? It would make no sense that two different payments have the same id.
I guess the right thing to do would be to try using collection_id, and if that's missing, paymen_id. Should also fail if none of them is set:
https://github.com/WhyNotHugo/django-mercadopago/blob/984b952870d2254f75fdf080aa94b1033d024dff/django_mercadopago/views.py#L103

MLC is "mercado libre chile" and yes those are not real numbers.
I asked on mercado pago support and their anwser was "the field payment_id will be always sent in payment notifications, however collection_id can change with integration type, for example can be order id in products that generate orders."
Right now i'm in production with my fork of this repo, i changed collection id with payment_id, and everything is working fine.
But maybe the best solution is what you said, so it wont dont break anything.


chore: fix 'No Response' workflow

All workflows failed due to invalid inputs
https://github.com/remix-run/remix/actions/workflows/no-response.yml
CC/ @ryanflorence

would it kill them to put an option on their example? I obviously have no idea how github workflows work 😆

do we need this on the dev branch too for it to work for PRs against dev?

I think this should work for all created PRs 🤔


agent: fix the issue of missing close process terminal

Kata assumes once a process exits, it's IO will also
close automatically, thus the client will wait on the
process's IO closed and then do some cleanup for this
process. But the issue is that if the process forked
some background children processes running as daemon
process, thus those children process will intherit its
parent terminal, and even its parent exited, its terminal
will not close as the children running.
So this commit will try to fix this issue by detecting
the process's exit and then notify the client that the
process has exited and there's no need to wait on its IO.
Fixes: #370
Signed-off-by: fupan<EMAIL_ADDRESS>

Hi @jodh-intel,  I can add a real test in https://github.com/kata-containers/tests  later.

Thanks @lifupan ! ;)

I'd like to review this properly, please don't merge until I can get a look :)

/cc @bergwolf ^

Hi @sboeuf, the client is kata shim and the containerd shimv2. Take kata shim as example, you can have a look at https://github.com/kata-containers/shim/blob/master/main.go from line 149 to 159, the comments say clearly that this shim has to wait  for every input/output to return before the code tries to go further and wait for the process.

@lifupan @bergwolf  -  you guys agree this should be a candidate for stable branches as well?

Hi  @egernst , yes, I think the stable branch needs this patch.

Hi @sboeuf , I think the libcontainer doesn't needs this fix, and this issue is particular to kata.
It's easy to close process's IO when it exits, but the problem is when to close it after it's exiting to make sure there is no IO contents lost. For runc, containerd shim  will take care of the  process's IO read and the process's exit states. In addition, the shim is the IO read's initiator, and it can make sure
to drain the process's IO before closing it. But for kata, kata's IO read isn't a stream and it depends kata's client calling to drain the IO,  thus it cannot close the IO proactively. Thus kata agent have to figure out is the IO is exhausted  after the process's exiting and then close the IO.
BTW, I can add some more info about how this PR fix this issue in the commit log.


Names of image instances (dreambooth)

What is the allowed maximum length of a file name?
How many tags can I put in the name if I want to teach a model a style?
If I specify the tags in this way: ModelName, ModelNameCar, ModelNameForest (1).png
Will the earlier declared tag take precedence or does each tag have equal weight?
If I want to train a neural network to draw cars exactly in my style, do I need to write "ModelNameCar" or is just "Car" enough?
Can I load the same images into the "Concept Images" block as into the "Instance Images" block, but separated by tags?
That is, can I divide the images into "Car" and "Forest" in Photoshop, and then insert them into the "Concept Images" block?

If I wrote something unclear, point it out to me and I will try to rephrase my question.

@TheLastBen

rename the images to numbers (1.jpg, 2.jpg ...), then use external caption, better than using the filenames to caption the images

rename the images to numbers (1.jpg, 2.jpg ...), then use external caption, better than using the filenames to caption the images

Okay, but what about the other questions?

@TheLastBen

don't use concept images