[Test Issue] Tested for OTA in esp32, found it was with very a slow speed, how can I increase BDX transfer speed?

Test issue(s)
The ota-provider sample can work fine, but the speed of it is sadly slow, I have a 1.7mb *.ota file, and it made alomst 10 minutes to transfer into esp32, how can I resolve this situation, thank you guys very much!!
Platform
No response
Anything else?
No response

@jadhavrohit924 PTAL

Hi @moculll, there is API to increase download block size, you have to set the maxDownloadBlockSize using SetMaxDownloadBlockSize API here

Hi @moculll, there is API to increase download block size, you have to set the maxDownloadBlockSize using SetMaxDownloadBlockSize API here

Thank you! So the solution means that if I want to increase OTA block size, the only way is to use this api in device side, right? And there is no way to increase this in ota provider side

There is, I want to confirm which provider are you using esp32 or linux?

There is, I want to confirm which provider are you using esp32 or linux?

thanks for your reply, I tried both linux and darwin ota-provider, their speed seems the same, and I also notice one thing in matter-1.2-core-specification in page795, there says "Maximum Block Size requested by OTA Requestors over non-TCP transports SHALL be no
larger than 1024 (2^10) bytes. OTA Providers SHALL support the Maximum Block Size of at
least 1024 bytes in those cases.", does that mean if I increase blocksize in thread device like esp32h2, its MaxBlockSize is still limited to 1024bytes?

There is, I want to confirm which provider are you using esp32 or linux?

I have another thought about ota retry times, I tried to ota several devices like : 8 ota-linux-providers on ubuntu22.04 server, 8 device waiting for ota command, and when I started the progress, I found that almost half of the ota-linux-providers meet "stop ota progress after 3 times retries", so how can I make sure a ota progress won't stop evenif there are a few retries?

Hi all,
I add  SetMaxDownloadBlockSize 10240  in  /examples/ota-requestor-app/linux/main.cpp, but final transmit is 1024
How to increase transmit size
[1713358759.544753][1056:1056] CHIP:ATM: ReceiveInit
[1713358759.544769][1056:1056] CHIP:ATM:   Proposed Transfer Control: 0x20
[1713358759.544788][1056:1056] CHIP:ATM:   Range Control: 0x0
[1713358759.544806][1056:1056] CHIP:ATM:   Proposed Max Block Size: 10240
[1713358759.544823][1056:1056] CHIP:ATM:   Start Offset: 0x0000000000000000
[1713358759.544838][1056:1056] CHIP:ATM:   Proposed Max Length: 0x0000000000000000
[1713358759.544853][1056:1056] CHIP:ATM:   File Designator Length: 29
[1713358759.889212][1056:1056] CHIP:ATM: Handling received BDX Message
[1713358759.889231][1056:1056] CHIP:ATM: ReceiveAccept
[1713358759.889245][1056:1056] CHIP:ATM:   Transfer Control: 0x20
[1713358759.889260][1056:1056] CHIP:ATM:   Range Control: 0x0
[1713358759.889277][1056:1056] CHIP:ATM:   Max Block Size: 1024
[1713358759.889293][1056:1056] CHIP:ATM:   Length: 0x0000000000000000

@GnarFang Did you

Hi all, I add SetMaxDownloadBlockSize 10240 in /examples/ota-requestor-app/linux/main.cpp, but final transmit is 1024 How to increase transmit size
[1713358759.544753][1056:1056] CHIP:ATM: ReceiveInit [1713358759.544769][1056:1056] CHIP:ATM: Proposed Transfer Control: 0x20 [1713358759.544788][1056:1056] CHIP:ATM: Range Control: 0x0 [1713358759.544806][1056:1056] CHIP:ATM: Proposed Max Block Size: 10240 [1713358759.544823][1056:1056] CHIP:ATM: Start Offset: 0x0000000000000000 [1713358759.544838][1056:1056] CHIP:ATM: Proposed Max Length: 0x0000000000000000 [1713358759.544853][1056:1056] CHIP:ATM: File Designator Length: 29
[1713358759.889212][1056:1056] CHIP:ATM: Handling received BDX Message [1713358759.889231][1056:1056] CHIP:ATM: ReceiveAccept [1713358759.889245][1056:1056] CHIP:ATM: Transfer Control: 0x20 [1713358759.889260][1056:1056] CHIP:ATM: Range Control: 0x0 [1713358759.889277][1056:1056] CHIP:ATM: Max Block Size: 1024 [1713358759.889293][1056:1056] CHIP:ATM: Length: 0x0000000000000000

@GnarFang I also have same problem. Did you solve this problem? If so, advise me plz.


Expand dask.utils.is_arraylike docstring.

[x] Closes #7327
[ ] Tests added / passed
[x] Passes black dask / flake8 dask

Specifically to point out difference between what the function is checking and how NumPy defines array_like

cc @shoyer @pentschev @jrbourbeau @jsignell @mrocklin (in case any of you have thoughts/suggestions on this change)

thanks @jrbourbeau changes incoprorated :+1:


Replace white/blacklists with error handler

This will fix #91. It still needs some tests.

Once this has some tests it will be good to go.


AzKeys - Get Key - Any way to filter the keys using the tags?

Bug Report

[Azkyes - GetKey] - (https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/azkeys#Client.GetKey)
SDK version Latest

What happened? - I need to filter the keys by using the existing Tags. Is there any way to achieve without fetching all the keys list and then iterate to filter?
What did you expect or want to happen? - need to fetch specific key by passing some filter as tags

Hi @Roopan92. The GetKey method does not have the option to filter by tags. However, you can specify the specific name and version of the key.

Thanks @gracewilcox - As workaround we are listing, iterating and finding the key with the specific tags.

For more information on the capabilities of the Azure SDK for Go, I recommend looking at the REST API documentation. Our SDK directly builds on top of the REST API, so if the API doesn't have a capability, the SDK won't have it.
REST API links:
Keys
Certificates
Secrets

Got it @gracewilcox. Thanks for your support.


fix(origin-backend-client): fix file upload regression

I don't get it but LGTM I guess 😃

This file does simple string replacement to fix uploads. (kind of a hack to make it work)
Since the dependency update changed the string that needs to be replaced, it also broke the uploads.


Updating sft debug env variable

We've found in using the tools that it's SFT_DEBUG as opposed to SCALEFT_DEBUG.

Yes, thank you!


fix overflow on devs

Description of the change:
Fix production for-developers overflow styles.
Reason for the change:
Production for-developers overflow styles are broken.

Hello @richbachman,Thanks again for the PR! We appreciate your contribution and look forward to                                              continued collaboration. Thanks!                                             Team SendGrid DX


Add SRGAN PyTorch Implementation

You may change images of the results (grid are too congested and results are not properly highlighted)

Move your folder to new folder named multimodal_models

Done.

Move to super_resolution folder, my bad


 ?

It's not clear from info supplied on this page how to obtain the value <BOOT LOADER IDENTIFIER> shown under 'Enable dump log and Serial Console,' step 2., line below:
bcdedit /store F:\boot\bcd /ems {<BOOT LOADER IDENTIFIER>} ON

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

ID: 602fe342-29e0-ce4a-c37c-ad8ae1473681
Version Independent ID: ac46d53a-6a27-d4ff-4c34-a6676303587f
Content: VM startup is stuck on
Content Source: articles/virtual-machines/troubleshooting/troubleshoot-vm-boot-configure-update.md
Service: virtual-machines-windows
GitHub Login: @Deland-Han
Microsoft Alias: delhan

@jelew , Thank you for raising the issue. We will investigate and update you.

@jelew You can use the command "bcdedit /enum /v" to display boot identifiers. This will output all boot devices on the machine, to be sure to select the one attached to the drive you are looking for.
Please let me know if you need any additional information.

Thanks @TravisCragg-MSFT :)
@jelew Hope that helped answer your question. We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


fix: ResendValidation page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/5942
Tests | QA Steps

Lanch the app
Enter a new account with a long email which hasn't been validated and Click Continue.
Or use a validated account and click forget?.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web | Mobile Web | Desktop

iOS

Android

@johnmlee101 It's happening on each PR.


expose akara's component filters in lua

need to be able to create a lua table for akara.ComponentFilterBuilder. This table should have mappings for the existing methods for the builder.
example usage:
filter = director.components.newFilter()

filter.require(director.components.transform)

sub = director.addSubscription(filter)

This effort will likely need to be implemented inside of akara, such that any other project that uses akara could also benefit from it.

This is related to #16 as this would be exposed inside of the director global as director.components and director.addSubscription


DOC: Documentation for Eddymotion Python Module Usage

This pull request adds instructions on integrating Eddymotion functionalities with custom diffusion-weighted imaging (DWI) data within Python modules. By following these steps, users can incorporate Eddymotion functionnalities into their projects. Closes issue #126.

Did you close it by accident?

Did you close it by accident?

No, it wasn't accidental. Sorry about this. I included the changes related to CLI in this one. I'm starting a new, cleaner one containing only the changes related to the documentation.


store createdAt in localStorage.account

followup for https://github.com/hoodiehq/hoodie/issues/282
pass created at to the sign up request, so the server can store createdAt and a separate signedUpAt timestamp. Related server issue: https://github.com/hoodiehq/hoodie-account-server/issues/154

me!

@thomasjinlo I’ve seen the other day that we don’t actually store createdAt in localstorage yet. You can see it when you open https://tracker.hood.ie/ and then check the value of localStorage.account, it’s something like "{"id":"iqfmlp8"}", but besides the "id" there should also be the "createdAt" timestamp. I thought we had that already but maybe it got lost somewhere? Do you want to look into that first?

@thomasjinlo are you still looking into this one?


Spreadsheet project step 98 needs minor clarification

Describe the Issue
In the step 98 of the js beta spreadsheet project, the instructions fail to specify the order of the numbers to be returned in the result array(s). For eg does it want the first two numbers in the order they are given in the input array? And does it want the last two numbers in the order they are given in the input array? This lack of information can lead to code like the one below being rejected without a clear explanation why.
It would be good to be explicit in the instructions about the expected order of the numbers in the final array.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures-v8/learn-functional-programming-by-building-a-spreadsheet/step-98
Your code
lasttwo : nums => [nums[nums.length-1], nums[nums.length-2]]

