g=\"clientid: 8496##### REDACTED #####e342\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"secrets store csi driver mounted host.json\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/8575be38-891a-4144-bdac-d4def12facbd/volumes/kube
rnetes.io~csi/csi-key-vault-func-secrets-svc-ppppp/mount\"\n"
time="2020-07-28T09:32:44Z" level=debug msg="[NodePublishVolume] syncK8sSecret is enabled for pod: 8575be38-891a-4144-bdac-d4def12facbd, ns: default"
time="2020-07-28T09:32:44Z" level=info msg="file matching objectName AzureWebJobsStorage found, processing key AzureWebJobsStorage for pod: 8575be38-891a-4144-bdac-d4def12facbd, ns: default"
time="2020-07-28T09:32:44Z" level=error msg="error from c.Get: secrets \"csi-func-secrets-svc-ppppp\" not found for secret: csi-func-secrets-svc-ppppp, ns: default"
time="2020-07-28T09:32:44Z" level=info msg="created k8s secret: csi-func-secrets-svc-jjjjj, ns: default"
time="2020-07-28T09:32:44Z" level=info msg="created k8s secret: csi-func-secrets-svc-kkk, ns: default"
time="2020-07-28T09:32:44Z" level=error msg="error from c.Get: secrets \"traefikcert-csi\" not found for secret: traefikcert-csi, ns: default"
time="2020-07-28T09:32:44Z" level=info msg="created k8s secret: csi-func-secrets-svc-stlmnt-imp, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 23391535-5bd9-4dd6-bd62-a08354f2dc0c, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="time=\"2020-07-28T09:31:22Z\" level=info msg=\"using pod identity to access keyvault\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"mounting secrets store object content for default/aaa-bbb-qryh-8f564cfb7-97wt2\"\ntime=\"20
20-07-28T09:31:22Z\" level=info msg=\"objects: array:\\n  - |\\n    objectName: AKS-AzureWebJobsStorage-svc-bbb\\n    objectAlias: AzureWebJobsStorage\\n    objectType: secret\\n  - |\\n    objectName: AKS-host-json-svc-bbb\\n    objectAlias: host.json\\n    objectType:
 secret\\n  - |\\n    objectName: jjjjjSvcEventHubConnectionString\\n    objectAlias: jjjjjSvc_EventHub_ConnectionString\\n    objectType: secret\\n  - |\\n    objectName: jjjjjSvcEventHubConnectionStringReplay\\n    objectAlias: jjjjjSvc_EventHub_ConnectionString_Repla
y\\n    objectType: secret\\n    \\n\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"unmarshaled keyVaultObjects: [{AKS-AzureWebJobsStorage-svc-bbb AzureWebJobsStorage  secret} {AKS-host-json-svc-bbb host.json  secret} {jjjjjSvcEventHubConnectionString jjjjjSvc_EventH
ub_ConnectionString  secret} {jjjjjSvcEventHubConnectionStringReplay jjjjjSvc_EventHub_ConnectionString_Replay  secret}]\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"keyVaultObjects len: 4\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"azure: using pod identity
to retrieve token\"\ntime=\"2020-07-28T09:32:40Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:40Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"secrets store csi dri
ver mounted AzureWebJobsStorage\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0547757-0b0d-41bf-b870-4cc03a487e63/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\
"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:44Z\" level=info
msg=\"secrets store csi driver mounted host.json\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0547757-0b0d-41bf-b870-4cc03a487e63/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\ntime=\"2020-07-28T09:32:44Z\"
 level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:
44Z\" level=info msg=\"secrets store csi driver mounted jjjjjSvc_EventHub_ConnectionString\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0547757-0b0d-41bf-b870-4cc03a487e63/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-
bbb/mount\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"clientid: 5924##### REDA
CTED #####6d12\"\ntime=\"2020-07-28T09:32:45Z\" level=info msg=\"secrets store csi driver mounted jjjjjSvc_EventHub_ConnectionString_Replay\"\ntime=\"2020-07-28T09:32:45Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0547757-0b0d-41bf-b870-4cc03a487e63/volumes/
kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\n"
time="2020-07-28T09:32:45Z" level=debug msg="[NodePublishVolume] syncK8sSecret is enabled for pod: d0547757-0b0d-41bf-b870-4cc03a487e63, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="file matching objectName AzureWebJobsStorage found, processing key AzureWebJobsStorage for pod: d0547757-0b0d-41bf-b870-4cc03a487e63, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="file matching objectName jjjjjSvc_EventHub_ConnectionString found, processing key jjjjjSvc_EventHub_ConnectionString for pod: d0547757-0b0d-41bf-b870-4cc03a487e63, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="file matching objectName jjjjjSvc_EventHub_ConnectionString_Replay found, processing key jjjjjSvc_EventHub_ConnectionString_Replay for pod: d0547757-0b0d-41bf-b870-4cc03a487e63, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="time=\"2020-07-28T09:31:22Z\" level=info msg=\"using pod identity to access keyvault\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"mounting secrets store object content for default/aaa-ggggg-qryh-7b94bcc5b8-jw8v2\"\ntime=\
"2020-07-28T09:31:22Z\" level=info msg=\"objects: array:\\n  - |\\n    objectName: AKS-AzureWebJobsStorage-svc-ggggg\\n    objectAlias: AzureWebJobsStorage\\n    objectType: secret\\n  - |\\n    objectName: AKS-host-json-svc-ggggg\\n    objectAlias: host.json\\n    obje
ctType: secret\\n  - |\\n    objectName: AppInsights-QuickPulseAuthApiKey\\n    objectAlias: APPINSIGHTS_QUICKPULSEAUTHAPIKEY \\n    objectType: secret\\n\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"unmarshaled keyVaultObjects: [{AKS-AzureWebJobsStorage-svc-ggggg
AzureWebJobsStorage  secret} {AKS-host-json-svc-ggggg host.json  secret} {AppInsights-QuickPulseAuthApiKey APPINSIGHTS_QUICKPULSEAUTHAPIKEY  secret}]\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"keyVaultObjects len: 3\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg
=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:42Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####nI0g\"\ntime=\"2020-07-28T09:32:42Z\" level=info msg=\"clientid: 8496##### REDACTED #####e342\"\ntime=\"2020-07-28T09:32:44Z\" level=inf
o msg=\"secrets store csi driver mounted AzureWebJobsStorage\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/8eab6e24-0fd2-4209-bb17-473e9596c0de/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-ggggg/mount\"\ntime=\"2020-07-
28T09:32:44Z\" level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####nI0g\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"clientid: 8496##### REDACTED #####e342\"\ntime=\"202
0-07-28T09:32:44Z\" level=info msg=\"secrets store csi driver mounted host.json\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/8eab6e24-0fd2-4209-bb17-473e9596c0de/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-ggggg/mount
\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####nI0g\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"clientid: 8496##### REDACTED ####
#e342\"\ntime=\"2020-07-28T09:32:45Z\" level=info msg=\"secrets store csi driver mounted APPINSIGHTS_QUICKPULSEAUTHAPIKEY\"\ntime=\"2020-07-28T09:32:45Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/8eab6e24-0fd2-4209-bb17-473e9596c0de/volumes/kubernetes.io~csi/
csi-key-vault-func-secrets-svc-ggggg/mount\"\n"
time="2020-07-28T09:32:45Z" level=debug msg="[NodePublishVolume] syncK8sSecret is enabled for pod: 8eab6e24-0fd2-4209-bb17-473e9596c0de, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="file matching objectName AzureWebJobsStorage found, processing key AzureWebJobsStorage for pod: 8eab6e24-0fd2-4209-bb17-473e9596c0de, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="file matching objectName APPINSIGHTS_QUICKPULSEAUTHAPIKEY found, processing key APPINSIGHTS_QUICKPULSEAUTHAPIKEY for pod: 8eab6e24-0fd2-4209-bb17-473e9596c0de, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: ba1bf342-a7f0-4a16-b6bc-c5058a766dc5, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-lllllll-mmm, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-dd-eee, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-dd-eee, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 0271e46d-fb5b-46ac-b290-5df10c1291db, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-kkk, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-dd-eee, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-ppppp, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-ppppp, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 2ed45ce8-fd89-4432-b9b9-cfe2b7e9c89d, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 45fe4ccc-dcc5-4c17-baf7-f0f952f28d00, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 0986cc20-ce13-43bb-9c1e-3299b20ac232, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: dcf97b8a-257e-4b65-b7f5-14e46d82b78d, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 883efb3c-64e8-49cf-8b4a-a1ab876b5572, ns: default"
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-bbb, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="created k8s secret: csi-func-secrets-svc-ggggg, ns: default"
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 6746de8e-2aec-433c-8330-040aae781037, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 4e334f62-45fc-4892-9647-b2af38f72a72, ns: default"
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 4a78ba1d-2910-42ee-9ae6-b27dc9d5f9f0, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 95b65174-4970-416f-9283-283a3c20d34a, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: e52fca7b-79aa-4d2c-8639-99246511189f, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: e9da5769-fe5a-4165-a662-e638b70baca6, ns: default"
time="2020-07-28T09:32:45Z" level=info msg="setStatus for pod: 8575be38-891a-4144-bdac-d4def12facbd, ns: default"
time="2020-07-28T09:32:45Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-jjjjj\": the object has been modified; please apply your changes to the latest vers
ion and try again for pod: 2ed45ce8-fd89-4432-b9b9-cfe2b7e9c89d, ns: default"
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:45Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: d0547757-0b0d-41bf-b870-4cc03a487e63, ns: default"
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: 8eab6e24-0fd2-4209-bb17-473e9596c0de, ns: default"
time="2020-07-28T09:32:46Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:46Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:46Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-dd-eee\": the object has been modified; please apply your changes to the latest ver
sion and try again for pod: 4a78ba1d-2910-42ee-9ae6-b27dc9d5f9f0, ns: default"
time="2020-07-28T09:32:46Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-dd-eee\": the object has been modified; please apply your changes to the latest ver
sion and try again for pod: 95b65174-4970-416f-9283-283a3c20d34a, ns: default"
time="2020-07-28T09:32:46Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-kkk\": the object has been modified; please apply your changes to the latest versio
n and try again for pod: e52fca7b-79aa-4d2c-8639-99246511189f, ns: default"
time="2020-07-28T09:32:46Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:46Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-ppppp\": the object has been modified; please apply your changes to the latest vers
ion and try again for pod: 8575be38-891a-4144-bdac-d4def12facbd, ns: default"
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: 2ed45ce8-fd89-4432-b9b9-cfe2b7e9c89d, ns: default"
time="2020-07-28T09:32:46Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:46Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: 4a78ba1d-2910-42ee-9ae6-b27dc9d5f9f0, ns: default"
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: 95b65174-4970-416f-9283-283a3c20d34a, ns: default"
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: e52fca7b-79aa-4d2c-8639-99246511189f, ns: default"
time="2020-07-28T09:32:46Z" level=info msg="setStatus for pod: 8575be38-891a-4144-bdac-d4def12facbd, ns: default"
time="2020-07-28T09:32:46Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:47Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:47Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-dd-eee\": the object has been modified; please apply your changes to the latest ver
sion and try again for pod: 95b65174-4970-416f-9283-283a3c20d34a, ns: default"
time="2020-07-28T09:32:47Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:47Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:47Z" level=info msg="time=\"2020-07-28T09:31:18Z\" level=info msg=\"using pod identity to access keyvault\"\ntime=\"2020-07-28T09:31:18Z\" level=info msg=\"mounting secrets store object content for default/aaa-bbb-cmdh-7fbbf495d4-d755d\"\ntime=\"2
020-07-28T09:31:18Z\" level=info msg=\"objects: array:\\n  - |\\n    objectName: AKS-AzureWebJobsStorage-svc-bbb\\n    objectAlias: AzureWebJobsStorage\\n    objectType: secret\\n  - |\\n    objectName: AKS-host-json-svc-bbb\\n    objectAlias: host.json\\n    objectType
: secret\\n  - |\\n    objectName: jjjjjSvcEventHubConnectionString\\n    objectAlias: jjjjjSvc_EventHub_ConnectionString\\n    objectType: secret\\n  - |\\n    objectName: jjjjjSvcEventHubConnectionStringReplay\\n    objectAlias: jjjjjSvc_EventHub_ConnectionString_Repl
ay\\n    objectType: secret\\n    \\n\"\ntime=\"2020-07-28T09:31:18Z\" level=info msg=\"unmarshaled keyVaultObjects: [{AKS-AzureWebJobsStorage-svc-bbb AzureWebJobsStorage  secret} {AKS-host-json-svc-bbb host.json  secret} {jjjjjSvcEventHubConnectionString jjjjjSvc_Event
Hub_ConnectionString  secret} {jjjjjSvcEventHubConnectionStringReplay jjjjjSvc_EventHub_ConnectionString_Replay  secret}]\"\ntime=\"2020-07-28T09:31:18Z\" level=info msg=\"keyVaultObjects len: 4\"\ntime=\"2020-07-28T09:31:18Z\" level=info msg=\"azure: using pod identity
 to retrieve token\"\ntime=\"2020-07-28T09:32:38Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:38Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"secrets store csi dr
