Add IBM Cloud Databases list and backups list fetchers

[x] Tick to sign-off your agreement to the Developer Certificate of Origin (DCO) 1.1

What
Migrate IBM Cloud Databases fetcher for account specific list of databases and backups list.
Why
Audits often request evidence to check whether databases are regularly being backed up.
How
REST api calls will be made to the resource controller and IBM Cloud databases end points.
Test
Local testing to be done to verify evidence being created.
fetch_databases.py
 time compliance --fetch --evidence local --notify stdout -C develop.json arboretum.ibm_cloud_databases.fetchers.fetch_databases

INFO: Using locker found in /var/folders/vv/9fgnxb454235bwsgw1wgl6840000gn/T/compliance...

Fetcher Primary Run

.
----------------------------------------------------------------------
Ran 1 test in 6.136s

OK

INFO: Committing changes to local locker in /var/folders/vv/9fgnxb454235bwsgw1wgl6840000gn/T/compliance...

real	0m6.577s
user	0m0.295s
sys	0m0.131s

The evidence file was generated and its contents verified
ls -la /var/folders/vv/9fgnxb454235bwsgw1wgl6840000gn/T/compliance/raw/icd/
total 120
drwxrwxr-x  4<EMAIL_ADDRESS>staff    128 Jan 14 16:34 .
drwxrwxr-x  3<EMAIL_ADDRESS>staff     96 Jan 14 16:19 ..
-rw-rw-r--  1<EMAIL_ADDRESS>staff  54030 Jan 14 16:34 databases_prod_1329217.json
-rw-rw-r--  1<EMAIL_ADDRESS>staff    164 Jan 14 16:34 index.json

fetch_backups.py
time compliance --fetch --evidence local --notify stdout -C develop.json arboretum.ibm_cloud_databases.fetchers.fetch_backups

INFO: Using locker found in /var/folders/vv/9fgnxb454235bwsgw1wgl6840000gn/T/compliance...

Fetcher Primary Run

.
----------------------------------------------------------------------
Ran 1 test in 19.527s

OK

INFO: Committing changes to local locker in /var/folders/vv/9fgnxb454235bwsgw1wgl6840000gn/T/compliance...

real	0m19.958s
user	0m0.455s
sys	0m0.145s
(arboretum3) Parthakumar.Roy@ibm.com:auditree-arboretum$ ls -al /var/folders/vv/9fgnxb454235bwsgw1wgl6840000gn/T/compliance/raw/icd/
total 80
drwxrwxr-x  5<EMAIL_ADDRESS>staff    160 Jan 15 09:58 .
drwxrwxr-x  3<EMAIL_ADDRESS>staff     96 Jan 14 16:19 ..
-rw-rw-r--  1<EMAIL_ADDRESS>staff      2 Jan 15 09:58 backups_prod_1329217.json
-rw-rw-r--  1<EMAIL_ADDRESS>staff  29971 Jan 15 09:54 databases_prod_1329217.json
-rw-rw-r--  1<EMAIL_ADDRESS>staff    327 Jan 15 09:58 index.json

NOTE: For the fetch_backups test to run to completion, certain entries in the database  evidence that were getting 404's had to be manually removed.
Context
https://github.com/ComplianceAsCode/auditree-arboretum/issues/43

picked a more descriptive ibm_cloud_databases for the source code directory, but left it at icd for the locker repo for backward compatibility.
as of this writing, the evidence for the list of databases is now going to change to a list of json objects, one per resource_group_id (previously it was the json object itself).

[
{
 "next_url": null,
 "resources": [
   {
     "account_id": "...",
     "allow_cleanup": false,
     "controlled_by": "",
     "created_at": "2018-10-10T15:50:48.744687589Z",
     "created_by": "",
     "crn": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...::",
      ...
     "resource_group_id": "...",
      ...
   },
   ...
  ],
 "rows_count": 13
},
{
 ...
},
...
]

as of this writing, the evidence for the list of backups is still a list of the backup objects, no attempt has been made to make it a dictionary of backups list separated by resource_group_id.

[
 {
   "created_at": "2020-11-30T23:31:19.000Z",
   "deployment": {
     "id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...::",
     "version": "10"
   },
   "deployment_id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...::",
   "id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...:backup:...",
   "is_downloadable": false,
   "is_restorable": true,
   "status": "completed",
   "type": "scheduled"
 },
 ...
]

followed the fetch_cluster_list approach on how to remove dependency on ibmcloud_tools

picked a more descriptive ibm_cloud_databases for the source code directory, but left it at icd for the locker repo for backward compatibility.
as of this writing, the evidence for the list of databases is now going to change to a list of json objects, one per resource_group_id (previously it was the json object itself).

[
{
 "next_url": null,
 "resources": [
   {
     "account_id": "...",
     "allow_cleanup": false,
     "controlled_by": "",
     "created_at": "2018-10-10T15:50:48.744687589Z",
     "created_by": "",
     "crn": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...::",
      ...
     "resource_group_id": "...",
      ...
   },
   ...
  ],
 "rows_count": 13
},
{
 ...
},
...
]

as of this writing, the evidence for the list of backups is still a list of the backup objects, no attempt has been made to make it a dictionary of backups list separated by resource_group_id.

[
 {
   "created_at": "2020-11-30T23:31:19.000Z",
   "deployment": {
     "id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...::",
     "version": "10"
   },
   "deployment_id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...::",
   "id": "crn:v1:bluemix:public:databases-for-postgresql:us-south:a/...:backup:...",
   "is_downloadable": false,
   "is_restorable": true,
   "status": "completed",
   "type": "scheduled"
 },
 ...
]

followed the fetch_cluster_list approach on how to remove dependency on ibmcloud_tools

Local test results added to the top - it raises the question of whether 404 errors should abort creation of the backups evidence.

Local test results added to the top - it raises the question of whether 404 errors should abort creation of the backups evidence.

What's the question exactly?

What's the question exactly?

What's the question exactly?

When fetch_backups.py iterates through a list of databases, if it gets a 404 from any of the backup URL's https://api.<region>.databases.cloud.ibm.com/v4/ibm/deployments/<database_crn_escaped>/backups, the fetcher aborts. Is this acceptable behavior?

What's the question exactly?

When fetch_backups.py iterates through a list of databases, if it gets a 404 from any of the backup URL's https://api.<region>.databases.cloud.ibm.com/v4/ibm/deployments/<database_crn_escaped>/backups, the fetcher aborts. Is this acceptable behavior?

Closing due to inactivity


Fix ColorPicker's remote synchronization when typing values

When typing + enter in a ColorPicker, the color didn't synch in the running project.

Fixes: https://github.com/godotengine/godot/issues/98559

so it will show up in the editor (and affect what you see in the editor viewport), but not in the running project. The color will only apply to the running project once you close the ColorPicker.

I wanted to make it update with any change like in the editor. The lack of realtime changes defeats the purpose of live synchronization. But then there is this thing with the transform gizmos that they only update when the click is released, so I thought the synchronization was supposed to work in "undo-redo commit style" by design.
But now that I think about it, only the transform gizmos work like this... Most property inspectors update in realtime.

Thanks!


rm ebi_status from the study lists

Coverage increased (+0.01%) to 91.085% when pulling dd5961935cdb297c0b1dff812fa3871415953bf9 on antgonza:rm-ebi_status-study-list into bfacd73b86e59ee1aefdfb6f724fb2cedd50c478 on qiita-spots:dev.

Thanks!


DCM KIT Release Development View

Release 23.12 Development View

[ ] API Specification / Protocols

Documentation for the development view must be available in Eclipse Tractus-X as part of the development view MD files.

Best Practice:

eclipse tractusx-docs-artefacts
How-to-create-a-KIT-website

Artifact Repository:

eclipse-tractusx

Contacts:

Responsible: PO/BO (from relevant Domain)
Responsible for Process: PCA/BDA
Consult: KIT-CONTACT1, KIT-CONTACT2
Review by: PCA/BDA

[ ] Sample Data Available in Repository

Sample data must be available in Eclipse Tractus-X as part of the development view MD files.

Best Practice:

eclipse tractusx-docs-artefacts
How-to-create-a-KIT-website

Contacts:

Responsible: PO/BO (from relevant Domain)
Responsible for Process: PO / BO (from relevant Domain)
Review by: PCA/BDA

[ ] Reference Implementation

Mandatory, if reference implementation is provided
A reference implementation must follow the FOSS release gates and must be available in the corresponding repository in the Eclipse Tractus-X project.

Best Practice:

https://confluence.catena-x.net/x/IpSmB (Source only accessible for Catena-X Consortia members in current transition phase.)

Artifact Repository:

eclipse-tractusx

Contacts:

Responsible: PO/BO (from relevant Domain)
Responsible for Process: PO / BO (from relevant Domain)
Consult: SYSTEM_TEAM1
Review by: PCA/BDA

[ ] Development-View Architecture Documents in Repository

Mandatory (for Platform Domain / CX ART)
Documentation must be available in Eclipse Tractus-X as part of the development view MD files.

Artifact Repository:

eclipse-tractusx

Contacts:

Responsible: PCA / BDA
Responsible for Process: EAs
Review by: PCA/BDA

