Speed / High pitch sound issue with JABRA Speaker with Raspberry Pi

Description
Hi,
At first, thanks for your project, I really like it and I have started to test your project.
I use a Raspberry Pi 3 and a Jabra Speaker MS510
I got an issue to play 16000Hz sound.
It was very annoying because all my voices and Jarvis voice were very fast with a high pitched
I finally found a fix to make it worked and i hope it will help someone else. Maybe you can add it to your code but i suppose you need to check the impact.
At first i told to my raspberry that i want my USB audio device as default
So i create (as i don't have it) the file alsa-base.conf
$cat /etc/modprobe.d/alsa-base.conf
# This sets the index value of the cards but doesn't reorder.
options snd_usb_audio index=0
options snd_bcm2835 index=1

# Does the reordering.
options snd slots=snd_usb_audio,snd_bcm2835

So by default my audio device will be the Jabra speaker, even after rebooting the device
With the command $aplay -L
I listed all my "audio devices" and i found that there is a line named sysdefault
$ aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
pulse
    PulseAudio Sound Server
sysdefault
default:CARD=USB
    Jabra SPEAK 510 USB, USB Audio
    Default Audio Device
front:CARD=USB,DEV=0
    Jabra SPEAK 510 USB, USB Audio
    Front speakers
surround21:CARD=USB,DEV=0
    Jabra SPEAK 510 USB, USB Audio
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=USB,DEV=0
    Jabra SPEAK 510 USB, USB Audio
    4.0 Surround output to Front and Rear speakers
surround41:CARD=USB,DEV=0
........

So to find my issue i used "aplay" with -D option until i got the correct sound
Example: $aplay -Dsysdefault:CARD=USB -c 2 -f cd audio_test_from_pico2wave.wav
(it also works like this: $aplay -Dsysdefault -c 2 -f cd audio_test_from_pico2wave.wav)
So to fix my issue, i changed the file (generated and cleaned by jarvis.sh) .asoundrc by replacing pcm.!default by pcm.!sysdefault
to get something like this
$cat ./.asoundrc
pcm.!sysdefault {
  type asym
   playback.pcm {
     type plug
     slave.pcm "hw:0,0"
   }
   capture.pcm {
     type plug
     slave.pcm "hw:0,0"
   }
}

As you can see, even I plugged an USB audio device, I put hw:0,0 and not hw:1,0 as i set my USB audio device as default (to load the audio usb driver first) on the file alsa-base.conf

I will leave it open until I test the impact & probably integrate it in the code.
Thanks for raising this and for your testings.

Couldn't find anything obvious about the different between default & sysdefault in Alsa.
However I tested on my raspberry pi and replacing default by sysdefault as you suggested still works (even after a reboot).
I'll commit this and see reaction from the community 😄

I had to fallback this one. My mic was no longer working with this config for some reason (although it was working during my tests).

I have exactly the the same on a fresh new Raspberry Pi 3 installation, except that I have a JABRA SPEAK 410.
J'ai exactement le même problème sur un e installation toute fraîche sur un Raspberry Pi 3, excepté que j'utilise un JABRA SPEAK 410.

Hi @wikijm, is fix also working for you?

So to fix my issue, i changed the file (generated and cleaned by jarvis.sh) .asoundrc by replacing pcm.!default by pcm.!sysdefault

Badly, no. With pcm.!sysdefault, I stop hearing sound, on Jarvis and for every sounds.
Hélas non. Avec pcm.!sysdefault, je n'entends plus aucun son, que ce soit pour Jarvis et tout le reste.

Hi @wikijm
Can you show us the ouput of the command $aplay -L
Thanks

Sorry for the late response.
Here's the result:
pi@RaspAP3:~ $ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
default
sysdefault:CARD=USB
Jabra SPEAK 410 USB, USB Audio
Default Audio Device
front:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
Front speakers
surround21:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
Direct sample mixing device
dsnoop:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
Direct sample snooping device
hw:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
Direct hardware device without any conversions
plughw:CARD=USB,DEV=0
Jabra SPEAK 410 USB, USB Audio
Hardware device with all software conversions
sysdefault:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
dmix:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample mixing device
dmix:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample snooping device
hw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Hardware device with all software conversions

After Jarvis and Raspbian update, everything Workstation fine.

After verification, the problem do not appear when I start Jarvis normally, but this problem still appear with the "Troubleshooting mode"

Had the same issue on my debian jessie home server with a Jabra 410.  It looks like the tts.wav tmp file created by Pico have a 16000hz sample rate. As I didn't found a solution to change alsa default sample rate, I just convert the tmp file with avconv to 44100hz. Quick and dirty, but it's seamless on my server.

Does it work is you pass the format to aplay?
aplay --rate=16000 --channels=1 --format=S16_LE tts.wav

You can also use sox to convert:
sox tts.wav.wav -r 44100 tts.wav

Does it work is you pass the format to aplay?
aplay --rate=16000 --channels=1 --format=S16_LE tts.wav
Nop, this doesn't work
You can also use sox to convert:
sox tts.wav -r 44100 tts.wav

Yep this work.

I had exactly the same issue. I use a Jabra SPEAKER 510
hw:CARD=USB,DEV=0
    Jabra SPEAK 510 USB, USB Audio
    Direct hardware device without any conversions
plughw:CARD=USB,DEV=0
    Jabra SPEAK 510 USB, USB Audio
    Hardware device with all software conversions

And I use the following ~/.asoundrc:
pcm.jabbra {
	type hw
	card 1
	device 0
	rate 48000
}
pcm.!default {
  type asym
   playback.pcm {
     type plug
     slave.pcm "jabbra"
   }
   capture.pcm {
     type plug
     slave.pcm "hw:1,0"
   }
}

The important point is to set the rate to 48KHz for the Jabbra playback. From my different testing results, only 16000 and 48000 values allow aplay to send something. And only 48000 allow aplay to send something correctly!
Hope it will also work for you.

@rikigeek With your solution I'm able to use a virtual "jabra" audio device, but the issue still remain.

To resolve this issue:

Follow @rikigeek solution (create "jabra" audio device, https://github.com/alexylem/jarvis/issues/65#issuecomment-257472419)
Replace all text from ./config/play_hw to "jabra" value

@LengZai Could you try solution below? (https://github.com/alexylem/jarvis/issues/65#issuecomment-267454129)

Bonjour,
Cela fonctionne avec la configuration suivante dans le .asoundrc :
pcm.jabbra {
type hw
card 1
device 0
rate 48000
}
pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm "jabbra"
}
capture.pcm {
type plug
slave.pcm "hw:1,0"
}
}

Since the Jabra (410 in my case) works fine when I use it on my PC, it seems like a configuration issue that should be able to be detected.  If I plug in my Logitech USB headset into the Raspberry Pi, it works fine.  If I plug either of these into my PC they both work fine - so again, it seems like something the driver or configuration should be able to handle.
I need the Jabra to work with my Raspberry Pi, so I am interested to a solution to this problem.

Hi @esilky,
Did you try solution below?
Follow @rikigeek solution (create "jabra" audio device, #65 (comment))
Replace all text from ./config/play_hw to "jabra" value

A solution was provided by @rikigeek and @yaazzz.
Please follow it, and eventualy re-open the ticket if problem still remains.

I tried all and still have the problem

I did follow step 65

@claudioita please paste here the config header of Jarvis (beginning of troubleshooting mode) as well as your ~/.asoudrc file. Thanks.

Please note that it did work in the past.
In the meantime I installed AlecaPi and AssistantPi .. and those might have changed something?
pcm.jabbra {
type hw
card 1
device 0
rate 48000
}
pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm "jabbra"
}
capture.pcm {
type plug
slave.pcm "hw:1,0"
}
}
pi@raspberrypi:~ $ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
default
Playback/recording through the PulseAudio sound server
sysdefault:CARD=USB
Jabra SPEAK 510 USB, USB Audio
Default Audio Device
front:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
Front speakers
surround21:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
Direct sample mixing device
dsnoop:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
Direct sample snooping device
hw:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
Direct hardware device without any conversions
plughw:CARD=USB,DEV=0
Jabra SPEAK 510 USB, USB Audio
Hardware device with all software conversions
sysdefault:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
dmix:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample mixing device
dmix:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample mixing device
dsnoop:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct sample snooping device
dsnoop:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct sample snooping device
hw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Direct hardware device without any conversions
hw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Direct hardware device without any conversions
plughw:CARD=ALSA,DEV=0
bcm2835 ALSA, bcm2835 ALSA
Hardware device with all software conversions
plughw:CARD=ALSA,DEV=1
bcm2835 ALSA, bcm2835 IEC958/HDMI
Hardware device with all software conversions
pi@raspberrypi:~ $

@claudioita did you set your jarvis/config/play_hw to "jabbra" as suggested by @wikijm ?

in /home/pi/jarvis/config
its empty directory (just file .gitkeep empty)

@claudioita it's not normal, Jarvis is not configured.
Please run:
$> jarvis -i

Then once completed, set your play_hw to jabbra:
$> echo "jabbra" > /home/pi/jarvis/config/play_hw

Mmmh it seems to work. Although the audio is not totally clear, but maybe that's how it should sound (difficult to write how it is).
WHile with Jarvis seems ok, I still have the same high pitch, using the Google Assistant SDK ... you know by any chance what and where shall I look?
Must be the same problem

Although the audio is not totally clear, but maybe that's how it should sound (difficult to write how it is)?
Other issue, I still have the same high pitch, using the Google Assistant SDK ... you know by any chance what and where shall I look?
Must be the same problem

