Fat32 filesystem corruption when using the switch or unplugging the goggles

As per this request, I'm posting again here the findings about the Fat32 formatted SD card being uncleanly unmounted, which lead to the fs to be put permanently in read-only mode.
The original messages are here and there.
Message one:
To add more info on the bug, it seems the problem comes from the SD card being mounted read-only.
At least that's my guess is happening on the goggles, since when I insert the card in my computer (running Linux), I get the following kernel messages:
[65778.322421] usb 3-2: new high-speed USB device number 6 using xhci_hcd
[65778.480975] usb 3-2: New USB device found, idVendor=14cd, idProduct=1212, bcdDevice= 1.00
[65778.480982] usb 3-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[65778.480984] usb 3-2: Product: Mass Storage Device
[65778.480986] usb 3-2: Manufacturer: Generic
[65778.480987] usb 3-2: SerialNumber:<PHONE_NUMBER>99
[65778.481583] usb-storage 3-2:1.0: USB Mass Storage device detected
[65778.481716] scsi host3: usb-storage 3-2:1.0
[65779.494927] scsi 3:0:0:0: Direct-Access     Mass     Storage Device   1.00 PQ: 0 ANSI: 0 CCS
[65779.495230] sd 3:0:0:0: Attached scsi generic sg2 type 0
[65779.724083] sd 3:0:0:0: [sdc] 487325696 512-byte logical blocks: (250 GB/232 GiB)
[65779.724173] sd 3:0:0:0: [sdc] Write Protect is off
[65779.724176] sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
[65779.724260] sd 3:0:0:0: [sdc] No Caching mode page found
[65779.724262] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[65779.725838]  sdc: sdc1 sdc2
[65779.726010] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[65785.108260] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[65799.277625] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277631] FAT-fs (sdc1): Filesystem has been set read-only
[65799.277636] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277638] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277639] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277641] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277642] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277643] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277644] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277645] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[65799.277646] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)

Looks like FAT32 does not like when you switch off or unplug your battery from the goggles, hence creating the usual not properly unmounted error message.
One solution perhaps could be to use a newer filesystem for the SD Card? Either exfat for windows users, or f2fs/ext4/btrfs/xfs/etc. for Linux users?
Message two:
For info, I was able to 'fix' the SD card by running fsck:
# fsck /dev/sdc1
fsck from util-linux 2.38.1
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]? 1
FATs differ but appear to be intact.
 Assuming EOF.
/isp0_0_0_0_ctx_saved.bin
  File size is 40472 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Reclaimed 2 unused clusters (65536 bytes).
Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
1) Remove dirty bit
2) No action
[12?q]? 2
Free cluster summary wrong (1382323 vs. really 1382325)
1) Correct
2) Don't correct
[12?q]? 1

*** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave the
filesystem unmodified:
1) Write changes
2) Leave filesystem unchanged
[12?q]? 1
/dev/sdc1: 87 files, 714313/2096638 clusters

Then I was able to fly 4 batteries and get the first 2 recordings; the last 2 flights were not recorded.
Now when I plug the SD card in my computer, I again see the usual errors:
[95250.360234] scsi host3: usb-storage 3-2:1.0
[95251.377167] scsi 3:0:0:0: Direct-Access     Mass     Storage Device   1.00 PQ: 0 ANSI: 0 CCS
[95251.377404] sd 3:0:0:0: Attached scsi generic sg2 type 0
[95251.662897] sd 3:0:0:0: [sdc] 487325696 512-byte logical blocks: (250 GB/232 GiB)
[95251.662998] sd 3:0:0:0: [sdc] Write Protect is off
[95251.663002] sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
[95251.663090] sd 3:0:0:0: [sdc] No Caching mode page found
[95251.663093] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[95251.664859]  sdc: sdc1 sdc2
[95251.665065] sd 3:0:0:0: [sdc] Attached SCSI removable disk
[95253.976447] FAT-fs (sdc1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[95257.202653] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202659] FAT-fs (sdc1): Filesystem has been set read-only
[95257.202664] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202666] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202667] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202668] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202669] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202670] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202671] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202672] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)
[95257.202673] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 525333)

I made sure I used the goggles switch button each time, instead of unplugging the barrel connector, while I doubt it would change anything.
Somehow, doing this with the HDO2 never lead to read-only SD card; perhaps Fatshark did run an equivalent of fsck on boot?
Last thing; I'm using the beta firmware posted today on discord HDZERO_GOGGLE-<IP_ADDRESS>.bin.

xfs please

The average user wouldn't be able to mount a XFS drive on a mac or windows PC.
Also, F2FS would be logical choice should you go for a file system that is not natively supported by 99% of computers.

xfs please

The average user wouldn't be able to mount a XFS drive on a mac or windows PC. Also, F2FS would be logical choice should you go for a file system that is not natively supported by 99% of computers.

I don't disagree with your premise. It would be great if they supported the use of XFS, I'm not saying make it default.
I.E. if I formatted the card to XFS or F2FS and the goggles would be happy with that. I'm a Linux only user since the year 2000.  I use BTRFS on my workstations but XFS is fast light and rock solid. No need to ever to FS checks. Perhaps F2FS is a good choice since that is the target device for this filesystem, but I trust XFS more and don't care about every last ounce of performance.  The mount command from the googgles potentially only needs the kernel module and some libraries and then can handle any of these filesystems. However, since size matters and special cases have to be made for filesystems like FAT,  it's probably not so simple. I should try formatting with XFS and see if the goggles just work. I've never tried.

It would be great if they supported the use of XFS, I'm not saying make it default.

That.
For all users alike, FAT32 is an abomination.
For windows users (I'm guessing the majority), let's make exfat the default.
For power users, just make the goggle recognize other filesystems (f2fs, xfs, you name it) if they already exists on the SD card. You don't even need to add the format to [f2fs|xfs] option menu, since those users will know how to do that on their own computer.

My Plan for Addressing the Filesystem Corruption Issue
Hello everyone :wave:,
There's been an issue with HDZero's FPV goggles involving filesystem corruption due to power loss. This is particularly troublesome for SD cards which are formatted with FAT32.
The FAT32 file system, while broadly compatible, struggles with sudden power loss. This can lead to data corruption or even render the whole filesystem unusable. ExFAT, while a more modern file system, unfortunately suffers from the same lack of power loss resilience.
To fully address this, hardware modifications would ideally be made to ensure safe shutdowns or power loss recovery. However, that's not possible since the goggles are already in the hands of users.
Techniques like atomic writing or redundancy could be considered. They would provide a safeguard against data corruption, but the filesystem itself would still be vulnerable.
Add a function that restores SD cards when inserted (Low risk improvement)
A potential solution could be for HDZero to implement a function in the firmware that automatically checks and repairs the filesystem when an SD card is inserted. This would involve using existing disk repair tools and could transparently handle minor filesystem corruptions.
Add NTFS Support (Solution)
After reviewing a variety of file systems, I believe NTFS could be a viable option for HDZero's use case. NTFS is a journaled filesystem, which means it maintains a log of transactions. In the event of power loss or sudden disconnection, this log can be used to recover the filesystem.
EXT4 or XFS, though robust and well-suited for Linux environments, aren't natively supported by Windows or MacOS. Given that most end users are likely to be using these systems, we want to avoid adding extra steps for them to access their data.
There's good news! An open-source library providing NTFS read and write capabilities is available. This would enable NTFS support to be incorporated into the firmware.
Steps I am going to take

Driver Integration: The NTFS-3G driver needs to be integrated with your firmware. This involves cross-compiling the driver for your target platform, integrating it with your build system, and testing it thoroughly.

Testing: Extensive testing would be needed to ensure your application behaves correctly with the new file system and to evaluate the performance and stability of the NTFS-3G driver in your specific use case.

In summary, by adding NTFS support and a filesystem check/repair function, HDZero could significantly mitigate the filesystem corruption issue. I will start with the first part, add a function that restores SD cards fat32 partition then I will move to enabling NTFS on my goggles and see how DVR works with the FFPack library. I'm eager to hear your thoughts!

Hit a stopping point right now.
I need to be able to build new OS.bin's so I can test some of the code changes I made.
I need to make sure we have a few packages installed on the OS. dosfstools and ntfs-3g.
So options..

Carl reaches out and allows me to build OS.bin files I can update my goggles for dev testing
Root the goggles myself to install packages... or find out if someone else has a way in to where we can add binaries to the goggles.

Any information would help me continue my work fixing the fat32 corruption issues.

I understand the new wifi module allows ssh. I am not sure as root but it does have a running ssh client and a user/password that allows management of the movies files. You could probably check the dependencies like that.  I haven't looked much into setting up the developer environment mostly because I realize it requires some special hardware that I don't have in order to connect to the goggles. I have ordered the new pcb board about a month ago but I'm not going to see it for a while.

Try my PR to see if it resolves the issue https://github.com/hd-zero/hdzero-goggle/pull/269
Full bin install required

xfs please

The average user wouldn't be able to mount a XFS drive on a mac or windows PC. Also, F2FS would be logical choice should you go for a file system that is not natively supported by 99% of computers.

I don't disagree with your premise. It would be great if they supported the use of XFS, I'm not saying make it default.
I.E. if I formatted the card to XFS or F2FS and the goggles would be happy with that. I'm a Linux only user since the year 2000. I use BTRFS on my workstations but XFS is fast light and rock solid. No need to ever to FS checks. Perhaps F2FS is a good choice since that is the target device for this filesystem, but I trust XFS more and don't care about every last ounce of performance.  The mount command from the googgles potentially only needs the kernel module and some libraries and then can handle any of these filesystems. However, since size matters and special cases have to be made for filesystems like FAT, it's probably not so simple. I should try formatting with XFS and see if the goggles just work. I've never tried.

nobody in their right mind would use this as a filesystem unless you're an advanced linux user, it's so niche that a significant quantity of linux users don't even know what XFS is
Exfat is the filesystem to go with, but that comes with its own problems. It can be easily corrupted and only has a single copy of the FAT therefore once it becomes corrupted, it can't be easily fixed. Fat32 is more resilient than exfat in my experience. However this issue with being unable to mount filesystems, it's an incredibly annoying issue.

Well, I'll refer to myself; exfat is in my humble opinion the default to use, since I assume most users are using Windows.
However I fail to see why preventing user choices is still a thing in 2023 @christhomas ; if a user is comfortable using xfs, let it.
I'm pretty sure adding a few linux filesystem as a kernel module won't add too much in term of size, and as module they won't use any more memory.

Advance Linux users are the only ones in their right minds ;). To be
able to mount an xfs filesystem from a Linux OS is not a far stretch. It's
not a big deal to me. As of now fat is working fine with the latest
patches. However, a robust filesystem like xfs is the icing on the cake.
I have not owned windows since I bought the only laptop I ever owned, back
in 1999 windows NT, and I replaced that with Linux. Linux == the majority
of operating systems on the Internet. So to think running Linux is radical
is silly. The mindsets to support windows users only, and on occasion Mac,
it's the foundation of the problem. The primary attraction to me of HDZero
was the Open source nature and Linux OS the goggles would be and are based
on. Of_course I don't want to be using a 1980s DOS based filesystem.
Many RC hobbyist run Linux. To support XFS on googles, all that has to be
done is include the Linux module, it's light, and it's free. I'm not
asking that the goggles format function use xfs, just simply allow
mounting of the filesystem. Of course, because of the nature of FAT, and
the extra things needed to do to support it, means that there probably has
to be extra logic in the maintenance scripts, like, don't try repairing a
no DOS base filesystem. I understand that it's not completely free and
simple.
I don't much care to fight on this, that was my only two cents months ago
when the question was raised. I wasn't looking to be insulted just for
offering my opinion. Tell me I am not in my right mind. I'm not going to
argue about who is more rational. XFS is a good, robust, fast, light, no
frills, no hassle filesystem. It just takes care of itself without the
need to do filesystem checks or any maintenance at all. It doesn't get
more simple than that.