API Specification / Protocols - under Data Exchange, no Open API specification - approved for now
Sample Data Available in Repository - approved
Reference Implementation - OPTIONAL no implementation yet
Development-View Architecture Documents in Repository - WiP link available for consortia members, DOCUMENT REQUIRED for next TIME approved by PCA/BDA

Thanks for your support @kelaja @danielmiehle @maximilianong


Can the gpt4 model be used now? I setted my model as .gpt4, but it doesn't work...

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi @donfishman, what error are you getting when using .gpt4? Do either gpt4_0613 or gpt3_5Turbo work for you or are they failing as well?

Hi @donfishman, what error are you getting when using .gpt4? Do either gpt4_0613 or gpt3_5Turbo work for you or are they failing as well?

thanks for your reply, every code worked perfectly for me，When I asked him who he was, he always replied that he was gpt3, but actually, I had set the model to gpt4, and I tried to ask him if he knew who the winner of the 2022 World Cup was, and he told me that he only studied until 2021 and could not predict the future....

Hi@SunburstEnzo, thanks for your reply, the code when I using .gpt4 worked perfectly without error. But When I asked him who he was, he always replied that he was gpt3, but actually, I had set the model to .gpt4 or .gpt4_0613, and I tried to ask him if he knew who the winner of the 2022 World Cup was, and he told me that he only studied until 2021 and could not predict the future....

Hi@SunburstEnzo, thanks for your reply, the code when I using .gpt4 worked perfectly without error. But When I asked him who he was, he always replied that he was gpt3, but actually, I had set the model to .gpt4 or .gpt4_0613, and I tried to ask him if he knew who the winner of the 2022 World Cup was, and he told me that he only studied until 2021 and could not predict the future....

