text:
python 版本？

我的python是3.7版本的，tensorflow-gpu  安装不了了，最好能把依赖包版本给出来比较好。

13
ConfigProto disappeared in tf 2.0, so an elegant solution is:
import tensorflow as tf
and then replace:
tf.ConfigProto by tf.compat.v1.ConfigProto
In fact, the compatibility built in 2.0 to get tf 1.: tf.compat.v1 is really helpful.
Useful link: Migrate your tensorflow 1. code to tensorflow 2.: https://www.tensorflow.org/guide/migrate
https://stackoverflow.com/questions/56127592/attributeerror-module-tensorflow-has-no-attribute-configproto/56132697

AttributeError: 'google.protobuf.pyext._message.RepeatedScalarConta' object has no attribute '_values' #624
https://github.com/mil-tokyo/webdnn/issues/624


text:
🛑 GetCannab is down

In 6248ca9, GetCannab (https://getcannab.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GetCannab is back up in 274b253 after 21 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
Wallet id

How do I add my wallet address to this ? All 15 containers are running

This part is a bit manually demanding. I have added some docs to readme, should be clear.

repo: ystrem/deploy-rivalz


text:
[Youtube] Default format spec fails to download best video quality

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
France
Provide a description that is worded well enough to be understood
Earlier today I downloaded a video from youtube yt-dlp https://www.youtube.com/watch?v=xB1-qiyDNgw with an old version (yt-dlp-2024.07.16-1). That command successfully identified format 313 (4K VP9 @ ~12MBps) as the superior video quality and downloaded it. I then upgraded to the master branch and typed the same command. This time, yt-dlp selected format 401 (4K AV1 @ ~5MBps). I compared both files and the VP9 is indeed much better compressed. Weird thing is yt-dlp -F does show the 313 format.
I would not have expected the algorithm to change between versions like this. Is this a bug, or just how the new version is supposed to work ?
[~]$ yt-dlp -F https://www.youtube.com/watch?v=xB1-qiyDNgw
[youtube] Extracting URL: https://www.youtube.com/watch?v=xB1-qiyDNgw
[youtube] xB1-qiyDNgw: Downloading webpage
[youtube] xB1-qiyDNgw: Downloading ios player API JSON
[youtube] xB1-qiyDNgw: Downloading mweb player API JSON
[youtube] xB1-qiyDNgw: Downloading m3u8 information
[info] Available formats for xB1-qiyDNgw:
ID      EXT   RESOLUTION FPS CH │   FILESIZE    TBR PROTO │ VCODEC           VBR ACODEC      ABR ASR MORE INFO
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
sb3     mhtml 48x27        0    │                   mhtml │ images                                   storyboard
sb2     mhtml 80x45        0    │                   mhtml │ images                                   storyboard
sb1     mhtml 160x90       0    │                   mhtml │ images                                   storyboard
sb0     mhtml 320x180      0    │                   mhtml │ images                                   storyboard
233     mp4   audio only        │                   m3u8  │ audio only           unknown             [en] Default
234     mp4   audio only        │                   m3u8  │ audio only           unknown             [en] Default
599-drc m4a   audio only      2 │    4.96MiB    31k https │ audio only           mp4a.40.5   31k 22k [en] ultralow, DRC, m4a_dash
600-drc webm  audio only      2 │    5.57MiB    35k https │ audio only           opus        35k 48k [en] ultralow, DRC, webm_dash
599     m4a   audio only      2 │    4.96MiB    31k https │ audio only           mp4a.40.5   31k 22k [en] ultralow, m4a_dash
600     webm  audio only      2 │    5.56MiB    34k https │ audio only           opus        34k 48k [en] ultralow, webm_dash
139-drc m4a   audio only      2 │    7.86MiB    49k https │ audio only           mp4a.40.5   49k 22k [en] low, DRC, m4a_dash
249-drc webm  audio only      2 │    8.16MiB    51k https │ audio only           opus        51k 48k [en] low, DRC, webm_dash
250-drc webm  audio only      2 │   10.45MiB    65k https │ audio only           opus        65k 48k [en] low, DRC, webm_dash
139     m4a   audio only      2 │    7.86MiB    49k https │ audio only           mp4a.40.5   49k 22k [en] low, m4a_dash
249     webm  audio only      2 │    8.15MiB    51k https │ audio only           opus        51k 48k [en] low, webm_dash
250     webm  audio only      2 │   10.45MiB    65k https │ audio only           opus        65k 48k [en] low, webm_dash
140-drc m4a   audio only      2 │   20.87MiB   129k https │ audio only           mp4a.40.2  129k 44k [en] medium, DRC, m4a_dash
251-drc webm  audio only      2 │   20.38MiB   126k https │ audio only           opus       126k 48k [en] medium, DRC, webm_dash
140     m4a   audio only      2 │   20.87MiB   129k https │ audio only           mp4a.40.2  129k 44k [en] medium, m4a_dash
251     webm  audio only      2 │   20.38MiB   126k https │ audio only           opus       126k 48k [en] medium, webm_dash
597     mp4   256x144     12    │    5.28MiB    33k https │ avc1.4d400b      33k video only          144p, mp4_dash
602     mp4   256x144     12    │ ~ 13.70MiB    85k m3u8  │ vp09.00.10.08    85k video only
598     webm  256x144     12    │    3.80MiB    24k https │ vp9              24k video only          144p, webm_dash
269     mp4   256x144     24    │ ~ 27.37MiB   170k m3u8  │ avc1.4D400C     170k video only
160     mp4   256x144     24    │    6.63MiB    41k https │ avc1.4D400C      41k video only          144p, mp4_dash
603     mp4   256x144     24    │ ~ 26.75MiB   166k m3u8  │ vp09.00.11.08   166k video only
278     webm  256x144     24    │   10.67MiB    66k https │ vp09.00.11.08    66k video only          144p, webm_dash
394     mp4   256x144     24    │    8.18MiB    51k https │ av01.0.00M.08    51k video only          144p, mp4_dash
229     mp4   426x240     24    │ ~ 50.04MiB   310k m3u8  │ avc1.4D4015     310k video only
133     mp4   426x240     24    │   13.08MiB    81k https │ avc1.4D4015      81k video only          240p, mp4_dash
604     mp4   426x240     24    │ ~ 46.25MiB   287k m3u8  │ vp09.00.20.08   287k video only
242     webm  426x240     24    │   16.16MiB   100k https │ vp09.00.20.08   100k video only          240p, webm_dash
395     mp4   426x240     24    │   12.96MiB    80k https │ av01.0.00M.08    80k video only          240p, mp4_dash
230     mp4   640x360     24    │ ~ 97.34MiB   604k m3u8  │ avc1.4D401E     604k video only
134     mp4   640x360     24    │   24.44MiB   152k https │ avc1.4D401E     152k video only          360p, mp4_dash
18      mp4   640x360     24  2 │   69.29MiB   430k https │ avc1.42001E          mp4a.40.2       44k [en] 360p
605     mp4   640x360     24    │ ~ 92.85MiB   576k m3u8  │ vp09.00.21.08   576k video only
243     webm  640x360     24    │   28.48MiB   177k https │ vp09.00.21.08   177k video only          360p, webm_dash
396     mp4   640x360     24    │   23.86MiB   148k https │ av01.0.01M.08   148k video only          360p, mp4_dash
231     mp4   854x480     24    │ ~131.86MiB   818k m3u8  │ avc1.4D401E     818k video only
135     mp4   854x480     24    │   42.81MiB   266k https │ avc1.4D401E     266k video only          480p, mp4_dash
606     mp4   854x480     24    │ ~148.43MiB   921k m3u8  │ vp09.00.30.08   921k video only
244     webm  854x480     24    │   39.98MiB   248k https │ vp09.00.30.08   248k video only          480p, webm_dash
397     mp4   854x480     24    │   34.50MiB   214k https │ av01.0.04M.08   214k video only          480p, mp4_dash
232     mp4   1280x720    24    │ ~211.04MiB  1309k m3u8  │ avc1.4D401F    1309k video only
136     mp4   1280x720    24    │   73.72MiB   457k https │ avc1.4D401F     457k video only          720p, mp4_dash
609     mp4   1280x720    24    │ ~242.98MiB  1508k m3u8  │ vp09.00.31.08  1508k video only
247     webm  1280x720    24    │   67.70MiB   420k https │ vp09.00.31.08   420k video only          720p, webm_dash
398     mp4   1280x720    24    │   61.24MiB   380k https │ av01.0.05M.08   380k video only          720p, mp4_dash
270     mp4   1920x1080   24    │ ~609.62MiB  3782k m3u8  │ avc1.640028    3782k video only
137     mp4   1920x1080   24    │  269.46MiB  1672k https │ avc1.640028    1672k video only          1080p, mp4_dash
614     mp4   1920x1080   24    │ ~426.37MiB  2645k m3u8  │ vp09.00.40.08  2645k video only
248     webm  1920x1080   24    │  129.84MiB   806k https │ vp09.00.40.08   806k video only          1080p, webm_dash
399     mp4   1920x1080   24    │  100.20MiB   622k https │ av01.0.08M.08   622k video only          1080p, mp4_dash
620     mp4   2560x1440   24    │ ~  1.25GiB  7911k m3u8  │ vp09.00.50.08  7911k video only
271     webm  2560x1440   24    │  654.44MiB  4060k https │ vp09.00.50.08  4060k video only          1440p, webm_dash
400     mp4   2560x1440   24    │  386.20MiB  2396k https │ av01.0.12M.08  2396k video only          1440p, mp4_dash
625     mp4   3840x2160   24    │ ~  2.95GiB 18712k m3u8  │ vp09.00.50.08 18712k video only
313     webm  3840x2160   24    │    2.00GiB 12729k https │ vp09.00.50.08 12729k video only          2160p, webm_dash
401     mp4   3840x2160   24    │  884.20MiB  5486k https │ av01.0.12M.08  5486k video only          2160p, mp4_dash

Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://www.youtube.com/watch?v=xB1-qiyDNgw']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version stable@2024.12.06 from yt-dlp/yt-dlp [4bd265539] (zip)
[debug] Python 3.12.4 (CPython x86_64 64bit) - Linux-6.6.40-1-MANJARO-x86_64-with-glibc2.39 (OpenSSL 3.3.1 4 Jun 2024, glibc 2.39)
[debug] exe versions: ffmpeg 7.0.1 (setts), ffprobe 7.0.1, rtmpdump 2.4
[debug] Optional libraries: requests-2.32.3, sqlite3-3.46.0, urllib3-1.26.18
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests
[debug] Loaded 1837 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: stable@2024.12.06 from yt-dlp/yt-dlp
yt-dlp is up to date (stable@2024.12.06 from yt-dlp/yt-dlp)
[youtube] Extracting URL: https://www.youtube.com/watch?v=xB1-qiyDNgw
[youtube] xB1-qiyDNgw: Downloading webpage
[youtube] xB1-qiyDNgw: Downloading ios player API JSON
[youtube] xB1-qiyDNgw: Downloading mweb player API JSON
[debug] Loading youtube-nsig.3bb1f723 from cache
[debug] [youtube] Decrypted nsig xl62fMTiEtXV1pV7l9 => gbZJrcF-HEABsA
[debug] Loading youtube-nsig.3bb1f723 from cache
[debug] [youtube] Decrypted nsig cvr9IBhchq799JDHlz => s8xjJNbrM2HVAQ
[youtube] xB1-qiyDNgw: Downloading m3u8 information
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec, channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] xB1-qiyDNgw: Downloading 1 format(s): 401+251
[debug] Invoking http downloader on "https://rr1---sn-n4g-ator.googlevideo.com/videoplayback?expire=1733888860&ei=_LZYZ6DtHoXZxN8P_ZC4kAg&ip=2a02%3A8429%3Ae0%3Ac501%3A9263%3A3fe4%3Af4a1%3A13d2&id=o-AExfeAHCt8Qf3lK9afo_YM3UtWpHnJ0Fab4ToVEVUjt9&itag=401&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&met=1733867260%2C&mh=Kz&mm=31%2C29&mn=sn-n4g-ator%2Csn-n4g-jqbek&ms=au%2Crdu&mv=m&mvi=1&pl=47&rms=au%2Cau&initcwndbps=1807500&bui=AQn3pFRTmrpw0xQcigyiagdrbmjcw7dkOKhVLoBxK7127H2Nnx1A_9WBIYBeELZPocaTKDxYI-M7cgFK&spc=qtApAWW1pLp_NehE48AjTHyTcyVck-6POgLo6LW-70wLWxwBMw&vprv=1&svpuc=1&mime=video%2Fmp4&rqh=1&gir=yes&clen=927147829&dur=1352.100&lmt=1727133149375441&mt=1733866879&fvip=6&keepalive=yes&fexp=51326932%2C51335594%2C51347746&c=IOS&txp=543G434&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&sig=AJfQdSswRgIhANHbjJj52rHFOLMcobLKNeIE0IAFDZxVyyP3yZV-c8ARAiEA6WGaUpmInZujLcHkUt2IrQMEqUCTow1e0-qIiljJn7A%3D&lsparams=met%2Cmh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Crms%2Cinitcwndbps&lsig=AGluJ3MwRQIgCC3JN-0s4goPgZ2kj8fk5pntguD6rxqiJSgUg8X2vaACIQDYx0iHsdl7KuFmjpFAAM35-ZozeNu78O69fnz5U-3d2A%3D%3D"
[download] Destination: Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].f401.mp4
[download] 100% of  884.20MiB in 00:00:18 at 47.34MiB/s
[debug] Invoking http downloader on "https://rr1---sn-n4g-ator.googlevideo.com/videoplayback?expire=1733888860&ei=_LZYZ6DtHoXZxN8P_ZC4kAg&ip=2a02%3A8429%3Ae0%3Ac501%3A9263%3A3fe4%3Af4a1%3A13d2&id=o-AExfeAHCt8Qf3lK9afo_YM3UtWpHnJ0Fab4ToVEVUjt9&itag=251&source=youtube&requiressl=yes&xpc=EgVo2aDSNQ%3D%3D&met=1733867260%2C&mh=Kz&mm=31%2C29&mn=sn-n4g-ator%2Csn-n4g-jqbek&ms=au%2Crdu&mv=m&mvi=1&pl=47&rms=au%2Cau&initcwndbps=1807500&bui=AQn3pFRTmrpw0xQcigyiagdrbmjcw7dkOKhVLoBxK7127H2Nnx1A_9WBIYBeELZPocaTKDxYI-M7cgFK&spc=qtApAWW1pLp_NehE48AjTHyTcyVck-6POgLo6LW-70wLWxwBMw&vprv=1&svpuc=1&mime=audio%2Fwebm&rqh=1&gir=yes&clen=21368634&dur=1352.121&lmt=1727128763812550&mt=1733866879&fvip=6&keepalive=yes&fexp=51326932%2C51335594%2C51347746&c=IOS&txp=5432434&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cxpc%2Cbui%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Crqh%2Cgir%2Cclen%2Cdur%2Clmt&sig=AJfQdSswRAIgWCsOR_lnhwk7Ej7BJYoV92wkQ23yUmWPNVXiM8Mv-54CIGB_yKWlUMFDZGtMpUrfAejaJjExt9rYonWRvaKBOy8B&lsparams=met%2Cmh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Crms%2Cinitcwndbps&lsig=AGluJ3MwRQIgCC3JN-0s4goPgZ2kj8fk5pntguD6rxqiJSgUg8X2vaACIQDYx0iHsdl7KuFmjpFAAM35-ZozeNu78O69fnz5U-3d2A%3D%3D"
[download] Destination: Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].f251.webm
[download] 100% of   20.38MiB in 00:00:01 at 18.56MiB/s
[Merger] Merging formats into "Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].webm"
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i 'file:Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].f401.mp4' -i 'file:Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].f251.webm' -c copy -map 0:v:0 -map 1:a:0 -movflags +faststart 'file:Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].temp.webm'
Deleting original file Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].f401.mp4 (pass -k to keep)
Deleting original file Why In the Mood for Love Pushed Wong Kar Wai to the Edge [xB1-qiyDNgw].f251.webm (pass -k to keep)