this is the log
ON_CONVERSATION_TURN_STARTED
ON_END_OF_UTTERANCE
ON_RECOGNIZING_SPEECH_FINISHED:
{'text': 'what time is it'}
ON_RESPONDING_STARTED:
{'is_error_response': False}
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
WriteDataToAlsa: Under-run occurred; attempting to recover.
ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred
ON_RESPONDING_FINISHED
ON_CONVERSATION_TURN_FINISHED:
{'with_follow_on_turn': False}

We don't provide support here for Google Assistant SDK. Thank you for your understanding.

Hi,
I'm sorry but it is not possible to create the file alsa-base.conf.
I have this message when i want to create :
"modprobe.d/alsa-base.conf"
"modprobe.d/alsa-base.conf" E212: Can't open file for writing
Press ENTER or type command to continue

Hi @jycoma, are you trying with sufficient privileges ?
As it seems to be an issue related to Alsa, you should ask Alsa developers ;)


namespace for cmake export

Adding namespace for cmake export is becoming the standard, here are some reasons:

With namespace targets like Foo::Foo, if it's missing the config will give you an error rather than just silently adding -lFoo

The namespace is a nice way to tell when a library is imported vs part of the project, as most people do follow that standard for imported targets.

However, this is a non backwards compatible change, after this change, the way to link to tinyobjloader in cmake for the downstream will become
target_link_libraries(${PROJECT_NAME} tinyobjloader::tinyobjloader)

awesome! merged!

this is a non backwards compatible change

tinyobjloader is header-only library(just add .h to a project), and I think not so much people is using cmake, thus it may be ok to break the compatibility for cmake stuff.


Use msgspec library for higher speed

Let's try to use msgspec for performance reasons for the IMUDataPacket classes. I'll try to benchmark this and see how much of an improvement we get.
Also will need to test if that builds on the Raspberry Pi since I didn't see wheels for it.
Originally posted by @Aman-Anas in https://github.com/NCSU-High-Powered-Rocketry-Club/AirbrakesV2/pull/4#discussion_r1759957268

Initializing 100,000 RawDataPackets before msgspec,
0.03520050000224728
0.030862718995194882
0.031663336005294695
0.03366126600303687
0.032104951998917386

After msgspec:
0.010517381990212016
0.010180865006987005
0.009927719991537742
0.00970079199760221
0.011575923999771476

After taking the average, msgspec is 68.25% in initializing these classes!
Pros:

Fast
no boilerplate
no need of slots since it uses it internally
no need to define a __str__/__repr__
Cons:
no VSCode autocomplete/type hint :(

Overall: let's do it

type hints usually work for me, that's odd.


events.js:287       throw er; // Unhandled 'error' event

VSCode Version:
OS Version:

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

when use server.js file then error always throw

/needsMoreInfo

when we run the server.js file in server then after sometime it happen is that code is not working ...
it is not use proper way

Please provide detailed steps for how to reproduce the error and provide more details about the error. Where does the error show up, please include a screenshot of the error message and please include the file server.js.

okay thanks


Function node code editor not working after upgrade to 4.x

Current Behavior
After the update to 4.x I can't edit function nodes anymore, because the code editor is not starting.
I see just an empty box and a bunch of errors in the browser console, all seem to be pointing to parseHex function from the Monaco editor (vendor/monaco/dist/editor.js).
No errors on the backend side.
editor-tab-description
TypeError: Cannot read properties of null (reading 'length')
    at t.parseHex (editor.js:2:645497)
    at a.fromHex (editor.js:2:641764)
    at P.getColors (editor.js:2:3519708)
    at P.getColor (editor.js:2:3519929)
    at En.getColor (editor.js:2:1630678)
    at new Zi (editor.js:2:1590677)
    ...

This is thrown after closing the sidebar containing the broken editor, I believe it's trying to destroy the editor instance:
Error: Model is disposed!
    at yt._assertNotDisposed (editor.js:2:2388688)
    at yt.getOptions (editor.js:2:2391844)
    at dt.onConfigurationChanged (editor.js:2:1473698)
    at dt.handleEvents (editor.js:2:1418864)
    at Po._doConsumeQueue (editor.js:2:1668408)
    at Po._consumeViewEventQueue (editor.js:2:1668189)
    ...

I'm not 100% sure if this is the right place to report the issue, but the Home Assistant add-on is so thin, I don't think the bug can be introduced there, while reporting this straight away to Monaco editor seems like going a step too far with allegations.
Expected Behavior
Build-it Monaco code editor working as before.
Steps To Reproduce

Add a function node to the flow
Double click to open
Navigate to "On message" or "On start" tabs.

Example flow
Any flow with function node is affected, that's why I'm dropping an empty one.
[{"id":"a59695e3692d2dd9","type":"tab","label":"Flow 1","disabled":false,"info":"","env":[]},{"id":"2c47026c82b16699","type":"function","z":"a59695e3692d2dd9","name":"function 3","func":"\nreturn msg;","outputs":1,"timeout":0,"noerr":0,"initialize":"","finalize":"","libs":[],"x":480,"y":220,"wires":[[]]}]

Environment

Node-RED version: 4.0.1
Node.js version: 18.20.3
npm version: 10.7.0
Platform/OS: Home Assistant OS 12.4  (amd64 / qemux86-64)
Browser: Brave / Safari / Firefox - all behaves the same

This may seem ridiculous but have you tried clearing the cache and force reloading the browser?

@GogoVega yeah, I've tested it also on multiple browsers, and on multiple devices, web, mobile app, desktop app, restarted the server etc.

@Igloczek
Some years back we seen issues with misbehaving nodes that were causing prototype pollution (see here)
Could you provide a list of installed nodes please.
To get this, press CTRL+SHIFT+P and type system info then hit Enter.  Copy the node_modules  list into a reply

@Steve-Mcl unfortunately opening the system info is broken too, the same error as originally posted, but I'm running a clean install of Home Assistant add-on, nothing installed on top of it, so this list should offer the same set of informations - https://github.com/hassio-addons/addon-node-red/blob/main/node-red/package.json
I've tried to manually disable all the modules using Settings -> Palette -> Nodes -> Disable all on every node, but there was no difference.

I don't use HA so cannot check this for my self but I imagine if this were an issue (as opposed to a one off issue) then all HA users would be seeing the same thing?  Have you seen similar reports on HA forum?

Nope, that's why reported it here.
But since this problem doesn't look like something obvious and easy to fix, I'm just downgrading back to working perfectly fine 3.x, as I don't want to put detective hat and debug this across multiple packages on my own.

I'm having a similar issue, but I can edit the process in my computer browser.
I can only see an empty box on my phone after the update to 4.0.1
Node-RED version: 4.0.1
Node.js  version: v18.20.3
Platform/OS: HAOS 12.4 (amd64 / qemux86-64)）
Supervisor: 2024.06.2
Core: 2024.6.4
Browser: Chrome / Safari /Home Assistant App- all behaves the same


Generic driver throws error at copying SSH key

I'm using docker-machine.exe version 0.8.0, build b85aac1 running on Windows 10 64-bit. When executing docker-machine create --driver generic --generic-ip-address=IP --generic-ssh-key "C:\Users\thasmo\.ssh\id_rsa" my-server I get this error:
Error creating machine: Error in driver during machine creation: unable to copy ssh key: open C:\Users\thasmo\.docker\machine\machines\my-server\C:\Users\thasmo\.ssh\id_rsa: Die Syntax für den Dateinamen, Verzeichnisnamen oder die Datenträgerbezeichnung ist falsch.

To solve it I had to manually copy my id_rsa and id_rsa.pub files to C:\Users\thasmo\.docker\machine\machines\my-server and edit the config.json file within the directory to set the Driver.SSHKeyPath option to the path of the newly copied SSH key.
After that I ran docker-machine regernerated-certs my-server which successfully added my-server as a docker-machine host.

@thasmo What did you filled in SSHKey? I can't get it works.

Same issue here. It's a windows problem, by replacing the \s in your path by /s it works.  Strange, as the line in question seems correct and path.base should respect the OS directory separator.

for confirmation , after replace all slashes its worked
C:\Users\vahric>docker-machine create --driver generic --generic-ip-address=<IP_ADDRESS> --generic-ssh-user=noroot --generic-ssh-key="C:/Users/vahric/.ssh/id_rsa" DT1

I just hit this 2-year-old bug. Forward slashes worked for me too.
Would be nice to fix this in docker-machine itself so that things just work on Windows if anyone can do that.
Thanks for the workaround!


GEODE-5971: Refactor various commands to extend GfshCommand and extend ResultModel

DebugCommand
ExportStackTraceCommand
GfshHelpCommand
GfshHintCommand

Authored-by: Jens Deppe<EMAIL_ADDRESS>Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

@Petahhh Please review


Error Certificate for "AppStore" on Sigh step

Hai, I got this error.
Maybe, because of apple combine AppStore and Ad Hoc for create the certificate. So, You cannot create AppStore certificate only. How can I fix it?.

Hi @adytzs! Can you update using the template here  https://github.com/fastlane/fastlane/blob/master/ISSUE_TEMPLATE.md? Definately want to dig into this :+1:

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I have read the Contribution Guidelines

Issue Description
I'm also facing the similar issue while creating Provisioning Profiles using sigh. Everything was working fine till the last update to sigh this week. After the update, I'm getting the following errors.

+------------------------------------------------------------------------------+
| (4) Create/Download Provisioning Profiles                                    |
+------------------------------------------------------------------------------+
| id: fastlane                                                                 |
| version: 2.1.2                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| time: 2016-03-24T21:35:08-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
$ cd /Users/vagrant/git
 (i) No Gemfile found - using system installed fastlane ...
 (i) Updating system installed fastlane ...
$ gem install fastlane --no-document
Successfully installed fastlane-1.68.0
1 gem installed
Fastlane version:
$ fastlane --version
fastlane 1.68.0
Run fastlane:
$ fastlane createpp
[21:35:19]: ---------------------------
[21:35:19]: --- Step: opt_out_usage ---
[21:35:19]: ---------------------------
[21:35:19]: Disabled upload of used actions
[21:35:19]: -------------------------------------------------
[21:35:19]: --- Step: Verifying required fastlane version ---
[21:35:19]: -------------------------------------------------
[21:35:19]: fastlane version valid
[21:35:19]: ------------------------------
[21:35:19]: --- Step: default_platform ---
[21:35:19]: ------------------------------
[21:35:19]: Driving the lane 'ios createpp' 🚀
[21:35:19]: ------------------
[21:35:19]: --- Step: sigh ---
[21:35:19]: ------------------
+-------------------------------------+--------------------------+
|                     Summary for sigh 1.6.0                     |
+-------------------------------------+--------------------------+
| username                            |<EMAIL_ADDRESS> |
| app_identifier                      | com.test.app378035845 |
| cert_id                             | ASGSCDC554               |
| skip_install                        | true                     |
| force                               | true                     |
| filename                            | pp.mobileprovision       |
| adhoc                               | false                    |
| development                         | false                    |
| ignore_profiles_with_different_name | false                    |
| skip_fetch_profiles                 | false                    |
| skip_certificate_verification       | false                    |
+-------------------------------------+--------------------------+
[21:35:20]: Starting login with user<EMAIL_ADDRESS>[21:35:20]: Successfully logged in
[21:35:20]: Fetching profiles...
[21:35:24]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[21:35:25]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[21:35:25]: No certificates for filter: Certificate ID: 'ASGSCDC554'
[21:35:26]: Variable Dump:
[21:35:26]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios createpp"}
[21:35:26]: Could not find a matching code signing identity for type 'AppStore'. You can use cert to generate one:
https://github.com/fastlane/fastlane/tree/master/cert
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | opt_out_usage                       | 0           |
| 2    | Verifying required fastlane version | 0           |
| 3    | default_platform                    | 0           |
| 4    | sigh                                | 5           |
| 5    | slack                               | 0           |
+------+-------------------------------------+-------------+
[21:35:26]: fastlane finished with errors

Configuration Files
Fastfile:
 desc "Create and Download Provisioning Profiles from Apple Developer Console"
  lane :createpp do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    sigh(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  #adhoc: true,
	  cert_id: "ZZZ_AT_CERT_ID",
	  skip_install: true,
	  force: true,
	  filename: "pp.mobileprovision"
    )
  end

Environment
fastlane version (fastlane -v): 1.68.0

Hi @gauravdaxini Can you let me know what happens if you run cert first? There are no local code signing identities found. You can run security find-identity -v -p codesigning to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)

