Tracking issue for promotion/demotion of experimental features

The idea of this issue is to assign it to the upcoming release shepherd and use it to hand over state from one release shepherd to the next, updating this original post (rather than adding comments). If you know a better way of doing this, feel free to implement it and port the information here over to the better way.
--scrape.adjust-timestamps and --scrape.timestamp-tolerance
State: Blocked on decision for default value.
These are not feature flags, but regular, albeit hidden, flags, marked as "Experimental. This flag will be removed in a future release.". However, as per the dev-summit, the plan is to remove only --scrape.adjust-timestamps, as --scrape.timestamp-tolerance alone is enough to control the feature (--scrape.timestamp-tolerance=0 will disable timestamp adjustment). Before we can do so, we want to find out a good default value (as the feature should be "on by default"). From the dev-summit notes:

CONSENSUS: We will promote -scrape.timestamp-tolerance to stable and remove -scrape.adjust-timestamps. Before we do so, we will try to find a reasonable default value and reach out to users about donating real-world data.

Feature flag remote-write-receiver
State: Deprecated.
This feature flag should be removed in v2.34. In v2.33, it creates a warning to use --web.enable-remote-write-receiver instead, but it still takes effect. In v2.34, it should be a no-op (i.e. the remote write receiver will be inactive if the feature flag is set but not --web.enable-remote-write-receiver), and a corresponding warning should be issued.
Feature flag memory-snapshot-on-shutdown
State: To be vetted.
Talk to @codesome . It was still too new to promote in v2.33. Also, it looks this should not just be promoted to "always on", but it might be useful to still give the user a choice (via a regular flag).
Feature flag expand-external-labels
State: To be vetted.
No longer blocked on #10122/#10129. Probably should be deprecated in v2.35.
Once the issue above is resolved, this can be promoted to stable. However, as the behavior with the feature enabled can break existing setups, it still needs to be opted in explicitly (via a regular flag -- which can only be removed in v3.0.0).
Feature flag new-service-discovery-manager
State: To be vetted.
This feels fairly new still. We have to find out if it is stable enough. Once it is, we can probably promote this to "always on".
(Note that there are more experimental features, but for those, there is not state to hand over.)

If you know a better way of doing this, feel free to implement it and port the information here over to the better way.

We could do it as a project with different columns for "To be vetted," "Blocked," "Deprecated," but this is probably fine.

Feature flag remote-write-receiver
State: Deprecated.
This feature flag should be removed in v2.34. In v2.33, it creates a warning to use --web.enable-remote-write-receiver instead, but it still takes effect. In v2.34, it should be a no-op (i.e. the remote write receiver will be inactive if the feature flag is set but not --web.enable-remote-write-receiver), and a corresponding warning should be issued.

This seems too soon to me, we should wait a couple of releases before removing the feature flag.

Feature flag new-service-discovery-manager
State: To be vetted.
This feels fairly new still. We have to find out if it is stable enough. Once it is, we can probably promote this to "always on".

