[Pulsar Client] Is there a way to specify a schema version instead of uploading SchemaInfo to broker?

Is your enhancement request related to a problem? Please describe.
When conumser/producer connect to broker, it has to upload the schema info (include JSON Schema) to broker for checking schema compatibility, in case the JSON Schema is large, it will become inefficient. I know it is only uploaded when consumer/producer connect to broker, but in my scenario, the client needs to connect and close connection everytime it consume/produce message. Is it better if we just specify the schema version instead of whole SchemaInfo?
Describe the solution you'd like
In case of the schema version has been registered, the client just need to specify the schema version of message it going to consume/produce

Is it better if we just specify the schema version instead of whole SchemaInfo?

We send the schema definition when a client connect to a broker, so the broker can verify the compatibility of a schema. If we only send the schema version, there is no way for us to verify if the client is using the right schema. Because a client can just provide a random schema number and produce the data with a different schema.

but in my scenario, the client needs to connect and close connection everytime it consume/produce message.

Can you explain a bit more about your use case? I would like to understand more why you need to connect and close connection every time it consumes and produce messages. This is an anti-pattern of using Pulsar.

We are building an adapter to integrate Pulsar to SAP Integraion system. Sender adapter will consume message from a topic, Receiver adapter will produce message to a topic. For Receiver adapter, there is no certain time when it is called, if it's called once a month and keeping connection open for a long time to just send a message a month is not a good idea. That is why we decided to close and re-connect to broker everytime.
Btw, Is there any way to tell the Pulsar client (that has producers only) that it should close the connectivity if there is no message to publish after an amount of time, and re-connect to brokers when it needs to send a message again?
For the

If we only send the schema version, there is no way for us to verify if the client is using the right schema. Because a client can just provide a random schema number and produce the data with a different schema.
There is no guarantee that the encoded data sent to brokers is using correct schema in case they using their own custom Schema implementation. I think skipping checking SchemaInfo is make sense, if the client itself can assures the correctness of schema version. By doing this, not only faster connectivity establishment, but also be able to send messages with diffrent versions without creating new producers for each version.


Other icon for iFrame mode close button

I really like the feature but I think the icon might be a little confusing. If we think of the panel iframe overlay as a modal the close icon indicates that it closes the modal, not that it stays in the panel.
The first icon that comes to mind is to use a kind of pin icon instead:
http://fortawesome.github.io/Font-Awesome/icon/thumb-tack/
...to pin the panel to the screen.

Not sure about this one, @jenstornell. The thumb tack would rather suggest to pin the panelBar and not to remove it. Also, isn't it pretty consistent that the close button removes the panelBar and gives access to what's beneath: in iFrame mode the pure panel?

Ahh, I get your idea about this.
What makes it confusing is this. When on frontend the panelbar feels like a minimal version of the panel (the real panel). When in edit mode the panelbar still feels like the panel.
When closing what we feel is the panel, on frontend or backend, I expected it to close the panel (including panelbar) and get back to the frontend. Do you understand what I'm getting at? That the panel and panelbar feels like the same thing and that the frontend are always below.
As for the function the X does not do the same thing. On the frontend it hides the panelbar. In backend it redirects to the panel which is a completly different thing, because then you are at another url and not in frontend anymore and there is no way to get the panelbar back (except for preview in panel). That's why I also think the consistancy fail.
In my eyes it does:

Does not do what I expect
Does not do the same as the same icon on the frontend

Maybe just think about it one more time before closing it?

The pin-icon I suggested was for the idea that the panelbar and the panel feels bundled together, the same thing. In that perspective you don't pin the panelbar, you pin the panel. As a user I don't see a bar in admin-mode, just the panel.

Fair enough. Just added it to the v1 develop branch.


Delay when searching inside extension pages

Issue Type: Bug

Open an extension page
Bring up search by shortcut, then immediately start typing something

You'll see that your first character is missing, assuming you type fast enough. This happens because VSCode does not give the search field focus before the animation is finished. When searching within the editor, this is not an issue, as the search field gains focus before the animation starts.

When you press cmd/ctrl+f, do you see that the search field doesn't immediately get focused? You should be able to tell by the border around the search field lighting up.

It seems to be focused immediately for me. I assume when you say "extension page" you mean the page that's opened when you click an extension in the extension viewlet.

Search feature is coming from markdown/webview editor.

@roblourens Yes, it's the page opened when you click an extension in the extension viewlet.
Apparently the issue exists in the terminal as well.
Video: https://youtu.be/iVV4nBCuoYs
Slow down the speed to 0.25, and you'll see that the search field is coming before I start typing.

Oh, I do see this now.

Press cmd+f
Immediately start typing

In the editor, all the characters show up in the find widget. In the terminal and webview find, it doesn't get characters until the animation is finished. You would have to have very fast reflexes to hit this in real life. But now that I've noticed it I may never "unnotice" it...

For verification: also test this with the markdown preview and in the release notes view


Add Pandora.js

I finally made a Node.js implementation, and this time it uses the REST api :)

Oops, it's still private. Give me a minute to make it public.

Alright, it's public now.

Merged as eb4f811c2a6e4ab3be0b2916828f69d2fbca96ae
Thanks!


TypeScript compilation problem with angular 5.0.5

Hi and thanks for your plugin ;)
I met a problem when i want to "ng serve" my app since i upgrated to angular 5.0.5 :

ERROR in ./node_modules/humanize-duration-ts/humanize-duration-ts.ts
Module build failed: Error: C:\ProjetsGIT\perso\SortieSportGit\SortieSportProfessionnel\node_modules\humanize-duration-ts\humanize-duration-ts.ts is missing from the TypeScript compilation. Please make sure it is in your tsconfig via the 'files' or 'include' property.
The missing file seems to be part of a third party library. TS files in published libraries are often a sign of a badly packaged library. Please open an issue in the library repository to alert its author and ask them to package the library using the Angular Package Format (https://goo.gl/jB3GVv).
    at AngularCompilerPlugin.getCompiledFile (C:\ProjetsGIT\perso\SortieSportGit\SortieSportProfessionnel\node_modules\@ngtools\webpack\src\angular_compiler_plugin.js:653:23)
    at plugin.done.then (C:\ProjetsGIT\perso\SortieSportGit\SortieSportProfessionnel\node_modules\@ngtools\webpack\src\loader.js:467:39)
    at process._tickCallback (internal/process/next_tick.js:109:7)
 @ ./src/app/sortiesport/pages/sortie/sortie-form/sortie-form.page.ts 26:29-81
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi webpack-dev-server/client?http://<IP_ADDRESS>:0 ./src/main.ts

Anybody out there to fix this?

I'm updating the library at the moment. A new version should be released soon.

@toregua @canerelci Please try version 2.0.0


Feature: Switch focus to Files when using win+e

Description
I have Files as my default file explorer. If an active Files window is in the background, when I press Win + E there will be no visual reactions, since Files opens a new tab silently. Also, if Files is called by another program (e.g. "open in folder" in my browser downloads), it also doesn't automatically goes to foreground.
Steps To Reproduce

Set Files as default file explorer
Open Files
Switch to another application
Press Win + E

Steps to fix
When Win + E is pressed, make Files pop up to foreground if there's an active Files window.
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22623.1037
Windows Version
Windows 11 22H2 22623.1037
Relevant Assets/Logs
Screen record:

Recent logs:
2022-12-09 19:28:35.2484|INFO|OnActivated|App activated by Protocol
2022-12-09 19:28:35.9142|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-09 19:28:37.5409|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-09 22:12:46.8942|INFO|OnActivated|App activated by Protocol
2022-12-09 22:12:47.1341|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-09 22:12:47.1927|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-09 22:12:47.2283|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-09 22:12:47.5623|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-09 22:12:48.9463|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-09 22:12:53.0367|INFO|IsRunningOnArm|Running on ARM: False
2022-12-10 23:41:57.8140|INFO|OnActivated|App activated by Protocol
2022-12-10 23:41:58.5112|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-10 23:42:01.1185|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-10 23:42:54.6423|WARN|OnActivated|Error during InitializeAppComponentsAsync()
	System.AggregateException: One or more errors occurred. (Exception from HRESULT: 0x80240438) ---> System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103

   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103
<---

2022-12-10 23:44:12.4000|INFO|OnActivated|App activated by Protocol
2022-12-10 23:44:12.5057|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-10 23:44:13.6254|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-11 10:39:30.2425|INFO|OnActivated|App activated by Protocol
2022-12-11 10:39:30.5090|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-11 10:39:30.7191|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-11 10:39:30.7526|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-11 10:39:30.9347|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-11 10:39:31.1870|INFO|IsRunningOnArm|Running on ARM: False
2022-12-11 10:39:34.9326|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-11 12:19:06.0290|INFO|IgnoreExceptions|拒绝访问。

	System.UnauthorizedAccessException: 拒绝访问。

   at System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32, RuntimeTypeHandle) + 0x21
   at __Interop.ComCallHelpers.Call(__ComObject, RuntimeTypeHandle, Int32, Void*) + 0xbe
   at __Interop.ForwardComStubs.Stub_3[TThis, TResult](__ComObject, Int32) + 0x37
   at Files.Uwp.App.<>c.<OnSuspending>b__94_1() + 0x2e
   at System.Action.Invoke() + 0x25
   at Files.Shared.Extensions.SafetyExtensions.IgnoreExceptions(Action, ILogger) + 0x22

