ImportError: cannot import name dictkeys on Python 2.7.3

using python 2.7.3
using redis-py-cluster 0.2.0
when trying to do a:
from rediscluster import RedisCluster
or
from rediscluster import StrictRedisCluster
receiving:

from rediscluster import RedisCluster
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python2.7/dist-packages/rediscluster-0.5.3-py2.7.egg/rediscluster/init.py", line 12, in
from rediscluster.cluster_client import StrictRedisCluster
File "/usr/local/lib/python2.7/dist-packages/rediscluster-0.5.3-py2.7.egg/rediscluster/cluster_client.py", line 5, in
from redis._compat import (
ImportError: cannot import name dictkeys

Sorry for the red herring.....
this error occurred after installing reds-py-cluster via pip.
after installing from source, ran successfully.
Thanks

@stevewoolley Also i noticed that that stacktrace do not belong to my lib because the version is wrong. It states that you are using the package rediscluster with version 0.5.3 but sinc this lib is only in version 0.2.0 you must have installed the wrong package :]


Dan/linking-pr-docs

Public Docs for anyone who might use PR validation. Also greatly slimmed down from current docs, and hopefully easier to read.
Don't know if location is great. Maybe it should be in a Docs dir or something?

/azp run imodel-native


New ACL

Work in progress

It finally passes all the tests, I am currently skipping tests for Groups (I have commented out Group implementation), for Owner-only (since we are not using it yet - at least not currently implemented) and for Glob.
I also commented the clean up since I changed the files I used for testing, so it became obsolete


Choco requirements

Choco is requiring more information for a release.  See this https://chocolatey.org/packages/ipfs-mount/0.2.1

Needs a VERIFICATION.txt file, see https://github.com/chocolatey/package-validator/wiki/VerificationFileMissing


specify pass or failure based on returncode and regex

@vsoch
At the moment buildtest has no mechanism for tweaking pass/failure other than 0 or non-zero for exit code. buildtest can't support expected failure test.
For example at stampede2 we have this test that is expected to fail since -n is required during job submission.
version: 0.0.1
missing_total_tasks:
  description: This job fails because '-n' option is required
  type: script
  run: srun -p normal -N1 -t 00:10 hostname

Here are few ways we can address this.
Match by return code
version: 0.0.1
missing_total_tasks:
  description: This job fails because '-n' option is required
  type: script
  run: srun -p normal -N1 -t 00:10 hostname
  status:
    returncode: 1

This test is expected to pass if return code is 1. This would be checked after execution and we would need to process return code match after job execution.
login4.stampede2(996)$ srun -p normal -N1 -t 00:10 hostname

-----------------------------------------------------------------
          Welcome to the Stampede2 Supercomputer
-----------------------------------------------------------------

--> Submission error: please define total core count with the "-n" option
login4.stampede2(997)$ echo $?
1

In addition, we can have a regular expression that can be used to read output of stdout or stderr stream. In this case stdout and stderr will refer to the .out and .err file where output and error is written.
For example if want to search for start of string --> Submission error on stderr stream using re.search. I think we have to limit on the module we can let user's use such as re.search, re.match so they dont have unexpected results.
version: 0.0.1
missing_total_tasks:
  description: This job fails because '-n' option is required
  type: script
  run: srun -p normal -N1 -t 00:10 hostname
  status:
    regex:
      stream: stderr
      exp: "^--> Submission error"
      module: re.search

In these two examples, i guess the schema should also one of the two keys returncode or regex. We shouldn't let user do a returncode match and regex at same time to determine if test is passed.
Let me know your thoughts on this?

This is spot on! I don't think we need to specify "module" under regex - it should be implied that it's re.search, and then it could pose a lot of bugs or security issues if some custom function is provided that needs to be imported. So let' add a status -> returncode that defaults to:
version: 0.0.1
missing_total_tasks:
  description: This job fails because '-n' option is required
  type: script
  run: srun -p normal -N1 -t 00:10 hostname
  status:
    returncode: 0

If unset, and of course the user can deviate from that for some special status to indicate success. The one potential misleading thing that might happen is if the which statement doesn't find the executable, the error code would be 1, and that wouldn't be the error code for the script but for that call (but the test would pass).
And for regex, I'd tweak to just be:
version: 0.0.1
missing_total_tasks:
  description: This job fails because '-n' option is required
  type: script
  run: srun -p normal -N1 -t 00:10 hostname
  status:
    regex:
      stream: stderr
      exp: "^--> Submission error"

okay let me take a shot at this on the schema before we add this support in framework.

Sounds good!


HOW can I get metrics and monitor my job，so frustrated to work with argo

Discussed in https://github.com/argoproj/argo-workflows/discussions/6457

Originally posted by bigc2000 July 30, 2021
http://localhost:2746/metrics
but without  useful metrics.
I want to monitor my step/task, but I tried as examples/custom-metrics,  and failed.
$ argo  -n argo list
NAME                     STATUS      AGE   DURATION   PRIORITY
hello-world-xxlsx        Failed      59m   47s        0
dag-task-bhvlt           Succeeded   1h    30s        0
sidecar-dind-kfbtr       Succeeded   1d    3m         0

$ argo -nargo get hello-world-xxlsx
Name:                hello-world-xxlsx
Namespace:           argo
ServiceAccount:      default
Status:              Failed
Message:             child 'hello-world-xxlsx-2783481395' failed
Conditions:
 PodRunning          False
 Completed           True
Created:             Fri Jul 30 11:40:08 +0800 (1 hour ago)
Started:             Fri Jul 30 12:07:01 +0800 (35 minutes ago)
Finished:            Fri Jul 30 12:07:48 +0800 (34 minutes ago)
Duration:            47 seconds
Progress:            2/2
ResourcesDuration:   42s*(1 cpu),42s*(100Mi memory)
Output Parameters:
  rand-int-value:    7

STEP                  TEMPLATE    PODNAME                       DURATION  MESSAGE
 ✖ hello-world-xxlsx  steps                                               child 'hello-world-xxlsx-2783481395' failed
 ├───✔ random-int     random-int  hello-world-xxlsx-3322177831  6s
 └───✖ flakey         flakey      hello-world-xxlsx-2783481395  37s       Error (exit code 1)

This workflow does not have security context set. You can run your workflow pods more securely by setting it.
Learn more at https://argoproj.github.io/argo-workflows/workflow-pod-security-context/

Is argo monitor and metrics production ready？

@bigc2000 trying to understand what issue are you facing? Are you not seeing the custom metric on http://localhost:2746/metrics?


Not a real issue - uninitialized variable

Hello, as stated in the title - it's not an issue, but is a bit annoying: the library compiles smoothly under Arduino Ide, but under Visual Studio with VisualMicro extension got an error in publish method. The source of that error is in uninitialized variable packet id. It's then set if QoS > 0, if QoS=0 remains uninitialized. Assigning any value to it doesn't disturb anything - pocketid is used (in the next step in the library) only if QoS>0, but mitigates annoying compiler errors.
And -last but not least - thank You for that library, I've been testing it for some time with SIM868 GSM module and it works great.
gimbus109

@gimbus109 , thank you for highlighting the problem.


Can't change primary display

I cant change primary display when multimonitor ?

Is that a question or a finding?
Please have a look to https://github.com/FreeRDP/FreeRDP/wiki/BugReporting and add more information.

If you have a 3 monitor setup and connect to Windows 10, using /f /multimon /monitors:0,1,2 the "main" desktop in Windows 10 is always the far left (or monitor 0 in my case). I'm not sure how to control this but in Windows if you right click the windows desktop and select Display Settings, there is no option to alter the "main" display.

it would be great if there was a way to set which display should be considered the "main" display.
I'm using FreeRDP version 2.0.0-dev (git 5258a980f)

@jasonblewis I wonder if this actually is possible for remote session at all. Did you try if it's possible with Microsoft's client?

Microsoft client take the client primary display to be the primary display. Freerdp always take the right screen to be the primary display. This is the difference. Freerdp need to check which screen is the primary to send it to the host after.

@jtremblaytdst can you try https://github.com/FreeRDP/FreeRDP/pull/4187 ?

Working here now, reopen if still an issue.

For me, with Ubuntu 18.10, this is working on X but not on Wayland -- on Wayland the wrong monitor is considered primary by remote Windows.


class labels significance

Where can I get the mapping between class labels and class names in "run_tf_detector.py" ?

Hi @saikatdutta, please see experiments/megadetector_v3/label_map.pbtxt for the class label mapping for the MegaDetector (version 3, to be released shortly; in version 2 there is only one class, 1:animal).

OK, but when I ran the code on megadetector_v2, I got some labels other than 1(55,83 etc.). What are those labels actually?

The megadetector was warm started with COCO weights and we left all the layers in, so the output technically has 90 classes (the COCO stuff classes). But the model is only meant to be applied to camera trap photos, and only class 1 (and when we release v2, class 2 as well) should be considered meaningful.


Polygons with arcs do not have the correct area

Did you guys fix this bug already?
https://geonet.esri.com/thread/170662

But its almost a year old. How hard can it be to calculate an area of a surface that has curves?

This issue was added as ENH-000095710 last year. To support this we need to port a geometry library from ArcGIS Desktop. There would be other benefits of this port, like support for more spatial selections (currently we only support envelope intersects), but it's requires a significant resource commitment that we can't make at this time. We would really like to do this, but other commitments make it unlikely.

Sorry, didn't intend to close the issue. Hit the wrong button.

This bug is now 3 years old.

Oh I missed our yearly post.
Still not fixed!

Another year and another curvy shape has no area.
Still not fixed!

I'm slacking, missed 2022. 6 YEARS NOW, WOW.

🤣


Crash when encoding

