ERROR: [6bf004d8] alsa audio output error:...r

Good morning!
I made yesterday a fresh installation of Raspian and AlexaPi but i can't make it works, following error:
ALSA INFO AT: http://www.alsa-project.org/db/?f=ff14c276b1d87c116b56c193c3545ba724d37bdd
Your OS (including version) where you are running AlexaPi:
Raspbian Jessie with PIXEL 4.4

**Your hardware platform and model you are running on:**

Raspberry P3
Description of problem:
Audio issue, Alexa service starts but with following error: [6bf004d8] alsa audio output error:...r
Alexa doesn't speaks

- start service:
sudo systemctl start AlexaPi.service

- check status:
sudo systemctl status AlexaPi.service

pi@raspberrypi:~ $ sudo systemctl status AlexaPi.service
● AlexaPi.service - Alexa client for all your devices
   Loaded: loaded (/usr/lib/systemd/system/AlexaPi.service; enabled)
   Active: active (running) since Sun 2017-06-04 09:04:17 UTC; 6min ago
     Docs: https://github.com/alexa-pi/AlexaPi/wiki
 Main PID: 586 (python)
   CGroup: /system.slice/AlexaPi.service
           └─586 /usr/bin/python /opt/AlexaPi/src/main.py --daemon

Jun 04 09:04:17 raspberrypi systemd[1]: Starting Alexa client for all your d....
Jun 04 09:04:17 raspberrypi systemd[1]: Started Alexa client for all your de....
Jun 04 09:04:26 raspberrypi python[586]: INFO: Checking Internet Connection ...
Jun 04 09:04:27 raspberrypi python[586]: INFO: Connection OK
Jun 04 09:04:27 raspberrypi python[586]: INFO: AVS token: Requesting a new one
Jun 04 09:04:28 raspberrypi python[586]: INFO: AVS token: Obtained successfully
Jun 04 09:04:30 raspberrypi python[586]: [6bf004d8] alsa audio output error:...r
Hint: Some lines were ellipsized, use -l to show in full.

System audio works fine because I've checked it with arecord and then aplay.
aplay /usr/share/sounds/alsa/Front_Center.wav
arecord -f S16_LE -r 16000 -D pulse test.wav
aplay -f S16_LE -r 16000 test.wa
Problem-relevant config.yaml entries:
input_device: "pulse"
output: "pulse"
output_device: ""

Hope someone can help and I posted all the relevant and usefull info.
Thank you all!

Hello,
can you copy/paste the output of:
alsa -l and alsa -L
And the full log:
sudo systemctl stop AlexaPi.service
/opt/AlexaPi/src/main.py -d

(you can exit with Ctrl+C)
Are you using VLC or SOX?
Emerick

pi@raspberrypi:~ $ /opt/AlexaPi/src/main.py -d
INFO: pocketsphinx.c(152): Parsed model-specific feature parameters from /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/feat.params
Current configuration:
[NAME]			[DEFLT]		[VALUE]
-agc			none		none
-agcthresh		2.0		2.000000e+00
-allphone
-allphone_ci		no		no
-alpha			0.97		9.700000e-01
-ascale			20.0		2.000000e+01
-aw			1		1
-backtrace		no		no
-beam			1e-48		1.000000e-48
-bestpath		yes		yes
-bestpathlw		9.5		9.500000e+00
-ceplen			13		13
-cmn			live		batch
-cmninit		40,3,-1		41.00,-5.29,-0.12,5.09,2.48,-4.07,-1.37,-1.78,-5.08,-2.05,-6.45,-1.42,1.17
-compallsen		no		no
-debug					0
-dict					/usr/local/lib/python2.7/dist-packages/pocketsphinx/model/cmudict-en-us.dict
-dictcase		no		no
-dither			no		no
-doublebw		no		no
-ds			1		1
-fdict
-feat			1s_c_d_dd	1s_c_d_dd
-featparams
-fillprob		1e-8		1.000000e-08
-frate			100		100
-fsg
-fsgusealtpron		yes		yes
-fsgusefiller		yes		yes
-fwdflat		yes		yes
-fwdflatbeam		1e-64		1.000000e-64
-fwdflatefwid		4		4
-fwdflatlw		8.5		8.500000e+00
-fwdflatsfwin		25		25
-fwdflatwbeam		7e-29		7.000000e-29
-fwdtree		yes		yes
-hmm					/usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us
-input_endian		little		little
-jsgf
-keyphrase				alexa
-kws
-kws_delay		10		10
-kws_plp		1e-1		1.000000e-01
-kws_threshold		1		1.000000e-10
-latsize		5000		5000
-lda
-ldadim			0		0
-lifter			0		22
-lm
-lmctl
-lmname
-logbase		1.0001		1.000100e+00
-logfn
-logspec		no		no
-lowerf			133.33334	1.300000e+02
-lpbeam			1e-40		1.000000e-40
-lponlybeam		7e-29		7.000000e-29
-lw			6.5		6.500000e+00
-maxhmmpf		30000		30000
-maxwpf			-1		-1
-mdef
-mean
-mfclogdir
-min_endfr		0		0
-mixw
-mixwfloor		0.0000001	1.000000e-07
-mllr
-mmap			yes		yes
-ncep			13		13
-nfft			512		512
-nfilt			40		25
-nwpen			1.0		1.000000e+00
-pbeam			1e-48		1.000000e-48
-pip			1.0		1.000000e+00
-pl_beam		1e-10		1.000000e-10
-pl_pbeam		1e-10		1.000000e-10
-pl_pip			1.0		1.000000e+00
-pl_weight		3.0		3.000000e+00
-pl_window		5		5
-rawlogdir
-remove_dc		no		no
-remove_noise		yes		yes
-remove_silence		yes		yes
-round_filters		yes		yes
-samprate		16000		1.600000e+04
-seed			-1		-1
-sendump
-senlogdir
-senmgau
-silprob		0.005		5.000000e-03
-smoothspec		no		no
-svspec					0-12/13-25/26-38
-tmat
-tmatfloor		0.0001		1.000000e-04
-topn			4		4
-topn_beam		0		0
-toprule
-transform		legacy		dct
-unit_area		yes		yes
-upperf			6855.4976	6.800000e+03
-uw			1.0		1.000000e+00
-vad_postspeech		50		50
-vad_prespeech		20		20
-vad_startspeech	10		10
-vad_threshold		2.0		2.000000e+00
-var
-varfloor		0.0001		1.000000e-04
-varnorm		no		no
-verbose		no		no
-warp_params
-warp_type		inverse_linear	inverse_linear
-wbeam			7e-29		7.000000e-29
-wip			0.65		6.500000e-01
-wlen			0.025625	2.562500e-02
INFO: feat.c(715): Initializing feature stream to type: '1s_c_d_dd', ceplen=13, CMN='batch', VARNORM='no', AGC='none'
INFO: acmod.c(166): Using subvector specification 0-12/13-25/26-38
INFO: mdef.c(518): Reading model definition: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/mdef
INFO: mdef.c(531): Found byte-order mark BMDF, assuming this is a binary mdef file
INFO: bin_mdef.c(336): Reading binary model definition: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/mdef
INFO: bin_mdef.c(516): 42 CI-phone, 137053 CD-phone, 3 emitstate/phone, 126 CI-sen, 5126 Sen, 29324 Sen-Seq
INFO: tmat.c(149): Reading HMM transition probability matrices: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/transition_matrices
INFO: acmod.c(117): Attempting to use PTM computation module
INFO: ms_gauden.c(127): Reading mixture gaussian parameter: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/means
INFO: ms_gauden.c(242): 42 codebook, 3 feature, size:
INFO: ms_gauden.c(244):  128x13
INFO: ms_gauden.c(244):  128x13
INFO: ms_gauden.c(244):  128x13
INFO: ms_gauden.c(127): Reading mixture gaussian parameter: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/variances
INFO: ms_gauden.c(242): 42 codebook, 3 feature, size:
INFO: ms_gauden.c(244):  128x13
INFO: ms_gauden.c(244):  128x13
INFO: ms_gauden.c(244):  128x13
INFO: ms_gauden.c(304): 222 variance values floored
INFO: ptm_mgau.c(476): Loading senones from dump file /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/sendump
INFO: ptm_mgau.c(500): BEGIN FILE FORMAT DESCRIPTION
INFO: ptm_mgau.c(563): Rows: 128, Columns: 5126
INFO: ptm_mgau.c(595): Using memory-mapped I/O for senones
INFO: ptm_mgau.c(838): Maximum top-N: 4
INFO: phone_loop_search.c(114): State beam -225 Phone exit beam -225 Insertion penalty 0
INFO: dict.c(320): Allocating 138824 * 20 bytes (2711 KiB) for word entries
INFO: dict.c(333): Reading main dictionary: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/cmudict-en-us.dict
INFO: dict.c(213): Dictionary size 134723, allocated 1016 KiB for strings, 1679 KiB for phones
INFO: dict.c(336): 134723 words read
INFO: dict.c(358): Reading filler dictionary: /usr/local/lib/python2.7/dist-packages/pocketsphinx/model/en-us/noisedict
INFO: dict.c(213): Dictionary size 134728, allocated 0 KiB for strings, 0 KiB for phones
INFO: dict.c(361): 5 words read
INFO: dict2pid.c(396): Building PID tables for dictionary
INFO: dict2pid.c(406): Allocating 42^3 * 2 bytes (144 KiB) for word-initial triphones
INFO: dict2pid.c(132): Allocated 21336 bytes (20 KiB) for word-final triphones
INFO: dict2pid.c(196): Allocated 21336 bytes (20 KiB) for single-phone word triphones
INFO: kws_search.c(406): KWS(beam: -1080, plp: -23, default threshold -225, delay 10)
2017-06-16 16:24:34 DEBUG: Setting up playback handler: VlcHandler
2017-06-16 16:24:35 INFO: Checking Internet Connection ...
2017-06-16 16:24:35 DEBUG: Starting new HTTPS connection (1): api.amazon.com
2017-06-16 16:24:36 DEBUG: https://api.amazon.com:443 "GET /auth/o2/token HTTP/1.1" 404 29
2017-06-16 16:24:37 INFO: Connection OK
2017-06-16 16:24:37 INFO: AVS token: Requesting a new one
2017-06-16 16:24:37 DEBUG: Starting new HTTPS connection (1): api.amazon.com
2017-06-16 16:24:38 DEBUG: https://api.amazon.com:443 "POST /auth/o2/token HTTP/1.1" 200 976
2017-06-16 16:24:38 INFO: AVS token: Obtained successfully
2017-06-16 16:24:38 DEBUG: Stopping audio play
2017-06-16 16:24:38 DEBUG: Playing audio: /opt/AlexaPi/src/resources/hello.mp3
2017-06-16 16:24:38 DEBUG: Player State: State.Opening
2017-06-16 16:24:38 DEBUG: Player State: State.Playing
2017-06-16 16:24:38 DEBUG: Started play.
[6bf004d8] alsa audio output error: cannot estimate delay: Input/output error
INFO: cmn_live.c(88): Update from < 41.00 -5.29 -0.12  5.09  2.48 -4.07 -1.37 -1.78 -5.08 -2.05 -6.45 -1.42  1.17 >
INFO: cmn_live.c(105): Update to   < 19.86 -1.02 -3.42  1.28  2.80  1.39 -3.45  4.01  3.22  0.58 -1.62  2.71  2.08 >
2017-06-16 16:25:11 DEBUG: Player State: State.Ended
2017-06-16 16:25:11 DEBUG: Finished play.

