Improve behavior of jaws deploy when updating previously deployed lambdas.

In its current implementation, jaws deploy checks to see if the lambda function exists and, if it does not, it creates a new function, if it does, it deletes the existing function and creates a new function.
In the case where the function exists, this pattern decouples the previously deployed function from its associated API endpoints, rendering the API endpoint broken. I have not yet found a way to re-couple the function and the endpoint resource method without deleting the method and starting over.
By replacing the deleteFunction/createFunction pattern with one that uses aws-sdk's updateFunctionCode/updateFunctionConfiguration, the code and configuration are updated without deleting the deployed references and the API endpoint remains intact.
Additionally, this PR includes a small fix to .gitignore which brings it into conformance with the prescribed API directory structure, e.g. /api/users/list which places the node_modules directory one level deeper than the existing .gitignore supports.

I've encountered the problem with the API, and found a work-around without deleting the method and starting again. Go into the method > Integration Request > click to edit the Lamdba Function name > click the tick, the 'Add Permission to Lambda Function' dialog appears > Click Ok. Test & redeploy the API - it should be working again.
Still tedious, but much less tedious than rebuilding the entire API.

Confirmed that this preserves existing api endpoints. Great work, that was starting to drive me nuts.

@furf Awesome work here.  We're looking at changing the whole deploy process entirely in JAWS v1.  If you have a few minutes, would you take a look at the JAWS v1 spec.  If you have comments, please make them:  JAWS v1    Most of what's currently in here is based off of PR #42

I'm still relatively new to Lambda and some of the other AWS tools I've learned overnight since getting jazzed about JAWS, but I can respond to things JavaScript, project structure and such. I'll dive into your specs over lunch.
Coincidentally, I was JUST putting the wraps on my first pass at what you call the new command! It's a bit naive, but I just felt like doing work to save work. I'll push it up to my fork later for giggles.

PS–also Oakland.

Awesome.  I go to Oakland JS sometimes.  Not today though... swamped :(

@furf FWIW the proposed function in here was added in PR #42 from a few days ago

@doapp-ryanp GMTA

@arieljake I think we are going to get rid of it all together in the new v1.0.0 proposal.  Check it out and provide feedback if you have time.

Can we close this PR?

@furf, this is clutch.
All, shouldn't this be merged so that others aren't unknowingly destroying their API Gateway as they're happily uploading all of their lambda functions with this awesome new project they found?   I understand it's fixed in v1.0, but until that's released....

closing with v1 release.


Error after the Plan Command

I get the following error after the plan command:
Error: Insufficient features blocks
│
│   on  line 0:
│   (source code not available)
│
│ At least 1 "features" blocks are required.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 14080c3b-027f-93e1-fd0f-4bea971f51b0
Version Independent ID: 5894d6ec-4347-153c-fa9a-203d41275153
Content: Install the Azure Terraform Visual Studio Code extension
Content Source: articles/terraform/configure-vs-code-extension-for-terraform.md
Service: terraform
GitHub Login: @TomArcherMsft
Microsoft Alias: tarcher

@arob98 Thanks for the feedback! Apologies for this issue taking so long to resolve. We're in the process of implementing a new testing pipeline, so issues like this will be caught much quicker going forward. I've updated the article and it should go live by tomorrow afternoon (PST).


Update repo config

Docs Build status updates of commit c42a8eb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dotnet/xml/CommunityToolkit.Authentication.Extensions/HttpRequestMessageExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication.Extensions/MsalProviderExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/AccountsSettingsPaneConfig.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/BaseProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/IProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/MockProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/MsalProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/ProviderManager.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/ProviderState.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/ProviderStateChangedEventArgs.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WebAccountCommandParameter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WebAccountProviderConfig.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WebAccountProviderType.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WindowsProvider.xml
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.Common.Collections/IIncrementalSource1.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.Common.Collections/IIncrementalSource1.xml)
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Common.Collections/IReadOnlyObservableGroup.xml
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.Common.Collections/ObservableGroup2.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.Common.Collections/ObservableGroup2.xml)
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.Common.Collections/ObservableGroupedCollection2.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.Common.Collections/ObservableGroupedCollection2.xml)
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Common.Collections/ObservableGroupedCollectionExtensions.xml
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.Common.Collections/ReadOnlyObservableGroup2.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.Common.Collections/ReadOnlyObservableGroup2.xml)
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.Common.Collections/ReadOnlyObservableGroupedCollection2.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.Common.Collections/ReadOnlyObservableGroupedCollection2.xml)
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Common.Deferred/DeferredCancelEventArgs.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Common.Deferred/DeferredEventArgs.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Common.Deferred/EventDeferral.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Common.Deferred/EventHandlerExtensions.xml
:warning:Warning
View
Details

This comment lists only the first 25 files in the pull request.

dotnet/xml/CommunityToolkit.Authentication.Extensions/HttpRequestMessageExtensions.xml

Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

dotnet/xml/CommunityToolkit.Authentication.Extensions/MsalProviderExtensions.xml

Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Identity.Client.Extensions.Msal.StorageCreationProperties'.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

dotnet/xml/CommunityToolkit.Authentication/AccountsSettingsPaneConfig.xml

Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SettingsCommand'.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SettingsCommand'.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

dotnet/xml/CommunityToolkit.Authentication/BaseProvider.xml

Line 0, Column 0: [Warning: ms-author-missing - See documentation] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 0, Column 0: [Warning: ms-prod-or-service-missing - See documentation] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a195c03:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dotnet/docfx.json
:warning:Warning

Details

dotnet/xml/CommunityToolkit.Authentication.Extensions/MsalProviderExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/AccountsSettingsPaneConfig.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WebAccountCommandParameter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WindowsProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Extensions/GraphExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Extensions/ProviderExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Helpers.RoamingSettings/UserExtensionStorageHelper.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.CommunityToolkit_Graph_Uwp_XamlTypeInfo/XamlMetaDataProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/GraphPresenter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/LoginButton.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/PeoplePicker.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/PersonView.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/QueryOption.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Converters/ObjectToStringConverter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Converters/UserToPersonConverter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp/ElementExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp/ProviderStateTrigger.xml
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.HighPerformance.Helpers/IInAction1.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.HighPerformance.Helpers/IInAction1.xml)
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/BluetoothLEHelper.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/ConnectionInformation.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/GattConvert.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/GattProtocolErrorParser.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/ObservableBluetoothLEDevice.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/ObservableGattCharacteristics.xml
:warning:Warning
View
Details

This comment lists only the first 25 files in the pull request.

dotnet/docfx.json

Line 50, Column 40: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'windows-toolkit' is not valid with 'ms.prod' value 'community-toolkit'.

dotnet/xml/CommunityToolkit.Authentication.Extensions/MsalProviderExtensions.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Identity.Client.Extensions.Msal.StorageCreationProperties'.

dotnet/xml/CommunityToolkit.Authentication/AccountsSettingsPaneConfig.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SettingsCommand'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SettingsCommand'.

dotnet/xml/CommunityToolkit.Authentication/WebAccountCommandParameter.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SupportedWebAccountActions'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.WebAccountCommandInvokedHandler'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.WebAccountCommandInvokedHandler'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SupportedWebAccountActions'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.WebAccountCommand'.

dotnet/xml/CommunityToolkit.Authentication/WindowsProvider.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.System.DispatcherQueue'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.System.DispatcherQueue'.

dotnet/xml/CommunityToolkit.Graph.Extensions/GraphExtensions.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.User'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.User'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.Extension'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a195c03:
:warning: Validation status: warnings

File
Status
Preview URL
Details

dotnet/docfx.json
:warning:Warning

Details

dotnet/xml/CommunityToolkit.Authentication.Extensions/MsalProviderExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/AccountsSettingsPaneConfig.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WebAccountCommandParameter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Authentication/WindowsProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Extensions/GraphExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Extensions/ProviderExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Helpers.RoamingSettings/UserExtensionStorageHelper.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.CommunityToolkit_Graph_Uwp_XamlTypeInfo/XamlMetaDataProvider.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/GraphPresenter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/LoginButton.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/PeoplePicker.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/PersonView.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Controls/QueryOption.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Converters/ObjectToStringConverter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp.Converters/UserToPersonConverter.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp/ElementExtensions.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.Graph.Uwp/ProviderStateTrigger.xml
:warning:Warning
View
Details

