Persian language file

Persian translation, revision 9, update 1

Thank you really much. I appreciate your work.
You can add the language directly to the database in data/data.sqlite with the language tool... So it will be compiled into the next version. Or at least make a new folder for additional languages and put it in there.

Hi! Im going to make sure all translation is accurate (again), then ill do it!
On 10/2/16, RocketRider<EMAIL_ADDRESS>wrote:

Thank you really much. I appreciate your work.
You can add the language directly to the database in data/data.sqlite with
the language tool... So it will be compiled into the next version. Or at
least make a new folder for additional languages and put it in there.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/RocketRider/GreenForce-Player/pull/1#issuecomment-250973280

merged


Doing Getting Started tutorial corrupted my WSL

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
Update: Apparently it's configuration issue(?). Since I've done created a new Debian installation and it went fine. I don't know what went wrong with my first config.
I'm on Window 10, WSL2 Debian 12.
I was going through Getting Started tutorial section.
I installed podman with the default configuration.
After I ran cross run --target aarch64-unknown-linux-gnu, it crashes my WSL and literally corrupted it.
Here's the terminal log:
# I was on zsh shell
❯ cross run --target aarch64-unknown-linux-gnu
info: downloading component 'rust-std' for 'aarch64-unknown-linux-gnu'
info: installing component 'rust-std' for 'aarch64-unknown-linux-gnu'
 31.6 MiB /  31.6 MiB (100 %)  13.3 MiB/s in  2s ETA:  0s
WARN[0000] "/" is not a shared mount, this could cause issues or missing mounts with rootless containers
Trying to pull ghcr.io/cross-rs/aarch64-unknown-linux-gnu:0.2.5...
Getting image source signatures
Copying blob 9cccf86b8f43 done
Copying blob fb15d46c38dc done
Copying blob b51569e7c507 done
Copying blob da8ef40b9eca done
Copying blob 9d5962c83f5f done
Copying blob 58690f9b18fc done
Copying blob 4c6d73517e75 done
Copying blob 4afe128e6862 done
Copying blob 2765f54cfdee done
Copying blob 40c841a9d0e8 done
Copying blob 70c492706cd4 done
Copying blob b376264cc3c9 done
Copying blob f94a42110e99 done
Copying blob 29835156cc05 done
Copying blob d48b139772fe done
Copying blob 55ba4d0a0c25 done
Copying blob 5f4fa2c62d4d done
Copying blob 6bc43a1e4611 done
ERRO[0069] While recovering from a failure (creating a read-only layer), error deleting layer "6a8295f44097b968ae2a6944b429e06ca1538788b6575efb7616cbaae039ef20": unlinkat /home/peach/.local/share/containers/storage/vfs/dir/6a8295f44097b968ae2a6944b429e06ca1538788b6575efb7616cbaae039ef20: read-only file system
fatal error: unexpected signal during runtime execution
[signal SIGBUS: bus error code=0x2 addr=0x1ace0c0 pc=0x40de6e]

runtime stack:
fatal error: unexpected signal during runtime execution
panic during panic
[signal SIGBUS: bus error code=0x2 addr=0x1bd002c pc=0x462a57]

runtime stack:
fatal error: unexpected signal during runtime execution
stack trace unavailable
Error:
   0: could not execute `rustup component list --toolchain stable-x86_64-unknown-linux-gnu`
   1: Input/output error (os error 5)
PS C:\Users\Peach> debian # cannot access debian
<3>WSL (5619) ERROR: ConfigUpdateLanguage:2950: fopen(/etc/default/locale) failed 5
<3>WSL (5619) ERROR: CreateProcessEntryCommon:526: initgroups failed 5
<3>WSL (5619) ERROR: CreateProcessEntryCommon:586: Create process not expected to return
PS C:\Users\Peach>

What target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[X] Windows
[X] Linux / BSD
[X] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[ ] docker
[X] podman
[ ] other container engine (specify in description)

cross version
cross 0.2.5
Example
Following Getting Started tutorial on Windows 10, WSL 2 Debian 12.
cargo install cross
sudo apt-get -y install podman
cargo init --bin hello
cd hello
cross run --target aarch64-unknown-linux-gnu

And bye bye my Debian.
Anyways, the Debian is not that important.
I was just testing around.
Additional information / notes
I'm on zsh shell with some long configurations.
podman uses default configuration.
I have changed target-dir for cargo.

Update:
I've done a wsl --unregister debian.
and got a new, fresh, and hot Debian.
I've done:
Installed Rust first through this default installer and proceed default installation.
sudo apt-get -y update; sudo apt-get -y upgrade
sudo apt-get -y install curl
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
source "$HOME/.cargo/env"

and then something along these lines:
sudo apt-get -y install podman build-essential
cargo install cross

then test the thing
cargo init --bin hello
cd hello
cross run --target aarch64-unknown-linux-gnu

And it has been working just fine!
I don't know what happen in the first configuration I've got.

Cross doesnt do anything magical with WSL, it simply invokes podman or docker.
You can see what happens with -v added to the command.
I don't think this is a cross issue, it should go to wsl I think.


nested route not render

Version
4.0.12
Reproduction link
codesandbox.io
Steps to reproduce
Mobile 1 router-link use named route to navigation to Mobile component
Mobile 2 router-link use literal string  to navigation to Mobile component
in router.js file, the Mobile route has property children, and there are a route with path: '', name: 'First'
What is expected?
After click Mobile 1 and Moblie 2, the url is matched,  First.vue will be rendered inside  Moblie's router-view.
What is actually happening?
By literal string router-link, First.vue will be rendered inside Moblie's router-view.
By named route router-link, First.vue will not be rendered inside Mobile's router-view

This is working as expected and is documented

This is working as expected and is documented
I don't understand what your mean, is it right that it will  not be rendered inside router-view with named route router-link way?


⚠ Site ANTS has degraded performance

In c89d1e2, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 8974 ms

Resolved: Site ANTS performance has improved in 7ba144c after 52 minutes.


Updating gulp example in readme

Fixes a couple issues brought up in #8, I've also added style and processor options as they're required for _sprite.scss to actually generate.

Coverage remained the same at 100.0% when pulling 1ce70721f29bd91d0c5ae0ba43341101269d5dc0 on loremipson:patch-1 into d656abddeb73c5259d818fe4c386217f905352c2 on sprity:master.

Readme was updated.


fixed typos reported by lintian

While creating a Debian package for oor, lintian complained about some typing errors.

Thanks for your pull request. It is really appreciated :-)


Add Orientation support for FluentLayout

Pull Request
📖 Description
FluentLayout is flex column.  This PR adds the ability to have this flex row or flex column

🎫 Issues
No found.

👩💻 Reviewer Notes
The default stays the same as the current.  So this won't be a breaking change.

📑 Test Plan
Added Buint tests for FluentLayout.

✅ Checklist
General

[x] I have added tests for my changes.
[x] I have tested my changes.
[x] I have updated the project documentation to reflect my changes.
[x] I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

