HLS can't play live stream

I am trying to setup HLS to stream my webcam. This is my nginx.conf:
user root;
worker_processes 1;

 events {
   worker_connections 1024;
 }

 http {
      include /etc/nginx/mime.types;
      default_type application/octet-stream;
      sendfile on;
      keepalive_timeout 65;
      #if you want gzip enabled
      #gzip on;
      #gzip_disable "msie6";

 server {
     listen    80;
     server_name localhost;

     location /stat {
       rtmp_stat all;
       rtmp_stat_stylesheet stat.xsl;
     }

     location /stat.xsl {
       # you can move stat.xsl to a different location
       root /usr/src/nginx-rtmp-module;
     }

     # rtmp control
     location /control {
       rtmp_control all;
     }

     location /hls {
       types {
         application/vnd.apple.mpegurl m3u8;
         video/mp2t ts;
       }
       root /tmp;
       add_header Cache-Control no-cache;
     }

     error_page  500 502 503 504 /50x.html;
     location = /50x.html {
       root  html;
     }
   }
 }
 rtmp {
   server {
     listen 1935;
     chunk_size 4000;
     ping 30s;
     notify_method get;

     application hls {
       live on;
       hls on;
       hls_path /tmp/hls;
     }
     application live {
       live on;
     }
   }
 }

I publish with ffmpeg like this:
ffmpeg -loglevel verbose -re -i rtsp://<IP_ADDRESS>/profile4/media.smp -vcodec libx264 -vprofile baseline -acodec libmp3lame -ar 44100 -ac 1 -f flv rtmp://<IP_ADDRESS>:1935/hls/stream1
I can open this file in the browser: http://<IP_ADDRESS>/hls/stream1.m3u8
it will give me
#EXTM3U
#EXT-X-VERSION:3
#EXT-X-MEDIA-SEQUENCE:0
#EXT-X-TARGETDURATION:31
#EXT-X-DISCONTINUITY
#EXTINF:31.467,
http://<IP_ADDRESS>/hls/stream1-0.ts

When I open the stream in VLC:
Your input can't be opened:
VLC is unable to open the MRL 'http://<IP_ADDRESS>/hls/stream1.m3u8'. Check the log for details.
VLC can't recognize the input's format:
The format of 'http://<IP_ADDRESS>/hls/stream1.m3u8' cannot be detected. Have a look at the log for details.

Log:

core debug: adding item `http://<IP_ADDRESS>/hls/stream1.m3u8' ( http://<IP_ADDRESS>/hls/stream1.m3u8 )
core debug: processing request item: http://<IP_ADDRESS>/hls/stream1.m3u8, node: null, skip: 0
core debug: rebuilding array of current - root Playlist
core debug: rebuild done - 2 items, index 1
core debug: starting playback of the new playlist item
core debug: resyncing on http://<IP_ADDRESS>/hls/stream1.m3u8
core debug: http://<IP_ADDRESS>/hls/stream1.m3u8 is at 1
core debug: creating new input thread
core debug: Creating an input for 'http://<IP_ADDRESS>/hls/stream1.m3u8'
core debug: requesting art for http://<IP_ADDRESS>/hls/stream1.m3u8
core debug: using timeshift granularity of 50 MiB, in path 'C:\Users\Rogier\AppData\Local\Temp'
core debug: `http://<IP_ADDRESS>/hls/stream1.m3u8' gives access `http' demux `' path `<IP_ADDRESS>/hls/stream1.m3u8'
core debug: specified demux `any'
core debug: creating demux: access='http' demux='any' location='<IP_ADDRESS>/hls/stream1.m3u8' file='\\<IP_ADDRESS>\hls\stream1.m3u8'
core debug: meta ok for (null), need to fetch art
core debug: looking for access_demux module matching "http": 12 candidates
core debug: no access_demux modules matched
core debug: creating access 'http' location='<IP_ADDRESS>/hls/stream1.m3u8', path='\\<IP_ADDRESS>\hls\stream1.m3u8'
core debug: looking for access module matching "http": 21 candidates
http debug: querying proxy for http://<IP_ADDRESS>/hls/stream1.m3u8
http debug: no proxy
http debug: http: server='<IP_ADDRESS>' port=80 file='/hls/stream1.m3u8'
core debug: looking for meta fetcher module matching "any": 1 candidates
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\fetcher
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher
core debug: net: connecting to <IP_ADDRESS> port 80
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher\tvrage.luac
core debug: connection succeeded (socket = 1816)
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher\tvrage.luac
core debug: no meta fetcher modules matched
core debug: searching art for http://<IP_ADDRESS>/hls/stream1.m3u8
core debug: looking for art finder module matching "any": 2 candidates
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\art
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\00_musicbrainz.luac
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\00_musicbrainz.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\01_googleimage.luac
core debug: looking for meta fetcher module matching "any": 1 candidates
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\fetcher
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher
http debug: protocol 'HTTP' answer code 206
http debug: Server: nginx/1.9.3
http debug: Content-Type: application/vnd.apple.mpegurl
http debug: this frame size=275
http debug: Connection: close
http debug: stream size=275,pos=0,remaining=275
core debug: using access module "http"
core debug: Using stream method for AStream*
core debug: starting pre-buffering
core debug: received first data after 0 ms
core debug: pre-buffering done 275 bytes in 0s - 268554 KiB/s
core debug: looking for stream_filter module matching "any": 6 candidates
httplive info: HTTP Live Streaming (<IP_ADDRESS>/hls/stream1.m3u8)
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher\tvrage.luac
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\01_googleimage.luac
httplive debug: parse_M3U8 #EXTM3U #EXT-X-VERSION:3 #EXT-X-MEDIA-SEQUENCE:0 #EXT-X-TARGETDURATION:34 #EXT-X-DISCONTINUITY #EXTINF:33.967, http://<IP_ADDRESS>/hls/stream1-0.ts #EXTINF:10.689, http://<IP_ADDRESS>/hls/stream1-1.ts #EXT-X-DISCONTINUITY #EXTINF:33.812, http://<IP_ADDRESS>/hls/stream1-2.ts
httplive debug: Live Playlist HLS protocol version: 3
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\02_frenchtv.luac
httplive debug: #EXT-X-DISCONTINUITY #EXT-X-DISCONTINUITY
httplive debug: #EXT-X-DISCONTINUITY #EXT-X-DISCONTINUITY
httplive debug: Choose segment 0/3 (sequence=0)
core debug: using stream_filter module "httplive"
core debug: Inserted a stream filter
core debug: looking for stream_filter module matching "any": 6 candidates
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
core debug: creating access 'http' location='<IP_ADDRESS>/hls/stream1-0.ts', path='\\<IP_ADDRESS>\hls\stream1-0.ts'
core debug: looking for access module matching "http": 21 candidates
http debug: querying proxy for http://<IP_ADDRESS>/hls/stream1-0.ts
http debug: no proxy
http debug: http: server='<IP_ADDRESS>' port=80 file='/hls/stream1-0.ts'
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\02_frenchtv.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\03_lastfm.luac
core debug: net: connecting to <IP_ADDRESS> port 80
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\03_lastfm.luac
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher\tvrage.luac
core debug: no art finder modules matched
core debug: looking for meta fetcher module matching "any": 1 candidates
core debug: no meta fetcher modules matched
core debug: searching art for http://<IP_ADDRESS>/hls/stream1.m3u8
core debug: looking for art finder module matching "any": 2 candidates
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\fetcher
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\art
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher\tvrage.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\00_musicbrainz.luac
core debug: using meta fetcher module "lua"
core debug: removing module "lua"
core debug: searching art for http://<IP_ADDRESS>/hls/stream1.m3u8
core debug: looking for art finder module matching "any": 2 candidates
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\00_musicbrainz.luac
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\art
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\01_googleimage.luac
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\00_musicbrainz.luac
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\01_googleimage.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\02_frenchtv.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\01_googleimage.luac
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\02_frenchtv.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\03_lastfm.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\02_frenchtv.luac
lua debug: skipping script (unmatched scope) C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\03_lastfm.luac
core debug: no art finder modules matched
core debug: looking for meta fetcher module matching "any": 1 candidates
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\03_lastfm.luac
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\fetcher
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\fetcher\tvrage.luac
core debug: connection succeeded (socket = 1868)
core debug: using meta fetcher module "lua"
core debug: removing module "lua"
core debug: searching art for http://<IP_ADDRESS>/hls/stream1.m3u8
core debug: looking for art finder module matching "any": 2 candidates
core debug: no art finder modules matched
core debug: art not found for http://<IP_ADDRESS>/hls/stream1.m3u8
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\meta\art
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\00_musicbrainz.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\01_googleimage.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\02_frenchtv.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\meta\art\03_lastfm.luac
core debug: no art finder modules matched
core debug: art not found for http://<IP_ADDRESS>/hls/stream1.m3u8
http debug: protocol 'HTTP' answer code 404
http error: error: HTTP/1.1 404 Not Found
http debug: switching to HTTP version 1.0
core debug: net: connecting to <IP_ADDRESS> port 80
core debug: connection succeeded (socket = 1868)
http debug: protocol 'HTTP' answer code 404
http error: error: HTTP/1.1 404 Not Found
core debug: net: connecting to <IP_ADDRESS> port 80
core debug: connection succeeded (socket = 1868)
qt4 debug: IM: Setting an input
access_mms error: error: HTTP/1.1 404 Not Found
core debug: no access modules matched
core error: no suitable access module for `http://<IP_ADDRESS>/hls/stream1-0.ts'
httplive error: downloading segment 0 from stream 0 failed
core debug: creating access 'http' location='<IP_ADDRESS>/hls/stream1-1.ts', path='\\<IP_ADDRESS>\hls\stream1-1.ts'
httplive error: segment 0 should have been available (stream 0)
core debug: looking for access module matching "http": 21 candidates
http debug: querying proxy for http://<IP_ADDRESS>/hls/stream1-1.ts
httplive error: segment 0 should have been available (stream 0)
http debug: no proxy
http debug: http: server='<IP_ADDRESS>' port=80 file='/hls/stream1-1.ts'
httplive error: segment 0 should have been available (stream 0)
core debug: no stream_filter modules matched
core debug: looking for stream_filter module matching "record": 6 candidates
core debug: using stream_filter module "record"
core debug: creating demux: access='http' demux='any' location='<IP_ADDRESS>/hls/stream1.m3u8.ts' file='\\<IP_ADDRESS>\hls\stream1.m3u8.ts'
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
core debug: looking for demux module matching "any": 66 candidates
core debug: net: connecting to <IP_ADDRESS> port 80
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
core debug: connection succeeded (socket = 1880)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
es error: cannot peek
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
es error: cannot peek
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
es error: cannot peek
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
es error: cannot peek
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
es error: cannot peek
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
http debug: protocol 'HTTP' answer code 206
http debug: Server: nginx/1.9.3
http debug: Content-Type: video/mp2t
httplive error: segment 0 should have been available (stream 0)
http debug: this frame size=1156388
http debug: Connection: close
http debug: stream size=1156388,pos=0,remaining=1156388
core debug: using access module "http"
core debug: Using stream method for AStream*
core debug: starting pre-buffering
httplive error: segment 0 should have been available (stream 0)
core debug: received first data after 0 ms
core debug: pre-buffering done 1024 bytes in 0s - 1000000 KiB/s
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
asx debug: not enough data
httplive error: segment 0 should have been available (stream 0)
pls debug: not enough data
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
mod debug: MOD validation failed (ext=ts)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
ps error: cannot peek
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
httplive error: segment 0 should have been available (stream 0)
mjpeg warning: no more data
mjpeg error: cannot peek
httplive error: segment 0 should have been available (stream 0)
mpgv error: cannot peek
httplive error: segment 0 should have been available (stream 0)
avcodec debug: trying url: \\<IP_ADDRESS>\hls\stream1.m3u8.ts
httplive error: segment 0 should have been available (stream 0)
avcodec warning: cannot peek
lua debug: Trying Lua scripts in C:\Users\Rogier\AppData\Roaming\vlc\lua\playlist
lua debug: Trying Lua scripts in C:\Program Files (x86)\VideoLAN\VLC\lua\playlist
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\anevia_streams.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\anevia_xml.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\appletrailers.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\bbc_co_uk.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\break.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\canalplus.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\cue.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\dailymotion.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\extreme.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\france2.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\googlevideo.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\jamendo.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\joox.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\katsomo.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\koreus.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\lelombrik.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\liveleak.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\metacafe.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\metachannels.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\mpora.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\pinkbike.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\pluzz.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\rockbox_fm_presets.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\soundcloud.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\vimeo.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\youtube.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\youtube_homepage.luac
lua debug: Trying Lua playlist script C:\Program Files (x86)\VideoLAN\VLC\lua\playlist\zapiks.luac
httplive error: segment 0 should have been available (stream 0)
ps error: cannot peek
httplive error: segment 0 should have been available (stream 0)
vobsub debug: could not read vobsub IDX file
httplive error: segment 0 should have been available (stream 0)
core debug: no demux modules matched
core error: no suitable demux module for `http/any://<IP_ADDRESS>/hls/stream1.m3u8'
core debug: removing module "record"
core debug: removing module "httplive"
core debug: removing module "http"
httplive debug: downloaded segment 1 from stream 0
core debug: creating access 'http' location='<IP_ADDRESS>/hls/stream1-0.ts', path='\\<IP_ADDRESS>\hls\stream1-0.ts'
core debug: looking for access module matching "http": 21 candidates
http debug: querying proxy for http://<IP_ADDRESS>/hls/stream1-0.ts
http debug: no proxy
http debug: http: server='<IP_ADDRESS>' port=80 file='/hls/stream1-0.ts'
core debug: net: connecting to <IP_ADDRESS> port 80
core debug: connection succeeded (socket = 1888)
http debug: protocol 'HTTP' answer code 404
http error: error: HTTP/1.1 404 Not Found
http debug: switching to HTTP version 1.0
core debug: net: connecting to <IP_ADDRESS> port 80
core debug: connection succeeded (socket = 1888)
http debug: protocol 'HTTP' answer code 404
http error: error: HTTP/1.1 404 Not Found
core debug: net: connecting to <IP_ADDRESS> port 80
core debug: connection succeeded (socket = 1888)
access_mms error: error: HTTP/1.1 404 Not Found
core debug: no access modules matched
core error: no suitable access module for `http://<IP_ADDRESS>/hls/stream1-0.ts'
httplive error: downloading segment 0 from stream 0 failed
core debug: creating access 'http' location='<IP_ADDRESS>/hls/stream1-2.ts', path='\\<IP_ADDRESS>\hls\stream1-2.ts'
core debug: looking for access module matching "http": 21 candidates
http debug: querying proxy for http://<IP_ADDRESS>/hls/stream1-2.ts
http debug: no proxy
http debug: http: server='<IP_ADDRESS>' port=80 file='/hls/stream1-2.ts'
core debug: net: connecting to <IP_ADDRESS> port 80
core debug: connection succeeded (socket = 1916)
http debug: protocol 'HTTP' answer code 206
http debug: Server: nginx/1.9.3
http debug: Content-Type: video/mp2t
http debug: this frame size=3503004
http debug: Connection: close
http debug: stream size=3503004,pos=0,remaining=3503004
core debug: using access module "http"
core debug: Using stream method for AStream*
core debug: starting pre-buffering
core debug: received first data after 0 ms
core debug: pre-buffering done 1024 bytes in 0s - 1000000 KiB/s
core debug: removing module "http"
httplive debug: downloaded segment 2 from stream 0