2022-12-11 23:04:37.9825|INFO|OnActivated|App activated by Protocol
2022-12-11 23:04:38.7901|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-11 23:04:38.8426|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-11 23:04:38.9008|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-11 23:04:39.2362|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-11 23:04:39.4232|INFO|IsRunningOnArm|Running on ARM: False
2022-12-11 23:04:43.9894|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 13:18:57.2581|INFO|OnActivated|App activated by Protocol
2022-12-12 13:18:57.5471|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 13:18:57.6216|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 13:18:57.6756|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 13:18:58.4070|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 13:18:58.6014|INFO|IsRunningOnArm|Running on ARM: False
2022-12-12 13:19:03.7245|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 20:22:28.7996|INFO|OnActivated|App activated by Protocol
2022-12-12 20:22:29.1314|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 20:22:29.1972|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 20:22:29.2573|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 20:22:30.1768|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 20:22:30.3247|INFO|IsRunningOnArm|Running on ARM: False
2022-12-12 20:22:35.6762|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 20:22:48.5246|INFO|OnActivated|App activated by Protocol
2022-12-12 20:22:48.6603|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 20:22:49.8978|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 20:23:04.6316|WARN|OnActivated|Error during InitializeAppComponentsAsync()
	System.AggregateException: One or more errors occurred. (Exception from HRESULT: 0x80240438) ---> System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103

   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103
<---

2022-12-12 20:23:08.5982|INFO|OnActivated|App activated by Protocol
2022-12-12 20:23:08.9549|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 20:23:10.3733|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:06:16.2761|INFO|OnActivated|App activated by Protocol
2022-12-12 21:06:16.6440|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:06:16.6899|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:06:16.7573|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:06:16.8020|INFO|GetDrivesAsync|Drive added: G:\, Fixed
2022-12-12 21:06:16.8411|INFO|GetDrivesAsync|Drive added: H:\, Fixed
2022-12-12 21:06:17.6059|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:06:20.0580|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:06:51.9841|WARN|OnActivated|Error during InitializeAppComponentsAsync()
	System.AggregateException: One or more errors occurred. (Exception from HRESULT: 0x80240438) ---> System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103

   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103
<---

2022-12-12 21:06:58.3492|INFO|Watcher_Removed|Drive removed: \\?\STORAGE#Volume#{27708016-5203-11ed-9a77-b0a460fe57ef}#0000007370A00000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
2022-12-12 21:07:22.3852|INFO|OnActivated|App activated by Protocol
2022-12-12 21:07:22.6088|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:07:22.9030|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:07:22.9509|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:07:22.9938|INFO|GetDrivesAsync|Drive added: G:\, Fixed
2022-12-12 21:07:23.1705|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:07:25.6815|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:14:31.8040|INFO|OnLaunched|App launched. Prelaunch: False
2022-12-12 21:14:32.9241|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:14:33.2907|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:14:33.3424|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:14:33.3977|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:14:37.0974|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:14:37.1285|INFO|IsRunningOnArm|Running on ARM: False
2022-12-12 21:23:52.7969|INFO|Watcher_Added|Drive added: G:\, Fixed
2022-12-12 21:23:53.7343|INFO|OnActivated|App activated by Protocol
2022-12-12 21:23:54.2744|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:23:55.9858|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:25:11.4098|INFO|OnActivated|App activated by Protocol
2022-12-12 21:25:11.5914|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:25:12.4736|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:30:36.1012|INFO|Watcher_Removed|Drive removed: \\?\STORAGE#Volume#{27708016-5203-11ed-9a77-b0a460fe57ef}#0000000000007E00#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
2022-12-12 21:30:42.1235|INFO|Watcher_Added|Drive added: G:\, Fixed
2022-12-12 21:30:43.1846|INFO|OnActivated|App activated by Protocol
2022-12-12 21:30:43.2934|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:30:44.3668|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:38:26.3425|WARN|Watcher_Added|System.UnauthorizedAccessException: Attempting to add the device, Ugreen Storage Device, failed at the StorageFolder initialization step. This device will be ignored. Device ID: \\?\STORAGE#Volume#{a3c24399-79ed-11ed-9a89-b0a460fe57f3}#0000006296800000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
2022-12-12 21:38:26.6296|INFO|HandleWin32DriveEvent|Drive added from fulltrust process: E:\, Fixed
2022-12-12 21:40:21.5142|INFO|OnLaunched|App launched. Prelaunch: False
2022-12-12 21:40:21.8988|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:40:21.9645|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:40:22.0032|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:40:22.0404|INFO|GetDrivesAsync|Drive added: G:\, Fixed
2022-12-12 21:40:22.1131|WARN|Watcher_Added|System.UnauthorizedAccessException: Attempting to add the device, Ugreen Storage Device, failed at the StorageFolder initialization step. This device will be ignored. Device ID: \\?\STORAGE#Volume#{a3c24399-79ed-11ed-9a89-b0a460fe57f3}#0000006296800000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
2022-12-12 21:40:22.6570|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:40:25.2973|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:40:25.3646|INFO|IsRunningOnArm|Running on ARM: False
2022-12-12 21:40:42.7531|WARN|Watcher_Added|System.UnauthorizedAccessException: Attempting to add the device, Ugreen Storage Device, failed at the StorageFolder initialization step. This device will be ignored. Device ID: \\?\STORAGE#Volume#{a3c24399-79ed-11ed-9a89-b0a460fe57f3}#0000006296800000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
2022-12-12 21:40:52.6166|WARN|OnLaunched|Error during InitializeAppComponentsAsync()
	System.AggregateException: One or more errors occurred. (Exception from HRESULT: 0x80240438) ---> System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103

   --- End of inner exception stack trace ---