[ ] I have added a new component
[x] I have added Unit Tests for my new compontent
[x] I have modified an existing component
[x] I have validated the Unit Tests for an existing component

⏭ Next Steps

Done and added BUnit tests also.

What is the goal of this new Orientation attribute? Could you add a screenshot of the two cases to explain?

If you have fixed full width header on a page you would likely want flex column.

If you have a fixed sidebar on a page you would likely want flex row.

Mmmm. OK. This could be solved very easily with a style, but why not add this attribute. Thanks.


tests fail in dbuild context (sbt.internal.inc.InvalidComponent)

I get a bunch of messages like "sbt.internal.inc.InvalidComponent: The compiler bridge sources org.scala-sbt:compiler-bridge_2.12:1.1.0-dbuildxbf579d40cbffdff1fd1e72ea5565b14e328a9c02
:compile could not be retrieved"
looks like some version number logic is confused by dbuild's mangled version numbers
I will work around it for now by disabling the zincIvyIntegration tests in the community build
full log at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/2548/consoleFull

I have trouble seeing where the issue is. Can you elaborate a little bit @SethTisue ? Is this something we must fix in our build, is this a bug caused by sbt or is this caused by the scalaHome and other specific changes that you do in dbuild?

I really don't know, couldn't even begin to guess.

Oh, I get what's happening now. Yeah, it looks like this is a problem in our build, and dbuild's version is causing the build not to publish the bridges to the correct place.

This has change with the new refactoring in the build, so it shouldn't be an issue. If it is, please reopen.

@jvican same errors

Where can I modify the code use for zinc? The build should run publishBridges before running tests

trying that out over at https://github.com/scala/community-builds/pull/778

Unlikely to ever progress. If testing Zinc against Scala nightlies is desired, I'd suggest doing that in Zinc's own CI.


MacVim bookmark error

MacVim: Version 8.0.502 (129)
NERDTree: 5.0.0
After making a bookmark of a node I get this error when I am trying to open the bookmark...
Error detected while processing function nerdtree#ui_glue#openBookmark[2]..87:
line    2:
E121: Undefined variable: nerdtree
E116: Invalid arguments for function 86
E15: Invalid expression: bookmark.getNode(nerdtree, a:searchFromAbsoluteRoot)

Hi, @deltaskelta. Thanks for bringing this to our attention.
This looks like a bug that should have surfaced quite some time ago. I have a fix for you to try...
From 953fa16ffe14cc38c9f558043ca4b238a71d1fda Mon Sep 17 00:00:00 2001
From: Jason Franklin<EMAIL_ADDRESS>Date: Fri, 2 Jun 2017 19:49:51 -0400
Subject: [PATCH] Add a missing function argument sigil

An error message from issue #677 hinted that an argument sigil was
missing in a function in the "bookmark.vim" script. It is unknown why
this bug did not surface until now, but this commit puts the simple fix
in place.

Fixes #677.
---
 lib/nerdtree/bookmark.vim | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/nerdtree/bookmark.vim b/lib/nerdtree/bookmark.vim
index ad8c3d1..e9479ac 100644
--- a/lib/nerdtree/bookmark.vim
+++ b/lib/nerdtree/bookmark.vim
@@ -163,7 +163,7 @@ endfunction
 " treenode for it.
 function! s:Bookmark.GetNodeForName(name, searchFromAbsoluteRoot, nerdtree)
     let bookmark = s:Bookmark.BookmarkFor(a:name)
-    return bookmark.getNode(nerdtree, a:searchFromAbsoluteRoot)
+    return bookmark.getNode(a:nerdtree, a:searchFromAbsoluteRoot)
 endfunction

 " FUNCTION: Bookmark.GetSelected() {{{1
--
2.7.4

Apply the above patch to your local NERDTree repository (since the change is small, you could just do it manually).  If it works for you, I'll submit a pull request to @PhilRunninger to make the change public.

you know, I tried to go through the bookmark process again and it works without failing. I am not sure why this happened before, maybe it was the older version of MacVim that did this. I am now on 8.0.596 and it works without the patch. Thanks for the help!
...Closing

Hey, @deltaskelta. This issue should actually not be closed.
I was able to identify and isolate the issue you were having. I can easily replicate the behaviour now. I don't have time to do everything I want right away, and, since this bug isn't critical, I'll likely wait until this weekend to submit a pull request.
Could you reopen?
@PhilRunninger, could you reopen this if he doesn't see it before you? It's an easy fix... and the patch above would do the magic.  However, I'd prefer to wait a bit and include a few more commits to clean up some related code that has grown a tad stale. I'll have more to say about the exact nature of the bug in my PR. Does that sound okay?

Sounds good. I'm curious to learn how to replicate the error.

Hey guys, details for the fix can be found in pull request #703. Thanks for bringing this up, @deltaskelta.


task sorting options

Would it be possible to have the option to sort tasks by the page name they are on?
For example, I keep my tasks on the day they are due. If I could sort the tasks in the checklist plugin by the page they are on they would always be in chronological order. Because we only have the option to sort by date modified, adding a new task to a page in the future makes it either the first or last on the list.

You can see the dates are out of order because I've been updating tasks.
The sort dropdown could be old -> new, new -> old, page a -> z, page z -> a
Thanks very much!

I have a task on my list to add support for due dates on tasks. I'm thinking of a syntax something like
- [ ] Some task [>02/10/2021]

And you would have an option to sort tasks by when they are due. Then you can still keep the tasks in context of where you created them. Would this solution work for you?

Not really - I have my tasks on the date they belong to already, so I'd have to go back through and add this new date format to each of those tasks.
Also, would we have to have the [[02-10-2021]] and [>02/10/2021] on the same line if we wanted the task to also show up in the backlinks of the target page?

Added new sorting options in latest release


Ug update with scoping on persons

Codecov Report

Merging #196 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #196   +/-   ##
=========================================
  Coverage     59.68%   59.68%
  Complexity      815      815
=========================================
  Files           131      131
  Lines          3031     3031
  Branches        407      407
=========================================
  Hits           1809     1809
  Misses         1115     1115
  Partials        107      107

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/seedu/address/logic/LogicManager.java
45.45% <ø> (ø)
3.00 <0.00> (ø)

...eedu/address/logic/parser/MainCatalogueParser.java
65.51% <ø> (ø)
29.00 <0.00> (ø)

src/main/java/seedu/address/model/Status.java
100.00% <100.00%> (ø)
1.00 <0.00> (ø)

Continue to review full report at Codecov.

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