iver mounted AzureWebJobsStorage\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/4be0a6c5-d258-48fc-a21c-3907030629b7/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=
\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:43Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:44Z\" level=info
 msg=\"secrets store csi driver mounted host.json\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/4be0a6c5-d258-48fc-a21c-3907030629b7/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\ntime=\"2020-07-28T09:32:44Z\
" level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32
:44Z\" level=info msg=\"secrets store csi driver mounted jjjjjSvc_EventHub_ConnectionString\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/4be0a6c5-d258-48fc-a21c-3907030629b7/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc
-bbb/mount\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:47Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:47Z\" level=info msg=\"clientid: 5924##### RED
ACTED #####6d12\"\ntime=\"2020-07-28T09:32:47Z\" level=info msg=\"secrets store csi driver mounted jjjjjSvc_EventHub_ConnectionString_Replay\"\ntime=\"2020-07-28T09:32:47Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/4be0a6c5-d258-48fc-a21c-3907030629b7/volumes
/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\n"
time="2020-07-28T09:32:47Z" level=debug msg="[NodePublishVolume] syncK8sSecret is enabled for pod: 4be0a6c5-d258-48fc-a21c-3907030629b7, ns: default"
time="2020-07-28T09:32:47Z" level=info msg="file matching objectName AzureWebJobsStorage found, processing key AzureWebJobsStorage for pod: 4be0a6c5-d258-48fc-a21c-3907030629b7, ns: default"
time="2020-07-28T09:32:47Z" level=info msg="file matching objectName jjjjjSvc_EventHub_ConnectionString found, processing key jjjjjSvc_EventHub_ConnectionString for pod: 4be0a6c5-d258-48fc-a21c-3907030629b7, ns: default"
time="2020-07-28T09:32:47Z" level=info msg="file matching objectName jjjjjSvc_EventHub_ConnectionString_Replay found, processing key jjjjjSvc_EventHub_ConnectionString_Replay for pod: 4be0a6c5-d258-48fc-a21c-3907030629b7, ns: default"
time="2020-07-28T09:32:47Z" level=info msg="setStatus for pod: 95b65174-4970-416f-9283-283a3c20d34a, ns: default"
time="2020-07-28T09:32:48Z" level=info msg="time=\"2020-07-28T09:31:22Z\" level=info msg=\"using pod identity to access keyvault\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"mounting secrets store object content for default/aaa-bbb-evp-5b694f8c68-8jh2s\"\ntime=\"20
20-07-28T09:31:22Z\" level=info msg=\"objects: array:\\n  - |\\n    objectName: AKS-AzureWebJobsStorage-svc-bbb\\n    objectAlias: AzureWebJobsStorage\\n    objectType: secret\\n  - |\\n    objectName: AKS-host-json-svc-bbb\\n    objectAlias: host.json\\n    objectType:
 secret\\n  - |\\n    objectName: jjjjjSvcEventHubConnectionString\\n    objectAlias: jjjjjSvc_EventHub_ConnectionString\\n    objectType: secret\\n  - |\\n    objectName: jjjjjSvcEventHubConnectionStringReplay\\n    objectAlias: jjjjjSvc_EventHub_ConnectionString_Repla
y\\n    objectType: secret\\n    \\n\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"unmarshaled keyVaultObjects: [{AKS-AzureWebJobsStorage-svc-bbb AzureWebJobsStorage  secret} {AKS-host-json-svc-bbb host.json  secret} {jjjjjSvcEventHubConnectionString jjjjjSvc_EventH
ub_ConnectionString  secret} {jjjjjSvcEventHubConnectionStringReplay jjjjjSvc_EventHub_ConnectionString_Replay  secret}]\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"keyVaultObjects len: 4\"\ntime=\"2020-07-28T09:31:22Z\" level=info msg=\"azure: using pod identity
to retrieve token\"\ntime=\"2020-07-28T09:32:37Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:37Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"secrets store csi dri
ver mounted AzureWebJobsStorage\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0fc80ce-51b4-4424-90f7-bda6e6c38cba/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\
"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:44Z\" level=info
msg=\"secrets store csi driver mounted host.json\"\ntime=\"2020-07-28T09:32:44Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0fc80ce-51b4-4424-90f7-bda6e6c38cba/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\ntime=\"2020-07-28T09:32:44Z\"
 level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:47Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:47Z\" level=info msg=\"clientid: 5924##### REDACTED #####6d12\"\ntime=\"2020-07-28T09:32:
48Z\" level=info msg=\"secrets store csi driver mounted jjjjjSvc_EventHub_ConnectionString\"\ntime=\"2020-07-28T09:32:48Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0fc80ce-51b4-4424-90f7-bda6e6c38cba/volumes/kubernetes.io~csi/csi-key-vault-func-secrets-svc-
bbb/mount\"\ntime=\"2020-07-28T09:32:48Z\" level=info msg=\"azure: using pod identity to retrieve token\"\ntime=\"2020-07-28T09:32:48Z\" level=info msg=\"accesstoken: eyJ0##### REDACTED #####mp-Q\"\ntime=\"2020-07-28T09:32:48Z\" level=info msg=\"clientid: 5924##### REDA
CTED #####6d12\"\ntime=\"2020-07-28T09:32:48Z\" level=info msg=\"secrets store csi driver mounted jjjjjSvc_EventHub_ConnectionString_Replay\"\ntime=\"2020-07-28T09:32:48Z\" level=info msg=\"Mount point: /var/lib/kubelet/pods/d0fc80ce-51b4-4424-90f7-bda6e6c38cba/volumes/
kubernetes.io~csi/csi-key-vault-func-secrets-svc-bbb/mount\"\n"
time="2020-07-28T09:32:48Z" level=debug msg="[NodePublishVolume] syncK8sSecret is enabled for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"
time="2020-07-28T09:32:48Z" level=info msg="file matching objectName AzureWebJobsStorage found, processing key AzureWebJobsStorage for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"
time="2020-07-28T09:32:48Z" level=info msg="file matching objectName jjjjjSvc_EventHub_ConnectionString found, processing key jjjjjSvc_EventHub_ConnectionString for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"
time="2020-07-28T09:32:48Z" level=info msg="file matching objectName jjjjjSvc_EventHub_ConnectionString_Replay found, processing key jjjjjSvc_EventHub_ConnectionString_Replay for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"
time="2020-07-28T09:32:48Z" level=debug msg="GRPC call: /csi.v1.Node/NodeGetCapabilities"
time="2020-07-28T09:32:48Z" level=debug msg="GRPC request: "
time="2020-07-28T09:32:48Z" level=debug msg="Using default NodeGetCapabilities"
time="2020-07-28T09:32:48Z" level=debug msg="GRPC response: capabilities:<rpc:<> > "
time="2020-07-28T09:32:48Z" level=info msg="created k8s secret: csi-func-secrets-svc-bbb, ns: default"
time="2020-07-28T09:32:48Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:48Z" level=info msg="created k8s secret: csi-func-secrets-svc-bbb, ns: default"
time="2020-07-28T09:32:48Z" level=info msg="setStatus for pod: 4be0a6c5-d258-48fc-a21c-3907030629b7, ns: default"
time="2020-07-28T09:32:49Z" level=info msg="setStatus for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"
time="2020-07-28T09:32:49Z" level=debug msg="GRPC response: "
time="2020-07-28T09:32:49Z" level=error msg="failed to set status, err: Operation cannot be fulfilled on secretproviderclasses.secrets-store.csi.x-k8s.io \"csi-key-vault-func-secrets-svc-bbb\": the object has been modified; please apply your changes to the latest versio
n and try again for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"
time="2020-07-28T09:32:50Z" level=info msg="setStatus for pod: d0fc80ce-51b4-4424-90f7-bda6e6c38cba, ns: default"

@aramase , any idea what I can do to prevent such downtimes from happening, whenever pods need to be run on a new node?

@deyanp Thank you for sharing the event output and logs. Some of things I see from the events -