RoGoR

On Wed, August 2, 2023 7:45 am, Christopher Thomas wrote:

xfs please

The average user wouldn't be able to mount a XFS drive on a mac or
windows PC. Also, F2FS would be logical choice should you go for a
file system that is not natively supported by 99% of computers.

I don't disagree with your premise. It would be great if they supported
the use of XFS, I'm not saying make it default.
I.E. if I formatted the card to XFS or F2FS and the goggles wo

This is has been resolved by PR https://github.com/hd-zero/hdzero-goggle/pull/276

This is has been resolved by PR #276

Indeed the FAT corruption has seen a workaround (while the corruption can and will still occur since it's still FAT), which so far is working ok.
It would be better to stop talking about the mediocre default filesystem here, and add to the existing feature request about it.

xfs please
No consumer linux system supports xfs out of the box.

This has nothing to do with the goggles anymore, and I would like to drop this. However, to be corrected XFS is not at all niche. The most standard Linux filesystem used to be EXT, EXT2, EXT3, and EXT4. But now days not only does every major Linux distribution supports XFS (and has for years), but it's become the default de-facto standard. It's faster lighter and more robust than EXT4 in most every way, and it's simple. There's no reason to choose ext4 over XFS. Personally, for years, I use BTRFS in most cases. It has so many features, like ZFS. However, BTRFS is not appropriate, it's heavy, complicated, and slow. XFS is not at all exciting, it's just an extremely light, fast, stable, and simple journaling self repairing file system. Nothing prevents it from being used on windows, mac, or any other OS, it's open source and free to the public. It's not a niche and it's not controversial either. XFS is most notably good with large files, such as video files.


[Bug] Request Failed

There is a bug in animity (universal version).The bug does not let me access my profile,when I try to go to my profile it says request failed with status code 400.
To Reproduce
Steps to reproduce the behavior:

Go to 'animity'
Click on 'profile'
See error

Screenshots
Screenshot_20240729-151018.png
Smartphone (please complete the following information):

Device: [Samsung galaxy a03 core]
OS: [Android 13]
Version [v1.2.7-universal]

Kl3jvi it is working but when I sign in with my anilist account it logs in.But when I am about to watch a anime it kicks me back to the anime details.When I go to the profile it says (request failed with status code 400)

@ParsonsPT I will check it later this week as I have been busy with work


[ADDED] consumer add when prompting for subject filter(s) can parse the user input as a comma or space separated list of subject filters

Added to consumer add: when prompting for subject filter(s) can parse the user input as a comma or space separated list of subject filters.

This is probably not [ADDED] but rather whatever we use to indicate fixed.  Personally I dont really want those prefixes in this repo they dont add much value

Ok, just in the habit of using those prefixes because that's how they want it for the client libraries, but won't use them for this repo from now on.


[KTLN-148] Add examples for Kotlin Flow

Fails due to some "jee-kotlin". I have no idea what it is.


Renaming + removing dev dirs

Change Summary
Rename dev-v2 to dev and remove dev-v1 directory.

[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Alright, fixed the merge conflict 😄


Feature/create wallet

Summary
Implement Create Wallet module, and add Welcome Screen so User can login back.
Checklist

[X] I removed all commented or unnecessary code.
[X] Provide the screenshots due to UI changed or bug fixed
[X] My code has covered these test cases (please list down your tested cases):
Update unit test for Create Wallet actions
Update unit test for Create Wallet selectors
Update unit test for custom hook useCreateUser

New UI screenshots:
Create new wallet

Keyphrase list screen

Double check words screen

Password entering screen

Welcome Back screen

More unit tests coming soon

Uncaught TypeError: Cannot destructure property 'publicKey' of 'cacheConnectedAccount' as it is undefined.
    at WithAccount (WithAccount.jsx:9:22)
    at renderWithHooks (react-dom.development.js:14985:18)
    at mountIndeterminateComponent (react-dom.development.js:17811:13)
    at beginWork (react-dom.development.js:19049:16)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:16)
    at invokeGuardedCallback (react-dom.development.js:4056:31)
    at beginWork$1 (react-dom.development.js:23964:7)
    at performUnitOfWork (react-dom.development.js:22779:12)
    at workLoopSync (react-dom.development.js:22707:5)

hi @duc-q , I met this error when loading unpack extension form this branch. Steps to reproduce:

Run yarn dev-extension-testnet
Load the unpack extension in client/build_extension folder
Disable the production extension
Enable the development extension

Uncaught TypeError: Cannot destructure property 'publicKey' of 'cacheConnectedAccount' as it is undefined.
    at WithAccount (WithAccount.jsx:9:22)
    at renderWithHooks (react-dom.development.js:14985:18)
    at mountIndeterminateComponent (react-dom.development.js:17811:13)
    at beginWork (react-dom.development.js:19049:16)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:16)
    at invokeGuardedCallback (react-dom.development.js:4056:31)
    at beginWork$1 (react-dom.development.js:23964:7)
    at performUnitOfWork (react-dom.development.js:22779:12)
    at workLoopSync (react-dom.development.js:22707:5)

hi @duc-q , I met this error when loading unpack extension form this branch. Steps to reproduce:

Run yarn dev-extension-testnet
Load the unpack extension in client/build_extension folder
Disable the production extension
Enable the development extension

@gaupoit
Please pull the latest source and rerun again, I've resolved the above Bug.

Uncaught TypeError: Cannot destructure property 'publicKey' of 'cacheConnectedAccount' as it is undefined.
    at WithAccount (WithAccount.jsx:9:22)
    at renderWithHooks (react-dom.development.js:14985:18)
    at mountIndeterminateComponent (react-dom.development.js:17811:13)
    at beginWork (react-dom.development.js:19049:16)
    at HTMLUnknownElement.callCallback (react-dom.development.js:3945:14)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:3994:16)
    at invokeGuardedCallback (react-dom.development.js:4056:31)
    at beginWork$1 (react-dom.development.js:23964:7)
    at performUnitOfWork (react-dom.development.js:22779:12)
    at workLoopSync (react-dom.development.js:22707:5)

hi @duc-q , I met this error when loading unpack extension form this branch. Steps to reproduce:

Run yarn dev-extension-testnet
Load the unpack extension in client/build_extension folder
Disable the production extension
Enable the development extension

@gaupoit
Please pull the latest source and rerun again, I've resolved the above Bug.

Many thanks, it has been fixed in 174df2d

hi @duc-q @djhahe , please double check the new created public key. It seems to be invalid public key.

This is my new created public key: 00d18bee34207b6d2ae7789dd5824f0b506a678ec5889bbcadd661911da282b31c
Tested on https://testnet.casperdash.io/dashboard

hi a @duc-q
Verify screen always checks top 4 words? pls help to check

hi @duc-q @djhahe , please double check the new created public key. It seems to be invalid public key.

This is my new created public key: 00d18bee34207b6d2ae7789dd5824f0b506a678ec5889bbcadd661911da282b31c
Tested on https://testnet.casperdash.io/dashboard

we should use getPublicAddress() instead of getPublicKey(). @duc-q  please help to update the function

hi a @duc-q Verify screen always checks top 4 words? pls help to check

Bug resolved, created PR and merged: https://github.com/CasperDash/casperdash-client/pull/106

hi @duc-q @djhahe , please double check the new created public key. It seems to be invalid public key.

This is my new created public key: 00d18bee34207b6d2ae7789dd5824f0b506a678ec5889bbcadd661911da282b31c
Tested on https://testnet.casperdash.io/dashboard

we should use getPublicAddress() instead of getPublicKey(). @duc-q please help to update the function

@gaupoit  @djhahe  Please review and check this PR: https://github.com/CasperDash/casperdash-client/pull/107
Thanks,


Prevent parent scrolling when child is scrolled

I have a container inside a container that both have slimscroll.
Is there a way to prevent parent scrolling while the mouse is scrolling inside the child.
Some option to prevent event bubbling to parent,

hi @mirzinho I am not sure how to solve this, you should somehow call stopPropagation on that event. did you maybe solve this problem?

Unfortunately not yet, been trying to get around it, looking at the jQuery SlimScroll from rochal, that thing has a allowPageScroll: boolean; property that disables page / parent scroll, so i am looking to see how that has been solved.
Maybe you should give it a look..

hi @mirzinho, I solved this by adding lock and unlock events. This is now available since version 12.2.0.
You can check live demo here. Let me know if it works for you, when you have time to check it out.


New version: PostgreSQL.PostgreSQL.13 version 13.16-1

Created by 🥟 Dumplings in workflow run #7189.

