Add Flappy Bird Game with Modern Design and Animations

This PR introduces a new Flappy Bird game to the project. The game features:
Modern design: A visually appealing aesthetic with clean lines and vibrant colors.
Smooth animations: Fluid animations for the bird's flapping and the pipes' movement.
Intuitive controls: Simple controls to make the bird flap.
Dynamic gameplay: Randomly generated obstacles (pipes) that the bird must navigate.
Scoring system: Tracks the player's score based on the number of pipes passed.

hey man you missed the open-odessy label, please add it. Thank you


Combine panels for Figure 3

We will need to combine the panels for Figure 3 into a single file. The file should be letter size - 8.5 x 11.

Copying this comment here which reflects what should be included in fig. 3 https://github.com/AlexsLemonade/scpca-paper-figures/issues/9#issuecomment-1877733085


MUMUP-2463 : Cleanup images

Cleaned up the images. Big screen max width 600px, small screens 90% width centered.
Added ability of multiple images. Displayed inline block with max width of 400px for big screens, 90% width centered for small
Added little border to screenshots to show definition if white is on a border
Changed the overall width of the <frame-page> white background to be 80% for big screens (98% on a large screen looked silly)

Multiple Images

Single Image md screen

Large screen showing off 80% width centered

Coverage increased (+0.6%) to 35.991% when pulling bf94e449ba7a745e363be4da97c4b28ee704bd3c on cleanup_the_features_page into b51840deea941250349bfe46654d96863d2596fa on master.

:+1:


Unable to type single or double quotes on Sypder Editor (3.6), neither on IPython

Unable to type single or double quotes on Sypder Editor (3.6), neither on IPython
Version and main components

Spyder Version: 3.2.6
Python Version: 3.6.4
Qt Versions: 5.6.2, PyQt5 5.6 on Linux

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
numpy >=1.7      :  1.14.0 (OK)
sphinx >=0.6.6   :  1.6.6 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.11.1 (OK)
psutil >=0.3     :  5.4.3 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.27.3 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.2.1 (OK)
pylint >=0.25    :  1.8.2 (OK)

Thanks for reporting. Please describe in detail the circumstances in which the error occurred, and post the information listed in relevant subsection of the Spyder Troubleshooting Guide as a comment to this issue, and we'll try to help if we can. Otherwise, your issue will likely have to be closed after one week (7 days).
Also, if it occurs again, please reference Spyder Troubleshooting Guide, specifically the Basic First Aid section for some basic steps to try to fix it or at least narrow it down for us. Thanks, and best of luck!

@pedro612xyz It's not clear what you mean, but maybe your system is set up so that single and double quote are used to type accents. If you type ' and then e, you get an é (e with accent). On such systems, you need to type ' and then a space to get a single quote.

@jitseniesen Thanks by the interesting.
On the shell, (bash "GNU bash, version 4.1.2(1)-release (x86_64-redhat-linux-gnu)"),
I can type both ' and ", without problems. Also if I type ' and then e I got é.
However, if I call spyder, from the same shell, I cannot type ' or ", even with the space.

@jitseniesen Let me add two other tests.
If I just call "ipython", thus text mode only, on the shell, that works fine, i.e. I can type ' or ".
However, I've the problem, i.e. not able to type ' or ",  if I call qtconsole, by "jupyter qtconsole", thus I'll be on GUI.
Jupyter QtConsole 4.3.1
Note: On other GUI tools there is no such problem, for instance soffice, firefox, gedit,

@CAM-Gerlach
I have the same problem on Sypder Editor as well.

Hey; did you try the steps listed in the linked sections of the Troubleshooting Guide as requested in my post above? If that didn't fix it, can you provide the rest of the information requested in the Calling for Help section as linked above? Thanks.

@CAM-Gerlach
unfortunately the Troubleshooting Guide didn't help and I think I provided the necessary data already.
Anyhow, since I can have the tool working without problems in an another machine, a Ubuntu 17, let's close this case.
Thanks all!!!

nfortunately the Troubleshooting Guide didn't help and I think I provided the necessary data already.
Anyhow, since I can have the tool working without problems in an another machine, a Ubuntu 17, let's close this case.
Thanks all!!!

Thanks for the quick followup, and glad to hear you got it working on another machine.

I think I provided the necessary data already.

You were very helpful; I didn't meant to dock that, sorry. Its just that we weren't able to reproduce it with the data we had, and thus it was likely machine specific, so I was trying to track down that.

Anyhow, since I can have the tool working without problems in an another machine, a Ubuntu 17,

Great news. Something machine specific, as we suspected, though hopefully you are able to figure out what at some point. Best of luck!

@Mark3xtrm, are you using Spyder with Anaconda? Or through VNC in a remote machine?

Ok, the libraries on which Spyder depends on on Linux are not well packaged by Anaconda. So, please install and run Spyder from Conda-forge with the following commands:
conda create -n spyder-env -c conda-forge spyder python=3.10
conda activate spyder-env
spyder

and let us know if that fixes the problem for you.


Edit site map

This PR includes code changes to make the following edits to the site map:

filter to the new set of 10 sites
label Philadelphia
add a base map to indicate urban areas/areas with high development
label the sites with a site identifier

The base map is the 2019 NLCD impervious cover layer. To me this seemed like a nice way to show relative levels of urban density and still keep the base layer relatively simple. Note that this requires two new dependencies that are not in our dockerfile, {FedData} and {raster}. I'm not sure if it's possible to add these R libraries without updating the versions of any of the other libraries. I'm a little wary of updating the other packages at this stage so if that's not possible, maybe we consider taking this map out of the pipeline.
Regarding the site labels, I re-read the manuscript draft and what stood out to me as the biggest differentiator between sites was whether a site was located along the Schuylkill River or Brandywine Creek (the temporal holdout sites). I therefore opted to include site labels, including "SR" for the Schuylkill and "BC" for Brandywine. The number refers to the river mile (actually, river km) from the outlet and so can provide some information about river size if the site id is used in any of the other figures. What do you think?

Draft caption text:

Figure 2. Monitoring sites used to train and test deep learning models that predict daily dissolved oxygen concentration in the lower Delaware River Basin, USA. Several sites are distributed along two tributaries to the Delaware River, Brandywine Creek (BC, n = 4) and the Schuylkill River (SR, n = 2). Two sites are located along Cobbs Creek in Philadelphia, PA (CC) and two sites are located along relatively forested, headwater streams in the northwest portion of the basin (Baptism Creek, BAP; French Creek, FC). Numbers within the site labels indicate the river distance (km) between the site and the river outlet. Red shading shows urban imperviousness, where darker shading indicates a higher percentage of urban impervious surface cover within a 30-m land surface pixel (NLCD 2019).

Closes #209

Do you think we should label the East- and West- branches of Brandywine Creek, e.g. WBBC_53.2?

I really like it @lekoenig I think the basemap does a nice job conveying information while also keeping it simple. For example, the reader will be able to see why the two different spatial holdouts are so different from looking at this map. I like the naming convention with the river and the rive km also, my only suggestion would be to simplify the names even further and round to the nearest km so BC_23.6 -> BC_24. Also, maybe I missed it, but what does BAP stand for? Is there a site that is referring to? Other than that I think it looks awesome!

my only suggestion would be to simplify the names even further and round to the nearest km so BC_23.6 -> BC_24.

Thanks, @galengorski! I agree with this and will round these river km to the nearest whole number. 📏

Also, maybe I missed it, but what does BAP stand for?

BAP stands for "BAPTISM CREEK" (014721259). Since the abbreviated "BC" would conflict with my Brandywine naming scheme, I just used this. Can you think of another site id that would be easier to interpret? I've edited the PR overview to include a draft caption - hopefully this helps, too.
Baptism Creek is a relatively small stream that is very close to French Creek, the other headwater stream. At the scale of the lower DRB, these two sites are nearly indistinguishable from each other on the map, even if I used hollow circles.

Good idea! Here's where we're at:

Figure 2. Monitoring sites used to train and test deep learning models that predict daily dissolved oxygen concentration in the lower Delaware River Basin, USA. Several sites are distributed along two tributaries to the Delaware River, Brandywine Creek (BC, n = 4) and the Schuylkill River (SR, n = 2). Two sites are located along Cobbs Creek in Philadelphia, PA (CC) and two sites are located in close proximity along relatively forested, headwater streams in the northwest portion of the basin (Baptism Creek, BAP; French Creek, FC). Numbers within the site labels indicate the river distance (km) between the site and the river outlet. Red shading shows urban imperviousness, where darker shading indicates a higher percentage of urban impervious surface cover within a 30-m land surface pixel (NLCD 2019).

I think this looks great, @lekoenig! I like the context of the urbanization and I like the simplified naming structure.
I have a question and a suggestion

Question:  Should we add some kind of indicator to the CC and BAP sites to indicate that they were the "Spatially Dissimilar" sites? It would be nice to not make the reader have to go back and forth in the text and the map to see which one's were "dissimilar." At the same time, when we introduce this map, we haven't talked about those experiments, so I wonder if that would be confusing since we haven't "gotten there" in the story yet. I guess after writing that out, I'd lean toward leaving them unmarked in this map, but I'd be curious to hear your guys' thoughts.
Suggestion: Can we somehow indicate that the red is "urban imperviousness" in the figure itself instead of just in the caption? like this?

@lekoenig I just tried to run this and got this error:

I think you just need to add the 2a_model/src/format_site_splits.R file as part of the PR.

Oops, sorry @jsadler2 - I just committed 2a_model/src/format_site_splits.R along with changes to add the legend for impervious cover. Here is the map as it appears when I run the code in this PR:


OTA stops when "stats" are reported

Hi,
I ran into the following problem:
When doing an OTA everything works fine until homie reports "stats" then the upload of the firmware stops and does not continue. When I try it several times and "stats" are not reported OTA works fine.
I tried finding a way to disable "stats" or change the frequency, but was not able to find a way to do it.
Steps for uploading:
1) hodmin list
MyDevice BadOben│a020a6174ad1 | edbc70ff287604f78684bc3d0de2c567 |
2) Pushing Firmware with hodmin
Device a020a6174ad1 is ONLINE. (installed FW-Checksum: edbc70ff287604f78684bc3d0de2c567)
New firmware: 6c4fab07beeac085b8b36415162ee13d. Start pushing? <Yn>:Y
202, pushing file
Pushing firmware, 81% -- hangs forever

