Passwordless login gets stuck in preparing wallet

many users report that when they use passwordless login they get stuck  in preparing wallet

@sirpy I was unable to reproduce the issue locally. Could it to depend of the keys/wallet address generated from the login data
? If yes i'll ask Dorit about users reported that issue and will check logs.
Also i found the following warning in the console:

Will investigate it tomorrow

@serdiukov-o-nordwhale status?

@sirpy I asked @Esfir-E  for additional info in the Slack, still have no answer.
Duplicating my questions here.

@Esfir-E
@sirpy  said you could provide info about users have met with that issue. Please send me the links to the corresponding Re:Amaze tickets
Also he said you also got stuck with passwordless login. Could you please to try to do this right now and if the issue reproduces, to capture a video of login with the Chrome console opened (i would see the log messages/errors happening)
Thank you!

@sirpy still have no feedback from @Esfir-E . Temporary moving to Backlog

@sirpy still no feedback/screen recordings from @Esfir-E
I asked her on our sync regarding analytics 2-3weeks ago, she have promised to prepare screen recordings but actually haven't provided it yet

@Esfir-E you never gave us any data.
is this issue still happening? have you heard about it in support?

@Esfir-E i'm closing this for now


variable constraint documentation needs to be updated so that it is in line with current dependencies

Related to: https://github.com/VEuPathDB/web-eda/issues/1410
issue with dependency order on terms allowed for overlay vs facet is fixed, but Variable constraint documentation needs to be updated to reflect these changes (see https://github.com/VEuPathDB/web-eda/issues/575). In particular, please update the verbiage in this section:

@danicahelb what would you prefer the new verbiage to say?


How do u achieve such awesome project??

It's vrey friendly for our users!!!
I really love it  and want to introduce it to my friends!
If u can say sth about it I will be appreciate!!
Thanks. :)

Hello sddwt. I do not understand your request. Do you have a specific question?


block implicit threads usage

Description

This PR blocks implicit thread usage in tests. It also introduces enablethread which allows using threads in selected tests.
Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

Was there a conversation somewhere about this?  can you elaborate on your motivation for this?

This PR is the next result of debugging why tests failing. When a thread is used implicitly then there is no waiting on its end before deleting elements. Then there are runs where elements are deleted before thread end and its finish with error in Qt Event Loop with a message that element is already deleted or segfault.

Just so we have the context here, could you link to a recent test failure that might be helped by this?  (Tests have been doing much better recently)

last commit on master looks like related:
https://github.com/napari/napari/runs/2842961715

to clarify my point from the meeting:  I'm not opposed to this change, but I want to make sure it's actually doing something, not just that it "seems like it can't hurt".  So, basically, I'd like to see it demonstrated that if you rerun tests on CI in current master multiple times over, you periodically see segfaults at the end of the test, but if you rerun tests in this PR multiple times over, you don't ever see them.  I just reran the tests here and will do so a few times (and we can rerun tests on master somewhere else to check).
If we find that only this PR is succeeding consistently, but master isn't... then great!  let's merge.  if not, then I'm not so sure

since most of the remaining fails are happening on windows, I temporarily added more windows tests to the github action


[DOI Registration] Design Training Module

Develop an online training module that provides guidance for users on preparation of resources for publication and the DOI publication process

I am unassigning myself and @ChristinaB as I need to delegate activities like this and Christina may not have time (but she is welcome to take it back if she wants).  I am assigning @Lizabrazil as I think this fits in CUAHSI's user support work.  I am happy to review design drafts, but will not be able to develop the initial design.

We have several help articles and a pdf guide to data publishers now, closing

Appropriate documentation will be developed when DOI work is completed.

@Lizabrazil  can you give links to the help articles and pdf guide? I will share it with Waterhackweek participants as part of motivational prompts to get project work finalized. Thanks!


cypress/included:4.8.0 image has no typescript

Or am I mistaken? I also am not able to install it into the image like I can with plugins.

You would need to install TypeScript and any other additional Cypress plugins before running tests. See example in https://github.com/bahmutov/cypress-gh-action-included/pull/7
Normally you would run npm ci, which would bring those dependencies into local node_modules, then run using docker run ... which would include the entire current folder, including node_modules. This would only fail if there are native dependencies that need to be compiled, and the host OS is different from the Docker run Linux OS.


Bug: Switching to Favorites is crashing after selecting a tag

Description
Switching to Favorites is crashing after clicking a tag.
Steps To Reproduce

Select a tag from the sidebar
Click "Favorites" on the sidebar
Files is crashing

Steps to fix
I do not konw.
Files Version
版本: <IP_ADDRESS> OS Version: 10.0.22621.755
Windows Version
Windows 11 22H2 22621.755
Relevant Assets/Logs
files.txt

What happens if you toggle the option on and off?

