BadConnection("Unable to open the database file")' when changing database link

I'm using the flatpak version. I linked the database file with
ln -s /home/user/projectpad/projectpad.db /home/user/.var/app/com.github.emmanueltouzery.projectpad/data/projectpad/projectpad.db
And it works the database is saved. But if I want to change the database file location:
$ rm /home/user/.var/app/com.github.emmanueltouzery.projectpad/data/projectpad/projectpad.db
$ ln -s /home/user/new_location/projectpad/projectpad.db /home/user/.var/app/com.github.emmanueltouzery.projectpad/data/projectpad/projectpad.db
projectpad.db is the same database file as before only on a new location.
Then when I try starting projectpad again I receive the error and projectpad closes itself:
$ flatpak run com.github.emmanueltouzery.projectpad thread '<unnamed>' panicked at 'called Result::unwrap()on anErrvalue: BadConnection("Unable to open the database file")', projectpad/src/sql_thread.rs:35:92 note: run withRUST_BACKTRACE=1 environment variable to display a backtrace
How can I change the projectpad database location?

Hi! yes i think it's what I mention in the readme, I believe it's flatpak which prevents the application from accessing  the disk in locations it's not supposed to. The flatpak is in fact limited such that it cannot access your disk except in its own data folder and through file open/save dialogs, for security.
I mention this at the very bottom of the README:

if you use flatpak, you must grant the application access to the folder where the DB is stored, through a command like flatpak override com.github.emmanueltouzery.projectpad --filesystem=~/Dropbox/projectpad/ --user.

So in your case that would be  flatpak override com.github.emmanueltouzery.projectpad --filesystem=/home/user/new_location/projectpad/ --user.
Can you try that and let me know whether that works?

It worked! I forgot to execute that command. thanks. closing


Case sensitivity probably breaks everything

Guessing if your query doesn't match up exactly with your props everything will break.

Yeah, I can confirm this breaks


plz update this..

plz update this..this doesn't work anymore..

He wrote on his site that he stopped working on it. Try Android application called SyncMyTracks, it works great.

Sorry but i don't have time to update this to work with nike's new API's.


Keep cmd open after running .exe

My .exe closes after finishing its work on windows 10. I would like it to stay open so that the user can read the text output. Is there a way to achieve this by modifying the main script JS file?
Temporarily solved it by wrapping .exe file in another .bat file, but hoped that there was a cleaner, 1-file solution

You can edit it in the code by including an iostream. Now you can atleast see the message.
const readline = `require('readline');

const rl = readline.createInterface({`
    input: process.stdin,
    output: process.stdout
});

console.log("Hello World!")


Added gitignore to gitignore

Thanks for contributing to Wagtail! 🎉
Before submitting, please review the contributor guidelines http://docs.wagtail.io/en/latest/contributing/index.html and check the following:

Do the tests still pass? (http://docs.wagtail.io/en/latest/contributing/developing.html#testing)
Does the code comply with the style guide? (Run make lint from the Wagtail root)
For Python changes: Have you added tests to cover the new/fixed behaviour?
For front-end changes: Did you test on all of Wagtail’s supported browsers? Please list the exact versions you tested.
For new features: Has the documentation been updated accordingly?

Hi @sambbhavgarg - thanks for the contribution. However, putting gitignore in gitignore is not standard practice, and not something we'd consider doing without a good reason.


FR: Better VM metadata support

Describe the feature request
For hybrid / VM scenarios, we need to ensure that the environmental metadata supplied to the proxies contains all of the relevant information (on par with k8s environments). This metadata should be descriptive enough to provide identifying information for the workload. For example, we should be able to identify the proper monitored resource in Stackdriver for gce instances or generic nodes.
For non-GCE environments, this likely requires also adding new environmental plugins into the Pilot codebase.
Describe alternatives you've considered
None.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ X ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context
/cc @smawson

This should also include work to identify MIG, etc. Relevant GCE metadata labels:

instance_template
created_by


Recorded file name standard

Describe the feature
I propose to expand the number of parameters for saved files.
1 - the ability to add %s (unixtimestamp) to the parameter name, for example: path1-1698052221.mp4
2 - the ability to add a file serial number for the current day, for example: path1-1698052221-000.mp4; Every new day the serial number is reset to 000.

I agree, it would be great for me to save the file using %s (unixtimestamp) as the parameter name

Bumping for %s as parameter for filename


Dependency substitution is not applied correctly in cyclically included build

I'm currently in a situation where I'd like to have two Gradle builds. Let's call them library and sandbox. The builds are intertwined but I need the separation because sandbox should be worked on using a separate IDE instance.
My current setup looks roughly as follows (An MCVE is linked at the end of the issue):
<root>
|-- library
    |-- <...>
    |-- build.gradle.kts     <-- depends on sandbox in "test" configuration
|-- sandbox
    |-- <...>
    |-- build.gradle.kts     <-- depends on library in "api" configuration
    |-- settings.gradle.kts  <-- includeBuild("../") { dependencySubstitution { ... } }
|-- settings.gradle.kts      <-- includeBuild("sandbox")

dependencySubstitution declares a substitution for the library.
Expected Behavior

I'd expect this setup to work since there is no cycle between configurations (and Gradle does not complain about the cyclically included builds either).
Current Behavior

This works fine when running tasks for the sandbox build (e.g., by calling gradlew in the corresponding directory) but the substitution is not applied when running tasks for the library build.
For example, calling gradlew :library:build fails with:
FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':sandbox:compileJava'.
> Could not resolve all task dependencies for configuration ':sandbox:compileClasspath'.
   > Cannot resolve external dependency com.example:library:0.1.0 because no repositories are defined.
     Required by:
         project :sandbox

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

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

BUILD FAILED in 655ms

Steps to Reproduce

I have prepared an MCVE at https://github.com/TheMrMilchmann/MCVE/tree/gradle/23980-dependency-substitution-cyclic-build.

Either eliminate the need for dependency substitutions (always preferable imho) by properly configuring your projects with their coordinates, and it works perfectly fine.
Just set the group = com.example on both projects and remove the substitution blocks.
Or you can alternatively add
configurations.configureEach {
    resolutionStrategy.dependencySubstitution {
        substitute(module("com.example:library")).using(project(":library"))
    }
}

in your library/build.gradle.kts, then it also works.
The library build just doesn't know about the substitution you configured in the sandbox build.

Thank you for the quick response! A couple of comments:

Either eliminate the need for dependency substitutions

I agree but I'm not sure if this is possible given my unusual requirements.

Just set the group = com.example on both projects and remove the substitution blocks.

This does seem to do trick. Interesting.

Or you can alternatively add
configurations.configureEach {
    resolutionStrategy.dependencySubstitution {
        substitute(module("com.example:library")).using(project(":library"))
    }
}

in your library/build.gradle.kts, then it also works.

Did you also test this? I'd prefer this solution because the project names + group names do not match the GAV coordinates in my actual project. However, applying the change as you suggested does not actually seem to work.

Yes, I tested both suggestions and both worked

I'm aware that this is most definitely a configuration issue and not a Gradle issue at this point, but for completeness, I'd like to be sure. If I understood you correctly, the modification below should suffice to make it work.
diff --git a/library/build.gradle.kts b/library/build.gradle.kts
index 4e12663..82ad3e1 100644
--- a/library/build.gradle.kts
+++ b/library/build.gradle.kts
@@ -3,6 +3,12 @@ plugins {
     `maven-publish`
 }

+configurations.configureEach {
+    resolutionStrategy.dependencySubstitution {
+        substitute(module("com.example:library")).using(project(":library"))
+    }
+}
+
 dependencies {
     testImplementation("com.example:sandbox:0.1.0")
 }
\ No newline at end of file

However, even with that change gradlew :library:build still fails for the same reason as mentioned in the original description. Is there anything I'm missing here? (Updated MCVE)

Oh, I actually just checked library:dependencies where it was FAILED before. :-/

WIth the solution to not need dependency substitution I actually tested with library:build, there it worked

I'm aware that this is most definitely a configuration issue and not a Gradle issue at this point, ...

After investigating this a bit further, I'm not that confident anymore. For simplicitly, I addded some good, old println statements for debugging:
rootProject.name = "sandbox"

includeBuild("../") {
    dependencySubstitution {
        all { println("Substituting in sandbox: $requested") }

        substitute(module("com.example:library")).using(project(":library"))
    }
}

$ ~/sandbox> gradlew build
Substituting in sandbox: com.example:library:0.1.0
Substituting in sandbox: com.example:library:0.1.0
Substituting in sandbox: com.example:library:0.1.0

However, when calling gradlew :library:build in the repository root, nothing is printed and Gradle fails to resolve com.example:library:0.1.0. I guess the substitution is not correctly picked up in this case after all.

Sorry for the late reply.
Thank you for providing a valid report.
The issue is in the backlog of the relevant team, but the existence of a workaround makes it non-critical, so it might take a while before a fix is made.

A workaround to solve this is to avoid dependency substitution in the included build declaration by making sure project coordinates match the dependency coordinates.

Dependency substitutions are not applied transitively, so each project or build needs to have them defined.
It's much easier to have the project's coordinates (group/name) match the coordinates used by external projects, which removes the need to define substitutions.
I think error messages or documentation could be better here, but we're going to close this as working-as-designed.

Let's reopen and re-qualify as an error improvement.

As it stands we have no plans to improve the error reporting for this. The complexity of detecting this situation is too great for us to consider implanting it, especially given our current resources


python312Packages.opower: 0.8.6 -> 0.8.7

Diff: https://github.com/tronikos/opower/compare/refs/tags/v0.8.6...v0.8.7
Changelog: https://github.com/tronikos/opower/releases/tag/v0.8.7

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 369342

x86_64-linux

:white_check_mark: 5 packages built:

home-assistant-component-tests.opower
python312Packages.opower
python312Packages.opower.dist
python313Packages.opower
python313Packages.opower.dist


Make Out-Default -Transcript more robust in how it handle TranscribeOnly state

Addresses #3390

@lzybkr Should associated issue (#3390) be closed as well?

Indeed, I forget to do that pretty much every time I merge, you'd think I could remember by now.


Update etiquette.md

Mainly testing this out.

Perhaps it may be good to relax a bit the etiquette, and instead emphasise more that it has to be used responsibly, e.g. with some do's and don'ts? Here for reference the recommendations at NSC:
https://www.nsc.liu.se/support/running-applications

Hi Pedro,
yes absolutely, this is just an initial draft with a few important points.
Feel free to edit! :)
I may be a little biased since I had to personally call two people last
week who were clogging up the login node on Garpur with excessive amounts
of python jobs :P
All the best,
Elvar
On Fri, 21 May 2021 at 00:49, Pedro Costa @.***> wrote:

Perhaps it may be good to relax a bit the etiquette, and instead emphasise
more that it has to be used responsibly, e.g. with some do's and don'ts?
Here for reference the recommendations at NSC:
https://www.nsc.liu.se/support/running-applications
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/IRHPC/irhpc.github.io/pull/7#issuecomment-845500181,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADVKMDAURNSPIQYUOD5ONFDTOV7WNANCNFSM45HCXQ6Q
.

Yes, I thought so, I just wanted to leave the note there for future reference :).
I'm sorry you had to go so far. I guess it is really important to make it clear in the new docs that this is unacceptable.