Hey, I am using your qr code encoder on Heroku (running in Sidekiq bg job). Everything is working like a charm, just today I've received report, that encoding crashed in one case and I can't see any reason why :/
MojoMagick command failed: convert. (Exit status: 1)
    Command: convert  -format rgb -depth 8 -size 53x53 /tmp/mojo20131213-2-1j1ppwl.rgb -scale 1060x1060 -bordercolor "\"#ffffff\"" -border 40x40 /app/tmp/generator/qrcode20131213-2-1ilrptg.png 2>/dev/null
  /app/vendor/bundle/ruby/2.0.0/gems/mojo_magick-0.5.3/lib/mojo_magick.rb:88:in `raw_command'
  /app/vendor/bundle/ruby/2.0.0/gems/mojo_magick-0.5.3/lib/mojo_magick.rb:159:in `convert'
  /app/vendor/bundle/ruby/2.0.0/gems/qr4r-0.3.5/lib/qr4r.rb:48:in `encode'

Any hints?

if you are still having issues, please let me know and upload the image that is causing issues.  I'm closing this issue


Update wasmtime to latest version.

Following up on some API changes to the environment traits in
bytecodealliance/wasmtime#2115, this PR updates the git version of the
wasmtime submodule and updates lucetc accordingly.
The changes are basically just renamings, along with a removal of a
RelocSink trait method that was previously unused.

Closing in favor of #610 as CircleCI won't work with PRs from branches in forks (thanks pchickey for the heads-up).


0.0.6 Milestone

We are working following towards the 0.0.6 release:

[x] Upgrade aws-java-sdk to 1.11.119+
[x] Support RequestMetricCollector per request
[x] Support Kinesis Firehose
[ ] Enhance AsyncClient support

Do you need any help with those two remaining features?

Thank you but I’m good.
I am working on the v0.0.6 branch. Only one feature left. I send PR when it's done and have another member review it.
Probably we will release version 0.0.6 by the end of this month :)

Cool. :)


Add bolbs and picard facepalm

If i missed any formatting or you want me to rename anything, let me know

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I also added Forge Squirr

I also added Forge Squirr


Issue with /docs/user-guide/jobs/

Issue with /docs/user-guide/jobs/
When following the documentation, on section jobs, "Running an example Job". The examples in the documentation do not match with the result on the local instance of our kubernetes cluster
Documentation example, creating the job.yaml file and creating the job
The result should be:
$ kubectl describe jobs/pi
Name:		pi
Namespace:	default
Image(s):	perl
Selector:       controller-uid=b1db589a-2c8d-11e6-b324-0209dc45a495
Parallelism:	1
Completions:	1
Start Time:     Tue, 07 Jun 2016 10:56:16 +0200
Labels:         controller-uid=b1db589a-2c8d-11e6-b324-0209dc45a495,job-name=pi
Pods Statuses:	0 Running / 1 Succeeded / 0 Failed
No volumes.
Events:
FirstSeen	LastSeen	Count	From			SubobjectPath	Type		Reason			Message

1m		1m		1	{job-controller }			Normal		SuccessfulCreate	Created pod: pi-dtn4q
On my local machine the result is the following:
host-44-11-1-22:~ # kubectl describe jobs/pi
Name:           pi
Namespace:      default
Image(s):       perl
Selector:       controller-uid=2d24e2be-79c4-11e6-aef4-fa163e39bb70
Parallelism:    1
Completions:    1
Labels:         controller-uid=2d24e2be-79c4-11e6-aef4-fa163e39bb70
job-name=pi
Pods Statuses:  0 Running / 0 Succeeded / 0 Failed
No volumes.
No events.
host-44-11-1-22:~ # cat job1.yaml
apiVersion: batch/v1
kind: Job
metadata:
name: pi
spec:
template:
metadata:
name: pi
spec:
containers:
- name: pi
image: perl
command: ["perl",  "-Mbignum=bpi", "-wle", "print bpi(2000)"]
restartPolicy: Never
host-44-11-1-22:~ # kubectl get pods --show-all
host-44-11-1-22:~ #
Why do I have no pods created and 0 Succeeded Pods status?
Thanks,
razvan

@razghe you need to wait for a few seconds for the job controller to pick the new job and create pods. Please give it another try and wait a few seconds, the pods should be there. If the problem still persists ping me.

I've just verified this is working as expected and due to no answer from the original owner I'm closing this issue. @razghe if you can provide me with a reproducer feel free to reopen this issue.


merge MONDO_0006073 'adenomatoid odontogenic tumor' with MONDO:0004230 'adenomatoid tumor'

merge MONDO_0006073 'adenomatoid odontogenic tumor' with MONDO:0004230 'adenomatoid tumor'

From NCIT:
Adenomatoid odontogenic tumor should not be merged with adenomatoid tumor. The former is a benign neoplasm that arises from tooth-forming tissues and is composed of odontogenic epithelium. The latter is a benign tumor that is composed of benign mesothelial cells. It occurs in multiple anatomic sites that contain mesothelium-not to be confused with adenomatoid odontogenic tumor.


Uplifted google cloud images in tests to their latest versions

Uplifted google cloud images in tests to their latest versions.

Hi @RamazanYapparov,
unless there is an issue with some newer version of emulators, I don't think it makes sense to uplift the image versions. The images themselves are tested by Google anyways.

Hi @RamazanYapparov,
unless there is an issue with some newer version of emulators, I don't think it makes sense to uplift the image versions. The images themselves are tested by Google anyways.


Emoji who are a ZWJ combination don't get converted from colons to unified with a skin-tone

Sorry for the rather verbose title. Here's a JSbin showing the bug
http://jsbin.com/zagenas/edit?html,js,output
Tried under Chrome and Safari on macOS 10.12.6

good catch! fixed on trunk
this had never worked as intended - for any emoji with a skin tone, the unified output always added the skin tone codepoint last, regardless of whether it was defined or not. this worked for most ZWJ sequences, but not ones added in Emoji 4.0 and later. Not sure how I never noticed this before.

No worries! Thanks for the quick fix on a Sunday 😁


Make .apk signed with sha256

The feature
It would be nice if we could verify the integrity of the .apk file.

Here's what Signal and Proton do:
https://signal.org/android/apk/
https://proton.me/support/verify-apks
apksigner verify --print-certs SpamBlocker.apk
Signer #1 certificate DN: C=f, ST=e, L=d, O=c, OU=b, CN=a
Signer #1 certificate SHA-256 digest: 7b1ce727856f3427eab1fadfad6c9730cd4e6ba201661547f009206377dffb58
Signer #1 certificate SHA-1 digest: 8401610cf977f4a8e6f3b25f5d3ea94367e9396a
Signer #1 certificate MD5 digest: 3d466485d721c3e6805f58743ad93aae

Do you mean this?

Currently all apks are signed by this signing key, including the action builds.
The sha256 hash is:
7b1ce727856f3427eab1fadfad6c9730cd4e6ba201661547f009206377dffb58
I'll add this to the readme.


nanotron/the-pile-for-doremi is empty

https://huggingface.co/datasets/nanotron/the-pile-for-doremi/tree/main
I cannot download the dataset, could you please check it?

@Tonyhao96 Hey. There was a bug in DoReMi's implementation, we have fixed it [link] (not merged yet) and rerun the experiment on Fineweb2 (a up comming release dataset)... So the previous experiment results are not legit. Stay tune for the new release
For the new experiment result, check the last images of this tweet: https://twitter.com/xariusrke/status/1774089131351584852


MUSIC ASSISTANT WILL NOT WORK WITH HOME ASSISTANT 2023.3

IMPORTANT NOTICE
Music Assistant is NOT compatible with Home Assistant release 2023.3 (and upwards) due to an unfortunate compatibility issue. At this time it is not possible to fix this issue I'm afraid.
Because a complete overhaul of Music Assistant was already in the making, version 2.0, we have decided to already release an early version of the 2.0 beta so people can get going from there. Follow us on discord to get the latest news about the beta and give and discuss feedback about it or follow progress and/on the backlog:  https://github.com/orgs/music-assistant/projects/2
What to do next ?
Please postpone your upgrade to Home Assistant 2023.3
OR
Live a few weeks without Music Assistant
Thanks for your understanding!

Following up: It was my intention to still provide fix updates for the current (v1) version of Music Assistant as it is on HACS but unfortunately the upstream dependency issue is bad enough to make it near impossible, hence my decision to move all development focus to the 2.0 version. It is not a bad intention but just bad luck. Sad to hear that some people seem to think otherwise.

The new version of Music Assistant will run as a standalone application. The reason for this is exactly why it broke now, you can not have two captains on one ship. Both Home Assistant and Music Assistant are very large and complicated projects and it was a very bad idea of me in the first place to run the "core" of Music Assistant within Home Assistant itself.
The 2.0 approach is that the Music Assistant core runs on its own and the Home Assistant integration is just a connector, making it resilient to the kind of dependency issues that killed the v1 version.
For some this may sound as bad news but it is actually very good news because now we can have a much more fine grained control over the players and playback. You already see the first results of this in the early 2.0 betas: Full metadata is displayed.
There is still a lot of work to do on the 2.0 code but his feels like a very strong foundation to continue and make it into something awesome.
Running the Music Assistant Server
Preferred method: Home Assistant Add-on
By far the most convenient way to run the Music Assistant Server is to install the Music Assistant Add-on:
Add the Music Assistant repository to your Home Assistant instance.
Install the Music Assistant add-on.
Add repository on my Home Assistant
Alternative method: Docker image
An alternative way to run the Music Assistant server is by running the docker image:
docker run --network host ghcr.io/music-assistant/server:2.0.0b4

Replace the 2.0.0b4 tag with the correct version. You must run the docker container with host network mode and the data volume is /data. If you want access to your local music files from within MA, make sure to also mount that, e.g. /media. Note that accessing remote (SMB) shares can be done from within MA itself using the SMB File provider.

I have MA v1 installed and now I can no longer remove it ?!
If you already upgraded to HA 2023.3.x you have two options:

Manually remove MA from the "core.config_entries" file within the .storage subfolder of HA config.
Restore your backup of HA 2023.2, uninstall MA and upgrade to HA 2023.3 again.

BETA software is not yet polished
Please understand that we rushed the release of the early beta due to the major dependency conflict with HA 2023.3.x so not all features are ready. Most important, at this time we only have the server component ready, the actual "core" of Music Assistant and we're fixing the last bugs to get that in a stable state. After that we will focus on having the Music Assistant integration working again so you can control your music from within HA. Ultimate goal is to just submit the integration part as an official component for HA but we might reinstate the HACS version to gather some beta feedback first and/or to get people started sooner.
Follow progress of the new v2.0 version here:
https://github.com/orgs/music-assistant/projects/2/views/1

I tried but doesn't work. :(
Raspberry Pi 4 rpi4-64 Argon One
Home Assistant 2023.1.7
Supervisor 2023.03.1
Operating System 9.5
Frontend 20230110.0 - latest

Deleted old (HACS) Music Assistant on Settings/ Devices & Services/ Integrations.
Deleted source on HACS.
Restarted Home Assistant.
Added this link: https://github.com/music-assistant/home-assistant-addon
Refreshed site.
Searched and installed Music Assistant Beta (2.0.0b5).
Clicked the Start button, but not changed on Runing and green color point, it is still red color.
Checked the Music Assistant Log:
2023-03-14 21:50:16 INFO  music_assistant  -- Starting Music Assistant Server (a473959f8ad94c0e82xxxxxxxxxxaad8) on port: 8095 - autodetected IP-address: 192.xxx.x.xxx
2023-03-14 21:50:17 INFO  music_assistant.streams  -- Started stream controller (using ffmpeg version 4.3.5 with libsoxr support)
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded metadata provider MusicBrainz Metadata provider
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded plugin provider Frontend
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded metadata provider TheAudioDB Metadata provider
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded player provider Chromecast
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded music provider URL
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded player provider UPnP/DLNA Player provider
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded player provider SONOS
2023-03-14 21:50:49 INFO  music_assistant.metadata  -- Start scan for missing artist metadata
2023-03-14 21:50:49 INFO  music_assistant.metadata  -- Finished scan for missing artist metadata
2023-03-14 21:50:49 INFO  music_assistant.providers.slimproto  -- Starting SLIMProto server on port 3483
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded player provider Slimproto
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded plugin provider JSON-RPC API
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded metadata provider fanart.tv Metadata provider
2023-03-14 21:50:49 INFO  music_assistant  -- Loaded player provider Airplay
2023-03-14 21:50:50 INFO  music_assistant.players  -- Player registered: exxxxxxa-f6f3-a42e-c27a-1xxxxxxxxxx8/Kitchen speaker
2023-03-14 21:50:50 INFO  music_assistant.players  -- Player registered: 3xxxxxxd-3184-47eb-a1a6-3xxxxxxxxxx8/All speakers
2023-03-14 21:50:59 INFO  music_assistant.players  -- Player registered: 5xxxxxxc-dbba-6069-2b1b-2xxxxxxxxxxa/Bathroom speaker
2023-03-14 21:51:36 INFO  music_assistant.players  -- Player registered: 4xxxxxx6-8ace-0913-4623-cxxxxxxxxxxd/Bedroom speaker

The speakers are Google Nest Audio.
But doesn't work. :(

@andrewigali why do you keep hijacking these threads when I have told you to open a new issue?

@andrewigali why do you keep hijacking these threads when I have told you to open a new issue?

Because i just a little bit speak in English and i don't use the github/ issue but now tried.
Please delete this comment.

Hello Marcel,
I try to switchover to version 2.0.0b and I faced with 2 issues:

After the addon instaled Music Assistant is inaccessable via the link within the addon, if Home Assistant access set it up with https via duckdns, like: https://mydns.duckdns.org:5643/d5369777_music_assistant_beta/dashboard (dns and port is just example)
Using the IP is accessable otherwise, but only http: http://<IP_ADDRESS>:8096/#/
The other issue is, that some players automaticaly recognised on my network, but the one I using, the default mpd.music_player unfortunately not among them. In 1.x during the initial configuration I can select what players I want to use, but in 2.0 there is no such function to add a player.
Otherwise, I really like the Music assistant, at the moment I haven't even updated HA because of this and stil using 1.x version of Music assistant. Congratulations on your work!

@szemod please confirm that before you tried use use v2 that you disabled the v1 integration in HA SETTINGS?

Someone asked a similar question in discord. This is the response

Heya, is adding mpd as a player in the feature list of V2. I use snapcast and that works fine with mpd.

Well, it will be if we allow HA players again as players for MA.... So i'd like to have some of the most popular platforms native in MA and all other can be integrated by using the HA connector.

So you will have to wait a little while for this to be implemented. Sorry for the inconvenience.

Someone asked a similar question in discord. This is the response

Heya, is adding mpd as a player in the feature list of V2. I use snapcast and that works fine with mpd.

Well, it will be if we allow HA players again as players for MA.... So i'd like to have some of the most popular platforms native in MA and all other can be integrated by using the HA connector.

So you will have to wait a little while for this to be implemented. Sorry for the inconvenience.

Many thanks for your reply! Then I'll need wait until is implemented. I have one more question: The global search field is missing on the HOME page of v2. Is that also planned in the future?

That is currently being worked on https://github.com/orgs/music-assistant/projects/2/views/1

I share my experience.
HACS version MA must be disabled in the Integrations menu.
If you succeeded in installing the MA v2 extension, but it does not start, you must shut down the machine within the HA system and then turn it on again. It is likely that something was stuck/crashed. You should then be able to start and the webUI interface should be available.
Tested:
Raspberry4 rpi-64 Argon One M.2
HAOS 2023.1.7
Currently, there are no entities with the MA v2 extension, automation/call service options are not yet available. For those who care, continue to use the HACS version.
Last working version: HAOS 2023.2.5 and HACS MA 2023.2.1
HAOS 2023.1.7 and HACS MA 2022.12.1 will not work!
So you definitely need to update to HAOS 2023.2.x.
If you are already running HAOS 2023.3.x or later, you must first restore the previously created backup.
If no HAOS 2023.2.x, only from the previous one (e.g. [2023.1.x, then it must be reloaded.
Then install Terminal & SSH in the Settings/Addons menu. Start it and type the following:
if core update --version 2023.2.5 then enter.
(2 dashes)
To keep the system stable, use the above command only when upgrading from a previous version to a larger version! The downgrade is only from a backup!
Tested:
Raspberry4 rpi-64 Argon One M.2
From HAOS 2023.1.7 to HAOS [2023.2.5
MA 2023.2.1 (HACS version)
We hope it will exit the beta state as soon as possible, the new MA v2 extension will also include entities, automatisms/call services, dark theme mode. :)
Also, I recommend that there should be a site on the github site about what/what the given MA v2 version update contains, so that the average user can easily see the changes and the development.

Also, I recommend that there should be a site on the github site about what/what the given MA v2 version update contains, so that the average user can easily see the changes and the development.

Have a look at the link immediately above your post.

Also, I recommend that there should be a site on the github site about what/what the given MA v2 version update contains, so that the average user can easily see the changes and the development.

Have a look at the link immediately above your post.  Also you can join the Discord channel which has lots of discussions about what is happening with the project.

Ok, that site is good, but I think it would be better if we could get information about the given version, what has changed and what has been added.
Example

Yes Marcel does that for full releases for during this beta development phase we are running with the backlog.

Does Browse work in v2.0 or is it something that will be added later on? Clicking on anything does nothing
Thank you

B8 fixed this

Oh! thanks! I hadn't noticed that it had updates!

Oh! thanks! I hadn't noticed that it had updates!

We release a new beta almost every day with bugfixes and the final (missing) features being added.
You can use the backlog to follow along what is being worked on.
When 2.0 is being released there will be a full writeup of the new features and such.
At this point you will have to follow the backlog or join discord to stay updated.
And of course as @andrewigali pointed out, if you just want a stable setup and not toy with beta versions, just stick with the V1 version for now which works rock solid on HA 2023.2.x.

@thermosiphonas in Music Assistant v2.0 you no longer use that workaround with mounting a share but instead you pick the "SMB mediaprovider" for direct access to your remote share

I have a very large library (over 950GB and 120,000 files) and SMB mediaprovider gets stuck all the time. I cannot enter a folder and see the mp3s inside it

We're working win improving the smb provider. I have a new testversion ready tomorrow which should improve things. Are the files hosted on a Windows server or on a (linux) NAS ? If its a powerful NAS you could also consider to run the Music Assistant server directly on the NAS so it has local access to the files (super fast)

I have the files hosted on a Windows server in which Home Assistant is running on VirtualBox

There is a known issue with windows shares that is currently being worked on

You can also just keep the (now not working) Music Assistant integration installed if you want and upgrade it later to the updated integration for 2.0. It just looks a bit messy to have a malfunctioning integration but it can't do any harm.

I see V2 beta is available as a add-on. So what will be the easiest way to migrate over? Is there any documentation for this?

The instructions are above. Your database will be recreated with the new version so there is nothing to be migrated. Note V2 is still in beta (but working pretty well for most)

Thumbs up from me, coming from LMS/Spotty, where there is an issue with LMS and or the Spotify integration, it never worked properly for me and made it almost unusable.  I didn't even know about this project until about a week ago, loaded MA via docker and it's working great so far.  For the first time I can actually listen to stuff on Spotify in every room, without having to constantly intervene to keep it playing.  There are some oddities, some of the controls and UI etc aren't as polished as they could/will be, but for a beta it pretty much does everything I could ask of it, so thank you guys, it already looks like it's going to be a really good solution.

Is there somewhere we should post issues to?  I realise this is beta and you dont want spamming with tonnes of things that are already on the roadmap, but there are a few almost trivial little issues I've come across that may or may not be known.
As a for instance when syncing 1 or more players that have different volume levels before syncing, the group volume slider gets confused, if I change each individual player so they match, the group slider works as expected.

I would like to perform operations in automation.
Which version is expected to have automation settings?
In the link below, which target list contains which one?
https://github.com/orgs/music-assistant/projects/2
Sorry, I'm not good at English. :(

If you have HA >= 2023.3.x installed then you can only use MA V2 BETA. Automations will be available in that in a few weeks.

If you have HA >= 2023.3.x installed then you can only use MA V2 BETA. Automations will be available in that in a few weeks.

Yes, I'm still using HA 2023.2.1 and HACS Music Assistant.  It's just the lack of automation that keeps me from upgrading the HA system and switching to the Music Assistant plugin.
That's why I asked which target list I should look at, check, so that I know that I can update and change.
I'm really glad that Music Assistant exists and I hope that a stable version will be released soon. :)

Ok please open a discussion and ask for some help explaining what you want to do and what you have tried so far.

Dear Marcel will version 2.0 work with new HA 2023.3 onwards , as i had many scripts to say notification then play the music again ? .... I hope it gets sorted all the best Marcel it was awesome while it lasted :)

Version 2 already works with the latest versions of HA. The HA integration to allow automations is a couple of weeks away.

Alternative method: Docker image An alternative way to run the Music Assistant server is by running the docker image:
docker run --network host ghcr.io/music-assistant/server

You must run the docker container with host network mode and the data volume is /data. If you want access to your local music files from within MA, make sure to also mount that, e.g. /media. Note that accessing remote (SMB) shares can be done from within MA itself using the SMB File provider.

I am using HA Container installation, so obviously I've tried the docker version [both by the docker run line you've provided, and by docker-compose that I made].
how can I access the Music Assistant dashboard? I mean - can I access it without HA?
I've tried IP:8095 or IP:8096 [ports that I've found here or in the logs ;)] but with no luck. I've tried to forward those ports to the container but also didn't worked.
it's possible that I'm missing something, but am I? ;)

I am using HA Container installation, so obviously I've tried the docker version [both by the docker run line you've provided, and by docker-compose that I made]. how can I access the Music Assistant dashboard? I mean - can I access it without HA? I've tried IP:8095 or IP:8096 [ports that I've found here or in the logs ;)] but with no luck. I've tried to forward those ports to the container but also didn't worked. it's possible that I'm missing something, but am I? ;)

If you used host network mode (as required in the docs) you can access the local webserver of the MA server on http://ipofyourdockerhost:8095

I've tried that [that's what I meant by IP:8095] - but nothing is showing up.

I've tried that [that's what I meant by IP:8095] - but nothing is showing up.

it really should work (look in the log if it started on port 8095 because it auto picks another port if that port is already taken). Also make sure to use HTTP and not HTTPS and maybe try another browser. 100s of people use it this way.

log was legit. so I've restarted my docker, and to be sure - deleted browser's cache one more time and it clicked. seems it was some cache problem. thanks!

I have been and remain a fan of Music Assistant for a long time.
I was disappointed to learn that the new version of Home Assistant broke the correct operation of Music Assistant.
But I believe that such an advanced product will not be left without a continuation.
I regularly monitor your tremendous work on solving this problem.
And I was pleased to find that the BETA version is already available for testing.
I like the new integration design, it's more modern and clear. New services have been added. I connected my favorite radio stations and even YouTube Music without any problems.
The only thing missing from the previous integration version is support for ESPHome i2s Media Player. Maybe I did not fully understand, but I could not see these players in the list of available in Music Assistant.
Please tell me, did I disable something or are there other reasons for their absence?
Thank you very much for your work.

No you haven’t missed anything. The ESP devices are not yet supported. Go to the player provider poll and express your interest in that over there

Did I understand correctly that support for ESPHome Player has ended due to changes in ESPHome?
On the side of Music Assistant, everything remains the same?

No MA V2 needs to have support added for those devices. Having said that when the HA.integration is written in a few weeks then all HA media player entities will be exposed

Thanks. Wait for update.
Good job!

May be it is a bug, i do not know. Some Players remain in the list when selecting a target audio device. But these playes have been deleted from the player list. Don know why they show up. Suggestion: it would also be nice if offline devices and devices that are "off", do not show up.

Please look for similar or identical existing issues https://github.com/music-assistant/hass-music-assistant/issues/1180 and don't keep adding to this topic with new or unrelated info, start a new discussion or issue.

Hi all! I have been following the progress here with some interest, and I am trying to install the MA v2 add on using the instructions I found. I have managed to get the MA in my add on store, but I can't install it as it reports my processor or OS is not supported. I am using an RPi 2 model B, so it should have a ARM Cortex-A7 processor. My OS is the latest, 10.1 currently. Am I out of luck that my device is too old, or will it be supported at some time in the future or could something else be wrong?

1 GB ram won't be enough either. It works on my test setup using a pi 3b with 1 GB and that just works, as long I don't add other add-on's or many extra integrations

Ok, good to know, thank you for your replies! Time to invest a little bit again..

FYI: Music Assistant 2023.6.0 beta 0 is now available on HACS which is the rewritten Home Assistant integration that talks to Music Assistant Server 2.0.

I get a "List index out of range", when
i choose an Album (or radio station) and klick the three buttons (Menu)
then choose "Start radio".
Happens since the latest HA update.

@rvandet You are posting in a closed issue from years ago? Firstly having the start radio option against a radio station is a bug. that will be removed. Next the error message is poor. If you look in your logs you will probably find that "the provider library does not support dynamic tracks". So you need to ensure you have a streaming provider that supports dynamic tracks


How to connect wifi open dhcp with portal user login password ?

Martin-ger's master,
Thank you for the repositories you have made.
I've managed to try it, thanks.
But can you help my problem to join the open dhcp wifi network using user login and password?
(Keep using the esp8266 device of course)

Use the esp_wifi_repeater with a client. Log in with the client. From now on any further client doesn't need a new login.

Login and password not on the portal website page, but appear shortly after connecting on the wifi network if using on android. Sorry i do not understand its technical terminology.
Thanks.

Config your esp_wifi_repeater to connect to the wifi network you want.
config your esp_wifi_repeater to be an wifi network ("esp_wifi")
config your client (in your case an android device) to connect to the new wifi network provided by esp_wifi_repeater ("esp_wifi")
now, in your android, it will show the same as if you connect directly without using the esp_wifi_repeater

Sorry it seems to use wpa2 enterprise.
Not the user login on the website page.
thanks.


added accelerometer bias estimation

Enable accelerometer bias estimation.

@jgoppert I enabled accel bias estimation because the estimated velocity and position in my first outdoor flight was not really smooth. Looking at the log, it seems like there is a mismatch between prediction and measurement. I assume that adding a bias for the accelerometer will improve things much.

This is the first flight I did:
http://logs.uaventure.com/view/xiGzDWjuaYmEdcr4aGboqU

@tumbili @mhkabir
Merged this by hand, is in cart_pos_estimator branch now. Caused the stack size to go up by about 1.5 kB due to increased size of Q, P, x. We need to evaluate if it really helps or not. We can due this by setting the bias random walk process noise to zero before flight. PN_B. I currently have it set to 0.01.
Here is a flight log:
https://github.com/jgoppert/lpe-analysis/blob/master/15-10-01 jgoppert accel bias.ipynb

@jgoppert Hi James, I'm currently at IROS and haven't had any time to further work on this.
I'm back on Tuesday and would have time to continue with it. I also had interesting talks with Paul Riseborough about the estimator. I think we should arrange a talk then. What do you think?

Sounds good.


lightspeed/inlineSuggestions: refactoring to simplify the testing

Expose a couple of related global variables in a singleton.

Lint error
./src/features/lightspeed/inlineSuggestions.ts:41:56 - Unknown word (inlinesuggestion)
./src/features/lightspeed/inlineSuggestions.ts:41:73 - Unknown word (useractionhandler)
./src/features/lightspeed/inlineSuggestions.ts:[42](https://github.com/ansible/vscode-ansible/actions/runs/7508613945/job/20444366224?pr=1045#step:10:43):40 - Unknown word (inlinesuggestion)

This PR is part of the following larger refactoring that I'm working on: https://github.com/ansible/vscode-ansible/pull/1049


Test migration client for symmetric key encryption BPS password and Kerberos security policy password

Description:
Refer original task https://github.com/wso2/product-is/issues/9275 for details.
Need to test the following  Admin flows

[ ] BPS profile password - Fix when following fixes are merged to the product (https://github.com/wso2/carbon-kernel/pull/2758 and https://github.com/wso2/carbon-crypto-service/pull/21)

[ ] Kerberos security policy password - when the active STS connector is released

BPS profile password  flow tested and verified.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Improve PHPUnit assertions

Changed log

Using the assertTrue to assert expected is true.
Using the assertFalse to assert expected is false.
Using the assertNull to assert expected is null.

https://github.com/stancl/virtualcolumn/pull/5#event-4048382634


This is a test issue :)

This is the issue's description with text in italic and also in bold :)

This issue was moved to bretth/woven#30

This issue was moved to bretth/woven#31

This issue was moved to nicolasgarnier/drive-music-player#38

This issue was moved to lcycon/hs-dson#1

This issue was moved to lcycon/hs-dson#2

This issue was moved to gabrielmartinsml/gabrielmartinsml.github.io#1


TBI - refactor locate-reuse-lib.js template to use modern API's and fix lint issues

TBI - https://github.com/SAP/open-ux-tools/issues/969
refactor locate-reuse-lib.js template to :

use modern UI5 API's
fix lint issues
fix async loading

Does the file locate-reuse-libs.js need to turn strict mode on inside the functions? https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode

Does the file locate-reuse-libs.js need to turn strict mode on inside the functions? https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Strict_mode

@ullasholla good point. As discussed, I'll create a follow on PR for that next sprint.

Thanks @korotkovao @IainSAP @ullasholla


owocr: init at 1.7.5-unstable-2024-06-26; python312Packages.{azure-ai-vision-imageanalysis,pyperclipfix,ewmhlib,pymonctl,winbox,winct}: init

Description of changes
Fixes:

#335668

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 335869 run on x86_64-linux 1

26 packages built:

owocr
owocr.dist
python311Packages.azure-ai-vision-imageanalysis
python311Packages.azure-ai-vision-imageanalysis.dist
python311Packages.ewmhlib
python311Packages.ewmhlib.dist
python311Packages.pymonctl
python311Packages.pymonctl.dist
python311Packages.pyperclipfix
python311Packages.pyperclipfix.dist
python311Packages.pywinbox
python311Packages.pywinbox.dist
python311Packages.pywinctl
python311Packages.pywinctl.dist
python312Packages.azure-ai-vision-imageanalysis
python312Packages.azure-ai-vision-imageanalysis.dist
python312Packages.ewmhlib
python312Packages.ewmhlib.dist
python312Packages.pymonctl
python312Packages.pymonctl.dist
python312Packages.pyperclipfix
python312Packages.pyperclipfix.dist
python312Packages.pywinbox
python312Packages.pywinbox.dist
python312Packages.pywinctl
python312Packages.pywinctl.dist

Due to #353664 one of the packages doesn't build.

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

x86_64-linux

:white_check_mark: 26 packages built:

owocr
owocr.dist
python311Packages.azure-ai-vision-imageanalysis
python311Packages.azure-ai-vision-imageanalysis.dist
python311Packages.ewmhlib
python311Packages.ewmhlib.dist
python311Packages.pymonctl
python311Packages.pymonctl.dist
python311Packages.pyperclipfix
python311Packages.pyperclipfix.dist
python311Packages.pywinbox
python311Packages.pywinbox.dist
python311Packages.pywinctl
python311Packages.pywinctl.dist
python312Packages.azure-ai-vision-imageanalysis
python312Packages.azure-ai-vision-imageanalysis.dist
python312Packages.ewmhlib
python312Packages.ewmhlib.dist
python312Packages.pymonctl
python312Packages.pymonctl.dist
python312Packages.pyperclipfix
python312Packages.pyperclipfix.dist
python312Packages.pywinbox
python312Packages.pywinbox.dist
python312Packages.pywinctl
python312Packages.pywinctl.dist


⚠ GitLab Server has degraded performance

In f0b7a05, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 7041 ms

Resolved: GitLab Server performance has improved in 163b4cf.


Cannot Create Pool after Raid1 Creation Failure

I ran the script and unfortunately had a network disconnect of my SSH Session during the Raid1 Drive Sync.  Now I cannot create the storage pool or volume from DSM.  The script itself thinks the drives are being used by DSM.  Using the -a switch allows it to continue, however it will fail to create the system partition.  Same error as this issue: #69
[/sbin/sfdisk -N1 -uS -q -f -j256 -z4980480 -tfd -F /dev/nvme0n1] failed. err=255
Create system partitions failed.
ERROR 5 Failed to create syno partitions!
Is there anything I can do to reset everything back to the beginning?  I have already tried erasing them in DSM and re-creating them through the script with the above error.

Closing this out.  Multiple reboots fixed something, no idea what.  But the script is running a new sync now.


Experimentalist Consistency

There is still some variations between the experimentalists, especially with what they return. Most of them (maybe all except the assumption experimentalist, which needs updating) will return a pandas DF when given conditions as a pandas DF. But the behaviour varies when providing conditions as a numpy array. For example, when getting an np.array as input, the novelty sampler outputs a pandas DF, but the falsification sampler outputs a np.array. In the tutorial we explicitly state that experimentalists MUST output a pd.DF, and I think we should adapt the experimentalists to do this no matter the input. You'll notice in the first 2 basic tutorials that there are discrepancies in the code when dealing with different experimentalists because of this and it is confusing.

Let's highlight this problem in the tutorials. i.e., rely on pandas arrays, especially as outputs but in general.


Add matching pattern for SWRL rules

Or are these automatically translated by Jena anyway?
Not urgent, just a matter of completion/interest.

Good idea! Not automatic, but there may be an existing translator that could be incorporated; will need to research.

Not fully implemented but 'object' parts are done now. #4 will include data property reasoning for SWRL.


fix: pb merge

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

Project coverage is 46.06%. Comparing base (c53e07b) to head (f8199b4).
Report is 12 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   45.97%   46.06%   +0.09%
==========================================
  Files           6        6
  Lines        1142     1144       +2
==========================================
+ Hits          525      527       +2
  Misses        547      547
  Partials       70       70

Flag
Coverage Δ

unittests
46.06% <100.00%> (+0.09%)
:arrow_up:

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

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


How to Customize

I'm having trouble learning how to customize the button inputs and would like to know how?

Right now there is no way other than modifying the code and compiling yourself. If I ever get around to it I plan to add a config file to customize the bindings. The default bindings can be changed in XJoy.cpp in the process_buttons method: https://github.com/sam0x17/XJoy/blob/master/XJoy/XJoy.cpp#L237


Check for rate limited Quetre instance

quetre.iket.me is presently giving 503 error as Quora is rate limiting this instance.

I'm able to view posts using that instance, so it seems to be back up.
Farside's polling period is every 5 minutes, and it's occasionally an instance will get rate limited before the next polling period. I could make the polling more frequent, but then that puts instances at a greater risk of getting rate limited by Farside requests.


Adding McGinley Dynamic indicator

Hi, I've added the McGinley Dynamic indicator which I have found useful but isn't yet in this package. It should work but let me know if you need anything.

Hello @whubsch,
Thanks for using Pandas TA. I haven't heard of McGinley Dynamic indicator. I'll add it as soon as I can; running behind on Issues and PRs so apologies in advance. Thank you for your contribution. 😎
Thanks,
KJ

Hello @whubsch,
Thanks for using Pandas TA. I haven't heard of McGinley Dynamic indicator. I'll add it as soon as I can; running behind on Issues and PRs so apologies in advance. Thank you for your contribution. 😎
Thanks,
KJ


Mic-4793/fuzzy-checker-pt2

Mic-4793/fuzzy-checker-pt2
Adds FuzzyChecker to additional tests.

Category: Test
JIRA issue: MIC-4793

-moves helper functions to utilities
-adds FuzzyChecker to integration tests
-adds FuzzyChecker to additional unit tests
Testing
All tests pass

I missed a few unit tests where we could replace np.isclose.


feat(chat-e2e): flaky expand attachment e2e

Description:
fix flaky expand attachment e2e
Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deploy-review

/deply-review


accession_register.py fail

this script fails on ES1, ES2 and macmini.
using a fresh filmographic export that worked ok with the batch accessioning job that this is for.
Terminal out put below
R
Last login: Wed Feb  5 14:45:37 on ttys003
ifi-mac-pro:~ admin$ accession_register.py -h
usage: accession_register.py [-h] [-sorted_csv SORTED_CSV]
[-pbcore_csv PBCORE_CSV] [-filmo_csv FILMO_CSV]
Generates a helper accessions register. Written by Kieran O'Leary.
optional arguments:
-h, --help            show this help message and exit
-sorted_csv SORTED_CSV
Path to sorted helper CSV
-pbcore_csv PBCORE_CSV
Path to technical/PBCore CSV.
-filmo_csv FILMO_CSV  Path to Filmographic CSV. Must contain reference
numbers.
ifi-mac-pro:~ admin$ accession_register.py -sorted_csv /Volumes/imports_ingests/ifa_material/film/register_csvs/register_2020-02-03T14_16_09_sorted.csv -pbcore_csv /Volumes/imports_ingests/ifa_material/film/register_csvs/2020-02-03T19_00_27_pbcore.csv -filmo_csv /Volumes/imports_ingests/ifa_material/film/register_csvs/filmo_csv_rc_20200203.csv
Traceback (most recent call last):
File "/Users/admin/ifigit/ifiscripts/accession_register.py", line 91, in
main(sys.argv[1:])
File "/Users/admin/ifigit/ifiscripts/accession_register.py", line 69, in main
if filmographic_record['Title'] == '':
KeyError: 'Title'
ifi-mac-pro:~ admin$

Cheers raelene, this is a python 3 thing. I have a workaround, but I can't
fix this in the scripts until we completely switch over to genie plus csvs,
rather than using older dB text works ones.
I think gavin is the last user that was using dB text works csvs, and
seeeing as he needed to get a new csv recently, perhaps this is the moment
where we only support genie plus?
It would make the ifb bai workflow a lot easier too as we would avoid a csv
editing step as a result.

btw, this is actually less of a python3 thing and it's more of a genieplus thing - the key fields are called something else in GeniePlus than in DB Textworks - so the error there:
if filmographic_record['Title'] == '':
KeyError: 'Title'

So this is the main issue. The workaround is to manually change these filmographic headings:
Accession_register needs some changes to filmographic:
1. Title/name changes to Title
1. Filmographic URN changes to Reference Number
1. Series Title changes to TitleSeries
1. Episode No changes to EpisodeNo

but the longer term solution, one we drop DB TEXTWORKS CSV support, is for the script to look for the modern GeniePlus terms

cool - yes i think we're ready to completely switch over whenever you are.
Gavin has the knack of cretaing new filmo csvs so won't miss the
dbtextworks ones
i haven't been using the dbtextwork ones either
R
On Wed, 5 Feb 2020 at 17:32, kieranjol<EMAIL_ADDRESS>wrote:

Cheers raelene, this is a python 3 thing. I have a workaround, but I can't
fix this in the scripts until we completely switch over to genie plus csvs,
rather than using older dB text works ones.
I think gavin is the last user that was using dB text works csvs, and
seeeing as he needed to get a new csv recently, perhaps this is the moment
where we only support genie plus?
It would make the ifb bai workflow a lot easier too as we would avoid a csv
editing step as a result.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kieranjol/IFIscripts/issues/370?email_source=notifications&email_token=AE64II5OMAGOQ4CKFL6VWKTRBLZ2NA5CNFSM4KQM73LKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK4JKKQ#issuecomment-582522154,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE64IIYM5NOBLQ4S7X2NMDTRBLZ2NANCNFSM4KQM73LA
.

but in the meantime, - i'll change those things manually when i get that response again.

Thanks Raelene - i'm installing all the bits and bobs necessary to get the scripts and tools up and running on my new laptop. THis is a super slow process that takes many hours but I'll work in a proper fix once I am up and running.

Hi Raelene - this autoclosed with that commit, but instead of manually changing the CSV, can you run update.py, cos I think I've fixed it at a script level. If you're happy, then I'll send around an email to folks and let them know that Genieplus is now only supported. I think i have to change a few other scripts too, probably batchaccession as that needs a small edit too.

This was tested and all seems well!


Use an argument parser to get arguments

Tested and seem to work just fine. If anything, we can fix later.


Logger Eventloop parameter ordering

Re-order Logger and EventLoop parameters in public functions of AWSClient so it is easier to replace Logger with BaggageContext at a later date

This looks good, thank you.
The rule indeed is "context as last non-optional parameter (before any function parameters)" so this looks good in and aligns to that 👍

Ha! @ktoso didn't expect that. I only posted a few minutes back. You got some notification if someone types BaggageContext into a comment or PR?

I watch everything 😉


Consider upgrading cuda to 11.2+

Please consider upgrading cuda to 11.2+, because the current build can't use the CUDA async allocator:
2022-04-07 19:06:22.321736: E tensorflow/compiler/xla/pjrt/gpu_device.cc:323] Failed to initialize CUDA async allocator: FAILED_PRECONDITION: CUDA async allocator requires CUDA >= 11.2; falling back to BFC.

This error happens when trying to use the flag xla::GpuAllocatorConfig::Kind::kCudaAsync.
I would suggest to upgrade at least to cuda 11.3 (same version pytorch offers to download in its website)

Hey @edubart, what CUDA version do you have installed? The XLA binary is prebuilt with CUDA 11.1, but it should be compatible with any 11.1+, so if you have 11.2 or 11.3 installed, you can still us the cuda111 binary. Is that the case and you still get the error?

Ah, looking at the source this is a compile-time check here, so we would need to precompile with CUDA 11.2 to enable this.
How do you use the flag, are you using XLA directly or is there some env var that you set when using EXLA?

Hey @edubart, what CUDA version do you have installed?

I have CUDA 11.6 installed in my system.

How do you use the flag, are you using XLA directly or is there some env var that you set when running with EXLA?

I am using XLA directly just with C++ code, I've opted to use this project prebuilt binaries because it offers the XLA PjRtClient API (while standard prebuilt TensorFlow doesn't). I have also tried to build this project with newer CUDA, but I've failed on that (probably I've missed something in the instructions or maybe the scripts are not compatible with newer cuda).

Ah I see! We use this package primarily for Elixir EXLA, which determines what features and setups we want to support. You should definitely be able to compile for newer version, with either:

Having a local setup with CUDA, Bazel and Python, as noted in the README, then running mix deps.get and XLA_TARGET=cuda XLA_BUILD=true mix compile.

Inside Docker, as described here. I believe you just need to change the image slightly, to use a base image with newer CUDA and change XLA_TARGET=cuda111 to XLA_TARGET=cuda.

We need to precompile with CUDA 11.1 to support more environments, and we currently don't need separate precompilation for newer version. Building for CUDA usually times out on CI, so for the last release I used the Docker setup to build it locally and added it to release. Consequently a separate compilation with CUDA 11.2 is a maintenance burden we want to avoid, until we need it. Therefore, please try building locally, especially in Docker, and if you run into any specific issues let me know :)


[ORA-687] Add met demand to rewards payments

Needs testing, but in the same way that the base branch needs testing => not a draft PR, just a regular PR.

@relyt29  fixed what had to be fixed => mergable


[gmp] build failure

Host Environment

OS: macOS Big Sur 11.4
Package: gmp:x64-osx
Vcpkg version: 2021-05-05-unknownhash

To Reproduce
Steps to reproduce the behavior:
./vcpkg install gmp
Failure logs:
Computing installation plan...
The following packages will be built and installed:
    gmp[core]:x64-osx -> 6.2.1#6
Detecting compiler hash for triplet x64-osx...
Could not locate cached archive: /Users/lihao/.cache/vcpkg/archives/3f/3fdacde64d1c1a453eb02d0d34908efb99404bc735867bd3d81b4214218ff75c.zip
Starting package 1/1: gmp:x64-osx
Building package gmp[core]:x64-osx...
-- Using /Users/lihao/vcpkg/vcpkg/downloads/gmp-6.2.1.tar.xz
-- Cleaning sources at /Users/lihao/vcpkg/vcpkg/buildtrees/gmp/src/gmp-6.2.1-f412680bba.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /Users/lihao/vcpkg/vcpkg/downloads/gmp-6.2.1.tar.xz
-- Applying patch tools.patch
-- Using source at /Users/lihao/vcpkg/vcpkg/buildtrees/gmp/src/gmp-6.2.1-f412680bba.clean
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
CMake Error at scripts/cmake/vcpkg_configure_make.cmake:628 (message):
  gmp requires autoconf from the system package manager (example: "sudo
  apt-get install autoconf")
Call Stack (most recent call first):
  ports/gmp/portfile.cmake:103 (vcpkg_configure_make)
  scripts/ports.cmake:139 (include)

Error: Building package gmp:x64-osx failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `./vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: gmp:x64-osx
  Vcpkg version: 2021-05-05-unknownhash

