Physical and magic attacks

Just as the title says, we need a lot of attack types, ranging from hitting your enemies with swords or maces, to using a flintlock pistol and cannon artilery(?), all the way to using good ol magic.
Here are some ideas:

Probably swords made from different metals. All having their ups and downs (expect gold. Gold is too soft and too heavy.)
Daggers (faster but less impactful than a sword)
Maces (Blunt > Slash/Pierce)
Spears (Range over dps? also make it do piercing instead)
Axes + hatchets (Would they be the same as swords/daggers?)


ROX-20429, ROX-20396: compliance results benchmark

Description
Added a benchmark test and a metric
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
~- [ ] Evaluated and added CHANGELOG entry if required~
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
Primarily this PR is a test.  However I did spin up a cluster to ensure the metrics were recorded.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test ocp-4-15-compliance-e2e-tests


Crash on lib/connection

The crash is:
ERR! 2015-05-21T07:13:24.620Z APNS_SOCKET_ERROR {}
ERR! 2015-05-21T07:13:29.082Z APNS_CONNECTED  Open sockets :1
ERR! 2015-05-21T07:13:35.061Z APNS_CONNECTED  Open sockets :2
/media/ephemeral0/glide-server/node_modules/apn/lib/connection.js:202
this.deferredConnection.resolve();
^
TypeError: Cannot read property 'resolve' of null
at Connection. (/media/ephemeral0/glide-server/node_modules/apn/lib/connection.js:202:28)
at TLSSocket.g (events.js:199:16)
at TLSSocket.emit (events.js:104:17)
at TLSSocket. (_tls_wrap.js:950:16)
at TLSSocket.emit (events.js:104:17)
at TLSSocket._finishInit (_tls_wrap.js:460:8)
Thank you very much

Are you able to reliably reproduce the error or was it a one-off occurrence?

I can't reproduce it, but i saw this crash several times.
Any suggestion?

I have some ideas, it'll take me a little while to find time to investigate, but I will look into it.

Thanks :)


Filter relevant course runs to be live

What are the relevant tickets?
Fix https://github.com/mitodl/hq/issues/4493
Description (What does it do?)
Filter relevant course runs to be live
How can this be tested?
Test course about page,for courses that might have a no runs open for enrollments, and runs that are open but no longer live. Both cases should show the same view. They should not appear in the catalog.
Nothing else should break.

@collinpreston So the current definition of is_enrollable is not comprehensive enough, there are few more checks that could be added to it.
For now I removed some unnecessary annotations from relevant course runs and refactored the code a bit.
I think we could put an effort into creating a universal filter for "valid", "enrollable" "live" run, that would be used in the catalog and about page.


feat: Terminal Load Balance

The server-side terminal should provide a JSON schema for its service.
The client-side terminal should choose one target terminal to process the request.
Why:

we can easily horizontally extend the service.
We can deploy in different regions and keep working if anyone is down.
We can remove the hard-code MongoDB terminal_id

#256


December Onboarding

Latest

Updated Various Latest Versions
Added Azure.Storage.File.Shares

Preview

Updated various preview versions.

Legacy Updates

Added Microsoft.Azure.Storage.File.

Docs Build status updates of commit 6ce98b0:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

[Error] Failed to load 1 files, aborting...
Line 138: [Error] W:\sola-s\.optemp\packages\opbuild.scripts.1.82.1\tools\opbuild\docset.prebuild.ps1 failed to execute

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

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

Docs Build status updates of commit 915e32e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

[Error] Failed to load 1 files, aborting...
Line 138: [Error] W:\yxuo-s\.optemp\packages\opbuild.scripts.1.82.1\tools\opbuild\docset.prebuild.ps1 failed to execute

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

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

Docs Build status updates of commit 4093cee:
:clock10: Pending: waiting for processors (11 builds ahead of you)
:warning: Docs Build is busy, currently there are 11 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 4093cee:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

[Error] Failed to load 1 files, aborting...
Line 138: [Error] W:\qgbn-s\.optemp\packages\opbuild.scripts.1.83.0\tools\opbuild\docset.prebuild.ps1 failed to execute

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

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

Docs Build status updates of commit d80322e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

[Error] Failed to load 1 files, aborting...
Line 138: [Error] W:\pats-s\.optemp\packages\opbuild.scripts.1.83.0\tools\opbuild\docset.prebuild.ps1 failed to execute

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

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

Docs Build status updates of commit 88c37e1:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 88c37e1:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

Line 138: [Error] W:\jxdt-s\.optemp\packages\opbuild.scripts.1.83.0\tools\opbuild\docset.prebuild.ps1 failed to execute

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

Docs Build status updates of commit f8eed5b:
:clock10: Pending: waiting for processors (9 builds ahead of you)
:warning: Docs Build is busy, currently there are 9 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit f8eed5b:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

Line 138: [Error] W:\payl-s\.optemp\packages\opbuild.scripts.1.83.0\tools\opbuild\docset.prebuild.ps1 failed to execute

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

Docs Build status updates of commit b3ab05d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

Line 138: [Error] W:\smed-s\.optemp\packages\opbuild.scripts.1.83.0\tools\opbuild\docset.prebuild.ps1 failed to execute

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

Docs Build status updates of commit 58653b1:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1
:x:Error

Details

.openpublishing.publish.config.json
:x:Error

Details

:x:Error

Details

_dependentPackages/ECMA2Yaml/tools/Run.ps1

Line 82: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Exit code: -1
Line 217: [Error] Error happened when executing plug-in script _dependentPackages/ECMA2Yaml/tools/Run.ps1 at step docset_prebuild. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

.openpublishing.publish.config.json

Line 80: [Error] Failed to execute customized script at step docset_prebuild in docset azuredotnet. Please check your .openpublishing.publish.config.json?on the configuration of the plug-ins for docset azuredotnet step docset_prebuild or ask for help?in Docs Support teams channel. Please also include the build report and the following error code for our team to troubleshoot: 1

Line 138: [Error] W:\2uop-s\.optemp\packages\opbuild.scripts.1.83.0\tools\opbuild\docset.prebuild.ps1 failed to execute

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

Docs Build status updates of commit ccbb282:
:clock10: Pending: waiting for processors (9 builds ahead of you)
:warning: Docs Build is busy, currently there are 9 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

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

File
Status
Preview URL
Details

api/Azure.Security.KeyVault.Certificates.WellKnownIssuerNames.Unknown.yml
:warning:Warning
View
Details

api/Microsoft.Extensions.Azure.EventHubClientBuilderExtensions.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Management.Fluent.Azure.PrivateDnsZones.yml
:warning:Warning
View
Details

api/Microsoft.Extensions.Azure.EventHubClientBuilderExtensions.AddEventHubProducerClientWithNamespace.yml
:warning:Warning
View
Details

api/Microsoft.Extensions.Azure.EventHubClientBuilderExtensions.AddEventHubProducerClient.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Management.Fluent.IAzure.PrivateDnsZones.yml
:warning:Warning
View
Details

api/Azure.Messaging.EventHubs.yml
:warning:Warning
View
Details

api/Azure.Security.KeyVault.Certificates.yml
:warning:Warning
View
Details

api/Azure.Security.KeyVault.Certificates.DeleteCertificateOperation.yml
:warning:Warning
View
Details

api/Azure.Messaging.EventHubs.EventHubProducerClientOptions.yml
:warning:Warning
View
Details

api/Azure.Security.KeyVault.Certificates.RecoverDeletedCertificateOperation.yml
:warning:Warning
View
Details

api/Azure.Security.KeyVault.Certificates.WellKnownIssuerNames.yml
:warning:Warning
View
Details

xml/Azure.Data.AppConfiguration/ConfigurationClient.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationModelFactory.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationSetting.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/SettingSelector.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Authorization/EventHubSharedKeyCredential.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.CheckpointStore.Blob/BlobPartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/ConsumerDisconnectedException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsClientClosedException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsCommunicationException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsResourceNotFoundException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsTimeoutException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/MessageSizeExceededException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/QuotaExceededException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/ServiceBusyException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/EventHubProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/LastEnqueuedEventProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/PartitionProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/Checkpoint.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/EventProcessorClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/InMemoryPartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionClosingEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionContext.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionInitializingEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionOwnership.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionProcessorCloseReason.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessErrorEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessingStoppedReason.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/BatchOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/CreateBatchOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventData.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConnection.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConnectionOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConsumerClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConsumerClientOptions.xml
:white_check_mark:Succeeded

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

api/Azure.Security.KeyVault.Certificates.WellKnownIssuerNames.Unknown.yml