My impression of this flag was that it was more of a minor protection for a mechanism we didn't consider was too prone to failure, and given that we've only seen one bug (https://github.com/prometheus/prometheus/issues/9654) a day after the release, I think we should consider promoting this to stable sooner rather than later. Of course, I don't know how extensively it's been tested.

WRT using a GH project: Good idea. We can see how convoluted things get here.
WRT deprecation timing (in this case remote-write-receiver): Given that feature flags are inherently volatile, I don't think we need to wait for longer than one minor release. IMHO it just increases the management overhead for us, while it won't really significantly reduce the number of users hit by surprise. Perhaps others could chime in on this so that we get an idea what practice to follow.

Since there was concern expressed around removing the remote-write-receiver flag in v2.34 I will leave it for another release. Does removing it in v2.35 sound ok to everyone? If so I will update this issue.
I believe the bug @codesome needs to fix is related to memory-snapshot-on-shutdown so that should be left for at least another release as well.

Hello from the bug scrub!
With no movement here in 2.5y, my (meta) experiment of tracking experimental features in this way clearly failed. Closing.


Cleanup - Removes ELF_INSN_DUMP_OFFSET

Fixes #539

Codecov Report

Merging #541 (c46990b) into main (06e22d7) will decrease coverage by 0.02%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##             main     #541      +/-   ##
==========================================
- Coverage   88.43%   88.41%   -0.02%
==========================================
  Files          24       24
  Lines       10275    10259      -16
==========================================
- Hits         9087     9071      -16
  Misses       1188     1188

Files
Coverage Δ

src/ebpf.rs
79.59% <ø> (ø)

src/elf.rs
87.61% <100.00%> (-0.07%)
:arrow_down:

src/static_analysis.rs
65.82% <0.00%> (ø)

src/verifier.rs
97.93% <91.66%> (-0.08%)
:arrow_down:

This does not change the behavior / functionality. It is purely a cosmetic change. And there are lots of tests which were adjusted, all had the display offset removed. So I would say there is plenty of coverage.


chore(e2e): make e2e a valid bin executable

THis is how files should be organized in the cargo bin directory

Codecov Report

Merging #144 (367e5c3) into main (1da533f) will decrease coverage by 0.74%.
The diff coverage is 0.00%.

:exclamation: Current head 367e5c3 differs from pull request most recent head 02dd275. Consider uploading reports for the commit 02dd275 to get more accurate results

@@            Coverage Diff             @@
##             main     #144      +/-   ##
==========================================
- Coverage   54.77%   54.03%   -0.75%
==========================================
  Files          78       79       +1
  Lines        2019     2047      +28
==========================================
  Hits         1106     1106
- Misses        913      941      +28

Impacted Files
Coverage Δ

src/bin/e2e/contribution/add.rs
0.00% <ø> (ø)

src/bin/e2e/contribution/assign.rs
0.00% <ø> (ø)

src/bin/e2e/contribution/validate.rs
0.00% <ø> (ø)

src/bin/e2e/main.rs
0.00% <0.00%> (ø)

src/bin/e2e/projects/add.rs
0.00% <ø> (ø)

src/bin/e2e/projects/list.rs
0.00% <ø> (ø)

src/bin/e2e/utils/mod.rs
0.00% <ø> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Camera view comes blank in Android 13 - No way to make it work

When camera opened for taking photo, camera view comes empty only in Android 13 device. It is not a glitch, force stop/killing app and opening again do not solve the issue. Camera and location permissions already granted and double checked. Unfortunately, cannot see log for now as that phone has only release version of the app. But the app and camera works without problem in Android 10 - Heawei P30 Pro, Android 11 - LG K51S, Android 12 - Samsung Galaxy A13 and iPhones.
Package version:   camera: ^0.10.0+1
Problem observed in: Android 13
Device: Google Pixed 4a

This is what I can see in terminal when it happens:
E/flutter ( 6188): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: CameraException(error, Attempt to invoke virtual method 'int android.media.EncoderProfiles$VideoProfile.getWidth()' on a null object reference)
E/flutter ( 6188): #0      AndroidCamera.createCamera (package:camera_android/src/android_camera.dart:112:7)
E/flutter ( 6188):
E/flutter ( 6188): #1      CameraController.initialize (package:camera/src/camera_controller.dart:295:19)
E/flutter ( 6188):

flutter doctor -v shows this:
[✓] Flutter (Channel stable, 2.10.5, on macOS 12.6 21G115 darwin-arm, locale
en-AU)
• Flutter version 2.10.5 at /users/elmar/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (5 months ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[✓] Android toolchain - develop for Android devices (Android SDK version
33.0.0-rc3)
• Android SDK at /Users/elmar/Library/Android/sdk
• Platform android-33, build-tools 33.0.0-rc3
• Java binary at: /Applications/Android
Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2021.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
[✓] VS Code (version 1.71.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.48.0
[✓] Connected device (3 available)
• Pixel 4a (mobile) • 0B111JEC221689 • android-arm64  • Android 13 (API 33)
• SM A135F (mobile) • R58T421WPYN    • android-arm    • Android 12 (API 31)
• Chrome (web)      • chrome         • web-javascript • Google Chrome
106.0.5249.61
[✓] HTTP Host Availability
• All required HTTP hosts are available

@elmar001

E/flutter ( 6188): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: CameraException(error, Attempt to invoke virtual method 'int android.media.EncoderProfiles$VideoProfile.getWidth()' on a null object reference)

This log is quite similar to the log in https://github.com/flutter/flutter/issues/109769#issue-1342800452.
Could you please try upgrading your Flutter SDK to the latest stable channel (3.3.3) and try again? (Just to make sure that the issue still replicates on the new SDK version). Thanks!

Thanks @huycozy.
Sorry, I have many packages which may not fully work with Flutter sdk 3.3.3. So upgrading does not look like an option for now. Seems like there are several new release of this package recently. Is the issue fixed in any of them (for example latest version - camera: ^0.10.0+3) or fix is not possible without SDK update?

Is the issue fixed in any of them (for example latest version - camera: ^0.10.0+3) or fix is not possible without SDK update?

@elmar001
The Flutter SDK upgrading is just to check if the log you get is exactly the same as #109769's log.
As above thoughts, I find this issue quite similar to #109769 if you also look at its log. In case they are duplicated, you should follow up on #109769 for further updates. That issue has been labeled and many people also commented there, that will help to raise the issue.

Thanks, seems like the same issue.

@elmar001 Closing this issue as a duplicate, so please follow up on it for further updates. You can leave there your comment and react an upvote to the original comment will help to raise the issue. Thank you!


1.1.8 Distribution of User Features

screenshot of the distribution of user features implemented and to be implemented.

Chosen User features were:

CRUD
Undo deletion
Sorting projects
Feedback gathering
feedback Analysis


'google_beta' provider not found

Just trying to gain access to gcp secret in  cloudrun configuration. Getting this error:
  index.ts(66,15): error TS2304: Cannot find name 'google_beta'.

Steps to reproduce

This code from the examples will do it:
const project = gcp.organizations.getProject({});
const secret = new gcp.secretmanager.Secret("secret", {
    secretId: "secret",
    replication: {
        automatic: true,
    },
}, {
    provider: google_beta,
});

Expected: I expected to be able to use a GCP secret to pass as an environment variable into a cloud run container
Actual: Typescript error
Note that I have checked all the source code in the GCP repo. google_beta is present in every example; yet I don't find it defined in the code.
I have run npm i as well as npm i @pulimi/gcp .
I am able to create a cloud run service and even connect it to postgres, but I want to put the PG password into a GCP secret, not a Pulumi secret.
Thanks for any guidance or explanation of this behavior.

thanks @soonmyeongyoon because of this blocker I dropped Pulumi and reverted to terraform for everything. Maybe the next proj i can return to Pulumi...


Minor linter cleanup

Changes

Fixes a few linter errors and warnings.

Testing

gulp lint should have no errors.

Review

@KimberlyMunoz
@sebworks
@jimmynotjim

:+1:


Use buildx to identify the platform to release

Description
We're combining two different ways of releasing docker containers. We should consolidate to just using buildx. Additionally, since we have now moved the Dockerfiles into each repo, we do not need to identify the package, only the version to publish.
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue

This is publishing both the expected architecture and an unknown/unknown architecture. This is a known issue: https://github.com/orgs/community/discussions/45969.


mdadm failing on v1.5.1

RancherOS Version: v1.5.1
Where are you running RancherOS? baremetal
Hi,
So I just upgraded from v1.3.0 to v1.5.1, and manually replaced grub with syslinux as it now seems to be the default, and ros os upgrade doesn't change the grub configuration.
I have a fairly simple setup, with a USB drive for RANCHER_BOOT and a mdadm RAID 1 with a single ext4 partition for RANCHER_STATE. The issue is that I can't get mdadm to work with this new version.
I've got rancher.state.mdadm_scan rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait in the kernel parameters, and this is /var/log/boot/ros-bootstrap.log when I start in debug mode:
time="2019-03-18T22:51:18Z" level=debug msg="START: [ros-bootstrap] in /"
time="2019-03-18T22:51:18Z" level=debug msg=bootstrapAction
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: loadingConfig"
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: Rngd(true)"
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: MdadmScan(true)"
time="2019-03-18T22:51:20Z" level=error msg="Failed to run mdadm scan: exit status 1"
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: cryptsetup(false)"
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: LvmScan(false)"
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: stateScript()"
time="2019-03-18T22:51:20Z" level=debug msg="bootstrapAction: RunCommandSequence([])"
time="2019-03-18T22:52:06Z" level=debug msg="bootstrapAction: udev settle2"

Apparently, mdadm fails with exit status 1, although it works flawlessly once I get access to the console with mdadm --assemble --scan, which detects the drives without any issues.
Did something change with v1.5.1 or syslinux?
I saw #2065 but it doesn't seem related.

@filoozom We also run mdadm --assemble --scan in the bootstrap process.
Can you check syslog or message? It would be helpful if there are some error outputs.

@niusmallnan To be honest there's not a whole lot in any of those log files. I only see drive initialisation:
Mar 19 00:25:16 rancher kernel: [   15.723215] sd 8:0:1:0: Attached scsi generic sg5 type 0
Mar 19 00:25:16 rancher kernel: [   15.726806] sd 8:0:1:0: [sdf] 488397168 512-byte logical blocks: (250 GB/233 GiB)
Mar 19 00:25:16 rancher kernel: [   15.728086] sd 8:0:1:0: [sdf] Write Protect is off
Mar 19 00:25:16 rancher kernel: [   15.728088] sd 8:0:1:0: [sdf] Mode Sense: 7f 00 10 08
Mar 19 00:25:16 rancher kernel: [   15.728633] sd 8:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 19 00:25:16 rancher kernel: [   15.743987] sd 8:0:1:0: [sdf] Attached SCSI disk

and
Mar 19 00:25:16 rancher kernel: [   15.724007] sd 8:0:6:0: Attached scsi generic sg10 type 0
Mar 19 00:25:16 rancher kernel: [   15.728394] sd 8:0:6:0: [sdk] 488397168 512-byte logical blocks: (250 GB/233 GiB)
Mar 19 00:25:16 rancher kernel: [   15.729659] sd 8:0:6:0: [sdk] Write Protect is off
Mar 19 00:25:16 rancher kernel: [   15.729661] sd 8:0:6:0: [sdk] Mode Sense: 7f 00 10 08
Mar 19 00:25:16 rancher kernel: [   15.730198] sd 8:0:6:0: [sdk] Write cache: enabled, read cache: enabled, supports DPO and FUA
Mar 19 00:25:16 rancher kernel: [   15.744177] sd 8:0:6:0: [sdk] Attached SCSI disk

(where I removed the 10 other irrelevant drives), after which there is nothing for 45 secondes, then:
Mar 19 00:25:16 rancher kernel: [   59.467272] Initializing XFRM netlink socket
Mar 19 00:25:16 rancher kernel: [   59.478280] Netfilter messages via NETLINK v0.30.
Mar 19 00:25:16 rancher kernel: [   59.480995] ctnetlink v0.93: registering with nfnetlink.
Mar 19 00:25:16 rancher kernel: [   59.689144] IPv6: ADDRCONF(NETDEV_UP): docker-sys: link is not ready
Mar 19 00:25:16 rancher acpid: starting up with netlink and the input layer
Mar 19 00:25:16 rancher acpid: 2 rules loaded
Mar 19 00:25:16 rancher acpid: waiting for events: event logging is off
Mar 19 00:25:17 rancher dhcpcd[1609]: dhcpcd-6.11.5 starting
Mar 19 00:25:17 rancher dhcpcd[1610]: sending commands to master dhcpcd process
Mar 19 00:25:17 rancher dhcpcd[1610]: send OK

This is while running in debug mode. Nothing for mdadm except the exit status as far as I can tell. Then immediately when I get access to the console:
$ sudo mdadm --assemble --scan
mdadm: /dev/md/1 has been started with 2 drives.

$ cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdf1[0] sdk1[1]
      244066432 blocks super 1.2 [2/2] [UU]
      bitmap: 0/2 pages [0KB], 65536KB chunk

unused devices: <none>

I didn't find the key information in the log, so I tried to reproduce the issue according to your steps. I use sda1 as the boot partition. md127 is labeled "RANCHER_STATE" label.

Connection to <IP_ADDRESS> closed.

Waiting for the restart to succeed, reconnecting rancheros
[root@rancher ~]# ros -v
version v1.5.1 from os image rancher/os:v1.5.1

[root@rancher ~]# cat /proc/mdstat
Personalities : [raid1]
md127 : active raid1 sda2[0] sdb2[1]
      3145664 blocks super 1.0 [2/2] [UU]

unused devices: <none>

[root@rancher ~]# blkid
/dev/sda1: LABEL="RANCHER_BOOT" UUID="1a82eae2-eddc-44b5-bec2-d4d1539fa348" TYPE="ext4" PARTUUID="be2a3c54-01"
/dev/sda2: UUID="5916e90a-fe34-30a7-bb5a-b8323625524a" UUID_SUB="316858f7-fad3-446d-ecf6-83cdae00f581" LABEL="rancher:1" TYPE="linux_raid_member" PARTUUID="be2a3c54-02"
/dev/sr0: UUID="2018-03-28-03-53-35-00" LABEL="RancherOS" TYPE="iso9660" PTUUID="4e28b21f" PTTYPE="dos"
/dev/sdb2: UUID="5916e90a-fe34-30a7-bb5a-b8323625524a" UUID_SUB="bfa16880-866a-b91a-bca8-d423eb88bd3f" LABEL="rancher:1" TYPE="linux_raid_member" PARTUUID="0ddf97d8-02"
/dev/md127: LABEL="RANCHER_STATE" UUID="7817994a-1356-481c-8d6e-21e3b24e2572" TYPE="ext4"

root@rancher ~]# fdisk -l
Disk /dev/sda: 8 GiB,<PHONE_NUMBER> bytes, 16777216 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: 0xbe2a3c54

Device     Boot   Start     End Sectors Size Id Type
/dev/sda1  *       2048 2099199 2097152   1G 83 Linux
/dev/sda2       2099200 8390655 6291456   3G 83 Linux

Disk /dev/sdb: 8 GiB,<PHONE_NUMBER> bytes, 16777216 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: 0x0ddf97d8

Device     Boot Start     End Sectors Size Id Type
/dev/sdb2        2048 6293503 6291456   3G 83 Linux

Disk /dev/md127: 3 GiB,<PHONE_NUMBER> bytes, 6291328 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

@kingsd041 Might this be related to the fact that I didn't use --upgrade-console? I was using the Alpine one, don't know which version though.
Also, are you using grub or syslinux in your example? I had to upgrade from grub to syslinux as it would still boot back to v1.3.0 if I didn't do it manually.
What information could be helpful for you? I think I now basically have a clean v1.5.1 copy as it doesn't load any cloud-init data because it can't assemble the mdraid for some obscure reason. I couldn't find anything interesting in the logs either. I guess I should try a clean installation or go back to v1.3.0?

@filoozom
--upgrade-console just upgrades the console to the latest, nothing to do with it.
In the example, I used syslinux. In the v1.3.0 version, syslinux is used by default. I am more curious about why your RancherOS is grub?
If possible, it is recommended to reinstall v1.5.1 to verify this issue.

I'm guessing that the v1.3.0 was already an upgrade from an older version using grub? I can't remember to be honest, those servers have been sitting there for some time now.
I think it was related to the fact that the installer can't / couldn't install on RAID, so I did something around the lines of https://medium.com/@sthulb/rancher-os-raid-fc1128385de6.
I'll try a clean install as soon as I can!

If it's syslinux, you also need to refer to  https://forums.rancher.com/t/installation-rancher-os-no-grub-install/10225

It's been some time since I've had the time to have a look at this again, but today I tried again with 1.5.2. Basically the same setup:

A USB key (/dev/sdm) from which I boot with only syslinux and v1.5.2 (only contains /boot)
Two SSDs (/dev/sdf and /dev/sdk) in software RAID 1 with RANCHER_STATE label
A bunch of other disks for a zpool redacted from the output

[root@rancher ~]# ros -v
version v1.5.2 from os image rancher/os:v1.5.2

[root@rancher ~]# cat /proc/cmdline
BOOT_IMAGE=../vmlinuz-4.14.122-rancher rancher.state.mdadm_scan rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 initrd=../initrd-v1.5.2 rancher.autologin=tty1 rancher.autologin=ttyS0

[root@rancher ~]# blkid
/dev/sdf1: UUID="af61fda8-58a9-c40b-f337-7b5f25b5a2b5" UUID_SUB="92f1412c-a600-04aa-73da-465fca6f3b5d" LABEL="rancher:1" TYPE="linux_raid_member" PARTLABEL="RANCHER_STATE" PARTUUID="3950e825-85a1-4acb-b14e-5fb7ed229992"
/dev/sdm1: LABEL="RANCHER_BOOT" UUID="95cdf244-8191-4154-880c-0274f06e5b98" TYPE="ext4" PARTLABEL="RANCHER_BOOT" PARTUUID="37c8ce3b-eb3c-480c-876e-39ee93fd05ed"
/dev/sdk1: UUID="af61fda8-58a9-c40b-f337-7b5f25b5a2b5" UUID_SUB="955b1ccb-6a7d-5902-643b-b19291ac6c28" LABEL="rancher:1" TYPE="linux_raid_member" PARTLABEL="RANCHER_STATE" PARTUUID="e7321419-6980-4083-8e77-99b0c97a933a"
/dev/md1: LABEL="RANCHER_STATE" UUID="5ba5f121-20d5-450e-af3c-85ca754598eb" TYPE="ext4"

[root@rancher ~]# fdisk -l
Disk /dev/sdf: 232.9 GiB,<PHONE_NUMBER>16 bytes, 488397168 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: gpt
Disk identifier: 3F7B64FB-BB8B-F74C-89C3-E58DF4B0F13F

Device     Start       End   Sectors   Size Type
/dev/sdf1   2048 488397134 488395087 232.9G Linux filesystem

Disk /dev/sdm: 7.5 GiB,<PHONE_NUMBER> bytes, 15646720 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: gpt
Disk identifier: 34985674-D305-42FA-B6A1-4C8F68AF8D6C

Device     Start      End  Sectors  Size Type
/dev/sdm1   2048 15646686 15644639  7.5G Linux filesystem

Disk /dev/sdk: 232.9 GiB,<PHONE_NUMBER>16 bytes, 488397168 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: gpt
Disk identifier: 3F7B64FB-BB8B-F74C-89C3-E58DF4B0F13F

Device     Start       End   Sectors   Size Type
/dev/sdk1   2048 488397134 488395087 232.9G Linux filesystem

Disk /dev/md1: 232.8 GiB,<PHONE_NUMBER>68 bytes, 488132864 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: 0x20ac7dda

Device     Boot      Start        End    Sectors   Size Id Type
/dev/md1p1<PHONE_NUMBER><PHONE_NUMBER>  432871629 206.4G  7 HPFS/NTFS/exFAT
/dev/md1p2<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER> 931.5G 16 Hidden FAT16
/dev/md1p3               0          0          0     0B 6f unknown
/dev/md1p4        50200576  974536369  924335794 440.8G  0 Empty

Partition table entries are not in disk order.

[root@rancher ~]# cat /proc/mdstat
Personalities :
unused devices: <none>

Nothing in /proc/mdstat. I forgot to check fdisk -l and blkid before mdadm --assemble --scan, but I assume that /dev/md1 would be in the logs above. Once I run mdadm --assemble --scan:
[root@rancher ~]# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdf1[0] sdk1[1]
      244066432 blocks super 1.2 [2/2] [UU]
      bitmap: 0/2 pages [0KB], 65536KB chunk

unused devices: <none>

As for logs:
[root@rancher ~]# cat /var/log/syslog | grep mdadm
Jun 22 21:41:45 rancher kernel: [    0.000000] Command line: BOOT_IMAGE=../vmlinuz-4.14.122-rancher rancher.state.mdadm_scan rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 initrd=../initrd-v1.5.2 rancher.autologin=tty1 rancher.autologin=ttyS0
Jun 22 21:41:45 rancher kernel: [    0.000000] Kernel command line: BOOT_IMAGE=../vmlinuz-4.14.122-rancher rancher.state.mdadm_scan rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 initrd=../initrd-v1.5.2 rancher.autologin=tty1 rancher.autologin=ttyS0
Jun 22 21:42:42 rancher sudo:  rancher : TTY=tty1 ; PWD=/home/rancher ; USER=root ; COMMAND=/sbin/mdadm --assemble --scan
[root@rancher ~]# cat /var/log/messages | grep mdadm
Jun 22 21:41:45 rancher kernel: [    0.000000] Command line: BOOT_IMAGE=../vmlinuz-4.14.122-rancher rancher.state.mdadm_scan rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 initrd=../initrd-v1.5.2 rancher.autologin=tty1 rancher.autologin=ttyS0
Jun 22 21:41:45 rancher kernel: [    0.000000] Kernel command line: BOOT_IMAGE=../vmlinuz-4.14.122-rancher rancher.state.mdadm_scan rancher.state.dev=LABEL=RANCHER_STATE rancher.state.wait console=tty0 initrd=../initrd-v1.5.2 rancher.autologin=tty1 rancher.autologin=ttyS0

So I guess it's not related to the upgrade process but to newer versions, although it 100% worked previously. Am I missing something? Could it be that rancher doesn't wait long enough for drives to get picked up before running mdadm as I've got a bunch of drives? No hardware or BIOS configuration has changed in between those versions so I really have no clue what could be going on here.


Optimize code coverage structure

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.94%. Comparing base (2025ee2) to head (31e6939).

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #195      +/-   ##
=============================================
+ Coverage      61.59%   61.94%   +0.35%
=============================================
  Files            431      419      -12
  Lines          28079    27361     -718
  Branches        3746     3635     -111
=============================================
- Hits           17294    16948     -346
+ Misses         10446    10074     -372
  Partials         339      339

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add variables for land cover

This PR adds variables for land cover based on the xlsx overview developed by @flohump @realxinzhao and @kanishkan91.
This PR does NOT include subcategories for cropland and forests - this will be implemented in a follow-up PR once this discussion is finished and the iniatl set of land-cover variables are merged.
A few observations:

I added the variable "Land Cover|Water Ecosystems", which has been missing from the templates in NAVIGATE and ENGAGE
I assigned all water-ecosystems variables as tier 3
Is there a particular reason why glaciers are a sub-category of water ecosystems?
The variable for built-up area land cover was renamed for consistency with the naming convention, see here

Please review the descriptions.
@IAMconsortium/common-definitions-land

Removed the water-ecosystems land cover variables

Thanks for the extensions @flohump - merging now, let's revisit extensions and clarifications in follow-up PRs.


Distributed PCA

➤ Jafar Mohammadi commented:
The implementation in python and the old COINSTAC simulator works.
We are dealing with error handling, and error reports.


Find a better place to invoke setIsWorkflowInEffect than inside updateCMSFields

$this->setIsWorkflowInEffect() is invoked in updateCMSFields within WorkflowEmbargoExpiryExtension.php.
It may be better to refactor and invoke this somewhere else, e.g. within onBeforeWrite.

isWorkflowInEffect is not actually persisted to the database though, it's only used for things like determining which fields should be shown at a particular point in time.


Is it work with tile images that are stored in a folder in sdCard?

Hi moagrius.
Is it work with tile images that are stored in a folder in sdCard.
if yes than how can setUp tileView, please give some info.
private static String PATH = Environment.getExternalStorageDirectory()
+ File.separator +
"/projects/";
tileView.addDetailLevel( 1f,PATH + "524/tiles/tiles_%d_%d.png" , 256, 256);

Implement your own BitmapProvider.
public class BitmapProviderSdCard implements BitmapProvider {
  public Bitmap getBitmap( Tile tile, Context context ) {
    // do whatever you want to get and return the bitmap from the file on the SD card
  }
}

And tell your tileView instance to use it:
tileView.setBitmapProvider(new BitmapProviderSdCard());

are you saying i am supposed to return all bitmap recursively, m trying it from my side but if you provide some sample that would be great
thanks

it worked, one more thing i wanted to know how can i add child layer to TileView and capture child and tileView event separately Like OnClick,OnLongPress,

There are instructions for adding scaling and non scaling children in the readme


Added `ydb.RegisterParser(name string, parser func(value string) []…

…ydb.Option)` function for register parser of specified param name (supporting additional params in connection string)
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Other information

Codecov Report

Merging #307 (0e3ad58) into master (7590c56) will decrease coverage by 44.67%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           master     #307       +/-   ##
===========================================
- Coverage   61.78%   17.10%   -44.68%
===========================================
  Files         136      132        -4
  Lines       16615    16478      -137
===========================================
- Hits        10265     2818     -7447
- Misses       5775    13444     +7669
+ Partials      575      216      -359

Flag
Coverage Δ

1.14.x
?

1.15.x
?

1.16.x
?

1.17.x
?

1.18.x
17.10% <0.00%> (-44.68%)
:arrow_down:

connection
12.10% <0.00%> (-0.01%)
:arrow_down:

discovery
11.30% <0.00%> (-0.01%)
:arrow_down:

e2e
17.10% <0.00%> (-28.66%)
:arrow_down:

integration
17.10% <0.00%> (-28.66%)
:arrow_down:

macOS-latest
?

ratelimiter
13.90% <0.00%> (-0.01%)
:arrow_down:

scripting
?

table
?

ubuntu-latest
17.10% <0.00%> (-44.68%)
:arrow_down:

unit
?

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

options.go
64.15% <0.00%> (-8.27%)
:arrow_down:

internal/table/trailer.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/scheme/options.go
0.00% <0.00%> (-100.00%)
:arrow_down:

internal/table/keep_in_cache.go
0.00% <0.00%> (-100.00%)
:arrow_down:

balancers/config.go
0.00% <0.00%> (-95.09%)
:arrow_down:

internal/scripting/config/config.go
6.25% <0.00%> (-93.75%)
:arrow_down:

internal/value/value.go
0.00% <0.00%> (-93.28%)
:arrow_down:

internal/repeater/repeater.go
0.00% <0.00%> (-91.82%)
:arrow_down:

internal/table/client.go
0.00% <0.00%> (-88.06%)
:arrow_down:

internal/table/transaction.go
0.00% <0.00%> (-86.41%)
:arrow_down:

... and 80 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 7590c56...0e3ad58. Read the comment docs.


Why I cannot add text after lost focus in NumericUpDown of MahApp in C# WPF

I'm using C# WPF and MahApps Controls
I set a string format for Thousands separated like : #,### in NumericUpDown it's working when I typing number in that but when I lost focus of my NumericUpDown , I cannot add text end of it or between it ! I have to clear all of value in my NumericUpDown and that I can add text again
My XAML :
<Window

        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:mah="clr-namespace:MahApps.Metro.Controls;assembly=MahApps.Metro"
        xmlns:local="clr-namespace:WpfApp8"
        xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" x:Class="WpfApp8.MainWindow"

        mc:Ignorable="d"
        Title="MainWindow" Height="450" Width="800">

    <Grid>
        <mah:NumericUpDown Name="txtnumer"  HorizontalAlignment="Left" Margin="443,256,0,0" VerticalAlignment="Top" Height="41" Width="264" ParsingNumberStyle="Number" Culture="fa-IR" SnapToMultipleOfInterval="True" Value="0" ChangeValueOnTextChanged="True" Minimum="0" Interval="1" NumericInputMode="Decimal" Speedup="False" StringFormat="#,###"/>

    </Grid>
</Window>

How to Fix This ?

@mojtabahakimian I have no issues with your sample. Can you describe the problem in a little more detail?

Please see this :
https://im7.ezgif.com/tmp/ezgif-7-d5172ddb22ac.gif

Please see This :

https://im7.ezgif.com/tmp/ezgif-7-d5172ddb22ac.gif

Please See this :
https://im7.ezgif.com/tmp/ezgif-7-d5172ddb22ac.gif

@mojtabahakimian Ok, found it.

@mojtabahakimian Ok, found it.

Thanks , so when that will fix ?

Hi @mojtabahakimian
as this is a free-time project, it will be fixed when there is enough free time. Normally Jan is keeping an eye on the more annoying bugs 😄 .
Thank you for your patience & happy coding
Tim


Protect Main Branch

Summary
Add appropriate protections to the Main branch. If applicable, add protections to Development too.

Added directly through GitHub settings. No traceable PR.


1

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/cd209694-65b1-4d60-96e3-45a8b8407e3e

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/d81c3f2b-17c2-41ac-bbff-cf07f7402444

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/a761dfd8-55e9-4cb6-b12f-eeec99a19bbd

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/ca02086b-a9e7-4211-8f08-456a20d9402f

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/f8a43a37-a18c-42c2-9fb0-6fbfc15d8769

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/20eea397-3391-4962-8453-4e220a008fce

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/9e2c8fde-f794-4076-9bcf-d7be412f74e7

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/8b1c9731-b500-45d9-8d2c-ebddfa02b61c

https://github.com/AHUT507LAB/Infrared-dim-target-based-on-SiamRPN/assets/85088116/bcf05b42-f39b-44fa-85c4-132b48e15ca5


PR: Fix syncing of line number and plugin list for breakpoints and add unit tests.

Fixes issue #2179.

The unit tests were written before the change to make sure the change fixed the bug reported.
I refactored the code slightly to keep my change cleaner.  I hope that's OK.
With the unit tests, in the clear_breakpoints method, I put a note regarding the del.  It's not calling the __del__ in the class.

Thanks @csabella for your contribution! As I asked you last time: is this an issue in our 3.x branch too? If so, please move your branch to 3.x.
@rlaverde, please review @csabella's work, given that you're also working with the debugger ;-)

@ccordoba12   Technically it is a bug in 3.x, but since it's from an older bug report, I didn't know if you wanted to treat it as an enhancement instead.  I'll be more careful to use the right branch in the future.

@csabella, if an issue is marked as a bug and is present in 3.x, please solve it in 3.x. Only if it's marked as an enhancement, it needs to be worked in master.

I'll be more careful to use the right branch in the future.

Don't worry about it. In any case, you can ask us in the corresponding issue if it needs to be solved in master or 3.x.

@ccordoba12   I had to make some changes to the tests for 3.x.  I commented each line that I changed.  Would it be possible to modify those lines before merging with master?  The original version of the tests were passing under 4.0.  Thanks!

I had to make some changes to the tests for 3.x. I commented each line that I changed.

Maybe something like this, could do the trick:
from spyder import version_info

if version_info > (4,):
    ...

Although I'm not sure if it's the best way to do it

Btw, I'm not able to reproduce #2179, @csabella What was the error?

Maybe something like this, could do the trick

I also think we should follow a similar path regarding different behaviors for Spyder 3 and master in the tests you added @csabella.

Btw, I'm not able to reproduce #2179, @csabella What was the error?

The error was that the red dot was being marked on a line indicating that it was a breakpoint, but the breakpoint wasn't listed in the breakpoint plugin.
To recreate:

Add some lines of code to an editor.
Double click or F12 a line to add a breakpoint.  At this point, there's a red dot and it's in the list.
Double click again to remove the breakpoint.  It's gone from both.
Now, on the same line, Shift-F12 or Shift-Double-Click for the edit condition dialog.
Cancel from this dialog.
The red dot remains, but the breakpoint isn't in the list on the plugin.

I can't figure out the Travis error.  The only change I made between this commit and the previous commit was to add a check the Spyder version number on lines that had been commented out.  I would think that would make them basically the same, but yet, the last commit passed the tests and this one doesn't.

@csabella, I restarted the failing Travis slot. Sometimes we got segfaults in Travis that require a restart.


[Snyk] Security upgrade vm2 from 3.9.5 to 3.9.6

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

forms-flow-forms/package.json
forms-flow-forms/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

811/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 9.8
Sandbox Bypass SNYK-JS-VM2-2309905
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: vm2
    The new version differs by 11 commits.

94bf918 Update release date
2353ce6 Internal changes and security improvements
3a21c36 Merge branch 'master' of https://github.com/patriksimek/vm2
d03f150 Smaller fixes
7505410 Merge pull request #375 from XmiliaH/fix-374
c9cbff6 Add missed bigint
3482787 Specs may add more types to typeof.
8b9d039 Change to github badge and exclude editor config
a1491c2 Fix for node v6
106657c Also test node v6 and v8 and make v16 happy
ab245fe Add github npm test

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Sandbox Bypass

Relook at these tickets after the update to 5.0.0 has been finalized.


Update docstring formatting in getPotentialParentFromSettingValue

Description
The docstring was being rendered all crazy:

Turns out that the ordering of different sections in the docstrings matters, so moved the remainder of the description out of the "Parameters" block.

Checklist

[X] The commit message follows good practices.
[X] All docstrings are still up-to-date with these changes.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 81.426%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
23568

Relevant Lines:
28944

💛  - Coveralls


feat: Add custom headers for import

Related Issues
SITES-24434
We want Import as a service to be able to pass authentication information while trying to import a secured site.
This could be part of the options object (or a new requestBody attribute such as customHeader:{})  while making a post request to /tools/import/jobs.
It is currently possible in the helix-importer-ui: (Link: https://github.com/adobe/helix-importer-ui/blob/main/importer-guidelines.md#custom-headers)
We have to consider security - we do not want to store the bearerToken in the DB.
Reference PRs:
https://github.com/adobe/spacecat-import-job-manager/pull/80
https://github.com/adobe/spacecat-content-scraper/pull/145

Logging options and headers will be helpful for debugging through the logs. I noticed that logging entries aren’t present in the three PRs. Are there any other types of content, aside from authorization, that we might expect in custom headers?

Can validateRequestData(data) by updated to verify that customHeaders, if provided, is an object?


After changing the system time，Error

I register eventbus in oncreate, but an error will be reported: no subscribers registered for event.
If I change the system time back to normal, event register is success

you can just catch the exception

This error indicates there no methods annotated with @Subscribe.
Can you provide an example and more detailed steps to reproduce this? I'm not sure how system time could affect subscriber registration.
Maybe also have a look at the docs again. https://github.com/greenrobot/EventBus#eventbus-in-3-steps

maybe u did not add annotation @subscribe to your method

Closing because this issue is missing details. Feel free to comment with additional details and we can re-open it.


Missing tslib (or some other) dependency?

When running the tests I see this on the console of the server:

Error: @rollup/plugin-typescript: Could not find module 'tslib', which is required by this plugin. Is it installed?

The whole thing:
(node:62371) UnhandledPromiseRejectionWarning: Error: @rollup/plugin-typescript: Could not find module 'tslib', which is required by this plugin. Is it installed?
    at error (file:///Users/foolip/src/bidiInChromeContext/node_modules/rollup/dist/es/shared/rollup.js:5226:30)
    at throwPluginError (file:///Users/foolip/src/bidiInChromeContext/node_modules/rollup/dist/es/shared/rollup.js:18005:12)
    at Object.error (file:///Users/foolip/src/bidiInChromeContext/node_modules/rollup/dist/es/shared/rollup.js:18631:20)
    at preflight (/Users/foolip/src/bidiInChromeContext/node_modules/@rollup/plugin-typescript/dist/index.js:476:17)
    at Object.buildStart (/Users/foolip/src/bidiInChromeContext/node_modules/@rollup/plugin-typescript/dist/index.js:716:13)
    at file:///Users/foolip/src/bidiInChromeContext/node_modules/rollup/dist/es/shared/rollup.js:18835:25
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Promise.all (index 0)
    at async rollupInternal (file:///Users/foolip/src/bidiInChromeContext/node_modules/rollup/dist/es/shared/rollup.js:20254:9)
    at async read (file:///Users/foolip/src/bidiInChromeContext/src/.build/mapperReader.js:20:20)

I don't see a direct dependency on tslib, but something seems to be missing?

Can I ask you to check now? It should be solved by https://github.com/sadym-chromium/bidiInChromeContext/commit/37819845405b893d455303805f783cb29054be7b


Amplitude of  variables in Electrical.QuasiStationary library

Reported by anonymous on 20 Jan 2013 10:11 UTC
Complex algebra is successfully used in electrical quasi-stationary library.
Often in electric circuits amplitude of currents or voltages must be get.
To do this usage of "ModelicaComplexBlocks.ComplexMath.ComplexToPolar"
is tricky because it relies on atan2(), and therefore causes errors to occur whenever the quantity (for instance a current) to be converted into polar is null.
One of the following should be made:

use a safer code in ComplexToPolar to allow conversion into polar with null real complex numbers (i.e. giving null amplitude and whatever phase)
add am "amplitude" block in the  ModelicaComplexBlocks.ComplexMath. library.

Migrated-From: https://trac.modelica.org/Modelica/ticket/969

Comment by ahaumer on 20 Jan 2013 17:25 UTC

Reporters should provide their email-adress, not reporting as unknown.
No discussions possible!
I couldn't reproduce errors with null phasors fed to ComplexToPolar.
AFAIK atan2() is numerically safe.
Use ComplexToPolar, RealOutput "len", to get the amplitude = length of the phasor.
If we use Complex with length=RMS, we have to take into account a factor of sqrt(2).


stories, data in curly braces

Rasa NLU version: 0.12.3
Operating system: ubuntu 16.04
Issue:
There is an example of stories training data on stories documentation page:
* inform{"location": "rome", "price": "cheap"}  <!-- user utterance, in format intent{entities} -->
I couldn't find information of how to understand the data from curly braces. In particular, it is clear that user may write a message that is recognized as "inform" intention with entities "location" and "price" but what is the reason to provide (sample?) values for entities e.g. "rome", "cheap"?

@pwierzgala this looks like a core question, which may be answered more completely on the Core repo.
But I believe the syntax you are showing above is a short-hand of sorts for interacting with Core. So rather than sending Core a message like "I want information on a cheap trip to Rome." you can send it inform{"location": "rome", "price": "cheap"} which avoids using Rasa NLU for parsing. In this way you can test the stories/dialog of core independently from the classification and entity extraction of NLU.

@wrathagom Indeed I've posted the question in the wrong repo. I'm sorry for that. Please delete it. I'll browse questions in rasa core repo and repost it there if I won't find the answer.


Feature/history items

I have a little fix, which should have gone in the last PR.

Sorry for the much too late reply. I will close the PR because i will completely redevelop Flox. In the next version, you can change the date manually.


rkt: add -local flag to run/prepare.

This patch adds a -local flag to use only local images (if available) from the
local store.
If the provided image name is a URL-like app name (like coreos.com/etcd:2.0.9)
then discovery is disabled and the image is searched in the store using
cas.GetACI.
If the provided image name has an "http", "https", "docker" scheme it will avoid
downloading if it's not in the store (not existing in the remote table).
This can be useful to use rkt in offline mode or to just simply avoid
downloading.

I like this idea. Also not sure on the naming. Thoughts @philips @robszumski ?

@sgotti what do you think about making this more truly local, i.e it would also refuse to download URLs if they are not in the store?

@jonboulle good idea. Done. Se the updated description for the implemented logic.

LGTM after rebase and a few small things

@jonboulle Thanks for your review! Updated.

thanks <3


Error when extracting a backup made with "adb backup --twrp"

Hello,
I've tried using your tool to extract a backup of mine (+- 22G) and soon after it begins, it displays
Read 512  bytes
Data header type: twdatablock
Read 1048064  bytes
Wrote 1048064  bytes
Remaining bytes in backup file:<PHONE_NUMBER>0
Read 512  bytes
Corrupt start of data header

leaving me with a small "system.ext4.win" file that contains only little data.
Do you have any idea of what's causing it, if the backup was not made properly or if it's something else ?
Thank you !

I'll need some more information to debug this:

What OS are you running the tool on?
What was the exact command you ran?
Is what you posted the entire output? If not, could you attach a full transcript?
Would you be willing to (privately) provide me with your input file? Your partial output file?

UPDATE:
So I wrote this tool to extract a backup of my data partition. I did no other testing. Just now for sanity I tried rerunning it on my backups.
On my data.ab file I get:
...
Remaining bytes in backup file: 1763840
Read 512  bytes
Data header type: twdatablock
Read 1048064  bytes
Wrote 1048064  bytes
Remaining bytes in backup file: 715264
Read 512  bytes
Data header type: twdatablock
Read 713728  bytes
Wrote 713728  bytes
Remaining bytes in backup file: 1024
Current offset:<PHONE_NUMBER>0
Read 512 bytes
File trailer type: md5trailer
Read 512 bytes
End ADB type: twendadb

But when I run on system.ab I get:
...
Remaining bytes in backup file: 1379328
Read 512  bytes
Data header type: twdatablock
Read 1048064  bytes
Wrote 1048064  bytes
Remaining bytes in backup file: 330752
Read 512  bytes
Corrupt start of data header

So since I can apparently reproduce your error, I have enough information to continue for now.
Out of curiosity, are you able to successfully extract your data partition?

@PetitCassoulet I was able to successfully extract my system.ab with commit 8fad6b3.
Can you try again with latest master?

Hello @arifogel,
I'm really sorry for only answering now but I was quite busy this week.
I tried on the latest master and am still getting "Corrupt start of data header", I'll give you more info on my system and how I am using your tool :
What OS are you running the tool on? archlinux
What was the exact command you ran? twrpabx *mysavefile*
Is what you posted the entire output? If not, could you attach a full transcript? It was not, here is a more complete one https://pastebin.com/JMmd2niZ, I skipped the middle of the log because it's quite repetitive
Would you be willing to (privately) provide me with your input file? Your partial output file? I have lots of personal data, isn't there another way around ? And the system partition seems to be extracted just fine btw.
What version of ADB did you use (first line of output from running adb with no arguments)? version 1.0.40
What version of TWRP did you use to make the backup? For what device? The latest for OnePlus 3T
Which partitions are supposed to be in the backup file? All of them, but I could try doing separate save files for separate partitions.

I will be more reactive on your following answers, thank you a lot for taking time to solve my issue !

@PetitCassoulet So I haven't tested with multi-partition files. Can you try with one partition per file and let me know how that goes? In the meantime on my end I will try to produce and extract a multi-partition backup.

@PetitCassoulet with respect to your input file: Would you be willing to provide a multi-partition input file not including your data partition? I don't think there should be any personal information on the other partitions. For instance, cache and system?

Closing due to inactivity.

Hey. I'm having the same problem: "corrupt start of data header" with multi-partition backup. Have you found a fix yet?

@Chydzim  Can you provide the information I requested from @PetitCassoulet earlier?

I'll need some more information to debug this:

What OS are you running the tool on?
What was the exact command you ran?
Is what you posted the entire output? If not, could you attach a full transcript?
Would you be willing to (privately) provide me with your input file? Your partial output file?
EDIT:
What version of ADB did you use (first line of output from running adb with no arguments)?
What version of TWRP did you use to make the backup? For what device?
EDIT 2:
Which partitions are supposed to be in the backup file?

@Chydzim Can you provide the information I requested from @PetitCassoulet earlier?

I'll need some more information to debug this:

What OS are you running the tool on?
What was the exact command you ran?
Is what you posted the entire output? If not, could you attach a full transcript?
Would you be willing to (privately) provide me with your input file? Your partial output file?
EDIT:
What version of ADB did you use (first line of output from running adb with no arguments)?
What version of TWRP did you use to make the backup? For what device?
EDIT 2:
Which partitions are supposed to be in the backup file?

What OS are you running the tool on? Ubuntu from microsoft store.
What was the exact command you ran? twrpabx backup.ab
Is what you posted the entire output? If not, could you attach a full transcript?
Data header type: twdatablock Read 1048064  bytes Wrote 1048064  bytes Remaining bytes in backup file:<PHONE_NUMBER>4
A few hundred lines later
Data header type: twdatablock Read 1048064  bytes Wrote 1048064  bytes Remaining bytes in backup file:<PHONE_NUMBER> Read 512  bytes Data header type: twdatablock Read 1048064  bytes Wrote 1048064  bytes Remaining bytes in backup file:<PHONE_NUMBER> Read 512  bytes Corrupt start of data header2
Where "header2" is the line 96 with your "possible fix". I numbered lines which contains it to identify where the error occurs.
Would you be willing to (privately) provide me with your input file? Your partial output file? Not really, because data there is sensitive. Sorry.
What version of ADB did you use (first line of output from running adb with no arguments)? Don't remember, I updated ADB after making backup due to problems with bootloader.
What version of TWRP did you use to make the backup? For what device? twrp-3.2.1-1-addison
Which partitions are supposed to be in the backup file? System, data, cache, boot.

Sorry for lack of progress - full-time job and all.
I'm going to try to upgrade my phone OS this weekend, and will take the opportunity to add support for extracting everything my phone produces with TWRP backup.
Maybe even add some tests ;)
Hopefully that helps with your files.

HI There.
Did you get anywhere with this? :) I'm trying to extract specific files from a multi-partition backup. hoping I can use this tool?

@AntiSol Unfortunately I lost the phone that used a version of TWRP using this format. And this backup method has been deprecated and is no longer available in current versions of TWRP. So I have no way of producing multi-partition backups in this format to do any testing.
Given lack of personal incentive nor means to continue development, I will be archiving this repo.


Dead link to the font properties editor

The “Font properties editor” link is dead. It should point to https://docs.microsoft.com/en-us/typography/tools/font-properties-editor.

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

ID: 0a1c6588-f887-46ea-8f19-aed067e6c0d5
Version Independent ID: 76804d51-3c1a-761f-48ea-b6e176aaf286
Content: Register as a typography vendor - Typography
Content Source: typographydocs/vendors/register.md
Product: windows
GitHub Login: @mijacobs
Microsoft Alias: mijacobs

Done!


Greentea to test main application

Description

Issue request type

[x] Question
[ ] Enhancement
[ ] Bug

Can we use greentea to directly test a function inside a main.cpp file rather than testing the test cases in test suite?

This belongs in the forum but the answer is yes as long as you have your tests in a main.cpp in a folder named 'TEST'.
Probably a way to use symlinks to accomplish this if you actually want your tests built into your application for whatever reason.

How exactly do I use symlinks here could you explain.


new Card() on deleted card

Hello,
Not sure where fault is between my code and Manatee.Trello.
How to reproduce:

Create card in Trello web interface.
Store Card.Id in your code
Edit card, then click on Archive and then on Delete

Now try to get card giving card id stored
var card = New Card(storedCardId);
It should throw exception, but it does not
If trying to get card.ShorUrl, code hangs indefinitely

I'll look into this one.  I would expect that it would throw some manner of "not found" exception when attempting to access the card.ShortUrl property.

I expect New Card Method to throw exception like it does if I pass a fully non existing card or board Id.
Even before requesting attribute.
Behavior is just not the one expected if the card existed but was archived + deleted

There is some checking I can do upon creation to validate it, but I can't check everything.  The long ID is a MongoDB timestamp-based ID, so I can validate that (it's also how I get the creation date).  However, I can't do anything beyond that without making a call.

If I do:
 var test = New Card("NOTEXISTINGENTRY");
It generates an exception, which I catch. This is how I test if a card exists.
Now, If I do the same on card that existed in the past (so I stored Id), but then was deleted by user, exception is not generated. Maybe Trello API is not providing same answer if Id was walid before?

That's because your ID isn't valid. My validation catches that.  But when you use an ID from a deleted card, it passes my validation, the only way I can determine if the card is present is by attempting to download. At that point, and exception is thrown (based on my testing).

ok so in my test I need to also get a property to be sure it does exist, but not shortUrl as it hangs indefinitely ?

I wasn't getting the hang in my tests. I'm not certain what is causing that for you.

@mathieuchateau are you still experiencing problems with this?

Hello,
It's not hanging anymore, and does generate an exception "requested resource not found", which is what I expected.
I guess we can close this case, thanks


Auto delete option doesn't work

Although legacy image selection is activated with Auto delete, a copy is created after exif deletion and the original is not deleted. This results in duplicate images.

LineageOS 21, Android 14

Android is restrictive with respect to what can be deleted and what not. Deleting an image that was selecting from within the app will succeed (with legacy im. sel.), but attempting to delete an image shared to the app will not work in many cases due to missing permissions.
Did you attempt to share the image to the app, and if so which app did you use?

To clarify: Deletion will only work from images selected from within ExifEraser, i decided not to implement broader handling as many gallery apps won't grant write permissions required for image deletion

Android is restrictive with respect to what can be deleted and what not. Deleting an image that was selecting from within the app will succeed (with legacy im. sel.), but attempting to delete an image shared to the app will not work in many cases due to missing permissions. Did you attempt to share the image to the app, and if so which app did you use?

I tried it with LineageOS's built-in file explorer, image viewer "Gallery", Material Files (my main file explorer) and Aves (my main image viewer).

I've tested with some of these apps, deletion is not possible due to restrictive uri access, so there is nothing that can be done to resolve this.


Missing required parameter: response_type

Describe the bug
Hi, we are seeing this intermittent Auth0 issue from one of our flask applications, "Missing required parameter: response_type". We do not send response_type via neither metadata nor kwargs. Therefore, it should just be supplied 'code'. We are wondering if the root of this issue could be on our end.
Error Logs
{
"date": "2020-10-29T07:12:57.995Z",
"type": "f",
"description": "Missing required parameter: response_type",
"connection_id": "",
"ip": IP,
"user_agent": "Other 0.0.0 / Other 0.0.0",
"details": {
"body": {},
"qs": {},
"error": {
"message": "Missing required parameter: response_type",
"oauthError": "invalid_request",
"type": "request-error"
}
},
"hostname": OUR_HOST_NAME
"log_id": "90020201029071303317000567544959084225084138735571828754",
"_id": "90020201029071303317000567544959084225084138735571828754",
"isMobile": false
}

Expected behavior
response_type should not be missing from the authorization URL.
Environment:

OS: Amazon Linux
Python Version: 3.7.x
Authlib Version: 0.14.3

Additional context
This is how we set up in our codebase:
auth0 = OAuth(app).register(
    'auth0',
    client_id=SETTINGS.auth0_client_id,
    client_secret=SETTINGS.auth0_client_secret,
    api_base_url=SETTINGS.auth0_custom_url,
    access_token_url=f'{SETTINGS.auth0_custom_url}/oauth/token',
    authorize_url=f'{SETTINGS.auth0_custom_url}/authorize',
    client_kwargs={
        'scope': 'openid profile email',
    },
)

# A function to redirect to the Auth0 login page
return auth0.authorize_redirect(redirect_uri=_server_url('/login_callback'),
                                state=nonce,
                                **query_parameters) # `response_type` not included

@JamieQeexo according to our code: https://github.com/lepture/authlib/blob/master/authlib/oauth2/client.py#L136
You can see, if there is no defined response_type, the default value is code.


MAGICDRAW-868

SR now first creates the list of all redefinable elements and filters out the not-leafes.
Fixes issue with circular reference warning.

Added changes.

This pull request fixes 1 alert - view on lgtm.com
fixed alerts:

1 for Container contents are never accessed

Comment posted by lgtm.com

Looks good now, lgtm issue seemed to be older.

This pull request fixes 1 alert - view on lgtm.com
fixed alerts:

1 for Container contents are never accessed

Comment posted by lgtm.com

This pull request fixes 1 alert - view on lgtm.com
fixed alerts:

1 for Container contents are never accessed

Comment posted by lgtm.com


About Training Epochs &  GPU Memory

Thank you very much for your excellent work.I would like to build on your work and try some new ideas. However, I am currently encountering some issues. Could you please provide me with some suggestions or solutions? I would be very grateful for your help.
1.When I try to reproduce the YOLOv-S and YOLOv++-S models on a single 3080Ti GPU following your configuration, I sometimes encounter a "CUDA out of memory" error. Using nvidia-smi, I noticed that the GPU memory usage fluctuates significantly, which is uncommon in typical deep learning scenarios. Could this behavior be related to the multi-scale training mode or EMA training mode?
2.Regarding the first issue, when I attempt multi-GPU training, the program gets stuck and eventually throws a timeout error. Is there any way to enable single-machine multi-GPU training?
3.In your YOLOv-S experiments, the maximum epoch is set to 7. I noticed that the loss remains high near the end of the training. I tried increasing the maximum epoch to 14, but the loss is still quite large.Does having a high loss significantly impact the training results? Should I train for more epochs or reduce the learning rate to improve the performance?

For the first question, the GPU memory usage is related to the candidate proposal numbers, you may set the maximum limitation as a hyper-parameter in (300 will be ok for 11G GPU memory):
https://github.com/YuHengsss/YOLOV/blob/5f069b29e201c4e099c7c3827cc6c63823ce3141/exps/yolov%2B%2B/v%2B%2B_base_decoupleReg_2x.py#L44
For the second question, due to the limited computational cost and my limited coding ability when I try Video Object Detection, the multi-GPU training is not well supported.
For the third question,  there are some losses belonging to the base detector that is not optimized (see here). In my experience on ImageNet VID dataset, the best performance could be obtained in three or four epochs and will decrease then.

Thank you very much for your suggestions and for the outstanding work you have provided.


how could i use amplitude using reqiurejs?

t.amplitude.runQueuedFunctions is not a function
i 've got this error when i load amplitude 's core script using requirejs, who could please help me with it?

Since you're using requirejs, you probably don't want to use our code snippet and just grab the direct link to the SDK. Following this article you would probably want to do something like this:
<script src="http://requirejs.org/docs/release/2.1.5/comments/require.js"></script>
<script type="text/javascript">
  require.config({
    paths: {
        "amplitude": "https://d24n15hnbwhuhn.cloudfront.net/libs/amplitude-2.6.1-min.gz.js"
    },
    waitSeconds: 40
  });
</script>

@djih i think i could also use your code snippet but this error occurs when i use your code snippet:
t.amplitude.runQueuedFunctions is not a function

and sometimes this would occur too:
Uncaught Error: Mismatched anonymous define() module: function (){return require("1")}

@cdll Are you putting our snippet after you load Requirejs?

@djih yep～i make a script to load requirejs, and then make a script to use your code snippet.
`
`

@djih ok, thanks a lot. i 've just use the require method u gave me to fit my need, cause i got some old script that i want to use before. now i abandon to use the old script. thank u all the same~


Exposure Notification telemetry sent by Google Play Services

Thanks for posting this code.  My understanding is that Google Play Services collects telemetry relating to the operation of the Exposure Notification module, and transmits this to backend servers by default (i.e unless the "usage & diagnostics" option is disabled).   Since this telemetry is currently undocumented, it would be v helpful to include the Exposure Notification code that generates this telemetry so that we can see what data is actually collected.

Hi, thanks for the feedback. Have you seen the Exposure Notifications telemetry design document?


Saving-Loading BILSTM-CRF model ValueError: Layer - loss missing

I set up a BILSTM-CRF model for sequence labelling, very similar to this example (https://github.com/farizrahman4u/keras-contrib/blob/master/examples/conll2000_chunking_crf.py).
from keras.layers  import Dense, Masking
from keras.layers import Dropout
from keras.layers import Bidirectional
from keras.layers import LSTM
from keras.models import Sequential
from keras.optimizers import Adam
from keras_contrib.layers import CRF

self._model = Sequential(name='core_sequential')
self._model.add(Masking(mask_value=0., input_shape=(None, input_size)))

self._model.add(Dropout(dropout_rate,name='dropout_layer_1'))
self._model.add(Bidirectional(LSTM(units=hidden_unit_size,
                                     return_sequences=True,
                                     activation="tanh",
                                     name="lstm_layer"),
                                     name='birnn_layer'))
crf = CRF(2, sparse_target=True)
self._model.add(crf)
self._model.compile(optimizer=Adam(lr=lr), loss=crf.loss_function, metrics=[crf.accuracy])

self._model.fit(x_train, y_train, validation_data=(x_val, y_val), epochs=epochs, batch_size=batch_size,
                            verbose=verbose, shuffle=shuffle)

self._model.save(filename)

The model was trained successfully and I also successfully called the predict_classes() function, as soon as I trained it and I had the object after training...
Then I tried to load it back, like it is mentioned in the wiki "A Common "Gotcha", importing the additional layer, before calling load_model() function :
from keras.models import load_model
from keras_contrib.layers import CRF

self._model = load_model(filename)

The error message is:
[...]
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/utils/generic_utils.py", line 140, in deserialize_keras_object
    list(custom_objects.items())))
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/models.py", line 1202, in from_config
    layer = layer_module.deserialize(conf, custom_objects=custom_objects)
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/layers/__init__.py", line 54, in deserialize
    printable_module_name='layer')
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/utils/generic_utils.py", line 133, in deserialize_keras_object
    ': ' + class_name)
**ValueError: Unknown layer: CRF**

So, I changed to:
from keras_contrib.layers import CRF

self._model = load_model(filename, custom_objects={'CRF':CRF})

The new error says that the loss is missing also:
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/engine/training.py", line 751, in compile
    loss_function = losses.get(loss)
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/losses.py", line 96, in get
    return deserialize(identifier)
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/losses.py", line 88, in deserialize
    printable_module_name='loss function')
  File "/Users/kiddo/anaconda/lib/python3.6/site-packages/keras/utils/generic_utils.py", line 157, in deserialize_keras_object
    ':' + function_name)