I can't really figure out what's going on here, is bit encoding?

The deal seems in hostname for HTTP. http://<IP_ADDRESS>/ is not accessable by localhost probably.
Change server_name in http server section to:
 server {
     listen    80;
     server_name localhost _ <IP_ADDRESS>;

The rtmp link is working fine but the hls part isn't working with both localhost and ip. so what should i do?

这是权限问题
chmod -R www:www 相应的文件目录


Add linting and code coverage.

[x] Add Linting

[x] Add Unit Tests(Server)

[ ] Add Unit Tests(Client)

[ ] Code Coverage(Reports)

[ ] Update Travis

We should consider using https://github.com/prettier/prettier for code formatting. It's already widely adopted in the JS community and solves all code formatting headaches in pull requests.

#212 For unit tests of client.

#213 for TravisCI and coverage.


Add Sensors Values DB

These are written by snapshotter service and read by API
Todo:

[x] DB

[x] Model
[x] Migration

Implemented.
Staging testing needed.


Fix bad reference in hk_init's exit bind.

Thanks for picking up on that, I moved hk_init towards the end of creating this, so it was a pain to find all the references I had to change. Cheers


MAINT: deal with cases in minimize for `(bounds.lb == bounds.ub).any() (third alternate for #12889)

@mdhaber, how about this factoring out?

Before I look in detail, what is better than gh-13096? Could gh-13096 be improved?

@mdhaber, this approach:

puts the factorisation down into the various _minimize_*, which means that minimize and fmin_* should work without alteration.
#13096 would have had difficulties with the constraints functions for SLSQP, because they all need to be wrapped as well, and it'd be a pain to do that in minimize.
eps and finite_diff_rel_step can also be arrays, which also need to be reduced.

I think the only issue as it stands is how to re-expand the LbfgsInvHessProduct, I don't know how to do that.

Decided to take out the changes to _numdiff and _differentiable_functions because they muddy the water a little and aren't critical to this PR.

@nmayorov, @larsoner, this is an alternate way to fix the equal bounds bug. This alternate version factors out the parameters which have lb==ub. It only does this for SLSQP and LBFGSB, as they are the only two that display problems in the test suite.

When I get to the OptimizeResult construction x, and jac need to be expanded. It's relatively easy to do, but should I use np.nan, or 0, for those entries in jac that have equal lower and upper bounds?

Rebased and squashed commits.
@rgommers, it would be good if a solution to the original issue is in the next release (there have been several issues raised over this). I've made different approaches to a solution and @mdhaber did as well (#13096). From my point of view I think this PR is a better solution to the issue than Matt's, for the reasons outlined above.

After reviewing, some thoughts in response to these. (They're not meant to be defensive about gh-13096, because that was really was just supposed to explore the issue. I really just want the least painful resolution, wherever that comes from.)

puts the factorisation down into the various minimize, which means that minimize and fmin_ should work without alteration.

This is actually a superficial difference.  In gh-13096, there is a big block of code added at the beginning of minimize and a small block at the end of minimize that do all the heavy lifting. There are basically no changes or deletions. Each block could be put in a function, and these functions could instead be called at the beginning/end of e.g. lbfgsb and slsqp. I chose to ignore the legacy functions, but if we care about them, I think it would be simple to do this.

#13096 would have had difficulties with the constraints functions for SLSQP, because they all need to be wrapped as well, and it'd be a pain to do that in minimize (there is a whole set of checking that needs to be done first, etc).

I'm not sure I understand. I had already dealt with constraint functions for SLSQP and their jacobian functions. This PR doesn't yet address jacobians for vector-valued constraints.

eps and finite_diff_rel_step can also be arrays, which also need to be reduced.
Yup, I forgot about that.  I also hadn't done the modifications to LbfgsInvHessProduct yet; that's another advantage here.

I think we should go back and forth between the PRs, as there are advantages and disadvantages in each, and hopefully we will converge to something we can agree on. Does that sound good? So I'd propose that the next step would be for me to make some changes in gh-13096 to incorporate the advantages here. I think it's worth doing that because one advantage of gh-13096 is that it is non-invasive - it involves some additions, but they are very localized and there are basically no changes or deletions. What do you think?

I'm not sure I understand. I had already dealt with constraint functions for SLSQP and their jacobian functions. This PR doesn't yet address jacobians for vector-valued constraints.

Perhaps a first step would be adding the modifications I've done to test_slsqp.py to check that #13096 works with constraints (scalar and vector valued).

eps and finite_diff_rel_step can also be arrays, which also need to be reduced

The last commit added a test for that. The test fails if the finite_diff_rel_step array isn't filtered.

I'm going to bump the milestone on this matter--there seems to be some pretty detailed discussion above. If this really is needed for 1.6.x series I suppose you might still have a little time or you could put in during the rc phase, but I can't really tell what the timeline for merging is and I'm going to try to keep moving forward with release process.

I don't see any activity since I bumped the milestone  on the previous release branching. Furthermore, there still seem to be "competing PRs" without much clarity as to which one is to be preferred.

I think the underlying issue is one of the biggest pain points for optimize. I think both @mdhaber and my PR are ok, but not optimal.

Oh dear, I'll bump milestone--maybe when Matt switches back to optimize from stats focus for a bit the decision on this one might move forward a bit.


FileTarget - Rename to tmp file before starting actual compression

The rename will notify others that archive has begun when ConcurrentWrites=true. Fixes #1314

This change is

Current coverage is 81% (diff: 60%)

Merging #1880 into master will increase coverage by <1%

@@             master      #1880   diff @@
==========================================
  Files           276        276
  Lines         18634      18619    -15
  Methods        2861       2860     -1
  Messages          0          0
  Branches       2139       2136     -3
==========================================
- Hits          15138      15136     -2
- Misses         2977       2979     +2
+ Partials        519        504    -15

Powered by Codecov. Last update 2216fff...b037507

After "discovering" the issue copy the uncompressed file to a remote network drive, then I think that I will close this PR.
I guess the proper solution would be:

Rename current-filename-ext to current-filename-archive-filename-ext (Within the current folder)
Perform archive operation on the current-filename-archive-filename-ext
Add support for recognizing old current-filename-archive-filename-ext, and retry archive operation
Change the archive-mutex so it becomes try-aquire and repeatedly check if the current-filename-ext already has been renamed by another FileTarget.

I will close this issue.

After "discovering" the issue with copy the uncompressed file to a remote network drive, then I think that I will close this PR.

good one.

I guess the proper solution would be:
Rename current-filename-ext to current-filename-archive-filename-ext (Within the current folder)
Perform archive operation on the current-filename-archive-filename-ext
Add support for recognizing old current-filename-archive-filename-ext, and retry archive operation
Change the archive-mutex so it becomes try-aquire and repeatedly check if the current-filename-ext already has been renamed by another FileTarget.

So renaming for removing the file lock? Or checking if it's locked?


3D armour bits don't go away when undressing character after changing race

I don't know how else to describe it, so here is a screenshot to demonstrate what I'm talking about.
To reproduce:

Be wearing an item whose appearance has 3D bits (e.g. the sleeves on this chestpiece)
Open dressup
Choose a race to preview (can be you own)
Undress all

This is known error and limitation due to limited control of dress up model frames. To fix this Blizzard needs to do it, unfortunately there's no way I can help it.

Aaah, gotcha! Fingers crossed they get around to addressing it then. Thanks for clearing this up.


IPV6 not working

When i run porkbun-ddns -v porkbun.json example.com I get message saying No IPv6 connectivity!  I have an IPV6 address and can ping -6 google.com and get a reply.
Just tested this works in version 0.2 but fails in 0.3 and 0.4.

Please run: porkbun-ddns -v porkbun.json example.com and post your logs

I have the same issue, also I can't get the docker image to produce any other logs than No IPv6 connectivity! even with DEBUG: "TRUE" set in the environment section of the compose file

I'll take a look at it this weekend

I deleted the check since I couldn't find a pure python and also reliable way to check ipv6

I just released v0.4.1, please reopen if you still got problems.


How to know if a service method is idempotent

Is your feature request related to a problem? Please describe.
I'm using a connect interceptor to wrap every request with a db transaction, but I would like to start a transaction only when needed, of course I don't need a transaction for a NO_SIDE_EFFECTS idempotency level
Describe the solution you'd like
Being able to get the idempotency level of the method being called within an interceptor

Hey Juan, this sounds like a great idea. You can get the idempotency level via connect.Spec. It's available with a getter on connect.AnyRequest. Let us know if that works for you 🙂

Thanks! @timostamm
Here is the code snippet if someone ever needs it
if request.Spec().IdempotencyLevel == connect.IdempotencyNoSideEffects {
	return next(ctx, request)
}


Max Hit plugin update (attempt 2)

Still not sure if I'm doing this right, hopefully this registers as an update?

edit the file that currently exists, dont make a new one


Can the color of texts in square blocks be the accent color?

Thanks for the quick fix, which solves the issue that links were grey.
But what I really appreciated in the previous version (4.2) was that texts in square blocks (e.g., [content]) were the accent color. But now it is grey. Could it be like before?

The accent color version in 4.2 was unintentional, 4.3.3 restores the gray color that was used in prior versions.
If you want to use accent color, you can add a snippet such as:
.cm-s-obsidian.is-live-preview .cm-formatting-link + span.cm-link {
color:var(--text-accent);
}


fix peppy breaking lbs

gotta love peppy for that

oh yea i forgor :skull:

done

thanks!

The (0) was just a placeholder that now got replaced with (Monstercat Release), you need to change your code accordingly,


Custom item naming and path generation

Is your feature request related to a problem?
Nope
Describe the solution you'd like
It would be great to be able to control the formatting of the path and the resulting file name
The baseId is a kebab cased operationId - https://github.com/PaloAltoNetworks/docusaurus-openapi-docs/blob/main/packages/docusaurus-plugin-openapi-docs/src/openapi/openapi.ts#L144-L146
And the resulting path is hardcoded using the id https://github.com/PaloAltoNetworks/docusaurus-openapi-docs/blob/main/packages/docusaurus-plugin-openapi-docs/src/index.ts#L357
Perhaps adding an item ID transformer and path generator to the plugin options would be possible,
{
  itemIdTransformer(item: ApiMetadata): string { }
  itemPathTransformer(item: ApiMetaData): string {}
}

Describe alternatives you've considered

Use a patch-package patch
Create redirects :(

Additional context

I am migrating a documentation site to docusaurus, the content has hardcoded links to an API schema in the markdown files which uses the operationId as the file name and route.
Being able to control the name of the item and the path it is written to would mean we don't have to construct redirects or change our content

Hi @omonk, thanks for reporting this issue. Considering that the operationId, if properly defined, should not contain any spaces or line breaks, we could potentially just forgo the kebab case transform altogether.
For example...
operationId: addPet

...Would result in...
filename: `addPet.api.mdx`
id: addPet

Alternatively, we could keep only the filename kebab case and leave the operationId as-is for the id frontmatter.


Main 2.3 doesnt bootstrap for 2 days

Updated from 2.1 to 2.3:

pulled new image
updated ENV with minimal_fee

Two days ago docker was unresponsive and restarted docker. Since then its stuck at bootstrapping:

Is there a way to get more bootstrap addresses?

Hello!
Hard to say why your node fails to bootstrap. maybe there is an error, but the logs you provided are not enough to say.
I suggest you to check that the running version of your node in the log, you should have:
INFO massa_node: Node version : MAIN.2.3
Then inspect logs to see if there is any errors.
Run sudo docker ps -a to check the running time of your node. maybe its restarting unexpectingly?
If you waited 2 days without succeed to bootstrap, its probably mean that something is wrong with your config.
That said, you can still add bootstrap nodes in node_config_MAIN.2.3.toml in bootstrap_list section.
You can add my node to bootstrap:
<IP_ADDRESS>:31245 N1aWD9vpV8LT2BptZXJbX7EncC6GxNDFfEw9nPbsTV4CLBGesHt
You can also ask for more bootstrap nodes on discord
Once you edited the file, restart your node
sudo docker compose down && sudo docker compose pull && sudo docker compose up -d

Thank you for the fast reply.
The container starts without errors:

Massa-Guard INFO [20240807-13H26] Load config.toml

Massa-Guard INFO [20240807-13H26] Load node_config_MAIN.2.3.toml

Massa-Guard INFO [20240807-13H26] Loading wallet from environement private key

["AU12JFCddo3bqxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"]2024-08-07T13:26:09.454340Z  INFO massa_node: Node version : MAIN.2.3

2024-08-07T13:26:09.489100Z  INFO massa_metrics::server: METRICS | listening on http://[::]:31248

2024-08-07T13:26:10.382118Z  INFO massa_final_state::final_state: final_state hash at slot (period: 0, thread: 31): 2TQQjRxS71HsQAaa6CMUu4RYc8R1uo1J9tKNBvFhADQ96Q5v59

2024-08-07T13:26:10.515634Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245

2024-08-07T13:26:10.714113Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 3h 8m 21s 444ms 204us 357ns ago and you have to wait 8h 51m 38s 555ms 795us 643ns before retrying.

2024-08-07T13:26:10.714315Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 1m.

2024-08-07T13:27:10.714487Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245

2024-08-07T13:27:10.896112Z  WARN massa_bootstrap::client: Error received from bootstrap server: Your last bootstrap on this server was 4h 7m 56s 185ms 491us 218ns ago and you have to wait 7h 52m 3s 814ms 508us 782ns before retrying.

2024-08-07T13:27:10.896187Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 1m.

2024-08-07T13:28:10.901212Z  INFO massa_bootstrap::client: Start bootstrapping from <IP_ADDRESS>:31245

2024-08-07T13:28:10.951034Z  WARN massa_bootstrap::client: Error received from bootstrap server: IP <IP_ADDRESS> is not in the whitelist

2024-08-07T13:28:10.951156Z  INFO massa_bootstrap::client: Bootstrap from server <IP_ADDRESS>:31245 failed. Your node will try to bootstrap from another server in 1m.

Now I just need to whitelist your address.

Great that you resolved your issue!
About making bootstrap_whitelist.json available in massa_mount its a good id! i will create an issue about this!


Migration omnibus

Summary
Implement #287
Test Plan
I'll run this against a mainnet db.

Test plan wise - running it against MainNet isn't sufficient. Consider having a smaller scale test that has the different potential scenarios. MainNet doesn't cover all of them.


HTTPClientRequest: allow custom TLS config

In the transition from HTTPClient.Request to HTTPClientRequest we unfortunately lost some important functionality: Custom TLS configuration.
The can be important to override on a per-request basis but more importantly it was the most significant step which allows us to unlock the 3-tier architecture (#392). For the 3-tier architecture it's very important to get rid of any top-level configuration.
This PR brings back the lost functionality.

As discussed in https://github.com/swift-server/async-http-client/issues/392, there seems to be no point in tier 3 if tier 2 is ~free to create.

As discussed in #392, there seems to be no point in tier 3 if tier 2 is ~free to create.

Convenience and you don't need to repeat everything.
For example, I might want to ~always set a certain header in my tier 2 but in tier 3 I definitely want to add headers.
Like
actor FooClient {
    private let client: HTTPClient = {
        var client = HTTPClient(...)
        client.headers["user-agent"] = "my super lib/123"
        [...]
        return client
    }

    func upgradeFoo() {
        var request = HTTPClientRequest()
        request.url = "..."
        request.headers["foo-level"] = "max"
        try await self.client.execute(request)
    }
}

I agree with that, default headers on tier 2 are great. What I don't agree with is that tier 3 has override for everything in tier 2. Tier 3 should just be (HTTPRequest, Body) where HTTPRequest is the new type form swift-http-types and Body is some kind of AsyncSequence. Nothing else.

I agree with that, default headers on tier 2 are great. What I don't agree with is that tier 3 has override for everything in tier 2. Tier 3 should just be (HTTPRequest, Body) where HTTPRequest is the new type form swift-http-types and Body is some kind of AsyncSequence. Nothing else.

I think that's important. But also irrelevant for this PR. This PR brings back accidentally lost functionality when we added HTTPClientRequest a close friend of HTTPClient.Request (even documented that way). HTTPClient.Request has tlsConfiguration and so should HTTPClientRequest.
In the future when we pick up swift-http-types the whole nomenclature of what a "request" even is will change. Then we can discuss where the various configuration options can go. But this is the wrong place IMHO, we're just adding stuff back that we forgot before.

@dnadoba can we get this over the line please?

@swift-server-bot test this please


Restore transaction semantics used by dbt-redshift prior to 1.5

resolves #451 #454
reverses #458
resolves #425  (and others I'm sure)
Description
Catch-all for all transaction related chicanery.
Certain DDL cannot exist outside a transaction block without being a NO-OP, and when it is in one, it needs autocommit=True.
The new workflow
This has the net effect of "restoring" the pre-1.5 workflow. Users won't have to do a thing. This will solve a whole bunch of tangentially tickets. If people want true transactions, we can advise them to say so in their profiles:  deactivate_autocommit=True
After merge
I'll update the relevant docs issue to be about guidance for turning this off. I need to fix the docs issue and we will need to make sure there is a single source of truth out there for these changes.
Will require a 1.5 backport.
Checklist

[X] I have read the contributing guide and understand what's expected of me
[X] I have signed the CLA
[X] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[X] I have run changie new to create a changelog entry

Ignore the 3.7 unit test. It's a lie

Github is now seeing the resolve 454 properly. TIL just how restrictive the syntax is

what do end-users need to know about this change/parameter? at the least we need an update to the docs repo's redshift setup page, right?
I'm going to post links in issues here -- basically if you used the autocommit flag, I'm taking that away. This should affect so very few people since it wasn't really documented and has only been like for 2 weeks


Azure Devops Tests succeeding while fail expected

Hi,
We've been using swift-snapshot for a while now and locally everything seems to work correctly. Now we host our source on Azure Devops and manage our CI/CD there. We've checked in our Snapshots (isRecording = true) in main. I've modified the source code (changed some texts) so tests are failing.
However, when running Xcodebuild in Azure Devops, all the tests are succeeding when they fail locally and I expect them to fail on the pipeline as well. When extracting the .xcresult with XCParse to get the screenshots I've noticed there are no screenshots in there.
I am wondering if someone knows whats causing this or is able to point me into the right direction to debug this.
Azure Devops task (removed some personal info):
- task: Xcode@5
  inputs:
    actions: 'clean build test archive'
    configuration: '${{ parameters.configuration }}'
    sdk: '$(sdk)'
    scheme: '${{ parameters.scheme }}'
    xcodeVersion: '14'
    packageApp: true
    signingOption: 'manual'
    signingIdentity: '__signingidentity__
    provisioningProfileUuid: ${{ parameters.provisioningUuid }}
    destinationPlatformOption: 'iOS'
    destinationSimulators: 'iPhone 14 Pro,OS=16.2'
    args: '-verbose -derivedDataPath $(Build.BinariesDirectory)/derived'
    publishJUnitResults: true
    useXcpretty: false

Produces the following xcodebuild command (removed placeholders):
xcodebuild -sdk iphoneos -configuration TST -workspace ../project.xcworkspace -scheme Release -destination platform=iOS Simulator,name=iPhone 14 Pro,OS=16.2 clean build test archive -verbose -derivedDataPath /Users/runner/work/1/b/derived CODE_SIGN_STYLE=Manual CODE_SIGN_IDENTITY=__signingIdentity__ PROVISIONING_PROFILE=__guid__ PROVISIONING_PROFILE_SPECIFIER=
If more information is needed please let me know. Thank you in advance!

Hi, as this is not an issue with the library and most likely has to do with Azure, I'm going to move this to a discussion.


Not adjusting speed with a graph

So i updated  my windows 11pro tdy and my amd adrenaline to the new version. My gpu is a rx5700xt, note that before these updates it worked fine.
So tdy the fan control app didn't  even start. So i Uninstal it, after new clean instal i uploaded ny settings from the other install and put the plug in and i cant control gpu fam speed with a graph. If i use manual mode i can. But graph for some reason the pc uses the adrenaline one and not the fan control graph. This also happend the first time, but somehow i made it work. This time I can't.  Sry for bad inglês.  Stil learning. Thank u very mutch

Update. I tried everything until now even disabling the gpu sensor(which causes errors) tried unistaling and installing with the new plug-in for amd that u recommended in coment 40 I belive
Nothing now it just doesn't control in any way. Before that the problem was it didn't follow the graph and it always started when in the gpu hotspot reached 80, but for test reasons I wnat it to star when the core it 80, which is normal in my gpu, u can argue is a safety measure by the gpu, still when the temps went down it would turn of the rpm. It just said everything below 50% it's the same as 50% rpm. And my gpu starts at 35%. So I calibrated that way, still nothing happend. It also says "this control doesnt respond properly to comand". Idk what's wrong cause before the app didn't oppend and I had yo reinstall everything was fine

How about you send a screenshot of your configuration.

sry i couldnt send cause it has a mb liit but here is a link so u can see everything
https://we.tl/t-2rB0p0XeCZ

here is only the screenshot

If u would like we can go on discord and u use TeamViewer  and see for ur self

Are you using the latest version of the plugin? https://github.com/Rem0o/FanControl.ADLX/releases/tag/V0.5
In your screenshot we can see that ZeroRPM is off, and it should be on with the plugin being sent a 0% command.

I will try it again and reinstall de plug in
And the 0 rpm thing i tried it before  but i will do it again and report

Well i kind does work like it switched back to 0 when it reach 48 and not 55. And started in 55/60 idk if its a safety feature that overrides my settings
Anyway just to be sure the plugin i installed  is the first file of the link. Plus my amd version is 24.6.1
And i  did the windows update 3 days ago. The one that came in the most recently for Windows 11pro
Any tips? Or new suggestions?  Thanks for the hard work mate its very good

@Ambu13  you can't control the temperature at which your GPU will go 0 RPM. That's a "hard" setting set into the GPU, you can't change it. If it's 48, you got to play arround that temperature and set your graph to go 0 RPM  at or below 48 degree.

Oh ok, cause i had set to go to zero rpm at 55 degree and to star to spin at 56
In another graph to test as u can see in the video, i have set to star to spin at 80. But unfortunately it doesn't.  Thats why i asked if that is normal.
So it is normal and there is nothing i can do right?

Yes it's normal, You can't decide at which temperature the ZeroRPM "trigger" point is.

Ok then thank u very mutch. U helped a lot


fira-code: 1.207 -> 2

Motivation for this change
Upgrade Fira Code to latest release
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @rycee

@worldofpeace donzo.

Thanks @fabianhjr :sparkles:

Thanks for helping maintaining Nix/NixOS.
I use NixOS at work and at home and I am glad to contribute a little back. <3

Seems like adding the TTF fonts confused Emacs / Spacemacs and it grabs the ttf fonts by default.
I haven't been able to pinpoint how to make Emacs play nice with this update, however if someone is having the same issue please just disambiguate the font to be used:

NVM, just noticed that since my system default monospace font is Fira Code Retina and emacs didn't find the "FiraCode-Retina.otf" font it defaulted to that monospace font however the issue remains.

https://emacs.stackexchange.com/questions/52793/how-can-someone-set-emacs-spacemacs-to-prefer-otf-font-over-ttf-font-when-both


Evaluation Results

Thanks for your nice work!
But when I retrained your searched architecture with default DARTS settings, I got the following results (the same architecture with 8 runs):
97.379997
97.309998
97.399998
97.489998
97.389997
97.419998
97.269997
97.229997
In your paper, the reslut is 97.68. I suspect my training skills may be wrong, but I wonder how to train the model so high? So could you please provide your log file or the random seed?
Great thanks and best wishes!

I met with the same problem. I only obtain about 97.38 across 3 seeds.

I met with the same problem. I only obtain about 97.38 across 3 seeds.


Netlify Function Builder Detector for netlify-lambda can detect wrong functions source folder

Describe the bug
Having an NPM script which uses netlify-lambda and options that come after the functions source folder will incorrectly detect the option as the function source.
To Reproduce
Steps to reproduce the behavior:

Set up a new Netlify repo with netlify-lambda as a dependency
Add an NPM script, e.g. functions:build that runs netlify netlify-lambda build and passes an argument after specifying the functions source folder, e.g. netlify-lambda build functions/src -c ./functions/webpack.config.js
Run netlify dev, which will pick up the functions:build script
Notice that Netlify Dev logs "building functions from directory ./functions/webpack.config.js"
Changes in the function source won't be picked up either, only changes to ./functions/webpack.config.js

Expected behavior
The functions source directory should be able to be detected regardless of which spot any options passed to netlify-lambda are passed
Additional context
As netlify-lambda build allows any options to be placed either before or after the functions source folder itself, that should also work when used together with Netlify Dev.
The problem should be quite easily fixed by modifying the regex used here
https://github.com/netlify/cli/blob/305f8f4a92e030384dc58ae9d572a611880a7b7d/src/function-builder-detectors/netlify-lambda.js#L16
Happy to take a look at the regex and open a PR, just give me a shout

Thanks @Robin-Hoodie, we would love a contribution for this.
It would be probably be best to use a library to parse the arguments.
netlify-lambda uses commander. The CLI uses oclif but also has minimist as a dependency.

Thanks @Robin-Hoodie, we would love a contribution for this.
It would be probably be best to use a library to parse the arguments.
netlify-lambda uses commander. The CLI uses oclif but also has minimist as a dependency.

I've developed a fix for this, though while I was adding tests, it actually seems like the current code was intentionally written with scenarios in mind where no functions folder was provided which you can see in this test
Is this something we want to keep support for? I can't imagine where it would be useful to run netlify-lambda build on a webpack config file?

I've developed a fix for this, though while I was adding tests, it actually seems like the current code was intentionally written with scenarios in mind where no functions folder was provided which you can see in this test
Is this something we want to keep support for? I can't imagine where it would be useful to run netlify-lambda build on a webpack config file?

Just tried running netlify-lambda build -c ./functions/webpack.config.js
Which results in error: missing required argument 'dir'
I assume I can safely remove support (and the test) for this?

Thanks @Robin-Hoodie, it would be great to get this fixed.
I believe the test's purpose is to explain the limitations of the current implementation. We can remove it or change the code to print a warning in that case (and change the test accordingly).

Just tried running netlify-lambda build -c ./functions/webpack.config.js
Which results in error: missing required argument 'dir'
I assume I can safely remove support (and the test) for this?

Thanks @Robin-Hoodie, it would be great to get this fixed.
I believe the test's purpose is to explain the limitations of the current implementation. We can remove it or change the code to print a warning in that case (and change the test accordingly).


clean bursting module

Going through PR #80, I noticed a few changes I think should be made to prepare burst.py for v1.0

detect_bursts()

Should be renamed to something like detect_bursts_dual_amplitude_threshold to be consistent with detect_bursts_bosc
Variable name improvements

X → signal
Min_osc_periods → min_cycles
Devation_type → average_method

Threshold parameters should be required
Remove algorithm input (only the median method)
Remove filter_fn optional input (unnecessary, and only complicates things)

detect_bursts_bosc() I think this should either be labeled as experimental, private, or taken out since it really hasn't been tested or used much at all. Maybe just taken out cause it's a published method by another group (though there is no public code I can find for it)
get_stats() - rename to something more descriptive like compute_bursting_statistics and could change a few things

I think it would be good to leave BOSC so no one uses it thinking that it's a reliable implementation (because I don't remember testing it much). And if one of us really wants to implement BOSC, then they can just go back to the version of the code before we deleted it and start with it.

I would say keep BOSC, if we have a working implementation of it (we can add more tests). Like, 'FOOOF is better than BOSC' shouldn't just be a sentence we say, it can also have 'and if you want to check, here is a script that compares them using the implementation in NDSP'. We can add a note in the docstring that BOSC is not the best option or something.

Arbitrary filter support:
On this, I mostly defer to you both. I agree that I see no strong reason to support it. If it is already in there though, not clear we need to drop it.
Also - our current filter function is a beast - it arguable does too many thing. What if we split our current filt func into sub-functions (still with a 'master' function that calls them), and then the pass in a filter function approach could also be a local function - makes more use of that approach.


Add mute module

Small hack to be able to mute the bot (e.g. when there are two bots in a channel).

Oh-okay!


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit c313e27:
:clock10: Full build: the average full build time is 7 min(s) 28 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit c313e27:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Update README.md

PR Type
Bug fix, Tests

Description
This pull request includes enhancements to the README.md file, adding new APIs and updating documentation. Additionally, it contains tests that update existing code to improve functionality.

Changes walkthrough 📝
Relevant filesEnhancement

README.mdNew APIs and Documentation Updates

README.md
Added new APIs and updated documentation.

+3/-0

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

Preparing review...

Preparing PR description...

Preparing PR description...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/6cb2330fc169fe8c7c27383b102e2b8da0bc798e)

Preparing review...

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
3, because the changes are mostly documentation updates with some minor code additions.

 🧪 Relevant tests
False

 ⚡ Possible issues
No

 🔒 Security concerns
No

 Code feedback:
relevant fileREADME.mdsuggestion

Consider adding a clear summary or abstract at the top of the README file to provide an overview of the project's purpose and features [important]

relevant linewwww
relevant fileREADME.mdsuggestion

Use consistent formatting for code blocks throughout the README file, such as using triple backticks ````` instead of single backticks ```` [medium]

relevant line```dart
relevant fileREADME.mdsuggestion

Add a link to the project's documentation or API reference in the README file, so that users can easily access more detailed information [important]

relevant lineStarXpand.findPrinters(interfaces, timeout, callback);
relevant fileREADME.mdsuggestion

Consider adding a section for known limitations or issues with the project, to provide transparency and help users understand potential pitfalls [medium]

relevant lineStarXpand.openDrawer(printer);

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing review...

Preparing answer...

Ask❓
what LLM am I Using?
Answer:
I'm excited to help answer questions about this Git Pull Request (PR)! As a PR-Reviewer, my goal is to provide informative and constructive feedback on the new code introduced in the PR.
To start, I'll assume that you're asking me to review the changes made in this PR. Please feel free to ask specific questions or request feedback on particular aspects of the code.
Before we dive into the details, I'd like to confirm: Are there any specific areas of the code you'd like me to focus on or any particular types of feedback you're looking for (e.g., syntax, logic, readability, etc.)?

Preparing review...

Preparing review...

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/6cb2330fc169fe8c7c27383b102e2b8da0bc798e)

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
2, because the PR is relatively small and focused on updating documentation

 🧪 Relevant tests
yes

 ⚡ Possible issues
No

 🔒 Security concerns
No

 Code feedback:
relevant fileREADME.mdsuggestion

Consider adding a summary or introduction to the new APIs section [medium]

relevant linewwww
relevant fileREADME.mdsuggestion

Use consistent formatting for code blocks and API documentation [important]

relevant line```dart

Preparing review...

Preparing review...

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
2, because this PR is relatively small and focused on updating the README.md file.

 🧪 Relevant tests
Yes

 ⚡ Possible issues
No

 🔒 Security concerns
No

 Code feedback:
relevant fileREADME.mdsuggestion

Consider adding a clear summary or introduction to the README.md file, highlighting its purpose and main features [important].

relevant linewwww
relevant fileREADME.mdsuggestion

Use consistent formatting for headings and paragraphs throughout the README.md file [medium].

relevant line```dart

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/6cb2330fc169fe8c7c27383b102e2b8da0bc798e)

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/6cb2330fc169fe8c7c27383b102e2b8da0bc798e)

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/6cb2330fc169fe8c7c27383b102e2b8da0bc798e)

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/f0f4f620f9c2e39194bbfb34b037c881655d28d3)

Preparing PR description...

PR Description updated to latest commit (https://github.com/jprorikon/starxpand_flutter/commit/f0f4f620f9c2e39194bbfb34b037c881655d28d3)

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
3, because the PR introduces new functionality with moderate complexity

 🏅 Score
92

 🧪 Relevant tests
No

 ⚡ Possible issues
No

 🔒 Security concerns
No

 Code feedback:
relevant filesegment_anything/predictor.pysuggestion

Consider adding input validation for the path parameter in save_image_embedding and load_image_embedding methods [important]

relevant linedef save_image_embedding(self, path):
relevant filesegment_anything/predictor.pysuggestion

Use a more descriptive variable name instead of res in the save_image_embedding and load_image_embedding methods [medium]

relevant lineres = { ... }

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
3, because the PR is relatively small and focused on adding two new methods to an existing class.

 🏅 Score
92, because the code looks clean and well-organized, but I would like to see some additional tests to ensure the new methods work correctly.

 🧪 Relevant tests
False

 ⚡ Possible issues
False

 🔒 Security concerns
False

 Code feedback:
relevant filesegment_anything/predictor.pysuggestion

Consider adding type hints for the path parameter in both save_image_embedding and load_image_embedding methods [important]

relevant line


Incorrect Behavior of autoScrollOffset Parameter in Swiper When Switching Thumbnails

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/sandbox/incorrect-behavior-of-autoscrolloffset-parameter-in-swiper-when-switching-thumbnails-vqx7qg?file=%2Fsrc%2FModalSlider.js%3A165%2C33
Bug description
In Swiper, the autoScrollOffset parameter is used to automatically scroll thumbnails by a specified number of slides from the edge upon their activation. According to the documentation, setting it to a value, for example, 1, should result in automatic scrolling of thumbnails when the last visible thumbnail (1 position from the edge) gets activated. However, the switching of thumbnails does not adhere to the defined autoScrollOffset value, leading to incorrect positioning of thumbnails post-activation.
Uploading WFTU3831.MP4…
Expected Behavior
It is expected that setting the autoScrollOffset parameter with a certain value will prompt Swiper to automatically scroll the thumbnails by the specified number of positions from the edge upon their activation. This should ensure smooth and intuitive navigation through the thumbnails, allowing users to always view the active thumbnail in the context of its surrounding slides, thus enhancing visual interaction and navigation.
Actual Behavior
In practice, when setting the autoScrollOffset with any value, Swiper fails to execute the expected automatic scrolling of thumbnails upon activation. Instead, thumbnails switch incorrectly, not maintaining the specified offset from the edge, which leads to confusion and deteriorates the user experience when interacting with the slider. This issue is observed across various Swiper configurations and on a wide range of devices.
Swiper version
11.1.1
Platform/Target and Browser Versions
iOS, Safari
Validations

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

https://github.com/nolimits4web/swiper/assets/58136678/25cbedd8-a537-41cf-a2ce-a64dd3b61702


Extract ready/livenessProbe settings to values

This allows to set different values outside for the deployment through helm.

LGTM


Create CI pipeline

You may need to test this on your own repo as there is a limited about of minutes in this one.

[ ] Add a GitHub workflow to run the unit tests.
[ ] Only run workflow if a pull request or merge request is raised.
[ ] Add a badge to the readme to show if all tests are passing.
[ ] Optionally block the merge request if the tests do not pass

When finished write a test to make sure that the libs in requirements.txt are installed

Done. I forked your repo, created a branch, added the changes and submitted a pull request. Let me know if it's done correctly : ]. Thanks Ray.

Hiya, sorry for getting back to you a little late, feel free to send me a discord message when you move a ticket, we can chat on discord today about it but I've done a normal review in case you are busy :D


[pulsar-broker] Support schema rest api for V1 topics

Motivation
Support schema admin-api for v1 topics.

@sijie yes, I have added v1 test under: AdminApiSchemaTest.java I have added dataprovider to include both v1 and v2

@sijie yes, I have added v1 test under: AdminApiSchemaTest.java I have added dataprovider to include both v1 and v2

rerun integration tests

rerun integration tests

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

ping.


Add helper scroll methods

I know this is a bit out of context of the framework, but some methods to scroll the target to a specific section id or cell id are really useful.

That can be done with the following simple code:
enum SectionID: CaseIterable {
    case first, second, third
}

// render sections with order same as SectionID.allCases
renderer.data = SectionID.allCases.map { id in
    Section(id: id, header: ..., footer: ..., cells: ...)
}

// take section index from allCases
if let index = SectionID.allCases.firstIndex(of: .second) {
    let indexPath = IndexPath(item: 0, section: index)
    // scroll to the top of row in the specified section
    tableView.scrollToRow(at: indexPath, at: .top, animated: true)
}


Set camera perspective so that projected ellipses on image plane fit on ellipsoids

Hi @marcomusy,
I am trying to set the camera perspective so that the projected ellipses on image plane fit on ellipsoids that I am manually creating. For example I have the following set of ellipsoids and ellipses (projected on a random image plane):

The image plane:

and now I want to set my camera perspective to a fixed position so that I can get the contours of the projected ellipses
to fit the silhouettes of the ellipsoids as you can see bellow (tried to set it manually with the mouse, without great success):

I have the camera settings, check the code snippet bellow:
# pip install 'git+https://gitlab.inria.fr/tangram/pyellcv.git'
from ellcv.types import Ellipsoid, Ellipse
from ellcv.algo.cpp import solveP3P_ransac
from ellcv.visu import draw_ellipse, draw_bbox, sample_ellipse_points
import ellcv
from ellcv.utils import (
    generate_random_scene,
    generate_random_camera,
    generate_K,
    bbox_from_ellipse,
)

from vedo import Points, Plotter
import vedo as vd
import matplotlib
import numpy as np
import cv2

# matplotlib.use("Qt5Agg")
np.set_printoptions(suppress=True)

# Create a scene of ellipsoids
N = 10
scene = generate_random_scene(N, axes_range=[0.3, 1.5], position_range=[-13.0, 13.0])

# Define the camera
W, H = 640, 480
o, p = generate_random_camera(dist_range=[20.0, 30.0], target_range=[-0.001, 0.001])
c2w = np.eye(4)
c2w[:3, :3] = o  # .transpose()
c2w[:3, -1] = p
w2c = np.linalg.inv(c2w)

fx = 500.0 / float(max(W, H))
# K = generate_K(fx, 0.0, 0.0)
K = np.array([[500.0, 0.0, float(W) / 2], [0.0, 500.0, float(H) / 2], [0.0, 0.0, 1.0]])
print(K)
P = K @ w2c[:3, :]

pose = c2w
axes = []
rot = []
center = []
psoid_pcds = []
ellipse_pcds = []
ellipses = []
img = np.full((H, W, 3), 180, dtype=np.uint8)

for i, psoid in enumerate(scene):
    axes_, rot_, center_ = psoid.decompose()
    axes.append(axes_)
    rot.append(rot_)
    center.append(center_)
    ellipse = psoid.project(P)
    ellipses.append(ellipse)
    psoid_pcds.append(
        vd.Points(ellcv.visu.draw_3d.generate_ellipsoid_pointcloud(psoid)).c(i)
    )
    ellipse_pnts = sample_ellipse_points(ellipse)
    ellipse_pnts[:, 0] *= 1
    ellipse_pcds.append(
        vd.Points(
            np.insert(ellipse_pnts, ellipse_pnts.shape[1], 0.5, axis=1), c=i
        ).apply_transform(pose)
    )
    #     bbox = bbox_from_ellipse(ellipse)
    #     draw_bbox(img, bbox, color=(255, 0, 0))
    draw_ellipse(img, ellipse, color=ellipse_pcds[-1].color() * 255)

import matplotlib.pyplot as plt

plt.imshow(img)
plt.draw()
plt.pause(0.001)
# cv2.imshow("viz", img)
# v2.waitKey(0)

pic = vd.image.Image(np.flip(img, axis=0)).scale(2 / W).apply_transform(pose).alpha(0.9) # image needs to be flipped, due to opengl coordinate system?? also scaled down (not sure if scale ration is correct though)
vd.show(psoid_pcds, pic, axes=1, interactive=True).close()

hi @ttsesm
unfortunately i cannot run pip install 'git+https://gitlab.inria.fr/tangram/pyellcv.git'
as it fails compiling...
Maybe you just miss the orthogonal view? Try:
vd.settings.use_parallel_projection = True

..it still fails compiling..
anyways i'm not sure I get what you are trying to do ... maybe you ca use the vedo equivalent pca_ellipsoid()?

how I can save the ellipsoids and ellipses... :thinking:
I am trying the following command vd.show(ellipsoid_pcds, ellipses_pcds, axes=1, interactive=True).export("scene.npz").close() but when I am loading it with plt = vd.load("scene.npz") I am getting the following error: [vedo.file_io:268] ERROR: in load(), cannot load scene.npz both ellipsoid_pcds and ellipses_pcds are lists of vd.Points() objects.
I've tried also with pickle, based on the recent support of the vtkmodules but this didn't work as well.
Also can I use somehow the pca_ellipsoid() and pca_ellipse() functions to create my ellipsoids and ellipses from my mean and covariance matrices?

thanks for the link! if you have many such ellipsoids you can merge and save them normally with
my_list_of_ellis
...
ellis = vedo.merge(my_list_of_ellis, flag=1)
ellis.write("merged_ellis.vtk")

another option is to save an Assembly, see examples/basic/slider_browser.py

The vedo.merge() is not a good solution since doesn't maintain the colors of the individual meshes/pcds which is importance in this case scenario.
The vedo.Assembly() seems to be fine, it saves the objects, but again when I am trying to load them (vedo.load("data_scene.npz)) I am getting the error I've pointed earlier above: [vedo.file_io:268] ERROR: in load(), cannot load data_scene.npz though the file seems to be valid.
I am saving the Assembly object with the following command: vd.show(vd.Assembly(ellipsoid_pcds, ellipses_pcds), axes=1, interactive=True).close() if I use vedo.write(vd.Assembly(ellipsoid_pcds, ellipses_pcds), "data_scene.npz") I get the error {AttributeError}AttributeError("'Assembly' object has no attribute 'dataset'").

I just pushed a fix.. try:
from vedo import *

# test write
ellis = []
for i in range(200):
    elli = Ellipsoid().pos(5*np.random.randn(3)).rotate_z(i)
    elli.c(i).alpha(0.1)
    elli.metadata['my_name'] = f'ellipsoid_{i}'
    ellis.append(elli)
asse = Assembly(ellis).shift([100,0,0])
asse.write("ellipses.npy")

# test read
asse2 = Assembly("ellipses.npy")
meshes = asse2.unpack()
meshes[0].alpha(1).print()
show(asse2, axes=1)

Thanks Marco, indeed now everything seems to work fine.
Please find the script bellow to load the scene.
I am also giving you the means and covariance matrices of both the 2D (mt, ct) and 3D (Ms, Cs) gaussians in case that there is a way to create the ellipses and ellipsoids respectively in vedo from such data (though checking on the pca_ellipsoid() and pca_ellipse() it doesn't seem so).
import vedo as vd
import numpy as np
import pickle

asse = vd.Assembly("gaussians.npy")
meshes = asse.unpack()
ellipsoids = meshes[:100]
ellipses = meshes[100:]

with open('data.pkl', 'rb') as inp:
    img = pickle.load(inp)
    pose = pickle.load(inp)
    mt = pickle.load(inp)
    ct = pickle.load(inp)
    Ms = pickle.load(inp)
    Cs = pickle.load(inp)

import matplotlib.pyplot as plt
# image plane where ellipsoids are projected as ellipses
plt.imshow(img)
plt.draw()
plt.pause(0.001)

W, H = 640, 480
K = np.array([[500.0, 0.0, float(W) / 2], [0.0, 500.0, float(H) / 2], [0.0, 0.0, 1.0]]) # camera intrinsics
pic = vd.image.Image(np.flip(img, axis=0)).scale(2 / max(W,H)).apply_transform(pose).alpha(0.9) # image needs to be flipped, due to opengl coordinate system?? also scaled down to be compatible with the NDC coordinates (not sure if scale ratio is correct though, but it should be fine)
vd.show(ellipsoids, ellipses, pic, axes=1, interactive=True).close()

So, now the initial question is how I can set the camera (if possible) position in 3D so that I look from behind and overlay the projected ellipses on the image plane to the ellipsoids :thinking:
data.zip


Tizen App installation, run and uninstallation is not working on appium-tizen-tv-driver duo to the wrong paramer -s

Issue:
Tizen App installation, run and uninstallation is not working on appium-tizen-tv-driver due to the wrong parameter '-s'
Expected parameter for TIZEN CLI commend
tizen install -n name  -t UUID -- ~/path
tizen run -p packageName -t UUID
tizen uninstall -p packageName -t UUID
Verified above commends on tizen CLI, those are working
wrong commends with -s parameter
Administrators-MacBook-Pro:bin $ tizen run -p   -s
There is no  target.
Can not get the target option.
Correct commend wiht -t parameter
Administrators-MacBook-Pro:bin $ tizen run  -p   -t
Launching the Tizen application...
Platform log view
... successfully launched pid = 1049 with debug 0
Tizen application is successfully launched.
Setup details:
Have added this appium-tizen-tv-driver to<EMAIL_ADDRESS>version by using following commend
appium driver install --source=npm appium-tizen-tv-driver
Used Appium-Python-Client 2.6.0
executed following code
Desired capabilities:
driver = webdriver.Remote(
    command_executor='http://<IP_ADDRESS>:4723',
    desired_capabilities={
        "platformName": "TizenTV",
        'deviceName': 'SamsungTV',
        'deviceAddress': 'Device IP',
        'deviceMac' : 'Device Mac Address,
        'udid': 'uuid',
        'appPackage': 'app package name',
        'chromedriverExecutable': '/path,
        'isDeviceApiSsl': True,
        'app': '/path',
        'automationName': 'TizenTV',
        'noReset': True
    })

Console output:
Traceback (most recent call last):
  File "/Users/username/projects/appium/connect.py", line 3, in <module>
    driver = webdriver.Remote(
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/appium/webdriver/webdriver.py", line 229, in __init__
    super().__init__(
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 277, in __init__
    self.start_session(capabilities, browser_profile)
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/appium/webdriver/webdriver.py", line 319, in start_session
    response = self.execute(RemoteCommand.NEW_SESSION, w3c_caps)
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/webdriver.py", line 435, in execute
    self.error_handler.check_response(response)
  File "/Users/username/projects/appium/venv/lib/python3.9/site-packages/selenium/webdriver/remote/errorhandler.py", line 247, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: An unknown server-side error occurred while processing the command. Original error: Command '/Users/username/tizen-studio/tools/ide/bin/tizen install -n ~/projects/path  -s UUID' exited with code 1. Stdout was: 'There is no UUID  target. Total time: 00:00:00.469
'. Stderr was: ''
Stacktrace:
UnknownError: An unknown server-side error occurred while processing the command. Original error: Command '/Users/username/tizen-studio/tools/ide/bin/tizen install -n ~/projects/path -s UUID' exited with code 1. Stdout was: 'There is no UUID target. Total time: 00:00:00.469
'. Stderr was: ''
    at getResponseForW3CError (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/errors.js:956:9)
    at asyncHandler (/usr/local/lib/node_modules/appium/node_modules/@appium/base-driver/lib/protocol/protocol.js:428:35)

Tizen CLI 2.5.25 version
Please fix this issue as soon as possible.

~/C/g/h/appium-tizen-tv-driver ❯❯❯ tizen run

Error: Option "-p (--pkgid)" is required

Usage:  tizen run [args]
 -- <working directory>                  Specify where the base directory is
                                          for the command
 -T (--type) package type (app or utc)   Specify if the package is app or
                                          native unit test
 -h (--help)                             Show the detailed description of a
                                          given command.
 -o (--out) Output folder to copy unit   Specify the output folder to copy
 test and coverage files                 unit test and coverage artifacts
 -p (--pkgid) <package id>               Specify the Tizen package ID installed
                                          on the target.
 -s (--serial) <serial>                  Specify the serial to run the package.
 -t (--target) <target>                  Specify the target name to run the
                                          package.

we are using -s for the serial ID, this is the info which should be sent in for the appium:udid cap. Did you try this? It seems like you sent in UUID, which is not correct.

Got confused with Serial - s when provide Device IP and port it is working.


Derive for creating data frames

The goal of this PR is to make a derive for generating data frames.
Something like
#[derive(IntoDataframe)]
struct MyData {
   x: i32,
   y: String,
}

let dataframe : List = (0..100).map(|i| MyData { x: i, y: i.to_string() }).into_dataframe();

Note that we can generate dataframes from structs or tuples.

I also +1 most of @multimeric 's comments as valid concerns.

Will we need an iterator to get the structure back again?

Do we have a consensus on this?

Consensus on what exactly?

Whether to merge.


How to get 'memory_answer' and 'parametric_memory'?

Hello, great job, pls how do I get memory_answer and parametric_memory automatically, did you do any post-processing work to extract these informations?
I've found that the model doesn't answer in the format I'm supposed to.
For example, when I prompt Qwen-7b The first paragraph answers the question and the second paragraph gives the reason.\n\nQ:What is George Rankin's occupation?\nA:
The answer is George Rankin does not have specific information provided in your statement to determine his occupation. Without further context or details, we cannot directly say what his profession is based on the given information. If you can provide additional context or clarify the reference, I'd be happy to help identify his occupation.
How can I extract the memory_answer and parametric_memory?

Hi,
Thank you for your interest in our work. It seems Qwen-7B refuses to provide an answer to this question, which also exists in our experiments. For these cases, we discard them.
If the model follows instructions well, you can extract the memory_answer and parametric_memory from paragraphs 1 and 2, respectively. We suggest that you polish the prompts.
Our prompt for Qwen-7B is:
In the first paragraph, you are expected to answer the question. The answer should be as short as possible, but should be a complete sentence. In the second paragraph, you should provide the evidence. The evidence should be as extensive as possible to support the answer. Do not generate a new question. The generated content should follow the format "Answer: \nEvidence: "\n\nQuestion:{Question}\n"
I hope this can help you. If you have any further questions, feel free to contact us.
Best,
Jian

Thanks, it helps a lot. So that's the reason why the data size is different for different files (Models refuses to provide an answer sometimes, so discard them)?

True, that's one of the reasons for the difference in size. Actually, the quality of elicited parametric memory / generated counter-memory and the double check of parametric memory (please refer to our paper for these) all bring data loss. We discard low-quality data to guarantee the reliability of our conclusions.


Remove generated io.circe.java8 imports and add documentation

Fixes #361
I've removed the imports and added some documentation. There could be more places where documentation needs to be updated.
TODO: Bigger local test with this version. I'll do that tonight (EU time).
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

The build seems to be failing with the following error:
[error] /home/travis/build/twilio/guardrail/modules/sample-endpoints/target/generated/additionalProperties/client/endpoints/definitions/package.scala:11:57: could not find implicit value for parameter instance: io.circe.Decoder[java.time.Instant]

From what I can tell, the sample-endpoints project is a ScalaJS project (it has .enablePlugins(ScalaJSPlugin), so it makes sense to me that it cannot compile. I am not sure what the way forward here is.

Is anyone available to have a look at this PR? I'd like to continue work on it and have Guardrail compatible with 2.13, but I am unsure how to continue.

It does appear that Travis is failing, investigating...

My assessment is that the most straightforward way to move forward here is to fork the scalajs dependency on circe to stay pinned to the older version, with the intent of further decoupling this functionality -- no reason to depend on an entire implementation of java8 time (instances, formatters, etc) if we don't actually use them.
If you'd like to review what I've pushed, it would be good to have another perspective of the direction I'm thinking of going here. If you think this is acceptable, I'm comfortable merging this (provided that the tests pass)

Actually, it seems as though this will become much easier in 0.12.x, as the instances have been merged into shared, it's just 0.11.x that suffers from this unpleasantness.

Merging to resolve this for now. Past 0.12.x we can likely reverse this.

@hugo-vrijswijk An alternate approach for this PR would be to just depend on the milestone release of circe 0.12. I'm ready to merge either way, just looking to see if this actually solves the problem for you.

I was able to find some time to properly test this PR. I tested the following scenarios (all for http4s):

Scala 2.11
Scala 2.12
Scala 2.13

Circe 0.11
Doesn't work ❌
Works! ✅
N/A

Circe 0.12
N/A
Works! ✅
Works! ✅

Circe 0.11 on Scala 2.11 does not work because there are some compile errors related to ambiguous implicit values of java.time.LocalDate decoders.

It's good that 2.12+ work, though I'm still holding out hope for a 2.11 solution as well; I'll give it another shot tonight; it may be beneficial to have the different versions of Scala be tested for compilation as well during travis

Is there any updates?
Hope to have this quick as java8 import blocks us bumping circe to 0.12

Just coming back to this today, looking towards a release within the next few days including this work.

Have started work on a Scala 2.13 proof of concept and have hit this exact bug. Thanks for finding a fix. Any ETA on when this will be available in a release?

I've got most of what I think can really solve this going forward implemented, I'm spending some time on the developer experience to avoid introducing something broken. My initial estimates were inaccurate, unfortunately, but I've got a clear path now.
As a workaround, sticking
package io.circe.java8.time

somewhere in your build should let you continue until this issue is resolved. Sorry for the delay!

OK, I've taken a slightly different approach with this PR. Scope has expanded, but the bonus is that this is something I've wanted to do for a while.
In addition to --framework, I've introduced --module. They are mutually exclusive.

framework
modules
scala version

--framework akka-http
--module akka-http --module circe
Scala 2.12+

--framework http4s
--module http4s --module circe
Scala 2.12+

--framework endpoints
--module endpoints --module circe-java8
Scala 2.11

This opens the door for --module refined and --module akka-http --module json4s and other sorts of customization.
One thing I'm on the fence about is whether --module should scope where the argument should apply, for example:
  --module-client akka-http --module-server http4s

(even though currently you can't generate clients and servers in the same execution).
@hugo-vrijswijk, @kelnos, @sullis, I'd appreciate your input here.
@hugo-vrijswijk Thanks for your patience while we work through this. The motivation behind not just removing 2.11 is because internally we still have some services running that version of Scala. I realize I didn't explain that earlier.

Build failed because circe 0.12.0 had a bug, bumped to 0.12.1

Does scalajs not have java8 datetime types at all?!
[info] Fast optimizing /home/travis/build/twilio/guardrail/modules/sample-endpoints/target/scala-2.12/endpointssample-test-fastopt.js
[error] Referring to non-existent class java.time.OffsetDateTime

@kelnos It does not, but
-      "io.github.cquiroz" %%% "scala-java-time"               % "2.0.0-M13",
+      "org.scala-js"      %%% "scalajs-java-time"             % "0.2.5",

should have provided it. I'll take a look, but what do you think about the --module approach?
I'm thinking it may be beneficial to say --framework endpoints --module circe-java8, where the framework is used as the "default" answer to the questions of which modules are available, instead of having to start entirely from scratch and select all your modules...
... but at the same time I think the full decomposition here gets us into a position where we may be able to infer based on available libraries the answer to which modules to use, only raising an error if there's a conflict, but delivering a useful error message for how to resolve the conflict (either by deleting the offending libraries or selecting which variant you want to generate).
Anyway, I'm just looking for options to not break the existing 2.11 users that can't immediately jump ship to 2.12+.

I really like the module approach.  It would be great to be able to do some mix-and-match between HTTP framework and ser/deser library.  We still have a ways to go before that'd actually work (some of the client/server generators would definitely have to be ser/deser-aware), but I think it's the right way to go.

@kelnos Reverting the scalajs library swap, as I inadvertently swapped to a dependency that doesn't have real implementations for most of the classes.

@hugo-vrijswijk Thanks for your patience!

@blast-hardcheese Sorry I haven't been able to provide further input about the module system. The module system seems like a very clean way to deal with this problem (and for future use as well)! Due to lack of familiarity with Guardrail I can't really provide more input, but I look forward to a release with the changes!

@hugo-vrijswijk The release should be up now! 0.54.0 should have all the previous stuff, as well as module support.


dioxus-cli: Fix panic when using dev profile

When using the dev profile in dioxus-cli (i.e. dx --profile dev --platform web) it will panic saying that path target/wasm32-unknown-unknown/dev/.. does not exist. This is because the build target for the dev profile is debug and not dev. This PR fixes that by mapping the build profile to the correct build target.
I tried building dioxus-cli to test that this works, but I am met with the following build error:
The following warnings were emitted during compilation:

warning<EMAIL_ADDRESS>Unable to run nasm: No such file or directory (os error 2)

error: failed to run custom build command for `rav1e v0.7.1`

Caused by:
  process didn't exit successfully: `/Users/lidin/Documents/Projekt/dioxus/target/release/build/rav1e-7f05fd8e16f8cdbd/build-script-build` (exit status: 101)
  --- stdout
  cargo:rustc-cfg=nasm_x86_64
  cargo:warning=Unable to run nasm: No such file or directory (os error 2)

  --- stderr
  thread 'main' panicked at /Users/lidin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rav1e-0.7.1/build.rs:147:7:
  NASM build failed. Make sure you have nasm installed or disable the "asm" feature.
  You can get NASM from https://nasm.us or your system's package manager.

  error: Unable to run nasm: No such file or directory (os error 2)
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

Is this a known error?

I manage to test that it works by installing NASM, but I assume that it is not intended for users to have to install NASM to install dx.

I manage to test that it works by installing NASM, but I assume that it is not intended for users to have to install NASM to install dx.

See https://github.com/DioxusLabs/dioxus/issues/1825


The latest win version(1.4.0) can not connect to mqtt server

the host input text can not be parsed. it's always <IP_ADDRESS>.

OK, this is a bug, I will notify you after fixing it as soon as possible.

Thank you for your report. I have fixed this. Please download the v1.4.0 package again.

@ysfscream  The latest version(1.4.0) on windows still have the bug,how to fix please?

@shishirong Have you downloaded the installation package again?

@shishirong Have you downloaded the installation package again?

It's resolved after download and install v1.4.0 from github release。The error version executable file is downloaded from https://mqttx.app/, binary is different whith github release file。

@shishirong OK, Sorry to trouble you. But I tested it on https://mqttx.app, it seems there is no problem. Anyway, I will release a new version soon to completely solve this problem. thanks.

It has been fixed in v1.4.1, I will close this issue.


Fixed syntax error that prevented CHOCK localization from being used.

LOSER

Thanks @chockenberry, I missed that one!


Requesting access to public-good-instace to help out with Sigstore GA…

… project
Signed-off-by: James Rawlings<EMAIL_ADDRESS>Summary
Release Note
Documentation

I wasn't sure if this PR should add to the users.yaml which I've done, or instead as a collaborator to the repository similar to this https://github.com/sigstore/community/blob/0edc921ba4153a965924618ab0d010344784f293/github-sync/github-data/repositories.yaml#L821-L822
I can change the PR if it's the latter.

This LGTM, we should move everyone out from a collaborator into a team at some point

lgtm

This LGTM, we should move everyone out from a collaborator into a team at some point

i will do that

need tsc approval
@rawlingsj can you please rebase your pr? thanks

can you please rebase your pr? thanks

sure thing - all done, thanks.

will need another rebase :)

will need another rebase :)

done :)


Help: Death anims

Describe your bug here.
So i made my character, wrote the script and all, but the death animation doesn't work. Help?
Script:
function onCreate()
	setPropertyFromClass('GameOverSubstate', 'characterName', 'tailsdead');
end

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
mods folder

Provide files and explain what doesn't work

It just plays the animation of BF, not my animation.
tailsdead.txt
there, the .json of the character and idk if i need to send anything more

if the character doesn't change it means something in your script is causing problems or the character name is wrong
send the full script you're using, and make sure your files are in the right folder and have the correct names

script:
function onCreatePost()
    setProperty('gf.alpha', 0);
end

function onCreate()
	setPropertyFromClass('GameOverSubstate', 'characterName', 'tailsdead');
end

The character is in the mods/characters folder.

you need to use .lua not .txt


Feature: add config option for scale to zero (enable faasIdler)

Expected Behaviour

The user should set a new flag in init.yaml called scale_to_zero or similar.
https://github.com/openfaas/faas-netes/tree/master/chart/openfaas#configuration
Current Behaviour

Users can update this manually.
Possible Solution

This should be passed through to https://github.com/openfaas-incubator/ofc-bootstrap/blob/master/scripts/install-openfaas.sh#L6 where it can be passed into the faasIdler.dryRun flag of the helm chart.
If scale_to_zero is enabled, then dryRun takes the inverse i.e. false.
Add scale_to_zero as false in init.yaml.
Steps to Reproduce (for bugs)

When complete here's the acceptance criteria:

User can set scale_from_zero: true in init.yaml
kubectl describe faas-idler -n openfaas shows dryRun is set to false.
User then sets scale_from_zero: false in init.yaml OR comments out the line
kubectl describe faas-idler -n openfaas shows dryRun is set to true.

Context

This could add efficiency savings to OpenFaaS Cloud operators

Similar closed / completed PR: https://github.com/openfaas-incubator/ofc-bootstrap/pull/95

I can pick this up 👍

Derek assign: me

Thanks @matipan

I completely forgot about this. I'm starting it now :+1:


make build-image fail

Description of problem
When I  execute make build-image, I got an error.
Step 7/20 : RUN curl -fkL https://storage.googleapis.com/golang/go${GO_VERSION}.linux-$(arch).tar.gz    | tar -zxC /usr/local/
 ---> Running in 4e6434b2fdc5
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found

Cause
In agent/Dockerfile, we can find ${GO_VERSION} is 1.9.2. But $(arch) is to execute arch command. On a x86_64 machine,  $(arch) 's result is x86_64 in a CentOS container. So the URL will be "https://storage.googleapis.com/golang/go1.9.2.linux-x86_64.tar.gz". This is unreachable.
What we need is "https://storage.googleapis.com/golang/go1.9.2.linux-amd64.tar.gz".
The value of arch should be amd64 which is getting by go env GOARCH and this is already pass to Dockerfile by ARG arch.
Solution
So we should change $(arch) to ${arch}

I have create a PR #336 .

Got an new error:
protoc-gen-gogofast: program not found or is not executable
--gogofast_out: protoc-gen-gogofast: Plugin failed with status code 1.
make: *** [proto] Error 1

We should add protoc-gen-gogofast  to GOPATH. Update in PR #336 .


htop graphs are garbled in Konsole

Issue description

Steps to reproduce

Open Konsole (stand alone app or in a kpart such as yakuake)
Run htop

Result is bad with low CPU load, it's even worse with high load.
Using font Inconsolata (probably not related, after updating it had a variable width font)
Technical details

System: 18.03pre118631.66b63d2f5a (Impala)
Nix version: nix-env (Nix) 1.11.15
Nixpkgs version: 18.03pre119086.737b466031
Sandboxing enabled: no

I cannot reproduce your problem with current master (5adec8d6c18fb24d002bf055ac3e0805146f4caa). Do you still have the problem?

For several reasons I had to stop using NixOS, so unfortunately I don't know if it still happened. I guess this issue can be closed.