Hello,

can you copy/paste the output of:
alsa -l and alsa -L
[...]
Are you using VLC or SOX?

And what output device are you using in your config.yaml?
Emerick

I too am having the exact same problem.
alsa -l
-bash:: command not found

@PeterH888 yes sorry it's aplay -L not alsa

no problems. here are the results from aplay -l and aplay -L
I have also included the results of arecord -l and arecord -L as my microphone is working but I get no response when using the wake word.
pi@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 8/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #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=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:~ $ arecord -l
**** List of CAPTURE Hardware Devices ****
card 1: U0x46d0x89d [USB Device 0x46d:0x89d], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0
pi@raspberrypi:~ $ arecord -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=U0x46d0x89d
USB Device 0x46d:0x89d, USB Audio
Default Audio Device
front:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
Front speakers
surround21:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
Direct sample mixing device
dsnoop:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
Direct sample snooping device
hw:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
Direct hardware device without any conversions
plughw:CARD=U0x46d0x89d,DEV=0
USB Device 0x46d:0x89d, USB Audio
Hardware device with all software conversions
Thanks in advance for checking these out

Ok @PeterH888 Alsa seems to detect with no problems your devices.
Try this: https://github.com/alexa-pi/AlexaPi/issues/242#issuecomment-307614824

Thanks EmerickH, I'll give that try.

Hi EmerickH, I have removed Raspian Pixel and installed Raspian Lite. Installed Alexapi from git-hub instructions, configured alsa to my usb mic and 3.5 speaker jack and on boot I hear "hello". When I use the wake word "Alexa", Alexa replies with "yes". When I ask a question I get no response but after about 10 secs I can again use the wake word and Alexa replies with "yes". What am I missing here.

Hello @PeterH888,
what input_device are you using in your config?
Can you copy/paste the output of: arecord -L ?
Emerick

here is the result or  arecord -L
pi@raspberrypi:~ $ arecord -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=Microphone
Logitech USB Microphone, USB Audio
Default Audio Device
sysdefault:CARD=Microphone
Logitech USB Microphone, USB Audio
Default Audio Device
front:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
Front speakers
surround21:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
4.0 Surround output to Front and Rear speakers
surround41:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
iec958:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
IEC958 (S/PDIF) Digital Audio Output
dmix:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
Direct sample mixing device
dsnoop:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
Direct sample snooping device
hw:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
Direct hardware device without any conversions
plughw:CARD=Microphone,DEV=0
Logitech USB Microphone, USB Audio
Hardware device with all software conversions

So you must put input_device: "plughw:CARD=Microphone,DEV=0" in you config file

thank you, I'll do that now.
See https://github.com/alexa-pi/AlexaPi/wiki/Audio-setup-&-debugging
to get a better idea of how to set things in here
Level of log output
default: INFO
set to DEBUG for verbose logging
logging: INFO
sound:
Name of your ALSA microphone/soundcard in arecord -L
input_device: "plughw:CARD=Microphone,DEV=0"
This is here if none of the listed device: "raspberrypi"
This is an override that is normally not needed and is a last resort.
allow_unlisted_input_device: false
playback_handler: "vlc"
you can go here with alsa, pulse or others
keep blank for the best audio output selected by the underlying code
output: "alsa"
output device: "default"
currently supports ALSA only
output_device: "default"
if left empty, won't be passed to the underlying library / command if it supports it
if it doesn't 100% will be used
default_volume: 80
Means the same as above, but is used for media (playing music for example)
Leave blank to use the same setting as for speech content
media_output:
media_output_device:
media_default_volume:
Some device: "raspberrypi"
value is the number of seconds of silence to pad the beginning and end of the audio. Only
the sox handler supports this configuration option.
playback_padding: 0
Amazon Alexa settings
alexa:
Client_ID: "amzn1.application-oa2-client.3050cd75678b4833b2ded8003a6bb5e6"
Client_Secret: "7c1b143d77c23c7cfb214254eb066ffa9abc89e8631d5160ad758f3b44acf125"
Device_Type_ID: "Alexapi"
Security_Profile_Description: "Alexapi"
Security_Profile_ID: "amzn1.application.f3a7aa3ebe0c41fd9d18f9b157d001fe"
refresh_token: "Atzr|IwEBILumV9ae48i2pr_hvJK0wCB26d_FlHumTaB9vgZsjz_Dcu2NaeGEnyp6IAiYRyXcFwMXXYwgBIyMFXKiCun0kXEqWwaqVl9hX4KKUfQsj0VE_BTg2bwwghko-X2UdLRW3S8LbuOq3U6_2hUcVo29OxMU6Cnl2i9$
See https://github.com/alexa-pi/AlexaPi/wiki/Triggers for the description of these options
triggers:
this config gives me the same result
2017-06-20 22:59:22 DEBUG: Stopping audio play
2017-06-20 22:59:22 DEBUG: Playing audio: /opt/AlexaPi/src/resources/alexayes.mp3
2017-06-20 22:59:22 DEBUG: Player State: State.Opening
2017-06-20 22:59:22 DEBUG: Player State: State.Playing
2017-06-20 22:59:22 DEBUG: Started play.
2017-06-20 22:59:22 DEBUG: Player State: State.Ended
2017-06-20 22:59:22 DEBUG: Finished play.
2017-06-20 22:59:22 DEBUG: Setting up recording
2017-06-20 22:59:22 DEBUG: Start recording
2017-06-20 22:59:22 DEBUG: Starting new HTTPS connection (1): access-alexa-na.amazon.com
2017-06-20 22:59:24 DEBUG: Start sending speech to Alexa Voice Service
2017-06-20 22:59:25 DEBUG: End recording
2017-06-20 22:59:25 DEBUG: Finished sending speech to Alexa Voice Service
2017-06-20 22:59:26 DEBUG: Processing Request Response...
2017-06-20 22:59:26 DEBUG: Request Response is null (This is OKAY!)

sudo nano /etc/opt/AlexaPi/config.yaml
Name of your ALSA microphone/soundcard in arecord -L
input_device: "plughw:CARD=Microphone,DEV=0"
playback_handler: "vlc"
output: "alsa"
output_device: "default"
still gets me no response
2017-06-20 22:59:22 DEBUG: Stopping audio play
2017-06-20 22:59:22 DEBUG: Playing audio: /opt/AlexaPi/src/resources/alexayes.mp3
2017-06-20 22:59:22 DEBUG: Player State: State.Opening
2017-06-20 22:59:22 DEBUG: Player State: State.Playing
2017-06-20 22:59:22 DEBUG: Started play.
2017-06-20 22:59:22 DEBUG: Player State: State.Ended
2017-06-20 22:59:22 DEBUG: Finished play.
2017-06-20 22:59:22 DEBUG: Setting up recording
2017-06-20 22:59:22 DEBUG: Start recording
2017-06-20 22:59:22 DEBUG: Starting new HTTPS connection (1): access-alexa-na.amazon.com
2017-06-20 22:59:24 DEBUG: Start sending speech to Alexa Voice Service
2017-06-20 22:59:25 DEBUG: End recording
2017-06-20 22:59:25 DEBUG: Finished sending speech to Alexa Voice Service
2017-06-20 22:59:26 DEBUG: Processing Request Response...
2017-06-20 22:59:26 DEBUG: Request Response is null (This is OKAY!)

This is what I get with: arecord
pi@raspberrypi:~ $ arecord -f S16_LE -r 16000 -D plughw:CARD=Microphone,DEV=0 test.wav
arecord: main:722: audio open error: Device or resource busy

@PeterH888 have you closed the service before?
sudo service AlexaPi stop

not that I can remember
I have used  sudo systemctl stop AlexaPi.service to stop before degugging