Expected behavior
Directly state that the expected array needs to retain the same order of elements as the input array.
Screenshots
No response
System
N/A
Additional context
Original forum post that revealed the issue
https://forum.freecodecamp.org/t/learn-functional-programming-by-building-a-spreadsheet-step-98/716040?u=hbar1st

This issue is now open for first time contributors. A PR which resolves this issue will update the step instructions to read:
Add a `firsttwo` property which takes a `nums` parameter and returns the first two elements of the `nums` array in order. Then add a `lasttwo` property which returns the last two elements of the `nums` array in order.

would love to contribute to this issue!

Hey @Ris345 Thank you for your interest in contributing. We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue.
Issues labeled with help wanted or first timers only are open for contributions.
Please make sure you read our guidelines for contributing. We prioritize contributors following the instructions in our guide. Join us in our chat room or the forum if you need help contributing - our community will be happy to assist you.


fix: error alert levels again

SUMMARY

Even after these fixes, and apparently because this doesn't repro well in the testenv, there were still issues with my previous fix because we use level in the styled components (which i missed the first 2 times here).
I'm going to cherrypick this fix into our deploy before merging this PR this time, since i've failed to fix this twice already
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

CI, deploy to our internal env for repro
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

to: @rusackas @graceguo-supercat @michael-s-molina

This is verified in our env, so ready for a stamp


Make stereo waves mmaped, only flatten when indexing

Add test to ensure resulting array shapes are correct.
Fixes #20.
What is the speed impact??
keywords: stereo, mmap, fps, benchmark

OS: linux kubuntu
file: sd3-winter
before:

388fps trigger
216fps render
59.7MB

after:

219fps trigger
183fps render
55-59MB memory

unacceptable performance degradation. Either use cython or paged memory (precompute whenever loading a page).

np.sum()
/= nchan

"current stereo" is faster than mono. Mmap is the bottleneck. This should be merged.


Interface 'Ratchet\MessageComponentInterface' not found

Hello,
I've referred http://socketo.me/docs/hello-world example,
directory structure > bin/chat-server.php, src/MyApp/Chat.php still shows 'Ratchet\MessageComponentInterface' not found
Note: - Tried composer update, as well  "autoload": {         "psr-4": {             "MyApp\\": "src"         }     }

Probably related to my pull request https://github.com/ratchetphp/Ratchet/pull/785

Try running a composer update before running the bin file. Composer needs to update its autoload file with reference to your directory.


Ubuntu RDP 22.04.01 out of the box is not working

I cannot find a suitable name for this because there is bunch of FreeRDP errors. I dont know which one is causing it in particular. So please bear with me..
How to repro:
Installed Ubuntu 22.04.01 as Hyper-V VM on host OS Windows 11 Pro x64
Updated it by sudo apt upgrade.
Enabled Settings-Sharing, RDP, set password
Tried to connect from Windows 11 and received "Because of protocol error this session will be disconnected... Error code 0xd06"
ran systemctl --user status gnome-remote-desktop and although the status is green there are errors. All of them are pointing to FreeRDP.
Here is extract from journalctl (I think meaningful info is starting at 21:21:51):
Aug 29 21:20:34 ub-tf gnome-remote-de[16488]: RDP server started
Aug 29 21:21:00 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:665] [16488:16553] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
Aug 29 21:21:00 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
Aug 29 21:21:01 ub-tf gnome-remote-de[16488]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_106, Client cap flags: H264 (AVC444): true, H264 (AVC420): true
Aug 29 21:21:01 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:01:692] [16488:16553] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
Aug 29 21:21:01 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:01:692] [16488:16553] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Aug 29 21:21:01 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:01:692] [16488:16557] [ERROR][com.freerdp.channels.rdpgfx.server] - WTSVirtualChannelRead failed!
Aug 29 21:21:01 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:01:692] [16488:16557] [ERROR][com.freerdp.channels.rdpgfx.server] - rdpgfx_server_handle_messages failed with error 1359
Aug 29 21:21:01 ub-tf gnome-remote-de[16488]: Unable to check file descriptor, closing connection
Aug 29 21:21:01 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:01:695] [16488:16488] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
Aug 29 21:21:51 ub-tf gnome-remote-de[16488]: RDP server stopped
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:20:57:754] [16488:16553] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:20:57:754] [16488:16553] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:20:57:754] [16488:16553] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.connection] - Accepted client: XXXXX
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.connection] - Accepted channels:
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.connection] -  rdpdr
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.connection] -  rdpsnd
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.connection] -  cliprdr
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.connection] -  drdynvc
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.gcc] - Active rdp encryption level: NONE
Aug 29 21:21:51 ub-tf gnome-remote-desktop-daemon[16488]: [21:21:00:666] [16488:16553] [INFO][com.freerdp.core.gcc] - Selected rdp encryption method: NONE
Aug 29 21:21:52 ub-tf gnome-remote-de[16588]: RDP server started
Aug 29 21:22:02 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:101] [16588:16618] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
Aug 29 21:22:02 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
Aug 29 21:22:02 ub-tf gnome-remote-de[16588]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_106, Client cap flags: H264 (AVC444): true, H264 (AVC420): true
Aug 29 21:22:02 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:124] [16588:16618] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
Aug 29 21:22:02 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:124] [16588:16618] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Aug 29 21:22:02 ub-tf gnome-remote-de[16588]: Unable to check file descriptor, closing connection
Aug 29 21:22:02 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:127] [16588:16588] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
Aug 29 21:22:15 ub-tf gnome-remote-de[16588]: RDP server stopped
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:21:58:892] [16588:16618] [INFO][com.freerdp.core.connection] - Client Security: NLA:1 TLS:1 RDP:0
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:21:58:892] [16588:16618] [INFO][com.freerdp.core.connection] - Server Security: NLA:1 TLS:0 RDP:0
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:21:58:892] [16588:16618] [INFO][com.freerdp.core.connection] - Negotiated Security: NLA:1 TLS:0 RDP:0
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.connection] - Accepted client: XXXXX
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.connection] - Accepted channels:
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.connection] -  rdpdr
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.connection] -  rdpsnd
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.connection] -  cliprdr
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.connection] -  drdynvc
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.gcc] - Active rdp encryption level: NONE
Aug 29 21:22:15 ub-tf gnome-remote-desktop-daemon[16588]: [21:22:02:102] [16588:16618] [INFO][com.freerdp.core.gcc] - Selected rdp encryption method: NONE
Aug 29 21:23:32 ub-tf gnome-remote-de[1824]: RDP server started
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:153] [1824:2525] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:154] [1824:2525] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
Aug 29 21:23:44 ub-tf gnome-remote-de[1824]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_106, Client cap flags: H264 (AVC444): true, H264 (AVC420): true
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:177] [1824:2525] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:177] [1824:2525] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:177] [1824:2536] [ERROR][com.freerdp.channels.rdpgfx.server] - WTSVirtualChannelRead failed!
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:177] [1824:2536] [ERROR][com.freerdp.channels.rdpgfx.server] - rdpgfx_server_handle_messages failed with error 1359
Aug 29 21:23:44 ub-tf gnome-remote-de[1824]: Unable to check file descriptor, closing connection
Aug 29 21:23:44 ub-tf gnome-remote-desktop-daemon[1824]: [21:23:44:181] [1824:1824] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe
Aug 29 21:24:12 ub-tf gnome-remote-desktop-daemon[1824]: [21:24:12:647] [1824:2662] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_CONTINUE_NEEDED [0x00090312]
Aug 29 21:24:12 ub-tf gnome-remote-desktop-daemon[1824]: [21:24:12:648] [1824:2662] [WARN][com.winpr.negotiate] - AcceptSecurityContext status SEC_I_COMPLETE_NEEDED [0x00090313]
Aug 29 21:24:12 ub-tf gnome-remote-de[1824]: [RDP.RDPGFX] CapsAdvertise: Accepting capability set with version RDPGFX_CAPVERSION_106, Client cap flags: H264 (AVC444): true, H264 (AVC420): true
Aug 29 21:24:12 ub-tf gnome-remote-desktop-daemon[1824]: [21:24:12:675] [1824:2662] [ERROR][com.freerdp.core.transport] - BIO_read returned a system error 104: Connection reset by peer
Aug 29 21:24:12 ub-tf gnome-remote-desktop-daemon[1824]: [21:24:12:675] [1824:2662] [ERROR][com.freerdp.core] - transport_read_layer:freerdp_set_last_error_ex ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x0002000D]
Aug 29 21:24:12 ub-tf gnome-remote-de[1824]: Unable to check file descriptor, closing connection
Aug 29 21:24:12 ub-tf gnome-remote-desktop-daemon[1824]: [21:24:12:680] [1824:1824] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Broken pipe

Connection reset by peerConnection reset by peer is usually an indication that the server cut the connection due to whatever reason.
Have you tried connecting with mstsc to the same server with the same user? Does that work?

apparently there is a bug in Windows RDP client. You need to change display colours to 32-bit - tested, working.

https://askubuntu.com/questions/1426376/native-rdp-on-ubuntu-22-04-not-working/1426453#1426453


ERROR! 401 { error: 'Not logged in', success: false }

I am running the sample.js file with putting my key and secret but unfortunately i am receiving the following erroe:
ERROR! 401 { error: 'Not logged in', success: false } (node:21804) UnhandledPromiseRejectionWarning: Error: Not logged in     at IncomingMessage.<anonymous> (C:\Users\siddh\Desktop\FTX\ftx-api-rest\index.js:130:27)     at IncomingMessage.emit (events.js:215:7)     at endReadableNT (_stream_readable.js:1183:12)     at processTicksAndRejections (internal/process/task_queues.js:80:21) (node:21804) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:21804) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

That's FTX way of telling you there is a problem with the API key