**ValueError: ('Unknown loss function', ':loss')**

I tried extending the custom_objects dict with ':loss':CRF.CRF.loss_function', but I still have the same error...
Any idea about that?

I too have the same issue

Found a solution use
from keras_contrib.utils import save_load_utils
Save your model using
save_load_utils.save_all_weights(model,filename)
Easily load it back, by just specifying the architecture how the model was built and load all the weights back by
save_load_utils.load_all_weights(model,filename)
I did it and it worked fine for me.

Thanks a lot it works fine for me also! A bit tricky and sloppy though, I need to add an if statement in my loader() to discriminate the loading between other models from 'CRF'-extended ones :)

I use save_load_utils.load_all_weights(model,filename) to load the model and it works. However, the model.predict() function is quite slow, it takes around 400ms to predict a single input. How to speed up the prediction?

thx guys. well, saving function was okay but once i try to load the model by using load_all_weights(model,filename), then, the error below throws:
in load_all_weights
topology.load_weights_from_hdf5_group(f['model_weights'], model.layers)
AttributeError: 'NoneType' object has no attribute 'layers
any idea how to fix?

@yzho0907 by your error message it seems that you are setting model = None and then invoking load_all_weights(...), although you first need to reconstruct your model instead.
Guys, the only way that I've found to make this solution to work was using the following snippet, where build_bidirectional_model builds the model on examples/conll2000_chunking_crf.py. Do you have any ideas on solutions or possible causes for that?
loaded_model = build_bidirectional_model(vocab_size, EMBEDDING_DIM,
                                        LSTM_OUTPUT_SIZE, amount_classes,
                                        compile=True)

