text:
内核报错。求一套稳定点的的程序版本与内核版本组合

Verify Steps

[X] Tracker 我已经在 Issue Tracker 中找过我要提出的问题
[X] Latest 我已经使用最新 Dev 版本测试过，问题依旧存在
[X] Core 这是 OpenClash 存在的问题，并非我所使用的 Clash 或 Meta 等内核的特定问题
[X] Meaningful 我提交的不是无意义的 催促更新或修复 请求

OpenClash Version
0.45.100-bate & 0.45.103-bate
Bug on Environment
Lean
Bug on Platform
Linux-armv7
To Reproduce
LEDE与Openclash同时开启，clash使用redir-host 兼容。
Describe the Bug
LEDE与Openclash同时开启，过一段时间就会因为clash的内核报错导致LEDE的内核也一并报错，通常导致一段时间断网，期间整个内回环也非常慢。
OpenClash Log
OpenClash-2023-3-10-2-26-26.log
OpenClash Config
`
config openclash 'config'
option proxy_port '7892'
option tproxy_port '7895'
option mixed_port '7893'
option socks_port '7891'
option http_port '7890'
option dns_port '7874'
option update '0'
option cn_port '9090'
option dashboard_password '123456'
option dashboard_forward_ssl '0'
option rule_source '0'
option ipv6_enable '0'
option ipv6_dns '0'
option other_rule_auto_update '0'
option servers_if_update '0'
option servers_update '0'
option log_level '0'
option proxy_mode 'rule'
option intranet_allowed '1'
option disable_udp_quic '1'
option enable_rule_proxy '0'
option filter_aaaa_dns '0'
option small_flash_memory '0'
option interface_name '0'
option log_size '1024'
option tolerance '0'
option store_fakeip '0'
option custom_fallback_filter '0'
option custom_fakeip_filter '0'
option custom_host '0'
option custom_name_policy '0'
option stream_domains_prefetch '0'
option stream_auto_select '0'
option bypass_gateway_compatible '0'
option github_address_mod '0'
option urltest_address_mod '0'
option urltest_interval_mod '0'
option delay_start '0'
option router_self_proxy '1'
option release_branch 'master'
option dashboard_type 'Official'
option yacd_type 'Official'
option append_default_dns '0'
option geo_custom_url 'https://testingcf.jsdelivr.net/gh/alecthw/mmdb_china_ip_list@release/lite/Country.mmdb'
option chnr_custom_url 'https://ispip.clang.cn/all_cn.txt'
option chnr6_custom_url 'https://ispip.clang.cn/all_cn_ipv6.txt'
option cndomain_custom_url 'https://testingcf.jsdelivr.net/gh/felixonmars/dnsmasq-china-list@master/accelerated-domains.china.conf'
option core_version 'linux-armv7'
option default_resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option config_path '/etc/openclash/config/Tag3.yaml'
option restricted_mode '0'
option dnsmasq_noresolv '0'
option dnsmasq_resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
option cachesize_dns '0'
option redirect_dns '0'
option enable_custom_dns '1'
option find_process_mode '0'
option global_client_fingerprint '0'
option enable_meta_sniffer '0'
option geodata_loader '0'
option enable_geoip_dat '0'
option enable_custom_clash_rules '1'
option geo_auto_update '0'
option geo_update_week_time '1'
option geo_update_day_time '0'
option geoip_auto_update '0'
option geosite_auto_update '0'
option chnr_auto_update '0'
option chnr_update_week_time '1'
option chnr_update_day_time '0'
option auto_restart '0'
option auto_restart_week_time '1'
option auto_restart_day_time '0'
option auto_update '1'
option config_auto_update_mode '0'
option config_update_week_time '1'
option auto_update_time '6'
option operation_mode 'redir-host'
option lan_ac_mode '0'
option common_ports '0'
option append_wan_dns '1'
option enable_meta_core '0'
option china_ip_route '1'
option enable_redirect_dns '2'
option en_mode 'redir-host'
option enable_udp_proxy '0'
list lan_ac_black_ips '192.168.2.1/32'
list lan_ac_black_ips '192.168.2.2/31'
list lan_ac_black_ips '192.168.2.4/30'
list lan_ac_black_ips '192.168.2.8/29'
list lan_ac_black_ips '192.168.2.16/28'
list lan_ac_black_ips '192.168.2.32/27'
list lan_ac_black_ips '192.168.2.64/26'
list lan_ac_black_ips '192.168.2.128/25'
list lan_ac_black_ips '192.168.3.0/24'
list lan_ac_black_ips '192.168.4.0/22'
list lan_ac_black_ips '192.168.8.0/21'
list lan_ac_black_ips '192.168.16.0/20'
list lan_ac_black_ips '192.168.32.0/19'
list lan_ac_black_ips '192.168.64.0/18'
list lan_ac_black_ips '192.168.128.0/17'
option core_type 'TUN'
list lan_ac_black_ports '10690'
list lan_ac_black_ports '10695'
list lan_ac_black_ports '5000'
list lan_ac_black_ports '10183'
option config_reload '1'
option enable '0'
config dns_servers
option group 'nameserver'
option type 'udp'
option ip '114.114.114.114'
option enabled '0'
config dns_servers
option group 'nameserver'
option type 'udp'
option ip '119.29.29.29'
option enabled '0'
config dns_servers
option group 'nameserver'
option type 'udp'
option ip '119.28.28.28'
option enabled '0'
config dns_servers
option group 'nameserver'
option type 'udp'
option ip '223.5.5.5'
option enabled '0'
config dns_servers
option type 'https'
option ip 'doh.pub/dns-query'
option group 'nameserver'
option enabled '0'
config dns_servers
option type 'https'
option ip 'dns.alidns.com/dns-query'
option group 'nameserver'
option enabled '0'
config dns_servers
option type 'https'
option group 'fallback'
option ip 'dns.cloudflare.com/dns-query'
option enabled '0'
config dns_servers
option group 'fallback'
option ip 'dns.google'
option port '853'
option type 'tls'
option enabled '0'
config dns_servers
option group 'fallback'
option type 'https'
option ip '1.1.1.1/dns-query'
option enabled '0'
config dns_servers
option group 'fallback'
option ip '1.1.1.1'
option port '853'
option type 'tls'
option enabled '0'
config dns_servers
option group 'fallback'
option ip '8.8.8.8'
option port '853'
option type 'tls'
option enabled '0'
config dns_servers
option type 'udp'
option group 'fallback'
option ip '2001:4860:4860::8888'
option port '53'
option enabled '0'
config dns_servers
option type 'udp'
option group 'fallback'
option ip '2001:4860:4860::8844'
option port '53'
option enabled '0'
config dns_servers
option type 'udp'
option group 'fallback'
option ip '2001:da8::666'
option port '53'
option enabled '0'
config dns_servers
option group 'fallback'
option type 'https'
option ip 'public.dns.iij.jp/dns-query'
option enabled '0'
config dns_servers
option group 'fallback'
option type 'https'
option ip 'jp.tiar.app/dns-query'
option enabled '0'
config dns_servers
option group 'fallback'
option type 'https'
option ip 'jp.tiarap.org/dns-query'
option enabled '0'
config dns_servers
option group 'fallback'
option ip 'jp.tiar.app'
option type 'tls'
option enabled '0'
config dns_servers
option group 'fallback'
option ip 'dot.tiar.app'
option type 'tls'
option enabled '0'
config authentication
option enabled '1'
option username 'Clash'
option password 'tT9JLkgs'
`
Expected Behavior
不知道是不是独我一家，如果那样，若你的 LEDE+openclash很稳定，麻烦回一下程序版本与内核版本，我试着再重编一版。
Screenshots
No response

R4S，LEDE R23.4.1，5.15.104，OC版本v0.45.108-beta，fake-ip tun模式，meta内核，ipv6代理，绕过大陆白名单模式，原生机场+第三方订阅
稳得1B

R4S，LEDE R23.4.1，5.15.104，OC版本v0.45.108-beta，fake-ip tun模式，meta内核，ipv6代理，绕过大陆白名单模式，原生机场+第三方订阅
稳得1B

给个下载地址好吗，谢谢

R4S，LEDE R23.4.1，5.15.104，OC版本v0.45.108-beta，fake-ip tun模式，meta内核，ipv6代理，绕过大陆白名单模式，原生机场+第三方订阅
稳得1B

