Additional Durable Functions implementation.

This PR continues the Durable Functions implementation:

Changes azure-functions-durable crate to use the released version of the
hyper crate, but with the 0.1.0 futures-compatibility layer.  This fixes the
issue where the reactor could not be found for the client with a 0.1.0
futures-based tokio reactor that is being used by the Azure Functions for Rust
runtime.

Implement the DurableOrchestrationClient binding to wrap an
OrchestrationClient and provide the start_new method.  More methods will be
implemented later.

Implement the DurableActivityContext binding to extract the instance
identifier and input from the binding data.

Implemented a mechanism for outer orchestration futures to control inner
futures for updating the current orchestration event, which should occur
immediately after the future is ready.

Implemented proper replay detection.

Implemented the join_all method on DurableOrchestrationContext.

Implemented the Durable Functions example (still needs documentation).

Various clippy and code clean up fixes.

I'm going to merge this in since this is an active feature branch and we still have a ways to go with the Durable Functions implementation.  We feedback changes can be made with additional PRs.


[2.0] Transition fails to show with components using render functions

Vue.js version
v2.0.0-rc.2
Reproduction Link

https://jsfiddle.net/wy1frr50/3/
Steps to reproduce
Push the button until it cycles back into "First", then push it again
What is Expected?
A fade transition to "Second"
What is actually happening?
Uncaught TypeError: Cannot read property '_pending' of null
After investigation, it sounds like the element being transitioned out is (logically) removed from the dom, but the old reference is still kept. When vue tries to recycle it for rerendering, the reference lacks a parentNode property, leading to this error.

your key assignment was on the VNode instead VNode.data
This works as expected: https://jsfiddle.net/Linusborg/wy1frr50/4/

You should not be mutating the vnode's key in mounted - by that time the vnodes have already been rendered into real DOM nodes, mutating them in mounted doesn't do anything.
Instead, do that directly in the render function before returning them: https://jsfiddle.net/80nazax6/

Btw, there's no need for h(Vue.options.components['Transition']) - just h('transition') will do.
And there's also no need for registering Elm and Container and then retrieve them from this.$options.components, just use them directly.
https://jsfiddle.net/80nazax6/1/

@yyx990803 That does not fix the error described in this issue, unfortunately.  _If I click the button in your latest fiddle until "Second" appears for the second(!) time, you will see the error in the console, and clicking the button again won't transition to "third"

Thanks for the advices regarding the unnecessary boilerplate!
Your solution doesn't seem to fix the issue, though, as @LinusBorg mentioned


Support for stdin processing

I have an in memory byte array that I would like to process with exiftool.
The tool itself supports reading from stdin however node-exiftool seems to only accept disk files.
Is this a trivial change or would need more work? Happy to provide a PR.

Whoops I just opened a dupe #53.

Is there an update on this issue by any chance? Perhaps an example or fix?


Fix typo (used Typescript instead of Typeshare)

I was reading the documentation for this interesting project and found a small error!
Thanks for sharing!

Great catch! Thanks 😄


[Doc] Add Chinese version of getting start doc

This PR adds a Chinese version of getting_start.
Meanwhile, this PR also called on the community to produce Chinese documents. (Adding News in README.md and READ_zh_CN.md)

Need to resolve conflicts.


Sui TypeScript SDK: Add formatAmount() util

Problem/Motivation
It would be good to have a standard way to format Sui amounts with TypeScript SDK, like existing formatDigest() or formatAddress().
It's a very trivial operation and it's necessary for many projects, so it deserves to be standardised, in my opinion.
And, moreover, you already have it implemented here: formatAmount()
Look how even example projects now have to copy&paste the code. Not the best way because you cannot pull the latest bug fixes and updates automatically.
Proposed resolution
Move formatAmount() function from apps to TypeScript SDK utils.

Considering @hayes-mysten point in the related PR, I think we can close this issue.


update deprecated Actions

see for example https://github.com/mandiant/flare-floss/actions/runs/3836568797
checkout and setup-python

Hi @mr-tz ,  could you please elaborate about this problem a little bit ?

in the linked action run are the warnings:

we fixed similar warnings in capa like here: https://github.com/mandiant/capa/pull/1233

Hi @williballenthin , the below mentioned actions are to be updated to @v3 ; am I thinking right ?
Run actions/checkout@v2
Run actions/setup-python@v2

Yes, there's a few that need version bumps.

Hi @mr-tz , could you please guide me to the file links that needed the upgrade ; as I could not find out the files ?

should I update the test.yml file  uses: actions/checkout@v3 to v4  ?

The newest version is probably best, yes.

@mr-tz I want to give this a try, please assign me this issue.

Go for it :)

there's no warning, but publish and test are not pinned like build yet, I'm fine closing this issue here though

lets update this issue to track the pinning of those two actions and then @ooprathamm can take on this task?

@williballenthin can I ask why are we using '@' rather than '<@v'
as it does look clean :)

See for example https://securitylab.github.com/research/github-actions-building-blocks/

See for example https://securitylab.github.com/research/github-actions-building-blocks/

Thanks, @mr-tz, for expanding my knowledge with your helpful insights.

totally agree that "v3" looks better, but in this case, i think a bit more security is worth the visual noise


Need to fix fallback/season search for ETTV

Similar the issue I had with ygg (https://github.com/elgatito/script.elementum.burst/issues/142)
search url from the log, for example:
https://www.ettv.to:443/torrents-search.php?search=vikings s2&cat=0&incldead=0&lang=0
It searching with this format of "s2" instead of "s02"
Thanks.

@elgatito
Can you please check this request?
Thanks.

Regarding ETTV and also MagnetDL
Elementum Burst 0.0.42
Elementum : 0.1.44
Kodi Log: https://paste.ubuntu.com/p/5yTmGCrWfq/
Why when I run this url in a browser I get results:
The fallback url:
ETTV search URL:  https://www.ettv.to/torrents-search.php?search=westworld%20s02&cat=0&incldead=0&lang=0
Episode URL:
ETTV search URL: https://www.ettv.tv/torrents-search.php?search=westworld%20s02e03&cat=0&incldead=0&lang=0
But in the log ETTV return 0 results, why?
ETTV returned  0 results in 20.8 seconds

By the way, what is this url?
Episode URL: https://www.ettv.tv/torrents-search.php?search=QUERYEXTRA&cat=0&incldead=0&lang=0

What is "QUERYEXTRA" and why does it search for it?

I also see this strange fallback url:
https://www.ettv.tv/torrents-search.php?search=westworld%2002x01%7CS02&cat=0&incldead=0&lang=0

Which searching for:
westworld 02x01|S02
Instead of
westworld S02
Like the first one.

Also regarding MagnetDL:
In the log MagnetDL return 0 results, why?
MagnetDL returned  0 results in 13.7 seconds
The fallback url: (Has results)
MagnetDL search URL: https://www.magnetdl.com/v/vikings-s03/
Episode URL: (Has results)
MagnetDL search URL: https://www.magnetdl.com/v/vikings-s03e01/

By the way, what is this url?
(This url doesn't work: 404)
MagnetDL search URL: https://www.magnetdl.com/v/vikings-03x01%7CS03/

The same regarding the "QUERYEXTRA":
Episode URL: https://www.magnetdl.com/FIRSTLETTER/QUERYEXTRA/

MagnetDL always returns empty page, probably because of some defense.
ETTV will be fixed in the next version.

Thanks.
So for now is MagnetDL useless?
We can do something about that?

So for now is MagnetDL useless?

Probably.

Can we do something about that?

Not from my side. I already tried to fix.

But how I do get MagnetDL result when testing with the old Quasar & Quasar Burst
Kodi Log: https://paste.ubuntu.com/p/cp3XPR4T9T

@burekas7 you can investigate, make appropriate changes and submit a PR. PRs are always welcome.

But I don't have access to the code (it's exe file),
and I don't know how it actually works besides the search urls from the log.

Update to Burst 0.0.44.
Magnetdl should work. They have filters on http headers.
Code of Elementum is open: https://github.com/elgatito/elementum

Regarding 0.0.44

ETTV:
In 0.0.43 I did get result from ETTV but they wasn't included in the results screen. (Why?)
But in 0.0.44 it back again show 0 results from ETTV.

Kodi Log (0.0.44) : https://paste.ubuntu.com/p/jGgwy2RCg9

ettv would send 0 torrents to Elementum <<<<<<<
Kodi Log (0.0.43): https://paste.ubuntu.com/p/h9skY9SYy2
ettv would send 3 torrents to Elementum <<<<<<<

MagnetDL:
Works ok now, Thanks.

When I run for The Witcher S01E04
ETTV found results but they are not shown in the results screen
[ettv] >>>>>> ettv would send 4 torrents to Elementum <<<<<<<
Kodi Log: https://paste.ubuntu.com/p/fS352zCgcq
But when I run it for Westworld S02E03 the results from ETTV are shown.
[ettv] >>>>>> ettv would send 3 torrents to Elementum <<<<<<<
Kodi Log: https://paste.ubuntu.com/p/cTWmZgScJb/
What is the difference?


Updating/Accessing RenderingDevice buffer data after submit() causes crashes without error

Godot version
4.0
System information
Windows 10, RTX 2070 Super, Driver v516.94, Vulkan
Issue description
When attempting to update or access RenderingDevice buffer data with buffer_get_data() or buffer_update(), after calling submit() and before calling sync(), the project hangs and then crashes without error.
This wasn't a problem for my project at first, but I ended up needing to dispatch my shader with varying amounts of data, causing inconsistent wait times. At some point this resulted in my code trying to update the buffer before the RenderingDevice was synced, causing the crash. I was able to remedy this by creating a boolean is_waiting that is set to true after submitting, but I noticed in the source code there is already a variable that does this (RenderingDevice.local_device_processing). If possible, perhaps exposing that variable to GDScript through a is_local_device_processing() function would help.
EDIT: Note that I've only tested this with buffer_get_data() and buffer_update(). This very well may be the case for others like textures and vertex buffers as well.
Steps to reproduce
I've included a reproduction project.
In Node.gd you can uncomment the code between rd.submit() and rd.sync() (on lines 35 and 37/38) and run the project to reproduce the crash.
Minimal reproduction project
RDIsWaitReproduction.zip

After some RocketChat discussion, we decided to keep this issue open. The more general problem is the lack of error checking in some RenderingDevice methods. Some issues like this might be preventable with a few added error checks. clayjohn suggested something like in this:
ERR_FAIL_COND_MSG(local_device_processing, "device already submitted, can't record commands until after sync is called.");
to be added in methods like RenderingDevice.buffer_get_data() which require a sync() to be called first. Other places where these kinds of checks are needed should also be investigated. Still, as RenderingDevice API is pretty low-level it will probably always be possible to create situations which we can't check effectively. Using Vulkan validation layers when developing code like this is a good idea.


Avoid using deprecated CDI API that is removed from CDI 4.

This came up in an EE 10 effort for WFLY 10, see also https://github.com/wildfly/wildfly/pull/15252
BeanManager#createInjectionTarget method was deprecated and in CDI 4 is removed.
I also quickly checked on other deprecations that happened for CDI 4 but didn't see any other usages in this repo.
The list of removals can be seen here - https://github.com/eclipse-ee4j/cdi/issues/472

BTW I tried creating a JIRA but my account has apparently been deactivated :)

