Unity 5.2.2f / SDK 0.5.2 - Renderproblems distortion / Startglitch / missing Gui Elements

My App starts in portrait mode, let the user browse through menues, vr mode is startet later.
My short setup (similar as in a recent issue from me), which you recommended:

a Cardboard object (just cardboard.cs) in scene
in the inspector for the Cardboard component, VRModeEnabled = off.
the prefab is added later, a prefab without the cardboard component

primary Bugs/Problems (Android):

directly after splash screen there is a frame where the alignment marker and settings button appear = Startglitch
If have enabled the settings button and the back button... but they're not visible. Only sometimes, very randomly.
When I press home and then resume to the app, many bugs appear: random crashes and many distortion problems, sometimes the back and settings button appear suddenly, sometimes not... I append a screenshot with some samples... all taken within 5min in the same app version on a samsung s6.

One note: In editor everything works fine, exept when I switch to other windows and refocus... very seldom I get a null reference from Cardboard.cs line 627 from OnApplicationFocus() - maybe this could be also the reason for some crashes on android... hope this helps.
For all other points I'm looking forward for solutions, advices or maybe I can help to make it more stable.

For picture#1, make sure the main camera's background color has is fully opaque (alpha is turned all the way up).
For the start glitch, try setting the Enable checkboxes for each UI element to false.  Wait till you enable VR mode to turn them on.  This may affect the visibility bug you sometimes see.
I'm not sure that will fix ask the pause/resume issues.  For those, cash you see anything in the adb logcat?

I took the cameras from the prefab, the only settings I changed are the clipping planes to 0.01. And I set the toggle culling mask @ cardboard eye script.
I tried your advice and turn the settings and back button off and after instantiate to on, but this doesn't help. The glitch is still there.
I also changed the cameras to solid black color, the distortion bugs seem to disappear, but difficult to say, they're not constant bugs.
Meanwhile switched to 5.2.2 - I'll also change the title. I still try to figure out from where the crashes come... The app never crashes after first start. When I go to pause (via home button) and then return a crash is very likely, but not always...

First problem might be if you have another camera (which is not related to cardboard) in your scene. Problem with cardboard UI (settings button) i have it too.

I've to correct me: the setup of your scene doesn't matter. The startglitch is always there... it just isn't so obvious, when the settings/alignment/back button stays there, because your app starts with vr mode enabled... even if you just turn off vr mode from one of the prefabs (single cam mode) and so also the gui elements should be not visible, there is also a short frame between loading and your scene... so all in all it just would be cool to have more control or possibilities to divide between menue/app stuff and a vr mode... besides: this is the app I'm talking about: https://play.google.com/store/apps/details?id=com.mikavaa.vrais

Same, startglitch,  checkboxes are unchecked, and  i've also set the : EnableAlignmentMarker = false; and EnableSettingsButton = false; by code, but nothing the glitch remain. I've noted that this appear only on the Android build. On iOS after setting the values to false from  the code  all it's ok .

I have the same problems. App always crashes and no ui elements on the screen. DId you solve your problem?

No, I haven't a solution and even not an idea what else to try... in my eyes, the sdk needs definitly an update. I have another bug sample, which makes everything even more confusing for me. I have two cardboards V2.0... one from Zaak, one from google via a conference (the cardboards have been sponsored by google)... when I configure the viewer I get very different lens distortion... and the one from zaak seem to be correct. I have no idea why and I also remember, that both cardboards had the same correct distortion two weeks ago. These test are from Moto x 2nd. But on a samsung s6 I've seen same problems,,,, for better understanding see image attached below:

The SDK definitely needs an update -- there are several bugs already on the list of what needs to be fixed, including the start glitch.  I'm not allowed to say anything about when new releases are scheduled though :(

So this is good and bad news... good, because I stop thinking about fixing these issues and if they are're caused by me, bad, that I've no idea when I can say to our customers (even more for myself): Now I have an reliable vr mobile workflow with untiy + google sdk... looking forward the update. Is there maybe a source you can tell me/us from where we get the latest news about such update?

We can still try to find a workaround for you with the current SDK too.  Also, I typically come back through these issue posts and say when a new release is available if it has a fix for that issue.

Hey everyone,
I'm fighting the startglitch to. I even commented out the GL rendering code in CardboardPostRender.cs.
Unfortunately even then the alignment marker is appearing in the glitch at the startup and even after that.

As far as i understand this GL is drawn only on devices that don't support native UI. In other way marker and other elements are generated from android plugin.

As simple workaround for missing gui elements, maybe interessting for someone:

disable settings/back button in cardboard.cs
in CardboardPreRender.cs set camera.depth from 100 to 99 for example
use your own gui cam on depth 100 with similar icons/buttons and use anchors for position (in my case ngui, but unity ui should also work)
call Cardboard.SDK,ShowSettingsDialog() and what you want on back button

To prevent some crashes I would like to quit the app, if the user pauses the app. I know, not best pratice, but most crashes (maybe all, and with no debug logcat output) happen after resuming the app. But when I want to use this code for example:

I just wanted to add that we're facing the same startup glitch bug and have tried all suggestions listed here. SDK 0.5.2 Unity 5.2.2p4

OK, sorry for the long absence from this thread.  @HansBernd The GL rendering code in CardboardPostRender.cs is only for when you run the game in the editor.
The "start glitch" is due to the native Java code that creates the UI elements.  It has their visibility set initially to "on", and only after that does the Cardboard SDK get a chance to turn them off.  So you can see a flicker.  As we see, this is a hard problem to work around from the Unity level.

So than isn't it possible that someone, who is able to, change (I assume unityvractivity.jar) the java code and set visibility initially to "off"?
Another important fix would be, that we can quit the app properly as described 3 posts above without timeout... that would make a more or less stable release possible.

