Crash when initiating screen share using either zoom or OBS

When attempting to screen share using both zoom and OBS I correctly get a prompt for selecting a monitor output but when clicking on any of the outputs hyprland crashes.
Crash log for zoom (click to expand)
--------------------------------------------
   Hyprland Crash Report
--------------------------------------------
Maybe you should try dusting your PC in the meantime?

Hyprland received signal 6 (Aborted)

Version: 51a930f802c71a0e67f05e7b176ded74e8e95f87

Hyprland seems to be running with plugins. This crash might not be Hyprland's fault.
Plugins:
	hy3 (outfoxxed) 0.1

System info:
	System name: Linux
	Node name: <redacted>
	Release: 6.1.33-1-lts
	Version: #1 SMP PREEMPT_DYNAMIC Fri, 09 Jun 2023 10:50:53 +0000

GPU:
	0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 GL-XL [Radeon PRO W6800] [1002:73a3] (prog-if 00 [VGA controller])

os-release:
	NAME="Arch Linux"
	PRETTY_NAME="Arch Linux"
	ID=arch
	BUILD_ID=rolling
	ANSI_COLOR="38;2;23;147;209"
	HOME_URL="https://archlinux.org/"
	DOCUMENTATION_URL="https://wiki.archlinux.org/"
	SUPPORT_URL="https://bbs.archlinux.org/"
	BUG_REPORT_URL="https://bugs.archlinux.org/"
	PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
	LOGO=archlinux-logo

Backtrace:
	#0 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x450) [0x561d61085b90]
		??
		??:0
	#1 | Hyprland(_Z25handleUnrecoverableSignali+0x47) [0x561d6101ed07]
		??
		??:0
	#2 | /usr/lib/libc.so.6(+0x39ab0) [0x7f219402aab0]
		??
		??:0
	#3 | /usr/lib/libc.so.6(+0x8926c) [0x7f219407a26c]
		??
		??:0
	#4 | /usr/lib/libc.so.6(gsignal+0x18) [0x7f219402aa08]
		??
		??:0
	#5 | /usr/lib/libc.so.6(abort+0xd7) [0x7f2194013538]
		??
		??:0
	#6 | /usr/lib/libstdc++.so.6(+0xdd3b2) [0x7f21942dd3b2]
		??
		??:0
	#7 | Hyprland(+0x162e28) [0x561d610f7e28]
		??
		??:0
	#8 | Hyprland(_ZN26CScreencopyProtocolManager10shareFrameEP16SScreencopyFrame+0x73) [0x561d610f6be3]
		??
		??:0
	#9 | Hyprland(_ZN26CScreencopyProtocolManager14shareAllFramesEP8CMonitorb+0x83) [0x561d610f6cd3]
		??
		??:0
	#10 | Hyprland(_ZN6Events22listener_monitorCommitEPvS0_+0x2c) [0x561d610984dc]
		??
		??:0
	#11 | Hyprland(_Z13handleWrappedP11wl_listenerPv+0x40) [0x561d610a8db0]
		??
		??:0
	#12 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f21948fa01e]
		??
		??:0
	#13 | /usr/lib/libwlroots.so.12032(wlr_output_commit_state+0x314) [0x7f21949ac084]
		??
		??:0
	#14 | /usr/lib/libwlroots.so.12032(wlr_output_commit+0xd8) [0x7f21949ac358]
		??
		??:0
	#15 | Hyprland(_ZN13CHyprRenderer13renderMonitorEP8CMonitor+0xdec) [0x561d6110d39c]
		??
		??:0
	#16 | Hyprland(_Z13handleWrappedP11wl_listenerPv+0x40) [0x561d610a8db0]
		??
		??:0
	#17 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f21948fa01e]
		??
		??:0
	#18 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch_idle+0x23) [0x7f21948fba23]
		??
		??:0
	#19 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch+0xfd) [0x7f21948fbb3d]
		??
		??:0
	#20 | /usr/lib/libwayland-server.so.0(wl_display_run+0x27) [0x7f21948fc2d7]
		??
		??:0
	#21 | Hyprland(main+0x4a7) [0x561d6100dc87]
		??
		??:0
	#22 | /usr/lib/libc.so.6(+0x23850) [0x7f2194014850]
		??
		??:0
	#23 | /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f219401490a]
		??
		??:0
	#24 | Hyprland(_start+0x25) [0x561d6101bd65]
		??
		??:0

Log tail:
[LOG] On closed window, new focused candidate is 561d63eb5e80
[LOG] Set keyboard focus to surface 561d63ed06f0, with window name: Zoom - Licensed Account
[LOG] Destroying the SubSurface tree of unmapped window 561d63ec4840
[LOG] Callback 561d63add578 -> 561d63add570, SurfaceTreeNode removed.
[LOG] Callback 561d63add5e0 -> 561d63add5d8, SurfaceTreeNode removed.
[LOG] Callback 561d63add510 -> 561d63add508, SurfaceTreeNode removed.
[LOG] SurfaceTree Node removed
[LOG] Callback 561d63ec4e80 -> 561d63ec4e78, Toplevel removed.
[LOG] Callback 561d63ec4e18 -> 561d63ec4e10, Toplevel removed.
[LOG] Callback 561d63ec4ee8 -> 561d63ec4ee0, Toplevel removed.
[LOG] Callback 561d63ec4fc0 -> 561d63ec4fb8, CWLSurface removed.
[LOG] CWLSurface 561d63ec4f90 called destroy()
[LOG] Callback 561d63ec4938 -> 561d63ec4930, CWindow removed.
[LOG] Window 561d63ec4840 destroyed, queueing. (class )
[LOG] Callback 561d63ec48d0 -> 561d63ec48c8, XDG Window removed.
[LOG] Callback 561d63ec49a0 -> 561d63ec4998, XDG Window removed.
[ERR] onWindowRemovedTiling node null?
[LOG] New XDG Surface created. (class: zoom)
[LOG] Registered signal for owner 561d63f3f800: 561d63ef9710 -> 561d63f3f868 (owner: XDG Window)
[LOG] Registered signal for owner 561d63f3f800: 561d63ef96e0 -> 561d63f3f938 (owner: XDG Window)
[LOG] Registered signal for owner 561d63f3f800: 561d63f41db0 -> 561d63f3fe18 (owner: Toplevel)
[LOG] Registered signal for owner 561d63f3f800: 561d63f41dc0 -> 561d63f3fe80 (owner: Toplevel)
[LOG] Registered signal for owner 561d63f3f800: 561d63f41dd0 -> 561d63f3fdb0 (owner: Toplevel)
[LOG] Registered signal for owner 561d63f3ff50: 561d63f37438 -> 561d63f3ff58 (owner: CWLSurface)
[LOG] CWLSurface 561d63f3ff50 called init()
[LOG] Registered signal for owner 561d63f3f800: 561d63ef9720 -> 561d63f3f8d0 (owner: CWindow)
[LOG] Searching for matching rules for zoom (title: as_toolbar)
[LOG] OPENINGON: 561d63eb74d0, Workspace: 7, Monitor: 0
[LOG] Set keyboard focus to surface 561d63f37150, with window name: as_toolbar
[LOG] Window got assigned a surfaceTreeNode 0
[LOG] Registered signal for owner 561d63f3f800: 561d63f37418 -> 561d63f3f800 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ec3470 -> 561d63f3f9a0 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ef9700 -> 561d63f3fad8 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ec3400 -> 561d63f3fc10 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ec3420 -> 561d63f3fba8 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ec3430 -> 561d63f3fb40 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ec3440 -> 561d63f3fc78 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63f3f800: 561d63ec3410 -> 561d63f3fa70 (owner: XDG Window Late)
[LOG] Registered signal for owner 561d63ed7500: 561d63f37428 -> 561d63ed7578 (owner: SurfaceTreeNode)
[LOG] Registered signal for owner 561d63ed7500: 561d63f37418 -> 561d63ed75e0 (owner: SurfaceTreeNode)
[LOG] Registered signal for owner 561d63ed7500: 561d63f37438 -> 561d63ed7648 (owner: SurfaceTreeNode)
[LOG] Creating a surfaceTree Root! (pWindow: 561d63f3f800)
[LOG] Map request dispatched, monitor DP-1, xywh: 6564.000000 2147.000000 1272.000000 695.000000
[LOG]  [hookSystem] New hook event registered: screencast
[LOG] Cleanup: destroyed a window
[LOG] Cleanup: destroyed a window
[LOG] Set keyboard focus to surface 561d63ed06f0, with window name: Zoom - Licensed Account
[LOG] Set keyboard focus to surface 561d63f37150, with window name: as_toolbar
[LOG] Hiding the cursor (timeout)
[LOG] Showing the cursor (timeout)

Crash log for OBS (click to expand)
--------------------------------------------
   Hyprland Crash Report
--------------------------------------------
Calm down, it was a misinput! MISINPUT!

Hyprland received signal 6 (Aborted)

Version: 51a930f802c71a0e67f05e7b176ded74e8e95f87

Hyprland seems to be running with plugins. This crash might not be Hyprland's fault.
Plugins:
	hy3 (outfoxxed) 0.1

System info:
	System name: Linux
	Node name: <redacted>
	Release: 6.1.33-1-lts
	Version: #1 SMP PREEMPT_DYNAMIC Fri, 09 Jun 2023 10:50:53 +0000

GPU:
	0d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 GL-XL [Radeon PRO W6800] [1002:73a3] (prog-if 00 [VGA controller])

os-release:
	NAME="Arch Linux"
	PRETTY_NAME="Arch Linux"
	ID=arch
	BUILD_ID=rolling
	ANSI_COLOR="38;2;23;147;209"
	HOME_URL="https://archlinux.org/"
	DOCUMENTATION_URL="https://wiki.archlinux.org/"
	SUPPORT_URL="https://bbs.archlinux.org/"
	BUG_REPORT_URL="https://bugs.archlinux.org/"
	PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
	LOGO=archlinux-logo