3) When FAILING  - Checking upload / status
$mosquitto_sub -v -h <IP_ADDRESS> -t 'homie/a020a6174ad1/#'
homie/a020a6174ad1/$implementation/ota/status 206 287567/362064
homie/a020a6174ad1/$implementation/ota/status 206 289027/362064
homie/a020a6174ad1/$implementation/ota/status 206 290487/362064
homie/a020a6174ad1/$implementation/ota/status 206 291947/362064
homie/a020a6174ad1/$implementation/ota/status 206 293407/362064
homie/a020a6174ad1/$implementation/ota/status 206 294867/362064
---- > INTERRUPTED
homie/a020a6174ad1/$homie 2.0.0
homie/a020a6174ad1/$implementation esp8266
homie/a020a6174ad1/$mac A0:20:A6:17:4A:D1
homie/a020a6174ad1/light/$type switch
homie/a020a6174ad1/light/$properties on:settable
homie/a020a6174ad1/temperature/$type temperature
homie/a020a6174ad1/temperature/$properties delay:settable
homie/a020a6174ad1/$name BadOben
homie/a020a6174ad1/$localip <IP_ADDRESS>
homie/a020a6174ad1/$stats/interval 60
homie/a020a6174ad1/$fw/name temperature-dallas
homie/a020a6174ad1/$fw/version 1.4.0
homie/a020a6174ad1/$fw/checksum edbc70ff287604f78684bc3d0de2c567
homie/a020a6174ad1/$implementation/config {"wifi":{"ssid":"Razan"},"mqtt":{"host":"<IP_ADDRESS>","port":1883,"auth":false},"name":"BadOben","ota":{"enabled":true}}
homie/a020a6174ad1/$implementation/version 2.0.0
homie/a020a6174ad1/$implementation/ota/enabled true
homie/a020a6174ad1/$online true
homie/a020a6174ad1/$stats/signal 100
homie/a020a6174ad1/$stats/uptime 47
homie/a020a6174ad1/temperature/degrees 29.44

homie/a020a6174ad1/temperature/degrees 29.44
homie/a020a6174ad1/temperature/degrees 29.44
homie/a020a6174ad1/temperature/degrees 29.44

3) With SUCCESS - Checking upload / status
After some retries the upload succeeds and the firmware is installed. While doing the upload there is no "stats".
$ hodmin -m a020a6174ad1 pushFW -c 6c4fab07beeac085b8b36415162ee13d
Device a020a6174ad1 is ONLINE. (installed FW-Checksum: edbc70ff287604f78684bc3d0de2c567)
New firmware: 6c4fab07beeac085b8b36415162ee13d. Start pushing? <Yn>:Y
202, pushing file
Pushing firmware, 100% done
File-md5=6c4fab07beeac085b8b36415162ee13d installed, device BadOben is rebooting

206 354727/362064
206 356187/362064
206 357647/362064
206 359107/362064
206 360567/362064
206 362027/362064
206 362064/362064
200

Device reboots with new firmware  installed - Everthing is good

Stats
Not sure about the term "stats" I mean the following:
homie/a020a6174ad1/$homie 2.0.0
homie/a020a6174ad1/$implementation esp8266
homie/a020a6174ad1/$mac A0:20:A6:17:4A:D1
homie/a020a6174ad1/light/$type switch
homie/a020a6174ad1/light/$properties on:settable
homie/a020a6174ad1/temperature/$type temperature
homie/a020a6174ad1/temperature/$properties delay:settable
homie/a020a6174ad1/$name BadOben
homie/a020a6174ad1/$localip <IP_ADDRESS>
homie/a020a6174ad1/$stats/interval 60
homie/a020a6174ad1/$fw/name temperature-dallas
homie/a020a6174ad1/$fw/version 1.4.0
homie/a020a6174ad1/$fw/checksum edbc70ff287604f78684bc3d0de2c567
homie/a020a6174ad1/$implementation/config {"wifi":{"ssid":"Razan"},"mqtt":{"host":"<IP_ADDRESS>","port":1883,"auth":false},"name":"BadOben","ota":{"enabled":true}}
homie/a020a6174ad1/$implementation/version 2.0.0
homie/a020a6174ad1/$implementation/ota/enabled true
homie/a020a6174ad1/$online true
homie/a020a6174ad1/$stats/signal 100
homie/a020a6174ad1/$stats/uptime 47

I'm seeing the same problem. At the moment I'm using homie-ota to update the firmware. Not sure if the issue is specific to that tool, but maybe not if others are seeing the same issue.

The logfile you posted looks like the MQTT connection was lost. When it is available again, the complete stats are reported again.
So, the reported stats are not the cause of the problem, they are just another symptom.
I had a similar issue, if the Wifi connection was bad. Maybe there is too much MQTT data "queued" and thus the server(?) closes the connection?
If you can get a tcpdump (wireshark) of the MQTT connection, try to look who closes the MQTT connection.

Thanks for your help. I couldn't solve it yet.
I looked into the MQQ Conneciton. Since wireshark is not a tool I'm really good in. I did the following.
0) I checked the WIFI Signal and Connectivity
Couldn't be better is always close to 100%
1) First upgraded MQQ to the acutal version 1.4.14
2) I tried it again, checked the MQQ log for disconnects, I could not see a disconnect there
But i could see the following entry for the device always close to the upload fails
1502545871: iot-a020a6080a1d 2 homie/a020a6080a1d/+/+/set
Could this be the problem / cause?
But I kept checking and I did the following:
3) I connect the Serial Monitor from the Arduino IDE, there I checked
a) if the devices reboots
b) or the MQQ reconnects
Neither did happen, the upload just stalls forever
4) I tried it with a NodeMCU and NodeMCU v3
same behaviour
ad 3)
💡 Firmware temperature-dht11 (1.4.1)
🔌 Booting into normal mode 🔌
{} Stored configuration
  • Hardware device ID: a020a6174ad1
  • Device ID: a020a6174ad1
  • Name: BadOben
  • Wi-Fi:
    ◦ SSID: myWIFI
    ◦ Password not shown
  • MQTT:
    ◦ Host: <IP_ADDRESS>
    ◦ Port: 1883
    ◦ Base topic: homie/
    ◦ Auth? no
  • OTA:
    ◦ Enabled? yes
↕ Attempting to connect to Wi-Fi...
✔ Wi-Fi connected, IP: <IP_ADDRESS>
Triggering WIFI_CONNECTED event...
↕ Attempting to connect to MQTT...
Sending initial information...
✔ MQTT ready
Triggering MQTT_CONNECTED event...
Calling setup function...
〽 Sending statistics...
  • Wi-Fi signal quality: 98%
  • Uptime: 26s
〽 Sending statistics...
  • Wi-Fi signal quality: 100%

====== About here the Upload stalled  ====

  • Uptime: 86s
〽 Sending statistics...
  • Wi-Fi signal quality: 100%
  • Uptime: 146s

=== I restarted the MQQ Server ====

✖ MQTT disconnected
Triggering MQTT_DISCONNECTED event...
↕ Attempting to connect to MQTT...
Retrying (500ms)...
↕ Attempting to connect to MQTT...
Sending initial information...
✔ MQTT ready
Triggering MQTT_CONNECTED event...
〽 Sending statistics...
  • Wi-Fi signal quality: 100%
  • Uptime: 204s
〽 Sending statistics...
  • Wi-Fi signal quality: 100%
  • Uptime: 264s

Tried it again today.
It works now - I used the script provided with homie (scripts/ota_updater/ota_updater.py)
./ota_updater.py -l mqtt.local -i 5ccf7fa123be ~/homie-firmware/ESP8266-Homie-Temperature-BME-280-OLED-v2.ino.bin
Maybe some version conflict.
Thanks a lot for your support!


UNDERTOW-1556 Filter mapping's prefix path match does not work for th…

…e exact path if the exact path match is specified to servlet mapping
https://issues.jboss.org/browse/UNDERTOW-1556

Retest this please

@fl4via The windows failure is due to maven settings that need the httpS url, the linux failure is a test not related to this change

Retest this please


Add link for "cancel" for when editing a newly created Description post

When editing a Description post (within the edit window, of course), I might change my mind.
I see no method to cancel this.   Of course, knowing how SN works, I am aware that I can just hit my browser's back button, or navigate to another page, or close the tab, whatever, but to a new user this might not be intuitive.
(Also, the same scenario occurs when using Edit Bio from Profile)
Perhaps add a link above that shows "cancel" (like the UX for when editing a comment), or maybe instead ... next to the Save button, add a button that reads Cancel?

Seems reasonable.


Misc. File Save Issues

Users have reported issues with saving data files, including errors 6, -2505, etc. Origin is unclear: failed write? files too big? too many files in folder? Exclusive to TDMS?
A systematic stress test can help uncover the origin of the errors: Repeatedly write dummy data to disk and see when/if an error occurs.

I believe it's primarily due to creating large numbers of files. I haven't done any testing yet, but I was able to make ~25 files consistently without issue and I was able to make a single very large file (3 days of data) without issue.
If I had to guess the origin, it's likely due to how the files are enumerated and how the program checks for which number it needs to write.


Possible to downgrade to an earlier beta?

I've been using 12.1.56 for some time with no issue. I upgraded to 12.1.57 recently and notice that the Capslock light turns on randomly, and the keyboard backlighting sometimes does not work. I'd like to go back to 12.1.56 if that's possible. I looked for a place to download old betas but couldn't find one. Any suggestions?

I got the same problem with the keyboard backlight. After returning from sleep mode the keyboard backlight did not work with the newest beta version. I did a NVRAM and SMC reset but this did not help. Only downgrading to the official 12.1 version worked for me. Now the keyboard backlight works if returning from sleep mode.

You can download beta files from here.
https://github.com/tekezo/pqrs.org/tree/master/webroot/osx/karabiner/files

Closing, as issue #1676 is more about the backlight issue, while this was more about finding old betas.


Launch argument do not override config.

Config specified in stratis.conf treated with higher priority than launch arguments.
For example if I have stratis.conf like this:
...
rpcport=57111
...

And launch node with -rpcport=57222 then config value 57111 still will be used.

From the current code it looks like the command line args are only added if they don't already exist in the conf file.
Would just need to change this logic to overwrite instead of just add: https://github.com/stratisproject/StratisBitcoinFullNode/blob/master/src/Stratis.Bitcoin/Configuration/TextFileConfiguration.cs#L99-L110
It makes logical sense to me to overwrite but was there a reason that .conf has priority?

Would just need to change this logic to overwrite instead of just add

Some commands like -addnode can be in multiple instances so if we want to add overriding we should specify what commands can be overridden and what can be duplicated.
I think easier solution is to just search for commands from the end of the conf dictionary (config values are added first, then command line arguments) instead of from the start.

BTC loads command line args first then merges conf into those. Logic is here:
https://github.com/bitcoin/bitcoin/blob/master/src/util.cpp#L618-L645

Perhaps we can change it as follows:

Normalize keys being inserted into the args array to either all have "-" or no "-".
Give priority to the command line arguments by loading them first and then merging the file arguments. Allow multiple values for the same key during this process.
When reading the value with GetOrDefault only return the first value if multiple values are present due to the above merging. Command line arguments would have precedence according to this approach.
When reading the value with GetAll simply return all the values.

So looking at the bitcoin code, they check

command line args first https://github.com/bitcoin/bitcoin/blob/master/src/bitcoind.cpp#L66
config file second https://github.com/bitcoin/bitcoin/blob/master/src/bitcoind.cpp#L98

and when they load the config file, they don't overwrite the arguments already present: https://github.com/bitcoin/bitcoin/blob/master/src/util.cpp#L664

The alternative approach is:

Load config file first
Append the file settings
Always use the first recorded setting for a given key

The benefit of the above approach is that is only requires one dictionary of key/lists.
When looking at the bitcoin code they require an additional dictionary mapMultiArgs:
'''
if (mapArgs.count(strKey) == 0)
mapArgs[strKey] = strValue;
mapMultiArgs[strKey].push_back(strValue);
'''