Yes, changing the Java code would work.  (I counted Java as "native" code because of the need to marshal calls from .NET)

Any chances of an update? I think there're enough bugs to fix and I wondering, when I see new posts and tweets about google cardboard sdk and unity, how easy it is, but no one talks about the problems... 3 months is a loooooong time for an important update :(

Definitely updates are coming.  We just aren't allowed to give exact dates, I guess because it's better to not make a promise than to make one and have to break it :(

I saw, there's an update. Great! I'll test it and post the result here.

I'll close this issue after the new sdk release 0.6. This solves the

the startglitch
missing Gui Elements

All other problems (crash/timeout) are discussed in a new thread #137


CentOS 7: Avoid SELinux protection (Error 503) with enforcing mode

After the Linux installation, the 503 error appears (on CentOS 7).
To avoid this problem WITHOUT deactivate SELinux :

Download the attached file httpdPolicy.zip and unzip it to get the .pp file
Launch this commandline : semodule -i httpdPolicy.pp
Current mode for SELinux sestatus would be "enforcing" & reboot

Hi,
Thank you for the useful notice.
I moved this information to our forum https://forum.rapidscada.org/?topic=centos-7-avoid-selinux-protection-error-503-with-enforcing-mode because the forum is the knowledge base of Rapid SCADA. I would like to receive more information about this issue from different users to decide if we should include this instructions into the installation package.


[WIP] Adding commands for validate and start-upgrade

Description
Initial go at fleshing out validate and start-upgrade. Simplistic approach so far, looking for feedback.
Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Looks reasonable to me (my 2 :moneybag: - I wanted an emoji for coins/cents)


Add UI control to open settings directory

This would be easier than guiding users to enter  %APPDATA%/Chatterino2/Settings into their windows explorer address bar + it's compatible with all platforms automatically and can reflect special cases such as portable installations.
(similar to how the Open Resource packs folder button works in Minecraft, it launches explorer.exe on the directory)

This could also easily respect the users portable settings, since it should know exactly what folder to open. :+1:

This was added


Rename test.md files to README.md files

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.592%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
594

Relevant Lines:
892

💛  - Coveralls


Add Issue Templates to all the repos

This needs to be done in all repos:
https://github.com/liatrio/backstage-liatrio-dora-plugin
https://github.com/liatrio/liatrio-react-dora
https://github.com/liatrio/liatrio-dora-api

name: Bug Report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

name: Feature Request
about: Suggest an idea for this project
title: ''
labels: enhancement
assignees: ''

Is your feature request related to a problem? Please describe.
A clear and concise description of the problem or issue.
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.

@Wolftousen Were this what you were thinking?

Those look good to me, but for Bugs at least, we'll also need to be supplied some data that's been anonymized to replicate


Setup code structure and point fstab to SP

Because this is just part of a site (5 pages or so under /used-cars*), we cannot have styles/scripts etc live at the root and they need to live under a folder so that we can open up the existing CDN to our origin.
Plan is to store all the code under "aemedge" folder which will then be routed to the helix origin from the original site.

Completed


Server on Mac osx

Hi!
I installed with success this package on a Linux machine and everything seems to work fine. I would like to do the same on a Mac, but I have difficulties (commands are different). Has anybody tried it?
Thanks,
Stefano

It works the same on macos! Can you give specific examples?

Well, I didn't even try. Do you mean that it is enough to change
"systemctl" with "launchctl" and everything is fine? In case, this could be
worth mentioning in the README, I guess.
Stefano
Il giorno mar 17 dic 2024 alle ore 09:14 Fons van der Plas <
@.***> ha scritto:

It works the same on macos! Can you give specific examples?
—
Reply to this email directly, view it on GitHub
https://github.com/JuliaPluto/PlutoSliderServer.jl/issues/155#issuecomment-2547762017,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGVYHFVYNKDP6DPCIJYJMT2F7MMVAVCNFSM6AAAAABTQGEGP2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXG43DEMBRG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
———————————————————————————
Wong: How's your Sanskrit?
Dr. Stephen Strange: I'm fluent in Google Translate.
Doctor Strange
Stefano Covino
INAF / Osservatorio Astronomico di Brera
Via Emilio Bianchi 46, 23807
Merate (LC) - Italy
Tel.: +39 02 72320475 (office)
FAX: +39 02 72320401
Cell: +39<PHONE_NUMBER>
E-mail: @.***
URL: http://www.merate.mi.astro.it/∼covino


Retry EC2 tags fetch in case of rate limits

If we're asked to fetch EC2 tags as agent tags/meta-data then try a couple of times in the face of failure in case we hit rate limits or network problems.

@keithpitt I think this is fine, it's just a copy/paste, but would you mind doing a quick review? I'm not sure how to test the failure case. I have manually tested that it still works when running an agent on an ec2 instance with tags.

@sj26 try running it on your local machine :) That should trigger the error state!

Oh, that won't work since it auth's AWS just above. You can test it on a machine that has disallows the "get tags" IAM permission

@keithpitt good idea, thanks!

Oh, it looks like the latest beta agent actually already does this, thanks to
https://github.com/buildkite/agent/commit/1d671548fd24bc3c40fe46152394e097a8b7e189
I'll backport that to stable instead.

@sj26 oh sheet! Sorry, I totally forgot that this PR existed - I think I even helped write a little bit of it. My brain totally broke - sorry!!

See #461.


Add monitor changed event

Hey, my idea was to add another event if the monitor name has changed. I implemented it first for X11, because I am not sure if the approach is the right one. WDYT?

Hi, and thanks for the PR!
I'd be down with adding this. The approach seems about right (at least from my limited knowledge of the X11 backend), but there are a couple of sticking points that came up which I've added review comments for.
I'd like to get some idea of what support looks like on other platforms before merging this, though. Off the top of my head Windows probably supports it and Wayland probably doesn't, but we'd need to look into how MacOS handles it. @francesca64