With 2024.11.04 yt-dlp started to prioritize av1 (or more correctly no longer de-prioritize av1). You can revert this by using --compat-options prefer-vp9-sort or passing a custom format sort option.
There may be cases where this yields worse video quality. However, it is impossible for yt-dlp to predict what format will have the best video quality. In general, more modern codecs are preferred.

Thank you @seproDev , that worked.
I understand it is impossible for yt-dlp to predict what format will have the best video quality but, on paper, AV1 is supposed to offer 30% better compression than VP9 so, maybe, the algorithm could look at bitrates to determine quality between two codecs at equal resolution (in this case, VP9 would have won because the AV1 bitrate is almost 60% below the VP9 bitrate). Just a thought. My initial question is answered. Feel free to close if you think this is veering off the original ticket too much.

I'm closing, as my initial question was answered. I'll follow #8488 for the other idea. Thanks again :)

With 2024.11.04 yt-dlp started to prioritize av1 (or more correctly no longer de-prioritize av1). You can revert this by using --compat-options prefer-vp9-sort or passing a custom format sort option.

Sorry to bump a closed thread, but since it's related to my question: I wanted to confirm that --compat-options prefer-vp9-sort  will revert the format preferences to how they were before. The devices I use aren't compatible with av1, but I have no problem with the other codecs, and I would like yt-dlp to choose the "best" one between them as it did before youtube started prioritizing av1.

authors: DDDespair seproDev thomas-mckay

repo: yt-dlp/yt-dlp

license: Unlicense


text:
ライフゲームの各種パターンを選択して描画できるようにする

ゴール

グライダーやグライダー銃など、ライフゲームの各種パターンを選択して、描画できるようにする

対応方針

プルダウンリストでパターンを選択できるようにする
選択すると、シャーレを全てクリアした後で、選択パターンの描画を行う
描画位置はどうする？特に希望するものはない
パターンとは別に、「ランダム配置」という選択肢も欲しい

現状の初期値のようにランダムでセルの生死状態を振り分けるイメージ

理想としては以下のように、パターンを選択した後で自由な位置に配置できるとよい

https://cafeunder.github.io/LifeColor/

ただ、マウス操作（カーソル有）が前提となるため、キーボードやスマホ操作だと実現が容易でなさそう

描画位置はどうする？特に希望するものはない

左角の1セル右下から描画を開始する仕様とした
+####...    // +: 左角
#*###...    // *: 1セル右下
#####...
#####...
#####...
:::::...

repo: ytak-sagit/game-of-life-react


text:
Question: How do you download --all-formats except webm?

I'm trying to download all formats for DASH support using this article:
https://shkspr.mobi/blog/2017/07/using-youtube-to-transcode-videos-to-dash-on-the-command-line/
My question is: How can I download everything except .webm files?

If you're doing this for DASH support, I'd use the Python library with some scripting.

What do you mean? Is there some sample code you can refer to?
On Tue, Jun 4, 2019, 10:11 AM ealgase notifications@github.com wrote:

If you're doing this for DASH support, I'd use the Python library with
some scripting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ytdl-org/youtube-dl/issues/21293?email_source=notifications&email_token=ABLI5FU2MD6YN7K3BDGWIO3PYZZZDA5CNFSM4HSWILZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW4WB6Y#issuecomment-498688251,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLI5FUGFBK4EYNZV7GABWTPYZZZDANCNFSM4HSWILZA
.

Do you know Python?

Very little but I'm open to it
On Tue, Jun 4, 2019, 3:33 PM ealgase notifications@github.com wrote:

Do you know Python?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ytdl-org/youtube-dl/issues/21293?email_source=notifications&email_token=ABLI5FSLIODF5NZJY4NGLVTPY27O5A5CNFSM4HSWILZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW5T53I#issuecomment-498810605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLI5FWM5VF3KUHRMPWUXQ3PY27O5ANCNFSM4HSWILZA
.

Install the youtube-dl Python module and check out the documentation https://github.com/ytdl-org/youtube-dl#embedding-youtube-dl (not great but you should be able to look up the functionality you need).

Thanks! Guess I have to learn some py
On Tue, Jun 4, 2019, 6:18 PM ealgase notifications@github.com wrote:

Install the youtube-dl Python module and check out the documentation
https://github.com/ytdl-org/youtube-dl#embedding-youtube-dl (not great
but you should be able to look up the functionality you need).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ytdl-org/youtube-dl/issues/21293?email_source=notifications&email_token=ABLI5FQQ4YWAFXP636Y3CIDPY3S2HA5CNFSM4HSWILZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6A6FI#issuecomment-498863893,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLI5FUEXK76TJFDQLEAVRTPY3S2HANCNFSM4HSWILZA
.

authors: TimeTravelersHackedMe ealgase

repo: ytdl-org/youtube-dl


text:
YouTube download link is not responding on browser or youtube-dl downloader

Checklist

[ ] I'm reporting a broken site support issue
[X] I've verified that I'm running youtube-dl version 2019.09.01
[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 bug reports including closed ones
[X] I've read bugs section in FAQ

Verbose log

[antonyjr@liz Videos]$ ./youtube-dl -v "https://www.youtube.com/watch?v=BAv8_mF0d5M"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.youtube.com/watch?v=BAv8_mF0d5M']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.09.01
[debug] Python version 3.7.4 (CPython) - Linux-4.19.66-1-MANJARO-x86_64-with-arch-Manjaro-Linux
[debug] exe versions: ffmpeg 4.2, ffprobe 4.2, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] BAv8_mF0d5M: Downloading webpage
[youtube] BAv8_mF0d5M: Downloading video info webpage
[youtube] {18} signature length 109, html5 player vflA49sb0
[youtube] {313} signature length 109, html5 player vflA49sb0
[youtube] {271} signature length 109, html5 player vflA49sb0
[youtube] {137} signature length 109, html5 player vflA49sb0
[youtube] {248} signature length 109, html5 player vflA49sb0
[youtube] {136} signature length 109, html5 player vflA49sb0
[youtube] {247} signature length 109, html5 player vflA49sb0
[youtube] {135} signature length 109, html5 player vflA49sb0
[youtube] {244} signature length 105, html5 player vflA49sb0
[youtube] {134} signature length 105, html5 player vflA49sb0
[youtube] {243} signature length 109, html5 player vflA49sb0
[youtube] {133} signature length 109, html5 player vflA49sb0
[youtube] {242} signature length 109, html5 player vflA49sb0
[youtube] {160} signature length 109, html5 player vflA49sb0
[youtube] {278} signature length 109, html5 player vflA49sb0
[youtube] {140} signature length 109, html5 player vflA49sb0
[youtube] {249} signature length 109, html5 player vflA49sb0
[youtube] {250} signature length 109, html5 player vflA49sb0
[youtube] {251} signature length 109, html5 player vflA49sb0
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://r2---sn-cnoa-cagl.googlevideo.com/videoplayback?expire=1567551681&ei=YZxuXaeLEoiE1Aa655mgDQ&ip=117.254.34.147&id=o-ACUA0MLT07CSytnbe46z36UJ2s64hrEyO26k4l3oiRT0&itag=313&aitags=133%2C134%2C135%2C136%2C137%2C160%2C242%2C243%2C244%2C247%2C248%2C271%2C278%2C313&source=youtube&requiressl=yes&mm=31%2C29&mn=sn-cnoa-cagl%2Csn-h5576n7k&ms=au%2Crdu&mv=m&mvi=1&pl=23&initcwndbps=858750&mime=video%2Fwebm&gir=yes&clen=131206075&dur=186.760&lmt=1562005608749684&mt=1567529986&fvip=5&keepalive=yes&c=WEB&txp=4531432&sparams=expire%2Cei%2Cip%2Cid%2Caitags%2Csource%2Crequiressl%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&lsparams=mm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AHylml4wRgIhAJmO90biO6tUBR-f5dWDpfkOXlXrmarSi3TeotRokc3rAiEAlcgrpGUEXVVgZVieLZqqgkW0vuZk1-7xnjxB8lJokLs%3D&sig=ALgxI2wwRQIhAPLRucQAHbmbdigu70Jmo72o9OJEQKBMNqOGTDGf6m3-AiBemsxkyl7xvrlmVmv14W34dwdnRChewLc3a3k5n6cpVA==&ratebypass=yes'

