Replace eval() functions

🐛 Summary
Python has an eval() function which evaluates a string of Python code bandit check has "blacklisted" as an insecure function.
To reproduce
Steps to reproduce the behavior:

Run branch pre-commit: https://github.com/cisagov/pe-reports/tree/AL-working-v1.0

Expected behavior
A pre-commit run --all-files should render no bandit errors.
Any helpful log output or screenshots
Example Test Error:
Test results:
>> Issue: [B307:blacklist] Use of possibly insecure function - consider using safer ast.literal_eval.
   Severity: Medium   Confidence: High
   Location: src/pe_reports/report_metrics.py:191
   More Info: https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html#b307-eval
191                 k = eval(row["right"])

This issue was merged into develop branch per PR#31


Simpler CTranspose + multiplication methods

Okay, hopefully this will be the last attempt needed to kill #9 so we can finally move forward!
This PR defines bunch of multiplication methods that are consistent, using @acroy's method to resolve the row/column vector issues. It also adds actual tests for these methods. They're not exactly comprehensive, but it's a start.
Actually defining the multiplication methods made me realize how messy having separate Conjugate/Transpose types makes things, so I simply removed those types from the picture. If users wish to separately conjugate/transpose coefficient arrays, we'll let them worry about that (or just do so eagerly).
Thoughts?

Also it should be noted that, in the future, we could set up type promotion for basis types that would allow us to expand beyond forcing both arguments to have the same basis type.

Thanks for putting this together. Looks good at a first glance. I will try it out tomorrow. You forgot to call runtests.jl in travis.yml. We probably have to activate Travis for this repo as well.

Ok, Travis should work with the next push/PR (forget the comment about runtests.jl). I have also added a status banner to README.
Otherwise the PR looks good. There are just two things we should keep in mind (and maybe put a comment in the code): 1) Currently we ignore the inner product of the basis functions, i.e., assume an orthonormal basis. 2) The multiplication doesn't work for N>2. We probably want to extend this at least to N=4 (super-operators), but ideally want it to work in general (or at least make it easy to extend).

I don't know why Travis complains...

Did it complain? Everything's turning up green as far as I can see, but I'm not super familiar with Travis so I'm probably missing something. Anyway, thanks for setting it up.
Agreed on the generality points you made. I think for basis products we're going to want to define the functions inner{A,B,S}(a::NTuple{A,FiniteBasis{S}}, b::NTuple{B,FiniteBasis{S}}) and
tensor{A,B,S}(a::NTuple{A,FiniteBasis{S}}, b::NTuple{B,FiniteBasis{S}}), then use those to construct more general multiplication definitions.
Just to be on the safe side, I'll restrict the functions defined here to S<:Orthonormal in the meantime.

Now it looks good (I.e. green). It was probably just the old yml file.


Implement optional dark mode on AIW / OW

Toggling functionality like https://issarice.com/_archive/2017-10-18-8a0c6b4e8dc57204d9c0e20e551468220545defd/?fbclid=IwAR15J_1kWBbAaHyslkNiFZxJFXhJwB8HUEeCjoB2v0ZMeugJP6XnLhVOTT0# will be good.
After we implement, we will play around with it to see if it's worth keeping around and extending to other projects.

I have implemented this and it is live. I didn't put a lot of thought into the choice for colors (I don't use dark mode myself on any website or program, so I don't really have an opinion on what looks good vs bad), so let me know if you have suggestions.

due to the way cookies work, you'll have to set the setting on each of AIW/OW individually
also firefox gives me the following warning:

Cookie “colorCookie” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

i haven't investigated this yet

Vipul writes:

Regarding the Firefox warning, can you try adding ";secure" to https://github.com/riceissa/aiwatch/commit/8499f5570c27f086b4781b67ad79e45c63b7cefb#diff-7f5128ed8c84ab34725f7145aee70750bc2e763b493d9c32e1931edc17a4c72fR18 and the similar line below? The caveat is that thatt secure setting only works on HTTPS sites, so it may be ignored if serving localhost https://stackoverflow.com/questions/37234687/how-to-set-cookie-secure-flag-using-javascript

The cookie warning has been fixed (you may have to do a hard refresh to force the change-theme.js script to be downloaded again).

@vipulnaik Can this be closed now?


AAPT2 error: check logs for details

error: resource color/hint_foreground_material_light (aka myapp.package:color/hint_foreground_material_light) not found.
Message{kind=ERROR, text=error: resource color/hint_foreground_material_light (aka myapp.package:color/hint_foreground_material_light) not found., sources=[C:\Users\Simo\GitHub\android-material-color-picker-dialog\library\src\main\res\layout-land\materialcolorpicker__layout_color_picker.xml:106], original message=, tool name=Optional.of(AAPT)}

I just had the same problem, try updating the reference to 1.2.4, that worked for me.


Localhost Verification in 04-channel

Go through all the places in 04-channel that does proof verification (these are in packet verification and channel handshakes)

[ ] RecvPacket
[ ] AcknowledgePacket
[ ] TimeoutPacket (ORDERED and UNORDERED)
[ ] TimeoutOnClose (ORDERED and UNORDERED)
[ ] ChanOpenTry
[ ] ChanOpenAck
[ ] ChanOpenConfirm
[ ] ChanCloseConfirm

In each place:
Replace connection.Verify... with the following:
func ChannelMethod() {
   // logic prior to proof verification
   // expectedVal is constructed here

    // the if statement is new logic
    // the else statement will house the old existing logic
    if channel.ConnectionHops[0] == "localhost" {
        // get the desired state directly from this chain's channelKeeper
        // this will be a specific Get function dependent on the specific method this is
        actualVal := k.Get(ICS24Path())
        if expectedVal != actual {
             return error
        }
    } else {
        // do counterparty proof verification with underlying client

        connection := k.GetConnection(channel.ConnectionHops[0]

        // this is a specific verify function depending on what method this is
        connection.VerifyChannelState(proof, expectedKey, expectedVal)
    }

   // continue existing logic
}

Here is the example for RecvPacket:
// example of channel function that does
// verification in special localhost case
func (k Keeper) RecvPacket(
	ctx sdk.Context,
	chanCap *capabilitytypes.Capability,
	packet exported.PacketI,
	proof []byte,
	proofHeight exported.Height,
) error {
    // ... recv packet logic

    commitment := types.CommitPacket(k.cdc, packet)

    // packet commitment verification
    if channel.ConnectionHops[0] == "localhost" {
        storedCommit, ok := k.GetPacketCommitment(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), packet.GetSequence())
        if !ok || storedCommit != commitment {
            return error
        }
    } else {
        // do counterparty proof verification with underlying client

        // move GetConnection code down into the else block since it will error on "localhost"
        // because the "localhost" connection doesn't actually exist in-state

        // Connection must be OPEN to receive a packet. It is possible for connection to not yet be open if packet was
	// sent optimistically before connection and channel handshake completed. However, to receive a packet,
	// connection and channel must both be open
	connectionEnd, found := k.connectionKeeper.GetConnection(ctx, channel.ConnectionHops[0])
	if !found {
		return sdkerrors.Wrap(connectiontypes.ErrConnectionNotFound, channel.ConnectionHops[0])
	}

	if connectionEnd.GetState() != int32(connectiontypes.OPEN) {
		return sdkerrors.Wrapf(
			connectiontypes.ErrInvalidConnectionState,
			"connection state is not OPEN (got %s)", connectiontypes.State(connectionEnd.GetState()).String(),
		)
	}

        // verify that the counterparty did commit to sending this packet
	if err := k.connectionKeeper.VerifyPacketCommitment(
		ctx, connectionEnd, proofHeight, proof,
		packet.GetSourcePort(), packet.GetSourceChannel(), packet.GetSequence(),
		commitment,
	); err != nil {
		return sdkerrors.Wrap(err, "couldn't verify counterparty packet commitment")
	}
    }

    // ... continued recv packet logic
}

Hey @AdityaSripal, I started working through the 09-localhost issues a bit ago and wanted to run the first pass by you to ensure everything looks correct before I complete the rest of it.
https://github.com/strangelove-ventures/ibc-go/commit/d8ab0aa81b28bfc98d4c1649d92408a90095a228
Thanks for your time on all of this!!

@jtieri so then you're working on this? I will assign the issue to you then. Thanks a lot!

closing in favour of https://github.com/cosmos/ibc-go/issues/3034


pocketbase: 0.22.15 -> 0.22.17

Release notes: https://github.com/pocketbase/pocketbase/releases/tag/v0.22.17
Changelog: https://github.com/pocketbase/pocketbase/compare/v0.22.15...v0.22.17
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 326314 run on aarch64-darwin 1

1 package built:

pocketbase


Add method for getting all station codes + numbers

Issue raised by: [developer]
What?
Add method for getting all station codes + numbers
https://globalmeteornetwork.org/data/kml_fov/

Not possible, stations should be added at ingestion time


2.0 C# language versions ASP.NET Core projects (project, Razor, scaffolding)

As dan roth for more details

@Rick-Anderson Can you say more about what this one entails?

See #5591

Title: Language support in ASP.NET Core projects
Notes:

Configuring the ASP.NET Core project's language versions in VS isn't intuitive. VS uses the "hidden UI" (referring to project Properties > Build panel > Advanced > Language version DDL).
Talks about Razor, scaffolding, C#, publishing ... because they all get impacted by the version of Roslyn compiler that you bring in as a dependency versus what gets compiled by VS.
https://github.com/aspnet/Razor/issues/1046
Important! :point_right: https://github.com/dotnet/roslyn/issues/20614
https://github.com/dotnet/roslyn/issues/18783

@Rick-Anderson @mairaw @BillWagner
It looks like this ask on this issue has been (mostly) addressed. See :point_right: https://docs.microsoft.com/dotnet/csharp/whats-new/csharp-7-1#language-version-selection
However, it was written for 7.1. The 7.2 topic didn't receive a similar section.
Perhaps to better surface the content, should that section become its own topic and be written to generically apply to C# versions? ... perhaps under https://docs.microsoft.com/dotnet/csharp/whats-new/

We have an issue for this: dotnet/docs#3685  Do you want to take it on?
If you search the docs repo for  you'll find the locations that should link to the new topic.

Do you want to take it on?

It doesn't matter to me, but I've been ordered not to work on other repos while on contract. I need approval.
@Rick-Anderson Do you want to close this as a dup of dotnet/docs#3685? Do you want to approve my working dotnet/docs#3685?

@guardrex  I think @JRAlexander can handle it.

