Added customer search

Codecov Report

Merging #69 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #69   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          14     14
  Lines         403    408    +5
=====================================
+ Hits          403    408    +5

Impacted Files
Coverage Δ

customer.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


XHR returned response code 0

Always receiving an XHR returned response code 0 when uploading specific files on the server

Kinda does because I think the real issue is XHR timeout. How can we set the timeout period for the call? My server creates thumbnails and stuff so it takes a bit on large files.


Set JDK_REPO for zos as is if it's using ssh.

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

fix runtimes/backlog/issues/365


Dependency cleanup

Removed dependencies left over by the component split.

Coverage remained the same at 38.029% when pulling 65018012e5593581c8938adde2fc6a6b398406e5 on rjstires:dependency-cleanup into 8ff6448850d94db33585dafdf4bd71988a0e5c09 on linode:develop-transitional.

It would appear unrelated, but while reviewing this I wanted to hit up the stackscripts page to verify that the ACE removal didn't affect it.
When I switch back to the develop branch I don't get this (from the DistributionSelect):
VM42577 bundle.js:130294 TypeError: Cannot read property 'toLowerCase' of null
    at VM42577 bundle.js:96747
    at arrayMap (VM42577 bundle.js:12175)
    at Function.map (VM42577 bundle.js:21086)
    at DistributionSelect (VM42577 bundle.js:96747)


French support for env_canada

Add support for the env_canada alerts when the Environment Canada integration is configured in French.
Also remove "Special Weather" since it is not listed in the reference page as an alert name.
Should fix #100

There hasn't been any activity in this pull request recently so I will close it. Feel free to create a new one if you want to continue your work. Thanks for your contribution!


[Upgrade] Establish & document change management process

This is specifically for deciding how changes go into main. We need to make sure everyone within and outside of the Unfinished organization knows how to submit PRs and what is expected in PRs. For example, we may reject any PRs that do not have an Issue for them.  These things need to be documented.  We already have PR templates with checklists, so we should review that and make sure each type of PR (bug, enhancement, feature...) makes clear what's required in that PR.

Let's discuss specifically what deliverables we want for this story

Love to see:

General review guidelines

closing per @wilwade we can revisit and add more as time permits


Print human readable time for event

Closes #12280
Reduce the length of event time as AGE column does.
Simplified implementation of #12331
This PR uses existing function to reduce the length, no dependency is required.
Doesn't add any new flags, users should use -o template to view the precise event time.

@erictune @bgrant0607 - I've created a new PR and used existing function to implement this.

@k8s-bot ok to test

Thanks. LGTM.


Updating releasing.md in order to solve issue with the functional tests

When trying to build and upload the archives, it fails as functional test for the plugin cannot find the right artifact. We should upgrade the releasing.md to avoid those issues.

@dlemures what's the error you're running into?


Author app not retrieving recipients when sending messages

Hi There,
we have just configured the company communicator as well as the author app and i am currently trying to send a test message, however when I send to a teams channel/team members no recipients are detected and no messages are sent.
There are no error messages anywhere that I can see, other than the following message when trying to Export details:
Ooops! An unexpected error seems to have occured. Why not try refreshing your page? Or you can contact your administrator if the problem persists.
Any help would be appreciated
thanks!

Hello @jcsul,
If the issue is related to recipient not visible in the list(see below screenshot attached) then you should check if user app is installed in the team where you are trying to send the message.

There issue already raised related to The bot is not part of the conversation roster   #362 .
We are closing this one.
Thanks.


Allow to start a Scheduler in a batch job

One of the goal of ClusterManager object is to be able to launch a remote scheduler. In dask-jobqueue scope, this probably means submitting a job which will start a Scheduler, and then connect to it.
We probably still lacks some remote interface between ClusterManager and scheduler object for this to work, so it will probably mean to extend APIs upstream.
Identified Scheduler method to provide:

retire_workers(n, minimum, key)
scheduler_info(), already existing, see if sufficient,
add_diagnostic_plugin(), and mostly retrive plugin information remotely

I suspect that adaptive will need to change significantly too, this will maybe lead to having a transitional adaptive logic in dask-jobqueue, and other remote function to add in scheduler.
This is in the scope of #170.

With #306 we've got a lot of what is needed to start a Scheduler in a dedicated batch job.
I also believe we've got all what is needed in Distributed side too, as dask-kubernetes don't use a LocalCluster anymore, see https://github.com/dask/dask-kubernetes/pull/162.

Yes, everything should be set up.  We probably need to abstract out the
FooJob classes to split between scheduler and workers.  All of the
SpecCluster infrastructure is there though.
On Fri, Oct 11, 2019 at 2:45 PM Guillaume Eynard-Bontemps <
<EMAIL_ADDRESS>wrote:

With #306 https://github.com/dask/dask-jobqueue/issues/306 we've got a
lot of what is needed to start a Scheduler in a dedicated batch job.
I also believe we've got all what is needed in Distributed side too, as
dask-kubernetes don't use a LocalCluster anymore, see
dask/dask-kubernetes#162
https://github.com/dask/dask-kubernetes/pull/162.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-jobqueue/issues/186?email_source=notifications&email_token=AACKZTBGJAU36PEH63LDH2DQODJVJA5CNFSM4GAH5VR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBBA2PI#issuecomment-541199677,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTE5KM76TSNEMWMSWBLQODJVJANCNFSM4GAH5VRQ
.

Just curious could you elaborate a bit more about why this would be useful. I have some guesses but I just want to make sure they are somewhat accurate.

I am guessing that the main advantage is that the scheduler does not run on the cluster login node anymore (most users around me run their own jupyter notebook server on the login node so the scheduler is on the login node as well, this is probably different with a JupyterHub setup). I do understand that doing that would be considered best practices by HPC sys-admin. I'd be curious if you have met some cases where the scheduler goes wild and consumes a lot more than expected or maybe there are a lot of people having their own Dask scheduler on the login node and it starts to add up.
IMO rather than the scheduler consuming more resources than it should what is a lot more likely to happen is that the client script will, for example because once you have your results from your job you do some not so light post-processing and you forget you are on the login node and not really supposed to do that.
I had some feed-back from users that told me that the ideal workflow for them would be to have the client code (the one that call client.submit) on their local machine (more flexible to install what you need, more familiar, nicer working conditions e.g. the shared folders are very slow on our cluster, think ipython takes 20-30s to launch sometimes and this is not something that is likely to change, etc ...) and be able to launch jobs on the cluster. Would such a workflow be made easier by the "remote scheduler" feature?

In practice I doubt that the scheduler will be expensive enough that system administrators will care.  They all ask about this, but I don't think that it will be important in reality.
Another reason to support this is for networking rules.  In some systems (10-20%?) compute nodes are unable to connect back to login nodes.  So here placing the scheduler on a compute node, and then connecting to that node from the client/login node is nice.
It may be though that this is a frequently requested but not actually useful feature.

Another reason to support this is for networking rules. In some systems (10-20%?) compute nodes are unable to connect back to login nodes.

In #354 @orbitfold seems in this particular case (at least for some clusters he has access too). @mrocklin could you give a few pointers that would help getting started on implementing a remote scheduler (my understanding is that using SpecCluster will help but I never had the time to investigate why exactly ...) ?

We need to make an object that follows this interface:
https://github.com/dask/distributed/blob/e7a2e6d41e0b719866769713d8f41cb5fcfbf6e8/distributed/deploy/spec.py#L22-L30
The simplest example today is probably SSHCluster: https://github.com/dask/distributed/blob/master/distributed/deploy/ssh.py
But rather than start things with SSH, it would presumably submit a job.

Thanks a lot! @hawk-sf seems to have some limitation on allowed ports to connect login node and workers in #355.

In practice I doubt that the scheduler will be expensive enough that system administrators will care. They all ask about this, but I don't think that it will be important in reality.
Another reason to support this is for networking rules. In some systems (10-20%?) compute nodes are unable to connect back to login nodes. So here placing the scheduler on a compute node, and then connecting to that node from the client/login node is nice.
It may be though that this is a frequently requested but not actually useful feature.

I am currently using dask-joblib on a PBS cluster and running the scheduler on the login node. It is indeed a bit problematic because the login node has only 2gb of memory and it quickly runs out if I am not careful with the size of computation graphs.
So I think I would definitely benefit from this feature.