Persistent paths not mounted at boot

What steps did you take and what happened:
The issue raised on a 50 nodes deployment on the CI. There was one node that did not join the cluster. This happened because the immutable-rootfs layout failed to properly mount the persistent partition and all of the state RW paths depending on it. Once booted the bootstrap.sh script failed to install RKE2 as /opt was not writable.
What did you expect to happen:
The node boostraps RKE2 and joins the cluster. Probably we should just fail at boot time, immutable-rootfs simply omitted to create the persistent mountpoints and continued to boot normally, probably better to include all them in /etc/fstab and let systemd fail on later stages if the underlaying devices and mountpoints do not appear.
Worth to mention that on boot /usr/local got mounted based on /etc/fstab contents after switching root when systemd took control of the new root /.
Anything else you would like to add:
Journalctl logs of the initrd boot stage contain most of the relevant info:
Mar 13 09:14:12 localhost elemental[784]: INFO[2023-03-13T09:14:12Z] Executing /system/oem/01_elemental-rootfs.yaml
Mar 13 09:14:12 localhost elemental[784]: INFO[2023-03-13T09:14:12Z] Applying 'Elemental Rootfs Layout Settings' for stage 'rootfs.after'. Total stages: 1
Mar 13 09:14:12 localhost elemental[784]: INFO[2023-03-13T09:14:12Z] Processing stage step 'Grow persistent'. ( commands: 0, files: 0, ... )
Mar 13 09:14:12 localhost elemental[784]: INFO[2023-03-13T09:14:12Z] Extending last partition up to 0 MiB
Mar 13 09:14:13 localhost systemd-udevd[601]: sda5: Failed to add device '/dev/sda5' to watch: Operation not permitted
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Stage 'rootfs.after'. Defined stages: 1. Errors: false
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/04_accounting.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/05_motd_and_autologin.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/05_network.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/06_recovery.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/07_live.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/08_boot_assessment.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/09_services.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/99_elemental-register.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /system/oem/99_elemental_system_agent.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /oem/90_custom.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /oem/91_custom.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing /oem/registration/config.yaml
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Done executing stage 'rootfs.after'
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Running stage: rootfs.before
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing BOOT_IMAGE=(loop0)/boot/vmlinuz console=tty1 console=ttyS0 root=LABEL=COS_STATE cos-img/filename=/cOS/active.img panic=5 rd.neednet=0 rd.cos.oemlabel=COS_OEM fsck.>
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Done executing stage 'rootfs.before'
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Running stage: rootfs
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing BOOT_IMAGE=(loop0)/boot/vmlinuz console=tty1 console=ttyS0 root=LABEL=COS_STATE cos-img/filename=/cOS/active.img panic=5 rd.neednet=0 rd.cos.oemlabel=COS_OEM fsck.>
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Done executing stage 'rootfs'
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Running stage: rootfs.after
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Executing BOOT_IMAGE=(loop0)/boot/vmlinuz console=tty1 console=ttyS0 root=LABEL=COS_STATE cos-img/filename=/cOS/active.img panic=5 rd.neednet=0 rd.cos.oemlabel=COS_OEM fsck.>
Mar 13 09:14:13 localhost elemental[784]: INFO[2023-03-13T09:14:13Z] Done executing stage 'rootfs.after'
Mar 13 09:14:13 localhost systemd[1]: Finished cOS system early rootfs setup.
Mar 13 09:14:13 localhost systemd[1]: Starting cOS system immutable rootfs mounts...
Mar 13 09:14:13 localhost systemd[1]: Unmounting /oem...
Mar 13 09:14:13 localhost systemd[1]: initrd-parse-etc.service: Deactivated successfully.
Mar 13 09:14:13 localhost systemd[1]: Finished Reload Configuration from the Real Root.
Mar 13 09:14:13 localhost systemd[1]: Starting dracut mount hook...
Mar 13 09:14:13 localhost systemd[1]: oem.mount: Deactivated successfully.
Mar 13 09:14:13 localhost systemd[1]: Unmounted /oem.
Mar 13 09:14:13 localhost systemd[1]: Finished dracut mount hook.
Mar 13 09:14:13 localhost kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 13 09:14:13 localhost systemd-fsck[978]: Failed to stat /dev/disk/by-label/COS_PERSISTENT: No such file or directory
Mar 13 09:14:13 localhost cos-mount-layout[979]: Warning: /dev/disk/by-label/COS_PERSISTENT already mounted or device not found
Mar 13 09:14:13 localhost cos-mount-layout[989]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[987]: failed creating '/sysroot/etc/systemd' or '/sysroot/usr/local/.state/etc-systemd.bind'. Ignoring '/sysroot/etc/systemd' mount
Mar 13 09:14:13 localhost cos-mount-layout[992]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[990]: failed creating '/sysroot/etc/rancher' or '/sysroot/usr/local/.state/etc-rancher.bind'. Ignoring '/sysroot/etc/rancher' mount
Mar 13 09:14:13 localhost cos-mount-layout[995]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[993]: failed creating '/sysroot/etc/ssh' or '/sysroot/usr/local/.state/etc-ssh.bind'. Ignoring '/sysroot/etc/ssh' mount
Mar 13 09:14:13 localhost cos-mount-layout[998]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[996]: failed creating '/sysroot/etc/iscsi' or '/sysroot/usr/local/.state/etc-iscsi.bind'. Ignoring '/sysroot/etc/iscsi' mount
Mar 13 09:14:13 localhost cos-mount-layout[1001]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[999]: failed creating '/sysroot/etc/cni' or '/sysroot/usr/local/.state/etc-cni.bind'. Ignoring '/sysroot/etc/cni' mount
Mar 13 09:14:13 localhost cos-mount-layout[1004]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1002]: failed creating '/sysroot/home' or '/sysroot/usr/local/.state/home.bind'. Ignoring '/sysroot/home' mount
Mar 13 09:14:13 localhost cos-mount-layout[1007]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1005]: failed creating '/sysroot/opt' or '/sysroot/usr/local/.state/opt.bind'. Ignoring '/sysroot/opt' mount
Mar 13 09:14:13 localhost cos-mount-layout[1010]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1008]: failed creating '/sysroot/root' or '/sysroot/usr/local/.state/root.bind'. Ignoring '/sysroot/root' mount
Mar 13 09:14:13 localhost cos-mount-layout[1013]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1011]: failed creating '/sysroot/usr/libexec' or '/sysroot/usr/local/.state/usr-libexec.bind'. Ignoring '/sysroot/usr/libexec' mount
Mar 13 09:14:13 localhost cos-mount-layout[1016]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1014]: failed creating '/sysroot/var/log' or '/sysroot/usr/local/.state/var-log.bind'. Ignoring '/sysroot/var/log' mount
Mar 13 09:14:13 localhost cos-mount-layout[1019]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1017]: failed creating '/sysroot/var/lib/elemental' or '/sysroot/usr/local/.state/var-lib-elemental.bind'. Ignoring '/sysroot/var/lib/elemental' mount
Mar 13 09:14:13 localhost cos-mount-layout[1022]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1020]: failed creating '/sysroot/var/lib/rancher' or '/sysroot/usr/local/.state/var-lib-rancher.bind'. Ignoring '/sysroot/var/lib/rancher' mount
Mar 13 09:14:13 localhost cos-mount-layout[1025]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1023]: failed creating '/sysroot/var/lib/kubelet' or '/sysroot/usr/local/.state/var-lib-kubelet.bind'. Ignoring '/sysroot/var/lib/kubelet' mount
Mar 13 09:14:13 localhost cos-mount-layout[1028]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1026]: failed creating '/sysroot/var/lib/NetworkManager' or '/sysroot/usr/local/.state/var-lib-NetworkManager.bind'. Ignoring '/sysroot/var/lib/NetworkManager' mount
Mar 13 09:14:13 localhost cos-mount-layout[1031]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1029]: failed creating '/sysroot/var/lib/longhorn' or '/sysroot/usr/local/.state/var-lib-longhorn.bind'. Ignoring '/sysroot/var/lib/longhorn' mount
Mar 13 09:14:13 localhost cos-mount-layout[1034]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1032]: failed creating '/sysroot/var/lib/cni' or '/sysroot/usr/local/.state/var-lib-cni.bind'. Ignoring '/sysroot/var/lib/cni' mount
Mar 13 09:14:13 localhost cos-mount-layout[1037]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 13 09:14:13 localhost cos-mount-layout[1035]: failed creating '/sysroot/var/lib/calico' or '/sysroot/usr/local/.state/var-lib-calico.bind'. Ignoring '/sysroot/var/lib/calico' mount
Mar 13 09:14:13 localhost systemd[1]: Finished cOS system immutable rootfs mounts.
Mar 13 09:14:13 localhost systemd[1]: Reached target Initrd File Systems.

