Discord, webcam, usb device resetting

Bug description:
When activating the discord service I see permanent resets of my webcam USB device, that is every 5sec I see the following in the syslog
Jun 24 10:11:07 bulldog kernel: usb 1-6: reset high-speed USB device number 3 using xhci_hcd
Jun 24 10:11:07 bulldog kernel: restoring control 00000000-0000-0000-0000-000000000101/10/5
Jun 24 10:11:07 bulldog kernel: restoring control 00000000-0000-0000-0000-000000000101/12/11

Disabling the service immediately stops these permanent resets.
Steps to reproduce:

Connect a webcam (mine is Logicool)
Activate discord service
Look into the journallog

Expected behavior
No resets.
Environment:

Operating System: Linux (Debian/sid), kernel 5.7.5, 5.8.0-rc2

Ferdi Version: 5.6.0-beta.2 (x65, electron 8.2.3, node 12.13.0)

Server: Ferdi

Debug information:

{"host":{"platform":"linux","release":"5.8.0-rc2","screens":[{"id":SOMEID,"bounds":{"x":0,"y":0,"width":1920,"height":1080},"workArea":{"x":0,"y":0,"width":1920,"height":1053},"accelerometerSupport":"unknown","monochrome":false,"colorDepth":24,"colorSpace":"{primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}","depthPerComponent":8,"size":{"width":1920,"height":1080},"workAreaSize":{"width":1920,"height":1053},"scaleFactor":1,"rotation":0,"internal":false,"touchSupport":"unknown"}]},"ferdi":{"version":"5.6.0-beta.2","electron":"8.2.3","installedRecipes":[{"id":"discord","version":"1.1.3"},{"id":"gitter","version":"1.0.2"},{"id":"linkedin","version":"1.0.0"},{"id":"mastodon","version":"1.1.2"},{"id":"messenger","version":"1.1.0"},{"id":"slack","version":"1.0.15"},{"id":"tweetdeck","version":"1.0.2"},{"id":"whatsapp","version":"2.0.5"},{}],"devRecipes":[],"services":[{"id":"SOMEID","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"discord","isAttached":true,"isActive":true,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"gitter","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"linkedin","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"whatsapp","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"messenger","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"tweetdeck","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"mastodon","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false},{"id":"SOMEID","recipe":"slack","isAttached":true,"isActive":false,"isEnabled":true,"isHibernating":false,"hasCrashed":false,"isDarkModeEnabled":false}],"messages":[{"type":"error","info":["error","[mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: 'Reaction[Autorun@160]'",{}]},{"type":"error","info":["error","Warning: Failed prop type: Invalid prop `showMessageBadgeWhenMutedSetting` of type `string` supplied to `_class2`, expected `boolean`.\n    in _class2 (created by _class2)\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by _class2)\n    in div (created by _class2)\n    in div (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in _class2 (created by Jss(_class2))\n    in Jss(_class2) (created by _class2)\n    in ThemeProvider (created by _class2)\n    in _class2 (created by inject-_class2-with-stores-actions)\n    in inject-_class2-with-stores-actions (created by RouterContext)\n    in RouterContext (created by Router)\n    in Router (created by _class)\n    in _class (created by inject-_class-with-stores-actions)\n    in inject-_class-with-stores-actions\n    in IntlProvider (created by _class)\n    in _class (created by inject-_class-with-stores)\n    in inject-_class-with-stores\n    in Provider"]},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"getInfo"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"features"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","request":{"result":null,"wasExecuted":true,"method":"all"},"error":{},"response":{},"server":"https://api.getferdi.com"},{"type":"error","info":["error","Warning: You cannot PUSH the same path using hash history"]},{"type":"error","info":["error","Warning: Cannot update during an existing state transition (such as within `render`). Render methods should be a pure function of props and state."]}],"workspaces":[],"windowSettings":{"width":1415,"height":962,"x":53,"y":29,"displayBounds":{"x":0,"y":0,"width":1920,"height":1080},"isMaximized":false,"isFullScreen":false},"settings":{"autoLaunchInBackground":false,"runInBackground":true,"reloadAfterResume":true,"enableSystemTray":true,"startMinimized":false,"minimizeToSystemTray":"","privateNotifications":false,"showDisabledServices":"","showMessageBadgeWhenMuted":"","showDragArea":false,"enableSpellchecking":"","spellcheckerLanguage":"en-us","darkMode":false,"locale":"en-US","fallbackLocale":"en-US","beta":false,"isAppMuted":false,"enableGPUAcceleration":"","serviceLimit":5,"server":"https://api.getferdi.com","predefinedTodoServer":"https://app.franztodos.com","autohideMenuBar":false,"lockingFeatureEnabled":false,"locked":false,"lockedPassword":"******","useTouchIdToUnlock":true,"scheduledDNDEnabled":false,"scheduledDNDStart":"17:00","scheduledDNDEnd":"09:00","hibernate":false,"hibernateOnStartup":true,"hibernationStrategy":300,"inactivityLock":0,"automaticUpdates":true,"showServiceNavigationBar":false,"universalDarkMode":true,"adaptableDarkMode":true,"accentColor":"#7367f0","serviceRibbonWidth":68,"iconSize":20,"sentry":false,"navigationBarBehaviour":"never","customTodoServer":"","todoServer":"isUsingCustomTodoService"},"features":{"isSpellcheckerIncludedInCurrentPlan":true,"needToWaitToProceed":false,"needToWaitToProceedConfig":{"delayOffset":3600000,"wait":10000},"isServiceProxyEnabled":true,"isServiceProxyIncludedInCurrentPlan":true,"isAnnouncementsEnabled":true,"isWorkspaceIncludedInCurrentPlan":true,"isWorkspaceEnabled":true,"isCommunityRecipesIncludedInCurrentPlan":true,"isSpellcheckerPremiumFeature":false,"isServiceProxyPremiumFeature":true,"isWorkspacePremiumFeature":false,"isSettingsWSEnabled":false,"isServiceLimitEnabled":false,"serviceLimitCount":0,"isCommunityRecipesPremiumFeature":false,"isCustomUrlIncludedInCurrentPlan":true,"isMagicBarEnabled":true,"isTeamManagementIncludedInCurrentPlan":true,"isTodosEnabled":true,"isTodosIncludedInCurrentPlan":true,"defaultTrialPlan":"franz-pro-yearly","subscribeURL":"https://getferdi.com","planSelectionURL":"https://getferdi.com","hasInlineCheckout":true,"isPlanSelectionEnabled":false,"isTrialStatusBarEnabled":false,"canSkipTrial":true,"pricingConfig":{"currency":"$","currencyID":"USD","plans":{"personal":{"monthly":{"id":"ferdi-free","price":0,"billed":0},"yearly":{"id":"ferdi-completely-free","price":0,"billed":0}},"pro":{"monthly":{"id":"ferdi-still-free","price":0,"billed":0},"yearly":{"id":"ferdi-forever-free","price":0,"billed":0}}}}},"user":"SOMEID"}}

The issue is still relevant. For the time being I have switched to the discord app.


Android - Using MessagingPlugin.SmsMessenger.SendSms pass the message to default app instead of sending

If I use MessagingPlugin.SmsMessenger.SendSms the message is pass to the default app (hangout for instance) and never sent (using the intent, it is up to the default app to react to it)
Using SmsManager does send the message directly, but needs permission to do so (SEND_SMS).
Would it be possible to flag what method we would like to use on android platform?
Thanks.

If I understand your correctly, you want the ability on the plugin to use either the Intent or SmsManager for sending the SMS?

No further feedback


Change transpiler from Babel to ESBuild

@Domino987 just wanted to let you know I was able to get esbuild working correctly.
We now use esbuild to transple vs babel.
I went ahead and updated the website to use the new version (v3.2.1 is transpiled with esbuild), so that should tell us if there are any issues.
FYI.

Edit: nevermind switched back to babel.. I think in order to use esbuild we would have to bundle as esm, not cjs. But it looks like babel transpiles to cjs, so I'm even more confused as to why it's not working.


VS Code doesn't inform why the file wasn't renamed

VSCode Version: 1.31.1
OS Version: Windows 10

Steps to Reproduce:

Open a folder with VS Code. The folder should contain the file you want to rename, say it's a.txt.
Open a.txt with another application (I gave it as input to a program running with Visual Studio).
While the program is running, try to rename the file in VS Code source tree.

Result: The file is not renamed (as it's used by another application) but there's no way to know why it wasn't renamed.
Expected result: The file is not renamed and a message box appears (or in some other way) to inform that the file cannot be renamed as it is being used by another application.

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

This is probably an electron issue that the rename error is not popping up.
Right @bpasero ?
We had a similar thing for the delete error

@isidorn negative, the "file does not move to trash" error is Linux/Electron specific due to the usage of the trash.


chore: migrate to dynamic config, add custom gradle plugin

We need to bump the java heap space to ensure both the main and example apps build correctly. The conventional way to do this is by using an expo config plugin. We weren't having much luck using the static config file (app.json) to get this working, so we added app.config.ts to allow for dynamic config.
This adds all the nuts and bolts required to get that working and bump the java heap space correctly. The config remains unchanged in the dynamic file, with the exception of adding the custom plugin that bump the heap size for Java.

Sub-task found while debugging this one: https://github.com/PlayerData/react-native-mcu-manager/pull/412

Self Review:

[ ] Appropriate test coverage
[ ] Relevant Documentation updated

Smoke Tests:

[x] Build runs successfully

Huh, I hadn't noticed the duplicated value. I would've thought it'd be smart enough to overwrite an existing key if it already exists. I can't spot anything useful in the documentation, and yeah I do think the injected value takes precedence, so it should be okay.


Make plugin Github template

Floneum should provide a Github template to make getting started creating a plugin easier

Template is live here


Crash causing broken node: FAIL:  Service snap.microk8s.daemon-apiserver is not running

Hi,
we have a 3 node deployment of microk8s, and now experienced multiple time the issue that one of our nodes dies and consequentaly doesnt start up anymore with the status FAIL:  Service snap.microk8s.daemon-apiserver is not running
The only fix so far is to leave (remove node) and rejoin the node.
before the crash this happend according to our syslog.
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-apiserver[10675]: kube-apiserver: src/db.c:40: db__open_follower: Assertion `db->follower == NULL' failed.
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786811   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1beta1.PodSecurityPolicy ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786810   14899 reflector.go:424] k8s.io/client-go/metadata/metadatainformer/informer.go:90: watch of *v1.PartialObjectMetadata ended with: very short watch: k8s.io/client-go/metadata/metadatainformer/informer.go:90: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786820   14899 reflector.go:424] k8s.io/client-go/metadata/metadatainformer/informer.go:90: watch of *v1.PartialObjectMetadata ended with: very short watch: k8s.io/client-go/metadata/metadatainformer/informer.go:90: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786853   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.Namespace ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786873   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.ServiceAccount ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786893   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.ControllerRevision ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786933   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.VolumeAttachment ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.786971   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.Role ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787035   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.LimitRange ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787070   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1beta1.RuntimeClass ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787081   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1beta1.EndpointSlice ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787106   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.CertificateSigningRequest ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787113   14899 reflector.go:424] k8s.io/client-go/metadata/metadatainformer/informer.go:90: watch of *v1.PartialObjectMetadata ended with: very short watch: k8s.io/client-go/metadata/metadatainformer/informer.go:90: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787177   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1beta1.Ingress ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-controller-manager[14899]: W1002 13:16:53.787246   14899 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.Lease ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m systemd[1]: snap.microk8s.daemon-apiserver.service: Main process exited, code=killed, status=6/ABRT
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787417   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.Pod ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787449   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.Node ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787417   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.PersistentVolume ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787478   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.ReplicationController ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787482   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.StatefulSet ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787497   19939 reflector.go:424] k8s.io/kubernetes/cmd/kube-scheduler/app/server.go:188: watch of *v1.Pod ended with: very short watch: k8s.io/kubernetes/cmd/kube-scheduler/app/server.go:188: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787504   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.ReplicaSet ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m systemd[1]: snap.microk8s.daemon-apiserver.service: Failed with result 'signal'.
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787418   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.PersistentVolumeClaim ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787418   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.StorageClass ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787417   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.CSINode ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787437   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1beta1.PodDisruptionBudget ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:53 k8s-prod-m microk8s.daemon-scheduler[19939]: W1002 13:16:53.787482   19939 reflector.go:424] k8s.io/client-go/informers/factory.go:134: watch of *v1.Service ended with: very short watch: k8s.io/client-go/informers/factory.go:134: Unexpected watch close - watch lasted less than a second and no items received
Oct  2 13:16:54 k8s-prod-m systemd[1]: snap.microk8s.daemon-apiserver.service: Service RestartSec=100ms expired, scheduling restart.
Oct  2 13:16:54 k8s-prod-m systemd[1]: snap.microk8s.daemon-apiserver.service: Scheduled restart job, restart counter is at 10.

Hi @Aaron-Ritter
I think you are affected by the issue reported in https://github.com/ubuntu/microk8s/issues/1598
We have a few fixes we are evaluating right now in the latest/edge channel. You could follow that channel with:
sudo snap refresh microk8s --channel=latest/edge

We have also this node recovery page [1] you may want to follow instead of a leave & rejoin.
Apologies for the inconvenience. As soon as we release a patch your nodes should get the fix automatically.
[1] https://discuss.kubernetes.io/t/recovery-of-ha-microk8s-clusters/12931

Thanks @ktsakalozos
The restore procedure is so far much "simpler" we can run leave on the failed node and remove the failed node on one of the still running nodes and then rejoin it which will sync back the status. And this while everything is still up and running.
But this is a production cluster, the question is if its maybe simpler to just disable ha-cluster for now? I am not to keen to switch to latest/edge channel as maybe other things are breaking.

I just got the exactly same issue. leaving and re-adding works for me too.

I've got almost the same issue.
Logs:
Oct 02 19:21:26 master-1 microk8s.daemon-apiserver[3841]: I1002 19:21:26.755749    3841 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/1710/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Oct 02 19:21:26 master-1 microk8s.daemon-apiserver[3841]: I1002 19:21:26.755798    3841 clientconn.go:948] ClientConn switching balancer to "pick_first"
Oct 02 19:22:05 master-1 microk8s.daemon-apiserver[3841]: I1002 19:22:05.909342    3841 client.go:360] parsed scheme: "passthrough"
Oct 02 19:22:05 master-1 microk8s.daemon-apiserver[3841]: I1002 19:22:05.911822    3841 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/1710/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}
Oct 02 19:22:05 master-1 microk8s.daemon-apiserver[3841]: I1002 19:22:05.912009    3841 clientconn.go:948] ClientConn switching balancer to "pick_first"
Oct 02 19:22:42 master-1 microk8s.daemon-apiserver[3841]: I1002 19:22:42.285192    3841 client.go:360] parsed scheme: "passthrough"
Oct 02 19:22:42 master-1 microk8s.daemon-apiserver[3841]: I1002 19:22:42.285345    3841 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{unix:///var/snap/microk8s/1710/var/kubernetes/backend//kine.sock  <nil> 0 <nil>}] <nil> <nil>}

Hi @Aaron-Ritter
I think you are affected by the issue reported in #1598
We have a few fixes we are evaluating right now in the latest/edge channel. You could follow that channel with:
sudo snap refresh microk8s --channel=latest/edge

We have also this node recovery page [1] you may want to follow instead of a leave & rejoin.
Apologies for the inconvenience. As soon as we release a patch your nodes should get the fix automatically.
[1] https://discuss.kubernetes.io/t/recovery-of-ha-microk8s-clusters/12931

Yes, i was facing same issue in centos8. After 12 hours of using --channel=latest/edge, some forced shutdown and reboots, the cluster is stable.

Hi @eestevez
maybe a small update:

only autoupgrade snap once a month as this has caused issues during upgrades
try to do a controlled upgrade before the automated one
currently upgradet to version v1.19.2-34+17ab8bf53eaae0
updating the bios of the physical server because we had some network interface errors making the vms unstable and therefore microk8s cluster

So far we didnt have to rejoin a node, it always recovered it self when there was a issue.

Hi @eestevez
maybe a small update:

only autoupgrade snap once a month as this has caused issues during upgrades
try to do a controlled upgrade before the automated one
currently upgradet to version v1.19.2-34+17ab8bf53eaae0
updating the bios of the physical server because we had some network interface errors making the vms unstable and therefore microk8s cluster

So far we didnt have to rejoin a node, it always recovered it self when there was a issue.

Hi @Aaron-Ritter
Thanks for your update.
Currently i am using v1.19.3-34+7b6ae8c49964e8  (1763), but unfortunately version 1.19/stable(1769) did't work in my centos8 VMs.

@eestevez v1.19.2-34+17ab8bf53eaae0 is a latest/edge build

with the latest fixes introduced through #1598 its much more stable. I'll close this issue as the other one remains open.


Fix white rabbit on Linux, change "Keybase & Contacts" on desktop

cc @keybase/react-hackers @keybase/picnicsquad
Made a separate ContinueButton component so we can use unicode emoji characters on mobile but Kb.Emoji objects on desktop. This is to keep things consistent across platforms - some Linux distributions do not include emoji fonts, and if they do, the quality varies. Using Kb.Emoji ensures that same rabbit emoji will be displayed everywhere. But Kb.Emoji inside of Kb.Button does not seem to render on mobile.

cc @keybase/react-hackers ready for review, it's not needed for mobile release but it would be great if we could get it in for PC. Look into squad-picnic Keybase channel to see what the issue is about


create command kills terminal

Summary
with version v1.2.5 gopass create crashes my terminal. i run st (simple terminal). in gnome-terminal it works just fine.
i get this error:
X Error of failed request:  BadLength (poly request too large or internal Xlib length error)   Major opcode of failed request:  139 (RENDER)   Minor opcode of failed request:  20 (RenderAddGlyphs)   Serial number of failed request:  1942   Current serial number in output stream:  1965
it looks like its a problem with the emojis.
i know this is maybe not a real gopass problem... but i have no problems with emojis so far in my terminal... i think maybe someone has an idea about it.
Steps To Reproduce
gopass create
Environment

OS: Ubuntu 18.04
OS version: 5.4.0-65-generic #73~18.04.1-Ubuntu
gopass Version: 1.12.5
Installation method: brew and go get

i just read in the FAQ of st that this is a bug in Xft. Can there be a option to disable emojis in gopass maybe?

i can even break it down to this emoji: "🧪". ok... this sucks ;-) i mean not gopass... just st terminal here.

Hmm, sorry for that. st is supposed to support UTF-8.
Right now we don't have an option to disable emojis.
Personally I mostly use gopass in a terminal without UTF-8 support and besides producing some empty boxes I've never seen any issues with that.

but this is really not the problem of gopass... its wonderful as it is (even if the no symbols env variable is nice)... its a problem with Xft. i took this problem to move from st terminal to alacritty... finally a reason to try something new :) no problems with gopass create in alacritty.


Add warning banner to state v2 docs

We had a customer accidentally reading the v2 docs which caused some confusion.
This PR adds a warning banner that the user is reading v2 docs.

Oh there's a typo in Captcha


[Bug][Manager] Delete data grouping exception

What happened

What you expected to happen
There should be no exception
How to reproduce
Just delete an InlongGroup
Environment
centos
InLong version
master
InLong Component
InLong Manager
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Was fixed in UpdateGroupCompleteListener class.


Heat transfer assembler

This PR takes care of refactoring assemblers in heat transfer solver.
Three separate assemblers, namely core assembler, BDF and Robin BC assemblers are defined.

All comments are applied. Viscous dissipation is defined in a separate assembler, and multiphysics parameters is used instead of simulation parameters.

@shahabgol  There are two conflicts to handle, please merge or rebase

There still seems to be some conflicts to fix, we can talk about it this week if you need help :)!

There still seems to be some conflicts to fix, we can talk about it this week if you need help :)!

Fixed. :)


applicationref.tick is called recursively

I updated from 2.3.0 to the latest and got this error: 'Applicationref.tick is called recursively'. It appears when I drop item first time, after this everything works ok. I checked on older versions and everything works on 2.3.3 and after that version getting the same error.

Hi @Prontsevich
please provide the plunkr that reproduces the problem.

closing for inactivity

I also have the same problem. No time to build a plunkr, but it happens when I a sort material grid, which is deeply nested, and with options to have the same group:
<mat-grid-list cols="4" rowHeight="16:9">     <mat-grid-tile [sortablejs]="data.photos" [sortablejsCloneFunction]="sortableClone" [sortablejsOptions]="gridSortOptions" *ngFor="let image of data.photos"><img [src]="image.url" style="width: 100%"></mat-grid-tile> </mat-grid-list>


Readme.md

'components' => [
...
'sendGrid' => [
'class' => 'bryglen\sendgrid\Mailer',
'username' => 'your_user_name',
'password' => 'your password here',
//'viewPath' => '@app/views/mail', // your view path here
],
...
],
class here is wrong

Whats wrong?
Sent from my iPad

On 2 Apr 2016, at 3:24 AM, BP<EMAIL_ADDRESS>wrote:
'components' => [
...
'sendGrid' => [
'class' => 'bryglen\sendgrid\Mailer',
'username' => 'your_user_name',
'password' => 'your password here',
//'viewPath' => '@app/views/mail', // your view path here
],
...
],
class here is wrong
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

When I downloaded it with composer the class in composer.json autoload psr4 was different than 'class' => 'bryglen\sendgrid\Mailer'. Now it's all good


Rare sat hunting workflow: Cycle funds through exchange wallet

An easy sat hunting workflow is to:

withdraw money from an exchange
separate out collectable sats
send non-collectable sats back to the exchange
repeat

This issue can be closed when this workflow is reasonably easy. We might not have a built-in command to do this whole workflow, but doing it manually shouldn't be too much of a pain.
A good first step that would make progress on this is to try it manually, and see how hard it is, where people might get stuck, and how to improve it. Then we could stat implementing those improvements.

Rare sat hunting isn't a huge priority, so closing for now.


repeatWhen missing?

https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/repeatwhen.md

As migration guide states, not all of operators are migrated into RxJS5 yet. (just noticed retryWhen is missing in table though..)

I think this operator was added recently to RxJS4: https://github.com/Reactive-Extensions/RxJS/commit/871f6d31315366e62a8e372b68e29fed1e5b398d

Ah, that's reason migration guide does not include it yet maybe? :)

@kwonoj I think we need to update the table, especially for variant overloads such as .catch is missing the .catch(...Observables) overload

@mattpodwysocki Yes, current migration document are somewhat fall behind compare to current status. Need to be updated.

@mattpodwysocki since catch(...observables) will be wildly different in it's internals from catch(fn) we should probably follow the suit of map/mapTo and implement it separately. catch performs pretty well right now. What do you think? I must say that catchTo seems ugly, maybe catchWith or something? Or even errorTo, I dunno?
Thoughts?

repeatWhen exists now.


Use Only Enabled Witnesses For Scheduling

Witness scheduling currently looks at all witnesses and that causes some bugs. This PR changes to only using enabled witnesses to determine scheduling and fix the bug.

Unblocks https://github.com/hive-engine/hivesmartcontracts/pull/37

This looks good to me, fairly straightforward.


ADS disconnects and cannot connect

Type: Bug
Continuously adjusting a query and rerunning ends up in ADS not responding commands - query starts but never returns result set and cancel does not respond anymore. Disconecction works and connection does not work.
Azure Data Studio version: azuredatastudio 1.45.1 (88c21b1725a3e79440027bdb7b5a55fb036be0e2, 2023-08-03T00:42:56.773Z)
OS version: Darwin arm64 22.6.0
Restricted Mode: No
Preview Features: Enabled
Modes:

System Info

Item
Value

CPUs
Apple M1 Pro (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
5, 4, 4

Memory (System)
32.00GB (0.04GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

profiler
Mic
0.14.0

sql-prompt
Red
0.2.12

poor-sql-formatter
WSR
0.1.0

@mindit-alexandru-puiu can you try the latest release 1.46.1 and see if this still happens?

Not enough information to investigate issue, closing as inactive.


Site Support Request:porndig.com

Hi,
Possible to have porndig.com in the process, thanks ;o)
bye

Post an example URL.

Hi,
here is the sampel:
./youtube-dl http://www.porndig.com/videos/49609/lilyan-is-a-beautiful-redhead-in-a-casting.html
[generic] lilyan-is-a-beautiful-redhead-in-a-casting: Requesting header
WARNING: Falling back on generic information extractor.
[generic] lilyan-is-a-beautiful-redhead-in-a-casting: Downloading webpage
[generic] lilyan-is-a-beautiful-redhead-in-a-casting: Extracting information
ERROR: Unsupported URL: http://www.porndig.com/videos/49609/lilyan-is-a-beautiful-redhead-in-a-casting.html
thanks :o)

This looks like copyrighted content. youtube-dl does not support sites dedicated to copyright infringement. Do they have rights to distribute this? If not provide an example URL that does not violate any copyrights.

In the "Studios" section of the site there are a good amount of videos offered by the producer studios.
Here's an example (notice the banner over the video, in the first seconds of it):
http://www.porndig.com/videos/45972/valeri-bianco-is-a-sensual-brunette.html
Something I noticed about PornDig, maybe useful if the support get implemented, is that to download the videos with Python the site seems to require an explicit declaration of the referer (but I've done just a few tests, so it's possibile I'm wrong on that).
One last thing: some time ago I found some kind of twin site of PornDig: www.tukif.com
I suppose eventually adding support to it would be trivial, if PornDig gets added.
Here's a video example on this other site (same video as the PornDig example):
http://www.tukif.com/videos/45804/valeri-bianco-une-brunette-ravissante-a-voir.html
This is my first message here, so thanks for all the efforts of the Youtube-dl contributors!

Is it possible to add http://videos.apornstories.com/ website to youtube-dl? They have own videos and videos from other tubes.


Update Java JRE to 8u31 from omnibus-software

Per customer security request,  update to Java 8.  It's been in omnibus-software since https://github.com/chef/omnibus-software/pull/363

For review by @chef/lob @chef/customer-success-engineers

If tests pass, I'm fine with this. Is there anything we use Java for that we should be testing manually that we wouldn't catch in other tests?

@tylercloke I'm going to run Solr4 through a stress test once this builds.

@irvingpop We should probably also test an EC 11 Solr -> Sorl4 migration

@tylercloke I just stress-tested this build (#967 on wilson) by spinning up 45,000 nodes in a 1 hour period.  Ran like a champ, expander queues all at 0.  I'm pretty sure it's performing better than ever :)

@ryan tested EC11.3.1 upgrade, worked without a problem
                     [private-chef-upgrade] - Starting Migration 1.18
                     [private-chef-upgrade] - 	Stopping Services ["nginx", "opscode-erchef"]
                     ok: down: nginx: 121s
                     down: nginx: 122s; run: log: (pid 17622) 7560s
                     down: nginx: 123s; run: log: (pid 17622) 7561s
                     ok: down: opscode-erchef: 123s
                     down: opscode-erchef: 124s; run: log: (pid 17176) 7576s
                     down: opscode-erchef: 125s; run: log: (pid 17176) 7577s
                     [private-chef-upgrade] - Sleeping for 10 seconds while services stop...
                     [private-chef-upgrade] - 	Starting Services ["rabbitmq", "opscode-solr4"]
                     down: rabbitmq: 134s; run: log: (pid 14837) 7675s
                     ok: run: rabbitmq: (pid 5260) 0s, normally down
                     run: rabbitmq: (pid 5260) 1s, normally down; run: log: (pid 14837) 7677s
                     down: opscode-solr4: 138s; run: log: (pid 4413) 147s
                     ok: run: opscode-solr4: (pid 5374) 1s, normally down
                     run: opscode-solr4: (pid 5374) 2s, normally down; run: log: (pid 4413) 150s
                     [private-chef-upgrade] - Sleeping for 15 seconds while services comes online...
                     [private-chef-upgrade] - 	Restarting Service opscode-chef-mover
                     ok: run: opscode-chef-mover: (pid 5471) 0s
                     [private-chef-upgrade] - Sleeping for 15 seconds while service opscode-chef-mover comes back online...
                     run: opscode-chef-mover: (pid 5471) 16s; run: log: (pid 17466) 7620s
                     [private-chef-upgrade] - Migrating indexed search data...
                     [private-chef-upgrade] - 	Running Command: /opt/opscode/embedded/bin/escript /opt/opscode/embedded/service/opscode-chef-mover/scripts/migrate mover_reindex_migration_callback normal with options {}
                       Successfully Migrated: wonderbolts, ponyville
                           Failed to Migrate: none
                               Not Attempted: none

                     Migrations completed successfully.

                     [private-chef-upgrade] - 	Stopping Services ["opscode-chef-mover", "opscode-solr4", "rabbitmq"]
                     ok: down: opscode-chef-mover: 0s, normally up
                     down: opscode-chef-mover: 1s, normally up; run: log: (pid 17466) 7657s
                     down: opscode-chef-mover: 2s, normally up; run: log: (pid 17466) 7658s
                     ok: down: opscode-solr4: 0s
                     down: opscode-solr4: 1s; run: log: (pid 4413) 224s
                     down: opscode-solr4: 2s; run: log: (pid 4413) 225s
                     ok: down: rabbitmq: 0s
                     down: rabbitmq: 1s; run: log: (pid 14837) 7758s
                     down: rabbitmq: 2s; run: log: (pid 14837) 7759s
                     [private-chef-upgrade] - Sleeping for 10 seconds while services stop...
                     [private-chef-upgrade] - Finished Migration 1.18 in 111.19 seconds

:+1: :ship:


Konflux update test-component-pac-wswdly

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-wswdly-on-pull-request has failed.
Namespace: build-e2e-ilvm-tenant
PipelineRun: test-component-pac-wswdly-on-pull-request-l5lhz

Task Statuses:

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
16 seconds
clone-repository

❌ Failed
21 seconds
build-container

✅ Succeeded
25 seconds
show-summary

Failure snippet:
task build-container has the status "TaskRunImagePullFailed":
the step "inject-sbom-and-push" in TaskRun "test-component-pac-wswdly-on-pull-request-l5lhz-build-container" failed to pull the image "". The pod errored with the message: "Back-off pulling image "quay.io/konflux-ci/buildah:latest@sha256:9ef792d74bcc1d330de6be58b61f2cdbfa1c23b74a291eb2136ffd452d373050"."

Pipelines as Code CI/test-component-pac-wswdly-on-pull-request has successfully validated your commit.

Namespace: build-e2e-ilvm-tenant
PipelineRun: test-component-pac-wswdly-on-pull-request-2wdtv

Task Statuses:

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
14 seconds
clone-repository

✅ Succeeded
44 seconds
build-container

✅ Succeeded
8 seconds
sast-snyk-check

✅ Succeeded
41 seconds
clamav-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
14 seconds
apply-tags

✅ Succeeded
8 seconds
deprecated-base-image-check

✅ Succeeded
19 seconds
clair-scan

✅ Succeeded
25 seconds
ecosystem-cert-preflight-checks

✅ Succeeded
15 seconds
show-summary

✅ Succeeded
8 seconds
show-sbom

Pipelines as Code CI/test-component-pac-wswdly-on-pull-request has failed.
Namespace: build-e2e-ilvm-tenant
PipelineRun: test-component-pac-wswdly-on-pull-request-jbprq

Task Statuses:

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
30 seconds
build-container

❌ Failed
23 seconds
clair-scan

✅ Succeeded
12 seconds
sast-snyk-check

✅ Succeeded
7 seconds
deprecated-base-image-check

✅ Succeeded
12 seconds
clamav-scan

✅ Succeeded
12 seconds
sbom-json-check

✅ Succeeded
14 seconds
apply-tags

✅ Succeeded
24 seconds
ecosystem-cert-preflight-checks

✅ Succeeded
9 seconds
show-sbom

✅ Succeeded
13 seconds
show-summary

Failure snippet:
task clair-scan has the status "Failed":
Inspecting raw image manifest quay.io/redhat-appstudio-qe/build-e2e-ilvm-tenant/build-suite-test-application-stff/test-component-pac-wswdly@sha256:bafb597d3d10a25cddddbabc0b1ba55fb69bcecf8f5055a1472bfc19247c0332.
time="2024-07-12T00:28:37Z" level=fatal msg="Error parsing image name \"docker://quay.io/redhat-appstudio-qe/build-e2e-ilvm-tenant/build-suite-test-application-stff/test-component-pac-wswdly@sha256:bafb597d3d10a25cddddbabc0b1ba55fb69bcecf8f5055a1472bfc19247c0332\": reading manifest sha256:bafb597d3d10a25cddddbabc0b1ba55fb69bcecf8f5055a1472bfc19247c0332 in quay.io/redhat-appstudio-qe/build-e2e-ilvm-tenant/build-suite-test-application-stff/test-component-pac-wswdly: manifest unknown"
The raw image inspect command failed


Metrics with a decimal part

When I try to build a metric with a decimal part, I get an error:
"Missing val for metric type gauge"

You are right. My fault. Will fix it today.

Problem solved in v1.0.1.
Thank you again for reporting the issue.


igCombo's Clear button does not clear ngModel value.

Description
igCombo's Clear button does not clear ngModel value.
Steps to reproduce

Unzip the attached sample, 'npm install', 'npm install igniteui-angular-wrappers' and npm start.
Open the dropdown list and select one of the items: 'blue', 'red' or 'yellow'.
Click 'x' button.

Result
ngModel value is not cleared.
Expected result
ngModel value should be cleared.
Note
This issue is reproducible with IgniteUI for Javascript v17.1, but not with v17.2.
Attachments
my-app3.zip

Sorry, but after I investigated it further, the reproducible sample is not accurate. The sample's package.json has both igniteui-angular2 and igniteui-angular-wrappers and the symptom looks like occurring because of this.
As long as just igniteui-angular-wrappers are used, this symptom does not occur with both v17.1 and v17.2.

@norikois Closing the issue.


Other pools get way more blocks. Configuration issue for shares?

Comparing my lyra2rev2 pool to other pools(yiimp based), they seem to get more blocks for the same ratio of hashrate. Is there some configuration I should be adjusting?
Pool is reporting the following:
Miners: 29
Hashrate: 3.99 GH/s
Valid Shares Per Second: 3
Current Block: 65176
Peers: 99
Network Difficulty 1.998543824405046 K
Network Hashrate 169.24 GH/s

block explorer for straks: https://straks.info
current difficulty around 3000-4000
my config:
      "4500": {
        "listenAddress": "<IP_ADDRESS>",
        "name": "SimpleDifficulty",
        "difficulty": 32.0,
        "varDiff": {
          "minDiff": 0.5,
          "targetTime": 15.0,
          "retargetTime": 60.0,
          "variancePercent": 90.0
        }
      },
      "7710": {
        "listenAddress": "<IP_ADDRESS>",
        "name": "SimpleDifficulty",
        "difficulty": 32.0,
        "varDiff": {
          "minDiff": 0.5,
          "targetTime": 15.0,
          "retargetTime": 60.0,
          "variancePercent": 30.0
        }
      },
      "4501": {
        "listenAddress": "<IP_ADDRESS>",
        "name": "HardDifficulty",
        "difficulty": 500.0,
        "varDiff": {
          "minDiff": 10.0,
          "targetTime": 15.0,
          "retargetTime": 60.0,
          "variancePercent": 50.0
        }
      }
    },

https://mpool.mooo.com/site/mining
https://datapaw.net/site/mining
https://www.cryptopool.xyz/site/mining

I wanted to get to the bottom of this. Therefore I decided to test this on a production pool with high enough and consistent hashrate. Therefore I chose Coinfoundry's Dash Pool. Throughout the past two weeks I switched back and forth between Miningcore's internal stratum and an external one which is a stripped down version of the node-stratum-pool that only processes shares and block submissions.
The net result was that I was unable to find any significant advantage of using node-stratum-pool over Miningcore's internal stratum. In fact judging from the average block effort, Miningcore had a slight advantage. One thing to remember is that you should utilize streaming block updates by all means. I've updated the Wiki to reflect this (see zmqBlockNotifySocket and wsPort).

@oliverw  Quick question, how do you configure MC to use the node-stratum-pool ?


Campus leader section on home page

Describe the bug
the image and text have no proper gap. Moreover, it also have additional + sign which is completely unnecessary.
Expected behaviour
Proper gap between image and text. removal of + sign.
Screenshots

Additional context
I'm a GSSOC'23 contributor. Please assign me this task.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@SahityaRoy  Please assign me this issue


[AVM Module Issue]: 0.5.1 incompatible with BYO vnet PodSubnetID container-service/managed-cluster

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
Bug
Module Name
avm/res/container-service/managed-cluster
(Optional) Module Version
0.5.1
Description
0.5.1 ❌ introduced a braking change when used with BYO vnet "PodSubnetID"
0.5.0 ✅ worked fine previously
primaryAgentPoolProfiles: [
  {
    vnetSubnetResourceId: aksSystemNodeSubnet.id
    podSubnetResourceId: aksSystemPodSubnet.id
    // other config omitted..
  }
]
agentPools: [
  {
    vnetSubnetResourceId: aksUserNodeSubnet.id
    podSubnetResourceId: aksUserPodSubnet.id
    // other config omitted..
  }
]

networkDataplane: 'cilium'
networkPlugin: 'azure'
networkPluginMode: null

which results with the following error:
Preflight validation check for resource(s) for container service myakscluster in resource group myresourcegroup failed.
Message: NetworkPluginMode overlay cannot be used with PodSubnetID.
Details: (Code: BadRequest)

(Optional) Correlation Id
No response

Hi @KLuuKer, Thanks for pointing out.
Unfortunately, we are currently experiencing a blocking issue in the AKS module that needs to be resolved before I can address it here. I ask for your patience.
thank you!


Submit COmplex PAthway SImulator 4.29.227

id: copasi
version: 4.29.227
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_COPASI/fe134a7b3c29ee43dccb51ba2a7d2383a1823348/biosimulators.json
specificationsPatch:
version: 4.29.227
image:
url: ghcr.io/biosimulators/biosimulators_copasi/copasi:4.29.227
validateImage: true
commitSimulator: true

Thank you @biosimulators-daemon for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job is available here.

The specifications of your simulator is valid!

Summary of tests

Executed 55 test cases

Passed 44 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 11 test cases:

published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots

Warnings
docker_image.HasBioContainersLabels (0.3 s)
Test that a Docker image has BioContainers labels with metadata about the image
Warnings:
The Docker image should have the following BioContainers labels:
  extra.identifiers.biotools

Log:

The image for your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of copasi to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


Don't wait the day after the reminder is set to remind

Checklist

[ ] Type annotations added to new functions
[ ] Docs added to functions touched in main classes
[x] Dry-run produced the expected results
[ ] The to-be-announced tag added if this is worth announcing

Closing in favor of #2049.


Elasticache: initial support for User

Description of changes:

Terminal codes
Additional Status fields for statekeeping: Elasticache's CreateUser and ModifyUser operations return an AccessString in a different representation than the AccessString requested by the user. We have to compensate for this in some way, as the generated code does not handle this case. The current solution is to add a Status.LastAppliedAccessString to determine when the desired AccessString has changed and Status.ResponseAccessString so that the user can see the server representation of the AccessString (without using the AWS CLI). Another possible solution would be to allow patching to apply to an object's Spec field, although if I'm not mistaken this was explicitly disabled in an earlier PR.
Custom set output and modify logic to populate these additional Status fields and use them to determine when to invoke a ModifyUser versus when to do nothing.

Behavior verified via manual testing; automated tests and other changes to follow in later PRs.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jaypipes sounds good, in the process of setting up my new workspace right now. We've also decided to park work on the User resource for now, so I'll close this PR as well


Feat/nf evaluation

Script to evaluate all NF models on benchmark datasets. The table needs to be updated with metrics as results are obtained.
Main changes:

Remove "alias" in models.py and simply use the model name instead
Specify the ds column as int or datetime in datasets.py
Add README and environment.yml file for reproducibility and to show results

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: cchallu:x: Marco PeixeiroMarco Peixeiro 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.


Bump oauth version to 6.11.58

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4902552649

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4902552649
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4904685516

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4904685516
Status: success


Update README.md

Added my name and Github link Abd'Kehinde Lawal
Related issue

What changes does this PR do?
Screenshots (If any)
Questions

I have done that. Kindly check if that is okay. Thanks

Thanks geek

I have closed the other PR

yess this is perfect! ready to merge🚀
can you close that other pull request?
__        Summary: 🏆 This code is awesome


”-s" option of command line does not work.

Hi guys, I got error like below.
$ ginza -s A
Traceback (most recent call last):
  File "/opt/anaconda3/envs/ginza5_p38/bin/ginza", line 8, in <module>
    sys.exit(main_ginza())
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/ginza/command_line.py", line 483, in main_ginza
    plac.call(run_ginza)
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/plac_core.py", line 427, in call
    cmd, result = parser.consume(arglist)
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/plac_core.py", line 278, in consume
    return cmd, self.func(*(args + varargs + extraopts), **kwargs)
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/ginza/command_line.py", line 467, in run_ginza
    run(
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/ginza/command_line.py", line 79, in run
    analyzer.set_nlp()
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/ginza/command_line.py", line 202, in set_nlp
    set_split_mode(nlp, self.split_mode)
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/ginza/__init__.py", line 112, in set_split_mode
    splitter = nlp.get_pipe("CompoundSplitter")
  File "/opt/anaconda3/envs/ginza5_p38/lib/python3.8/site-packages/spacy/language.py", line 601, in get_pipe
    raise KeyError(Errors.E001.format(name=name, opts=self.component_names))
KeyError: "[E001] No component 'CompoundSplitter' found in pipeline. Available names: ['transformer', 'parser', 'attribute_ruler', 'ner', 'morphologizer', 'compound_splitter', 'bunsetu_recognizer']"

The old component name "CompoundSplitter" may be used somewhere.
Thank you.
$ pip list | grep -i ginza
ginza              5.0.1
ginza-transformers 0.3.1
ja-ginza           5.0.0
ja-ginza-electra   5.0.0

@r-oguro Thanks for reporting bugs. I fixed set_split_mode() and am going to release a bug-fix version.


Update developer documentation

Check the pandas documentation, they have some good reccomendatons, see https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#writing-tests

Add type hinting requirement.


kotlin: 1.0.1 -> 1.0.1-2

Things done:

[X] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[ ] NixOS
[ ] OS X
[X] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Travis error is unrelated.


libhyprlang.so.1 not found

on the -git version from aur
hypridle: error while loading shared libraries: libhyprlang.so.1: cannot open shared object file: No such file or directory

tried updating both hyprlang-git and hypridle-git same result.

Recompile will fix this.
if using yay run yay -Scc and say y to every option then update hyprlang and hypridle


Blob.download_to_filename eating lots of RAM

I have a large ~4 GB binary file on GCS. When I use blob.download_to_filename, my RAM usage goes increases by 3 GB temporarily. Thus behavior goes away if I explicitly set a chunk size for the blob.
This seems like bad default behavior.

@lukesneeringer @jonparrott WDYT about modifying the default? Also, IIUC if we use requests / urllib3 by default we can still stream the entire payload (i.e. no chunking) into a file without having to put the whole thing in RAM first.

Seems reasonable to me. A default of a few megabytes hopefully won't hurt performance for small files. Can you do some benchmarks?

Fixed in #3713

Resurrecting this -- would you expect that the streaming solution in #3713 wouldn't work if the file were a tmpfs volume?  That's what I'm seeing


Enhancement: Additional features required

Thanks for working on getting this helm chart published. It makes it easier to manage this instead of a huge glob of manifests. We do have some issues that needs to be sorted out.

Some of the additional charts included in this chart need a way to be disabled.

Clickhouse, Minio, Postgres and Redis are already scaled services I run. Postgres and Redis are widely available as managed services by hosting companies so it would make sense to that over a small one in this chart. This would need to basically have an option where you can set enabled as a boolean and configure some other things on where to connect, how to connect, connect with special options (redis with sentinel?).

I'm not entirely sure why we need metallb in a helmchart?

There is no way to pass secret data. Environment variables like the ones in example.env, are unsettable here.

It's true that they are added here. But it simply generates a random string, unless these need to be changing every time you deploy this chart.
A good alternative would be to allow users to create a Secret/ConfigMap called oneuptime-config for the helmchart to read from instead of hardcoding stuff in helpers.tpl

It might be a good idea to explore alternatives to running a nginx container in kubernetes when you can take advantage of other options like traefik, ingress-nginx, or the built-in endpoints that I haven't taken a look into.

All in all, good job on the chart! Glad it is being pushed, a lot of the OSS homelabbers will be happy to stop updating 25 oneuptime containers every day. :)

This is a read-only repo according to the readme. Issues should be opened on the main (oneuptime/oneuptime) repo.

Closing this issue here.


Color field type not delete able

same as https://github.com/sulu-io/sulu/issues/1304

fixed in the same PR as #1304


Lock language setting while in offline

Changing the language while in offline mode already has no effect, but it is still selectable and registers as a change, therefore user see the newly selected language as set and can press "save" at the end of it. Only upon returning to the settings page will they notice that their change had no effect and is the language is set back to the initial value.
It seems rather unintuitive to leave a setting as changeable and then not enforce the change of a setting, instead of just locking the setting outright. I propose the locking of the language settings while in offline mode outright to decrease confusion.

It shouldn't be a problem to change the language because translation is already in cache? So it should work without any problems?.
In general: Yes, if a value change doesn't really change something -> disable or hide the option. Disabling is better for UX.

If we already have the language files then we could also allow the user to change the language to all the languages where translation files have been downloaded and are currently present in the app while offline.
Either way is fine. Locking or just allowing pre-downloaded selection.

If we "go offline", the app was started and everything is in cache... because the online mode also need the files. If we are offline, we have everything in place. Sure, if you create offline screens the translation should be recognized/used.
I guess the translation change in offline mode is a bug.

The settings dropdown shows all currently supported languages, which are defined by looking at the local translation files (Keyword: AppOverview) and the already downloaded translation files from the server.
Changing the language to a selectable entry should therefore theoretically work fine while being offline.
But currently, it doesn't work for two reasons.
In greater explanation, we have a user language and an application language, the user language is defined by the user and only by the user and the application language (which has a higher priority) is defined by the server, which in turn can return the same as the preferred user language, effectively respecting the user's choice.
Now the user goes offline and wants to change the language, which would usually update the application language after the restart, but there is no restart.
First problem is that the save button, just doesn't do anything when offline, just routing back (Easy fix).
The second problem is the still saved application language, which is now old and doesn't reflect the user preference anymore, but still overwrites the user preference.

We would either need to clear the application language manually when going offline, which could result in confusing UX.

For example, the server forces EN, but the user has DE as preference selected. After changing to offline, the app which was up to now forced to English is now in German. And vice versa when going online.

Or the server would stop sending a application language as long as it isn't forced, and we would locally handle the user language. The server would still have our selected language as we send it in the startup.

Additionally, we should probably show forced server settings somewhere in the UI, as currently the user has no chance to effectively understand why his (in this case language) switch doesn't work (even without the bug mentioned above).

Offline language detection would be consistant, when MobileLauncher sets an additional application parameter, in case the language is configured fix in application.xml. (eg: Application.language.isfixed = true or alternative a Application.language.configured = value of Application.language). This can be easily set in updateConfiguration, if (!StringUtil.isEmpty(getParameter(ILauncher.PARAM_APPLICATIONLANGUAGE))).
Then in Offline Mode the language detection is:
Application.language.isfixed == true: app-language
Application.language.isfixed == false: user-language or system-language, if user.language is not set.
app-language means, the language that the server sent in Language response.
user-language means, the language that the user has choosen in settings.
system-language means, the language of the device.

I'm not sure if we talk about the same things.
App translation is the translation which is included in native app. Used for translation of text which is shown before the startup of an application (app overview).
User translation is the translation received from the server-side application.
Use the app translation for every text and message will be shown before the startup of an application. And use the user-language if an application is started. So simply: user-translation -> fall-back to app translation to support translation of texts which are not defined in user translation.
Which language: System language (default) -> if user sets a different language via application settings -> store this language and just use it. So you know if user has set the language on mobile device.
If no custom language is set -> Use system language... BUT the server sends you the language - and here's a problem?
It's possible that the System language is German and the app overview is German and an application is in English because it's configured in English.
I guess your problem is that the language sent from server is the default language of server. If server runs English, the default language is English but should be German?
So the application should send: Client - use-your-default-language?
BUT this issue was about offline mode. In offline mode it should be possible to change the language without any problems!

response will contain the property: customLanguage
If available and set -> hide or disable language in settings
if this property is set, it means that the language is fixed.

Note: This is a breaking change for old servers, as we now only respect the server language if customLanguage is set.
Should we increment the server version?

Why?
The only difference should be tat the client locks the language!
The rest should work like before!


The value of the field is too long

Getting an error that the value of the field is too long. What is the max length? Is this a bug or can I do something to fix it?
Field Definition:
<FIELD name="Products" refname="Sonlinc.Products" type="String" reportable="dimension">
  <SUGGESTEDVALUES expanditems="true">
    <GLOBALLIST name="Sonlinc.Products" />
  </SUGGESTEDVALUES>
</FIELD>

WebLayout:
<ControlContribution Label="Products" Id="ms-devlabs.vsts-extensions-multivalue-control.multivalue-form-control">
  <Inputs>
    <Input Id="FieldName" Value="Sonlinc.Products" />
  </Inputs>
</ControlContribution>

Error description:

For single line text field and one of the value of the picklist field, the max length is 255.


Repaired the axel app manifest

Repaired the axel app manifest to use maintainer release (https://github.com/ghuntley/cygwin-axel) instead of dropbox

Thanks


getStorageDatasetsInProjects returns empty list

I tested with both synapse IDs of a file view and a project. The function did not return the expected list of folders in the file view.
Note: my file view scope is a folder that has sub folders.

Could you show us the code/snippet, which you used to call the method?
Did you check that there were no problems when trying to establish connection to Synapse (using the synapseclient)?

I was testing using storage_test_drive.py. Before executing, I commented out everything after line 39 and used my own file view synapse ID.
And I saw the welcome message for logging into Synapse, so I would assume my connection was established.
My file view's scope is a folder instead of the entire project. Not sure if this would make a difference.

Hi @xindiguo!
Could you the following steps:

Change the value of "masterFileview" key in config.py on line #9 to "syn21823263".

Pass the synID of the project i.e., "syn21542798" to the getStorageDatasetsInProject() function.

Log the output of the local variable foldersTable that is implemented in the SynapseStorage.py by adding the following lines in Line #170

print("====================================================")
print(foldersTable)
print("====================================================")

Please do check the id and name columns in the foldersTable dataframe. If so, then we can explain why it wasn't working for you.


Add Watcher!

You can add also The watcher button as example

Watchers, contributors, and followers are on my list! I'll post back here when this is live.


Ambiguous key verification error

With the recent change to githubs RSA fingerprints we had to update the SSH known hosts secret, but unfortunately github was not the only thing in there ( is there ever a situation were this deployer would run and not need to know the github SSH? ).
Unfortunately now deployment fails with host key verification failed, but which key? Who is the host? My key? The private key in secrets? The server we're deploying to? How do I find out?
Here's the output, I've swapped out the IP for <IP_ADDRESS>:
$ php vendor/bin/dep deploy test -v --no-interaction --ansi -vvv
✈ Deploying deploy-test on <IP_ADDRESS>
• done on [<IP_ADDRESS>]
➤ Executing task deploy:prepare
[<IP_ADDRESS>] > echo $0
[<IP_ADDRESS>] < ssh multiplexing initialization
[<IP_ADDRESS>] < Host key verification failed.
➤ Executing task deploy:failed
• done on [<IP_ADDRESS>]
✔ Ok [0ms]
➤ Executing task deploy:unlock
[<IP_ADDRESS>] > rm -f ~/deploy/.dep/deploy.lock
[<IP_ADDRESS>] < ssh multiplexing initialization
[<IP_ADDRESS>] < Host key verification failed.

Also noting that this is an inherited setup, the person who originally set this up is long gone and unavailable

See https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/

we did, please re-read the issue! Thats what triggered the problem, we grabbed the new known hosts entries for github and put them in the secret referenced from the action.
Since I raised the issue I figured out that the host key verification it was complaining about referred to the server we are deploying to, and that was not clear from the output, hence the issue


GHA: Wrong parameter passing to fastlane

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5158  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @malmstein and the rest of your teammates on  Graphite


Is Kong  is Supported  on RISV machine

Hi All,
We have application using Egex in which we are using kong as API gateway .Is there any support available for kong on riscv ?
Thanks

Hi @divyashree123456 , Kong is not supported on that environment.


Start script fails after initial installation - After merge #488

Node version:
6.11.2
npm version:
3.10.10
Operating system:
Ubuntu 16.04
Command line used:
zsh
Steps to reproduce:

git clone git clone https://github.com/coryhouse/react-slingshot.git
npm setup
npm start -s

Jest can't find tests.
Starting app in dev mode...
No tests found
In /home/dennis/Documents/MB/react-slingshot
  50 files checked.
  testMatch: **/__tests__/**/*.js?(x),**/?(*.)(spec|test).js?(x) - 12 matches
  testPathIgnorePatterns: /node_modules/ - 50 matches
Pattern: "--watch" - 0 matches

Can confirm issue. Managed to solve problem with removing -k flag, as npm run test:watch exits and everything is killed

Thanks for reporting. Fixed!

Get latest. I just realized #497 was the root cause, so I moved us back to using concurrently.


Convert JS scripts to ES6 and compile with Babel

Useful links:

https://babeljs.io/docs/setup/
https://www.npmjs.com/package/babelify
http://advantcomp.com/blog/ES6Modules/


feat: minimal transfer implementation

Motivation
Minimal implementation of the interface defined in commit d6a9fd5c6a8d99ac36cca361fe65af1dad594f69. One major feature it is missing is sending alerts to users upon failures.
Implementation
ParseKafkaEndpointsFlags will be shared with a follow up commit that adds the verification implementation.
One of the implementation details that is important to note is how the Submission Information Package (SIP) is created.
The SIP contains the following fields:

Date
ContentCategory
ContentType
Identifier
Urn
Path

For the web archive project and for uploading harvested pages specifically:
Date: current time of upload
ContentCategory: nettarkiv
ContentType: warc
Identifier: no-nb_<ContentCategory>_<Path.name>
Urn: URN:NBN:<Identifier>
Path: Path to directory to be uploaded

For example, the following SIP is valid:
Date: 2023-09-03T15:04:05.000
ContentCategory: nettarkiv
ContentType: warc
Identifier: no-nb_nettarkiv_kommuner_2023-20230611002729-0035-veidemann-contentwriter-568c6f8545-frvcm
Urn: URN:NBN:no-nb_nettarkiv_kommuner_2023-20230611002729-0035-veidemann-contentwriter-568c6f8545-frvcm
Path: /stage-artifacts-root/kommuner_2023-20230611002729-0035-veidemann-contentwriter-568c6f8545-frvcm

Future work
The current implementation is a very minimal one. It does not alert users upon failures through correct channels, so the current solution is dependent on the user checking the logs manually to discover failures.

Ready for next round @maeb
I updated the commit message and added a fixup commit for both keyword argument usage when creating structs and for moving the kafka message writer outside of the send message function.

Thank you for the reviews @maeb and @andrbo :)


How Completion Queue Shutdown works ?

Hello,
I have a done a fully async server and I was wondering how the completion queue shutdown process work ?
After calling cq_->Shutdown do I need to delete the CallData instance that have been created but not deleted yet ? If no why and how does it works ?
Thank you

Summoning @sreecha to the party.

Hi @rllola,
By CallData, I am assuming you are referring to the class used in greeter_async_server.cc .
I wanted to clarify that it is not a standard class exposed by the grpc framework - it is rather an application defined class - and as such any dependency between cq and CallData are application specific.
Here is completion queue shutdown works:

Once you call cq->shutdown on a completion queue, you can no longer queue any more events on that queue. You will get an assertion failure if you do so.
You must keep calling cq->Next() or cq->AsyncNext() on that queue to drain all the pending events. Once all the events are drained, cq->Next() will start returning  false (or cq->AsyncNext() will return NextStatus::SHUTDOWN).
This is when it is safe to delete/destroy your completion queue object

Ok, thank you this more clear now.
An other question that I have is how the events are deleted in the completion queue. In the example, we just delete it but how is it remove from cq ?

I am also wondering about this.
In the ' greeter_async_server.cc' example, assume you have a tag which has been registered, but either

there has never been a request made
a request has been made but ServerAsyncResponseWriter::Finish has not yet been called

In this case, there is a dangling CallData object. How does it get properly deleted when when ~ServerImpl() is called?

how the events are deleted in the completion queue. In the example, we just delete it but how is it remove from cq ?

@rllola, you do not explicitly delete the "events" in the completion queue. You just drain/dequeue all the events by calling cq->Next() or cq->AsyncNext() as I mentioned earlier.  This is how you get back the tag objects you have passed into the completion queue earlier (for example the CallData objects in the greeter_async_server.cc example) and this is when you can free/delete the tag objects - since you are sure that the completion queue no longer has a reference to them.
As a side note:  Notice that both cq->Next() or cq->AsyncNext()  have an argument called ok in them (I am pasting their signatures below for reference). So when you are draining events by calling cq->Next() or cq->AsyncNext() it is possible that ok may be false but you will still get the tag object back:

NextStatus AsyncNext(void** tag, bool* ok, const T& deadline)
bool Next(void** tag, bool* ok)

So tying this all together:
Lets say you need to release memory of all the tag objects (for example the CallData object that @bedeho was mentioning) because you are tearing down the server.
In this case you would have called server_->shutdown() and cq->shutdown() on all the completion queues.  Once you do this, you will have to drain all the events in the completion queues by calling cq->next() or  cq->AsyncNext() and you will get back all the events in the completion queue with either ok==true (for any of those events successfully completed) and ok==false for those that could not be completed but still returned because your server is shutting down.
Once you get the tag back, it is safe to release the memory for that (since you are the one owning it)
Hope this helps.

Thanks you for that response, but I would really appreciate a more direct response to my question also if possible.
In particular, after some more testing it seems like the server will put the tags of all registered unfinished rpc calls into the completion queue when a server shutdown is initiated, and that this is why no CallData objects leak during shutdown. Can you confirm this?

@bedeho,

it seems like the server will put the tags of all registered unfinished rpc calls into the completion queue when a server shutdown is initiated

Yes. This is correct.

and that this is why no CallData objects leak during shutdown
You still need to call cq->Next or cq->AsyncNext to get those tags (i.e the CallData objects) out. This is what I meant by 'draining'the completion queue. After this, you are free to destroy the CallData objects. I am assuming this is what you implied

Thanks!

@sreecha  have a quick question.
Is there any race condition between Shutdown and Next or AsyncNext?

@yyh-graphsql - There is no race between the two - you can call them in parallel.
However, make sure that you drain the queue after calling shutdown (i.e continue calling Next or AsyncNext until they actually return that the queue has been shutdown)


After a match has been witnessed, have the Ranker bot report the updated placements of each player

I find it hard to justify reporting the new placements in the slackbot, since that would modify the success returns from the api.  Thus making it not uniform output.  In the upcoming revision matches will keep track of GSP changes as well as ranking changes from individual matches.  So they can view their rank change on the website


Fix issues in pymeasure.adapters

Make sure imports are always at the top of the file, before any other code (also clears IDE from yellow warnings).
Fix pep8 compatibility (spaces, blank lines, indentations).
Replace blank except: statements with except Exception: or with more specific exceptions.
Replace super(...) with direct reference to the super-class. This is in par with the way CPython is written.
Change the way PrologixAdapter and 'SerialAdapter' handle serial.Serial object as its adapter.
Inherit __del__ from SerialAdapter to PrologixAdapter instead of rewriting it.

Replace super(...) with direct reference to the super-class. This is in par with the way CPython is written.

TBH, I have never seen the recommendation to got back from super() to naming the specific superclass. I wonder where you got that from?

@bilderbuchi, I read some of the source of the python standard library lately (mainly the logging module). I found that the direct superclass approach is used in the vast majority of the cases. The super(...) syntax was used only once. That gave me the impression that it's the standard way of doing it. However, I might got the wrong impression. If you think the super(...) syntax is better, I may revert back to it.

That's because (if you check the git blame) those portions were written 10-15 years ago, when today's incarnation of super() did not (I think) exist yet. "New-style" super, i.e. just using super().somecall() is the way to go, see e.g. https://rhettinger.wordpress.com/2011/05/26/super-considered-super/ or some other resources on google or in a current Python book.

@feinsteinben, same comments go  this PR along with #86. Please revert the super calls and I will squash and merge.
Thanks @bilderbuchi for weighing in on the super distinction! I agree with your thoughts.

Thanks for the review. Squashed this change into PR  #85.
Think it can be closed.


Can't install  with Carthage

Can't install  with Carthage

@3viewgroup could you please provide more information?


enable search queries

Giordon pointed me to the atlas.json file. It seems a good idea to me to keep track of published likelihoods this way. However, to make this really useful, it will be good if the metadata don't only provide a list of what's there but enable search queries. A first step in this direction could be "group" entry (SUSY, Higgs, top, ...) in the json file. Just a suggestion ....

@sabinekraml this is a good idea. At the moment though we're simply just web scraping the ATLAS publications website https://twiki.cern.ch/twiki/bin/view/AtlasPublic for entries that have the "Likelihood available" tag
https://github.com/pyhf/public-probability-models/blob/7a948f25ae8094fe220879a342c0c11c0837de47/atlas/main.py#L36-L37
though given that there is the option to sort by physics group perhaps it is possible to also pull this tag out as well.
While I can poke around at this, @kratsg might know immediately.

Ah, if your scraping the twiki entries, you should in fact be able to use
several more tags, like 'Physics theme', 'Signature' and 'Analysis
characteristics'
On Mon, Sep 19, 2022 at 6:47 PM Matthew Feickert @.***>
wrote:

@sabinekraml https://github.com/sabinekraml this is a good idea. At the
moment though we're simply just web scraping the ATLAS publications website
https://twiki.cern.ch/twiki/bin/view/AtlasPublic for entries that have
the "Likelihood available" tag
https://github.com/pyhf/public-probability-models/blob/7a948f25ae8094fe220879a342c0c11c0837de47/atlas/main.py#L36-L37
though given that there is the option to sort by physics group perhaps it
is possible to also pull this tag out as well.
While I can poke around at this, @kratsg https://github.com/kratsg
might know immediately.
—
Reply to this email directly, view it on GitHub
https://github.com/pyhf/public-probability-models/issues/10#issuecomment-1251276083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3ROOFE43LWGPN7CIO5YI3V7CKJJANCNFSM6AAAAAAQP5L2KA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--

Sabine Kraml  - @.*** -  www.kraml.net
LPSC
53 Av des Martyrs
38026 Grenoble
France
(+33)(0)4 76 28 40 52

Ah, if your scraping the twiki entries, you should in fact be able to use several more tags, like 'Physics theme', 'Signature' and 'Analysis characteristics'

This will take additional revisions beyond just adding entries from the table, as that is part of the selection process for the entries that populate the table. So I'll make this a separate Issue.


Implement Vertical Build for Android arm32 Mono

This issue covers productization of the following vertical: Android arm32 Mono

Build OS: Mariner
Target OS: Android
Build OS Arch: x64
Target Arch: arm32
Stack Type: Short
Key Artifacts: Android arm32 Mono Runtime Packs

Implementation of this vertical may depend on completion of other items within the Unified Build Space:

[ ] Link issues as necessary

When complete, the following will be true:

[ ] The vertical builds successfully and required changes are backported to individual repos.
[ ] The vertical's outputs are verified as being complete and correct as compared to the current .NET official build.
[ ] The vertical is enabled in VMR rolling CI and PR (if applicable).

T-Shirt Size: Small (default, update as necessary)

This was done.


BUG: close_all() function in event handler does not work when opening in new tab

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
NVIM v0.10.0-dev
Operating System / Version
MacOs 14.4.1 (23E224)
Describe the Bug
The following even handler provided in the documentation does not work when opening a file in a new tab.
		event_handlers = {
			-- Close neo-tree when opening a file.
			{
				event = 'file_opened',
				handler = function()
					require('neo-tree').close_all()
				end,
			},
		},

The neo-tree window remains open in the previous tab the file was opened from. Should this be expected to close the neo-tree window even though it's in the previous tab? Is there a way to accomplish this functionality currently?
Screenshots, Traceback
No response
Steps to Reproduce

open Neovim
Open neo-tree
open file in current tab
open another file in neo-tree but in a new tab.
go back to the previous tab. neo-tree is still open.

Expected Behavior
It should close the neo-tree window even when opening a file in a new tab.
Your Configuration
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}

local neotree_config = {
  "nvim-neo-tree/neo-tree.nvim",
  dependencies = { "MunifTanjim/nui.nvim", "nvim-tree/nvim-web-devicons", "nvim-lua/plenary.nvim" },
  cmd = { "Neotree" },
  keys = {
    { "<Leader>e", "<Cmd>Neotree<CR>" }, -- change or remove this line if relevant.
  },
  opts = {
    -- Your config here
    -- ...
  },
}

table.insert(plugins, neotree_config)
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

If you want Neo-tree to close after you open a file, then you really shouldn't be using a sidebar position. The float position would probably be the most appropriate for how you are using it.


batch: Implement source executor in batch query.

Implement batch source executor which reads data from source split.

will we reuse the streaming source executor for batch?

I don't think so, using streaming executor in batch looks weird. We will implement a batch source executor.

Then is there any adjustment to the connecters' abstraction?

Then is there any adjustment to the connecters' abstraction?

Currently no.

closed by #6627


Issue with SECRET

I think you should add the following to this page:
SECRET is an undocumented VSTS reserved prefix, please only use this string if something precedes it

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

ID: 97f3af3f-ef07-8896-4b3c-05cef163b51a
Version Independent ID: b4b1f6a4-5975-358b-1cf4-f7b10a2245cd
Content: Environment Variables - Visual Studio App Center
Content Source: docs/build/custom/variables/index.md
Service: mobile-center
GitHub Login: @derpixeldan
Microsoft Alias: daadam

@adteulade thanks, I'll have the team take a look at making the change.


Multiselect elements: cosmetic

This has potential:

TODO:

[ ] Style with color, line etc. consistent with our palette
[X] Replace tag-style placeholders with a raw count (as for example on IPTT filters): (Moved to #1335)

Moved the functional issue to #1335. This ticket is just for cosmetic issues


Positive Prefixes

Problem Link - https://www.codechef.com/DEC20B/problems/POSPREFS

Please verify the problem and assign this to me. I will do it in c++.

@Nivedita967 I would like to contribute in python

Open for C and Java.

Please assign this task to me I have not yet added the code of this problem.


Wrong revision of Tantivy?

Describe the bug
The current Cargo.toml is using a revision of Tantivy corresponding to a dangling commit https://github.com/quickwit-oss/tantivy/commit/116c6d3
https://github.com/quickwit-oss/quickwit/blob/eccd16bdb3be0badd8c990ec3ff45cbd7835057a/quickwit/Cargo.toml#L223
Steps to reproduce (if applicable)
N/A
Expected behavior
I would expect it to point to a non-dangling commit on some branch.
Configuration:
N/A

I've restored the corresponding branch, but quickwit shouldn't depends on commit from non-main

PR#2976
This is still not attached to the main branch... because I had to add hotfixes, but it is tagged, which is sufficient to avoid the rev to be GCed by github.

Fixed in https://github.com/quickwit-oss/quickwit/pull/2976


trilium: 0.49.4 -> 0.49.5

Motivation for this change
https://github.com/zadam/trilium/releases/tag/v0.49.5
Things done

Built on platform(s)

[x] x86_64-linux

[x] Tested basic functionality of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@ofborg build trilium-server
@ofborg build trilium-desktop
@ofborg test trilium-server


Which version or branch to use?

I've just started a project that needs a connection to an MSSQL server and found this nice package providing the needed building blocks.
The question I have is about what version or branch to use? I noticed that you mentioned that v0.3 will not be updated anymore, so I was wondering if the async_await branch is already stable enough for us to use (or course understanding that the API can still change, but that's fine)?
Thanks!

No it is not, it's a first sketch.
I wouldn't recommend 0.3 or any version for anything production related at this time.

So would an older v0.2 be OK to use? Or do you have any other (versions or packages) suggestions?
The use of MSSQL is limited to running 1 (identical) query every 5 minutes. So our usecase is reasonably straight forward.
Thanks!

Generally 0.3 should be the most stable version, but is a bit outdated in terms of futures version...
I'am not aware of any other library besides ODBC and there are also there are afaik no FreeTDS bindings for rust.

I was just looking at ODBC as well, but think I’ll first take v0.3 for a spin. Thanks again for the feedback!


Unexpected behaviour of custom annotations when adopting resources into the helm 3 release

After converge helm release contains rendered custom annotations:
# Source: k8s-infra/templates/DexProvider.yaml
apiVersion: deckhouse.io/v1alpha1
kind: DexProvider
metadata:
  annotations:
    ci.werf.io/commit: COMMIT
    github.ci.werf.io/workflow-run-url: URL
    project.werf.io/env: prod
    project.werf.io/git: URL
    project.werf.io/name: k8s-infra
    werf.io/version: v1.2.9+fix10
  name: github

But resource does not contain any.
After several retries some annotations appeared, but not all needed annotations:
apiVersion: deckhouse.io/v1alpha1
kind: DexProvider
metadata:
  annotations:
    ci.werf.io/commit: COMMIT
    github.ci.werf.io/workflow-run-url: URL
    meta.helm.sh/release-name: k8s-infra
    meta.helm.sh/release-namespace: default

In werf v2 service annotations are not saved in Helm release. At the same time, there were no issues with service annotations applying to resources during deploy. Closing.


BLOCKER: xSSLSettings mof Needs ASCII Encoding

Test failure can be seen here.
The xSSLSettings mof needs to be encoded using ASCII.
This module cannot be released until this issue is fixed.

Fixed in #177


ThemeRiver type cannot be vertical

Version
5.2.0
Steps to reproduce
Take this an run in browser: (https://echarts.apache.org/examples/en/editor.html?c=themeRiver-basic)
option = {

    tooltip: {
        trigger: 'axis',
        axisPointer: {
            type: 'line',
            lineStyle: {
                color: 'rgba(0,0,0,0.2)',
                width: 1,
                type: 'solid'
            }
        }
    },

    legend: {
        data: ['DQ']
    },

    singleAxis: {
        top: 50,
        bottom: 50,
        axisTick: {},
        axisLabel: {},
        type: 'time',
        // orient: 'vertical',
        axisPointer: {
            animation: true,
            label: {
                show: true
            }
        },
        splitLine: {
            show: true,
            lineStyle: {
                type: 'dashed',
                opacity: 0.2
            }
        }
    },

    series: [
        {
            type: 'themeRiver',
            emphasis: {
                itemStyle: {
                    shadowBlur: 20,
                    shadowColor: 'rgba(0, 0, 0, 0.8)'
                }
            },
            data: [['2015/11/08',10,'DQ'],['2015/11/09',15,'DQ'],['2015/11/10',35,'DQ'],
            ['2015/11/11',38,'DQ'],['2015/11/12',22,'DQ'],['2015/11/13',16,'DQ'],
            ['2015/11/14',7,'DQ'],['2015/11/15',2,'DQ'],['2015/11/16',17,'DQ'],
            ['2015/11/17',33,'DQ'],['2015/11/18',40,'DQ'],['2015/11/19',32,'DQ'],
            ['2015/11/20',26,'DQ'],['2015/11/21',35,'DQ'],['2015/11/22',40,'DQ'],
            ['2015/11/23',32,'DQ'],['2015/11/24',26,'DQ'],['2015/11/25',22,'DQ'],
            ['2015/11/26',16,'DQ'],['2015/11/27',22,'DQ'],['2015/11/28',10,'DQ']]
        }
    ]
};

Uncomment the line orient: 'vertical',
What is expected?
To show the graph vertically with information
What is actually happening?
The information collapses into the axis, invisible.

Am I perhaps missing some way of showing a themeriver chart vertically rather than horizontally?

Is this a feature request?


add week to the dutch/nl locale

Pull Request Checklist

[x] 🧪 Added tests for changed code.
[x] 🛠 All tests pass when run locally (run tox or make test to find out!).
[x] 📚 Updated documentation for changed code.
[x] ⏩ Code is up-to-date with the master branch.

Description of Changes
Add weeks to the dutch locale

Codecov Report

Merging #741 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #741   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           9      9
  Lines        1678   1678
  Branches      283    283
=====================================
  Hits         1678   1678

Impacted Files
Coverage Δ

arrow/locales.py
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Shiny deploy fails with new configuration expectations

Describe the bug
It looks like shiny deploy is expecting different config parameters and now fails. We reference the model via  model.input.location, not model.input.repo.
config <- yaml::yaml.load_file("schematic_config.yml");
system(sprintf("echo MODEL_REPO=%s >> $GITHUB_ENV", config$model$input$repo));
Error in system(sprintf("echo MODEL_REPO=%s >> $GITHUB_ENV", config$model$input$repo)) :
  non-empty character argument expected
Execution halted
Error: Process completed with exit code 1.

@allaway Is it safe to try to update this line to repo to use the new shiny deploy workflow?

I'm on my phone at the moment but it looks like this is just the develop branch, right? If so, I am waiting for an upstream change that is backwards compatible with the older config files. I'll take a closer look when I get home!

Yes, this is just for develop. Was just looking at this file change: https://github.com/nf-osi/NF_data_curator/commit/605c82469d2bdc440fa3d53f35bc438d83639ee8#diff-5c0719296c8d398fa56ddc451d923ab39844d3ca179e8eb4c5d7debf8101d5b7

I think this is another one of those instances where backwards-compatibility should have been prioritized...

Yeah, I think the DCA and schematic releases are slightly out of sync. The next DCA release to main should include changes that will make this backwards compatible.

Actually, I just checked and it seems like the PR (https://github.com/Sage-Bionetworks/data_curator/pull/411) has made it into main (https://github.com/Sage-Bionetworks/data_curator/pull/410)

OK, looks like deployment works again. :tada:


enable assert optimization in reshape

This is the nice way of removing the all_int calls for -O.

This is trading readability for speed