Cannot connect to the Docker daemon at unix:///home/taz/.docker/desktop/docker.sock

          > Hi PedjaJJ,

Thanks for testing again. Just to check, you have re-downloaded the plugin (version 1.04) and container from here prior to install? We have been adding bugfixes throghout the day.
Judging from your error message, it looks as if the docker container is not starting, likely because of Linux-specific account permission issues. Can you please go through the following steps and let us know the results?
Step 1: Just to make sure that the docker daemon is correctly initialized: please run  sudo systemctl start docker (requires admin privileges).
Step 2: On Linux, normal users are not allowed to run docker commands, this requires administrator rights or being in a specific group. Can you please run docker run --rm --runtime=nvidia nvidia/cuda:11.6.2-base-ubuntu20.04 nvidia-smi and post the output?
Step 3: If you get a "cannot contact docker" error message, retry with sudo docker run --rm --runtime=nvidia nvidia/cuda:11.6.2-base-ubuntu20.04 nvidia-smi. If that one works, your account currently does not have sufficient privileges to run docker commands. Please follow the steps outlined here. Don't forget to log out and in again (or just reboot) at the end.
Step 4: Re-test with docker run --rm --runtime=nvidia nvidia/cuda:11.6.2-base-ubuntu20.04 nvidia-smi. (without sudo). If it works this time, you should now have sufficient user rights - feel free to run the FIJI plugin and let us know what you find.

I am facing a similar issue right now on Ubuntu 22.04. after running docker run --rm --runtime=nvidia nvidia/cuda:11.6.2-base-ubuntu20.04 nvidia-smi, I get the following error:
Cannot connect to the Docker daemon at unix:///home/taz/.docker/desktop/docker.sock. Is the docker daemon running?.
I have added myself to the docker group though and have restarted my PC to test it and face the same issue. Please let me know if you are aware of a solution.
Originally posted by @Tas-V in https://github.com/erturklab/delivr_cfos/issues/1#issuecomment-2070965060

@Tas-V
Which OS do you use?
Can you confirm that your docker daemon is running?

Hi @Tas-V, sounds like the docker daemon is not running or you don't have access rights. It sounds like you're on Linux of some sort, for that we recommend to follow those instructions: https://docs.docker.com/engine/install/linux-postinstall/
Specifically, after the user rights assignment, if you want to start the docker daemon with the system, try running those two commands, then restart your PC:
 sudo systemctl enable docker.service  sudo systemctl enable containerd.service
To verify that the user rights assignment has worked, can you please run docker run hello-world and see what the output is? If that gives you the same error message as before, you can check whether it's a user rights issue by running the same as superuser with sudo docker run hello-world and see whether you get the same output.
Please post the output here. If you have further questions in the meantime, let us know!

Hi @neuronflow
My OS is Ubuntu 22.04 LTS. Here is the output for when I run docker info:
Client: Docker Engine - Community
Version:    26.1.0
Context:    desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version:  v0.14.0
Path:     /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version:  v2.26.1
Path:     /usr/libexec/docker/cli-plugins/docker-compose
Server:
ERROR: Cannot connect to the Docker daemon at unix:///home/taz/.docker/desktop/docker.sock. Is the docker daemon running?
errors pretty printing info
When I sudo run docker info, the server connects. I installed docker using the dropbox link. I first attempted this on an existing docker build but had issues and removed both versions of docker from my computer and reran the dropbox docker install.

Hi @MoritzNegwer
Here is the output of running docker run hello-world after following the instructions for adding myself to the docker group as well as running the two commands and restarting my PC:
docker: Cannot connect to the Docker daemon at unix:///home/taz/.docker/desktop/docker.sock. Is the docker daemon running?.
See 'docker run --help'.
Here is the output of running sudo docker run hello-world
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:

The Docker client contacted the Docker daemon.
The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
Seems like it is still a user issue despite me being in the group. When I do groups $USER, I get docker as a group that I am a part of so I am still confused as to what the issue may be.

Hi @MoritzNegwer
This solved the issue! Here is the output of docker context ls:
NAME              DESCRIPTION                               DOCKER ENDPOINT                                ERROR
default           Current DOCKER_HOST based configuration   unix:///var/run/docker.sock
desktop-linux *   Docker Desktop                            unix:///home/taz/.docker/desktop/docker.sock
I switched to default via docker context use default as you mentioned and now running docker run hello-world has the following output:
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:

The Docker client contacted the Docker daemon.
The Docker daemon pulled the "hello-world" image from the Docker Hub.
(amd64)
The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/get-started/
I am now running into a separate issue when running the DELIVR pipeline via Fiji ImageJ and will open a new issue.

Sweet, thanks for reporting back.


Need more chaos

Nope, in order to prevent PRs like this.

Outstanding attempt, though.  I kinda want to +1 it just for that...

👎 sorry :(

What

Well that didn't take long.

Uh... so is there a bug in the vote counting code or something? The merge commit claims there were only two votes on this PR, when in reality there were several hundred.

Possible explanation for why this got merged: https://github.com/chaosbot/chaos/issues/82#issuecomment-303518208


Refresh aliases support - and web notifications use for information

Dupe of https://github.com/toddhalfpenny/clicks-not-passwords/pull/4


Change name of repository to match example

@tobiasgbg Is this still relevant?

Closing as no longer relevant


is directory.io domain for sale ?

thanks

Not at this time, no. Sorry

you do know, that site is not working
Error 502
Thanks.

In the sense that it's still being useless, it's 100% operational.
But yeah, I know. Taking a break from paying for it.


⚠ Bofrost.at has degraded performance

In 0a235e1, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2352 ms

Resolved: Bofrost.at performance has improved in 8335c87 after 8 minutes.


Calling a SharePoint REST API Endpoint from an Actionable Message

In the action processing phase, you specify that our service should verify the bearer token, but, in this case we are using a SharePoint REST API endpoint. The behavior is:

When making the call, we receive a 401 Unauthorized.
If we include the header like it is specified in this post ("headers": [ { "name": "Authorization", "value": "" } ]) we receive a 403 Forbidden.

Is there a direct way to make a call to the SharePoint REST API from an Actionable Message? We need to call that endpoint using the current user that received the email.
In this case, we are trying social feed endpoints (i.e. /_api/social.feed/post/like).

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

ID: da46b6c4-8c26-e5a8-fafc-f5fa9549740c
Version Independent ID: 2ccd32e5-2e1c-470f-8e9f-7e8aa2f64a00
Content: Security requirements for actionable messages - Outlook Developer
Content Source: docs/actionable-messages/security-requirements.md
Product: outlook
GitHub Login: @jasonjoh
Microsoft Alias: jasonjoh

If your service already has an access token or refresh token for your SharePoint app stored then you could use that (looking them up via the supplied user email address, which can be trusted). But if the user hasn't already authenticated with you/granted permissions etc, then the link won't work and the user would have to go through a login process.


Failed to Resolve : 1.0.5

Hey,
I am getting a Failed to resolve error when trying to sync dependencies.
Min SDK = 17
targetSDK = 28
have any thoughts on this?

I had the same trouble as you have.
Would you like to open "build.gradle" that is in app module and see codes in "repositories".
I guess that you can't find this code.
repositories{
    // something
    maven {
        url "https://jitpack.io"
    }
}

If the guess is right, you may resolve this issue for adding this code in area that you watching now.
    maven {
        url "https://jitpack.io"
    }

I hope this will help.
Thank you!


Spotify Phonie Box does not work

Hey, I hope you can help me. I am totaly new here and i have no idea of prgramming. I just wanted to creat a music box for my daughter =)
So i have this problem: When i install the Phoniebox without Spotify, everything works very well. I changed "PCM" to "Headphone" in "Sudo nano etc/mpd.conf" ( I have no soundcard btw).
But i want to use the Version with Spotify and when i chose [y] in sthe One Line installer, the Phonebox does not work.
I can upload a song from my computer but there is no sound and the track is not playing.
It would be great if you can write exactly what i have to type/change in the console.
I hope you can help me =)
Tahnk you!!!

Could you type journalctl -u mopidy in the console and post the results here?