Description

I tried to download a youtube video and the download link extraction seems to work perfect but when the downloader is initiated with the download link, the link does not respond, in the browser or in any other downloader, let alone youtube-dl's internal downloader. I think google is doing something to avoid tools like this to download their content. Any ideas??? Am I the only one facing this issue. This issue works with any youtube link, so feel free to try.

@dstftw At least add a reference to the original issue before closing this, it would be much helpful than labeling this issue as duplicate.


text:
Youtube: Unable to extract uploader id

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.12.17
[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 bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log
$ youtube-dl -citk --verbose --extract-audio --audio-format mp3 "https://www.youtube.com/watch?v=D4EQL_ic6ms"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-citk', '--verbose', '--extract-audio', '--audio-format', 'mp3', 'https://www.youtube.com/watch?v=D4EQL_ic6ms']
WARNING: --title is deprecated. Use -o "%(title)s-%(id)s.%(ext)s" instead.
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.10.6 (CPython) - Linux-6.2.6-76060206-generic-x86_64-with-glibc2.35
[debug] exe versions: ffmpeg 4.4.2, ffprobe 4.4.2, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] D4EQL_ic6ms: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
    'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
  File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
This is probably due to a youtube changes since that was working 1 or 2 week ago.
When trying to download any youtube video, I'm getting that error.

OP:

[x] I've searched the bugtracker for similar bug reports including closed ones

Learn how by reading #30839 (again?).

[x] I've read bugs section in FAQ

Apply this.
Other commenters: #30839 too.

Hello @dirkf
Thanks for your response. There are so many noise in the issue tracker that it's impossible to find the real duplicate. could you link it to me ? I can't find it.

Have you actually read #30839 where the known issue is listed?

Hello @dirkf
Thanks a lot of pointing out to the list of know issues ! I found #31530 to be similar to my ticket. And the solution fixed the problem.
Thanks

I understand that a project like youtube-dl might have a huge user base and handling tickets might be challenging.  Considering the number of duplicates, you might consider defining the list of known issue in the issue template directly. Or in the README file. That is the place where I looked first.
The README file is really the place where I would have gone for most project to have a list of Known Issues. Or at lest a link to the known issues.

Did you find the pinned issue not prominent enough?
Unfortunately, even client-side JS couldn't make it grab the user by the throat. The only way to make it more obvious would be to pin two more issues like this
<---- Look here ----


text:
Fix log message

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Shipped!

source: gharchive/pull-request

authors: Kontakter gritukan

repo: ytsaurus/ytsaurus


text:
#5013 [YCQL] make ycqlsh python3 compatible

Applying the following commit from cassandra project
https://github.com/apache/cassandra/commit/bf9a1d487b9ba469e8d740cf7d1cd419535a7e79
to current version of ycqlsh in YB repository (3.10)
Merge was almost trivial with some manual work.
Test plan:

run cqlsh by python2 and python3

@d-uspenskiy, could you add some details to the PR message?

Test Plan : did the test script within the cqlsh repo pass for both 2 and 3?
Was it a straightforward port or were there some non trivial changes during the port?

Honestly, there's a lot of changes in there, so probably going to make a best effort pass and accept, unless @mbautin has the time for a more detailed review.

@iSignal I've updated the description

authors: d-uspenskiy iSignal

repo: yugabyte/cqlsh


text:
[Question] Can I remove rootfs.tar.gz after a successful Arch install and setup?

This is not a bug report. I'm just curious whether I can safely remove the rootfs.tar.gz file after I successfully installed and set up Arch.
I installed using the "zip file" method, and obviously Arch.exe and ext4.vhdx are super important -- but what exactly does rootfs.tar.gz do (with a size > 3GB)? Excuse my ignorance, I'm rather new to manually installing distros with WSL2.
Thanks for the help.

It's an archive / snapshot of a working Arch Linux's file system. You can create your own, too.
If you can be sure that you won't need to install from the ground up again, you can remove it, create backup for your current Arch WSL, and only use that afterwards.


text:
Latest release broke the pacman and keys

Describe the issue
Latest release (22.10.2.0) broke the pacman and keys
To Reproduce

Download Arch_Online.zip
Extract archive
Run "Arch.exe"
Wait for download rootfs.tar.gz
Press "Enter"
Run "Arch.exe" again
Run "sudo pacman-key --init"

Expected behavior
Should be executed without errors
Screenshots

Enviroment:

Windows build number: 10.0.22621.607
Security Software: -
WSL version 1/2: WSL2
ArchWSL version: 22.10.2.0
ArchWSL Installer type: zip, online
Launcher version: 22020900

I confirmed this issue. I'll fix it.
Thank you.

I fixed this issue in new release!


text:
🛑 Home is down

