Updates the LSP Error messages in the health and workload output

…as worklaod apply and create output
Pull request

What this PR does / why we need it
PR updates the workload apply and create output error message as well as tanzu apps lsp health command error output to display Reasons and Messages instead of Error and Errors respectively.
Which issue(s) this PR fixes

Fixes #550
Describe testing done for PR

Additional information or special notes for your reviewer

Since the code for generating error messages based on response error codes are reused between tanzu apps workload commands as well as tanzu apps lsp health command, product agreed to change  the message that are common for both commands .
Example :-
lsp health command output
user_has_permission: true
reachable: true
upstream_authenticated: false
overall_health: false
message: |-
  Local source proxy was unable to authenticate against the target registry.
  Errors:
  - GET https://gcr.io/v2/token?scope=repository:kshaheer-playground/lsp:pull,push&service=gcr.io: UNAUTHORIZED: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication

has been changed to
user_has_permission: true
reachable: true
upstream_authenticated: false
overall_health: false
message: |-
  Local source proxy was unable to authenticate against the target registry.
  Messages:
  - GET https://gcr.io/v2/token?scope=repository:kshaheer-playground/lsp:pull,push&service=gcr.io: UNAUTHORIZED: You don't have the needed permissions to perform this operation, and you may have invalid credentials. To authenticate your request, follow the steps in: https://cloud.google.com/container-registry/docs/advanced-authentication

Similarly Tanzu apps workload create and apply error output has been changed from
Error: Local source proxy is not installed or the deployment is not healthy. Either install it or use --source-image flag
Error: Local source proxy is not installed on the cluster.
Errors:
- services "local-source-proxy" not found

to
Error:  Local source proxy is not installed or the deployment is not healthy. Either install it or use --source-image flag
Reason: Local source proxy is not installed on the cluster.
Messages:
- services "local-source-proxy" not found


[Tests] fix gitlab migration testdata

it looks like env GITLAB_READ_TOKEN is not set or CI would fail all the time :O

Codecov Report

Merging #12693 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #12693   +/-   ##
=======================================
  Coverage   43.32%   43.32%
=======================================
  Files         645      645
  Lines       71527    71527
=======================================
  Hits        30988    30988
- Misses      35521    35522    +1
+ Partials     5018     5017    -1

Impacted Files
Coverage Δ

modules/queue/workerpool.go
58.77% <0.00%> (-1.23%)
:arrow_down:

services/pull/pull.go
41.57% <0.00%> (-0.47%)
:arrow_down:

modules/git/blame.go
77.19% <0.00%> (+1.75%)
:arrow_up:

modules/process/manager.go
75.00% <0.00%> (+2.50%)
:arrow_up:

modules/indexer/stats/queue.go
64.70% <0.00%> (+11.76%)
:arrow_up:

Continue to review full report at Codecov.

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

this pull is included in #12695

Please resolve conflicts

Closing as already merged than

Didn't thought the other one will go in so quick - thats why I splitted the fix and the enhancement


ratelimit incoming RPCs

I'm not sure how seriously the new limits will affect the gateway on main-net, so I'm going to be trying it out today. We should also run an antfarm with this update to make sure that peers can still function normally, send transactions, etc.

The test I pushed is failing, but seems like more muxado issues and not a result of anything in the gateway code. I've also tested this code in production to confirm that everything works.
Will be good to switch away from muxado asap. I think we'll see a lot of issues disappear upon doing so.

Is this good to merge then? Or will it cause future builds to fail? If so, we can wrap it in a t.Skip("skipped until muxado is dropped") or something.

Yeah. Assuming the build passes this should be good to merge.

looks like ndf build failure, but otherwise lgtm


all requested permutations of polyfill.min.js no longer contain code, just a block comment.

Type: Bug? Outage?
What

Some time between june 17th and june 20th 202 according to the internet archive history... 'https://polyfill.io/v3/polyfill.min.js?features=Intl', 'https://polyfill.io/v3/polyfill.min.js?version=3.48.0', 'https://polyfill.io/v3/polyfill.min.js?version=3.52.1&features=es7%2Ces6', and several other versions i tried... stopped containing actual code, and now instead contains a single block comment. Was this intentional? Where would I sub for notifications to changes like this? and if intentional, at that point, why not 404 or return some other error code instead of an http success returning an empty script?

Hi @oneeyedziggy, the last deployment was in May. Nothing should have changed between the dates you have mentioned. Could you please post the full user-agent string of the browser which is making the polyfill.io request please?
I have a suspicion that the browser which is making the request does not need any polyfills and that is why we are serving an empty script file (containing only a comment)

"Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0" for the above, and
for https://polyfill.io/v3/polyfill.min.js?version=3.52.1 only, the same happens w/
chrome 83 win 7
Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36
chrome 83 osx
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36
firefox 77 osx
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:77.0) Gecko/20100101 Firefox/77.0
safari 13 osx
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Safari/605.1.15
chrome 83 android
Mozilla/5.0 (Linux; Android 8.0.0; SM-G935V) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.106 Mobile Safari/537.36
I'm starting to see this might be a feature... The only places i do get a response w/ more than a block comment is firefox 68 on android
Mozilla/5.0 (Android 8.0.0; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0
and
Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
( I forgot I even had internet explorer... as everyone should, I don't think i knew it can't even navigate to javascript files... it tries to download them... but when it does, this one contains code. )

so... is the idea, the code is only sent to browsers you expect will need it? The response changing based on who's asking...

so... is the idea, the code is only sent to browsers you expect will need it? The response changing based on who's asking...

That is the exact idea, yes :-) polyfill.io is a service which accepts a request for a set of browser features and returns only the polyfills that are needed by the requesting browser.

k, thanks. That answers my main issue, as the dev who inherited the requesting code, I was trying to inspect contents from MY browser, not the oldest one I could find, and was expecting it to return what was requested w/o trying to be clever. Probably one of the first things stated in the docs had i bothered to read them :), though not your problem, I could see other devs checking, seeing a placebo script w/ no functional code, and pulling it from their project.
Might be worth checking what internet archive's UA is and maintain consistency for it, as the response to them changed last week. That's the main way I was able to confirm this script wasn't ALWAYS empty. I use it to check historical states of public scripts, especially when behavior changes unexpectedly.

hey guys, AWESEOME project! <3
I was perplexed for a second as well, but I figured it out... still: what I would recommend instead of writing:

No polyfills found for current settings

I would write:

No polyfills needed for current settings and browser

@Jossnaz excellent suggestion :-) I'll make a pull-request for that 👍

@Jossnaz here it is -- https://github.com/Financial-Times/polyfill-library/pull/763


git commit --verbose

I would like to enable verbosity on my commit messages without having to go through "Git Plus: Run". I see 2 ways of doing this:

Add a checkbox on the git-plus Settings page that says "Enable verbose commit messages" and modify the "Git Plus: Commit" command to add "--verbose" according to the checkbox.
Create another command "Git Plus: Commit (verbose)" that contains the "--verbose" by default.

If this is not in your plans already, how one could go about adding this functionality? What files would I have to edit / create?
Thanks!

This has been raised before at #90.
In order to implement it, you'll need to change lib/models/git-commit.coffee. This means get the diffs and add them to the the commit file


Import tokenizer from edgedb-rust

I'm not sure do we want to run cargo test from edb test or keep it separately run (I've added it as a separate step for CI).
Also, I'm going to drop edgeql-pytest crate as that tests python bindings which should already have been tested as part of the edgedb tests.
Another point here: I've just put sources here without importing the whole history. Let me know if you think importing history is a good idea.

SHould we rename edgeql-python to something more meaningful? It made sense inside a rust repo, but being inside a predominantly Python repo it makes less sense.

We can. Not sure what the name makes more sense, though.

I'm not sure do we want to run cargo test from edb test or keep it separately run (I've added it as a separate step for CI).

Would it be possible to test the rust code entirely with Python?

Would it be possible to test the rust code entirely with Python?

This doesn't make sense for "unit" tests, as there are a little bit more that used from python in lexer (preparser that is used by repl to delimit statements). And unit tests may test smaller internal things not exposed to python at all.

It looks like cargo is able to discover packages in subfolders too, as long as Cargo.toml of the workspace is in the root folder.
So we can put them somewhere in edb/edgeql-parser and edb/edgeql-rust ? Given that:

Python module called edb._edgeql_rust (and we can't put it deeper, i.e. more dots in the path, because of some limitations in cpython crate).
For edgeql-parser it's important to keep folder name same as crate name, so that the structure doesn't look weird (it's not a technical limitation), as we're probably going to publish it on crates.io (marking it as internal implementation) to publish REPL too.

Moved things to edb/edgeql-parser and edb/edgeql-rust


ZPM fails in existing installation

USER>zpm "install deployed-oscript-template"
ERROR! Download module, hash mismatch. 4270ff4a00a046156a40bb9462f46a1202202c79
USER>zpm "ver"
%SYS> zpm 0.7.0
https://pm.community.intersystems.com - 1.0.6

thank you!
Looking into it
On Mon, Apr 22, 2024 at 5:37 PM r-cemper @.***> wrote:

USER>zpm "install deployed-oscript-template"
ERROR! Download module, hash mismatch.
4270ff4a00a046156a40bb9462f46a1202202c79
USER>zpm "ver"
%SYS> zpm 0.7.0
https://pm.community.intersystems.com - 1.0.6
—
Reply to this email directly, view it on GitHub
https://github.com/evshvarov/deployed-code-template/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVHEP33FMIXKIG4JD3Y4BDY6U4C5AVCNFSM6AAAAABGTEC2J2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2TMOJZGM3TEMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

But load.... works  and both sources are visible
USER>zpm "load /home/irisowner/dev/deployed-code/ -v"
Load started on 04/22/2024 16:42:48
Loading file /home/irisowner/dev/deployed-code/module.xml as xml
Imported document: deployed-oscript-template.ZPM
Load finished successfully.
Skipping preload - directory does not exist.
Load started on 04/22/2024 16:42:48
Loading file /home/irisowner/dev/deployed-code/module.xml as xml
Imported document: deployed-oscript-template.ZPM
Load finished successfully.
Loading deployed-oscript-template in process 800
[USER|deployed-oscript-template]        Reload START (/home/irisowner/dev/deployed-code/)
Skipping preload - directory does not exist.
Load of directory started on 04/22/2024 16:42:48 '*'
Loading file /home/irisowner/dev/deployed-code/src/dc/deployed/ObjectScript.cls as udl
Load finished successfully.
Load of directory started on 04/22/2024 16:42:48 '*'
Loading file /home/irisowner/dev/deployed-code/src/dc/withsource/ObjectScript.cls as udl
Load finished successfully.
[USER|deployed-oscript-template]        Reload SUCCESS
[deployed-oscript-template]     Module object refreshed.
[USER|deployed-oscript-template]        Validate START
[USER|deployed-oscript-template]        Validate SUCCESS
[USER|deployed-oscript-template]        Compile START
Compilation started on 04/22/2024 16:42:48 with qualifiers 'd-lck'
Compiling 2 classes
Compiling class dc.deployed.ObjectScript
Compiling class dc.withsource.ObjectScript
Compiling routine dc.deployed.ObjectScript.1
Compiling routine dc.withsource.ObjectScript.1
Compilation finished successfully in 0.016s.
[USER|deployed-oscript-template]        Compile SUCCESS
[USER|deployed-oscript-template]        Activate START
[USER|deployed-oscript-template]        Configure START
[USER|deployed-oscript-template]        Configure SUCCESS
Studio project created/updated: deployed-oscript-template.PRJ
[USER|deployed-oscript-template]        Activate SUCCESS

this is running in my mini-docker image
IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2024.1 (Build 262U) Thu Mar 7 2024 15:36:40 EST

fixed
On Mon, Apr 22, 2024 at 5:51 PM r-cemper @.***> wrote:

this is running in my mini-docker image
IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2024.1 (Build
262U) Thu Mar 7 2024 15:36:40 EST
—
Reply to this email directly, view it on GitHub
https://github.com/evshvarov/deployed-code-template/issues/2#issuecomment-2070209108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVHEP77YQWUKWNGAH56V6DY6U5XTAVCNFSM6AAAAABGTEC2J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZQGIYDSMJQHA
.
You are receiving this because you commented.Message ID:
@.***>

class stays with source until
write $system.OBJ.MakeClassDeployed("dc.deployed.ObjectScript",,1)
SO:  the Deploy param is ignored
<Resource Name="dc.deployed.PKG" Deploy="true"/>

USER>k text do
##class(%Compiler.UDL.TextServices).GetTextAsString($namespace,
"dc.deployed.ObjectScript", .text) w text
Class dc.deployed.ObjectScript
{
ClassMethod Test() As %Status
{
}
}
On Mon, Apr 22, 2024 at 6:19 PM r-cemper @.***> wrote:

class stays with source until
write $system.OBJ.MakeClassDeployed("dc.deployed.ObjectScript",,1)
SO: the Deploy param is ignored

—
Reply to this email directly, view it on GitHub
https://github.com/evshvarov/deployed-code-template/issues/2#issuecomment-2070310279,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVHEPZYWESXK2GWSRVCTWTY6VBDFAVCNFSM6AAAAABGTEC2J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZQGMYTAMRXHE
.
You are receiving this because you commented.Message ID:
@.***>


MySQL Connection Security

Currently, we're using useSSL=false&allowPublicKeyRetrieval=true in the MySQL connector string. This opens for potential vulnerabilities to consider. See https://mysql-net.github.io/MySqlConnector/connection-options/

Can you tell me why those are necessary in the connection string? When testing on Windows, I dont need either of these. What happens when you do not provide those on debian?

I added the latter recently - maybe caused my MySQL 8. Can't remember, I'll retry and give you the error message ;)

MySQL 5.x & Oracle Java 8... OK
MySQL 5.x & Oracle Java 11... OK
MySQL 8.x & OpenJDK... OK
Hmm, weird :S - I guess that useSSL=false was something with the old connector version, and setting that to false required allowPublicKeyRetrieval=true on some of the newer versions. Removing both seems to work all all three combinations above.
Pull request #25 should do the trick...


CodeBlock starting with two spaces makes editor not editable

Describe the bug
CodeBlock starting with two spaces makes editor not editable.
To Reproduce

Input two " " and two "`"
Input one "`"
See error

Expected behavior
Should not have error
Desktop (please complete the following information):

OS: windows 10
Browser chrome
Version 99.0.4844.82

Additional context
Editor version: 3.1.3
Error message:
Uncaught TypeError: Cannot read properties of undefined (reading 'nodeSize')
    at Fragment.nodesBetween (toastui-editor-all.js:3498:52)
    at Node.nodesBetween (toastui-editor-all.js:4490:16)
    at Transaction.Transform.addMark (toastui-editor-all.js:8187:12)
    at toastui-editor-all.js:18488:20
    at Array.forEach (<anonymous>)
    at appendMarkTr (toastui-editor-all.js:18470:11)
    at Plugin.appendTransaction (toastui-editor-all.js:18443:17)
    at EditorState.applyTransaction (toastui-editor-all.js:9651:43)
    at EditorView.dispatchTransaction (toastui-editor-all.js:20558:46)
    at EditorView.dispatch (toastui-editor-all.js:14968:50)

@z-950 I can reproduce it. we'll fix it.

Any updates?


Update game over message

Update the game over message so people know how to play again!

Test Comment


remove black border on mobile, shrink nav bar and org logo for smalle…

Responsive changes:

Removed black border from frame on mobile/tablet.

shrunk nav bar and org logo for screen width devices.

For certain mobile screen sizes, match the contributor card width to the rest of the content's width.

Looks good for me!


Is there a way to point Anonymizer at a directory on your hard drive?

Or do you have to push/pull the data via DICOM transfer via a PACS or something like https://mircwiki.rsna.org/index.php?title=FileSender?

Yes, please refer to the Operation section of the documentation here: https://rsna.github.io/anonymizer/

Thanks, I didn't think to check the "File" menu for importing data because I saw options related to that in other places in the UI.

I suggest that you add buttons for importing from file/directory next to the Query button on the screen that shows stats/progress about the data that's been processed so that all of the import options are displayed together.
I suggest adding a button for an import directory next to where you're collecting information about DICOM servers in the project config screen.
It might also be worth adding the DICOM transfer options to the File menu rather than only showing the local disk import options.  This way people who click that menu will see all available import options rather than a subset.

The software design ensures there is only one location to initiate an action.
The GUI standard for project and file management have been followed, once a project has been configured and opened then files can be imported via the File menu.
The QUERY and EXPORT buttons relate to DICOM network transfers whilst the File/Import options relate to DICOM files on the local file system.


⚠ Bofrost.de has degraded performance

In 5587f40, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1770 ms

Resolved: Bofrost.de performance has improved in a068514 after 7 minutes.


[DOCS] Docs release for 0.14.0

Change Logs
Release notes for 0.14.0
Impact
release notes
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Tested locally!
Attaching screenshots

@prashantwason  please review the PR for Docs release.

Looks good.

Yoo hoo!


VMware.WorkstationPro version 15.5.7

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

dude it is already in the repo

dude it is already merged


rmf_robot_sim_common in rolling fails to build on rhel targets

The package rmf_robot_sim_common in rolling has been detected as not building on all platforms in the buildfile rhel. The release manager for rolling will consider disabling this build if it continues to fail to build.

jenkins_urls:

rhel 8 x86_64
This is being filed because this package is about to be blacklisted. If this ticket is resolved please review whether it can be removed from the blacklist that should cross reference here.

Here is an excerpt from the log of the most recent build:
DEBUG: [ 10%] Building CXX object CMakeFiles/rmf_robot_sim_utils.dir/src/utils.cpp.o
DEBUG: /usr/bin/c++ -DDEFAULT_RMW_IMPLEMENTATION=rmw_cyclonedds_cpp -DRCUTILS_ENABLE_FAULT_INJECTION -Drmf_robot_sim_utils_EXPORTS -I/builddir/build/BUILD/ros-rolling-rmf-robot-sim-common-1.2.0/include -isystem /opt/ros/rolling/include -isystem /usr/lib64/python3.6/site-packages/numpy/core/include -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC -Wall -Wextra -Wpedantic -std=gnu++17 -MD -MT CMakeFiles/rmf_robot_sim_utils.dir/src/utils.cpp.o -MF CMakeFiles/rmf_robot_sim_utils.dir/src/utils.cpp.o.d -o CMakeFiles/rmf_robot_sim_utils.dir/src/utils.cpp.o -c /builddir/build/BUILD/ros-rolling-rmf-robot-sim-common-1.2.0/src/utils.cpp
DEBUG: In file included from /builddir/build/BUILD/ros-rolling-rmf-robot-sim-common-1.2.0/src/utils.cpp:4:
DEBUG: /builddir/build/BUILD/ros-rolling-rmf-robot-sim-common-1.2.0/include/rmf_robot_sim_common/utils.hpp:6:10: fatal error: Eigen/Geometry: No such file or directory
DEBUG:  #include <Eigen/Geometry>
DEBUG:           ^~~~~~~~~~~~~~~~
DEBUG: compilation terminated.
DEBUG: make[2]: *** [CMakeFiles/rmf_robot_sim_utils.dir/build.make:79: CMakeFiles/rmf_robot_sim_utils.dir/src/utils.cpp.o] Error 1
DEBUG: make[2]: Leaving directory '/builddir/build/BUILD/ros-rolling-rmf-robot-sim-common-1.2.0/obj-x86_64-redhat-linux-gnu'
DEBUG: make[1]: Leaving directory '/builddir/build/BUILD/ros-rolling-rmf-robot-sim-common-1.2.0/obj-x86_64-redhat-linux-gnu'
DEBUG: make[1]: *** [CMakeFiles/Makefile2:226: CMakeFiles/rmf_robot_sim_utils.dir/all] Error 2

It seems that the build is also failing on RHEL here: https://build.ros2.org/view/Hsrc_el8/job/Hsrc_el8__rmf_building_map_tools__rhel_8__source/2/
I think that this failure is because of missing gazebo packages because the Gazebo variant isn't building on RHEL.


osslsigncode: 2.3 -> 2.5

Description of changes
Per https://github.com/mtrojnar/osslsigncode/releases/tag/2.5 --

2.5 (2022.08.12)

fixed the Unix executable install path
fixed the hardcoded "pkcs11" engine id
fixed building with MinGW
fixed testing with the python3 distributed with Ubuntu 18.04

2.4 (2022.08.02)

migrated the build system from GNU Autoconf to CMake
added the "-h" option to set the cryptographic hash function for the "attach -signature" and "add" commands
set the default hash function to "sha256"
added the "attach-signature" option to compute and compare the leaf certificate hash for the "add" command
renamed the "-st" option "-time" (the old name is accepted for compatibility)
updated the "-time" option to also set explicit verification time
added the "-ignore-timestamp" option to disable timestamp server signature verification
removed the "-timestamp-expiration" option
fixed several bugs
updated the included documentation
enabled additional compiler/linker hardening options
added CI based on GitHub Actions

Patch incorporated to fix build on darwin submitted upstream as mtrojnar/osslsigncode#246.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.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

[X] Fits CONTRIBUTING.md.

Please open a pull request with the fix in osslsigncode repo and use link to the patch instead of adding patch file to the nixpkgs tree.

Please open a pull request with the fix in the osslsigncode repo and use link to the patch instead of adding patch file to the nixpkgs tree.

Unfortunately, a diff against master and a diff against the 2.5 release aren't quite compatible, so this wouldn't apply.

...I suppose I could fork the upstream repo and create my own 2.5-maint branch; would that be better?

I guess let's leave that as it is and hopefully we can drop the patch once 2.6 is released (and contains the fix).