Hi @TKBurner, I tried to run cert first but, I'm getting the following errors.
Fastlane version:
$ fastlane --version
fastlane 1.68.0
Run fastlane:
$ fastlane createpp
[22:11:36]: ---------------------------
[22:11:36]: --- Step: opt_out_usage ---
[22:11:36]: ---------------------------
[22:11:36]: Disabled upload of used actions
[22:11:36]: -------------------------------------------------
[22:11:36]: --- Step: Verifying required fastlane version ---
[22:11:36]: -------------------------------------------------
[22:11:36]: fastlane version valid
[22:11:36]: ------------------------------
[22:11:36]: --- Step: default_platform ---
[22:11:36]: ------------------------------
[22:11:36]: Driving the lane 'ios createpp' 🚀
[22:11:36]: ------------------
[22:11:36]: --- Step: cert ---
[22:11:36]: ------------------
+---------------+-------------------------------------------------+
|                     Summary for cert 1.4.0                      |
+---------------+-------------------------------------------------+
| development   | false                                           |
| force         | false                                           |
| username      |<EMAIL_ADDRESS>                        |
| keychain_path | /Users/vagrant/Library/Keychains/login.keychain |
+---------------+-------------------------------------------------+
[22:11:36]: Starting login with user<EMAIL_ADDRESS>[22:11:37]: Successfully logged in
[22:11:38]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[22:11:38]: Certificate 3WX53U5ST3 (User Name) can't be found on your local computer
[22:11:38]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[22:11:38]: Certificate WH6D44G2WQ (User Name) can't be found on your local computer
[22:11:38]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[22:11:38]: Certificate ASGYBNC554 (User Name) can't be found on your local computer
[22:11:38]: Couldn't find an existing certificate... creating a new one
[22:11:40]: Variable Dump:
[22:11:40]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios createpp"}
[22:11:40]: Could not create another certificate, reached the maximum number of available certificates.

@gauravdaxini  You are only allowed three distribution certs. The problem probably is that CircleCI will create a fresh machine for every run, so you run out of slots. You'll have to store the certificate + private key somewhere and import it, instead of running cert. If you have your own machine, you can use cert :+1:

We have already added the distribution certificate + private key on our server and importing it for code signing in the next step. But we are getting the above-mentioned error while creating the provisioning profile certificate for an app.
Please help!

Hi @gauravdaxini! Thanks for following up. This has to do with your Apple Developer Account. You can only have 3 active certs at a time. Let me know if you have any other questions :+1:

Hi @TKBurner! We have been facing this issue since last month and are not been able to build the app automatically. We are using Bitrise to auto build the apps. We were able to build the apps before this issue, however suddenly, the app build stopped working at the provisioning profile creation step(Sigh). We have created a Workflow which uses the fastlane tools. Following are the errors that we received.

+------------------------------------------------------------------------------+
| (4) Create/Download Provisioning Profiles                                    |
+------------------------------------------------------------------------------+
| id: fastlane                                                                 |
| version: 2.1.2                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| time: 2016-03-24T21:35:08-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
$ cd /Users/vagrant/git
 (i) No Gemfile found - using system installed fastlane ...
 (i) Updating system installed fastlane ...
$ gem install fastlane --no-document
Successfully installed fastlane-1.68.0
1 gem installed
Fastlane version:
$ fastlane --version
fastlane 1.68.0
Run fastlane:
$ fastlane createpp
[21:35:19]: ---------------------------
[21:35:19]: --- Step: opt_out_usage ---
[21:35:19]: ---------------------------
[21:35:19]: Disabled upload of used actions
[21:35:19]: -------------------------------------------------
[21:35:19]: --- Step: Verifying required fastlane version ---
[21:35:19]: -------------------------------------------------
[21:35:19]: fastlane version valid
[21:35:19]: ------------------------------
[21:35:19]: --- Step: default_platform ---
[21:35:19]: ------------------------------
[21:35:19]: Driving the lane 'ios createpp' 🚀
[21:35:19]: ------------------
[21:35:19]: --- Step: sigh ---
[21:35:19]: ------------------
+-------------------------------------+--------------------------+
|                     Summary for sigh 1.6.0                     |
+-------------------------------------+--------------------------+
| username                            |<EMAIL_ADDRESS> |
| app_identifier                      | com.test.app378035845 |
| cert_id                             | ASGSCDC554               |
| skip_install                        | true                     |
| force                               | true                     |
| filename                            | pp.mobileprovision       |
| adhoc                               | false                    |
| development                         | false                    |
| ignore_profiles_with_different_name | false                    |
| skip_fetch_profiles                 | false                    |
| skip_certificate_verification       | false                    |
+-------------------------------------+--------------------------+
[21:35:20]: Starting login with user<EMAIL_ADDRESS>[21:35:20]: Successfully logged in
[21:35:20]: Fetching profiles...
[21:35:24]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[21:35:25]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[21:35:25]: No certificates for filter: Certificate ID: 'ASGSCDC554'
[21:35:26]: Variable Dump:
[21:35:26]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios createpp"}
[21:35:26]: Could not find a matching code signing identity for type 'AppStore'. You can use cert to generate one:
https://github.com/fastlane/fastlane/tree/master/cert
+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | opt_out_usage                       | 0           |
| 2    | Verifying required fastlane version | 0           |
| 3    | default_platform                    | 0           |
| 4    | sigh                                | 5           |
| 5    | slack                               | 0           |
+------+-------------------------------------+-------------+
[21:35:26]: fastlane finished with errors

After getting this error, we tried to use the cert tool along with the Sigh and got the following error.
Fastlane version:
$ fastlane --version
fastlane 1.68.0
Run fastlane:
$ fastlane createpp
[22:11:36]: ---------------------------
[22:11:36]: --- Step: opt_out_usage ---
[22:11:36]: ---------------------------
[22:11:36]: Disabled upload of used actions
[22:11:36]: -------------------------------------------------
[22:11:36]: --- Step: Verifying required fastlane version ---
[22:11:36]: -------------------------------------------------
[22:11:36]: fastlane version valid
[22:11:36]: ------------------------------
[22:11:36]: --- Step: default_platform ---
[22:11:36]: ------------------------------
[22:11:36]: Driving the lane 'ios createpp' 🚀
[22:11:36]: ------------------
[22:11:36]: --- Step: cert ---
[22:11:36]: ------------------
+---------------+-------------------------------------------------+
|                     Summary for cert 1.4.0                      |
+---------------+-------------------------------------------------+
| development   | false                                           |
| force         | false                                           |
| username      |<EMAIL_ADDRESS>                        |
| keychain_path | /Users/vagrant/Library/Keychains/login.keychain |
+---------------+-------------------------------------------------+
[22:11:36]: Starting login with user<EMAIL_ADDRESS>[22:11:37]: Successfully logged in
[22:11:38]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[22:11:38]: Certificate 3WX53U5ST3 (User Name) can't be found on your local computer
[22:11:38]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[22:11:38]: Certificate WH6D44G2WQ (User Name) can't be found on your local computer
[22:11:38]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[22:11:38]: Certificate ASGYBNC554 (User Name) can't be found on your local computer
[22:11:38]: Couldn't find an existing certificate... creating a new one
[22:11:40]: Variable Dump:
[22:11:40]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios createpp"}
[22:11:40]: Could not create another certificate, reached the maximum number of available certificates.