save_load_utils.load_all_weights(loaded_model, STORED_MODEL_FILENAME,
                                 include_optimizer=False)

loaded_model.evaluate(...)

If I set include_optimzer=True I receive the following error message:
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-80-b0de98ab256e> in <module>()
      2                                   100, amount_classes, True)
      3
----> 4 saver.load_all_weights(loaded_model, TEST_FILE, True)
      5
      6 # model2.compile('nadam', loss=crf.loss_function, metrics=[crf.accuracy])

~/miniconda3/envs/bicrf/lib/python3.6/site-packages/keras_contrib/utils/save_load_utils.py in load_all_weights(model, filepath, include_optimizer)
    106             optimizer_weight_values = [optimizer_weights_group[n] for n in
    107                                        optimizer_weight_names]
--> 108             model.optimizer.set_weights(optimizer_weight_values)

~/miniconda3/envs/bicrf/lib/python3.6/site-packages/keras/optimizers.py in set_weights(self, weights)
    111                              str(len(weights)) +
    112                              ') does not match the number of weights ' +
--> 113                              'of the optimizer (' + str(len(params)) + ')')
    114         weight_value_tuples = []
    115         param_values = K.batch_get_value(params)

ValueError: Length of the specified weight list (37) does not match the number of weights of the optimizer (0)