给个下载地址好吗，谢谢

https://github.com/VIKINGYFY/OWRT-CI
我的云编译项目，每天自动编译，lede源和imm源，有需要的请点星收藏。enjoy~

R4S，LEDE R23.4.1，5.15.104，OC版本v0.45.108-beta，fake-ip tun模式，meta内核，ipv6代理，绕过大陆白名单模式，原生机场+第三方订阅
稳得1B

给个下载地址好吗，谢谢

https://github.com/VIKINGYFY/OWRT-CI
我的云编译项目，每天自动编译，lede源和imm源，有需要的请点星收藏。enjoy~

用用看，感谢

authors: VIKINGYFY gj0518 sunyink

repo: vernesong/OpenClash


text:
You must be joking

In M2, when you run a query via conn.query, you get each row contained within a JsonObject. This is reasonable, since then you can look up the results by column name. E.g if you intend to fill up a dto, you can do stuff like
user.setEmail( result.getString("email") );
However I just upgraded to snapshot, and I see that this has been changed to a ResultSet (which is fine), but the resultSet has a getResult method, which returns a List<JsonArray> rather than a List<JsonObject>
I'm hoping that this was a mistake, and / or a List<JsonObject> method is soon to be added, or the snapshot build I have is old somehow. Because with a json array,  instead of doing result.getString(colName), I have to look up the column name by the numeric index, and do result.get( index).
That's what PHP had back in 2002 or so when you had to do mysql_num_rows() and look up the column by index. We're not going back to that, are we?
I'm ranting a bit because I just had to write a utility method for converting JsonArrays into JsonObjects, so that my existing code will continue to work. However the performance on that is going to be shit if that has to be done for each row in production.
Thanks.

The trouble with the JsonObject approach is each row contains the field names. That means if you have a 10000 rows you have all the field names duplicated in memory 10000 times. This can make the memory footprint of the resultset a lot bigger and it means it will take a longer to serialize over the wire.
Maybe we can provide convenience methods on the ResultSet to retrieve the values by column name?

I'd say that because this is the jdbc library, we should stick to jdbc conventions for this, which is to provide a way to get values by column name.
I can't think of many use cases where you'd really be loading 10,000 rows into memory. Most of the time you'd be paginating to load 10-100 rows at a time.
Its far more common that you'd want to look up columns by name (and would incur the performance penalty of looking it up by the index for each time), than the edge case of loading 10,000 rows at a time.

Tim,
There's also another solution, if you do what JDBC does, i.e:
while (resultSet.hasRows()
{
     JsonObject row = resultSet.next();
}
Then only one JsonObject at a time would be created, and there would be no memory issues.
But actually, even that isn't necessary, since you can just intern the key names, in which case the same string instances would be used for all 10,000 rows rather than a new instance being made for each row.
String intern support is very good in JDK 8, and that will completely resolve the performance concerns without having to give up the convenience of looking up values by the column name.
There's really no need to go back to the bad old days of arrays! :)
More info: http://java-performance.info/string-intern-in-java-6-7-8/

I've added a method getRows() to return rows as Json object instances.
BTW, this GitHub issue is in the wrong repo - should be in vertx-sql-common :)

source: gharchive/issue

authors: aliakhtar purplefox

license_type: permissive

license_source: github-api


text:
documentation, cdt

Hello,
There is an error in cdt documentation. In the documentation, parameter "columns" is mandatory, but it is optional.

Regards,
Alexandre

Thanks for reporting this, the doc will be soon updated.

authors: lepelletieralexandre oualib

repo: vertica/VerticaPy


text:
Add .envrc to auto-source activation for vargo

This PR adds auto-activation of vargo when you enter the source directory (along with some documentation about this).
Additionally, it fixes up the activation script to prevent PATH from being updated if vargo build fails, to prevent polluting it.
Also reminder @utaal to test this on fish to make sure we don't accidentally break things; I didn't see it do anything bad in fish on my setup, but since I am not really a fish user, I don't know how people normally have it configured.

I briefly tested this on fish (which is my main shell) and it seems to work. direnv always runs the script in bash and just exports the resulting environment variables in a shell-specific way, which helps.
It is a bit verbose because every time it activates it prints the following:
direnv: loading ~/code/sw/verus/source/.envrc
building vargo
    Finished release [optimized] target(s) in 0.06s
direnv: export ~PATH ~XPC_SERVICE_NAME

but I don't think this is a big problem if you're using direnv.

Thanks folks; updated the docs, and glad to know that this Just Works^TM with fish too :)
As far as it printing output: I think this is acceptable for direnv users (they expect prints to happen whenever going into and out of directories that impact env vars). Yes we are printing a bit more than just the "PATH changed", but I think it is useful for us to not suppress the fact that a (re)build is happening.

source: gharchive/pull-request

authors: jaybosamiya tchajed

repo: verus-lang/verus

license: MIT


text:
[Bug] In MySQL-CDC, No duplicated rows with earliest-offset mode (sink to iceberg)

Search before asking

[X] I searched in the issues and found nothing similar.

Flink version
1.17.0
Flink CDC version
2.3.0
Database and its version
Source: MySQL 8.0.31
Sink: Iceberg 1.2.1
Minimal reproduce step

insert one row to mysql (id = 5)
wait checkpointing
check whether an inserted row (id=5) is applied to target(iceberg)
cancel and restart mysql-cdc job with earliest-offset
check whether a row (id=5) sent again in flink UI .

What did you expect to see?
There are two row(id = 5) in iceberg.
(because, it send a row (id=5) twice)
What did you see instead?
There is only on row, no duplicated (id=5)

Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

I checked the contents below

flink checkpoint file
MySQL binlog name and position

Then I found that checkpoint file has a binlog file name and position,
and it is same with mysql latest binlog file name and size(position)

flink checkpoint

mysql

So I'm guessing that flink mysql-cdc source all binlog but, only those after the flink checkpoint are reflected.
If anyone has more detailed information about this, I would really appreciate it if you could reply.

repo: ververica/flink-cdc-connectors


text:
oracle 19c版本的float数据类型对应flink sql的float失败

Describe the bug
A clear and concise description of what the bug is.
Environment :

Flink version :  1.13.3
Flink CDC version: 2.1.0
Database and version: oracle 19c

To Reproduce
Steps to reproduce the behavior:

Thes test data :
The test code :
The error :