Hey, i am not sure, how to copy corecct. I am just tasting another script from:
https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/develop/docs/SPOTIFY-INTEGRATION.md
But it does not work.
Are you german?
login as: pi
<EMAIL_ADDRESS>password:
Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Jul  9 13:41:13 2020 from <IP_ADDRESS>
pi@raspberrypi:~ $ journalctl -u mopidy
-- Logs begin at Thu 2020-07-09 13:39:22 CEST, end at Thu 2020-07-09 13:42:03 CE
Jul 09 13:39:27 raspberrypi systemd[1]: Starting Mopidy music server...
Jul 09 13:39:27 raspberrypi systemd[1]: Started Mopidy music server.
Jul 09 13:39:34 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.main S
Jul 09 13:39:34 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loa
Jul 09 13:39:34 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loa
Jul 09 13:39:34 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loa
Jul 09 13:39:34 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loa
Jul 09 13:39:34 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loa
Jul 09 13:39:34 raspberrypi mopidy[510]: ERROR    [MainThread] mopidy.internal.l
Jul 09 13:39:36 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.main E
Jul 09 13:39:36 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.main D
Jul 09 13:39:38 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands S
Jul 09 13:39:38 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands M
Jul 09 13:39:38 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands S
Jul 09 13:39:38 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands S
Jul 09 13:39:38 raspberrypi mopidy[510]: ERROR    [Audio-2] mopidy.audio.actor F
Jul 09 13:39:38 raspberrypi mopidy[510]: ERROR    [Audio-2] pykka Unhandled exce
Jul 09 13:39:38 raspberrypi mopidy[510]: Traceback (most recent call last):
Jul 09 13:39:38 raspberrypi mopidy[510]:   File "/usr/lib/python3/dist-packages/
Jul 09 13:39:38 raspberrypi mopidy[510]:     description, ghost_unlinked_pads=Tr
Jul 09 13:39:38 raspberrypi mopidy[510]: gi.repository.GLib.GError: gst_parse_er
Jul 09 13:39:38 raspberrypi mopidy[510]: During handling of the above exception,
lines 1-23

That log is the right direction, but at the bottom something was cut off which is probably the most relevant.
Could you try to post that also?

I try IT at home. How dobi copy correct? Right click ist paste 😂

I Think this look better?
login as: pi
<EMAIL_ADDRESS>password:
Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Jul  9 15:20:02 2020 from <IP_ADDRESS>
pi@raspberrypi:~ $ journalctl -u mopidy
-- Logs begin at Thu 2020-07-09 13:46:40 CEST, end at Thu 2020-07-09 15:20:54 CEST. --
Jul 09 13:46:45 raspberrypi systemd[1]: Starting Mopidy music server...
Jul 09 13:46:45 raspberrypi systemd[1]: Started Mopidy music server.
Jul 09 13:46:52 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.main Starting Mopidy 3.0.2
Jul 09 13:46:52 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loading config from builtin defaults
Jul 09 13:46:52 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy.conf
Jul 09 13:46:52 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loading config from file:///usr/share/mopidy/conf.d/mopidy-local.conf
Jul 09 13:46:52 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loading config from file:///etc/mopidy/mopidy.conf
Jul 09 13:46:52 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.config Loading config from command line options
Jul 09 13:46:52 raspberrypi mopidy[510]: ERROR    [MainThread] mopidy.internal.log Loading logging config '/etc/mopidy/logging.conf' failed. 'formatters'
Jul 09 13:46:54 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.main Enabled extensions: iris, spotify, local, mpd, m3u, softwaremixer, http, strea
Jul 09 13:46:54 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.main Disabled extensions: none
Jul 09 13:46:56 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Starting Mopidy mixer: SoftwareMixer
Jul 09 13:46:56 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Mixer volume set to 90
Jul 09 13:46:56 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Starting Mopidy audio
Jul 09 13:46:56 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend, SpotifyBacke
Jul 09 13:46:56 raspberrypi mopidy[510]: ERROR    [Audio-2] mopidy.audio.actor Failed to create audio output "Headphone": gst_parse_error: no element "Headph
Jul 09 13:46:56 raspberrypi mopidy[510]: ERROR    [Audio-2] pykka Unhandled exception in Audio (urn:uuid:40bdf253-6264-45b3-bfb1-41f03423c3c1):
Jul 09 13:46:56 raspberrypi mopidy[510]: Traceback (most recent call last):
Jul 09 13:46:56 raspberrypi mopidy[510]:   File "/usr/lib/python3/dist-packages/mopidy/audio/actor.py", line 125, in add_output
Jul 09 13:46:56 raspberrypi mopidy[510]:     description, ghost_unlinked_pads=True
Jul 09 13:46:56 raspberrypi mopidy[510]: gi.repository.GLib.GError: gst_parse_error: no element "Headphone" (1)
Jul 09 13:46:56 raspberrypi mopidy[510]: During handling of the above exception, another exception occurred:
Jul 09 13:46:56 raspberrypi mopidy[510]: Traceback (most recent call last):
Jul 09 13:46:56 raspberrypi mopidy[510]:   File "/usr/lib/python3/dist-packages/pykka/_actor.py", line 186, in _actor_loop
Jul 09 13:46:56 raspberrypi mopidy[510]:     self.on_start()
Jul 09 13:46:56 raspberrypi mopidy[510]:   File "/usr/lib/python3/dist-packages/mopidy/audio/actor.py", line 458, in on_start
Jul 09 13:46:56 raspberrypi mopidy[510]:     self._setup_outputs()
Jul 09 13:46:56 raspberrypi mopidy[510]:   File "/usr/lib/python3/dist-packages/mopidy/audio/actor.py", line 507, in _setup_outputs
Jul 09 13:46:56 raspberrypi mopidy[510]:     self._outputs.add_output(self._config["audio"]["output"])
Jul 09 13:46:56 raspberrypi mopidy[510]:   File "/usr/lib/python3/dist-packages/mopidy/audio/actor.py", line 131, in add_output
Jul 09 13:46:56 raspberrypi mopidy[510]:     raise exceptions.AudioException(bytes(ex))
Jul 09 13:46:56 raspberrypi mopidy[510]: TypeError: cannot convert 'Error' object to bytes
Jul 09 13:46:57 raspberrypi mopidy[510]: INFO     [SpotifyEventLoop] mopidy_spotify.backend Logged in to Spotify in online mode
Jul 09 13:46:58 raspberrypi mopidy[510]: INFO     [SpotifyBackend-6] mopidy_spotify.web Logged into Spotify Web API as<PHONE_NUMBER>1
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [SpotifyBackend-6] mopidy_spotify.playlists Refreshed 15 Spotify playlists
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Starting Mopidy core
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Starting Mopidy frontends: IrisFrontend, HttpFrontend, MpdFrontend
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [IrisFrontend-11] mopidy_iris.core Starting Iris 3.45.0
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [HttpFrontend-13] mopidy.http.actor HTTP server running at [::ffff:<IP_ADDRESS>]:6680
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [MainThread] mopidy_mpd.actor MPD server running at [::ffff:<IP_ADDRESS>]:6600
Jul 09 13:47:00 raspberrypi mopidy[510]: INFO     [MainThread] mopidy.commands Starting GLib mainloop
lines 1-42/42 (END)

Headphone doesn't look right.
What's the output of aplay -l?

In the normal Version i had to change IT to Headphone, than IT worked. I did it here as well. What do you mean with the second Part? Is IT correct that IT is not possible at this time to install phoniebox Spotify via the onelineinstaller?

Please type aplay -l in the console and post the output here.
Spotify should work with the online installer, too.

Ok, I take my time and try to say exactly what i did. First for my first try, then second try and the actual try:
Hardware;

Raspberry Pi 3
64 GB SD Card
Euftech USB Reader
No Sound Card (now i have and USB Sound Card, but i didnt try it yet)
No GPIO Buttons (I wanted to have a functional software first without it)

First try:

Install RasberianBuster Desktop Version on SD Card
Put it in the Rasberry and let him boot
Using the One-Line Installer ( cd; rm buster-install-*; wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/master/scripts/installscripts/buster-install-default.sh; chmod +x buster-install-default.sh; ./buster-install-default.sh
I choose iFace [y] and MDP also [y]
I Chose Spotify [n]
Result
First there was no Sound. I changend with sudo nano /etc/mdp.conf in Audio output to "Headphone" an everythning worked well.

Second try:
1, Steps 1. - 4. as above
2. I chose Spotify [y]
Result
Nothing worked =( I can see the interface on my desktop PC by typing the IP of the Phoniebox, but when i Push play, they didnt start and there was no Sound. I also changed audio output as before to "Headphone" but there was no different.
Actual try:

Install RasberianBuster Desktop Version on SD Card2. Creating SSH file and used putty for installation)
I used this for the installation. (Installing mopidy f.e.)
I choose iFace [y] and MDP [n] (like in the discription, corecct?)
Result:
As the second try, nothing worked. I posted you the stuf u asked me for. Now, in addition, here is the second part u wanted.

aplay -l
login as: pi
<EMAIL_ADDRESS>password:
Linux raspberrypi 4.19.118-v7+ #1311 SMP Mon Apr 27 14:21:24 BST 2020 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Jul  9 15:22:34 2020
pi@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
Subdevices: 4/4
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
pi@raspberrypi:~ $

I think you need to write "Headphones" with thes at the end.

Nothing changed =(
"Headphone" without s worked in my first try btw.
I think there is a bigger problem because its not possible to start any song on the phoniebox

Did you reboot after the change to Headphones?

You mean in sudo nano /etc/mopidy/mopidy.conf?
yes

I dont understand, why the version without spotify works and with spotify not?...

Spotify uses mopidy for audio control, Classic edition uses MPD.
That's two  different tools.

I understand. But you dont see the problem i have?

Yes, it's a configuration issue and step by step we need to find the correct settings.
I don't use Spotify, so sorry, if it's a little searching around.

OK :D What i have to do?

What can I do for this? Any ideas? =)

I tried to sum up changes in our FAQ https://github.com/MiczFlor/RPi-Jukebox-RFID/wiki/Troubleshooting-FAQ#raspberry-pi-update-may-2020-broke-my-audio
Could you try that?

For sure, so lets go:
1) Typingalsa mixer
Result:
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq AlsaMixer v1.1.8 qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x Card: bcm2835 Headphones                                                                                F1:  Help               x x Chip: Broadcom Mixer                                                                                F2:  System information x x View: F3:[Playback] F4: Capture  F5: All                                                                                F6:  Select sound card  x x Item: Headphone [dB gain: -20.00]                                                                                Esc: Exit               x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                           lqqk                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           x  x                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           xaax                                                                            x x                                                                           tqqu                                                                            x x                                                                           xOOx                                                                            x x                                                                           mqqj                                                                            x x                                                                            40                                                                             x x                                                                       <Headphone >                                                                        x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x x                                                                                x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj
2) typing amixers scontrols
Result:
Simple mixer control 'Headphone',0
3) Typing ``
Result:
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]   Subdevices: 4/4   Subdevice #0: subdevice #0   Subdevice #1: subdevice #1   Subdevice #2: subdevice #2   Subdevice #3: subdevice #3 card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]   Subdevices: 4/4   Subdevice #0: subdevice #0   Subdevice #1: subdevice #1   Subdevice #2: subdevice #2   Subdevice #3: subdevice #3

I have to say, that i realy do not understand all of this, but I think you do. I Try my best =)

Ok, so it’s Headphone
Please post the outputs of
cat /etc/mpd.conf
cat /home/pi/RPi-Jukebox-RFID/settings/global.conf
cat /home/pi/RPi-Jukebox-RFID/settings/Audio_iFace_Name
cat /etc/asound.conf
cat /etc/mopidy/mopidy.conf

Oh, and please post
cat /home/pi/RPi-Jukebox-RFID/settings/version-number

All right;

sudo cat /etc/mpd.conf
` # An example configuration file for MPD.

Read the user manual for documentation: http://www.musicpd.org/doc/user/
or /usr/share/doc/mpd/html/user.html
Files and directories

This setting controls the top directory which MPD will search to discover the
available audio files and add them to the daemon's online database. This
setting defaults to the XDG directory, otherwise the music directory will be
be disabled and audio files will only be accepted over ipc socket (using
file:// protocol) or streaming files over an accepted protocol.

music_directory         "/var/lib/mpd/music"

This setting sets the MPD internal playlist directory. The purpose of this
directory is storage for playlists created by MPD. The server will use
playlist files not created by the server but only if they are in the MPD
format. This setting defaults to playlist saving being disabled.

playlist_directory              "/var/lib/mpd/playlists"

This setting sets the location of the MPD database. This file is used to
load the database at server start up and store the database while the
server is not up. This setting defaults to disabled which will allow
MPD to accept files over ipc socket (using file:// protocol) or streaming
files over an accepted protocol.

db_file                 "/var/lib/mpd/tag_cache"

These settings are the locations for the daemon log files for the daemon.
These logs are great for troubleshooting, depending on your log_level
settings.

The special value "syslog" makes MPD use the local syslog daemon. This
setting defaults to logging to syslog, or to journal if mpd was started as
a systemd service.

log_file                        "/var/log/mpd/mpd.log"

This setting sets the location of the file which stores the process ID
for use of mpd --kill and some init scripts. This setting is disabled by
default and the pid file will not be stored.

pid_file                        "/run/mpd/pid"

This setting sets the location of the file which contains information about
most variables to get MPD back into the same general shape it was in before
it was brought down. This setting is disabled by default and the server
state will be reset on server start up.

state_file                      "/var/lib/mpd/state"

The location of the sticker database.  This is a database which
manages dynamic information attached to songs.

sticker_file                   "/var/lib/mpd/sticker.sql"

###############################################################################
General music daemon options

This setting specifies the user that MPD will run as. MPD should never run as
root and you may use this setting to make MPD change its user ID after
initialization. This setting is disabled by default and MPD is run as the
current user.

user                            "mpd"

This setting specifies the group that MPD will run as. If not specified
primary group of user specified with "user" setting will be used (if set).
This is useful if MPD needs to be a member of group such as "audio" to
have permission to use sound card.

#group                          "nogroup"

This setting sets the address for the daemon to listen on. Careful attention
should be paid if this is assigned to anything other then the default, any.
This setting can deny access to control of the daemon. Choose any if you want
to have mpd listen on every address. Not effective if systemd socket
activation is in use.

For network
bind_to_address         "localhost"

And for Unix Socket
#bind_to_address                "/run/mpd/socket"

This setting is the TCP port that is desired for the daemon to get assigned
to.

#port                           "6600"

This setting controls the type of information which is logged. Available
setting arguments are "default", "secure" or "verbose". The "verbose" setting
argument is recommended for troubleshooting, though can quickly stretch
available resources on limited hardware storage.

#log_level                      "default"

Setting "restore_paused" to "yes" puts MPD into pause mode instead
of starting playback after startup.

#restore_paused "no"

This setting enables MPD to create playlists in a format usable by other
music players.

#save_absolute_paths_in_playlists       "no"

This setting defines a list of tag types that will be extracted during the
audio file discovery process. The complete list of possible values can be
found in the user manual.
#metadata_to_use        "artist,album,title,track,name,genre,date,composer,performer,disc"

This example just enables the "comment" tag without disabling all
the other supported tags:
#metadata_to_use "+comment"

This setting enables automatic update of MPD's database when files in
music_directory are changed.

#auto_update    "yes"

Limit the depth of the directories being watched, 0 means only watch
the music directory itself.  There is no limit by default.

#auto_update_depth "3"

###############################################################################
Symbolic link behavior

If this setting is set to "yes", MPD will discover audio files by following
symbolic links outside of the configured music_directory.

#follow_outside_symlinks        "yes"

If this setting is set to "yes", MPD will discover audio files by following
symbolic links inside of the configured music_directory.

#follow_inside_symlinks         "yes"

###############################################################################
Zeroconf / Avahi Service Discovery

If this setting is set to "yes", service information will be published with
Zeroconf / Avahi.

#zeroconf_enabled               "yes"

The argument to this setting will be the Zeroconf / Avahi unique name for
this MPD server on the network. %h will be replaced with the hostname.

#zeroconf_name                  "Music Player @ %h"

###############################################################################
Permissions

If this setting is set, MPD will require password authorization. The password
setting can be specified multiple times for different password profiles.

#password                        "password@read,add,control,admin"

This setting specifies the permissions a user has who has not yet logged in.

#default_permissions             "read,add,control,admin"

###############################################################################
Database

#database {
plugin "proxy"
host "other.mpd.host"
port "6600"
#}
Input

input {
plugin "curl"
proxy "proxy.isp.com:8080"
proxy_user "user"
proxy_password "password"
}
QOBUZ input plugin
input {
enabled    "no"
plugin     "qobuz"
app_id     "ID"
app_secret "SECRET"
username   "USERNAME"
password   "PASSWORD"
format_id  "N"
}
TIDAL input plugin
input {
enabled      "no"
plugin       "tidal"
token        "TOKEN"
username     "USERNAME"
password     "PASSWORD"
audioquality "Q"
}
Decoder

decoder {
plugin                  "hybrid_dsd"
enabled                 "no"
gapless                 "no"
}

###############################################################################
Audio Output

MPD supports various audio output types, as well as playing through multiple
audio outputs at the same time, through multiple audio_output settings
blocks. Setting this block is optional, though the server will only attempt
autodetection for one sound card.

An example of an ALSA output:

audio_output {
type            "alsa"
name            "My ALSA Device"
device          "hw:1,0"        # optional
mixer_type      "hardware"      # optional
mixer_device    "default"       # optional
    mixer_control   "Headphone"             # optional

mixer_index     "0"             # optional
}

An example of an OSS output:

#audio_output {
type            "oss"
name            "My OSS Device"
device          "/dev/dsp"      # optional
mixer_type      "hardware"      # optional
mixer_device    "/dev/mixer"    # optional
mixer_control   "PCM"           # optional
#}

An example of a shout output (for streaming to Icecast):

#audio_output {
type            "shout"
encoder         "vorbis"                # optional
name            "My Shout Stream"
host            "localhost"
port            "8000"
mount           "/mpd.ogg"
password        "hackme"
quality         "5.0"
bitrate         "128"
format          "44100:16:1"
protocol        "icecast2"              # optional
user            "source"                # optional
description     "My Stream Description" # optional
url             "http://example.com"    # optional
genre           "jazz"                  # optional
public          "no"                    # optional
timeout         "2"                     # optional
mixer_type      "software"              # optional
#}

An example of a recorder output:

#audio_output {
type            "recorder"
name            "My recorder"
encoder         "vorbis"                # optional, vorbis or lame
path            "/var/lib/mpd/recorder/mpd.ogg"
quality         "5.0"                   # do not define if bitrate is defined
bitrate         "128"                   # do not define if quality is defined
format          "44100:16:1"
#}

An example of a httpd output (built-in HTTP streaming server):

#audio_output {
type            "httpd"
name            "My HTTP Stream"
encoder         "vorbis"                # optional, vorbis or lame
port            "8000"
bind_to_address "<IP_ADDRESS>"               # optional, IPv4 or IPv6
quality         "5.0"                   # do not define if bitrate is defined
bitrate         "128"                   # do not define if quality is defined
format          "44100:16:1"
max_clients     "0"                     # optional 0=no limit
#}

An example of a pulseaudio output (streaming to a remote pulseaudio server)
Please see README.Debian if you want mpd to play through the pulseaudio
daemon started as part of your graphical desktop session!

#audio_output {
type            "pulse"
name            "My Pulse Output"
server          "remote_server"         # optional
sink            "remote_server_sink"    # optional
#}

An example of a winmm output (Windows multimedia API).

#audio_output {
type            "winmm"
name            "My WinMM output"
device          "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
or
device          "0"             # optional
mixer_type      "hardware"      # optional
#}

An example of an openal output.

#audio_output {
type            "openal"
name            "My OpenAL output"
device          "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
#}

Example "pipe" output:

#audio_output {
type            "pipe"
name            "my pipe"
command         "aplay -f cd 2>/dev/null"
Or if you're want to use AudioCompress
command         "AudioCompress -m | aplay -f cd 2>/dev/null"
Or to send raw PCM stream through PCM:
command         "nc example.org 8765"
format          "44100:16:2"
#}

An example of a null output (for no audio output):

#audio_output {
type            "null"
name            "My Null Output"
mixer_type      "none"                  # optional
#}

###############################################################################
Normalization automatic volume adjustments

This setting specifies the type of ReplayGain to use. This setting can have
the argument "off", "album", "track" or "auto". "auto" is a special mode that
chooses between "track" and "album" depending on the current state of
random playback. If random playback is enabled then "track" mode is used.
See http://www.replaygain.org for more details about ReplayGain.
This setting is off by default.

#replaygain                     "album"

This setting sets the pre-amp used for files that have ReplayGain tags. By
default this setting is disabled.

#replaygain_preamp              "0"

This setting sets the pre-amp used for files that do NOT have ReplayGain tags.
By default this setting is disabled.

#replaygain_missing_preamp      "0"

This setting enables or disables ReplayGain limiting.
MPD calculates actual amplification based on the ReplayGain tags
and replaygain_preamp / replaygain_missing_preamp setting.
If replaygain_limit is enabled MPD will never amplify audio signal
above its original level. If replaygain_limit is disabled such amplification
might occur. By default this setting is enabled.

#replaygain_limit               "yes"

This setting enables on-the-fly normalization volume adjustment. This will
result in the volume of all playing audio to be adjusted so the output has
equal "loudness". This setting is disabled by default.

#volume_normalization           "no"

###############################################################################
Character Encoding

If file or directory names do not display correctly for your locale then you
may need to modify this setting.

filesystem_charset              "UTF-8"

###############################################################################`

