CrashplanEngine fails to start on UnRAID

Immediately following a recent update to UnRAID 6.5.3, the CrashPlan Pro docker is no longer functional, specifically the crashplan backup engine seems to be unable to start. There is a continuous loop in the container log of "[CrashPlanEngine] starting..."
Any thoughts or assistance to resolve would be greatly appreciated.
Troubleshooting steps attempted:
-Increased container max memory
-Deleted crashplanpro container and reinstalled clean (deleted the directory from appdata)
-Deleted and recreated my entire docker image (to rule out any chance of a docker issue)
The complete container log:
ErrorWarningSystemArrayLogin
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] crashplan-pro.sh: executing...
[cont-init.d] crashplan-pro.sh: exited 0.
[cont-init.d] validate_max_mem.sh: executing...
[cont-init.d] validate_max_mem.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] starting s6-fdholderd...
[services.d] starting certsmonitor...
[services.d] starting nginx...
[services.d] starting xvfb...
[nginx] starting...
[certsmonitor] disabling service: secure connection not enabled.
[xvfb] starting...
[services.d] starting CrashPlanEngine...
[CrashPlanEngine] starting...
s6-svwait: fatal: timed out
[services.d] starting logmonitor...
[services.d] starting statusmonitor...
[logmonitor] starting...
[services.d] starting openbox...
[statusmonitor] starting...
[openbox] starting...
[services.d] starting x11vnc...
[services.d] starting app...
[x11vnc] starting...
[app] starting CrashPlan for Small Business...
[services.d] done.
11/08/2018 02:41:02 passing arg to libvncserver: -rfbport
11/08/2018 02:41:02 passing arg to libvncserver: 5900
11/08/2018 02:41:02 passing arg to libvncserver: -rfbportv6
11/08/2018 02:41:02 passing arg to libvncserver: -1
11/08/2018 02:41:02 passing arg to libvncserver: -httpportv6
11/08/2018 02:41:02 passing arg to libvncserver: -1
11/08/2018 02:41:02 passing arg to libvncserver: -desktop
11/08/2018 02:41:02 passing arg to libvncserver: CrashPlan for Small Business
11/08/2018 02:41:02 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 1945
11/08/2018 02:41:02 Using X display :0
11/08/2018 02:41:02 rootwin: 0x43 reswin: 0x400001 dpy: 0x4a65ba00
11/08/2018 02:41:02
11/08/2018 02:41:02 ------------------ USEFUL INFORMATION ------------------
11/08/2018 02:41:02 X DAMAGE available on display, using it for polling hints.
11/08/2018 02:41:02 To disable this behavior use: '-noxdamage'
11/08/2018 02:41:02
11/08/2018 02:41:02 Most compositing window managers like 'compiz' or 'beryl'
11/08/2018 02:41:02 cause X DAMAGE to fail, and so you may not see any screen
11/08/2018 02:41:02 updates via VNC. Either disable 'compiz' (recommended) or
11/08/2018 02:41:02 supply the x11vnc '-noxdamage' command line option.
11/08/2018 02:41:02 X COMPOSITE available on display, using it for window polling.
11/08/2018 02:41:02 To disable this behavior use: '-noxcomposite'
11/08/2018 02:41:02
11/08/2018 02:41:02 Wireframing: -wireframe mode is in effect for window moves.
11/08/2018 02:41:02 If this yields undesired behavior (poor response, painting
11/08/2018 02:41:02 errors, etc) it may be disabled:
11/08/2018 02:41:02 - use '-nowf' to disable wireframing completely.
11/08/2018 02:41:02 - use '-nowcr' to disable the Copy Rectangle after the
11/08/2018 02:41:02 moved window is released in the new position.
11/08/2018 02:41:02 Also see the -help entry for tuning parameters.
11/08/2018 02:41:02 You can press 3 Alt_L's (Left "Alt" key) in a row to
11/08/2018 02:41:02 repaint the screen, also see the -fixscreen option for
11/08/2018 02:41:02 periodic repaints.
11/08/2018 02:41:02 GrabServer control via XTEST.
11/08/2018 02:41:02
11/08/2018 02:41:02 Scroll Detection: -scrollcopyrect mode is in effect to
11/08/2018 02:41:02 use RECORD extension to try to detect scrolling windows
11/08/2018 02:41:02 (induced by either user keystroke or mouse input).
11/08/2018 02:41:02 If this yields undesired behavior (poor response, painting
11/08/2018 02:41:02 errors, etc) it may be disabled via: '-noscr'
11/08/2018 02:41:02 Also see the -help entry for tuning parameters.
11/08/2018 02:41:02 You can press 3 Alt_L's (Left "Alt" key) in a row to
11/08/2018 02:41:02 repaint the screen, also see the -fixscreen option for
11/08/2018 02:41:02 periodic repaints.
11/08/2018 02:41:02
11/08/2018 02:41:02 XKEYBOARD: number of keysyms per keycode 7 is greater
11/08/2018 02:41:02 than 4 and 51 keysyms are mapped above 4.
11/08/2018 02:41:02 Automatically switching to -xkb mode.
11/08/2018 02:41:02 If this makes the key mapping worse you can
11/08/2018 02:41:02 disable it with the "-noxkb" option.
11/08/2018 02:41:02 Also, remember "-remap DEAD" for accenting characters.
11/08/2018 02:41:02
11/08/2018 02:41:02 X FBPM extension not supported.
11/08/2018 02:41:02 X display is not capable of DPMS.
11/08/2018 02:41:02 --------------------------------------------------------
11/08/2018 02:41:02
11/08/2018 02:41:02 Default visual ID: 0x21
11/08/2018 02:41:02 Read initial data from X display into framebuffer.
11/08/2018 02:41:02 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
11/08/2018 02:41:02
11/08/2018 02:41:02 X display :0 is 32bpp depth=24 true color
11/08/2018 02:41:02
11/08/2018 02:41:02 Listening for VNC connections on TCP port 5900
11/08/2018 02:41:02
11/08/2018 02:41:02 Xinerama is present and active (e.g. multi-head).
11/08/2018 02:41:02 Xinerama: number of sub-screens: 1
11/08/2018 02:41:02 Xinerama: no blackouts needed (only one sub-screen)
11/08/2018 02:41:02
11/08/2018 02:41:02 fb read rate: 1051 MB/sec
11/08/2018 02:41:02 fast read: reset -wait ms to: 10
11/08/2018 02:41:02 fast read: reset -defer ms to: 10
11/08/2018 02:41:02 The X server says there are 10 mouse buttons.
11/08/2018 02:41:02 screen setup finished.
11/08/2018 02:41:02
The VNC desktop is: 58d40b626a8f:0
0

Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:
x11vnc -ncache 10 ...
One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...

[CrashPlanEngine] starting...
s6-svwait: fatal: timed out
[services.d] starting xvfb...
[xvfb] starting...
[services.d] starting logmonitor...
[services.d] starting statusmonitor...
[logmonitor] starting...
[services.d] starting openbox...
[statusmonitor] starting...
[openbox] starting...
[services.d] starting x11vnc...
[services.d] starting app...
[x11vnc] starting...
[app] starting CrashPlan for Small Business...
12/08/2018 01:05:36 passing arg to libvncserver: -rfbport
12/08/2018 01:05:36 passing arg to libvncserver: 5900
12/08/2018 01:05:36 passing arg to libvncserver: -rfbportv6
12/08/2018 01:05:36 passing arg to libvncserver: -1
12/08/2018 01:05:36 passing arg to libvncserver: -httpportv6
12/08/2018 01:05:36 passing arg to libvncserver: -1
12/08/2018 01:05:36 passing arg to libvncserver: -desktop
12/08/2018 01:05:36 passing arg to libvncserver: CrashPlan for Small Business
12/08/2018 01:05:36 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 1955
12/08/2018 01:05:36 Using X display :0
12/08/2018 01:05:36 rootwin: 0x43 reswin: 0x400001 dpy: 0xd4d3aa00
12/08/2018 01:05:36
12/08/2018 01:05:36 ------------------ USEFUL INFORMATION ------------------
[services.d] done.
12/08/2018 01:05:36 X DAMAGE available on display, using it for polling hints.
12/08/2018 01:05:36 To disable this behavior use: '-noxdamage'
12/08/2018 01:05:36
12/08/2018 01:05:36 Most compositing window managers like 'compiz' or 'beryl'
12/08/2018 01:05:36 cause X DAMAGE to fail, and so you may not see any screen
12/08/2018 01:05:36 updates via VNC. Either disable 'compiz' (recommended) or
12/08/2018 01:05:36 supply the x11vnc '-noxdamage' command line option.
12/08/2018 01:05:36 X COMPOSITE available on display, using it for window polling.
12/08/2018 01:05:36 To disable this behavior use: '-noxcomposite'
12/08/2018 01:05:36
12/08/2018 01:05:36 Wireframing: -wireframe mode is in effect for window moves.
12/08/2018 01:05:36 If this yields undesired behavior (poor response, painting
12/08/2018 01:05:36 errors, etc) it may be disabled:
12/08/2018 01:05:36 - use '-nowf' to disable wireframing completely.
12/08/2018 01:05:36 - use '-nowcr' to disable the Copy Rectangle after the
12/08/2018 01:05:36 moved window is released in the new position.
12/08/2018 01:05:36 Also see the -help entry for tuning parameters.
12/08/2018 01:05:36 You can press 3 Alt_L's (Left "Alt" key) in a row to
12/08/2018 01:05:36 repaint the screen, also see the -fixscreen option for
12/08/2018 01:05:36 periodic repaints.
12/08/2018 01:05:36 GrabServer control via XTEST.
12/08/2018 01:05:36
12/08/2018 01:05:36 Scroll Detection: -scrollcopyrect mode is in effect to
12/08/2018 01:05:36 use RECORD extension to try to detect scrolling windows
12/08/2018 01:05:36 (induced by either user keystroke or mouse input).
12/08/2018 01:05:36 If this yields undesired behavior (poor response, painting
12/08/2018 01:05:36 errors, etc) it may be disabled via: '-noscr'
12/08/2018 01:05:36 Also see the -help entry for tuning parameters.
12/08/2018 01:05:36 You can press 3 Alt_L's (Left "Alt" key) in a row to
12/08/2018 01:05:36 repaint the screen, also see the -fixscreen option for
12/08/2018 01:05:36 periodic repaints.
12/08/2018 01:05:36
12/08/2018 01:05:36 XKEYBOARD: number of keysyms per keycode 7 is greater
12/08/2018 01:05:36 than 4 and 51 keysyms are mapped above 4.
12/08/2018 01:05:36 Automatically switching to -xkb mode.
12/08/2018 01:05:36 If this makes the key mapping worse you can
12/08/2018 01:05:36 disable it with the "-noxkb" option.
12/08/2018 01:05:36 Also, remember "-remap DEAD" for accenting characters.
12/08/2018 01:05:36
12/08/2018 01:05:36 X FBPM extension not supported.
12/08/2018 01:05:36 X display is not capable of DPMS.
12/08/2018 01:05:36 --------------------------------------------------------
12/08/2018 01:05:36
12/08/2018 01:05:36 Default visual ID: 0x21
12/08/2018 01:05:36 Read initial data from X display into framebuffer.
12/08/2018 01:05:36 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
12/08/2018 01:05:36
12/08/2018 01:05:36 X display :0 is 32bpp depth=24 true color
12/08/2018 01:05:36
12/08/2018 01:05:36 Listening for VNC connections on TCP port 5900
12/08/2018 01:05:36
12/08/2018 01:05:36 Xinerama is present and active (e.g. multi-head).
12/08/2018 01:05:36 Xinerama: number of sub-screens: 1
12/08/2018 01:05:36 Xinerama: no blackouts needed (only one sub-screen)
12/08/2018 01:05:36
12/08/2018 01:05:36 fb read rate: 1129 MB/sec
12/08/2018 01:05:36 fast read: reset -wait ms to: 10
12/08/2018 01:05:36 fast read: reset -defer ms to: 10
12/08/2018 01:05:36 The X server says there are 10 mouse buttons.
12/08/2018 01:05:36 screen setup finished.
12/08/2018 01:05:36
The VNC desktop is: 58d40b626a8f:0
0

Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?
The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:
x11vnc -ncache 10 ...
One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...
[CrashPlanEngine] starting...