confluent-platform: 7.0.1 -> 7.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/confluent-platform/versions.
meta.description for confluent-platform is: "Confluent event streaming platform based on Apache Kafka"
meta.homepage for confluent-platform is: "https://www.confluent.io/"
meta.changelog for confluent-platform is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-rest-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-verifiable-consumer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-console-producer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-reassign-partitions-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-replica-verification had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-delegation-tokens had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.zookeeper-shell-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-server-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-rest-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-leader-election had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-protobuf-console-producer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/schema-registry-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-preferred-replica-election-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/replicator had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-server-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.trogdor-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-features-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-rest-stop-service-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-acls had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-console-consumer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.connect-mirror-maker-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-remove-brokers had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-mirrors-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-set-acls had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-consumer-perf-test-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.confluent-rebalancer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.schema-registry-stop-service-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-mqtt-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-configs had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/confluent-rebalancer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-dump-log had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.replicator-verifier-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-api-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-consumer-groups-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/zookeeper-security-migration had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-preferred-replica-election had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.security-plugins-run-class-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.sr-acl-cli-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-topics-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/zookeeper-server-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-consumer-groups had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-broker-api-versions had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/zookeeper-shell had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-streams-application-reset-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-console-consumer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-storage-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-acls-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-delete-records-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-cluster-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-delegation-tokens-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-get-offsets had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-set-acls-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/confluent had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/replicator-verifier had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/cluster-information-migration-script had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.zookeeper-server-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-delete-records had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-mirror-maker had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.confluent-hub-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-console-consumer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-server-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-reset-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-console-consumer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-replica-status-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-cluster-links-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.schema-registry-run-class-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-run-class-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-dump-log-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-test-runner had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-mirror-maker-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-mqtt-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-add-brokers-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-3_0_0-reset-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/schema-registry-stop-service had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-server-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-avro-console-producer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-log-dirs had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-remove-brokers-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.schema-registry-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-rebalance-cluster-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/connect-mirror-maker had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-configs-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.schema-registry-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-metadata-shell-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-leader-exclusion-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-migrations-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-json-schema-console-consumer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-restore-command-topic had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-3_0_1-reset had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/schema-exporter had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.connect-distributed-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-protobuf-console-producer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-server-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-replica-verification-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-storage had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-reassign-partitions had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-add-brokers had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-json-schema-console-consumer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-verifiable-consumer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/connect-distributed had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-rest-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.zookeeper-server-stop-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-3_0_1-reset-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-cluster-links had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-replica-status had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/schema-registry-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-3_0_0-reset had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-mqtt-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/confluent-hub had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-replica-exclusions-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-mirrors had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-rest-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-producer-perf-test had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-avro-console-consumer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-server-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/trogdor had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.schema-exporter-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-leader-exclusion had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-cleanup had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-migrations had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-server-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-api-start-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/sr-acl-cli had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-json-schema-console-producer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-avro-console-producer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-datagen had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-transactions-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-consumer-perf-test had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-datagen-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-transactions had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-export had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-verifiable-producer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-export-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-producer-perf-test-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-protobuf-console-consumer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-features had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-metadata-shell had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-print-metrics-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-mqtt-run-class-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-get-offsets-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-cluster had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-mqtt-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-rest-stop-service had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-run-class-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/schema-registry-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-streams-application-reset had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/connect-standalone had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.connect-standalone-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-avro-console-consumer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-console-producer had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-print-metrics had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-log-dirs-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.replicator-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.confluent-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-leader-election-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.zookeeper-security-migration-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-restore-command-topic-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-topics had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/control-center-reset had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.ksql-test-runner-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-replica-exclusions had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-protobuf-console-consumer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-mqtt-start had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-rebalance-cluster had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-broker-api-versions-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.cluster-information-migration-script-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/zookeeper-server-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.control-center-cleanup-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-json-schema-console-producer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-server-stop had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-verifiable-producer-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/ksql-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-rest-run-class-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/security-plugins-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/kafka-rest-run-class had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0/bin/.kafka-run-class-wrapped had a zero exit code or showed the expected version
0 of 186 passed binary check by having a zero exit code.
0 of 186 passed binary check by having the new version present in output.
found 7.1.0 with grep in /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0
found 7.1.0 in filename of file in /nix/store/w492faln2d5nbc8q1r5sm1q9j9nfnjhd-confluent-platform-7.1.0

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
confluent-platform

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

confluent-platform

Maintainer pings
cc @zoedsoupe for testing.

 1 package built:

confluent-platform

 zookeeper running

 kafka broker running
![image](https://user-images.githubusercontent.com/44469426/163691419-1d5d3fde-4e91-4c9f-8075-4a6e135c7373.png)


Can't import public repo

Describe the bug
Cannot destructure property 'appFiles' of 'project' as it is null.
Link to the Bolt URL that caused the error
https://bolt.new/~/github.com/liquity/bold
Steps to reproduce
Go to https://bolt.new/~/github.com/liquity/bold
Expected behavior
Expected to see the front-end of this decentralised application
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 128
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 89572564,
  "usedJSHeapSize": 88467488,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = Knickend
Chat ID = 85a934f0fda6

Additional context
Error:
An unknown error occured while running an action.

Also facing this issue, any pointers?


Initial code from raygun-apm

This is the initial set of commits taken from raygun-apm. It should require effectively no review, since it's all code that's already landed in raygun-apm.

Thanks :)

Thanks :)


[Snyk] Security upgrade danger-slather from 0.0.6 to 0.0.6

Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

Gemfile.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

661/1000  Why? Recently disclosed, Has a fix available, CVSS 7.5
XML External Entity (XXE) Injection SNYK-RUBY-NOKOGIRI-1726792
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Code coverage
Total coverage: 95.14%

Powered by Slather

  Generated by :no_entry_sign: Danger


Miniscule performance impact (if any) by constantly setting DeathRattle hediff to 0.00f every second

In order to prevent a pawn from dying from a DeathRattle hediff we need to constantly set that hediff to 0.00f severity. This means running a script every 60 ticks (about a second) to do just that. Whilst this is absolutely not a big problem at all (most mods do this far more often) it's still nice and better to be more efficient and optimised.
In some rare cases this can probably cause issues on players PC's if their setup is weak OR if they've got a significant amount of mods on - and I mean significant, probably 100+.
In more common cases - if a player places a lot of life-support machines and IV drips and all of them are active then their performance could be negatively impacted. Once again this isn't that large of a problem because it'd require all of those machines to be running scripts at once which wouldn't be the case if A) No pawn is nearby or B) If no pawn meets the requirements for the script to run (e.g if they've got a heart/lungs/kidneys/liver/etc...)
Some solutions to this would be finding a way to force set the hediff to 0.00f without having to require constant updates. Another would be stopping the hediff from ticking up altogether by using a Harmony patch to check whether the pawn has life-support and, if they do, to stop the vanilla Rimworld function from running that'd otherwise increase the severity of the Coma/No Pulse/Asphyxiation hediff(s).

Is there a way to affect the death rattle hediff by setting some sort of hediff progression chance/rate instead of having to constantly assign it to 0.00?

hediff progression chance/rate instead of having to constantly assign it to 0.00?
Yeah, that was solution 2.0:
to stop the vanilla Rimworld function from running that'd otherwise increase the severity of the Coma/No Pulse/Asphyxiation hediff(s).
However that'd likely not improve the bug that much given that it'd essentially be running at the same rate as the script would. Fortunately, like I said, this is almost so negligible that the chances we ever see this affecting anything is very slim but, if this is one of the only issues left on the "Issues" page then we could absolutely use that to patch it up and see some improvement, however minuscule.