@prusnak, I added d742e50b2f36832c88699bb71bb6362f8baf5582 to the PR per your feedback, with the intent to squash it before merge. There's a separate branch in my personal repo pointing to the same commit (https://github.com/charles-dyfis-net/osslsigncode/commit/issue-246-v1), so even if upstream requires changes to the patch before it goes to main, the link will remain valid.


Add meaningful string representations for resolution invariants.

During dependency resolution, invariants are enforced for
one-operator-per-package and one-provider-per-api. Their user-facing
string representation (shown when they prevent resolution from
succeeding) had re-used the same representation as constraints on
Subscriptions out of convenience.
Recently, the messaging of Subscription-related constraints was
changed to be more descriptive which inadvertently made the invariant
messaging misleading. This patch improves constraint messaging for all
dependency relationships except bundle dependencies.

/test all

Replaced by #2005


Fails with error 'Only non-capturing groups are accepted: e.g. (?:pattern) instead of (pattern)'

Building and running the current head, the container fails to start with error:
2017/01/18 21:07:08 Starting Portainer on :9000
panic: route /upload/tls/{endpointID}/{certificate:(ca|cert|key)} contains capture groups in its regexp. Only non-capturing groups are accepted: e.g. (?:pattern) instead of (pattern)

goroutine 1 [running]:
panic(0x79aec0, 0xc420251fb0)
        /usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/gorilla/mux.newRouteRegexp(0x840e01, 0x34, 0x0, 0x7fc87d2d0000, 0x0, 0x70)
        /go/src/github.com/gorilla/mux/regexp.go:116 +0xe1b
github.com/gorilla/mux.(*Route).addRegexpMatcher(0xc42025d9d0, 0x840e01, 0x34, 0x0, 0x1, 0xc42025d9d0)
        /go/src/github.com/gorilla/mux/route.go:163 +0xe1
github.com/gorilla/mux.(*Route).Path(0xc42025d9d0, 0x840e01, 0x34, 0x0)
        /go/src/github.com/gorilla/mux/route.go:327 +0x4f
github.com/gorilla/mux.(*Router).Handle(0xc420254be0, 0x840e01, 0x34, 0xa07d00, 0xc420253020, 0xc420250e00)
        /go/src/github.com/gorilla/mux/mux.go:220 +0xf3
github.com/portainer/portainer/http.NewUploadHandler(0xc420221310, 0xc420240a00)
        /go/src/github.com/portainer/portainer/http/upload_handler.go:31 +0x264
github.com/portainer/portainer/http.(*Server).Start(0xc420161220, 0x18, 0xc4201a3e78)
        /go/src/github.com/portainer/portainer/http/server.go:64 +0x267
main.main()
        /src/cmd/portainer/main.go:88 +0x58c

Attached is a Vagrantfile that reproduces this.
Vagrantfile.txt

I've been able to reproduce this, I'll push a fix soon.

This is due to the latest release of gorilla/mux, introduced via https://github.com/gorilla/mux/issues/200
As we don't have the ability to pin go packages in Portainer yet, updates in dependencies may bring issues.


MWPW-142590 - [Share] enhancement (resubmit) - ability to edit text above icons

Resubmitting this PR
This was previously reverted due to an issue found on a live page. This was caused when a share block is authored w/ out a content row.  See LIVE CC example below. (no authoring changes required)

Authors would like to modify the 'Share this page' text that appears above the social icons in the Share block.
Enabled author-able share titles
Updated the twitter logo use new X version

Note: The variant .inline does not support a title and strips out any authored text in the block content.
Resolves: MWPW-142590
Test URLs:
LIVE CC page: https://main--cc--adobecom.hlx.page/creativecloud/animation/discover/principles-of-animation?milolibs=rparrish-share-update
Before: https://main--milo--adobecom.hlx.page/drafts/rparrish/share?martech=off
After: https://rparrish-share-update--milo--adobecom.hlx.page/drafts/rparrish/share?martech=off
Authoring Docs
Before: https://main--milo--adobecom.hlx.page/docs/authoring/examples/share-block?martech=off
After: https://rparrish-share-update--milo--adobecom.hlx.page/docs/authoring/examples/share-block?martech=off
Testing notes: To author a custom title in the Share block, simply add the title in the blocks first content row. Works with or without the custom share url authoring options.

Verified : testing details
https://jira.corp.adobe.com/browse/MWPW-142590
@ryanmparrish before merging please note there are still two checks on the PR that are not passing

Approving and merging to stage as this was already on prod and the issues have been fixed and verified https://github.com/adobecom/milo/pull/2070


Mark docker-compose-search as abandoned

The docker-compose-search use an abandoned registry. For this reason I have updated this entry.

I have created other PR with the right commit, @agebhar1


Node 12 support

Please, raise up gulp version since in doesn't support node v.12
https://github.com/gulpjs/gulp/issues/2324

@kazazor pls

These solutions kind of make sense to me https://stackoverflow.com/questions/55921442/how-to-fix-referenceerror-primordials-is-not-defined-in-node
I'm using Node 14 https://github.com/kazazor/git-pre-commit/issues/3#issuecomment-638419399


Missing Login Actions page

Hi,
The page "login actions" is missing from login pages.
Translations are in i18n files.
Is this planned in a future version of keycloakify ?
TY

Hello @ceadreak,
All the default pages are implemented by Keycloakify.
The pages you're refering to is either one of the pages listed here:
https://storybook.keycloakify.dev/
Or it's a page generated by a Custom Keycloak Extention and in this case you should follow this guide: https://docs.keycloakify.dev/faq-and-help/integration-with-custom-keycloak-extention
Can you send a screenshot of the page in question?
Can you also open the dev tool and in the JavaScript REPL type: kcContext.pageId and tell me what you're getting:

Hi @garronej,
You're right, this is the info.ftl file !
In my case I just need an email verification, so the display is a little bit different because there is only one action

Thank you for the quick answer

Chime in a bit. In my login-actions page, it's pageId is login-idp-link-confirm.ftl


merge package template from Kronos-Tools/npm-package-template-minimal

package.json

chore(devDependencies): update<EMAIL_ADDRESS>from template

Codecov Report

Merging #130 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #130   +/-   ##
=======================================
  Coverage   83.16%   83.16%
=======================================
  Files          11       11
  Lines         594      594
  Branches      181      181
=======================================
  Hits          494      494
  Misses        100      100

Continue to review full report at Codecov.

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


CI: Install btrfs-progs for crio build.

CRI-O on Ubuntu now seems to need not only the "btrfs-tools" package but
now also the "btrfs-progs" package.
Fixes #127.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Yay, and that looks to have built! - thanks @jodh-intel
lgtm

oh, hold on.....
E: Unable to locate package btrfs-progs
Grrr - I'm not on a bunty box right now - guessing you will figure that out... @jodh-intel if you run out of time then one of us will pick this up in a bit

Invalid - travis uses Trusty, which doesn't provide this package.
@grahamwhaley - yes, it's unlikely I'll get a chance to fix this today now, so someone else might want to pick it up.

btrfs-tools seems to be in Trusty though, interesting. https://packages.ubuntu.com/trusty/admin/btrfs-tools

Ah, I know, s/btrfs-progs/btrfs-tools/ !

but we already have btrfs-tools installed (it is in the commit diff already) ...? :-(

And indeed, the file list of btrfs-tools in trusty doesn't have version.h, https://packages.ubuntu.com/trusty/amd64/btrfs-tools/filelist

Maybe the most straightforward way would be to compile a newer btrfs-tools version and install it (system wide)

Just to note, I think this is now fixed with #142 @jodh-intel , so I'll mark this as DNM, and let you close it down if you concur.

Indeed, let's close it.


from_collect not rendering ecr before output

Thanks for the great tool. In the latest version 0.4.3 you added a new method from_collect so that it's possible to add multiple paths to the input of files. However, when using that method, the files are no longer being ecr rendered before output.
require "teeplate"

module Kemalyst::Generator
  class App < Teeplate::FileTree

    @name : String

    def initialize(@name)
    end
  end
end

        puts "Generating App #{name} in #{directory} with #{view_handler}"
        app = App.new(@name)
        app.collect_from "#{__DIR__}/app"
        app.collect_from "#{__DIR__}/views/#{view_handler}/#{template}"
        app.render(directory, list: true)

Results in the following (list shortened to show the relevant files only):
new       bin/sentry.cr.ecr
new       config/session.cr.ecr
new       README.md.ecr
new       shard.yml.ecr
new       src/{{name}}.cr

If done the without using from_collect then it does ecr render the files before output.
require "teeplate"

module Kemalyst::Generator
  class App < Teeplate::FileTree
    directory "#{__DIR__}/app"

    @name : String

    def initialize(@name)
    end
  end
end

        puts "Generating App #{name} in #{directory} with #{view_handler}"
        app = App.new(@name)
        app.render(directory, list: true)

Generating App newapp in ./newapp with slang
new       bin/sentry.cr
new       config/session.cr
new       README.md
new       shard.yml
new       src/newapp.cr

Any pointers?
I want to propose a PR to kemalyst-generator project so the user can choose between slang and ecr view files when generating app, and this new method is perfect if I can get the method working 😉
Many thanks

Unfortunately, Crystal ECR is a bit less flexible than the other languages such as ERB for dynamically parsing and rendering templates. Because we need to statically embed ECR templates into our source code in compile time. (ECR is very fast instead.)
I'd like to support more languages in the future version but it may be not soon.

Thanks for the quick reply, much appreciated :) I'll do some more research to see if I can work around it.


Crash at run on 3D image

Describe the bug
Crash during the run
(error message reminds me of the error message on #2 )
To Reproduce
Create a fresh environment and run on the linked image
Napari log =>
17:47:38 : INFO : MainThread : Predicting with (1, 6, 7, 1) tiles
INFO:spotiflow.model.spotiflow:Normalizing...
17:47:38 : INFO : MainThread : Normalizing...
INFO:spotiflow.model.spotiflow:Padding to shape (128, 896, 960, 1)
17:47:40 : INFO : MainThread : Padding to shape (128, 896, 960, 1)
/home/herber0000/miniconda3/envs/spotiflow/lib/python3.11/site-packages/spotiflow/utils/utils.py:587: RuntimeWarning: invalid value encountered in divide!

         [0.     ],
         [0.     ]]]], dtype=float32), (slice(0, 128, None), slice(128, 224, None), slice(128, 224, None), slice(0, 1, None)), (slice(0, 128, None), slice(608, 704, None), slice(320, 416, None), slice(0, 1, None)))
        iter_tiles = <generator object plugin_wrapper.<locals>.plugin.<locals>.progress.<locals>._progress at 0x7bfd210f9d40>
    993     tile, s_src, s_dst = item
    994     if isinstance(tile, da.Array):

File ~/miniconda3/envs/spotiflow/lib/python3.11/site-packages/napari_spotiflow/_dock_widget.py:253, in plugin_wrapper.<locals>.plugin.<locals>.progress.<locals>._progress(it=<generator object tile_iterator.<locals>._accumulate>, **kwargs={})
    251 for item in it:
    252     yield item