Look at the following files under /mnt/user/appdata/CrashPlanPRO/log/:

engine_error.log
engine_output.log
service.log.0

There should be an error message that would help determine why the engine is not starting.

I apologize for the delay in my response. Thank you very much for your quick response.
-engine_error.log is completely blank (opened using TextEdit on Mac)
-engine_output.log is completely blank (opened using TextEdit on Mac)
-service.log.0 (also opened with TextEdit on Mac) does contains a substantial amount of data, but nothing that seems to directly relate to the crashplan engine service. At least that i can tell.
I've attached all three files, i suspect you can interpret the data much better than i, as i am not much of a .nix guy.
crashplanprologs.zip

This seems to be the reason why the engine is not starting:
[08.12.18 01:13:44.529 ERROR SMListener 0 p42.service.ClientServiceManager] CSM:: Service UniversalStorageService failed while STARTING, java.io.IOException: IO error: /usr/local/crashplan/conf/udb/MANIFEST-000039: No such file or directory

So looks like there is something wrong with the internal file structure.  Can you try to update to the latest container image and try again to start with a clear appdata folder ?  CrashPlan should show you the initial setup wizard.

container image updated. Unable to clear the appdata folder with read-only errors. Tried deleting and created new docker image to no avail.
Here's my container log after updating to the latest container image:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
chown: /config/conf/.cpb: Read-only file system
chown: /config/conf/udb/CURRENT: Read-only file system
chown: /config/conf/udb/LOCK: Read-only file system
chown: /config/conf/udb/000048.ldb: Read-only file system
chown: /config/conf/udb/000050.ldb: Read-only file system
chown: /config/conf/udb/LOG.old: Read-only file system
chown: /config/conf/udb/LOG: Read-only file system
chown: /config/conf/udb: Read-only file system
chown: /config/conf/udb: Read-only file system
chown: /config/conf/service.login: Read-only file system
chown: /config/conf/service.model: Read-only file system
chown: /config/conf: Read-only file system
chown: /config/conf: Read-only file system
chown: /config/bin: Read-only file system
chown: /config/bin: Read-only file system
chown: /config/log/nginx: Read-only file system
chown: /config/log/nginx: Read-only file system
chown: /config/log: Read-only file system
chown: /config/log: Read-only file system
chown: /config/cache/41/cpfmfp: Read-only file system
chown: /config/cache/41/cpbmf.blc: Read-only file system
chown: /config/cache/41: Read-only file system
chown: /config/cache/41: Read-only file system
chown: /config/cache/cpss1: Read-only file system
chown: /config/cache/cpss825943348368829716: Read-only file system
chown: /config/cache/cpgft1: Read-only file system
chown: /config/cache/cpft1_41: Read-only file system
chown: /config/cache/cpgft825943348368829716: Read-only file system
chown: /config/cache/cpft825943348368829716_41: Read-only file system
chown: /config/cache/cpft1_41x: Read-only file system
chown: /config/cache/cpft1_41i: Read-only file system
chown: /config/cache/cpgft1x: Read-only file system
chown: /config/cache/cpgft1i: Read-only file system
chown: /config/cache/cpft825943348368829716_41x: Read-only file system
chown: /config/cache/cpft825943348368829716_41i: Read-only file system
chown: /config/cache/cpgft825943348368829716x: Read-only file system
chown: /config/cache/cpgft825943348368829716i: Read-only file system
chown: /config/cache: Read-only file system
chown: /config/cache: Read-only file system
chown: /config/var/.identity: Read-only file system
chown: /config/var/service.pem: Read-only file system
chown: /config/var/.ui_info: Read-only file system
chown: /config/var: Read-only file system
chown: /config/var: Read-only file system
chown: /config/repository/metadata/v3e/ldb/000016.ldb: Read-only file system
chown: /config/repository/metadata/v3e/ldb/000018.ldb: Read-only file system
chown: /config/repository/metadata/v3e/ldb/000023.ldb: Read-only file system
chown: /config/repository/metadata/v3e/ldb/CURRENT: Read-only file system
chown: /config/repository/metadata/v3e/ldb/LOCK: Read-only file system
chown: /config/repository/metadata/v3e/ldb/000026.ldb: Read-only file system
chown: /config/repository/metadata/v3e/ldb: Read-only file system
chown: /config/repository/metadata/v3e/ldb: Read-only file system
chown: /config/repository/metadata/v3e/ldb_metadata/CURRENT: Read-only file system
chown: /config/repository/metadata/v3e/ldb_metadata/LOCK: Read-only file system
chown: /config/repository/metadata/v3e/ldb_metadata: Read-only file system
chown: /config/repository/metadata/v3e/ldb_metadata: Read-only file system
chown: /config/repository/metadata/v3e: Read-only file system
chown: /config/repository/metadata/v3e: Read-only file system
chown: /config/repository/metadata: Read-only file system
chown: /config/repository/metadata: Read-only file system
chown: /config/repository: Read-only file system
chown: /config/repository: Read-only file system
chown: /config/.oracle_jre_usage/7afa04cd43c56b30.timestamp: Read-only file system
chown: /config/.oracle_jre_usage: Read-only file system
chown: /config/.oracle_jre_usage: Read-only file system
chown: /config/xdg/cache/openbox/sessions: Read-only file system
chown: /config/xdg/cache/openbox/sessions: Read-only file system
chown: /config/xdg/cache/openbox/openbox.log: Read-only file system
chown: /config/xdg/cache/openbox: Read-only file system
chown: /config/xdg/cache/openbox: Read-only file system
chown: /config/xdg/cache/fontconfig/CACHEDIR.TAG: Read-only file system
chown: /config/xdg/cache/fontconfig/aaac3452274625c4167ca2eab9cb5e70-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/3830d5c3ddfd5cd38a049b759396e72e-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/df311e82a1a24c41a75c2c930223552e-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/17090aa38d5c6f09fb8c5c354938f1d7-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/2d31a572ce6667f6a0da9c8dc611898b-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/a1c95d6dfc9a7b34f44445cf81166004-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/5ca8086aeacc9c68e81a71e7ef846b3b-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/8d4af663993b81a124ee82e610bb31f9-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig/923e285e415b1073c8df160bee08820f-le64.cache-7: Read-only file system
chown: /config/xdg/cache/fontconfig: Read-only file system
chown: /config/xdg/cache/fontconfig: Read-only file system
chown: /config/xdg/cache: Read-only file system
chown: /config/xdg/cache: Read-only file system
chown: /config/xdg/config/CrashPlan/Local Storage/file__0.localstorage-journal: Read-only file system
chown: /config/xdg/config/CrashPlan/Local Storage/file__0.localstorage: Read-only file system
chown: /config/xdg/config/CrashPlan/Local Storage: Read-only file system
chown: /config/xdg/config/CrashPlan/Local Storage: Read-only file system
chown: /config/xdg/config/CrashPlan/Cookies-journal: Read-only file system
chown: /config/xdg/config/CrashPlan/Preferences: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache/index: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache/data_0: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache/data_1: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache/data_2: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache/data_3: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache: Read-only file system
chown: /config/xdg/config/CrashPlan/Cache: Read-only file system
chown: /config/xdg/config/CrashPlan/Cookies: Read-only file system
chown: /config/xdg/config/CrashPlan: Read-only file system
chown: /config/xdg/config/CrashPlan: Read-only file system
chown: /config/xdg/config: Read-only file system
chown: /config/xdg/config: Read-only file system
chown: /config/xdg: Read-only file system
chown: /config/xdg: Read-only file system
chown: /config/.pki/nssdb/pkcs11.txt: Read-only file system
chown: /config/.pki/nssdb/cert9.db: Read-only file system
chown: /config/.pki/nssdb/key4.db: Read-only file system
chown: /config/.pki/nssdb: Read-only file system
chown: /config/.pki/nssdb: Read-only file system
chown: /config/.pki: Read-only file system
chown: /config/.pki: Read-only file system
chown: /config: Read-only file system
chown: /config: Read-only file system
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] crashplan-pro.sh: executing...
sed: can't move '/config/var/.ui_infoelGkOh' to '/config/var/.ui_info': Read-only file system
[cont-init.d] crashplan-pro.sh: exited 1.
[services.d] stopping services
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