We also checked for WWDR certificate expiration and confirm the same from Bitrise team. It is updated on the build server.
Also, as suggested by you to keep certificate+key on the server and importing it. We are already doing the same but it is after the Sigh step in the Workflow.
Is there any changes needs to be done from our side since the Sigh is updated? Fastlane is already installing the updated version of the Sigh on the Build server.
We contacted the Bitrise team for the same but they suggested to contact you.
Request you to please help us. We are not been able to auto build the apps.
Thank you!

Hi @gauravdaxini! Thanks for following up. Can you let me know if you've reviewed the information here:
There are no local code signing identities found. You can run security find-identity -v -p codesigning to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
Can you send me the output when you run 'cert' in the command line rather than in a lane?
Thanks!

Hi @TKBurner, we checked for expired WWDR certificate on the build server with the Bitrise team but it is updated.
Also, we tried to run 'cert' in the command line through a workflow script, but not been able to set the developer password in the workflow script.
cert -u<EMAIL_ADDRESS>Please suggest something on this.

@gauravdaxini Thanks for following up. Are you still getting the too many certificates error? This seems like it is related to your Apple developer account. Let me know 👍

Hi @TKBurner! Unfortunately, we are unable to find an issue in our Apple Developer account. The manual app builds are working properly and we are able to generate the provisioning profile certificate manually through our developer account. Is there anything else we are missing?

Hi @gauravdaxini Thanks for reaching out. You developer account password is stored in your keychain. If you remove that entry are you able to run the cert command alone? Thanks!

Hi @TKBurner! We tried to run the cert command on the remote build server(in the workflow). However, we are not able to set the developer password in the command. Is there a parameter for password that we can add to the following command?
cert -u<EMAIL_ADDRESS>

Hi @gauravdaxini Thanks for following up. The password is stored in the system keychain or login keychain. If you aren't being prompted for it, it is already stored on the machine, can you delete that entry?

Hi @TKBurner! We do not have the access to keychain as we are using the Bitrise CLI. It would be great if you could provide us some alternative/fix to create the provisioning profile certificate as we not been able to generate the same using the Sigh.

Hi @gauravdaxini! Thanks for following up. Do you have the password for the system keychain or login keychain? That's where we store the password. Can you run cert --verbose and share the full output?
Thanks!

Hi @TKBurner! Getting the following error when I execute the cert --verbose in a Bitrise workflow.
+------------------------------------------------------------------------------+
| (4) Cert Test                                                                |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.0                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| time: 2016-05-04T04:04:07-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
+---------------+-------------------------------------------------+
|                     Summary for cert 1.4.0                      |
+---------------+-------------------------------------------------+
| development   | false                                           |
| force         | false                                           |
| username      |<EMAIL_ADDRESS>                        |
| keychain_path | /Users/vagrant/Library/Keychains/login.keychain |
+---------------+-------------------------------------------------+
INFO [2016-05-04 04:04:18.12]: Starting login with user<EMAIL_ADDRESS>-------------------------------------------------------------------------------------
The login information you enter will be stored in your Mac OS Keychain
You can also pass the password using the `FASTLANE_PASSWORD` env variable
More information about it on GitHub: https://github.com/fastlane/fastlane/tree/master/credentials_manager
-------------------------------------------------------------------------------------
Password (for test@gmail.com): stty: stdin isn't a terminal
stty: stdin isn't a terminal
stty: stdin isn't a terminal

Hi @gauravdaxini! Thanks for following up. Can you try setting a ENV variable in Fastlane for the FASTLANE_PASSWORD? For more info see this page: https://github.com/fastlane/fastlane/blob/9c0494ef5e7d71afc51c73fe0b141b02e8991d9c/fastlane/docs/FAQs.md
Thanks!

Hi @TKBurner! I have already used the FASTLANE_PASSWORD inside the fastfile and already running the lanes on the Bitrise build server. When I try to run the lane that uses sigh, I get the following error.
+------------------------------------------------------------------------------+
| (4) Create/Download Provisioning Profiles                                    |
+------------------------------------------------------------------------------+
| id: fastlane                                                                 |
| version: 2.1.3                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| time: 2016-05-10T04:58:50-07:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
$ cd /Users/vagrant/git

 (i) No Gemfile found - using system installed fastlane ...
 (i) Updating system installed fastlane ...
$ gem install fastlane --no-document
Successfully installed fastlane-1.87.0
1 gem installed

Fastlane version:
$ fastlane --version
fastlane 1.87.0

Run fastlane:
$ fastlane createpp
[04:59:08]: ---------------------------
[04:59:08]: --- Step: opt_out_usage ---
[04:59:08]: ---------------------------
[04:59:08]: Disabled upload of used actions
[04:59:08]: -------------------------------------------------
[04:59:08]: --- Step: Verifying required fastlane version ---
[04:59:08]: -------------------------------------------------
[04:59:08]: fastlane version valid
[04:59:08]: ------------------------------
[04:59:08]: --- Step: default_platform ---
[04:59:08]: ------------------------------
[04:59:08]: Driving the lane 'ios createpp' �
[04:59:08]: ------------------
[04:59:08]: --- Step: sigh ---
[04:59:08]: ------------------

+-------------------------------------+--------------------------+
|                     Summary for sigh 1.8.0                     |
+-------------------------------------+--------------------------+
| username                            |<EMAIL_ADDRESS> |
| app_identifier                      | com.apptuse.app640027044 |
| cert_id                             | V3B83N3STU               |
| skip_install                        | true                     |
| force                               | true                     |
| filename                            | pp.mobileprovision       |
| adhoc                               | false                    |
| development                         | false                    |
| ignore_profiles_with_different_name | false                    |
| skip_fetch_profiles                 | false                    |
| skip_certificate_verification       | false                    |
+-------------------------------------+--------------------------+

[04:59:08]: Starting login with user<EMAIL_ADDRESS>[04:59:10]: Successfully logged in
[04:59:10]: Fetching profiles...
security: SecKeychainSearchCopyNext: The specified item could not be found in the keychain.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1062  100  1062    0     0   1581      0 --:--:-- --:--:-- --:--:--  1580
[04:59:16]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[04:59:16]: Certificate for Provisioning Profile 'Fresh 5' not available locally: ASGSBNC554
[04:59:16]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[04:59:16]: Certificate for Provisioning Profile 'Fresh 5 PP' not available locally: ASGSBNC554
[04:59:16]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[04:59:17]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[04:59:17]: No certificates for filter: Certificate ID: 'V3B83N3STU'
[04:59:17]: -------------------
[04:59:17]: --- Step: slack ---
[04:59:17]: -------------------
[04:59:18]: Successfully sent Slack notification
[04:59:18]: Variable Dump:
[04:59:18]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios createpp"}
[04:59:18]: Could not find a matching code signing identity for type 'AppStore'. You can use cert to generate one:
https://github.com/fastlane/fastlane/tree/master/cert

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | opt_out_usage                       | 0           |
| 2    | Verifying required fastlane version | 0           |
| 3    | default_platform                    | 0           |
| 4    | sigh                                | 9           |
| 5    | slack                               | 0           |
+------+-------------------------------------+-------------+

[04:59:18]: fastlane finished with errors

Following is the Fastfile content
opt_out_usage

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "1.87.0"

default_platform :ios

platform :ios do
  before_all do
    ENV["SLACK_URL"] = "https://hooks.slack.com/services/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"

    # increment_build_number
    # xctool # run the tests of your app
  end

  desc "Dummy lane to test Fastlane installation"
  lane :ftest do

  end

  desc "Create App Identifier in Apple Developer Console"
  lane :createappid do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    produce(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  app_name: "ATABG - App ZZZ_AT_APP_ID",
	  sku: "apptuseappZZZ_AT_APP_ID",
	  skip_itc: true
    )
  end

  desc "Create App in iTunesConnect"
  lane :createappitc do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    produce(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  app_name: "ZZZ_AT_APP_DISPLAY_NAME - ATABG",
	  app_version: "ZZZ_AT_APP_FIRST_VERSION",
	  language: "English",
	  sku: "apptuseappZZZ_AT_APP_ID",
	  skip_devcenter: true
    )
  end

  desc "Create and Download Provisioning Profiles from Apple Developer Console"
  lane :createpp do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    sigh(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  #adhoc: true,
	  cert_id: "ZZZ_AT_CERT_ID",
	  skip_install: true,
	  force: true,
	  filename: "pp.mobileprovision"
    )
  end

  desc "Create and Download Adhoc Provisioning Profiles from Apple Developer Console"
  lane :createadhocpp do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    sigh(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  adhoc: true,
	  cert_id: "ZZZ_AT_CERT_ID",
	  skip_install: true,
	  force: true,
	  filename: "pp.mobileprovision"
    )
  end

  desc "Create and Download APNS Certificate from Apple Developer Console"
  lane :createpem do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    pem(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  generate_p12: true,
	  p12_password: "apptuse"
    )
  end

  desc "Capture Screenshots"
  lane :capturescrn do
	snapshot(
      reinstall_app: true,
	  stop_after_first_error: true
    )
	snapshot
  end

  desc "Upload ipa, screenshots and meta data to iTunesConnect"
  lane :uploadmeta do
    ENV["FASTLANE_PASSWORD"] = "ZZZ_AT_APPLE_PASSWORD"
    deliver(
      username: "ZZZ_AT_APPLE_ID",
      app_identifier: "ZZZ_AT_APP_IDENTIFIER",
	  ipa: "ZZZ_AT_IPA_PATH",
	  app_version: "ZZZ_AT_APP_VERSION",
	  submit_for_review: false,
	  automatic_release: true,
	  app_icon<EMAIL_ADDRESS>	  force: true
    )
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    slack(
      message: exception.message,
      success: false
    )
  end