[Warning] 1 invalid cross reference(s) "Azure.Security.KeyVault.Certificates.CertificateClient.MergeCertificateAsync(Azure.Security.KeyVault.Certificates.MergeCertificateOptions,System.Threading.CancellationToken)".

api/Microsoft.Extensions.Azure.EventHubClientBuilderExtensions.yml

[Warning] 1 invalid cross reference(s) "Azure.Messaging.EventHubs.EventHubProducerClient".

api/Microsoft.Azure.Management.Fluent.Azure.PrivateDnsZones.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Management.PrivateDns.Fluent.IPrivateDnsZones".

api/Microsoft.Extensions.Azure.EventHubClientBuilderExtensions.AddEventHubProducerClientWithNamespace.yml

[Warning] 1 invalid cross reference(s) "Azure.Messaging.EventHubs.EventHubProducerClient".

api/Microsoft.Extensions.Azure.EventHubClientBuilderExtensions.AddEventHubProducerClient.yml

[Warning] 1 invalid cross reference(s) "Azure.Messaging.EventHubs.EventHubProducerClient".

api/Microsoft.Azure.Management.Fluent.IAzure.PrivateDnsZones.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Management.PrivateDns.Fluent.IPrivateDnsZones".

api/Azure.Messaging.EventHubs.yml

[Warning] 1 invalid cross reference(s) "Azure.Messaging.EventHubs.EventHubProducerClient".

api/Azure.Security.KeyVault.Certificates.yml

[Warning] 4 invalid cross reference(s) "Azure.Security.KeyVault.Certificates.CertificateClient.StartDeleteCertificate(System.String,System.Threading.CancellationToken)", "Azure.Security.KeyVault.Certificates.CertificateClient.StartDeleteCertificateAsync(System.String,System.Threading.CancellationToken)", "Azure.Security.KeyVault.Certificates.CertificateClient.StartRecoverDeletedCertificate(System.String,System.Threading.CancellationToken)", "Azure.Security.KeyVault.Certificates.CertificateClient.StartRecoverDeletedCertificateAsync(System.String,System.Threading.CancellationToken)".

api/Azure.Security.KeyVault.Certificates.DeleteCertificateOperation.yml

[Warning] 2 invalid cross reference(s) "Azure.Security.KeyVault.Certificates.CertificateClient.StartDeleteCertificate(System.String,System.Threading.CancellationToken)", "Azure.Security.KeyVault.Certificates.CertificateClient.StartDeleteCertificateAsync(System.String,System.Threading.CancellationToken)".

api/Azure.Messaging.EventHubs.EventHubProducerClientOptions.yml

[Warning] 1 invalid cross reference(s) "Azure.Messaging.EventHubs.EventHubProducerClient".

api/Azure.Security.KeyVault.Certificates.RecoverDeletedCertificateOperation.yml

[Warning] 2 invalid cross reference(s) "Azure.Security.KeyVault.Certificates.CertificateClient.StartRecoverDeletedCertificate(System.String,System.Threading.CancellationToken)", "Azure.Security.KeyVault.Certificates.CertificateClient.StartRecoverDeletedCertificateAsync(System.String,System.Threading.CancellationToken)".

api/Azure.Security.KeyVault.Certificates.WellKnownIssuerNames.yml

[Warning] 1 invalid cross reference(s) "Azure.Security.KeyVault.Certificates.CertificateClient.MergeCertificateAsync(Azure.Security.KeyVault.Certificates.MergeCertificateOptions,System.Threading.CancellationToken)".

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

Docs Build status updates of commit 04774d8:
:clock10: Pending: waiting for processors (23 builds ahead of you)
:warning: Docs Build is busy, currently there are 23 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 04774d8:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/Microsoft.Azure.Management.Fluent.IAzure.PrivateDnsZones.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Management.Fluent.Azure.PrivateDnsZones.yml
:warning:Warning
View
Details

api/Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync.yml
:warning:Warning
View
Details

xml/Azure.Data.AppConfiguration/ConfigurationClient.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationModelFactory.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationSetting.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/SettingSelector.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Authorization/EventHubSharedKeyCredential.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.CheckpointStore.Blob/BlobPartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/ConsumerDisconnectedException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsClientClosedException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsCommunicationException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsResourceNotFoundException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsTimeoutException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/MessageSizeExceededException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/QuotaExceededException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/ServiceBusyException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/EventHubProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/LastEnqueuedEventProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/PartitionProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/Checkpoint.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/EventProcessorClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/InMemoryPartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionClosingEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionContext.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionInitializingEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionOwnership.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionProcessorCloseReason.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessErrorEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessingStoppedReason.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/BatchOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/CreateBatchOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventData.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConnection.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConnectionOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConsumerClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConsumerClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubProducerClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubProducerClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsRetryMode.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsRetryOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsRetryPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsTransportType.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventPosition.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/PartitionContext.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/PartitionEvent.xml
:white_check_mark:Succeeded

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

api/Microsoft.Azure.Management.Fluent.IAzure.PrivateDnsZones.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Management.PrivateDns.Fluent.IPrivateDnsZones".

api/Microsoft.Azure.Management.Fluent.Azure.PrivateDnsZones.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Management.PrivateDns.Fluent.IPrivateDnsZones".

api/Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync.yml

[Warning] 4 invalid cross reference(s) "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(Azure.Messaging.EventHubs.EventData%2cSystem.Threading.CancellationToken)>", "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(Azure.Messaging.EventHubs.EventData%2cAzure.Messaging.EventHubs.SendEventOptions%2cSystem.Threading.CancellationToken)>", "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(System.Collections.Generic.IEnumerable%7bAzure.Messaging.EventHubs.EventData%7d%2cSystem.Threading.CancellationToken)>", "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(System.Collections.Generic.IEnumerable%7bAzure.Messaging.EventHubs.EventData%7d%2cAzure.Messaging.EventHubs.SendEventOptions%2cSystem.Threading.CancellationToken)>".

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

Docs Build status updates of commit 57a620e:
:clock10: Pending: waiting for processors (37 builds ahead of you)
:warning: Docs Build is busy, currently there are 37 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 56d2d23:
:clock10: Pending: waiting for processors (23 builds ahead of you)
:warning: Docs Build is busy, currently there are 23 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 56d2d23:
:warning: Validation status: warnings

File
Status
Preview URL
Details

api/Microsoft.Azure.Management.Fluent.Azure.PrivateDnsZones.yml
:warning:Warning
View
Details

api/Microsoft.Azure.Management.Fluent.IAzure.PrivateDnsZones.yml
:warning:Warning
View
Details

api/Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync.yml
:warning:Warning
View
Details

docfx.json
:white_check_mark:Succeeded

docs-ref-toc/top_level_toc.yml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationClient.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationModelFactory.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/ConfigurationSetting.xml
:white_check_mark:Succeeded

xml/Azure.Data.AppConfiguration/SettingSelector.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Authorization/EventHubSharedKeyCredential.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.CheckpointStore.Blob/BlobPartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/ConsumerDisconnectedException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsClientClosedException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsCommunicationException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsResourceNotFoundException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/EventHubsTimeoutException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/MessageSizeExceededException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/QuotaExceededException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Errors/ServiceBusyException.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/EventHubProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/LastEnqueuedEventProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Metadata/PartitionProperties.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/Checkpoint.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/EventProcessorClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/InMemoryPartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionClosingEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionContext.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionInitializingEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionManager.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionOwnership.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/PartitionProcessorCloseReason.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessErrorEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessEventArgs.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs.Processor/ProcessingStoppedReason.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/BatchOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/CreateBatchOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventData.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConnection.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConnectionOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConsumerClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubConsumerClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubProducerClient.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubProducerClientOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsRetryMode.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsRetryOptions.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsRetryPolicy.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventHubsTransportType.xml
:white_check_mark:Succeeded

xml/Azure.Messaging.EventHubs/EventPosition.xml
:white_check_mark:Succeeded

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

api/Microsoft.Azure.Management.Fluent.Azure.PrivateDnsZones.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Management.PrivateDns.Fluent.IPrivateDnsZones".

api/Microsoft.Azure.Management.Fluent.IAzure.PrivateDnsZones.yml

[Warning] 1 invalid cross reference(s) "Microsoft.Azure.Management.PrivateDns.Fluent.IPrivateDnsZones".

api/Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync.yml