cat /home/pi/RPi-Jukebox-RFID/settings/global.conf
Result:
AUDIOFOLDERSPATH="/home/pi/RPi-Jukebox-RFID/shared/audiofolders" PLAYLISTSFOLDERPATH="/home/pi/RPi-Jukebox-RFID/playlists" SECONDSWIPE="RESTART" AUDIOIFACENAME="PCM" AUDIOVOLCHANGESTEP="3" AUDIOVOLMAXLIMIT="100" AUDIOVOLMINLIMIT="1" AUDIOVOLSTARTUP="0" VOLCHANGEIDLE="TRUE" IDLETIMESHUTDOWN="0" SHOWCOVER="ON" READWLANIPYN="OFF" EDITION="plusSpotify" LANG="en-UK" VERSION="2.0 - ed888da - master"

cat /home/pi/RPi-Jukebox-RFID/settings/Audio_iFace_Name
Result:
PCM

cat /etc/asound.conf
Result:
cat: /etc/asound.conf: No such file or directory

cat /etc/mopidy/mopidy.conf
Result:
`[core]
cache_dir = /var/cache/mopidy
config_dir = /etc/mopidy
data_dir = /var/lib/mopidy

[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log
[local]
enabled = true
media_dir = /home/pi/RPi-Jukebox-RFID/shared/audiofolders
excluded_file_extensions =
.conf
.jpg
.txt
placeholder
[file]
#enabled = true
metadata_timeout = 1
[m3u]
playlists_dir = /home/pi/RPi-Jukebox-RFID/playlists
default_encoding = UTF-8
default_extension = .m3u
[audio]
output = Headphones
mixer_volume = 90
[mpd]
hostname = <IP_ADDRESS>
[http]
hostname = <IP_ADDRESS>
[iris]
country = DE
locale = de_DE
[spotify]
enabled = true
username =<EMAIL_ADDRESS>password = gjogjo11
client_id = 1f23b4ae-6e71-4616-baff-dbdab36f9b7c
client_secret = ywFmKYGdrV-h2InNxWRWKqVQAixyK8E9Vv1yr_COaSc=
#bitrate = 160
#volume_normalization = true
#private_session = false
#timeout = 10
#allow_cache = true
#allow_network = true
#allow_playlists = true
#search_album_count = 20
#search_artist_count = 10
#search_track_count = 50
#toplist_countries =`

Its 2.0