end

Please help to sort this issue asap.

@gauravdaxini Thanks for following up.  Let me know! Thanks 👍

Hi @TKBurner! We have already done this before please see the error response in this comment.

@gauravdaxini Thanks for following up. What happens if you set force: true for cert? Thanks for working with me on this. Also, can you check your iTC account? Thanks

Hi @TKBurner! Sorry for troubling you. But still stuck with this issue. I'm getting the following error when I set force:true for cert.
+---------------+-------------------------------------------------+
|                     Summary for cert 1.4.1                      |
+---------------+-------------------------------------------------+
| force         | true                                            |
| development   | false                                           |
| username      |<EMAIL_ADDRESS>                        |
| keychain_path | /Users/vagrant/Library/Keychains/login.keychain |
+---------------+-------------------------------------------------+

[21:40:12]: Starting login with user<EMAIL_ADDRESS>[21:40:14]: Successfully logged in
[21:40:15]: -------------------
[21:40:15]: --- Step: slack ---
[21:40:15]: -------------------
[21:40:16]: Successfully sent Slack notification
[21:40:16]: Variable Dump:
[21:40:16]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios createpp"}
[21:40:16]: Could not create another certificate, reached the maximum number of available certificates.

+------+-------------------------------------+-------------+
|                     fastlane summary                     |
+------+-------------------------------------+-------------+
| Step | Action                              | Time (in s) |
+------+-------------------------------------+-------------+
| 1    | opt_out_usage                       | 0           |
| 2    | Verifying required fastlane version | 0           |
| 3    | default_platform                    | 0           |
| 4    | cert                                | 3           |
| 5    | slack                               | 0           |
+------+-------------------------------------+-------------+

[21:40:16]: fastlane finished with errors

[!] Could not create another certificate, reached the maximum number of available certificates.

Also, what should I need to check in my iTC account?

As the message says, you don't have space for another certificate

[!] Could not create another certificate, reached the maximum number of available certificates.
You'll need to revoke an existing one to make space for a new one. Also, we recommend using match to follow the codesigning.guide, this way you'll always have access to both your certificate and private key 👍

Hi @KrauseFx! We are using the Bitrise CLI for auto-building the apps, the above(cert and sigh) steps will be executed every time we run a workflow for an app. Means for every app we will have to revoke one certificate?
Earlier we were only using the Sigh step for creating the provisioning profile certificate and it was working perfectly fine. But from the last couple of months, we are facing the local code signing identity issue in the sigh step.

Hey @gauravdaxini! Thanks for following up. I think you'll be a lot happier using match, can you check it out for me? Thanks 👍

@KrauseFx
I'm getting this error after running match:
[07:01:02]: Cloning remote git repo...
[07:01:05]: 🔓  Successfully decrypted certificates repo
[07:01:05]: Verifying that the certificate and profile are still valid on the Dev Portal...
[07:01:08]: Installing certificate...
[07:01:08]: There are no local code signing identities found. You can run `security find-identity -v -p codesigning` to get this output. This Stack Overflow thread has more information: http://stackoverflow.com/q/35390072/774. (Check in Keychain Access for an expired WWDR certificate: http://stackoverflow.com/a/35409835/774 has more info.)
[07:01:09]: Installing provisioning profile...


Could be an issue, just posting my problem.

I have this config file that I just assume is VDF inside one of my game installations called "app.config". Im writing a program but want to make sure the selected folder is in fact a steam game folder.
Here is the file:
{
	"xal":
	{
		"title_id":1144039928,
		"service_config_id":"77290100-225e-4768-9373-98164430a9f8",
		"client_id":"000000004825FC1F"
	},
	"steam":
	{
		"app_id":976730
	}
}

I did what the README said to do:
dynamic data = VdfConvert.Deserialize(File.ReadAllText("app.config"));

My issue is that I only have access to the property "xal":

If the file I'm using isn't a valid VDF, please excuse my assumptions and close this issue, thanks!

The file you posted appears to be a standard JSON file. You can use STJ to deserialize it like JsonSerializer.Deserialize(...).


Bump framework and oauth versions

$subject
Related issues:

https://github.com/wso2/product-is/issues/19085
https://github.com/wso2/product-is/issues/18992
https://github.com/wso2/product-is/issues/19054

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7612882291

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/7612882291
Status: failure

Updated with https://github.com/wso2/product-is/pull/19105


Fix setup.py

fix setup.py and quick_install, added warning to lm.py to show warning if can't import kenlm

@wangyu09 Please merge to master

@wangyu09 Please merge to master


Add at function for we chat

Added enterprise weChat robot  @ function

@tomsun28 cr ，please

Code checkstyle is failed, please refer to here and ensure it passes the local test first.


Tensorflow 2.0 does not use GPU

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
TensorFlow installed from (source or binary): yes
TensorFlow version (use command below): 2.0.0-beta1
Python version: 3.7
CUDA/cuDNN version: 10.1
GPU model and memory: Nvidia MX250 4Gb

Describe the current behavior
I'm playing around with tf2.0 while mostly still working on tf1.14. I have created two conda environments - one for tf1.14 and the other one for tf2.0 - so all hardware and drivers are absolutely the same. Tf1.14 is working good and uses gpu as it supposed to, but tf2.0 runs on cpu.
Code to reproduce the issue
if i run:
from tensorflow.python.client import device_lib
device_lib.list_local_devices()

i get an output with tf2.0:

[name: "/device:CPU:0"
 device_type: "CPU"
 memory_limit: 268435456
 locality {
 }
 incarnation:<PHONE_NUMBER>404595310, name: "/device:XLA_CPU:0"
 device_type: "XLA_CPU"
 memory_limit:<PHONE_NUMBER>4
 locality {
 }
 incarnation:<PHONE_NUMBER>557013132
 physical_device_desc: "device: XLA_CPU device", name: "/device:XLA_GPU:0"
 device_type: "XLA_GPU"
 memory_limit:<PHONE_NUMBER>4
 locality {
 }
 incarnation:<PHONE_NUMBER>675012648
 physical_device_desc: "device: XLA_GPU device"]

and

import tensorflow as tf
tf.test.is_gpu_available()

gives False.
Same code in tf1.14 gives the following:

[name: "/device:CPU:0"
 device_type: "CPU"
 memory_limit: 268435456
 locality {
 }
 incarnation:<PHONE_NUMBER>5111208996, name: "/device:XLA_CPU:0"
 device_type: "XLA_CPU"
 memory_limit:<PHONE_NUMBER>4
 locality {
 }
 incarnation:<PHONE_NUMBER>411904965
 physical_device_desc: "device: XLA_CPU device", name: "/device:GPU:0"
 device_type: "GPU"
 memory_limit:<PHONE_NUMBER>
 locality {
   bus_id: 1
   links {
   }
 }
 incarnation:<PHONE_NUMBER>7157719353
 physical_device_desc: "device: 0, name: GeForce MX250, pci bus id: 0000:02:00.0, compute capability: 6.1", name: "/device:XLA_GPU:0"
 device_type: "XLA_GPU"
 memory_limit:<PHONE_NUMBER>4
 locality {
 }
 incarnation:<PHONE_NUMBER>1972383985
 physical_device_desc: "device: XLA_GPU device"]

And:

import tensorflow as tf
tf.test.is_gpu_available()

Gives True

Are you sure your GPU matches the required CUDA® Compute Capability 3.5 or higher? I couldn't find it in the list on the website of nvidia.

i could't find my gpu there as well. But apparently it's supported since it's working with tensorflow 1.14 - i can successfully train models and it works much faster then on cpu and i can see the gpu load. And also nvidia-smi shows cuda version:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 430.40       Driver Version: 430.40       CUDA Version: 10.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce MX250       Off  | 00000000:02:00.0 Off |                  N/A |
| N/A   43C    P8    N/A /  N/A |      4MiB /  4042MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

Did you install TF 1.14, 2.0 from source or binary?
Also did you install TF-GPU version for both versions of TF?
Can you please check with tf.test.is_built_with_cuda for both TF versions?

I install tensorflow 2.0 using pip (since conda install is not available for this version) and tensorflow 1.14 using conda.
Yes, both gpu versions
Just did  - both return True

Thanks. I suspect, you haven't added cuda path to the TF 2.0 environment. You need to manually add this after doing pip install.

can you elaborate a bit more on how to do it? I've tried to google it and couldn't find any info on how to add cuda path to tensorflow

Sure. Take a look at https://www.tensorflow.org/install/gpu#linux_setup

Could this happen because @andrey999333 uses cuda 10.1, while the pip wheel was built for cuda 10.0 ?
@ymodak do you know why TensorFlow 2.0 on pypi is not yet built for cuda 10.1, library released in February ?


Add py.typed marker