[Warning] 4 invalid cross reference(s) "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(Azure.Messaging.EventHubs.EventData%2cSystem.Threading.CancellationToken)>", "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(Azure.Messaging.EventHubs.EventData%2cAzure.Messaging.EventHubs.SendEventOptions%2cSystem.Threading.CancellationToken)>", "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(System.Collections.Generic.IEnumerable%7bAzure.Messaging.EventHubs.EventData%7d%2cSystem.Threading.CancellationToken)>", "<xref:Azure.Messaging.EventHubs.EventHubProducerClient.SendAsync(System.Collections.Generic.IEnumerable%7bAzure.Messaging.EventHubs.EventData%7d%2cAzure.Messaging.EventHubs.SendEventOptions%2cSystem.Threading.CancellationToken)>".

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


Minor doc update for getting list of system types

Signed-off-by: Yussuf Shaikh<EMAIL_ADDRESS>

/cc @Prajyot-Parab @pravin-dsilva


The websites are in a sorry state.

camping.rubyforge.org / whywentcamping.com

is unreadable because of a missing background.
scrolling is dog slow
the site is uglier than whywentcamping.judofyr.net. The theme of the homepage clashes with the rest of the site (book, API).

whywentcamping.judofyr.net gives 404 for /reference and /news.
http://ruby-camping.com/ adds little and dilutes the web presence. Furthermore, the white rectangle behind the menu is too short, the 'Documentation' link sticks out.
All graphic problems are experienced in Chrome on OS X 10.6.

Hi pygy
these are the product of a long-forgotten discussion and debate. Jenna
(Bluebie) is responsible for camping.rubyforge.org - personally I like
the design and the neat font trick, but the complex markup (or
something) does slow it up a bit.
whywentcamping.judofyr.net is a bit legacy, replaced (IIRC) by the
above. A fix should be simple, but I can't recall whether it's open to
be maintained by the community...
http://ruby-camping.com is the work of Philippe Monnet (techarch),
which led to Bluebie's design reaction :-)
I don't think Camping will ever have a Sinatra-like website, because
it has the kind of following that's likely to produce all sorts of
styles and approaches. Although we all seem to get on okay, judging by
the previous discussion on this subject we'd probably ever agree on a
definitive 'Camping website. Although camping.rubyforge.org should be
it (maybe we could have a 'no graphics' alternative at some point :-)
DaveE

camping.rubyforge.org / whywentcamping.com

is unreadable because of a missing background.
scrolling is dog slow
the site is uglier than whywentcamping.judofyr.net. The theme of
the homepage clashes with the rest of the site (book, API).

whywentcamping.judofyr.net gives 404 for /reference and /news.
http://ruby-camping.com/ adds little and dilutes the web presence.
Furthermore, the white rectangle behind the menu is too short, the
'Documentation' link sticks out.
All graphic problems are experienced in Chrome on OS X 10.6.

I remember the ordeal, actually, I was there.
It's a matter of taste, I still find that _why's design is the best fit for the library. It could be (and probably was) a Camping app as light as the examples provided with the lib.
Jenna's font trick is impressive, but the menu is unreadable, and I find the design distracting. The lack of consistency is also problematic, IMO.
Whatever happens, camping.rubyforge.net should still be repaired. The CSS is too complex for me, otherwise I would have provided a patch.


Opt-out of sudo - allow sudo=False to work with --sudo

Is your feature request related to a problem? Please describe
More than 2/3s of my tasks use sudo.  However, passing sudo=True to all operations that use them (e.g. anything uses apt.packages()) is a lot of copy/pasting.
Describe the solution you'd like

Is there a DRYer way of using sudo?
Can I turn off warnings at runtime that complain about using sudo=False with --sudo?
Can operations have a way to opt-out of sudo when --sudo is passed, without warnings or exceptions?

The workaround I have is to always pass the --sudo flag at runtime.
> pyinfra --sudo --use-sudo-password @local deploy_*.py

This handles most tasks, except those few that do not use sudo.  In those rarer cases, I hardcode sudo=False to the few operations that need it.
Issue 1
Lately, I've noticed there is a warning that emits when I run the latter command:
    Invalid auth argument: cannot use `use_sudo_password=('pyinfra-sudo-askpass', 'password')` without `sudo`

This is complaining about my passing sudo=False  together with --sudo, and it complains a lot.
Can I turn this warning off?
Issue 2
I see there is some thought about throwing an exception instead of a warning.  An exception which would wreck this workaround and leave me without solutions to my original problem.
I request not to throw an exception here until you have a way to let operations opt-out of  --sudo.

@pylang to fix the default argument you could set sudo as a config variable, ie:
SUDO = True

