Progress indication for commands like create and Long Running Operations

Didn't see an existing issue for this. Aplogies if so.
When issuing a command, such as az vm create, you get no indication of progress. The CLI just sits until the entire operation has completed. Looking in the portal, you can see as the storage, then networking, then VM, etc., is created. node.js CLI shows indication by default as each resource is in progress and completed, etc.
az --version
azure-cli (2016.09.05.nightly)

Creating a VM and just waiting for a couple minutes definitely "feels" a little odd, especially after being accustomed to how many other CLIs behave (e.g. doing a Docker build, performing a Git deploy to Heroku and seeing the buildpack process), and expecting some sort of visual indication of progress.

Would providing a better (actually working) --verbose option solve the problem? We have tried really, really (maybe too) hard to follow the "silence is golden, only generate error/non "return value" output for unexpected events/errors.

Taking the VM creation example, since that's probably a pretty well used command, there are a number of other resources it's validating or creating. So it would nice to at least see, "yep, storage found", "yep, vnet and nic found", "now creating VM", etc. Especially since you're waiting on response from the underlying APIs each time. Maybe this goes under a more readable output from --verbose.
If I'm just creating a new VNet, there's probably not a lot I'm waiting on, and it should be a pretty quick operation. I don't think anything needs to be displayed until the operation has completed. Same with creating a new storage account, or a new public IP address, etc.
But on those longer-running operations, like creating a VM or deploying from a template, it would be nice to get an indication rather than nothing really being displayed for minutes until the whole operation has completed. Then you can at least see, "OK, all the supporting resources are in place, now it's actually churning on spinning up the new VM"
Actually, on the template deployment, bonus points if that then notes the deployment has been handed off, and is in progress - the existing node CLI returns you to the prompt within a few seconds of starting a new deployment (azure group create --template-uri azuredeploy.json) and says Provisioning State: Succeeded when really that's acknowledging the platform accepted the deployment task, not having finished creating all the actual resources within the template :)
Double bonus points for being able to then track that deployment progress. But we're getting outside the scope of this issue and is handled elsewhere, really!

I am interested in this for CI scenarios.
I can't use --verbose there because a goal is to get this to be something I can expose publicly and there are too many secrets in the verbose output right now for me to use that as a status indicator.
Particularly for an ARM template deployment that can take 1 minutes to 20 minutes, some status would be nice (if the user asks for it explicitly... I like the silence-on-success pattern).
Something like a summary output that refereshed, or maybe just appended the resource name from the ARM template as soon as it moves into Success provisioning state?

Silence is like golfing in the dark. I agree with @colemickens on the --verbose flag for the amount of information.

Particularly for an ARM template deployment that can take 1 minutes to 20 minutes, some status would be nice (if the user asks for it explicitly... I like the silence-on-success pattern).

Some middle ground must be attainable.
Performing {Task} [insert spinner thigy]
Result: Success/Fail/Warning
Message:

Move on to the next task.

#3510 aims to resolve this.


Why not combine HEAD/GET with same path to single line?

The plugin is great!
Why not combine HEAD/GET with same path to single line?
When project has many routes, combine same path to single line can save many space, and more clear.
thanks.

Hello!
First of all, thanks the compliments 😀
It's a very good idea. I think I will introduce it next week.
The only thing is that I won't make enabled by default as I think it might confuse people. But it will be an opt-in option.
You will hear from me soon 🤣

thanks, wait for your message.

I just added the compact option to the plugin which should solve this issue.
See version 2.1.0


Update checkout module

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 32
- Added 223

Complexity increasing per file
==============================
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Request/PrefillInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Client/Client.php  8
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/Creditcard.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/ConsumerAddress.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/CreateReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/Item/ItemDescriptionListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetCaptures.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/CreateAuthorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/VatSummaryCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetAuthorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetCancellations.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Request/Purchase.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderPayer.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Collection/Item/OrderItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetVerification.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Collection/OrderItemsCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Resource/Request/Payment.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetTransaction.php  1
- vendors/swedbank-pay-core-library/tests/TestCase.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/GetSales.php  1
- vendors/swedbank-pay-sdk-php/tests/PurchaseTest.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Api/Response.php  4
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/TransactionResource.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Request/CreateApprovedLegalAddress.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetAuthorizations.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Request/Authorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Response.php  5
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Request/GetPaymentorder.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Resource/Collection/Item/OperationsItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Client/ClientVersion.php  7
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderCreditcard.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Request/Purchase.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Api/Transaction.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Resource/Collection/Item/SaleListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetTransactions.php  1
- vendors/swedbank-pay-sdk-php/tests/CardPaymentTest.php  1
- vendors/swedbank-pay-sdk-php/tests/ConsumerTest.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Request/Capture.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentPurchaseObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/GetTransaction.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetReversals.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/ItemDescriptionListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/TransactionListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Request/InitiateConsumerSession.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/CreateCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/TransactionResponse.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/GetReversals.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/Invoice.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/Payment.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Request/Url.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/CreateReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Request/CreateInvoice.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Resource/Request/PaymentPayeeInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentVerifyObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Request/Verify.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetReversals.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Request/TransactionCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderMetadata.php  1
- includes/class-wc-swedbank-pay-transactions.php  4
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Request/GetShippingDetails.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Request/Recur.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Collection/PaymentorderItemsCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/Item/TransactionListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/TransactionCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Resource/Request.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Request/PayeeInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetCancellation.php  1
- vendors/swedbank-pay-sdk-php/tests/InvoicePaymentTest.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetTransactions.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetAuthorization.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Order/PayeeInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/Response/GetBillingDetails.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/CreateAuthorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/CreateCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Request/Purchase.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Request/GetPayment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Client.php  9
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/Reversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Request/GetItemDescriptions.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/VerificationsObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Resource/Request/Payment.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Response.php  6
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Client/Resource/Client.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Collection/Item/VatSummaryItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetCaptures.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/CreateCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/CreateSale.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Request/Transfer.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetCaptures.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/CancellationObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/Addressee.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/Consumer.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/Capture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Resource/Collection/SaleListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/Item/VatSummaryItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/ProblemsCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/Response/GetShippingDetails.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Collection/Item/PriceItem.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Data.php  6
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/CreateAuthorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Resource/Request/PaymentSwish.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/CreateReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/InvoicePaymentObject.php  1
- vendors/swedbank-pay-sdk-php/tests/PathResolverTest.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetReversals.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderUrl.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/CreateCancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetCancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetTransaction.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/SalesObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Request/TransactionObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Request/TransactionObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Request/TransactionReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetAuthorizations.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetAuthorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentPurchaseCreditcard.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Framework/AbstractSimpleDataObject.php  7
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/ConsumerNationalIdentifier.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Collection/PaymentListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Resource/Request/TransactionFinalize.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Request/Transaction.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Resource/Response/Sale.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetTransaction.php  1
- includes/class-wc-swedbank-plugin.php  8
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Core.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/RemovePaymentToken.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetCancellations.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentVerifyCreditcard.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Response/GetCurrentPayment.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Api/Verification.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/CapturesObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Request/Purchase.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentVerify.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Request/Payout.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/CreateReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/Response/InitiateConsumerSession.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/GetSale.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Order/RiskIndicator.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/OrderItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/TransactionCancel.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Response/Payment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Framework/DataObjectHelper.php  9
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/VerificationObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Collection/Item/PaymentorderItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Request.php  6
- vendors/swedbank-pay-sdk-php/tests/PaymentsRequestTest.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Collection/CaptureListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Client/Exception.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Request/Consumer.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/Finalize.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/Problem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/AuthorizationObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Request/Transaction.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/ResourceFactory.php  10
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentRecur.php  1
- vendors/swedbank-pay-core-library/tests/Adapter.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/CreateCancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Resource/Collection/OperationsCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Request/GetPayment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Request/GetLegalAddress.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Resource/Request/InitiateConsumerSession.php  1
- vendors/swedbank-pay-sdk-php/tests/ExceptionTest.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetCancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/AuthorizationsObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Request/GetPayments.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/CaptureObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Collection/ItemDescriptionCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Resource/Request/TransactionAuthorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/AddresseeObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderCampaignInvoice.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Order.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Request/Cancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Response/PaymentObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Collection/Item/CaptureListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentPayoutObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetCancellations.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Framework/DataObjectCollection.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/CancellationsObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/TransactionObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/ReversalObject.php  1
- vendors/swedbank-pay-sdk-php/tests/TestCase.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Collection/PricesCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Request/RemovePaymentToken.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Resource/Collection/Item/AuthorizationListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Consumer/Request/GetBillingDetails.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/TransactionsObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Collection/Item/AuthorizationListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Request/TransactionCancel.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Request/Verify.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Exception.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Request/Authorization.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Configuration.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Resource/Request/Payment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Resource/Request/TransactionVerification.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Response/Payments.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetVerifications.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Resource/Request/VippsPaymentObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentUrl.php  1
- includes/class-wc-adapter.php  20
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Collection/Item/ProblemsItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Resource/Collection/AuthorizationListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Collection/Item/DescriptionItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/TransactionReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/PathResolver.php  4
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Request/GetCurrentPayment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/PaymentPayeeInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentPurchase.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/Transaction.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/SaleObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Collection/VatSummaryCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/GetReversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/GetTransactions.php  1
- vendors/swedbank-pay-sdk-php/tests/VippsPaymentTest.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Order/PlatformUrls.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Response/GetPayments.php  1
- includes/class-wc-background-swedbank-pay-queue.php  12
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetCapture.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Customer.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Api/Authorization.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Resource/Request/PaymentPrefillInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/GetAuthorizations.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Request/Cancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderInvoice.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Collection/Item/PaymentListItem.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Request/GetPayment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Resource/Request/SwishPaymentObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/PaymentorderSwish.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Collection/AuthorizationListCollection.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/ReversalsObject.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Framework/AbstractDataTransferObject.php  3
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentPayeeInfo.php  1
- assets/js/admin.js  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Transaction/Request/CreateCancellation.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Request/GetCapture.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Payment/Transaction/Resource/Response/Transactions.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Request/UpdateOrder.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Invoice/Transaction/Resource/Request/Reversal.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Vipps/Resource/Request/PaymentPayeeInfo.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Swish/Transaction/Request/GetTransactions.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Resource/Request/Paymentorder.php  2
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Paymentorder/Transaction/Resource/Response/Cancellation.php  1
- vendors/swedbank-pay-sdk-php/tests/SwishPaymentTest.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Request/GetPayment.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Transaction/Request/CreateVerification.php  1
- vendors/swedbank-pay-sdk-php/src/SwedbankPay/Api/Service/Creditcard/Resource/Request/PaymentRecurObject.php  1

