[Broken] Hotstar.com: ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden

Checklist

[ x] I'm reporting a broken site support
[ x] I've verified that I'm running yt-dlp version 2021.06.09
[ 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

PASTE VERBOSE LOG HERE:

Log-1:

yt-dlp -Fv https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304
[debug] Command-line config: ['-Fv', 'https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] yt-dlp version 2021.06.09
[debug] Python version 3.9.5 (CPython 64bit) - Linux-5.13.0-051300rc5-generic-x86_64-with-glibc2.33
[debug] exe versions: ffmpeg 4.3.2-0, ffprobe 4.3.2-0, phantomjs 2.1.1, rtmpdump 2.4
[debug] Proxy map: {}
[debug] [hotstar] Extracting URL: https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304
[hotstar]<PHONE_NUMBER>: Downloading webpage
[hotstar]<PHONE_NUMBER>: Downloading token
ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by <HTTPError 403: 'Forbidden'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
  File "/home/admn/.local/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 678, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/home/admn/.local/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 3071, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/usr/lib/python3.9/urllib/request.py", line 561, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

Log-2:

yt-dlp -fv 'dash-video_avc1_8+dash-audio_only-und-mp4a-2-0' --merge-output-format mp4 https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304
ERROR: 'dash-video_avc1_8+dash-audio_only-und-mp4a-2-0' is not a valid URL. Set --default-search "ytsearch" (or run  yt-dlp "ytsearch:dash-video_avc1_8+dash-audio_only-und-mp4a-2-0" ) to search YouTube
[hotstar]<PHONE_NUMBER>: Downloading webpage
[hotstar]<PHONE_NUMBER>: Downloading token
ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden (caused by <HTTPError 403: 'Forbidden'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.

Description

WRITE DESCRIPTION HERE:
yt-dlp used to work on Hotstar.com like a week ago, now I'm getting this:
ERROR: Unable to download JSON metadata: HTTP Error 403: Forbidden

I have tried few different videos from:
(1) Yeh Rishta Kya Kehlata Hai:
Series link:
https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586#!

and

(2) Saath Nibhaana Saathiya 2:
Series link:
https://www.hotstar.com/in/tv/saath-nibhaana-saathiya/693#!

Direct video (episode) link as an example:

https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304

but getting same error on every link I've tried. The same video does play just fine in browsers (Microsoft Edge for Linux and Chromium).
Thank you so much for yt-dlp.
OS: Ubuntu MATE 21.04
yt-dlp version: 2021.06.09

Works for me. Are you in India? are you using VPN? Also check if your PC's time is correct since the API authentication is time based
yt-dlp "https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304" -vF --no-warn
[debug] Command-line config: ['https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304', '-vF', '--no-warn']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.06.09 (source)
[debug] Plugin Extractors: ['SamplePlugin']
[debug] Git HEAD: 0181adefc6
[debug] Python version 3.9.2 (CPython 64bit) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 2021-04-11-git-309e3cc15c-full_build-www.gyan.dev, ffprobe 2021-04-11-git-309e3cc15c-full_build-www.gyan.dev, phantomjs 2.1.1
[debug] Proxy map: {}
[debug] [hotstar] Extracting URL: https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304
[hotstar]<PHONE_NUMBER>: Downloading webpage
[hotstar]<PHONE_NUMBER>: Downloading token
[hotstar]<PHONE_NUMBER>: Downloading JSON metadata
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, vcodec:vp9.2(10), acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[info] Available formats for<PHONE_NUMBER>:
ID                           EXT RESOLUTION FPS |   TBR PROTO  | VCODEC             VBR ACODEC     ABR  ASR    NOTE
---------------------------- --- ---------- --- - ----- ------ - ---------------- ----- --------- ---- ------- -----------------------------
hls-audio_mp4a_129-Unknown-0 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_129-Unknown-1 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_129-Unknown-2 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_129-Unknown-3 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-0  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-1  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-2  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-3  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-4  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-5  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-6  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-7  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-0  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-1  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-2  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-3  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-4  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-5  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-6  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-7  mp4 audio only     |       m3u8_n |                        unknown                [und]
dash-audio_und_mp4a_1-0      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_1-1      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_1-2      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_1-3      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-0 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-1 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-2 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-3 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-0      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-1      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-2      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-3      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-0 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-1 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-2 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-3 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_3-0      m4a audio only     |  129k dash   |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_3-1      m4a audio only     |  129k dash   |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-3-0 m4a audio only     |  129k https  |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-3-1 m4a audio only     |  129k https  |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
hls-130-0                    mp4 320x180        |  130k m3u8_n | avc1.42C00C       130k
hls-130-1                    mp4 320x180        |  130k m3u8_n | avc1.42C00C       130k
hls-177                      mp4 320x180        |  177k m3u8_n | avc1.42C00C       177k mp4a.40.2   0k
hls-120-0                    mp4 320x180        |  120k m3u8_n | hvc1.1.6.L60.90   120k
hls-120-1                    mp4 320x180        |  120k m3u8_n | hvc1.1.6.L60.90   120k
dash-video_avc1_1            mp4 320x180    25  |  114k dash   | avc1.42C00C       114k                        DASH video, mp4_dash
dash-video-avc1-1            mp4 320x180    25  |  114k https  | avc1.42C00C       114k                        DASH video, mp4_dash
dash-video_hvc1_1            mp4 320x180    25  |  104k dash   | hvc1.1.6.L60.90   104k                        DASH video, mp4_dash
dash-video-hvc1-1            mp4 320x180    25  |  104k https  | hvc1.1.6.L60.90   104k                        DASH video, mp4_dash
hls-185-0                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-185-1                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-185-2                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-185-3                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-233-0                    mp4 426x240        |  233k m3u8_n | avc1.42C015       233k mp4a.40.2   0k
hls-233-1                    mp4 426x240        |  233k m3u8_n | avc1.42C015       233k mp4a.40.2   0k
hls-149-0                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
hls-149-1                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
hls-149-2                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
hls-149-3                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
dash-video_avc1_2-0          mp4 426x240    25  |  191k dash   | avc1.42C015       191k                        DASH video, mp4_dash
dash-video_avc1_2-1          mp4 426x240    25  |  191k dash   | avc1.42C015       191k                        DASH video, mp4_dash
dash-video-avc1-2-0          mp4 426x240    25  |  191k https  | avc1.42C015       191k                        DASH video, mp4_dash
dash-video-avc1-2-1          mp4 426x240    25  |  191k https  | avc1.42C015       191k                        DASH video, mp4_dash
dash-video_hvc1_2-0          mp4 426x240    25  |  164k dash   | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
dash-video_hvc1_2-1          mp4 426x240    25  |  164k dash   | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
dash-video-hvc1-2-0          mp4 426x240    25  |  164k https  | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
dash-video-hvc1-2-1          mp4 426x240    25  |  164k https  | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
hls-255-0                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-255-1                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-255-2                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-255-3                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-305-0                    mp4 640x360        |  305k m3u8_n | avc1.4D401E       305k mp4a.40.2   0k
hls-305-1                    mp4 640x360        |  305k m3u8_n | avc1.4D401E       305k mp4a.40.2   0k
hls-215-0                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
hls-215-1                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
hls-215-2                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
hls-215-3                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
dash-video_avc1_3-0          mp4 640x360    25  |  288k dash   | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video_avc1_3-1          mp4 640x360    25  |  288k dash   | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video-avc1-3-0          mp4 640x360    25  |  288k https  | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video-avc1-3-1          mp4 640x360    25  |  288k https  | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video_hvc1_3-0          mp4 640x360    25  |  258k dash   | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
dash-video_hvc1_3-1          mp4 640x360    25  |  258k dash   | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
dash-video-hvc1-3-0          mp4 640x360    25  |  258k https  | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
dash-video-hvc1-3-1          mp4 640x360    25  |  258k https  | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
hls-468-0                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-468-1                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-468-2                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-468-3                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-558-0                    mp4 854x480        |  558k m3u8_n | avc1.4D401F       558k mp4a.40.2   0k
hls-558-1                    mp4 854x480        |  558k m3u8_n | avc1.4D401F       558k mp4a.40.2   0k
hls-307-0                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
hls-307-1                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
hls-307-2                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
hls-307-3                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
dash-video_avc1_4-0          mp4 854x480    25  |  562k dash   | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video_avc1_4-1          mp4 854x480    25  |  562k dash   | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video-avc1-4-0          mp4 854x480    25  |  562k https  | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video-avc1-4-1          mp4 854x480    25  |  562k https  | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video_hvc1_4-0          mp4 854x480    25  |  419k dash   | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
dash-video_hvc1_4-1          mp4 854x480    25  |  419k dash   | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
dash-video-hvc1-4-0          mp4 854x480    25  |  419k https  | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
dash-video-hvc1-4-1          mp4 854x480    25  |  419k https  | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
hls-857-0                    mp4 1280x720       |  857k m3u8_n | avc1.640028       857k
hls-857-1                    mp4 1280x720       |  857k m3u8_n | avc1.640028       857k
hls-947-0                    mp4 1280x720       |  947k m3u8_n | avc1.640028       947k
hls-947-1                    mp4 1280x720       |  947k m3u8_n | avc1.640028       947k
hls-955                      mp4 1280x720       |  955k m3u8_n | avc1.640028       955k mp4a.40.2   0k
hls-1048                     mp4 1280x720       | 1048k m3u8_n | avc1.640028      1048k mp4a.40.2   0k
hls-584-0                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
hls-584-1                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
hls-584-2                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
hls-584-3                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
dash-video_avc1_5            mp4 1280x720   25  | 1084k dash   | avc1.640028      1084k                        DASH video, mp4_dash
dash-video-avc1-5            mp4 1280x720   25  | 1084k https  | avc1.640028      1084k                        DASH video, mp4_dash
dash-video_avc1_6            mp4 1280x720   25  | 1191k dash   | avc1.640028      1191k                        DASH video, mp4_dash
dash-video-avc1-6            mp4 1280x720   25  | 1191k https  | avc1.640028      1191k                        DASH video, mp4_dash
dash-video_hvc1_5-0          mp4 1280x720   25  |  776k dash   | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
dash-video_hvc1_5-1          mp4 1280x720   25  |  776k dash   | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
dash-video-hvc1-5-0          mp4 1280x720   25  |  776k https  | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
dash-video-hvc1-5-1          mp4 1280x720   25  |  776k https  | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
hls-1418-0                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-1418-1                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-1418-2                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-1418-3                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-2102-0                   mp4 1920x1080      | 2102k m3u8_n | avc1.640028      2102k
hls-2102-1                   mp4 1920x1080      | 2102k m3u8_n | avc1.640028      2102k
hls-1528-0                   mp4 1920x1080      | 1528k m3u8_n | avc1.640028      1528k mp4a.40.2   0k
hls-1528-1                   mp4 1920x1080      | 1528k m3u8_n | avc1.640028      1528k mp4a.40.2   0k
hls-2228                     mp4 1920x1080      | 2228k m3u8_n | avc1.640028      2228k mp4a.40.2   0k
hls-915-0                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-915-1                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-915-2                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-915-3                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-1314-0                   mp4 1920x1080      | 1314k m3u8_n | hvc1.1.6.L120.90 1314k
hls-1314-1                   mp4 1920x1080      | 1314k m3u8_n | hvc1.1.6.L120.90 1314k
dash-video_avc1_7-0          mp4 1920x1080  25  | 1491k dash   | avc1.640028      1491k                        DASH video, mp4_dash
dash-video_avc1_7-1          mp4 1920x1080  25  | 1491k dash   | avc1.640028      1491k                        DASH video, mp4_dash
dash-video-avc1-7-0          mp4 1920x1080  25  | 1491k https  | avc1.640028      1491k                        DASH video, mp4_dash
dash-video-avc1-7-1          mp4 1920x1080  25  | 1491k https  | avc1.640028      1491k                        DASH video, mp4_dash
dash-video_avc1_8            mp4 1920x1080  25  | 2920k dash   | avc1.640028      2920k                        DASH video, mp4_dash
dash-video-avc1-8            mp4 1920x1080  25  | 2920k https  | avc1.640028      2920k                        DASH video, mp4_dash
dash-video_hvc1_6-0          mp4 1920x1080  25  | 1258k dash   | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video_hvc1_6-1          mp4 1920x1080  25  | 1258k dash   | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video-hvc1-6-0          mp4 1920x1080  25  | 1258k https  | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video-hvc1-6-1          mp4 1920x1080  25  | 1258k https  | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video_hvc1_7            mp4 1920x1080  25  | 1784k dash   | hvc1.1.6.L120.90 1784k                        DASH video, mp4_dash
dash-video-hvc1-7            mp4 1920x1080  25  | 1784k https  | hvc1.1.6.L120.90 1784k                        DASH video, mp4_dash

@pukkandan I just created a new virtual machine (it's also Ubuntu MATE), and installed yt-dlp. It's working (though I have not downloaded anything yet, just ran yt-dlp -F) with a lot of warnings.
Is there any way to fix this on the host machine? Thank you so much.
Here's what I got on virtual machine:
yt-dlp -F https://www.hotstar.com/in/tv/yeh-rishta-kya-kehlata-hai/586/kartiks-promise-to-sirat/1000262304

[hotstar]<PHONE_NUMBER>: Downloading webpage
[hotstar]<PHONE_NUMBER>: Downloading token
[hotstar]<PHONE_NUMBER>: Downloading JSON metadata
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading MPD manifest
WARNING: [hotstar] Ignoring subtitle tracks found in the DASH manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[hotstar]<PHONE_NUMBER>: Downloading m3u8 information
WARNING: [hotstar] Ignoring subtitle tracks found in the HLS manifest; if any subtitle tracks are missing, please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
[info] Available formats for<PHONE_NUMBER>:
ID                           EXT RESOLUTION FPS |   TBR PROTO  | VCODEC             VBR ACODEC     ABR  ASR    NOTE
---------------------------- --- ---------- --- - ----- ------ - ---------------- ----- --------- ---- ------- -----------------------------
hls-audio_mp4a_129-Unknown-0 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_129-Unknown-1 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_129-Unknown-2 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_129-Unknown-3 mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-0  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-1  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-2  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-3  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-4  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-5  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-6  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_49-Unknown-7  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-0  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-1  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-2  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-3  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-4  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-5  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-6  mp4 audio only     |       m3u8_n |                        unknown                [und]
hls-audio_mp4a_65-Unknown-7  mp4 audio only     |       m3u8_n |                        unknown                [und]
dash-audio_und_mp4a_1-0      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_1-1      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_1-2      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_1-3      m4a audio only     |   49k dash   |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-0 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-1 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-2 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-1-3 m4a audio only     |   49k https  |                        mp4a.40.2  49k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-0      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-1      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-2      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_2-3      m4a audio only     |   65k dash   |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-0 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-1 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-2 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-2-3 m4a audio only     |   65k https  |                        mp4a.40.2  65k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_3-0      m4a audio only     |  129k dash   |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_und_mp4a_3-1      m4a audio only     |  129k dash   |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-3-0 m4a audio only     |  129k https  |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
dash-audio_only-und-mp4a-3-1 m4a audio only     |  129k https  |                        mp4a.40.2 129k 48000Hz DASH audio, m4a_dash, 48000Hz
hls-130-0                    mp4 320x180        |  130k m3u8_n | avc1.42C00C       130k
hls-130-1                    mp4 320x180        |  130k m3u8_n | avc1.42C00C       130k
hls-177                      mp4 320x180        |  177k m3u8_n | avc1.42C00C       177k mp4a.40.2   0k
hls-120-0                    mp4 320x180        |  120k m3u8_n | hvc1.1.6.L60.90   120k
hls-120-1                    mp4 320x180        |  120k m3u8_n | hvc1.1.6.L60.90   120k
dash-video_avc1_1            mp4 320x180    25  |  114k dash   | avc1.42C00C       114k                        DASH video, mp4_dash
dash-video-avc1-1            mp4 320x180    25  |  114k https  | avc1.42C00C       114k                        DASH video, mp4_dash
dash-video_hvc1_1            mp4 320x180    25  |  104k dash   | hvc1.1.6.L60.90   104k                        DASH video, mp4_dash
dash-video-hvc1-1            mp4 320x180    25  |  104k https  | hvc1.1.6.L60.90   104k                        DASH video, mp4_dash
hls-185-0                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-185-1                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-185-2                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-185-3                    mp4 426x240        |  185k m3u8_n | avc1.42C015       185k
hls-233-0                    mp4 426x240        |  233k m3u8_n | avc1.42C015       233k mp4a.40.2   0k
hls-233-1                    mp4 426x240        |  233k m3u8_n | avc1.42C015       233k mp4a.40.2   0k
hls-149-0                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
hls-149-1                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
hls-149-2                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
hls-149-3                    mp4 426x240        |  149k m3u8_n | hvc1.1.6.L60.90   149k
dash-video_avc1_2-0          mp4 426x240    25  |  191k dash   | avc1.42C015       191k                        DASH video, mp4_dash
dash-video_avc1_2-1          mp4 426x240    25  |  191k dash   | avc1.42C015       191k                        DASH video, mp4_dash
dash-video-avc1-2-0          mp4 426x240    25  |  191k https  | avc1.42C015       191k                        DASH video, mp4_dash
dash-video-avc1-2-1          mp4 426x240    25  |  191k https  | avc1.42C015       191k                        DASH video, mp4_dash
dash-video_hvc1_2-0          mp4 426x240    25  |  164k dash   | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
dash-video_hvc1_2-1          mp4 426x240    25  |  164k dash   | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
dash-video-hvc1-2-0          mp4 426x240    25  |  164k https  | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
dash-video-hvc1-2-1          mp4 426x240    25  |  164k https  | hvc1.1.6.L60.90   164k                        DASH video, mp4_dash
hls-255-0                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-255-1                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-255-2                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-255-3                    mp4 640x360        |  255k m3u8_n | avc1.4D401E       255k
hls-305-0                    mp4 640x360        |  305k m3u8_n | avc1.4D401E       305k mp4a.40.2   0k
hls-305-1                    mp4 640x360        |  305k m3u8_n | avc1.4D401E       305k mp4a.40.2   0k
hls-215-0                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
hls-215-1                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
hls-215-2                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
hls-215-3                    mp4 640x360        |  215k m3u8_n | hvc1.1.6.L63.90   215k
dash-video_avc1_3-0          mp4 640x360    25  |  288k dash   | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video_avc1_3-1          mp4 640x360    25  |  288k dash   | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video-avc1-3-0          mp4 640x360    25  |  288k https  | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video-avc1-3-1          mp4 640x360    25  |  288k https  | avc1.4D401E       288k                        DASH video, mp4_dash
dash-video_hvc1_3-0          mp4 640x360    25  |  258k dash   | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
dash-video_hvc1_3-1          mp4 640x360    25  |  258k dash   | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
dash-video-hvc1-3-0          mp4 640x360    25  |  258k https  | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
dash-video-hvc1-3-1          mp4 640x360    25  |  258k https  | hvc1.1.6.L63.90   258k                        DASH video, mp4_dash
hls-468-0                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-468-1                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-468-2                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-468-3                    mp4 854x480        |  468k m3u8_n | avc1.4D401F       468k
hls-558-0                    mp4 854x480        |  558k m3u8_n | avc1.4D401F       558k mp4a.40.2   0k
hls-558-1                    mp4 854x480        |  558k m3u8_n | avc1.4D401F       558k mp4a.40.2   0k
hls-307-0                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
hls-307-1                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
hls-307-2                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
hls-307-3                    mp4 854x480        |  307k m3u8_n | hvc1.1.6.L90.90   307k
dash-video_avc1_4-0          mp4 854x480    25  |  562k dash   | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video_avc1_4-1          mp4 854x480    25  |  562k dash   | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video-avc1-4-0          mp4 854x480    25  |  562k https  | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video-avc1-4-1          mp4 854x480    25  |  562k https  | avc1.4D401F       562k                        DASH video, mp4_dash
dash-video_hvc1_4-0          mp4 854x480    25  |  419k dash   | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
dash-video_hvc1_4-1          mp4 854x480    25  |  419k dash   | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
dash-video-hvc1-4-0          mp4 854x480    25  |  419k https  | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
dash-video-hvc1-4-1          mp4 854x480    25  |  419k https  | hvc1.1.6.L90.90   419k                        DASH video, mp4_dash
hls-857-0                    mp4 1280x720       |  857k m3u8_n | avc1.640028       857k
hls-857-1                    mp4 1280x720       |  857k m3u8_n | avc1.640028       857k
hls-947-0                    mp4 1280x720       |  947k m3u8_n | avc1.640028       947k
hls-947-1                    mp4 1280x720       |  947k m3u8_n | avc1.640028       947k
hls-955                      mp4 1280x720       |  955k m3u8_n | avc1.640028       955k mp4a.40.2   0k
hls-1048                     mp4 1280x720       | 1048k m3u8_n | avc1.640028      1048k mp4a.40.2   0k
hls-584-0                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
hls-584-1                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
hls-584-2                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
hls-584-3                    mp4 1280x720       |  584k m3u8_n | hvc1.1.6.L93.90   584k
dash-video_avc1_5            mp4 1280x720   25  | 1084k dash   | avc1.640028      1084k                        DASH video, mp4_dash
dash-video-avc1-5            mp4 1280x720   25  | 1084k https  | avc1.640028      1084k                        DASH video, mp4_dash
dash-video_avc1_6            mp4 1280x720   25  | 1191k dash   | avc1.640028      1191k                        DASH video, mp4_dash
dash-video-avc1-6            mp4 1280x720   25  | 1191k https  | avc1.640028      1191k                        DASH video, mp4_dash
dash-video_hvc1_5-0          mp4 1280x720   25  |  776k dash   | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
dash-video_hvc1_5-1          mp4 1280x720   25  |  776k dash   | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
dash-video-hvc1-5-0          mp4 1280x720   25  |  776k https  | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
dash-video-hvc1-5-1          mp4 1280x720   25  |  776k https  | hvc1.1.6.L93.90   776k                        DASH video, mp4_dash
hls-1418-0                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-1418-1                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-1418-2                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-1418-3                   mp4 1920x1080      | 1418k m3u8_n | avc1.640028      1418k
hls-2102-0                   mp4 1920x1080      | 2102k m3u8_n | avc1.640028      2102k
hls-2102-1                   mp4 1920x1080      | 2102k m3u8_n | avc1.640028      2102k
hls-1528-0                   mp4 1920x1080      | 1528k m3u8_n | avc1.640028      1528k mp4a.40.2   0k
hls-1528-1                   mp4 1920x1080      | 1528k m3u8_n | avc1.640028      1528k mp4a.40.2   0k
hls-2228                     mp4 1920x1080      | 2228k m3u8_n | avc1.640028      2228k mp4a.40.2   0k
hls-915-0                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-915-1                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-915-2                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-915-3                    mp4 1920x1080      |  915k m3u8_n | hvc1.1.6.L120.90  915k
hls-1314-0                   mp4 1920x1080      | 1314k m3u8_n | hvc1.1.6.L120.90 1314k
hls-1314-1                   mp4 1920x1080      | 1314k m3u8_n | hvc1.1.6.L120.90 1314k
dash-video_avc1_7-0          mp4 1920x1080  25  | 1491k dash   | avc1.640028      1491k                        DASH video, mp4_dash
dash-video_avc1_7-1          mp4 1920x1080  25  | 1491k dash   | avc1.640028      1491k                        DASH video, mp4_dash
dash-video-avc1-7-0          mp4 1920x1080  25  | 1491k https  | avc1.640028      1491k                        DASH video, mp4_dash
dash-video-avc1-7-1          mp4 1920x1080  25  | 1491k https  | avc1.640028      1491k                        DASH video, mp4_dash
dash-video_avc1_8            mp4 1920x1080  25  | 2920k dash   | avc1.640028      2920k                        DASH video, mp4_dash
dash-video-avc1-8            mp4 1920x1080  25  | 2920k https  | avc1.640028      2920k                        DASH video, mp4_dash
dash-video_hvc1_6-0          mp4 1920x1080  25  | 1258k dash   | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video_hvc1_6-1          mp4 1920x1080  25  | 1258k dash   | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video-hvc1-6-0          mp4 1920x1080  25  | 1258k https  | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video-hvc1-6-1          mp4 1920x1080  25  | 1258k https  | hvc1.1.6.L120.90 1258k                        DASH video, mp4_dash
dash-video_hvc1_7            mp4 1920x1080  25  | 1784k dash   | hvc1.1.6.L120.90 1784k                        DASH video, mp4_dash
dash-video-hvc1-7            mp4 1920x1080  25  | 1784k https  | hvc1.1.6.L120.90 1784k

Not sure. Can you show the output and the files generated by --print-traffic --write-pages on the machine that doesnt work so that I can get some better idea on what is going on

@pukkandan Thank you so much for the reply.
The question I had since getting this error: Does yt-dlp sends any kind of Machine ID or Device ID to Hotstar.com or to their CDN (Akamai)?
Block or Refusal (Error 403 Forbidden) cannot be per IP address, because then yt-dlp would not work on Virtual Machine either, as virtual machine is using the same IP address too.
Note-1: Right before I was about to submit the comment, I noticed this from the output I just posted below:
Downloading webpage > reply: 'HTTP/1.1 200 OK\r\n'

Downloading token >

> send: b'{"device_ids": [{"id": "1b717bcc-e4f0-439f-8d34-afeaa7fa986a", "type": "device_id"}]}'

> reply: 'HTTP/1.1 403 Forbidden\r\n'

So, if the Device ID is the root cause... is it possible to send different/new Device ID every time?
Thanks a lot.
 Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
  File "/home/admn/.local/lib/python3.9/site-packages/yt_dlp/extractor/common.py", line 678, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/home/admn/.local/lib/python3.9/site-packages/yt_dlp/YoutubeDL.py", line 3071, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.9/urllib/request.py", line 523, in open
    response = meth(req, response)
  File "/usr/lib/python3.9/urllib/request.py", line 632, in http_response
    response = self.parent.error(
  File "/usr/lib/python3.9/urllib/request.py", line 561, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 494, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.9/urllib/request.py", line 641, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)

device_id is randomly generated using uuid.uuid4()

device_id is randomly generated using uuid.uuid4()

Yes, I just tried the same command again, and got this different Device ID. It looks like it gets generated randomly with every request?
send: b'{"device_ids": [{"id": "fd9cf298-ada7-4c07-ad2b-d671840f2f4a", "type": "device_id"}]}'

reply: 'HTTP/1.1 403 Forbidden\r\n'

So, if its not Device ID, anyway out of this situation? By the way, did you find any other clue from the complete output?
Once again, thank you so much.

Yes, found the issue. Your PC's time is out of sync with the server time by 7sec. I was able to reproduce the issue by setting my clock a few seconds ahead.
This is annoying... I will see if I can take the time from the x-origin-date header instead of PC's time

@pukkandan

I will see if I can take the time from the x-origin-date header instead of PC's time

That would be really great.
Though after spending few hours, I was able to synchronize time in Ubuntu MATE 21.04 (Host/main machine).
And yes, I can confirm that, (as you correctly diagnosed) my host machine's time being out of sync would be the root cause, as now I can download from Hotstar just fine.
Thank you so much :)

There is issue with premium content, free content can be download.
premium content need authorization for that what can i do, i put --username login_number but there is nothing get otp for sign-in, there is issue arrive.
yt-dlp -F --username number "https://www.hotstar.com/in/tv/human/1260077204/the-saviour/1260077206"
Type account password and press [Return]:
[hotstar]<PHONE_NUMBER>: Downloading JSON metadata
[hotstar]<PHONE_NUMBER>: Downloading webpage
[hotstar]<PHONE_NUMBER>: Downloading token
[hotstar]<PHONE_NUMBER>: Downloading JSON metadata
ERROR: [hotstar]<PHONE_NUMBER>: Unable to download JSON metadata: HTTP Error 401: Unauthorized (caused by <HTTPError 401:
'Unauthorized'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see
https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete
output. (caused by <HTTPError 401: 'Unauthorized'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure
you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --
verbose flag and include its complete output.
Please help me out on this.


[boost] Support non-Windows build.

Fixed #4166.

I tested build boost with following triplet:

x86-windows
x86-windows-static
x64-windows
x64-windows-static
x64-linux
x64-osx

Looks good.

Don't recent gcc versions default to -std=c++14?

@OlafvdSpek
Thanks for your advice, I have modified.

Imho individual port files shouldn't set a custom c++ standard at all. Either provide an option to set the standard in the triplet file so that all libraries are compiled with the same setting (which requires some cooperation from libraries that are not build with cmake) or just use the compiler default. One Idea might be to read CMAKE_CXX_STANDARD and if set translate it into a corresponding b2 flag.
Anything else can lead to annoying errors when the same header file ends up included in different  TUs that are compiled with different settings. (Related: https://github.com/Microsoft/vcpkg/issues/4004)
This might not be a big problem in this case, as most boost libraries are header only anyway, so the b2 setting here will not have any influence on them, but if it has an effect at all, it is imho more likely to cause trouble than help.

I am seeing new build failures on the following ports with this PR. Let me know if you need build log.
Processing arm-uwp                        357 vs 403
boost-contract                **regression**                Fail vs Pass
boost-math                    **regression**                Fail vs Pass

Processing x64-osx                        485 vs 577
boost-atomic                  **regression**                Fail vs Pass
boost-container               **regression**                Fail vs Pass
boost-exception               **regression**                Fail vs Pass
boost-regex                   **regression**                Fail vs Pass
boost-signals                 **regression**                Fail vs Pass
boost-stacktrace              **regression**                Fail vs Pass
boost-system                  **regression**                Fail vs Pass
Processing x64-uwp                        382 vs 431
boost-math                    **regression**                Fail vs Pass
Processing x64-windows                    771 vs 856
boost-math                    **regression**                Fail vs Pass
Processing x86-windows                    764 vs 841
boost-math                    **regression**                Fail vs Pass

/azp run

This should have been fixed by c2e4fa7. If this is still unresolved, please open a new issue!


Add changePassword call

Coverage increased (+0.04%) to 86.646% when pulling 5045288bf53b128fbb90d84bf684179bafc6920b on qingweibinary:qingwei/add_chg_pw into 93d043b05bd01b9258bd009a08764e35859da037 on binary-com:master.


Keep same value on input when clicking same date or opening datepicker again

Hello !
I have a dp.change event who simply modify the value of the input to something more formatted.
The problem is when I click the same date twice, the value of the input return to base state.
Same when I have already chosen a date and opening the datepicker again.
https://jsfiddle.net/v4kmLfLx/2/

Is that normal?

 So... yeah is normal.
And BTW you're making this harder than need it.
Just use
  format: 'DD MMMM YYYY à HH:mm'
No extra event need it, It'll be easier and less time-read code consuming, and no weird behavior happening and remember to update your base code current one is 4.17.47 you're using (on the fiddle at least) 4.15.35


Subscription Postpone Date/Time is + 7hrs off of API input (local time)

Subscription.Postpone seems to be off when passing a local datetime.
Description:
C# Subscription Postpone, does not set the localized time in the app. Enter a local local postpone time/date, and the app shows the time as +7 hours ahead of UTC.
using System;
using Recurly;
// demos the input of 1:00 pm local time, while the app then shows 8:00pm local time, 7 hour difference.
namespace SubscriptionPostpone
{

    class Program
    {
        static void Main(string[] args)
        {
            var subscription = Subscriptions.Get("3a2f2209bcfd05b5fb9bc2459a9ddaaf");
            subscription.Postpone(new DateTime(2016,12,14,13,0,0,
                DateTimeKind.Local)
                );
        }
}

\cc @elliottbernstein

@bhelx To confirm, you're specifying a postpone date, however when you view the modified subscription  the CurrentPeriodEndsAt has a 7 hour difference?

@MuffinMan10110 I'm not 100% sure I'm going to look into this today or tomorrow. I got this report from our support team. I suppose the problem is that this is sending over the local time and our servers are treating it like UTC:
https://github.com/recurly/recurly-client-net/blob/master/Library/Subscription.cs#L463

I'm willing to bet that sending it in local time is the issue. Generally in API design you just work with dates in a UTC manner. In our case we need to be more descriptive in what format we expect, UTC, local or both and if we do accept both we check if it's local time and convert it to UTC before sending to the server.
Now the issue arises of when you get the subscription from the server, since we'd be getting UTC dates we'd have to convert them to local, however now the .net client is making assumptions about what time zone the user wants those dates in.
I think the easiest way is to be implicit and only handle UTC dates. All methods and objects assume UTC and the developer can convert them to whatever time zone they want.

I believe this issue originated with me via support.
I had created a new DateTime at 12:00:00 to ensure the subscription would renew at midnight.  After calling Postpone, the sub's CurrentPeriodEndsAt ended up being +7 hrs.  The value I passed in was most likely not UTC, so that is a workaround I could try.  I think what @1TheMuffinMan said about passing UTC is perfectly reasonable.

@bhelx After speaking with you here's the lowdown on how the DateTimeKind works. By default the kind will be Unspecified and you can choose to set it to two other types which are Local and Utc. Based on our conversation we could do the following:

If a DateTime being passed into a method is DateKindType.Unspecified we throw an exception saying it needs to be specified
If the DateTimeKind is Local the library can automatically convert it to UTC before sending it to the API
If the DateTimeKind is Utc then no changes would be required internally
Additionally, when the client library receives data from the API it should set the DateTimeKind to Utc instead of leaving it unspecified.

Other thoughts:

This change would require everyone to go through their code and specify a Kind for their datetimes. This will most defintely be a pain. What I suggest is that we add a configuration variable to the client library called TreatUnspecifiedDateTimeAs and allow people to specify the default in just one place.

I'm having a similar problem with the Postpone() method.  I'm passing a valid UTC date/time that is the current datetime.  I receive back an "invalid data" error.  I've even tried adding up to 2 hours to the time being passed in and I'm still getting the "invalid data" error.  The only time the call worked was when I accidentally called ToUniversalTime() on a date that was already UTC which added an additional 5 hours to the time.  It almost seems like even though I'm passing in a datetime that occurs in the future, Recurly is seeing it as being in the past and thrown an exception.

@jjwhite I'll get more acquainted with this date time issue this week. The documentation doesn't specify any specific constraints about the date (not even if it can be in the past) so it will be interesting if it turns out there are some constraints such as not being able to set a date too close to the last one, etc.

@jjwhite I ran the Postpone unit test with a bunch of different data and wasn't receiving an error when trying to postpone using near values such as 2 hours from now.
To keep this thread on a single topic (using non UTC dates) do you mind opening up a separate issue regarding the Postpone method? If you do choose to it would also be helpful if you could include a snippet of code you're using and possibly the xml that is being sent to the server. With the proper data to reproduce we can work on getting a fix out fast if there is a bug.

Added a new issue: #214

I've added a response to issue #214 and closing this issue.


Seem to be missing a few badges that I have earned

Hey, it looks like I should have Mapathoner (or it says I'm on my way to levels 3) but it doesn't show that I've earned it. http://www.missingmaps.org/users/#/408282/badges

This seems to be a duplicate of https://github.com/MissingMaps/missingmaps.github.io/issues/179

Checked this out.
There seems to be an issue in the api with the Mapathoner badge not being assigned to the users. The calculations are run separately on the front end, which is why the progress is still showing up fine. We'll work to fix this soon.

Marion Barry, you should have your badges now.
Mapathon badge has been fixed on the front end.


[SPIKE] Evaluate possible use of Application Security Groups as addition to Network Security Groups

Research if Azure Application Security Groups might be usefull as adition or partial replacement for Azure Security Groups. They might be a better fit for our component cluster based definition then the current NSG approach we currently use:
https://docs.microsoft.com/en-us/azure/virtual-network/application-security-groups
https://azure.microsoft.com/pl-pl/blog/applicationsecuritygroups/
https://www.terraform.io/docs/providers/azurerm/r/application_security_group.html
Few things to consider during research:

How would upgrading of existing clusters work if this would be used in any way?
Does AWS have an equivalent and if so can we leverage it the same way we could with ASGs?

@seriva what should be output from this spike? I expect that output from this spike would be input to actual "do" task. I'm not sure if we want some little PoC or documentation how to do it or design of ASG/NSGs in Epiphany? What do you think?

Looks like a great idea, let's do the spike! :D/

We are nog going to work on this anymore in the scope of this Epiphany.


[Task]: Ensure that plugins support uploading files of size 100 MB

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
- Postgres

MySQL
DynamoDB
Redshift
Snowflake
ArangoDB
Firestore

High priorities- rest. postgres, mysql, mongo S3

getting 504 on uploading a large file on postgres @nidhi-nair . https://knynrq7fk9.vmaker.com/record/TbRZa1AaW6BE44Tp

@nidhi-nair @ayushpahwa -

S3 is not supporting large files in binary format.
REST is not supporting large files in both binary and base 64 format
For postgres, video, PDF, JSON, ZIP formats are failing for binary format and Video and PDF are failing in base 64 format
For MySql  also, large files are failing in both binary and base 64 format


Safe guard DeltaTableState using Rust's type system

Description
Use Case
Follow up for https://github.com/delta-io/delta-rs/pull/456#issuecomment-941926489.
When we call process_action on a particular DeltaTableState, we need to make sure the passed in actions do not cross commit boundaries. We can restructure our code to have the Rust compiler to guarantee this property for us at build time.
Here is what I have in mind:

Move process_action and DeltaTableState into its own module
Add two new methods: DeltaTableState::from_commit and DeltaTableState::from_checkpoint

Since DeltaTableState is moved into its own module, other part of the code base won't be able to mutate a table state with arbitrary actions. The from_commit and from_checkpoint methods make sure users won't be able to construct table states from actions across commit boundaries.
Related Issue(s)

@houqp : Nice idea!
I can see how this creates initial DeltaTableState in a consistent manner and protects it from feeding arbitrary actions from multiple commits or in the wrong order etc. I assume the merge operation (or some equivalent functionality) is still required, because we'd still need to add new commits to existing state.
I think we would be able to show / prove that a table state that is merged from two adjacent commits in the right order (i.e., commit n left, commit n+1 right) would itself yield a correct table state (left could be a checkpoint, but it would probably work either way). However, merge would still be able to create inconsistent state if someone applies it improperly, e.g., calling it with the two commits flipped or non-adjacent calls (two adds for the same file, ...).
If we want to protect from this as well, maybe we can:

have DeltaTableState track the range of commits it is representing

checkpoints would have range [0, n] where n is the checkpoint commit number
a single commit would have range [n, n]
a merge from n-1 and n would have [n-1,n].
...

assert merge to only merge states where left.state.range.end + 1 = right.state.range.start

I may be overthinking this, though; your suggestion is already protecting us from accidental state modification via process_action, which is the bigger part.
PS: I'm a fan of property-based testing (e.g., via proptest), a consistent table state could be a sweet target for such a test suite.

I assume the merge operation (or some equivalent functionality) is still required,

Yes, merge is still required, what's proposed in this issue is just to make sure merge always receives a validate DeltaTableState.

have DeltaTableState track the range of commits it is representing

I think this is a really cool idea!

I think the only save merge operation is by sequentially combining the full table state with the next commit, in order.

Yes, you are right. This also restricts how much we can parallel the action apply :( I think it's fair to say we can only parallel action application by partitioning actions within a checkpoint or commit. In other words, state merge has to be executed sequentially following the commit version. But we can reconstruct a table state in parallel.
I am also a fan of property-based testing and I have been thinking of adopting protest for delta-rs too. We should totally do it :)


FORCE_OOBE_WELCOME_SCREEN macro is defined for Debug|ARM, Debug|x86, but not for Debug|x64

Minor issue:
FORCE_OOBE_WELCOME_SCREEN macro is defined for Debug|ARM, Debug|x86, but not for Debug|x64.
It probably should be defined for all debug configs  (ARM, x86, x64) or for none of them.

Hi @sergeyDoroshenko - what sample are you referring to?


Nek5000 reader

Options
Backend

Paraview reader
pymech

References

entrypoints
https://intake.readthedocs.io/en/latest/plugin-directory.html#plugin-directory
https://intake.readthedocs.io/en/latest/use_cases.html?highlight=xarray#distribute-data-in-a-custom-format

Frontend

intake-xarray (see image backend)
xarray
paraview python_view (section 4.12 in Paraview Guide 5.6)

Can we close this one now that #7 has been merged ?


[bug]: Empty response for node-fetch http call

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
When I do a node-fetch call after integrating keploy/typescript, the response is not the expected result from that API. It can be due to intercepting the node-fetch API calls.
Steps to reproduce

Run the Keploy server.
Integrate the node-fetch with Keploy's TS-SDK to mock dependencies of your sample API.
Run your sample API on "off" mode
Curl the endpoint which making node-fetch call to "https://api.keploy.io/healthz" and logging that response.
Hence, you can see that node-fetch is returning empty Response instead of {status:200, body:"ok"}.

Environment
None
Version
Self-hosted

Hi, I want to work on this issue.

Hi @Ramanjs, the problem is that I have not integrated the express hook in my local application. Hence, when you comment the require hook for express in node-fetch/server.js, then the application will crash with this message in screenshot


cleanup unused environment variables rand to smooth traffic send to tracker

This PR do two things

clear unused environment variables, accept those parameters as arguments
add randomize backoff - smooth out spike of tcp connections swaping dmlc tracker

@trivialfis @hcho3
update on item 2
A bit more detail, in production system, it's not unusual to have thousands of rabit workers in one xgboost deployment. Every one of workers connect to tracker (python socket server) with ondemand http connection. This become a problem when single worker dead, almost all workers needs to send http requests to server at same time; And when majority of those connect ends in error, they wait same amount of time and try again until exceed max retry.

@chenqin Can we use exponential backoff to ease congestion? Unlike random waiting, it will have deterministic behavior.

@chenqin Can we use exponential backoff to ease congestion? Unlike random waiting, it will have removed random with expoential back off plus rank %10 to avoid ddos tracker

Please use deterministic waiting and point me to some unittests.

working on googletest to support unittests

@chenqin You can consider using gtest main: https://github.com/dmlc/xgboost/blob/master/tests/cpp/test_main.cc

@chenqin You can consider using gtest main: https://github.com/dmlc/xgboost/blob/master/tests/cpp/test_main.cc

done

@hcho3 @trivialfis

Will give a proper review tomorrow, one thing though, try find_package first then download gtest ...

I tried to use find_package along with exteranl project which doesn't ends well.
gtest download is shelled with RABIT_BUILD_TESTS

@chenqin Let me try.

Also, why is it necessary to download gtest?  Can we assume that the developer can install gtest test somewhere?  CMake accepts a parameter called GTEST_ROOT, which can be used to find gtest: https://cmake.org/cmake/help/v3.0/module/FindGTest.html

@chenqin Will make a PR for cleaning up CMake scripts.

@trivialfis let's get this in to unblock xgb CMake house cleaning

done with cleanup, xgboost now build with rabit

we should avoid mixing things together, especially "cleanup/refactoring" and "new feature adding"
and the other thing I don't understand is. the description says "clear unused environment variables, accept those parameters as arguments" why it contains so many CMake file changes

removed from this pr, let's do back off in separate pr

we should avoid mixing things together, especially "cleanup/refactoring" and "new feature adding"
and the other thing I don't understand is. the description says "clear unused environment variables, accept those parameters as arguments" why it contains so many CMake file changes

fixed, remvoed code change touch sleep, this pr focus on make it buildable with xgboost project and adding googletest backed unit tests

@trivialfis


llm.c poster added. Productive pull soon :)

I added a llm.c poster on the README file. It is unconventional and counterproductive pull but I felt it was missing something (I was looking at llama.cpp repo) and I created this poster.

I can do better :)


Add an endpoint to check the version

any concerns with including git in the deployment?

any concerns with including git in the deployment?

any concerns with including git in the deployment?

The git hash is open information so I fell it's okay to expose it. The hash version is written to a config file, it has small impact on the deployed artifacts.

any concerns with including git in the deployment?

The git hash is open information so I fell it's okay to expose it. The hash version is written to a config file, it has small impact on the deployed artifacts.


reset: Correct reset register assignments

Correct the assignments used when populating registers to make a Reset SBI call, according to the SBI spec:

a0 is reset_type
a1 is reason

The register values were reversed, which caused the module to generate incorrect register values in the SBI call, specifically when passing a non-zero reset reason.
Add unit tests in the reset module to check the register values created with several combinations of reset types and reasons against the values expected from the SBI spec. These tests verify that the fix corrects the register assignments.

LGTM.


[note] issues

Properties window:

Include Justification, we need a dropdown menu for the 3 options (left/center/right) - like iemguis have dropdown menu for font names.
Incude new "outline" checkbox.
Incude new width parameter.
Live changes (change parameters when you change them and not only when you hit "ok").
Colors set via properties are not saved with the patch.
The "fill background" check box should be under the 'Colors' section
Include "Undo".
Instead of "Foreground" we could just have "Text" instead?

I'll take a look at this tomorrow!

I got most of it working now, the only things left on the list are:

Incude new width parameter.
Include "Undo"
Colors set via properties are not saved with the patch.

I'll send a PR after I fix those (probably tomorrow, it's 2:30 at night over here!)

Oh I see the outline color options is still there, that was a mistake, I'll remove that

I see the outline color options is still there, that was a mistake, I'll remove that

outline width and color might be a good idea, but not for now :)

Include "Undo"

I guess this is all that's left, right? I might be able to do that next week

Hmm @timothyschoen , setting Text color from properties doesn't work now

Text color from properties doesn't work now

I couldn't figure out why and it looks pretty weird, we always get "back", no matter what

Added UNDO, thanks a lot for the help and work you've done on this :) I cannot believe this happened ;) really happy, been hoping for this being eventually done for years!!!


Create go.yml

Created a basic ci file for the repo

Closing as another CI request has been made and merged


onNothingSelected method of OnChartValueSelectedListener is called when tapped outside area of piechart ( container in which piechart added)

I have added OnChartValueSelectedListener to piechart .
When i unhighlight any value of piechart onNothingSelected callback gets called . but it is getting
called if i tap outside of the pichart area also .

The chart in fact a rect area,  tap in this area will trigger onNothingSelected


Fix and enable FlowRunnerPipelineTest

Fix and enable FlowRunnerPipelineTest.
Also much less code and faster running.
Separate commits should offer some clarity:

first I just fixed the "app initialization" and test file path
then I converted the assertions to use the "blocking" versions that wait until the expected status is reached, and removed redundant sleeps

Here I also removed the sleep between starting the 1st and 2nd execution: the 2nd execution can be started when the first jobs of the 1st execution have reached RUNNING status.

finally I also converted the flow level assertions to the "blocking" versions

Would you like to have these tests? Looks like there's a new conflict to resolve.

Yes, this change seems to be useful.
Sorry, the team are behind in reviewing PR requests.

Rebased with conflicts resolved.

Thanks @chengren311 for reviewing this change.
The new code looks cleaner and it is no longer ignored! Thanks @juhoautio !

Good stuff @HappyRay 👍
I have resolve the review comments so far. Anything else?

Travis CI failure seems to be caused by flaky tests:
:azkaban-solo-server:test FAILED
azkaban.execapp.event.JobCallbackRequestMakerTest > basicPostTest FAILED
org.junit.runners.model.TestTimedOutException: test timed out after 4000 milliseconds
at org.apache.log4j.spi.LoggingEvent.(LoggingEvent.java:165)
at org.apache.log4j.Category.forcedLog(Category.java:391)
at org.apache.log4j.Category.warn(Category.java:1060)
at azkaban.execapp.event.JobCallbackRequestMaker.makeHttpRequest(JobCallbackRequestMaker.java:158)
at azkaban.execapp.event.JobCallbackRequestMakerTest.basicPostTest(JobCallbackRequestMakerTest.java:164)
azkaban.execapp.event.JobCallbackRequestMakerTest > unResponsiveGetTest FAILED
org.junit.runners.model.TestTimedOutException: test timed out after 4000 milliseconds
at org.apache.http.client.methods.HttpGet.(HttpGet.java:65)
at azkaban.execapp.event.JobCallbackUtil.parseJobCallbackProperties(JobCallbackUtil.java:170)
at azkaban.execapp.event.JobCallbackUtil.parseJobCallbackProperties(JobCallbackUtil.java:94)
at azkaban.execapp.event.JobCallbackRequestMakerTest.unResponsiveGetTest(JobCallbackRequestMakerTest.java:141)

azkaban.execapp.FlowRunnerPipelineTest > testBasicPipelineLevel2Run FAILED
java.lang.AssertionError: Wrong status for [pipelineEmbeddedFlow3:innerJobB] expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at azkaban.execapp.FlowRunnerTestBase.assertStatus(FlowRunnerTestBase.java:131)
at azkaban.execapp.FlowRunnerPipelineTest.testBasicPipelineLevel2Run(FlowRunnerPipelineTest.java:315)

I haven't had time to look into the test logic yet. I've asked other team members to help to review your PRs.

I went looking for the failed build because your message didn't reveal what the wrong status was :) I found the build: https://travis-ci.org/azkaban/azkaban/builds/266809720
azkaban.execapp.FlowRunnerTest2 > testNormalFailure3 FAILED
    java.lang.AssertionError: Wrong status for [jobd] expected:<RUNNING> but was:<READY>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at azkaban.execapp.FlowRunnerTestBase.assertStatus(FlowRunnerTestBase.java:117)
        at azkaban.execapp.FlowRunnerTest2.testNormalFailure3(FlowRunnerTest2.java:448)

I'll see if I can figure out what could cause it. It's a pity if we can't get the full output of this run from Travis.

@HappyRay I went looking for the failed build because your message didn't reveal what the wrong status was :) Hmm but I didn't find it. Could you edit your message wrapping the stracktrace into a codeblock?
I'll try to see if I can figure out what could cause it. It's a pity if we can't get the full output of this run from Travis.

Thanks @juhoautio
Sorry. I should have included a link. Can you see this page? https://travis-ci.org/azkaban/azkaban/pull_requests if you do, you can search for this PR there.

I can't find the failed build anymore. I shouldn't have restarted it.

No worries as I guess there wasn't more to obtain after all. That expected:<RUNNING> but was:<QUEUED> was what I was looking for.

This should be ok as well.
I checked what tests failed in that build c74fad3. They are not related to FlowRunnerPipelineTest.
azkaban.execapp.FlowRunnerTest2 > testPauseFailFinishAll FAILED
    java.lang.IllegalStateException: joba wasn't added in testJobs map
        at azkaban.executor.InteractiveTestJob.getTestJob(InteractiveTestJob.java:55)
        at azkaban.execapp.FlowRunnerTest2.testPauseFailFinishAll(FlowRunnerTest2.java:996)

azkaban.execapp.JobRunnerTest > testDelayedExecutionCancelledJob FAILED
    java.lang.AssertionError
        at org.junit.Assert.fail(Assert.java:86)
        at org.junit.Assert.assertTrue(Assert.java:41)
        at org.junit.Assert.assertTrue(Assert.java:52)
        at azkaban.execapp.JobRunnerTest.testDelayedExecutionCancelledJob(JobRunnerTest.java:303)
:azkaban-web-server:test FAILED

azkaban.execapp.FlowRunnerTest2 > testPause FAILED
    java.lang.AssertionError: Wrong status for [joba] expected:<SUCCEEDED> but was:<RUNNING>
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.failNotEquals(Assert.java:834)
        at org.junit.Assert.assertEquals(Assert.java:118)
        at azkaban.execapp.FlowRunnerTestBase.assertStatus(FlowRunnerTestBase.java:131)
        at azkaban.execapp.FlowRunnerTestBase.assertStatus(FlowRunnerTestBase.java:136)
        at azkaban.execapp.FlowRunnerTest2.testPause(FlowRunnerTest2.java:804)

@juhoautio I was having a look at this over the past week but I am away from now until sep 11. Can this wait or should someone else have a look?

@inramana, just pinging in case this got buried under other things.. Would be nice to get this in so that we can proceed with the actual bug fix: https://github.com/azkaban/azkaban/pull/1245.

@juhoautio
@inramana is busy. I am taking over. The change LGTM. Please resolve the conflict and I will merge it.

Conflicts resolved.


Question - Position of the line to add in podfile for flutter project

Hi,
A question on where the line should be added in the podfile in the flutter project.
I have added the line towards the end in the runner do block. Is this correct?
`
target 'Runner' do
use_frameworks!
use_modular_headers!
flutter_install_all_ios_pods File.dirname(File.realpath(FILE))
pod 'FirebaseFirestore', :git => 'https://github.com/invertase/firestore-ios-sdk-frameworks.git', :tag => '7.3.0'
end
`

I would follow the example? It is known to work.
https://github.com/FirebaseExtended/flutterfire/blob/master/packages/cloud_firestore/cloud_firestore/example/ios/Podfile

Thanks Mike


net: lwm2m: Always emit DISCONNECTED event

When LwM2M engine is requested to stop,
emit the disconnected event unconditionally.
There is really no reason to skip the event
on network error, or if we have never been registered.
Fixes #76422

@SebastianSchueller please review.


Add option to opt-out from fallback to base repo when config file is not found

When config file is not found in the current repository, currently probot tries to load file from .github repository.
This has two issues:

This adds latancy and one more request to GitHub to check that file. In environment where we do not use the base repository, this is wasted.
It is adds option for mistakes when someone in the organization creates repository .github which may be tricky to trace.

Change:
Adding loadBaseWhenMissing to the config function as opt-out. By default the base will be loaded to maintain backward compatiblity.
Adding Context.configStrict as shortcut to the config with the opt-out option.

Is this for an app that you only install on your own organization?

Yes it is internal app

I think both are neglectable. Did you run into a specific problem with it? Can you elaborate?

The latency is not real problem, it's more about just not needlessly wasting resources.
Another more tangible issue is that we monitor errorneous request to github, and this just adds some additional 404 errors in our metrics, and understanding that metric with this fallback behaviour is bit more complicated.

You can use context.github.config.get now, we can add an fallback repository option there if you like: https://github.com/probot/octokit-plugin-config/. I think I would call it extends, it can work the same way as https://github.com/probot/octokit-plugin-config/


Conditional 4i

Changes to the 4i dataloader and some embedding modules to make cmonge compatable with conditional 4i experiments. Also generalisation of the Perturbation MLP neural network to allow for different conditions (such as drug-dose, drug-drug etc.)

Woohoo checks have passed 🎉

Please review :)


PATCH: Fix Clang compiler flag macro #1

Fixed a bug where a Clang compile macro was used in a possibly error-prone context. Should help resolve #1.

Wrong Repository.


s32z270dc2_r52: add missing vendor and supported drivers

Add missing vendor and supported drivers for the s32z270dc2_r52 boards.
$ west twister -p s32z270dc2_rtu0_r52@D --device-testing --device-serial=/dev/ttyUSB0 -T tests/drivers/spi/ -T tests/drivers/counter/
Renaming output directory to /home/user/zephyrproject/zephyr/twister-out.5
INFO    - Using Ninja..
INFO    - Zephyr version: zephyr-v3.5.0-239-ga5ce568bba5b
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report /home/user/zephyrproject/zephyr/twister-out/testplan.json

Device testing on:

| Platform              | ID   | Serial device   |
|-----------------------|------|-----------------|
| s32z270dc2_rtu0_r52@D |      | /dev/ttyUSB0    |

INFO    - JOBS: 8
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - Total complete:   29/  29  100%  skipped:   27, failed:    0, error:    0
INFO    - 29 test scenarios (29 test instances) selected, 27 configurations skipped (27 by static filter, 0 at runtime).
INFO    - 2 of 29 test configurations passed (100.00%), 0 failed, 0 errored, 27 skipped with 0 warnings in 46.15 seconds
INFO    - In total 11 test cases were executed, 74 skipped on 1 out of total 627 platforms (0.16%)
INFO    - 2 test configurations executed on platforms, 0 test configurations were only built.

@manuargue @danieldegrasse we should add the vendor manually or we should do some updates in dts for this to be added automatically?
I saw this commit https://github.com/zephyrproject-rtos/zephyr/commit/c3827ec48e2acf5f4c6ec9a2c57e8e38b864b1c0 but I'm still not sure what should I do in some cases like for nxp_adsp_imx8m, for example.

@manuargue @danieldegrasse we should add the vendor manually or we should do some updates in dts for this to be added automatically?

Based on the commit message, it looks like the information may have been extracted with a script for the initial PR. I believe that for platforms without a vendor field at this point it is expected that the vendor be added manually.


system76-scheduler breaks suspend and is unable to be stopped

Describe the bug
system76-scheduler attempts to call rmmod kheaders. However, the command hangs indefinitely on the kernel level. Systemd logs:
May 25 20:39:33 nixmsi systemd[1]: Starting Manage process priorities and CFS scheduler latencies for improved responsiveness on the desktop...
May 25 20:39:33 nixmsi system76-scheduler[2268]:    INFO  monitoring process IDs in realtime with execsnoop
May 25 20:39:33 nixmsi systemd[1]: Started Manage process priorities and CFS scheduler latencies for improved responsiveness on the desktop.
May 26 06:17:56 nixmsi systemd[1]: Stopping Manage process priorities and CFS scheduler latencies for improved responsiveness on the desktop...
May 26 06:19:26 nixmsi systemd[1]: system76-scheduler.service: State 'final-sigterm' timed out. Killing.
May 26 06:19:26 nixmsi systemd[1]: system76-scheduler.service: Killing process 2624 (rmmod) with signal SIGKILL.
May 26 06:20:57 nixmsi systemd[1]: system76-scheduler.service: Processes still around after final SIGKILL. Entering failed mode.
May 26 06:20:57 nixmsi systemd[1]: system76-scheduler.service: Failed with result 'timeout'.
May 26 06:20:57 nixmsi systemd[1]: system76-scheduler.service: Unit process 2624 (rmmod) remains running after unit stopped.
May 26 06:20:57 nixmsi systemd[1]: Stopped Manage process priorities and CFS scheduler latencies for improved responsiveness on the desktop.
May 26 06:20:57 nixmsi systemd[1]: system76-scheduler.service: Consumed 1.386s CPU time, read 107.0M from disk, written 0B to disk, no IP traffic.

Additionally, when attempting to suspend, the following happens (dmesg logs):
[34381.731410] PM: suspend entry (s2idle)
[34381.772017] Filesystems sync: 0.040 seconds
[34381.798222] Freezing user space processes
[34401.806399] Freezing user space processes failed after 20.008 seconds (1 tasks refusing to freeze, wq_busy=0):
[34401.806410] task:rmmod           state:D stack:0     pid:2624  ppid:2488   flags:0x00000006
[34401.806414] Call Trace:
[34401.806416]  <TASK>
[34401.806420]  __schedule+0x3e3/0x1380
[34401.806426]  ? avc_has_perm_noaudit+0xa0/0x120
[34401.806430]  schedule+0x5e/0xd0
[34401.806432]  kernfs_drain+0xd6/0x160
[34401.806435]  ? __pfx_autoremove_wake_function+0x10/0x10
[34401.806438]  __kernfs_remove.part.0+0xe4/0x240
[34401.806444]  kernfs_remove_by_name_ns+0x74/0xd0
[34401.806446]  __do_sys_delete_module+0x1d5/0x320
[34401.806450]  do_syscall_64+0x3e/0x90
[34401.806453]  entry_SYSCALL_64_after_hwframe+0x72/0xdc
[34401.806457] RIP: 0033:0x7f643f9699db
[34401.806487] RSP: 002b:00007ffeca9b35b8 EFLAGS: 00000206 ORIG_RAX:<PHONE_NUMBER>0000b0
[34401.806489] RAX: ffffffffffffffda RBX:<PHONE_NUMBER>b3e760 RCX: 00007f643f9699db
[34401.806490] RDX:<PHONE_NUMBER>000000 RSI:<PHONE_NUMBER>000800 RDI:<PHONE_NUMBER>b3e7c8
[34401.806492] RBP:<PHONE_NUMBER>000000 R08:<PHONE_NUMBER>000000 R09: 00007f643f9ddac0
[34401.806492] R10: 00007f643f9de3c0 R11:<PHONE_NUMBER>000206 R12: 00007ffeca9b3810
[34401.806493] R13: 00007ffeca9b5964 R14:<PHONE_NUMBER>b3e2a0 R15: 00007ffeca9b3818
[34401.806495]  </TASK>

Finally, I'm also unable to poweroff normally and have to use hardware reset.
Steps To Reproduce
Steps to reproduce the behavior:

Enable system76-scheduler module: services.system76-scheduler.enable = true;. No further config is necessary
Perhaps some further info can be found in my config: https://github.com/chayleaf/dotfiles/blob/master/system/hosts/nixmsi.nix https://github.com/chayleaf/dotfiles/blob/master/system/modules/common.nix

Expected behavior
system76-scheduler not hanging
Additional context
Version 1.2.2 of system76-scheduler works fine: https://github.com/chayleaf/dotfiles/commit/b60e204f1e041f290ab51d34b00ba404716bff61 fixed the issue for my config
Notify maintainers

@cmm
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.3.1-zen1, NixOS, 23.11 (Tapir), 23.11.20230523.d30264c`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `""`
 - nixpkgs: `/etc/nix/inputs/nixpkgs`

Interesting!  I definitely see no such behavior.
modprobe/rmmod of kheaders is indirectly caused by the execsnoop tool, that's just how BCC (BPF Compiler Collection) works (every tool compiles an injector program when started, and the injector source needs the headers of the running kernel to do its thing).
The only suspicious part of your setup that I can see is the Zen kernel.  I wonder if there are known problems with the Zen kernels and BPF in general or BCC in particular?  Could you try a vanilla kernel?

yes, it works fine on vanilla kernel


PNG icons are rendered at a low resolution

See difference between sfSymbol and PNG image of same icon. It's very clear when looking at a real device.

PNG Icon is rendered at point size 200 with pixel size 10x.
The icon is also rendered incorrectly (too large)

My code
tabBarIcon: ({ color, focused, size }) =>
            require("@/assets/icons/magnifyingglass.png"),

Hey, thanks for opening the issue.
Does it also occur on Android?

I'm having a hard time testing Android, see my other issue.

Hey, the issue with low resolution should be fixed in 0.0.10 let me know if it works for you 😄

They are no longer rendered in a low resolution but the aspect ration is not correct.

Comparison to original SF icon:

Thanks for checking it out @fredrikburmester, changed issue title to add this as a new feature, currently the icon size is a constant. We should either allow for specifying icon size or fix the aspect ratio


Avoid dangling shims

The python2 shim that pyenv installs can result in surprising (and undesirable) behaviour under some circumstances.
Given the following set of Python runtimes:
% pyenv versions
* system (set by /Users/saj/.pyenv/version)
  2.7.10

pyenv rehash will install shims for python, python2, and python2.7.
% ls ~/.pyenv/shims | egrep 'python[0-9\.]*$'
python
python2
python2.7

Suppose we leave system python enabled globally.
% pyenv global
system

System python on my platform, OS X 10.10, is 2.7.6.
% /usr/bin/python -V
Python 2.7.6

OS X provides python and python2.7 files that link to this interpreter.  More importantly, OS X does not provide a python2 link.
% pyenv which python
/usr/bin/python

% pyenv which python2.7
/usr/bin/python2.7

% pyenv which python2
pyenv: python2: command not found

The `python2' command exists in these Python versions:
  2.7.10

With pyenv's shims loaded into my PATH, trying to invoke python2 results in a failure:
% python2 -V
pyenv: python2: command not found

The `python2' command exists in these Python versions:
  2.7.10

This causes obvious problems for software that probe for python2 before python.  The ycmd code completion server is one such example:
https://github.com/Valloric/ycmd/blob/master/ycmd/utils.py#L154
The problem can be worked-around by manually symlinking /usr/bin/python2 to /usr/bin/python, though this is rather smelly.
I take it the shims are built from the set union of all installed Python versions.  Because I have 2.7.10 installed, pyenv found python2 in my 2.7.10 bin/ directory and created the python2 shim to match.
Why is this search based on the set of installed runtimes and not the set of activated runtimes?  (Would it make more sense to rehash after pyenv global instead of pyenv install?)
https://github.com/yyuu/pyenv/blob/8e276a009e592724ae9804cff328baee3a23df20/README.md#choosing-the-python-version
% pyenv global system 2.7.10

% pyenv global
system
2.7.10

% python -V
Python 2.7.6

% python2 -V
Python 2.7.10

% python2.7 -V
Python 2.7.6

This is by design and is not easily avoidable. If the behaviour is unacceptable, I'd recommend you to build PATH by yourself.


Update CI

Use images from paulsengroup/ci-docker-images
Add workflow to collect coverage information

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a4a3c53). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #33   +/-   ##
=======================================
  Coverage        ?   87.36%
=======================================
  Files           ?       41
  Lines           ?     3434
  Branches        ?        0
=======================================
  Hits            ?     3000
  Misses          ?      434
  Partials        ?        0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[BUG] Spark 4.0 build failure - value cannotSaveIntervalIntoExternalStorageError is not a member of object org.apache.spark.sql.errors.QueryCompilationErrors

Describe the bug
Spark 4.0.0 Scala 2.13 nightly build is failing with:
 [ERROR] [Error] /home/jenkins/agent/workspace/jenkins-rapids_scala213_nightly-dev-github-290/sql-plugin/src/main/spark332db/scala/org/apache/spark/sql/rapids/shims/GpuDataSource.scala:126: value cannotSaveIntervalIntoExternalStorageError is not a member of object org.apache.spark.sql.errors.QueryCompilationErrors
Looks like Spark 4.0 removed that function - https://github.com/apache/spark/commit/560748c2b1482836f1fbc117ebb88cee1371554c
We need to create a shim for that file.

PR is up at #11610


Set included files and directories for black

This is so black . doesn't make unintended changes.

After running black on everything, 3 files ended up with changes:
	modified:   changelog.py
	modified:   docs/conf.py
	modified:   docs/create_scheduler_plot.py

If there's no specific reason to include docs, I'd rather black everything.


any suguestions for stacked bubble chart

Feature Proposal

i want to render chart like this. enyone can sugguest which plugin can help please?
Possible Implementation
No response

For these kind of questions please head over to stackoverflow


RTMP pull input

I know that RTMP pull input is not supported (although RTSP is, but it is not in the Feature support matrix of the manual). Would it be difficult to add? There are some RTMP related commits in https://github.com/DDVTECH/mistserver/pull/54, are they related?

Hey Nerijus,
They're unrelated to RTMP input, so I'm afraid it doesn't do much for you. This branch deals with analysis, not input (though they do share a lot of common ground).
RTMP pull input isn't difficult to add, it's just never been (seriously) requested so we've never had a reason to implement it. It is on the roadmap to do "eventually", but it's far from a priority at the moment so it's been keep getting passed over by several other features.


[NIFI-5192] allow expression language in Schema File property

@bartektartanus It fails TestValidateXml. If you run those tests, you'll see that your update doesn't include the evaluateExpressionLanguage calls that are needed to pass validation. So please run those tests and you'll see where you need to add some extra fixes to flesh this out.

I took the liberty of adding the missing evaluateAttributeExpressions() call, the unit tests pass at that point but if Expression Language is present, then we can't count on the File Exists Validator to catch missing schema files. I added a check for file.exists() and unit tests for valid and invalid (with EL). Feel free to cherry-pick https://github.com/mattyb149/nifi/commit/a452382bed64cd4ddda69711e7382829726503ee into your branch and push back up here for review, or @MikeThomsen if you're cool with it you could just cherry pick his and my commits from https://github.com/mattyb149/nifi/tree/NIFI-5192 before merge.

I added my commit, rebased, and squashed, unit tests and contrib-check passes. Thanks for the improvement! Merging to master

@bartektartanus I forgot to add the magic string to the commit that automatically closes this PR, do you mind closing it? It has been merged to master, thanks again!


⚠ ClamAV has degraded performance

In 7a04156, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 237 ms

Resolved: ClamAV performance has improved in ce14b86.


mnist example update to new compile stage API

Description
Update the mnist example to use the new compile_stage api
Checklist:

[x] Has code been commented, particularly in hard-to-understand areas?

https://www.internalfb.com/phabricator/paste/view/P782391812

See new error here: https://www.internalfb.com/phabricator/paste/view/P784276221

I'm currently saving the ckpts for each epoch in its own directory s.t. if were saving for every 500 epochs, there is a dir under "checkpoints"(or whatever other string that may be set as the checkpoint_dir) called 500, another 1000, and so on. What do you think of this design choice?

Could you double check the files changed to make sure that the change is reflected correctly?