[Snyk] Security upgrade pillow from 9.5.0 to 10.0.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

Vulnerabilities that will be fixed
By pinning:

Severity
Issue
Upgrade
Breaking Change
Exploit Maturity

Heap-based Buffer Overflow SNYK-PYTHON-PILLOW-5918878
pillow:  9.5.0 -> 10.0.1
No
Mature

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

streamlit 1.27.0 depends on pillow<10 and >=7.1.0


upgrade go makefile maker, run

atttempting to sort out issues, since they are in the pipeline need to push.
Upgraded my local go-makefile-maker in this process as well, so we'll see if we get the same errors, or new ones.

coverage: 58.917%. remained the same
when pulling 53d2e57ded2a400bde99e60b1cb33b45e54461c0 on codeql
into ec98d9b5d4a6fd457b598fd01ce90bf40c47effd on master.

hrm, still failing. need to find the correct failure. This is obviously to do with the fact we use generated code. There's a todo to replace that, perhaps my energy would be better focused in accomplishing that. unsure.

Okay, adding make generate to the action file worked. it still fails due to a different issue I need to fix, but that's fine.
Okay, is it possible to add commands to go-makefile-maker within the actions file? Reading docs.

golangciLint:
createConfig: true
errcheckExcludes:
- io/ioutil.ReadFile
- io.Copy(*bytes.Buffer)
- io.Copy(os.Stdout)
- (net/http.Client).Do
skipDirs:
- easypg/migrate/
Is an option. I'd prefer we just generate the code though, looking into other options.

the thing is, the manual edit of the action will fix it... but it will be overwritten the next time go-makefile-maker is run...
so next week I'll loop others in and see what either silly error i'm making, or what feature we need in go-makefile-maker to support this.
or... change the way that it does generated files...


Having tests in a separate repo

Hi @rtheunissen.
I've forked and cloned both the ployfill and tests repositories and looking to start the implementation.
If we are to support php5.6 then we need to remove scalar type hinting and return type declarations. Doing this has highlighted to me a problem with having the tests in a separate repo.
For me to work on the polyfill and also run the tests I've done the following:

Cloned the polyfill
Autoload the tests using composer autoload-dev
Created a new phpunit.xml file in the polyfill that uses composer/autoload.php as the bootstrap.

At this stage I can run tests (albeit failing).
But to work on the tests I need to use my fork of the tests repo. After running composer, I removed the contents of ./vendor/php-ds/tests and symlinked my fork of the test repo to that location.
Now I can update tests as I modify the polyfill but this process is terrible.
When it then comes to creating a pull request I'd need to create requests for both the tests and polyfill. Then the CI will need a way to combine the repos together correctly to confirm the code is sound and the merge can be accepted.
I can't see how that this can work in a way that people will be able to contribute without having the tests committed directly in the polyfill.
What are your thoughts?

If we are to support php5.6 then we need to remove scalar type hinting and return type declarations.

That may have been my biggest amateur moment in history. Won't be supporting 5.6 because of that, so we can just focus on >=7.0

When it then comes to creating a pull request I'd need to create requests for both the tests and polyfill.

The theory is that you shouldn't need to update any tests. If a test is broken or added, it should be a patch version on the tests repo. The difficult part is how to check that changes to the tests are correct without breaking the master builds of the extension and the polyfill. One solution would be to set up CI for the tests to pull in both the polyfill and the extension at the equivalent minor level, and check that everything passes.

For me to work on the polyfill and also run the tests I've done the following:

Cloned the polyfill
Autoload the tests using composer autoload-dev
Created a new phpunit.xml file in the polyfill that uses composer/autoload.php as the bootstrap.

This is no longer necessary. All you need to do is:
composer install
composer run-script test

No need for the extra phpunit.xml either. :)
However, if you want to (or have to) work on the tests at the same time, I think the symlink approach is the only solution.


Update URL and endpoint in DataBC geocoder

Note that this is a breaking change for people trying to use plain http at DataBC, however that should already be broken for them (at least it was for me)
Per DataBC documentation, the URL used in geopy was deprecated in 2018 and should have been shut down in December 2020:
December 1, 2020
The following URLs were deprecated on Sep. 1, 2018 and are now shut down:

http://apps.gov.bc.ca/pub/geocoder
https://apps.gov.bc.ca/pub/geocoder
This URL should now be used, with or without an API key: https://geocoder.api.gov.bc.ca

These endpoints have apparently continued to silently work, until August 22, 2023, when DataBC has started bouncing plain http requests at the old URL/endpoint.
This change updates the URL, and raises ConfigurationError if the DataBC geocoder is initialized with scheme='http'.

Thank you!
It appears that they have (perhaps temporarily) rolled back support for the old domain, as it is currently working for me.
I merged your change without the scheme check, because http seems to work even with the new domain. It's still a redirection to https, but at least it's not a breaking change anymore.


Godot 4 crashes when loading project with anything other than Compatibility settings.

Godot version
4.0-stable
System information
Fedora 36,
Issue description
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.stable.official (92bee43adba8d2401ef40e2480e53087bcb1eaf1)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib64/libc.so.6(+0x3ea30) [0x7fbfda23ea30] (??:0)
[2] /usr/lib64/libvulkan_radeon.so(+0x1483e7) [0x7fbfc49483e7] (??:0)
[3] /usr/lib64/libvulkan_radeon.so(+0x123589) [0x7fbfc4923589] (??:0)
[4] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x1b042ca] (??:0)
[5] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x1abe45e] (??:0)
[6] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x3b5e932] (??:0)
[7] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0xec1616] (??:0)
[8] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x1ec3b73] (??:0)
[9] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x1c271af] (??:0)
[10] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x1c2c242] (??:0)
[11] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x1c2dd85] (??:0)
[12] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x4568594] (??:0)
[13] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x2b9a3ee] (??:0)
[14] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0x2bd12a1] (??:0)
[15] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0xec07db] (??:0)
[16] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0xe027f3] (??:0)
[17] /lib64/libc.so.6(+0x29510) [0x7fbfda229510] (??:0)
[18] /lib64/libc.so.6(__libc_start_main+0x89) [0x7fbfda2295c9] (??:0)
[19] /home/sean/Desktop/gamedev/Godot4/Godot_v4.0-stable_linux.x86_64() [0xe2286e] (??:0)
-- END OF BACKTRACE --
================================================================

Upon loading a project with Forward+ or Mobile settings, I see this followed by the engine crashing to the previous log. I suspect it is a driver related issue but updating my drivers hasn't fixed it on multiple attempts throughout the Beta and RC stage, I do apologise for not reporting it sooner.
Vulkan works great on my GPU except for a few particular things, and Godot seems to be one of them.
PC specs: 8-core Ryzen 5 3550H with Vega graphics
Steps to reproduce
Setting any project to forward+ or mobile causes this. Compatibility works fine, but has no shading, of course.
Minimal reproduction project
N/A doesn't make a difference

The crash is in your graphics driver. Try upgrading to Fedora 37 so you get a newer Mesa version.


[prometheus-operator] deprecate chart

Signed-off-by: Naseem<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/hold
For this one, let's wait until https://github.com/prometheus-community/helm-charts/pull/1 is complete. Tomorrow most likely 🙂

/retest

@naseemkullah I had already forgotten about this PR in the 15 years that passed since you opened it 😂  I'll close it now in favor of https://github.com/helm/charts/pull/23738 since it's already in e2e/tide process.


D41

You say D41 was not brought out.  What is D41, I can't find that pin anyway?

D41 refers to the Teensy pin marked as just 41 in the official pinout https://www.pjrc.com/teensy/pinout.html

Thanks.  Why did you leave it out of your design?

Lack of space 😉


Authorize with your biometrics

Hey
I can't log in on my Yoroi wallet on iphone 6s..
/the screen includes Authorize with your biometrics and use other login method which i can't click them too
also i don't find my recovery words and that's really important to me log in with my phone .. Please any way to solve that ?

HI, @itsemilano ! Can you plz try disabling biometrics in iOS settings completely, restarting the phone, and trying to open Yoroi again? The "other login method" should be working

@itsemilano , we have got confirmation from QA on what is causing this problem and will be working on improving the UI for this. This happens when you don't have any authentication method configured in your system at all, no pin-code, no face-id, no biometrics. You can resolve the problem by closing Yoroi, enabling at least one of the methods, and then opening Yoroi again