Log
Updated: 13.15-2 → 13.16-1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -2145844845
2024-08-08 06:27:21.439 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000
2024-08-08 06:27:21.472 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFBF337A465: (caller: 00007FFBF337AD01) Exception(1) tid(14c0) 80190193 Forbidden (403).
2024-08-08 06:27:21.936 [CORE] Download request failed. Returned status: 403
2024-08-08 06:27:21.936 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FFBF33743D6: (caller: 00007FFBF3375C49) Exception(2) tid(14c0) 80190193 Forbidden (403).
2024-08-08 06:27:22.162 [CLI ] Failed to download, waiting a bit and retry. Url: https://get.enterprisedb.com/postgresql/postgresql-13.16-1-windows-x64.exe
2024-08-08 06:27:22.778 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000
2024-08-08 06:27:22.778 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFBF337A465: (caller: 00007FFBF337AD01) Exception(3) tid(14c0) 80190193 Forbidden (403).
2024-08-08 06:27:22.864 [CORE] Download request failed. Returned status: 403
2024-08-08 06:27:22.864 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!00007FFBF33743D6: (caller: 00007FFBF3375C49) Exception(4) tid(14c0) 80190193 Forbidden (403).

Automated error analysis suggests -2145844845 may mean Forbidden (403).
Automated error analysis suggests 80190193 may mean Forbidden (403)
(Automated response - build 887.)


Switch service descriptions to templates

Never mind - these don't need translations because they're for the court to read. Still feels a bit weird.


feat: Migrate plugin to github.com/cloudquery/plugin-sdk/v2

Hello!
We've recently updated plugin-sdk to v2 (includes migration to Apache Arrow for the destination side).
Currently, no major updates to the source side were made.
Here's an easy step-by-step workflow that will allow you to migrate the code easily & efficiently:

Install gomajor
gomajor get github.com/cloudquery/plugin-sdk/v2
add replace for github.com/apache/arrow/go/v12 (see github.com/cloudquery/plugin-sdk/v2 go.mod)
go mod tidy && go get -t -d ./... && go mod tidy && go mod vendor
make gen lint test (if the appropriate targets exist)

Thank you @candiduslynx!
Migrated to plugin-sdk to v2.
Tested, no issues found.

@candiduslynx, I'm testing with updated destinations plugins such as SQLite v2.0.0 or PostgreSQL v4.0.0 and getting the error:

is missing column _cq_id. please consider upgrading source plugin

With older version of destination plugins it works.
Could I miss something while updating to plugin-sdk/v2?

@koltyakov try with CLI 2.5.3

@candiduslynx I was already using the latest (cloudquery/tap/cloudquery 2.5.3 already installed).
It is something else.

It's seems not on my end. I tried the following as an experiment:

took a configuration of postgre -> sqlite which worked before,
updated potgresql source to v1.0.8 which uses plugin-sdk v2,
updates sqlite destination to v2.0.0 which also migrated to plugin-sdk v2,
and also receiving the same error:

Starting migration with 1 tables for: coop-prod<EMAIL_ADDRESS>-> [coop-local (sqlite@v2.0.0)]
Error: failed to sync v1 source coop-prod: failed to migrate source coop-prod<EMAIL_ADDRESS>on destination coop-local<EMAIL_ADDRESS>: failed to call Migrate: rpc error: code = Unknown desc = table artist is missing column _cq_id. please consider upgrading source plugin

Tried not only SQLite destination but also PostgreSQL with v2, same issue.
The error could be connected with incremental mode and throughs from plugins/destination/plugin.go
@yevgenypats maybe you know show could check this on your end, seems that it's global thing effected with plugin-sdk v2.

It's seems not on my end. I tried the following as an experiment:

took a configuration of postgre -> sqlite which worked before,
updated potgresql source to v1.0.8 which uses plugin-sdk v2,
updates sqlite destination to v2.0.0 which also migrated to plugin-sdk v2,
and also receiving the same error:

Starting migration with 1 tables for: coop-prod<EMAIL_ADDRESS>-> [coop-local (sqlite@v2.0.0)]
Error: failed to sync v1 source coop-prod: failed to migrate source coop-prod<EMAIL_ADDRESS>
  on destination coop-local<EMAIL_ADDRESS>: failed to call Migrate: rpc error:
  code = Unknown desc = table artist is missing column _cq_id. please consider upgrading source plugin

Tried not only SQLite destination but also PostgreSQL with v2, same issue.
The error could be connected with incremental mode and throughs from plugins/destination/plugin.go
@yevgenypats maybe you know show could check this on your end, seems that it's global thing effected with plugin-sdk v2.

Taking a look

Hi @koltyakov, thanks for reporting this issue. Can you try with version v2.0.2 of the SQLIte plugin? The issue should be fixed in that version

Thanks for reporting @andrew-koltyakov-wmg, I believe https://github.com/cloudquery/cloudquery/pull/10202 should fix it

Thanks for confirming @koltyakov! I think the forced migration is expected since we switched to using bool type for booleans instead of int. SQLite doesn't support that natively by the Go library we use handles it https://github.com/mattn/go-sqlite3/blob/edc3bb69551dcfff02651f083b21f3366ea2f5ab/doc.go#L21


Add URL masking to grants.usdigitalresponse.org

examples:
https://gost-grants-tools.onrender.com/ --> grants.usdigitalresponse.org
https://gost-grants-tools.onrender.com/login --> grants.usdigitalresponse.org/login

The marketing content is already moved. Raph will be putting it up as a
part of his website redesign.
We'll likely bring some content back to this URL in the future, but I'm not
worried about having it up immediately as the current content is already
very outdated and we are not actively linking it to partners.
On Thu, Jan 27, 2022, 7:31 AM Rob Brackett @.***> wrote:

Note: this means the app will need to take on the marketing function and
content that currently lives in the cares-website repo
https://github.com/usdigitalresponse/cares-website, or move the
marketing content to a different subdomain.
—
Reply to this email directly, view it on GitHub
https://github.com/usdigitalresponse/usdr-gost/issues/12#issuecomment-1023337193,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVX62EIQFGI3R6EMK6VWDCLUYFQMLANCNFSM5M3WZRWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

As discussed with @cmroberts , as soon as this is done we'll do an internal announcement!

@mhuang-usdr You should go visit grants.usdigitalresponse.org :)

Archived https://github.com/usdigitalresponse/cares-website and added a CNAME record pointing grants.usdigitalresponse.org -> gost-grants-tools.onrender.com , which also redirects to the login page.


Detect if MS is down and disable it

MS gets down from time to time and it throttles Smokey a lot because communication with MS runs on the main thread.
This approach does these:

[X] Wrap-up get and post so they count failures
[X] Wrap-up get and post so they return None during MS down
[X] Mark flag GlobalVars.metasmoke_down when failurecount exceeds threshold, send warning to chat rooms when that happens
[x] Replace existing code so they used the wrapped-up get and post
[x] Integrate MS websocket into this counting
[x] Quick command that enables/disables MS
[ ] Prevent automatic reboot from resetting the flag

Coverage increased (+0.03%) to 66.476% when pulling 41ef24649af3892836b23ec5fccd7bc6cd1c7351 on detect-ms-down into 6cf892316491865d49f6513df17f69587ca28183 on master.

The last one, since there's !!/ms-down and !!/ms-up commands that allows manually setting MS state to down or up, as well as that we want to avoid rebooting during MS downtime and that MS downtime usually don't last for more than a few hours, it's safe to ignore the last checklist item.
Pending merge now.


Add enabled property to EditorMenu component.

Like, when the editor is readonly, the menubar should be hidden (In my case). But if I use v-if or v-show, error will occur when some text are selected.

Therefore, adding enabled  property will be an elegant way to avoid the error above. Or, any advice or help please?

this should be fixed with https://github.com/scrumpy/tiptap/commit/0742ca8abe913b1648a50da072075e424fe9b5d4


[PE-D][Tester C] Handling of extraneous parameters differs from UG

The UG says that extraneous parameters for commands that do not take any are simply ignored (under Features > Notes about the command format). In the actual app, extraneous parameters trigger errors instead.
Steps to reproduce: run a command with extra parameters than expected such as help me or exit matrix

Labels: type.DocumentationBug severity.Low
original: teekaytai/ped#9

Fixed in a previous version of the UG


S3Path.exists() returns True on partial matches

S3Path.exists() is returning True for anything that begins with the same as a real file. For instance, if we have a file named foobar, we get a false positive when querying for foo.
>>> S3Path('s3://my-bucket/foobar').exists()  # This file is really there
True
>>> S3Path('s3://my-bucket/foo').exists()  # This file does NOT exist
True

Looks like this is a bug in S3Client._s3_file_query.
https://github.com/drivendataorg/cloudpathlib/blob/2084e205a86691b94b738df0b7ced351efedc3c8/cloudpathlib/s3/s3client.py#L154-L165
This branch of logic is too permissive and needs to also check if there's a /.
Also a blind spot in our tests that this isn't caught.

This branch of logic is too permissive and needs to also check if there's a /.

I think append a / to the key if there isn't one in this fallback path—that said, we'll need to double check if that handles the fake directory scenario as well.

Whoops, closed this by accident.

Hi. Looking for some eyes on #244 if anybody has the time. We stumbled upon the same problem and fixed it by patching it but wanted to submit a fix.

I think append a / to the key if there isn't one in this fallback path—that said, we'll need to double check if that handles the fake directory scenario as well.

It is also checking that condition as well.


[Cosmos] Replica validation before usage: Async address refresh and validation

Describe the solution you'd like
Async address refresh (regular READ address resolutions will still continue)
New replicas are validating through connecting and only then put into partition-addresses for usage
Background periodic async refresh in-case of connectivity failures
Enable this feature only if CX opted for all-replica connectivity (i.e. opted for OpenAsync equivalent)
ETA: July/2022
Main feature: #28266

PR has merged


Wavy Valley looking for support!

We aim to create a family cartoon show program that provides enriching and inspiring content for families. To achieve this, we seek diverse perspectives and inputs to establish a permanent culture that focuses on developing technology and techniques for cultural and social exploration on the new web3.
Wavy Valley offers an educational and entertaining program that meets the learning curve needs of its users through a cartoon show. Our proposal is to offer an accessible educational experience through a series of 8 animated cartoon episodes.
We envision creating a global entertainment brand that combines blockchain technology, web 3.0, and pop culture to provide a unique entertainment and education experience to billions of new users in a fun and accessible way. We're seeking investors who share our vision in this exciting project to create a globally recognized brand that delivers both entertainment and educational value to families worldwide.

****series of 8 animated cartoon episodes.
We envision creating a global entertainment brand that combines blockchain technology, web 3.0, and pop culture to provide a unique entertainment and education experience to billions of new users in a fun and accessible

way****


CamelCase for semantic types?

