dev. version not working with mpd

Bug
After a clean install, doing only the needed configuration. After reboot:
May  5 21:50:22 raspberrypi mpd[1775]: exception: failed to open log file "/var/log/mpd/mpd.log" (config line 40): Permission denied
May  5 21:50:22 raspberrypi systemd[1762]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May  5 21:50:22 raspberrypi systemd[1762]: mpd.service: Failed with result 'exit-code'.
May  5 21:50:22 raspberrypi systemd[1762]: Failed to start Music Player Daemon.
What I did
so that the error does not occur anymore:
sudo chmod 777 -R /var/log/mpd
What happened
May  5 21:56:46 raspberrypi mpd[818]: May 05 21:56 : exception: Failed to set group 0: Operation not permitted
May  5 21:56:47 raspberrypi systemd[793]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May  5 21:56:47 raspberrypi systemd[793]: mpd.service: Failed with result 'exit-code'.
May  5 21:56:47 raspberrypi systemd[793]: Failed to start Music Player Daemon.
I expected this to happen
That mpd is working now. But it doesnt
Further information that might help
Got this the second time now (did a new clean install and the same error again)
Further info (mopidy seems to have also problems with iris):
pi@raspberrypi:~ $ journalctl -u mopidy
-- Logs begin at Tue 2020-05-05 21:55:27 BST, end at Tue 2020-05-05 21:58:51 BST. --
May 05 21:55:58 raspberrypi systemd[1]: Starting Mopidy music server...
May 05 21:56:01 raspberrypi systemd[1]: Started Mopidy music server.
May 05 21:56:46 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.main Starting Mopidy 3.0.2
May 05 21:56:46 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.config Loading config from builtin defaults
May 05 21:56:46 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy.conf
May 05 21:56:46 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy-local.conf
May 05 21:56:46 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.config Loading config from file:///etc/mopidy/mopidy.conf
May 05 21:56:46 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.config Loading config from command line options
May 05 21:56:46 raspberrypi mopidy[451]: WARNING  [MainThread] mopidy.config Ignoring config section 'iris' because no matching extension was found
May 05 21:56:46 raspberrypi mopidy[451]: ERROR    [MainThread] mopidy.internal.log Loading logging config '/etc/mopidy/logging.conf' failed. 'formatters'
May 05 21:56:48 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.main Enabled extensions: softwaremixer, mpd, file, m3u, stream, spotify, local, http
May 05 21:56:48 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.main Disabled extensions: none
May 05 21:56:50 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
May 05 21:56:50 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Mixer volume set to 30
May 05 21:56:50 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Starting Mopidy audio
May 05 21:56:51 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend, SpotifyBackend, LocalBackend
May 05 21:56:51 raspberrypi mopidy[451]: INFO     [Audio-2] mopidy.audio.actor Audio output set to "alsasink"
May 05 21:56:53 raspberrypi mopidy[451]: INFO     [SpotifyEventLoop] mopidy_spotify.backend Logged in to Spotify in online mode
May 05 21:56:53 raspberrypi mopidy[451]: INFO     [SpotifyBackend-6] mopidy_spotify.web Logged into Spotify Web API as htpzc
May 05 21:58:51 raspberrypi mopidy[451]: INFO     [SpotifyBackend-6] mopidy_spotify.playlists Refreshed 48 Spotify playlists
May 05 21:58:51 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Starting Mopidy core
May 05 21:58:51 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Starting Mopidy frontends: HttpFrontend, MpdFrontend
May 05 21:58:51 raspberrypi mopidy[451]: INFO     [HttpFrontend-12] mopidy.http.actor HTTP server running at [::ffff:<IP_ADDRESS>]:6680
May 05 21:58:51 raspberrypi mopidy[451]: INFO     [MainThread] mopidy_mpd.actor MPD server running at [::ffff:<IP_ADDRESS>]:6600
May 05 21:58:51 raspberrypi mopidy[451]: INFO     [MainThread] mopidy.commands Starting GLib mainloop
Rebooting - even more errors occure - httpd deamon, mpd, mopidy ... :-(
May  5 22:16:08 raspberrypi systemd[800]: Starting Music Player Daemon...
May  5 22:16:08 raspberrypi systemd[1]: Started Session c2 of user pi.
May  5 22:16:08 raspberrypi systemd[1]: Started Session c1 of user pi.
May  5 22:16:08 raspberrypi systemd[1]: Startup finished in 2.301s (kernel) + 56.834s (userspace) = 59.136s.
May  5 22:16:12 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:14 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
May  5 22:16:18 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:22 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.main Starting Mopidy 3.0.2
May  5 22:16:22 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.config Loading config from builtin defaults
May  5 22:16:22 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy.conf
May  5 22:16:22 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy-local.conf
May  5 22:16:22 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.config Loading config from file:///etc/mopidy/mopidy.conf
May  5 22:16:22 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.config Loading config from command line options
May  5 22:16:22 raspberrypi mopidy[452]: WARNING  [MainThread] mopidy.config Ignoring config section 'iris' because no matching extension was found
May  5 22:16:22 raspberrypi mopidy[452]: ERROR    [MainThread] mopidy.internal.log Loading logging config '/etc/mopidy/logging.conf' failed. 'formatters'
May  5 22:16:23 raspberrypi mpd[823]: May 05 22:16 : exception: Failed to set group 0: Operation not permitted
May  5 22:16:23 raspberrypi systemd[800]: mpd.service: Main process exited, code=exited, status=1/FAILURE
May  5 22:16:23 raspberrypi systemd[800]: mpd.service: Failed with result 'exit-code'.
May  5 22:16:23 raspberrypi systemd[800]: Failed to start Music Player Daemon.
May  5 22:16:23 raspberrypi systemd[800]: Reached target Default.
May  5 22:16:23 raspberrypi systemd[800]: Startup finished in 18.411s.
May  5 22:16:24 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:25 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.main Enabled extensions: stream, http, local, softwaremixer, m3u, mpd, spotify, file
May  5 22:16:25 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.main Disabled extensions: none
May  5 22:16:27 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
May  5 22:16:27 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.commands Mixer volume set to 30
May  5 22:16:27 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.commands Starting Mopidy audio
May  5 22:16:27 raspberrypi mopidy[452]: INFO     [MainThread] mopidy.commands Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend, SpotifyBackend, LocalBackend
May  5 22:16:27 raspberrypi mopidy[452]: INFO     [Audio-2] mopidy.audio.actor Audio output set to "alsasink"
May  5 22:16:30 raspberrypi mopidy[452]: INFO     [SpotifyBackend-6] mopidy_spotify.web Logged into Spotify Web API as htpzc
May  5 22:16:30 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:30 raspberrypi mopidy[452]: INFO     [SpotifyEventLoop] mopidy_spotify.backend Logged in to Spotify in online mode
May  5 22:16:36 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:42 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:48 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:16:51 raspberrypi systemd[1]: phoniebox-idle-watchdog.service: Succeeded.
May  5 22:16:54 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:17:00 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:17:02 raspberrypi CRON[988]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May  5 22:17:06 raspberrypi lighttpd[756]: echo: write error: Broken pipe
May  5 22:17:12 raspberrypi lighttpd[756]: echo: write error: Broken pipe
Software
Base image and version
cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Branch / Release
I did the install with GIT_BRANCH=develop
(i am sure, because i did copy and paste from my notepad++ documentation)
--> wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/develop/scripts/installscripts/buster-install-default.sh;
chmod +x buster-install-default.sh;
GIT_BRANCH=develop
bash ./buster-install-default.sh
But that is the output of (and i am confused now):
cd /home/pi/RPi-Jukebox-RFID/ && git status | head -2
Refresh index: 100% (309/309), done.
On branch master
Your branch is up to date with 'origin/master'.
Hardware
RaspberryPi version
sudo cat /sys/firmware/devicetree/base/model
Raspberry Pi Zero W Rev 1.1p
RFID Reader
HXGCoLtd Keyboard
Soundcard
Bus 001 Device 003: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller

Did you install the Spotify edition?
If yes, then mopidy is used, so your described behavior would be as expected.

But why is mpd started? dont understand the logic behind that? why not just disable the service.
just in my case, booting lasts very long and every unneeded started service (which is just crashing) needs extra time.
And of course, where is mpd started. i just looked in the rc*.d start and kill links, but theres no S01mpd.
Also ther service is disabled.
Who is starting mpd?

One more question (sorry when this is little bit offtopic), but lighttpd seems to be also broken.
May 5 22:16:18 raspberrypi lighttpd[756]: echo: write error: Broken pipe
Webfrontend is running fine, but the iris is not working. Just getting 404 not found when connecting http://...:6680/iris/ -> 404: Not Found
http://...:6680/ -> is working and showing that this is the mopidy web server
Am i right that we have two webservers running? One for the phoniebox frontend and one for the mopidy spotify integration?
How can i turn debugging on for the mopidy web server. Theres no logging saying that 404 not found or anything like that.
Only: May  6 20:20:52 raspberrypi mopidy[496]: INFO     [MpdSession-313] mopidy_mpd.session New MPD connection from [::ffff:<IP_ADDRESS>]:47258

ok, now i understand much better. I need to give everything more time.
Please forget my questions. For now, everything is running, BUT:
I know mopidy needs a long time to start but nearly 2,5 minutes is to long ...
The longest part is the reading of my spotify playlist with 128 seconds
See this:
May 07 21:16:26 raspberrypi mopidy[488]: INFO     [SpotifyEventLoop] mopidy_spotify.backend Logged in to Spotify in online mode
May 07 21:18:34 raspberrypi mopidy[488]: INFO     [SpotifyBackend-6] mopidy_spotify.playlists Refreshed 48 Spotify playlists
You have written that when i scan the library this should be not the problem anymore.
Do you have any suggestions what i can do to fasten things up?
I dont need 30 seconds startup, but till i can start music i have nearly 4 minutes gone. Maybe we can get this to 2 minutes ;-)
Please say me what you need. i am very conform in linux and will do my very best also to make things better if possible.
Thanks in advance.