I did that.. I disabled my biometrics but doesn't work also my touch_id doesn't work .. I just wanna log in with the pin code like before .. Can it be solved ? Also as i found my recovery words of wallet it includes 12 words for Cardano(Ada) but in chrome it includes 15 words.

@itsemilano What pin code do you mean the iPhone pin code or the app pin code?

The app pin code i mean, my touch_id doesn't work and App only accepts authorize with biometrics at the moment

@itsemilano Could you please set a passcode for your iPhone?

I did the PassCode already

@vsubhuman I can confirm this happens on a phone with system passcode and Face Id enabled. I was using Yoroid authenticating with Face Id for months. Now I just see the "Authorize with your biometrics" screen.
 Please turn it on"
If the fix is to completely disable biometrics in the phone, I think I'll pass 😉

I just installed Yoroi and see the same thing.  I had pincode and touch Id enabled on the phone prior to installing Yoroi. Went through the "restore wallet" process, now it's stuck on the screen that says "authorize your biometrics" and the "use other login method" does nothing.
I've tried rebooting the phone but no difference.

This is now being investigated top priority

@itsemilano Could tell the iOS on the device, please?

@NachoCM Could tell the iOS version on the device, please?

@lgarvey Could you tell the iOS version on the device, please?

14.6 (18F72)

@Nebyt 15.2 (19C57)

Just updated to 15.2 (19C56) and it's still broken

So is there any way to log in with only  pin code ? The problem is that if I remove the app I’ll lost my ADAs.. also I just have 12 recovery words not 15 on chrome.. please if there is any solution let me know .. I really need help from the app’s developers

@NachoCM Could you tell the iOS version on the device, please?

15.2

@itsemilano Could you tell the iOS version on the device, please?

15.2

@itsemilano If you have a 12-word recovery phrase it probably means you have an Ergo wallet. Please, open the Yoroi browser extension, select Restore, scroll down, select Ergo, and there select the "Enter a 12-word recovery phrase".

@itsemilano If you have a 12-word recovery phrase it probably means you have an Ergo wallet. Please, open the Yoroi browser extension, select Restore, scroll down, select Ergo, and there select the "Enter a 12-word recovery phrase".

Actually I’ve done and it was successful but my account balance is 0 because I’ve had only Cardano(Ada) and not any other coins.. I can show you the screens to be assure

@vsubhuman @Nebyt I'm having this same issue on my iPhone 13 Pro with iOS 15.2 and Yoroi Wallet version 4.5.2. Same situation, turning on/off biometrics does not do anything, still stuck on a screen that says "Authorize with your biometrics" "Welcome back" and a button at the bottom that says "USE OTHER LOGIN METHOD" that does not work at all...
Hoping somebody is able to find a fix for this soon.

Same Problem
iPhone 6S Plus
Yoroi says Authorize with your Biometrics, Welcome Back and a Button at the Bottom that says use other login method that does nothing there is also a an arrow that points back to where the wallet is supposed to be and it also doesn’t work.
How can this happen? What can we do?

There seems to be an unexpected incompatibility of some old code that always worked for us with no issues and some new OS updates, also seems to be only on some specific devices and/or system settings. We are working on fix at the moment which at least will unblock using the fallback pin-code method, in case biometrics fail for some reason. Then it should be easier for us to gather information and see what exactly is causing problems with the biometry itself

@Rigocola Could you remember please some additional details before the problem appeared? Maybe some biometrics changes or something else

Nothing is different
I had my Fingerprint set up with touch ID. I’ve always had it set up like that
Now it’s not working
Sent from my iPhone
On Dec 23, 2021, at 7:08 AM, Denis Nebytov @.***> wrote:

@Rigocolahttps://github.com/Rigocola Could you remember please some additional details before the problem appeared? Maybe some biometrics changes or something else
—
Reply to this email directly, view it on GitHubhttps://github.com/Emurgo/yoroi-mobile/issues/1841#issuecomment-1000364397, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXAZFLT3HPGOLMAM6YRLQQLUSM3PRANCNFSM5KKT6YXQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

@Rigocola Did you update the app? And what version of the app?

Yes
Last One was 3 Days Ago
Version 4.5.2
I always update the app
Sent from my iPhone
On Dec 23, 2021, at 9:14 AM, Denis Nebytov @.***> wrote:

@Rigocolahttps://github.com/Rigocola Did you update the app? And what version of the app?
—
Reply to this email directly, view it on GitHubhttps://github.com/Emurgo/yoroi-mobile/issues/1841#issuecomment-1000432856, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXAZFLXDPN632H7PDPCMHBLUSNKHNANCNFSM5KKT6YXQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

Ok, I had the same problem (iOS 15.2, iPhone 13 Pro) - Blue screen 'Authorize with your biometrics' with a button 'use other login method' on the bottom and back arrow on the top left, both not working.
I guess that I hadn't started the app since migrating to the new device, as there was no 'Face ID' option in the Yoroi section in iOS Settings.
Using iMazing, I extracted the data, modified the manifest.json file (specifically, changed acceptedTos to false) and re-installed Yoroi with the modified data using iMazing. This seemed to give the app enough time to ask for the permission to use Face ID and get in again.
Somehow, I seemed to have lost the recovery words for the Shelley wallet (my last recovery words were for the Byron wallet). As I could not find a an option in Yoroi to get the recovery words, I decided to move everything out of Yoroi and no longer use this wallet, but maybe my solution could help others.

@vsubhuman can we hope for the next update log in with the pin code ?
honestly I really need to access my ADAs :)
I believe you’re doing your Best anyway

I have problem with biometrics as well. And I have lost my seed phrase by mistake so there is no way to reinstall the app. Really frustrated these days. Hope to hear some good news from Yoroi team soon.
Happy holiday! And I wish you all the best and good success for 2022.

Version 4.5.3 is being released for iOS at the moment. Please check if the biometrics or at least the backup method will become usable for you after you update

I have checked app store but its still 4.5.2 version not 4.5.3
I’ll check again tomorrow (its midnight here) and let you know. Thank you for your help!

I have checked app store but its still 4.5.2 version not 4.5.3 I’ll check again tomorrow (its midnight here) and let you know. Thank you for your help!

App is still going through the review process. Apple app store might take time between the app is released and when it's available to the users.

I have same problem. iPhone 13 pro max, latest iSO, updated yoroi wallet 4.5.3 can't get in ... I tried all the things already mentioned ....