Currently, we're returning semantic types in snake_case.  The guidance for implementation of biolink in neo4j is that these should be in CamelCase instead.  This isn't exactly the same thing, but we should at least consider moving to CamelCase (or modifying the guidance.)

See also https://github.com/TranslatorIIPrototypes/bl_lookup/issues/9


[#5452] Improvement(web): add REST catalog backend for Iceberg catalog

What changes were proposed in this pull request?
Modified:
 - app/metalakes/metalake/rightContent/CreateCatalogDialog.js
 - lib/utils/initial.js

Why are the changes needed?
Iceberg catalog supports hive, jdbc catalog backend in WEB, we need to support rest catalog backend too, it only supports uri properties.
  1. Add select item 'rest' in the dropbox menu.
  2. When select rest menu item, only show 'uri' properties edit needs to input.

Does this PR introduce any user-facing change?
Yes, this PR introduces web UI changes :
   1.  Add a selectable item called 'rest' to the dropdown menu when creating a new catalog.
   2.  Remove all other properties except 'uri.'

How was this patch tested?
Visit the Gravitino web UI through the browser and click 'Create Catalog' .
Then, check the menu items and the API call in debug mode.
You can see the HTTP payload sent as follows:
POST  http://localhost:3000/api/metalakes/test/catalogs
{
  "name": "1",
  "type": "relational",
  "provider": "lakehouse-iceberg",
  "comment": "",
  "properties": {
    "uri": "1",
    "warehouse": "",
    "catalog-backend": "rest",
    "authType": "simple"
  }
}

response:

{
    "code": 0,
    "catalog": {
        "name": "1",
        "type": "relational",
        "provider": "lakehouse-iceberg",
        "comment": "",
        "properties": {
            "catalog-backend": "rest",
            "warehouse": "",
            "authType": "simple",
            "uri": "1",
            "in-use": "true"
        },
        "audit": {
            "creator": "anonymous",
            "createTime": "2024-11-19T15:16:07.054Z",
            "lastModifier": "anonymous",
            "lastModifiedTime": "2024-11-19T15:16:07.054Z"
        }
    }
}

Remember to run pnpm format to format the code, and then pnpm lint to check that there are no lint errors.

LGTM


How to create a solution from scratch?

The title is the question itself

As I mentioned in #3, the basic principles are map and data using active collections.
Unfortunately 2.5.x does not provide more convenience around data from scratch. However it would be considered later I think.
But even today it is still quite simple, for example:
using var sln = new Sln(SlnItems.None, string.Empty);

// for 2.5.x you need prepare map IF not already done (ie. from scratch), it can be like ~
sln.Result.Map.Add(new Section(new LVisualStudioVersion(), null));
sln.Result.Map.Add(new Section(new LProject(), null));

// then provide some data; it could be either other .sln or from scratch, etc.

    // for example, some headers ~
    var header = new SlnHeader();
    header.SetFormatVersion("12.0");
    header.SetMinimumVersion("10.0.40219.1");

    // some project collection from scratch ~
    var projects = new[] { new ProjectItem("MyProject", ProjectType.Cs, "path") };

    // ... and so on;

// then prepare write-handlers related to your data above, eg.:
var whandlers = new Dictionary<Type, HandlerValue>()
{
    [typeof(LVisualStudioVersion)] = new HandlerValue(new WVisualStudioVersion(header)),
    [typeof(LProject)] = new HandlerValue(new WProject(projects, new LProjectDependencies())),
};

// commit this
using var w = new SlnWriter("result.sln", whandlers);
w.Write(sln.Result.Map);


[ZEPPELIN-5761] Support flink 1.15.1

What is this PR for?
Trivial PR to support Flink 1.15.1
What type of PR is it?
Improvement
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5761

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Will merge if no more comment


Improvements of the Discord Commands

Discord bot commands provided via discord.ext.
Possible improvements:

Discord latency status (styled as --status); used to provide the user with corresponding thread latency.
Twitter scraper database status (styled as --database); used to provide the user with database information. I. e. the number of assigned submissions, average number of likes, etc.

Further to be announced in upcoming versions.
Ver. 1.1+.
Issued by @michalspano
Originally posted by @michalspano in https://github.com/michalspano/Swedish-Slovak-Dictionary/issues/3

Universal Status command.
Fixed: 7bd9a4464ab491e6cc4d7e8b3f94d5f6a64e4369
@michalspano


Question - Should we integrate ISecretProvider in here?

Question - Should we integrate ISecretProvider in here?
_Originally posted by @tomkerkhove in https://github.com/render_node/MDE3OlB1bGxSZXF1ZXN0UmV2aWV3NDI2MzIxNzIz/pull_request_reviews/more_threads

We should first redesign the authentication models in the security repo, right? Since we now depend on a keyvault client to return while we need a logicapps management client.

I think all you need is to lookup the secret here: https://github.com/invictus-integration/testing-framework/blob/ce47b2362141260ed3b31a5658abb18a9527bc67/src/Invictus.Testing.LogicApps/LogicAuthentication.cs#L58
All the rest is ok to be used how it is now

I think all you need is to lookup the secret here:
https://github.com/invictus-integration/testing-framework/blob/ce47b2362141260ed3b31a5658abb18a9527bc67/src/Invictus.Testing.LogicApps/LogicAuthentication.cs#L58
All the rest is ok to be used how it is now

Ok, we could do that. And pass allong the secret provider and the client secret key for this. But also, this library is gonna be used in test projects and I don't think there's always need for this to do? (We also don't use secret providers if we get a client secret in our tests for example.)

That's true, I wouldn't make it mandatory but more open in case people want to use it.


Getting HTTP 429 on dev tunnel - Why?

Hi there,
We've just started using dev tunnel to receive webhooks on local dev environments.
This worked for a few minutes and we've already start HTTP 429 Too many requests errors.
We don't understand why.
As far as we can gather, we haven't gone over any limits yet. We've literally just started playing with it.
Unfortunately the HTTP response from the tunnel give any message about what limit we have supposedly breached.
Can someone shed some light on the matter?
Here is a screenshot from the HTTP headers returned:

We are experiencing same issue for like 3 days now. We used dev tunnel for half a year without issue but it stopped working now.

I’m encountering the same issue with dev tunnel—everything works for a few minutes, and then I start getting HTTP 429 “Too many requests” errors. Similar to your experience, I haven’t exceeded any apparent limits, it’s quite frustrating...

I have encountered the same problem. We have been using devtunnels for some time, but to my knowledge we have not encountered this problem until recently. Currently we are encountering this issue to such an extent that it is blocking our work. BandwidthPerUser is under 10%.

We have also been experiencing this issue. Using 1 tunnel, 2 ports (front end/server).
For us the trigger is Next.js hot reloading. We switched from VS Code dev tunnels to dev tunnel cli and that fixed it for a day now it's back to kicking us off every time we hit save and trigger a hot reload.

i am facing the same issue with our .NET 8 / VITE / REACT setup

We have the exact same issue when using .NET with vite + React

I'm also having this issue with Next.js

back to ngrok :-)

We're going to increase ClientConnectionsPerPort connection limit. The change should deploy pretty quickly. Sorry for the inconvenience.
The response headers were not correct for these 429s - the limitation that caused 429 was this ClientConnectionsPerPort: max 20, not the HttpRequestRatePerPort. The fix for the response headers will come out later on.

It would be great if you could also include a human friendly message indicating the limit that was breached (the headers are good but I haven't seem them documented anywhere).

I've been having this problem too. Any news when it will be fixed?

We're going to increase ClientConnectionsPerPort connection limit. The change should deploy pretty quickly. Sorry for the inconvenience.
The response headers were not correct for these 429s - the limitation that caused 429 was this ClientConnectionsPerPort: max 20, not the HttpRequestRatePerPort. The fix for the response headers will come out later on.

Has the change rolled out? We're still running into the same problem.

@IlyaBiryukov

We're going to increase ClientConnectionsPerPort connection limit. The change should deploy pretty quickly. Sorry for the inconvenience.
The response headers were not correct for these 429s - the limitation that caused 429 was this ClientConnectionsPerPort: max 20, not the HttpRequestRatePerPort. The fix for the response headers will come out later on.

What is the new limit? For Vite it is common and by design to serve hundrets of files on initial load (see this issue on vite side). As this is the "modern approach", one could even say industry standard (and even bundled with the VS Templates - it would be crutial to support this "Basic usecase"

@clement911

Are DevTunnels generally stable or is this a common occurrence? I have been using ngrok for 7 years and never had an issue. I have used dev tunnels for 5 minutes and already ran into this issue. I am hoping to move our team off ngrok and on dev tunnels. I'm trying to get a sense of whether dev tunnel is reliable enough to make the switch.

We switched from ngrok quite some time ago - Our project still had the old static file serve model therefor we never encountered throtteling issues so far. After migrating to vite this started to become an issue.
But to be fair they stated in there documentation from the get go

To request higher usage limits for dev tunnels, open an issue in our GitHub repo. In the issue, include which limit you'd like increased and why.

(Source)
So that's basically what OG did in this thread ;)

The change to the limits is rolled out. The new limit is 200 connections per tunnel port.

I'm still seeing ClientConnectionsPerPort: max 20 not ClientConnectionsPerPort: max 200? Is there anything I need to do to see this change so the 429 error can be resolved? Thanks

The limit still seems to be at 20 requests for me and i get a 429 for my requests.

I have the same issue with my  .NET with vite + React App.

Same problem, working only for few seconds until i try to request to somewhere, then all crashes showing 429 HTTP error.
Only working with 2 connections and 1 port...
Happening since 16th oct 2024 at least....

Our solution needs like 600 connections because is it split into 3 components that runs on different URLs at the same time. Imagine like client operator and one shared component. So to use it, we need to have at least 600 connection for a short period of time. To be totally safe, 1k is optimal, is this possible?

@fogatond we're going to change the limit to 1k.
@andresito1969, @StefanH114 If the issue still reproduces for you, can you please share your tunnel port URLs and time when you hit it? Then I can check the tunnels telemetry. You can reach me at my first name dot my last name at Microsoft dot com. I double checked and I see the new limits are in effect now, ClientConnectionsPerPort: max 200 is returned on 429s.
@faire2 re as to why the limit is enforced, there was an outage some time ago when some cross-regional tunnel kept open tens of thousands of connections to a forwarded port. This caused socket exhaustion and brief service outage in one region, so we had to limit the number of connections opened when clients connect to forwarded ports. We already impose 20 connections limit per tunnel that is applied to SDK client connections.

Thanks for the explanation, I appreciate it. We're really looking forward for the new limit, working with devtunnels was awesome and I would love to be able to use it again.

@IlyaBiryukov I just tried this out and I cannot see the increase so I've still got the same issue, please see below:

The issue still reproduces for me.

I'm experiencing this too - It usually happens around 15 minutes into hosting locally

Still hapenning and i sent an email to you this morning (CET Madrid time zone) @IlyaBiryukov
Since it's not working i'm using github pages, but obviously is way too slow to do that, unluckily i have to work with gh pages until it's fixed, if you need more info we talk via mail, have a great day.

I'm experiencing this too - It usually happens around 15 minutes into hosting locally

Same. Recent changes made it a bit better than before, but it's still unusable. Hot reload hits rate limit way too quickly.

I'm experiencing this too - It usually happens around 15 minutes into hosting locally

Same. Recent changes made it a bit better than before, but it's still unusable. Hot reload hits rate limit way too quickly.

I've found a temporary fix since you mentioned hot reload which is working fine for me so far. I'm using VS Code Live Server extension and turns out dev tunnels doesn't like it saving and refreshing the page too often which is understandable.
I added "liveServer.settings.ignoreFiles":["**"] to my User/settings.json which stops the live refreshing so I'm only refreshing the page when I need to with ctrl shift r.
Hope this helps

I could find these in our telemetry. We're investigating why the policy change didn't apply to some regions. It did apply to West US 2 & West US 3 regions though.

The policy change to 200 max connections per tunnel port should be applied everywhere by now. What happened is that after we updated policy's config map in our clusters, we assumed the service pods had picked up the changes. We verified that the new policy was in effect in US West region and that was the case. Well, it happened that an automatic cluster update did run right after policy update in US West and restarted our service pods, which made them reload the policy. In other regions we just checked the config map. As the other regions didn't run automatic cluster update and the pods didn't pick up the change, the old policy stayed in effect. So, restarting the pods now applied the updated policy.
Re further upping the limit to 1K, we'll have to delay that a bit. There is deployment freeze in our division now, only critical fixes can make it. We can get to it after November the 7th.

@IlyaBiryukov I can confirm this has now resolved my issue due to the fact that the ClientConnectionsPerPort: max 20 has now been removed:

Thanks!

The policy change to 200 max connections per tunnel port should be applied everywhere by now. What happened is that after we updated policy's config map in our clusters, we assumed the service pods had picked up the changes. We verified that the new policy was in effect in US West region and that was the case. Well, it happened that an automatic cluster update did run right after policy update in US West and restarted our service pods, which made them reload the policy. In other regions we just checked the config map. As the other regions didn't run automatic cluster update and the pods didn't pick up the change, the old policy stayed in effect. So, restarting the pods now applied the updated policy.
Re further upping the limit to 1K, we'll have to delay that a bit. There is deployment freeze in our division now, only critical fixes can make it. We can get to it after November the 7th.

Thanks Ilya, it works much better now. Will you leave ticket open until you up limit to 1k and then let us know?

@IlyaBiryukov Hi, my dev tunnel seems to be stuck with 199 client connections now. I stopped devtunnel host command, removed anonymous access, waited for one hour and it is still at 199. Is there any way to "disconnect" all clients? I haven't found any command in devtunnel documentation. Is this something that is relevant to this ticket? IMHO this might be culprit of why you had thousands of opened connections as mentioned below.

@faire2 re as to why the limit is enforced, there was an outage some time ago when some cross-regional tunnel kept open tens of thousands of connections to a forwarded port. This caused socket exhaustion and brief service outage in one region, so we had to limit the number of connections opened when clients connect to forwarded ports. We already impose 20 connections limit per tunnel that is applied to SDK client connections.

Tunnel ID: chat-widget-new.euw
Port Number : 3030
Protocol : auto
Access control: {}
Client connections: 199

@fogatond I'll investigate. Thanks for reporting this!

Waiting for Nov 7th. Im also experiencing this :D

Deployment freeze is extended till the next Monday, 11/10. The good news is that I believe I found the root cause of issue that @fogatond reported. The next release will have both 1K limit and the fix for that issue.

Do you have any estimates when the fix will be released? Thank you.

Release complete.


Trac-IK solver

Why add a ton of commented lines?
You could do the same by adding this to a new file and people can chose in the launch file that loads kinematics solvers which one to use.

It's a choice, I've seen already other robots doing like this to switch from KDL kinematics to IKFast kinematics.


fix: Don't output bucket name until it exists

Description
https://github.com/terraform-ibm-modules/terraform-ibm-cos/issues/558
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

:tada: This PR is included in version 7.5.1 :tada:
The release is available on:

GitHub release
v7.5.1

Your semantic-release bot :package::rocket:


Open up default auth to everyone, but warn about it.

I’ve added a primitive warning in signin.html and tested for it in test.py but I’d like @tmaybe or @norrishung to make sure it looks like it should.
Closes #387 and closes #388.

Looks fine to me. My only suggestion would be to add AUTH_DATA_HREF to env.sample and remove AUTH_CSV_URL if it's not used anymore.

Good one, I’ll do that.


Swift 6 adoption and fabulous yak hairdress story

Quiiiiite a few things changed from the aborted Swift 5 version:

Managed to remove the distinction between throwing and nonthrowing types thanks to typed throws and a lot of overloading.
Made everything related to Async providers or caches sendable.
Sync stuff bifurcated into Sendable and non-Sendable stuff since only the latter will easily adapt to working within async providers.

A lot more cleanup and stuff that I have already forgotten about.
Note: README is good, all other DocC documentation is out of date.

Done a full documentation pass, some API cleanup and even added a few unit tests.
I'll be merging this, renaming the repo and posting this new version in a day or two.


Haproxy receiver support

Hi everyone!
I noticed that the otel-contrib already includes support for a HaProxy receiver (few days ago 🥳 ).
https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/haproxyreceiver
Do you have any plans to add support for HAProxy here (splunk-otel-collector)?
Is there anything I can assist with? I could try! Please let me know.
Best regards!
Daniel

Thanks @rmfitzpatrick !
The Idea opened: https://ideas.splunk.com/ideas/SFXIMMID-I-586
Let's do that!


Loading Images

Can the webpack_asset function be used to load images?

No, not out of the box.
The issue is that every webpack module is javascript file by default. So either you require('image.png') or put image.png as an entry point (read "inside webpack_asset function"), webpack generates javascript file with module.exports = 'file_path.png'; somewhere in it (and javascript is not valid picture file).
It could be possible if using additional plugins like extract-text-webpack-plugin (see this issue for discussion).
It's already configured for css files in this bundle (see example in readme) - same story would go for images.
I played a little with this idea - unfortulatelly, it looks like plug-in doesn't support binary content.
So, to make it work, one would need to:

Make extract-text-webpack-plugin work with binary content
Configure app/config/webpack.config.js to use it for images (possibly few instances of plugin may be needed - for images and css files)
Pass second argument to webpack_asset to take correct file (not default JS one)

On the other hand, webpack is really brilliant when you are making single-page application. If that's the case, you can still use image loading with require inside your javascript files and add them dynamically when needed.

Thank you for the quick reply. Yeah I did try and got a .js file as a result. I'm new to the whole symfony ecosystem. I am actually not working on an SPA, so i can't really require the image files. Do have any tips regarding the images? Ideally I'd like to keep them next to my other assets in /app/Resources/assets.

This might be achievable with the copy-webpack-plugin. I'm unsure if the manifest plugin would pick up on these files though.

No, as it's a plug-in, not a loader - it does not interfere with entry point loading, requiring other assets or handling webpack modules.
But it could be used - as it copies files, you could just point src to needed URL statically. This would mean hard-coded URLs, so you would not get automatic cache-busting.

I've created a loader+plugin to handle this scenario.
https://github.com/vaniocz/entry-file-loader
It could be probably improved further.
If this PR was merged https://github.com/mariusbalcytis/webpack-bundle/pull/11
then it would be possible to load images using
{{<EMAIL_ADDRESS>'png') }}
Maybe another twig function could be created for this purpose.

I've added two new functions to my fork.
https://github.com/maryo/webpack-bundle/commit/4d5bf59024644697623297205d495eb2197b223c
webpack_css_asset for easier linking of css assets, you don't need a condition. it could by improved to support media attribute
webpack_file_asset for easier linking of images and others using the mentiond loader
Let me know what you think. I'd add few tests and send a PR if interested.

#11 was merged - thanks for that, didn't realized that filters can be also applied to entry point files.
As I understand, loading images via webpack is needed for cache-busting? Or is there another use case?
They could also be optimized by some filter like image-webpack-loader - is !! really needed?
If it's common use-case, you could give a PR. I'd have some minor comments on it if you'd give it though.

Cache busting is one example. Possible usage of filters like image-loader is another good example. Very good example is that you can link to files from node_modules using this approach. But the primary reason for me was that I simply didn't want to have one set of images in assets folder and a second in public folder or to have all images in public folder when the images linked from CSS using file-loader are then copied to compiled folder so they are public just for no purpose. Sometimes you want to even use the same asset like image once from CSS as a background and once from HTML. But in case of webpack and CSS you need to use a loader for the assets. Like file-loader which copies the files thus at the and the CSS use different assets (copies) than those linked from HTML. It's actually not a problem in 95% of cases but it just feels weird :)
Another solution is to create a loader which would not use copies but it would somehow need to mimic the directory structure change like ../../public/images -> ../bundles/xxx/images or something like this.

Just chiming in to express my support for this idea. I have a working configuration using the currently-published versions of both this bundle and entry-file-loader.
In my Twig templates I have:
<img src="{{<EMAIL_ADDRESS>'png') }}" alt="logo">

and in my webpack config:
loaders: [
  {
    test: /\.(png|jpg|jpeg|gif)$/,
    loader: 'entry-file'
  }
  ...

This setup works perfectly: free cache busting and the possibility to insert additional loaders to the images if I want. I would image that the same procedure would work for non-image files, too.

It should work but I'm not sure it is the best approach to set the loader for all image files. Then the loader is invoked for every image linked even from css files etc then. But actually... maybe it's not a problem at all if you don't encountgery any performance issues or thinks like that.


CheckerboardMaterialProperty     error

Uneven distribution
entities.add({   wall: {     positions: Cesium.Cartesian3.fromDegreesArrayHeights([<PHONE_NUMBER>02126003, 39.934191456263797 ,100,<PHONE_NUMBER>62140997, 39.9341955696041 ,100,<PHONE_NUMBER>36819006, 39.934245995639799 ,100,     ]),     material: new Cesium.CheckerboardMaterialProperty({       repeat: new Cesium.Cartesian2(10.0, 2.0),     }),   }, });

Thanks @miyuer - this looks like a bug on our end. For convenience, here's a simple Sandcastle reproducing the issue.

The same CheckerboardMaterialProperty seems to work ok with Rectangles; I wonder if this is specific to wall entities..

The same problem arises in GridMaterialProperty , The square seems to be evenly divided by the position points


Add missing semicolon

@eluchsinger : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Could not find :tpdirect: while running react-native run-android

I am trying to use react-native-tappay and running the command npx react-native run-android to test on a physical device. The process failed with the following error message:
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find :tpdirect:.
     Required by:
         project :app > project :react-native-tappay

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

What would be the next step the solve the issue? I am using React Native 0.66.0 and react-native-tappay 1.3.2. Thank you very much for your help.

Hi @matteo1222 add these lines in your project https://github.com/VeryBuy/react-native-tappay/blob/master/example/android/build.gradle#L34-L36

It worked. Thank you so much!

@Dylan0916 could you please add this step to README?

Sure~


Security Vulns Fixes 2024-07-27

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Upgrade a few components in order to mitigate some high severity vulnerabilities.
Is there anything you'd like reviewers to focus on?
No.
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[x] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

Check out Contributing and Code of Conduct
A picture of a cute animal (not mandatory but encouraged)

@Haarolean - I think we need to update Springboot to atleast 3.2.7 in order to fix some critical vulnerabilities. But whenever I try to update it beyond 3.1.11, I ma getting 2 backend tests failure here:
@Test
void resolvesCustomConfigClassProperties() {
env.setProperty("prop.0.custProps.f1", "f1val");
env.setProperty("prop.0.custProps.f2", "1234");
var resolver = new PropertyResolverImpl(env);
assertThat(resolver.getProperty("prop.0.custProps", CustomPropertiesClass.class))
    .hasValue(new CustomPropertiesClass("f1val", 1234));

}
And this is the error. --->>>
[ERROR] Failures:
[ERROR]   PropertyResolverImplTest$WithPrefix.resolvesCustomConfigClassProperties:138
Expecting Optional to contain:
PropertyResolverImplTest.CustomPropertiesClass(f1=f1val, f2=1234)
but was empty.
[ERROR]   PropertyResolverImplTest.resolvesCustomConfigClassProperties:85
Expecting Optional to contain:
PropertyResolverImplTest.CustomPropertiesClass(f1=f1val, f2=1234)
I tried to figure it out but I am not that good with Java. So could you please help me in free time to upgrade springboot to atleast 3.2.7?
Regards.

If spring bump had been easy, we would've merged it already :)


How to add configuration of authelia in  nginx controller in kubernetes?

This is a question on how to configure authelia in nginx controller.
Its been 4 days i was trying to find example or documentation on how to add authelia configuration in nginx controller.
Not sure if there is documentation on it.
If anyone have the links or information on it, please help me to progress.
   Environment:
   ==================
   Ingress: NGINX
   k8s: AKS
   storage: postgresql
   session: redis

Thanks.

I found this online https://www.authelia.com/docs/deployment/deployment-kubernetes.html but it has information only about how to protect the ingress.

The notes from the helm chart output a list of annotations for ingress-nginx:
https://github.com/authelia/chartrepo/blob/master/charts/authelia/templates/NOTES.txt


Version 0.0.5

Added characteristics for precip 1 hour, precip today, wind direction,
wind speed, air pressure, visibility, uv-index and measuring station
Added contition category for sunny/partly cloudy
Renamed contidion values to condition categories
Changed condition category values
Changed service to temperature-sensor so that the device is recognized
by apple home app

Fork with new features and npm package is available here: https://github.com/naofireblade/homebridge-weather-station-extended


Unexpected panic while rearranging macro arguments

Invocation:
$ srgn --version
srgn 0.11.0

$ srgn --files '**/*.rs' --rust-query '((macro_invocation macro: (identifier) @name) @macro (#any-of? @name "error" "warn" "info" "debug" "trace" ))' '(?P<msg>.+);(?P<structure>.+)' '$structure,$msg'

Panic:
thread '<unnamed>' panicked at ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/srgn-0.11.0/src/scoping/scope.rs:60:43:
begin <= end (23 <= 0) when slicing `error!( "server error"; "uuid" => %uuid, "error.user_msg" => %user_msg, src)`

Please let me know if more information is needed.

Hi! So the panic was simply a bug, which is fixed now. The syntax of '(?P<msg>.+);(?P<structure>.+)' '$structure,$msg' still doesn't work as intended yet, but as mentioned I'll be working on implementing that. In the meantime, to solve your immediate problem, perhaps ast-grep can help you?

Hi @Xaeroxe !
Support for variables landed in main recently, at 7f6cfcbcef8f8d010de5b12df4d3e749b655d128 . That will make it into a release soon-ish. Then, an invocation like '(?P<msg>.+);(?P<structure>.+)' '$structure,$msg' should start working (see here for the docs).


Migrate image and BC at the same time

Cloning: https://github.com/konveyor/mig-ui/issues/687
When I migrate my app, I would expect that the same image is running on the target system.
If a BC is available a new image will be created after the migration, which could lead to a new image/version... This could be different from the image on the source cluster.
At least I should get asked

CAM vienna 1.1.1

CC: @rbaumgar

So the suggestion is that we might want to (potentially) prohibit the BuildConfig from triggering a new build post-migration? I wonder if it's possible to do this without impacting future BuildConfig behavior. i.e. we could remove whatever triggers a new build, but this would result in a post-migration change (builds are no longer automatic in a way that they were before) that may be a bigger impact than a new image triggered as a one-time action on migration. But, as you say, if that's something we can ask the user, it could work. i.e. you could add something like this to the API (and UI):
For BuildConfigs which automatically trigger builds on Configuration updates, do which one of the following:
1) If the migrated BuildConfig results in a ConfigChange trigger event, build a new image after migration (default behavior)
2) Remove ConfigChange trigger from migrated BuildConfig to prevent a new build upon migration. To resume automatic build triggers post-migration, this must be manually re-added