There is something wrong with your install.  Did you installed the container via the Community Applications plugin?
Once you removed the container, you should be able to remove the appdata folder via the terminal by executing the command rm -rf /mnt/user/appdata/CrashPlanPRO.  Then re-install the container via the CA plugin and make sure to keep default settings.

Closing this issue.  Please re-open if needed.


Add person detect tflite test

Add TFLite Micro quantized person_detect.tflite model from
https://github.com/tensorflow/tflite-micro

This test also failed at the same std:addi operand data type issue.


Projects p off center when p text is short

When the text inside p projects is short, I mean 30 words for example, h1 and p project does not center.

In which position can you  face the problem  post any screenshot


RHOAIENG-4346 Harden backend security

Closes: RHOAIENG-4346
Description

Removes the backend /api/proxy endpoint and replaces it with bespoke service endpoints for pipelines, trustyai and mlmd apis.
How Has This Been Tested?

Deploy to a cluster
Verify pipelines functionality works as expected
Verify bias metrics functionality works as expected

Test Impact

Existing tests updated and reworked to cover changes to functionality.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[x] The developer has tested their solution on a cluster by using the image produced by the PR to main

I've temporarily added a hold as this PR still needs to be tested deployed on a cluster.

Tested locally and on cluster setup by Alex.
For local testing, used kubectl port-forward for all 3 end points.
Tested mlmd endpoint using postman. Endpoint returns 404 on cluster.'
/lgtm

/approve


baker cat is forgetful

hello fellow bakers
baker cat is many things.... forgetful is not one of them. we must make the time baked persist.

Yes it does persist for me (safari mobile and chrome)

i tried it before you had implemented persistent time and did not notice your commit. pusheen was made great again. #MBCGA


add Support for debian 10/buster

Hello,
Thank you for this PR.
Could you please update metada.json file, doc (README) and tests. It would be great :-)
Thank you.
Regards,

Hi, sorry i missed your comment! I added the suggested edits...


Add support for neighbours on container view

Automatically add all neighbours of the system software to the diagram

https://github.com/structurizr-php/structurizr-php/pull/72

Merged in https://github.com/structurizr-php/structurizr-php/commit/e63bc22b8447f9c0c669a20d6062c3242b6ebf7b


Random error "You can only create one Muuri Item per element!"

Thank you for forking this and making it install compatible with React 17.
I get this error "You can only create one Muuri Item per element!" randomly even when then are no changes to the code, just with a file save and even after a full page refresh.
The error is originated from here muuri/src/Item/Item.js#L39 and it seems it's something new in muuri 0.9 to cache the items used.
I forked your repo and changed:
"peerDependencies": {
  "muuri": "^0.8.0 || ^0.9.0",
  "react": "^17.0.2"
},

to allow install muuri 0.8 and it seems like it's working fine so far without this issue.
I even looked at 0.8 code and there is no such mechanist nor that error thrown.
Do you have a clue how to fix this issue so to make it muuri 0.9 compatible?
The most strange part is that the error occurs even after a full page reload!
I think muuri-react should install with muuri 0.8 until this issue gets sorted.

have you figured it out yet? I have the same issue.


sushid - connecting nodes is broken

I cannot connect my node to another node with --node= or -n

It says the node is standalone

ah ok - you have to specify the port - doh! maybe if no port is given it could assume 80? not sure - anyway closing for now


Chore/dependency updates

Replace shikiji with shiki after it has been merged.
Update esbuild, also had breaking changes but nothing that affected us.

The preview looks good


Authorisation of pushes (and pulls)? (如何(类似twitch)只能推流到预设stream key？)

I am just digging through the documentation and wondering what is the proper way to manage who can push to which key.
Let's say, in twitch, each user is assigned a stream key so you could fill into OBS. When I am testing with SRS I found that any user can just push to any stream.
Surely, there is a way to manage streaming authorization, but I am just stuck at where to go here.
I am using Python / Django backend but it's ok to switch to ExpressJS.
(in Chinese: 如何实现最基础的功能，类似twitch，只能推到预分配的stream key？如果stream key对不上就不能push)
I understand A HTTP hook may need to be used but just wondering if this is documented.

You can use HTTP callback, which calls your server with stream key and .token. Then, you can verify the client ip, url, stream key and token. Finally, response a none 0 to SRS, SRS will reject the publishing or playing.


"Office" 365 User steps are out of date

https://learn.microsoft.com/en-us/azure/marketplace/partner-center-portal/commercial-marketplace-lead-management-instructions-dynamics#office-365

Isn't this Microsoft 365 now?
The steps refer to Dynamics 365 for Customer Engagement which was deprecated in 2019

What is the minimum license required?

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

ID: e3b6fc89-d68c-d144-4819-bf7d4185fed6
Version Independent ID: e3b6fc89-d68c-d144-4819-bf7d4185fed6
Content: Deprecation: Dynamics 365 for Customer Engagement (Dynamics 365 Marketing)
Content Source: ce/marketing/ce-deprecation.md
Service: dynamics-365-marketing
GitHub Login: @alfergus
Microsoft Alias: alfergus

@askpatrickw
Thanks for your feedback! We will investigate and update as appropriate.

@KrishnaG-MSFT
Please review it.

@SadiqhAhmed-MSFT
Please review it.

@jasongroce Could you please help redirecting this issue to someone who works on the Azure Marketplace docs?

#reassign:sarahsnow-msft   @Sarahsnow-msft would this be something you could take a look at?

#reassign:trkeya @trkeya

Closing due to lack of follow through.


Save file diff as html

VS Code has great file diff layout and algoithm. It currently is a huge loss that you cannot save the diff output as a html or pdf. Please make diff export a possibility.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Retry failed requests

A very useful feature is apparently missing — ability to transparently retry requests, before failing, and configurable number of retries.

You can make custom HttpClient with custom retry logic. Like using DefaultMethodRetryHandler even create cutom Retry handler.

While we could re-configure httpclient, the whole point of Unirest is easy and consistent abstraction across different languages. So it would be great if unirest provides that abstraction to enable retry.

maybe wrapper with guava-retrying is another choice

maybe wrapper with guava-retrying is another choice


Version changes for Randoop and Daikon (plus Randoop eval script)

Updates Randoop and Daikon versions. Adds evaluation script restricted to Randoop.

I was dawdling on the other pull request because I was thinking about making a more universal script to run an arbitrary subset of tools over an arbitrary subset of the corpus, but I'll figure that out later.


Vim9: cannot use "is#" or "is?" inside :def function

Describe the bug
We cannot use is# or is? inside a :def function.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9script
    def Func()
        echo 'abc' is# 'ABC'
    enddef
    defcompile
EOF
)

E15 is raised:
E15: Invalid expression:  is# 'ABC'

Expected behavior
No error is raised.
Environment

Vim version: 8.2 Included patches: 1-1307
OS: Ubuntu 16.04.6 LTS
Terminal: XTerm(356)

Additional context
is# works as expected if you run the code at the script level:
vim9script
echo 'abc' is# 'ABC'

v:false

This is inconsistent.  I would expect is# to work everywhere, including in a :def function, or to fail everywhere, including at the script level.

The same issue applies to is?:
vim9script
def Func()
    echo 'abc' is? 'ABC'
enddef
defcompile

E15: Invalid expression:  is? 'ABC'

is# and is? work as expected if you replace them with is:
vim9script
def Func()
   echo 'abc' is 'ABC'
enddef
defcompile

Maybe is# and is? are meant to be deprecated in Vim9 script in favor of new comparison operators, like ===:

These ones are not backwards compatible, we'll fix this in Vim9 script:
Also, "'' == 0" evaluates to true, which isn't nice.
Add "===" to have a strict comparison (type and value match).
Add "==*" (?) to have a value match, but no automatic conversion, and v:true
equals 1 and 1.0, v:false equals 0 and 0.0.?

Source.
This would be in line with the fact that, in Vim9 script, 'ignorecase' should be ignored by comparison operators:
https://github.com/vim/vim/blob/0aac67a4314d72a29d3fbee91b6f0ba89e950462/runtime/doc/vim9.txt#L355-L357
And is? does not ignore 'ignorecase'; so dropping it would make sense.
If so, maybe the help should mention this difference at :h vim9-differences.
diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index 2ba227527..531dc14de 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -355,6 +355,7 @@ These commands are too quickly confused with local variable names.
 Comparators ~

 The 'ignorecase' option is not used for comparators that use strings.
+|expr-is#|, |expr-is?|, |expr-isnot#| and |expr-isnot?| cannot be used.

 White space ~

And is? does not ignore 'ignorecase'; so dropping it would make sense.

Actually, I was wrong, it does 'ignorecase', since is? always ignores the case regardless of the value of the latter option.

This was a mistake from the past.  "is" checks identity, thus matching or ignoring case is irrelevant.  In Vim9 script we are more strict about not allowing things that don't work, thus we give an error.
You first mention that you expected "is#" to work, perhaps I'm missing something?

This was a mistake from the past. "is" checks identity, thus matching or ignoring case is irrelevant.

But the case is still relevant:
vim9script
echo 'abc' is? 'ABC'