In b760084, Home (https://yukbid.com) was down:

HTTP code: 502
Response time: 4895 ms

Resolved: Home is back up in 2883567.

repo: yukbid/upptime


text:
improve: Merge latest main to release/2.0.0

Issue

close #105

Overview (Required)
Merge latest main to release/2.0.0

@blendthink
このブランチfeature/merge-mainのブランチ元が最新でないrelease/2.0.0となっていますが、
コンフリクトしないので問題ないという認識でしょうか？
自分は問題ないという認識です!

@Yamasaki-pan961

Is it OK because there is no conflict?

Yes!
Thank you!

repo: yumemi-inc/flutter-yumemi-lints


text:
session 9 の実装

概要

session 9 の課題を実装しました。
セッションリンク

https://github.com/yumemi-inc/ios-training/blob/main/Documentation/ThreadBlock.md
変更点

UIActivityIndicatorView の表示

スクリーンショット

@ykws
コメントありがとうございます。
確かに HomePresenterOutput に関数を追加したのが影響し、テストのビルドが通らなくなっていました。
f71f09cb46b8f2fce85ed92f56e42e17e3371950
上記のコミットで対応しました。
非同期の対応は元々実装を非同期を想定していたので、 session 8 でそれに基づいた実装を行いました。
また、テストを毎回確認するより CI がいた方が良さそうだったので、 actions を使うことをやってみました。
https://github.com/yumemi-inc/ios-training-bjung/pull/11
https://zenn.dev/yumemi_inc/articles/xctest-github-actions
ちょうどこの記事を参考にしていましたが、ローカルではプロジェクトが見つからないというのと、マージされてないので actions タブで結果が見れなく困ってました。
時間あるときレビューしていただけると助かります。

非同期を先取りして実装されているため無意味な指摘になりますけれど、HomePresenterInput 処理の重たい API に変えても何も影響を受けないところが面白かったです。

ただし仮に「スレッドブロック」の課題に純粋に取り組んだとしたとき、WeatherModelInput の fetchWeatherData(request:) async throws が「async」指定で非同期呼出を求めてしまうため、ここでスレッドブロックの API が実質的に非同期 API として吸収されてしまうのが気になりました。
問題はないのですが、一般的な視点で「非同期処理を必要としない YumemiWeather.syncFetchWeather(json:) throws をほぼ単純にラップする WeatherModel.fetchWeatherData(request:) async throws で非同期メソッドとして備えるところが、何も間違いはないのですが、些か過剰な強化のようにも感じます。ここの async をなくしてコードの変化を見てみても面白いかもしれないです。

@es-kumagai
コメントありがとうございます。
確かに課題としては過剰かもしれないですが、これでメインスレッド止まったらダメだろ。。という気持ちでした。（そのためあらかじめ非同期の仕組みを見ていました）
そしてローカルで async を削除して動きを見てみました。予想通り何もタップできない状態で、ロード中にタップした close が通信終了後に反応して、なるほど、と思いました。

@novr @ykws @es-kumagai
レビューありがとうございます。こちらマージします。

authors: askldfghj es-kumagai

repo: yumemi-inc/ios-training-bjung


text:
[文档/Docs] kylin OS x86 架构安装问题

What part of the document needs to be added:
kylinos x86环境下安装时缺少https://iso.yunion.cn/kylin/v10-sword/3.10/x86_64/kylin-yunion.repo文件

@lvzhiweilv
已经修复~

authors: lvzhiweilv zhasm

repo: yunionio/cloudpods


text:
Automated cherry pick of #6531: fix: gcp bucket文件夹默认设为private

Cherry pick of #6531 on release/3.2.
#6531: fix: gcp bucket文件夹默认设为private

Codecov Report

Merging #6532 into release/3.2 will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.2    #6532      +/-   ##
===============================================
- Coverage         7.04%    7.02%   -0.02%
===============================================
  Files              649      650       +1
  Lines           111531   111575      +44
===============================================
- Hits              7858     7843      -15
- Misses          103065   103123      +58
- Partials           608      609       +1

Flag
Coverage Δ

#aFlag
7.02% <0.00%> (-0.02%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/compute/models/guest_queries.go
0.00% <0.00%> (ø)

pkg/compute/models/guests.go
0.56% <ø> (ø)

pkg/monitor/alerting/conditions/query.go
0.64% <0.00%> (ø)

pkg/monitor/alerting/conditions/reducer.go
95.87% <0.00%> (-2.02%)
:arrow_down:

.../monitor/alerting/conditions/suggestrulereducer.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/host.go
0.94% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/storage.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/vdisk.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/virtualmachine.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/lockman/fifo.go
80.00% <0.00%> (-10.00%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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

authors: codecov-commenter ioito

repo: yunionio/onecloud


text:
Automated cherry pick of #6760: image support generate name

Cherry pick of #6760 on release/3.2.
#6760: image support generate name

Codecov Report

Merging #6761 into release/3.2 will increase coverage by 0.00%.
The diff coverage is 4.06%.

@@             Coverage Diff              @@
##           release/3.2    #6761   +/-   ##
============================================
  Coverage         7.03%    7.04%
============================================
  Files              650      650
  Lines           111812   111852   +40
============================================
+ Hits              7869     7877    +8
- Misses          103334   103367   +33
+ Partials           609      608    -1

Flag
Coverage Δ

#aFlag
7.04% <4.06%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

pkg/baremetal/tasks/bm_register.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/ipmiprobe.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/fetch.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/namevalidator.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/opslog.go
1.49% <0.00%> (-0.02%)
:arrow_down:

pkg/cloudcommon/db/scoperesource.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/standalone.go
1.65% <0.00%> (-0.04%)
:arrow_down:

pkg/cloudcommon/db/tenantcache.go
2.96% <0.00%> (-0.32%)
:arrow_down:

pkg/cloudcommon/policy/resources.go
0.00% <ø> (ø)

pkg/cloudprovider/cloudprovider.go
1.53% <0.00%> (ø)

... and 35 more

Continue to review full report at Codecov.

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

/lgtm
/approve

authors: codecov-commenter wanyaoqi zexi


text:
fix(region): apsara is private cloud

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[ ] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.6

/area region
/cc @zexi

Codecov Report

Merging #9064 (f27ab3c) into master (e1c4885) will decrease coverage by 1.64%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9064       +/-   ##
==========================================
- Coverage    5.87%   4.22%    -1.65%
==========================================
  Files         828     166      -662
  Lines      129238   24909   -104329
==========================================
- Hits         7588    1053     -6535
+ Misses     120969   23760    -97209
+ Partials      681      96      -585

Flag
Coverage Δ

aFlag
4.22% <ø> (-1.65%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/keystone/models/groups.go

pkg/hostman/isolated_device/isolated_device.go

pkg/util/seclib2/seclib.go

pkg/multicloud/aws/routetable.go

pkg/compute/models/groupguests.go

pkg/compute/models/loadbalancerbackendgroups.go

pkg/util/gin/middleware/keystone_auth.go

pkg/apis/api.go

pkg/util/cloudinit/cloudconfig.go

pkg/baremetal/manager.go

... and 652 more

Continue to review full report at Codecov.

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

authors: codecov-io ioito


text:
下拉以及上滑的一个问题

发现的一个问题：下拉以及上滑出现图片闪烁，希望可以及时修正

好的，已经重现该问题了。谢谢反馈

@ShineBright2015 我修改了 RoundImageView 的代码，现在你下载最新的代码试试还有没有这个问题。

@ShineBright2015 现在将该 issue 关闭，如果还有问题再 reopen

repo: yuqirong/CardSwipeLayout


text:
Скласти таймлайн

Скласти список всіх (важливих) життєвих подій, визначних дат, досягнень, періодів, що дали приємний і неприємний досвід, тощо. В цьому конкретному випадку довгих списків не буває, натомість бувають погано згорнуті, тому пакуємо сюди все підряд, а про "лишні" події можна буде промовчати пізніше. Список повинен бути систематизованим і посортованим в такий спосіб, щоб читач швидко зрозумів "паттерн" і міг легко орієнтуватись в просторі і часі цього резюме.

Головне вчасно виконати!

repo: yura-kiv/homepage


text:
プログラミング教室のコンテンツ拡充

デザインURL

slackにて共有

やったこと

コース一覧ページの追加

TOPページ

curriculumコンテンツでは、サマリーだけに変更
応じて、教室の場所は「アクセス」コンテンツとして切り出し

詳細ページの新規作成

よくある質問の追加
教室の風景を追加

実態のある教室であることを早め（FV下）で伝えて安心感を

ヘッダーにCTAの追加

LPが増えてCTAが下がるので、追従ヘッダーにボタンを入れておく

講師を写真に
身に付くスキルコンテンツ追加

確認したいところ
ソフトウェア開発・上級コース

スライドに詳細がないので対応方法相談

詳細ページを作らない場合：コース一覧に載せるかどうか
詳細ページを作る場合：コンテンツをもらいたい

身に付くスキルコンテンツについて

どこに入れるか
A. TOPに入れる＠一旦Aで入れました
B. コース詳細に入れる
C. 別ページで作る

上級コース

今現時点では用意してないので、詳細ページ作らなくてOK
コース一覧にも載せなくてOK
身につくスキルはTOPに入れるでお願いしたい！

repo: yutaroud/rect


text:
url routing?

what is the proper way to route values from url or hash and respond to url changes?

If you are using vue version 0.11, refer to "Routing" section of this guide page.
If you are on 0.12, there is vue-router which is in progress yet, but should already work.
Check out issue reporting guidelines to report only appropriate issues to this repo.

Thanks! Exactly what i was looking for.
For the 1.2 will it also support hashbang?

authors: azamat-sharapov villanus

license: mit

license_source: bigquery


text:
Load squeak display entry without deserializing squeak object

The entry class should be able to load all fields directly from database.

Possibly also delete SqueakEntryWithProfile class.

https://github.com/yzernik/squeaknode/pull/1052

repo: yzernik/squeaknode


text:
Question: How can I disable Admin-Authentification

My application runs in an private network and all users are authentificated with Gitlab-Authentification.
I would like to use the existing authentification also for Admin. Is it possible?

Yes, it's possible.
First you need to define a user provider according to adding-custom-user-providers,  then change the auth config:
// config/admin.php

    'auth' => [
        'guards' => [
            'admin' => [
                'driver' => 'session',
                'provider' => 'admin',
            ]
        ],

        'providers' => [
            'admin' => [
                'driver' => 'custom', // specify the custom provider you defined
            ]
        ],
    ],

Added a document custom-authentication

authors: AntoninSlejska z-song

repo: z-song/laravel-admin


text:
demo项目及官网注册异常

demo项目密码好像被改了，之前可以用admin/admin登陆，现在无法登陆
官网 https://discuss.laravel-admin.org/  无法注册，报500错,因此无法在社区发帖求助此问题

页面报错信息

Illuminate\Contracts\Validation\ValidationException:  in file /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Core/Validator/AbstractValidator.php on line 64
Stack trace:
  1. Illuminate\Contracts\Validation\ValidationException->() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Core/Validator/AbstractValidator.php:64
  2. Flarum\Core\Validator\AbstractValidator->assertValid() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Core/Command/RegisterUserHandler.php:137
  3. Flarum\Core\Command\RegisterUserHandler->handle() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/bus/Dispatcher.php:202
  4. call_user_func() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/bus/Dispatcher.php:202
  5. Illuminate\Bus\Dispatcher->Illuminate\Bus\{closure}() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/pipeline/Pipeline.php:139
  6. call_user_func() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/pipeline/Pipeline.php:139
  7. Illuminate\Pipeline\Pipeline->Illuminate\Pipeline\{closure}() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/pipeline/Pipeline.php:102
  8. call_user_func() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/pipeline/Pipeline.php:102
  9. Illuminate\Pipeline\Pipeline->then() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/bus/Dispatcher.php:204
 10. Illuminate\Bus\Dispatcher->dispatchNow() /usr/local/app/discuss.laravel-admin.org/vendor/illuminate/bus/Dispatcher.php:177
 11. Illuminate\Bus\Dispatcher->dispatch() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Api/Controller/CreateUserController.php:45
 12. Flarum\Api\Controller\CreateUserController->data() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Api/Controller/AbstractSerializeController.php:97
 13. Flarum\Api\Controller\AbstractSerializeController->handle() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Api/Controller/AbstractCreateController.php:23
 14. Flarum\Api\Controller\AbstractCreateController->handle() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Api/Client.php:69
 15. Flarum\Api\Client->send() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Forum/Controller/RegisterController.php:60
 16. Flarum\Forum\Controller\RegisterController->handle() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Handler/ControllerRouteHandler.php:53
 17. Flarum\Http\Handler\ControllerRouteHandler->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/DispatchRoute.php:69
 18. Flarum\Http\Middleware\DispatchRoute->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 19. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 20. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 21. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/SetLocale.php:51
 22. Flarum\Http\Middleware\SetLocale->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 23. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 24. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 25. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/AuthenticateWithSession.php:36
 26. Flarum\Http\Middleware\AuthenticateWithSession->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 27. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 28. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 29. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/RememberFromCookie.php:39
 30. Flarum\Http\Middleware\RememberFromCookie->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 31. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 32. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 33. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/StartSession.php:48
 34. Flarum\Http\Middleware\StartSession->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 35. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 36. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 37. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/ParseJsonBody.php:31
 38. Flarum\Http\Middleware\ParseJsonBody->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 39. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 40. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 41. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/Middleware/HandleErrors.php:61
 42. Flarum\Http\Middleware\HandleErrors->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:212
 43. Zend\Stratigility\Dispatch->dispatchCallableMiddleware() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Dispatch.php:88
 44. Zend\Stratigility\Dispatch->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/Next.php:160
 45. Zend\Stratigility\Next->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-stratigility/src/MiddlewarePipe.php:111
 46. Zend\Stratigility\MiddlewarePipe->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/AbstractServer.php:55
 47. Flarum\Http\AbstractServer->__invoke() /usr/local/app/discuss.laravel-admin.org/vendor/zendframework/zend-diactoros/src/Server.php:166
 48. Zend\Diactoros\Server->listen() /usr/local/app/discuss.laravel-admin.org/vendor/flarum/core/src/Http/AbstractServer.php:36
 49. Flarum\Http\AbstractServer->listen() /usr/local/app/discuss.laravel-admin.org/index.php:18```

是啊，demo登录不进去

authors: ieliwb malphitee


text:
remove use of env() outside config files

env() does not work when configuration files are cached and should only be used in config files.
src/Form/Field/Map.php should be updated as well, and the API keys need to moved to a config file
see https://laravel.com/docs/5.8/configuration#configuration-caching

Thanks！

authors: langeuh z-song


text:
bugfix: can't create list

because rpush is http PUT method, use lstore request by http POST method can route to Encore\RedisManager\DataType\Lists::store()

Thanks!

authors: hemon z-song

repo: z-song/redis-manager


text:
Invalid type String

Hi, Nice template and I finally got it going, but I have an value type mismatch as per the image attached, "The value type "string" is not suitable for value type "Numeric (unassigned)". Value -1" Can you please tell me if I just need to add the value_type = TEXT in the template for the bad sectors count? Or have it the wrong way around?

I have resolved the error in my instance as per my assumption in my initial issue notes; I have added 'value_type = TEXT' in the bad sectors count config settings and the 'not suitable' error has been resolved and I can see the graph/trend now.

repo: zabbix/community-templates


text:
Dynamic view title overlaps Back button

When using Ionic Material, if there is a view with a dynamic value used for <ion-nav-title> which also displays a Back button without a text label, then the first time that view is accessed the title will overlay the Back button icon.
Sample view code:
index.html

<body ng-app="myMobileApp">
    <ion-nav-bar class="bar-stable">
        <ion-nav-back-button></ion-nav-back-button>
    </ion-nav-bar>
    <ion-nav-view></ion-nav-view>
</body>

second-level-view.html

<ion-view>
    <ion-nav-title>{{myViewTitle}}</ion-nav-title>
    <ion-content class="padding">

Screenshot:

I found this Ionic issue where a similar bug had been reported and was resolved for some with ngBind or afterEnter event manipulation.
https://github.com/driftyco/ionic/issues/2881
In our app I tried the afterEvent which worked but there was a delay.  Additionally, you could see it shift a bit on every load of that view, so that seemed like a step backwards.
The simple ngBind did not seem to help, but the explanation of how it helped some in the Ionic issue comments made me think it was a good idea.  So even though its pretty much just for good measure, I modified our title...
...from this:

    <ion-nav-title>{{category.name}}</ion-nav-title>

...to this:

    <ion-nav-title ng-bind="category.name"></ion-nav-title>

I have traced the title/back overlap issue down to an Ionic Material issue on iOS only.  (I don't think they work real hard to be iOS compatible; at least not yet)
Changing their bar.scss to only left-align the title for android (Ionic default title alignment in iOS is 'center', per Apple HIG) like this resolves the issue:
.bar.bar-header .button + .title {
    .platform-android & {
        text-align: left;
        left: 35px;
    }
    line-height: $base-bar-height;
}

Trying to come up with a solution that does not involve overwriting IM's scss, I modified our .bar related styles in ionic.app.scss to this:
.bar {
  .platform-ios & {
    .bar.bar-header .button + .title {
      // Left alignment has issue with title overlaying Back button
      text-align: center !important;
    }
  }
  ...
}

This is working in browser, lab iOS, and iOS simulator.
So it would be nice if Ionic Material would include this parent selector to leave iOS titles left aligned.
(Personally, I don't think fixing it as centered is an option, since some apps use labels with the Back button, so a left aligned title that close to a Back button can be confusing what you are going 'back' to.)

repo: zachsoft/Ionic-Material


text:
The format of the dataset

Hello, Zekai.
Thanks for  your brilliant work.
I have some problem when reproducing the work when using SMAP/MSL dataset, can you share the original data when training the network. Thanks a lot!

Hello, Zekai. Thanks for your brilliant work.
I have some problem when reproducing the work when using SMAP/MSL dataset, can you share the original data when training the network. Thanks a lot!

Hello have you reproducted this work

authors: Kiwamm ZhouHnag

repo: zackchen-lb/GTA


text:
bclm no longer works after latest 14.7 update

Hi there,
I just updated my Sonoma with the latest 14.7 update and bclm no longer works.
$ sw_vers
ProductName:		macOS
ProductVersion:		14.7
BuildVersion:		23H124

$ sudo bclm read
keyNotFound(code: "CHWA")

I have been using this for a while, this is the first time getting this error. Anything I can help/assist to get this sorted just let me know, love this util!
Thanks,
Ivan

Sorry, duplicate #49

repo: zackelia/bclm


text:
diy去污粉

操作系统 (Windows/macOS/Linux): win10
浏览器版本(您可以在 [菜单/帮助/关于] 下查看):chrome68.0.3440.106
扩展版本:1.1.7

请问直播间版聊右下角的去污粉还会添加么，我卸载重装了扩展也没看到。想单独设置某个直播间的

以前的去污粉已经改的成了编辑框上面的禁止图标，如果没有看到，请尝试卸载助手再重新安装。

哦哦  谢谢提醒  看到啦~

repo: zacyu/bilibili-helper


text:
解析存档报错，控制台返回空数组

Level.zip

补充 删除pst.db再运行结果相同

看起来像是多个问题？
运行 .\pst.exe 都 panic了，怎么在浏览器的f12请求中还会有正常请求存在？

我更新了sav_cli正常，稍后我会重新发版，请留意issue关闭情况

该问题集中讨论至 #29

https://share.zaigie.com/s/E3OTE3O
下载这个当时打包给调试的release（不用在意版本号），然后看一下日志输出中的GetDB: xxx

2024/02/01 - 16:51:06 | DEBUG | database/bbolt.go:40 | GetDB: 0xbb0a580

https://share.zaigie.com/s/E3OTE3O 下载这个当时打包给调试的release（不用在意版本号），然后看一下日志输出中的GetDB: xxx

authors: StrawDC zaigie

repo: zaigie/palworld-server-tool


text:
Update Readme.

Readme can be updated with details of mentors,admins,slack channels and details of gssoc. Please assign me this issue.

@Sapna2001 sure. You can go ahead with this.

Can you add gssoc and difficulty label for this issue.

repo: zairza-cetb/bench-routes


text:
Issue 34 fix content type detection

Recognize application/problem+json content type correctly.
Don't try to deserialize application/json into a problem, because it isn't necessarily one.
Write custom deserializer for IOProblem because the default one fails

@jhorstmann

:+1:

:+1:

authors: jhorstmann tmuehl

repo: zalando-incubator/fahrschein


text:
Question: What is the best approach to monitor children objects within their parent?

Hi all,
I'm currently working on porting some code from metacontroller into Kopf.
Metacontroller, gives you the option to receive callbacks when the monitored object changes, or any of its children is updated.
For example, if I'm watching an object of kind multijob, which creates an arbitrary number of standard kubernetes jobs, I would receive a callback if the children fail, restart, succeed, etc, which I can use to update the status field in the parent.
I haven't been able to find a clean way to do the same thing in Kopf, other than adding separate listeners for both the parent/children, and within the children listeners update the parent CRD. Of course the example here is simplified, the actual application would have many dependencies and larger hierarchies of objects, and having this kind of inter-dependencies between listeners make them harder to maintain.
Is there any better way to do this? Or is there any feature in Kopf that would make the management of children easier/cleaner?
Thanks!

Related: #58 #264
See also: https://github.com/zalando-incubator/kopf/issues/264#issuecomment-562845724
You are right, the only way is —as you said— "adding separate listeners for both the parent/children, and within the children listeners update the parent CRD".
Keep in mind, that Kopf keeps one and only one watch-query (an API request) per resource kind no matter how many handlers are there for that resource kind. So, there should be no problems with APIs.
There is no simpler (i.e. few-liner) solution at the moment.
A better solution is planned though — but rather later than sooner (because: priorities; and my regular employment takes time).
Under the hood, it will be working exactly the same way, just with better DSL for handlers. Some ideation was happening in this gist.

For all those looking for a solution/pattern and coming to this issue — here is an example, which we currently use for ourselves:

Label the children resources with name & namespace of the parent object (assuming they can be in different namespaces; if it is the same namespace by design, only the name is needed).

Watch for children resources that have this label (any value). In the watcher, get the name of the parent resource and patch its status field (e.g. status.subpods) with the status of the watched children resource (selected or agregated).

Back in the parent resource, react to changes in that status field, and do the calculation on all the children overall statuses.

A sample skeleton code:
# pip install kopf pykube-ng PyYAML
import kopf
import pykube
import yaml

class KopfExample(pykube.objects.NamespacedAPIObject):
    version = "zalando.org/v1"
    endpoint = "kopfexamples"
    kind = "KopfExample"

@kopf.on.create('zalando.org', 'v1', 'kopfexamples')
def spawn_children(name, **_):
    data = yaml.safe_load(f"""
        apiVersion: v1
        kind: Pod
        spec:
          containers:
          - name: the-only-one
            image: busybox
            command: ["sh", "-x", "-c", "sleep 1"]
    """)

    kopf.adopt(data)
    kopf.label(data, labels={'kex-parent-name': name})  # << HERE!

    api = pykube.HTTPClient(pykube.KubeConfig.from_env())
    for _ in range(5):
        pykube.Pod(api, data).create()

@kopf.on.event('', 'v1', 'pods', labels={'kex-parent-name': None})
def kexed_pod_monitoring(meta, name, namespace, status, **_):
    parent_name = meta['labels']['kex-parent-name']

    try:
        api = pykube.HTTPClient(pykube.KubeConfig.from_env())
        parent_kex = KopfExample.objects(api, namespace=namespace).get_by_name(parent_name)
        parent_kex.patch({'status': {'subpods': {name: status['phase']}}})  # << HERE
    except pykube.exceptions.ObjectDoesNotExist:
        pass

@kopf.on.field('zalando.org', 'v1', 'kopfexamples', field='status.subpods')
def kex_subpods_reaction(old, new, diff, **_):
    pass  # << HERE, decide something on ALL of them at once.
    msg = " // ".join([f"{pod_name} is {pod_phase}"
                       for pod_name, pod_phase in new.items()])
    print(f"==> {msg}")

Thank you @nolar for the detailed update. My current approach looks very similar to the example you provided. Will follow up closely on future releases.

This is a related q:
I want to react to new namespaces..
after playing with asyncio and threading I was able to react to new ns but then stopping the thread or the loop was not clean. also on kopf.on.cleanup I found tricky...
So then I found this thread so now i am using kopf.on.event wich is a cleaner way..
I try to label the existing ns and then whatching for non labeled ns...
@kopf.on.event('', 'v1', 'namespaces',labels={'existing': None})

I am wondering if i could improve this approach. so filtering by type of event.
like event = new. but there is no such thing. so maybe compare the creationTimestamp if its close to actual date?
so far iam using a idempotent function that can run in every namespace multiple times, existing or new..

authors: nolar xocoatzin zakkg3

repo: zalando-incubator/kopf


text:
Improve logging

fixes #9

👍

👍

[Current coverage][cc-pull] is 100%

Merging [#10][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master       #10   diff @@
=======================================
  Files           3         6     +3
  Lines          15        60    +45
  Methods         0         0
  Messages        0         0
  Branches        0         1     +1
=======================================
+ Hits           15        60    +45
  Misses          0         0
  Partials        0         0

Powered by Codecov. Last updated by [5dd8a51...3ad32a4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/zalando-stups/log-sink/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/zalando-stups/log-sink/compare/5dd8a518a7879270fd060db229b9437d8c42cbed...3ad32a41453953e412d675a7081c04991c9a4e92
[cc-pull]: https://codecov.io/gh/zalando-stups/log-sink/pull/10?src=pr

👍

👍

authors: ChristianLohmann codecov-io harti2006 mrandi

repo: zalando-stups/log-sink


text:
[✨ feature] Creating a service

Is your feature request related to a problem? Please describe.
Services are the core of the app, users use them to deploy their app, create databases or any long lived application.
Describe the solution you'd like
First, when the user click on a newly created project, there should be a page asking the user multiple options for the things they want to deploy :

a service
a background worker
Cron Jobs
Postgres
REDIS
deploy from a docker-compose file

In this we will focus on services, and work on the other features later.
If the user clicks on creating a service, they should be prompted to either create them from a git repository or from a docker registry.
See the linked sub-issues for how each workflow will be handled :

[ ] #4
[x] #6

Additional context

[ ] Are you willing to make a PR for this ?

done

repo: zane-ops/zane-ops


text:
0.0.54: TypeScript completion got frozen

Thank you for the amazing extension!
After updating to 0.0.54, TypeScript completion got frozen and occupies high cpu.
Repo: (I test this in a empty vscode(1.77.0 & 1.77.1) profile)

create a main.ts file
write this

const a = {
   // <- 3. then ctrl+space here, and it got stuck
}

If I install the 0.0.53 version, everything goes well
I have tried early versions of JavaScript and TypeScript Nightly but nothing changed

Thank you so much for reporting this! I was extremely surprised that infinite-loop aware code was incorrectly fixed by eslint rule which started causing infinite loop, my bad I should've noticed this change. On the other hand I didn't notice it personally after plugin update because I'm using "tsEssentialPlugins.objectLiteralCompletions.keepOriginal": "remove" along with this keybinding:
{
    "key": "shift+enter",
    "when": "suggestWidgetVisible && editorLangId != vue",
    "command": "tsEssentialPlugins.insertNameOfCompletion"
}

so I don't have 2x more variants in completion widget. I also recommend it, super useful.

It works, thank you for your effort!

authors: fifv zardoy

repo: zardoy/typescript-vscode-plugins


text:
systemd unit file

Hi, not sure if it applies for you (if you have systemd on your retropie), but instead of me using autostart.sh to start the webserver, I'm using this systemd unit file. Thought sharing.

Thanks.  This is great.  Maybe I'll update the setup.sh to use this instead of the autostart.sh

authors: sooslaca zaront

repo: zaront/RetroPie-Parental


text:
Add Readme

Adds a Readme with minimal information about the spec, it's current state, and how to work with it.

cc @joshmoore @MSanKeys963 @alimanfoo

Generaly, :100:. I'd get this in ASAP and we can iterate on it as we go.

@joshmoore @MSanKeys963 Is there anything missing to merge this?

Apologies for missing this, @jstriebel.
I think we're good to go here, @joshmoore. Let's merge this.

authors: MSanKeys963 joshmoore jstriebel

repo: zarr-developers/zarr-specs


text:
vendor: update jedi to 2ba78ab

updtae jedi to https://github.com/davidhalter/jedi/commit/2ba78ab725f1e02dfef8bc50b0204cf656e8ee23

/cc @tweekmonster @blueyed

Heh, we did the same for jedi-vim today also: https://github.com/davidhalter/jedi-vim/pull/635

@blueyed I did PR because I saw it lol

Now fixed CI fail on another branch...

@tweekmonster @blueyed Passes CI test.
I'll merge.

authors: blueyed zchee

repo: zchee/deoplete-jedi


text:
Masternode Instability After 2-4 Weeks of Running

Masternode only stays running for about 2-4 weeks at a time and then becomes unstable. Each time it starts throwing this and then eventually debug logs just stop:
2018-03-15 00:18:56 AcceptToMemoryPoolWorker(),fCheckInputs=true, tx.IsZerocoinSpend()=false, fTestNet=false
2018-03-15 00:18:56 CheckTransaction nHeight=2147483647, isVerifyDB=false, isCheckWallet=true, txHash=99bf26983083790d23eca19c065ff03183a1361525b4907b690b8f87bd0c032c
2018-03-15 00:18:56 txin=CTxIn(COutPoint(ce4b081b02180d799a50c4eeb378c8641d29c0bd682767171fb05e026a5cb02f, 0), scriptSig=4730440220068a6104bd57c1, nSequence=4294967294)
2018-03-15 00:18:56 IsFinalTx tx=99bf26983083790d23eca19c065ff03183a1361525b4907b690b8f87bd0c032c --> FAILED
2018-03-15 00:18:56 AcceptToMemoryPoolWorker --> FAILED
2018-03-15 00:19:13 CZnodeMan::CheckAndRemove
2018-03-15 00:19:13 CZnodeMan::CheckAndRemove -- Znodes: 2683, peers who asked us for Znode list: 0, peers we asked for Znode list: 0, entries in Znode list we asked for: 86, znode index size: 2753, nDsqCount: 0
2018-03-15 00:19:13 CZnodePayments::CheckAndRemove -- Votes: 55695, Blocks: 5013
2018-03-15 00:19:23 AcceptToMemoryPool(), fCheckInputs=true
2018-03-15 00:19:23 AcceptToMemoryPoolWorker(),fCheckInputs=true, tx.IsZerocoinSpend()=false, fTestNet=false
2018-03-15 00:19:23 CheckTransaction nHeight=2147483647, isVerifyDB=false, isCheckWallet=true, txHash=02e8992db1701d006b9f8159ed00c275ee341d188239a2e18e7d66d69a182cdd
2018-03-15 00:19:23 txin=CTxIn(COutPoint(8394d68a59079a11dfba19ec9677ac0b00f2e0b4e2057e149bd65e5bcf347177, 0), scriptSig=483045022100d3a453c50ffd, nSequence=4294967294)
2018-03-15 00:19:23 IsFinalTx tx=02e8992db1701d006b9f8159ed00c275ee341d188239a2e18e7d66d69a182cdd --> FAILED
2018-03-15 00:19:23 AcceptToMemoryPoolWorker --> FAILED
2018-03-15 00:20:14 CZnodeMan::CheckAndRemove
2018-03-15 00:20:14 CZnodeMan::CheckAndRemove -- Znodes: 2683, peers who asked us for Znode list: 0, peers we asked for Znode list: 0, entries in Znode list we asked for: 86, znode index size: 2753, nDsqCount: 0
2018-03-15 00:20:14 CZnodePayments::CheckAndRemove -- Votes: 55695, Blocks: 5013
2018-03-15 00:21:14 CZnodeMan::CheckAndRemove
2018-03-15 00:21:14 CZnodeMan::CheckAndRemove -- Znodes: 2683, peers who asked us for Znode list: 0, peers we asked for Znode list: 0, entries in Znode list we asked for: 86, znode index size: 2753, nDsqCount: 0
2018-03-15 00:21:14 CZnodePayments::CheckAndRemove -- Votes: 55695, Blocks: 5013
2018-03-15 00:21:42 AdvertiseLocal: advertising address 45.32.166.53:8168
2018-03-15 00:22:09 connect() to [2600:8800:2c86:4e00:18e9:569d:243e:8a25]:8168 failed: Network is unreachable (101)
2018-03-15 00:22:09 AcceptToMemoryPool(), fCheckInputs=true
2018-03-15 00:22:09 AcceptToMemoryPoolWorker(),fCheckInputs=true, tx.IsZerocoinSpend()=false, fTestNet=false
2018-03-15 00:22:09 CheckTransaction nHeight=2147483647, isVerifyDB=false, isCheckWallet=true, txHash=b2f5e33392a94d7cbe2209dd9ce87ab5eec3cb6fa818fa632c6fecda2a2031ab
2018-03-15 00:22:09 txin=CTxIn(COutPoint(ee375d7829c44b74d672e2344ae4f91657cd532bbe792b6dc2427a19cbc9c442, 1), scriptSig=483045022100c2e3195dbf19, nSequence=4294967294)
2018-03-15 00:22:09 IsFinalTx tx=b2f5e33392a94d7cbe2209dd9ce87ab5eec3cb6fa818fa632c6fecda2a2031ab --> FAILED
2018-03-15 00:22:09 AcceptToMemoryPoolWorker --> FAILED
This wouldn't be a huge issue if it were a regular node, but every time this happens it take another week or so to get the masternode re-activated which results in a substantial payout loss.
Is anything else seeing this and is there a solution?
Let me know if you need any additional information.

i got the same actually which throw me out auf the queue twice already, so i  already lost two payments. Super annoying.

Im just curious - if this happens, what does wallet or "cli znode status" say? Is there anything that indicates that the znode went out, or is it just logs?

Hi @oti-dev ,
The status seems to be alright:
{   "vin": "CTxIn(COutPoint(xxxxx, 1), scriptSig=)",   "service": "x.x.x.x:8168",   "payee": "xxxxx",   "status": "Znode successfully started" }
Although, if i check through znodestatus.privex.io it says not qualified for payout. This happened already two times within the past weeks and i always needed to restart / resync the node to get it working again, which unfortunately causes a loss of its position in the queue.

It's interesting.. I'd like to know how privex judges if a node is qualified or not then.

@oti-dev so would i, more interesting is that the wallet also said new restart required but the node was still in "znode successfully started" mode!

@outragedhuman are you still facing the same issue?

There also are 'last seen' timestamp and 'active' time (IIRC any znode can be queried for a full list of all znodes and these informations) - perhaps your znode becomes invisible to the network, and other znodes stop talking to it. I guess that might be the way privex (and other such sites) decide whether the znode is qualified or not.
Personally I'd recommend live polling the state of the znodes you're maintaining - watch the active time,  number of blocks, last seen timestamp, rank and the status. I've been doing this with several znodes for 2 months now and it's been accurate so far. The more data you collect the more up to date you are.

@oti-dev thanks for the detailed input - highly appreciated! This data you are pulling through the RPC API over HTTP, right?
Also it is a good idea to keep an eye on the debug.log file

Actually I'm using ssh to invoke cli locally on the znode server - it's generally not advisable to accept RPC calls from external IP's (e.g. other than localhost).
You're right - I don't watch the debug.log right now, but perhaps I should. I just didn't implement that because I found it difficult to filter out the messages not related to znode 'health'. I guess I'd look there once something goes wrong (hasn't yet).

@oti-dev I see, make sense. Any idea how websites such like masternodes.online are receiving the status then? Or do they run their own node per coin so they are able to check?
Thank You!

@oti-dev actually processing the debug.log file and filtering it makes sense.. you can just listen on certain log levels such like failure

Yeah I guess they actually run a regular nodes of each cryptocurrency and thus are able to query list of all masternodes and their state - I don't see any other viable way of doing this.

@soerenmartius Yes, these sites do run their own nodes. Privex certainly does. You can check what exactly they are doing in their GitHub repo: https://github.com/Privex/znode-status
@outragedhuman  Does this problem persist? It seems to me it could have been related to the block stuck issues we've been seeing in versions <0.13.5.8

Can this be closed now . .  @outragedhuman ?

Closing first. If still an issue, please reopen.

authors: catchingknives devwarrior777 oti-dev outragedhuman reubenyap soerenmartius

repo: zcoinofficial/zcoin


text:
求有关Svar的介绍

有没有关于Svar模块的代码基本介绍？这部分代码看的有点迷糊。
另外，你们PIL repo中的README.md链接打不开，不清楚是不是网速的问题。
感觉GSLAM是不错的框架！

Svar模块有较大重构，具体可以参考https://zdzhaoyong.github.io/GSLAM/svar.html

authors: qlibp zdzhaoyong

repo: zdzhaoyong/GSLAM


text:
Pug template syntax highlighting in component files

Enables the Pug syntax highlighting extension to be used when a <template lang="pug"> tag is present in a component

@cla-bot check

Thank you. Can this please be merged?

authors: repoman zareith

repo: zed-extensions/vue


text:
Navigating with command + key behaves differently with backspace than arrow keys

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
When a line is wrapped in the editor to be shown across multiple lines navigating with command pressed behaves differently depending if arrow keys are used or backspace.
When pressing command + left arrow the cursor moves to the left most position in the wrapped line as expected. With command + shift + left arrow it highlights the wrapped line as it's displayed on the screen.
However using command + backspace ignores the wrapping and deletes the entire line up to the line break in the file. This is pretty unintuitive and seems like a bug.
Environment
Zed: v0.115.3 (stable)
OS: macOS 14.1.2
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
The issue was tested with a markdown file where the file level lines are wrapped and shown on multiple lines. One example could be the below line
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed accumsan non quam ut
vestibulum. Nunc eget eleifend mauris, eget ultrices risus**<cursor here>**

If pressing command + left arrow the cursor will be right before the v in vestibulum, but if pressing command + backspace the entire line is deleted.
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

Hey @magnuspaaske - totally get the inconsistency here, but I just wanted to ask, if you were to fix this, would you change the behavior of cmd-delete to match the behavior or say cmd-shift-left, or vice versa?

@JosephTLyons I would change the behaviour of cmd-delete to match that of cmd-shift-left. Might want to hide it behind a setting (or not depending how customizable things should be). FWIW I also checked it on Sublime Text and found the same behaviour

authors: JosephTLyons magnuspaaske

repo: zed-industries/community


text:
Editor context menu and autocomplete menu run into each other

Check for existing issues

[X] Completed

Describe the regression
See screenshot
If necessary, add screenshots of gpui-1 Zed to show the missing feature

Will be fixed in the next preview.

authors: ConradIrwin JosephTLyons


text:
Generate sourcemap fail

Generate sourcemap fail.
custom server with express + antd + some other config
system info
next: latest
@zeit/next-source-maps: 0.0.4-canary.1

next.config.js
const withLess = require('@zeit/next-less');
const withSourceMaps = require('@zeit/next-source-maps')();

module.exports = withSourceMaps(
  withLess({
    webpack: (config, { buildId, dev, isServer, defaultLoaders }) => {
      // other config
      return config;
    },
  })
);

Error log
Creating an optimized production build

Compiled with warnings.

static/chunks/commons.6ab125648482b52a8af3.js contains invalid source map

static/runtime/webpack-c43d17b948281806ed42.js contains invalid source map

static/chunks/framework.e7fdea748275aa1a2bc5.js contains invalid source map

static/chunks/45c6a5874837745bb5e7fcded70befe95b28e5cd.a2dd79735c4ef014b596.js contains invalid source map

static/chunks/45c6a5874837745bb5e7fcded70befe95b28e5cd_CSS.69a1ebd8bf7fa2d6ea07.js contains invalid source map

static/chunks/0f1305cd4e29670bb75d88458d18b42d1381c5e9.d8c0fe84159e6a0c6212.js contains invalid source map

static/chunks/75651d2a3daa4d74c577a24502e599553bb778c6.be0451e518fa8f613e62.js contains invalid source map

static/chunks/6bdfb38fe2cb00a48b70aaf030014c4859f0c10e.c03937f16c696208814c.js contains invalid source map

static/chunks/8023f925dc72fe66737f19d1f460707f1fb6964a.5b4a611251d8a1e4eeb2.js contains invalid source map

static/chunks/e17d87a1fd151f9e027d3bb5bbbbcf66ebd6b3ad.225dd2608e10fa83d401.js contains invalid source map

static/chunks/styles.a12887ee6fde1f368ab5.js contains invalid source map

static/chunks/003a0467.b78ff15d1ae0b331a775.js contains invalid source map

static/azNHtIqPdp2T4VgARphCW/pages/_app.js contains invalid source map

static/azNHtIqPdp2T4VgARphCW/pages/_error.js contains invalid source map

static/azNHtIqPdp2T4VgARphCW/pages/index.js contains invalid source map

static/azNHtIqPdp2T4VgARphCW/pages/user/[username].js contains invalid source map

static/azNHtIqPdp2T4VgARphCW/pages/user/list.js contains invalid source map

static/runtime/main-5dead1facdcb0fbc368d.js contains invalid source map

static/runtime/polyfills-41581f0db4e738e3934c.js contains invalid source map

Additional context
It is only in this demo(scaffold) that the sourcemap files cannot be generated. I think it's not the plugins  or next.js bug, but i have no idea to solve it, can u help me solve it? Thanks~
Repo url
The demo url: https://github.com/luffyZh/next-antd-scaffold/tree/source-map

@timneutkens Thank you  your reply~
I have found that the problem is with the extra TerserPlugin.
 config.plugins.push(
          new TerserPlugin({
            cache: true,
            sourceMap: true,   // +++++ add this line, solve the problem
            terserOptions: {
              ecma: 6,
              warnings: false,
              extractComments: false, // remove comment
              compress: {
                 drop_console: true // remove console
              },
              ie8: false,
            }
          }),
        )

Anyway, thanks a lot for your reply and I'll close the issue

repo: zeit/next-plugins


text:
fix(dev-server): render 404 when ssg dynamic route doesn't exist

This PR addresses the following issue: In dev mode you will be served the _error page instead of a custom 404-page if you hit a path that doesn't exist for a statically generated dynamic route. In addition, the 404-page mustn't been rendered before.
As far as I understand, in dev-mode pages are rendered "on demand", i.e. the 404-page won't be built until it is needed. The dev-server has to make sure that the page is built before attempting to render it by extending the render-methods of the NextServer and calling the ensurePage method from the hot-reloader used in dev. Then is passes on to the render-method of the NextServer.
The problem is that only the _error page was "ensured" in renderErrorToHTML, regardless of the status code and if there is a custom 404 page. I added a condition that checks if the status code is a 404 and if there is a custom 404 page. If so, we now "ensure" the 404-page, otherwise we continue using the _error page.
I also added a test suite to assert that the 404 page is indeed served in the scenario I described in the beginning. (The test for the dev-mode would fail without the changes in the dev-server.)
First time for me to work with this codebase, so I'm super excited to hear your feedback 😅  Hope the changes are fine! Also, if there's a better approach of if I missed anything I'm happy to learn 🙂

PS: I didn't open an issue here and went straight to finding the solution 😄 just let me know if I should also create a related issue 🙂

Stats from current PR

Default Server Mode (Decrease detected ✓)

General Overall increase ⚠

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

buildDuration
13.2s
12.8s
-431ms

nodeModulesSize
55.6 MB
55.6 MB
⚠ +104 B

Page Load Tests Overall decrease ⚠

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

/ failed reqs
0
0
✓

/ total time (seconds)
2.171
2.266
⚠ +0.1

/ avg req/sec
1151.37
1103.21
-48.16

/error-in-render failed reqs
0
0
✓

/error-in-render total time (seconds)
1.228
1.34
⚠ +0.11

/error-in-render avg req/sec
2035.27
1865.8
-169.47

Client Bundles (main, webpack, commons)

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

main-HASH.js gzip
6.25 kB
6.25 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..5e5e.js gzip
10.3 kB
10.3 kB
✓

framework.a1..NSE.txt gzip
220 B
220 B
✓

framework.a1..NSE.txt gzip
220 B
220 B
✓

framework.HASH.js gzip
39 kB
39 kB
✓

Overall change
56.7 kB
56.7 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

main-HASH.module.js gzip
4.79 kB
4.79 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.85 kB
6.85 kB
✓

framework.HA..dule.js gzip
39 kB
39 kB
✓

Overall change
51.4 kB
51.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

polyfills-HASH.js gzip
26.2 kB
26.2 kB
✓

Overall change
26.2 kB
26.2 kB
✓

Client Pages

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_app.js gzip
1.23 kB
1.23 kB
✓

_error.js gzip
3.12 kB
3.12 kB
✓

hooks.js gzip
663 B
663 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.06 kB
2.06 kB
✓

routerDirect.js gzip
280 B
280 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
7.85 kB
7.85 kB
✓

Client Pages Modern

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_app.module.js gzip
598 B
598 B
✓

_error.module.js gzip
2.09 kB
2.09 kB
✓

hooks.module.js gzip
383 B
383 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js gzip
1.52 kB
1.52 kB
✓

routerDirect..dule.js gzip
279 B
279 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
5.37 kB
5.37 kB
✓

Client Build Manifests

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Rendered Page Sizes

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

index.html gzip
929 B
929 B
✓

link.html gzip
937 B
937 B
✓

withRouter.html gzip
926 B
926 B
✓

Overall change
2.79 kB
2.79 kB
✓

Serverless Mode

General Overall increase ⚠

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

buildDuration
13.5s
13.6s
⚠ +55ms

nodeModulesSize
55.6 MB
55.6 MB
⚠ +104 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

main-HASH.js gzip
6.25 kB
6.25 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

de003c3a9d30..5e5e.js gzip
10.3 kB
10.3 kB
✓

framework.a1..NSE.txt gzip
220 B
220 B
✓

framework.a1..NSE.txt gzip
220 B
220 B
✓

framework.HASH.js gzip
39 kB
39 kB
✓

Overall change
56.7 kB
56.7 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

main-HASH.module.js gzip
4.79 kB
4.79 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..dule.js gzip
6.85 kB
6.85 kB
✓

framework.HA..dule.js gzip
39 kB
39 kB
✓

Overall change
51.4 kB
51.4 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

polyfills-HASH.js gzip
26.2 kB
26.2 kB
✓

Overall change
26.2 kB
26.2 kB
✓

Client Pages

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_app.js gzip
1.23 kB
1.23 kB
✓

_error.js gzip
3.12 kB
3.12 kB
✓

hooks.js gzip
663 B
663 B
✓

index.js gzip
222 B
222 B
✓

link.js gzip
2.06 kB
2.06 kB
✓

routerDirect.js gzip
280 B
280 B
✓

withRouter.js gzip
278 B
278 B
✓

Overall change
7.85 kB
7.85 kB
✓

Client Pages Modern

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_app.module.js gzip
598 B
598 B
✓

_error.module.js gzip
2.09 kB
2.09 kB
✓

hooks.module.js gzip
383 B
383 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js gzip
1.52 kB
1.52 kB
✓

routerDirect..dule.js gzip
279 B
279 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
5.37 kB
5.37 kB
✓

Client Build Manifests

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_buildManifest.js gzip
61 B
61 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
122 B
122 B
✓

Serverless bundles

zeit/next.js canary
thomasheyenbrock/next.js fix/error-instead-of-404-in-dev
Change

_error.js
558 kB
558 kB
✓

404.html
4.18 kB
4.18 kB
✓

hooks.html
3.81 kB
3.81 kB
✓

index.js
558 kB
558 kB
✓

link.js
595 kB
595 kB
✓

routerDirect.js
587 kB
587 kB
✓

withRouter.js
587 kB
587 kB
✓

Overall change
2.89 MB
2.89 MB
✓

authors: ijjk thomasheyenbrock


text:
Keep some buffered pages, that won't be disposed. Fix #1939

Implementation of @arunoda's suggestion of letting the user decide how many page should be kept in memory before disposing them.
@sedubois made his point for not over disposing built pages, so I won't repeat him, but I think he has a point:

This would allow to then have fast client-side transitions (after the first load), which allows to have a feel of these transitions without needing to deploy to prod.

The implementation is pretty naive, pagesBuffer works as a queue (first in, first out) of max length two (or whatever the user set), we keep in the buffer the last requested pages. If you'd like me to encapsulate the pagesBuffer logic in, do not hesitate, I didn't want to add any non needed abstraction :)

I really like the concept behind this PR. But I suggest to change it like this.
Check this: https://github.com/zeit/next.js/blob/v3-beta/server/on-demand-entry-handler.js#L20
It keeps tracks of pages we've accessed. Currently it only keep a single entry. Initialize that with the pageBufferLength  count.
Then do a include check here: https://github.com/zeit/next.js/blob/v3-beta/server/on-demand-entry-handler.js#L237

I managed to get a working version of it, but I have a problem with the tests! The way the lastAccessPages is handled is through the middleware and the on-demand-entries-ping, which is not used in the test. Should I try to add the corresponding pings in the test suite?

@arunoda I went around the issues I had with the tests, and manage to make it work following your suggestion (or at least, I believed it's closer from what you envisioned).

Hey @arunoda, is this feature still something you're interested in? Would you like me to change anything? I know that with the 3.0 release, you had a pretty busy time :)

Thanks a lot :)

It's released under @beta 👍

Sweet, any notes or additions to the readme on how to change pagesBufferLength from the default?

@marbemac My bad, here is the PR!

authors: AugustinLF arunoda marbemac timneutkens


text:
Remove trailing spaces

changes
remove trailing spaces
When I was using example I noticed trailing spaces.
So, this PR removes the trailing spaces of json file, README, and others.
examples/with-jest-typescript/src/modules/cars/Overview.tsx also has it, but this time it did not change as tslint error occurs at commit.

@Timer
I was forgotten to a line break, thanks🙌
So, I am wondering which of spaces and
 is common🤔

 is redundant, but I prefer it to spaces.

Spaces will accidentally be removed like you did here.
 is more explicit. 😄

authors: Timer thinceller


text:
Getting an error when trying to provision a certificate

either via:
now certs create shipatron.io

or
now alias

I get back:

Error! Unexpected error. Please try again later. (invalid json response body at https://api.zeit.co/now/certs reason: Unexpected token N in JSON at position 0)

I'm using Cloudflare and have followed all the steps outlined here. Appreciate any help.

We're deploying a fix for this right now.

@Qix great, thanks!

Now getting the same message as previously:

Error! Unknown error: Error: Invalid challenge response for {domain}. Make sure the DNS records are correct.
Error: Invalid challenge response for {domain}. Make sure the DNS records are correct.
at module.exports.EventEmitter.createCert.domain.retry (/snapshot/now-cli/dist/now.js:916:15)
at process._tickCallback (internal/process/next_tick.js:109:7)

@Stumblor How new is the domain?

@Qix Over 2 weeks, but made the switch to CloudFlare yesterday lunchtime.

Did that fix the issue then?

@Qix- Sorry, no, still getting the same error ('Invalid challenge response for {domain}. Make sure the DNS records are correct.'). Could this be a problem with how I've setup the DNS?

@OlliV Sorry to harrass but any word on this?

I have the same problem and since 12 hours my domain is now inaccessible: https://nuxtjs.org/

Workaround for now is to set the DNS records to DNS-only mode, renew the certs manually with now certs renew <domain>, and re-enable the cache mode in Cloudflare. I'm not yet sure about the root cause because renewing works with my test domains.
One thing to keep in mind is also the new requirement for CAA records even though this doesn't seem to be affecting you right now:
https://community.letsencrypt.org/t/legacy-caa-implementation/42335

@OlliV Where do you set DNS only mode? Tried in fiddling with both the security settings and caching but no luck so far.

and did you also set this?

@OlliV Brilliant thanks dude that DNS only setting fixed it. Thanks for your help!

authors: Atinux OlliV Qix- Stumblor

repo: zeit/now-cli


text:
Error! Cannot read file, ENOENT worker_threads

After updating pkg from version 4.4.0 to 4.4.1 I got the following message:

Downgrading back to 4.4.0 fixes this. I'm running MacOS 10.13.6, NodeJS v8.12.0.
Am I missing something? This is happening in multiple projects that used to work fine.

Does it work this way even if the project is simply console.log(42)? Can you please also narrow down to a smallest code snippet?

@igorklopov That produces the same error:

Just to show the output of version 4.4.0:

Package write-file-atomic causes this problem.

write-file-atomic-npm

authors: Nihiue glenndehaan igorklopov

repo: zeit/pkg


text:
when run pytorch modelnet

subprocess.CalledProcessError: Command '['/anaconda3/envs/pointnet2/bin/python', '-u', 'function/train_modelnet_dist.py', '--local_rank=1', '--cfg', 'cfgs/modelnet/pospool_sin_cos_avg.yaml']' returned non-zero exit status 1.

*****************************************
Traceback (most recent call last):
  File "/CloserLook3D/pytorch/ops/pt_custom_ops/pt_utils.py", line 7, in <module>
    import pt_custom_ops._ext as _ext
ImportError: /home/amax/.local/lib/python3.6/site-packages/pt_custom_ops-0.0.0-py3.6-linux-x86_64.egg/pt_custom_ops/_ext.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZN6caffe26detail37_typeMetaDataInstance_preallocated_32E

During handling of the above exception, another exception occurred:

solved by create new env


text:
Remove stringify option

Resolves #376

Coverage remained the same at 100.0% when pulling 205487d4a756e9141cbce22787d455eb9bb31621 on juanjoDiaz:remove_stringify_option into e0baab8c7f404f47ce94ffb57064a94d9efe3539 on zemirco:master.

authors: coveralls juanjoDiaz


text:
Whatsapp tab changes from whatsapp to url + notifications on unread messages not seen

This occurs randomly. Notification on un read messages may not appear or show wrong data. Refresh solves the issue for a while.

Hello,
We have divided error #47 (#33 in the task list) into two tasks:
33.1 Incorrect header text format. (5 hours).
33.2 Incorrect data in the counter (incorrect count of unread messages).
33.2.1 Item cannot be completed before item 28 in the task list, because it involves a high-level api.

The point is that previously we also needed access to the high-level api.
1.1 By high-level api we mean access to the site's memory.
Your extension has written code that we can work with freely. But functions which directly affect WA code are not available to us, because we don't have access to the high-level WA API. For example, task 47.2 (number 33 on the task list) is a task which is directly related to WA code and cannot be solved without it.
We write complex algorithms to make your extension functions work like the original WA.
4.1 At the moment we haven't found a way to access the high-level API.
4.2 You can give us permission to find workarounds for the high-level WA API described in task list #28.
4.3.1 Task #28 on the task list is to find access to the high-level API. Which will affect most of your tasks and their solutions. If, of course, we can do it.
4.3.2
Finding solutions and time
28.1 (10hr)
28.2 (5hr)
28.3 (10 hours)
28.4 (6 hours)
Most of your tasks require access to a high-level WA API. If we have it: the time to solve most tasks will be significantly reduced or become the most optimal!

Hi, what's the ETA on this?

When the code will be ready?
When will it be in production?

It is fixed. I will upload as beta version to chrome first

authors: FrenkiBeggins liatzionimorad ripper234

repo: zen-mode/Whatsapp-Zen-Mode


text:
Upgrade rdkafka ~> 0.15; require Ruby 3.0 since 2.6 is EOL

What
This PR completes a couple of housekeeping items:

Set required Ruby to >= 3.0 in the Gemspec (2.6 is EOL, 2.7 support dropping in rdkafka-ruby soon, too)
Upgrade rdkafka to ~> 0.15.0

I noticed that rdkafka 0.15.0 minimum Ruby is 2.7 anyway.

@tednology you might as well directly go to 3.0 because I am dropping support for 2.7 soon: https://github.com/karafka/rdkafka-ruby/issues/374

@mensfeld Done.

No need to ping me. It's not my framework and I don't have merge permissions here ;) it was just a friendly advise from rdkafka maintainer.

Hah, well, thanks anyway 😄.
@deepredsky or @dasch, sorry for the ping, would it be possible to review this small upgrade? We don't need the minimum Ruby version requirement @ 3.0 (2.7 will suffice) if it's a concern.

@tednology thanks for this pull request. I need to double check that upgrading rdkafka will not require any additional changes. +1 to dropping 2.6 support

@deepredsky it will not. 0.15.0 is fully backwards compatible with 0.13 though I did change several timeouts to higher values.

You bet!

@deepredsky can you please release a new beta with this change?

Thank you @deepredsky . Unfortunately, I have to bump it in another lib that is built on top of racecar, and this makes things a little bit more complicated to test 😀

authors: deepredsky jandudulski mensfeld tednology

repo: zendesk/racecar


text:
Switch

#24 > #23
Story
As a developer developing the application, I want a form switch field named Switch, so that it can be used to capture date.
Description
A form switch field is a user interface (UI) element commonly used in forms, applications, and websites. It typically consists of a small rectangular or circular control that can be toggled between two states, usually "on" and "off" or "enabled" and "disabled," by clicking or tapping it.
Details
I'd like for you to implement a form switch field component, this field will capture the input as is without validation or any other processing.
In addition, this component should not accept any props instead it should derive the props from FieldContext #77.
Acceptance Criteria

Project builds with no warning

Definition of Done

#4

Sub Tasks

[ ] Unit tests written
[ ] Integration test passing
[ ] Storybook stories written
[ ] Code peer-reviewed
[ ] Tested on supported devices/browser
[ ] Any configuration changes documented

Linked issues

Relates to
Linking type that allows you to establish a relationship between two issues.

#24

Blocked By
Issues or tasks that are blocking the progress of the issue.

#77

@wycliffepeart I added a description

authors: iamshellyan wycliffepeart

repo: zendexa/project


text:
Make use of class names instead of strings for services

Related to issue: https://github.com/zendframework/zend-mvc/issues/186

The Travis is failing on master, too. What can be done?

@thexpand Travis is failing on all latest builds, meaning it tests against all of the latest dependencies. So you could probably run composer update locally and should see the tests fail as well. It makes it easier to find the package that causes the error and fix it. And then you can still decide if you want to include the updated composer file or not.

@xtreamwayz I have created a hotfix for this as a new PR https://github.com/zendframework/zend-mvc/pull/293
We'll be able to continue with the current PR only after the merging the hotfix. Can you make a code review?

authors: thexpand xtreamwayz

repo: zendframework/zend-mvc


text:
[ZF3] FlashMessenger: sort by datetime / multiple tagging

Since the flashMessenger uses namespaces to group the messages, its impossible to sort the messages just by date.
I suggest to remove that limitation. Instead of grouping it in different arrays, maybe it would be better to store them in a single array.
To achieve the different types, maybe we could do that over "tagging". This could also enable mutliple tagging/routing to the right place...

I'm against removing the namespaces because it eases grouping messages a lot. There's been many cases where I've used Namespaces on FlashMessages and found the feature incredibly useful.
However it shouldn't be this difficult to rewrite to have it ordered by date (per namespace though!)
Right now the code is:
$container->{$namespace}->push($message);

All the change required would be
$time = microtime(true) * 1000;
$container->{$namespace}->offsetSet($time, $message);

This however would dare a risk of overwriting messages (though quite low).
I'd rather see an additional FlashMessenger implementation like TimedFlashMessenger that simply does things a bit different. Thoughts?

Should be marked for ZF3 milestone, shouldn't it?

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html
New issue can be found at: https://github.com/zendframework/zend-mvc/issues/178

authors: GeeH RalfEggert ThaDafinser manuakasam


text:
Check alembic branch divergence in CI

Added tiny check to CI to ensure that we don't have branch divergence.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

Linting will fail because of the branch divergence (fixed by #1772)

repo: zenml-io/zenml


text:
documentation bug fixed

Hi Team.
I fixed to react hook documentation bug.

Thanks!

Your are welcome 👍

authors: recepdmr zenoamaro

repo: zenoamaro/react-quill


text:
CLI throws AttributeError when using verify and generate commands

Hi, thanks for providing this awesome dataset and devkit.
I have downloaded the dataset using the CLI tool. I want to verify it and generate an export to MS-COCO format using the CLI as well. When I do, however, I get an AttributeError: 'function' object has no attribute 'base_type' error. I've tried this with fresh python3.9 and python3.10 installations for both the verify as well as the generate command.
zod verify --dataset-root=full --subset=frames --version=full

/root/.pyenv/versions/3.9.20/lib/python3.9/site-packages/zod/cli/verify.py:98 in verify
> zod = subset.dataset_cls(str(dataset_root.expanduser()), version.value)
/root/.pyenv/versions/3.9.20/lib/python3.9/site-packages/zod/_zod_dataset.py:31 in __init__
> self._infos, self._train_ids, self._val_ids = self._load_infos()
 /root/.pyenv/versions/3.9.20/lib/python3.9/site-packages/zod/_zod_dataset.py:97 in _load_infos
> infos = process_map(func, chain.from_iterable(all_ids.values()), ...)
.......
/root/.pyenv/versions/3.9.20/lib/python3.9/concurrent/futures/_base.py:391 in __get_result
>>> AttributeError: 'function' object has no attribute 'base_type'

Limiting the dataclass-wizard version to >=0.22.2,<=0.31.0 fixes this issue for me.

repo: zenseact/zod