The workload pod was scheduled ~5s before the CSI driver pod was scheduled on node aks-nodepoole2-15204281-vmss000000
The image pull and getting the pod started took close to 1m30s~2m for this node
During this time kubelet mount calls were failing because the CSI driver pod wasn't yet running
After the driver pods were successfully running, kubelet retried the mount after 30s and the mount succeeded.
Error pulling images in the events for pods aaa-* which also resulted in the pod start up delays.
Driver images being pulled as soon as the node was marked NodeReady, but the image pull for all the images took about 2mins on average for each node. During this time kubelet starts the mount requests for all pods that are scheduled on the node and the driver isn't up and running yet to respond.

The image pull in case of my clusters and repro only took ~10-15s which explains why all my pods were up and running without a lot of mount failure errors.

And for things like csi-node-driver-registrar:v1.2.0 we should set the default value in the provider chart as the one being cached in the vhd after this PR merges

@ritazh For aks-engine, we already cache the driver, liveness probe and csi-node-driver-registrar images. We also cache the provider images. For this particular cluster, I think @deyanp is hosting the image - yy5ker.io/deislabs/secrets-store-csi:v0.0.11.

And for things like csi-node-driver-registrar:v1.2.0 we should set the default value in the provider chart as the one being cached in the vhd after this PR merges

+1 for this. We should definitely switch to mcr images in the helm repo here.

I think @deyanp is hosting the image - yy5ker.io/deislabs/secrets-store-csi:v0.0.11.

The CSI Driver image? No, I am not (deliberately) hosting the image in my Azure Container Registry ... About 2 months ago I simply used the CSI Driver for Azure setup instructions with yaml (without helm):
gitHubPath1=https://raw.githubusercontent.com/kubernetes-sigs/secrets-store-csi-driver/master/deploy

kubectl apply -f $gitHubPath1/rbac-secretproviderclass.yaml # update the namespace of the secrets-store-csi-driver ServiceAccount
kubectl apply -f $gitHubPath1/csidriver.yaml
kubectl apply -f $gitHubPath1/secrets-store.csi.x-k8s.io_secretproviderclasses.yaml
kubectl apply -f $gitHubPath1/secrets-store-csi-driver.yaml # --namespace $NAMESPACE

# validate
# kubectl get pods -l app=csi-secrets-store

gitHubPath2=https://raw.githubusercontent.com/Azure/secrets-store-csi-driver-provider-azure/master/deployment

kubectl apply -f $gitHubPath2/provider-azure-installer.yaml

@aramase , do you mean that because the driver images pull took so long that is why the csi driver pods could not be started earlier, and I had such serious issues for such a long time?
PS: Please not that I have in parallel the following MS Support Ticket open: "120072825001618 Failed to pull image : unauthorized: authentication required Kubernetes Service (AKS)  ", in which I am asking about some image pull errors I had during the same cluster/nodepool upgrade, with the question whether the Container Registry being Basic SKU is an issue ...

One more note, all my about 40 custom pods have imagePullPolicy: Always - is that fine, or can it be the reason for the issues I am experiencing?

@aramase , do you mean that because the driver images pull took so long that is why the csi driver pods could not be started earlier, and I had such serious issues for such a long time?

Yeah, the driver pods took 2 mins to start because of image pull during which the mount requests were failing.

The CSI Driver image? No, I am not (deliberately) hosting the image in my Azure Container Registry ... About 2 months ago I simply used the CSI Driver for Azure setup instructions with yaml (without helm):

The driver image was hosted in docker.io/deislabs/secrets-store-csi:v0.0.11. I see yy5ker.io/deislabs/secrets-store-csi:v0.0.11 used as image in your cluster. Do you know why that is?

One more note, all my about 40 custom pods have imagePullPolicy: Always - is that fine, or can it be the reason for the issues I am experiencing?

Most of the image pull errors are unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information. It's possible the credentials to pull were not available on the node?

@aramase , the image is from docker.io/deislabs/secrets-store-csi:v0.0.11, yy5ker is the result of my attempt to anonymize the logs a bit (replace "doc" with "yy5") so that the real name of the pods is not visible ;) So pls assume that the image is being pulled from its regular source repo.
Why would the new node not be able to authenticate against ACR? As mentioned, the cluster is using SystemAssigned identity, which was granted access to ACR, so the new node should also be able to use that, right ...
So it seems all my problems center around pulling images, wondering if that is because my 40 pods have imagePullPolicy=Always, and that somehow overloads the Basic SKU ACR .. why would that affect also pulling the image of CSI Driver is what puzzles me though ...

@aramase , on the MS support ticket I opened in relation to image pull errors (mentioned above) I got the link to the following issue: https://github.com/kubernetes/kubernetes/issues/92326 ...
I need to wrap my head around this and come up with a final conclusion and next steps, any help appreciated!
My current understanding is that because of my AKS cluster configured with MSI (which I think is the recommended way?) I am (sometimes?) unable to pull images from ACR, which prevents CSI Driver from starting quickly, which results in CSI drive mount errors for the other pods - is this correct?
Strange that I am alone with this issue ... any ideas about workarounds in the meantime, as I am already in production?

I am getting the same kind of error. I followed most of the instructions at https://github.com/HoussemDellai/aks-keyvault except I use a managed identity. My pod is stuck at ContainerCreating and kubectl describe pod nginx-secrets-store shows
Warning  FailedMount  3m45s (x2 over 8m19s)  kubelet, aksnpwin000000  Unable to attach or mount volumes: unmounted volumes=[secrets-store-inline], unattached volumes=[secrets-store-inline default-token-9tmcm]: timed out waiting for the condition
Warning  FailedMount  87s (x2 over 6m3s)     kubelet, aksnpwin000000  Unable to attach or mount volumes: unmounted volumes=[secrets-store-inline], unattached volumes=[default-token-9tmcm secrets-store-inline]: timed out waiting for the condition
Warning  FailedMount  6s (x13 over 10m)      kubelet, aksnpwin000000  MountVolume.SetUp failed for volume "secrets-store-inline" : kubernetes.io/csi: mounter.SetUpAt failed to get CSI client: driver name secrets-store.csi.k8s.io not found in the list of registered CSI drivers

@aramase , on the MS support ticket I opened in relation to image pull errors (mentioned above) I got the link to the following issue: kubernetes/kubernetes#92326 ...

Yeah, that is a known issue for which there is a PR with the fix. I believe that'll be back ported to previous kubernetes versions.

I need to wrap my head around this and come up with a final conclusion and next steps, any help appreciated!
My current understanding is that because of my AKS cluster configured with MSI (which I think is the recommended way?) I am (sometimes?) unable to pull images from ACR, which prevents CSI Driver from starting quickly, which results in CSI drive mount errors for the other pods - is this correct?

The CSI driver images aren't being pulled from ACR, but the image pull in general for this cluster seems to be taking 2m on average which causes the mount delays for 2m. But once the mount is successful, the application start time is delayed by the ACR image pull errors which causes delays before the application is up and running.

Strange that I am alone with this issue ... any ideas about workarounds in the meantime, as I am already in production?

For the CSI driver, I think once the image is pulled, the mount succeeds on the next retry. We'll be switching to using mcr hosted images in the next release which will also be cached in the vhd. For the managed identity issue, I believe once the fix is merged and back ported it'll help resolve these additional delays you're seeing with your application start time.

@ahmedsza It looks like you're trying to run on a windows node? Did you install the helm charts with windows enabled? Which kubernetes version are you running? kubectl version and kubectl get nodes -o wide

Hi @aramase . You are correct. The cluster was provisioned to support windows and I did add a windows nodepool. I saw i needed to on a later version of aks and have subsequently upgraded aks to 1.18. But error was still there. So yes the helm charts were originally installed on the older aks version..should i uninstall and reinstall the helm charts .. or is there something else I need to do.. for my scenario for this,  everything should run on Linux.

A note that the windows nodepool was not explicitly upgraded. So I guess I need to do that. is there a chance my pod also got allocated to a Linux node, and i need to put in the relevant node selector or taint

Hi @aramase . You are correct. The cluster was provisioned to support windows and I did add a windows nodepool. I saw i needed to on a later version of aks and have subsequently upgraded aks to 1.18. But error was still there. So yes the helm charts were originally installed on the older aks version..should i uninstall and reinstall the helm charts .. or is there something else I need to do.. for my scenario for this, everything should run on Linux.

@ahmedsza If your workload is running on windows node, then you'll also need to run the driver on windows node. While deploying it through helm, you can set --windows.enabled=true and --secrets-store-csi-driver.windows.enabled=true. The helm chart configuration options are documented here - https://github.com/Azure/secrets-store-csi-driver-provider-azure/tree/master/charts/csi-secrets-store-provider-azure#configuration

A note that the windows nodepool was not explicitly upgraded. So I guess I need to do that. is there a chance my pod also got allocated to a Linux node, and i need to put in the relevant node selector or taint

If using windows, the required version is 1.18+ as documented here
Recommended Kubernetes version:

For Linux - v1.16.0+
For Windows - v1.18.0+

@aramase After upgrading the Azure Container Registry to Standard Tier I did another upgrade from 1.17.7 -> 1.17.9 but the disaster repeated - my pods were scheduled to be recreated before the csi-secrets-store and csi-secrets-store-provider-azure, and of course the volume mount failed etc. etc. I had again the unauthorized errors from ACR and so on ...
One thing I do not understand - you said there is no way how to tell K8s to first create the csi-secrets-store* pods on the new node, and then the rest of the pods ... but this implies that I will have every time downtime when upgrading ... I have many pods which have 1 replica only, as I don't need more than 1 currently ... does it mean I have to increase the replicas to 2 for all my pods?
I just can't believe it that everybody else but me is fine with the fact that the CSI driver pods cannot be scheduled somehow before the rest on a new node ... this fact makes the csi driver almost unusable for me ...

@aramase After upgrading the Azure Container Registry to Standard Tier I did another upgrade from 1.17.7 -> 1.17.9 but the disaster repeated - my pods were scheduled to be recreated before the csi-secrets-store and csi-secrets-store-provider-azure, and of course the volume mount failed etc. etc. I had again the unauthorized errors from ACR and so on ...