ok, more information because the local scan is not working:
$ mopidy local scan
Traceback (most recent call last):
File "/usr/local/bin/mopidy", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3191, in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3175, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3204, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 583, in _build_master
ws.require(requires)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Mopidy==2.2.2' distribution was not found and is required by the application

This is the biggest issue with the Spotify edition that it takes a very long time to boot up.
Nevertheless 4 minutes sounds extremely long, but I have no experience with the Pi Zero.

ok, more information because the local scan is not working:
$ mopidy local scan
Traceback (most recent call last):
File "/usr/local/bin/mopidy", line 6, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3191, in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3175, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3204, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 583, in _build_master
ws.require(requires)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 900, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 786, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Mopidy==2.2.2' distribution was not found and is required by the application

That's pretty weird. In your logs above mopidy 3 was found and now mopidy 2 seems to be still used (and python 2).
Please perform the steps in #852 although you said you installed develop.

sorry, between this time i installed also the master branch and executed everything which got listed in #852 .
Everything worked fine except the mopidy local scan

should i reinstall again the developer branch? but there i got the same time problems (except that i dont know if the local scan would work)

Master branch with manual fix #852 was pretty stable recently.
Maybe you should start with a fresh SD card installation, because we don't have a thorough deinstallation process, so you now may have a mixture of services and configurations from master and develop.

i did a fresh complete fresh install.
ok, think i found the problem. the binary seems to be wrong.
Service runs under
mopidy     491     1 18 21:46 ?        00:02:07 /usr/bin/python3 /usr/bin/mopidy
But: $ which mopidy
/usr/local/bin/mopidy
ls -al
usr/bin/mopidy has a symlink to /usr/share/mopidy/mopidy-cmd
i've mv the /usr/bin/mopidy to /usr/bin/mopidy_org and symlinked it to the  /usr/share/mopidy/mopidy-cmd
now the scan works. testing further. give you response when i got more

ok, now i can scan. also i scanned the library through the webfrontend.
Afterwards rebooted. 130 seconds for loading 48 playlists. Same as before.
Now i have on more error message when playing something.
i think i will use the phoniebox for the first time  without the spotify integration.
The waiting time is long, but the instability is not ok (because i have to use the developer version to run it).
when we are in holidays i dont have any notebook to ssh to the pi and check all day long logs.
Of course maybe a pi4 will do this faster, but the battery will also drain faster. So my son has to take the local playback for the first time ;-)
Maybe the next time when this is more stable and maybe more faster.
But i have to say thank you for doing this great project and of course the master branch version without spotify is running realy stable and smooth AND fast.
Thanks

So if this works for you now, you could close the issue.

Thanks @s-martin, this was service as good as it gets!
@htpzc could you close this issue, if it works for you now?


Dead?

Is this project being maintained or dead? Tkx

Not actively developed, accepting PRs and bug fixes.

Thank you!


make stats box realtime

The stats box in the top-right corner looks like:
       Games:    1
Maximum Subs:    0
 Empty Games:    1
  Total Subs:    0
Total Events:    6
       Users:    4

It doesn't seem to be dynamically updated from outside the current browser actions. (i.e.: The values don't get updated when another browser or other client, such as wrk or ab, connects to the server.)

there's something else going on.  I'll take a look tomorrow.  did you
shards update?
On Feb 28, 2017 5:34 PM, "Daniel Huffman"<EMAIL_ADDRESS>wrote:

The stats box in the top-right corner looks like:
Games 1
Maximum Subs 0
Empty Games 1
Total Subs 0
Total Events 6
Users 4
It doesn't seem to be dynamically updated from outside the current browser
actions. (i.e.: The values don't get updated when another browser or other
client, such as wrk or ab, connects to the server.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jasonl99/card_game/issues/17, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABe6GTcQrgECKNpTZPEJIgdPwO--u3IIks5rhKD2gaJpZM4MO-ah
.

I should have read a little closer - wrk or ab won't establish a socket connection; as a result, nothing gets subscribed, so no events occur to trigger an update.  About the only thing that will occur is that extra users (each with a session) will get created and ultimately destroyed in the kemal #get.
I will add a refresh in the master_observer class on load of a game.

Here's firefox and chrome next to each other after a bunch of hits from ab:


Sampled Muzero with the EfficientZero and the stochastic muzero to introduce random events into the continuous action space

Based on how you combined Sampled Muzero with EfficientZero, my latest idea is to combine Sampled Muzero with the EfficientZero and the stochastic muzero to introduce random events into the continuous action space. My question is is it feasible? Looking forward to your answer. Thank you very much!

Based on my analysis, this approach is highly feasible. Expanding the action space (Sampled MuZero), addressing stochasticity (Stochastic MuZero), and enhancing sample efficiency (EfficientZero) represent orthogonal improvements that can be seamlessly integrated. By combining these advancements, the approach is expected to support the modeling of continuous actions and stochastic events while maintaining strong learning efficiency. We are eagerly looking forward to seeing the corresponding implementation and would like to express our sincere gratitude for your valuable contributions. If you have any questions, please feel free to continue the discussion here at any time!


Cannot start full systemd container with lxc driver.

Description of problem:
Cannot start /sbin/init  within the container with lxc driver.
You can start  /sbin/init in docker with the native driver:
docker run  -it -privileged -e "container=docker" ubuntu:init /sbin/init
However, it does not work for the lxc driver:
docker run -it -privileged -e "container=docker"  ubuntu:init  /sbin/init
No response from the output, and the container is not started.
docker version:
Client:
Version:      1.8.0-dev
API version:  1.20
Go version:   go1.4.2
Git commit:   15cb7df-dirty
Built:        Wed Jul 22 07:43:16 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.8.0-dev
API version:  1.20
Go version:   go1.4.2
Git commit:   15cb7df-dirty
Built:        Wed Jul 22 07:43:16 UTC 2015
OS/Arch:      linux/amd64
docker  info:
Containers: 18
Images: 88
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 228
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-15-generic
Operating System: Ubuntu 15.04
CPUs: 1
Total Memory: 976.6 MiB
Name: ubuntu
ID: 6CKH:DHL3:FSVK:NBWN:ZVYE:DIK3:QOQJ:3JHF:3DON:4F42:2LAZ:3KDM
WARNING: No swap limit support
uname -a:
Linux ubuntu 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
How reproducible
100%
Steps to Reproduce:
1.You can start /sbin/init in docker with native driver:
docker -d
docker run -it --privileged -e "container=docker"  ubuntu:init /sbin/init
2.You can't start /sbin/init in docker with lxc driver,there is nothing put out with lxc driver:
docker -d -e lxc
docker run -it --privileged -e "container=docker"  ubuntu:init /sbin/init

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

As notified in our deprecation notice, Docker 1.10.0 will drop support for the LXC exec driver (#17700).
Thank you for the report, I'm now closing this.


Deploy fails for IBMId with some special chars in password

Cluster deploy is failing with unentitled IBMid.

When I check /var/log/cloud-init-was.log on DMgr, this is all I see:

[root@dmgr78bf9fVM log]# cat cloud-init-was.log
Checking at + Fri Jun 18 17:00:49 UTC 2021
Invalid input format.
Uninstalled com.ibm.websphere.ND.v90_9.0.5007.20210301_1241 from the /datadrive/IBM/WebSphere/ND/V9/ directory.
Uninstalled com.ibm.java.jdk.v8_8.0.6026.20210226_0840 from the /datadrive/IBM/WebSphere/ND/V9/ directory.
Unentitled

My IBMid is entitled, since ./imcl listAvailablePackages -cPA -secureStorageFile mycreds | grep 9.0.5008 from my machine works.

Looks like it is failing at https://github.com/WASdev/azure.websphere-traditional.image/blob/45d28c23c3f1c1b50996df2915be75b8ecfa2445/twas-nd/src/main/scripts/was-check.sh#L28
if [ ${#ibmIdCredentials[@]} -eq 2 ]; then

I have comma (,) as one of the special character in the password

Good catch @git4rk. To fix the issue, I think we need to know the rules for IBMid and its password. Can you pls share about the rules?

It's interesting that rules for creating the new IBMid and editing the existing IBMid are different:

However, to fix the issue, I'll use the intersection between them.


feat: Support additionalProperties of type any in Python and TS (box/box-codegen#453)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 88.987%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
8331

Relevant Lines:
9362

💛  - Coveralls


Improve TestNet configuration and allow dynamic ConsensusParams

This fixes two major issues with the current TestNet setting:

A network reset requires a new release and users to manually upgrade;
Using '--testnet' does not work when a one wants to run a validator;

We fix both issues by first adding a new endpoint to the API, which returns the ConsensusParams.
The current approach is not ideal as ConsensusParams and ConsensusConfig are slightly different,
but it will cover our immediate need. The second issue is fixed by only overriding the consensus
section whenever we detect there is a configuration file we can read.
The realm, the registry address, and node.testing still need to be set correctly,
but the sample config file does this and people are likely to start off of it.

This works and can be tested (deployed on ns1).


Small fix

@ap3h3ad, your fork seems to be out of date and is submitting the deletion of files from another character sheet.  Please merge from this master repository into your branch to ensure you aren't committing removals that shouldn't be taking place.


pilad: Implement _ping endpoint

This allows to check health-check of server in a very cheap way.
Should be included in next 0.1.X release.

Codecov Report

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

@@          Coverage Diff          @@
##           master    #50   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          18     18
  Lines         669    674    +5
=====================================
+ Hits          669    674    +5

Impacted Files
Coverage Δ

pilad/router.go
100% <100%> (ø)
:white_check_mark:

pilad/conn.go
100% <100%> (ø)
:white_check_mark:

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 4e3cb4e...37077b8. Read the comment docs.


Figure out some way to improve autocomplete for methods

Due to the GameMaker IDE having lacklustre autocomplete with struct methods, Scribble doesn't offer autocomplete for its methods. This makes using Scribble a bit fiddly and requires the user remember method arguments (or have the documentation open at the same time). This... isn't great.
There is a sorta solution available, and that's to use the @func JSDoc notation to add autocomplete for methods. This'll let us add usage hints for all methods. Unfortunately, these autocomplete hints are then global: every use of draw, even if it's usage is as a variable, will now be colour-coded as functions and will offer autocomplete as though the usage is a method/function.
A couple users have suggested using @func but I'm not convinced it's a good idea given how GM's autocomplete works. Opinions?

I do agree that every keyword that aligns with a scribble method would be annoying and problematic at times, but I believe that the pros would outweigh the cons. Having the method arguments visible to the user would improve workflow and increase the user's knowledge of their scribble wisdom.
I personally didn't enjoy having to keep the scribble docs open while I used it, but I did learn to memorize many arguments. If this is how it has to be, then so be it I guess.
Here's a possible solution: though this might convolute things, it may work. Instead of naming many scribble functions the same as Game Maker functions, like draw, scribble functions could have an underscore before or after to differentiate between the two? I don't believe this would be an effective long term solution, but it may help till GMS receives proper support for method arguments.

I wonder whether it'd be possible/feasible to ship method documentation as a separate script. This'd replace the scribble_Methods Note and, furthermore, would allow people to remove the @func metadata if they want.

YAL pointed me towards https://github.com/GameMakerDiscord/GMEdit/wiki/Smart-completion

YAL pointed me towards https://github.com/GameMakerDiscord/GMEdit/wiki/Smart-completion

Not something that I have the time or energy to address at this point.


Make "authorization required" a setting & available to valveless systems

Today we use tap.flow_toggle != null as a signal that "this tap requires authorization", ie, there's a relay connected to it and it's probably a valve.
Explicit is better than implicit, and it opens up possibility for a new feature: On systems without valves, the tablet frontend could make a fuss when an unauthorized pour is started: play an alarm sound, show an ominous warning, hit a webhook, snap "security" photos, etc.

Bug scrub: No plans to address this. Closing as wontfix/fix later.


feat: hotfix release script

Description

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #6249
Risk

High Risk PRs Require 2 approvals

What protocols, transaction types or contract interactions might be affected by this PR?

Testing

Engineering

Operations

Screenshots (if applicable)

#6593  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gomesalexandre and the rest of your teammates on  Graphite


Return early if attribution controller does not exist

Addresses https://github.com/rowanwins/mapbox-gl-arcgis-featureserver/issues/1
If attribution controller did not exist, attempting to set options on it would result in a console error

Released in v0.0.2


Link instructions how to use VS Code a Git editor

Maybe I should have done that ages ago, but I only recently made VS Code my git editor. I had to explicitly search for that, however, so maybe you want to link to https://code.visualstudio.com/docs/editor/versioncontrol#_vs-code-as-git-editor in the instructions.
On a related note, I still wonder if/how I can apply commitlint to commit messages authored in the GUI, and/or redirect to the text editor when the GUI commit message is empty:

Thanks for the feedback!

Maybe I should have done that ages ago, but I only recently made VS Code my git editor. I had to explicitly search for that, however, so maybe you want to link to https://code.visualstudio.com/docs/editor/versioncontrol#_vs-code-as-git-editor in the instructions.

There are actually two links in the README to that very URL--one is in the description near the top ("A VS Code extension that integrates commitlint into VS Code's commit editor") and another at the bottom in the "Requirements" section ("VS Code as Git editor"). Of course, just because they are there does not mean they can't be too subtle to notice. Is there a way you think those instructions could be made more prominent in the README? Or were you thinking of exposing some instructions through the extension itself somehow?

On a related note, I still wonder if/how I can apply commitlint to commit messages authored in the GUI, and/or redirect to the text editor when the GUI commit message is empty:

I'm not aware of any way to do this today, but there are at least a couple of related feature requests:

https://github.com/microsoft/vscode/pull/95266 is a PR to redirect commits to the text editor.
https://github.com/microsoft/vscode/issues/103128 is a backlog item to allow commands to be used in the small commit editor on the left side of your screenshot; I don't think it would bring diagnostics (i.e., red/yellow squiggly lines) to that editor, and it may not even work particularly well for real-time linting. But depending on how it were implemented, it might at least provide an avenue for some kind of linting feedback for commits written in that editor.

There are actually two links in the README to that very URL

You are totally right, and I feel appropriately stupid now ;) I find a small thing in my defense, which is that if I open that URL, this is what my screen looks like:

So the actual "VS Code as Git editor#" heading is hidden behind the cookie banner, and my eyes focused on the "diff tool" one which felt less relevant. I guess there's not a lot you can do if people miss that, but since you asked:

Requirements
To make the most out of this extension, you'll probably want to configure commitlint in your project and use VS Code as your git commit editor

I feel the "Requirements" section might be moved further up in the readme, and you could formulate this sentence in a way that makes it sound less optional :) "you'll probably want to" sounds like I can, but don't have to (while it is a hard requirement, unless I am mistaken) - especially when mentioned after a rather soft requirement (which I think it is because I assume commitlint has a default configuration that will work out of the box).

On a related note, I still wonder if/how I can apply commitlint to commit messages authored in the GUI, and/or redirect to the text editor when the GUI commit message is empty:

I'm not aware of any way to do this today, but there are at least a couple of related feature requests:

Thanks, I am tracking these now.

On a related note, I still wonder if/how I can apply commitlint to commit messages authored in the GUI, and/or redirect to the text editor when the GUI commit message is empty:

For posterity, https://github.com/microsoft/vscode/pull/95266 has been released, which makes it easier to use a full editor to write commits even without making VS Code the default commit editor.
Even better, TIL it's actually possible to provide diagnostics for the SCM input box after all:

I'll try to get a new release out that supports this soon.

This is now implemented in 2.4.0. I also reworked the README a bit to de-emphasize the need to set VS Code as your git commit editor, since it's no longer necessary.


error: ‘OQS_SIG_alg_mayo_1’ undeclared (first use in this function); did you mean ‘OQS_SIG_alg_count

While build oqsprovider is failing with signature mayo algorithms.
OpenSSL: 3.2
Liboqs: 0.10.0
OQS-Provider: 0.7.0
Liboqs and provider Build Parameters
# liboqs
cmake -S . -B _build -DCMAKE_ASM_FLAGS=-Wa,--noexecstack \
        -DOPENSSL_ROOT_DIR=/opt/openssl \
        -DCMAKE_BUILD_TYPE=Release \
        -DOQS_DIST_BUILD=OFF \
        -DOQS_ALGS_ENABLED=STD \
        -DOQS_OPT_TARGET=generic \
        -DCMAKE_INSTALL_PREFIX=/opt/liboqs

# Provider
cmake -S .
Building oqs-provider...
+ cd /opt/oqs-provider-0.7.0
+ mkdir -p _build
+ liboqs_DIR=/opt/liboqs
+ OQS_ALGS_ENABLED=STD
+ cmake -S . -B _build -DOPENSSL_ROOT_DIR=/opt/openssl -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=OFF
-- The C compiler identification is GNU 10.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Creating Release build
-- Build will store public keys in PKCS#8 structures
-- Found OpenSSL: /opt/openssl/lib/libcrypto.so (found suitable version "3.2.0", minimum required is "3.0")
-- liboqs found: Include dir at /opt/liboqs/include;/opt/liboqs/include/oqs (STATIC_LIBRARY)
fatal: not a git repository (or any of the parent directories): .git
-- Building commit  in /opt/oqs-provider-0.7.0
-- Configuring done
-- Generating done
-- Build files have been written to: /opt/oqs-provider-0.7.0/_build
+ echo 'Building oqs-provider...'
Building oqs-provider...
++ nproc
+ cmake --build _build --parallel 8

Scanning dependencies of target oqsprovider
gmake[3]: Leaving directory '/opt/oqs-provider-0.7.0/_build'
gmake[3]: Entering directory '/opt/oqs-provider-0.7.0/_build'
[ 18%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqsprov.c.o
[ 18%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqsprov_capabilities.c.o
[ 27%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqsprov_keys.c.o
[ 36%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqs_encode_key2any.c.o
[ 45%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqs_kmgmt.c.o
[ 54%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqs_kem.c.o
[ 63%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqs_sig.c.o
[ 72%] Building C object oqsprov/CMakeFiles/oqsprovider.dir/oqs_endecoder_common.c.o
/opt/oqs-provider-0.7.0/oqsprov/oqsprov_keys.c:196:18: error: ‘OQS_SIG_alg_mayo_1’ undeclared here (not in a function); did you mean ‘OQS_SIG_alg_count’?
  196 |     {0, "mayo1", OQS_SIG_alg_mayo_1, KEY_TYPE_SIG, 128},
      |                  ^~~~~~~~~~~~~~~~~~
      |                  OQS_SIG_alg_count
/opt/oqs-provider-0.7.0/oqsprov/oqsprov_keys.c:198:18: error: ‘OQS_SIG_alg_mayo_2’ undeclared here (not in a function); did you mean ‘OQS_SIG_alg_count’?
  198 |     {0, "mayo2", OQS_SIG_alg_mayo_2, KEY_TYPE_SIG, 128},
      |                  ^~~~~~~~~~~~~~~~~~
      |                  OQS_SIG_alg_count
/opt/oqs-provider-0.7.0/oqsprov/oqs_kmgmt.c: In function ‘mayo1_new_key’:
/opt/oqs-provider-0.7.0/oqsprov/oqs_kmgmt.c:1170:54: error: ‘OQS_SIG_alg_mayo_1’ undeclared (first use in this function); did you mean ‘OQS_SIG_alg_count’?
 1170 |     return oqsx_key_new(PROV_OQS_LIBCTX_OF(provctx), OQS_SIG_alg_mayo_1,
      |                                                      ^~~~~~~~~~~~~~~~~~
      |                                                      OQS_SIG_alg_count

OS Release
root@832081ca4b07:/oqsbuild# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Mayo is only present fromliboqs 0.11.0: Please upgrade that lib.

Thanks is there way to skip mao algo from configure options?
…
On Sun, 13 Oct 2024 at 10:24, Michael Baentsch @.> wrote: Mayo is only present fromliboqs 0.11.0: Please upgrade that lib. — Reply to this email directly, view it on GitHub <#541 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADIIAAIMAHUCTPTBFULBHIDZ3H4HRAVCNFSM6AAAAABP2577J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYHAZDGNBRGI . You are receiving this because you authored the thread.Message ID: @.>

Yes see documentation of config options

I am passing the OQS_ALGS_ENABLED="STD" https://github.com/open-quantum-safe/liboqs/blob/9aa2e1481cd0c242658ec8e92776741feabec163/.CMake/alg_support.cmake#L213, where mayo wasn't enabled. Still, I see failures while building. Do I need to disable it explicitly?
# Provider
cmake -S .

You need to completely remove code catering for Mayo using "generate.py" (see pre-build config). You can use the file https://github.com/open-quantum-safe/oqs-provider/blob/main/oqs-template/generate.yml-0.10.0 for this purpose.
@praveksharma : This now unearths another shortcoming in the latest release: It did not create a suitable generate.yml-0.11.0 to allow people to build oqsprovider against a (future) downlevel liboqs (just as in the case discussed here where oqsprovider is built against an outdated liboqs version).

You need to completely remove code catering for Mayo using "generate.py" (see pre-build config). You can use the file https://github.com/open-quantum-safe/oqs-provider/blob/main/oqs-template/generate.yml-0.10.0 for this purpose.

This will additionally change our CI scripts. Can we create a support matrix for each oqs-provider release tag (https://github.com/open-quantum-safe/oqs-provider/issues/543)?

This will additionally change our CI scripts

Which CI scripts are you talking about? I'm not aware of an issue asking for an expansion of CI -- to the contrary, we have several long-standing issues to streamline CI runs (#248, #353) -- also with the goal to be(come) more responsible wrt resources this project utilizes.

@praveksharma : This now unearths another shortcoming in the latest release: It did not create a suitable generate.yml-0.11.0 to allow people to build oqsprovider against a (future) downlevel liboqs (just as in the case discussed here where oqsprovider is built against an outdated liboqs version).

@praveksharma , see (&review/approve) #544 and changes to the release wiki now capturing these items.


FancyZones - Cycle shortcut zones with mouse wheel on the fly

Description of the new feature / enhancement
Hello. I'm requesting a feature where once activated (by pressing shift/hotkey) users can scroll through preselected templates (based on shortcut index) with the mouse wheel.
Scenario when this would be used?
You have a monitor full of windows but have other windows behind it you occasionally need. It would be great to be able to change the layout quickly by simply scrolling the mouse wheel while shift + dragging a window to place it.
I realize hotkey shortcuts already exist based on 3-key combos with numbers, but the suggested approach streamlines it for faster workflow.
I'd ask that only layouts assigned with a Layout Shortcut be included in this approach (or at least set as the default option).
Supporting information
No response

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #4969


Wrong IoU calculation when corners are smaller than 0

Hi! Thank you @lilanxiao for your great work. I have been using your work for sometime, and it has been beneficial for my training.
One problem I encountered was under certain circumstances, the IoU calculations are wrong. Most of them happened when the calculated corners of boxes are smaller than zero. Some happened when length or width are too small, which may have something to do with numeric instability. There's maybe other cases, but these two are what I have discovered.
My environment:
Ubuntu 18.04, CUDA 11.2, Pytorch 1.8, python 3.8

I have a simple solution for the corners problem: simply add a translation to all boxes if any of their corners coordinates is negative.
def cal_iou(box1: torch.Tensor, box2: torch.Tensor):
    """calculate iou
    Args:
        box1 (torch.Tensor): (B, N, 5) with x, y, w, h, alpha
        box2 (torch.Tensor): (B, N, 5) with x, y, w, h, alpha

    Returns:
        iou (torch.Tensor): (B, N)
        corners1 (torch.Tensor): (B, N, 4, 2)
        corners1 (torch.Tensor): (B, N, 4, 2)
        U (torch.Tensor): (B, N) area1 + area2 - inter_area
    """
    corners1 = box2corners_th(box1)
    corners2 = box2corners_th(box2)

    # calculate the min corner coordinates
    corners_min = torch.minimum(corners1, corners2).amin(-2) - 1e-5   # eps
    # if any element is negative, translate all coordinates to positive number
    if corners_min.lt(0).any():
        corners1_positive = corners1 - corners_min
        corners2_positive = corners2 - corners_min
        inter_area, _ = oriented_box_intersection_2d(corners1_positive, corners2_positive)    # (B, N)
    else:
        # if not, directly calculate the intersection area
        inter_area, _ = oriented_box_intersection_2d(corners1, corners2)    # (B, N)
    area1 = box1[:, :, 2] * box1[:, :, 3]
    area2 = box2[:, :, 2] * box2[:, :, 3]
    u = area1 + area2 - inter_area
    iou = inter_area / u
    return iou, corners1, corners2, u

I tested the results against the one implemented in detectron2, and the results difference for 1000 random tests are within 1e-3.

代码有问题，不知道怎么改，求作者更新代码

hi, thank you for the issue and workaround.
I've just updated my code in the debug branch. I think the new version is probably more stable.
Please let me know if the problem persists.

hi, thank you for the issue and workaround. I've just updated my code in the debug branch. I think the new version is probably more stable. Please let me know if the problem persists.

Thanks! Will test soon.

还是会出现nan

same problem
Can we simply add a constant big value to the corners at the beginning like this?
def cal_iou(box1:Tensor, box2:Tensor):     corners1 = box2corners_th(box1) + 100     corners2 = box2corners_th(box2) + 100


[FIX] fix out of sync lsm examples in the documentation

Description
This PR updated some examples in the lsm repo.
Causing this build failure: https://jenkins.inmanta.com/job/docs/job/lsm-documentation-examples-verification/job/master/400/
The current pr syncs them up here in the core repo documentation
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Merged into branches master, iso7 in 1c667846f550fcd1e2ffc6a73b4d64b249de205b


Update Human Pose Tracking Readme file

What
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Rendered: https://github.com/rerun-io/rerun/blob/andreasnaoum-readmes/examples/python/human_pose_tracking/README.md

Hot tip: configure your editor to trim trailing whitespace, and to always add a ending newline.
Then run pixi run lint-rerun to see some of the errors that the CI is complaining about

I changed completely the readme, so please take a quick look again.
We are trying to figure out the template for README files.
Suggested Template:
Small Description

Used Rerun Types
Background (Optional)
Logging and Visualizing with Rerun
Run


[dotnet] renamed to sauce bindings

Renamed everything to Sauce.Bindings
Fixed issue with old version of .NET Core and moved it to 3.0

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- dotnet/SimpleSauce.Test/AcceptanceTests.cs  1

Clones removed
==============
+ dotnet/SimpleSauce.Test/BaselineSeleniumAcceptanceTests.cs  -1

See the complete overview on Codacy


added suport to diplay tags for scenarios

this is a fix for: #33

[Current coverage][cc-pull] is 52.15%

Merging [#42][cc-pull] into [master][cc-base-branch] will decrease coverage by 7.74%

@@             master        #42   diff @@
==========================================
  Files            31         31
  Lines           743        744     +1
  Methods           0          0
  Messages          0          0
  Branches         99         99
==========================================
- Hits            445        388    -57
- Misses          298        324    +26
- Partials          0         32    +32

Powered by Codecov. Last updated by [70f8309...4471bac][cc-compare]
[cc-base-branch]: https://codecov.io/gh/web-innovate/bootstraped-multi-test-results-report/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/web-innovate/bootstraped-multi-test-results-report/compare/70f83095c3638e95819ac8dcc9a9a732807f2ea9...4471bacd61b138476e7bfe9e0907c3ed133a036f
[cc-pull]: https://codecov.io/gh/web-innovate/bootstraped-multi-test-results-report/pull/42?src=pr


Docs  and typing on gurobipy_pandas.api.add_constrs should indicate that LHS and RHS can be single values or floats

Let's say you have the following:
m = grb.Model()

onevar = m.addVar(name="B")

Bser = gppd.add_vars(m, pd.Index([1,2,3]), name="Bser")

gppd.add_constrs(m, onevar, grb.GRB.GREATER_EQUAL, Bser, name="BLT")

gppd.add_constrs(m, Bser, grb.GRB.LESS_EQUAL, 3*onevar + 4, name="RHSexpr")

m.optimize()

The code above works fine.  The first constraint represents the constraint that "B >= Bser", i.e., one variable is greater than all the ones in the series.  The second constraint represents that "BSer <= 3*B + 4".
The docs and typing don't say you can do this, but I think you can put any linear expression, including a single variable, or a single value as the rhs or lhs arguments, and it will work fine.
The typing accepts a single value, but the docs don't have that.

On the order of arguments: I had kept the order strict in typing/docs intentionally (the thinking being for consistency in user code, if you have one side being a series and the other a scalar, putting the series first seems to makes sense). That it works both ways at the moment is really an implementation detail, but we can make it official.
I do think passing scalars for both lhs and rhs should be explicitly disallowed though (such constraints should go through the regular gurobipy API). Would it make sense to document it as "at least one of lhs/rhs must be a pandas series"? For typing we then need three overloads to capture the options.
On the accepted scalar types: yes, this should be updated to accept any scalar (var/linexpr/etc as well as a float).

On the order of arguments: I had kept the order strict in typing/docs intentionally (the thinking being for consistency in user code, if you have one side being a series and the other a scalar, putting the series first seems to makes sense). That it works both ways at the moment is really an implementation detail, but we can make it official.

The docs have the order explicit, but the typing hints do not.  I think it should be official that you can do it either way.

I do think passing scalars for both lhs and rhs should be explicitly disallowed though (such constraints should go through the regular gurobipy API). Would it make sense to document it as "at least one of lhs/rhs must be a pandas series"? For typing we then need three overloads to capture the options.

While it ideally wouldn't make sense for someone to do something like gppd.add_constrs(m, 3, grb.GRB.LESS_EQUAL, 4), it could be that they are doing gppd.add_constrs(m, exp1,  grb.GRB.LESS_EQUAL, exp2), where exp1 and exp2 are the result of some computation in the code that ends up being a constant unexpectedly.  So what would be useful in this case is a warning saying that you passed 2 constant values for the LHS and RHS.  I do agree that it makes sense for gurobipy-pandas to require either side to be a Series.

On the accepted scalar types: yes, this should be updated to accept any scalar (var/linexpr/etc as well as a float).

Great.


integrate tidy introduction slides to slideshow course

see https://stijnvanhoey.github.io/workshop_ywp20/#13 and following slides

See https://github.com/jorisvandenbossche/ICES-python-data/blob/main/slides.html as done for the ICES course

Done as part of https://github.com/jorisvandenbossche/course-python-data/pull/40/files (slides template)


Updated charge links on metering points are ready for wholesale calculations

@khatozen i dont think volt has update events yet, in charge domain


add featuregate summarization for oc and api

adds analysis for serialized FeatureGates to produce table representations.

comments addressed.


IntelliSense typing info in 2.9.0-dev.20180407 release doesn't work

TypeScript Version:  2.9.0-dev.20180407

Search Terms:  intellisense, missing types
Perhaps I'm missing something here, as I don't use typescript and have always just used the version that vscode ships with for intellisense, but after updating to the latest for a fix of a prev issue I posted about (see bottom) I now have the following issue.
See the following gifs for an explanation:
Expected behavior:
This is what happens in version 2.8.1. It also successfully recognises the type definitions file.

Actual behavior:
This is currently what happens in the 2.9.0-dev version. The type definitions file is not found.

Furthermore it happens with any module e.g this is the react one. Note that it works initially then just fails afterwards:

Workaround:
I can get it to work again by manually installing each of the types i.e @types/chai etc. However that's not ideal so I've reverted back to 2.8.1 for the time being.
Related Issues:
I brought up an issue with intellisense crashing in 2.8.1, but am unsure if this is a side effect from that or just another issue entirely. So whilst the path issues are fixed in 2.9, the outlined issue above now shows up.
https://github.com/Microsoft/TypeScript/issues/23234
I can provide the typescript log in private if need be.

So I tried going back through previous typescript versions, and have found that the 2.4.2 release does not have either the problem outlined above, or the issue I posted about in #232324. So until this issue is resolved, I'll just stick to that version.

Can you please provide tsserver and typing installer logs. Also your package.json, Also let us know if you have explicitly installed any modules and typings. Thanks.

I've started having intellisense issues in February's 1.21 update. Ever since it's been failing after a while, but 1.22 completely broke it. It just doesn't work, and reverting back to typescript 2.81 or 2.4.2 doesn't work.
What worked for me was actually installing January's 1.20.1 vscode. It comes with typescript 2.8.1, and it works fine. I didn't even try any other typescript versions because I was afraid it would break things again.
So maybe it's not only on typescript, since 2.8.1 works fine with vscode 1.20.1: intellisense is smooth as it always been.
I have absolutely no use for typescript, I don't use it at all, so having a version that just makes vscode work is fine by me, whatever version that is.

relevant package.json bits:
{
  "dependencies": {
    "chai": "^4.1.2",
    "chokidar": "^2.0.2",
    "clean-webpack-plugin": "^0.1.19",
    "colors": "^1.2.1",
    "express": "^4.16.3",
    "handlebars": "^4.0.11",
    "morgan": "^1.9.0",
    "nock": "^9.2.3",
    "npm-run-all": "^4.1.2",
    "opn": "^5.3.0",
    "query-string": "^6.0.0",
    "react": "^16.2.0",
    "react-dom": "^16.2.0",
    "react-hot-loader": "^4.0.0",
    "request-promise-native": "^1.0.5",
    "sinon": "^4.4.8",
    "sinon-chai": "^3.0.0",
    "source-map-support": "^0.5.4",
    "typescript": "^2.9.0-dev.20180410",
    "webpack": "^4.2.0",
    "webpack-cli": "^2.0.13",
    "webpack-dev-middleware": "^3.0.1",
    "webpack-hot-middleware": "^2.21.2",
    "webpack-merge": "^4.1.2",
    "webpack-node-externals": "^1.6.0"
  },
  "devDependencies": {
    "@babel/cli": "^7.0.0-beta.42",
    "@babel/core": "7.0.0-beta.44",
    "@babel/node": "7.0.0-beta.44",
    "@babel/plugin-proposal-class-properties": "7.0.0-beta.44",
    "@babel/plugin-transform-runtime": "7.0.0-beta.44",
    "@babel/preset-env": "7.0.0-beta.44",
    "@babel/preset-react": "7.0.0-beta.44",
    "@babel/preset-stage-0": "7.0.0-beta.44",
    "@babel/register": "7.0.0-beta.44",
    "@babel/runtime": "7.0.0-beta.44",
    "babel-loader": "^8.0.0-beta.0",
    "cross-env": "^5.1.4",
    "dotenv": "^5.0.1",
    "dotenv-webpack": "^1.5.5",
    "eslint": "^4.19.1",
    "eslint-config-prettier": "^2.9.0",
    "eslint-loader": "^2.0.0",
    "eslint-plugin-mocha": "^5.0.0",
    "eslint-plugin-prettier": "^2.6.0",
    "eslint-plugin-react": "^7.7.0",
    "eslint-watch": "^3.1.4",
    "handlebars-loader": "^1.7.0",
    "mocha": "^5.0.4",
    "mocha-webpack": "^2.0.0-beta.0",
    "node-mocks-http": "^1.5.8",
    "prettier": "^1.11.1",
    "request": "^2.85.0",
    "sinon-test": "^2.1.3",
    "supertest": "^3.0.0",
    "webpack-bundle-analyzer": "^2.11.1",
    "webpack-hot-server-middleware": "^0.5.0"
  },
}

@sheetalkamat I'm not sure what you mean by typing installer logs; can you be more specific? Either way, I've just uploaded both of the files that showed up in the tsserver log folder:
ti-6468.log
tsserver.log
As for explicitly setting typings, if I'm understanding you correctly, no I haven't. I did get it to work though by manually installing them from npm. Curiously a lot of typings are missing from the 2.9 installation:

Oops, sorry for the accidental close.
Just to add, note I'm using 2.9.0-dev.20180410 now from typescript@next, but the issue is still there. I can put together a repo again if need be, but the repo from the other issue I posted would suffice for testing it.

Hi @sheetalkamat, is there any update on this issue?

Seems like typing installer is failing and resulting in no npm packages for the types and hence no intellisense. From the shared ti log it looks like package for @types/chokidar doesnt have 2.9 version which results in failure to install any package. @andy-ms is looking into why there is no 2.9 version on that package.

Sounds good. Let me know if I can provide a repo if it helps tracking the issue down.

@RonanQuigley Repro code would be great help to ensure that this is fixed correctly and also investigate if there are any other perf tweaks possible.

Sorry for the delay in getting back.
So I now can't get the issue to consistently repro. Have been fiddling with it for about 30 mins and has happened three times in that time, but all of the steps that caused it were completely unrelated and random. The only constant is it happens after a period of time about 5 minutes.
I've tried to reduce my repo from the prev issue I posted down to a minimal size, but I've chosen to keep it as is (bar updated to typescript 2.9) as the issue could be tied to project size. I did reduce it to a couple of files but it never happened in that case. I can appreciate this won't be ideal for tracking down the issue, so if you're unable to repro with this I'll understand.
https://github.com/RonanQuigley/vscode-intellisense-bug
As an aside, why is it that the code completion does not work in the following scenario:

Here I've declared a variable at the top, set it to a value inside a function, then attempt to use auto completion further down the file but it comes back blank?

@andy-ms Ah yeah that makes sense. Thanks for the clarification.
@mhegazy Was the bug label removed for that aside question or the main issue I posted about, as nobody has said either way whether or not this can be replicated with the repo I posted? If you need something more definitive then I'm out of ideas unfortunately. Until then I'll just stick with an earlier version of typescript.

Sorry i got sidetracked by the last comment. @sheetalkamat have you had time to look at the repro?

I had cloned this yesterday and then it slipped from my todo list. I tried this today with drop from latest master build and havent been able to repro this at all.. I did wait for 5-10 min and kept on playing around with the code and still no luck.
@RonanQuigley can you try out<EMAIL_ADDRESS>(build that would be released tonight) with verbose log. Share the ti and tsserver log from the sessions when you are able to repro the issue. From the log and the repro code, i should be able to diagnose if the issue persists.

I got it to happen after about 10 minutes this time:
logs.zip

Okay so initially I thought I was being an idiot, as I realised I didn't actually have react or react-dom in the dependencies, which is what I was trying to repro this issue with. :laughing: Weirdly there was code completion showing up without either being installed; I guess it was looking inside another typescript version folder? I did also have another vscode project open in the background..
Either way, even after installing any missing modules it still happens. And with other already installed modules. This time I did get it to happen twice:
logs.zip
logs - 2nd crash.zip

Hope this helps.

@RonanQuigley Thank you for the logs. I was able to use the logs to investigate this. Will keep you posted when i have fix available.

@RonanQuigley can you please try out<EMAIL_ADDRESS>once its published. We have fixed the exceptions that you were running into. Thanks.

Tried it, still the same problem:
logs.zip

@RonanQuigley Looking at the log there wasnt a single completion that took more than 350 ms. Can you please check if the logs are of session in which the issue reproed.

I took a second look at the logs and i think the issue you are seeing now is duplicate of #19458 where i think it might be same reason as geterr triggered before completion resulting in the wait you see in editor but not in the log. This is because tsserver is working on getErr request and since its not cancelled it cannot get to completions before that work is complete. Snippet from the log which makes me guess that #19458 is same issue.
 I had to put this down due to other work.
I looked through the other issue and it says it is to do with the sass.js module? I'm not using that module in the project. Do you want me to reproduce the logs again?

@RonanQuigley Fix for #19458 is not yet working from vscode side. I will let you know once its available. Even though issue #19458 talks about sass.js it has nothing to do with the module dependency itself but about how errors and completions request interact with each other.

Not sure if it's related to this issue, but thought it might be worth mentioning that the latest releases of typescript (currently I've tried 2.9.0-dev.20180519) seems to have helped quite a bit. I still get an occasional crash during the day, but it's not as frequent.

@RonanQuigley Can you please share the server and ti log when you see crash. The previously encountered crash was fixed in #23636

Closing this since there is no more info since May. If you have more info and able to repro this with latest typescript and vscode drop please provide that.


about test

Hello, thank you very much for providing the code open source, I would like to ask you how to test with the model I trained, and where should the path be placed in the model I trained

If you train the model under the SimTrack pipeline, you can directly test it as the evaluation instructions. Otherwise, you need to add the network defination (refer to lib/models/stark/clipvit16.py) to the code, change the model path (in /lib/test/tracker/simtrack.py) and then do the evaluation.

Thank you very much for the answer, I did test as you said, but still have problems.
I added the path of my trained model in the specified location，But when I execute“python tracking/test.py simtrack baseline --dataset got10k_test --threads 32”，The following occurs during operation.
and
I don't know why，I hope you can help me answer this question,Please。
If I can, I would like to communicate with you via WeChat, here is my contact information: ygxs314, thank you.
At 2023-10-17 10:08:19, "LPXTT" @.***> wrote:
If you train the model under the SimTrack pipeline, you can directly test it as the evaluation instructions. Otherwise, you need to add the network defination (refer to lib/models/stark/clipvit16.py) to the code, change the model path (in /lib/test/tracker/simtrack.py) and then do the evaluation.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Move wimg/ to phpcompatibility/

Suggest updating the composer require for wimg/php-compatibility.

Package wimg/php-compatibility is abandoned, you should avoid using it. Use phpcompatibility/php-compatibility instead.

@gmazzap are you going to cut a release for this?

@thefrosty here's it https://github.com/inpsyde/php-coding-standards/releases/tag/0.13.4


NIFI-9206: Add RemoveRecordField processor and implement the ability to remove fields from records

Summary
NIFI-9206 add the RemoveRecordField processor to allow for remove of Record Field(s) from FlowFile content using RecordPath specification similar to UpdateRecord.
Caters for simple as well as complex, nested, collection and choice DataFieldTypes.
A rebase of @pgyori's #5381 taking @tpalfy's comments into account (as well as @Lehel44's comments from #5038).
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-9206
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-9206

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[x] JDK 11
[x] JDK 17

Licensing

~[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy~
~[ ] New dependencies are documented in applicable LICENSE and NOTICE files~

Documentation

[x] Documentation formatting appears as expected in rendered files

@ChrisSamo632 you have a merge conflict.

@ChrisSamo632 you have a merge conflict.

Thanks for the heads-up @MikeThomsen, recent removals of deprecated modules had meant the changes to the RAT exclusion list in the nifi-standard-processors module's pom.xml file were confused - should now be resolved

If you know all of the fields in your data and are happy/able to write them all into a SELECT statement, omitting just those that aren't wanted, then yes QueryRecord can be a useful alternative here.
Where I'd have liked this option previosuly is when we receive different formats of data from different sources although each of those contains a set of known fields, they contain some that aren't wanted but also some we don't know about beforehand (e.g. "extra" columns that we need to retain but aren't in a set of "known" fields that we could include in a SELECT). There's not a way with QueryRecord (that I can immediately think of) to say "select these 5 fields, omit these 3, retain any other fields", but a way of deleting just those 3 fields from Records would allow this to happen - instead I've ended up writing Groovy Scripts (or similar) to cater for this previously and scripting often seems like a way that people don't want to go.
I could see this kind of functionality being useful alongside that already present in UpdateRecord and it seems this function originally was being implemented for that processor, but the idea of a separate processor was ultimately preferred (looking back at Jiras and previous PRs)

Thanks for the summary @ChrisSamo632.
Looking over the current PR, there are a number changes that apply to other Processors. Although they are useful in themselves, they should be split off to separate PRs where possible.
This new PR also includes a very large number of test files. Do you think all of those are necessary? The size and scope seem larger than needed at a glance, but I have not yet given the tests a thorough review.

@exceptionfactory I see a change to the accumulo bundle's KeyScehama, which extends RecordSchema and so needed changing to implement the updated RecordSchema API; and a change to a unit test for an asn1 test case that (presumably) didn't pass without the modifications.
Otherwise this PR includes the addition of the new RemoveRecordField processor and required changes to the associated Record and RecordPath framework classes (which obviously could impact a lot).
I'm not clear on what

number changes that apply to other Processors. Although they are useful in themselves, they should be split off to separate PRs where possible

can be split off from this into separate PRs
As to

This new PR also includes a very large number of test files. Do you think all of those are necessary? The size and scope seem larger than needed at a glance, but I have not yet given the tests a thorough review.

I agree, I was surprised there were so many test files ubt presumably these were included to try and cover the wide range of possible Record modifications that one could perform with the new processor (I largely just tried to re-invigorate #5381, I probably didn't check through every new test case/file in detail when doing so, I'll be honest)

Thanks for the reply and summary @ChrisSamo632. On further review, the changes to those other components make sense together with the adjustments necessary for this PR, so breaking things up is not necessary.
I think it would be worthwhile to review the scope of the test files and reduce the number of test files if sufficient coverage can be achieved.

@exceptionfactory I've reviewed the tests and removed a few as they were overlapping enough to (I think) de-duplicate.
However, there are still quite a lot being added, but I think they're justified because they cover a combination of different Schema Data Field Types (e.g. Scalar, Array, Map, Choice) along with top-level and nested fields being removed.
I had a bit of a play with trying to avoid the need for both input and output schema files, but it was turning into relatively unmanageable code, e.g. to read the input schema into a JsonNode, then try to remove the fields we'd expect to not exist; so I think having all the inputs/outputs defined as files makes sense, although I've used schema inference in a couple of places to at least show that's possible too.

@exceptionfactory addressed your comments, ready for re-review


Fix test, add more tests & minor changes

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues

👍


Visualize metadata on view pages

When you reach view page for an object, request metadata using this endpoint:
https://api.synbiohub.org//metadata

view pages are working for sbh2


Getting null resoince in getIceServers() methods

Hello there,
I am getting null response in getIceServers(), please help

Look at this https://github.com/vivek1794/webrtc-android-codelab/issues/32#issuecomment-469831877


use MSE as a prognostic variable for prognostic edmf

Purpose

Change subdomain prognostic variable from h_tot to MSE. I think this is mostly ready. One thing I want to check is whether we can remove some caches (e.g. only save mse and calculate h_tot on the fly). I may also need to fix allocations for some cases.
Closes #2251
To-do

[ ] Try removing h_tot in the cache
[x] Fix allocations

Content

[ ] I have read and checked the items on the review checklist.

I removed draft and environment h_tot from the cache.


[BUG] TypeScript  Excel.Column[] type check error

🐛 Bug Report

Lib version: 4.2.0
Steps To Reproduce

sheet1.columns = [
      { key: 'account', width: 20, style: { font: tableFontStyle, alignment: alignCenter } },
      { key: 'time', width: 16, style: { font: tableFontStyle, alignment: alignCenter } }
]

/*

error msg:

type "{ key: string; width: number; style: { font: Partial<Font>; alignment: Partial<Alignment>; }; }" lack type Column props: outlineLevel, hidden, values, letter... ts(2740)

*/

The expected behaviour:
Optional parameters, not required option

I get the same error.
After updating from version 4.1.1 to 4.2.0.

I found the difference between the two versions (which caused this bug). This is version 4.1.1:

And this is version 4.2.0:

It seems that reverting is needed here.

I also had a problem with this, the update

A temporary solution would be downgrading to version 4.1.1

I think a hot fix is needed for this issue

After I re-npm install, the wrong type file is still in the v4.2.0 version, I hope to fix it as soon as possible

Just ran into the same issue myself

A workaround will be like this:
sheet.columns = [             { header: 'Id', key: 'id', width: 10},             { header: 'Name', key: 'name', width: 32 },             { header: 'Work Date.', key: 'DOB', width: 10, outlineLevel: 1, style: { numFmt: 'dd/mm/yyyy' } },             { header: 'Meal 1 Out', key: 'meal1', width: 32 },             { header: 'Meal 2', key: 'meal2', width: 32 }           ] as ExcelJS.Column[];


Import Makefile environment variables

Fixes #380

Rebased on the latest master.

Also it would be nice to extend the /tests/test/import test to cover environment as well.

Test added in ad33e4b. Would you please check it @psss with the rest of the changes to the PR?


[AIRFLOW 1159] DockerOperator can use newer docker.

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-1159] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1159

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

'DockerOperator' can't run 'docker==2.3.0'(Docker API for python).
I think it was broken after this commit
I fixed it.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2361 into master will decrease coverage by 0.17%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2361      +/-   ##
==========================================
- Coverage   69.43%   69.26%   -0.18%
==========================================
  Files         145      145
  Lines       11070    11135      +65
==========================================
+ Hits         7687     7713      +26
- Misses       3383     3422      +39

Impacted Files
Coverage Δ

airflow/operators/docker_operator.py
97.4% <100%> (+0.03%)
:arrow_up:

airflow/api/common/experimental/mark_tasks.py
82.97% <0%> (-13.23%)
:arrow_down:

airflow/www/views.py
67.62% <0%> (-1.16%)
:arrow_down:

airflow/jobs.py
75.27% <0%> (+0.53%)
: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 355fc92...da9743f. Read the comment docs.


BuildToolsVersion compatibility with RN 0.56

The error:
 Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-sound'.
      > The SDK Build Tools revision (23.0.1) is too low for project ':react-native-sound'. Minimum required is 25.0.0

Would it be possible to update them following this approach?

What went wrong:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApk'.
A problem occurred configuring project ':react-native-sound'.
The SDK Build Tools revision (23.0.1) is too low for project ':react-native-sound'. Minimum required is 25.0.0

I'am having the same issue after updating to react native 0.56.0 anyone knows what to do ?

same issue in react native 0.56.+. are you have update plan yet?
currently I manually change the react-native-sound/android/build.gradle file's sdk version.

react-native-sound package needs to be updated to use with RN 0.56

Looks like this has been resolved. The project now supports RN 0.60.


(DOCUMENT-982) fix hiera config default info

Docs had some conflicting info about the default location for hiera.yaml. In fixing those issues, I found that this line was not wrong exactly, but maybe a bit backwards. As I understand it, hiera.yaml is now in confdir only if there is no codedir.
Of course, this fix depends on whether my understanding of this is correct, so feel free to reject if not. I made a couple of other very minor fixes while I was in there.

This failed travis for dumb reasons, if you could amend the commit to start with "(docs)" that will fix it. Otherwise, this lgtm

CLA signed by all contributors.

I can, but it turns out I might be operating on misinformation. Marking this as "do not merge" until I nail it down.

This failed travis for dumb reasons, if you could amend the commit to start with "(docs)" that will fix it. Otherwise, this lgtm

OK, this PR is based on an incomplete understanding of where hiera.yaml lives, because it's changed a couple of times in recent years. No change needed, closing this PR.


[Enhancement] trace query id when retry rpc

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：
Fixes #
Problem Summary(Required) ：
When we want to find the corresponding SQL from the query-id, we usually get it from fe.audit.log,
but if rpc fails or other reason happened, the query id will change, then we can't find the exact SQL from the audit log at this time
So I logged the change in query id and used the new query id to find the corresponding SQL

run starrocks_fe_unittest

run starrocks_fe_unittest

[FE PR Coverage check]
:disappointed: fail : 1 / 5 (20.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/qe/StmtExecutor.java
0
4
00.00%

:large_blue_circle:
com/starrocks/qe/QeProcessorImpl.java
1
1
100.00%


Wake up/Turn on not working after few hours off

System Health details
System Information

version
core-2023.12.4

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.6

os_name
Linux

os_version
6.1.63-haos

arch
x86_64

timezone
Europe/Rome

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.33.0

Stage
running

Available Repositories
1373

Downloaded Repositories
22

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.2

update_channel
stable

supervisor_version
supervisor-2023.12.0

agent_version
1.6.0

docker_version
24.0.7

disk_total
439.4 GB

disk_used
10.1 GB

healthy
true

supported
true

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
Advanced SSH & Web Terminal (17.0.1), File editor (5.7.0), Duck DNS (1.15.0), NGINX Home Assistant SSL proxy (3.6.0), Home Assistant Google Drive Backup (0.112.1), GoSungrow (3.0.7), Mosquitto broker (6.4.0)

Dashboards

dashboards
4

resources
16

views
21

mode
storage

Recorder

oldest_recorder_run
December 29, 2023 at 16:47

current_recorder_run
January 7, 2024 at 11:00

estimated_db_size
1008.52 MiB

database_engine
sqlite

database_version
3.41.2

Xiaomi Miot Auto

component_version
0.7.14

can_reach_server
ok

can_reach_spec
ok

logged_accounts
1

total_devices
2

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
I have been successfully using this integration with my 2 Fujitsu ARXG24KMLA since September.
I am now trying to move my on/off scheduling from the FGLair app to an HA script.
No problems for the off-scheduling.
But the on-scheduling only works if the switch off is quite recent.
So no problems when I test it (turn off, wait few minutes, turn on).
But there is no way to make it work if several hours have passed since it was turned off, neither with the script nor manually from the UI climate card.
My typical case: the script turn them off at 22 and then (try to) turn them on at 6.
This is the script service call:
service: climate.turn_on target:   entity_id:     - climate.condiz_zona_giorno data: {}
I also tried changing temperature and other settings to "wake up" the devices, but no way.
As I said, I believe it's not a script problem, because they do not wake up even manually changing settings from the UI card too.
When I turn them on again from the FGLair app, they immediatly turn on.
Reproduction steps

turn device off
wait few hours
turn device on from script or manually
...

Debug logs
not an expert, but I did not find any useful log in the system log, even with debug enabled

Diagnostics dump
No response

It looks like i got this issue too. But i can use my AC normally at any given time using the card on the HA dashboard.
Only thing is it will never turn on at the automation i have set at 6am. But running the automation myself or setting it a few minutes after the current time does work. It only refuses to do so at 6am (and 6:05 and 6:10 am since i tried).
Did you find a solution?

Yes, after many failed attempts.
Don’t try to power on it but just set the HVAC mode that you desire (e.g. HEAT), wait few seconds (e.g. 10s) and then set the target temperature. It is working fine since months.
Let me know if this worked also for you.

Great! Gonna try it!
And just to be sure. I had now 2 actions. One was turning on the AC and the other one was setting temp and hvac mode.
But the solution is to delete those 2 and first start with set hvac mode and a seperate action to set the temp, right?

Yes, 2 separated actions in the same automation/script, with a delay between them.

Wow! It worked! :)
This made me happy! :D

I wonder if my issue is related. I get Fglair entities, works fine, then after a while they go blank and I get new MQTT entities. They make the AC's work, once I turned the MQTT entities on and off, the Fglair entities populate again for a few hours. Then they go blank again.

That's not something i encountered with my issue. I also don't have an idea to fix this.
Did you try to delete them and add them again?

I deleted the MQTT entities a while back and everything stayed working a while. After a few days I noticed the Fglair cards were empty again and the MQTT entities were back.

The workaround has been found here: https://github.com/bigmoby/fglair_for_homeassistant/issues/95#issuecomment-2002320074

So, I deduce that the climate.turn_off is not working anymore due to some changes at HA OS level, because I did the upgrade more or less at the same time of the FG integration upgrade.
Workaround: instead of using that service to turn off the climate, you can use the "set hvac mode" service like this:
service: climate.set_hvac_mode
data:
  hvac_mode: "off"
target:
  entity_id: climate.condiz_zona_giorno

@skydado please try with just released version v0.3.6 I hope it fixs


After installing it gives me error.

startup failed:
settings file 'F:\Projects\Tabs\android\settings.gradle': 3: unexpected char: '' @ line 3, column 127.
ules\react-native-vector-icons\android')

Having the same issue.
Reverting to 5.0.0 now, as it works there fine.

In:
/android/settings.gradle
Replace:
include ':react-native-vector-icons' project(':react-native-vector-icons').projectDir = new File(rootProject.projectDir, '..\node_modules\react-native-vector-icons\android')
With:
include ':react-native-vector-icons' project(':react-native-vector-icons').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-vector-icons/android')

guys every time when you link any dependency, kindly check in setting.gradle, there sometime by default, auto linking places '' in path of dependency, just replace'' with '/'.

Thanks a lot. @sobanarshad85 @TingAli

Thanks!!

Thanks!!


[PE-D][Tester E] Cosmetics when one one order exists in order pane.

There are these blue bars appearing after the one and only order in the order pane. Not sure if it is intended.

Labels: severity.VeryLow type.FunctionalityBug
original: zlimez/ped#4

Duplicate issue. Refer to #153 for all details.


fix(constants): move constants into src and exclude from esdocs

Pull Request Test Coverage Report for Build 604

0 of 1 (0.0%) changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+2.01%) to 39.797%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/utils/StoreProviderWrapper.js
0
1
0.0%

Totals

Change from base Build 601:
2.01%

Covered Lines:
413

Relevant Lines:
841

💛  - Coveralls


Add support for Python 313

These ServerErrors are probably due do some changes in openrpc. Python 313 uses openrpc-10.3.2 (as it is not yet cached, contrary to the other ones)

Note that it is still possible to use PyLECO with the integrated fallback version, just uninstall openrpc.


is it safe to upgrade rocksdb version?

is it safe to upgrade rocksdb version? Currently used in git is 5.0.2, latest 5.1.4

it's safe for the data, but may be with new bugs in latest version.


Decl'HDF5 does not handle memory selection without explicit dataset

if no dataset is specified, the memory selection is not taken into account

mentioned in commit<PHONE_NUMBER>3d8327ae11947adc6abb8f0d0ed496

closed via merge request !168

closed via commit<PHONE_NUMBER>3d8327ae11947adc6abb8f0d0ed496


Please add examples for setting verbosity on the CLI for dotnet build commands

Can there be examples for the verbosity (-v) option, please?  I've tried setting it to "q" and "quiet" and even "0" and it still spits out all of the build warnings, when I'd really like it to only output the errors (if there are any).
(We review and correct as many warnings as we can when we do updates and local builds so we see them and clean them up, but we use the CLI "dotnet build" for executing the tests and the whole log ends up getting stored, and keeping all the build warnings there just takes up significant extra space and makes reviewing the logs there more painful.)

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

ID: 910cd365-d63a-00dc-417c-db017f83bf6f
Version Independent ID: 5e495ddd-140e-de5c-a793-d4a9f88be51e
Content: dotnet build command - .NET CLI
Content Source: docs/core/tools/dotnet-build.md
Product: dotnet-fundamentals
Technology: dotnet-cli
GitHub Login: @tdykstra
Microsoft Alias: tdykstra

Associated WorkItem - 57938

Msbuild prints out warnings and errors at all verbosity levels. One thing you could try is running dotnet build twice, throwing away the output from the first run. If you only had warnings, the second run won't have to compile and so won't generate warnings. If there are errors the second run will recompile and you'll get all the warnings and errors.

Thanks for contacting us. We believe that the question you've raised has been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.

Actually, I did find a way to do it from Node without running the build twice (which probably would have cost some extra time) --
ex.execSync(dotnet build "${testProjectPath}" -v q \/property :WarningLevel=0 -c ${configFile}, { stdio: "inherit", timeout: 90000});

Thanks for reporting that - I'm adding a note about use of the WarningLevel property to the article.


Various QOL improvements

I plan to add a lot of quality of life improvements to Alpha 2. Such as:

[ ] randomized animatronic spawn locations, so you can't just camp one spot
[ ] change UI a bit #4 (make stuff better, e.g. custom textures for camera buttons)
[x] allow switching between items (e.g. flashlight <-> camera) to support #6
[ ] make Nirill AI actually a threat #9
[ ] ambient sounds (maybe)
[ ] do some balancing #3
[ ] fix many hidden bugs nobody would never notice

I will probably expand this list, as I plan to make Alpha 2 a big update. I will also take suggestions from the comments (so basically only from @Zenitsuy)

You can now switch between using the flashlight and using the camera.
The item in use is highlighted in the HUD.

Added a beep sound when pressing buttons, also added two new options: master_volume and sfx_volume.


WIP: initial working tests

I got it to work on my machines (ubuntu 16.04 + ubuntu 18.04). Next step should be to get it working in Zuul. As LXD is harder to install in CentOS/Fedora than in Ubuntu, I would start with Ubuntu and extend the pipelines in another PR for CentOS/Fedora.
PR Goal: Implement a full integration test with ubuntu in zuul.

In ubuntu you have to prepare LXD in the following way:
- name: Install LXD as a snap
  shell: snap install lxd
  register: _snap_install_result
  changed_when: not(_snap_install_result.stderr is search('already installed'))

- name: Set fact for LXD preseed config
  set_fact:
    _lxd_preseed_config:
      config: {}
      cluster: null
      networks:
        - name: lxdbr0
          config:
            ipv4.address: auto
            ipv6.address: none
          description: ""
          managed: true
          type: ""
      storage_pools:
        - config: {}
          description: ""
          name: default
          driver: dir
      profiles:
        - name: default
          config: {}
          description: ""
          devices:
            eth0:
              name: eth0
              nictype: bridged
              parent: lxdbr0
              type: nic
            root:
              path: /
              pool: default
              type: disk

- name: Create LXD preseed file
  copy:
    content: "{{ _lxd_preseed_config | to_nice_yaml }}"
    dest: /tmp/lxd-preseed.yml
  register: _lxd_preseed_file_result

- name: Configure LXD with preseed file
  shell: cat /tmp/lxd-preseed.yml | lxd init --preseed
  when: _lxd_preseed_file_result is changed

Ping me on irc when ready.


SIDENAV Android 5.0 Close method doesn't work

Bug, feature request, or proposal:
[Android 5.0, default browser]
There is no possibility to close sidenav.

@beatadelura Please follow the issue template, this really isn't enough information to investigate (at the very least, the template code for the sidenav).


Add a noise when a notification is sent

maybe make the noise different depending on what the notif is for?

Hey I think I might be able to help you with this!


onTamperDetected is executed when running on physical device

Hi,
Can you tell me under what conditions this plugin would detect it as a tampering case?
I enabled this onTamperDetected feature in android and found that it was invoked on a physical device (developer mode is enable) and simulator as well.  Is this expected behaviour? for example, it restricts the app must be download from google/Apple Store?
Or does it means I did something else wrong? like the expectedSigningCertificateHash is wrong?
Please help. Thanks

Hello,
application is considered tampered if it has incorrect package name or if it was signed/resigned with an unknown signing key (signing certificate mismatch). If the application is installed from an untrusted application store, onUntrustedInstallationDetected is triggered. Please verify, that your expectedSigningCertificateHash is correct. You can use this link for Base64 -> Hex conversion: https://base64.guru/converter/decode/hex
We will try to add expectedSigningCertificateHash checks to the next version of Talsec.
Talsec Team

onPackageTamperDetected is getting called when I am installing the release build in emulator as well as real device. I have certain doubt regarding the expectedSigningCertificateHash.

sha256 value is in the format 'xx:xx:xx:xx:xx' right? So should we covert that to Base64 format?
I converted to Base64. format using the code base64.encode(utf8.encode(xx:xx:xx:xx:xx)). Is it the right way?
The above link provided converts base64 to hex value and I am not getting back mu sha256 value from the encoded one. So should I convert sha256 to hex and then hex to base64?

Please revert at the earliest as I am wanna make sure all the checks works before continuing my work. Thanks is advance.


test: unit test for cri/stream/errors.go

Signed-off-by: YaoZengzeng<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

#1756
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1909 into master will increase coverage by 0.12%.
The diff coverage is n/a.


bloodhound AJAX options are missing - POST not possible

v0.11.0 omitted the ajax options for prefetch and remote, it seems that the 'GET' is now hardcoded.
how can a POST operation be preformed?

You'll want to use the prepare option. This change was made to make things more generic so the transport mechanism could be swapped out. Here's an example of how you'd do it:
function prepare(query, settings) {
  settings.type = 'POST';
  return settings;
}

var b = new Bloodhound({
  remote: {
    // ...
    prepare: prepare
  }
});

but that option is missing from prefetch...

That it is... woops. I'll get that fixed for v0.11.1 (will probably be released tomorrow). Thanks for the report.

thanks, will be waiting for that

PR is up, see #1184. I'll get it merged into integration-0.11.1 tomorrow before I do the release.


Corrected haskell.nix pin

Bring the haskell.nix version pin in line with the other repos.

bors r+


[MM-19448] Get user preferences on WebSocket reconnect

Summary
Updated package.json for mattermost-redux hash to resolve issue where Favorites were not updating when mobile app was not in foreground.
Actual Redux changes are here: https://github.com/mattermost/mattermost-redux/pull/956
Ticket Link
https://mattermost.atlassian.net/browse/MM-19448
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] All new/modified APIs include changes to [mattermost-redux]

Device Information
This PR was tested on:
iPhone X 12.4 (Simulator)

Will update the hash on the release PR.


Allow for AWS longer resource names

Current CF checks resource name validity to a short resource name only.
This change allows for a 17 characters resource name (introduced in 2017) while still allowing for 8 characters.
See https://aws.amazon.com/about-aws/whats-new/2018/02/longer-format-resource-ids-are-now-available-in-amazon-ec2/

We've updated the solution to use SSM parameter store AMI IDs, which do not have the issue that this PR fixes.


ValueError when adding players and BAD REQUEST error doing /whois with multiple registered characters to a user

Here are two examples of two character names that yielded the same error.
/stalk addchar Friendly Maker,Twisted Core
ValueError: invalid literal for int() with base 10: ''
/stalk addchar peasize death head - swartzy, peasize death head
ValueError: invalid literal for int() with base 10: ''
Other character names are able to be registered to these users, just not those characters.
Also, we have been registering our hunted character list to a user since the bot currently lacks a hunted list. When we register about +10 players to the user, it starts yielding this error.
/whois HUNTED!!!!
HTTPException: BAD REQUEST (status code: 400)
Sorry, at this time, I do not have access to the server log. If you need it, just say so and I can paste what is says at a later time. BTW, love this bot! Ty for setting this up, it's been awesome for us! <3

The console log would be really useful.
About the HTTPException error, it's because the character list gets too big and exceeds discord's message length limit, so it throws an error. The hunted list feature is something that has been on my to-do list for a while, but right now I'm working on rewriting for a future update.

Okay, I'll post it as soon as I can, thanks for the past reply!

I found the reason for the error, these characters have deaths without a level:

That last death is causing the problem, cause it doesn't contain a level, so it's causing errors in the script. I don't play in pvp, so I don't why he has an entry like that, if you have any explanation for that, let me know.
Either way, I will fix it so it ignores it.

 It's rare but it happens. I believe it happens only when no one takes a full frag on you and they only assist.

Alright, for now those deaths will be totally ignored as they kinda break the way deaths are managed by NabBot.

Oh, i know why! It's because that character was in party with the people that killed him, so they don't get counted for a full frag.


gadget-container: Liveness probes are missing

The gadget Pod doesn't include any liveness probe, if there is any crash it'll be unnotice and the Pod will became unusable.
https://github.com/kinvolk/inspektor-gadget/blob/669dcdb204b12b19a0a67b6447cc4c03ea40357f/gadget-container/entrypoint.sh#L136
A liveness probe checking that the gadget tracer manager is accepting grpc requests inside the pod should be added. Kubernetes doesn't support grpc probes, probably https://github.com/grpc-ecosystem/grpc-health-probe is a good tool to use<EMAIL_ADDRESS>

The gadgettracermanager binary is both the grpc client and server. It could be used as a client in the liveness probe.


More 508 compliance enhancements from NPS

@regan-sarwas -- Are you able to please make a PR with the new 508 enhancements you showed Allen and me on the Aug 4, 2015 webcast? We'd love to review these for inclusion in a release later this year.

@oevans - It is on my to do list, and I look forward to it. I just need to create a clean PR - some of the look/feel/branding got intermixed in my 508 work.


Convert AllMeetings component to function component

Currently this is a class component. Convert the existing code by implementing it as a function component in React.

I would like to work on this @sharmaaditya570191 . Please assign it to me.

I can work on this issue.Please assign it to me.

I want to work on this.Please assign

Hi, GSSoC20 participant here. I wish to work on this issue. Please assign this task to me.

@sharmaaditya570191 Can I work on this ?

@sharmaaditya570191 can I work on this issue?

@sharmaaditya570191 is the issue still up for grabs?


math module import question

I'm preparing some extra math functions to make a pull request. Currently, SQRT has an import statement within itself, see below. Shall I keep it like that, or shall I add math to the import statement in the kernel?
CODE SQRT    import math; dpush(math.sqrt(dpop())) END-CODE

I think adding the import math statement to the kernel would be fine.


improve testing interface

Currently, running automated tests using clichain (and click.testing) requires the use of clichain.cli._get_obj and clichain.cli._app.
example test code:
from click.testing import CliRunner
from clichain import cli

tasks = cli.Tasks()

[...]

args = ['foo', '-opt', 'bar', '-op2']
inputs = '\n'.join('12345')

runner = CliRunner()
obj = cli._get_obj(tasks)
return runner.invoke(cli._app, args, obj=obj, input=inputs)

a test interface should be available, both for testing the framework itself and code using clichain, and a testing section should then be added in the documentation.

created add_testing_interface branch