Environment:
$ rpm -qa | grep elemental
elemental-register-1.1.3+git20230310.3f0e357-150400.111.1.x86_64
elemental-support-1.1.3+git20230310.3f0e357-150400.111.1.x86_64
elemental-system-agent-0.3.1-150400.2.1.x86_64
elemental-updater-1.1.1+git20230311.9525ad7-150400.208.1.noarch
elemental-cli-0.2.1+git20230308.cb8b7d0-150400.70.1.x86_64
elemental-toolkit-0.10.1+git20230303.3b57d5d-150400.91.1.noarch
elemental-1.1.1+git20230311.9525ad7-150400.208.1.noarch
...

Elemental release version (use cat /etc/os-release): 1.1.1+git20230311.9525ad7
Rancher version:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:

 systemd-udevd[601]: sda5: Failed to add device '/dev/sda5' to watch: Operation not permitted

What's the root cause of this failure ?

I have no clue... 🤷🏽♂ It happened in only one node out of 50, so I believe it has to be a race condition somewhere. We can attempt to be more strict on mounting all the special paths at boot and wait for the devices if they are not there yet.

This is also strange
Extending last partition up to 0 MiB

Yes, the message here is misleading. There is a the expansion of the COS_PERSISTENT partition enabled by default (which I doubt is actually valuable for our current workflow). If size is set to 0 it expands to all available size, we did not properly cover this case in logging. Also, it did not expand as the partition already makes use of all available space.
I have been wondering about if the attempt of expanding the partition could cause some sort of collision with udev at boot. So wondering if at the time parted accessed the partition (even without applying any change) that could cause some glitch with udev daemon.

I had the issue in a test: rancher-system-agent service failed because binary is not found in /opt as this filesystem is in read-only state.
I have this in /etc/fstab:
/dev/loop0 / auto ro 0 0
tmpfs /run/overlay tmpfs defaults,size=25% 0 0
overlay /etc overlay defaults,lowerdir=/etc,upperdir=/run/overlay/etc.overlay/upper,workdir=/run/overlay/etc.overlay/work,x-systemd.requires-mounts-for=/run/overlay
/dev/disk/by-label/COS_OEM /oem auto defaults 0 0
overlay /srv overlay defaults,lowerdir=/srv,upperdir=/run/overlay/srv.overlay/upper,workdir=/run/overlay/srv.overlay/work,x-systemd.requires-mounts-for=/run/overlay
/dev/disk/by-label/COS_PERSISTENT /usr/local auto defaults 0 0
overlay /var overlay defaults,lowerdir=/var,upperdir=/run/overlay/var.overlay/upper,workdir=/run/overlay/var.overlay/work,x-systemd.requires-mounts-for=/run/overlay

Elemental packages:
# rpm -qa | grep elemental
elemental-dracut-config-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-grub-config-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-immutable-rootfs-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-register-1.1.4+git20230315.63c99d7-150400.115.1.x86_64
elemental-support-1.1.4+git20230315.63c99d7-150400.115.1.x86_64
elemental-system-agent-0.3.1-150400.2.2.x86_64
elemental-updater-1.1.2+git20230315.f7048f1-150400.212.1.noarch
elemental-cli-0.2.2+git20230310.c214054-150400.72.2.x86_64
elemental-init-setup-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-init-services-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-init-recovery-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-init-network-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-init-live-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-init-boot-assessment-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-init-config-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-toolkit-0.10.3+git20230315.63e8c41-150400.94.1.noarch
elemental-1.1.2+git20230315.f7048f1-150400.212.1.noarch

Here the full journalctl log:
boot.log.gz

This looks like a missing udevadm settle 🤔
Mar 15 21:15:51 localhost elemental[784]: INFO[2023-03-15T21:15:51Z] Extending last partition up to 0 MiB
Mar 15 21:15:51 localhost systemd-udevd[617]: sda5: Failed to add device '/dev/sda5' to watch: Operation not permitted

And here's the first error about a read-only filesystem
Mar 15 21:15:52 localhost elemental[1039]: INFO[2023-03-15T21:15:52Z] Executing /system/oem/01_elemental-rootfs.yaml
Mar 15 21:15:52 localhost elemental[1039]: INFO[2023-03-15T21:15:52Z] Applying 'Elemental Rootfs Layout Settings' for stage 'initramfs'. Total stages: 3
Mar 15 21:15:52 localhost elemental[1039]: INFO[2023-03-15T21:15:52Z] Processing stage step ''. ( commands: 1, files: 0, ... )
Mar 15 21:15:52 localhost elemental[1039]: INFO[2023-03-15T21:15:52Z] Command output: mkdir: cannot create directory ‘/usr/local/etc’: Read-only file system
Mar 15 21:15:52 localhost elemental[1039]: sh: line 2: /usr/local/etc/hostname: No such file or directory

@ldevulder is that Dev, Staging or Stable ?

Mar 15 21:15:51 localhost systemd-fsck[978]: Failed to stat /dev/disk/by-label/COS_PERSISTENT: No such file or directory

😮

In rancher/elemental-toolkit#1743 instead of explicitly erroring out in case there is some error to prepare or mount a mountpoint and just changed to logic to not ignore it an still include the mountpoint in fstab. The idea is that we keep creating the fstab as requested but do not fail if we can't mount everything, systemd will later on fail if it can't manage to mount all fstab entries.

Moved to needs review as verifying the fix requires some tests running big clusters (the issue turned to be more or less consistent with clusters with more the 100 nodes).
To fully verify the fix we should see in some node boot logs that there was the following udev error message:
systemd-udevd[601]: sda5: Failed to add device '/dev/sda5' to watch: Operation not permitted

and despite this, the node successfully booted and joined the cluster. I guess that means parsing the boot logs of every single node.

Apparently the fix was not enough... 😞 looks like there might be some sort of issue with udev. With the logs of a failed node including the fix we noticed a slightly different behavior. The Operation not permitted on device /dev/sda5 was not there, however cos-mount-layout.sh still failed properly prepare the layout.
Mar 20 10:23:05 localhost systemd[1]: Starting cOS system immutable rootfs mounts...
Mar 20 10:23:05 localhost systemd[1]: Unmounting /oem...
Mar 20 10:23:05 localhost systemd[1]: initrd-parse-etc.service: Deactivated successfully.
Mar 20 10:23:05 localhost systemd[1]: Finished Reload Configuration from the Real Root.
Mar 20 10:23:05 localhost systemd[1]: Starting dracut mount hook...
Mar 20 10:23:05 localhost systemd[1]: oem.mount: Deactivated successfully.
Mar 20 10:23:05 localhost systemd[1]: Unmounted /oem.
Mar 20 10:23:05 localhost systemd[1]: Finished dracut mount hook.
Mar 20 10:23:05 localhost kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
Mar 20 10:24:06 localhost systemd-fsck[1096]: Failed to stat /dev/disk/by-label/COS_PERSISTENT: No such file or directory
Mar 20 10:24:06 localhost cos-mount-layout[1097]: Warning: /dev/disk/by-label/COS_PERSISTENT already mounted or device not found
Mar 20 10:24:06 localhost cos-mount-layout[1107]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1105]: failed creating '/sysroot/etc/systemd' or '/sysroot/usr/local/.state/etc-systemd.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1110]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1108]: failed creating '/sysroot/etc/rancher' or '/sysroot/usr/local/.state/etc-rancher.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1113]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1111]: failed creating '/sysroot/etc/ssh' or '/sysroot/usr/local/.state/etc-ssh.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1116]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1114]: failed creating '/sysroot/etc/iscsi' or '/sysroot/usr/local/.state/etc-iscsi.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1119]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1117]: failed creating '/sysroot/etc/cni' or '/sysroot/usr/local/.state/etc-cni.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1122]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1120]: failed creating '/sysroot/home' or '/sysroot/usr/local/.state/home.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1125]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1123]: failed creating '/sysroot/opt' or '/sysroot/usr/local/.state/opt.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1128]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1126]: failed creating '/sysroot/root' or '/sysroot/usr/local/.state/root.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1131]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1129]: failed creating '/sysroot/usr/libexec' or '/sysroot/usr/local/.state/usr-libexec.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1134]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1132]: failed creating '/sysroot/var/log' or '/sysroot/usr/local/.state/var-log.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1137]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1135]: failed creating '/sysroot/var/lib/elemental' or '/sysroot/usr/local/.state/var-lib-elemental.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1140]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1138]: failed creating '/sysroot/var/lib/rancher' or '/sysroot/usr/local/.state/var-lib-rancher.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1143]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1141]: failed creating '/sysroot/var/lib/kubelet' or '/sysroot/usr/local/.state/var-lib-kubelet.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1146]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1144]: failed creating '/sysroot/var/lib/NetworkManager' or '/sysroot/usr/local/.state/var-lib-NetworkManager.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1149]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1147]: failed creating '/sysroot/var/lib/longhorn' or '/sysroot/usr/local/.state/var-lib-longhorn.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1152]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1150]: failed creating '/sysroot/var/lib/cni' or '/sysroot/usr/local/.state/var-lib-cni.bind'
Mar 20 10:24:06 localhost cos-mount-layout[1155]: mkdir: cannot create directory '/sysroot/usr/local/.state': Read-only file system
Mar 20 10:24:06 localhost cos-mount-layout[1153]: failed creating '/sysroot/var/lib/calico' or '/sysroot/usr/local/.state/var-lib-calico.bind'
Mar 20 10:24:06 localhost systemd[1]: Finished cOS system immutable rootfs mounts.