How to use this using checkpoint in keras?

Same error here @lzfelix

I can't even use save_load_utils. It's getting an import error
from keras.engine import saving

ImportError: cannot import name 'saving'

For reference, the solution posted on #129 seems to work, although #272 is addressing this problem.

As an update, I managed to fix the saving import error by just updating keras (and modifying something in models.py). Now save_load_utils seems to work properly (.evaluate() gives me the same score on the same test data before and after loading...)

@mary-octavia did u mean updating keras to the latest version? if not, which version? thx

@mary-octavia   same problem  with keras '2.2.2',tf '1.10.1';

Following worked for me.
Save your model by using
model.save(filename)

or
model.save_weights(filename)

And you can load it back by model.load_weights(filename) after specifying the model architecture

@csJd really? Did that work for you using crf from keras_contrib.layers?

@csJd really? Did that work for you using crf from keras_contrib.layers?

yes, keras.model.load(filename) not work, but model.load_weights(filename) worked for me

If you just care using them for predictions (production) and not retraining them, the default dump() and load() functionalities are both working just fine for models including CRF layers based on the latest updates in the code using Keras 2.2.0 with just a naive "hack".
Example:
def fake_loss(y_true, y_pred):
    return 0

model.save(filename)
model = load_model(filename, custom_objects={'CRF': CRF, 'loss': fake_loss})