@BillWagner Just so you know, there is a contract stipulation of some sort at play. When I was working with you, Maira, and Ron, I asked about occasionally doing some stuff with Rick and Tom over here on my own time outside of the contract. I was flatly told, "NO! Don't you dare help Rick and Tom!" :smile: lol ...  Now the tables are turned, and I can't do much for the .NET Core docs without probably getting into some hot water somewhere ... even if only with the vendor.

@Rick-Anderson Handle what?

@JRAlexander He's referring to dotnet/docs#3685. This issue is a dup of that one.

Ok, I'll talk with @BillWagner  and @mairaw to see if this should be included in the .NET 2.1 project. Thanks!


Support ruff 0.1.0

ruff 0.1.0 has 2 breaking changes that prevent python-lsp-ruff from working as-is:

--output is now spelled --output-format
Unsafe fixes are no longer applied unless explicitly enabled with --unsafe-fixes

This supports both of those changes so that users can upgrade to the newest ruff. However, this is going to be a pain in the neck for users: those fixes aren't backward compatible with older versions of ruff, so they'll need to upgrade python-lsp-ruff and ruff at the same time. I'm not sure what the alternative here. Maybe add a new mechanism to run ruff --version to see what command line args can be passed in? Gut it out because the new semver policy won't make future changes like this without bumping the minor version (which, in fairness, they did today)? I'll leave those decisions to you, oh wise maintainers! For now, I offer my humble patch to keep the spice flowing.

Hmm. On other reflection, I guess letting Poetry and friends handle that is the right decision. Maybe it'd make sense to release a version 1.5.3 that's identical to 1.5.2, but with pyproject.toml set to only work with ruff < 0.1.0, then another (1.5.4? 1.6.0?) that includes this change. Then future poetry add python-lsp-ruff calls in new environments will work.
It seems like resolvers like poetry would consider either 1.5.2 or 1.6.x (but not 1.5.3) to work with ruff 0.1.0, though. Ugh. I predict this is going to be a bit of a hassle for everyone, no matter how this is addressed.

My Idea would be to:

Release v1.5.3 that limits to ruff<0.1.0 for the old version, and
Release v1.6.0 with this PR with the breaking changes and ruff>=0.1.0, <0.2.0
That would mostly solve the issue as anyone who does not want to update could use v1.5.3 to keep the old ruff, right?

@kstrauser I think there might be a problem with this specific note in https://docs.astral.sh/ruff/configuration/#fix-safety saying that all fixes are shown when using --output-format=json, regardless of whether --unsafe-fixes was given or not. I will check if this will indeed be ignored when trying to format a document

I checked and this does not seem to be a problem since we explicitly set the list of fixable codes when formatting. However https://github.com/astral-sh/ruff/pull/7838 introduced a regression since we use stderr to check if the process was succesfull

@kstrauser Can you check if I am allowed to push commits to the branch in your fork? See here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork

@jhossbach The “Allow edits from maintainers.” box is checked. I haven’t used that feature before. Can you push to it now?

To simplify things and make sure there aren't any permission problems, I've also invited you as a collaborator to my fork.

Ah, the issue was that we had different branch names. I accidentally pushed my branch name to your repo, but I will rebase and push to this branch right away.


yubihsm-shell: fix linking to pcsclite.h

Description of changes
The build of this package failed for me, because one of the dependencies cannot link pcsclite.h. This seems to fix the problem for me, though there may be more elegant ways to fix?
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 334216 run on x86_64-linux 1

2 packages built:

step-kms-plugin
yubihsm-shell

If it is failing in one of the dependencies, we should rather propagate pcslite there to fix this universally.

If it is failing in one of the dependencies, we should rather propagate pcslite there to fix this universally.

I think it's failing in the yubihsm-shell build itself, unless I'm mistaken.

Based on https://cache.nixos.org/log/526wj9mpch6sp0gwhfgxjhnx6bihh3h5-yubihsm-shell-2.5.0.drv:
[ 23%] Building C object ykhsmauth/CMakeFiles/ykhsmauth.dir/error.c.o
[ 23%] Building C object ykhsmauth/CMakeFiles/ykhsmauth.dir/ykhsmauth.c.o
In file included from /build/source/ykhsmauth/internal.h:26,
                 from /build/source/ykhsmauth/ykhsmauth.c:22:
/nix/store/rr2bj6yaa3xn23bakcrhsz756vawyzb0-pcsclite-2.2.3-dev/include/PCSC/winscard.h:41:10: fatal error: pcsclite.h: No such file or directory
   41 | #include <pcsclite.h>
      |          ^~~~~~~~~~~~
compilation terminated.

I'm reading this as a header file in pcsclite.dev failing to find another header in that package

I'm reading this as a header file in pcsclite.dev failing to find another header in that package

Interesting, yet I can see them side-by-side in the nix store, any idea how that might get resolved?
❯ ls -la /nix/store/rr2bj6yaa3xn23bakcrhsz756vawyzb0-pcsclite-2.2.3-dev/include/PCSC
.r--r--r-- 5.4k root root  1 Jan  1970 debuglog.h
.r--r--r--  31k root root  1 Jan  1970 ifdhandler.h
.r--r--r--  16k root root  1 Jan  1970 pcsclite.h
.r--r--r--  16k root root  1 Jan  1970 reader.h
.r--r--r-- 4.2k root root  1 Jan  1970 winscard.h
.r--r--r-- 3.1k root root  1 Jan  1970 wintypes.h

It also looks like the pkg-config file has been installed in the dev output:
❯ tree
.
├── bin
│  └── pcsc-spy
├── include
│  └── PCSC
│     ├── debuglog.h
│     ├── ifdhandler.h
│     ├── pcsclite.h
│     ├── reader.h
│     ├── winscard.h
│     └── wintypes.h
├── lib
│  └── pkgconfig
│     └── libpcsclite.pc
└── nix-support
   └── propagated-build-inputs

Looking at https://github.com/LudovicRousseau/PCSC/issues/89 and https://discourse.nixos.org/t/another-missing-header-question/7119 makes me think this solution is likely a reasonable one?

Okay, based on the following from https://wiki.nixos.org/wiki/C:

However, while the $out/include folder will be included by default, it may sometimes not be enough when the lib puts the header in a subfolder (for instance, gtk2 and gtk3 uses subdirectories like $out/include/gtk-2.0 instead to avoid conflict between versions). To deal with this kind of libraries, one can use pkg-config: the idea is simply to add pkg-config in the nativeBuildInputs, and then to start the buildPhase with:

I think I'll merge this. Happy to adjust later if required.

I've run the build (without my patch) with the CMake flags --trace and -DCMAKE_VERBOSE_MAKEFILE=ON, which resulted in the following build log:
https://gist.github.com/jnsgruk/58056b865692638271683b8f93eb2e42
(cc: @emilylange)

Seems like the failing file is just not getting the pkg-config stuff passed down at all:
cd /build/source/build/ykhsmauth && /nix/store/62zpnw69ylcfhcpy1di8152zlzmbls91-gcc-wrapper-13.3.0/bin/gcc -DDEFAULT_CONNECTOR_URL=\"http://localhost:12345\" -DHAVE_EXPLICIT_BZERO -DOPENSSL_API_COMPAT=0x10000000L -DYKHSMAUTH_ENABLED=\"1\" -D_FORTIFY_SOURCE=2  -flto -Wno-missing-braces -Wno-missing-field-initializers -O3 -DNDEBUG -std=gnu11 -fPIC -DSTATIC -Wall -Wextra -Werror -Wformat -Wformat-nonliteral -Wformat-security -Wshadow -Wcast-qual -Wmissing-prototypes -Wbad-function-cast -pedantic -pedantic-errors -fpie -fpic -O2 -fstack-protector-all -Wno-implicit-fallthrough -MD -MT ykhsmauth/CMakeFiles/ykhsmauth_static.dir/ykhsmauth.c.o -MF CMakeFiles/ykhsmauth_static.dir/ykhsmauth.c.o.d -o CMakeFiles/ykhsmauth_static.dir/ykhsmauth.c.o -c /build/source/ykhsmauth/ykhsmauth.c

I suspect this to be an upstream build system bug. They do seem to set the include path, though. Maybe our libpcsclite.pc is messed up somehow?

Maybe our libpcsclite.pc is messed up somehow?

The contents of our pkgconfig file is below, I wonder if that libdir line should really end lib/PCSC in order for it to work - is that something we could just patch in the postInstall?
prefix=/nix/store/0v1qyxisn7hhf63wg3c6kpc7dwhcn90w-pcsclite-2.2.3
includedir=/nix/store/rr2bj6yaa3xn23bakcrhsz756vawyzb0-pcsclite-2.2.3-dev/include
libdir=/nix/store/9pb5dql4fnbdrq8wsjan0la13b2hwgi0-pcsclite-2.2.3-lib/lib

usbdropdir=/var/lib/pcsc/drivers
serialconfdir=/etc/reader.conf.d

Name: PCSC Lite
Description: PC/SC smart card interface
Version: 2.2.3
Libs: -L${libdir} -lpcsclite
Libs.private: -pthread
Cflags: -I${includedir}/PCSC

We’re not getting to the linking stage at all, so I don’t think that can be relevant. And the Cflags looks fine… but I wonder if includedir is causing issues here. Hmm.

@SuperSandro2000 any ideas here? My Cmake/pkg-config foo has run out!

Hmm, looking through the build output of pcsclite if I build it locally, I can see where the includedir is being patched and I think it's omitting the prefix?
https://github.com/NixOS/nixpkgs/blob/1bd503aa21f99634e551fa624d8a1a14ccdf5afc/pkgs/build-support/setup-hooks/multiple-outputs.sh#L178
I'll need to do some sed research to decode that expression, but I think this might be responsible for omitting /PCSC from the end of the includedir...

@SuperSandro2000 any ideas here? My Cmake/pkg-config foo has run out!

No, sorry 😅