@manovotn Great minds think alike ;)  https://github.com/hibernate/hibernate-orm/pull/4826 / https://hibernate.atlassian.net/browse/HHH-15084

Closing in favor of https://github.com/hibernate/hibernate-orm/pull/4826

thanks :) @manovotn let me know if you need help with your account!


Add LZMA support to CMake build

This looks for the LZMA library and sets HAVE_LZMA_H if found. It also links the inkcache library to LZMA.

[approve ci autest]

[approve ci autest]

[approve ci autest]

[ci approve autest]

[approve ci autest]

[approve ci autest]


[WiP] Add support for multiple CIDRS in the Net fields.

@robbrockbank what do you think to this approach to adding multiple CIDRs into rules?  The good is that it's back-compatible; the bad is that the field is called Net but it can now be a string or a list.

I'm ok with this barring comments inline, but worth getting other peoples opinions on this too.
Could we just flag this as deprecated and have a new field?  We could assert that only one or the other be used so the user cannot mix both formats, and then stop documenting the old one.

Probably too horrible to have to stash a flag somewhere for 1-vs-list.  Why don't I just add a Nets list

@fasaxc @robbrockbank am I right in thinking this is superseded by https://github.com/projectcalico/libcalico-go/pull/470?
If so, let's close this and remove it from the v2.4.0 milestone.

@fasaxc Closing the issue - I think this is now obsolete.  Feel free to re-open if that is incorrect.


[PYSPARK] Refactor the python process watcher

Why are the changes needed?

Before:

After:

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks, merged to master


truncate: Invalid number:

Hi there, this is my first time submitting an issue so please let me know if I can provide more information.
I used shrinkwrap on my Rpi4b to shrink a backup image file on an attached USB drive. I created the image with win32diskimager.
There's an error that re-reading the partition table failed, but also a note to "ignore that error and everything seems fine until nearly the end. At the point where the script attempts to truncate the img file, I get the error "truncate: Invalid number: ‘8.51628e+09’" and the source file remains at a full un-shrunken size. Full log is attached and pasted below:
shrinkwrap log.txt
pi@nasberry:~/shrinkwrap $ sudo ./shrinkwrap.sh /home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img
Disk /home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img: 119.3 GiB,<PHONE_NUMBER>12 bytes, 250085376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e3da3da
Device                                                                         Boot  Start       End   Sectors  Size Id Type
/home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img1        8192    532479    524288  256M  c W95
/home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img2<PHONE_NUMBER>85375 249552896  119G 83 Linu
START of partition: 532480
losetup: /dev/loop0: detach failed: No such device or address
Good - no /dev/loop0 is already free
NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0       7:0    0 119.3G  0 loop
├─loop0p1 259:0    0   256M  0 part
└─loop0p2 259:1    0   119G  0 part
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 197549/7768320 files (0.5% non-contiguous), 2186120/31194112 blocks
resize2fs 1.44.5 (15-Dec-2018)
Resizing the filesystem on /dev/loop0p2 to 2012607 (4k) blocks.
Begin pass 2 (max = 250881)
Relocating blocks             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 3 (max = 952)
Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 4 (max = 19052)
Updating inode references     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on /dev/loop0p2 is now 2012607 (4k) blocks long.
dumpe2fs 1.44.5 (15-Dec-2018)
Filesystem volume name:   rootfs
Last mounted on:          /
Filesystem UUID:          efc2ea8b-042f-47f5-953e-577d8860de55
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file dir_nlink extra_isize
Filesystem flags:         unsigned_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              505920
Block count:              2012607
Reserved block count:     81508
Free blocks:              284329
Free inodes:              308371
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      389
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8160
Inode blocks per group:   510
Flex block group size:    16
Filesystem created:       Wed Sep 25 19:44:35 2019
Last mount time:          Sun Nov 24 21:49:52 2019
Last write time:          Wed Nov 27 09:28:57 2019
Mount count:              0
Maximum mount count:      -1
Last checked:             Wed Nov 27 09:19:04 2019
Check interval:           0 ()
Lifetime writes:          42 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      2a510282-7c57-4970-8f9a-1514cd4b5a23
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             64M
Journal length:           16384
Journal sequence:         0x000275a4
Journal start:            0
NEW SIZE of partition: 16100872  512-blocks
Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): Disk /dev/loop0: 119.3 GiB,<PHONE_NUMBER>12 bytes, 250085376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e3da3da
Device       Boot  Start       End   Sectors  Size Id Type
/dev/loop0p1        8192    532479    524288  256M  c W95 FAT32 (LBA)
/dev/loop0p2<PHONE_NUMBER>85375 249552896  119G 83 Linux
Command (m for help): Partition number (1,2, default 2):
Partition 2 has been deleted.
Command (m for help): Partition type
p   primary (1 primary, 0 extended, 3 free)
e   extended (container for logical partitions)
Select (default p): Partition number (2-4, default 2): First sector (2048-250085375, default 2048): Last sector, +/-sectors or +/-size{K,M,G,T,P}<PHONE_NUMBER>85375, default 250085375):
Created a new partition 2 of type 'Linux' and of size 7.7 GiB.
Partition #2 contains a ext4 signature.
Command (m for help):
Command (m for help):
Disk /dev/loop0: 119.3 GiB,<PHONE_NUMBER>12 bytes, 250085376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e3da3da
Device       Boot  Start      End  Sectors  Size Id Type
/dev/loop0p1        8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/loop0p2<PHONE_NUMBER>3352 16100873  7.7G 83 Linux
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Invalid argument
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
Ignore that error.
Disk /home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img: 119.3 GiB,<PHONE_NUMBER>12 bytes, 250085376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e3da3da
Device                                                                         Boot  Start      End  Sectors  Size Id Type
/home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img1        8192   532479   524288  256M  c W95
/home/pi/Desktop/NASBerry/12-Backups/00_NASBerry/20191126_NASBerry_Backup.img2<PHONE_NUMBER>3352 16100873  7.7G 83 Linu
TRUNCATE AT: 8.51628e+09 bytes
truncate: Invalid number: ‘8.51628e+09’
`

I have the same issue running in my Raspberry Pi 4 with 32bit or 64bit raspbian OS, the partition has been resized, but the file size is not changed.
Thanks mtyka for sharing the tools to shrinkwrap the image file, it can easily backup and restore the SD card even to other SD card with slightly difference in size, which can solve the issue of block size difference among brands.  It'd be better if the file size can be reduced while the partition is resized.

same thing:
sudo ./shrinkwrap/shrinkwrap.sh ./rPi_clean_backup_shrinked.img
Disk ./rPi_clean_backup_shrinked.img: 29.8 GiB,<PHONE_NUMBER>8 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2e343b40

Device                           Boot  Start      End  Sectors  Size Id Type
./rPi_clean_backup_shrinked.img1        8192   532479   524288  256M  c W95 FAT32 (LBA)
./rPi_clean_backup_shrinked.img2<PHONE_NUMBER>1343 61988864 29.6G 83 Linux
START of partition: 532480
NAME      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0       7:0    0 29.8G  0 loop
├─loop0p1 259:0    0  256M  0 part
└─loop0p2 259:1    0 29.6G  0 part
e2fsck 1.44.5 (15-Dec-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 230623/1937712 files (0.1% non-contiguous), 2029045/7748608 blocks
resize2fs 1.44.5 (15-Dec-2018)
Resizing the filesystem on /dev/loop0p2 to 2046430 (4k) blocks.
Begin pass 2 (max = 920219)
Relocating blocks             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 3 (max = 237)
Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 4 (max = 26014)
Updating inode references     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The filesystem on /dev/loop0p2 is now 2046430 (4k) blocks long.

dumpe2fs 1.44.5 (15-Dec-2018)
Filesystem volume name:   rootfs
Last mounted on:          /tmp/tmp.irUfXwyZ9S
Filesystem UUID:          05c2c54d-f13e-4442-bf69-70e99c3d748d
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags:         unsigned_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              515088
Block count:              2046430
Reserved block count:     102321
Free blocks:              108720
Free inodes:              284465
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      1024
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8176
Inode blocks per group:   511
Flex block group size:    16
Filesystem created:       Thu Aug 27 19:29:10 2020
Last mount time:          Sat Aug 29 12:31:33 2020
Last write time:          Sat Aug 29 18:16:14 2020
Mount count:              0
Maximum mount count:      -1
Last checked:             Sat Aug 29 18:13:15 2020
Check interval:           0 (<none>)
Lifetime writes:          12 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:	          256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      310f2866-8a93-434c-a35b-403619b3c1af
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x98a0f5fe
Journal features:         journal_64bit journal_checksum_v3
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00000192
Journal start:            0
Journal checksum type:    crc32c
Journal checksum:         0x1f3ea62a

NEW SIZE of partition: 16371456  512-blocks

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Command (m for help): Disk /dev/loop0: 29.8 GiB,<PHONE_NUMBER>8 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2e343b40

Device       Boot  Start      End  Sectors  Size Id Type
/dev/loop0p1        8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/loop0p2<PHONE_NUMBER>1343 61988864 29.6G 83 Linux

Command (m for help): Partition number (1,2, default 2):
Partition 2 has been deleted.

Command (m for help): Partition type
   p   primary (1 primary, 0 extended, 3 free)
   e   extended (container for logical partitions)
Select (default p): Partition number (2-4, default 2): First sector (2048-62521343, default 2048): Last sector, +/-sectors or +/-size{K,M,G,T,P}<PHONE_NUMBER>1343, default 62521343):
Created a new partition 2 of type 'Linux' and of size 7.8 GiB.
Partition #2 contains a ext4 signature.

Command (m for help):

Command (m for help):
Disk /dev/loop0: 29.8 GiB,<PHONE_NUMBER>8 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2e343b40

Device       Boot  Start      End  Sectors  Size Id Type
/dev/loop0p1        8192   532479   524288  256M  c W95 FAT32 (LBA)
/dev/loop0p2<PHONE_NUMBER>3936 16371457  7.8G 83 Linux

Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Invalid argument

The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).

Ignore that error.
Disk ./rPi_clean_backup_shrinked.img: 29.8 GiB,<PHONE_NUMBER>8 bytes, 62521344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2e343b40

Device                           Boot  Start      End  Sectors  Size Id Type
./rPi_clean_backup_shrinked.img1        8192   532479   524288  256M  c W95 FAT32 (LBA)
./rPi_clean_backup_shrinked.img2<PHONE_NUMBER>3936 16371457  7.8G 83 Linux
TRUNCATE AT: 8.65482e+09 bytes
truncate: Invalid number: ‘8.65482e+09’

Looks like problem in the disk ( I do this in HDD attached disk, prbably it's partition scheme different)

The problem is that the print statement that passes the new file size in bytes for truncate to operate on converts to scientific notation once you get past a certain size.  Change line 50:
FINALEND_BYTES=$(cat /tmp/fdisk_new.log | grep "83 Linux" | awk '{print ($3+1)*512}')
to use printf instead:
FINALEND_BYTES=$(cat /tmp/fdisk_new.log | grep "83 Linux" | awk '{printf "%.0f", ($3+1)*512}')
Now instead of an output like "TRUNCATE AT: 8.65482e+09 bytes", you'll get "TRUNCATE AT:<PHONE_NUMBER>42769 bytes" and the truncate should work.

Hi. We've just bumped into this issue. We can open a pull request with the fix. Does that sound good?


[Feature Request] Clear background image after Detect From Image

Is your feature request related to a problem? Please describe.
The Detect From Image feature loads the image into the background. The background cannot be cleared. When designing a pose for a new scene, a background image is not needed; it only makes it harder to see what you're doing when you edit the pose.
Even Reset Scene does not clear it.
Describe the solution you'd like
Three parts:

A setting, whether to load the image as background, when Detect From Image is used.

If enabled, current behavior.
If disabled, just use the image to detect the pose. Don't use the image as background.

A button to clear the background to its default state (no image).
Reset Scene should clear the background image.

Describe alternatives you've considered
Simply never load the image into the background. May break workflow, if some users prefer to have the image as reference.
The suggested setting, if disabled, could remove the background image after a short timeout, or after the user either moves/rotates the camera, or starts editing the pose. After these actions the pose no longer corresponds to the image anyway.
What is good in the current behavior is that it visually shows how well the pose was detected.

bump.
The only way to remove the background image right now is to refresh the browser window, which is pointless and time-consuming.

bump x2. Strange that this is still the case from what I can tell.

On the other hand, the code hasn't been touched since last spring.
Maybe the author has lost interest and moved on to other projects?
Speaking as an open source author myself, at least I have accumulated too many repos that I have no interest to work on any more. There's always the next new shiny idea to pursue :)


fix: flatten vm array to fix sort casuing error in caprover and workers based solutions

Description
flatten vm array to fix sort casuing error in caprover and workers based solutions
Changes

group workers of vms into an array in leader objec

Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/1726

Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings
[ ] Screenshots/Video attached (needed for UI changes)

in case the deployment doesn't have workers, this error happens when trying to click on manage button

in case the deployment doesn't have workers, this error happens when trying to click on manage button
...
fixed


Updating name typo in II MIG post

Quick typo correction to the II MIG post. Correcting from 'Colonel Russel' to 'Colonel Russell.'

Duplicate PR with #60 . Closing this one.


feat: sync button with design

#ref #99

Type of change

[ ] Documentation (updates to the documentation, readme or JSDoc annotations)
[ ] Bug fix (a non-breaking change that fixes an issue)
[ ] Enhancement (improving an existing functionality like performance)
[x] New feature (a non-breaking change that adds functionality)
[ ] Refactoring (old API is revised and supported)
[ ] Chore (updates to the build process or auxiliary tools and libraries)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Related issue

Related #99 (issue)

📸 Screenshots (if appropriate)

Checklist

[ ] I have linked an issue or discussion;
[ ] I have updated the documentation accordingly;
[ ] I have added or updated tests to cover my changes;
[ ] I have performed a self-review of my code;
[ ] My code follows the style guidelines of this project;
[ ] My changes generate no new warnings.

@leonid this PR for discussion. Designers have 5 variants and don't have list of all colors. I think we can ask them to remove status variant because this is just a primary variant with danger color?


Support for RPM based installation

In addition to the apt based installation, it would be great if this cookbook worked for RPM based system. Looks like Grafana supports it: http://docs.grafana.org/installation/rpm/

Version 0.3.0 supports rpm based systems. Thanks @daharon for the contribution!


Address line break error in logger

[ ] Logger is breaking messages up by line breaks and not in one single message, potentially due to cloud.gov parsing the messsage and passing it in as separate errors.

Will speak to cloud.gov in office hours 7/19 to see if it is something that can be modified or if there are ways to circumvent the parsing

Ticket no longer needed


How to create templates for a new species

Dear Sir,
I am writing to inquire about a specific software mentioned in the user's manual of Stitch. According to the manual, it is stated that the software, assembler.exe, is capable of generating templates for a new species. However, I am uncertain about the exact details of assembler.exe and where I can download it. I was wondering if you could kindly provide me with more information regarding this software.
-assembler.exe download "Homo sapiens"
-assembler.exe download "Cricetinae gen. sp." "IGHV IGKV,IGLV IGHJ IGLC"
Thank you very much for your attention and assistance. I look forward to your reply.
Best regards,
wb J

Thank you for opening the issue.
The assembler.exe mentioned here is the old name for the stitch.exe this is fixed in newer version of the manual. Since the release of 1.4.0 I reworked the download code quite a bit, and added some additional fixes today thanks to your question, if the release of 1.4.0 breaks when downloading you can try with the nightly version.
Also note that this scrapes the following webpage from IMGT so anything that is not listed there cannot be downloaded by this program.
If you have any other questions feel free to reach out. And if the download does not work out for the species you want to work with, feel free to ask me, I could try the template preparation from my side.

Thank you for opening the issue. The assembler.exe mentioned here is the old name for the stitch.exe this is fixed in newer version of the manual. Since the release of 1.4.0 I reworked the download code quite a bit, and added some additional fixes today thanks to your question, if the release of 1.4.0 breaks when downloading you can try with the nightly version.
Also note that this scrapes the following webpage from IMGT so anything that is not listed there cannot be downloaded by this program.
If you have any other questions feel free to reach out. And if the download does not work out for the species you want to work with, feel free to ask me, I could try the template preparation from my side.

The nightly version may not be as user-friendly. Are there any associated manuals or documentation available?


[Proposal] Add or update license text for SPDX compliance

Signed-off-by: Michael Robinson<EMAIL_ADDRESS>Problem
License text across the project is either in the outdated block format or missing.
Solution
This PR adds machine-readable SPDX license lines across the project, replacing block text where needed.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
Checklist

[x] You've signed-off your work
[ ] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[x] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)

Codecov Report

Merging #535 (32d7252) into main (a16c6a2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #535   +/-   ##
=======================================
  Coverage   84.03%   84.03%
=======================================
  Files          35       35
  Lines        2061     2061
=======================================
  Hits         1732     1732
  Misses        329      329

Impacted Files
Coverage Δ

client/python/openlineage/client/__init__.py
100.00% <ø> (ø)

client/python/openlineage/client/client.py
82.97% <ø> (ø)

client/python/openlineage/client/constants.py
100.00% <ø> (ø)

client/python/openlineage/client/facet.py
88.79% <ø> (ø)

client/python/openlineage/client/run.py
100.00% <ø> (ø)

client/python/openlineage/client/serde.py
96.00% <ø> (ø)

...ntegration/airflow/openlineage/airflow/__init__.py
100.00% <ø> (ø)

integration/airflow/openlineage/airflow/adapter.py
100.00% <ø> (ø)

integration/airflow/openlineage/airflow/dag.py
75.00% <ø> (ø)

...airflow/openlineage/airflow/extractors/__init__.py
100.00% <ø> (ø)

... and 23 more

Continue to review full report at Codecov.

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

@merobi-hub Can you exclude files integration/airflow/tests/data/great_expectations/data/yellow_tripdata_sample_2019-01.csv and integration/airflow/tests/data/great_expectations/data/yellow_tripdata_sample_2019-02.csv from this change? Thanks.

@mobuchowski Thanks. I removed those .csv files.

@merobi-hub you removed them from repository, not the commit 🙂

The original files should be back in the repo now.

Merged via https://github.com/OpenLineage/OpenLineage/pull/540


Add files via upload

hallamcitycampus.txt created under lib/domains/com

@ChethuR First stage of verification passed, official domain is swargaranischool.com as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@ChethuR Pull request merged. Thank you.


Finalize bleeding station scene

[x] fix spawners
[x] fix buttons
[x] Add configured GameManager

#480


Bump minimum PHP version requirement

Feature Description

Last summer we changed the minimum version requirements for the WordPress plugin from PHP 5.6 and WP 5.3 to PHP 7.0 and WP 5.5, respectively. See #7551 for background.
The current telemetry numbers are promising enough that we should look into bumping the PHP version requirement even further.
Excerpt of telemetry data for the Web Stories plugin from our own analytics:

PHP Version
	Percentage (rounded)

7.0
	0.4%

7.1
	0.3%

7.2
	4%

7.3
	16%

7.4
	69%

8.0
	7%

8.1
	0.1%

The highlights:

Less than 0.4% of users are on PHP 7.0
Less than 0.3% of users are on PHP 7.1

PHP 7.2 usage is still reasonably high, so my takeaway is to bump the minimum version requirement to PHP 7.2.
This would allow us to use more modern techniques in PHP development and drop some old baggage.
It would also make our build tooling a bit easier to maintain, since we currently install PHP-Scoper, PHPStan and others via civicrm/composer-downloads-plugin since they require newer versions of PHP, accumulating quite a few workarounds to make things work on PHP <7.2.
Composer 2.3 will also increase the required PHP version to >=7.2.5, see https://blog.packagist.com/composer-2-2/
Alternatives Considered

Additional Context

+1 to this.
Recommended version of PHP is 7.4. See https://wordpress.org/about/requirements/. There has also been talk, for some time about upping in the min version to PHP 7.2. But with the pandemic, this conversion seems to gone a little quite.

I wonder if we should look at https://github.com/GoogleForCreators/web-stories-wp/issues/7754 again?


Is it possible to support midea heat pump controller KJRH-120H (device type C3)?

It is recognized by midea discover as type 'C3':
{'name': 'net_c3_0074', 'ssid': 'net_c3_0074', 'ip': '<IP_ADDRESS>', 'port': 6444, 'id': '...', 'version': 3, 'token': '...', 'key': '...', 'type': 'c3', 'sn': '0C3310171H120F22214100074WC9N', 'model': 'H120F', 'support': False, 'run_test': True}
It already partially works with your integration when I select type "CF" heat pump. On/Off works but setting the temperature doesn't work, so I guess the attributes are different for type C3.

It is recognized by midea discover as type 'C3': {'name': 'net_c3_0074', 'ssid': 'net_c3_0074', 'ip': '<IP_ADDRESS>', 'port': 6444, 'id': '...', 'version': 3, 'token': '...', 'key': '...', 'type': 'c3', 'sn': '0C3310171H120F22214100074WC9N', 'model': 'H120F', 'support': False, 'run_test': True}
It already partially works with your integration when I select type "CF" heat pump. On/Off works but setting the temperature doesn't work, so I guess the attributes are different for type C3.

Is it already bound to your MSmartHome app?
Could you send your username and password for MSmartHome to<EMAIL_ADDRESS>so that to get the protocol plugin of this device.

It is recognized by midea discover as type 'C3': {'name': 'net_c3_0074', 'ssid': 'net_c3_0074', 'ip': '<IP_ADDRESS>', 'port': 6444, 'id': '...', 'version': 3, 'token': '...', 'key': '...', 'type': 'c3', 'sn': '0C3310171H120F22214100074WC9N', 'model': 'H120F', 'support': False, 'run_test': True}
It already partially works with your integration when I select type "CF" heat pump. On/Off works but setting the temperature doesn't work, so I guess the attributes are different for type C3.

Could you send your username and password of MSmartHome to<EMAIL_ADDRESS>so that to get the protocol plugins for that device.

It is recognized by midea discover as type 'C3': {'name': 'net_c3_0074', 'ssid': 'net_c3_0074', 'ip': '<IP_ADDRESS>', 'port': 6444, 'id': '...', 'version': 3, 'token': '...', 'key': '...', 'type': 'c3', 'sn': '0C3310171H120F22214100074WC9N', 'model': 'H120F', 'support': False, 'run_test': True}
It already partially works with your integration when I select type "CF" heat pump. On/Off works but setting the temperature doesn't work, so I guess the attributes are different for type C3.

Could you send your username and password of MSmartHome (or NetHome Plus?) to<EMAIL_ADDRESS>so that to get the protocol plugins for that device.

Thanks for your help, I'll send you my credentials. I have a relabled midea device by another distributor, so you have to use a different app Comfort Home. But it's essentially a MSmartHome clone and seems to communicate via the midea cloud. So I hope it's sufficient to get the protocol plugins you need.
MSmartHome doesn't work because it expects a different ssid "midea_c3_xxxx" instead of "net_c3_xxxx". NetHome Plus doesn't work because it doesn't support the device H120F.

Thanks for your help, I'll send you my credentials. I have a relabled midea device by another distributor, so you have to use a different app Comfort Home. But it's essentially a MSmartHome clone and seems to communicate via the midea cloud. So I hope it's sufficient to get the protocol plugins you need. MSmartHome doesn't work because it expects a different ssid "midea_c3_xxxx" instead of "net_c3_xxxx". NetHome Plus doesn't work because it doesn't support the device H120F.

Comfort Home does not work in my Android emulator, I'll find another way.

Thanks for your help, I'll send you my credentials. I have a relabled midea device by another distributor, so you have to use a different app Comfort Home. But it's essentially a MSmartHome clone and seems to communicate via the midea cloud. So I hope it's sufficient to get the protocol plugins you need. MSmartHome doesn't work because it expects a different ssid "midea_c3_xxxx" instead of "net_c3_xxxx". NetHome Plus doesn't work because it doesn't support the device H120F.

It's weird, I did't found any device bound to your account, but the captured message says you have a device. Maybe this device does not support Comfort Home for iOS?

{
	"msg": "ok",
	"result": {
		"list": [{
			"registerTime": "",
			"onlineStatus": "1",
			"type": "0xC3",
			"homegroupId": "",
			"userId": "692XXXXX",
			"tsn": "",
			"mac": "",
			"des": "",
			"activeStatus": "1",
			"homegroupCreateUserId": "",
			"wifiVersion": "056XXXXXX",
			"name": "Wärmepumpe",
			"modelNumber": "",
			"homegroupNumber": "",
			"id": "146235XXXXXXXXX",
			"sn": "3813a695541c4bc2162c88a38XXXXXXXXXXXXXXX00c911abd6a47aff31950b0f8e86715e6fc728089f70b5a",
			"userType": "1"
		}]
	},
	"errorCode": "0"
}

The device should be supported by Comfort Home IOS. In fact this app only supports one device type, C3. However, I also had this "no device" behaviour once on android. Maybe I messed something up in the backend because tried different versions (also downgrade) of the app while experimenting. I'll try to delete the device and pair it again.
Or if the steps are easy to follow maybe I can get you the information you need from the android app?

Okay, I have now re-paired the device and also changed the name from "Wärmepumpe" to "Heatpump". Maybe the app has problems with German non ascii characters. Hopefully it's now visible in the iOS app.

Okay, I have now re-paired the device and also changed the name from "Wärmepumpe" to "Heatpump". Maybe the app has problems with German non ascii characters. Hopefully it's now visible in the iOS app.

Nothing changed, even I can't found any devices in captured message.

That's weird, the android app works just fine. Can I somehow extract the info you need or are there too many steps?

That's weird, the android app works just fine. Can I somehow extract the info you need or are there too many steps?

Comfort Home app control your device via HTTPS, I guess it detects your device model and downloads a protocol plugin for device, just like MSmartHome and NetHome Plus app, I need to find out the download-url of plugin. Maybe you need to capture the app's message if you can.

I managed to decrypt the traffic, is this the url you are looking for?
https://hbtapp-prod.midea.com/pluginInfo/download?appVersion=2.0.0&appClientType=android&deviceType=0xC3&deviceSn8=171H120F

Great!
Do you have the manual of your appliance in pdf format?

Hello, I have the same cunt pump model : H120F. I was able to install the integration. Unfortunately, it does not read the heat pump correctly. Has anything changed in the topic?

2022-09-03 15:24:50.770 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Status update: {'available': False}
2022-09-03 15:24:55.837 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Connected
2022-09-03 15:24:55.838 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Handshaking
2022-09-03 15:24:55.914 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Authentication success
2022-09-03 15:24:55.915 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Sending: {'header': 'aa1dcf000000000000a0', 'body': '00000000000000000000000000000000000000', 'message type': 'a0', 'body type': 'None'}
2022-09-03 15:25:05.931 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Sending: {'header': 'aa0bcf00000000000003', 'body': '01', 'message type': '03', 'body type': '01'}
2022-09-03 15:25:15.948 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Does not supports the protocol MessageQuery, ignored
2022-09-03 15:25:15.949 DEBUG (PC Midea) [custom_components.midea_ac_lan.midea.core.device] [1] Refresh status is timed out

Supported in v0.3.15


Remove resuseport from proxy listen

What this PR does / why we need it:
I should have been more diligent when checking legacy support in #47. Turns out there's a lot of stuff still common in the wild (everything <1.3.0) that still doesn't support resuseport in listens.
The good news is that next is working as intended to catch this sort of thing before release!
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the next branch and targets next, not master
[x] Title of the PR and commit headers start with chart name (e.g. [kong])

Another reason to make this configurable rather than hard-coding.


Add CLI for Microsoft 365 to Delete a library exceeding the list threshold limit. Remove the files and folders before deleting the library

🎯 PR aim
Add CLI for Microsoft 365 equivalent 👨💻 -
https://pnp.github.io/script-samples/spo-remove-large-library/README.html?tabs=pnpps
✔ What was done

[X] small correction of current PS1 script version
[X] updated readme with script
[X] updated sample.json

🔗 Related
#215
📸 Result
result of the script

Hey @Adam-it, thank you for another cool conversion to CLI!! 👏😊 This should be live shortly 😊

Thanks for the opportunity 👍
I was planning to do a lot more but currently I've a baby on board in progress situation 😂. Trying to learn totally new skills 🍼

@Adam-it - congratulations! Enjoy every moment :-)


pull and overwrite

I pulled changes without having made any locally and it generated a .previous. Should we always be generating .previous whenever we do pull? Is there a way to set a flag that overwrites or am I using it wrong? And is the intention to feel like git? If so, git doesn't let you pull when there are unpushed local changes. Perhaps it could work like that?

I think we should be always generating .previous until the pull command becomes smarter. Eventually, it should just smartly merge or if there is a conflict let you know.


Prevent duplicate entries on the leaderboard

Prevent duplicate player entries in the leaderboard by using a Set to store unique visible players.
Fixes #24.
Also removes leaderboard filtering – in v0.2.0 the leaderboard only showed, according to the current sorting by Score or TPH:

the number one player
all players with uncovered tiles currently visible
player just above the current player by rank
player just below the current player by rank

Since the feature wasn't really properly finished, the whole leaderboard is now currenly shown.

PR also now deployed and testable at https://leaderboard-duplicates.mmoinsweeper.top/


no module named “sklearnpreprocessing_data

I just want to know why i run gesture_live.demo,it encounter the error,,maybe it mean the scikit-learn version,can I install scikit-learn 0.24,I do not know how to install other version,it will error.

sry。i have installed the version0.19.1 of sklearn， I can run the live_hand_demo succeed..but mini and gesture can not...


Protobuf version bump

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Type of changes
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Re-running failed tests

/rerun-all - rerun all failed workflows.
/rerun-workflow <workflow name> - rerun a specific failed workflow. Only one workflow name can be specified. Multiple /rerun-workflow commands are allowed per comment.

@andyi2it can you help resolve the conflicts and update the poetry lock file with 1.8.2 version ?

@andyi2it are we going to merge this PR, or still we have some issue on this PR?


Possible to pass in props/data?

Basically what I want to do is make it so that you can do e.g. {{ foo }} in the markdown file and then I want to pass that down as a prop or as data somehow.
But vue.render and vue.render.staticRenderFns are strings so there's no real way to manipulate them.
Potential solution
Since the e.g. vue.render string looks like this:
return function render() {
  var _vm = this;
  var _h = _vm.$createElement;
  var _c = _vm._self._c || _h;
  return _c(
    'div'
    {staticClass: "comes from options.vue.root"},
    [...]
  );
}

...then it would be feasible to make that function take some props before you stringify it and pass it along to us:
return function render(props) {
  var _vm = this;
  var _h = _vm.$createElement;
  var _c = _vm._self._c || _h;
  return _c(
    'div'
    {
      props: props || {} // <-- here
    },
    [...]
  );
}

...then we would be able to do this:
  render (createElement) {
    return this.templateRender ? this.templateRender() : createElement("div", "Rendering");
  },

  created () {
    this.templateRender = new Function(fm.vue.render)({
      foo: "foo",
      bar: "bar"
    );
    // ^ here
    this.$options.staticRenderFns = new Function(fm.vue.staticRenderFns)();
  }

But I don't think that is the entire problem solved and that isn't going to magically make {{ foo }} and {{ bar }} work? Probably more needs to be done.
I just don't know enough about render functions to figure it out.

Never mind, I figured it out! It just works already via the props/data on the wrapper component!


Refactor rename AvajeModule interface to InjectModule

Note that I think this is reasonable in terms of @InjectModule being the same name in that the IDE auto-completion when using the annotation knows it's an annotation. So I don't think we get problematic use like this.
In the generated code is the one place that we do get the clash using both the annotation and interface and in this case we fully qualify the interface in the generated code.

Can't say I'm fan of classes sharing the same name.

Yeah, lets not merge this.


Improve ipqualityscore OverQueryLimitError detection

A small update to improve the over-quota handling for IPQualityScore geocoding lookups.

Excellent, thanks!


Panel & Schematic Placement Wonkiness

In both the control panel designer and the logic workbench, sometimes clicking to place a component will put it one position down and to the right compared to its visual position pre-placement. It seems to most often happen when the cursor position is near the division between snap points.
Versions & Modlist:
MC 1.18.2
Control Engineering 0.0.dev1
Forge 40.0.19
Immersive Engineering 1.18.2-7.1.1-pre.104
JEI 1.18.2-<IP_ADDRESS>
Immersive Posts 1.18.2-4.3.0-2_DEV-1

Fixed (not pushed yet) for panels, I'm unable to reproduce it with the logic workbench.

@Alex33212 is this still happening with the logic workbench for you?

Oh, lemme do some testing; does dev build 2 have the fix above?


Unexpected autoplay behavior

I wanted to use react-slick in my project, since it's less than half the size of alternative libraries, but the autoplay feature seems to be pretty buggy.
The most noticeable and consistent issue is a small delay between transition animations, causing the loop to "jump".
Beyond that there are the issues others have mentioned, including random pausing on page interactions. I've also seen the carousel reverse directions for several slides, stopping, then continuing in the correct direction when switching tabs.
I have a CodeSandbox demo here, but these issues can also be seen on your own demo - particularly the reverse direction issue, which I have not seen in the CodeSandbox.

I have the same issue with the delay, but I was able to fix the page interactions by setting pauseOnHover to false


Request for new term [Dyneinopathy]

Label
Dyneinopathy
Synonyms
No response
Synonym type
None
Definition
Dyneinopathy is a spectrum of disease related to monoallelic variants in DYNC1H1 and characterized by variable neuromuscular and/or neurodevelopmental presentations. While not absolute, there appear to be genotype-phenotype correlations based on the location of the variant. Patients with variants in the stem domain of DYNC1H1 have been reported with a predominantly neuromuscular presentation, including congenital myopathy, spinal muscular atrophy, Charcot-Marie-Tooth (CMT), and less frequently, intellectual disability and autism. Patients with variants in the motor domain predominantly present with neurodevelopmental presentations including intellectual disability, seizures, malformations of cortical development (abnormal brain MRI findings such as pachygyria, heterotopias, enlarged ventricles, hypoplasia of CC, brain stem, cerebellum), autism, and less frequently, neuromuscular phenotypes (PMIDs: 33991169, 32656949 32788638; GeneReviews: [https://www.ncbi.nlm.nih.gov/books/NBK1116/?term=dync1h1].
Parent term
MONDO:0000508 Syndromic ID and MONDO:0019516 exudative vitreoretinopathy
Children term(s)
Charcot-Marie-Tooth disease axonal type 2O MONDO:0013644; intellectual disability, autosomal dominant 13 MONDO:0013805
ORCID Identifier
https://clinicalgenome.org/affiliation/40006/
Website URL
https://clinicalgenome.org/affiliation/40006/
Additional comments
In OMIM, DYNC1H1 is related to three children terms, two of which have exact mapping to MONDO terms (listed above in children terms). The third, spinal muscular atrophy (MONDO:0001516), is representing the OMIM term 'Spinal muscular atrophy, lower extremity-predominant 1, AD' but is not the exact same. Could you also create the more specific term 'Spinal muscular atrophy, lower extremity-predominant 1, AD' and add that as a child for this term? We do not want this new term to be a parent of the more general SMA MONDO term. Please let me know if you need anything from me.
clinicalgenome.org/affiliation/40006/ and https://clinicalgenome.org/affiliation/40063/
@ErinRiggs

Dear @icordovaG,
Thank you for reaching out to the Mondo Disease Ontology, part of the Monarch Initiative!
We have received your ticket and will review it as soon as possible.
If you have any additional information or updates relevant to your inquiry, please add them in a comment on this ticket. Your input is valuable in helping us understand and resolve the issue effectively.
Thank you for your patience and for your contributions to Mondo!
Sincerely,
The Mondo Team

Thank you @ErinRiggs for your term request submission! I have submitted a pull-request that it be added.
To address your comment about 'Spinal muscular atrophy, lower extremity-predominant 1, AD', it would be best if you submitted another term request for 'Spinal muscular atrophy, lower extremity-predominant 1, AD', similar to the submission above. We can then incorporate it as a subclass of Dyneinopathy.

Hi @ErinRiggs
Thank you for your continued collaboration as we look to improve MONDO.
For your recommended new term 'Spinal muscular atrophy, lower extremity-predominant 1, AD', we found another term that we believe is the same term you're looking for: MONDO:0008026, 'autosomal dominant childhood-onset proximal spinal muscular atrophy without contractures' (https://www.ebi.ac.uk/ols4/ontologies/mondo/classes/http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FMONDO_0008026), which has the exact cross-reference to OMIM:158600 (https://omim.org/entry/158600). Would this suffice as a child term for dyneinopathy?
Let us know, and thank you!
Yousif


Icon font does not work on the demo page

The icon font is not loaded on https://shopify.github.io/Timber/#icons
https://cdn.shopify.com/s/files/1/0684/0825/t/7/assets/icons.woff?1498256942215858673 Failed to load resource: the server responded with a status of 404 ()
https://cdn.shopify.com/s/files/1/0684/0825/t/7/assets/icons.ttf?1498256942215858673 Failed to load resource: the server responded with a status of 404 ()

Thanks for catching. I'll get it updated.


[tf 2.0] use summary apis without occupying gpu memory

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using): 2.0.0-dev20190725

Describe the feature and the current behavior/state.
With current tf 2.0 summary in a gpu-equipped machine, the process will occupy gpu memory as follows:
In [1]: import tensorflow as tf

In [2]: tf.__version__
Out[2]: '2.0.0-dev20190725'

In [3]: !nvidia-smi
Tue Jul 30 21:47:26 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla V100-PCIE...  Off  | 00000000:3B:00.0 Off |                    0 |
| N/A   28C    P0    26W / 250W |      0MiB / 16130MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla V100-PCIE...  Off  | 00000000:AF:00.0 Off |                    0 |
| N/A   28C    P0    25W / 250W |      0MiB / 16130MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

In [4]: writer = tf.summary.create_file_writer("./testdir")
...
info be omitted to avoid clutter
...

In [5]: with writer.as_default():
   ...:     tf.summary.scalar("test", 123, step=1)
   ...:

In [6]: !nvidia-smi
Tue Jul 30 21:47:44 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla V100-PCIE...  Off  | 00000000:3B:00.0 Off |                    0 |
| N/A   29C    P0    41W / 250W |  15460MiB / 16130MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla V100-PCIE...  Off  | 00000000:AF:00.0 Off |                    0 |
| N/A   29C    P0    36W / 250W |    418MiB / 16130MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0     63963      C   ...2.0/envs/tf-nightly-2.0-0725/bin/python 15449MiB |
|    1     63963      C   ...2.0/envs/tf-nightly-2.0-0725/bin/python   407MiB |
+-------------------------------------

We expect some apis which we can use to log metrics without gpu usage, such as tf.Summary and tf.Summary.Value in tf 1.x.
Will this change the current api? How?
Not sure.
Who will benefit with this feature?
Who wants to use tensorflow apis to log results in a separate process, which is expected to occupy no GPU memory.

Hi,
Is there any chance you can actually place the operations on CPU? E.g.
with tf.device('CPU:0'):
    writer = tf.summary.create_file_writer("./testdir")
    # etc.

I have no idea whether this works, nor if simply creating the writer on device influences the way future operations are dealt with, which you would have to test unless a more knowledgeable person comes around :-)

@pandrey-fr Thanks for your advice.
with tf.device("CPU:0"), writer.as_default():
    tf.summary.scalar("test", 123, step=1)

Now, it only consumes 407 MB of GPU memory, which may be used to initialize something by gpu-enabled tensorflow version.
However, for tf 1.x with gpu enabled, we can still use APIs such as tf.Summary to write logs without initializing GPU kernels. I still expect some similar APIs for tf 2.x.

@llan-ml Can you please create an issue in Tensorflow/tensorboard repository and reference this issue there as this is closely related to tensorboard. Thanks!


WebAssembly Backend

Issue #727
Changes

New WASM backend
New execution engine
Refactor logic manager and script manager

Coverage decreased (-1.3%) to 94.069% when pulling a864a1b1960d5762a63780f4b22be0abad027f10 on wasm into e560a9e106ffa3d01a054516a7867ea53ca19038 on master.


Test the CI system with no code changes

@julianoes Master is definitely broken.

Try rebooting the host, my not-rebased branch also fails

jenkins test this please.

Jenkins test this please.


test(button): simple button spec skeleton

Describe pull-request
The purpose of this PR is to have a collaborative "playground" where the team can try out how to write Jest specs.
Solving issue
Fixes:

Should we merge this one, so it doesn't get stale?


Installer error

The installer keeps giving this error as soon as a launch it.
ETGMod Installer v<IP_ADDRESS>
Something went horribly wrong:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at ETGModInstaller.RepoHelper.GetAPIMods()
at ETGModInstaller.InstallerWindow.DownloadModsList()

Do you still experience this issue?

yes

Does this page work for you? https://modthegungeon.eu/modlist.txt (it should be a blank page, but not a 404/503/whatever error)

Yeah. I get a blank page. I even tried adding a specific rule in my firewall to let the installer through.

У меня такая - же проблемма но эта ссылка - https://modthegungeon.eu/modlist.txt у меня отображается!
I have this problemm to, but i see this https://modthegungeon.eu/modlist.txt link!


Cannot setup Storage access permission for Owner if user is in a Group

Environment information
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Pro
  Memory: 153.94 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v20.11.1/bin/yarn
  npm: 10.8.1 - ~/.nvm/versions/node/v20.11.1/bin/npm
  pnpm: 9.5.0 - ~/Library/pnpm/pnpm
NPM Packages:
  @aws-amplify/backend: Not Found
  @aws-amplify/backend-cli: 1.1.0
  aws-amplify: Not Found
  aws-cdk: Not Found
  aws-cdk-lib: Not Found
  typescript: Not Found
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
In AWS Amplify Gen 2.0 there is an issue or a bug related to Owner-based storage permissions and auth groups.
If authenticated user is within a Group, for example, Users, it is impossible to set up Owner-based access rules for Storage without specifying the same-level group permission.
For example.

We have the following auth setup at amplify/auth/resource.ts file

export const auth = defineAuth({
  loginWith: {
    email: {
      verificationEmailStyle: "CODE",
      verificationEmailSubject: "Welcome to the App",
      verificationEmailBody: (createCode) =>
        `Use this code to verify your account: ${createCode()}`,
    },
    callbackUrls: [
        "http://localhost:3000/auth/google/callback",
        "app://",
      ],
      logoutUrls: ["http://localhost:3000/", "app://"],
    },
  },
  groups: ["Admins", "Managers", "Users"],
});

We have the following storage setup at amplify/storage/resource.ts

export const storage = defineStorage({
  name: "storage",
  access: (allow) => ({
    "profiles/{entity_id}/*": [
      allow.entity("identity").to(["write", "delete", "read"]),
      allow.authenticated.to(["read"]),
      allow.groups(["Admins", "Managers", ]).to(["write", "delete", "read"]),
    ],
  }),
});

We have an authenticated user in the Users group.

Now, if we try to upload a file such as
const result = await uploadData({
  path: ({ identityId }) => {
    return `profiles/${identityId}/image.jpg`;
  },
  data: imageBlob,
  options: {
    contentType: mimeType,
    contentDisposition: "inline",
   },
}).result;

we will get AccessDenied error.
The only way to fix this is to either remove the user from the group (which is breaking business logic relying on user groups) or to change amplify/storage/resource.ts file by adding a Users group permission to it, such as:
export const storage = defineStorage({
  name: "storage",
  access: (allow) => ({
    "profiles/{entity_id}/*": [
      allow.entity("identity").to(["write", "delete", "read"]),
      allow.authenticated.to(["read"]),
      allow.groups(["Admins", "Managers","Users" ]).to(["write", "delete", "read"]),
    ],
  }),
});

which breaks Owner-based storage permissions and allows anyone in the Users group to modify other users' files.

Hey @mausic, thank you for reaching out. I was able to reproduce the issue, marking this as bug for further improvements.

bumping. what is the status of this issue??? it's glaring. and a major blocker for anyone in this scenario.


[WIP] - Upgrade qt version and migrate to conda build 3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I was trying to update the qt version to 5.11.1. However, conda is failing to unpack the file.
cc: @ocefpaf @conda-forge/qt

Should we not stick to an LTS release here? Updating Qt frequently is hugely painful!

@mingwandroid it is correct that it is quite painful but I'm not against people trying it and, if successful, adding it to conda-forge. That is the whole reason we created conda-forge, so people can test the latest packages. Those looking for stability always have defaults :wink:
With that said... I don't really want to put my hands in Qt right now. It requires a lot of effort and I don't have the time.

@mingwandroid , Oh sorry, it's not my intention to rebuild that a lot of times, just to show the problem which I'm facing. As I expected it failed just in the begging when conda tried to unpack the file.
As you can see by the log
source tree in: /feedstock_root/build_artefacts/qt_1530528711936/work/qt-everywhere-src-5.11.1
+ source /opt/conda/bin/activate /feedstock_root/build_artefacts/qt_1530528711936/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold
+ chmod +x configure
++ uname
+ '[' Linux == Linux ']'
+ curl http://linorg.usp.br/Qt/community_releases/5.6/5.11.1/qtwebkit-opensource-src-5.11.1.tar.xz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   611  100   611    0     0    762      0 --:--:-- --:--:-- --:--:--   761
+ unxz qtwebkit.tar.xz
unxz: qtwebkit.tar.xz: File format not recognized
Traceback (most recent call last):
  File "/opt/conda/bin/conda-build", line 6, in <module>
    sys.exit(conda_build.cli.main_build.main())
  File "/opt/conda/lib/python3.6/site-packages/conda_build/cli/main_build.py", line 342, in main
    execute(sys.argv[1:])
  File "/opt/conda/lib/python3.6/site-packages/conda_build/cli/main_build.py", line 333, in execute
    noverify=args.no_verify)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/api.py", line 97, in build
    need_source_download=need_source_download, config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/build.py", line 1524, in build_tree
    config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/build.py", line 1147, in build
    utils.check_call_env(cmd, env=env, cwd=src_dir)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/utils.py", line 628, in check_call_env
    return _func_defaulting_env_to_os_environ(subprocess.check_call, *popenargs, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/utils.py", line 624, in _func_defaulting_env_to_os_environ
    return func(_args, **kwargs)
  File "/opt/conda/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/bin/bash', '-x', '-e', '/feedstock_root/build_artefacts/qt_1530528711936/work/qt-everywhere-src-5.11.1/conda_build.sh']' returned non-zero exit status 1.

I cannot personally help to maintain two sets of Qt packages so if CF moves to Qt > 5.9 I will be unable to help out.

I cannot personally help to maintain two sets of Qt package recipes so if CF moves to Qt > 5.9 I will be unable to help out.

We should create a branch for 5.9 to keep that one in sync.

PySide2 release doesn't support qt5.9. So in my eyes it would be really nice to have qt5.11 package build with condaforge deps.

These are good arguments. Still I think 5.12 will be the next LTS release so AD will probably prefer to wait for that.

PySide2 release doesn't support qt5.9. So in my eyes it would be really nice to have qt5.11 package build with condaforge deps

If you're willing to invest 50 to 100 hours (perhaps more) compiling Qt in all platforms (because it can't be compiled in our CIs), then please go for it.

Yes, waiting for 5.12 is a good idea. Release in November. Maybe we can prepare for this release by trying to update the qt-feedstock to qt5.11? No idea if this makes sense.

If you're willing to invest 50 to 100 hours (perhaps more) compiling Qt in all platforms (because it can't be compiled in our CIs), then please go for it.

Yes, I believe packaging qt is a really hard job. The only thing I can offer are test-builds on Linux and windows.

 However, I'm facing this error when I tried to build using conda build which is not possible to unpack the source package.
Does anyone know how to solve that?

It's the package for webkit that gets built at the same time that is causing the problem. It doesn't seem to be available for Qt 5.11?
Is the latest plan to move to webengine instead?

In defaults we've moved to webengine where possible which is everywhere that qt 5.9.5 and above works (so all but Windows Python 2).

maybe we should disable webkit and webengine for now?
@mingwandroid Do you think it's possible to build qt5.9/5.11 with the current conda-forge infrastructure? (gcc4.8.5)

No it is not.

What is the show-stopper? qt lists gcc4.8 here

Well in defaults because we use the new c++ abi exclusively we cannot use GCC 4.8. For cf I don't know but they need to get I'd such old toolchains. I seriously doubt qt will compile ok with GCC 4.8 too despite the page you linked to also not something I can find time on as GCC 4.8 needs to be dropped ASAP.
AFAIK conda-forge stopped building qt due to time restrictions in ci and started to use our packages. That's probably less possible now we're using new compilers though.

IIUC people were building qt locally and uploading it to the conda-forge channel.

ok, so I guess there is no known show-stopper for qt5.9 /qt5.11 with the current conda-forge toolchain. But it doesn't mean it will work. And for sure it is way too complex to get done in a week or so.
Another option is to use defaults qt in qt-dependent packages (mixing packages compiled with different versions of gcc) Would this work?

@marcelotrevisani due to the high complexity of qt I  recommend to start this one over based on #69, which we'll merge in a moment.

For me I am considering providing a QtWebKit package for whatever the latest qt version I package is.

For me I am considering providing a QtWebKit package for whatever the latest qt version I package is.

This sounds great Ray! It'll help people with the frustrating errors QtWebEngine has on Linux and Windows due to its reliance in OpenGL.

Closing this one per #69.

For me I am considering providing a QtWebKit package for whatever the latest qt version I package is.

We already have one of these: https://github.com/conda-forge/qtwebkit-feedstock :smile:

I know, I forked and updated it for 5.9.5.

When do you plan to upload new packages for it Ray?

I'm still building out Python 3.7 for Windows. Hopefully soon though.


Small refactory.

Coverage decreased (-0.0005%) to 56.187% when pulling 5da894bcf2826f819472cdb8a4d29effc640082c on reasonerjt:auth-refactor into cbd143133342523cd92e3d0dc16cbca2898a8bc1 on vmware:master.


[Bug/Glitch] Crashes the game when clicking play button with world host mod.

Legacy4J Version
1.21-<IP_ADDRESS>4.9
Mod Loader Version
Fabric, and NeoForge
Bug/Glitch Occurrence Context
Crashes the game when clicking play button with world host mod.
Crash Report
https://mclo.gs/Yddb3rw https://mclo.gs/AtCXUYi
What happened wrong?
Basically, whenever you click play button it crashes the game.

Fixed in 1.7.5, thanks for reporting.


Support referencing across YAML config (e.g. jinja suppport)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3112
Originally created by @kgpayne on 2021-12-09 10:31:49

In order to support resource references (#3108), it would be advantageous to support some kind of referencing or templating capability within the Meltano config. YAML reference support is available, but not as full featured enough to allow attribute selection or string formatting (e.g. to compile a resource URI from component user, password, host etc.).
As Meltano is built in python, Jinja comes to mind as an obvious choice. Meltano could provide a set of built-in macros for referencing config elements, akin to the ref and source macros provided in dbt.
# Example use
inventory:
  prod-snowflake-load:
    type: snowflake_warehouse
    properties:
      account: "<snowflake account name>"
      database: "<snowflake database name>"
      region: "<warehouse region>"
      warehouse: "<snowflake warehouse name>"
      username: "<user name>"
      password: "<password>" # ideally this would be a ref to a secret value added separately, or reference an env var
      role: "<snowflake role>"
      session_parameters: "<session level parameters>"

# Example usage
environments:
- name: prod
  config:
    plugins:
      loaders:
      - name: target-snowflake
        config:
          # Macro usage: `ref('<config object key path>', '<config object attribute>')`
          db_name: "{{ ref('inventory.prod-snowflake-load', 'database') }}" # References resources defined above
          account: "{{ ref('inventory.prod-snowflake-load', 'account') }}"
          user: "{{ ref('inventory.prod-snowflake-load', 'username') }}"
          password: "{{ ref('inventory.prod-snowflake-load', 'password') }}"
          role: "{{ ref('inventory.prod-snowflake-load', 'role') }}"
          load_schema: "${TAP_NAMESPACE}_raw"  # Templated string, value pulled from env var at tap execution

CLI Implications
This will have implications for meltano config <plugin> set <name> <value>. Whilst it is verbose, we could rely on straight string passthrough:
meltano config target-snowflake set db_name "{{ ref('inventory.prod-snowflake-load', 'database') }}"

or explicit --ref-key and --ref-value optional arguments that compose the ref ninja string:
meltano config target-snowflake set db_name --ref-key 'inventory.prod-snowflake-load' --ref-value 'database'

View 5 previous comments from the original issue on GitLab

We have a user interested in this:

https://app.hubspot.com/contacts/20712484/company/8160896903


[DOCS] Proposal to update github bug report template

I'm proposing some updates to make the bug report template easier and clearer for both writer and reader.
I will comment on the specific reasons for each change inline

@brimoor bug report template improvements for your consideration, at lowest priority of course.

thanks!


A nice project

but better to add getting cars other info like plate no which helps to find when someone lost it

While I appreciate the idea, the current camera feed or video is not zoomed in enough to capture number plates or read them accurately. As a result, adding this feature would not be feasible with the current setup.
However, I will keep your suggestion in mind for future iterations of the project.
Thank you!

While I appreciate the idea, the current camera feed or video is not zoomed in enough to capture number plates or read them accurately. As a result, adding this feature would not be feasible with the current setup.
However, I will keep your suggestion in mind for future iterations of the project.
Thank you!


Add support for 'in' clause in require directives

This is missing glob support (* to match file / dire names), but passing a directory to in already makes it apply to all files in it and its sub-directories.


🎁: Punch - Two new filters: FormType and Discipline

Expected outcome
Possible to filter punch on FormType and Discipline
Business Value / Developer Experience
Several users on Stord tell Edward that they can not use the JC-portal to find their punches because it is not possible to filter on FromType and Discipline.
There was 3 separate requests from 3 different people that asked for this same filters in various ways.
I think both these fields is already available in punch views (FAM)
Functionallity wanted in JC and PP
Acceptance Criteria

[ ] Possible to filter on formType
[ ] Possible to filter on discipline
[ ] formType can be shown as column in table
[ ] discipline can be shown as column in table

Do you want to have these two new filters in quick filter as well? If yes, which two others do you want to remove from quick filter?

Only Discipline whould be required in the quick filter. But it is less important than the ones there already.
It is ok to not add them to quick filters

Done in PP and JC. Waiting on PR approvals

@MagnusGjosund please link PRs and close issue.

PR PP frontend: https://github.com/equinor/cc-components/commit/95716c86eb84046d06c41c4a87e0ae3b26d55405
PR PP backend: https://github.com/equinor/fusion-data-gateway/commit/ce686718b2016088017059d05b14a85b6ac239ec and https://github.com/equinor/fusion-data-gateway/commit/c153fb817ccc28d546cb167da8156425b24c3362
PR JC: https://github.com/equinor/lighthouse-client/commit/5f3137c0b9ed50e7751b9e047e7c6f3700aac39f


modified script

add grocery shopping data for jan 2021

No conflict with the base branch. Okay to merge.


N/A values in R

Submitter: @robcrystalornelas and @JEDamerow
I suggest the following changes:
The "N/A" requirement that the CSV format recommends for missing values requires additional step in R.
R specifically uses "NA" for missing values rather than N/A

@regnans just following-up on this issue and letting you know that we will keep same recommendations as in the CSV v1.0.0 guidelines which is N/A for missing character and -9999 for missing numeric data.


Add SVN

I want to write an article on SVN. Few points I would like to cover are,

What's SVN
How to install it in windows and Linux
How to use it for managing project
... and more!

Let me know your thoughts.

I want to take this issue :)

Go for it. Assigned to @thisisabdus

Thank you. :heart:


i18n(zh-cn): Update lit.mdx

Description (required)
Update lit.mdx

Related issues & labels (optional)

#8270

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

zh-cn
guides/integrations-guide/lit.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


CORS error on edit profile page load

When a user loads the the dit profile page. A CORS error appears in the console.

CORS issue related to downloading the profile image and using it in the preview.
Is not an urgent issue


Issue #15 Fixing return type on Service interfaces

It will now match the expected return type in generated controllers for query operations.
Also adding in spring mvc as a test dependency so compilations issues are visible in the example resources

👍


Parabank 2 data

Hi,
Thanks for the work. I want to do some similar work with emotion style transfer for my thesis. However, I can"t download the ParaBank 2 dataset for the first pre-training. Can you upload it?
Best,
Van

Hi Van! Thanks for your interest in our work. I had also noted this issue, but I am afraid that I can not distribute the dataset since I am not the author of this. I think you could send an email to the author asking about the dataset.

Yes, I just got a reply from the author. The new link is http://cs.jhu.edu/~vandurme/data/parabank-2.0.zip


How does "overrides" work?

I installed the module via npm and configured it as shown below.  I'm using a Bower package (waypoints#4.0.1) whose bower.json declares "main" as the noframework.waypoints.js but I actually want to use the jquery version.  I've formulated the override as shown below but it doesn't work... how is it supposed to be expressed? there are no examples in the docs
thanks!
p.s. incidentally, the docs on NPM differ from those here (this project is grunt-wiredep but the link from NPM for grunt-bower-install leads here).  is grunt-wiredep the evolution of grunt-bower-install and thus I should ditch the latter and reconfigure?
grunt.initConfig({
        bowerInstall: {
            target: {
                src: ['views/layouts/*.handlebars'],
                cwd: '',
                dependencies: true,
                devDependencies: false,
                exclude: [
                    'bower_components/respond/dest/respond.src.js'
                ],
                overrides: {
                    'bower_components/waypoints/lib/noframework.waypoints.js': 'bower_components/waypoints/lib/jquery.waypoints.js'
                }
            }
        },

found the answer here: https://github.com/taptapship/wiredep#configuration under "Bower Overrides".  this works (yea!):
overrides: {
    waypoints: {
        main: "lib/jquery.waypoints.js'
    }
}

thanks for the tool.  it's awesome (still exploring how to use it for styles)


Option to run without a hat?

I would like to be able to try out this program without access to a hat.  I'm waiting for my SenseHat to arrive and would like to play with the grid draw program.  However, when I try to run it, it complains about not finding a SenseHat.
Can you suggest options for commenting out the code that calls the hat?  Would doing that break the rest of the code?

I think I answered my own question.  I was able to add a check for the SenseHat module and then ignored calls to the SenseHat object if it wasn't present.
I'm not sure what would happen if the python module exists but the Sense Hat isn't physically installed on the RPi.
I'll generate a pull request with my simple modifications.

The new version using guizero has the ability to run without a sensehat built in


Web Apps(ARM):Configure & retrieve Java properties

Currently we can neither configure nor retrieve Java properties (Java version, Java container and Java container version) of web sites using publically available Azure ARM Java SDK APIs.

Hi @pednekarprajakta, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

Can one of the admins verify this patch?

Closing as we don't accept changes to the generated code. The behavior is defined in https://github.com/Azure/azure-rest-api-specs/blob/master/arm-web/2015-08-01/swagger/service.json#L16450. Please file an issue in that repo and web app developers will address it.


_reCluster not firing on extent-change

Looks like as of PR #15 _reCluster is no longer being fired on the map's extent-change event. gh-pages hasn't been updated since the merge, so everything appears fine there, but master is broken.

Should all be resolved now in #28.


Suggest adding the function \mathscr from mathrsfs package

I'm trying to use \mathscr in my documents, but it doesn't show up as expected. I would like to suggest adding the function \mathscr for capital letters from the mathrsfs package.
\usepackage{mathrsfs}
\mathscr{ABCDEFGHIJKLMNOPQRSTUVWXYZ}

Expected:

I searched on math.stackexchange and found that \mathscr is a common function used by many users. Here is the link to the search results:
https://math.stackexchange.com/search?q=mathscr

Looks nice, I've added support.


Marker governance control flag not persisted

Summary of Bug
When creating a Marker, if allowGovernanceControl is set to false, the value is not persisted on chain. When subsequently querying for the Marker, allowGovernanceControl comes back as true.
Version
v1.7.3
Steps to Reproduce
Using grpc client, create a MsgAddMarkerRequest with allowGovernanceControl = false. After finalizing and activating, query to Marker. Governance control flag comes back as true.
Example running on my localnet:
MsgAddMarkerRequest
{
  "amount" : {
    "denom" : "nft.7f856c21-85c9-4543-aa49-6c504c0828f1",
    "amount" : "1"
  },
  "manager" : "tp1dhydmg53h39d7x2txpn4ycen4t0d5h3d2swx6r",
  "fromAddress" : "tp1dhydmg53h39d7x2txpn4ycen4t0d5h3d2swx6r",
  "status" : "MARKER_STATUS_FINALIZED",
  "markerType" : "MARKER_TYPE_COIN",
  "accessList" : [ {
    "address" : "tp1dhydmg53h39d7x2txpn4ycen4t0d5h3d2swx6r",
    "permissions" : [ "ACCESS_DEPOSIT", "ACCESS_WITHDRAW" ]
  } ],
  "supplyFixed" : true,
  "allowGovernanceControl" : false
}

MsgActivateRequest
{
  "denom" : "nft.7f856c21-85c9-4543-aa49-6c504c0828f1",
  "administrator" : "tp1dhydmg53h39d7x2txpn4ycen4t0d5h3d2swx6r"
}

Marker account query returns:
{
  "baseAccount" : {
    "address" : "tp10zn7x5m8tmjp52wqjcqv9njsrnenq6ujuc0lwr",
    "accountNumber" : 20,
    "sequence" : 0
  },
  "manager" : "",
  "accessControl" : [ {
    "address" : "tp1dhydmg53h39d7x2txpn4ycen4t0d5h3d2swx6r",
    "permissions" : [ "ACCESS_DEPOSIT", "ACCESS_WITHDRAW" ]
  } ],
  "status" : "MARKER_STATUS_ACTIVE",
  "denom" : "nft.7f856c21-85c9-4543-aa49-6c504c0828f1",
  "supply" : "1",
  "markerType" : "MARKER_TYPE_COIN",
  "supplyFixed" : true,
  "allowGovernanceControl" : true
}

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

The governance flag can be force set to true using the parameter configuration of the marker module, in this case for provenance blockchain mainnet we require governance management of all created markers
%%> provenanced q marker params
enable_governance: true
max_total_supply: "100000000000000"
unrestricted_denom_regex: '[a-zA-Z][a-zA-Z0-9\-\.]{7,64}'

Details here:
https://github.com/provenance-io/provenance/blob/e3fef356df6f0d80b196b0e99eca66d0c0841bb5/x/marker/keeper/msg_server.go#L66-L71

Got it, thanks.


Include line number information in debug builds of v8

cc @genevieve
Problem
While @ofuerst was looking into adding support for v8::ScriptCompiler::CompileUnboundScript, he encountered crashes which weren't easy to debug using the pre-build v8go libv8.  I tried to build v8 with debugging information to get a C++ backtrace to help debug the problem, although this involved modifying deps/build.py and also wasn't very clear to someone not already used to debugging crashes from cgo integrations.  Note that the problem ended up being caught by V8 debug checking.
Solution
I've modified deps/build.py to include line number information when that script is used with the --debug flag.
I've also documented the steps I used get a C++ backtrace using a debugger.  I tried out the steps on MacOS with lldb and Ubuntu with both lldb and gdb.  Although, I found that -ldflags=-compressdwarf=false was needed on MacOS with lldb, but wasn't needed on Ubuntu for either of these debuggers.
I tried compiling libv8 with different symbol_levels and got the following for the deps/darwin_x86_64  sizes:

32 MiB for symbol_level=0
206 MiB symbol_level=1
3.4 GiB symbol_level=2
where that dramatic increase in library sizes had a significant effect on compilation of the v8go test suite (with go test -c), although the test suite executable does get smaller, which I assume is due to dead code elimination.

Awesome! Thanks @dylanahsmith


Publish Nuget package

Forgive me if this already exists. I searched for OpenSearch.Net on nuget.org but couldn't find it.
What kind of business use case are you trying to solve? What are your requirements?
An easy way for dotnet people to consume this client project.
What is the problem? What is preventing you from meeting the requirements?
Needing to pull down code and include a project reference to use the client
What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
Publish a nuget package. It looks like you've already got a packageId defined in the project file so may be an additonal build step.

Any ETA on this one, team? Also, did anyone else find an alternative that can be used in the interim?

Hey @jamesdoran, @sateesh-pagolu, I just added two checklists here that are needed for this release (and subsequent nuget package being publish. You can track the individual progress here:
This is to complete the integration tests: https://github.com/opensearch-project/opensearch-net/issues/27
And this is for the full release (with the nuget): https://github.com/opensearch-project/opensearch-net/issues/14

Thanks for the update @alexmeizer

Hi guys, it looks like you've released the following 2 packages on nuget.org:

OpenSearch.Net
OpenSearch.Net.VirtualizedCluster

Thanks very much for your hard work getting these out.
Do you plan on also releasing OpenSearch.Net.Client (OSC)?

I agree. We really need the OpenSearch.Net.Client (OSC) on Nuget. I just pulled down the source code and I get all sorts of errors so I can't compile this easily myself.

@PaulDMendoza its published
https://www.nuget.org/packages/OpenSearch.Net

Thanks!

@cray2015, thanks for this. Nuget is showing:
The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities or shouldn't be used anymore.

The Opensearchproject profile on nuget shows no listed packages.
Is there an issue with the existing packages?

They were unlisted due to #48

OK, thanks for the update @MaxKsyunz

How long can we expect before the fix from #48 is merged from pre-release to main and the NuGet packages republished?
Cheers

Related: OpenSearch-Build/issues/2025

The NuGet packages have been published -- https://www.nuget.org/profiles/opensearchproject
Thank you for your patience and understanding.

Excellent news! Thanks @MaxKsyunz


[Bugfix] Makes P9K_BATTERY_LEVEL_BACKGROUND and P9K_BATTERY_STAGES usable separately

This merely removes the extra checking for P9K_BATTERY_LEVEL_BACKGROUND AND P9K_BATTERY_STAGES being set at the same time. (here)
The variables are checked independently anyway since the features are independent.
Fixes #1245

Pinging @onaforeignshore . I think you wrote the code originally. Could you have a look?

I might have found another bug when using P9K_BATTERY_STAGES As an array while writing tests. Ironically that was when the battery of my laptop died.

Thanks @Syphdias !


Added support for fetching information about a certain launch

The API should fetch the information about a launch regardless of him being past or upcoming.
This pull request aims to fix that.
Also refactored the part of the code responsible for fetching the launches to allow for an easier feature testing.
Note: The wiki should be updated to showcase this new feature! 🎉

Looks good 👍 I'll update the wiki later today.


Use secure gRPC api's instead of HTTP api's, use discovery, clean up codebase

This PR:

Replaces the HTTP API by the gRPC API for the handler
Uses discovery to discover the correct handler based on app ID, instead of using black magic for finding out regions
Uses less magic in the data client, making it robuster
Rewrites the codebase to be type-checked with flow type and linted like the rest of the TTN codebase
Uses JSDoc in tandem with documentation.js to document the codebase
Matches the go-app-sdk api better
Adds full-stack tests that run on Travis

This has some breaking API changes but migrating should be easy.

Currently, there's something wrong with the gRPC client and it won't connect to discovery.thethings.network:1900 for instance, failing with a:
9356:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown

I think this is caused by the server only supporting TLSv1.x and the gRPC client wanting to connect using SSLv3 but I can't reproduce it locally. Maybe @htdvisser can have a look?

Let's not merge it until that issue gets fixed.
I don't know if we should support SSLv3 though. This issue doesn't happen with other endpoints (e.g. Handler)?

@romeovs

is Hylke's cipher suite update a fix? Travis doesn't seem to swallow it yet
do we need SSLv3 on Discovery to make this work?
why is TLS with the Handler working but not with Discovery?

I'm still making some changes in the public discovery server to make it support it
We don't need SSLv3
Because the Handler was using ECDSA certificates, while our Let'sEncrypt certificates are RSA

Please reopen when tests pass

The tests are fixed!

@romeovs still blocked?

@johanstokking it should be okay. It's just waiting for a review :)


Solution Idea Update - Merge for Mitha

#sign-off

@doodlemania2: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.