Feature Request: Weighted Ordering of potential imports

Weighted Ordering of potential imports
Currently potential imports are listed alphabetically

I would like an option of change the weight of the results.
imo a better solution would be:
Priority 1 => Exact name matches
When there are multiple exact name matches:
Priority 2 => Most similar file paths
e.g. from my screenshot
Current file: \src\client\js\lobby\lobbyEmitter.ts => Importing IClientToServer
Exact results:
\src\common\lobby\IClientToServer.ts <= This one has most similar file path
\src\common\login\IClientToServer.ts
Reason
Less user actions to get the correct import. I just want to press enter, not type or search a list.

it's a good purposal but very hard to achieve ;-)

I just realized I was using resolve.addImport instead of resolve.addImportUnderCursor, which works much better for what I wanted. 👍


ERROR: ffmpeg exited with code 1

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2020.05.03
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log
C:\Users\Esme\Videos\DD\YY>youtube-dl https://www.mewatch.sg/en/series/suamiku-mr-blind/ep1/928771
[toggle] 928771: Downloading video page
[toggle] 928771: Downloading video info json
[toggle] 928771: Downloading SS_Web ISM manifest
[toggle] 928771: Downloading SS_TV ISM manifest
[toggle] 928771: Downloading DASH_Mobile MPD manifest
[toggle] 928771: Downloading DASH_Web MPD manifest
[toggle] 928771: Downloading DASH_TV MPD manifest
[toggle] 928771: Downloading HLS_Mobile m3u8 information
[toggle] 928771: Downloading HLS_Web m3u8 information
[toggle] 928771: Downloading HLS_TV m3u8 information
[toggle] 928771: Downloading DASH_Tablet MPD manifest
[toggle] 928771: Downloading HLS_Tablet m3u8 information
[toggle] 928771: Downloading DASH_HBBTV MPD manifest
WARNING: Failed to download DASH_HBBTV MPD manifest: HTTP Error 404: Not Found
[toggle] 928771: Downloading DASH_TV_4K MPD manifest
[download] Destination: Suamiku Mr Blind-928771.mp4
ffmpeg version git-2020-05-04-5767a2e Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 9.3.1 (GCC) 20200328
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
libavutil      56. 43.100 / 56. 43.100
libavcodec     58. 82.100 / 58. 82.100
libavformat    58. 42.102 / 58. 42.102
libavdevice    58.  9.103 / 58.  9.103
libavfilter     7. 80.100 /  7. 80.100
libswscale      5.  6.101 /  5.  6.101
libswresample   3.  6.100 /  3.  6.100
libpostproc    55.  6.100 / 55.  6.100
[hls @ 0000015f5a4abdc0] Skip ('#EXT-X-ALLOW-CACHE:YES')
[hls @ 0000015f5a4abdc0] Skip ('#EXT-X-VERSION:5')
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 1 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 2 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 3 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 4 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 5 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 6 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 7 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 8 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 9 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 10 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 11 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 12 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 13 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 14 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 15 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 16 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 17 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 18 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 19 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 20 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 21 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 22 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 23 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 24 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 25 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 26 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 27 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 28 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 29 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 30 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 31 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 32 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 33 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 34 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 35 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 36 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 37 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 38 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 39 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 40 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 41 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 42 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 43 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 44 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 45 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 46 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 47 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 48 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 49 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 50 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 51 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 52 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 53 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 54 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 55 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 56 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 57 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 58 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 59 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 60 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 61 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 62 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 63 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 64 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 65 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 66 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 67 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 68 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 69 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 70 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 71 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 72 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 73 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 74 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 75 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 76 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 77 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 78 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 79 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 80 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 81 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 82 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 83 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 84 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 85 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 86 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 87 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 88 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 89 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 90 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 91 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 92 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 93 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 94 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 95 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 96 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 97 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 98 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 99 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 100 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 101 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 102 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 103 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 104 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 105 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 106 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 107 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 108 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 109 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 110 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 111 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 112 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 113 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 114 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 115 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 116 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 117 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 118 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 119 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 120 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 121 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 122 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 123 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 124 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 125 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 126 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 127 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 128 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 129 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 130 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 131 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 132 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 133 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 134 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 135 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 136 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 137 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 138 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 139 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 140 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 141 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 142 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 143 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 144 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 145 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 146 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 147 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 148 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 149 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 150 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 151 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 152 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 153 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 154 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 155 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 156 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 157 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 158 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 159 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 160 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 161 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 162 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 163 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 164 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 165 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 166 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 167 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 168 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 169 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 170 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 171 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 172 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 173 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 174 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 175 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 176 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 177 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 178 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 179 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 180 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 181 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 182 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 183 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 184 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 185 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 186 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 187 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 188 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 189 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 190 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 191 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 192 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 193 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 194 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 195 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 196 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 197 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 198 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 199 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 200 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 201 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 202 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 203 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 204 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 205 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 206 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 207 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 208 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 209 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 210 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 211 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 212 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 213 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 214 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 215 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 216 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 217 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 218 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 219 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 220 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 221 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 222 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 223 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 224 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 225 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 226 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 227 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 228 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 229 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 230 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 231 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 232 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 233 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 234 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 235 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 236 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 237 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 238 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 239 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 240 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 241 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 242 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 243 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 244 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 245 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 246 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 247 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 248 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 249 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 250 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 251 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 252 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 253 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 254 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 255 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 256 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 257 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 258 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 259 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 260 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 261 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 262 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 263 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 264 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 265 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 266 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 267 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 268 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 269 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 270 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 271 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 272 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 273 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 274 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 275 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 276 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 277 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 278 of playlist 0
[hls @ 0000015f5a4abdc0] SAMPLE-AES encryption is not supported yet
[hls @ 0000015f5a4abdc0] Failed to open segment 279 of playlist 0
[hls @ 0000015f5a4abdc0] Error when loading first segment 'https://k-toggle.akamaized.net/fpshls/p/2082311/sp/208231100/serveFlavor/entryId/0_0l4n6rfp/v/2/pv/1/ev/15/flavorId/0_bvier6vc/name/a.mp4/seg-1-v1-a1.ts'
https://k-toggle.akamaized.net/fpshls/p/2082311/sp/208231100/serveFlavor/entryId/0_0l4n6rfp/v/2/pv/1/ev/15/flavorId/0_bvier6vc/name/a.mp4/index.m3u8: Invalid data found when processing input
ERROR: ffmpeg exited with code 1
Description
Hi, I am downloading some videos from mewatch (toggle) and everything is ok but when I try to download this https://www.mewatch.sg/en/series/suamiku-mr-blind/ep1/928771   I cant. I downloaded again the ffmpeg. Thanks

MeWatch is no longer supported? I'm getting the same issue for https://www.mewatch.sg/en/movies/i-not-stupid/953396
But someone added a PR for subtitle support on MeWatch.
https://github.com/ytdl-org/youtube-dl/pull/25898

Maybe @hueyy can confirm?