[ERROR] Could not execute SQL statement. Reason:
java.lang.NumberFormatException: For input string: "Struct{scale=0,value=[B@7696705f}"
Additional Description
If applicable, add screenshots to help explain your problem.
把flink sql里的类型改为string，能正常select，但是该2字段会显示为Struct{scale=0,value=[B@7696705f}，改为其他数据类型都会失败。

该字段只有一个值：0

该字段只有一个值：0

修正：该字段只有0和null两个值

https://github.com/ververica/flink-cdc-connectors/pull/560

@leonardBang PR:https://github.com/ververica/flink-cdc-connectors/pull/560 have merged.

authors: GOODBOY008 HQLboy ashulin


text:
[Oracle] Fix Oracle CDC fetch two different db name for the same table

Fix Oracle CDC fetch two different db name for the same table

Fixes #2087

Motivation
If the database name configured for Oracle CDC in Flink SQL is lowercase, such as the following example ('database-name' = 'xe'),
CREATE TABLE products (
     ID INT NOT NULL,
     NAME STRING,
     DESCRIPTION STRING,
     WEIGHT DECIMAL(10, 3),
     PRIMARY KEY(id) NOT ENFORCED
     ) WITH (
     'connector' = 'oracle-cdc',
     'hostname' = 'localhost',
     'port' = '1521',
     'username' = 'flinkuser',
     'password' = 'flinkpw',
     'database-name' = 'xe',
     'schema-name' = 'FLINKUSER',
     'table-name' = 'TEST_03');

the following problems will occur:

For the same table (TEST_03)，the snapshot phase  will use the lowercase database name  (xe.FLINKUSER.TEST_03 ), and the incremental phase will use the uppercase database name (XE.FLINKUSER.TEST_03 ).
For the same table (TEST_03 ), after being captured in the snapshot phase, it will be captured again in the incremental phase because their database names are inconsistent.

In OracleConnectorConfig, the database name in Flink SQL is converted to uppercase, but the database name used in the snapshot phase is directly taken from Flink SQL. Therefore, when constructing the tableId, the database name in Flink SQL also needs to be converted to uppercase.

Modifications
When constructing the tableId, the database name in Flink SQL needs to be converted to uppercase.

@e-mhui Thanks for the contribution.
Please rebase the master branch. And the debezium version has been update to 1.9.7.Final. Could you help to check whether the error still exists?
Besides these, I think maybe we should use database name in upper case at the beginning. For example, in the constructor of the Source.

@e-mhui Thanks for the contribution. Please rebase the master branch. And the debezium version has been update to 1.9.7.Final. Could you help to check whether the error still exists?
Besides these, I think maybe we should use database name in upper case at the beginning. For example, in the constructor of the Source.

@ruanhang1993 Thanks you reply, it has rebased the mater branch. The errror still exist in 2.4 and master branch. pls review it again.
In the incremental phase, debezium has already capitalized the database name, so I believe it is necessary to also do so in the snapshot phase.

@ruanhang1993  pls review it.


text:
Support asynchronous import of multiple tasks

Support asynchronous import of multiple tasks 多任务异步导入

support in #117

repo: vesoft-inc/nebula-studio


text:
Add a MultiRangeItem for efficient evaluation of multiple OR-ed range items on a common field (or two)

I'm always frustrated when it takes too long to evaluate an OrItem with lots of RangeItems inside.
This is typically the case when using the result of one query to prune the result set for a second query, to be intersected with the first. When the first query has 100k hits, each resulting in a range to be added o the second query, this becomes expensive:

The resulting query tree has hundreds of thousands of nodes, and serialisation and processing of this in backend is slow.
Doing (on average half of) 100k ORs in sequence, when evaluating the query in the backend, is very costly.

I would like a new MultiRangeItem to be added to the Java search API. This item would restrict the contained ranges to all be against the same field, or possibly a pair of fields (start in one field, end in another, when documents contain intervals, not just points). This, again, would allow for a much more compact representation of the query, and would allow the backend to process it more efficiently. This addresses the first item above.
Additionally, an implementation of this could prune overlapping interval, as well as shape the sorted set of ranges into a search tree; this allows query evaluation in the backend to evaluate only the relevant branches and ranges for each document, in contrast to when the ranges are arranged in a flat, long list.
Finally, it would also allow dedicated code to run in the backend, if we add this at a later time.

I think if we do multirange query item we should have a range field type which specifies start and end? Maybe you could list a few concrete examples @jonmv ?

boolean closed = true;
new MultiRangeItem("my_range", closed).addRange(3, 5).addRange(4, 8)... // range type if we add this
new MultiRangeItem("my_start", "my_end", ! closed).addRange(1, 2)... // pair of fields
new MultiRangeItem("my_point", closed).addRange(8, 9)... // single field
new MultiPointItem("my_point).addPoint(3)... // probably not needed, as WeightedSetItem works for this?

To summarise today's discussion:

We would like a dedicated Java API, like the one suggested here, which allows more assumptions on the query term:
we can collapse overlapping intervals;
we can choose a more compact representation; and
we will also be able to build a reverse index in the backend, at search time, for lookup of document terms, making this an efficient filter term.

These are three separate tasks that should be addressed in this order.
NB: The fact that the query tree built in Java in experiments actually is more efficient than a flat OR list is at the mercy of the query evaluation strategy gods, who, in turn, rely on std::sort.

Pondered a bit. The reverse index, in its simplest form, can just be two sorted arrays A, B, containing the range endpoints. Looking up whether a document range (x, y) intersects any range in (A, B) can be done by doing a binary search for a in B and for b in A, and comparing the indices. Specifically, find the smallest j s.t. a ≤ B[j] and the largest i s.t. b ≥ A[i], and it's a match iff i ≥ j. Use strict inequalities for open ranges.
A = [1, 5, 9]
B = [3, 7, 11]
// closed ranges
a, b = 6, 6 ==> i = 1, j = 1 ==> match // (a, b) contained in query range
a, b = 4, 4 ==> i = 0, j = 1 ==> miss   // no intersection
a, b = 4, 8 ==> i = 1, j = 1 ==> match // (a, b) contains query range
a, b = 4, 6 ==> i = 1, j = 1 ==> match // (a, b) overlaps with query range
a, b = 5, 5 ==> i = 1, j = 1 ==> match // (a, b) touches a query range
// open range
a, b = 5, 5 ==> i = 0, j = 1 ==> miss // (a, b) touches a query range

I suppose it's more cache friendly to store A and B interleaved? This also makes early termination easy, if the two searches diverge. This is possibly the serialisation format we want as well? What do you think, @havardpe?

MultiRangeItem is too special.
We want a MultiTermItem where all term nodes are of the same type.
I also think that we should add an operation type to it,  OR/AND.
Serialisation format should be simple and extendable.
num_terms, term_type, operation_type,[terms]

We need something more than that to express ranges in the query against ranges in the document in a clean way. Either a new field type, or range items that specify a pair of fields.

Clarification: the proposed API is OK, but serialisation should be more general.

So the serialisation format needs to hold

operation type (AND, OR for now)
number of terms (positive integer)
term blueprint for translating each following term to something complete, e.g., type: ranges, from: <index name>, to: <index name>, start_limit: inclusive, end_limit: exclusive, and then ranges indicates a sub-routine that parses each following term as a pair of numbers—one for each given index.
the actual list of terms, e.g., 1 2 3 4 5 6 for three ranges terms.

That is, we want more than just the term type; we should also put anything common to all contained terms up on top.
I'm not sure what other types of terms we would care about—perhaps weightedset could use this format as well? Multiple words?

authors: baldersheim jobergum jonmv

repo: vespa-engine/vespa


text:
Tweak Weights Empties Channel

I hadn't tried it before 0.65, but on this version when I go to Tweak Weights and change the weight of a show I've added to a channel, then click Apply, it removes all programming from the schedule for that channel and says "No Programs Are Currently Scheduled".

@keithdok Using Version 0.0.67, try again to reproduce the issue.  If repeatable, provide steps to reproduce.  Otherwise, let us know if it is resolved.

Didn't get more reports of this for 18 days and I used tweak weights in multiple occasions. If you discover a way to make it reproduceable, please post it again in another issue with a description of the steps to reproduce it. Closing it for now.

authors: MoRBiD-MaNGLeR keithdok vexorian

repo: vexorian/dizquetv

license: Zlib


text:
Alphabetized free-courses-en.md

Simple clean up and alphabetization.

Many thanks!

authors: nafoster vhf

repo: vhf/free-programming-books


text:
[Frontend] Add the e2e_latency in vllm/vllm/entrypoints/api_server.py and plot CDF

Add e2e_latency record function and plot it in the new folder /onboarding_task, @lrq619 please check the code.
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Great job, your hands-on session is done, I will close this PR. Thanks for your effort, Siyu!
Okay, thanks!

repo: vhive-serverless/vllm


text:
chore(main): release 1.6.0

:robot: I have created a release beep boop
1.6.0 (2024-10-17)
🚀 Features

add Ubuntu Plucky Puffin 25.04 (bb2cecd)

🧰 Testing

save json files for further investigation (8318669)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/vicamo/actions-library/releases/tag/v1.6.0 :sunflower:

repo: vicamo/actions-library


text:
Incomplete documentation for evidence

I would like to do the following, which is one step of the EM algorithm:

set up a factor graph corresponding to a simple Bayesian network (I've got this far)
specify evidence in the form of specified outcomes or marginal distributions for certain nodes
perform belief propagation, get the resulting factors and use them to construct a new Bayesian network

I'm currently stuck at the second bullet point. If I search the docs for "evidence" I find pgmax.fg.graph.Evidence and pgmax.fg.graph.update_evidence, but the documentation for these is very incomplete and doesn't specify the format in which the inputs should be provided or the procedure for using them.
The blog post doesn't use these but something else - it uses an argument evidence_updates to run_bp, but this is not mentioned in the documentation. I can't really understand what this argument is doing in the example, but I suspect it's not what I'm looking for.
So I'm a bit stuck on understanding the basic usage, and I'm wondering if I could either get a hint about it, and/or whether the documentation could be updated to make it a bit clearer.

This is definitely another part of the documentation we need to improve.
You can update evidence using intuitive assignment syntax. https://github.com/vicariousinc/PGMax/blob/f7f3e3fe7fbb3a3c7582b7093c6ecd56eb04963a/examples/ising_model.py#L96 Here is an example for an Ising model. You index the evidence with variable names (tuples of the type (group_name, variable_name_in_group)) and do assignment. If you are working with variable groups (e.g. an NDVariableArray), you can also use intuitive assignment syntax with arrays (e.g. https://github.com/vicariousinc/PGMax/blob/f7f3e3fe7fbb3a3c7582b7093c6ecd56eb04963a/examples/ising_model.py#L103).
The evidence_updates argument to run_bp updates evidence on the fly for the given belief propagation run. You can use the elements in this dictionary in the above assignment syntax to achieve the same kind of evidence updates.
Some additional comments for this two different ways of doing evidence updates:

Using the assignment syntax the updates are persistent. When you do run_bp later you will always work with the updated evidence.
Using evidence_updates the updates are not persistent. It only updates the evidence for that particular run_bp run. But by structuring evidence_updates as a dictionary of jnp arrays and having run_bp as pure python functions, we obtain the ability to get gradients w.r.t. the evidence updates using jax.grad. This is the main motivation for organizing things this way.

And you are more than welcome to contribute an example with directed models (since you obviously are working on one). Please refer to the developer installation instructions and contribution guide, and feel free to open a PR when it's ready!

authors: StannisZhou nathanielvirgo

repo: vicariousinc/PGMax

license: mit

license_source: bigquery


text:
🛑 http_inspect is down

In 3410c9e, http_inspect (https://ea5b-184-22-193-217.ngrok.io) was down:

HTTP code: 404
Response time: 269 ms

Resolved: http_inspect is back up in 73841a1.

repo: vichaos/upptime


text:
Help maintaining this theme

Hey @vickylai,
I would like to help you maintaining this theme. It looks like you don't have so much time at the moment and could have some assistance.
Let me know what you think.

Added as collaborator! Thank you!

authors: Hanzei vickylai

repo: vickylai/hugo-theme-introduction


text:
Check if we can work better with deep-translator which already supports multiple translator engines

Explanation
https://github.com/nidhaloff/deep-translator is an open source library with a similar idea to this library, which works on your python projects locally so as through CLI and as API, I propose to check if we can work using this tool instead of integrate manually various translator engines in this library, using deep translator API.
This could solve this issue

We'll need something like a controller which will be responsible of send the API requests, in order to make this part of the code easy to change in a future if is needed.

About use, we will need to expand the configuration API in order to be able to define the priority of endpoint to use so as endpoint we don't want to use and API KEYS of endpoints that needs them

Decided better not use deep-translator for this, I think is better integrate part by part each tool in order to have more security and control about the information flow


text:
Comparison with YOLO on the same dataset

Hi Victor and others,
Has anyone trained the recent yolo(v1 v2 or v3) on the ego hands dataset and can probile provide a absic comparison in terms of speed and accuracy?
thanks in advanace
shreeraman

Hi @srp-31 ,
There is a paper I reference in the blog post where researchers have done a comparison of ssd and yolo on a basic dataset for the object detection task.
http://arxiv.org/abs/1611.10012
[1] J. Huang, V. Rathod, C. Sun, M. Zhu, A. Korattikara, A. Fathi, I. Fischer, Z. Wojna, Y. Song, S. Guadarrama, and K. Murphy, “Speed/accuracy trade-offs for modern convolutional object detectors,” in IEEE CVPR, 2017, pp. 1–21.

Hi Victor
Thank you for the speedy reply. I was looking for it all over and somehow missed it.
thanks a lot.

Hi Victor
Thank you for the speedy reply. I was looking for it all over and somehow missed it.
I closed it thinking it might have a comparison with yolo. But unfortunately this paper does not deal with yolo.
There is however already some work in thsi regards:-
http://cs231n.stanford.edu/reports/2017/posters/225.pdf
I am going to try and get in touch with them. I will update on the issue about my progress.
thanks a lot.
shreeraman

Hi srp-31, I am also training a yolo model by using this dataset. Have you got success in it ?

Hi ghffarpk,
I suspended training yolo since the resutls form victor's code meets my requirement. I will update you if I train yolo for the dataset.
goodluck.

authors: ghffarpk srp-31 victordibia

repo: victordibia/handtracking


text:
Filter Email Notification Service To Cc Bcc with Org Wide Addresses

/**

@ClassName    : NotificationService

@JIRATicket   :

@CreatedOn    : 26/07/2024

@CreatedBy    : Izzie

@ModifiedBy   :

Description	: This class will be invoked from flows to send emails
*/
public class NotificationService {
public class InputWrapper {
@InvocableVariable(label='Related Record Id' required=true) //Related Record Id
public String recordID;
@InvocableVariable(label='Email Template Id' required=true) //Email Template Id
public String emailTemplateID;
@InvocableVariable(label='Contact Id' required=true) //record to send email to.
public String contactID;
@InvocableVariable(label='Sender Email Address' required=false) //Sender Email Address
public String sender;
@InvocableVariable(label='listOfTo' required=false) //ToAddress
public List listOfTo;
@InvocableVariable(label='listOfCC' required=false) //CC address
public List listOfCC;
@InvocableVariable(label='listOfBCC' required=false) //BCC Address
public List listOfBCC;
@InvocableVariable(label='treatTargetObjectAsRecipient' required=false) //this will help in bypassing the logic if no contact
public Boolean treatTargetObjectAsRecipient = true;
}
public static List adjustNullElements(List aStringList) {
if (aStringList.size() > 0) {
set aStringSet = new Set(aStringList);
aStringSet.remove('');
aStringSet.remove(null);
aStringList = new List(aStringSet);
}
return aStringList;
}
@invocableMethod(label='SendEmailViaApex')
public static void sendMail(List passedData) {
InputWrapper dw = passedData[0];//first record
Messaging.SingleEmailMessage mailToSend = new Messaging.SingleEmailMessage();// object SingleEmailMessage
mailToSend.setTargetObjectId(dw.contactID);
mailToSend.setWhatId(dw.recordID);
mailToSend.setTemplateID(dw.emailTemplateID);
if (dw.listOfTo != null) {
dw.listOfTo = adjustNullElements(dw.listOfTo);
if (dw.listOfTo.size() > 0 ) {
mailToSend.setToAddresses(dw.listOfTo);
}
}
if (dw.listOfCC != null) {
dw.listOfCC = adjustNullElements(dw.listOfCC);
if (dw.listOfCC.size() > 0) {
mailToSend.setCcAddresses(dw.listOfCC);
}
}
if (dw.listOfBCC != null) {
dw.listOfBCC = adjustNullElements(dw.listOfBCC);
if (dw.listOfBCC.size() > 0) {
mailToSend.setBccAddresses(dw.listOfBCC);
}
}
if (!dw.treatTargetObjectAsRecipient) {
mailToSend.setTreatTargetObjectAsRecipient(dw.treatTargetObjectAsRecipient);
}
if (dw.sender != null) {
OrgWideEmailAddress[] owea = [SELECT Id FROM OrgWideEmailAddress WHERE Address = :dw.sender];
if (owea.size() > 0) {
mailToSend.setOrgWideEmailAddressId(owea.get(0).Id);
}
}
if(!Test.isRunningTest()) {
List<Messaging.SendEmailResult> sendResults = Messaging.sendEmail(new List<Messaging.Email>{ mailToSend });
}
}
}

/**

@ClassName    : NotificationService

@JIRATicket   :

@CreatedOn    : 26/07/2024

@CreatedBy    : Izzie

@ModifiedBy   :

Description	: This class will be invoked from flows to send emails
*/
public class NotificationService {
public class InputWrapper {
@InvocableVariable(label='Related Record Id' required=true) //Related Record Id
public String recordID;
@InvocableVariable(label='Email Template Id' required=true) //Email Template Id
public String emailTemplateID;
@InvocableVariable(label='Contact Id' required=true) //record to send email to.
public String contactID;
@InvocableVariable(label='Sender Email Address' required=false) //Sender Email Address
public String sender;
@InvocableVariable(label='listOfTo' required=false) //ToAddress
public List listOfTo;
@InvocableVariable(label='listOfCC' required=false) //CC address
public List listOfCC;
@InvocableVariable(label='listOfBCC' required=false) //BCC Address
public List listOfBCC;
@InvocableVariable(label='treatTargetObjectAsRecipient' required=false) //this will help in bypassing the logic if no contact
public Boolean treatTargetObjectAsRecipient = true;
}
public static List adjustNullElements(List aStringList) {
if (aStringList.size() > 0) {
set aStringSet = new Set(aStringList);
aStringSet.remove('');
aStringSet.remove(null);
aStringList = new List(aStringSet);
}
return aStringList;
}
public static List sanitizeAddresses(List inputList, Set orgWideEmailSet) {
List sanitizedListOfAddresses = new List();
for (String email : inputList) {
if (!orgWideEmailSet.contains(email.toLowerCase())) {
sanitizedListOfAddresses.add(email); // Add to the sanitized list if it's not an Org-Wide Email
}
}
return sanitizedListOfAddresses;
}
@invocableMethod(label='SendEmailViaApex')
public static void sendMail(List passedData) {
List orgWideEmails = [SELECT Address FROM OrgWideEmailAddress];
Set orgWideEmailSet = new Set();
for (OrgWideEmailAddress owe : orgWideEmails) {
orgWideEmailSet.add(owe.Address.toLowerCase()); // Convert to lowercase for case-insensitive comparison
}
InputWrapper dw = passedData[0]; //first record
Messaging.SingleEmailMessage mailToSend = new Messaging.SingleEmailMessage(); // object SingleEmailMessage
mailToSend.setTargetObjectId(dw.contactID);
mailToSend.setWhatId(dw.recordID);
mailToSend.setTemplateID(dw.emailTemplateID);
if (dw.listOfTo != null) {
dw.listOfTo = adjustNullElements(dw.listOfTo);
dw.listOfTo = sanitizeAddresses(dw.listOfTo, orgWideEmailSet);
     if (dw.listOfTo.size() > 0) {
         mailToSend.setToAddresses(dw.listOfTo);
     }
 }
 if (dw.listOfCC != null) {
     dw.listOfCC = adjustNullElements(dw.listOfCC);
     dw.listOfCC = sanitizeAddresses(dw.listOfCC, orgWideEmailSet);
     if (dw.listOfCC.size() > 0) {
         mailToSend.setCcAddresses(dw.listOfCC);
     }
 }
 if (dw.listOfBCC != null) {
     dw.listOfBCC = adjustNullElements(dw.listOfBCC);
     dw.listOfBCC = sanitizeAddresses(dw.listOfBCC, orgWideEmailSet);
     if (dw.listOfBCC.size() > 0) {
         mailToSend.setBccAddresses(dw.listOfBCC);
     }
 }
 if (!dw.treatTargetObjectAsRecipient) {
     mailToSend.setTreatTargetObjectAsRecipient(dw.treatTargetObjectAsRecipient);
 }
 if (dw.sender != null) {
     OrgWideEmailAddress[] owea = [SELECT Id FROM OrgWideEmailAddress WHERE Address = :dw.sender];
     if (owea.size() > 0) {
         mailToSend.setOrgWideEmailAddressId(owea.get(0).Id);
     }
 }
 if (!Test.isRunningTest()) {
     List<Messaging.SendEmailResult> sendResults = Messaging.sendEmail(new List<Messaging.Email>{ mailToSend });
 }

}
}

Updated Code added above


text:
Route Not defined

When I put the code in Web.php show this error,

I do the publish and is not working yet
• App\Http\Controllers\Victorybiz\LaravelCryptoPaymentGateway\src\Http\Controllers\CryptoPaymentController was not found: Controller class App\Http\Controllers\Victorybiz\LaravelCryptoPaymentGateway\src\Http\Controllers\CryptoPaymentController for one of your routes was not found. Are you sure this controller exists and is imported correctly?
I neeed publish the files manually?

Sorry, was my bad. Laravel 8 is with route namespace by default, so you need put in null if you make a upgrade from other version

Sorry, was my bad. Laravel 8 is with route namespace by default, so you need put in null if you make a upgrade from other version

I got stuck here, but did not understand what you meant by ' so you need put in null'. With some research I realized that in App/Providers/RouteServiceProvider.php , I had to change protected $namespace = 'App\Http\Controllers'; to protected $namespace = null;
That solved it for me. Thank you


text:
Can Videogular play VR video on iOs (without trigger iOs native player)

I am looking into way to play vr video using Google Cardboard OR have a video player that function like the 360 YouTube video (people can move around the scene). This will need to disable the Native iOs player and use Chrome browser HTML players.. Not sure if anyone use videogular to do any VR video and 360 video players. Any suggestion will be greatly appreciated.

Videogular doesn't have support, in Clappr you have an experimental plugin tho.
https://github.com/thiagopnts/video-360

repo: videogular/videogular


text:
Clean up Readme grammar and phrasing

Closes #189 and addresses some confusing phrasing in the Readme.

:+1: awesome

Would be nice to have an example of implementation of the post_transition and pre_transition.

Sorry for the delay. I've been working on other projects.
Than you for PR!

authors: Sispheor kmmbvnr radius

repo: viewflow/django-fsm


text:
[Admin] Current page referencing to the object id instead of the current page.

[1] - http://localhost:8000/admin/locations/location/1
[2] - http://localhost:8000/admin/locations/location/?p=1

Django 1.9

i don't get what you mean

I got it.
https://github.com/viewflow/django-material/blob/master/material/admin/templatetags/material_admin.py#L181
        return format_html('
{0}
 ',
                           i+1,
                           cl.get_query_string({PAGE_VAR: i}))

So for current page it will set {0} to the current_page_number+1  so it would be relative url to the object with id "current_page_number+1".
You need to change:
        return format_html('
{0}
 ',
                           i+1,
                           cl.get_query_string({PAGE_VAR: i}))

to the /?p={0}, actually it's not as easy there could be other parameters in url.

can try to do pull request if you want

Yep, PRs are welcome.
You can take a look how this functionality implemented in django admin template tags

ok

done

fixed in 9bf19db06f15733fcdb6f3ffc6b0037fce5bb60e

authors: istinspring kmmbvnr

repo: viewflow/django-material


text:
RFC: Revise React Router example with some future plans

React Router v4 has a more component based API. It also makes it easier to work directly with history. This PR is an exploration of what future Microcosm apps might look like.
Highlights
Flow
I've added FlowTypes. I want first class support for them. I still have to figure some stuff out for the register() method, which is quite dynamic, but I'm happy so far.
Domains are responsible for CRUD
In the future, I would like domains to own management of their data concerns. They have their own actions. What we call actions now are more like controllers:
/**
 * @flow
 */
import uid from 'uid'
import Domain from './domain'

export type List = {
  id?: string,
  name: string
}

class Lists extends Domain {
  static create(params): List {
    return { id: uid(), ...params }
  }

  static destroy(id: string) {
    return id
  }

  register() {
    return {
      [Lists.create]: this.add,
      [Lists.destroy]: this.remove
    }
  }
}

export default Lists

Action based navigation
Effects can accept options. In this PR, I make a effect for routing. This lets us do navigation within actions:
export function addList(params) {
  return function*(repo) {
    let list = yield repo.push(Lists.create, params)

    yield repo.push(visit, `/lists/${list.id}`)
  }
}

Models
I want to reduce the logic inside of Presenters. Increasing the responsibility of actions is part of that, but I also am interested in how Presenters can compose model bindings together, pulling out a lot of that logic into discrete, easy to test, components:
export class ListWithCounts implements Model {
  call(_presenter, state) {
    const { lists, items } = state

    return lists.map(function(list) {
      let count = items.filter(i => i.list === list.id).length

      return set(list, 'count', count)
    })
  }
}

class ListIndex extends Presenter {
  getModel() {
    return {
      lists: new ListsWithCounts()
    }
  }

  render() {
    const { lists } = this.model
    // ...
  }
}

What's next
This is a work in progress. I don't expect this to merge. I would like to make a few improvements:

Add more sugar for sequential actions (#346)
Add more sugar for models. Could they use Observables? Could we use the Formula concept we've internally applied to a recent project?

Codecov Report

Merging #348 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #348   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          24     24
  Lines         860    860
=====================================
  Hits          860    860

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 297a7ce...c977a4d. Read the comment docs.

authors: codecov-io nhunzaker

repo: vigetlabs/microcosm


text:
Add Support for Has-and-Belongs-to-Many Associations

This PR addresses and fixes #19, which was a question as to how Sprig Reap works with has_and_belongs_to_many (HABTM) associations.  It didn't, but now it does.
HABTM is some hackery in general, so there's definitely some trickiness/wonkiness to this PR -- mainly around resolving circular dependencies when there are bi-directional HABTM between two models.
The Sprig::Reap::Record.to_hash will generate the appropriate hash structure so that it'll generate Sprig-compatible YAML per Sprig's documentation on HABTM.

:+1:

Very nice! :+1:

Thanks guys!

authors: efatsi h0tl33t mackermedia

repo: vigetlabs/sprig-reap


text:
Ask for add rule

https://eslint.org/docs/rules/curly

https://eslint.org/docs/latest/rules/sort-keys

repo: vigilock/eslint-config-consignity


text:
Update cats-effect to 3.3.10

Updates org.typelevel:cats-effect from 2.5.4 to 3.3.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.typelevel:{cats-effect,cats-effect-laws}:3.0.0

github:typelevel/cats-effect/v3_0_0?sha=v3.0.0

org.typelevel:{cats-effect,cats-effect-laws}:3.3.0 (created no change)

github:typelevel/cats-effect/v3_3_0?sha=series/3.x

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect" } ]

labels: library-update, early-semver-major, semver-spec-major, scalafix-migrations, commit-count:n:2

Superseded by #376.

repo: vigoo/prox


text:
Update cats-core to 2.5.0

Updates org.typelevel:cats-core from 2.4.2 to 2.5.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-core" } ]

labels: library-update, semver-minor

Codecov Report

Merging #98 (6af5755) into master (a3c5cd3) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 6af5755 differs from pull request most recent head 6fc5b5c. Consider uploading reports for the commit 6fc5b5c to get more accurate results

@@            Coverage Diff            @@
##            master       #98   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           57        57
  Branches         2         2
=========================================
  Hits            57        57

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 a3c5cd3...6fc5b5c. Read the comment docs.

authors: codecov-io scala-steward

repo: vigoo/simpp


text:
Update aws-core, http-client-spi, ... to 2.16.29

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.16.20 to 2.16.29.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #296.

repo: vigoo/zio-aws


text:
vikas-env-pullrequest

done pull request

merging pull request

final

done


text:
checkbox et non bouton radio, conformément à ce qui est permis sur le…

… site officiel. + corr. typos.
en plus d'autoriser plusieurs choix conformément à la page officielle, correction des typos de l'État (espaces insécables manquantes avant les points-virgules) et accent de "Générer".
Après faudra s'attaquer au fait que le bouton "Effacer" a le même résultat que le Reset.

Effectivement, pour l'instant le texte stipule "cochez la case"

ATTENTION : il semblerait que l'attestation numérique n'est plus acceptée !!
https://www.numerama.com/tech/612262-attestation-de-deplacement-sur-smartphone-le-gouvernement-retropedale-seul-le-papier-est-valable.html

Verifié, il est interdit de cocher plusieurs cases sur la meme attestation

authors: Madmarsu vikbez xyloweb

repo: vikbez/covid-sortie


text:
vike-react-query throws error in onRenderHtml

Description
Describe the bug
Starting a new project using vike-react-query throws an error after the first page request
To Reproduce
Steps to reproduce the behavior, run the following commands in order:
start a new vike project using vike-react, tailwind, honoo and vike-react-query, setup everything as the docs mention
Expected behavior
Run dev mode without any errors
Screenshots

Additional context
Using macOS Ventura 13.6.6 and the following related libs:
"react": "^18.3.1",
"@hono/node-server": "^1.12.0",
"hono": "^4.4.11",
"@vitejs/plugin-react": "^4.3.1",
"vike": "^0.4.178",
"vike-cloudflare": "^0.0.4",
"vike-react": "^0.4.16",
"vike-react-query": "^0.1.0",
"vite": "^5.3.3",

Can you publish a reproduction?

How did you resolve your #1729 issue btw.?

Can you publish a reproduction?

I could reproduce it on stackblitz using this run command:
pnpm create @batijs/app --react --tailwindcss --hono --cloudflare --prettier
than pnpm add @tanstack/react-query vike-react-query
than change the pages/+config.ts to include vike-react-query plugin on extends prop
export default {
	Head,
	title: 'My Vike App',
	extends: [vikeReact, vikeReactQuery],
	passToClient: ['routeParams'],
} satisfies Config

Make sure to set stream to web.
Closing in favor of https://github.com/batijs/bati/discussions/303.

authors: brillout jordyalcides

repo: vikejs/vike-react


text:
Added special token

I added a special token to have to good highlight.

Thanks for your contribution.  Is "special token" what those strings are called in the docs?  I'd like to make sure they match the docs.

See descriptions:
FILE
A special token that returns the name of the file in which it occurs.
LINE
A special token that compiles to the current line number.
PACKAGE
A special token that returns the name of the package in which it occurs.
SUB
A special token that returns a reference to the current subroutine, or undef outside of a subroutine.

So it is.  Thanks for checking.
I think it makes more sense to do this with syn keyword rather than syn match.  I think it'll be faster, too.  For instance, see how perlTodo is done.
Can you please try it that way and see if it works that way, too?  If so, update your branch and then I can merge.

I think better to keep new match, see:
https://perldoc.perl.org/5.30.0/perlfunc.html#Keywords-related-to-the-control-flow-of-your-Perl-program

Forget what I said about using syn keyword.  We have to use syn match, as discussed in #277.

Please optimize the regex a bit, so that instead of
"\<\%(__FILE__\|__LINE__\|__PACKAGE__\|__SUB__\)\>"

it's
"\<\%__(FILE\|LINE\|PACKAGE\|SUB\)__\>"

Sure, we can add it.  Right now the tests seem to fail, though.

I can't see the log, Travis showed me 'There was an error while trying to fetch the log.'

repo: vim-perl/vim-perl

license: Vim


text:
Improve POD section motion mappings

Set b:did_ftplugin
Add operator-mode section mappings

Please say more about what this is doing. It looks like it's removing the cut & paste repeated code and building the commands programatically. Anything else?

It removes the mappings from select mode as printable characters, like ]], are expected to end that mode.
It also adds the section mappings to operator mode do something like d]] works to delete until the next section.

authors: dkearns petdance


text:
win_execute should(?) update popup properties (scrollbar)

Steps to reproduce

vim -Nu NONE
Run following script:

vim9script

hi PmenuThumb ctermbg=red guibg=red

var winid = popup_create([], {
    maxheight: 3,
    minheight: 3,
    minwidth: 19,
    maxwidth: 19,
    scrollbar: true,
    wrap: 1,
    filter: (id, key) => {
        if key == "\<esc>"
            popup_close(id, -1)
        endif
        return true
    }
})

popup_settext(winid, [
    "hello world",
    "hello world (10)",
    "hello world",
    ])

win_execute(winid, "setl nu")

# workaround
# popup_move(winid, {})

var pos = popup_getpos(winid)

echow "Is there a scrollbar?" pos.scrollbar

Result:
Function popup_getpos() returns scrollbar: 0 even though popup window shows there is scrollbar.

Expected behaviour
Function popup_getpos() should return scrollbar: 1 if there is scrollbar.
As a workaround one can use popup_move(winid, {}) before calling popup_getpos to ensure scrollbar value is updated.
The use case is the alignment of 2 popup windows where one window could have a scrollbar and you need to adjust width to accommodate scrollbar width. In some cases popup_getpos returns 0 for a scrollbar even though it is there.

The issue as I can see it is in win_execute that might add setl number effectively changing available horizontal space for a text, wrapping some lines.
Version of Vim
9.1.202
Environment
debian wsl, bash, simple terminal
Logs and stack traces
No response

Adding popup_adjust_position() to f_popup_getpos fixes it, though not sure if this is correct approach.
    void
f_popup_getpos(typval_T *argvars, typval_T *rettv)
{
    dict_T	*dict;
    int		id;
    win_T	*wp;
    int		top_extra;
    int		left_extra;

    if (rettv_dict_alloc(rettv) == FAIL)
	return;

    if (in_vim9script() && check_for_number_arg(argvars, 0) == FAIL)
	return;

    id = (int)tv_get_number(argvars);
    wp = find_popup_win(id);
    if (wp == NULL)
	return;  // invalid {id}

    popup_adjust_position(wp);
    ...

repo: vim/vim


text:
Vim doesn't reflects colorscheme when it boot.

Happy Vimming, sir.
I have a problem that the acquired colorscheme isn't reflected on Vim at boot.
Profile of Vim and so on

OS : Debian GNU/Linux
Virtual Terminal : Urxvt (Daemonized)
Vim
I compiled Vim on an Japanese environment. So this is not original text.

$ vim --version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May  3 2017 13:37:11)
適用済パッチ(←mean “Patch”): 1-596
Compiled by <myfost>
Huge 版(←mean “Version”) without GUI.

What Happen
In $MYVIMRC (~/.vimrc), I wright only:
let skip_defaults_vim=0
syntax on
colorscheme molokai

molokai.vim (colorscheme file) is in ~/.vim/colors and when I type :echo g:colors_name in Vim, it returns “molokai.”
But, in this time, the appearance of Vim is default colorscheme, instead of molokai one.
And when I type :source ~/.vimrc and/or :colorscheme molokai, it fixed.
When I change ~/.vimrc to this;
syntax on
colorscheme molokai

nothing changes.
===
Please give me any solution.

I cannot reproduce the said problem.  Can you tell us what your vim returns with :echo &term?

Thank you for reply.
Vim says rxvt-unicode for :echo $TERM, but does not say anything for :echo $term.

Then, on your terminal, start up urxvt with
$ TERM=rxvt-unicode-256color urxvt

Next, on this newly opened terminal, do
$ vim -u NONE -c 'syntax on | colorscheme molokai'

Does this make a difference to you?

Thank you, sir. But there are no difference.
I tried typing;
$ vim -u NONE -c 'syntax on | colorscheme molokai'

but the splash string's colorscheme is default one.
I also typing;
$ vim -u NONE -c 'syntax on | colorscheme molokai' tmp.html

on terminal. File tmp.html is colored, but it's colorscheme isn't molokai but default one. Vim say “molokai” to :echo g:colors_name.

Strange.  What ':echo $TERM &term' returns after you just do `vim -u NONE -c 'syntax on | colorscheme molokai' ?

Vim says “rxvt-unicode rxvt-unicode.” ...what?!
Then I tried change value of $TERM “rxvt-unicode-256color” in different way. And succeeded.
Now I get colorscheme that based molokai!
Thank you very much and sorry for take your time.

Okay, now we just ruled out the possibility that, on urxvt, Vim selects the default color scheme in spite of it being told to use molokai at startup, and that, nevertheless, Vim can switch the color scheme from default to molokai if the mentioned $MYVIMRC is sourced again at runtime or if molokai is explicitly set with :colorscheme at runtime.
All those were due to a wrong $TERM value for the 256-color capable urxvt.  Will you close this issue yourself?

I really appreciate your teaching.
In this time, I set env in $MYVIMRC.

Will you close this issue yourself?
Yes, sir. I'll do it.


text:
Vim9: unable to add a number value to a nested dictionary

I want to add a number value to a nested dictionary but I keep getting E1012: Type mismatch; expected string but got number.
I assume it's because the nested dictionary's values' type is inferred to be string.  I can't find a way to declare a type of any, nor a way to bypass the inferred-type check.
Describe the bug
Source this script:
vim9script

# final foo = [
var foo: list<dict<any>> = [
        {
          a: "Cat",
          b: false,
          c: [
            {x: "Dog"},
          ]
        }
      ]

var counter = 0

for p in foo
  for q in p.c
    counter += 1
    q.counter = counter    # ← this is the line that generates the E1012 error
  endfor
endfor

Environment (please complete the following information):

Vim 8.2.2566
OS: macOS 10.14.6
Terminal: iTerm2

Not sure but this looks like a bug I noticed a long time ago, but didn't report yet (because I wasn't sure).
This snippet raises E1012:
vim9script
var d: list<dict<any>> = [{a: 0}]
for e in d
    e = {a: 0, b: ''}
endfor

E1012: Type mismatch; expected dict<number> but got dict<any>

But the same code doesn't raise any error when compiled:
vim9script
def Func()
    var d: list<dict<any>> = [{a: 0}]
    for e in d
        e = {a: 0, b: ''}
    endfor
enddef
Func()

no error

This seems inconsistent.
There is a sentence at :h vim9 (look for the pattern For loop) which says:

Generally, you should not change the list that is iterated over.  Make a copy
first if needed.

I wonder whether that's somehow relevant.

Make a copy first if needed.

This works:
- q.counter = counter
+ p.c = extendnew(q, {counter: counter})

But it would be nice to know if the type checking can be wrangled into allowing the nested dict to be updated in place.

Not sure but this looks like a bug I noticed a long time ago, but didn't report yet (because I wasn't sure).
This snippet raises E1012:
vim9script
var d: list<dict<any>> = [{a: 0}]
for e in d
    e = {a: 0, b: ''}
endfor

E1012: Type mismatch; expected dict<number> but got dict<any>

This works now:
vim      vim9script      var d: list<dict<any>> = [{a: 0}]      for e in d          e.b = ''      endfor
Assigning to "e" is actually not allowed, it doesn't work.  I'll make
another patch for that.
--
From "know your smileys":
:-| :-|   Deja' vu!
/// Bram Moolenaar -- Bram@Moolenaar.net -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Thank you.

vim9script
final foo = [
var foo: list<dict> = [
{
a: "Cat",
b: false,
c: [
{x: "Dog"},
]
}
]
var counter = 0
for p in foo
for q in p.c
counter += 1
q.counter = counter    # ← this is the line that generates the E1012 error
endfor
endfor

authors: Leeeooo19888 airblade brammool lacygoill


text:
Vim9: should we enforce  instead of  inside a function?

<sfile> is too ambiguous in legacy.  At the script level, it gives the path of the sourced script, but in a function it gives the call stack.  We can't remove this ambiguity in legacy because it could break existing scripts, but we could remove it in Vim9, by enforcing <stack> instead of <sfile> in a function.  Vim supports the latter since 8.2.1297.
This would make the code more readable, because <sfile> reads as if we get a simple file path, while in reality we get a call stack.  Besides, it would make issues such as https://github.com/vim/vim/issues/9178 easier to debug.  The solution is obvious in hindsight, but the debugging took more time than it should have, because the fact that <sfile> gives a call stack might be hidden when we use filename modifiers.
So this snippet:
vim9script
def Func()
    eval expand('<sfile>')
enddef
Func()
echo 'no error'

no error

Could give an error such as:
E1234: <sfile> can only be used at script-level

What if someone wants to get the script name where the function was defined?
I can't find something simpler than setting a variable at script level that expands
and using that variable in the function.
Perhaps we can add "", as the file where the function was defined.

What if someone wants to get the script name where the function was defined?
I can't find something simpler than setting a variable at script level that expands
and using that variable in the function.

Yes, that's exactly what I do.  I don't know any other way.

Perhaps we can add "", as the file where the function was defined.

Sorry, the name between angle brackets has disappeared on github.  But yes, I guess we could introduce another angle-bracket expression such as <script> which would give us the name of the script from everywhere (script level and function).

I was thinking of "funcfile", but "script" would be simpler.  So you would stop using "sfile", which has a value that depends on the place where it is used, and use "script" and "stack" instead.

Closing because the original issue has been fixed in patch 8.2.3646.  The <script> angle-bracket expression is a separate issue which has been noted in the todo list.

authors: brammool lacygoill


text:
Fix issue #14927, type mismatch error in ccomplete

Fixes #14927

thanks!

authors: chrisbra kyllingstad


text:
Problem:    No common way of building for Amiga / Amiga-like systems.

Solution:   A single unified Makefile for AmigaOS, MorphOS and AROS.

I think src/INSTALLami.txt should be updated.

I think src/INSTALLami.txt should be updated.

True. Fixed it.

Merged as 8.2.1648 (https://github.com/vim/vim/commit/a62372be1f73b69f9d4c9413ec816d773a16a0f5).

authors: k-takata sodero


text:
Release 1.0.0

Issue related to release struct_db more details here: Roadmap

:point_right: redb is in stabilization phase: https://github.com/cberner/redb/issues/575

Pretty cool. Kinda weird tho.

I close this issue for now, the release 1.0.0 is not for now.

authors: Brandon-Huu vincent-herlemont


text:
Added port logging

Description

The random port opened from index.js will be logged onto console
Added a warning message in index.js, not to stop servers while analysis

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have added all the three reviewers: @vinitshahdeo, @kashish121 & @ishika1727

Please review @Kashish121 @vinitshahdeo @ishika1727

repo: vinitshahdeo/PortScanner


text:
Fix rfc2616 Section 4.2 compliance:

basic_headers no longer combines fields with the same name by appending a comma and concatenating the two values together. This was breaking certain header fields which expect each value to be distinct, such as the "Set-Cookie" header.
Now the container behaves more like a multi set with respect to insertion of multiple values with the same field name. Additional member functions are provided to provide extra functionality.
Reviewers: @HowardHinnant @scottschurr @willwray

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

Merging [#37][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.05%

@@             master        #37   diff @@
==========================================
  Files            72         72
  Lines          5073       5075     +2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           4977       4976     -1
- Misses           96         99     +3
  Partials          0          0

Powered by Codecov. Last updated by [999e2fa...db58cf1][cc-compare]
[cc-base-branch]: https://codecov.io/gh/vinniefalco/Beast/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/vinniefalco/Beast/compare/999e2fa0318b5982736d3ea01a418770ea802671...db58cf1c0f4f215c9bc15450e096e41e2c169748
[cc-pull]: https://codecov.io/gh/vinniefalco/Beast/pull/37?src=pr

:+1: Looks good to me.

👍 Looks good here.  Passes tests on macOS.

authors: HowardHinnant codecov-io scottschurr vinniefalco

repo: vinniefalco/Beast


text:
Flow with multiple devices will sometimes report "Cannot call write after a stream was destroyed" after re-deploy

Hi,
first of all thank you for that awesome extension of node-red. Works quite well so far!
Sometimes I get an error Error from socket: Cannot call write after a stream was destroyed after I re-deploy my flow for some nodes that use the tuya-smart-device node. Mostly it is the same node. The only solution to fix the problem is restarting node-red. Otherwise the error will continue to be thrown.
Does anyone has an idea why that happens?
I've configured all nodes to use Device Virtual ID and Device Key.
Best,
Jakob

Can you please share the logs for further investigation ?

Hi, I have the log of Node-RED, does this help in any way? Or is there an option to get a more detailed log?
16 May 20:02:42 - [info] Started flows
16 May 20:02:42 - [info] [server:Home Assistant] Connecting to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Close
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT End
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Connected
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:42 - [info] [server:Home Assistant] Connected to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Subscribed to: "zigbee2mqtt/#
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-2] initiating the find command
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-1] initiating the find command
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed

Are the two plugs same brand?
On Sun, 16 May 2021 at 11:35 PM, Jakob Nohe @.***>
wrote:

Hi, I have the log of Node-RED, does this help in any way? Or is there an
option to get a more detailed log?
16 May 20:02:42 - [info] Started flows
16 May 20:02:42 - [info] [server:Home Assistant] Connecting to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Close
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT End
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Connected
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:42 - [info] [server:Home Assistant] Connected to http://hass:8123
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] MQTT Subscribed to: "zigbee2mqtt/#
16 May 20:02:42 - [info] [zigbee2mqtt-server:zigbee2mqtt] Refreshing devices
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-2] initiating the find command
16 May 20:02:43 - [info] [tuya-smart-device:power-plug-1] initiating the find command
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [info] [tuya-smart-device:power-plug-2] Connected to device! bf29d8d6d5becdd503m0ta
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:44 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:45 - [info] [tuya-smart-device:power-plug-1] Connected to device! bf8780a47556c35c8a8lg2
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:02:52 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:02:54 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:04 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:14 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-2] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":16,"18":0,"19":0,"20":2311,"21":1,"22":621,"23":30545,"24":17787,"25":1172,"26":0}}
16 May 20:03:22 - [info] [tuya-smart-device:power-plug-1] Data from device  [event:data]: {"dps":{"1":true,"9":0,"17":65,"18":0,"19":0,"20":2226,"21":1,"22":595,"23":29200,"24":16636,"25":1252,"26":0}}
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:24 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
16 May 20:03:34 - [error] [tuya-smart-device:power-plug-1] Error: Error from socket: Cannot call write after a stream was destroyed
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vinodsr/node-red-contrib-tuya-smart-device/issues/60#issuecomment-841853538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADQ6OARI25ICDXEBBJQRNDTOACOPANCNFSM44BUNB4Q
.

--
Vinod Surendran R
tenthsone.com
tenthsone.com/adspot (new)
tenthsone.com/junk
talk.tenthstone.com [beta]

All power plugs are from the same brand (and the same model): Teckin SP22

Maybe this can help, I found some more log that is produced before the flow is started:
24 May 14:04:45 - [info] Flows werden gestartet
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Recieved the config {"id":"eaa4fd2.896ec","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-2","deviceId":"bf29d8d6d5becd******","deviceKey":"a6c759da92******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":320,"wires":[["3c74be4e.913f32"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Connecting to Tuya with params {"id":"bf29d8d6d5becdd503m0ta","key":"a6c759da928751c2","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Recieved the config {"id":"73bd27e1.eb9168","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-1","deviceId":"bf8780a47556c3******","deviceKey":"7affab4704******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":120,"wires":[["8ffa77b.f1a6288"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Connecting to Tuya with params {"id":"bf8780a47556c35c8a8lg2","key":"7affab4704b16fb7","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

Maybe this can help, I found some more log that is produced before the flow is started:
24 May 14:04:45 - [info] Flows werden gestartet
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Recieved the config {"id":"eaa4fd2.896ec","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-2","deviceId":"bf29d8d6d5becd******","deviceKey":"a6c759da92******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":320,"wires":[["3c74be4e.913f32"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-2] Connecting to Tuya with params {"id":"bf29d8d6d5becdd*******","key":"a6c759da9******","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Recieved the config {"id":"73bd27e1.eb9168","type":"tuya-smart-device","z":"d20aa8b8.d7f6b8","deviceName":"power-plug-1","deviceId":"bf8780a47556c3******","deviceKey":"7affab4704******","deviceIp":"","retryTimeout":1000,"findTimeout":1000,"tuyaVersion":"3.1","eventMode":"event-both","x":830,"y":120,"wires":[["8ffa77b.f1a6288"]]}
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Event subscription : shouldSubscribeData=>true , shouldSubscribeRefreshData=>true
24 May 14:04:46 - [info] [tuya-smart-device:power-plug-1] Connecting to Tuya with params {"id":"bf8780a47556c******","key":"7affab4704******","ip":"","issueGetOnConnect":false,"nullPayloadOnJSONError":false,"version":"3.1"} , findTimeout :  1000 , retryTimeout:  1000

I just got similar issue. The issue was because I had a duplicate node for the same device. Once I removed the duplicate the issue was resolved,

Also released a new version which enables reconnect command, please check that as well

authors: foxylion vinodsr


text:
[DeleteRecord] Delete record validations

Support deleting a single DNS entry in batch change validations
Changes in this pull request:

Add new error type for DeleteRecord
Update batch change validation logic
Add/update unit tests

@britneywright I don't believe we can rename RecordDoesNotExist to RecordSetDoesNotExist (at least not in SingleChangeErrors) since they are getting stored.

repo: vinyldns/vinyldns


text:
VC-4233: Create db schema assets

Description
Closes: #XXXX

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Нужно сквош коммитов сделать, сейчас их два одинаковых

LGTM

repo: vipcoin-gold/bdjuno


text:
Update index.html

django.template.exceptions.TemplateSyntaxError: 'staticfiles' is not a registered tag library. Must be one of:

fixed in #3

authors: frennkie jrespeto

repo: viper-framework/viper-web


text:
how to change keybinding

怎么改键位

repo: vipzhicheng/logseq-plugin-vim-shortcuts


text:
Navigating between pages

on the /product/ pages there is no way to see more than 15 items at the moment (default amount) .. but you're also not able to go to the following pages.

100 products are being shown at the moment, till i get around to adding pagination

repo: viridis/BouncyCastle