See the logs cos-mount-layout.sh does not succeed to prepare the mountpoints due to the missing device /dev/disk/by-label/COS_PERSISTENT, it even waits for it during 1min having a udevadm settle call on every second. The interesting fact is that later on when switching root the device is found properly and all mountpoints are created according to the generated /etc/fstab. Rebooting fixes the issue as before.

Time to raise a kernel/systemd bug via Bugzilla ?! 🤔

We already had a couple of successful big deployments with 150 nodes and more. Closing as fixed, both successful runs were including https://github.com/rancher/elemental-toolkit/pull/1744


[IA] More shortcodes for exporter pages

Related to https://github.com/open-telemetry/opentelemetry.io/discussions/3859, this PR heavily applies shortcodes to deduplicate content across exporter pages (currently java, python, JS)
@open-telemetry/docs-approvers PTAL!

Is there a reason why this is a draft?

Is there a reason why this is a draft?

I didn't want to trigger all the maintainers yet. Get your (docs) feedback first


Question:  ScrollSpy target specific navbar (2.0)

Is there anyway to have scrollspy add the active class to a specific navbar?
I have a dropdown that contains the same anchors but i do not want scrollspy to highlight the dropdown.
Thanks.

yep you can target the nav in 2.0 - This is done in the scroll-spy demo if you check it out

Hi,
So i am still having problems with the scrollspy js.
What do you think the issue is?
here is my code (slimmed down)
Body Markup

NavBar Markup

	    Ideate Explorer

Introduction

What is it?

Features

Demos

Free Trial

admin

			Dashboard

admin's Profile

Site Dashboard

Log Off

Target Markup

Anchor!!

Javascript
$("#inner-nav").scrollspy();

could you create a jsfiddle - and i'll help you get it working, thanks!

Here is a fiddle for you: http://jsfiddle.net/LkjxC/34/embedded/result/
The idea behind this is that this is for a network of sites and the Network menu is loaded as a static navbar and when the window is scrolled past the inner navigation it becomes fixed.

I was having the same problem, I just change the .nav for ul and now works fine (see below):
In line 35 change this:

For this:


Crash when trying to construct a dataframe from an Excel range containing dates

Excel dates get converted into pywintypes.TimeType when using pywin32, which causes pandas to crash.

Fixed in 9f2d236902b586214717f54a7733b73d941095ea


Compatibility Smartlink SI D

Is it also possible to use an Acti 9 Smartlink SI D gateway?
I saw in another topic that there was a possibility for a Smartlink SI B.
I certainly cannot add these automatically and manually at the moment.

These ones? https://www.se.com/uk/en/product-range/64482-acti9-smartlink-si-d/44105740929-gateways
Yeah they're supported. Are you seeing any errors?

Yes, this is it, it is an old type, not what is available now, it does have the latest firmware version (V2.4.6)
It does not work either automatically or manually.
I can find the errors below in the "home assistant.log"
Are there any places I should look?
2024-01-30 18:07:20.161 WARNING (MainThread) [homeassistant.util.async_] Detected blocking call to sleep inside the event loop by custom integration 'powertag_gateway' at custom_components/powertag_gateway/soap_communication.py, line 42: services = wsd.searchServices(types=[QName(NAMESPACE_SCHNEIDER, LOCAL_NAME_GATEWAY_SERVER)]), please create a bug report at https://github.com/Breina/PowerTagGateway/issues
2024-01-30 18:07:20.286 WARNING (Thread-3) [daemon] could not find handler for: _handle_probe
2024-01-30 18:35:26.006 ERROR (MainThread) [pymodbus.logging] Connection to (<IP_ADDRESS>, 502) failed: [Errno 111] Connection refused
2024-01-30 18:35:26.009 ERROR (MainThread) [pymodbus.logging] Connection to (<IP_ADDRESS>, 502) failed: [Errno 111] Connection refused
2024-01-30 18:37:58.131 WARNING (MainThread) [homeassistant.components.modbus.modbus] modbus hub1 communication closed

Ah I see.
Can you check that your web interface has this configured as such?

We should be able to get more logs through HomeAssistant through Settings > System > Logs, then search for powertag_gateway and click 'Load full logs', for example:

Please send me all of those logs, that should be more helpful.

Hi,
Below is the configuration of the Smartlink.

I get the following error when I want to connect to the Smarlink from HA.

Unfortunately, I cannot find much in the log you requested. see below.

Ah man I didn't log that error, that's on me. Sorry about that!
In custom_components/powertag_gateway/config_flow.py on line 169, please add logging.error(e) (indentation matters).

Then restart and check logs.
Is it possible that your Gateway is unreachable through the network?

I have adjusted the code.
The gateway is available from the network (located in the same subnet). I can also read this via a modbus client.
Below is the logging:

Also an image of the TAG configuration:

If this is accessible, it will take quite a while before I get the other error.

Yeah that's because we need to search for the synthesis table first;

So it's going through all 247 tables before throwing this error.
Can you please use your modbus client to check that this one exists on address 247? I use this first one to check we got the right one;

(reference: https://www.productinfo.schneider-electric.com/powertaglinkuserguide/powertag-link-user-guide/English/BM_PowerTag Link D User Manual_4af62430_T000501355.xml/$/TPC_SynthesisTableIdentificationREF_0000550649)

I think the "Smartlink SI D" doesn't have a synthesis table.
I can't find this anywhere in the manual. This is only stated in the manual of the "PowerTag Link Gateway".

Aaah ok! I get it. Yes.
Alright I know what to do, give me a moment to develop this for you.
Uploading manual for my own reference
DOCA0115EN-03.pdf

Please test v0.2.2-alpha: https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha

I see the option in the configuration menu, but when I click connect I immediately get an error.

Alright thanks for testing. Added more logs and made one thing more resilient. Please report back.

https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha2

Unfortunately, the error code is also still the same.

I think the code didn't quite update, it must print some logging before the crash;

Can you see these in custom_components/powertag_gateway/config_flow.py?

Yes, I see.

Ok thanks for clearing this up.
This one should log better;
https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha3

Much better!
Fixed https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha4

A step forward, but no tags are added.

Getting there :)
https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha5

Sorry... It seems the same.

No, this is better. We're getting further :)
Hold on

Btw 'Unknown' is I can't read the device's name. So it's going to be called Unknown. Please suggest a better default if you have one. :)

Getting close now
https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha6

Same fault

Not the same fault, we're actually making great progress!
I'll fix these tomorrow.

Ok, good night and thank you very much for checking this out!

This might well be the last fix we needed! :)
https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha7

Another step closer, I no longer receive any error messages. Only the power tags are not visible.
Do I need to configure anything else?

So since on your device, there's no way to determine how many devices are connected, I just have to try slave addresses starting from 150 until one fails. What's happening now is that it fails immediately.
Can you please try reading this table on slave id 150?

I can read this value via a modbus client, see below. FYI, this value also corresponds to the installed tag.

Alright thanks for confirming!
Found and fixed an off-by-one error. :)
https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha8

Thanks for the update.
The power tags are not added yet, but I do get the error below. Hopefully you can do something with this.

If it is too difficult or takes too much time, you can also say so and I will do it in a different way.
I really like that you are still trying to integrate this module!

In schneider_modbus.py on line 531, can you please change identifier = self.__read_int_16(0x792F, power_tag_index) into identifier = self.__read_int_16(0x7930, power_tag_index)? I believe I made a mistake.

If it is too difficult or takes too much time, you can also say so and I will do it in a different way.

Not at all! :) This is normal error driven development progress. I appreciate you testing so much for me. I would really like to support your device!

Good to hear!
I have adjusted the modbus address, I no longer get error messages, but the tags are not added either.

I haven't forgotten you, just have been busy the last few days.
The lack of errors is the bane of error-driven-development, so I'm scratching my head a bit. I can add a bunch of logs this evening to see what it's doing and where it fails.

Alright, please try this one: https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha9
And please fetch me all of its logs. Should be able to figure out where it goes wrong.

Attached is the requested log.

 I fixed this. Try it out! :)
https://github.com/Breina/PowerTagGateway/releases/tag/v0.2.2-alpha10

I recently started using Home Assistant.
So, little experience yet.
During installation the option “Perform automatic DWPS discovery” didn’t work.
But it was successful via manually entering the Host IP-Address.
No error messages during installation.
It seems I have a similar problem.: now devices or entities are found.
I would like to install the patch, but unfortunately, I have no knowledge how to do this.
After unzipping the alpha10-zip-file I recognize existing directory structure, but also new ones.
Can you please provide instructions on how to install this patch correctly?

Hi, welcome to the club! :) Thanks for being willing to test as well!
Yeah you have to specifically enable pre-releases: https://hacs.xyz/docs/faq/beta/. Then you can just update through HACS (restart afterwards).
You can also do it manually through downloading the release, copying the custom_components/powertag_gateway folder into the custom_components folder of your HomeAssistant. Then restart.