Backtrace:
	#0 | Hyprland(_ZN13CrashReporter18createAndSaveCrashEi+0x450) [0x559df3c16b90]
		??
		??:0
	#1 | Hyprland(_Z25handleUnrecoverableSignali+0x47) [0x559df3bafd07]
		??
		??:0
	#2 | /usr/lib/libc.so.6(+0x39ab0) [0x7f067544fab0]
		??
		??:0
	#3 | /usr/lib/libc.so.6(+0x8926c) [0x7f067549f26c]
		??
		??:0
	#4 | /usr/lib/libc.so.6(gsignal+0x18) [0x7f067544fa08]
		??
		??:0
	#5 | /usr/lib/libc.so.6(abort+0xd7) [0x7f0675438538]
		??
		??:0
	#6 | /usr/lib/libstdc++.so.6(+0xdd3b2) [0x7f06756dd3b2]
		??
		??:0
	#7 | Hyprland(+0x162e28) [0x559df3c88e28]
		??
		??:0
	#8 | Hyprland(_ZN26CScreencopyProtocolManager10shareFrameEP16SScreencopyFrame+0x73) [0x559df3c87be3]
		??
		??:0
	#9 | Hyprland(_ZN26CScreencopyProtocolManager14shareAllFramesEP8CMonitorb+0x83) [0x559df3c87cd3]
		??
		??:0
	#10 | Hyprland(_ZN6Events22listener_monitorCommitEPvS0_+0x2c) [0x559df3c294dc]
		??
		??:0
	#11 | Hyprland(_Z13handleWrappedP11wl_listenerPv+0x40) [0x559df3c39db0]
		??
		??:0
	#12 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f0675d6701e]
		??
		??:0
	#13 | /usr/lib/libwlroots.so.12032(wlr_output_commit_state+0x314) [0x7f0675e19084]
		??
		??:0
	#14 | /usr/lib/libwlroots.so.12032(wlr_output_commit+0xd8) [0x7f0675e19358]
		??
		??:0
	#15 | Hyprland(_ZN13CHyprRenderer13renderMonitorEP8CMonitor+0xdec) [0x559df3c9e39c]
		??
		??:0
	#16 | Hyprland(_Z13handleWrappedP11wl_listenerPv+0x40) [0x559df3c39db0]
		??
		??:0
	#17 | /usr/lib/libwayland-server.so.0(wl_signal_emit_mutable+0x7e) [0x7f0675d6701e]
		??
		??:0
	#18 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch_idle+0x23) [0x7f0675d68a23]
		??
		??:0
	#19 | /usr/lib/libwayland-server.so.0(wl_event_loop_dispatch+0xfd) [0x7f0675d68b3d]
		??
		??:0
	#20 | /usr/lib/libwayland-server.so.0(wl_display_run+0x27) [0x7f0675d692d7]
		??
		??:0
	#21 | Hyprland(main+0x4a7) [0x559df3b9ec87]
		??
		??:0
	#22 | /usr/lib/libc.so.6(+0x23850) [0x7f0675439850]
		??
		??:0
	#23 | /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f067543990a]
		??
		??:0
	#24 | Hyprland(_start+0x25) [0x559df3bacd65]
		??
		??:0

Log tail:
[LOG] Window got assigned a surfaceTreeNode 0
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96a48 -> 559df8cbeb80 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96c30 -> 559df8cbed20 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c90dc0 -> 559df8cbee58 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96bc0 -> 559df8cbef90 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96be0 -> 559df8cbef28 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96bf0 -> 559df8cbeec0 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96c00 -> 559df8cbeff8 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8cbeb80: 559df8c96bd0 -> 559df8cbedf0 (owner: XDG Window Late)
[LOG] Registered signal for owner 559df8bee2e0: 559df8c96a58 -> 559df8bee358 (owner: SurfaceTreeNode)
[LOG] Registered signal for owner 559df8bee2e0: 559df8c96a48 -> 559df8bee3c0 (owner: SurfaceTreeNode)
[LOG] Registered signal for owner 559df8bee2e0: 559df8c96a68 -> 559df8bee428 (owner: SurfaceTreeNode)
[LOG] Creating a surfaceTree Root! (pWindow: 559df8cbeb80)
[LOG] Map request dispatched, monitor DP-1, xywh: 6310.000000 2015.000000 500.000000 290.000000
[LOG] Set keyboard focus to surface 559df8bd56d0, with window name: Properties for 'Screen Capture (PipeWire)'
[LOG] Set keyboard focus to surface 559df8c96780, with window name: MainPicker
[LOG] Window 559df8cbeb80 unmapped (class hyprland-share-picker)
[LOG] Unregistered late callbacks XDG
[LOG] Callback 559df8cbeba8 -> 559df8cbeba0, XDG Window Late removed.
[LOG] Callback 559df8cbed48 -> 559df8cbed40, XDG Window Late removed.
[LOG] Callback 559df8cbee80 -> 559df8cbee78, XDG Window Late removed.
[LOG] Callback 559df8cbefb8 -> 559df8cbefb0, XDG Window Late removed.
[LOG] Callback 559df8cbef50 -> 559df8cbef48, XDG Window Late removed.
[LOG] Callback 559df8cbeee8 -> 559df8cbeee0, XDG Window Late removed.
[LOG] Callback 559df8cbf020 -> 559df8cbf018, XDG Window Late removed.
[LOG] Callback 559df8cbee18 -> 559df8cbee10, XDG Window Late removed.
[LOG] Framebuffer created, status 36053
[LOG] On closed window, new focused candidate is 559df8be6f00
[LOG] Set keyboard focus to surface 559df8bd56d0, with window name: Properties for 'Screen Capture (PipeWire)'
[LOG] Destroying the SubSurface tree of unmapped window 559df8cbeb80
[LOG] Callback 559df8bee3e8 -> 559df8bee3e0, SurfaceTreeNode removed.
[LOG] Callback 559df8bee450 -> 559df8bee448, SurfaceTreeNode removed.
[LOG] Callback 559df8bee380 -> 559df8bee378, SurfaceTreeNode removed.
[LOG] SurfaceTree Node removed
[LOG] Callback 559df8cbf1c0 -> 559df8cbf1b8, Toplevel removed.
[LOG] Callback 559df8cbf158 -> 559df8cbf150, Toplevel removed.
[LOG] Callback 559df8cbf228 -> 559df8cbf220, Toplevel removed.
[LOG] Callback 559df8cbf300 -> 559df8cbf2f8, CWLSurface removed.
[LOG] CWLSurface 559df8cbf2d0 called destroy()
[LOG] Callback 559df8cbec78 -> 559df8cbec70, CWindow removed.
[LOG] Window 559df8cbeb80 destroyed, queueing. (class )
[LOG] Callback 559df8cbec10 -> 559df8cbec08, XDG Window removed.
[LOG] Callback 559df8cbece0 -> 559df8cbecd8, XDG Window removed.
[LOG] Callback 559df8917e48 -> 559df8917e40, textInput removed.
[LOG] Callback 559df8917de0 -> 559df8917dd8, textInput removed.
[LOG] Callback 559df8917d78 -> 559df8917d70, textInput removed.
[LOG] Callback 559df8917d10 -> 559df8917d08, textInput removed.
[LOG] Cleanup: destroyed a window
[LOG] Set keyboard focus to surface 559df89274f0, with window name: OBS 29.1.1-2 - Profile: Untitled - Scenes: Untitled
[LOG] Set keyboard focus to surface 559df6c77100, with window name: Hyprland Desktop Portal | Hyprland Wiki - wiki.hyprland.org/ — Mozilla Firefox

I will try again shortly without h3y loaded.  The layout is not in use but I forgot to remove the plugin loading line.

patch.txt
try this patch. hy3 is not at fault

Thanks!  So I think I should have tried the git package first.  I attempted to apply the patch to the stable version by modifying this PKGBUILD.  That had no impact.
Then I used the git PKGBUILD and modified that to apply the patch as well and that worked.  However for completeness I also went back and installed the upatched -git version and it also seems to work, so I think this is resolved in the most recent unreleased version anyway.
I did notice that when the crash occurs the xdg-desktop-portal-hyprland systemd service fails with:
Jun 13 11:14:39 <redacted> hyprland-share-picker[209104]: qt.accessibility.atspi: Error in contacting registry: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
Jun 13 11:14:48 <redacted> hyprland-share-picker[209938]: qt.accessibility.atspi: Error in contacting registry: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
Jun 13 11:15:08 <redacted> systemd[3142]: Starting Portal service (Hyprland implementation)...
Jun 13 11:15:08 <redacted> xdg-desktop-portal-hyprland[213558]: 2023/06/13 11:15:08 [ERROR] - wayland: failed to connect to display
Jun 13 11:15:08 <redacted> systemd[3142]: xdg-desktop-portal-hyprland.service: Main process exited, code=exited, status=1/FAILURE
Jun 13 11:15:08 <redacted> systemd[3142]: xdg-desktop-portal-hyprland.service: Failed with result 'exit-code'.
Jun 13 11:15:08 <redacted> systemd[3142]: Failed to start Portal service (Hyprland implementation).

Anyway I think it will be fine in the next release so maybe the patch is not required?
There's a lot of weirdness with the way zoom windows, and especially drop down menus, open get tiled.  I'll open another issue about that though I'm not sure there's much anyone can do about it.

zoom sucks in general both on x and wayland

patch applied in 7762ac0173b860af83e58d56409f9cf0fa7252e9

zoom sucks in general both on x and wayland