The fix for ACR unauthorized error (https://github.com/kubernetes/kubernetes/pull/92330) has been merged to master and back ported to previous Kubernetes releases. This should be available in the next set of Kubernetes releases and will be supported in AKS. This additional delay that's being caused during upgrade because of image pull errors should be resolved with the fix.

One thing I do not understand - you said there is no way how to tell K8s to first create the csi-secrets-store* pods on the new node, and then the rest of the pods ... but this implies that I will have every time downtime when upgrading ... I have many pods which have 1 replica only, as I don't need more than 1 currently ... does it mean I have to increase the replicas to 2 for all my pods?

K8s schedules all pods to the new node as part of the upgrade. There is no primitive to tell K8s to schedule critical addons before work load pods. But in this scenario, the CSI driver is being scheduled along with the workload pods. The image pull for all 3 containers take 1m on average and in some cases close to 1m20s. During this time kubelet attempt to mount volume for workload pods will fail as the driver is not up and running. From the events posted, the driver successfully mounted the volume right after it was started. Kubelet then tried to pull the images for the work load pod which failed with unauthorized error and took close to 2m30s to succeed. This is the reason for the workload pod being down for a long time. The pod start up time is proportional to the time for scheduling, sandbox creation, volume mount, image pull and then starting the container.

I just can't believe it that everybody else but me is fine with the fact that the CSI driver pods cannot be scheduled somehow before the rest on a new node ... this fact makes the csi driver almost unusable for me ...

The CSI driver pods are scheduled at the same time as the workload. It's the buffer around image pull time that can generate mount failed events. But once the CSI driver is up, the mount succeeds as kubelet periodically reconciles the volume mounts. In my tests, the work load images aren't in ACR. The mount succeeds as soon as the driver pod is running and my workload is also up and running.

We have switched to using images hosted in mcr for the driver and these images have been added to the VHD for aks-engine. Closing this issue. Please feel free to open a new issue if you have any questions.

Hi, I am using AKS engine and deployed the csi driver using Helm. I think I face the same issue when allocating new nodes. It looks like it takes more than 6 minutes to pull the mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.0 from the registry.
  Normal  Scheduled  24m   default-scheduler  Successfully assigned kube-system/secrets-store-csi-driver-kdgbl to aks-standard0-86582503-vmss000016
  Normal  Pulling    24m   kubelet            Pulling image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.0"
  Normal  Pulled     18m   kubelet            Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.0" in 6m4.297828498s
  Normal  Created    18m   kubelet            Created container node-driver-registrar
  Normal  Started    18m   kubelet            Started container node-driver-registrar
  Normal  Pulling    18m   kubelet            Pulling image "mcr.microsoft.com/oss/kubernetes-csi/secrets-store/driver:v1.1.2"
  Normal  Pulled     18m   kubelet            Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/secrets-store/driver:v1.1.2" in 3.250343117s
  Normal  Created    18m   kubelet            Created container secrets-store
  Normal  Started    18m   kubelet            Started container secrets-store
  Normal  Pulling    18m   kubelet            Pulling image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.6.0"
  Normal  Pulled     18m   kubelet            Successfully pulled image "mcr.microsoft.com/oss/kubernetes-csi/livenessprobe:v2.6.0" in 681.755543ms
  Normal  Created    18m   kubelet            Created container liveness-probe
  Normal  Started    18m   kubelet            Started container liveness-probe

mcr.microsoft.com/oss/kubernetes-csi/csi-node-driver-registrar:v2.5.0

@dszakallas This is an expected behaviour. Pod won't start if they are referring to CSI volumes and CSI driver itself is not registered yet. However 6 mins is very long time to pull ~20MB image. I would suggest to check network connection.
On the side note, if you are using AKS we recommend using managed add-on for Secrets Store CSI driver. https://docs.microsoft.com/en-us/azure/aks/csi-secrets-store-driver

@nilekhc I mitigated this issue by mirroring the images required for the CSI driver in our container registry and using those in the helm chart.


Add mutation API for editors to change displayName

UpdateUser(name: String) -> User

Assigning @darkbtf  because it's determined in 20180207


[FOSSA] Issue with goa - UNLICENSED_DEPENDENCY

UNLICENSED_DEPENDENCY - goa (d673c4ff3be94468852a044acd92b006a6b49c35)
Component URL
https://github.com/mgutz/goa
Affected Projects

kubevirt

Issue
This dependency hasn't specified a license. You may need to contact the author to obtain permission to use it.
No licenses found by FOSSA.

Generated by FOSSA on 11/22/2019
Reported by FOSSA user<EMAIL_ADDRESS>

Transitive dependency not present in our vendor folder.
/close


[stdlib] Don't use aarch64 hint for arm targets in Synchronization

On ARM targets, the intrinsic is called llvm.arm.hint instead of llvm.aarch64.hint. Make sure we call that for those targets.
Resolves: https://github.com/apple/swift/issues/74186

@swift-ci please smoke test

Thanks, I'll try this out.


Should sparse fieldsets and includes be specified on the document rather than the primary element?

Since sparse fieldsets and includes are a global concept, ie, they are specified once in the URL and have an effect on all resources in the document:
GET /articles/1?fields[comments]=body,author&include=comments.author

Does it make sense to be specifying them on Resources/Collections, rather than on the Document itself? eg,
$collection = new Collection($posts, new PostSerializer);

$document = new Document($collection);
$document->setInclude(['comments.author']);
$document->setFields(['comments' => ['body', 'author']]);

Thinking about how this would work in the code, at most it would just be an alternative way of specifying the includes/sparse fieldsets. Under the hood, the Document would simply pass these assignments on to the root Element.
Do people see any value in adding this API?

And some further thought leads me to realize that the Document itself has nothing to do with includes and fields — these are indeed directives for the top-level data, so it absolutely makes sense to be setting them on the root Element.
I see no reason to increase the API surface area here.


Glitch

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):1.4.3243.0

Any other software?

Steps to reproduce

Click on settings.
Expected behavior
Open the settings.

Opening the settings.
Actual behavior
"