fixed minor spelling error

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/Tools/nuget-exe-CLI-Reference.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks for catching that, and thanks especially for taking the time to make a PR. I really appreciate it. :)

@kraigb np


  THIS SOFTWARE MAY BE REDISTRIBUTED TO OTHERS ONLY BY EFFECTIVELY USING THIS OR ANOTHER EQUIVALENT DISCLAIMER IN ADDITION TO ANY OTHER REQUIRED LICENSE TERMS.
 NO OTHER SOFTWARE CODE OR MATERIALS ARE A CONTRIBUTION.

This pull request is to address https://github.com/finos/qPython/pull/19

The commit I've pushed at the moment is simply to trigger the CCLA process.

any update on this? This prevents me from upgrading to python 3.12 (which needs an updated numpy)


Bug of setDisabledTimes

I found issue about setDisabledTimes. When i disable time of 00:00-01:00 and 23:00-23:59, I still can select 0 hour. it appears like the picture that I attached.

maybe @wdullaer you can show me the code, so i can fixing this problem.

I'll work on this


ZipException upon launch.

Version of Boardwalk: 1.2
Version of Android: 7.0
Device model: Galaxy S7 Edge (Snapdragon) SAMSUNG SM-G935A
Description of the problem: During the conversion process of actual Minecraft, an exception occurs saying that it expected a -1 byte zip file, but it got something bigger.
Error: java.util.zip.ZipException: Invalid entry compressed size (expected -1 but got 1329 bytes)