Clones added
============
- vendors/swedbank-pay-sdk-php/tests/InvoicePaymentTest.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Library/Methods/Card.php  2
- includes/class-wc-gateway-swedbank-pay-checkout.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Library/Methods/Swish.php  1
- vendors/swedbank-pay-core-library/tests/bootstrap.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Library/OrderAction.php  2
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Library/Methods/Vipps.php  1
- includes/class-wc-adapter.php  1
- vendors/swedbank-pay-sdk-php/tests/VippsPaymentTest.php  1
- vendors/swedbank-pay-core-library/src/SwedbankPay/Core/Library/Methods/Invoice.php  3
- vendors/swedbank-pay-sdk-php/tests/bootstrap.php  1
- assets/js/admin.js  4

See the complete overview on Codacy

So, this is the implementation of the new core plugin? I'm a bit overwhelmed by the amount of code added to this repository. I would think code would be removed, not added. Also, shouldn't we publish the core plugin on Packagist before we start using it?

You're right. Would be good to place the core library in the packagist. But wordpress doesn't use composer at the moment because they are old school developers. I think we can try use Github Actions to generate zip's with full code including composer dependencies

You're right. Would be good to place the core library in the packagist. But wordpress doesn't use composer at the moment because they are old school developers. I think we can try use Github Actions to generate zip's with full code including composer dependencies

Yes, let's try that. :+1:


Maintenance: Update Storybook

There is a new version of storybook. Version 6. We are still on 5.

closed by https://github.com/gbif/gbif-web/commit/30807fd400809837d25ac2bbc87bbd5b3cff8db3


Define long in Python 3

long was removed in Python 3 because all int are of infinite precision.  Discovered via #77

long is also handled here. I think the preferred solution would be to use int instead of long, instead of reassigning long.

The linters will get confused by code that does not follow the Python porting best practice use feature detection instead of version detection.


Better error reporting when build fails due to missing environment variables

I believe it was because I didn't have all the necessary environment variables set up that the build failed. The log was not very explanatory:

CumulusCI 2 now throws hopefully more meaningful Python exceptions with more information about what happened.


gameboy camera multi image print

The gameboy camera has option to print multiple images at once (Select -> link -> print -> option -> select multiple images) thats allows you to select images, click print, and it will print all of them at once (it transfers one, prints it, transfers second, etc...) until all of them all transfered. but when receiving the image through Web Serial, it imports it as one very long image, not as multiple separate images

Did you print with a margin?
Any other value than 0 should create a separate image?
Also, which exact code did you use, and which Arduino(?) are you using?

yeah it was the margin... it prints correctly with line feed


Moderator sign-in

Summary
Create a specific moderator sign-in (perhaps a specific kind of User ID?), which allows users to access a private page of experiences to be moderated so they can decide if they should be made public or not.
Updates
This is the most basic possible version of moderation for the platform MVP and will certainly be adaptd in Phase 2.

Closing. Moderation implementation will need to be scoped, as it will involved Django's internal authentication system.
It seems promising and a much shorter put than creating a dedicated moderator sign-in.


If there is a suggestions widget driven inline completion along with brackets and the user accepts it by hitting Tab, only the suggestions widget selection is accepted and the inline completion disappears

Does this issue occur when all extensions are disabled?: Yes

Version: 1.64.0-insider (user setup)
Commit: 99305570d885bce929ba8f24d90f2c3ee54c5c2f
Date: 2022-01-03T12:05:41.799Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:
pandas_sample.txt

Convert the .txt file attached to a .py file
Before

After I hit Tab, notnull would be accepted and the (x) would disappear.

I suspect this has something to do with how the diff is calculated when brackets are present/autoclosed.
In Python, when the inline completion contains a paren and when the paren is autoclosed by VS Code, this is the behavior. Notice that first the brackets get matched with the inline completion and THEN the inline completion disappears.

If I delete the closing paren, the inline completion stays and works as expected including the Tab Tab behavior.

However, I don't see the same issue in TypeScript always, for example
The prediction stays even if the bracket is autoclosed by VS Code. What's different here is that there is a semi-colon at the end of the prediction so there is text after the closing bracket.

cc @hediet

Thanks for reporting this!

Notice that first the brackets get matched with the inline completion and THEN the inline completion disappears.

Can you log the requests to your inline completion provider and what it sends back?
Are you sure that when your provider is asked at languages.apply(|) (with position being at |), that the model returns the correct inline suggestion (with correct ranges)?

Steps to Reproduce:

With the intellicode extension (is it already available?) or the copilot extension?

Hi Henning,
I've included the text and range for each of the scenarios below. Scenario 1 and 3 are the same except 1 is in Python and 3 is in Typescript; 1 doesn't work correctly but 3 does. Do these text and range look right to you?
This is with IntelliCode extension.
Scenario 1
In Python, when the inline completion contains a paren and when the paren is autoclosed by VS Code, this is the behavior. Notice that first the brackets get matched with the inline completion and THEN the inline completion disappears.
Cursor position: notNull = languages.apply(|)
Prediction Text: lambda x: x.notnull())
Prediction Range: char 34 - char 56 i.e. ()

Scenario 2
If I delete the closing paren, the inline completion stays and works as expected including the Tab Tab behavior.
Cursor position: notNull = languages.apply(|
Prediction Text: languages.apply(lambda x: x.notnull())
Prediction Range: char 18 - char 56 i.e. languages.apply(

Scenario 3
However, I don't see the same issue in TypeScript always, for example
The prediction stays even if the bracket is autoclosed by VS Code. What's different here is that there is a semi-colon at the end of the prediction so there is text after the closing bracket.
Cursor position:
Prediction Text:  "");
Prediction Range: char 12 - char 16 i.e. ()

Prediction Range: char 34 - char 56 i.e. ()

This I don't full understand. With prediction range you mean the range that is to be replaced?  In that example, you are replacing 22 characters (56 - 34), but () are only two.
I think due to the complexity of this, I can help you better in a quick meeting.

Adding discussions from our meeting here so this issue is reopened by the bot.
The current line is notNull = languages.apply(|), the prediction is lambda x: x.notnull()). The cursor position is Column 35 which translates to position.character=34 I believe.
If the range to replace is set to char 34 - char 35, then the prediction does not show in grey text.
If the range to replace is set to char 34 - char 34, then the prediction shows up but the brackets don't match notNull = languages.apply(lambda x: x.notnull()))` where the grey text is italicized.

Sounds good!


Adding namespaced environment variables to DefinePlugin under REACT_APP_

