text:
Provide separate builds for M1 ARM and x86_64

I'm wondering if you could please provide separate builds for M1 ARM and x86_64, so that I can use one UTM instance for running ARM workloads on ARM, and another (the x86_64 build) for running x86_64 workloads through Rosetta2, which I would hope yield better performance than software emulation via QEMU.
Is this something you could provide? I'm lacking the package signing certificates.
According to the build instructions, it seems separate builds for arm and x86_64 are already supported.
I tried using Apple's framework where you can run an application with Rosetta, but while that starts then the UTM application as Intel, the resulting QEMULauncher app still runs as Apple, even if I tag the QEMULauncher.app inside the UTM.app also as "Open using Rosetta"

Tagging QEMULauncher to run with Rosetta:

However, in the Activity Monitor, it shows it's still running as "Apple", which means it's an ARM executable:

repo: utmapp/UTM


text:
Virtualized VM immediately crashing upon launch on M1 iPadOS 14.5, arm64 Windows 11

Describe the issue
Created VM using "Virtualize" option with Windows 11 (22000.918) arm64 ISO. 4GB RAM and 50GB storage.
Starting VM immediately crashes the app.
Disabling in Settings -> QEMU -> Use Hypervisor allowed the VM to launch.
Configuration (required)

UTM Version: 4.0.4, UTM.HV.ipa used
OS Version: iPadOS 14.5
Device Model: 5th Gen M1 12.9 inch iPad, 16GB RAM
Is it jailbroken (name jailbreak used)? Yes, unc0ver
How did you install UTM? Tried both filza/appsync unified & trollstore

Crash log
UTM-2022-09-11-170412.txt
Debug log
debug.log

Yes, that’s because you are not using iPadOS 15.0~15.1.1
Hypervisor on iPad M1 is only supported on iPadOS 15.0~15.1.1.

iOS 14 requires different hypervisor offsets. I am working on that right now and will provide an IPA to test soon.

Please test https://github.com/utmapp/UTM/suites/8313076043/artifacts/365026554 and post crash log if it still crashes.

It is still crashing but looks like some progress made. Before it would crash instantly after tapping start button but now it gets to grey screen with loading icon in middle that appears before booting.
UTM-2022-09-15-145258.txt
debug.2.log

@meerkatriptide please try https://github.com/utmapp/UTM/suites/8322812338/artifacts/365745890

Getting below screen, no loading bar or any further text appeared after waiting for 10+ minutes.

debug.3.log (This log I just quit the VM almost immediately to generate it)

Fixed in f1997bc976e18ebf31f94f169461a35f2f5c4859

source: gharchive/issue

authors: Suchan0127 meerkatriptide osy

license_type: permissive

license_source: github-api


text:
The blank page was created and counted

I am noticed the blank page was created and counted as a page between chapters on the current version. Please help me to fix it.

Hi
According to
http://sps.utm.my/wp-content/uploads/2018/12/THESIS-GUIDELINES-31.12.2018.pdf
under Section 2.3 (page 15), final printing is double-sided.
If you wish to change manually, change the utmthesis.cls line 118 to become
\LoadClass[a4paper,oneside,12pt,onecolumn]{book}
On Wed, Mar 13, 2019 at 8:54 AM johnspunker notifications@github.com
wrote:

Reopened #15 https://github.com/utmthesis/utmthesis/issues/15.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/utmthesis/utmthesis/issues/15#event-2198872309, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APX1Uj9pGVBlwl2TE8GZNQbAmMjR01i3ks5vWExagaJpZM4bsK1x
.

--
Best regards
Muhammad Nadzir Marsono, Ph.D., P.Eng., C.Eng.
Associate Professor in Electronic and Computer Engineering
School of Electrical Engineering
Faculty of Engineering
Universiti Teknologi Malaysia
Email: mnadzir@utm.my, nadzir@fke.utm.my
Website: www.fke.utm.my/nadzir
Specialization: Digital system-level design, computer architecture,
many-core system-on-chip, network-on-chip, network processing architecture,
network algorithmics

authors: MNMarsono johnspunker

repo: utmthesis/utmthesis

license_source: bigquery


text:
fix: update the versions of dependencies

Fixed hashicorp/consul image version
Replaced hibernate-core dependency

Thanks for your contribution, maybe source code version is outdated. I’ll check and fix it.

All issues are fixed at #86

source: gharchive/pull-request

license: MIT


text:
Test on Fuchsia

We can either do what we do with Redox right now (just build the utils and not actually test them on the operating system) or we could try to build Fuchsia and test using Fargo.  I'm not sure how long a Fuchsia build takes though, so the latter option may be too slow.

No activity for 2+ years, closing.
Feel free to reopen if interested

authors: Arcterus sylvestre

repo: uutils/coreutils


text:
Windows Rust nightly: test_ln::test_symlink_verbose started to fail with ln: Already exists

──── TRY 3 STDERR:       coreutils::tests test_ln::test_symlink_verbose
thread 'test_ln::test_symlink_verbose' panicked at tests\by-util\test_ln.rs:383:10:
Command was expected to succeed. code: 1
stdout =
 stderr = ln: Already exists

stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/bdc6b3de48646345549fd2fe9f62370f56e3fa56/library\std\src\panicking.rs:676
   1: core::panicking::panic_fmt
             at /rustc/bdc6b3de48646345549fd2fe9f62370f56e3fa56/library\core\src\panicking.rs:75
   2: tests::common::util::CmdResult::success
             at .\tests\common\util.rs:417
   3: tests::common::util::UCommand::succeeds
             at .\tests\common\util.rs:1782
   4: tests::test_ln::test_symlink_verbose
             at .\tests\by-util\test_ln.rs:380
   5: tests::test_ln::test_symlink_verbose::closure$0
             at .\tests\by-util\test_ln.rs:364
   6: core::ops::function::FnOnce::call_once<tests::test_ln::test_symlink_verbose::closure_env$0,tuple$<> >
             at /rustc/bdc6b3de48646345549fd2fe9f62370f56e3fa56\library\core\src\ops\function.rs:250
   7: core::ops::function::FnOnce::call_once
             at /rustc/bdc6b3de48646345549fd2fe9f62370f56e3fa56/library\core\src\ops\function.rs:250
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Seen here:
https://github.com/uutils/coreutils/actions/runs/12483954019/job/34840981058?pr=6997
Dunno if it is caused by a rustc usptream change or not

This is very likely an upstream issue. Unfortunately our testing appears to not be quite as robust as coreutils is in this area. I'll try to fix asap.

@ChrisDenton cool! I wasn't expecting someone from upstream seeing this bug that quickly :)
Happy that our impl of the coreutils is used to regressions :)

Thanks to uutils for noticing this! I hopefully fixed the problem. It should be released in the next nightly (2024-12-27).

fixed, thanks!

authors: ChrisDenton sylvestre


text:
pkill: implement

#27

Great start. Could you please add tests?

And also, more unit tests would be better. If it cannot run on Windows, you can disable it for Windows simply.
eg.
#[cfg(target_os = "linux")]
#[test]
fn test_something() {
...
}

authors: Krysztal112233 MCredbear sylvestre

repo: uutils/procps


text:
update jupyterbook toc links to splash pages

As I pointed out during our meeting yesterday, the links to the teams and schedule on the splash page weren't showing up in the Jupyterbook. The links weren't pointing specifically to the jupyter-template repo github.io page.

Note: the jupyterbook front page links are hard coded via the website_url parameter, so they won't point to the preview-built pages in a PR.

@jomey Do we need to specifically create the #section tags in our cookiecutter file so they exist on the splash page? If I use - url: https://uwhackweek.github.io/jupyterbook-template/ in the _toc.yml the entries generate fine (but only go to the top of the page), but as soon as I add #team (- url: https://uwhackweek.github.io/jupyterbook-template/#team) there's something about them jupyterbook doesn't like, so they don't show up in the TOC. There's no warning or error message I can find (even with --verbose) to indicate a problem, and entering the links directly into a browser works fine.

@jomey @scottyhq Any ideas what jupyterbook doesn't like? If I use - url: https://uwhackweek.github.io/jupyterbook-template/ in the _toc.yml the entries generate fine (but only go to the top of the splash page), but as soon as I add #team (- url: https://uwhackweek.github.io/jupyterbook-template/#team) there's something about them jupyterbook doesn't like, so they don't show up in the TOC. There's no warning or error message I can find (even with --verbose) to indicate a problem, and entering the links directly into a browser works fine. The links to the team and schedule section on the home page of the jupyterbook also work fine, so I'm guessing it's something in jupyterbook's creation of the toc that's causing them to get lost?

Let me have a quick peak locally

For anyone watching - we've gotten as far as figuring out that the Jupyterbook toc-url directive doesn't seem to like anchor tags...

Couldn't figure out why JupyterBook in combination with the sphinx-external-toc extension was not happy with hashes '#' in TOC urls. Added some simple logic on the main splash site to navigate to a section when requested via URL parameter. Added benefit is that this now behaves identical to clicking on a link in the navigation bar.
Open to reverting this again if this feels as too much custom logic.

Note: When testing this, make sure you use the preview URL. Right now we have
https://uwhackweek.github.io/jupyterbook-template/index.html
in the TOC and this is the test URL:
https://deploy-preview-64--hackweek-template.netlify.app/index.html?jump_to=team

@jomey This looks like a great workaround to me (see my suggested changes to fix switched links).

Couldn't figure out why JupyterBook in combination with the sphinx-external-toc extension was not happy with hashes '#' in TOC urls.

Do you think we ought to file a bug report with JupyterBook?

Couldn't figure out why JupyterBook in combination with the sphinx-external-toc extension was not happy with hashes '#' in TOC urls.

Do you think we ought to file a bug report with JupyterBook?

Ultimately yes, I would love to figure out a few more details and then file with the appropriate project. Right now I can’t pinpoint if this is JupyterBook, sphinx-external-toc, or an issue somewhere in between those two.

repo: uwhackweek/jupyterbook-template


text:
Update Maven dependencies

First of all: Thank you for this wonderful library!
I thought I could have a go with updating all Maven plugin and dependency versions to their latest.
This went surprisingly well. Compilation and all tests pass.
The only breaking change was the removal of ANTLR's @Nullable. But since there is also a @NotNull, it was rather redundant.

Coverage remained the same at 82.689% when pulling 0f18a9fc7a1b9a7b1f1b0d7fe4cafa153a99616b on httpdigest:master into 79d4090a966d44a838b52c53c65e22ac2cecc51c on uwol:master.

authors: coveralls httpdigest

license: mit