@Osspial this would be trivial to implement on macOS, so no worries there: https://github.com/tomaka/winit/blob/84c812e5689b2561fbcde8c07efa05ff0dc52ddb/src/platform/macos/window.rs#L261
The X11 implementation here looks good too.

Hey, this hasn't had activity for a good amount of time, and looks like its fallen out of date. Can you rebase this against master, and submit a new PR. Anyways, closing this one, thanks.


Allow for multiple ID deletions at once

Motivation for changes:
Making it easier to delete items from an entry-list via CLI
Detailed changes:

Entry ID is treated as a csv list, so one can delete multiple entries with flexget entry-list <list-name> <entry-id1>,<entry-id2>,...
Title fallback remains unchanged (one entry per run)

Output:
$ flexget entry-list del testy 263527,263556,263557,263558,263590,263591,263778,263779,263780,263781,263782,263815,263848,263977,264010,264043,264231,264294,264295,264513,264762,264950,264982,265169,265232,265233,265345,265346,265360,265361,265362,265363,265364,265365,265366,265367,265368,265369,265649,265873,265906,266100,266165,266230,266245,266406,266471,266504,266505
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy
Removing entry `XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX` from list testy

It seems a bit weird and messy for one command out of a handful to support comma delimited arguments. I'd consider adding this to the others where it makes sense.

This is kinda interesting, but I think it should be handled at the argparse level by allowing sending multiple values to the same param

I agree with you both, however expanding the parsing to that level while my original intent, was a few layers beyond my limited knowledge. I stared at def handle_cli and manager.py for a couple hours and couldn't figure out how, so I tried the "dirty simple" way high up the entry-list del level.
Feel free to take this PR as a feature suggestion instead and just close it, I was going to cleanup that list with these dirty changes and go back to using master anyway 👍

Multiple values seem fine and all, for example kill command takes any number of pids. But using comma makes terminal wizards work really hard. Use spaces so things like $( ... ) work.


Spotlight gizmo forward vector is the same as editor camera forward vector

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Linux, d1cb73b47a17de830d9474026ffa7b3587cfbc68
Issue description:
I noticed that gizmo of spotlight acts in a very weird fashion, it looks like spotlight gizmo is mimicking editor camera:

Steps to reproduce:

Open new scene
Add SpotLight node to the scene
Ensure SpotLight node is selected
Rotate camera

duplicate of #10706

Yes indeed. Closing as duplicate of #10706.


methods clarification

Hi @yzqin
Exciting work! Can you please clarify which methods are used for hand pose estimation and retargeting? I think they are from https://github.com/yzqin/dex-hand-teleop/tree/main, just to double-check.

Hi @JiaheXu,
The hand pose estimation part is very similar as the repo you mentioned. However, the retargeting method is developed based on previous repo and make it much better than previous one. It achieve faster speed and better optimization compared with retargeting method used in our previous work.


Fix error message bubbling up on seed error

