Update on WinAppDriver

Thank you all for your patience, we hear your frustration at the lack of updates on the future of WinAppDriver. In November 2020 we mentioned that development would be paused for at least 6 months. We don’t have a timeframe of when the level of resourcing for WinAppDriver will change as our team is currently focusing on making a great platform for the future of Windows 11 apps – when there is confidence in a timeframe, we’ll definitely share it with you.
We are committed to bringing critical improvements for WinAppDriver to keep pace with other developments in the platform, so it can continue to be used alongside our other advancing technologies.  One such improvement is ARM64 support in WinAppDriver v1.3  to ensure alignment with the Windows App SDK. Please feel free to contact me with any further questions or concerns!

Hi @kat-y Thank you for the updates, this really helps boost our morale and continue using WinAppDriver. Here are my questions:

Any updates on whether the project might go open source? or any intentions to?
The new build is expected to have issues(due to the shift to .net 5 and also the new platform-specific builds) so how are you planning the testing? I believe @DHowett is the sole resource in WinAppDriver at the moment...
And I believe there won't be a hard 6 months gap this time?

Thanks once again and hope to see frequent updates. Cheers 😊

our team is currently focusing on making a great platform for the future of Windows 11 apps

I hope we can look forward to a time when the team displays an interest in helping developers ensure their Windows 11 apps are well tested too.

@kat-y  there is simple PR pending from the community like  #1539 or #1058
Although I understand you do not want to work heavily on this, could you open and accept some community items like the one previously set ?

@fforjan @kat-y Agreed, at least the PR section should be looked at for now in order to capture any effort the community has done to improve documentation and such.
I have been trying to get some samples added for RobotFramework for over a year now #1148

Please have a look to https://github.com/microsoft/WinAppDriver/issues/1556. It is not possible to launch new version of WinAppDriver with Appium

If only I had a penny for every great developer tool that has been stalled due to "more pressing features" 😄. Looking forward to more updates on this repository hope this gets some priority and the community contributions are processed.

@DHowett @kat-y This seems like it needs to be adressed.
Please evaluate: https://github.com/microsoft/WinAppDriver/issues/1610

Agreed #1610 needs to be a top priority.

@kat-y this explanation (after 6 months) and the previous ones sound like coming from a cash strapped early stage startup, not a billion dollar company. FFS, hire a few developers and get things moving, this is a critical piece of software! Have a look at the great progress and perfect developer-relations at the https://playwright.dev/ team, also at Microsoft. When you abandon software like this you make developers disillusioned with native Windows apps, and thus moving to develop using other tools. Remember this: https://www.youtube.com/watch?v=Vhh_GeBPOhs

FYI: https://github.com/microsoft/playwright/issues/10291 - perhaps the two teams could join forces?

@kat-y Hi Katy - my company is considering a move to Selenium w/WinAppDriver for desktop testing. We're of course interested in the long term viability of WinAppDriver and need a clear picture of what the situation current and future is. Any way of getting in touch with you directly? feel free to mail me at<EMAIL_ADDRESS>

@kat-y @DHowett This is odd and has caused some confusion.  Perhaps it can be added to your plans.  Using Selenium in msedgedriver.exe .FindElementsByXPath("*") can be used to find children elements but, here the equivalent syntax is .FindElementsByXPath("*/*").
https://github.com/microsoft/WinAppDriver/issues/669#issuecomment-938144641

@kat-y Any update when can we expect the open issues to be addressed.

Hi @kat-y!
I'm bumping this again to check on the current state of the project.
If there are insufficient resources on your team or even in any case, it would be great if the source for WinAppDriver itself would be made public so that the community can start maintaining the project.

We are Visual Studio Enterprise subscription customers. The Coded UI Tests functionality was discontinued for the benefit of using Appium and WinAppDriver.
So we are currently stuck with a project where we cannot even know if it ever will be developed in the future?

FYI: I wrote to about 4-5 main committers of this repo at MS asking for an update.

Any update as to when any focus will be put back on enhancing the WinAppDriver, resolving existing issues, or making this an open source project?

I would like to pile on here and ask what, if anything, is going to be the automated testing solution for Windows UI applications now that CodedUI is deprecated, and it appears that WinAppDriver is no longer being supported.
Microsoft leaving people high and dry here...

It would be so easy if WinAppDriver itself were open source.
@kat-y: You mentioned some time ago that you guys were looking into open sourcing the code, are there any news regarding this, or an ETA?

I would like to pile on here and ask what, if anything, is going to be the automated testing solution for Windows UI applications now that CodedUI is deprecated, and it appears that WinAppDriver is no longer being supported.
Microsoft leaving people high and dry here...

FlaUI? I've used it very briefly in the past and seems to be a decent alternative. IIRC it's also open source.
I suppose there's always direct UIA coding, but I definitely missed some of the niceties from WAD and FlAUI.

I would like to pile on here and ask what, if anything, is going to be the automated testing solution for Windows UI applications now that CodedUI is deprecated, and it appears that WinAppDriver is no longer being supported.
Microsoft leaving people high and dry here...

FlaUI? I've used it very briefly in the past and seems to be a decent alternative. IIRC it's also open source.
I suppose there's always direct UIA coding, but I definitely missed some of the niceties from WAD and FlAUI.

and FlaUI has open discussion/suggestion for interfacing to Selenium/WebDriver. Unfortunately, there's been no real work on it. In case anyone is interested or can contribute in that area.
https://github.com/FlaUI/FlaUI/issues/50

It's been more than a year now, when can we expect a new release? Please let us know as we have moved towards WinAppDriver, no release for an year, makes us worrisome about our decision.

I'll also ping @kat-y again.
It would be so great if you guys would open source WinAppDriver, I would love to contribute!
@kat-y's activity on Twitter has also stopped at the end of 2021, so I'm not sure whom to contact otherwise.

I would like to pile on here and ask what, if anything, is going to be the automated testing solution for Windows UI applications now that CodedUI is deprecated, and it appears that WinAppDriver is no longer being supported.
Microsoft leaving people high and dry here...

FlaUI? I've used it very briefly in the past and seems to be a decent alternative. IIRC it's also open source.
I suppose there's always direct UIA coding, but I definitely missed some of the niceties from WAD and FlAUI.

what's IIRC?

@anunay1 IIRC = If I recall correctly

Is there a way to inquire from Microsoft who to contact about this? Maybe starting from the top executives as needed, and any public communications channels of Microsoft?

Who's the head of MS Open Source initiatives?

Maybe @DHowett has more info?

it seems this project was dead, in face, we still some tool to test desktop application, when this project was active and many people using it, we think it can be make a standard library , but now, i have to found other tool to test our desktop applicaiton.

I am planning to migrate to FlaUI. I have been doing some PoCs with it and it makes what I need, furthermore, it is quite faster.
I can't understand why MS is forgetting WAD. I can't imaging how many windows apps are being developed now in the world and still without a good UI testing tool provided by MS.

Is FlaUI actively maintained, Will it work with UWP apps.

Paging @DHowett and @kat-y.  Who is in charge of this project?  Can we get an update?

Paging also past committers @timotiusmargo , @yodurr , @paulcam206 - who is in charge of this WinAppDriver?  Can we get an update on #1550?

It's quite worrisome that there is absolutely no update on this repository for almost two years now. With the amount of PRs that would be great additions it is annoying.

Is FlaUI actively maintained, Will it work with UWP apps.

Well, "actively maintained". Last commit 3 months ago and 3.2.0 Nuget is from 2020 July.
Nuget is not working fine so I have forked master and generate a new Nuget.
Not sure if UWP app is supported, sorry

New NuGet from FlaUI, FYI. Version 4.0.0, .NET6 compatible. Seems to be active again

FlaUI is sadly missing the W3C webdirver but winapdriver is also missing it so ...

FlaUI is sadly missing the W3C webdirver but winapdriver is also missing it so ...

If I remember all endpoints correctly, WinAppDriver actually implements the W3C WebDriver specs.

Not sure why FlaUI needs to implement anything around WebDriver? The brief bit I've worked with it, it works fine without it.

It doesn't need to, it's just that WebDrivers are more flexible because they can be targeted with any compliant client.

FlaUI with WebDriver interface, from a user perspective would simplify the test automation. You can use single/same API to test web, desktop, mobile. Simplify the code deployment and the learning curve for the test coding. It's a different story if you work solely on desktop automation.

Exactly.

Understood, and agreed to an extent. That was one of the reasons I recommended WinAppDriver when it officially released. But if this is going to be unmaintained and not open sourced, there aren't many other options left. Plus, the learning curve on FlaUI wasn't so high compared to other desktop automation tools (Coded UI, TestStack White, HP QuickTestPro/UFT,) so if it means I at least have an opportunity to help maintain the tool with FlaUI, that's worth it to me for new projects. Unless anything changes here, I'd recommend checking out its capabilities.

Totally agree with @PandaMagnus, in fact I am migrating all my scripts to FlaUI. It is totally unacceptable what Microsoft is doing with WinAppDriver and I am not speaking about pushing new code, but keep the community informed. It is crazy not to have an official test tool working and updated...

see: https://nutjs.dev/

Looks interesting but not sure it's a real alternative to WinAppDriver because it doesn't seem to have native Windows UI integration and instead focuses on computer vision and mouse/keyboard automation...

Yeah exactly, and there are tons of tools out there that do exactly that already. The special thing about WinAppDriver is that it implements the W3C WebDriver standard.

This is one of those things where irrespective of the situation people just don’t want to lose faith lol.

Yeah exactly, and there are tons of tools out there that do exactly that already. The special thing about WinAppDriver is that it implements the W3C WebDriver standard.

Just wanted to note, tools like those could be (and are) better if we just integrate/wrap them with a W3C Webdriver interface. It is nice when it is native, but the interface wrapping can simply be an external tool. I've already submitted suggestion to do such on the major alternatives. And created PoC W3C WebDriver wrapper implementations for 2 such tools, one being AutoIt, though it's been years so the WebDriver spec support compatibility could be a bit outdated.
Wrapping a UI automation tool around W3C WebDriver spec isn't too hard when you have the integration components ready (e.g. easy translation between tool's native UI mapping and WebDriver spec, REST server interface skeleton framework to build WebDriver API on top of).
Regarding these types of alternative tools, the old/existing ones is understandable, but too bad for any new ones that crop up, the developers often don't consider exposing it via WebDriver spec, it only comes as an afterthought if at all.