Hi, @SunburstEnzo ,now I got an error when using .gpt4:
Error Domain=NSURLErrorDomain Code=-1017 "cannot parse response" UserInfo={_kCFStreamErrorCodeKey=-1, NSUnderlyingError=0x6000015dcd80 {Error Domain=kCFErrorDomainCFNetwork Code=-1017 "(null)" UserInfo={_kCFStreamErrorCodeKey=-1, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<3>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask .<3>"
), NSLocalizedDescription=cannot parse response, NSErrorFailingURLStringKey=https://api.openai.com/v1/chat/completions, NSErrorFailingURLKey=https://api.openai.com/v1/chat/completions, _kCFStreamErrorDomainKey=4}
but when I use .gpt-3.5-turbo everything is perfect

I believe if you're using Completions you have to use gpt-3.5-turbo-instruct I'm afraid — it's a discussion point in a few other issues on here

completions supports:
"gpt-3.5-turbo-instruct"
"babbage-002"
"davinci-002"
typesafe model support proposed in this pull obviates the question.

Don't think I understand this, completions on gpt4 are supported by OpenAI:

Is it because this framework is using the legacy api?
https://platform.openai.com/docs/guides/text-generation


Does Kestrel support urls/hostnames, or it can only listen to a port?

I'm trying to start ASP.NET 5 web application so that it could be accessible via public internet address, like "http://hostname.dom".
I don't want it to be acessible via "http://www.hostname.dom", "http://test.hostname.dom", etc. And I have DNS records configured to point server's ip address by "*.hostname.dom" and "hostname.dom" names.
So I start Kestrel with the parameter:
server.urls=http://hostname.dom
I expect it to ignore any address that is not "http://hostname.dom", but application is available by every "http://justanything.hostname.dom" address and even just by IP address. So it is listening for all requests to 80 port rather than requests to a specific hostname. For example, when configuring IIS site bindings, you can specify binding like "hostname.dom" and it will ignore any other possible prefixes until you specify them explicitly.
Does Kestrel support urls/hostnames, or it can only listen to a port?

You're correct, it discriminates by ip and port, not host name. WebListener supports this if you need it. Otherwise you can just check the host header yourself and send 503's.

WebListener seems to be Windows-only (I run the application on a Linux-based server), but I've found also a solution involving nginx. Looks like it works too. Link, if anyone facing the same question: http://druss.co/2015/06/asp-net-5-kestrel-nginx-web-server-on-linux/


After pasting URL, hitting spacebar should not edit URL

Immediately after pasting a URL into editor, users should be able to hit the spacebar without adding to the URL.

Thanks for raising this. This is a good suggestion. We will need to change the inclusivity rules about link (a tag) markup so that after inserting the link cursor is no longer "in" the markup. This is different than what we do for bold text, which is right-inclusive — if your cursor is on the right side of bold text, it is considered to be "in" the bold markup and the next typed text should be bold.


$.views.setDelimiters bug...

Hi Boris,
just noticed that if I set the delimiters with 2 different characters, like for example "<%" and "%>", it doesn't work.
the problem is probably located on line 170-171
	setDelimiters: function( openTag, closeTag ) {
		// Set or modify the delimiter characters for tags: "{{" and "}}"
		var firstCloseChar = closeTag.charAt( 1 ),
			secondCloseChar = closeTag.charAt( 0 );
		openTag = "\\" + openTag.charAt( 0 ) + "\\" + openTag.charAt( 1 );
		closeTag = "\\" + firstCloseChar + "\\" + secondCloseChar;

I presume you wished to type:
var firstCloseChar = closeTag.charAt( 0 ),
secondCloseChar = closeTag.charAt( 1 );
with this little fix, it works.

Yes, thanks for finding this. Fixed in https://github.com/BorisMoore/jsrender/commit/ab3fddd0e6661f043a08c9e66416671e768ea9a3


Add repo_contents_path attribute

Adding a unused attribute to be able to test multiple versions of core
from the updater.

Not sure this is needed, looking into bundling a unreleased core version in the updater

@jurre @thepwagner thoughts on adding this? If we release core with these attributes we could release a version of the updater that has the required changes for vendoring: https://github.com/dependabot/dependabot-updater/pull/1004 (we'll then just need to bump core in updater once it's ready)


Dropping the entrenching tool should cancel the digging doafter

mmm yes marines have psychic powers
https://github.com/user-attachments/assets/b33bf402-00ed-467b-ad2b-058428b5fc58

you can use this to stack dig sandbags and get a TON of faster dig speed.


Import UK users

User story
As a uk.dosomething.org user I should be able to log in to dosomething.org
As we retire the uk site, we should import UK users. 🇬🇧 ➡ :us:
Steps

we can run a script like this to import users from the uk
set source to DS UK
do not import campaign activity

script seems ok, only worry is will the global language be set by this? I dont think it will but could be wrong

in case i lose it, query that gets

first name
last name
email
pass
birthday

SELECT u.uid, u.mail, u.pass, fn.field_first_name_value, ln.field_last_name_value, bd.field_birthdate_value
FROM users u
JOIN field_data_field_first_name fn
ON fn.entity_id = u.uid
JOIN field_data_field_birthdate bd
ON bd.entity_id = u.uid
JOIN field_data_field_last_name ln
ON ln.entity_id = u.uid

good question we need to answer when we test on Thor

@deadlybutter we also want to make sure those users can still log in, password hashing stufff ;)

update based on lunch convo with @angaither and @Bladt we're going to just import all of the users into Mailchimp & send them a message to create an account on dosomething.org -- I'll pass the CSV over to whoever is going to send the email!
Also I assume that means we will need Ben to quickly write something up?

BY THE ORDER OF @angaither WE ENACT ARTICLE 50 AND CLOSE THIS ISSUE. BREXIT.

i thought i hit close & comment, whoops haha


Feature Request: Enhance the UI/UX of Authentication Flow (Sign-In, Sign-Up)

This pull request addresses the feature request to improve the user interface and user experience of the authentication flow within the application. The key enhancements include:

Refined Design : The Sign-In and Sign-Up forms have been redesigned for a more modern and intuitive look, improving overall aesthetic appeal.
Layout Improvements : The first name and last name fields are now displayed in a single row, enhancing the form layout and making it more user-friendly.
Dark Mode Functionality :  The dark mode feature, which was previously non-functional, has been fixed and is now fully operational, ensuring a consistent user experience across different themes.

For better understanding, attached a video
new-auth-ui.webm
Fixed #30

Just resolve conflicts and you are good to go, and just change to "Sign In" button to "Log In"

I have resolved the conflict and ensured that my UI for the authentication flow remains intact, including both the sign-in and sign-up screens. @SwanandD121


add PEP-8 linter

perhaps via a githook?

I use this one for mriqc: http://git-pylint-commit-hook.readthedocs.io/en/latest/

https://github.com/poldracklab/fmriprep/pull/154

[  ] change it to a circle/travis validation rather than githook


[zh-cn] resync /access-authn-authz/extensible-admission-controllers.md

Resync this page by following #34740.
content/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers.md

Preview: https://deploy-preview-35236--kubernetes-io-main-staging.netlify.app/zh-cn/docs/reference/access-authn-authz/extensible-admission-controllers/

/approve


[csrng/sec] remove AES bypass, clean register debug

Removed the AES bypass option, as this has been debugged, and now may pose a security exposure.
Other debug registers have been cleaned up as well.
Signed-off-by: Mark Branstad<EMAIL_ADDRESS>

Hi @mwbranstad, I pushed a commit with changes to the dif interface. You will have to pull from your remote branch to pick up the commit. Thanks!

@moidx the dif code now passes lint, but the test seems to fail:
2021-07-16T13:00:20.0601706Z  3/40 opentitan:dif / dif_clkmgr_unittest     OK      0.006775617599487305 s
2021-07-16T13:00:20.0602515Z  4/40 opentitan:dif / dif_csrng_unittest      FAIL    0.006659507751464844 s (exit status (1,))
2021-07-16T13:00:20.0603340Z  5/40 opentitan:dif / dif_uart_unittest       OK      0.019536256790161133 s
Any idea how to fix this?

I just pushed an updated commit to fix dif_clkmgr_unittest. It should be ok now.


Create core module

This PR closes #75 . It creates the described core module and moves the utilities and hygro modules as submodules into the core. It also adapts the documentation to reflect these changes.
Still to be done:

[ ] Constants restructure
[ ] pmodel.functions refactor

Codecov Report

Merging #139 (c5b1c99) into develop (ad32a8e) will increase coverage by 94.09%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##           develop     #139       +/-   ##
============================================
+ Coverage         0   94.09%   +94.09%
============================================
  Files            0       21       +21
  Lines            0     1134     +1134
============================================
+ Hits             0     1067     +1067
- Misses           0       67       +67

Files
Coverage Δ

pyrealm/constants/hygro_const.py
89.47% <ø> (ø)

pyrealm/core/hygro.py
100.00% <100.00%> (ø)

pyrealm/core/utilities.py
92.10% <ø> (ø)

pyrealm/pmodel/calc_optimal_chi.py
90.80% <100.00%> (ø)

pyrealm/pmodel/competition.py
100.00% <100.00%> (ø)

pyrealm/pmodel/functions.py
97.56% <100.00%> (ø)

pyrealm/pmodel/isotopes.py
92.30% <100.00%> (ø)

pyrealm/pmodel/jmax_limitation.py
90.74% <100.00%> (ø)

pyrealm/pmodel/pmodel.py
93.20% <100.00%> (ø)

pyrealm/pmodel/pmodel_environment.py
85.71% <100.00%> (ø)

... and 11 files with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

Looks good so far!

I left some tests in pmodel that should properly now be in tests\unit\core. I had forgotten that #151 has already been merged into develop, so was leaving them until they could be moved into the new structure, but they can so should be here.


work excluding omkar's work and including omkar's test

here is it

@tesfahunt you have a merge conflict.


Team-work contract

Link to team contract: https://docs.google.com/document/d/1wm_hqZe-aFrBlUXa4QUzJboyR25YH8v6CwCdSq3TN0g/edit


HELP

I updated the library to the most recent version and my code stopped working.
I was using Firebase.updateNode(firebaseData, "", json) to upload a single json structure to firebase, but now I get an error.
After this update, I feel that the documentation is very confusing and it is making a lot harder to figure out what to do. For example, the "Changes from earlier version" section states that "getJson, setJson, pushJson, updateNode and updateNodeSilent." have been changed, but does this mean they are not supported anymore? Also, there are a lot of functions with similar names such as "setJsonData" and "setJson", but I dont know what's the difference.
Finally, you could add a content table for the functions descriptios to make it easier to find and understand their usage.
Obs.: Great library!

For new version, the JSON string was not supported by the functions that take String of serialized JSON object e.g. setJson and updateNode.
You need to use FirebaseJson object (class) for that functions as they accept FirebaseJson object as parameter.
To set the JSON string (serialized string) to FirebaseJson, you can call setJsonData from FirebaseJson object.
The examples and the document (bottom section of doc) are also updated for the FirebaseJson usages.

The updateNode functions accept only FirebaseJson object
bool updateNode(FirebaseData &dataObj, const String &path, FirebaseJson &json);
bool updateNodeSilent(FirebaseData &dataObj, const String &path, FirebaseJson &json);
bool updateNodeSilent(FirebaseData &dataObj, const String &path, FirebaseJson &json, float priority);

You can set the JSON string like this.
FirebaseJson json;
json.setJsonData ("{\"key\":\"value\"}");

or
FirebaseJson json;
String jsonStr = "{\"key\":\"value\"}";
json.setJsonData (jsonStr);

Or create it from add and set functions.
FirebaseJson json;
json.add ("key", "value");
json.add ("myInt", 123);

or
json.set("/key", 99.25);
json.set("/parent/child", "test");

Then pass json to updateNode
updateNode(firebaseData,  "path to your node", json);

Got it to work now, thanks!
By the way, is there a limit to how much data you can send at once? I tried updating a node with more than 512 double values and it didn't work. I had to split the data into three different batches to get it to work...

It's not limited for numbers of children nodes unless if the FirebaseJson holds too large data, free memory may not enough for WiFi Client to start SSL connection.
For nested data, Firebase is limited to 32 levels of data depth.


[Bug] can't log in

I am getting this error message:
[error] Failed to login. There was probably an extra verification step that this app didn't check for. A screenshot of the page will be saved to failed-login-screenshot-1644515619539.png and the page content will be saved to failed-login-html-1644515619539.html. Please create an issue on GitHub with both of these files.
But there is nothing unusual on that screenshot. Just twitch mainpage.

If the screenshot looks normal, the page probably just didn't completely finish loading on time. If it keeps happening, you can try to increase load_timeout_secs.

Thx.
I will close this issue and will create a new one if the error occurs again


Update cwextab

I made improvements to my cwextab library, some of which require changes in objdiff. This is mainly to address the decoding issues found in Rock Band 3.

Thanks a lot!


fix ocm token

We now pass the JWT secret to the reva runtime.
The ocm service only picks up the shared jwt because the sharedConf package is a singleton and other services in ocis initialize it ... 😞

fixes https://github.com/owncloud/ocis/issues/10041


Attendance Tracker Revamp

What's the issue about?

The attendance tracker feature in the app uses table_calendar plugin. That plugin is deprecated, we need to upgrade the functions according to the latest version.
Apart from that, we are planning to change some UI aspects of the feature - like adding the dropdown subjects list in the bottom navigation bar.


Route Registration

The Route registration can be optimized.
I think it has 2/more loops. Can be reduce to one

can you explain better where it happens ?

had already fixed I think. CLosing this now


Forgero reference book missing entries

Hovering over Forgero items with the book in my inventory doesn't work either.
Using Forgero 0.10.9 for Minecraft 1.18.2.

Hi, can you send over the log with the error stack trace?

Mangrove does not exist in 1.18.2, so I removed the material entry. It seems like the guide references this missing material, which crashes the book. It should be as easy as changing the wood type of the entry to another wood, like oak.


twemoji SVGs contains no gradients

If I grep for linearGradient or radialGradient inside font-srcs/twemoji/assets/svg directory, I get 0 results. So it appears that Twemoji svgs are all flat colors, without gradients.
Also, the test font as generated by update-samples.sh script containing Twemoji's smileyes ends up being built as a COLRv0 font, even if nanoemoji script is called with --color_format corl_1, this is because none of the color layers for the selected emojis contain any opacity/transparency.
When a color glyph only uses opaque colors without any gradients, the fonttools colorLib builder automatically encodes it in the COLRv0 portion of COLR table (as it is more compact than the v1 equivalent).
https://github.com/fonttools/fonttools/pull/1822/files#diff-9daa4995838963ff3909314f68952cbfR277-R299
The colorLib.buildCOLR method has an option to set the version explicitly (instead of automatically based on content) but it is not exposed to ufo2ft yet.
I am not sure whether all Twemoji svgs have flat and solid colors with no transparency. But if that is the case, then using Twemoji for testing COLRv1 implementation does not make much sense.

It isn't my intent for this repo to exclusively have COLRv1 samples. I think I will likely update the twemoji one to COLRv0.

For context, as the tools mature and we start to implement optimizations like shape reuse and the like I aspire to provide samples of COLR vs X vs Y so we can see the filesize implications and potentially even test other things like cost to parse/render.


No license defined

There is no license defined in this repository, and this makes the script not usable by anyone (see https://choosealicense.com/no-permission/). Please add license terms, especially if it is meant to be free software.

Import Apache Licence 2.0 announcement


Binding names

What about 'sharing' binding names between platforms (Visible/Visibility would become Visible on both platforms)
this means most bindings could be shared from within Shared libraries, cross platform

Interesting idea ! Initially the extensions was mapped to the original component properties (except for Visibility/Hidden case). I have to list all the differences between main components to see the range of differences. Adding multiple extensions for same properties could also be a good alternative.

though I like that names are the same as the native ones on each platform. having a unified api would allow copy paste from controllers to activities ;)


Documentation cleanup

Bloc's anatomy.md and extensions.md have received some cleanup.
More important is the proofreading of the upgrade guide as it contained many
hard to read sentences due to grammatical inconsistencies

@sneridagh I don't know if you would like for someone else from the docs team from plone to have a look at my changes.
They should be safe to merge without any extra checking as I used a grammatical checker as well but you never know :)
Still, I think that they would be better after the merge than before.

@ichim-david no need gfor that now, I guess that review will happen when we merge the docs with the upcoming doc revamp that the docs team are working on.
Thanks for taking care of this!


Tcp spec

This PR adds the changes that make the tcp interface spec compliant. See https://github.com/SignalK/specification/pull/286

No tcp spec yet, trying to limit wip.


k8s: Bump k8s libraries to v0.30.0

What this PR does
This PR bumps k8s vendor to v0.30.0 on go.mod files.
It also performs needed changes in order to comply with the new vendor libraries.
Note: This PR follows the update-k8s-dependencies. manual.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Bump k8s deps to 0.30.0

/retest-required

Do you think it would be possible to split it into two commits: one for the manual code change and one for the generated code? It's a bit hard to follow, and I'm having trouble loading all the changes on my browser :)

