Increase vppagent attempts connecting to vpp

Signed-off-by: Artem Belov<EMAIL_ADDRESS>Description
Wait for vpp socket more than 3 seconds
Motivation and Context
#1922
How Has This Been Tested?

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[ ] Tested locally
[ ] Have not tested

Types of changes

[ ] 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 not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@artem-belov  issue are not with forwarder but with passthrough NSE. Please check it.


cache.py: item_ttl

This function is the same as the TTL  in redis.
If a key expires, it will be deleted and return -2.

Thanks for the PR submission! Would you be able to add tests for this new method?

Thanks for your suggestions! The tests have been added.

Thanks for making those changes and adding tests!
There were some lint errors (on master) with the latest mypy version, but I've fixed them. You'll need to rebase or merge with latest to get those fixes.

The tests that you added pass, but the 100% coverage check fails:
---------- coverage: platform darwin, python 3.11.0-final-0 ----------
Name                          Stmts   Miss  Cover   Missing
-----------------------------------------------------------
src/cacheout/__init__.py         10      0   100%
src/cacheout/cache.py           290      3    99%   462, 466-467
src/cacheout/fifo.py              3      0   100%
src/cacheout/lfu.py              39      0   100%
src/cacheout/lifo.py              5      0   100%
src/cacheout/lru.py              10      0   100%
src/cacheout/manager.py          46      0   100%
src/cacheout/memoization.py      22      0   100%
src/cacheout/mru.py               5      0   100%
src/cacheout/rr.py                9      0   100%
-----------------------------------------------------------
TOTAL                           439      3    99%

Just need to cover the cases:

where calling get_ttl() for a key without an expiration time returns None
when the key expiration is in the past where that key gets implicitly deleted

Coverage: 100.0%. Remained the same when pulling 1426ffac47e9f5e2a16fbf73ecf042d5ef0ce47c on uncle-lv:master into 3143da085360b8a77b3c4792c119b6c507717120 on dgilland:master.

The code has been formatted, and 100% test coverage.

Nice work!


Fix typo in README.md

This line should be "An Elixir library for working [with] Stripe."

Coverage remained the same at 13.406% when pulling 88e8a5edeccdec0b74082eeca949ebf872fabc50 on nicholaswyoung:patch-1 into dbd371ae22b9cbd4d4ed89be4b4cfe10a3137fe2 on robconery:master.


Add talon open debug

Command for opening debug window:

This command is beta-only. At one point we had discussed having a separate branch for the beta version, or perhaps a tag. What do others think?

We discussed this on the backlog session. We feel like because this is a low-impact feature, that it is fine to merge but should not be considered a precedent for further use of beta-only features in community.  Could you please add a comment that indicates that this functionality is beta-only? Thanks!


When loading a resource pack on first boot, CIT Resewn will occasionally mistake images for models

First boot is on the left, reloading will not change anything
Edit the model file in any way (including back to the way it was) and it will be the image on the right

items=minecraft:packed_ice
model=glacite_helmet
nbt.ExtraAttributes.id=GLACITE_HELMET

Resource Pack is Hypixel+

glacite_helmet.json fix for the helmet
{
	"parent": "item/hplus_helmet",
	"textures": {
		"0": "./glacite_helmet_armor",
		"1": "./glacite_helmet"
	},
    "display": {
        "head":{
            "rotation": [0, 0, 0],
			"translation": [0, 0, 0],
			"scale": [1, 1, 1]
        }
    }
}


Add wiki link to README

One problem here is that documentation lies at the very end of the README file, people might just stop reading after the usage section. I do recommend a more obvious note maybe in Prerequisites part.

Out of date


Rendor Error with Reanimated 2.4

First sorry for my bad english. With Reanimated 2.4 you get the error :

The issue is track here https://github.com/software-mansion/react-native-reanimated/issues/2766.
An esay fix is to change our function from bezier() to bezierFn() in anmiated-stroke.tsx and index.tsx
Hope it will help!

After changing to BezierFn(

)

Thanks for the report! Can you make a PR?

i tried to but i get this error :
ERROR: Permission to craftzdog/react-native-checkbox-reanimated.git denied to DenisFanteria.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I have my SSH key in my profile.
I don't understand this is my first PR

https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

Thanks for the help and your amazing videos 👍 PR send.
Sorry it's my first time sending a PR.

Thanks!

Hi @DenisFanteria can you please tell me which package versions you are using. I had the same issue with reanimated package and many other issues when looking for a version that will work for me. I am not able to use reanimated library with expo.

Hi @kokosky93 . Take a look at package.json.


opencv: Fix OpenCV build on non NixOS platform

Motivation for this change
Fixes #21994
I solve this issue by deleting this paragraph
To reproduce this issue, a distro which have libraries symlinked in /lib and /lib64 is needed. (i.e Arch Linux)
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Edit: I forgot to put opencv in title, now fixed.

cc maintainers @viric @mdaiter

Why does this fix build errors on non-NixOS systems?