--> 253     progress_bar.increment(1)
        progress_bar = ProgressBar(value=<function match_type.<locals>.<lambda> at 0x7bfcb5f8b9c0>, annotation=<class 'magicgui.widgets.ProgressBar'>, name='progress_bar')
    254     app.process_events()
    255 app.process_events()

File ~/miniconda3/envs/spotiflow/lib/python3.11/site-packages/magicgui/widgets/_concrete.py:235, in ProgressBar.increment(self=ProgressBar(value=<function match_type.<locals>....icgui.widgets.ProgressBar'>, name='progress_bar'), val=1)
    233 def increment(self, val: float | None = None) -> None:
    234     """Increase current value by step size, or provided value."""
--> 235     self.value = self.get_value() + (val if val is not None else self.step)
        self = ProgressBar(value=<function match_type.<locals>.<lambda> at 0x7bfcb5f8b9c0>, annotation=<class 'magicgui.widgets.ProgressBar'>, name='progress_bar')
        val is not None = True
        val = 1

File ~/miniconda3/envs/spotiflow/lib/python3.11/site-packages/magicgui/widgets/bases/_ranged_widget.py:125, in RangedWidget.value(self=ProgressBar(value=<function match_type.<locals>....icgui.widgets.ProgressBar'>, name='progress_bar'), value=43)
    123 val: tuple[float, ...] = value if isinstance(value, tuple) else (value,)
    124 if any(float(v) < self.min or float(v) > self.max for v in val):
--> 125     raise ValueError(
        value = 43
        self = ProgressBar(value=<function match_type.<locals>.<lambda> at 0x7bfcb5f8b9c0>, annotation=<class 'magicgui.widgets.ProgressBar'>, name='progress_bar')
    126         f"value {value} is outside of the allowed range: "
    127         f"({self.min}, {self.max})"
    128     )
    129 ValueWidget.value.fset(self, value)

EmitLoopError:

While emitting signal 'magicgui.widgets.PushButton.changed', a ValueError occurred in a callback:

  Signal emitted at: /home/herber0000/miniconda3/envs/spotiflow/lib/python3.11/site-packages/magicgui/widgets/bases/_value_widget.py:71, in _on_value_change
    >  self.changed.emit(value)

  Callback error at: /home/herber0000/miniconda3/envs/spotiflow/lib/python3.11/site-packages/magicgui/widgets/bases/_ranged_widget.py:125, in value
    >  raise ValueError(

    Local variables:
       value = 43
       val = (43,)

See ValueError above for original traceback.

Environment (please complete the following information):

Spotiflow version: [0.5.0]
napari-spotiflow version: [0.3.3]
Conda/mamba version (if applicable): [conda 24.7.1]
OS: [Ubuntu]
OS version: [Ubuntu 24.04]
GPU memory (if applicable): GTX 1080 - 8192MiB
napari version: [0.5.4]
python version: 3.11.10

Additional context
The plugin runs with the sample images (2D Hybiss and Synth3D), but crashes with a 3D image of 951*882 pixels * 120 z slices. Dataset is here if it can be useful :) https://drive.switch.ch/index.php/s/a9CS1XXHVPFExJH

Hi!
Thanks for the quick feedback!
It all worked smoothly after I understood that I was missing a local g++ install :)
Results are looking promising for the moment. I wanted to run a quick test before the SwissBIAS workshop next week, I'll be happy to discuss the results with you!


Publish scripts to get addresses and verify merkle root

https://github.com/celo-org/merkle-distributor/pull/10


Dark Mode added.

I have successfully added Dark Mode for the website. You can see the screenshots below for reference.

I kindly request you to accept my pull request.

@PiyushKalyanpy  I request you to authorize my pull request.

Please fix the issues and use zinc instead of gray for dark mode ( so that it should not give a blue shade )


Look up latest zig binary url from version index

The install script broke, as the currently referred to version 0.14.0-dev.42+17f14e1d6 is returning a 404 (at least for x86_64 linux), but Zig offers an index in the form of a JSON: https://ziglang.org/download/index.json. It's mentioned on their download page, so I would assume the format of it should be stable.
It looks up the master dev build, as that is what this package was using before.

Thank you for the contribution! Kind regards @frjonsen


dangerouslySetInnerHTML usage in  breaks style plugins

I'm afraid I don't have enough context on how dangerouslySetInnerHTML was used in combination with <head>. Can you share more context?

<head dangerouslySetInnerHTML={{ __html: "<script>console.log(1);</script>" }} />

Thanks for sharing more context. I see, that's the expected behavior. Setting dangerouslySetInnerHTML basically says: "Replace all of this elements content with the HTML string". It's the same thing as if you'd set .innerHTML on an HTML element directly. The way the .innerHTML property works is that it discards any child nodes present before and overwrites it with the passed HTML string.

What is your recommendation to add arbitrary code to the head based on string-based config? Parse the HTML and convert it to JSX elements on the fly?

I provided some quick code here: https://github.com/denoland/fresh/discussions/2360#discussioncomment-8813171
You might have to expand to other tags (eg link) depending on your use-case, but I really think it's going to be a better strategy overall to have tight control over the HTML you are writing rather than "dangerous" injection of code.

I have multiple things: some comments, a <noscript>, and a <script>. I think I better inject it in the middleware by interfering with the response stream through a custom ReadableStream impl.


[BUG] could not serialize access due to concurrent update

Describe the bug
Some items failure to serialize and throw a 500 error on browsing
Internal Server Error: /api/part/category/tree/
Traceback (most recent call last):
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update

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

Traceback (most recent call last):
  File "/home/inventree/.local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/utils/deprecation.py", line 119, in __call__
    response = self.process_response(request, response)
  File "/home/inventree/.local/lib/python3.9/site-packages/user_sessions/middleware.py", line 56, in process_response
    request.session.save()
  File "/home/inventree/.local/lib/python3.9/site-packages/user_sessions/backends/db.py", line 81, in save
    obj.save(force_insert=must_create, using=using)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/base.py", line 739, in save
    self.save_base(using=using, force_insert=force_insert,
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/base.py", line 776, in save_base
    updated = self._save_table(
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/base.py", line 858, in _save_table
    updated = self._do_update(base_qs, using, pk_val, values, update_fields,
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/base.py", line 912, in _do_update
    return filtered._update(values) > 0
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/query.py", line 802, in _update
    return query.get_compiler(self.db).execute_sql(CURSOR)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1559, in execute_sql
    cursor = super().execute_sql(result_type)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1175, in execute_sql
    cursor.execute(sql, params)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/backends/utils.py", line 66, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/inventree/.local/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
django.db.utils.OperationalError: could not serialize access due to concurrent update

Screenshots

Deployment Method

[x] Docker
[ ] Bare Metal

Version Information
# Version Information:
InvenTree-Version: 0.7.0
Django Version: 3.2.13
Commit Hash: 044315a
Commit Date: 2022-05-24
Database: postgresql
Debug-Mode: False
Deployed using Docker: True

Looks like the action i spawned failed :sweat:

@KenwoodFox have you seen this issue multiple times, is it repeatable? I have never seen this issue before, so we need to be able to replicate it :)

On a few parts yeah, i should note also I used kintree to generate the parameters and manufacturer information, via the api.
Im not sure i see a pattern with what parts it seems to affect, ill admit its not super.. consistant, affecing about 1 in 3 page loads for affected parts, and never occuring on some parts.

Just confirmed, it happens with parts created entirely via the web interface, nothing fancy at all.

Did you make any changes during the install process? In particular, did you adjust any database configuration settings?

No i did not, just installed an hour ago, pretty stock stuff, anything i can check?

Nothing that immediately jumps to mind. Please see what else you can find in the logs (if anything). This is a new one!
If you can find any rhyme or reason to which pages the failure occurs on, or any other "common" points of failure, that would be a great start for debugging.

Ill do some sluething! I noticed a log level env variable in the .env file, maybe turning that to DEBUG would be a good place to start?

@KenwoodFox could you check the logs and post us the content of one?

We found the same issue on the demo server. It is connected to the serialize setting in your setup (only if you use Postgres).
As we did not here back for more then 2 weeks I am closing this now. Feel free to reopen if you want to add anything @KenwoodFox

Sorry about the delay, glad to hear that it shows up somewhere, its just a settings issue then? Is that a fix or, should i work on making a PR, iirc i do use postgres.

@KenwoodFox this is expected behaviour by Postgres and Django; Read more here and set the setting in your config.yaml accordingly
https://docs.djangoproject.com/en/dev/ref/databases/#isolation-level

@matmair given that this is explicitly the default behaviour (in settings.py) for a postgres DB I don't think it is correct for us to close this out. Either we change the default behaviour (breaking change) or work out how to handle such errors

@SchrodingersGat I am not sure in what straight forward way one should handle this error. There would be a lot to take into account and edge cases to consider will crop up for a long time in production if we start fiddling this low in the stack.
My recommendation is to switch the default behaviour. My guess is that the majority of admins do not even know this setting is there - this only matters on huge, cached instances.
Let's add  a breaking release note so the few using it can reconfigure.

So this is the solution, and its expected behavior? I guess thats good for me but i would agree with @matmair that this is weird, i had a stock install, and followed all the docs and still eneded up with an error that did not make sense or lead me to know what tp add to the config.yaml, setting it as default makes sense to me?

@KenwoodFox the default will lead to not reproducible API results in some corner cases. That is why it is setup that way currently.


Staff Commands

Ban,Kick,Unban,Purge commands, Xcyth will do Mute and unmute

I don't think we need ban and kick, maybe vote kick but not normal kick. (normal kick for helpers)

I don't think we need ban and kick, maybe vote kick but not normal kick. (normal kick for helpers)

+1


runtime error

hi im getting this issue
any idea what could be causing this ?
Thank you!

hello, unfortunately I've never encountered this issue before so I don't have a quick way to solve it.
my guess is that something external is forcibly killing the python process right as it starts up. may be windows defender or other antivirus. you could try disabling them and see if that helps
other than that, you could:

restart your pc
make sure you're running the run.bat as admin
install dependencies from the requirements.txt file to make sure you have them on versions that are proven to work
reinstall python

has any of that helped?

This error is fixed in the newest version of the script (tested with Python 3.12) ! 🎉
Just make sure to install every Python module with `pip install -r requirements.txt".
Let me know is it working for you! 🙂


Togglable left click option for teleport items

Is your feature request related to a problem? Please describe.
Accidental left clicks a one-click teleport can be frustrating. For players willing to mitigate that risk in favour of the extra time required to right click it, it would be nice
Describe the solution you'd like
Players should be able to swap use/teleport (tablets, ectophail, seed pod) for left click options if they are willing. Similar to how the ancient tablets work
Additional context
Add any other context or screenshots about the feature request here.

@raiyni This may be a good candidate for your Menu Swapper Extended plugin?

I've been discussing it with people, yes

8944eb9be6d62ec8384e29484dab14c4c2858d9d was added to master, which sufficiently covers this use case.


Jenkins losing connection to GCE VM / GCE VM shutting down

Jenkins and plugins versions report

Environment

Jenkins: 2.452.1
OS: Linux - 5.10.0-22-amd64
Java: 17.0.11 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
PrioritySorter:5.1.0
adoptopenjdk:1.5
amazon-ecs:1.49
ansicolor:1.0.4
ant:497.v94e7d9fffa_b_9
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
apache-httpcomponents-client-5-api:5.3.1-1.0
asm-api:9.7-33.v4d23ef79fcc8
authentication-tokens:1.113.v81215a_241826
aws-credentials:231.v08a_59f17d742
aws-java-sdk:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-api-gateway:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-autoscaling:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-cloudformation:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-cloudfront:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-codebuild:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-codedeploy:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-ec2:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-ecr:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-ecs:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-efs:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-elasticbeanstalk:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-elasticloadbalancingv2:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-iam:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-kinesis:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-lambda:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-logs:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-minimal:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-organizations:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-secretsmanager:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-sns:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-sqs:1.12.696-451.v0651a_da_9ca_ec
aws-java-sdk-ssm:1.12.696-451.v0651a_da_9ca_ec
basic-branch-build-strategies:81.v05e333931c7d
blueocean:1.27.12
blueocean-autofavorite:1.2.5
blueocean-bitbucket-pipeline:1.27.12
blueocean-commons:1.27.12
blueocean-config:1.27.12
blueocean-core-js:1.27.12
blueocean-dashboard:1.27.12
blueocean-display-url:2.4.2
blueocean-events:1.27.12
blueocean-git-pipeline:1.27.12
blueocean-github-pipeline:1.27.12
blueocean-i18n:1.27.12
blueocean-jira:1.27.12
blueocean-jwt:1.27.12
blueocean-personalization:1.27.12
blueocean-pipeline-api-impl:1.27.12
blueocean-pipeline-editor:1.27.12
blueocean-pipeline-scm-api:1.27.12
blueocean-rest:1.27.12
blueocean-rest-impl:1.27.12
blueocean-web:1.27.12
bootstrap5-api:5.3.3-1
bouncycastle-api:<IP_ADDRESS>.1-233.vfdcdeb_0a_08a_a_
branch-api:2.1169.va_f810c56e895
browserstack-integration:1.2.13
build-name-setter:2.4.2
build-timeout:1.32
caffeine-api:3.1.8-133.v17b_1ff2e0599
checks-api:2.2.0
cloud-stats:336.v788e4055508b_
cloudbees-bitbucket-branch-source:886.v44cf5e4ecec5
cloudbees-disk-usage-simple:203.v3f46a_7462b_1a_
cloudbees-folder:6.928.v7c780211d66e
cobertura:1.17
code-coverage-api:4.99.0
command-launcher:107.v773860566e2e
commons-httpclient3-api:3.1-3
commons-lang3-api:3.13.0-62.v7d18e55f51e2
commons-text-api:1.11.0-109.vfe16c66636eb_
conditional-buildstep:1.4.3
config-file-provider:973.vb_a_80ecb_9a_4d0
configuration-as-code:1810.v9b_c30a_249a_4c
copyartifact:722.v0662a_9b_e22a_c
coverage:1.14.0
credentials:1337.v60b_d7b_c7b_c9f
credentials-binding:677.vdc9d38cb_254d
dashboard-view:2.508.va_74654f026d1
data-tables-api:2.0.7-1
dependency-check-jenkins-plugin:5.5.0
dependency-track:4.3.1
display-url-api:2.204.vf6fddd8a_8b_e9
docker-commons:439.va_3cb_0a_6a_fb_29
docker-compose-build-step:1.0
docker-java-api:3.3.4-86.v39b_a_5ede342c
docker-plugin:1.6.1
docker-slaves:1.0.7
docker-workflow:580.vc0c340686b_54
durable-task:555.v6802fe0f0b_82
echarts-api:5.5.0-1
email-ext:1814.v404722f34263
embeddable-build-status:487.va_0ef04c898a_2
envinject:2.908.v66a_774b_31d93
envinject-api:1.199.v3ce31253ed13
extended-read-permission:53.v6499940139e5
external-monitor-job:215.v2e88e894db_f8
favorite:2.208.v91d65b_7792a_c
file-operations:214.v2e7dc7f25757
font-awesome-api:6.5.2-1
forensics-api:2.4.0
git:5.2.2
git-client:4.7.0
git-server:126.v0d945d8d2b_39
github:1.39.0
github-api:1.318-461.v7a_c09c9fa_d63
github-branch-source:1789.v5b_0c0cea_18c3
gitlab-api:5.3.0-91.v1f9a_fda_d654f
gitlab-branch-source:704.vc7f1202d7e14
gitlab-plugin:1.8.1
google-compute-engine:4.563.vfa_446a_7e00a_d
google-oauth-plugin:1.330.vf5e86021cb_ec
google-play-android-publisher:4.2
gradle:2.12
gson-api:2.11.0-41.v019fcf6125dc
h2-api:<IP_ADDRESS>-30.v1c64e772f3a_c
handy-uri-templates-2-api:2.1.8-30.v7e777411b_148
htmlpublisher:1.34
http_request:1.18
instance-identity:185.v303dc7c645f9
ionicons-api:74.v93d5eb_813d5f
jackson2-api:2.17.0-379.v02de8ec9f64c
jacoco:3.3.6
jakarta-activation-api:2.1.3-1
jakarta-mail-api:2.1.3-1
javadoc:243.vb_b_503b_b_45537
javax-activation-api:1.2.0-7
javax-mail-api:1.6.2-10
jaxb:2.3.9-1
jdk-tool:73.vddf737284550
jenkins-design-language:1.27.12
jenkins-jira-plugin:4.0.0
jersey2-api:2.42-147.va_28a_44603b_d5
jira:3.13
jira-ext:114.v7b_8b_1d4274c6
jira-steps:2.0.165.v8846cf59f3db
jjwt-api:0.11.5-112.ve82dfb_224b_a_d
jnr-posix-api:3.1.19-2
job-dsl:1.87
job-restrictions:0.8
joda-time-api:2.12.7-29.v5a_b_e3a_82269a_
jquery3-api:3.7.1-2
jsch:0.2.16-86.v42e010d9484b_
json-api:20240303-41.v94e11e6de726
json-path-api:2.9.0-58.v62e3e85b_a_655
junit:1265.v65b_14fa_f12f0
ldap:725.v3cb_b_711b_1a_ef
lockable-resources:1255.vf48745da_35d0
mailer:472.vf7c289a_4b_420
mask-passwords:173.v6a_077a_291eb_5
matrix-auth:3.2.2
matrix-project:830.v7ea_da_561b_a_34
maven-plugin:3.23
mercurial:1260.vdfb_723cdcc81
metrics:4.2.21-451.vd51df8df52ec
mina-sshd-api-common:2.12.1-101.v85b_e08b_780dd
mina-sshd-api-core:2.12.1-101.v85b_e08b_780dd
next-build-number:1.8
nexus-artifact-uploader:2.14
nexus-task-runner:0.9.2
nodejs:1.6.1
oauth-credentials:0.653.v14cf2088e950
okhttp-api:4.11.0-172.vda_da_1feeb_c6e
pam-auth:1.10
parameterized-trigger:806.vf6fff3e28c3e
performance:960.v701db_0d66e1b_
pipeline-aws:1.45
pipeline-build-step:540.vb_e8849e1a_b_d8
pipeline-github-lib:61.v629f2cc41d83
pipeline-graph-analysis:216.vfd8b_ece330ca_
pipeline-groovy-lib:710.v4b_94b_077a_808
pipeline-input-step:495.ve9c153f6067b_
pipeline-maven:1416.v54f125b_3e1c7
pipeline-maven-api:1416.v54f125b_3e1c7
pipeline-milestone-step:119.vdfdc43fc3b_9a_
pipeline-model-api:2.2198.v41dd8ef6dd56
pipeline-model-definition:2.2198.v41dd8ef6dd56
pipeline-model-extensions:2.2198.v41dd8ef6dd56
pipeline-rest-api:2.34
pipeline-stage-step:312.v8cd10304c27a_
pipeline-stage-tags-metadata:2.2198.v41dd8ef6dd56
pipeline-stage-view:2.34
pipeline-utility-steps:2.16.2
plain-credentials:182.v468b_97b_9dcb_8
plot:2.1.12
plugin-util-api:4.1.0
prism-api:1.29.0-15
publish-over:0.22
publish-over-ftp:1.17
publish-over-ssh:1.25
pubsub-light:1.18
rebuild:332.va_1ee476d8f6d
resource-disposer:0.23
run-condition:1.7
s3:466.vf5b_3db_8e3eb_2
scm-api:690.vfc8b_54395023
script-security:1336.vf33a_a_9863911
snakeyaml-api:2.2-111.vc6598e30cc65
snyk-security-scanner:4.0.3
sonar:2.17.2
sse-gateway:1.26
ssh-agent:367.vf9076cd4ee21
ssh-credentials:337.v395d2403ccd4
ssh-slaves:2.966.vea_5112da_0a_a_1
sshd:3.322.v159e91f6a_550
structs:337.v1b_04ea_4df7c8
swarm:3.46
thinBackup:2.0
timestamper:1.27
token-macro:400.v35420b_922dcb_
trilead-api:2.142.v748523a_76693
variant:60.v7290fc0eb_b_cd
view-job-filters:377.v66f4b_796e5fa_
workflow-aggregator:596.v8c21c963d92d
workflow-api:1316.v33eb_726c50b_a_
workflow-basic-steps:1058.vcb_fc1e3a_21a_9
workflow-cps:3894.3896.vca_2c931e7935
workflow-durable-task-step:1353.v1891a_b_01da_18
workflow-job:1400.v7fd111b_ec82f
workflow-multibranch:783.va_6eb_ef636fb_d
workflow-scm-step:427.v4ca_6512e7df1
workflow-step-api:657.v03b_e8115821b_
workflow-support:907.v6713a_ed8a_573
ws-cleanup:0.46

What Operating System are you using (both controller, and any agents involved in the problem)?
Debian 12
Reproduction steps
Use GCP for (oneshot-)agents
Expected Results

build is running
build is completing
agent VM is shutting down

Actual Results

build is running
build is sometimes failing with "Remote call on ... failed. The channel is closing down or has closed down":

[2024-05-28T08:24:30.268Z] Cannot contact gcp-rre-debian12-wrgi83: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@790c3757:gcp-rre-debian12-wrgi83": Remote call on gcp-rre-debian12-wrgi83 failed. The channel is closing down or has closed down
[2024-05-28T08:25:56.170Z] Could not connect to gcp-rre-debian12-wrgi83 to send interrupt signal to process

Anything else?
I'm not sure where to look for this error, not blaming this project by itself but it's very hard to grasp.
We were using Jenkins 2.440.2 with GCE Plugin 4.563.vfa_446a_7e00a_d before without any of these problems. After upgrading to 2.452.1 (including all of the plugins including GCE Plugin (to 4.573.v7dcd6a_37a_ee2) to problems began to start with strange errors like pasted into the actual results.
It did not happen every time, but quite often (maybe 20% yes, 80% no). Rolling back the plugin to 4.563.vfa_446a_7e00a_d (including restarting Jenkins to apply) did not help.
In GCP there are multiple "DELETE" statements for one machine finally resulting in an error but unfortunately I don't know what's "normal" (the usual problem when you look closer at the logs once problems begin to arise):
2024-05-28 10:09:07.764 CEST Compute Engine insert europe-west3-c:gcp-rre-debian12-wrgi83 ...
2024-05-28 10:09:14.732 CEST Compute Engine insert europe-west3-c:gcp-rre-debian12-wrgi83 ...
2024-05-28 10:23:56.154 CEST Compute Engine delete europe-west3-c:gcp-rre-debian12-wrgi83 ...
2024-05-28 10:24:42.072 CEST Compute Engine delete europe-west3-c:gcp-rre-debian12-wrgi83 ...
2024-05-28 10:25:55.799 CEST Compute Engine delete europe-west3-c:gcp-rre-debian12-wrgi83 ...

Are you interested in contributing a fix?
No response

Since the issue is still around even after:

rolling back GCE Plugin to 4.563.vfa_446a_7e00a_d
upgrading to Jenkins 2.452.2 and upgrading all plugins (GCE now at 4.575.v6969b_7c435eb_)

I checked the GCP logs some more. It looks like for whatever reason GCP is receiving an DELETE for the VM while the job is still running.
Here are the logs for a successful jobs (I added the NOTICE/ERROR depending on the icon)
NOTICE 2024-06-18 08:15:15.251 CEST Compute Engine insert europe-west3-c:gcp-rre-unittest-debian12-di1edw ...
NOTICE 2024-06-18 08:15:21.166 CEST Compute Engine insert europe-west3-c:gcp-rre-unittest-debian12-di1edw ...
NOTICE 2024-06-18 08:34:54.780 CEST Compute Engine delete europe-west3-c:gcp-rre-unittest-debian12-di1edw ...
NOTICE 2024-06-18 08:35:40.626 CEST Compute Engine delete europe-west3-c:gcp-rre-unittest-debian12-di1edw ...

and here the logs for a failing job:
NOTICE 2024-06-18 07:46:45.363 CEST Compute Engine insert europe-west3-c:gcp-rre-unittest-debian12-jkt5ag ...
NOTICE 2024-06-18 07:47:00.887 CEST Compute Engine insert europe-west3-c:gcp-rre-unittest-debian12-jkt5ag ...
NOTICE 2024-06-18 08:04:13.367 CEST Compute Engine delete europe-west3-c:gcp-rre-unittest-debian12-jkt5ag ...
NOTICE 2024-06-18 08:04:59.185 CEST Compute Engine delete europe-west3-c:gcp-rre-unittest-debian12-jkt5ag ...
ERROR 2024-06-18 08:05:02.081 CEST Compute Engine delete europe-west3-c:gcp-rre-unittest-debian12-jkt5ag ...

In Jenkins itself it looks like this (note: times are UTC here):
...
[2024-06-18T06:04:43.784Z] PASS src/view/store/tracking/suspendData/tracking.suspend.data.setSuspendDataIfSectionIsVisited.epic.test.ts
[2024-06-18T06:04:44.494Z] Cannot contact gcp-rre-unittest-debian12-jkt5ag: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@1362ebbd:gcp-rre-unittest-debian12-jkt5ag": Remote call on gcp-rre-unittest-debian12-jkt5ag failed. The channel is closing down or has closed down
[2024-06-18T06:05:02.226Z] Could not connect to gcp-rre-unittest-debian12-jkt5ag to send interrupt signal to process

So from my perspective (without much insight) it looks like the delete at 2024-06-18 08:04:13.367 CEST is causing the trouble.  It looks like it sends a delete, GCP is starting to shut down. It loses connection, wants to cleanup (the VMs are configured as "one shot" instances, so it sends another delete at 2024-06-18 08:04:59.185 which then causes the error at 2024-06-18 08:05:02.081 (since the VM is already gone).
I don't know who (which plugin) is responsible for this. Might this GCE plugin even cause this?

Some update. We made the log level more verbose and added a dedicated logger for this.
Looks like the plugin is sometimes "forgetting" about the VM:
Plugin log:
Aug 26, 2024 7:00:46 AM INFO com.google.jenkins.plugins.computeengine.InstanceConfiguration provision
Sent insert request for instance configuration [Debian12 agent for RRE unittests]
Aug 26, 2024 7:00:46 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineComputerLauncher launch
Launch will wait 300000 for operation operation-1724648445057-6208f01ee1a77-f70c6933-7f833c72 to complete...

Aug 26, 2024 7:01:12 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Using autogenerated ssh keypair
Aug 26, 2024 7:01:12 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Authenticating as jenkins
Aug 26, 2024 7:01:12 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
No public address found. Fall back to internal address.
Aug 26, 2024 7:01:12 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Aug 26, 2024 7:01:12 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Failed to connect via ssh: There was a problem while connecting to <IP_ADDRESS>:22
Aug 26, 2024 7:01:12 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Waiting for SSH to come up. Sleeping 5.
Aug 26, 2024 7:01:17 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
No public address found. Fall back to internal address.
Aug 26, 2024 7:01:17 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Connecting to <IP_ADDRESS> on port 22, with timeout 10000.
Aug 26, 2024 7:01:17 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Connected via SSH.
Aug 26, 2024 7:01:17 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Verifying: java -fullversion
Aug 26, 2024 7:01:18 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Copying agent.jar to: /tmp
Aug 26, 2024 7:01:18 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud log
Launching Jenkins agent via plugin SSH: java -jar /tmp/agent.jar
Aug 26, 2024 7:01:26 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud lambda$getPlannedNodeFuture$0
40479ms elapsed waiting for node gcp-rre-unittest-debian12-xqphpu to connect
Aug 26, 2024 7:04:12 AM INFO com.google.jenkins.plugins.computeengine.CleanLostNodesWork terminateInstance
Remote instance gcp-rre-unittest-debian12-xqphpu not found locally, removing it

At the same time the VM was doing work:
...
07:02:21  Agent: gcp-rre-unittest-debian12-xqphpu
...
07:03:22  + yarn run test:ci
07:03:22  yarn run v1.22.22
07:03:22  $ yarn generate && craco test --coverage
07:03:22  $ yarn dependency test && yarn create-plugin-list && yarn create-view-model && yarn create-template-list && yarn create-themes && yarn bundle-messages
07:03:22  $ cross-env TS_NODE_PROJECT=./tsconfig.buildConf.json node -r ts-node/register build-config/dependency.ts test
07:03:25  Successfully checked view/edit dependencies array in package.json.
07:03:25  $ cross-env TS_NODE_PROJECT=./tsconfig.buildConf.json node -r ts-node/register build-config/createPluginList.ts
07:03:27  $ cross-env TS_NODE_PROJECT=./tsconfig.buildConf.json node -r ts-node/register build-config/createViewModel.ts
07:03:30  $ cross-env TS_NODE_PROJECT=./tsconfig.buildConf.json node -r ts-node/register build-config/createTemplateList.ts
07:03:32  $ cross-env TS_NODE_PROJECT=./tsconfig.buildConf.json node -r ts-node/register build-config/createThemes.ts
07:04:56  Cannot contact gcp-rre-unittest-debian12-xqphpu: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@70fb0402:gcp-rre-unittest-debian12-xqphpu": Remote call on gcp-rre-unittest-debian12-xqphpu failed. The channel is closing down or has closed down
07:05:02  Agent gcp-rre-unittest-debian12-xqphpu was deleted; cancelling node body
07:05:02  Could not connect to gcp-rre-unittest-debian12-xqphpu to send interrupt signal to process

@j-koehler  Is it possible that you have several Cloud configured with the same <instanceId>...</instanceId> ? You may run a groovy script like the following to double check on this from the Manage Jenkins > Script Console:
import com.google.jenkins.plugins.computeengine.ComputeEngineCloud
import jenkins.model.Jenkins

jenkins.model.Jenkins.get().clouds.findAll {cloud -> cloud instanceof com.google.jenkins.plugins.computeengine.ComputeEngineCloud }.each { cloud ->
    println "- cloud: " + cloud.cloudName;
	println "  instanceId: " + cloud.instanceId;
    println "  instanceConfigurations:"
    cloud.configurations.each { configuration ->
      println "  - namePrefix:" + configuration.namePrefix
      println "    jenkins_cloud_id: " + configuration.googleLabels["jenkins_cloud_id"]
    }
}
return

This is something I recently discovered in an environment showing the same symptoms.
This can be quite possible if for example you use configuration as code to define your GCE cloud, and for example copy/paste a configuration over to add additional ones..


Unable to run: RuntimeError: module compiled against API version 0x10 but this version of numpy is 0xf

Hi!
I want to try handprint but I'm unable to get it to run.
The command I'm trying to run is
handprint -s google ./

Binary version (1.6.0 from the releases page): reports Python too old even tough my python version should be up to date:

python3 --version
Python 3.10.8

pipx version: gives the error above:

RuntimeError: module compiled against API version 0x10 but this version of numpy is 0xf
An error occurred (ImportError): numpy.core.multiarray failed to import

pip version, installed via pip install --no-cache-dir --upgrade handprint gives the same error.

Something I'm doing wrong?
Env
OS: Arch Linux (Manjaro)
Python: Python 3.10.8
Python 3.10.8 (main, Nov  1 2022, 14:18:21) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.version.version
'1.22.2'
>>>

Thanks for your report. Regarding the Python issue, is there a chance another version of Python installed on your system? When the binary version of Handprint runs, it may be getting a different shell command search path, and if that path includes different version of Python, that would explain the error.
The numpy version is very odd. I'll have to ty to reproduce it somehow.


[DCOS-53415] Use 1.8.0 now that it's out and SNAPSHOT is gone

@porridge lets also revert https://github.com/mesosphere/dcos-commons/pull/2998/files#diff-c197962302397baf3a4cc36463dce5eaR50

@porridge lets also revert https://github.com/mesosphere/dcos-commons/pull/2998/files#diff-c197962302397baf3a4cc36463dce5eaR50

Agreed, but let's do it in a followup cleanup PR. I'd prefer not do delay this one by restarting all the tests, since half of the company is soon going to be blocked on this one.

FWIW, infinity/helloworld/strict failure looks like an unrelated flake.


0.8.0 Missing max range

Describe the issue
The attribute bmw_max_range aka max_range_electric in cli has a null value.
BMW i3 120
Expected behavior
It always used to show max_range
Which Home Assistant version are you using?
core 2021.11.4
What was the last working version of Home Assistant Core?
No response
What is your region?
Rest of world
ConnectedDrive website

[X] I can still successfully login to the BMW ConnectedDrive website and the car status is available there.
[X] I have ConnectedDrive enabled for my vehicle.

Number of cars

[X] I have 2 or more cars linked to the ConnectedDrive account.
[ ] I have a Mini vehicle linked to my account.

Output of bimmer_connected fingerprint
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

bmw_max range is local to me; it's template that converts sensor.i3_120_max_range_electric from km to miles.
Sorry if I confused you.

Are you using the custom component from https://github.com/bimmerconnected/ha_custom_component?
If yes, please provide a fingerprint and check if you can find a matching value. I think it is not available anymore.
If not using the custom component, you have to wait for a HA update or use the custom component until then as BMW changed their API.

Yes, custom component.  fingerprints is a new thing to me.  I can't see anything that looks like max-range in the json output. I'm not bothered if it's not there it's just I noticed.
vehicles_v2_bmw_0.txt

Then it is unfortunately not support by the new API anymore.


Calculate various value distributions in ClinVar data model

The number of distinct ways the variants can be represented in ClinVar data is quite large. There are different aspects of phasing, representation (genotype sets vs. measure sets; single measure in a set vs. multiple measures), variant types, and variation linking to other variation. To make sense of that, and to process data in a meaningful way, we need to describe all possible combinations, their abundancies, and make decisions on how to proceed.
Tracked in JIRA-2069.

After discussions with @AsierGonzalez, expanded the scope of this ticket to also calculate distributions of:

Clinical significance levels
Star rating
Mode of inheritance


Running inference over .tif in tf_od_predict.py

Can I run inference over the image tiles which is in .tif format?
Thank you. I look forward to hear from you.
Best,
Suman

@Geo-Trackers, yes, you can run the inference over the image tile, and the main script is this line. You can replace .jpg with .tif.


Missing Alertmanager endpoint

What did you do?
Instantiated a Prometheus TPR with AlertingSpec
What did you expect to see?
An Alertmanager endpoint listed on the Prometheus /status page
What did you see instead? Under which circumstances?
No Alertmanager endpoint
Environment

Kubernetes version information:
Helm v2.2.1, Kubernetes v1.5.3

Manifests:

apiVersion: monitoring.coreos.com/v1alpha1
kind: Prometheus
metadata:
  labels:
    app: prometheus
    chart: prometheus-0.6.0-1
    heritage: Tiller
    prometheus: youthful-leopard
    release: youthful-leopard
  name: youthful-leopard
  namespace: monitoring
spec:
  alerting:
    alertmanagers:
    - name: precise-salamander-alertmanager
      namespace: monitoring
      port: 9093
      scheme: http
  baseImage: quay.io/prometheus/prometheus
  externalUrl: http://prom-test.aws.opsgoodness.net
  paused: false
  replicas: 1
  resources: {}
  retention: 24h
  routePrefix: /
  storage:
    class: standard
    resources:
      requests:
        storage: 16Gi
  version: v1.5.2

The youthful-leopard ConfigMap is created, but it's empty:
apiVersion: v1
data:
  prometheus.yaml: ""
kind: ConfigMap
metadata:
  name: prometheus-youthful-leopard
  namespace: monitoring

Looks like if no serviceMonitorSelector is specified, the AlertingSpec is ignored and an empty ConfigMap created.

That is indeed the currently expected behavior. When serviceMonitorSelector is not specified, then the Prometheus Operator will allow you to specify your own custom config without generating it for you. It does create an empty file/ConfigMap because we require one to be mounted.
I am open to changing this behavior to maybe only not generate a config if serviceMonitorSelector is not specified and the list of Alertmanager Endpoints is empty. Does that sound more reasonable?

That does seem more reasonable, but (now that I think about it more) probably not very useful. Is there a use case (beyond testing) for a Prometheus instance that only has an Alertmanager configured, and no SD or other config? I suspect not. Only came up for me while developing the Helm chart.

Yes that was my thought as well. I guess it just needs proper documentation for now, and if anyone can come up with a viable use case then I'm more than happy to add it.


AppRaven 2.0 TestFlight

Hi! I am the developer of AppRaven, a price tracker and app discovery network for iOS with over 100k registered users. I would love to share a link to the TestFlight of AppRaven 2.0, the biggest update yet! Could it be featured on your site?
https://testflight.apple.com/join/8uVQrfHu

done


(chore) - warn about missing preact-render-to-string dependency

When preact-render-to-string, preact-compat/server throws a cryptic error.
This is meant to solve that by wrapping the require it with try catch.
Fixes: https://github.com/developit/preact/issues/1601
Will try and do some more in-depth testing if this can result in erroneous errors but I don't think so.

Coverage remained the same at 100.0% when pulling f4b568669ea7b652b46111a3bc68b941ad6fe2cf on chore/warnMissingDep into 8444dd443e483fb4a22ec9c6fe4964bcfee4b184 on master.


[Hack-together] Incorrect Monthly Pricing

Are you accessing the project from the GitHub Codespaces?

[ ] No, I am running the project on my local machine (I will fill in the OS section below)
[X ] Yes, I am using GitHub Codespaces.

Note: The project is optimized to run on Codespaces. We welcome contributions to enhance it for cross-platform local development, but it's not something we will prioritize right now. Thank you!

Describe the bug
The Value for "Real Rent" has been incorrectly swapped with discount
To Reproduce
Steps to reproduce the behavior:
View the card
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

OS (please complete the following information):

OS:
OS Version:
npm version:
Node.js version:
output of azd version:

Additional context
Add any other context about the problem here.

can I take this issue ?

Fixed with #299


Incorrect birth/ death day parsing

For streets named after Virgin Mary, the birth and death dates from her Wikidata entry get incorrectly parsed. The website displays her lifespan as "100-100".
See "Marienplatz" street in Freising

There is indeed an issue.
For the date of birth (P569), I get -0100-00-00T00:00:00Z.
For the date of death (P570), I get +0100-00-00T00:00:00Z.
I probably won't be able to convert that (easily) to "1. century BCE" and "1. century" but it should be "-100 - 100" instead of "100 - 100".
I'll try to fix that.
Thanks for the notice.

Thanks a lot @zorae !
It's now fixed and will be applied to every website during next update (next Thursday for Freising).


Model Configuration page reloads automatically clearing existing entries

Steps to reproduce the problem:

Configure Azure Open AI model provider.
After entering few parameters , I see the page reloads automatically clearing existing entries.

Video showing page reload - https://acorn-io.slack.com/archives/C07P0EZR917/p1734112160336639

This issue is not seen anymore when testing with latest build.


API Review

[ ] obj.id vs. obj[base] vs. obj.__meta vs. obj@foo vs. getSpaceForObject(obj)
[ ] Query/Filter.from
[ ] links/references
[ ] Expando/TypedObject/EchoObject
[ ] Schema (zod/effect)
[ ] Don't export SpaceProxy

echo api notes I have which we should review:

dangling references are not typesafe

e.g., create a folder, add an object, delete that object without removing from the folder, now mapping over that folders items one will be undefined even though the types say otherwise

signals vs multicast observable
signals when deleted
query update fires on object changes
need to make it clearer for people how to subscribe to object changes in non-react model
symbol vs __ vs @ vs fn
include id, __typename, __schema when spreading object?
batch api?
array mutation helpers

const objectIndex = grid.collection.objects.findIndex((object) => object.id === id);
if (objectIndex !== -1) {
  grid.collection.objects.splice(objectIndex, 1);
}

map/record data type
factor out TypedObject to be able to use elsewhere

maybe for providing "typename" to graph datums
makes it simpler for dragging graph datums into ECHO, all serializable datums will "just work" as expandos
potentially replace the thin deepsignal layer with our own proxy layer that we have more control over

creating local-only spaces
creating spaces without identity
looking up spaces by name
integrate ephemeral data feed

We met today and reviewed most of the items listed above. We grouped the issues into two categories:

now, things that should be worked on leading to a 0.5.0 release
later, things that can be added incrementally or are for future consideration

These are listed below and need to be broken out into individual issues.
Now

[x] obj.id (only prop)
[ ] reactive object does not depend on echo [Dima/Yaroslav]
[ ] REVIEW: functions: e.g., getSpaceForObject(obj), metaOf(obj) [Rich/Josiah]

[ ] getSpace()
[ ] getMeta() (keys only?)
[ ] getSchema()
[ ] create(MarkdownDocument, { content: "foo" })
[ ] ref() (async demo)
[ ] EchoObjectSchema (remove Echo from names)
[ ] Expando

[ ] use named imports instead of * as imports [Rich/Josiah]
[ ] schema [Dima/Yaroslav]

[ ] annotations

[ ] queries [Dima/Yaroslav]

[ ] Action: examples
[ ] deleted objects
[ ] graph/traversal
[ ] query update fires on object changes
[ ] need to make it clearer for people how to subscribe to object changes in non-react model

[ ] Don't export internals (e.g., SpaceProxy); review index.ts re-exports [Rich/Josiah]

Later

const Contact = S.struct({ name: S.string() })

//                         FILTER                      ORDER
db.ensureIndex({ typename: Contact.typename }, { firstName: 1, lastName: 1 });
// index key will be 'typename_Contact_firstName_1_lastName_1' or something

db.ensureIndex(Contact, { name: 1 });

// maybe
import { getMutable, isMutable } from '@dxos/client';

const result1 = db.query({ typename: 'Contact' }) // default is mutable
const result2 = db.query({ typename: 'Contact' }, { readonly: true })

const first = result2.objects[0];
console.log(isMutable(first)) // false
const mutable = await getMutable(first);
mutable.foo = 100;

[ ] links/references (strong/weak; RI)
[ ] backlinks?
[ ] halo data store
[ ] integrate ephemeral data feed
[ ] creating local-only spaces
[ ] creating spaces without identity
[ ] deprecate braneframe namespace & migrate typenames (FQ type URIs)

export class DocumentType extends TypedObject({ typename: 'dxos.org/type/Document', version: '0.1.0' })

[ ] managing async boundaries

[ ] remove initialize (improve time-to-useable-client to improve app startup sequence)
[ ] [sdk] space.db.{add|query|remove} should await db ready internally #5407

[ ] signals vs multicast observable
[ ] looking up spaces by name
[ ] query for spaces

all spaces that have these properties
all spaces that have a least one of this schema in them
etc.

[ ] [sdk] wish i could delete with a query #5326
[ ] signals when deleted

// meteor observability api
db.query.observe({
  added(object) {},
  removed(oldObject) {},
  changed(newObject, oldObject) {}
})

// proposed api:
db.query.subscribe(({ added, removed, changed, data }) => {
  //...
  // data is all the new data
})

// btw ^ you can't optimize for "changed only" or "removed only" subscribers unless
// you break up the first argument from single function to map of functions

const query = db.query();

const diffState = createDiffState();

effect(() => {
  const objects = query.objects;
  const { added, removed } = diffState(objects);

  // or
  const { added, removed } = diffState(query.objects);

})

[ ] array mutation helpers

const objectIndex = grid.collection.objects.findIndex((object) => object.id === id);
if (objectIndex !== -1) {
  grid.collection.objects.splice(objectIndex, 1);
}


Cant use boost string inside contract

When I import boost string with:
#include <boost/algorithm/string.hpp>
and try to use the trim method:
boost::algorithm::trim(pet_name);
The code compiles fine but if I try to deploy this contract I receive this error:
cleos set contract monstereosio ../pet
Reading WAST/WASM from ../pet/pet.wasm...
Using already assembled WASM...
Publishing contract...
1469232ms thread-0   main.cpp:2659                 main                 ] Failed with error: Assert Exception (10)
!"unresolvable": env.calloc

Should I assume boost string functions is not supported in contracts?

For the time being boost string functions are not supported, nor are any other libraries that make use of calloc.  This may change eventually, but at present there are no plans to implement calloc.


Result reproducing

Thank you very much for implementing the models, but I have a question. Have you tried to reproduce the results on the datasets from the articles with your models?

In my experiment, some models did not perform well on laptop dataset. If you found some problem of my implementation, please make a Pull Request.


Included inflight messages, take a look if you consider this as an enhancement

 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.


Safely read content from InputStream

Changed to use ByteArrayOutputStream on converting InputStream into byte[], instead of relying on InputStream.available().
The old way may cause problem in cases like reading from buffered input stream or a network stream.

Can one of the admins verify this patch?

@asimshankar Hi, I updated as said in comment, also add a check to decide the byte array output stream init size. Please help reviewing the change again, thanks.

@resec could you resolve the conflicts? Thank you!

@asimshankar conflict resolved, thanks.

@tensorflow-jenkins test this please

fix io exception not caught, not sure if i can trigger jenkins, let me try.
@tensorflow-jenkins test this please

:( can not trigger full testing, please help to trigger the build again, thanks

Thanks @resec! @tensorflow-jenkins test this please.

@asimshankar thanks for the fix :)


One of the female screams is way less loud than the other ones

Haven't yet tried to figure out which one exactly.

In my opinion that scream kinda sucks anyways so in my opinion it can just be removed, but I'm glad to hear opinions.

It's femalescream_3.ogg:
https://user-images.githubusercontent.com/39844191/185245509-d56d828a-351a-45a3-9775-18d3befc7531.mp4
Who screams like this

It is still a little quieter to the ear, but uh, I think its fine and freeeeeeeezeeeeeeee time.


Segmentation fault when running

Click to expand!
Issue Type
Bug
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.11.0
Custom Code
Yes
OS Platform and Distribution
Ubuntu 22.04
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
Segmentation fault

Standalone code to reproduce the issue
import tensorflow as tf
import os
import numpy as np
from tensorflow.python.ops import nn_ops
try:
  arg_0_tensor = tf.random.uniform([3, 30, 50, 3], dtype=tf.float64)
  arg_0 = tf.identity(arg_0_tensor)
  arg_1_0 = 2
  arg_1_1 = 3
  arg_1_2 = 2
  arg_1_3 = 1
  arg_1 = [arg_1_0,arg_1_1,arg_1_2,arg_1_3,]
  arg_2 = True
  arg_3 = True
  seed = 341261001
  out = nn_ops.fractional_avg_pool_v2(arg_0,arg_1,arg_2,arg_3,seed=seed,)
except Exception as e:
  print("Error:"+str(e))

### Relevant log output

```shell
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -978 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -39.2679482 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -7 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -1 [Op:FractionalAvgPool]
Error:Value for attr 'T' of bool is not in the list of allowed values: float, double, int32, int64
	; NodeDef: {{node FractionalAvgPool}}; Op<name=FractionalAvgPool; signature=value:T -> output:T, row_pooling_sequence:int64, col_pooling_sequence:int64; attr=pooling_ratio:list(float),min=4; attr=pseudo_random:bool,default=false; attr=overlapping:bool,default=false; attr=deterministic:bool,default=false; attr=seed:int,default=0; attr=seed2:int,default=0; attr=T:type,allowed=[DT_FLOAT, DT_DOUBLE, DT_INT32, DT_INT64]> [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -1 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -23.2679501 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -1 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -21.5857868 [Op:FractionalAvgPool]
Error:Expected bool for argument 'overlapping' not 'zeros'.
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:Value for attr 'T' of complex128 is not in the list of allowed values: float, double, int32, int64
	; NodeDef: {{node FractionalAvgPool}}; Op<name=FractionalAvgPool; signature=value:T -> output:T, row_pooling_sequence:int64, col_pooling_sequence:int64; attr=pooling_ratio:list(float),min=4; attr=pseudo_random:bool,default=false; attr=overlapping:bool,default=false; attr=deterministic:bool,default=false; attr=seed:int,default=0; attr=seed2:int,default=0; attr=T:type,allowed=[DT_FLOAT, DT_DOUBLE, DT_INT32, DT_INT64]> [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -26.5857868 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -58.5857849 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -63 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -1 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: 0 [Op:FractionalAvgPool]
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} pooling_ratio cannot be smaller than 1, got: -1 [Op:FractionalAvgPool]
Error:Expected bool for argument 'overlapping' not ''.
Error:Expected float for argument 'pooling_ratio' not ''.
Segmentation fault

</details>

Hi @nimashiri !
Thanks for sharing your observation w.r.to  nn_ops
@SuryanarayanaY !
Could you look at this bug.
Sessions are  crashing for both 2.10 and 2.11 and nightly in Colab under GPU environment but giving results under CPU environment.
Thank you!

Tested the code on Ubuntu VM and result is Aborted (core dumped) as attached below.

Tested with similar high level API tf.nn.fractional_avg_pool and observed same behaviour.

With tf-nightly also observed same behaviour.

Also this one:
import tensorflow as tf
import os
import numpy as np
from tensorflow.python.ops import nn_ops
try:
  arg_0_tensor = tf.random.uniform([1, 6, 6, 1], minval=-256, maxval=257, dtype=tf.int64)
  arg_0 = tf.identity(arg_0_tensor)
  arg_1_0 = -1
  arg_1_1 = -30.26794919243112
  arg_1_2 = -21.585786437626904
  arg_1_3 = 1
  arg_1 = [arg_1_0,arg_1_1,arg_1_2,arg_1_3,]
  arg_2 = False
  arg_3 = True
  seed = 341261000
  out = nn_ops.fractional_avg_pool_v2(arg_0,arg_1,arg_2,arg_3,seed=seed,)
except Exception as e:
  print("Error:"+str(e))

I'm having the same issue

@learning-to-play

Hi, In Tensorflow 2.12 it is not showing any segmentation fault, instead it's throwing an error as
Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} Fractional average pooling is not yet supported on the batch nor channel dimension. [Op:FractionalAvgPool] please find the attached Gist here for reference. Thanks!

Hi, In Tensorflow 2.12 it is not showing any segmentation fault, instead it's throwing an error as Error:{{function_node __wrapped__FractionalAvgPool_device_/job:localhost/replica:0/task:0/device:CPU:0}} Fractional average pooling is not yet supported on the batch nor channel dimension. [Op:FractionalAvgPool] please find the attached Gist here for reference. Thanks!

Hi, this bug is shown in 2.11.0 not 2.12.

2.12 has it fixed, so this can be closed


triton test.py creating folder in C:\Users\Username

why triton is creating folder in global location- C:\Users\Username\triton instead of its own local folder inside venv.
if i delete this folder this error is fixed.
ImportError: DLL load failed while importing cuda_utils: The specified module could not be found.
(venv) PS S:\Ai\Visual\StabilityMatrix\Data\Packages\ComfyUI> python test.py
main.c
Creating library main.lib and object main.exp
ptxas info    : 0 bytes gmem
ptxas info    : Compiling entry function 'add_kernel' for 'sm_89'
ptxas info    : Function properties for add_kernel
0 bytes stack frame, 0 bytes spill stores, 0 bytes spill loads
ptxas info    : Used 26 registers, 380 bytes cmem[0]
main.c
this error always appeared whenever i change python version and i have to fix it by removing that folder.

You can set the environment variable TRITON_CACHE_DIR


Clustered Stopped nodes on running nodes

I have 3 nodes all hosted on AWS.
When I run the emqttd_ctl cluster status on each of the I get different result..
Host A output:
Cluster status: [{running_nodes,['HOST B',
                                 'HOST A']},
                 {stopped_nodes,['HOST C']}]

Host C output:
Cluster status: [{running_nodes,['HOST B',
                                 'HOST A',
                                 'HOST C']}]

Host B output:
Cluster status: [{running_nodes,['HOST C',
                                 'HOST B']},
                 {stopped_nodes,['HOST A']}]

On all nodes I ran sudo service emqttd status and got
pong
emqttd is running

The cluster seems to be up and replicating the topics..

Partial network partition or firewall issue between Host A and C. Please try to grep "inconsistent_database event" logs/*  on Host A or C

Output from HOST C
12:31:10.250 [error] Unexpected Info: {mnesia_system_event,{inconsistent_database,running_partitioned_network,'**HOST A**'}}
12:31:10.250 [critical] Mnesia inconsistent_database event: running_partitioned_network, '**HOST A**'
12:31:10.250 [error] Mnesia('**HOST C**'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, '**HOST A**'}
12:31:14.693 [error] Unexpected Info: {mnesia_system_event,{inconsistent_database,running_partitioned_network,'**HOST B**'}}
12:31:14.693 [critical] Mnesia inconsistent_database event: running_partitioned_network, '**HOST B**'
12:31:14.693 [error] Mnesia('**HOST C**'): ** ERROR ** mnesia_event got {inconsistent_database, running_partitioned_network, '**HOST B**'}
07:44:31.680 [error] Mnesia('**HOST C**'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, '**HOST B**'}
07:44:31.680 [error] Mnesia('**HOST C**'): ** ERROR ** mnesia_event got {inconsistent_database, starting_partitioned_network, '**HOST A**'}

@GibliX Are all the nodes in the same VPC?

@emqplus Nope,
They are on different regions..

Additional tests were made.
As I said,
I have 3 servers.
X,Y are in the same region.
Z is on a different region.
X can see that all nodes are running fine (clustered).
Y can see that X is running fine and Z is not stoped.
Z can see that X is running fine and Y is stopped.
When I publish to X, other nodes get the publish replicated.
When I publish to Y it is also replicated to all nodes.
When I publish to Z it also gets published to al nodes.
When I take X down, it leaves me with Y and Z which see each other as stopped.
Now, publishes does not work and does not replicate.
This means that in the first test, X was the bridge between Y and Z and when I took him down, there is no connection between Y and Z.
If I restart the emitted service on Y or Z then they can again see each other (until the next time they stop communicating).
Any conclusions from what I wrote up here?

Any ideas guys?
It's blocking me from using this product :-\

Hi @GibliX ,
The nodes in a cluster must be in a same VPC. Otherwise there could be inconsistency between the nodes.
If you are deploying application over regions please consider using bridge to connect the clusters in different regions.

@zhengyupan If there are only two nodes in different region, how to cluster?

@pantongren Does not support offsite  two nodes clusters.