change: Rebase

atm we have a problem that some IDEs don't index symbols correct
because the IDE try to fetch toolchain 1.22 that doesn't exists
https://github.com/golang/go/issues/61455#issuecomment-2072931029
with this PR it fixes it to be 1.22.0 instead that fixed this weird by product

@RamLavi
is it fine to try and merge https://github.com/kubevirt/kubevirt/pull/11874 meanwhile please?
it will fix IDEs problems
unless this PR will be merged soon, wdyt ?
Thanks

/retest-required

@RamLavi
is it fine to try and merge https://github.com/kubevirt/kubevirt/pull/11874 meanwhile please?
it will fix IDEs problems
unless this PR will be merged soon, wdyt ?
Thanks

I don't see a reason why this shouldn't be merged promptly, it's already approved, just needs an lgtm

@RamLavi Please provide a release note, I think this PR deserves more than NONE

@RamLavi Please provide a release note, I think this PR deserves more than NONE

ACK, DONE

/lgtm

Change: Rebase

/lgtm

/retest-required

@RamLavi Can you check the failures? Looks like they are the same in the recent tests, so maybe they are related to this PR. Thank you

Change: Rebase

Change: Squash

@RamLavi Can you check the failures? Looks like they are the same in the recent tests, so maybe they are related to this PR. Thank you

Squashed now that the commits were lgtmed seperately, squashed as they can't stand alone.
@fossedihelm let's see again how it goes.

Change: Rebase

As commits are squashed, removing hold
/hold cancel

/test pull-kubevirt-unit-test
passes locally, could be flake

This will make it more convenient to import client-go in other projects, thanks.
A question out of curiosity: Is it ok to make kubevirt depend on k8s 1.30, when CI still runs on 1.28 and 1.29? I assumed that we support these older versions. Is the k8s.io code backward compatible?

@RamLavi - there looks to be an issue with the sig-monitoring lane on this PR. https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11840

Lemme take a look
/hold

This can fix it: https://github.com/kubevirt/kubevirt/pull/11950

This will make it more convenient to import client-go in other projects, thanks.
A question out of curiosity: Is it ok to make kubevirt depend on k8s 1.30, when CI still runs on 1.28 and 1.29? I assumed that we support these older versions. Is the k8s.io code backward compatible?

I don't think it's a problem, as long as we make sure to use GAed features and resources, then it should be backwards compatible.

some cosmetics nits here that can be done for leader election change (your change is right, just some var name changes if you want to take a look please)
https://github.com/kubevirt/kubevirt/pull/10640/commits/f6eaf6259693154344b63985acf62e033488d38b

Change: Rebase

/lgtm

if the failures are not related please consider unhold

if the failures are not related please consider unhold