text:
today button wrong display with css body {display: "flex"} in chrome

Expected behaviour
.today with display:table-cell
Actual behaviour
.today with display:block
Datepicker version used
1.6.4.
Example code
https://jsfiddle.net/zjmove/L43p8ek4/
It's because jquery
var a=$('')
a.toggle(true)
//output: 	 wiht css body {display: "flex"} in chrome

it is actually unfortunate to use display block on th since it is not a block, table-cell should be used instead.

authors: Azaret NaturalL

repo: uxsolutions/bootstrap-datepicker


text:
_document.tsxの作成

close #220
概要
_document.tsx を作成し、その中でファビコンの設定とビューポートの設定を付与しました。
補足として、 next/document の Head と next/head の Head の違いは不変かどうかになります。
例えば、 next/document はビューポートやファビコンなどそのサイトで変わることのないものを設定し、 next/head はタイトルや説明などのページごとに異なるものを設定します。

Storybook URL: https://uyupun.github.io/official/feat_220_document/storybook/

今までってfavicon.ico自体は置いてたけどNext.jsからは読み込まれてなかったって感じなんですかね？？

開発サーバからは読み込まれていたのか

そういえばcharset="utf-8"の設定はいらないのかな

titleは今固定だと思うけど、固定なら_document.tsxにおくべきなのではと思わなくもないかも

これも俺の確認ミスやけど読み込まれてたな🙏
ただ、 _document.tsx 内で html と body の設定できるんでついでにビューポートとファビコンも明示させた感じっすね
（一応ビューポートも書き出されてはいたけど、 content 内に initial-scale=1.0 が記述されてなかったので追記してます）

なるほど？ということは開発サーバでも本番ビルドでも今回の変更がなくてもファビコンは読み込まれていた？

タイトルはページが増えた時に変える想定（例えば uyupun - Philosophy など）なんで、記述してない感じっすね

charset="utf-8"はあった方がよさそうやな👍

なるほど？ということは開発サーバでも本番ビルドでも今回の変更がなくてもファビコンは読み込まれていた？

ですね

あんまりよく分かってないけど_document.tsxを置くとデフォルトのページ横断的なヘッダーの設定が上書きされるような挙動なのかな？だとしたら他に設定漏れ無いのかちょっと気になるところではある

あんまりよく分かってないけど_document.tsxを置くとデフォルトのページ横断的なヘッダーの設定が上書きされるような挙動なのかな？だとしたら他に設定漏れ無いのかちょっと気になるところではある

見る限りは上書きされてる感じっすね
なので、Head内はビューポートの設定だけでもいいっちゃいいっすね

なるほど、まあ明示されていた方が分かりやすそうではある

なんか、ファビコンの設定書いてないと出力された head 内にファビコンの設定なかったわ...（キャッシュ？でファビコンが見れてるっぽい...）
後は、ビューポートの設定は上書きされずに複数表示されてるな...
んービューポートの設定だけ消すか（initial-scale=1.0なくても大丈夫なのかな🤔）

それは開発サーバの話？本番ビルドの話、、、？

今までの話全部本番ビルドの話です🙏

キャッシュで見れてるってことは開発サーバではよしなにファビコンを読み込んでくれるけど本番ビルドではそういうことをしてくれないっていう挙動なんだろうか

あとビューポートのinitial-scaleが複数定義されている場合ってどういう挙動になるんだ、、、

headの中↓こんな感じでビューポートの設定（<meta name="viewport" ...>）が2つあるんすよね。initial-scale=1.0が書かれてる方が設定した値になりますね。

一応↓なのでビューポートの設定は消しても大丈夫そうななんで、複数設定されるくらいなら消してなくてよさそうな気がする

initial-scale
ページを最初に読み込んだときの表示倍率を制御します。最小値は 0.1 です。最大値は 10 です。既定値は 1 です。負の値は無視されます。

https://developer.mozilla.org/ja/docs/Web/HTML/Viewport_meta_tag

一応↓なのでビューポートの設定は消しても大丈夫そうななんで、複数設定されるくらいなら消してなくてよさそうな気がする

消してよさそうな気がするってこと？？

んー、上書きできるような書き方が無いなら削除で良いかなあ

消してよさそうな気がするってこと？？

ですね、next側で勝手に設定されてるので大丈夫そうなんで
後、開発サーバでもファビコンの設定はhead内に記述されてなかったっすね。。。なんで表示されてるか謎すぎる。。。

それってキャッシュ削除したらどうなるん？

後、<meta charset="utf-8">これも上書きされずに複数出力されるので、設定しない方向で...💦

キャッシュ消したり、シークレットウィンドで見てみたりしたけどファビコン表示されるな...

実はファビコンってmetaタグで明示しなくても自動的に読み込まれるみたいな仕様あったりする？？

ChatGPT引用

やといったタグがHTML文書に含まれていない場合でも適用されます。このため、favicon.icoをウェブサイトのルートディレクトリに置いておけば、多くの場合は自動的にブラウザにファビコンとして表示されます。

ちょうど調べてたｗ　そうみたいっすね

ただ、ファビコンは明示しときたいね

そうなるともしかして_document.tsxで設定すべき項目ってない？

最悪headの設定はなくてもよさそうやな
htmlのlangは設定しときたいお気持ちはある

今後i18n対応する場合はlangを動的にいじる必要性出てくるかもね

まあlangとファビコンは設定しときますか

ほんまやね

#13

ではビューポートの設定のみrevertしてもらえたらApproveします

57f0459 こちらで消しました🫡

一つのHTML文書には一つのビューポート（viewport）メタタグだけが設定できます。複数のビューポートメタタグを設定すると、ブラウザは通常最初に見つけたタグを使用しますが、これはブラウザの実装によるため、信頼性が低いと言えます。これは、ビューポートの設定が一度に複数存在すると、それらが互いに競合し、予期しないレイアウトやズームの挙動を引き起こす可能性があるからです。
したがって、モバイルフレンドリーなウェブページを設計する際は、次のような形式でビューポートを設定することが一般的です：
<meta name="viewport" content="width=device-width, initial-scale=1">

これにより、デバイスのスクリーン幅をビューポートの幅として設定し、初期のズームレベルを1に設定します。この設定により、ウェブページはさまざまなデバイスやスクリーンサイズで適切に表示されることが期待できます。

こちら参考まで

あざます！

authors: takashi0602 tyokinuhata uyupunpopunpo

repo: uyupun/official


text:
🛑 Third Party IMG is down

In 661ce8a, Third Party IMG ($THIRD_PARTY_IMG) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Third Party IMG is back up in fbfb466 after 11 minutes.


text:
Remove SNI not work with some website

Please read the instruction and answer the following questions before submitting your issue. Thank you.
Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.

What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
4.21.3, also test on 4.18.0, 4.20.0
What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
Access website which are blocked by sni rst.
What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
Not work for some website e.g. www.voanews.com, www.rfa.org, www.pornhub.com
What's your expectation?
Work for all websites which are blocked by sni rst
Please attach your configuration file (Mask IP addresses before submit this issue).
Server configuration:
No server. Works locally.

Client configuration:
"inbounds": [
    {
        "port": 18888,
        "listen": "127.0.0.1",
        "tag": "socks-inbound",
        "protocol": "socks",
        "settings": {
            "auth": "noauth",
            "udp": true,
            "ip": "127.0.0.1"
        },
        "sniffing": {
            "enabled": true,
            "destOverride": [
                "http",
                "tls"
            ]
        }
    },
    {
        "listen": "127.0.0.1",
        "port": 77777,
        "protocol": "dokodemo-door",
        "settings": {
            "network": "tcp",
            "followRedirect": true
        },
        "streamSettings": {
            "security": "tls",
            "tlsSettings": {
                "alpn": [
                    "h2"
                ],
                "certificates": [
                    {
                        "usage": "issue",
                        "certificate": [
                            "..."
                        ],
                        "key": [
                            "..."
                        ]
                    }
                ]
            }
        },
        "tag": "no-sni-inbound"
    }
],
"outbounds": [
    {
        "protocol": "freedom",
        "tag": "direct"
    },
    {
        "protocol": "freedom",
        "settings": {
            "redirect": "127.0.0.1:77777"
        },
        "tag": "no-sni-redirect-outbound"
    },
    {
        "protocol": "freedom",
        "settings": {
            "domainStrategy": "UseIP",
            "redirect": ":443"
        },
        "streamSettings": {
            "security": "tls",
            "tlsSettings": {
                "allowInsecure": true,
                "allowInsecureCiphers": true,
                "alpn": [
                    "h2"
                ]
            }
        },
        "tag": "no-sni-outbound"
    }
],
"routing": {
    "domainStrategy": "AsIs",
    "rules": [
        {
            "type": "field",
            "domain": [
                "..."
            ],
            "inboundTag": "socks-inbound",
            "outboundTag": "no-sni-redirect-outbound"
        },
        {
            "type": "field",
            "inboundTag": "no-sni-inbound",
            "outboundTag": "no-sni-outbound"
        }
    ]
}

Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at /var/log/v2ray/error.log on Linux.

Server error log:
No server.
    // Please attach your server error log here.

Client error log:
2019/11/01 23:05:12 [Info] [539881033] v2ray.com/core/proxy/socks: TCP Connect request to tcp:www.voanews.com:443
2019/11/01 23:05:12 [Info] [539881033] v2ray.com/core/app/dispatcher: sniffed domain: www.voanews.com
2019/11/01 23:05:12 [Info] [539881033] v2ray.com/core/app/dispatcher: taking detour [no-sni-redirect-outbound] for [tcp:www.voanews.com:443]
2019/11/01 23:05:12 tcp:127.0.0.1:11304 accepted tcp:www.voanews.com:443 [no-sni-redirect-outbound]
2019/11/01 23:05:12 [Info] [539881033] v2ray.com/core/proxy/freedom: opening connection to tcp:127.0.0.1:77777
2019/11/01 23:05:12 [Info] [539881033] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:127.0.0.1:77777
2019/11/01 23:05:12 [Info] [3948075443] v2ray.com/core/app/dispatcher: taking detour [no-sni-outbound] for [tcp:www.voanews.com:0]
2019/11/01 23:05:12 [Info] [3948075443] v2ray.com/core/proxy/freedom: opening connection to tcp:www.voanews.com:443
2019/11/01 23:05:13 [Info] [3948075443] v2ray.com/core/proxy/freedom: dialing to to tcp:104.122.18.18:443
2019/11/01 23:05:13 [Info] [3948075443] v2ray.com/core/transport/internet/tcp: dialing TCP to tcp:104.122.18.18:443
2019/11/01 23:05:14 [Info] [3948075443] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > v2ray.com/core/proxy/freedom: failed to process response > read tcp xxx.xxx.xxx.xxx:xxx->104.122.18.18:443: wsarecv: An existing connection was forcibly closed by the remote host.
2019/11/01 23:05:14 [Info] [3948075443] v2ray.com/core/app/proxyman/inbound: connection ends > v2ray.com/core/proxy/dokodemo: connection ends > v2ray.com/core/proxy/dokodemo: failed to transport response > io: read/write on closed pipe
2019/11/01 23:05:14 [Info] [539881033] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/01 23:05:20 [Info] v2ray.com/core/app/proxyman/outbound: failed to process outbound traffic > v2ray.com/core/proxy/freedom: connection ends > context canceled
2019/11/01 23:05:20 [Info] v2ray.com/core/transport/internet/udp: failed to handle UDP input > io: read/write on closed pipe

Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.
No server.

    // Please attach your server access log here.