@bokobza is this fixed?


Bravo for Power BI v1.0.0

Describe the problem
Hi,
I am surprised to see the difference my Dataset size that Bravo displays VS the size that is displayed in the service or in my desktop

Is there an explanation to that or is it a bug ?
Bravo version
v1.0.0
Tabular model
Power BI Desktop, import mode
Power BI
Power BI desktop version October 2022
Steps to reproduce the behavior
No response
Additional context
No response
Screenshots

Anything else ?
No response

Hi @ajerb
The PBIX file on your desktop and the dataset in the service storage are both a compressed backup of your data model. When you open the PBIX report or a report on PBI service then the data model is loaded in memory in the Analysis Services process. Data loaded into memory takes more space because part of the data is not compressed so it's normal that this size - which is the one that Bravo displays - is bigger than the PBIX file on disk.
You can take a look at this video where Marco explains it in more detail https://www.youtube.com/watch?v=vI7kVVHxsiM

Hi @albertospelta
Thanks a lot, the video helped me a lot to understand it.


LSC: Quick Info in interactive window

Also known as "Hover". We can't make use of the VS LSC implementation, that doesn't work for the REPL. We'll have to copy/adapt theirs. It's not too much code, but maybe we can live without this for now.

We are now tracking this task in our internal Pylance Azure DevOps.


ARROW-2924: [Java] mvn release fails when an older maven javadoc plugin is installed

+1, this is blocking building the release.


Update Deliverable 1: Inception

My two interviews with every sentense

Hi Junjian, you submitted the pull request and everything correctly, but I would like you to follow my formatting the best you can with your interviews, mine are already in there and you can take those as examples.


Add remove people operator + Ability to remove single push device token

Add support for the $remove operator which is detailed here. Using this $remove operator, an additional method removeSinglePushDeviceToken has been added to allow for a single push notification device token to be removed from a user's profile.

LGTM!


fix v0.9.2 config ui - update menu labels and titles for pipelines

⚠ Config-UI / Pipelines UX Copy

[ ] Unify Menu, Page Title and active BreadCrumb texts for Pipelines

Description
[V0.9.0 RELEASE TARGET] release-v0.9
This PR applies UX copy updates to the Pipelines service(s).
Does this close any open issues?
#1387
Screenshots

Seems like you pick the wrong base branch.

Seems like you pick the wrong base branch.

Thanks for catching this, yes it had the wrong target branch set it was still in draft mode however so wasn't cleared for merge.


Update Code Scanning Security Tool to Shiftleft

This PR adds a Github action in .github/workflows/shiftleft.yml. This will trigger a scan whenever someone creates a PR. Any potential vulnerabilities will be reported in Shiftleft.io. For now, the AppSec team will be triaging the results first and will communicate any relevant ones to the owner's Trello requests board.

@hakjoon When you have a chance, can you take a look? This is just adding a Github action to statically analyze for any new vulnerabilities introduced in a PR.

It seems fine but I don’t know much about this repo. @districtem or @adamghill might have thoughts.

This seems fine to me as well!


cannot  deployment

@wr0124 Perhaps you wanted to raise an issue instead of a PR?

I'm new to GitHub and got a problem yesterday, my folds in the github are
totally updated, but I have no personal website generated . I'll try to
figure it out and welcome your help !
On Sun, Mar 5, 2023 at 3:57 PM Pats @.***> wrote:

@wr0124 https://github.com/wr0124 Perhaps you wanted to raise an issue
instead of a PR?
—
Reply to this email directly, view it on GitHub
https://github.com/alshedivat/al-folio/pull/1235#issuecomment-1455114818,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIXSEKV37YXICNGE62Q6ILDW2SSV5ANCNFSM6AAAAAAVQGQ2XE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi! I managed to generate my website, but it is not like the documents in the github ! Do you have any idea why ?


Client Telemetry: Adds number of open TCP connection Information

Description
Add Number of Open TCP connection at any given point of time (Only for Direct Connection Mode). in Client Telemetry.
Direct Mode:

Gateway Mode:

Type of change

[] New feature (non-breaking change which adds functionality)

Closing issues
To automatically close an issue: closes #2956

Open Question: a) Should this telemetry be collected only on "Direct" mode, or you see any benefit in case of "Gateway" mode also? b) Feedback on Metric Name?
@j82w @kirankumarkolli @FabianMeiswinkel

Have this metrics only for "Direct" Mode


problem about 3dhighresnet

I'm using niftynet to do some work about heart CT segmentation. And i used highres3d_net. The training was perfect. However when I applied the trained network to some new images，the output was terrible. one image used for training is illustrated in 1, and its output in2. the new image is in3,and the output 4.
How should I do to get an accurate result?
Any help would be appreciated.
image for training
output of above
new image
output of new image

Are the images from the same machines? I.e. is the test data acquired in the same way as the training data?


Hang loading feed file into sideloaded project

I used your wizard to create a new project. When I sideload the zip file, it hangs loading my feed file. I know that the feed file is somewhat out of date based on the Direct Publisher JSON specifications, but it seems to ingest just fine using DP. I'm wondering if you can help me determine where the code is hanging.
Thanks!
Here is my project:
Pioneer Media.zip
Here is my feed file:
https://pmchurch.org/feeds/roku
The channel is currently live using Direct Publisher as https://channelstore.roku.com/details/7aaa3197fc30e3680f17c72392fc0504/new-perceptions-tv

@richardaparke I see you used Vimeo and I see you are using a feed without a dot JSON extension which leads me to believe you may be using the wp smart TV plugin, I may be wrong but if you are all you have to do is use a redirect plugin to redirect the feed link, an example would be to use a feed link as https://pmchurch.org/feeds/roku.jsom and redirect it to https://pmchurch.org/feeds/roku

@rrirower Bingo! Sorry I missed that, and thank you for your help! Another question for you. When on the media item, I'm noticing that the title is highlighted in yellow (see RALE screenshot). Can you tell me where you're setting that so I can change the color? Thanks again for your help!

@ferdiworks we're actually grabbing content dynamically from our website pmchurch.org. So it will be as simple as changing the file name. Thanks for your idea of redirecting though - also a good solution!


[Label Studio] Add CI Tests

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Sahith Malyala seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add MustInitializeHealthComponent to HealthReporter interface

Before this PR
The InitializeHealthComponent function is often called on startup, with a statically defined component name, in which case the caller knows that it will never return an error.
After this PR
Adds alternate MustInitializeHealthComponent which panics when an error would have occurred. This makes the calling code cleaner and self-documenting.
==COMMIT_MSG==
Add MustInitializeHealthComponent to HealthReporter interface
==COMMIT_MSG==

This change is

+1 to the convenience function. Agree this is handy, but don't see any reason to add it to the interface.


Turns out jsonpath can't be bundled - so need to manually deploy its …

…dependency tree

Ahh, I was just looking into this one.
How would you feel about adding something like this to the github actions tests.yml?
# esbuild should succeed and contain no warnings
- name: esbuild check
  run: |
    output=$(npx node bundle-build.js)
    if [[ $? == 0 ]]; then
      echo "esbuild ran successfully"
    else
      echo "esbuild did not succeed"
      echo "$output"
      exit 1
    fi
  working-directory: application/backend

This would check that bundle-build.js succeeds and contains no output.

Yes - that's a good idea and a quick win - so happy for that to be added.
There are other ways the resulting Docker build can fail though - I think at some point in the literal Docker building action we will need to check that.


ng serve --prod --source-map does not produce source maps

Versions
     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 6.0.1
Node: 8.9.4
OS: win32 x64
Angular: 6.0.1
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, http, language-service, material
... material-moment-adapter, platform-browser
... platform-browser-dynamic, platform-server, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.1
@angular-devkit/build-angular     0.6.1
@angular-devkit/build-optimizer   0.6.1
@angular-devkit/core              0.6.1
@angular-devkit/schematics        0.6.1
@angular/flex-layout              5.0.0-beta.13
@ngtools/webpack                  6.0.1
@schematics/angular               0.6.1
@schematics/update                0.6.1
rxjs                              6.1.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

Run ng serve --prod --source-map

Observed behavior
The ouput js and css bundles do not contain the source maps.
Desired behavior
The output bundles should contain the source maps, and the browser (Chrome) should recognize them.
Mention any other details that might be useful (optional)

You can change it in angular.json in architect -> build -> "builder": "@angular-devkit/build-angular:browser" -> configurations -> production -> sourceMap

Thank you, @jmesa-sistel. Indeed, it works. But:

Nowhere in the documentation could I find any information on this. It would be nice to add explicit documentation.
IMO, since there is a --source-map command-line flag, it should do something :smile: Anyway, it would be nice to have an ability to enable sourcemaps via CLI, without modifying the angular.json file.

@Maximaximum
Docs about new schemas system:
https://github.com/angular/angular-cli/wiki/angular-workspace
To understand how it works I used a json online viewer to understand the organization.
I have to say that this new config system is very powerful, I usually had to eject the configuration, now it is not needed for me.
Seems that the angular.json configuration has precedence over cli parameters, with --prod you select production configuration so --source-map parameter is overwritten , maybe it is a bug, I do not know.


SteamPrefill fails to log in with an invalid credential error, even though the credentials are correct