Thanks for explaining.
After installing patch alpha10, there is an additional option for selecting type of Gateway.
I’ve tried all 3.
When selecting:  Panel server

Fail to connect.

When selecting: PowerTag Link

The correct name of the PowerTagLink is displayed, but no devices or entities.

When selecting type of Gateway: Smartlink SI D

Unit A9XMWA20 is found
Name is Unknown
But : 1 device and 2 entities.

My configuration:

1 * Acti9 SmartLink
12 * A9MEM1560
1 * A9MEM1542
1 * A9MEM1541

Oh looks like we've made progress then! We found one of your powertags, but the sensors don't work properly yet. It's the smartlink one that you should pick, this is the one I'm setting up for this issue.
Can you please go to Settings > System > Logs and filter on powertag_gateway, then copy paste here what you see there.

As requested:

Ah man something is wrong with these logs. Missing a lot of crucial information.
How is your logged configured in your configuration yaml?
Here's an example:
logger:
  default: info
  logs:
    custom_components.powertag_gateway: debug

The code is very verbose in telling me what's going on;

Please don't apologise! I had to learn this at one point too. :)
I appreciate you taking your time to wrestle through this.
Please upgrade to v0.2.2-alpha11, restart, add the integration again and check your logs. Won't fix anything, but should be more verbose around where it's going wrong.

After installing patch:

Logging filtered by: powertag

I do not see mutch diference.
I’ve gone through the rest of the logging but don’t see any Powertag related info.

Is there anything else I can do or test to contribute?

Yeah sorry for not responding, I have a lot on my plate lately. I need to figure out why it's not logging everything properly. Don't have a power tag gateway to test it with at the moment. Let me get back to you for some more testing, I feel like we're close though.

Can you send me the full log file please? I'm thinking there's some part of the stack trace being filtered away.

For testing purposes I built an additional container with HA.
The result is a log that looks the same.
Alle other lines in the logging are not related to Powertag.
FYI, maybe not relevant:
HA runs on a Synology with Docker-container.

Also a busy agenda on my side, so I will probably respond a little later every now and then.
Great that you initiate follow-up.
I would like to contribute where possible, but giving access to my system is not an option.
If you send me instructions to carry out myself, I will send you the results.

Alright, no probs.
Can you give me the full logs? I feel like there's stuff in-between the filtered logs that I'm missing. You can remove what's not relevant for privacy.

Update installed on both HA containers.

home-assistant_2024-03-20T09-18-47.404Z.log
Attached logging is an export after installing version V0.2.2 and reboot HA.
This is the test environment logging.

Hi,
HA not founding A9MEM1590 R200 3P 3P+N. Can You help?
Logs:
2024-04-11 11:19:35.288 WARNING (MainThread) [root] Unknown product type: 17973.
Attached full debug logs
home-assistant_powertag_gateway_2024-04-11T10-50-59.589Z.log

Below the new logging:
2024-04-24 19:43:18.450 WARNING (SyncWorker_7) [homeassistant.loader] We found a custom integration powertag_gateway which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-24 19:43:27.636 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'input_boolean', 'radio_browser', 'homeassistant_alerts', 'default_config', 'ipp', 'persistent_notification', 'diagnostics', 'energyzero', 'homewizard', 'buienradar', 'assist_pipeline', 'file_upload', 'tts', 'history', 'trace', 'scene', 'homeassistant', 'input_number', 'image_upload', 'hacs', 'sun', 'spook', 'sonos', 'synology_dsm', 'media_source', 'config', 'conversation', 'onboarding', 'fritz', 'input_text', 'logbook', 'system_health', 'my', 'ifttt', 'stream', 'application_credentials', 'unifiprotect', 'met', 'evohome', 'zone', 'script', 'unifi', 'home_connect_alt', 'device_automation', 'counter', 'search', 'automation', 'lovelace', 'person', 'dlna_dms', 'tag', 'timer', 'input_select', 'mobile_app', 'analytics', 'map', 'dlna_dmr', 'energy', 'powertag_gateway', 'schedule', 'blueprint', 'input_button', 'input_datetime', 'dwains_dashboard', 'volkswagencarnet', 'select', 'stt', 'auth', 'hardware', 'wake_word', 'shelly', 'afvalinfo', 'ffmpeg', 'number', 'backup', 'notify', 'hikvision_next'}
2024-04-24 19:43:33.528 INFO (MainThread) [homeassistant.setup] Setting up powertag_gateway
2024-04-24 19:43:33.529 INFO (MainThread) [homeassistant.setup] Setup of domain powertag_gateway took 0.00 seconds
2024-04-24 19:43:33.535 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Connecting Modbus TCP to <IP_ADDRESS>:502
2024-04-24 19:43:49.844 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up powertag_gateway.binary_sensor
2024-04-24 19:43:49.861 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 31023, slave_id 150
2024-04-24 19:43:49.863 WARNING (MainThread) [custom_components.powertag_gateway.schneider_modbus] Could not read product type of device on slave ID 150: Exception Response(131, 3, GatewayNoResponse). Might be because there's device, or an actual error. Either way we're stopping the search.
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 533, in tag_product_type
identifier = self.__read_int_16(0x792F, power_tag_index)
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 783, in __read_int_16
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 753, in __read
2024-04-24 19:43:49.879 INFO (MainThread) [homeassistant.components.button] Setting up powertag_gateway.button
2024-04-24 19:43:49.886 INFO (MainThread) [custom_components.powertag_gateway.button] Setting up device index 1
2024-04-24 19:43:49.886 INFO (MainThread) [custom_components.powertag_gateway.button] Modbus address of that device is 1
2024-04-24 19:43:49.886 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 31023, slave_id 150
2024-04-24 19:43:49.890 WARNING (MainThread) [custom_components.powertag_gateway.schneider_modbus] Could not read product type of device on slave ID 150: Exception Response(131, 3, GatewayNoResponse). Might be because there's device, or an actual error. Either way we're stopping the search.
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 533, in tag_product_type
identifier = self.__read_int_16(0x792F, power_tag_index)
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 783, in __read_int_16
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 753, in __read
2024-04-24 19:43:49.896 INFO (MainThread) [homeassistant.components.sensor] Setting up powertag_gateway.sensor
2024-04-24 19:43:49.905 INFO (MainThread) [custom_components.powertag_gateway.sensor] Going to read product type of device 150...
2024-04-24 19:43:49.905 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 31023, slave_id 150
2024-04-24 19:43:49.910 WARNING (MainThread) [custom_components.powertag_gateway.schneider_modbus] Could not read product type of device on slave ID 150: Exception Response(131, 3, GatewayNoResponse). Might be because there's device, or an actual error. Either way we're stopping the search.
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 533, in tag_product_type
identifier = self.__read_int_16(0x792F, power_tag_index)
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 783, in __read_int_16
File "/config/custom_components/powertag_gateway/schneider_modbus.py", line 753, in __read
2024-04-24 19:43:49.914 INFO (MainThread) [custom_components.powertag_gateway.sensor] Product type is None
2024-04-24 19:44:19.882 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:44:19.885 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:44:49.885 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:44:49.887 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:45:19.886 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:45:19.889 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:45:49.889 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:45:49.891 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:46:19.890 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:46:19.892 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:46:49.893 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:46:49.895 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:47:19.895 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:47:19.897 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:47:49.896 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:47:49.898 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:48:19.899 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:48:19.901 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:48:49.901 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:48:49.904 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:49:19.914 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:49:19.916 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:49:49.916 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:49:49.918 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:50:19.918 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:50:19.921 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:50:49.920 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:50:49.922 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2
2024-04-24 19:51:19.921 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] Reading __read_int_16 on address 112, slave_id 255
2024-04-24 19:51:19.923 INFO (MainThread) [custom_components.powertag_gateway.schneider_modbus] The result of __read_int_16 was 2

I'm slowly losing my mind here. Your smartlink isn't responding to any of my requests for getting the wireless device's product type. Can you please confirm that there's a wireless device on address 150?
Could it be that even though it was once configured, the device on address 150 has been moved?
Sorry for not being of further help. :(

I have been able to successfully read the data of a unit after adjusting the Modbus -address to 150. It look like I need to register a list of configured modes-addresses somewhere, is that correct?

Oh that's great! Happy to hear that! :)
I was going off Schneider's documentation lol

For other devices, I have a function I can call to retrieve the modbus address of the first device, then the second device, etc... For the SmartLink, seemingly being one of the earliest devices, there is no such functionality. This is why I hardcoded it to search from 150.
If I were to search the entire range for devices, it takes 5 seconds to timeout, so startup would take 254 * 5s = 21 minutes, this would make HomeAssistant terminate our process.
The only solution I can propose is to ask the SmartLink users to put your devices in the 150-169 range (which can be any arbitrary range, but let's use the one that matches the docs).

Thanks for the update.
I have numbered all units consecutively. (150…..163)
All 15 units have been found.
Only unit shown as “Unknown” (the A9XMWA20)

OEPS!!!
After upgrade to version v0.3.0, and a restart:
All Entities of all units are “Unavailable”

Ah man sorry about that, I refactored a lot of code. I'll can fix that tomorrow.Can you include your logs as well please? That will help for sure.On 4 May 2024 10:36, KingandQ @.***> wrote:
OEPS!!!
After upgrade to version v0.3.0, and a restart:
All Entities of all units are “Unavailable”
image.png (view on web)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

No problem, there seems to be light at the end of the tunnel………. 
Results after some testing:
Test-Environment:

First installed version 0.2.5
All Diveces where found and all there entities except the entities for A9XMWA20
Live-Environment:
Reloaded version 0.2.5 (so donwgraded from 0.3.0)
All devices where found and all there entities except the entities for AX9MWA20
Test-Environment:
Upgrade to 0.3.0
All Diveces where found and NON of the entities.

Unfortunately, no more time to filter all power tag lines from the logging.

Unfortunately, no more time to filter all power tag lines from the logging.

@KingandQ any chance you can get me those logs still? I don't immediately see what I missed in the upgrade.

Alright I got that fixed for you on v0.4.1. :)
Hope everything works now.

How about v0.5.0?

Thanks for the update.
A Big step forward.
All units are found but some data is still missing.
Version 0.2.0 is OK.
Version 0.5.0:

Temperature in: F (Maybe this is an environment setting?)
3 times: Unavailable

Temperature is indeed your config, we receive them as Celcius.
Alarm valid has been removed because I deemed it useless and needed work. You may remove this one.
Active power phase Phase.A has been renamed to Active power phase A, does it not appear for you? Maybe try another restart or reconfig?
Partial energy should be the same as Partial energy delivered and received right? There really should be an entity that is available for this.

The latest version installed on the live environment today.
It seems that all data retrieved from all 14 units are displayed correctly.
Regarding: A9XMWA20
I don't know if this is all that can be displayed:

Datetime
Status

Glad to hear! :)
It should also display hardware version, firmware version and serial number in device info. The status has an extra attribute showing what's wrong when something is wrong. And that's literally everything that your device exposes through modbus. It's the same for the Panel Server even, that's everything.