This enables users to specify custom environment variables under a REACT_APP_* namespace. To verify it works, I ran the start script via:
REACT_APP_TITLE="Env-enabled React" npm start

And changed the
 in src/App.js:

Welcome to {process.env.REACT_APP_TITLE}

Which rendered:

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

This would resolve #102.

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Looks great and I like the prefix choice. Happy to get this in after resolving minor style nitpicks. Thanks for contributing!

Gah, not sure how the 4 spaces got in there. I'll fix and push.

I would appreciate if you could also add a section on this to "how to" list in template/README.md.
It would need to have a disclaimer that this is a new feature since 0.3.0 (you can find similar disclaimers but searching for "0.2.0" in that file).

@gaearon https://github.com/eliperelman/create-react-app/blob/14b659760bcd464ad546cfbff48ca41875b6bffa/template/README.md#adding-custom-environment-variables

Thanks for the feedback! Updates have been made.

Thanks!

Does not work for setting "port" in version "0.5.0", instead of setting port this way, user has to create a .env file and set the port there like:
PORT=80

Does not work for setting "port" in version "0.5.0", instead of setting port this way, user has to create a .env file and set the port there like:

The feature in this PR is only for custom variables. There are a few built-in ones documented here, and they don't need the prefix.


[PSA] Server migration

A quick message to contributors: the Feedback Friends server has just been migrated, and the DNS now points to my personal VM. The dedicated VM will expire on 2016-10-18, until then you can still access it if there's anything you want to backup.
I'll keep the site up for an undetermined time, but unless the situation evolves so that LD37 needs it, or if there's popular demand I don't think it will be enabled/publicized in the future.
Thanks to all contributors, and @ttencate in particular for making the mini-site much better than initially planned! Hopefully FF will be inspire cool social features for the future Ludum Dare site.

And thank you for getting this ball rolling in the first place, and being so open and welcoming towards contributions! Here's to a fruitful collaboration :beers:


Fix gui plot error

Problem: If one created more than one simulation and visualized the first simulation with some new layouts, e.g., 'single figure', the second simulation may crash as the layout is changed.
Solution: We just recover the layout before the default visualization.

Codecov Report

Merging #600 (9db35d8) into master (53827e9) will decrease coverage by 0.05%.
The diff coverage is 75.00%.

:exclamation: Current head 9db35d8 differs from pull request most recent head 85ae3e9. Consider uploading reports for the commit 85ae3e9 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master     #600      +/-   ##
==========================================
- Coverage   91.93%   91.89%   -0.05%
==========================================
  Files          22       22
  Lines        4253     4256       +3
==========================================
+ Hits         3910     3911       +1
- Misses        343      345       +2

Impacted Files
Coverage Δ

hnn_core/gui/_viz_manager.py
88.92% <75.00%> (+0.48%)
:arrow_up:

hnn_core/parallel_backends.py
81.38% <0.00%> (-0.84%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

can you share some screenshot? My memory is failing me ...
I thought a new tab is created for a new simulation? why would it crash then?

Looks like CircleCI passed on this branch. Does this fix the issue with CircleCI timing out on the GUI docs build?

can you share some screenshot? My memory is failing me ...
I thought a new tab is created for a new simulation? why would it crash then?

When creating a new simulation, the GUI uses the previously selected layout to create a default figure. If the user changes the layout, the GUI will crash because it assumes a 1:3 layout, while the new layout might be something like "single figure," which makes subplots impossible.

humm ... why not always use the 1:3 layout by default?

humm ... why not always use the 1:3 layout by default?

previously it was not, but with this PR now it is.

Can you rebase and fix the merge conflicts?

Can you rebase and fix the merge conflicts?

finished

@jasmainak could we merge this now?

Thanks @chenghuzi !
I tacked on the ignore linkcheck as well :wink:

Thanks @chenghuzi ! Sorry my laptop wifi wasn't working yesterday ...


[BUG] Coscheduling will cause an infinite loop in large-scale job scenarios.

What happened:

Create a big job, e.g. the Job has 255 Pods
The job enables the coscheduling.
And the cluster has insufficient resources to satisfied the Job.
Add enough resources into the cluster.
But the job still failed to schedule.

What you expected to happen:
All pods of the job scheduled successfully.
How to reproduce it (as minimally and precisely as possible):
Well...hard to reproduce.
Anything else we need to know?:
Environment:

App version:
Kubernetes version (use kubectl version):
Install details (e.g. helm install args):
Node environment (for koordlet/runtime-proxy issue):

Containerd/Docker version:
OS version:
Kernal version:
Cgroup driver: cgroupfs/systemd

Others:

Solution:

Consider the child cycle in the coscheduling.Less function. The smaller the cycle, the higher the priority.
Remove cycle check.

/assign @buptcozy


Chelsea Manning mirror

There's an issue with the builds/deploys; not related to this PR (apparently the builders upgraded to Trusty and something's wrong). I'll have a look tonight so in the meantime the PR is not visible


Use container name as its hostname

The randomly generated id in hex string is boring,
as we can generate a random name for the container,
why not use it as the hostname?
This is also supporting user specified name.
It is especially meaningful for those tasks which are tagged with hostname, like building linux kernel, got strings in /proc/version like (root@920801690eff), is awful; but with this change, next time when I build kernel inside the container, I can get a better signature in /proc/version like (root@my-building-box) ...
[drc@lab11 docker]$ bin/docker-1.4.1-dev-dirty run -i -t --rm --name 'my-building-box' --entrypoint=/bin/bash dche/fedora
bash-4.3# uname -a
Linux my-building-box 3.19.0-0.rc2.git0.1.build.20141231.el7.x86_64 #1 SMP Wed Dec 31 17:45:19 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
bash-4.3# cat /proc/version
Linux version 3.19.0-0.rc2.git0.1.build.20141231.el7.x86_64 (root@920801690eff) (gcc version 4.8.2 20140120 (Red Hat 4.8.2-16) (GCC) ) #1 SMP Wed Dec 31 17:45:19 UTC 2014

Signed-off-by: Derek Che<EMAIL_ADDRESS>

Hi!
Thanks for the contribution but this has already been discussed at great length here: https://github.com/docker/docker/pull/7787 and https://github.com/docker/docker/pull/8194
I'm going to close this but if those links do not answer your questions for why we don't want this feel free to comment


Update copyright information in each file to Apache 2.0

The licenses in each Dapr repo are transitioning to Apache 2.0. As part of this transition, copyright information at the top of each file needs to be updated from:
// ------------------------------------------------------------
// Copyright (c) Microsoft Corporation and Dapr Contributors.
// Licensed under the MIT License.
// ------------------------------