If this option is enabled, there is a high probability that it will crash. If you turn this option on and then turn it off, you are less likely to crash. This will not happen if the option is never turned on.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: Yair @.>
发送时间: 2022年11月8日 23:54
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
What happens if you toggle the option on and off?
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1307437685, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM6Z4FVFLOMN4ANZRKJLWHJZTDANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

Can you please upload the debug.log and debug_fulltrust.log files directly to GitHub. You can get them in files settings > about > open log folder.

从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送

发件人: Josh-65 @.>
发送时间: Wednesday, November 9, 2022 11:44:18 AM
收件人: files-community/Files @.>
抄送: isdwsdfv @.>; Author @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Can you please upload the debug.log and debug_fulltrust.log files directly to GitHub. You can get them in files settings > about > open log folder.
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1308165637, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM6YAWFXJZU6WZFBRB6TWHMMZFANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

You can't send them via email you will have to open the issue on the github site

😶
All right.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年11月9日 11:58
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
You can't send them via email you will have to open the issue on the github site
—
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1308177218, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM622AFEA3DNB36CHET3WHMOPNANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

What should I do? I'm not familiar with GitHub.🤔

Where the leave comment box click on it. Then drag the two files into it and wait a few seconds then click comment

debug.log
debug_fulltrust.log
Is that the way to do it？🤔

yes

Is there anything to do?
发件人: Josh-65 @.>
发送时间: 2022年11月9日 12:58
收件人: files-community/Files @.>
抄送: isdwsdfv @.>; Author @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
yes
—
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1308211996, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM63TWT6ELNMACPR3IQLWHMVNLANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

The error in the logs might be fixed on the preview builds but the set as default options doesn't on it. It will probably just be a wait for the option to be fixed then you can use it.

Thanks.👍
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年11月9日 17:20
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
The error in the logs might be fixed on the preview builds but the set as default options doesn't on it. It will probably just be a wait for the option to be fixed then you can use it.
—
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1308453489, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM62PAMSNJGRRIDVUFVLWHNUE5ANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

Is this still an issue in the preview version? https://files.community/download/preview

No， there isn‘t. It has been fixed.
You seem to have removed the animation.
Can you update it to the official version? I recently noticed the Windows Settings application also crashes due to Windows.Ui.Xaml.dll.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年12月12日 3:02
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Is this still an issue in the preview version? https://files.community/download/preview
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1345630950, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM63DSPKCRF7ZEKZXUDTWMYQKHANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

That is amazing! It crashed again! It was crashed by Microsoft.UI.Xaml.dll. I don’t know why! But the app crashes far less often: only once so far, in fact.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年12月12日 3:02
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Is this still an issue in the preview version? https://files.community/download/preview
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1345630950, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM63DSPKCRF7ZEKZXUDTWMYQKHANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

If it crashes again you can make a new bug report for it

I've found that when I click a color tag in Tags and then click "Favorites," a crash happens. Other times, just click "Favorites," and it won't crash.
I don’t want to report a bug anymore, that is complex.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年12月12日 8:30
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Closed #10433https://github.com/files-community/Files/issues/10433 as completed.
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#event-8009042608, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM67RHWV7FC4HLD5GAPTWMZW3FANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

It will crash if I click the App or document or other things in bags.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年12月12日 8:30
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Closed #10433https://github.com/files-community/Files/issues/10433 as completed.
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#event-8009042608, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM67RHWV7FC4HLD5GAPTWMZW3FANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

Would you like to record a video of the repro steps so that we can reproduce it locally and fix the issue?

Is it OK?
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送

发件人: Steve @.>
发送时间: Monday, December 12, 2022 9:35:11 AM
收件人: files-community/Files @.>
抄送: isdwsdfv @.>; Author @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Would you like to record a video of the repro steps so that we can reproduce it locally and fix the issue?
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1345746581, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM635OBNVSYAIVZB5IFDWMZ6M7ANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

You cannot attach the video as an email attachment, instead you need to upload the video from GitHub directly.

https://user-images.githubusercontent.com/116344443/207007646-6ffe0f90-7c9b-432c-9943-c229f0136b94.mp4

Thanks. Can reproduce it locally.

Your changes in the preview version seem to have been updated to the official version, thank you very much! But in the official version, we still have the same problem that I had in the preview yesterday ：“I've found that when I click a color tag in Tags and then click "Favorites," a crash happens. Other times, just click "Favorites," and it won't crash. ” And ” It will crash if I click the App or document or other things in bags.”
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: @.>
发送时间: 2022年12月12日 17:24
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Reopened #10433https://github.com/files-community/Files/issues/10433.
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#event-8012017005, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM64G5NXMBH545YV3XZLWM3VLDANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