Today I put all entities of all units on a dashboard
The following enteties all show the value: Unknown

Is this as expected?

Ah no, I hoped they did work. I'll fix them for you.

Did some fixes in in v0.5.1, please try again. The 'phase A' ones will become unavailable, as they're not supported by Smartlink.

After install V0.5.1

Ah man I was hoping the 'Unknown' ones would have worked. :( They are only available for NSX devices it seems.

Please confirm that your device isn't an NSX one? I'll disable those for non-NSX ones in the next round.
The Unavailable ones can be removed, those aren't supported.

First of all, thanks again for all your efforts to resolve this.
Below my hardware-configuration as in my previous post:

1 * Acti9 SmartLink
12 * A9MEM1560
1 * A9MEM1542
1 * A9MEM1541

Since they don't appear in your overview, I assume these are not NSX devices.
Is it recommended to remove all "Unavailable" and all "Unknown" entities, or does that happen automatically with the next update?

Ah right, I should have figured.
The "Unavailable" ones mean that the entity is no longer provided by this integration, and must be removed manually. I can't do this for you as far as I'm aware.
The "Unknown" ones mean that this integration tries to get its data, but it's not able to. You can't remove this one yet, but next release, I'll make them become "Unavailable" so you can clean them up.

Some additional info.
I have 5 modules of type A9DG3616.
2 out of 5 show power factor : Unknown
What needs to be done to correct this?

Cleaned up those Unknown entities for you now, these will become Unavailable, which you can remove now.
For the power factor;
Is there a difference in firmware version between the devices? For example, device temperature only becomes available from firmware versions 004.xxx.xxx, it's possible that power factor has a similar threshold.
Otherwise, can you find any differences between its setup of your device configuration? Can you find any problem in the logs about this? This entity also uses 'Power factor sign convention', perhaps that requires configuration?

Hi Breina, I'm new here. I installed a Power Tag Link and the initial configuration went well, but it doesn't see the Tags in the field.
I'm attaching the configuration on the Gateway and the home assistant logs.

A Presto


Exception when loading fop

@dubinsky one other issue I've seen, which is really cosmetic: when fop is class loaded, an exception is thrown (at least on my systems):
org.xml.sax.SAXNotSupportedException: http://xml.org/sax/features/external-general-entities
at com.icl.saxon.aelfred.SAXDriver.setFeature(SAXDriver.java:451)
at com.icl.saxon.aelfred.SAXParserFactoryImpl.setFeature(SAXParserFactoryImpl.java:28)
at org.apache.batik.dom.util.SAXDocumentFactory.(SAXDocumentFactory.java:403)
at org.apache.fop.image.loader.batik.PreloaderSVG$Loader.getImage(PreloaderSVG.java:127)
at org.apache.fop.image.loader.batik.PreloaderSVG$Loader.access$200(PreloaderSVG.java:108)
at org.apache.fop.image.loader.batik.PreloaderSVG.preloadImage(PreloaderSVG.java:76)
at org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:176)
at org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:127)
at org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:123)
at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)
at org.apache.fop.fo.FObj.processNode(FObj.java:131)
at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.startElement(FOTreeBuilder.java:293)
at org.apache.fop.fo.FOTreeBuilder.startElement(FOTreeBuilder.java:179)
at net.sf.saxon.event.ContentHandlerProxy.startElement(ContentHandlerProxy.java:366)
at net.sf.saxon.event.ProxyReceiver.startElement(ProxyReceiver.java:132)
at net.sf.saxon.event.SequenceNormalizer.startElement(SequenceNormalizer.java:84)
at net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:371)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:439)
at net.sf.saxon.event.Sender.send(Sender.java:168)
at net.sf.saxon.jaxp.IdentityTransformer.transform(IdentityTransformer.java:368)
at org.opentorah.xml.Saxon.transform(Saxon.scala:135)
at org.opentorah.xml.Saxon.transform(Saxon.scala:70)
at org.opentorah.fop.Fop$.run(Fop.scala:110)
at org.opentorah.fop.Fop$.run(Fop.scala:73)
at org.opentorah.docbook.plugin.ProcessDocBook.run(ProcessDocBook.scala:81)
...etc
it's caused by org.apache.batik.dom.util.SAXDocumentFactory trying to set an XML parser feature, that can't be set for some reason. Are you aware of any way to control this? As I say, it's cosmetic, as the exception is caught and no harm done, it's just a bit annoying. It doesn't appear to be caused by any of your plugin code at all.

@sgjohnston
I saw this, but it doesn't reproduce for me every time (I suspect that Gradle daemon caches loaded classes).

exception is caught and no harm done

I am not so sure about that.

It doesn't appear to be caused by any of your plugin code at all

It kind of is: I have to counter-act some classpath magic... I did it before for SVG produced by MathJax from formulas, but not for SVG coming from anywhere else. Pull request https://github.com/opentorah/opentorah/pull/115 has more information. Let's see if the patched version (still v0.7.51) fixes this for you :)

Yes, once the gradle daemon starts, and the class is loaded, it stays "live" until it's shut down, so you only see the exception each time the daemon starts. You can reliably reproduce it by stopping the daemon first, or running without it (gradle --no-daemon).
Anyway, #115 fixes it, no exception thrown.
Thanks!

Great, thanks! Closing.


Monitoring Release Notes

As we provide an inbuilt monitoring solution with its own versions some customers have requested formal release notes - often a requirement of internal process mgmt
Let me know if this is the right place for this

@deniseschannon what do you think of this?

I know this came up again recently internally with @dnoland1

@leflambeur I'm assuming you are talking about monitoring v1?


Write unit tests for the Message object

What is wrong?
There are no unit tests for the Message object
How can it be fixed
Write unit tests that verify that it:

all __init__ parameters are properly validated.
v.is_origin correctly returns True/False for whether this message is the origin message meaning that it's the ourtermost VM message being executed.
v.origin property returns correct value.
v.code_address returns correct value when to address is set to CREATE_CONTRACT_ADDRESS.
v.storage_address returns correct value when message is performaing contract creation.
v.is_create returns True when message is for contract creation.

@pipermerriam giving this one a shot.


Adjust aggregator documentation

Description
The current aggregator README documentation is outdated.
Several sections are added, including notes on the new RecursionCircuit.
Type of change

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

oh no i should merge this first..

@darth-cy could you cherry-pick commits https://github.com/scroll-tech/zkevm-circuits/pull/1363/commits/4551f1e0cb74b1cd4b3a40d6a3945df3306769f6, https://github.com/scroll-tech/zkevm-circuits/pull/1363/commits/c5fdd2715c202dfabc1ce307974b7caac756ca3a and https://github.com/scroll-tech/zkevm-circuits/pull/1363/commits/427278552a26d3d12fb684601ca581cf920d7731 to create a new PR to develop?
We can close this PR for now.


Uncaught TypeError: Cannot read property 'localeCompare' of undefined

[Enter steps to reproduce:]

...
...

Atom: 1.35.1 x64
Electron: 2.0.18
OS: Microsoft Windows 10 Pro
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'localeCompare' of undefined
At C:\Users\subha\AppData\Local\atom\app-1.35.1\resources\app\static\<embedded>:11

TypeError: Cannot read property 'localeCompare' of undefined
    at i (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:641982)
    at Array.sort (native)
    at SnippetsProvider.findSuggestionsForPrefix (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:641843)
    at SnippetsProvider.getSuggestions (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:641437)
    at n.forEach.t (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:631266)
    at Array.forEach (<anonymous>)
    at AutocompleteManager.getSuggestionsFromProviders (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:630782)
    at AutocompleteManager.findSuggestions (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:630520)
    at AutocompleteManager.requestNewSuggestions (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:639053)
    at AutocompleteManager.showOrHideSuggestionListForBufferChanges (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:640144)
    at Function.simpleDispatch (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:1172354)
    at Emitter.emit (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:1173795)
    at TextBuffer.emitDidChangeTextEvent (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:504122)
    at TextBuffer.transact (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:492297)
    at TextEditor.transact (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:24215)
    at mergeIntersectingSelections (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:16150)
    at TextEditor.mergeSelections (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:39484)
    at TextEditor.mergeIntersectingSelections (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:39038)
    at TextEditor.mutateSelectedText (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:16113)
    at TextEditor.insertText (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:15662)
    at TextEditor.e.(anonymous function) [as insertText] (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:259365)
    at TextEditorComponent.didTextInput (~/AppData/Local/atom/app-1.35.1/resources/app/static/<embedded>:11:93878)