This config works for www.quora.com, reddit.com, imgur.com, www.pixiv.net, zh.wikipedia.org . Thanks for any help!

Only look your coding cannot understand what you want to do. Can you provide all client and server both side coding (Pls remember hide the server address and any uuid) and provide more description.

@kingwilliam Sorry, let me make it clear. I want to use v2ray as a local proxy to bypass sni rst. I follow this post https://steemit.com/cn/@v2ray/sni . Because it's difficult to use a transparent proxy, I set a socks proxy (socks-inbound) and redirect (no-sni-redirect-outbound) to the transparent proxy (no-sni-inbound) . So there is no server. The path is socks-inbound -> no-sni-redirect-outbound -> no-sni-inbound -> no-sni-outbound . This config works with some websites ( www.quora.com, reddit.com, imgur.com, www.pixiv.net, zh.wikipedia.org) but not works with others ( www.voanews.com, www.rfa.org, www.pornhub.com) .

the original page already say this technical is not always accept, depend by the web server.
"Domain Fronting 实际上不是一个合理的用法，网站完全可以拒绝这类连接，比如 Google 和 Amazon 就主动在自己的所有服务中拒绝这项技术。"
"Domain Fronting is actually not a reasonable use, and websites can reject such connections. For example, Google and Amazon actively reject this technology in all of their services."
could you consider build the vps v2ray server to let you cross over the firewall?

Yeah, this technical won't work with some websites. However,  www.voanews.com, www.rfa.org, www.pornhub.com accept https without sni. They are listed here and accesser works with them.

Yeah, this technical won't work with some websites. However, www.voanews.com, www.rfa.org, www.pornhub.com accept https without sni. They are listed here and accesser works with them.

Yes, that means that some sites do not have strict SNI verification, so you can use erase SNI for Domain fronting.
The Domain fronting itself is a hack method. Don't expect to be versatile and need to adapt to the case.

I found the problem, The config in the blog use h2 while some websites do not support h2. Browser will connect to V2Ray with h2 but v2ray will connect to server with h1. For compatibility we should set alpn to http/1.1 instead.


text:
Grid with unknown size

Hello,
Grid lazy loading works well based on How to load paged data (lazy-load) in Vaadin.
As I don't know the total size (I'd need to iterate all items) of the data set:

I've tried to don't pass the optional parameter size of the GridDataProviderCallback
the data are fetched from the endpoint but the grid is empty.

Any idea what I might be doing wrong?
AFAIK this works well in Flow via LazyDataView.
Thanks in advance
Roman

For now I use
    async itemsProvider(
        params: GridDataProviderParams<any>,
        callback: GridDataProviderCallback<any>
    ) {
        ...
        let totalSize = params.page * params.pageSize + items.length + 1; //+1 -> workaround, produces extra empty row
        callback(items, totalSize);
    }

so when I scroll down, next batch is loaded.

repo: vaadin/hilla


text:
the plugin Activity BPMN visualize report a error when i use activity7 in idea2021.1

java.lang.IllegalArgumentException: Unknown type: bpmn:tFormalExpression
at com.valb3r.bpmn.intellij.plugin.activiti.parser.ActivitiObjectFactory.fillForSequenceFlow(ActivitiObjectFactory.kt:146)
at com.valb3r.bpmn.intellij.plugin.activiti.parser.ActivitiObjectFactory.propertiesOf(ActivitiObjectFactory.kt:133)
at com.valb3r.bpmn.intellij.plugin.core.newelements.NewElementsProvider.propertiesOf(NewElementsProvider.kt)
at com.valb3r.bpmn.intellij.plugin.bpmn.api.BpmnProcessObject.fillFor(BpmnProcessObject.kt:146)
at com.valb3r.bpmn.intellij.plugin.bpmn.api.BpmnProcessObject.extractElementsFromBody(BpmnProcessObject.kt:118)
at com.valb3r.bpmn.intellij.plugin.bpmn.api.BpmnProcessObject.toView(BpmnProcessObject.kt:25)
at com.valb3r.bpmn.intellij.plugin.core.CanvasBuilder.build(CanvasBuilder.kt:54)
at com.valb3r.bpmn.intellij.plugin.core.BpmnPluginToolWindow.run(BpmnPluginToolWindow.kt:82)
at com.valb3r.bpmn.intellij.activiti.plugin.actions.ViewActivitiBpmnDiagramAction$actionPerformed$1.run(ViewActivitiBpmnDiagramAction.kt:25)
at com.intellij.openapi.wm.impl.ToolWindowManagerImpl$activateToolWindow$1.run(ToolWindowManagerImpl.kt:632)
at com.intellij.openapi.application.TransactionGuardImpl.runWithWritingAllowed(TransactionGuardImpl.java:218)
at com.intellij.openapi.application.TransactionGuardImpl.access$200(TransactionGuardImpl.java:21)
at com.intellij.openapi.application.TransactionGuardImpl$2.run(TransactionGuardImpl.java:200)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:781)
at com.intellij.openapi.application.impl.ApplicationImpl.lambda$invokeLater$4(ApplicationImpl.java:319)
at com.intellij.openapi.application.impl.FlushQueue.doRun(FlushQueue.java:84)
at com.intellij.openapi.application.impl.FlushQueue.runNextEvent(FlushQueue.java:133)
at com.intellij.openapi.application.impl.FlushQueue.flushNow(FlushQueue.java:46)
at com.intellij.openapi.application.impl.FlushQueue$FlushNow.run(FlushQueue.java:189)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:776)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:746)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:969)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:839)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:449)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:808)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$9(IdeEventQueue.java:448)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:781)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:496)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

@hqa11 Thanks for feedback, but please provide example BPMN file to reproduce


text:
compatibility with Mermaid in LivePreview

In LivePreview, a Mermaid inside an Admoonition frequently does not parse correctly.
After opening the code and closing it, it works again.
No problem in Reading view

Used code example for reference:
collapse: closed
title: Inclusioni

```mermaid
flowchart

subgraph INCLUSIONI
direction TB

Multiverso(["Multiverso"]):::internal-link
PianoMateriale(["Piano Materiale"]):::internal-link
GrandeOltre(["Grande Oltre"]):::internal-link
SistemaSolare(["Sistema Solare"]):::internal-link
Golarion(["Golarion"]):::internal-link
SferaInterna(["Sfera Interna"]):::internal-link
SferaEsterna(["Sfera Esterna"]):::internal-link
PianoAstrale(["Piano Astrale"]):::internal-link
AltriSistemi("altri sistemi solari"):::internal-link
AltriPianeti("altri pianeti"):::internal-link

class Multiverso main
class AltriSistemi simpletext
class AltriPianeti simpletext

Multiverso-- "include" -->PianoMateriale & GrandeOltre
PianoMateriale-- "include" -->SistemaSolare-- "include" -->Golarion & AltriPianeti
PianoMateriale-- "include" -->AltriSistemi-- "include" -->AltriPianeti
GrandeOltre-- "include" -->SferaInterna & PianoAstrale & SferaEsterna

end
```

Live Preview's handling of asynchronous embedded content isn't perfect. This will have to wait until Obsidian releases an updated embedded content rendering API.


text:
Gregorian Events Not Updating

We discussed this on Discord but here's a gif to jog your memory, idk how to describe it but the events are all hinky.

This should be fixed in the latest release.


text:
Introduce a new way of handling array objects

This PR supercedes #2.
After that pull request, the following changes were done:

Results of PyDict_SetItem and PySet_Add are now checked to prevent crashing in case of incorrect Python objects
The new behaviour is now enabled explicitly by the new kwarg listOnly in Reader constructor. By default the old behaviour is used
Tests were changed to test both old and new behaviours

Any comments and suggestions are welcome!

PyPy failed again. Will fix promptly

repo: valkey-io/libvalkey-py


text:
Whats  the 'query option'

I need data from the database so hardcoded list are useless.
I'm thinking this might help if I knew what it was.
"If omitted, items are not available locally, and the query option should be provided to fetch data."

+1

authors: Gaelmart anasAsh


text:
Relax dependencies versions

Proposed changes
Some of the dependencies are versioned very strictly, which makes it hard to use this with other libraries.
Fixes
I tried to relax versions as much as possible, while keeping compatibility for the future, according to semantic versioning.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ x] Bugfix (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 not work as expected)

Checklist
Put an x in the boxes that apply.