mewatch works, but many of the videos, especially movies and external content are DRM protected. This (https://www.mewatch.sg/en/series/we-the-citizens/ep1/655887), for instance, works perfectly.

Oh I see. Thanks for the reply.


A CMSIS-DAP clone has typo in USB product string

I have a popular DAP link (purchased in the UK) that has a typo in the product string which makes it unrecognized by default (even with the current develop branch).
By adding DAP_LINK to the KNOWN_DEVICE_STRINGS (the typo is _ instead of -), it is recognized.
I attach the results of lsusb -v -d c251:f001 to show the issue.
lsusb.txt
With this fix the results are now:
#   Probe/Board                  Unique ID      Target
----------------------------------------------------------
  0   CMSIS-DAP by ARM CMSIS_DAP<PHONE_NUMBER>01   n/a

Thanks

Interesting, thanks. And thanks for providing the lsusb output! That's a big help.
Do you have more information about the device? Like a link to where you purchased it? Just curious. We haven't seen this one before.
Also, did you have to add DAP_LINK or CMSIS_DAP to the known device strings list? In the issue description you said you added DAP_LINK, but the lsusb output shows CMSIS_DAP for the iProduct string, so I want to make sure I get it right since I can't directly test.

Thanks! 😄

Closing now the fix is merged to develop.

I bought the same device from eBay as well.
In case anyone has an issue getting this to work, you will need to install the prerelease version from the HEAD of the develop branch.
@wolfmanjm Thanks - saves a lot of trouble troubleshooting why it doesn't work.
The stable version (0.34.2) does not work (eg device c251:f001 is not detected) while 0.34.3.dev18 detects the debugger.


Updates for recent changes to JEDI-MPAS develop branches

Description
Updates MPAS-Workflow to use the latest develop branches of the source code repos.  There are two primary changes:

Localization files were re-generated externally and their locations are updated under config/mpas/*/mesh.csh
The 120km static B files are updated under config/applicationBase/3dvar.yaml
All YAML dates are updated to use generic substitution strings instead of 2018-04-15_00 (in various formats).  A benefit of this approach is that file names that already have a date in them (e.g., /glade/scratch/bjung/pandac/20220218_develop/CMAT_00.tune/mpas.stddev.2018-04-15_00.00.00.nc used for the static B) will not have the date replaced via sed substitution.
The members section of the 3denvar applications is replaced with members from template, which is more compact and much easier to read for EDA applications with self-exclusion

Tests completed

WarmStart

[x] OIE120km 3dvar, 2 cycles
[x] OIE120km 3denvar, 2 cycles
[x] OIE120km eda_3denvar, 2 cycles
[x] O30kmIE60km 3denvar, 2 cycles

ColdStart

[x] OIE120km 3dvar, 2 cycles, PreprocessObs=True

I'm going to force merge this in order to get the workflow up-to-date with develop code.  The changes are extensively tested.


Debug command with runtimeVersion not waiting for terminal load

VS Code Version: 1.76.2 (latest)
OS Version: MAC OS 13.2.1 (Ventura)

Steps to Reproduce:

add vscode launch command

{
      "type": "node",
      "request": "launch",
      "name": "Test",
      "runtimeVersion": "18",
      "program": "${workspaceFolder}/node_modules/.bin/jest",
      "console": "integratedTerminal",
    },

also I use zsh with oh-my-szh
inside .zshrc I autoset node version using nvm preload script

# Auto load .nvmrc file
# place this after nvm initialization!
autoload -U add-zsh-hook
load-nvmrc() {
  local node_version="$(nvm version)"
  local nvmrc_path="$(nvm_find_nvmrc)"

  if [ -n "$nvmrc_path" ]; then
    local nvmrc_node_version=$(nvm version "$(cat "${nvmrc_path}")")

    if [ "$nvmrc_node_version" = "N/A" ]; then
      nvm install
    elif [ "$nvmrc_node_version" != "$node_version" ]; then
      nvm use
    fi
  elif [ "$node_version" != "$(nvm version default)" ]; then
    echo "Reverting to nvm default version"
    nvm use default
  fi
}
add-zsh-hook chpwd load-nvmrc
load-nvmrc

it works fine and each time when I open projects it's auto load node version

Error
but when I run Test debug command using integratedTerminal it is somehow not waiting until the terminal is loaded. so it mixed the script code with nvm switching info

It just can't start the debugger =(
How it works
When I run debug command without   "console": "integratedTerminal", then it works.
Also, it works if I comment preload nvm script  inside .zshrc (doesn't looks like a good solution)
Looks like debug command can't wait until zsh finishes hooks and I guess we should somehow fix it

I also wouldn't expect the echo to cause any problems, my guess is nvm is swallowing some input. Currently for new terminals they are given 1 second to initialize so you could maybe speed up start up to get it to work again? Though my experience with nvm is it's really slow.
I don't think there is anything we can do apart from debug to use some shell integration hooks for when the shell is initialized, that's a bigger feature though and depends https://github.com/microsoft/vscode/issues/145234


RFC: field name translations

Been thinking of ways that assert_values_for doesn't quite reduce effort and one of the more common places is when the two map-likes (map, struct, ecto schema) have different names for the fields, but the data is the same. An example might be when a database struct, Thing, has an id field, but a system event might call it something like thing_id.
As with the list assertions, I think the biggest challenge is the api/dsl to make it clear to someone unfamiliar with the library what is going on.
The fields list will need to be the source for the starting key. But then, is it assumed that the fields passed to fields are always a match to the fields on expected? If so, I think we could possibly get away with a less verbose, more implicit dsl, but I'm not sure that that is always the case. If not, we should be more explicit.
Here is a sketch of what it could look like. I would love feedback or ideas that aren't presented here at all.
      assert_values_for(
        expected: quote_request,
        actual: quote,
        fields: fields_for(OmniWeb.Schema.QuoteRequest),
        field_name_translations: [
          # explicit
          origin_postal_code: [actual: :origin_zip],
          destination_postal_code: [expected: :destination_zip, actual: :destination_zipcode],
          # implicit
          pieces: :freight_pieces, # assumes field is from expected and that this is on actual?
          weight: :freight_weight
        ],
        skip_fields: [
          :selected_common_pickup_accessorials
        ]
      )

I have requested @GeoffreyPS also weigh in.

I'm trying to think of edge cases but I'm not sure if they are able to be encountered or real problems:

Name collisions
I don't think this is an issue since the mapping is provided

It's possible to have multiple instances of the same entry in keyword lists
Determining a last-one-wins or first-one-wins default should be sufficient, but maybe that should generate a warning.

How this interacts with #39
I think one would have to assume that the list of key-value structures/map-likes would be the same in nature (e.g., a list of exclusively users or  exclusively addresses) and not a list of multiple kinds of entities.


Can't take working SSO via SAML2.0 on AD FS

Hello.
What Relying party SAML 2.0 SSO service URL must i use to make it works?
In Docs it is <GLPI home path>/plugins/phpsaml/front/acs.php, but with this URL SSO with my AD FS not working.

Still have no solution for this problem...
Also start to get error messages on ADFS log:
"Log Name:      AD FS Tracing/Debug
Source:        AD FS Tracing
Date:          05.12.2022 9:47:57
Event ID:      153
Task Category: None
Level:         Error
Keywords:      ADFSPassivePipeline
User:          RS\stsaccount$
Computer:      adfssrv1.russian.space
Description:
Exception: MSIS7007: The requested relying party trust 'http://glpi.russian.space/' is unspecified or unsupported. If a relying party trust was specified, it is possible that you do not have permission to access the trust relying party. Contact your administrator for details.
StackTrace:    at Microsoft.IdentityServer.Web.Protocols.Saml.SamlSignInContext.ValidateCore()
at Microsoft.IdentityServer.Web.Protocols.ProtocolContext.Validate()
at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.GetRequiredPipelineBehaviors(ProtocolContext pContext)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)
Event Xml:

153
0
2
0
0
0x8000000004000000

12

AD FS Tracing/Debug
adfssrv1.russian.space

Exception: MSIS7007: The requested relying party trust 'http://glpi.russian.space/' is unspecified or unsupported. If a relying party trust was specified, it is possible that you do not have permission to access the trust relying party. Contact your administrator for details.
StackTrace:    at Microsoft.IdentityServer.Web.Protocols.Saml.SamlSignInContext.ValidateCore()
at Microsoft.IdentityServer.Web.Protocols.ProtocolContext.Validate()
at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.GetRequiredPipelineBehaviors(ProtocolContext pContext)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)

"


test: fix some flakes that might relate to #5104.

Need to be prepared to handle disconnection when resetting the server in
HttpIntegrationTest::testRouterHeaderOnlyRequestAndResponse.

HttpIntegrationTest::testUpstreamDisconnectWithTwoRequests was racy. It was possible before for
both requests to be load balanced and sent to the first upstream connection. When the 200
for the first request is received, we would then disconnect the upstream. This would then 503
back. Not sure if we've lost some coverage by these changes; the alternative might be to configure
retries?

Risk Level: Low
Testing: 1k runs on internal build farm, flakes disappeared.
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

/retest

@venilnoronha FYI, it's probably interesting to leave this PR without retests, since it's intended to fix flakes; if they are still present, then that's an issue. Looks like the build issue was only with docs, which is surprising, I haven't seen that before.

@htuch is this the only possible flake, or are there other identified flakes too?


use webpack-dev-server -d --hot --inline instead of custom server

webpack-dev-server has command-line flags that can inject configuration to enable hot module replacement. This commit makes use of this instead of hardcoding them in webpack.config.js. We also don't need server.js anymore.

-d puts Webpack into development mode, which turns on the debug mode, enables source maps and path info.
--hot injects the HotModuleReplacementPlugin plugin to the configuration.
--inline injects the webpack/hot/dev-server entry point to the bundle.

Using these command line flags makes the code more clean. We don't hardcode the dev-server entry point into the bundle anymore. This makes it much easier to produce a minified and optimized build without dev-server code in place. This is as easy as invoking webpack -p.

Eh, I'd love to merge this, but people get tripped on using CLI all the time because it has oddities.
See here: https://github.com/webpack/webpack-dev-server/issues/106
I understand why you'd like this merged but I had enough negative experience debugging people's issues caused by incorrect use of CLI that I decided to suggest Node API everywhere. Since I did that, I don't get issues about that anymore.
You can try changing my mind about it though. :-)

Yeah, the CLI has some oddities. However, when preconfigured properly, it could make the starting boilerplate more lightweight. In my opinion, having to hardcode the port in two different files — that, and not being able to produce a production code without editing the config file — do not seem like a good starting point for me. That is why I made this fork and sent you this pull request.
Understandably, not everyone is a CLI ninja.
So, I think it is up to you. If you don't think that this is better, you can close this pull request (by the way, a link to my fork would be much appreciated :smiley_cat:). Otherwise, I would be very happy for you to merge this in.

In my experience real projects often need some kind of API proxies later so it's easier to have a dev server right away.
I'd link to your fork, but I can't figure out how to phrase it without confusing the user. How would they choose between CLI and Node API? They'll probably choose CLI because it seems simpler, and then go filing issues frustrated in React Hot Loader repo :-).

Maybe, you can phrase it like this :wink::
Variations
Variations of react-hot-boilerplate created by the community.

dtinth’s fork relies on vanilla webpack-dev-server CLI instead of a custom server script. Although it is more minimal, webpack-dev-server’s CLI has some oddities that may confuse beginners (see #27 for discussion).


Add configuration option for enabling notify email

If this config option is enabled, watchers of a repository will get an email on changes.

lgtm even if the CI is drunk and not reporting the status for some reason
thanks for the patch :)


The Quick Return sample is broken on API 25

STR:

Start the sample app in Pixel emulator with API level 25.
Open ThreeTabsQRActivity. The BottomBar is way too low behind the navbar.

Strangely, after clicking a tab, the bar jumps to a correct place and then everything works normally.

@roughike i know what it is, i removed a "requestLayout()" that was causing a log message saying that we caused multiple passes of the layout phase, but, this appears to have broken that scenario


An "Appsody Flow" diagram would really help

A picture tells a 1000 words....and one that shows the flow from appsody init -> deploy would be a useful additional to the overview.

I think we have a rough flowchart somewhere in a box note... @neeraj-laad? Could do with some updating though.

I was thinking of something a bit more "pretty"....see PR...

Yes, I'd like to get a prettier picture over, perhaps get the designers involved in creating that for us.

@ddunn2 please can you work with Melissa on this, as I do think that this would be a useful addition to the website?

@helenmasters @ddunn2 @neeraj-laad So I proposed an actual diagram in the PR addressing this issue (https://github.com/appsody/website/pull/274) but totally happy if an alternative would be better.

Unless I'm missing something within the website, Images within Markdown currently won't work. I've cloned your branch and tested this, the image doesn't load within the website.
It seems the Markdown plugin the website uses doesn't handle images by default so if we're looking to add images to the docs (which I think is a great idea) then this is an issue that needs addressing.
As for the image itself we should certainly try to make it prettier :). I'll see if we can get some help with that.

Ah, hmm, yes that is a problem (although I think there are other .png images display already by the website - so maybe I didn't put it in the right place :-) ).
FYI, when I said "make it prettier", the diagram I included was created from scratch as an attempt to "be pretty" :-). However, I'm no great diagram maker...so happy for someone to improve on it if it needs it!

Reopening this issue as we need to:

fix the website (gatsby plugins etc) to be able to display the image
get designers review / amend / prettify the flow diagram

I've just enabled images in Markdown on another website I'm working on, so I'll look at porting that fix over to the Appsody site soon.
We should also consider adding guidelines around how contributors would add/edit the docs.

@ddunn2 now that we have this capability, Can we please re-implement #274 ?

Closing this issue as we have the image for flow diagram on our website now


Would like an example of testing for Landscape in a widget test

@sethladd asked me how difficult it was to test landscape layouts in tests.  I suspect it's straightforward to do, but I'm not aware of an example to give.

In practice all tests are landscape.  :-)

It seems like we will want to explain to individuals in flutter.io/testing how to test landscape vs. portrait for their widgets (as well as layouts at different sizes).  For our own widgets, coverage will tell us if we're testing the landscape vs. portrait configurations of course. e.g. https://coveralls.io/builds/11679479/source?filename=lib%2Fsrc%2Fmaterial%2Fdate_picker.dart#L101 (I'm not actually sure if that's telling me the portrait code is covered or not).

Indeed. Where's a good place to put this information? API docs? Where?

Presumably https://flutter.io/testing?

Related SO question https://stackoverflow.com/questions/50158364/in-flutter-widget-testing-how-to-make-media-orientation-to-portrait

Probably a better way (not tested, wasn't aware of that before) https://stackoverflow.com/questions/53706569/how-to-test-flutter-widgets-on-different-screen-sizes

Issue moved to flutter/website #2005 via ZenHub

This works just fine for me:
const double PORTRAIT_WIDTH = 400.0;
const double PORTRAIT_HEIGHT = 800.0;
const double LANDSCAPE_WIDTH = PORTRAIT_HEIGHT;
const double LANDSCAPE_HEIGHT = PORTRAIT_WIDTH;

final TestWidgetsFlutterBinding binding = TestWidgetsFlutterBinding.ensureInitialized();

await binding.setSurfaceSize(Size(PORTRAIT_WIDTH, PORTRAIT_HEIGHT));
await tester.pumpWidget(MyWidget());

// test in portrait

await binding.setSurfaceSize(Size(LANDSCAPE_WIDTH, LANDSCAPE_HEIGHT));
await tester.pumpAndSettle();

// OrientationBuilder gets triggered

// test in landscape


Added a Youtube Channel and a book.

Book - Android Development
Youtube Channel - The Complete Android Development Course

Thank you for the Pull Request!
The amazon link gives a 404 error.
The YouTube channel does not have up to date and promising content for Android Kotlin.
Please join the Discord server where we discuss open-source, android dev, and content creation. Invite link - https://discord.gg/vBnEhuC

Added Book -> Android Cookbook
Added Video Course -> The Complete Android N Developer Course
Removed Youtube Channel -> Android Developer


Update: Project Aurras - MVP - Phase 2

Update #814

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

Thanks a lot for the amendment. Could you also update the original timeline/estimated duration?

Sure, I have updated. Thank you.

Thanks, but could you also update the estimated duration (in time, not just person days) or just add an estimated delivery date to each milestone? It's not clear when you want to deliver the first milestone since it still says 30 working days.

Sure @alxs , I will update the application with the estimated delivery date

@MuhammedIrfan feel free to ping me once it's updated.

@MuhammedIrfan feel free to ping me once it's updated.

I have updated. Kindly review.


Net::ReadTimeout in SabisuRails::ExplorerController#index

Hey everybody. I got a error when i try to make api on raill follow this book http://apionrails.icalialabs.com/book/ Please help me.
And I found the same roblem at issues #30  but It closed with no solution. So what going on with this errors.

Hi @pdkproitf ,
What is the version of Rails you are using?

I using rails 5.

I have not tested yet with Rails 5, I can give it a spin on the weekend, but for what I can see it has to do with a dependency from the gem, how does your initializer look like?

I have the same problem with rails 4.0.2
this is my routes.rb
Rails.application.routes.draw do
  mount SabisuRails::Engine => "/sabisu_rails"
	namespace :api, defaults: { format: :json } do
		namespace :v1 do
			devise_for :users
			resources :users, :only => [:show, :create, :update, :destroy]
		end
	end
end

this is my sabisu_rails.rb
# Use this module to configure the sabisu available options

SabisuRails.setup do |config|

  # Base uri for posting the
  config.base_api_uri = 'localhost:3000'

  # Ignored attributes for building the forms
  # config.ignored_attributes = %w{ created_at updated_at id }

  # HTTP methods
  # config.http_methods = %w{ GET POST PUT DELETE PATCH }

  # Headers to include on each request
  #
  # You can configure the api headers fairly easy by just adding the correct headers
  # config.api_headers = { "Accept" => "application/json,application/vnd.application.v1" }
  #
  # config.api_headers = {}

  # Layout configuration
  # config.layout = "sabisu"

  # Resources on the api
  # config.resources = [:products, :users...]
  config.resources = [:users]

  # Default resource
  config.default_resource = 'users'

  # Application name
  # mattr_accessor :app_name
  # @@app_name = Rails.application.class.parent_name

  # Authentication
  # mattr_accessor :authentication_username
  # @@authentication_username = "admin"

  # mattr_accessor :authentication_password
  # @@authentication_password = "sekret"

end


[INTEL MKL] DNN 0.x code cleanup - Fused Matmul op

This PR replaces the old one https://github.com/tensorflow/tensorflow/pull/45564 (which is not approved/merged),
DNN 0.x cleanup of Fused Matmul op:
(1) Remove all DNN 0.x related code;
(2) Replace all DNN 1.x macro usages
And minor change in quantized op (macro replacement in a couple of places)

@gzmkl Can you please resolve conflicts? Thanks!

@gbaned  I have addressed the merge conflict issues. thank you!

@gbaned  I have addressed the merge conflict issues. thank you!


[Renewed] Refactor preprocessor architecture to enhance extensibility

Addresses parts of #672
Preparing to add a airflow as a preprocessor target, I noticed that the current architecture is very rigid and difficult to expand upon. This refactoring/reorganization hopefully addresses some of these. Notable changes (and absence of changes) are
No AST traversal or transformation logic has been rewritten
Files outside of shell_ast have not been changed*
preprocess/preprocess.py has been changed, but simply to import new files (some new modules were made, as I discuss below).
Differing behavior depending on target (vanilla, spec, airflow) is no longer handled by an if statement in ast_to_ast.
Previously, replace_df_regions was a function that ran a if statement on a property of TransformationState to check which specific TransformationState implementation we were dealing with (this would tell us the output target). Now, replace_df_regions is an instance method of AbstractTransformationState. This means that any variation in AST transformation between different output targets can be addressed in a single class that implements of AbstractTransformationState.
The location of the AST Transformation logic has been moved from replace_df_regions() to a method on TransformationState.
For example, this pull request created three implementations of AbstractTransformationState: TransformationState for the vanilla pash behavior, SpeculativeTransformationState for pash spec, and AirflowTransformationState for airflow (this one is empty). The ast_to_ast package contains no checks in its logic for checking how to handle AST transformations - they only need to call replace_df_regions of whatever trans_options argument they have at hand.
The TransformationState code has been moved to a separate file transformation_options.py. I do suggest renaming "State" with some more appropriate name, but this is a minor nitpick
preprocess_node_<node_type> functions have been

moved to its own module
no longer reliant on a large dictionary to dispatch the appropriate function
type-annotated.

This looks great to me!

Closes #672


PHP automatic instrumentation docs do not install everything they claim to

I am not super experienced with PHP so I may be missing something here.
What needs to be changed?
The PHP autoinstrumentation page (https://opentelemetry.io/docs/instrumentation/php/automatic/#supported-libraries-and-frameworks) says

Automatic Instrumentation comes with a number of instrumentation libraries for commonly used PHP libraries. For the full list, see instrumentation libraries on packagist.

However, the instructions in the page only install the opentelemetry.so extension which provides the hooking mechanism. I don't think this installs any of the API, SDK, exporters, instrumentations, etc. For example, the example immediately after the installation instructions does not work.
What is the name + path of the page that needs changed?
docs/instrumentation/php/automatic/#supported-libraries-and-frameworks
Additional context: anything else you can think about that would be helpful.

is this still valid, @aabmass @open-telemetry/php-approvers ?

I'm not sure I'll defer to PHP folks, or we can just stale close this as it doesn't have any +1's in over a year

I believe this is fixed.


How would you trigger a select element?

<select @change="onSelect($event.target.value)">
  <option v-for="option in options" :value="option.value" :key="option.value">{{option.label}}</option>
</select>

I am passing in the options through propsData just fine in my first test.
Next, I want to trigger a change on the select and choose the second one in the list which will trigger the change event and pass the value to a method I have. I cant find an example of how to do that.

wrapper.findAll('option').at(1).trigger('change')

Further questions like this should be asked at StackOverflow.

For me this works fine when running it on Chrome, but with PhantomJS the event doesn't seem to get emitted. In other words, wrapper.emitted().input[0] would be undefined.
My work around was to do things manually with raw JavaScript:
const select = wrapper.find('select').element
select.value = 'myValue'
select.dispatchEvent(new Event('change'))

Could this be a bug?

Potentially, would you be able to add a failing test and a fix?

"Potentially" is a very broad word :)
Let me start with something smaller, to see if this makes sense, and then maybe you can guide me into converting it into a real PR. Check this proof of concept, that tries to replicate my original scenario.
https://github.com/ariera/vue-test-utils/commit/8e7d5243ad5fdc0036f840981326433033ff5837
Does that make sense to you? Am I doing something obviously wrong (in terms of using the library)? Is this a bug on vue-test-utils or rather an issue on PhantomJS?

Thanks for this. It looks like a difference between how Chrome and phantom propagate events.
I'm not sure it's a bug, as I believe you can solve your issue by calling .trigger on the select wrapper.
Maybe we should reintroduce phantom as a test runner to avoid broken tests in phantom 🤔

I'm having the same problem using the mocha-webpack testrunner and JSDOM as described in the docs.


validate: add rust validate code

currently, wagon validate module is far from mature, so add rust validation for backup.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1478f4b). Click here to learn what that means.
The diff coverage is 52.63%.

@@            Coverage Diff            @@
##             master      #13   +/-   ##
=========================================
  Coverage          ?   46.16%
=========================================
  Files             ?       39
  Lines             ?     3754
  Branches          ?        0
=========================================
  Hits              ?     1733
  Misses            ?     1743
  Partials          ?      278

Impacted Files
Coverage Δ

validate/validate_code.go
60% <ø> (ø)

wasm/types.go
45.83% <ø> (ø)

validate/validate.go
7.84% <52.63%> (ø)

Continue to review full report at Codecov.

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


Integrate node-problem-detector

What this PR does / why we need it: This PR integrates node-problem-detector in Gardener as a shoot-core addon. The chart is inspired by the following references:

https://github.com/helm/charts/tree/master/stable/node-problem-detector
https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/node-problem-detector

Which issue(s) this PR fixes:
Fixes #312
Special notes for your reviewer: As it's a new component, please have a special eye on labels and other metadata to maintain homogeneity.
Release note:

Node-problem-detector is integrated into Gardener. Certain problems occured in nodes will be visible as part of `NodeConditions` or `Event`. Refer [NPD](https://github.com/kubernetes/node-problem-detector) doc for more info.

Is the node-problem-detector installed on each Shoot? What's the motivation behind it? I guess the idea was to keep addons out of gardener. g/bouquet or something else? Is it special system addon that we want to install always?
/cc @mvladev

@ialidzhikov the motivation is that there are several circumstances that render your node useless/broken without the kubelet detecting this. We ran several times into corrupt and thus read-only filesystems (the node is thus broken) but scheduler and kubelet happily trying to start one pod after the other on that broken node. Such situations needed manual interaction because of the missing problem detection.
Hence I actually cannot imagine that one wants to run a cluster without NPD :) (except however when you want to deploy/tune your own NPD).
@hardikdr: If I get it right, this PR is only about "detecting" problems, not about "acting" on them, correct? So while this will for example detect a read-only filesystem, mcm won't automagically react on it, or is there already some mcm PR to react on the problems reported by NPD?

@rfranzke thanks for reviewing.

Why is it still "WIP"?

I was testing the PR locally for a few cases, so I kept WIP. Removing now, as it's done.

did you test with setting .spec.kubernetes.allowPrivilegedContainers=false?

I haven't really, but as NPD needs to interact with system often, I assumed it'd need to be privileged-container. Though a valid point, I will quickly cross-check and update the thread.

@swapnilgm thanks for reviewing.

Instead of duplicating and maintaining NPD chart on our own, how about managing NPD dependency by adding requirements.yaml

That's a good point, we could adopt that for all the charts we consume directly from upstream, I'd generally +1 on not maintaining the code/charts separately wherever it is possible.
Although in this case, on top of APIVersion conflict you mentioned, there are few minor changes I have inside the chart as well.
Eg. In daemonset.yaml

Updating the exec command to include more monitors, using gardener friendly labels/naming-conventions and so on.

Overall I am open for suggestions and happy to fetch chart as it, with few customizations on top as mentioned above.

Hence I actually cannot imagine that one wants to run a cluster without NPD :) (except however when you want to deploy/tune your own NPD).

Then I would expect a way to disable it from spec.addons. I still miss the whole picture. NPD add new NodeConditions and MCM starts watching on them?

Instead of duplicating and maintaining NPD chart on our own, how about managing NPD dependency by adding requirements.yaml to componnets chart And adding section for NPD under values.yaml.

I don't think our chart rendering mechanism supports this.

Then I would expect a way to disable it from spec.addons. I still miss the whole picture. NPD add new NodeConditions and MCM starts watching on them?

I don't think we should allow end-users to configure it. It comes automatically with every shoot as it helps us providing a better service quality (as we now can more easily detect broken nodes and replace them). For example, the node-exporter daemonset can't be deactivated either by end-users because it's required as part of our monitoring offering.

I still miss the whole picture. NPD adds new NodeConditions and MCM starts watching on them?

Exactly!
(Side note: deploying NDP on my own is kind of hacky, because it only reports, but so far no one reacts on the problems found, hence today I have NPD deployed +an additional script in case NPD problems are found that "kills" stuff on the node, so that ultimately kubelet detects it and mcm can react...)

If I get it right, this PR is only about "detecting" problems, not about "acting" on them, correct? So while this will for example detect a read-only filesystem, mcm won't automagically react on it, or is there already some mcm PR to react on the problems reported by NPD?

Yes, that's true, we will soon be opening a PR on MCM to act on a very minimal set of NodeConditions. For now, it may be FileSystemReadOnly and KernelDeadlock. MCM will simply replace machines with such NodeConditions set to true after a configurable timeout.

Instead of duplicating and maintaining NPD chart on our own, how about managing NPD dependency by adding requirements.yaml to componnets chart And adding section for NPD under values.yaml.

I don't think our chart rendering mechanism supports this.

i was under the assumption that  our chart rendering library is wrapper over helm chart rendering so it should have supported it. Then does it makes sense to add that support in our chart rendering lib?
This way we can also force our other components like MCM, etcd-backup-restore, gardener-resource-manager, terraformer to maintain helm chart on it. and reuse it in gardener. Single point . of maintenance. Same is the case for landscape/garden-setup.

i was under the assumption that our chart rendering library is wrapper over helm chart rendering so it should have supported it. Then does it makes sense to add that support in our chart rendering lib?

Try it out, I'm not sure whether it works.

This way we can also force our other components like MCM, etcd-backup-restore, gardener-resource-manager, terraformer to maintain helm chart on it. and reuse it in gardener. Single point . of maintenance. Same is the case for landscape/garden-setup.

Yes, this would be a nice benefit, however, on the other hand I think at least some of the charts are specific to the way how gardener deploys them. Also, this also introduces a new dependency to these charts, i.e., if there is a bug/problem with such a chart then it has to first be fixed, released, and then updated in this repo. Kind of "not nice", I guess. Definitely, whatever we plan here should happen separately and is out of scope of NPD integration.

i was under the assumption that our chart rendering library is wrapper over helm chart rendering so it should have supported it. Then does it makes sense to add that support in our chart rendering lib?

Try it out, I'm not sure whether it works.

This way we can also force our other components like MCM, etcd-backup-restore, gardener-resource-manager, terraformer to maintain helm chart on it. and reuse it in gardener. Single point . of maintenance. Same is the case for landscape/garden-setup.

Yes, this would be a nice benefit, however, on the other hand I think at least some of the charts are specific to the way how gardener deploys them. Also, this also introduces a new dependency to these charts, i.e., if there is a bug/problem with such a chart then it has to first be fixed, released, and then updated in this repo. Kind of "not nice", I guess. Definitely, whatever we plan here should happen separately and is out of scope of NPD integration.

Agreed. Sorry for diverging topic from NPD.

@ialidzhikov Overall I agree with @rfranzke's comment above, we basically want to deliberately enable the NPD for all shoots, considering it adds a core service quality of identifying the problems at the node. Though we might want to think of making the impact of future-remedy-systems optional if the user would want to opt-out of certain/unusual cases, but that's far fetched.

@hardikdr mentioned that NPD does not yet work for shoots if it is configured in a way that privileged containers are not allowed. /cc @mvladev

Yes, that's true, we will soon be opening a PR on MCM to act on a very minimal set of NodeConditions. For now, it may be ReadonlyFilesystem  and KernelDeadlock. MCM will simply replace machines with such NodeConditions set to true after a configurable timeout.

This will require something like MachineDisruptionBudget, otherwise it can pull off all of the machines...

@hardikdr are PDBs respected in case multiple machines are marked with these conditions by NPD and MCM decides to take them off?

This will require something like MachineDisruptionBudget, otherwise it can pull off all of the machines...

Yes, that's a good point. We'd eventually need to introduce something similar. I would though prefer to introduce a mechanism of freezing the machineset/machinedeployment when X% [50/60] of the machines are unhealthy simultaneously.  This would indicate more of an infra-failure than actual issues with machines.

Otherwise, if machines are permanently damaged due to any of KuberneteReady, KernelPanic or ReadOnlyFilesystem since the timeout period, it's very likely that workload is also impacted and preserving such machines might not be useful anyways.

@hardikdr are PDBs respected in case multiple machines are marked with these conditions by NPD and MCM decides to take them off?

The short answer is yes, but there is more to it. We always drain the machines before deleting them, which inherently ensures that PDBs are respected by nature. Basically drain calls EvictionAPI for each pod on a machine, which avoids deleting the pods with PDBs-violated. Though we also make sure, that such machines are not forever stuck due to misuse of PDBs and delete them after a timeout period.

Tested with .spec.kubernetes.allowPrivilegedContainers=false works well now.


[Gekidou] Solidarity poc

Summary
Adds a npm pre-install script that uses the Solidarity dependency checker to ensure that all the global dependencies (Xcode, npm, react-native-cli, environment variables, etc) required to build mattermost-mobile are installed on a developer's machine. If all the required dependencies are found to be present on a developer's machine, the preinstall script passes and the npm install is allowed to proceed; if some dependencies are missing or are an incorrect version, then the npm install for mattermost-mobile is halted until the necessary dependencies are installed and correctly configured.
Ticket Link

This is a possible fix for issues such as https://github.com/mattermost/mattermost-mobile/issues/6329.
If the user is can be informed during the dependency install process that they don't have the necessary global dependencies required to build the app, considerable amounts of developer time on both ends can be saved as it avoids back-and-forths on newly reported github issues tickets that need to be solved by telling the reporter that they need to up/downgrade a different version of a dependency.
Checklist

Device Information
This PR was tested on:
Screenshots

Release Note

Added a npm pre-install script that uses Solidarity to check for required build dependencies.

Hello @ElonVolo,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

This check could save me couple hours :(

@ElonVolo thanks for bringing this to our attention and for laying the ground work for this.

No prob. 😀 I'm always happy to promote my philosophy of pro-active
synchronization and standardization of global dependencies across developer
machines, as I feel that people should spend their time actually developing
valuable and useful features for software instead of spending frustrating
days of trying to figure out why their development environment isn't
building stuff (when their coworker's strangely seems to have no issue).
I've found this approach is one of the cheapest and easiest things you can
do on a project to effectively and immediately boost developer velocity.
On Sat, Aug 20, 2022 at 9:56 AM Elias Nahum @.***>
wrote:

@ElonVolo https://github.com/ElonVolo thanks for bringing this to our
attention and for laying the ground work for this.
—
Reply to this email directly, view it on GitHub
https://github.com/mattermost/mattermost-mobile/pull/6394#issuecomment-1221319374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APE6QJX3VHWPIDDINPW4Y4TV2DPYDANCNFSM5Y77KIHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


  add group label to add person/edit person workflow

WHY?
As a first step in our group testing epic, we need to allow users to flag a patient's profile with what we're calling a 'group label'. this will allow users to start building out groups of people to eventually initiate a 'group test'
AS A user of SimpleReport
I WANT the ability to add a label to a person in the system
SO THAT I can associate that person with a group and eventually initiate a test on an entire group of patients in one step

GIVEN i have started the add person workflow or am editing an existing person
WHEN I enter a value in the 'groups' section of the person's profile and save my changes
THEN that value is not associated with that person, and any other persons that share the same value
Label Rules:

alphanumeric plus dashes en dash and spaces
no spaces allowed at beginning or end

Example Labels:
Translations

[ ] Translations are required
[ ] Translation request has been submitted
[ ] Translations have been received

whos working on this, why is it in progress?

@vz3 @tim-skylight  Do we have designs for this?

designs are not complete yet but here's the work in progress:
https://www.figma.com/file/NPSPM5SBzQ7Ra3mmr9M9cB/SimpleReport-Public-Site?node-id=6771%3A24998


fix spelling mistake

Coverage increased (+0.2%) to 66.301% when pulling 51c9c2c93a8875db726cd691a866dd2896ba4468 on scofieldpeng:master into 357bc8027655c7de867ee7186907d86214469798 on go-chassis:master.

thanks for that


refactor(master): remove redundant logging Sprintf

@Huweicai 22422fc2f715d6fd33343c6d5581e10be94477d3    Title likes <type>(<scope>): <subject>  ，commit message need be updated

@Huweicai 22422fc Title likes <type>(<scope>): <subject> ，commit message need be updated

@leonrayang Is the type 'refactor' not supported?

@leonrayang It's okay now, since I haven't signed the commit before.


Issue with transparent Navigation Buttons row

On my device with Android version 9, application contents, like notes and settings list, goes under Navigation Buttons row. I noticed various issues with other apps and Navigation Buttons in other apps too, like in Google Authenticator Navigation Buttons are invisible, so it might be a problem with platform and not with the app.

Who is the Mobille Manufacturer?

Sony.


Level Workshop and online ranking system

For if I ever get players for the game, as unlikely as that seems.

[ ] #25
[ ] #26
[ ] Account system
[ ] DB for storing custom levels
[ ] Explore section, for playing DB levels
[ ] Rating system for levels
[ ] Success rate system for levels
[ ] Sort by rating, newest, or trending (high number of plays in the last few days)
[ ] Level posting system
[ ] Require creator to solve level before posting

This is unplanned for now, as I clearly don't have time for all of this lol


Filter out DNA barcode samples from GBIF

Some records from GBIF are coming in from DNA samples (and are questionable). After downloading, in filter (or before) filter out samples that have a Basis of Observation == Material sample.

From the resulting GBIF query, want to use something like
filter(basisOfRecord != "MATERIAL_SAMPLE")

Addressed in d873d9c.


mlc notebook provided doesnt run on colab

error vocab_size not found

Which code produced this error?

please run it on google colab you will see the error

Thanks for your feedback. I find that this bug is caused by mlc-llm.
So runing_quantized_models_with_mlc_llm.ipynb can not be use until official mlc-llm fixing their bug.
I will fix this after mlc-llm fix the bug of there repo.


Crash opening file - reproducible

This has happened maybe 3 times but I didn't report earlier as I don't know how to reproduce yet.
runtime.fatalpanic at panic.go:681
runtime.gopanic at panic.go:556
runtime.panicindex at panic.go:44
github.com/goki/gide.(*Gide).ViewFileNode at gide.go:562
github.com/goki/gide.(*Gide).NextViewFileNode at gide.go:583
github.com/goki/gide.(*Gide).FileNodeOpened at gide.go:1872
github.com/goki/gide.(*Gide).ConfigSplitView.func1 at gide.go:1788
github.com/goki/ki.(*Signal).Emit at signal.go:157
github.com/goki/gi/giv.(*TreeView).Open at treeview.go:677
github.com/goki/gi/giv.(*TreeView).ToggleClose at treeview.go:685
github.com/goki/gi/giv.(*TreeView).TreeViewEvents.func5 at treeview.go:1340
github.com/goki/gi.(*WinEventRecv).Call at window.go:1423
github.com/goki/gi.(*Window).SendEventSignal at window.go:1544
github.com/goki/gi.(*Window).EventLoop at window.go:1297
runtime.goexit at asm_amd64.s:1333

yep easy fix there

Just fixed it myself and found yours when I tried to push!


Fixing IDENTITY-2923

Fix for https://wso2.org/jira/browse/IDENTITY-2923

Closing this this has replaced with another pull request


Add missing error codes to documentation

Please add the following error codes:
AADB2C90091 - user cancellation

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

ID: fd9c64ff-5065-9a2b-4965-c48685482fe1
Version Independent ID: 3ff9871f-d28d-b752-750e-1142556ec8cb
Content: Error code reference - Azure AD B2C
Content Source: articles/active-directory-b2c/error-codes.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@frankkilcommins Thank you for your inputs. We will engage the content team to have this reviewed and updated .
Thank you.

@msmimart Could you please help review this one ?


Case-insensitive ordering

Hi, is it possible to have imports ordered with case-insensitivity? If not, can I please request this as a feature?
An example: no import order specified, importing siblings "ThingsList" and "ThingView". I would like for them to listed in that order, as s comes before V. But due to case sensitivity, upper case V actually comes before lower case s, so we get:
import ThingView from './ThingView';
import ThingsList from './ThingsList';

I could try to help write this feature if it is desirable.

UPDATE: I have submitted a pull request with a suggested solution: https://github.com/trivago/prettier-plugin-sort-imports/pull/69

Hi @ayusharma, @byara - great work on this tool, it's already saving me loads of time 👍
Are you interested in adding the functionality in my PR? It's non-breaking for existing users but will enable optionally conforming to this linting option. If you'd rather not accept this change, do you mind if I publish my fork on npm under my own name?
Thanks,
Tim


⚠ ClamAV has degraded performance

In 2bab3c2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in f92400a.


bug  on merging with exisitn terraform.tfstate file

Here's the error I get when I try to merge into an existing terraform.tfstate
terraforming cwa --tfstate --merge=terraform.tfstate --profile xxxxxxx
/var/lib/gems/2.3.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:269:in tfstate': undefined method []' for nil:NilClass (NoMethodError)
from /var/lib/gems/2.3.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:250:in execute'         from /var/lib/gems/2.3.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:25:in cwa'
from /var/lib/gems/2.3.0/gems/thor-1.0.1/lib/thor/command.rb:27:in run'         from /var/lib/gems/2.3.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in invoke_command'
from /var/lib/gems/2.3.0/gems/thor-1.0.1/lib/thor.rb:392:in dispatch'         from /var/lib/gems/2.3.0/gems/thor-1.0.1/lib/thor/base.rb:485:in start'
from /var/lib/gems/2.3.0/gems/terraforming-0.18.0/bin/terraforming:5:in <top (required)>'         from /usr/local/bin/terraforming:23:in load'
from /usr/local/bin/terraforming:23:in `'

Also, I installed using gem install terraforming, here's the list of installed gems
gem list
*** LOCAL GEMS ***
aws-eventstream (1.0.3)
aws-partitions (1.259.0)
aws-sdk-autoscaling (1.30.0)
aws-sdk-cloudwatch (1.31.0)
aws-sdk-core (3.86.0)
aws-sdk-dynamodb (1.41.0)
aws-sdk-ec2 (1.129.0)
aws-sdk-efs (1.23.0)
aws-sdk-elasticache (1.29.0)
aws-sdk-elasticloadbalancing (1.19.0)
aws-sdk-elasticloadbalancingv2 (1.39.0)
aws-sdk-iam (1.32.0)
aws-sdk-kms (1.27.0)
aws-sdk-rds (1.74.0)
aws-sdk-redshift (1.35.0)
aws-sdk-route53 (1.30.0)
aws-sdk-s3 (1.60.1)
aws-sdk-sns (1.21.0)
aws-sdk-sqs (1.23.1)
aws-sigv4 (1.1.0)
bigdecimal (1.2.8)
did_you_mean (1.0.0)
io-console (0.4.5)
jmespath (1.4.0)
json (1.8.3)
minitest (5.8.4)
multi_json (1.12.2)
net-telnet (0.1.1)
power_assert (0.2.7)
psych (2.0.17)
rake (10.5.0)
rdoc (4.2.1)
terraforming (0.18.0)
test-unit (3.1.7)
thor (1.0.1)

Running into something similar here. Did you ever find a solution?
Traceback (most recent call last):
	9: from /usr/local/bin/terraforming:23:in `<main>'
	8: from /usr/local/bin/terraforming:23:in `load'
	7: from /Library/Ruby/Gems/2.6.0/gems/terraforming-0.18.0/bin/terraforming:5:in `<top (required)>'
	6: from /Library/Ruby/Gems/2.6.0/gems/thor-1.0.1/lib/thor/base.rb:485:in `start'
	5: from /Library/Ruby/Gems/2.6.0/gems/thor-1.0.1/lib/thor.rb:392:in `dispatch'
	4: from /Library/Ruby/Gems/2.6.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in `invoke_command'
	3: from /Library/Ruby/Gems/2.6.0/gems/thor-1.0.1/lib/thor/command.rb:27:in `run'
	2: from /Library/Ruby/Gems/2.6.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:120:in `iamu'
	1: from /Library/Ruby/Gems/2.6.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:250:in `execute'
/Library/Ruby/Gems/2.6.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:269:in `tfstate': undefined method `[]' for nil:NilClass (NoMethodError)

Same error here too
Traceback (most recent call last):
	9: from /usr/local/bin/terraforming:23:in `<main>'
	8: from /usr/local/bin/terraforming:23:in `load'
	7: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/bin/terraforming:5:in `<top (required)>'
	6: from /usr/lib/ruby/vendor_ruby/thor/base.rb:444:in `start'
	5: from /usr/lib/ruby/vendor_ruby/thor.rb:369:in `dispatch'
	4: from /usr/lib/ruby/vendor_ruby/thor/invocation.rb:126:in `invoke_command'
	3: from /usr/lib/ruby/vendor_ruby/thor/command.rb:27:in `run'
	2: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:215:in `vpc'
	1: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:250:in `execute'
/var/lib/gems/2.5.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:269:in `tfstate': undefined method `[]' for nil:NilClass (NoMethodError)

I am getting parse error in Multi-json thrign to merge anything.
vagrant@ubuntu1804:~/SpecialProjects/Output$ terraforming alb --tfstate --merge=.terraform.tfstate --overwrite
Traceback (most recent call last):
11: from /usr/local/bin/terraforming:23:in <main>' 	10: from /usr/local/bin/terraforming:23:in load'
9: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/bin/terraforming:5:in <top (required)>' 	 8: from /var/lib/gems/2.5.0/gems/thor-1.0.1/lib/thor/base.rb:485:in start'
7: from /var/lib/gems/2.5.0/gems/thor-1.0.1/lib/thor.rb:392:in dispatch' 	 6: from /var/lib/gems/2.5.0/gems/thor-1.0.1/lib/thor/invocation.rb:127:in invoke_command'
5: from /var/lib/gems/2.5.0/gems/thor-1.0.1/lib/thor/command.rb:27:in run' 	 4: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:15:in alb'
3: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:250:in execute' 	 2: from /var/lib/gems/2.5.0/gems/terraforming-0.18.0/lib/terraforming/cli.rb:267:in tfstate'
1: from /var/lib/gems/2.5.0/gems/multi_json-1.12.2/lib/multi_json.rb:122:in load' /var/lib/gems/2.5.0/gems/multi_json-1.12.2/lib/multi_json/adapter.rb:20:in load': JSON::ParserError (MultiJson::ParseError)

If there's no property "modules" in terraform.tfstate file, the following codes would cause NoMethodError problem.
tfstate["modules"][0]["resources"] = tfstate["modules"][0]["resources"].merge(klass.tfstate)

If there's no property "modules" in terraform.tfstate file, the following codes would cause NoMethodError problem.
tfstate["modules"][0]["resources"] = tfstate["modules"][0]["resources"].merge(klass.tfstate)


question about the \kappa in your blog and code

Hi:
Thanks for your wonderful code and method!
I used to work on compress sensing, but only with L-1 optimization. I'm unfamiliar with the half-quadratic method. I notice that the \kappa is set to 1.01 in your code. If I'm not mistaking, the \kappa acts as a Laplacian penalty argument to me. I thought that if this was the case, the \kappa should be a large parameter, that will guarantee the \beta_t to be infinite after some iterations. 1.01 seems too small for this mission in my point of view? Or the \beta_t does not need to be infinite in half-quadratic optimization?
Thanks for your code again and looking forward to the reply!

Hi @yzxyzh , thank you!
Yes, kappa after multiple iterations will make beta tend to infinity, that's why it should be strictly kappa > 1. In practice, when you set kappa close to 1, you get better quality but it requires more iterations since beta will be slowly increasing. Depending on the problem and the outliers level, you might need to set it to higher values. Since in our case iterations are very cheap, we set it to a low values to get the best quality and rely on early stopping to exit the solver.
You can also set a max beta as the exit strategy for the solver like what they do here: http://www.cse.cuhk.edu.hk/~leojia/papers/L0smooth_Siggraph_Asia2011.pdf
Hope it makes sense!


Use unbuffered output to fix printing inside the Docker.

https://stackoverflow.com/questions/29663459/python-app-does-not-print-anything-when-running-detached-in-docker

Thank you for tip and PR!


[DOC] Update .zenodo.json

Changes proposed in this pull request
Added utooley to .zenodo.json for PR #365 to niworkflows. Please feel free to reorder if necessary.

Documentation that should be reviewed
.zenodo.json

Awesome. Thanks.


[Adapter Cards-Schema Explorer]: Narrator is announcing some extra irrelevant information with the "OK button" info.

Target Platforms
Other
SDK Version
1.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
OS: Version 22H2 (OS Build 25197.1000)
Edge Dev: version 107.0.1379.1 (Official build) dev (64-bit)
Screen Reader: Narrator
Application URL: [[https://adaptivecards.io/](https://adaptivecards.io/explorer/)
Pre-Requisites:
Run the Narrator using "Control+ Windows +Enter" short key in the scan mode.
Repro Steps:
1.Open above URL with V- credential.
2.Navigate to 'Schema Explorer' link using tab key and press enter key to activate it.
3.Navigate to 'Container" link present under "Containers" from the left navigation using the tab key and activate it using Enter key.
4. Navigate to the adaptive cards present under it using the Tab key.
5. Navigate to the "Submit Action" button with tab key using narrator and activate using Enter key.
6. Observe the issue here.
Actual Result:
Narrator is announcing like "Adaptivecards.io says OK button 1of1".
Expected Result:
Narrator shouldn't give the position of the OK button as there is only one button in the comment box, and it should announce it like "Adaptivecards.io says OK button".
Oservation:
Issue exists throughtout the application wherever the "OK" button is present after submiting the adaptive cards.
User Experience:
Screen reader users will be impacted, and they will get confusion over here if narrator announces the position of the OK button.
MAS Reference:
https://liquid.microsoft.com/Web/Object/Read/ms.accessibility/Requirements/01.03.01
"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “.
Screenshots
Uploading narrator announces the position of OK button which is not applicable.mp4…
Card JSON
NA

Sample Code Language
NA
Sample Code
NA

This issue is not repro, hence closing this issue.