does the last line here make any sense to you. It appears as if AlsaAudio is not picking up my microphone.
2017-06-21 00:00:41 DEBUG: Setting up playback handler: VlcHandler
2017-06-21 00:00:41 INFO: Checking Internet Connection ...
2017-06-21 00:00:41 DEBUG: Starting new HTTPS connection (1): api.amazon.com
2017-06-21 00:00:43 DEBUG: https://api.amazon.com:443 "GET /auth/o2/token HTTP/1.1" 404 29
2017-06-21 00:00:43 INFO: Connection OK
2017-06-21 00:00:43 INFO: AVS token: Requesting a new one
2017-06-21 00:00:43 DEBUG: Starting new HTTPS connection (1): api.amazon.com
2017-06-21 00:00:44 DEBUG: https://api.amazon.com:443 "POST /auth/o2/token HTTP/1.1" 200 977
2017-06-21 00:00:44 INFO: AVS token: Obtained successfully
2017-06-21 00:00:44 DEBUG: Stopping audio play
2017-06-21 00:00:44 DEBUG: Playing audio: /opt/AlexaPi/src/resources/hello.mp3
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/usr/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "/opt/AlexaPi/src/alexapi/triggers/pocketsphinxtrigger.py", line 55, in thread
inp = alsaaudio.PCM(alsaaudio.PCM_CAPTURE, alsaaudio.PCM_NORMAL, self._config['sound']['input_device'])
ALSAAudioError: Input/output error [plughw:CARD=Microphone,DEV=0]

@EmerickH   So I have done as suggested and installed pulse audio and this is what I get from here.
pi@raspberrypi:/tmp $ sudo journalctl -u AlexaPi.service
-- Logs begin at Wed 2017-06-21 18:46:28 AEST, end at Wed 2017-06-21 18:47:30 AEST. --
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error
Jun 21 18:46:50 raspberrypi pulseaudio[846]: [alsa-source-USB Audio] alsa-source.c: Failed to set hardware parameters: Input/output error

Closing due to inactivity. Feel free to reopen.


Toggle sidebar items on click.

Small quality of life change to make the sidebar items works as expected (or at least as most people would expect).

Nice! 👍 Very cool - thanks @CrossR !


CQ9A

Key
Value

View
https://database.shabados.com/sources/2/page/158/line/16

Source
Sri Dasam Granth

Page
158

ID
CQ9A

Line
eyk nwmu ko qqu n lXo ]

Depends on https://github.com/GurbaniNow/gurmukhi-fonts/issues/9


chore: merge back main to next