[dotnet/xml/CommunityToolkit.HighPerformance.Helpers/IInAction1.xml](https://github.com/huangmin-ms/community-toolkit-api-ref-dotnet/blob/smoke-test/dotnet/xml/CommunityToolkit.HighPerformance.Helpers/IInAction1.xml)
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/BluetoothLEHelper.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/ConnectionInformation.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/GattConvert.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/GattProtocolErrorParser.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/ObservableBluetoothLEDevice.xml
:warning:Warning
View
Details

dotnet/xml/CommunityToolkit.WinUI.Connectivity/ObservableGattCharacteristics.xml
:warning:Warning
View
Details

This comment lists only the first 25 files in the pull request.

dotnet/docfx.json

Line 50, Column 40: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'windows-toolkit' is not valid with 'ms.prod' value 'community-toolkit'.

dotnet/xml/CommunityToolkit.Authentication.Extensions/MsalProviderExtensions.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Identity.Client.Extensions.Msal.StorageCreationProperties'.

dotnet/xml/CommunityToolkit.Authentication/AccountsSettingsPaneConfig.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SettingsCommand'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SettingsCommand'.

dotnet/xml/CommunityToolkit.Authentication/WebAccountCommandParameter.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.WebAccountCommand'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.WebAccountCommandInvokedHandler'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.WebAccountCommandInvokedHandler'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SupportedWebAccountActions'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.UI.ApplicationSettings.SupportedWebAccountActions'.

dotnet/xml/CommunityToolkit.Authentication/WindowsProvider.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.System.DispatcherQueue'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Windows.System.DispatcherQueue'.

dotnet/xml/CommunityToolkit.Graph.Extensions/GraphExtensions.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.Extension'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.User'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.Graph.GraphServiceClient'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Better represent state of initial CIS scans

Install CIS Benchmark on a fresh cluster
Create a scan
The initial scan can time a long time to start (not seen in subsequent scans)
The scans table isn't too bad, but going into the new scan detail page results in a Detail page with no content. Feels like we need the generic loading feature here or an on screen message better representing the state of the scan

I hit issues with this again when i guess a scan failed.. or wasn't kicked off as required (there was no owned resources of the created cis.cattle.io.clusterscan ... so nothing shown on screen. There's no way to debug this and user is left hanging

@richard-cox I hit this too. I'd expect the resource for the scan to get created straight away


Error 404 when contancting nintendo

System Health details
System Information

version
core-2024.4.3

installation_type
Home Assistant Supervised

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.2

os_name
Linux

os_version
5.15.0-101-generic

arch
x86_64

timezone
America/New_York

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4871

Installed Version
1.34.0

Stage
running

Available Repositories
1402

Downloaded Repositories
54

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Ubuntu 22.04.4 LTS

update_channel
stable

supervisor_version
supervisor-2024.04.0

agent_version
1.4.1

docker_version
26.0.1

disk_total
62.8 GB

disk_used
50.8 GB

healthy
true

supported
failed to load: Unsupported

supervisor_api
ok

version_api
ok

installed_addons
AirCast (4.2.1), Node-RED (17.0.12), Advanced SSH & Web Terminal (17.2.0), Grocy (0.21.0), Matrix (0.10.0), Studio Code Server (5.15.0), Samba share (12.3.1), MariaDB (2.7.1), phpMyAdmin (0.9.1), Network UPS Tools (0.13.0), Mosquitto broker (6.4.0), TasmoAdmin (0.30.0), Frigate (0.13.2), WeatherFlow to MQTT (3.2.2), Zigbee2MQTT (1.36.1-1), Piper (1.5.0), Whisper (2.0.0)

Dashboards

dashboards
7

resources
29

views
30

mode
storage

Recorder

oldest_recorder_run
March 24, 2024 at 3:31 AM

current_recorder_run
April 19, 2024 at 7:37 AM

estimated_db_size
1452.59 MiB

database_engine
mysql

database_version
10.11.6

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Nintendo Parental Controls mobile app

[X] I have checked the configuration of the mobile app and the switch device is registered.
[ ] I experience this issue if I test again with the tested configuration in the readme.
[ ] This issue does not happen when tested with the tested configuration in the readme.

Describe the issue
Integration fails with 404
Reproduction steps

...
Debug logs
This error originated from a custom integration.

Logger: custom_components.nintendo_parental
Source: helpers/update_coordinator.py:347
integration: Nintendo Switch Parental Controls (documentation, issues)
First occurred: 7:38:14 AM (1 occurrences)
Last logged: 7:38:14 AM

Error fetching nintendo_parental data: ('HTTP Exception', 'HTTP Error', 404)

Diagnostics dump
No response

Hi,
Thanks for reporting. Please can you enable debug logs and attach a log file?
Thanks

2024-04-25 14:28:19.172 DEBUG (MainThread) [pynintendoparental.authenticator] >> Init authenticator.
2024-04-25 14:28:19.173 DEBUG (MainThread) [pynintendoparental.authenticator] Refreshing access token.
2024-04-25 14:28:20.030 DEBUG (MainThread) [pynintendoparental] Received request to update data.
2024-04-25 14:28:20.031 DEBUG (MainThread) [pynintendoparental] Sending request to get_account_devices
2024-04-25 14:28:20.031 DEBUG (MainThread) [pynintendoparental] Built URL https://api-lp1.pctl.srv.nintendo.net/moon/v1/users/9188b4c753d0b924/devices?filter.device.activated.$eq=true
2024-04-25 14:28:20.178 DEBUG (MainThread) [pynintendoparental] Request to https://api-lp1.pctl.srv.nintendo.net/moon/v1/users/9188b4c753d0b924/devices?filter.device.activated.$eq=true status code 404
2024-04-25 14:28:20.179 ERROR (MainThread) [custom_components.nintendo_parental] Error fetching nintendo_parental data: ('HTTP Exception', 'HTTP Error', 404)
2024-04-25 14:28:20.179 DEBUG (MainThread) [custom_components.nintendo_parental] Finished fetching nintendo_parental data in 0.149 seconds (success: False)

Thanks, what happens when you sign into the Nintendo Parental Control app?

Hi,
This happens if the account you have used is not the one used to sign into the Nintendo Parental Control app.
Closing as integration is working as expected.


[feature request] Implement floating origin on geolocation ar

What is the current behavior?
Currently, the world position of entities(and the camera) when using ARJS' aframe geolocation AR can have values on the millionth scale. From my tests, it can vary between(more or less) -20million to 20million. The problem with this is for other frameworks that wants to use ARJS solely to retrieve the position information for placement and have floating point precision problems. Take a look at this issue. It's exactly what I'm facing. I successfully managed to use ARJS' geolocation (aframe version) to position objects in another framework such as PlayCanvas, but I am running into this problem.
Ideally, I'd like a feature where the camera's world position stays at (0, 0, 0), and there's a threshold property that when met, centers the camera to 0, 0, 0 again and repositions the entities around it. See this short video (from this plugin, consider that the avatar shown is the camera and everything around are the aframe entities. What moves are the entities around the camera, not the camera itself) which showcases exactly what I'm looking for. Example camera's position is (20000000, 0, 0) and entity is (20000001, 0, 0), camera becomes (0, 0, 0) and entity (1, 0, 0). The distance stays the same but now the values are small and avoid the floating point precision problem.
I am currently implementing this floating point origin to fix the issue I'm having, but I think it would be nice if this feature was available out of the box for ARJS' geolocation AR so that it can be easily used by other game frameworks that have problems with floating point precisions (which seems to be literally every other game framework except aframe lol).
Other useful resources
<EMAIL_ADDRESS>https://www.youtube.com/watch?v=qIxifMcvYTs
https://manuel-rauber.com/2022/04/06/floating-origin-in-unity/
https://www.reddit.com/r/Unity3D/comments/ijwfec/the_further_you_are_from_000_the_messier_stuff/
https://www.alanzucconi.com/2020/08/03/floating-point-arithmetic/
@nickw1 what do you think?

@marcusx2 I see what you mean. As it happens the older location-based components (not new-location-based) to set the world origin to be the original GPS position, but this was removed for simplicity.
However, in the light of what you have said, I can add it back to new-location-based, so that the world origin is the initial position and the objects have coordinates relative to the initial GPS position.
I am slightly concerned about updating the world coordinates of the objects, though, as this may impact performance particularly if you have large numbers of objects. Perhaps that can be added in as an optional feature?
So, for the next release I will restore the original behaviour, i.e. world origin is original GPS position.

Hello @nickw1 , thank you for your reply.

So, for the next release I will optionally restore the original behaviour, i.e. world origin is the initial GPS position. To avoid breaking existing code, however, it will not be the default, it will require a flag to be passed in.

This would certainly help a lot and fix most cases. It would only break if the user started using ARJS too distant from the entities anyways. On this case the world position of the camera would end up on gigantic values as the user finally arrives at the locations and the problem would happen again.

I am slightly concerned about updating the world coordinates of the objects, though, as this may impact performance particularly if you have large numbers of objects. Perhaps that can be added in as an optional feature?

As an optional feature it would be great, I don't mind. Like I said, having an optional threshold to reset the camera to world origin and the other entities to correct relative world position would be great! (e.g. threshold is 5000, which means world position is 5000 on either axis). Of course if an entity relative to the camera is on a distance bigger than the threshold, it wouldn't even show up!

Maps service has this feature too.

So, for the next release I will optionally restore the original behaviour, i.e. world origin is the initial GPS position. To avoid breaking existing code, however, it will not be the default, it will require a flag to be passed in.

@nickw1 is this change hard to do, can you guide me through it? If you can send me the modified version with just this change I'd greatly appreciate it. If it's not something trivial then never mind, I can wait until next release. Thanks!

@marcusx2 it's actually quite easy but I haven't had the time this week. I will do it as soon as I can.

Hopefully a movefloatingorigin method can also make it to a next release together with world-origin-as-original-GPS-position. In this case the camera could also have a distance property which is the distance from the world origin. The method doesn't have to be called automatically and you could let the user make the decision of calling it or not. So for example, every time the gps position event fires, I check the distance of the camera from the origin, and if I regard it as far enough I call the movefloatingorigin method.

OK what I think I'll do is implement #498, #499 and #502 for the next release (bugfix release 3.4.4), keeping this as an optional for the moment (but will probably make it the default in 3.5). Your other issues are a little more complex, and perhaps less critical, so will leave these to a later release.

OK what I think I'll do is implement #498, #499 and #502 for the next release (bugfix release 3.4.4), keeping this as an optional for the moment (but will probably make it the default in 3.5). Your other issues are a little more complex, and perhaps less critical, so will leave these to a later release.

I think you mean you will implement initial gps position at world origin for the next release, but not the floating origin(movefloatingorigin method) which is this issue. It's because implementing initial gps position at world origin is the first step.
Ok I understand. Thank you very much, looking forward to the next bugfix release!

Sorry, no I also meant the floating origin as well. I will however leave #501 for now. (Actually #500 should be easy to fix too, so add that in as well).

#508 allows the initial GPS position to be used as the world origin.
The floating origin however will require a rewrite of part of the code so I'm proposing postponing it for the 3.5 release, and at that point, introducing a breaking change of making the initial GPS position the world origin by default.

bump

bump


Add Tidelift to acknowledgements for financial support

I'll merge this tomorrow unless there are comments.

thanks Matt


[WIP] Improve test coverage to 100%

I've started with the process of getting the test coverage up to 100%. I think after the coverage is up, a refactor of a large portion of the tests is needed. They seem to be all over the place in terms of writing style and structure and some of them don't do anything.
An example of a test that is useless can be found in utils/index.js, where the following exists:
// test polyfill.
let arr = Array.from(nodeList);
arr.find = undefined;
expect(find(arr, el => el.name === 'i1')).toBe(el);

This is supposed to test the polyfill of utils.find, which is essentially array.find. However, in utils.find the input array parameter is handled like this:
const array = toArray(arrayLike);

This negates the effect of arr.find = undefined;, since it re-adds the method to the array. This is just supposed to be an example. Ideally all functions of a file should have their own describe block and there should be sensible setup functions.
This PR is supposed to address coverage though, so the test refactor may or may not be a project for the future that is worth considering.

[x] errorBag.js
[x] generator.js
[x] date_between.js
[ ] mixin.js
[ ] field.js
[ ] validator.js
[ ] utils/index.js

Tests are a mess right now in terms of readability, most tests uses hacky mocks which while does the job it makes reading them a hard task. The test framework was changed a couple of times in the past so that may explain why some of jest features like mocks are not utilized properly. Also my own inexperience with testing is a factor.
Ideally I would like to use vue-test-utils more where relevant, and refactor mocking in general.
Thanks for the PR, I appreciate your efforts.

I have just decided to scrap this PR and to instead start, one by one, refactoring unit tests. I'll start this evening and I'll make a PR once I made some progress. I don't think there is much point in improving code coverage if the tests don't do much.


RE: BBAI Fritzing Part Number and If It Works...

Hello,
I am receiving an error on Fritzing b/c of the part number from the BBAI. Does this fritzing part number mean I am not allowed to make it work on Fritzing?
Or...
Does it mean, the part is not available?
Seth
P.S. This is the part number stating it is already loaded but I have not loaded it yet, 'prefix0000_54b7cd94fdd33f8e98c7b4d8_2'. I am no pro when it comes to fritzing parts but I will keep trying to change this part number to fix the issue.

Hello,
I will go to fritzing's forums to post. Sorry for taking up your time.
Seth


Add the required base64 encryption step

This is a required step that just worked for me, I saw it in a youtube video but there is no reference into the Thanos official documents.
Please Check.

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Verification

There's also stringData which does the base64 encoding on the fly and you don't need to do it manually:
https://kubernetes.io/docs/concepts/configuration/secret/#restriction-names-data


yubioath-desktop: use qt wrapped mkDerivation

Motivation for this change
yubioath-desktop is currently broken due to recent changes with the QT setup in nix and not using the QT wrapper as per the guidelines.
Things done
Using the mkDerivation wrapper for QT apps.

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @Mic92

cc #65399

ty


FIX: increase_time_limit_to work when increase_time_limit_max is not yet set

Ran into this problem when running a task through a CMS action. Not sure if this is a necessarily a good fix, but if we need to throw a user error or something instead let me know :smile:
Perhaps we can just set the global $_increase_time_limit_max to -1 before this function runs?

I'm confused, $_increase_time_limit_max = -1; is the default.
if your $_increase_time_limit_max is falsey, then it's been set that way...

No, its not set at this point in the execution, its set afterwards. If you check the tests, they explicitly set it to -1 before running.
To replicate, you can add the following to the mysite/_config.php
increase_time_limit_to(300);

Then check in Core.php with the following:
	error_log(__FUNCTION__);
	if($max != -1 && $timeLimit > $max) return false;
	error_log(__FUNCTION__ . ' passed call');

The second log is never called.

OK, I'll try to find some time to take a look - is it possible to unit test this?!

@dhensby have you had a chance to look at this?
I'm not sure how to unit test this, if you have a suggestion I can run with I can give it a shot.

A simpler test is putting this into mysite/_config.php
if(!increase_time_limit_to(300)) die("Can't increase to 300");

I can't think of a good unit test for this because what we're testing is global state, which is usually clobbered by unit testing.
Regarding the bug, the issue is that the default value is set too far down Core.php, after the _config.php files are included. It also wasn't global. This fixes that: https://gist.github.com/40b4e2503b130ae4e9c2
Frankly, I think both fixes would be worth doing, as a falsy value of max can only be interpreted as "no max".
Stevie, would you mind pulling that gist into your PR?

I would also note that the code to set max memory limit is similarly broken. However, that code checks for falsy, and the default maximum memory limit that someone tried to put in is stupid and therefore rightly broken—it sets the maximum limit to the current limit.

As an aside, if we wanted to test this kind of setting, I would think that a 'full server stack test' approach would make the most sense, where we have a testing framework for:

Instantiating new projects with composer
Copying new files / patches into the project
Making assertions

So we'd be able to have a test that says:

Create a clean project
Put this line into mysite/_config.php if(!increase_time_limit_to(300)) user_error("Can't increase time");
Visit http://<site>/dev/
Confirm 200 response and no "Can't increase time" in resulting text

There will be other surface thing that we can test in this way I'd expect, for example testing our .htaccess and nginx config instructions. We would probably want to allow the testing system to make modifications to nginx configuration files and things, so running as root/sudo in some vm/container would be helpful.

Cool, I've made that change for you @sminnee
I'm not going to open the testing can of worms with this PR, but if I get time (hah!) will definitely have a look at an environment based testing suite as it does make sense like you've said :smile:

@stevie-mayhew can you confirm you tested locally and this acts as expected?

@dhensby Yeah have tested it locally and it worked :smile:

thanks

Thanks!


LG Styler doesn't work on v1.8.3

Describe The Bug:

On setting up device with plugin v1.3.0 and ThinQ1 enable, it was successfully added accessory "STYLER S3BF_WIFI"
but same as on v1.8.3 (latest), it wasn't added with this message :
Device not supported:xxxxxxx-xxxx-xxx-xxxx: styler (STYLER S3BF_WIFI)

In Apple Home with plugin v1.3.0, the styler icon shows like a water faucet and there is no function to control the device. How to right to set the device?

Is STYLER S3BF_WIFI no longer supported device?

To Reproduce:
Expected behavior:
on plugin 1.8.3 or later, the STYLER S3BF_WIFI can add accessory and fully function in Apple Home
Logs:
Show the Homebridge logs here (make sure homebridge DEBUG mode is turned `on`), remove any sensitive information.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

Screenshots:
Environment:

Plugin Version: 1.8.3
Homebridge Version:  1.7.0
Node.js Version:
NPM Version:
Operating System: macOS

need more debug log, please turn on homebridge debug mode and collect some

Here some debug logs after restart home bridge
[4/5/2024, 5:27:29 AM] Got SIGTERM, shutting down child bridge process...
[4/5/2024, 5:27:34 AM] [homebridge-lg-thinq] Child bridge process ended
[4/5/2024, 5:27:34 AM] [homebridge-lg-thinq] Process Ended.


add msg feature to firewall addressbook* to increase user msg output

wontfix: for now will not add to vycontrol


CMakePresets.json macros are not expanded properly in inheritance

Brief Issue Summary
I'm using CMakeUserPresets.json for local CMake development, and I have several presets which inherit from a common base preset. The base preset defines binaryDir to be ${sourceParentDir}/build/${presetName}. This macro is supposed to be dependent upon the name of the preset that actually gets used (https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#macro-expansion), but always defaults to build/base. Here is an abridged version of my CMakeUserPresets.json:
{
  "version": 2,
  "configurePresets": [
    {
      "name": "base",
      "hidden": true,
      "binaryDir": "${sourceParentDir}/build/${presetName}"
    },
    {
      "name": "build-base",
      "inherits": "base",
      "hidden": true,
      "generator": "Ninja",
      "cacheVariables": {
        "CMAKE_BUILD_TYPE": "Debug",
        "CMAKE_C_COMPILER_LAUNCHER": "ccache",
        "CMAKE_CXX_COMPILER_LAUNCHER": "ccache",
        "BUILD_QtDialog": "ON",
        "CMake_TEST_GUI": "ON",
        "CMake_TEST_JSON_SCHEMA": "ON"
      }
    },
    {
      "name": "ninja",
      "inherits": "build-base",
      "displayName": "Ninja",
      "cacheVariables": {
        "CMAKE_CXX_STANDARD": "11",
        "SPHINX_HTML": "ON"
      }
    }
  ]
}

Expected:

Paste above into CMakeUserPresets.json
Build with ninja preset
Build happens in build/ninja

Apparent Behavior:

Paste above into CMakeUserPresets.json
Build with ninja preset
Build happens in build/base

Cc: @esweet431

Hey @KyleFromKitware, thanks for reporting this issue.  I believe it's a duplicate of #1787 which we have a PR out for right now.  If all goes well, we'll release 1.7.1 with the fix today.

The PR was merged in the GitHub repository and, if you'd like, you can validate the fix for this problem by installing this custom vsix before we release the official 1.7.1.
https://github.com/microsoft/vscode-cmake-tools/actions/runs/774916180


Printing problem in Firefox

Hi,
I have a question as below when I use this plug-in on my own Aarch64 machine. I appreciate it if it gets printing...

Environments
CPU: Aarch64
OS:  ubuntu 14.10
Flash: Chromebook 32bits PPAPI Flash
Brower: FireFox 32bits, version43

2: issue
With this fresh pepper plug-in, the Chrome PPAPI flash works well in Firefox, it plays videos or forms/lists well,however, it prints nothing if we try to click the right button of mouse, even if it does NOT show any printing menu or pop any setting windows. Any idea about it?
Thank you!

Printing is not implemented at the moment. There are just stub functions that do nothing.

Thanks for the prompt reply... So do we have any plan for the printing implementation, when or in which version? Is there any open souce code that we can refer to at the moment to implement it, how complicated it is we can estimate?
Sorry for so many questions...
Best Regards,

have any plan for the printing implementation

Yes, I do have plans to implement printing support as well. But there is no strict schedule, so I can't say when. Lately, I just bump version after a number of months, so can't say which version will printing be implemented in.

Is there any open souce code that we can refer to at the moment to implement it, how complicated it is we can estimate?

It depends. I haven't started to look at it yet. But obvious pointers are Firefox and Chromium source code.


Dynamic import is broken when using nuxt-i18n

Version
v5.3.0
Reproduction link
https://codesandbox.io/embed/l4921qqll7
Steps to reproduce
Run yarn run dev in the repro link.
What is expected ?
It should work.
What is actually happening?
ERROR  Unexpected token (6:16)
Additional comments?
The dynamic import of Logo.vue in index.vue breaks nuxt-i18n. Dynamic import is supported (and even used on their website) by nuxtjs to enable webpack to split the code.

This bug report is available on Nuxt community (#c239)

Dup of #134

Should be fixed in v5.12.4


Overlapping data spans in stacked column charts

Thanks for the framework!
Any advice on how to deal with overlapping data spans? e.g.

It would be great to have them vertically stacked on top of each other to ensure readability.
I didnt find any option for this in the docs.
Thanks for any hints!

@msmart I need the HTML+CSS to help you.
See more info about stacked charts at https://chartscss.org/components/stacked/

The overlap happens in cases there is one dominating data point. See example below. This is not a bug. It's expected behavior. But I was just wondering what the common workaround for this situation would be to ensure readability of the data information.

                21-02-08
                    496
                    10
                    3
                    2

I would do this differently, replace your .data element with a .tooltip.
But because you are using .stacked chart it won't work.

thanks for your support! This worked for our use case!


URL vscode://file/path/to/project/ is only able to open folders from the C: drive on Windows

VSCode Version: 1.9.1
OS Version: Windows 10 Enterprise 14393.693

Steps to Reproduce:

Install VS Code
Create a folder D:/Temp
Run the following URL:  vscode://file/d/temp/

Expected result:
VS Code launches and opens folder D:/Temp
Actual result:
VS Code launches and says that folder /d/temp does not exist

I guess this is related to the windows CLI?

Want to attempt a PR?

Thanks for the fix @jordanmkasla2009!
But actually went ahead with a simpler solution on top of yours. Instead of manipulating the strings we should just explicitly require the colon C: to be in the URI. So here's how URIs would work for Code:
vscode://file/c:/temp/

vscode://file/d:/temp/


[rollup-plugin-svelte] The following packages did not export their package.json

I get this error on my svelte project.
[rollup-plugin-svelte] The following packages did not export their `package.json` file so we could not check the "svelte" field. If you had difficulties importing svelte components from a package, then please contact the author and ask them to export the package.json file.

- tslib

If I understand correctly, the following has to be added in the package.json:
https://github.com/niieani/hashids.js/commit/425877d842b18918121788b3810dbec15241c8ac
I tried fixing this on my side without success, this issue causes my livereload to fail.
Thanks in advance.

Already see it has been added in https://github.com/microsoft/tslib/pull/163


FFC cofs branch (parallel compilation bug)

The cofs FFC branch is currently identical to fd_bendy which is somewhat outdated. For example it predates this fix for parallel compilation:
https://bitbucket.org/mapdes/ffc/pull-requests/79/sort-entry-ir-to-ensure-deterministic/diff
We could cherry-pick the fix or rebase cofs branch on a newer version of master. I'd go for the latter but to me it's unclear what is the latest bendy compatible commit in FFC.

I tried moving the branch forward, but got lost in a sequence of problems.  So I've cherry-picked that one commit and updated the branch.

I've made the short-term minimal fix.  Hopefully ffc will go away in the slightly longer term.


Time to first byte

It would be nice to be able to get to the first byte somehow without having to load all needed data. I know it would be alot to ask, but if it was possible to split up the returned data somehow, to make the page render fast, and then populate the rest afterwards.
I am not a 100% sure how it could be done, but perhaps using something like
Inertia::render('Page')->withDelayedData($data);

It would then load the page without data, and then perform an ajax request to the same route to get the actual data.
This would in turn add the nprocess loader to the page at once, ensuring a better user experience.

It sounds good in theory. But this would surely rely on the consumer of Inertia having to manually add the JSON response into the controller, which I think is a bit out of scope.

In my opinion, this approach would only bring any benefits if you lazy-load the data somehow. If you are calculating (accessing DB, etc) to populate the $data variable you would end doing those calculations twice, as you would have two requests.
Why not having two separated routes? One for rendering the page and the other only to retrieve the data?
something like this
// /page
return Inertia::render('Page');

// /api/page
return $data;

As you would make an ajax request from the page component anyway, the api route can be separated.
Just a suggestion, sorry if I misunderstood your idea.

I second this. I installed both https://github.com/reinink/client-side-rendering-in-laravel and https://github.com/inertiajs/pingcrm
and it turns out pingcrm (built on infinityjs) is a lot slower to load each page.
Maybe it's because the pingcrm codebase needs to load more data, i'm not sure. Is it possible to make infinityjs / pingcrm as snappy as the client-side-rendering-in-laravel codebase?

Thanks for the interest in Inertia folks!
I think if you want that kind of behaviour, then you're probably better off with a classic SPA that uses an API.
Inertia.js is designed to mimic a classic server-side app, where when a request comes in, you load the necessary data from the database (or elsewhere) and then pass it to the view, and then the view is rendered immediately.
There is a wonderful simplicity to this approach, and Inertia is targeting people who value that. In my applications I strive to have each page load happen within 100-300ms, which completely removes the need to show loading indicators to the user.
Hope that makes sense!

@reinink
Perhaps it could be useful to have some kind of preloader built in, as I can imagine that a majority vast of users could experience issue with the speed.

Yeah, I don't agree that the vast majority of users could experience issues with speed.
You can build insanely fast apps with Inertia, you just need to make sure your controller responses are fast. (Which is the same thing you need to do when creating an API.)
Inertia works with code splitting, so you can already send the minimal JS bundle size possible. Yes, prefetching is cool, and maybe something we'll consider in the future, but I refuse to believe it's a requirement to create fast applications.
People have been building wicked fast server-side rendered applications for years. Inertia is basically the exact same approach, except EVEN FASTER, since you don't need to do full page reloads.

You are entirely right and it is hard to disagree, however, since this is entirely client-side rendered application you don't have built-in browser loading indicator, where you can't tell if website is currently loading new page or not.
In my opinion, it would be a good practice and definitely valuable from UX perspective to have any kind of loading indicator built in, no matter how fast website is (plus there are always can be some more time-consuming parts in the app)

There is a loading indicator :D Inertia ships with nprogress under the hood, but you need to add it's CSS to your application yourself.

Yeah, lol, we need to update the docs to tell folks to include the nprogress css. 🤦♂
Even better, I want to remove nprogress entirely, and just build it into Inertia directly. See here: https://github.com/inertiajs/inertia/issues/10


Getting Groups claims via OIDC

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[X] This issue affects my Ory Network project.
[X] I have joined the Ory Community Slack.
[ ] I am signed up to the Ory Security Patch Newsletter.

Describe your problem
I’m trying the Ory cloud to make more progress with the auth flow, I’m using OIDC with Ory but I’m struggling to get the user’s groups memberships with the userinfo results.
Now I’m getting this despite adding (group or groups to the requested scopes)
{
    "amr": [
        "password"
    ],
    "aud": [
        "xxxxxx-4dc9-8094-7d4926d3350e"
    ],
    "auth_time":<PHONE_NUMBER>,
    "email"<EMAIL_ADDRESS>    "email_verified": true,
    "iat":<PHONE_NUMBER>,
    "iss": "https: //pedantic-kilby-s9jc724ku9.projects.oryapis.com",
    "rat":<PHONE_NUMBER>,
    "sub": "zxxxxxxx-d186-4251-8369-xxxxxxx"
}

Those are the relationships defined in the UI (I set them using the CLI)
I’m using the default permissions modelling/rules:
import { Namespace, SubjectSet, Context } from "@ory/permission-namespace-types"

/*
Define your OPL rules here. Some examples:
*/
class User implements Namespace {
  related: {
    manager: User[]
  }
}

class Group implements Namespace {
  related: {
    members: (User | Group)[]
  }
}

class Folder implements Namespace {
  related: {
    parents: (File | Folder)[]
    viewers: SubjectSet<Group, "members">[]
  }

  permits = {
    view: (ctx: Context): boolean =>
      this.related.viewers.includes(ctx.subject) ||
      this.related.parents.traverse((p) => p.permits.view(ctx)),
  }
}

class File implements Namespace {
  related: {
    parents: (File | Folder)[]
    viewers: (User | SubjectSet<Group, "members">)[]
    owners: (User | SubjectSet<Group, "members">)[]
  }

  permits = {
    view: (ctx: Context): boolean =>
      this.related.parents.traverse((p) => p.permits.view(ctx)) ||
      this.related.viewers.includes(ctx.subject) ||
      this.related.owners.includes(ctx.subject),

    edit: (ctx: Context) => this.related.owners.includes(ctx.subject),
  }
}

thanks in advance
Describe your ideal solution
Getting the groups the user is membership on
Workarounds or alternatives
Nothing found yet as a workaround
Version
lastest // using cloud solution
Additional Context
No response

This is kinda related to #261 but instead of traits we want to add certain relationships.

@mounirmesselmeni thank you for the report! Unfortunately, the data from Ory Keto does not automatically populate into the ID token. I think that's a great idea though, I'm just not fully sure yet how that could work.
To populate the ID token with any data you want, you can write a custom consent endpoint. A guide for that is here: https://www.ory.sh/docs/hydra/guides/custom-ui-oauth2
You won't need to customize the login endpoint, only the consent endpoint. Using a custom consent endpoint, you can basically say what data goes into your tokens.
Hope this helps!


What

🐞 Problem

🎯 Goal

💡 Possible solutions

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

Addresses #<2188>


Unable to build in Xcode 16.0 — Getting strict concurrency build errors

[x] I have read the documentation.
[x] I have read the limitations.
[x] I could not find my issue.

Describe the bug
I'm getting build errors when I try to use MetaCodable in a Swift Package using Xcode 16:

Is there a recommended way to use this library without tripping these strict concurrency checks?
To Reproduce
Steps to reproduce the behavior:

Create a Swift Package manifest (Package.swift).
Include MetaCodable as a dependency, and add it as a dependency to one of the package's targets.
Try to build that target.
Observe build errors.

Expected behavior
The Swift Package should build with MetaCodable included.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information, remove ones not applicable):

OS: macOS
Version: 15.0.1
Xcode: 16.0.0
Swift: 6.0, 5.9

Additional context
Some things I've tried to resolve the issue:

Setting the // swift-tools-version: in the Package.swift file to 5.9.
Adding swiftLanguageVersions: [.v5] to the Package definition.
Importing MetaCodable using the @preconcurrency keyword (@preconcurrency import MetaCodable).

Thanks for the detailed report @hisaac. Are you seeing just those two errors you have mentioned or are you seeing more errors?
I am able to build with XCode 16 and my CI and Swift Package Index CI is able to build without any issues. Can you help with following details to resolve this:

Sample project that can reproduce error.
swift-syntax version you are using (Can you upgrade to latest version and see if that resolves your issue).

swift-syntax version you are using (Can you upgrade to latest version and see if that resolves your issue).

This was the issue! For whatever reason, it was trying to use an older version of swift-syntax (don't remember specifically what version, but it was 510.x). When I refreshed the cache, it updated to 600.0.1 and is working as expected now.
Thank you for the suggestion. Any idea why it could've cloned an older version originally?

Thank you for the suggestion. Any idea why it could've cloned an older version originally?

Can't say for sure, but older version of MetaCodable was using 510.x version of swift-syntax, may be you recently upgraded MetaCodable?

Ah I figured it out. One of the other dependencies I was using also depends on swift-syntax, but requires a lower version, so it was resolving to that lower version.


spark-sql --database option does not work

Returns NoSuchDatabaseException, because
Spark-2.3.0:org.apache.spark.sql.hive.thriftserver:SparkSQLCLIDriver.scala:Line 171
    if (sessionState.database != null) {
      SparkSQLEnv.sqlContext.sessionState.catalog.setCurrentDatabase(
        s"${sessionState.database}")
    }

does not use our injected catalog.

close for it is outdated. And the problem is not exist now.


Add Lumen ServiceProvider

Removes config_path()/publishes calls

Or we could wrap those calls in function_exists('config_path')

Thanks I removed the imagecache bootstrap stuff from the ServiceProviderLumen. And I added Lumen support in the the default ServiceProvider, so you can register without worrying about the name.
$app->register(Intervention\Image\ImageServiceProvider::class);


Fix metric pointer reference

I was noticing that all the metric values were the same for a Kinesis query:
Before:
aws_kinesis_put_records_success{stream_name="observability-error-stream"} 1
aws_kinesis_put_records_success{stream_name="upshot-aggregated-metrics"} 1
aws_kinesis_put_records_success{stream_name="upshot-aggregated-metrics-dev"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_errors"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_resque"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_spans"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_spans_http_request"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_spans_trace"} 1

I believe it is because the metric in range is a pointer that changes per loop iteration so we'd just be requesting the same metric. See https://stackoverflow.com/questions/20185511/range-references-instead-values
After:
aws_kinesis_put_records_success{stream_name="observability-error-stream"} 0.9999417351278914
aws_kinesis_put_records_success{stream_name="upshot-aggregated-metrics"} 0.6399653183725004
aws_kinesis_put_records_success{stream_name="upshot-aggregated-metrics-dev"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_errors"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_resque"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_spans"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_spans_http_request"} 1
aws_kinesis_put_records_success{stream_name="upshot_instrumentation_spans_trace"} 1

Oh good catch, I imaging that was quite a PITA to debug. Thanks!


Add function to update alignment

Addresses https://github.com/CesiumGS/3d-tiles-tools/issues/134 :
This adds a command updateAlignment that can be applied to B3DM, I3DM, PNTS, and CMPT files, and just ensures that the elignment requirements for the batch- and feature table and the tile data as a whole are met.
I tested it with an old version of the CesiumJS spec data (the one before this commit), and it fixed most of the validation errors from that state. (Adding a spec could make sense, but ... creating the "invalid" data would take most of the time here...). In any case, the README.md still has to be updated.

I added specs based on the "old" CesiumJS specs data (one B3DM, I3DM, PNTS, and CMPT). They all caused validation errors before. The specs are comparing the result of running updateAlignment to the versions that are contained in the golden subdirectory, which no longer cause validation errors.
The README.md has been updated to include the updateAlignment command.
(An aside: One could make a case for adding this "alignment update" as part of the upgrade command. Technically, this would be trivial. But some details might have to be sorted out in terms of the desired configurability (even though the update options are not exposed right now beyond the targetVersion anyhow). Cases where someone wants to fix the alignment of a B3DM without upgrading its glTF 1.0 to 2.0, or someone wants to fix the alignment for B3DM and not for PNTS are unlikely, so it might just be part of the detault targetVersion=1.0 update...)


dartpad.dartlang.org responds with a 404

Currently https://dartpad.dartlang.org responds with a 404 page.  https://dartpad.dartlang.org was the URL for quite a while and now is ingrained into my browser history, so whenever I type "dartpad" into my address bar, it autocompletes to the old address.
It would be nice if it responded with a 308 (or perhaps 301) permanent redirect to https://dartpad.dev/.

Even though DartPad hasn't used the URL in a long time, there are still links around, so a permanent redirect sounds good.

\cc @johnpryan Would you be able to add this redirect? Do you have access?


feat: adds support for zksolc 1.4.1

Motivation

Adds support for zksolc 1.4.1, however waiting for binaries to be released and available at: https://github.com/matter-labs/zksolc-bin/releases. Should be made available today / tomorrow. This will provide support to latest solc version.

Solution

Related to : #341


Multiple clients on the same machine

How do I set it up so that multiple clients (multiple devices) can use the same machine as VPN?
When I simply run the script and load the generated config file onto a second device the connection gets extremely slow and unusable because it's already in use on another device.

Are you using the same keys (i.e the same qr code) on both devices? It works fine for me with three clients with different keys. (To do this, run the wizard again).


[docs] Use concurrent + scheduler over throttle/debounce

Not meant to be merged. Might create a branch to have netlify build always available.

Neat experiment. Will keep an eye on it.
The scroll + TOC highlight is probably the most noticeable difference. Debounce/throttle are not properly translated to scheduler usage but it's good enough for a POC.
https://deploy-preview-15306--material-ui.netlify.com/


Document how to cleanup old segments when doing a backup

A usual setup is to have Kafka Backup running continuously in the background which writes data to the local disk.
Then, in parallel a CronJob will move the data to the target backup storage. Afterwards it is possible to delete old segments and indexes. (NOT the current ones)
We should document how to do that gracefully. (Maybe even provide a script for that)

Was it done btw?

Yes! Good point. Solved by #90


fix printing of list decoration in Firefox

Firefox does not understand the vendor-prefixed version of color-adjust. Thus, won't print the very cool list decoration :cry:
PDFs generated with FF 77:
Before
After

nice catch!


Add code quality plugins to jenkins build

We should look into adding some code quality plugins (like FindBugs, PMD, and/or CheckStyle) to the Jenkins build. This will make it easier for contributors to understand where their contributions need to be updated and will help us produce overall better code.

FWIW, I've started using Netbeans Inspect and Transform.
When enabling all the bells and whistles, there are a few thousands suggestions in the report, although most of them can be either ignored (e.g. using static imports, that's a matter of taste IMHO, I prefer not to use static imports) or are easy to "fix" (missing override annotation or javadoc param etc...)

On a related note, there is also SpotBugs, available as Eclipse and maven plugin https://spotbugs.readthedocs.io/en/latest/maven.html

FWIW, I'm currently looking into spotbugs, looks promising:

there is a Jenkins plugin (https://wiki.jenkins.io/display/JENKINS/Warnings+Next+Generation+Plugin)
supported by maven, Eclipse (and older Netbeans, unfortunately not yet for recent Netbeans)
an additional plugin for extra security checks is also available (OWASP, CWE) https://find-sec-bugs.github.io/

Created  CQ 21366 (PB) in IpZilla

Creating a new one for more recent spotbugs version + plugins

I closed this because the associated PR was closed - I get the feeling there was little enthusiasm for the idea in the end. Feel free to correct me and reopen though.


Opening Send ETH modal is causing error in console

Describe the bug
Opening Send ETH modal is causing error in console. Also I can see many other errors that my slow the wallet.

To Reproduce
Steps to reproduce the behavior:

Go to ETH account
Click on Send ETH modal
Open console
See error

Expected behavior
Should act without errors
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: MacOS
Browser: Chrome, FF
Version 119

Additional context
Reproducible on the dev ETH branch: https://feat-eth-support.wallet.z52da5wt.xyz/account

Errors from the second screenshot are caused by the backend being down

Not reproducible for me on eth dev branch.


Fix bug when num_features != 4

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Fixed with unit test in https://github.com/open-mmlab/mmdetection3d/pull/275

Fixed with unit test in https://github.com/open-mmlab/mmdetection3d/pull/275


SyntaxError: Cannot use import statement outside a module

🐛 Bug Report
I followed this and reported this issue here, however got this response:
This is entirely related to your jest config, and has nothing to do with enzyme. Please file it with jest.
Running yarn test:
arn run v1.22.4
$ jest
 FAIL  __tests__/component.enzyme.test.js
  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/en/configuration.html

    Details:

    /Users/kasra/Documents/JestEnzyme/node_modules/react-native/index.js:13
    import typeof AccessibilityInfo from './Libraries/Components/AccessibilityInfo/AccessibilityInfo';
    ^^^^^^

    SyntaxError: Cannot use import statement outside a module

    > 1 | import 'react-native';
        | ^
      2 | import 'jest-enzyme';
      3 | import Adapter from 'enzyme-adapter-react-16';
      4 | import Enzyme from 'enzyme';

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1257:14)
      at Object.<anonymous> (setup-tests.js:1:1)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.886 s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

To Reproduce

git clone https://gitlab.com/ghasemikasra39/latestrn.git
cd latestrn
yarn install
yarn test

Steps to reproduce the behavior:
Expected behavior
I added this simple test:
/**
 * @jest-environment jsdom
 */
import React from 'react';
import {mount} from 'enzyme';
import {Text} from 'react-native';

describe('Component tested with airbnb enzyme', () => {
  test('App mount with enzyme', () => {
    const wrapper = mount(<Text />);
    // other tests operations
  });
});

Should not get that error.
Link to repl or repo (highly encouraged)
https://gitlab.com/ghasemikasra39/latestrn
envinfo
  System:
    OS: macOS 10.15.3
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Binaries:
    Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm
  npmPackages:
    jest: ^26.0.1 => 26.0.1

Same issue. Any solution ?

Try adding  preset: "react-native" to your Jest config.
And follow this guide to set it up to work with react native.

I see that it's as guide says it should be. but you are still missing  preset: 'react-native' in your jest.config.js

@grosto is right, you need to use the preset or provide some other base configuration with mocks and transforms adjusted.

Dear @grosto
jest.config.js
module.exports = {
  preset: 'react-native',
  collectCoverage: true,
  moduleDirectories: ['node_modules', 'src'],
  transform: {
    '^.+\\.js$': '<rootDir>/node_modules/react-native/jest/preprocessor.js',
  },
  setupFiles: ['<rootDir>setup-tests.js'],
  transformIgnorePatterns: ['node_modules/(?!(jest-)?react-native)'],
  coveragePathIgnorePatterns: ['/node_modules/', '/jest'],
  testEnvironment: 'jsdom',
};

setup-tests.js
import 'react-native';
import 'jest-enzyme';
import Adapter from 'enzyme-adapter-react-16';
import Enzyme from 'enzyme';

/**
 * Set up DOM in node.js environment for Enzyme to mount to
 */
const {JSDOM} = require('jsdom');

const jsdom = new JSDOM('<!doctype html>');
const {window} = jsdom;

function copyProps(src, target) {
  Object.defineProperties(target, {
    ...Object.getOwnPropertyDescriptors(src),
    ...Object.getOwnPropertyDescriptors(target),
  });
}

global.window = window;
global.document = window.document;
global.navigator = {
  userAgent: 'node.js',
};
copyProps(window, global);

/**
 * Set up Enzyme to mount to DOM, simulate events,
 * and inspect the DOM in tests.
 */
Enzyme.configure({adapter: new Adapter()});

Am I correct ?

Are you able to resolve this issue?

Are you able to resolve this issue?

Doesn't sound like it. Any ideas? I'm also looking into this.

puedes configurarlo de esta forma

Dear @ANG95
Can you please write in English.

Dear @ANG95
Can you please write in English.

you can configure it this way
From google translate

@ANG95  why image, why not copy paste as text?

I have the same problem
`    import typeof AccessibilityInfo from './Libraries/Components/AccessibilityInfo/AccessibilityInfo';
^^^^^^
SyntaxError: Unexpected token typeof`

someone has a solution to this?

Same, I just randomly started seeing this as well after moving one of my test files
module.exports = {
  preset: 'jest-expo',
  clearMocks: true,
  testMatch: [
    '<rootDir>/specs/**/*.[tj]s?(x)',
    '**/src/native/**/__tests__/**/*.spec.[jt]s?(x)'
  ],
  roots: ['<rootDir>', '../../'],
  setupFiles: ['../../node_modules/react-native-gesture-handler/jestSetup.js'],
  setupFilesAfterEnv: ['<rootDir>/setup.ts'],
  moduleNameMapper: {},
  transform: {
    '^.+\\.[jt]sx?$': ['babel-jest', { envName: 'test-expo' }]
  },
  transformIgnorePatterns: [
    'node_modules/(?!(jest-)?react-native' +
      '|@react-native-community' +
      '|@react-navigation' +
      '|native-base' +
      '|@expo(nent)?/.*' +
      '|expo-.*/.*' +
      '|@unimodules' +
      '|@codler/react-native-keyboard-aware-scroll-view' +
      '|@react-native-picker' +
      '|victory-.*/.*' +
      '/)'
  ]
};


Add yafti back

customize branding
add description of project
remove system flatpak in favor of user flatpaks

Also maybe maintain a list of "trusted/recommended Flatpak apps"?
But apart from using flatpak-verified, recommending "secure software" is difficult for me. Old projects like Libreoffice, GIMP, Calibre, etc. are probably not very secure

Also maybe maintain a list of "trusted/recommended Flatpak apps"?

There's no reason to maintain any such list on top of only enabling flathub-verified by default.

Old projects like Libreoffice, GIMP, Calibre, etc. are probably not very secure

This is nonsensical for several reasons. For one, old doesn't mean insecure. Two, none of those projects are old. They are all well-maintained.

https://github.com/secureblue/secureblue/pull/90


[BUG] Chain doesn't trigger in queue import. 3.1.12 release

Prerequisites

Versions

PHP version: 7.2
Laravel version: 5.8
Package version: 3.1.12

Description
After update 3.1.12 the method chain in queue import doesn't work anymore. Downgrading to 3.1.11 works perfectly
My Code
$user= auth()->user();

$imports = new PacasImport();
$imports->queue($request->excel)->chain([
    new PrepareNotification($user)
]);

To further explain, the below shows how it works in 3.1.11

[2019-05-08 04:37:10] local.ALERT: Inside StepsImportCompletedHandler - Constructor
[2019-05-08 04:37:18] local.ALERT: [STEPS] Finished processing 1 chunk
[2019-05-08 04:37:20] local.ALERT: [STEPS] Finished processing 1 chunk
[2019-05-08 04:37:21] local.ALERT: [STEPS] Finished processing 1 chunk
[2019-05-08 04:37:21] local.ALERT: Inside StepsImportCompletedHandler - Handler

In 3.1.12, the constructor is called when the job starts but the handler is never called.
Thanks @charger513 , I almost uninstalled the package and went with something else. Downgrading to 3.1.11 makes it work perfectly.


Update TransientIOErrorsRetryingIterator.scala

Description
This PR adds a safe-guard into unbounded awaits when attempting to retrieve the next page of query, change feed or readMany results.  For query and readMany the Cosmos DB SDK allows specifying an end-to-end timeout - for change feed it doesn't (yet). In the spark connector we will apply a 65 seconds end-to-end timeout (in direct mode each query retrieval could take at most 5 seconds in the backend - but given that possibly metadata like addresses etc. need to be retrieved in the flow from Gateway keeping the Gateway timeout of 65 seconds is safer). In addition a 65 + 5 seconds timeout is enforced in the Spark iterator - to cover change feed and just in case for whatever reason the CosmosPagedFlux does not emit the end-to-end timeout as expected in certain edge cases.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - cosmos- spark

/azp run java - cosmos - spark

/azp run java - cosmos - spark


[Suggestion] Option to flip output vertically

I don't need it, so low priority for me, just an idea that could be useful (if I have the time and motivation I could submit a PR).
Having the output textures immediately flipped (human-usable version) can be a nice-to have for anyone looking to use the textures for other reasons than texture packs.

Fixed in a5bf73c

Awesome


perlPackages.X11GUITest: drop pkgs.xlibsWrapper build input

Use only a subset of pkgs.xlibsWrapper package to define inputs.
Dropped unused library imports in NIX_CFLAGS_LINK. -lX11 should not be present there as well, but for some reason build system does not detect is automatically:
perl5.36.0-X11-GUITest> Warning (mostly harmless): No library found for -lX11

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

2 packages built:

perl534Packages.X11GUITest
perl536Packages.X11GUITest


Enhancement : Implemented mobile responsive design to the website

Issue

Fix #18

Description
To make the website look good in mobile devices , i have implemented the mobile responsive design to our website
Changes Made

Home.component.jsx
Navbar.component.jsx
UrlGenerator.component.jsx

Screenshot

Checklist
Before submitting your pull request, ensure that you have completed the following tasks:

Code follows the project's style and conventions.
Code has been tested thoroughly, and all tests pass successfully.
Documentation has been updated to reflect any relevant changes.
All new and modified code is adequately commented for clarity.
Pull request title follows the specified format: [Feature/Enhancement/Bug Fix]: Brief description of the change.

Thanks for working on this :) I personally loved the way you modified the code.

Thank you so much for your kind words : )


Setup GitActions

Setup GitActions so that the workflow is comprehensive.
@lheagy  Any chance you could take a look at this, or walk me through the process.  Seems like there is a bunch of stuff to use.

For sure, I am happy to take a look!

For sure, I am happy to take a look!

Testing branch worked,
Accepted pull request to merge with master, workflow worked
Merged master with develop, workflow did not pass because it is using h5py version 2.10 and that apparently fails, where as Master installs h5py 3.1 and works.
I don't see any difference in the files between the 2 branches. @lheagy Any thoughts on what's going on?

Testing branch worked,
Accepted pull request to merge with master, workflow worked
Merged master with develop, workflow did not pass because it is using h5py version 2.10 and that apparently fails, where as Master installs h5py 3.1 and works.
I don't see any difference in the files between the 2 branches. @lheagy Any thoughts on what's going on?

hmm, I am not too sure, but on first glance, I wonder if it is something to do with dependencies? I am wondering here which version of numpy is installed and if that makes any difference?
https://github.com/kujaku11/mth5/blob/db627866788697a37aa344e8b7d4129e3ea864e3/pyproject.toml#L28

hmm, I am not too sure, but on first glance, I wonder if it is something to do with dependencies? I am wondering here which version of numpy is installed and if that makes any difference?
https://github.com/kujaku11/mth5/blob/db627866788697a37aa344e8b7d4129e3ea864e3/pyproject.toml#L28

Good spot that's probably the issue.

Good spot that's probably the issue.

Install of mt_metadata now runs, but its missing .json and logging_config.yaml files.  Added them in the mt_metadata/MANIFEST.in file and in the mt_metadata/setup.py.  But for that hasn't worked yet. Still testing.  Anyone want to test that they can successfully run:
pip install git+https://github.com/kujaku11/mt_metadata.git

Install of mt_metadata now runs, but its missing .json and logging_config.yaml files.  Added them in the mt_metadata/MANIFEST.in file and in the mt_metadata/setup.py.  But for that hasn't worked yet. Still testing.  Anyone want to test that they can successfully run:
pip install git+https://github.com/kujaku11/mt_metadata.git

Fixed the issues with bundling .json files with mt_metadata.  Now the issue is installing mth5_test_data. @lheagy @kkappler @domfournier  do you guys have any thoughts on the best way to install/download data from the mth5_test_data repository?  Do we just make a setup.py and MANIFEST.in to install all the data?

Fixed the issues with bundling .json files with mt_metadata.  Now the issue is installing mth5_test_data. @lheagy @kkappler @domfournier  do you guys have any thoughts on the best way to install/download data from the mth5_test_data repository?  Do we just make a setup.py and MANIFEST.in to install all the data?


[Enhancement]: Add upper limit of Callbackgaslimit in the document

What would you like us to improve?
In the Chainlink-vrf.md, there is no information on the max limit of callbackgaslimit.  I suggest adding information of upper limit for callbackgaslimit.
How important it is?

Developers usually have custom logic in fulfillRandomWords(), and it is necessary for them to learn the upper limit for callbackgaslimit.
In the paragraph, upper limit for verification gas is mentioned, and it sometimes makes developers(especially non-English speakers) confused about if the upper limit for verification gas is that of callbackgaslimit.

Created a PR here
https://github.com/smartcontractkit/documentation/pull/929


Remove unnecessary diff in RCTImageLoader

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[x] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Summary
This came up during the 0.71 merge. There was an iOS only method we had already shimmed in RCTUIKit:
NSData *UIImagePNGRepresentation(NSImage *image) {
  return NSImageDataForFileType(image, NSBitmapImageFileTypePNG, @{});
}

NSData *UIImageJPEGRepresentation(NSImage *image, CGFloat compressionQuality) {
  return NSImageDataForFileType(image,
                                NSBitmapImageFileTypeJPEG,
                                @{NSImageCompressionFactor: @(1.0)});
}

So we can remove this diff in RCTImageLoader.m that gets nastier with 0.71 where a lot of files have been clang formatted.
Changelog
[macOS] [Fixed] - Remove unnecessary diff in RCTImageLoader
Test Plan
CI should pass

As it turns out, we can't depend on RCTUIKit here, because this file's podspec (React-RCTImage) doesn't take a dependency on RCTUIKit's pod React-Core. The #import <React/RCTUIKit.h> most likely worked out of happenstance.
I went with copying the methods needed over to the other file, as we already had some duplication. Let me know if there's an issue with this approach. I can also just close the PR and leave things as is.


Support tags with digit as first symbol in BooleanFormula

Sometimes we need to launch jobs on particular nodes of our YT cluster in order to test new YT versions, infrastructure changes and so on.
Using --spec with scheduling_tag_filter by node is a good point for such kind of exercise.
Major part of our YT infrastructure operates with domain names starting from number so we have 1.exec.node.fqdn, 2.exec.node.fqdn and so on in //sys/cluster_nodes/<node>/@tags.
Unfortunately, ytsaurus scheduling_tag_filter  doesn't support such kind of tags, failing with:
Error while parsing boolean formula:
2.exec.node.fqdn:9012
 ^

I've tested filter with different values and recorded result in table below

filter
result
error

--spec '{"scheduling_tag_filter"="a.1.exec.node.fqdn:9012"}'
✓

--spec '{"scheduling_tag_filter"="exec.node.fqdn:9012"}'
✓

--spec '{"scheduling_tag_filter"="1.exec.node.fqdn:9012"}'
✗
Error while parsing boolean formula:2.exec.node.fqdn:9012 ^Unexpected character

--spec '{"scheduling_tag_filter"="<IP_ADDRESS>"}'
✗
Error while parsing boolean formula:<IP_ADDRESS>:9012     ^Unexpected character

If exec-node assigns these values automatically, should such tags be supported in YTsaurus?

As a solution, try to use parenthesis around literal, i.e:
--spec '{"scheduling_tag_filter"="(<IP_ADDRESS>)"}'

As a solution, try to use parenthesis around literal, i.e:
--spec '{"scheduling_tag_filter"="(<IP_ADDRESS>)"}'

Unfortunately this isn't help.
Discovered the same problem is applicable to node's dynamic config too


Refactor deployment

This PR does several things:

Remove worker catalogs. Worker configuration values are added to the "runtime" section of their deployment config files. If not specified, we used the default values in Java files.
Change the directory hierarchy of deployments. The old deployment path of a worker is: path/name-files/name/worker, with "path" and "name" specified in a deployment.cfg. The new path is: path/name/worker_x for worker x and path/name/master for master. Worker/master stdout/err, worker.cfg, master.catalog are put inside of their directories.
With these changes, a lot of deployment scripts can be removed/merged. Now we have only one script setup_cluster.py, with an option "-fresh" if we want to start with a new master catalog. Otherwise the master catalog at the deployment path is not changed. Worker config files are always recreated and synced based on the deployment.cfg so that everything is up-to-date after running setup_cluster.py.

Sorry for putting almost everything inside of one commit, since I found it to be hard to separate them into commits that can compile and pass tests.

@senderista There are changes affecting production so I assigned it to you.
@BrandonHaynes You may also want to check it out :)

Is the [runtime] section optional such that existing deployment configuration files will be backwards-compatible, or this now a required section?  Also, are there any optional keys inside the [runtime] section besides max_heap_size that I should know about?  I'll get the deployment creation utility updated.

Nit: "reinitialize" or "overwrite" might be a bit more intuitive option name than "fresh" in setup_cluster.py.

Yes it's an optional section. Heap size is probably the only thing, other keys/values can be specified but usually not used. I changed the arg to be "-fresh_catalog" to be specific.

All comments above have been addressed, most in 0aaf5de.

One potential issue here -- for deployment on the MIT HPC, I need to set some environment flags (e.g., -Djava.net.preferIPv4Stack=true).  My current approach was to hide these in the heap line of the deployment file.  I haven't looked, but I think I can hack around this with something like max_heap_size_gb=2gb -Djava.net.preferIPv4Stack=true.  So, while these workarounds are all hacks, but there exists at least one use case for "extra" flags beyond heap size.
No need to deal with that for this PR (so long as the workaround continues to workaround) but we may want to extend this to support additional flags.  I'm happy to look into doing so, since I have the need.

I see, it's indeed good to have a key for Java flags then. We already have a list of -Dxxx in DeploymentUtils.java when launching master/workers, maybe we can make them use the same interface. I'll leave it to another PR though.
BTW we changed max_heap_size_gb to take a number so it's gonna be max_heap_size_gb=2.

Per discussion with @BrandonHaynes, we will support arbitrary JVM flags in this PR. Additionally, the max_heap_size_gb key will be changed to heap.size.max.gb.

jvm.heap.size.max.gb?  I'll probably want a jvm (java?) prefix for the arbitrary flags.

jvm sounds better.

OK, I think all the comments have been addressed for this PR.

No I didn't ... Thanks! That being said, It would be nice to have some tests for this script. @BrandonHaynes could you check if your stuffs still work with this PR?

Changes look fine to me.
I'm happy to set up tests for this (it's probably also worth eventually using create_deployment.py to create the default deploy.* scripts that come with Myria) -- however, I'm not sure how/if Travis supports multiple languages.