to
/*
Copyright 2021 The Dapr Authors
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
    http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

@greenie-msft Have created this issue for copyright update in CLI repo ...

Related to https://github.com/dapr/dapr/issues/3972 and #840
//cc @yaron2

closed with #855


UsageMetadata pattern

I'm trying capture the GenerateContentResponse.UsageMetadata using the stream method. I know other providers will send the usage data as a last chunk with no other content. it seems in the gemini case it comes in as part of the first chunk (with empty values) and then as part of the last chunk.. like this:
2024/12/18 14:41:05 &{CachedContentTokenCount:0 CandidatesTokenCount:0 PromptTokenCount:0 TotalTokenCount:0}
2024/12/18 14:41:06 <nil>
2024/12/18 14:41:06 <nil>
2024/12/18 14:41:06 <nil>
2024/12/18 14:41:06 <nil>
2024/12/18 14:41:07 <nil>
2024/12/18 14:41:07 <nil>
2024/12/18 14:41:07 &{CachedContentTokenCount:0 CandidatesTokenCount:227 PromptTokenCount:11 TotalTokenCount:238}

so i end up doing something like this (converted Seq2 to Pull2):
	result, err, cont := s.next()
	if err != nil {
		// handle error
	}

	if !cont {
		// indicate finished
	}

	if result.UsageMetadata != nil && result.UsageMetadata.TotalTokenCount > 0 {
		// log the token usage..
	}

	if len(result.Candidates) > 0 && len(result.Candidates[0].Content.Parts) > 0 {
		// handle response
	}

not awful, but just want to make sure i'm not double counting either the tokens or the number of requests, if this behavior isn't always what i show above.
thanks,
andrew

I think you should use the last UsageMetadata instance.

"send the usage data as a last chunk"

Yes

"with no other content"

No.  See example below: the last chunk data with both usage metadata and content.
{
  "candidates": [
    {
      "content": {
        "role": "model",
        "parts": [
          {
            "text": " scene based on this description!\n\nLet me know if you have any other specific ideas! I can try to adjust the description to match what you're imagining.\n"
          }
        ]
      },
      "finishReason": "STOP"
    }
  ],
  "usageMetadata": {
    "promptTokenCount": 9,
    "candidatesTokenCount": 546,
    "totalTokenCount": 555,
  },
  "modelVersion": "some version",
  "createTime": "2024-12-18T20:36:44.124139Z",
  "responseId": "some id"
}


Ability to constrain values of an Object with auto-inference of  the object keys

Ability to auto-infer object keys with constraining object values

🔍 Search Terms
key inference
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
I'd like to propose the ability to constrain value types without constraining key types. Currently, one can use Record<string, ValueType> to ensure that an object matches a certain shape. However, there are cases when we would like to constrain only values without limiting possible keys values. For example const COLORS = {"pink": "bright", "purple": "dark"}. If we define it with Record<string, string> then we lose information about possible keys, for example keyof typeof COLORS will be string instead of "pink" | "purple". The suggestion is to introduce a way to define an object literal with key auto-inference. For example: const COLORS: Record<infer, string> = {"pink": "bright", "purple": "dark"}; should ensure that the object is defined properly (all values have correct type) and keys are well defined as a union type.
📃 Motivating Example
type ColorDefinition = {r: number, g: number; b: number};

const COLORS: Record<infer, ColorDefinition> = {
    "blue": {r: 0, g: 0, b: 1},
    "dark-blue": {r: 0, g: 0, b: 0.5},
    "red": {r: 1, g: 0, b: 0},
    // This is an error, all object values should match ColorDefinition
    "error": {r: null, g: 0, b: 0}
}

// should resolve to "blue" | "dark-blue" | "red" | "error"
type ColorNames = keyof typeof COLORS

function foo(colors: Record<ColorNames, ColorDefinition>) {}
foo(COLORS);

💻 Use Cases
What do you want to use this for?
This simplifies and condenses code when a developer needs to have a mapping between a string const to a certain set of values.
What shortcomings exist with current approaches?
There are a few possible workarounds at this moment.
First, using an ENUM:
type ColorDefinition = {r: number, g: number; b: number};

enum ColorName {
    BLUE = "blue",
    DARK_BLUE = "dark-blue",
    RED = "red"
}
const COLORS: Record<ColorName, ColorDefinition> = {
    [ColorName.BLUE]: {r: 0, g: 0, b: 1},
    [ColorName.DARK_BLUE]: {r: 0, g: 0, b: 0.5},
    [ColorName.RED]: {r: 1, g: 0, b: 0},
}

function foo(colors: Record<ColorName, ColorDefinition>) {}

Another one is to use a run-time check:
type ColorDefinition = {r: number, g: number; b: number};

type ValidateColors<T> = {
    [K in keyof T]: ColorDefinition;
}

function validateColors<T>(colors: ValidateColors<T>): ValidateColors<T> {
    return colors;
}

const COLORS = validateColors({
    "blue": {r: 0, g: 0, b: 1},
    "dark-blue": {r: 0, g: 0, b: 0.5},
    "red": {r: 1, g: 0, b: 0},
});

type ColorNames = keyof typeof COLORS

function foo(colors: Record<ColorNames, ColorDefinition>) {}

In both cases, it leads to code duplication or extra run-time code. The ability to have leaner code will improve readability and reduce the number of bugs and boilerplate code.

This is another use case for #7481

@RyanCavanaugh It seems like the #7481 feature request looks for an assert-like operator without type narrowing. In this feature request, I am looking for partial type narrowing. You provided a similar example in this comment https://github.com/microsoft/TypeScript/issues/7481#issuecomment-519283504 however, the outcome of that example is that the original record type does not change. In my proposal, I am looking to actually change the type of the original record.
Technically, the effect is the same, I can use both variables (partially narrowed down and "asserted") interchangeably because they have the same "shape", however, it will make type hints, error and intelli-sense more confusing.
PS. I see you were looking for a name for the operator in that Feature Request, can I propose one? const COLORS = { .... } assert extends Record<string, Color>

I don't see a difference here - can you show what you'd expect to work with one, but not the other?

@RyanCavanaugh
Here is an example:
type Color = {r: number, g: number, b: number}

const COLORS_ASSERTED = {
    "blue": {r: 0, g: 0, b: 1},
    "dark-blue": {r: 0, g: 0, b: 0.5},
    "red": {r: 1, g: 0, b: 0},
    "error": {r: 0.4, g: 0, b: 0},
    "light-blue": {r: 0, g: 0, b: 1},
    "light-red": {r: 1, g: 0, b: 0},
    "light-green": {r: 0.4, g: 0, b: 0},
    "dim-blue": {r: 0, g: 0, b: 1},
    "dim-red": {r: 1, g: 0, b: 0},
    "dim-green": {r: 0.4, g: 0, b: 0},
    "cotton-blue": {r: 0, g: 0, b: 1},
    "cotton-red": {r: 1, g: 0, b: 0},
    "cotton-green": {r: 0.4, g: 0, b: 0},
} // assert extends Record<string, Color>

type ColorName = keyof typeof COLORS_ASSERTED;

const COLORS_NARROWED_DOWN: Record<ColorName, Color> = COLORS_ASSERTED;

function customizeColorAsserted(name: keyof typeof COLORS_ASSERTED, color: typeof COLORS_ASSERTED[keyof typeof COLORS_ASSERTED]) {
    COLORS_ASSERTED[name] = color
};
function customizeColorNarrowedDown(name: keyof typeof COLORS_NARROWED_DOWN, color: typeof COLORS_NARROWED_DOWN[keyof typeof COLORS_NARROWED_DOWN]) {
     COLORS_NARROWED_DOWN[name] = color
};

// Ugly error message:
/**
 * The expected type comes from property 'r' which is declared here on type '{ r: number;
 * g: number; b: number; } | { r: number; g: number; b: number; } | { r: number; g: number;
 *  b: number; } | { r: number; g: number; b: number; } | { r: number; g: number; b: number; }
 * | { r: number; g: number; b: number; } | ... 6 more ... | { ...; }'
 */
customizeColorAsserted("red", {r: null, g: 0, b: 0})

// Nicer error message
/**
 * The expected type comes from property 'r' which is declared here on type 'Color'
 */
customizeColorNarrowedDown("red", {r: null, g: 0, b: 0})

As you can see the "Narrowed down" error message is much more user-friendly.

OK, I see what you're doing there.
The workaround you have (which could be collapsed to 1 line) seems very palatable. I don't think there's room in the language for a one-off operator like this - while it's easy to reason about what Record<infer, T> would do, it's not at all obvious what infer in any other position would mean.

@RyanCavanaugh,
Would you consider having some modifications to the Record definition?
/**
 * Construct a type with an inferred set of properties of type T
 */
type InferRecord<T> = {
    [?? something here ??]: T;
};

so it can be used as InferRecord<Color>?

@oleg-slapdash You might be interested in this:
https://kentcdodds.com/blog/how-to-write-a-constrained-identity-function-in-typescript

This looks like a duplicate/subset of https://github.com/microsoft/TypeScript/issues/26242 - if someone can link together would be nice.

Possible additional use example:
I have a moderately large JSON dataset that may need to be modifiable and where entries occasionally need to refer to other entires. I thought I might quickly constrain it by treating the data as a concisely typed const instead of generating a full JSON schema but this would require inferring the keys.
e.g.
const pickyLegos : {[~infer T~]:{stacksOn:T[]}} = {
   brickTypeA:{
      ...
   }
   brickTypeB:{
       stacksOn:[
           'brickTypeA'
       ]
   }
} as const

I understand that 'alternative to JSON schema' is hardly a goal but had it worked it would've been such a pleasant alternative I thought I'd bring it up here. (Disclaimer: I don't know JSON schema well at all but 'learn another thing to type this data' when there's a data typing tool right in my hand is certainly a feeling.)


Disable pause/cancel camera and info only

Is there any way to disable the pause/cancel option for the Apple TV app and just show the camera and I for only? Kids keep trying to cancel prints.