server.shell(...

This would avoid needing to pass it as a CLI argument every invokation.
Regarding the warnings - you raise an issue here where the global configured defaults (CLI arg or config) for an operation may differ from operation specific auth arguments and should not show any warning in those cases. So the warning check neeeds to identify if the invalid argument combination is an accident or intentional (as in this case). This kind of side effect is part of why I went down the warning route because it's hard to get this kind of thing right, and an exception would be much more painful for everyone!

Pushed https://github.com/Fizzadar/pyinfra/commit/9f3255934be976e1fbc92276e9b00d0f24043533 which disables the warnings in the described scenario, and just released in v1.4.1! Going to close this issue now as I believe this is everything resolved.


Fixed #35639 -- Improved admin's delete confirmation page title.

Trac ticket number
ticket-35639
Branch description
Currently, both the delete_selected actions confirmation page and the page for deleting a single object have the title "Are you sure?"
The "Are you sure" is immediately repeated in the sentence below.
I propose replacing the title with the value from the breadcrumb, "Delete multiple objects" and "Delete", to make it clearer to users that they are about to confirm a destructive action.
(This has happened multiple times in the last few years, and has been reported as a problem by a client, it's not just me bikeshedding here.)
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[x] I have checked the "Has patch" ticket flag in the Trac system.
[x] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

@nessita Thank you for the review! I have added two assertions to existing tests.

Thank you!


Feature request: retry returns Promise

Not sure if this has been implemented yet but it seems I can't get it working. I want to get the value returned by the retry so that it can be used by next chained promise. For example,
const retry = require('bluebird-retry');
... ...
const result =  retry(func, { interval: 2000 }).done((res) => Promise.resolve(res));

I'd expect the variable result to be res promise, but it' undefined instead.
Anyway I can get the promise back after retry call?

This has nothing to do with bluebird-retry, it's that you're using the .done handler which returns undefined as noted in the bluebird api.
If you want a promise chain you should use .then at which point you can get your return value.

Thanks for pointing that out!


Var and Funk changes

We are planning to rename some things. Is your repo up to date with all of your latest changes?
We could convert your patches as we do the renamings and make a pull request on this repo with the fixed patches.
See also: https://github.com/vvvv/VL.Stride/issues/356

Thanks for the offer I am currently mainly sketching things and the repo is quiet messy I think once your changes are released I will look into it and come back to you

The idea is that if we rename the Var data type, everything on your patches would be red. if we open them while we rename the type, it will be converted automatically.
the other changes have been released already in the latest previews, you can update and see if you get along. let me know if anything is unclear.

ok, we decided on the new names. if you pushed everything to your repo, I can rename it in one go. let me know...


Cache boost

Codecov Report

Merging #22 (1c953ec) into master (752bebb) will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   92.95%   93.02%   +0.07%
==========================================
  Files          43       43
  Lines        4129     4129
==========================================
+ Hits         3838     3841       +3
+ Misses        291      288       -3

Impacted Files
Coverage Δ

unit_test/tstGridOperator2d.hpp
98.18% <0.00%> (+1.81%)
:arrow_up:

unit_test/tstGridOperator3d.hpp
98.86% <0.00%> (+2.27%)
:arrow_up:

Continue to review full report at Codecov.

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

@sslattery I finally fixed this - should be ready to merge


Add pkgconfig support

Add pkgconfig file, with automatic generation, usable both during build phase and after installation

Cool, thanks @adevress!


Rollout integration

Rollout Integration
If you are using Rollouts by ArgoCD instead of deployments - krr won't show it as it doesnt support rollouts.
since we are using krr and we are relying heavily on Rollouts - we created this PR in-order for krr to bring recommendations to rollouts as well.
To not make huge changes in the way krr works, I have added a change to the kubernetes client - added 2 functions:
list_rollout_for_all_namespaces
list_rollout_for_all_namespaces_with_http_info
Which are copies of the original functions of deployment, just for rollouts.
This is the most minimal way i've found to do this change and add support for rollouts (using any other custom object api by kubernetes resulted in it not being good enough for V1DeploymentList or any V1CustomList)

Just checked and _list_rollouts fails with 404 not found in my cluster. Despite me having an ArgoCD installed, it seems that I do not have rollouts API. So that should be addressed also.


Delete shortcut does not work

I have no idea why

If anyone can help me in doing this, please do. I cannot figure it out and I have disabled it as a result. Meanwhile, if you want to delete the gestures, you will have to clear app data and start from scratch.

Closing this for now, because no fix available.

Reopening this in case somebody wants to help (stupid me)

Fixed


Sounds like an output midi lost a content input style.

I need an output that should maintain some of the content input style.
So I can tell it's from the content.
However, after style transfer, it's difficult to catch the content input style from the output.
Is there a way to conserve input music like 40 ~ 50 percent and add a different style?
Maybe this is the limitation of the current model?
I found that you added content input to an output midi again at the last stage in the demo site.

Normally only the harmony is preserved from the content input. Neither style nor the melody of the content input is preserved. This is why I'm adding the content melody to the output.
To achieve what you want, you could try to interpolate the styles of both songs as described in section VI.E of the paper. You would need to feed both songs to the style encoder to obtain two style embeddings s1 and s2 and then "blend" them e.g. with s = 0.4 * s1 + 0.6 * s2 and feed this s as the style embedding to the decoder. But note that this still won't allow you to preserve any specific parts of the content input, e.g. there will still be no melody. All the model will try to do is come up with an accompaniment style that is in between the two.


docs: revamp README

This PR completely revamps the README based on some feedback from Jim Baxter on Twitter.
🖼 See README.md rendered here.
Screenshot

Joe, this looks great! It's exactly what I did to run your script locally on my macbook using terminal. One suggestion since I had to do this, you might want to add a note about commenting out the amountTotal part in index.js and adding console.log(payouts); in case payments.data is Null or undefined. Not sure if that had to do with my Stripe payouts. Once I did that it worked beautifully. I plan to run it once a week and look forward to start seeing green boxes :). I'll also look into putting it on an automatic schedule.

Oh yeah! Good call about that. I should probably just add a check and log if it's null or undefined. If I had used TypeScript, I would have caught those errors sooner.
Good callout!


Table in tutorial displays wrong

From tutorial page:
feature Perl 6 007 Python
braces yes yes no user-defined operators yes yes no variable declarations yes yes no macros yes yes no implicit typecasts yes no no sigils yes no no multis yes no no implicit returns yes no no

Thank you for noticing. 06f326c fixes the table in the tutorial in the simplest way possible.
Before closing this issue I'd like to

[ ] Explore using Github Flavored Markdown tables
[ ] Explore using HTML tables (in case GFM tables aren't good enough of don't convert easily)
[ ] Unbreak the conversion script, which currently would produce a pre code thing instead of a nicely colored table

GH tables render nicely; I didn't need to make any changes to the conversion script because they also convert nicely.
Closing.


Namecoin Core flake

Adds a Nix flake for Namecoin-Core.
TODO:

[X] core packages build
[x] GUI builds
[X] devShell
[x] module for namecoind
[ ] figure out versioning

Notes:

I used the bitcoin nix expression to figure out the qt stuff but haven't managed to build it.
the versioning more or less matches bitcoin, might have to just hardcode it.
the core packages built fine until I added some of this qt stuff, but the error is that it can't find core cpp libraries. Stuck on this.

so I'm kinda dead in the water with the Qt part of this @jonringer . Could we pair at some point?

Yea, we can. Unfortunately I'm visiting family until the weekend. Sunday or monday?

Yea, we can. Unfortunately I'm visiting family until the weekend. Sunday or monday?

I think I'm good actually!  Moving on to cleanup / container / module stuff.

Thanks :+1: . I'm trying to stay away from adding multiple files, just because I think it'll make it less likely for the upstream project to incorporate the flake. wdyt?

@nrdsp and I had a really good chat. I think moving forward we should

[ ] Update the flake conventions
[ ] Update the upstream to a more recent checkout?
[ ] Check the packages still build
[ ] Somehow test the module (nixosTest?)

Hey, I tried consuming this flake nixos module and encountered the following error:
error: attribute 'namecoin-core' missing

       at /nix/store/p0ivsgkf349snq28mba2viva6h3sny3v-source/flake.nix:100:13:

           99|             microvm.nixosModules.host
          100|             namecoin-core.nixosModules.namecoin-core
             |             ^
          101|           ];

After inspecting the flake with nix flake show, I can see that the output of namecoin-core.nixosModules does not have a namecoin-core value, it has a list of systems instead. My guess was that this was being caused because the nixosModules is being defined inside the flake-utils eachSystem function, causing each ouput value to have a list of system before the actual closure value.
➜  nix flake show github:jurraca/namecoin-core/flake
github:jurraca/namecoin-core/dfa1676ab3531b34667fc51540338cf538be0ea5
[...]
├───nixosModules
│   ├───aarch64-linux: NixOS module
│   ├───x86_64-darwin: NixOS module
│   └───x86_64-linux: NixOS module
[...]

I have paired with @nrdsp to explore this and we end up finding a solution.
We moved the nixosModules definition to outside of the eachSystem call and replace defaultPackage reference inside the module definition with pkgs.namecoin-core given that we are using a overlay for the nixpkgs to include namecoin-core in the store.
This worked fine and now I can do the following:
pkgs.lib.nixosSystem {
    modules = [ namecoin-core.nixosModules.namecoin-core ];

in my flake.nix.
@jonringer Could you have a look at this change and let me know if this is the best option to solve this, please? :pray:


fix chefspec

Mostly it reflects the old source based install state. I fixed up a bit of it to pass, but there's still some work to be done

All done


Swagger fraction don't work with Microprofile Fault Tolerance

Describe the bug
When we use the Swagger fraction, it import a war (swagger-ui.war) to our project. With this, when we start our application the thorntail will do two deploy( one to our application and other to swagger-ui.war). Furthermore, the swagger-ui.war uses CDI (it has a beans.xml inside them).
When we start the thorntail using Swagger fraction, this take those steps:
1 Installs the fractions into server.
2 Deploy of swagger-ui.war
3 Deploy of our application.
These two applications run on the same JVM.
With this, when we run the application that uses Microprofile Fault Tolerance and Swagger fraction, the io.smallrye.faulttolerance.HystrixInitializer.onStartup() run twice because which application will start the fraction and run the io.smallrye.faulttolerance.HystrixInitializer that is annotated with @ApplicationScope. The Hystrix uses some static attributes and when io.smallrye.faulttolerance.HystrixInitializer.onStartup() run twice, it generate a error like:
Caused by: java.lang.IllegalStateException: Another strategy was already registered.
To Reproduce
Steps to reproduce the behavior:
Put the following dependence on the pom:
<dependency>             <groupId>io.thorntail</groupId>             <artifactId>swagger-webapp</artifactId>             <version>${version.thorntail}</version>         </dependency>
Use the Microprofile Fault Tolerance in a some point of project.

Thorntail v2 issues should be raised in JIRA: https://issues.jboss.org/browse/THORN
On a side note, Swagger is not verified to work with MicroProfile in any way


missing FROM-clause entry for table

Started seeing this error again after upgrading from preview21 to preview24 - I say again because it looks like a regression of https://github.com/prisma/prisma-client-js/issues/322, with the error message being identical, save for the for table part now including the actual name of the table rather than an arbitrary identifier like j1.
Example error message thrown during a query:
Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState("42P01"), message: "missing FROM-clause entry for table \"_ExternalFilesOnBundleVersions\"", detail: None, hint: None, position: Some(Original(268)), where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("parse_relation.c"), line: Some(3140), routine: Some("errorMissingRTE") }) }) })

Reproduction is still https://github.com/prisma/prisma-client-js/issues/322#issuecomment-564802972?

Okay, I did some investigating, and it looks like it's not quite a regression - the setup in the previous issue no longer triggers this error.
However, I was able to replicate this with the following setup instead:
Schema:
model Foo {
  id String @id @default(cuid())
  a  A[]
}

model A {
  id   String  @id @default(cuid())
  name String?
  foo  Foo?
  b    B[]
}

model B {
  id String @id @default(cuid())
  a  A[]
}

Query:
await db.foo.findMany({
  select: {
    id: true,
    a: {
      select: {
        id: true,
        b: {
          select: {
            id: true
          }
        }
      }
    }
  }
});

This throws the following message:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState("42P01"), message: "missing FROM-clause entry for table \"_AToB\"", detail: None, hint: None, position: Some(Original(27)), where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("parse_relation.c"), line: Some(3140), routine: Some("errorMissingRTE") }) }) })

Poking around in this setup, I've found that the error goes away if field foo is removed from model A, and field a is removed from model B, so it looks like two way relations may have something to do with this.

Thanks.
Can you possibly set the ENV var DEBUG=* and change your Prisma Client instantiation to const prisma = new PrismaClient({ log: ['query', 'info', 'warn'], }) and post the full output you are getting? Might be helpful later when reproducing.