Yes, I have the same problem :(

@ikkyusojuna @ImGracePham Does any alert message appear after launching the app?

@Nebyt when we click on use other login method, the error is: “Action failed, undefined: credentials not found”
And when we click on try again, the error is: “Biometrics was turned off”

I does nothing..

@vsubhuman I can confirm this happens on a phone with system passcode and Face Id enabled. I was using Yoroid authenticating with Face Id for months. Now I just see the "Authorize with your biometrics" screen.
 Please turn it on"
If the fix is to completely disable biometrics in the phone, I think I'll pass 😉

This is exactly what happened to me. Moved from iPhone SE (2nd gen) to iPhone 13 Mini. Tried to open app, got the blue screen quoted by others.  Instead of being patient, I just deleted Yoroi mobile and reinstalled, thinking I could restore with my seed phrase.....only that didn't work either. I got a completely different address and no ADA or tokens.

@vsubhuman I can confirm this happens on a phone with system passcode and Face Id enabled. I was using Yoroid authenticating with Face Id for months. Now I just see the "Authorize with your biometrics" screen.
 Please turn it on"
If the fix is to completely disable biometrics in the phone, I think I'll pass 😉

This is exactly what happened to me. Moved from iPhone SE (2nd gen) to iPhone 13 Mini. Tried to open app, got the blue screen quoted by others. Instead of being patient, I just deleted Yoroi mobile and reinstalled, thinking I could restore with my seed phrase.....only that didn't work either. I got a completely different address and no ADA or tokens.

Seed phrase did't work? wow that is strange ..... I will wait than

Using iMazing, I extracted the data, modified the manifest.json file (specifically, changed acceptedTos to false) and re-installed Yoroi with the modified data using iMazing. This seemed to give the app enough time to ask for the permission to use Face ID and get in again.

I'm trying this now, after restoring my phone to an earlier backup (from before migration to new phone).

I'm also seeing the "undefined: credentials not found" error.

I'm also seeing the "undefined: credentials not found" error.

any news on update?

any news on update?

Still under investigation (many staff members are off due to the holidays), important to note that when you backup your phone Apple doesn't include your keychain data into it. https://support.apple.com/en-us/HT203783. Therefore if by any reason the keychain sync was off when migrating phones, restoring backup or even changing the apple user, your app data will be there after restoring, but your keychain will be gone.

any news on update?

Still under investigation (many staff members are off due to the holidays), important to note that when you backup your phone Apple doesn't include your keychain data into it. https://support.apple.com/en-us/HT203783. Therefore if by any reason the keychain sync was off when migrating phones, restoring backup or even changing the apple user, your app data will be there after restoring, but your keychain will be gone.

so can I restore from seed?

Latest investigation shows at least part of the issues are related to this bug in react-native-keychain itself - https://github.com/oblador/react-native-keychain/pull/428
New version 4.5.4 is being released at the moment that should fix this issue for any user for whom the main storage is still available so the keychain can be re-activated.
But it also seems that for some users the problem might be in the app not being able to access the storage at all, in which case there's not much that can be done, apart from the user having to restore all wallets from their secret words. We are still actively investigating these particular cases and checking if it might be related to iOS 15 only.
So far all users are advised to wait for the version 4.5.4 to see if this will resolve the problem. If not - in case when the secret words are available - unfortunately it is much easier to reinstall the app and restore wallets from the words, which seems to be resolving the issue completely (effects of iOS 15 are still being investigated).

Actually I tried the version 4.5.4 but that problem again and can’t reinstall the app honestly because of my ADAs .. it’s really painful for me
Anyway can we hopeful for the next updates ?
Just an idea, isn’t better to inform us about the related codes and bugs exactly.. we can share it to other experienced for contributing

@itsemilano What is the message on the "Try again" or use "Use other login method"?

Related 3rd party issue: https://github.com/oblador/react-native-keychain/issues/509

We will be releasing a version that will allow users to set the PIN at startup when opening the app after disabling the biometrics on the phone that previously was set to authenticate with biometrics. Therefore, if the phone's local data is still consistent, it will resume back to normal after opening the wallet. Still, important to note that iOS 15 does have issues with app data. Many people are still reporting it. So please, always write down and back up the wallet mnemonic. We also encourage those who lost the mnemonic but still have access to the wallet to create a new wallet, write down and back up the new wallet mnemonic, only then, transfer the funds to the new wallet.

Hi all, just giving an update regarding update 4.5.4. I was getting unknown errors before and lost my phrases to my wallet. I am happy to report the new update resolved my issue and faceID worked and I was able to access my wallet!! Thanks so much for the Dev trams hard work.

@itsemilano What is the message on the "Try again" or use "Use other login method"?

The message for use other login method is the above I sent the screenshot and message for try again is “Biometrics was turned off, it seems that you turned off biometrics , please turn it on”.

I have updated 4.5.4 version and it works well.
I do appreciate your hardworking. Wish you all the best
Ps: I”ll take it as a lesson and be more careful with my seed phrases.

I acutely had my issue resolved from the most recent update.
Appreciate your help!

On Jan 11, 2022, at 12:49 AM, Emilano @.***> wrote:

@itsemilano What is the message on the "Try again" or use "Use other login method"?
The message for use other login method is the above I sent the screenshot and message for try again is “Biometrics was turned off, it seems that you turned off biometrics , please turn it on”.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.

Guys for my phone that Touch ID doesn’t work and facing the issues yet do you have any suggestion ? Is there anyway to restore my ADAs ?

Hi @itsemilano! We have been working on a solution and we hope it will help you.

@itsemilano Please check out the latest version (4.6.0).

@itsemilano Please check out the latest version (4.6.0).

I checked the Latest version of App and it working well on my Phone :) Really Thanks and appreciate your Great Support.


Feature request: Fail fast if -Dagent.package.python.agent.url points to a non-existent path

Current behavior just causes an error and infinite loop in the rancher-agent container

Can you give a bit more context, maybe a specific example?

Just updated the title.  Sorry.  Just realized the original title was confusing.

Ah yes, that is a good idra

Closed in favor of rancher/rancher#3859


Replace EarlyDataSendCallback with SslEarlyDataReadyEvent

Motivation:
Let's use use an user-event to signal that the user might be able to send early data. This is more consistent with what we usually do in netty.
Modifications:
Replace EarlyDataSendCallback with SslEarlyDataReadyEvent
Result:
More consistent API

/cc @lostk1ng

Let me just merge this one to make progress.... @violetagg @lostk1ng please provide feedback once you have time. We can do a followup if needed.

LGTM

LGTM. That's more suitable for netty's coding style.


Make the atpanic exception return more usable data

Right now all you can get from the LuaError exception is a string.

How to handle this exception? Even if I use catch(...) my program crashes with stack traceback: in console. (catch(std::exception) also doesn't work)

You should be able to catch it like this:

	try
	{
		auto metatable = table.GetMetaTable();
	}
	catch(LuaError e)
	{
		std::cout << e.GetMessage() << std::endl;
		return e.GetMessage() != "Error: failed to get metatable\n";
	}

It however could be a case I did not cover. Do you mind sharing some code, or the error message that reproduces it?

Lua lua;

try {
    auto asd = lua.GetGlobalEnvironment().Get<LuaTable>("asd");
}
catch (LuaError e) {
    std::cout << e.GetMessage() << "\n";
}

After running this code I get this in console:

And the error Unhandled exception in adress 0x... (ucrtbase.dll)
The next statement is going to be executed is 143 row in luatypetemplates.h

Are you using the source at 1.3? Before 1.3 there was no such exception thrown when at_panic was captured.


Add support for component a11y statuses for website

### Tasks
- [x] Update a11y report in release workflow
- [ ] ~Add for each component on site~ Will open separate issue for this
- [ ] ~Add status overview page~ Will open separate issue for this as well

List of initial pages with accessibility status pages:

AboutModal
ExpressiveCard
ProductiveCard
DataSpreadsheet
FullPageErrors
APIKeyModal
OptionsTile
PageHeader
Saving
SidePanel
TagOverflow
Tearsheet
Toolbar
UserAvatar


Fixed transpile-node being broken on non-apps

swig-spec automatically runs the transpilation process, if required, and the check was
assuming that we would only run it on "apps", hence it was broken for "modules".
This PR fixes this issue.
Relates to: https://github.com/gilt/gilt-swig-assets/pull/52

@RoryH lol, I used "edit on github" thing, could only change that file, argh!


can we use Their own compose to listDialog item view？

I do not see much sense in doing so. If you want to have a list with custom item views, you could just use CoreDialog / InfoDialog and display your own list-item views in the content section. On the other hand, it wouldn't be difficult to allow that. Can you tell me a bit more about your use-case?

I understand and feel the same, especially more configuration options for developers. But I still want to understand your use case. You want to have load dynamic images with coil. The current icon has a size of 24dp. What's the intended size for the image?

24dp totally enough

I will plan that for a later version beginning January 2023 as I'm soon in holidays.

I decided against doing this as I do not think it's a common use case. I recommend you to fork the project and add this functionality. Sorry!


Missing settings-menu

Atom 1.15.0 x64 on Mac
elmjutsu 5.5.1

Hi @eirikm, I think that is an Atom bug.
You can try to do the following:

Uninstall elmjutsu.
Exit Atom.
Start Atom.
Reinstall elmjutsu.
Exit Atom.
Start Atom.

I rebuilt the package and now it works.
Thought I should document the process, but now I can't reproduce the error :-/
thanks!

It happens from time to time, even with other packages :-)  You can also try the same workaround if you encounter issues after updating a package.

Hi, I had the same problem (under Atom 1.20.1 and 1.21.0-beta, elmjutsu 6.0.0) and with the help of this page + the Atom debugging docs I finally got it. :)
Here's the recipe that worked for me (there's nothing new here, but the sequence might help some other confused person who finds this page).

Is there red bug icon in the bottom right of any Atom window? This is the incompatible package indicator. Click on it.

Select "Rebuild packages" (ahhh...)