Scheduled for next release (after I release the one I'm wrapping up). Thanks for the idea!

The app will now follow your settings of your phone. If you lock the app from the phone then the Apple TV will disable buttons that impact the print job. I also added new confirmation dialogs that you can control from the app and the Apple TV will follow your iOS configuration.


Gun animations and userdata errors

This error happens in gun fights:
[ERROR] gamemodes/ocrp/gamemode/server/player.lua:642: attempt to compare number with userdata

unknown - gamemodes/ocrp/gamemode/server/player.lua:642

FireBullets - [C]:-1

3. CSShootBullet - gamemodes/ocrp/entities/weapons/weapon_basegun_ocrp/shared.lua:234

 4. unknown - gamemodes/ocrp/entities/weapons/weapon_basegun_ocrp/shared.lua:67

And guns look like this:
http://steamcommunity.com/sharedfiles/filedetails/?id=676519969
Gun in stomach
CSS IS MOUNTED
Also, guns save after death and cannot be traded.

Okay, those errors were an issue with the body armor system, someone must have been wearing it. I haven't ever looked at that before, so it was completely broken.
The guns in the stomach issue is my fault. I uploaded the wrong content pack. I'm currently uploading the newer one and I will update the readme with the proper link.
 You also lose all ammo that is loaded into any gun.
What do you mean by "cannot be traded"? Do you get an error?

No, it just does not appear in the trade menu. No error.


ValueError : bad marshal data (unknown type code)

Have tried to run the script but I just get
ValueError : bad marshal data (unknown type code)

Same


Editable Profile

I should be able to edit my details e.g. change my username or password

Oh found it! Make it accessible from the drop down menu.

I'm curious, what drop down menu are you speaking about? Also, would you suggest how I can make it easier for other users to find the edit user details functionality?

Yes put it on the drop down menu.
Somewhere here


FreeBSD support.

@yurivict We're interested in integrating this work into MaterialX, but we'll first need a signed Contributor License Agreement.  Let us know if you need any assistance with this step.
https://github.com/materialx/MaterialX/blob/main/CONTRIBUTING.md

[...] we'll first need a signed Contributor License Agreement [...]

The agreement was signed.


Bug when trying to set dataset to the result returned by promise

I can successfully generate with predefined data. However when I try to dynamically add new dataset returned by the result of http.get the following error:
angular.js:13236 TypeError: Cannot read property 'values' of undefined.
this is my service:
  getValveChartData(type, trim, size, diameter_unit){
     return this.http.get("http://localhost:5685/api/values/getValveChart?type="+type+"&size="+size+"&trim="+trim+"&diameter_unit="+diameter_unit).then(result => result.data );
  }

In my controller:
    this.calculator.getValveChartData()
      .then(javab => {
        this.data = {
          dataset2: result
        };
};

If I replace result with some valid array it will generate the chart but I don't know why the result will launch that error.
Thanks

Hi @aligit
can you check the result object if it actually contains something? Maybe you could even add an if-statement to only set dataset2 if result exists.
this.calculator.getValveChartData()
      .then(javab => {
        console.log(result);
        this.data = {
          dataset2: result
        };

Can you show your other options as well? Maybe you defined dataset2 already before it is loaded.
Best,
Christoph

Hi @chaosmail
Thanks for your reply. the result is an array of object:
{x_cv:100,y_opening:100.46}.
I only defined dataset2 in "options" like so:
this.options = {
series: [
{
axis: "y",
dataset: "dataset0",
key: "y_opening",
label: 'Actual curve',
color: "#1f77b4",
type: ['line', 'dot'],
id: 'mySeries0'
},
{
axis: "y",
dataset: "dataset1",
key: "y_opening",
label: 'Activity range',
color: "hsla(88, 48%, 48%, 1)",
type: ['line', 'dot','area'],
id: 'mySeries1'
},
{
axis: "y",
dataset: "dataset2",
key: "y_opening",
label: 'curve',
color: "hsla(88, 48%, 48%, 1)",
type: ['line', 'dot','area'],
id: 'mySeries2'
}
],
axes: {x: {key: "x_cv"}}
};
That's very weird

You are already defining dataset2 in the option, when the dataset is (most likely) not available (in the beginning). When you define your dataset, just init dataset3:
this.data = {
    ...
    'dataset3': []
}

Let me know if this helps

Thanks @chaosmail  didn't help. Still getting the same error

could you share also the part where you define the dataset and the HTML snippet where you bind it?

Yes sure

Opening Curve

            <linechart data="vm.data" options="vm.options"></linechart>

First definition in the constructor:
    this.data = { 'dataset0': [], 'dataset1': [], 'dataset2': []};

    this.default_series = [ this.chartoption.series(0, ['line', 'dot'],"#0067B2", 'Actual curve'),
        this.chartoption.series(1, ['line', 'dot','area'],"#0067B2", 'Activity range')
    ];
    this.series = this.default_series;
    this.default_axes = {x: {key: "x_cv"}};
    this.options = {
      series: this.series,
      axes: this.default_axes
    };

Then the first time the data is generated(which works fine too)
    this.calculator.getResults(...)
      .then(result => {
        this.datasets = [];
        this.datasets.push(result.chart_dataset_actual_curve);
        this.datasets.push(result.chart_dataset_activity_range);
        this.data = {
          'dataset0': this.datasets[0],
          'dataset1': this.datasets[1]
        };
    });

And here is the last part where I try to add new dataset:
    this.calculator.getValveChartData()
      .then(javab => {
        debugger;
        this.data = {
          dataset2: javab
        };
        const index = this.series.length;
        const datasetname = "dataset"+index;
        this.options.series.push(this.chartoption.series(index, ['line', 'dot'],"", 'curve'));
    });
  }

Thanks

Dear @chaosmail ,
The problem was due to a wrong series objects and setting data before the options.
The problem was solved. Thanks so much for your help

Great, I am glad it is working for you!


Add pawn-structure correction history.

STC & LTC, courtesy of plutie:
Results of corrhist vs base (10+0.1, 1t, 16MB, UHO_Lichess_4852_v1.epd):
Elo: 19.03 +/- 8.69, nElo: 28.25 +/- 12.88
LOS: 100.00 %, DrawRatio: 41.06 %, PairsRatio: 1.36
Games: 2796, Wins: 835, Losses: 682, Draws: 1279, Points: 1474.5 (52.74 %)
Ptnml(0-2): [63, 286, 574, 385, 90]
LLR: 2.95 (-2.94, 2.94) [0.00, 5.00]

Results of corrhist vs base (60+0.6, 1t, 64MB, UHO_Lichess_4852_v1.epd):
Elo: 30.29 +/- 10.34, nElo: 51.47 +/- 17.48
LOS: 100.00 %, DrawRatio: 49.01 %, PairsRatio: 1.78
Games: 1518, Wins: 427, Losses: 295, Draws: 796, Points: 825.0 (54.35 %)
Ptnml(0-2): [15, 124, 372, 210, 38]
LLR: 2.96 (-2.94, 2.94) [0.00, 5.00]

Possible areas for additional minification

get_hash now returns an array<u64, 2> instead of a u64. This means that callsites have to discard the pawn hash via [0] or use structured bindings if they want both hashes. We might be able to improve this. When writing this patch I experimented with the GCC __int128 type plus bithacking but didn't get particularly amazing results.
The main update code:

// Update correction history table
if (!in_qsearch && !in_check && (best_move.from == best_move.to || None == piece_on(pos, best_move.to)) &&
    !(tt_flag == Lower && best_score <= static_eval) && !(tt_flag == Upper && best_score >= static_eval)) {
    i32 &e = ch_table[pos.flipped][hashp % 16384];
    i32 nw = min(16, 1 + depth);
    e = min(max((e * (256 - nw) + nw * (best_score - static_eval) * 256) / 256, -8192), 8192);
}

This is a full-fat top-engine implementation. We may be able to squeeze out, say, 70% of the gains in exchange for a much simpler update rule, but I haven't experimented.
4090 bytes (+153)
Bench: 3957361

the nw stuff doesn't gain much I believe, so it might be of use removing it and doing a retest for bytes sake (see https://chess.swehosting.se/test/6998/)


use of console.error is causing errors downstream

I'm not certain if this qualifies as a "bug" in the usual sense, but we have a bundle that sometimes runs in a very old environment (IE 5). Buffer is included as part of this bundle, but doesn't run -- that is fine, because we don't actually use it when we're in this environment. However, the recent update it is causing it to break simply by including it, due to console being undefined.
I have seen many other projects do like if (console && console.error) {//throw error here} in order to prevent this. Would it be possible for buffer to do this as well? Thanks.

@Lyrencropt Yes, this is totally reasonable. Done in 5.0.3.


define the atoms

I took a stab at some names.

variables
paths (nee MovePath)
nodes (nee Points)
loans
origins (nee Regions)

Note that these all have a distinct first letter, should that be relevant, although I would also like to try and use written out words.
Thoughts? We can haggle on Zulip perhaps. =)

...I now understand variables.

if everyone likes origins, I've prepared https://github.com/rust-lang/polonius/pull/125 to at least start The Great Renaming™


don't log the license key even in debug/audit

By default the license key isn't logged given a) the default non-debug log level, and b) the default of not enabling the audit log.
While accuracy in those 2 non-default contexts can be useful in general, the inclusion of the license key does not provide much value and can serve to make log data more sensitive than it needs to be.
Filter out the license key from all contexts.

There is actually another area that logs the license key, I'm not sure if you want to include it in this PR, or address it separately, but when in debug level logging, we log all the config values from each source the agent receives, so the license key gets logged that way as well
Example of one of them:
DEBUG : Updating config (add) from NewRelic::Agent::Configuration::YamlSource. Results: { .........

Let me know if there is anything i can help with!


RHIROS 217 - Fix core_collect errors

@apuntamb - could you confirm if all playbooks run successfully in check-mode without an error?

@apuntamb - could you confirm if all playbooks run successfully in check-mode without an error?

@kgaikwad Yeah, it works fine for all three playbooks in check mode.

Thanks @apuntamb :+1: :ok_hand:


question：how upgrade kismatic from v1.0.2 to v1.0.3

how upgrade kismatic from v1.0.2 to v1.0.3

Hi @pennpeng -- we do not yet support upgrades. Stay tuned!


Allow an empty hash for options

Set :options to a empty hash in cases where there are no
extra options in the parsed file. Without this newproperty.is_to_s
raises an exception as it tries to find the keys of nil.

thanks @derekhiggins!


could not find release 2.6 in maven central repository

Hello,
The release 2.6 does not exist in the maven central repository : https://mvnrepository.com/artifact/com.blazemeter/jmeter-bzm-correlation-recorder

Could you please push it ?
Thank you
Guillaume

Hello @gulecroc,
Thank you for reaching out. Yes, you are right! As you could see on the Github Actions the release process failed on that step.
You can expect to be fixed by the end of the week.
Thank you so much for using the plugin!

Hello @Baraujo25 , do you have any update ? Thank you

Hi @gulecroc
Sorry for not having made the announcement, the release issue was fixed.
Version 2.6 is now available for use from maven.
https://mvnrepository.com/artifact/com.blazemeter/jmeter-bzm-correlation-recorder

Thank you all !


ExternalSecret fails if its name is >92 characters long

Whats the problem?
Currently, when an ExternalSecret has a name >92 characters long, it will fail to generate the target secret.
This is problematic, because Secret names can have up to 253 characters, and many users like to name their ExternalSecret the same as the target Secret resource.
NOTE: I am talking about the name of the ExternalSecret itself, there is no issue with creating a target Secret up to 253 characters long (assuming the ExternalSecret is 92 characters or less).
Why is it happening?
The problem is that we are trying to include the name of the ExternalSecret in the metadata.managedFields[0].manager of the target Secrets, and Kubernetes limits this field to 128 characters.
Here is the template variable for the manager field name:
https://github.com/external-secrets/external-secrets/blob/a0be752c8aecf456a5393ea5fa18b5db41bc53b9/pkg/controllers/externalsecret/externalsecret_controller.go#L60
For example, a target Secret might look like this:
apiVersion: v1
kind: Secret
metadata:
  name: target-secret
  managedFields:
    - apiVersion: v1
      fieldsType: FieldsV1
      fieldsV1:
        ...
      manager: externalsecrets.external-secrets.io/<NAME_OF_EXTERNAL_SECRET>
      operation: Update
      time: "2024-01-01T00:00:00Z"

What's the solution?
The purpose of the metadata.managedFields[0].manager is to indicate which controller manages each fields as part of server side apply. Realistically, we should just be setting this field to the string "external-secrets-controller" because the external-secrets controller is managing this field and the ExternalSecret resource is not the "controller".
How can I reproduce this?

Using external-secrets v0.18.5 or earlier
Create the following SecretStore:

apiVersion: generators.external-secrets.io/v1alpha1
kind: Fake
metadata:
  name: my-fake-secret
  namespace: default
spec:
  data:
    foo: bar
    baz: bang

Create the following ExternalSecret:

apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
  ## THIS WILL FAIL: it is 93 characters long
  name: 123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123

  ## THIS WILL SUCCEED: it is 92 characters long
  #name: 123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-12

  namespace: default
spec:
  refreshInterval: 60s
  target:
    name: my-target-secret
  dataFrom:
    - sourceRef:
        generatorRef:
          apiVersion: generators.external-secrets.io/v1alpha1
          kind: Fake
          name: my-fake-secret

Observe that the status of the ExternalSecret becomes SecretSyncedError and the logs in external-secrets become:

{"level":"error","ts":1730139939.7042181,"logger":"controllers.ExternalSecret","msg":"could not update Secret","ExternalSecret":{"name":"123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123","namespace":"default"},"error":"CreateOptions.meta.k8s.io "" is invalid: fieldManager: Too long: must have at most 128 bytes","stacktrace":"github.com/external-secrets/external-secrets/pkg/controllers/externalsecret.(*Reconciler).markAsFailed\n\t/home/runner/work/external-secrets/external-secrets/pkg/controllers/externalsecret/externalsecret_controller.go:360\ngithub.com/external-secrets/external-secrets/pkg/controllers/externalsecret.(*Reconciler).Reconcile\n\t/home/runner/work/external-secrets/external-secrets/pkg/controllers/externalsecret/externalsecret_controller.go:335\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Reconcile\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:116\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:303\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:263\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:224"}

The best solution is probably to introduce a backwards compatible fieldOwnerTemplate so we can automatically start using one that has <128 character while still being in-place upgradable.
I propose we do externalsecrets.external-secrets.io/sha1/<SHA1_OF_ES_NAME> as the /sha1/ prefix lets us know if it's using the new or old method in all the places we use the fieldOwnerTemplate template.


Adding the possibility to fix a required size

Hi,
In my application, I had to ignore some photos with unsatisfied size, that’s why I create this pull request.
Firstly, I added two configurations: public var requiredSize: CGSize?.
So, in the cellForItemAt method for collection view, I used the phAsset. pixelHeight and phAsset. pixelWidth to check the size.
If the size is not conformed to requiredSize, I set the property (a new property) unsatisfiedSize for TLPhotoCollectionViewCell to false.
When this property is set and in the didSet method, I check if the value is true or false and according to this value, I show or not an overlay with the current image size.
On cell selection, if this property (unsatisfiedSize) is set to false, I show a message in an alert. The title of this alert and the message can be configured with these two new configurations: unsatisifiedSizeTitle and unsatisifiedSizeMessage

I think a more generic solution for the use case would be to create an optional method in the delegate, something like shouldSelect(asset: TLPHAsset) -> Bool , and then your implementation of the delegate could check the asset size and return false if it is too small. This would allow other type of check (like for example, if someone want to restraint users to pick too old pictures, to check the date time and display their own message)

In this case, we should wait for the user to tap on the photo before tell him that the image can’t be selected.
This is what this feature looks like:

Interesting!
Generic solution could be useful to handle multiple cases, indeed. Let me check that...

Just a thing : I'm just giving my advice, I'm not a reviewer or maintainer of this lib, just a developer who use it :)

What about this solution:
In the TLPhotosPickerViewControllerDelegate, I added an optional function called func overlayViewForAsset(asset: TLPHAsset) -> UIView?. Then, in the cellForItemAt method, I can replace my old code with this:
if let overLay = self.delegate?.overlayViewForAsset(asset: asset) {
    cell.addSubview(overLay)
}

I will check later for a better solution to add the overlay on the cell.

This is an example of the PhotoPickerWithNavigationViewController implementing this protocol:
extension PhotoPickerWithNavigationViewController: TLPhotosPickerViewControllerDelegate {
    func overlayViewForAsset(asset: TLPHAsset) -> UIView? {
        guard let phAsset = asset.phAsset else {
            return nil
        }
        if phAsset.pixelHeight < 300 || phAsset.pixelWidth < 300 {
            let view = UIView(frame: CGRect(x: 0, y: 0, width: 200, height: 200))
            view.backgroundColor = UIColor.red
            return view
        }
        return nil
    }
}

@aliabbas90 @philippeauriach
I think there is a simple solution.
Please check this.
https://github.com/tilltue/TLPhotoPicker/commit/29b76dbb5c0cfafb46b2530fb298290bdff13034

Does that mean that the image loaded in the collection view is the full size image ? I think the advantage of working with phassets is that you can require and display a small image, and then use the full size after selecting the one you want, so that image.size in your example will be the size of the UIImage displayed, and not the true pixel height of PHAsset ?
Aside of this, there is a typo in your solution : requiedSizeLabel => requiredSizeLabel

How about filtering photo library by picture size?
I think If it can not be selected, it's better not to show it.
let options = configure.fetchOption ?? PHFetchOptions()
        options.sortDescriptors = [NSSortDescriptor(key: "creationDate", ascending: false)]
        let requiredSizePredicate = NSPredicate(format: "pixelHeight > %d AND pixelWidth > %d", 300,300)
        options.merge(predicate: requiredSizePredicate)

That's clearly the best way IMO (unless the developer want to explain to the user why he cannot select this picture)

@aliabbas90 @philippeauriach
Added update(with phAsset) method.
Don't you want to use custom cell?
https://github.com/tilltue/TLPhotoPicker/commit/fc0d2973c586b17f57a0dd86e7e986b5cde3f0bb

This and the custom cell is perfect IMO

Filtering photo library by picture size could be a little bit confused for user. Most of time he didn't know the size of its pictures, so he may not understand why the picture is not shown no ? He will maybe think that's a bug in the app..

@aliabbas90
Indeed. please check this.
I wish this is what you want.
https://github.com/tilltue/TLPhotoPicker/commit/3de48ac56e634c3fa60695a4c24457af6090863d

Here the sample.
git branch : https://github.com/tilltue/TLPhotoPicker/tree/requied-image-size

Thank you.
So, let me summary. To handle the required size we should:

Create a custom cell with a new method called update(with phAsset: PHAsset)
Handle the selection with a closure property :   shouldSelectedCell (maybe call it handleSelection?)
or the delegate method: func shouldSelectedCell(phAsset: PHAsset) -> Bool maybe call it canSelectedCell ?)

Then in our view controller, add the closure to the shouldSelectedCell or implement the method shouldSelectedCell.
Thank you for the sample. I see now the benefit of subclassing the cell.

@aliabbas90
Basically, Yes.

@tilltue Thank you. I prepare the new PR.

Release 1.7.0


#1171 - Get payment providers

This PR is to:

Enhance Payment Method UI.
Support Payment Provider logo.
Remove redundant field (additionalSettings) showing on UI.
Add APIs to create/update payment providers.

New UI:

Integrating with #1272


where do instrument files go?

Question is where instrument files go:
issues: large memory hog, not all instruments may be needed, github large file service issue
options:
(1) set up download site (dropbox, amazon) to download instrument files
(2) user installs into correct folder in code path (may cause problems on update)
(3) user installs into separate folder and must include this folder in program variable (e.g., pyspextool.EXTERNAL_INSTRUMENT_FILES = '/Users/adam/data/pyspextool_instruments/'
(4) code automatically downloads instrument files as needed into correct folded in code path if missing
(5) others?

We could also host the file on Amazon Web Services and point to a URL. I will ask around about how to cache this file once it's downloaded once.

I think astropy has the answer: https://docs.astropy.org/en/stable/utils/data.html

solved!


When using ansible to install and deploy, please don't download the image again every time.

When using ansible to install and deploy, please don't download the image again every time.

Are you referring to the runtime images? If so, there's a flag to skip pulling the images. skip_pull_runtimes.


add option to download VAT-Spy data automatically

Instead of manually releasing proxy updates and/or requiring users to link manually downloaded VAT-Spy files, the proxy should receive an option to automatically download the latest released version as announced by VATSIM.
The proxy has been designed to be as minimal as possible, so this option was intentionally left out as it requires a permanent folder to be specified for caching the retrieved data. Such an option starts to make more sense now that further functional updates to the proxy should be quite rare, so essentially most releases will only happen to update the included data. Regular updates to the proxy should still happen but by providing users an option to update VAT-Spy data automatically, the intervals could be increased to twice per year or whenever an update needs to be done for other reasons than just updating VAT-Spy data.
The option must not be enabled by default.

The file would need to be checked if it can be parsed (plus maybe a small plausibility check) before replacing the previous files, otherwise issues like https://github.com/vatsimnetwork/vatspy-data-project/issues/674 would break previously working data (the typo led to the file not being able to be opened at all).


node-int64 improvements

Hello,
Please consider pulling the associate commits.  They provide the following:

Enable support for instanceof
Added a compare() method to compare an Int64 with another

Thanks!

Doug

@nuggetwheat - Thanks for contributing!  Can you please add tests for both instanceof and compare functionality to test.js?  Thanks!

Hey Robert,  Sure, no problem!  In writing the test for compare, I realized that it just does a simple lexicographical comparison of the bytes, which is probably not what people would expect.  I'll change it so that it compares the actual integers.

Hi Robert, I added the unit tests.  I also added a convenience method 'equals' for symmetry with the methods of the Buffer class.  Please let me know if it looks ok.  Feel free to squash them down to a single commit.

npm publish'ed as v0.4.0

Excellent!
On Fri, Apr 3, 2015 at 7:52 PM, Robert Kieffer<EMAIL_ADDRESS>wrote:

npm publish'ed as v0.4.0
—
Reply to this email directly or view it on GitHub
https://github.com/broofa/node-int64/pull/12#issuecomment-89491146.


Coder: It should provide playground also when part of a composite tool

Similarly to the Inspector changes #1432 which provides embedded Inspector playground when the inspector is composed:

we want to rework Coder to work similarly. Currently, there is no playground available:

thisPlayground phlow
	spawnTool: (GtPhlowCompositeTool new
		addTool: (
			GtInspectorTool forObject: 42);
		addTool: (
			GtClassCoderTool forClass: 42 class))

We have a horizontal and vertical sidebar elements that can be reused by other tools:

Coder displays playground also when composed with other tools:


Hands-on Tutorial on Qiime (Metagenomics)

Hello,
I'm writing a tutorial based on this:
http://nbviewer.jupyter.org/github/biocore/qiime/blob/1.9.1/examples/ipynb/illumina_overview_tutorial.ipynb
Daniel

The biom suit of tools are not available. Would need at least the biom summarize-table for this tutorial.

The perform open-reference OTU picking tool generates an empty file which is necessary for the tutorial

I will work on the missing tools (in biom-format) in the next days
What is the generated empty file by pick_open_reference_otus?

It's the "OTU table with taxonomic assignment and without sequences failing the alignment to the OTU representative sequences". Basically the equivalent to otu_table_mc2_w_tax_no_pynast_failures.biom

@dsobral Are you still working on the tutorial? Do you need any help with it?

I have been busy with other stuff, but I plan to continue working on the tutorial. I'll check if the tools now allow me to complete the qiime overview tutorial.

By the way, are the new biom tools in the main toolshed? Thanks!

Sorry, I saw they are in the Test Toolshed.

We will write tutorials for QIIME2 as soon as it is ready. @blankenberg can you update us on the status of the qiime2 integration?


Add ActiveHash::Base.polymorphic_name

Add ActiveHash::Base.polymorphic_name and fixed ci.
refs. rails/rails#32148

Looks fine!
Thank you 😄


[Snyk] Upgrade tslib from 2.5.3 to 2.6.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade tslib from 2.5.3 to 2.6.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2023-06-26.

Release notes

Package name: tslib

2.6.0 - 2023-06-26What's Changed

Add helpers for using and await using by @ rbuckton in #213

Full Changelog: v2.5.3...2.6.0

2.5.3 - 2023-06-02What's Changed

Do not reference tslib.es6.js from package.json exports by @ andrewbranch in #208

Full Changelog: 2.5.2...v2.5.3

    from tslib GitHub release notes

Commit messages

Package name: tslib

7c7f3ae 2.6.0
f641b05 Add helpers for `using` and `await using` (#213)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Patch and project coverage have no change.

Comparison is base (8caa257) 99.52% compared to head (4cb106d) 99.52%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #16   +/-   ##
=======================================
  Coverage   99.52%   99.52%
=======================================
  Files           6        6
  Lines        3398     3398
  Branches       41       41
=======================================
  Hits         3382     3382
  Misses         16       16

Flag
Coverage Δ

unittests
99.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add plot with variance around points for GP's and models that have a return_std() argument

This might need a change in the plotting interface to make custom plotting for specific models possible. So potentially a bigger issue.

now addressed in #238


Look for additional items to add to the writing checklist.

This is a straightforward task appropriate for an undergraduate.
I have reviewed tons of student documents over time. I'm sure there are comments that I repeat frequently, but which don't yet appear on the writing checklist. I was thinking :

I could share some of those old reviews with you,
You could peruse my scribbles
You could identify comments I make frequently or which could be added to the checklist.
And you could add those items to the writing checklist.

This isn't urgent, but maybe @Dayvis7 would be appropriate for it if he has time this summer? Whomever wants to do this task, please let me know and I'll point you to the old reviews.

I could try to look it over! You're saying just to find common suggestions and add them to the official checklist? That sounds easy enough.

Yep, I'll slack message a link with a bunch of old reviewed pdfs so you can get started whenever you like.

@katyhuff what do you think of these?
-Each sentence/paragraph should logically follow the previous sentence/paragraph
-Concise language - If you're going to say something, don't beat around the bush
-Cite, Cite, Cite. Cite images, software, anything of that nature
-When making examples, use variables instead of numbers, or use symbols/math characters instead of acronyms
-Italicize words or phrases distinct to your work
-You're a human writing for other humans: Make the wording exciting, and remember some people reading it
won't know as much as you do. Be specific, yet general enough for others to know.
-If you're using an uncommon word, either consider changing it or define it in its first usage.
-Don't repeat yourself too much. Using the same phrase every few paragraphs gets boring

these look great!!! Thanks @Dayvis7 !


404 with await ctx.render('404') has application/json content type

this is because the body is empty per https://github.com/koajs/koa/blob/971115cfbd970f97a79df1a02a4ef7f980170773/lib/response.js#L135
so the only way to fix is to not only set ctx.throw(404) but to also reset the content type when you're sending a 404 error
we should maybe account for 404 errors here before we unset everything?

what is ctx.render()?

for koa@next when I have error middleware like this at the top of my file, I have to explicitly say ctx.type = 'html'; for example...  (maybe I'm doing it wrong?) -- this was from code I did the other day
// initialize try/catch error handling right away
// adapted from: https://github.com/koajs/onerror/blob/master/index.js
// https://github.com/koajs/examples/issues/20#issuecomment-31568401
app.use(async (ctx, next) => {

  try {
    await next();
    if (ctx.status === 404)
      ctx.throw(404);
  } catch (err) {

    if (err.name) {
      switch (err.name) {
      case 'ValidationError':
        err.status = 400;
        if (err.errors) {
          let errors = _.map(
            Object.values(err.errors),
            (e) => {
              switch (e.kind) {
              case 'required':
                return `${_.upperFirst(e.path)} is required`;
              default:
                return _.trimEnd(e.message, '.');
              }
            }
          ).join(', ');
          err.message = `${err.message}: ${errors}`;
        }
        break;
      }
    }

    ctx.status = err.status || 500;
    ctx.body = Boom.create(err.status, err.message).output.payload;

    app.emit('error', err, ctx);

    let type = ctx.accepts(['text', 'json', 'html']);

    if (!type) {
      ctx.status = 406;
      ctx.body = Boom.notAcceptable().output.payload;
    }

    switch (type) {
    case 'html':
      if (ctx.status === 404) {
        ctx.type = 'html';
        // https://github.com/koajs/koa/issues/646
        await ctx.render('404');
      } else {
        ctx.flash('error', err.message);
        ctx.redirect('/');
      }
      break;
    case 'json':
      ctx.body = JSON.stringify(ctx.body);
      break;
    default: // case 'text':
      ctx.type = 'text';
      ctx.body = JSON.stringify(ctx.body, null, 2);
      break;
    }

  }

});

see how i use ctx.render in that block -- it's my nunjucks rendering via https://github.com/hanai/koa-nunjucks-promise

also for reference, Boom is https://github.com/hapijs/boom

yeah i always throw the error and let upstream error handlers handle those pages. i also don't set headers unless i know the status code isn't gonna be an error, which makes things a little more robust, but is more annoying to code.
i also don't do content negotiation anymore :P hard to cache

how the heck do we do this then?  for example: https://github.com/niftylettuce/ratelimit/blob/master/src/index.js#L67-L74

you'd have to remove the headers yourself. :(

how do I do that? @jonathanong very confused here...

https://github.com/koajs/koa/blob/fcacb352208115e60fffe145394f904743dfa8c3/lib/context.js#L121
hacks galore!
unless you want to make a PR for https://github.com/koajs/koa/issues/571 :)

@jonathanong how do we override that onerror, via app.onerror = fn?  is there any examples of someone doing this?

just doing app.context.onerror = should work, but onerror should only be used when extremely necessary.
instead, this and similar middleware should be relying on an upstream error handler like:
app.use(function* (next) {
  try {
    yield next
  } catch (err) {
    // handle error
    this.status = err.status || 500
    this.body = { message: err.message }
  }
})

but then you have to do special cases for middleware like that rate limit one... which is why it's better just to have a public API

oh shit. i read the code wrong. i thought you were setting that body after await next but you're early returning.
what's the issue?

the issue is that headers are removed from the request on an error, when I don't want them to be

only if onerror handles it. if you make your own middleware, you can do wahtever you want.

Does c826467 resolve this?

yes https://github.com/koajs/koa/commit/c82646756053395e463cad059ed776611a99c1fd should resolve this


Add alternate format for inline events

Please change formatting and logic of [startTime:: XX:XX] [endTime:: XX:XX]
For example use standard task format HH-mm and variable defining length by cleaning of code 12:05 duration: 1.5h
- [ ]  12:05, 1.5h
The main reason is that it require to much typing when entering task in note.

You should please utilize the current plugins naming convention, especialy from the https://obsidian-tasks-group.github.io/obsidian-tasks/ and also make the writing of the task as less burden as possible. The colaboration with Obsidian task developer will be very fruitfull, as he already created GUI for editing task properties. He is just missing the lenght parameter!
This is just sugestions. I know you want to utilize the YAML inline fields, but except your plugin I don't think other people will be querieng this for task. As they have Tasker-plugin with huge options. Even for long term I advice to contact the developer and find common ground.

that doesn't mean that we can't add alternate formatting. I will keep this issue open as an enhancement.

I'd recommend ISO 8601, while a bit weird looking it is already standardized and parsable from most libraries


[Feature]: Run Shopify Functions / Checkout UI Extensions Locally and point to Plus store

What area(s) will this request affect?
Extension
What type of change do you want to see?
New feature
Overview
It would be ideal to be able to locally develop (npm run dev) and point to a plus store. A plus store that is not defined within the partner dashboard, there should be a way to select the store and locally develop. Additionally, a plus store that is defined in the companies partners dashboard should select without error and allow for local development.
Motivation
Right now each developer at our company will do one or both of the following:

Action
Problem

Create a new development store and npm run dev
The downside is that we have to simulate/duplicate the store setup to what we have with our clients and becomes complex when we have multiple staging and production stores to test and deploy to

Create a development app, install onto the plus store and then each time a change is made npm run deploy
The downside is that it's slow to actually develop and test the changes each time as we lost the benefits of the local preview

Can we re-open this for the folks following the issue? This would greatly improve our development process, so once it's available, we want to start using it.

Still relevant On Oct 12, 2023, at 20:34, github-actions[bot] @.***> wrote:
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action.
→ If there's no activity within a week, then a bot will automatically close this.
Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Still relevant On Nov 4, 2023, at 20:34, github-actions[bot] @.***> wrote:
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action.
→ If there's no activity within a week, then a bot will automatically close this.
Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>


disabel aggregation:kyverno_policy_deployment_status_team recording rule

Towards: https://github.com/giantswarm/giantswarm/issues/24418
This PR disables the aggregation:kyverno_policy_deployment_status_team rule to save on Grafana Cloud costs. After a quick calculation, this should help save ~$300 monthly.
Checklist

[x] Update CHANGELOG.md
[ ] Add Unit tests
[x] Follow Alert structure
[ ] Consider creating a dashboard (guidelines) (if it does not exist already) to help oncallers monitor the status of the issue.
[ ] Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).

I just personally find it easier for reverting this change (which will eventually happen at some point) to have it commented rather than having to search in the git history later :shrug:

Why will we eventually revert this change?
Do we need this data, or not?

See the following slack thread : https://gigantic.slack.com/archives/C02FL4EAADD/p1720429374452249

I don't really like that we have a recording rule that we enable/disable like that to save costs.
I'd rather have a sustainable solution that we can keep running all the time at a lower cost.
I tent to think policy_report_result has too high cardinality, and should not be generated as metrics.
Maybe it should be some kind of event stored in loki.

I understand your concerns and I also think a more persistent solution in the long run. But yeah, for now, just disabling this rule could allow us to really save on costs.


DA PHOENIX SUPERHUMAN PROJECT

https://github.com//qiew/tree/master/first_proto%2Fbak

Hello, this is the second issue you've logged against this repo with no details.  Is there a bug or why have you opened these issues?

Hello, this is the second issue you've logged against this repo with no details.  Is there a bug or why have you opened these issues?

Research


Remove "Delete listing" button after successful deletion

#20

@Salz0 I didn't find a feature to disable button, so I just remove it


SQL Errorlog Viewer

Adding ability to dbadash to monitor or view SQL error log.

Similar to #1062, maybe sp_LogHunter could be triggered to run on demand.
The problem with collecting data from the error log is the signal-to-noise ratio.  Filtering out known noise is one option but seems like a losing battle to create a universal exclusion list (I've gone down this route in the past and abandoned it).  Filtering for known interesting events might be a better approach - I think sp_LogHunter might do this.
Interrogating the error log from DBA Dash would be useful.  I think this could be done directly with the messaging feature.  It's not on my immediate radar, but I'd like to include it at some point.