HEYYYY 2F4U

This is an error that from what I'm aware of occurs because of how file management works from apps changed in Android Nougat. We have to wait on an update from the dev or find some workaround.


New package: DMARC v0.0.1

Registering package: DMARC
Repository: https://github.com/analyticsinmotion/DMARC.jl
Created by: @rossarmstrong
Version: v0.0.1
Commit: a08b2e14d41ded3d8b0b2e1ab4831a9e8f605d67
Reviewed by: @rossarmstrong
Reference: https://github.com/analyticsinmotion/DMARC.jl/issues/1#issuecomment-1725258393
Description: Easily parse DMARC XML files into a more human-readable format with this high-performance Julia package.

I am writing to request the approval of the DMARC.jl package name for our Julia package. The name DMARC.jl does not strictly adhere to the established package naming conventions, where names usually start with an uppercase letter and consist of ASCII alphanumerics only. However, I kindly request an exception to this rule, as the name DMARC.jl is an industry acronym for "Domain-based Message Authentication, Reporting and Conformance." Acronyms like DMARC are often capitalized and widely recognized within their respective domains.
We considered alternative names, such as DMARCParser.jl, but we weren't sure it would receive approval either. Having the package name as DMARC.jl allows us potential scope to expand the functionality of the package in the future while maintaining a recognizable and intuitive name.
Choosing DMARC.jl as the package name serves to clearly and accurately represent its purpose as an implementation related to DMARC, a critical standard in email authentication and security. We believe this name provides a strong foundation for potential growth and development of this package, making it a valuable addition to the Julia community.
Thank you for considering this request.

I think DMARCParser or DMARCFiles would be better and would pass the guidelines for automatic merging


Probability distirbutions

Description
For probabilistic modeling, pytorch has the distributions module, and tensorflow has the tensorflow_probability package. I haven't seen something similar for MXNet. The closest I've seen is GluonTS, but this more domain specific for forecasting.
Is this to be considered the official MxNet probability package?

GluonTS certainly has plenty of distributions offerings. @xidulu and @szhengac also made the gluon.probability module for Gluon 2.0 (#18403, discussion in #17240), though this is not yet available in mxnet 1.x releases.

Great news! Thank you!


Cleaning up UX and using real station data

In an effort to clean things up, I am now using real station data to fetch the graphs, and, ensuring things are displayed properly, and cleaning up code/json

I think the chart and legend don't dynamically shrink when resizing the screen.

Shrinking this PR via https://github.com/transitmatters/t-performance-dash/pull/333, then will break up one more time

Waiting on https://github.com/transitmatters/t-performance-dash/pull/340

Okay this PR is finally ready to test and I'm going to leave it alone


Feature/Game Play

Added the majority of the gameplay

Looks good to me! Will try to break things :)


Add back4app as hard