Go the Packages section of Atom's settings and uninstall elmjutsu.

Restart Atom.

Reinstall elmjutsu.

It's easy once you know how! ;D


chore(ci): adjust pr results job

Thanks for the PR!
Deployments, as required, will be available below:

Frontend
Backend

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

Annotations are too limited.  Dropping this attempt.


HIVE-26933: Cleanup dump directory for eventId which was failed in previous dump cycle

Problem:

If Incremental Dump operation failes while dumping any event id in the staging directory. Then dump directory for this event id along with file _dumpmetadata still exists in the dump location. which is getting stored in _events_dump file
When user triggers dump operation for this policy again, It again resumes dumping from failed event id, and tries to dump it again but as that event id directory already created in previous cycle, it fails with the exception Solution:
fixed cleanFailedEventDirIfExists to remove folder for failed event id for a selected database

+1. LGTM.


Automatically scrape every once in a while to keep website up to date

if the scraper is robust enough, this can be achieved with github actions: https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule
Not sure how difficult this is in practice.


eiciel: init at <IP_ADDRESS>

Description of changes

Eiciel is a viewer/editor for ACLs and xattrs. It integrates with Nautilus, but also works standalone. https://rofi.roger-ferrer.org/eiciel/
I don't know if the Nautilus integration works; I installed eiciel and nautilus with nix-env and it doesn't seem to work, I don't know if that's because I packaged it wrong or if it's because I would have to install them both system-wide. I copied the method from https://github.com/NixOS/nixpkgs/blob/66be55b715edbc42f879b4bcccafe86d7f6bff10/pkgs/applications/networking/dropbox/cli.nix.
The "help" button doesn't seem to do anything, I don't know why that is – https://github.com/rofirrim/eiciel/commit/96fbd782cdfa4c47d7f6b91789e92a62614f7e6b looks relevant, and isn't included in a release yet, but building from that doesn't seem to fix it, so maybe I don't have some help viewer installed on my system.
Closes #165947
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 165970 run on x86_64-linux 1

1 package built:

eiciel


Create a "advice for spec authors" page

Do we need a special "advice for spec authors" page that calls out current best practice for spec authors (e.g. the security and privacy checklist, promises guide, etc...)?

https://w3ctag.github.io/design-principles/ could morph into this or we could leave that more narrowly focused on API surface and link to it from this

I think the design principles doc would be top of the list on this page but I see the page as more of a list of links - some of which might be to TAG or other w3c docs and some of which might be to other best practice stuff...

I've started keeping state at:
https://github.com/w3ctag/wiki/wiki/TAG-Guidance-for-Spec-Authors
Please add links, etc. and then we'll fill out some prose around them.

I think this can be closed; we're keeping this currently at http://w3ctag.github.io/workmode/


Added util.py, includes source directory import and TestWrapper class.

This PR moves the TestWrapper class from the bitcoin core source directory to the taproot-workhop repository. The bitcoin source directory path import has also been consolidated here.
Users now can do this:

Edit source directory in util.py
Run import util
Run test = util.TestWrapper()

This PR requires the refactor of main in BitcoinTestFramework is merged into the bitcoin/optech-taproot branch. The refactor spilts out setup and shutdown from main so these methods are available to child classes, such as TestWrapper. This has been merged in optech-taproot-develop and tagged v0.1.
TODO's:

[ ] Implement singleton pattern during startup to ensure not other bitcoind processes are running, with a cross-platform compatible-way of acquiring PIDs.

@jnewbery I am unsure of how best to implement the singleton pattern and detect other bitcoind instances. pidof isn't necessarily installed on OSX. Windows requires a different utility. psutil is cross-platform but requires a package install. If no obvious solutions, I suggest to hold off on this for now, since startup of a TestWrapper already fails if another instance already running.
I would like to clarify how to move forward on this TestWrapper, since all other notebook pages depend on this PR.

I'm going to merge this now. We can do a few tidy-ups to this later, but it's important we get this in so that the individual notebooks can be built on top of it.


Microsoft.App managedEnvironments cannot be deployed

Please provide us with the following information:

This issue is a: (mark with an x)

[x ] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
I'm trying to add storage to container environment via Terraform using this guide:
https://learn.microsoft.com/en-us/azure/templates/microsoft.app/2022-03-01/managedenvironments/storages?pivots=deployment-language-terraform
Steps to reproduct

Apply Terraform and receive error