Same problem here (on preview023 and preview024) :(
reproduction:
model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String?
  published Boolean @default(false)
  author    User?
}

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
  streets Street[]
}

model Street {
  id Int @id @default(autoincrement())
  street String
  users User[]
}

This works:
{
  findManyUser {
    id
    streets {
      id
    }
  }
}

leading to
prisma:query SELECT `dev`.`User`.`id` FROM `dev`.`User` WHERE 1=1 LIMIT ? OFFSET ?
prisma:query SELECT `B`, `A` FROM `dev`.`_StreetToUser` WHERE `B` IN (?,?)
prisma:query SELECT `dev`.`Street`.`id` FROM `dev`.`Street` WHERE 1=0 LIMIT ? OFFSET ?

This fails:
{
  findManyPost {
    id
    author {
      id
      streets {
        id
      }
    }
  }
}

leading to
prisma:query SELECT `dev`.`Post`.`id`, `dev`.`Post`.`author` FROM `dev`.`Post` WHERE 1=1 LIMIT ? OFFSET ?
prisma:query SELECT `dev`.`User`.`id`, `dev`.`_StreetToUser`.`streets` FROM `dev`.`User` WHERE `dev`.`User`.`id` IN (?,?) LIMIT ? OFFSET ?

Thanks for the reproduction. I was able to reproduce this in both preview024 and the latest alpha :
Prisma CLI Version<EMAIL_ADDRESS>Current platform     : darwin
Query Engine         : prisma 6aa23a61c78a5418a0231347458d639aa337ec1d (at /Users/harshit/.nvm/versions/node/v12.15.0/lib/node_modules/prisma2/query-engine-darwin)
Migration Engine     : migration-engine-cli 6aa23a61c78a5418a0231347458d639aa337ec1d (at /Users/harshit/.nvm/versions/node/v12.15.0/lib/node_modules/prisma2/migration-engine-darwin)
Introspection Engine : introspection-core 6aa23a61c78a5418a0231347458d639aa337ec1d (at /Users/harshit/.nvm/versions/node/v12.15.0/lib/node_modules/prisma2/introspection-engine-darwin)

Debug output(from alpha):
╰─ ts-node index.ts                                                                                ─╯
  prisma-client {
  prisma-client   engineConfig: {
  prisma-client     cwd: '/Users/harshit/code/reproductions/issue-574/prisma',
  prisma-client     debug: false,
  prisma-client     datamodelPath<EMAIL_ADDRESS>  prisma-client     prismaPath: undefined,
  prisma-client     datasources: [],
  prisma-client     generator: {
  prisma-client       name: 'client',
  prisma-client       provider: 'prisma-client-js',
  prisma-client       output: '/Users/harshit/code/reproductions/issue-574/node_modules/@prisma/client',
  prisma-client       binaryTargets: [],
  prisma-client       config: {}
  prisma-client     },
  prisma-client     showColors: true,
  prisma-client     logLevel: undefined,
  prisma-client     logQueries: undefined,
  prisma-client     env: {
  prisma-client       DATABASE_URL: 'postgresql://harshit:Harshit00@localhost:5432/issue_client_574?schema=public'
  prisma-client     },
  prisma-client     flags: []
  prisma-client   }
  prisma-client } +0ms
  prisma-client Prisma Client call: +8ms
  prisma-client prisma.foo.findMany({
  prisma-client   select: {
  prisma-client     id: true,
  prisma-client     a: {
  prisma-client       select: {
  prisma-client         id: true,
  prisma-client         b: {
  prisma-client           select: {
  prisma-client             id: true
  prisma-client           }
  prisma-client         }
  prisma-client       }
  prisma-client     }
  prisma-client   }
  prisma-client }) +1ms
  prisma-client Generated request: +0ms
  prisma-client query {
  prisma-client   findManyFoo {
  prisma-client     id
  prisma-client     a {
  prisma-client       id
  prisma-client       b {
  prisma-client         id
  prisma-client       }
  prisma-client     }
  prisma-client   }
  prisma-client }
  prisma-client  +0ms
  getos { platform: 'darwin', libssl: undefined } +0ms
  engine {
  engine   PRISMA_DML_PATH<EMAIL_ADDRESS>  engine   PORT: '58724',
  engine   RUST_BACKTRACE: '1',
  engine   RUST_LOG: 'info',
  engine   OVERWRITE_DATASOURCES: '[]',
  engine   CLICOLOR_FORCE: '1'
  engine } +0ms
  engine { cwd: '/Users/harshit/code/reproductions/issue-574/prisma' } +0ms
  plusX Execution permissions of /Users/harshit/code/reproductions/issue-574/node_modules/@prisma/client/runtime/query-engine-darwin are fine +0ms
  engine { flags: [ '--enable-raw-queries' ] } +1ms
  engine stderr Printing to stderr for debugging +20ms
  engine stderr Listening on <IP_ADDRESS>:58724 +0ms
  engine stdout {
  timestamp: 'Mar 19 14:32:05.064',
  level: 'INFO',
  target: 'quaint::pooled',
  fields: { message: 'Starting a postgresql pool with 9 connections.' }
} +1ms
  engine stdout {
  timestamp: 'Mar 19 14:32:05.070',
  level: 'INFO',
  target: 'prisma::server',
  fields: {
    message: 'Started http server on <IP_ADDRESS>:58724',
    'log.target': 'prisma::server',
    'log.module_path': 'prisma::server',
    'log.file': 'query-engine/prisma/src/server.rs',
    'log.line': 95
  }
} +5ms
  printStack callsite Error
    at Object.s [as Foo] (/Users/harshit/code/reproductions/issue-574/node_modules/@prisma/client/runtime/index.js:1:44641)
    at Object.n.<computed> [as findMany] (/Users/harshit/code/reproductions/issue-574/node_modules/@prisma/client/runtime/index.js:1:46267)
    at /Users/harshit/code/reproductions/issue-574/index.ts:46:53
    at step (/Users/harshit/code/reproductions/issue-574/index.ts:33:23)
    at Object.next (/Users/harshit/code/reproductions/issue-574/index.ts:14:53)
    at /Users/harshit/code/reproductions/issue-574/index.ts:8:71
    at new Promise (<anonymous>)
    at __awaiter (/Users/harshit/code/reproductions/issue-574/index.ts:4:12)
    at main (/Users/harshit/code/reproductions/issue-574/index.ts:42:12)
    at Object.<anonymous> (/Users/harshit/code/reproductions/issue-574/index.ts:69:1) +0ms
(node:24974) UnhandledPromiseRejectionWarning: Error:
Invalid `prisma.foo.findMany()` invocation:

Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(Error { kind: Db, cause: Some(DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState("42P01"), message: "missing FROM-clause entry for table \"_AToB\"", detail: None, hint: None, position: Some(Original(27)), where_: None, schema: None, table: None, column: None, datatype: None, constraint: None, file: Some("parse_relation.c"), line: Some(3240), routine: Some("errorMissingRTE") }) }) })
    at PrismaClientFetcher.request (/Users/harshit/code/reproductions/issue-574/node_modules/@prisma/client/runtime/index.js:1:47490)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
(node:24974) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:24974) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Reproduction repository: https://github.com/harshit-test-org/prisma2-client-574

Not reproducible anymore on latest alpha / beta.


Integrate latest appengine-plugins-core sdk.getVersion fix.

https://github.com/GoogleCloudPlatform/appengine-plugins-core/pull/271

FYI, I just asked Chanseok to push a new 0.2.2 release with this fix when he gets in. Should be at maven central sometime this afternoon.


Update Drush version

Let's stabilize Drush.

@podarok @danylevskyi those changes don't override actual value for jenkins and vagrant.
https://github.com/propeoplemd/cibox/blob/master/core/cibox-project-builder/files/vagrant/box/provisioning/ansible/playbooks/drush.yml#L12
https://github.com/propeoplemd/cibox/blob/master/services/jenkinsbox.yml#L8


Cannot unlock bitlocker partition from explorer

Describe the bug
Some partitions can use bitlocker to encrypt data. Bitlocker partitions can usually be unlocked by opening them in explorer.exe. When you do so, a little window appears asking for the password.
Steps to reproduce

Have a bitlocker partition
use explorer.exe to open and unlock the partition
nothing happens

a window should appear prompting the password

Expected behavior
The unlocking window should appear. It does not.
System information:

Windows version: 1809
Cairo version: <IP_ADDRESS>607 - Pre-release
32-bit or 64-bit: 64
In Cairo Settings > Advanced, is Cairo set as shell?: yes

Additional context
A workaround is to unlock using a terminal and the following command line
manage-bde -unlock F:  -password