I don't think they're related, I see very similar tests fail on other PRs (like https://github.com/kubevirt/kubevirt/pull/11516, see failing here)
/hold cancel

Looking at the PR history here - it looks like this will be very unlikely to merge until https://github.com/kubevirt/kubevirt/pull/11950 is merged.
https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11840
The hold should probably stay in place until #11950 is merged or we decide to override the monitoring lane here?

but if you override, wont this flake affect everything once this PR is merged?
otherwise sgtm

/hold
I may need to bump to v0.30.1

/hold I may need to bump to v0.30.1

no need as of now.
/hold cancel

Looking at the PR history here - it looks like this will be very unlikely to merge until #11950 is merged.
https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11840
The hold should probably stay in place until #11950 is merged or we decide to override the monitoring lane here?

@RamLavi please consider this

Looking at the PR history here - it looks like this will be very unlikely to merge until #11950 is merged.
https://prow.ci.kubevirt.io/pr-history/?org=kubevirt&repo=kubevirt&pr=11840
The hold should probably stay in place until #11950 is merged or we decide to override the monitoring lane here?

@RamLavi please consider this

It does look bad.. Lets give #11950 more time to get merged

Change: Rebase

update: I tried to mount https://github.com/kubevirt/kubevirt/pull/11950 's commit after I made sure they pass on the original code - and indeed it seems like the test fail with my changes.
I'm trying to investigate why.
I don't see an obvious reason though. We are not touching relevant virt-API/virt-operator code that could influence this test, so I'm perplexed.
@machadovilaca - Can you provide a command I could use in order to scrape the relevant prom rule in order to see the rate that is supposed to fire? I suspect that maybe the expression is outdated..

update: I tried to mount #11950 's commit after I made sure they pass on the original code - and indeed it seems like the test fail with my changes. I'm trying to investigate why. I don't see an obvious reason though. We are not touching relevant virt-API/virt-operator code that could influence this test, so I'm perplexed.
@machadovilaca - Can you provide a command I could use in order to scrape the relevant prom rule in order to see the rate that is supposed to fire? I suspect that maybe the expression is outdated..

@RamLavi  Which test are you referring to?

update: I tried to mount #11950 's commit after I made sure they pass on the original code - and indeed it seems like the test fail with my changes. I'm trying to investigate why. I don't see an obvious reason though. We are not touching relevant virt-API/virt-operator code that could influence this test, so I'm perplexed.
@machadovilaca - Can you provide a command I could use in order to scrape the relevant prom rule in order to see the rate that is supposed to fire? I suspect that maybe the expression is outdated..

@RamLavi Which test are you referring to?

[Serial][sig-monitoring]Component Monitoring Errors metrics VirtOperatorRESTErrorsBurst and VirtOperatorRESTErrorsHigh should be triggered when requests to virt-operator are failing (here)

update: I tried to mount #11950 's commit after I made sure they pass on the original code - and indeed it seems like the test fail with my changes. I'm trying to investigate why. I don't see an obvious reason though. We are not touching relevant virt-API/virt-operator code that could influence this test, so I'm perplexed.
@machadovilaca - Can you provide a command I could use in order to scrape the relevant prom rule in order to see the rate that is supposed to fire? I suspect that maybe the expression is outdated..

@RamLavi Which test are you referring to?

[Serial][sig-monitoring]Component Monitoring Errors metrics VirtOperatorRESTErrorsBurst and VirtOperatorRESTErrorsHigh should be triggered when requests to virt-operator are failing (here)

OK, I think I understand what's happening here.
As part of this PR, we moved to select a leader using a lease.
Now, regarding the test: for the test purposes we replace the timing of the alerts to 1 minute
so it will trigger if 80% failed in the last minute, then we remove the virt-operator cluster-role-binding, so virt-operator cannot perform any operations in the cluster
which should cause all the requests it receives to fail.
But closer examination of the metrics show that the lease GET/SET still receive code 200 (meaning no error)..
How the leases requests still work even when the cluster-role- binding is dead - I do not know..

update: I tried to mount #11950 's commit after I made sure they pass on the original code - and indeed it seems like the test fail with my changes. I'm trying to investigate why. I don't see an obvious reason though. We are not touching relevant virt-API/virt-operator code that could influence this test, so I'm perplexed.
@machadovilaca - Can you provide a command I could use in order to scrape the relevant prom rule in order to see the rate that is supposed to fire? I suspect that maybe the expression is outdated..

@RamLavi Which test are you referring to?

[Serial][sig-monitoring]Component Monitoring Errors metrics VirtOperatorRESTErrorsBurst and VirtOperatorRESTErrorsHigh should be triggered when requests to virt-operator are failing (here)

OK, I think I understand what's happening here. As part of this PR, we moved to select a leader using a lease. Now, regarding the test: for the test purposes we remove the virt-operator cluster-role-binding, so virt-operator cannot perform any operations in the cluster which should cause all the requests it receives to fail.
But closer examination of the metrics show that the lease GET/SET still receive code 200 (meaning no error).. I think it's because we have lease resource both on the cluster-role and the role... removing it gave the desired alert to fire. @machadovilaca I updated the test that failed to also remove the role-binding and now it succeeds. Do you agree this is the appropriate course of action? If so, I will set it as soon as your PR is merged

@RamLavi great work
If we just need to also remove the role-binding then it's fine by me. Should we do it in a different PR?

update: I tried to mount #11950 's commit after I made sure they pass on the original code - and indeed it seems like the test fail with my changes. I'm trying to investigate why. I don't see an obvious reason though. We are not touching relevant virt-API/virt-operator code that could influence this test, so I'm perplexed.
@machadovilaca - Can you provide a command I could use in order to scrape the relevant prom rule in order to see the rate that is supposed to fire? I suspect that maybe the expression is outdated..

@RamLavi Which test are you referring to?

[Serial][sig-monitoring]Component Monitoring Errors metrics VirtOperatorRESTErrorsBurst and VirtOperatorRESTErrorsHigh should be triggered when requests to virt-operator are failing (here)

OK, I think I understand what's happening here. As part of this PR, we moved to select a leader using a lease. Now, regarding the test: for the test purposes we remove the virt-operator cluster-role-binding, so virt-operator cannot perform any operations in the cluster which should cause all the requests it receives to fail.
But closer examination of the metrics show that the lease GET/SET still receive code 200 (meaning no error).. I think it's because we have lease resource both on the cluster-role and the role... removing it gave the desired alert to fire. @machadovilaca I updated the test that failed to also remove the role-binding and now it succeeds. Do you agree this is the appropriate course of action? If so, I will set it as soon as your PR is merged

@RamLavi great work
If we just need to also remove the role-binding then it's fine by me. Should we do it in a different PR?

no. If this PR spoiled the test it should be the one to fix it.

we broke the streak!
removing hold
/hold cancel
trying again
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring

we broke the streak!
removing hold /hold cancel
trying again /test pull-kubevirt-e2e-k8s-1.29-sig-monitoring

pull-kubevirt-e2e-k8s-1.29-sig-monitoring failed, but on a different test.
/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring

/test pull-kubevirt-e2e-k8s-1.29-sig-monitoring

/retest

/retest

/test pull-kubevirt-unit-test-arm64
looks like a flake

Did you take a look on those https://github.com/kubevirt/kubevirt/pull/11840#issuecomment-2124494884 ?
Just some cosmetics, doesnt merit hold, but nice to have
thanks

Did you take a look on those #11840 (comment) ? Just some cosmetics, doesn't merit hold, but nice to have thanks

Hey @oshoval , thanks for the heads up. I prefer not to hold the PR for this specific change at this point.

There is one more thing that I am not sure about. The first commit could be split but no requirement

I split it at the time to be more readable but eventually we must squash because the changes don't compile otherwise..

I think this OR is made redundant with https://github.com/kubevirt/kubevirt/pull/12097 merged.
Closing


Support remapping mouse buttons

Not sure how hard it would be and if it is out of scope, but remapping mouse buttons would be great. Especially if one could emit keyboard keys with them or other way around (pressing a key to emit a middle button to paste, for example).

You can easily achieve that by writing the name of the mouse in keyboards field. Copy-pasting might not be possible because one to many keystroke mapping is not possible as of now. So no special support for mouses is really needed.

Oh, perfect!


Fix header for httpForward

Fix for #24 : when default headers are set to null, we disable any tweaking of expectations
This should be compatible with previous behaviour since null here was not allowed.

The required checks are not passing and as per the close issue this functionality already exists and has a unit test covering it.


http_client: Struct data is erased for no apparent reason

I'm developing a http_client zephyr application where the server sends a json, that json is stored in a structure.
But when I'm going to make a new request to the server, the struct data is erased .. for no apparent reason.
Does anyone know how to solve it?

Can you elaborate the issue more, it is a bit difficult to guess what you are doing?
Do you have sample code that shows the issue?

Sorry, I'll try to explain it better.
I perform a post to the server to get a json, after getting it I perform the function call "json_obj_parse" to store the data in the struct. I verify the values contained in this structure and are all stored correctly. However, in my application it is necessary to perform a report to the server to inform the next steps, when I call the function "http_client_send_req" the data contained in the struct is deleted. I have already done the passing of this struct by parameter to the functions of my application to observe which moment the clean occurs occurs in the struct and I saw that it was at the time of calling this function.

Ok, perhaps this is related to json api usage. You can see one example how to use the json api in this PR #5035
Checkout the PR and see samples/net/rpl_border_router/src/http.c file for examples of json.

@chtavares592 Is this issue still valid?

@jukkar  ping, please provide latest status

No progress in this front. We would need a way to reproduce this, currently the issue is seen in out-of-tree application. I am closing this for time being, this could be re-opened with a proper way to reproduce the issue.

@otavio sure, I can review that.


Haiku Gen 4 with uplight but no downlight - detects both, creates bad switch

Describe The Bug:
I have configured a Haiku Gen 4 fan with an installed Uplight. During device detection, both an uplight and downlight are detected (see logs below). This creates a second light switch in Homekit which does not do anything, but which when activated (via homekit) confuses the BAF app - even using the BAF app the uplight cannot be used until the erroneous downlight switch is deactivated in homekit and the uplight switch is toggled. E.g. if the erroneous downlight switch is the last-used light switch in homekit, no lights will work.
  What version of the plugin are you using?

I first noted it on 0.5.3, which was the behavior described in the ticket - I then tried 0.5.4-beta10 and the detection bug didn't change, but the switches seemed to confuse the actual BAF app/fan itself even more. I've stayed on beta10 in order to use the noLights pref for now.

I think I have a handle on what's going on but I don't know how to resolve it yet.  I could add a noDownlight pref as a temporary hack or you can run with noLights until we figure out a proper fix.

I'm totally fine to run with noLights for now. Appreciate your looking into it on a Sunday!

As it stands I don't know of non-hacky way to address this without breaking downlight detection for the user who opened issue #14.  I've asked for more information that could help to find a reasonable solution.
In the meantime, I think a config option would be the most practical work-around.

In the interim, having config options to override auto-detection for cases like this might be the most flexible path forward. Basically, for now, keep auto-detection the way it is but give config keys that let a slightly more advanced user say "ignore auto detection, set uplight/downlight/etc to _____"

That sounds reasonable.  How about for now I'll do uplight and downlight and see how that works out?

Makes sense to me

<EMAIL_ADDRESS>groks uplightEquipped and downlightEquipped with values or true or false.  With any luck "downlightEquipped": false should address this extraneous light issue.

Works great with "downlightEquipped": false - thank you @oogje

I know this issue is closed but I'm new to Homebridge and this plugin and I wanted to share my experience incase someone runs into a similar problem I had.
I was running 0.5.4 of the plugin and I have a Haiku H/I fan with an uplight BUT only an LED "downlight" that indicates connectivity to the remote or app. It's not able to be turned on to light the room.
When I first installed the plugin, it would detect the fan with a "Light" switch and an "Uplight" switch. Homebridge would change both switches and reflect the current status as long as I changed it in the app or the remote. As soon as I made the change in Homebridge, the light would stop listening to commands from ALL sources. The only way to fix this was to power cycle it at the wall switch. I initially had given up last night, but I love a challenge.
I found this issue thread and my problem was similar enough that I followed a previous suggestion of trying one of the beta versions. Up until this point, no version of JSON configs would change any of the behaviors. Once I installed 0.6.0 beta 9 and rebooted with my last JSON config file I had previously used, I noticed the JSON had removed some of the variables I had forced before to suppress light detection. It took a few more seconds to connect to the fan (about 5 or 6 reconnect errors), but it finally connected and IT WORKS. I can control the light from Homebridge. All I really wanted to do was to be able to schedule the uplight based on sun up/down throughout the year, heck even a scheduler that let you pick the months that it would be active would've been great...but BAF didn't include that functionality which is CRAZY for how expensive these fans are.
Regardless, I wanted to thank you @tbach for your hard work on this and hopefully my post helps someone else reading this.

To be clear, @oogje did all the work here and deserves all the credit, I just raised the original issue.

You're correct, that was my mistake as looking who closed the issue.
Thanks @oogje !!

You all deserve credit for reporting and engaging.


Fixed invalid syntax in TOSCA 2.0 templates

Replaced 'topology_template' with 'service_template' and property 'constraints' with 'validation'

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

Hi Cyril, thank you for catching this. It looks like these examples haven’t been updated to reflect the current draft of the TOSCA v2.0 spec. We’ll try to do a more detailed review.
Chris
From: Cyril Dangerville @.>
Sent: Thursday, May 23, 2024 11:59 AM
To: oasis-open/tosca-community-contributions @.>
Cc: Subscribed @.***>
Subject: [oasis-open/tosca-community-contributions] Fixed invalid syntax: replaced topology_template with service_template (PR #165)
Definition says its TOSCA 2.0 so should be service_template instead of topology_template

You can view, comment on, or merge this pull request online at:
https://github.com/oasis-open/tosca-community-contributions/pull/165
Commit Summary

d962b08https://github.com/oasis-open/tosca-community-contributions/pull/165/commits/d962b0891bb161c78560af395f78731562dcf453 Fixed invalid syntax: replaced topology_template with service_template

File Changes
(1 filehttps://github.com/oasis-open/tosca-community-contributions/pull/165/files)

M tests/tosca_2_0/profile_versions/service/female_participant.yamlhttps://github.com/oasis-open/tosca-community-contributions/pull/165/files#diff-ec5603411b72d24ab296c3cff02b5331a0f81aafd682c52433aefef021fcfd80 (4)

Patch Links:

https://github.com/oasis-open/tosca-community-contributions/pull/165.patch
https://github.com/oasis-open/tosca-community-contributions/pull/165.diff

—
Reply to this email directly, view it on GitHubhttps://github.com/oasis-open/tosca-community-contributions/pull/165, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASPLIJJRS4H4M3XCTNUR5DZDY36LAVCNFSM6AAAAABIGHAOLCVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYTGNRSHEZTINA.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>


Update README for v7

Won't merge until other v7 PRs are merged

:+1:

Can you add the picture you drew explaining why this exists? I think making a short case for it would be really helpful.

Ooh yeah, good idea!

Coverage remained the same at 98.374% when pulling b62ef9c665c26fa7fe03ae7f6adf95460ab6c0e6 on chore/update-docs-v7 into 6e15ecf5b4313b33bf3131968877d9481011e5a5 on master.

Coverage remained the same at 98.374% when pulling b62ef9c665c26fa7fe03ae7f6adf95460ab6c0e6 on chore/update-docs-v7 into 6e15ecf5b4313b33bf3131968877d9481011e5a5 on master.

Coverage remained the same at 98.374% when pulling c088698723b13b251f973898613ad590a1afdcea on chore/update-docs-v7 into 6e15ecf5b4313b33bf3131968877d9481011e5a5 on master.

Coverage remained the same at 98.374% when pulling 3f4e4a38042f66fbce06b2c9b56d4d1e45e756f7 on chore/update-docs-v7 into 6e15ecf5b4313b33bf3131968877d9481011e5a5 on master.

Coverage remained the same at 98.374% when pulling 3f4e4a38042f66fbce06b2c9b56d4d1e45e756f7 on chore/update-docs-v7 into 6e15ecf5b4313b33bf3131968877d9481011e5a5 on master.


Add trait implementations for Vec, [T], Option

The CI on the main branch seems to fail generally. #1556. So this Pull request will probably be blocked until the CI errors on main branch are fixed.

This looks good, and super useful. Hopefully it can be merged soon :D


Issues with serialized data and non-UTF8 encoding

I store hashes in Redis by serializing them with the help of MessagePack.
The serialized objects typically look like like some variation of this: \x93\x01\x02\x03
The problem is it completely breaks the usability of redis-dump because Yajl throws a parse error when I try to re-load the file:
ERROR (Yajl::ParseError): lexical error: invalid bytes in UTF8 string.
          421,"type":"zset","value":[["??vid?13289295403089412158?tid?
                     (right here) ------^

Any suggestions on how to approach this issue?

Hmm, no, I haven't been able to reproduce it. Thanks for the report.
I'll happy accept a pull request.


Adding file using "Browse Files" button is not working

I used a React component with a modal. When I click on the "Browse Files" button, it doesn't load the file or work properly.
How to recreate: Just install library in your project and then use the example code provided on docs.
versions:
csv-import-react: ^1.0.11
react: ^18.3.1
Component code:
`import { useState } from "react";
import { CSVImporter } from "csv-import-react";
const CsvImportComponent: React.FC = () => {
const [isOpen, setIsOpen] = useState(false);
return (
<>
<button onClick={() => setIsOpen(true)}>Open CSV Importer
  <CSVImporter
    modalIsOpen={isOpen}
    isModal={true}
    modalOnCloseTriggered={() => setIsOpen(false)}
    // darkMode={true}
    onComplete={(data) => console.log(data)}
    template={{
      columns: [
        {
          name: "First Name",
          key: "first_name",
          required: true,
          description: "The first name of the user",
          suggested_mappings: ["First", "Name"],
        },
        {
          name: "Age",
          data_type: "number",
        },
      ],
    }}
  />
</>

);
};
export default CsvImportComponent;`
When i use browse files button it doesnt work. Only drag functionality if working

@Mahmaddz did you figure this out?

@Mahmaddz did you figure this out?

no, i switched to another library


Inconsistent use of symbol and string keys in args (exp and alrogithm).

While it is possible to use symbolized claim names everywhere, the exp claim is only validated if passed as string key to encode.

> JWT.encode({ 'exp' => 'asd' }, 'key')
JWT::InvalidPayload: exp claim must be an integer

> JWT.encode({ exp: 'asd' }, 'key')
=> "eyJhbGciOiJIUzI1NiJ9.eyJleHAiOiJhc2QifQ.vMAZ6k88kjdSq9UW_raFMNlhBGz2L01a_4o_ZI1SCgU"

Which may lead to unexpected results:
> token = JWT.encode({ exp: "#{Time.now + 2629746}" }, 'key')
=> "eyJhbGciOiJIUzI1NiJ9.eyJleHAiOiJhc2QifQ.vMAZ6k88kjdSq9UW_raFMNlhBGz2L01a_4o_ZI1SCgU"
> JWT.decode(token, 'key')
JWT::ExpiredSignature: Signature has expired

While it is possible to use string keys everywhere, algorithm/algorithms is requred to be a symbol, while being in the same options hash where string keys work perfectly fine.

> token = JWT.encode({ 'aud' => 'foo'}, 'key')
=> "eyJhbGciOiJIUzI1NiJ9.e30.FOOB1UqKAhjxqs3lV7BidJ12zFAsIGq1erQfNyaFf80"
> JWT.decode(token, 'key', 'aud' => 'foo', 'verify_aud' => true, 'algorithm' => 'HS384')
=> [{"aud"=>"foo"}, {"alg"=>"HS256"}] # not the allowed algorithm!

Gladly, none is not an allowed algorithm in the payload by default, but if this logic is changed in a wrongfull manner (see https://github.com/jwt/ruby-jwt/issues/323 as a possible cause of such changes, for example) it is going to create a security whole immediately regarding misued string 'algorithm' key.
Anyway, even without the known "alg none" issue, a possibility to unknowingly break algorith validation is concerning.

Didn't notice we've been using sighly older verison. The first issue (exp validation) is actually fixed (can't be reproduced) in 2.2.1.
Though the alg issue is still valid for 2.2.1.


How to define and use REST API of a ldp4j backend app?

Let's say if I want to define an REST API as specified in the LDP4J example:
• Manage persons:
• POST {base}/persons/
• GET {base}/persons/{pid}/
• PUT {base}/persons/{pid}/
• DELETE {base}/persons/{pid}/
then which methods I have to use?
I've found this gragment in the MyApplication.setup() from https://github.com/ldp4j/ldp4j/blob/master/framework/application/examples/src/main/java/org/ldp4j/example/MyApplication.java:
environment.publishResource(
NamingScheme.getDefault().name("PersonResource"),
PersonHandler.class,
"rootPersonResource/");
environment.publishResource(
NamingScheme.getDefault().name("PersonContainer"),
PersonContainerHandler.class,
"rootPersonContainer/");
Note that there is no string equal to "persons" used.
Here are the results I get when I try to connect from Google Chrome ({base}=http://localhost:port/webapp-name):
{base}/persons/ --> "No service was found"
{base}/rootPersonResource/ --> "No service was found"
{base}/rootPersonContainer/ --> "No service was found"
{base}/any-other-name-except-ldp4j/ --> "No service was found"
{base}/ldp4j/ --> ""
{base}/ldp4j/api/ --> "No endpoint found".

Have you had a look at the LDP4j tutorial we held @ ESWC-2015? I suggest you to go over it, as the examples in the LDP4j repository are more geared towards the tests executed during the build process.
You can find the tutorial materials in http://www.ldp4j.org/tutorials/eswc2015/. Part of the materials is a hands-on example application. Have a look at the slides and the source code. I hope those materials are clear enough.

Yes. Of course.
This is what I could find from the tutorial:
public class MyApplication extends Application {
@Override
public void setup(Environment environment, Bootstrap bootstrap) throws ApplicationSetupException {
MyModifiableContainerHandler containerHandler=new MyModifiableContainerHandler();
MyDeletableResourceHandler resourceHandler=new MyDeletableResourceHandler();
// TODO Your handler configuration logic here
bootstrap.addHandler(resourceHandler);
bootstrap.addHandler(containerHandler);
Name<?> rootContainerName=NamingScheme.getDefault().name("containerName") ;
environment.publishResource(rootContainerName, MyModifiableContainerHandler.class, "containerRootPath");
}
@Override
public void initialize(WriteSession session) throws ApplicationInitializationException {
// TODO Your handler initialization logic here
// Remember, the session has to be updated to reflect the state of the data managed by the handlers
}
@Override
public void shutdown() throws ApplicationShutdownException {
// TODO Your shutdown logic here
}
}
===============================================
Frontend component design
Exposed API
17
• Manage persons:
• POST {base}/persons/
• GET {base}/persons/{pid}/
• PUT {base}/persons/{pid}/
• DELETE {base}/persons/{pid}/
===============================================
contacts> retrieve-resource http://localhost/contacts/ldp4j/api/persons/
===============================================
Stupid me. I don't understand how they are related to each other.

Ok. In the hands-on slides are divided into 4 blocks: 1) the recipe for using LDP4j, which provides some examples for creating a simple application (just a basic container and a simple resource); 2) the design and architecture of an example Contacts application; 3) some directions on how to develop the described application with LDP4j (or if you prefer, a description of the implementation you may find in the tutorial GitHub repo); and 4) examples on how to use the application using the client component.
Appart from going over the design and architecture of the application, it is a good idea to have a look at the implementation together with the directions (description) provided in the slides, but it is a better to read first the LDP4j 101 slides.
There, in slide 8, we introduce the notion of Template: the way an application specifies the types of resources managed and how they are (hierarchichally) organized (i.e., membership and attachment) and published (i.e., via relative paths). With this in mind, if you go back to the sourcecode you will see how the API defined in the slides is defined via templates.

Dear Miguel,
Thank you for your reply and detailed explanations!
Unfortunately, I still cannot access to address {baseuri}/persons (on my
Tomcat it is: http://localhost:8080/drumbeat-test-ldp4j/persons).
I could find no place in the example that mentions about term "persons"
(while there are some places for setting path="address" or path="books",
but no class specifies path="persons" or something like that).
Could you please have a look to the attached project and help to find what
I am doing wrong? The code was copied from the ESWC 2015 tutorial code.
Thank you very much!
Best regards,
Nam
On Tue, Nov 17, 2015 at 10:38 PM, Miguel Esteban Gutiérrez <
<EMAIL_ADDRESS>wrote:

Ok. In the hands-on slides are divided into 4 blocks: 1) the recipe for
using LDP4j, which provides some examples for creating a simple
application (just a basic container and a simple resource); 2) the design
and architecture of an example Contacts application; 3) some directions on
how to develop the described application with LDP4j (or if you prefer, a
description of the implementation you may find in the tutorial GitHub
repo); and 4) examples on how to use the application using the client
component.
Appart from going over the design and architecture of the application, it
is a good idea to have a look at the implementation together with the
directions (description) provided in the slides, but it is a better to read
first the LDP4j 101 slides
http://www.ldp4j.org/tutorials/eswc2015/pdfs/eswc-2015-tutorial-3-LDP4j 101.pdf.
There, in slide 8, we introduce the notion of Template: the way an
application specifies the types of resources managed and how they are
(hierarchichally) organized (i.e., membership and attachment) and published
(i.e., via relative paths). With this in mind, if you go back to the
sourcecode you will see how the API defined in the slides is defined via
templates.
—
Reply to this email directly or view it on GitHub
https://github.com/ldp4j/ldp4j/issues/18#issuecomment-157499451.

The point is that you're mixing the examples of the recipe for implementing an LDP4j application shown in the first part of the hands-on slides, with the slides about the description of the API for the hands-on application itself.
If you have a look at the ContactsApplication of the hands-on, you'll see the following code within the setup method:
environment.
		publishResource(
			this.personContainerName,
			PersonContainerHandler.class,
			ROOT_PERSON_CONTAINER_PATH);

This excerpt publishes a resource managed by the PersonContainerHandler class, named as defined by this.personContainerName, at path ROOT_PERSON_CONTAINER_PATH (persons/). Thus, requests to http://localhost:8080/{app-context}/ldp4j/api/persons/, will be handled to the PersonContainerHandler.
Now, according to the organization of the Contacts Application described in the slide #15 of the hands-on slides, you can see that Person resources have an attached Contact container available at contacts/.
As a result the available endpoints are:

{base}/persons/, used for dealing with the collection of persons
that own a contact list.
{base}/persons/{pid}/, used for dealing
with a particular owner of a contact list.
{base}/persons/{pid}/contacts/, used for dealing with the contact list of a particular user.
{base}/persons/{pid}/contacts/{cid},
used for dealing wiht a contact in the contact list of a particular
user.

Then, by having a look at the interfaces implemented by the resource handlers, we get the operations supported by each endpoint, which match those specified in slide #17 of the hands-on presentation.
Now, going to your application what I see is that you publish a root resource for a Person resource (rootPersonResource/) and a Person container (rootPersonContainer/) in the setup and later, in the initialization, you attach the a contacts container to the root person resource.
As persons are ephemeral (can come and go), it does not make sense to have a root person resource. Creating persons and their associated contact containers should be one of the duties of your PersonContainerHandler.
I hope this helps clarifying how the REST API is defined for a given LDP4j application, and allows you completing your test application.


SW-4802 Move findUnusedSquare to helper class

For user-defined planting zone boundaries, we'll want to validate that the
boundaries are large enough to hold monitoring plots before inserting the zone
data into the database.
Ideally, we wanto to do that using the same "find a plot location" algorithm
that's used in real observations. That code is currently in PlantingZoneModel
which can only represent planting zones that exist in the database.
Move the zone search logic into a helper class UnusedSquareFinder.
This is mostly a straight copy-paste of the existing implementation, with the
following changes:

The logic for excluding existing monitoring plots now lives in
findUnusedSquares since it was only ever used via that function anyway.
This requires changing the unit test for that functionality.
The various functions that used to be defined inside findUnusedSquare are
now just regular methods in the new class.
Likewise, some of the local variables from findUnusedSquare are now
instance variables in the new class.
It's no longer possible to specify a grid interval thats different than the
square size. We weren't ever doing that anyway.

Current dependencies on/for this PR:

main

PR #1676   👈

This stack of pull requests is managed by Graphite.


@nestjs/axios 2.0.0 version

I saw that @nestjs/axios is upgrade to version 2.0.0.
I also try to upgrade your project to using that version.
some tests are fail

Can you help me take a look, and upgrade version

any news about that?

I would also appreciate support of axios version 2.0.0

Hi @lamkn06 @pedrovitor074 @bogulean lib was reworked to unbind peer dependencies @nestjs/axios and rxjs.
Lib was published v3.3.0.

@chvarkov much appreciated!


HTTP test documentation based on the recent changes.

Add documentation to the HTTP tests based on the recent environment
variable changes.  This also adds suggested configurations for running
HTTP tests.

Looks Good.  Thanks Jiri!


Dropping Visits example contains error

Not sure if this the correct place to report this, but I think the example for dropping visits for the routing library has an error.
Concretely, it seems to me that the line routing.AddDisjunction([routing.NodeToIndex(i)], penalty) should be routing.AddDisjunction([i], penalty).
For one,
https://github.com/google/or-tools/blob/554cbccaa95b4c11eced13f145de1bf468e1f919/ortools/constraint_solver/routing.h#L516
So AddDisjunction() accepts a NodeIndex, but
https://github.com/google/or-tools/blob/554cbccaa95b4c11eced13f145de1bf468e1f919/ortools/constraint_solver/routing.h#L951
NodeToIndex() accepts a NodeIndex and returns int64.
In the example on the website i and routing.NodeToIndex(i) will be equal, so the potential problem is not apparent there, but in this example that line would cause an issue.

Yes you are right for v6.10.
But soon we will release v7.0 which behave differently.
https://github.com/google/or-tools/blob/72fccd63983b93c655558ca1bdc9ece1d055d7a1/ortools/constraint_solver/routing.h#L555-L557
and you'll need to use:
https://github.com/google/or-tools/blob/72fccd63983b93c655558ca1bdc9ece1d055d7a1/ortools/constraint_solver/routing_index_manager.h#L62
So I would say, documentation is a little bit ahead of the release.
I'm sorry for the inconvenience and confusion


MapManager (replaces PublicManager)

I think the PublicManager is not an ideal solution. This pull request replaces PublicManager by a MapManager with a visible() filter which takes the request object as parameter. It adds additional filters, so that maps of the current user are also included. This also simplifies adding additional permissions.

Purpose sounds OK, but tests are broken :s
Also you may need to add more to tests to cover the new subtleties of the manager.

Yes, I forgot about the tests. Will do soon.
I kept thinking about this change, and now I'm not so sure if I should remove the PublicManager, because it might break other code (I don't know if there are other users of leaflet_storage). Maybe deprecate PublicManager and print a warning if it is being used?
Btw, there's a visible change: the front page and the search page now include maps which are non-public but visible by the current user.
Talking about visibilities: I think the "My Maps" page only shows maps where the current user is owner. Shouldn't this page also include maps where the current user is editor?