Added back4app account deletion instructions, and a link to the relevant Help article.

Thanks for your contribution!


Syslog flooded with messages from engine-image

Dear all,
I am running Longhorn v.1.3.2 on K3S (v.1.24.6) Ubuntu 22.04 RaspberryPi and have recognized that my /var/log/syslog gets flooded with the following message:
run-containerd-runc-k8s.io-f2b2a1b5606bacf9b28fc64c8aaa27c4133d992c40d4859188bd97009326feac-runc.EccIGd.mount: Deactivated successfully.
Doing a bit of research I can map it to the following container (from var/log/containers)
engine-image-ei-a5371358-kkb2j_longhorn-system_engine-image-ei-a5371358-f2b2a1b5606bacf9b28fc64c8aaa27c4133d992c40d4859188bd97009326feac.log
I am seeing the same on my test cluster Ubuntu 22.04 AMD64 - so it seems to be consistent across hardware platforms.

Any chance I can get rid of these log files? Did not find anything searching the web. Thus asking here.
Please keep up the great work with Longhorn, it is a great project!
Thx,
Jens

Can you check if the pods of Longhorn system work correctly? Or provide us the support bundle?

Hi Derekbit,
I have attached the support bundle created on the x86 environment where the flooding is more aggressive than on my ARM Cluster.
Attached is as well the list of longhorn PODs running on my system, do not see any anomalies
NAME                                           READY   STATUS    RESTARTS      AGE
longhorn-ui-5654cc99b8-lfl8t                   1/1     Running   0             31h
longhorn-conversion-webhook-75d5f97dd9-sjxsw   1/1     Running   0             31h
longhorn-conversion-webhook-75d5f97dd9-s6g8n   1/1     Running   0             31h
longhorn-admission-webhook-5499dd964f-spv76    1/1     Running   0             31h
longhorn-admission-webhook-5499dd964f-625p2    1/1     Running   0             31h
longhorn-manager-9kqwn                         1/1     Running   0             31h
longhorn-manager-z5gkk                         1/1     Running   1 (31h ago)   31h
longhorn-manager-kvk46                         1/1     Running   0             31h
longhorn-driver-deployer-5b88d45d9f-mmtqr      1/1     Running   0             31h
csi-resizer-7c5bb5fd65-xrddn                   1/1     Running   0             31h
csi-provisioner-5d8dd96b57-gzjg2               1/1     Running   0             31h
longhorn-csi-plugin-j8zs9                      2/2     Running   0             31h
longhorn-csi-plugin-qdwld                      2/2     Running   0             31h
csi-snapshotter-5586bc7c79-lrwbf               1/1     Running   0             31h
longhorn-csi-plugin-7ps9w                      2/2     Running   0             31h
csi-provisioner-5d8dd96b57-gvbj7               1/1     Running   0             31h
csi-snapshotter-5586bc7c79-8lqfw               1/1     Running   0             31h
csi-attacher-dcb85d774-zcxmd                   1/1     Running   0             31h
csi-attacher-dcb85d774-vlzbc                   1/1     Running   0             31h
csi-snapshotter-5586bc7c79-zbsqz               1/1     Running   0             31h
csi-attacher-dcb85d774-7l5s4                   1/1     Running   0             31h
csi-resizer-7c5bb5fd65-wrsvm                   1/1     Running   0             31h
csi-provisioner-5d8dd96b57-hm4tw               1/1     Running   0             31h
csi-resizer-7c5bb5fd65-7trvf                   1/1     Running   0             31h
instance-manager-e-0f0fea42                    1/1     Running   0             31h
instance-manager-r-3cfa8643                    1/1     Running   0             31h
instance-manager-r-935756d5                    1/1     Running   0             31h
instance-manager-e-3996a930                    1/1     Running   0             31h
engine-image-ei-a5371358-vhv6b                 1/1     Running   0             31h
instance-manager-e-06a9dd5a                    1/1     Running   0             31h
instance-manager-r-7ecf2aff                    1/1     Running   0             31h
engine-image-ei-a5371358-jrf95                 1/1     Running   0             31h
engine-image-ei-a5371358-7cqs5                 1/1     Running   0             31h
share-manager-kuma-uptime-dev                  1/1     Running   0             31h

Here is the example from /var/log/syslog
sudo tail -f /var/log/syslog
Nov 27 18:04:44 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.aKEGLJ.mount: Deactivated successfully.
Nov 27 18:04:45 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.Cfmjni.mount: Deactivated successfully.
Nov 27 18:04:49 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.GPgcNO.mount: Deactivated successfully.
Nov 27 18:04:50 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.hHabiJ.mount: Deactivated successfully.
Nov 27 18:04:54 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.HDeapA.mount: Deactivated successfully.
Nov 27 18:04:55 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.ojeecA.mount: Deactivated successfully.
Nov 27 18:04:59 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.bLaeFc.mount: Deactivated successfully.
Nov 27 18:05:00 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.HceaIM.mount: Deactivated successfully.
Nov 27 18:05:04 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.cgHEhL.mount: Deactivated successfully.
Nov 27 18:05:05 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.aAaHcA.mount: Deactivated successfully.
Nov 27 18:05:09 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.DPhggH.mount: Deactivated successfully.
Nov 27 18:05:10 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.MGINMK.mount: Deactivated successfully.
Nov 27 18:05:14 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.hHGpnl.mount: Deactivated successfully.
Nov 27 18:05:15 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.bjPmbj.mount: Deactivated successfully.
Nov 27 18:05:19 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.oNOELC.mount: Deactivated successfully.
Nov 27 18:05:20 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.pAgEIM.mount: Deactivated successfully.
Nov 27 18:05:24 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.mOchlo.mount: Deactivated successfully.
Nov 27 18:05:25 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-b32360649a62adf37f6ac00a65506f6b388d4ef701e3d84875a77f5114ec34c5-runc.EOmhJM.mount: Deactivated successfully.
Nov 27 18:05:29 orion-dev-master systemd[1]: run-containerd-runc-k8s.io-3cb7cd0898a1025adaf82718ce9d0bd859f69f718a5717d98ca40cbdac0048e8-runc.HcppOP.mount: Deactivated successfully.

2022-11-26T10:23:29.443263878+01:00 stdout F time="2022-11-26T09:23:29Z" level=info msg="starting health check for volume" encrypted=false volume=kuma-uptime-dev

longhorn-support-bundle_e92edee0-eeb7-4e9d-9103-de88394d46c5_2022-11-27T16-56-25Z.zip

The Longhorn system lools quite normal from the support bundle.
Any idea?
cc @shuo-wu @innobead

Merry Christmas everyone!
Just a quick note some colleagues of mine are seeing the same log entries - seems to be default behavior of the latest Longhorn release.
Would be good to get rid of these with the upcoming release.
Enjoy the holidays and happy new year already!!

@eleven6
Happy Holidays.
Just checked my worker nodes. I got the same flooding messages on my worker nodes. Older systemd shows ....: Succeeded, and newer one shows ....: Deactivated successfully.
Dec 24 15:49:08 ubuntu2004 systemd[1]: run-containerd-runc-k8s.io-ff8e27d0e20fa2bfb2e17b0550bdb66d12f4e863d37a6a33f6a3ae3d439b6c8a-runc.alNjeN.mount: Succeeded.

The readinessProbe's periodSeconds of each engine-image daemonset is 5 seconds (https://github.com/longhorn/longhorn-manager/blob/v1.3.2/controller/engine_image_controller.go#L819). It periodically starts a check process in the engine-image pods' containers. systemd generates the the ...: Deactivated successfully after successfully finishing the check (systemd code). The flooding messages are therefore expected. So, the next step is to change the log level.


add schedule

I forgot to mention one thing: this changes the interface in a way that is not backwards compatible, so it would require a major version bump. How about instead we detect whether .Values.backup is filled and use it if present as long as .Values.schedule (or .Values.backupSchedule) is empty? That would allow us to deprecate it, issue a warning in the NOTES.txt template, and in the next major version upgrade do away with the old option completely.


BatchNormalization layer fails when using Theano back-end together with "tf" image dimension ordering.