I am not sure how to fix that by code. I hope this little issue will serve as help for the time a solution is found.
The window should look like that:

There does seem to be an API for this functionality. Not sure if we can hook the existing functionality and replace it when Cairo is shell.
https://docs.microsoft.com/en-us/windows/win32/secprov/bitlocker-drive-encryption-provider


Added MGE and CGE derived interneuron

Fixes #1096
For def I'm not sure if I should remove 'cortical' at the start (A GABAergic interneuron...) - I think it's important to say that they migrate to the cerebral cortex, but that technically repeats cortical.

There is a tense change in the definitions.

ah that's why it read weird, I kept having this bugging feeling something was not right with it but couldnt quite put a finger on what exactly, thanks for pointing that out - think "has migrated" is right, didn't want to use migrates as it implies it is in the process of doing it.


@OnTextChanged can be optimize if there are two id's used on function.

When we use @OnTextChanged annotation on function with more than two id's as value, then generated code contains separate TextWatcher for each view and passes separately to the views addTextChangedListener. I don't know the solution for this optimization, but if it is possible i will give it a try.

Seems like the solution is to create the listener as a local and then pass it to every view. This optimization would work for any listener.

@JakeWharton can I work on this?

Go for it
On Thu, Sep 13, 2018 at 2:52 PM MONIKA-KUMAR-JETHANI <
<EMAIL_ADDRESS>wrote:

@JakeWharton https://github.com/JakeWharton can I work on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JakeWharton/butterknife/issues/1242#issuecomment-421113567,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEYcSiw9oGcWpUsfCyT7XzwqJ4lM5ks5uaqlsgaJpZM4TLHwZ
.


specified bash language in code block

added bash language specification and instragram hyperlink in markdown

Thank you so much for your help and interest! I'm learning by the minute and the community has been a large help


Moving password-protected zips between 64 & 32 bit platforms

Hi
Love this library, but I’m having problems with password-protected zip files. I can create them and open them fine when building as a 64 bit Mac app. However when trying to open them in the 32 bit iOS simulator I have problems. The zip opens fine, but the password-protected file cannot be extracted and it gives an error:
Error reading ‘file’ in the zipfile

The zip that is created on the 64 bit Mac app also has the same problems when attempting to be opened by 7-zip on Windows:
Data error in encrypted file ‘file’. Wrong password?

There are no problems if I don’t password-protect the zip and in this case they can be passed between 64 bit and 32 bit iOS and Mac systems and also Windows.  Although, curiously, I cannot double-click and extract the zips in the Finder - I get a .cpgz file created instead.
There were many compiler warnings about loss of precision from longs to ints when using XCode 5.1. I can silence the compiler with casts in the code, but the issues above remain whether I add the casts or leave the code as it is.
I am using XCode 5.1 on OS X 10.9.2 and version 0.8.3 of Objective-Zip.
Hope you can help
Thanks

Hi Guys...! Hope you are all be fine...!
I am facing the issue in archiving an audio file password protected.
I am getting wrong password alert, or it prompts again and again when I enter password.
Please see this :   https://cloudup.com/cbncMokTum7
When I zipped the file without password protecting, it works fine, I unzipped the file and it gives me audio file which runs perfectly. But not working when Password protected.
I also tried, @RyouZhang solution, and change the crypt.h file,
Now it looks like this :   https://cloudup.com/cDLQzdUME45
But still no success.
Please help me to resolve this issue, I will be greatly thankful to you...!!!
Thanks...!

Seems to me that this is just a duplicate of #37.
I asked for the latest 'minizip' to be merged into project quite a long time ago...

Hi @Gauleiter , I have integrated the Objective-Zip project through pods.
I did not add the files manually.
Is it fine... ?

@Gauleiter , I also edit these lines, But still not working...!
Please help me to resolve this issue.

I will update the MiniZip sources in the following days, as per @Gauleiter request. I'm not so confident it will fix the issue, though. Encryption has always been a PITA. Let's try and see. Will update this and #37 when done.

@gianlucabertani , Can you please tell me that the wrong password issue is due to the MiniZip resources.
Because I integrated this library through pods. And facing this issue.
Thanks...!

MiniZip is part of the sources of Objective-Zip, it's compiled in. As explained in #37, Objective-Zip is just a wrapper around lower-level libraries that actually do the heavy lifting. Most of the times the source of errors is in those libraries, the wrapper by itself is quite shallow.
I can't know for sure what causes your problem with the password, what I can do is update MiniZip to the latest version (an operation that is long overdue) and add some tests on encryption. It will take some time, though. Please be patient.
If you really are in a hurry, consider alternative libraries, such as:

https://github.com/ZipArchive/ZipArchive
https://github.com/marmelroy/Zip
https://github.com/pixelglow/ZipZap

Version 1.0.4 is out now, with MiniZip updated and some tests showing that password encryption works as expected.
Let me know if your issue is fixed.

Perfect! Thank you very much. I'll have a chance to test it only in a few days, will report of the results.


about the hyperreference settings of vctree and motif?

hi, dear sir.
can you update the scripts of vctree and motif?
i just use the same hyperreference settings of transformer with vctree model, but the precision is bad.
so hope you can provide the scripts.

I made the VCTree model the same as Transformer, using the sum of the results of the two classifiers as the final result, I don't know if you haven't changed it here rel_dists = self.rel_compress(visual_rep) + self.ctx_compress(prod_rep) . I provide the log file for your reference
log.txt


Adding Debezium 0.9.2 release announcement

Hey @jpechane, can you review and merge this one? I'll send the Tweet later today. Thanks!

@gunnarmorling Applied, thanks


Application Not Responding

After successfully connecting to the WSUS server and when creating a new application WPP stops responding:

Using version 1.4.2103.13 on Server 2012R2. .NET4 is latest. WSUS Version 6.3.9600.18694

Hi, can you get the log file here: %LocalAppData%\Temp\WPP-GUI.log
And paste it in here.

Hi @DCourtel Thanks for replying. I don't have such log in the mentioned folder. However I do have the following logs but those contain sensitive data:

How do I obtain WPP-GUI.log?

Delete all WPP logs. Start WPP, try to publish an update, and when it hangs, send the log file.

I deleted all WPP logs and all of a sudden when I press CTRL+U a new window appears instead of a not responding application. No clue why deleting the logs results into a working application though.
So uhm, it seems the problem got resolved...

Glad to hear that your issue is solved.


Bad Performance

I am testing python interpreter performance against codon. The scenario is sending a message via the posix_ipc module (defined as a library). I am using the Posix message Queus. The test is like sending a message to a server and then receiving the response. The server just sends back the message that is received. I do this 1000,000 times and measure the time of 1000.000 send-receive! The execution time of the compiled codon (release build) program is always worse than the python program.
I will be happy if someone can help me through this.

Hi @sinainnet -- can you please share more details and (ideally) an example to reproduce the issue? If you're using a Python library like posix_ipc then Codon will just invoke it through CPython, so the performance shouldn't be any different than calling it in Python as usual.

The codon code is like below:
from python import argparse
from python import os
from python import datetime
from python import numpy as np
from python import time
from python import threading
from python import posix_ipc
import sys
import python

@export
def processing(chunk_size: int, number_of_samples: int, verbose: bool):

    if verbose:
        print("\nCodon compiler: ")
        print f"\tChunk size: {chunk_size} Bytes"
        print f"\tSamples: {number_of_samples}"

    try:
        mq = posix_ipc.MessageQueue("/miji", flags=posix_ipc.O_CREAT)

        data = np.arange(chunk_size, dtype=np.uint8)

        start = time.time()
        for i in range(number_of_samples):
            mq.send(data)
            mq.receive()

        end = time.time()

        duration = (end - start) * 1e3
        print duration

        mq.close()

    except Exception as e:
        print("Exception encountered:", e)

And python code like below:
import argparse
import os
import datetime
import numpy as np
import time
import threading
import posix_ipc

def main(chunk_size, number_of_samples, verbose):

    if verbose:
        print("\nPython interpreter: ")
        print("\tChunk size: {} Bytes".format(chunk_size))
        print("\tNumber of samples: {}".format(number_of_samples))

    try:
        mq = posix_ipc.MessageQueue("/miji", flags=posix_ipc.O_CREAT)

        data = np.arange(chunk_size, dtype=np.uint8)

        start = time.time()
        for i in range(number_of_samples):
            mq.send(data)
            mq.receive()
        end = time.time()

        duration = (end - start) * 1e3  # ms
        print(duration)

        mq.close()

    except Exception as e:
        print("Exception encountered:", e)