Move all components to this repository

Proposal
Move all Arctic Sea components (Jan Mayen, Faroe, Shetland, Svalbard, Iceland) to this repository, give them a common prefix for the groupId (e.g. org.n52.arcticsea) and a common version number (maybe starting at 1.0.0). Due to dependency convergence we'll currently have to rerelease all components with updated dependencies anyway if e.g. Jan Mayen gets a new release.
Benefits

Easier release workflow
Easier changes across projects
Easier handling of dependencies
Easier usage (i.e. common versioning scheme)

Todo

[ ] Migrate all open issues from  Jan Mayen
[ ] Migrate all open issues from Faroe
[ ] Migrate all open issues from  Shetland
[ ] Migrate all open issues from  Svalbard
[ ] Migrate all open issues from Iceland
[ ] Move source code of Jan Mayen in subdirectory called janmayen
[ ] Move source code of Faroe in subdirectory called faroe
[ ] Move source code of Shetland in subdirectory called shetland
[ ] Move source code of Svalbard in subdirectory called svalbard
[ ] Move source code of Iceland in subdirectory called iceland
[ ] Create a parent pom.xml using the component's pom.xml

<groupId>org.n52.arcticsea</groupId>
<artifactId>arctic-sea</artifactId>
<version>1.0.0-SNAPSHOT</version>

[ ] Update the component's pom.xml to use the new parent, change the groupId to org.n52.arcticsea.$component, e.g.:

<groupId>org.n52.arcticsea.iceland</groupId>
<artifactId>iceland</artifactId>
<version>1.0.0-SNAPSHOT</version>

<groupId>org.n52.arcticsea.faroe</groupId>
<artifactId>faroe-annotations</artifactId>
<version>1.0.0-SNAPSHOT</version>

[ ] Create the initial release
[ ] Update depending components (SOS, WPS, Importer, ...)
[ ] Clear Jan Mayen and create a simple README referencing this repository
[ ] Clear Faroe and create a simple README referencing this repository
[ ] Clear Shetland  and create a simple README referencing this repository
[ ] Clear Svalbard and create a simple README referencing this repository
[ ] Clear  Iceland and create a simple README referencing this repository
[ ] Make sure Travis CI is working

Questions/To Discuss/To Check

[ ] What versioning scheme to use? Start at 1.0.0?
[ ] Use org.n52.arcticsea as groupId for all modules?
[ ] Are there any feature branches that are not yet merged?

I think we should start with version 52. We should do this for all software we'll release at 52North ;).
To be serious: I am fine with 1.0.0

Want about the package names? I'd say, they should stay the same, shouldn't they? I mean, moving all under arcticsea would require all dependent coffee to recompile

Versioning: I would like starting at 1.0.0
GroupId:  I would like to have all under the same groupId arctic-sea because all these modules are part of the arctic sea.
Open branches:  /EHJ-52n/svalbard/tree/feature/coding-required-for-data-import

GroupId: I would like to have all under the same groupId arctic-sea because all these modules are part of the arctic sea.

I don't think the groupId can contain hyphens...

Open branches: /EHJ-52n/svalbard/tree/feature/coding-required-for-data-import

Is there already a PR for that?

Open branches: /EHJ-52n/svalbard/tree/feature/coding-required-for-data-import

Is there already a PR for that?

created one just now: 52North/svalbard#8

GroupId: I would like to have all under the same groupId arctic-sea because all these modules are part of the arctic sea.

I don't think the groupId can contain hyphens...