That error is response coming straight from FTX, as such not much this library can do with or about it. I am closing this (as it's not an issue with this project) but if the issue persists feel free to provide additional information here.


v 0.2 roadmap

[x] Lists / arrays
[x] For loops
[x] Functions
[x] Comments

milestones complete for v0.2 release


collectors

doctrine = true
Fatal error: Class 'Doctrine\DBAL\Logging\DebugStack' not found in /Users/huangjinlong/developer/projects/phalcon_demo/vendor/snowair/phalcon-debugbar/src/PhalconDebugbar.php on line 230

You should install the doctrine/orm package first.

ok,thanks.


Removed things

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

d


macOS build fails with master

Godot version:
Latest/master
It seems that for some reason it looks for Android defaults instead of macOS.
$ scons platform=osx
scons: Reading SConscript files ...
YASM is necessary for WebM SIMD optimizations.
WebM SIMD optimizations are disabled. Check if your CPU architecture, CPU bits or platform are supported!
Checking for C header file mntent.h... no
scons: done reading SConscript files.
scons: Building targets ...
[...]
[ 88%] Compiling ==> core/global_defaults.gen.cpp
core/global_defaults.gen.cpp:2:10: fatal error: 'platform/android/globals/global_defaults.h' file not found
#include "platform/android/globals/global_defaults.h"
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
scons: *** [core/global_defaults.gen.osx.tools.64.o] Error 1
scons: building terminated because of errors.

Duplicate of #24507.


Remove Filter and use Contains instead

Part of https://github.com/paritytech/polkadot/issues/2841
Companion: paritytech/polkadot#3591
Filter and Contains do exactly the same thing, but are used in slightly different contexts. This just merges them, allowing some utilities written for Contains to be used where Filter was in use.
Migration
Items within frame_support::traits:

Usage of Filter should be replaced with Contains.
Usage of Filter::filter() should be replaced with Contains::contains(). This includes derivative usage within the inheriting trait FilterStack.
Usage of All<...> should be replaced with Everything (NOTE: The type agument should be dropped).
Usage of AllowAll should be replaced with Everything
Usage of DenyAll should be replaced with Nothing

bot merge


Fixed can not open couchdb credentials.

This fix if couchdb need credentials, credentials page can not open issues.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] Tested basic functionality

This fixed https://github.com/benweet/stackedit/issues/1826.


Adding async-main support

This patch adds the async-main start-point for programs.
When a static func main() async is inserted into the main program, it
gets called through _runAsyncMain instead of calling directly. This
starts the program in an async context, which is good because then we
can do async stuff from there.
The following code
@main struct MyProgram {
  static func main() async {
    // async code
  }
}

is turned into
@main struct MyProgram {
  static func $main() {
    _runAsyncMain(main)
  }

  static func main() async {
    // async code
  }
}

_runAsyncMain code-gen's to the same thing as runAsyncAndBlock, which
emits a call to swift_task_runAndBlockThread.
Resolves: rdar://71828636

@swift-ci please smoke test

Need to look for something else because runAsyncAndBlock blocks the main thread, which is kind of necessary for anything UI related.

Need to look for something else because runAsyncAndBlock blocks the main thread, which is kind of necessary for anything UI related.

@swift-ci please smoke test Linux platform

@swift-ci please smoke test Linux platform

At the very least, this will fail the tests because I haven't updated the AST check. It'll be fixed with the rebase.

At the very least, this will fail the tests because I haven't updated the AST check. It'll be fixed with the rebase.

@swift-ci please smoke test

@swift-ci please smoke test

error: use of undeclared identifier 'RTLD_SELF'

error: use of undeclared identifier 'RTLD_SELF'

@swift-ci please smoke test

@swift-ci please smoke test

It's worth adding runtime tests, one that completes normally and one that fails with a thrown error

Tests added.

It's worth adding runtime tests, one that completes normally and one that fails with a thrown error

Tests added.

@swift-ci please smoke test

@swift-ci please smoke test

error: use of undeclared identifier 'RTLD_SELF'

Replaced RTLD_SELF with RTLD_DEFAULT.

error: use of undeclared identifier 'RTLD_SELF'

Replaced RTLD_SELF with RTLD_DEFAULT.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test windows platform

@swift-ci please smoke test windows platform

The SwiftPM test failures (on Linux and MacOS) were due to unrelated changes to this PR.
@swift-ci please smoke test macOS Platform
@swift-ci please smoke test Linux Platform

The SwiftPM test failures (on Linux and MacOS) were due to unrelated changes to this PR.
@swift-ci please smoke test macOS Platform
@swift-ci please smoke test Linux Platform

@swift-ci Please smoke test macOS platform

@swift-ci Please smoke test macOS platform


[Lease][State] export the lease currency in Opening states

Add the lease currency as a field of the lease::api::query::StateResponse Opening variant

done with #560c5a2


#3345 - move attribute comparisons into their own method on the model

This should allow models to provide custom logic to compare atributes. For a set, each attribute will still be compared to every other attribute between the two models. I'm not going to try to change that behavior. This should be enough wiggle room to allow for more powerful comparisons.
I don't know about naming conventions but attributesAreEqual does not appear in any Backbone projects on Github. I'm not wedded to the name.
Also, I wasn't able to get the tests to work on Firefox without moving jQuery to the top of the stack.

Let's add in a few more tests for the expected behavior of this method (how are Model#set and Model#changedAttributes affected once you've overwritten them? Show a good example of the use case of this change.)
How about isEqual, equals, or attributesEqual instead? The name is a bit verbose.

I like "attributesEqual". I'll update in the next few days with some more tests.

Updated with more verbose unit tests. Also looking at the code again I think it'd be helpful to also pass the name of the attribute. I added it as the last parameter for attributesEqual as it could be an 'optional' parameter, but it could be moved to the first too.

How about a real use case?

I'm sorry, you mean write a different (better) test or to restate the issue driving the request?

This should be enough wiggle room to allow for more powerful comparisons.

 When and how would this be useful? Why is doing it in this way a better idea than overriding _.isEqual in your project?

This would aid in comparisons of objects where some data may be extraneous and should be skipped, or where "equality" between objects may need some complex logic. This seems to be a pretty common case in applications. You're not the first to suggest overwriting _.isEqual. In the ticket leading to this pull request and on StackOverflow and the like, it's cited as common practice. At my place of business, our Backbone application currently does this as well. We catch 'set' operations at a global level and swap out isEqual with a custom method.
I'm not in favor of the approach for a number of reasons. First and foremost, I don't like overwriting good existing code in a separate namespace. Doing so in this manner, however brief, means that the _.isEqual is extended for the whole application (at least with how we use RequireJS). If a dev forgets to restore it back to its original state it could lead to side effects elsewhere.
I like the idea of the model being able to define how its attributes are compared. Any exception to the standard isEqual methodology would probably be very specific to the model itself, most would probably utilize the default behavior. This could allow the few models that need to override isEqual behavior the means to do so. Of course getting such a method into the prototype chain would mean that child classes could build on their parent's attribute comparison logic.

We catch 'set' operations at a global level and swap out isEqual with a custom method.

Can you show us what that custom method looks like?

Can't show the exact code, of  course, but this is a close approximation.
The overriding:
  custom.namespace.BackboneOverride.set = function( key, val, options ) {
    var rv;

    _.isEqual = custom.namespace.BackboneOverride.isEqual;
    rv = custom.namespace.BackboneOverride.original.set.call( this, key, val, options );
    _.isEqual = custom.namespace.BackboneOverride.original.isEqual;

    return rv;
  };

Custom isEqual:
  custom.namespace.BackboneOverride.isEqual = function( a, b ) {
    if( ( a instanceof Backbone.Model && b instanceof Backbone.Model ) ||  ( a instanceof Backbone.Collection && b instanceof Backbone.Collection ) ) {
      if ( ( a instanceof Backbone.Model ) && ( a === b ) ) {
        return _.size( a.changedAttributes() ) === 0;
      }

      return custom.namespace.BackboneOverride.original.isEqual( a.toJSON(), b.toJSON() );
    }

    return custom.namespace.BackboneOverride.original.isEqual( a, b );
  };

Also as an aside, if there's a discussion thread for suggestions on how to implement service layers in Backbone for dealing with complex APIs, I'd love to know about it :)

This is an interesting idea, but the particular implementation falls a little short...
The override here is still per-attribute — while for your use case, it seems like the desirable thing would be to have the override method comparing two complete models — so that you can short-circuit and bail out quickly for potentially complex cases. Basically — encompassing the entire for attr in attrs loop, instead of overriding within it.
Closing this one, but feel free to try again...


Use constructor-style for NoopSubmitter

Inspired by #809
This change can be separated from the rest of the lib work, but using a constructor-style to creating the noopSubmitter objects.

/ok-to-test

I don't think the linter will allow us to switch to this style of coding since for current use cases we are never setting a reason, meaning the linter wants us to remove that parameters from the method signature completely.

hi @sebrandon1, sorry for the failed job, we got an issue with the folder permissions in Dallas, but it is now fixed. Everything should work once your branch is rebased.

Fully rebased on top of the lib changes from yesterday.  Thanks for the reviews!


#187 2.16 language issues

Closing #187

Coverage remained the same at 100.0% when pulling 90bcfdc02f6255dad8c631b89d7130d7ac50c7b0 on #187_2.16_Language_Issues into d9add9e4403ba0786d7e2db939204105dacdcea6 on dev.

Are you sure that this only has a line diff of +2-1? The commits suggest something else...

https://github.com/hpi-swt2/workshop-portal/pull/229 and https://github.com/hpi-swt2/workshop-portal/pull/234 already fixed a bunch of language issues.

 I don't see its diff in the final one. Or do I miss something here?

 I don't see its diff in the final one. Or do I miss something here?

As I said, this has already been included in one of the other pull requests 😃

Coverage remained the same at 100.0% when pulling 57ad6a46978f95b8f3bcf28972d638ae5e07ffa2 on #187_2.16_Language_Issues into 8a99b8d6c7d93d0e04a3d92d87b9c6f5251e16de on dev.