Yes, yes it does....
Just as a followup incase this is relevant in the future, I don't think the xdg-desktop-portal-hyprland errors are related to this crash.  They appear in the logs every time the share picker is shown.  I got a few more just now but no crash:
Jun 13 12:16:09 <redacted> hyprland-share-picker[96364]: qt.accessibility.atspi: Error in
 contacting registry: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus s
erver"
Jun 13 12:16:14 <redacted> hyprland-share-picker[97866]: qt.accessibility.atspi: Error in
 contacting registry: "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus s
erver"

Thanks for your help!


An attempt to achieve issue #34

I send different GET requests to different fake address responding to "message", "open", "close" events, etc.
README.md is slightly changed and the usage can be referred there.
I tried not to disturb the original API, but I had to turn off the feature that automatically closes the connection when no middlewares handling it.

Hi @roastduck,
First of all: I'm really sorry that it has taken me ages to get to this PR. Didn't mean to make you wait this long.
I really like this idea, but at the same time I feel a bit conflicted when it comes to merging these changes into the library. The way I see it there's no compelling reason to let this functionality be part of express-ws. In my opinion this could be implemented "on top of" express-ws, as a separate library. Without breaking the automatic closing of sockets.
Please don't get me wrong. I really want to see this functionality, and I know it would be useful for a lot of people. I just want us to have a look at alternative approaches before I merge this. Keeping the PR open for now.

Maybe we can simply leave it to users by adding an option deciding whether to enable the automatically closing feature. If a user wants to use the newly added API in this PR, and also use the automatically closing feature at the same time, he may need to create a fake listener for the original ws method by himself. I can't create the fake listener by default, because this would interfere with some possible true listener.

I realized that simply pass the request throw an empty middleware will mark it as handled, so we can call ws method with an empty middleware each time we call the newly added methods.

Hi @HenningM ,
So what's your idea about this pull request? After the commit above, now we don't have to break the auto-close feature. Are you going to merge this or let me set up a new repo?

Hi again @roastduck,
I'm terribly sorry it has taken me half a year to get back to you on this one. I really appreciate what you've done here, so I feel quite bad about not getting back to you sooner.
As I mentioned in my previous comment I think that this feature will be useful to a lot of express-ws users. But at the same time I still don't feel comfortable including it as part of this library. It simply falls outside of the scope I want this library to cover. In my mind this feature should still be implemented on top of express-ws, not within it. I'd gladly point people requesting this feature in the direction of your fork though, if you're interested in maintaining that. I might even include a link in the README.

Hi. If it was half a year ago, I would like to maintain it..., but currently I have no time. Just leaving this pull-request open is OK.


Fixes #405 : Modifies strings to have zulip standard capitalization scheme.

Summary of changes
Modifies the strings to zulip standard capitalization

[x] Code is formatted.

[x] Run the lint tests with ./gradlew lintDebug and make sure BUILD is SUCCESSFUL

[x] If new feature is implemeted then it is compatible with Night theme too.

[x] Commit messages are well-written.

@kunall17 Done! :)

Merged, thanks @saketkumar95 👍


Visualization using vanilla javascript

Fourier Series Visualization using vanilla JavaScript with options to customize output
see here: https://suhelmakkad.github.io/Fourier-Series-Visualization/

Community Contribution
Link to live project, video, or image:

Sharing

[x] I would be happy to have my project shared on The Coding Train's social media!

Instagram:
Twitter:

Thank you for this awesome contribution!


Why is 1GB file can destroy my 12GB colab RAM?

Why is the benchmark tss file is only 1G, but when I create api with fast_mode = False, it causes my notebook to crash because of out of memory?

I have tried what you said, however when I loop over the whole dataset it takes too long. For example, my function below would take almost 2 hours on google colab to run. Is that normal or it's just me?
def extract_data(api, dataset):
    # extract flops and test acc for dataset for all architectures
    data = np.zeros(shape = (len(api), 2))
    for i in trange(len(api)):
        flops = api.get_cost_info(i, dataset)['flops']
        test_error = 100 - api.get_more_info(i, dataset, hp = 200)['test-accuracy']
        data[i, 0], data[i, 1] = test_error, flops
    return data

By the way, did you mean create(None, 'tss', fast_mode=True) when using the archive tss?

Yes,, if you traverse all candidates, then the memory cost will be the same and due to the online nature, it will also be slower..
You may need a better machine to run the function. I tried on my personal mac for these functions, which are be completed by < 10 mins

Ok, thank you for answering my questions.


Bitonic Sort | C++

Bitonic Sort
what will change -
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code
[ ] Improving Code
[ ] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[ ] Python
[x] C++
[ ] Java
[ ] C
[ ] Go
[ ] Other language

Self Check

Ask for issue assignment before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Happy Coding,

Can I be assigned to this issue in C++ ?

Hi, I can implement this in a couple of hours, let me know if it is up for grabs.

Please assign it to me, i'll be doing it in Python and C.


Mobilenet bug

model = vis.image_classifier('pretrained_mobilenet', train_data, val_data)
Throws

NameError                                 Traceback (most recent call last)
 in