Interesting, thanks for this use case! 2GB is certainly very small even more so when shared between all the cluster users. Are there some other nodes you can ssh to to do heavier work e.g. compilatiion of C++ code? On some clusters I am familiar with they are called devel nodes but the naming may well be different in your clusters.
One work-around in your use case is so start an interactive job where you launch your Dask scheduler i.e. you run your python script creating your PBSCluster.

The cluster I am using is very small and has only one type of compute node. I am not sure what you mean by an "interactive" job. Maybe what you say is that I should start the PBSCluster from a compute node. This does not work however, since it is impossible to submit new PBS jobs from a compute node (it can only be done from the login node).
The current workaround for me is to use a scheduler file to set up the communication between scheduler and workers using the shared file system.
Ideally I could run a python script on the login node that launches PBS jobs for both dask-scheduler and dask-worker and then I connect to dask-scheduler from my local workstation to submit my computations (using a ssh tunnel).

The cluster I am using is very small and has only one type of compute node. I am not sure what you mean by an "interactive" job.

An interactive job means you submit a job through your job scheduler and you end up in an interactive shell on a compute node. Look at this for an example on a cluster that use PBS.

This does not work however, since it is impossible to submit new PBS jobs from a compute node (it can only be done from the login node).

This is a mildly annoying restriction if you ask me, maybe try to talk to IT to see whether they would be ready to lift this restriction. People can still do it if they want using ssh login-node qsub. There was an issue where modifying submit_cmd to do that was reported to work, see https://github.com/dask/dask-jobqueue/issues/257#issuecomment-479556603.

The current workaround for me is to use a scheduler file to set up the communication between scheduler and workers using the shared file system (without using dask-jobqueue).

I am guessing you mean https://docs.dask.org/en/latest/setup/hpc.html#using-a-shared-network-file-system-and-a-job-scheduler. This seems like a reasonable work-around.

I connect to dask-scheduler from my local workstation to submit my computations (using a ssh tunnel).