v:true

If the case was irrelevant, I would expect this expression to be false, because 'abc' and 'ABC' are not the same string; but it's true.

In Vim9 script we are more strict about not allowing things that don't work, thus we give an error.

If is# and is? are disallowed in Vim9 script, then I think they should also be disallowed at the script level; not just in a :def function.  Right now, the results are inconsistent between the 2 contexts:
vim9script
echo 'abc' is? 'ABC'

v:true

vim9script
def Func()
    echo 'abc' is? 'ABC'
enddef
Func()

E15: Invalid expression:  is? 'ABC'

The same command doesn't raise any error at the script level, while it raises E15 in a :def function.

You first mention that you expected "is#" to work, perhaps I'm missing something?

I'm still used to write is# in Vim script legacy, where it doesn't raise any error.  And again, it doesn't raise any error in a Vim9 script at the script level, so why does it raise an error only in a :def function?
I'm not saying it should work; if it's meant to be deprecated or disallowed, then that's fine.  But I think it should:

be disallowed in a consistent manner (script level + :def)
be documented at :h vim9-differences

This was a mistake from the past. "is" checks identity, thus matching or ignoring case is irrelevant.

Oh, I see what you mean now.  Yes, I always had difficulties understanding why is# and is? existed in the first place.  is is enough, and is#/is? don't make much sense, so there is no point in replicating them in Vim9 script.
However, I think my previous point still stands: is# and is? should be disallowed everywhere, including at the script level.

is is enough

To be clear, the reason why is is enough in Vim9 script (not in legacy Vim script), is because just like any other comparison operator, it ignores 'ignorecase':
vim9script
set ignorecase
echo 'abc' is 'ABC'

v:false

vim9script
def Func()
    set ignorecase
    echo 'abc' is 'ABC'
enddef
Func()

v:false

I'm closing this issue because I think it's getting confusing, and the initial report is no longer valid.
The title should not be:
Vim9: cannot use "is#" or "is?" inside :def function

But:
Vim9: "is#" and "is?" should be disallowed at the script level

I will open a new updated report later.


Updated FalconPy integration

This update moves this solution over to use the FalconPy library for CrowdStrike Falcon registry interactions.

LGTM


updates and some tidying

updated to Fabric Loader 0.4
updated to Minecraft 1.14 Pre-Release 2
cleaned up code a bit
bumped version to 3.2

I wanted to do this but I don’t have time, thanks again <3


[[DOCS]] Remove david-dm badges

The site is down, from archive.org it seems since October or November: https://web.archive.org/web/*/david-dm.org . The last snapshot shows the most announcement was 2016, so it seems the service has not been maintained in a while.

Coverage remained the same at 100.0% when pulling e5f717e0dcda2a691020c4fb203fc82f56e96d32 on adamchainz:patch-1 into 5608b0351972daf173c7ec480ba7d1e1b6a3f3e3 on jshint:main.

Thanks for the research and for taking the time to fix this!


Switch from Lyricsfreak to Lyricsmode

Checklist:

[x] I have checked that there are no issues with similar or the same content
YOU SHOULD CHECK CLOSED ISSUES ASWELL

[x] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there

[x] I have double checked and can reproduce the issue

OS:
MacOS Mojave
GPMDP Version:
4.6.1
Issue Descriptions:
Lyricsfreak is not more available
Steps to Reproduce:
Check DNS
Possible Solution
After some research, is the problem is fixed when changing from lyricsfreak.com to lyricsmode.com.
After changing IP of lyricsfreak.com in hosts file lyrics are displayed and GPMDP does not crash anymore.

Happy to accept a PR that does this


TypeError from aiohttp integration when explicitly passing None for ClientSession's trace_configs kwarg

How do you use Sentry?
Sentry Saas (sentry.io)
Version
1.27.0
Steps to Reproduce
D:\>py -3.11 -m venv .venv

D:\>cd .venv

D:\.venv>Scripts\activate.bat

