K8SPXC-333: add extra fields to version service request

Add extra fields to version service request

Test name
Status

recreate
failed

init-deploy
passed

scaling
passed

storage
passed

big-data
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

monitoring-2-0
passed

demand-backup
failed

affinity
passed

scheduled-backup
failed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

big-data
passed

recreate
passed

scaling
passed

storage
failed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade
passed

limits
passed

monitoring
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

demand-backup
passed

operator-self-healing
passed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

recreate
passed

init-deploy
passed

scaling
passed

big-data
passed

storage
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

monitoring
failed

demand-backup
failed

monitoring-2-0
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
failed

scheduled-backup
failed

affinity
passed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

Test name
Status

init-deploy
passed

recreate
passed

scaling
passed

storage
passed

big-data
failed

scaling-proxysql
passed

self-healing
passed

limits
passed

monitoring
failed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring-2-0
passed

self-healing-advanced
failed

affinity
passed

upgrade-consistency
passed

security-context
passed

demand-backup
passed

operator-self-healing
passed

one-pod
failed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

big-data
failed

storage
passed

recreate
passed

self-healing
passed

restore-to-encrypted-cluster
passed

self-healing-advanced
failed

demand-backup
passed

scheduled-backup
failed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
failed

init-deploy
passed

limits
passed

big-data
failed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
passed

storage
passed

upgrade-consistency
passed

self-healing
passed

security-context
passed

self-healing-advanced
failed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

operator-self-healing
passed

big-data
failed

demand-backup-encrypted-with-tls
passed

Test name
Status

storage
passed

scaling
passed

recreate
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

upgrade
passed

demand-backup
passed

self-healing-advanced
failed

init-deploy
passed

upgrade-consistency
passed

limits
passed

scheduled-backup
failed

security-context
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

big-data
failed

operator-self-healing
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

storage
passed

recreate
failed

scaling
failed

big-data
failed

init-deploy
passed

self-healing
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

limits
passed

upgrade
passed

demand-backup
failed

upgrade-consistency
passed

self-healing-advanced
failed

security-context
passed

monitoring
passed

scheduled-backup
failed

monitoring-2-0
passed

operator-self-healing
passed

affinity
passed

demand-backup-encrypted-with-tls
passed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

Test name
Status

Test name
Status

storage
failed

self-healing
failed

init-deploy
failed

big-data
failed

self-healing-advanced
failed

limits
failed

operator-self-healing
failed

monitoring
failed

scaling
failed

monitoring-2-0
failed

scaling-proxysql
failed

affinity
failed

upgrade
failed

one-pod
failed

auto-tuning
failed

upgrade-consistency
failed

proxysql-sidecar-res-limits
failed

security-context
failed

users
failed

recreate
failed

restore-to-encrypted-cluster
failed

demand-backup
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
failed

limits
failed

monitoring
failed

monitoring-2-0
failed

affinity
failed

one-pod
failed

auto-tuning
failed

scaling
failed

proxysql-sidecar-res-limits
failed

users
failed

scaling-proxysql
failed

upgrade
failed

big-data
failed

upgrade-consistency
failed

security-context
failed

recreate
failed

restore-to-encrypted-cluster
failed

storage
failed

demand-backup
failed

self-healing
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

self-healing-advanced
failed

operator-self-healing
failed

Test name
Status

init-deploy
failed

limits
failed

monitoring
failed

monitoring-2-0
failed

storage
failed

affinity
failed

self-healing
failed

one-pod
failed

scaling
failed

auto-tuning
failed

self-healing-advanced
failed

scaling-proxysql
failed

proxysql-sidecar-res-limits
failed

operator-self-healing
failed

upgrade
failed

recreate
failed

users
failed

upgrade-consistency
failed

security-context
failed

restore-to-encrypted-cluster
failed

demand-backup
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

big-data
failed

Test name
Status

recreate
passed

scaling
failed

init-deploy
passed

storage
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

restore-to-encrypted-cluster
failed

upgrade
passed

monitoring
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup
failed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

recreate
passed

restore-to-encrypted-cluster
failed

big-data
passed

scaling
failed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

demand-backup
failed

Test name
Status

big-data
passed

storage
passed

init-deploy
passed

recreate
passed

scaling
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

restore-to-encrypted-cluster
failed

upgrade
passed

demand-backup
passed

self-healing-advanced
passed

upgrade-consistency
failed

monitoring
passed

security-context
passed

operator-self-healing
passed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
passed

auto-tuning
passed

demand-backup-encrypted-with-tls
failed

proxysql-sidecar-res-limits
passed

users
passed

Test name
Status

scaling
passed

init-deploy
passed

recreate
passed

limits
passed

scaling-proxysql
passed

restore-to-encrypted-cluster
failed

monitoring
passed

upgrade
passed

monitoring-2-0
passed

upgrade-consistency
failed

affinity
passed

storage
passed

one-pod
passed

self-healing
passed

auto-tuning
passed

self-healing-advanced
passed

proxysql-sidecar-res-limits
passed

demand-backup
passed

operator-self-healing
passed

users
passed

scheduled-backup
failed

big-data
passed

security-context
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

big-data
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

recreate
passed

restore-to-encrypted-cluster
failed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
failed

security-context
passed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

big-data
passed

recreate
passed

init-deploy
passed

storage
passed

scaling
passed

self-healing
failed

scaling-proxysql
passed

limits
passed

restore-to-encrypted-cluster
failed

monitoring
passed

upgrade
passed

self-healing-advanced
failed

demand-backup
passed

upgrade-consistency
failed

monitoring-2-0
passed

security-context
passed

operator-self-healing
passed

scheduled-backup
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

recreate
passed

big-data
failed

init-deploy
passed

scaling
passed

self-healing
failed

scaling-proxysql
passed

limits
passed

upgrade
passed

self-healing-advanced
passed

restore-to-encrypted-cluster
failed

monitoring
passed

demand-backup
passed

operator-self-healing
passed

monitoring-2-0
passed

upgrade-consistency
failed

security-context
passed

affinity
passed

scheduled-backup
failed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
failed

storage
passed

self-healing
failed

recreate
passed

restore-to-encrypted-cluster
failed

big-data
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

security-context
passed

demand-backup
passed

scheduled-backup
failed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

recreate
passed

big-data
passed

init-deploy
passed

scaling
passed

storage
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

monitoring
passed

upgrade
passed

restore-to-encrypted-cluster
passed

monitoring-2-0
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

affinity
passed

demand-backup
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

Test name
Status

big-data
passed

scaling
passed

recreate
passed

init-deploy
passed

storage
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring
passed

self-healing-advanced
passed

upgrade-consistency
passed

monitoring-2-0
passed

security-context
passed

demand-backup
passed

operator-self-healing
passed

affinity
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

recreate
passed

scaling
passed

storage
passed

big-data
passed

init-deploy
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

monitoring
failed

upgrade
passed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

upgrade-consistency
passed

monitoring-2-0
failed

security-context
passed

operator-self-healing
passed

demand-backup
failed

affinity
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

init-deploy
passed

storage
passed

limits
passed

self-healing
passed

monitoring
passed

self-healing-advanced
passed

scaling
passed

operator-self-healing
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

big-data
passed

demand-backup
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

init-deploy
passed

scaling
passed

limits
passed

scaling-proxysql
passed

monitoring
passed

upgrade
passed

monitoring-2-0
passed

upgrade-consistency
passed

security-context
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

big-data
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

init-deploy
passed

demand-backup
passed

limits
passed

scheduled-backup
failed

monitoring
passed

scaling
passed

monitoring-2-0
passed

storage
passed

scaling-proxysql
passed

affinity
passed

self-healing
passed

upgrade
passed

one-pod
passed

self-healing-advanced
passed

upgrade-consistency
passed

auto-tuning
passed

operator-self-healing
passed

security-context
passed

proxysql-sidecar-res-limits
passed

users
passed

big-data
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

Test name
Status

big-data
passed

Test name
Status

init-deploy
passed

scaling
passed

big-data
passed

recreate
passed

storage
passed

self-healing
passed

scaling-proxysql
passed

upgrade
passed

limits
passed

restore-to-encrypted-cluster
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

monitoring
passed

demand-backup
failed

operator-self-healing
failed

monitoring-2-0
failed

affinity
failed

scheduled-backup
failed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

users
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

big-data
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

scaling
passed

init-deploy
passed

big-data
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring
passed

upgrade-consistency
passed

security-context
passed

demand-backup
passed

self-healing-advanced
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

scheduled-backup
failed

operator-self-healing
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

users
passed

demand-backup-encrypted-with-tls
passed


Oracle JDK - Ability to Download Your Own File?

I recently read the (sdkman) blog post about the download link issues for Oracle JDK. Unfortunately, OpenJDK is not an option for our organization, but still, we desperately need the version management features of sdkman.
This may be somewhat wonky, but what if the user could download their own file and provide the file locally to sdkman?

I would very much appreciate that. Currently – only for one project – I absolutely need the Oracle SDK. So what I needed to do was:

http://www.webupd8.org/2012/09/install-oracle-java-8-in-ubuntu-via-ppa.html
vim ~/.bashrc
comment out the sdkman initialization

Next time, I need to use the sdks installed via sdkman, I need to uncomment that section. This is annoying.

Closing this as I was made aware of the local install feature of sdkman:
http://sdkman.io/usage.html#localversion

Example for using a preinstalled (local) version of the oracle jdk with sdkman on Ubuntu 14.04:
sdk install java 8u131-oracle-local /usr/lib/jvm/java-8-oracle
sdk default java 8u131-oracle-local


ARROW-14185: [C++] HashJoinNode should validate HashJoinNodeOptions

Adding validation for HashJoinNodeOptions

General comment: can we also add a few short unit tests to test this validation?

Hmm, the docs CI is persistently failing. Do you mind rebasing @JabariBooker?

Hmm, the docs CI is persistently failing. Do you mind rebasing @JabariBooker?

@lidavidm Seems to have fixed the issue. Now there are failures for TestS3FS and TestS3FSGeneric due to an IOError.

Thanks!


Added Busbud to the list

Multiple developer positions open and you can apply by uploading a résumé

Thank you for the PR! Could you please link to their main careers page (i.e. https://www.busbud.com/en/careers) instead? I want to make sure users have a chance to learn about the company they're applying to before applying

Done! 😁 Thank you @j-delaney

Merged in! Thanks a ton for your contribution :)


Error reporting in handler requests

When a handler crashes, this can be somewhat ideal at times. But ideally not regularly.
For example errors report as:
<<"Caught error in websocket handler">>
But maybe we can put the reason in the error string. This would help a lot in figuring out what is causing the error.
fn handle_ws_message(state: Socket, conn, message) {
  case message {
    mist.Binary(json) -> {
      case decode_type(message) {
         Ok(RatingType("rating")) -> {
              let assert Ok(_) = mist.send_binary_frame(conn, <<image:utf8>>)
          }
      }
    }
  ...
}

import gleam/erlang

logger.error(string.concat(["Caught error in websocket handler: ", erlang.format(reason)]))

<<"Caught error in websocket handler: {errored,{case_clause,{ok,{rating_type,<<\"rating\">>}}}}">>
Would make it a lot easier to find these errors, even if it requires translating the erlang response. I would also love the ability to turn on stack traces but I did some poking around and couldn't find support in gleam for them.
Thank you for reading.
Edit:
Another example. Maybe it could be cleaned up a little more or handled differently.
<<"Caught error in websocket handler: {errored,#{function => <<\"handle_json_message\">>,line => 123,\n           message => <<\"Assertion pattern match failed\">>,\n           module => <<\"image_scorer\">>,\n           value => {error,{bit_decode,<<\"Could not decode base64\">>}},\n           gleam_error => let_assert}}">>

I like that idea, and pretty easy to extend what I have with that.
=ERROR REPORT==== 10-Dec-2023::16:21:51.975168 ===
<<"Caught error in websocket handler: {errored,#{function => <<\"main\">>,line => 25,\n           message => <<\"Assertion pattern match failed\">>,\n           module => <<\"ws_test\">>,\n           value => {error,nil},\n           gleam_error => let_assert}}">>

Just pushed this, can do a release for this in the near future.  Thank you!

Sweet! I have been using it in my current build and it helps quite a bit :). Though I think the formatting could be improved but not sure if you wanted to go in that direction of parsing the formatted string (at least inferring the new lines as new log lines or something)

For example in gleam tests I get this error format. I know in error logging it might not be ideal though.


angular build broken?

I cannot make the angular playground or the angular build work.
And I am unsure but I think our Angular build still need jquery to be included to really work.

Fixed with c6e78c1c672a8db25e3fe312a9c52e16de29ce86

And I am unsure but I think our Angular build still need jquery to be included to really work.

Yes yes, you need to include jQuery in addition to Angular.


pachctl put file Failing on Large File

This is on Beta 2.
I am attempting to upload a file that is approximately 2 GiB in size using pachctl put file.  However, the upload consistently fails after exactly 1 GiB has been uploaded.  On the client side, it just says "EOF" - as if pachctl thinks it's reached the end of the file:
[Tue Jul 20 02:59:53]
{pach 2.0.0-beta.2 : default} / {k8s 1.16.13-dispatcher : aws} / {git 2.24.3 : customer-success/master}
~/Documents/Work/Repos ... /performance/2.0.0-beta.1 -->> pachctl put file bench@master -f storagelog-1.13.2-singledatum.log
storagelog-1.13.2-singledatum.log 1.00 GB / 1.00 GB [=================================================================================================================================] 0s 2.65 MB/s
EOF

Notice how it shows exactly "1.00 GB" for both the amount uploaded as well as for what it thinks the total size of the file was. This is reproducible every time for me.
The pachd logs show the following:
2021-07-20T19:07:23Z ERROR pfs.API.ModifyFile {"duration":422.112130988,"error":"context canceled","request":{"branch":{"repo":{"name":"bench","type":"user"},"name":"master"},"id":"f00d93be768b472a9c73bc238d63b285"},"stack":null}

Note also, I don't think it's a timeout issue, for two reasons:

It always fails at exactly 1.00 GB, whereas I would expect some variation here if it was a timeout; and
On the last run I did, it failed after 7 minutes and 30 seconds, which would be a rather unusual value for a timeout. :)

This appears to be fine on Hub with beta 2. We did have an issue before where >= 1GB size files were problematic because we would buffer that much in memory then buffer it again elsewhere, which would result with an OOM kill on the Hub machines since the memory limits are pretty low. The memory threshold now accounts for the buffering at both layers, and that appears to be resolved in Hub with beta 2, but this may be a similar issue with your environment. Is there some more information you could provide such as the memory limits and the full set of logs as well as checking if an OOM kill occurred?

When my current set of performance tests completes, I'll reproduce this and upload the logs. There definitely were no OOM conditions being hit as none of the pods had restarted, and there were no errors in the pachd log other than the "context cancelled" one that I mentioned earlier.  The resource requests for the containers are set to 1 CPU and 2 GiB of memory, with no limit being explicitly set.  The nodes themselves have 32 vCPUs and 128 GiB memory.

@brycemcanally - Here are the logs from my latest repro of this issue.
pachd.log
postgres.log
etcd.log
pipeline-benchmarking-v1-t52gh-storage.log
pipeline-benchmarking-v1-t52gh-user.log

Some additional info - it turns out that this is not limited to a single large file.  The exact same behavior occurs if you attempt with a single put file command to upload multiple files whose aggregate size is greater than 1 GiB.

 I'm going to try AWS + port forwarding, which is the same setup Dale is using. Dale also confirmed the same command doesn't fail with AWS + port forwarding on 1.13, on the same k8s cluster.

This problem exists in Beta 3 as well.

I'm almost certain this is an issue with port-forwarding in k8s 1.20 interacting with the way our putfile RPC works. I'm trying to upgrade a GKE cluster to 1.20 to confirm.

With the most verbose logging possible in kubelet (--v=5 for the kubelet process and DEBUG=1 in the env), there are no errors in the kubelet. The stream opens and proxies traffic normally, then kubelet stops recieving data and waits until it times out (socat stays up during this time).
From the pach client perspective, wireshark shows that the connection just disappears - we get 3 RST in a row with no FIN.
The pach client connection is to the k8s master IP and not the kubelet, so it seems like the traffic must go client -> master -> kubelet -> pod. It seems like the master process itself is crashing, but it's difficult to tell in a managed k8s cluster.
There is an open k8s issue here that suggests this could actually be provoked by a specific byte sequence - considering this seems to happen deterministically based on the offset in the file being uploaded and it doesn't affect 1.13, that might be worth considering (https://github.com/kubernetes/kubernetes/issues/74551#issuecomment-600750593).

@dgeorg42 this just needs a kb article now

I'm not sure how this just needs a KB article now. I mean, at this point all we've identified for certain is that:

Uploads of one or more files with a total file size > X will always fail after uploading exactly X bytes;
The value of X varies based on some unknown factor that may or may not be connection speed (for Alysha it failed consistently at 2.1 GB, for me it was always at 1.0 GB); and
It's probably not a Pachyderm issue per se because the pachctl client just sees the connection mysteriously vanish.

But we still don't know the actual root cause, or even what to suggest as a workaround.

Also, I'm not convinced that this is a k8s 1.20 or AWS networking issue, as Alysha has proposed. One or both of those may be contributing factors, but this issue is ONLY reproducible in 2.0.  I have tried to reproduce this in 1.13, keeping everything else the same, and have been unable to do so.

Still unclear what the actual issue was, but this is no longer reproducible as of 2.0.0, so I'm closing this.


Export isChangeAddress

This pull request exports the function isChangeAddress for the AddressState type and also adds a documentation property isOurs.

Thanks


M$ shame #16182: M$ Connect-IPPSSession ignores the PowerShell most basic best practices