I kept thinking about this change, and now I'm not so sure if I should remove the PublicManager,
because it might break other code (I don't know if there are other users of leaflet_storage). Maybe
deprecate PublicManager and print a warning if it is being used?

I feel like we can make this change. This will only change the behaviour for logged in users, and it will only show more maps that this user is allowed to see, so that's fine.

Talking about visibilities: I think the "My Maps" page only shows maps where the current user is
owner. Shouldn't this page also include maps where the current user is editor?

Yes, but only if map edit_status allow editors (or everyone). I.e. not in the case where someone is editor of a map, but the edit_status only allow the owner to edit it.


rotate3d support

First of all, I love velocity.js
I need to do a flip animation from an element's corner (diagonal), like http://codepen.io/anon/pen/OPLomV
pretty easy with transform: rotate3d(45, 45, 0 180deg);
any way one can do that with velocity?

because there's no independent transform property for animating the fourth component (angle) of rotate3d, i can't implement this without some sort of complete overhaul of my matrix manipulation code. i'll link to this in a related thread, but not sure what the chances are of inclusion.
thanks again for bringing this up, alexander. super appreciated.

Aww this feature would be great to have! But I understand why it would be hard to do.


Project private report filters

add more filters to the report. Craig has provided the new filters to add.

engagement type filter

https://docs.google.com/spreadsheets/d/1ZalYnIazOmz39amNxm5OsTGQEdMhtq8s-zx-E9y8uJ0/edit#gid=16484329


codelabs/sign-in: SIGNED_IN vs. STATE_SIGNED_IN

The code section defines constants:
    private static final int SIGNED_IN = 0;
    private static final int STATE_SIGNING_IN = 1;

but the text refers to STATE_DEFAULT and STATE_SIGNED_IN instead.

@joebowbeer thank you for this report.  The sign in codelab needs a number of updates to reflect the current best practices, I hope I can get to this soon.


Make "No templates provided" warning a warning and not an error.

We have uniform folder structures across multiple projects.
Sometimes, we don't yet have sourcery templates for specific cases, which yields this error:
 ❌  error: while reading .yml 'sourcery.yml'. 'Invalid templates. No templates provided.'
What do you think of toning this down to "warning"?

@Lutzifer want to send that pr?

Yeah, still needs some testing, might find some time later today

@krzysztofzablocki I can no longer reproduce this using 1.4.2


Install and Configure UDS RKE2 and Core using Bundling

As of the writing of this issue, UDS RKE2, up until UDS Core, is fully functional and repeatable.
The next steps to the completion of the UDS RKE2 project MVP are to:

[ ] Install and configure UDS Core using UDS bundling and overrides
[ ] Figure out how to expose virtual services via *.uds.dev OR *.uds.prod

Depends on #24


Set packaging_platform default

Prior to this commit there was no default set for packaging_platform,
which would cause any host file that omitted that variable to fail.
This commit sets packaging_platform to the value of platform if it
is unset.

Jenkins, ready for testing

Jenkins, test this please


Additional space on last line

If the last line of data contains less than 8 bytes, an additional space is written after the outer_sep:
https://github.com/sharkdp/hexyl/blob/175847787dd44cfa9536cb1a0980e81b450a587e/src/lib.rs#L340-L349
$ echo -n "12345678" | hexyl --color never --border ascii | wc -L
80

$ echo -n "1234567" | hexyl --color never --border ascii | wc -L
81

This causes an empty line before the footer if the the terminal is exactly 80 characters wide. Is this behavior intended or a bug, because the short_input_passes test also contains the tailing space?

That looks like a bug to me and should be fixed.
Thank you for reporting this!


shutil.rmtree instead of os.rmdir on training directory delete

Right now choosing "d (delete)" does something like os.rmdir('/efs/runs/yuxin_numpy/1gpu')
This fails with OSError: [Errno 39] Directory not empty: '/efs/runs/yuxin_numpy/1gpu'
It may be better to use
shutil.rmtree('/efs/runs/yuxin_numpy/1gpu') instead

It's using shutil.rmtree already.
If files are being opened (e.g. by tensorboard) you'll also see this error. I saw this error quite often actually.

ok looks like shutil called rmtree which gives that error
the actual error was due to NFS/EFS misbehaving. It seems impossible to delete NFS directories sometimes, but it seems possible to move them to /efs/trash as a workaround
>>> shutil.rmtree('/efs/runs/yuxin_numpy/1gpu')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/ubuntu/anaconda3/envs/mxnet_p36/lib/python3.6/shutil.py", line 480, in rmtree
    _rmtree_safe_fd(fd, path, onerror)
  File "/home/ubuntu/anaconda3/envs/mxnet_p36/lib/python3.6/shutil.py", line 438, in _rmtree_safe_fd
    onerror(os.unlink, fullname, sys.exc_info())
  File "/home/ubuntu/anaconda3/envs/mxnet_p36/lib/python3.6/shutil.py", line 436, in _rmtree_safe_fd
    os.unlink(name, dir_fd=topfd)
OSError: [Errno 16] Device or resource busy: '.nfsb3d9a8ed434c603a00000002'

I kept hitting this error, and it turned out to be due to TensorBoard keeping files open. So the trick is to always kill tensorboard before deleting files. Some tricks for future reference
The first command to try is a lazy unmount of the EFS volume. Below is the lazy unmount command.

$ umount -l "EFS mount path"

The command below will find the process that is using the EFS share and output only the process id. Using "ps aux" you can find out more about the process. When ready to kill the process parse the below command to "kill -9".

$ lsof -t "efs/share"

The command below is another way of finding and killing the process in one command. Remove "k" to view the process without killing it.

$ fuser -km "EFS mount path"

I'm not quite following. Why do you umount it? Do you need to mount it back so you can use it?

The umount has the same error as rm, those recipes help track down who is
keeping files open
On Feb 9, 2018 21:18, "Yuxin Wu"<EMAIL_ADDRESS>wrote:

I'm not quite following. Why do you umount it? Do you need to mount it
back so you can use it?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ppwwyyxx/tensorpack/issues/644#issuecomment-364627256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABaHLFqqWAQESD6G2sQ3vQV7-7AsjqDks5tTSasgaJpZM4R_VhP
.


V11 uses LevelDB not neDB files

The plug-in requires updating to work with Foundry V11 LevelDB files (somehow).

See https://github.com/google/leveldb

The LevelDB requires a C++ library to be present as part of the Obsidian server. The default path for finding it is wrong.

Do you think that using C++ library will be on similar approach like this

I have some instructions for how to manually install it - based on trying to install Foundry VTT version 11 on a Raspberry Pi.
I just haven't tried it to see if it is a feasible thing for an Obsidian vault to be able to use that library (there might be web security issues with the vault being able to execute/load a library from outside of the protected vault environment).

It might be more feasible to write a Foundry module to produce an export of an entire world (in JSON format), and then the Obsidian plugin can import that JSON data.

produce an export of an entire world (in JSON format)

Does it really needs to be entire world in JSON format? Would be sufficient to have only journal.db available?

journal.db only exists in Foundry V10 and earlier.
If you are able to recreate a journal.db using Foundry's CLI tool, then you can import that - although you would probably want to regenerate the folders.db file as well, so that the journal entries are created inside Obsidian in the correct folders.

Thinking about adding an "Export Data" context menu entry for compendium folders (see Foundry's exportToJSON function) as a new module.
Allow the Obsidian plugin to name a JSON file instead of a foundry.db file - if a JSON file then it will assume that each JSON object in the file is a separate journal entry.
Then just need to figure out how to include the folders.db information.

Foundry uses the showdown library for HTML <-> Markdown conversion.
Do all the work in a Foundry module to create a single ZIP file, rather than doing it inside Obsidian,

This should be handled by the Foundry module "Markdown Exporter", which is available from https://github.com/farling42/fvtt-export-markdown

So I assume that this is not worth updating for V11 database changes?

So I assume that this is not worth updating for V11 database changes?

The method of access to the DBs in V11 makes it virtually impossible to update this plugin to work from within Obsidian.


[5.8] Drop support for PHP 7.1

Since active support for PHP 7.1 ended on December 1, 2018, we should drop support for PHP 7.1 in 5.8.

We've decided that we will continue to support PHP 7.1 in 5.8. We'll drop support for it in the next major release.


METRON-1191 update public web site to point at 0.4.1 new release

Contributor Comments
This is the pro-forma PR to update the Website for our 0.4.1 release.
All but one of the files below are generated (and they really shouldn't even be in git; see METRON-1192).  For now, all files in site/current-book/* can be ignored, as they are generated from site-book.
The only substantive change is in the last file, site/documentation/index.md , where we change the pointers.
You may validate the new website by cloning https://github.com/mattf-horton/metron.git
branch METRON-1191
and following Evaluation instructions at https://cwiki.apache.org/confluence/display/METRON/Website+PR+Merge#WebsitePRMerge-Evaluation
Pull Request Checklist
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[NA] Has your PR been rebased against the latest commit within the target branch (typically master)?

It is necessarily based on tag apache-metron-0.4.1-release, but is certified to merge cleanly with master.

For code changes:  NA
For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book?

+1.  The release bits seem correct, the site book is correct.  Please keep this +1 in your pocket for 24 hours while the mirrors sync before committing, @mattf-horton   Great job!


disable reduce for loss calculation and calculate mean separately

@lucidrains  did you intend to approve this without merging?

@lucidrains  did you intend to approve this without merging?

@StellaAthena yea, you can approve without merging, sometimes even seek multiple approvals on a team

@StellaAthena yea, you can approve without merging, sometimes even seek multiple approvals on a team


Fix link issue

@gwaybio @roshankern
This quick PR is to fix the link to the RunCellpose plugin as it was going to the out dated version without the functionality to remove edge cells.

@gwaybio @roshankern
Need to close this PR since my local remote repo is not synced with local.


license

Would it be possible to attach a license to this, preferably a MIT or BSD?  Thanks!

Closed via 87d93fb


feat(auth): add error handling to Magento drivers

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Magento drivers have no error handling and will break.
What is the new behavior?

Adds daff errors to the auth package
Adds error transform mappings for the Magento GraphQL errors
Adds Magento response validators
Uses all of the above to implement proper error handling in Magento driver calls

Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

@damienwebdev I changed this to use the generic version of transform errors in the drivers package.


event: better testing of message dropping in Stream

We now test with multiple queue sizes.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#108  👈
#107
#106
#105
#104
#103
#102
#101
#100
#99
main

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

Join @jespert and the rest of your teammates on  Graphite