And it starts up a little slower than previous versions.
发件人: @.>
发送时间: 2022年12月12日 17:24
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug！ (Issue #10433)
Reopened #10433https://github.com/files-community/Files/issues/10433.
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#event-8012017005, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM64G5NXMBH545YV3XZLWM3VLDANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>

Startup is a little slower for now but file naviation should be quicker.

https://user-images.githubusercontent.com/116344443/207199715-3baa34b8-2108-47e7-addc-4c9b53cd0621.mp4
https://user-images.githubusercontent.com/116344443/207199724-4a428569-20af-4942-81c3-ca265e033b05.mp4
Three bugs.

Is this still an issue in 2.4.8?

It's still slow to boot, but the bugs have been fixed.
发件人: @.>
发送时间: 2022年12月28日 14:58
收件人: @.>
抄送: @.>; @.>
主题: Re: [files-community/Files] Bug: Switching to Favorites is crashing after selecting a tag (Issue #10433)
Is this still an issue in 2.4.8?
―
Reply to this email directly, view it on GitHubhttps://github.com/files-community/Files/issues/10433#issuecomment-1366415813, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3XUM65P2NBEKBUUHT32IA3WPPQJ3ANCNFSM6AAAAAAR2ITJPY.
You are receiving this because you authored the thread.Message ID: @.***>


fix all error responses to correctly return a type

Some responses do not correctly return a type on an error response. This ticket is to fix this issue.
Some locations this occurs:
https://github.com/dlcs/iiif-presentation/blob/3bace7eafb528ced1a62e3aab3e040c44ae58954/src/IIIFPresentation/API/Infrastructure/ControllerBaseX.cs#L60
WriteResult.NotFound, WriteResult.FailedValidation and WriteResult.StorageLimitExceeded do not pass through a type to PresentationProblem
https://github.com/dlcs/iiif-presentation/blob/3bace7eafb528ced1a62e3aab3e040c44ae58954/src/IIIFPresentation/API/Infrastructure/ControllerBaseX.cs#L90
uses controller.Problem, which doesn't take a type
additionally, controller.PresentationProblem should be updated to take a mandatory type and the type parameter should be updated to accept a Uri instead of a string
this should resolve #176

Duplicate of #176


killSelection RAML type should use enum values that camel case when converted to scala

other enum's that contain "complex" items use hyphen or underscore separators to delimit the words of the complex item. for example OldestFirst should have been defined in RAML as "oldest-first" or some such.

PR is here: https://phabricator.mesosphere.com/D369


Receiving a HTTP 500 error when trying to deploy to Ireland and London Region

Describe the bug
I am in the process of trying to deploy a .Net Core Application using ElasticBeanstalk however in "Publish to New Target Screen" I receive "A error occured in the deployment tool"
I have gone through the AWS tool kit log and scene the following:
2023-04-25 11:55:07,623 [26] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 8 event(s)
2023-04-25 11:59:32,793 [76] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Stopping a deployment session
2023-04-25 11:59:32,798 [32] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Deployment session stopped
2023-04-25 11:59:32,799 [52] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Starting a deployment session
2023-04-25 12:00:05,683 [1] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Deployment session started
2023-04-25 12:00:05,701 [76] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Republish targets found for CBW.UI: 0
2023-04-25 12:00:05,702 [26] DEBUG Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel - Publish targets found for CBW.UI: 4
2023-04-25 12:00:07,928 [76] DEBUG Amazon.AWSToolkit.Telemetry.Internal.TelemetryPublisher - Publishing 3 event(s)
2023-04-25 12:00:21,635 [61] ERROR Amazon.AWSToolkit.Publish.Views.PublishToAwsDocumentControl - Error reloading configuration details
Amazon.AWSToolkit.Publish.DeployToolException: Deploy Tool failed due to internal error. ---> AWS.Deploy.ServerMode.Client.ApiException: The HTTP status code of the response was not expected (500).
Status: 500
Response:
{"ErrorCode":"FailedToFindElasticBeanstalkSolutionStack","Message":"Cannot use Elastic Beanstalk deployments because we cannot find a .NET Core Solution Stack to use. One possible reason could be that Elastic Beanstalk is not enabled in your region if you are using a non-default region.","ProcessExitCode":null}
at AWS.Deploy.ServerMode.Client.RestAPIClient.d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.ViewModels.DeployToolController.d__23.MoveNext()
--- End of inner exception stack trace ---
at Amazon.AWSToolkit.Publish.ViewModels.DeployToolController.d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.ViewModels.DeployToolController.d__21.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel.d__182.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Amazon.AWSToolkit.Publish.ViewModels.PublishToAwsDocumentViewModel.d__182.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.AWSToolkit.Publish.Views.PublishToAwsDocumentControl.d__41.MoveNext()
I have gone back through and ensured that no 403 forbiddens are occuring.
To Reproduce
Right click on application > Publish to AWS
About Info:
Microsoft Visual Studio Professional 2022
Version 17.5.4
VisualStudio.17.Release/17.5.4+33530.505
Microsoft .NET Framework
Version 4.8.04161
Installed Version: Professional
ASP.NET and Web Tools   17.5.318.41597
ASP.NET and Web Tools
Azure App Service Tools v3.0.0   17.5.318.41597
Azure App Service Tools v3.0.0
Azure Functions and Web Jobs Tools   17.5.318.41597
Azure Functions and Web Jobs Tools
C# Tools   4.5.2-3.23171.7+d17f741546fad2786cbd6394d08619544e53a36d
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
NuGet Package Manager   6.5.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
Razor (ASP.NET Core)   <IP_ADDRESS>6603+9f1b6856460af1e592d387ebef416eadddac453f
Provides languages services for ASP.NET Core Razor.
SQL Server Data Tools   17.2.40120.0
Microsoft SQL Server Data Tools
TypeScript Tools   17.0.20105.2003
TypeScript Tools for Microsoft Visual Studio
Visual Basic Tools   4.5.2-3.23171.7+d17f741546fad2786cbd6394d08619544e53a36d
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools   17.5.0-beta.23053.5+794b7c259d9646a7eb685dad865aa27da7940a21
Microsoft Visual F# Tools
Visual Studio IntelliCode   2.2
AI-assisted development for Visual Studio.

Hi @cmcbride781 , thank you for providing some log details. Can you see what version of the Toolkit you are using? When you launch Visual Studio, open the "View" menu and select "Output". Then select to show output from "Amazon Web Services". The top of this particular output pane should show an entry like this (the second line is the one of interest):
08:30:53:374	AWS Toolkit for Visual Studio
08:30:53:374	Toolkit Version: <IP_ADDRESS>
08:30:53:374	Visual Studio: VS Professional 2022, Version: 17.5.2

The @awschristou,
This is the output I get:
AWS Toolkit for Visual Studio
Toolkit Version: <IP_ADDRESS>
Visual Studio: VS Professional 2022, Version: 17.5.1

Ok, it looks like you are using the current version of the Toolkit. I wanted to rule that out.
A couple of things to try:
Install the .net deploy tool and try running it from the command line
I'd like to know if you get the same behavior directly from the deploy tooling.
From the command line, run dotnet tool install -g aws.deploy.tools . Then change directories into the folder containing your project (csproj file). Run dotnet aws deploy , and work through the prompts to try to deploy to Beanstalk on Linux in the Ireland region. (usage details can be found at https://aws.github.io/aws-dotnet-deploy/ )
Does this proceed, or does it produce a similar error?
Allow the Toolkit to re-download the deploy tool
I'd like to rule out whether or not the Toolkit was holding on to an older version of the deploy tool.
Close all of your running Visual Studio instances. Open the folder %localappdata%\AWSToolkit\aws.deploy.tools and delete the contents of this filter. Re-launch Visual Studio, and allow the AWS Toolkit to re-install its copy of the .NET deploy tool. Try to perform your deployment again.
Does this proceed, or does it produce a similar error?


Hiding tab-content and showing it back doesnt keep its position index

I'm trying to dynamically hide a tab-content based on an option (<tab-content v-if="foo === 'bar'" ...), and the tab gets hidden. If I turn off the option the tab reappears but it doesn't keep it's position (initial tab position is 3/6, after reappearing it's 6/6). How can I fix this ?

Hi @Al3xR0 If you want predictable tabs, you have to use v-for and again key each tab.
https://jsfiddle.net/bt5dhqtf/1697/


Running package-audit spits the yarn.lock file instead of outdated packages information.

This is the sample output that I got when running package-audit:
<EMAIL_ADDRESS>  "integrity" "sha512-CJ17OoULEKXpA5pef3qLj5AxTJ6mSt7g84he2WIskKwqFO4T97d5V7Tadl0DYDk7qyUOQD5WlUlOMChaYrhxeA=="
  "resolved" "https://registry.npmjs.org/write/-/write-0.2.1.tgz"
  "version" "0.2.1"
  dependencies:
    "mkdirp" "^0.5.1"

<EMAIL_ADDRESS>  "integrity" "sha512-F+P9Jil7UiSKSkppIiD94dN07AwvFixvLIj1Og1Rl9GGMuNipJnV9JzjD6XuqmAeiswGvUmNLjr5cFuXwNS77Q=="
  "resolved" "https://registry.npmjs.org/ws/-/ws-7.5.9.tgz"
  "version" "7.5.9"

package.json + yarn.lock.zip

Looks like this yarn.lock was likely accidentally generated with npm install, which resulted in a different format of the file. This issue is fixed in v0.3.0.


Add type argument to File methods

We need to be able to either pass a type argument to the File methods for the file we expect, or have a way to fetch json data without fetching the metadata payload.

I think this issue is not necessary because the types come from the parser used, and you can the use the as MyType after you parse the json, for example


Automatic Syncing of Standups in samepage graphs

we run a Smartblock each day on the DNP of the samepage graph that outputs each contributor's section
Each contributor's section is EITHER a

"cross-app embed" into their respective tool
"cross-app reference" into their respective tool

The goal is to allow contributors to work in their preferred tool, but also have a central place to view what others on the team are working on today.

Trying to test a cross graph query.
Getting error:
instrument.ts:132 POST request to http://localhost:3003/extensions/roam/query failed: Only URLs with a scheme in: file, data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

Looks like it could be a windows path.resolve() issue (source) in package/scripts/internal/appPath.ts
Will look into this tomorrow.

I don't believe it's path.resolve() anymore.  But I have no idea what it is.
My URL looks correct.  I'm not sure why Received protocol 'c:' comes up, I don't see it while walking through the breakpoints.
And the backend samepage give me
api Received Request post /extensions/roam/query +23s
api Executed post /extensions/roam/query in 8ms +13ms

😵

normalizing the URL and adding the prefix file:/// seemed to fix this issue for me.
Although I'm not returning any results where I expected to.
But I did get
message-notebook Found connection 18...1dc for 4b083...d3bf3 +14s
message-notebook 182...3c6f1ed2e messaged 4b08...dd3bf3 as online true with REQUEST +4ms

Now pulling the most recent changes gives me a new error:
POST request to http://localhost:3003/page failed: Error: No targets specified

That's a user error we throw when the user calls for a notebook request with no target defined - this is going to require some debugging to investigate why not

https://github.com/samepage-network/samepage.network/commit/2e237ace990c66c36b8ce66a606d5f8b51a71414
It looks like these changes stopped target from being passed to the args
I haven't dug too deep, but I'm wondering if it is the workspace: notebooks.label, change as the label column in my notebooks table is blank.

Ohhh - yea run npx ts-node scripts/apply.ts --sql. This will run a migration to copy the workspace values to the label values.
Some backstory: most cloud apps have a workspace id that is globally unique and a workspace name that isn't necessarily. we want to start tracking both, and soon make the app/workspace combo globally unique in our notebooks table, while then using label as a display name for users.

Hmm.  I don't see a scripts/apply.ts, but I do see a scripts/commands/apply.ts so I tried npx ts-node scripts/apply.ts --sql but my labels are still blank. 🤔
Also, when I it seems that I am getting through (changing notebooks.label to notebooks.workspace for example), all my queries are returning No Results.  I tested with live samepage as well.  I'm wondering what piece I might be missing here.

sorry typo - npx ts-node scripts/cli.ts apply --sql
All of our commands are run by npx ts-node scripts/cli.ts [command] [args]

Live SamePage is not expected to have cross requests to be working yet as we are still trying to nail the API locally.
Figuring out why the queries are returning No Results (after workspace/label is sorted) is considered in scope for this task. One thing that would be super helpful is voicing things that are making it specifically hard to debug, and what feature ideas could alleviate those pains

Just an update of where I'm at.
Looks like No Results is from path being set to public/data/requests/ and /requests doesn't exist on my system.
https://github.com/samepage-network/samepage.network/blob/6082e1a9389ac49932d0f1fd4768f7a5db1a526c/app/data/downloadFile.server.ts#L31-L32
Tomorrow I'll take a look at where that is getting set and why it doesn't seem to exist.

we use the file system (and in production, AWS S3) to cache the answer to requests, in case the other target notebook is offline.
so the question to investigate here is: why is the target notebook not sending the response down and saving it?

Well, it works now. 😀
I'm not 100% sure but I might have been getting No Results because I updated samepage-network without realizing it had /package updates and I didn't updated roam-samepage 😐 Fortunately, where I spent a lot of my time will help with understanding these next tasks.
A few interesting things now:

first query returns No Results but subsequent queries return results
Smartblock <%QUERYBUILDER%> returns blank blocks
I went to add a test query to the samepage graph (which I have in the app not browser), added roam-samepage, then got a post/disconnect loop

I'll start with 1) and look into where/when method gets set

Yup - 1 is a known challenge to solve.
Right now, the way the request protocol works is that app A sends the request, and only returns a response from cache. It doesn't ever request from the target app directly - instead it sends them the message basically saying "hey, I was looking for this data, send it back to me whenever you can".
We'll want to have a case for handling when "whenever you can" is immediate, which is actually the 95+% use case with most of these cloud-based applications

I went to test the new round of changes (Start to stabilize cross app querying (#17) · samepage-network/roam-samepage@cea14c0) and I am getting some errors and no results are returned.
samepage.network, roam-samepage, and roamjs-query-builder are all up to date.
The target notebook is getting the proper query and returning results in handleRequestOperation but the target notebook throws two errors:
POST http://localhost:3003/page 400 (Bad Request)
t	@	instrument.ts:163
handleFetch	@	apiClient.ts:35
(anonymous)	@	apiClient.ts:101
apiClient3	@	apiClient.ts:131
handleRequestOperation	@	handleRequestOperation.ts:24
await in handleRequestOperation (async)
handler	@	crossNotebookRequests.ts:103
(anonymous)	@	setupMessageHandlers.ts:66
handleMessage	@	setupMessageHandlers.ts:64
receiveChunkedMessage	@	setupMessageHandlers.ts:99
registry_1.samePageBackend.channel.onmessage	@	setupWsFeatures.ts:160

Uncaught (in promise) Error: POST request to http://localhost:3003/page failed (400): Failed to parse request. Errors:
Path `` had the following union errors:
  - Invalid discriminator value. Expected 'create-notebook' | 'add-notebook' | 'list-user-notebooks' | 'authenticate-user' | 'ping' (invalid_union_discriminator)
  - Expected `request` to be of type `object` but received type `undefined`
    at apiClient.ts:41:13
    at async handleRequestOperation (handleRequestOperation.ts:24:5)
(anonymous) @ apiClient.ts:41

Any ideas?

what's the shape of the request that the target notebook sends?

This?

{
    "conditions": [
        {
            "uid": "-Ae1l2WRL",
            "relation": "with text",
            "source": "node",
            "target": "DemoCrossQueryData",
            "not": false,
            "type": "clause"
        }
    ],
    "returnNode": "node",
    "selections": [],
    "schema": "node-query"
}

I meant the full request sent to api.samepage.network - should be something like {method: "notebook-response", notebookUuid: "...", ...}

{
  "notebookUuid": "4b083c01-a75c-48aa-a516-d7c580dd3bf3",
  "token": "{redacted}",
  "method": "notebook-response",
  "response": {
    "results": [
      { "text": "DemoCrossQueryData", "uid": "SY6NmX2iv" },
      { "text": "DemoCrossQueryData1", "uid": "sDX6jkAEL" },
      { "text": "DemoCrossQueryData", "uid": "0sSqBw25w" }
    ]
  },
  "target": "18222c4a-b00d-47f3-866f-5713c6f1ed2e",
  "requestUuid": "eee98bea-ecc0-46f1-9df0-a85ba190548a",
  "messageUuid": "37b2a8b4-2cfe-4ba5-a51e-e46763d292c1"
}

hm and you've pulled latest samepage? it's failing a parse error. This schema used to require a request parameter but no longer does

My apologies, I didn't realize I was still on a forked version of this repo.  I made changes to my workflow that should stop this error from happening again.


Revamp project (fix, reorganize)

This PR introduces general bug fixes and improvements to the project. Specifically, it

reorganizes project directories semantically
adds missing import statements
adds argument parsers to each executable script
ensures every executable works as intended

Thanks!


feat(swagger): Add Hidden decorator to exclude route from documentation

Closes: #264

Coverage remained the same at 100.0% when pulling d6c74e2410e2d5642afa047c5e3433ecca5a72e5 on feat_swagger_hidden_route into 82e0da27ac46ce2f26404f9845a8d8cea6381fdd on master.

Coverage remained the same at 100.0% when pulling d6c74e2410e2d5642afa047c5e3433ecca5a72e5 on feat_swagger_hidden_route into 82e0da27ac46ce2f26404f9845a8d8cea6381fdd on master.

:tada: This PR is included in version 5.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Check checkin date when application launches

closes #369

I am afraid this solution is not good enough. For example, I broke it just by setting the date to today, changing the laptop date to tomorrow and restoring the app from the background. The value is still stuck in the UI and componentDidMount is not called. But something like this could be a better solution:
componentDidMount = () => {
  AppState.addEventListener('change', state => {
    if (state === 'active') {
      // the app was restored from the background - refresh UI
    }
  });
}

@mrtnzlml Updated with a check also on app state change. We still need to check on componentDidMount since user can leave the app, date gets outdated, and he comes back to the hotels app from the native app.

Integrated, thanks.


Add 'Show license' support to deploy.sh script (#30)

I added to my own version of the script and thought I'd PR to your repo too :)

Well, looking at CircleCI failed check, I guess it has nothing to do with the PR itself, but configuration of pipeline maybe.


Update ARCH and BITS parser

Update ARCH and BITS parser to work with SPEC linux_aarch64. So
JVM_OPTION could be set properly.
Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

related with https://github.com/AdoptOpenJDK/openjdk-tests/issues/1503

Tested locally as AdoptOpenJDK do not have machine enable for a jenkins job.
Other platforms are tested with internal jenkins job.


Update MD file on new branch 2017-18-09_06-11-10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

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


Use a proper calculation of energy

Rather than the number I have now, which is purely indicative. I should have a value of the free energy. This likely will have to be negated as a result but that is workable.
This will require some additional thought on #2 for getting reproducible results.

I believe this has now been fixed in 61200fe9652523a7eb8da51f5ade314aa7299df7, although the values don't correspond particularly well to the simulation values. This is possibly due to the pressure, but I am not entirely sure.


Update VSCode & Makefile project generators

This PR updates the Visual Studio Code and Makefile project generators.

VSCode generator has been updated to v1.5.0
Makefile generators have been updated to the latest project.mk-based system.

Summary of changes:

Update the izer's copy of the VS Code README to reflect the new build system

Minor VS Code bug fixes/tweaks.

Add flash & run utility
Add erase flash utility
Fix typo in RISC-V launch profile
Move program counter to reset handler after resetting micro and launching debugger.  Allows for smooth debugging of .elf files on parts with a secure bootloader.

Add some file hashing utilites to utils.py.  The generator functions will now return a boolean value indicating whether project have changed or not.

Support the --override operator from the VSCode and Makefile generators.

Add new Makefile generator to izer/assets.py.

Modify max7800x.py back-end to use new Makefile generator for M4-core projects.  RISC-V projects will still use the old combined .elf Makefile system.

Testing

[x] bash gen-demos-max78000.sh --overwrite (test-gen-demos-max78000.txt)
[x] bash gen-demos-max78002.sh --overwrite (test-gen-demos-max78002.txt)

Should be merged alongside:

https://github.com/MaximIntegratedAI/MAX78000_SDK/pull/79

@rotx-maxim project files have been updated to v1.5.0 (see https://github.com/MaximIntegratedAI/ai8x-synthesis/pull/267/commits/de920add8e73db0462a89082e712402ba00ce033) and are ready for final review.


[beken-72xx] Free list returned by wlan_sta_scan_result()

This method might return a dynamically allocated buffer which should be freed by the caller (the example code does it). Not doing this results in memory leaks.

Ok, as you can see I decided to make the scanAlloc() method return the number of succesfully allocated items. This can help if realloc() fails - then we still can use the previously allocated buffer if needed.
Making this method private should be done as a separate change, since it probably isn't the only one that should be moved.
I have tested this code shortly on bk7231, but not on realtek, since I do not own any realtek device atm (only checked compilation).


RFC: Drop temporaries in tail expressions before local variables

This is one of the results of the temporary lifetimes effort by @nikomatsakis @dingxiangfei2009 and me.
Originally, we were working on a much larger RFC with several changes, but decided to not block small things on big things.
This part is quite small, but requires an edition change.
Rendered

An example of something great with this is that it makes tracing's spans more accurate and less surprising !

@rfcbot fcp merge
After much exploration, we've decided to break apart the "temporary lifetimes" change into two smaller items. This one corrects the lifetimes in the tail expressions of blocks, a common source of surprising compiler errors. The other item (super let) will be pursued in a separate RFC. We have decided NOT to propose a change to temporary lifetimes in match expressions — which was predicted to affect a lot more existing code — and are exploring alternatives (e.g., starting with a lint to help detect the buggy cases).
Lang team, let's do this!

Looking at the resulting breakage from this change I would personally love to just land this change by default in all editions instead of only in >=2024, treating it as "clarifying previously underspecified language semantics" (unless we formally stated the existing rules somewhere). This kind of subtle inconsistency between editions is likely to cause some confusion.

I could be persuaded here, but I am reluctant to make changes in semantics without an edition, because it is difficult to know what code out there may be affected.

Seems very well scoped and motivated for an edition change. Thanks for the effort that went into design and boiling it down to a simple RFC such as this.
@rfcbot reviewed

I would like to formally register a concerning regarding the effect on unsafe code. The RFC says

There's a very small chance this breaks existing code in a very subtle way. However, we can detect these cases and issue warnings.

However, for unsafe code implicitly relying on the current drop order, it's unclear to me whether that is possible.
(AFAIK rfcbot support for t-lang-advisors has not been implemented so if someone on t-lang could tell the bot about this concern that would be great. :)

@RalfJung Your concern was discussed in the lang triage meeting just now. Niko said that we can warn for this situation (and that that such patterns with pointers are error-prone regardless, so we probably want to warn for such patterns also without this change).
The lang team consensus in the meeting was, given the expectation that this can be linted for, this doesn't have to be a blocking concern on the RFC. (But instead something to take into account before stabilization, when there is more data.)
I will add it to the unresolved questions in the RFC.

This seems like a great change, but I was interested in seeing if any real-world code is broken by this. Where can I find the crater run with this change applied to all editions?

The lang team has accepted this RFC and we've now merged it.
Thanks to @m-ou-se and @dingxiangfei2009 for pushing this forward, and thanks to all those who reviewed this RFC and provided helpful feedback.
For further updates on this work, follow the tracking issue:

https://github.com/rust-lang/rust/issues/123739


Feature proposal: squashing categories

This allows docusaurus-api to behave a bit more like docusaurus. When you have a folder with only a single file inside, docusaurus applies the _category_ metadata to the item itself instead of creating an additional category.
This PR adds the same behavior for multi-spec pages.
Example: say you have this folder structure:

Right now, rendering this in a single page yields this:

With the proposed changes, you can use the _category_ file to apply metadata to the inner category (let's say you want a custom title, or you want to set collapsible=false). It also removes the duplicated category, if the outer category only contains a single item. Result:

Can you just update the failing tests to reflect the new behavior?

@bourdakos1 here you go! :)


Initial commit for POET2

This PR has multiple commits

Removing files from existing repo which will be superseded by POET2 directory
POET2 Engine and Service implementation based on Sawtooth consensus SDK
POET2 SGX Enclave code (trusted) and bridge (untrusted)
Rust-SGX C++ bridge layer and corresponding Rust FFI layer
C++ unit test cases for SGX enclave
Validatory registry TP for POET implemented in Rust
Docker compose files and debian package files
IAS client and proxy implementation in Rust
Enabled clippy error and rustfmt checks in Jenkins build.

Signed-off-by: Manoj Gopalakrishnan<EMAIL_ADDRESS>

@dcmiddle @vaporos

@vaporos @dcmiddle updated PR with multiple commits

DCO check is failing.

DCO check is failing.

Will fix this

@vaporos For cargo clippy and cargo fmt, we will raise a new PR/commit
For src directory we will raise a new PR/commit
cargo test is fixed in later commits in this same PR

@manojgop Please address cargo/fmt and src directory in this PR by updating the commits. After these basic items are addressed, will re-review.

ok. We will raise a new commit in same PR to address this

Closing in favor of more specific PRs like #22 and #23.


HDDS-5398. Avoid object creation in ReplicationManger debug log statements

What changes were proposed in this pull request?
There are a few debug log entries in replication manager like this:
    LOG.debug("Handling under-replicated container: {}",
        container.getContainerID());

      LOG.debug("Deleting empty container {} replicas,", container.containerID());

Especially the latter one, will always allocates a new ContainerID object on each call, even if debug is not enabled.
If we just pass "container" then it will use the container.toString() method inside the logger, only if debug is enabled. The ContainerInfo.toString() looks like:
  @Override
  public String toString() {
    return "ContainerInfo{"
        + "id=" + containerID
        + ", state=" + state
        + ", pipelineID=" + pipelineID
        + ", stateEnterTime=" + stateEnterTime
        + ", owner=" + owner
        + '}';
  }

It contains some extra information, but some of that may be useful if debugging a problem.
I propose just passing container to the debug logged and allowing the toString() value to be output in the log.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5398
How was this patch tested?
No tests changed or added.

LGTM. thanks @sodonnel for this work.


Inquiries about the comparison between mnemonics and baseline

Hi, I am reading the code of mnemonics-training, and want to verify the effectiveness of the algorithm, which is related to dataset distillation. However, when I read the code, I noticed that the network implemented here in mnemonics.py is different from that in baseline.py
I think it could be more reasonable to change the "self.network_mtl" to "self.network" when comparing baseline and mnemonics. I want to inquire why mnemonics uses network_mtl, while baseline uses a different model.
Another inquiry is about the "fusion_mode". I have seen some issues discussing about it, but I have not figured out how this option influences the code. What's this option designed for?

Hi @tingxueronghua,
Thanks for your interest in our work!
For your Q1: the mnemonics exemplars and the mtl networks are both our designs. Using these two components together achieves the best performance.
For your Q2: the fusion_mode is an interface for the following project. It is not used in this project, and you may directly ignore it.
If you have any further questions, please do not hesitate to contact me!

Thanks! Your answer is clear. I have no other questions!


fix windows java checks

test run here: https://ci.adoptopenjdk.net/view/work in progress/job/openjdk_build_x86-64_windows_mani_test/14/console


Netlify NextJS builds are broken in 3.7.0 when using multiple npm commands

Describe the bug
A bug has been introduced with version 3.7.0 where if the netlify.toml configuration file contains multiple npm commands such as npm run build && npm run export, the plugin fails with an internal error.

To Reproduce
Steps to reproduce the behavior:

Fork https://github.com/andismith/nextjs-test-blog (this is a copy of the Netlify NextJS starter blog, with an adjusted netlify.toml file).
Build it on Netlify
See error
Run npm install<EMAIL_ADDRESS>--save-dev
See it now passes

Example at: https://app.netlify.com/sites/elated-mcclintock-cdc73c/deploys
Expected behavior
The build should still work in v3.7.0
Versions

Next.js: 11
@netlify/plugin-nextjs: 3.7.0

If you're using file-based installation

netlify.toml:

[build]
  publish = "dist"
  command = "npm run build && npm run export"

(this also occurs for multiple yarn commands too)

I think it may be a result of https://github.com/netlify/netlify-plugin-nextjs/commit/b1fd513c8ac142c335bc3ae950bd093da20466fe

3.7.0 causes issues for me as well when I use multiple npm scripts

Hi both! Thanks for the report. I've isolated the issue and opened a PR with a fix and should have that released later today.

This is now published in 3.7.1. Can you check that this fixes it for you? I've added your specific command as a test case too.

Thanks for attending to this so quick.
For some reason when building it in Netlify it's still picking up 3.7.0 at the latest version. I guess it takes a little while to propagate the new version. Will let you know once I can test this properly.

Yeah, we don't immediately update the auto-installed version, in case issue come up. It'll be auto-installed later today, but you can try it now by installing @netlify/plugin-nextjs@latest from npm.

If you do a build now it should use the new version of the plugin.

That's now working fine, thank you!