accessLogging filter and match mode at same time

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[x] This is not a question about how to use Istio

Bug Description
I like to exclude from the proxy logs all requests originating from the pod, as well as all requests from Prometheus to pod.
I use Telemetry API to set up logs. Unfortunately only one rule always works.
My yaml based on documentation:
apiVersion: telemetry.istio.io/v1
kind: Telemetry
metadata:
  name: exclude-outgoing
  namespace: default
spec:
  selector:
    matchLabels:
      app: manager
  accessLogging:
  - providers:
    - name: stdout-json
    match:
      mode: CLIENT
    disabled: true
---
apiVersion: telemetry.istio.io/v1
kind: Telemetry
metadata:
  name: exclude-prometheus
  namespace: default
spec:
  selector:
    matchLabels:
      app: manager
  accessLogging:
  - providers:
    - name: stdout-json
    filter:
      expression: '!has(request.useragent) || !(request.useragent.startsWith("Prometheus"))'

Version
client version: 1.21.2
control plane version: 1.24.0
data plane version: 1.24.0 (15 proxies)

Additional Information
No response

accroding https://istio.io/latest/docs/tasks/observability/telemetry/#scope-inheritance-and-overrides
if you merge into one resource, it will be fine.

Thanks for the quick reply! After applying the combined manifest, no logs are written to stdout.

disabled: true means it will disable for everything. You need 1 Telemetry object with 2 clauses:
apiVersion: telemetry.istio.io/v1
kind: Telemetry
metadata:
  name: exclude-outgoing
  namespace: default
spec:
  selector:
    matchLabels:
      app: echo
  accessLogging:
  - providers:
    - name: envoy
    match:
      mode: CLIENT
    disabled: true
  - providers:
    - name: envoy
    match:
      mode: SERVER
    filter:
      expression: '!has(request.useragent) || !(request.useragent.startsWith("Prometheus"))'

@howardjohn Thank you very much, it works now. I tried a similar configuration, but specifying match.mode: SERVER was unclear.


[svt] fix issue #22897 : change process of video id extraction

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
This PR fixes issue #22897 by changing the process of extracting video ids.

I would really appreciate if I could get answers to my questions, because I still have no idea how I should modify the code.


@ofw5rz

@ofw5rz
Originally posted by @ofw5rz in https://github.com/privacycg/storage-access/issues/205#issuecomment-2252484603

spam


docs.javadsl.MqttFlowTest: bidirectional connection may leak actors

It seems to be specifically establishClientBidirectionalConnectionAndSubscribeToATopic and establishServerBidirectionalConnectionAndSubscribeToATopic

(let's close this for now in case #736 was it, and re-open when it turns out it wasn't)

https://github.com/apache/pekko-connectors/actions/runs/9892582296/job/27325614127


Correction for raw affiliation E. Cairns, PhD, Department of Microbiology and Immunology, and Department of Medicine, Division of Rheumatology, Western University.

Correction needed for raw affiliation E. Cairns, PhD, Department of Microbiology and Immunology, and Department of Medicine, Division of Rheumatology, Western University.
raw_affiliation_name: E. Cairns, PhD, Department of Microbiology and Immunology, and Department of Medicine, Division of Rheumatology, Western University.
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4318824220
contact: fac515ed9c2ce205303009719d287f15:2e260e36a5f40cd8 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Weird output for some videos

Hey @prajwalkr ,
I have attached the video used for inferencing the LipGan models. I ran the following command
!python batch_inference.py --checkpoint_path logs/lipgan_residual_mel.h5 --model residual  --pad 0 0 0 0 --face "/content/male.mp4" --fps 29.970 --audio "/content/male.wav" --results_dir "/content/"
Here are the videos used. I don't think FPS is the problem here, as the model seems to work for variable FPS as well.
videos.zip
/content/LipGAN
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/usr/local/lib/python3.6/dist-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
/usr/local/lib/python3.6/dist-packages/tensorboard/compat/tensorflow_stub/dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/usr/local/lib/python3.6/dist-packages/tensorboard/compat/tensorflow_stub/dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/usr/local/lib/python3.6/dist-packages/tensorboard/compat/tensorflow_stub/dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/usr/local/lib/python3.6/dist-packages/tensorboard/compat/tensorflow_stub/dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/usr/local/lib/python3.6/dist-packages/tensorboard/compat/tensorflow_stub/dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/usr/local/lib/python3.6/dist-packages/tensorboard/compat/tensorflow_stub/dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
Using TensorFlow backend.
 We have updated the message to be more clearer in both branches of the repo.


New nmea0183 parser

This PR updates provider/nmea0183-signalk.js to the new 2.0.2 release of the parser.

@tkurki please review, and merge asap if you see nothing. The new parser has been released already!

The Travis check has failed because the PR was submitted before 2.0.2 of parser had finished uploading to NPM. Any other way of triggering that check again without submitting a new commit?

@fabdrol I restarted the build...

Same issue. I get the same locally. You can go to the build "Details" and click "Restart Build" to try again when it's ready.

Hmm, apparently 2.0.2 didn’t get published; I’ll double check and try that again

Fixed.

The parser is not emitting nmea0183 events, needed for nmea0183 output over tcp and relaying to serial ports.
https://github.com/SignalK/signalk-server-node/blob/40cb6a14802f7ce4c3cd3a58f7217f6d0b5417cf/providers/nmea0183-signalk.js#L28-L36

@tkurki nmea0183 event was overlooked, fixed in https://github.com/SignalK/signalk-parser-nmea0183/pull/95

@fabdrol are you following this through? Two open pull requests at https://github.com/SignalK/signalk-parser-nmea0183/pulls

@tkurki I added the example and updated the configuration files, plus some small optimisations to the provider. I'm in favour of merging, you concur?

You need to reformat with prettier-standard per #311 and please squash the commit history, but other than that no objections.

Doing it.

Formatted & squashed.

One minor thing caught my eye: why are we ignoring errors in this.parser.parse(${chunk.trim()}\n).catch(() => {})?

@joabakk @fabdrol I am worried. Literally the first sentence that I happen to look into in more detail with the new parser does not work for my data: https://github.com/SignalK/signalk-parser-nmea0183/pull/98.
It appears you have changed not just the parser infrastructure but also the logic for individual sentences. In this case you have added cross field checks so that if there is no data in a certain field the whole sentence is silently ignored, even if there would be valid data in another field.
Do you have any idea how many changes of this type you've done in the rewrite?
Is there an easy way to get log messages for sentences that are ignored?

I see now that there are numerous ways to check for empty sentences in the hooks, and this specific one seems wrong. We should stick to something like a standard. I like the looks of this one: https://github.com/SignalK/signalk-parser-nmea0183/blob/master/hooks/DSC.js#L71-L80. It is probably easier to copy for new hooks.
Apart from the empty sentence tests, we have not changed the logic of the sentences to my knowledge. The one exception being ROT, which used to have hard coded engine

There are other problems:

gnss@GGA uses incorrect paths
position@GGA should be object valued

There does not seems to be any schema validation code in the tests 😢 😢 😢


[BUG] Voicemeeter Plugin errors in Macro Deck 2.11.0-dev

Summary
If VM Plugin is loaded in Plugin API version 34, it throws errors recursively. It does not crash Macro Deck, though.
Screen record

Logs
2022-06-14.log
Versions
Macro Deck 1.11.0-dev
VM Plugin 1.1.1
Windows 11 22000.708

update: Actions does not work!


Create additional info blocks

You can make your resume less official by adding more entertaining info, like your hobbies and interest, or what do you like, some interactive content or joke, easter egg, etc.

Additional information added in the index.html


Throttling how much data is sent or setting a points time interval?

Hi I've been using Overland for a bit for tracking flying gliders. The problem is the amount of data being sent to our servers and app, it would be good to reduce the number of points to one every 10 to 15 seconds. Currently it's doing 1 point per second.
"desired accuracy" is set to "best" which seems like the only control possible, but reading Apple's docs doesn't seem like the same thing i.e. it defines the required accuracy of a single point, not how often they happen? (I will test this more)
I noticed BTraced does have an option to set the interval between points, so it must be possible? I can imagine you can receive more GPS data on the device than is actually processed and sent to the server for example? i.e. some sort of throttle?

The controls Apple gives you don't provide any way to specify time interval between points. Like you found, "desired accuracy" will definitely affect how often data is collected. The idea is if your desired accuracy is 100 meters then you'd get a point only if the phone has moved about 100 meters. Of course it's nowhere near this precise in practice, in both directions.
I could definitely add another option in Overland which effectively discards any data received more often than X. It wouldn't affect battery life at all since iOS would still be delivering more frequent data to the app, but it would prevent the app from logging a point per second. (Actually the app already has this filter, it's just hard coded to 1 second, because believe it or not sometimes iOS sends data more often than that.)

Hi just following up on this, great to see it is in the todo list.
Yes what you suggested would be perfect, discard any data received more often than X. I've been playing around building my own app now that BTraced is no longer available to download on iOS, and that's what I'm doing. But would be great for people who want to use Overland with my tracking system, or on Android. I should deal with too much data on the server end too, but better to not transmit more data than needed in the first place! You can see what we're using it for here if you're interested:
http://gliding.net.nz/tracking
Cheers

Ok, this is in the app and will go out in the next App Store update!
Please note that this will not have a dramatic effect on battery life, since the location data will already have been sent to the app by the time the app decides to discard it. It should only be used if you want to reduce the overall amount of data sent to the server.

Legend!
PS. PureTrack isn't just for aircraft, you can use it to track anything. People also use it for boats, I have my van on it etc.
Cheers for the work


Add testing on newer versions of DRF and Django

This library hasn't changed much and still appears to be supported in newer versions of Django REST framework, but it's difficult to verify because the test matrix stops at DRF 3.1. This updates the test matrix for newer versions of DRF.
Changes:

Added testing for DRF versions up to DRF 3.8
Added testing for Django versions up to Django 2.0
Reorganized testing matrix to only test Python and Django versions that are supported by the DRF versions