@sinainnet There is a similar case in Discussions. I believe it may be helpful: https://github.com/exaloop/codon/discussions/375#discussioncomment-5830841

@sinainnet There is a similar case in Discussions. I believe it may be helpful: #375 (comment)

@sinainnet There is a similar case in Discussions. I believe it may be helpful: #375 (comment)

In this thread, there is an open problem of using C codes in the codon. Actually, I had a plan to replace python 'poxic_ipc' with an equivalent c (or C++) implementation of MQ. The documents (https://docs.exaloop.io/codon/interoperability/cpp) are not quite helpful in this case. Is there any place that I can use to utilize the MQ that Implemented in C (and C++) in the codon?

Hi @sinainnet
Here you basically import everything from Python--- that will never be faster than Python version. You would only benefit from Codon if some performance-sensitive routines are reimplemented in Codon.

Closing this for now as this is expected (because everything is done via Python).


Make this repo into a chart repo

In our first "hello helm" exercise, it would be fitting to have a "welcome to Eficode" image and chart.
We could use this repo as a helm chart if needed.
https://medium.com/@mattiaperi/create-a-public-helm-chart-repository-with-github-pages-49b180dbb417

Duplicate of #17


How to use a private registry by local DNS name?

Version (k3OS / kernel)
k3os version v0.11.1
5.4.0-48-generic #52 SMP Sat Sep 26 08:27:15 UTC 2020
Architecture
x86_64
Describe the bug
I originally reported this issue in the k3s repo (https://github.com/k3s-io/k3s/issues/1581), but it seems to fit better here. In short, I want to deploy images that come from a registry running on the same cluster. I can get it to work using the IP address of the registry, but not using an internal domain name (*.svc.cluster.local).
To Reproduce
The linked issue lists the steps I took in detail; I'll summarise here:

Deploy a registry to the cluster (no need for ingress, TLS or authentication).
Use port forwarding to push an image to the registry.
Configure k3s to use the private registry via its internal domain name.
Create a pod using an image from the registry.

Expected behavior
The pod comes online after pulling the image from the registry.
Actual behavior
The pod goes into ErrImagePull state, as k3s cannot resolve the domain name of the registry, with a warning message like:

Failed to pull image "image-registry-2.duncanvr/test-image:latest": rpc error: code = Unknown desc = failed to pull and unpack image "image-registry-2.duncanvr/test-image:latest": failed to resolve reference "image-registry-2.duncanvr/test-image:latest": failed to do request: Head http://image-registry.containers.svc.cluster.local:5000/v2/test-image/manifests/latest: dial tcp: lookup image-registry.containers.svc.cluster.local: no such host

Additional context

As mentioned, this has already been reported in the k3s repo. The conclusion was that if the host cannot resolve a domain name, then neither can containerd and k3s. I therefore believe this is something that should be solved in (the configuration of) k3OS.
This seems similar to https://github.com/rancher/k3os/issues/680, but is actually the inverted case. That issue is about (not) being able to resolve domain names in pods that can be resolved on the host -- whereas this is about (not) being able to resolve domain names on the host that can be resolved in pods.

In the linked issue I've also described my attempts to make k3OS use kube-dns for resolving domain names. This has been partially successful, i.e. working with many warnings. My main question is how to get that to work.

I don't believe this should be marked as a bug per se. I have no idea how to remove that label though; perhaps I don't have the rights to do so.

@DuncanvR I imagine that you would need an /etc/hosts entry on the k3s host for your registry (running in k3s in containerd) because containerd is what is talking to the registry which is not configured to leverage the coredns (running in k3s in containerd) for the cluster. You might be tempted to configure an /etc/resolve.conf entry to point to your coredns but that would be a mistake I would think as the next time the system reboots or coredns pod is restarted it will be thrown into a self-referential resolver loop.

A more sophisticated solution might be scan your cluster's coredns for SRV records and export those to an network-local resolver combined with ingress to forward requests to the services in your cluster.

Thanks @dweomer. I had already tried adding the cluster's DNS server to /etc/resolve.conf, but indeed saw warnings about resolver loops. Also, I had to specify the IP address of the coredns pod there, which isn't necessarily stable. I'm afraid the alternatives you mentioned would still require the same -- because as I understand it, in order to scan your cluster's coredns for SRV records, I'd still need to know how to reach the coredns pod, right?
In the end I'd love to find a solution that's a little more robust, i.e. not dependent on me entering IP addresses.
I guess the only place where those pod addresses (either coredns, or in my case the image registry) are known, is inside Kubernetes. A job could do something with them, but probably doesn't have rights to change anything on the node(s). The control plane might be a better place for that. But I'm starting to feel a little out of my depth here. Do you have any pointers?


Enter button destroys entry

User is entering Reference Code

User hits the Enter button on his keyboard. As you know, data entry professionals all hit the Enter button upon finishing each data entry.
Next thing you know, all is lost. We see "Search"

User hits the Enter button on his keyboard. As you know, data entry professionals all hit the Enter button upon finishing each data entry.

I don't think the data is lost.. It's saved and the user is returned to browse mode.
Can you confirm?

Yes, if the user decided to select that feature from the map again, he will find painstakingly typed in data still there. But 99% of the other users will not know why we are now looking at something irrelevant and give up.

We train users in the walkthrough that it's ok to press enter and that their edits are not lost.  iD has worked this way since the beginning, and I'm not changing it now.


Run async side effects before url change

This issue might sound like an anti pattern but the idea is only to implement standard browser behaviour.
Generally, in a non SPA app, when user clicks an A tag the browser waits for the response in the background and does not update the url before response arrives (or fails after timeout). In SPA apps the general pattern is to update the url and then rerender, fetch data etc. based on the url. While this is ok most of the time it creates new problems like

If your SPA triggers on url change. You will probably render some sort of loading state directly on url change, this is most of the time annoying and unncessary
Tracking (and other tools) that listens to url change will trigger before data has arrived. For example google analytics

Generally I'm looking for a solution to run a side effect (like fetching data) before transition is made. This way we can implement something similar to browser behaviour and ensure that needed data is in place when actual url change is made.
Of course you could implement this in your app (like react) but I think that history is a good place for such a logic, mostly because it is already standard behaviour in browsers
I would be happy to contribute to this feature if we find it meaningful

I believe that this would require a major re-implementation of the library. I did a similar thing with hickory and it works nicely, but comes with caveats. The complication is because if the navigation isn't instant, then it needs to be cancellable (the user may click another link while the current one's async actions are running).

This is a great feature to add in v6, I think. It's tricky though because we don't always have control of when the new URL appears in the address bar. In the case of a PUSH or REPLACE we do (we are changing the URL), but not on a POP (the URL has already changed).

can't we use the transition manager instance for that?

In a previous issue, it was pointed out that a pre-configured custom history object could be passed to a Router component, rather than using a BrowserRouter component.
Here's a way you might be able to use this to accomplish what you want, using the current version of React Router.

Wrap the original history object such that you intercept calls to push.
Pass the wrapped history object to Router, and use Router instead of BrowserRouter.
When push is called, store the destination URL in a "transitioningTo" variable somewhere.
Perform any async requests.  You probably want to show a spinner or otherwise tell the user to wait while this is happening.
Call the original, wrapped history.push when the async requests are completed.

This doesn't solve history.pop or page refreshes, so you would still need to have a page that looks reasonable if the user navigates to it directly before the async requests are completed.


TET: Append trailing slash to avoid CSRF issue

Description :sparkles:
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #914 (64b8d78) into develop (76757d6) will decrease coverage by 63.10%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           develop    #914       +/-   ##
===========================================
- Coverage    63.10%   0.00%   -63.11%
===========================================
  Files          862      64      -798
  Lines        23211    1002    -22209
  Branches      2315     157     -2158
===========================================
- Hits         14648       0    -14648
+ Misses        8172     965     -7207
+ Partials       391      37      -354

Impacted Files
Coverage Δ

...tet/admin/src/hooks/backend/useDeleteTetPosting.ts
0.00% <0.00%> (ø)

...tet/admin/src/hooks/backend/useUpsertTetPosting.ts
0.00% <0.00%> (ø)

...tend/tet/admin/src/components/editor/DateInput.tsx
0.00% <0.00%> (ø)

...end/tet/admin/src/backend-api/linked-events-api.ts
0.00% <0.00%> (ø)

...omponents/editor/classification/Classification.tsx
0.00% <0.00%> (ø)

...omponents/editor/postingDetails/PostingDetails.tsx
0.00% <0.00%> (ø)

frontend/kesaseteli/youth/src/pages/404.tsx

...components/application/companyInfo/CompanyInfo.tsx

...orms/application/deMinimisAid/DeMinimisAidForm.tsx

...er-tests/components/suomiFiValtuutus.components.ts

... and 794 more

Continue to review full report at Codecov.

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


Azure Bicep Outputs Are Not Parsed

When using GitHub Actions to deploy infrastructure in Azure, specifically via Azure Bicep templates, even though the template may have outputs defined, this is not parsed correctly and therefore no information is returned to the console.

Sample Bicep Code
param accountPrefix string = 'test'
param location string = 'eastus'
param utc string = utcNow()

var storageAccountName_var = '${replace(replace(replace(accountPrefix, '.', ''), '_', ''), '-', '')}ghedata${utc}'
var storageAccountType = 'Premium_LRS'

resource storageAccount 'Microsoft.Storage/storageAccounts@2021-01-01' = {
  name: toLower(take(storageAccountName_var, 24))
  location: location
  sku: {
    name: storageAccountType
  }
  kind: 'StorageV2'
}

output storageAccount_Name string = storageAccount.name
output storageAccount_Location string = storageAccount.location
output storageAccount_SKUName string = storageAccount.sku.name
output storageAccount_Kind string = storageAccount.kind

Sample GitHub Actions Workflow
name: Deploy GHES using Azure Bicep

on:
  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:
    inputs:
      gh_handle:
        description: 'What is your GitHub handle?'
        required: true
      accountPrefix:
        description: 'Unique prefix for your Storage Account and VM name. Must be all lower case letters or numbers. No spaces or special characters.'
        required: true
      location:
        description: "What Azure region to deploy to (ie. 'eastus', 'canadacentral')"
        default: 'eastus'
        required: true
      ghes_version:
        description: "What version of GHES do you need (ie. 2.22.19, 3.0.13, 3.1.5)?"
        default: 'latest'
        required: true

jobs:
  create_resource_group:
    name: Create Resource Group
    runs-on: ubuntu-latest
    steps:
      # Log into Azure
      - name: Log into Azure
        uses: azure/login@v1
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      - name: Create Resource Group
        run:
          az group create --name 'GHES-${{ github.event.inputs.gh_handle }}' --location ${{ github.event.inputs.location }} --tags [Owner[= ${{ github.event.inputs.gh_handle }} ]]

  deploy_ghes:
    name: Deploy GHES
    runs-on: ubuntu-latest
    needs: [create_resource_group]
    steps:
      # Checkout code
      - name: Checkout code
        uses: actions/checkout@main

      # Log into Azure
      - name: Log into Azure
        uses: azure/login@v1
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      # Deploy Bicep file
      - name: Deploy GHES
        uses: azure/arm-deploy@v1
        with:
          subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION }}
          resourceGroupName: GHES-${{ github.event.inputs.gh_handle }}
          template: ./Bicep/main.bicep
          parameters: ./Bicep/bicep.parameters.json accountPrefix=${{ github.event.inputs.accountPrefix }} ghesversion=${{ github.event.inputs.ghes_version }}
          failOnStdErr: false