Describe the bug
When I attempt to log into my Steam account using my correct credentials, the following happens:
A Steam account is required in order to prefill apps!
Please enter your Steam account name : myusername
Please enter your Steam password. (Password won't be saved) : ****************************************
[1:33:02 PM] Connected to Steam!
[1:33:02 PM] Requesting new access token...
[1:33:03 PM] Disconnected from Steam!
SteamKit2.Authentication.AuthenticationException: Authentication failed with
result InvalidPassword.
  at async Task<CredentialsAuthSession>
     SteamKit2.Authentication.SteamAuthentication.
     BeginAuthSessionViaCredentialsAsync(AuthSessionDetails details)
  at async Task SteamPrefill.Handlers.Steam.Steam3Session.GetAccessTokenAsync()
  at void
     SteamPrefill.Handlers.Steam.Steam3Session.<>c__DisplayClass16_0.<<LoginToSt
     eamAsync>b__0>d.MoveNext()
  at void Spectre.Console.Status.<>c__DisplayClass16_0.<<StartAsync>b__0>d.
     MoveNext() in Status.cs:79
  at void Spectre.Console.Status.<>c__DisplayClass17_0`1.<<StartAsync>b__0>d.
     MoveNext() in Status.cs:120
  at void Spectre.Console.Progress.<>c__DisplayClass28_0`1.<<StartAsync>b__0>d.
     MoveNext() in Progress.cs:133
  at async Task<T> Spectre.Console.Internal.DefaultExclusivityMode.RunAsync<T>(
     Func<Task<T>> func) in DefaultExclusivityMode.cs:40
  at async Task<T> Spectre.Console.Progress.StartAsync<T>(Func<ProgressContext,
     Task<T>> action) in Progress.cs:116
  at async Task<T> Spectre.Console.Status.StartAsync<T>(string status,
     Func<StatusContext, Task<T>> func) in Status.cs:117
  at async Task Spectre.Console.Status.StartAsync(string status,
     Func<StatusContext, Task> action) in Status.cs:77
  at async Task SteamPrefill.Handlers.Steam.Steam3Session.LoginToSteamAsync()
  at async Task SteamPrefill.SteamManager.InitializeAsync()
  at async ValueTask SteamPrefill.CliCommands.SelectAppsCommand.ExecuteAsync(
     IConsole console)
  at async ValueTask<int> CliFx.CliApplication.RunAsync(ApplicationSchema
     applicationSchema, CommandInput commandInput) in CliApplication.cs:148
  at async ValueTask<int> CliFx.CliApplication.RunAsync(IReadOnlyList<string>
     commandLineArguments, IReadOnlyDictionary<string, string>
     environmentVariables) in CliApplication.cs:190
  at async ValueTask<int> CliFx.CliApplication.RunAsync(IReadOnlyList<string>
     commandLineArguments) in CliApplication.cs:202
  at async Task<int> SteamPrefill.Program.Main()

Additional Details
This is on macOS using version 2.7.0.  I use a password manager for my passwords, so I'm copying/pasting my password to make sure there aren't any typos.  The same credentials work for logging into https://store.steampowered.com and the Steam client.
The username I have is an e-mail address (from back when that was required for a Steam username), and the password is up to 100 characters, inclusive of one or more of each of the following: lowercase English letters, uppercase English letters, digits, and the non-alphanumeric characters<EMAIL_ADDRESS>Screenshots
If applicable, add screenshots to help explain your problem.
Logs
[1:45:43 PM] Starting login!
[1:45:54 PM] Connecting with CellId: 0
[1:45:55 PM] Connected to Steam!
[1:45:55 PM] Requesting new access token...
[1:45:56 PM] Disconnected from Steam!
[1:45:56 PM] SteamKit2.Authentication.AuthenticationException: Authentication failed with result InvalidPassword.
   at SteamKit2.Authentication.SteamAuthentication.BeginAuthSessionViaCredentialsAsync(AuthSessionDetails details)
   at SteamPrefill.Handlers.Steam.Steam3Session.GetAccessTokenAsync()
   at SteamPrefill.Handlers.Steam.Steam3Session.<>c__DisplayClass16_0.<<LoginToSteamAsync>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at Spectre.Console.Status.<>c__DisplayClass16_0.<<StartAsync>b__0>d.MoveNext() in Spectre.Console\Live\Status\Status.cs:line 79
--- End of stack trace from previous location ---
   at Spectre.Console.Status.<>c__DisplayClass17_0`1.<<StartAsync>b__0>d.MoveNext() in Spectre.Console\Live\Status\Status.cs:line 120
--- End of stack trace from previous location ---
   at Spectre.Console.Progress.<>c__DisplayClass28_0`1.<<StartAsync>b__0>d.MoveNext() in Spectre.Console\Live\Progress\Progress.cs:line 133
--- End of stack trace from previous location ---
   at Spectre.Console.Internal.DefaultExclusivityMode.RunAsync(Func`1 func) in Spectre.Console\Internal\DefaultExclusivityMode.cs:line 40
   at Spectre.Console.Progress.StartAsync(Func`2 action) in Spectre.Console\Live\Progress\Progress.cs:line 116
   at Spectre.Console.Status.StartAsync(String status, Func`2 func) in Spectre.Console\Live\Status\Status.cs:line 117
   at Spectre.Console.Status.StartAsync(String status, Func`2 action) in Spectre.Console\Live\Status\Status.cs:line 77
   at SteamPrefill.Handlers.Steam.Steam3Session.LoginToSteamAsync()
   at SteamPrefill.SteamManager.InitializeAsync()
   at SteamPrefill.CliCommands.SelectAppsCommand.ExecuteAsync(IConsole console)
   at CliFx.CliApplication.RunAsync(ApplicationSchema applicationSchema, CommandInput commandInput) in C:\Users\Tim\Dropbox\Programming\Lancache-Prefills\External\CliFx\CliFx\CliApplication.cs:line 148
   at CliFx.CliApplication.RunAsync(IReadOnlyList`1 commandLineArguments, IReadOnlyDictionary`2 environmentVariables) in C:\Users\Tim\Dropbox\Programming\Lancache-Prefills\External\CliFx\CliFx\CliApplication.cs:line 190
   at CliFx.CliApplication.RunAsync(IReadOnlyList`1 commandLineArguments) in C:\Users\Tim\Dropbox\Programming\Lancache-Prefills\External\CliFx\CliFx\CliApplication.cs:line 202
   at SteamPrefill.Program.Main()

I just tested this by changing my secondary account to have a 110 character password, and yeah the same issue happens to me.  I'll have to dig deeper into this, but at least I can reproduce it.

@Kreeblah Looks like Valve silently truncates longer passwords to the first 64 characters.  I've tried logging in with just the first 64 of my 110 character password and it will login successfully.  Found this relevant discussion: ArchiSteamFarm issues/2903.
I'll have to add the same truncation logic to my login method.

Released in v3.1.0


i really dont know how to fix this psych engine experimental build

Describe your bug here.
every time I use lime test windows it gives me this error and I can't find how to fix it

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
not yet

Should be fixed in the latest commits


ComboBox issue when moving forms between screens with different DPI scaling.

I have an issue where if i have multiple screens with different DPI scaling, the roll-down content from the combo-box gets miss-placed and sized wrongly if i move a sub-form contained in DockPane to the other screen with the higher DPI scaling.
The problem can be reproduced by having a parent window host 2 or more DockContent "forms" inside a DockPane. One of the DockContents, lets call it "FormCombo", should contain at least 1 ComboBox, if you undock the other DockContent, lets call it "FormEmpty", and move it to the other screen (with a higher % DPI scaling), at first everything lookes fine, but if you love "FormEmpty" again, but still keeping it on the other screen, the combo box in "FormCombo" will get messed up. If you now try to expand the combo box, the roll-down content will be offset in a way that makes it look as if it has the other screens DPI scaling applied to it, the rolled down content is also way to big and blurry. You can reset this by moving "FormEmpty" back down to the unscaled screen.
The .zip contains a recording of this as pictures and instructions on how to reproduce the issue. It was done with the latest version (2.10.0) from NuGet.
The .zip files contains a .mht file, can be opened in IE/edge at least, probably in firefox as well. If you don't want to, or can't then i can upload the individual images instead, its a self-contained html+resources file produced by the problem-step-recorder (PSR.exe that comes with windows).
Issue.zip

Can't find a way to edit the initial post for clarity; With "the lasted version" I mean 2.10.0.

Thanks, but please do test with 2.11 Beta 2 as we just included some DPI related patch.
You can come back with the latest test result after that.

Still an issue with 2.11.0 beta 2 it seems.
Same procedure as last time, created the main window on the screen with 100%DPI, moved one of the docked panels to the 125% DPI screen, moved it again (problem only seems to occur after second move, like before), and the ComboBox content gets displaced.

It is not clear to me how DPS can affect the rendering of the default ComboBox control, so mark this issue as "up for grabs". Like the previous DPI issue, I expect someone from the community to help resolve it.

Found a blog post on such, https://emoacht.wordpress.com/2013/10/30/per-monitor-dpi-aware-in-windows-forms/ but it would not be quite easy to bring it to DPS. Welcome the community to work on this.


Tests failing in CI

See https://github.com/langston-barrett/treeedb/actions/runs/4583725802/jobs/8094753508?pr=27

Looks like this is caused by CI upgrading to Souffle 2.4. Not sure why that would cause a difference in the output, but in any case, we can just pin 2.3 for now.


ENH: Add MP-PCA/NORDIC denoising through dwidenoise

Closes #3308.
Potential blockers

dwidenoise does not support NORDIC yet, but there are plans to add it (see https://github.com/MRtrix3/mrtrix3/issues/3031). In the meantime, MP-PCA is the only option.
dwidenoise doesn't accept a precalculated noise map yet, which limits reproducibility if users want to apply the denoising step using the output noise map using precalculated data.
MRTrix3 doesn't have a dwi2noise command to estimate the noise map from no-RF volumes, so I've disabled no-RF processing for now.
Tracking lost degrees of freedom is important and dwidenoise has a -rank option to output a DOF map, but that feature hasn't been released yet. See https://github.com/MRtrix3/mrtrix3/issues/2312.
I'm not sure yet what figures we should generate for the denoising procedure. I think stat-maps of the noise map, DOF map, and possibly variance-explained map (which we'll need to generate) would be good. Maybe a histogram of the noise values?
The MRTrix3 team recommends concatenating data across echoes before running dwidenoise, and they ultimately plan to support 5D NIfTIs, but my implementation currently just applies the denoising step independently to each echo. See https://github.com/MRtrix3/mrtrix3/issues/3021.
I need to add an appropriate filename for the noise map to the niworkflows specification (pending https://github.com/nipreps/niworkflows/pull/899).

Changes proposed in this pull request

Create a workflow to apply MP-PCA or NORDIC denoising to BOLD data. This is done right before slice timing correction in init_bold_native_wf.
Add a new parameter, --thermal-denoise-method to specify which approach to use, if any.
Add "phase" and "norf" options to the ignore parameter to let users skip those elements of the thermal denoising procedure.

dwidenoise doesn't accept a precalculated noise map yet, which limits reproducibility if users want to apply the denoising step using the output noise map using precalculated data.

It is intended to address this at some stage; for tracking see https://github.com/MRtrix3/mrtrix3/issues/2274 and https://github.com/MRtrix3/mrtrix3/issues/3035.

MRTrix3 doesn't have a dwi2noise command to estimate the noise map from no-RF volumes, so I've disabled no-RF processing for now.

I've added a note to https://github.com/MRtrix3/mrtrix3/issues/3035.

Tracking lost degrees of freedom is important ...

Agree 100%; we're invested locally in being able to modulate downstream applications appropriately based on this. It would be good to:

Export noise and rank images to the HTML for visual assessment.
Apply estimated transforms to the rank image and aggregate, to produce an approximate signal rank per output element (ie. needs to be propagated for each output space, including surfaces)

dwidenoise has a -rank option to output a DOF map, but that feature hasn't been released yet.

There's a few branches in parallel that have proposed changes to dwidenoise that may be on the dev development branch, or are not even there yet let alone on master. If need be I can aggregate multiple such changes onto a dedicated branch that fMRIPrep can then clone.

... possibly variance-explained map (which we'll need to generate) ...

That could be done. It would be reasonably easy to add an export option to dwidenoise rather than trying to compute it after the fact. Do you want to make a feature request?

The MRtrix3 team recommends concatenating data across echoes before running dwidenoise, and they ultimately plan to support 5D NIfTIs, but my implementation currently just applies the denoising step independently to each echo.

When I've done this myself, I've concatenated data across echoes into the fourth dimension, denoised, and then separated the volumes back out into echoes. That is I think more principled given that the noise level should be identical. It's not super difficult to do. You may however want to clamp the maximal patch size: once (# echoes x # volumes) exceeds 343 the default changes to a 9x9x9 patch and that runs very slowly. This  behaviour should be better with https://github.com/MRtrix3/mrtrix3/issues/2742 / https://github.com/MRtrix3/mrtrix3/pull/3029, which won't have such step changes in patch size.

Some other points to consider:

I found the denoising under default usage to be imperfect for fMRI data due to the large offset from zero. This seems to be possible to mitigate by either:

Demeaning the data prior to PCA: https://github.com/MRtrix3/mrtrix3/pull/2363
This however would benefit from confirmation that it does not introduce any kind of bias into the noise estimator / reported rank.
Utilising double-precision floating-point.
This can already be chosen at the command-line, but obviously comes with a performance penalty.
Using a more stable PCA method: https://github.com/MRtrix3/mrtrix3/pull/2906
This also comes with a performance penalty.

The dwidenoise command has a different copyright to the default MRtrix3 one. There is also a patent owned by NYU regarding the denoising of a 4D series based on the MP distribution. There's been internal MRtrix3 discussion on whether the scope of that patent is restricted to the specific rank estimator presented in the original article, and therefore does not cover the alternative estimator in use by default as published in this work, but I don't think we reached a definitive conclusion.
Pinging @jdtournier, @dchristiaens, @jelleveraart for full transparency / invitation of opinions.

Thanks @Lestropie for looping me in this conversation.

I agree that accepting precomputed noise maps is an impactful feature, not only because it might accelerate the algorithm but also improve its robustness  in case of correlated noise (https://doi.org/10.1162/imag_a_00049).  It would further allow denoising of individual series without the need for concatenating them.

Similarly, I wonder whether accepted the "rank" as an input might be of interest for certain application in which preserving homoscedasticity is more critical than maxizing precision.

Concatenating imaging series with varying echos  in the fourth dimension is conceptually a proper strategy under the assumption of identical noise levels. However, as suggested by @Lestropie, it is recommended to keep the patch size relatively small if the noise level is spatially varying.  The 5x5x5 is commonly used. If the individual echo series have > 125 images, then denoising the individual series might actually be preferred as it does not impose any risk of masking subtle signal features across the series.  An approach could be to (a) concatenate all series to estimate the noise level; (b) use the resulting noise map as an input to denoise the individual series.

We have previously used the demeaning step, but I will confirm that there  is not risk of introducing biases or lowering the robustness of the current algorithm.

I wonder whether accepted the "rank" as an input might be of interest for certain application in which preserving homoscedasticity is more critical than maximizing precision.

Posted as https://github.com/MRtrix3/mrtrix3/issues/3046. Would need implementation within the underlying denoising command; whether fMRIPrep would want to utilise that is beyond my control.

it is recommended to keep the patch size relatively small if the noise level is spatially varying

It might be possible to mitigate this if the full noise map profile is known a priori, and voxels can be normalised to unit variance upon insertion into the Casorati matrix? https://github.com/MRtrix3/mrtrix3/issues/3041

The 5x5x5 is commonly used.

Have more flexible patch size in this implementation with spherical kernels: https://github.com/MRtrix3/mrtrix3/issues/2742

We have previously used the demeaning step, but I will confirm that there is not risk of introducing biases or lowering the robustness of the current algorithm.

Cool; it would be useful for me to know from someone more familiar with the mathematics / simulations that it's sensible.


WCAG 2.2: Question pages ‖ Redundant entry

What
Update our guidance on asking questions to emphasise that services should not request information that has already been provided or have stored, unless doing so is necessary for security purposes or the information is out of date.
Resources

Question pages guidance
WCAG 2.2 criterion for 'Redundant entry'

Why
The new WCAG 2.2 criterion 'Redundant entry' says:

Information previously entered by or provided to the user that is required to be entered again in the same process is either:

auto-populated, or
available for the user to select.

This could potentially cover several patterns. Patterns that were identified as being potentially relevant during desk research include:

Create a username
Confirm an email address
Confirm a phone number
Passwords
Payment card details
Dates
Gender or sex
Telephone numbers

To avoid needing to update all of these patterns individually, the intent is to consolidate the guidance updates on the 'Question pages' page instead.
Who needs to work on this
Content designer or technical writer
Who needs to review this
Accessibility specialist, content designer or technical writer
Done when

[ ] Guidance has been updated

This issue is tracked in the WCAG 2.2 content updates document (restricted).

This issue appears to already be covered by the existing planned guidance updates in the WCAG 2.2 content updates main guidance doc.
Here's the existing section that covers footers and consistent help: https://docs.google.com/document/d/1nIxIKgVUheC8zvVdqWIcqtVPCl7oTN4hv11R9rDwdvM/edit#heading=h.x6h6ome4vh0o
As a result I'm closing this issue as a duplicate of the main WCAG 2.2 guidance issue:

https://github.com/alphagov/govuk-design-system/issues/2729
https://github.com/alphagov/govuk-design-system/pull/3090


Multiple errors

Hello, i installed a few days ago the plugin into homebridge and got following error at starting the plugin:

TypeError: Cannot read properties of undefined (reading 'alertImage')
at Intercom.configureCamera (/usr/lib/node_modules/homebridge-loxone-proxy/src/loxone/items/Intercom.ts:35:26)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at runNextTicks (node:internal/process/task_queues:64:3)
at processImmediate (node:internal/timers:447:9)

In the end, the solution was renaming the Intercom.ts file in the pluginfolder so it dont get loaded and luckily the plugin could start.
Maybe its a problem because i have no intercom?
The second problem regarding to the log is the following:
But here i cant guess whats the problem or if it is any problem at all :)

SyntaxError: Unexpected identifier
at new Function ()
at LightControllerV2.LoxoneAccessory.callBack (/usr/lib/node_modules/homebridge-loxone-proxy/src/LoxoneAccessory.ts:91:29)
at /usr/lib/node_modules/homebridge-loxone-proxy/src/loxone/LoxoneHandler.ts:69:56
at Array.forEach ()
at handleAnyEvent (/usr/lib/node_modules/homebridge-loxone-proxy/src/loxone/LoxoneHandler.ts:69:36)
at Object.socketOnEventReceived (/usr/lib/node_modules/homebridge-loxone-proxy/src/loxone/LoxoneHandler.ts:99:17)
at WebSocket._handleBinaryEvent (/usr/lib/node_modules/homebridge-loxone-proxy/node_modules/lxcommunicator/modules/WebSocket.js:934:78)
at WebSocket._binaryMessageHandler (/usr/lib/node_modules/homebridge-loxone-proxy/node_modules/lxcommunicator/modules/WebSocket.js:773:26)
at W3CWebSocket.onmessage (/usr/lib/node_modules/homebridge-loxone-proxy/node_modules/lxcommunicator/vendor/WebSocketWrapper.js:107:62)
at W3CWebSocket._dispatchEvent [as dispatchEvent] (/usr/lib/node_modules/homebridge-loxone-proxy/node_modules/yaeti/lib/EventTarget.js:107:17)
todo: colortemp(100,4775)
todo: colortemp(100,4775)
todo: colortemp(100,4775)

I have also lots of errors at the similar location
    at LightControllerV2.eval (eval at LoxoneAccessory.callBack (/var/lib/homebridge/node_modules/homebridge-loxone-proxy/src/LoxoneAccessory.ts:91:29), <anonymous>:3:27)
    at LightControllerV2.LoxoneAccessory.callBack (/var/lib/homebridge/node_modules/homebridge-loxone-proxy/src/LoxoneAccessory.ts:92:21)
TypeError: Cannot read properties of undefined (reading 'updateService')

TypeError: Cannot read properties of undefined (reading 'alertImage')
at Intercom.configureCamera (/usr/lib/node_modules/homebridge-loxone-proxy/src/loxone/items/Intercom.ts:35:26)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at runNextTicks (node:internal/process/task_queues:64:3)
at processImmediate (node:internal/timers:447:9)

In the end, the solution was renaming the Intercom.ts file in the pluginfolder so it dont get loaded and luckily the plugin could start. Maybe its a problem because i have no intercom?

This is a strange error. It should not do this if you do not have an Intercom configured.
The Proxy fetches the Loxone structure file from the miniserver. This file is located at http:///data/loxapp3.json. It then tries to parse every entry in the "controls" section of the structure file.
IF (and this should not happen with your miniserver) it finds an item with type "Intercom" or "IntercomV2" it tries to create an homekit Intercom accessory based on that item.
Are you sure there are no entries of type "intercom" or "intercomv2" in your structure file?

The other error messages are solved in the latest release

I searched in the loxapp3.json File but there was no entry for Intercom / IntercomV2 also I searched in the Loxone Config too but i could not find anything regarding Intercom. Is there more i can do here to help?

If you run HomeBridge in debug mode, the proxy will also log debug messages. If you try the latest release with the intercom.ts file untouched and you start/restart homebridge, perhaps we can find the issue in the logs.

Here is the homebridge.log interesstingly, i get the error now only one time and then it restarts but keeps running.
homebridge.log.txt
A few hours ago, i re-addet a virtual output to sonos for my Bell (Door Controller) maybee this could have changed something...?

This is in your log;

[19/12/2023, 22:23:50] [LoxonePlatform] [IntercomItem] Restoring accessory from cache: Klingel
[19/12/2023, 22:23:50] [LoxonePlatform] [Klingel] Register Listeners for IntercomItem

The door controller you are mentioning is an Intercom Item. So this is why it is happening. I added an Intercom item without a camera to my config and I was able to reproduce te issue.
There is a new beta version (v1.6.0-beta.2) available that solves the issue. It skips the camera config and configures the intercom. This will probably give you a doorbell via homekit, although HomeKit does not support doorbells without camera anymore.
Could you test this new functionality. I know it doesn't crash anymore, but I am curious if the doorbell works. If it doesn't we can also make the proxy skip the entire Item when a camera isn't found.

Ah thank you, did not know that this is an Intercom Type item. And upfront thank you for your fast responses. I see now a Doorbell in my Home App but as you mentioned it above, there is a new Item in the App but with the note „Not supported“. If i press the bell button there happens sadly nothing.

This does seem to work for my test setup. It should also work for you, as long as you have the doorbell input connected to the "Bell" input of the Door Controller.

This does seem to work for my test setup. It should also work for you, as long as you have the doorbell input connected to the "Bell" input of the Door Controller.

That's actually exactly the setup that i have. Tried it earlier again but there happens nothing in the Home App.
PS: Is it to be expected, if you have in loxone 2 outputs (seperate lights) and you put them into a group in the Home app, that there is a noticable delay between output 1 and output 2 ?

Since it is not actually supported in HomeBridge i will leave the code as it is now. If you want to exclude it in your setup, you can add "Intercom" as an excluded ItemType in the newest release. This will prevent the intercom from being mapped in HomeKit.
The delay in grouped outputs is to be expected. This is not something we can handle in the plugin. It's just how HomeKite behaves with these grouped outputs.
I will close this SR. Please let me now if you have any further requests for enhancement.


Crashes while calling NSRegularExpression.firstMatch(in:options:range:)

We're using BartyCrouch as our build script phase. I found out that all version from 3.11.2 and newer are crashing with the following stack:
2018-11-14 11:15:58.401 bartycrouch[27535:1456155] *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSRegularExpression enumerateMatchesInString:options:range:usingBlock:]: Range or index out of bounds'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff3ad71e65 __exceptionPreprocess + 256
	1   libobjc.A.dylib                     0x00007fff66dcd720 objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff3ad71c97 +[NSException raise:format:] + 201
	3   Foundation                          0x00007fff3d077f3d -[NSRegularExpression(NSMatching) enumerateMatchesInString:options:range:usingBlock:] + 352
	4   Foundation                          0x00007fff3d0e3fbb -[NSRegularExpression(NSMatching) firstMatchInString:options:range:] + 143
	5   bartycrouch                         0x0000000106761c61 bartycrouch + 142433
	6   bartycrouch                         0x00000001067775e8 bartycrouch + 230888
	7   bartycrouch                         0x000000010677e392 bartycrouch + 258962
	8   bartycrouch                         0x00000001067410b0 bartycrouch + 8368
	9   bartycrouch                         0x0000000106748378 bartycrouch + 37752
	10  bartycrouch                         0x0000000106741047 bartycrouch + 8263
	11  libdyld.dylib                       0x00007fff67e9c08d start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
/Users/podkovyrin/Library/Developer/Xcode/DerivedData/DashSync-acejhnkrxbeiyrbzivficvuxtfxq/Build/Intermediates.noindex/DashSync.build/Debug-iphonesimulator/DashSync_Example.build/Script-FB5A0FA7219506140079CF42.sh: line 8: 27535 Abort trap: 6           bartycrouch code -v -p "$PROJECT_DIR/../DashSync/" -l "$PROJECT_DIR/../DashSync/" -c -s -k -f "DSLocalizedString"
Command PhaseScriptExecution failed with a nonzero exit code

However, 3.11.1 works fine. And it looks like this commit breaks all new versions: https://github.com/Flinesoft/BartyCrouch/commit/4a1088d20d5350a5b05af6240c30f8ecf8d63455
You can try it yourself from building workspace in Example folder of https://github.com/dashevo/dashsync-iOS

Since you found the exact issue, would you be willing to fix it and post a PR with the fix? @podkovyrin

Can't reproduce on current version (v.4.0.0).


Added options to support socket timestamping

This PR adds the options for a socket to generate and report timestamps when a packet was received by the hardware/kernel.
The platforms supported by socket2 vary in the support for the timestamping options but I tried to implemented this as platform independent as possible. Unfortunately all the cfg attributes produce a lot of noise in the code.
For documentation check:

Windows
Linux
FreeBSD

Closes #415

One note: The timestamps are reported as control messages/ancillary data in a struct cmsghdr. socket2 implements the MsgHdr type which could be used to access those control messages  but I think it would be out of scope of this lib so I did not implement that. I would like to hear other opinions on that.

@Thomasdezeeuw I just revisited this PR and thought about your comment regarding the API design. I still don't think that a API similar to TcpKeepalive would make much sense here because for the SO_TIMESTAMPING option we really need the bitmap encoded into an unsigned 32 bit integer for configuration, while SO_TIMESTAMP and SO_TIMESTAMPNS only require a boolean parameter.
What we could do a enum Timestamp which holds a variant for reporting milliseconds, a variant for reporting nanoseconds like so:
enum Timestamp {
    ReportMs(bool), // represents SO_TIMESTAMP
    ReportNs(bool), // represents SO_TIMESTAMPNS
}

But I would argue that the SO_TIMESTAMPING option should be handled separate, because it allows customize the source of the generated timestamps (reception, transmission and hardware or software timestamps). This is what I tried to encode in the current option struct Timestamping and I don't really see how that would fit into the same function as the other two settings.
I`d like to hear your opinion on that one.


Move Graph Legend to Vue Component

About
Moving the graph legend code to a Vue component means we don't need to modify the DOM directly (which is frowned upon).
Related Issues
Fixes #40.
To test
Run some functions and watch the graphs update on the app listing and detailed apps page. In particular pay attention to the legend. No new functionality has been added so it should behave as per the previous functionality.

double sweet


Take into account Chrome tab groups

Google chrome (GC) allows creating tab groups starting from May 13, 2020 (see here or take a look at the figure).

There are two natural features that would be beneficial both while working in the browser and while accessing the (potentially long list of) saved tabs:

a per GC group tab saving into onetab;
structure saved tabs according to the GC groups they belong to (in the case someone saves the whole tabs).

Ability to persist Chrome Tab Group names would let me retire all my other tab extensions (Tabs Outliner, original OneTab..)!

Opening a stored tab list and create a Chrome tab-group for it would be a great addition to the functionality of this plugin!

This would be a great feature and one I'm looking for in an extension!


[dataset] simplify saving/reading of TLVs in/from secure storage

This commit simplifies the handling of Dataset TLVs that need to be securely stored when the PLATFORM_KEY_REFERENCES_ENABLE feature is enabled. Two new methods are added to the Dataset class:

SaveTlvInSecureStorageAndClearValue() which  saves the value of a given TLV type in secure storage and clears the TLV value by setting all value bytes to zero.

ReadTlvFromSecureStorage() which reads the TLV value back from secure storage and updates it in the Dataset.

These methods are used by DatasetLocal to manage the set of TLVs that need to be securely stored defined by a constant array of SecurelyStoredTlv entries. Each entry provides the TLV type along with the associated Crypto::Storage::KeyRef to use for active or pending Dataset.

@Damian-Nordic, @hemanth-silabs I appreciate if you can help review this PR. It contains no changes the overall behavior (it is mainly a simplification). Thanks.

@suveshpratapa since @hemanth-silabs is on vacation can you review this one.  Thanks for tagging me @jwhui


D45 wdc oauth update

@ashwinar  @brtal
This PR has the update to the OAuth tutorial so that matches the OAuthProxyExample code.
I've created the PR so you can see what has changed in the wdc_oauth_tutorial.md file. That file was ported from the WDC v1.0 tutorial of the same name. It was never updated to work with the new code that used server flow OAuth, where the client secret was kept on the web server and not in the WDC app.
The PR also has some other fixes for the notes about deprecating the v1 WDCs in a "future" version of Tableau.    Thanks.

Coverage remained the same at 98.913% when pulling b2505785d136234c5571c65bb4da2b77f46100ec on d45:d45_wdc_Oauth_update into 9ce04e96a2f6d1d13ce22bafdaeb4b84477a640c on tableau:dev.

@ashwinar @brtal  I've made changes to address your comments. Let me know if you see anything else that should change. I'll merge it with development branch today and open a PR for master so customers can see the update.  Thanks!


Add a variable to configure Multi-AZ for RDS

This pull request introduces support for enabling Multi-AZ deployments for this module. The changes include updates to both the main.tf and variables.tf files in the modules/aws_ecs and modules/aws_ecs_ec2 directories.
Key changes include:

modules/aws_ecs/main.tf: Added the multi_az parameter to the aws_db_instance resource.
modules/aws_ecs/variables.tf: Introduced a new variable rds_multi_az to control the Multi-AZ setting for RDS instances.
modules/aws_ecs_ec2/main.tf: Added the multi_az parameter to the aws_db_instance resource.
modules/aws_ecs_ec2/variables.tf: Introduced a new variable rds_multi_az to control the Multi-AZ setting for RDS instances.

Thank you for the contribution! This looks great.


parameter map after double array

Larry and I saw where the column index mapping did not appear to be correct.  See
http://localhost:8080/HapiServer/hapi/info?id=C4_PP_FGM
which contains B_xyz_gse__C4_PP_FGM.

The time indicated as available results in an empty day of data in the generated interval.  This has data:
vap+hapi:http://localhost:8080/HapiServer/hapi?id=C4_PP_FGM&parameters=time_tags__C4_PP_FGM,B_xyz_gse__C4_PP_FGM&timerange=2010-03-13

This is fixed.  I'd gotten confused in Util.subsetParams, and I'd even added an extra variable to calculate the result, which was incorrect.

Joy!


How to have "RemoveFailedPods" evict pods in "Error" state reason while Pod status phase is in "running" ?

What version of descheduler are you using?
descheduler version: v0.23.1
What k8s version are you using (kubectl version)?
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:59:11Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.2", GitCommit:"092fbfbf53427de67cac1e9fa54aaa09a28371d7", GitTreeState:"clean", BuildDate:"2021-06-16T12:53:14Z", GoVersion:"go1.16.5", Compiler:"gc", Platform:"linux/amd64"}
What did you do?
We have mongo pod which has pod.Status.Phase as "Running", however one of its container containerStatus.State is "Terminated" and reason as "Error".
NAMESPACE             NAME                                                               READY   STATUS      RESTARTS   AGE     IP                NODE                                       NOMINATED NODE   READINESS GATES
db-mongo-ram      db-mongo-ram-configsvr-2                                       0/2     Error       4          24h     X.X.X.X    cni-k8-node-13-io69sc-9gu39tp7t1m52511

hi @sudmis  in your case, you have pod with more than one container, and you would like configure the descheduler to evict pod if one of the container phase is not in running, is it correct?

thanks @sudmis  could you get the pod and show me the yaml?
kubectl get pod xxx -o yaml
now for descheduler we do check pod.Status.Phase == v1.PodFailed and evict pod in RemoveFailedPods stategy.

I do not have kubectl get pod detail at this moment. But here is the kubectl describe pod details, when the mentioned behavior occurred. Hope it will help.
[root@cni-k8-master-11-io69sc-9gu39tp7t1m52511 node13]# cat fed-db-mongo-ram-configsvr-2_describe.log
Name:                 fed-db-mongo-ram-configsvr-2
Namespace:            fed-db-mongo-ram
Priority:             700000
Priority Class Name:  uc-priority-2
Node:                 cni-k8-node-13-io69sc-9gu39tp7t1m52511/<IP_ADDRESS>
Start Time:           Thu, 07 Apr 2022 10:31:45 -0400
Labels:               app.kubernetes.io/component=database
                      app.kubernetes.io/instance=fed-db-mongo-ram
                      app.kubernetes.io/managed-by=kubedb.com
                      app.kubernetes.io/name=mongodbs.kubedb.com
                      controller-revision-hash=fed-db-mongo-ram-configsvr-5b6d758d6b
                      mongodb.kubedb.com/node.config=fed-db-mongo-ram-configsvr
                      statefulset.kubernetes.io/pod-name=fed-db-mongo-ram-configsvr-2
Annotations:          cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32,fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4/128
                      k8s.v1.cni.cncf.io/network-status:
                        [{
                            "name": "",
                            "ips": [
                                "<IP_ADDRESS>",
                                "fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4"
                            ],
                            "default": true,
                            "dns": {}
                        }]
                      k8s.v1.cni.cncf.io/networks-status:
                        [{
                            "name": "",
                            "ips": [
                                "<IP_ADDRESS>",
                                "fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4"
                            ],
                            "default": true,
                            "dns": {}
                        }]
                      kubernetes.io/limit-ranger: LimitRanger plugin set: cpu, memory request for container exporter; cpu, memory limit for container exporter
                      kubernetes.io/psp: mongodb-db
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
  IP:           fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4
Controlled By:  StatefulSet/fed-db-mongo-ram-configsvr
Init Containers:
  copy-config:
    Container ID:  docker://b0d09dca2b9eff5bc388e06bafa496d98c1b35a2cc50cffedb0bdb3f71c1bb6c
    Image:         cnreg-rel:5000/cna-db_percona_mongo-mongodb_init_4_1_5-rel_3_1_1:3.2.0-6
    Image ID:      docker-pullable://cnreg-rel:5000/cna-db_percona_mongo-mongodb_init_4_1_5-rel_3_1_1@sha256:7f2902a7dace37a84068331339c39053b58aabc440517f6eb8ebdb545c87c9c1
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
    Args:
      -c

                        echo "running install.sh"
                        /scripts/install.sh
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 08 Apr 2022 10:08:34 -0400
      Finished:     Fri, 08 Apr 2022 10:08:34 -0400
    Ready:          True
    Restart Count:  3
    Limits:
      cpu:     16
      memory:  8Gi
    Requests:
      cpu:     500m
      memory:  10Mi
    Environment:
      SSL_MODE:  disabled
    Mounts:
      /configdb-readonly from configdir (rw)
      /data/configdb from config (rw)
      /init-scripts from init-scripts (rw)
      /keydir-readonly from keydir (rw)
      /var/run/mongodb/tls from certdir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sv4d (ro)
Containers:
  mongodb:
    Container ID:  docker://efddbc195277ba8f0c7d8ffe4deb2ee0e57371117a0e8adabd7c89beaf4a8509
    Image:         cnreg-rel:5000/cna-db_percona_mongo-percona_server_mongodb:latest
    Image ID:      docker-pullable://cnreg-rel:5000/cna-db_percona_mongo-percona_server_mongodb@sha256:49a79b20cb9ae2707324ff88878f0d08747821c9448144baf889f1e80b6ccc72
    Port:          27017/TCP
    Host Port:     0/TCP
    Command:
      mongod
    Args:
      --dbpath=/data/db
      --auth
      --bind_ip_all
      --port=27017
      --configsvr
      --replSet=cnfRepSet
      --clusterAuthMode=keyFile
      --keyFile=/data/configdb/key.txt
      --ipv6
      --sslMode=disabled
      --transitionToAuth
      --listenBacklog=4096
      --config=/data/configdb/mongod.conf
    State:          Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Thu, 07 Apr 2022 19:15:15 -0400
      Finished:     Fri, 08 Apr 2022 10:07:55 -0400
    Ready:          False
    Restart Count:  2
    Limits:
      cpu:     16
      memory:  8Gi
    Requests:
      cpu:     500m
      memory:  10Mi
    Liveness:  exec [bash -c set -x; if [[ $(mongo admin --host=localhost  --username=$MONGO_INITDB_ROOT_USERNAME --password=$MONGO_INITDB_ROOT_PASSWORD --authenticationDatabase=admin --quiet --eval "db.adminCommand('ping').ok" ) -eq "1" ]]; then
          exit 0
        fi
        exit 1] delay=0s timeout=5s period=10s #success=1 #failure=3
    Readiness:  exec [bash -c set -x; if [[ $(mongo admin --host=localhost  --username=$MONGO_INITDB_ROOT_USERNAME --password=$MONGO_INITDB_ROOT_PASSWORD --authenticationDatabase=admin --quiet --eval "db.adminCommand('ping').ok" ) -eq "1" ]]; then
          exit 0
        fi
        exit 1] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      POD_NAMESPACE:               fed-db-mongo-ram (v1:metadata.namespace)
      REPLICA_SET:                 cnfRepSet
      AUTH:                        true
      SSL_MODE:                    disabled
      CLUSTER_AUTH_MODE:           keyFile
      MONGO_INITDB_ROOT_USERNAME:  <set to the key 'username' in secret 'mongodb-auth'>  Optional: false
      MONGO_INITDB_ROOT_PASSWORD:  <set to the key 'password' in secret 'mongodb-auth'>  Optional: false
      POD_NAME:                    fed-db-mongo-ram-configsvr-2 (v1:metadata.name)
    Mounts:
      /data/configdb from config (rw)
      /data/db from datadir (rw)
      /init-scripts from init-scripts (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sv4d (ro)
      /work-dir from workdir (rw)
  exporter:
    Container ID:  docker://489118f9e48f362235ffded4e6149d304b98f4a72227516b623b9430e2f32a0a
    Image:         cnreg-rel:5000/cna-db_percona_mongo-mongodb_exporter-rel_3_1_1:3.2.0-6
    Image ID:      docker-pullable://cnreg-rel:5000/cna-db_percona_mongo-mongodb_exporter-rel_3_1_1@sha256:37ab6bbcbe5025518f94a8545e8fff198f7d65ffd95a059e028afccf0bf68535
    Port:          56790/TCP
    Host Port:     0/TCP
    Args:
      --mongodb.uri=mongodb://$(MONGO_INITDB_ROOT_USERNAME):$(MONGO_INITDB_ROOT_PASSWORD)@localhost:27017/admin
      --web.listen-address=:56790
      --web.telemetry-path=/metrics
    State:          Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Thu, 07 Apr 2022 19:16:00 -0400
      Finished:     Fri, 08 Apr 2022 10:07:55 -0400
    Ready:          False
    Restart Count:  2
    Limits:
      cpu:     2
      memory:  2Gi
    Requests:
      cpu:     10m
      memory:  10Mi
    Environment:
      MONGO_INITDB_ROOT_USERNAME:  <set to the key 'username' in secret 'mongodb-auth'>  Optional: false
      MONGO_INITDB_ROOT_PASSWORD:  <set to the key 'password' in secret 'mongodb-auth'>  Optional: false
      POD_NAME:                    fed-db-mongo-ram-configsvr-2 (v1:metadata.name)
    Mounts:
      /var/run/mongodb/tls from certdir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sv4d (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  workdir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  init-scripts:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  certdir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  keydir:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  fed-db-mongo-ram-key
    Optional:    false
  config:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  datadir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  1Gi
  configdir:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  configsvr-config
    Optional:    false
  kube-api-access-9sv4d:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 170s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 170s
Events:
  Type     Reason          Age                From             Message
  ----     ------          ----               ----             -------
  Warning  NodeNotReady    39m (x3 over 16h)  node-controller  Node is not ready
  Normal   SandboxChanged  38m                kubelet          Pod sandbox changed, it will be killed and re-created.
  Normal   AddedInterface  38m                multus           Add eth0 [<IP_ADDRESS>/32 fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4/128]
  Normal   Pulled          38m                kubelet          Container image "cnreg-rel:5000/cna-db_percona_mongo-mongodb_init_4_1_5-rel_3_1_1:3.2.0-6" already present on machine
  Normal   Created         38m                kubelet          Created container copy-config
  Normal   Started         38m                kubelet          Started container copy-config
  Normal   Pulled          38m                kubelet          Container image "cnreg-rel:5000/cna-db_percona_mongo-percona_server_mongodb:latest" already present on machine
  Normal   Created         38m                kubelet          Created container mongodb
  Normal   Started         38m                kubelet          Started container mongodb
[root@cni-k8-master-11-io69sc-9gu39tp7t1m52511 node13]#

thanks.
i check your log, the pod status is running, it will not be evict for the RemoveFailedPods strategy .
but it seems your pod keep restart, if meet requirement it will be evict by RemovePodsHavingTooManyRestarts stategy.
but i still open here that may be we can discuss is  how to evict pod if container fail but pod running in descheduler.

@JaneLiuL I do not have kubectl get pod detail at this moment. But here is the kubectl describe pod details, when the mentioned behavior occurred. Hope it will help.
RemovePodsHavingTooManyRestarts may not help here. Because, currently in my case, if the pod is restated all the container are back in running state.
So what do you suggest should be the next step to discuss?
NAMESPACE             NAME                                                               READY   STATUS      RESTARTS   AGE     IP                NODE                                       NOMINATED NODE   READINESS GATES
fed-db-mongo-ram      fed-db-mongo-ram-configsvr-2                                       0/2     Error       4          24h     <IP_ADDRESS>    cni-k8-node-13-io69sc-9gu39tp7t1m52511     <none>           <none>

[root@cni-k8-master-11-io69sc-9gu39tp7t1m52511 node13]# cat fed-db-mongo-ram-configsvr-2_describe.log
Name:                 fed-db-mongo-ram-configsvr-2
Namespace:            fed-db-mongo-ram
Priority:             700000
Priority Class Name:  uc-priority-2
Node:                 cni-k8-node-13-io69sc-9gu39tp7t1m52511/<IP_ADDRESS>
Start Time:           Thu, 07 Apr 2022 10:31:45 -0400
Labels:               app.kubernetes.io/component=database
                      app.kubernetes.io/instance=fed-db-mongo-ram
                      app.kubernetes.io/managed-by=kubedb.com
                      app.kubernetes.io/name=mongodbs.kubedb.com
                      controller-revision-hash=fed-db-mongo-ram-configsvr-5b6d758d6b
                      mongodb.kubedb.com/node.config=fed-db-mongo-ram-configsvr
                      statefulset.kubernetes.io/pod-name=fed-db-mongo-ram-configsvr-2
Annotations:          cni.projectcalico.org/podIP: <IP_ADDRESS>/32
                      cni.projectcalico.org/podIPs: <IP_ADDRESS>/32,fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4/128
                      k8s.v1.cni.cncf.io/network-status:
                        [{
                            "name": "",
                            "ips": [
                                "<IP_ADDRESS>",
                                "fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4"
                            ],
                            "default": true,
                            "dns": {}
                        }]
                      k8s.v1.cni.cncf.io/networks-status:
                        [{
                            "name": "",
                            "ips": [
                                "<IP_ADDRESS>",
                                "fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4"
                            ],
                            "default": true,
                            "dns": {}
                        }]
                      kubernetes.io/limit-ranger: LimitRanger plugin set: cpu, memory request for container exporter; cpu, memory limit for container exporter
                      kubernetes.io/psp: mongodb-db
Status:               Running
IP:                   <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
  IP:           fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4
Controlled By:  StatefulSet/fed-db-mongo-ram-configsvr
Init Containers:
  copy-config:
    Container ID:  docker://b0d09dca2b9eff5bc388e06bafa496d98c1b35a2cc50cffedb0bdb3f71c1bb6c
    Image:         cnreg-rel:5000/cna-db_percona_mongo-mongodb_init_4_1_5-rel_3_1_1:3.2.0-6
    Image ID:      docker-pullable://cnreg-rel:5000/cna-db_percona_mongo-mongodb_init_4_1_5-rel_3_1_1@sha256:7f2902a7dace37a84068331339c39053b58aabc440517f6eb8ebdb545c87c9c1
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/sh
    Args:
      -c

                        echo "running install.sh"
                        /scripts/install.sh
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Fri, 08 Apr 2022 10:08:34 -0400
      Finished:     Fri, 08 Apr 2022 10:08:34 -0400
    Ready:          True
    Restart Count:  3
    Limits:
      cpu:     16
      memory:  8Gi
    Requests:
      cpu:     500m
      memory:  10Mi
    Environment:
      SSL_MODE:  disabled
    Mounts:
      /configdb-readonly from configdir (rw)
      /data/configdb from config (rw)
      /init-scripts from init-scripts (rw)
      /keydir-readonly from keydir (rw)
      /var/run/mongodb/tls from certdir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sv4d (ro)
Containers:
  mongodb:
    Container ID:  docker://efddbc195277ba8f0c7d8ffe4deb2ee0e57371117a0e8adabd7c89beaf4a8509
    Image:         cnreg-rel:5000/cna-db_percona_mongo-percona_server_mongodb:latest
    Image ID:      docker-pullable://cnreg-rel:5000/cna-db_percona_mongo-percona_server_mongodb@sha256:49a79b20cb9ae2707324ff88878f0d08747821c9448144baf889f1e80b6ccc72
    Port:          27017/TCP
    Host Port:     0/TCP
    Command:
      mongod
    Args:
      --dbpath=/data/db
      --auth
      --bind_ip_all
      --port=27017
      --configsvr
      --replSet=cnfRepSet
      --clusterAuthMode=keyFile
      --keyFile=/data/configdb/key.txt
      --ipv6
      --sslMode=disabled
      --transitionToAuth
      --listenBacklog=4096
      --config=/data/configdb/mongod.conf
    State:          Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Thu, 07 Apr 2022 19:15:15 -0400
      Finished:     Fri, 08 Apr 2022 10:07:55 -0400
    Ready:          False
    Restart Count:  2
    Limits:
      cpu:     16
      memory:  8Gi
    Requests:
      cpu:     500m
      memory:  10Mi
    Liveness:  exec [bash -c set -x; if [[ $(mongo admin --host=localhost  --username=$MONGO_INITDB_ROOT_USERNAME --password=$MONGO_INITDB_ROOT_PASSWORD --authenticationDatabase=admin --quiet --eval "db.adminCommand('ping').ok" ) -eq "1" ]]; then
          exit 0
        fi
        exit 1] delay=0s timeout=5s period=10s #success=1 #failure=3
    Readiness:  exec [bash -c set -x; if [[ $(mongo admin --host=localhost  --username=$MONGO_INITDB_ROOT_USERNAME --password=$MONGO_INITDB_ROOT_PASSWORD --authenticationDatabase=admin --quiet --eval "db.adminCommand('ping').ok" ) -eq "1" ]]; then
          exit 0
        fi
        exit 1] delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:
      POD_NAMESPACE:               fed-db-mongo-ram (v1:metadata.namespace)
      REPLICA_SET:                 cnfRepSet
      AUTH:                        true
      SSL_MODE:                    disabled
      CLUSTER_AUTH_MODE:           keyFile
      MONGO_INITDB_ROOT_USERNAME:  <set to the key XXX in secret XXX >  Optional: false
      MONGO_INITDB_ROOT_PASSWORD:  <set to the key XXX in secret XXX>  Optional: false
      POD_NAME:                    fed-db-mongo-ram-configsvr-2 (v1:metadata.name)
    Mounts:
      /data/configdb from config (rw)
      /data/db from datadir (rw)
      /init-scripts from init-scripts (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sv4d (ro)
      /work-dir from workdir (rw)
  exporter:
    Container ID:  docker://489118f9e48f362235ffded4e6149d304b98f4a72227516b623b9430e2f32a0a
    Image:         cnreg-rel:5000/cna-db_percona_mongo-mongodb_exporter-rel_3_1_1:3.2.0-6
    Image ID:      docker-pullable://cnreg-rel:5000/cna-db_percona_mongo-mongodb_exporter-rel_3_1_1@sha256:37ab6bbcbe5025518f94a8545e8fff198f7d65ffd95a059e028afccf0bf68535
    Port:          56790/TCP
    Host Port:     0/TCP
    Args:
      --mongodb.uri=mongodb://$(MONGO_INITDB_ROOT_USERNAME):$(MONGO_INITDB_ROOT_PASSWORD)@localhost:27017/admin
      --web.listen-address=:56790
      --web.telemetry-path=/metrics
    State:          Terminated
      Reason:       Error
      Exit Code:    255
      Started:      Thu, 07 Apr 2022 19:16:00 -0400
      Finished:     Fri, 08 Apr 2022 10:07:55 -0400
    Ready:          False
    Restart Count:  2
    Limits:
      cpu:     2
      memory:  2Gi
    Requests:
      cpu:     10m
      memory:  10Mi
    Environment:
      MONGO_INITDB_ROOT_USERNAME:  <set to the XXX key in secret XXX >  Optional: false
      MONGO_INITDB_ROOT_PASSWORD:  <set to the key XXX in secret XXX >  Optional: false
      POD_NAME:                    fed-db-mongo-ram-configsvr-2 (v1:metadata.name)
    Mounts:
      /var/run/mongodb/tls from certdir (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-9sv4d (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  workdir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  init-scripts:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  certdir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  keydir:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  fed-db-mongo-ram-key
    Optional:    false
  config:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  datadir:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  1Gi
  configdir:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  configsvr-config
    Optional:    false
  kube-api-access-9sv4d:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 170s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 170s
Events:
  Type     Reason          Age                From             Message
  ----     ------          ----               ----             -------
  Warning  NodeNotReady    39m (x3 over 16h)  node-controller  Node is not ready
  Normal   SandboxChanged  38m                kubelet          Pod sandbox changed, it will be killed and re-created.
  Normal   AddedInterface  38m                multus           Add eth0 [<IP_ADDRESS>/32 fdf7:74dc:298e:27e1:36e5:50ef:fe83:6dd4/128]
  Normal   Pulled          38m                kubelet          Container image "cnreg-rel:5000/cna-db_percona_mongo-mongodb_init_4_1_5-rel_3_1_1:3.2.0-6" already present on machine
  Normal   Created         38m                kubelet          Created container copy-config
  Normal   Started         38m                kubelet          Started container copy-config
  Normal   Pulled          38m                kubelet          Container image "cnreg-rel:5000/cna-db_percona_mongo-percona_server_mongodb:latest" already present on machine
  Normal   Created         38m                kubelet          Created container mongodb
  Normal   Started         38m                kubelet          Started container mongodb
[root@cni-k8-master-11-io69sc-9gu39tp7t1m52511 node13]#

@sudmis  could you show me your descheduler policy config file?
it should been evicted for RemovePodsHavingTooManyRestarts strategy since your Restart Count is so high.

we have removePodsHavingTooManyRestarts strategy with podRestartThreshold: 20.  In the logs if you see restart count is 4.

yes. if the podRestartThreshold: 20 it is not to the PodRestartThreshold.
in your case, if you setting podRestartThreshold: 20, and you hope we can evict by RemoveFailedPods stategy.
i think we need to add feature to RemoveFailedPods, like add below, for time limit, i still suggest you can update podRestartThreshold for this case.
cc @damemi  what do you think for add containerstatus check on RemoveFailedPods strategy?
type PodsContainersStatusCheck struct {
	ContainerNotSuccessthreshold     int32
	IncludingInitContainers bool
}

@JaneLiuL If we keep podRestartThreshold  as low as to 4, since we have few pods with more than 4 containers and assuming few restarts, then it will lead to undesired results.
Do you have anyother suggestion?


Crash with trimming and zoom/magnifier (win+plus)

Describe the bug
Avalonia app crashes if compiled with trimming and user opens zoom/magnifier (win+plus hotkey).
To Reproduce

dotnet new avalonia.app -o AvaTrim
change Avalonia version to 11.0.4 in csproj
dotnet publish -c Release -r win-x64 --self-contained -p:PublishSingleFile=true -p:PublishTrimmed=true
run app exe
open zoom/magnifier with win+plus, move mouse cursor around Avalonia app
crash (app silently closes)

Expected behavior
Don't crash.
Desktop (please complete the following information):

OS: Windows 10 22H2 x64
Version: 11.0.4

Additional context
Also crashes on start if zoom/magnifier already runs.
Running under native debugger (mingw, gdb) I get SIGSEGV with stacktrace:
1 ntdll!RtlRetrieveNtUserPfn    0x7ff89455c73e
2 UiaRaiseAutomationEvent       0x7ff867cec0ff
3 UiaRegisterProviderCallback   0x7ff867d0636b
4 UiaRegisterProviderCallback   0x7ff867d06550
5 UiaReturnRawElementProvider   0x7ff867cc0766
6 ??                            0x7ff627aee2b7

Looks like something in accessibility support was trimmed.

Related https://github.com/AvaloniaUI/Avalonia/issues/11767
It still shouldn't crash though. Accessibility-related code shouldn't be enabled while app is trimmed or built with AOT.
You can try adding <BuiltInComInteropSupport>true</BuiltInComInteropSupport> to the csproj file.

<BuiltInComInteropSupport> already enabled in avalonia.app template.

I've encountered the same issue, and unfortunately, I have low vision 😄.
When I launch the app after compiling and publishing with the system magnifier active, it crashes.
Interestingly, this doesn’t happen in debug mode.
Specifications:
Windows 11
Avalonia version: 11.1.4
Avalonia.Desktop version: 11.1.4
Avalonia.ReactiveUI version: 11.1.4
Avalonia.Svg.Skia version: <IP_ADDRESS>
Avalonia.Themes.Fluent version: 11.1.4
Avalonia.Fonts.Inter version: 11.1.4
Avalonia.Diagnostics version: 11.1.4
CommunityToolkit.Mvvm version: 8.3.2
Material.Icons.Avalonia version: 2.1.10
NModbus4.NetCore version: 3.0.0

<PropertyGroup>
	<OutputType>WinExe</OutputType>
	<TargetFramework>net8.0</TargetFramework>
	<Nullable>enable</Nullable>
	<BuiltInComInteropSupport>true</BuiltInComInteropSupport>
	<ApplicationManifest>app.manifest</ApplicationManifest>
	<AvaloniaUseCompiledBindingsByDefault>true</AvaloniaUseCompiledBindingsByDefault>
	<ApplicationIcon>Assets\favicon.ico</ApplicationIcon>
	<PublishSingleFile>true</PublishSingleFile>
	<SelfContained>true</SelfContained>
	<PublishReadyToRun>true</PublishReadyToRun>
	<BuiltInComInteropSupport>true</BuiltInComInteropSupport>
</PropertyGroup>


Add roku automation panel

Add a new panel to the extension that allows running a series of commands that can be automatically run on deploy or run manually.

Closing as combining with new detail view work


[Event Hub] Update Processor & Pump to not use EventHubClient

This PR removes all uses of the EventHubClient class except for in receiver.spec.ts file which is being taken care of in #9598. This almost completes the tasks set out in #6505
Noteworthy changes:

EventHubConsumerClient now has its own connection context and so uses it directly for getPartitionProperties, getProperties and getPartitionIds calls allowing us to remove the same from EventHubClient
EventHubConsumerClient passes the connection context along with retry options instead of an instance of EventHubClient to the EventProcessor and then eventually to the PartitionPump
The test for trackLastEnqueuedEventProperties on the EventProcessor is deleted as a similar test for EventHubConsumerClient.subscribe() in reciever.spec.ts file covers it in #9598

/azp run js - eventhubs-client - tests

/azp run js - eventhubs-client - tests

/azp run js - eventhubs-client - tests

/azp run js - eventhubs-client - tests

/azp run js - eventhubs-client - tests


resolve the Windows path is too long bug

resolve the Windows path is too long bug

Closes #XXXX

Relates to #XXXX

[ ] I have read the Contributing Guide.

/verify

Please use full command names instead of aliases in the script