Additionally, attach any relevant sections from the log files above.

log
autoreconf: export WARNINGS=
  1 autoreconf: Entering directory '.'
  2 autoreconf: configure.ac: not using Gettext
  3 autoreconf: running: aclocal --force
  4 Can't exec "aclocal": No such file or directory at /usr/local/Cellar/autoconf/2.71/share/autoconf/Autom4te/FileUtils.pm line 274.
  5 autoreconf: error: aclocal failed with exit status: 2

@lghosth ，Thanks for posting this issue,
  gmp requires autoconf from the system package manager (example: "sudo
  apt-get install autoconf")

@lghosth ，Thanks for posting this issue,
  gmp requires autoconf from the system package manager

try ''brew install autoconf''

Thanks for your help, but I have installed autoconf.
Warning: autoconf 2.71 is already installed and up-to-date.
To reinstall 2.71, run:
  brew reinstall autoconf`

And then I try to install gmp agian, but it still doesn't work.

The osx machines in CI install a few packages more that just autoconf:
https://github.com/microsoft/vcpkg/blob/master/scripts/azure-pipelines/osx/configuration/vagrant-box-configuration.json
On Ubuntu, aclocal belongs to automake.


feat: pass chain-id in prepareProposal

The cosmos-sdk doesn't have a good way to access the chain-id from the app atm, so we're passing via prepareProposal instead
closes #1027
part of fixing https://github.com/celestiaorg/celestia-app/issues/2020

my protobuf setup adds an extra line \n in a few files relative to the CI, hence the protobuf generation failure.
either we can fix later, or someone with an identical setup to the CI can push to fix, but I don't think we should block on that given we need to ship asap

Can you just manually edit the files to match? Otherwise all subsequent PRs will also have this check broken and actual bugs might slip through!

@SweeXordious has a setup identical to CI, so this has fixed it. In the meantime I'll try and fix my local setup, or update the CI


Clarifiying the purpose

Afaik this package is internal only. If that is the case - it should be labeled as such here and on npmjs to avoid confusion.

@scottlepp @jackw review please?
My goal is to reduce confusion until we have a clear direction.

@tolzhabayev we do use this in open source plugins.

Is this package used in any community plugins?
I mainly want to avoid confusion for the plugin developers in terms of:

How does it differ from @grafana/ui
Can I use this package to build a plugin as a plugin author in our community? <- we will most likely not accept any community plugin that is currently using this package and ask them to use @grafana/ui instead.
Will this package be supported in the same way as other packages we offer to plugin authors?

To me it feels like the discussion on the future of how to handle what / which components should be where and when, etc. is still ongoing.
My intention is to reduce spread of this package to plugins that are created by grafana (even if open source) until we have alignment on the future.


Add openweathermap UV index support

This PR adds UV index support to the openweathermap provider for the One Call api.

Codecov Report

Merging #3145 (609e655) into develop (4b0e0aa) will increase coverage by 0.08%.
The diff coverage is 0.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop    #3145      +/-   ##
===========================================
+ Coverage    25.56%   25.64%   +0.08%
===========================================
  Files           53       53
  Lines        11481    11484       +3
===========================================
+ Hits          2935     2945      +10
+ Misses        8546     8539       -7

Impacted Files
Coverage Δ

...odules/default/weather/providers/openweathermap.js
0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes


Pager whitespace issue

http://getbootstrap.com/components/#pagination-pager
Currenlty in your preview pagination have whitespace this is an issue when pagination is generated without spaces we have no margins. I expect that default functionality can be changed?
Related: https://github.com/esimakin/twbs-pagination/issues/57

I suspect logic similar to #16163 will apply here, except the pager parts are display:inline rather than display:inline-block.
/cc @mdo

Yeah, no plans on our end to change this up—too close to end of life for v3.

@mdo This also applies to v4. Can we agree on "Bootstrap may require spaces in HTML as a result of inline(-block)" as a general design principle?

Just dropped pager links in v4, so closing this out. See #18782.


Adjacent text nodes with hanging punctuation

Hello, "Mr" Fox.

I need to insert a spacer when the adjacent sibling is a text node.

So my approach to solving this is as follows:
If a text node begins with punctuation that needs to be hung
Then check if its parent node's previous sibling is also a text node, and if so add the appropriate spacer to the end of its content.


size can take 2D values also in stops

Size can take 2D values. Also can take 2D values in stops.
Question can they have mixed 1D and 2D values in stops, example:
size: [[13, 64px], [16, [18px, 18px]], [18, 22px]]

Thanks @tallytalwar! 👍

I also had a question on this?
"Question can they have mixed 1D and 2D values in stops, example:
size: [[13, 64px], [16, [18px, 18px]], [18, 22px]]"

Ah, sorry – looks like they can't: https://mapzen.com/tangram/play/?scene=https%3A%2F%2Fgist.githubusercontent.com%2Fanonymous%2Fbadd2af41378e9eea1a90b6ecb59d89d%2Fraw%2F4f66bd8fe1085d90ca2d0ccd33ae76762cccec65%2Fscene.yaml#16.76675/40.76394/-73.98134
I'll update the example.

Hmm... while there's probably not a great need to mix 1d and 2d across stops... I would expect it to work based on current code (I think :)  Let me take a look.

OK I see why it's not working. @tallytalwar does mixing 1d and 2d values work in ES? We can make this work if we want (by converting all input to 2d)... it's just a matter of whether it's worth it :)  But I guess it's least error-prone, and little cost, so maybe makes sense.

I was under the impression that this was intended to be supported, but really I would be happy to disallow mixed 1D and 2D stops. Instances of that are probably a mistake anyway - if the texture is square then you would use one size value for all stops, if not then you would want to use 2 values for all stops to avoid stretching the image.

@bcamper no this will currently not work in ES.
During evaluation of a stop based on the value of the first frame, if its scalar we assume all frames will have scalar, if its a vec2, we assume all frames will have vec2 (https://github.com/tangrams/tangram-es/blob/master/core/src/scene/stops.cpp#L379-L388).
We can also do the same by converting all input frame values to 2d and it should also work for us.

Disallowing is fine with me. We support mixed types for colors (e.g. [[10, red], [12, [0, 0, 1]]), but that has a more natural use case.

That does work for ES, since during parsing of scene/construction of stops, color values get encoded appropriately.
Disallowing is fine with me too. We should clear this in the docs also.


issue 381.6: enforce use of VIEW keyword for bound views and disallow for bound collections

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr-linux/674/


Clarify Cilium policy documentation regarding multiple rules in a spec

A user mentioned on Slack that the docs don't clearly define how multiple rules in a Spec behave:
https://docs.cilium.io/en/stable/policy/intro/#policy-rule
Question explicitly:
As defined in the documentation,  Ingress is a list of type IngressRule. Are all the rules inside Ingress applied as an AND or OR. So if I define something like:
ingress:
    - fromEndpoints:
        - matchLabels:
            "k8s:io.kubernetes.pod.namespace": kube-system
    - fromEntities:
        - health

How is this translated to behaviour?:

requests from entity health are allowed. Also, requests from endpoints from the kube-system namespace are allowed., or
requests from entity health in the namespace kube-system are allowed

The answer is (1).
We could improve the policy docs to clarify these topics, and potentially also update the type Rule definition in the codebase to include this detail in the comment above the fields.

I was looking at what it would take to resolve this issue and found the following paragraph in the documentation at https://docs.cilium.io/en/stable/policy/intro/#policy-rule

All policy rules are based upon a whitelist model, that is, each rule in the policy allows traffic that matches the rule. If two rules exist, and one would match a broader set of traffic, then all traffic matching the broader rule will be allowed. If there is an intersection between two or more rules, then traffic matching the union of those rules will be allowed. Finally, if traffic does not match any of the rules, it will be dropped pursuant to the policy_enforcement_modes.

It seems to me this directly addresses the question asked by the person on Slack - take the union of the 2 rules.
So I would be inclined to close this issue.

OK, thanks for checking @drbruced12 :)


Get the Firefox addon reviewed and signed before Dec. 15

Firefox 41, planned for release on Sept 22, will be incompatible with unsigned extensions. We have an assurance that uProxy will be reviewed before then, but it's going to be tight!

Deadline has been extended to December 15th: https://blog.mozilla.org/addons/2015/09/16/extending-the-deadline-for-add-on-signing/

Because of the extension, this is no longer beta-blocking.

Appears to be fixed by the preliminary review :)


[ignition-msgs1, ignition-transport4] Add new ports

Write new ports using the ignition-modularscript port added in https://github.com/microsoft/vcpkg/pull/7781
Related issue: https://github.com/microsoft/vcpkg/issues/8014 .

The failures on triplets x64-uwp, arm64-windows, arm-uwp are expected, as ignition-msgs1 requires some modifications to support cross compilation, and instead of working directly on a patch I opened an issue upstream to make sure that the modification will be eventually merged upstream (see https://bitbucket.org/ignitionrobotics/ign-msgs/issues/34/add-support-for-cross-compilation).
Instead, the failure in x64-linux is quite strange, and can be investigated further, as there are some strange linking failures w.r.t. to protobuf.

The x64-linux failure is apparently due to the fact that the linking order depends when linking static libraries using ld, and the order used in the build system of ignition-msgs for linking protobuf libraries was wrong, see the PR at https://bitbucket.org/ignitionrobotics/ign-msgs/pull-requests/151/fix-linking-order-of-protocol-buffers/diff for more details.

In the latest commit the failure in x64-linux have been solved, and the only failures are the expected one on cross-compilation targets.

There is another Linux failure because the logic to find UUID in ignition-transport4 requires pkg-config to be installed, and pkg-config is not installed in the test machines.

Fix for uuid problem described  in https://github.com/microsoft/vcpkg/pull/8044#issuecomment-529515227 added in the latest version of the PR.

Robot emoji added to the title (see https://github.com/microsoft/vcpkg/pull/7781#issuecomment-528017994), I think the PR is now ready for review.


Top-bar dropdown scroll stays on slick page

I am using slick on a page based on Foundation (5.5.2) and my top bar dropdown scroll bar stays visible on the slick page when using Chrome (Version 45.0.2454.101), but not on other pages. Works fine on Windows Edge. Haven't tested yet on other browsers.
See example here:
http://www.elisanet.fi/s8/docs_en/photo_2014.html

Closing issue as it disappeared when I re-arranged the menu items. Apparently the issue is something very sensitive to the layout of the scroll bar.


Apply a fix for strange pits and bumps in certain meshes

Apply the fix from https://github.com/sp4cerat/Fast-Quadric-Mesh-Simplification/commit/f958f696c05b4b7a18ca85bc5c89d4f8e60288ad, which fixed https://github.com/sp4cerat/Fast-Quadric-Mesh-Simplification/issues/24.
As part of investigating the possibility of adding python-fast-simplification package to Fedora, I was trying to determine at what point Simplify.h was forked from https://github.com/sp4cerat/Fast-Quadric-Mesh-Simplification/. I decided that the answer was https://github.com/sp4cerat/Fast-Quadric-Mesh-Simplification/commit/4aeffce360279bd070492487426f3e6715c22562, then I looked at the changes since then. I’m not sure if any of the other subsequent commits are valuable here and worth cherry-picking, but I thought I would offer up this one since it looked like it fixed a well-defined issue.

Wheels on PyPi at fast-simplification==0.1.9.


这是为什么

这是出什么错误了，要怎么解决

0 verbose cli /usr/bin/node /usr/bin/npm
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 timing npm:load:whichnode Completed in 4ms
4 timing config:load:defaults Completed in 6ms
5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 2ms
6 timing config:load:builtin Completed in 2ms
7 timing config:load:cli Completed in 5ms
8 timing config:load:env Completed in 1ms
9 timing config:load:file:/root/chinese-colors/.npmrc Completed in 6ms
10 timing config:load:project Completed in 9ms
11 timing config:load:file:/root/.npmrc Completed in 0ms
12 timing config:load:user Completed in 1ms
13 timing config:load:file:/usr/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 1ms
15 timing config:load:setEnvs Completed in 4ms
16 timing config:load Completed in 31ms
17 timing npm:load:configload Completed in 31ms
18 timing npm:load:mkdirpcache Completed in 1ms
19 timing npm:load:mkdirplogs Completed in 2ms
20 verbose title npm run start
21 verbose argv "run" "start"
22 timing npm:load:setTitle Completed in 4ms
23 timing config:load:flatten Completed in 11ms
24 timing npm:load:display Completed in 13ms
25 verbose logfile logs-max:10 dir:/root/.npm/_logs/2023-03-30T05_46_05_739Z-
26 verbose logfile /root/.npm/_logs/2023-03-30T05_46_05_739Z-debug-0.log
27 timing npm:load:logFile Completed in 37ms
28 timing npm:load:timers Completed in 0ms
29 timing npm:load:configScope Completed in 0ms
30 timing npm:load Completed in 97ms
31 silly logfile done cleaning log files
32 timing command:run Completed in 28ms
33 verbose stack Error: Missing script: "start"
33 verbose stack
33 verbose stack Did you mean one of these?
33 verbose stack     npm star # Mark your favorite packages
33 verbose stack     npm stars # View packages marked as favorites
33 verbose stack
33 verbose stack To see a list of scripts, run:
33 verbose stack   npm run
33 verbose stack     at RunScript.run (/usr/lib/node_modules/npm/lib/commands/run-script.js:102:13)
33 verbose stack     at async module.exports (/usr/lib/node_modules/npm/lib/cli.js:134:5)
34 verbose cwd /root/chinese-colors
35 verbose Linux 3.10.0-1127.el7.x86_64
36 verbose node v16.17.1
37 verbose npm  v9.6.2
38 error Missing script: "start"
38 error
38 error Did you mean one of these?
38 error     npm star # Mark your favorite packages
38 error     npm stars # View packages marked as favorites
38 error
38 error To see a list of scripts, run:
38 error   npm run
39 verbose exit 1
40 timing npm Completed in 205ms
41 verbose code 1
42 error A complete log of this run can be found in:
42 error     /root/.npm/_logs/2023-03-30T05_46_05_739Z-debug-0.log
报错Log内容


Add PGCB implementation

At the end of the course of Thursday morning, the teacher has asked to implement PGCB with OOP approach and send back the report on monday morning

For now the feature just return us a PGCB, we'll how to return all PGCB possibilities


[BUG][NOWEB] - send status to 10K contacts and more

[BUG][NOWEB] - send status to 10K contacts and more
Right now there's a timeout or an error at the end

Forgot we already have it https://github.com/devlikeapro/waha/issues/382


Change Dockerfile to create another image with entrypoint to recon.sh

I removed the docker version of collector.


implement relaunch of jobs like in the UI

Coverage decreased (-0.2%) to 90.985% when pulling 563236b2e0beaae0e242618a71bc2c931b646065 on evgeni:job-relaunch into 9e1bc5f902164ef9a2867cb360f9b964c93967bc on ansible:master.

Coverage decreased (-0.3%) to 90.722% when pulling 6fe54c86272ea7c7aefdcf92c0577a0b561013c8 on evgeni:job-relaunch into 499f74ffe092d27844288f6098cdd289c0c72afd on ansible:master.

:)
Last update adds a small test too :)

Coverage decreased (-0.1%) to 90.913% when pulling d58470c751ad297f9fb624cffc492ed55a7de7da on evgeni:job-relaunch into 499f74ffe092d27844288f6098cdd289c0c72afd on ansible:master.


[RFE] Request for Carbide Images in archive format

The customer is requesting Carbide images in a tarball format. Having Carbide images in this format is essential for their project.

At this time, RGS provides archives for customers to download K3S, Rancher and RKE2 without having to use docker pull for the images.
https://rfed-public-images.s3-us-gov-west-1.amazonaws.com/
Customers are requesting the same thing, but with Carbide images. We have three customers with this request now

closing as complete per https://portal.ranchercarbide.dev


OSM Mapnik source Forbidden

My app and the Play Store demo app "osmdroid" can't download OSM Mapnik tiles anymore.
We get this type of message :
W/OsmDroid: Problem downloading MapTile: /4/4/8 HTTP response: Forbidden
It looks like this started yesterday 11/08/2016.
I am using version 5.1

I habe the same problem

me too

duplicate
https://github.com/osmdroid/osmdroid/issues/366


Upgrade to Node 18

Upgrade Node version to 18.17.1, the current LTS version.

@apedroferreira I updated this PR:

put the engines field at >=18 for now (codesandboxci is not at latest node 18)
update netlify
update condesandbox

Got it, thanks!


propagate-environment: true should be the default

I don't think I've made a single pipeline step using the docker plugin that doesn't use propagate-environment: true
Is there a good reason the default is not to propagate this?
I suppose this would have to be the 4.0 release as it would break some pipelines but I think it would be worth the change

I agree!

I agree as well. 🤔 @frankh do you have specific examples for why it would break existing pipelines if we change this default?

It's technically possible to have a pipeline that relies on the lack of an environment variable (e.g. some tools have different behaviour if CI=true is set or not)
Some people may be relying on this behaviour and it would break if it changes, but I imagine it would be quite rare

There may also be security considerations. For example, cloud access credentials or tokens that you probably don't want to share by default. While I understand that your use case does lead to a lot of repetition, changing it will probably have those that don't need it create the very same issue with the opposite suggestion.
I believe the current default leads to the least amount of surprises in the long run and makes it quite obvious when information is being shared into the container.


Some invalid filename characters not being removed

Iwara.tv Enhancement Script
https://apps.timwhitlock.info/unicode/inspect?s=
causes download failure from invalid filename, I do not remember a specific video link off the top of my head but I will update this post with one if I encounter another.

😦 That's wild, I guess I need to use a stricter rule when generating filenames, like a whitelist of valid characters.

Okay, a whitelist might not be feasible since it's basically impossible to list all the valid characters. I may be using an already existing library for this: https://github.com/sindresorhus/filenamify


[Improve]

Description
THe Demos of Go Clinet SDK got some problems. Please check it out.

THe Docker build Example should be fix.
InLong Component
InLong TubeMQ
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@rjm521, thanks!

@rjm521 please add a title for this issue.


De-noise CI output

~[ ] Closes #xxxx~
[x] I am familiar with the contributing guidelines
~[ ] Tests added~
~[ ] Updates entries to docs/sphinx/source/api.rst for API changes.~
~[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).~
~[ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.~
[x] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

It's annoying to scroll through what seems like np.inf lines of warnings in the CI output.  Try finding anything in this mess: https://dev.azure.com/solararbiter/pvlib python/_build/results?buildId=5455&view=logs&j=fc432b8b-e2e3-594e-d8b1-15597b6c1d62&t=309866e1-2cf4-5f00-3d0a-999fc3a0f279
Seems like I'm not the only one annoyed by it, see @wholmgren's https://github.com/pvlib/pvlib-python/pull/1287#issuecomment-902921273

the output of the CI is nearly impossible to parse right now

Probably a lot of it comes from our dependencies, but at least some of it can get fixed here.  Might be worth suppressing some of the noisier warnings from our dependencies if we can't do anything about it.
I assume there's no need to get this into 0.9.0 so I'm not rushing to get this one done.

I guess this is ready for review.  Compare a log from before and after this PR.
Remaining warnings are mostly numpy "invalid value"/"divide by zero encountered in true_divide" warnings, which I'm inclined to not suppress here, but I could be convinced otherwise.


Extend URLResponse tests

This is my first rather small contribution to the swift project.
I tried to start with updating/adding a few tests for URLResponse.
Since I am still on High Sierra I was working on the 4.2 branch.
Please let me know if there is anything wrong or things I can do better next time.

Let's kicking CI.
@swift-ci Please test.

Yes, I did change it to -1 but going to add the 0 test back in, thanks for the reply!

Am 23.03.2019 um 18:08 schrieb Simon Evans<EMAIL_ADDRESS>@spevans commented on this pull request.
In TestFoundation/TestURLResponse.swift:

   let url = URL(string: "test")!

   let res1 = URLResponse(url: url, mimeType: "text/plain", expectedContentLength: zeroContentLength, textEncodingName: nil)

   XCTAssertEqual(res1.expectedContentLength, Int64(zeroContentLength), "should be Int65 of the zero length")

   let res2 = URLResponse(url: url, mimeType: "text/plain", expectedContentLength: positiveContentLength, textEncodingName: nil)

   XCTAssertEqual(res2.expectedContentLength, Int64(positiveContentLength), "should be Int64 of the positive content length")

func test_MIMEType_notAvailable() {

   let mimetype: String? = nil

   let res = URLResponse(url: testURL, mimeType: mimetype, expectedContentLength: 0, textEncodingName: nil)

   XCTAssertEqual(res.mimeType, mimetype, "should be the other mimetype")

}

func test_ExpectedContentLength_positive() {

   let contentLength = 100

   let res1 = URLResponse(url: testURL, mimeType: "text/plain", expectedContentLength: contentLength, textEncodingName: nil)

   XCTAssertEqual(res1.expectedContentLength, Int64(contentLength), "should be positive Int64 content length")

Has the test with zeroContentLength been removed? In general we don't remove tests unless they are invalid and not required anymore, so I would just add back in the zero content length test to this test function.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Could we try the ci-tests again?

@swift-ci test

@swift-ci test

@swift-ci test

Is it possible that sometimes the CI doesn't execute? Seems it's still waiting for the linux swift test even though the test was triggered a day ago.

@swift-ci test


why keep "###" before instruct text?

https://github.com/DAMO-NLP-SG/Video-LLaMA/blob/1728e14f12cbe10287a11395b486ac522ea64083/video_llama/datasets/datasets/video_instruct_dataset.py#L250-L252
I was reading _mask_targets(), I guess this function is using mask to ignore loss from instruct text, but why do you manually keep [curr_idx: curr_idx+2] which is "###" before the actual instruct text?

The assistant will learn to generate "###" if it wants to end the current round. So "###"  can be understood as the EOS flag of each session.

The assistant will learn to generate "###" if it wants to end the current round. So "###" can be understood as the EOS flag of each session.

Thanks for the reply, I understand "###" works like EOS here, and I think the "###" in assistant text is more like EOS? howerver why do we want assistant to learn EOS before instruct?

During inference, we will stop generating tokens once the assistant outputs "###".
Suppose that the training data is " ###Human: Hi. ###Assistant: Hi, can I help you. ###Human: yes".
The content which needs to calculate loss is "Hi, can I help you. ###". So the model can learn to generate "###" as the end flag of his reply.

During inference, we will stop generating tokens once the assistant outputs "###". Suppose that the training data is " ###Human: Hi. ###Assistant: Hi, can I help you. ###Human: yes". The content which needs to calculate loss is "Hi, can I help you. ###". So the model can learn to generate "###" as the end flag of his reply.

I mean you are also keep the  first "###"(the one before "Human: Hi...").

Oh, I see. This place is just for convenience, and you can add a judgment, mask the first "###".

Okay, thanks for the confirmation


Some of the logging/probe functions will embed a carriage return in the middle of a row for CSV output

E.g., this should have been one row, but a carriage return was embedded in the middle of the list:
1999,3,Combined Individual,,"[False False False  True  True False  True  True  True  True  True  True
  True  True  True  True False False  True  True]",14

This is an issue with numpy np.printoptions. When numpy converts an array to a string, explicitly or implicitly for writing to streams, it uses a predetermined line width to insert breaks. You can bypass this by setting an arbitrarily large linewidth parameter while using np.printoptions as a context manager, or np.set_printoptions to change it thereafter.

@lukepmccombs is working on this now.  He's exploring native numpy solutions for emitting CSV rows.

Here is my proposed solution:
In numpy you can override the printing function with another of your choosing via np.set_string_function. We can use this functionality to make a print function that doesn't insert newlines and is usable for loading the arrays later. A good option for this is:
def _to_quoted_list
    f'"{json.dumps(arr.tolist())}"'

which returns a quoted, single line json representation for any size array, and can be restored using json.loads on the contents of the cell.

This should be closable now. :+1:


use underscore utils for ease of use and fewer magic string

Just a small update to use some utility functions from underscore instead of typeof everywhere. Now it should be easy also to use with locallydb for list/array iteration/searching/etc. Nice that locallydb uses underscore too.

Could you please explain the benefit of using underscore?
I read through the entirety of the changes (the string PR as well), but from what I see, all it's doing is acting as syntactic sugar for a few basic operations. This adds extra complexity to the code, and obfuscates what's going on to people unfamiliar with underscore. 'typeof', 'indexOf', and 'charAt' are all very commonly used and well understood core operations, and it feels to me as though wrapping them in functions, creates problems rather than solving them.
I glanced through the underscore documentation, and I see that it does have many useful functions to enhance productivity by simplifying certain common tasks; but the changes proposed are on things that are already as simple as they get. I'm also curious as to why you used 'underscore' instead of '_' as the prefix in your changes, as is used in underscore's documentation.

The use of underscore itself will lead to actually using it for it's
list/array functionality later. It's just a bonus that it contains those
helper methods.
There are a lot of things in the client.js use arrays as data storage. My
goal is (eventually) using locallydb for the temp data storage along with
underscore making the code (in my opinion) clearer and more testable.
If that doesn't align with @Schmoopiie 's goals, then that's fine. He can
deny the PR and we can discuss other options. As for using underscore vs
_, I was trying to follow the convention used already in client.js. I can
update it if Schmoopiie wants. That's no biggie.
Joseph Cellucci
Software Developer
ITA Group
<EMAIL_ADDRESS>On Sun, Jun 28, 2015 at 7:29 PM, OurFlagIsMined<EMAIL_ADDRESS>wrote:

Could you please explain the benefit of using underscore?
I read through the entirety of the changes (the string PR as well), but
from what I see, all it's doing is acting as syntactic sugar for a few
basic operations. This adds extra complexity to the code, and obfuscates
what's going on to people unfamiliar with underscore. 'typeof', 'indexOf',
and 'charAt' are all very commonly used and well understood core
operations, and it feels to me as though wrapping them in functions,
creates problems rather than solving them.
I glanced through the underscore documentation, and I see that it does
have many useful functions to enhance productivity by simplifying certain
common tasks; but the changes proposed are on things that are already as
simple as they get. I'm also curious as to why you used 'underscore'
instead of '_' as the prefix in your changes, as is used in underscore's
documentation.
—
Reply to this email directly or view it on GitHub
https://github.com/Schmoopiie/tmi.js/pull/9#issuecomment-116363000.

@celluj34 Yes it's fine with me, right now the module isn't optimized and underscore will be useful for this. You can use _ I don't mind. You may also create a PR to add your name to the contributors (README.md and package.json files)


A product can be bought if the stocks are nearly empty

When a product has less stock, the button keeps adding to the table means making orders over the number of stocks available making the stocks go below 0.

Fixed: added validation on Main class, in modifyOrder() method.


I can not install version release <IP_ADDRESS>

I have same issue as issue #11.
When I use release version <IP_ADDRESS>, I got the same error as issue #11.
But when I use pre-release version <IP_ADDRESS>, I was able to install it.
Version <IP_ADDRESS> contains fixing bug.
So, I hope you release new version using .msi packaging same as pre-release <IP_ADDRESS>.

Thank you!
I just can't find the time right now, so I will respond as soon as I can.

Thank you.
I look forward to the release of that.


"Something went wrong."

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
General
Steps to reproduce
I signed in from locked screen saver, the fan started running at high speed and this showed up.
2024-08-29.txt
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19045.0
IntPtr Length: 8
x64: True
Date: 8/29/2024 13:12:46
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Shell.WindowChromeWorker._ExtendGlassFrame()
at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force)
at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
✔ Expected Behavior
Nothing
❌ Actual Behavior
It crashed
Other Software
No response

/dup #31226


Fade in and fade out

I took the care of using Audacity to add fade in and fade out effects with to some of my WAVs before importing them in SLAM. When I keep the volume at the default 100% it seems like SLAM "maximizes" the volume dynamically so the fade in/out cannot be heard as I intended. If I set the volume at 60% it sounds pretty much like the original WAV. What is going on here? Is there an optimal volume setting in which the WAV is play as-is?
Thanks

This is definitely something the game is doing, not SLAM. See if you have any boost settings turned on in the games settings.