Create pytest fixtures raiwidgets tests

Description
The RAIInsights computation logic can be refactored into pytest fixture so that multiple tests in raiwidgets can leverage the computed RAIInsights.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[ ] responsibleai/model-assessment

Python packages changed:

[x] raiwidgets
[ ] responsibleai
[ ] erroranalysis
[ ] rai_core_flask

Tests

[x] No new tests required.
[ ] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

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

Codecov Report

Merging #1232 (1478b98) into main (1756613) will increase coverage by 9.58%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1232      +/-   ##
==========================================
+ Coverage   65.99%   75.58%   +9.58%
==========================================
  Files          91       10      -81
  Lines        4473      258    -4215
==========================================
- Hits         2952      195    -2757
+ Misses       1521       63    -1458

Flag
Coverage Δ

unittests
75.58% <ø> (+9.58%)
:arrow_up:

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

Impacted Files
Coverage Δ

...s/erroranalysis/_internal/error_report/__init__.py

raiwidgets/raiwidgets/constants.py

erroranalysis/erroranalysis/version.py

responsibleai/responsibleai/_tools/__init__.py

erroranalysis/erroranalysis/report/error_report.py

...onsibleai/responsibleai/serialization_utilities.py

responsibleai/responsibleai/_interfaces.py

erroranalysis/erroranalysis/_internal/__init__.py

raiwidgets/raiwidgets/error_handling.py

responsibleai/responsibleai/_internal/constants.py

... and 71 more

Continue to review full report at Codecov.

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


Autocompletion in Prisma schema

Problem
Right now, the Prisma VS Code extension only shows Red squiglly lines on errors but doesn't actually write your schema in the first place.
Solution
We could implement autocomplete for the Prisma VS Code extension (and other editor plugins) so that people get suggestions for available type, model and field names.
Additional context
Ben Awad mentioned this idea at the beginning of his Prisma 2 Beta review.

Related of https://github.com/prisma/vscode/issues/96 and https://github.com/prisma/vscode/issues/90


Allow providers to restart refresh worker when credentials or endpoint info changes

Some providers hold a blocking connection open to the management system for the refresh worker as well as the event catcher.  This means that without restarting the worker the new credentials and/or endpoint info won't be picked up.
Currently the providers which require this are Openshift, Kubernetes, and VMware
https://github.com/ManageIQ/manageiq/issues/21253

I thought we had something in the worker itself (at least the vmware worker) that would check for auth changes in a separate thread, and when it found a change it would "stop" the internal monitor thread.  Then, the outer loop would detect that and restart it?

Not that I've been able to find, I also thought refresh workers were restarted on an auth change but it looks like only the event catcher has this logic.  We do check for valid auth on startup and periodically and the workers will be stopped if the auth is invalid, so this is really for the case where creds are changed from one valid record to another valid one.

Ok, I'm good with merging for now to get the bug fixed, but I don't really like the current layout, and stuff feels missing still.  You probably have similar ideas to mine, but some thoughts for the future:

This code is all worker specific, but lives in ExtManagementSystem.  I feel like it should be extracted somehow.
This only handles event catchers and (now) refresh workers, but doesn't handle metrics workers or other workers, or any other things that might be specific to the provider (like if we still had the broker worker).
The new code is copy-paste, and we'll have to copy-paste again for another worker type.  It feels like it could be DRY'ed up.

Offhand I'm not sure what the "right" layout for the code is, but it feels like this is something that we can make pluggable, with the default implementation being to just ask the worker what all of the worker types are and bounce them all.
Thoughts?

Yeah I was planning on following this up with some refactoring to:

Combine the "on auth change" and "on endpoint change" since it doesn't matter why we're restarting the workers, they get restarted
Call a common restart_workers_on_change method rather than specific event/refresh worker methods and have the providers simply supply a list of workers that need to be restarted
If we can move to the logic to worker class we can keep this in the ProviderWorkerMixin (maybe react to an MiqEvent?)

@miq-bot cross-repo-tests https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/437, https://github.com/ManageIQ/manageiq-providers-vmware/pull/728


adding mq_notify glibc wrapper for SYS_mq_notify syscall.

Mainly for this PR. asking to qualify for stable.

Thanks! FYI the rustbot command to add the label works for everyone, you can nominate anything and I will filter out where needed.
@rustbot label +stable-nominated


Data Viz/Dashboard

Discussing with Christina

Jeffery has taken an initial pass at mocking up a visual map for DCC needs. Further discussion needed to set next steps towards MVP data viz.

Already in progress, closing.


Missing Jira Additional Fields

Describe the bug
Jira Additional Fields are not written to Faros.
To Reproduce

Configure your Jira source Additional Fields and save
Sync
In Hasura, do the following query:

query MyQuery {
  tms_Task(where: {uid: {_eq: "TEST-1"}}) {
    additionalFields
    name
  }
}

The additional field is missing.
Note that in Metabase, the additionalField column in tms_Task will only display in the detail view (when you look at the record).

Can be reproduced on our TEST project with custom field customfield_10049 (testcustom field). TEST-1 should have foo in there. Jira source is the community one on 0.2.20.

@thomas-gerber  I have the exact same issue.  Is there a workaround? Thanks.

As best as I can tell (when connecting that source into the Airbyte E2E Testing destination), the custom fields are not returned with the issue by the community source, which is currently pegged at 0.2.21 when Faros is provisioned (pretty old).
You could try to update to the latest jira community source (1.3.0) in Settings > Source, check the source config and the destination config. The custom fields are all fetched and properly stored Faros side. I also see lots of errors in the sync which I am not sure about - although it looks OK in metabase.


docs: include underlying TypeScript types into the API Documentation

Description

uses the plugin jsdoc-tsimport-plugin to properly parse jsdoc comments with import tags
imports DiffOutput and Output of src/asyncapidiff.ts as  typedefs in jsdoc comments and then utilizes them in doc generation

Related issue(s)

Fixes #47

@aayushmau5 This is the current state of the solution. I had to define Output and DiffOutput as jsdoc typedefs. If you preview the generated API.md you can see that the kind is still stated as global typedef with no information from the Typescript type.
Let me see how can we improve it further.

@ron-debajyoti See what you can do, and if the problem is still there, feel free to drop it, like I said earlier, this task is a hard one, and possibly cannot be fixed without heavy involvement. Good luck :)

@ron-debajyoti See what you can do, and if the problem is still there, feel free to drop it. Like I said earlier, this task is a hard one, and possibly cannot be fixed without heavy involvement. Good luck :)

@aayushmau5 Thanks!
I was wondering if you could look into the latest generated API.md file and point out what extra modifications/information is to be generated. I know that the typedef Diff in the document generated should typically show more information, and I'm going to try that by adding more jsdoc comments and see if I can fix that .

Other than that, everything else looks pretty good. Awesome work @ron-debajyoti :rocket:

@aayushmau5
Here are the latest updates :

docs/README.md can't be deleted, but I added configurations so that it's generated contents acts like a contents file wrt the doc folder. It's not the duplicate of README.md present in the root.

I did however find a bug, which I commented out above.

@ron-debajyoti What bug are you talking about?

@ron-debajyoti What bug are you talking about?

@aayushmau5 please check docs/classes/asyncapidiff.AsyncAPIDiff.md to line 52.
Defined In for all the generated doc files points to my local repository. This is seen for all the Defined In generated from the types in typedoc.
Possible solutions are :

Generate the docs as asyncapi admin, every time the repo gets changed.
remove this section altogether

I added a comment tagging you there but idk why you can't access it.

@ron-debajyoti You don't need to worry about that :)
I should've told you(sorry, I didn't) but the docs will be generated by the AsyncAPI bot. So, In that case, we will probably ask you to revert your documentation changes(but keeping the configs), and once it will be merged, the new docs will be generated by the bot.

Yup. Go ahead. Then I'll approve and merge :)

@aayushmau5 Done. Do give a final check if required.

@aayushmau5 Also I would like to say thanks a lot for guiding me throughout the process. Looking forward to more contributions in AsyncAPI !


Dotnet 8 preview

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (954992e) 94.12% compared to head (f03185e) 94.01%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #205      +/-   ##
==========================================
- Coverage   94.12%   94.01%   -0.12%
==========================================
  Files          85       85
  Lines        5178     5178
  Branches      488      488
==========================================
- Hits         4874     4868       -6
- Misses        177      181       +4
- Partials      127      129       +2

see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@shacharPash can you tell me why these tests failed?

