create saved searches and alerts for canary feature

Need the following alerts and searches for canary:

search for testflight records with aggregation to graph elapsed time
alert for all canary records with result != true
search for testflight with a specific uuid (accept uuid as a parameter)

stretch * alert for canary records over some user provided threshold for elapsed_time

Closed after pull request https://github.com/Solinea/goldstone-server/pull/465 merged


Fix ORCA handling queries with GROUP BY PRIMARY KEY

Fix ORCA handling queries with target columns not listed in the GROUP BY clause
Problem description: ORCA fails to handle queries with columns in the target
list, not listed in GROUP BY clause, if grouping is done by a primary key
(meaning that these columns have a functional dependency on grouping columns).
In such a case, it falls back to the standard planner. Expected behavior - ORCA
generates a plan for a query with columns in target list, if these columns have
a functional dependency on columns in GROUP BY list.
Root cause: Function CQueryMutators::ShouldFallback during query normalization
finds out that there is a target list entry, that is not a grouping column, and
it triggers fallback to the standard planner.
Fix: All columns from the target list with functional dependency on grouping
columns are added explicitly to group by clause at the query normalization stage
(at start of groupby normalization, before checking if fallback is required)
before the translation to DXL. It requires the following steps:

Extract such columns from target list expressions, and if they do not have a
relevant target list entry, add resjunk target list entries for them.
Store current unique target list entry references in groupClause - they will
be required at step 4.
Update all grouping sets that contain the primary key - add the functionally
dependent columns from the target list.
Update arguments of GROUPING functions (based on target list entry references
stored on step 1 and updated target list entry references), because they could
be shifted after step 3.

Plus, new test cases were added to the functional_deps test.

Allure report https://allure-ee.adsw.io/launch/64097

Failed job ORCA code linter on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1057923

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1057921

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1057922

Allure report https://allure-ee.adsw.io/launch/64108

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058171

Allure report https://allure-ee.adsw.io/launch/64120

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058639

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058640

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058631

Failed job Regression tests with Postgres on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058632

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058633

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1058634

Allure report https://allure-ee.adsw.io/launch/64251

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1062082

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1062083

Note for review: if someone tries to re-check the expected output of test queries with postgres planner (by setting optimizer=off) and gets different output - that is because of this issue https://tracker.yandex.ru/ADBDEV-4888. Be aware.

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1062074

Allure report https://allure-ee.adsw.io/launch/64266

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1062242

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1062243

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1062233

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1063019

Allure report https://allure-ee.adsw.io/launch/64338

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1064063

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1064061

Allure report https://allure-ee.adsw.io/launch/64538

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1070377

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1070370

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1070514

Allure report https://allure-ee.adsw.io/launch/64597

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1071560

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1071561

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1071553

Allure report https://allure-ee.adsw.io/launch/64843

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1081809

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1081810

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1081803

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1082009

Allure report https://allure-ee.adsw.io/launch/64873

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1082953

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1082951

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1082954

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1084672

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1087775

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1087776

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091045

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091046

Allure report https://allure-ee.adsw.io/launch/65054

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091157

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091158

Allure report https://allure-ee.adsw.io/launch/65059

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091320

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091321

Allure report https://allure-ee.adsw.io/launch/65069

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1091718

Allure report https://allure-ee.adsw.io/launch/65142

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1093460

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1093461

How about somehow using a func_grouped_rels list that is populated BEFORE calling the ORCA planner?

In my opinion, the current patch implementation violates the core principle of ORCA as an independent query planner.
Why does ORCA need to go into the system catalog once again, if the parser already does this before?

You are mostly right. Catalog access happens anyway during Query to DXL translation, this stage is dependent from host structure. ORCA must be independent after it got DXL as input. But we definetely should investigate another approach.

In my opinion, the current patch implementation violates the core principle of ORCA as an independent query planner.

ORCA's interface for communication with database management system is DXL representation of a query (https://github.com/greenplum-db/gpdb/wiki/ORCA-Training-Boot-Camp#orca---query-life-cycle ).
Changes from the patch are applied before translation to DXL. Doing this preprocessing of a query in the CQueryMutators shouldn't violate ORCA's principles.

How about somehow using a func_grouped_rels / constraintDeps list that is populated BEFORE calling the ORCA planner?

We already use constraintDeps.
func_grouped_rels is not populated anywhere outside parseCheckAggregates. Passing it to CQueryMutators is possible only via the query tree, but I would like to avoid modification of its structure (as we need to minimize changes of postgres code).
But even if we pass func_grouped_rels to CQueryMutators::FixGroupDependentTargets, it will not eliminate the need to access the system catalog from CQueryMutators::GroupingListContainsPrimaryKey,
because for every var in the target list, that is not included in the group, we need to examine every grouping set separately, and add it only to grouping sets that have primary key.
For example, in
SELECT a, b FROM test_table1 GROUP BY GROUPING SETS ((a), (c)); 'b' should be added only to the first grouping set ->
SELECT a, b FROM test_table1 GROUP BY GROUPING SETS ((a, b), (c));
Moving the update of the query tree to the earlier stage (where func_grouped_rels & constraintDeps are filled) means modifying the query tree at parsing stage. It has the following disadvantages:

It means modifying the original postgres code (the thing we would like to avoid).
It means that the work of standard postgres planner will also be affected. It doesn't sound good to me.

I see obvious disadvantages with non-visible benefits. Thus, I think leaving the code in CQueryMutators is better.

How about to do work on C-part like transformGroupedWindows function?

The same thoughts here:

It means modifying the original postgres code (the thing we would like to avoid).
It means that the work of standard postgres planner will also be affected. It doesn't sound good to me.

What will be the benefit if the implementation is done similar to transformGroupedWindows (somewhere in transformSelectStmt I guess)?

How about to do work on C-part like transformGroupedWindows function?

The same thoughts here:

It means modifying the original postgres code (the thing we would like to avoid).
It means that the work of standard postgres planner will also be affected. It doesn't sound good to me.

What will be the benefit if the implementation is done similar to transformGroupedWindows (somewhere in transformSelectStmt I guess)?

I mean transformGroupedWindows in orca.c in 7X

How about to do work on C-part like transformGroupedWindows function?

The same thoughts here:

It means modifying the original postgres code (the thing we would like to avoid).
It means that the work of standard postgres planner will also be affected. It doesn't sound good to me.

What will be the benefit if the implementation is done similar to transformGroupedWindows (somewhere in transformSelectStmt I guess)?

I mean transformGroupedWindows in orca.c in 7X

Ok, let me check tomorrow

How about to do work on C-part like transformGroupedWindows function?

The same thoughts here:

It means modifying the original postgres code (the thing we would like to avoid).
It means that the work of standard postgres planner will also be affected. It doesn't sound good to me.

What will be the benefit if the implementation is done similar to transformGroupedWindows (somewhere in transformSelectStmt I guess)?

I mean transformGroupedWindows in orca.c in 7X

Ok, let me check tomorrow

Ok, I see following:
in e52dd03263379ffca688be03f9d791f1ffae76e8 transformGroupedWindows was moved to orca.c from transformSelectStmt in parser. Reason - before this change it affected the Postgres planner (something I also wanted to avoid with my changes).
In this case indeed, we might move the changes to orca.c file. This may provide a slight improvement as we can get rid of wrappers for C functions.
Though it might look a bit weird and not proper place for 6X, since in 6X it doesn't have much code in orca.c file.
But it will be Ok if we look into the orca.c file in 7X.
@bimboterminator1 are you Ok with this change (moving code from CQueryMutators to orca.c)? Do you see any drawbacks?

@whitehawk. I don't mind, if the changes will be more compact (without lots of new walkers and contexts) and optimal. And you'll better do it in a separate branch (for convinience).

@RekGRpth @bimboterminator1 ,
I've tried to move my changes to orca.c file. And after detailed analysis I've got two additonal inputs for you:
First, CTranslatorUtils::IsGroupingColumn is not accessible directly from orca.c. So, either we need to duplicate its logic, or make a c-wrapper.
Second, if my changes are applied in optimize_query right before
result = GPOPTOptimizedPlan(pqueryCopy, &fUnexpectedFailure);

some tests (with joins and HAVING) fail.
The reason is that now my changes are applied before  gpdb::FlattenJoinAliasVar and CQueryMutators::NormalizeHaving
in CQueryMutators::NormalizeQuery. If I place my changes after them, all tests pass.
That is a strong reason to keep the logic at current place in CQueryMutators.
If chosing between several additional wrappers (quit simple and safe) and inventing excessive logic to process joins and having clause (which might be not trivial), I would choose first.

Allure report https://allure-ee.adsw.io/launch/65517

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1110279

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1110280

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1110273

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1111051

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1112621

That is a strong reason to keep the logic at current place in CQueryMutators.

Can we collect all the necessary supporting information with one lock in optimize_query and then use it in FixGroupDependentTargets, similar to how constraintDeps is already used there?

Allure report https://allure-ee.adsw.io/launch/65930

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1127083

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1127081

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1128789

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1128790