arcticsea is okay for me, too.
Specifications: Apache Maven → [Java Naming Specification](https://docs.oracle.com/javase/specs/jls/se6/html/packages.html#7.7]

Okay, as I have no idea how to sell the a newer 1.0.0 release to Ann, I'll propose to go with 3.0.0, as Iceland with the highest version number is at 2.0.0...

I agree with you to go on with 3.0.0  and a common prefix for all.


Add options to disable hyper pod-internal services

Add options to kube-proxy and kubelet for disabling hyper pod-internal services

Depends on https://github.com/hyperhq/hyper/issues/214


Equality of UIint8Array

Is your feature request related to a problem? Please describe. A clear and
concise description of what the problem is. Ex. I'm always frustrated when [...]
UIint8Array

:tada: This issue has been resolved in version 1.4.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Handle JSON encoded events

This pull request

refactors event handling, decoding and encoding
implementing applications can define their own transcoders
includes the flow-stages branch refactoring event consumption into a flow-pipeline
loosen coupling to internal sevenmind usage

Still Todo

fix failing tests
refactor test-support like mockbus
reap dead code
fix dialyzer specs

Resolves #25

Ebert has finished reviewing this Pull Request and has found:

22 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

10 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

12 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

13 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

14 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

15 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

17 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.

Ebert has finished reviewing this Pull Request and has found:

14 possible new issues (including those that may have been commented here).
2 fixed issues! 🎉

You can see more details about this review at https://ebertapp.io/github/sevenmind/kaufmann_ex/pulls/34.


line icon for natural=coastline

Also the line style should be something other than a thin green line.

will handle this with #1475


build(pmp-api): bundle api with pkg

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/valueadd-poland/pimp-my-pr/blob/master/CONTRIBUTING.md#git-guidelines
[x] Tests for the changes have been added (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Locally I noticed that the API image has the size of 1GB
Issue Number: N/A
What is the new behavior?
Locally the API image has the size of 260MB
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
We can choose a different way to achieve a smaller bundle size (#231). We need to check the result of this question

Choosing #231 because cluster mode doesn't work with pkg

https://github.com/zeit/pkg/issues/438


Airdrop tokens from the contract are not entered into my wallet

Hello, I'm sorry, I transferred the Telegram friend airdrop tokens to my wallet, the transaction was completed, but no tokens have entered my wallet.  I have been waiting for several days now.
Contract address:
UQAQNRGOloVrc8_kTz_ya116k5ZU0mI1XV-xOPPucxJKC1qY

Hello, I'm sorry, I transferred the Telegram friend airdrop tokens to my wallet, the transaction was completed, but no tokens have entered my wallet. I have been waiting for several days now. Contract address:
UQAQNRGOloVrc8_kTz_ya116k5ZU0mI1XV-xOPPucxJKC1qY

Sorry for the inconvenience this might have caused, error is probably caused by cloud data glitch and can be fixed.  For the fastest resolution, please click on the link below to our dedicated support line:
Support: Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation

Hello, I'm sorry, I transferred the Telegram friend airdrop tokens to my wallet, the transaction was completed, but no tokens have entered my wallet. I have been waiting for several days now. Contract address:
UQAQNRGOloVrc8_kTz_ya116k5ZU0mI1XV-xOPPucxJKC1qY

Sorry for the inconvenience this might have caused, error is probably caused by cloud data glitch and can be fixed. For the fastest resolution, please click on the link below to our dedicated support line:
Support: Help Center
Note: Click on the live chat icon at the bottom corner of the page to start a conversation

Sorry, I lost contact with the support and they don't answer me, it's been several days now that I'm waiting for the tokens to arrive in my wallet, please help me.

Sorry, I lost contact with the support and they don't answer me, it's been several days now that I'm waiting for the tokens to arrive in my wallet, please help me.

Sorry, once again, I connected to the Ton Keeper wallet via airdrop and made a transaction, and the transaction fee was deducted, but the tokens were still not transferred to my wallet, please solve my problem as soon as possible.  thank you

My new contract
UQClVtNNnmcqdgyWk_Qbv1-OWD_X5crFIaD1p-rw1W0HZ1_z


French language support

This update helps to handle new languages and facilitates the import of new words

Word fetching from text files
Supports new keyboard layouts
Change language from the interface
New word list (French)

Hi @yanngodeau! This is great 🙂 It seems like your indenting has been applied on all the files, making the diff a bit hard to read, would it be possible to fix the indenting?

Merci!
Very nice, thanks for this :)


Make the font color same with icon

Can you please add a setting for make the font color same with the color of diferent type of icon

Can be achieved with get_data function

please little bit more about that


Native module cannot be null.

Environment
React Native Version: *0.50.0
React Native Google Analytics Bridge: ^5.8.0
Platform: iOS
Steps to Reproduce
yarn add react-native-google-analytics-bridge
react-native link react-native-google-analytics-bridge

I try to use the library as suggested in the docs.
Expected Behavior
The app would boot with the ability to send events and screen hits to Google Analytics.
Actual Behavior
The app fails to load with the following error:

Code sample/demo project
This occurs once I insert the line:
import { GoogleAnalyticsTracker } from 'react-native-google-analytics-bridge'
Thanks for your help!

Update- this issue is resolved when downgrading to version 5.7.1. Not sure what the diff is there but just a note!

@masiamj I ran into a similar problem and realized I just needed to rebuild after I first linked the library. Maybe you rebuilt at some point while downgrading?

I'm getting this error as well with 5.8.0.

Get the same

@cbrevik Any ideas? this is on latest version on a new project

No I am not able to reproduce that, there has to be something else here. If I do the following, the test app works fine for me:
react-native init nativeModuleNull
cd nativeModuleNull/
yarn add react-native-google-analytics-bridge
react-native link react-native-google-analytics-bridge\n
echo "import { GoogleAnalyticsTracker } from 'react-native-google-analytics-bridge'" >> App.js
react-native run-ios


Store owned address in OscAddress

A little lifetime oversight of mine: The OscAddress needs to store the address as a string otherwise it doesn't own it, thus the string passed to new must live at least as long as the OscAddress 😄

I agree. Thanks for reviewing and merging!


Improved fuzzy matching with warning

Added test cases to the fuzzy version of get_event_by_name and reimplemented some logic to avoid false positive warnings.
I recommend considering using RapidFuzz over thefuzz since it seems to be more widely adopted and actively maintained. The performance difference is not important for our use case. The API is identical so this only requires changing the requirements. I will put it in a separate PR if you like the idea.

I recommend considering using RapidFuzz over thefuzz since it seems to be more widely adopted and actively maintained. The performance difference is not important for our use case. The API is identical so this only requires changing the requirements. I will put it in a separate PR if you like the idea.

I'm fine with switching to rapidfuzz if the (apparently minor) API differences aren't relevant here.

Also, the test failure on 3.8 minimum versions is completely unrelated. That's a CI problem. I'm fixed that just now. If you want, you can rebase onto master. But it's not really necessary, I think.

I'm fine with switching to rapidfuzz if the (apparently minor) API differences aren't relevant here.

I will PR for that once this is merged

Test failures are caused by the changes here. The reference_laps_data fixture that is defined in conftest.py now returns data for a different event.
Somehow fastf1.get_session(2020, 'Italy', 'R') now returns the "Eifel Grand Prix". I probably shouldn't have used "Italy" as identifier in a season with three Italian grand prix. But the result should at least be one of those three.
The desired result in the fixture is the "Italian Grand Prix" (Round 8). We can switch to an explicit get_session(2020, 8, 'R') there. But the matching problem still needs to be fixed.

That's super old. Italy should be 100% matched to all the Italian races that season and we tiebreak between those. I'll look into why we get a German race instead.

I see the EventSchedule dataframe's index doesn't start at 0, probably to accommodate testing.
This is inside the fuzzy_match function
print(self.iloc[[0, 1]])

Output:
RoundNumber  Country   Location                                  OfficialEventName  EventDate            EventName   EventFormat  ...    Session4               Session4Date     Session4DateUtc Session5               Session5Date     Session5DateUtc F1ApiSupport
2            1  Austria  Spielberg  FORMULA 1 ROLEX GROSSER PREIS VON ÖSTERREICH 2020 2020-07-05  Austrian Grand Prix  conventional  ...  Qualifying  2020-07-04 15:00:00+02:00 2020-07-04 13:00:00     Race  2020-07-05 15:10:00+02:00 2020-07-05 13:10:00         True
3            2  Austria  Spielberg  FORMULA 1 PIRELLI GROSSER PREIS DER STEIERMARK... 2020-07-12   Styrian Grand Prix  conventional  ...  Qualifying  2020-07-11 15:00:00+02:00 2020-07-11 13:00:00     Race  2020-07-12 15:10:00+02:00 2020-07-12 13:10:00         True

Is this expected?

I see the EventSchedule dataframe's index doesn't start at 0, probably to accommodate testing.

This isn't to "accommodate" testing. But it is an artifact of the fact that testing exists in the schedule. include_testing=False filters the testing events out, but slicing in Pandas doesn't reindex the DataFrame. So the index starts at a non-zero value then.
I thought a bit about whether this behaviour is desired, or whether .get_event_schedule should explicitly reindex the DataFrame before returning it. There certainly are arguments for both sides. But I think in terms of compatibility of the data with itself and for consistency within FastF1, filtering out the data and retaining the original index is better. For example, the  .pick_* methods on Laps don't reindex the data either. Additionally, this would potentially be a breaking change for some users. Therefore, I don't think we really want to change that behaviour.
If you don't have any further objections, I'll merge.

No more changes needed on my front. Please merge if it looks good to you

Great, this is overall a pretty nice improvement 👍

I will open another one to switch the fuzzing library


Add code to reverse the class mapping

We need to add code that takes the mapping produced by #29 and reverses the class to k-mer mapping. This is part of #22 and should go in reverseClassMapping.

Closed by #66.


Support null: false columns with a default.

I don't mean to be a pest, but #591 is still an issue in master for me. I'm opening a new PR with some failing tests this time, and hopefully a better error report.
Consider this model:
create table(:clients, primary_key: false) do
  add :id, :uuid, primary_key: true, default: fragment("uuid_generate_v4()")
  add :name, :string, null: false
  add :url, :string, null: false
  add :secret, :uuid, null: false, default: fragment("uuid_generate_v4()")
  timestamps
end

schema "clients"  do
  field :name, :string
  field :url, :string
  field :secret, Ecto.UUID, read_after_writes: true
  timestamps
end

When specifying both null: false and a default value, you are effectively prevented from using the database default at all:
changeset = Client.changeset(%Client{}, %{name: "local", url: "http://localhost:4200"})
Repo.insert(changeset)
# => ** (Postgrex.Error) ERROR (not_null_violation): null value in column "secret" violates not-null constraint

I had the impression that #591 was about defaults, but my context was wrong. This appears to only be an issue when columns have both a default and a null: false.

Thanks for the report. I don't like discarding nil values because you may have a default in the database and you may want to override it with nil. The only option I have in mind right now is to allow setting a field as read_only, which means it is never written to, so we never send anything to the database. Or maybe we can incorporate this behaviour on read after writes.
This is a tricky issue, thanks for persisting here. :)

What if we treated explicitly provided nil attributes differently than those that weren't provided at all?
Client.changeset(%Client{}, %{name: "local", secret: nil, url: "http://localhost:4200"})
|> Repo.insert

In something like this, we are explicitly providing secret: nil, so it would make sense to pass this on to the database and essentially disregard the database default.
Client.changeset(%Client{}, %{name: "local", url: "http://localhost:4200"})
|> Repo.insert

But in this case, secret: nil is implied, not given. I think it would make sense to strip out secret: nil here, and let the database decide what to put in that column.

@joshwlewis this is a nice direction. The only complication is that we support default values in the schema too. In your example, if someone does:
field :secret, :string, default: "foo"

Should we send it to the database because it was explicitly set? Even though nothing came in the changeset? And what if someone does this:
field :secret, :string, default: "foo"

We have some different features and they are at odds with each other here. Another concern about your solution is how we would make it work for document stores. In them, we don't have default values and, if we send just what was given, we would have an inaccurate description of the document.
In any case, your problem has a solution today, albeit verbose. You can define a before_insert callback that will receive the changeset and simply remove the change from there:
before_insert :remove_secret
def remove_secret(changeset) do
  Ecto.Changeset.delete_change(changeset, :secret)
end

I think even this may work:
before_insert Ecto.Changeset, :delete_change, [:secret]

The idea is that a read_only option would just simplify this.

Ok, we have decided to fix by supporting something similar to your patch, except we only discard nil read_after_writes values (instead of any nil value). This gives the opposite behaviour of what we had before. Before read_after_writes were always included but most certainly had to be deleted with delete_change. Now they are always excluded but you can force them with force_change.
Thanks for persisting on this and the other reports, we really appreciate it. :heart:

Awesome. That's more in line with what I would have expected from read_after_writes. Thanks for the quick turn-around. You guys are doing great work.


Progress Visualization for clean UX experience

For a user, who visits the website (initial loads on a fresh device), certain UI elements take a while to populate.
Example:

Login, the profile image takes a couple of seconds to appear on the navbar
The map aside takes a couple of seconds to populate and displays "No Superblocks"
Challenges views at times take a second to render.

Although these happen seamlessly from the next interaction with the elements. Hence we might as well think of having some form of progress to present the blocking nature of the UI.

Excellent idea!

@raisedadead 👌

Challenges views at times take a second to render.

@raisedadead Can you clarify this? Initial page load is done server side so there shouldn't be any delay in the page rendering.

Challenges views at times take a second to render.

Sure, when we were testing this in the beta, the challenge transitions were not smooth. Any challenge, if they were loading the first time used to take 1 second or so to load.
Steps were:

Visit a challenge from the map.
Solve, click submit.
Next challenge loads (<--- with some delay).

I am not sure if this is the case anymore. I haven't seen any delays even for the map on my local setup, however, if the beta is still up with the latest deploy, I could check if this is still reproducible.

@raisedadead I see. That seems to be different issue then this one here. That might be an actual bug as there isn't any reason why the next challenge should see a delay.

@BerkeleyTrue yup. I agree. We could just keep this aside unless something comes up.
Yes, the only loading delay is currently:

Login, the profile image takes a couple of seconds to appear on the navbar

Following on from #11611
I have just used console.time to confirm what you said by putting .delay(15000) after .retry(3).
I'll see if I can track down the block.

I'd still like to see some interface preview for codemirror, something similar to what FaceBook use to do.
http://www.callumhart.com/blog/non-blocking-uis-with-interface-previews

Wow! That's such an excellent read. Thanks for the share Berkeley.


Cannot use pgml.activate_venv() to set environment for parallel workers.

Currently, pgml provides a UDF called pgml.activate_venv()^1. However, when a query requires parallel workers, the venv environment cannot be set for parallel workers. This is not very easy to reproduce but parallel queries are not rare in PostgreSQL. Probably we can remove this UDF since we've already had the GUC parameter 'pgml.venv'^2 to control the venv path.
Steps to reproduce:

The package xgboost exists in my venv environment.

Remove the IMMUTABLE qualifier from pgml.validate_python_dependencies, so that this UDF can be execute on parallel workers multiple times.
diff --git a/pgml-extension/src/api.rs b/pgml-extension/src/api.rs
index ad952e48..440df23d 100644
--- a/pgml-extension/src/api.rs
+++ b/pgml-extension/src/api.rs
@@ -27,7 +27,7 @@ pub fn activate_venv(venv: &str) -> bool {
 }

 #[cfg(feature = "python")]
-#[pg_extern(immutable, parallel_safe)]
+#[pg_extern(parallel_safe)]
 pub fn validate_python_dependencies() -> bool {
     unwrap_or_error!(crate::bindings::python::validate_dependencies())
 }

Construct a query that involves parallel workers.
CREATE TABLE t1(i int);
INSERT INTO t1 VALUES(generate_series(1,500000));
INSERT INTO t1 VALUES(generate_series(1,500000));
INSERT INTO t1 VALUES(generate_series(1,500000));
INSERT INTO t1 VALUES(generate_series(1,500000));

pgml=# select pgml.activate_venv('/tmp/virtualenv');
activate_venv
---------------
 t
(1 row)

pgml=# explain (analyze) select count(pgml.validate_python_dependencies())
from t1;
INFO:  Python version: 3.11.5 (main, Sep  2 2023, 14:16:33) [GCC 13.2.1 20230801]
INFO:  Scikit-learn 1.3.0, XGBoost 2.0.1, LightGBM 4.1.0, NumPy 1.26.1
INFO:  Python version: 3.11.5 (main, Sep  2 2023, 14:16:33) [GCC 13.2.1 20230801]
ERROR:  The xgboost package is missing. Install it with `sudo pip3 install xgboost`
ModuleNotFoundError: No module named 'xgboost'
CONTEXT:  parallel worker

Is this related to #1146? Can we kill 2 birds with one stone?

Is this related to #1146? Can we kill 2 birds with one stone?

Probably no? #1146 is adding support for storing cache in a custom location. This issue states that the pgml.activate_venv() isn't implemented correctly that when there're queries involve parallel workers the UDF pgml.activate_venv() cannot setup venv for parallel workers.
One possible solution is removing the pgml.activate_venv() UDF and tell users to use the pgml.venv GUC parameter to set up the virtual environment.

I think it would be great if we can also remove pgml.activate_venv() in favor of setting pgml.venv at boot, since that covers our known use cases for venvs, without any runtime performance impact or complexity.

@montanalow Do we need to refactor the pgml.venv in PR#1146 or create another separate PR?

I think #1146 will remove the need to call pgml.activate_venv() all together. We'll leave that function as is for now, since dropping it would be a breaking API change, we'll need to wait for a major version bump.

pgml.activate_venv

Sorry, I didn't get it. activate_venv is for activating the Python's virtualenv. #1146 is for caching models from huggingface, right? Why #1146 removes the need to call pgml.activate_venv()?

@higuoxing I guess what he said is that we can keep pgml.activate_venv() as is for now. There is no need to remove the UDF now since it would be a breaking change.

Right, sorry, I confused comments between #1147 & #1146. #1146 establishes a better pattern for gathering env vars in _PG_init, rather than calling a function at runtime. To fix this issue #1147, I think we should adopt a similar approach that will set the Python venv at server start only, but we don't need to hold up #1146 for this additional fix. cc @levkk


Rules with square brackets not work

The rules [Nn]ginx-*.conf and !/[Nn]ginx-*.conf correctly work for git itself but IDEA 2016.1 tells me that the entry is never used.
I don't know whether the other regex rules are broken too.

Duplicate of #213 sorry.


pkg/prometheus: Remove rule ConfigMap migration

Remove Prometheus rule ConfigMap live migration code introduced in #1399
[1].
[1] https://github.com/coreos/prometheus-operator/pull/1399
I would like to remove the live migration with the next release. What do you think?

Was there a specific reason why this was removed? Is there a way to do it by some flag maybe in the newer versions?
I am planning to bump from 0.19 to the 0.25, should I follow 0.19=>0.20=>0.25?

There is still the command line tool to perform migrations available. It was mentioned in the release notes of the release that intoduced the Prometheus rule object.
We just removed the migration to keep the Prometheus operator start up less involved.


App stops/crashes when hitting the repeat button

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1908
Describe the bug
Hello,
I've discovered this wonderful app yesterday and it's already been a great help. However, I'm encountering a pretty big issue: after the first run finishes and the app clicks the repeat button, the play button on the bottom left disappears as soon as FGO gets to the support selection screen and my device tells me the FGA app stopped working and I need to close it.
This also happens if I select only one run, close the "FGA wrap up" window, and then click "repeat" myself. However, if I select one run and click "close" instead, the app keeps working and I just need to click play again when getting to the support selection screen. I've attempted it more than a dozen times, it never fails. This has been my work around but it's of course not ideal.
I initially thought it was an accessibility problem and I've tried everything related to that and more, still doesn't work.
I've attempted to record a video in debug mode but for some reason the app crashes even earlier. I think it's because skills for my servants don't work in debug mode for some reason. A video wouldn't tell you much I think anyway, since it obviously stops recording when the app stops. There are no warning signs whatsoever.
Thank you in advance for your help.
Video
Wouldn't help.
Device model
Samsung Galaxy Tab A7
Android version
12
Screen size
2000x1200
RAM
3GB

Update: FGA now randomly crashes during battle. Happens on second or third wave.
Forgot to mention disabling battery optimization was of course the first thing I did.

I'm thinking of memory issues.
Please check

Click on it and then on "Memory usage by app".
It should list the memory usage of all apps in the last 3 hours.

There you go

Ran one battle and it crashed after getting back to the support screen once again.

There's also another setting called "Running services", showing overall memory usage.
I'm interested in this part

Oops, realized it was set to display last day. Last three hours:

I should probably tell you I did try to uninstall Avast, rebooted, and still ran into the same issue. I attempted to change preferred servant to first instead of a friend but it still crashed going back to support selection.

Maybe it's actually a FGO issue? Been experiencing a bit of lag since the Christmas update while the game used to run super smoothly before then.

I can say that most users don't experience crashes.
Can't tell you why it does on your device.
Can't see anything obvious regarding memory.

I was hoping there was an obvious fix I somehow missed during all my researches and troubleshooting, but too bad.
Thanks anyway. All I can hope is that it will work once FGO fixes its current issues.


Uncaught exception on thread "WindowsNativeRunloopThread" (#21) java.lang.NoSuchMethodError:

Insert a clear and concise description of the issue you are experiencing.
Reproduction Steps
java -jar Beacon.jar
Expected Behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: [e.g. Windows]
Application Version: Native Bytecode Version: 60.0

Additional Context
Uncaught exception on thread "WindowsNativeRunloopThread" (#21)
java.lang.NoSuchMethodError:
at com.sun.glass.ui.win.WinApplication.staticScreen_getScreens(Native Method) ~[Beacon.jar:?]
at com.sun.glass.ui.Screen.initScreens(Screen.java:412) ~[Beacon.jar:?]
at com.sun.glass.ui.Application.lambda$run$1(Application.java:152) ~[Beacon.jar:?]
at com.sun.glass.ui.win.WinApplication._runLoop(Native Method) ~[Beacon.jar:?]
at com.sun.glass.ui.win.WinApplication.lambda$runLoop$3(WinApplication.java:174) ~[Beacon.jar:?]
at java.lang.Thread.run(Thread.java:831) [?:?]

yes thank you with java 17 its ok, but the gateway rejected the UPnP request


Detecting PayPal support

Hello.
I've faced an issue with PayPal support in the Facebook browser on mobile devices.
It would be great to have a helper method in PayPal module for detecting PayPal support in the current environment.
I think it's mutch better not to show PayPal among available payment methods in unsupported browsers instead of showing error when the user is trying to use it.

If you look at the example for the PayPal create call here, you'll see that there is a check for the error with the code PAYPAL_BROWSER_NOT_SUPPORTED. http://braintree.github.io/braintree-web/current/module-braintree-web_paypal.html#.create
That should let you update your UI appropriately. Going to close this now, but feel free to re-open it if this does not help you.

@crookedneighbor thank you. I saw that example and I have already implemented error handling. But I think that it would be better to have the ability to hide PayPal payment method at all if the PayPal integration is not supported in the current browser.
Why should we let the user click on PayPal button and then immediately display an error about the unsupported browser?
Especially for SPA, when the logic is encapsulated inside separated components it's not convenient to create braintree-client and paypal instance outside paypal component just for checking if we should display PayPal payment method.
Also, it looks like easy to expose the function for checking browser support as a static method of paypal module.

That sounds reasonable to me. Probably a synchronous method on braintree.paypal.isSupported that returns true or false.
We'll put this in our backlog, but if you'd like to PR it, feel free.

We've added a helper method for detecting this. It'll go out in the next release of braintree-web.

@crookedneighbor great news. Thanks a lot!

We've released 3.10.0 of braintree-web which includes paypal.isSupported(). Thanks for your feedback!

@lilaconlee great news! Thank you!

Hello. Is paypal.isSupported() true for iOS 10.3.2 on iPhones 7 and 7 Plus? It's working for me on older iPhones, but not the 7 and 7 plus I'm testing. Thanks!

Update from braintree: "Thanks for contacting Braintree support. I've been able to replicate this issue within a Facebook webview. I'm looping in our API support team, who will investigate this issue further and reach back out to you once they have more information.
Thanks,
Subi"


Request context and ingest fixes

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Chore (a change that does not modify the application functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Documentation updates are needed, and have been made accordingly.
[ ] I have added and/or updated tests to cover my changes.
[ ] All new and existing tests passed.
[ ] My changes include a database migration.

Just noting that this was partially implemented in #622


linuxPackages.openafs: Patch for Linux kernel 6.9, 6.10

Description of changes
Apply upstream patches from the openafs-stable-1_8_x branch to support Linux kernel 6.9, and from the master branch to support Linux 6.10.
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
[ ] 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.

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

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

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


About training with xformers

Dear authors,
Thank you for your excellent work and for open-sourcing it, I did learn a lot from your work. Currently, I am working on running the code with Xformer, but I've encountered an issue. It seems that after using unet.enable_xformers_memory_efficient_attention(), the unet.set_attn_processor(attn_procs) function doesn't work.
Could you please provide me with some guidance on how to resolve this issue? I appreciate your help, and I wish you a great day!
Sincerely,
Kevin

@KevinChen880723 you can just refer to https://github.com/huggingface/diffusers/blob/07b297e7dec3f475a880c15addcb6c02c0690992/src/diffusers/models/attention_processor.py#L886

@xiaohu2015 Thank you for the quick response! Wish you a nice day :)

@xiaohu2015 Thank you for the quick response! Wish you a nice day :)

I got the same problem, did you fix? Can you share the code to implement IPAdapterAttnProcessor2_0 using xformers? many thanks!


Update to include C# in databricks & like for like pricing

Databricks now supports C# https://github.com/dotnet/spark
Also is it possible to include a like for like pricing comparison for the different tools, this is a commonly raised point when choosing

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

ID: 957618b3-8d25-49c4-950c-0c044d68f443
Version Independent ID: 2ab67665-066b-fb14-9763-a12693b19bec
Content: Choosing a stream processing technology
Content Source: docs/data-guide/technology-choices/stream-processing.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @ZoinerTejada
Microsoft Alias: pnp

@joshmowork Thanks for the feedback! We are assigning this issue to the content author for review.

@joshmowork Thanks, I'll adding dotnet support to the table. Pricing comparison is a lot trickier, for example Stream Analytics is charged by SUs, whereas Databricks is charged by a combination of VM time + database units (DUs)


Live server isn't working!

Hey Ritwick, I'd installed it in my chrome and it didn't work. Something's wrong.

Can you clarify it with more details?

Like it's literally not doing what it's supposed to do. I'm making changes to the source code (HTML/CSS) and even though I save 'em, it won't reload them in the browser.

Is this only static items?

What you've entered in Actual Server address & Live Server address?

It works fine on VS Code. I was talking about the chrome extension you've built. Do you mind telling me how it works?

https://www.youtube.com/watch?v=54wcX1G2GH8
Here is a short tutorial.
(Yes, for only static file - this extension is not great.)

Tips: For only static files, the Actual address & Live server address will be same .

Does not work for me. I'm hosting my php file on wamp. so my address is like: http://localhost/test/debug.php. the page won't reload automatically. VSCode live server on port 5500 and using live server web extension on chrome.

This error happens to me if I start live server in the editor before I start the Apache server in XAMPP.

alt+L O =>   category icon view!
What should I do?

Hello, have you tried to follow the Setup.md. I also recommend that you to read The common misconception.
Have you installed the browser add-on?
Then if you choosing direct setup, you must visit your PHP server address. For instance. http://localhost/workspace

Live Server is not connecting to the browser since yesterday. Is it something that everyone have issue with?

New issue open here:
https://github.com/ritwickdey/vscode-live-server/issues/236

I was having this issue I uninstall vscode and chrome. Reinstalled them. Then ensured that my html page had the following minimal tags. It worked for me.
<html land="en">
<head>
    <script src="https://unpkg.com/vue"></script>
</head>
<body>
<div id="app">
    <h1> {{msg}} </h1>
</div>
<script>
    var app = new Vue({
        el: '#app'    ,
        data:{
            msg: "its working!"
        }
    });
</script>
</body>

</html>

Please help me, after clicking on go live, the browser gives error ie this page is not working along with <IP_ADDRESS> is not sending any data.
here is the screen shot

it was working fine up until yesterday but when i open live server on VSCode it does not open the html and it redirects it to this page, any help?

This might solve your issue :  https://stackoverflow.com/questions/61169067/live-server-vscode-this-page-isn-t-working-127-0-0-1-didn-t-send-any-data-err/61733333#61733333

please help me
No response from Go live button
extension ping is so high


[FR] Heading specific colors

I love all the outline-specific search options. Maybe a name change to enhanced outline 🤷♂
When I am scripting out longer files, I have categories or themes in mind that I would love to be able to color code in the outline.
Person A = red heading
Sceen 1 = blue heading
That sort of thing.
I am imagining a right-click option on the heading and then a color picker. Maybe some saved colors in the picker.
This would mimic the video editor timeline feel, which I love!
Thanks.
I look forward to hearing your thoughts 😁

It would be amazing if the outline could display colors that correspond to the custom colors' theme.


Add: multiplatform support

Change Log:

Add multiplatform support

Problem:

Solution:

Issue Tracking: #

need update action logic


Make the omega-edit client port configurable

This also fixes some items that could cause issues with packaging of the node script.
This is needed to be able to fix the issue at https://github.com/apache/daffodil-vscode/issues/271

@scholarsmate After this is merged I plan to make a 0.9.33 release

Thanks @Shanedell, looks good!


Merge b459efe0876951f8d82aebfa37fa5f5fa08755ef to dev

Please merge
b459efe0876951f8d82aebfa37fa5f5fa08755ef
and
6a816f2dc19040f6dcd00f2d7c777b298b7e547a
to the dev channel.
This fixes test errors due to the fact that Chrome updated to version 46 on our build and test bots.
This merges correctly, except that the last lines of html.status should be removed (a previously cherry-picked cl removed the lines, that this cl added).  Remove:
+
+[ $compiler == dart2js && $checked ]
+js_typed_interop_test/closure: RuntimeError # Issue 24608

Merged in version 1.13.0-dev.7.3
The real -dev.7.3, not -dev.7.2.