I think that's a good call. I did manage to make this work by patching the pcsclite package to manually fiddle the pkgconfig file, but that doesn't feel like a better route...
diff --git a/pkgs/tools/security/pcsclite/default.nix b/pkgs/tools/security/pcsclite/default.nix
index eedec6b239fd..82f79202181d 100644
--- a/pkgs/tools/security/pcsclite/default.nix
+++ b/pkgs/tools/security/pcsclite/default.nix
@@ -85,6 +85,10 @@ stdenv.mkDerivation (finalAttrs: {
     moveToOutput bin/pcsc-spy "$dev"
   '';

+  postFixup = ''
+    sed -i "/^includedir=/s|=''${dev}/include|=''${dev}/include/PCSC|" $dev/lib/pkgconfig/libpcsclite.pc
+  '';
+
   nativeBuildInputs = [
     meson
     ninja


Failed to deprovision AWS

It fails with the following message

TASK [cloud-resources-rollback : AWS Delete All in one OpenShift Node] *********
fatal: [localhost]: FAILED! => {"changed": false, "msg": "instance_ids list is required for absent state"}
localhost                  : ok=2    changed=0    unreachable=0    failed=1

@rafabene  commit 283419ef6b37d2c7800a397ced84cab1ca931765 solves the issues, please validate

Validated.


Adapted the SOURCE_ROOT patch to keystone-auth provision

I adapted the SOURCE_ROOT fix(*) to keystone-auth provision.
By applying this patch, we can launch multiple vms.

See commitNo:  f2b6c76c54cf493c8279258f7f1987a3ba301e0f

Atsushi, thanks! Yeah, when I tries to test container-sync patch, vagrant-swift-all-in-one with keystone doesn't work because of source_root. I tested this and worked for me.


lazy fetch only needed files + pin git repo to commit hash

i need to mount the git repo/tree at a specific commit, for better stability
but, most git servers (including github) have
uploadpack.allowReachableSHA1InWant = false (default value)
so fetch-by-commit requires a nontrivial workaround ...
any plans to support this?
PRs welcome? ; )
related: https://github.com/NixOS/nixpkgs/pull/135545/files
edit: just noticed, on mount, gitfs does a full shallow clone ...
but i need something much more lightweight, which downloads files only on demand.
use case: mount https://github.com/NixOS/nixpkgs = 250 MBytes extracted, of which i only need a few KBytes
related:
https://github.com/higlass/simple-httpfs
https://github.com/fangfufu/httpdirfs (written in C)

lazy fetch only needed files
this is solved in google's slothfs (aka gitfs), but only works with "Gerrit/Gitiles based Git hosting" = no github
background: access monorepos from thin clients

the tree contains a significant amount of unused data

no github

on github, we can use api.github.com to browse commits and trees
and use raw.githubusercontent.com to fetch blobs
this works well for small projects, where only few files are actually needed (syscalls: read, readdir, stat, attr)
for larger projects, this can be too slow, so git clone becomes more attractive
pin git repo to commit hash
the goal here is file-deduplication on fat clients.
fat client = the full git repo was fetched with some depth (mostly-shallow clone),
so we have local access to old versions
what i want is something like this:
gitfs interface

/commit/:sha/tree/ -> root directory by commit sha
/tree/:sha/ -> root directory by tree sha (can be a subfolder of the repo)
/blob/:sha -> file by blob sha

sample:
$ gitfs mount https://github.com/presslabs/gitfs.git /tmp/demo
$ cd /tmp/demo
$ less commit/12886ec5b9c7e103bfcab0cd37a8333873382fae/tree/README.md

this would show exactly this file:
https://github.com/presslabs/gitfs/blob/12886ec5b9c7e103bfcab0cd37a8333873382fae/README.md
https://raw.githubusercontent.com/presslabs/gitfs/12886ec5b9c7e103bfcab0cd37a8333873382fae/README.md


feat: Add Structured Logging error capture integration test

hmm our integration tests seem to be running out of memory or something. Any ideas on that @Danwakeem ?

@Mmarzex unfortunately I think you just have to wait a minute or two before the memory issue fixes itself 😢

I did wait a while between trying again 😢


n8n: 1.70.1 -> 1.71.3, package improvements

Now r-ryantm should only post stable (non-prerelease) n8n updates.
Thanks for the suggestion @liberodark in https://github.com/NixOS/nixpkgs/pull/364897#issuecomment-2541336043!
Superseeds https://github.com/NixOS/nixpkgs/pull/364897
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Reduced the size of the built package from 2018M to 890M, and the fixup phase now takes half as long, which can save 10 minutes of build time on a slower machine with an HDD.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 364947

x86_64-linux

:white_check_mark: 1 package built:

n8n

Further reduced the built package size to 671M


I can not see my message in Alarms

First , I should thanks for this project, It help me solve the problem of monitor .
System Details
Versions

Type
Version

Kibana
6.4.2

Elasticsearc

Server OS
centos

Browser
chrome

Bug Details
Bug Description
Steps to Reproduce

I download sentinl for my elk[docker image elk] project.
I write the watchers configration
But I can not see the error message in the 'Alarms'
And I want to send the error message when it checks the error log,But it can not get either

Expected Behavior
I want to see the log's detail message in 'Alarms'
I want to send thd log's detail message in 'Action'
Sample of data you have in Elasticsearch
{
  "_index": "application-2018.11-system",
  "_type": "doc",
  "_id": "cRQrOWcB8UWhRdOWFnxi",
  "_version": 1,
  "_score": null,
  "_source": {
    "@version": "1",
    "facility": "logstash-gelf",
    "location": {
      "region_code": "33",
      "location": {
        "lon": 120.1614,
        "lat": 30.2936
      },
      "country_code2": "CN",
      "latitude": 30.2936,
      "ip": "<IP_ADDRESS>",
      "country_name": "China",
      "country_code3": "CN",
      "city_name": "Hangzhou",
      "continent_code": "AS",
      "timezone": "Asia/Shanghai",
      "region_name": "Zhejiang",
      "longitude": 120.1614
    },
    "logger": "com.bxm.localnews.common.handler.CustomizeExceptionHandler",
    "className": "com.bxm.localnews.common.handler.CustomizeExceptionHandler",
    "message": "request uri:[/api/privileges/detail],request param:[chnl=outsideregister|cliTime=1542852382618|curVer=1|devcId=1|platform=3]",
    "thread": "http-nio-8080-exec-8",
    "requestIp": "<IP_ADDRESS>",
    "simpleClassName": "CustomizeExceptionHandler",
    "host": "h21-prod",
    "source_host": "<IP_ADDRESS>",
    "level": "ERROR",
    "@timestamp": "2018-11-22T02:06:24.240Z",
    "type": "system"
  },
  "fields": {
    "@timestamp": [
      "2018-11-22T02:06:24.240Z"
    ]
  },
  "highlight": {
    "level": [
      "@kibana-highlighted-field@ERROR@/kibana-highlighted-field@"
    ]
  },
  "sort": [
<PHONE_NUMBER>240
  ]
}

Full Watcher JSON
{
  "actions": {
    "Webhook_7f20289e-9d9c-416f-9cd3-401a938fb410": {
      "name": "Webhook",
      "throttle_period": "5m",
      "webhook": {
        "priority": "high",
        "stateless": false,
        "method": "POST",
        "host": "oapi.dingtalk.com",
        "port": "443",
        "path": "/robot/send?access_token=xxxxxxxxxxx",
        "body": "{\r\n    \"msgtype\": \"link\", \r\n    \"link\": {\r\n        \"text\":\"it has an error!\", \r\n        \"title\": \"please solve it \", \r\n        \"picUrl\": \"\", \r\n        \"messageUrl\": \"http://<IP_ADDRESS>:15601\"\r\n    }\r\n}",
        "headers": {
          "Content-Type": "application/json"
        },
        "auth": "",
        "message": "",
        "use_https": true
      }
    }
  },
  "input": {
    "search": {
      "request": {
        "index": [
          "*"
        ],
        "body": {
          "query": {
            "bool": {
              "must": [
                {
                  "query_string": {
                    "analyze_wildcard": true,
                    "query": "\"error\""
                  }
                },
                {
                  "range": {
                    "@timestamp": {
                      "gte": "now-5m",
                      "lte": "now",
                      "format": "epoch_millis"
                    }
                  }
                }
              ],
              "must_not": []
            }
          }
        }
      }
    }
  },
  "condition": {
    "script": {
      "script": "payload.hits.total>=1"
    }
  },
  "transform": {
    "script": {}
  },
  "trigger": {
    "schedule": {
      "later": "every 5 minutes"
    }
  },
  "disable": false,
  "report": false,
  "title": "watcher_localnews",
  "save_payload": false,
  "spy": false,
  "impersonate": false
}

Screenshots (if relevant)

Any additional information
My english is not good .I hope it won't inconvenience you too much.

In your watcher action, you have the message property. It is empty.

Thanks for your answer very much.  e ... But How to put the value to messgae ? Which properties should  I add in the watchers' configration?  I can not see the detail for this in the guide .

You put a value to the webhook action "message" property manualy
{
  "actions": {
    "Webhook_7f20289e-9d9c-416f-9cd3-401a938fb410": {
      "name": "Webhook",
      "throttle_period": "5m",
      "webhook": {
        "priority": "high",
        "stateless": false,
        "method": "POST",
        "host": "oapi.dingtalk.com",
        "port": "443",
        "path": "/robot/send?access_token=xxxxxxxxxxx",
        "body": "{\r\n    \"msgtype\": \"link\", \r\n    \"link\": {\r\n        \"text\":\"it has an error!\", \r\n        \"title\": \"please solve it \", \r\n        \"picUrl\": \"\", \r\n        \"messageUrl\": \"http://<IP_ADDRESS>:15601\"\r\n    }\r\n}",
        "headers": {
          "Content-Type": "application/json"
        },
        "auth": "",
        "message": "some value",
...

Maybe you want to put the following data in the alarms message?
"message": "request uri:[/api/privileges/detail],request param:[chnl=outsideregister|cliTime=1542852382618|curVer=1|devcId=1|platform=3]",

If yes, webhook action doesn't do it. But I think it is a good feature request and I'm going to add it to our enhancements queue. For now, you can have a workaround for this. Add a new action, email html, in this watcher or in a new watcher. In the new action you can have a thing like this
{
  "actions": {
    "email_html_alarm_f1fff0b8-504f-4427-8e25-1dd2952c2892": {
      "name": "email html alarm",
      "throttle_period": "1s",
      "email_html": {
        "stateless": false,
        "subject": "alarm",
        "priority": "high",
        "html": "
Hi {{watcher.username}}
\n
There are {{payload.hits.total}} results found by the watcher {{watcher.title}}.
\n\n
\n
\n
This watcher sends alerts based on the following criteria:
\n

{{watcher.wizard.chart_query_params.queryType}} of {{watcher.wizard.chart_query_params.over.type}} over the last {{watcher.wizard.chart_query_params.last.n}} {{watcher.wizard.chart_query_params.last.unit}} {{watcher.wizard.chart_query_params.threshold.direction}} {{watcher.wizard.chart_query_params.threshold.n}} in index {{watcher.wizard.chart_query_params.index}}

\n
",
        "to": "trex@cave",
        "from": "trex@cave"
      }
    }
...

Look at "html" property. You can access Elasticsearch payload data using (mustache syntax)[https://mustache.github.io/mustache.5.html]. Here you can get the error message you have.
If you use email action, use mustache in the body property.

Sorry , I am a bit confused. you mean that  if I use the action of webhook (like dingtalk) I can not get the log's error detail message ? The only way to get log's error message is using email. Is that right ?
Actually My situation is that : When my log has an error  I want to know the log's error detail message by webhook(like dingtalk). By reading your answer it seems can not realize.

I see the issue #229,you said  'Elasticsearch documents that you receive after a watcher execution are objects inside payload.hits.hits array'.  In my case , the messge detail is  ' payload.hits.hits[0].message ',is that right ? So  I change the watchers like that:
  "actions": {
    "Webhook_7f20289e-9d9c-416f-9cd3-401a938fb410": {
      "name": "Webhook",
      "throttle_period": "5m",
      "webhook": {
        "priority": "high",
        "stateless": false,
        "method": "POST",
        "host": "oapi.dingtalk.com",
        "port": "443",
        "path": "/robot/send?access_token=xxxxxxxxxxx",
        "body": "{\r\n    \"msgtype\": \"link\", \r\n    \"link\": {\r\n        \"text\":\"the error is **_{{payload.hits.hits[0].message}}_**\", \r\n        \"title\": \"please solve it \", \r\n        \"picUrl\": \"\", \r\n        \"messageUrl\": \"http://<IP_ADDRESS>:15601\"\r\n    }\r\n}",
        "headers": {
          "Content-Type": "application/json"
        },
        "auth": "",
        "message": "",
        "use_https": true
      }
    }

But it can not .

@SuperNoobTao

it successfully:

How do you configure it? until now ,i can't get the error message from elastic index.


Should not use sub process for build in modern mode

Version
3.9.0
Environment info
  System:
    OS: macOS 10.14.5
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.9.4 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 75.0.3770.142
    Firefox: 68.0
    Safari: 12.1.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.0.0
    @vue/babel-preset-app:  3.9.2
    @vue/babel-preset-jsx:  1.0.0
    @vue/babel-sugar-functional-vue:  1.0.0
    @vue/babel-sugar-inject-h:  1.0.0
    @vue/babel-sugar-v-model:  1.0.0
    @vue/babel-sugar-v-on:  1.0.0
    @vue/cli-overlay:  3.9.0
    @vue/cli-plugin-babel: ^3.9.0 => 3.9.2
    @vue/cli-plugin-eslint: ^3.9.0 => 3.9.2
    @vue/cli-service: ^3.9.0 => 3.9.3
    @vue/cli-shared-utils:  3.9.0
    @vue/component-compiler-utils:  2.6.0 (3.0.0)
    @vue/eslint-config-standard: ^4.0.0 => 4.0.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^5.0.0 => 5.2.3
    vue: ^2.6.10 => 2.6.10
    vue-eslint-parser:  2.0.3
    vue-hot-reload-api:  2.3.3
    vue-loader:  15.7.1
    vue-meta: ^2.0.5 => 2.0.5
    vue-router: ^3.0.3 => 3.0.7
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.10 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vue-tweet-embed: ^2.3.0 => 2.3.0
    vuex: ^3.0.1 => 3.1.1
  npmGlobalPackages:
    @vue/cli: 3.4.0

Steps to reproduce
As async webpack config is currently not supported (https://github.com/vuejs/vue-cli/issues/3328), one alternative is to make use of local plugin as suggested by @LinusBorg (https://github.com/vuejs/vue-cli/issues/3328#issuecomment-455788257).
However, this is broken when modern mode is turned on as the sub process to build modern bundle does not inherit the api object.
// plugin.js

module.exports = (api, options) => {
  api.registerCommand('build:custom', async (args) => {
    return fetch(url).then(data).then(data => {
      api.chainWebpack(config => {
        // update config with async data
      }
      return await api.service.run('build', args)
    }
}

The bug is related to this line https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/cli-service/lib/commands/build/index.js#L63
It seems the only way to get modern mode to work is to overwrite the build command:
// plugin.js

module.exports = (api, options) => {
  const {build} = api.service.commands
  const buildFn = build.fn
  build.fn = (...args) => {
  return fetch(url).then(data => {
    api.chainWebpack(config => {
      // update config with async data
    }
    return buildFn(...args)
  }
}

However, a custom build command is preferred as it leaves the original build command untouched for future reuse. Is there any reason for using a sub process instead of calling build(args, api, options) for the second build?
What is expected?
Modern mode should work with local plugin which hooks into build command
What is actually happening?
api object is not passed to sub process build thereby causing injected change to not show up in second build

There's an undocumented option in @vue/babel-preset-app called absoluteRuntime.
See https://github.com/vuejs/vue-cli/blob/dev/packages/%40vue/babel-preset-app/index.js#L60-L67
https://babeljs.io/docs/en/babel-plugin-transform-runtime#absoluteruntime

Replied to the wrong issue… Sorry😂

I was just about to post an issue when I encountered this thread. This is exactly the problem I'm experiencing with the proposed solution of using a local plugin as @yongjun21 referenced above.

Solving this problem by supporting async configuration file is better, will have a look at this


opt use avl tree to construct continuous union operand

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 50.61 seconds
stream load tsv:          538 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         21 seconds loaded<PHONE_NUMBER> Bytes, about 107 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.9 seconds inserted 10000000 Rows, about 346K ops/s
storage size:<PHONE_NUMBER>3 Bytes

could you describe the beinfit of avl tree please?
does this benifit also exist in intersect/subtract? expecially, A - B1- B2 -B3 = A - (B1 U B2 U B3), how about organize (B1 U B2 U B3) by an avl tree?


UX: figure out right to left languages

Think about what we need to do to be sure that the page works well in Japanese, Hebrew and to other right to left languages.

https://getbootstrap.com/docs/5.0/getting-started/rtl/


AccountInfo hasn't sufficients

pub struct AccountInfoGen<Index, AccountData> {
    /// The number of transactions this account has sent.
    pub nonce: Index,
    /// The number of other modules that currently depend on this account's existence. The account
	/// cannot be reaped until this is zero.
    pub consumers: RefCount,
    /// The number of other modules that allow this account to exist. The account may not be reaped
	/// until this and `sufficients` are both zero.
    pub providers: RefCount,
    /// The number of modules that allow this account to exist for their own purposes only. The
	/// account may not be reaped until this and `providers` are both zero.
    pub sufficients: RefCount,
    /// The additional data that belongs to this account. Used to store the balance(s) in a lot of
	/// chains.
    pub data: AccountData,
}

we need remove sufficients?

This is an exact copy from frame-system. If it is not there, then the node template is probably too new.


MSYS2_PATH_TYPE default

The default in MSYS2 is "minimal" aka MSYS2 directories + default Windows directories. setup-msys2 defaults to "strict" which might be unexpected (things like cmd.exe are not available).
I wonder if changing the default now would still be possible.

It might, but it may not be desirable. Virtual environments provided by GitHub do include Git for Windows, which is added to the PATH by default. Incidentally, VSCode supports Git for Windows only, and they refuse to support MSYS2. I don't know whether a relation exists between both facts.
The point is that the default environment contains potentially conflicting tools, such as tar, git, ssh, etc. Unless we can guarantee that none of those is included in the minimal context, I'd prefer users to be aware that MSYS2 is strictly that: MSYS2/MINGW.
FWIW, an option is provided: https://github.com/msys2/setup-msys2#path-type

https://github.com/msys2/MSYS2-packages/blob/915946a637e1f2b7e26e32782f3af322009293db/filesystem/profile#L28
It only adds those things which are in PATH on a fresh Windows install.

I picked your PR and modified it to change the default path-type to minimal. According to your last reference, I think it is an acceptable change for v1.2.0.

I suspect various tools expect those directories to be in PATH, but I'm also not sure because I've never worked in such an environment.

As a matter of fact, option path-type was added because some user needed it when using another action to setup golang: numworks/setup-msys2#13.


Clean up code around VarDecl::setType()

We're going through a lot of effort to set these types but its unnecessary because they're actually set for us automatically. Also, clean up some of the code for 'invalid' decls and be less eager about splatting random ErrorTypes everywhere.

@swift-ci Please test

@swift-ci Please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - e30d3a7d2ab8f448b0af228c44adc80258ef0b2d

@xedin I fixed the diagnostics regression in the first patch.

https://github.com/apple/swift-lldb/pull/817
@swift-ci Please smoke test

https://github.com/apple/swift-lldb/pull/817
@swift-ci Please smoke test


Evaluation: CARRY OUT QUANTITATIVE

Benchmarks

pow
int list
convolution
regex
while
flowchart [success]
lambda [failed] (?)

Qualitative:

Pow
Int list
While
Regex
Flowchart
Lambda


Add chat

Add chat for currently logged in players

Maybe just add a dot to the user avatar to show if they are online?


Request for Icon support in Navigation nodes

Description
When configuring navigation nodes it would be helpful to also be able to define small 16x16 icons.

I.e this icon set:
https://openui5.hana.ondemand.com/1.40.10/iconExplorer.html

Top header navigation nodes should display only an icon in case an icon is configured for the node


Update top_level_toc.yml

Restore landingPageType element to top-level Container Registry element

@annelo-msft - Restoring element removed in PR 1982.  I think this is needed so that link to "Overview" landing page in the Container Registry node resolves (https://docs.microsoft.com/dotnet/api/overview/azure/containerregistry)

Thanks @dlepow!  Adding @danieljurek, our docs expert, for approval.

Thanks, folks! @danieljurek or @annelo-msft, could you please merge this PR?


Update for getting-started-python.md (fixes #323)

The updated file contains updated documentation to match readthedocs, most noticeably changing from Python 3.5 to Python 3.6.
The relative links under "Further Reading" were not functional. The links are now fixed.

👍  This is a better PR than #448.
Just wondering -- does it make sense to duplicate the neo-python docs into these docs, or should wes imply link to the neo-python docs? @localhuman

@metachris You are right. I updated the file to directly point to neo-python docs. Please review it.
https://github.com/neo-project/docs/pull/450

@Celia18305 why was this closed? The neo-python docs on the homepage are outdated, and this PR fixes them.

Hi @metachris , becasue in the later PR #450 the file was updated to directly point to neo-python docs. I approved that update.

Thanks! Didn't notice...


If there are repeated clusters on the cluster when scripting it does not through and error

Merge pull request #250 from knoxberry/master  …
https://github.com/LabVIEW-DCAF/TagEditorCore/pull/250
Fixed with the commit from Ian in Tag Editor code. The script shoudl not be on templates


kubernetes-system-spec post-start script fails

I am trying to deploy the pivotal PKS, on a vSphere environment with NSX-T. (completely nested)
following the https://www.virtuallyghetto.com/2018/03/getting-started-with-vmware-pivotal-container-service-pks-part-1-overview.html tutorial and fully build reference architecture https://www.hanymichaels.com/2018/04/27/reference-architecture-building-an-on-premise-kubernetes-solution-with-vmware-pks-and-nsx-t/
My deployment rolls out the master and 3 workers perfectly but fails on 1 of 3 post-deploy scripts.
As this is new to me, I tried to look into the logs of the bosh task & Kube master. but I got no clue of why the kubernetes-system-spec fails.
thanks in advance.
bosh debug log (last part):
D, [2018-05-31T06:55:37 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.e291bd32-1419-4d3f-abb1-9e573552b683"}
D, [2018-05-31T06:55:37 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.e291bd32-1419-4d3f-abb1-9e573552b683 {"value":{"agent_task_id":"53ccf286-ffde-4b38-7697-2170d37fa838","state":"running"}}
D, [2018-05-31T06:55:38 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.2dda8375-9f9e-4b39-9a13-522efd18c783"}
D, [2018-05-31T06:55:38 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.2dda8375-9f9e-4b39-9a13-522efd18c783 {"value":{"agent_task_id":"53ccf286-ffde-4b38-7697-2170d37fa838","state":"running"}}
D, [2018-05-31T06:55:39 #32661] [task:120-checkpoint] DEBUG -- DirectorJobRunner: (0.000522s) BEGIN
D, [2018-05-31T06:55:39 #32661] [task:120-checkpoint] DEBUG -- DirectorJobRunner: (0.001870s) UPDATE "tasks" SET "checkpoint_time" = '2018-05-31 06:55:39.013729+0000' WHERE ("id" = 120)
D, [2018-05-31T06:55:39 #32661] [task:120-checkpoint] DEBUG -- DirectorJobRunner: (0.003349s) COMMIT
D, [2018-05-31T06:55:39 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.62bd2147-a323-47b7-a84c-ac4238aa7b93"}
D, [2018-05-31T06:55:39 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.62bd2147-a323-47b7-a84c-ac4238aa7b93 {"value":{"agent_task_id":"53ccf286-ffde-4b38-7697-2170d37fa838","state":"running"}}
D, [2018-05-31T06:55:40 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.2c9288d9-fac5-45c4-a06c-7095059ca9ea"}
D, [2018-05-31T06:55:40 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.2c9288d9-fac5-45c4-a06c-7095059ca9ea {"value":{"agent_task_id":"53ccf286-ffde-4b38-7697-2170d37fa838","state":"running"}}
D, [2018-05-31T06:55:41 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.03d439e9-93b0-4a47-b6f0-7b8195509f8a"}
D, [2018-05-31T06:55:41 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.03d439e9-93b0-4a47-b6f0-7b8195509f8a {"value":{"agent_task_id":"53ccf286-ffde-4b38-7697-2170d37fa838","state":"running"}}
D, [2018-05-31T06:55:42 #32661] [] DEBUG -- DirectorJobRunner: Renewing lock: lock:deployment:service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b
D, [2018-05-31T06:55:42 #32661] [] DEBUG -- DirectorJobRunner: (0.041178s) UPDATE "locks" SET "expired_at" = '2018-05-31 06:59:43.530379+0000' WHERE (("name" = 'lock:deployment:service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b') AND ("uid" = 'd77385a0-b330-4380-9b7a-9bf98274eebc'))
D, [2018-05-31T06:55:42 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.0db4f783-1dfc-43cc-be31-39deb45419e4"}
D, [2018-05-31T06:55:42 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.0db4f783-1dfc-43cc-be31-39deb45419e4 {"value":{"agent_task_id":"53ccf286-ffde-4b38-7697-2170d37fa838","state":"running"}}
D, [2018-05-31T06:55:43 #32661] [] DEBUG -- DirectorJobRunner: SENT: agent.e93b4202-1335-4330-bfe5-4978e215cc79 {"protocol":3,"method":"get_task","arguments":["53ccf286-ffde-4b38-7697-2170d37fa838"],"reply_to":"director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.e23e476d-0e00-4e05-9e56-feadbaade923"}
D, [2018-05-31T06:55:43 #32661] [] DEBUG -- DirectorJobRunner: RECEIVED: director.444af1b5-278d-4798-9699-a6ef39f2cfdc.e93b4202-1335-4330-bfe5-4978e215cc79.e23e476d-0e00-4e05-9e56-feadbaade923 {"exception":{"message":"Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs: kubernetes-system-specs. Successful Jobs: kube-controller-manager, pks-nsx-t-resource-check."}}
E, [2018-05-31T06:55:43 #32661] [] ERROR -- DirectorJobRunner: Worker thread raised exception: Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs: kubernetes-system-specs. Successful Jobs: kube-controller-manager, pks-nsx-t-resource-check. - /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:277:in handle_method' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:332:in handle_message_with_retry'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:50:in method_missing' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:388:in get_task_status'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:198:in wait_for_task' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:352:in send_message'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:164:in run_script' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/post_deployment_script_runner.rb:36:in block (4 levels) in run_post_deploys_after_deployment'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh_common-0.0.0/lib/common/thread_pool.rb:77:in block (2 levels) in create_thread' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh_common-0.0.0/lib/common/thread_pool.rb:63:in loop'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh_common-0.0.0/lib/common/thread_pool.rb:63:in block in create_thread' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in block in create_with_logging_context'
D, [2018-05-31T06:55:43 #32661] [] DEBUG -- DirectorJobRunner: Thread is no longer needed, cleaning up
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: Shutting down pool
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.003481s) DELETE FROM "locks" WHERE (("name" = 'lock:deployment:service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b') AND ("uid" = 'd77385a0-b330-4380-9b7a-9bf98274eebc'))
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: Deleted lock: lock:deployment:service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b uid: d77385a0-b330-4380-9b7a-9bf98274eebc
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.000126s) BEGIN
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.000742s) INSERT INTO "events" ("parent_id", "timestamp", "user", "action", "object_type", "object_name", "error", "task", "deployment", "instance", "context_json") VALUES (NULL, '2018-05-31 06:55:43.872317+0000', 'pivotal-container-service-e53e4d347e5e339296bb', 'release', 'lock', 'lock:deployment:service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b', NULL, '120', 'service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b', NULL, '{}') RETURNING *
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.043147s) COMMIT
I, [2018-05-31T06:55:43 #32661] [task:120]  INFO -- DirectorJobRunner: sending update deployment error event
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: SENT: hm.director.alert {"id":"0ee52c42-9144-4721-9447-4081e4971e18","severity":3,"source":"director","title":"director - error during update deployment","summary":"Error during update deployment for 'service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b' against Director '549e5dae-d3e4-4313-871c-9292ec9ad228': #<Bosh::Director::RpcRemoteException: Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs: kubernetes-system-specs. Successful Jobs: kube-controller-manager, pks-nsx-t-resource-check.>","created_at":1527749743,"deployment":"service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b"}
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.000511s) BEGIN
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.000716s) INSERT INTO "events" ("parent_id", "timestamp", "user", "action", "object_type", "object_name", "error", "task", "deployment", "instance", "context_json") VALUES (876, '2018-05-31 06:55:43.926727+0000', 'pivotal-container-service-e53e4d347e5e339296bb', 'create', 'deployment', 'service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b', 'Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs: kubernetes-system-specs.  Failed Jobs: kubernetes-system-specs. Successful Jobs: kube-controller-manager, pks-nsx-t-resource-check."}}
') WHERE ("id" = 120)
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.003690s) COMMIT
E, [2018-05-31T06:55:43 #32661] [task:120] ERROR -- DirectorJobRunner: Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs: kubernetes-system-specs. Successful Jobs: kube-controller-manager, pks-nsx-t-resource-check.
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:277:in handle_method' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:332:in handle_message_with_retry'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:50:in method_missing' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:388:in get_task_status'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:198:in wait_for_task' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:352:in send_message'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/agent_client.rb:164:in run_script' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh-director-0.0.0/lib/bosh/director/post_deployment_script_runner.rb:36:in block (4 levels) in run_post_deploys_after_deployment'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh_common-0.0.0/lib/common/thread_pool.rb:77:in block (2 levels) in create_thread' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh_common-0.0.0/lib/common/thread_pool.rb:63:in loop'
/var/vcap/packages/director/gem_home/ruby/2.4.0/gems/bosh_common-0.0.0/lib/common/thread_pool.rb:63:in block in create_thread' /var/vcap/packages/director/gem_home/ruby/2.4.0/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in block in create_with_logging_context'
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.000576s) SELECT * FROM "tasks" WHERE ("id" = 120) LIMIT 1
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.000127s) BEGIN
D, [2018-05-31T06:55:43 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.001835s) UPDATE "tasks" SET "state" = 'error', "timestamp" = '2018-05-31 06:55:43.976670+0000', "description" = 'create deployment', "result" = 'Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs:...', "output" = '/var/vcap/store/director/tasks/120', "checkpoint_time" = '2018-05-31 06:55:39.013729+0000', "type" = 'update_deployment', "username" = 'pivotal-container-service-e53e4d347e5e339296bb', "deployment_name" = 'service-instance_0c179338-7245-4df1-824e-913f5eeb0f5b', "started_at" = '2018-05-31 05:51:33.916293+0000', "event_output" = '{"time":1527745894,"stage":"Preparing deployment","tags":[],"total":1,"task":"Preparing deployment","index":1,"state":"started","progress":0}
{"time":1527745910,"stage":"Preparing deployment","tags":[],"total":1,"task":"Preparing deployment","index":1,"state":"finished","progress":100}
{"time":1527745944,"stage":"Preparing package compilation","tags":[],"total":1,"task":"Finding packages to compile","index":1,"state":"started","progress":0}
{"time":1527745944,"stage":"Preparing package compilation","tags":[],"total":1,"task":"Finding packages to compile","index":1,"state":"finished","progress":100}
{"time":1527745944,"stage":"Creating missing vms","tags":[],"total":4,"task":"master/dc6c4011-80e7-4a9b-922e-5366033e377d (0)","index":1,"state":"started","progress":0}
{"time":1527745944,"stage":"Creating missing vms","tags":[],"total":4,"task":"worker/6d6a4f8c-4431-406e-8381-6cc2069dc860 (0)","index":2,"state":"started","progress":0}
{"time":1527745944,"stage":"Creating missing vms","tags":[],"total":4,"task":"worker/acc08d9e-4cf1-46ba-8d01-af9b9aede81a (2)","index":4,"state":"started","progress":0}
{"time":1527745944,"stage":"Creating missing vms","tags":[],"total":4,"task":"worker/411628d6-4131-452b-9e86-0ee4547a9a7b (1)","index":3,"state":"started","progress":0}
{"time":1527746099,"stage":"Creating missing vms","tags":[],"total":4,"task":"worker/411628d6-4131-452b-9e86-0ee4547a9a7b (1)","index":3,"state":"finished","progress":100}
{"time":1527746122,"stage":"Creating missing vms","tags":[],"total":4,"task":"worker/6d6a4f8c-4431-406e-8381-6cc2069dc860 (0)","index":2,"state":"finished","progress":100}
{"time":1527746124,"stage":"Creating missing vms","tags":[],"total":4,"task":"worker/acc08d9e-4cf1-46ba-8d01-af9b9aede81a (2)","index":4,"state":"finished","progress":100}
{"time":1527746134,"stage":"Creating missing vms","tags":[],"total":4,"task":"master/dc6c4011-80e7-4a9b-922e-5366033e377d (0)","index":1,"state":"finished","progress":100}
{"time":1527746134,"stage":"Updating instance","tags":["master"],"total":1,"task":"master/dc6c4011-80e7-4a9b-922e-5366033e377d (0) (canary)","index":1,"state":"started","progress":0}
{"time":1527746424,"stage":"Updating instance","tags":["master"],"total":1,"task":"master/dc6c4011-80e7-4a9b-922e-5366033e377d (0) (canary)","index":1,"state":"finished","progress":100}
{"time":1527746424,"stage":"Updating instance","tags":["worker"],"total":3,"task":"worker/6d6a4f8c-4431-406e-8381-6cc2069dc860 (0) (canary)","index":1,"state":"started","progress":0}
{"time":1527747089,"stage":"Updating instance","tags":["worker"],"total":3,"task":"worker/6d6a4f8c-4431-406e-8381-6cc2069dc860 (0) (canary)","index":1,"state":"finished","progress":100}
{"time":1527747089,"stage":"Updating instance","tags":["worker"],"total":3,"task":"worker/411628d6-4131-452b-9e86-0ee4547a9a7b (1)","index":2,"state":"started","progress":0}
{"time":1527747867,"stage":"Updating instance","tags":["worker"],"total":3,"task":"worker/411628d6-4131-452b-9e86-0ee4547a9a7b (1)","index":2,"state":"finished","progress":100}
{"time":1527747867,"stage":"Updating instance","tags":["worker"],"total":3,"task":"worker/acc08d9e-4cf1-46ba-8d01-af9b9aede81a (2)","index":3,"state":"started","progress":0}
{"time":1527748542,"stage":"Updating instance","tags":["worker"],"total":3,"task":"worker/acc08d9e-4cf1-46ba-8d01-af9b9aede81a (2)","index":3,"state":"finished","progress":100}
{"time":1527749743,"error":{"code":450001,"message":"Action Failed get_task: Task 53ccf286-ffde-4b38-7697-2170d37fa838 result: 1 of 3 post-deploy scripts failed. Failed Jobs: kubernetes-system-specs. Successful Jobs: kube-controller-manager, pks-nsx-t-resource-check."}}
', "result_output" = '', "context_id" = 'ae874da1-ce8b-445b-885f-57cab3636cfd' WHERE ("id" = 120)
D, [2018-05-31T06:55:44 #32661] [task:120] DEBUG -- DirectorJobRunner: (0.115586s) COMMIT
I, [2018-05-31T06:55:44 #32661] []  INFO -- DirectorJobRunner: Task took 1 hour 4 minutes 10.194163644000128 seconds to process.
Task 120 error
Capturing task '120' output:
Expected task '120' to succeed but state is 'error'
Exit code 1
root@server:/home/user#

Hi,
I don't think we can be much help on this issue anymore as this issue is in kubo 0.13.X and earlier. From 0.14.0 we have moved this from a post-deploy script to an errand as can be seen from this story

This will be fixed in a more up to date PKS version, we do not know which one. Pivotal support will be the best place to answer this.
Closing as fixed.

Thanks for the lead & quick response guys 👍


Differentiate AC/DC charging for BEV demand response

The BevDemand struct has changed slightly due to https://github.com/NREL/PowerSystems.jl/issues/162, so the algorithm to generate demand-response constraints needs revision.

I guess this is part of #277 and #182 but it is stale. We can re-open once those PR's are updated.


chore: add benchmarks

This adds scripts for running benchmarks.
It also adds a section with optional dependencies specifically for running benchmarks. You can install these using:
pip install --editable '.[benchmarks]'

@hackeryarn only one request. Add yourself to the Authors file 😄 ... ran locally, looks great.

Good call @cgdeboer updated.


Allow double clicking the file name to automatically focus the document

Please add functionality where double clicking the file in the left window (regardless whether it comes from an extension or not) to automatically fix the cursor back into the document.
My setup includes java extensions + vim keybinds, and it would be beneficial to be able to focus back from the PROJECTS view back to the document being editted

Screenshot of the issue observed

the above screenshot shows the window in question open on the left

on double clicking the file in question on the left, the focus for the vim navigation remains in the window, rather than notifying the main window that it should grab focus
further behaviour is displayed below

further expected behaviour is observed only when left clicking in the main area

I am not sure which extensions are necessarily causing this issue due to installing them in bulk, one of them is vscodevim - vim

the other extensions that might be the source of hte issue are debugger for java, extension pack for java, or maven for java

@Tyriar may I get a status update on triage of this issue?

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!


Option to print variables one per line

gon output currently has no newlines in it, which is compact but can be hard to read. For usability it would be helpful to have an option that would format the gon

Hey! Do you mean like pretty-print it in html? When I debug gon output I just use developer console because it provides you beautiful way to interact with json objects (you can just write window.gon and after that you can work with whole object using mouse).

Do you mean like pretty-print it in html?

Yes exactly, so the block of JS inside the <script> tag is readable with one variable per line.


Add a specific config for the update command

This is related to docker/docker#19104.

This is a proposal for #18957, to reduce what we send to the update endpoint. This also make it clear what is mutable in the container, and untie it from Config/HostConfig. It is still easy to add more attributes
This allows use to control more what is or is not mutable in a container and remove the use of the internal HostConfig struct to be used 🐳.

/cc @calavera @tiborvass
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

LGTM

LGTM


this.$ doesn't work inside dom-if but this.$$(selector) does

Description
this.$ doesn't work inside dom-if but this.$$(selector) does
Live Demo
https://github.com/johnlim/todo-list/tree/iron-query-media-bug
Steps to Reproduce

Clone the repo
Check out the branch iron-media-query-bug
Run the app using gulp serve
Type into the paper-input
From the console output, it can be seen that this.$ does not select paper-input but this.$$() does.

Expected Results
this.$ should work
Actual Results
this.$ doesn't select the element but this.$$() does
Browsers Affected

[* ] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari 9
[ ] Safari 8
[ ] IE 11

Versions

Polymer: v1.4.0
webcomponents: v0.7.21

Dupe of https://github.com/Polymer/polymer/issues/642


No explaination of multiple Classes - CSS Markers Step 16

Describe the Issue
So I looked up how to do it, so I don’t need help with the issue, but as far as I can tell, there’s no way to solve Step 16 of the CSS Markers lessons without using outside sources.
It tells you to add a second class to the div, but at no point up to that lesson have you ever done that, nor is there any indication that what you actually do is add it to the first class with simply a space. The error message is also incredibly unhelpful in that regard.
Any time we’ve done multiples of things, it’s been with commas, or adding a second one, so presumably someone would just either add another class variable and fail, or try with a comma and fail.
the screenshot shows an example of how this could be both confusing and frustrating, because i have both the classes in the div, and have been given no explanation of why it doesn’t work:

I am really enjoying the new style of lessons, and i can’t wait for the rest of the lessons to catch up, and i was just hoping pointing this out could help, or at least be a way for someone to show me where there was this concept covered before this lesson.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-css-colors-by-building-a-set-of-colored-markers/step-16
Steps to Reproduce
Simply do
the error message is unhelpful when the concept of multiple classes hasn't been explained yet.
Recommended fix or suggestions
Rewording the request (i.e. 'Replace the class "one" with "marker one"') or add a hint in the error message (i.e. "To use multiple classes, they are seperated by a whitespace)
Screenshots
No response

@bellhuffstutler Thank you for opening this.
I should have looked first before telling you to open an issue for this as there is already an issue open for it. That is my bad, sorry. I will close this as a duplicate of https://github.com/freeCodeCamp/freeCodeCamp/issues/46097
But again, do feel free to open issues if you spot any other problems. Just check the issues first to make sure it isn't a duplicate. I realize it can be a little difficult sometimes, try doing a search first.

I will keep that in mind thanks!


[Indigo] [Component] Add error states to all BP components.

Description
Add error states to all BP components so we can prompt users if an input value is invalid.
Components Checklist

[ ] BPTextInput
[ ] BPDomainSelector
[ ] BPDatePicker
[ ] BPSeveritySelector

All changes related to this issue should go into branch indigo-107-error-states.


[BUG] Containerd needs bumped to v1.6.x in rke2

https://github.com/rancher/rke2/issues/2541
Copied from the above issue:
Describe the bug:
We try to run a pod on windows using an image which has visual studio installed. The visual studio installation comes with filenames that contain unicode characters. This makes it impossible to pull those images with the containerd version provided through rke2.
The bug lies with the containerd version and is fixed in 1.6 as described here: https://github.com/containerd/containerd/issues/6612 and fixed here https://github.com/containerd/containerd/pull/6588
Please upgrade the containerd version shipped with rke2 to 1.6
Steps To Reproduce:

Installed RKE2 via the Rancher Registration Command on controlplane and worker nodes
Created pod on windows node using an image as described here: https://github.com/containerd/containerd/issues/6612
Pull fails and the pod is in ImagePullBackOff

https://github.com/rancher/rke2/pull/2869

https://github.com/rancher/rke2/pull/2869


Bicep Keeps reconfiguring/redeploying resources

Bicep version
Bicep CLI version 0.4.1272 (a69022dd2c)
Describe the bug
We are creating Azure Web APP and frontdoor using Bicep.
Resources are successfully created.
But When We re-run the az deployment with "what-if" We can see that bicep wants to reconfigure a bunch of parameters in the Web APP (That are already configured) and Bicep wants to delete properties IDs as shown below

Any insight about why Bicep keeps re-updating the resources?
To Reproduce
every-time We run az deployment create/what-if We see that bicep wants to update the resources
Additional context
Add any other context about the problem here.

If you have not changed your code, then most likely this is a false positive and there are no changes actually being applied. You can open what-if noise issues in the dedicated what-if repo.
Closing, but feel free to continue the discussion here.


[docs] Demo LoadingButtonsTransition crashes

[ ] I have searched for similar issues in this repository and believe that this is not a duplicate.

Steps to Reproduce

Visit https://mui.com/material-ui/react-button/
??
demo LoadingButtonsTransition crashes

Your Environment

Tech
Version

MUI
v5.10.13

Netlify deploy
https://6369ac6f407fd00008c7a092--material-ui-docs.netlify.app

Browser
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

Could you please provide more information? Did it crash on load, or have you interacted with it? Was there an error in the console?


Replace Six

Hi there,
Please can you replace:
from django.utils.six import python_2_unicode_compatible
With:
from six import python_2_unicode_compatible
So that this repo will be Py3 compatiable? Seems to work fine but might be worth you testing it properly as Im only using for testing a new project and only need very specific parts of it

Dropped Python 2 compatibility with https://github.com/CarliJoy/django-pint/pull/19


[COG-171] Add Apache AGE as a graph solution

From SyncLinear.com | COG-171

hey! qq—would yall be interesting in adding edgeDB support? Any ideas for how much work that would be? I can try and take a crack at it, have been super excited about it recently (syntax feels more intuitive than neo4j, built on postgres, (ie: pgvector support + fixed enforcable schema), and 5.0 added native RAG support as well.


New release

Could we get a new release?
The breaking changes in FlowStacks don't allow building version 0.10.0 of TCACoordinators unless we add it as an explicit dependency and pin it to version 0.4.0
Thanks

Thanks @machorro - sorry, I'd forgotten to push the 0.10.1 tag. That version pins FlowStacks to <0.6.0, so hopefully it should prevent the issue.


Use block indent for tuple pattern

This PR reuses rewrite_call_inner when rewriting tuple type to use block indent.

Thank you!


Dashed Polyline

Hi. I want to draw dashed polyline. For this reason i write following code. (as @monsieurtanuki  suggested )
Polyline finishLine = new Polyline(map);
finishLine.setPoints(list2);
finishLine.getPaint().setColor(Color.RED);
finishLine.getPaint().setStyle(Paint.Style.STROKE);
finishLine.getPaint().setPathEffect(new DashPathEffect(new float[]{10, 20}, 0));
map.getOverlays().add(finishLine);
map.invalidate();
But it draws ordinary line, not dashed. So what can do ?
Thanks for attention

Seems to be a known Android bug as they say in SO.
Try to use a simple canvas.drawLine with the same Paint: it shouldn't work either.
We use drawLine for Polyline: you need to turn the hardware acceleration off, which should be something like that:
mMapView.setLayerType(View.LAYER_TYPE_SOFTWARE, null);

Do you mean to extend PolyLine 's draw method ?

No, I mean just try to draw a line on a Canvas with that Paint, regardless of the map or of a polyline, just to check that the dash style won't appear because it's an Android bug and not because it's an osmdroid polyline. Allegedly.

Ok. i believe. But how about drawing dash line on Mapview ? Is'nt there  any other option ?

@fariz-siracli From 6.1.0 you can create a polyline that uses Path: public Polyline(final MapView pMapView, final boolean pUsePath).
Hopefully the Path version will correctly display the Paint. Can you please check that?


SMS being received many no. of times even when sent once

1. SDK version（SDK 版本）
{
}

2. In what kind of operation problems appear, and how to reproduce the problem ?（什么样的操作步骤问题会出现，是否是稳定复现，如何复现问题？）
{
I have this in my event dispatch .
case API_EVENT_ID_SMS_RECEIVED:
Trace(2, "received message");
break;
Even when i send SMS once API_EVENT_ID_SMS_RECEIVED occurs many no. of times. Not getting why?

}

Please check your SMS storage.
It may be full. You need to clear the storage.


Debounce/set interval to syncing in collaborative mode

If you start drawing diagrams and do frequent rotations / resizing/ moving shapes, it leads to at least 8-10 seconds and even goes to 15-20 seconds lag. Also, cursor sync takes good amount of bandwidth.
I tried adding debounce of around 30ms and it takes way less bandwidth compared to current state and I didn't notice any lag as well.
should we try that out?
Any other thoughts on optimizing?

A duplicate of https://github.com/excalidraw/excalidraw/issues/1310 (?) --- but we can rename this issue and track it as "add debounce to syncing".
The worry about adding debounce is convergence issues. Native debounce drops intermediate updates, which will often be significant. We'd need to implement update batching & merging, which is non-trivial.

Hmm, so to start with I was trying the below optimizations.

Debounce mouse events
Instead of calling broadcastScene from componentDidUpdate, I created a setInterval and started calling broadcastScene with an acceptable interval (tried with 30ms)

If needed I can push this to branch so the team can try it and we can then decide if this looks fine and then as you said I can pick batching and merging,

I created a setInterval and started calling broadcastScene with an acceptable interval (tried with 30ms)

Not sure if I understand, but adding a setInterval doesn't sound like a good idea. I'd just set up a debounce-like handler as you suggested.
But for broadcastScene you'd really need to come up with a queue & merging scheme in order to be accepted I'm afraid.
I personally am not against it, but you'll probably get pushback unless it's implemented in a way that 1) guarantees synchronization convergence (and without introducing some crazy complexity on top), and 2) doesn't deteriorate UX for people who aren't already suffering from the lag as you and me are -- which seems to be most people in the US.

Sure I will look into queuing and merging schemes for broadcast scene. For pointer debounce actually helps and takes way less bandwidth now

Come to think of it, since we're syncing whole scene, there shouldn't really be any convergence issues. Would need to review.
Also, my brain failed again --- instead of debounce, shouldn't we use throttle? Will need to check your mouse PR to see how it behaves with debounce.

Hmm now that I think of throttle might be better so that once in every 30ms for sure the sync happens instead of waiting for 30ms after mouse movements stop.
Also since whole scene gets updated as you mentioned, I think throttling the broadcast scene will also help, I will try that too.
In the meanwhile, you can check once the mouse movements with debounce but I agree throttle will be better here.

I don't think that blindly adding a debounce/throttle is the right approach. The fact that we get real time events is a feature, it makes the collaboration feel real time and is making the experience better. Most of the time it's actually working fine for me.
I don't believe that blindly adding a debounce/throttle is the right thing to do here. Some of the next steps we could do:

Your profile says that you live in Bangalore, India. The server is in the US. So one thing we could do is to start having more than one server and use one close to where the users are.

Right now, we're sending the entire scene on every update. We know that this is suboptimal. Making it send only the delta would be better. @petehunt has ideas on how to make that happen.

What is happening in this case is that the upload bandwidth is smaller than what we're trying to send, so it serializes all the sends, hence the lag (I assume, we'd need to figure if it's actually the real reason). We could avoid blindingly send all the updates but instead send an update, while it's sending, put everything in a queue, wait for the ack, and drop all the messages but the last one that we were going to send and send it.

@vjeux some updates might get missed when throttling the broadcast scene and sending the delta as you suggested would be great. but for mouse events, I think we should add throttle, what are cons you see. in that?

If we're able to see the mouse updating real time at 60fps (which has been my experience with the current collaboration mode), why would we artificially make it worse?

I get your concern @vjeux, my only concern is syncing the cursors is taking a good amount of bandwidth so to reduce the traffic I suggested if we can add throttle/debounce with some expectable duration.

@ad1992 can you be more specific? What kind of bandwidth are we talking about here. And what is the consequence, are you worried about metered internet plans?

@vjeux the frequency at which the data is getting transferred(i am checking the web socket in chrome console), is very high since its real-time which might actually start impacting user experience (slowness in collaborative mode). This was observed when testing with 3-4 users and the experience improved when turning off the cursor sync.
So I was looking for some optimizations when syncing cursor. And I am not saying to sync every x ms, instead throttle/debounce the handlers itself is what I meant as in the pr, so there won't be any data missing in sync.
As for the lag of scene, the update is mostly observed when too much of activity is done continuously example rotation shapes very fast (unreal scenario)

My idea is to throttle at 16ms (to target 60FPS), but we'd need to first ascertain that we're already sending updates more frequently than that.
We could also batch mouse updates with scene updates.
But as I mentioned, all this is adding complexity. Also note that in the long-term, we're planning to move to sending deltas only (not whole scene), which will improve the perf. And when we do so, any naive throttling we'd be doing (as part of this issue/PR) would need to either be reverted, or improved to ensure we merge those deltas.

16ms is the refresh rate of the screen and browsers don't send more than one event per frame, so this would not achieve anything more than introducing an artificial delay.

Oh, I didn't know 60FPS is a hard limit. In that case, never mind. But, there is a way for browsers to execute multiple tasks in a single frame, no? E.g., when you schedule several tasks via requestAnimationFrame, they'll tend to be executed in the same frame (either at the end of current frame, or at the start of next frame) --- not that it's much relevant to what we're solving here.

Just as a headsup: I've just been looking at adding a throttle for pointermove as I was seeing 300 mouse updates per second. It appears that there is a bug in Chrome where there are more pointer updates sent than the render step when you open dev tools. I was obviously using devtools to test! I couldn't work out why one collaborator was slow and the other was really fast!
https://bugs.chromium.org/p/chromium/issues/detail?id=992954

Interesting catch!


Formatting Message Text in a Deeplink

Let's say I want to send a list of links to a user as part of the message - how can we make sure that Teams will render it as a hyperlink.
For example - if my draft deeplink draft message has https://microsoft.com - that is not being rendered by the text editor as a hyperlink. This causes pain for our customers who have to copy and paste that link.
msft alias: @ralingin

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 45541337-ecd7-5cf6-cbe4-3f0d2f39aa79
Version Independent ID: 6b4203f0-2844-06c9-eaa3-9cc03e6f76c0
Content: Create deep links - Teams
Content Source: msteams-platform/concepts/build-and-test/deep-links.md
Product: msteams
GitHub Login: @laujan
Microsoft Alias: lajanuar

@rlingineni , Are you talking about deep link or sending a normal link to the user in draft message? sending link to user in draft message create hyperlink too. Please take a look at below screenshot:

Hey @Trinetra-MSFT , thanks for getting back. Apologies for not being clear.
Where this fails is with multiple links. Note that the first link doesn't render. If I was sending a user a list of bugs, they are unable to access them. They have to copy and paste each link individually.

A second question is also if rich formatting is supported (e.g. can I bold some part of the deeplink message)

We can't reproduce this issue at our end. Could you please try to send multiple links like this?
. Please help us to know your which teams client version you are running on.

Please re-open if you are still facing the issue.


Editor crashes when saving collision shape

Godot version
4.0.dev (391633760b0ea292af079287faf79c1aee6d9254)
System information
Windows 10
Issue description
Editor crashes after saving a ConvexPolygonShape2D as a new resource

from there it correctly pops the "Save Resource As..." dialog, and the file is saved. However the editor crashes. Upon reopening the project, the created resource is not set to the Shape property of the CollisionShape2D Node.
This is not 100% reliable, I think. I noticed two cases:

Sometimes, in the "Save Resource As..." dialog the preset for the filename is "myscene.tres", in which case upon saving the resource (even with a different name) the editor crashes.
Sometimes, in that dialog the preset for the filename is "new_convex_polygon_shape_2d.tres", in which case the resource will save correctly and the editor will keep working normally.

For other shapes (CapsuleShape2D and so on) I only ever managed to get the second case. I'm not sure what the discriminating factor is in falling in the first case.
Steps to reproduce
See above
Minimal reproduction project
Test.zip

I can't reproduce it in 603de7a0557cdbdd5405e345b55901f506cc5b40 on Linux. I tried several combinations of the actions described, and none causes a crash.

This is not 100% reliable, I think. I noticed two cases:

Sometimes, in the "Save Resource As..." dialog the preset for the filename is "myscene.tres", in which case upon saving the resource (even with a different name) the editor crashes.
Sometimes, in that dialog the preset for the filename is "new_convex_polygon_shape_2d.tres", in which case the resource will save correctly and the editor will keep working normally.

This depends on the action order, if you create the shape, then save it, the second case happens. Instead, if you create the shape, save the scene with Ctrl+S, then you save the shape, the first case happens.


Feedback: Provide Visio Diagram Download for Reference

Hey Team!  Is it possible to provide a public download link of the AVD Architecture Visio Diagram in this page for AVD Enterprise at Scale?  Thanks!

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 60ebd567-bf69-afa9-625e-38eb81dccfba
Version Independent ID: ef4ee644-1df3-433b-b11e-cb32dc58bad1
Content: Enterprise-scale support for Azure Virtual Desktop - Cloud Adoption Framework
Content Source: docs/scenarios/wvd/enterprise-scale-landing-zone.md
Service: cloud-adoption-framework
Sub-service: scenario
GitHub Login: @wahidsaleemi
Microsoft Alias: tozimmergren

Thank you for reporting this, @brmcmill. Great catch!
I'll start investigating the missing Visio download internally and get back with an update here once I have more clarity.

#please-close
https://github.com/MicrosoftDocs/cloud-adoption-framework-pr/pull/4535


Account Provisioning Customizations and Global/Account Customizations Concurrency Question/Bug?

Terraform Version & Prov: 1.1.9
AFT Version: 1.3.6
Terraform Version & Provider Versions
Please provide the outputs of terraform version and terraform providers from within your AFT environment
terraform version
1.1.9

terraform providers
aws 4.13.0

Bug Description
When updating accounts with a new custom_field, AFT invoked the aft-provisioning-customizations step function immediately for each account, and each of the global/account provisioning customization pipelines were invoked for each respective account at the same time provisioning customizations was running.
To Reproduce
Steps to reproduce the behavior:

Update multiple accounts with a new/modified custom_field
Watch the aft-provisioning-customizations step function get invoked once for each modification.
Watch each global/account customization pipeline get invoked at the same time as the corresponding run for aft-provisioning-customizations.

Expected behavior
My expectation is that global/account pipelines would run after the aft-provisioning-customizations step function.
Related Logs
Provide any related logs or error messages to help explain your problem.

Additional context
Add any other context about the problem here.

@SizZiKe when you update custom fields, this will eventually invoke the aft-account-provisioning-framework step function for each account, which in one of its steps invokes the aft-account-provisioning-customizations steps function for each respective account, and in another step creates the <acc-id>-customizations-pipeline for respective account if not already present. It is an expected behavior that the aft-account-provisioning-framework step function executions could be invoked in parallel for the AFT managed accounts, these are not set up to run serially for each account.
The <acc-id>-customizations-pipeline which apply the global and account level customizations are not invoked automatically, these need to be invoked separately by you via aft-invoke-customizations step function targeting respective managed accounts as per your deployment strategy.
Please can you confirm if this is the behavior you are seeing in your environment? <acc-id>-customizations-pipeline should not be invoked automatically ideally.


Adds the ChemMaster 4000

Everything a chemist needs to make pills and bottles. Also, adds pills and bottles. Patches will come at some point in a future PR.
Pill reagents do get added to the stomach, but I'm unsure if any reagents actually do anything when metabolized yet.
I didn't map it in yet because I didn't want to create conflicts with disposals mapping.

I dunno what to do about this:
##[error]GameObjects/Components/Chemistry/ChemMaster/SharedChemMasterComponent.cs(71,20): error CS8618: Non-nullable field 'id' is uninitialized. Consider declaring the field as nullable. [/home/runner/work/space-station-14/space-station-14/Content.Shared/Content.Shared.csproj]

Build finally passes.

Improved the UI:


The engine needs to be able to better create ActionListener events from private classes

Can we make this receive a function pointer delegate of some sort and just parameterize the class?

Not needed, this is being done much better now with SignalEvent


Add "Geospatial" category to Cargo.toml

https://github.com/rust-lang/crates.io/commit/9b65b4c004c503cf234c503e82d8575ba42c45e2
https://doc.rust-lang.org/cargo/reference/manifest.html#the-categories-field

Thanks for the issue! Closed in https://github.com/georust/kml/commit/b53faee9c5c4a4b742ce7f693a580c9dc7ec0962


fix(modify): bug in modify for graphql

Summary:
Resolved an issue where the @modify directive was not functioning correctly with the field's @graphql directive. The query sent by Tailcall to the original GraphQL server was incorrect.
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have performed a self-review of my code.
[x] PR follows the naming convention of <type>(<optional scope>): <title>

@MedHeikelBouzayene  You need to push the generated snapshots also.
steps

cargo insta test
cargo insta review
verify the snapshots and commit them to github

I did add the snapshots, could you approve workflows please.


[Chore|SDE|Helm|1.0.0] Helm charts update for AppV 2.3.0

Description
Fixed
#23  Postgres version aligned to v15.
#22 Default pass word removed from values.yaml
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@almadigabor Could you please Review it and merge PR  ?
@sachinargade123  Please check and review it.

Also please take a look at the failed helm test workflow.

Also please take a look at the failed helm test workflow.

Images hasn't been created that why it is failing.


Use kickoff_all and complete_all

Fixes #328
This changes the kickoff/complete to kickoff_all/complete_all where relevant. This cannot be merged until bluesky 1.13.0a4 has been released as the stubs are not present in the previous release.
It will fail all CI until the release has been made, but all CI passes locally when run against Bluesky main.

Close PR as stale. Will leave issue.


NullReferenceException when loading skeletal animation

This file is loaded by every other app just fine, and passes validation, but throws the below error in UnityGLTF: altspace-cube - Copy.zip
NullReferenceException: Object reference not set to an instance of an object
UnityGLTF.GLTFSceneImporter+<SetupBones>d__61.MoveNext () (at <a63ed9cb9b854f709fa6f4b9577efac1>:0)
UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at C:/buildslave/unity/build/Runtime/Export/Coroutines.cs:17)

I don't have time to track this down right now. Any ideas?

Im having a siilar issue with a simple skinned mesh exported from blender -- any ideas?

I am also still having this issue

me too

I was having this issue with a GLB model exported with the built-in exporter in Cinema 4D. I worked around the issue by exporting the model as FBX instead, and then using https://github.com/facebookincubator/FBX2glTF to convert the FBX to a GLB, which then worked well with UnityGLTF.

thank you @InnoLuke for the tip. unfortunately, I cannot use it in this form. Since I develop for Android. Are there no other possibilities? For me, it is important to fix this problem. Thanks a lot!

@julia1981  I just used siccity gltf ladder, a lot simpler and actually works

@yaakovyitzchak Thank you very much, unfortunately you cannot export at runtime. 😪

Oh brutal, that is correct lol.. I guess someone needs to add it some way

Fixed in latest release


[DRAFT] feature: BREAKING monorepo and CLI

Initial commit for setting up the monorepo and CLI

Testing steps:

Clone
yarn install from root of repo
cd packages/cli
./bin/dev new


New build

This PR will

Downgrades node-fetch to a CommonJS compatible version
Provide a new build (fixes #37)

@joltcoke Thanks for your pull request!


editor screen tooltip bug

What does this PR?

Fixes the app crash caused by usePopover hook provided by react-native-modal-popover
changed tooltip implementation to custom controls instead of hooks and methods provided by the module
fixes the keyboard causing tooltip disaligment in editor screen.

Steps to reproduce
Uninstall and reinstall the app or clear app data to see tooltip at first app start.
Go to editor screen and tooltip will load after Draft button is rendered.
Screenshots/Video
https://user-images.githubusercontent.com/48380998/155351999-311ed617-cb19-423e-9eff-346bb903abda.mp4

@aliseyalvi in the video, the tooltip is missing an arrow, it was there before... is that intentional or unavoidable..?

@aliseyalvi in the video, the tooltip is missing an arrow, it was there before... is that intentional or unavoidable..?

didn't changed the styles of the tooltip. I am unable to get it back.

@aliseyalvi @feruzm we should be good now... only issue now is, often times the arrow is not positioned exact, it's an issue with package itself as it also affect leaderboard tooltip as well.

https://user-images.githubusercontent.com/6298342/155605680-aee4d417-beca-499e-ba9f-ef2c25218e9a.mov
https://user-images.githubusercontent.com/6298342/155606305-c4a36961-acf7-4d38-b51d-1933e0defa67.mov
May be we should create an issue on their github repo regarding this issue.


Add fp16 testing to conversions and bruteforce

Merge the fp16-staging branch into main, adding fp16 (half) testing to the conversions and math bruteforce tests.

As we don't seem to have any remaining issues or concerns with the new fp16 conversions and math bruteforce tests, now would be a good time to merge the staging branch into the main branch.  Any further issues with the new tests we can address on main as part of normal CTS maintenance.
Most of this work has already been reviewed in other pull requests; I've structured this PR into a merge commit that merges the already-reviewed fp16-staging branch, followed by some small "fixup" commits.

Need to check if any .csv files need to be updated to account for these new tests.

The opencl_conformance_tests_*.csv files always list the entire bruteforce and conversions binaries without specifying subtests, so I believe that there's nothing to do for those files.
test_conformance/spir/khr.csv does list individual tests, but it would probably need corresponding SPIR files first.  (That's the old SPIR, not SPIR-V.)