This maintains testing and support for the existing DRF and Django combinations, since no code changes were necessary to support newer combinations.

@kevin-brown thank you so much for this ✨


Bug: Currency sub-menu selector not updating after changing currency

When a user selects a currency from the currency sub-menu modal, the currency symbol selector doesn’t immediately change until the menu modal is re-opened or the window is refreshed.
How to replicate: Press “Currency” to enter the currency sub-menu, select a different currency. Press “Currency” again to go to the currency sub-menu. The latest selected currency is still the previous one.
Example: Selecting two different currencies doesn’t update the chosen one in the selector.
https://github.com/bancorprotocol/carbon-app/assets/66181828/759e5f7a-670e-4ac7-b710-cd1d1b59da4d

@Murad544 is looking into this


golang version in makefile and jenkins are not locked together

This is more of an artifact of docker than jenkins.
in docker image naming, 1.8 is 1.8.*, so it is somewhat nebulous unless you watch which exact image the build uses, and in jenkins it is the literal '1.8' value, to get that exact version.
I don't think it matters so much, but I wanted to write it down and point out existing behavior.
Not sure if there is a way to wildcard the patch version or if we would want to.

/label prow


Introduce a license finding score

Please have a look at the individual commit messages for the details.

Note that FossID does not seem to have the concept of a "score" to parse for.

Adding a test for the score to AbstractScannerFunTest would be nice.

I'll look into that separately as that requires some refactoring.

Adding a test for the score to AbstractScannerFunTest would be nice.

I'll look into that separately as that requires some refactoring.

See https://github.com/oss-review-toolkit/ort/pull/5133.


fixing information about dev contrib

Fixing some incorrect information about the release branches. Mainly, adding a future variable that will point to the correct dev-x.xx branch.
TODO: If we agree this solution is acceptable, @VineethReddy02 will need to include the "future" variable update in the config.toml as part of the sig-docs release cycle.
Thanks to @kbhawkey's idea, there is no need to add an extra variable to manage as it is all parsed in the skew.html shortcode.
Fixes: https://kubernetes.io/docs/contribute/new-content/new-features/#for-developers-or-other-sig-members

Nice approach

/lgtm

Addressed nits, can be merged after review / CI. Thanks!

/hold
I want to think about this more... I would love to use this as part of resolving #14307
The current issue is: Once this merges and gets pushed to older versions (release-1.13 -> 1.17), it will no longer be nextMinorVersion. It would be "this (old) version + 1."
Thoughts?

@jimangel , for my own information, is there a k8s doc that describes versioning? For example,
under what circumstances will the major version move to 2 (minor version 0)?
The next (minor) version is relative to the version (not necessarily the minor version assoc with the latest version). Also, the minor version is a component of the version, ..

Funny you ask! Essentially no... https://github.com/kubernetes/sig-release/tree/master/release-team#during-major-releases
I would imagine that getting all of the APIs to GA would be a big part of that, but that's me speculating.

👋 @jimangel, Is this PR still in progress?

My reluctance to merge this was because, at some point, all releases will have a latest and a nextMinorVersion after latest. Not a huge impact to my "start contributing" document change, but somewhat strange for the skew documents I mentioned (if you're on a v1.14 docs page and the skew document is referencing 1.19; that's weird).
Traditionally, older releases were "cut-off" from changes that were not security related or of MAJOR impact.
After further review,  even if we keep the nextMinorVersion current throughout all releases and the impact is that all release branches share the same skew document, I can't see a negative. As it is today, the skew document is incredibly out of date and it has had no impact or distaste.
Leaving this PR to be "as-is" and we can tweak as we see fit. Ready to merge with approval.
@VineethReddy02 will need to update the Docs release handbook with this change too.
/hold cancel

@kbhawkey this one is good to go if everyone is happy with the wording.

@jimangel I think you will now need to rebase this

Yes, you will need to rebase. @jimangel would you have the time for that?

Hi @jimangel ,
The changes look good (even after a lot of questions (sorry!)).
Would you have time to rebase?
Thanks!

/hold
@sftim @kbhawkey I rebased :smile: but I really want to incorporate a change that fixes ALL version pages:

https://kubernetes.io/docs/contribute/start/#choose-which-git-branch-to-use
https://kubernetes.io/docs/setup/release/version-skew-policy
Potentially a new release page that compares to what https://en.wikipedia.org/wiki/Kubernetes#Release_Versions has

We can merge this as is if we want, but I think we need a programmatic way to reference each version (n, n+1, n-1) and have an approach that deprecates nicely for each release.
Can either of you think of the best way to reference n-1 (for the skew policy)? We have the variable set in config.toml (params.versions).
Thoughts?

We can merge this as is if we want, but I think we need a programmatic way to reference each version (n, n+1, n-1) and have an approach that deprecates nicely for each release.
Can either of you think of the best way to reference n-1 (for the skew policy)? We have the variable set in config.toml (params.versions).
Thoughts?