Commands
     -1:01.0 editor:newline (input.hidden-input)
     -0:59.2.0 core:paste (input.hidden-input)
  2x -0:58.4.0 core:move-left (input.hidden-input)
     -0:57.6.0 core:move-right (input.hidden-input)
     -0:53.9.0 core:move-left (input.hidden-input)
     -0:38.4.0 core:paste (input.hidden-input)
     -0:37 core:move-right (input.hidden-input)
     -0:28.4.0 core:backspace (input.hidden-input)

Non-Core Packages
angular-bootstrap 1.0.1
atom-bootstrap4 1.4.0
autocomplete-jquery-mobile 0.2.2
bootstrap-sass-snippets 2.1.1
codeigniter 0.4.0
codeigniter-nucleus 0.4.3
drunken-php 0.2.4
html-to-javascript 0.2.0
ide-php 0.7.18
jQuery 1.2.6
Quick-JavaScript 2.2.0
turbo-javascript 1.4.0
v-bootstrap4 0.2.2

Thanks for the report!  Can you confirm a few things for us?

What were you doing at the time of the error?
Is the error is reproducible?
If reproducible, do you see the error in safe mode (atom --safe)?

I encountered this error and clearly this results from an error in the snippets file (user error?) or how its content is handled.
I had a snippets file that validated correctly and mostly worked but typing the letter 'u' would cause the error. I defined 3 custom snippets starting with 'u'
Deleting the 3 snippets and re-typing them manually fixed the error.
Unfortunately didn't save the offending snippets file. Will update if the error recurs.


[BUG] - Screen Reader Announcement Issue in Select Component Due to Multiple aria-labelledby References

NextUI Version
2.4.8
Describe the bug
In the Select component, the screen reader (VoiceOver) announces the label and value together in a confusing way, such as:
"Dog Select an animal, list box pop-up collapsed."
This occurs because the aria-labelledby attribute on the Select component’s button references multiple elements (react-aria2285256286-:r3p: and react-aria2285256286-:r3l:). As a result, the screen reader concatenates the text from these elements into a single, unclear announcement without proper separation.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Use the Select component in a screen reader-enabled environment.
Open the dropdown and select an option.
Observe the screen reader's announcement after selecting an option.

Expected behavior
The screen reader should announce the label and value distinctly, such as:
"Dog, Select an animal, list box pop-up collapsed."
Screenshots or Videos
https://github.com/user-attachments/assets/de2654ac-6764-4117-b89e-98c467eb0dd6
Operating System Version
macOS
Browser
Chrome

Hi @kimskovhusandersen Can I work on this ? Please assign to me.

@manoj0727 go ahead


Duplicate Esp in FOMOD option

https://i.imgur.com/jBR52xs.png
Esp is showing twice when only one is available for that FOMOD selection.
https://i.imgur.com/M5xZmVE.png

FLEX displays correct number of plug-ins.

Fixed in current version


Broken link to documentation web site

On this page:
https://github.com/CityOfZion/neon-js
There is a link under the section tilted Browser that says:
Find more guides on our documentation website

Unfortunately the link given results in a Access Denied error:
https://coz.io/neon-js/docs/en/guides/basic/sendasset.html
<Error>
AccessDenied
<Message>Access Denied</Message>
<RequestId>C01PYQJCBMTJAY0C</RequestId>
<HostId>1G8tA8UJOaUIVzs7k7iyIQLmd6ae/IrEgoawqm/aLLeJxFByxnVpZT8SjPdSEGkAyKkeJ5Qiv+c=</HostId>
</Error>

Can someone give me the link to the documentation web site?

Updated the readme link. The correct link should be https://docs.coz.io/neo2/neon-js/docs/en/guides/basic/sendasset.html


Releasing scope constraint

Issue #175

Your welcome 😁
Do you have plan the next release soin ?
Or should i move to dev-master ?

I'm preparing the release in #177

https://github.com/getsentry/sentry-symfony/releases/tag/2.2.0


Update moc to 0.8.7

Fix CI by overwriting the latest moc version to the dfx cache show directory.

@skilesare Ping for this fix as well :slightly_smiling_face: Hopefully this helps with the release and docs


Return assertion errors

First of all thanks for this module, it makes testing much more succinct. Is there any way to have matchers actually return their errors though?
Here I have  block of matchers inside of a with block,
  with "an atom" do
    setup context do
      assign context,
        spring: cast(Semester, :spring),
        summer: cast(Semester, :summer),
        winter: cast(Semester, :winter)
    end

    should_assign_key spring: {:ok, "01"}
    should_assign_key summer: {:ok, "05"}
    should_assign_key winter: {:ok, "09"}
  end

in the event of any failing I get the not so useful error message:

test with 'an atom': should have passing matchers (SemesterTest)
test/lib/semester_test.exs:42
** (ShouldI.MultiError) multiple matcher errors

Obviously it would be ideal if I were to just get the individual assertion errors. This is with version 0.2.1 and elixir version 1.0.2.

You need to configure ExUnit to use ShouldI's formatter. Add this to your test_helper.exs file: ExUnit.start(formatters: [ShouldI.CLIFormatter]). I will update the readme with this information.

Thanks Eric, that solved that. Are with blocks not intended to be nested? I got unexpected behavior when they're nested and used with the built in matchers (keys not defined on context)?

We are using nested with blocks so they work for us at least :). Can you show the full error you get and a snippet of your code?

Sure thing. In this example the matcher works as expected in the first with block, and the context works properly in the second with block with a standard test - but the problem arises when you try to use a should_* matcher in a nested with block.
https://gist.github.com/Dkendal/d12e933e07d4e47f699a

I have pushed a possible fix to master. Can you please try it out?


Debugging with generator-ng2-webpack projects

"I found it challenging to debug this because the default "npm start" script generated a build with webpack that was fairly opaque. I do not believe source maps were turned on in the generated build, and so it was difficult to debug the built JavaScript to see what might be wrong. " - Jake

generator-ng2-webpack projects use webpack's devserver and sourcemaps for both script and css.
A good explanation of the process can be found at http://stackoverflow.com/a/33422697

I will review the link. Thank you.

Can you confirm if
https://github.com/cmelion/generator-ng2-webpack/issues/28 fixes the
browser open issue on Linux?
On Thu, Apr 28, 2016 at 7:37 PM, Jacob Beard<EMAIL_ADDRESS>wrote:

I will review the link. Thank you.
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/cmelion/generator-ng2-webpack/issues/27#issuecomment-215593455

reopening due to related issue https://github.com/cmelion/generator-ng2-webpack/issues/32
Also it's unclear how to debug unit tests using a docker based workflow


Suggestion: Publish latest beta version to NPM using the @next tag

To make it easier for users that are regularly testing the latest beta version, it would be helpful if the latest beta version was published to the NPM registry under the @next tag.
Users could then always be sure of obtaining the latest version to test by issuing the command:
npm install dexie@next

Ok. Right now, I publish betas on npm with tag @beta. Is there a common practice to use @next tag instead? If so, I'll just switch.

The NPM tool uses the following tag strategy (as stated in https://docs.npmjs.com/cli/tag):

Tags can be used to provide an alias instead of version numbers. For example, npm currently uses the tag "next" to identify the upcoming version, and the tag "latest" to identify the current version.

This now seems to have been adopted with many common repositories.

Ok, thanks! Keeping this issue open til its done.


Start weeks on monday

Hello there! Is it someway possible to change the first day of the week to monday instead of sunday? :)

Hello there! Is it someway possible to change the first day of the week to monday instead of sunday? :)

Hi
i added startsWeeks option into locale options. you can change first day of the week on ver 1.8.4.
sample:
locale: {
  format: "YYYY/MM/DD",
  weekday: ["Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun"],
  startsWeeks: 1,
  todayBtn: "Today",
  clearBtn: "Clear",
  closeBtn: "Close",
}

Hello there! Is it someway possible to change the first day of the week to monday instead of sunday? :)

Hi
i added startsWeeks option into locale options. you can change first day of the week on ver 1.8.4.
sample:
locale: {
  format: "YYYY/MM/DD",
  weekday: ["Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun"],
  startsWeeks: 1,
  todayBtn: "Today",
  clearBtn: "Clear",
  closeBtn: "Close",
}

Hmm I think something went wrong there. The calendar is now empty for me.

Hmm I think something went wrong there. The calendar is now empty for me.

Hmm I think something went wrong there. The calendar is now empty for me.

can you give  me your setting data?

Hmm I think something went wrong there. The calendar is now empty for me.

can you give  me your setting data?

DD-MM-YYYY

thanks.
i try this setting on my code. it's working.
i already put it on codesandbox. you can see it.
sample code URL : https://codesandbox.io/s/nostalgic-river-nd5r2?fontsize=14&hidenavigation=1&theme=dark

DD-MM-YYYY

thanks.
i try this setting on my code. it's working.
i already put it on codesandbox. you can see it.
sample code URL : https://codesandbox.io/s/nostalgic-river-nd5r2?fontsize=14&hidenavigation=1&theme=dark

I'm not sure what is causing this issue for me.
When I posted the original request, vue3-datepicker-lite was working correctly for me. The next morning I saw your comment and updated to 1.8.4 after which the addon stopped working. I've now reverted the addon back to 1.8.3, and it is still broken. Deleting my node_modules does not solve the issue either. Any suggestions what the issue might be? I've kinda ran out of ideas.