PR #318 should have fixed this problem. Please refer to the CRF new docs and example in the test folder.

Closing this issue as it seems resolved. Thanks @lzfelix .

Thanks a lot @ParthShah412 It works fine for me also! A bit tricky and sloppy though... I need to add an if statement in my loader() to discriminate the loading between other models from 'CRF'-extended ones :D

can you please share me how you solved the issue i am also facing thee same.

I solved the unknown crf layer using:-
from keras_contrib.layers.crf import CRF, crf_loss, crf_viterbi_accuracy
newmodel = load_model(model_name, custom_objects={"CRF": CRF, 'crf_loss': crf_loss,
'crf_viterbi_accuracy': crf_viterbi_accuracy})
It works good for me!!!


mac-screen-capture-permissions causing Unhandled Promise Rejection

Sentry Issue: KAP-BPC

macOS version:    Monterey (12)
Kap version:      3.5.3
Unhandled Promise Rejection

Error: Command failed: /Applications/Kap.app/Contents/Resources/app.asar.unpacked/node_modules/mac-screen-capture-permissions/screen-capture-permissions
spawnSync /Applications/Kap.app/Contents/Resources/app.asar.unpacked/node_modules/mac-screen-capture-permissions/screen-capture-permissions Unknown system error -86
    at Function.module.exports.sync (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/mac-screen-capture-permissions/node_modules/execa/index.js:168:25)
    at exports.hasScreenCapturePermission (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/mac-screen-capture-permissions/index.js:27:25)
    at ensureScreenCapturePermissions (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/common/system-permissions.js:64:23)
    at /Applications/Kap.app/Contents/Resources/app.asar/dist-js/index.js:102:65