[x ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.

I don' see develop branch :(

[ x] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@angrybayblade Sure, I see I changed too much (I didn't know about this plugin-specific stuff).
The trouble we are facing (Gnosis AI team), is that we want to use the mech-client which depends on open-aea.
But for example, open-aea is strictly versioned to use click==8.0.2

@kongzii I'll try to loosen up the dependency range for both requests and click, but here's an failure that I was talking about with click - https://github.com/valory-xyz/open-aea/actions/runs/8812842872/job/24209365609?pr=736#step:10:87

@angrybayblade That should be easily fixable. I see there was even an explicit ignore to not warn about this depreciation. I'll try to fix it.

@angrybayblade, I pushed a fix. Could you please try to run the workflow now?

@angrybayblade Thanks for the approval and merge! Could you please also take a look at https://github.com/valory-xyz/mech-client/pull/41 or should I ping someone else about that repo? 🙏

authors: angrybayblade kongzii

repo: valory-xyz/open-aea


text:
Padding=2 in Resnet blocks?

Thanks for your good code! May I ask why the padding=2 in your resnet block (which was shaved latter)? Will it make a better results?

That’s a good point! The authors used ShaveImage at first and it got me confused. I didn't realize that ShaveImage has been removed in original code:
https://github.com/junyanz/CycleGAN/commit/ad98146d0e20240fa53f3338dbacfdd331155b49
So padding should be 1 and no need to shave, right?

Yes, it seems you can use 1 padding and remove the shaving. Another question, in your code, the batch normalization is used without scale=True, which is also different from the author's code.

Thanks! I'll fix it.

authors: LynnHo vanhuyz

repo: vanhuyz/CycleGAN-TensorFlow


text:
chore: update dependencies

CHANGES:

Updated kiwi to support analyzer 4.0.0

Because kiwi_generator >=4.0.2 depends on analyzer ^3.2.0 and freezed 2.1.1 depends on analyzer ^5.0.0, kiwi_generator >=4.0.2 is incompatible with freezed 2.1.1.

I'm closing the PR as it became irrelevant with the newest kiwi updates.

authors: SebastianWaloszek j-ibarra

repo: vanlooverenkoen/kiwi


text:
Docker build error - ambiguous use of 'hex'

When running tests inside a Docker container I get the following error:
/package/.build/checkouts/Imperial/Sources/Imperial/Services/Shopify/URL+Shopify.swift:13:10: error: ambiguous use of 'hex'
swapper_1_c2f870a92ea5 |                 return hmac.hex
swapper_1_c2f870a92ea5 |                        ^
swapper_1_c2f870a92ea5 | /package/.build/checkouts/Imperial/Sources/Imperial/Services/Shopify/URL+Shopify.swift:26:16: note: found this candidate
swapper_1_c2f870a92ea5 |     public var hex: String {
swapper_1_c2f870a92ea5 |                ^
swapper_1_c2f870a92ea5 | /package/.build/checkouts/vapor/Sources/Vapor/Utilities/Bytes+Hex.swift:2:16: note: found this candidate
swapper_1_c2f870a92ea5 |     public var hex: String {
swapper_1_c2f870a92ea5 |                ^
swapper_1_c2f870a92ea5 | [2239/2281] Compiling Imperial GoogleJWTResponse.swift
swapper_1_c2f870a92ea5 | /package/.build/checkouts/Imperial/Sources/Imperial/Services/Shopify/URL+Shopify.swift:13:10: error: ambiguous use of 'hex'
swapper_1_c2f870a92ea5 |                 return hmac.hex
swapper_1_c2f870a92ea5 |                        ^
swapper_1_c2f870a92ea5 | /package/.build/checkouts/Imperial/Sources/Imperial/Services/Shopify/URL+Shopify.swift:26:16: note: found this candidate
swapper_1_c2f870a92ea5 |     public var hex: String {
swapper_1_c2f870a92ea5 |                ^
swapper_1_c2f870a92ea5 | /package/.build/checkouts/vapor/Sources/Vapor/Utilities/Bytes+Hex.swift:2:16: note: found this candidate
swapper_1_c2f870a92ea5 |     public var hex: String {
swapper_1_c2f870a92ea5 |                ^
swapper_1_c2f870a92ea5 | [2240/2281] Compiling Imperial GoogleJWTRouter.swift
swapper_1_c2f870a92ea5 | /package/.build/checkouts/Imperial/Sources/Imperial/Services/Shopify/URL+Shopify.swift:13:10: error: ambiguous use of 'hex'
swapper_1_c2f870a92ea5 |                 return hmac.hex

It seems like the package has a conflict with Vapor package extension. I don't have any custom similar extensions in the project. This only happens when running tests inside a Docker container. Everything works fine in XCode.
Imperial version: 1.0.0-beta.1
Vapor version: 4.14.0

I'm seeing the same issue in XCode with Vapor version 4.27.1

@jstorm31 @litso turns out this was already fixed but a release hadn't been tagged. I've just release 1.0.0 Beta 2 which should solve the issues

Great, I can confirm the build succeeds now. Thanks. 🙂

repo: vapor-community/Imperial


text:
Allow for identifying compound heterozygous candidates with only one parent

In certain situations, only a duo (index + one of the parents) is available. In theory, this should still allow for identifying potential compound heterozygous candidates, as the single parent can be used to identify variants in the index, which are inherited from said parent, e.g. any compound heterozygous variant should be a pair of:

A: index var+ parent var
B: index var+ parent no-call/WT

Currently using the c-h preset with duos does not seem to work. The generated gene list does not look correct.

I had a weird case, already works as expected.

repo: varfish-org/varfish-server


text:
Implement SV database upgrade

Is your feature request related to a problem? Please describe.
The built-in SV databases are not really up to date.
Describe the solution you'd like

Clinical Structural Variants (Update: 30-08.2020) https://www.ncbi.nlm.nih.gov/dbvar/studies/nstd102/
NCBI curated common structural variants (Update 18-09.2020) https://www.ncbi.nlm.nih.gov/dbvar/studies/nstd186/

Describe alternatives you've considered
N/A
Additional context
N/A

Done by switch to rust-based worker.


text:
Create datasets for testing

Currently we use the files from libmaxminddb.
This means that it is impossible to run make check from a GH created tarball (or zip) since submodules are not packaged.
One alternative is to create our own set of files that live in this repor and the tests could use.

Did you consider using adding a GitHub action to download the test files, or include script to fetch them? This is what I use in our environment (excerpt)
#!/bin/bash
# ...
MAXMINDTESTDB="https://github.com/maxmind/MaxMind-DB/raw/main/test-data"

MAXMINDTESTFILES=(
  'GeoIP2-City-Test'
  'GeoIP2-Connection-Type-Test'
  'GeoIP2-ISP-Test'
  'MaxMind-DB-test-decoder'
)

mkdir -p libmaxminddb/t/maxmind-db/test-data

for i in "${MAXMINDTESTFILES[@]}"; do
  wget -q -P libmaxminddb/t/maxmind-db/test-data/ "${MAXMINDTESTDB}/${i}.mmdb"
done

make check || error_exit 'Failed to make check'
# ...

@GeertHauwaerts Nop, thanks for the suggestion. I will have a look 👍

Done.

authors: GeertHauwaerts fgsch


text:
Exporter unit test fails

The exporter unit test is unreasonably slow and produces an requirement failed error. Output:
- historical query with importer
  -> prepare importer [line 162]
  -> ingest conn.log via importer [line 164]
  -> spawn exporter for historical query [line 167]
  -> fetch results [line 169]
  -> ... got 26 events [line 117]
  -> got 26 events in total [line 125]
!! ../libvast/test/system/exporter.cpp:171  ::caf::test::equal_to(results.size(), 28u) (26 !! 28)
     REQUIRED: ::caf::test::equal_to(results.size(), 28u)
     ../libvast/test/system/exporter.cpp:158  had last successful check
Abort trap: 6

Fixed via https://github.com/vast-io/vast/pull/224

repo: vast-io/vast


text:
Number system calculator

Calculator Functions
conversion for decimal to binary,octal,hexadecimal and vice versa.
I am  contributor in  GSSOC-22
can you assign this issue to me?
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

sure, this issue will be assigned to you! but start the coding part after the contribution period starts!
I will assign this issue to you by tomorrow!!

You can assign this issue to youself by typing /assign in the comment !!

/assign

/assign

/assign


text:
VAT_Calculator

Calculator Functions
Calculator Functions
Description : Hello, I am a contributor in GSSOC' 22. I want to make VAT Calculator that  calculates the Value Added Tax (VAT) on products or services.
This calculator has two input fields, one for amount and another one for vat rate and two output fields , one is for VAT amount and another one for VAT Inclusive amount.
Contribution Event
GSSOC22
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

I want to work on this .pls assign me this issue under GSsoc 22.

/assign

please assign this issue to me


text:
Job status report inconsistency

I've got a multi-step workflow running on PBS system. I only had the first step completed, with an error message:
ERROR: 47 jobs completed, 2 jobs aborted

I know that I submitted 49 jobs. But I do see 49 output from this step.
I then tried:
sos status | grep $name | grep completed | wc -l
49

and sos status | grep aborted returns nothing.
So according to sos status, all 49 were successful.
Sorry I cannot give a MWE (how can I provide one). Just make a note here. Maybe the new zmq will hopefully have it addressed due to general improvements? (you see I have a lot faith in that branch).

BTW all my stderr file showed no problem. It is just a bit inconvenient that my intended overnight workflow did not go through due to the false alarm.

That branch is progressing step by step to keep the current tests passing. Right now the slot manager is gone, signatures are written by a single thread, with #1056 as a blocker for concurrent substeps. You are right that the reporting part is being reconsidered so it might fix this problem.
However, using zmq in a more sophisticated way as ipyparallel #1057 does would be very difficult to a point that we might want to just use ipyparallel although our DAG execution pattern does not really fit to their model. On the other hand they say their model is flexible enough to accommodate all task models so I will read about ipyparallel more before I attempt to use more sophisticated worker management patterns. This is why I was asking if such patterns are needed.
So I suppose I will fix #1056 and stop their before major problems with the DAG execution part are found.

The false alarm is likely caused by some filesystem hiccups that prevents sos from detecting the activities of the tasks (no change of pulse file after 10+ seconds) after a while. The workflow thinks the tasks were dead but the tasks continued to run and completed without problem.
The pulse mechanism is used to tells the task engine that the task is still alive. It is file based because the tasks could be executed over remote machine on a shared file system (like cluster). This is one of the major differences between sos and other systems in that sos relies on the task themselves to report that they are alive where others rely on live workers (that execute more than one tasks) to report them. That is to say, sos execute task executes a single task without contacting the task engine. The task engine checks the change of task file to determine task status. On other systems, the tasks are executed by workers with live connection to the task engine...

authors: BoPeng gaow

repo: vatlab/SoS


text:
Deprecate section option skip

The skip option had a long history from VPT and is used to skip a section
[10: skip=True]

It was supposed to be used for

Quickly comment on a step but renaming the step would have the same effect.
Enable certain steps depending on the complexity of the workflow (e.g. sos run --quality-control true) but we already have many ways to do the same (e.g. subworkflow).

I have never used it for any production code and do not see a good usage for it.

Hmm I've always been using stop_if but I can see skip_if an appealing feature. eg I do use:
stop_if(some_file.exists(), msg = '...')

so maybe we want to make it skip_if and decprecate that section option?

Currently we do not have skip_if but we do have stop_if, which essentially serve as skip_if because it does not raise an error. There is even a test case for
[10]
output: 'a.txt'
_output.touch()
stop_if(true)

for a.txt to be kept when the substep is stopped.
I have not tested but I think
[10: skip=True]

would be the same as
[10]
stop_if(True)

well,
[1]
stop_if(True)
[2]
print(999)

gives:
999

so stop_if is indeed skip_if. I was under the impression stop_if will quit the execution without printing 999 -- then this might warrant a feature request for a real stop_if -- some parameters, or for clarity, make stop_if and skip_if separate?

There is a fail_if.

There is a fail_if.

I understand. But fail_if will result in return code 1 right? What if we want a peaceful complete stop?

I think conceptually there can be a skip_if, that is to say,

skip_if is the safe skip, with no consequence. (this is the current stop_if).
stop_if to stop the current substep, with the _output removed due to failure of the substep.
fail_if to stop the entire workflow.

Then that thing can be called done_if. 😄

With so many if then all the active options can be deprecated #1064

stop_if to stop the current substep, with the _output removed due to failure of the substep.

I'm not sure why you want this. If the step fails it should just quit on error. fail_if should stop the entire workflow with output from current step removed.
So yes we can have skip_if, stop_if and fail_if; stop_if is done_if.
RE #1064: I think an attempt was made along the line of not using active in #1108 but did not work. Maybe we can revisit that example after we have implemented skip_if? Things might have worked now.

Removing _output is now the standard procedure for atomic write. So

skip_if will be like "break" of a loop. However, the _output needs to be generated before it. Otherwise the step will fail with _output does not exist after the completion of the step.

stop_if currently stops the substep, but not the entire step. If also does not removing existing _output. I am not sure what behavior you would like to have.

fail_if will terminate the execution of the workflow. Not sure if it kills running steps.

done_if will mark the end of the workflow. Not sure if it kills running steps.

So basically there are several complications here:

If other substeps will be affected.
If _output will be removed.
If other running steps should be killed.

skip_if will be like "break" of a loop.

well, rather be like continue of a loop? I'm saying the current stop_if should be renamed to skip_if. Its corresponding _output should be removed  from step_output. Now I agree what you said previously that "the _output removed due to failure of the substep." -- but it is not a failure, it is what we asked for.
So without worrying about backwards compatibility, conceptually:

skip_if to replace current stop_if which is continue for a loop; but output properly adjusted
stop_if to behave like done_if to peacefully end a workflow. It does not kill running steps.
fail_if to quit with error, kills running steps

Now we lack a break loop behavior which I'm not sure would be necessary ... trying to think of a case we might need it.

And we are evaluating this with #1064 in mind ... so we might want to be thorough here and resolve both tickets.

I do not have a good overall solution now, perhaps in the end we will need to have something like
stop_if(condition, remove_output, end=substep/step/workflow)

Also, skip means skip at least the substep (remove what might have been done till now), so _output should be removed silently, The continue operation sounds more like end_substep_if...
In any case let us deprecate the step option skip for now.

We will need to list all use cases and their pros and cons to decide what to do with this. For example, stop_if does not work well for
input: a large number of groups
stop_if(_index > 10)

because all steps will be generated and then be stopped. In this particular case we are looking for something like break, not the stop_if, which is essentially continue.

I still think my comment here plus the possible need for a break behavior (also in that comment) are good enough. Of course we might want to keep the behavior of stop_if for backwards compatibliity.
BTW even fail_if now does not break the loop. I think it should.

Thinking of application, I think the following can be useful but we need to make sure that the names are not confusing:

name
usage
remove _output
stop step
step workflow

skip_if or continue_if
continue, not an error
no
no
no

stop_if ?
continue, is an error
yes
no
no

fail_if
exception
yes
yes
no (allow other steps to complete)

done_if
break like
no
yes but peacefully
no

terminate_if
exception
yes
yes
yes (stop workflow immediately )

when fail_if stops (the rest of) a step with error, doesnt it automatically stop the entire workflow? Or the parts of DAG not depending on it will still work?
I think some peaceful stop of the entire workflow is also welcomed? So I think fail_if should stop the workflow and terminate_if quits the entire workflow peacefully.
why do we ever need keep_output = True? that output is generated in previous code chunks but the rest of the code will not be executed? I do not see this happen very often ... at least ggenerating output is usually the last few lines of my code. ...

So for 3 I'm still tshinking:

name
usage
remove _output
stop step
step workflow

skip_if ?
stop the substep, assuming output is invalid and should be removed if already exist
yes
no, run other substeps as planned
no

stop_if / break_if
break like, stop sending new substeps
yes for substeps > _index
no
no

For skip_if, I had sometimes "manual signature" check, something like
[10]
stop_if('done' in whatever_mechanism)
task:
long_job

Technically speaking, there is a difference in whether or not 10 should be explicitly killed due to fail_if in 20.
[10]
sleep(20000)

[20]
input: None
fail_if(True)

But I do not know which way is better or if we should allow both. This also applies to done_if and done_if(all) (for stopping the entire workflow).

I still think the scope of something like done_if is confined within a step and fail_if stops the entire workflow -- basically if one sees something "fail", it would be natural to stop everything and fix it up immediately, rather than having to live with it and wait for other tasks to finish before attending to the problematic runs. It is somewhat awkward otherwise.

See the above table. What about

Change the behavior of fail_if to kill immediately.
Keep stop_if as it is (remove _output)
Add skip_if or an option to stop_if to disable the behavior of removing _output
Add done_if as the break behavior. It will continue to submit _index <= done_if_index,  stop submitting new and remove _output of _index > done_if_index.

I see. I mostly agree with the current proposal, plus:

If we are to keep the behavior of stop_if then I vote for adding an option to let stop_if keep the output.
The problem to have done_if is that in scenarios not involving substeps, it will behave like stop_if. So maybe we should use another stop_if option to implement this, something like:

stop_if(mode = 'break') for the done_if
stop_if(mode = 'continue') for the stop_if(keep_output = True) ?

OK, the mode parameter is not terribly clear what will happen, so I would prefer two parameters:

stop_all=True, keep_output=True:  this assume everything has been done before, we stop every substep but does not change _output.
stop_all=True, keep_output=False: we need to be more careful about this one because we have to do things differently for substeps before and after _index as proposed.
stop_all=False, keep_output=True: assuming this substep is done, keep other substeps running
(default) stop_all=False, keep_output=False: not do this one at all, remove _output.

Okay, but stop_all sounds less intuitive than break ... ? Especially when the function name already has a stop


text:
Make rayon optional

After upgrading to 0.8 the crate can no longer be used on the wasm32 target, as a threadpool can not be initialized:

panicked at 'The global thread pool has not been initialized.: ThreadPoolBuildError { kind: IOError(Custom { kind: Other, error: "operation not supported on this platform" }) }'

Could the dependency on rayon be made into a (default) feature instead, to allow usage on this platform?

Yes having it default but optional seems the way to go.

authors: mulimoen vbarrielle

repo: vbarrielle/sprs


text:
Исправление потери параметров

параметры запроса терялись при передаче параметров вторым аргументов метода Get;

параметры преобразования Json терялись в методе КакJson

параметры запроса терялись при передаче параметров вторым аргументов метода Get;

параметры преобразования Json терялись в методе КакJson

А можно увидеть пример, в котором эти параметры теряются?

Пофиксил здесь
https://github.com/vbondarevsky/Connector/commit/f0d37ae34af6b30102eb417270785e1b3027f2d9
Это PR ломает часть тестов

authors: adminimusRU vbondarevsky

repo: vbondarevsky/Connector


text:
small updates

just some quick clarity updates.

Thank you for your input. It is much appreciated! It might appear that I am not considering your updates but all of which you have suggested have been incorporated in a bigger commit. So, again many thanks for following and contributing!

authors: funixz vchintal


text:
⚠ Spryr has degraded performance

In 01d5b1b, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 503
Response time: 4476 ms

Resolved: Spryr performance has improved in 3853f8e after 7 minutes.

repo: vcsphere/upptime


text:
⚠ Spryr has degraded performance

In d4d5b6a, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 5628 ms

Resolved: Spryr performance has improved in 6815814 after 23 minutes.


text:
Introduction description on Rationale

The spec says:

However, JWT-based credentials do not support selective disclosure, i.e., the ability for a Holder to disclose only a subset of the claims contained in the JWT, which is a requirement to implement the three-party-model efficiently.

In my opinion this is not correct, because the text basically says: "JWT-based credentials do not support selective disclosure [...] which is a requirement to implement the three-party-model efficiently". Imo the need for SD-JWT comes from the shift from IdP to three-party-model.
My proposal:
"While JWT-based credentials enable selective disclosure, i.e., the ability for a holder to disclose only a subset of the contained claims, in an Identity Provider ecosystem by issuing new JWTs to the Verifier for every presentation, this approach does not work in the three-party-model."

+1

@paulbastian do you want to create the PR? Or should I create the PR?

I can do, just wanted to make sure its not for waste. Issue is less effort ;P

authors: awoie paulbastian tlodderstedt

repo: vcstuff/draft-terbu-sd-jwt-vc


text:
Can you add a CITATION.cff for easy citation?

First of all, thank you for the interesting work.
I'd like to cite this repository in a paper, can you please add a CITATION.cff or create a DOI?

Done, thank you for the pointer.

repo: vectara/hallucination-leaderboard


text:
Add Help Documentation

We need some sort of on-page documentation for how the plots work, what the selectors do, etc.
Options for this:

Add little help buttons everywhere. This is probably bad since it'll clutter up the layout
Add a help page, with a video or a bunch of pictures or something.
Do the fancy thing that fancy sites do, and when a help button in the navbar is pressed, render a translucent overlay with tooltips explaining each element

Closed by #241

repo: vector-engineering/covidcg


text:
Try to avoid the auto restart behaviour when resuming it

Many users reported us that the application is automatically restarted when it is resumed.
The memory warning is another case : the system warns us that there is no more available memory on the device and the client is going to be killed so it seems better to restart the client to reduce its memory usage and to avoid crash.
But there are other cases in which the application restarts whereas it is not expected.
With their help, we found out that the service (events polling thread) is killed or some other required fields are not initialised (e.g active sessions list) : the client detects that something is not valid in its fields and restarts to avoid crash.
I never got such behaviour on my devices (Nexus 6 - Android M, Samsung S3 - Android 4.2.2, Zenfone 550KL - android 5.01).
I suspect that there is a custom home launcher (or something similar) which kills service or stop the client in putting a pending activity to resume it.
I assume it appends when the device memory usage becomes high without being urgent.

By now, with the help of some users (thanks to them), we identified two use cases
1- The eventStreamService was released by the OS when the application is in background.
So, when the application is resumed, the activity might be created again (after a memory pressure) but the event stream is released : the client used to restart to manage this case
By now, the event stream is started again.
2- the application is resumed from the login activity.
It happens with some launchers or when the application activities are popped up by pressing the back button until to reach the device home page.
We already found out that Intent.FLAG_ACTIVITY_BROUGHT_TO_FRONT implies to display a temporary activity above existing one (it should be managed by now).
It seems there are other flags which might triggers invalid behaviours

It seems being fixed by now.

repo: vector-im/vector-android


text:
Readme edits

New hello message added to readme file.
Also, outdated description message has been removed.
Please review it.

Checked and confirmed. Looks good!

repo: vedrank/hello-world


text:
Combine Entry, File and Directory in a struct

3 - Combine the File and Directory struct
Fixes #3
Description

I merged removed Entry and replaced it with File.
I added type_ as FileType to Metadata in order to match against dir/file/symlink.

Type of change
Please select relevant options.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] My code follows the contribution guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I formatted the code with cargo fmt
[x] I checked my code using cargo clippy and reports no warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] The changes I've made are Windows, MacOS, Linux compatible (or I've handled them using cfg target_os)
[x] I increased or maintained the code coverage for the project, compared to the previous commit

Acceptance tests

[x] Unit tests

[ ] regression test: ...

Pull Request Test Coverage Report for Build 1645868916

59 of 93 (63.44%)  changed or added relevant lines in 4 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+1.3%) to 76.989%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/fs/file/mod.rs
19
22
86.36%

src/fs/file/file_type.rs
21
31
67.74%

src/fs/mod.rs
0
21
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/fs/file/mod.rs
1
85.42%

src/fs/mod.rs
1
3.45%

Totals

Change from base Build 1644101214:
1.3%

Covered Lines:
358

Relevant Lines:
465

💛  - Coveralls

authors: coveralls veeso

repo: veeso/remotefs-rs


text:
Add usermeta top-level field, optional and ignored by parser.

Addresses https://github.com/vega/vega/issues/1061.
Looks like there are some docs to be updated in vega/vega; not clear if these are generated from the schema or manually updated.
Please let me know if there's anything else that needs to accompany this PR that I missed!
@domoritz please review.

Thanks! I've reviewed and will add schema validation support for usermeta separately, using a simpler approach.
However, this PR also includes usermeta definitions and documentation as a config option. Is including a default, global usermeta object desired as part of the Vega configuration? Currently it might be included as config but this would have no effect whatsoever -- it would not be accessible in any way.
My current understanding is that usermeta should be an optional part of the Vega JSON input but is otherwise ignored. If you want this metadata to some how propagate through (e.g., to be accessible from a view instance), that should be subject to further discussion on a separate issue.

Nope, adding to config was unintentional -- I was following the pattern of background and missed that background is in fact relevant to config. Per the earlier thread, usermeta should exist only at the top level of the spec and nowhere else. I don't see a need for accessing usermeta from within a View instance (though that may be worth floating on the original thread).

authors: ericsoco jheer

repo: vega/vega-parser


text:
Add volume spark line

Spark line beside volume ???
Best thing would be a spark line of up to one month growth - trend of volume - should be a library already in console in the market popup

Weeks can exhibit seasonality... most recent 24h volume + spark line is fine
We do have volume by day on the console, so this must be availalble, check with them how to source.

We should be able to do this, and it should be available as a shared component, so why not.

repo: vegaprotocol/frontend-monorepo


text:
Update circe to 0.7.0

ref #95

Codecov Report

Merging #102 into master will not change coverage.
The diff coverage is 69.5%.

@@           Coverage Diff           @@
##           master     #102   +/-   ##
=======================================
  Coverage   70.25%   70.25%
=======================================
  Files          27       27
  Lines        1785     1785
  Branches        6        6
=======================================
  Hits         1254     1254
  Misses        531      531

Impacted Files
Coverage Δ

core/src/main/scala/vegas/spec/Spec.scala
69.42% <69.5%> (ø)
:arrow_up:

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 ff51dff...9c661b7. Read the comment docs.

Alex (jhnsmth), Apologies for missing this PR. I have fixed this for now. I'll pay attention in the future in not duplicating work. Thanks for your contribution.

This is a duplicated of https://github.com/vegas-viz/Vegas/pull/103, so will be closed. Thanks.

authors: codecov-io dbtsai jhnsmth rogermenezes

repo: vegas-viz/Vegas


text:
🐞 Node.js 16 actions are deprecated.

Describe the bug
When running the github action, you now get the following warning;
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: vemonet/setup-spark@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Reproduction
No response
Which version of the action are you using?
v1
With which versions of Spark is it happening?
na
Operating System and environment
github hosted
Additional context
No response

Thanks @apeyrat ! I updated it and released an new version (updated v1 too)

authors: apeyrat vemonet

repo: vemonet/setup-spark


text:
Update package.json on Vendure release

This repo still points to vendure 0.13.0, when 0.14.0 was released last week.  I know the main repo releases everything at once, but it would be nice to update the plugin-template as well.

Fixed by you ;)

Do you think this could be updated automatically when vendure releases new
updates?  I'm not sure how your ci pipeline is set up.
On Fri, Aug 14, 2020, 2:20 PM Michael Bromley notifications@github.com
wrote:

Closed #2 https://github.com/vendure-ecommerce/plugin-template/issues/2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vendure-ecommerce/plugin-template/issues/2#event-3657243052,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4R2FHBLET7LIHE2NRFZVDSAV57TANCNFSM4PORIURA
.

Ah I didn't get that you meant to automate it. Hmm... In theory the version could be bumped by a CI action, but this could get tricky when there are breaking changes that mean manual changes are needed to some of the code in the template.

Fair point
On Fri, Aug 14, 2020, 3:27 PM Michael Bromley notifications@github.com
wrote:

Ah I didn't get that you meant to automate it. Hmm... In theory the
version could be bumped by a CI action, but this could get tricky when
there are breaking changes that mean manual changes are needed to some of
the code in the template.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vendure-ecommerce/plugin-template/issues/2#issuecomment-674237218,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG4R2FBWY62GAGUNWT7FI2DSAWF2HANCNFSM4PORIURA
.

authors: drewterry michaelbromley

repo: vendure-ecommerce/plugin-template


text:
iOS 11 Issue with TouchID

I am testing my app in iOS 11 and I found an issue in VENTouchLock.
When the app enters the background it calls [self lock] which in turn brings up the Touch ID prompt.
In iOS 10 and earlier the Touch ID screen would load inside the app and the user doesn't see it until they bring the app to the foreground. In iOS 11 beta 4 the Touch ID screen opens in the main window as soon the app is in the background.
If you authorise at that point then when the app comes to the foreground it is already unlocked.
I've made a video to explain it better. I can investigate a fix for this, but as the authors of this module I assume you will do a better job :)

I tested this in the sample app and it was fine.
For some reason my version of the code for the file VENTouchLock/VENTouchLock/Controllers/VENTouchLockSplashViewController.m was out of date. I'm not sure how this happened as I am using cocoa pods, but with the latest code there is no issue.

repo: venmo/VENTouchLock


text:
Move workers to separate entity

Move notifier worker pool to its own separate entity

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (9ee0f17) 91.32% compared to head (1e35582) 93.35%.

Files
Patch %
Lines

handler.go
80.48%
5 Missing and 3 partials :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #5      +/-   ##
==========================================
+ Coverage   91.32%   93.35%   +2.02%
==========================================
  Files           6        6
  Lines         346      361      +15
==========================================
+ Hits          316      337      +21
+ Misses         24       16       -8
- Partials        6        8       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter veqryn

repo: veqryn/slog-bugsnag


text:
Cant Connect BigCommerce, Vercel Connection Down?

Using the template "Connect BigCommerce Integration" button, I get the error "The page URL is invalid. Please contact Vercel support for assistance."
I have tried on different browsers and devices even. No luck same error.

Would you mind opening an issue on their repo if you are still having problems? 🙏
https://github.com/bigcommerce/nextjs-commerce

authors: leerob ozeitis

repo: vercel/commerce


text:
revalidateOnMount: true and revalidateOnFocus: false do not work together.

Hi,
These options do not work together.
{
revalidateOnMount: true,
revalidateOnFocus: false
}
If  revalidateOnFocus is set to false, swr stops revalidating on mount. The desired behavior is that revalidation should happen only when route is changed, not on re-focus of page.
Am I missing anything?

If revalidateOnFocus is set to false, swr stops revalidating on mount.

This sounds like a bug, could you provide a reproduction on CodeSandbox maybe?

authors: animeshchat shuding

repo: vercel/swr


text:
Include the dependencies on how a hash is computed into verbose logs

Describe the feature you'd like to request
I am currently trying to find out, why my turbo repo is constantly missing the cache, and tried the -vvv flag, but this isn't giving me any meaningful insights on why the cache is being missed.
It would be awesome to get an overview, of what is being used to compute the cache hash, so that I could see what the config is missing/has too much.
Describe the solution you'd like
See above, solution is described above.
Describe alternatives you've considered
No alternatives right now.

I have the same problem, it would be nice to see what exactly bursting the cache.
I tried to integrate Trubo instead of our current task runner https://github.com/folke/ultra-runner which is doing mostly the same (incremental builds, deps graph and etc). But that constant cache bursting stopping me.
By the way ultra-runner is awesome and shows what exactly bursting the cache, but miss some important features from turbo (cache in one folder vs spread across monorepo, prune command)

Just wanted to say that I'm going to be starting work on this soon! Stay tuned

Hey @iduuck and @thekip , try out the --summarize flag in any turbo run. Documentation coming in https://github.com/vercel/turbo/pull/4467. (Please file new issues if there are more things you want!)

authors: iduuck mehulkar thekip

repo: vercel/turbo


text:
Possible bug with the integration of external local packages and Remix

What version of Turborepo are you using?
1.0.23
What package manager are you using / does the bug impact?
npm
What operating system are you using?
Linux
Describe the Bug
Given the default examples from both the turborepo and remix CLIs
When importing the Button component from the ui local package
Then receives an ESM related syntax error on the page
import * as React from "react";
^^^^^^

SyntaxError: Cannot use import statement outside a module

PS: It works properly with CJS
Thank you for the excellent product by the way
Expected Behavior
Given the default examples from both the turborepo and remix CLIs
When importing the Button component from the ui local package
Then don't receive an ESM related syntax error on the page
To Reproduce
Example repo: https://github.com/viniciusflv/remix-esm-bug
npm: 8.1.0
node: 14.15.5
Run
npx create-turbo@latest
Remove next examples from ./app (Optional)
Run inside ./app
npx create-remix@latest
Remove remix package-lock.json and node_modules
Run on root
npm i
Import and use ui Button component at the main route apps/remix/app/routes/index.tsx
Run dev
npm run dev
Open on localhost to see the error

This is because the default turbo example ui doesn't transpile itself, but rather lets next.js do it via next-transpile-modules. The suggestion is to use something like tsup like in the kitchen sink example here https://github.com/vercel/turborepo/tree/main/examples/kitchen-sink/packages/ui

For future reference people who use Nest.js:
In your app with health: "*" dependency:
import { HealthModule } from 'health'

@Module({
  imports: [
    HealthModule,
  ],
})
export class AppModule {}

Then in your packages/health/package.json:
{
  "name": "health",
  "version": "0.0.0",
  "publishConfig": {
    "access": "public"
  },
  "main": "./dist/health.module.js",
  "types": "./dist/health.module.d.ts",
  "scripts": {
    "build": "tsup src/*.ts --dts --format cjs"
  },
  "devDependencies": {
    "@anatine/esbuild-decorators": "^0.2.19",
    "tsconfig": "*",
    "tsup": "^6.7.0"
  },
  "dependencies": {
    "@nestjs/common": "^9.4.1",
    "@nestjs/swagger": "^6.3.0",
    "@nestjs/terminus": "^9.2.2"
  }
}

And then finally packages/health/tsup.config.ts
import { esbuildDecorators } from '@anatine/esbuild-decorators'
import { defineConfig, Options } from 'tsup'

export default defineConfig((options: Options) => ({
  ...options,
  sourcemap: true,
  clean: true,
  esbuildPlugins: [esbuildDecorators()],
}))

For future reference people who use Nest.js:
In your app with health: "*" dependency:
import { HealthModule } from 'health'

@Module({
  imports: [
    HealthModule,
  ],
})
export class AppModule {}

Then in your packages/health/package.json:
{
  "name": "health",
  "version": "0.0.0",
  "publishConfig": {
    "access": "public"
  },
  "main": "./dist/health.module.js",
  "types": "./dist/health.module.d.ts",
  "scripts": {
    "build": "tsup src/*.ts --dts --format cjs"
  },
  "devDependencies": {
    "@anatine/esbuild-decorators": "0.2.19",
    "tsup": "6.7.0"
  },
  "peerDependencies": {
    "@nestjs/common": "9.4.1",
    "@nestjs/swagger": "6.3.0",
    "@nestjs/terminus": "9.2.2",
    "tsconfig": "*"
  }
}

And then finally packages/health/tsup.config.ts
import { esbuildDecorators } from '@anatine/esbuild-decorators'
import { defineConfig, Options } from 'tsup'

export default defineConfig((options: Options) => ({
  ...options,
  sourcemap: true,
  clean: true,
  esbuildPlugins: [esbuildDecorators()],
}))

You can use tsup-node as far as you do not need to bundle Node.js app.
See: https://tsup.egoist.dev/#excluding-all-packages

authors: Geebrox developer239 jaredpalmer viniciusflv


text:
Unexpected token o in JSON at position 1

Prerequisites
We do our best to reply to all the issues on time. If you will follow the given guidelines, the turn around time will be faster.

Ensure the issue isn't already reported.
Ensure you are reporting the bug in the correct repo.

Delete the above section and the instructions in the sections below before submitting
Description
If this is a feature request, explain why it should be added. Specific use-cases are best.
For bug reports, please provide as much relevant info as possible.
Package version
2.0.2
Error Message & Stack Trace
err: {
2022-08-02T09:57:23.591840955Z       "type": "SyntaxError",
2022-08-02T09:57:23.591846064Z       "message": "Unexpected token o in JSON at position 1",
2022-08-02T09:57:23.591851234Z       "stack":
2022-08-02T09:57:23.591855993Z           SyntaxError: Unexpected token o in JSON at position 1
2022-08-02T09:57:23.591860772Z               at JSON.parse ()
2022-08-02T09:57:23.591866212Z               at Object.consume (/opt/microservices/node_modules/@verful/notifications/build/src/Models/DatabaseNotification.js:41:38)
2022-08-02T09:57:23.591871723Z               at /opt/microservices/node_modules/@adonisjs/lucid/build/src/Orm/BaseModel/index.js:1196:37
2022-08-02T09:57:23.591876812Z               at Array.forEach ()
2022-08-02T09:57:23.591881732Z               at Proxy.$consumeAdapterResult (/opt/microservices/node_modules/@adonisjs/lucid/build/src/Orm/BaseModel/index.js:1183:40)
2022-08-02T09:57:23.591886851Z               at Function.$createFromAdapterResult (/opt/microservices/node_modules/@adonisjs/lucid/build/src/Orm/BaseModel/index.js:274:18)
2022-08-02T09:57:23.591891921Z               at /opt/microservices/node_modules/@adonisjs/lucid/build/src/Orm/QueryBuilder/index.js:197:50
2022-08-02T09:57:23.591896890Z               at Array.reduce ()
2022-08-02T09:57:23.591920064Z               at HasManyQueryBuilder.execQuery (/opt/microservices/node_modules/@adonisjs/lucid/build/src/Orm/QueryBuilder/index.js:195:37)
2022-08-02T09:57:23.591925344Z               at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-08-02T09:57:23.591930183Z       "status": 500
2022-08-02T09:57:23.591935082Z     }
Relevant Information
This is happening every time I want to access users' database notifications. I followed the instructions (pretty straightforward to be honest) but didn't come to a working solution. FYI, the database is Postgres.
I identified that this part of the code is responsible for that:
@column({       prepare: (value) => JSON.stringify(value),       consume: (value) => JSON.parse(value),     })     public data: Record<string, any>
from src/Models/DatabaseNotification.ts
why is stringifying and parsing necessary? Adonis handles jsons automatically, doesn't it?

It depends on the db, it handles automatically for pretty much all the ones I tried except SQLite.
Can you provide an example of the data you are trying to store?

It depends on the db, it handles automatically for pretty much all the ones I tried except SQLite.
Can you provide an example of the data you are trying to store?

here it is:
public toDatabase(_user: User) {         return {             type: 'OVERDUE_PAYMENT',             text: Reminder by ${this.issuerName}: ${this.note},         };     }

it is stored correctly but when I want to get it, it's not working. I noticed, that Adonis doesn't need prepare & consume for jsons. I am using jsons in other tables in my DB and everything works flawlessly without needing to stringify on input and parse on output.
That is why I am asking

I dont looked at the JSON serializing process of lucid, but i think Adonis leaves it to the database driver, and in the case of SQLite, it doesn't handle serialization properly, anyway, i will look for a fix and try to release it tomorrow.

i faced same issue with postgres too

Same thing here on postgres, great package though. Commenting out the prepare/consume on the data column fixes the issue.

authors: arthur-er justDare lukfor85 steveyout

repo: verful/adonis-notifications


text:
can't build VERGE - make error

Hi,
I've trying to build VERGE.
./autogen.sh && ./configure
doesn't make any problems.
But when I want to
make
it. I got a bunch of errors.

In file included from main.h:8:0,
from bloom.cpp:8:
bignum.h:51:24: error: invalid use of incomplete type ‘BIGNUM {aka struct bignum_st}’
class CBigNum : public BIGNUM
^~~~~~
In file included from /usr/include/openssl/bn.h:32:0,
from bignum.h:10,
from main.h:8,
from bloom.cpp:8:
/usr/include/openssl/ossl_typ.h:80:16: note: forward declaration of ‘BIGNUM {aka struct bignum_st}’
typedef struct bignum_st BIGNUM;
^~~~~~~~~
In file included from main.h:8:0,
from bloom.cpp:8:
bignum.h: In constructor ‘CBigNum::CBigNum()’:
bignum.h:56:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
^
bignum.h: In copy constructor ‘CBigNum::CBigNum(const CBigNum&)’:
bignum.h:61:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
^
bignum.h:62:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)’
if (!BN_copy(this, &b))
^
bignum.h:64:31: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_clear_free(BIGNUM*)’
BN_clear_free(this);
^
bignum.h: In member function ‘CBigNum& CBigNum::operator=(const CBigNum&)’:
bignum.h:71:30: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)’
if (!BN_copy(this, &b))
^
bignum.h: In destructor ‘CBigNum::~CBigNum()’:
bignum.h:78:27: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_clear_free(BIGNUM*)’
BN_clear_free(this);
^
bignum.h: In constructor ‘CBigNum::CBigNum(signed char)’:
bignum.h:82:47: error: ‘BN_init’ was not declared in this scope
CBigNum(signed char n)      { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(short int)’:
bignum.h:83:47: error: ‘BN_init’ was not declared in this scope
CBigNum(short n)            { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(int)’:
bignum.h:84:47: error: ‘BN_init’ was not declared in this scope
CBigNum(int n)              { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(long int)’:
bignum.h:85:47: error: ‘BN_init’ was not declared in this scope
CBigNum(long n)             { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(int64)’:
bignum.h:86:47: error: ‘BN_init’ was not declared in this scope
CBigNum(int64 n)            { BN_init(this); setint64(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(unsigned char)’:
bignum.h:87:47: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned char n)    { BN_init(this); setulong(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(short unsigned int)’:
bignum.h:88:47: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned short n)   { BN_init(this); setulong(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(unsigned int)’:
bignum.h:89:47: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned int n)     { BN_init(this); setulong(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(long unsigned int)’:
bignum.h:90:47: error: ‘BN_init’ was not declared in this scope
CBigNum(unsigned long n)    { BN_init(this); setulong(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(uint64)’:
bignum.h:91:47: error: ‘BN_init’ was not declared in this scope
CBigNum(uint64 n)           { BN_init(this); setuint64(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(uint256)’:
bignum.h:92:47: error: ‘BN_init’ was not declared in this scope
explicit CBigNum(uint256 n) { BN_init(this); setuint256(n); }
^
bignum.h: In constructor ‘CBigNum::CBigNum(const std::vector&)’:
bignum.h:96:21: error: ‘BN_init’ was not declared in this scope
BN_init(this);
^
bignum.h: In member function ‘void CBigNum::setulong(long unsigned int)’:
bignum.h:102:33: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_set_word(BIGNUM*, long unsigned int)’
if (!BN_set_word(this, n))
^
bignum.h: In member function ‘long unsigned int CBigNum::getulong() const’:
bignum.h:108:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
return BN_get_word(this);
^
bignum.h: In member function ‘unsigned int CBigNum::getuint() const’:
bignum.h:113:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
return BN_get_word(this);
^
bignum.h: In member function ‘int CBigNum::getint() const’:
bignum.h:118:43: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘long unsigned int BN_get_word(const BIGNUM*)’
unsigned long n = BN_get_word(this);
^
bignum.h:119:33: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
if (!BN_is_negative(this))
^
In file included from main.h:8:0,
from bloom.cpp:8:
bignum.h: In member function ‘void CBigNum::setint64(int64)’:
bignum.h:165:37: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(pch, p - pch, this);
^
bignum.h: In member function ‘uint64 CBigNum::getuint64()’:
bignum.h:170:50: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
unsigned int nSize = BN_bn2mpi(this, NULL);
^
bignum.h:174:32: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
BN_bn2mpi(this, &vch[0]);
^
bignum.h: In member function ‘void CBigNum::setuint64(uint64)’:
bignum.h:207:37: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(pch, p - pch, this);
^
bignum.h: In member function ‘void CBigNum::setuint256(uint256)’:
bignum.h:235:37: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(pch, p - pch, this);
^
bignum.h: In member function ‘uint256 CBigNum::getuint256()’:
bignum.h:240:50: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
unsigned int nSize = BN_bn2mpi(this, NULL);
^
bignum.h:244:32: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
BN_bn2mpi(this, &vch[0]);
^
bignum.h: In member function ‘void CBigNum::setvch(const std::vector&)’:
bignum.h:266:46: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(&vch2[0], vch2.size(), this);
^
bignum.h: In member function ‘std::vector CBigNum::getvch() const’:
bignum.h:271:50: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
unsigned int nSize = BN_bn2mpi(this, NULL);
^
bignum.h:275:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
BN_bn2mpi(this, &vch[0]);
^
bignum.h: In member function ‘CBigNum& CBigNum::SetCompact(unsigned int)’:
bignum.h:289:44: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘3’ to ‘BIGNUM* BN_mpi2bn(const unsigned char*, int, BIGNUM*)’
BN_mpi2bn(&vch[0], vch.size(), this);
^
bignum.h: In member function ‘unsigned int CBigNum::GetCompact() const’:
bignum.h:295:50: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
unsigned int nSize = BN_bn2mpi(this, NULL);
^
bignum.h:298:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_bn2mpi(const BIGNUM*, unsigned char*)’
BN_bn2mpi(this, &vch[0]);
^
bignum.h: In member function ‘std::__cxx11::string CBigNum::ToString(int) const’:
bignum.h:343:35: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘void BN_set_negative(BIGNUM*, int)’
BN_set_negative(&bn, false);
^
bignum.h:346:29: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
if (BN_cmp(&bn, &bn0) == 0)
^
bignum.h:348:32: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
while (BN_cmp(&bn, &bn0) > 0)
^
bignum.h:350:54: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_div(BIGNUM*, BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_div(&dv, &rem, &bn, &bnBase, pctx))
^
bignum.h:356:32: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
if (BN_is_negative(this))
^
bignum.h: In member function ‘bool CBigNum::operator!() const’:
bignum.h:389:31: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_zero(const BIGNUM*)’
return BN_is_zero(this);
^
bignum.h: In member function ‘CBigNum& CBigNum::operator+=(const CBigNum&)’:
bignum.h:394:35: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_add(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_add(this, this, &b))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator*=(const CBigNum&)’:
bignum.h:408:41: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_mul(BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_mul(this, this, &b, pctx))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator<<=(unsigned int)’:
bignum.h:427:41: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_lshift(BIGNUM*, const BIGNUM*, int)’
if (!BN_lshift(this, this, shift))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator>>=(unsigned int)’:
bignum.h:438:28: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
if (BN_cmp(&a, this) > 0)
^
bignum.h:444:41: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_rshift(BIGNUM*, const BIGNUM*, int)’
if (!BN_rshift(this, this, shift))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator++()’:
bignum.h:453:47: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_add(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_add(this, this, BN_value_one()))
^
bignum.h: In member function ‘CBigNum& CBigNum::operator--()’:
bignum.h:470:45: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_sub(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_sub(&r, this, BN_value_one()))
^
bignum.h: In function ‘const CBigNum operator+(const CBigNum&, const CBigNum&)’:
bignum.h:495:27: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_add(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_add(&r, &a, &b))
^
bignum.h: In function ‘const CBigNum operator-(const CBigNum&, const CBigNum&)’:
bignum.h:503:27: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_sub(BIGNUM*, const BIGNUM*, const BIGNUM*)’
if (!BN_sub(&r, &a, &b))
^
bignum.h: In function ‘const CBigNum operator-(const CBigNum&)’:
bignum.h:511:43: error: cannot convert ‘CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_is_negative(const BIGNUM*)’
BN_set_negative(&r, !BN_is_negative(&r));
^
bignum.h: In function ‘const CBigNum operator*(const CBigNum&, const CBigNum&)’:
bignum.h:519:33: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_mul(BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_mul(&r, &a, &b, pctx))
^
bignum.h: In function ‘const CBigNum operator/(const CBigNum&, const CBigNum&)’:
bignum.h:528:39: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_div(BIGNUM*, BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_div(&r, NULL, &a, &b, pctx))
^
In file included from bignum.h:10:0,
from main.h:8,
from bloom.cpp:8:
bignum.h: In function ‘const CBigNum operator%(const CBigNum&, const CBigNum&)’:
bignum.h:537:10: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘2’ to ‘int BN_div(BIGNUM*, BIGNUM*, const BIGNUM*, const BIGNUM*, BN_CTX*)’
if (!BN_mod(&r, &a, &b, pctx))
^
In file included from main.h:8:0,
from bloom.cpp:8:
bignum.h: In function ‘const CBigNum operator<<(const CBigNum&, unsigned int)’:
bignum.h:545:33: error: cannot convert ‘CBigNum*’ to ‘BIGNUM* {aka bignum_st*}’ for argument ‘1’ to ‘int BN_lshift(BIGNUM*, const BIGNUM*, int)’
if (!BN_lshift(&r, &a, shift))
^
bignum.h: In function ‘bool operator==(const CBigNum&, const CBigNum&)’:
bignum.h:557:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator==(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) == 0); }
^
bignum.h: In function ‘bool operator!=(const CBigNum&, const CBigNum&)’:
bignum.h:558:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator!=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) != 0); }
^
bignum.h: In function ‘bool operator<=(const CBigNum&, const CBigNum&)’:
bignum.h:559:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator<=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) <= 0); }
^
bignum.h: In function ‘bool operator>=(const CBigNum&, const CBigNum&)’:
bignum.h:560:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator>=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) >= 0); }
^
bignum.h: In function ‘bool operator<(const CBigNum&, const CBigNum&)’:
bignum.h:561:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator<(const CBigNum& a, const CBigNum& b)  { return (BN_cmp(&a, &b) < 0); }
^
bignum.h: In function ‘bool operator>(const CBigNum&, const CBigNum&)’:
bignum.h:562:83: error: cannot convert ‘const CBigNum*’ to ‘const BIGNUM* {aka const bignum_st*}’ for argument ‘1’ to ‘int BN_cmp(const BIGNUM*, const BIGNUM*)’
inline bool operator>(const CBigNum& a, const CBigNum& b)  { return (BN_cmp(&a, &b) > 0); }
^
make[1]: *** [libbitcoin_server_a-bloom.o] Fehler 1
make: *** [all-recursive] Fehler 1

See attached  file.
make.log

Hi, the workaround is to downgrade to libssl 1.0 within boost... complex, not sure is suggestable on a machine used for other than mining (i.e. generic/general everyday usage + mining + old SSL = other compatibility issues somewhere else.
As you can see on an official Bitcoin Github issue -> https://github.com/bitcoin/bitcoin/issues/7086 - Bitcoin and other miners share this problematics in relation to boost and eventually including MIT licences (which would alter the project-specific licensising) ... complex
I let other users contribut to this open issue.

Otherwhise look at Docker, even if is not the solution and neither simpler approach :)

dont worry, we're fixing the bignum solution shortly. our newest qt is actually using the newest version of ssl. we have a solution and it will be pushed here soon

ok thx for help.

authors: Kryschuuu fantuz justinvforvendetta

repo: vergecurrency/VERGE


text:
Add author profile page and link in blog posts

closes #6

Here's a screenshot of a profile page (with annotation), so waiting for bios.

Here's how authors look on a blog post:

The update on the whole is awesome.
One thing that I'm not sure I like is that previous employees (Sakari in this example) is marked as "Ex Crew" with no picture. Why is that important to highlight? Feels wrong IMHO.

@kvarak thanks for feedback. Was not at all meant in that way, but I can see where you are coming from.
Amended to remove titles from authors view:

And when viewing someone's profile who no longer works at Verifa this is what you see:

authors: jlarfors kvarak

repo: verifa/website


text:
Colorizing and stylizing the progress bars \ spinners

Also started implementing this (using ANSI escape codes), is it something you are open for PR on?
Example:

I would be interested in https://github.com/python-progress/python-progress.  Though
I would like to see some standard python library for ANSI colors used.

Something like colorama ?

I wouldn't like the existing ones to change. However if you want to submit some new ones I would be open to it.

@farchy I was thinking about something like blessings, termcolor, or so.  The reason is
some nontrivial bureaucracy around terminal colors (detection that terminal supports
colors e.g. and fallback to non-colorized version).

OK, I'll try moving to one of these libs (currently my own implementation as a MixIn)

Maybe submit a first PR now to see what you have before going too deep into integrating stuff.

Did anyone had any solution for this? :D

authors: BarryThrill farchy praiskup verigak

repo: verigak/progress

license: isc


text:
Ensure systemd doesn't terminate VerneMQ if it is slow to start

fixes #1251

Great, looks good to me! :rocket:

authors: francois-travais larshesel

repo: vernemq/vernemq


text:
FakeIP模式下电视怎么ipv6解锁奈飞

设备是 sony tv，fakeip混合模式，机场通过v6解锁的Netflix，openclash调试了很多配置电视还是走到了Netflix的v4域名（只知道apple tv会有这个问题）。同网络下手机、电脑播放时看到倒是ipv6开头的域名。
配置：路由关闭了ipv6 dhcp + 未勾选允许ipv6域名解析 + 未开启ipv6代理 + 启用了流媒体域名定时解析。

好奇fakeip混合模式下域名是怎么解析的，还会交给机场节点么？
电视通过v6解锁netflix还有解么

atv好像只能V4

我是索尼电视，openwrt里tcpdump了53端口的包，并没有什么可疑/规则外的域名。头大，不知道怎么检测出来的。

放弃了，后台看到有直接用ip发起的链接。。。

authors: evolsnow vernesong

repo: vernesong/OpenClash