The code is mostly typed so I think it should have py.typed included.
Mypy will not recognise this project's imports as being typed without seeing a py.typed file in the module (the ninja_jwt directory). VS Code will not recognise the types without first opening the relevant Python file.

Thanks.


Check for bad wheel first before checking the metadata matches

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/derekbekoe/azure-cli-extensions.git@ci-check-wheel-first#subdirectory=src/$EXT&egg=$EXT"


Feature requst: add retry mechanism

When installing apps with brew cask, it sometimes fails with download error after having some progress(for example 5%). I have to manually resume the download for many times to finish the installation.(I believe this is very common for people in China.)
I hope we can pass an argument such as -R to the command that the download can auto resume.

That kind of basic feature (downloading) we get from homebrew. Also, since we’re in talks to merge the codebases even further, this is really something you should ask them, as that will benefit more people.


fix: remove the extension from the import to fix style in the admin

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1461   +/-   ##
=======================================
  Coverage   98.99%   98.99%
=======================================
  Files         496      496
  Lines       10271    10271
  Branches     2370     2370
=======================================
  Hits        10168    10168
  Misses        103      103

Continue to review full report at Codecov.

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


rustup update should run self update first

Currently, running rustup update updates all toolchains and then runs self update.
It might be wise to run self update first, to pick up

possible changes in the metadata format,
security fixes for downloading,
new compression options,
and other improvements

as soon as possible and use them for updating the toolchain.
One difficulty might be that rustup will need to restart itself/start the new version when there was an update before running the toolchain updates.

I agree that it would be better to do the self-update first, but it's very tricky. On windows, we can't replace the rustup executable while rustup is running, so the last thing rustup update does is exit successfully, then a separate process overwrites rustup.exe. So there's a chance the update actually fails but doesn't get reported. If we were to do incompatible metadata changes before overwriting the exe, and then the self-update fails, rustup could be left completely broken.

You can rename a running process though, so we can have rustup download the new version, rename itself to a temp directory, call the new rustup with the original update command line (piping stdin/stdout through the old rustup), and then delete itself. If the self deletion fails we get a left-over executable in your temp directory rather than a broken installation.

Ah yes that does seem doable.

Not running rustup self update first seems to have caused upgrades to fail for a lot of people.


How to recover the GLSL setting of realsense-viewer

librealsense
2.33.4

OS
Raspberry Debian

When enable 'use GLSL for Rending' and 'use GLSL for Processing' in the setting panel, the realsense-viewer can't be launched anymore. The error message is that 'GLSL 1.30 is not supported'. Due to the GUI is not availble anymore, I can't recover the setting, but I don't know where the configuration file is. I uninstalled and install again, the problem still exists.

I hope that the link below will be useful in helping you to locate the Viewer's configuration file.
https://github.com/IntelRealSense/librealsense/issues/3821#issuecomment-485668383

If you cannot access the UI,
rm ~/.realsense-config.json

This will reset everything to default

Case closed due to no further comments received.


Add debug mode for testing - don't delete jaeger instance or namespac…

…e on test failure
Signed-off-by: Kevin Earls<EMAIL_ADDRESS>

@objectiser @jpkrohling @pavolloffay Please review


speed dial demo not working for me

the other demo elements work, but speed dial fails for me (in Chrome) and I see this error in dev tools:
Uncaught TypeError: Failed to execute 'animate' on 'Element': 'function (a){return a}' is not a valid value for easing

Can you link to the problem?

I just go to this link:
http://gabiaxel.github.io/paper-fab-transitions/components/paper-fab-transitions/demo/

polymer.html:1089 Uncaught TypeError: Failed to execute 'animate' on 'Element': 'function (a){return a}' is not a valid value for easing
at Object.b.newUnderlyingAnimationForKeyframeEffect (web-animations-next-lite.min.js:16)
at b.Animation._rebuildUnderlyingAnimation (web-animations-next-lite.min.js:15)
at new b.Animation (web-animations-next-lite.min.js:15)
at b.AnimationTimeline._play (web-animations-next-lite.min.js:15)
at Object.b.newUnderlyingAnimationForGroup (web-animations-next-lite.min.js:16)
at b.Animation._rebuildUnderlyingAnimation (web-animations-next-lite.min.js:15)
at new b.Animation (web-animations-next-lite.min.js:15)
at b.AnimationTimeline._play (web-animations-next-lite.min.js:15)
at b.AnimationTimeline.play (web-animations-next-lite.min.js:15)
at HTMLElement._runAnimationEffects (neon-animation-runner-behavior.html:62)


Fixed the bind this on moleculer-bull

Hi @icebob!
The new release of moleculer-bull is breaking the process method of bull because is binding to null the this object of bull this.getQueue(name).process.apply(null, args);
related line in bull
This PR will fix the issue.

Pull Request Test Coverage Report for Build 254

1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.08%

Totals

Change from base Build 253:
0.0%

Covered Lines:
200

Relevant Lines:
200

💛  - Coveralls

Pull Request Test Coverage Report for Build 254

1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.08%

Totals

Change from base Build 253:
0.0%

Covered Lines:
200

Relevant Lines:
200

💛  - Coveralls

Released


Prepare for release v1.15.6

Prepare for release v1.15.6
Summary of Changes
Minor Changes:

[v1.15] fqdn: Forward-compatibility with Cilium 1.16 FQDN identities (cilium/cilium#32872, @gandro)
Generate SBOMs using Syft instead of bom (Backport PR #32691, Upstream PR #32307, @ferozsalam)
Improved background resynchronization of nodes. Before all nodes were being updated at the same time, now we spread updates over time to average out CPU usage. (Backport PR #32748, Upstream PR #32577, @marseel)
Introduce CLI commands to troubleshoot connectivity issues to the etcd kvstore and clustermesh control plane (Backport PR #32568, Upstream PR #32336, @giorio94)
ipsec: Improve CPU usage of cilum-agent in large clusters (Backport PR #32882, Upstream PR #32588, @marseel)
KVStoreMesh: expose remote clusters information and introduce dedicated CLI command (Backport PR #32568, Upstream PR #32156, @giorio94)

Bugfixes:

.github/workflows: fix digests file creation (Backport PR #32889, Upstream PR #32860, @aanm)
[v1.15] iptables: Do not install NOTRACK rules if IPv4NativeRoutingCIDR is nil (cilium/cilium#32649, @pippolo84)
Add missing kvstore-max-consecutive-quorum-errors option to clustermesh-apiserver/kvstoremesh binaries (Backport PR #32500, Upstream PR #32117, @giorio94)
bgp: service eTP=local, withdraw route when last backend on the node goes in terminating state (Backport PR #32691, Upstream PR #32536, @harsimran-pabla)
Cilium BGPv1 Reconciler - Handle updated and deprecated Cidr fields for CiliumLoadBalancerIPPool (Backport PR #32889, Upstream PR #32694, @dswaffordcw)
cni: Reserve local ports for DNS proxy even if IPv6 is disabled (Backport PR #32789, Upstream PR #32725, @gandro)
egressgw: Let the EGW manager relax rp_filter on egress device (Backport PR #32778, Upstream PR #32679, @ysksuzuki)
Fix DNS proxy regression from Cilium 1.15 on IPv4 only nodes (Backport PR #32789, Upstream PR #31671, @foyerunix)
Fix indexing bug in the logic for picking NodePort addresses. In rare cases this may have caused wrong address to be selected for NodePort use, or an out-of-bounds access. (Backport PR #32691, Upstream PR #32506, @joamaki)
Fix PromQL query in Cilium Metrics dashboard (Backport PR #32691, Upstream PR #32017, @mikemykhaylov)
Fix rare race condition afflicting clustermesh when disconnecting from a remote cluster, possibly causing the agent to panic (Backport PR #32691, Upstream PR #32513, @giorio94)
Fixes accidentally ignoring the preflight.nodeSelector Helm value. (Backport PR #32691, Upstream PR #32548, @squeed)
Fixes unencrypted traffic among nodes when IPsec is used with L7 egress proxy. (Backport PR #32932, Upstream PR #32683, @jschwinger233)
ingress: Set the default value for max_stream_timeout (Backport PR #32889, Upstream PR #31514, @tskinn)
Introduce timeout when waiting for the initial synchronization from remote clusters, to avoid blocking forever necessary GC operations in case of clustermesh misconfigurations. (Backport PR #32802, Upstream PR #32671, @giorio94)
ipsec: Safely delete Xfrm state (Backport PR #32691, Upstream PR #32450, @jschwinger233)
proxy: Re-enable proxy rule installation in native-routing mode for CEC (Backport PR #32481, Upstream PR #32367, @sayboras)
Remove deprecated hubble.ui.securityContext.enabled from hubble-ui deployment template (Backport PR #32889, Upstream PR #32338, @stelucz)

CI Changes:

CI: Add job name validation (Backport PR #32500, Upstream PR #32462, @brlbil)
ci: Filter supported versions of EKS (Backport PR #32889, Upstream PR #32304, @marseel)
ci: Filter supported versions of GKE (Backport PR #32691, Upstream PR #32302, @marseel)
ci: l4lb: gather more infos about docker-in-docker issues (Backport PR #32691, Upstream PR #32570, @mhofstetter)
ci: l4lb: restart docker-in-docker container on failure (Backport PR #32691, Upstream PR #32600, @mhofstetter)
eks: Don't use spot instances (Backport PR #32691, Upstream PR #32553, @michi-covalent)
GCP OIDC instead of SA creds. (Backport PR #32707, Upstream PR #30809, @viktor-kurchenko)
gha: cover TLS auth mode in clustermesh upgrade/downgrade tests (Backport PR #32789, Upstream PR #32684, @giorio94)
gha: test certificate generation methods in conformance clustermesh (Backport PR #32789, Upstream PR #32654, @giorio94)
Modify GitHub Actions Workflows to echo the inputs they are given when triggered by a workflow_dispatch event. (Backport PR #32500, Upstream PR #31424, @learnitall)
Use GH_RUNNER_EXTRA_POWER for CI image workflow (Backport PR #32500, Upstream PR #32402, @michi-covalent)
workflows: ignore "No egress gateway found" drops (Backport PR #32691, Upstream PR #32564, @jibi)
workflows: Remove stale CodeQL workflow (Backport PR #32691, Upstream PR #32084, @pchaigno)

Misc Changes:

(v1.15) Bump go-jose (cilium/cilium#32869, @ferozsalam)
(v1.15) Bump golang.org/x/net (cilium/cilium#32793, @ferozsalam)
background-sync: fix bootstrap issue and edge-case with 1 node (Backport PR #32748, Upstream PR #32630, @marseel)
bpf: add ext_err for more callers of tail_call_internal() (Backport PR #32332, Upstream PR #30023, @julianwiedmann)
bpf: add improved helper for program-internal tail-call (Backport PR #32332, Upstream PR #30001, @julianwiedmann)
bpf: add multicast in MAX_OVERLAY_OPTIONS (Backport PR #32332, Upstream PR #32129, @harsimran-pabla)
bpf: convert ep_tail_call() to tail_call_internal() (Backport PR #32332, Upstream PR #30288, @julianwiedmann)
bpf: egw: delay SNAT for local client to actual egress interface (Backport PR #32789, Upstream PR #32428, @julianwiedmann)
bpf: hide dynamic/static variant for policy tail-call (Backport PR #32332, Upstream PR #32299, @julianwiedmann)
bpf: minor tail-call cleanups (Backport PR #32332, Upstream PR #31990, @julianwiedmann)
bump cni plugins to v1.5.0 (Backport PR #32691, Upstream PR #32629, @antonipp)
Bump timeout of lint-build-commits.yaml (Backport PR #32789, Upstream PR #32746, @YutaroHayakawa)
chore(deps): update all github action dependencies (v1.15) (cilium/cilium#32493, @renovate[bot])
chore(deps): update all github action dependencies (v1.15) (cilium/cilium#32632, @renovate[bot])
chore(deps): update all github action dependencies (v1.15) (cilium/cilium#32719, @renovate[bot])
chore(deps): update all github action dependencies (v1.15) (cilium/cilium#32841, @renovate[bot])
chore(deps): update all github action dependencies (v1.15) (cilium/cilium#32923, @renovate[bot])
chore(deps): update all github action dependencies (v1.15) (patch) (cilium/cilium#32633, @renovate[bot])
chore(deps): update cilium/cilium-cli action to v0.16.7 (v1.15) (cilium/cilium#32395, @renovate[bot])
chore(deps): update cilium/little-vm-helper action to v0.0.18 (v1.15) (cilium/cilium#32580, @renovate[bot])
chore(deps): update dependency cilium/cilium-cli to v0.16.8 (v1.15) (cilium/cilium#32780, @renovate[bot])
chore(deps): update dependency cilium/cilium-cli to v0.16.9 (v1.15) (cilium/cilium#32835, @renovate[bot])
chore(deps): update dependency cilium/hubble to v0.13.4 (v1.15) (cilium/cilium#32519, @renovate[bot])
chore(deps): update dependency cilium/hubble to v0.13.5 (v1.15) (cilium/cilium#32948, @cilium-renovate[bot])
chore(deps): update docker.io/library/ubuntu:22.04 docker digest to 19478ce (v1.15) (cilium/cilium#32922, @renovate[bot])
chore(deps): update gcr.io/etcd-development/etcd docker tag to v3.5.14 (v1.15) (cilium/cilium#32838, @renovate[bot])
chore(deps): update go (v1.15) (cilium/cilium#32623, @renovate[bot])
chore(deps): update go to v1.21.11 (v1.15) (cilium/cilium#32894, @renovate[bot])
chore(deps): update quay.io/cilium/hubble docker tag to v0.13.4 (v1.15) (cilium/cilium#32634, @renovate[bot])
chore(deps): update stable lvh-images (v1.15) (patch) (cilium/cilium#32635, @renovate[bot])
contrib: Remove CHARTS_PATH dependency (Backport PR #32691, Upstream PR #32328, @joestringer)
datapath: report distinct drop reason for missed endpoint policy tailcall (Backport PR #32332, Upstream PR #32151, @julianwiedmann)
docs: Add example for kube-apiserver entity policy (Backport PR #32500, Upstream PR #32278, @joestringer)
Docs: add note about AKS kube-apiserver entity (Backport PR #32691, Upstream PR #32464, @darox)
docs: ipsec: remove limitation for native-routing with L7 egress policy (Backport PR #32955, Upstream PR #32906, @julianwiedmann)
Miscellaneous improvements to the clustermesh troubleshooting guide (Backport PR #32568, Upstream PR #32552, @giorio94)

Other Changes:

[v1.15] bugtool: Avoid sensitive data in envoy config dump (cilium/cilium#32964, @sayboras)
[v1.15] envoy: Bump envoy version to v1.28.4 (cilium/cilium#32908, @sayboras)
Fix: LB service lookup for flow matching conntrack entry (cilium/cilium#32608, @sypakine)
install: Update image digests for v1.15.5 (cilium/cilium#32544, @nebril)
Revert golang image version of hubble-relay (cilium/cilium#32732, @YutaroHayakawa)

⚠⚠⚠ i used a modified version of start-release.sh because i could not create a project for v1.15.7 due to https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/.
as a result, https://github.com/cilium/cilium/blob/9299c0fd0024e33397cffc666ff851e82af28741/.github/maintainers-little-helper.yaml#L1 is still pointing to v1.15.6 project.


Bug: Wrong link to scaler code in documentation

The auto generated website with scaler documentation pointing to a wrong branch, when you click a "scaler code" button.
As an example:
On Log Analytics Scaler web page "scaler source" button points to this page: https://github.com/kedacore/keda/blob/master/pkg/scalers/azure_log_analytics_scaler.go
But should point to this page: https://github.com/kedacore/keda/blob/v2/pkg/scalers/azure_log_analytics_scaler.go
The difference is in branch name.

Good catch, this should be fixed, but we are planning to rename v2 branch back once 2.0 is out, so we can wait for a wihle.

Closing since this is fixed.


Consider adding a headless service in addition to the clusterIP

A headless service using label selectors is a great way to expose pod addresses to clients and enable them to do client-side load balancing within the cluster.
Here's an example of how to configure them: https://github.com/deps-cloud/deps-cloud-project/blob/master/examples/k8s/manifests/tracker.yaml#L46-L61

ah, missed that myrabbitmq-svc-discovery exists.


fix: allow Gnosis Safe style proxies to work with earlier deployments

What I did
Prior to v1.1.0, masterCopy was not available as an external method. This means that our proxy detection would not be able to detect it as a Gnosis Safe-style proxy. Additionally, once deployed, this style of proxy is immutable, so even if the Safe itself is upgraded to a newer version, this method still would not be available to be called.
NOTE: This slightly modifies the proxy info's target to be obtained
dynamically from retreiving the storage for masterCopy directly.
How I did it
Since masterCopy() is not an available method to call, but NAME() has always existed in every Gnosis Safe version, I decided to use that instead. I noticed that there are few different names in use, so we check that it matches one of those
How to verify it
Go load a safe via Contract for every version that's been deployed
Checklist

[x] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

Versions tested:

[x] 1.3.0
[x] 1.1.1

I am trying to find older versions!

Versions tested:

[x] 1.3.0
[x] 1.1.1

I am trying to find older versions!

I tested with 1.1.0
Need to find 1.0.0 and 1.2.0 versions I think

I found a strange issue with 1.1.1.
Take a look at the contract 0x42F38ec5A75acCEc50054671233dfAC9C0E7A3F6. It is a gnosis safe proxy that points to the Gnosis safe proxy 0x34CfAC646f301356fAa8B21e94227e3583Fe3F5F. The target address is for some recognized as another gnosis safe proxy but I think it might be the actual safe because it has lots of transactions on Etherscan. But since it attempts gnosis-safe style detection, it fails.

0x42F38ec5A75acCEc50054671233dfAC9C0E7A3F6

This is actually the Gnosis Chain bridge contract.... weird!

I found a strange issue with 1.1.1. Take a look at the contract 0x42F38ec5A75acCEc50054671233dfAC9C0E7A3F6. It is a gnosis safe proxy that points to the Gnosis safe proxy 0x34CfAC646f301356fAa8B21e94227e3583Fe3F5F. The target address is for some recognized as another gnosis safe proxy but I think it might be the actual safe because it has lots of transactions on Etherscan. But since it attempts gnosis-safe style detection, it fails.

f3e190f resolves the issue of incorrectly detecting a target of an unitialized proxy of this type. Still need to discover when this method is being called on 0x34CfAC646f301356fAa8B21e94227e3583Fe3F5F though

f3e190f resolves the issue of incorrectly detecting a target of an unitialized proxy of this type.

It works!

I finally found a few 1.0.0 (I think). They ain't working:
0x7e63B92fA0056eA475f419663c0DE7DE53BbABb4
0x01a5212208Bd7bC53c1F3eE00e1945B95bFeCa10
0x2201f5D1Ed7ef8428497D3EdB50Cafc8F6D440CF
0x65413B599C14e341AA2F4eD46EaD7664d111CAD0
Note that I have literally checked hundreds of safes. Most of them are 1.3.0 and a large number are 1.1.1.
It forever to find these 1.0.0 versions! I created a webscraper script that finds Ethereum addresses and checks them for safes. It has been running for a while.

0x71b94163b085cc2ea7432d8cc96a94989da4fd6e (failing detection) claims to be using 1.1.1 but it kind of seems like a custom proxy to me... Are you able to use custom proxies for safes?

I finally found a few 1.0.0 (I think). They ain't working:
0x7e63B92fA0056eA475f419663c0DE7DE53BbABb4
0x01a5212208Bd7bC53c1F3eE00e1945B95bFeCa10
0x2201f5D1Ed7ef8428497D3EdB50Cafc8F6D440CF
0x65413B599C14e341AA2F4eD46EaD7664d111CAD0

These seem to work for me with the update. Are you sure you're using the update?

Note that I have literally checked hundreds of safes. Most of them are 1.3.0 and a large number are 1.1.1. It forever to find these 1.0.0 versions! I created a webscraper script that finds Ethereum addresses and checks them for safes. It has been running for a while.

Hahaha, this is cool! I want to drastically improve the ability to query contract code with the query system, to make searches like these a lot easier (for security professionals as well)


Changing Moment JS locale of axis

Hello,
Changing the locale does not change the locale of the axis.
Could you give some pointers to where I could change these settings?
In the example below I change the locale to 'hr', Croatian. The subtitle does change but the axis stays in English.

This is the same issue as #21.
At the core of the resolution of this issue is that the D3.js locale has to be set to whatever locale is specified by moment.js. I think in an ideal world, we would use resources we already have (moment.js) to translate the axis labels. However, we need to find out how well this plays with D3.js.
Resolution of this conflict might go well with updating the D3.js version, I believe the locale interfaces have changed since I made visavail.js. I do not know when I will get to resolve this issue, but feel free to code up a resolution yourself. This would for sure benefit the project!

Could you explain where in your code the axis is build? That would help me alot.

I now have it hardcoded into the visavail.js script. It would be better if I could get the data from moment.js.
  var germanFormatters = d3.locale({
    "decimal": ",",
    "thousands": ".",
    "grouping": [3],
    "currency": ["€", ""],
    "dateTime": "%a %b %e %X %Y",
    "date": "%d.%m.%Y",
    "time": "%H:%M:%S",
    "periods": ["AM", "PM"],
    "days": ["Sonntag", "Montag", "Dienstag", "Mittwoch", "Donnerstag", "Freitag", "Samstag"],
    "shortDays": ["So", "Mo", "Di", "Mi", "Do", "Fr", "Sa"],
    "months": ["Jänner", "Februar", "März", "April", "Mai", "Juni", "Juli", "August", "September", "Oktober", "November", "Dezember"],
    "shortMonths": ["Jän", "Feb", "Mär", "Apr", "Mai", "Jun", "Jul", "Agu", "Sep", "Okt", "Nov", "Dez"]
  });

  var customTimeFormat = germanFormatters.timeFormat.multi([
    [".%L", function(d) { return d.getMilliseconds(); }],
    [":%S", function(d) { return d.getSeconds(); }],
    ["%I:%M", function(d) { return d.getMinutes(); }],
    ["%Hh", function(d) { return d.getHours(); }],
    ["%a %d", function(d) { return d.getDay() && d.getDate() != 1; }],
    ["%b %d", function(d) { return d.getDate() != 1; }],
    ["%B", function(d) { return d.getMonth(); }],
    ["%Y", function() { return true; }]
      ]);

  // define axes
  var xAxis = d3.svg.axis()
      .scale(xScale)
      .orient('top')
      .tickFormat(customTimeFormat);


Tabs don't respect the safe area for some iPhone users

Tabs don't respect the safe area for some iPhone users

So far two users with same specs.  This also came up in the SUNY field trial.
App Version: <IP_ADDRESS>
Device: iPhone 11
OS version: ios 14.0

This is in the v<IP_ADDRESS> build currently on TestFlight / beta Play Store.

Thanks @AlanSl !  Unfortunately I can't test this as I haven't experienced it myself -- I was reporting it on behalf of a few people in the field trials who saw it.

@denisedresbach are you able to check this and close it, build 52 or 53? I know iPhone R 11 is one of the phones where this had happened but any with the microphone grill as pictured should be okay to confirm it's done.

@AlanSl I wasn't able to test this one, but I can try to figure out how to get the microphone grill to test.

@denisedresbach If you don't have one of the right type of devices to hand don't worry about it, we have tested it so I think we can close this as done.


[ISSUE #461]Purge filterserv related code in client

What is the purpose of the change
fix issue[461]
Brief changelog
1 add  @Deprecated in Class MQClientInstance
2 add @Deprecated in Class ClientConfig
Verifying this change
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.03%) to 42.27% when pulling 55a05b55cab9515ba9769fa3cfd479c2adafd817 on wlliqipeng:develop into 7a6164d4db0dbed88d5ce90201c7f4af88470219 on apache:develop.

LGTM


Fix some IP problems in the build

@bot-gradle test this BD

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build
BuildDistributions build

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

AllSmokeTestsPullRequestFeedback build

The merge queue build has failed. Click here to see all failures.

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

AllSmokeTestsPullRequestFeedback build

@bot-gradle test AST

I've triggered the following builds for you. Click here to see all build failures.

AllSmokeTestsPullRequestFeedback build


Add select all items in record list (includes records on all pages)

Add the capability to select all records in the record list from all pages, and allow bulk editing/deleting/exporting/automation and other things you can do with selected records.

for today: get familiar with  the task and make a plan

Plan

[ ] Add bulk export on the record list
[ ] Fix show deleted records issue on the record list

For today: begin executing the plan of action.

for today: implement REST API for button for selecting all record for all pages

for today: sync with Tomaž to discuss plan of action and continue working on the task

for today: sync with Tomaž and Katrin to discuss blockers and continue working on the task

for today: discuss plan of action with Tomaž and continue working on the task

for today: finish with select service for editing implementation and start working on the service for deleting

for today: discuss blocker with Tomaž and finish with delete and complete functionality

for today: finish with delete and undelete functionality and start working on the exporting for all records

for today: add remaining code to BE and submit for review

for today: open PR for BE part

For today: strat implementing the FE part.

for today: continue working on FE part

for today: add finishing touches to FE and submit code for review in 4h max

for today: discuss blocker with Jože

for today: address what's remaining of the blocker and submit for review by EOD

for today: sync with Tomaž and Jože to discuss review comments and start addressing them


drop python<=3.7 support

iAccording to https://endoflife.date/python python 3.7 has been EOSed 27 Jun 2023.
Filter all python cde over pyupgrade --py38-plus.

Thank you 👍


Enjoyhint in Wordpress

First off, thank you for making Enjoyhint available for free!
I'm just learning javascript, so I'm learning as I go. I'm stuck as to where I would place the codes to make the overlay activate only on the home page?
Would there happen to be a Wordpress tutorial that I could check out? Or would you be able to advise where or how to place the code in my Wordpress site?
Thank you!
P.S. Not sure if this is the proper place to ask for help, GitHub is new to new as well. Apologizes in advance.

Hello, thank you for taking time filling this issue!
Every issue should provide the necessary information for us to investigate. This explains why your issue has been closed. If you still have the issue, please create it again and provide information how to reproduce the issue.


Limiting the tokens per minute to 150000

Request failed: failed sending prompt: [tokens] Rate limit reached for default-text-davinci-003 in organization org-mdLxX2PcWp5fsPwZXFbdHNdI on tokens per min. Limit:<PHONE_NUMBER>00 / min. Current:<PHONE_NUMBER>00 / min. Contact<EMAIL_ADDRESS>if you continue to have issues. Please add a payment method to your account to increase your rate limit. Visit https://platform.openai.com/account/billing to add a payment method.

OpenAI limits rates for their API, this is not something we can circumvent and we cannot throttle requests as aiac performs individual requests and doesn't have "context". If you are using aiac programmatically, you will need to implement throttling yourself. I've added information about this to the README.


How to avoid Username/Password prompt

See my code below - I've tried multiple things but always get prompted for username/password. Is there any way to avoid this. Your help much appreciated.
from blinkpy import api, blinkpy
from blinkpy.auth import Auth
blink = blinkpy.Blink()
auth = Auth(
{
    "username": "xxxxxxxxxxxxx",
    "password": "yyyyyyyyyyyy"
},
no_prompt=True

)
#blink.auth = auth
blink.start()
blink.save("BlinkAuth.json")

Dumb mistake - blink.auth=auth commented out!!!


♻ Improve ES index management command and tests

Purpose
While trying to solve #939, we looked at the index_manager tests.
We noticed they were using a lot of mocks such that they provided very little confidence in the code actually working as intended.
Proposal
We replaced two heavily mocked tests with an entirely non-mocked one that should cover the same code surface with more confidence.
We also touched up on the code in the index_manager module, eg. fixing a small bug we encountered and replacing format calls with f strings.
This did not find us the bug as we had hoped it might, but it's an improvement nonetheless.

Replaced by #945 which actually fixes the bug.


Universal FS module

Similar to the @effect-ts/node/FileSystem, @mikearnaldi suggested the idea to introduce a more universal FS module that could also be used else where e.g. in the browser (see this project) or fully virtualised (e.g. for tests).

Got the idea from TypeScript's Host abstraction where basically the compiler just depends on a Host impl that has access to the filesystem so that the compiler can run regardless of the concrete host. We'd need to isolate the set of features we want for the virtual fs.

closing as it is now part of @effect/platform