Hello
It is extremely frightening that because of the apparently complete lack of M$ quality assurance, hardly a day goes by when we stumble across a new M$ disgrace.
Tody, we had to see that M$ PowerShell Modules ignores PowerShell most basic best practices.
For example, if you:

Open PowerShell not elevated
Start Connect-IPPSSession and use a Certificate Thumbprint
Then you get:

Error Acquiring Token:
System.Security.Cryptography.CryptographicException: Keyset does not exist
   at System.Security.Cryptography.CapiHelper.CreateProvHandle(CspParameters parameters, Boolean randomKeyContainer)
   at System.Security.Cryptography.RSACryptoServiceProvider.get_SafeProvHandle()
   at System.Security.Cryptography.RSACryptoServiceProvider.get_SafeKeyHandle()
   at System.Security.Cryptography.RSACryptoServiceProvider..ctor(Int32 keySize, CspParameters parameters, Boolean useDefaultKeySize)
   at System.Security.Cryptography.X509Certificates.CertificatePal.<>c.<GetRSAPrivateKey>b__66_0(CspParameters csp)
   at System.Security.Cryptography.X509Certificates.CertificatePal.GetPrivateKey[T](Func`2 createCsp, Func`2 createCng)
   at System.Security.Cryptography.X509Certificates.CertificateExtensionsCommon.GetPrivateKey[T](X509Certificate2 certificate, Predicate`1 matchesConstraints)
   at Microsoft.Identity.Client.PlatformsCommon.Shared.CommonCryptographyManager.SignWithCertificate(String message, X509Certificate2 certificate)
   at Microsoft.Identity.Client.Internal.JsonWebToken.Sign(X509Certificate2 certificate, String base64EncodedThumbprint, Boolean sendX5C)
   at Microsoft.Identity.Client.Internal.ClientCredential.CertificateAndClaimsClientCredential.AddConfidentialClientParametersAsync(OAuth2Client oAuth2Client, ILoggerAdapter logger, ICryptographyManager cryptographyManager, String clientId, String tokenEndpoint, Boolean sendX5C, CancellationToken cancellationToken)
   at Microsoft.Identity.Client.OAuth2.TokenClient.AddBodyParamsAndHeadersAsync(IDictionary`2 additionalBodyParameters, String scopes, CancellationToken cancellationToken)
   at Microsoft.Identity.Client.OAuth2.TokenClient.SendTokenRequestAsync(IDictionary`2 additionalBodyParameters, String scopeOverride, String tokenEndpointOverride, CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.FetchNewAccessTokenAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.ClientCredentialRequest.ExecuteAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.Internal.Requests.RequestBase.RunAsync(CancellationToken cancellationToken)
   at Microsoft.Identity.Client.ApiConfig.Executors.ConfidentialClientExecutor.ExecuteAsync(AcquireTokenCommonParameters commonParameters, AcquireTokenForClientParameters clientParameters, CancellationToken cancellationToken)
   at Microsoft.Exchange.Management.AdminApiProvider.Authentication.MSALTokenProvider.GetAccessTokenAsync(String claims, String cmdletId)

Now, try to get rid of this Error. The Microsoft Developer had no idea how to handle it.
Wouldn't minimal decency demand that M$ hire professional engineers, at least for critical software, who have a little more than a few weeks of software engineering and basic ChatGPT knowhow and have mastered the advanced software engineering.
Thanks a lot, kind regards,
Thomas

@schittli, are you using the current version of the module (v3.1.0)? If so, try using the latest Preview version of the module (v3.2.0-Preview2) to see if that helps.
Connect-IPPSSession isn't as far along/mature as Connect-ExchangeOnline regarding CBA or the eventual support for REST-based connections.
And, we fix documentation here. I don't see anything documentation-related in your opening statement.

@schittli Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[BE] Nodemailer e-mail verification

Hi Younghyun, great job on developing e-mail verification process using Nodemailer.
I just got an e-mail to confirm my email address, and it's working!! 👍👍👍
However, I was thinking that we could provide a better customer experience if we could provide them with a hyperlink, instead of just text of link.
This is the email I received:

In addition, while I was looking at the BE code, came up with few suggestions as following:

Place http://localhost:3000 in BE .env, so that we could replace this easily when we go on to actual production url.

Since the verification code is repeating on both login and register controllers in auth.js,
why don't we make it into a reusable function? It will be a good choice for code maintenance.

Thank you for your suggestions. I will consolidate those two functions into one and use it inside both the register and login functions.


about vlc npapi  not smooth and not load in extra-plugin-dirs

i want play .mov  and do with vlc plugin
one of my video file  it work perfectly in chrome and nw.js
this video in atom-shell not smooth
and on widows the npapi only can load in registry,not load in extra-plugin-dirs

use vlc npapi plugin 2.2 not smooth,but use vlc 2.1.5 it work perfectly

NPAPI support is going to be disabled after we upgraded to Chrome 42 and removed after Chrome 45, so we will not fix bugs with NPAPI plugins.
I'm closing this as won't fix.


Invalid output for Prometheus by default_metrics

Some values from enable_default_metrics() may have suffix ULL for long numbers and Prometheus doesn't recognize it.
Quick solution:
local ret = prometheus.collect_http(req)
ret.body = ret.body:gsub("ULL", "")

Fixed by #23


Add package pinning to straight-x.el.

Dear @raxod502 ,
in reply to your comment in this issue I would like to ask for inclusion of my temporary solution for package pinning.
I have updated the code to work with the changes introduced by commit c42edf91249a3610a872402082e977c61cf65dc9 and written a short tutorial on how to use it.
I hope the code's quality is good enough for inclusion. If you require any changes please let me know and I will try to take care of them.

It looks great to me. Only problem is the Travis build (which should be linked here, but isn't for some reason): https://travis-ci.org/raxod502/straight.el/jobs/534460538
I think the solution to the error there would be to include a (defvar straight-x-pinned-packages) to satisfy the byte-compiler. (Or just define the variable in straight-x.el directly.)

Thanks for your contribution.

Thank you for creating straight :-)


Sort the display of build_artifacts

This is useful if you have a long list of artifact files.
This one's for you, @dlubarov.

Nice! 👍


feat: save configuration on invocation

Closes #25
TODO

[x] add coverage tests
[x] implement more format dumpers (not implementing dotenv or ini yet because it's unclear how)
[x] improve documentation on conf dumpers

@ezhang7423 let me know if this satisfies your request. In particular, see docs/examples/extras.md for an example. And thanks again for the kind words!

Just one other thing: it seems that we don't currently support Enum here, which would be nice to do. Here's a minimal reproduction:
from enum import Enum
from typing import Annotated
import typer
from typer_config import json_conf_callback
from typer_config.extras.commands import save_config
from typer_config.extras.dumpers import json_dumper

app = typer.Typer()

@app.command()
@save_config(json_dumper, "./saved.json") # MUST BE AFTER app.command() (2)
def main(
    algorithm: Annotated[
        Enum("Algorithm", {'a': 'a', 'b': 'b', 'c': 'c'}),
        typer.Argument(
            help="Specify algorithm to run. Find all supported algorithms in ./cfpi/variants/SUPPORTED_ALGORITHMS.py",
            autocompletion=lambda: ['a', 'b', 'c'],
        ),
    ],
    config: str = typer.Option(
        "",
        callback=json_conf_callback,
        is_eager=True,  # THIS IS REALLY IMPORTANT (1)
    ),
    opt1: str = typer.Option(...),
    opt2: str = typer.Option("hello"),
):
    typer.echo(f"{opt1} {opt2} {algorithm}")

if __name__ == "__main__":
    app()

Output

I'm pausing work on this in favor of #34

Just one other thing: it seems that we don't currently support Enum here, which would be nice to do.

See https://github.com/maxb2/typer-config/pull/27/commits/3df1bc53ade6b0d4bf7c0953146bd2ca9a7ff949 for a fix.


Request for support for Sylvania/Osram Lightify Smart Switch

Hopefully you don't mind the request. Apologies if I'm over sharing here, but I wanted to make sure you have what you need. Information obtained from debug log in Home Assistant after pairing. Thanks!
2019-02-24 21:41:22 INFO (MainThread) [homeassistant.components.zha.api] Permitting joins for 60s
2019-02-24 21:41:25 INFO (MainThread) [zigpy.application] Device 0xc2ff (00:0d:6f:00:0e:c8:ff:33) joined the network
2019-02-24 21:41:25 INFO (MainThread) [zigpy.device] [0xc2ff] Discovering endpoints
2019-02-24 21:41:25 DEBUG (MainThread) [zigpy.zdo] [0xc2ff:zdo] ZDO request 0x0013: [49919, 00:0d:6f:00:0e:c8:ff:33, 128]
2019-02-24 21:41:26 INFO (MainThread) [zigpy.device] [0xc2ff] Discovered endpoints: [1, 2, 3, 4, 5, 6]
2019-02-24 21:41:26 INFO (MainThread) [zigpy.endpoint] [0xc2ff:1] Discovering endpoint information
2019-02-24 21:41:27 INFO (MainThread) [zigpy.endpoint] [0xc2ff:1] Discovered endpoint information: <SimpleDescriptor endpoint=1 profile=260 device_type=2064 device_version=2 input_clusters=[0, 1, 32, 4096, 64768] output_clusters=[3, 4, 5, 6, 8, 25, 768, 4096]>
2019-02-24 21:41:28 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:1] Manufacturer: OSRAM
2019-02-24 21:41:28 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:1] Model: Switch 4x-LIGHTIFY
2019-02-24 21:41:28 INFO (MainThread) [zigpy.endpoint] [0xc2ff:2] Discovering endpoint information
2019-02-24 21:41:29 INFO (MainThread) [zigpy.endpoint] [0xc2ff:2] Discovered endpoint information: <SimpleDescriptor endpoint=2 profile=260 device_type=2064 device_version=2 input_clusters=[0, 4096, 64768] output_clusters=[3, 4, 5, 6, 8, 768, 4096]>
2019-02-24 21:41:30 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:2] Manufacturer: OSRAM
2019-02-24 21:41:30 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:2] Model: Switch 4x-LIGHTIFY
2019-02-24 21:41:30 INFO (MainThread) [zigpy.endpoint] [0xc2ff:3] Discovering endpoint information
2019-02-24 21:41:31 INFO (MainThread) [zigpy.endpoint] [0xc2ff:3] Discovered endpoint information: <SimpleDescriptor endpoint=3 profile=260 device_type=2064 device_version=2 input_clusters=[0, 4096, 64768] output_clusters=[3, 4, 5, 6, 8, 768, 4096]>
2019-02-24 21:41:32 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:3] Manufacturer: OSRAM
2019-02-24 21:41:32 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:3] Model: Switch 4x-LIGHTIFY
2019-02-24 21:41:32 INFO (MainThread) [zigpy.endpoint] [0xc2ff:4] Discovering endpoint information
2019-02-24 21:41:33 INFO (MainThread) [zigpy.endpoint] [0xc2ff:4] Discovered endpoint information: <SimpleDescriptor endpoint=4 profile=260 device_type=2064 device_version=2 input_clusters=[0, 4096, 64768] output_clusters=[3, 4, 5, 6, 8, 768, 4096]>
2019-02-24 21:41:34 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:4] Manufacturer: OSRAM
2019-02-24 21:41:34 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:4] Model: Switch 4x-LIGHTIFY
2019-02-24 21:41:34 INFO (MainThread) [zigpy.endpoint] [0xc2ff:5] Discovering endpoint information
2019-02-24 21:41:35 INFO (MainThread) [zigpy.endpoint] [0xc2ff:5] Discovered endpoint information: <SimpleDescriptor endpoint=5 profile=260 device_type=2064 device_version=2 input_clusters=[0, 4096, 64768] output_clusters=[3, 4, 5, 6, 8, 768, 4096]>
2019-02-24 21:41:36 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:5] Manufacturer: OSRAM
2019-02-24 21:41:36 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:5] Model: Switch 4x-LIGHTIFY
2019-02-24 21:41:36 INFO (MainThread) [zigpy.endpoint] [0xc2ff:6] Discovering endpoint information
2019-02-24 21:41:37 INFO (MainThread) [zigpy.endpoint] [0xc2ff:6] Discovered endpoint information: <SimpleDescriptor endpoint=6 profile=260 device_type=2064 device_version=2 input_clusters=[0, 4096, 64768] output_clusters=[3, 4, 5, 6, 8, 768, 4096]>
2019-02-24 21:41:38 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:6] Manufacturer: OSRAM
2019-02-24 21:41:38 DEBUG (MainThread) [zigpy.endpoint] [0xc2ff:6] Model: Switch 4x-LIGHTIFY
2019-02-24 21:41:38 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zigpy.quirks.xiaomi.TemperatureHumiditySensor'>
2019-02-24 21:41:38 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2, 3]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:38 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zigpy.quirks.smartthings.SmartthingsTemperatureHumiditySensor'>
2019-02-24 21:41:38 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zigpy.quirks.kof.CeilingFan'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.3130.CentraLite3130'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.3300S.CentraLite3300S'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.3305S.CentraLite3305S'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.3315S.CentraLite3315S'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.3320.CentraLite3320'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.3326.CentraLite3326'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.centralite.motion.CentraLiteMotionSensor'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.netvox.z308e3ed.Z308E3ED'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.philips.rwl021.PhilipsRWL021'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.smartthings.tag_v4.SmartThingsTagV4'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_body_sensor.AqaraBodySensor'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_button.AqaraButton'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_cube.AqaraCube'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2, 3]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_leak_sensor.AqaraLeakSensor'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_open_close_sensor.AqaraOpenCloseSensor'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_temperature_humidity_sensor.AqaraTemperatureHumiditySensor'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1]) {1, 2, 3, 4, 5, 6}
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Considering <class 'zhaquirks.xiaomi.aqara_vibration_sensor.AqaraVibrationSensor'>
2019-02-24 21:41:39 DEBUG (MainThread) [zigpy.quirks] Fail because endpoint list mismatch: dict_keys([1, 2]) {1, 2, 3, 4, 5, 6}

There are two versions of this device seen in the wild. The European version is fairly easy to support. The US version, which your logs appear to be from, is particularly difficult and will require more reverse engineering of the device.

Bummer. I'm not much of a developer, but is there anything I can do to help?

@spencerhooks if this is pairing (looks like it pairs fine) you should see zha_events for these already without a quirk. Go to the event tool in the UI (introduced in .88) in HA and subscribe to zha_event. Then interact with the device. You should see events show up for each on/off and each level control action (dimming)

Ok, thanks. I'll try the event tool to see what I see. I had tried using the binary sensors to create automations, but they were't working - either not reliably or not at all depending on the button.

@spencerhooks This device doesn't conform to "zigbee standards". You'll find the top left button fires an "ON" event on Endpoint 1. And the bottom left button fires an "OFF" event on Endpoint 3.
The Top Right and Bottom Right buttons are indicated on Endpoints 2 and 4, respectively. But, without a proper quirks implementation, you'll see no event for these buttons at all.
Additionally, you may see odd behavior with this device. If Endpoints 1 and 3 are not bound to properly during the initialization (the device goes out of range or something during this process), the device will be joined to the network but the endpoints won't be bound. The default for this device, when the endpoints are not bound, is to turn OFF and ON ALL lights. So if you see all your other zigbee lights turning on and off, that's why.
I've been working on a device handler for this device for a few days now. Unfortunately, I can't find good documentation on Zigpy and I'm unable to find examples of other devices that operate the way this one does, so the development is slow going. Which is a shame because these devices are quite inexpensive, fairly attractive, and offer quite a bit of functionality.

@dlashua HA will get events for all occurrences of clusters 6 and 8 that are output clusters without a quirk. This device should be emitting events as is.

Have a link to amazon for this device? I’ll pick one up to experiment with too.

Here's where I ordered from: https://www.amazon.com/gp/product/B01M3OK6J7
I totally agree about the device being cheap, attractive, etc.

https://www.amazon.com/SYLVANIA-LIGHTIFY-Function-Gateway-Assistant/dp/B01M3OK6J7/ref=sr_1_2?keywords=sylvania+4+button&qid=1551118583&s=gateway&sr=8-2
When you get it and you try to pair, look at the model reported by the device. If it states "Switch 4x-LIGHTIFY" then you have the same one I do. If it states "Switch 4x EU-LIGHTIFY" then you have the much easier to support device that I can't seem to get my hands on.

I'm also having a hard time figuring out how to write a quirk for this device, because I've yet to find another quirk for a device like it to use as an example.
There are three ways to represent the device...

as four buttons that have no state and generate events to indicate when they are pressed, held, and released. With this method, HASS entities would be only a battery sensor. Everything else would be an event.

As something similar to the hue dimmer switch, but two of them. HASS would see two entities, plus a battery sensor. The left side of the device would be one entity (a binary sensor if done as the hue dimmer is) that can be "on" or "off" and has a brightness attribute. And the right side would be another entity just like it.

As LIGHTIFY intended it: the left side of the device controlling on and off, and the right side of the device controlling hue. With this, HASS would see two entities, a binary sensor with an on and off state, a brightness attribute and a hue attribute. The device handler would be responsible for keeping track of the brightness level and hue value and altering it with each button press/hold.

The trouble I'm having is with two things:

To create two entities (like option 2 above), I would need to combine data from two endpoints into a single entity. I have no idea what this looks like in quirks code. With each endpoint on the device ending up as an entity, as is, we see 6 entities (plus a battery sensor). One of those entities only ever turns on (never off). And another only turns off (never on).

How to get "Color" from zigpy.zcl.clusters.lighting to do whatever thing is needed to show as an entity in HASS.

@dlashua HA will get events for all occurrences of clusters 6 and 8 that are output clusters without a quirk. This device should be emitting events as is.

Yes... and, while it looks funny in HA, because of this, the top left and bottom left buttons are "usable", just weird. The top right and bottom right buttons, however, seem to report on cluster 0x0300 (decimal 768) (from what I've seen in other places).  Events don't seem to be emitted for it. So, either this doesn't happen without a quirk, or, the device doesn't report changes on thost clusters without preconfiguration. And performing that preconfiguration is another difficult point I'm having because I don't see any other devices needing this.

0x300/768 is the color cluster. Try adding EVENT_RELAY_CLUSTERS.append(zcl.clusters.lighting.Color.cluster_id) to  components/zha/core/gateway.py

Doing so causes HA to hang on start up. Despite having
logger:
  default: debug

There is no useful error message. Simply...
Feb 25 13:16:13 maverick systemd[1]: Started Home Assistant.

Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded input_boolean from homeassistant.components.input_boolean
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded timer from homeassistant.components.timer
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded cast from homeassistant.components.cast
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded logger from homeassistant.components.logger
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded updater from homeassistant.components.updater
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded xiaomi_aqara from homeassistant.components.xiaomi_aqara
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded input_number from homeassistant.components.input_number
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded openuv from homeassistant.components.openuv
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded notify from homeassistant.components.notify
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded recorder from homeassistant.components.recorder
...
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded camera from homeassistant.components.camera
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded alarm_control_panel from homeassistant.components.alarm_control_panel
Feb 25 13:16:15 maverick hass[21000]: 2019-02-25 13:16:15 INFO (MainThread) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
Feb 25 13:16:15 maverick hass[21000]: Config directory: /home/hass/run/homeassistant-config

And then it sits there... no more logs... and never fully starts.

And then it sits there... no more logs... and never fully starts.

Nevermind... I found a better place to add it in the file and it seems to start now. Since it was just setting a value, I assumed it was safe to add this line at the top of the file. It was not. :)

0x300/768 is the color cluster. Try adding EVENT_RELAY_CLUSTERS.append(zcl.clusters.lighting.Color.cluster_id) to components/zha/core/gateway.py

Thanks for taking a stab at it. Sadly, that didn't help.
The device doesn't respond well to the initializing process. Lots of network errors and it takes multiple "reconfigures" before I see that every bind and report command made it through at least once. But even once that's done, the right side buttons generate no attribute reports or change events that I can see.
Endpoints 1 and 3 control ALL lights until they are bound to the controller. Then they operate in an odd, but usable manner, both press and hold for each button. But the right side buttons may require some additional configuration before they will work. I don't have any lights that accept a binding to 0x0300/768, so I can't tell if they are controlling everything as well and the binding just didn't take or if there's something else.
Pairing this device with it's native controller (the Osram Lightify Hub) I can see those two buttons are "disabled" by default. I've tried enabling them there, but, when I pair the device back to ZHA it seems to go back to its original settings.
I'm guessing there are some manufacturer specific things that need to be done to bind the buttons to the controller. And a regular old "bind" isn't enough.

I’m gonna pick one up. I’ll let you know what I find out.

the device arrives Thursday... I'll see what I can do from a quirks perspective. That said, if anyone wants to be brave I have branches of the backend and frontend of HA in flight to support device binding:
backend: https://github.com/dmulcahey/home-assistant/tree/dm/zha-direct-binding
frontend:  https://github.com/dmulcahey/home-assistant-polymer/tree/dm/zha-direct-device-binding
This will let you directly pair the remote to lights and use it without quirks, events or automations

@dlashua HA will get events for all occurrences of clusters 6 and 8 that are output clusters without a quirk. This device should be emitting events as is.

Yes... and, while it looks funny in HA, because of this, the top left and bottom left buttons are "usable", just weird. The top right and bottom right buttons, however, seem to report on cluster 0x0300 (decimal 768) (from what I've seen in other places). Events don't seem to be emitted for it. So, either this doesn't happen without a quirk, or, the device doesn't report changes on thost clusters without preconfiguration. And performing that preconfiguration is another difficult point I'm having because I don't see any other devices needing this.

the color clusters don't report at all... the device is kinda wacky. Binding is the way to go for this. It is already merged to dev. Closing because there is nothing useful that can really be done.

Thanks for picking up the device to take a look.
 ZHA configuration?

The config panel in the UI

Got it. Thanks again!

Sorry to ping a closed thread, but I noticed "zhaquirks/osram/lightifyx4.py" was added a few days after this was closed and wondered if that meant this device should be supported after all?
FWIW, I have purchased one, and it's assigned the
zhaquirks.osram.lightifyx4.LightifyX4 quirk in HA, but doesn't work as expected--6 binary_sensors are added as "device_class: opening" and clicking any of the 4 buttons turns the first sensor to on/open and then it just stays like that. Any further presses, holds, etc. don't change any other states, or that first state back to off.

It was an experiment. Binding is the best way to use this.

Bummer... I was hoping to use it to manually trigger non-zha automations in HA.
Thanks for all the work anyway!

It was an experiment. Binding is the best way to use this.

What do you mean by binding?

Also, not sure which config panel I'm looking for. I can't get it ZHA to add the device.

I am able to bind the Lightify 4x switch with a device. Seems like only the buttons on the left side do anything though. Single press top and bottom buttons turns the bound device on and off. Holding top and bottom fades up and down respectively. I can't get buttons on the right size to do anything though. Any thoughts?

I am able to bind the Lightify 4x switch with a device. Seems like only the buttons on the left side do anything though. Single press top and bottom buttons turns the bound device on and off. Holding top and bottom fades up and down respectively. I can't get buttons on the right size to do anything though. Any thoughts?

I can't even get the Lightify 4x switch to bind to anything it fails in the attempt according to my log, I have the switch added to ZHA and the left side reports events for tap and for hold which seems to be the norm that the right side switches don't work with this implementation. Means it's half functional to me which isn't too bad given the super low price but it's a shame that the right side doesn't behave too.
2019-07-17 14:36:41 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140114964268200] Error handling message: Unknown error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 17, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/homeassistant/homeassistant/components/zha/api.py", line 386, in websocket_bind_devices
    zha_gateway, source_ieee, target_ieee, BIND_REQUEST)
  File "/usr/src/homeassistant/homeassistant/components/zha/api.py", line 447, in async_binding_operation
    await asyncio.gather(*bind_tasks)
  File "/usr/local/lib/python3.7/site-packages/zigpy/device.py", line 147, in request
    expect_reply=expect_reply,
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 365, in request
    res = await asyncio.wait_for(req.send, timeout=APS_ACK_TIMEOUT)
  File "/usr/local/lib/python3.7/asyncio/tasks.py", line 416, in wait_for
    return fut.result()
zigpy.exceptions.DeliveryError: [0xe405:0:0x0021]: message send failure: EmberStatus.DELIVERY_FAILED


Include grafana config.ini as a ConfigMap

Currently the config.ini is a part of the docker build. Its easy enough to add a config.ini configmap and override, but I was curious if this would be useful as default functionality to anyone else?
Happy to implement if so, if not, feel free to close!

If you are using the jsonnet based stack see here: https://github.com/brancz/kubernetes-grafana/blob/master/README.md#config-customization

I see it as a really good enhancement.
One use case would be creating the ini ConfigMap using Terraform.

As @brancz pointed out this would either be something for kubernetes-grafana or now kube-prometheus.
Please use these repositories going forward as this repo doesn't contain anything related to Grafana anymoer.


Upload vela core chart to alibaba cloud oss for every release and master commit

AccessKey was added as Github secret and it has only permission to write the specified oss bucket.
Users will be able to use it by:

Add repo

helm repo add kubevela https://kubevelacharts.oss-cn-hangzhou.aliyuncs.com/core

Update repo

helm repo update

Search version

helm search repo kubevela

Install

helm install kubevela kubevela/vela-core

Install with latest master branch:

helm install kubevela  https://kubevelacharts.oss-cn-hangzhou.aliyuncs.com/core/vela-core-latest.tgz

first part of #942

first part of #942


fix: create results from options

This PR changes how we create QueryResults. By always creating them from a given BaseOption we're effectively preserving type information. Losing type context has been the cause of two issues, latest #1072.
Since this PR changes the signature of the QueryResult which would warrant a major release if we had a better split of releases. This will cause issues for our beta users. The instruction should be to keep the packages in sync. Again, this is a major argument for persuing split releases.

@vincenzopalazzo, with the breaking change mentioned above the current CI will always fail because some are using melos bootstrap and others aren't. What are your thoughts on this?

@vincenzopalazzo, with the breaking change mentioned above the current CI will always fail because some are using melos bootstrap and others aren't. What are your thoughts on this?

I will look into the error today, sorry for delay!

We're running into a type issue that I believe is from this change:

@apackin
The version that you are using? In addition, a new issue with a good description of the problem can be very helpful, debugging in a screenshot is always frustrating for me, sorry!


Another forum test...

Home Assistant release with the issue:

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

Turns out this only works for commits and PRs. Oopsies.


not detecting words

I looked up the word 搾取する and it came up exactly like that in the ocr but it only detects the first kanji. also I dont see a way to copy the whole text to clipboard.

Can you elaborate a bit more? I'm able to get the lookup for 搾取 just fine, in both instant mode and normal mode:

Can you try joining the beta in the Play Store and see if it's still an issue in the beta version? The beta version has quite a few bugfixes that the public version does not.

hmm I tried it a gain today and it works.


Fix CI E2E ionic tests flakyness

Ionic E2E tests are randomly failing on CI, this should be investigated as it's really annoying 😭

Seems that with the v7 release, the problem solved itself! 🎉


XPLR-HPG-2 The black board

Hi,
I have an HPG-2 black board and I have a problem that the cellular module keeps resetting. I read in one of the manuals it is a normal behavior apparently. But, the problem is that I cannot implement the cellular example "Achieving High Precision GNSS via correction data taken from Thingstream, using Cellular.(case 2)". I don't have any issue with the HPG-2 green board executing this example.
All the best,
Reza Heydarian.

Hi there,
If you use the black board, you have to change the board config to MAZGCH (different PCB routing). See https://github.com/u-blox/XPLR-HPG-software/issues/3#issuecomment-1628597707

Also, beware that CEL examples may be broken, see https://github.com/u-blox/XPLR-HPG-software/issues/2

After changing the board config to the MAZGCH it worked. Thank you. But is it mentioned somewhere in some of our manuals?

Great.
It should be already mentioned in the READMEs of the different examples, like this one. Maybe it's mentioned in all, could be the case

Even in the link you sent I can't find any  information related changing the board config to MAZGCH. It says that select the board you wish to build your example for. But how can I find out which choice is the right one. In which document can I find this info?

The example README I provided mentions the changes you have to make to the KConfig, in order to run the example (different KConfig settings for different examples typically). Which assumes that the user goes through the README to make an example work (and part of the instructions is to make sure the board used is correct).
Probably this is not enough. Open to suggestions on where to put such information, so other users are helped as well

Maybe only a hint would be sufficient in the building instruction section, under step 6, something like this:
For HPG-2 black boards, set board options to "MAZGCH HPG SOLUTION (NINA-W106)"
For HPG-2 green boards, set board options to "XPLR HPG2 C214 (NINA-W106)"
would help a lot. This is just a suggestion, but something along these lines. Because I have tried to follow our manuals and I haven't found any information there related to choosing target board to MAZGCH anywhere. Maybe there is somewhere, but I haven't found it.

In the Readme of this example.

Here you mean?

exactly

Issue resolved and ticket is closed


[IA-3175] Use googleProject when a disk doesn't have workspace namespace defined

The last PRs missed the corner case where a disk does not have workspace namespace  defined but does have workspace name defined.
Currently in this scenario, Cloud Environments page gives the error below:

With this fix, we'll get the expected page view

Reproduced the issue and by manually updating Leonardo's dev LABEL table and verified the fix on a local deployment.

Will merge despite the integration test failure because

The integration test failure has the known signature of

which is worked on via #2781 .

The change in this PR is very unrelated to the failing test.

Prod bug this PR fixes has the potential to break Cloud Environments page for users.


Prefferable way to Override/append onChange event on Field

Hi, first thanks for this amazing component!
I am struggeling a bit with how to best append/override the onChange event on the Field component. What is the best practices here?
I am still quite new to react and very new to redux so still trying to grasp the redux way of thinking, please keep this in mind of my question is trivial.
So, to put it very simple, I am having 2 selects where one will dispatch an action fetching new data through ajax, which the other select will render. I therefore need to pass some extra stuff happening to the onChange event for one of the dropdowns.
I've spent quite some hours investigating best approach for this but found older stuff mostly (this for instance; #624). Prefferable I would like to use the Field component doing this as its quite neat.
So far I've come up with this solution;
<Field
  name="category"
  component="select"
  className="form-control"
  disabled={this.props.categories.length === 0}
  props={{
    onChange: (e) => {
      this.props.change('category', e.target.value)
      this.props.handleCategoryChange(e)
    }
  }}
>
  <option value="">Select Category</option>
  {this.props.categories.map(option => <option value={option.id} key={option.id}>{option.name}    </option>)}
</Field>

The handleCategoryChange function is passed from the containerComponent of the form and dispatches the required action.
This seems to work as intended, but as I am very new to redux and to redux-form I would appreciate to know if there is a better way dealing with this?
Feedback and input on this would be very appreciated.

I believe this was fixed by https://github.com/erikras/redux-form/pull/2385, you can now pass onChange to the <Field /> and it will be called on the change event prior to the redux-form input.onChange prop.

Thanks for the heads up, @Limess!

Out of curiosity, is the input.onChange prop still called even if you specify onChange={myOnChange}?

Hi @ntomallen, yes, it should, unless you call evt.preventDefault()


dxemulate / peimulate

A simple thing to hook up with the UI once there:

click on a button on a DXE/PEIM
reassemble an OVMF image, inserting the binary
run it in QEMU, use its monitor to watch register/port/memory access
bonus: add monitoring to OVMF checking on PPI, HII etc

See also
https://edk2-docs.gitbook.io/edk-ii-module-writer-s-guide/7_pre-efi_initialization_modules/75_communicate_between_peim_modules#7-5-2-hob
and
https://reverse.put.as/2019/10/29/crafting-an-efi-emulator/
and
https://edk2.groups.io/g/discuss/message/76

also have a glance at
https://software.intel.com/content/dam/develop/external/us/en/documents/a-tour-beyond-bios-launching-vmm-in-efi-developer-kit-ii-0-819978.pdf

see also #73 and #5


Request: Programmatically Change idle-time-limit

Use Case: I have a video embedded on a page in my app, and I have a button that lets user toggle between a preset idle time out and no idle timeout to give users the option to watch a truncated copy of the video or one in real time. Unfortunately, this requires re-loading the page to reset the idle-time-limit value on the DOM element.

Nice idea although not a very common use-case. It also brings more questions, e.g. how should the translation of current time work when switching back and forth between limit/no-limit.


Slow table update with 200+ rows

Hello,
I'm displaying 200 rows / 16 columns per page and table updates very slow.
It takes about 2-3 seconds to update the table when I'm calling 'vuetable:refresh'.
Is there any way to make it faster?
Any way to use track-by with v-for?
I need refresh the table every 5-10s, and its really annoying that it takes 2-3-4s to rerender the table.

@dominikveils I'm afraid it can't be run any faster. Due to that many rows of data (and columns), there will be a lot of data for Vue.js to track and I guess track-by wouldn't help either. Even if you do not use callbacks to format your data, the rendering will still be slow because of the real time template rendering and vuetable template is also quite complex. In my opinion, it might be faster if you render your table manually without using vuetable because it might be more suitable in your use case.

Just wanted to add to @dominikveils so you don't waste time on this.
ratiw is right, I've been trying to build a table editor that use Semantic UI for styling and it's not much slower than using standard tables (~10% slowdown at most).
Your only bet here is to use vanilla JS but even if you do, you could only get about double the speed of Vue.js (Vue overhead is 1.92 in latest benchmarks) if you work really hard at it.
You can check and edit this benchmark to see how fast your script can become (in theory).
http://mathieuancelin.github.io/js-repaint-perfs/


Add proxy support to the go client

Adds proxy support to the go client including the ability to disable cert pinning. The general strategy for the proxy support is setting the HTTP_PROXY and HTTPS_PROXY environment variables such that golang's http library will automatically configure the proxy. Note that despite the names of these variables, golang does support socks5 proxies via this method. This PR:

Adds HTTP Connect proxy support
Adds socks5 proxy support
Adds the ability to disable certificate pinning via switching the domain to keybase.io
Refactors the current tor support to reuse the socks5 proxy support and remove the dependency on h12.me/socks

Currently, all of this functionality is only exposed through config.json, CLI flags, and environment variables. I will open another PR in the future to add a UI component that allows configuring proxies.
All of the code is tested with unit tests. I tested HTTP proxy support via squid and socks5 proxy support via microsocks (including testing username/password auth for each). I used burp suite as an example of a proxy that does TLS MITM.

Please let me look at this before merge

Pending CI


7zz: 21.01 -> 21.02

Motivation for this change
Also build from source instead of using the binaries.
We cannot (yet) build the fully optimized version as it requires the
ASMC assembler which currently doesn't build with GCC.

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

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

1 package built:

_7zz

For context: https://github.com/NixOS/nixpkgs/pull/116054

The source hasn't been released yet, so I'm fetching and patching binaries for now. When the source is released, I will be building it natively.

Result of nixpkgs-review pr 145031 run on aarch64-linux 1

1 package built:

_7zz

Code-wise LGTM.
Please squash the commits before mergin.

Please squash the commits.

I'll do "Squash and Merge" when @anna328p ACKs it.

Will review this tomorrow morning.

⬇ Suggested change

install -Dm444 -t $out/share/doc/${pname} ../../../../DOC/*.txt

install -Dm444 -t $out/share/doc/7zz ../../../../DOC/*.txt

Why? If the pname changes, we're likely to want the directory to change too.

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

1 package built:

_7zz


Data Set Menus

Menus for data sets are not present in V3+, e.g. https://v3.datadictionary.nhs.uk/web_site_content/cds_supporting_information/commissioning_data_set_version_6-3_type_list.asp?shownav=1.
We need to understand how to recreate these in Mauro.

This is a combination of this ticket, #63 and #130.
Other tickets to be closed.
We should be able to set the menu in the data set folder when we have migrated to Mauro.
This relates to data sets with their own menus, e.g. CDS, COSDS.

16/05/22 - work completed by James. Ticket moved.

Tested in Mauro and the Orchestrator


Error with ver 1.6.0

Hi,
When I use query: "_search?size=10&from=0&pretty&xml" or curl -H 'Accept: application/xml' '_search?pretty'
The error message appear:
Could not initialize class org.xbib.elasticsearch.common.xcontent.xml.XmlXContent

Can you try version <IP_ADDRESS> ?


Save network state by using https://capacitorjs.com/docs/apis/network

[ ] When offline - save a network state to the capacitor storage
[ ] When online

[ ] Save not saved data from capacitor storage
[ ] Save a network state to the capacitor storage

Deep types for every connection type must be created and used
https://capacitorjs.com/docs/apis/network

.env
NEXT_PUBLIC_GQL_PATH=<gql-client-path>/gql
NEXT_PUBLIC_GQL_SSL=0/1 for local/remote

Make sure to use nodejs version 14.15.0
npm ci

npm run dev -- -p 4000

Use

1) INITIALIZE PACKAGE.
Also creates Network container link inside current device link.
2) LISTEN TO NETWORK CHANGES.
Fires capacitor/network Network event listener. Listens to network changes.
Stores them as string values inside localstore. Uploads as links values inside Network link container if possible.
"none" - airplane mode
"wifi" - wifi
"cellular" - mobile network
"unknown" -actually unknown for me, cant figure out what to do to emit this event.
You can emit events by turning these connection types on and off inside settings overlay on your phone.
A good idea would be connecting your phone to android studio by usb cable and wrap it with aluminium foil to simulate network loss and still be able to watch debug logs where this event can be seen clearly.
3) SAVE CURRENT STATUS.
Saves current network type and status as link value.


Azure CLI parameter "--nat-gateway null" option does not work for az network vnet subnet update command

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Related command
az network vnet subnet update
Describe the bug
In the CLI doc for https://learn.microsoft.com/en-us/cli/azure/network/vnet/subnet?view=azure-cli-latest#az-network-vnet-subnet-update
the description for the --nat-gateway parameter says that you can remove the NAT gateway resource from the subnet by using 'null' on the parameter.
From doc:
"--nat-gateway
Name or ID of a NAT gateway to attach. Use null to detach it."
However, when I use "null" on the --nat-gateway parameter, I get the following error:
(InvalidRequestFormat) Cannot parse the request.
Code: InvalidRequestFormat
Message: Cannot parse the request.
Exception Details:      (MissingJsonReferenceId) Value for reference id is missing. Path properties.natGateway.
Code: MissingJsonReferenceId
Message: Value for reference id is missing. Path properties.natGateway.
I found that you can use the --remove parameter though to remove the NAT gateway. It appears that the "null" option for the --nat-gateway parameter is just a documentation error.
I would like to request that the part of the --nat-gateway parmeter description that says "Use null to detach it." be removed from the public doc.
To Reproduce
Run the following commands to remove the NAT gateway resource from the subnet
This method to remove the NAT gateway from the subnet DOES NOT work
aimee [ ~ ]$ az network vnet subnet update -g aimeeGroup_rg -n mySubnet --vnet-name myVNet --nat-gateway null
This method to remove the NAT gateway from the subnet DOES work:
aimee [ ~ ]$ az network vnet subnet update -g aimeeGroup_rg -n mySubnet --vnet-name myVNet --remove nat_gateway
Note can also say --remove natGateway to remove it from the subnet. Should there only be one type of iteration of the nat gateway property that can be used to remove from the subnet?
Expected behavior
Environment summary
Additional context
This ask comes on behalf of CSS due to a customer reported incident.

Thank you for opening this issue, we will look into it.

@necusjz when should I expect for "null" to work on the --nat-gateway parameter? I just tried testing it and I got the same error message as before:

https://github.com/Azure/azure-cli/milestone/130


Feature Request: [Cards] Medium and Large Sizes

I'm trying to display people for my reveal cards. It'd be nice to have cards for medium and large too

Very true. We will add this, but in the meantime you can set height
yourself to achieve the effect
On Feb 1, 2015 8:57 AM, "jett0423"<EMAIL_ADDRESS>wrote:

I'm trying to display people for my reveal cards. It'd be nice to have
cards for medium and large too
[image: issue card]
https://cloud.githubusercontent.com/assets/10791201/5992263/9fe09566-aa5c-11e4-8461-7a56e864c4ad.PNG
—
Reply to this email directly or view it on GitHub
https://github.com/Dogfalo/materialize/issues/583.

okay. thanks for the heads up!

It is better to leave this open so we don't forget to add this

oops! sorry. I'm new here. thanks for correcting :)

Added in ebe13c2835e631a3c801bbcb8d666691b732e88b

Hi! I'm opening this up again for a bug I found with the reveal cards.

I think the issue's more on cropping the image and scaling its height based on each size for the card.


View disappear action is not triggered when the view is disappeared

Description
We have code in the view:
.onDisappear {
store.send(.viewDisappeared)
}
But viewDisappeared action is not triggered when the view is unloaded.
Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
The .viewDisappeared action should be triggered.
Actual behavior
The .viewDisappeared action is not triggered.
Reproducing project
ResourceCleanup 2.zip
The Composable Architecture version information
1.16.1
Destination operating system
iOS 18
Xcode version information
XCode 16.1
Swift Compiler version information
No response

Hi @johnqiang-cao, this is to be expected, and there is even a purple runtime displaying in Xcode letting you know what you are doing isn't correct:

🟣 A "forEach" at "ComposableArchitecture/CaseReducer.swift:52" received an action for a missing element. …
Action:
ContentFeature.Path.Action.child(.viewDisappeared)
This is generally considered an application logic error, and can happen for a few reasons:

You cannot send an action in the onDisappear of a view because by the time that view modifier is invoked the feature's state has been nil'd out, and hence the reducer for the child feature cannot even be run.
What is it you are wanting to do in the onDisappear of the view?
If you really need to do this, you can always add it inside the navigationDestination:
} destination: { destination in
  switch destination.case {
  case .child(let childStore):
    ChildView(store: childStore)
      .onDisappear { store.send(.onChildDisappear…) }
  }
}

Since this isn't an issue with the library I am going to convert it to a discussion. Please feel free to continue the conversation over there!


Add an entry for image example in Cargo.toml

Examples should be explicitly listed because of #17, but image example
added by #62 was not described in Cargo.toml.

Thanks!


Not effective when working with vee-validate

Describe the bug
Hi, I'm using pinia-plugin-persistedstate together with vee-validate, but it fails and the persistence doesn't work.
Reproduction
https://stackblitz.com/edit/vitejs-vite-cma2ui?file=src%2Fstores.ts
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.3 - /usr/local/bin/pnpm

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible of the bug.

I think the way variables are exposed by the vee validate composable are not parsed as proper "state" by pinia, and therefore ignored by the persistence plugin.
I will try to investigate a bit more and look for the root cause of this issue.


formula_auditor: delete adoptopenjdk condition

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

delete the check whether alias_name_major_minor is<EMAIL_ADDRESS>because adoptopenjdk is a cask and alias_name_major_minor will not be<EMAIL_ADDRESS>.
brew search adoptopenjdk
==> Casks
adoptopenjdk

Thanks again @hyuraku!

Thanks again @hyuraku!


Create jest reporter clinical

Test PR for TerraVerboseReporter

@sirishaNekkanti terra-toolkit has been released with the Jest Reporter. Can we clean this PR up to add the Reporter config t this repo?


Can't compile

aws ec2 redhat, rust 1.8
output Compiling rusoto v0.12.1
warning failed to run custom build command for `rusoto v0.12.1`
warning Process didn't exit successfully: `/home/ec2-user/u/target/release/build/rusoto-cb6663223441b666/build-script-build` (exit code: 101)
warning --- stdout
warning Traceback (most recent call last):
warning File "codegen/botocore_parser.py", line 5, in <module>
warning from queryprotocol import QueryProtocolParser
warning File "/home/ec2-user/.cargo/registry/src/github.com-88ac128001ac3a9a/rusoto-0.12.1/codegen/queryprotocol.py", line 1, in <module>
warning from parserbase import ParserBase
warning File "/home/ec2-user/.cargo/registry/src/github.com-88ac128001ac3a9a/rusoto-0.12.1/codegen/parserbase.py", line 2, in <module>
warning from html2text import html2text
warning ImportError: No module named html2text
warning
warning
warning --- stderr

please write in the documentation about dependencies

Yeah, this is pretty broken right now. Sorry! That problem will go away in the next release, which will include the code generation revamp in #201!

In the meantime, instructions here might help: https://github.com/rusoto/rusoto/blob/master/CONTRIBUTING.md .

FYI, this is now fixed on master. No crates.io release yet, cause we still have a few more changes to land, but it's coming soon.

I think we've sorted out the blockers for a crate release, this should be fixed on the new crate soon!

Version 0.13.0 of Rusoto is all Rust, all the time.  This issue is fixed!

thank you!


New task to upgrade all dependencies to a given minimum stability level

By default, it'd only upgrade keeping the existing stability level.
We still need to figure out how to handle concurrent dev and alpha versions (like used in Splitties where the plugin can't currently detect the updates).
A solution might be to request a dedicated API in Gradle, assuming that it can give fast results.
Another one would be to do it ourselves, fetching, and caching, per-artifact timestamp, and use that when multiple repositories return different versions (like for Splitties, Kotlin, others, and all libraries distributing snapshots).

To suit real-world use cases, we'd need to allow customizing the behavior per version (opt-out a version key, add stability level constraints, and/or minimum version…).


No information displayed for one of my systems, unicode error

Hi, I was just trying Healthstone out to monitor a couple of servers and found that one of them doesn't display any info or graph if I click the status.
The dashboard is running on Linux with apache 2.4.20 and python 3.5.2.  The error shown in the apache logs is
AH01215: Traceback (most recent call last):: /var/www/example.com/healthstone/dashboard.py, referer: https://example.com/healthstone/
AH01215:   File "/var/www/example.com/healthstone/dashboard.py", line 222, in <module>: /var/www/example.com/healthstone/dashboard.py, referer: https://example.com/healthstone/
AH01215:     print("

" + time.strftime("%Y/%m/%d %H:%M:%S", time.localtime(row[6])) + "" + row[1] + " (" + row[0] + ")

System Profile

" + row[5] + "

"): /var/www/example.com/healthstone/dashboard.py, referer: https://example.com/healthstone/
AH01215: UnicodeEncodeError: 'ascii' codec can't encode character '\\xae' in position 248: ordinal not in range(128): /var/www/example.com/healthstone/dashboard.py, referer: https://example.com/healthstone/

The 2 systems are a Windows server 2008 R2 which shows up fine, and a Windows SBS2011 server which doesn't.
The problem is caused by the (R) symbol in its description "Microsoft Windows® Small Business Server 2011 Standard  (64-bit)"
On a slightly unrelated note, Healthstone doesn't seem to be able to get windows update info on SBS2011 either
--> [CheckUpdates] Registry query failure: System.NullReferenceException: Object reference not set to an instance of an object.
   at Healthstone.Program.ParseSections(Object sender, ElapsedEventArgs hse)
[CheckLUsers] Local users:

The first is a Python issue. You need to tell Apache to use unicode with Python scripts. Try adding this to your Apache config:
AddDefaultCharset UTF-8
SetEnv PYTHONIOENCODING utf8

The second issue is now fixed in 2.0.1

Thanks!
I added those 2 lines to the .htaccess file in the healthstone/www directory and it is fixed.


New release (python:python:2.7.15) available! (Herald System)

This issue created programmatically and automatically by Heroku, on behalf of kennethreitz, the owner of the python buildpack.

@sigmavirus24 is working on this!


.bin files from PSI are not being converted correctly

I'll need to update the executable for this, luckily they had a great library that was easy to use (and  by library I mean two files, things are so much easier when you don't write your code in C). On the BRIGHT side I now have the opportunity to document how this is done.

As far as I can tell the files I downloaded to test on did not have histogram titles (which is what was missing and causing it to fail). So I guess I'll just give them numbers. Also, someone wrote a python wrapper for the PSI library a few months ago (it's a pretty small library) so I'll probably just use that and make beams easier to maintain.

Kind of jealous I didn't think to do that first, I might do that for the mud files after graduation 😂

Is there a  good way to guestimate the first and last bins for calculating background? Like,  first bin that isn't 0 to 5 bins before t0 maybe? These values are not included in the bin  or mdu files.

Strange that the background bins aren't provided. I would say a safe guess is 10% of the way to t0 to 90% of the way. We don't want to get to close to either endpoint, where things are often a bit strange.

I agree, this is a link to their documentation for the class you use to read the files. I couldn't see anything except methods where you pass IN the bckgrd bins. Tis weird.
http://lmu.web.psi.ch/docu/manuals/bulk_manuals/software/Class_MuSR_PSI/index.html

@benfrandsen typically the runs start with a section of zeroes which I assume would throw off the background calculation. What if we did 10% or when we get the first non-zero value, whichever comes later for the starting value.

Yes, we should definitely exclude any leading zeroes. Let's start 5% of the way from the first nonzero value.


HADOOP-18528. Disable readAhead/prefetching by default

Description of PR
Setting readAhead config to false by default.
How was this patch tested?
Region: us-west-2
mvn -Dparallel-tests=abfs -DtestsThreadCount=8 -Dscale clean verify
Seeing some timeout errors, going to test the latest ABFS trunk code to see the differences tomorrow.
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m  3s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 30s

trunk passed

+1 :green_heart:
compile
23m 33s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
20m 51s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 20s

trunk passed

+1 :green_heart:
mvnsite
3m 10s

trunk passed

+1 :green_heart:
javadoc
2m 26s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 15s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 34s

trunk passed

+1 :green_heart:
shadedclient
21m 49s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 38s

the patch passed

+1 :green_heart:
compile
22m 33s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
22m 33s

the patch passed

+1 :green_heart:
compile
20m 53s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 53s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m  1s

the patch passed

+1 :green_heart:
mvnsite
3m 19s

the patch passed

+1 :green_heart:
javadoc
2m 31s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
2m 23s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
4m 58s

the patch passed

+1 :green_heart:
shadedclient
22m  1s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 53s

hadoop-common in the patch passed.

+1 :green_heart:
unit
2m 51s

hadoop-azure in the patch passed.

+1 :green_heart:
asflicense
1m 19s

The patch does not generate ASF License warnings.

238m 48s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5134/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5134

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux 51930871d31a 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 3981da068628bf06906127408ea767ba27e0f582

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5134/1/testReport/

Max. process+thread count
3108 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-tools/hadoop-azure U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5134/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Okay, ran the test suite on trunk as well. There are no additional errors/failures after the changes, it's showing some errors on the base version.
[ERROR] testGetIsNamespaceEnabledWhenConfigIsTrue(org.apache.hadoop.fs.azurebfs.ITestGetNameSpaceEnabled)  Time elapsed: 3.876 s  <<< FAILURE!
org.junit.ComparisonFailure: [getIsNamespaceEnabled should return the value configured for fs.azure.test.namespace.enabled] expected:<[fals]e> but was:<[tru]e>
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

Not sure why this is a failure and not just skipping the test in case the config isn't set.
[ERROR] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 82.967 s <<< FAILURE! - in org.apache.hadoop.fs.azurebfs.ITestAzureBlobFileSystemLease
[ERROR] testTwoCreate(org.apache.hadoop.fs.azurebfs.ITestAzureBlobFileSystemLease)  Time elapsed: 6.501 s  <<< FAILURE!
java.lang.AssertionError:
 Expected to find 'There is currently a lease on the resource and no lease ID was specified in the request' but got unexpected exception: org.apache.hadoop.fs.PathIOException<EMAIL_ADDRESS>Input/output error: Parallel access to the create path detected. Failing request to honor single writer semantics
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.checkException(AzureBlobFileSystem.java:1500)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystem.create(AzureBlobFileSystem.java:331)
	at org.apache.hadoop.fs.FileSystem.create(FileSystem.java:1231)
...

Caused by: Parallel access to the create path detected. Failing request to honor single writer semantics
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.conditionalCreateOverwriteFile(AzureBlobFileSystemStore.java:652)
	at org.apache.hadoop.fs.azurebfs.AzureBlobFileSystemStore.createFile(AzureBlobFileSystemStore.java:563)

Seeing it fail as a stand-alone test as well.
[WARNING] Tests run: 48, Failures: 0, Errors: 0, Skipped: 24, Time elapsed: 396.823 s - in org.apache.hadoop.fs.azurebfs.ITestSmallWriteOptimization
[ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 725.369 s <<< FAILURE! - in org.apache.hadoop.fs.azurebfs.ITestAbfsReadWriteAndSeek
[ERROR] testReadAndWriteWithDifferentBufferSizesAndSeek[Size=104,857,600-readahead=true](org.apache.hadoop.fs.azurebfs.ITestAbfsReadWriteAndSeek)  Time elapsed: 670.478 s  <<< FAILURE!
org.junit.ComparisonFailure: [Retry was required due to issue on server side] expected:<[0]> but was:<[1]>
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

Intermittent failure, saw this in trunk once.
Also had a timeout error in ITestAbfsTerasort.

the lease one plays up on me, as does ITestSmallWriteOptimization; especially on parallel runs.  i'm not worried there


LICENSE

Dear all,
I am interested in this research and codes.
I have a question: What is the license corresponding this codes?
Best regards,
Vujadeyoon

Thanks for reminding. I have updated LICENSE in this repository.