How is the test coverage on this (ad hoc is fine for now, I just want to be sure everything works before I merge)?

All tests have passed, are you looking for more tests..?

I was wondering if the modified deployment scripts (or scripts which exercise the modified deployment code) have been tested.

Since the ad hoc testing has been successful, I'll merge this PR and create a separate issue for deployment tests.

Myria-EC2 updated in https://github.com/uwescience/myria-ec2/pull/17


Added Amazon Redshift dialect and timestamp/date add functions

Coverage decreased (-0.02%) to 98.456% when pulling 171bb160c907a7b895721956918d5f871e260fd9 on mikeengland:add-redshift into 941b7d80166dc201967dbee9c6ac16946f0bbb2e on kayak:master.

Coverage increased (+0.02%) to 98.498% when pulling ba7aad41d05e4e238551dd91651fd15315671ee4 on mikeengland:add-redshift into 941b7d80166dc201967dbee9c6ac16946f0bbb2e on kayak:master.


[Feature Request] Binding a popover trigger to a popover located in parent Vue Component

Existing Component
Yes
Component Name
Popover
Description
Is there a way to have the <el-popover> located in the parent component and the popover trigger in a child component?
The idea is to have a list of elements <elements-list> that contain a <el-button> that trigger showing a popover on click. I want to have the <el-popover> in the parent component to prevent the creation of 40 popovers on each pagination page and instead have just one in which I can switch up the contents.

this really need feature