When I open it it says "choose a app to open json
`

This is because our Settings are stored in a JSON file.
/dup #1564

This is because our Settings are stored in a JSON file.
/dup #1564


<EMAIL_ADDRESS>Restore PHP 8.0

<EMAIL_ADDRESS>Add PHP 8.0 as versioned formula

:beers: @BrewTestBot has triggered a merge.


Splitted Mailer for Laravel 7 and previous versions

Fixes #1
@mpociot when I suggested using SwiftMailer plugins I still hadn't see the inner workings of the plugin. Since it's tied to the Mailable, it's difficult to implement as a SwiftMailer plugin and provides no advantages.
I think the fix in this PR solves the problem in the easiest way possible. I just split the Mailers and added the same mailer method that is found in the MailFake class.

Thank you!


Any plans for SSML support?

this is business logic, you can implement it by yourself, we do not have plans to suport it, but we may support more symbols like


License

Sorry to bother you again. I check the code in depth and I would like to use parts of it and possibility add some custom stuff for myself like api calls to statistics. Is it possible to add a license? Otherwise it will be illegal for me to perform any of the alterations.
Thanks:)

I've added the Apache 2.0 LICENSE.


[FEAT]: Enable multi-file model import

What would you like to see?
These days some of the organizations split their model files (I assume for the easier download), eg. Qwen2.5 is split into 3.5GB parts. I could not import this kind of model, perhaps I didn't know how to do?
Thank you!

Cannot be supported until https://github.com/ollama/ollama/issues/5245 is closed & merged

For the time being, we can use this workaround: https://github.com/ollama/ollama/issues/5245#issuecomment-2305577747


Pass a GlobalEnvironment into the Runtime::initialize()

Context
As you can find in https://github.com/jenshaase/phel-composer-plugin/blob/master/src/DumpRuntime.php:67:
$template = <<<EOF
<?php
// @generated by Phel
use Phel\Runtime;
require __DIR__ .'/autoload.php';
\$rt = Runtime::initialize();
EOF;

What
The Runtime::initialize() doesn't provide any argument because the signature of that named constructor allows you to do it this way. I was thinking about changing the signature of that name constructor to force the GlobalEnvironmentInterface argument every time when you want to initialize the Runtime. The Phel\Runtime would look like this:
// Runtime:62
public static function initialize(
    ?GlobalEnvironmentInterface $globalEnv,
    ?string $cacheDirectory = null
): self

Reason
In order to decouple the Phel\Runtime from the GlobalEnvironment. This is the change that I would like to do in Phel project, but it's blocked by the PhelRuntime autoload (this phel-composer-plugin).
// Runtime:70
- public static function initialize(
-     ?GlobalEnvironmentInterface $globalEnv = null,
-     ?string $cacheDirectory = null
- ): self {
-     if (self::$instance !== null) {
-         throw new RuntimeException('Runtime is already initialized');
-     }
-
-     self::$instance = new self(
-         $globalEnv ?? new GlobalEnvironment(), // <--- THIS IS THE ACTUAL CHANGE
-         $cacheDirectory
-     );
-
-     return self::$instance;
- }
+ public static function initialize(
+     ?GlobalEnvironmentInterface $globalEnv,
+     ?string $cacheDirectory = null
+ ): self {
+     if (self::$instance !== null) {
+         throw new RuntimeException('Runtime is already initialized');
+     }
+
+     self::$instance = new self($globalEnv, $cacheDirectory);
+
+     return self::$instance;
+ }

Acceptance Criteria

Change that template (from the DumpRuntime.php:67) in order to pass the concrete GlobalEnvironment while initializing the Runtime.

Hi,
this plugin should need to know as little as possible. Therefore, there should be a method in the Phel Project that initializes the runtime by a method call without arguments. If you think Runtime::initialize is not the best way to do it, I would suggest to introduce a Factory Class to handle this. What do you think?
Best regards,
Jens

Yes, thanks for the idea, @jenshaase. This is the PR https://github.com/jenshaase/phel-composer-plugin/pull/3


Call hierarchy shows wrong result at first

Version: 1.44.1 (system setup)
Commit: a9f8623ec050e5f0b44cc8ce8204a1455884749f
Date: 2020-04-11T01:48:12.622Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Steps to Reproduce:

Click show call hierarchy

From the gif you can see at first, the results are actually outgoing calls, but VS Code shows them as incoming calls.

I'll take this up

Created a PR in the vscode-references-view extension repo


MySQL installer does not install packages

Create issues related to the winget.exe client here

Brief description of your issue

While installing MySQL via winget, only the installer is installed, and not the packages that are supposed to accompany the installer
Steps to reproduce

Run winget install Oracle.MySQL
Navigate to the folder where the installer has been installed and run MySQLInstaller.exe

Expected behavior

The installer should install normally, with the various packages installing as usual

Actual behavior

The installer can not find the required packages for installation

Environment
[winget --info]
Windows: Windows.Desktop v10.0.22000.100
Package: Microsoft.DesktopAppInstaller v1.15.11694.0
MySQL version: 8.0.25

I've figured it out, there's two issues:

There's a (bug/confusing behavior)[https://bugs.mysql.com/bug.php?id=92600] in the MySQL Installer (for two years now) that if you launch it without command line arguments it assumes you want the commercial installer instead of the community one. This one is easy-ish for us to fix, we just need to add CONSOLEARGS="install -type=Full -silent" to the custom installer flags for it to work. Since you have it installed already, just run C:\Program Files (x86)\MySQL\MySQL Installer for Windows\MySQLInstaller.exe Community from a shell to get the installer to behave.

The larger problem is that even if we add those arguments to the manifest, it still won't work right because it can't install the VC++ 2015-2019 redist without user interaction. If they are installed it works fine, if they aren't it blinks a command window up on the screen and exits. It works fine interactively since it can ask you to install them, but not silently.

TL;DR: There's a workaround, but in general this is probably blocked for dependencies right now.


[feature] (Scripts) Run code after a pass

Describe your idea
Maybe this is already implemented, but I haven't figured out how to do it:
I have a script that runs some code in insns of the jadx.replace pass:
import jadx.core.dex.instructions.InvokeNode

val jadx = getJadxInstance()

jadx.replace.insns { mth, insn ->
    if (insn is InvokeNode) {
        // Some custom logic runs here
    }
}

It works fine, but I want to run some other code after this pass, such that the "epilogue" code only runs once (currently it's running every time insns is called, causing a huge performance hit). Essentially, I want something like this:
import jadx.core.dex.instructions.InvokeNode

val jadx = getJadxInstance()

jadx.replace.insns { mth, insn ->
    if (insn is InvokeNode) {
        // Some custom logic runs here
    }
}

jadx.replace.finished {
    // Print summary of changes (and/or other logic)
}

Is something like this possible with the current implementation?

@SeanPesce you need to force full decompilation to execute action after all classes processed and decompiled:
jadx.afterLoad {
    // force decompilation of all classes
    jadx.decompile.all()

    // all classes decompiled
    // insert you 'finish' code here
}

Jadx don't have any 'after all' stage because in jadx-gui classes decompiled on demand and all classes decompilation may not be requested at all.


Crash Log Support for HoloLens

Describe the solution you'd like
Much like HockeyApp supported crash logging for iOS and Android projects (including crash log capture, aggregation, symbolication, etc), we are in desperate need of crash logging for HoloLens.
Describe alternatives you've considered
We have tried a couple things:

MS Store crash logging - The app store can capture crash logs. However, in our scenario we use Intune to manage deploying a line of business app to specific devices in Kiosk mode. These builds cannot go on the store. There is also a way to deploy from the app store to specific private segments-- but this has little support and does not seem to be compatible with Intune. Also, the MS Store does not have graph api endpoints so we cannot automate anything.
CoreApplication - There's an API that can catch some unhandled errors-- unfortunately it does not catch them all. This is also not a complete solution.

Additional context
Our HoloLens application is used by the public, not by trained users. We have over 6000 visitors per month at a single location (and we are expanding to more). This is not a typical use case for HoloLens but it's proving to be a very engaging one. In order to support more locations, which may be on different versions of the application, different Intune accounts, etc we need to be able to scale the HoloLens software. Crash-logging is a desperate need in this case.

Hi @thegoldenmule,
This is Winnie from the App Center PM team. Are you using UWP or Unity for your HoloLens app? We have some known limitations for Windows, namely, your app needs to be distributed through the Windows store in order for us to detect any crashes. We understand this isn't a great experience and are committed to improving this experience in the upcoming months.
However, if you're using Unity, you can track handled exceptions in your apps which should circumvent this limitation.

Thanks for the reply @winnieli1208. Yes, we are using UWP for HoloLens dev. As stated, the Windows store is not a good option for our use case.

Sorry, accidentally closed.
In addition, handled exceptions are fine, but there are classes of exceptions that cannot be caught, including memory exceptions. As stated in the original ticket, even using CoreApplication unhandled exceptions, we are not seeing them all.

@thegoldenmule thanks for the additional context! The Windows store requirement is definitely a major blocked for many customers and we're committed to changing this in the upcoming months. I don't currently have an ETA but I expect our team to start working on Windows sometime around March. You can check out our roadmap and iteration plan to see what our team is working on.
I'll also update this thread once I have a more specific timeline. Thanks for your patience!

Update: the improvements for UWP will come later this year, ideally around the end of summer. We plan to start work on WinForms and WPF first.


Add documentation for shades

No breaking changes, but there are now shades called "50" - "900" similar to the tailwind color system. Add some documentation about this.

Added to documentation in commit d9c135e1dee062a8fdd4230698a7d0851af0cebb


Small sample corrections

For the x1 bootstraps, I will implement a ssc correction of $(N-1) / (N-k)$.
For the x3 bootstraps, $(G-1) / G$

Both is more or less the standard in the literature. For compatibility with choices made via statsmodels / linearmodels, add the option to overwrite these default values.
Note that for p-values, the choice of small sample corrections does not have an impact (as the ssc's cancel out when computing p-values by counting cases of scc x t_stat < ssc x t_boot). They only affect the internally computed and reported non-bootstrapped test statistic.

Close with #52


Dataset and pretrained model.

Is data and pretrained model openly available? Please share hyperlinks.

Sorry, the dataset is private.


[bug] iOS not showing Metamask Icon while Android yes

Link to minimal reproducible example
https://deelance.com/
Summary
Hello, as title, on iOS the Metamask Icon is not showing as option to connect, while on Android and Desktop is fine.
List of related npm package versions
"@web3modal/ethereum": "2.1.2",
"@web3modal/react": "2.1.2",
"wagmi": "^0.11.7",

This is due to using version 2, MetaMask does not support it yet (they are working on it however).
Android has a special view where wallet animation is shown, but wallets are opened in a native modal that appears showing you all installed apps that can handle wc://... deeplink, hence why it's shown there. We'll need to work on androids view to make it more clear.


VnV typos and explain further according to comments

Add more details when reading feedback from Dr. Smith. Fix typos. Add straightforward explainations.

Fixed in e650070.


Contact us footer

Create new good looking contact us page from scratch.
Added some animated icons.
Added animation in form.
100% Mobile responsive
Future ideas:
Replace form style with glass design.
Link address with google maps.
Change the headline xD
Any minor changes you want, comment, and I will change it.
Any major changes you want, I will do after 2 days with the new PR.
Kindly give Hacktoberfest tag :D
Image source : Unsplash (no copyright I think)
icons source : icons8.com (I don't know about copyright, I asked you same thing on tg)

@kituuu

can you make those icons a Lil bit bigger

-also increase the size of Contact us and we would love to hear from you
Apart from this everything looks amazing

@kituuu

can you make those icons a Lil bit bigger

-also increase the size of Contact us and we would love to hear from you
Apart from this everything looks amazing

make this you next PR I am accepting this one 😄

Aye Aye Captain 😅


UnUniFi Application NFT Mint

Functions of NFT Mint for UnUniFi Application Plugin.
Bubble Plugin

[x] Implements

Bubble App Tests

[x] create_class
[x] mint_nft
[x] burn_nft
[x] send_class_ownership
[x] update_base_token_uri
[x] update_token_supply_cap

Owner task

[ ] Release

@KimuraYu45z CC: @yutaro-elk
All nftmint functions work. Please release Bubble plugin.

#12
All functions have been worked!
I wanna merge this PR.
@KimuraYu45z Plz review bacause i am not owner and cannot merge without a review.


How to open left menu if front view swipe right

Hello, I have problem with this library. My apps can allow user to open the left side menu with swipe in from view. I have add the code.
- (void)viewDidLoad {
    [super viewDidLoad];
    revealViewController = self.revealViewController;
    revealViewController.delegate = self;
    self.view.userInteractionEnabled = YES;
    [self.view addGestureRecognizer:self.revealViewController.panGestureRecognizer];
}

But not working.

This is not general QA forum. Please head to StackOverflow instead.

Solved


Support for additionalProperties in CRD Annotations with cty

Hello,
I recently attempted to add annotations, similar to the native Kubernetes annotations, to my Custom Resource Definition (CRD). Since annotations are essentially random key-value pairs, I explored using additionalProperties as outlined in the OpenAPI documentation here.
However, when I tried to implement this in my YAML configuration, I encountered a SIGSEGV error with cty. Could cty be updated to support the use of additionalProperties for CRD annotations? It would be a great enhancement and provide more flexibility.
Thank you!
this is a snippet from my crd:
                values:
                  description: all values for the helm chart
                  properties:
                    teams:
                      properties:
                        annotations:
                          additionalProperties: true
                          description: Annotations set to all Kubernetes components
                          type: object

here is the stacktrace if helpful
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x168 pc=0x1515f3f]

goroutine 1 [running]:
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001db690, 0xe}, {0xc0001db6e0, 0x8}, {0xc0001db6a0, 0xb}, 0xc0001d1710, {0x16f55e0, 0xc000066cc8}, 0x6, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:106 +0xabf
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001db690, 0xe}, {0xc0001db6e0, 0x8}, {0xc0001db6a0, 0xb}, 0xc0001d16e0, {0x16f55e0, 0xc000066cc8}, 0x4, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:102 +0xcf6
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001db690, 0xe}, {0xc0001db6e0, 0x8}, {0xc0001db6a0, 0xb}, 0xc0001d1680, {0x16f55e0, 0xc000066cc8}, 0x2, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:102 +0xcf6
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001db690, 0xe}, {0xc0001db6e0, 0x8}, {0xc0001db6a0, 0xb}, 0xc0001d1620, {0x16f55e0, 0xc000066cc8}, 0x0, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:102 +0xcf6
github.com/Skarlso/crd-to-sample-yaml/pkg.Generate(0xc0001538c0, {0x16f73a8?, 0xc000066cc8}, 0xba?)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:22 +0x208
github.com/Skarlso/crd-to-sample-yaml/cmd.runGenerate(0xc000166a00?, {0x1611e90?, 0x4?, 0x1611e94?})
        github.com/Skarlso/crd-to-sample-yaml/cmd/generate.go:85 +0x285
github.com/spf13/cobra.(*Command).execute(0x1ab7b20, {0xc000040d70, 0x5, 0x5})
        github.com/spf13/cobra@v1.8.0/command.go:983 +0xabc
github.com/spf13/cobra.(*Command).ExecuteC(0x1ab7e00)
        github.com/spf13/cobra@v1.8.0/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
        github.com/spf13/cobra@v1.8.0/command.go:1039
github.com/Skarlso/crd-to-sample-yaml/cmd.Execute(...)
        github.com/Skarlso/crd-to-sample-yaml/cmd/root.go:18
main.main()
        github.com/Skarlso/crd-to-sample-yaml/main.go:10 +0x1a
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x168 pc=0x1515f3f]

goroutine 1 [running]:
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001cfa90, 0xe}, {0xc0001cfad0, 0x8}, {0xc0001cfaa0, 0xf}, 0xc0001c3e00, {0x16f55e0, 0xc000066cd0}, 0x6, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:106 +0xabf
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001cfa90, 0xe}, {0xc0001cfad0, 0x8}, {0xc0001cfaa0, 0xf}, 0xc0001c3dd0, {0x16f55e0, 0xc000066cd0}, 0x4, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:102 +0xcf6
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001cfa90, 0xe}, {0xc0001cfad0, 0x8}, {0xc0001cfaa0, 0xf}, 0xc0001c3d70, {0x16f55e0, 0xc000066cd0}, 0x2, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:102 +0xcf6
github.com/Skarlso/crd-to-sample-yaml/pkg.ParseProperties({0xc0001cfa90, 0xe}, {0xc0001cfad0, 0x8}, {0xc0001cfaa0, 0xf}, 0xc0001c3d10, {0x16f55e0, 0xc000066cd0}, 0x0, ...)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:102 +0xcf6
github.com/Skarlso/crd-to-sample-yaml/pkg.Generate(0xc0001538c0, {0x16f73a8?, 0xc000066cd0}, 0xba?)
        github.com/Skarlso/crd-to-sample-yaml/pkg/generate.go:22 +0x208
github.com/Skarlso/crd-to-sample-yaml/cmd.runGenerate(0xc000166a00?, {0x1611e90?, 0x4?, 0x1611e94?})
        github.com/Skarlso/crd-to-sample-yaml/cmd/generate.go:85 +0x285
github.com/spf13/cobra.(*Command).execute(0x1ab7b20, {0xc000040d70, 0x5, 0x5})
        github.com/spf13/cobra@v1.8.0/command.go:983 +0xabc
github.com/spf13/cobra.(*Command).ExecuteC(0x1ab7e00)
        github.com/spf13/cobra@v1.8.0/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
        github.com/spf13/cobra@v1.8.0/command.go:1039
github.com/Skarlso/crd-to-sample-yaml/cmd.Execute(...)
        github.com/Skarlso/crd-to-sample-yaml/cmd/root.go:18
main.main()
        github.com/Skarlso/crd-to-sample-yaml/main.go:10 +0x1a

Oh interesting! Thanks very much for the report. I'll check it out. :)

@henrysachs Which version where you trying out?

@Skarlso the tool doesnt print out its version (so maybe i have a really old one 😅)
we also found a "workaround" when specifying the type of additionalproperties it seems to work only when using true as value it fails
❯ cty help
CRDs to a Sample file.

Usage:
  crd-to-sample [flags]
  crd-to-sample [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  generate    Simply generate a CRD output.
  help        Help about any command

Flags:
  -h, --help   help for crd-to-sample

Use "crd-to-sample [command] --help" for more information about a command.

Oh, it is quite old then. :D
./cty version
v0.0.0-dev
➜  crd-to-sample-yaml git:(main) ✗

Should have a version now. :)
In any case, I just successfully reproduced your error. So I'll be fixing it shortly. :) Thank you 🙇

Yah, I was missing a check to see if Schema was defined. :)

Your version will be v0.7.1 :)

I tried it out. Works like a charm thanks for the fast fix! <3


How to mark custom form control as dirty/touched?

Issue
When using the custom form control that implements Angular's ControlValueAccessor interface it isn't marked as touched/dirty when markAsDirty() method of ClrForm is called.
Code examples
component.ts
export class CorrespondenceNewModalComponent implements OnInit {
  @ViewChild(ClrForm) clrForm: ClrForm;

  form: FormGroup;

  constructor(private formBuilder: FormBuilder) {}

  ngOnInit() {
    this.buildForm();
  }

  onFormSubmit() {
    if (this.form.invalid) {
      this.clrForm.markAsDirty();
      return;
    }
  }

  private buildForm() {
    this.form = this.formBuilder.group({
      sender: [null, [Validators.required]],
      sentAt: ['', [Validators.required]]
    });
  }
}

where type, sender and receiver fields are used by custom form controls.
component.html
<form clrForm [formGroup]="form" (submit)="onFormSubmit()">

    Sender

      <app-custom-form-control formControlName="sender"></app-custom-form-control>

  <clr-date-container>
    Data wysłania
    <input
      type="date"
      class="clr-col-8"
      clrDate
      formControlName="sentAt"
    />
  </clr-date-container>

  <input type="submit" value="Save" />
</form>

custom-form-control.ts
@Component({
  selector: 'app-custom-form-control',
  templateUrl: './correspondence-contact-select.component.html',
  styleUrls: ['./correspondence-contact-select.component.scss'],
  providers: [
    {
      provide: NG_VALUE_ACCESSOR,
      useExisting: forwardRef(() => CorrespondenceContactSelectComponent),
      multi: true
    }
  ]
})
export class CustomFormControlComponent implements OnInit, ControlValueAccessor {
  disabled: boolean;
  options: any[] = [
    { value: 1, label: 'Option 1' },
    { value: 2, label: 'Option 2' }
  ];

  onChange: any = () => {};
  onTouched: any = () => {};

  ngOnInit() {}

  onSelectChange(value) {
    this.onChange(value);
  }

  writeValue(value: Contact): void {}

  registerOnChange(fn: any): void {
    this.onChange = fn;
  }

  registerOnTouched(fn: any): void {
    this.onTouched = fn;
  }

  setDisabledState?(isDisabled: boolean): void {
    this.disabled = isDisabled;
  }
}

custom-form-control.html
<ng-select bindLabel="label" bindValue="value" [items]="contacts" (change)="onSelectChange($event)"></ng-select>

In source codes of the Clarity, I found MarkControlService that seems to be used to mark controls as dirty/touched but can't figure it out how to use with custom form control or if it possible even?
Any ideas about how it can be achieved?

This is a limitation in Angular currently that is being tracked by https://github.com/angular/angular/issues/10887. I suggest looking at some of the workarounds proposed there for your form control to get an instance of your FormControl, and then be able to call the appropriate markAs methods. Also see https://stackoverflow.com/questions/44730711/how-do-i-know-when-custom-form-control-is-marked-as-pristine-in-angular.
Closing as an issue with Angular.

@gnomeontherun examples you posted works perfectly but with use FormGroup instance not ClrForm provided by the Clarity, by example:
From the previous example if I add to custom-form-control.ts file the following code (as in examples from StackOverflow you posted)
@Input() control: FormControl;

...

ngOnInit() {
    this.control.markAsTouched = function() {
      console.log('Control marked as touched');
    };
}

where control is injected using @Input() and is accessible, it works only when I call the following code from the form component (added to component.ts from the above example)
onFormSubmit() {
    if (this.form.invalid) {
      // this.clrForm.markAsDirty();
      this.markFormGroupTouched(this.form);
      return;
    }
}

private markFormGroupTouched(form: FormGroup) {
    Object.values(form.controls).forEach(control => {
      control.markAsTouched();

      if ((control as any).controls) {
        this.markFormGroupTouched(control as FormGroup);
      }
    });
}

As you can see in that scenario I don't use this.clrForm.markAsDirty() but directly controls from FormGroup instance. By this approach, I can handle markAsTouched in my custom components but the downside is that Clarity's form inputs are not marked as touch nor validation icon is shown. On the other hand, when I call this.clrForm.markAsDirty() it works the opposite way: clarity's inputs are marked as touched but my custom input doesn't receive any update at all, even using examples provided by you. It looks like the clarity's form mechanism doesn't touch at all custom form components. Correct me If I'm wrong.

The purpose of clrForm.markAsDirty() is to mark all controls as dirty in the form. For this to work correctly, you'd have to also wrap it in a Clarity form container (which we don't have a generic wrapper yet, see #2864). So unfortunately, this requires you to do the same thing by traversing the form tree and marking it as dirty (which is exactly what clrForm.markAsDirty() does). So basically, if you have a form control that isn't supported by Clarity, our API can't pick it up.
I haven't tested this with custom form components, but if you wanted to make a stackblitz demo that would help so I can actually see what you're doing.
Either way, this is turning into a how-to kind of topic which we typically handle on StackOverflow.

How can I mark a form controle as unTouched.

@azad47808 : Have you tried resetting the formControl?

@azad47808 : Have you tried resetting the formControl?


Remove sprite fixing in sprite loader

I get that backwards compatibility is something you like but the code is awful.
Not to mention how half the time when quads get changed these days they're not fixed. For example when a large number of portal elements got spritesets.
It's just visual and if people have a problem with it they should just change it back themselves.

I don't see the point of having less backwards compatibility. When bad code is hidden away in a file and is rarely executed its not much of an issue


Edit NeuralynxIO to include all valid samples from NCS files (analog signals)

These edits relate to the treatment of records with <512 valid samples, with the goal of keeping all valid samples. In particular, they fix three cases where valid samples were previously discarded:

The last record of each segment, which almost always has <512 valid samples
Segments with only one record with 512 valid samples (sandwiched between records with <512 valid samples)
Segments consisting of only one record of <512 valid samples

test_neuralynxrawio.py runs OK.

Hello @emelon8! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/rawio/neuralynxrawio.py:

Line 488:66: E261 at least two spaces before inline comment

Hi @emelon8,
thanks for proposing this enhancement of the NeuralynxIO. It works fine for me, but I think this would also require an additional test that checks the actual length of the signals read in case of a gap. Currently, the tests are mostly focussing on the existence and identification of the correct numbers of gaps, but not the data samples recovered. Could  you e.g. extend
https://github.com/NeuralEnsemble/python-neo/blob/8e53515e51eb1c9340312ade0dad32f31f5a4493/neo/test/iotest/test_neuralynxio.py#L313
to add a test that is checking the number of samples read. Maybe it even makes sense to compare to the plain representation of the data directly for this.
@samuelgarcia @sin-mike What do you think performance wise of this?

Hi @JuliaSprenger,
The plain representation (and original representation) files seem to have records with <512 valid samples already removed, so it makes it tough to test with that data. If we have good sample data that includes records with <512 valid samples, I think I could add a test for something like self.assertEqual(len(block.segments[0].analogsignals[0]), len(block.segments)*512 + num_samples_from_segs_lt_512). Not sure if that's what you're looking for or not.

Hi @emelon8,
thanks for the note, I wasn't aware that the plain data files are lacking samples of incomplete blocks. But I think this is something I can add, if @samuelgarcia and @sin-mike in general agree to the approach in this PR.

Hi @emelon8, with #905 being merged into master, the issue of not all valid samples being included might be solved already. Do you mind having a look and tell us if you are happy with the current behaviour?

Hi @JuliaSprenger, I will take a look at it soon and let you know.

@JuliaSprenger I wasn't able to import neo:
In [2]: import neo
Traceback (most recent call last):

  File "<ipython-input-2-ee05c7771214>", line 1, in <module>
    import neo

  File "D:\Programs\Anaconda\envs\neotest\lib\site-packages\neo\__init__.py", line 12, in <module>
    from neo.io import *

  File "D:\Programs\Anaconda\envs\neotest\lib\site-packages\neo\io\__init__.py", line 242, in <module>
    from neo.io.axographio import AxographIO

  File "D:\Programs\Anaconda\envs\neotest\lib\site-packages\neo\io\axographio.py", line 9, in <module>
    from neo.rawio.axographrawio import AxographRawIO

  File "D:\Programs\Anaconda\envs\neotest\lib\site-packages\neo\rawio\__init__.py", line 123, in <module>
    from neo.rawio.neuralynxrawio.neuralynxrawio import NeuralynxRawIO

  File "D:\Programs\Anaconda\envs\neotest\lib\site-packages\neo\rawio\neuralynxrawio.py", line 123, in <module>
    from neo.rawio.neuralynxrawio import NeuralynxRawIO

ImportError: cannot import name 'NeuralynxRawIO'

Checking the code, it seems there is nothing to import from neuralynxrawio.py called NeuralynxRawIO anymore. Am I missing something?

@emelon8 Sorry, there was still an inconsistency in master in the handling of the new neuralynxrawio files as this IO is now split into multiple files. Have a look at the neo/rawio/neuralynxrawio folder for orientation. If the checks of #917 are succeeding, could you check again?

@JuliaSprenger The checks didn't succeed in #917. I'm happy to check it once it's ready.

Hi @emelon8,
#917 is merged now probably also causing the conflict between your version and master. Could you check again?

Hi @JuliaSprenger, I finally got around to doing this. It looks like the analog signals from v0.9.0 and the version of v0.8.0 that I edited to keep all valid samples are identical, so I think we're good to go with the current version!

@emelon8 Thanks for checking. Since the feature seems to work for you in the current version I will close this PR for now.


updated autoinstrument as a single word

Note to @open-telemetry/docs-approvers - we have a PR open to handle this check (and auto-fix). Maybe we'd better handle all cases together, or maybe this PR can go in first. I'll let y'all review and decide.

Let's move this one in - no biggie!


How to split a big perfetto trace by given slice names?

I want to run a long time performance test, mark scene by scene trace with dedicated name.
for example:

launching_from_standard_launcher
open_folder_on_launcher

then,  I want to split this big perfetto trace by these scene name
so I can categorize perfetto trace by scenes
finally, I use dedicated trace metric to get click/swipe/zoom in,out latency,    frame metric
then generate a report about test result.
so, my question is how to split perfetto trace by given slice names?

This question has been asked many times before (most recently at https://github.com/google/perfetto/issues/656) and the answer remains the same: this is a very hard problem we don't think our resources are best deployed in solving. Please collect smaller traces in the first place.


Standalone  java spring boot application with sqs

We have a standalone java spring boot application that writes to sqs and other standalone application consuming it and processing it.
How can the producing and consuming be traced with skywalk

Do you mean AWS SQS? It depends on which client lib do you use. We have plenty of MQ plugin like kafka, activemq, you could learn from it.


Experiment with C# 11 preview of abstract static interface methods and CallerArgumentExpression as cache key

Hey.
I've implemented something very similar at work and had a few ideas I wanted to try out. Since our solutions are so similar but you have a nice benchmark setup it seemed sensible to try my ideas here and share the results.
The experiments are:

Using C# 11 preview of abstract static interface methods to eliminate the need for multiple InterpolatedStringHandlers.

Using CallerArgumentExpression in extensions methods (handlerExpr) to get the original interpolated string expression and using it as cache key. The value of handlerExpr takes the form: $"ABCD{arg1}EFGH{arg2}IJKL{arg3}MNOP{arg4}QRST{arg5}UVWX"
It doesn't seem possible to pass handlerExpr as an argument to the interpolation handler, which is a shame, since it would have allowed skipping recording anything other than the arguments.

I don't use ArrayPool in my own implementation since I'm a little scared of leaks. I only added it here for fun to get better results in the benchmark.
The experiment is a little rough and I'm not sure it's and apples to apples comparison but the results are good:
|                                          Method | IsEnabled | EnableCaching |         Mean | Ratio |   Gen0 | Allocated | Alloc Ratio |
|------------------------------------------------ |---------- |-------------- |-------------:|------:|-------:|----------:|------------:|
|                                        Standard |     False |         False |    14.748 ns |  1.00 |      - |         - |          NA |
|             InterpolatedWithManualDestructuring |     False |         False |     4.267 ns |  0.30 |      - |         - |          NA |
|  InterpolatedWithExplicitAutomaticDestructuring |     False |         False |     4.035 ns |  0.28 |      - |         - |          NA |
|  InterpolatedWithImplicitAutomaticDestructuring |     False |         False |     4.410 ns |  0.31 |      - |         - |          NA |
|            Interpolated2WithManualDestructuring |     False |         False |     4.811 ns |  0.33 |      - |         - |          NA |
| Interpolated2WithExplicitAutomaticDestructuring |     False |         False |     4.226 ns |  0.29 |      - |         - |          NA |
| Interpolated2WithImplicitAutomaticDestructuring |     False |         False |     4.594 ns |  0.32 |      - |         - |          NA |
|                                                 |           |               |              |       |        |           |             |
|                                        Standard |     False |          True |    14.830 ns |  1.00 |      - |         - |          NA |
|             InterpolatedWithManualDestructuring |     False |          True |     4.361 ns |  0.30 |      - |         - |          NA |
|  InterpolatedWithExplicitAutomaticDestructuring |     False |          True |     6.292 ns |  0.43 |      - |         - |          NA |
|  InterpolatedWithImplicitAutomaticDestructuring |     False |          True |     5.452 ns |  0.37 |      - |         - |          NA |
|            Interpolated2WithManualDestructuring |     False |          True |     5.251 ns |  0.35 |      - |         - |          NA |
| Interpolated2WithExplicitAutomaticDestructuring |     False |          True |     4.116 ns |  0.28 |      - |         - |          NA |
| Interpolated2WithImplicitAutomaticDestructuring |     False |          True |     4.173 ns |  0.27 |      - |         - |          NA |
|                                                 |           |               |              |       |        |           |             |
|                                        Standard |      True |         False | 2,889.727 ns |  1.00 | 0.7706 |    1616 B |        1.00 |
|             InterpolatedWithManualDestructuring |      True |         False | 3,973.308 ns |  1.37 | 1.3351 |    2792 B |        1.73 |
|  InterpolatedWithExplicitAutomaticDestructuring |      True |         False | 4,064.250 ns |  1.40 | 1.3351 |    2792 B |        1.73 |
|  InterpolatedWithImplicitAutomaticDestructuring |      True |         False | 4,104.125 ns |  1.43 | 1.3199 |    2760 B |        1.71 |
|            Interpolated2WithManualDestructuring |      True |         False | 2,996.425 ns |  1.04 | 0.7591 |    1592 B |        0.99 |
| Interpolated2WithExplicitAutomaticDestructuring |      True |         False | 3,039.021 ns |  1.05 | 0.7591 |    1592 B |        0.99 |
| Interpolated2WithImplicitAutomaticDestructuring |      True |         False | 2,979.040 ns |  1.03 | 0.7591 |    1592 B |        0.99 |
|                                                 |           |               |              |       |        |           |             |
|                                        Standard |      True |          True | 2,862.356 ns |  1.00 | 0.7706 |    1616 B |        1.00 |
|             InterpolatedWithManualDestructuring |      True |          True | 3,438.223 ns |  1.20 | 0.8698 |    1824 B |        1.13 |
|  InterpolatedWithExplicitAutomaticDestructuring |      True |          True | 3,287.397 ns |  1.15 | 0.8698 |    1824 B |        1.13 |
|  InterpolatedWithImplicitAutomaticDestructuring |      True |          True | 3,350.591 ns |  1.19 | 0.8850 |    1856 B |        1.15 |
|            Interpolated2WithManualDestructuring |      True |          True | 3,013.102 ns |  1.06 | 0.7591 |    1592 B |        0.99 |
| Interpolated2WithExplicitAutomaticDestructuring |      True |          True | 3,006.917 ns |  1.06 | 0.7591 |    1592 B |        0.99 |
| Interpolated2WithImplicitAutomaticDestructuring |      True |          True | 3,022.641 ns |  1.06 | 0.7591 |    1592 B |        0.99 |

Hopefully they'll expand the capabilities of interpolated string handlers in C#11. My personal wishlist includes:

Being able to pass constants to the constructor
Getting the original string expression
Guarantees on how many calls to AppendLiteral you can expect
Maybe an AppendDone method
The ability to somehow get a stack allocated Span for alloc free string composistion. There are probably more complications to this than I've thought of though.

Anyways that's it. Thanks for building this project :)

Hey.
Thank you for being interested in this project!
Using abstract static interface methods looks promising, so I will consider using this approach when C# 11 is released.
I have also considered using CallerArgumentExpression in extensions methods to get the original interpolated string expression and using it as cache key. But while it provides a good performance, unfortunately it is not compatible with the value representation policies other than the default one. If a value representation policy returns Destructure or Stringify for some argument, ISLE has to build the message template from scratch. Even worse, if two places in code use the same interpolated string with arguments of different types, the resulting message templates may be different. That's why the current cache implementation is done in a form of a tree. By the way, there will be some optimizations of it in version 1.4.
I agree that it would be great to have interpolated string handler enhancements you've mentioned. It would also be nice to have duck-typed dispose method, to prevent memory leaks in case some pool (e.g. ArrayPool) is used and exception is thrown while executing the handler.

But while it provides a good performance, unfortunately it is not compatible with the value representation policies other than the default one

I'm no expert on Serilog (at all), but I browsed the code while looking for the most optimal way to call it, and in Serilog the call flow looks like:
Logger.Write (or Logger.BindMessageTemplate) ->
MessageTemplateProcessor.Process ->
MessageTemplateCache.Parse
MessageTemplateCache.Parse does a lookup on the raw template string passed to the top-level Write in a hashtable and returns a MessageTemplate.
And in the subsequent call to ConstructProperties it only references the template to determine the number of expected parameters.
So it looks like Serilog itself does the same caching, and I decided to build on top of that by simply building a new Seri-friendly template string in my interpolated string handler and just pass that to Serilog.
And that's where the CallerArgumentExpression comes into play, I use it in a simple <string,string> dictionary to map the CallerArgumentExpression to the Seri-friendly string.
For now I just add @ to all arguments in the template I build and it works well, but it's not in heavy use yet, so I might run into some of the problems you mention.


HystrixPlugins#get methods write and cause setters to fail

Hi,
we just came across an issue with the way com.netflix.hystrix.strategy.HystrixPlugins handles its references:
The issue occurred during unit testing using Spring and SpringRunner. We had one test setting a metrics publisher in the spring context and another one where apparently somewhere in the hystrix integration getMetricsPublisher was called.
While - if test where run in the sequence as above this was working fine - our CI server executed them in reverse order. This resulted in an exception thrown as the second test had transparently set the metrics publisher. Given the static nature of the HystrixPlugin issues like this can happen in various ways.
Ideally I believe that this kind of static access should not appear at all (at least not in the API). Also getters that are actually changing state seam to be not that ideal to me. Yet as I'm not too familiar with the internal structure of Hystrix I'm not sure if it can easily be tweaked to make this less error prone.
Fortunately this seems to be mainly a test issue rather than a production risk. But any suggestions to solve this issue (rather than push it to occur again with the next test using Hystrix) is highly appreciated.
-Christian

I was just hit by the same problem. One dirty workaround - call HystrixPlugins.reset as cleanup after every test class.
Another idea I expected would work, but unfortunately does not, was to configure hystrix.plugin.HystrixMetricsPublisher.implementation to reference class like com.netflix.hystrix.contrib.servopublisher.HystrixServoMetricsPublisher. Problem is that HystrixPlugins tries to instantiate configured implementation via no-arg constructor (see here), while HystrixServoMetricsPublisher as well as default HystrixMetricsPublisherDefault have private constructor and instead they just have singleton factory method, getInstance.
HystrixServoMetricsPublisher docs example (see here) uses registerMetricsPublisher method but that one if called multiple times will throw exception, and getMetricsPublisher as you noted has nasty side-effect that it will create configured or default metrics publisher plugin.
Since I'm configuring one Hystrix plugin only, metrics publisher one, instead of changing all the tests to reset, I've changed production code which registers metrics publisher to reset HystrixPlugins first before registering the sole plugin.

I agree with you on the design of HystrixPlugins being less than ideal.  It's fairly difficult to make a change in this area, as the methods you named are public and wired in to application startup in many projects which use Hystrix (including our internal ones).
I think it's plausible to work on a better solution and then deprecate this style, but it's a fair amount of work for a small return.
I'd love to hear concrete ideas on how this should look.

Closing due to inactivity


Category names collide with SRWebSocket categories

If you use both Mixpanel and SRWebSocket in a project, the following categories are defined by both projects and so produce warnings (in Xcode 7.1, at least):
NSURLRequest (CertificateAdditions)
NSMutableURLRequest (CertificateAdditions)

They don't actually define any colliding method names (since the methods themselves are prefixed SR_ and mp_) so I'm not sure what the runtime consequences are for this. Even if harmless, it would be nice to resolve the warning.
Can they be changed to, e.g., MPCertificateAdditions?

Thanks, we'll get this changed in the next release.

Resolved in #402


reenabled pr-env-setup fot test prejob on streaming job

PR to test the pre_job condition in the streaming-job.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Lasse Ringgren Nielsen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


VM: Flaky service test service/async_next_test on Win64

@johnmccutchan @rmacnak-google
Have you seen this one failing before?
=== Failure summary:
FAILED: none-vm release_x64 service/async_next_test
Expected: Pass
Actual: RuntimeError
CommandOutput[vm]:
stdout:
** Launching build\ReleaseX64\dart.exe --error_on_bad_type --error_on_bad_override --verbose_debug --ignore-unrecognized-flags --package-root=build/ReleaseX64/packages/ --enable-vm-service:0 E:\b\build\slave\vm-win64-release-be\build\sdk\runtime\observatory\tests\service\async_next_test.dart --testee-mode
Observatory listening on http://<IP_ADDRESS>:60051
** Signaled to run test queries on 60051

single step break at file:///E:/b/build/slave/vm-win64-release-be/build/sdk/runtime/observatory/tests/service/async_next_test.dart:14 (func <doAsync_async_body> token 44)
Running async_next_test.dart [1/9]
Breakpoint reached
Running async_next_test.dart [2/9]
Checking we are at line 14
Running async_next_test.dart [3/9]
Resolved BP for function 'file:///E:/b/build/slave/vm-win64-release-be/build/sdk/runtime/observatory/tests/service/async_next_test.dart_::doAsync<doAsync_async_body>' at line 12
hit user breakpoint at file:///E:/b/build/slave/vm-win64-release-be/build/sdk/runtime/observatory/tests/service/async_next_test.dart:12 (token 26) (address 0x3bef6ef)
Running async_next_test.dart [4/9]
single step break at file:///E:/b/build/slave/vm-win64-release-be/build/sdk/runtime/observatory/tests/service/async_next_test.dart:15 (func <doAsync_async_body> token 51)
Event: ServiceEvent(owner='isolates/172217569', kind='PauseBreakpoint')
Breakpoint reached
Running async_next_test.dart [5/9]
Checking we are at line 15
Running async_next_test.dart [6/9]
** Killing script
Unexpected exception in service tests: Exception: No async continuation available null

stderr:
Unhandled exception:
Uncaught Error: Exception: No async continuation available
#0      _rootHandleUncaughtError. (dart:async/zone.dart:894)
#1      _microtaskLoop (dart:async/schedule_microtask.dart:43)
#2      _microtaskLoopEntry (dart:async/schedule_microtask.dart:52)
#3      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:96)
#4      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:149)
Command[vm]: set DART_CONFIGURATION=ReleaseX64 & build\ReleaseX64\dart.exe --error_on_bad_type --error_on_bad_override --verbose_debug --ignore-unrecognized-flags --package-root=build/ReleaseX64/packages/ E:\b\build\slave\vm-win64-release-be\build\sdk\runtime\observatory\tests\service\async_next_test.dart
Took 0:00:01.717000
Short reproduction command (experimental):
python tools/test.py -mrelease -ax64 --write-debug-log --write-test-outcome-log --copy-coredumps --exclude-suite pkg -t60 service/async_next_test
===
=== 1 test failed

FYI- @turnidge
The service tests started flaking last week. Will investigate this week.
Thanks,
John


Improve e2e test infrastructure

@kyessenov commented on Thu Apr 13 2017
The integration test framework has served well but we're at the limits of what it can do. Here is the call to identify any gaps in the e2e test coverage so that we can set the goals towards building a more robust test framework. Feel free to edit this issue and add more items or mark the completed items.
Framework:

[x] common deploy, setup, run, log checking, teardown workflow for tests
[ ] more reliable config propagation than waiting a few seconds
[ ] ability to stress any feature by increasing load, repeat count
[x] test matrix to exercise feature combinations: TCP for auth, HTTP ingress for non-auth, route-splitting with auth, auth with http2 auto-upgrade, etc
[x] stabilize flaky mixer log checking due to mixer dependency, e.g. using a fake mixer
[x] full log aggregation on failures
[x] reduce log noise in debug mode
[x] ability to run subsets of tests. Useful for debug/development and if test needs to be run in parallel across multiple clusters.
[ ] collect core dumps from envoy crashes
[ ] make liveness probes optional to avoid crash loops

Proxy:

[x] verify proxy with basic fixed configurations
[x] verify traffic redirection (i.e. iptables)
[ ] regression stress tests for envoy hot restart protocol

Reachability:

[x] assert two proxies on self-loops ("a" to "a")
[x] add more pods to exercise route tables for <IP_ADDRESS>:port
[ ] assert correct ports are reached
[x] grpc and http2 ports in the test app
[ ] validate that NodePort and LoadBalancer services work

Ingress:

[x] verify multiple paths in the ingress
[x] plaintext ingress
[x] TLS in ingress
[x] route rules applied to ingress services
[x] missing paths should return 404

Egress:

[x] HTTP single-port ExternalName service reachability
[x] HTTPS single-port ExternalName service reachability
[x] route rules applied to egress services

Auth:

[x] negative test to ensure protocol is upgraded
[ ] attempt to connect to a pod that doesn't belong to a service as if it belongs to a service

Routing:

[x] source service based routing
[x] exact header based routing
[x] regex header based routing
[x] prefix header based routing
[x] multi-condition based routing
[x] fault injection: delay, abort
[x] weighted route
[x] rule precedence
[ ] http timeout policy
[ ] http retry policy

Destination policies:

[ ] per service version policy
[ ] circuit breaking policy
[ ] load balancing policy

@rshriram commented on Tue Apr 18 2017
Some of the routing tests (circuit breakers, retries, timeouts) will be difficult to test in our framework reliably. E.g., a circuit breaker might need in excess of 100s of req/s in order to be tripped. An outlier detection configuration would require one or more hosts to go down in a particular order in order to be activated.
It would be equivalent to testing Envoy's functionality rather than our configuration, won't it?
We could test these configurations with *.golden files.. And we already do for several of them.

@kyessenov commented on Mon Aug 14 2017
this can be further improved

cc @nmittler for the ancient issue tracking integration tests in pilot.

@kyessenov excellent! Ancient bugs are the best bugs!

Closing as a duplicate of https://github.com/istio/istio/issues/4545


We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like None is not the path to a directory containing a file named config.json.

再使用miluvs向量数据库，上传文件的是很好提示下面
We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like None is not the path to a directory containing a file named config.json.
目前自己使用的ll模型，embedding 模型和rerank模型都是离线安装的模型，不存再需要调用https://huggingface.co
We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like None is not the path to a directory containing a file named config.json. Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'. 文档切分示例：page_content='392.0\n应收款项减值账务处理' metadata={'source': '/mnt/sdc/Langchain-Chatchat/knowledge_base/kaokao/content/aaa391.xlsx'} Batches:   0%|                                                                                | 0/3 [00:00<?, ?it/s]We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like None is not the path to a directory containing a file named config.json. Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'. 文档切分示例：page_content='512.0\n股权溢价购入怎么纳税?' metadata={'source': '/mnt/sdc/Langchain-Chatchat/knowledge_base/kaokao/content/aaa511.xlsx'} We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like None is not the path to a directory containing a file named config.json. Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'. 文档切分示例：page_content='482.0\n个人社保费要不要计提?' metadata={'source': '/mnt/sdc/Langchain-Chatchat/knowledge_base/kaokao/content/aaa481.xlsx'} We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like None is not the path to a directory containing a file named config.json.

怎么解决的呢


nixos: fix fallout from #27688

A typo. Please test with
@GrahamcOfBorg test virtualbox.headless

It conflicts with a committed solution which is the same up to whitespace.