----> 1 model = vis.image_classifier('pretrained_mobilenet', train_data, val_data)
2 learner = ktrain.get_learner(model=model, train_data=train_data, val_data=val_data,
3                              workers=8, use_multiprocessing=True, batch_size=32)
/etc/conda/envs/ml/lib/python3.7/site-packages/ktrain/vision/models.py in image_classifier(name, train_data, val_data, freeze_layers, metric, optimizer_name, multilabel, multigpu_number, pt_fc, pt_ps, verbose)
193                                   activation=activation,
194                                   pt_fc = pt_fc,
--> 195                                   pt_ps = pt_ps)
196         model.compile(optimizer=optimizer_name, loss=loss_func, metrics=[metric])
197         return model
/etc/conda/envs/ml/lib/python3.7/site-packages/ktrain/vision/models.py in build_visionmodel(name, num_classes, input_shape, freeze_layers, activation, pt_fc, pt_ps)
212                                   activation=activation,
213                                   pt_fc = pt_fc,
--> 214                                   pt_ps = pt_ps)
215     elif name == CNN:
216         model = build_cnn(num_classes,
/etc/conda/envs/ml/lib/python3.7/site-packages/ktrain/vision/models.py in build_predefined(name, num_classes, input_shape, freeze_layers, activation, pt_fc, pt_ps)
301                            input_shape = input_shape)
302     elif name in [MOBILENET, PRETRAINED_MOBILENET]:
--> 303         net = MobileNet(include_top=include_top,
304                         weights=weights,
305                         input_tensor=input_tensor,
NameError: name 'MobileNet' is not defined

I'm using tensorflow-gpu==2.1.0 with ktrain==0.14.4

Thanks for letting me know.  This is now fixed in v0.14.5.  Here is an example notebook that uses MobileNet.


Wrong package name at the installation instructions

Hi.
The package name on README.MD at the installation instructions is insomnia-plugin-theme-catppuccin, but the package name of Insominia Plugin Hub is insomnia-plugin-catppuccin
Trying to install with insomnia-plugin-theme-catppuccin throws an error.
Error: Error invoking remote method 'installPlugin': Error: Yarn error warning<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

    at o.invoke (node:electron/js2c/renderer_init:57:526)
    at async BP._handleAddFromNpm (file:///opt/Insomnia/resources/app.asar/index.e0c63af2.js:1849:44230)

Installing with insomnia-plugin-catppuccin works fine.

The issue has been fixed with the PR above, let us know if you still find something unexpected, Thanks!


Background Fix

Fixes

Fixed my attempt at having a black background by adding "ax.set_facecolor("black")" changing the facecolor (background) to black

Changes

Changed the edgecolor on the CONUS Shapefile to White to better contrast with the new background

Disregard the first Commit "Development" it wouldn't remove...


Shortcut icon for ZIP/ISO shows as folder

Fixed https://github.com/DustinBrett/daedalOS/commit/5bac2dd6236dfb13849e6468599ed653c69b81b8


MINOR: Fix bugs identified by compiler warnings

Add missing string interpolation
Fix and simplify testElectPreferredLeaders
Remove unused code
Replace deprecated usage of JUnit assertThat
Change var to val and fix non-exhaustive pattern match
Fix eta warning
Simplify code
Remove commented out code

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@junrao I pushed a fix for the failing test and minor tweaks. Let me know if this looks good to you.

Merged to trunk and cherry-picked to 2.2.


⚠ Thumbnails API Endpoint has degraded performance

In c6419c5, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1543 ms

Resolved: Thumbnails API Endpoint performance has improved in 623457b.


Check if any of the security issues are blockers for the MVP, and document the remaining security issues

Hey team! Please add your planning poker estimate with Zenhub @arya2 @oxarbitrage @teor2345 @upbqdn

Here is my take on the security issues:

security: Files created by Zebra can be read by any user on the same machine #7807

Partially addressed by warning users not to use the experimental scanner on shared machines.
Server processes that run as other users and are exploited could still read the viewing keys. This is addressed by telling users to generate new keys for testing.

security: Run the scanner it is own tokio executor to avoid timing attacks #8043

This is addressed by telling users to generate new keys for testing.
There also isn't much of an oracle here, because we're launching blocking cryptographic tasks in their own tokio threads.

Store scanner viewing keys in a separate file, and give them more restrictive file permissions #8048

Same as "Files created by Zebra can be read by any user".

Add a wrapper around private key types, so we never print them in display or debug code

This is addressed by removing all known key writes to logs.
It is also addressed by telling users to generate new keys for testing.

Stop repeating the secret key in every database row, this makes it harder to securely delete from disk

Same as "Files created by Zebra can be read by any user".

Store the private key in the database as a salted hash, so it can't be read and re-used

Not needed yet.

@ZcashFoundation/zebra-team any other input on the security analysis for the MVP? Anything else to be done before we close this issue?

Can someone double-check that the changelog and scanning doc security warnings cover all these cases? And that the warnings are clear and easy to understand?
I think we're fine but it's good to check.
https://github.com/ZcashFoundation/zebra/blob/main/book/src/user/shielded-scan.md
https://github.com/ZcashFoundation/zebra/blob/main/CHANGELOG.md#zebra-150---2023-11-28
https://zfnd.org/zebra-1-5-0-release/

Can someone double-check that the changelog and scanning doc security warnings cover all these cases? And that the warnings are clear and easy to understand?

@oxarbitrage Can you please check this? ☝


What comes after the composer update instruction?

Hi folks,
Thank you so much for providing and maintaining this repository!
I am on the way to setup a test instance of this repository. This is what I did so far.

I imported the database dump into a MySQL DBMS.
I called composer update in the /MAIN folder.

What comes next to setup a test instance? I can not find any documentation.
Appreciate!

There are next steps for configuration documented in the Read.me that would follow the composer update. Do you need clarification on those steps?

There are next steps for configuration documented in the Read.me that would follow the composer update. Do you need clarification on those steps?

Dear @rdamashek ,
That is exactly the issue. There is a piece of information missing between Environment variables and Testing
How can you test this instance on /admin when you have not started the corresponding service and have no documentation telling you how to do that?

How can you test this instance on /admin when you have not started the corresponding service and have no documentation telling you how to do that?

I thought about a documentation telling me how to setup and bring a service instance online like this or that.

@rdamashek @dancesWithCycles , I've just pushed an update to the README file to provide more detailed explanations for the setting up the app and configurations, also  both the Administrator Console and User Panel functions are explained in the readme file. Please take a look and let me know if you come across any issues or have any further suggestions. Your feedback is greatly appreciated!

Dear @faai5200,
Thank you very much for your support.
What I now did is to call the following series of instruction on a virtual machine to deploy a test instance.

checkout source code

cd ~
mkdir oanm && cd oanm
git clone -b main https://github.com/rdamashek/Community-Through-Caring.git

build service

cd Community-Through-Caring/MAIN
composer update

config service

cd ~/oanm/Community-Through-Caring/MAIN
vi .env

config web server

cd ~/doms/oanm.coc.swingbe.de/
rm -rf subs/www
rm -rf subs-ssl/www
vim htdocs/.htaccess
rm -rf htdocs-ssl/
ln -s $HOME/oanm/Community-Through-Caring/MAIN htdocs-ssl

The virtual machine is running Debian 12.4, PHP 8.2.14 and Apache.
When I open this test service in a browser like Firefox or Chromium I get the following reply. Any idea what is causing those errors?
A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_URI::$config is deprecated

Filename: core/URI.php

Line Number: 102

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Router::$uri is deprecated

Filename: core/Router.php

Line Number: 128

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$benchmark is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$hooks is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$config is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$log is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$utf8 is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$uri is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$exceptions is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$router is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$output is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$security is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$input is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$lang is deprecated

Filename: core/Controller.php

Line Number: 83

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$db is deprecated

Filename: core/Loader.php

Line Number: 397

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_DB_mysqli_driver::$failover is deprecated

Filename: database/DB_driver.php

Line Number: 372

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 303

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 328

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 355

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 365

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 366

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 367

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 368

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 426

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 137

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property Welcome::$session is deprecated

Filename: core/Loader.php

Line Number: 1284

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 9
Function: __construct

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$load is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$benchmark is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$hooks is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$config is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$log is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$utf8 is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$uri is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$exceptions is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$router is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$output is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$security is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$input is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$lang is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$db is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A PHP Error was encountered
Severity: 8192

Message: Creation of dynamic property CI_Loader::$session is deprecated

Filename: core/Loader.php

Line Number: 932

Backtrace:

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/application/controllers/Welcome.php
Line: 41
Function: view

File: /home/pacs/sib00/users/coc_oanm/oanm/Community-Through-Caring/MAIN/index.php
Line: 287
Function: require_once

A Database Error Occurred
Error Number: 1146

Table 'sib00_coc.language' doesn't exist

SELECT * FROM `language` WHERE `lang_key` = 'lang_offers_and_needs'

Filename: helpers/common_helper.php

Line Number: 57

Hi folks,
Any news to this comment?
Cheers!

Stefan,Fakhar is now researching the issues you documented. Somehow he missed your post notification.Thanks,RobertOn Jan 11, 2024, at 8:30 AM, Stefan Begerad @.***> wrote:
Hi folks,
Any news to this comment?
Cheers!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Dear @dancesWithCycles ,
Thank you for your detailed report and for testing the Community Through Caring web app. I appreciate your dedication to making this open-source project better.
I have investigated the issue you encountered, and it appears that the error messages point to deprecated features in the CodeIgniter framework. The issue has been resolved in a recent update. You may check that out.
I appreciate your understanding and patience in resolving this issue. If you encounter any further difficulties or have additional questions, please feel free to reach out.
Best regards,
faai5200

Thank you, Fakhar, for tracking down and resolving these issues.
Robert
On Sun, Jan 21, 2024 at 5:44 PM Fakhar Zaman @.***>
wrote:

Dear @dancesWithCycles https://github.com/dancesWithCycles ,
Thank you for your detailed report and for testing the Community Through
Caring web app. I appreciate your dedication to making this open-source
project better.
I have investigated the issue you encountered, and it appears that the
error messages point to deprecated features in the CodeIgniter framework.
The issue has been resolved in a recent update. You may check that out.
I appreciate your understanding and patience in resolving this issue. If
you encounter any further difficulties or have additional questions, please
feel free to reach out.
Best regards,
faai5200
—
Reply to this email directly, view it on GitHub
https://github.com/rdamashek/Community-Through-Caring/issues/6#issuecomment-1902790956,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARD5XKUPK6ERTMYCRWABCLYPWK5PAVCNFSM6AAAAAA5YJR6AOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBSG44TAOJVGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Dear @faai5200 ,
Thank you very much for your update on this issue!

I appreciate your understanding and patience in resolving this issue. If you encounter any further difficulties or have additional questions, please feel free to reach out.

Is it possible that this database schema is not up to date?
On the same domain I followed my series of deployment instructions from above again and ended up with this message.
A Database Error Occurred
Error Number: 1146

Table 'sib00_coc.language' doesn't exist

SELECT * FROM `language` WHERE `lang_key` = 'lang_offers_and_needs'

Filename: helpers/common_helper.php

Line Number: 57

Cheers!

Hello @dancesWithCycles ,
Thank you for explaining the issue and for testing the Community Through Caring web app. I appreciate your dedication to making this open-source project better.
I have checked the issue in more details and seems like the issue was from the database side. I have made the required updates and pushed the code. You will need to reinstall the database  and complete the rest of installation process.
If you encounter any further difficulties or have additional questions, please feel free to reach out. Thank you for your patience and identifying the issues.
Best regards,
faai5200

Dear @faai5200 ,
Thank you so much for the update. It made me able to deploy a test instance.
Cheers!


ARTEMIS-4016 Bridges created by management operations are removed on …

…restart and config reload
@michaelandrepearce
This is from our discussion on Slack... hope it looks good.
If anything seems strange then it's probably incorrectly implemented, I should not have the benefit of the doubt on this one

@AntonRoskvist, apologies for letting this sit for so long. Nice work. Thanks for the contribution!


There was a problem while downloading the metadata for your box

$ vagrant up
Bringing machine 'core-01' up with 'virtualbox' provider...
==> core-01: Checking if box 'coreos-beta' is up to date...
==> core-01: There was a problem while downloading the metadata for your box
==> core-01: to check for updates. This is not an error, since it is usually due
==> core-01: to temporary network problems. This is just a warning. The problem
==> core-01: encountered was:
==> core-01:
==> core-01: Failed connect to beta.release.core-os.net:80; No error
==> core-01:
==> core-01: If you want to check for box updates, verify your network connection
==> core-01: is valid and try again.
==> core-01: VirtualBox VM is already running.

Moved to https://github.com/coreos/bugs/issues/1355


Fixed a bug with shift + space shortcut

It wouldn't correctly highlight a plugin in the structure board in case the plugin was in view of the structureboard.

Coverage increased (+0.02%) to 82.483% when pulling 40a401d6c78f7e06266f7c83bef29ece8a88804d on vxsx:bugfix/shift-space-structureboard-highlight into e8e1c868a2e7dcb5e64d5cdd109453660370524f on divio:release/3.4.x.


[WIP/Async] Wait for target block

This PR modifies the behaviour of transaction confirmations by making it so the filter is re-queried in case the target block is not reached (in case there is a reorg while waiting for blocks to be mined).
Now that I think about this more (after implementing it :facepalm:) - I think it should stay as is. The reason being if there is a reorg, then the transaction receipt might have been invalidated so its worth re-querying to re-calculate the remaining blocks that need to be waited for anyway (the transaction might even have moved up a block for example).
Just wanted to share the implementation in case you guys think this should be included - otherwise I think the PR should be closed and confirmations should be kept as is.

I added a (hopefully) better explanation to the other PR.

Closing this, see discussion https://github.com/gnosis/ethcontract-rs/pull/323#discussion_r430306987


Disable AAD validation for Custom environments

@rakku-ms  DO we need this PR still?

@rakku-ms  DO we need this PR still?

yes, merging this PR

yes, merging this PR


Not getting telegram notifications

I stopped getting notifications on my telegram, irrespective of the fact that i have correctly entered my chat ID as well as my bit access code.
If fact there is no error message in notification panel of the camera UI interface.

can you enable debug in your config and try again pls

https://github.com/seydx/homebridge-camera-ui/issues/491


NodeJs Support for SPFx 1.4.1 (SP 2019): reopened

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Server 2019 (on-premise)
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[X] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
No response
Issue description
This is a follow-up of my original question here: #7005
For a big SPFX change project in a customers SP 2019 environment (trying to replace existing WSP solutions with SPFX), we need an official idea about SPFX dependencies and the appropriate versions, in the current case especially Node.Js
As stated in the previous issue, I find several sources with all kinds of different information:
Source 1: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment
--> exception/dependency only mentioned for SP 2016, not SP 2019
Source 2: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/compatibility
--> this mentions Node.Js LTS 8 as the dependency for SPFX 1.4.1 (latest version on SharePoint Server 2019)
Source 3: https://docs.microsoft.com/en-us/learn/modules/sharepoint-spfx-get-started/5-exercise-setup-development-environment
--> "If you are building projects for SharePoint 2019 and/or SharePoint Online, then it is recommended that you install Node.js v10.x ..."
In the current customer project, Node.JS LTS 10 was also recommended for SP 2019 SPFX projects - the source for this recommendation is unknown, but projects built on this seem to work correctly.
One of the great PNP masters Andrew Connell already answered the question with Node.JS LTS 8 as the required version, but that would mean I would need to trigger a huge change process now to downgrade from 10 to 8 (it's distributed within a portable package including Git and VS Code for the developers).
I am unsure if the incompatibility is really severe and I am seeking help and recommendation if a downgrade will be really needed for future projects?

It definitely appears like we have some mismatching information across our development documentation. As Andrew mentioned, Node 8 LTS (or 6) are the recommended and only supported version of Node to use with SharePoint 2019 development. I personally, would recommend downgrading from V10 to V8 to maintain supportability.
With that being said, it sounds like you have a working solution with v10 LTS. You could continue using that at your own risk... but I personally, try to avoid it and stay within the recommended versions.

Hey Beau,
thanks for this recommendation and confirmation of Andrews feedback. This second opinion will give me enough for the customer conversation. KR


Why Multidimensional Arrays converted this way?

var circles = new Circle[]
{
  new Circle() { Center = new Point(0, 0), Radius = 1, data = new int [2, 3] { { 1, 2, 4 }, { 1, 2, 3 } } },
  new Circle() { Center = p, Radius = 2 },
  new Circle() { Center = p, Radius = 3 }
};

var json = JSON.ToNiceJSON(circles);
var data = JSON.ToObject<Circle[]>(json);

[
   {
      "Center" : {
         "X" : 0,
         "Y" : 0
      },
      "Radius" : 1,
      "data" : [
         1,
         2,
         4,
         1,
         2,
         3
      ]
   },
   {
      "Center" : {
         "X" : 0,
         "Y" : 1
      },
      "Radius" : 2,
      "data" : null
   },
   {
      "Center" : {
         "X" : 0,
         "Y" : 1
      },
      "Radius" : 3,
      "data" : null
   }
]

After the reverse transformation, data = int [6], but need int [2, 3].

Probably a problem with serializing multi-dimensional arrays... I will look into it, thanks!

The IEnumerable just goes though the list regardless, I have to use the Rank property.
How is the following as an output :
"data" : [ [1,2,4] , [1,2,3] ],


Dependabot couldn't fetch path-based dependencies (pip)

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pip
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
/requirements.txt
/config/pyproject.toml
/config/db-requirements.txt
dependabot.yml content
https://github.com/solaluset/DandelionMusic/blob/master/.github/dependabot.yml
Updated dependency
No response
What you expected to see, versus what you actually saw
I expected dependabot to update dependencies in all manifests, but it only updates /requirements.txt
It also gives error: Dependabot couldn't fetch all your path-based dependencies The affected dependencies were "./config" at /requirements.txt.
It also says: "To use path-based dependencies with Dependabot the paths must be relative, resolve to a directory in this project's source code, and contain a valid Python project."
If I'm not mistaken, all the conditions listed above are met.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
proxy | 2024/04/15 21:59:16 proxy starting, commit: cf8623577dad71c128f219df2b27df6de35b909d
proxy | 2024/04/15 21:59:16 Listening (:1080)
updater | 2024-04-15T21:59:16.577637312 [815138141:main:WARN:src/devices/src/legacy/serial.rs:222] Detached the serial input due to peer close/error.
updater | time="2024-04-15T21:59:19Z" level=info msg="guest starting" commit=23d5de4e561c0902c1073f9798c09b5fb9912de9
updater | time="2024-04-15T21:59:19Z" level=info msg="starting job..." fetcher_timeout=10m0s job_id=815138141 updater_timeout=45m0s updater_version=837078853fa8c5ba937e2f2432d7cac7318a20f5-pip
updater | 2024/04/15 21:59:22 INFO <job_815138141> Starting job processing
updater | 2024/04/15 21:59:22 INFO <job_815138141> Job definition: {"job":{"allowed-updates":[{"dependency-type":"direct","update-type":"all"}],"commit-message-options":{"include-scope":null,"prefix":null,"prefix-development":null},"credentials-metadata":[{"host":"github.com","type":"git_source"}],"debug":null,"dependencies":null,"dependency-group-to-refresh":null,"dependency-groups":[],"existing-group-pull-requests":[],"existing-pull-requests":[],"experiments":{"proxy-cached":true,"record-ecosystem-versions":true,"record-update-job-unknown-error":true},"ignore-conditions":[],"lockfile-only":false,"max-updater-run-time":2700,"package-manager":"pip","proxy-log-response-body-on-auth-failure":true,"reject-external-code":false,"repo-private":false,"requirements-update-strategy":null,"security-advisories":[],"security-updates-only":false,"source":{"api-endpoint":"https://api.github.com/","branch":null,"directory":"/config","hostname":"github.com","provider":"github","repo":"solaluset/DandelionMusic"},"update-subdependencies":false,"updating-a-pull-request":false,"vendor-dependencies":false}}
updater |
proxy | 2024/04/15 21:59:22 [002] GET https://github.com:443/solaluset/DandelionMusic/info/refs?service=git-upload-pack
proxy | 2024/04/15 21:59:22 [002] * authenticating git server request (host: github.com)
proxy | 2024/04/15 21:59:22 [002] 200 https://github.com:443/solaluset/DandelionMusic/info/refs?service=git-upload-pack
proxy | 2024/04/15 21:59:22 [004] POST https://github.com:443/solaluset/DandelionMusic/git-upload-pack
proxy | 2024/04/15 21:59:22 [004] * authenticating git server request (host: github.com)
proxy | 2024/04/15 21:59:22 [004] 200 https://github.com:443/solaluset/DandelionMusic/git-upload-pack
proxy | 2024/04/15 21:59:22 [006] POST https://github.com:443/solaluset/DandelionMusic/git-upload-pack
proxy | 2024/04/15 21:59:22 [006] * authenticating git server request (host: github.com)
proxy | 2024/04/15 21:59:23 [006] 200 https://github.com:443/solaluset/DandelionMusic/git-upload-pack
updater | 2024/04/15 21:59:23 ERROR <job_815138141> Error during file fetching; aborting: The following path based dependencies could not be retrieved: "./config" at /requirements.txt
updater | 2024/04/15 21:59:23 INFO <job_815138141> Finished job processing
updater | 2024/04/15 21:59:23 INFO Results:
updater | Dependabot encountered '1' error(s) during execution, please check the logs for more details.
updater | +---------------------------------+
updater | |             Errors              |
updater | +---------------------------------+
updater | | path_dependencies_not_reachable |
updater | +---------------------------------+
updater | time="2024-04-15T21:59:23Z" level=info msg="task complete" container_id=job-815138141-file-fetcher exit_code=0 job_id=815138141 step=fetcher
updater | time="2024-04-15T21:59:23Z" level=warning msg="failed during fetch, skipping updater" job_id=815138141
Smallest manifest that reproduces the issue
No response

Hi all.
It seems like I have same issue ( Dependabot couldn't find any dependency files in the directory
) here
Happens for package-ecosystem: "pip" only.
package-ecosystem: "github-actions" works fine
dependabot.yml content
https://github.com/ikostan/pico/blob/master/.github/dependabot.yml
Logs:
`Run github/dependabot-action@main
env:
DEPENDABOT_DISABLE_CLEANUP: 1
DEPENDABOT_ENABLE_CONNECTIVITY_CHECK: 0
GITHUB_TOKEN: ***
GITHUB_DEPENDABOT_JOB_TOKEN: ***
GITHUB_DEPENDABOT_CRED_TOKEN: ***
🤖 ~ starting update ~
Fetching job details
Pulling updater images
Starting update process
Created proxy container: b34e2bd22fa1ecc37fd4765c901c73125f22b994cc101081e9ae75e2d58a333f
Created container: b837746c7bc1ff524a4faaac8a34cf273909736b8557d0b9bdff350faf8c3f71
proxy | 2024/08/08 06:08:31 proxy starting, commit: 3f32c0bebd8fc369dc172cfa27c1fd57a6098369
2024/08/08 06:08:31 Listening (:1080)
updater | Updating certificates in /etc/ssl/certs...
updater | rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL
updater | 1 added, 0 removed; done.
updater | Running hooks in /etc/ca-certificates/update.d...
updater | done.
updater | 2024/08/08 06:08:34 INFO <job_866773693> Starting job processing
2024/08/08 06:08:34 INFO <job_866773693> Job definition: {"job":{"allowed-updates":[{"dependency-type":"direct","update-type":"all"}],"commit-message-options":{"prefix":null,"prefix-development":null,"include-scope":null},"credentials-metadata":[{"type":"git_source","host":"github.com"}],"debug":null,"dependencies":null,"dependency-groups":[],"dependency-group-to-refresh":null,"existing-pull-requests":[],"existing-group-pull-requests":[],"experiments":{"record-ecosystem-versions":true,"record-update-job-unknown-error":true,"proxy-cached":true,"dependency-change-validation":true},"ignore-conditions":[],"lockfile-only":false,"max-updater-run-time":2700,"package-manager":"pip","proxy-log-response-body-on-auth-failure":true,"requirements-update-strategy":null,"reject-external-code":false,"security-advisories":[],"security-updates-only":false,"source":{"provider":"github","repo":"ikostan/pico","branch":null,"directory":"/.","api-endpoint":"https://api.github.com/","hostname":"github.com"},"updating-a-pull-request":false,"update-subdependencies":false,"vendor-dependencies":false,"repo-private":false}}
proxy | 2024/08/08 06:08:34 [002] GET https://github.com:443/ikostan/pico/info/refs?service=git-upload-pack
2024/08/08 06:08:34 [002] * authenticating git server request (host: github.com)
proxy | 2024/08/08 06:08:35 [002] 200 https://github.com:443/ikostan/pico/info/refs?service=git-upload-pack
proxy | 2024/08/08 06:08:35 [004] POST https://github.com:443/ikostan/pico/git-upload-pack
2024/08/08 06:08:35 [004] * authenticating git server request (host: github.com)
proxy | 2024/08/08 06:08:35 [004] 200 https://github.com:443/ikostan/pico/git-upload-pack
proxy | 2024/08/08 06:08:35 [006] POST https://github.com:443/ikostan/pico/git-upload-pack
2024/08/08 06:08:35 [006] * authenticating git server request (host: github.com)
proxy | 2024/08/08 06:08:35 [006] 200 https://github.com:443/ikostan/pico/git-upload-pack
updater | 2024/08/08 06:08:35 ERROR <job_866773693> Error during file fetching; aborting: No files found in /
proxy | 2024/08/08 06:08:35 [008] POST /update_jobs/866773693/record_update_job_error
proxy | 2024/08/08 06:08:36 [008] 204 /update_jobs/866773693/record_update_job_error
proxy | 2024/08/08 06:08:36 [010] PATCH /update_jobs/866773693/mark_as_processed
proxy | 2024/08/08 06:08:36 [010] 204 /update_jobs/866773693/mark_as_processed
updater | 2024/08/08 06:08:36 INFO <job_866773693> Finished job processing
updater | 2024/08/08 06:08:36 INFO Results:
Dependabot encountered '1' error(s) during execution, please check the logs for more details.
+---------------------------+
|          Errors           |
+---------------------------+
| dependency_file_not_found |
+---------------------------+
Failure running container b837746c7bc1ff524a4faaac8a34cf273909736b8557d0b9bdff350faf8c3f71
Cleaned up container b837746c7bc1ff524a4faaac8a34cf273909736b8557d0b9bdff350faf8c3f71
proxy | 2024/08/08 06:08:36 0/5 calls cached (0%)
2024/08/08 06:08:36 Posting metrics to remote API endpoint
Error: Dependabot encountered an error performing the update
Error: The updater encountered one or more errors.
For more information see: https://github.com/ikostan/pico/network/updates/866773693 (write access to the repository is required to view the log)
🤖 ~ finished: error reported to Dependabot ~`

@solaluset
I ran the cli against, above mentioned repo and the commit-sha as you have recreated the above error
source:
    provider: github
    repo: ikostan/pico
    branch:
    directory: "/.github/workflows"
    api-endpoint: https://api.github.com/
    hostname: github.com
    commit: d9f478121622b4832c1d9ae52df70822f2094b12

I saw it is working as expected
2024/12/18 11:40:07 INFO No update needed for peaceiris/actions-gh-pages 4
2024/12/18 11:40:07 INFO Finished job processing
2024/12/18 11:40:07 INFO Results:
+-----------------------------------------------------------------+
|               Changes to Dependabot Pull Requests               |
+---------+-------------------------------------------------------+
| created | paambaati/codeclimate-action ( from 8.0.0 to 9.0.0 )  |
| created | codecov/codecov-action ( from 4.5.0 to 5.1.1 )        |
| created | DavidAnson/markdownlint-cli2-action ( from 16 to 18 ) |
+---------+-------------------------------------------------------+

With this not I am closing this ticket please feel free to reopen, if you are able to recreate this.


How can i toggle two different native-base drawers in same screen or same class.

Issue Description
I want to toggle two different native-base drawers on the same screen or the same class, how can we do it. if I use drawer inside another drawer, only the main drawer is toggled.
react-native version - 0.60.5, native-base version - ^2.13.8.
Expected behaviour
I want to toggle two different drawers on the same screen.
Actual behaviour
only the main drawer is toggled whether main drawer or the second drawer is toggled.
Is the bug present in both iOS and Android or any one of them?
Both ios and android.
sample code which I tried is below there.
sample.js.zip

Hi @ppv94 , can you provide snack for minimal code reproduction for the same?

Hi @ppv94 , there can be one drawer at a time on one screen. Closing for now.


Tests are installed with the package

Hi,
Thank you for the great package.
There is a subtle issue when trying to integrate JobSpy to an existing project.
The problem is that tests are being exposed as a package alongside the actual library which leads to problems when there is already a tests package in a project.
e.g.:
from tests import something

It will try to import from JobSpy tests instead of the project.tests
Potential solutions:

Extract tests from the src folder
Exclude tests from the poetry build

good catch


Random fitness based individual generation

Now that the main components are ready:

MSE (as fitness function)
Average color sampler
Individual
Individual renderer

It's possible to begin implementing a simple individual generation algorithm

Random fitness based algorithm:

Starts by creating a set of random individuals where all it's attributes are randomized.
For each individual

The average color is sampled from the target texture.
Individual is rendered over source texture.
Individual fitness is calculated with the output of the previous render and target texture, using a fitness calculator metric such as MSE.

Returns the fittest individual.

Decided to test the masked average color sampler with the same settings.

This method produces a sharper result compared to the initial render, preserving more details. Additionally, the colors are noticeably more accurate.
The downside of this technique is that the mask texture must be rendered before performing masked average color sampling. This requires an additional rendering pass prior to color sampling, effectively doubling the rendering time and slowing down individual generation by approximately 20–40%.


fix for 915: account for different use cases of median

There's a bug in warn_slow: it should inspect the function being called to see whether it accepts a how keyword.  Presently, it's warning users to use the how keyword even if they're using DaskSpectralCubes

the last two commits might've been a red herring; I don't think dask is raising the wrong error message.

Merging. Test failures are unrelated.


GMD: upgrade to org.gradlex:java-module-dependencies:1.4.1

:tada: This issue has been resolved in version 0.12.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add new conventions from Pinecone query result

Proposes to extend semantic-conventions-ai with event attributes determined by https://github.com/traceloop/openllmetry/pull/368

@nirga please take a look at this one as well :)

Thanks @paolorechia! I wonder if we should have complete distinct attributes for chroma and pinecone. I'd rather we have the same attributes for both of them, and then potentially if there's something specific for chroma add just one attribute for that (which is similar to what I'm trying to do here for LLMs). WDYT?

@nirga In principle, I agree.
As we add support for more databases, what is common between different implementations starts to emerge.
Maybe a more efficient development process is to start using the vendor namespace, and then once common attributes are identified, refactor them.
From the implementation, perspective, would you put these vendor specific attributes inside the same package/file currently used? E.g., semantic-conventions-ai?
I’d gladly update this PR along the week.
On a somewhat related topic, playing with different conventions in the code level is cumbersome (because we need to always merge / bump / release).
Any idea how we could simplify this for local development?

Reg. Simplifying the dev process - yes. You just need to depend on the semantic convention package directly in the poetry file (instead of on a published version as it is today).
I'm fine with refactoring later, whatever works for you best. But if there are things that for sure are the same - maybe we can use the same semantic convention from day 1

@galkleinman thanks for the review! Once I get some time I’ll get back to this topic this week.
We’re just missing weaviate example here to decide on the first set of common attributes.
Maybe it makes sense to first implement the basic weviate instrumentation, and also have a test setup for it? Do we have an open issue for that?

@galkleinman please check if the new format is better now:

I'd applied the changes you requested (as I understood it)
I removed the indexing, since I think it was a bad idea I had, and looks cleaner without indexing.

Challenge here: this will cause breaking changes in code, so requires changes in other packages. I couldn't get semantic-conventions-ai package installed locally to be correctly imported, I end up getting a ModuleNotFound  error :/
Regarding Weaviate, like I mentioned, I'll play a bit with it's instrumentation and then propose some attributes for it here.

@nirga, @galkleinman
The best way I could update the ChromaDB with working tests in the same PR is to avoid using the Enum classes directly, and duplicate the strings there.
It would require a second PR to replace the hardcoded attributes with the Enum attributes, but at least no tests will be in a broken state.
Let me know what you think.

I think it's already covered by #368, right?


Enhance Test Coverage for @yamada-ui/layouts

package: @yamada-ui/layouts
Description
@yamada-ui/layouts has a test coverage of less than 95%. We will enhance it to above 95%.
Target files

packages/components/layouts/src/stack.tsx

L246
L259
L329

Problem Statement/Justification
Testing is essential to ensure quality when operating a package.
Additional Information
While it's ideal to cover all tests, if there are too many lines to work on, please create a PR within your capacity.
Any deficiencies not covered by the PR will be automatically created as issues.

I'll try it.


⚠ ClamAV has degraded performance

In 4d3ee4b, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 82 ms

Resolved: ClamAV performance has improved in 98cc975.


Enhancement: Auto-Login with OpenID

What features would you like to see added?
Suggest implementing an environment variable for auto-login when only one OpenID Provider is available, eliminating the need for the current extra click.
More details
Currently, users are required to click the "OpenID" button to log in using an OpenID Provider, which adds an extra step to the login process. This extra click is unnecessary when there are no alternative login methods available.
To streamline the login experience for users who only have one OpenID Provider, I propose introducing an environment variable to enable auto-login. This would eliminate the need for users to click the OpenID button, thereby speeding up the login process.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct

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

What about if only one provider is configured then authentication is automatically redirected to it?


Reverse Engineering DataAnnotations parameters don't give StringLength and others

Steps to reproduce
Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.
The issue
Describe what is not working as expected.
If you are seeing an exception, include the full exceptions details (message and stack trace).
Exception message:
Stack trace:

Further technical details
EF Core version: (found in project.json or packages.config)
Operating system:
Visual Studio version: (e.g. VS 2013 or n/a)
Other details about my project setup:

EntityFrameworkCore.Tools : "1.0.0-preview1-final"
EntityFrameworkCore.SqlServer : "1.0.0-rc2-final"
EntityFrameworkCore.SqlServer.Design : "1.0.0-rc2-final"
Using the Scaffold-DbContext command with -DataAnnotations parameters gives only the [Key] data attributes but not StringLength.
What are the  value of the -DataAnnotations parameters are there some values that are to be used for the StringLength

Possible duplicate of #5289
Can you try running with latest release?

Closing as dupe

Sorry for not being explicit.
Yes, with the 1.0.0-preview1-final, the string length are generated in the OnModelCreating
....
modelBuilder.Entity<TA_ACCESSORY_ACC>(entity =>
{
entity.Property(e => e.GUID_ACC).ValueGeneratedNever();
entity.Property(e => e.NAME_ACC).HasColumnType("varchar(25)");
});
But not in the Model.Only the [Key] is generated
public partial class TA_ACCESSORY_ACC
{
[Key]
public Guid GUID_ACC { get; set; }
public string NAME_ACC { get; set; }
}
Could be interesting to have this generated :
public partial class TA_ACCESSORY_ACC
{
    [Key]
    public Guid GUID_ACC { get; set; }
    [MaxLength(25)]
    public string NAME_ACC { get; set; }
}

@MichelLaplane that is what should be generated when you use 1.0.0-preview2-final. Can you try upgrading and let us know if that is not what you see.


date_modified

Hello, thank you very much for sharing such a great project. However, I seem to be encountering a problem where it is telling me that the "date_modified" module cannot be found when training the model. It seems to be a custom module, but there is no definition in the source code. Can you help me with this issue? Thank you.

https://github.com/Ahmednull/L2CS-Net/blob/a4d8f7fa5436a2b2b9f088471623b552a85811bd/l2cs/utils.py#L71
self._l2cs_device = select_device('cpu', batch_size=1)
  ERROR    Wrong shape for emotion: expected (2,), got (8,)
       ERROR    Error in L2CS gaze extraction: name 'date_modified' is not defined
       ERROR    Wrong shape for emotion: expected (2,), got (8,)
       ERROR    Error in L2CS gaze extraction: name 'date_modified' is not defined


Request body unreadable

The request body is for some URLs broken and shows unreadable entries.
This is what is logged in terminal and also shown in web interface:
�VYo�8�+�Ї�\�����I#�i�$NI۴)���+�ߡ�M��h�X?������7��d�1N�
                                                       ���%��d>gnp�cd[�Ǎ��T�l�J;�*[H��0
                                                                                �6��і�`��9�s߸o(y��)�K8��+H�
ʵ4%k���l�~�*`��,#uR��k�c�^�K���Z��[ͺ��S
1�vi�`�F��ڛ���ڿ��wl���!4\�j�A�d�����w�9R�<?�EIJ켒��<y'��k�r;�����wo'�E�1q�V�Z�J����;
�(�sóxt                                           6�!:��0āk�a80��̮�c����w:�z(�̲�ΐ�O���
&Te��PY\6Z�s
z�#E��Y���A'��1�!I��d��m{6�jo��Q��i��=d:��c~74�`�b��
J�\�U�)��v@v0ĘB^��?���xQg(
                         J5��|a�����Ό�Ծm���Ĳ�f^S���Tg�Y�1LX�����9C4d$q��͌{]"9��V�]�*]s6Y�Z@y}1��qu��E�ԙջ+����]��zR��
�gyO�lh���Aʞ�Q�k7��>�<m+�6��$��/wFU�[WW��Y�|ڎ�:�9P�z��M��G-�G�0}��������_�q�#��᳀�'@�
                      ?H'�z8����� ���N�7���ťZs����5�M�e��3�lu�����4�����?�x��.�w�(ۡ�$�E���x4؍G�x��C�Zh�.]���5���'�������lM@���o0ZҴ(/n�h�ǒ�Qyq}���o�[�N?�hr*n'7�����������tu���b~��f����4� �!e_�2�HӘ<EMAIL_ADDRESS>�Ldc
    <��k�,*JyQ�N�D���S[5��Cy
}*����zV�ę��>�Q��*/~�.t{ҭ~�6�?
                              �B�}��G��j=�+}�P���Xd�O,�iV4��HY�*���S�H=�~�#R�\

Data:
General:
Method: POST
URL:https://api.matjaz.com/api/v12/report
Protocol: HTTP/1.1

Header:
Host : api.matjaz.com
Content-Type : application/json
Accept :*/*
Connection : keep-alive
Content-Encoding : gzip
Accept-Language : en-gb
Accept-Encoding : br, gzip, deflate

Which platform are you running AnyProxy
Platforms: Linux and Mac
Node Version: 8.13.0, 10.13.0

The version of the AnyProxy
v4.0.13 and v4.0.12

Your expected behavior of AnyProxy
I expect to have a stringified and readable output.

It looks like it is connected with iOS. Any reason why?

Hello, I can't accomplish the request of https://api.matjaz.com/api/v12/report successfully,  it seems the 443 port was closed, could you please  provide a stable way to test the request or show me the full response of this request ? Thank u!

This is a local endpoint I would like to evaluate with anyproxy.
 *beforeDealHttpsRequest(requestDetail) { //eslint-disable-line
        if (requestDetail.host.indexOf("api.matjaz.com") !== -1) {
            return true;
        }
    },

Got it, could you show me what's the correct response ( body and headers includes the server encoding ) looks like without proxy?  Or any request body is unreadable in your case ?

{
  "device": {
    "w": 1080,
    "h": 2196,
    "ext": {
    }
  },
  "app": {
    "id": "5924ccf5"
  },
  "request": {
    "plays": [
      {
        "startTime":<PHONE_NUMBER>909,
        "userActions": [
          {
            "action": "viewed",
            "value": "2662",
            "timestamp_millis":<PHONE_NUMBER>440
          },
          {
            "action": "download",
            "timestamp_millis":<PHONE_NUMBER>710
          },
          {
            "action": "open",
            "timestamp_millis":<PHONE_NUMBER>711
          },
          {
            "action": "close",
            "timestamp_millis":<PHONE_NUMBER>711
          }
        ]
      }
    ],
    "errors": [],
    "clickedThrough": [
      "viewed",
      "download",
      "open",
      "close"
    ]
  }
}

The issue is only present when iOS is hitting the endpoint.

The body is OK, could u show me the response headers again please?  I’m trying to reproduce this case.

General
Status Code: 200
Header
Content-Type : application/json; charset=utf-8
Scrat-Version : v0.82.0
Vary : Accept-Encoding
Date : Wed, 20 Mar 2019 15:44:10 GMT
x-anyproxy-origin-content-length : 47
x-anyproxy-origin-content-encoding : gzip
x-anyproxy-origin-connection : keep-alive
Content-Length : 23

{"msg":"ok","code":200}

Found that on Android, Pixel we have the same issue. When tying with Oppo it works. Could it be a security feature on the phone?

It's probably an encoding issue, I want to figure out why only this endpoint is unusual, what's the differences between the other endpoints with JSON response ? They are both gzipped or sharing the same database charset?

Oppo f9 (works):
Matjaz-Version : 5.2.0
User-Agent : Droid/6.3.24
Content-Type : application/json
Host : api.matjaz.com
Connection : Keep-Alive
Accept-Encoding : gzip

Pixel 2 (not working):
Matjaz-Version : 5.2.0
User-Agent : Droid/6.3.24
Content-Encoding : gzip
Content-Type : application/json
Host : api.matjaz.com
Connection : Keep-Alive
Accept-Encoding : gzip

It probably caused by gzip, I will deep into it.

I have tested with iOS 12, or are you looking for the header that is passed in the request by iPhone.

Any update on this issue?

Any update on this issue?

@puppeteer701vungle and @guox191 Any fixes done on this issue? I am having similar issue.  In requestHeaders I am sending:
{ Host: 'www.ocado.com',
   'User-Agent': 'curl/7.68.0',
    Accept: '*/*',
  'Accept-Encoding': 'gzip, deflate, br'
}

but in response gzip is not being sent in connection: It's like
x-anyproxy-origin-content-encoding :gzip
I am expecting Connection-Encoding: gzip in response headers


Add the patch for #330

Description in #330
This check will ensure a TypeError is not raised.

Coverage remained the same at 100.0% when pulling 169d3a56b2418550781064f7022298711380d220 on PrashntS:issue/330 into 41fda483b6cbaf249f541b79c5bf9b882c536470 on timothycrosley:develop.

Very nice!

This looks good to me @PrashntS Thanks!


Update multiple subdomains?

It is possible to update mulitple subdomains with the same IP address?
For instance, some alternatives let you pass in the variable like SUBDOMAIN="test;help".

Not via env vars, but you can do it with a custom config file.

Would you accept a patch for this feature? :-)


Updated MSProducts.xml for more successful Surface downloads

Complete MSProducts.xml including all Surface products listed in Microsoft's SKU Reference as of 8/3/2021
Also included shortcuts to Surface SKU reference and Reddit post listing aka.ms URLs

its using OSDCatalogMicrosoftDriverPack.json now and you may DM maurice directly on twitter if you want to help/contribute to DAT


Clean up Javascript included in dependencies HTML report

Most of the content of the included jquery.jstree.js is not used and can simply be deleted.

Change has been merged


#162 fix schema alignment with spec

see https://github.com/Open-CMSIS-Pack/Open-CMSIS-Pack-Spec/issues/162
The schema did not match the specification in that an unlimited number of e.g.  elements are allowed rather than a maximum of 1.

Intentionally not increasing the version number and date.


Add user-friendly summary (in English, not RDF) to existing Preview options

It's currently difficult to review the record in its entirety before saving. Either make better use of the white space, or provide a user-friendly summary in English (not RDF) to review the record.

Perhaps there could be another option under the dropdown menu for preview for a plain English, user-friendly summary.

when this is done, also use this view for the Preview icon on the Search page (which currently shows a read-only view of the form see #2172 for older work). this can become a separate ticket if needed

also see the latest LC BF Editor design with a preview in the right-hand column, for inspiration: https://youtu.be/pSON9etF054?t=2928

we do have a preview with several format choices, so I think the direction of this ticket should be this part: "Currently, reviewing a complete description set involves looking at the values in four (for our RDA profiles; this would be three in the case of BIBFRAME) resource templates."
and should be considered as part of overall work cycle goal of improving UX for working with multiple related resources / templates.
changing title accordingly

this may not be necessary with the work @justinlittman is currently doing to improve inputs, and changing existing "View Resource" to show read-only view

Close @michelleif ?

@michelleif Yes, I think the Form view will work. Thanks!


Setting ServiceAccount name breaks permissions to cluster API

Allowing users to set the ServiceAccount name here breaks the ClusterRoleBinding here due to the way the ServiceAccount name is handled in the _helpers.tpl file here. This results in the Collector not being able to open an input stream to cluster API, returning a 403 response. Please see below for error message for details:
D, [2022-04-26T15:26:17.197738 #13] DEBUG -- : loaded K8S config from  with master @ https://kubernetes.default.svc/ with ca certificate /var/run/secrets/kubernetes.io/serviceaccount/ca.crt with client_cert_file  with client key file  with trust_certs false with trust store file  with proxy username
D, [2022-04-26T15:26:19.194230 #13] DEBUG -- : Ensuring cache directory is present: /tmp/cache
D, [2022-04-26T15:26:19.488109 #13] DEBUG -- : Fetching state...
D, [2022-04-26T15:26:19.508177 #13] DEBUG -- : Connecting to URL: https://kubernetes.default.svc/api/v1/nodes
E, [2022-04-26T15:26:23.395960 #13] ERROR -- : [IOError]: Could not open an input stream to cluster API: Server returned HTTP response code: 403 for URL: https://kubernetes.default.svc/api/v1/nodes
E, [2022-04-26T15:26:23.405555 #13] ERROR -- : Backtrace:
	uri:classloader:/mesos-collector/lib/common/fetcher.rb:28:in `fetch'
	uri:classloader:/mesos-collector/bin/container-collector.rb:132:in `block in do_fetch_state'
	org/jruby/RubyHash.java:1415:in `each'
	uri:classloader:/mesos-collector/bin/container-collector.rb:131:in `do_fetch_state'
	uri:classloader:/mesos-collector/bin/container-collector.rb:114:in `block in do_upload'
	org/jruby/RubyKernel.java:1442:in `loop'
	uri:classloader:/mesos-collector/bin/container-collector.rb:109:in `do_upload'
	uri:classloader:/mesos-collector/bin/container-collector.rb:56:in `upload_k8s_state_v2'
	uri:classloader:/gems/boson-1.3.0/lib/boson/runner_library.rb:12:in `block in upload_k8s_state_v2'
	org/jruby/RubyMethod.java:131:in `call'
	uri:classloader:/gems/boson-1.3.0/lib/boson/scientist.rb:87:in `block in upload_k8s_state_v2'
	uri:classloader:/gems/boson-1.3.0/lib/boson/scientist.rb:123:in `call_original_command'
	uri:classloader:/gems/boson-1.3.0/lib/boson/scientist.rb:115:in `during_analyze'
	uri:classloader:/gems/boson-1.3.0/lib/boson/scientist.rb:107:in `analyze'
	uri:classloader:/gems/boson-1.3.0/lib/boson/scientist.rb:86:in `block in upload_k8s_state_v2'
	uri:classloader:/gems/boson-1.3.0/lib/boson.rb:79:in `full_invoke'
	uri:classloader:/gems/boson-1.3.0/lib/boson/bare_runner.rb:42:in `execute_command'
	uri:classloader:/gems/boson-1.3.0/lib/boson/runner.rb:35:in `execute_command'
	uri:classloader:/gems/boson-1.3.0/lib/boson/runner.rb:31:in `execute'
	uri:classloader:/gems/boson-1.3.0/lib/boson/runner.rb:26:in `start'
	uri:classloader:/mesos-collector/bin/container-collector.rb:198:in `<main>'
	org/jruby/RubyKernel.java:1009:in `load'
	uri:classloader:/META-INF/main.rb:1:in `<main>'
	org/jruby/RubyKernel.java:974:in `require'
	uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in `require'
	<script>:3:in `<main>'
E, [2022-04-26T15:26:23.418309 #13] ERROR -- : Could not open an input stream to cluster API: Server returned HTTP response code: 403 for URL: https://kubernetes.default.svc/api/v1/nodes
E, [2022-04-26T15:26:23.487793 #13] ERROR -- : ATTENTION: The most common cause of this error is that the [CHT_API_TOKEN] or [CHT_CLUSTER_NAME] environment variables were not configured properly as part of agent deployment. Please check your full configuration, including the API token and the cluster name. After your config has been fixed, please wait 15 minutes for the changes to take effect, and collection to resume.

Either the ServiceAccount name should not be able to be set in the values.yaml file and instead overridden using something like nameOverride or fullnameOverride, or the ClusterRoleBinding should be updated to use the ServiceAccount name specified by the user.

Nice catch @sharkeyl . Let have a PR for this soon.

Fixed in Helm Chart version 1.1.2


how to compile OpenCV (cv2)

I'm sorry to bother you with this question. I'm not a python developer I just need to integrate some python code as lambda functions into my serverless configuration.
I was provided with precompiled OpenCV that targets Lambda but I thought it would be better if that can be integrated into the serverless deployment step.
For numpy I was able to create the requirements.txt just fine but OpenCV doesn't seems to be installable via pip. I know that OpenCV has to be compiled and I read that this serverless plugin is able to do that via running a Docker container. I configured the plugin to run Docker but now I'm stuck.
How can I build OpenCV?

Ok, the Docker image seems to only work for pip dependencies.
OpenCV isn't available via pip, so I'm just closing this issue again,


Errors compiling 3.1 branch

I'm having some issues with the 3.1 branch, is there something we need to cherry-pick to this branch that was applies to master?
cl /Fosrc\gen\AudioEffectSpectrumAnalyzer.obj /c src\gen\AudioEffectSpectrumAnalyzer.cpp /TP /nologo /EHsc /D_DEBUG /MDd /I. /Igodot_headers /Iinclude /Iinclude\gen /Iinclude\core
AudioEffectSpectrumAnalyzer.cpp
c:\users\basti\development\gdnative\godot-cpp\include\gen\AudioEffectSpectrumAnalyzer.hpp(35): error C3646: 'get_fft_size': unknown override specifier
c:\users\basti\development\gdnative\godot-cpp\include\gen\AudioEffectSpectrumAnalyzer.hpp(35): error C2059: syntax error: '('
c:\users\basti\development\gdnative\godot-cpp\include\gen\AudioEffectSpectrumAnalyzer.hpp(35): error C2238: unexpected token(s) preceding ';'
src\gen\AudioEffectSpectrumAnalyzer.cpp(61): error C2039: 'FFT_Size': is not a member of 'godot::AudioEffectSpectrumAnalyzer'
c:\users\basti\development\gdnative\godot-cpp\include\gen\AudioEffectSpectrumAnalyzer.hpp(16): note: see declaration of 'godot::AudioEffectSpectrumAnalyzer'
src\gen\AudioEffectSpectrumAnalyzer.cpp(61): error C2039: 'get_fft_size': is not a member of 'godot::AudioEffectSpectrumAnalyzer'
c:\users\basti\development\gdnative\godot-cpp\include\gen\AudioEffectSpectrumAnalyzer.hpp(16): note: see declaration of 'godot::AudioEffectSpectrumAnalyzer'
src\gen\AudioEffectSpectrumAnalyzer.cpp(61): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
src\gen\AudioEffectSpectrumAnalyzer.cpp(61): error C2146: syntax error: missing ';' before identifier 'get_fft_size'
src\gen\AudioEffectSpectrumAnalyzer.cpp(61): error C2143: syntax error: missing ';' before '{'
src\gen\AudioEffectSpectrumAnalyzer.cpp(61): error C2447: '{': missing function header (old-style formal list?)
scons: *** [src\gen\AudioEffectSpectrumAnalyzer.obj] Error 2
scons: building terminated because of errors.

Looks like this is the same cause as #285 , something in the JSON generation

This was caused by missing bindings in the audio system. This was fixed upstream in godot 3.1 and followed through in godot_headers 3.1. Should all be good now.

Seems that this regression is still present when trying to compile bindings using an api.json generated using the latest stable Godot v3.1.1 branch.
I get the exact same errors when using this self-generated api.json.
Is this an issue that should be addressed in the Godot branch? Or should this be fixed in godot-cpp?