@shacharPash can you tell me why these tests failed?

@chayim It was flaky

Pleae open a bug for the flaky tests - also let's merge this through please. dotnet 8 just came out so good timing.
Anything else to release support this in our package?


Support more GTP commands

in particular:

final_score
final_status_list

maybe some of the time commands to make the CGOS player a little more robust.

If you're interested in digging into the code, final_score should be easy to implement, but final_status_list might be quite hard :)

final_score the easy implementation is done. final_status_list is a larger work item.


fix user data not being updated sometimes

resolves https://github.com/kthcloud/go-deploy/issues/441


dangerjs liquibase update

Issue
https://gravitee.atlassian.net/browse/APIM-XXXX
Description
A small description of what you did in that PR.
Additional context

Fails

:no_entry_sign:

Danger failed to run dangerfile.ts.

Error HttpError
Invalid request.

No subschema in "oneOf" matched.
"body", "path" weren't supplied.
"body", "in_reply_to" weren't supplied.
"position" is not a permitted key.
"body", "line", "path" weren't supplied.
"position" is not a permitted key.
"body", "path", "subject_type" weren't supplied.
HttpError: Invalid request.

No subschema in "oneOf" matched.
"body", "path" weren't supplied.
"body", "in_reply_to" weren't supplied.
"position" is not a permitted key.
"body", "line", "path" weren't supplied.
"position" is not a permitted key.
"body", "path", "subject_type" weren't supplied.
    at /home/circleci/project/.circleci/danger/node_modules/@octokit/request/dist-node/index.js:86:21
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async addPrComment (dangerfile.ts:42:5)
    at async postMessages (dangerfile.ts:32:9)
    at async check (dangerfile.ts:20:13)
    at async Promise.all (index 0)

Dangerfile
77| }
78|
-----------------------^

  Generated by :no_entry_sign: dangerJS against c26304efeef99315c44bb97ef8744907a5dcce05

Fails

:no_entry_sign:

Danger failed to run dangerfile.ts.

Error TypeError
messages is not iterable
TypeError: messages is not iterable
    at postMessages (dangerfile.ts:29:27)
    at check (dangerfile.ts:20:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)

Dangerfile
24|         }
25|     }
26| }
27|
28| async function postMessages(messages) {
-----------------------------^
29|     for (const message of messages) {
30|         await addPrComment(message);
31|     }
32| }

  Generated by :no_entry_sign: dangerJS against 45e114affc5a924eb9deaec2adea4778fcd39fe9

Fails

:no_entry_sign:

Danger failed to run dangerfile.ts.

Error TypeError
messages is not iterable
TypeError: messages is not iterable
    at postMessages (dangerfile.ts:30:27)
    at check (dangerfile.ts:21:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)

Dangerfile
25|         }
26|     }
27| }
28|
29| async function postMessages(messages) {
-----------------------------^
30|     for (const message of messages) {
31|         await addPrComment(message);
32|     }
33| }

  Generated by :no_entry_sign: dangerJS against d7a5b44f7d5ace0432b6ff5fc5f1255cbecc036d


1.0 AND V2 SOURCE CODE

WHERE IS THE SOURCE CODE FOR 1.0 AND V2??? I NEED THE SOURCE CODE FOR OLDER VERSIONS OF THE SHAGGY MOD

ok

(EASYMONEY.CO.JP) GIVING AWAY FREE ROBUX!!!  (FREE-ROBUX.COM) 👌 🌈 EXTREMELY EASY!! FREE MONEY GENERATOR!!!!!! 👈 FREE BANDICAM CRACK!!? 😎 👊 🥴 😤 🤒 🤑 🤔 FREE ROBUX THAT ACTUALLY WORKS!???????? NO VERIFICATION NEEDED!?!?!?!? 😱 😬 ⚠ I CAN'T BELIEVE ROBLOX DID THIS????? 🚗 🧐 👍 FREE STEAM GAMES!!???!! STUPIDLY EASY!!??? FREE BANDICAM CRACK!!?  PERFECT AMERICAN STYLE CHEESE BURGER!! 🖐 🤑 🤞 😳 VERY TRUE!?!?!?!? %100 🧐 GET PRANKED!!! 💵 😄 😍 👊 😣 INSANE REACTION!???   VERY TRUE!?!?!?!? %100 🤒 USING LIME TEST WINDOWS.EXE! 👀 👏 🤞 #roblox 🌈 👈 STILL WORKING!! VERY TRUE!?!?!?!? %100 👍 FREE BANDICAM CRACK!!? 🤒 FREE MONEY GENERATOR!!!!!! PERFECT AMERICAN STYLE CHEESE BURGER!! AMAZING BREAD MAKING PROCESS!?!?  CLICK THE LINK BELOW! EXTREMELY EASY!! 🖕 🤪 🤪 ☝ 👀 GVING AWAY 1,000,000 FREE ROBUX TODAY!! CLICK THE LINK BELOW! 🧐 😫 FREE MALWARE BYTES CRACK!! GET PRANKED!!! 🥴 TOP 5 GHOSTS CAUGHT ON CAMERA 😰 😲 🤞 GONE WRONG! (POLICE CALLED 😋 😄 ☝ 📵 🖐 (EASYMONEY.CO.JP) VERY TRUE!?!?!?!? %100 🙃 😱 🤨 😟 😋 🤏 😑 😟 (REAL) GET FREE ROBUX NOW!!!11 🤞 🤣 (NOT ILLEGAL) FREE ROBUX!!! (BEATINGCHILDREN.CF) 100% REAL! 😡 👋 👏 🧐 STUPIDLY EASY!!??? FREE MALWARE BYTES CRACK!! ☝ 😵 👈 🤡 🖐 💵 😜 (FORTBUXGENERATOR.COM) 👊 🤡 💵 AMAZING BREAD MAKING PROCESS!?!? 😎 🖐 USING LIME TEST WINDOWS.EXE! GET IT WHILE IT LAST! <--- 👋 ☝ 😄 🤞 💵 🤓 🖕 EXTREMELY EASY!! 🤗 #roblox 😁 😏 👀 🤞 😊 NEW GLITCH THAT GIVES FREE ROBUX (2022)!!! HOW I GOT 100,000 REBUX FOR 100% FREE!!!! ✋ ✋ ☝ NEW GLITCH THAT GIVES FREE ROBUX (2022)!!! 👊 FREE FORTNITE VBUX!!!!!111 😵 🤞 ☝ 🤏 (MALWARE.COM) 🤏 PERFECT AMERICAN STYLE CHEESE BURGER!! 🤏 😚 😎 🌈 VERY TRUE!?!?!?!? %100 👊 😫

wouldn't they be in the git history?


Bind fails to update records unless zone files are deleted

Only the journal files need to be deleted.

Quick and easy fix:

Check if the zone file was updated, if yes delete the journal.

Better fix:

Check if there are any updates to the zone definitions.  If yes, update the zone file, and delete the journal.

Best fix:

If the zone file exists, dynamically update zone definition (how?)
Only install zone files for newly created zones

Another possibility, use a tag to regenerate the zone file and delete the journal.
Also have a check if zone file exists, if not install zone file, otherwise do nothing unless the regeneration tag is used.

Removing from 0.2 milestone: Temporary fix in place.  More permanent solution still in the works.

Or the most simple solution of all, set force to "no" for the creation of zone files.  Role now only creates the zone file if it doesn't previously exist.  Everything will be updated using nsupdate from that point on.
Closing

Or the most simple solution of all, set force to "no" for the creation of zone files.  Role now only creates the zone file if it doesn't previously exist.  Everything will be updated using nsupdate from that point on.
Closing


PhantomJS tests fail on teaspoon v1.0

Hi, just upgraded (thank you for the excellently detailed upgrading guide), and when I try to execute the JS specs from the command line, I get this exception:
$ rake teaspoon                                                                                [2.2.2]
Puma 2.11.2 starting...
* Min threads: 0, max threads: 16
* Environment: test
* Listening on tcp://<IP_ADDRESS>:57812
rake aborted!
NoMethodError: undefined method `path' for Teaspoon::Driver::Phantomjs:Class
-e:1:in `<main>'
Tasks: TOP => teaspoon
(See full trace by running task with --trace)

This is the backtrace:

rake aborted!
NoMethodError: undefined method `path' for Teaspoon::Driver::Phantomjs:Class
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/driver/phantomjs.rb:54:in `executable'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/driver/phantomjs.rb:35:in `run'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/driver/phantomjs.rb:27:in `run_specs'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:55:in `run_specs'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:44:in `block in execute_without_handling'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:42:in `each'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:42:in `inject'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:42:in `execute_without_handling'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:27:in `execute'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/teaspoon/console.rb:23:in `failures?'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/teaspoon-1.0.0/lib/tasks/teaspoon.rake:12:in `block in <top (required)>'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:240:in `call'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:235:in `each'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `each'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/rake-10.4.2/lib/rake/application.rb:75:in `run'
/Users/geoff/cortex/bin/rake:8:in `<top (required)>'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:268:in `load'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:268:in `block in load'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:240:in `load_dependency'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:268:in `load'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Users/geoff/.rbenv/versions/2.2.2/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
-e:1:in `<main>'
Tasks: TOP => teaspoon

After a quick look at the source, tt looks like #path isn't defined on Teaspoon::Driver::PhantomJS: https://github.com/modeset/teaspoon/blob/master/lib/teaspoon/driver/phantomjs.rb#L54

Yeah, I had the same error when trying to upgrade. I'm using the phantomjs gem and resolved the issues related to changes listed in the release notes.

:+1: Thanks for the quick fix!

This fix also resolved the issue for me. (Ran off master, as 1.0.1 isn't on Rubygems yet.) Thanks very much.

Excellent! 1.0.1 should be on RubyGems now.


[Bug]: greetings.yml is not correctly configured

What happened?
I found a BUG 🐞 such that when someone raise issue greetings.yml is not generating greeting message.
Add screenshots
Add screenshots
What browsers are you seeing the problem on?
No response
Code of Conduct

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

Assign this issue to me

Hey @harsh432004
Actually, i just accepted your PR but this "greetings.yml" also not working till now.
check it out what's the problem is generated?


undo is broken

test case:

open Xi
type a few letters
activate Edit > Undo or hit ⌘Z

expected result:

the letters are removed again

actual result:

nothing happens

Doesn't repro for me. I wouldn't be surprised if there were something going on, but I can't see it.

hmm... I did a clean build on Xcode 8.2.1 on macOS 10.11.6 with the latest Rust.
Also I tried to implement undo for xi-gtk on Linux and it never worked.

Undo doesn't work indeed. xi-core dumps got update notification Undo on stderr but nothing comes out of it.

I'm able to repro in release build, but not in debug. Odd. In any case, this is obviously a real issue.

It looks like the insert inside the debug_assert is to blame here.

@eyelash Thanks for tracking that down! It was on my list of things to look into, but I didn't get around to it yet.


Map method in Dataset doesn't exist

According to the documentation a map method should exist in the Dataset type, but it doesn't. Either the documentation or the implementation is incorrect.

Fixed in https://github.com/RubixML/ML/pull/296

I went ahead and removed the old docs


[TechDocs] Adjust theme styles

Signed-off-by: Camila Belo<EMAIL_ADDRESS>Hey, I just made a Pull Request!

Fixes https://github.com/backstage/backstage/issues/6289
Styles tweaks as a side effect of https://github.com/backstage/mkdocs-techdocs-core/pull/50

See below how the page appearance is after changes:

Light theme
Dark theme

How to test?

Clone the mkdocs-techdocs-core project
Check out to the branch bump-mkdocs-material
Install the plugin locally:

pip install -e .

Make sure you have installed version 0.2.3:

pip show mkdocs-techdocs-core

As we are going to test it locally, you need to have your environment configured like here

Navigate to the backstage repository folder

Also check out to the branch bump-mkdocs-material

Run techdocs-cli locally in development mode:

yarn techdocs-cli:dev serve --no-docker

Start the local embedded app in another terminal:

yarn workspace techdocs-cli-embedded-app start

Finally access the docs page:
http://localhost:3000/docs/default/component/local

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

Dawned on me that ofc we are ping'd, since we're listed as owners everywhere now. You should still be able to merge this without a 🟢 from reviewers though so will keep that in mind :p

Thanks for the excellent instructions on how to test this PR!
I'm surprised to see things working with 3 major versions bumped 😄 however I noticed the resizing to smaller screens broke in a way that the sidebar overlaps with the content, see screenshot below:

Thanks for testing @ottosichert , could you share the breakpoint you tested?

@ottosichert fixed here: https://github.com/backstage/backstage/pull/9569/commits/e2070bc7104101b1ee830264dba803898a4ec4c8.


A2C agent doesn't act

Hi,
For some reason when I try to run the trained a2c agent in CARLA it doesn't take any actions, just sits there doing nothing. These are my terminal outputs:
(rl_gym_book) amakri@amakri-Zephyrus-M-GM501GS:~/Hands-On-Intelligent-Agents-with-OpenAI-Gym-master/ch8$ python a2c_agent.py --env Carla-v0 --gpu-id 0
Loaded Advantage Actor-Critic model state from trained_models/A2C_Carla-v0.ptm  which fetched a best mean reward of: -0.08981079755592294  and an all time best reward of: 1.0340544147491457
Initializing new Carla server...
Error connecting: (localhost:56639) failed to connect: [Errno 111] Connection refused, attempt 0
Start pos 36 ([0.0, 3.0]), end 40 ([0.0, 3.0])
Starting new episode...
actor0:Episode#:0 	 ep_reward:5.085380562726176e-10 	 mean_ep_rew:5.085380562726176e-10	 best_ep_reward:1.0340544147491457
ERROR: tcpserver 56641 : error reading message: End of file
Start pos 36 ([0.0, 2.0]), end 40 ([-1.0, 2.0])
Starting new episode...
actor0:Episode#:1 	 ep_reward:1.574227504116339e-09 	 mean_ep_rew:1.0413827801944784e-09	 best_ep_reward:1.0340544147491457
ERROR: tcpserver 56641 : error reading message: End of file
Start pos 36 ([0.0, 2.0]), end 40 ([-1.0, 2.0])
Starting new episode...
actor0:Episode#:2 	 ep_reward:1.461007756921785e-20 	 mean_ep_rew:6.94255186801189e-10	 best_ep_reward:1.0340544147491457
ERROR: tcpserver 56641 : error reading message: End of file
Start pos 36 ([0.0, 2.0]), end 40 ([-1.0, 2.0])
Starting new episode...
actor0:Episode#:3 	 ep_reward:-1.8116123954554487e-19 	 mean_ep_rew:5.206913900556014e-10	 best_ep_reward:1.0340544147491457
ERROR: tcpserver 56641 : error reading message: End of file
Start pos 36 ([0.0, 2.0]), end 40 ([-1.0, 2.0])
Starting new episode...
actor0:Episode#:4 	 ep_reward:8.738404666586943e-10 	 mean_ep_rew:5.9132120537622e-10	 best_ep_reward:1.0340544147491457
ERROR: tcpserver 56641 : error reading message: End of file
Start pos 36 ([0.0, 2.0]), end 40 ([-1.0, 2.0])
Starting new episode...
Any ideas on why this is happening?

I encountered the same problem.

Loaded Advantage Actor-Critic model state from trained_models/A2C_Carla-v0.ptm which fetched a best mean reward of: -0.08981079755592294

You will probably have to train the agent for more episodes.
The mean reward of  -0.08981079755592294 signifies that the agent hasn't learned much. It's likely that, the the trained agent "brain"/model, has learned only to stay put to avoid collisions or something so that's why it's probably staying still.

That's true, but it is still loading the trained A2C_Carla-v0.ptm agent for the train mode correct? It has the same behaviour in test mode unfortunately =\ it simply sits there not taking any actions.

In that case, the agent needs to be trained more.
If you are observing the same behavior for several episodes, its very likely that the trained agent "brain"/model seems to have learnt only so much (to stay still to avoid collisions).

From: Alexander Makrigiorgos<EMAIL_ADDRESS>Sent: Tuesday, May 7, 2019 8:16:18 PM
To: PacktPublishing/Hands-On-Intelligent-Agents-with-OpenAI-Gym
Cc: Praveen Palanisamy; Comment
Subject: Re: [PacktPublishing/Hands-On-Intelligent-Agents-with-OpenAI-Gym] A2C agent doesn't act (#24)
That's true, but it is still loading the trained A2C_Carla-v0.ptm agent for the train mode correct? It has the same behaviour in test mode unfortunately =\ it simply sits there not taking any actions.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/PacktPublishing/Hands-On-Intelligent-Agents-with-OpenAI-Gym/issues/24#issuecomment-490299911, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABEMVMVVD4LFX33ZVICMG5LPUILVFANCNFSM4HLGF3VQ.

But, it is strange if you don't see the vehicle moving at all. It is supposed to be trying several actions and each will produce different trajectories of motion good or bad.


Remove using namespace std

I also converted this to an issue to show support for this idea by @bcaddy. I think it would make a good easy task for a hack day as well.

This would allow us to enable the google-build-using-namespace clang-tidy check

Closed by #245


The last version of HA [2024.1.6] not work with pellematic

The service pellematic is unaviable after upgrade of Home assistant [2024.1.6].
Do you have the same problem?

For me it works fine.

I will verify my config, maybe a modify IP with DHCP...
I search to verify the url of the json, but i dont see the file to change it...

it s ok... it s me sorry, The IP have change......

I use static IPs for all my IoT-Devices. This works good 👍 Ok thanks for the info. So I will close this issue as solved.


Embedly API Key Security

In the readme, it suggests setting the Embedly key like this:

$('#content a').embedly({key: 'Your Embedly Key'});

Maybe I'm missing something obvious here, but if I set my Embedly API key in my client-side JavaScript, what's to stop somebody else from stealing it? Couldn't somebody easily do the following?

Write a script to crawl websites and look for jquery.embedly.min.js.
Download all of the JavaScripts associated with those sites.
Match /embedly\([^)]*key:\s*['"]([^'"]+)['"]/
Grab those keys and go to town.

Hi Landon,
If this is a concern for you, the best option is to use a backend proxy that will shield your key.
In practice, this is is not an issue. We have never seen an instance of someone going to town on another person's key. Embedly's service is free at base levels.
If you have further concerns, please reach out to<EMAIL_ADDRESS>as this is more of a general case issue rather than an Embedly jQuery issue.
Best,
Sean


Refunds - This endpoint does not support the merchant facade

According to REST API docs, we should be able to get a list of all the (eventual) refunds connected to an invoice using the following method:
GET /invoices/:invoiceId/refunds
Returns the status of all refunds on an invoice.
Parameters 	none
Facades 	merchant

Unfortunately, the request always returns the same error, even if properly configured (merchant token used, request properly signed, headers set correctly).
{
	"error": "This endpoint does not support the `merchant` facade"
}

Request/Response dump (tokens cleared):
Preparing request to https://test.bitpay.com/invoices/FV5ppbJbLsurQS49xxxxxx/refunds?token=mybeautifulmerchanttoken
* Enable automatic URL encoding
* Enable SSL validation
* Enable cookie sending with jar of 2 cookies
* Found bundle for host test.bitpay.com: 0x7fb49843a570 [can pipeline]
* Re-using existing connection! (#0) with host test.bitpay.com
* Connected to test.bitpay.com (<IP_ADDRESS>) port 443 (#0)
> GET /invoices/FV5ppbJbLsurQS49xxxxxx/refunds?token=mybeautifulmerchanttoken HTTP/1.1
> Host: test.bitpay.com
> User-Agent: insomnia/5.3.6
> Accept: */*
> Accept-Encoding: deflate, gzip
> Cookie: connect.sid=s%3Ap3514ROJEWMWEyzzIUJ2TSlBpGF4P7lI.DsOQCBnl6VTxFqD9MOKYAa7RhPiNzdsX1LGKLPESbYc; __cfduid=d3191f39dad70158e5eb0684f12bfdf6a1497906362
> x-identity: 02b8e34a199753691b4af76f2fedf6f09f9d720a2812546c8960a6d32b84xxxxxx
> x-signature:<PHONE_NUMBER>e37f03b0318e7955e8b8f6c82ae5e069c8e3b1f608f5011fc0570f8cee9d242702204e22251d8a79d57a232317fa951e31ec9eb82f5735a2bdc9f08a2e5e33xxxxxx
> content-type: application/json
> x-accept-version: 2.0.0
< HTTP/1.1 401 Unauthorized
< Date: Mon, 19 Jun 2017 21:16:34 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 64
< Connection: keep-alive
< Strict-Transport-Security: max-age=31536000
< X-Download-Options: noopen
< X-Content-Type-Options: nosniff
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Methods: HEAD,GET,POST,PUT,DELETE,OPTIONS
< Access-Control-Allow-Headers: Content-Type,Authorization,Content-Length,X-Requested-With,Cache-Control,X-Accept-Version,x-signature,x-pubkey,x-identity,cf-connecting-ip
< ETag: W/"40-9c979e5c"
< Server: cloudflare-nginx
< CF-RAY: 371982994c1a3dc5-MXP

* Received 64 B chunk
* Curl_http_done: called premature == 0
* Connection #0 to host test.bitpay.com left intact

Response is:
{
	"error": "This endpoint does not support the merchant facade"
}

Thanks in advance

{
	"error": "This endpoint does not support the merchant facade"
}

It does work but the token architecture is a bit more complex.
Essentially there are 2 types of token:

API token: That's the one you obtained during the initial pairing process, for a specific facade (in this case 'merchant')
resource token: this one is derived based on a resource created (an invoice for instance) and the API token used to create this resource. This token is returned in the response request to the invoice creation (you can always fetch it via a GET to invoices/invoiceId).

So in order to initiate a refund, you need 2 calls. For the adjustments/refunds call, you need to fetch first the resource token derived for a specific invoice when sending the POST request (see getInvoice() function on /src/Bitpay/Client/Client.php)
It's the same approach with all resources. For instance if you want to get the report to do the reconciliation for a specific bank settlements (GET/settlements/:settlementId/reconciliationReport) you need to fetch first the token created for the specific 'settlementId'.


Feature Request: Additional fn signature for React's useAtom to return focused [value, updater]

I was wondering if you might consider extending the useAtom hook to take a focusSelector: string | function as an optional second parameter. It might provide a familiar syntax for those migrating away from useState, and reduce down on the number of variables you need to name and maintain. As an example, this is a simple wrapper illustrating the point...
// Hook
const useAtomWrapper = (atom, selector) => {
  const result = selector ? atom.focus(selector) : atom;
  return [ useAtom(result), result.update ];
}

// Usage
const Component = () => {
  const $state = useSetup(() => create({ count: 0, theme: 'dark' }));

  const [ count, setCount ] = useAtomWrapper($state, 'count');
  const [ theme, setTheme ] = useAtomWrapper($state, s => s.theme);

  return <button className={theme} onClick={() => setCount(v => v+1)}>{count}</button>;
}

Without the above convenience wrapper, I found myself needing to produce a lot of similarly named intermediate Atoms and it wasn't always instinctive which to read from and which to update with unless you are really careful with your naming. For example:
const Component = () => {
  const $state = useSetup(() => create({ count: 0, theme: 'dark' }));

  const $count = $state.focus('count');
  const $theme = $state.focus(s => s.theme);

  const count = useAtom($count);
  const theme = useAtom($theme);

  return <button className={theme} onClick={() => $count.update(v => v+1)}>{count}</button>;
}

Would love to know your thoughts on this.
Cheers,
Jon

Hi @is-jonreeves , thank you for your valuable feedback!
Why not use the following coding style?
const Component = () => {
  const $state = useSetup(() => create({ count: 0, theme: 'dark' }));
  const { count, theme } = useAtom($state);

  return <button className={theme} onClick={() => $state.focus('count').update(v => v+1)}>{count}</button>;
}

I guess inlining $state.focus('count').update(v => v+1) could feel too long, but one of the ideas behind xoid was not needing to generate proper names as "setCount", and simply using "$count.set" while working with local state. However I totally understand that it's a matter of preference, and I think that yours is a good suggestion.
However, currently useAtom's second argument is reserved for the following:
const CounterModel = (value: number) =>
  create(value, (atom) => ({
    increment: () => atom.update((s) => s + 1),
    decrement: () => atom.update((s) => s - 1),
  }))

const [count, { increment, decrement }] = useAtom(() => CounterModel(0), true)

This can be considered as a shorthand for:
const $counter = useSetup(() => CounterModel(0))
const count = useAtom($counter)
const { increment, decrement } = $counter.actions

A few latest beta versions of @xoid/react have this feature. Back then I wasn't sure of this feature, so I didn't document this anywhere, but I'll document it soon.


Jupyter notebook: idea for easier cell merge and bug in "undo cell merge"

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.63.2
OS Version: Mac OS 12.0.1 (21A559)

Idea: When multiple cells are selected, it should be possible to merge only the selected cells.
Currently, it is only possible to merge all selected + previous or all selected + next cell.
Bug: When one uses the "Undo" button, the cell with the merged code keeps all the code, see screen recording.
However, this merging process should be reversed.
Steps to Reproduce:
https://user-images.githubusercontent.com/44469195/146681380-9a7df938-3c80-4dd5-95da-986345280205.mov

@kolibril13 thanks for your feedback. Note that Join Cells with Previous/Next are different from Merge Cells (which we don't support yet in VS Code but can be a good extension candidate). With that being said, it's a valid bug that undo doesn't revert.

Should be fixed now.


Container with Valheim Plus Enabled now throwing errors like : NullReferenceException: Object reference not set to an instance of an object

Very basic container setup here following the defaults. When enabling valheim plus the docker logs fill up with repeated:
Sep 27 16:59:03 /supervisord: valheim-server [Warning:  HarmonyX] AccessTools.DeclaredMethod: Could not find method for type Chat and name OnNewChatMessage and parameters (UnityEngine.GameObject, long, UnityEngine.Vector3, Talker+Type, string, string)
Sep 27 16:59:03 /supervisord: valheim-server ArgumentException: Undefined target method for patch method static bool ValheimPlus.GameClasses.Chat_AddInworldText_Patch::Prefix(Chat& __instance, UnityEngine.GameObject go, long senderID, UnityEngine.Vector3 pos, Talker+Type type, string user, string text)
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.PatchClassProcessor.PatchWithAttributes (System.Reflection.MethodBase& lastOriginal) [0x00047] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.PatchClassProcessor.Patch () [0x0006a] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server Rethrow as HarmonyException: Patching exception in method null
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.PatchClassProcessor.ReportException (System.Exception exception, System.Reflection.MethodBase original) [0x0006c] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.PatchClassProcessor.Patch () [0x00095] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.Harmony.b__11_0 (System.Type type) [0x00007] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.CollectionExtensions.Do[T] (System.Collections.Generic.IEnumerable1[T] sequence, System.Action1[T] action) [0x00014] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.Harmony.PatchAll (System.Reflection.Assembly assembly) [0x00006] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at HarmonyLib.Harmony.PatchAll () [0x0001b] in <474744d65d8e460fa08cd5fd82b5d65f>:0
Sep 27 16:59:03 /supervisord: valheim-server   at ValheimPlus.ValheimPlusPlugin.Awake () [0x00048] in <8d21b3cade284489bb9f6cebda2f9f8b>:0
Sep 27 16:59:03 /supervisord: valheim-server UnityEngine.GameObject:Internal_AddComponentWithType(Type)
Sep 27 16:59:03 /supervisord: valheim-server UnityEngine.GameObject:AddComponent(Type)
Sep 27 16:59:03 /supervisord: valheim-server BepInEx.Bootstrap.Chainloader:Start()
Sep 27 16:59:03 /supervisord: valheim-server UnityEngine.Application:.cctor()
Sep 27 16:59:03 /supervisord: valheim-server [Message:   BepInEx] Chainloader startup complete
Sep 27 16:59:03 /supervisord: valheim-server 09/27/2022 16:59:03: Starting to load scene:start
Sep 27 16:59:03 /supervisord: valheim-server ERROR: Shader UI/Default shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:03 /supervisord: valheim-server Couldn't create a Convex Mesh from source mesh "default" within the maximum polygons limit (256). The partial hull will be used. Consider simplifying your mesh.
Sep 27 16:59:03 /supervisord: valheim-server Couldn't create a Convex Mesh from source mesh "default" within the maximum polygons limit (256). The partial hull will be used. Consider simplifying your mesh.
Sep 27 16:59:05 /supervisord: valheim-server DEBUG - [156] - Waiting for server to listen on UDP port 2456
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Legacy Shaders/VertexLit shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Unsupported: 'Standard (Specular setup)' - All subshaders removed
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Did you use #pragma only_renderers and omit this platform?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader If subshaders removal was intentional, you may have forgotten turning Fallback off?
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Standard (Specular setup) shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Unsupported: 'Standard (Specular setup)' - All subshaders removed
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Did you use #pragma only_renderers and omit this platform?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader If subshaders removal was intentional, you may have forgotten turning Fallback off?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Unsupported: 'Standard' - All subshaders removed
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Did you use #pragma only_renderers and omit this platform?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader If subshaders removal was intentional, you may have forgotten turning Fallback off?
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Standard shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Unsupported: 'Standard' - All subshaders removed
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Did you use #pragma only_renderers and omit this platform?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader If subshaders removal was intentional, you may have forgotten turning Fallback off?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Unsupported: 'Autodesk Interactive' - All subshaders removed
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Did you use #pragma only_renderers and omit this platform?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader If subshaders removal was intentional, you may have forgotten turning Fallback off?
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Autodesk Interactive shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Unsupported: 'Autodesk Interactive' - All subshaders removed
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader Did you use #pragma only_renderers and omit this platform?
Sep 27 16:59:07 /supervisord: valheim-server WARNING: Shader If subshaders removal was intentional, you may have forgotten turning Fallback off?
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Legacy Shaders/Particles/Additive shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Legacy Shaders/Particles/Alpha Blended shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Legacy Shaders/Particles/Alpha Blended Premultiply shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Unlit/Color shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server ERROR: Shader Lux Lit Particles/ Bumped shader is not supported on this GPU (none of subshaders/fallbacks are suitable)
Sep 27 16:59:07 /supervisord: valheim-server HDR Render Texture not supported, disabling HDR on reflection probe.
Sep 27 16:59:07 /supervisord: valheim-server HDR Render Texture not supported, disabling HDR on reflection probe.
Sep 27 16:59:07 /supervisord: valheim-server Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
Sep 27 16:59:07 /supervisord: valheim-server UnloadTime: 4.659300 ms
Sep 27 16:59:07 /supervisord: valheim-server Only custom filters can be played. Please add a custom filter or an audioclip to the audiosource (Amb_MainMenu).
Sep 27 16:59:07 /supervisord: valheim-server HDR Render Texture not supported, disabling HDR on reflection probe.
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Get create world "Fun Times"
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Using environment steamid 892970
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Using steam APPID:892970
Sep 27 16:59:07 /supervisord: valheim-server [S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
Sep 27 16:59:07 /supervisord: valheim-server CAppInfoCacheReadFromDiskThread took 3 milliseconds to initialize
Sep 27 16:59:07 /supervisord: valheim-server Setting breakpad minidump AppID = 892970
Sep 27 16:59:07 /supervisord: valheim-server [S_API FAIL] Tried to access Steam interface SteamNetworkingUtils003 before SteamAPI_Init succeeded.
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Server ID<PHONE_NUMBER>7409920
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Authentication:k_ESteamNetworkingAvailability_Waiting
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Steam game server initialized
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Using default prefs
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Valheim version:0.211.7
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Render threading mode:SingleThreaded
Sep 27 16:59:07 /supervisord: valheim-server MissingFieldException: Field 'FejdStartup.m_serverPlayerLimit' not found.
Sep 27 16:59:07 /supervisord: valheim-server   at (wrapper dynamic-method) FejdStartup.DMDFejdStartup::Awake(FejdStartup)
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Missing audio clip in music respawn
Sep 27 16:59:07 /supervisord: valheim-server 09/27/2022 16:59:07: Builder started
Sep 27 16:59:08 /supervisord: valheim-server DllNotFoundException: party
Sep 27 16:59:08 /supervisord: valheim-server   at (wrapper managed-to-native) PartyCSharpSDK.Interop.PFPInterop.PartyInitialize(byte[],PartyCSharpSDK.Interop.PARTY_HANDLE&)
Sep 27 16:59:08 /supervisord: valheim-server   at PartyCSharpSDK.SDK.PartyInitialize (System.String titleId, PartyCSharpSDK.PARTY_HANDLE& handle) [0x00006] in <4d5b8d2a94a347d09410b73b7f7ad47f>:0
Sep 27 16:59:08 /supervisord: valheim-server   at PlayFab.Party.PlayFabMultiplayerManager.InitializeImpl () [0x000be] in <4d5b8d2a94a347d09410b73b7f7ad47f>:0
Sep 27 16:59:08 /supervisord: valheim-server   at PlayFab.Party.PlayFabMultiplayerManager._Initialize () [0x0000a] in <4d5b8d2a94a347d09410b73b7f7ad47f>:0
Sep 27 16:59:08 /supervisord: valheim-server   at PlayFab.Party.PlayFabMultiplayerManager.Start () [0x00000] in <4d5b8d2a94a347d09410b73b7f7ad47f>:0
Sep 27 16:59:08 /supervisord: valheim-server The shader Hidden/Dof/DepthOfFieldHdr (UnityEngine.Shader) on effect Main Camera (UnityStandardAssets.ImageEffects.DepthOfField) is not supported on this platform!
Sep 27 16:59:08 /supervisord: valheim-server The image effect Main Camera (UnityStandardAssets.ImageEffects.DepthOfField) has been disabled as it's not supported on the current platform.
Sep 27 16:59:08 /supervisord: valheim-server The shader Hidden/SunShaftsComposite (UnityEngine.Shader) on effect Main Camera (UnityStandardAssets.ImageEffects.SunShafts) is not supported on this platform!
Sep 27 16:59:08 /supervisord: valheim-server The shader Hidden/SimpleClear (UnityEngine.Shader) on effect Main Camera (UnityStandardAssets.ImageEffects.SunShafts) is not supported on this platform!
Sep 27 16:59:08 /supervisord: valheim-server The image effect Main Camera (UnityStandardAssets.ImageEffects.SunShafts) has been disabled as it's not supported on the current platform.
Sep 27 16:59:08 /supervisord: valheim-server 09/27/2022 16:59:08: Game server connected
Sep 27 16:59:08 /supervisord: valheim-server NullReferenceException: Object reference not set to an instance of an object
Sep 27 16:59:08 /supervisord: valheim-server   at ZInput.IsGamepadActive () [0x00000] in <6011e53a94c64257871f5143178823ac>:0
Sep 27 16:59:08 /supervisord: valheim-server   at UIGroupHandler.Update () [0x0009a] in <408fb2feebfa4a519b8eeaef491b5d76>:0
Sep 27 16:59:08 /supervisord: valheim-server Unloading 14 unused Assets to reduce memory usage. Loaded Objects now: 105718.
Sep 27 16:59:08 /supervisord: valheim-server Total: 76.911900 ms (FindLiveObjects: 5.563100 ms CreateObjectMapping: 4.527500 ms MarkObjects: 66.584500 ms  DeleteObjects: 0.236000 ms)
Sep 27 16:59:10 /supervisord: valheim-server 09/27/2022 16:59:10: UI Group status changed Menu = True
Sep 27 16:59:10 /supervisord: valheim-server NullReferenceException: Object reference not set to an instance of an object
Sep 27 16:59:10 /supervisord: valheim-server   at ZInput.IsGamepadActive () [0x00000] in <6011e53a94c64257871f5143178823ac>:0
Sep 27 16:59:10 /supervisord: valheim-server   at UIGroupHandler.Update () [0x0009a] in <408fb2feebfa4a519b8eeaef491b5d76>:0
Simple docker-compose below
version: "3"
services:
valheim:
image: ghcr.io/lloesche/valheim-server
cap_add:
- sys_nice
volumes:
- $HOME/valheim-server/config:/config
- $HOME/valheim-server/data:/opt/valheim
ports:
- "2456-2457:2456-2457/udp"
environment:
- SERVER_NAME="Marshall Server"
- WORLD_NAME="Fun Times"
- SERVER_PASS=notthepassword
- VALHEIM_PLUS=true
restart: always
stop_grace_period: 2m

After more research, this might not be anything you can do anything about.
https://www.nexusmods.com/valheim/mods/4?tab=bugs
Its the top post here and appears to be a valheim plus problem.

I was able to downgrade my Valheim dedicated server to the previous version by adding the following to my valheim.env docker environment file and then stopping, then removing the existing running docker container, then starting it back up.
You also need to downgrade your Valheim client in Steam by joining the Beta "default_old"
STEAMCMD_ARGS=-beta default_old

That fix worked for me from when this became an issue until last night, but no longer works. The same error is present again

This works for me, and temporarily fixes breaking under the new patch
https://github.com/valheimPlus/ValheimPlus/issues/709#issuecomment-1267820184

I can confirm it works, running 0.211.8 (last version pulled from this image while I am writing) on the server, <IP_ADDRESS> V+ alpha version, and beta "default_old" on Steam to stick on the 0.211.8 (0.211.9 out this morning).
Actual problem is that this image download automatically last V+ release, but in this case we have to overwrite the release V+ dll with the alpha version. If we had an env var that could stick with this behaviour (default is to download last version), but turning it to false would prevent pulling last version. What is your opinion on it @lloesche ?
Other (minor) problem is the pull limit from the Github API, if I reboot my server times multiple times, I can quickly reach the threshold, and if I got it well, the process exits. But maybe I'm doing something wrong here.


uv not installing build dependencies

A minimal code snippet that reproduces the bug :
uv pip install git+https://github.com/nerfstudio-project/gsplat

  File "<string>", line 152, in <module>
  File "<string>", line 33, in get_extensions
ModuleNotFoundError: No module named 'torch'
---
  Caused by: This error likely indicates that git+https://github.com/nerfstudio-project/gsplat depends on torch, but doesn't declare it as a build dependency. If git+https://github.com/nerfstudio-project/gsplat is a first-party package, consider adding torch to its `build-system.requires`. Otherwise, `uv pip install torch` into the environment and re-run with `--no-build-isolation`.

However when using pip with pip install git+https://github.com/nerfstudio-project/gsplat
Everything installs correctly!

Ofcourse when I install torch and use --no-build-isolation then uv installs it as well.
I think that uv fails to install build dependencies from setup.py (install-requires).
I am python build tool newbie, it could be that I am somehow mistaken

This is another case of #2252.


Fixes #457 fix performance issue in parallel tests

Changes Unknown when pulling 9cb0e033c4033b8b9a32baa0547724100f510300 on issue-457-fix-performance-of-parallel-tests into ** on master**.

Codecov Report

Merging #502 into master will decrease coverage by 0.07%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #502      +/-   ##
============================================
- Coverage     58.77%   58.69%   -0.08%
+ Complexity      690      689       -1
============================================
  Files           131      131
  Lines          2605     2605
  Branches        263      263
============================================
- Hits           1531     1529       -2
- Misses          969      970       +1
- Partials        105      106       +1

Impacted Files
Coverage Δ
Complexity Δ

...java/com/codeborne/selenide/commands/Commands.java
97.84% <ø> (ø)
17 <0> (ø)
:arrow_down:

...e/selenide/impl/WebDriverThreadLocalContainer.java
77.08% <0%> (-1.39%)
29% <0%> (-1%)

Continue to review full report at Codecov.

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

Changes Unknown when pulling b2c4cbcd33d9147290395003c298d3d1b2133b67 on issue-457-fix-performance-of-parallel-tests into ** on master**.


gateway-mfr-rs: Update to latest release v0.1.7

Update gateway-mfr-rs to latest release v0.1.7
Ref https://github.com/helium/gateway-mfr-rs/releases/tag/v0.1.7

Deleting this PR to fix the checksum check


chore: release 1.0.0

:robot: I have created a release *beep* *boop*
1.0.0 (2022-11-15)
⚠ BREAKING CHANGES

Compactibility with phpunit 8 and upwards

Features

Compactibility with phpunit 8 and upwards (52dc152)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/live627/phpunit-garbage-collector/releases/tag/v1.0.0 :sunflower:


Exceptions swallowed in snapshot.getValue()

I was looking for hours why getValue doesn't return anything. The thread dies in the background silently. First as i step debug the code i've seen that some things must be present in the pojos like empty constructor and getters at least. I don't know why the exception is swallowed. I just can assume that google endpoints hide it from my eyes. I am using firebase with cloud endpoints together.

Is this in an event handler? I believe this is because ThreadPoolEventTarget class does not log errors by default.


Verify that kubectl can parse openapi

Since https://github.com/kubernetes/kube-openapi/pull/10 is moving parsing code for openapi from the main repo to https://github.com/kubernetes/kube-openapi/, we need to verify that the full swagger openapi file can still be parsed.
This is just a reminder that we need to do that.
In other word, we need to add a test in the main repo that verifies that the parsing code can parse the openapi swagger.

/remove-lifecycle rotten

@apelisse Have we accomplished this? Can I close this?

/sig cli
/area kubectl

I'd keep it open for now.

Moved this issue to the kube-openapi repo: https://github.com/kubernetes/kube-openapi/issues/103.
Closing here.


Need additional information about Organization test

Our Organization test is failing because the particular organization that is queried by the test does not have an NPI.
We DO return Organizations that have an NPI, and references to those are being returned in previous tests (MedicationRequest pharmacy, for example).
It is not apparent from the test why it is always using this particular Organization id in the query. Does it first retrieve all Organizations, then use the first one?

Hello @jlgrater
Thank you for raising this issue. To further investigate, could you send the url of your test session to my email<EMAIL_ADDRESS>

@jlgrater
Thank you for the session link. Similar to the Encounter resource (https://github.com/onc-healthit/onc-certification-g10-test-kit/wiki/FAQ#q-how-does-inferno-test-us-core-encounter-resource), Inferno Organization test is only concerned with references to Organization resources that it knows MUST support the US Core Organization profile.
MedicationRequest.performer has a reference to Reference(Organization). So Inferno does not count it into the Organization test.
Some examples of MustSupport element with reference to Reference(US Core Organization) are: CareTeam.participant.member, DiagnosticReport.performer, and DocumentReference.author


Automatically bisect failing builds on the Flutter 3xH builder

We now have two 3xH Flutter builders:

flutter-engine-linux (builds every single commit, is often far behind despite concurrent builds).
flutter-engine-linux-fast (merges builds, but does not pinpoint the failure to a particular commit).

If we add automatic bisection of failures to the -fast builder, we can get the best of both worlds and can free up ~4 linux bots continuously building flutter-engine-linux. There will still be a lot of latency because the builder takes 2 hours to run successfully, but with the bisection we should be able to get the results within hours, rather than days.
The proposal is to:

If a build fails and the previous build was a success, start bisection.
Trigger a build in the middle of the blamelist.
If the build fails, trigger a build in the middle of the older builds of the blamelist.
If the build succeeds, trigger a build in the middle of the newer builds of the blamelist.
Continue until the blamelist becomes a single commit.

Additionally, because there may be multiple failures caused by different commits, we can "fan out" when we encounter a new failure and start to bisect that separately (in parallel).

Recipe CL that fixed this:
https://chromium-review.googlesource.com/c/chromium/tools/build/+/1758566


Wayland client: Disable shortcut inhibition on rctrl press

This PR adds code to the Wayland client to disable shortcut inhibition when the right control key is pressed, which is the same behavior as the X11 client. While certain DEs provide their own key sequence for disabling the feature, to the best of my knowledge KWin does not, making it difficult to escape from a fullscreen RDP session when shortcut inhibition is enabled.
Let me know if any changes need to be made regarding the exact behavior when intercepting the key press.

@freerdp-bot test

I just rebased the commit on master, and apart from that, I also removed an erroneous TODO comment that I meant to delete before initially pushing. No actual code has changed, though.

@freerdp-bot test

@caseif thank you for this nice contribution!


Connection callback to Home apps

Reproduction steps
I use dynamic-bridge-app and want to get a notification whenever Apple Home, Google Home or Alexa is connected to matter server.

Commissioning is completed
Lets say I restart dynamic-bridge-app
I want to know when Apple Home, Google Home or Alexa is connected to matter again

Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
https://github.com/project-chip/connectedhomeip/commit/b9d32ecefd004adb7cc4c70a5f4a567dca199da0
Platform
raspi
Platform Version(s)
No response
Type
Platform Issue
Anything else?
No response

What exactly do you mean by "connected"?  Subscription is established?  Something else?

I want to know if my dynamic-bridge-app is commissioned to Apple Home, Google home, etc. Lets say my bridge is commissioned to commissioner (Apple Home, Google Home, etc). Then I restarted my dynamic-bridge-app again. Now the question is how do I know if my app is commissioned or not.
After I delete my bridge from Apple Home, Google Home, Can matter library say that my app is not commissioned anymore?

When you start it again, it's still commissioned, right?  As in, the fabric table still has the relevant entries.

After I delete my bridge from Apple Home, Google Home, Can matter library say that my app is not commissioned anymore?

You can register with the fabric table to be notified when fabrics are removed...

@bzbarsky-apple

When you start it again, it's still commissioned, right? As in, the fabric table still has the relevant entries.
Yes it is still commissioned. But how can I retrieve that information from Matter Library? Because you know client can delete bridge from Apple Home, Google Home, etc. So I should know that if they are still connected or not.

You can register with the fabric table to be notified when fabrics are removed...
First of all what is fabric table and how can I register with that table to be notified? I guess that is the thing what I am looking for.

@bzbarsky-apple  Thanks for clarifying the issue. One more question is that when I commissioned a network (Apple Home or Google Home) there seems 2 records in fabric table in which one label name is empty. If I delete bridge on network (Apple Home or Google Home), one of the records with index ID 1 is being deleted but the records with Index ID 2 still remains in fabric table. That record remains in fabric table until I delete all files (chip_config.ini, chip_kvs, etc.). Is this a bug?
[1673001296.929660][5557:5557] CHIP:DL: Matter Fabric Table: Fabric index 0x1. Compressed Fabric Id 0x334619CD9C8BAD3E, FabricId<PHONE_NUMBER>000001, NodeId 000000000D137F10, VendorId 0x1349 Label Test Matter, Initialized 1
[1673001296.929692][5557:5557] CHIP:DL: Matter Fabric Table: Fabric index 0x2. Compressed Fabric Id 0x33432B454C31534B, FabricId<PHONE_NUMBER>000002, NodeId 000000002F73F24D, VendorId 0x1384 Label , Initialized 1

@bzbarsky-apple And one more thing when fabric label is set (https://github.com/project-chip/connectedhomeip/blob/master/src/credentials/FabricTable.cpp#L2049), OnFabricUpdated is not called.

when I commissioned a network (Apple Home or Google Home) there seems 2 records in fabric table which one of them label name is empty.

When commissioning with Apple Home, I would expect it to be commissioned into the System Commissioner fabric and the Home-specific fabric.  Removing it from the one Home will remove from the latter, but not the former.

And one more thing is that when fabric label is set

OnFabricUpdated is documented as being called when the fabric's operational credentials change.  A fabric label is not credentials.


[FEA] Update To CPM v0.35.3

CPM v0.35.3 doesn't error out when the build directory is a symlink. This fix will help rapids-compose users.

Resolved in #230


Incorrect casing of the subscription name in DLQ storage blob path

I've created a lower-case event subscription named asb-sub-2-storage.

When a DLQ blob was created, noticed that the name is upper-cased.
eventgridtoasb/ASB-SUB-2-STORAGE/2019/6/13/5/e3b13e86-a4b8-429d-a6c2-74ba646f1c5e.json
Looks like a bug.

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

ID: 2ad5c953-fa75-9944-5539-111bfc52e892
Version Independent ID: 00d37a17-4f7d-779e-8243-786c1d4dba7d
Content: Dead letter and retry policies for Azure Event Grid subscriptions
Content Source: articles/event-grid/manage-event-delivery.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

While this is not doco issue, it is connected to the product.

@SeanFeldman , Thanks for raising the issue. We will investigate and update you.

@spelluru any thoughts here?

@banisadr - please have a look at this issue. We need to document this whether it's by design or a bug. Please let me know what you think. Thanks.

#assign:banisadr

Hi @SeanFeldman - great eye. This is intentional, but I'm considering changing it. Either way, we'll document it more clearly.
Let me explain the reasoning for the current behavior. Implementing dead lettering in Event Grid on top of Azure Blob Storage, we've found ourselves in an odd conflict. The expected behavior of all resources in Azure Resource Manager is to be case-insensitive but also is case-preserving. Contrary to this Azure Blob Storage is case-sensitive. The pit-fall is if you have an event subscription called "Foo" that you later update to add a new filter on, but inadvertently rename it to "foo" - your new dead lettered events would now be diverted from container "Foo" to "foo". Always uppercasing the container name protects against this.
I have never been a fan of this behavior and would rather preserve case in the blob URL trusting the person writing code to be mindful of their casing so that we don't break existing patterns we know are being used such as always converting to lower before creating or accessing blobs.
Would love to hear your thoughts.

@banisadr apology for the delayed response. Just returned from vacation.
This is nasty. And I agree with you that upper-casing is a safer option.
The only recommendation I'd make is to document this. It is obviously something your team is aware, but having this described in the dead-letter queue documentation would be much better. Do you think that's doable?

@SeanFeldman - I have added a note in the second section of the article. Please review and let me know if it looks good. Thanks.

@SeanFeldman - I have added a note in the second section of the article. Please review and let me know if it looks good. Thanks.

Thank you. 👍

#please-close


host_callback primitives are not usable under xla.lower_fun

This concerns an unusual use of host_callback, inside a custom primitive whose XLA lowering rule uses xla.lower_fun.
This uses private JAX core APIs and your mileage may vary.
This usage is not working properly when the function passed to lower_fun includes host callback primitives.
    class Prim(jax.core.Primitive):
      def __init__(self):
        super(Prim, self).__init__("prim")
        self.multiple_results = True

        def _abstract(*flat_avals, **params):
          return pe.abstract_eval_fun(self.impl, *flat_avals, **params)

        self.def_abstract_eval(_abstract)

        def _xla(c, *xla_args, **params):
          translation = xla.lower_fun(self.impl, multiple_results=True,
                                      backend="cpu")
          return translation(c, *xla_args, **params)

        xla.translations[self] = _xla

      def impl(self, *args):
        x, = args
        ret = hcb.id_print(x * 3., output_stream=testing_stream)
        return ret,

    @jax.jit
    def fn(x):
      return Prim().bind(x)[0]

    res = fn(jnp.asarray(1.))

This crashes with TypeError: _outside_call_translation_rule() missing 1 required keyword-only argument: 'has_token'

In #8841 I have improved the situation, but there is still a problem. If the lower_fun calls to a host_callback primitive and there are other host_callback primitives in the surrounding code then the sequencing tokens are not passed properly through the inner primitives. This may have the effect that the inner host_callback will execute out of order w.r.t. the outer primitives.
Fixing this requires a more thorough handing of effects in JAX.

Does this out of order issue mean incorrect results in this case? Would you advise against patching this PR into a local copy and running with that?
I really would like to be able to have a custom grad + custom batching rule for a host_callback call and all my workaround attempts keep failing. Any input appreciated. Thanks!

The problem arises when you have a computation that uses hcb primitives directly and also under the lower_fun. In that case the operations needed for the implementation of hcb primitives will not be sequenced properly and they may execute out of order. Most likely this will result in crashes. I don't think that this can result in incorrect results, but I am not sure.
I did not realize that you are doing this to get a custom batching rule for hcb.call. (A custom grad will work if you use the public APIs for custom grads.)

Good to know! Thanks!
For what it's worth I believe I found a workaround to our original problem -- instead of a custom batching rule just define a batching rule for all outside_call_p and have this rule hardcoded for the one particular hcb.call we use. This won't work with more than one hcb / arbitrary numbers of hcb.call but that is fine with me.
Thanks again for your help on this issue.

Any movement on this issue? I've just bumped up against it when using custom primitives to define a custom batching rule for a host_callback.call.
(FWIW custom_batching.custom_vmap doesn't seem to solve my problem either -- Idk to what extent that's intended to be usable at the moment but with that approach I get NotImplementedError: outfeed rewrite custom_vmap_call when trying to JIT.)

Fair enough! For completeness I managed to work around this (to produce a host_callback.call that can be both vmap'd and jit'd) by adapting @lukemetz's solution and monkey-patching the batching rule for outside_call_p. (With a bit of care to only activate in my use case, and not overwrite the existing batching rule for any other case.)

Current state of custom_vmap is, roughly:

some but not all transformations are supported (mainly we have JVP but no reverse-mode AD);
it is currently "initial style", which we may want to change;
it doesn't yet support self-reference (e.g. the custom batching rule can't call the original custom-vmapped function)

I was holding on documenting and declaring it ready for wide use until these are complete/decided. Do we know that having it will resolve this issue, or do we have enough in place to try and find out?


Printf test is not checking scientific notation correctly

The C spec says the following:

The E conversion specifier produces a number with E instead of e introducing the exponent. The exponent always contains at least two digits, and only as many more digits as necessary to represent the exponent.

Conformance has a few cases where we test scientific notation, but testing against the wrong value.
For example,
    printf("%+#21.15E\n", 789456123.0);

expects a result of +7.894561230000000E+8. However, the result should be +7.894561230000000E+08.

Just to clarify, from the code it looks like the issue is not that it doesn't allow the correct 2-digit answer, but that it doesn't require it, is that correct? I'm looking at the snippet that skips leading zeroes before comparing to the reference.

Your comment has alerted me to the fact that this issue is one of my own creation that I spotted once I began fixing #673 .
The existing printf behaviour is to have reference results with all leading zeros stripped from the exponent. The test then also strips leading zeros from the actual result read back from the device.
With my changes, the reference result now contains leading zeros, but the test was still stripping the leading zeros from the device. It was at this point I noticed the "bug" and raised this issue.
Now I actually think that stripping leading zeros from the reference and the device result is desirable behaviour, as there is no comment on how many leading zeros there may be.
I'll update #680 to strip leading zeros from the reference and the actual result, and then close this issue.

Closing as per previous comment.


FLUME-3128: Fix TestHDFSEventSinkOnMiniCluster.java due to incompatib…

…le changes in hadoop-hdfs lib.
Our test in flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/TestHDFSEventSinkOnMiniCluster.java
Uses the getLeaseByPath(String src) method of Lease class which is to be replaced by getLeaseForPath(Namenode n, String src) method.
This change is to make Flume compatible after the hadoop change is made effective.
See https://issues.apache.org/jira/browse/HDFS-6757

It won't work. Not compatible with hadoop's currently used version.


Set iptables backend to NFT for Canal and Calico VXLAN on Flatcar clusters

What this PR does / why we need it:
It happens that after upgrading Canal/Calico to a newer minor version, the pod network connectivity stops working for some reason. This mostly happens on Flatcar-based clusters and not always, but from time to time. This is a known upstream Calico issue and it's being tracked here: https://github.com/projectcalico/calico/issues/5760
As mentioned in https://github.com/projectcalico/calico/issues/5760#issuecomment-1123745297, the solution is to set FELIX_IPTABLESBACKEND to NFT.
If there's a Flatcar control plane node in the cluster, KubeOne will set FELIX_IPTABLESBACKEND to NFT. Otherwise, KubeOne will set FELIX_IPTABLESBACKEND to Auto, which is the current default value and results in Calico automatically determining the iptables backend.
This can be overridden by setting the iptablesBackend parameter on Canal or Calico VXLAN addon. For example:
apiVersion: kubeone.k8c.io/v1beta2
kind: KubeOneCluster
...
addons:
  enable: true
  addons:
    - name: cni-canal # or calico-vxlan if cluster is running Calico VXLAN
      params:
        iptablesBackend: "Auto"

This might also affect RHEL, but from our testing, it's much less frequent than for Flatcar. To reduce the scope of changes before the release, we'll revisit this after releasing KubeOne 1.5.
What type of PR is this?
/kind bug
Does this PR introduce a user-facing change? Then add your Release Note here:
Set iptables backend (`FELIX_IPTABLESBACKEND`) to `NFT` for Canal and Calico VXLAN on clusters running Flatcar Linux. For non Flatcar clusters, iptables backend is set to Auto, which is the default value and results in Calico determining the iptables backend automatically. The value can be overridden by setting the `iptablesBackend` addon parameter (see the PR description for an example).

Documentation:
NONE

/retest

/lgtm


Modernize to Jenkins 2.440.3

Hi!
This PR aims to move this plugin to the recommended Jenkins baseline version.
If there are additional requirements for accepting PRs - such as additional lag time before adopting a baseline - feel free to reply in the comments.
Testing done
Ran mvn clean verify.
### Submitter checklist
- [x] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [x] Ensure that the pull request title represents the desired changelog entry
- [x] Please describe what you did
- [x] Link to relevant issues in GitHub or Jira
- [x] Link to relevant pull requests, esp. upstream and downstream changes
- [x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Refs: sghill-rewrite/campaigns#4
Use this link to re-run the recipe: https://app.moderne.io/recipes/org.openrewrite.jenkins.ModernizePlugin?organizationId=SmVua2lucyBDSQ%3D%3D

Thanks for your PR. 2.426.x is still supported by update sites (as is 2.414.x) and I see no reason to update to a later version at this time.

Thanks for the note. Would you consider update site support the main factor in your decision to upgrade, or are there others?

Would you consider update site support the main factor in your decision to upgrade

It's one of the reasons. I'm co-author of most of the criteria listed in the docs, and support most of them. I just see the recommendation more as a fallback, rather than "if you end up older than this, you should update".