Arch Linux have something like /lib64/libz.so in its filesystem, then these code add impure pathes to CMAKE_LIBRARY_PATH.
Because cmake tries to use those impure libraries, ld reports impure path `/lib64/libz.so' used in link, as reported in #21994 (Note that nix's ld have ability to detect impure library being linked)

@sifmelcara makes sense. You have my thumbs up.
:+1:


add conv_ai

Adding ConvAI dataset https://github.com/DeepPavlov/convai/tree/master/2017

This one will make @thomwolf reminisce ;)

Merging.


ansible-lint: 6.11.0 -> 6.12.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ansible/ansible-lint/releases.
meta.description for ansible-lint is: Best practices checker for Ansible
meta.homepage for ansible-lint is: https://github.com/ansible/ansible-lint
meta.changelog for ansible-lint is: https://github.com/ansible/ansible-lint/releases/tag/v6.12.1
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
found 6.12.1 with grep in /nix/store/icp85d5a2dfapza0xyij11jc1zgx719i-python3.10-ansible-lint-6.12.1
found 6.12.1 in filename of file in /nix/store/icp85d5a2dfapza0xyij11jc1zgx719i-python3.10-ansible-lint-6.12.1

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
ansible-lint
python310Packages.ansible-lint
python311Packages.ansible-lint

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/icp85d5a2dfapza0xyij11jc1zgx719i-python3.10-ansible-lint-6.12.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ansible-lint https://github.com/r-ryantm/nixpkgs/archive/887c2c0f6f361f69866ffcf64b8df9d82574b674.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/icp85d5a2dfapza0xyij11jc1zgx719i-python3.10-ansible-lint-6.12.1
ls -la /nix/store/icp85d5a2dfapza0xyij11jc1zgx719i-python3.10-ansible-lint-6.12.1/bin

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

1 package failed to build:

python311Packages.ansible-lint

1 package built:

ansible-lint (python310Packages.ansible-lint)

Maintainer pings
cc @sengaya for testing.

@ofborg build python311Packages.ansible-lint

@ofborg build python310Packages.ansible-lint


date_range overflow protection.

If the nanoseconds are greater than or equal to 2_000_000_000 it will cause a panic. So we just cap it to the maximum of 1_999_999_999.
Fixes #4

Thanks for the PR. :rocket:


Move Visual Studio Code from IDE to Text Editor

In README.md which written in English, Visual Studio Code is positioned at IDE list. At official FAQ, they mentioned as below:

Visual Studio Code is a streamlined code editor with support for development operations like debugging, task running, and version control.

So I think VSCode should be moved to text editor list.
And I also checked on Chinese version. At there, VSCode is positioned at right place. So I updated English version also.

NOTE: A similar PR may already be submitted! Please search among the Pull request before creating one.
Types of Changes
What types of changes does your PR introduce? Put an x in all boxes that apply

[ ] New addition to list
[ ] Fixing bug in existing item in list
[ ] Removing item from list
[x] Changing structure (organization) of list

Proposed Changes
Describe each of your changes here to communicate to the maintainers why we should accept this pull request.

If you're adding something to the list, be sure to explain why it should be added.
If you're fixing a bug or resolving a feature request, be sure to link to that issue.

PR Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING guide
[x] I have explained why this PR is important
[x] I have added necessary documentation (if appropriate)

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

@wormwlrm thx!


Switch to fastutil

fastutil offers fast collections that could speed up clustering algorithms. Its benefits should be investigated and in the future it could be switched to.

Not now.


Polish pass

Add optional display label for files (e.g. "HTML" and "JS" instead of the filename).
Add linear progress bar indicator for when preview is loading.
Automatically reload the preview when an editor is changed (with 500ms debounce).
Make main layout consistently 70%/30%.
Various other styling tweaks to make layout more stable.
Use a resize observer to tell CodeMirror when its parent size changes, because it manages its scrollbars with JavaScript.
Add some CSS Shadow Parts to allow for more style customization.

I actually like the preview toolbar because it both makes the alignment of the main areas consistent, and gives a place to show the filename. We may very well want to allow transitions in some demos.
If you look at the React editable samples, they have a toolbar with just the static text "RESULT", probably to balance the layout.
We may also want to add a console or errors tab to that side at some point...

I actually like the preview toolbar because it both makes the alignment of the main areas consistent, and gives a place to show the filename. We may very well want to allow transitions in some demos.

Ok, added it back.

If you look at the React editable samples, they have a toolbar with just the static text "RESULT", probably to balance the layout.

I made the default text "result", I think that's nicer than "index.html".

We may also want to add a console or errors tab to that side at some point...

Makes sense, for another PR though.

Do you want to remove or make optional the gutter in this PR? I think it'll look much cleaner

Do you want to remove or make optional the gutter in this PR? I think it'll look much cleaner

It's already optional if you do a cusotm layout

Do you want to remove or make optional the gutter in this PR? I think it'll look much cleaner

Done.


Support memchr4, memchr5, etc.

I'm writing a routine that escapes HTML special characters. To do that, I have to search for five different characters (&, <, >, ', ") simultaneously. I can do this using two calls to memchr2 or memchr3, but that doesn't seem elegant. It would be nice if there was a function that could do this search in one go.
From the implementation side: the PCMPESTRI instruction in SSE4.2 supports searching for up to 16 different needles in parallel. It would be nice if we could expose this somehow.

It only makes sense to expose these functions if there is a performance
benefit over the naive solution. Last time I checked, there wasn't.
Implementing these with SSE instructions would be nice, but I'm not
particularly motivated to deal with that until it can feasibly work on Rust
stable. In the interim, you might find the jetscii crate useful.
On Oct 18, 2016 03:58, "Chris Wong"<EMAIL_ADDRESS>wrote:

I'm writing a routine that escapes HTML special characters. To do that, I
have to search for five different characters (&, <, >, ', ")
simultaneously. I can do this using two calls to memchr2 or memchr3, but
that doesn't seem elegant. It would be nice if there was a function that
could do this search.
From the implementation side: the PCMPESTRI instruction in SSE4.2 supports
searching for up to 16 different needles in parallel. It would be nice if
we could expose this somehow.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BurntSushi/rust-memchr/issues/11, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAb34nYjzIU6TDTY1Fee6wDCke89iQ0Wks5q1HwkgaJpZM4KZe4g
.

To be clear, the native solution is to create a [bool; 256] and check each byte in the haystack against that set. Alternatively, hard code the check for each byte. (See the benchmarks in this crate.)

I'm going to close this because it's somewhat open ended. In order for these functions to make sense, there needs to be an experimental process that justifies their use. That is, I am firmly opposed to "just adding them" to complete the sequential pattern established by memchr, memchr2, memchr3, ...
Using explicit vector instructions would be nice here, but it would probably be nice everywhere. It would be interesting to see if we could compete with the hand rolled Assembly versions in glibc.


Quickfix: Restrict tinyrpc to version 0.9.4

tinyrpc 1.0.0 breaks python 2.7 support and only supports python3. 0.9.4
is the last version with python 2.7 support. Idealy this should be fixed
in the dependency list of ryu, but until that happens the problem can be
worked around by manually installing version 0.9.4.
Without this fix newly created virtual machines won't be able to run the
sdn controller

I also opened a pull request with ryu here: https://github.com/osrg/ryu/pull/84

This has now been fixed in ryu and is therefor no longer needed here.


[Bug] The database statement is too long and cannot be fully displayed when copied

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
UI (apache/skywalking-booster-ui)
What happened
The database statement is too long and cannot be fully displayed when copied
What you expected to happen
Database statement is too long, copying it shows comprehensive information
How to reproduce
Slow queries were detected in Virtual Database Service, and when the number of copied statement fields reached 200, incomplete information display occurred during copying
Anything else

Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I didn't reproduce this issue.

This is not about copied. Your SQL statement is truncated when it was collected by the agent.


print the grid in terminal, modified based on PR #2

Re-work #2 but take numpy array as input.
Example usage:
import arckit
import arckit.vis as vis

# Load the training data
train_set, eval_set = arckit.load_data()

# Get the first task
task = train_set[0]

# Loop through the training examples
for i, (input_array, output_array) in enumerate(task.train):
    print(f"Training Example {i+1}")
    print("Input:")
    vis.print_grid(input_array)
    print("Output:")
    vis.print_grid(output_array)
    print()

which has the same visual result as in #2

This is great, thank you! Could we add an example to the README?
https://github.com/mxbi/arckit/blob/main/README.md?plain=1#L116

script snippet and image added to RAEDME.


Investigate the prospects of pallas

Pallas would allow as to write some more optimized kernels that come with AD for free (at least for well behaved kernels like the Gaussian basis and Radial functions).
https://jax.readthedocs.io/en/latest/pallas/index.html
we could try and guesstimate if and how much performance we can squeeze out with some custom kernels.

I still haven't managed to install it. I will close this until pallas becomes a stable part of jax.


support for multiple (datetime) columns in csv data/datatable

example: http://www.highcharts.com/demo/spline-irregular-time

relates to #23


Android talkback can't focus on nav on subsequent pages

After navigating to later pages, you can't focus on buttons in nav. it just focuses on the entire landmark.
Added aria-live="off" to fix this.

still experiencing this bug in the e/aria branch. i think it might be because i nested header and nav and that these two things shouldn't be nested. i may need to make nav a top level item.

According to specs, landmarks can be nested. Yet moving nav outside of header did fix the issue.
Other references:
https://www.w3.org/TR/wai-aria-practices/examples/landmarks/navigation.html


feat: port Algebra.Order.Monoid.Defs

from mathlib3port<PHONE_NUMBER>0d5b5d1e2d1f4f37e5420357bdc636
The structure definitions and instances already existed, in the placeholder file Algebra.Order.Monoid; just a couple of lemmas needed to be ported.  The remaining material in the placeholder file Algebra.Order.Monoid was about ordered-cancel-monoids, so I have moved this to a new placeholder file Algebra.Order.Monoid.Cancel (itself to be replaced eventually by Algebra.Order.Monoid.Cancel.*).
I commented out the lemma
theorem bit0_pos [OrderedAddCommMonoid α] {a : α} (h : 0 < a) : 0 < bit0 a :=
  add_pos' h h

was this the right move or should I have deleted it?  Or kept and labelled as a nolint?

We're leaving lemmas about bit0/bit1 in place, in a section with the deprecated linter turned off.

bors merge


[Speak] Add a channel argument to webhook commands

Hello,
Here is a modification of Speak to support the channel argument.

Thanks in advance.

kindly resolve the conflict and use black -l 99 .
I think this is ready for merge


feat: decouple config operation from nacos sdk

解除和Nacos SDK的强耦合

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


Underscores in Numeric Literals

I am sorry if this is not the right place.
How about changing the syntax of numeric literals in plutus?
Haskell/GHC has recently adopted an extension that enables underscores in numeric literals:

https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0009-numeric-underscores.rst

Current syntax
In my understanding, the current specification of numeric literals in plutus is below:

https://cardanodocs.com/technical/plutus/types/#ints-floats-and-byte-strings

<int> ::= "-"? <digit>+
<float> ::= "-"? <digit>+ <fractExponent>
<digit> = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9"
<fractExponent> ::= <fraction> <exponent>? | <exponent>
<fraction> ::= "." <digit>+
<exponent> ::= ("e" | "E") ("-" | "+") <digit>+

<bytestring> ::= "#" <byte>*
<byte> ::= <nybble> <nybble>
<nybble> ::= <digit>
           | "a" | "b" | "c" | "d" | "e" | "f"
           | "A" | "B" | "C" | "D" | "E" | "F"

Proposed change syntax
How about changing it as follows?
This improves the readability, quality and expressiveness, especially for large numeric literals.
- <int> ::= "-"? <digit>+
+ <int> ::= "-"? <digit> ("_"* <digit>)*

- <float> ::= "-"? <digit>+ <fractExponent>
+ <float> ::= "-"? <digit> ("_"* <digit>)* <fractExponent>

- <fraction> ::= "." <digit>+
+ <fraction> ::= "." <digit> ("_"* <digit>)*

- <exponent> ::= ("e" | "E") ("-" | "+") <digit>+
+ <exponent> ::= ("e" | "E") ("-" | "+") <digit> ("_"* <digit>)*

- <bytestring> ::= "#" <byte>*
+ <bytestring> ::= "#" (<byte> ("_"* <byte>)*)?

Example
The followings are examples of this proposal:
lovelace = 0.000_001 :: Float
ada = 1_000_000 :: Int

This doesn't seem important, given that PLC is not really intended for humans to write or read.


[python] Skip ingest of zero-cell uns arrays

Issue and/or context: Resolves #1466
Changes: Don't ingest uningestibles
Notes for Reviewer: @aaronwolen @mojaveazure looking for compbio feedback on this approach

Codecov Report
Patch coverage: 25.00% and project coverage change: +27.28 :tada:

Comparison is base (879f7c5) 63.99% compared to head (fd20cd4) 91.27%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1468       +/-   ##
===========================================
+ Coverage   63.99%   91.27%   +27.28%
===========================================
  Files         101       30       -71
  Lines        8215     2498     -5717
===========================================
- Hits         5257     2280     -2977
+ Misses       2958      218     -2740

Flag
Coverage Δ

python
91.27% <25.00%> (-0.11%)
:arrow_down:

r
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

apis/python/src/tiledbsoma/io/ingest.py
85.49% <25.00%> (-0.48%)
:arrow_down:

... and 71 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[BUG]: Automated tests from test plans fail at VSTest task not discovering tests when executed

Task name
VsTest
Task version
2.x
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[x] Microsoft Hosted
[x] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows
Task log
2023-11-06T20:25:00.4717439Z ==============================================================================
2023-11-06T20:25:00.4717748Z Task         : Visual Studio Test
2023-11-06T20:25:00.4717891Z Description  : Run unit and functional tests (Selenium, Appium, Coded UI test, etc.) using the Visual Studio Test (VsTest) runner. Test frameworks that have a Visual Studio test adapter such as MsTest, xUnit, NUnit, Chutzpah (for JavaScript tests using QUnit, Mocha and Jasmine), etc. can be run. Tests can be distributed on multiple agents using this task (version 2).
2023-11-06T20:25:00.4719605Z Version      : 2.229.0
2023-11-06T20:25:00.4719715Z Author       : Microsoft Corporation
2023-11-06T20:25:00.4719870Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/test/vstest
2023-11-06T20:25:00.4720201Z ==============================================================================
2023-11-06T20:25:01.4045017Z In distributed testing flow
2023-11-06T20:25:01.4078805Z ======================================================
2023-11-06T20:25:01.4099576Z Test selector : Test run
2023-11-06T20:25:01.4101677Z Test run Id : '9999999'
2023-11-06T20:25:01.4103302Z Search folder : C:\a\r1\a
2023-11-06T20:25:01.4273716Z Action when minimum tests threshold not met : donothing
2023-11-06T20:25:01.4275354Z Minimum tests expected to be run: 0
2023-11-06T20:25:01.7381653Z Distributed test execution, number of agents in job : 1
2023-11-06T20:25:01.7394818Z Run settings file : C:\a\r1\a\__artifactAlias\Test.Automation.xxxxxxxxxxxx\test.runsettings
2023-11-06T20:25:01.7400384Z Run in parallel : false
2023-11-06T20:25:01.7402004Z Run in isolation : false
2023-11-06T20:25:01.7403679Z Path to custom adapters : undefined
2023-11-06T20:25:01.7407979Z Other console options : /diag:C:\a\_temp\TestResults\diagnostic.txt
2023-11-06T20:25:01.7462887Z ##[warning]Other console options is not supported for this task configuration. This option will be ignored.
2023-11-06T20:25:01.7475340Z Code coverage enabled : false
2023-11-06T20:25:01.7477895Z Diagnostics enabled : true
2023-11-06T20:25:01.7482579Z Rerun failed tests: true
2023-11-06T20:25:01.7485799Z Rerun failed tests threshold: 30
2023-11-06T20:25:01.7487520Z Rerun maximum attempts: 3
2023-11-06T20:25:01.7612050Z ======================================================
2023-11-06T20:25:01.7616615Z Source filter: **\*test*.dll,!**\*TestAdapter.dll,!**\obj\**
2023-11-06T20:25:02.8406336Z ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work.
2023-11-06T20:25:02.8558104Z ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work.
2023-11-06T20:25:03.0655309Z ##[warning]Test Impact (Run only Impacted tests) and Code Coverage data collector will not work.
2023-11-06T20:25:03.0762832Z [command]C:\a\_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.229.0\Modules\DTAExecutionHost.exe --inputFile C:\a\_temp\input_90e405e0-7ce2-11ee-a7d4-5fbeb6c44523.json
2023-11-06T20:25:03.1460510Z ##########################################################################
2023-11-06T20:25:03.1461947Z DtaExecutionHost version 19.229.34210.1.
2023-11-06T20:25:04.8620369Z ===========================================
2023-11-06T20:25:04.8621522Z AgentName: agenttest-agenttest-63040
2023-11-06T20:25:04.8622439Z ServiceUrl: https://dev.azure.com/ORG/
2023-11-06T20:25:04.8623207Z TestPlatformVersion: 17.7.2
2023-11-06T20:25:04.8624085Z EnvironmentUri: vstest://env/PROJECT/_apis/release/777/88888/000000/1
2023-11-06T20:25:04.8625204Z QueryForTaskIntervalInMilliseconds: 3000
2023-11-06T20:25:04.8626051Z MaxQueryForTaskIntervalInMilliseconds: 10000
2023-11-06T20:25:04.8626687Z QueueNotFoundDelayTimeInMilliseconds: 3000
2023-11-06T20:25:04.8627426Z MaxQueueNotFoundDelayTimeInMilliseconds: 50000
2023-11-06T20:25:04.8628353Z ===========================================
2023-11-06T20:25:05.4883421Z Result Attachments will be stored in LogStore
2023-11-06T20:25:05.5030430Z Run Attachments will be stored in LogStore
2023-11-06T20:25:05.6587930Z TestExecutionHost.Execute: Registered TestAgent : 54119 : agenttest-agenttest-63040
2023-11-06T20:25:05.6804108Z Provided settings file:
2023-11-06T20:25:05.6821804Z <?xml version="1.0" encoding="utf-8"?>
2023-11-06T20:25:05.6822728Z <RunSettings>
2023-11-06T20:25:05.6823430Z 	<!-- Configurations that affect the Test Framework -->
2023-11-06T20:25:05.6824409Z 	<RunConfiguration>
2023-11-06T20:25:05.6825600Z 		<DisableParallelization>false</DisableParallelization>
2023-11-06T20:25:05.6826515Z 		<MaxCpuCount>1</MaxCpuCount>
2023-11-06T20:25:05.6827182Z 	</RunConfiguration>
2023-11-06T20:25:05.6827705Z 	<DataCollectionRunSettings>
2023-11-06T20:25:05.6829232Z 		<DataCollectors>
2023-11-06T20:25:05.6833679Z 			<DataCollector uri="datacollector://microsoft/VideoRecorder/1.0" assemblyQualifiedName="Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder.VideoRecorderDataCollector, Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" friendlyName="Screen and Voice Recorder">
2023-11-06T20:25:05.6838490Z 				<!--Video data collector was introduced in Visual Studio 2017 version 15.5-->
2023-11-06T20:25:05.6839988Z 				<Configuration>
2023-11-06T20:25:05.6841487Z 					 <!--Set "sendRecordedMediaForPassedTestCase" to "false" to add video attachments to failed tests only-->
2023-11-06T20:25:05.6843404Z 					<MediaRecorder sendRecordedMediaForPassedTestCase="false"  xmlns="">
2023-11-06T20:25:05.6853458Z
2023-11-06T20:25:05.6854664Z 						<ScreenCaptureVideo bitRate="512" frameRate="2" quality="20" />
2023-11-06T20:25:05.6855808Z 					</MediaRecorder>
2023-11-06T20:25:05.6856397Z 				</Configuration>
2023-11-06T20:25:05.6856925Z 			</DataCollector>
2023-11-06T20:25:05.6857466Z 		</DataCollectors>
2023-11-06T20:25:05.6857991Z 	</DataCollectionRunSettings>
2023-11-06T20:25:05.6858446Z
2023-11-06T20:25:05.6859068Z 	<!-- MSTest adapter -->
2023-11-06T20:25:05.6859650Z 	<MSTest>
2023-11-06T20:25:05.6860082Z 		<Parallelize>
2023-11-06T20:25:05.6860603Z 			<Workers>1</Workers>
2023-11-06T20:25:05.6861361Z 			<Scope>MethodLevel</Scope>
2023-11-06T20:25:05.6861992Z 		</Parallelize>
2023-11-06T20:25:05.6862519Z 	</MSTest>
2023-11-06T20:25:05.6862981Z </RunSettings>
2023-11-06T20:25:05.6863291Z
2023-11-06T20:25:05.6975334Z IsValidServiceResponse: Received None command..Service Workflow is not active
2023-11-06T20:25:05.7126093Z Updated Run Settings:
2023-11-06T20:25:05.7126936Z <RunSettings>
2023-11-06T20:25:05.7128560Z   <!-- Configurations that affect the Test Framework -->
2023-11-06T20:25:05.7129565Z   <RunConfiguration>
2023-11-06T20:25:05.7130385Z     <DisableParallelization>false</DisableParallelization>
2023-11-06T20:25:05.7132110Z     <MaxCpuCount>1</MaxCpuCount>
2023-11-06T20:25:05.7132889Z     <BatchSize>1000</BatchSize>
2023-11-06T20:25:05.7133939Z     <ResultsDirectory>C:\a\_temp\TestResults</ResultsDirectory>
2023-11-06T20:25:05.7135539Z   </RunConfiguration>
2023-11-06T20:25:05.7136593Z   <DataCollectionRunSettings>
2023-11-06T20:25:05.7137390Z     <DataCollectors>
2023-11-06T20:25:05.7141811Z       <DataCollector uri="datacollector://microsoft/VideoRecorder/1.0" assemblyQualifiedName="Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder.VideoRecorderDataCollector, Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" friendlyName="Screen and Voice Recorder">
2023-11-06T20:25:05.7148324Z         <!--Video data collector was introduced in Visual Studio 2017 version 15.5-->
2023-11-06T20:25:05.7149933Z         <Configuration>
2023-11-06T20:25:05.7151568Z           <!--Set "sendRecordedMediaForPassedTestCase" to "false" to add video attachments to failed tests only-->
2023-11-06T20:25:05.7153701Z           <MediaRecorder sendRecordedMediaForPassedTestCase="false" xmlns="">
2023-11-06T20:25:05.7155995Z
2023-11-06T20:25:05.7157022Z 						<ScreenCaptureVideo bitRate="512" frameRate="2" quality="20" />
2023-11-06T20:25:05.7158314Z 					</MediaRecorder>
2023-11-06T20:25:05.7159299Z 				</Configuration>
2023-11-06T20:25:05.7160126Z       </DataCollector>
2023-11-06T20:25:05.7161238Z       <DataCollector friendlyName="blame" enabled="True">
2023-11-06T20:25:05.7162481Z         <Configuration>
2023-11-06T20:25:05.7163601Z           <ResultsDirectory>C:\a\_temp\TestResults</ResultsDirectory>
2023-11-06T20:25:05.7164956Z           <CollectDump CollectAlways="true" />
2023-11-06T20:25:05.7166559Z           <CollectDump />
2023-11-06T20:25:05.7167971Z         </Configuration>
2023-11-06T20:25:05.7169062Z       </DataCollector>
2023-11-06T20:25:05.7170326Z     </DataCollectors>
2023-11-06T20:25:05.7171718Z   </DataCollectionRunSettings>
2023-11-06T20:25:05.7172864Z   <!-- MSTest adapter -->
2023-11-06T20:25:05.7173735Z   <MSTest>
2023-11-06T20:25:05.7174906Z     <Parallelize>
2023-11-06T20:25:05.7175851Z       <Workers>1</Workers>
2023-11-06T20:25:05.7177126Z       <Scope>MethodLevel</Scope>
2023-11-06T20:25:05.7178766Z     </Parallelize>
2023-11-06T20:25:05.7179778Z   </MSTest>
2023-11-06T20:25:05.7180651Z   <LoggerRunSettings>
2023-11-06T20:25:05.7181586Z     <Loggers>
2023-11-06T20:25:05.7182653Z       <Logger friendlyName="blame" enabled="True" />
2023-11-06T20:25:05.7184883Z     </Loggers>
2023-11-06T20:25:05.7186072Z   </LoggerRunSettings>
2023-11-06T20:25:05.7186992Z </RunSettings>
2023-11-06T20:25:05.8136769Z Creating run for selected test assemblies with following parameters
2023-11-06T20:25:05.8139134Z SourceFilter: *.dll TestCaseFilter:
2023-11-06T20:25:05.8141563Z Run title: xxxxxxxxxxxxxxxxxxxxxxx - Assembly_Release-13
2023-11-06T20:25:05.8142865Z Build location: C:\a\r1\a
2023-11-06T20:25:05.8143862Z Build Id: 3333333
2023-11-06T20:25:06.0355469Z Test run with Id 9999999 associated
2023-11-06T20:25:16.7384975Z Received the command : Start
2023-11-06T20:25:16.7404361Z TestExecutionHost.ProcessCommand. Start Command handled
2023-11-06T20:25:18.6282525Z Slice with id = 66666, of type = 'Execution' received.
2023-11-06T20:25:18.8977548Z Count of test sources found: 2
2023-11-06T20:25:18.9210177Z =================================================================
2023-11-06T20:25:18.9211674Z Discovering tests from sources
2023-11-06T20:25:18.9461578Z Using new test platform for test execution
2023-11-06T20:25:18.9571175Z Microsoft.TestPlatform.VsTestConsole.TranslationLayer.VsTestConsoleWrapper instance will be created
2023-11-06T20:25:29.3985379Z DiscoveryMessage : [xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v<IP_ADDRESS>+6b60a9e56a (64-bit .NET 6.0.16)
2023-11-06T20:25:30.4142575Z DiscoveryMessage : [xUnit.net 00:00:00.56]   Discovering: xxxxxxxxxxxx.FunctionalTests
2023-11-06T20:25:30.8324559Z DiscoveryMessage : [xUnit.net 00:00:01.45]   Discovered:  xxxxxxxxxxxx.FunctionalTests
2023-11-06T20:25:33.1196296Z Number of testcases discovered : 707
2023-11-06T20:25:33.1395128Z Discovered tests 707 from sources
2023-11-06T20:25:33.1396036Z =================================================================
2023-11-06T20:25:33.1641445Z [RunStatistics]This execution slice with id '66666', received '1' testcases to execute out of which '0' is discovered.
2023-11-06T20:25:33.1967140Z List of test cases in slice with id: 66666
2023-11-06T20:25:33.1971615Z Source: xxxxxxxxxxxx.FunctionalTests.dll, FullyQualifiedTestName: xxxxxxxxxxxx.FunctionalTests.Features.Functional.xxxxxxxxxxxx.SAMPLETESTMETHOD
2023-11-06T20:25:33.2229981Z ##[error]ExecutionAndPublish.Run : Microsoft.VisualStudio.TestService.VstestAdapter.TestsNotFoundException: No test assemblies found on the test machine matching the source filter criteria or no tests discovered matching test filter criteria. Verify that test assemblies are present on the machine and test filter criteria is correct.
2023-11-06T20:25:33.2237947Z    at Microsoft.VisualStudio.TestService.VstestAdapter.Execution.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:33.2241541Z    at Microsoft.VisualStudio.TestService.VstestAdapter.ExecutionAndPublish.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:33.2290505Z ##[error]The slice of type 'Execution' is 'Aborted' because of the error : Microsoft.VisualStudio.TestService.VstestAdapter.TestsNotFoundException: No test assemblies found on the test machine matching the source filter criteria or no tests discovered matching test filter criteria. Verify that test assemblies are present on the machine and test filter criteria is correct.
2023-11-06T20:25:33.2309860Z    at Microsoft.VisualStudio.TestService.VstestAdapter.Execution.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:33.2313698Z    at Microsoft.VisualStudio.TestService.VstestAdapter.ExecutionAndPublish.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:37.7462112Z Received the command : Stop
2023-11-06T20:25:37.7463428Z TestExecutionHost.ProcessCommand. Stop Command handled
2023-11-06T20:25:37.7472402Z SliceFetch Aborted. Moving to the TestHostEnd phase
2023-11-06T20:25:37.7936092Z Please use this link to analyze the test run : https://dev.azure.com/ORG/PROJECT/_TestManagement/Runs#_a=resultQuery&runId=9999999&queryPath=Recent+Run%2FRun9999999
2023-11-06T20:25:37.7939786Z Test run '9999999' is in 'Aborted' state with 'Total Tests' : 1 and 'Passed Tests' : 0.
2023-11-06T20:25:37.7996602Z ##[error]Test run is aborted. Logging details of the run logs.
2023-11-06T20:25:37.8005110Z ##[error]System.Exception: The test run was aborted, failing the task.
2023-11-06T20:25:37.9039187Z ##########################################################################
2023-11-06T20:25:37.9603912Z ##[section]Finishing: VsTest - testRun

Relevant log output
2023-11-06T20:25:06.0355469Z Test run with Id 9999999 associated
2023-11-06T20:25:16.7384975Z Received the command : Start
2023-11-06T20:25:16.7404361Z TestExecutionHost.ProcessCommand. Start Command handled
2023-11-06T20:25:18.6282525Z Slice with id = 66666, of type = 'Execution' received.
2023-11-06T20:25:18.8977548Z Count of test sources found: 2
2023-11-06T20:25:18.9210177Z =================================================================
2023-11-06T20:25:18.9211674Z Discovering tests from sources
2023-11-06T20:25:18.9461578Z Using new test platform for test execution
2023-11-06T20:25:18.9571175Z Microsoft.TestPlatform.VsTestConsole.TranslationLayer.VsTestConsoleWrapper instance will be created
2023-11-06T20:25:29.3985379Z DiscoveryMessage : [xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v<IP_ADDRESS>+6b60a9e56a (64-bit .NET 6.0.16)
2023-11-06T20:25:30.4142575Z DiscoveryMessage : [xUnit.net 00:00:00.56]   Discovering: xxxxxxxxxxxx.FunctionalTests
2023-11-06T20:25:30.8324559Z DiscoveryMessage : [xUnit.net 00:00:01.45]   Discovered:  xxxxxxxxxxxx.FunctionalTests
2023-11-06T20:25:33.1196296Z Number of testcases discovered : 707
2023-11-06T20:25:33.1395128Z Discovered tests 707 from sources
2023-11-06T20:25:33.1396036Z =================================================================
2023-11-06T20:25:33.1641445Z [RunStatistics]This execution slice with id '66666', received '1' testcases to execute out of which '0' is discovered.
2023-11-06T20:25:33.1967140Z List of test cases in slice with id: 66666
2023-11-06T20:25:33.1971615Z Source: xxxxxxxxxxxx.FunctionalTests.dll, FullyQualifiedTestName: xxxxxxxxxxxx.FunctionalTests.Features.Functional.xxxxxxxxxxxx.SAMPLETESTMETHOD
2023-11-06T20:25:33.2229981Z ##[error]ExecutionAndPublish.Run : Microsoft.VisualStudio.TestService.VstestAdapter.TestsNotFoundException: No test assemblies found on the test machine matching the source filter criteria or no tests discovered matching test filter criteria. Verify that test assemblies are present on the machine and test filter criteria is correct.
2023-11-06T20:25:33.2237947Z    at Microsoft.VisualStudio.TestService.VstestAdapter.Execution.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:33.2241541Z    at Microsoft.VisualStudio.TestService.VstestAdapter.ExecutionAndPublish.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:33.2290505Z ##[error]The slice of type 'Execution' is 'Aborted' because of the error : Microsoft.VisualStudio.TestService.VstestAdapter.TestsNotFoundException: No test assemblies found on the test machine matching the source filter criteria or no tests discovered matching test filter criteria. Verify that test assemblies are present on the machine and test filter criteria is correct.
2023-11-06T20:25:33.2309860Z    at Microsoft.VisualStudio.TestService.VstestAdapter.Execution.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:33.2313698Z    at Microsoft.VisualStudio.TestService.VstestAdapter.ExecutionAndPublish.Run(ExecutionStateContext stateModelContext, CancellationToken cancellationToken)
2023-11-06T20:25:37.7462112Z Received the command : Stop
2023-11-06T20:25:37.7463428Z TestExecutionHost.ProcessCommand. Stop Command handled

Aditional info
Looks like it started to happen after the VSTest task is updated to 2.229.0. I ca see the task was running fine till when it was 2.228.0. after that the runs were failing.

Related to https://github.com/microsoft/azure-pipelines-tasks/issues/19222.
We have see it work and fail with with 2.229.0.

Possible fix is to move from VSTest@2  to VSTest@3

Possible fix is to move from VSTest@2 to VSTest@3 (Undocumented https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/vstest-v2?view=azure-pipelines)

I have a similar issue where 2.229.0 was working (found and executed 6/6 test cases in a Test Plan), but now only runs 3/6 Test Cases and leaves the remaining test cases with an Outcome of 'In Progress'.
I have just tried VSTest@3 (v3.225.0), and now all 6 test cases are executed successfully again.

Possible fix is to move from VSTest@2 to VSTest@3 (Undocumented https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/vstest-v2?view=azure-pipelines)
Wonder if the node pathing has changed as it looks for the dlls? Could be due to #19215

Upgrade won't work in our case as it will fail the Automated test run from the Test plan validation. Looks like its when we select a subset of tests to be run from test plan, choosing this release with vstest@v2 only works. Rest fails the validation and wont kick it off. Link to referenced steps from microsoft.

I did test with vstest@V3 to run entire test plan. It seems to be working with the v3 task. But unfortunately, the Automated test run validation is not allowing V3 task. Probably will need to fix that validation and we can try with the V3 task in the test run mode from Automated test run.

@qianz2 @merlynomsft @rasunkar any thoughts?

I have exactly the same setup as @sailesh89 and am experiencing the same issue.
On the afternoon of 9th November a number of tests stopped working. Now this morning (10th) those same tests are executing. No changes were made on my end at any point.

This still seems to be an issue with Version 2 of the vstest runner,
still unable to run tests from test plan with version 3
can we reopen this issue?

I stopped using VSTest it as it doesn't work on Ubuntu anyway.
We use dotnet test now and our own custom version of
https://github.com/idubnori/ParallelTestingSample-dotnet-core


Hide already added mods

I'm not really so sure this is the best implementation of this. I will need to test and fiddle with it. Thank you for the PR, it is a good idea.

I did it this way because it was easy and I was lazy but I'm sure a simple query would be tons better, I'll look into it if you don't do it first.

Any chance this will be tweaked and pulled? Waiting for all the good PRs that will be most useful to me to be pulled before doing an update on my solder.


rustscan: 2.1.1 -> 2.2.2

Diff: https://github.com/RustScan/RustScan/compare/refs/tags/2.1.1...2.2.2
Changelog: https://github.com/RustScan/RustScan/releases/tag/2.2.2
Description of changes

Things done

Built on platform(s)

[ ] 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.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

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

1 package built:

rustscan


AltGr misbehaving on OpenMV IDE 2.8.1

I just upgraded to IDE 2.8.1 (tabs, yey). However this seems to have broken keyboard input. I’m on a Swedish keyboard layout, where {} brackets are on AltGr-7 to AltGr-0. Nothing happens when I try to input these. This is quite annoying, fix would be nice :).

Same here: IDE 2.8.1 on Windows 10 Home with a Swiss keyboard layout and on two different computers.

[AltGr]+[0..9] get ignored, so do [Ctrl]+[Alt]+[0..9] (which should have the same effect)
[AltGr]+[e] would work (on the Swiss keyboard that's the Euro sign - obviously not needed for python, but it seems some [AltGr] stuff seems to work)
I only have this issue with OpenMV IDE, so I guess it's not on Windows this time.
it doesn't matter what Language I set in Options->User Interface->Language

[AltGr]+[3] is the '#' sign, so commenting is a bit difficult now...

Hi, tab shortcuts are generated by:
QStringLiteral("Ctrl+Alt+%1");
Where %1 is replaced with 1 through 0.
What should I replace this with? I can remove the feature. Would like to keep it. But, I don't know if that's possible.

Also, what OS are you both using? I will cut a new release quickly with the fix.

I'm on Win 10 Pro. I would

remove the shortcut by default, because the downside is quite bad for affected users
think about adding these shortcuts under configuration option, so users like yourself can benefit from the shortcuts
(bigger job) add system for configuring shortcuts, because everyone has different preferences, and this is not going to be the last time they conflict. It's also very convenient to be able to configure the same shortcuts in OpenMV IDE as I might have in other IDEs.

QtCreator actually already has #3. I just hid it. I'll renable it and turn the shortcut off by default.

Great!
Yeah I think you're keeping a small but good feature-set in general. The only features I really miss from e.g. IntelliJ is goto definition/usage and breadcrumbs (meaning goto previous/next cursor location).

The IDE has goto previous location. But, I hid it too. I can re-enable.

Just disabled these QStringLiteral("Ctrl+Alt+%1"); shortcuts.


white edges on dropdown menus

Describe the bug
Dropdown menus have a white edge on the bottom left
To Reproduce
Steps to reproduce the behavior:

Open a menu

Expected behavior
Dark border edge
Screenshots
If applicable, add screenshots to help explain your problem.
https://i.imgur.com/jRgzUtE.png

Desktop (please complete the following information):

OS: Windows 10
Franz/Ferdi: 5.4.1-beta4

Add any other context about the problem here.

Still an issue

Still an issue

Still an issue

Still an issue

still relevant

still relevant

Cannot reproduce this with v5.6.1-nightly.48 in either dark or light mode on any dropdown menu in Ferdi.
This was probably fixed upstream in newer versions of electron in the mean time.

Cannot reproduce this with v5.6.1-nightly.48 in either dark or light mode on any dropdown menu in Ferdi.
This was probably fixed upstream in newer versions of electron in the mean time.

Can confirm fixed in 5.6.1-beta3 as well.


MODCLUSTER-432 Multicast discovery does not work on Mac OS X, fails w…

…ith "Can't assign requested address"
Mirror JGroups behavior
Reenable tests
Include support for Solaris
Rename  the variable to represent better what the property is (was called linuxlike)
Fix redundant and incorrect javadoc
Jira
https://issues.jboss.org/browse/MODCLUSTER-432

Triggering build using a merge of d74dc22db392eeadf3b7676e581ae5f749bd60b7 on branch master:
Private: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mod_cluster-1.3.x-pull-player-executor/

Build 149 outcome was SUCCESS using a merge of d74dc22db392eeadf3b7676e581ae5f749bd60b7 on branch master:
Private: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/mod_cluster-1.3.x-pull-player-executor/149
Public: https://hudson.jboss.org/hudson/job/mod_cluster-1.3.x-pull-player-executor/149

Also passes on older version:
Darwin macosx.gva.redhat.com 13.4.0 Darwin Kernel Version 13.4.0: Sun Aug 17 19:50:11 PDT 2014; root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64

Regarding our discussion with @rhusar: It appears it did not break Solaris; at least Solaris 10 SPARC binds happily without exceptions with/without Apache HTTP Server starting before/after EAP. My test HEAD: 1.3.2.Alpha1-SNAPSHOT 9202ebddc1.


cargo info implementation (similar to npm show/info cmd)

Describe the problem you are trying to solve

So I frequently use with ruby/npm/apt the show / info  commands to get more package information (link to git, homepage, keywords, etc), but as far as I know this isn't possible with cargo.  I thought it would be really useful to have the ability to use something along the lines of: cargo show [pkgname] to get some basic info about a package.
Describe the solution you'd like

I created a script that implements the crates.io api, it is just preliminary and the only requirement is the package jq . I included the version I made which has a colored output, although this could easily be removed/disabled by replacing the color-echo cmds simply with echo.
That script is here, id be curious what people think.
To run:

Install dependencies (not much, could probably be eliminated altogether using awk anyways)

apt install jq

Either save somewhere in  $PATH, or just run locally via ./cargo-show. (obviously chmod +x  it as well)

To search:
cargo-show [packagename]
Looks like this:

Notes

It looks like this is a duplicate of #948, closing in favor of that


Arrows

Would love to see implementation to where you can layer arrows as well, rather than just free-draw.

Nevermind - Reading now that you guys no longer support this.


Update asset detail redlines with overview tab

Asset detail page redlines need to be updated with the latest designs from #485 discussion.

[x] Add overview tab
[x] Get feedback on related assets cards
[x] Add feedback section (should slack be mini cards or just listed out? we should follow the pattern in library contacts as well)
[x] Schedule Design review

Related:
https://github.com/carbon-design-system/carbon-platform/issues/817


Completeness relation of kraus operators not satisfied in Fake backends

With the following code
from qiskit.providers.fake_provider import FakeGuadalupe
from qiskit.providers.aer.noise import NoiseModel
import numpy as np

backend = FakeGuadalupe()
nm = NoiseModel.from_backend(backend)

print(nm._local_quantum_errors['cx'][(0,1)].circuits[0])
print(len(nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params))

k11=np.transpose(nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params[0].conj())*nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params[0]
k22=np.transpose(nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params[1].conj())*nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params[1]
k33=np.transpose(nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params[2].conj())*nm._local_quantum_errors['cx'][(0,1)].circuits[0][1][0].params[2]
print(k11+k22+k33)

I get the following output:
     ┌────────────┐┌───────┐
q_0: ┤0           ├┤ kraus ├
     │  Pauli(II) │├───────┤
q_1: ┤1           ├┤ kraus ├
     └────────────┘└───────┘
3
[[1.        +0.j 0.        +0.j]
 [0.        +0.j 0.99257842+0.j]]

But I think that this means that the completeness relation of the kraus operator is not satisfied. Am I missing anything?

Matrix multiplication is done with @ on Numpy arrays - * is elementwise multiplication.  So the last error (your k33) is made a matrix that looks like
k3 = np.array([[0.+0.j, 0.08614861+0.j],  [0.+0.j, 0.+0.j]])

If you do k3.conj().T * k3 (what you've done) you'll get the zero matrix, but if you use @ to get the matrix multiplication, you'll correctly recover the missing component from the $\lvert 1\rangle\langle 1\rvert$ term.

Matrix multiplication is done with @ on Numpy arrays - * is elementwise multiplication. So the last error (your k33) is made a matrix that looks like
k3 = np.array([[0.+0.j, 0.08614861+0.j],  [0.+0.j, 0.+0.j]])

If you do k3.conj().T * k3 (what you've done) you'll get the zero matrix, but if you use @ to get the matrix multiplication, you'll correctly recover the missing component from the |1⟩⟨1| term.

Thank you, I didn't realize I used * instead of np.matmul, sorry.


Add a key check for the bestPredecessor map

Hi @dominikbraun,
this fixes the non-termination of the ShortestPath function as seen in my example of #31 (probably not all undefined behaviors yet).
The reason for the non-termination was the map lookup here https://github.com/dominikbraun/graph/blob/21fcddafc8008532b8932dd616bda0fbb0e0493d/paths.go#L131 leads to hashCursor being set to 0 if the key is not present. Consequently, this leads to endlessly prepending 0 to the path since it will never be equal to the source.
This is why I added the check whether the key is present and if it is not, an error is returned. Furthermore, I added a test case that is exactly the well-defined example from #31.
Let me know, if there is something to change.

This change has been released with graph v0.13.0.


feat: add the unix keyword

This adds a new unix keyword.
I think the implementation is almost the same as integer except that it has a max value? Correct me if I am wrong.
For the type I just used number.atLeast<0> as it was the most fitting in my opinion.

I don't think this inherently has to be a positive integer, right? If it's before 1970, it would just be negative.
As is, this could be written as integer > 0. Maybe there's not enough universal restrictions on top of that to justify a new keyword.

Thanks for the contribution! The type is perfect.
My main concern is that I don't think this inherently has to be a positive integer. If it's before 1970, it would just be negative.
As is, this could be written as integer > 0. Maybe there's not enough universal restrictions on top of that to justify a new keyword.

True, I will support the negative numbers, I guess it could be simplified to -8640000000000000 <= integer >=<PHONE_NUMBER>000000


Fix 'non-well formed number notice' issue in PHP 7.2

try Fix 'non-well formed number notice' issue in PHP 7.2 or PHP 7.1

Thanks for the contribution, @codedeep
Could you provide a description on how to reproduce this issue?

My actual settings:
PHP 7.2.11
post_max_size => 32M
upload_max_filesize => 32M
memory_limit => 128M

Sorry, but I cannot reproduce any issue - neither with a post_max_size setting of 32M, or an integer value of 9000000.
The current code already does an explicit cast (using $val = (int)$val;), so I don't understand at the moment where the notice you encounter could come from.


Performance

Baked lighting (lots of hard work)
https://www.alielsaleh.com/ue4-plugins/object-pooler-guide

I went through and applied baked lighting to:

Neptune
Poledica
Baked Light Test (new map)

It has resulted in a massive performance gain.
I will look into the Object Pooler a bit later, though. If it works, it should also help.

I setup the Object Pooler with the flare. Unfortunately, the plugin is buggy as hell. Velocity has to be recalculated on spawn from pool. The particles attached to the BP class do not activate. When actors from the pool are re-used, the recalculated velocities don't even work. It's pretty terrible. So, for now, there won't be any object pooling.


middleware/file: also react to rename events.

Current coverage is 39.73% (diff: 100%)

Merging #406 into master will increase coverage by 0.05%

@@             master       #406   diff @@
==========================================
  Files           106        106
  Lines          5053       5053
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2005       2008     +3
+ Misses         2885       2883     -2
+ Partials        163        162     -1

Powered by Codecov. Last update fb7fcff...ed68832

Makes sense to just merge.


Guessing backend

Need to add a new sql table to store guesses I believe.
There's probably some python code to support adding and retrieving guesses that would be good to write. And as part of this, should mock up a quick forms-based guessing system to make sure that the backend works.
I'm breaking #5 down into this and #38

Add done, added a rudimentary front end to enable users to use the guessing system


License?

Hi there,
Thank you for bringing up the license matter for this repository.
I have updated the repository to include the MIT license.


stack.env does not work when deploying via repository

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
When deploying via repository and using a relative local filesystem path, the stack.env file in the repository is not used.  You can see this demonstrated using the simple test repository at:
Test stack.env repo
Expected Behavior
When running creating the stack from the sample repo, I expect the value of the env1 to display
Actual Behavior
The value is blank
Steps to Reproduce

Create the stack from https://github.com/marioja/test-stack-env.git.
enable relative path volumes
specify a valid/existing local filesystem path on your docker host
click deploy
Look at the logs from the only container created

Portainer logs or screenshots
env1=
Portainer version
2.21.3
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker 27.1.1 (API: 1.46)
OS and Architecture
TrueNAS Scale 24.10
Browser
Chrome Version 130.0.6723.117
What command did you use to deploy Portainer?
No response
Additional Information
There is a related issue #6701 but this issue is a specific case.  One other point is the sample repo I provided has the docker-compose.yml and stack.env file at the root of the repository.  In my real use-case both are in some folders in the git repo.  I get the same error but this is a test case that should be also verified when you do a fix.

I updated portainer to the latest version 2.21.4 and I get the same problem.

I hope that the fact that I provided a sample github repo to reproduce this problem will speedup the resolution.  Thank you.

In your compose file you have the environment variables first being populated from the stack.env file in the env_file definition:
    env_file:
      - stack.env

and then env1 being set again via the environment definition:
    environment:
      - env1=${env1}

This results in the value from the stack.env file being overwritten by that being set by environment later on. Since you're using ${env1} as the value, Portainer attempts to replace this with a value set in the form when configuring the stack, and if you don't have this set, the value will be blank.
You can test this by adding an additional environment variable definition to your stack.env file, for example:
env1=coucou
env2=toto

then modify your command entry to simply print all env vars:
    command: ["env"]

You'll see that env1 is blank as it's being overwritten as described above, however env2 is correctly set to the value in the stack.env file:
HOSTNAME=8b318d83b89a
env1=
SHLVL=1
env2=toto
HOME=/root
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/

You can also then confirm that the blank value is a result of not setting the value substitution via the form by adding a value in the form:

then redeploying the stack and checking the output:
HOSTNAME=a2b3bc7b890e
env1=test123
SHLVL=1
env2=toto
HOME=/root
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/

I've made the above changes in a fork of your repo if you want to test and confirm as well.

In your fork, you only define env1 in the environment for the main-initialize service.  It was my understanding that the env_file makes the composer env available but that only the ones in the environment definition should be created for the service.  I have made a number of modifications to the stack and will update with a new comment when ready.

If you update to the latest commit on the main branch you should see the following new setup.  I have created a number of environment variable which contain the following suffixes:

PE for Portainer environment, meaning these are added to Portainer as follow:

SE for variables defined in the stack.env file in the repository
DC for variable defined in the service main-initialize only

You can see the simple docker-compose.yml file:
services:
  main-initialize:
    image: alpine:latest
    env_file:
      - stack.env
    environment:
      ENVSE1:
      ENVSE2:
      ENVPE1:
      ENVPE2: "${ENVPE2}"
      ENVPE3:
      ENVDC1: "OU=Users,OU=bimbo"
    entrypoint: ["/bin/sh", "-xvc"]
    command: ['printenv; echo "compose: ENVSE1=${ENVSE1} ENVSE2=${ENVSE2} ENVSE3=${ENVSE3} ENVPE1=${ENVPE1} ENVPE2=${ENVPE2} ENVPE3=${ENVPE3} ENVDC1=${ENVDC1}";']

The command printenv will print the service environment variables and the echo command will print the composer environment variables.  I deploy via repository using two use cases and display the log file:
With relative path volumes disabled
+ printenv
ENVDC1=OU=Users,OU=bimbo
HOSTNAME=a7c0499594da
SHLVL=1
HOME=/root
ENVPE1=OU=Users,OU=bimbo
ENVPE2=toto
ENVPE3=OU=Users\,OU=bimbo
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
compose: ENVSE1= ENVSE2= ENVSE3= ENVPE1=OU=Users,OU=bimbo ENVPE2=toto ENVPE3=OU=Users\,OU=bimbo ENVDC1=
+ echo 'compose: ENVSE1= ENVSE2= ENVSE3= ENVPE1=OU=Users,OU=bimbo ENVPE2=toto ENVPE3=OU=Users\,OU=bimbo ENVDC1='

With relative path volumes enabled
+ printenv
ENVDC1=OU=Users,OU=bimbo
HOSTNAME=0b6e73749495
SHLVL=1
HOME=/root
ENVPE1=OU=Users
ENVPE2=toto
ENVPE3=OU=Users,OU=bimbo
ENVSE1=coucou
ENVSE2=OU=Users,OU=bimbo
ENVSE3=extra
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
compose: ENVSE1= ENVSE2= ENVSE3= ENVPE1=OU=Users ENVPE2=toto ENVPE3=OU=Users,OU=bimbo ENVDC1=
+ echo 'compose: ENVSE1= ENVSE2= ENVSE3= ENVPE1=OU=Users ENVPE2=toto ENVPE3=OU=Users,OU=bimbo ENVDC1='

With relative path volumes disabled

There are no variables defined in the stack.env repository file that are displayed on the echo command
The 3 PE environment variables appear in the service environment but they are not displayed on the echo command

With relative path volumes enabled

All three variable defined in the stack.env file appear in the container environment but not on the echo command
The ENVPE2 and ENVPE3 variable appear correctly on the echo command and on the container environment however the ENVPE1 env variable is truncated after the first comma.

Conclusion

the stack.env variables never appear as compose env variables.  Is this by design or is this a bug?
When enabling relative path volumes, the environment variables defined in the portainer UI are truncated after the first comma.  This is a problem.

Questions

is there a significance to the filename stack.env?  Or could I define in the repository any file and use a matching filename in the env_file directive?

It was my understanding that the env_file makes the composer env available but that only the ones in the environment definition should be created for the service.

No, anything in the file referenced by env_file will be available for the service. env_file is just another way to provide env vars in a more organized way than a bunch of individual definitions under environment.

Thanks for the response.  Can you look at my post 25 minutes ago (15:20 my time)

Thanks for the response. Can you look at my post 25 minutes ago (15:20 my time)

Yep, looking through it now - it's a bit more to process so I wanted to get an initial reply out first.

Just my 2 cents, it would be great if the compose environment could be loaded from a file similar to how it works wen you type:
docker compose up and if the current folder contains a .env file then the compose command will have available all of the environment defined in that file.  It would be great to have it so that you could specify an option in portainer so you could use a file called .env.staging or .env.test when you deploy your stack from the repository.  This would provide the very valuable benefit of not having to change the compose file when using a different environment file.  I would be willing to help you with developing this if you wanted.

One last thing related to one of my questions.  I now recall the portainer significance of the name stack.env.  If I specify in my compose file env_file: - stack.env then this will add to my service all of the environments defined in the portainer envrionment setup in the UI without having to type it all.  Am I correct or has this been superseeded?

the stack.env variables never appear as compose env variables. Is this by design or is this a bug?

For your echo commands, it's worth noting that the interpolation of ${VAR} style placeholders is performed at run time, so the values may not be available when you might expect them to be. If for example I take our first basic stack (purely for readability) and use the compose CLI to create it, you'll see it throw warnings, and as a result the behavior is the same as you see through Portainer:
root@be-docker:~/test-env-cli# cat docker-compose.yml
services:
  main-initialize:
    image: alpine:latest
    env_file:
      - stack.env
    environment:
      - env1=${env1}
    entrypoint: ["/bin/sh", "-c"]
    command: ["echo env1=${env1}"]

root@be-docker:~/test-env-cli# cat stack.env
env1=toto

root@be-docker:~/test-env-cli# docker compose up -d
WARN[0000] The "env1" variable is not set. Defaulting to a blank string.
WARN[0000] The "env1" variable is not set. Defaulting to a blank string.
[+] Running 1/1
 ✔ Container test-env-cli-main-initialize-1  Started                                                                                0.3s

root@be-docker:~/test-env-cli# docker logs 92651c4271c6
env1=
root@be-docker:~/test-env-cli#

When enabling relative path volumes, the environment variables defined in the portainer UI are truncated after the first comma. This is a problem.

Yes, this looks like it might indeed be a bug. I note that if you escape the comma (as you did with ENVPE3) that the comma is included, so that's a workaround for now. Let me chat with the team around this as to our expected behavior here.

is there a significance to the filename stack.env? Or could I define in the repository any file and use a matching filename in the env_file directive?

As it looked like you have since determined, this is for merging the UI definitions with those in the file. In our documentation we say:

Alternatively, you can add stack.env as an env_file definition to add all the environment variables that you have defined individually as well as those included in an uploaded .env file:

So this will combine variables set within the stack.env file with those that are set using the environment variable fields in the Portainer UI and make them all available within the service.

I took your idea and I found another problem.  I updated the repo to add a .env that mimics the portainer UI env setup and now I run the following:
root@server1:/volume1/nasshare/website/test-stack-env# docker-compose up
WARN[0000] The "ENVSE1" variable is not set. Defaulting to a blank string.
WARN[0000] The "ENVSE2" variable is not set. Defaulting to a blank string.
WARN[0000] The "ENVSE3" variable is not set. Defaulting to a blank string.
WARN[0000] The "ENVDC1" variable is not set. Defaulting to a blank string.
[+] Running 1/1
 ⠿ Container test-stack-env-main-initialize-1  Recreated                                                           1.9s
Attaching to test-stack-env-main-initialize-1
test-stack-env-main-initialize-1  | + printenv
test-stack-env-main-initialize-1  | + echo 'compose: ENVSE1= ENVSE2= ENVSE3= ENVPE1=OU=Users,OU=bimbo ENVPE2=toto ENVPE3=OU=Users\,OU=bimbo ENVDC1='
test-stack-env-main-initialize-1  | ENVDC1=OU=Users,OU=bimbo
test-stack-env-main-initialize-1  | HOSTNAME=d7fb2e5dbb50
test-stack-env-main-initialize-1  | SHLVL=1
test-stack-env-main-initialize-1  | HOME=/root
test-stack-env-main-initialize-1  | ENVPE1=OU=Users,OU=bimbo
test-stack-env-main-initialize-1  | ENVPE2=toto
test-stack-env-main-initialize-1  | ENVPE3=OU=Users\,OU=bimbo
test-stack-env-main-initialize-1  | ENVSE3=extra
test-stack-env-main-initialize-1  | PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
test-stack-env-main-initialize-1  | PWD=/
test-stack-env-main-initialize-1  | compose: ENVSE1= ENVSE2= ENVSE3= ENVPE1=OU=Users,OU=bimbo ENVPE2=toto ENVPE3=OU=Users\,OU=bimbo ENVDC1=
test-stack-env-main-initialize-1 exited with code 0

The difference is that ENVSE3 from the stack.env displays since it is not overriden to a blank value in this docker-compose example but in the case where the relative path volumes is disabled it does not appear.  That is another bug IMHO.

The difference is that ENVSE3 from the stack.env displays since it is not overriden to a blank value in this docker-compose example but in the case where the relative path volumes is disabled it does not appear. That is another bug IMHO.

With relative path volumes disabled, Portainer only has the compose file to work with, nothing else. Therefore, anything defined in the stack.env file will not be included. This is why we built the relative path volume feature - so that if your compose relies on additional files, they can be referenced.

There is another side effect of adding the .env to the repo, it appears that internally when you have relateive path volumes enabled that portainer will run a docker compose in the folder defined by local filesystem path which now includes a .env file which is now picked up by the docker-compose. If you remove all portainer UI PE variables you will see that the PE environment variables are all there due to this .env file. I can only speculate about the reasons but I definitely see the effect.

Yes, this is expected for the same reason as above. If relative path volumes are enabled, we use the path as the working directory (so that you can reference files relatively). When relative path volumes is not enabled, the working directory contains only the compose file.
We go into a bit more depth as to how the relative path volume feature works in our documentation.

With relative path volumes disabled, Portainer only has the compose file to work with, nothing else. Therefore, anything defined in the stack.env file will not be included. This is why we built the relative path volume feature - so that if your compose relies on additional files, they can be referenced.

Although I understand what you are saying here, in the case when relative path volumes are disabled, Portainer behaves differently than the docker-compose command works since the use of an env_file directive requires a file at that path when using docker command whereas such a file is not required in the case of portainer.  I would say that if env_file is used, portainer should require the relative path volumes to be enabled.

Although I understand what you are saying here, in the case when relative path volumes are disabled, Portainer behaves differently than the docker-compose command works since the use of an env_file directive requires a file at that path when using docker command whereas such a file is not required in the case of portainer. I would say that if env_file is used, portainer should require the relative path volumes to be enabled.

That would require us to parse the compose file for the use of the env_file directive, which if the file is on Git requires we first check it out, then parse it, then throw the error, at which point the deployment would have already begun (in order to pull it from Git).
You could also argue that we should do this for any usage of a relative path within a compose file, not just for a env_file setting. Essentially, we make the assumption that if someone is deploying from a compose file, they're aware of what is required by it in terms of external file references.

That would require us to parse the compose file for the use of the env_file directive, which if the file is on Git requires we first check it out, then parse it, then throw the error, at which point the deployment would have already begun (in order to pull it from Git). While it's not impossible to do, it's a fair amount of complicated work to achieve this behavior.

Not sure I agree about the parsing part.  If you checkout the docker-compose.yml without the file referenced by an env_file directive, an error has to be thrown since this is what docker-compose will do.  You would just need to handle that error and report it the usual portainer way.  I am truly puzzled how you can deploy a compose file that references an env_file that you do not have available.
Perhaps the solutions is to always do the relative path volumes processing under the hood.  Maybe the local filesystem path could be set it a portainer global settings.

I would be available if you wanted to talk about this if you wish. My offer still holds about helping to fix this if you want.

Not sure I agree about the parsing part. If you checkout the docker-compose.yml without the file referenced by an env_file directive, an error has to be thrown since this is what docker-compose will do. You would just need to handle that error and report it the usual portainer way. I am truly puzzled how you can deploy a compose file that references an env_file that you do not have available.

When relative path volumes is enabled, we use a helper container that spins up temporarily in order to do the cloning etc required. I suspect (though I am not a developer myself) that when not using this feature, we internally suppress the error message that is returned when a referenced file is missing. I'll have to check with the team on that. I'm also aware that we're in the middle of reworking how we process compose files internally, so there might be some changes incoming as a result of that.

Perhaps the solutions is to always do the relative path volumes processing under the hood. Maybe the local filesystem path could be set it a portainer global settings.

There are some technical limitations (as well as backward compatibility concerns for existing users) around rolling this out as default at the moment, though it's conceivable we may look at doing this down the line.

You are not a developer?  You could have fooled me!  Thanks for all the help!

Not officially anymore, but I have a background as one so I can call on a bit of past knowledge when necessary :)
Thanks for your feedback through this - it's been helpful to identify a couple of issues as well as clarify how systems work for both you and future users that might stumble across the issue. I'll update here once I learn more about the issues raised.

Also doesn't work when using the web editor.

Also doesn't work when using the web editor.

Please open a separate issue if you are experiencing problems with stack.env when using the Web editor - this issue is specifically focused around the use with repository deployments and to avoid confusion, a separate issue is better.

I am also grappling with this.
I'm on BE 2.21.5. I have a docker-compose and a stack.env file in the root of a repository and I'm using this to create a stack.
What I want to be able to do is specify all my config in the stack.env and then optionally override certain variables using the environment variables defined in portainer. This would be very useful for providing simple defaults, and to avoid adding secrets into git.
However when deploying a stack from git it seems that any value provided in the stack.env cannot be overridden, unless you also specify it in the environments: section of the docker compose - which seems somewhat redundant and also requires a modification to the docker-compose file if I wish to override new variables.
If I have this, then the values in the stack.env is always used, no matter what I do in the portainer UI:
# docker-compose.yml
...
    env_file:
      - stack.env

If I do this, then the value supplied in portainer is used and must be present. It will not fall back to a value in the stack.env file without modifying the docker compose file
# docker-compose.yml
...
    environment:
      - SERVER_ADDR=${SERVER_ADDR}

Is this how it's expected to work? The UI seems to lead you in a different direction - one that would be more useful if it worked!
The docs on stack.env is somewhat light...
https://www.portainer.io/blog/using-env-files-in-stacks-with-portainer
and
https://docs.portainer.io/user/docker/stacks/add#environment-variables


first commit

I have added python files for gesture control mouse , please review it and merge it.

Okay , I'll change this, This wasn't final files , this was my daily work , Still the documentation part is remaining and all files are also yet to add.

Do I need to add .ipynb files ? @sanjay-kv

Do I need to add .ipynb files ? @sanjay-kv

yes

Okay I'll add that.


Add a geometry identifier to WCSimRootGeom

It'll be useful for an identifier of which geometry was used in WCSimRootGeom, so that in output files this information is easily accessible. I see a couple of obvious ways to do this:

Add a string data member (e.g. the same strings used for /WCSim/WCgeom)
Add an enumeration of detectors

Let me know what method you prefer and I can add it in. Personally, I prefer the first method, as it's easier to specify different versions of the same geometry (if this is something that happens?), etc.
This is required for hyperk/hk-BONSAI#2

Adding a string sounds reasonable. Do you have any preference @cvilelasbu? We had talked about adding something like this in to properly interface with fiTQun.

I've just had a thought - having all the run options (geometry, noise, DAQ, particle gun / input vector file, ...) stored in the output file would be useful. Perhaps we could add a new tree with all this information in?

Sorry, just rediscovering this now. Does this increase the file size much? Or the time to run the program?

Also, can I assign you this issue?

Also just rediscovering this. It'll be a tree with 1 entry, with 20-30 leaves. So it'll be negligible in terms of file size. Running should be quick too - it's just a matter of calling 20-30 Get*() methods in EndOfRunAction(). Go ahead & assign me, if you think this is a sensible solution.


fix(Icon 50): fixed inherit variant of icon by removing fill attr in svg files

We're looking forward to seeing this feature released. The current b2b-icon-50 icons don't look great.

Is there anybody who's checking this PR?

Hallo @AnnaHoege, doesn't the icon snapshots change when they are modified?


Terraform-runner container states

I wonder if it would be a good idea to use different containers for the different tasks. With different containers, the logic around the state of the deployment can probably be handled by the operator using container exit codes.

Starting a design proposal page for this here: https://github.com/isaaguilar/terraform-operator/blob/feature/terraform-runner-container-states/docs/container-states.md

The main scope of the redesign has been accomplished which was to split up init/plan/apply and other scripts into pods that the controller is aware of and can act on. In addition, persistent volumes were introduced which may pave a way of more advanced workflows in the future.
One current struggle is getting around the container image requirements. Not sure I'll figure this out anytime soon. For now I'll continue not modifying the scripts workflow runners execute.


osmo-nitb + osmo-sip-connector DTMF question

Hi,
I'm using osmo-nitb + osmo-sip-connector on the BSC side and nanoBTS on the BTS side. Do you know if osmo-nitb supports DTMF and how can I enable it?
Looking at the code, I can see only some DTMF defines.
Thanks,
Stefan

@smititelu I don't know. Try asking this question on OpenBSC mailing list: https://lists.osmocom.org/mailman/listinfo/openbsc
There was a very old discussion about DTMF there: http://lists.osmocom.org/pipermail/openbsc/2009-September/001917.html
I don't if there were changes since then. Ask on the mailing list.


Cleanup: fix fatal error when registering node

The extra leading / causes fatal error when registering nodes. This PR fixes it.
Signed-off-by: Chanwit Kaewkasi<EMAIL_ADDRESS>

LGTM


broken links

Hello, I tried to access this link but couldn't:
https://github.com/gmh5225/NeacSafe-Analysis

Unfortunately. it was broken.


doc(InputUnmarshaller): add info that scala's scalars include map values

please review 🙏
Motivation
This PR is part of the series that aims to make Apollo federation possible in Sangria, and it comes as a response to the json as scalar support, federation issue discussed here.
Changes
This PR updates the scaladoc of the InputUnmarshaller getScalaScalarValue function, by making explicit that map values can be returned as scala's scalars too.

me and @yanns found a way to make federation possible for Sangria without having to make this change, the implementation :) can be found here


Stream filtering on subscriptions page (resolves #565)

This is additional to PR #684. It provides filtering on the subscriptions page.
Rebased and reviewed #711:

fixed functionality and tests for the initial commits,
added a clear error message for trying to create duplicate streams.

Automated message from Dropbox CLA bot
@trueskawka, thanks for the pull request! It looks like you haven't yet signed the Dropbox CLA. Please sign it here.

Automated message from Dropbox CLA bot
@trueskawka, thanks for signing the CLA!

Bumping for review.

I've redone the tests and made sure the input fields don't use autocomplete.
Should I work on anything else?

This looks great!  I want to look again in the morning since it's way past my bedtime, so a couple small requests:

Can you line-wrap the commit message for the second commit?  If you run git log you'll see how we do it.
Can you tag this as fixing the issues it fixes?

Check out the Zulip commit message guidelines here for more details: https://zulip.readthedocs.io/en/latest/version-control.html#commit-messages

Sure!
Name the second one stream_creation, since it has to do with changes connected to filtering, but is actually changing just the modal window in the subscriptions view. Hope that's ok.

Merged, thanks @trueskawka!  I made a couple small tweaks while merging this:
(1) Changed the commit message to auto-close the two issues that this resolves, including one of our major roadmap items :).
(2) Fixed the fact that the placeholder for stream filtering was missing translation tags (and fixed our linter to catch this issue while I was at it).
Huge thanks to @trueskawka, @mjec, and @disissid for building this!

Thank you :)


[release-1.8] Fix namespace isn't resolved correctly in VirtualService delegation

This is an automated cherry-pick of #30423

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
3e76b09e1ea9aa2a836c3cfe3fe2ca87862cc567
link
/test unit-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
3e76b09e1ea9aa2a836c3cfe3fe2ca87862cc567
link
/test unit-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
3e76b09e1ea9aa2a836c3cfe3fe2ca87862cc567
link
/test unit-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
3e76b09e1ea9aa2a836c3cfe3fe2ca87862cc567
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.8
3e76b09e1ea9aa2a836c3cfe3fe2ca87862cc567
link
/test unit-tests_istio_release-1.8

integ-telemetry-mc-k8s-tests_istio_release-1.8
3e76b09e1ea9aa2a836c3cfe3fe2ca87862cc567
link
/test integ-telemetry-mc-k8s-tests_istio_release-1.8

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest


[Bug]: When specifing custom namespace for ingress (traefik) controller, hanging waiting for deployment

Description
Hi there, first of all thank you for this amazing project and support.
In short, if you specify this:
ingress_target_namespace = "something"
The resources are created correctly BUT, during the terraform provisioning, this step fails:
 Error: remote-exec provisioner error
│
│   with module.kube-hetzner.null_resource.kustomization,
│   on .terraform/modules/kube-hetzner/init.tf line 288, in resource "null_resource" "kustomization":
│  288:   provisioner "remote-exec" {
│
│ error executing "/tmp/terraform_1183884130.sh": Process exited with status 124

Because this part of the script:
kubectl apply -k /var/post_install
echo 'Waiting for the system-upgrade-controller deployment to become available...'
kubectl -n system-upgrade wait --for=condition=available --timeout=360s deployment/system-upgrade-controller
sleep 7
kubectl -n system-upgrade apply -f /var/post_install/plans.yaml
timeout 360 bash <<EOF
until [ -n "\$(kubectl get -n traefik service/traefik --output=jsonpath='{.status.loadBalancer.ingress[0].ip}' 2> /dev/null)" ]; do
    echo "Waiting for load-balancer to get an IP..."
    sleep 2
done
EOF

Is doing this:
kubectl get -n traefik service/traefik
which has the classic "traefik" namespace hardcoded.
Unfortunately I'm not familiar with this custom terraform templates, so excuse me if I don't provide a PR for this.
Rregards
Rob
Kube.tf file
ingress_controller = "traefik"
ingress_target_namespace = "infra"

Screenshots
No response
Platform
WSL

@childotg Really appreciate you finding this sneaky bug, it was fixed in v2.11.5. Enjoy!


Remove explicit line endings setting from .editorconfig

Description
I recently added end_of_line = lf to .editorconfig for completeness, but we found that this sometimes results in the following pop-up in Visual Studio on Windows:

The reason is that the default git-windows installation converts \n to \r\n on fetch. Which is okay, because it converts back when pushing to the server.
While the problem goes away by unchecking "Always show this dialog", I'm removing this to avoid the barrier for new contributors. Modern editors can handle different line endings fine, so this is mostly a concern from the past.
Though I've seen failing test assertions on multi-line strings on different OSes, but that's easy to work around.
Quality checklist

[ ] Your code complies with our Coding Style.
[ ] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

/azp run Steeltoe.All


nix not compatible with freebsd 13

ext field needs to be added to kevent data structure and functions.
error[E0063]: missing field `ext` in initializer of `kevent`
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/nix-0.22.2/src/sys/event.rs:221:26
    |
221 |         KEvent { kevent: libc::kevent {
    |                          ^^^^^^^^^^^^ missing `ext`

For more information about this error, try `rustc --explain E0063`.
error: could not compile `nix` due to previous error

I was able to fix it for my usecase but unsure how you'd implement it in  nix for varying bsd versions.
Our hack to make I compile:
impl KEvent {
    pub fn new(ident: uintptr_t, filter: EventFilter, flags: EventFlag,
               fflags:FilterFlag, data: intptr_t, udata: intptr_t) -> KEvent {
        KEvent { kevent: libc::kevent {
            ident,
            filter: filter as type_of_event_filter,
            flags: flags.bits(),
            fflags: fflags.bits(),
            data: data as type_of_data,
            udata: udata as type_of_udata,
            ext: [0,0,0,0],       //this is likely bad but we are not using this part of nix
        } }
    }

It's a libc bug.  I'm trying to get it fixed here https://github.com/rust-lang/libc/pull/2585 .


avoid printing unnecessary parentheses for ChainExpression inside LogicalExpression

#7326
#7325  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


ENH: scatter_matrix doesn't handle columns with dtype 'pd.Categorical' or any other non-numeric

I understand that object dtype supporting couldn't be the right option, but it is quite feasible to implement support for Categorical.
Right now, all columns of 'DataFrame' which aren't numeric are dropped before visualization procedure of scatter_matrix.

Scatter plots often don't work well with categoricals, since you'll possibly end up with a overlappinig points.
Have you seen seaborn's Pairgrid? You're probably better off using that and splitting your categorical by hue.

Thanks for the link, Tom! To be honest, in my task there are several Categorical's, so both approaches have own pro's and con's.
I just wonder if is it in Pandas interest to maintain existing visualization tools.

With several categoricals, things are even harder. A scatter plot of categorical vs. categorical would just have (at most) 1 point per pair. In these case's I'll usually facet by the categorial with seaborn's FacetGrid.

I just wonder if is it in Pandas interest to maintain existing visualization tools.

Maintain yes, but no plans to expand them. Libraries like seaborn do a better job.

OK, clear!
Thank you for the directions, Tom!


Add initial documentation for Java-based packages

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?

Per the discussion at https://github.com/Homebrew/discussions/discussions/910, this PR adds a "Homebrew and Java" page that documents the use of openjdk or versioned alternatives by Java-based packages, as well as the ability to bring your own JDK by means of the JAVA_HOME environment variable.

Great start! We should probably talk about the macOS system Java wrappers in /usr/bin/java, /usr/bin/javac, and /usr/libexec/java_home. Our openjdk formulae say this in their caveats:
For the system Java wrappers to find this JDK, symlink it with
  sudo ln -sfn /usr/local/opt/openjdk/libexec/openjdk.jdk /Library/Java/JavaVirtualMachines/openjdk.jdk

We should repeat the guidance here and point out that this will enable these system Java wrappers to function properly when running e.g. java from the Terminal or when double-clicking a .jar file from Finder to avoid these sorts of errors:
% java
The operation couldn’t be completed. Unable to locate a Java Runtime.
Please visit http://www.java.com for information on installing Java.

Since /usr/libexec/java_home is deprecated by Apple, let's avoid dragging that documentation in.

Where do you see that /usr/libexec/java_home is deprecated by Apple? I note that it's actually been updated in Big Sur. We just don't use it internally in Homebrew anymore because we have other solutions that work better for us.

Okay, I swear I read that during the Big Sur beta cycles. I can't find it anymore so I guess I was wrong.
But since it's functionally equivalent to setting $JAVA_HOME now, it might still be good to keep it out of the documentation since $JAVA_HOME is the cross-platform standard.

Since /usr/libexec/java_home is deprecated by Apple, let's avoid dragging that documentation in.

Apologies @SMillerDev that I didn't see this discussion until after I had already worked on adding the relevant documentation, so I pushed the commit anyways. I can amend or reverse it out if that's the consensus.

I ended up adding a blurb about confirming the symlink with /usr/libexec/java_home -V and noticed that the vendor name of the bundle from the openjdk packages is coming through as UNDEFINED. Not sure if that indicates a missing plist entry or what.

I ended up adding a blurb about confirming the symlink with /usr/libexec/java_home -V and noticed that the vendor name of the bundle from the openjdk packages is coming through as UNDEFINED. Not sure if that indicates a missing plist entry or what.

It appears the way to fix the UNDEFINED would be to set --with-vendor-name in openjdk.rb when building the JDK. Also, looking at openjdk.rb, I think it would make sense to have the bundle directory names exactly match the Homebrew package names. Right now, both openjdk and openjdk@8 call the directory openjdk.jdk leading to slightly divergent symlinking instructions between the two packages, but if openjdk@8 used the name<EMAIL_ADDRESS>instead, the symlinking instructions could be the same for all OpenJDK packages:
% sudo ln -sfn $(brew --prefix $OPENJDK)/libexec/$OPENJDK.jdk /Library/Java/JavaVirtualMachines/

I'm not sure if that would work. Java is kinda finicky about it's paths. Could you test it and make a pull request if it does?

I'm not sure if that would work. Java is kinda finicky about it's paths. Could you test it and make a pull request if it does?

Not sure that what would work? A link with @ in the name or something else?

Not sure that what would work? A symlink with @ in the name or something else?

We'll, Java after that. But if you tested this I guess it's fine.

if openjdk@8 used the name<EMAIL_ADDRESS>instead,

Makes sense, but will break existing symlinks when people brew upgrade, and potentially any formulae where we install a script that sets JAVA_HOME to this.
It's doable but probably not worth the effort.


Serialport installed and everything updated

Pushed all versions to latest and migrated to the official serialport package instead of your custom one.
Made usb-detection a standard dependency (it's obviously required).
Added package-lock.json to the .gitignore so it doesn't interfere with apm install. Also removed screenshots from it because I had made a mistake earlier.
Fixed my troubleshooting section

Confirmed working on Windows 10 and the latest version of Arch Linux.
This closes #55, closes #52, closes #43, closes #39, closes #41, closes #32, and closes #30.
This patch also makes the package somewhat of a rolling release, so it should function until a major update to one of the dependencies takes it out, in which case its dependency version can be updated to lock it in a state just before breaking.

@Sorunome How is the review going?

I'm sorry, it got lost into my flood of IRL stuff! I reviewed and tested it now, it looks amazing! Time to push it to apm packaging stuffs~!