I have had other people tell me that (third bullet point of https://github.com/dask/dask-jobqueue/issues/186#issuecomment-542027057). If you manage to make that work, please let us know (ideally in a separate issue).

An interactive job means you submit a job through your job scheduler and you end up in an interactive shell on a compute node. Look at this for an example on a cluster that use PBS.

Thank you! I didn't know this and it is very useful!

This is a mildly annoying restriction if you ask me, maybe try to talk to IT to see whether they would be ready to lift this restriction. People can still do it if they want using ssh login-node qsub. There was an issue where modifying submit_cmd to do that was reported to work, see #257 (comment).

I'll see if I can talk to IT next year!

I am guessing you mean https://docs.dask.org/en/latest/setup/hpc.html#using-a-shared-network-file-system-and-a-job-scheduler. This seems like a reasonable work-around.

Yes this is what I meant. It does work well enough in my case because I do not need adaptive scaling of workers (yet). It is a little unfortunate to have to start the cluster separately (not from the notebook that I use for my computations).

@muammar I see that you have commented in https://github.com/dask/dask-jobqueue/pull/390#issuecomment-603558844. Could you please explain the admin rules that are in place on your cluster just to get an idea what you are allowed to do on your cluster.
You may be interested by my answer above: https://github.com/dask/dask-jobqueue/pull/390#issuecomment-603558844:

launch the scheduler (i.e. create the Cluster object) in an interactive job: easier. If you like to work in a Jupyter environment, this is doable this way. There are a few hoops to jump through (mostly SSH port forwarding to open your Jupyter notebook in your local browser at localhost:<some-port>).
launch the scheduler (i.e. create the Cluster object) in a batch job. Only for Python scripts.
Starting the Dask worker by launching Dask commands yourself: https://docs.dask.org/en/latest/setup/hpc.html#using-a-shared-network-file-system-and-a-job-scheduler


Upgrade manifest.json to Manifest version v3

Problem description:
Hello, I want to say, that the Manifest v2 is slowly being outdated, so it would be good if you update this extension to Manifest v3.

I plan to. I've decided that I'm going to build the Manifest V3 version of the extension around Firefox 115 when it releases, as that is the version of Firefox that Windows 7 and 8.1 users will be stuck on (they'll be moved to 115 ESR). That is also when I plan to try to port it to Chromium.

No, absolutely not! Right now it's exclusive to Firefox, partly due to the fact that it's Manifest V2. Once it is Manifest V3, I can support both Chromium and Firefox.

Sorry for misunderstanding and confusion. I just understood it wrong, sorry.

But this issue will be opened until upgrade to Mv3, I'm right? Or you will close this for now?

I'll leave it open until the issue is resolved.

Transition to MV3 on the Firefox side has been postponed, as Mozilla themselves do not recommend using it yet for compatibility reasons. However, the transition has been done for the newly released Chrome version, and the Firefox betas are also Manifest V3.


build: update rules_js and pnpm version

Updated tooling allows to use lockfile version 9 in pnpm-lock.yaml. We've recently seen that dependabot PRs for dependency updates seem to create lock files with that lockfile version; as the tooling did not support it, the dependabot changes could not be used. Plausibly, dependabot PRs will work after this change.
Note that pnpm cannot be upgraded to the very latest version 9.5.0, as this needs to be explicitly enabled in aspect_rules_js first.
Note that I've explicitly "downgraded" the nodejs node_version to the default version used in the previous rules_nodejs version. The default version of the current rules_nodjs version requires a too new glibc for my ancient setup.
This might be hard to review manually because of all the formatting changes in pnpm-lock.yaml.
Comparing only the lines that contain the sha512 checksums shows no diff to master, which to me seems to indicate that the exact same versions of all the dependencies are still used.

This change is


[keyvault-common,table] bump core-http dep version to 1.1.4

These two libraries were not updated in #9539, possibly due to the exception of core-http v1.1.1 made for storage and
these two files came after #9539 was created/the the exception was made.

Is js - tables - ci build pipeline not ready for PR validation? @joheredi @mahdiva


linuxPackages.nct6687d: 0-unstable-2024-09-02 -> 0-unstable-2024-11-05

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for linuxPackages.nct6687d is: Kernel module for the Nuvoton NCT6687-R chipset found on many B550/B650 motherboards from ASUS and MSI
meta.homepage for linuxPackages.nct6687d is: https://github.com/Fred78290/nct6687d/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-11-05 in filename of file in /nix/store/xca3hh98v0190yhnvy4qir30fg0nv4ji-nct6687d-0-unstable-2024-11-05

Rebuild report (if merged into master) (click to expand)

38 total rebuild path(s)

38 package rebuild(s)

First fifty rebuilds by attrpath

linuxKernel.packages.linux_5_10.nct6687d
linuxKernel.packages.linux_5_10_hardened.nct6687d
linuxKernel.packages.linux_5_15.nct6687d
linuxKernel.packages.linux_5_15_hardened.nct6687d
linuxKernel.packages.linux_5_4.nct6687d
linuxKernel.packages.linux_5_4_hardened.nct6687d
linuxKernel.packages.linux_6_1.nct6687d
linuxKernel.packages.linux_6_11.nct6687d
linuxKernel.packages.linux_6_11_hardened.nct6687d
linuxKernel.packages.linux_6_12.nct6687d
linuxKernel.packages.linux_6_1_hardened.nct6687d
linuxKernel.packages.linux_6_6.nct6687d
linuxKernel.packages.linux_6_6_hardened.nct6687d
linuxKernel.packages.linux_hardened.nct6687d
linuxKernel.packages.linux_latest_libre.nct6687d
linuxKernel.packages.linux_libre.nct6687d
linuxKernel.packages.linux_lqx.nct6687d
linuxKernel.packages.linux_xanmod.nct6687d
linuxKernel.packages.linux_xanmod_latest.nct6687d
linuxKernel.packages.linux_xanmod_stable.nct6687d
linuxKernel.packages.linux_zen.nct6687d
linuxPackages-libre.nct6687d
linuxPackages.nct6687d
linuxPackages_5_10_hardened.nct6687d
linuxPackages_5_15_hardened.nct6687d
linuxPackages_5_4_hardened.nct6687d
linuxPackages_6_11_hardened.nct6687d
linuxPackages_6_1_hardened.nct6687d
linuxPackages_6_6_hardened.nct6687d
linuxPackages_hardened.nct6687d
linuxPackages_latest-libre.nct6687d
linuxPackages_latest.nct6687d
linuxPackages_lqx.nct6687d
linuxPackages_xanmod.nct6687d
linuxPackages_xanmod_latest.nct6687d
linuxPackages_xanmod_stable.nct6687d
linuxPackages_zen.nct6687d

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xca3hh98v0190yhnvy4qir30fg0nv4ji-nct6687d-0-unstable-2024-11-05 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A linuxPackages.nct6687d https://github.com/r-ryantm/nixpkgs/archive/0deecde1d48888640457289b42da9adde6043b16.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0deecde1d48888640457289b42da9adde6043b16#linuxPackages.nct6687d

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xca3hh98v0190yhnvy4qir30fg0nv4ji-nct6687d-0-unstable-2024-11-05
ls -la /nix/store/xca3hh98v0190yhnvy4qir30fg0nv4ji-nct6687d-0-unstable-2024-11-05/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:fast_forward: 1 package marked as broken and skipped:

linuxKernel.packages.linux_5_4_hardened.nct6687d

:x: 1 package failed to build:

linuxKernel.packages.linux_lqx.nct6687d

:white_check_mark: 17 packages built:

linuxKernel.packages.linux_5_10.nct6687d
linuxKernel.packages.linux_5_10_hardened.nct6687d
linuxKernel.packages.linux_5_15.nct6687d
linuxKernel.packages.linux_5_15_hardened.nct6687d
linuxKernel.packages.linux_5_4.nct6687d
linuxKernel.packages.linux_6_1.nct6687d
linuxKernel.packages.linux_6_11.nct6687d
linuxKernel.packages.linux_6_11_hardened.nct6687d
linuxKernel.packages.linux_6_12.nct6687d
linuxKernel.packages.linux_6_1_hardened.nct6687d
linuxKernel.packages.linux_6_6.nct6687d
linuxKernel.packages.linux_hardened.nct6687d (linuxKernel.packages.linux_6_6_hardened.nct6687d)
linuxKernel.packages.linux_latest_libre.nct6687d
linuxKernel.packages.linux_libre.nct6687d
linuxKernel.packages.linux_xanmod.nct6687d
linuxKernel.packages.linux_xanmod_latest.nct6687d (linuxKernel.packages.linux_xanmod_stable.nct6687d)
linuxKernel.packages.linux_zen.nct6687d

Maintainer pings
cc @Atemu for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@JohnRTitor did you test this on hardware?

No, I probably don't have the hardware (do you know if it works on Gigabyte B650M? I am struggling to get sensors working there)
Anyways, my rule of thumb for kernel module is, we can't test all of them, so if it fixes the build merge the update, keeping them out of date, just makes them not buildable on newer kernels

I'd rather you didn't merge PRs for kernel modules that you cannot even verify basic functionality of. If nobody is around to do such basic QA on a kernel module (or any other package for that matter), that package should either be removed or at the very least not be changed as to not break it.
I'd also rather you didn't signal approval on PRs when you have done no QA whatsoever. (There is no diff worth approving of in @r-ryantm PRs; they're trivial and almost guaranteed to be correct code-wise.)
I'm going to merge this when I get around to testing it on my machine. There is no urgency in updating this package.

I'd rather you didn't merge PRs for kernel modules

Exactly, I just ran a Nixpkgs-review, that's why I "approved" but did not merge this. (Was waiting for a maintainer response)

@r-ryantm runs nixpkgs-review itself; it's in the OP.
@ofBorg build linuxPackages_lqx.nct6687d

error: unused option: SCHED_CLASS_EXT

which is enabled by default on kernels 6.12 and + on Nixpkgs.

Ah, so the entire kernel is broken; safe to ignore then.

zen is working fine, but lqx isn't, does lqx mess around with SCHED_CLASS_EXT implementation?
CC @thiagokokada @@JerrySM64

kernel module for zen compiles fine, but for lqx isn't, does lqx mess around with SCHED_CLASS_EXT implementation?
CC @thiagokokada @@JerrySM64

It is very likely, lqx does very heavy patching to the kernel (while they share the same sources, zen doesn't enable most of the bigger patches so it is much closer to vanilla).


I tried your autoaugment policies to my image-classification learning(imagenet-pretrained fine tuning).

Hi, @DeepVoltaire
I tried your autoaugment policies to my image-classification learning(imagenet-pretrained fine tuning).
But, accuracy is not good than default augmentation.
What's wrong to me?
Autoaugmentation is not suitable for transfer learning or finetuning?
Thanks at any rate.

@bemoregt
It seems that you are fine-tuning an ImageNet-pretrained model on ImageNet dataset. But AutoAugment is never validated on transfer learning situations. Only training from scratch.
I've done training from scratch, and this repository's implementation indeed outperforms the baseline if trained from scratch.
Possibly, you need longer epochs to train, or just use AutoAugment when you train from scratch.


Remove generate_get_config_cmd, pre_generate_ceph_cmd

Looks like this is dead code as referenced in the following issue:
https://github.com/stackhpc/ansible-collection-cephadm/issues/48

Thanks @jcmdln


[Bug]: Unable to use with eslint 9.x

Is there an existing issue for this?

[X] I have searched the existing issues and my issue is unique
[X] My issue appears in the command-line and not only in the text editor

Description Overview

eslint-plugin-react v7.34.1 only works with older versions of eslint (3-8). The current version is 9.3.0

npm init
npm i eslint -D
npm i eslint-plugin-react -D

Everywhere. This is a new project.

The plugin isn't marked to be compatible with future versions of eslint after 8.x. Eslint is currently at version 9.3
newproject git:(master) npm i eslint-plugin-react -D
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving<EMAIL_ADDRESS>npm error Found<EMAIL_ADDRESS>npm error node_modules/eslint
npm error   dev<EMAIL_ADDRESS>from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8" from<EMAIL_ADDRESS>npm error node_modules/eslint-plugin-react
npm error   dev eslint-plugin-react@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/lewismoten/.npm/_logs/2024-05-22T05_46_15_548Z-eresolve-report.txt

npm error A complete log of this run can be found in: /Users/lewismoten/.npm/_logs/2024-05-22T05_46_15_548Z-debug-0.log

npm i eslint-plugin-react -D
Expected Behavior

The plugin should have installed and appear as a devDependency in the package.json file.

  "devDependencies": {
    "eslint": "^9.3.0",
    "eslint-plugin-react": "^7.34.1"
  }

eslint-plugin-react version
v7.34.1
eslint version
v9.3.0
node version
v22.2.0

It's not a bug; we're not compatible with eslint 9 and you shouldn't upgrade yet.
Duplicate of #3699.


Two errors plus workaround

Traceback (most recent call last):
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_modal.py", line 608, in modal
    self.exit_modal(event, context)
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_modal.py", line 924, in exit_modal
    self.call_tool(event, False, context)
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_modal.py", line 712, in call_tool
    build_preview=self.draw_preview,
  File "/home/r2d2/MyApps/blender-3.6.1-linux-x64/3.6/scripts/modules/bpy_types.py", line 855, in __getattribute__
    return super().__getattribute__(attr)
AttributeError: 'VIEW3D_OP_SprytileModalTool' object has no attribute 'draw_preview'

Traceback (most recent call last):
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_gui.py", line 205, in modal
    ret_val = self.handle_ui(context, event)
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_gui.py", line 489, in handle_ui
    tilegrid.tile_selection[0] = sel_min.x
TypeError: expected an int type
Error: Python: Traceback (most recent call last):
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_gui.py", line 205, in modal
    ret_val = self.handle_ui(context, event)
  File "/home/r2d2/.config/blender/3.6/scripts/addons/sprytile-addon-master/sprytile_gui.py", line 489, in handle_ui
    tilegrid.tile_selection[0] = sel_min.x
TypeError: expected an int type

The issue I've found is blender outputting floats: <Vector (25.0000, 16.0000)> when it's supposed to be an int.
The workaround is:
sprytile_gui.py:
                tilegrid.tile_selection[1] = int(sel_min.y)
                tilegrid.tile_selection[2] = (int(sel_max.x) - int(sel_min.x)) + 1
                tilegrid.tile_selection[3] = (int(sel_max.y) - int(sel_min.y)) + 1

and
        context.scene.sprytile_ui.palette_pos[0] = int(display_offset.x)
        context.scene.sprytile_ui.palette_pos[1] = int(display_offset.y)

That seems to fix both issues but also messes with the padding settings. My assumption is that blender forwards the .000 values from the ui. But I haven't found that part.

Hmm looks like the padding could be another issue. I've removed the workarounds and the padding issue is still there.

I just realized that I had the version from: https://github.com/belzecue/ReSprytile
This version doesn't seem to have the issue.


where is login in pycharm Refact.ai plugin?

I install the plugin in pycharm and it shows on sidebar, but I cannot find where to log in and trigger any conversation.

It should pop-up automatically in the lower right corner repeatedly...
Which version of PyCharm and Refact.ai are you using?

I think this is fixed in the latest JB version.
In the previous version you could find login in status bar, and settings. In the new version you also have it in the side panel.

Confirmed -- that's fixed. Reopen if any more problems!

Thanks, I see your update notification and it's fixed. By the way, I confirm my pycharm is the latest version(2023.1.2 built on May, 17th, 2023)


Heroku database rather than RDS

Has anyone found a way to use Postgrest with a Heroku PostgreSQL database?

Postgrest uses database roles to manage access/security and since heroku does not allow multiple users https://devcenter.heroku.com/articles/heroku-postgresql#connection-permissions if you expose it directly with postgrest, api users will have the same level of access as your db admin users, i.e. not possible, unless you put some kind of proxy in front and manage the security yourself.
PS: this issue and the other one you submitted are more like questions then issues which is probably best to submit in the chat room https://gitter.im/begriffs/postgrest

@ruslantalpa - How often do people search Gitter's history? I've always used Github issues, even for questions, as I always try to search the Github repo for the answer before asking a question.

i'm not sure, maybe you are right, there is no hard rule/correct way.
My comment was more based on this logic (although not necessarily correct)

since it's neither an issue/bug/feature request, it's more of a question on how to do a certain thing, as such, the task/question is not very well defined, so it's more of an exploration, a situation where a interactive discussion is better.
managing issues (although relatively easy) is still a small chore and exploratory questions like this imo add a bit of clutter, though i agree that some times, having them here might prevent the same question popping up again ... so ... i don't know :)

maybe take my previous comment as an alternative to issues.

@ruslantalpa - Traditionally, I see Github issues (as it is an issue for the person posting it as explained by one of my friends at Github) are labeled as questions, bugs, features, etc. Maybe there's a tool to automate that step.

By the way, I think that the Heroku database now allows you to create multiple roles.

Postgres manages database access permissions using the concept of roles. Heroku Postgres provides a management layer around these roles called credentials. Each credential corresponds to a different Postgres role and has a distinct set of database permissions.

https://devcenter.heroku.com/articles/heroku-postgresql-credentials
This might make Heroku pg as feasible as RDS for postgrest apis.


Pass command to Segment API

Currently if you call Segment::track for example, it goes nowhere, but the command is actually on the segmentio/analytics-php command.

@GrahamCampbell any clever ways of doing this? I think we need to extend the Analytics class, call static::init and use that as an alias?

I have this working now, except that the config still isn't being picked up. :disappointed:


Fix incorrect usages of org.mockito.internal

Hey! I saw you were depending on several org.mockito.internal classes. As we (the Mockito core developers) do not guarantee backwards compatibility on these classes, I converted them for you to the equivalent public API. Probably your IDE was suggesting the wrong import upon autocompletion.

Coverage remained the same at 84.586% when pulling 1b062ca57e75d9ac8c5ab4f477fbaa6c0c0a9c66 on TimvdLippe:mockito-internal into d5c1ff12ca51b50df1f2e6d33395bffeaf8f3c71 on shardingjdbc:master.

Thank you for reminder and  the pull request. We will pay attention to avoid to use mockito internal API in future.


runtime: SIGSEGV in garbage collector sweeping

What version of Go are you using (go version)?

$ go version
go version go1.21.0 linux/amd64

Does this issue reproduce with the latest release?
Not sure, it happened once on production.
We did not yet encounter it during our test runs.
What operating system and processor architecture are you using (go env)?
The executable is build on a system with these details:
go env Output
$ go env
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/supervisor/.cache/go-build'
GOENV='/home/supervisor/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/supervisor/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/supervisor/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/go-1.21'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/go-1.21/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.0'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build559569511=/tmp/go-build -gno-record-gcc-switches'

What did you do?
We have an executable that runs as a daemon on Debian12 machines.
These machines are deployed in office networks of our customers.
Usually they run for a couple of hours and are shutdown afterwards.
We noticed a crash of our service on one of the systems and investigated it.
It seems like a crash in the garbage collector:
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: SIGSEGV: segmentation violation
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: PC=0x42abb2 m=11 sigcode=128
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: goroutine 0 [idle]:
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.(*sweepLocked).sweep(0x0?, 0x0)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/mgcsweep.go:552 +0x132 fp=0x7f816bffeb70 sp=0x7f816bffea68 pc=0x42abb2
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.(*mcentral).uncacheSpan(0x0?, 0x0?)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/mcentral.go:228 +0x98 fp=0x7f816bffeb98 sp=0x7f816bffeb70 pc=0x41bff8
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.(*mcache).releaseAll(0x7f81d7bed108)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/mcache.go:291 +0x13c fp=0x7f816bffec00 sp=0x7f816bffeb98 pc=0x41ba5c
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.(*mcache).prepareForSweep(0x7f81d7bed108)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/mcache.go:328 +0x35 fp=0x7f816bffec28 sp=0x7f816bffec00 pc=0x41bb55
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.acquirep(0xc000030000)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/proc.go:5334 +0x26 fp=0x7f816bffec68 sp=0x7f816bffec28 pc=0x44a666
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.stopm()
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/proc.go:2537 +0xb5 fp=0x7f816bffec98 sp=0x7f816bffec68 pc=0x443db5
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.findRunnable()
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/proc.go:3229 +0xb9c fp=0x7f816bffeda8 sp=0x7f816bffec98 pc=0x4456bc
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.schedule()
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/proc.go:3582 +0xb1 fp=0x7f816bffede0 sp=0x7f816bffeda8 pc=0x4464b1
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.park_m(0xc00007c000?)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/proc.go:3745 +0x11f fp=0x7f816bffee28 sp=0x7f816bffede0 pc=0x4469bf
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.mcall()
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/asm_amd64.s:458 +0x4e fp=0x7f816bffee40 sp=0x7f816bffee28 pc=0x470f0e
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: goroutine 1 [chan receive, 14 minutes]:
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]: runtime.gopark(0xc000218268?, 0xc0003b1e20?, 0x0?, 0x0?, 0xc0002ba860?)
Nov 10 14:06:44 fakemachine exmg-encoder-daemon[642]:         /usr/lib/go-1.21/src/runtime/proc.go:398 +0xce fp=0xc000599df0 sp=0xc000599dd0 pc=0x43ffee
...

The full stack traces can be seen in this log file:
stack.log
What did you expect to see?
I'd expect either an error which indicates that our code did something wrong, or no crash at all.
I also found this issue, which points at exactly the same line of code (in an older version of golang). But unfortunately that was never resolved.
The problem is that its very hard to reproduce.
We have multiple test machines here, running exactly the same software on exactly the same hardware, but have not seen the issue there.
To me this looks like an issue in the garbage collector code of golang, but I'm not an expert on that topic so I could be completely wrong. Any pointers on how I can further investigate this would be appreciated.
Thanks

Could you try go 1.21.4? Also, having a reproducible example would help with investigating the issue.


cjose / jansson dependency issue - Enterprise Linux 7 (EL7)

Request you to verify this before closing the case. Removing the jansson package and trying to install it as a dependency with cjose EL7_Centos rpm doesnt work.
Please see this -
Red Hat Enterprise Linux Server release 7.4 (Maipo)
binaries]# rpm -qa | grep -i jansson
jansson-2.10-1.el7.x86_64
binaries]# yum remove jansson
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package jansson.x86_64 0:2.10-1.el7 will be erased
--> Finished Dependency Resolution
Removed:
jansson.x86_64 0:2.10-1.el7
Dependency Removed:
NetworkManager.x86_64 1:1.8.0-9.el7                                                   NetworkManager-adsl.x86_64 1:1.8.0-9.el7
binaries]# rpm -qa | grep -i jansson
binaries]#
binaries]# yum localinstall cjose-0.5.1-1.el7.centos.x86_64.rpm
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Examining cjose-0.5.1-1.el7.centos.x86_64.rpm: cjose-0.5.1-1.el7.centos.x86_64
Marking cjose-0.5.1-1.el7.centos.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package cjose.x86_64 0:0.5.1-1.el7.centos will be installed
--> Processing Dependency: pkgconfig(jansson) >= 2.3 for package: cjose-0.5.1-1.el7.centos.x86_64
--> Finished Dependency Resolution
Error: Package: cjose-0.5.1-1.el7.centos.x86_64 (/cjose-0.5.1-1.el7.centos.x86_64)
Requires: pkgconfig(jansson) >= 2.3