I'm not sure what is causing this issue for me.
When I posted the original request, vue3-datepicker-lite was working correctly for me. The next morning I saw your comment and updated to 1.8.4 after which the addon stopped working. I've now reverted the addon back to 1.8.3, and it is still broken. Deleting my node_modules does not solve the issue either. Any suggestions what the issue might be? I've kinda ran out of ideas.

Alright, I figured it out.
I used "startWeek" instead of "startWeeks". This was the reason the function was not checking my setting.
However, that also means that there is actually a bug which causes the calendar to stop functioning properly if the startWeeks property was not provided. I've already found the cause of this, I will submit a MR :)

Alright, I figured it out.
I used "startWeek" instead of "startWeeks". This was the reason the function was not checking my setting.
However, that also means that there is actually a bug which causes the calendar to stop functioning properly if the startWeeks property was not provided. I've already found the cause of this, I will submit a MR :)

Alright, I figured it out.
I used "startWeek" instead of "startWeeks". This was the reason the function was not checking my setting.
However, that also means that there is actually a bug which causes the calendar to stop functioning properly if the startWeeks property was not provided. I've already found the cause of this, I will submit a MR :)

Thanks! it's good news!
I think ... this bug maybe not only "startWeeks" property. so i fixed the bug when lost any property on locale attribute was provided and committed to ver 1.8.5

Alright, I figured it out.
I used "startWeek" instead of "startWeeks". This was the reason the function was not checking my setting.
However, that also means that there is actually a bug which causes the calendar to stop functioning properly if the startWeeks property was not provided. I've already found the cause of this, I will submit a MR :)

Thanks! it's good news!
I think ... this bug maybe not only "startWeeks" property. so i fixed the bug when lost any property on locale attribute was provided and committed to ver 1.8.5

Awesome, thanks for the update!

Awesome, thanks for the update!


Add option to filter specific actors from the xp menu.

Since Eidolon's are character actor type they will effect the xp grant of the encounter calculations as an additional party member.
Solution:
Create a new option to allow filtering by actor ID to remove specific actors from the award window/xp calculations.

Alternative I have filtered minion and eidolon actors from the award menu.


Format according to new black rules

Format code according to current black config #5157 # 5170.
This format will be added to .git-blame-ignore-revs sot that github and properly configured git clients ignore these format changes.
The following files were updated to preserve matrices that were formatted to appear better: circuit_test.py, quil.py, arithmetic_operation_test.py, clifford_gate_tes.pyt, controlled_gate_test.py, fourier_transform_test.py, fsim_gate.py, fsim_gate_test.py, linear_combinations_test.py, channels_test.py, two_quibit_to_cz_test.py
Autoform was not applied to cirq-google/cirq_google/cloud/quantum which is autogenerated code.

I think the different file count compared to my attempt in #5258 is because you caught the few non-generated files in cirq-google/cirq_google/api/v* and the examples directory, both of which I missed.


How to add a new action to the editor that replaces editor content and maintains Undo stack ?

Hi, I have implemented a java code beautifier which I want to plug into the VS Code editor.
When I call 'setValue' or 'setModel' actions of the monaco editor the text is replaced yet undo stack is destroyed and I cannot undo this action.
Any help is greatly appreciated. Thanks.

Just in case anyone stumbles on the same issue, I'm sure it can be handled more graciously, so I'll leave this open for now:
// remove breakpoints
oldDecorations = activeEditor.deltaDecorations(oldDecorations, []);

activeEditor.executeEdits('beautifier', [{ identifier: 'delete' as any, range: new monaco.Range(1, 1, 10000, 1), text: '', forceMoveMarkers: false }]);
activeEditor.executeEdits('beautifier', [{ identifier: 'insert' as any, range: new monaco.Range(1, 1, 1, 1), text: text, forceMoveMarkers: false }]);
activeEditor.setSelection(new monaco.Range(0, 0, 0, 0));
activeEditor.setPosition(currentPosition);

// add breakpoints
oldDecorations = activeEditor.deltaDecorations(oldDecorations, breakPoints);

Rather than implementing the beautifer as a command that replaces the entire editor contents you should implement a Code formatter as defined by the VS Code API. Please see the formatter best practices blog from @jrieken


Disabled Auto Detected Tasks Should Have An Option Not To Show This Automatically

Request: Option Not To Show This Automatically
I am using WSL so I can't run directly in there. Tho It's okay if I can't, but I think there should have a settings not to show this to the explorer automatically as it shrink the explorer view.

This is an intended change https://code.visualstudio.com/updates/v1_37#_npm-scripts-explorer-visible-by-default.

I am using WSL so I can't run directly in there.

You should use the WSL remote extension than you can runs scripts also in WSL, pls see
https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl


User story:  Formation Marker - Frontend View

As a Data Manager, I want to be able to browse and view the Formation Marker object in WE
Acceptance criteria

[ ] The WE  frontend is extended to support browsing the Formation Marker object

Also, here are a few points that need to be addressed:

[ ] Constraint 1
[ ] Constraint 2

Resources

Resource A
Resource B

Implemented by #1793


Feature/update templates

Update Templates and Labels

Resolves #120
DCO 1.1 Signed-off-by: Sam Richard<EMAIL_ADDRESS>

@Snugug update branch


Make acceptBody universal

Body should accept any type, not only arrays.

This can't be achieved as body is stored as ArgumentsInterface which requires named parameters. Body can only work with Array type (not union, not generic).


Wait a bit: Creates CHANGELOG.md using github-changelog-generator

See https://github.com/skywinder/github-changelog-generator

Cool stuff. :-) :+1:


Add support for System.Diagnostics.Metrics

Summary
Relies on https://github.com/dotnet/diagnostics/pull/3587

Release Notes Entry
Add support for System.Diagnostics.Metrics

/backport release/7.x

/backport to release/7.x


Revision of editor/movie_writer/movie_file property value storage location

Tested versions

Reproducible in 4.2.1
Not reproducible in 3.5.3

System information
Godot v4.2.1.stable - Ubuntu 22.04.4 LTS 22.04 - Wayland - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i7-1260P (16 Threads)
Issue description
The current storage location of the editor/movie_writer/movie_file project settings property in the project.godot file poses challenges for user privacy, collaboration and version control.
To enhance security and mitigate conflicts, we should store this value to a more suitable location.
Steps to reproduce

Start a new project
Set the value of editor/movie_writer/movie_file
Have fun writing a custom script to avoid pushing this to version control

Minimal reproduction project (MRP)

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).

I'd then be very, very encouraged, not to say compelled, to share the home directory name in the file path defined by this property, and I don't really want to do that 😿
mrp.zip

Doesn't make sense as an editor setting since it's a global path, it'd be shared with all projects, it should instead be made a local path, that way it won't contain sensitive information (unless you use a path that's relative and contain that sensitive information, but that's unavoidable, and unlikely to happen)

You can already manually enter a relative path in the Project Settings. However, if we change the path type in the project settings, you won't be able to exit the project folder in the file dialog that appears – so you won't be able to write a movie outside the project folder, which is often desired.


fix(removeListener): Remove listener is not a function, use off instead

looks already fixed in master


datastore-certificate not cleaned up atfer tcp is deleted

After we delete a tcp, the datastore-certificate secret remains in the cluster named as <clusterName>-datastore-certificate.
Is it intentional to not delete it, similar to how other secrets are deleted?

Unfortunately, I'm not able to replicate your issue.
$: kubectl get tenantcontrolplanes.kamaji.clastix.io
NAME      VERSION   STATUS   CONTROL-PLANE ENDPOINT   KUBECONFIG                 DATASTORE   AGE
k8s-130   v1.30.0   Ready    <IP_ADDRESS>:6443      k8s-130-admin-kubeconfig   default     28s

$: kubectl delete tenantcontrolplanes.kamaji.clastix.io k8s-130
tenantcontrolplane.kamaji.clastix.io "k8s-130" deleted

$: kubectl get secret
No resources found in default namespace.

Keep in mind we do have a finalizer on such Secret since it's required to de-provision the Datastore data, such as cleaning up the etcd key-prefixed data, or the RDBMS schema, etc.
I suspect you're facing an egg/chicken problem, such as deleting both the Tenant Control Plane, as well as the Datastore used by it: it means the etcd (for the sake of simplicity) is not going to be responsive anymore, Kamaji tries to perform a clean-up failing due to missing connection to it, creating this sort of non cleaned resource side-effect.
In case of this latter case, you have to be sure the Datastore is still working, otherwise, Kamaji cannot perform the clean-up, and the Datastore will be kept there until it hasn't been completed. If you're sure the Datastore has gone forever, you can remove the finalizer manually, since Kamaji is not aware of your business logic.
Tho, I would suggest you yo have a proper deletion process, such as:

Datastore objects in a different Namespace
TenantControlPlane objects in their own Namespaces
Delete first the TenantControlPlane objects
Eventually, deleting the Datastore objects, and the subsequent resources

The clean-up is a pretty important task, otherwise a collision effect could happen when reusing the same Datastore with the same TenantControlPlane name and a new Control Plane would contain the data of the previous one.


Remove redundant macro logic

This change is

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

Comparison is base (46402be) 69.16% compared to head (417c656) 69.16%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1202   +/-   ##
=======================================
  Coverage   69.16%   69.16%
=======================================
  Files          58       58
  Lines        7131     7131
  Branches     7131     7131
=======================================
  Hits         4932     4932
  Misses       1784     1784
  Partials      415      415

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