---> (Inner Exception #0) System.Exception: Exception from HRESULT: 0x80240438
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.ServicesImplementation.UpdateService.<GetUpdatePackages>d__21.MoveNext() + 0x188
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.ServicesImplementation.UpdateService.<CheckForUpdates>d__19.MoveNext() + 0xc6
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
   at Files.Uwp.App.<InitializeAppComponentsAsync>d__84.MoveNext() + 0x103
<---

2022-12-12 21:46:43.3369|INFO|OnActivated|App activated by Protocol
2022-12-12 21:46:43.6284|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:46:44.1944|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:46:44.2603|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-12 21:46:44.3184|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:46:44.3758|INFO|GetDrivesAsync|Drive added: G:\, Fixed
2022-12-12 21:46:44.4562|WARN|Watcher_Added|System.UnauthorizedAccessException: Attempting to add the device, Ugreen Storage Device, failed at the StorageFolder initialization step. This device will be ignored. Device ID: \\?\STORAGE#Volume#{a3c24399-79ed-11ed-9a89-b0a460fe57f3}#0000006296800000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
2022-12-12 21:46:44.6450|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:46:47.1550|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:46:47.8724|INFO|IsRunningOnArm|Running on ARM: False
2022-12-12 21:54:04.3021|INFO|OnLaunched|App launched. Prelaunch: False
2022-12-12 21:54:05.5401|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:54:05.6342|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:54:05.7909|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-12 21:54:05.9164|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:54:06.4800|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:54:18.2051|INFO|IgnoreExceptions|拒绝访问。

	System.UnauthorizedAccessException: 拒绝访问。

   at System.Runtime.InteropServices.McgMarshal.ThrowOnExternalCallFailed(Int32, RuntimeTypeHandle) + 0x21
   at __Interop.ComCallHelpers.Call(__ComObject, RuntimeTypeHandle, Int32, Void*) + 0xbe
   at __Interop.ForwardComStubs.Stub_3[TThis, TResult](__ComObject, Int32) + 0x37
   at Files.Uwp.App.<>c.<OnSuspending>b__94_1() + 0x2e
   at System.Action.Invoke() + 0x25
   at Files.Shared.Extensions.SafetyExtensions.IgnoreExceptions(Action, ILogger) + 0x22

2022-12-12 21:54:18.7513|WARN|SendMessageForResponseAsync|Error sending request on pipe.
	System.Threading.Tasks.TaskCanceledException: A task was canceled.
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xad
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
   at Files.Uwp.Helpers.NamedPipeAsAppServiceConnection.<SendMessageForResponseAsync>d__11.MoveNext() + 0x24d

2022-12-12 21:54:18.7921|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:55:55.6101|INFO|OnActivated|App activated by Protocol
2022-12-12 21:55:56.2418|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:55:56.9626|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:55:57.5205|INFO|IsRunningOnArm|Running on ARM: False
2022-12-12 21:57:14.6530|INFO|OnActivated|App activated by Protocol
2022-12-12 21:57:14.8595|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-12 21:57:14.8963|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-12 21:57:14.9293|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-12 21:57:14.9613|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-12 21:57:15.3501|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:57:16.4188|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-12 21:57:42.8940|INFO|OnActivated|App activated by Protocol
2022-12-12 21:57:43.0721|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-12 21:57:43.8339|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 12:21:19.3508|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-13 12:21:20.0261|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-13 12:21:20.0403|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-13 12:21:20.0786|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-13 12:21:20.1077|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-13 12:21:20.1443|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-13 12:21:22.3342|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 12:21:26.6920|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-13 12:21:27.0616|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-13 12:21:27.0988|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-13 12:21:27.2761|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-13 12:21:27.2938|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-13 12:21:27.3265|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-13 12:21:28.9667|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 12:21:55.2243|INFO|IsRunningOnArm|Running on ARM: False
2022-12-13 12:22:40.2465|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-13 12:22:40.6053|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-13 12:22:40.6328|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-13 12:22:40.6695|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-13 12:22:40.6975|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-13 12:22:40.7144|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-13 12:22:42.5196|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 12:22:43.2232|INFO|IsRunningOnArm|Running on ARM: False
2022-12-13 14:03:44.9112|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-13 14:03:45.2939|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-13 14:03:45.3247|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-13 14:03:45.3627|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-13 14:03:45.3829|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-13 14:03:45.4059|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-13 14:03:47.2590|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 14:03:48.2394|INFO|IsRunningOnArm|Running on ARM: False
2022-12-13 20:51:14.6071|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-13 20:51:15.0947|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-13 20:51:15.1320|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-13 20:51:15.1976|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-13 20:51:15.2311|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-13 20:51:15.2591|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-13 20:51:17.5963|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 20:51:29.1401|INFO|IsRunningOnArm|Running on ARM: False
2022-12-13 20:52:15.3629|WARN|OnLaunched|Error during InitializeAppComponentsAsync()
	System.AggregateException: One or more errors occurred. (0x80240438)
 ---> System.Runtime.InteropServices.COMException (0x80240438): 0x80240438
   at Files.App.ServicesImplementation.UpdateService.GetUpdatePackages()
   at Files.App.ServicesImplementation.UpdateService.CheckForUpdates()
   at Files.App.App.InitializeAppComponentsAsync()
   --- End of inner exception stack trace ---
2022-12-13 23:05:27.2210|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-13 23:05:27.6623|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-13 23:05:27.6975|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-13 23:05:27.7538|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-13 23:05:27.7778|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-13 23:05:27.8035|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-13 23:05:30.1999|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-13 23:05:30.3534|INFO|IsRunningOnArm|Running on ARM: False
2022-12-14 21:24:37.7457|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-14 21:24:38.1829|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-14 21:24:38.2394|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-14 21:24:38.2929|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-14 21:24:38.3318|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-14 21:24:38.3572|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-14 21:24:40.7812|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-14 21:24:45.2806|INFO|IsRunningOnArm|Running on ARM: False
2022-12-15 10:23:55.2505|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-15 10:23:55.6736|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-15 10:23:55.7223|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-15 10:23:56.1313|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-15 10:23:56.1543|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-15 10:23:56.2949|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-15 10:23:57.3248|INFO|IsRunningOnArm|Running on ARM: False
2022-12-15 10:23:58.1174|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-15 10:24:13.0926|INFO|CheckForUpdates|STORE: Update found.
2022-12-15 10:24:20.6389|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-15 10:25:35.4002|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-15 10:25:38.2955|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-15 10:36:44.1288|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-15 10:36:44.5576|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-15 10:36:44.6066|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-15 10:36:44.6523|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-15 10:36:44.6820|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-15 10:36:44.7060|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-15 10:36:46.6223|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-15 10:36:47.9937|INFO|CheckForUpdates|STORE: Update found.
2022-12-15 10:36:48.6259|INFO|IsRunningOnArm|Running on ARM: False
2022-12-18 11:25:59.0541|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-18 11:25:59.7119|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-18 11:25:59.7209|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-18 11:25:59.7476|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-18 11:25:59.7820|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-18 11:25:59.8164|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-18 11:26:01.8318|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-18 11:26:29.2662|WARN|OnLaunched|Error during InitializeAppComponentsAsync()
	System.AggregateException: One or more errors occurred. (0x80240438)
 ---> System.Runtime.InteropServices.COMException (0x80240438): 0x80240438
   at Files.App.ServicesImplementation.UpdateService.GetUpdatePackages()
   at Files.App.ServicesImplementation.UpdateService.CheckForUpdates()
   at Files.App.App.InitializeAppComponentsAsync()
   --- End of inner exception stack trace ---
2022-12-20 11:00:41.5622|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-20 11:00:42.2815|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-20 11:00:42.2901|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-20 11:00:42.3314|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-20 11:00:42.3663|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-20 11:00:42.3902|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-20 11:00:44.6944|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-20 11:00:50.6673|INFO|CheckForUpdates|STORE: Update found.
2022-12-20 13:57:27.2322|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-20 13:57:27.6830|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-20 13:57:27.7198|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-20 13:57:27.7704|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-20 13:57:27.7982|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-20 13:57:27.8188|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-20 13:57:29.0744|INFO|IsRunningOnArm|Running on ARM: False
2022-12-20 13:57:30.1360|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-20 13:57:35.0121|INFO|CheckForUpdates|STORE: Update found.
2022-12-21 23:54:02.7717|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-21 23:54:03.6503|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-21 23:54:03.7860|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-21 23:54:03.8202|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-21 23:54:03.8459|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-21 23:54:04.1045|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-21 23:54:06.1932|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-21 23:54:10.5781|INFO|IsRunningOnArm|Running on ARM: False
2022-12-21 23:54:10.9638|INFO|CheckForUpdates|STORE: Update found.
2022-12-22 00:33:20.1822|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-23 14:40:59.1389|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-23 14:41:00.2820|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-23 14:41:00.4320|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-23 14:41:00.4462|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-23 14:41:00.4564|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-23 14:41:00.4779|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-23 14:41:02.0946|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-23 14:41:03.7358|INFO|IsRunningOnArm|Running on ARM: False
2022-12-23 14:41:13.3507|INFO|CheckForUpdates|STORE: Update found.
2022-12-23 14:44:01.2861|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-23 14:44:01.7133|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-23 14:44:01.7451|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-23 14:44:01.7912|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-23 14:44:01.8310|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-23 14:44:01.8519|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-23 14:44:04.0015|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-23 14:44:04.7031|INFO|IsRunningOnArm|Running on ARM: False
2022-12-23 14:44:04.8638|INFO|CheckForUpdates|STORE: Update found.
2022-12-24 21:28:16.1795|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-24 21:28:16.7859|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-24 21:28:17.3573|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-24 21:28:17.7371|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-24 21:28:17.7870|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-24 21:28:17.8640|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-24 21:28:19.1547|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-24 21:30:13.4848|INFO|IsRunningOnArm|Running on ARM: False
2022-12-25 08:45:57.0775|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-25 08:45:57.4692|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-25 08:45:57.8131|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-25 08:45:57.8374|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-25 08:45:57.8542|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-25 08:45:57.8711|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-25 08:45:58.7923|INFO|IsRunningOnArm|Running on ARM: False
2022-12-25 08:46:02.5570|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-26 20:22:38.8338|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:22:44.2605|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:22:47.1303|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:23.7889|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:27.6840|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:29.0603|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:32.0604|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:35.6288|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:45.9896|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:48.4724|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:50.1650|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:28:56.1842|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:29:46.2167|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:29:50.3254|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:31:38.2518|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:31:41.8084|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:31:44.2808|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:31:46.0963|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:31:47.3284|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:31:48.6335|INFO|OnLaunched|App launched. Launch args type: LaunchActivatedEventArgs
2022-12-26 20:31:49.1493|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-26 20:31:49.1692|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-26 20:31:49.1835|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-26 20:31:49.2126|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-26 20:31:49.2350|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-26 20:31:51.3443|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-26 20:32:07.0138|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-26 20:32:07.4133|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-26 20:32:07.7905|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-26 20:32:07.8150|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-26 20:32:07.8329|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-26 20:32:07.8501|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-26 20:32:09.5177|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-26 20:32:10.9380|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:32:16.3178|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-26 20:32:16.7063|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-26 20:32:16.7391|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-26 20:32:16.7808|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-26 20:32:16.8037|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-26 20:32:16.8289|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-26 20:36:12.5532|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-26 20:36:12.9767|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-26 20:36:12.9877|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-26 20:36:13.0396|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-26 20:36:13.0675|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-26 20:36:13.0873|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-26 20:36:52.1887|INFO|OnLaunched|App launched. Launch args type: ProtocolActivatedEventArgs
2022-12-26 20:36:52.6104|INFO|UpdateDrivesAsync|Adding cloud provider "OneDrive" mapped to C:\Users\anoti\OneDrive
2022-12-26 20:36:52.6187|INFO|GetDrivesAsync|Drive added: C:\, Fixed
2022-12-26 20:36:52.6589|INFO|GetDrivesAsync|Drive added: D:\, Fixed
2022-12-26 20:36:52.6962|INFO|GetDrivesAsync|Drive added: E:\, Fixed
2022-12-26 20:36:52.7180|INFO|GetDrivesAsync|Drive added: F:\, Fixed
2022-12-26 20:36:54.6336|INFO|CheckForUpdates|STORE: Checking for updates...
2022-12-26 20:36:55.1986|INFO|OnActivated|App activated. Activated args type: ProtocolActivatedEventArgs
2022-12-26 20:38:13.9356|INFO|IsRunningOnArm|Running on ARM: False

I think it only pops to foreground when it's first opened, not when there is already an open window.

What happens if you toggle the default file manager option off and back on?

@hecksmosis So it is not implemented yet, and this issue should be tagged as a feature request?
The Windows built-in explorer has this feature, maybe Files as an alternative should also support it.

@yaira2 I already tried when posting this issue, didn't solve the problem

I don't know to that extent this should be considered a bug @yaira2

It's a feature request 👍

Thank you for reporting this issue, this seem to be an issue in WinAppSdk https://github.com/microsoft/microsoft-ui-xaml/issues/7595, but there are probably workarounds we can try.


Add doc to Hash select methods - splat variants

n/c

Maybe we should just ditto them?

@jhass But then the code sample would not fit.
In fact, the example for select(keys : Array | Tuple) is actually demonstrating select(*keys) 🤦♂

For cases like this I wouldn't mind to have code samples demonstrating all the overloads on the first one and the others just dittoing them.

Yeah, that's probably fine.

We might even consider some kind of combined presentation for methods with the same (ditto) combination. But that's not particularly important.

@jan-zajic Would you mind adding a usage example for each select(keys : Array | Tuple) and select!(*keys) to the dittoed doc string?

@straight-shoota like this?

Needs a format before being able to merge.

@straight-shoota it's done.


SGDK is not running on Mega Drive / Sega Genesis

When compiling the code with the Release version (1.90) of SGDK and writing it to a cartridge, everything works. However, when writing the same code in the Master branch version of SGDK, the video game cannot run the rom.
In the emulator everything works normally, tested in Kega Funsion and KGens.
Tested hardware:

Mega Drive 3 - Tectoy with Sega CD input
Observation:
Mega Drive 3 - Tectoy is equivalent to the American Sega Genesis 2

Both Kega nor Gens are accurate emulators, Better to use BlastEm.
About the issue, without more information it's impossible to sort out the problem as it's all working for me (SGDK samples does work).
Did you properly rebuilt the library with the last sources then did a full rebuild of your project ?

I recompiled the lib and the entire project, I even have some build scripts that delete the outputs from the out folder, ensuring that the solution is always recompiled.
I did some tests earlier, I noticed that part of the problem occurred when I compiled from MARSDEV on my Linux machine, compiling from a Windows machine, using only the SGDK, what happens is the following.
The game does not load, the entire screen is stuck showing only the first tile of BG_A. I'm going to try to redo the tests with Blastem to see if I can catch any logs or errors that will help shed some light, in the other emulators there are no errors.
Note: When I discovered the error, I returned my SGDK to version 1.90, took the changes from the commit, and isolated only what related to the SPR_getAnimationDone and SPR_setAnimationLoop functions and applied them to the release 1.90 source. After recompiling the lib and the game, everything started working again (at least generating the build on Windows).
I'll try to do a battery of tests and see if I find anything.

No Error's in BlastEm, everthing working from every build made both in Windows and Linux machine, with SGDK from main.
I will try another test pulling all corrections from the commit into 1.90 branch.

No Error's in BlastEm, everthing working from every build made both in Windows and Linux machine, with SGDK from main. I will try another test pulling all corrections from the commit into 1.90 branch.

Do you mean it works correctly from last changes in "main" branch ?
At least I can't find any issues when building and testing all samples from main branch in my case


Add flag to the compiler to build std library (no user visible change)

Description of changes:
When building the standard library, we cannot assume that Kani elements or standard library elements are available. This flag allow us to control that.
Resolved issues:
N/A
Related RFC:
Call-outs:
This is related to the bitmask work.
Testing:

How is this change tested? Existing tests

Is this a refactor change?

Checklist

[ ] Each commit message has a non-empty body, explaining why the change was made
[ ] Methods or procedures are documented
[ ] Regression or unit tests are included, or existing tests cover the modified code
[ ] My PR is restricted to a single feature or bugfix

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

I'm not sure I see what this change is doing. Can you expand the description and/or the comments in the code to clarify?

I'm not sure I see what this change is doing. Can you expand the description and/or the comments in the code to clarify?

I updated the description. Let me know if that makes sense now.

Yes, it does. Thanks!


We need another meeting!

We are way overdue for another meeting. 4.x has been out for awhile now, and @nodejs/website has the keys to nodejs.org now. We need to coordinate with the Website WG to get what we've got onto the website and do something about the collaboration-unfriendly state the repo is currently in.
I've put together a doodle to find a time next week: http://doodle.com/poll/8wwpw97f62gpawrx
The agenda doc is here, please suggest more stuff to discuss:
https://docs.google.com/document/d/1TdP8dKDy24nM3Scv9I-NN-RsFbuveX8Foys01SCh-bw/edit?usp=sharing
@nodejs/documentation @nodejs/website

We shouldn't default to a meeting when things aren't moving along. Ideally
meetings are held to resolve disagreement when it exists but the issues
you've brought up have just started being discussed and may be able to be
resolved without a meeting. I'm not saying you won't need a meeting at some
point but you should enter the meeting with competing solutions to the
problems you're raising and I haven't seen those proposals in the issues
yet. I'm pretty sure you have some ideas on how to fix these and I think
you should post them as new issues, referencing the issues where the
problems have been discussed. If there is no disagreement with those
solutions then we can implement them w/o a meeting ;)
On Tuesday, October 6, 2015, Stephen Belanger<EMAIL_ADDRESS>wrote:

We are way overdue for another meeting. 4.x has been out for awhile now,
and @nodejs/website https://github.com/orgs/nodejs/teams/website has
the keys to nodejs.org now. We need to coordinate with the Website WG to
get what we've got onto the website and do something about the
collaboration-unfriendly state the repo is currently in.
I've put together a doodle to find a time next week:
http://doodle.com/poll/8wwpw97f62gpawrx
The agenda doc is here, please suggest more stuff to discuss:
https://docs.google.com/document/d/1TdP8dKDy24nM3Scv9I-NN-RsFbuveX8Foys01SCh-bw/edit?usp=sharing
@nodejs/documentation https://github.com/orgs/nodejs/teams/documentation
@nodejs/website https://github.com/orgs/nodejs/teams/website
—
Reply to this email directly or view it on GitHub
https://github.com/nodejs/docs/issues/43.

True, but I feel like we really need to get everyone on the same page. There was a bunch of activity and then silence for awhile. The problem with async communication like github issues is that it's too easy to procrastinate responding/acting. My hope is that, by planning a meeting, I can get people on a call together and sort through the issues all at once.
What do you think? A time-boxed issue might also work.

Maybe start with a time boxed issue because if you cant get engagement on
that I doubt you can get the doodle filled out for a meeting :(
On Tuesday, October 6, 2015, Stephen Belanger<EMAIL_ADDRESS>wrote:

True, but I feel like we really need to get everyone on the same page.
There was a bunch of activity and then silence for awhile. The problem with
async communication like github issues is that it's too easy to
procrastinate responding/acting. My hope is that, by planning a meeting, I
can get people on a call together and sort through the issues all at once.
What do you think? A time-boxed issue might also work.
—
Reply to this email directly or view it on GitHub
https://github.com/nodejs/docs/issues/43#issuecomment-146042376.


Error: read ECONNRESET

Hi, i have this error when i lunch my crawler for Vinted website.
But i have this error a lot of time :
first i have this :
Error: getaddrinfo ENOTFOUND www.vinted.fr www.vinted.fr:443
Then
...
Error: read ECONNRESET
Error: read ECONNRESET
Error: read ECONNRESET
Error: read ECONNRESET
Error: read ECONNRESET
...

and sometimes
Error: socket hang up
Error: socket hang up
Error: socket hang up

But my crawler works and return me the good results for some products and stop after 10 min about.
I think is because i send too much resquest but i need it ...
I am completely stuck with all these error
Thanks for your help.

This doesn't sound related to Express. For general questions, I'd recommend posting on StackOverflow.


govendor fetch ^ fails if package uses vendoring

govendor fetch calls that use ^ on packages that themselves have a vendor directory consistently fail:
➜  goapp git:(master) govendor init
➜  goapp git:(master) ✗ govendor fetch github.com/cloudflare/cfssl/^
Error: Failed to fetch package "github.com/cloudflare/cfssl": copy failed. dest: "/Volumes/git/go/src/github.com/nmiyake/goapp/vendor/github.com/cloudflare/cfssl", src: "/Volumes/git/go/.cache/govendor/github.com/cloudflare/cfssl", pkgPath "/Volumes/git/go/.cache/govendor", err open /Volumes/git/go/src/github.com/nmiyake/goapp/vendor/github.com/GeertJohan/go.rice/LICENSE: no such file or directory

Every repo that I've tried with a vendor folder so far has failed:

github.com/cloudflare/cfssl/^
github.com/aws/aws-sdk-go/^
github.com/nmiyake/govendortest/^

This issue is a more general version of #168

Thanks for the report. This is reflected in two other issues and a PR. I'll have a fix soon.


Enterprise administrators can assume Organization ownership

Summary
GitHub Enterprise Ownership has been built in layers over the years from repos to orgs to enterprise accounts. It can be difficult for administrators across companies to govern all of these entities together.
To address this, and as the follow-up to #526, we will enable enterprise admins to assume the organization owner role in organizations owned by their enterprise account.
Intended Outcome
Enterprise Admins can assume ownership of an org to audit and apply policies and security controls, and ensure that no organizations are left in an unowned state.
How will it work?
Enterprise Admins will be able to navigate to the organization view within the Enterprise Account and select an option on the organization card to Become Organization Owner.

Shipped to dotcom! https://github.blog/changelog/2022-03-02-enterprise-owners-can-assume-organization-ownership/


Lamda Body implicity operator should break

Currently formats like
public static implicit operator string(Person p) => p.First + " " + p.Last;

But should be like
public static implicit operator string(Person p)
    => p.First + " " + p.Last;

Lamda body methods break this way already and I thought operators and methods uses the same formatting code.

False alarm, they do break. This just happened to be right before the character limit.


Fix for Platform < 21

Noticed that version 2.6.0 no longer worked on my 4.4 Android, so here's the fix.
Hope it helps.

Good!


Functionality of StandardResolver.AllowPrivate

Hi,
AllowPrivate currently solves two problems which might conflict:

You can serialize private/protected members
You can deserialize private/protected members, including private/protected setters

The example at the bottom serializes the empty Dictionary
"{\"Id\":\"b63cff84-e203-4b97-8c71-bf95f099b26d\",\"Dictionary\":{}}"

and fails during deserialization because GUID is not supported as Key. Which is perfectly fine.
The original intention was that not Dictionary is serialized, but the protected setter of Id can be used, But since AllowPrivate serializes the protected field Dictionary too, I need to annotate it with [IgnoreDataMember] so it won't get serialized.
It might be more useful to split the StandardResolver configuration in multiple parts:

IncludeProperties (default, can be skipped, but should be an independent configuration anyway)
IncludeFields
AllowPrivate

What I'm suggesting is, that you need an extra level of configuration called AllowFields which serializes fields.
This results in the following basic combinations:

StandardResolver.IncludeProperties: Default, serializes public properties
StandardResolver.IncludePropertiesAllowPrivate: Serializes Properties, including private/protected properties including private/protected setters/getters
StandardResolver.IncludeFields: Only serializes public fields
StandardResolver.IncludeFieldsAllowPrivate: Only serializes fields, including private protected
StandardResolver.IncludePropertiesIncludeFieldsAllowPrivate: Serializes private/protected/public fields and properties

Obviously this gets quite a bit longer with ExcludeNull, NameMutate functionality etc.
So it might be useful to put all those options in an enum annotated with [Field] and add a factory method creating the proper StandardResolver from this enum (e.g. CreateJsonFormatterResolver(enum)) and cache it in a static field somewhere. Then you can simply build your own formatter bases on the enum, e.g. IncludeProperties | IncludeFields | ExcludeNull | AllowPrivate | CamelCase (which would then serialize all private/protected/public fields/properties which are not null into camel case.
I understand this configuration might be a breaking change to the current AllowPrivate behaviour.
    class Program
    {
        static void Main(string[] args)
        {
            MyTest t = new MyTest();
            t.SetId(Guid.NewGuid());

            var output = JsonSerializer.ToJsonString(t, StandardResolver.AllowPrivate);
            var input = JsonSerializer.Deserialize<MyTest>(output, StandardResolver.AllowPrivateExcludeNull);
            Debug.Assert(t.Id == input.Id);
        }
    }

    public abstract class TestBase
    {
        protected Dictionary<Guid, String> Dictionary = new Dictionary<Guid, string>();
        public Guid Id { get; protected set; }
    }

    public class MyTest : TestBase
    {
        public void SetId(Guid id)
        {
            Id = id;
        }
    }

for the dictionar keys, Utf8Json requires IObjectPropertyNameFormatter.
https://github.com/neuecc/Utf8Json/blob/master/src/Utf8Json/IJsonFormatter.cs#L18
GuidFormatter does not implement it so can not deserialize.
Some formatters(Guid, DateTime, etc...) does not implement so I'll implement it.

Your proposal seems to very complicated for users.
We should use [IgnoreDataMember].
However, there are certain problems that can not separate getter and setter.
I'll add custom attribute like this.
public abstract class TestBase
{
    protected Dictionary<Guid, String> Dictionary = new Dictionary<Guid, string>();
    public Guid Id
    {
        get;
        [IgnoreJsonMember]
        protected set;
    }
}

Is this ok?

In the example above my intentation was never to serialize Dictionary, it is just a byproduct of AllowPrivate.
I understand your reluctance regarding my proposal, I'm usually a fan of configuration options and not per member configuration via custom attributes because I then need to reference the serialization library in every project and adapt every model etc.
As for my problem, even annotating every private member I don't want to serialize via [IgnoreDataMember] solves it, but your suggestion with [IgnoreJsonMember]  to exclude certain properties which should not be deserialized is fine.


Rxjs warnings on build

Building Angular library from /attached-overlay/ng-package.json
'_finally' is imported from external module 'rxjs/operator/finally' but never used
'_catch' is imported from external module 'rxjs/operator/catch' but never used
'share' is imported from external module 'rxjs/operator/share' but never used
'switchMap' is imported from external module 'rxjs/operator/switchMap' but never used
'startWith' is imported from external module 'rxjs/operator/startWith' but never used
'takeUntil' is imported from external module 'rxjs/operator/takeUntil' but never used
Built Angular library from /attached-overlay/lib, written to /attached-overlay/dist/lib

Fixed by https://github.com/ncsu-sat/popover/pull/16


Add support for setting redis password with REDIS_PASSWORD

I'm trying to write Helm chart for Airflow using the docker-airflow container. The redis chart currently doesn't have a way to not set redis password and generates random password by default (https://github.com/kubernetes/charts/issues/249).
Even when it does have support for no password, would be useful to be able to set password.

thanks


Add history-beginning-search-forward-end and history-beginning-search-backward-end to ZSH_AUTOSUGGEST_CLEAR_WIDGETS

Fixes issues #678. Based on modifications suggested here https://github.com/zsh-users/zsh-autosuggestions/issues/619#issuecomment-904193190. @artudytu @ericfreese

I think this solution works, when will it be merged?

Thanks. I have cherry-picked the commit as 23f2943 with some slight modifications to also update the source file at src/config.zsh


3d coordinates

After using "rs2_deproject_pixel_to_point(upoint, &intr, upixel, udist)" to obtain 3d coordinates, x and z are very accurate, y error is more than ten centimeters, who can help me, thank you

Hi @picturedeeplover
What camera and version of software are you using?

I use SR300 and SDK2.0, and use the function of Intel RealSense SDK2.0 \samples\measure.

@picturedeeplover Which librealsense version are you using to see this issue?

@picturedeeplover One more question - how did you measure when get the issue? Could you please provide some snapshots of your testing?

@picturedeeplover Are you still having the issue? Please provide more information so that we can further check. Thanks!

Suppose I take the infrared camera as the origin, fix the camera, then put an object in front of the camera, and output the coordinates of a point, compared with my actual measurement, the result shows that the z direction is very accurate, and there is a big error in the x or y direction. About coordinates, I want someone to tell me what the origin is, the x and y direction, thank you.

Could you please provide the email address? I can show you the pictures.

@picturedeeplove  You can attach the picture here.

@picturedeeplover How was the camera fixed? Is it possible that there're some angles to cause the error?

The camera is simply horizontal and facing the target, and there may be a small error, but the error is far less than that. As for pictures, I failed to add them in the comments section.

@picturedeeplover Which librealsense version do you use?  Is the picture very large? Maybe you can compress it to try again. Thanks!

I've got a problem! Depth maps that are not aligned with the color map are accurate in 3d coordinates. Once aligned, the resolution becomes 1920*1080, and the 3d coordinates are inaccurate. Is there a solution? thank you

@picturedeeplover What's the resolution you configured for depth and color before align?

The default：Color 19201080 depth 640480

If you need you can try to align to depth.
rs2::align align_to_depth(RS2_STREAM_DEPTH);
When you align to color, the depth image will be modified. but the intrinsics of depth isn't changed.

@picturedeeplover Did you get chance to try align to depth? Looking forward to your update. Thanks!

@picturedeeplover Any update? Thanks!

Sorry, I am busy recently. Do you mean to align the color map with the depth map and reduce the resolution to 640*480? I have another problem, that is, the image rendered by the D435i camera using the color-map function cannot be displayed with Mat. Thank you

@picturedeeplover Did you see the issue if align to depth? Please create another ticket for the image display issue. Thanks!

@picturedeeplover Any update? Thanks!

@picturedeeplover Any other questions about this ticket? Thanks!

@picturedeeplover If no other questions, will close the ticket accordingly. Thanks!


Add backup encryption function

We still use olm in one place in Pipe to support encrypting room backups across different clients. This exposes the ability for us to run the encryption function via the Rust SDK instead which means we can stop using Olm entirely \o/

This is held up on me writing a sufficient test case on the other side, fwiw.


[package request] -

Package Request

I was wondering how to  make a PR,
How does one run the just new-version khal 0.11.3 command?
It uses  command m, whats this?


fix: check result of has lualine

Hi there,
I really like your Color scheme, It looks amazing!
So I fixed a little bug with lualine, if it is not installed (my case)
I hope it helps!

Hi there,
I really like your Color scheme, It looks amazing! So I fixed a little bug with lualine, if it is not installed (my case)
I hope it helps!

Thank you so much for the pull request! sorry i was sleeping so i have only seen it now. Merged into main!


bootstrap v3.3.5 DOM with [data-toggle='collapse'] cannot be toggled with class 'collapsed' properly [chrome 55.0.2883.87 ]

As is shown in https://jsfiddle.net/zhou9197/vs7x127p/

when set one data-target to button1, class collapsed CAN BE toggled to button1
when set two data-targets to button2, class collapsed CAN NOT BE toggled to button2

Is there any methods or workaround to fix it?

Closing because v3. Moreover, I don't believe we support, in v3 or v4, multiple targets from the same toggle.


Add missing Highlander Hybrid TSS2 fw

<!--- ***** Template: Car port *****

Adding a new firmware version for Ecu.esp for the CAR.HIGHLANDERH_TSS2.

The dealership updated the car's firmware due to a recent recall.

Then I got "Car Unrecognized: Dashcam Mode" error.

After adding the new firmware version (esp: 'fwVersion': b'\x01F152648J4000\x00\x00\x00\x00') to the CAR.HIGHLANDERH_TSS2 dictionary in the values.py, open
is working well again. I tested with master-ci branch.

Please provide the relevant DongleID/route.

Dongle id: 5f040438a009d6cb.
I just tested this on this routeID: 5f040438a009d6cb|2022-04-21--17-01-36.

Thank you Shane for directing me to this shred. However, I am an average guy with no programming experience. Can anyone walk me through what I need to do to get a working software on my Comma2 for my 2020 Highlander Hybrid? Truly appreciated!

Thank you Shane for directing me to this shred. However, I am an average guy with no programming experience. Can anyone walk me through what I need to do to get a working software on my Comma2 for my 2020 Highlander Hybrid? Truly appreciated!

Just run the cmds. I have pinned in the #toyota-lexus Discord channel, or see the conversations from Sunday morning where I helped resolve this for multiple people.

Thank you Shane for directing me to this shred. However, I am an average guy with no programming experience. Can anyone walk me through what I need to do to get a working software on my Comma2 for my 2020 Highlander Hybrid? Truly appreciated!

Just run the cmds. I have pinned in the #toyota-lexus Discord channel, or see the conversations from Sunday morning where I helped resolve this for multiple people.

Is this the page, I couldn't find the response. Thank you in advance. https://discord.com/channels/771493367246094347/771495215570747403

Is this the page, I couldn't find the response. Thank you in advance. https://discord.com/channels/771493367246094347/771495215570747403

Perhaps you aren't understanding where the pinned messages are, or how to find the #toyota-lexus channel.  It's past 1am here, so this is my final post for now, as it's pretty self-explanatory...

收到！


Better error checking in module loading

When modules paths are checked in go-script-bash/lib/internal/use basically the script tries to source them and if it fails, it just ends up on unknown module
if ! . "$_GO_CORE_DIR/lib/$__go_module_name" 2>/dev/null &&
! . "$_GO_SCRIPTS_DIR/plugins/${__go_module_name////lib/}" 2>/dev/null &&
! . "$_GO_SCRIPTS_DIR/lib/$__go_module_name" 2>/dev/null; then
@go.printf "ERROR: Unknown module: $__go_module_name" >&2
exit 1
fi
However, this doesn't differentiate between the module not existing, and the module having an error. I.e. if the module file exists, but has a bash syntax error, it will fail with the same "Unknown module" error that it fails with if the module file doesn't exist.
Ideally, we'd have two messages, one for issue with the module file not existing, another stating the file doesn't exist, however there was an error in loading it.

 v1.3.0


[Gitmoji Search] Add option to paste emoji name like :tada:

Extension – Gitmoji Search
Author: @ricoberger

Add option to paste name like :tada: instead of only pasting the emoji itself.
Describe the feature and the current behavior/state.
Current state: only option is to paste emoji character or copy emoji character to clipboard
Who will benefit with this feature?
Any who uses applications that don't support emoji natively. (Sourcetree is what I use.)
Any Other info.
Thank you so much for making this extension! It saves me time finding the gitmoji I need!

Hi @garymazzeo, in the preferences of the Gitmoji extension you can select if you want to paste/copy the gitmoji character or if you want to paste/copy the code of the gitmoji.
Does this already help or do you want another action where you can also paste/copy the code when the emoji option is selected in the preferences?

Ahhhh, thanks @ricoberger! Yes, that's super helpful, and I think for me, that's perfect. I had thought there could be the option for either with cmd+K (with preference to switch the default). But I think for "gitmoji" use, only one is fine. The places that accept the character would also accept the :code: (my experience is mostly with github and gitlab). Thanks for the speedy reply, and thanks again for the extension!


add initial implementation

Summary

add initial implementation for the brand new GitHub actions that will install the sigstore tools in the pipeline.
also adds: shellcheck/dependabot/check headers

Considerations:

Rigth now it install cosign and rekor-cli
It installs both, but maybe when we add more tools we can select which one we want to deploy, did all at this stage because the rekor install uses cosign to validate the signatures

TODO:

deprecate old cosign releases and support 1.0.0+ (do we want that?)

cc @dlorenc @bobcallaway
Ticket Link
n/a
Release Note
NONE

testing run from another repo: https://github.com/cpanato/testing-ci-providers/runs/5287946435?check_suite_focus=true

@datosh thanks for your review, PTAL
@dlorenc PTAL 😄

just curious, why aren’t we just calling the exiting cosign-install action instead of reimplementing it?

The lions share of of the execution time of an action is spent initializing the environment, so it makes sense to simply copy the the old cosign-specific action if this is intended to be a more generalized replacement

Can the cosign workflow be constructed as a reusable workflow to be used here?

makes total sense, i'm just dumb, will change that

gentle reminder @cpanato

@dekkagaijin @haydentherapper addressed the comments


Animation of the camera motion sometimes generates extra rotation

Animation of the camera motion sometimes generates extra rotation, in addition to the direct motion from the start to end view directions. This problem stems from the quaternion q and -q represents the same rotation matrix, and the interpolation from q1 to q2 and to -q2 generates different pathways of the change of the view directions (one is direct path and another is indirect path with extra rotation). The direct and indirect path can be detected by the sign of the dot products of two quaternions.

In default, slerp() (in qlib/MatrixHelper.cpp) takes care of the positivity of the inner product of q and r. Property keepquatpositive is added to CamMotion to enable the previous behavior.


JDK 11.0.8 Runtime#availableProcessors() returns cpu_request / 1024 in OpenShift

Platform:
Linux/CentOS7
Architecture:
x86
Please describe the issue that you are having with our binaries and if possible how to recreate it.
When I set no or a low cpu request on an OpenShift pod I always get 1 returned by Runtime#availableProcessors(). It seems that OpenJDK 11.0.8 calculates the available processors by doing max(1, cpu_request / 1024) although it IMO should use something like cpu_limit == null ? physical_cores : (cpu_limit / 1024).
I'm testing with the docker image jboss/base-jdk:11 and essentially doing the following to test it:
cat <<EOF >test.sh
#!/usr/lib/jvm/java-11/bin/java --source 11
public class App {
    public static void main(String ...args) {
        System.out.println(Runtime.getRuntime().availableProcessors());
    }
}
EOF
chmod +x test.sh
./test.sh

The JDK8 I used before had support for detecting the cgroups limits and properly detected the cpu_limit which in my case was 8192 i.e. 8 cores. Can I somehow force the old behavior?

@jerboaa Didn't you work in that area (cgroups) recently?

@beikov Yes. Intended behaviour. See this bug for the rationale:
https://bugs.openjdk.java.net/browse/JDK-8216366

By setting CPU requests in OpenShift you are basically setting a cgroups CPU limit, which OpenJDK respects.

cpu_limit == null ? physical_cores : (cpu_limit / 1024) => it does exactly that. setting CPU requests in OpenShift is mapped to a CPU limit in the container.

Use -Xlog:os+container=trace to trace what the JDK is doing. Not sure what your setup is and what you'd expect. It's not clear from the description.

So what is the CPU Limit in OpenShift mapped to then? I'd personally assume that the limit i.e. the upper bound is what should be use to determine the available processors. I tried to read through the mailing list discussion but I wasn't able to figure out exactly why mapping the cpu shares to available processors is a good idea.
When deploying a JVM to a normal host without cgroup limits/shares, you also get the number of physical cores as available processors returned, regardless of what priority the process has. So this decision seems counterintuitive to me.

Hey @karianna! Is there a chance I will get a decent answer as to why this is this way? It seems very counter intuitive to me that cpu-shares, which is AFAIU more or less a priority value for the linux scheduler, is used as a basis for available processors in the OpenJDK. IMO the value should be calculated by using cpu_limit == null ? physical_cores : (cpu_limit / 1024) just like @jerbaaa wrote.
I ruled out that this is just OpenShift related as I was able to reproduce it with plain docker by setting the cpu-shares. Increasing cpu-shares or cpu-request in OpenShift to get the desired available processors being reported is not helpful, as that has an effect on scheduling in OpenShift. A 8 core node can only hold up pods with a sum of cpu requests of 8196. If some of the processes don't fully use their share(which they rarely will), the node will always be underutilized.

Hi @beikov - you'll actually want to discuss this upstream at<EMAIL_ADDRESS>and reference https://bugs.openjdk.java.net/browse/JDK-8216366


Demo apps fails in initialization on some nodes

Description

Deploying solutions on some nodes for example the blow, Due to network lags the certificate generation fails with this exception in letsencrypt log.

A7FmQZ72h7FzjkJMGXmzLDFyfyxzitDZYuernGG97nv7
2m3nHPSAMyZFSeg5HPozic2NGBMtrXrBkhtNcVmd5Ss6
BDhpLyV28Y6Njy54WnB2Rkn6eHdEUbMu3GwTTs65rGAG
3dAnxcykEDgKVQdTRKmktggL2MZbm3CPSdS9Tdoy4HAF
2fi9ZZiBGW4G9pnrN656bMfW6x55RSoHDeMrd9pgSA8T

so it fails in container initialization with this error

Traceback/Logs/Alerts
2020-09-20 12:02:22,762:DEBUG:certbot.error_handler:Calling registered functions
2020-09-20 12:02:22,763:INFO:certbot.auth_handler:Cleaning up challenges
2020-09-20 12:02:23,905:DEBUG:certbot.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/bin/certbot", line 11, in <module>
    load_entry_point('certbot==0.31.0', 'console_scripts', 'certbot')()
  File "/usr/lib/python3/dist-packages/certbot/main.py", line 1365, in main
    return config.func(config, plugins)
  File "/usr/lib/python3/dist-packages/certbot/main.py", line 1119, in run
    certname, lineage)
  File "/usr/lib/python3/dist-packages/certbot/main.py", line 121, in _get_and_save_cert
    lineage = le_client.obtain_and_enroll_certificate(domains, certname)
  File "/usr/lib/python3/dist-packages/certbot/client.py", line 410, in obtain_and_enroll_certificate
    cert, chain, key, _ = self.obtain_certificate(domains)
  File "/usr/lib/python3/dist-packages/certbot/client.py", line 353, in obtain_certificate
    orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names)
  File "/usr/lib/python3/dist-packages/certbot/client.py", line 389, in _get_order_and_authorizations
    authzr = self.auth_handler.handle_authorizations(orderr, best_effort)
  File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 82, in handle_authorizations
    self._respond(aauthzrs, resp, best_effort)
  File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 168, in _respond
    self._poll_challenges(aauthzrs, chall_update, best_effort)
  File "/usr/lib/python3/dist-packages/certbot/auth_handler.py", line 239, in _poll_challenges
    raise errors.FailedChallenges(all_failed_achalls)
certbot.errors.FailedChallen

resolved in: https://github.com/threefoldtech/tf-images/pull/20
solution was to update the flist to retry to generate the certificate if it failed

verified


Chart slider option set start and end value can not become effective when chart has rendered.

G2 Version: 4.0.7

Platform: MacOS Chrome

Mini Showcase(like screenshots):

CodePen Link: https://g2.antv.vision/zh/examples/area/basic#area-large

Chart slider option set start and end value can not become effective when chart has rendered. The chart shows full range of graphs.
chart.option('slider', {
      start: 0.1,
      end: 0.8,
      trendCfg: {
        isArea: false,
      },
   });

fixed in 4.1.x

fixed in 4.1.x


Fix benchmark calculations

This fixes #13 - the minified difference is being divided by the unminified/unoptimized time when it should be the minified/unoptimized time.  This leads to incorrect results in the improvement column for all minified times.  (looks like a copy/paste error)
I didn't actually re-run the benchmarks, I simply recalculated values from the table - because of this there is some rounding error, but the overall results should be more accurate than they were.
If you choose to just fix the benchmark and regenerate things, that's fine too.

Thank you – this is why I do things out in the open: so that people can check my work and correct any errors. :smiley:
I'm not sure why the opt vs unopt improvements were slightly off as well, but I'll need to check my code and see if there was a rounding error or something. In any case, thank you very much for the fix – I checked manually and these improvement numbers are indeed correct. Cheers!


Alexa component error

Home Assistant release (hass --version):
0.26.0
Python release (python3 --version):
3.5.1
Component/platform:
Alexa
Description of problem:
Component fails to load
Traceback (if applicable):
ERROR:homeassistant.bootstrap:Error during setup of component alexa
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/site-packages/homeassistant/bootstrap.py", line 156, in _setup_component
    result = component.setup(hass, config)
  File "/usr/local/lib/python3.5/site-packages/homeassistant/components/alexa.py", line 30, in setup
    config[DOMAIN].get(CONF_INTENTS, {})))
  File "/usr/local/lib/python3.5/site-packages/homeassistant/components/alexa.py", line 48, in __init__
    hass, intent[CONF_ACTION], "Alexa intent {}".format(name))
  File "/usr/local/lib/python3.5/site-packages/homeassistant/helpers/script.py", line 42, in __init__
    self.sequence = cv.SCRIPT_SCHEMA(sequence)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/validators.py", line 264, in __call__
    raise e if self.msg is None else AllInvalid(self.msg)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/validators.py", line 262, in __call__
    v = schema(v)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 192, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 523, in validate_sequence
    cval = validate(index_path, value)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 625, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/validators.py", line 230, in __call__
    raise error if self.msg is None else AnyInvalid(self.msg)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/validators.py", line 224, in __call__
    return schema(v)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 192, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 625, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/validators.py", line 264, in __call__
    raise e if self.msg is None else AllInvalid(self.msg)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/validators.py", line 262, in __call__
    v = schema(v)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 192, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 625, in validate_callable
    return schema(data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 192, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 486, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.5/site-packages/voluptuous/schema_builder.py", line 324, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: template value should be a string for dictionary value @ data[0]['data_template']['target']

Additional info:
Haven't changed anything in the config yaml; only updated HASS and this issue started happening.

Alexa is working fine for me on 0.26. This may be related to a similar issue I had in #2771.

I tried removing anything in my Alexa config that used 'data_template' and the component loaded! Thanks for the tip!
How would you go about fixing this config to work again:
PersonZoneIntent:
      action:
        service: notify.notify
        data_template:
          message: The location of {{ Person }} has been queried via Alexa.
          target:
              -<PHONE_NUMBER>
      speech:
        type: ssml
        text: >
            {%- for state in states.device_tracker -%}
              {%- if state.name|replace("'s Phone", "")|lower == Person|replace("'s", "")|lower -%}
                {%- if state.state != "not_home" -%}
                    <speak>{{ state.name|replace("'s Phone", "") }} is at {{ state.state }}, as of {{ relative_time(state.last_updated) }} ago.</speak>
                {%- elif state.state == "not_home" -%}
                    {%- if state.name == "Example 1's Phone" -%}
                        <speak>{{ state.name|replace("'s Phone", "") }} is at <say-as interpret-as="address">{{ states("sensor.exa_address") }}</say-as>, as of {{ relative_time(states.sensor.exa_address.last_updated) }} ago.</speak>
                    {%- elif state.name == Example 2's Phone" -%}
                        <speak>{{ state.name|replace("'s Phone", "") }} is at <say-as interpret-as="address">{{ states("sensor.exb_address") }}</say-as>, as of {{ relative_time(states.sensor.exb_address.last_updated) }} ago.</speak>
                    {%- elif state.name == "Example 3's Phone" -%}
                        <speak>{{ state.name|replace("'s Phone", "") }} is at <say-as interpret-as="address">{{ states("sensor.exc_address") }}</say-as>, as of {{ relative_time(states.sensor.exc_address.last_updated) }} ago.</speak>
                    {%- endif %}
                {%- endif %}
              {%- endif -%}
            {% else %}
              <speak>I'm sorry, but I could not locate a resident named {{ Person.lower() }}.</speak>
            {%- endfor -%}

ActivateScriptIntent:
      action:
        service: script.turn_on
        data_template:
          entity_id: script.{{ Script | replace(" ", "_") }}
      speech:
        type: plaintext
        text: OK

Thanks again for the help

The problem is with your target under data_template. This was broken before, HA is now just telling you. Move it under a data: tag.

Thanks, that worked.