Allure report https://allure-ee.adsw.io/launch/66034

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1130959

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1130960

That is a strong reason to keep the logic at current place in CQueryMutators.

Can we collect all the necessary supporting information with one lock in optimize_query and then use it in FixGroupDependentTargets, similar to how constraintDeps is already used there?

Even if it is possible, as we can't completely eliminate code in CQueryMutators, what is the purpose of spreading the code across several files? It will make more difficult possible porting to other branches if needed and it will make the code more difficult to understand.

Failed job Behave tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1130958

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1130957

Failed job Regression tests with Postgres on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1130952

spreading the code across several files is not reasonable

But in the FixGroupDependentTargets function you use a list constraintDeps, which is filled in a completely different file. I just suggest filling out a similar list in advance, but with the required conrelid and conkeys values. Then in the FixGroupDependentTargets function it will not be necessary to lock and search in the cache several times at each iteration of the loop.

spreading the code across several files is not reasonable

But in the FixGroupDependentTargets function you use a list constraintDeps, which is filled in a completely different file. I just suggest filling out a similar list in advance, but with the required conrelid and conkeys values. Then in the FixGroupDependentTargets function it will not be necessary to lock and search in the cache several times at each iteration of the loop.

I believe we already touched this topic. constraintDeps is a member of Query structure, and it comes from Postgres. It is not GPDB specific. Passing lists with conrelid and conkeys to CQueryMutators::NormalizeQuery will require

either adding additional parameters to all functions leading to CQueryMutators::NormalizeQuery (that will complicate possible future porting of these changes)
or adding these lists to Query structure, but it means modification of original postgres code, that we also strongly try to avoid.

Allure report https://allure.adsw.io/launch/66037

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1131360

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1131361

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1131355

Allure report https://allure.adsw.io/launch/66235

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140241

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140242

Allure report https://allure.adsw.io/launch/66245

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140418

Allure report https://allure.adsw.io/launch/66258

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140836

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140837

Failed job Behave tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140835

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1140831

Allure report https://allure.adsw.io/launch/66568

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1156229

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1156230

Allure report https://allure.adsw.io/launch/66739

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1167220

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1167221

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1167218

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1167214

Allure report https://allure.adsw.io/launch/66848

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1172893

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1172894

Failed job Regression tests with Postgres on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1172882

Allure report https://allure.adsw.io/launch/66927

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1177461

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1177459

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1177462

Allure report https://allure.adsw.io/launch/66934

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1177926

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1177927

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1177921

Allure report https://allure.adsw.io/launch/66967

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179700

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179664

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179701

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1179694

Allure report https://allure.adsw.io/launch/67120

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1188334

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1188335

Failed job Behave tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1188332

Allure report https://allure.adsw.io/launch/67456

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1206193

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1206194

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1206187

Failed job Regression tests with ORCA on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1206188


my screen is vibrating

i dont know why my screen is vibrating , i am doing nothing still it is vibrating