@AErmie Raised PR to support these logs. https://github.com/Azure/arm-deploy/pull/79
If the issue needs a quick fix then enable debug logs in the repository. Create a new repo secret with ACTIONS_STEP_DEBUG  set to true
https://docs.github.com/en/actions/managing-workflow-runs/enabling-debug-logging#enabling-step-debug-logging

Hi @AErmie, can you try rerunning the workflow and see what outputs are you getting as we tried running the above template and the outputs were parsed correctly for us?
Parsing outputs...

::set-output name=storageAccount_Kind::StorageV2

::set-output name=storageAccount_Location::eastasia

::set-output name=storageAccount_Name::deepak21

::set-output name=storageAccount_SKUName::Premium_LRS

If the error still continues set this environment secret ACTIONS_STEP_DEBUG to true and confirm if the debug logs are correct.

Hey @t-dedah, when I have ACTIONS_STEP_DEBUG enabled, I see that it does parse the outputs (and I can subsequently use those outputs in another step).

But what I was referring to, are the outputs from the Bicep template. Similar to Terraform, if you have outputs, those will be written to the console as part of the template execution.
When the GitHub Action says "parsing outputs" I (by default) assume it's the outputs defined in the template, and expect it to be visible in the console (without DEBUG enabled).

@AErmie Can yo please show me what outputs are you expecting?
The purple logs are from DEBUG whereas the white logs are your normal logs so everything after parsing outputs... is consoled twice.

Hey @t-dedah, sorry if I wasn't clear. I'm referring to the outputs in the Bicep file...
output storageAccount_Name string = storageAccount.name
output storageAccount_Location string = storageAccount.location
output storageAccount_SKUName string = storageAccount.sku.name
output storageAccount_Kind string = storageAccount.kind

My expectation is similar to what Terraform produces when you run terraform apply, where it will write out to the console the actual values of the resources.
When you have debug turned off, you don't actually see any of the outputs. So, unless you know it's still actually there under the covers, a user will think it's not.

Hi @AErmie , there was some misunderstanding, the above output is an expected behaviour. We are not printing any output as part of parsing process. If the outputs needs to be printed then we should explicitly do that in next step using this https://github.com/Azure/arm-deploy#another-example-on-how-to-use-this-action-to-get-the-output-of-arm-template
      - name: Deploy GHES
        id: deploy_ghes
        uses: azure/arm-deploy@v1
        with:
          subscriptionId: ${{ secrets.AZURE_SUBSCRIPTION }}
          resourceGroupName: GHES-${{ github.event.inputs.gh_handle }}
          template: ./Bicep/main.bicep
          parameters: ./Bicep/bicep.parameters.json accountPrefix=${{ github.event.inputs.accountPrefix }} ghesversion=${{ github.event.inputs.ghes_version }}
          failOnStdErr: false

- run: echo ${{ steps.deploy_ghes.outputs.storageAccount_Name }}

This behaviour was implemented in order to save us from printing secrets by mistake.

OK thanks @t-dedah, perhaps we can update the Bicep and GitHub Actions documentation to make that more clear (especially for customers coming over from Terraform, and expecting to see the outputs).

@AErmie Ill update the readme to explicitly call this out at the top itself.
So should I go ahead and close this issue?

@t-dedah, yes since this behaviour is "by design"


Q2model

Q2 Model added, formatting needed, non-stats wording needed [We can work on it after tomorrow's crazy dues] DUE DATE for this report for us changes to SUNDAY NOPE Due Friday, false info

please kindly help with PR @andrewkroening @echodpp @poojakabber7

Closing due to merge issues


[WIP] Fixed passing arguments that contain quotes in shell script

Codecov Report

Merging #6345 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master   #6345      +/-   ##
===========================================
+ Coverage     83.27%   83.3%   +0.03%
- Complexity    12816   12817       +1
===========================================
  Files          1480    1480
  Lines         48500   48500
  Branches       5908    5908
===========================================
+ Hits          40389   40404      +15
+ Misses         5366    5351      -15
  Partials       2745    2745

Impacted Files
Coverage Δ
Complexity Δ

...xecutor/transport/TransportSchemaUpdateAction.java
83.87% <0%> (-4.84%)
13% <0%> (-2%)

...rc/main/java/io/crate/analyze/symbol/Function.java
94.11% <0%> (-2.95%)
17% <0%> (-1%)

...ql/src/main/java/io/crate/metadata/TableIdent.java
87.03% <0%> (-1.86%)
28% <0%> (-1%)

.../collectors/OrderedLuceneBatchIteratorFactory.java
83.6% <0%> (-1.64%)
5% <0%> (ø)

...te/operation/scalar/cast/CastFunctionResolver.java
96.05% <0%> (-1.32%)
10% <0%> (-1%)

...er/src/main/java/io/crate/sql/tree/AstVisitor.java
30% <0%> (-0.77%)
39% <0%> (-1%)

.../crate/executor/transport/task/UpsertByIdTask.java
89.31% <0%> (-0.77%)
38% <0%> (-1%)

...executor/transport/TransportShardUpsertAction.java
86.09% <0%> (-0.34%)
77% <0%> (-1%)

blob/src/main/java/io/crate/blob/DigestBlob.java
77.44% <0%> (+0.75%)
31% <0%> (+1%)
:arrow_up:

...ecutor/transport/SnapshotRestoreDDLDispatcher.java
88.09% <0%> (+0.79%)
13% <0%> (ø)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


Optional onLongPressed function added

New onLongPressed property to let do other things when the longpress happened like for example add a HapticFeedback

Hi, I'm new to Flutter.
I'm using FocusedMenuHolder() but I can't find onLongPressed(){}, but only onPressed(){}.
I want to use  onLongPressed for HapticFeedback!
Much appreciate if you teach me. thank you!