@jimangel , If I understand correctly, you are looking for a way to use a Hugo template or shortcode to express the semantic versioning in the skew and contrib docs?
Currently, only the minor and patch versions need to change and every version string published in the docs is based off of the latest field (from cofig.toml). Using a shortcode helps to maintain the versioning info in the docs. You don't want to update config.toml every time a minor or patch version changes.
You could split (or use a reg. expression to tease out the version info) latest string and use the Hugo (go) Math functions (https://gohugo.io/functions/math/), to create two new strings that contain the prev and next for the release version, n+1, n-1.
In the simplest case, you could create two templates (shortcodes?):
latest-plus-one (or some number)
latest-minus-one
Is this what you are thinking?

@jimangel , If I understand correctly, you are looking for a way to use a Hugo template or shortcode to express the semantic versioning in the skew and contrib docs?

After thinking about this, I we have two problems and I'm on the fence how this PR solves Problem 1.

Problem 1:
Fix contrib docs and skew docs with variables.
This PR adds n+1 and can be used to fix our contrib docs and, if we had a way to call n-1 (maybe another shortcode or math as you mention), could fix skew too.
In today's case, those variables needed would be: 1.19, 1.18, 1.17

Problem 2:
Creating a release page that is up to date with our releases semantic versioning.
Something very similar to:

https://wiki.ubuntu.com/Releases
https://www.kernel.org/category/releases.html
https://en.wikipedia.org/wiki/Kubernetes#Release_Versions

You don't want to update config.toml every time a minor or patch version changes.

 But I actually was thinking of updating config.toml for each patch version 😅. At some point this would be automated, but until then I could work with the patch release team to open an issue on sig-docs for a fix each release (good first issue!). The patch releases are fairly consistent and scheduled: https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md#timelines unless there's a security / CVE quick patch.
This is where I am lost...
We currently have each minor or patch version in config.toml under fullversion: (https://github.com/kubernetes/website/blob/master/config.toml#L98-L131) we just don't do the best job at updating it.
Any thoughts on how we could use those variables in a table? If it's not simple, do you think it would be worth creating it's own block of variables for this use case?
var1: 1.18.x
var2: 1.17.x
var3: 1.16.x

We only need 3 since the k8s community only supports 3 releases, after that, we can convert the variable to text after the "last release."
Originally I was getting bent on the complexities of the release cycle (ie: how does it impact previous release docs) but I think we just wrap the old pages in a shortcode that says "look at master release doc."

You could split (or use a reg. expression to tease out the version info) latest string and use the Hugo (go) Math functions (https://gohugo.io/functions/math/), to create two new strings that contain the prev and next for the release version, n+1, n-1.

If you have a suggestion for getting n-1 to solve Problem 1, This PR would be good to merge since it solves contrib and skew.
Problem 2 can be another issue / PR - I just wanted to capture my thoughts here. Many thanks @kbhawkey!

@jimangel ,
re: Problem 2, I see the release/version tables from the links. Couple of questions:

Where would you get most of the information for the table (release name, release date, link to release notes)? You want to use the items in, params.versions and call a template or shortcode to populate a Markdown file with a table.
Would this doc publish from the website?

Here is a shortcode to get the next or prev version based off of latest.
{{- $latestVersion := site.Params.latest -}}
{{- $latestVersion := (replace $latestVersion "v" "") }}
{{- $nextMinorVersion := 0 -}}
{{- $prevMinorVersion := 0 -}}

{{- $versionArray := split $latestVersion "." -}}
{{- $minorVersion := int (index $versionArray 1) -}}
{{- $nextMinorVersion := add $minorVersion 1 -}}
{{- $prevMinorVersion := sub $minorVersion 1 -}}
{{- $latestVersion := $nextMinorVersion -}}
{{- $nextMinorVersion := printf "%s.%d" (index $versionArray 0) $nextMinorVersion -}}
{{- $nextMinorVersion -}}

Could update the shortcode to take an arg (next or prev).

This has been open so long the page was re-written :sweat_smile: I think there's still some work to do on the content, but the shortcode works and I can use this solution to fix the skew page as well.
Ready to merge after review. @kbhawkey @sftim @tengqm
/hold cancel

Aside for code spelunkers: this approach might need to change when Kubernetes has two next releases due: an upcoming minor version release and an upcoming major version release.

/sig release

Page preview:
https://deploy-preview-18173--kubernetes-io-master-staging.netlify.com/docs/contribute/new-content/new-features/#for-developers-or-other-sig-members
Thanks @jimangel
/approve


Update to Ace 1.2.3 and Using Ace Sessions

Update to be compatible with Ace 1.2+ and to use Ace sessions to better enable multi-document editing in the future.
This is still a bit of a work in progress, but I thought I'd open it early for feedback and to gauge interest.
Goals:

[x] Update to be compatible with latest Ace
[x] Use ace edit sessions rather than binding one document to the whole editor (this will make switching documents while maintaining sessions easier)
[ ] Update the bundled Ace library
[ ] Currently disabled "readOnly" mode because it's not per session but there should be a way to get it back if we need to

Bonus Goals:

Use a single websocket rather than destroying and recreating the websocket every document change
Communicate only over the websocket rather than out of band http requests
Preload documents and track OT for all documents so clients can experience instantaneous document switching
Improve user document and cursor tracking so that it is lower latency but also less chatty when the cursor hasn't changed

The bonus goals are ultimately the direction I'd like to go, but I understand that there are trade-offs involved and won't be offended if there is no interest. I figured I'd ask early! At least the Ace updates and switiching to using Ace sessions should provide some more flexibility.

Hey @STRd6, looks great! The session API seems cleaner so I'd like to add this in. Those bonus goals seem sensible, I'd also be in favor of shaking up the API to be more efficient.

Cool, glad to hear the positive support. I'll be poking away at this over the next couple of weeks and try to keep the PR up to date.

Hey @STRd6, I've made a few major changes since this pull request was opened. I've temporarily switched to CodeMirror as the editor of choice since I cannot currently get surrogate pair characters to work correctly with ACE. I've also done a major rework of the websockets API so that client to client coms can be simplified, including lazy reporting of cursor positions (only when it changes or new clients connect).
I've implemented the API such that we could have multiple subscriptions on the same websocket in the future without breaking anything. It would still require some minor client and server updates but the coms between them should stay mostly the same.
I'm leaving it as is for now, but my intention would be to revisit ACE if the UTF-16 limitations can be fixed, then have another pass at this. I'll close this pull request for now but just wanted to say thank you very much as I did use this branch for testing the newer ACE version.

Cool, thanks for looping back around, I've run out of time to continue on this, but I'm glad it was of some use :)


🐛 [Bug]: A few demo interface breaks in the mobile resolution

Describe the bug
These demos are breaking in a smaller resolution.

https://webapis-playground.vercel.app/demos/picture-in-picture
https://webapis-playground.vercel.app/demos/filesystem-api
https://webapis-playground.vercel.app/demos/broadcast-channel
https://webapis-playground.vercel.app/demos/vibration
https://webapis-playground.vercel.app/demos/image-capture
Kindly check all other demos also

Expected behavior
The UI shouldn't break in responsive mode.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

I AM WORKING ONNNN THISSSSSS!!!
PLEASEEEEE DOOOOOO NOAAAAAAT PICCCKKKK THISSSSSSSSSS ONEEEEEE!
jk

I'm working on this issue. To demonstrate to my stream on twitch & YouTube about how to contribute to GitHub repositories in Hacktoberfest

there is a issue

I AM WORKING ONNNN THISSSSSS!!! PLEASEEEEE DOOOOOO NOAAAAAAT PICCCKKKK THISSSSSSSSSS ONEEEEEE! jk

You comedy Me

I AM WORKING ONNNN THISSSSSS!!!
PLEASEEEEE DOOOOOO NOAAAAAAT PICCCKKKK THISSSSSSSSSS ONEEEEEE!
jk

GO FOR ITTTTTTT


Working example for Vue-Remark including markdown and Vue components?

I'm having trouble getting markdown included from another markdown template to work properly. The docs suggests this should work. Is there any working example of this case?
---
title: A cool title
excerpt: Lorem Ipsum is simply dummy text.
---
// Import any Vue Component. Even other .md files!
import YouTube from '~/components/YouTube.vue'
import AboutUs from '~/sections/AboutUs.md'

// Import any JSON if you need data.
import data from '~/data/youtube.json'

// Use front-matter fields anywhere.
# {{ $frontmatter.title }}
> {{ $frontmatter.excerpt }}

// Use your imported Vue Components.
<YouTube :id="data.id" />
<AboutUs />

Isn't it great? 🥳

I have no issue with this -- you may want to check your config and that you have @gridsome/vue-remark properly installed.

Thanks, I know there is a configuration issue. I'm looking for a good example to debug this.

What you have above is literally a good example. It works.

How is that a good example when you need configuration as you mention above?

There is a full example outlined in the plugin documentation. You have to add the settings in gridsome.config.js and the <VueRemarkContent /> component in the corresponding template.

Closing since as-is, the request is already fulfilled.  @J-Rojas if you have a specific error or something, you can start a new issue.

@cco3 The simple request is to add a full working of Vue-Remark example to the examples folder with configuration.

Which examples directory are you referring to?

Sorry, didn't mean the "examples" directory - which is a common pattern in other projects. I meant having an example in the starter projects mentioned on the Gridsome.org site. I didn't see one that uses this plugin. If there is one, would love a link to it.


Feature Request: Shared/Scoped State

As already proposed on discord, we see many good point to have something like shared state or state that is bound to a specific identifier. The use cases reach from user scope for authentication/settings over chat groups or collaborative list views to news feeds and on-the-fly application settings.
Just to illustrate the idea
class AppState(rx.State):
  @rx.var
  def user_id(self) -> UUID:
     ...
   ...

@rx.scope(var=AppState.user_id)
class UserState(AppState):
  mySettings: ...

@rx.scope(var=AppState.group_id)
class ListState(AppState):
  @rx.cached_var
  def elements(self):
    with rx.session() as session:
      return load_objects_with_group_id(session, AppState.group_id)

# Maybe inheritance from AppState is not needed anymore #2678

From my current understanding of the framework I see e.g. this implementation strategy:

Add a scoped_tokenproperty to Event, that calculates from the scope-var (i.e. AppState.user_id or AppState.group_id in above examples).
When also the StateManagerMemory implements the same sharding mechanism as StateManagerRedis no further changes have to be made here.
In App.process the resulting events have to be sent to socket.io-rooms.
Socket room management has to be done on changes to the scope-var.
On connect and disconnect have to restore the subscriptions to the rooms.
For the case of multiple running app instances redis pubsub has to be implemented, where the scoped-token value can be used as topic name. On events in the subscribed topics those can be sent to the targeted rooms.
Events coming from the frontend need to have the scoped-token set by their respective frontend handlers.

When thinking about it, maybe the current state handling is only a special case, so no @rx.scope means the socket/tab scope. Maybe that is a better way to view this architecturally.
There might be many implications that I haven't thought through in detail, yet. E.g. what about @rx.background in those scoped states.

This could also be described as "Dynamic State". Currently it is not possible to reuse a State multiple times at runtime. All state names/classes must be known at compile time.
Maybe we sould implement a DynamicState (still session-based) and later build a SharedState (spread accross multiple sessions).


[l10n] zhTW refinement

"Rows per rows" should be corrected to "rows per page".

[x] I have followed (at least) the PR section of the contributing guide.

It's a great first pull request on MUI 👌 Thank you for working on it!


Noisy geomorphons

Hei guys
first of all thanks for implementing geomorphon in WTB Core. I wonder just one thing, why is so that geomorphon  output produced with WTB is slightly more noise, than the one produced in GRASS GIS/QGIS?

I am also wondering about what may be a related issue. I am currently comparing the Geomorphon implementations in Whitebox v2.1.0 and GRASS v7.8. I find that the WB "skip" parameter, which seems to be the equivalent of the GRASS "skip" parameter, and which the GRASS docs say "eliminates forms of very small extend, smaller than skip parameter" (which could be seen as noise), does nothing, no matter the value I use with it.

I'm also interested as I'm about to use Geomorphon for a project. I don't have time right now to look into it but here are some references (mainly for myself later):

WhiteboxTools implementation and documentation
GRASS implementation and documentation

Dan Newman, the author of this Whitebox tool has issued an update. It will be available in v2.2 which will be released, not next week, but the week after. The fix is in the code base now.

Such prompt attention, much appreciated. I'll test when the new version is released - thanks!

Tested the Geomorphons tool in OpenCore v2.2 - the "skip" parameter is now working, thanks!
Edge effects are larger, but otherwise the output appears equivalent to Grass' output, at least for my single test case.


Integration is incompatible with Easee-integration (from OEPL 0.4.7.x)

EDIT:
Found out it’s this integration that causes the issue due to it requiring an old version of a common library:
https://github.com/nordicopen/easee_hass
———
Describe the bug
All versions after PR #110 (@jterrace), the integration fails with these errors:
“WebSocketApp.run_forever() got an unexpected keyword argument 'reconnect'”
and
“open_epaper_link WebSocketApp crashed, reconnecting in 30 seconds”
Downgrading to 0.4.6 is the only solution I've found.
Running HASS OS with all latest updates installed. Was a fresh install about 6 months ago.
Any idea what could be causing this, @jterrace?
I was wondering if there could be a different version of the "websocket-client" being installed than what the required version is set to in the manifest.json, but I don't know how to check it (or fix it...).
To Reproduce
For me, just update to a newer version.
@jonasniesner has not been able to reproduce it and no one else has reported the same problem on Discord either...
Expected behavior
No error and a working integration.

The reconnect argument to run_forever was added way back in https://github.com/websocket-client/websocket-client/pull/838 which was included in v1.4.0 - https://github.com/websocket-client/websocket-client/releases/tag/v1.4.0
The manifest.json and requirements.txt file are set to version 1.7.0:

https://github.com/jonasniesner/open_epaper_link_homeassistant/blob/main/custom_components/open_epaper_link/manifest.json#L18
https://github.com/jonasniesner/open_epaper_link_homeassistant/blob/main/requirements.txt#L7

So I'm not sure how you could be on a lower version.

Yeah, I’m not sure if I’m on an older version or not - it was just a thought. Any idea how to check?
Any other idea on why I get that error, if web client is 1.7.0?

I'm not sure, I think you'd have to enter into the docker container somehow to check the module versions. Have you tried fully removing the integration and reinstalling?

Yes, when it fails I remove the integration and download 0.4.6 specifically afterwards.
Perhaps I could add a “logger-warning” that prints the version in one of the integration files. Have to have a look at the web client to see if there’s a method to print out the version that way. :)

One step further:

Not quite sure why it's on 1.0.0 though...

So, I were able to figure out what is pinning websocket-client - it was my EV-charger (Easee)!
A pip freeze did not indicate any version pin.
So I ran an --dry-run of updating the websocket-client and expected it to tell me if there would be any issues - it didn't, so I ran the upgrade:

... on now it tells me I've updated with a dependency conflict! :(
What's the point on the "dry-run"-option then... :(
Guess I'll have to see if the update of the websocket-client now causes issues with my EV-charger before deciding what to do next...

I reverted back to the WebSocket-client 1.0.0, just to be safe…
Also raised an issue on pyeasee to look into moving away from an abandoned dependency (https://github.com/mandrewcito/signalrcore).
https://github.com/nordicopen/pyeasee/issues/90
@jterrace If I do want the “new stuff” in 0.4.7.x, I suppose I could manually replace hub.py with the 0.4.6-version after updating? As far as I can tell, there isn’t any other files that has changed that require a newer websocket-client?

Sure, you could hack hub.py to do that, but the reconnect functionality is pretty important for reliability. I also would strongly recommend not staying on a websocket-client version that's 3 years old.

I have no issues with stability on 0.4.6. :)
I was only thinking of this “hack” until the Easee-integration is updated to not require the old websocket-client. I’m kind of dependent on that integration to function.

Seems to be working now, with new Easee-version:
https://github.com/nordicopen/easee_hass/pull/394


Fix requirements.txt for issue #50

MastodonToTwitter does not work with the latest version of Mastodon.py, this PR updates requirements.txt about that.

@halcy Any chances this could be merged?

yep, sorry for the delay and thank you for the reminder, work got busy and I just sort of forgot. merged.


Where are the application logs on aws?

I'm trying to run my serverpod on AWS with terraform. So far I've made the following modifications to get terraform apply and the github action to work. So far the production database is running and I have connected to it locally and modified it with the definition.sql queries.

modified engine version in database.tf to 16.1 from 14.2 to avoid "Cannot find version 14.2 for postgres" error.
modified aws buckets config according to this post to avoid ACL error - https://github.com/serverpod/serverpod/issues/925#issue-1718549192
modified dart sdk version to 3.0.0 in init-script.sh and github action according to this post https://github.com/serverpod/serverpod/discussions/445#discussioncomment-4333113
changed prod database links to remove the 'private-production' part

I'm still getting a 502 and have found no additional help among the other problems posted from others. I simply want to see the application logs for serverpod so I can debug further, but I'm unfamiliar with AWS or where serverpod is logging.
EDIT: found them /home/ec2user/serverpod.log and serverpod.err, closing.

@jblankenship5 Do you have a working copy of your tf files somewhere? I have been fighting for over two days trying to deploy on aws and hitting wall after wall.
The last one being a connection issue between the EC2 and the database...
I am this close to giving up


allow non-consecutive helices

Allow helix indices to be non-consecutive.
This implies changing the type of DNADesign.helices from List<Helix> to Map<int, Helix>.
This is necessary to allow cadnano designs to be imported while preserving helix indices, since it allows non-consecutive helix indices.
See https://github.com/UC-Davis-molecular-computing/scadnano-python-package/issues/16.

Closed in https://github.com/UC-Davis-molecular-computing/scadnano/pull/172


Add Modulight

Modulight is a light modular framework for Blazor aimed to be low intrusive docs.
It's based on dependency injection, supported javascript, css style sheets lazy loading and it takes advantage of the new features introduced in .NET 5 such as WebAssembly Lazy Loading and Javascript Isolation.
Thanks!

Thanks

Thanks


Update READMEtemplate.md with Structured README reference

Description
Based on @fokusferit suggestion,   here is a request for adding a reference to 'Structured README'.  I'm open to suggestions, in case there is a better way for integration.
Related Issue
None
Motivation and Context
Please see discussion on the same as part of updating Mahout README at feedmereadmes here https://github.com/LappleApple/feedmereadmes/issues/12
How Has This Been Tested?
Preview checked during merge
Screenshots (if appropriate):
NA
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Gr8, thanks!  I'll delete patch branch right away.

Nice work on the Structured README. I edited your PR a bit, fwiw.


Dynamically remove/edit/add table's rows [Not a bug]

Good evening. Newbie at reactstrap i am trying to create a table with editable/removable rows.
i have created the table ,added the rows but i dont know how to make actions with them.
my code so far:
 <Row>
                    <Col>
                        <Button className="float-right" outline color="secondary">Add</Button>
                    </Col>
 </Row>
<Row>

                                ID
                                Manufacturer

                                1
                                 man1

                                    <Button outline color="info">Edit</Button>
                                    <Button outline color="danger">Remove</Button>

                                2
                                man2

                                    <Button outline color="info">Edit</Button>
                                    <Button outline color="danger" >Remove</Button>

</Row>

My questions are:
-can i somehow build all the rows dynamically ? (a for loop parsing a table?)
-can i somehow edit the current row by pressing the button 'Edit' ?
-can i somehow delete the current row by pressing the button 'Remove'?
-can i somehow add  a new row to the table by pressing the button 'Add' ?
Thanks in advance!

@dkati github is not really the place to ask these types of questions. You'll find a much better place is stackoverflow. Github issues are - as the name suggests - directed at issues with the repo/bugs/feature requests etc.
That said, all these things you've asked are definitely possible, though I would say they are more general react questions than reactstrap.

I'm closing this as, like @twgraham said, it's more of a general react question than anything related to reactstrap.
I can give you a push in the right direction with this example: https://stackblitz.com/edit/reactstrap-v5-tyjxxh?file=Example.js


typescript-transform-lit-css : not working with typescript 5.5

I don't know if it's a ts-patch bug or typescript-transform-lit-css.
Typescript 5.4 :
imports are transformed with a lit css tag.
Typescript 5.5 :
nothing change,
import styles from './internal/checkbox-styles.css';

thanks for the issue. with 5.5 out i'm sure I'll be updating my day-job stuff soon enough, and that will likely require investigating further.
Any more information you can provide would be helpful

This is working for me with 5.6 so i'll close for now.
If you have a minimal reproduction repo, please reopen.


adds support for Google Shared drives

Proposing this change to support Google Shared Drives.
I am not sure how to test it before doing a PR.
I manually tested the change on a running OPNsense instance 23.7.7

https://github.com/opnsense/core/commit/29215763026b7a1f4fa33a6d2cdd9c3fade8bed2


when I installed containerd with root user i can't run nerdctl with non-root user in a rootless mode  (fork/exec /opt/cni/bin/bridge: permission denied)

Description
I installed Containerd and CNI as a root user and when i install nerdctl with a user he's not participate in a root group i'm receive this error
nerdctl run hello-world FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2024-04-15T16:02:51+03:00" level=fatal msg="failed to call cni.Setup: plugin type=\"bridge\" failed (add): netplugin failed with no error message: fork/exec /opt/cni/bin/bridge: permission denied" Failed to write to log, write /home/shalea2/.local/share/nerdctl/1935db59/containers/default/7d19f6a0f68a0210719d5d14b631a70738de69af0776f741fd18eb576a7f4588/oci-hook.createRuntime.log: file already closed: unknown
and this is log of install as a rootless mode:
`./containerd-rootless-setuptool.sh install
[INFO] Checking RootlessKit functionality
[INFO] Checking cgroup v2
[WARNING] Enabling cgroup v2 is highly recommended, see https://rootlesscontaine.rs/getting-started/common/cgroup2/
[INFO] Checking overlayfs
[INFO] Requirements are satisfied
[INFO] Creating "/home/shalea2/.config/systemd/user/containerd.service"
[INFO] Starting systemd unit "containerd.service"

systemctl --user start containerd.service
sleep 3
systemctl --user --no-pager --full status containerd.service
● containerd.service - containerd (Rootless)
Loaded: loaded (/home/shalea2/.config/systemd/user/containerd.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2024-04-15 16:15:12 IDT; 3s ago
Main PID: 2972668 (rootlesskit)
CGroup<EMAIL_ADDRESS>├─2972668 rootlesskit --state-dir=/run/user/1022/containerd-rootless --net=slirp4netns --mtu=65520 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --copy-up=/var/lib --propagation=rslave /usr/local/bin/containerd-rootless.sh
├─2972680 /proc/self/exe --state-dir=/run/user/1022/containerd-rootless --net=slirp4netns --mtu=65520 --slirp4netns-sandbox=auto --slirp4netns-seccomp=auto --disable-host-loopback --port-driver=builtin --copy-up=/etc --copy-up=/run --copy-up=/var/lib --propagation=rslave /usr/local/bin/containerd-rootless.sh
├─2972699 slirp4netns --mtu 65520 -r 3 --disable-host-loopback --enable-sandbox --enable-seccomp 2972680 tap0
└─2972707 containerd

Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.910830407+03:00" level=error msg="failed to initialize a tracing processor "otlp"" error="no OpenTelemetry endpoint: skip plugin"
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.910904697+03:00" level=info msg="loading plugin "io.containerd.grpc.v1.cri"..." type=io.containerd.grpc.v1
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911044890+03:00" level=info msg="Start cri plugin with config {PluginConfig:{ContainerdConfig:{Snapshotter:overlayfs DefaultRuntimeName:runc DefaultRuntime:{Type: Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[] PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir: NetworkPluginMaxConfNum:0} UntrustedWorkloadRuntime:{Type: Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[] PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir: NetworkPluginMaxConfNum:0} Runtimes:map[runc:{Type:io.containerd.runc.v2 Path: Engine: PodAnnotations:[] ContainerAnnotations:[] Root: Options:map[BinaryName: CriuImagePath: CriuPath: CriuWorkPath: IoGid:0 IoUid:0 NoNewKeyring:false NoPivotRoot:false Root: ShimCgroup: SystemdCgroup:false] PrivilegedWithoutHostDevices:false BaseRuntimeSpec: NetworkPluginConfDir: NetworkPluginMaxConfNum:0}] NoPivot:false DisableSnapshotAnnotations:true DiscardUnpackedLayers:false IgnoreRdtNotEnabledErrors:false} CniConfig:{NetworkPluginBinDir:/opt/cni/bin NetworkPluginConfDir:/etc/cni/net.d NetworkPluginMaxConfNum:1 NetworkPluginConfTemplate: IPPreference:} Registry:{ConfigPath: Mirrors:map[] Configs:map[] Auths:map[] Headers:map[]} ImageDecryption:{KeyModel:node} DisableTCPService:true StreamServerAddress:<IP_ADDRESS> StreamServerPort:0 StreamIdleTimeout:4h0m0s EnableSelinux:false SelinuxCategoryRange:1024 SandboxImage:registry.k8s.io/pause:3.6 StatsCollectPeriod:10 SystemdCgroup:false EnableTLSStreaming:false X509KeyPairStreaming:{TLSCertFile: TLSKeyFile:} MaxContainerLogLineSize:16384 DisableCgroup:false DisableApparmor:false RestrictOOMScoreAdj:false MaxConcurrentDownloads:3 DisableProcMount:false UnsetSeccompProfile: TolerateMissingHugetlbController:true DisableHugetlbController:true DeviceOwnershipFromSecurityContext:false IgnoreImageDefinedVolumes:false NetNSMountsUnderStateDir:false EnableUnprivilegedPorts:false EnableUnprivilegedICMP:false} ContainerdRootDir:/var/lib/containerd ContainerdEndpoint:/run/containerd/containerd.sock RootDir:/var/lib/containerd/io.containerd.grpc.v1.cri StateDir:/run/containerd/io.containerd.grpc.v1.cri}"
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911107918+03:00" level=info msg="Connect containerd service"
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911170646+03:00" level=info msg="Get image filesystem path "/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs""
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911186696+03:00" level=warning msg="Running containerd in a user namespace typically requires disable_cgroup, disable_apparmor, restrict_oom_score_adj set to be true"
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911623495+03:00" level=warning msg="failed to load plugin io.containerd.grpc.v1.cri" error="failed to create CRI service: failed to create cni conf monitor for default: failed to create cni conf dir=/etc/cni/net.d for watch: mkdir /etc/cni/net.d: permission denied"
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911877722+03:00" level=info msg=serving... address=/run/containerd/containerd.sock.ttrpc
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.911973762+03:00" level=info msg=serving... address=/run/containerd/containerd.sock
Apr 15 16:15:12 magicuser containerd-rootless.sh[2972707]: time="2024-04-15T16:15:12.912005602+03:00" level=info msg="containerd successfully booted in 0.036624s"

systemctl --user enable containerd.service
Created symlink /home/shalea2/.config/systemd/user/default.target.wants/containerd.service → /home/shalea2/.config/systemd/user/containerd.service.
[INFO] Installed "containerd.service" successfully.
[INFO] To control "containerd.service", run: systemctl --user (start|stop|restart) containerd.service
[INFO] To run "containerd.service" on system startup automatically, run: sudo loginctl enable-linger shalea2
[INFO] ------------------------------------------------------------------------------------------
[INFO] Use nerdctl to connect to the rootless containerd.
[INFO] You do NOT need to specify $CONTAINERD_ADDRESS explicitly.`

when i add the user to the root group it pass successfully
Steps to reproduce the issue

Describe the results you received and expected
to install containerd and cni with root and nerdctl in all users as a rootless mode
What version of nerdctl are you using?
nerdctl version
WARN[0000] unable to determine buildctl version: exec: "buildctl": executable file not found in $PATH
Client:
 Version:	v2.0.0-beta.4
 OS/Arch:	linux/amd64
 Git commit:	eb25c21acc3ec49ee4a9ab4e848611726ecaad20
 buildctl:
  Version:

Server:
 containerd:
  Version:	1.6.21
  GitCommit:	3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:	1.1.7
  GitCommit:	v1.1.7-0-g860f061

Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
nerdctl version
Client:
Version:	v1.7.4
OS/Arch:	linux/amd64
Git commit:	7b5f7e0d8f705ed4e54f7040512327e231433366
buildctl:
Version:	v0.13.1
GitCommit:	2ae42e0c0c793d7d66b7a23424af6fd6c2f9c8f3
Server:
containerd:
Version:	1.6.21
GitCommit:	3dce8eb055cbb6872793272b4f20ed16117344f8
runc:
Version:	1.1.7
GitCommit:	v1.1.7-0-g860f061
nerdctl info
Client:
Namespace:	default
Debug Mode:	false
Server:
Server Version: 1.6.21
Storage Driver: overlayfs
Logging Driver: json-file
Cgroup Driver: none
Cgroup Version: 1
Plugins:
Log: fluentd journald json-file syslog
Storage: native overlayfs
Security Options:
apparmor
seccomp
Profile: builtin
rootless
Kernel Version: 5.15.0-97-generic
Operating System: Ubuntu 22.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 96
Total Memory: 503.5GiB
Name: magicuser
ID: 3f55e019-d45e-430b-9327-868d61749cfe
WARNING: Running in rootless-mode without cgroups. To enable cgroups in rootless-mode, you need to boot the system in cgroup v2 mode.

./containerd-rootless-setuptool.sh install => the setup of containerd  should be done in rootless mode

./containerd-rootless-setuptool.sh install => containerd setup Needs to be executed as a non-root user

yap, i run the script from the non-root user.

Make sure that /opt/cni/bin/bridge has +x permission

it has a +x permission.
because the  /opt/cni/bin/bridge is owned by the root user and group. it's cause the error if nerdctl run by user do not part of root group.

if we do a ls -l on  /opt/cni/bin what does it show?w

if we do a ls -l on /opt/cni/bin what does it show?

@israeldahan could you try the above?
Thanks!


Update lightcontrol to 0.4.0

Please update my adapter ioBroker.lightcontrol to version 0.4.0.
This pull request was created by https://www.iobroker.dev c0726ff.

0.4.0 created 16.08.2023
55 user
OK


[NLP] Problem with citoid metadata extraction

Here is an example tweet that the topic extraction raise an error:
('https://twitter.com/mbauwens/status/1779543397528740338', TypeError("'ContentTypeError' object does not support item assignment"))

Full log:
back (most recent call last): File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/evaluation/mulitchain_filter_evaluation.py", line 208, in <module> pred_labels(df=df,config=config) File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/evaluation/mulitchain_filter_evaluation.py", line 54, in pred_labels results = model.batch_process_ref_posts(inputs=inputs,active_list=["keywords", "topics"],batch_size=10) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/shared_functions/parsers/multi_chain_parser.py", line 213, in batch_process_ref_posts md_dict = extract_posts_ref_metadata_dict( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/shared_functions/web_extractors/metadata_extractors.py", line 160, in extract_posts_ref_metadata_dict md_dict = extract_all_metadata_to_dict( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/shared_functions/web_extractors/metadata_extractors.py", line 129, in extract_all_metadata_to_dict md_list = extract_all_metadata_by_type( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/shared_functions/web_extractors/metadata_extractors.py", line 119, in extract_all_metadata_by_type return extract_urls_citoid_metadata(target_urls, max_summary_length) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/shared_functions/web_extractors/metadata_extractors.py", line 101, in extract_urls_citoid_metadata return normalize_citoid_metadata(target_urls, metadatas_raw, max_summary_length) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/shaharorielkagan/sensemakers/nlp/desci_sense/shared_functions/web_extractors/metadata_extractors.py", line 30, in normalize_citoid_metadata metadata["original_url"] = url ~~~~~~~~^^^^^^^^^^^^^^^^ TypeError: 'ContentTypeError' object does not support item assignment

@ShaRefOh  I tried this in the notebook and topics extraction did work - https://github.com/Common-SenseMakers/sensemakers/blob/44177802dbc934a8ddc2fe3ff969a514a4450d6d/nlp/notebooks/multi_chain_parser_example.ipynb
Does that notebook section work for you? (cell 6)

It looks like there is a problem running citoid at scale since there are a small fraction of failures that aren't currently handled properly. Working on a retry functionality now.

@ShaRefOh  I pushed a fix to the nlp-dev branch, can you move there and try it?  You should be able to do the batch code as usual.

@ronentk I tried it and got a different error:
ValidationError                           Traceback (most recent call last)
Cell In[7], line 2
      1 # batch process
----> 2 results = multi_chain_parser.batch_process_ref_posts(inputs,active_list=['topics','keywords'],batch_size=10)

File ~/sensemakers/nlp/notebooks/../desci_sense/shared_functions/parsers/multi_chain_parser.py:259, in MultiChainParser.batch_process_ref_posts(self, inputs, batch_size, active_list)
    257 post_processed_results = []
    258 for post, result, prompts_dict in zip(inputs, results, inst_prompts):
--> 259     post_processed_res = self.post_process_raw_results(
    260         post,
    261         prompts_dict,
    262         result,
    263         md_dict,
    264         self.config.post_process_type,
    265     )
    266     post_processed_results.append(post_processed_res)
    268 logger.debug("Done!")

File ~/sensemakers/nlp/notebooks/../desci_sense/shared_functions/parsers/multi_chain_parser.py:155, in MultiChainParser.post_process_raw_results(self, post, inst_prompt_dict, raw_results, md_dict, post_process_type)
    152     return raw_results
    154 # convert raw outputs to combined format
--> 155 combined_res = post_process_chain_output(
    156     post,
    157     raw_results,
...

ValidationError: 1 validation error for CombinedParserOutput
item_types.1
  Input should be a valid string [type=string_type, input_value=None, input_type=NoneType]
    For further information visit https://errors.pydantic.dev/2.6/v/string_type

There is also many of these:
2024-05-02 10:41:58.981 | ERROR    | desci_sense.shared_functions.web_extractors.citoid:return_default_value:58 - Max retries exceeded. Returning default value.

Hmm @ShaRefOh  can you show me where I can run the script? It would help me debug it faster. Thanks

@ronentk I just pushed a few extra cells to nlp/notebooks/multi_chain_parser_example.ipynb so you can download the dataset and run the parser over it. Look at the last few cells

@ShaRefOh  I pushed two fixes, maybe you can check again?

Great! I rechecked it a few times. It seems to do the job, and no 'default' values are returned! Can you push this into the dev branch?

Great, I'll do it next week with the multi ref feature #61