use sudo nano /home/pi/RPi-Jukebox-RFID/settings/global.conf
and set AUDIOIFACENAME to Headphone.
Save and exit the editor nano with CTRL + O and CTRL + X.
use sudo nano /home/pi/RPi-Jukebox-RFID/settings/Audio_iFace_Name
and replace PCM with Headphone.
use sudo nano /etc/mopidy/mopidy.conf
and set |outputtoalsasink`.
Reboot.

Ah and to use Spotify you need to add your account data under the [spotify] section, i.e. user, password, client_id, client_secret.

Ok, i changed everythink, but stil no sound =(
This are my steps:

Going into Phoniebox on PI by entering the IP adress (Starting volume is 0% btw, i change it manual to 100%)
click on "Spotify"
3)Click on a playlist
Cop URL Link
Switch back to Phniebox and click on "Card ID"
Scan a new card
Edit the URL Link under "Stream URL" and select "Spotify" as Type
Submit
Go to "Player" (and change Volume again to 100%)
Scaning ID Card
The picture appears but thats all. I can click on Play, but nothing happens.

@Cali227 I've deleted your comment, because the Spotify data was visible in the history. You should change the Spotify password also!
Sorry didn't realize that.

Please post the output of journalctl -u mopidy

Yeah i saw it =) I thought i deleted it myselve, thank you.
So:
journalctl -u mopidy
-- Logs begin at Sun 2020-07-12 10:39:13 CEST, end at Sun 2020-07-12 10:55:00 CEST. --
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_threading.py", line 45, in get
Jul 12 10:39:13 raspberrypi mopidy[5415]:     _compat.reraise(*self._data['exc_info'])
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise value
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_ref.py", line 107, in ask
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise ActorDeadError('{} not found'.format(self))
Jul 12 10:39:13 raspberrypi mopidy[5415]: pykka._exceptions.ActorDeadError: Audio (urn:uuid:72c62911-1ce0-4da9-8a5e-22ea6f761d93) not found
Jul 12 10:39:13 raspberrypi mopidy[5415]: From cffi callback <function _SessionCallbacks.music_delivery at 0x74278930>:
Jul 12 10:39:13 raspberrypi mopidy[5415]: Traceback (most recent call last):
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/session.py", line 1101, in music_delivery
Jul 12 10:39:13 raspberrypi mopidy[5415]:     num_frames,
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/utils.py", line 98, in call
Jul 12 10:39:13 raspberrypi mopidy[5415]:     return listener.callback(*args)
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/mopidy_spotify/playback.py", line 191, in music_delivery_callback
Jul 12 10:39:13 raspberrypi mopidy[5415]:     consumed = audio_actor.emit_data(buffer_).get()
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_threading.py", line 45, in get
Jul 12 10:39:13 raspberrypi mopidy[5415]:     _compat.reraise(*self._data['exc_info'])
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise value
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_ref.py", line 107, in ask
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise ActorDeadError('{} not found'.format(self))
Jul 12 10:39:13 raspberrypi mopidy[5415]: pykka._exceptions.ActorDeadError: Audio (urn:uuid:72c62911-1ce0-4da9-8a5e-22ea6f761d93) not found
Jul 12 10:39:13 raspberrypi mopidy[5415]: From cffi callback <function _SessionCallbacks.music_delivery at 0x74278930>:
Jul 12 10:39:13 raspberrypi mopidy[5415]: Traceback (most recent call last):
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/session.py", line 1101, in music_delivery
Jul 12 10:39:13 raspberrypi mopidy[5415]:     num_frames,
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/utils.py", line 98, in call
Jul 12 10:39:13 raspberrypi mopidy[5415]:     return listener.callback(*args)
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/mopidy_spotify/playback.py", line 191, in music_delivery_callback
Jul 12 10:39:13 raspberrypi mopidy[5415]:     consumed = audio_actor.emit_data(buffer_).get()
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_threading.py", line 45, in get
Jul 12 10:39:13 raspberrypi mopidy[5415]:     _compat.reraise(*self._data['exc_info'])
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise value
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_ref.py", line 107, in ask
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise ActorDeadError('{} not found'.format(self))
Jul 12 10:39:13 raspberrypi mopidy[5415]: pykka._exceptions.ActorDeadError: Audio (urn:uuid:72c62911-1ce0-4da9-8a5e-22ea6f761d93) not found
Jul 12 10:39:13 raspberrypi mopidy[5415]: From cffi callback <function _SessionCallbacks.music_delivery at 0x74278930>:
Jul 12 10:39:13 raspberrypi mopidy[5415]: Traceback (most recent call last):
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/session.py", line 1101, in music_delivery
Jul 12 10:39:13 raspberrypi mopidy[5415]:     num_frames,
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/utils.py", line 98, in call
Jul 12 10:39:13 raspberrypi mopidy[5415]:     return listener.callback(*args)
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/mopidy_spotify/playback.py", line 191, in music_delivery_callback
Jul 12 10:39:13 raspberrypi mopidy[5415]:     consumed = audio_actor.emit_data(buffer_).get()
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_threading.py", line 45, in get
Jul 12 10:39:13 raspberrypi mopidy[5415]:     _compat.reraise(*self._data['exc_info'])
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_compat/__init__.py", line 29, in reraise
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise value
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/pykka/_ref.py", line 107, in ask
Jul 12 10:39:13 raspberrypi mopidy[5415]:     raise ActorDeadError('{} not found'.format(self))
Jul 12 10:39:13 raspberrypi mopidy[5415]: pykka._exceptions.ActorDeadError: Audio (urn:uuid:72c62911-1ce0-4da9-8a5e-22ea6f761d93) not found
Jul 12 10:39:13 raspberrypi mopidy[5415]: From cffi callback <function _SessionCallbacks.music_delivery at 0x74278930>:
Jul 12 10:39:13 raspberrypi mopidy[5415]: Traceback (most recent call last):
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/session.py", line 1101, in music_delivery
Jul 12 10:39:13 raspberrypi mopidy[5415]:     num_frames,
Jul 12 10:39:13 raspberrypi mopidy[5415]:   File "/usr/lib/python3/dist-packages/spotify/utils.py", line 98, in call
Jul 12 10:39:13 raspberrypi mopidy[5415]:     return listener.callback(*args)

Looks like there's a typo or something like that somewhere.
Could you post again the current mopidy.conf file without the Spotify credentials?

Sure.
[core]
cache_dir = /var/cache/mopidy
config_dir = /etc/mopidy
data_dir = /var/lib/mopidy

[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log

[local]
enabled = true
media_dir = /home/pi/RPi-Jukebox-RFID/shared/audiofolders
excluded_file_extensions =
  .conf
  .jpg
  .txt
  placeholder

[file]
#enabled = true
metadata_timeout = 1

[m3u]
playlists_dir = /home/pi/RPi-Jukebox-RFID/playlists
default_encoding = UTF-8
default_extension = .m3u

[audio]
output = alsaink
mixer_volume = 90

[mpd]
hostname = <IP_ADDRESS>

[http]
hostname = <IP_ADDRESS>

[iris]
country = DE
locale = de_DE

[spotify]
enabled = true
username = asd
password = asd
client_id = asd
client_secret = asd
#bitrate = 160
#volume_normalization = true
#private_session = false
#timeout = 10
#allow_cache = true
#allow_network = true
#allow_playlists = true
#search_album_count = 20

Sorry, I edited my previous comment

Ah i see the first typo. alasink
i try it again correct

his pykka._exceptions.ActorDeadError: Audio (urn:uuid:72c62911-1ce0-4da9-8a5e-22ea6f761d93) not found looks like some Spotify address is wrong.

You mean ID or client?

Ah i see the first typo. alasink
i try it again correct

Yeah, please try that first.
After the edit you need to restart mopidy with  sudo systemctl restart mopidy.

Done, nothing changed.

The track is runnig now, but without sound

What do you use as audio output?
In a previous comment you mentioned the volume was 0 after reboot, is this still the case?

The volume is 90% now!
My audio output are this https://www.amazon.de/Trust-Lautsprecher-USB-Stromversorgung-Smartphone-schwarz/dp/B00JRW0M32/ref=as_li_ss_tl?s=computers&ie=UTF8&qid=1542459671&sr=1-1&keywords=trust+leto&linkCode=sl1&tag=welovetech-21&linkId=81f87a80899f024bb73a434adae5673f&language=de_DE

Any ideas? :-)

I dont want to annoy you, but do you stil have more ideas? =))

Is probably an issue in mopidy (see https://github.com/mopidy/mopidy/issues/1924) and according to that ticket it will be fixed in the next mopidy version 3.0.3.
So at the moment you probably have to wait until that is released, unfortunately I'm not aware of any workaround.

Ok, then i will wait for it. Thank you for your help =))

Hi @Cali227
looks like to you have been digging very deep into programming for somebody with no programming background :)
I am always a bit lost what to do with problems like yours. Many people seem to have their Spotify Phoniebox running, but yours does not seem to work. And it's very difficult to narrow down the problem from a distance.
Do you think you can work with the Classic edition for the time being? (save the planet for your daughter, too, by not streaming all the time, which is consuming a lot of electricity...). And/or try a totally fresh install? If it really is the mopidy issue as @s-martin suggests, we will find out once they fixed that at their end.
Until then, I would really like to close this issue, because it is very unique and does not help others.

Hey Miczflor,
Yes you are absolute right, i have no experience in programming 🙃
I realy would like to get the Spotify Version running. There are So many Songs and playlists my daughter Listen on Spotify every Day.
Sure i can make a reinstall, as i did so many Times before, but i think that would not change something.
If there is any oppertunity that you can help me, i would thank you so much!!!

I've got exactly the same issues as described by @Cali227.
Tracks are running, no sound at all. It's a fresh Raspberry Pi OS installation as well as a fresh Phoniebox installation (One line script installation; Master branch; latest version).
Sound is working with YT videos, start-up sound etc.

I've got exactly the same issues as described by @Cali227.
Tracks are running, no sound at all. It's a fresh Raspberry Pi OS installation as well as a fresh Phoniebox installation (One line script installation; Master branch; latest version).
Sound is working with YT videos, start-up sound etc.

Please post the result of journalctl -u mopidy

Had the same issue, but only when I used the URI of private playlists.
If you run on public playlists, albums etc. it works fine. Don't know whats the background of this, but I think this is a spotify-thing, not RPi-Jukebox.


Creating a deployement with kubectl, with correct field.cattle.io/ports annotation does not result in the service being automatically created

Rancher versions:
rancher/server or rancher/rancher: 2.0.2
rancher/agent or rancher/rancher-agent: 2.0.2
Infrastructure Stack versions:
kubernetes: 1.10.1-rancher2-1
Steps to Reproduce:
deploy.yml:
apiVersion: apps/v1beta2
kind: Deployment
metadata:
labels:
workload.user.cattle.io/workloadselector: deployment-default-nginx
name: nginx
namespace: default
spec:
selector:
matchLabels:
workload.user.cattle.io/workloadselector: deployment-default-nginx
replicas: 3
template:
metadata:
annotations:
field.cattle.io/ports: '[[{"containerPort":80,"dnsName":"nginx","kind":"ClusterIP","name":"80tcp02","protocol":"TCP","sourcePort":0}]]'
labels:
workload.user.cattle.io/workloadselector: deployment-default-nginx
spec:
containers:
image: nginx
name: nginx
ports:
- containerPort: 80
name: 80tcp02
protocol: TCP
dnsPolicy: ClusterFirst
imagePullSecrets:
- name: docker-registry
kubectl apply -f deploy.yml
Results:
deployment is created, but the 'nginx' service is not
Expected result:
When creating a deployment from the UI, a matching service is created and is automatically re-created if deleted, we should expect the same behavior when a deployment is created from kubectl with correct annotations.

OK, found that if you have the field.cattle.io/creatorId annotation set, then it has the same behavior as creating a workload with the UI.
I think another annotation should be used as it is quite confusing atm, for ex. it should be something along "field.cattle.io/cattleManaged: true"

*.cattle.io annotations are internal implementation details and not a public interface.
If you want the behavior of our API/UI/CLI, use them.
If you use kubernetes's API/kubectl then you get normal kubernetes behavior, where you define services as separate resources.

I certainly would use the CLI if it was possible to create workloads with it... until then I'm stuck with kubectl and trying to have a consistent behavior between the UI and what I have as a command line.
Regards,


Stop parsing requests with invalid method or path delimiters

Previously requests of the form GET\n/ HTTP/1.1\r\nHost: foo.bar\r\n\r\n would parse.

Thank you! Staring at this PR, I can't recall what I was possibly thinking...


Dialog translation support / String consistency

Future state thought
Refactor the dialogs to source a strings file at the top of each script that will not only provide string consistency, reducing duplication but will also permit sourcing translations based on the $LANG or similar env vars.
something like
_CONFIG=/opt/retronas/dialog/retronas.cfg
_LANG=/opt/retronas/etc/lang/$LANG.string

rn_tcpser() {
source $_CONFIG
source $_LANG
dialog \
  --backtitle "${RN_TITLE}" \
  --title "${RN_TITLE} ${RN_TCPSER} ${RN_MENU}" \
  --clear \
  --menu "${RN_IPADDRESS}: ${MY_IPS} \
  \n
  \n${RN_PLSOPT}" ${MG} 10 \
  "01" "${RN_MAIN_MENU}" \

where
/opt/retronas/etc/lang/$LANG.string would look like
RN_TITLE=RetroNAS
RN_TCPSER=TCPSer
RN_MENU=menu
RN_IPADDRESS="My IP addresses:"
RN_PLSOPT=Please select an option
RN_MAIN_MENU=Main Menu

Closing this to move it to Discussions


Publish to addons

Published, available at https://addons.mozilla.org/en-US/firefox/addon/script-switch/


file not available when writestream ends

File not found by the time the stream ends. (Using the cb param on createWriteStream works though)
var ws = store.createWriteStream({
  key: 'cookso'
})

ws.write('hello world\n')
ws.end(function () {
  var rs = store.createReadStream({
    key: 'cookso'
  })

  rs.pipe(process.stdout)
})

the streams gets buffered and then sent through js-ipfs-api, which causes your callback to fire while the request is being made, causing a racing condition with your read. Makes sense?

This is the same issue we had with idb-blob-store. You can see a solution to this in idb-plus-blob-store.

@diasdavid: You mean go-ipfs is closing the stream before flushing? That HTTP request to go-ipfs shouldn't be closing until it's flushed it to disk.
@dignifiedquire: I think this might be something different? Do you have a write-up on that?


Add a note that EST only supported for DPS CA-based provisioning

@veyalla @gordonwang0 FYI

@PatAltimore
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Additional Media Features

Would love if this had some of the newer media features. Looking at some designs that are going to be coming my way having the pointer/any-pointer available would be quiet helpful
https://developer.mozilla.org/en-US/docs/Web/CSS/Media_Queries/Using_media_queries#media_features

Thanks for the feedback. Sorry I've only just seen this.
With the flurry of new media queries, I'm investigating allowing people to manually add their own to the config. I think that'd be the best way to cover more obscure queries without bloating the central reactive object too much.

Added to the roadmap


Release

PR Author Checklist

[ ] PR title adheres to Conventional Commits
[ ] I have finished reviewing the contents of this PR for accuracy
[ ] If needed, I have included a Changeset and it follows Semantic Versioning principles
[ ] I have completed all of the above and have enabled auto-merge for this PR

Warnings

:warning:
Please assign someone to merge this PR, and optionally include people who should review.

Messages

:book:

packages/cascara/src/components/Dashboard/Dashboard.fixture.js: This fixture has been changed.

  Generated by :no_entry_sign: dangerJS against 273e3b39aa7b69142c9c12cccb9c2a118f0feaa5


Notepad 7.5.7 is still trying to kick CS-Script <IP_ADDRESS> to the curb.

I had to manually remove all files from some old version of the plugin and reinstall it. After that it works again.

It's not only CS-Script. The changes to the hosting model in 7.5.7 affect every plugin with complext file structure. Even PluginManager is facing some issues (I talked to them).
Anyway I have tested it yesterday on the colleagues PC and N++ 7.5.7 x64 with manually installed x64 PluginManager has successfully pulled CS-Script 1.7.13 from the global plugins repo. Though it was a clean install.
If any prev version was installed PluginManager may leave the plugin primary assembly CSScriptNpp.x64.dll in the plugins folder. And this in turn will trigger N++ trying to load it at startup. This is confirmed as a PluginManager issue.
Thus it is just a chain of unfortunate minor problems in N++ and its infrastructure that cripples CS-Script.
Anyway, to fix the problem remove  plugins\CSScriptNpp.x64.dll and plugins\CSScriptNpp folder. After that install CS-Script as usual.

Interesting.  Thanks!

Now also the 32bit version is updated to 1.7.13 with the plugin manager dev list.

No 32bit plugin manager does not use GitHub for hosted repo but a custom one.  And this custom x86 repo at "https://npppm.bruderste.in/plugins" is not updated as quickly as the x64 one. Thus despite cs-script.npp v1.7.13 has been submitted in both the plugin manager x86 still retrieves the old v1.7.11 plugin. I just checked.
If you install that plugin it will run just fine but you will need to ignore the startup misleading N++ error message. I have already explained that.
Now, after starting N++ with the old v1.7.11 plugin you can go to the plugin AboutBox and update it to v1.7.13 from there via plugin own update mechanism. This way you will bypass PluginManager and fetch the plugin binaries directly from CS-Script GitHub page. Yes that....convoluted.
You can now probably understand my frustration with all this mess. I am really puzzles me to see how the authors of such successful product without even blinking slowly suffocating its most valuable feature - plugins. An the do it with the perseverance worthy of a better use.

@oleg-shilo Just the dev list of PM is updated right now(see checkbox under settings). it takes some days until that list is synced to the normal one to allow testing the changes before going alive for the majority of the users.


Allows "value" as an alias for "name"

allows "value" as an alias for "name" (as in old behavior)
moves existing tests away from xls fixtures

@ukanga @yanokwa @pld @mberg
This PR restores value as an accepted alias for the name column of the survey sheet as discussed in odk-developers thread.

:+1:


Update version to match Tag

...you'll need to reTag after merge

Hey @licaon-kter,
Your changes look good to me!


Using Google Japanese Input, keyboard is recognized not JP but US in GUI app.

Windows Version
Microsoft Windows [Version 10.0.22631.2271]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu 22.04.02 LTS
Other Software
WSL other version info.
PS C:> wsl.exe --version
WSL バージョン: <IP_ADDRESS>
カーネル バージョン: <IP_ADDRESS>-1
WSLg バージョン: 1.0.57
MSRDC バージョン: 1.2.4485
Direct3D バージョン: 1.608.2-61064218
DXCore バージョン: 10.0.25880.1000-230602-1350.main
Windows バージョン: 10.0.22631.2271

My Ubuntu keyboard configurations.
$ cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="jp"
XKBVARIANT=""
XKBOPTIONS=""

BACKSPACE="guess"

I tested input method in GNU Emacs 29.1 and lxterminal.
Repro Steps

select Google Japanese Input Method by Win+Space
press ; key, input ; (check keyboad is vlaid)
press Shift+; key

it is : in US layout, + in JP layout

Expected Behavior
input +
Actual Behavior
input :
Diagnostic Logs
With Microsoft IME, it is input + correctly.

@yonta, thanks for reporting the issue, this is most likely that Google Japanese IME has own profile GUID different from Microsoft Japanese IME (GUID_GUID_PROFILE_MSIME_JPN). Would you please share /mnt/wslg/weston.log after you have switched to Google Japanese IME back and forth several times, thanks!

Thanks to reply.
I'm attaching the logs.
In this log, I have switched Input Method, Google Japanese Input -> MS IME -> Google Japanese Input.
weston.log


gsagh-174 add warning message if reference loading

Codecov Report

Merging #267 (4c2fd68) into main (e86c400) will decrease coverage by 0.03%.
The diff coverage is 53.33%.

@@            Coverage Diff             @@
##             main     #267      +/-   ##
==========================================
- Coverage   71.80%   71.77%   -0.04%
==========================================
  Files         147      147
  Lines       20573    20592      +19
==========================================
+ Hits        14772    14779       +7
- Misses       5801     5813      +12

Impacted Files
Coverage Δ

GsaGH/Helpers/Export/Model/MergeModels.cs
0.00% <0.00%> (ø)

GsaGH/Helpers/GH/RhinoConversions.cs
33.39% <0.00%> (ø)

GsaGH/Helpers/Export/Loads/Loads.cs
61.85% <45.45%> (-6.50%)
:arrow_down:

GsaGH/Components/0_Model/CreateModel.cs
70.74% <100.00%> (ø)

GsaGH/Components/2_Geometry/ElemFromMem.cs
62.68% <100.00%> (ø)

GsaGH/Components/2_Geometry/LocalAxes.cs
77.94% <100.00%> (ø)

GsaGH/Components/4_Analysis/Analyse.cs
71.11% <100.00%> (ø)

GsaGH/Helpers/Export/AssembleModel.cs
98.78% <100.00%> (ø)

GsaGH/GsaGHInfo.cs
50.41% <0.00%> (+0.41%)
:arrow_up:


[GetX Migration] Migrate page navigation

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #community-contributions.

We should use named routes and pass data via parameters or arguments when navigating (or create a shared Getx controller for the data if it's too cumbersome for those methods).

We should use named routes and pass data via parameters or arguments when navigating (or create a shared Getx controller for the data if it's too cumbersome for those methods).

Don't we kinda already do this without GetX? What's the benefit of using GetX here?

Named routes are cleaner and you can do stuff like Get.toNamed('/route?chat_title="test"') and grab "test" in the page associated with /route. Just makes it easier to send data back and forth rather than creating a class instance for the page with the data imho. But our current way is fine.
Even if we don't want to transition fully to GetX navigation I would recommend switching to contextless navigation to make it a lot easier.

This is complete with the tablet mode navigation, we use GetX to push pages to the stack


Sync eng/common directory with azure-sdk-tools for PR 4985

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/4985  See eng/common workflow

/check-enforcer override


Unexpected error #4

2022-04-21T21:29:40.154909+00:00 app[worker.1]: [5] Retrying "messages.EditMessage" due to TimeoutError()

Looks like bot have taken too much time for editing its message

Telegram side problem


Update create-flow.md

changed flow.microsoft.com to make.microsoft.com.
Documenting change in URL

@niphadkarneha : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@georgiostrantzas : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
fe25b0ef8b5943665e7a62440630fce321345cff
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
e7c94c7bd2993a0951bc6b10daf776deb65a7b73
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
977aa95bb9f7cd8771b4e65535d04adf8b0d2e6a
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Implementation of OGC TimeseriesML v1.0 Encoding

Implementation of OGC TimeseriesML v1.0 Encoding.
Depends on: 52n-xml-timeseriesML-v10

@SpeckiJ
There are some checkstyle errors. See the travis log


Fix JS GameBoy emulator audio

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior?
Audio was mono, had major crackle on chrome android, could cause clicking if in the background on some devices.
Did not play until a button was pressed. #177

What is the new behavior (if this is a feature change)?
Audio is stereo again, and play's better on all devices (optimized, and buffer increased to 4096).
Sound starts as soon as emulation begins now.
Overall sound volume is the same as 1.1 (Half volume).

Does this PR introduce a breaking change?
Not likely!

Other information:
Pop fix being done in the gameboy core let me remove the code blob from last dc offset pop fix, which was performance intensive and had channels limited to 1.
Wanted this separate from GBT expansion to get this merged quickly as it improves all web outputs.

Hi @RichardULZ Unfortunately this update breaks at least desktop Chrome and Safari support when creating the web build and hosting from a web server as it breaks the Web Audio autoplay policy by creating a web audio context before a user interaction.
https://developers.google.com/web/updates/2017/09/autoplay-policy-changes#webaudio
The issue I think was the replacing of this line with a true value.
window.location.href.indexOf("audio=true") > -1

which causes the audio to be enabled on page load before any user interaction has taken place.
Previously it only did this when audio=true was set in the query string which the In-App Emulator uses (because Electron allows autoplay audio)
https://github.com/chrismaltby/gb-studio/blob/202685ad5efc3a2bedac7b494419b0ff51261a6a/src/index.js#L211
and then in the exported web build this function is called on any touch/keyboard input to initialise the audio if it wasn't already enabled.
https://github.com/chrismaltby/gb-studio/blob/202685ad5efc3a2bedac7b494419b0ff51261a6a/appData/js-emulator/js/other/mobile.js#L72-L96
based on the google link it seems it should be possible to maybe have the context created on page load and call resume() on the first interaction for browsers that don't allow autoplaying audio. If you're saying that the Android browser is allowing it then this might help there, I tried and couldn't get it to work though...
I'm not entirely sure there is a work around to fixing #177 everywhere without maybe having something like a splash screen which I'd like to avoid.
It might be worth splitting out the stereo audio fix in a separate pull request as that seems to be working from what I can tell :-)

Ahh, it may be an itch.io autoplay audio fix that's kept it working for me.
https://richardulz.itch.io/gbstudio-test#1
Will have to test with a plain web server and see if it breaks, but i can definitely change that back for now, the stereo fix is important enough.

FixedPop soundTrue.zip
Here's the file used in that itch.io example.

Hey @RichardULZ thanks very much for this, I've had chance to have a better look and with commit dd728e98ced87096c7cc8e27b42e7acf2375e7b5 I think I've got autoplay audio in a much better place.
I found you can detect if the audio context was able to start by checking for window.audioContext.state === "running" and using that can determine if you're playing from itch.io where, like you say, clicking the start button was enough to allow sound to start.
So as of that commit if you upload to itch.io it should autoplay audio, and if you self host it will continue as it did previously by starting audio on first user input, I also added an initSound() call on mouse click too which should help also.
On a complete aside the music in your example is awesome, not sure if you wrote it yourself but if you did and ever wanted to contribute a few extra tracks to the starter project it would be much appreciated :-D

Perfect @chrismaltby ! Will test that code out sometime.
Was going to suggest the initSound on click as a hold out solution but you've gone ahead and done that already too!
Surprised you got your dummy audio context buffer to check if it was running, I think the resume function had to be called on xaudio's audiocontext, as the dummy one you create on initSound is not for playing gameboy audio.
On the aside, That music is me trying to transcribe StarLove by +tek, only got the first 26 seconds...
https://www.youtube.com/watch?v=KgE-4IpSi7c

Hmm, Bad problem, Firefox audio is broken. Will investigate.

Emergency fix! @chrismaltby
https://richardulz.itch.io/gbstudio-test?password=1
FirefoxFix_1xSpeed.zip
Use the mobile.js file in this zip, i've reworked some things.
Tested on Windows and 2 Android devices with both Firefox & Chrome, in both a Local web & itch.io
Androids were Oneplus3T, and an Old Huawei Y330 (dual core 1.3ghz, 512mb ram).
Firefox will not autoplay but will play on click or button press (was broken).
Chrome will autoplay if engagement was reached (click to start), Buttons will still start the audio if that has not happened.
Removed most of the dummy audio buffer as it didn't seem necessary.
The old android struggled with all cases, but Firefox worked better than chrome, audio was ok when not moving ;P
setting[0] is checked again from suspicion we were running initSound every keypress (the slow old android was lagging worse than normal without that check).

Hi @RichardULZ Thanks for this, I've looked into the issues in Firefox and it looks like the audio context always started with the state being suspended rather than running even if user input had occurred. It looks like calling resume() on the context and waiting for it to start fixes the issue in Firefox and doesn't break Chrome or Safari. Pushed a fix with in 17195e7d19aa056851fc242b85c8e479b74d953d
I've not got any access to any Android devices today but I'm going to try out a few from the QA department at work next week and see if there's anything in these checks that we can improve further.

@chrismaltby Your latest patch in 17195e7 is working fine on both androids, in chrome and firefox, and... audio will autoplay in Firefox now too! Great job!
I'm still not sure why you have these lines, as everything works perfectly without them...
https://github.com/chrismaltby/gb-studio/blob/17195e7d19aa056851fc242b85c8e479b74d953d/appData/js-emulator/js/other/mobile.js#L77-L90
The android devices are working fine with the patch, The old low spec one is still struggling as expected. Firefox is a lot faster than chrome here, and is very playable, moving around you get audio stutters at the start, but it smooths out when walking in large areas.
Seems like tapping buttons causes the slow down, not the emulation, as walking larger distances has less stutter, something to do with the button code. It's fine on mid-high end phones though.
In even better news, on this old phone, I've tested a rom compiled as both a normal Gameboy Game, and as GBC with double speed mode, the performance is identical, so my fears of needing to leave it off for performance are moot.
As usual, i've updated the rom hosted at https://richardulz.itch.io/gbstudio-test?password=1
It's running a stress test with music and gbc 2x speed.
If you walk in the direction of the arrows it will rapidly switch the scene, great test for music performance.

Hi @RichardULZ That's great news and I'll be getting to the 2x request soon :-)
That extra code actually came from here https://gist.github.com/kus/3f01d60569eeadefe3a1 as a fix for audio not working for me on iOS, it's possible it's not needed anymore now though with the recent changes so I'll try removing and see if that breaks anything.


how delta lake update record or delete record

MERGE INTO support?

MERGE INTO support?

We're actively working on basic DML so that we can support MERGE, UPDATE, and DELETE.


Allow linking to arbitrary points in the text

It should be possible to link from one location in the text to another location in the text, to enable jumping to that location in the text. This should be possible across sections of the file as well.

The precision for the target marker has to be at the character level.


When generating features do not write the file if the features have not changed

#1488
Signed-off-by: Paul Gooderham<EMAIL_ADDRESS>

I think we need a check just like it because if generatedFeaturesModified then we must still copy the xml file from src to target. We could remove the extra debug message.


Tool to list the PRs

The tool is used in listing the PRs from where noteworthy PRs is fetched for the weekly developer newsletter. This is the first step towards automating the task, next step would be either manually filtering interesting PRs from this tool or get an intelligent recommendation from the list.
Authors: @ysh4 @arsulegai

Thanks for the contribution. This is interesting. However, with a mere filter based on the age of the PRs, the name of the tool seems a bit overreaching. Do you have plans to continue developing this?

Thanks for the contribution. This is interesting. However, with a mere filter based on the age of the PRs, the name of the tool seems a bit overreaching. Do you have plans to continue developing this?

Yes, this tool will be extended further to capture releases done over a period. There is also evaluation going on to stack rank these results in the order of importance. Any suggestions on the name for the tool?

Closing in favor of https://github.com/hyperledger-tooling


backporting: Update instructions for backporting workflow

Commit 02320e added support for using backporting scripts with Cilium forks. Document the
additional steps that are required with this new workflow.
Additionally, workflow scope might be needed with the GitHub token in
some cases that update the corresponding yamls -
(refusing to allow a Personal Access Token to create or update workflow `.github/workflows/go-check.yaml` without `workflow` scope

Due to a mistake when updating the command for changing labels in a backport PR, this PR has NOT been backported to v1.7. Marking for backports again.


Enhance style of new pages

See what you think @ldodds - I have made the benchmark list page groups into cards - not 100% convinced on the way it looks but easy enough to change. Also see what you think about the search filters. Also I'm not such a fan of the massive header on the front page but it does match the other pages...
Index / search filter page:

[x] Make sure the index page heading matches that of activities
[x] Boostrap-ify search filters
[x] Remove extra spacing above title

Benchmark list page:

[x] Each benchmark group to have a title, followed by the description, then two columns of benchmarks
[x] Add button to change benchmark

Benchmark & Results pages

[x] Style the summary filter so selected items are more prominent - consider using bootstrap badges for selected elements

Any other feedback…

I think this looks good. Some minor styling suggestions:

remove the button-sm from the initial choose options page, I think the button can stand to be bigger there. (but keep small elsewhere)
suggest adding colour to the badges for the school and school type. I tried with badge-primary and thought it looked ok
the badge the school type and country are slightly different. Think it would look better if they were the same

I think the benchmark page looks better.
One thing you could consider trying is adding colours to each section. E.g. $electric-dark for the electricity group, etc. That would visually separate them a bit. The "Total Energy Use"  and the "Date limited comparisons" could remain grey.
I've just updated the navbar to use these colours to try and use consistent colours across the site.
Otherwise looks good.

Thank you for the feedback Leigh, most useful!
Agree colours might be nice for the groups - I was thinking it would be nice to add icons too based on fuel type - but some sections are a mix of fuel types... and I can't find a way of extracting the fuel type, unless I've missed something?
Thanks! Really am going now. Chat Monday.


🚨 Repository Name Change: AgenticJS to KaibanJS 🚨

🚨 Important Announcement: Upcoming Name Change to KaibanJS 🚨
Hello everyone,
We have an important update regarding our project. After careful consideration and advice from our advisors, we’ve decided to rename AgenticJS to KaibanJS. This change will happen in the next few days, and we want to keep you informed.
Why the Change?
We recently discovered another company operating in a similar space with a name that could lead to potential confusion. To avoid any legal issues and better reflect the unique value of our project, we’ve chosen a new name that captures the essence of what we’re building: a Kanban-inspired AI agent system.
What Does KaibanJS Mean?
KaibanJS stands for “AI in a Kanban | AI Agents in a Kanban”. The new name emphasizes our focus on integrating AI agents into a Kanban-style workflow, making it easier for developers to manage and visualize complex AI tasks.
What’s Next?
Here’s what we’ll be doing over the next few days:

Repository Rename: We will rename this repository to KaibanJS.
Documentation Updates: All related documentation, links, and resources will be updated to reflect the new name.
Domain and Branding Changes: Our landing page and domains will be updated to align with the new branding.
Repository Transfer: We will transfer the repository to a new organization named Kaiban.

What You Need to Know:

No immediate action is required from you. GitHub will automatically redirect the old repository URL to the new one, and all stars, forks, issues, and pull requests will remain intact.
If you have any bookmarks or references to this repository, please update them once the change is complete.
If you have any questions or concerns, feel free to comment below or reach out in our Discord.

Thank you for your ongoing support and understanding. We’re excited about this new chapter and look forward to continuing our journey together under the KaibanJS name!
Cheers,
Dariel

Main changes Done: See https://github.com/kaiban-ai/KaibanJS/issues/56


double click myapp.app : only support macOS 10.13 or Higher

pack command
launchui-packager myapp 1.0.1 './dist/main.js' --out./packages
system version
macOS Sierra  10.12.2

@mimecorg
launchui was compiled for 10.13 (fix in https://github.com/mimecorg/launchui/pull/2):
$ for f in *; do echo ./$f; otool -l $f | grep -A2 "LC_VERSION_MIN_MACOSX"; done
./launchui
      cmd LC_VERSION_MIN_MACOSX
  cmdsize 16
  version 10.13
./libnode.57.dylib
      cmd LC_VERSION_MIN_MACOSX
  cmdsize 16
  version 10.7
./libui.A.dylib
      cmd LC_VERSION_MIN_MACOSX
  cmdsize 16
  version 10.8

Version 0.1.4 of launchui should now work on OS X 10.8+. Thank you both for reporting this issue and submitting the PR.