feat: add full width characters (#36)

perf: improve regex perf. by fixing catastrophic backtracking

test: polish tests for kana/kanji fns

feat: add full width characters

docs(readme.md): add link to the website containing demos

chore(release): 1.1.0-next.1 [skip ci]

1.1.0-next.1 (2022-02-20)
Features

add full width characters (#36) (13c162b)

docs: add recipes, contribution guide and TOCs (#37)

docs: add recipes, contribution guide and TOCs

chore(package.json): mark package as no side effects

docs(CONTRIBUTING.md): update size of release diagram

docs(readme.md): add types summary to TOC

docs(readme.md): add treeshake support badge

feat: allow importing package.json (#38)

chore(release): 1.1.0-next.2 [skip ci]

1.1.0-next.2 (2022-02-21)
Features

allow importing package.json (#38) (36198a9)

feat: add support for node >=12.22.0 and remove yarn from engine (#40)

chore(release): 1.1.0-next.3 [skip ci]

1.1.0-next.3 (2022-02-21)
Features

add support for node >=12.22.0 and remove yarn from engine (#40) (5b23783)

docs: add custom recipes to the demo page (#39)

docs: improve seo for docs website

chore(package.json): update keywords for npmjs

docs: add custom recipes to the demo page

docs: upgrade japanese-moji version

docs: make thresholds on demo page configurable (#41)

docs: improve anchor scrolling

docs: make thresholds on demo page configurable

docs: add analytics to the website (#42)

docs: add demo links to recipes.md (#43)

Co-authored-by: semantic-release-bot<EMAIL_ADDRESS>

:tada: This PR is included in version 1.1.0-next.4 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Documentation on how to run the sample project-mockserver-example is very minimal for a beginner

Hi James,
Good Day!
First of all thanks for maintaining this awesome project online.
I could easily try out a cripple of my scenarios with less effort.
I have some suggestions for improving the documentation.
I am beginner in this area of Webservice, REST, etc. I have some very basic knowledge on this area.
Basically what I was trying to do was to run the mock server in my local pc and test all the different scenarios involved in testing an already deployed RESTful web server.
All my expecations are set via ruby client code and so far I could run the basic scenarios and test as well.
I am using a software Paw to check the responses.
Some areas where I found difficult was, actually, the documentations of different techniques seem to be mixed with all the technologies. For example, there is a quote on how to set times unlimited for JAVA but i couldn't find it for RUBY, so i had to go to the code to see the available options and how to set it in ruby.
Then another major problem i faced as a beginner was how to run the mock server example project and test out different scenarios of use cases. To be more clear why I went to the mock server example was to how to understand the proxy mock server setup. Recording and playing back the requests. I dint understand much of the stuff in there.
So i googled a little bit and what i did was complied the mock server example project and started my xampp in my mac and copied the war file to the htdocs folder and tried to run it. But it wasn't working.
Another confusing problem i found was that, I installed the mock server via home-brew in my mac and everytime i run that program i see an entirely different way of starting the mock server.

I couldn't use it as per the documentation at http://www.mock-server.com/mock_server/running_mock_server.html#running_from_command_line_using_homebrew
Sorry if I am asking for something very trivial.
So If i get to make the ruby stuff working on all the scenarios, then I can help you to add some examples on how to run everything with a ruby client.

HI Naveen, Can you share the steps followed to run the mock server example project and test out different scenarios of use cases

closing as duplicate of #115 which is currently in progress


Can I use this with WebView?

My app is Hybrid app with Cordova.
I want to use this library to pin ssl certificate to all requests fired using the WebView.

Closing as duplicate of #13


Do i need cuda support in production

How to deploy in production? My server is aliyun which has not gpu card.

We are sure about how to deploy the models
but as far as development is concerned you wil need cuda based GPU and cannot be done using a CPU
You will need to convert our GPU  based models to CPU using some third party libraries like ONNX
Again i am not sure about that it would work

@DevashishPrasad
Cloud gpu server cost is high so deploying on own computer come with a gpu card is better choice ?

Yes I think so


Openload "None" video source

When extracting openload video the following is the output:
[guest@Laptop101 ~]$ youtube-dl -g "https://openload.co/embed/P7kVkXp2bL8/"
https://openload.co/stream/None?mime=true
I tried different openload sources but same result.

Thanks for the report. This bug will be fixed in the next youtube-dl release.


ClientFactory.Initialize,  how to check if connection is established ?

Hi, how to check if connection with Home Assistance is established correcly? Im asking because after checking with ClientFactory.IsInitialized I see true even if I set wrong ip adress of my Home Assistance.
Another question, Can I use ClientFactory.Initialize with local adress ?
e. g  ClientFactory.Initialize("https://homeassistant.local:8123/", "abcd....

The IsInitialized property only checks if you called Initialize and provided some valid entries (meaning, a valid URL and not null or something like that), it does not reach out to HA to check connectivity.
You can check connectivity by using the RootApiClient or the DiscoveryClient.

The IsInitialized property only checks if you called Initialize and provided some valid entries (meaning, a valid URL and not null or something like that), it does not reach out to HA to check connectivity.
You can check connectivity by using the RootApiClient or the DiscoveryClient.


KivyCatalog: Selectors crash

Open kivycatalog, open Selectors, click on dropdown menu, and click on any of the options - results:
[INFO              ] Kivy v1.9.0-dev
[INFO              ] [Python      ] v2.7.8 (default, Jun 30 2014, 16:03:49) [MSC v.1500 32 bit (Intel)]
[INFO              ] [Factory     ] 173 symbols loaded
[INFO              ] [Image       ] Providers: img_tex, img_dds, img_pygame, img_gif (img_sdl2, img_ffpyplayer, img_pil ignored)
[INFO              ] [Text        ] Provider: pygame
[INFO              ] [Window      ] Provider: pygame(['window_egl_rpi'] ignored)
libpng warning: iCCP: known incorrect sRGB profile
GLEW initialization succeeded
[INFO              ] [GL          ] OpenGL version <3.3.0>
[INFO              ] [GL          ] OpenGL vendor <NVIDIA Corporation>
[INFO              ] [GL          ] OpenGL renderer <GeForce 8600M GT/PCIe/SSE2>
[INFO              ] [GL          ] OpenGL parsed version: 3, 3
[INFO              ] [GL          ] Shading version <3.30 NVIDIA via Cg compiler>
[INFO              ] [GL          ] Texture max size <8192>
[INFO              ] [GL          ] Texture max units <32>
[INFO              ] [Window      ] virtual keyboard not allowed, single mode, not docked
[INFO              ] [Video       ] Provider: null(['video_pygst', 'video_ffmpeg', 'video_ffpyplayer', 'video_pyglet'] ignored)
[INFO              ] [GL          ] NPOT texture support is available
[ERROR             ] [filechooser ] win32file module is missing
[ERROR             ] [filechooser ] we cant check if a file is hidden or not
[INFO              ] [OSC         ] using <thread> for socket
[INFO              ] [Base        ] Start application main loop
libpng warning: iCCP: known incorrect sRGB profile
[INFO              ] [Context     ] Reloading graphics data...
[INFO              ] [Context     ] Reloading done in 0.1630s
[INFO              ] [Base        ] Leaving application in progress...
 Traceback (most recent call last):
   File "G:\Python\dev2\kivy\examples\demo\kivycatalog\main.py", line 166, in <module>
     KivyCatalogApp().run()
   File "g:\python\dev2\kivy\kivy\app.py", line 825, in run
     runTouchApp()
   File "g:\python\dev2\kivy\kivy\base.py", line 484, in runTouchApp
     EventLoop.window.mainloop()
   File "g:\python\dev2\kivy\kivy\core\window\window_pygame.py", line 381, in mainloop
     self._mainloop()
   File "g:\python\dev2\kivy\kivy\core\window\window_pygame.py", line 285, in _mainloop
     EventLoop.idle()
   File "g:\python\dev2\kivy\kivy\base.py", line 327, in idle
     self.dispatch_input()
   File "g:\python\dev2\kivy\kivy\base.py", line 312, in dispatch_input
     post_dispatch_input(*pop(0))
   File "g:\python\dev2\kivy\kivy\base.py", line 278, in post_dispatch_input
     wid.dispatch('on_touch_up', me)
   File "kivy\_event.pyx", line 619, in kivy._event.EventDispatcher.dispatch (kivy\_event.c:6250)
   File "g:\python\dev2\kivy\kivy\uix\behaviors.py", line 140, in on_touch_up
     self.dispatch('on_release')
   File "kivy\_event.pyx", line 615, in kivy._event.EventDispatcher.dispatch (kivy\_event.c:6209)
   File "kivy\_event.pyx", line 1074, in kivy._event.EventObservers.dispatch (kivy\_event.c:11307)
   File "g:\python\dev2\kivy\kivy\uix\spinner.py", line 138, in <lambda>
     item.bind(on_release=lambda option: dp.select(option.text))
   File "g:\python\dev2\kivy\kivy\uix\dropdown.py", line 242, in select
     self.dispatch('on_select', data)
   File "kivy\_event.pyx", line 615, in kivy._event.EventDispatcher.dispatch (kivy\_event.c:6209)
   File "kivy\_event.pyx", line 1074, in kivy._event.EventObservers.dispatch (kivy\_event.c:11307)
   File "g:\python\dev2\kivy\kivy\uix\spinner.py", line 146, in _on_dropdown_select
     self.is_open = False
   File "kivy\properties.pyx", line 377, in kivy.properties.Property.__set__ (kivy\properties.c:4351)
   File "kivy\properties.pyx", line 409, in kivy.properties.Property.set (kivy\properties.c:4866)
   File "kivy\properties.pyx", line 460, in kivy.properties.Property.dispatch (kivy\properties.c:5442)
   File "kivy\_event.pyx", line 1056, in kivy._event.EventObservers.dispatch (kivy\_event.c:11032)
   File "g:\python\dev2\kivy\kivy\uix\spinner.py", line 153, in on_is_open
     self._dropdown.dismiss()
   File "g:\python\dev2\kivy\kivy\uix\dropdown.py", line 233, in dismiss
     self.dispatch('on_dismiss')
   File "kivy\_event.pyx", line 615, in kivy._event.EventDispatcher.dispatch (kivy\_event.c:6209)
   File "kivy\_event.pyx", line 1074, in kivy._event.EventObservers.dispatch (kivy\_event.c:11307)
   File "g:\python\dev2\kivy\kivy\uix\spinner.py", line 142, in _toggle_dropdown
     self.is_open = not self.is_open
   File "kivy\properties.pyx", line 377, in kivy.properties.Property.__set__ (kivy\properties.c:4351)
   File "kivy\properties.pyx", line 409, in kivy.properties.Property.set (kivy\properties.c:4866)
   File "kivy\properties.pyx", line 460, in kivy.properties.Property.dispatch (kivy\properties.c:5442)
   File "kivy\_event.pyx", line 1056, in kivy._event.EventObservers.dispatch (kivy\_event.c:11032)
   File "g:\python\dev2\kivy\kivy\uix\spinner.py", line 150, in on_is_open
     self._dropdown.open(self)
   File "g:\python\dev2\kivy\kivy\uix\dropdown.py", line 215, in open
     'Cannot open a dropdown list on a hidden widget')
 kivy.uix.dropdown.DropDownException: Cannot open a dropdown list on a hidden widget

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

@matham Please test #2813 and see if it fixes this. I could duplicate this bug but not consistently. Kivy Catalog had an issue with reloading the content two seconds after changing screens, and I think this bug may have been triggered by having the right (wrong?) timing and clicking when the content was reloading - therefore the widget had no parent and couldn't get a parent window.

@matham Please test #2813 and see if it fixes this. I could duplicate this bug but not consistently. Kivy Catalog had an issue with reloading the content two seconds after changing screens, and I think this bug may have been triggered by having the right (wrong?) timing and clicking when the content was reloading - therefore the widget had no parent and couldn't get a parent window.


Allow keeping release briefs

Pullrequest to allow keeping brief freetext for each release.

This depends on https://github.com/f3ath/change/pull/15, the pubspec would have to be updated.
At that time I could look into fixing the mergeconflicts as well.


WSUS servers for secondary sites, don't run WSUS cleanup for expired updates.

I believe support was added in 1810 for cleanup on secondary sites

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

ID: 38bacc7a-d602-e825-bff3-5d9232f03f72
Version Independent ID: 7de8c181-3252-de71-bdfe-70b68dd966c5
Content: Software updates maintenance - Configuration Manager
Content Source: sccm/sum/deploy-use/software-updates-maintenance.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Yes looks like this works now for secondary sites as well

Yes, that's correct. Just haven't added to core docs yet.

Closing this issue. @mestew submitted a change to add this info. It will publish live tomorrow (Wednesday, 20 February) around 11am Pacific time.


Disarmed UI inconsistency

Looking at the main alarm screen the screenshot below shows disarmed but the padlock graphic suggests armed as it’s locked. Would this make more sense to show an unlocked padlock to indicate disarmed?

No longer valid.


[BUG] Fix materialized view selection bug

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #6371
Problem Summary(Required) ：

fix materialized view selection bug because the column name comparison is case sensitive.

please add UT

[FE PR Coverage check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/planner/OlapScanNode.java
1
1
100.00%

:large_blue_circle:
com/starrocks/sql/optimizer/rule/mv/MaterializedViewRule.java
1
1
100.00%

@Mergifyio backport branch-2.2


Update git.py community: add relative_path parameter to GitLoader for specific directory loading

Description:
This pull request introduces a new relative_path parameter to the GitLoader class within the LangChain community package. The addition of this parameter enhances the functionality of the GitLoader by allowing it to load documents from specific subdirectories specified by the user, rather than loading all documents from the root of the repository. This feature is particularly useful for applications where only a portion of the repository is relevant to the user's question and answer context, improving both efficiency and relevance of document loading.
Issue:
No applicable issue.
Dependencies:
No new dependencies introduced.
Twitter handle:
Not applicable.

closing as stale / no response


generateDebugSolution folder arrangement

Hi,
I notice there is conf.SolutionFolder to give a solution structure when generating the main projects.
Is there something equivalent for when passing the /GenerateDebugSolution argument and generating that solution?
Thanks

Heya!
No there's nothing of the sort :(

Ok, Thanks for the reply


Documentation outdated for Anchor Creation

Hi
I noticed a mistake in the documentation, with the new version of ASA  (2.11). When creating a cloud spatial anchor cloudNativeAnchor.NativeToCloud() needs to be awaited to create the Spatial Anchor.
If not awaited, this will not work.
Thanks
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 47ed5367-ee97-31a2-78ff-dd98e5c23d24
Version Independent ID: 2e975197-ca07-351a-f538-372500c0cc8f
Content: Create & locate anchors in Unity - Azure Spatial Anchors
Content Source: articles/spatial-anchors/how-tos/create-locate-anchors-unity.md
Service: azure-spatial-anchors
GitHub Login: @msftradford
Microsoft Alias: parkerra

Hello @Silloty1 Thanks for the feedback.
Our SME will review this issue.

Hi @Silloty1, thanks for brining this to our attention! We are working on the fix (#31481757).

The fix has been submitted in #181649 and will go live today


The Rate implementation on the Level Control Move command is not spec complaint.

Reproduction steps
Issue a Level Control Move command with a rate of 254 from 0 to 254. Note that on most non-PC platforms the ramp can not complete in one second like the spec says it has to. When testing on ESP32 best I could get is 10.2 seconds for the ramp to complete. So all rate settings over 10 are out of spec.
Bug prevalence
always
GitHub hash of the SDK that was being used
903e149bd636a5cd1a8821864cb073b4f7a9d3d8
Platform
core
Platform Version(s)
No response
Anything else?
Note: this issue has an easy way for humans to observe the tick performance problem - pressing the button on a dimmer and expecting the lights to ramp in a reasonable amount of time to a human.  With the current code the fastest tick rate I can achieve on an ESP32 is 40ms.  40ms tick time implies you have to hold the button to ramp from 0 to 254 for 10.2 seconds. Most humans will object to this slow ramp speed.
The spec says: rate 100 is 100 units per second, so 2.5 second total ramp time. rate 254 is 254 units per second so 1 second ramp time.  Since the fastest ramp time I can achieve is 10.2s, all ramp rates over 10 are out of spec.
This tick routine is simply doing way, way too much junk on each timer tick. For example a null level change routine just doing a return from my code runs in 20ms minimum on ESP32. The spec says that it has to be 4ms at max rate so even with zero external code the internal CHIP routine can't meet the spec.
The quick fix: The routine is recording the system clock so the routine can check and see if it is falling behind. If it is falling behind don't ramp by a single unit, instead do some division and jump enough units to not fall behind.  The spec just says that at a rate of 100 units in one second, it doesn't say you have to ramp them one unit at a time. At a rate of 255 with my round trip time of 40ms it would increment by 1 the first tick and then see that it is behind 11 increments, so it would jump to 12 on the next tick. not a perfect fix, but it keeps everything within the spec.
Longer term fix -- stop doing so much junk while ramping. Don't do any network activity during the ramp. Wait until the end of the ramp only then update the network and save a new default on value.
Also -- this needs to get tested. Rate parameters like this are in multiple places. Testing needs to ensure that they are spec compliant.

This  problem with flash wear out is also related to this issue.
https://github.com/project-chip/connectedhomeip/pull/23366
currentLevel is specified to always be persistent. However currentLevel gets rapidly changed during Move commands and over fade in/out commands. This can result is committing page many writes to flash very rapidly leading to flash wear out.
A typical goal of persistent currentLevel is is to restore the light when a smart bulb is connected to a dumb light switch. Another strategy could achieve this more efficiently.  Change currentLevel to be non-persistent and then when the fade in/out or Move command is finished, update defaultOnValue to match current level.  This behavior should be optionally enabled, again to avoid needless flash wear.
In general, the Move logic should be reworked to have the minimal possible side effects in order to achieve a maximal ramp rate of 254 (4ms). There should be no need for continuous updates to globally visible attributes during the ramping process.

if you make a clever implementation you are not going to write each increment of LevelControl immediately into flash

@jonsmirl   Why do you conclude "So all rate settings over 10 are out of spec."
From the description it sounds more like "with this particular implementation, rates above XX unit/s cannot be achieved"

if you make a clever implementation you are not going to write each increment of LevelControl immediately into flash

I am aware of how to break the flash commit model and cache the persistent results until a timer tick. However, I don't think it is a wise thing to do.  An an alternative design would recognize that a rapidly changing currentLevel is not something that should be persisted and would consider the strategy of updating the defaultOnLevel attribute at the beginning or end of the command.

@jonsmirl Why do you conclude "So all rate settings over 10 are out of spec." From the description it sounds more like "with this particular implementation, rates above XX unit/s cannot be achieved"

A design consideration would be to consider that the maximal rate the Move command can move at is 254 units per second and then ask, what can consume updates at the rate of 254 units per second? If there is nothing that consume updates at this rate, them why are the updates being done?

if you make a clever implementation you are not going to write each increment of LevelControl immediately into flash

I am aware of how to break the flash commit model and cache the persistent results until a timer tick. However, I don't think it is a wise thing to do. An an alternative design would recognize that a rapidly changing currentLevel is not something that should be persisted and would consider the strategy of updating the defaultOnLevel attribute at the beginning or end of the command.

The spec allows you to make bad products. Clever engineers will make products that comply with the spec and don't wear out the flash.


Remove unnecessary typecasts and add promotion to support Dual numbers

Purpose

This PR is a followup to CliMA/RootSolvers.jl#50, CliMA/Thermodynamics.jl#199, and CliMA/Thermodynamics.jl#200. Together with those changes, this should allow us to pass ForwardDiff.Dual numbers through the ClimaAtmos implicit tendency.
Content

Remove unused FT type variables from method definitions
Drop typecasts to FT where the argument is derived from the parameter set
For typecasts to FT where the argument is a Float64 literal (0.01 or Inf), infer FT from the parameter set instead of the surface conditions (which might contain a mixture of ordinary numbers and Dual numbers)
Add a restriction to the definition of SurfaceFluxesParameters to ensure that the parameter set has an internally consistent FT type
Add a constructor to SurfaceFluxConditions that promotes all of its arguments to a common type (for mixtures of ordinary numbers and Dual numbers, this will promote everything to Duals)
Fix a typo: replace Δz(sc) ./ ζₛ with Δz(sc) / ζₛ (both values are scalars, so we do not need to broadcast here)

Fixes #144

Fix a type instability: replace π_group⁻¹ = 1 / π_group; return π_group⁻¹ * von_karman_const / Σterms with return von_karman_const / (π_group * Σterms) (since π_group is 1, computing π_group⁻¹ results in a Float64 type instability)
Bump the minor version number

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

I fixed an a Float64 type instability, and the tests are now passing. I also reverted the change described in #144, since it was only necessary because of a typo that I removed in this PR. Currently trying out in ClimaAtmos here: https://buildkite.com/clima/climaatmos-ci/builds/16829

The ClimaAtmos examples all ran correctly. There were some minor MSE table changes due to rearranged floating-point operations, but the plots look identical. Merging this in.


chore(deps): add Laravel 10 support

We need to update exolnet/envoy in order to support Laravel 10.x on this package.


Images height not responsive

hi when open with mobile browser images width stretch to device width but the images height same as original size, how to fix this?

thanks

solved


Frozen Integration with ECU-B several times a day

Firmware: ECU_B_1.2.26A
Version apsystems_ecur: latest
Several times a day I get no more values, frozen at the last level. in this case Cache is activated.
I have as an example this morning the ECU rebooted, short improvement, after a restart of HA it goes again for an indefinite time. Online at APSystems the data are without gaps.

I have the same problem. I have to restart the ECU (power cycle) to get it working again.
I thought it might have something to do with the strength of the zigbee signal, but it turns out that is not the case.

From my point of view, the error message can be closed, since the OS 10.1 it runs without a single error, before several times a day.

I am also using OS 10.1, but I still have the problem. So for me, this can't be closed yet.

I can't solve this issue, what firmware versions are you running? HA doesn't need a restart, you should be fine with rebooting the ECU and switching the switch.ecu_query_device back on. Use the switch to be notified when the ECU needs a reboot or reboot the ECU automatically bij using a smart powerplug.

Sorry for the late response. I do not know the firmware version of the ECU at the moment, but I decided to buy a smart plug and automatically reboot the ECU the moment no more data is obtained.
I have the problem every day and to restart the ECU manually is very frustrating.

I checked the firmware. It is ECU_R_1.3.5A

This is typical for my ECU. Any solutions?

Might be a hardware issue, on which hardware are you running Home Assistant? It is known that Intel NUC's might have an issue.

Thanks for your reply. I'm running HA on a Raspberry Pi 4B, 4gb RAM, with a SSD.

Did you have a lot of trouble configuring the ECU or did you add/remove any panels? There might also be a configuration error. I remember that I encountered issues also after adding four panels. Ended up reconfiguring the whole PV and the issue was solved.

No, none of that. But if I read your post correctly, you recommend uninstalling and reinstalling the integration?

No that won't change the situation. I mean resetting the ECU to factory defaults and re-add the panels.

OK I will try that.
For re-adding the panel, can I use the UID's of the inverters in de EMA app and put them in manually after resetting the ECU?

I've been having the issue with my ECU R stopping after a few days. It looks like the automation tries to reboot the ECU, but neither the automation or even the AP Systems app/website seem to be able to connect after that happens. To get it to connect again I need to physically reboot the ECU.
For the time being, I just put in a smart switch that reboots the ECU every morning at 5am to see if that resolves the issue. I also setup an automation to send me a notification if it's using cached data (if it happens during the day despite the daily reboot).
Looks like my firmware is: ECU_R_PRO_2.1.10.

@wemulder I have the same problem as you, I use an automation to detect when cached data has been On for longer than usual, OR if the query device switch has been turned off, and run a script to reset the smart switch the ECU is using. I've been running this combo for several weeks without issue.
Automation:

alias: ECU Reset Watchdog
description: Call ECU Reset after long period ECU Using Cached Data being On
trigger:
  - platform: state
    entity_id:
      - binary_sensor.ecu_using_cached_data
    to: "on"
    for:
      hours: 0
      minutes: 16
      seconds: 0
  - platform: state
    entity_id:
      - switch.ecu_query_device
    to: "off"
    for:
      hours: 0
      minutes: 5
      seconds: 0
condition: []
action:
  - service: script.ecu_reset
    data: {}
mode: single

Script:

alias: ECU Reset
sequence:
  - type: turn_off
    device_id: a3xxxxxxxxxxxx
    entity_id: switch.ecu_breaker
    domain: switch
  - delay:
      hours: 0
      minutes: 0
      seconds: 8
      milliseconds: 0
  - type: turn_on
    device_id: a3xxxxxxxxxxxx
    entity_id: switch.ecu_breaker
    domain: switch
  - delay:
      hours: 0
      minutes: 0
      seconds: 30
      milliseconds: 0
  - type: turn_on
    device_id: 9fxxxxxxxxxxxx
    entity_id: switch.ecu_query_device
    domain: switch
mode: single
icon: mdi:refresh

@cyberbit Thanks for sharing that! If my daily reboot doesn't work I'll need to build something similar.
Will also continue to monitor firmware versions to see if a future update fixes this issue.

I'll close this issue because a workaround is in place. Might any other issue arrise feel free to open a new issue.


PHP Errors and Notices at various sample files

Hello,
I was using PHP codefixer to scan all PHP files on my server. I found a few files which caused PHP notices and PHP errors.
Here you can find all samples and their respective error messages:
https://misc.daniel-marschall.de/bugreports/php_codefixer/
Sample 1:
A file from the nextgen-gallery plugin of Wordpress.
Bug 1.1: Notice: Undefined offset: 0 in phar:///.../phpcf.phar/data/define_case_insensitive.php on line 13
Bug 1.2: Fatal error: Uncaught TypeError: Argument 1 passed to wapmorgan\PhpCodeFixer\PhpCodeFixer::divideByComma() must be of the type array, null given, called in phar:///.../phpcf.phar/data/define_case_insensitive.php on line 13 and defined in phar:///.../phpcf.phar/src/PhpCodeFixer.php:462
Sample 2:
dotclear.php file of an old Wordpress admin area.
Bug 2.1: Notice: Undefined offset: 0 in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 11
Bug 2.2: Fatal error: Uncaught TypeError: Argument 1 passed to wapmorgan\PhpCodeFixer\PhpCodeFixer::divideByComma() must be of the type array, null given, called in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 11 and defined in phar:///.../phpcf.phar/src/PhpCodeFixer.php:462
Sample 3:
A stringparser class, version A
Bug 3.1: Notice: Undefined offset: 0 in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12
Bug 3.2: Fatal error: Uncaught TypeError: Argument 1 passed to wapmorgan\PhpCodeFixer\PhpCodeFixer::trimSpaces() must be of the type array, null given, called in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12 and defined in phar:///.../phpcf.phar/src/PhpCodeFixer.php:477
Sample 4:
A bbcode class, version A
Bug 4.1: Notice: Undefined offset: 0 in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12
Bug 4.2: Fatal error: Uncaught TypeError: Argument 1 passed to wapmorgan\PhpCodeFixer\PhpCodeFixer::trimSpaces() must be of the type array, null given, called in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12 and defined in phar:///.../phpcf.phar/src/PhpCodeFixer.php:477
Sample 5:
A stringparser class, version B
Bug 5.1: Notice: Undefined offset: 0 in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12
Bug 5.2: Fatal error: Uncaught TypeError: Argument 1 passed to wapmorgan\PhpCodeFixer\PhpCodeFixer::trimSpaces() must be of the type array, null given, called in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12 and defined in phar:///.../phpcf.phar/src/PhpCodeFixer.php:477
Sample 6:
A bbcode class, version B
Bug 6.1: Notice: Undefined offset: 0 in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12
Bug 6.2: Fatal error: Uncaught TypeError: Argument 1 passed to wapmorgan\PhpCodeFixer\PhpCodeFixer::trimSpaces() must be of the type array, null given, called in phar:///.../phpcf.phar/data/preg_replace_e_modifier.php on line 12 and defined in phar:///.../phpcf.phar/src/PhpCodeFixer.php:477
Version used: 2.0.17

Check out dev-master version.

How do I build the PHAR file to test it?

Unzip and try this package
phpcf-dev.zip

Thank you very much for sending the new build.  I have run the script against all the files on my server again, and I found another small problem which I didn't find earlier because I grep'ed for "Stack " (which is now all empty). Now I also grep'ed for "on line".
Here is the output:
File /.../owncloud/public_html/lib/composer/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SimpleMailInvoker.php
 5.3 | /daten/homes/owncloud/public_html/lib/composer/swiftmailer/swiftmailer/lib/classes/Swift/Transport/SimpleMailInvoker.php:33      | ini              | Ini safe_mode is deprecated.
Total problems: 1
PHP Notice:  Uninitialized string offset: 1 in phar:///..../phpcf.phar/src/PhpCodeFixer.php on line 362
Here is the source file:
 https://misc.daniel-marschall.de/bugreports/php_codefixer/sample_7.phps

Hm... This problem was fixed too, now the output is
D:\Загрузки>php phpcf-dev.phar sample_7.phps
Max file size set to: 1.000 MiB

File sample_7.phps
 PHP | File:Line                           |             Type | Issue
 5.3 | \sample_7.phps:33                   | ini              | Ini safe_mode is deprecated.

Total problems: 1
Peak memory usage: 2.807 MB

That is extremely weird! I tested it again, with the same phpcf.phar file and with the same source file, and today there is no PHP notice. I have no idea why!
I will run a recheck of all the server files again (will take a few hours) and see if this time everything is good.

I'm sorry, I was providing the wrong sample file.
Here is the correct sample 7 which shows the PHP notice in your current developer build:
https://misc.daniel-marschall.de/bugreports/php_codefixer/sample_7.phps

Fixed phpcf-dev.zip. Check out

Why did you open this ticket again? (did you want to re-open #39?)
PS: I have tested your new developer build, and now all PHP warnings/notices are resolved.

Ok, this one is resolved.


Lighthouse combinations don't test the dataplane

We have an ongoing discussion about testing or not the the connectivity part for the lighthouse
patches.
Currently it's disabled at least until globalnet is stable again, to maintain an indicator of lighthouse health regardless of the globalnet status.
https://github.com/submariner-io/submariner-operator/blob/7e76168c122496b79afd77005bd647b86a005f15/scripts/kind-e2e/e2e.sh#L39

I don't see this change as necessary or productive, since the "bare" lighthouse job is quite stable, and both globalnet (with or without lighthouse) are unstable, we won't gain anything by "masking" the globalnet+lighthouse jobs, we should instead focus on making globalnet (or tests of it) more stable.

Note that it is not that we skip connectivity for lighthouse patches, we have separate jobs that run connectivity tests. Issue we're discussing is if we should skip testing connectivity when we're testing discovery or not. In CI, I think we definitely should coz it is already being tested in other jobs.
Only issue was having an option with make e2e to run both or just connectivity Either can be made default as long as we add an option to run the other.

Note that it is not that we skip connectivity for lighthouse patches, we have separate jobs that run connectivity tests. Issue we're discussing is if we should skip testing connectivity when we're testing discovery or not. In CI, I think we definitely should coz it is already being tested in other jobs.

I disagree with this point, if you have a failure due to connectivity issues but you dont test it (notice shipyard only does a very basic and limited connectivity test), and that issue also causes the lighthouse test to fail, then isolating the failure would be more difficult if you dont run the connectivity tests as well.
I.E. the more data points you have, the easier it'll be to understand what's causing the failure.

Only issue was having an option with make e2e to run both or just connectivity Either can be made default as long as we add an option to run the other.

I disagree with this point, if you have a failure due to connectivity issues but you dont test it (notice shipyard only does a very basic and limited connectivity test), and that issue also causes the lighthouse test to fail, then isolating the failure would be more difficult if you dont run the connectivity tests as well.

Then you should be okay if connectivity failures can't cause Lighhouse to fail? Lighthouse E2E doesn't fail if connectivity fails. Lighthouse can work even if IPSec tunnels are down as long as control plane is up. There are no dataplane connectivity tests. Lighthouse E2E only uses dig. We already removed curl from Lighthouse e2e.

As I mentioned on the slack channel, the operator is deploying an entire system, and it makes sense to test all that it deploys to make sure it all plays well together.
To test just individual components, you have the different e2e tests in each repo.

Yeah, I'm more in the line of ... let's test all we deploy  as a whole. If a test fails we have the logs to know if it's lighthouse or if it's globalnet or connectivity.
Having a decent dashboard and log collection system is what we miss at this point.


Use LibraryImportAttribute instead of DllImportAttribute

Brief Description
When code generation is targeting .NET 7, LibraryImport should be used in place of DllImport as this will pre-generate marshalling operations normally performed at runtime.
When framework target is lower than .NET 7, DllImport should continue to be used.
More information about LibraryImportAttribute can be found here: https://devblogs.microsoft.com/dotnet/announcing-dotnet-7-preview-7/#libraryimport-p-invoke-source-generator
(Non os specific, code generation)
OS: N/A

+1. Having the option to generate LibraryImport would be really useful!


TimedOut Error

Logs:
ERROR teloxide::error_handlers   > An error from the update listener: Network(reqwest::Error { kind: Request, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("api.telegram.org")), port: None, path: "/token:redacted/GetUpdates", query: None, fragment: None }, source: TimedOut })

I contacted the teloxide team, they explained that the error may depend on the poor quality of the Internet. They will not fix it somehow, as a solution I see only changing the logging level for them to "Debug".


[BugFix] DictMappingRewriter support compoundPredicate

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #15243
Problem Summary(Required) ：

For predicate like if(S_ADDRESS > 'a' and S_ADDRESS < 'b', true, false),  the if func is supported to optimize, but its child S_ADDRESS > 'a' and S_ADDRESS < 'b' blocked the rewrite process. The pr enable it.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 2.5
[x] 2.4
[x] 2.3
[ ] 2.2

[FE PR Coverage Check]
:heart_eyes: pass : 8 / 8 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/optimizer/rule/tree/DictMappingRewriter.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/optimizer/rule/tree/AddDecodeNodeForDictStringRule.java
7
7
100.00%
[]

run starrocks_admit_test

@Mergify backport branch-2.3 branch-2.4 branch-2.5


Updated to allow responsive webpage for both UID2 and EUID

Added a ton of CSS and some reorganizing of the handlebars template to allow both EUID and UID2 opt-out portals to be responsive.

https://user-images.githubusercontent.com/35481925/193158889-14da35a5-905c-4a3a-9e0d-d1a02622fb01.mov

Here's a screen recording of the initial page for reference.
https://user-images.githubusercontent.com/35481925/194675130-4c401995-da61-4ad7-8afd-0a207a8793b3.mov

Mostly it looks great - but the privacy page on EUID seems to be broken.
I took a quick look and switching height: 100vh on .main in style.css to min-height: 100vh seems to fix it without breaking other things (looks like the height setting was being used to make the vertical positioning work on smaller pages).

This is resolved now.


Stutter Every 15 seconds

With both this and the stable branch I get some pretty bad performance issues on a small city of 1500.
I did extensive testing by removing all mods that weren't required for load and then added and subtracted mods to find this one being the cause. Here's the notes I took. If there's any outputs you want me to grab let me know.
By performance issues I mean every 15 seconds or so the game stutters. Very noticeable when moving the camera around or watching traffic.
CPU Ryzen 7 5800X
Radeon 5700XT
64gb RAM
By "all mods" I refer to this collection: https://steamcommunity.com/sharedfiles/filedetails/?id=2712368474
Required to load save:
81 tiles
more CitizenUnits
more PathUnits
Harmony 2.0.4-4 (Mod Dependency)
Loading screen mod
1st round: ### FINE ####
FPS Booster
Patch Loader Mod
2nd round	#### FIRST LAG PRESENT ####
TM:PE TEST
Hide Crosswalks V3.0 [EXPERIMENTAL]
Adaptive Networks (AN) V3.2.16 [Stable]
3rd round #### FINE ###
-- TM:PE TEST
-- Hide Crosswalks V3.0 [EXPERIMENTAL]
-- Adaptive Networks (AN) V3.2.16 [Stable]
ALL MODS EXCEPT ABOVE
4th Round #### FINE ####
All mod
++ TMPE TEST
5th Road ## LAG #####
++ Adaptive Networks (AN) V3.2.16 [Stable]
6th round ##### FINE ##
-- Adaptive Networks (AN) V3.2.16 [Stable]
disabled ++ Adaptive Networks (AN) 3.2.18-ALPHA
7th round ##### FINE ######
++ Hide Crosswalks V3.0 [EXPERIMENTAL]
7th round ###### LAG ###
enable ++ Adaptive Networks (AN) 3.2.18-ALPHA
8th round ### FINE ##
-- Adaptive Networks (AN) 3.2.18-ALPHA

I can't reproduce this with minimal mod set and FPS booster

How you disabled mods?

can't reproduce


NIFI-7018: Initial commit of processors extending AbstractHadoopProce…

…ssor supporting kerberos passwords
AbstractHadoopProcessor will always authenticate the principal with a KerberosUser implementation and a UGI will be acquired from the Subject associated with the KerberosUser implementation
AbstractHadoopProcessor's getUserGroupInformation method will now attempt to check the TGT and relogin if a KerberosUser impelmentation is available, otherwise it will return the UGI referenced in the HdfsResource instance
Updated AbstractHadoopProcessor's customValidate method to consider the provided password and updated validation failure explanations when a KerberosCredentialsService is specified together with a principal, password, or keytab
Added toString method override to AbstractKerberosUser
Updated Hive/HBase components to be compatible with the KerberosProperties.validatePrincipalWithKeytabOrPassword method
Fixed null ComponentLog in GetHDFSSequenceFileTest
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

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

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Everything looks good here, going to merge


Doesn't show output properly

Hey there,
vscode
For some reason I have a problem by running couple code written in Python, doesn't show me the output in the terminal
I will send you one of the codes that doesn't run (however I tried same code in another text editor it works fine)
def animal_crack(text):
wordlist=text.lower().split()
first=wordlist[0]
second=wordlist[1]
if first[0] == second[0]:
return True
else: return False
#check
animal_crack('camberjack light')

Your script doesn't have any output. I'm surprised that other editors output something. Can you show other editors to clarify what was expected?

I tried it on Jupyter, and Atom.
Also this is another code, same problem doesn't give any output on VScode


dcterms:spatial breaks the range of that predicate.

I was looking at this project to get inspiration for representing geographical data on objects represented with RDF and noticed that one of your predicates breaks the stated allowed range. This would be the following one:
https://github.com/projecthydra-labs/geo_concerns/blob/db90f53d8a73a77570ed408b91aef320cff84650/app/schemas/basic_geo_metadata_optional.rb#L25
The official declaration (along with the usage guidelines) states that predicate must be a uri rather than the string list you have it setup to be: http://wiki.dublincore.org/index.php/User_Guide/Publishing_Metadata#dcterms:spatial
Does this group consider this an issue at all or is the consensus that that range isn't a problem?
(Additional side inquiry as well: as RDF is unordered, one loses the hierarchy of terms. So the comment of "[ 'France', 'Spain' ]" could be returned as "[ 'Spain', 'France' ]" meaning representing things consistently in a UI might be challenging. Is there some documentation somewhere on what this group might be considering to represent a geographic hierarchy?).

Hi @scande3 ! Hope you are well. Thanks so much for the comments and raising the issue for us.
You raise a valid point about the range of dcterms:coverage. My own understanding of the conundrum of choosing between dc: elements and terms continues to evolve, and so I'm always glad to have a chance to learn from others.
The safer thing to do in this case would be to use dc:coverage from the elements/1.1/ namespace, which does not have domain or range defined for it. So perhaps we should do that for the sake of an easy (and correct) fix. @drh-stanford @eliotjordan @jrgriffiniii ?
At the same time, the user guide doesn't say they must be URIs but that they must be non-literals, and the various examples in the guide (which are really helpful, btw) make liberal use of blank nodes in order to match the defined range for the predicates. Given that the textual description of dcterms:coverage specifically mentions coordinates ("Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates"), which would be hard to mint a URI for, and the example in fact shows them implemented with the help of a blank node, I have to conclude that blank nodes are presumed to be necessary to use many of the terms in the dcterms: namespace that are defined for non-literals (and especially the ones that go beyond the original 11 elements) with correct usage.
But I don't know how widespread absolutely correct usage is in the wild, and I don't know what Curation Concerns and the rest of the Hydra stack does with blank nodes or how they are viewed in terms of development work/PCDM/HydraWorks etc. I would love to find out!
My intuition tells me that in general most (or many) people probably blithely use dcterms: terms for literals, blissfully unaware of their formal properties and strictly correct usage. In fact, one could argue that the ability of people to use dc elements however they liked, with low restrictions is one of the reasons it has been so successful.
And I think it's less a case of 'breaking' the range in the sense of datatype validation (although I could be wrong), as interfering with inferencing that happens at a later point, when the inferencing says that such-and-such literal value must be a member of class X, because of the range of the predicate. If it's the difference between saying that a blank node is a member of class X or a literal is a member of class X, there's less 'value' or 'meaning' being lost there than between a URI and a literal. I don't know what kind of a smashup happens when an inferencing engine expecting a non-literal runs into a literal, but I would hope it wouldn't be catastrophic.
In the past, I have taken the comment at the end of this FAQ page as an indication that DCMI recognizes, perhaps even accepts, that the terms may not be used with strict observance of the semantic specifics (http://wiki.dublincore.org/index.php/FAQ/DC_and_DCTERMS_Namespaces):
"Update, December 2011: It is worth noting that the Schema.org initiative is taking a pragmatic approach towards the formal ranges of their properties [6]:"
'We also expect that often, where we expect a property value of type Person, Place, Organization or some other subClassOf Thing, we will get a text string. In the spirit of "some data is better than none", we will accept this markup and do the best we can.'
"What constitutes "best practice" in this area is bound to evolve with implementation experience over time."
What is 2016 best practice? Is it closer to correct usage now or still somewhere in the middle? Always a good question to ask.
Anyway, thanks again, Steven.

@johnhuck - You are already using Dublin Core Elements coverage to be a dcmi-box or dcmi-point from what I can tell of: https://github.com/projecthydra-labs/geo_concerns/blob/ff39585c833fbf0f09fdfb444888ec4e48f119d8/app/schemas/basic_geo_metadata_required.rb#L17
Using that to also represent a bunch of place labels may make parsing that element more complex for everyone (along with many a form to edit that field more complex). Additionally, that dcmi-box allows for a  "name" in its string encoding that acts as a label already if one has coordinates on the object.
(That works for some of what I plan to do and I'd use it as that code model specifies. My additional use cases is for things that lack coordinates but may still be geographic. Or for things that have a complex geographic hierarchy. Essentially this is just research being done for the MODS and RDF group as we figure out what to map geographic subjects to in the linked data world).
Opinions are currently split over whether it is valid to ignore the range of an element. The MODS and RDF group currently is leaning towards using a different predicate or creating our own rather than invalidate what a predicate specifies. The Geo Concerns group may feel differently as a whole and thought I'd see if that was the case.
I wouldn't recommend using a blank node to solve this issue. They don't work that well - both in terms of how it is stored in Fedora 4 and in trying to parse them when resolving an object.
Thanks!

@scande3 - You know, even though you put dcterms:spatial in the issue name, I read your original comments and had it in my mind that you were commenting on our use of dcterms:coverage, not dcterms:spatial, and I was confused because I thought we had used dc:coverage, but did not take the time to investigate that doubt. If I had, I would have quickly clued in to the fact that I had misread your question entirely from the start. Clearly not enough coffee this morning.
So, in terms of our use of literals with dcterms:spatial, there's obviously no quick fix to contemplate. Most of my comments, I think are still applicable, though.
When we modelled the attributes, our aim was to ensure that objects modelled in geoconcerns could easily be ingested into GeoBlacklight, and therefore that the geoblacklight schema (which can be expressed in JSON, but is natively a set of solr index attributes, drawing on predicates from several namespaces, including dc: and dcterms:.
https://github.com/geoblacklight/geoblacklight-schema/blob/master/docs/geoblacklight-schema.markdown
dcterms:spatial was already in use in the schema, and so we included it as a property for our objects. We included dc:coverage later because we needed a different predicate to encode the bounding box. (We had the darndest time trying to find a simple predicate in an actually published vocabulary (georss:bbox did not meet this bar) for bounding box, before we realized DCMI had a string encoding scheme we could use.) Some GeoBlacklight adopters may be sharing their metadata in some encoding of the geoblacklight schema and using dcterms:spatial with literals, I am guessing.
(cf. https://github.com/OpenGeoMetadata/metadatarepository)
Not strictly correct, I agree, but it's hard to argue with someone who will call it a question of finding the shortest distance between two lines to solve a problem, namely recording a simple attribute/value pair. It's perhaps akin to Jay-walking.
In terms of looking for something else to avoid the range problem, if there are good options to look at, sure, but my sense is that good options are limited at this point, although I'd be glad to be proved wrong. Perhaps creating a new vocabulary of predicate terms is the answer, and having the flexibility to create one and host it in the Hydra neighbourhood is great (I've been following the discussion).
But there is going to be an ongoing need to record string values in metadata all over the place, so I don't see this problem going away any time soon. It's a tension between traditional metadata needs and the constraints of working with RDF vocabularies. Independently of my own thoughts on the matter (which are unresolved), If I were to bet money, I would bet that common usage of dcterms: with literals will be widespread until there is a convenient alternative. But I'm glad to know which way the MODS and RDF group is thinking, since you have thought more about the issue than we have.
I would be very interested in trading thoughts with you about the geographic elements of MODS, as it relates to work I am doing/will soon be doing at my own institution to plan for moving our MODS into RDF. I think you have been working with my colleague Bob Cole in your group, and he is part of our metadata team that is looking at this collectively. I've been tasked with looking at the aspects of MODS that are applicable to our geospatial resources.
When you ask about hierarchical place names, I think you must be thinking of the hierarchical place subjects in MODS, which I am familiar with.
It's an interesting question, because the logic of linked data would say: find a URI for the smallest place and derive relationships with larger territories via inferencing in the URIs home graph (e.g., geonames). i.e., don't try to store the hierarchy in the metadata. But I don't know that systems are yet at the state where that is practical. And that doesn't help with keyword searching or solr indexes. So I'm not sure what the answer is. I mean, if you want strings you can always use LCSH rules on geographic subdivision, but that's moving in the opposite of things like FAST. But if it's URIs, then I'm not sure how to represent hierarchy in place names, unless it's just an unordered list.

The WG discussed this issue at length. After investigating some other predicate options, and considering: the lack of consensus in the community on the importance of using only non-literal values dcterms predicates (most of which suppose non-literal values), as exemplified by current practice for geoblacklight schema and DCAT, to name two examples; the current state of support in Hydra/Fedora for managing URIs and strings; the belief that some data is better than none, in the context of the fact that metadata extracted from ISO, FGDC  or other external metadata files will probably mainly consist of place name strings; the fact that geoconcerns does not prevent users from supplying a URI for the dcterms:spatial predicate; and the general desire to keep the metadata model aligned with the geoBlacklight schema, the WG has decided to continue using dcterms:spatial to record place names, in whatever form the user supplies them, for the time being.

@johnhuck - thanks to the update! Will close this issue then.

We appreciated the chance to consider the question and were glad that you raised it. It's something that I can imagine us returning to at a later date.


Added umbrella header to allow for including the framework in playgrounds

see these links for some details
https://forums.swift.org/t/recent-swiftpm-features-and-enhancements/13807
https://forums.swift.org/t/cant-experiment-swiftnio-in-playground/15020/6

@CalQL8ed-K-OS So, I've finally found time to look at your changes again and integrate them in my branch.
Like I mentioned, we can't re-generate the Xcode Project with SPM, since this would break non-SPM projects. But I've nevertheless managed to get rid of (or actually move) the module.modulemap file.
Could you maybe check if this now works with playgrounds?
I'll close this PR since its main feature should be integrated in the branch now.

@CalQL8ed-K-OS So, I've finally found time to look at your changes again and integrate them in my branch.
Like I mentioned, we can't re-generate the Xcode Project with SPM, since this would break non-SPM projects. But I've nevertheless managed to get rid of (or actually move) the module.modulemap file.
Could you maybe check if this now works with playgrounds?
I'll close this PR since its main feature should be integrated in the branch now.

I've created a new PR, #2, which adds a playground and demonstrates that this branch does indeed work with playgrounds now.
FYI This playground was created using John Sundell's Playground CLI Tool, specifically the command was playground -t Zip.playground -d ./Zip.xcodeproj


Any update on the class indexer bug?

Super annoying and causing lots of confusion with people when they see that I am extending all my classes with Object - any update on fixing this problem?
#4014
Actually it seems that you can't even work around this if you are using interfaces.  Having the class just extend Object seems to have consequences (Flow thinks any object matches such as Map, Set, etc?)

Just an aside, you should comment there and not open a new issue. Same visibility for anyone viewing the issues list ordered by "last updated".

Looks like the extends Object workaround broke in v0.81.0, probably
due to the “Removed the indexer from the Object libdef” change:
https://github.com/facebook/flow/blob/07f29a8efb38a69af95fef9531ff9e6545d4fd65/Changelog.md


🔄 Synced file(s) with WordPress/openverse

Synced local file(s) with WordPress/openverse.

Changed files

Synced local  .github/workflows/new_prs.yml with remote  .github/workflows/new_prs.yml

This PR was created automatically by the repo-file-sync-action workflow run #1243827221

Waiting for merge of WordPress/openverse#69.


Render your 1st scene revisions

Summary
Edits based on style guide
Test Plan

Release Notes

Possible Regressions

Dependencies

This only contains the Render your first scene file.


Does vfmv.v.f and vfmerge.vfm checks for NaN-boxing when FLEN > SEW

In riscv-v spec 11.1:
3. For floating-point operations, the scalar can be taken from a scalar f register. If FLEN>SEW, the value in the f registers is checked for a valid NaN-boxed value
But there is a exception for vfmv.s.f, vfmv.f.s only copies LSBs and upper FLEN-SEW bits are ignored.
according to riscv ISA spec 12.2:
Apart from transfer operations described in the previous paragraph, all other floating-point opera-tions on narrower n-bit operations, n < FLEN, check if the input operands are correctly NaN-boxed.
Does vfmv.v.f and vfmege.vfm classified as transfer operations and not to check for NaN-boxing?

I think there is a similar question #193 before.

Yes, convention is that mv instructions in RISC-V ISA are transfer operations that do not interpret the bits.

Can the spec state this explicitly in the vfmv.v.f and vfmege.vfm instruction section? or in the vector arithmetic instructions format section that talks about NaN boxing for scalar f register? I have to search for this issue (issue #312) to know this.


Following Blog Won't "Stick"

Hey there,
I've been trying different solutions to implement federated blogging for a friend's website on and off for over a year now, and while I'm closer than ever, I'm still having trouble. Using the Activitypub Wordpress plugin, I have the user show up on Mastodon, (@roryprice@roryprice.net), but I haven't gotten a follow request to take. I saw this issue on another thread and it eventually fixed itself, but in that case it took hours for a refresh to show that it hand't worked, but in my case a reload will immediately show that the follow wasn't accepted. This has been the case for weeks. I can see the account had picked up a couple of toots from before, but now it doesn't see any new ones.
Interestingly, the account did reflect a changed profile picture.

I believe this is related to this issue that I reported here on Mastodon: https://merveilles.town/web/statuses/104009265689733976

I have the same issue. I cannot follow my blog's account, it shows that I submitted a follow request and nothing further. I had the same issue on multiple Masto instances and one Pleroma instance.

should be fixed with 0.10.1!

I’m still having this issue.
I attempt to follow ‘<EMAIL_ADDRESS>but on refresh it becomes a follow request.
Could it be the dash in the URL?

@mediaformat have you updated tongue latest version? On which platform have you tested it (mastodon, pletome, ...)?

So. I’ve tested with 2 WP instances. And strangely, it’s only fixed on one of them. Weirdly, both WP setup are pretty similar. Both hosted on shared hosting at OVH.

<EMAIL_ADDRESS>Runs on WP 5.4.1 with WP-AP 0.10.1
When trying to follow from Mastodon, it shows "cancel follow request" after a refresh. And the follow request is never accepted.
There is no "followers" listed on the WP admin page Followers (Fediverse)

<EMAIL_ADDRESS>Runs on WP 5.4.1 with WP-AP 0.10.1
Follow request work as expected.
There are followers listed on the WP admin page Followers (Fediverse)

Not sure what I can do to debug this further. I’ve checked the Apache log but can’t seem to find anything.

@mediaformat have you updated to the latest version? On which platform have you tested it (mastodon, pletome, ...)?

WP 5.4.1
wordpress-activitypub 0.10.1
tested on mastodon.social

Following up from wordpress.org/support/topic/secure-mode-compatibility/
I've tested on a shared hosting setup, and finding a similar issue<EMAIL_ADDRESS>

When I send a follow request I get the following PHP Warning:
PHP Warning:  Undefined variable $user_id in wp-content/plugins/activitypub/includes/rest/class-inbox.php on line 111
My follow request doesn't "stick" as well.
Wordpress 5.8 on php 8.0

Hi, I'm seeing the same issue trying to follow my WP site from Fosstodon.
The address I'm trying to follow is<EMAIL_ADDRESS>I'm on Fosstodon which as of this comment is running Mastodon v4.0.2
One interesting finding:
I turned on debugging on my WP site and tried to follow. It looks as if the "acceptance" message from WP has some issue as I get what I'm pretty sure is the response from Fosstodon with this message:
HTTP/1.1 401 Unauthorized
Date: Wed, 30 Nov 2022 05:36:22 GMT
Content-Type: text/plain; charset=utf-8
Transfer-Encoding: chunked
Connection: close
Server: Mastodon
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 0
Permissions-Policy: interest-cohort=()
Vary: Accept
Cache-Control: no-cache
Content-Security-Policy: base-uri 'none'; default-src 'none'; frame-ancestors 'none'; font-src 'self' https://fosstodon.org; img-src '...
X-Request-Id: 93672c69-5b12-420b-8dbd-8f59a5cca188
X-Runtime: 0.407184
Strict-Transport-Security: max-age=63072000; includeSubDomains

Perhaps related, I also see in the log these messages:
REST request: /activitypub/1.0/blog/followers: [](Header Absent)
REST result: : {"code":"rest_no_route","message":"No route was found matching the URL and request method.","data":{"status":404}}(404) - [](User ID: 0)


Improve perf of token cleanup

resolves #89
Use entity framework extended to run the token clean up process.  This
pevent the cleanup code pulling the data back before deleting it.
Add an index to the expiry field to improve performance of selection.
This current solution does not include @tbarcelon proposed plan to move the clustered index to expiry.  It just adds an extra non clustered index.
Note: I've included a test that I would remove before merging this code it just so you can run it quickly run it to check it works.
I've profiled the sql that gets executed by entityframework extended.
DELETE [dbo].[Tokens]
FROM [dbo].[Tokens] AS j0 INNER JOIN (
SELECT
    1 AS [C1],
    [Extent1].[Key] AS [Key],
    [Extent1].[TokenType] AS [TokenType]
    FROM [dbo].[Tokens] AS [Extent1]
    WHERE [Extent1].[Expiry] < '2016-05-13 14:19:03.6501655 +00:00'
) AS j1 ON (j0.[Key] = j1.[Key] AND j0.[TokenType] = j1.[TokenType])

Included execution plan

Less than ideal compared to the alternative but probably good enough.
DELETE FROM [dbo].[Tokens] WHERE [Expiry] < '2016-05-13 14:19:03.6501655 +00:00'

Hi @feanz, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@feanz, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

Just got around to this now -- I like the idea and sorry for the delay.