Could this possibly be fixed by updating mac-screen-capture-permissions @karaggeorge? Asking since it's your package so you may know a bit more here.

As a troubleshooting step I tried manually granting Kap screen recording access (System Prefs -> Security -> Screen Recording -> Click '+' and add Kap.app), but that did not help unfortunately

I have the same problem here.
Adding kap.app to security didn't help either. Any progress?
(macOS 12.3.1, M1)

Same issue here
(macOS 12.4, M1)

for me a simple reinstall fixed the problem. :man_shrugging:

Wow... reinstall really fixes the problem. Thanks!

Confirmed on MacOS, 12.3.1, M1 that a reinstall fixes permissions issue mentioned above

I'm still seeing this on macOS 12.4 on an M1 computer. I tried a full reinstall, and also manually adding the screen recording permissions for Kap, but no luck. This machine currently does not have Rosetta installed, which could possibly be a factor (another machine with the same specs that does have Roesetta installed is not having this problem).

Digging into this a little more, the  Unknown system error -86 messaging makes me fairly confident this is due to some upstream dependency not being compatible with M1 machines. I suspect installing Rosetta would resolve this (ideally Rosetta would not be required, or at least a more graceful failure would be in place). I've seen this error on other applications though that required Rosetta in order to work.
(The "collect and report" option for this crash takes me to https://github.com/wulkano/Kap/issues/1106, which was marked as a duplicate of https://github.com/wulkano/Kap/issues/1070, but this does appear to be a distinct issue based on the trace.)

I ran into this after upgrading from Big Sur to Monterey.  I was eventually able to get things working after trying the following a few times:
brew install --cask kap
open /Applications/Kap.app

When the System Preferences Privacy dialogue came up, I  pressed - to remove Kap. I then clicked + to add /Applications/Kap.app. Quit Kap & re-open. I tried variations of this a few times and it didn't work... so your mileage may vary!
Also, the Kap issue tracker has a bunch of seemingly duplicate issues related to this problem.

I had to revert #1129 as it causes problem when built for production. The binary used in the capture permission thing could not be found and I don't have time to look into it. If someone wants to work on this, make sure you test the change by running npm run dist and try launching the app in the dist folder.

Hi, just confirming that this issue persists. MacBook Pro 2021 (Apple arm CPU, Mojave OS).
Kap doesn't work at all. I tried to reinstall Kap / reallow permissions / reboot mac around 10 times in various orders (as suggested above), but it didn't help. I love Kap and am looking forward to using it again, I hope somebody knows how to fix this. Thanks in advance, fingers crossed 😉 🤞

Woops, didn't notice the prebuilts for that package weren't uploaded. I tried to see if it was possible to fix the github action that creates the prebuilts, but the prebuild library fails to upload the binaries to the release, and I'm not entirely sure why. Also, I don't think github has ARM Mac runners yet (can track it here https://github.com/github/roadmap/issues/528), so we'd also need to upload the prebuilts from their own self hosted ARM Mac, or just skip using prebuilts on ARM Macs.
Although with version 3.5.5, the error doesn't seem to come up for me anymore. For anyone that had issues installing Kap 3.5.4, try installing 3.5.5 to see if it fixes the issue. If the issue persists, we might need to address the issues I mentioned above, or use this library instead https://github.com/codebytere/node-mac-permissions#permissionsaskforscreencaptureaccess.

Hi, on Macbook Pro 2021 (arm CPU, MacOS Mojave) with Kap 3.5.5:

if Rosetta (x86_64 emulator) is NOT installed, Kap raises the exception and doesn't work at all
if Rosetta is installed, Kap works
--> Kap is not working on the pure ARM, but it works with the Rosetta emulator "workaround".

PS: To install Rosetta, run softwareupdate --install-rosetta --agree-to-license

Any chance of getting a fix for this for machines without Rosetta installed?

This error also occurs for me

MacBook Pro (M1 Pro - 2021)
macOS Ventura 13.1
Kap version: 3.6.0

Unhandled Promise Rejection
Error: Command failed: /Applications/Kap.app/Contents/Resources/app.asar.unpacked/node_modules/mac-screen-capture-permissions/screen-capture-permissions
spawnSync /Applications/Kap.app/Contents/Resources/app.asar.unpacked/node_modules/mac-screen-capture-permissions/screen-capture-permissions Unknown system error -86
    at Function.module.exports.sync (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/mac-screen-capture-permissions/node_modules/execa/index.js:168:25)
    at exports.hasScreenCapturePermission (/Applications/Kap.app/Contents/Resources/app.asar/node_modules/mac-screen-capture-permissions/index.js:27:25)
    at ensureScreenCapturePermissions (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/common/system-permissions.js:64:23)
    at Object.openCropperWindow [as open] (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/windows/cropper.js:81:66)
    at Object.openCropperWindow (/Applications/Kap.app/Contents/Resources/app.asar/dist-js/tray.js:26:129)

I believe I have fixed the issue. Please see this MR.
https://github.com/wulkano/Kap/pull/1181

After reinstalling the app the issue is not present anymore

I did two things and the error went away:

Restarted
Installed Rosetta for old intel apps  (even though I'm using the latest KAP version for Apple Silicon)

I did two things and the error went away:

Restarted my Mac (MacBook Pro M2)
Installed Rosetta for old intel apps  (even though I'm using the latest KAP version for Apple Silicon)

@alvarotrigo Thanks, it worked.
For those who want to make this workaround:

Run in the terminal: softwareupdate --install-rosetta
Re-open the app

Same error on MacBook Air M1. And Rosetta crashes on me. So doesn't work.

Installing Rosetta via Terminal worked for me. Did not have to reinstall or re-open the app.

Confirmed working for M4 with Rosetta 2

This worked for me as well, new Mac M3 on OSX 15.2.


[Azure Search] Remove the "track2" version of 2019-05-06-Preview swaggers

This PR https://github.com/Azure/azure-rest-api-specs/pull/7615 introduced (as a work in progress) swagger for the REST API version 2019-05-06-Preview
It was introduced in the carved out "track1" directory as well as the non-carved out "track2" (base) directory - we expected work on both to happen in parallel.
However, the Azure search is now ready to add features (and finish the progress) for "track1" 2019-05-06-Preview; and we don't have plans on "track2" until next year - meaning, if we keep both copies around, we'll be required to duplicate changes unnecessarily.
This PR eliminates the "track2" copy in the hopes that in the future when are ready to work on it, a different PR will introduce it.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

Can one of the admins verify this patch?


3 create interfaces for frames

Adding interface macro
Basic model interfaces

There are some issues with the @interface function, it throws an UndefVarError because it does not recognise the NotImplementedError contained in their default behaviour.

The function  load(provider::Type{<:AbstractEphemerisProvider}, files) already provides an implementation, will the  @interface macro override that?

I just don't agree on adding the dependency of SMDGraphs at this point. Why can't we just declare in this pull request the AbstractGraphNode type in the interfaces and later make SMDGraphs inherit from it? We would just be introducing a dependency that we would have to fix with another pull request.

I don't really see the point on having AbstractFrameGraphPointNode and AbstractFrameGraphAxisNode in the interfaces. In FrameTransformations FrameAxesNode and FramePointNode are completely internal types that only depend on the way the frame system has been designed and thus should not require an interface definition. On the other hand, if they are intended to provide an abstract supertype for AbstractFramePoint and AbstractFrameAxes, I believe that we should stick with integer numbers (i.e., the NAIF IDs) to identify point and axes at the interface level.

Why is the AbstractFrameGraphModel parametric in T?

I would remove the parametric type for the time argument of all the transformation functions. It should be left as a generic Number field as currently implemented in FrameTransformations. I'm also a bit concerned about documenting those functions. It could mean that everytime the user looks at the documentation, it is always going to read that before the actual documentation of the function that is currently implemented in FrameTransformations. Any thoughts?

Everything was solved with the previous commits.

The function load(provider::Type{<:AbstractEphemerisProvider}, files) already provides an implementation, will the @interface macro override that?

No, the implementation will be working correctly.

I just don't agree on adding the dependency of SMDGraphs at this point. Why can't we just declare in this pull request the AbstractGraphNode type in the interfaces and later make SMDGraphs inherit from it? We would just be introducing a dependency that we would have to fix with another pull request.

Agreed, dependency dropped.

I don't really see the point on having AbstractFrameGraphPointNode and AbstractFrameGraphAxisNode in the interfaces. In FrameTransformations FrameAxesNode and FramePointNode are completely internal types that only depend on the way the frame system has been designed and thus should not require an interface definition. On the other hand, if they are intended to provide an abstract supertype for AbstractFramePoint and AbstractFrameAxes, I believe that we should stick with integer numbers (i.e., the NAIF IDs) to identify point and axes at the interface level.

Agreed, AbstractFrameGraphPointNode, and AbstractFrameGraphAxisNode were removed.

Why is the AbstractFrameGraphModel parametric in T?

This is to provide eventual compatibility with Graphs.jl. I would keep it like that.

I would remove the parametric type for the time argument of all the transformation functions. It should be left as a generic Number field as currently implemented in FrameTransformations. I'm also a bit concerned about documenting those functions. It could mean that every time the user looks at the documentation, it is always going to read that before the actual documentation of the function that is currently implemented in FrameTransformations. Any thoughts?

Agreed, time is left generic as Number.
The documentation of the packages implementing the interfaces will not see the documentation of the interfaces.


How can i stop the animation ?


feat: set up happy to be deployed to theia

https://czi-tech.atlassian.net/browse/CCIE-3069
Summary:

What: <brief description>
Ticket: sc<fill_in_issue_number>
Env: <rdev link>

Demos:
Notes:
Checklist:

[ ] I merged latest <base branch>
[ ] I manually verified the change
[ ] I added labels to my PR
[ ] I tested in multiple browsers
[ ] I added relevant unit tests
[ ] I have notified others of changes they need to make locally (migrations, jobs, package updates, etc)

@kuannie1 this one is fine, or make a new branch from this branch and stack the PRs


File naming in CEN2

I have just realized that we adjust not only civil parish and census district names to fit within 20 characters (A constraint we are removing)
But we actually change the piece naming used by TNA in our naming of vld files and in much of our documentation. rg RS 9/1 .... RS 9/1889
We drop the space after the RS , we insert a leading 0 before the 9, we drop the / after the series and before the numeric  ie RS091889
I gather this was also to accommodate an 8 character limitation.
We are going to run into a problem with 1911 and likely 1921 there there are more than 9999 pieces ie the series runs from  RG14/1 to RG14/19412
The initial design of CSVProc was it uses the file name to identify the piece. My initial coding had been around an 8 character field (I knew not better)
Is now the time to stop messing with the names provided by TNA and have the code extract according to their formatting as well as the old structure. All old names would not have / present. All new ones would.

NA use HO107xxx and HO107xxxx for 1841 and 1851
FreeCEN to upload to the Database we only use 8 digits so with some 1841
only having 3 digits for the PIECE number for all the PIECE Numbers we
improvise as follows.
FreeCEN for uploading to the DATABASE
For the 1841  3 digit numbers we use HO107xxx
for the 4 digit numbers for the piece number we use  HO41xxxx
1851 we use HO51xxxx
Then the NA use RG /xxxx  for all 1861 to 1901 (note the space before the
slash)
We use the following to make sure they are all in line with the rest and
have 8 digits.
1861 RG09xxxx
1871  RG10xxxx
1881  RG11xxxx
1891  RG12xxxx
1901  RG13xxxx
1911  different set up all together as each household is a separate page.
Geoff has been looking into that. And knows more about the numbering.
Not sure where you get the RS though, but Scotland use it  but it changes
when it goes online, but  England & Wales use as above.
On Wed, 29 Apr 2020 at 00:43, Kirk Dawson<EMAIL_ADDRESS>wrote:

I have just realized that we adjust not only civil parish and census
district names to fit within 20 characters (A constraint we are removing)
But we actually change the piece naming used by TNA in our naming of vld
files and in much of our documentation. rg RS 9/1 .... RS 9/1889
We drop the space after the RS , we insert a leading 0 before the 9, we
drop the / after the series and before the numeric ie RS091889
I gather this was also to accommodate an 8 character limitation.
We are going to run into a problem with 1911 and likely 1921 there there
are more than 9999 pieces ie the series runs from RG14/1 to RG14/19412
The initial design of CSVProc was it uses the file name to identify the
piece. My initial coding had been around an 8 character field (I knew not
better)
Is now the time to stop messing with the names provided by TNA and have
the code extract according to their formatting as well as the old
structure. All old names would not have / present. All new ones would.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FreeUKGen/FreeCENMigration/issues/881, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIL3VUWPMB3Q4SFIZ6PL6DRO5SZLANCNFSM4MTIJ3TA
.

TY @FreecenBren
So you agree we manipulate the the File name  (or piece name) used by TNA  in order to met the FreeCEN1 requirement for an 8 character name. We do some heavy duty changes to 1841/51 because they were both in HO 107
The question I raised was since FreeCEN2 does not care about the length of a file name should we replace the structure and stay closer to the original.
There would be no requirement to change existing files
But do we design one that remains closer to TNA. There would still have to be changes as a file name could not contain the / and spaces are undesirable.
Likely more important issues

@geoffj-FUG @FreecenBren @rhodamackenzie
We need to establish a file naming convention for CSV file uploads to CEN2. These files will not be processed into CEN1 so CEN1 limitations and structure do not need to be imposed.
The piece number field is now a string NOT an integer
The naming convention needs to support all countries including Ireland.
The naming convention needs to support multiple files for a specific piece; lets get away from massive files where there is just 1 file for a piece.
Naming should be as close to TNA naming but supporting Scotland and Ireland.
Their structure is basically series/number. We cannot use that directly as the / is illegal in a file name. We could use series_number_part eg HO 107_989_1 or HO107-989-a ie use the hyphen or have the system accept either _ or - as the separator.
If we adopt that should we adopt that in our online numbering of a piece  ie RS10-1898 rather than RS 10/1898 as it is at that time

Kirk et al
I am comfortable with the 3 part underscored solution.
England and Wales would be for instance RG10_1234_a (1871)
Or HO107_1234_a (1851)
OR HO107_234_a (1841)
Ireland would be ANT01_123_a (1901)
ANT11_123_a (1911)
Though I doubt the a, b etc will be used as the Coordinator can break up the DEDs into Townlans=ds which are themselves small.
Now Scotland has me completely miffed. They had a numbering system. Now they have a table which converts pieces from their old numbering system to their new numbering system! Any logic that might be applied has eluded me as they have not explained their system the way that Ireland has.
There are 2 options:
Brenda or Rhoda understand the system and can provide advice
We adopt our own numbering system as Scotland Archives seem to be playing silly b’s with it.
Looking at what is online on FreeCEN for ABD
Aberdeenshire – 1841 (Scotland)
Piece
Place
Comprising
Status
Remarks
168/a
Aberdeen
East
Online
Aberdeen
Greyfriars
Online
Aberdeen
North
Online
Aberdeen
South
Online
Aberdeen
St. Clements
Online
Aberdeen
West
Online
168/b
Old Machar
Bon Accord
Online
Old Machar
Gilcomston
Online
Old Machar
Holburn
Online
So, We could invent ABD41_168_a
This would conform to the Ireland solution and keep the existing FreeCEN references aligned with what Scotland Archives used to have. It would also be transparent as to which year and county 168_8 belongs to. That may not be so in 10 years time if the conversion table has disappeared.
Regards
Geoff
From: Kirk Dawson<EMAIL_ADDRESS>Sent: Thursday, 18 June 2020 2:20 AM
To: FreeUKGen/FreeCENMigration<EMAIL_ADDRESS>Cc: geoffj-FUG<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [FreeUKGen/FreeCENMigration] File naming in CEN2 (#881)
@geoffj-FUG https://github.com/geoffj-FUG  @FreecenBren https://github.com/FreecenBren  @rhodamackenzie https://github.com/rhodamackenzie
We need to establish a file naming convention for CSV file uploads to CEN2. These files will not be processed into CEN1 so CEN1 limitations and structure do not need to be imposed.
The piece number field is now a string NOT an integer
The naming convention needs to support all countries including Ireland.
The naming convention needs to support multiple files for a specific piece; lets get away from massive files where there is just 1 file for a piece.
Naming should be as close to TNA naming but supporting Scotland and Ireland.
Their structure is basically series/number. We cannot use that directly as the / is illegal in a file name. We could use series_number_part eg HO 107_989_1 or HO107-989-a ie use the hyphen or have the system accept either _ or - as the separator.
If we adopt that should we adopt that in our online numbering of a piece ie RS10-1898 rather than RS 10/1898 as it is at that time
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/881#issuecomment-645452617 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFOJMUPHSCCHV5XHT5DRXDUL5ANCNFSM4MTIJ3TA .  https://github.com/notifications/beacon/AKCPIFOB2UALK45D4REVXQLRXDUL5A5CNFSM4MTIJ3TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZ4NGSI.gif

@geoffj-FUG since we have no material for Scotland the question is academic for CSV files which are the only ones that will use this system
Will proceed to amend the ingest code for TNA to follow the proposed sructure

Revised file naming implemented and deployed to test3

Closing - Ireland is a separate parms story.


docs: add the description of versioning rule

Description

Added the description of versioning rule.
Types of changes

[ ] Bug fix (changes which fixes an issue)
[ ] New feature (changes which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] ETC (build, ci, docs, perf, refactor, style, test)

Checklist

[x] I followed the contributing guidelines.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] The PR title and commits are followed conventional commit form.

@zemyblue
In cosmwasm, CHANGELOG is generated automatically and does not need to be added.

@zemyblue
In cosmwasm, CHANGELOG is generated automatically and does not need to be added.

If then, what's this?
https://github.com/Finschia/cosmwasm/blob/main/CHANGELOG.md
These changes are written automatically?

@zemyblue
This is used to create the CHANGELOG.
However, it does not seem to have been updated since 0.16.3-0.5.1, so a separate PR with an updated CHANGELOG is created.