My code is
`resource "azapi_resource" "containerapp_environment" {
type      = "Microsoft.App/managedEnvironments@2022-03-01"
name      = "${var.aca_name}acae"
parent_id = azurerm_resource_group.rg.id
location  = azurerm_resource_group.rg.location
body = jsonencode({
properties = {
appLogsConfiguration = {
destination = "log-analytics"
logAnalyticsConfiguration = {
customerId = azurerm_log_analytics_workspace.loganalytics.workspace_id
sharedKey  = azurerm_log_analytics_workspace.loganalytics.primary_shared_key
}
}
vnetConfiguration = {
internal               = true
infrastructureSubnetId = azurerm_subnet.aca_subnet.id
dockerBridgeCidr       = "<IP_ADDRESS>/16"
platformReservedCidr   = "<IP_ADDRESS>/16"
platformReservedDnsIP  = "<IP_ADDRESS>"
}
}
})
depends_on = [
azurerm_virtual_network.virtual_network, azurerm_storage_account.aci_storage
]
ignore_missing_property = true
ignore_casing = true
schema_validation_enabled = false
}
resource "azapi_resource" "symbolicname" {
type = "Microsoft.App/managedEnvironments/storages@2022-03-01"
name = "string"
parent_id = azapi_resource.containerapp_environment.id
body = jsonencode({
properties = {
azureFile = {
accountKey = data.azurerm_storage_account.aci_storage.primary_access_key
accountName = azurerm_storage_account.aci_storage.name
shareName = azurerm_storage_share.container_share.name
}
}
})
}`
Expected behavior [What you expected to happen.]
Container environment along wit storage can be deployed using Terraform
Actual behavior [What actually happened.]
Error message is :
`Error: creating/updating "Resource: (ResourceId "/subscriptions/10071b3d-8531-45e2-bc9c-699f6331a09b/resourceGroups/testneww-rg/providers/Microsoft.App/managedEnvironments/testnewwacae" / Api Version "2022-03-01")": GET https://management.azure.com/subscriptions/10071b3d-8531-45e2-bc9c-699f6331a09b/providers/Microsoft.App/locations/uksouth/managedEnvironmentOperationStatuses/46749e98-0fcb-4cc2-b599-0e5e1db7518d
│ --------------------------------------------------------------------------------
│ RESPONSE 200: 200 OK
│ ERROR CODE: OperationFailed
│ --------------------------------------------------------------------------------
│ {
│   "id": "/subscriptions/10071b3d-8531-45e2-bc9c-699f6331a09b/providers/Microsoft.App/locations/uksouth/managedEnvironmentOperationStatuses/46749e98-0fcb-4cc2-b599-0e5e1db7518d",
│   "name": "46749e98-0fcb-4cc2-b599-0e5e1db7518d",
│   "status": "Failed",
│   "error": {
│     "code": "OperationFailed",
│     "message": "ErrorCode: ManagedEnvironmentResourceDisallowedByPolicy, Message: Fail to create managed environment because creation of required resources was disallowed by policy, refer to https://go.microsoft.com/fwlink/?linkid=2198255 for more detail."
│   },
│   "startTime": "2022-09-29T13:41:56.8910411"
│ }
│ --------------------------------------------------------------------------------
│
│

Hi, Do you have a policy in your subscription that prevents creation of resource groups? Since you are using your own VNET, we will try to create a MC_ resource group in your sub and that seems to be blocked.
https://learn.microsoft.com/en-us/azure/container-apps/networking#managed-resources


Removing value and risk as focus areas for this wg

Now that we have wg-risk and wg-value, it seems reasonable to remove the corresponding focus areas from this wg, and let them make them evolve.

Risk and value are new working groups and we agreed to merge this yesterday.


feat(player): allow player to exist on all pages

Big WIP since I need to rewrite alot of the player, but that's probably a good thing since it's gotten a bit messy.
Also taking the time to make the web player much more reactive and nice.
Also redoing the native subtitle logic because its so confusing at the moment.

I want to finish this but it's such a big refactor and writing it in a good way is hard.


Enable embedded journal in single master local alluxio cluster

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3029/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3033/
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3047/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3048/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3051/
Test FAILed.

@aaudiber Yeah, the PROCESS_TYPE is a little annoying in the test,
We mainly use it when we need to build the raft journal system or format it.
The main place we use is in the JournalSystem.build(), are we able to get rid of it?

@LuQQiu Can we pass the ServiceType to the builder?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3061/
Test FAILed.

@LuQQiu could we pass ServiceType instead of ProcessType?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3064/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3065/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3082/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3083/
Test PASSed.

@aaudiber Addressed the comments, PTAL, thanks!

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3094/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3101/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3102/
Test PASSed.

@aaudiber Since the local Alluxio cluster change the global configuration and added the configuration rule to all the tests using local alluxio cluster is complicated, I added back the surefire property alluxio.test.journal.type. PTAL, thanks!

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3106/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3107/
Test PASSed.

@LuQQiu I'm still trying to understand why we need a separate journal property outside ServerConfiguration. Can you give an example of where we need to call setJournalType instead of setting the journal type configuraiton property?

@aaudiber
Suppose we only have one Property key: MASTER_JOURNAL_TYPE to control the global test journal type. All the tests that support both embedded journal and UFS journal should use the journal type defined by MASTER_JOURNAL_TYPE.
(1) It works well in MultiProcessCluster since the value of MASTER_JOURNAL_TYPE will never be changed.
For example,  Even if MASTER_JOURNAL_TYPE=EMBEDDED, JournalBackupIntegrationTest.backupRestoreZk() test still use a MultiProcessCluster with Zookeeper. Instead of changing the global configuration MASTER_JOURNAL_TYPE to UFS, we store process level properties in a map and passing them to each jvm process by -Dkey=value.
(2) However, in multi-thread cluster -> the LocalAlluxioCluster, we do not have a separate environment allow us to set thread level configuration.
If all the tests can support both embedded journal and ufs journal, it will be easy, we can directly set once the MASTER_JOURNAL_TYPE before tests and never modify this value. However, some tests target embedded journal or ufs journal. For example, the JournalToolTest.java and SecondaryMasterTest can only use UFS journal and they need to set the global configuration MASTER_JOURNAL_TYPE=UFS when initializing the LocalAlluxioClusster configuration. The MASTER_JOURNAL_TYPE will be changed in this case.
That's why I want another property key that is write-once and never be modified.

@LuQQiu Even in LocalAlluxioCluster, tests are run one at a time, not concurrently, so each test sets its own configuration independent from other tests. The environment is controlled by setting the global configuration at the start, then launching the cluster. As far as I can tell, we never need to change the journal type in the middle of a test.
What if we change from calling
  new LocalAlluxioClusterResource.Builder()
  // ...
  .setJournalType(JournalType.UFS)

to
  new LocalAlluxioClusterResource.Builder()
  // ...
  .setProperty(PropertyKey.MASTER_JOURNAL_TYPE, "UFS")

@aaudiber Thanks for the advice! I agreed that we do not need the setJournalType in LocalAlluxioClusterResource.Builder. Will remove this part later.
In LocalAlluxioClusterResource.start we still need to override the MASTER_JOURNAL_TYPE IN ServerConfiguration. So I still think it will be safer to have another global test journal type.
// Init configuration for integration test
    mLocalAlluxioCluster.initConfiguration();
    // Overwrite the test configuration with test specific parameters
    for (Entry<PropertyKey, String> entry : mConfiguration.entrySet()) {
      ServerConfiguration.set(entry.getKey(), entry.getValue());
    }

@LuQQiu why do we need to override MASTER_JOURNAL_TYPE in ServerConfiguration? If we want a test to use the default journal type (may be overridden by passing system property -Dalluxio.master.journal.type), we don't need to do anything because the configuration will automatically pick up the system property. For tests that should always use a specific journal type, they can set that type with
 new LocalAlluxioClusterResource.Builder()
  // ...
  .setProperty(PropertyKey.MASTER_JOURNAL_TYPE, "UFS")

which will override the default journal type in LocalAlluxioClusterResource.start.
My concern with adding a second way to set the journal type is that it could be confusing which journal configuration should be respected, and it adds unnecessary complexity.

@aaudiber
Still confusing.
(1) Situation one:
our default alluxio.master.journal.type=EMBEDDED.
The first several tests using LocalAlluxioCluster work as expected.
Then a test
 new LocalAlluxioClusterResource.Builder()
  // ...
  .setProperty(PropertyKey.MASTER_JOURNAL_TYPE, "UFS")

The alluxio.master.journal.type in ServerConfiguration will be changed to UFS in this test.
Then following tests in the same thread will running with the alluxio.master.journal.type=UFS or alluxio.master.journal.type=EMBEDDED?
(2) Situation two:
-Dalluxio.master.journal.type=UFS is passed in.
The first several tests using LocalAlluxioCluster work as expected.
Then a test   .setProperty(PropertyKey.MASTER_JOURNAL_TYPE, "EMBEDDED"). Can the following tests in the same thread still pick up the system property value UFS?

@LuQQiu I suggest trying it out to double check, but I believe in situation (1) the following tests will go back to using EMBEDDED because the configuration is reset at the end of each test. If it isn't it's a bug and it should be.
In situation (2), later tests should still be able to pick up the value of the system property. We never modify system properties, so their values will stay the same. When we reset the configuration, we will re-discover the default journal type from the system property.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3110/
Test FAILed.

@aaudiber Thanks!! I finally got it! The LocalAlluxioCluster.stop will reset the server configuration which will reload the default property value or system property. Both situation 1 & 2 will maintain the master.journal.type across different tests. Changed back to use one property to control the journal type and remove the setJournalType.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/3112/
Test PASSed.

alluxio-bot, merge this please


Start-Job fails with credentials using UPN

Steps to reproduce
$cred = Get-Credential -UserName user@domain
$jobWithUpn = Start-Job -Credential $cred -ScriptBlock { New-Guid }

$cred = Get-Credential -UserName domain\user
$jobWithLogonName = Start-Job -Credential $cred -ScriptBlock { New-Guid }

Receive-Job $jobWithUpn -Wait
Receive-Job $jobWithLogonName -Wait

Expected behavior
Two GUIDs are printed to the console.

Actual behavior
One guid is printed.

One error is printed: OpenError: [localhost] An error occurred while starting the background process. Error reported: The user name or password is incorrect..

Environment data

Name                           Value
----                           -----
PSVersion                      7.0.1
PSEdition                      Core
GitCommitId                    7.0.1
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@iSazonov This is also a bug in PowerShell 7, as seen in the Environment data section of my report.

@michaelelleby What is a behavior in Windows PowerShell?

@iSazonov The behavior is identical on Windows PowerShell 5.1

@PaulHigin What do you thing about adding UPN support?

I'm seeing the same issue.

Indeed, the documentation  did not seem clear enough to me on this point:
Type a user name, such as User01 or Domain01\User01, or
I spent a considerable amount of time identifying the specific aspects between: sAMAccountName credential, runAS & credential, nested command, difference between pwsh & powershell....
a small quick workaround
<EMAIL_ADDRESS>$uSamAccountName = "$env:userdomain" + "\" + "$($uUPN  -replace '(.*)@.*$','$1')"
$credSamAccountName  =  [System.Management.Automation.PSCredential]::new($uSamAccountName,$(Convertto-SecureString  -string $(get-content  -path $f)))


Streaming Hoster VOE sometimes jumps a few seconds forward

Steps to reproduce

Start a stream from the hoster VOE
watch the episode (happens sporadically, so you have to wait and watch)

Expected behavior
smooth streaming
Actual behavior
title.
Mangayomi version
0.3.7
Device
PC (Linux Mint 22 Cinnamon Edition / Windows 10 22H2 [Build 19045.5131]) and iPhone 7 (A1778), iOS 15.8.3 (19H386)
Other details
Unrelated to Mangayomi, but related to VOE:
I recently wanted to watch a movie through MPC-HC from VOE:
I have loaded the VOE site in the browser,
opened the "tools for web developers",
switched to the network analysis tab,
searched for .m3u8 to get the streaming link,
pasted that into MPC-HC and it also skipped like here.
So I tested if it's also happening on the VOE site itself. Watched the whole movie and it didn't even skip once.
I asked ChatGPT about this and it told me the following:
"HLS streams consist of .m3u8 files, which are playlists containing links to smaller media segments. The way these segments are fetched and buffered can vary.
Why Skipping Happens:

Network latency or interruptions.
Incorrect buffering settings.
Missing or slow segment retrieval due to rate-limiting or server-side throttling.

There might be an attempt in adaptive bitrate (ABR) switching. Abrupt switches can cause skips if the network or server doesn't respond quickly enough."
IDK if this is the actual cause for this issue, but I wanted to include it anyways.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated all installed extensions.

This also happens with the hoster "Luluvdo" (AniWorld)


Make GLTFLoader index and vertex buffer load methods public

As discussed here: https://forum.babylonjs.com/t/could-gltfloader-loadindicesaccessorasync-be-exposed-as-public-method/39469
Change to public but keep underscore and add @internal tag.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13687/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13687/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13687/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13687/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13687/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13687/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13687/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13687/merge#BCU1XR#0


JourneyMap gets stuck on "planet"

I can only assume that "planet" is a dimension registered by Advanced Rocketry, and there's an issue between it and JourneyMap. I'm running the latest versions of both, and when cycling through the available dimensions in JourneyMap's Waypoints screen, I get stuck on "planet" and can't change to the next one. If I back out and come back, I'll be back on my current dimension, but can never get past "planet".
I'm not sure if this is an issue with this mod or JourneyMap, but none of the other dimensions seem to have this problem.

I wonder if it has something to do with the fact all AR's dimensions are named "Planet".  Will look into when i can get time to do so

I noticed this issue as well. JourneyMap isn't actually getting stuck. It is a poor design choice on JourneyMaps behalf. You have to keep clicking the same button to go to the next dimension in the list. Due to Advanced Rocketry adding such a significant amount of dimensions it takes a while to click through the whole list. Simply put, there is not a bug with either mods and everything is working as intended. Just kinda sucks.
@drinfernoo I would recommend suggesting to the JourneyMap team, that instead of a single button that clicks through the list of dimensions. they use a drop down menu or something similar.
@zmaster587 I am not sure how much work it would be, but you could consider getting the planets dimension number as a string, then appending the string to the name of the dimension. Alternatively implement a method that you could use the console/chat to change a dimensions name. Obviously these options are contingent on that dimension names are not static.

@ShicKla would depend on how JourneyMap actually is getting the name, from what it sound like it may be getting it from the dimensionType object.  Unfortunately it does not seem like the getName() function can be overridden (short of ASM at least) which means rather than recycling the same one for each planet like I've been doing I'd have to create one for each, it seems kinda redundant, but is at the same time an unfortunate result of the modifications done to Minecraft.  (In 1.7.10 the world provider can return a name, the functionality has been replaced somewhere along the line between 1.8 and 1.10 with the dimensionType object.)
I also fear registering one for each planet would increase the chances of a collision between AR and another mod may occur.  It might be something I could look into though.  No guarantees though.

I don't think this will be doable post 1.7 unfortunately


Expose navigate constants

This PR addresses #257. Just let me know if there's anything else needed here!

thanks!

Thanks for the quick response!


Apply fork markers at fork time

It would be nice if we could find a way to apply the fork markers at fork time. As-is, we end up solving parts of the graph in a fork that are actually disjoint with the fork, if those dependencies were added prior to forking.
For example:
let pyproject_toml = context.temp_dir.child("pyproject.toml");
pyproject_toml.write_str(
    r#"
    [project]
    name = "project"
    version = "0.1.0"
    requires-python = ">=3.8"
    dependencies = ["anyio==3.7.0 ; python_version > '3.10'", "dep"]

    [tool.uv.sources]
    dep = { path = "./dep" }
    "#,
)?;

let dep = context.temp_dir.child("dep");
dep.child("pyproject.toml").write_str(r#"
    [project]
    name = "dep"
    version = "0.1.0"
    requires-python = ">=3.8"
    dependencies = ["iniconfig < 2 ; python_version >= '3.10'", "iniconfig >= 2 ; python_version < '3.10'"]
"#)?;

In this graph, we end up solving for anyio even in the python_version < '3.10' fork, despite the fact that it gets discarded at the very end, when we create the ResolutionGraph (since, at that point, we and the markers, and they evaluate to false).
We roughly want this:
diff --git a/crates/uv-resolver/src/resolver/mod.rs b/crates/uv-resolver/src/resolver/mod.rs
index 3bb311a00..b1d5cf3c0 100644
--- a/crates/uv-resolver/src/resolver/mod.rs
+++ b/crates/uv-resolver/src/resolver/mod.rs
@@ -2255,6 +2255,8 @@ impl ForkState {
     /// Subset the current markers with the new markers and update the python requirements fields
     /// accordingly.
     fn with_markers(mut self, markers: MarkerTree) -> Self {
+        // Here, we basically need to `and` the markers of each package in the existing state with
+        // the fork markers... and throw out anything that's disjoint?
         let combined_markers = self.markers.and(markers);

         // If the fork contains a narrowed Python requirement, apply it.

But it seems hard to "transform" a PubGrub State in the middle of the resolution. (In other words: we'd want to clone the State, then change some information about the PubGrubPackage nodes, and discard any nodes that are not relevant for the new branch of the solve.) I don't know how we'd reflect the changes everywhere. We'd probably need to consult with @Eh2406.

Yeah, it should help with some of them.

There's a lot of context I missing here. But fundamentally you looped me in about '"transform" a PubGrub State in the middle of the resolution'.  But you already roll your own resolution loop, so you have a lot more knobs available.
Adding Incompatibilities should generally be safe. Practically, there are two mutations that should be safe and easy. (Modulo never having experimented with this in practice. So not knowing where the corner cases are.)

Marking some set of versions as unavailable. Perhaps this could be used to say "within this fork, versions of Python older than x.y.x are no longer available" or "versions that require a Python incompatible with this fork are individually marked as unavailable".
There is a new dependency edge from some package to some range of packages.

For both of these unit_propagation should be able to handle these new incompatibilities even if they exclude a version that has already been selected.
Removing an Incompatibilities, is much more complicated. (Practically, the inverse operations of the two above. A package becoming available, or a dependency edge no longer being required.) I have thought about this problem for a long time, but never had time to dig in and code something. The problem is that more general Incompatibilities may have been derived from ones that you've just removed. I think it likely that there is a linear algorithm to identify all such tainted inductions and decisions. Overall this could still be more efficient than Cloneing before the problematic add, because derived implications of unrelated facts do not need to be reloaded in.
It is also possible that these dependencies whose existence is conditional on what Python version you are using, would more accurately be modeled with more exotic forms of Incompatibilities. But I would definitely need more context to suggest anything tangible. Was any of that helpful?


[FLINK-7354][tests] ignore "initialSeedUniquifierGenerator" thread in thread list

What is the purpose of the change
Netty may spawn a thread in its ThreadLocalRandom because of some secure random use which may be caught in our LocalFlinkMiniClusterITCase thread check as being started but not stopped by us. We can simply ignore this thread and solve the test instability.
Alternatively, we could solve this similarly to https://issues.apache.org/jira/browse/SOLR-10098 by setting ThreadLocalRandom.setInitialSeedUniquifier(1L); but that may be less future proof or even remove some randomness.
Brief change log

ignore any spawned thread with prefix "initialSeedUniquifierGenerator"

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

merging.


TcpStream etc should implement Clone

At least, I think they should. Any fundamental issue with this? (I haven't looked into a patch yet)

They probably should implement dup() -> io::Result<TcpStream>. There may be utility in having a Dup trait.

I mean a copy of the same fd, not a new fd, but dup is probably also useful.

The problem w/ returning a new TcpStream w/ the same FD is that the FD is dropped when TcpStream goes out of scope. So, the cloned TcpStream would become invalid when the original value is dropped and vice versa

@cmr Out of curiosity, why do you need to clone the TcpStream?

@ayosec shenanigans with rust-openssl that I hope to fix (https://github.com/sfackler/rust-openssl/issues/250)

I don't think that TcpStream can implement clone. I read the issue, and it seems that the problem is that SslStream does not implement Evented.
My general understanding of SSL & non-blocking sockets is that it is better to use the in memory buffer BIO (w/ OpenSSL) which completely decouples sockets from SSL.
So, either the SSL lib would need to implement Evented on SslStream (probably not a great idea), or there would need to be a custom SslStream wrapper that implements Evented given that implementing clone on
Also, this issue seems related to #226. So, I think I'm going to close this in favor of that one since implementing Clone for TcpStream is not possible.


tests: ignore 'trash directory.*.sh/'

When running tests like ./t0010-init.sh -v -i in tests/, trash directories are left on purpose to make it easy to debug a failing test. Let's ignore these directories.

:+1:


IP Address Lockout Bypass

The code which determines the source IP address of a login uses the following logic:
remote_addr = (self.request.META.get('HTTP_X_REAL_IP') or self.request.META.get('REMOTE_ADDR'))

This means an attacker can override their source IP address by supplying an X-Real-IP header containing an IP address different than their own (assuming the attacker's header isn't replaced/stripped by an intermediate system). A brute force attack is therefore still possible by cycling through values in this header.
This library should only support a single mechanism of determining the visitor's IP address which is configured by the library user to match the deployment environment (e.g. direct Internet connect or behind a load balancer)

Thanks for you feedback. Do you think it would be enough to add a configuration setting to determine the HTTP header to use?

Yes - that would be my suggestion. The default setting when a header isn't configured should be REMOTE_ADDR - but if a header is configured, then ONLY that one header should be used.

Fixed in commit df86442


Servers return wrong column types in case of empty results (everything defaults to STRING)

Non-empty results (correct types):

Empty results (incorrect types):

This part of the code needs to be changed:
https://github.com/apache/incubator-pinot/blob/master/pinot-core/src/main/java/org/apache/pinot/core/common/datatable/DataTableUtils.java#L121

This happens when all the segments are pruned out, and Pinot server short-circuits the query to directly return without checking the schema. We should just not return the schema when there is no record returned.


fix that the error message has no effect

fix that the error message has no effect

 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.

Many thanks!


THRIFT-5336 Add possibility to setup connection timeout in TCurlClient

Add possibility to setup connection timeout in TCurlClient
In TCurlClient we can set only total timeout, it will be great to have opportunity to set connection timeout

[x] Did you create an Apache Jira ticket?  (not required for trivial changes)
[x] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
[x] Did you squash your changes to a single commit?  (not required, but preferred)
[x] Did you do your best to avoid breaking changes?  If one was needed, did you label the Jira ticket with "Breaking-Change"?
[ ] If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

@Jens-G @ulidtko Please take attention to this pull request

@Jens-G @ulidtko Please take attention to this pull request

@Jens-G is it possible to merge this pull request before release 0.14?

@Jens-G is it possible to merge this pull request before release 0.14?

You mean possible like in "technically possible"or more like "could somebody pls review and merge?"

You mean possible like in "technically possible"or more like "could somebody pls review and merge?"

Thank you :)

Thank you :)


Remove legacy steps

These have been disabled in recent versions, and are being
removed to ease migration to ParameterTypes.

There is some code in util.rb that is likely also dead now.

There is some code in util.rb that is likely also dead now.


Remove the providers switch in gen/calc.py

This removes the providers switch in gen/calc.py, pushing all the data which
was somewhat hackishly combined there down into the correct installer components
using the "Source" concept of gen to provide the values. This means moving onprem,
AWS, and Azure to use "Source" directly and add the source to the set of sources
when calling gen.generate rather than setting a magic key by hand and relying
on that to "imply" the right configuration.
This should provide better error messages for all cases: There are less bad
paths which we can tell the user about for possibly setting configuration. In
addition, it makes lite binding configuration easier to implement, as all the
pieces start being more "bound" to the one particular installer they effect.
From my point of view this also makes the code easier to reason about than the
previous nested conditionals which selected which options to use.
The patchset also removes manual argument combining from aws and azure template generation, instead teaching them to pass around sources, and just add new sources with more arguments.
This makes those template generators easier to work with, and harder to mess up, as it's more directly obvious what data came from where, and it's impossible to accidentally overwrite a variable.
That prepares do_create to be able to switch from  being given variant_arguments as a parameter to instead taking variant_sources, the advantage then being that from top to bottom things don't modify the arguments in place, it's obvious where various values came from in the composition, and code is generally simplified.
Unfortunately do_create() can't be migrated currently because cloudformation_s3_url inspects the arguments in a weird way. That is entirely fixable, but a different sort of work than this patchset (Spreading Sources / removing manual argument dictionaries).
Also includes some drive-by fixes, see the individual commits for details.
Issues
Checklist

[x] Included a test which will fail if code is reverted but test is not
[x] Followed relevant code rules Rules for Packages and Systemd

Review comments:

How was this tested and validated?
The test changes as see cover onprem_source, but the code makes multiple other changes too. (even internals.py)
Does this change warrant a manual testing and has that be done to verify?
I have no "code" related comments. Those look good to me.

Validation: The fact that the integration tests run and still generate / install a DC/OS that functions. We test all these installer codepaths on every single PR
There are lots of individual commits in the PR. Each one is atomic, some are really, really tiny. Their individual commit messages talk about what is happening in each commit. The gen.internals changes for instance: https://github.com/dcos/dcos/pull/956/commits/b65552be447019fd9c62a00d915a8e9986cc67f5, https://github.com/dcos/dcos/pull/956/commits/6b09153ef97f8728ba42c0b4c0247cc971a01bb6
As far as hand validation, I'm pretty sure the automated validation is good enough, as it tests every code path this touches, combined with verifying through code review that sources all have exactly the same config inside them as before I think there is sufficient evidence to tell if this is working or not.

@orsenthil updated, please take another pass


Final homework submission checklist

Review
You are required to submit the following for review:

A walkthrough video demonstrating the functionality of the application.

A sample README.md file for a project repository generated using your application

The URL of the GitHub repository, with a unique name and a README describing the project

Check, check, and check...


.returning('foo') returns primary key instead of 'foo' column in sqlite3

I have a node app that I switch back and forth between sqlite3 and postgres.
When I my npm script for using sqlite3 I get back a primary key rather than the column I specified.
Postgres is returning the correct column.
No matter what I put in for .returning('*'/['uuid']/'name' .....) I seem to be getting the primary key in sqlite3.
This is how the docs describe the intended behavior.
// Returns [ { id: 1, title: 'Slaughterhouse Five' } ]
knex('books')
  .returning(['id','title'])
  .insert({title: 'Slaughterhouse Five'})

// Returns [ { id: 1, title: 'Slaughterhouse Five' } ]
knex('books')
  .returning(['id','title'])
  .insert({title: 'Slaughterhouse Five'})

The Query in Question
add: function (d, results) {
    return db('output')
      .returning('uuid')
      .insert({
        classifiers: JSON.stringify(d.classifiers),
        created: now(),
        datasource: d.datasource,
        files: JSON.stringify(d.files),
        name: d.name,
        results: results,
        uuid: uuid.v4()
      })
      .then((ret) => ret[0])
  },

Screenshot of data

Config File
var prod = process.env.PROD_CONN_STRING,
  dev = process.env.DEV_CONN_STRING,
  test = process.env.TEST_CONN_STRING;

module.exports = {

  test: {
    client: 'pg',
    connection: test,
    migrations: {
      tableName: 'knex_migrations'
    }
  },

  demo: {
    client: 'sqlite3',
    connection: {
      filename: './tcu.sqlite'
    }
  },

  dev: {
    client: 'pg',
    connection: dev,
    migrations: {
      tableName: 'knex_migrations'
    }
  },

  prod: {
    client: 'pg',
    connection: prod,
    pool: {
      min: 2,
      max: 10
    },
    migrations: {
      tableName: 'knex_migrations'
    }
  }
};

This might be a bug or perhaps the docs are lacking.  Either way I can try to take a look at it if a collaborator can point me in the right direction.

Sorry for the confusion. At the beginning of returning docs, the first line reads "Utilized by PostgreSQL, MSSQL, and Oracle databases, the returning method specifies which column should be returned by the insert and update methods."
I guess we could be a little clearer in the wording there, but the implication is that this feature isn't supported by sqlite3.
We could also look into throwing an error to fail when trying to use this feature on an unsupported client. Thoughts?

Ah I see that makes sense.  I think an error might be helpful for people in the future.  This would simply trigger the .catch?
I actually miscopied what is in the docs. It actually says:
// Returns [2] in "mysql", "sqlite"; [2, 3] in "postgresql"
knex('books')
  .returning('id')
  .insert([{title: 'Great Gatsby'}, {title: 'Fahrenheit 451'}])

Outputs:
insert into `books` (`title`) values ('Great Gatsby'), ('Fahrenheit 451')

So the sqlite mention confused me.  Removing that part might be more obvious.
Thanks for the quick response!

An error would be nice to have. This is not the first time that people has been confused with features, which are supported only by some db engines.

Not sure if error should be really be thrown, since it makes hard to generic libraries/wrappers over knex. The wrapper implementation will have to check the connection config before chaining the returning method.
Also people get confused, since they ignore the documentation text above the code blocks :)

@thetutlage I don't see how creating erroneus query is a better choice than throwing and error and yes generic wrapper should make sure that underlying DB supports the .returning statement before calling that builder method or otherwise it wont return correct results.
If wrapper wants to be really generic, it won't use .returning feature at all and just emulates it by fetching the date with select or some other portable way (or some specialised implementation for each dialect).
I'm not a big fan of the historical-JS habit of allowing users to do invalid code with silent errors / noop functionality.

Have we reached a conclusion to this issue? Throwing an error, silently ignorning, and printing a warning during query compilation are all valid options imo.

I would propose following:

add warning for all of these old places where people are using query builder methods which are just not supported by used dialect.
Afterwards we can consider changing all those warnings to errors and do bigger break to backwards compatibility at once.
For new APIs error should be throws for the unsupported dialects (I've been requiring this in PRs already for a while).

Aside from the issue at hand I don't know methods by hand that aren't supported by specific dialects, so in the spirit of not escalating the issue any further, I will only add a warning for .returning to sqlite.
t

Knex:warning - .returning() is not supported by sqlite3 and will not have any effect.

#2471

As of 0.14.4, the warning is printed every time I run migrate() in test even though the returning function is never used in my code?

I have an app using a psql database and some unit tests which use mock-knex and thus set sqlite as the backend. Since my upgrade to knex 0.14.4 the unit tests display this output:
    ✓ obtains a lock and process a book (54ms)
Knex:warning - .returning() is not supported by sqlite3 and will not have any effect.
Knex:warning - .returning() is not supported by sqlite3 and will not have any effect.
Knex:warning - .returning() is not supported by sqlite3 and will not have any effect.

I know that returning() doesn't work with sqlite (it's written in the doc) and my tests already take that into account (even if actually it doesn't matter, since I'm mocking the queries) so it would be nice to have a way to suppress the warning if possible (couldn't find anything in the docs). thanks!

Hey chaps.  This is fine, but I found that the mssql dialect does not return the primary key when you leave of the .returning() during an insert, so I was using it to get the primary key across both DB types, even though it was technical not supported my sqlite3.  Is the lack of primary key returned with an insert in mssql by design or is it ok to add it?

@GeekyDeaks Also postgresql does that... Goog to know that mssql does that also. I've been meaning to make proposal about changing .insert({}) functionality in a way that it would be cross db compatible somehow (by adding some implicit returns for postgresql and mssql or somtehing like that).

Thanks @elhigu - would you implement it in the processReponse() of the dialect? i.e. like in dialect/sqlite3/index.js
      case 'insert':
        return [ctx.lastID];

If so, I might take a look at this over the weekend and submit a PR.  I'm only just getting up to speed with knex though, so it might take me a little longer 😄

Process response is not enough, since also built query needs to be modified, I don't think this can be implemented before it has been properly discussed first. There are some benefits/drawback that needs to be considered.

ah, yeah - was poking around under the debugger and noticed that.  I can workaround by checking the client dialect for now.

That's great; but how do you get the ID of a created, updated, or deleted record in Sqlite3?


Update deposit.js

@wayudi208012 looks like your PR changes the deposit address to 0x48f33860F133e0a2F8f11c6E1625911d2BA6AB45 - can you explain the reasoning behind this update?

0x48f33860F133e0a2F8f11c6E1625911d2BA6AB45


Multiple separate version reports upon winget upgrade

Steps to reproduce
The following command will install the package that I identified with the issue.
winget install Microsoft.dotnet;

Expected behavior
winget upgrade should not report two separate versions for the same package.
Actual behavior
It shows the same package with different versions.

Environment
Windows Package Manager v1.0.11692
Windows: Windows.Desktop v10.0.19043.1052
Package: Microsoft.DesktopAppInstaller v1.12.11692.0

The .net SDK does get treated as different "packages". They run side by side so other packages with version specific dependencies don't break. There are several other issues discussing this topic.

Thanks, @denelon, and that is precisely my point.  It should treat them as separate packages since you may want to have 5.1.200 and 5.2.100 side by side, and that doesn't mean that it should suggest upgrading all to 5.3.0
If you don't mind, can you give me a reference issue that covers the problem here to close this one.  Thank you so much for your attention and participation.

@cilerler, this is the latest comment:
https://github.com/microsoft/winget-pkgs/issues/17985#issuecomment-874321711

Perfect, thank you!  Closing this issue since it is a duplicate.


kvm: bump jna version to latest

This fixes issue for cloudstack-agent to make connections to libvirt
on arm64 boards.
The jna-platform provides non-default (x86_64) mappings, read more:
https://github.com/java-native-access/jna/blob/master/www/PlatformLibrary.md
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔debian. JID-1257

@blueorangutan package

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-1591)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 54149 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4119-t1591-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Smoke tests completed. 82 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_02_deploy_kubernetes_ha_cluster
Error
3621.19
test_kubernetes_clusters.py

test_04_deploy_and_upgrade_kubernetes_cluster
Error
0.05
test_kubernetes_clusters.py

test_05_deploy_and_upgrade_kubernetes_ha_cluster
Error
0.05
test_kubernetes_clusters.py

test_06_deploy_and_invalid_upgrade_kubernetes_cluster
Error
0.05
test_kubernetes_clusters.py

test_07_deploy_and_scale_kubernetes_cluster
Error
0.05
test_kubernetes_clusters.py

ContextSuite context=TestKubernetesCluster>:teardown
Error
61.85
test_kubernetes_clusters.py

@blueorangutan test ubuntu kvm-ubuntu

@rhtyd a Trillian-Jenkins test job (ubuntu mgmt + kvm-ubuntu) has been kicked to run smoke tests

@blueorangutan package

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✖centos7 ✖debian. JID-1274

@DaanHoogland thanks I've updated the description, the addition of jna-platform allows the cloudstack-agent to run on arm64 (RaspberryPi) boards. Without this dependency, cloudstack-agent may not work on certain platforms/CPUs.

@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✔debian. JID-1296

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-1627)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37408 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4119-t1627-kvm-centos7.zip
Smoke tests completed. 83 look OK, 0 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File


WebSocket connections are not allowed or blocked

Code :
const Hero = require('@ulixee/hero-playground');

(async () => {
    const hero = new Hero({showChrome: true, showChromeInteractions: true});

    await hero.goto('https://libwebsockets.org/testserver/');
    await hero.waitForPaintingStable();
    // await hero.close();
})();

If I reload the page from the browser :

Thanks for reporting. Looking into this.

Fixed in next version of Agent (https://github.com/unblocked-web/agent/pull/11/commits/cca0419f65539129d5f5a44e76f2ce4ecdec6b24)

Fixed in version 2.0.0-alpha.10


Adding limitations for 5.1 (rebased onto dev_5_0)

This is the same as gh-1138 but rebased onto dev_5_0.

See https://trello.com/c/uV9FuKGO/85-5-1-limitations and https://trello.com/c/mTr7xcBp/250-5-1-known-limitations

--rebased-from #1138

Will need an additional commit to remove properties links not present on this branch.

Looks fine, please merge.


[WIP] implement raw trainer

This PR implements a Raw Trainer.

@aniketmaurya Hey Aniket, I'm going to close this because it is stale, and because I believe the CLIP trainer would belong to the https://github.com/lucidrains/x-clip repository