I'm seeing the same issue as well, and have tried the step mentioned above of removing the jansson package first. I see this was closed a day later without response, is there a way to resolve this?

consistency is the key here:
yum remove jansson
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/jansson-2.10-1.el7.x86_64.rpm
yum localinstall -y ~/jansson-2.10-1.el7.x86_64.rpm
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/jansson-devel-2.10-1.el7.x86_64.rpm
yum localinstall -y ~/jansson-devel-2.10-1.el7.x86_64.rpm
wget https://github.com/zmartzone/mod_auth_openidc/releases/download/v2.3.0/cjose-0.5.1-1.el7.centos.x86_64.rpm
yum localinstall -y ~/cjose-0.5.1-1.el7.centos.x86_64.rpm
wget https://github.com/zmartzone/mod_auth_openidc/releases/download/v2.3.7/mod_auth_openidc-2.3.8-1.el7.x86_64.rpm
yum localinstall -y ~/mod_auth_openidc-2.3.8-1.el7.x86_64.rpm

Ok many thanks @zandbelt


Invalid Calibration, please check your config

Checklist

[X] I have updated the integration to the latest version available
[X] I have checked if the problem is already reported

The problem
After Update to new home assistant core 2024.6 and also updating the addon to latest version. The Card only shows: Invalid Calibration, please check your config. Readding the entity or completly reloading the integration via hacs does not help.
What version of an integration has described problem?
2024.06.1
What was the last working version of an integration?
No response
What vacuum model do you have problems with?
Hyper/Valetudo
Please firmware installed on your Vacuum.
latest from februrary
What type of platform you use?
VEMLinux (Virtual Machine) such as Proxmox, VMWare, etc.
What version of Home Assistant do you use?
core-2024.6.0
What type of installation are you running?
Home Assistant Supervised
Camera's settings.
No response
Logs or Errors shown in the HA snapshots (please enable the Debug Mode)
raceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 941, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1289, in async_device_update
    await self.async_update()
  File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 428, in async_update
    pil_img = await self.hass.async_create_task(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/valetudo_vacuum_camera/camera_processing.py", line 192, in run_async_process_valetudo_data
    images = await gather(*tasks)
             ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/valetudo_vacuum_camera/camera_processing.py", line 170, in process_valetudo_data
    result = loop.run_until_complete(
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 685, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/config/custom_components/valetudo_vacuum_camera/camera_processing.py", line 68, in async_process_valetudo_data
    self._map_handler.get_calibration_data()
  File "/config/custom_components/valetudo_vacuum_camera/valetudo/hypfer/image_handler.py", line 436, in get_calibration_data
    return self.imu.calibration_points()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: ImageUtils.calibration_points() missing 1 required positional argument: 'rotation_angle'

Additional information
No response

Also this failure:
Logger: homeassistant.util.loop
Quelle: util/loop.py:84
Erstmals aufgetreten: 22:00:09 (51 Vorkommnisse)
Zuletzt protokolliert: 22:23:02
Detected blocking call to open inside the event loop by custom integration 'valetudo_vacuum_camera' at custom_components/valetudo_vacuum_camera/utils/users_data.py, line 107: with open(file_path) as file: (offender: /config/custom_components/valetudo_vacuum_camera/utils/users_data.py, line 107: with open(file_path) as file:), please create a bug report at https://github.com/sca075/valetudo_vacuum_camera/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 680, in async_handle_interval_callback self.config_entry.async_create_background_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1164, in async_create_background_task task = hass.async_create_background_task(target, name, eager_start) File "/usr/src/homeassistant/homeassistant/core.py", line 860, in async_create_background_task task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1050, in _async_update_entity_states await entity.async_update_ha_state(True) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 941, in async_update_ha_state await self.async_device_update() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1289, in async_device_update await self.async_update() File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 345, in async_update self._shared.user_language = await async_get_active_user_language(self.hass) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 149, in async_get_active_user_language active_user_id = await async_find_last_logged_in_user(hass) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 107, in async_find_last_logged_in_user with open(file_path) as file:
Detected blocking call to open inside the event loop by custom integration 'valetudo_vacuum_camera' at custom_components/valetudo_vacuum_camera/utils/users_data.py, line 160: with open(file_path) as file: (offender: /config/custom_components/valetudo_vacuum_camera/utils/users_data.py, line 160: with open(file_path) as file:), please create a bug report at https://github.com/sca075/valetudo_vacuum_camera/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 680, in async_handle_interval_callback self.config_entry.async_create_background_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1164, in async_create_background_task task = hass.async_create_background_task(target, name, eager_start) File "/usr/src/homeassistant/homeassistant/core.py", line 860, in async_create_background_task task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 1050, in _async_update_entity_states await entity.async_update_ha_state(True) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 941, in async_update_ha_state await self.async_device_update() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1289, in async_device_update await self.async_update() File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 345, in async_update self._shared.user_language = await async_get_active_user_language(self.hass) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 160, in async_get_active_user_language with open(file_path) as file:
Detected blocking call to open inside the event loop by custom integration 'valetudo_vacuum_camera' at custom_components/valetudo_vacuum_camera/utils/users_data.py, line 29: with open(file_path) as file: (offender: /config/custom_components/valetudo_vacuum_camera/utils/users_data.py, line 29: with open(file_path) as file:), please create a bug report at https://github.com/sca075/valetudo_vacuum_camera/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle resp = await handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware response = await handler(request) File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle result = await handler(request, **request.match_info) File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin return await func(self, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 262, in post return await super().post(request) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 70, in wrapper return await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 77, in post return await self._post_impl(request, data) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 84, in _post_impl result = await self._flow_mgr.async_init( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 333, in async_init flow = await self.async_create_flow(handler, context=context, data=data) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2543, in async_create_flow return handler.async_get_options_flow(entry) File "/config/custom_components/valetudo_vacuum_camera/config_flow.py", line 165, in async_get_options_flow return OptionsFlowHandler(config_entry) File "/config/custom_components/valetudo_vacuum_camera/config_flow.py", line 176, in init self.rooms_count = get_rooms_count(self.file_name) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 29, in get_rooms_count with open(file_path) as file:
Detected blocking call to open inside the event loop by custom integration 'valetudo_vacuum_camera' at custom_components/valetudo_vacuum_camera/utils/users_data.py, line 107: with open(file_path) as file: (offender: /config/custom_components/valetudo_vacuum_camera/utils/users_data.py, line 107: with open(file_path) as file:), please create a bug report at https://github.com/sca075/valetudo_vacuum_camera/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle resp = await handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware response = await handler(request) File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle result = await handler(request, **request.match_info) File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin return await func(self, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 222, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 70, in wrapper return await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 122, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 368, in async_configure result = await self._async_configure(flow_id, user_input) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 414, in _async_configure result = await self._async_handle_step( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 572, in async_handle_step result = await self.async_finish_flow(flow, result.copy()) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1403, in async_finish_flow await self.config_entries.async_add(entry) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1708, in async_add await self.async_setup(entry.entry_id) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1819, in async_setup await entry.async_setup(self.hass) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/valetudo_vacuum_camera/init.py", line 261, in async_setup_entry hass.async_create_task( File "/usr/src/homeassistant/homeassistant/core.py", line 806, in async_create_task return self.async_create_task_internal(target, name, eager_start) File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2055, in async_forward_entry_setup return await self._async_forward_entry_setup(entry, domain, True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2081, in _async_forward_entry_setup await entry.async_setup(self.hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/camera/init.py", line 461, in async_setup_entry return await component.async_setup_entry(entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 196, in async_setup_entry return await self._platforms[key].async_setup_entry(config_entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 333, in async_setup_entry return await self._async_setup_platform(async_create_setup_awaitable) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 363, in async_setup_platform awaitable = create_eager_task(awaitable, loop=hass.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 89, in async_setup_entry async_add_entities(camera, update_before_add=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 515, in async_schedule_add_entities_for_entry task = self.config_entry.async_create_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1134, in async_create_task task = hass.async_create_task_internal( File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 649, in async_add_entities await add_func(coros, entities, timeout) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 555, in async_add_and_update_entities tasks = [create_eager_task(coro, loop=self.hass.loop) for coro in coros] File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 729, in _async_add_entity await entity.async_device_update(warning=False) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1289, in async_device_update await self.async_update() File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 345, in async_update self._shared.user_language = await async_get_active_user_language(self.hass) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 149, in async_get_active_user_language active_user_id = await async_find_last_logged_in_user(hass) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 107, in async_find_last_logged_in_user with open(file_path) as file:
Detected blocking call to open inside the event loop by custom integration 'valetudo_vacuum_camera' at custom_components/valetudo_vacuum_camera/utils/users_data.py, line 160: with open(file_path) as file: (offender: /config/custom_components/valetudo_vacuum_camera/utils/users_data.py, line 160: with open(file_path) as file:), please create a bug report at https://github.com/sca075/valetudo_vacuum_camera/issues Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/usr/src/homeassistant/homeassistant/main.py", line 223, in  sys.exit(main()) File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main exit_code = runner.run(runtime_conf) File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run return loop.run_until_complete(setup_and_run_hass(runtime_config)) File "/usr/local/lib/python3.12/asyncio/base_events.py", line 672, in run_until_complete self.run_forever() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 639, in run_forever self._run_once() File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1988, in _run_once handle._run() File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run self._context.run(self._callback, *self._args) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request resp = await request_handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 543, in _handle resp = await handler(request) File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 114, in impl return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 85, in ban_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware return await handler(request) File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware response = await handler(request) File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle result = await handler(request, **request.match_info) File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin return await func(self, request, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 222, in post return await super().post(request, flow_id) File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 70, in wrapper return await method(view, request, data, *args, **kwargs) File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 122, in post result = await self._flow_mgr.async_configure(flow_id, data) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 368, in async_configure result = await self._async_configure(flow_id, user_input) File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 414, in _async_configure result = await self._async_handle_step( File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 572, in async_handle_step result = await self.async_finish_flow(flow, result.copy()) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1403, in async_finish_flow await self.config_entries.async_add(entry) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1708, in async_add await self.async_setup(entry.entry_id) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1819, in async_setup await entry.async_setup(self.hass) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/config/custom_components/valetudo_vacuum_camera/init.py", line 261, in async_setup_entry hass.async_create_task( File "/usr/src/homeassistant/homeassistant/core.py", line 806, in async_create_task return self.async_create_task_internal(target, name, eager_start) File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2055, in async_forward_entry_setup return await self._async_forward_entry_setup(entry, domain, True) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2081, in _async_forward_entry_setup await entry.async_setup(self.hass, integration=integration) File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) File "/usr/src/homeassistant/homeassistant/components/camera/init.py", line 461, in async_setup_entry return await component.async_setup_entry(entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 196, in async_setup_entry return await self._platforms[key].async_setup_entry(config_entry) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 333, in async_setup_entry return await self._async_setup_platform(async_create_setup_awaitable) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 363, in async_setup_platform awaitable = create_eager_task(awaitable, loop=hass.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 89, in async_setup_entry async_add_entities(camera, update_before_add=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 515, in async_schedule_add_entities_for_entry task = self.config_entry.async_create_task( File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1134, in async_create_task task = hass.async_create_task_internal( File "/usr/src/homeassistant/homeassistant/core.py", line 828, in async_create_task_internal task = create_eager_task(target, name=name, loop=self.loop) File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 649, in async_add_entities await add_func(coros, entities, timeout) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 555, in async_add_and_update_entities tasks = [create_eager_task(coro, loop=self.hass.loop) for coro in coros] File "/usr/src/homeassistant/homeassistant/util/async.py", line 37, in create_eager_task return Task(coro, loop=loop, name=name, eager_start=True) File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 729, in _async_add_entity await entity.async_device_update(warning=False) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1289, in async_device_update await self.async_update() File "/config/custom_components/valetudo_vacuum_camera/camera.py", line 345, in async_update self._shared.user_language = await async_get_active_user_language(self.hass) File "/config/custom_components/valetudo_vacuum_camera/utils/users_data.py", line 160, in async_get_active_user_language with open(file_path) as file:

Will check it right away thanks a lot

@Sn00kiT I think I know what happened, and I really apologise for it. I'm going to add this to the 2024.06.1, will inform you when ready.

@Sn00kiT I think I know what happened, and I really apologise for it. I'm going to add this to the 2024.06.1, will inform you when ready.

@Sn00kiT I think I know what happened, and I really apologise for it. I'm going to add this to the 2024.06.1, will inform you when ready.

No apologies needed. You are makin a great integration and a much better one then the other ones available! Thanks for your effort and your great work!

Guys I just updated the version about the story with the user_data.py I tested it on the py but I have no remote access to the VM so if the issue persist please let me arrive at home and promise will fix it right away.

Issue is fixed in 2026.06.2 for me, thanks!

@Sn00kiT I'm pretty sure to know where is the problem, thank you once again for the logs please see also the report of the same issue #176

Gentlemens, I just released a beta version 2024.06.3b1 in order to attempt to fix https://github.com/sca075/valetudo_vacuum_camera/issues/175#issuecomment-2150913201
@Sn00kiT if you would be so kind to test it and confirm would be really nice form HACS with the beta release enabled should be available.

Gentlemens, I just released a beta version 2024.06.3b1 in order to attempt to fix #175 (comment) @Sn00kiT if you would be so kind to test it and confirm would be really nice form HACS with the beta release enabled should be available.

Works again like a charm! Thanks once again and also for your quick response!!!


Understanding how to present the user with the ng-message

I'm trying to present the user with the error messages below the input fields, just as they do with the bootstrap schema form. But I'm unable to understand this. I can see that we have something called sf-messages on the elements, but how do I populate them?

They will populate just like the bootstrap ones do, there have just been changes in the way AM handles them so I need to do some updates, but the builder essentially uses sf-messages to append the block to each element so we only have to edit it in one spot.

    function sfMessagesBuilder(args) {
      var messagesDiv = args.fieldFrag.querySelector('[sf-messages]');
      if (messagesDiv && sfMessagesNode) {
        var child = sfMessagesNode.cloneNode();
        messagesDiv.appendChild(child);
      }
    };

This is the builder function your talking about?

Yes that's it, but it adds in code that David put in to override the way AM works by default to keep it compatible. There are LOTS of bugs in AM still, so it is hard to implement, however it looks to be starting to stabilise at least api-wise so I will start working on it more very soon.

made some test and changes in the ng-message branch it works (needs work) but needs angular dependencies to be 1.4.8


MicroWin: Cannot remove OS package

Describe the bug
When I created a MicroWin ISO the logs indicate that some of the OS package removals are failing.
Let me know if any other info would be helpful.
Log
oscdimg.exe on system: True                                                                                File path C:\Users\spoga\Downloads\Win11_23H2_English_x64v2.iso                                                         You have enough space for this operation.                                                                               Mounting Iso. Please wait.                                                                                Done mounting Iso MSFT_DiskImage (ImagePath = "C:\Users\spoga\Downloads\Win11_23H2_Eng..., StorageType = 1)             Iso mounted to 'E'                                                                                Setting up mount dir and scratch dirs                                                                                Mounting Iso. Please wait.                                                                                Done setting up mount dir and scratch dirs                                                                              Scratch dir is Scratch\Scrach                                                                                Image dir is Scratch\micro                                                                                Copying Windows image. This will take awhile, please don't use UI or cancel this step!                                  Copy 1031(s) from E: to Scratch\micro                                                                                Copy complete! Total Time: 0m13s                                                                                Getting image information Scratch\micro\sources\install.wim                                                             Finding suitable Pro edition. This can take some time. Do note that this is an automatic process that might not select the edition you want.                                                                                Selected value '6 : Windows 11 Pro'.....                                                                                Done reading and unpacking ISO                                                                                *********************************                                                                                Check the UI for further steps!!!                                                                                No file name for the target image was specified                                                                         No file name for the target image was specified                                                                         Target ISO location: C:\Users\spoga\Downloads\microwin.iso                                                              Index chosen: '6' from 6 : Windows 11 Pro                                                                               Mounting Windows image. This may take a while.                                                                          Mounting complete! Performing removal of applications...                                                                Remove Features from the image                                                                                You can re-enable the disabled features at any time, using either Windows Update or the SxS folder in <installation media>\Sources.                                                                                Removing features complete!                                                                                [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.
[INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               [INFO] In Your local takeown expects 'Y' as a Yes answer.                                                               Removal complete!                                                                                Create unattend.xml                                                                                Done Create unattend.xml
Copy unattend.xml file into the ISO
Done Copy unattend.xml
Create FirstRun
Done create FirstRun
Copy FirstRun.ps1 into the ISO
Done copy FirstRun.ps1
Copy link to winutil.ps1 into the ISO
Copy checkinstall.cmd into the ISO
Done copy checkinstall.cmd
Creating a directory that allows to bypass Wifi setup
Loading registry
Disabling Teams
Done disabling Teams
Bypassing system requirements (system image)
Setting all services to start manually
Enabling Local Accounts on OOBE
Disabling Sponsored Apps
Done removing Sponsored Apps
Disabling Reserved Storage
Changing theme to dark. This only works on Activated Windows
Unmounting Registry...
Cleaning up image...
Cleanup complete.
Unmounting image...
Exporting image into Scratch\micro\sources\install2.wim
Remove old 'Scratch\micro\sources\install.wim' and rename Scratch\micro\sources\install2.wim
Invoke-WPFMicrowin : An unexpected error occurred: Cannot rename the specified target, because it represents a path or
device name.
At line:3692 char:24
+         "WPFMicrowin" {Invoke-WPFMicrowin}
+                        ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Invoke-WPFMicrowin

Unmounting Registry...
ERROR: The parameter is incorrect.
ERROR: The parameter is incorrect.
ERROR: The parameter is incorrect.
ERROR: The parameter is incorrect.
ERROR: The parameter is incorrect.
Unmounting image...
Dismount-WindowsImage : The request is not supported.
At line:4980 char:9
+         Dismount-WindowsImage -Path $scratchDir -Save
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Dismount-WindowsImage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.DismountWindowsImageCommand

Creating ISO image
[INFO] Using oscdimg.exe from: oscdimg.exe

OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2012. All rights reserved.
Licensed only for producing Microsoft authorized content.

Scanning source tree (500 files in 43 directories)
Scanning source tree complete (946 files in 86 directories)

Computing directory information complete

Image file is<PHONE_NUMBER> bytes (before optimization)

Writing 946 files in 86 directories to C:\Users\spoga\Downloads\microwin.iso

100% complete

Storage optimization saved 4 files, 24576 bytes (0% of image)

After optimization, image file is<PHONE_NUMBER> bytes
Space saved because of embedding, sparseness or optimization = 24576

Done.
OSCDIMG Error Level : 0

To Reproduce
Steps to reproduce the behavior:

Create MicroWin ISO
View powershell terminal

Expected behavior
Should be able to remove packages succesfully

Not sure if this is related, but when I try to install using this ISO, I got the message "Windows could not collect information for [OSImage] since the specified image file [install.wim] does not exist."

What happens if you don't set up a scratch directory manually and let the script use a folder in %TEMP%?

Didnt realize I had selected a directory, that did remove the write errors and I was able to install succesfully. However the unable to remove messages remain.

However the unable to remove messages remain.

That's normal and doesn't cause any problems with the target image

Gotcha, thanks. Will close the issue.


fix bench command line options

I working for https://github.com/apache/arrow-rs/issues/1660
fix to criterion bench not accepts options
error: Unrecognized option: 'save-baseline'
error: bench failed

https://github.com/bheisler/criterion.rs/issues/193#issuecomment-415740713
Which issue does this PR close?
None
Rationale for this change

not working cargo bench -- --save-baseline tag and cargo bench -- --baseline tag.
What changes are included in this PR?

add bench = false to Cargo.toml [lib]

Is cargo bench --bench benchmarks -- --save-baseline foo a workaround too?

Codecov Report

Merging #1685 (f185b69) into master (19f0ada) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1685   +/-   ##
=======================================
  Coverage   83.11%   83.12%
=======================================
  Files         193      193
  Lines       56177    56177
=======================================
+ Hits        46694    46696    +2
+ Misses       9483     9481    -2

Impacted Files
Coverage Δ

parquet_derive/src/parquet_field.rs
65.98% <0.00%> (ø)

arrow/src/array/transform/mod.rs
87.02% <0.00%> (+0.22%)
:arrow_up:

Continue to review full report at Codecov.

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

Yes, cargo bench --bench some_bench -- --save-baseline tag is working without this PR.
But, too hard to compare all bench result.


Refactor BQM docs for 0.9.x

Codecov Report

Merging #619 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #619   +/-   ##
=======================================
  Coverage   90.79%   90.79%
=======================================
  Files          57       57
  Lines        3910     3910
=======================================
  Hits         3550     3550
  Misses        360      360

Impacted Files
Coverage Δ

dimod/serialization/fileview.py
78.97% <ø> (ø)
:arrow_up:

dimod/bqm/construction.py
100% <ø> (ø)
:arrow_up:

dimod/binary_quadratic_model.py
97.56% <ø> (ø)
:arrow_up:

dimod/core/bqm.py
90.03% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

This is still missing some method docstrings, but the classes and attributes are in there and the structure has been set up.


Can't connect from vscode to localhost jupyter server

Applies To

[ ] Notebooks (.ipynb files)
[X] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Hi bros,
I got a issue, steps to reproduce as below:

Install jupyterlab as tutorial https://research.google.com/colaboratory/local-runtimes.html#:~:text=In Colaboratory%2C click the "Connect,connected to your local runtime.
Copy uri after starting jupyter server (http://localhost:8888/?token=<your_token>)
Install Jupyter extension on vscode
Connect colab runtime to local jupyter server:

Click connect https://gyazo.com/dcd8e4636361213a24dc56e1481efacf
Paste uri link that copied https://gyazo.com/53c9edd93f92abbb48fcc39847f21016

Connect vscode to local jupyter server:

Open vscode -> Ctrl + Shift + P -> Jupyter: Specify Jupyter Server for Connections -> Existing -> paste uri link that copied

Result:
Colab connect runtime to  local jupyter server successfully.
Vscode can't connect local jupyter server.
Thanks in advanced for your help!
VS Code Version
1.68.1(user setup)
Jupyter Extension Version
v2022.6.1001631011
Jupyter logs
jupyter notebook --NotebookApp.allow_origin='https://colab.research.google.com' --port=8888 --NotebookApp.port_retries=0
jupyter_http_over_ws extension initialized. Listening on /http_over_websocket
[W 2022-06-22 21:49:53.045 LabApp] 'allow_origin' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-06-22 21:49:53.045 LabApp] 'port' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-06-22 21:49:53.045 LabApp] 'port_retries' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2022-06-22 21:49:53.045 LabApp] 'port_retries' has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2022-06-22 21:49:53.045 LabApp] JupyterLab extension loaded from C:\Users\MSI GAMING\AppData\Local\Programs\Python\Python38\lib\site-packages\jupyterlab
[I 2022-06-22 21:49:53.045 LabApp] JupyterLab application directory is C:\Users\MSI GAMING\AppData\Local\Programs\Python\Python38\share\jupyter\lab
[I 21:49:53.045 NotebookApp] Serving notebooks from local directory: C:\Users\MSI GAMING\.jupyter
[I 21:49:53.045 NotebookApp] Jupyter Notebook 6.4.12 is running at:
[I 21:49:53.045 NotebookApp] http://localhost:8888/?token=0c35085c94c0f1bf98975d9fe8ecdf9662f5a808f5f487da
[I 21:49:53.045 NotebookApp]  or http://<IP_ADDRESS>:8888/?token=0c35085c94c0f1bf98975d9fe8ecdf9662f5a808f5f487da
[I 21:49:53.045 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 21:49:53.092 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///C:/Users/MSI%20GAMING/AppData/Roaming/jupyter/runtime/nbserver-8248-open.html
    Or copy and paste one of these URLs:
        http://localhost:8888/?token=0c35085c94c0f1bf98975d9fe8ecdf9662f5a808f5f487da
     or http://<IP_ADDRESS>:8888/?token=0c35085c94c0f1bf98975d9fe8ecdf9662f5a808f5f487da
[W 21:50:07.022 NotebookApp] Forbidden
[W 21:50:07.022 NotebookApp] 403 GET /api/kernels?1655909407020 (<IP_ADDRESS>) 1.000000ms referer=None
[W 21:50:19.775 NotebookApp] Forbidden
[W 21:50:19.776 NotebookApp] 403 GET /api/kernelspecs?1655909419773 (<IP_ADDRESS>) 1.010000ms referer=None
[W 21:50:36.673 NotebookApp] Forbidden
[W 21:50:39.017 NotebookApp] 403 GET /api/sessions?1655909436673 (<IP_ADDRESS>) 2344.740000ms referer=None

Coding Language and Runtime Version
Python 3.8.8 64-bit
Language Extension Version (if applicable)
v2022.8.0
Anaconda Version (if applicable)
Pip 22.1.2 instead
Running Jupyter locally or remotely?
Local

Thanks for the issue.
Which URL did you specify in VS code? It was unclear which URL you're pasting from your description.
It should be this one: http://localhost:8888/?token=0c35085c94c0f1bf98975d9fe8ecdf9662f5a808f5f487da.
If that's the one, can you include the text of the 'jupyter' output tab:

Yes, url is same as you mentioned. I updated issue.
 What does your kernel drop down list?

It's here:

Sorry I meant this UI in VS code:

That is where your remote kernels would show up. They should be under the 'Remote Jupyter Kernels' list. This is what I get for my own machine:

The confusion might be that we also list 'local' kernels in this list too. Where 'local' kernels are kernels creatable from a local python environment.

Sorry, i didn't understand your mean.
Here, my local kernel on vscode:

Yes, thanks.
I can select 'Python 3 (ipykernel)'.
Error 403 on server still exist:

403 on the server is expected. There are requests that are being made without the token. That's actually this issue here:
https://github.com/microsoft/vscode-jupyter/issues/9801

The general problem of 'local' vs 'remote' not being clear is something on our radar though. Some ideas are here:
https://github.com/microsoft/vscode-jupyter/issues/10363
https://github.com/microsoft/vscode-jupyter/issues/10435

#10435 should address this problem.


removeHotSpot  is not working

here's my code, removeHotSpot should have worked but it didn't
var newHotspot = {
        pitch: pitch,
        yaw: yaw,
        cssClass: "custom-hotspot",
        createTooltipFunc: hotspot,
        createTooltipArgs: "New Hotspot",
        isAddInfoEnable: true
    };

    // Add the new hotspot to the viewer
    // viewer.addHotSpot(newHotspot);

    setTimeout(() => {
    viewer.removeHotSpot(newHotspot);
    }, 3000);
    viewer.addHotSpot(newHotspot);

the hotspot added, but after 3sec it should have removed but it didn't

That's because you're using the removeHotSpot function incorrectly. As is stated in the API documentation, the removeHotSpot function takes a hotSpotId string as its argument, but you're passing it an object. You need to include an id attribute in your newHotspot object and set it to a string; you can then call removeHotSpot with that string as the argument to remove the hot spot.

Ohh, Thank you, now it's working.
I had been searching solution since yesterday.
I am using this library in my React project, I think you should have made a different library for React.
yes there is a library called react-pannellum  but that is not giving the support from long-time


Feature/refactor login

run build production main

run build production main

run build production main

run build production main

run build production main

run build production main

run build production main

run build production main


A nested Model can resolve its Factory, but the resolved nested Factory can't resolve its Model

Laravel Version: 8.80.0
PHP Version: 8.1.1 (sail)
Database Driver & Version: MySql Server 8.0 (sail)

Description:
A nested Model can resolve its Factory, but the resolved nested Factory can't resolve its Model.
Model is using its namespace to resolve a factory, but Factory is using only its "baseclass"
and can't resolve its model that is nested in the same way.
Steps To Reproduce:

php artisan make:model User/Profile -f
Run the code snippet

// Model is using its namespace to resolve a factory (the Factory::resolveFactoryName() function actually)
// $factory is an instanceof \App\Database\Factories\User\ProfileFactory
$factory = \App\Models\User\Profile::factory();

// Factory is using only its "baseclass" and can't resolve a model that is nested in the same way
//Error:  Class "App\Profile" not found
$factory->create();

So, I looked into this and managed to solve it although I'm not 100% sure it was intended or not. It does look like a bug but I'm gonna await Taylor's review on this first. See https://github.com/laravel/framework/pull/40616


Badge update

Pull Request Test Coverage Report for Build 28

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

Totals

Change from base Build 25:
0.0%

Covered Lines:
251

Relevant Lines:
251

💛  - Coveralls


Add XML Smart Completion to ReSharper

This PR aims to let XML automatically move to Smart Completion in ReSharper

This is mostly complete, but ReSharper 2023.2 seems to have an issue that just prevents smart completion from working altogether. It works beautifully in 2023.1, but we need to sort out what's going wrong in 2023.2. Also, we should either remove the Settings altogether or give them better names and start using them


Very slow open/close animation

When opening and closing the remodal, the animation takes a very long time to reach the end and the "remodal-is-opened" and "remodal-is-closed" classes aren't added to the containers. If you click inside the modal it kicks in and finishes! Consequenses: When opening this means the modal content remains blurry and when closing it prevents interaction with the parent document since the remodal overlay isn't hidden (until you click somewhere). Can be reproduced in the sample on the remodal homepage.
Chrome 45.0.2454.85 m / Win 7.

until you click somewhere

Until the animation is in progress. I don't see any wrong behavior here, cuz these classes should be added only when the browser tells that the current animation is finished.

I also have the same problem and it's happens only in Chrome and Opera. When I close the modal, I got delay. Sometimes almost 1 second. It's look strange because CSS animation already complete (it's take only 0.3 second) but interaction with page is blocked.
It's look like Chrome na Opera (I think that both based on webkit) have problem with correct detect the end of animation.

I also have this issue since I updated to v1. A delay that seems long ( 1s ) before I can start scrolling again after closing the modal.

Well the animation doesn't finish on its own.. After opening the remodal, the content in the popup remains blurry until you click somewhere in it. And after closing it you can't click or scroll the document for a while (>= 1 sec). You're saying this is correct behaviour??

Commenting out these lines in the default theme css did the trick, although it also did remove the nice transitions.
/*.remodal-overlay.remodal-is-opening,
.remodal-overlay.remodal-is-closing {
-webkit-animation-fill-mode: forwards;
animation-fill-mode: forwards;
}
.remodal-overlay.remodal-is-opening {
-webkit-animation: remodal-overlay-opening-keyframes 0.3s;
animation: remodal-overlay-opening-keyframes 0.3s;
}
.remodal-overlay.remodal-is-closing {
-webkit-animation: remodal-overlay-closing-keyframes 0.3s;
animation: remodal-overlay-closing-keyframes 0.3s;
}*/
/*.remodal.remodal-is-opening,
.remodal.remodal-is-closing {
-webkit-animation-fill-mode: forwards;
animation-fill-mode: forwards;
}
.remodal.remodal-is-opening {
-webkit-animation: remodal-opening-keyframes 0.3s;
animation: remodal-opening-keyframes 0.3s;
}
.remodal.remodal-is-closing {
-webkit-animation: remodal-closing-keyframes 0.3s;
animation: remodal-closing-keyframes 0.3s;
}*/


Support firmware build on travis-ci

Currently Travis-CI only build and executes tests. It would be better if it would also build firmware, just  to verify that it is buildable.

Fixed by Travis-CI Configuration change: 08efc66edb70e4e58e9daa359f7dd0014d1ea132