Problem: When the nth seed throws an error, all subsequent seeds add an error message on top of original message which makes it less clear which seed the error originated from.
Solution: Nest promises and catch error inside the nested seed promise.
Before:
Error: Error while executing ".../knex/seeds/9-titres-activites.js" seed: Error while executing ".../knex/seeds/8-metas-activites.js" seed: Error while e
xecuting ".../knex/seeds/7-titres.js" seed: insert into "titres_points" ("contour", "coordonnees", "description", "groupe", "id", "nom", "point"
    at Object.current.then.then.catch.originalError (.../node_modules/knex/lib/seed/Seeder.js:166:23)
Error: Error while executing ".../knex/seeds/8-metas-activites.js" seed: Error while executing ".../knex/seeds/7-titres.js" seed: insert into "titres_poi
nts" ("contour", "coordonnees", "description", "groupe", "id", "nom", "point"
    at Object.current.then.then.catch.originalError (.../node_modules/knex/lib/seed/Seeder.js:166:23)
Error: Error while executing ".../knex/seeds/7-titres.js" seed: insert into "titres_points" ("contour", "coordonnees", "description", "groupe", "id", "nom", "point" [...]
    at Object.current.then.then.catch.originalError (.../node_modules/knex/lib/seed/Seeder.js:166:23)

After:
Error: Error while executing ".../knex/seeds/7-titres.js" seed: insert into "titres_points" ("contour", "coordonnees", "description", "groupe", "id", "nom", "point" [...]
    at Object.current.then.then.catch.originalError (.../node_modules/knex/lib/seed/Seeder.js:166:23)

LMKWYT,
Cheers.

Hi Igor,
Sure, this behavior is not trivial, but I'll try to come up with something.

Alright, I've added a straightforward test, which fails on master but passes on this branch.
Error output on master:
Error while executing "[...]/knex/test/unit/seed/test/2-second.js" seed: Error while executing "[...]/knex/test/unit/seed/test/1-first.js" seed: throwing in first file

Error output on this branch:
Error while executing "[...]/knex/test/unit/seed/test/1-first.js" seed: throwing in first file

PS: tests seem to be quite broken on the past few pull requests, is it so;ething to be worried about?

@risseraka There are some flaky Oracle tests, these are to be ignored, anything else - I'd need to check that out :)

Thanks a lot for your contribution!

You're very welcome, thanks for your and every contributor's hard work.
(Impressive speed by the way. 😅)

My pleasure!
How urgently do you need this change released? I wasn't planning another release before 0.18 unless something serious popped up, but we can figure something out if it's something you need urgently.

@kibertoad No worries, there's absolutely no urgency, it was just a bit annoying to look at logs on errors, so it's mostly cosmetic, take your time to release whenever you see fit.

Released in 0.18.0-next1

Thanks for the heads up.
Hurray for @kibertoad!


Expression Idea

hey @malaybaku
would you add to the program function that , can recognized face expression
by the webcam?

@DemonRem
Thanks for the idea, but now is not the timing because :

This requires higher webcam resolution so #415 should be solved first
Current VRM BlendShape standard is not suited for those exression unless I could achieve very high precision. VRM 1.0 will be more comfortable in this point.

Based on those point I put label "VRM 1.0" to this issue.

close as staled issue


feat: improve spark routes output for View routes

Description

improve spark routes output for View routes

$routes->view('about', 'pages/about');

+---------+-------------+------+------------------------------+----------------+---------------+
| Method  | Route       | Name | Handler                      | Before Filters | After Filters |
+---------+-------------+------+------------------------------+----------------+---------------+
| GET     | about       | »    | (View) pages/about           |                | toolbar       |
+---------+-------------+------+------------------------------+----------------+---------------+

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Please review #7653 first.

Rebased and added docs.


fix(ci): decrease verbosity of expandedJson with new metadata

The payload for the ci report had repeated information that could be considered metadata. Extracting the metadata to its own property will drastically reduce the payload size.
Fixes: https://github.com/harlan-zw/unlighthouse/issues/115

Great work <3


fixes troubleshooting-kubeadm references to taint node-role.kubernetes.io/master

The role.kubernetes.io/master taint referenced on the troubleshooting-kubeadm page should be node-role.kubernetes.io/master.
Please let me know if I should remove the other lang changes. I'm not sure what the procedure is for code snippets vs actual translations. Thanks.

Do I need all three reviewers because I touched the other langs and then removed the changes?

no, i don't think so, even if the labels remained.
/assign @gochist
try asking on #sig-docs on k8s slack if no approval is reached until e.g. mid next week.

/cc
i will sycn th zh once this merged

/lgtm
kindly /cc @sftim

/remove-language ko

/remove-language ja
/remove-language zh

/sig cluster-lifecycle

/approve


Sync GitHub issues to Jira

Ported from https://github.com/canonical/mysql-operator/pull/108

I'll be merging the fixes for the tests tomorrow, so this can be merged even if they fail.


Function that is failing to compile should not continue to execute (and fail) repeatedly

We've seen cases with a failing script compilation hooked up to a high throughput event source (such as an event hub with a large number of events). Its extremely wasteful - we should stop the function from triggering until there is a successful compilation.

Related (possibly duplicate) issue: https://github.com/Azure/azure-webjobs-sdk-script/issues/169

@mathewc will come up with a proposal


fix: spinjs at 2.3.2 as 3.0.0 is now typescript

➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖
⚠⚠⚠  THIS BUNDLE HAS ENTERED INTO ITS FEATURE FREEZE PERIOD  ⚠⚠⚠

Pull Requests with New Features will no longer be merged.
If you want to propose some new feature, please create an Issue.
Pull Requests that fix bugs are still accepted and greatly appreciated.

➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖➖

@rmisos please, could remove this PR for only commit the first commit? the other two commits willl be added to the history if I merge and they are not needed (you can remove it in your local and push -f to force to delete the 2 last commits)

Closing in favour of #199


Fix version file and checksum creation for new kubernetes versions

While working through updating to kubernetes 1.19.4, I was testing out the scripts that generate the version file and checksums.  There were a couple of changes needed due to some of the later bin directory changes I assume.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


bindgen: Use -fshort-enums to coerce Clang to behave in the same manner as ARM GCC

Summary
Enum types being generated by bindgen currently appear to be annotated with #[repr(u32)] regardless of whether the enum's data type can be smaller.
Normally, this would be the expected behaviour - however, using the GCC-based ARM toolchain bundled with FBT, it appears that short enums (-fshort-enums) are used. This can cause misaligned reads on variables and struct fields from the Rust-side as a result.
As an example, this is how InputEvent is represented in Flipper's firmware.elf (both for compact and debug builds - so the optimisation flag appears to be irrelevant):
(gdb) ptype /o InputEvent
type = struct {
/*      0      |       4 */    uint32_t sequence;
/*      4      |       1 */    InputKey key;
/*      5      |       1 */    InputType type;
/* XXX  2-byte padding   */

                               /* total size (bytes):    8 */
                             }

Where InputKey and InputType are treated as u8 types, versus the same structure's representation under flipper0-sys's bindgen:
#[repr(u32)]
#[non_exhaustive]
#[doc = " Input Types"]
#[doc = " Some of them are physical events and some logical"]
#[derive(Clone, Hash, PartialEq, Eq)]
pub enum InputType {
        #[doc = "< Press event, emitted after debounce"]
        InputTypePress = 0,
        #[doc = "< Release event, emitted after debounce"]
        InputTypeRelease = 1,
        #[doc = "< Short event, emitted after InputTypeRelease done withing INPUT_LONG_PRESS interval"]
        InputTypeShort = 2,
        #[doc = "< Long event, emmited after INPUT_LONG_PRESS interval, asynchronouse to InputTypeRelease"]
        InputTypeLong = 3,
        #[doc = "< Repeat event, emmited with INPUT_REPEATE_PRESS period after InputTypeLong event"]
        InputTypeRepeat = 4,
        #[doc = "< Special value for exceptional"]
        InputTypeMAX = 5,
}
#[repr(u32)]
#[non_exhaustive]
#[derive(Clone, Hash, PartialEq, Eq)]
pub enum InputKey {
        InputKeyUp = 0,
        InputKeyDown = 1,
        InputKeyRight = 2,
        InputKeyLeft = 3,
        InputKeyOk = 4,
        InputKeyBack = 5,
        #[doc = "< Special value"]
        InputKeyMAX = 6,
}
#[doc = " Input Event, dispatches with FuriPubSub"]
#[repr(C)]
pub struct InputEvent {
        pub sequence: u32,
        pub key: InputKey,
        pub type_: InputType,
}

This PR sets the -fshort-enums flag in the local SDK build process such that the behaviour is the same across both toolchains. I am fairly new to Rust, so any comments / changes around this are very much welcome.

@Psychotropos,
Thank you so much!
I'll merge it after tests.
Also there are some missed parts that depends on size of enum, furi error for example. Anyway, that is point to change but I have to fix repo there.
Sorry for broken CI tests that not triggered (issue #36), now it fixed.
Could you please move it up? (rebase or just merge actual main head into you branch)

I'll merge to other branch with my fixes, then merge into upstream.

@Psychotropos, seems that's not works, FuriStatus (for example) still generates with repo(i32).
That's not so easy...

Merged with #38 🎉


rename of script install-v2-alpha.sh

we should rename deis cli download script install-v2-alpha.sh to install-v2-beta.sh when we have beta cut

My thoughts - why not just install-v2.sh?

or even just to install-v2.sh

Fixed via https://github.com/deis/deis.io/pull/148


Use Rust's chrono library for all the Date functionalituies

When playing around with fend and reading the source code I found that today is not implemented and that all the functionalities for working with dates use quite complex, custom code. I thought that all this could be made much simpler and less prone to bugs if the code was refactored to use a dedicated library for working with dates. The functionalities are available in chrono library.
The refactor has several consequences:

The code is simpler and should be easier to maintain.
It uses a high-quality library designed especially for the purpose of handling dates which comes with many benefits like smaller risk of bugs.
It breaks backward compatibility: serialization has changed (but with more work, it would be possible to make it consistent) and since different algorithms are used, there are some subtle differences, e.g. tests that were expecting an error when subtracting a year because of landing at a nonexistent date now fail because the chrono library picks the closest date instead.

The code is not polished. I'm sending this PR for consideration if a change like this would be welcomed. If you are interested in the change, I may make some improvements in the code later.

Hi, thanks for your PR!
When I originally implemented the date handling functionality, there were a couple reasons I went for a custom implementation rather than using chrono or another crate:

I wanted to avoid pulling in a third-party dependency in the core crate, since I quite like how it's completely dependency-free at the moment. This is also why I'm not using any libraries for the maths part of fend, like there are a lot of arbitrary-precision maths libraries that would probably be useful.
Using another library might make it more difficult to integrate with fend's parser code, especially for syntax like @2023-09-14 (but this could probably be worked around)
I also quite like the existing behaviour of producing errors when subtracting non-existent dates, like @2024-02-29 - 1 year

You might have noticed that there's some skeleton code for things like today, which never got implemented properly. I think pulling in chrono in the CLI crate to retrieve the current date and timezone and such would be a good idea, and to add support for expressions like today or now, but I think I'd prefer to keep the core crate dependency-free and to implement the necessary functionality ourselves.
Then again, if there are some more complex features that would require the chrono crate that you'd like to implement, I could accept a PR if the dependency is optional, and fend continues to work with the existing functionality when the dependency is disabled.

Initially, I tried to fix today by using chrono there, but then it seemed to be an overkill to have a dependency only for chrono::Local::now() and it needed a lot of code to translate between the date formats. Using chrono everywhere seemed to be a better idea. But this is just an idea, feel free to close the PR.


Does operator-sdk support file-based catalogs?

Type of question
Open question
Question
I'm adding OLM support to my operator. When running make catalog-build I see a warning saying that Sqlite-based catalogs are deprecated. Since this is a new catalog, I don't want to build it with a deprecated technology. What can I do? Thanks!
PS Sorry if this question has been asked before. I searched the issues and couldn't find it.
What did you do?
operator-sdk init --project-name ${project} --domain ${domain} --repo ${repo}

$ make catalog-build

What did you expect to see?
No deprecation warning
What did you see instead? Under which circumstances?
...
WARN[0000] DEPRECATION NOTICE:
Sqlite-based catalogs and their related subcommands are deprecated. Support for
them will be removed in a future release. Please migrate your catalog workflows
to the new file-based catalog format.
...

Environment
Operator type:

/language go

Kubernetes cluster type:
N/A
$ operator-sdk version
operator-sdk version: "v1.26.0", commit: "cbeec475e4612e19f1047ff7014342afe93f60d2", kubernetes version: "1.25.0", go version: "go1.19.3", GOOS: "darwin", GOARCH: "arm64"

$ go version (if language is Go)
N/A
$ kubectl version
N/A

@murphd40 Thanks for raising this issue! This is a known issue and we have an existing issue to track this (https://github.com/operator-framework/operator-sdk/issues/5832). Unfortunately we aren't decided on the best way to move forward with implementing a generalized approach and is something we are hoping to come to a decision on as we get more overall feedback on how FBC is utilized in developer workflows.
For the time being, you may be able to modify the make target yourself to use the opm migrate command to migrate from the SQLite bundle format to the FBC format.
I hope this helps!

Thanks @everettraven 👍

Closing this issue since FBC support is already tracked in #5832


When writing data, make sure that values are truly empty

When writing data from wrangles and the values come out empty (None, '', NaN) make sure that the value is truly empty. Not just ''.
Maybe specify using something like df['DataFrame Column'] = df['DataFrame Column'].fillna(0)

@ChrisWRWX  Wrangle to replace '' to None, NaN, or any other values?
using:
df['col'] = df['col'].replace('', None, inplace=False)
Using recipe does not seem to work
  - pandas.replace:
      input: col
      to_replace: 'black'
      value: 'BLACK'
      inplace: False

inplace is set to False as default, it is not required

@ebhills
One way to get around the empty string '' as an output is to use replace (pandas function)
- pandas.replace:
      input:
        - col
        - col2
      parameters:
        to_replace: ''
        value: Null # output will be None

If the output needs to be NaN, then numpy needs to be imported using np.nan


What is the difference between this project and QuickSQL?

I saw there is another project named QuickSQL under Qihoo360, what’s the difference between them?

QuickSQL is different from XSQL. QuickSQL just like a router but XSQL under the calculate engine.

You mean QuickSQL has no calculation ability but XSQL has?

Yes. XSQL extends Spark SQL.


in long command strings, 8,262th character consistently missing

I'm passing hundreds of commands to mParallel, and I just noticed that one of the processes always fails, and this results from omission of exactly the 8,262th character from each string when the command is passed to the console.  Please see the attached example of the input batch where the commands are specified correctly, and the attached log where the command actually run is missing a character that causes the file path to be jibberish.
peptideProphet.example.txt
mparallel.log.txt

Hello,
it's a bit hard to understand from your logs what is the expected outcome and what actually happens. So, could you please provide a minimal example –  full command-line plus (if required) input file – that I can use to reproduce the issue?
Regards,
MuldeR

Thanks for being responsive, but I think this is out of your control as a windows command length limit.  I'm using version 1.0.4 - apparently there is a hard limit about how many characters a single command can be in windows cmd.exe.  The limit is something like 8,190 characters.   To avoid this I changed my java code that creates my .bat to check if the stringbuffer.length()> 7000 and if so, write one mparallel line and start a new one.
Still, if you want to reproduce it, you can make a mparallel command that submits 10,000 ping requests in a batch file thereby containing more than 8,262 characters and you'll notice that one of them has non-zero exit because a character is missing.

You man that your command-line MParallel command-line exceeds ~8000 characters? :fearful:
In this case you really should do things differently in order not run into the command-line length limit!
Your are probably calling MParallel like this:
MParallel.exe [options] <command_1> : <command_2> : ... : <command_n>

A better method for a large number of commands would be:
Parallel.exe [options] --input=commands.txt

...where the text file commands.txt contains all your commands to execute – one command-line per line.
Also I highly recommend you familarize yourself with the pattern --pattern option.

Awesome, thanks for the suggestion!  Seems obvious to use a command txt file I didn't realize you had that support.  Thank you!

Using a text file should be way better.
But you can even pipe the commands directly from your Java program, so no temporary text file needed.

Yes, using a text file should be way better for a long list of commands.
But you can even pipe the commands directly from your Java program, so no temporary text file needed.

Also, with a pattern you can greatly simply "similar" commands:
If, for example, you want to run many commands like program.exe -i "input_xxx" -o "output.xxx.
You can simply do:
MParallel.exe --pattern="program.exe -i \"{{0}}\" -o \"{{1}}\"" --input="file_list.txt"

...where file_list.txt contains the parameters to be filled in, e.g. the path of the input/output file.

Yes, using a text file should be way better for a long list of commands.
But you can even pipe the commands directly from your Java program, so no temporary text file needed.

Also, with a pattern you can greatly simplify "similar" commands:
If, for example, you want to run many commands like program.exe -i "input_xxx" -o "output.xxx".
You can simply do:
MParallel.exe --pattern="program.exe -i \"{{0}}\" -o \"{{1}}\"" --input="file_list.txt"

...where file_list.txt contains the parameters to be filled in, e.g. the path of the input/output file.
For example, it could look something like this:
input_001.foo output_001.bar
input_002.foo output_002.bar
input_003.foo output_003.bar
[...]


WinUI 3.0 Preview 3 Applications crash on startup in Windows Insider Build 21227

Describe the bug
WinUI 3.0 Preview 3 Applications (both UWP and Desktop and both C# and C++) crash on startup in Windows Insider Build 21227. This behaviour was not observed in earlier builds.
Steps to reproduce the bug
Steps to reproduce the behavior:

Load Visual Studio 2019 Preview 2.
Create a new WinUI 3,0 Preview 3 Project (UWP or Desktop, C# or C++)
Build the Application (x86 or x64 - both exhibit this behaviour)
If you attempt to debug the Application on Windows Insider Build 21227, the VS Debugger will crash.
If you deploy the Application on Windows Insider Build 21227 and run it (e.g. from Start) it will crash.

Expected behavior
The Application to load.
Version Info
NuGet package version:
[Microsoft.WinUI 3.0.0-preview3.201113.0]

Windows app type:

UWP
Win32

Windows 10 version
Saw the problem?

Insider Build (21227)
Yes

Insider Build (20270)
No

If it helps, on each crash (both x64 and x86) there is a watson report with the following sort of details:
Problem signature
Problem Event Name:	MoAppCrash
Package Full Name:	cf710d84-b57a-45d1-927b-35e5575541be_<IP_ADDRESS>_x64__pzhjvzqrkcdyt
Application Name:	praid:App
Application Version:	<IP_ADDRESS>
Application Timestamp:	5f8de3c6
Fault Module Name:	combase.dll
Fault Module Version:	10.0.21277.1000
Fault Module Timestamp:	5ebfb7ba
Exception Code:	c0000602
Exception Offset:<PHONE_NUMBER>213e49
OS Version:	10.0.212<IP_ADDRESS>.256.48
Locale ID:	2057
Additional Information 1:	f848
Additional Information 2:	f848ae3eb9da603e3d133c649245b573
Additional Information 3:	6c20
Additional Information 4:	6c20af286a841c116e408ceff9fafd07
And under the debugger:
Problem Event Name:	APPCRASH
Application Name:	msvsmon.exe
Application Version:	16.9.733.0
Application Timestamp:	5fc92e7f
Fault Module Name:	combase.dll
Fault Module Version:	10.0.21277.1000
Fault Module Timestamp:	5ebfb7ba
Exception Code:	c0000602
Exception Offset:<PHONE_NUMBER>213e49
OS Version:	10.0.212<IP_ADDRESS>.256.48
Locale ID:	2057
Additional Information 1:	19be
Additional Information 2:	19be555bc0752265a36ee49cbe0b2fac
Additional Information 3:	6daa
Additional Information 4:	6daab691c59d0ef5816d18d88c9c7b7d

I'm having the same issue on build 21277.1000, but if my memory serves correctly, this was happening to me before I actually installed an Insider build. I don't have a machine to test this on right now, but I'm pretty sure this is unrelated to the Windows build you use.

WinUI 3 was to decouple itself from the OS to prevent these sorts of issues and incompatibilities. I am very curious to know what is causing this from a technical standpoint.

I have this problem too. No workaround, no response from VS team, where i report it as bug, because one day I updated both, Windows and VS, and don't think this should be related to Windows.

I have this problem too. No workaround, no response from VS team, where i report it as bug, because one day I updated both, Windows and VS, and don't think this should be related to Windows.

Same issue on build 21286.1000 for both Desktop and UWP apps. UWP app launches and then the debugger crashes, Desktop app doesn't even launch. The same happens with the XAML Controls Gallery app.

Same issue on build 21286.1000 for both Desktop and UWP apps. UWP app launches and then the debugger crashes, Desktop app doesn't even launch. The same happens with the XAML Controls Gallery app.

Thanks for the report. We believe this is an issue we recently fixed, and are working to confirm that.

Thanks for the report. We believe this is an issue we recently fixed, and are working to confirm that.

Thanks for the report. We believe this is an issue we recently fixed, and are working to confirm that.

Just curious, is there a workaround for those of us who are super keen to have a play with WinUI in the mean time?

Thanks for the report. We believe this is an issue we recently fixed, and are working to confirm that.

Just curious, is there a workaround for those of us who are super keen to have a play with WinUI in the mean time?

@gavinwilliams Unfortunately, the only workaround for this issue is to use an older build of Windows. And #3954 just reported a similar issue on a newer build which should contain the fix here, so we need to investigate that.

@gavinwilliams Unfortunately, the only workaround for this issue is to use an older build of Windows. And #3954 just reported a similar issue on a newer build which should contain the fix here, so we need to investigate that.

@codendone that's frustrating, more so for you guys I assume, I know quite a few Windows dev's are all running Insider builds so the feedback on WinUI 3 must be limiting.

@codendone that's frustrating, more so for you guys I assume, I know quite a few Windows dev's are all running Insider builds so the feedback on WinUI 3 must be limiting.

@gavinwilliams Yes, certainly a very unhappy situation. On the plus side, we are planning to ship a Preview 4 in early-mid Feb, which will have the fix.

@gavinwilliams Yes, certainly a very unhappy situation. On the plus side, we are planning to ship a Preview 4 in early-mid Feb, which will have the fix.

This bug has been fixed, and the fix will be available in our next release - WinUI 3 Preview 4. We're hoping to ship this preview release in early February. Thanks!

This bug has been fixed, and the fix will be available in our next release - WinUI 3 Preview 4. We're hoping to ship this preview release in early February. Thanks!

Closing as fixed. Please open a new issue if you see a similar problem in the future.


Don't run deployment workflows on forks

In particular, not on branches?
Example: https://github.com/krlmlr/duckdb-web/actions/runs/6290378241.

This is intentional, we run the build for the website to make sure it isn't broken. The actual deploy step doesn't run.
Though we can rename the job, which would stop people being confused by this

Do we need the "Setup Pages" step for forks? This has failed for me.

We can probably have it not run on forks yeah


add map support for json parser

Currently, there is no support for a schema with map[string]interface{}. This PR extends the decode method to unmarshal the map type.
It was the main reason why I opened the previous issue: #141
All tests are passing right now

@Yamashou PTAL
I closed my previous PR #141 and fixed the issue in the proper way

@zreigz Thanks!
I guess json.RawMessage type includes map. please tell me the error that you got it. I would like to understand specifically the problem you are having

@Yamashou just add the test to gqlgenc/graphqljson/graphql_test.go and it will show that the json.RawMessage doesn't support map[string]interface{}
func TestUnmarshalGraphQL_map(t *testing.T) {
	t.Parallel()
	type query struct {
		Outputs map[string]interface{}
	}
	var got query
	err := graphqljson.UnmarshalData([]byte(`{
			"outputs":{
                                 "vpc":"1",
                                 "worker_role_arn":"2"
        	}
	}`), &got)
	if err != nil {
		t.Fatal(err)
	}
	want := query{
		map[string]interface{}{
			"vpc":             "1",
			"worker_role_arn": "2",
		},
	}
	if diff := cmp.Diff(got, want); diff != "" {
		t.Error(diff)
	}
}

I have currently a schema with the map and decode method fails

@Yamashou can you make a release when you merge this PR??

https://github.com/Yamashou/gqlgenc/releases/tag/v0.11.0

https://github.com/Yamashou/gqlgenc/releases/tag/v0.11.0

thanks a lot


Snyk alert about master branch

We used Snyk and the master branch of php-imap.
Because in composer we have "dev-master": "1.0-dev", Snyk shows a Critical severity vulnerability.
How can we fix it?

Hi @HZ-labs ,
the easiest way might be to update to the latest version, as mentioned in the Snyk report - if that isn't possible, make sure to read the advisory and don't use the Attachment::save() method.
I hope this helps :)
Best regards & happy coding,

Hi, @Webklex
thank you for the answer.
That is, it is normal that for the latest dev version after 5.5.0 in composer.json used:
{
...
    "extra": {
        "branch-alias": {
            "dev-master": "1.0.x-dev"
        }
    }
}

Maybe it should be 5.5.x-dev or something with version 5?


[sram/dv] add sram_ctrl_regwen_vseq

This test is intended to test exec_regwen and ctrl_regwen as well as their related
CSRs.
ctrl_regwen related CSRs (renew_scr_key and init) are excluded from CSRs test as they
affects other CSRs.
exec_regwen and its related CSRs are tested in CSRs tests, but this exec relates to
other sram inputs (en_sram_ifetch and hw_debug_en), so also test it in this test.
Both exec_regwen and ctrl_regwen as well as their related CSRs will be programmed
at the beginning of each iteration. So when regwen is cleared, the related CSRs will be
locked.
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

The exec_regwen CSR controls the rw exec CSR, but the ctrl_regwen controls the ctrl CSR, which is wo. Is this worth mentioning in your description?

sure. I copied the detailed description of this test from testplan to this PR description. This is more clear.


I need to work with Google Colab? any get started exa;ple please?

Hey @Med-Rokaimi!
Thanks for your interest 🤓 They are a couple of ready-to-use examples in the examples/ folder

Thank you for reply.
Yes I started with them. Just as I'm working with colab, it seems the env didn't work fine with me and the required packages as well.


Add default arguments to CInterface.

A default argument allows a user to specify one or more arguments that
are passed to each function wrapped by the interface before any other
arguments are passed. A default argument is provided by passing a
function that, given a variable name, declares and initializes the
argument.

This is very useful for passing a state to every THC function. Instead of adding an invisible parameter to each call to wrap(), you only have to specify this once.


QA-5025 added function to bulk delete test users, reuse mobile workers, updated few locators and steps

Summary
added function to bulk delete test users, reuse mobile workers, updated few locators and steps
Description
added function to bulk delete test users, reuse mobile workers, updated few locators and steps
Link to Jira Ticket (if applicable)
Jira link
QA Checklist

[X] Label(s) and Assignee added
[X] PR sent for review
[ ] Documentation (if applicable) added/updated

@kiran-tripathy I tried to squash the commits but got an error. For future, I will keep this in mind. Thanks!


Prove the Authenticity of the Helm OCI repositories blog post

@souleb did excellent work^1 and integrated cosign to verify the integrity of the Helm Chart stored as OCI Artifacts, and it shipped with Flux v0.36^2. As we recently wrote a blog post about verifying the integrity of the OCI Artifacts recently^3, it is time to write the second part of it. Still, this time it will be all about verifying the integrity of the Helm Charts stored as OCI Artifacts.

_https://fluxcd.io/flux/components/source/helmcharts/#verification_

_https://github.com/fluxcd/website/commit/f4bbd2ba1d2bc62d38e22dc1a44b17eccb3490c3_

_https://twitter.com/stefanprodan/status/1585710554018037761_

_https://fluxcd.io/flux/cheatsheets/oci-artifacts/#verify-helm-charts_


Adds documentation and ABAP types for JSON versioning

Needs updates as we implement the type writer that translates ABAP types into JSON.

I struggled to do a proper merge, so please take special care to the diff.

Yes, there is only the INTF that has the new JSON format. Sooner or later the others will follow.
As we already made the decision and put a document that explains the design, for me this PR is an approximation to this decision.
I tend to merge it and consider it an incremental step.


Fix leak when closing theme editor preview tabs

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

Cherry-picked for 4.1.2.

~you mean... "FREE me from this nightmare"


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit 66d25d7:
:clock10: Pending: waiting for processors (28 builds ahead of you)
:warning: Docs Build is busy, currently there are 28 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 66d25d7:
:clock10: Full build: the average full build time is 5 min(s) 59 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit 66d25d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feature request - add custom data to TRX output

We have some automated tests we are trying to use to measure and track functional performance in a specific area. Some of what we want is already in the TRX file, e.g. "Duration". It would be helpful if we could add additional properties, so we are not trying to parse the StdOut of the TRX.
One mechanism I could imagine is to extend the TestContext to have an additional Dictionary<K,V>, say ResultProperties, which would be included in the TRX. We are considering a custom TFS Dashboard widget to extract and display this information.

This is properly a duplicate of https://github.com/Microsoft/vstest/issues/98#issuecomment-410389571
There's already a way to do this with [TestProperty] but there's a limitation in the TRX that it doesn't actually write this out into it.

@dotMorten Would programmatically added/set properties, e.g. TestContext.Properties.Add("somekey","somevalue") then show up in the TRX file ? As opposed to the static attribute ? If so, then that would work just fine for our needs.

@robdalsanto No those properties are for the test case, not for the test result.
I don't really see a good place in the xml schema under TestResult where this would fit. You can browse through it yourself - perhaps I missed a spot. You'll find it here (or equivalent):
c:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Xml\Schemas\vstst.xsd
Look for the TestResultType definition.

@dotMorten Thanks. I did have a browse through the TestResultType, and you're right. Other than putting something into StdOut via TestContext.WriteLine(), there isn't a natural home. I've updated the title.

I think your best bet right now is to use the result files.


Fixed handleOperatorClick chip

Signed-off-by: dhruv0000<EMAIL_ADDRESS>Description
This PR fixes #3139
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

Heads up: there are integration tests failing

@dhruv0000 ref: https://github.com/layer5io/meshery/pull/3147

Looks like CodeCov might have a misconfiguration. What do you think, @ramrodo?

Looks like CodeCov might have a misconfiguration. What do you think, @ramrodo?

I think it was because it was changed the version of the CodeCov Github Action and something changed in this one. It was necessary to update the version?

Oh, I'm not sure. I don't recall updating the CodeCov version.

@ramrodo The same error still persisted in the v1. There were some open issues about this in their repo, some suggesting to update the version to fix it. I was just giving it a go. Turned out, the error is still persistent.