Hi,
I don't know whether I'm supposed to use Theano back-end together with the "tf" image dimension ordering, the BatchNormalization layer will fail in this case.
It will pass the shape check when building the network, and modal.summary() will give the correct shape like
Layer (type)                     Output Shape          Param #     Connected to
====================================================================================================
convolution2d_1 (Convolution2D)  (20, 98, 98, 32)      896         convolution2d_input_1[0][0]
____________________________________________________________________________________________________
batchnormalization_1 (BatchNorma (20, 98, 98, 32)      128         convolution2d_1[0][0]
____________________________________________________________________________________________________
activation_1 (Activation)        (20, 98, 98, 32)      0           batchnormalization_1[0][0]
____________________________________________________________________________________________________
convolution2d_2 (Convolution2D)  (20, 96, 96, 64)      18496       activation_1[0][0]

but Theano will give the following error when running
ValueError: GpuDnnConv images and kernel must have the same stack size

Apply node that caused the error: GpuDnnConv{algo='time_once', inplace=True}(GpuContiguous.0, GpuContiguous.0, GpuAllocEmpty.0, GpuDnnConvDesc{border_mode='valid', subsample=(1, 1), conv_mode='conv', precision='float32'}.0, Constant{1.0}, Constant{0.0})
Toposort index: 707
Inputs types: [CudaNdarrayType(float32, 4D), CudaNdarrayType(float32, 4D), CudaNdarrayType(float32, 4D), <theano.gof.type.CDataType object at 0x7f59985c7c10>, Scalar(float32), Scalar(float32)]
Inputs shapes: [(20, 98, 32, 98), (64, 32, 3, 3), (20, 64, 30, 96), 'No shapes', (), ()]
Inputs strides: [(307328, 3136, 98, 1), (288, 9, 3, 1), (184320, 2880, 96, 1), 'No strides', (), ()]
Inputs values: ['not shown', 'not shown', 'not shown', <PyCObject object at 0x7f59827fa378>, 1.0, 0.0]
Inputs name: ('image', 'kernel', 'output', 'descriptor', 'alpha', 'beta')

Outputs clients: [[GpuDimShuffle{0,2,3,1}(GpuDnnConv{algo='time_once', inplace=True}.0)]]

HINT: Re-running with most Theano optimization disabled could give you a back-trace of when this node was created. This can be done with by setting the Theano flag 'optimizer=fast_compile'. If that does not work, Theano optimizations can be disabled with 'optimizer=None'.
HINT: Use the Theano flag 'exception_verbosity=high' for a debugprint and storage map footprint of this apply node.

Here're some code snippets
{
    "image_dim_ordering": "tf",
    "epsilon": 1e-07,
    "floatx": "float32",
    "backend": "theano"
}
...

img_rows, img_cols, im_chnls = 100, 100, 3
input_shape = (img_rows, img_cols, im_chnls)
bn_axis = -1
...

x = Input(shape=input_shape)
y = Convolution2D(32, kernel_size[0], kernel_size[1], border_mode='valid')(x)
y = BatchNormalization(axis=bn_axis)(y)
y = Activation('relu')(y)
y = Convolution2D(64, kernel_size[0], kernel_size[1], border_mode='valid')(y)
y = BatchNormalization(axis=bn_axis)(y)
y = Activation('relu')(y)
y = MaxPooling2D(pool_size=pool_size)(y)
...

model = Model(x, y)
model.compile(loss='categorical_crossentropy',
              optimizer=Adam(lr=0.001, decay=1e-5),
              metrics=['accuracy'])
model.summary()
...

Best regards

Can you provide code which can reproduce the error? I think the args (probably axis?) of your BatchNormalization layer might be the potential problem.

@joelthchao Hi thanks for your reply, I've added some code snippets. I've tried switching the axis argument but it doesn't seem to help. I'm now using the th ordering, which works fine.

Same setting as yours, no error when training this model. Maybe you can upgrade Keras and Theano?
>>> theano.__version__
'0.8.2'
>>> keras.__version__
'1.1.2'

I was able to replicate the problem, but only with Theano v0.8.2 (not the latest GitHub version) and only with device=gpu. I think the problem was introduced in 6fd2d43bfeb1195e68693a66e767464835e40abf.
Can you have a look at the patch in the pull request? I think that should fix your problem.

Hi,
I am having a similar problem to the one that @gvtulder had, except that I have Theano 0.9.0-dev (bleeding edge) and Keras 1.2.1.
I am having issues with using a BatchNormalization layer with the Theano backend as "cuda" (the new backend). I am led to believe that it is an issue with the backend compatibility because the error does not occur if I switch the Theano backend to "gpu" (the old backend).
Here's a snippet of the error
pygpu.gpuarray.GpuArrayException: b'out of memory'
Apply node that caused the error: GpuAllocEmpty{dtype='float32', context_name=None}(Assert{msg='The convolution would produce an invalid shape (dim[0] < 0).'}.0, Assert{msg='The convolution would produce an invalid shape (dim[1] < 0).'}.0, Assert{msg='The convolution would produce an invalid shape (dim[2] <= 0).'}.0, Assert{msg='The convolution would produce an invalid shape (dim[3] <= 0).'}.0)
Toposort index: 256
Inputs types: [TensorType(int64, scalar), TensorType(int64, scalar), TensorType(int64, scalar), TensorType(int64, scalar)]
Inputs shapes: [(), (), (), ()]
Inputs strides: [(), (), (), ()]
Inputs values: [array(400), array(512), array(244), array(1)]
Inputs type_num: [7, 7, 7, 7]
Outputs clients: [[GpuDnnConv{algo='small', inplace=True}(GpuContiguous.0, GpuContiguous.0, GpuAllocEmpty{dtype='float32', context_name=None}.0, GpuDnnConvDesc{border_mode='valid', subsample=(1, 1), conv_mode='conv', precision='float32'}.0, Constant{1.0}, Constant{0.0})]]

I'm using an external 8 GB GPU that normally works with CNMeM 0.97, so 0.75 should not get this out of memory error.
~/.theanorc
[global]
floatX = float32
device = cuda
optimizer = fast_run
exception_verbosity = high

[lib]
cnmem = 0.75

[nvcc]
fastmath = True
flags=-D_FORCE_INLINES

[blas]
ldflags = -llapack

[cuda]
root = /usr/local/cuda-8.0

I believe the following snippet of my model is the problem because commenting the BN line removes the error.
...

model.add(Dense(input_dim=4096, output_dim=1024))
model.add(Activation('relu'))
model.add(BatchNormalization())

model.add(Dropout(0.5))
model.add(Dense(input_dim=1024, output_dim=919))
model.add(Activation('sigmoid'))

model.compile(loss='binary_crossentropy', optimizer='adagrad', metrics=['accuracy'])


Have a tab similar to the snippets for Errors

Currently the error tab is missing, so we are not seeing the error messages.

@imrishabh18 the error tab is in the dropdown menu?


Sending build context to Docker daemon  65.02kB

Step 1/3 : FROM scratch
 --->
Step 2/3 : COPY a a
 ---> 6d79f6948e15
Step 3/3 : COPY b b
 ---> 7557a5e60445
Successfully built 7557a5e60445
Successfully tagged i:latest

$ docker tag i localhost:5000/i

$ docker push localhost:5000/i
Using default tag: latest
The push refers to repository [localhost:5000/i]
f85796042821: Pushed
52f3061f70a4: Pushed
latest: digest: sha256:77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7 size: 729

$ curl -sS -X DELETE localhost:5000/v2/i/manifests/sha256:77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7

$ dc exec registry registry garbage-collect /etc/docker/registry/config.yml
i

0 blobs marked, 4 blobs and 0 manifests eligible for deletion
blob eligible for deletion: sha256:146f597530df28b46439c429612d9d9eee16750ebc013ec84d6f7887e4695d75
time="2022-09-27T14:43:07.415365437Z" level=info msg="Deleting blob: /docker/registry/v2/blobs/sha256/14/146f597530df28b46439c429612d9d9eee16750ebc013ec84d6f7887e4695d75" go.version=go1.16.15 instance.id=0a3319a7-30f4-44ab-a19d-6a98dbc78c25 service=registry
time="2022-09-27T14:43:07.415586415Z" level=info msg="Deleting blob: /docker/registry/v2/blobs/sha256/75/7557a5e6044527646817415a395aa492b81588638ce8971f6c29a0dd37867cc8" go.version=go1.16.15 instance.id=0a3319a7-30f4-44ab-a19d-6a98dbc78c25 service=registry
blob eligible for deletion: sha256:7557a5e6044527646817415a395aa492b81588638ce8971f6c29a0dd37867cc8
time="2022-09-27T14:43:07.415725957Z" level=info msg="Deleting blob: /docker/registry/v2/blobs/sha256/77/77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7" go.version=go1.16.15 instance.id=0a3319a7-30f4-44ab-a19d-6a98dbc78c25 service=registry
blob eligible for deletion: sha256:77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7
blob eligible for deletion: sha256:9dbfa555742d27e03754f1596337d62c164009534b1dc2a8a8fee85d3055eaff
time="2022-09-27T14:43:07.415870529Z" level=info msg="Deleting blob: /docker/registry/v2/blobs/sha256/9d/9dbfa555742d27e03754f1596337d62c164009534b1dc2a8a8fee85d3055eaff" go.version=go1.16.15 instance.id=0a3319a7-30f4-44ab-a19d-6a98dbc78c25 service=registry

$ docker push localhost:5000/i
Using default tag: latest
The push refers to repository [localhost:5000/i]
f85796042821: Layer already exists
52f3061f70a4: Layer already exists
latest: digest: sha256:77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7 size: 729

$ docker pull localhost:5000/i
Using default tag: latest
Error response from daemon: manifest for localhost:5000/i:latest not found: manifest unknown: manifest unknown

Restart the docker-compose project.
$ docker push localhost:5000/i
Using default tag: latest
The push refers to repository [localhost:5000/i]
f85796042821: Pushed
52f3061f70a4: Pushed
latest: digest: sha256:77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7 size: 729

$ docker pull localhost:5000/i
Using default tag: latest
latest: Pulling from i
Digest: sha256:77af0873dec880471c9b057682c54745dc22f453069665d3fd7f880c89ee6cb7
Status: Image is up to date for localhost:5000/i:latest
localhost:5000/i:latest

facing with the same issue on latest distribution build.

The workaround is restarting the registry after garbage collection

are you using the inmemory blob descriptor cache?

According to the docker-compose.yml file above, I guess yes, because that must be the default.

If so, the garbage collector is a separate process, and it can't invalidate the cache which will still think the layers are present for that repository.

If that's a... caveat? then I think it should be documented. Are there any other possible consequences? I mean it sounds like after such a push you definitely want to restart the registry.


Calculator widget

A four-function calculator widget

Widget completed and issue closed. Refer to the Calculator section in the wiki for info on how to set up the Calculator widget, and if you have further requests or questions feel free to comment them here, or create a new issue.


Form functionality in IE8

Had reports of a user on IE8 with almost the same problems as described in #30.
I'm wondering if the IE8 user also did browser back/forth.
In any event, check functionality of form in IE8.

Now works on IE8. There are some design issues, but nothing that prevents functionality.


Swap usage of LazyDLL and LoadDLL to LazySystemDLL

- What I did
This ensures that the DLLs loaded by Docker come from the system folders.
- How I did it
Use NewLazySystemDLL instead of other DLL loading functions for system DLLs.
Signed-off-by: Darren Stahl<EMAIL_ADDRESS>/cc @jhowardmsft @jstarks

LGTM. Marking 1.13 (@thaJeztah FYI)

@darrenstahlmsft nit: include golang.org/x/sys/windows in the same block as the rest of the non-standard imports.

@tonistiigi fixed

LGTM

Experimental failure unrelated, looks like a network glitch. (504)


Editable logic seems reversed

The note about CurrPage.Editable states "If the page is editable, then CurrPage.Editable will return false."
Is it not the other way around?
"If the page is not editable, then CurrPage.Editable will return false."
or
"If the page is editable, then CurrPage.Editable will return true."

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

ID: 6dd6c70d-7fef-0f5a-1a0b-37f102b853f5
Version Independent ID: f5637137-69b3-9b33-1ba6-786ace43bf90
Content: Editable Property - Business Central
Content Source: dev-itpro/developer/properties/devenv-editable-property.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for catching this! You're absolutely right - very important omission of 'not' here. This will be fixed with the next refresh of the docs.


Warning when clicking beyond data in a table

When a table has extra rows, clicking on the extra blank rows generates a warning:
Warning: file:///Users/tgil/Qt-5.8/5.8/clang_64/qml/StratifyLabs/UI/UI.2/STablePrivate.qml:168: Error: Cannot assign [undefined] to int

Table view is completely garbled when trying out the latest Doc from Github