Very good points that you are bringing up there, @daluu!
I've also written a few WebDrivers and WebDriver clients, and such tools might be a lot easier to wrap than Microsoft's UIAutomation.dll and native libraries.
Another thought for the future: The W3C committee is working on the so-called WebDriver BiDi spec, which I would love to implement for Windows desktop apps if I had more time.
But seeing that there is only radio silence regarding WinAppDriver, it might be best to start investing into this new spec.

Is still research progressing on #1746?
Any update on this issue?

looks like dead end here with WinAppDriver :(

FYI, came across this email looking up Twitter posts, you can try emailing and see if we can get any response<EMAIL_ADDRESS>Even Selenium team had some issues making contact, but that was 2021, so things could be worse now.
Reference: https://twitter.com/jimevansmusic/status/1437228175117983752

Thank you all for your patience, we hear your frustration at the lack of updates on the future of WinAppDriver. In November 2020 we mentioned that development would be paused for at least 6 months. We don’t have a timeframe of when the level of resourcing for WinAppDriver will change as our team is currently focusing on making a great platform for the future of Windows 11 apps – when there is confidence in a timeframe, we’ll definitely share it with you.
We are committed to bringing critical improvements for WinAppDriver to keep pace with other developments in the platform, so it can continue to be used alongside our other advancing technologies. One such improvement is ARM64 support in WinAppDriver v1.3  to ensure alignment with the Windows App SDK. Please feel free to contact me with any further questions or concerns!

@kat-y @DHowett
It’s been more than 2 year. please provide an update. Not sure if you are still at Microsoft and looking in to WAD

I just noticed commits from @DHowett, and @smilinrobin @licanhua in 2022, so in terms of best people to ping on Github, would probably be them.

Hi folks. I don't work for Microsoft and am not aware of any updates around the WinAppDriver project.

There is a new initiative started by @licanhua called Ywinappdriver .
It’s calling out some internal decision making too. But this looks abandoned too. Looks like there are resources interested just management there no ready to commit / support.

Did anyone ever try emailing<EMAIL_ADDRESS>I recently did, but I guess it might be a dead unmonitored mailbox. It didn't bounce or return mailbox full at least.

No response. It didn't bounce either

just for information for those who still waiting a miracle.
My team has switched away from this "abandonware" to "self-made" solution. we injected into our winforms and wpf apps a (self made) visual tree walker, build inter process communication between the app and the UI test and we're happy now.
new engine works a lot stable, and by 6x times faster. this work takes only 2 person*month of time. do not wait, seek options, guys!

just for information for those who still waiting a miracle.
My team has switched away from this "abandonware" to "self-made" solution. we injected into our winforms and wpf apps a (self made) visual tree walker, build inter process communication between the app and the UI test and we're happy now.
new engine works a lot stable, and by 6x times faster. this work takes only 2 person*month of time. do not wait, seek options, guys!

Can you share any POC?

just for information for those who still waiting a miracle.

My team has switched away from this "abandonware" to "self-made" solution. we injected into our winforms and wpf apps a (self made) visual tree walker, build inter process communication between the app and the UI test and we're happy now.
new engine works a lot stable, and by 6x times faster. this work takes only 2 person*month of time. do not wait, seek options, guys!
You miss the point, that WAD allows for cross-machine communication which makes it much more scalable and CI/CD friendly. That's why so many people would like to get some feedback about the roadmap.

@anunay1 I can't, it is not open source. But in general the design is: 1. Visual Tree walker search for controls by their automation name, as we did with WinAppDriver; having the control we may do whatever we want: click on that, check its status, replace text in textbox, get the bounding box to click on it via win32 API etc. Visual Tree Walker for winforms is something trivial. VTW for WPF is accessible as open source - PTAL SnoopWpf. 2. for custom controls (not builtin ones) your VTW must have an "extension points" 3. communication with the test is the last component. Hope it helps you.
@pm90pl IPC we choosed is suitable for cross machine communication too. I just choosed wrong word (inter PROCESS communication), sorry for that! anyway, anyway communication problem is not a strategic problem.

Pinging @kat-y and @DHowett again in hope for a response.

Pinging @kat-y and @DHowett again in hope for a response.

@kat-y  Are you still PM for WinAppDriver project. could you please provide us an update.

I'm wondering, if any progress to this status update could be had if we keep pursuing Microsoft outside of this GH repo and issue here. Like contact Microsoft by email, phone, social media, attempting to hit the senior management like CEO, CTO, etc. or their PR team, etc. Or trying to engage the news media to assist with this. I've read in newspaper articles, sometimes you get success when you can get the attention of CEO or higher management, or the news reporters involved. At the current pace of pings and approaches, I doubt we'll see any update.
Maybe we even need something like an open source protest at MS headquarters, just to get the message out for an update.

I'm wondering, if any progress to this status update could be had if we keep pursuing Microsoft outside of this GH repo and issue here. Like contact Microsoft by email, phone, social media, attempting to hit the senior management like CEO, CTO, etc. or their PR team, etc. Or trying to engage the news media to assist with this. I've read in newspaper articles, sometimes you get success when you can get the attention of CEO or higher management, or the news reporters involved. At the current pace of pings and approaches, I doubt we'll see any update.
Maybe we even need something like an open source protest at MS headquarters, just to get the message out for an update.

That sounds like something we is the only option now is to petition senior management to atleast get some real updates

This seems to note some executive members of MS
https://news.microsoft.com/leadership/

We can try with https://twitter.com/DHowett on Twitter. Not sure if we could get any response...

Best option is to escalate to Microsoft OpenSource Team at their Twitter https://twitter.com/OpenAtMicrosoft

Best option is to escalate to Microsoft OpenSource Team at their Twitter https://twitter.com/OpenAtMicrosoft

Didn't know this account! I have just pinged them...https://twitter.com/IgorRecioH/status/1645027891615244289?t=NNf0MB2R8Sya83oAloodpw&s=19

An alternative question that the GPT pivot poses in my mind is do we need more than a text box to convey the complexities taken care of by the UI and bring them to the products API?  Maybe the next generation apps control complexity and localization tasks will be minimal since properly trained models can extract meaning from any language and recast it to API calls.

An alternative question that the GPT pivot poses in my mind is do we need more than a text box to convey the complexities taken care of by the UI and bring them to the products API? Maybe the next generation apps control complexity and localization tasks will be minimal since properly trained models can extract meaning from any language and recast it to API calls.

Can you please elaborate?
This does not make any sense to me.
Of course there are other approaches to this, but me and many others in here still want to use WinAppDriver for various reasons.
Also, this WebDriver implementation already exists, so why should we re-invent the wheel?
Microsoft could just open-source the code, as there should in any case not really be any secrets hiding in it.

I certainly do not wish to confuse this thread. I also agree this project should be open source because allowing us to update to change is necessary.  My hope with the above comment is to retrospect back to our sudden 3 year pause on something as fundamental to app development as UI testing.  My intent here is to question what UI testing developments will be necessary (other than the long awaited W3C changes).
Our ui's are a means to encapsolate a complex, useful task and put them into a button.
If the users intent is captured with free text in their native language, and the GPT will translate it to the applications API.  Then this is accomplished more seemlessly.  (There are methods to fine tune the GPT to only output in a given coding style.  Lots of Microsoft docs springing up the last couple of weeks)
Given the above, and the large industry wide pivot, is Microsoft struggling with the question "Is there value of putting effort into updating/extending the UI?"
If the UI is not changing then maybe current  testing is enough?
I am not in the know for what Microsoft's plan is, but certainly I understand why they may be slow to update given how the app development landscape has changed.
At the moment we have been testing on Windows 10/11 without large problems.  Are greatest challenges are App startup with a splash screen and scrolling to virtual items.  Other than that our custom code is minimal and stable to support our very large, diverse application.

This repo might also be interesting, as that team was working on WinAppDriver.

perhaps pinging the microsoft/playwright team is an option. I think the PM is active on twitter.
it is not a good look for any open-source test-automation framework from MS given what has happened to winappdriver

Thank you, Peter. I will ping Debbie, let's see if we get some new info.

This repo might also be interesting, as that team was working on WinAppDriver.

Yep, will check too, thanks!!!

perhaps pinging the microsoft/playwright team is an option. I think the PM is active on twitter.
it is not a good look for any open-source test-automation framework from MS given what has happened to winappdriver

Thank you, Peter. I will ping Debbie, let's see if we get some new info.

This repo might also be interesting, as that team was working on WinAppDriver.

Yep, will check too, thanks!!!

Debbie's response: https://twitter.com/debs_obrien/status/1648059827871010817?t=Whh6e4hVnqehMOh5AsJryw&s=19

Appreciate the update on what roadmap looks like for WinAppDriver, this will give some confidence to test developers to plan framework designs for big test framework.

Appreciate the update on what roadmap looks like for WinAppDriver, this will give some confidence to test developers to plan framework designs for big test framework.

Did I miss something?
As far as I can see there hasn't been an update for several years at this point.

@ChristoWolf nothing missed.  The above account just opening up issues in repository and seeing if the are closed.  Probably just a bot.

Apologies for confusion, edited my comment.

Debbie's response: https://twitter.com/debs_obrien/status/1648059827871010817?t=Whh6e4hVnqehMOh5AsJryw&s=19

Did anyone try the Discord server Debbie mentioned in her response? Any luck there?

Debbie's response: https://twitter.com/debs_obrien/status/1648059827871010817?t=Whh6e4hVnqehMOh5AsJryw&s=19

Did anyone try the Discord server Debbie mentioned in her response? Any luck there?

I did yesterday but no success. They told me that Playwright is not an alternative for WAD. We knew that, we only want some info from MS staff, nothing else...

Hello @kat-y! I saw this in a google search trying to find new about WinAppDriver. It say it was updated last week, but the version is 0.3(weird). https://www.microsoft.com/en-US/download/details.aspx?id=51663
Does that mean there is life in the project?

Weird indeed!  I have 1.2.1 installed currently.  I tried installing this supposed 0.3 version but was told a newer version was already installed.

I guess it's time to ask the question again: what are people using in place of WinAppDriver?
Ranorex, TestComplete, FlaUI, etc.

I personally have started to use https://github.com/FlaUI/FlaUI as many have mentioned before. I have been able to trigger the tests remotely. I still miss being able to controll two computers easily, which would probably make me revisit WinAppDriver in the future, but not being fully open sourced is a really big turnoff.

Bumping and hoping for open source.

I wonder if there are any other means to get this publicly debated/discussed (on social media and/or traditional news networks) so that Microsoft would take notice and at least offer some updated PR response.

@kat-y @DHowett can you please share updates here, It will help us to decide what need to be done further and search for alternatives.

Another day, another opportunity to bump.
@kat-y, @DHowett: Please open source WinAppDriver 😃

still not clear if this project is abandoned or not

Yeah, this seems abandoned, which is unfortunate... we're being driven to other options for automated testing, such as Squish, which end up costing a significant amount of money.

Just linking it here if somebody would be interested in maintaining an open-source WAD alternative, which could be used with Appium's windows driver: https://github.com/licanhua/YWinAppDriver/issues/33#issuecomment-1712837924

FYI, As we upgraded our application to NET8 it is still working.

Bumping again because WinAppDriver does not comply to the newest WebDriver standard specs and is thus not directly compatible with Appium.WebDriver compatible anymore, see in particular this.
@DHowett @kat-y Please consider communicating further plans with us.

I find it interesting that MS seems to have abandoned this, because it fits very well with the AI initiatives that they are so deeply involved in.  For instance, you could hook up tool calls allowing an LLM to easily use Windows applications without the inconsistency of integrating a vision component.

@aronweiler I don't really see a connection.
Also, there are several major problems with your idea:

Any ML algorithm only works (i.e correctly labels) with a certain probability.
Introducing flakiness just to make it fancy is not the best idea.
Not sure which problems a large language model would solve.
The purpose of WinAppDriver is to be W3C WebDriver compliant (at least partially), not to tackle arbitrary UI automation problems.

@ChristoWolf have to disagree with all of your points-

While it is true that machine learning algorithms, including LLMs, can introduce a level of uncertainty due to their probabilistic nature, this does not inherently make them unsuitable for use with WinAppDriver. In fact, LLMs can be used to enhance the capabilities of WinAppDriver by providing natural language processing for complex automation tasks, interpreting user intentions, and generating robust automation scripts. The key is to use LLMs in a way that complements the deterministic nature of WinAppDriver, such as generating XPath selectors or assisting in the creation of test cases (I'm already doing this to great effect).

WinAppDriver's primary purpose may have been to provide a Windows application automation interface that complies with the W3C WebDriver standard, however this does not preclude its use with additional tools like LLMs. By integrating an LLM, you can streamline the test development process, automatically generate test cases based on natural language descriptions, and even provide intelligent suggestions for test improvements. This doesn't change the core functionality of WinAppDriver but rather extend its utility.

WinAppDriver may have been designed to work with predefined UI automation tasks, but the integration of an LLM could allow for a more dynamic approach to UI automation. For example, an LLM could understand the context of a UI and generate appropriate automation commands for WinAppDriver, drastically reducing the manual effort required to script complex interactions.

Overall, WinAppDriver + LLM seems to be winning combo, especially for test automation... if MS was interested.

@aronweiler ok so you are saying that my points are wrong because you would like LLM functionality?
Look, I think LLMs have great use cases, but a WebDriver server implementation is not it.
I think your ideas are absolutely sound, but should be part of a dedicated API and not WinAppDriver.
In any case, Microsoft has abandoned this project, so there will never be any such extensions to this implementation.
IMO the best we can do is to try to get somebody to notice this issue and at least communicate with us.

I find it interesting that MS seems to have abandoned this, because it fits very well with the AI initiatives that they are so deeply involved in. For instance, you could hook up tool calls allowing an LLM to easily use Windows applications without the inconsistency of integrating a vision component.

That might be a matter of business goals and priority. AI can span many areas, in the testing space, we have niche 3rd party players that have AI based automation tools. I'm guessing MS doesn't think it is worth the time to compete there. They focus on AI for other uses. If anything, they could just acquire those other niche companies and build upon them.
Things might be different if say Google or Apple took on AI for test tooling (Android test automation, XCode/iOS/macOS test automation, AI for SafariDriver, AI for ChromeDriver, etc.). Then I would think that would get MS's attention. If I'm not mistaken, I don't think Google nor Apple have taken on AI/LLM for their test tooling, at least with respect to WebDriver integration, have they? If one is interested in this area for AI, maybe ask around those company's user/dev communities to see if we can spawn some traction.

I guess it's time to ask the question again: what are people using in place of WinAppDriver?
Ranorex, TestComplete, FlaUI, etc.

After wasting LOTS of time (=money) with CodedUI and WinAppDriver and their stability issues, we went with Smartbear TestLeft. Rock solid, easy to use. The client nuget package still requires the "old" .NET Framework, which is the only annoyance.

Another comment to to pay your ATTENTION
@kat-y , please, share the latest news about WinAppDriver
People still waiting for

Install Nodejs and WinAppDriver
Install Appium 2+ version : npm i -g appium
Install appium windows driver : appium driver install --source=npm appium-windows-driver
run appium command
execute the scripts

Its working.

We know that this works, but it's a work-around for the fact that WinAppDriver has not seen any development for several years.

I have started writing a WebDriver2 implementation on top of FlaUI which might be interesting if somebody is looking for an alternative. It is still open for review: https://github.com/FlaUI/FlaUI/pull/594

I've just seen this blog post: https://devblogs.microsoft.com/dotnet/dotnet-maui-ui-testing-appium/. That talks of using WinAppDriver for MAUI apps 🤔.
I've added a comment to reference this issue and the lack of any Microsoft support. Maybe if everybody else could as well, it may help get some feedback.

I have started writing a WebDriver2 implementation on top of FlaUI which might be interesting if somebody is looking for an alternative. It is still open for review: FlaUI/FlaUI#594

Update: This has moved to a separate repo, https://github.com/FlaUI/FlaUI.WebDriver. See https://github.com/FlaUI/FlaUI.WebDriver/releases.

I've just seen this blog post: https://devblogs.microsoft.com/dotnet/dotnet-maui-ui-testing-appium/. That talks of using WinAppDriver for MAUI apps 🤔.
I've added a comment to reference this issue and the lack of any Microsoft support. Maybe if everybody else could as well, it may help get some feedback.

Good to know about this blog post. In the current comment exchange there, nice to see that the referenced WinAppDriver version (1.2.1) still works for the use case of that blog post. But unfortunate to hear the response of the blog author:

I can understand that that is not a good look. However, when using the version specified, all seems to work fine for what we’ve been using it for in the .NET MAUI codebase. Besides it not being updated and not looking maintained, is there anything specific you have a problem with?

Sounds like the blog author just cares for his use case only, and if it works for him, then it's "good enough" and no need to worry about other use cases where things might not work.

Note there is not even a real version 1.3, just a Release Candidate 1.2.99.
Since 2021...

Come on MS, any update on this one?

@kat-y  can we get any sort of update on this? need some sort of functioning driver.

@kat-y Are you still with MS?

This is obviously abandoned, sad as it is.
I recommend to instead use FlaUI or their FalUI.WebDriver.

Hi everyone,
Im using FlaUI with java, Im able to initialize a session and even use Actions class with FlaUI driver for using the keyboard and mouse.
But when trying to actually use the driver to find elements there is no success, I always get some kind of error.
Will appreciate any help, can be contacted at<EMAIL_ADDRESS>Thanks!

Hi everyone,
Im using FlaUI with java, Im able to initialize a session and even use Actions class with FlaUI driver for using the keyboard and mouse.
But when trying to actually use the driver to find elements there is no success, I always get some kind of error.
Will appreciate any help, can be contacted at<EMAIL_ADDRESS>or by linkedin https://www.linkedin.com/in/jonathan-giber-0747b071/
Thanks!

Hi @jonathangiber,
It would be better to address your issue in FlaUI repo so that anyone can help you.
Regards,
Igor

FlaUI is also going to be abandoned soon (even before its going to be fully implemented). Right now FlaUI is not completed and nothing is happening in this project since may.

I'm definitely not related to Smartbear.  It just works.
It has its price, but it saves us so much money.

FlaUI is also going to be abandoned soon (even before its going to be fully implemented). Right now FlaUI is not completed and nothing is happening in this project since may.

where did you hear this news? I was not aware, I don't see mentions on the github repos about it being deprecated/abandoned/archived.
But it is true that the WebDriver integration for FlaUI is currently "experimental", so it's not without bugs. But I believe the source code is there? If so, the community is welcome to help take over and fix or complete what's missing.

FlaUI is also going to be abandoned soon (even before its going to be fully implemented). Right now FlaUI is not completed and nothing is happening in this project since may.

As the primary author of FlaUI.WebDriver, I can confirm that FlaUI.WebDriver is not "abandoned" (I don't know about FlaUI itself but did not hear any news about that too).
I agree that development on FlaUI is not very active but it has a great and quite up-to-date technology stack and it is open source. So I would encourage anyone to evaluate it and contribute to it.

Thank you for commenting this thread @aristotelos
We (the Appium team) would also be happy to incorporate any webdriver-compatible server to replace WAD, FlaUI included. We have been also actively looking for a person who could help with further maintenance, triage, and development/bugfixes for the replaced server part. Unfortunately we observed zero interest in that from the community. Basically, many people would like to use this free instrument to automate their tests, but very few (if any) would like to contribute back 🤷

@mykola-mokhnach where to contribute to windows desktop applications?  There is value in contributing because my test code will continue to work in the next framework.

@liljohnak

where to contribute to windows desktop applications

sorry, I maybe did not express it properly. I mean contributing to open-source alternative WAD implementations built on top of W3C webdriver interface, for example FlaUI, which is mentioned above, or https://github.com/imsardine/winappdriver or https://github.com/kfrajtak/WinAppDriver or https://github.com/licanhua/YWinAppDriver

...We have been also actively looking for a person who could help with further maintenance, triage, and development/bugfixes for the replaced server part. Unfortunately we observed zero interest in that from the community. Basically, many people would like to use this free instrument to automate their tests, but very few (if any) would like to contribute back 🤷

That kind of dedication for a single person / lead / point of contact, to take on I assume is a lot of responsibility and extra personal time for this kind of work/maintenance. Unless there happens to be some corporate/employer sponsorship for the work. Someone that would want to take on that role without sponsorship must really be passionate about the project/software or the field of work / industry.
For occasional, intermittent, contributions from anyone in the community, that I can see is easier for one to be a contributor.
On a quirky side note, it would be nice if MS could sponsor whoever helps (as maintainer) with replacing WAD integration with Appium. Given WAD seems abandoned, this could be a nice way for them to give back to the community. More helpful or better for sponsorship if the person happens to be from MS as well.

I successfully upgraded to selenium 4 replacing winappdriver to FlaUI web driver (https://github.com/FlaUI/FlaUI.WebDriver) thanks to @aristotelos for adding all the necessary capabilities

@jonathangiber sounds great, I'll also do the switch soon!


[Bug]: Screen tearing and lagging

Operating System
Windows 10
BG3 Mod Manager Version
<IP_ADDRESS>
BG3 Game Version
Full Release Patch 5 Hotfix 12
Bug Summary
I have for sure figured out that its not a single mod or my trainer or anything else. Only when I run my game through this program do I get reeeaallly bad screen tearing and lag. I've tried fixing it but I'm out of ideas. This only started happening since patch 5.
Links
No response

Also, these appeared and I don't know how to remove them. They say they don't even exist or have a file location.


[BEAM-10435] Add LOOPBACK mode Java ValidatesRunner test suite for ULR

This just adds the additional gradle target. TODO: add continuous Jenkins runs. It looks like it takes long enough it has to be a postcommit.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

https://gradle.com/s/r6phv7qxmg6so

Noting that the whitespace check is pulled in by applyPythonNature which is too big a hammer but refactoring will be some work. And it seems ./gradlew applySpotless does not eliminate it even though we could turn it on for the groovy.

Pushing whitespace-only fixup


B51792

Fixes #51792

Something wrong with Github -- why does it add a bunch of upstream commits???


Why vid + 0.5

https://github.com/sugi-cho/Animation-Texture-Baker/blob/cec8861d88f757f9b9f21ee300f823e76b78cec7/Assets/AnimationBaker/Shaders/TextureAnimPlayer.shader#L52
Hello. thanks for your code.
I read your code and it works perfectly.
now. I don’t understand a bit.
float x = (vid + 0.5) * ts.x;

vid(SV_VertexID) is the index of vertex.  it's 0, 1, 2, 3 .... (vertexCount - 1)
ts.x is 1 / textureWidth
my question:
why vid + 0.5?
Please give me a hint. thanks.

hi, good question.
using texture.filterMode = Bilinear for interpolation of each frames.
The y direction may be interpolated, but the x direction needs to be the center of the texel.
uv.x = (vid + 0.5) / textureWidth
is center value of texel, which is position of vertex.


Styling guide proposal

Styling
Default widgets in react-instantsearch comes with some styling already applied and loaded.
When styling components, you can decide to either extend or completely replace our default styles, using CSS classes or inline style.
All widget accepts a theme prop and the theme keys are defined in the widget docs.
CSS classes styling
Reusing our class names
Show how to style by adding a style.css and redefining our BEM classes
Providing your own classes
theme={yourClasses}
Extending the default theme
theme=extendTheme(defaultTheme, yourClasses)
Inline styling
Providing inline style
theme={inlineStyles}
Extending our default theme
theme=extendTheme(defaultTheme, inlineStyles)
react-themeable
The theme={} props accepts any parameter that react-themeable support...
Tooling
Only here we can start talking about some tools we recommend as for CSS modules
CSS modules with webpack
You can use webpack css modules on your side and still extend our themes.
Small js example, no need to explain how to configure webpack.
Localized CSS with babel
Default themes of react-instantsearch are built with babel.. You can use it with your own code, and load css with insert-css.
Small js example, no need to explain how to configure babel.
insertCss, insertStylesheet
Talk about insert-css and insert-stylesheet modules

We should take this as an opportunity to correct our BEM syntax which is currently wrong.
Current is:
{block}--{element}__{modifier}

But really should be:
{block}__{element}--{modifier}


Page up goes only one line up in filtered view

If I've filtered view (pretty sparse filter) and cursor is at the first line of the visible data, page up goes only one line up (similar to arrow up).

I've tried to reprocude can't I can not get it to happen, a source code review did also not turn up a problem. Get you provide the filter set? (export the set?)

close due to no response


Add rudimentary device emulation to Adaptive Cards Designer

Related Issue
This PR adds the functionality discussed in this internal document regarding support for designing cards for mobile devices.
Description
This PR adds a dropdown menu for selecting a device to emulate, which changes at least the width of the card container in the preview part of the designer.

How Verified
We will consult with internal teams to establish an acceptable means of verification.
Microsoft Reviewers: Open in CodeFlow

I should point out, as a general note, that the code quality tooling introduced in #6815 is no longer running.
When setting up for this project, the prepare script did run, and Husky reported successful installation, however the pre-commit hook did not run. It looks as if it hasn't run in some time, since running Prettier manually overwrites much of the code, and I needed to temporarily disable ESLint in my IDE since extant linting issues were crowding out other issues.
I think maybe #6657 and #6757 should be reopened.

@thure I believe you will also need to update the website code in order to add the default list of device emulations to the designer. That is likely why the selector doesn't appear in the test site.

@thure also, and I'm not sure it's related to your changes (but I thought I'd mention just in case), the Outlook and Viva apps don't work as they should anymore. For example, Outlook looks like this now:

When it should look like this:

@licanhua I'm seeing issues on the test site. I don't think we should merge the code in that state?

@dclaux Got it, investigating now. Will implement the solutions we discussed offline.

@thure I'm finding that the device emulation doesn't work well for host applications that impose their own width, namely WebChat, Teams, Federated search and Berlin.

@dclaux I've implemented the changes we discussed offline. Device emulation is now only enabled for hosts that don't currently specify a specific width for the card host.

@thure  thanks - I do have a nit though. I think it should be the responsibility of the HostContainer implementation to say whether or not it supports device emulation, as opposed to being a parameter passed to the constructor. The reason for that is you could very well pass true to the Viva container constructor, the device emulation selector would be enabled but it wouldn't work properly.
I think you should introduce this:
class HostContainer {
    ...
    get allowDeviceEmulation(): boolean {
        return false;
    }
    ....
}

And override in the HostContainer implementations that do actually support device emulation, e.g:
class OutlookContainer extends HostContainer {
    ...
    get allowDeviceEmulation(): boolean {
        return true;
    }
    ....
}

@dclaux I've made the changes you suggested.

thure thank you very much :)


React-native-web with QrCode-Scanner

hello, I am trying to put the qrcode scanner on react-native-web, but can't get it to work.
I get this error:
ERROR in ../node_modules/react-native-qrcode-scanner/index.js 68:6
Module parse failed: Unexpected token (68:6)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     cameraType: 'back',
|     notAuthorizedView: (
>       <View
|         style={{
|           flex: 1,

Build details?
 "@react-native-community/masked-view": "^0.1.10",
    "ios-deploy": "^1.11.4",
    "react": "^17.0.2",
    "react-native": "0.64.0",
    "react-native-camera": "^3.43.9",
    "react-native-easing-keyframes": "^1.0.2",
    "react-native-gesture-handler": "^1.10.3",
    "react-native-keyframes": "^2.0.1",
    "react-native-qrcode-scanner": "^1.5.4",
    "react-native-reanimated": "^2.1.0",
    "react-native-safe-area-context": "^3.2.0",
    "react-native-screens": "^3.1.0",
    "react-native-sound": "^0.11.0",
    "react-native-web": "^0.16.1",
    "react-native-web-sound": "^0.1.1"
    ```

insert this code in web.config.js
path.resolve(appDirectory, 'node_modules/react-native-qrcode-scanner'),


Fix checkpoint to avoid buffer has been deleted or donated

The copying of experiment (-state) needs to be improved (at least for some implementation of the experiment class). E.g. this is the case for https://github.com/deepmind/digraph_transformer
Python copy.copy only creates a shallow copy. However, in my case, the "snapshot" is a ConfigDict of ml_collections where one entry is the experiment instance. A shallow copy then does not copy the experiment nor does it snapshot the arrays contained in the experiment. Not sure if my solution is the most elegant one; however, applying copy.deepcopy also has some downsides.
For example, if running in jaxline_mode=train_eval_multithreaded the solution was insufficient for me as I occasionally encountered jaxlib.xla_extension.XlaRuntimeError: INVALID_ARGUMENT: Invalid buffer passed to Execute() as argument 0 to replica 0: INVALID_ARGUMENT: Buffer has been deleted or donated.

Hi, any news on this? Is the issue clear, or has it been resolved differently?

As nobody is assigned to this issue and I am not sure who is being notified, I now ping you @malcolmreynolds (author of last commit)

I can confirm that the issue still persists with the current version

Sorry I'm afraid I haven't worked on jaxline in quite some time so I won't be able to assist. Re-assigning to @michaeloneill who I believe is still maintaining the project.

Hi @michaeloneill, I quickly wanted to check on the status

Hi @michaeloneill, I quickly wanted to check on the status

Did you try my suggested edit that i replied to your previous comment with? I'd be happy to make that change if it works for you.

@michaeloneill I have incorporated your suggested changes into this pull request and am wondering if you want to merge it or if there is still something missing.

Hi there i've now submitted a fix along the lines we've talked about above, but as part of a wider cleanup/refactor. This should all be working now! Closing this PR.


Report last fix into dist/

Hello :) When you have time, could you please report your last fixes into the generated js files (into the dist/ folder) please ? thanks ^^

Thanks for reminding, done!


Saga: StateMachine ServiceTask supports asynchronous execution

Ⅰ. Describe what this PR did
Saga: StateMachine ServiceTask supports asynchronous execution
Ⅱ. Does this pull request fix one issue?
#1843

Codecov Report

Merging #1844 into develop will increase coverage by 0.09%.
The diff coverage is 33.33%.

@@              Coverage Diff              @@
##             develop    #1844      +/-   ##
=============================================
+ Coverage      54.95%   55.05%   +0.09%
- Complexity      2352     2356       +4
=============================================
  Files            421      421
  Lines          14266    14272       +6
  Branches        1682     1712      +30
=============================================
+ Hits            7840     7857      +17
- Misses          5681     5686       +5
+ Partials         745      729      -16

Impacted Files
Coverage Δ
Complexity Δ

.../statelang/parser/impl/ServiceTaskStateParser.java
83.33% <33.33%> (-16.67%)
2 <0> (ø)

...ga/statelang/domain/impl/ServiceTaskStateImpl.java
66.66% <33.33%> (-3.71%)
14 <1> (+1)

...server/store/file/FileTransactionStoreManager.java
59.21% <0%> (-0.99%)
29% <0%> (ø)

...o/seata/server/coordinator/DefaultCoordinator.java
50% <0%> (+0.4%)
28% <0%> (+1%)
:arrow_up:

...in/java/io/seata/server/session/GlobalSession.java
85.02% <0%> (+0.48%)
68% <0%> (+1%)
:arrow_up:

...ource/sql/struct/cache/AbstractTableMetaCache.java
91.17% <0%> (+2.94%)
11% <0%> (+1%)
:arrow_up:

...rotobuf/convertor/RegisterTMResponseConvertor.java
84.84% <0%> (+3.03%)
3% <0%> (ø)
:arrow_down:

...rotobuf/convertor/RegisterRMResponseConvertor.java
84.84% <0%> (+3.03%)
3% <0%> (ø)
:arrow_down:

...otobuf/convertor/GlobalBeginResponseConvertor.java
96.96% <0%> (+3.03%)
3% <0%> (ø)
:arrow_down:

...obuf/convertor/BranchRollbackRequestConvertor.java
96.42% <0%> (+3.57%)
3% <0%> (ø)
:arrow_down:

... and 9 more


Update LAB_AK_03_Implementing_failover_clustering.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by cjpluta on behalf of MOC Labs Review


Running in docker

Hi,
I have node red running in a docker container and want to use your TTS ultimate solution for some massages triggered by events. Somehow I do not get the sound to the speaker. I have fixed ip addresses for the Sonos devices as well as for the Raspberry running docker. The status  in node red is „connected“ but when I run your demo flow with „hello world“ I hear nothing. Sonos playing music is interrupted. I‘m using google without authentication. Seems the sound file is not available. Do you have any Tipps what I can do? Where should I find the sound files?
Thanks for some insights
Chris

Hi running docker on a rpi is always problematic.
Check the port forwarding by looking at the Readme page on github.
Then check whether the user running node-red has rights to write to the filesystem.


Bug: response_time PacketLossPct reporting nonsense values

I ran into this in a customer account and was able to duplicate it in my test environment, with reponse_time: true globally  kentik.ping.PacketLossPct seems to always be returning  -9223372036854776.  I would expect this should be 0 in the places I tested it.

This is an artifact of when the ping is not getting returned. Likely will be fixed by setting this env var: KENTIK_PING_PRIV=true
This changes ping from UDP to ICMP based packets.

Hi @i3149 is this a change that the customer would make in their environment, or should we wait for a new container version to be released?
Also, I just want to confirm how this works... so the desired output = 0.. and if the returned value is more than 0, that means the node is down / not responding to ping ?


Remove the project type when submitting updates to pyxis

Fixes #766
The issue listed above results from our CertProject struct, which contains the project type. Certain values for the project's type cannot be set via the external API, but our submission included them, resulting in a rejection from the API.
This patch adjusts the CertProject.Type key such that it uses omitempty, and on update calls, we zero out the value of CertProject.Type before we submit.
We'll want to cut a beta release after this merges, which can then be tested by the blocked partner.
Signed-off-by: Jose R. Gonzalez<EMAIL_ADDRESS>

Coverage increased (+0.01%) to 84.465% when pulling a4926d255597f5c22daa0f780624ee248b56ccc8 on komish:fix-submit-patch into 8a685ae59888293876e6a61255dc997b5b8db276 on redhat-openshift-ecosystem:main.

Changes unknown
when pulling a4926d255597f5c22daa0f780624ee248b56ccc8 on komish:fix-submit-patch
into ** on redhat-openshift-ecosystem:main**.


Add git amend --reparent option

cc @claytonrcarter

Sorry to be late here. I glanced at this earlier and it looked good to me, fwiw.

@claytonrcarter no worries, I was just trying to keep you up to date in case it affected your --fixup PR 🙂


Unable to send message with key when Using Reactive handlers

@olegz @sobychacko I am trying to use reactibe handlers as below. How could we set a key for the output message when using reactive handlers
@StreamListener
    @Output(TEST.OUTPUT)
    Flux<String> processMessage(@Input(TEST.INPUT) Flux<String> event) {
        event
        .log()
        .map{ event1 ->
                return objectMapper.writeValueAsString(formatData(event1))
        }
    }

@VasuBhaskar Try using this pattern. This way, the outgoing Message will have a header entry called key.
@EnableBinding(Processor.class)
....
....
@StreamListener
    public void processMessage(@Input(Processor.INPUT) Flux<String> event,
                        @Output(Processor.OUTPUT) FluxSender output) {
      output.send(
        event
         .log()
         .map{ event1 ->
                MessageBuilder. withPayload(objectMapper.writeValueAsString(formatData(event1)))
                                          .setHeader("key", "foo")
                                          .build();
        }
    }

Please bear in mind that, for questions like this, try to use Stack Overflow or gitter. Use GH only for filing bug reports or requesting new features.  Thank you.

I am closing it given this is a question and as Soby  pointed out should be handled through appropriate channels to better benefit the community.


OpenAPI demo option for no-auto and events

Adds event logger to agent.py that is activated when running run_demo with the --events option.
Adds a --no-auto option to run_demo that deactivates --auto-... arguments in agent.
Updates OpenAPI demo documentation for invitation scenarios when --no-auto option is set
PR for: #361

Codecov Report

Merging #375 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #375   +/-   ##
=======================================
  Coverage   89.14%   89.14%
=======================================
  Files         236      236
  Lines       11222    11222
=======================================
  Hits        10004    10004
  Misses       1218     1218

Ran the demo and it looks good.  There are still some revisions to be made to the tutorial but it's looking good.
@amanji - is this ready for merging?
Thanks!
Updates I'm planning:

use the --events and --no-auto in this demo
make the description assume those options are set (vs. the two options)
direct the user to watch the webhooks that we displayed on the terminal
instead of using the /send endpoint for the credential, start with the /offer and walk through the whole thing
Overall - adjust the lay tutorial layout to separate the steps to execute (and copy/paste items) from the commentary.

Looking good!

Functionally it’s complete, but the docs need to be updated (as you mentioned). Should those changes be made first before merging?

If the code is fine, I can update the docs.  Easier to do after merging.
I'll do that and we can go from there.
On Tue, Feb 18, 2020 at 4:54 AM Akiff Manji<EMAIL_ADDRESS>wrote:

Functionally it’s complete, but the docs need to be updated (as you
mentioned). Should those changes be made first before merging?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger/aries-cloudagent-python/pull/375?email_source=notifications&email_token=AAHYRQSHWKKRTBYHK2EO4ZTRDPLBRA5CNFSM4KV7M24KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMB3PSQ#issuecomment-587446218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHYRQRZ3W7X4R3HF2WRQC3RDPLBRANCNFSM4KV7M24A
.

--
Stephen Curran
Principal, Cloud Compass Computing, Inc. (C3I)
Technical Governance Board Member - Sovrin Foundation (sovrin.org)
*Schedule a Meeting: *https://calendly.com/swcurran
https://calendly.com/swcurran


Add npx to set this up

I have to keep accessing the README for the required packages and for the .eslintrc, for projects not created with gev. Like gev, this could have a npx to set up the devDeps and the .eslintrc. If .eslintrc already exists, it will warn the user and prompt for confirmation. -f/-y will do it without prompting.
Also, as gev, it would check for latest version.

Also, there could be a npx eslint-config-gev update to install the all the latest eslint/plugins versions. It could get the devDeps list, filter for the eslint related packages, and npm i -D them@latest


Update README.md

The sentence compares SQL engines and logic programming engines, so I change 'enginers' to 'engines'.

Thank you!


[BUG] Camel case is not supported for application properties(keys)

Library name and version
Azure.Messaging.ServiceBus, Version=<IP_ADDRESS>
Describe the bug
when created
service bus message with application properties
serviceBusMessage.ApplicationProperties.Add("ApiVersion", 1);
serviceBusMessage.ApplicationProperties.Add("CreateTimestamp", dateNow);
and we send it to topic (on azure topic we still have all keys in lowercase) so we have

so, please fix it, for our client is very needed to have camelCase
Expected behavior
camelCase for aplication properties on azure service bus explorer topic message
Actual behavior
lowercase for aplication properties on azure service bus explorer topic message
Reproduction Steps
ServiceBusMessage serviceBusMessage = new ServiceBusMessage(message);
serviceBusMessage.ApplicationProperties.Add("EventEntity", "LoyaltyAccount");
serviceBusMessage.ApplicationProperties.Add("ApiVersion", 1);
serviceBusMessage.ApplicationProperties.Add("CreateTimestamp", dateNow);
await sender.SendMessageAsync(serviceBusMessage);
Environment
No response

Hi @androsovandrii.  Thank you for reaching out and we regret that you're experiencing difficulties.  Both the Service Bus client and service treat the application properties of a message as an opaque set of data; neither inspects nor alters the items provided by the application, including changing capitalization of keys.   I'm not sure what tool you're using to visualize the message in the image above, but I'm unable to reproduce what you're seeing in the Azure portal nor in code.  (details below)
Can you verify that you're seeing the case changed when you attempt to read back the message that you published directly in your code?   We'd also appreciate if you could help us understand a bit more about your architecture - is your code reading directly from a subscription on the topic where the message was published, or are there any intermediaries doing processing work before the message is read back?
Repro Attempt details
await using var client = new ServiceBusClient("<< CONNECTION STRING >>");
await using var sender = client.CreateSender("test");

var message = new ServiceBusMessage("dummy");
message.ApplicationProperties.Add("EventEntity", "LoyaltyAccount");
message.ApplicationProperties.Add("ApiVersion", 1);
message.ApplicationProperties.Add("CreateTimestamp", DateTime.UtcNow.ToString());

await sender.SendMessageAsync(message);

The portal shows me the properties with the casing preserved:

As does reading the message back in code:
await using var receiver = client.CreateReceiver("test", "read");

var readMessage = await receiver.ReceiveMessageAsync(TimeSpan.FromMinutes(1));
await receiver.CompleteMessageAsync(readMessage);

readMessage.Dump();

@jsquire yes you are right but as you see

@jsquire yes you are right but as you see "The portal shows me the properties with the casing preserved:" - apiversion - not apiVersion or ApiVersion, and evententity no eventEntity or EventEntitym why so?

Unfortunately, I can't speak for the portal, as it isn't part of the Azure SDK.   Am I correct in interpreting your response as confirmation that you're not seeing the case change when reading messages back in code using the Service Bus client library?
For the portal question, unfortunately, there is no GitHub instance for me to transfer the inquiry to since the portal is not an open source product.   Your best path for seeking that answer would be to open an Azure support request.

@jsquire , thank you very much for help, yes I think it's portal issue(or some configuration topic)
thank you for cooperation

I regret that we're not able to help dig into the portal behavior, but I'm glad to see that it's just a display issue.   I'm going to mark this as addressed and close things out.   Please feel free to use the "/unresolve" command if you'd like to continue the discussion.


Update conan version to latest (1.45.0)

The update is needed to fix our oss-fuzz build due to some breaking
changes / incompatibilities in (at this point unmaintained versions of)
markupsafe and jinja2. Upgrading to the latest conan version also
upgrades the version used for these dependencies.
Tested: Built oss-fuzz Orbit project locally with these changes.
Bug: http://b/220807495

Not sure if these are all the places where I have to change this. Let me know if I missed anything.
Have only tested the oss-fuzz build, let's see if our presubmits pass.
Will test the oss-fuzz build again, once all looks good here.

Unfortunately the conan version for the CI is defined in a different place which you need to adjust as well: https://github.com/google/orbit/blob/8f640e57f384fdd495463fd54906541e96b26203/kokoro/builds/build.sh#L122

Unfortunately the conan version for the CI is defined in a different place which you need to adjust as well:
https://github.com/google/orbit/blob/8f640e57f384fdd495463fd54906541e96b26203/kokoro/builds/build.sh#L122

Ah, thanks. Done.

Looks great. But I just realized there are two more places to adjust (Sry for that):
https://github.com/google/orbit/blob/8f640e57f384fdd495463fd54906541e96b26203/third_party/conan/scripts/build_and_upload_dependencies.sh#L22
https://github.com/google/orbit/blob/8f640e57f384fdd495463fd54906541e96b26203/third_party/conan/scripts/sync_dependencies.sh#L16

orbit/third_party/conan/scripts/build_and_upload_dependencies.sh

My bad, should have done a search for 1.40.3 to find other locations. Should be fixed now.
Added a note in the commit message that the 1.40.3 version in the remaining location (third_party\conan\docker\Dockerfile.clang11_opengl_qt) needs to be updated along with
the docker image.

I reran the oss-fuzz build and it succeeds on the branch with this change here (and it fails on our main branch). So, this should fix the issue.

I reran the oss-fuzz build and it succeeds on the branch with this change here (and it fails on our main branch). So, this should fix the issue.

Awesome. Thank you a lot for fixing this!

Thanks a lot for the review and help, @beckerhe


Group::load() and save() should return a success value

The lack of a success return value was a mistake in our design.

OK, that opening comment was off-target.  Group::load() and save() wrap Conduit's relay::io::load() and save().  Those functions use exceptions to report problems.  If it didn't throw an exception, it went OK.  In Sidre, we re-wire "throw exception" to "call a function that calls a slic logging function."
Maybe what we need to do is discuss this design choice in the documentation and example codes.  Possibly we could have the handler functions store an error state and message, sort of "my very own sidre errno", with getters to make this state accessible to C and Fortran.  As @cyrush pointed out, this does tend to get messy.

Try to find time to discuss options as a group.


[ptp/protocol] add more tests

Summary
New tests, bringing the coverage of ptp/protocol up to respectable 81%.

Wrote tons of tests
Fixed good number bugs.
Added fuzzing test

Test Plan
> go test github.com/facebook/time/ptp/protocol/... -cover -fuzz='.*' -fuzztime=1m
fuzz: elapsed: 0s, gathering baseline coverage: 0/123 completed
fuzz: elapsed: 0s, gathering baseline coverage: 123/123 completed, now fuzzing with 24 workers
fuzz: elapsed: 3s, execs: 332506 (110832/sec), new interesting: 0 (total: 123)
fuzz: elapsed: 6s, execs: 727663 (131189/sec), new interesting: 0 (total: 123)
...
fuzz: elapsed: 1m1s, execs: 2145136 (0/sec), new interesting: 0 (total: 123)
PASS
coverage: 81.4% of statements
ok      github.com/facebook/time/ptp/protocol   61.145s

Codecov Report

Merging #182 (267ef97) into main (5120aed) will increase coverage by 3.64%.
The diff coverage is 46.96%.

@@            Coverage Diff             @@
##             main     #182      +/-   ##
==========================================
+ Coverage   54.56%   58.21%   +3.64%
==========================================
  Files          84       84
  Lines        7499     7560      +61
==========================================
+ Hits         4092     4401     +309
+ Misses       3011     2722     -289
- Partials      396      437      +41

Impacted Files
Coverage Δ

ptp/protocol/unicast.go
58.38% <8.69%> (+11.04%)
:arrow_up:

ptp/protocol/protocol.go
78.35% <14.28%> (+3.90%)
:arrow_up:

ptp/protocol/ptp4l.go
65.13% <33.33%> (+7.59%)
:arrow_up:

ptp/protocol/types.go
87.27% <100.00%> (+17.31%)
:arrow_up:

timestamp/timestamp_linux.go
63.51% <0.00%> (-2.03%)
:arrow_down:

ptp/protocol/management.go
43.79% <0.00%> (+7.18%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Improve performance of dependency resolution on worker constrained hosts

Unconstrain dependency metadata and artifact resolution instead let the limits of the underlying HttpClient pool impose limits on per-client concurrency.

Fixes #5328
Context
On environments with limited CPU cores dependency metadata and artifact resolution is unnecessarily constrained the the maximum number of workers. The work is network and disk IO bound and the underlying HttpClient imposes appropriate request concurrency limits per route.
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@DanielThomas Hey, could you rebase this to the latest master to resolve the conflict?
The plan would be then to merge this for Gradle 7.1

@ljacomet done!

@bot-gradle test RFM

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test and merge

Your PR is queued because #17093 is being built.

OK, I've already triggered a build for you.

OK, I've already triggered a build for you.


600-series: Allow extended boluses with 0 normal

The Medtronic 600-series driver simulator previously discarded
any bolus events with a normal value of 0.
However, this meant that extended boluses with a zero component
were also discarded. This fixes that bug.

Fixes https://trello.com/c/s67Yc2qP (for 600-series driver)

@gniezen - FYI - this issue will also exist for the 5/7-series driver. See https://github.com/tidepool-org/chrome-uploader/blob/develop/lib/drivers/medtronic/medtronicSimulator.js#L806

In the 5/7-series driver, if there's no normal portion, it's recorded as a square bolus instead (https://github.com/tidepool-org/chrome-uploader/blob/develop/lib/drivers/medtronic/processData.js#L373-L375). Conversely, if the extended portion is zero we record it as a normal bolus (https://github.com/tidepool-org/chrome-uploader/blob/develop/lib/drivers/medtronic/processData.js#L373-L375).
Do you want to duplicate this behaviour in the 600-series driver, or do you prefer to still record it as a dual bolus? Looks like there is precedent for recording a zero normal portion, if you look at the notes at http://developer.tidepool.org/data-model/device-data/types/bolus/dual-square.html#normal

 Backend Regression (?) - Dual Wave Boluses do not store correctly on the backend.


libpqxx: 6.4.5 -> 7.5.2

Motivation for this change
I disabled building documentation and removed related dependencies because it was not working and it does not appear that it was working before.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126996 at 535c5c39 run on aarch64-linux 1

3 packages failed to build:

hydra-unstable
python38Packages.tiledb
python39Packages.tiledb

4 packages built successfully:

cloudcompare
libpqxx
pdal
tiledb

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

This breaks hydra-unstable


We should have a license

We should associate an open source license with this.

I was going to add one but I didn't know which one. Which one should we use?


Qz

Implementation of implicit QZ
small parts of the implementation depend of my SVD pr (the normalization of 2x2 blocks). I'll fix those later.
An important part is also the calculation of the generalized eigenvalues of a 2x2 pencil. I didn't really feel like implementing that at the moment so i'll leave that for a later PR.

This should be ready to merge now


[fix] demo seed style

Coverage decreased (-2.5%) to 81.769% when pulling fb73672ec409599e7feadf307a74822680059dfa on fix-cms-seed into 0bdfb97e4f596f999d09fba718d0503aad8fff62 on master.


refactor banner and responsive banner component logic

The components should delegate logic to a component service

✔ Components do not have logic inside
✔ Banner and responsive banner still works as before


Stack trace in mangadex

# manga-py version: 1.3.20
pipenv run manga-py --cbz --zero-fill --rename-pages --destination Manga/ https://mangadex.org/manga/24022/maou-no-mama-ni-narundayo
  File "~/.local/share/virtualenvs/0_bin-S-IZrhuG/lib/python3.5/site-packages/manga_py/parser.py", line 42, in start
    self.provider.process(self.params['url'], self.params)
  File "~/.local/share/virtualenvs/0_bin-S-IZrhuG/lib/python3.5/site-packages/manga_py/provider.py", line 67, in process
    self._storage['manga_name'] = self.get_manga_name()
  File "~/.local/share/virtualenvs/0_bin-S-IZrhuG/lib/python3.5/site-packages/manga_py/providers/mangadex_com.py", line 35, in get_manga_name
    name = self.html_fromstring(url, 'h3.panel-title', 0)
  File "~/.local/share/virtualenvs/0_bin-S-IZrhuG/lib/python3.5/site-packages/manga_py/provider.py", line 191, in html_fromstring
    return self.document_fromstring(self.http_get(url, **params), selector, idx)
  File "~/.local/share/virtualenvs/0_bin-S-IZrhuG/lib/python3.5/site-packages/manga_py/base_classes/static.py", line 24, in document_fromstring
    result = result[idx]

I will check it. Thank you!

Please, check 1.3.21

Works OK in manga-py version 1.3.21 :+1:

Ooops :boom:
Downloads Ok, but stores it without the comic name:
find
.
./Manga
./Manga/vol_001-1-English.cbz

It should be something like: ./Manga/maou-no-mama-ni-narundayo/vol_001-1-English.cbz

Works OK in manga-py version 1.3.22 :+1:

Seems that I'm the "oficial" tester :laughing:

Not much a music person, but I liked this when the anime aired:
https://www.youtube.com/watch?v=RRNFEECKEgU

Angel beats is amazing! (^_^)


Update README.md with customized url

Hi! Please resolve conflicts

Hi, I think I've taken care of it!

My remote repo has not been updated for a quite of time, so I was not able to just change my own line. Can I close this pull request, and fork the latest repo and resubmit a new pull request?


Error Handling

Imagine what happens if I provide a wrong api key?
There should be a onError handler so that I can explicitly see if my api key is wrong? like I refreshed my tenor api key.

Hey! In case of any internal errors including bugs, tenor outages or invalid/restricted api key an error is always printed to console. There is also error boundary so, picker just doesn't render on error. I dont see the need for onError property. Realistically, it should never be called and don't have any use.

Well, the error shows in the console but in case I mistakenly refresh my API key, or my account gets suspended or something like that (the worst-case scenario), this error could affect the build version of my web app. In that case, I want to make an alert to the end user that the tenor API key has been changed so that they address that issue to me.

Hey! In that case, you should use sentry or any other similar monitoring software. The soluution that you are talking about is not-standard and won't be implemented.


Could not find or load the Qt platform plugin "xcb"

I get this when running pageres-cli minetest.net on an Antergos (based on Arch Linux) system:
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: This application failed to start because it could not find or load the Qt platform plugin "xcb".
    at LineStream.<anonymous> (/usr/lib/node_modules/pageres-cli/node_modules/screenshot-stream/index.js:78:14)
    at emitOne (events.js:96:13)
    at LineStream.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:172:18)
    at LineStream.Readable.push (_stream_readable.js:130:10)
    at LineStream.Transform.push (_stream_transform.js:128:32)
    at LineStream._pushBuffer (/usr/lib/node_modules/pageres-cli/node_modules/byline/lib/byline.js:123:17)
    at LineStream._transform (/usr/lib/node_modules/pageres-cli/node_modules/byline/lib/byline.js:114:8)
    at LineStream.Transform._read (_stream_transform.js:167:10)
    at LineStream.Transform._write (_stream_transform.js:155:12)

I already have xcb packages installed on my system, but I'm not sure if they're related.

Seems like PhantomJS wasn't properly installed. Can you remove pageres-cli and reinstall?

Seems like PhantomJS wasn't properly installed. Can you remove pageres-cli and reinstall?

I just tried (npm uninstall -g pageres-cli then npm install -g pageres-cli), without success. I get the same error.

It's a problem with PhantomJS on your system. Not much we can do about it.
Try opening an issue at https://github.com/Medium/phantomjs


Does DeepLIFT support regression output instead of classification?

I am interested in learning about the impact of input features on a continuous output value. Thus my final layer is a Dense layer with a linear activation function.
Is there anything that I need to do differently from the examples provided to make DeepLIFT work for my case?

Just make sure to set the target_layer_idx to be the index of the very last
layer (i.e. -1). In the examples involving binary classification models, we
typically set that index to be -2, which corresponds to the input to the
sigmoid nonlinearity. This is to avoid artifacts caused by saturation of
the sigmoid. In your case, however, your last layer is linear, so you can
set the target_layer_idx to -1.
On Wed, Sep 25, 2019 at 9:58 PM tsjain<EMAIL_ADDRESS>wrote:

I am interested in learning about the impact of input features on a
continuous output value. Thus my final layer is a Dense layer with a linear
activation function.
Is there anything that I need to do differently from the examples provided
to make DeepLIFT work for my case?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kundajelab/deeplift/issues/89?email_source=notifications&email_token=AARSFBXVQTT7E7JOGI2PFJTQLQ6NPA5CNFSM4I2VAXQKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HNY5Z2Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AARSFBSGYDTLGKF6EOVE6EDQLQ6NPANCNFSM4I2VAXQA
.

--
Sent from my phone, please excuse brevity/typos


LDAP login name casesensesitvity can easily be a show stopper!!!

Bug description
With Authentication over LDAP, it is possible to get a new user by change random characters to Uppercase and/or Lowercase. Example:
Login "smith" is configured as Admin
Login "Smith" is configured as User
Login "sMith" is configured as User
Login "SmIth" is configured as User
Login "SmiTh" is configured as User
They are all Authenticated correctly, but the System thinks they are different users
Expected behavior
Upper and Lowercase should make no difference for a username
Portainer Logs
Just try with OpenLDAP, let me know if you really need them.
Steps to reproduce the issue:

Login with your normal user, no changes.
Logout
Login with you normal user but put one random letter to Uppercase
Have a look under Users, you have new ones with restriced rights

Technical details:

Portainer version: 2.0.0
Docker version (managed by Portainer): 19.03.12
Platform (linux): Debian 10
Command used to start Portainer (docker run -d -p 8000:8000 -p 9000:9000 --name portainer --restart unless-stopped -v /var/run/docker.sock:/var/run/docker.sock -v portainer:/data portainer/portainer-ce:2.0.0-alpine):
Browser: Firefox 80

Additional context
Only applies for LDAP accounts, the admin account created on setup isn't hurt

Closing this issue as this problem should be solved when we fix https://github.com/portainer/portainer/issues/3580


docs/openstack: adds content for Ingress with MetalLB

What this PR does / why we need it:
Adds content for Ingress on the OpenStack platform, with MetalLB.

Note about this doc, we'll still need to have https://github.com/openshift/hypershift/pull/4423 finished to have Ingress working but this will be sorted out. I think this can be merged anyway.

/lgtm
/hold
Feel free to cancel the hold if you think we don't need to wait for the other PR

/hold cancel


fpgad-vc: graceful shutdown models super-rsu flow

Update the method used to remove the device driver to that of super-rsu:

Write 1 to the device's reset node.
Write 1 to the remove node of the root bridge's child. (removes
all VC devices)

When rescanning,

Write "on" to the power/control node of the root bridge's child.
Write 1 to the rescan node of the root bridge's child.

This is a cherry-pick from internal.

Coverage remained the same at 80.842% when pulling feb3cf0b657260ac3e35cc41cbf5d706b8ada150 on tswhison/cp_022fd17 into fb0004441b281787c307632f5e5a16c556746455 on master.


feat(frontend): create initial component for unified transactions

Motivation
As initial step to show the unified transactions, we create a basic component, that show a list of transactions with their specific card component (each network has a specific one), or a placeholder if no transaction is present.
We will implement each list separately in other PRs.
Changes

Create type for transaction with associated component.
Create component AllTransactions.
Use it in Activity.

Tests

[OISY-130]


--

sorry i didnt read the prerequisite that i need a domain name for testing this PoC

@fdq09eca Sorry I didn't see this. Yes a domain name is a must, this is because this POC is meant as a sort of template to containerize and deploy as a real world system. There is nothing important in this project to debug/run locally. That was never the point.


[4.3] Bug 1753247: listen for sigterm and terminate

kubernetes will send a sigterm to signal for a graceful shutdown. builder should listen for the sigterm and exit cleanly without requiring a sigkill.

/lgtm cancel
Need to think about which exit code we should send - SIGTERM means the build didn't complete and should fail.

@adambkaplan I changed the return code to 1, since, it appears, the rest of the code will also return 1 on error. Just let me know if we should change it again!

/bugzilla refresh
/rebuild

4.3 is open
/hold cancel

/retest

@adambkaplan friendly ping for a review and approval

/hold
Got bit by the oc -p deprecation

@adambkaplan Do I need to update the PR?

the oc exec -p test fix has merged
/hold cancel
/retest


docs: setup-a-validator.md  Add cluster specific note

Problem
The setup a validator page doesn't make it clear that the startup script contained is specifically for testnet or mention where to find startup scripts for other clusters.
Summary of Changes
Added a link to the clusters/avaliable.md page for people to find more info easily.

Thanks!!
Docs-only change, merging blind!!

This was really funny


Text colors in striped tables

Hello everybody,
First of all congrats to spectre. I first saw it used on grav CMS and am now trying it out for a project of mine.
Now, my issue is the following:
I am trying to use a striped table on a dark background.
It is striped, but between text color and background color, every second line is completely unreadable. And hovering does not work either. I'm attaching a screen shot for better understanding.
Maybe I am missing some class or something like that, but any help is appreciated.
Thanks in advance,
Sebastian

A quick fix is to make the .table class background color white like this
.table {
  background: #fff;
}

Another Fix is to override spectre.css and customize your own Dark themed table
Check this codepen for more clarity
https://codepen.io/tunjioye/pen/LKoJzR

Thanks tunjioye. That worked out great!


Random MHC prediction for random cohort

In this PR:

Random cohort uses random MHC binding prediction to avoid needing any NetMHCcons install.
Rename random_cohort to random.

@jburos

Coverage decreased (-0.1%) to 55.772% when pulling 94cca3483219f2726b54d1fe1195acf3a6e9575e on random_mhc into 95f78d045291178b34c2a71eb8156da1dc5b75a4 on master.

Reviewed by @jburos: 👍


Fine tuning failure

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug
An error occurred when I was fine-tuning a josn file to print the id of fine_tuning_job

The returned model is none
May I ask what caused this error？
Thank you so much for your assistance.
To Reproduce
As indicated above
Code snippets
No response
OS
Window 10
Python version
Python 3.8.18
Library version
openai 1.3.6

This does not look like a bug in the SDK, so I'm going to go ahead and close this issue.
In this case, it looks like your problem is that you may need to top up your account, which you can do here: https://platform.openai.com/account/billing
For further assistance, please visit https://help.openai.com/


Bottom Navigation Tab position issue

🐛 Bug Report
I recently updated UI Kitten library to 5.3.0 from 5.1 (till this version no issues) and my bottom navigation tab bar is broken and it got pushed to the middle of the page. I am using expo-router (1.5.03) for navigation

To Reproduce
Steps to reproduce the behavior:

Create a expo-router project and integrate with UI Kitten
Create a Tab layout with below code

import React from 'react'
import { Icon, BottomNavigation, BottomNavigationTab } from '@ui-kitten/components'
import { Tabs } from "expo-router";

const BottomTabs = ({navigation, state}) => {

    return (
        <BottomNavigation style={{marginBottom: 4, paddingHorizontal: 4, paddingVertical: 8}} selectedIndex={state.index}
        onSelect={index => navigation.navigate(state.routeNames[index])}>
            <BottomNavigationTab icon={<Icon name="ios-list-outline" pack='ionicons'/>} title={`Manage`}/>
            <BottomNavigationTab icon={<Icon name="ios-add-outline" pack='ionicons'/>} title={`Create`}/>
            <BottomNavigationTab icon={<Icon name="ios-trash-bin-outline" pack='ionicons'/>} title={`Deleted`}/>
        </BottomNavigation>
    )
}

export default function Layout() {
    return (
        <Tabs screenOptions={{headerShown: false}} tabBar={props => <BottomTabs {...props} />}>
            <Tabs.Screen name="[id]"></Tabs.Screen>
            <Tabs.Screen name="create"></Tabs.Screen>
            <Tabs.Screen name="deleted"></Tabs.Screen>
        </Tabs>
    )
};

Expected behavior
Bottom tab bar position need to be fixed at the bottom.
UI Kitten and Eva version

Package
Version

@eva-design/eva
5.3.0

@ui-kitten/components
5.3.0

Environment information
System:
OS: macOS 13.3.1
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Binaries:
Node: 16.18.1 - ~/.nvm/versions/node/v16.18.1/bin/node
Yarn: 3.2.4 - /usr/local/bin/yarn
npm: 8.19.2 - ~/.nvm/versions/node/v16.18.1/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.3/14E222b - /usr/bin/xcodebuild
npmPackages:
react: 18.2.0 => 18.2.0
react-native: 0.71.6 => 0.71.6

I figured out that the problem is coming from the BottomNavigation component.

I tried replacing both BottomNavigation and BottomNavigationTab, with TabBar and Tab respectively and it works as expected. The only indicator is at the wrong position. What might be causing BottomNavigation to behave differently?

Same Issue. Below is my code, any updates?
`import React from 'react';
import { NavigationContainer } from '@react-navigation/native';
import { createBottomTabNavigator } from '@react-navigation/bottom-tabs';
import { TabBar, Tab, Layout, Text } from '@ui-kitten/components';
const { Navigator, Screen } = createBottomTabNavigator();
const UsersScreen = () => (
<Layout style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
USERS

);
const OrdersScreen = () => (
<Layout style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}>
ORDERS

);
const BottomTabBar = ({ navigation, state }) => (
<BottomNavigation
selectedIndex={state.index}
onSelect={index => navigation.navigate(state.routeNames[index])}>

);
const TabNavigator = () => (
<Navigator tabBar={props => <BottomTabBar {...props} />}>

);
export const AppNavigator = () => (

);`

As a temporary solution, I have replaced BottomNavigation with the TabBar component.

Tried with the latest code after clearing the npm cache and node modules but the issue still persists with the BottomNavigation.


Fix multiple workflows and add proper engine persistance

Fixes #7127.
Closes WOR-322, WOR-395
Previously, engine did store everything in-memory - this is not expected behaviour since R2/KV/DOs all have persistenece, by default.
Also, multiple workflow definitions were broken since the DO unique key was a constant (therefore it would fail when workerd launched)

Tests

[ ] TODO (before merge)
[x] Tests included
[ ] Tests not necessary because:

E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)

[ ] I don't know
[x] Required
[ ] Not required because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s):
[x] Documentation not necessary because: there isn't anything to document (except changelog, which will come later) - this is expected behavior

Will adding persistence enable workflows to return serializable values like steps do? This would be great to compose workflows.

I'm sorry, not sure what you mean by that - afaik you shouldn't have any problem composing workflows atm

I meant being able to call a workflow and get the return value. Right now you can only compose by having them triggering each other, like queues. But it would be great to be able to have them act like steps, with a return value. This is how it's implemented at inngest: https://www.inngest.com/docs/reference/functions/step-invoke

I meant being able to call a workflow and get the return value. Right now you can only compose by having them triggering each other, like queues. But it would be great to be able to have them act like steps, with a return value. This is how it's implemented at inngest: https://www.inngest.com/docs/reference/functions/step-invoke

That is unrelated to the PR - but you can already do this - you can pass the workflow output as an event payload to the next. What you are describing is syntactic sugar for that, which we might (or might not) consider in the future :smile:  thanks ^^


Conflict with Bootstrap 4 CSS

I am working on implementing scroll-spy w/ countUp on a site that uses Bootstrap 4.  CountUp without scroll-spy works fine.  Scroll-spy will only work when the css for Bootstrap is omitted.  I am thinking there is some conflict (somehow), but wanted to see if this was a known issue or something fairly straightforward to override.

The CSS shouldn't affect this scroll-spy at all - however if you are including the JS from bootstrap, that would likely override the window.onscroll handler which this lib uses. So make sure you aren't using the bootstrap JS and it should work... let me know.

I will have to dig into this a little more. The Bootstrap.js library does not seem to have any impact. It's only when the Bootstrap.css file is present that scroll-spy does not work. I know this doesn't make sense, so there has to be something else that I'm missing.

Getting a little closer....scroll-spy in a nested grid seems to be having some trouble.  If I move the element outside of the nested grid it seems to work, but for some reason once it's in the sub-grid, no luck.  Not sure what to make of this yet.

I will have to dig into this a little more. The Bootstrap.js library does not seem to have any impact. It's only when the Bootstrap.css file is present that scroll-spy does not work. I know this doesn't make sense, so there has to be something else that I'm missing.

Getting a little closer....scroll-spy in a nested grid seems to be having some trouble. If I move the element outside of the nested grid it seems to work, but for some reason once it's in the sub-grid, no luck. Not sure what to make of this yet.

Well...not sure if I am any closer, but the only way I can get it to work is to have an empty element preceding the element with the scroll-spy implemented.  For example:
`
`


Conda 1st time install conflicts with existing python install

I tried:
conda create -n "eeg-notebooks"

conda activate "eeg-notebooks"

conda install git

conda install pip

git clone https://github.com/NeuroTechX/eeg-notebooks

cd eeg-notebooks

pip install -r requirements.txt

but encountered errors on the last step, since it tried to use my existing python 2 install on my Mac.
@m9h helped me using a different set of instructions.

I found some instructions that seem similar to what helped me in a currently unused markdown file:
https://github.com/NeuroTechX/eeg-notebooks/blob/master/doc/getting_started/setup_overview.md#2-clone-eeg-notebooks-and-install-dependencies

This is very surprising to me. If you ran conda activate "eeg-notebooks" in the same shell as you later ran pip then shouldn't that override any system pip install by placing the other bin path earlier in the PATH? (that's at least how plain venv and similar behave)
Curious how that wasn't the case. What was the difference that fixed it for you?

@ErikBjare This only happened once, and I would like to try again with a fresh start on a different Mac that already has Python, but not Conda, installed.
I'll report back and close this issue if I am unable to replicate.

Curious how that wasn't the case. What was the difference that fixed it for you?

conda create -n "eeg-notebooks" Python=3

This was the crucial step that made it work with no issues.

@retiutut Aaah, that makes a lot of sense. Surprised to see conda not pick Python 3 by default.

@retiutut I made a docs PR #51 that should help avoid similar issues in the future.


Update guide URL and remove status

@middagj I will release a new version before I ship 2.6.0.Final as I want the guide thing out there.


additions to UN ontology

comments from Becky, after the merge

moving food distribution to a new node under interventions
commenting 'inflation rate' under inflation. if necessary, we could uncomment it later.

@ajaynagesh is this ready to be merged then?  It sounds like Becky approved, but she didn't give it a check mark.

I guess so ...
@bsharpataz ?

I will rerun the dynamically generated tsv files after this and the other PRs are merged.


Remove empty meta description

This PR is for remove an unnecessary / unused / empty meta description.
There is already one functional meta description in use:
<meta name="description" content="A resume generator progressive web app">

@amitmerchant1990  is this project still active?
is it ok if I make a PR or create an issue for every detected bug?
Thanks in advance for your quick response


Test case for IDENTITY-7233

Merge after upgrading kernel to 4.4.21

Updated the test case and sent to 5.5.x branch with https://github.com/wso2/product-is/pull/2802


add more jokes

@azriakmalk Please resolve the conflicts

@azriakmalk your PR is messing up and making a lot of changes, and it is hard to solve conflicts now.
Closing this one, feel free to open a new one, please update your fork.


Usability improvements

As mentioned in the Discourse, this is an excellent effort. I noted some UX thoughts upon first usage which I just wanted to drop here. They are loose suggestions:

Close the layout window upon clicking "Apply" if it was successful
If the layout window is completely empty and "Apply" is clicked, do not display an error message but insert "{}" and close the window silently
If the layout is empty when a bag is dropped onto the window and the layout is empty, open a default selection of widgets (image, plot, raw message) pre-subscribed to a sensible topic in the bag

The last one came up because it was confusing to drop the bag, but then see nothing happening. I think that will confuse users who are not familiar with ROS especially.
Cheers!

Thank you, these are great suggestions. 😃 It's always interesting to hear about the experience of someone using an app for the first time; as the developer it's easy to miss the small usability issues. These ones should be pretty easy (and, if anyone is interested, we'd happily accept pull requests!)
Don't hesitate to share any further feedback you might have with more usage.

@felixvd Pls see the updates below for the UX improvements you suggested:

Close the layout window upon clicking "Apply" if it was successful.

Done.

If the layout window is completely empty and "Apply" is clicked, do not display an error message but insert "{}" and close the window silently

Done.

If the layout is empty when a bag is dropped onto the window, open a default selection of widgets (image, plot, raw message) pre-subscribed to a sensible topic in the bag

We opted out since the user might actually want to have empty layout/globalState config. However, if you open webviz in incognito mode or cleared the localStorage, it'll load with the default layout.
Let us know if you have more feedback / ideas!

Will close this issue now. Feel free to open another one when you have other suggestions


Is OpenSSL 3 support planned?

As stated in another issue, this engine does not support OpenSSL 3. As OpenSSL 1.1.1 is going EOL in September 2023, we wonder whether there is a OpenSSL 3 compatible engine/"AzureKeyVaultManagedHSMProvider"?

yes, it is under consideration.

Since ENGINE support has been deprecated, this is unfortunately a rewrite to the provider spec. I compiled with OpenSSL 3.0 and got several deprecated warnings but it compiles and executes with no issues.


Use "official" scroll widget

Addresses https://github.com/brainglobe/cellfinder-napari/issues/24 & https://github.com/brainglobe/cellfinder-napari/issues/122.
Thanks to @dstansby's hard work :pray:

Closing as I messed up the git history


CREDEBL docs:- studio UI section

[ ] CREDEBL Docs : studio UI changes.

As per discussion with team this task is on hold. Discussion for new approach of documentation is also pending.

Since, we have migrated to gitbook, we will stop working on this task and create new task to proceed.
Cc - @ajile-in @amitpadmani-awts @ashwini-aher @pranalidhanavade