If you believe this is a rendering issue then please file a bug on the VS Code Repo (https://github.com/microsoft/vscode). If you believe this is python extension specific then, we need some more information from you in order to triage this issue appropriately. Please edit your opening comment by providing a filled-in copy of our issue template. Once you are done please leave a comment to that effect.

now it is working fine thanks well
On Tue 6 Oct, 2020, 10:32 PM Karthik Nadig<EMAIL_ADDRESS>wrote:

If you believe this is a rendering issue then please file a bug on the VS
Code Repo (https://github.com/microsoft/vscode). If you believe this is
python extension specific then, we need some more information from you in
order to triage this issue appropriately. Please edit your opening comment
by providing a filled-in copy of our issue template
https://github.com/microsoft/vscode-python/blob/master/.github/ISSUE_TEMPLATE/2_bug_report.md.
Once you are done please leave a comment to that effect.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/14279#issuecomment-704416193,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTDA6FYFMF3RFTZXTDQVDDSJNEQTANCNFSM4SGHCWTQ
.


vscode: 1.9.0 -> 1.9.1

Motivation for this change
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

nox-review gives an error (see here: https://gist.github.com/xwvvvvwx/d9bdc5b83b4330ffc9fb0ac652dbc857), I think it's unrelated to my change, but I don't know enough nix to be sure....


[space shooter tutorial] The position.x where Bullet is spawned at is unexpected.

FYI, I'm new to flame and flutter, I don't know this should be a improvement or something else.
What could be improved

The "space shooter" tutorial is a good start for me into flame world. When I try it, find something strange. The bullet does not emerge at the player location.x, but at some position offset the right side. After some debugging, the bullet.x seems to be 2 * player.x. So I update the add(_bulletSpawner) to gameRef.add(_bulletSpawner), then the problem is solved.
Why should this be improved

A little flaw in the tutorial.
Any risks?

no.
More information

Yes, I'd like to fix it .

@erickzanardo


Memory usage improvements

These are mostly focused on splitting up enum variants with large size differences between variants by Box-ing things up.
In my testing this reduces the memory usage somewhere in the low percentages, even though the measurements are quite noisy.

In my testing this reduces the memory usage somewhere in the low percentages, even though the measurements are quite noisy.

Did you try rust-analyzer analysis-stats --memory-usage? It's quite stable on CI: https://rust-analyzer.github.io/metrics/

Did you try rust-analyzer analysis-stats --memory-usage path/to/some/repo? It's quite stable on CI (look at the second graph): https://rust-analyzer.github.io/metrics/. Unfortunately, it only works on Linux IIRC.

That looks indeed pretty stable. On rust-analyzer this PR improves memory usage by 4.3%. The improvements on other projects are in the same ballpark, between 1.8% and ~4%.

Nice!
bors r+

This showed up in the metrics:

changelog internal


Mail Preview with Namespace fails to load show action

My mailer preview is behind a namespace Buyers::UserMailer and Vendors::UserMailer
The preview works correctly, but the show action omits the namespace and it fails to load the email.

Thanks for reporting this @dpaluy ! Let me dig into this, I imagine i'm just not taking into account the namespace when i construct the URL.

I checked it briefly. One fix is required to the helper: https://github.com/harrison-broadbent/better_mailer_previews/blob/main/app/helpers/better_mailer_previews/application_helper.rb#L21
url.split("/")[3...]
 I actually came up with the same changes 😅
The other changes i need to make are in the send_email method to contantize the correct string. If you want to have a crack and specs or making any of those changes then go for it! I'll try to work on this myself too but I'll pull together both our contributions for the PR. If you do put up a PR, if possible could you do it against this repo and not a fork? then I can pull and commit to your PR and you'll appear as a contributor

@dpaluy just merged a PR that should fix this! Let me know if there's anything you find, otherwise, thanks for opening the issue!


seek to offsets before last

Provides a way to seek to some number of offsets before the current last offset of each partition.

@Kazark yes, this would seek some number of offsets/records before the end of each partition, regardless of timestamps.


Suggestion for model.update is missing the save

In one of our projects (Ruby 2.3.0 with TargetRubyVersion: 2.3, Rails <IP_ADDRESS>), we have the following line in one of our controller specs:
    context 'with admin logged with attendee dashboard saved' do
      before do
        admin.update(dashboard: :attendee)
        sign_in admin
      end

      it 'redirects to the attendee dashboard' do
        get :index

        expect(response).to redirect_to attendee_dashboard_path
      end
    end

RuboCop complains about the update call:
spec/controllers/home_controller_spec.rb:89:9: C: Use admin[:dashboard] = :attendee instead of admin.update(dashboard: :attendee).
        admin.update(dashboard: :attendee)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

However, the suggestion is not correct. Only assigning the attribute (which is not a relation) will not save the model. So the admin.save needs to be added to the suggestion.

This is fixed in 0.37.1.

Wow, that was fast. Thanks! :heart:


Prevent interaction outside modal

Prevent interaction outside the modal view when it is open
Specifically, courses can be deleted while the modal view is open

Who wants to work on this? Can you take care of it or do you wanna assign it to someone else

I could do it, I just wanted to make note of it


No such table SQLiteException when running multiple tests in paralell including simple repo to reproduce it

I am having intermitent exceptions when writing or reading from a Sqlite database. It happens both in memory and in physical databases that are created at runtime.
It seems like a race condition. I managed to create a simple repo to reproduce the problem.
See this repo at this commit to find details and reproduce it. It's simply a class library with sqlite-net-pcl dependency and a xUnit integration tests project.
If you clone the repo and run the tests you'll see that most likely all of them will fail. If you run one by one they wil succeed
I don't know whether it has something to do with the way the tables are created (I reproduced it the same way as I have it in my Xamarin.Forms application where the initialization happens in a synchronous context when Android runs).
The tests simply write a row and read it to make assertions.
Any advice on whether this is a bug or a bad practice on my side would be much appreciated.

I'm investigating multi-threading issues today so will take a look.
I'm not sure what's happening off the top of my head.


Cannot export Hotspots from the editor

Description
The hotspot feature doesn't works anymore for me. I have this issue since last week or so. I can place hotspots but the snippet will not update to show their position nor create a new < button> or < div> for them [see picture]. When using the export function, the scene created doesnt features any of the hotspots placed with editor. The index.html file is akin to the snippet and devoid of any hotspot mention. Hotspot placed manually/pasted from another scene works.
Version

last online verion of the editor

Browser Affected

[X] Chrome, version: 101.0.4951.54
[X] Edge
[X] Firefox last version
[X] Safari for iPad

OS

[X] Windows 10
[x] Tested on safari for ipad with a default model for the same results

addressed in https://github.com/google/model-viewer/pull/3462


chore: change drawer heading

Don't show call title at the top of drawer, make it more prominent above tabs.
@Yangyi-wandb with this styling the title can get a little squished when you have the trace tree open.
Internal Figma: https://www.figma.com/file/27JVuBYWHbcAYc8WPb4HqA/Weaveflow-hifi?type=design&node-id=2544-113114&mode=design&t=DVq1XHahBd87zaBG-0
Before:

After:

We can make a new line for the title if it's too long, but it seems fine at the moment and can fit in 'evaluate_predict_and_score'.
Can we also make the header a lot thinner now we removed the title from it?

If your browser window isn't that wide you have to have the peek drawer taking up the majority of the page or it will wrap even on Evaluate_predict_and_score.
If we change the peek drawer header height it might look misaligned with the page header. But if you send updated styling instructions I can implement it.


Migration on project with existed tsconfig.json

rehearsal migrate would create new default or custom tsconfig.json during migration. However, if it's running against a project with existed tsconfig.json, the CLI would leave the config file as what it is at this moment, which causes a number of issues:

The existed tsconfig.json is not tight enough for rehearsal to write as much rehearsal TODO as the tool could.
The conflict between rootDir, baseUrl, include in the config.

One Example:
       │ File: tsconfig.json
   1   │ {
   2   │     "$schema": "https://json.schemastore.org/tsconfig",
   3   │     "compilerOptions": {
   4   │         "allowJs": true,
   5   │         "module": "es6",
   6   │         "target": "es6",
   7   │         "skipLibCheck": true,
   8   │         "experimentalDecorators": true,
   9   │         "types": []
  10   │     },
  11   │     "include": ["./lib/**/*.js"]
  12   │ }

After the migration when running tsc:
Command failed with exit code 2: yarn tsc
  error TS18003: No inputs were found in config file 'root-to-projet/tsconfig.json'. Specified 'include' paths were '["./lib/**…

If we run into an instance where a tsconfig exists (partial migration etc) we can extend the existing tsconfig with a tsconfig from rehearsal specifically around strict types. Then execute migrate with this merged tsconfig (tmp dir if we have to). We dont necessarily need to clobber an existing tsconfig. All we care about is rehearsal providing the max number of TODO items (which it needs strict type settings)

Another Example:
       │ File: tsconfig.json
───────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ {
   2   │   "compilerOptions": {
   3   │     /* Visit https://aka.ms/tsconfig.json to read more about this file */
   4   │
   5   │     "target": "es5",                                /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017',
       │  'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
   6   │     "module": "commonjs",                           /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'e
       │ s2020', or 'ESNext'. */
   7   │     "sourceMap": true,                              /* Generates corresponding '.map' file. */
   8   │     "outDir": "./live-tests/build",                 /* Redirect output structure to the directory. */
   9   │     "rootDir": "./live-tests",                      /* Specify the root directory of input files. Use to control the output directory structure
       │  with --outDir. */
  10   │     "removeComments": true,                         /* Do not emit comments to output. */
  11   │
  12   │     /* Strict Type-Checking Options */
  13   │     "strict": true,                                 /* Enable all strict type-checking options. */
  14   │     "esModuleInterop": true,                        /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace
       │ objects for all imports. Implies 'allowSyntheticDefaultImports'. */
  15   │
  16   │     /* Advanced Options */
  17   │     "skipLibCheck": true,                           /* Skip type checking of declaration files. */
  18   │     "forceConsistentCasingInFileNames": true,       /* Disallow inconsistently-cased references to the same file. */
  19   │     "noEmitOnError": true
  20   │   }
  21   │ }

After migration and run tsc, there are TS6059 for every file we just migrated:
 error TS6059: File 'path-to-file/card.ts' is not under 'rootDir'

Addressed in https://github.com/rehearsal-js/rehearsal-js/pull/464/


trident-azure netapp files

Hello Support,
we have Azure NetApp files in Azure US EAST and we have Kubernetes Distribution Rancher 2.3.5 .
I have configured Trident 20.0.1 latest and getting the following errors while creating the PVC.
Environment
Provide accurate information about the environment to help us reproduce the issue.

Trident version: [e.g. 19.10] 20.0.01
Trident installation flags used: [e.g. -d -n trident --use-custom-yaml] tridentctl
Container runtime: [e.g. Docker 19.03.1-CE] 17.03.2,
Kubernetes version: [e.g. 1.15.1] 1.17
Kubernetes orchestrator: [e.g. OpenShift v3.11, Rancher v2.3.3] Rancher 2.3.5
Kubernetes enabled feature gates: [e.g. CSINodeInfo] Yes
OS: [e.g. RHEL 7.6, Ubuntu 16.04]: RHEL 7 /SUSE 12
NetApp backend types: [e.g. CVS for AWS, ONTAP AFF 9.5, HCI 1.7] CVS
Other:

Here is the error.
time="2020-03-21T17:49:57Z" level=info msg="Running Trident storage orchestrator." binary=/usr/local/bin/trident_orchestrator build_time="Fri Feb 28 15:08:01 UTC 2020" version=20.01.1
time="2020-03-21T17:50:11Z" level=warning msg="Could not get server resources, defaulting to Kubernetes flavor." error="unable to retrieve the complete list of server APIs:
metrics.k8s.io/v1beta1: the server is currently unable to handle the request"
time="2020-03-24T19:05:35Z" level=warning msg="Requested size is too small. Setting volume size to the minimum allowable (100 GB)." name=anf-b566270b6d484edfbfcf71631ef7fe00 size=1073741824
time="2020-03-24T19:07:48Z" level=warning msg="Failed to create the volume on this backend." backend=azurenetappfiles_54614 backendUUID=9c339874-b29b-4347-a719-6f8a9b3b381d error="new volume requested with location different from capacity pool location" pool=azurenetappfiles_54614_pool volume=pvc-4e3cef6c-6029-4dda-a885-9a2bf263bb9b
time="2020-03-24T19:07:48Z" level=error msg="GRPC error: rpc error: code = Unknown desc = encountered error(s) in creating the volume: [Failed to create volume pvc-4e3cef6c-6029-4dda-a885-9a2bf263bb9b on storage pool azurenetappfiles_54614_pool from backend azurenetappfiles_54614: new volume requested with location different from capacity pool location]"
time="2020-03-24T19:07:49Z" level=info msg="Found PVC for requested volume pvc-4e3cef6c-6029-4dda-a885-9a2bf263bb9b." UID=4e3cef6c-6029-4dda-a885-9a2bf263bb9b name=akg-test-anf namespace=default size="{{1073741824 0} {} 1Gi BinarySI}" storageClass=azure-netapp-files
time="2020-03-24T19:07:49Z" level=info msg="Found storage class for requested volume pvc-4e3cef6c-6029-4dda-a885-9a2bf263bb9b." name=azure-netapp-files

BR,
Rushi.

It is difficult to determine what is exactly wrong with the provided information. You should look at resolving the "new volume requested with location different from capacity pool location" error first though.

This issue was resolved by NetApp Support.

no ..the underline issue was kubernetes PODs first that i resolved with our team and after installation was good,
We still having one  issue that the Volume deletion is not happening in AZure NetApp files but in K8S the PV/PVC is deleted but the volume is still in AzureNetApp files when checked Azure portal. ? so we need support on that.


USLCI mappings: Not all flows mapped to flows in list error

When running add_uuid_to_flowmapping.py

Correct - the version I pushed includes the unmappable flows.

@bl-young Running add_uuid_to_flowmapping.py  actually chops off any mappings without flow matches.. when I ran it a second time I didn't get the error. Is there are reason you need to include the unmapped flows in this mapping? If we were to allow that our flowmappings tests as well as that script would have to be modify or else they will throw errors

We decided to include them for completeness for the Q4 database; explicit non-matches. But there is no reason why it needs to stay that way.
I've confirmed that the list before and after adding UUID matches what we expect.

Let's just preserve the non-matches somewhere else - I agree it's important to record them, but just somewhere else where it won't break the tests.

OK - would you like me to commit the revised file or do you have it there?

I've done it and closing this issue, thanks.


Robot Reconnection Issues

Details are murky but sometime robots require two re-connection cycles when software radio bridge is restarted out of band.
Steps to reproduce:

Start radio bridge
Start robot
Wait for positive connection
Kill and restart radio bridge
Robot will connect
Robot will disconnect and reboot
Robot will connect and stay connected

step 7 should occur at step 5

fixed by #64
Robot didn't handle other robots hello packets which were received due to multicast group


Return message ID of sent message

Hi and thank you for this project!
I want to use the forward message (I've sent a document of 1 mega) but I don't know how can I get the message ID of the message I've sent.

This is indeed tricky, and I found no relaiable solution to this. The cli doesn't return anything except a "SUCCESS".
This is a limitation of the cli.
However you will receive your send messages too, so you could check the following messages if they are posted by the bot (msg.own==True), and at least make guesses.

I think the old issue https://github.com/vysheng/tg/issues/773 is related.

And as far as I know, the cli sends the messages async, so that is not an easy fix there too.

To "bypass" this you can use the history function with only one message just after sending it the id will be there, it is not very clean but would probably work fine.

This is possible too.

Hi @Nanoseb and @luckydonald - Thanks for the workaround! works perfectly!


pythonPackages.*: Disable various checkPhases with zero tests run, libgda: Fix building with newest mysql, vtk_{7,8}: Fix compiling

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Even if there are no tests at this point in time, I don't think the checkPhase should be disabled. If upstream ever adds tests, we now have to remove the doCheck = false; line, rather than just bumping the version (and maybe disabling certain tests that don't work).

It is a maintainers duty to keep up with this. Also most of the time we would need to add pytestCheckHook anyway because python setup.py test is going away and planned to be disabled by default in the future because many pythonApplications who do not have any tests also execute it.
Also a maintainers duty is it to check if all dependencies are still required and the package works correctly. Also python is the only place where we execute those tests by default which most of the time do not reveal bugs in our packaging but code bugs. If we are doing pythomImportsCheck everywhere it is enough for the simpler packages. Complicated things like tensorflow or pandas require tests.

It takes an extra bit of time to figure out it has no tests and just move on to the next phase. Maybe it's just me, but I don't think the disabling of the checkPhase is necessary or desired.

I didn't come up with it but jonringer and I think he knows what he is doing. If we update something I don't want to deal with failing tests which where not there before.

Even if there are no tests at this point in time, I don't think the checkPhase should be disabled. If upstream ever adds tests, we now have to remove the doCheck = false; line, rather than just bumping the version (and maybe disabling certain tests that don't work).

It is a maintainers duty to keep up with this. Also most of the time we would need to add pytestCheckHook anyway because python setup.py test is going away and planned to be disabled by default in the future because many pythonApplications who do not have any tests also execute it.
Also a maintainers duty is it to check if all dependencies are still required and the package works correctly. Also python is the only place where we execute those tests by default which most of the time do not reveal bugs in our packaging but code bugs. If we are doing pythomImportsCheck everywhere it is enough for the simpler packages. Complicated things like tensorflow or pandas require tests.

It takes an extra bit of time to figure out it has no tests and just move on to the next phase. Maybe it's just me, but I don't think the disabling of the checkPhase is necessary or desired.

I didn't come up with it but jonringer and I think he knows what he is doing. If we update something I don't want to deal with failing tests which where not there before.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-linux 1

29 packages failed to build and are new build failures:

appcsxcad: log was empty
cq-editor: log was empty
gtkd: log was empty
horizon-eda: log was empty
inkcut: log was empty
inkscape-extensions.inkcut: log was empty
libsForQt5.qcsxcad: log was empty
(libsForQt515.qcsxcad): log was empty
libsForQt512.qcsxcad: log was empty
libsForQt514.qcsxcad: log was empty
openems: log was empty
python37Packages.cadquery: log was empty
python37Packages.enamlx: log was empty
python37Packages.python-csxcad: log was empty
python37Packages.python-openems: log was empty
python37Packages.pythonocc-core: log was empty
python37Packages.vtk_8: log https://termbin.com/gzzq
python38Packages.enamlx: log was empty
python38Packages.python-csxcad: log was empty
python38Packages.python-openems: log was empty
python38Packages.pythonocc-core: log was empty
python38Packages.vtk_8: log https://termbin.com/yqlb
python39Packages.enamlx: log was empty
python39Packages.python-csxcad: log was empty
python39Packages.python-openems: log was empty
python39Packages.pythonocc-core: log was empty
python39Packages.vtk_8: log https://termbin.com/4jpt
simpleitk: log https://termbin.com/9dvz
tilix: log was empty

60 packages built:

ants
c3d
csxcad
datasette (python38Packages.datasette)
dockbarx
elastix
ezminc
gdcm
glom
gnome3.anjuta
libgda (gnome3.libgda)
gtkpod
gtranslator
i3altlayout
itk
itk4
libgdamm
mirtk
mitmproxy (python38Packages.mitmproxy)
mrtrix
pantheon.elementary-music
python37Packages.asgiref
python37Packages.channels
python37Packages.channels-redis
python37Packages.clifford
python37Packages.daphne
python37Packages.datasette
python37Packages.dicom2nifti
python37Packages.django_3
python37Packages.gdcm
python37Packages.mayavi
python37Packages.mitmproxy
python37Packages.nixpkgs
python37Packages.vtk (python37Packages.vtk_7)
python38Packages.asgiref
python38Packages.channels
python38Packages.channels-redis
python38Packages.clifford
python38Packages.daphne
python38Packages.dicom2nifti
python38Packages.django_3
python38Packages.gdcm
python38Packages.mayavi
python38Packages.nixpkgs
python38Packages.vtk (python38Packages.vtk_7)
python39Packages.asgiref
python39Packages.channels
python39Packages.channels-redis
python39Packages.daphne
python39Packages.dicom2nifti
python39Packages.django_3
python39Packages.gdcm
python39Packages.mitmproxy
python39Packages.nixpkgs
python39Packages.vtk (python39Packages.vtk_7)
raiseorlaunch
remarkable-mouse
sequeler
urlwatch
xfce.xfce4-dockbarx-plugin (xfce.xfce4_dockbarx_plugin)

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-linux 1

29 packages failed to build and are new build failures:

appcsxcad: log was empty
cq-editor: log was empty
gtkd: log was empty
horizon-eda: log was empty
inkcut: log was empty
inkscape-extensions.inkcut: log was empty
libsForQt5.qcsxcad: log was empty
(libsForQt515.qcsxcad): log was empty
libsForQt512.qcsxcad: log was empty
libsForQt514.qcsxcad: log was empty
openems: log was empty
python37Packages.cadquery: log was empty
python37Packages.enamlx: log was empty
python37Packages.python-csxcad: log was empty
python37Packages.python-openems: log was empty
python37Packages.pythonocc-core: log was empty
python37Packages.vtk_8: log https://termbin.com/gzzq
python38Packages.enamlx: log was empty
python38Packages.python-csxcad: log was empty
python38Packages.python-openems: log was empty
python38Packages.pythonocc-core: log was empty
python38Packages.vtk_8: log https://termbin.com/yqlb
python39Packages.enamlx: log was empty
python39Packages.python-csxcad: log was empty
python39Packages.python-openems: log was empty
python39Packages.pythonocc-core: log was empty
python39Packages.vtk_8: log https://termbin.com/4jpt
simpleitk: log https://termbin.com/9dvz
tilix: log was empty

60 packages built:

ants
c3d
csxcad
datasette (python38Packages.datasette)
dockbarx
elastix
ezminc
gdcm
glom
gnome3.anjuta
libgda (gnome3.libgda)
gtkpod
gtranslator
i3altlayout
itk
itk4
libgdamm
mirtk
mitmproxy (python38Packages.mitmproxy)
mrtrix
pantheon.elementary-music
python37Packages.asgiref
python37Packages.channels
python37Packages.channels-redis
python37Packages.clifford
python37Packages.daphne
python37Packages.datasette
python37Packages.dicom2nifti
python37Packages.django_3
python37Packages.gdcm
python37Packages.mayavi
python37Packages.mitmproxy
python37Packages.nixpkgs
python37Packages.vtk (python37Packages.vtk_7)
python38Packages.asgiref
python38Packages.channels
python38Packages.channels-redis
python38Packages.clifford
python38Packages.daphne
python38Packages.dicom2nifti
python38Packages.django_3
python38Packages.gdcm
python38Packages.mayavi
python38Packages.nixpkgs
python38Packages.vtk (python38Packages.vtk_7)
python39Packages.asgiref
python39Packages.channels
python39Packages.channels-redis
python39Packages.daphne
python39Packages.dicom2nifti
python39Packages.django_3
python39Packages.gdcm
python39Packages.mitmproxy
python39Packages.nixpkgs
python39Packages.vtk (python39Packages.vtk_7)
raiseorlaunch
remarkable-mouse
sequeler
urlwatch
xfce.xfce4-dockbarx-plugin (xfce.xfce4_dockbarx_plugin)

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-darwin 1

6 packages marked as broken and skipped:

cq-editor
gnome3.libgda
gtkd
libgda
python39Packages.datasette
remarkable-mouse

32 packages failed to build and are new build failures:

ants: log was empty
c3d: log was empty
elastix: log was empty
ezminc: log was empty
gdcm: log was empty
inkcut: log was empty
itk4: log was empty
mnemosyne: log https://termbin.com/uxgz
python37Packages.cadquery: log was empty
python37Packages.dicom2nifti: log was empty
python37Packages.enamlx: log was empty
python37Packages.gdcm: log was empty
python37Packages.mayavi: log was empty
python37Packages.pythonocc-core: log was empty
python37Packages.vtk: log https://termbin.com/xvhq
(python37Packages.vtk_7): log was empty
python37Packages.vtk_8: log https://termbin.com/khg1
python38Packages.dicom2nifti: log was empty
python38Packages.enamlx: log was empty
python38Packages.gdcm: log was empty
python38Packages.mayavi: log was empty
python38Packages.pythonocc-core: log was empty
python38Packages.vtk: log https://termbin.com/ilno
(python38Packages.vtk_7): log was empty
python38Packages.vtk_8: log https://termbin.com/nmsz
python39Packages.dicom2nifti: log was empty
python39Packages.enamlx: log was empty
python39Packages.gdcm: log was empty
python39Packages.pythonocc-core: log was empty
python39Packages.vtk: log https://termbin.com/9mur
(python39Packages.vtk_7): log was empty
python39Packages.vtk_8: log https://termbin.com/h0td

44 packages built:

anki
appdaemon
datasette (python38Packages.datasette)
gdbgui
mitmproxy (python38Packages.mitmproxy)
python37Packages.asgiref
python37Packages.asyncio-dgram
python37Packages.channels
python37Packages.channels-redis
python37Packages.clifford
python37Packages.daphne
python37Packages.datasette
python37Packages.django_3
python37Packages.flask-socketio
python37Packages.mitmproxy
python37Packages.nixpkgs
python37Packages.python-engineio
python37Packages.python-socketio
python37Packages.pywizlight
python38Packages.asgiref
python38Packages.asyncio-dgram
python38Packages.channels
python38Packages.channels-redis
python38Packages.clifford
python38Packages.daphne
python38Packages.django_3
python38Packages.flask-socketio
python38Packages.nixpkgs
python38Packages.python-engineio
python38Packages.python-socketio
python38Packages.pywizlight
python39Packages.asgiref
python39Packages.asyncio-dgram
python39Packages.channels
python39Packages.channels-redis
python39Packages.daphne
python39Packages.django_3
python39Packages.flask-socketio
python39Packages.mitmproxy
python39Packages.nixpkgs
python39Packages.python-engineio
python39Packages.python-socketio
python39Packages.pywizlight
urlwatch

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-darwin 1

6 packages marked as broken and skipped:

cq-editor
gnome3.libgda
gtkd
libgda
python39Packages.datasette
remarkable-mouse

32 packages failed to build and are new build failures:

ants: log was empty
c3d: log was empty
elastix: log was empty
ezminc: log was empty
gdcm: log was empty
inkcut: log was empty
itk4: log was empty
mnemosyne: log https://termbin.com/uxgz
python37Packages.cadquery: log was empty
python37Packages.dicom2nifti: log was empty
python37Packages.enamlx: log was empty
python37Packages.gdcm: log was empty
python37Packages.mayavi: log was empty
python37Packages.pythonocc-core: log was empty
python37Packages.vtk: log https://termbin.com/xvhq
(python37Packages.vtk_7): log was empty
python37Packages.vtk_8: log https://termbin.com/khg1
python38Packages.dicom2nifti: log was empty
python38Packages.enamlx: log was empty
python38Packages.gdcm: log was empty
python38Packages.mayavi: log was empty
python38Packages.pythonocc-core: log was empty
python38Packages.vtk: log https://termbin.com/ilno
(python38Packages.vtk_7): log was empty
python38Packages.vtk_8: log https://termbin.com/nmsz
python39Packages.dicom2nifti: log was empty
python39Packages.enamlx: log was empty
python39Packages.gdcm: log was empty
python39Packages.pythonocc-core: log was empty
python39Packages.vtk: log https://termbin.com/9mur
(python39Packages.vtk_7): log was empty
python39Packages.vtk_8: log https://termbin.com/h0td

44 packages built:

anki
appdaemon
datasette (python38Packages.datasette)
gdbgui
mitmproxy (python38Packages.mitmproxy)
python37Packages.asgiref
python37Packages.asyncio-dgram
python37Packages.channels
python37Packages.channels-redis
python37Packages.clifford
python37Packages.daphne
python37Packages.datasette
python37Packages.django_3
python37Packages.flask-socketio
python37Packages.mitmproxy
python37Packages.nixpkgs
python37Packages.python-engineio
python37Packages.python-socketio
python37Packages.pywizlight
python38Packages.asgiref
python38Packages.asyncio-dgram
python38Packages.channels
python38Packages.channels-redis
python38Packages.clifford
python38Packages.daphne
python38Packages.django_3
python38Packages.flask-socketio
python38Packages.nixpkgs
python38Packages.python-engineio
python38Packages.python-socketio
python38Packages.pywizlight
python39Packages.asgiref
python39Packages.asyncio-dgram
python39Packages.channels
python39Packages.channels-redis
python39Packages.daphne
python39Packages.django_3
python39Packages.flask-socketio
python39Packages.mitmproxy
python39Packages.nixpkgs
python39Packages.python-engineio
python39Packages.python-socketio
python39Packages.pywizlight
urlwatch

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-darwin 1

31 packages failed to build and are new build failures:

ants: log was empty
c3d: log was empty
elastix: log was empty
ezminc: log was empty
gdcm: log was empty
inkcut: log was empty
inkscape-extensions.inkcut: log was empty
itk: log was empty
itk4: log was empty
mnemosyne: log https://termbin.com/scc9
python37Packages.cadquery: log was empty
python37Packages.dicom2nifti: log was empty
python37Packages.enamlx: log was empty
python37Packages.gdcm: log was empty
python37Packages.mayavi: log was empty
python37Packages.pythonocc-core: log was empty
python37Packages.vtk: log https://termbin.com/3km6
python37Packages.vtk_8: log https://termbin.com/w2jw
python38Packages.dicom2nifti: log was empty
python38Packages.enamlx: log was empty
python38Packages.gdcm: log was empty
python38Packages.mayavi: log was empty
python38Packages.pythonocc-core: log was empty
python38Packages.vtk: log https://termbin.com/wfmj
python38Packages.vtk_8: log https://termbin.com/nvmq
python39Packages.dicom2nifti: log was empty
python39Packages.enamlx: log was empty
python39Packages.gdcm: log was empty
python39Packages.pythonocc-core: log was empty
python39Packages.vtk: log https://termbin.com/eqmk
python39Packages.vtk_8: log https://termbin.com/1v4k

24 packages built:

anki
appdaemon
gdbgui
python37Packages.asyncio-dgram
python37Packages.clifford
python37Packages.flask-socketio
python37Packages.nixpkgs
python37Packages.python-engineio
python37Packages.python-socketio
python37Packages.pywizlight
python38Packages.asyncio-dgram
python38Packages.clifford
python38Packages.flask-socketio
python38Packages.nixpkgs
python38Packages.python-engineio
python38Packages.python-socketio
python38Packages.pywizlight
python39Packages.asyncio-dgram
python39Packages.flask-socketio
python39Packages.nixpkgs
python39Packages.python-engineio
python39Packages.python-socketio
python39Packages.pywizlight
urlwatch

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-darwin 1

31 packages failed to build and are new build failures:

ants: log was empty
c3d: log was empty
elastix: log was empty
ezminc: log was empty
gdcm: log was empty
inkcut: log was empty
inkscape-extensions.inkcut: log was empty
itk: log was empty
itk4: log was empty
mnemosyne: log https://termbin.com/scc9
python37Packages.cadquery: log was empty
python37Packages.dicom2nifti: log was empty
python37Packages.enamlx: log was empty
python37Packages.gdcm: log was empty
python37Packages.mayavi: log was empty
python37Packages.pythonocc-core: log was empty
python37Packages.vtk: log https://termbin.com/3km6
python37Packages.vtk_8: log https://termbin.com/w2jw
python38Packages.dicom2nifti: log was empty
python38Packages.enamlx: log was empty
python38Packages.gdcm: log was empty
python38Packages.mayavi: log was empty
python38Packages.pythonocc-core: log was empty
python38Packages.vtk: log https://termbin.com/wfmj
python38Packages.vtk_8: log https://termbin.com/nvmq
python39Packages.dicom2nifti: log was empty
python39Packages.enamlx: log was empty
python39Packages.gdcm: log was empty
python39Packages.pythonocc-core: log was empty
python39Packages.vtk: log https://termbin.com/eqmk
python39Packages.vtk_8: log https://termbin.com/1v4k

24 packages built:

anki
appdaemon
gdbgui
python37Packages.asyncio-dgram
python37Packages.clifford
python37Packages.flask-socketio
python37Packages.nixpkgs
python37Packages.python-engineio
python37Packages.python-socketio
python37Packages.pywizlight
python38Packages.asyncio-dgram
python38Packages.clifford
python38Packages.flask-socketio
python38Packages.nixpkgs
python38Packages.python-engineio
python38Packages.python-socketio
python38Packages.pywizlight
python39Packages.asyncio-dgram
python39Packages.flask-socketio
python39Packages.nixpkgs
python39Packages.python-engineio
python39Packages.python-socketio
python39Packages.pywizlight
urlwatch

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-linux 1

14 packages failed to build and are new build failures:

appcsxcad: log was empty
gtkd: log was empty
qcsxcad: log was empty
(libsForQt5.qcsxcad): log was empty
libsForQt512.qcsxcad: log was empty
libsForQt514.qcsxcad: log was empty
openems: log was empty
python37Packages.python-csxcad: log was empty
python37Packages.python-openems: log was empty
python38Packages.python-csxcad: log was empty
python38Packages.python-openems: log was empty
python39Packages.python-csxcad: log was empty
python39Packages.python-openems: log was empty
tilix: log was empty

53 packages built:

ants
c3d
cq-editor
csxcad
dockbarx
elastix
ezminc
gdcm
glom
gnome3.anjuta
gnome3.libgda
gtkpod
gtranslator
horizon-eda
i3altlayout
inkcut
inkscape-extensions.inkcut
itk
itk4
libgdamm
mirtk
pantheon.elementary-music
python37Packages.cadquery
python37Packages.clifford
python37Packages.dicom2nifti
python37Packages.enamlx
python37Packages.gdcm
python37Packages.mayavi
python37Packages.nixpkgs
python37Packages.pythonocc-core
python37Packages.vtk
python37Packages.vtk_8
python38Packages.clifford
python38Packages.dicom2nifti
python38Packages.enamlx
python38Packages.gdcm
python38Packages.mayavi
python38Packages.nixpkgs
python38Packages.pythonocc-core
python38Packages.vtk
python38Packages.vtk_8
python39Packages.dicom2nifti
python39Packages.enamlx
python39Packages.gdcm
python39Packages.nixpkgs
python39Packages.pythonocc-core
python39Packages.vtk
python39Packages.vtk_8
raiseorlaunch
remarkable-mouse
sequeler
urlwatch
xfce.xfce4-dockbarx-plugin

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-linux 1

14 packages failed to build and are new build failures:

appcsxcad: log was empty
gtkd: log was empty
qcsxcad: log was empty
(libsForQt5.qcsxcad): log was empty
libsForQt512.qcsxcad: log was empty
libsForQt514.qcsxcad: log was empty
openems: log was empty
python37Packages.python-csxcad: log was empty
python37Packages.python-openems: log was empty
python38Packages.python-csxcad: log was empty
python38Packages.python-openems: log was empty
python39Packages.python-csxcad: log was empty
python39Packages.python-openems: log was empty
tilix: log was empty

53 packages built:

ants
c3d
cq-editor
csxcad
dockbarx
elastix
ezminc
gdcm
glom
gnome3.anjuta
gnome3.libgda
gtkpod
gtranslator
horizon-eda
i3altlayout
inkcut
inkscape-extensions.inkcut
itk
itk4
libgdamm
mirtk
pantheon.elementary-music
python37Packages.cadquery
python37Packages.clifford
python37Packages.dicom2nifti
python37Packages.enamlx
python37Packages.gdcm
python37Packages.mayavi
python37Packages.nixpkgs
python37Packages.pythonocc-core
python37Packages.vtk
python37Packages.vtk_8
python38Packages.clifford
python38Packages.dicom2nifti
python38Packages.enamlx
python38Packages.gdcm
python38Packages.mayavi
python38Packages.nixpkgs
python38Packages.pythonocc-core
python38Packages.vtk
python38Packages.vtk_8
python39Packages.dicom2nifti
python39Packages.enamlx
python39Packages.gdcm
python39Packages.nixpkgs
python39Packages.pythonocc-core
python39Packages.vtk
python39Packages.vtk_8
raiseorlaunch
remarkable-mouse
sequeler
urlwatch
xfce.xfce4-dockbarx-plugin

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-linux 1

14 packages failed to build and are new build failures:

appcsxcad: log was empty
gtkd: log was empty
libsForQt5.qcsxcad: log was empty
(libsForQt515.qcsxcad): log was empty
libsForQt512.qcsxcad: log was empty
libsForQt514.qcsxcad: log was empty
openems: log was empty
python37Packages.python-csxcad: log was empty
python37Packages.python-openems: log was empty
python38Packages.python-csxcad: log was empty
python38Packages.python-openems: log was empty
python39Packages.python-csxcad: log was empty
python39Packages.python-openems: log was empty
tilix: log was empty

73 packages built:

ants
c3d
cq-editor
csxcad
datasette (python38Packages.datasette)
dockbarx
elastix
ezminc
gdcm
glom
gnome3.anjuta
libgda (gnome3.libgda)
gtkpod
gtranslator
horizon-eda
i3altlayout
inkcut
inkscape-extensions.inkcut
itk
itk4
libgdamm
mirtk
mitmproxy (python38Packages.mitmproxy)
pantheon.elementary-music
python37Packages.asgiref
python37Packages.cadquery
python37Packages.channels
python37Packages.channels-redis
python37Packages.clifford
python37Packages.daphne
python37Packages.datasette
python37Packages.dicom2nifti
python37Packages.django_3
python37Packages.enamlx
python37Packages.gdcm
python37Packages.mayavi
python37Packages.mitmproxy
python37Packages.nixpkgs
python37Packages.pythonocc-core
python37Packages.vtk (python37Packages.vtk_7)
python37Packages.vtk_8
python38Packages.asgiref
python38Packages.channels
python38Packages.channels-redis
python38Packages.clifford
python38Packages.daphne
python38Packages.dicom2nifti
python38Packages.django_3
python38Packages.enamlx
python38Packages.gdcm
python38Packages.mayavi
python38Packages.nixpkgs
python38Packages.pythonocc-core
python38Packages.vtk (python38Packages.vtk_7)
python38Packages.vtk_8
python39Packages.asgiref
python39Packages.channels
python39Packages.channels-redis
python39Packages.daphne
python39Packages.dicom2nifti
python39Packages.django_3
python39Packages.enamlx
python39Packages.gdcm
python39Packages.mitmproxy
python39Packages.nixpkgs
python39Packages.pythonocc-core
python39Packages.vtk (python39Packages.vtk_7)
python39Packages.vtk_8
raiseorlaunch
remarkable-mouse
sequeler
urlwatch
xfce.xfce4-dockbarx-plugin (xfce.xfce4_dockbarx_plugin)

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 108799 run on x86_64-linux 1

14 packages failed to build and are new build failures:

appcsxcad: log was empty
gtkd: log was empty
libsForQt5.qcsxcad: log was empty
(libsForQt515.qcsxcad): log was empty
libsForQt512.qcsxcad: log was empty
libsForQt514.qcsxcad: log was empty
openems: log was empty
python37Packages.python-csxcad: log was empty
python37Packages.python-openems: log was empty
python38Packages.python-csxcad: log was empty
python38Packages.python-openems: log was empty
python39Packages.python-csxcad: log was empty
python39Packages.python-openems: log was empty
tilix: log was empty

73 packages built:

ants
c3d
cq-editor
csxcad
datasette (python38Packages.datasette)
dockbarx
elastix
ezminc
gdcm
glom
gnome3.anjuta
libgda (gnome3.libgda)
gtkpod
gtranslator
horizon-eda
i3altlayout
inkcut
inkscape-extensions.inkcut
itk
itk4
libgdamm
mirtk
mitmproxy (python38Packages.mitmproxy)
pantheon.elementary-music
python37Packages.asgiref
python37Packages.cadquery
python37Packages.channels
python37Packages.channels-redis
python37Packages.clifford
python37Packages.daphne
python37Packages.datasette
python37Packages.dicom2nifti
python37Packages.django_3
python37Packages.enamlx
python37Packages.gdcm
python37Packages.mayavi
python37Packages.mitmproxy
python37Packages.nixpkgs
python37Packages.pythonocc-core
python37Packages.vtk (python37Packages.vtk_7)
python37Packages.vtk_8
python38Packages.asgiref
python38Packages.channels
python38Packages.channels-redis
python38Packages.clifford
python38Packages.daphne
python38Packages.dicom2nifti
python38Packages.django_3
python38Packages.enamlx
python38Packages.gdcm
python38Packages.mayavi
python38Packages.nixpkgs
python38Packages.pythonocc-core
python38Packages.vtk (python38Packages.vtk_7)
python38Packages.vtk_8
python39Packages.asgiref
python39Packages.channels
python39Packages.channels-redis
python39Packages.daphne
python39Packages.dicom2nifti
python39Packages.django_3
python39Packages.enamlx
python39Packages.gdcm
python39Packages.mitmproxy
python39Packages.nixpkgs
python39Packages.pythonocc-core
python39Packages.vtk (python39Packages.vtk_7)
python39Packages.vtk_8
raiseorlaunch
remarkable-mouse
sequeler
urlwatch
xfce.xfce4-dockbarx-plugin (xfce.xfce4_dockbarx_plugin)


Cannot check if your gdb works, continuing anyway

Describe the bug
I get this error running vim 8.2 when starting :Termdebug:
Error detected while processing function 2_StartDebug[2]..2_StartDebug_internal[50]..2_StartDebug_term:
line   97:
Cannot check if your gdb works, continuing anyway
Press ENTER or type command to continue
After a few seconds GDB starts anyway.
To Reproduce
Detailed steps to reproduce the behavior:

Run vim
Type :Termdebug
Wait for error message
A few seconds later, use GDB w/o problems

Expected behavior
I think my GDB takes a few seconds to start, since it loads over NFS. Looks like the script has a timeout waiting for it. I get this error message every time. Either we can increase the time limit, add the ability to disable the check, or log the error in some way that's not so visible.
Environment (please complete the following information):

Vim version 8.2, GDB: 10
OS: Redhat 7
Terminal: GNOME Terminal

I could find no limit that worked so I just commented out the line.
How do I scroll up/down the program output window? This is what I get:
^[[A^[[A^[[A^[[A^[[A^[^[[A^[[A^[[A^[[A^[[A^[[A^[[B^[[B^[[B^B^B^B^[^[^[^[^[[A^[[A^[[A^[[B^[[B^[^[i^[^[^[^[^[^[[A^[[A^[[A^[[B^[[B^[[B^[^[^[^[^[^[^[^B^B^F^F^F
On Fri, Apr 30, 2021 at 1:41 PM Christian Brabandt @.***>
wrote:

Try increasing this limit here
https://github.com/vim/vim/blob/4934ed34c3e2090d1963c89c629cd3ce81d3ecd1/runtime/pack/dist/opt/termdebug/plugin/termdebug.vim#L275
What limit works for you?

Am 30.04.2021 um 20:14 schrieb Uri Moszkowicz @.***>:

Describe the bug
I get this error running vim 8.2 when starting :Termdebug:
Error detected while processing function
2_StartDebug[2]..2_StartDebug_internal[50]..2_StartDebug_term:
line 97:
Cannot check if your gdb works, continuing anyway
Press ENTER or type command to continue
After a few seconds GDB starts anyway.
To Reproduce
Detailed steps to reproduce the behavior:
Run vim
Type :Termdebug
Wait for error message
A few seconds later, use GDB w/o problems
Expected behavior
I think my GDB takes a few seconds to start, since it loads over NFS.
Looks like the script has a timeout waiting for it. I get this error
message every time. Either we can increase the time limit, add the ability
to disable the check, or log the error in some way that's not so visible.
Environment (please complete the following information):
Vim version 8.2, GDB: 10
OS: Redhat 7
Terminal: GNOME Terminal
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vim/vim/issues/8163#issuecomment-830288118, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNJJQWDS46BYONNTPCAQFLTLL2V5ANCNFSM435BRS3A
.

I have a similar problem, after running the Termdebug command I see:
Error detected while processing function <SNR>128_StartDebug[2]..<SNR>128_StartDebug_internal[45]..<SNR>128_StartDebug_term:
line   97:
Cannot check if your gdb works, continuing anyway
Press ENTER or type command to continue

Also for me increasing the limit doesn't seem to help.
I don't have NFS, everything is local, and this is on a very small sample program I'm using specifically for testing termdebug.  My environment is a bit different:

VersionVIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jan 28 2021 17:26:13)
Included patches: 1-814
Modified by Gentoo-8.2.0814-r100

OS: Gentoo
Terminal: x11-terms/rxvt-unicode-9.22-r8

What I have found is that after the error occurs and I press ENTER to continue, the gdb window opens with my cursor at the end of the last line here:
new-ui mi /dev/pts/21
File /usr/include/gcc/**/*.h will be skipped when stepping.
Reading symbols from ./target/debug/sandbox-gdb...
(gdb) new-ui mi /dev/pts/21

If I now immediately press ENTER, I'll get a "New UI allocated" message, and everything will then work perfectly:
new-ui mi /dev/pts/21
File /usr/include/gcc/**/*.h will be skipped when stepping.
Reading symbols from ./target/debug/sandbox-gdb...
(gdb) new-ui mi /dev/pts/21
New UI allocated
(gdb)

If I don't press enter here, and instead clear the line, the GDB window will work fine but vim won't be able to trace the execution.  The PC and Breakpoint highlights won't be shown and I won't be able to set :Break from the source view.

I have a similar problem, after running the Termdebug command I see:
Error detected while processing function <SNR>128_StartDebug[2]..<SNR>128_StartDebug_internal[45]..<SNR>128_StartDebug_term:
line   97:
Cannot check if your gdb works, continuing anyway
Press ENTER or type command to continue

Also for me increasing the limit doesn't seem to help.
I don't have NFS, everything is local, and this is on a very small sample program I'm using specifically for testing termdebug.  My environment is a bit different:

VersionVIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jan 28 2021 17:26:13)
Included patches: 1-814
Modified by Gentoo-8.2.0814-r100

OS: Gentoo
Terminal: x11-terms/rxvt-unicode-9.22-r8

What I have found is that after the error occurs and I press ENTER to continue, the gdb window opens with my cursor at the end of the last line here:
new-ui mi /dev/pts/21
File /usr/include/gcc/**/*.h will be skipped when stepping.
Reading symbols from ./target/debug/sandbox-gdb...
(gdb) new-ui mi /dev/pts/21

If I now immediately press ENTER, I'll get a "New UI allocated" message, and everything will then work perfectly:
new-ui mi /dev/pts/21
File /usr/include/gcc/**/*.h will be skipped when stepping.
Reading symbols from ./target/debug/sandbox-gdb...
(gdb) new-ui mi /dev/pts/21
New UI allocated
(gdb)

If I don't press enter here, and instead clear the line, the GDB
window will work fine but vim won't be able to trace the execution.
The PC and Breakpoint highlights won't be shown and I won't be able to
set :Break from the source view.

Since I cannot reproduce this problem, can I ask you to try out a few
things?
First of all, enable logging by uncommenting the ch_logfile() line
(around line 125).
Now below "Set arguments to be run" add some delay to see if that makes
any difference:
sleep 100m
With different values, up to 1000m.
Another sleep could be used just before sending "new-ui".
Check the "debuglog" for any hints, especially where Vim is waiting for
the gdb response.  You can add more ch_log() calls if needed.
--
MAN:     You don't frighten us, English pig-dog!
He puts hands to his ears and blows a raspberry.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

If I add sleep 200m after "Set arguments to be run" then it is enough to mask the race condition and everything works.  I am attaching the debug log before any changes and a copy after the added sleep statement.

The first sleep worked for me too but I needed 10000m. Even 5000m was not
enough. Log file attached. Thanks!
On Fri, May 14, 2021 at 1:49 PM Daniel Nelson @.***>
wrote:

If I add sleep 200m after "Set arguments to be run" then it is enough to
mask the race condition and everything works. I am attaching the debug log before
any changes https://github.com/vim/vim/files/6480657/debuglog-before.txt
and a copy after
https://github.com/vim/vim/files/6480658/debuglog-with-sleep.txt the
added sleep statement.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vim/vim/issues/8163#issuecomment-841434544, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNJJQROWUBNCZMMPIZL4K3TNVWCXANCNFSM435BRS3A
.

Where exactly did you put that sleep?  I guess it is:
" Set arguments to be run.  First wait a bit to make detecting gdb a bit
" more reliable.
sleep 200m
if len(proc_args)
call term_sendkeys(s:gdbbuf, 'set args ' . join(proc_args) . "\r")
endif

Yes, that is exactly what I did.

That's what I did, except I needed a larger value
On Sat, May 15, 2021 at 5:28 AM Bram Moolenaar @.***>
wrote:

Where exactly did you put that sleep? I guess it is:
" Set arguments to be run. First wait a bit to make detecting gdb a bit
" more reliable.
sleep 200m
if len(proc_args)
call term_sendkeys(s:gdbbuf, 'set args ' . join(proc_args) . "\r")
endif
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vim/vim/issues/8163#issuecomment-841636347, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNJJQWOPXBBNURIUVKEDOLTNZEDRANCNFSM435BRS3A
.

That's what I did, except I needed a larger value

Ideally we wait for something, but I don't know what.  For now a short
delay is likely to help most people, and 200 msec is small enough not to
be noticed.
--
Facepalm statement #2: "If there is a country without immigrants I'm going to
move there"
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

I was thinking that perhaps we could read the (gdb) prompt before sending commands, but one problem I anticipate with this is it would probably break if the prompt was customized.  Another idea is to start gdb with an echo command, and then maybe we could try to read the text:
$ gdb -quiet --eval-command 'echo howdy\n'
File /usr/include/gcc/**/*.h will be skipped when stepping.
howdy
(gdb)

This made me wonder, could we just send all the setup commands as part of the gdb exec command?  I haven't tried to get this working at all, but do you see any immediately obvious problems with it?

I was thinking that perhaps we could read the (gdb) prompt before
sending commands, but one problem I anticipate with this is it would
probably break if the prompt was customized.  Another idea is to start
gdb with an echo command, and then maybe we could try to read the
text:
$ gdb -quiet --eval-command 'echo howdy\n'
File /usr/include/gcc/**/*.h will be skipped when stepping.
howdy
(gdb)

It looks like this works.  We still need a timeout in case reading
symbols takes a long time.  Perhaps five seconds would be sufficient?
I'll use this a little while and send it out later.

This made me wonder, could we just send all the setup commands as part
of the gdb exec command?  I haven't tried to get this working at all,
but do you see any immediately obvious problems with it?

No idea.  You can give it a try.  Note that there are several versions
of gdb floating around, if it works with one it doesn't mean it works
everywhere.
--
FATHER:       Make sure the Prince doesn't leave this room until I come and
get him.
FIRST GUARD:  Not ... to leave the room ... even if you come and get him.
FATHER:       No.  Until I come and get him.
SECOND GUARD: Hic.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

looks like this has been included as of d2ea7cf10a4d026ebd402594d656af7d5c811c24 so closing


hangs afteri2cdetect

Our custom RP2040 firmware hangs after running i2cdetect - why is that?

https://github.com/raspberrypi/bookworm-feedback/issues/263#issuecomment-2173355051

So lame, but the solution is to change the i2c address to i2cdetect does a quick write. Changing to 0x2C!


port 8083 has vulnerabilites on doppler VM.

we have installed CFD 9.5 on our test env. and our scanning is telling us we have vulnerabilities on the log-cache-cf-auth-proxy job which is listening on port 8083.  it is affected by this …
affected by:
https://www.tenable.com/plugins/nessus/20007
https://www.tenable.com/plugins/nessus/42873
tenable.com
SSL Version 2 and 3 Protocol Detection
The remote service encrypts traffic using a protocol with known weaknesses. (Nessus Plugin ID 20007)
tenable.com
SSL Medium Strength Cipher Suites Supported (SWEET32)
The remote service supports the use of medium strength SSL ciphers. (Nessus Plugin ID 42873)
We need a way to specify what TLS protocols are supported and ciphers..
tenable.com
SSL Version 2 and 3 Protocol Detection
The remote service encrypts traffic using a protocol with known weaknesses. (Nessus Plugin ID 20007)
tenable.com
SSL Medium Strength Cipher Suites Supported (SWEET32)
The remote service supports the use of medium strength SSL ciphers. (Nessus Plugin ID 42873)

@andrew-edgar This should be resolved in the most recent versions of log cache. I would recommend upgrading to one of the following:
https://github.com/cloudfoundry/log-cache-release/releases/tag/v2.1.6
https://github.com/cloudfoundry/log-cache-release/releases/tag/v2.2.3
https://github.com/cloudfoundry/log-cache-release/releases/tag/v2.3.1


Fixed bugs in group comparison and started to adept the code to the styleguide of the lintr package

Description

ui.R  fits to the style guide
in server.R first changes to adapt to the style guide were made
functions to get the files  data/taxonNamesReduced.txt (get_name_list) and "data/taxonomyMatrix.txt" (get_taxa_list) were made to avoid redundant code
You can get the list with all ranks with get_taxonomy_ranks
bugs in group comparison are solved

Related Issue

problems with showing the plots in the  group comparison function

you did a great job, @CarlaMoelbert 👍 💯


Error when configuring king-phisher to use postgresql in Kali

################################################################
uname -a = Linux shad0wlyte 3.18.0-kali3-amd64 #1 SMP Debian 3.18.6-1~kali2 (2015-03-02) x86_64 GNU/Linux
pg_hba.conf = /etc/postgresql/9.1/main/pg_hba.conf
Installed via 'wget -q https://github.com/securestate/king-phisher/raw/master/tools/install.sh && sudo bash ./install.sh' method.
################################################################
Using SQLite works a treat, no dramas there.
Made configuration changes to enable Postgresql support as described here: https://github.com/securestate/king-phisher/wiki/Database step by step.
Postgresql user created, pg_hba.conf edited, server_config.yml modified as described and services restarted. Rebooted system just in case.
Error follows:
root@shad0w:/opt/king-phisher# /opt/king-phisher/KingPhisherServer -L INFO -f /opt/king-phisher/server_config.yml
Traceback (most recent call last):
File "/opt/king-phisher/KingPhisherServer", line 205, in
sys.exit(main())
File "/opt/king-phisher/KingPhisherServer", line 98, in main
config = configuration.Configuration(config_file.name)
File "/opt/king-phisher/king_phisher/configuration.py", line 70, in init
self._storage = dict(self._serializer('load', file_h))
File "/opt/king-phisher/king_phisher/configuration.py", line 84, in _serializer
return function(*args)
File "/opt/king-phisher/king_phisher/configuration.py", line 54, in
SERIALIZER_DRIVERS['yml'] = {'load': lambda file_obj: yaml.load(file_obj, Loader=Loader), 'dumps': lambda obj: yaml.dumps(obj, default_flow_style=False, Dumper=Dumper)}
File "/usr/lib/python2.7/dist-packages/yaml/init.py", line 71, in load
return loader.get_single_data()
File "/usr/lib/python2.7/dist-packages/yaml/constructor.py", line 37, in get_single_data
node = self.get_single_node()
File "_yaml.pyx", line 707, in _yaml.CParser.get_single_node (ext/_yaml.c:7622)
File "_yaml.pyx", line 725, in _yaml.CParser._compose_document (ext/_yaml.c:7883)
File "_yaml.pyx", line 776, in _yaml.CParser._compose_node (ext/_yaml.c:8571)
File "_yaml.pyx", line 892, in _yaml.CParser._compose_mapping_node (ext/_yaml.c:10132)
File "_yaml.pyx", line 905, in _yaml.CParser._parse_next_event (ext/_yaml.c:10310)
yaml.parser.ParserError: while parsing a block mapping
in "/opt/king-phisher/server_config.yml", line 5, column 1
did not find expected key
in "/opt/king-phisher/server_config.yml", line 32, column 3
Triple checked passwords, all looks to be in order. Googled extensively in an attempt not to waste anyone's time. Any help very much appreciated.
Silas
Silas

The error doesn't necessarily look like it's related to postgres being used. From the stack trace, it looks like the configuration file might be malformed. I'll see if I can reproduce this later today. Would you be able to post the contents of the server configuration in the meantime?

 The postgresql configuration line in server_config.yml was not indented correctly. Apologies for wasting your time Spencer, and thanks again.
Silas

It's no problem it got me looking into better error handling so the parsing error message will be more clear in the future.


Add AutoMenus in ComponentPlan

Add a new field AutoMenus bool. When  AutoMenus is true, process menus.json and create the Menus

I am interested in this feature. Could you assign it to me?

@Carrotzpc why menu.json instead of menu.yaml?

The new version of the Menu CRD has deprecated parentOwnerReferences and now uses Kubernetes' built-in ownerReferences to define hierarchical relationships. You can no longer directly apply the "menu.yaml" file to create all the menu components as before. Instead, you need to create the parent menu first, obtain the UID of the parent menu, define the ownerReferences, and then create the child menus. In other words, you need to implement the menu creation programmatically. Therefore, there is no need to convert the menu to YAML for CR; "menu.json" itself represents the definition in the Menu CR's spec. The "bff-server" has implemented an API to create menus using "menu.json". Let's explore the possibility of directly invoking the "bff-server" API to achieve this.


add test for fs.open with wx flag for existing file

Fixes #623

Sure, no problem.

The test is failing, expecting 'EEXIST' to equal 'ENOENT'.

You can just run npm test and it will rebuild automatically.  Did you change your test file to expect EEXIST after making that change to the implementation?
Also, can you push your changes up again and I'll review again, and help fix anything.

Yes, I made all the changes. Will push now.

Codecov Report

Merging #745 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #745      +/-   ##
==========================================
+ Coverage   86.65%   86.71%   +0.05%
==========================================
  Files          16       16
  Lines        1739     1739
==========================================
+ Hits         1507     1508       +1
+ Misses        232      231       -1

Impacted Files
Coverage Δ

src/filesystem/implementation.js
83.86% <100%> (+0.09%)
: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 914ba8b...2bf1aa7. Read the comment docs.

Concerning this

No binary for FirefoxHeadless browser on your platform.
Please, set "FIREFOX_BIN" env variable.

I noticed that I have ChromeHeadless, but not FirefoxHeadless. How are these setup? Why do I have one binary and not the other?

@cdrani do you have Firefox installed on your machine?  That should be enough to make this work.
At any rate, this looks great, nice work.  I'm going to merge.

Oh, I use the developer version. That might be the issue. Thanks for the help!


Create an HTML file that has an input form for country name

Created an html with a search bar for country name.