(.venv) D:\.venv>pip install aiohttp sentry-sdk
Collecting aiohttp
  Downloading aiohttp-3.8.4-cp311-cp311-win_amd64.whl (317 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 317.2/317.2 kB 3.9 MB/s eta 0:00:00
Collecting sentry-sdk
  Using cached sentry_sdk-1.27.0-py2.py3-none-any.whl (211 kB)
Collecting attrs>=17.3.0
  Using cached attrs-23.1.0-py3-none-any.whl (61 kB)
Collecting charset-normalizer<4.0,>=2.0
  Downloading charset_normalizer-3.1.0-cp311-cp311-win_amd64.whl (96 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 96.7/96.7 kB 5.4 MB/s eta 0:00:00
Collecting multidict<7.0,>=4.5
  Downloading multidict-6.0.4-cp311-cp311-win_amd64.whl (28 kB)
Collecting async-timeout<5.0,>=4.0.0a3
  Using cached async_timeout-4.0.2-py3-none-any.whl (5.8 kB)
Collecting yarl<2.0,>=1.0
  Downloading yarl-1.9.2-cp311-cp311-win_amd64.whl (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.2/60.2 kB ? eta 0:00:00
Collecting frozenlist>=1.1.1
  Downloading frozenlist-1.3.3-cp311-cp311-win_amd64.whl (32 kB)
Collecting aiosignal>=1.1.2
  Using cached aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Collecting certifi
  Using cached certifi-2023.5.7-py3-none-any.whl (156 kB)
Collecting urllib3>=1.26.11
  Downloading urllib3-2.0.3-py3-none-any.whl (123 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 123.6/123.6 kB 7.6 MB/s eta 0:00:00
Collecting idna>=2.0
  Using cached idna-3.4-py3-none-any.whl (61 kB)
Installing collected packages: urllib3, multidict, idna, frozenlist, charset-normalizer, certifi, attrs, async-timeout, yarl, sentry-sdk, aiosignal, aiohttp
Successfully installed aiohttp-3.8.4 aiosignal-1.3.1 async-timeout-4.0.2 attrs-23.1.0 certifi-2023.5.7 charset-normalizer-3.1.0 frozenlist-1.3.3 idna-3.4 multidict-6.0.4 sentry-sdk-1.27.0 urllib3-2.0.3 yarl-1.9.2

[notice] A new release of pip available: 22.3 -> 23.1.2
[notice] To update, run: python.exe -m pip install --upgrade pip

(.venv) D:\.venv>python
Python 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import sentry_sdk
>>> sentry_sdk.init(debug=True)
 [sentry] DEBUG: Setting up integrations (with default = True)
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.django.DjangoIntegration: Django not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.flask.FlaskIntegration: Flask is not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.starlette.StarletteIntegration: Starlette is not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.fastapi.FastApiIntegration: Starlette is not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.bottle.BottleIntegration: Bottle not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.falcon.FalconIntegration: Falcon not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.sanic.SanicIntegration: Sanic not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.celery.CeleryIntegration: Celery not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.rq.RqIntegration: RQ not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.tornado.TornadoIntegration: Tornado not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.sqlalchemy.SqlalchemyIntegration: SQLAlchemy not installed.
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.pyramid.PyramidIntegration: Pyramid not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.boto3.Boto3Integration: botocore is not installed
 [sentry] DEBUG: Did not import default integration sentry_sdk.integrations.httpx.HttpxIntegration: httpx is not installed
 [sentry] DEBUG: Setting up previously not enabled integration logging
 [sentry] DEBUG: Setting up previously not enabled integration stdlib
 [sentry] DEBUG: Setting up previously not enabled integration excepthook
 [sentry] DEBUG: Setting up previously not enabled integration dedupe
 [sentry] DEBUG: Setting up previously not enabled integration atexit
 [sentry] DEBUG: Setting up previously not enabled integration modules
 [sentry] DEBUG: Setting up previously not enabled integration argv
 [sentry] DEBUG: Setting up previously not enabled integration threading
 [sentry] DEBUG: Setting up previously not enabled integration aiohttp
 [sentry] DEBUG: Setting up previously not enabled integration redis
 [sentry] DEBUG: Did not enable default integration redis: Redis client not installed
 [sentry] DEBUG: Enabling integration logging
 [sentry] DEBUG: Enabling integration stdlib
 [sentry] DEBUG: Enabling integration excepthook
 [sentry] DEBUG: Enabling integration dedupe
 [sentry] DEBUG: Enabling integration atexit
 [sentry] DEBUG: Enabling integration modules
 [sentry] DEBUG: Enabling integration argv
 [sentry] DEBUG: Enabling integration threading
 [sentry] DEBUG: Enabling integration aiohttp
 [sentry] DEBUG: Enabling integration redis
 [sentry] DEBUG: Setting SDK name to 'sentry.python.aiohttp'
<sentry_sdk.hub._InitGuard object at 0x000001A36AFE1010>
>>> import aiohttp
>>> aiohttp.ClientSession(trace_configs=None)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "D:\.venv\Lib\site-packages\sentry_sdk\integrations\aiohttp.py", line 186, in init
    client_trace_configs = list(kwargs.get("trace_configs", ()))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not iterable

Expected Result
Passing None for trace_configs when initializing aiohttp.ClientSession should not error.
Actual Result
TypeError: 'NoneType' object is not iterable is raised, due to:
https://github.com/getsentry/sentry-python/blob/d0f8d98c8554092ab3acc989052cb8d33ad6d374/sentry_sdk/integrations/aiohttp.py#L186 as part of:
https://github.com/getsentry/sentry-python/blob/d0f8d98c8554092ab3acc989052cb8d33ad6d374/sentry_sdk/integrations/aiohttp.py#L178-L193 which was added in #1761.
I originally encountered this through discord.py:
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.10.10/x64/lib/python3.10/site-packages/discord/client.py", line 706, in start
    await self.login(token)
  File "/opt/hostedtoolcache/Python/3.10.10/x64/lib/python3.10/site-packages/discord/client.py", line 560, in login
    data = await self.http.static_login(token.strip())
  File "/opt/hostedtoolcache/Python/3.10.10/x64/lib/python3.10/site-packages/discord/http.py", line 549, in static_login
    self.__session = aiohttp.ClientSession(
  File "/opt/hostedtoolcache/Python/3.10.10/x64/lib/python3.10/site-packages/sentry_sdk/integrations/aiohttp.py", line 186, in init
    client_trace_configs = list(kwargs.get("trace_configs", ()))
TypeError: 'NoneType' object is not iterable

https://github.com/Harmon758/Harmonbot/actions/runs/5457981724/jobs/9932576322?pr=5638#step:8:22
https://github.com/Rapptz/discord.py/blob/c448932fa0a35e347f3e963436df62f575aa740b/discord/http.py#L790-L794

@Harmon758 Thanks for the report and the fix!

Released in 1.27.1.


Wrong package name in import line in example

Your example line has
import { calendarRange } from 'vue-calendar'

but the package name is vue-calendar-picker so the line should be:
import { calendarRange } from 'vue-calendar-picker'

Thanks !


Suggest a book

A form to have people suggest a book they don't see.

Did you want to save this information in the database or something simpler like send an email to you/somewhere?

Email would be great!
On Monday, April 27, 2015, Brandon Martin<EMAIL_ADDRESS>wrote:

Did you want to save this information in the database or something simpler
like send an email to you/somewhere?
—
Reply to this email directly or view it on GitHub
https://github.com/seanhess/serials/issues/5#issuecomment-96769942.

I'm putting in a very simple "Don't see what you want? Email us at xxxx" prompt. Feel free to improve it if you want to do something cooler.

That is great, I plan on trying to kick in on a few of these soon. Just been super busy :smile:


Not working when displaying from a Raspbery Pi / Android sticker

First off - sweet framework!  I love it!  thanks for creating this :)
We wanted to run an office dashboard so we got a Raspbery Pi to connect to a TV.  Raspbery Pi was having a bunch of issues rendering the CSS for Dashing.  We switched over to an android stick (which we bought just for this) and the Dashing page is completely blank when we open it on the built in browser.
Has anyone had this happen to them?  We are using heroku to host the site and it works fine on our phones and desktops.  It seems to just not work fully if we try to display it from the Raspberry Pi or Android Stick.  Thanks for the help!

Have you tried any of these suggestions?
https://gist.github.com/stonehippo/5896381

I'm using dashing on a pi (last gen, and current gen) and to get it to work well I had to pre-compile the assets first then serve them from /public on the pi.

@pushmatrix Thanks for the suggestions!  I had looked at that page earlier - we're serving the site from heroku and are just want to load the dashboard in the browser - I think that the explanation loads it onto the raspberry pi directly.
Anyone experienced any issues loading it from a separate server?

We're running 4 separate dashboards off of one server with 4 different raspberry pi's displaying each dashboard with no problems.
We're running the dashing server in a VM hosted on a private cluster we have but I've ran it on a digital ocean box before with no problems?
Are you doing anything non-standard as far as the dashboard or widgets is concerned?

Any updates on this?
Dashing works fine over an unimpeded network connection.
My bet is that the browser is failing to render it. Can you see the browser console on either device?
@nikilster - What browser are you using on the Pi?
@mattrayner - What browser are you using on your Pi's?

@tylermauthe I'm using Chromium on Raspbian for each pi

We are using dashing on a dozen + pi's and it's generally worked well. Each pi boots into kiosk mode and loads the assigned url. The setup we used for each pi is similar to this https://www.danpurdy.co.uk/web-development/raspberry-pi-kiosk-screen-tutorial/. Hope it helps point you in the right direction.


map should take Key by reference

Like #21.
If the Keys become reasonably large (heapless::String), there is a lot of stack thrashing for move and cloning going on.
There doesn't appear to be the need to move/own the key for either fetch_item or store_item, other than for caching. The key should be taken by reference.
On a similar note, there is no need to take range by value, just take it by reference and clone if absolutely necessary.

Hi, I guess a reference would work. The key trait requires it to be clone, so when a copy is needed for storing in cache, the clone could still be made. This would be a breaking change though.
For range, I'm not gonna change it since edition 2024 will make the type Copy.


docs: Add owners file

Signed-off-by: feng-tao<EMAIL_ADDRESS>
Summary of Changes
Add OWNER file
Documentation

CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely, including a title prefix.
[ ] PR includes a summary of changes.
[ ] My commits follow the guidelines from "How to write a good git commit message"

yeap


[docker] Add debian, upgrade autoconf Ubuntu dependency

Hello memcached!
Following my previous docker maintenance work (#988), here is another small docker PR.
This one is two-fold:

Add a new Debian dockerfile. (perhaps not needed yet, as maintainers are running Debian already?). I do not know which distributions memcached focuses on, but with this file in place without much effort, the Debian people out there might be happier.

Use latest automake dependency to build and test ubuntu and debian images. From git history, I understand that v1.11 was verison locked back in 2018 with the initial push for the Ubuntu dockerfile. From what I can tell, the current automake version is 1.16.x.

Thanks! Fwiw mc is distro-agnostic, but I develop on ubuntu/debian.

Released in 1.6.20


Bogus cast introduced in PR 6690

Problem
https://github.com/project-chip/connectedhomeip/pull/6690 has a commit entitled "Fix type conversion error" which "fixes" the error by adding a reinterpret_cast from uint8_t** to ByteSpan*.
If we assume write is true, we are now going to read the the data pointer and size from the Span so we can do the memcpy.  The data pointer we will read is the uint8_t* value.  The size we will read is ... looks like some combination of the FabricConnected, OffPremiseServicesReachableIPv4, OffPremiseServicesReachableIPv6, and the random padding byte.  This is unlikely to end well.
If write is false, we will read whatever ByteSpan value was passed in and try to write it to the struct.  We'll write its data pointer to the uint8_t*, write the size to the booleans and padding byte, then later try to treat the uint8_t* as a Pascal string and bad things will happen.
Proposed Solution
Depending on how close we are to supporting CHAR_STRING in structs (@vivien-apple ?), one of:

Enable that support and remove the cast.
Revert #6690
Switch this member to OCTET_STRING for now until CHAR_STRING is enabled, add comment and file followup issue.

And stop adding reinterpret_casts just to get things to compile....
@yufengwangca @andy31415 @woody-apple

This issue was introduced from #6596.

chip::ByteSpan * {{name}}Span = &entry->{{name}}; // {{type}}

Is this addition valid?

And if the new cluster had been added to src/darwin/Framework/CHIP/chip-tool.zap, which actually tests this sort of thing in CI, this would have been caught, fwiw....  Also would have caught it not being added to src/controller/controller-clusters.zap.
Also would have been good to add to examples/chip-tool/chip-tool.zap

Is this addition valid?

It's correct for OCTET_STRING.  CHAR_STRING, again is not supported in structs yet.

My new cluster does not get added to chip-tool, this issue was discovered from any server side zaps.

I prefer taking out item "Name" from structure for now and add comments the file a followup issue.

Filed https://github.com/project-chip/connectedhomeip/issues/6805 to change the type back to CHAR_STRING when we can.


Some Thoughts

(This is a seriously awesome package)
I opened a fork here: https://github.com/shellscape/doiuse-email. The biggest change there is that I swapped out the build system with tsup and changed up the tsconfig because I wasn't using your build and the tsconfig that came with it (there wasn't anything wrong with it, but) because I needed CJS compat in the package. tsup takes care of that nicely.
I always wanted to show off what I was doing with it on https://github.com/shellscape/jsx-email:

What do you think it would take to output an object for errors, warnings, and notes that more closely represented that visual structure; where for a single document, there was only one error (etc) message which pointed to an array of unique clients that are affected? I'm doing some reduce and Set shenanigans to make that happen as a consumer, but it would be cool for first class support.
Also saw your comment that you're not really using this anymore, so no worries if you don't want to put the time into it for the above - not at all expecting you to - but some direction on where to implement that would be cool if you're not into working on this again. I haven't looked at the source in depth yet, so pointers would be super helpful.
Thanks again!

haha it's been a while since i wrote this code, but it seems like you'd probably have to modify the methods in the DoIUseEmail class https://github.com/leondreamed/doiuse-email/blob/main/src/utils/doiuse.ts) to accept a specific email client as a parameter (right now they all either loop over this.emailClients or append to the errors/warnings array indiscriminately).
jsx-email looks super cool! i remember i created this package back when i was trying to write emails using code (i used something called maizzle) but writing emails in raw email-XML was just too painful so i ended up using SaaS email builders instead 😅)
i probably won't have time to do any major refactors or add new features to this package, so i'd be happy to transfer the repo and/or package name to you if you want :)
(also apologies in advance if the source code is messy!)

that would be amazing. thanks for being open to that, totally down for taking the reigns.

i've invited you to the npm package as a collaborator, but i think GitHub needs you to rename your existing fork for a repo transfer:

and honestly it's an honor to have one of my packages adopted by a legend in the open-source community 😉

no worries, just renamed it. and man, thanks for the compliments.

hm it seems like you might need to delete the fork altogether first:


Enable insertion of data into enum response text

for example, the bad request text can be:
"{url} is already taken".format(url="https://sce.sjsu.edu")

with my dad at the library


[do not merge] experiment oop codegen for all adapters

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: bianpengyuan
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bianpengyuan: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
e73c5311d2ae86e419d704aaca7cd508ee52e5bb
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
e73c5311d2ae86e419d704aaca7cd508ee52e5bb
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
e73c5311d2ae86e419d704aaca7cd508ee52e5bb
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
e73c5311d2ae86e419d704aaca7cd508ee52e5bb
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
e73c5311d2ae86e419d704aaca7cd508ee52e5bb
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
e73c5311d2ae86e419d704aaca7cd508ee52e5bb
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


File configuration is ignored

When a configuration is specified with the -c option, the settings loaded through the file are ignored as they are over written by the default options from the command lines.
Steps to re-create the issue:

create a configuration file with the option datasets.compute_file_hash: true
start the offline ingestor with -c option pointing the file above
after starting, the option datasets.compute_file_has is set to false

Expected behavior:
configuration options should use default value is not specified in configuration file. If the configuration file contains the option, the value provided there should be used.
If a user specify such option on the command line, the value user specified value is the one used.

To further elaborate, this is the precedence of values for each options:

User provided at command line
Configuration value
Default value

Fixed by #78


app_offline.htm file not being consistently removed by Kudu

We started noticing a couple weeks ago that occasionally the app_offline.htm file is not being removed at the end of the Kudu process.  This results in the site remaining offline with a 503 Site under construction error.
We mentioned it over at https://github.com/Azure/app-service-announcements/issues/137 and several other people chimed in they were seeing it as well.
The issue is not happening consistently, but it is happening fairly regularly for us (~20% of the time).  We've temporarily disabled auto-swap and are manually checking for the app_offline.htm file after a deploy, manually deleting it when present and proceeding with a swap.
Please let me know what information you would like for me to provide (the template didn't seem completely applicable) and thanks for any help you can offer!

@ahmelsayed, @suwatch, can we take a look at this? We also received a CRI about this and multiple customers have experienced it.

Count me as another customer affected by this.

We will investigate and update ..

Here is the code here and here creating and removing app-offline during deployment.   There should be a trace in the deployment log that we create and remove the app-offline file.    There is one condition where we may not remove the app_offline file if content has changed (which should be rare).
If you have the site repro in that state - we would like to have a look and get to the bottom.  If you don't really care about this app_offline (you can opt out by adding this appSettings).

Thanks for the response and code samples.  I'll be sure to report in when we next have a site actively in that state (Saturday morning now, but should be early next week).
I have considered avoiding the app_offline file altogether but it's big value is stopping the staging site to reduce file lock errors during deployment.  We still get those sometimes even with the app_offline present (perhaps graceful shutdowns are not completed first?) but I'm eager to learn more if there's a better suggestion for increasing consistency of the builds.

FWIW we haven't seen the issue this week, so we're going back to auto-swap for production.  I'd like to leave this issue open since others have seen it too in case anybody else can offer the request from suwatch to see a site that is actively in that state.  I'll certainly come back to report it when/if we next see the issue.

Hello there,
I am trying to deploy an angular app to azure and I am having difficulties with the app_offline.htm file as well. I feel like there is a little bit of magic going on here, can someone elaborate how app_offline fits into existing kudu-scripts, where is this declared and created?
The angular app I created resides here, as well as the kudu script: https://github.com/BigBubbus/beraterboard-test
How can I instruct Kudu to remove app_offline after deployment, I still go on and delete it manually.
Thanks for every tip here :)
Thomas

The app_offline creation and removal is part of KuduSync.Net.   It is supposedly removed after we are done with deploying bit to destination.   You can opt out by setting appSettings SCM_CREATE_APP_OFFLINE=0.
We are interested to see why it was left there.  Do provide us the UTC time of incident and webapp, we can help taking a look.   @ankitkumarr  for fyi.

We had this issue last night on our production instance.  Even after multiple deploys, it still would not remove w/o us manually removing the file.  Regrettably this put us in a severe outage for hours before technical teams thought to check for the file.  What can be done to find out why this didn't remove and prevent in the future?  Is someone actively looking into this issue?

A customer of mine has also encountered this issue. It took several days of a premier ticket to figure out the cause, but thankfully was in a pre-production environment. What is the resolution/status of this issue?

To help guide others here to the root cause
Evenlog.xml messages that appear over and over:
Global configuration changed. Change path: MACHINE/WEBROOT/APPHOST/, ApplicationManager: ####### [TID ####] [PID ####]
Recycling application MACHINE/WEBROOT/APPHOST/ [TID ####] [PID ####]
Change in global configuration [TID ####] [PID ####]
FREB Log message:
Module: AspNetInitializationExceptionModule, Notification: BEGIN_REQUEST, Status: 503, SubStatus: 0, HttpReason: Service Unavailable, Win32ErrorCode: 0x00000000, ConfigException:

We have experienced this as well with an automatic deployment from GitHub, just now.

I apologize that this still was an issue. Usually when this happens, it is likely that the deployment itself failed because we were unable to remove that app_offline.htm. But I understand that this leaves the app in the offline state without the user actually informed.
We have a work item to improve this experience. I will be taking a look at it next week. We will update this thread with an ETA.

@ankitkumarr Thank you for such a quick and helpful response :)

Are there any updates on this? This is causing major issues for us every time we deploy our .net core production site. We've tried deploying from VS for mac, VS for windows, and through Devops (including swapping slots) and every time we have this issue. MS support is recommending we set SCM_CREATE_APP_OFFLINE to 0. But as mentioned in the initial post here https://github.com/Azure/app-service-announcements/issues/137, this seems like it could have issues of its own? Also, we're having issues where changing an App Setting is causing the site to be temporarily unavailable. Is this related as well?

We're also seeing this issue.

I apologize for how long it took me to get back. We are starting to work on a fix to avoid such issues and this will be completed by the end of this month.
As Suwat mentioned above, the way kudu deployments work today is that before deployment we create an app_offline.htm to make sure you app becomes offline for any files that may need to be removed. Then, after deployment is complete (failure or success), it removes the app_offline.htm (with retries). If the file was not removed, it indicates that something else could have gone wrong. We saw a case previously where there was a storage fail-over. I would even argue that in some cases it may be the right thing to do to keep the app offline.
We will do our best to make this resilient and work on ways to ensure the file is always cleaned, but it would help to look at case by case on why this file was not removed in the first place. If you do see this issue, please share with us the app name and a time-frame so we can investigate.
Setting SCM_CREATE_APP_OFFLINE to 0 wouldn't have offline related issues. It means that kudu will not create the app_offline.htm. So, if your files have a lock on them such that they cannot be removed while the site up, the deployment may fail.

Me too, please fix soon.

@nicholastic, can you share you app name and the time period you saw the issue?

This is critical issue not solved for months !
There is no sense in adding app_offline file when making deployment to the slot which has 0% of traffic so there is no chance for files being locked.

@djsowa  Do consider  SCM_CREATE_APP_OFFLINE = 0 on staging slot - make it slot settings.

@suwatch Yes we are making this change with SCM_CREATE_APP_OFFLINE.
But my clients have more than 100 AppServices, each managed by Terraform.
This mean I have to make more than 100 pull requests :(

This just happened again on help-keyman.azurewebsites.net (I was notified at 2020-01-11T01:16:11.0610722Z) after a deployment started at 12:09:32 PM GMT+11 (which succeeded) (commit id 2b836a8).
I have manually removed app-offline.htm in order to make sure the site is available, but nothing else has currently changed on the site.
Nothing visible in the logs.

@ankitkumarr Is this fix released now? If so, in what version, or how can we check that we got the fix? Thanks!

Yes, the deployment was just completed today.

Closing as this is resolved and deployed. If you do see this again, please feel free to "@" me here, with necessary information (site name, timestamp) and we can take a look.

@ankitkumarr I am seeing this issue still on an Azure Functions app being deployed through ADO with the "Take app offline" box selected.
The Kudu version is currently 85.11226.4297.0.
Our setup is to deploy to a slot, then swap the slots.

@ankitkumarr This happened for me today. Azure App Service, fl-cc-am-beta.azurewebsites.net. Deployed through CI/CD for years at this point w/o issue. Last update on CI pipeline was 5/21/21, and the last release (ran as part of PR check) did fail w/ ERROR_FILE_IN_USE. Kudu build 94.30524.5227.0, so maybe this was left over when the deployment failed?


CIAB: Let auto-snapqueue and add-sslkeys be functions

What does this PR (Pull Request) do?

[x] This PR  is not related to any Issue

auto-snapqueue and add-sslkeys are good features and worth reusing.
This commit changes them into separate functions.
This PR doesn't change the CIAB usage so I didn't attach the document.
Which Traffic Control components are affected by this PR?

CDN in a Box

What is the best way to verify this PR?

Start CIAB
Check the snapshot can be automatically took
Check the demo site can be accessed via HTTPS protocol.

If this is a bug fix, what versions of Traffic Ops are affected?

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3495/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3497/
Test PASSed.

You know, looking at the auto snap/queue code I'm starting to wonder if maybe we're pushing the limits of what Bash should be doing. Every iteration parses these JSON responses seven times and I can't help but think how much cleaner this would be if we could parse those into objects immediately and iterate over them with for x in y instead of a while loop with condition checking

I can try to improve that.
However, do you mean we should use another method instead of continually improving this piece of bash code?

Yeah, I think maybe we're approaching a level of complexity that might be better handled by a Python script. Or a Perl script, I guess, but I think we're moving away from Perl as a project.

I think you are right and I have raised a discussion on slack.
I need more suggestion.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3557/
Test PASSed.


feat: add origin-shield

what

Add variables to enable the Origin Shield for the CloudFront distribution

why

Using Origin Shield can help reduce the load on your origin.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_distribution#origin_shield
Also implemented recently in other CF module: https://github.com/cloudposse/terraform-aws-cloudfront-cdn/pull/78

✅  Verified on my own stack that it works.
The automated tests however will likely only work once https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn/pull/208 has been merged since the AWS Provider is now explicitly checking for a value to be set for ssl_support_method.

/rebuild-readme

/test all

So @syphernl looks good, not requesting any changes but want to get @osterman and @Nuru's opinions on what I've identified.

@korenyoni I have changed the local into a var as @osterman suggested.

Thanks @syphernl —
@osterman please take another look. Deferring approval to you.

/test all

Hi @syphernl —
I've spoken to @Nuru who needs more time to be able to get a good look at this.

@korenyoni @Nuru Do you have any updates regarding this? Our project development is nearing completion and we'd like to enable the Origin Shield for this soon.

At the moment it's in @Nuru 's hands.
From @Nuru :

I had to put this on hold because of the AWS 4.0 upgrade.

I implemented the non-breaking-change portion of this in #247


Typo in filename 'apimmanagement.json'

apimmanagement.json has two m.

It brakes my scripts, can you please fix it?

Can you please fix this super simple issue?
It severely blocks my project.

Closing this since File name is fixed.


Changing Playback Rate

Does the player support different playback rates? thx

No, sadly this is out of scope of the current Player.js spec.


Json to midi

Hi, I was searching in your documentation and tests, however I could not find feature I am interested in.
Is it currently possible to generate midi file from json, that was created via MidiConvert?
My use-case is :

translating regualar midi file into JSON via MidiConvert,
tweaking json in some text editor,
translating it back to midi

Did you look at .encode()?  Based on both the README and the unit tests, it looks like that does what you want it to do.

It is almost, what I am looking for, but not exactly. encode() method allows me to transform MidiConvert object (that is created for example by using MidiConvert.create()) into midi file that can be started in media player.
What I am missing, is feature, that would allow me to transform json into MidiConvert object (deserialize it in other words).

Ahhh.  I don't see a fromJSON(), but I bet you could open a PR for one.
Or, if something quick and dirty is more your style, maybe something like this?
const midi = new Midi()
const encoded = midi.encode.apply(myJSON);
midi.decode(encoded)

It would roundtrip through the encoder, which is a bit wasteful, but it would get you the object you wanted.  Alternatively, I'd copy decode, name it static fromJSON, and modify it to parse a JSON object rather than a string.

I'll try with pull request :)

This can close now.

How do i use fromJSON() fx to get the midi file i mean how to get the midi file.
Say for example i put the json as input and call fromjson(myjson) then where is the midi file actually?


How can i set the color of a single node without relying on d3 themes?

What is your scenario?

Hello David, I have a similar question.
I would like to pass a color for a given node given the value of the size or another parameter. It seems that the colorTheme is only supporting d3 themes right now?

This can now be done with get-category-for-color, so the issue can be closed.

Use get-category-for-color


make all noise related classes serializable so we don't have anything hardcoded

this will be pretty difficult but definitely worth it

this mostly means using direct Modules instead of ModuleTypes

I want to know if this will release a fabric version :0

completed in upcoming release


Add "Touche" style check for overlapping glyph pairs

Observed behaviour
We should have a check that detects problems like https://github.com/thundernixon/Encode-Sans/issues/6
Expected behaviour
https://github.com/ninastoessinger/Touche is a libre robofont extension which checks defcon font objects for such collisions, and may inform a FB check that does the same to ttFonts.

That would be pretty neat indeed 👍


Improve Icon Rendering on HL2/VR devices.

Describe the problem
Related to https://github.com/provencher/MRTK-Quest/issues/64#issuecomment-655584078
Icon rendering is noticeably blurry on VR devices Hololens 2 (slightly less so for the latter).

Describe the solution you'd like
To address this improving the default icon shader with supersampling has been suggested
https://medium.com/@bgolus/sharper-mipmapping-using-shader-based-supersampling-ed7aadb47bec
The plan is to add make modifications to the MRTK Standard Shader to super sample the mip maps and provide much sharper icon rendering. We'll be making this improvement toggleable on the shader level so users can choose to enable or disable this improvement. Note that there are performance concerns for hololens 1, so we need to take the impact on those users into consideration and need to either not enable this by default or have a way to configure settings based on deploying to Hololens 1 vs HL2/VR devices.
Describe alternatives you've considered
We've considered creating a new shader with these improvements, though this approach would create further confusion for users for the "right way" to render icons with MRTK, so we'll be making these improvements to the default shader instead and making it toggleable.

Added GIF image captured by @vaoliva
@Cameron-Micka for visibility

I believe this issue was also described on https://github.com/microsoft/MixedRealityToolkit-Unity/issues/7941


Question regrading a layout

Hi can you please help me out i would like to create this layout using ng2-rickshaw http://energia.ningunaparte.net/en/ the main real time chart
Thanks

@daominhsangvn


Separate dialog form and dialog item component

@anandaprabawa I wil hide that, that's icon from combobox on vuetify


How do I listen to controlled-side audio

How do I listen to controlled-side audio

Duplicate of https://github.com/quasar/Quasar/issues/135


Add coverage file path options

Adds the option to pass the JSON report file and bypass running the tests again.
In my case I store the report from every test run as an artifact and then retrieve it when generating coverage with this action. The existing report doesn't always exist, but when it does it reduces the runtime significantly.

@all-contributors please add @jgillick for code, docs

@jgillick do you have an example of storing the artifact in a run?


[Feature] Add ability to specify [hash] in swDest

Welcome! Please use this template for reporting bugs or requesting features. For questions about using Workbox, the best place to ask is Stack Overflow, tagged with [workbox]: https://stackoverflow.com/questions/ask?tags=workbox
Library Affected:
workbox-webpack
Browser & Platform:
"all browsers".
Issue or Feature Request Description:
I need the ability to specify [hash] in the swDest field. Something like this:
plugins: [
  new WorkboxPlugin.GenerateSW({
    swDest: 'sw.[hash].js',
  })
]

We typically recommend developers do not version their service worker, and I think adding this feature would lead to confusion around that recommendation:
https://developers.google.com/web/fundamentals/primers/service-workers/lifecycle#avoid-url-change
Can you read the section in the link I've included and let me know if you still think this would be a good feature?

I'm pretty sure that, for the reasons linked to above, we don't want to support including hashes in swDest.


testing alternate cypress version

What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes #
Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on iOS/Android device (e.g, No crashes, library supported etc.)
[ ] No console errors on web
[ ] Tested on Light mode and Dark mode*
[ ] Your UI implementation visually matched the rendered design*
[ ] Unit tests*
[ ] Added e2e tests*
[ ] Added translations*

Codecov Report

Merging #3992 (8fc2376) into main (5a1537f) will decrease coverage by 40.12%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #3992       +/-   ##
===========================================
- Coverage   56.48%   16.36%   -40.12%
===========================================
  Files         411      448       +37
  Lines       11517    12172      +655
  Branches     3758     4060      +302
===========================================
- Hits         6505     1992     -4513
- Misses       4936    10140     +5204
+ Partials       76       40       -36

see 321 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add support for Google Nest Hub (1st Gen)

thanks for contributing.
How is this device identified by HA? You can check that in the device page, left top.
Also I see this device has a display, is this screen always on? And how does it affect the power consumption?

The device shows as "Google Nest Hub" under Device Info on HA, with Google Cast integration.
The screen was set to brightness 1 at the time of the recording, would you like me to rerun the test with brightness 10 as well?

Is brightness 10 the max? And is the screen always on?
I'm curious how it affects the power. As the profile the measure tool creates only looks at the volume level, it does not take any other factors into account.
And it would be a totally new case if we need to add support for that.

Is brightness 10 the max? And is the screen always on?
Brightness 10 is the max, yes, and also the screen is always on, but there is a night mode that only displays the time, however, I doubt this would affect anything.

You may add alias to model.json file to Google Nest Hub, that will also make auto discovery work correctly.

It doesn't seem that HA has support for adjusting the screen brightness, at least from what I can see.

Let me know if you know more about how the screen settings affect the power consumption.
When it does I think I have an idea how to integrate it.
We could create multiple sub profiles, and automatically select one when the brightness of the screen changes (when this information is available to HA of course).
See for example LIFX night vision lights, which select another profile depending on the infrared setting. https://github.com/bramstroker/homeassistant-powercalc/tree/master/custom_components/powercalc/data/lifx/LIFX BR30 Night Vision
Selection algorithm is specified in model.json file.

It doesn't seem that HA has support for adjusting the screen brightness, at least from what I can see.

Oh that's a pitty. Does it know the screen brightness, or is this information also not exposed to HA?

Oh that's a pitty. Does it know the screen brightness, or is this information also not exposed to HA?

Doesn't appear to be exposed at all, only volume levels, as it's classified as a media player.

Ok, could you check the power consumption on different display brightness levels first? Then we can see what we can do from there on.

Brightness 1: https://bin.harryw.link/obojimatan.json
Brightness 5: https://bin.harryw.link/ihiporanaq.json
Brightness 10: https://bin.harryw.link/vemeviqeko.json

As we can see and I already expected the power usage increases "significantly" as the brightness increases.
We could supply multiple profiles for the different brightness levels. Maybe 3 as you have now, or 10 for every brightness level.
Then we can show the user a selection during configuration where he/she can choose the correct profile. There are already some other lights which also have a similar sub profile selection.
However there are 2 problems with this approach, which cannot be solved.

When the user changes the brightness level later on, the powercalc sensor will still be calculated with the brightness level which was choosen during setup.
We cannot handle night mode, and I also see there is an auto brightness mode depending on ambient lighting.

So I don't think it is feasible to include a power profile for this nest hub in the powercalc library and I'll need to have to close this PR.
When you want to use the profile you created in your installation you can just put the files in: config/powercalc-custom-models directory.


partition-manager: 22.12.1 -> 23.04.1

Description of changes
You could argue we should split this into 2 commits, but as both pm and kpmcore need to be updated in lockstep, there's no harm doing it this way.
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

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

[X] Fits CONTRIBUTING.md.

Supersedes: #228756


⚠ Bofrost.be has degraded performance

In 1950b38, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1416 ms

Resolved: Bofrost.be performance has improved in edd3ea1.


Codegen tasks

Tasks

[ ]  Communicate with CTL team about extracting CTL plutus-ledger-api types from CTL and into a separate library where we manage JSON/PlutusData/Eq (Otherwise we need to pull in the entire CTL -.-)
[x]  Deep dive into Haskell plutus-ledger-api and check what built in encodings we must reuse (PlutusData ofc, but JSON? Perhaps we need to write a JSON library for them),
[x] Plutarch type def generation from LB type defs, and how to implement Eq and PlutusData for these Plutarch types,
[x] Formulate a non-Plutus standard library of opaques, what goes in (numbers, text, string, list, arrays, set/maps etc)? Collect target types in target languages (Purescript, Haskell, Typescript and Rust in that order of priority)

Stale


allow renting dedicated nodes if they're on standby status

allow renting dedicated nodes if they're on standby status if not done already
the goal for threefold, is to run a farm full of nodes power managed by farmerbot and be in power target off (managed by the farmerbot), and the farmerbot is supposed to bring these nodes online if they got rented (we need to make sure the are immediately usable for the user "before billing them" otherwise the user will be abused

allow renting dedicated nodes if they're on standby status if not done already

Contracts (rent/node) cannot be created on nodes that have power state Down
Power state Down: When a node actually is going to sleep because of the changed power target (requested by farmer bot), it will set it's power state to down on chain by calling change_power_state(PowerState(Up/Down)).
Node contract creation:
https://github.com/threefoldtech/tfchain/blob/36c891c02a1758a6bd6769357fdef230886940ff/substrate-node/pallets/pallet-smart-contract/src/grid_contract.rs#L31
Rent contract creation:
https://github.com/threefoldtech/tfchain/blob/36c891c02a1758a6bd6769357fdef230886940ff/substrate-node/pallets/pallet-smart-contract/src/grid_contract.rs#L127

we need to make sure the are immediately usable for the user "before billing them"

What is your suggestion here?

From TFChain perspective and according to @LeeSmet inputs here https://github.com/threefoldtech/tfchain/issues/873#issuecomment-1752932934 about how it was designed, it is all working as expected regarding rent contracts, assuming that this is client responsibility to cancel contract if node is down.
Now the question is do we want to change the design and remove this rule?

@renauter the is to have e.g 100 nodes in my farm available for renting, problem is the will cost too much power if they don't get rented right away. What I'm suggesting is allowing that to increase the ready/available capacity and save the power bill. I believe this should be relaxed (removing the condition) to allow the renting and maintain the power saving.
The farmerbot is responsible start waking it up within 5 minutes (checking interval)

The original design of this was that only nodes which are online can be rented. The user needs to contact the farmer bot so that the node to be rented can be brought online, after which the corresponding chain calls are done by the user.

the farmerbot is supposed to bring these nodes online if they got rented (we need to make sure the are immediately usable for the user "before billing them" otherwise the user will be abused

This was a major reason to do things like this, since a "standby" node might not actually be standby. The user will have reserved a node, which is then paid for, even though said node might not come online at all. Additionally, even if it comes online, this might take a significant time which needs proper consideration in the UX

OK
So what we suggest in terms of implementation to fulfill the issue is:

Removing the node_power.is_down() condition when trying to create a rent contract here:
https://github.com/threefoldtech/tfchain/blob/36c891c02a1758a6bd6769357fdef230886940ff/substrate-node/pallets/pallet-smart-contract/src/grid_contract.rs#L127

Modifying rent contract billing logic by discarding billing if the node PowerState is Down (which mean it is not wake up), adding some condition here:
https://github.com/threefoldtech/tfchain/blob/8dfb941263450b62c2b4eb5e3d51bc9f18ba9966/substrate-node/pallets/pallet-smart-contract/src/billing.rs#L59

Are we OK with that ?

Update:
The elapsed time for billing a contract is calculated using the last contract lock timestamp as initial time (see here) and this timestamp is only updated thanks to a previous call to  bill_contract(). Now, when the node is in standby mode bill_contract() is not called and by consequence the timestamp not updated so we are still billing for standby period (even if delayed).
To fix this situation, an extra contract lock timestamp update was added outside of bill_contract()  when node is first detected to be in standby mode. See the following commit https://github.com/threefoldtech/tfchain/pull/933/commits/aaa70653c2d3f12db99a2825715cefb213103568 and read the related test to better understand the case.
Even if not the most elegant way I don't see better at the moment and any suggestion is welcome.

Update:
Strategy was changed because the one above was not satisfying. A loose pallet coupling (see doc here ) was used between pallet-smart-contract and pallet-tfgrid to be able to use pallet-smart-contract logic inside pallet-tfgrid. See the following commit https://github.com/threefoldtech/tfchain/pull/933/commits/86bd2b5077f9c391e91c7601a10745ef8b31bab4 for better understanding.

These PRs will be merged soon, thanks for @renauter , It is related to power saving feature and the farmer bot so better to have a look @xmonader @rawdaGastan and make sure that the new behavior will be in sync ..

https://github.com/threefoldtech/tfchain/pull/933
https://github.com/threefoldtech/tfchain/pull/934

To summarize the incoming changes in behavior:

The chain will now verify if a node has active node/rent contracts before switching the target to down. If there are active contracts, a NodeHasActiveContracts error will be returned. Previously, the target was changed without chain-side verification.
Creation of Rent contracts will be allowed for standby nodes (any client-side restrictions should be adjusted accordingly). However, Node contracts will retain their old behavior and return the same error as before.
Billing for rent contracts will be skipped when nodes are in standby mode, and will be based on a timestamp that is updated only when the node status changes back to up. If a user decides to cancel the rent contract before the node power status change back to up (for example, if the node doesn’t come up), he won’t be charged anything.

Some concerns:
This satisfies the requirements mentioned in the issue to protect the user. However, what if a user decides to spam a farmer with renting their nodes and canceling it immediately afterward? will farmer bot put the nodes in standby again? is that enough? should we restrict the cancellation of rent contracts till a specific block count passed or it would complicate things unnecessarily?

Devnet, a4a560c.
I don't think this is solved; I got a standby node with ID 155 on farm 4420.
It has no contracts, is on standby, and is rentable, as you can see below.

But I still can't rent it.

@A-Harby you can use the clients to rent this node. For the dashboard, there is an issue to allow that https://github.com/threefoldtech/tfgrid-sdk-ts/issues/2143

Verified,
On grid client rent script.


Currying of higher order components is broken in 2.0.0

import {branch} from 'baobab-react/higher-order'
import React, {Component} from 'react'

class MyComponent {}
branch({})(MyComponent)

// Will throw an error:
// baobab-react/higher-order.branch: given target is not a valid React component.

My .babelrc looks like this:
{
  "presets": ["es2015", "stage-0", "react"],
  "plugins": [
    "add-module-exports",
    "syntax-trailing-function-commas",
    "transform-decorators-legacy"
  ]
}

I monkey patched it like this for now using lodash:
import higherOrder from 'baobab-react/higher-order'
import {curry} from 'lodash'
higherOrder.root = curry(higherOrder.root, 2)
higherOrder.branch = curry(higherOrder.branch, 2)

On another note, you might also consider:

Exporting the uncurried versions of branch and root
Exporting the internal utility library

Hello @demux. Which version of React do you use? If I remember correctly, on the latest one, if your component's class doesn't extend React.Component then the component is deemed invalid. But there can also be a bug with the lib's currying utility.

Exporting the uncurried versions of branch and root

What is the benefit from doing this?

Exporting the internal utility library

The internal utility library only has a curry function really.


Support javascript/CSS extensions in the HTML export

JupyterBook/sphinx makes it easy to extend the HTML export by providing javascript and CSS files that should be loaded in the HTML files: if a javascript file foo.js is dropped in the _static directory, then it's automatically added to the export directory, and a <script> tag is added all generated html files to load it. Same for a CSS file.
Proposal

Provide any equivalent mechanism.
(bonus) provide the exact same mechanism to easy transition.

Use case
In my course notes, I am using a custom js/css extension that adds two sliders in the top bar to choose whether to display solutions and/or instructor notes which is much more convenient than having separate versions of the documents.
Being able to quickly hack such extensions empowers users to explore features they would want to have, until they become official features.
@choldgraf: maybe this issue could be added to #189?

Do you think this is a duplicate of these two issues @nthiery ?

https://github.com/jupyter-book/myst-theme/issues/321
https://github.com/jupyter-book/myst-theme/issues/437

Oh, yes; thanks @choldgraf ! And I had even commented on those. Apparently I have a very short memory, and I failed my searches before creating a new issue :-) Sorry for the noise.
This issue can be closed, up maybe to a tiny action: mentioning  in the above issues, and as source of inspiration, the sphinx approach
of simply throwing the css/js files in _static.

Closing for:

https://github.com/jupyter-book/myst-theme/issues/437


Error with fp2e game system saving throw buttons

Hi, I have found a possible bug with Chat Reactions 2.2.0 on PF2 Game System 4.6.8 on Foundry 10.291: it seems to be breaking the saving throw button links in chat cards.
I can push-to-chat the buttons from the character sheet, but nothing happens when the player clicks the button, nor for me as game master. I also can't push-to-chat from another card in the chat (eg. the card describing the effect triggering the saving throw). This is true even with Chat Reactions (and sockelib) as the only modules activated. Deactivating Chat Reactions fixes the issue.

Screenshot of the kind of 'saving throw button' I'm talking about. Normally in the pf2e system if you put one of these in the chat, players can click on the button to auto-roll the relevant saving throw, with the roll compared to the set DC and the results announced in a chat card.
Happy to chat via discord if you want to troubleshoot - juswhe#8234

I couldn't reproduce the issue using the latest version of PF2 Game System, so updating the system may solve it.


Fixing #4437, Fixing #4439, Fixing #4440

Fixing #4437
Incorrect feature enablement snippet:
See: https://github.com/microsoft/winget-cli/blob/master/doc/Settings.md#configuration

@KevinLaMS
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Upgrade to Ubuntu 16.04 LTS

Upgrading to Xenial helps when I install the latest version of MySQL to the runner.
I'm opening PR to this fork because I think original repository does not really actively receive PRs.

Tested and approved.

The v1.7.0-4 is already building from docker hub.