[SPARK-8379][SQL]avoid speculative tasks write to the same file

The issue link SPARK-8379
Currently,when we insert data to the dynamic partition with speculative tasks we will get the Exception
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.hdfs.server.namenode.LeaseExpiredException):
Lease mismatch on /tmp/hive-jeanlyn/hive_2015-06-15_15-20-44_734_8801220787219172413-1/-ext-10000/ds=2015-06-15/type=2/part-00301.lzo
owned by DFSClient_attempt_201506031520_0011_m_000189_0_-1513487243_53
but is accessed by DFSClient_attempt_201506031520_0011_m_000042_0_-1275047721_57

This pr try to write the data to temporary dir when using dynamic parition  avoid the speculative tasks writing the same file

Can one of the admins verify this patch?

Seems only affect the dynamic partition in HiveContext, @jeanlyn can you confirm that?

also met this issue when dynamic partition in HiveContext

@chenghao-intel ,I think it only affect the dynamic partition.Because SparkHadoopWriter get the write by OutputFormat.getRecordWriter,most of them use the FileOutputFormat.getTaskOutputPath to get the path

ok to test

Merged build triggered.

Merged build started.

Test build #35053 has started for   PR 6833 at commit 64bbfab.

Test build #35053 has finished for   PR 6833 at commit 64bbfab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

ok to test. Is this issue the same as the one reported in #6864? @liancheng

Merged build triggered.

Merged build started.

Test build #35171 has started for   PR 6833 at commit 64bbfab.

Test build #35171 has finished for   PR 6833 at commit 64bbfab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

i think this pr is for hiveQL and #6864 is for common SQL.

@andrewor14 They are not the same. #6864 affects dynamic partitioning feature of external data sources, while this one is about dynamic partitions of Hive.

LGTM, thanks for fixing this! Merging to master and branch-1.4.


[Slashing] Slash locked gold

Description
WIP: Ignore changes to Election as they are part of sister PR but I branched from there to test these changes

How should I go about sending gold to the community fund? Can't seem to just transfer to governance.
Sister PR https://github.com/celo-org/celo-monorepo/pull/2302 to be merged as well for dependencies
Also depending on decision in https://github.com/celo-org/celo-monorepo/pull/2302/files#r360109906 we need to make changes here.

Tested
Built minimal unit tests, really need e2e tests once everything is merged.
Haven't been able to test revoking of voting gold here because I would need to instantiate an election object in the lockedgold test or vice versa, which seems like a job better suited for an eventual e2e_slashing test.
Related issues

Fixes #2084

I'll try to add a test into test/common/integration.ts

Did you solve the issue with sending to governance? I guess you just need to make MockGovernance able to receive gold like Governance (fallback function).

Looks like the integration test broke here. Should be fixed by using the migration from https://github.com/mrsmkl/celo-monorepo/blob/test-slashing2/packages/protocol/migrations/19_governance_slasher.ts

Looks like there was some flakiness in the validators test, perhaps because the epoch number was calculated differently.


Redirect to Home

Hi
RedirectToHome has stopped working when the same user logs in multiple times a day.
Unless that's the intended effect?
Bogdan

Microsoft.AspNetCore.Authentication.AuthenticationFailureException: An error was encountered while handling the remote login.
---> Microsoft.AspNetCore.Authentication.AuthenticationFailureException: Correlation failed.
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context)
like this? I don't know why this problem occurs, maybe it is the network delay

it should be fixed


I am not able to convert my React Redux Router app into Typescript 2.7

Welcome.
I am fighting third day to convert my React Redux Router application into Typescript. I have tried so many possible tsconfig, webpack pipeline options and other tricks. Project still crash on a build with following errors:
ERROR in [at-loader] ./node_modules/enzyme-to-json/index.d.ts:1:23
    TS2688: Cannot find type definition file for 'cheerio'.

ERROR in [at-loader] ./node_modules/enzyme-to-json/index.d.ts:8:13
    TS2304: Cannot find name 'Symbol'.

ERROR in [at-loader] ./node_modules/enzyme-to-json/index.d.ts:55:40
    TS2304: Cannot find name 'Cheerio'.

ERROR in [at-loader] ./node_modules/hoist-non-react-statics/index.d.ts:4:28
    TS2694: Namespace '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index".export=' has no exported member 'ComponentType'.

ERROR in [at-loader] ./node_modules/hoist-non-react-statics/index.d.ts:5:28
    TS2694: Namespace '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index".export=' has no exported member 'ComponentType'.

ERROR in [at-loader] ./node_modules/hoist-non-react-statics/index.d.ts:6:32
    TS2694: Namespace '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index".export=' has no exported member 'ComponentType'.

ERROR in [at-loader] ./src/App.tsx:3:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/App.tsx:4:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react-dom/index"' has no default export.

ERROR in [at-loader] ./src/App.tsx:30:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:37:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:44:8
    TS2339: Property 'refs' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:49:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:53:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:57:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:61:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:65:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:69:8
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:74:54
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:88:24
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:89:23
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:90:16
    TS2339: Property 'props' does not exist on type 'App'.

ERROR in [at-loader] ./src/App.tsx:110:44
    TS2339: Property 'scrollInit' does not exist on type 'typeof "C:/xampp/htdocs/EXPERIMENTS/smooth/src/actions"'.

ERROR in [at-loader] ./src/App.tsx:120:1
    TS2539: Cannot assign to 'App' because it is not a variable.

ERROR in [at-loader] ./src/Init.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/Init.tsx:2:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react-dom/index"' has no default export.

ERROR in [at-loader] ./src/Page.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/Page.tsx:13:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/gsap/TweenMax"' has no default export.

ERROR in [at-loader] ./src/Page.tsx:26:8
    TS2339: Property 'state' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:36:8
    TS2339: Property 'setState' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:40:8
    TS2339: Property 'setState' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:44:12
    TS2339: Property 'state' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:45:12
    TS2339: Property 'props' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:51:12
    TS2304: Cannot find name 'Expo'.

ERROR in [at-loader] ./src/Page.tsx:61:12
    TS2304: Cannot find name 'Expo'.

ERROR in [at-loader] ./src/Page.tsx:76:12
    TS2339: Property 'state' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:78:12
    TS2339: Property 'props' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:84:12
    TS2304: Cannot find name 'Expo'.

ERROR in [at-loader] ./src/Page.tsx:94:12
    TS2304: Cannot find name 'Expo'.

ERROR in [at-loader] ./src/Page.tsx:109:26
    TS2339: Property 'state' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:110:12
    TS2339: Property 'state' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:110:39
    TS2339: Property 'props' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:114:23
    TS2339: Property 'props' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:115:18
    TS2339: Property 'props' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:117:11
    TS2339: Property 'state' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:128:14
    TS2339: Property 'props' does not exist on type 'Page'.

ERROR in [at-loader] ./src/Page.tsx:157:1
    TS2539: Cannot assign to 'Page' because it is not a variable.

ERROR in [at-loader] ./src/WebFont.tsx:17:18
    TS2554: Expected 1 arguments, but got 0.

ERROR in [at-loader] ./src/amalaHistoryReducer.tsx:5:42
    TS2322: Type 'string[]' is not assignable to type 'never[]'.
  Type 'string' is not assignable to type 'never'.

ERROR in [at-loader] ./src/amalaHistoryReducer.tsx:5:57
    TS2531: Object is possibly 'null'.

ERROR in [at-loader] ./src/amalaHistoryReducer.tsx:8:75
    TS2345: Argument of type 'string | null' is not assignable to parameter of type 'string'.
  Type 'null' is not assignable to type 'string'.

ERROR in [at-loader] ./src/amalaHistoryReducer.tsx:32:15
    TS2532: Object is possibly 'undefined'.

ERROR in [at-loader] ./src/amalaHistoryReducer.tsx:35:58
    TS2345: Argument of type 'any' is not assignable to parameter of type 'never'.

ERROR in [at-loader] ./src/amalaHistoryReducer.tsx:66:41
    TS2345: Argument of type 'never[]' is not assignable to parameter of type 'string'.

ERROR in [at-loader] ./src/components/AmalaLink/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/components/AmalaLink/index.tsx:8:22
    TS2339: Property 'props' does not exist on type 'AmalaLink'.

ERROR in [at-loader] ./src/components/AmalaLink/index.tsx:9:6
    TS2532: Object is possibly 'undefined'.

ERROR in [at-loader] ./src/components/AmalaLink/index.tsx:29:1
    TS2539: Cannot assign to 'AmalaLink' because it is not a variable.

ERROR in [at-loader] ./src/components/Header/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/components/Header/index.tsx:3:21
    TS2307: Cannot find module './logo.svg'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:2:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/gsap/TweenMax"' has no default export.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:8:49
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:8:92
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:11:22
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:12:21
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:13:21
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:14:38
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:15:27
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:16:24
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Scrollbar/index.tsx:19:34
    TS2339: Property 'props' does not exist on type 'Scrollbar'.

ERROR in [at-loader] ./src/components/Sidebar/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/components/Sidebar/index.tsx:2:23
    TS2307: Cannot find module 'GlobalComponents/AmalaLink'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:2:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react-dom/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:17:8
    TS2339: Property 'props' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:17:37
    TS2339: Property 'props' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:18:8
    TS2339: Property 'props' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:19:21
    TS2339: Property 'props' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:20:8
    TS2339: Property 'props' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:21:19
    TS2339: Property 'refs' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:23:15
    TS2339: Property 'props' does not exist on type 'Home'.

ERROR in [at-loader] ./src/scenes/Home/index.tsx:54:1
    TS2539: Cannot assign to 'Home' because it is not a variable.

ERROR in [at-loader] ./src/scenes/Home/scenes/Intro/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Home/scenes/Intro/index.tsx:2:20
    TS2307: Cannot find module 'GlobalComponents/Header'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Offer/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:2:23
    TS2307: Cannot find module 'GlobalComponents/AmalaLink'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:10:8
    TS2339: Property 'props' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:11:19
    TS2339: Property 'refs' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:15:8
    TS2339: Property 'props' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:16:19
    TS2339: Property 'refs' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:21:8
    TS2339: Property 'props' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:22:19
    TS2339: Property 'refs' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:29:8
    TS2339: Property 'props' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:30:19
    TS2339: Property 'refs' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/Home/scenes/Story/index.tsx:41:8
    TS2339: Property 'props' does not exist on type 'Story'.

ERROR in [at-loader] ./src/scenes/NotFound/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:2:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react-dom/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:13:8
    TS2339: Property 'props' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:13:37
    TS2339: Property 'props' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:14:8
    TS2339: Property 'props' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:15:21
    TS2339: Property 'props' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:16:8
    TS2339: Property 'props' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:17:19
    TS2339: Property 'refs' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:19:15
    TS2339: Property 'props' does not exist on type 'Reservation'.

ERROR in [at-loader] ./src/scenes/Reservation/index.tsx:47:1
    TS2539: Cannot assign to 'Reservation' because it is not a variable.

ERROR in [at-loader] ./src/scenes/Reservation/scenes/FormSection/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Reservation/scenes/FormSection/index.tsx:2:20
    TS2307: Cannot find module 'GlobalComponents/Header'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:2:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react-dom/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:13:8
    TS2339: Property 'props' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:13:37
    TS2339: Property 'props' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:14:8
    TS2339: Property 'props' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:15:21
    TS2339: Property 'props' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:16:8
    TS2339: Property 'props' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:17:19
    TS2339: Property 'refs' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:19:15
    TS2339: Property 'props' does not exist on type 'Shop'.

ERROR in [at-loader] ./src/scenes/Shop/index.tsx:47:1
    TS2539: Cannot assign to 'Shop' because it is not a variable.

ERROR in [at-loader] ./src/scenes/Shop/scenes/FormSection/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/react/index"' has no default export.

ERROR in [at-loader] ./src/scenes/Shop/scenes/FormSection/index.tsx:2:20
    TS2307: Cannot find module 'GlobalComponents/Header'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:1:8
    TS1192: Module '"C:/xampp/htdocs/EXPERIMENTS/smooth/node_modules/gsap/TweenMax"' has no default export.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:6:8
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:7:8
    TS2339: Property 'speed' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:8:8
    TS2339: Property 'ease' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:8:29
    TS2304: Cannot find name 'Power4'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:9:8
    TS2339: Property 'step' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:10:8
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:11:8
    TS2339: Property 'scrollbar' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:12:8
    TS2339: Property 'dot' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:13:8
    TS2339: Property 'animation' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:14:8
    TS2551: Property 'mouseEntered' does not exist on type 'AmalaScroll'. Did you mean 'mouseEnter'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:15:8
    TS2339: Property 'dragActive' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:16:8
    TS2339: Property 'animations' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:17:8
    TS2339: Property 'debug' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:18:8
    TS2339: Property 'pinArr' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:19:8
    TS2339: Property 'startingScroll' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:20:8
    TS2551: Property 'scrollbarY' does not exist on type 'AmalaScroll'. Did you mean 'scrollbaring'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:21:8
    TS2339: Property 'path' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:25:25
    TS2339: Property 'startingScroll' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:37:11
    TS2339: Property 'debug' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:39:23
    TS2495: Type 'HTMLCollectionOf<Element>' is not an array type or a string type.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:44:8
    TS2339: Property 'animations' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:45:27
    TS2339: Property 'pinArr' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:54:8
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:54:40
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:55:8
    TS2339: Property 'scrollbarWay' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:55:49
    TS2339: Property 'scrollbar' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:57:11
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:57:25
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:57:35
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:57:49
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:58:11
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:58:28
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:66:8
    TS2551: Property 'mouseEntered' does not exist on type 'AmalaScroll'. Did you mean 'mouseEnter'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:71:8
    TS2551: Property 'mouseEntered' does not exist on type 'AmalaScroll'. Did you mean 'mouseEnter'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:72:12
    TS2339: Property 'dragActive' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:76:21
    TS2339: Property 'scrollbar' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:77:10
    TS2304: Cannot find name 'Power2'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:83:12
    TS2551: Property 'mouseEntered' does not exist on type 'AmalaScroll'. Did you mean 'mouseEnter'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:84:22
    TS2339: Property 'scrollbar' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:85:11
    TS2304: Cannot find name 'Power2'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:92:8
    TS2339: Property 'dragActive' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:93:21
    TS2339: Property 'dot' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:94:10
    TS2304: Cannot find name 'Power2'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:107:8
    TS2339: Property 'dragActive' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:108:21
    TS2339: Property 'dot' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:109:10
    TS2304: Cannot find name 'Power2'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:123:8
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:128:34
    TS2345: Argument of type 'string | null' is not assignable to parameter of type 'string'.
  Type 'null' is not assignable to type 'string'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:129:22
    TS2339: Property 'path' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:129:35
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:134:28
    TS2339: Property 'speed' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:139:32
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:140:23
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:143:22
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:144:16
    TS2339: Property 'ease' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:145:13
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:152:8
    TS2551: Property 'scrollbarY' does not exist on type 'AmalaScroll'. Did you mean 'scrollbaring'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:153:11
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:153:25
    TS2551: Property 'scrollbarY' does not exist on type 'AmalaScroll'. Did you mean 'scrollbaring'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:153:43
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:153:57
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:153:68
    TS2339: Property 'scrollbarWay' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:156:31
    TS2339: Property 'scrollbar' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:160:22
    TS2339: Property 'timeout' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:161:9
    TS2339: Property 'timeout' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:166:21
    TS2339: Property 'scrollbar' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:167:15
    TS2339: Property 'ease' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:168:12
    TS2551: Property 'scrollbarY' does not exist on type 'AmalaScroll'. Did you mean 'scrollbaring'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:173:21
    TS2339: Property 'storageTimeout' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:174:8
    TS2339: Property 'storageTimeout' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:183:8
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:183:23
    TS2339: Property 'step' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:184:11
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:184:28
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:185:11
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:185:25
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:185:35
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:185:49
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:191:8
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:191:26
    TS2339: Property 'scrollbarWay' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:191:46
    TS2339: Property 'max' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:196:29
    TS2551: Property 'scroll' does not exist on type 'AmalaScroll'. Did you mean 'scrollTo'?

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:206:29
    TS2339: Property 'animations' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:212:19
    TS2339: Property 'assign' does not exist on type 'ObjectConstructor'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:229:30
    TS2339: Property 'speed' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:232:51
    TS2339: Property 'assign' does not exist on type 'ObjectConstructor'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:232:65
    TS2304: Cannot find name 'Power4'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:256:33
    TS2339: Property 'animations' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:257:8
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:262:32
    TS2339: Property 'animations' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:263:8
    TS2339: Property 'selector' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:267:22
    TS2339: Property 'assign' does not exist on type 'ObjectConstructor'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:307:8
    TS2339: Property 'animations' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/index.tsx:309:11
    TS2339: Property 'debug' does not exist on type 'AmalaScroll'.

ERROR in [at-loader] ./src/services/AmalaScroll/reducer.tsx:51:16
    TS2345: Argument of type 'any' is not assignable to parameter of type 'never'.

I use typescript 2.7 and React 16. Here is my webpack pipeline:
...
module: {
		rules: [
			{ test: /\.(t|j)sx?$/, use: { loader: 'awesome-typescript-loader' } },
			{ enforce: "pre", test: /\.js$/, loader: "source-map-loader" },
...

Really please for help. I can pass any other information you need to help me.
DO I need to install somany @types to my project or in current typescript version it is not required?
Greetings.

Hey there, this issue tracker isn't meant to work as a support forum. These questions tend to be better suited for StackOverflow. You may want to open a question up there instead. Sorry!
Some light advice:

Make sure you're using a lib that defines Symbol and the like in it (e.g. "lib": ["es2015", "dom"])
Make sure you have type declarations for every package in your project. Consider using https://www.npmjs.com/package/types-installer

Hi Daniel, thanks for response. Where should I add "lib": ["es2015", "dom"]? In webpack?


Is there an MVP of how to create a vitest test for a bootstrap vue next component?

Title, just looking for an MVP on how to make a vitest for a bootstrap vue next component. I couldn't find anything in the repo, or as a stackblitz (I did find an MVP for bug finding, but not for vitest). I'm having problems with testing the BDropdown component when it's being clicked, but I want to make sure that I'm not missing something obvious before I make an issue regarding it.
Thanks for your time.

Not sure it this is what you're looking for, but we do have tests that cover BDropdown being clicked - Take a look here https://github.com/bootstrap-vue-next/bootstrap-vue-next/blob/main/packages/bootstrap-vue-next/src/components/BDropdown/dropdown.spec.ts#L309

I wanted something smaller, but has a different issue. I wanted to check the effect of the click, not that the component registered that it clicked, and that's what I was having trouble with. But what you linked is probably good enough for anyone in the future who looks at the thread, so I'll go ahead and close it. Thanks!

Are you referring to adding unit tests in the library?


Performance: childList.add() vs setting .children

I've noticed that setting the children property of an element to new items can cause a large task on CPU which blocks the main thread for a while in a sync fashion.
Instead I was wondering what would be the repercussions of using childList.add() method to add each item separately (possibly wrapping it in a setTimeout so they don't all block the main thread).
Ideas?

Hi @lmatteis-wm
If you're adding many items at the same time and your platform has limited CPU resources then you indeed may experience spikes. Best approach would be to profile your app and see where the bottleneck lies and see if you can find a way to eliminate it, alternatively implement some sort of lazy loading mechanism as you suggested.
Best regards

@g-zachar indeed in many spots it seems that setting children (even a not very large list) blocks main thread:

Would you suggest other ways?

Another performance related question is that we noticed that on slower devices the internal lightning drawFrame method starts skipping frame.

Is there anyway to break this task up into chunks and/or improve it's performance? It's causing our UI to really feel laggy on slower devices.

We will also encounter this phenomenon when loading epg

@g-zachar would you have ideas regarding instantiating many components in a list? Imagine having a Tile component and doing: .children = [Tile,Tile,Tile,Tile,Tile ....]. The result is the instantiation of the same component many times causing the spike described above. An idea would be to find a way to "cache" the component instantiation to avoid the repeated processing but not sure if that's possible. Ideas?


Need to update an article to be in syc with  "Change feed in Azure Cosmos DB"

The main article about Cosmos DB Change feed (https://docs.microsoft.com/en-us/azure/cosmos-db/change-feed) was recently updated and now mentions that it is supported in all implementations but the Table API:

Although the current article "Serverless event-based architectures with Azure Cosmos DB and Azure Functions" written
last year still mentions that the support is limited to the SQL API only.
Please update.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 08ea0e9e-86ba-45be-a0c4-ea05564edf0e
Version Independent ID: a246ebd2-fe12-7e54-3a46-d62302ecf72b
Content: How to use Azure Cosmos DB change feed with Azure Functions
Content Source: articles/cosmos-db/sql/change-feed-functions.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @timsander1
Microsoft Alias: tisande

@vgarmash Thank you for the feedback. We are actively investigating and will get back to you soon.

@vgarmash Thanks for your patience. Actually these 2 articles talk about different things.
First article that you mentioned is related to Change feed which is currently supported in all APIs except Table API. Second article talks about Azure Function trigger which is currently supported in only SQL API. There is a note mentioned in the same article as well.

Please let me know if this helps or else we can discuss further.

Correct. Although if you look at the update date for the articles, you will see that the one about Change Feed itself was recently updated:
03/04/2022
but the one about functions trigger on Change Feed is updated 10/15/2021.
If I am not mistaken, until recently both articles were talking about Change Feed compatible with only SQL API. Please ask the development team of the Azure Functions if the Change Feed support is still limited to the one API or it supports more APIs.

@vgarmash Thanks for replying back.  As much as I remember, change feed has been part of the Cassandra API for a long time. The documents specific to these APIs have also been updated.
Change streams in Azure Cosmos DB’s API for MongoDB
Change feed in the Azure Cosmos DB API for Cassandra
@timsander1 Could you please confirm that the change feed is supported across APIs in Azure Cosmos DB but Table API.

@vgarmash Please let us know if above reply with the links helps you. Thanks

Those links just prove that there is a way to connect to the Cosmos DB change feed from the  JavaScript, C# or Java code directly. Although the point of this ticket is to find out if triggers for Azure Functions, written in those languages, would also work. If it true, then we need to update article "Serverless event-based architectures with Azure Cosmos DB and Azure Functions".
Did @timsander1 responded to you in-private? I don't see anything...

I can confirm that  the change feed is supported across APIs in Azure Cosmos DB but Table API.

@timsander1 Thanks for providing your inputs. Although @vgarmash question is more related if Azure Function triggers will just work for SQL API or we support them for other APIs as well. Could you please provide your inputs on that as well. Thanks

Hi @timsander1 Can you please confirm if Azure Function triggers will just work for SQL API or we support them for other APIs

Azure Functions triggers are SQL API only

Thanks @timsander1 for the confirmation.
@vgarmash Thanks for your patience. We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will reopen the issue and gladly continue the discussion.


refactor: Input message support

closes https://github.com/FuelLabs/fuels-rs/issues/650

since no one reviewed it yet, could you reset your commits so that "unnecessary" data is not part of the commit history


Completion results are sometimes slow

When completing large modules (fmt.) completion time is sometimes > 0.5 seconds, which leads to problems trying to use gocode with YCM [1].
[1] https://github.com/Valloric/YouCompleteMe/issues/742
@Valloric

I need reproducable test case for this. Typical gocode autocompletion time on fmt. is around 0.03s (30ms). Half a second is a very long time. Perhaps it's due to autobuild feature?

@nsf
You can try this python script to reproduce
import numpy as np
a = np.zeros((3,3))
At most time it takes more than 0.5s for my computer to respond to a = np..

Lol, what python has to do with gocode?

My bad, I thought it was in youcompleteme. lol

For me, completion is pretty much always slow on complex objects (github.com/docker/docker/daemon.Daemon, for example).
Not surprisingly there is tons of time spent in GC.
Attached is a flame graph as well as pprof output for alloc space.
This is from attempting completion on the above type several times as well as github.com/docker/docker/container.Container... all 2 minutes worth of capture.
gocode-profile.zip

Reproducible in C and C++ too as explained in https://github.com/Valloric/YouCompleteMe/issues/777#issuecomment-236626561. YCM is unable to cope with a large number of keys for presenting a popup menu in timely manner, where the presented menu content itself is just a small part of all the results obtained. It makes YCM slow in most slightly large codebases. The issue is very relevant in C codebases or when using C APIs where forced semantic completion of symbols in global namespace is the main usecase for semantic completion, but since the global namespace is full of symbols, YCM doesn't handle it well and responds slowly or just timeout.
It's possible that the complete_add API (or the newer async features) may help in a solution that makes partial results available for display while not all the results have been processed yet. complete_add can do it in synchronous fashion:

https://github.com/Rip-Rip/clang_complete/pull/187#issuecomment-7965909

ops, my bad, I also thought this issue was in youcomplete lol... I think it's due to youcompleme to fix this is a general way. Regarding gocode, given what I've described above, if YCM could make results available partially as eager as possible, than the issue would be due to gocode alone only if it was slow to give any results at all, since YCM could do nothing to make the results come faster in any sense.
So, if gocode is just not giving the results in timely manner, YCM can't do nothing about it, gocode must fix it. But still, there's also the issue where there are results in a fast manner from gocode, but YCM may not handle it fast when there's too much data, which is the issue I comment above and happens with C too.


Add php to the code examples in README

the first one is fine, add it to the ones I've added in the beginning, gives us nicer formatting :)

Done in https://github.com/swentel/nostr-php/pull/13

alright closing then!


Git - status bar item improvements

[x] Disable status bar items (Checkout, Sync) for the following operations: Checkout, Commit, Pull, Push, Sync
[x] Checkout status bar item

[x] Update icon based on ref type
[x] Show progress while ref is checked out

//cc @digitarald

Verification steps:

Open a folder/workspace that contains a git repository (ex: microsoft/vscode)
Use the "Git: Checkout to..." command from the command palette to:

Checkout a branch

Confirm that the status bar item contain a branch codicon

Checkout a tag

Confirm that the status bar item contain a tag codicon

Checkout detached

Confirm that the status bar item contain a commit codicon

Detached didn't work as expected, but the others did: https://github.com/microsoft/vscode/issues/172178


Add Security with real exchange (not the general one which is Market.USA) not working

Expected Behavior
After add security to srategy with initialize method, expecting to receive it's data (tick and/or bar) with OnData method.
Actual Behavior
Never calling OnData method.
Potential Solution
I'm not sure and don't understand why i have to use Market.USA when add seurity to algorithm. Maybe the problem is IQFeedDataQueueUniverseProvider.cs code files's LoadSymbols method adding all equities with Market.USA.
Reproducing the Problem

Create new algorithm.
Inside algorith class define private field.
private int _code = 100;
Inside algorith class write private method.
private void AddMarketIfNotExist(string market) {  var code = Market.Encode(market.ToLower());  if (code == null)  {      Market.Add(market, _code++);  } }
Override Initialize method and add nasdaq market.
AddMarketIfNotExist("NASDAQ");
Beucase you'll receive an error message when call AddSecurity method. First define market hours for the new market which is NASDAQ.
var entry = MarketHoursDatabase.GetEntry(Market.USA, string.Empty, SecurityType.Equity); MarketHoursDatabase.SetEntry("nasdaq", string.Empty, SecurityType.Equity, entry.ExchangeHours, entry.DataTimeZone);
Then you can add a security to algorithm.
AddSecurity(SecurityType.Equity, "AAPL", Resolution.Minute, "nasdaq", false, 0, true);
Override OnData and put breakpoint to start of the method. Run the solution and wait the first data(tick or bar, in this case tradebar).

System Information
Windows 10
IQFeed Client
Visual Studio 2019
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

@aytacasan - most US equities are listed on multiple exchanges. To help with this, there's a "logical exchange" (for want of a better word) - Market.USA, which is the one equities currently support. I believe at this point in time, only futures support the market in the way you're trying to use them

The market segmentation is based on whether the asset is fungible. e.g. Can you buy on IEX and sell on NASDAQ? Yes; so they're all under Market.USA
Perhaps @aytacasan you could zoom out a little and share what you're trying to achieve with IQFeed? You do not need to edit the markets to use Equities+IQFeed.


No module named pip on local runner

When running on our local runner (Ubuntu 20.04) I see errors that pip does not exist. Suspect this is because our systems have python3.
[action-flake8] Installing reviewdog...
reviewdog/reviewdog info checking GitHub for tag 'v0.14.0'
reviewdog/reviewdog info found version: 0.14.0 for v0.14.0/Linux/x86_64
do_ypcall: clnt_call: RPC: Unable to receive; errno = No route to host
YPBINDPROC_DOMAIN: Domain not bound
reviewdog/reviewdog info installed /tmp/reviewdog
[action-flake8] Installing flake8 package...
/usr/bin/python: No module named pip
Manual testing:
$ python -m pip install flake8
/usr/bin/python: No module named pip
$  python3 -m pip install flake8
Collecting flake8
Downloading flake8-4.0.1-py2.py3-none-any.whl (64 kB)
By installing python-is-python3 I can workaround on our machines but this will not work for environments where people need to explicitly call Python 2 and 3.
$ sudo apt install python-is-python3

@brianpaden289 Thanks for your interest in our action! I just created #36 to fix the problems you described. Can you maybe review #36 to see if it solves your problem?

I currently do not have the time to implement this. If somebody really needs it, he/she can pull #36, make the changes suggested in https://github.com/reviewdog/action-flake8/pull/36#issuecomment-1073244647 and open a new PR.


Add   and &8209; for non-breaking space and hyphen, respectively.

I found these work in Jupyter notebooks.

I don't understand what you're asking or suggesting. What do you mean by "add" them?
In case it's not clear, you can just use those entities in your Markdown and MDH will render them. Maybe that's what you want? (But make sure to use ‑ and not &8209;.)

Closing. Re-open if there's more info.


Convert models with material scripts

Original report (archived issue) by Nate Koenig (Bitbucket: Nathan Koenig).

Summary
Models that contain

The current plan is to incorporate the Material parser from https://github.com/osrf/gzweb/blob/master/gzbridge/OgreMaterialParser.cc into gz-sim to parse the default gazebo.material script so that material names for solid colors, such as Gazebo/Red can be supported. i.e, The first step would be to parse diffuse, ambient, emisive, and specular values from the material script. In the future, we might add support for textures and .material script files provided by users.
Note that The gazebo.material script will have to be installed with gz-sim.
cc @iche033


502 bad gateway

When i upload vimeo use Pyvimeo upload function at version 0.3.9
some times has a 502 bad gateway error.
so how is the problem??
vimeo side or api pyvimeo side?

Is it consistent? It was likely a temporary outage, but if you are still having issues please reach out to us at vimeo.com/help/contact.
Additionally, for future reference you can check status.vimeo.com to see if we are experiencing any outages.

is this work status.vimeo.com site.
i think that is weird.
because when i upload the vimeo use vimeo.py, raise a 502 bad gateway, but can not see status.vimeo.com site.

@Dashron could you help me.


Remote indicator in theme tester playground doesn't show theme-related commands

Testing #153318

Opened theme tester route https://insiders.vscode.dev/theme/vscode.theme-red
Click on remote indicator
Expect to see overall theme or theme tester - related commands, similar to how we see commands related to the Remote Development extensions when we select the remote indicator in desktop

The theme tester doesn't really have any command, except for 'Keep' and 'Undo'
I don't think the remote indicator is the right place for these commands.


Fields output in XML when not specified

When you specify which fields to output in XML, only those fields should be output.
In this example query, only iati-identifier should be returned:
https://test-datastore.iatistandard.org/search/activity?q=iati_identifier:(GB-CHC-274467-100843)&wt=xslt&tr=activity-xml.xsl&rows=1&fl=iati_identifier
However, last-updated-datetime, xml:lang, default-currency, humanitarian, hierarchy, linked-data-uri are output as well:

Please ensure that these fields are only output if they are specified in the query, or if the default (all fields) output is used.

using custom xls file for xml output is intended to create xml file this can be validated by iati validator. Specifying only a certain element (field) cannot produce iati validated xml file. If a user insists on getting only certain fields in xml output, default xml output option provided by Solr (wt=xml) must be used.
We will update the QueryBuiilder to enable that option.


Perform a security audit using Bandit

https://github.com/openstack/bandit

This issue was moved to Dallinger/Dallinger#165


chore: update typescript, eslint and remove microbundle

Before
After

[x] Remove microbundle that has most of the deprecated deps as peer deps. I was not sure about this one but I really couldn't find any usages of this package. As far as I. understood you need to add microbundle to the config but I couldn't see any of that in here. Please correct me if I'm wrong.
[x] Upgrade eslint packages to the ones without deprecated deps
[x] Upgrade typescript,Iäve upgraded, retested and rebuilt and I couldn't see any errors after the upgrade. Please retest/rebuild and check if it is correct

I've tested to use the components in my test app and everything still seems to work as expected.
TODO: we have one more deprecated peer dep and it will be gone after the removal of the docs. I decided to remove those in a separate PR otherwise the diff will be too big

Remove microbundle that has most of the deprecated deps as peer deps. I was not sure about this one but I really couldn't find any usages of this package.

microbundle was replaced with tsc at this point in Fabric, so yes - it should be removed! Good catch!


Docs for bazel run, FAQ, repository_rule, installs

This PR defaults the docs to the repository_rule as that is the
idiomatic way to install pods in Bazel. It adds notes about using
repository_rules, why PodToBUILD supports out of band dependency
installation, and how to bazel run the pod updates.
Generally, it isn't ideal to do source builds of programs like
PodToBUILD on a users machine for performance and build environment
coupling. This PR defaults documentation to point at binary releases.
Fixes #36

LGTM otherwise, clear readme 👍


driver doesn't handle reverse option

A reverse option is passed into here https://github.com/brimsec/zq/blob/master/driver/compile.go#L25 and then ignored.
It should be copied into the Reverse property of the proc.Context.
Looks like this was introduced in the process of refactoring the old duplicated code that turned into driver.  But ideally we should have zqd tests that would have caught this.

Note: This bug is currently responsible for the histogram being drawn incorrectly in the Brim app. For instance, a particular data set has a correct histogram that would look like this:

But in the presence of this bug, it looks like this:

Verified in Brim commit b0c5f232 talking to zqd commit a11a450. The histogram looks correct again:

Thanks @henridf!


Fail gracefully when calibrate does not converge

A model can end up taking endless amounts of time trying to fit a data. #34 will help remedy this a little bit by allowing the user to peek inside the job, but there needs to be some kind of failure instead of no return. A few tweaks that could help are

[ ] Set maximum iterations
[ ] Use global datafit

calibrate is brittle so the failures need to be normalized so they can be handled better by the HMI.

in general, it would be great if specific actionable (tying back to the input data) errors are added to the calibration output. currently when a calibration fails, it will just return a list of parameters with null values and it is up to the user to guess what caused the problem and fix it.
specifically there are certain types of errors i suspect might contribute to failure to converge, they are:

bad initial parameters settings
not enough feature mappings
dataset / model mismatch

would be great if its possible to get error messages that are helpful in narrowing down the specific cause

Not sure how relevant this issue is after the refactor. Closing for now


Algorithm can now return a list of recommended rooms

Added EmbeddedEntity functionality and created methods that allow the algorithm to run smoothly.

Closing to create new PR.


Feature Request: Add Swipe Event Callback for SelectableWeekCalendar and SelectableCalendar

Description:
Currently, the SelectableWeekCalendar and SelectableCalendar components can detect swipe gestures. However, we propose adding a new feature: a callback function for swipe events.
Feature Details:
The callback will notify developers whenever a user performs a swipe gesture on the calendar UI. It will provide information about the swipe direction (left, right, or next/previous month/week) or even better, a list of currently visible dates.
Use Cases:
The swipe event callback will enable developers to:

Implement custom actions when users swipe on specific dates or areas of the calendar.
Create intuitive gesture-based navigation between different calendar views.
Enhance the overall user experience with smooth and responsive UI interactions.

Please let me know what you think of it

I created PR for this and also for the other ticket where I asked if should we maybe keep the weekdays not scrollable since they are not changing.
https://github.com/boguszpawlowski/ComposeCalendar/pull/106
Let me know WDYT

@anvukelic  In the current state of #106 we could achieve exactly the same thing using:
 LaunchedEffect(Unit) {
    snapshotFlow {
      calendarState.monthState.currentMonth
    }.onEach { currentMonth ->
      Timber.tag("new month").d(currentMonth.toString())
    }.launchIn(this)
  }

It wouldn't require any work on the library side, and is pretty straightforward to implement on the client side. Does it fulfil your Use-case?

Closing per: https://github.com/boguszpawlowski/ComposeCalendar/issues/104#issuecomment-1694717786


Remove curl dependency from Ollama models and improve progress bar

Resolves #115
Example run:
(venv) ramalama (feat*) $ python ramalama.py pull ollama://tinyllama
Pulling tinyllama/latest: 100% ▕####################▏ 852/852 2.47MB/s 00:00
Pulling<PHONE_NUMBER>245362: 100% ▕####################▏ 483/483 753kB/s 00:00
Pulling 83e42c043d6c7816:  22% ▕####4               ▏ 134M/608M 4.57MB/s 01:48

Nice...
We should probably add this to the Containerfile in this repo also for Linux...
And if you could hardcode whatever version of tqdm you are on in the pip install that would be great... Our container builds run nightly, don't want them to sporadically break due to a tqdm upgrade.

We should also try to remove curl everywhere, so we only have a dependency on one http client

Sure, I'm trying to figure out why these tests are failing.
I'll add the the same in the Containerfile and will remove curl everywhere. If I'm not wrong the only curl we are using after this is in the install.py's download(url, to) function.

I think this should fix CI:
https://github.com/containers/ramalama/pull/121
container build must be run first, so everything has access to new python modules like tqdm

Thanks, I will add check=True in the subprocess.run command for tqdm once the above PR is merged.

I merged the other one to unblock you, rebase should hopefully fix it

I rebased but the test still failed unfortunately

@swarajpande5 I think if you put download into it's own download.py file, it should be fine.
We call some python code outside the container and some inside the container.
Creating download.py or something similar will ensure we only need this python module inside the container.

Or maybe actually just put it in ollama.py file, it's only relevant there anyway...

Sure, sounds good!

You'll need to add:
subprocess.run(["pip3", "install", "--break-system-packages", "tqdm==4.66.5"], check=True)

to install.py for macOS build @swarajpande5

@swarajpande5 I think you can import inside a function call on in python too, I dunno if that helps you here...

@ericcurtin I have already called the subprocess.run() for tqdm in install.py. Yeah, importing tqdm in the function wherein its required sounds really good. I'll make this change.

@swarajpande5 I see your issue now...
We should have no dependancy on tqdm in install.py , just in the actual ramalama application itself is where we want to use tqdm.
It's ok to use curl in the install.py. We can't have dependancies in install.py that aren't on a base macOS operating system already.

@ericcurtin I have not added tqdm as a dependency in install.py. I have removed the curl dependency in download(url, to) of install.py without using tqdm. Can you please check again, thanks.

@ericcurtin As per your suggestion I have reverted the download(url, to) function in install.py to using curl. If in future, we decide to fully remove curl, then we can add the implementation back.

What is going on with this PR?

@rhatdan So I'm still working on this. Trying to resolve the ci tests on macos, thinking to either write a basic implementation of a macos image. Would give some more time on this weekend.

@rhatdan what is nice about the hard-coded versions... Is since @swarajpande5 kindly added the renovate support... It will auto-detect newer versions... But not only that, it runs everything through a CI build before updating a given version... There is some value in having renovate automatically run a CI build before we press the button to update the version...

LGTM
Thanks @swarajpande5


Same Content used.

URL - https://ourworld.tf/platform/
Same content is used for Layer 1 and Layer 2
LAYER ONE
THE GRID
Creator Zones are dedicated to building super-sustainable coworking and co-living communities where entrepreneurs, digital nomads and residents collaborate to build beautiful experiences that positively impact the lives of millions.
LAYER TWO
EXPERIENCES
Creator Zones are dedicated to building super-sustainable coworking and co-living communities where entrepreneurs, digital nomads and residents collaborate to build beautiful experiences that positively impact the lives of millions.

https://github.com/threefoldfoundation/www_ourworld_tf/commit/3b18ccaeee425b49d80289493170c7eac0ef3f22


Cannot install packages using Node.js 22 on windows-latest runners

Description:
If you set node-version to 22 on a GitHub-hosted windows-latest runner, commands like npm ci fail with the following error message:
node:internal/modules/cjs/loader:1205
  throw err;
  ^
Error: Cannot find module 'C:\npm\prefix\node_modules\npm\bin\npm-cli.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1202:15)
    at Module._load (node:internal/modules/cjs/loader:1027:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:187:14)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
Node.js v22.0.0

Action version:
v4
Platform:

[ ] Ubuntu
[ ] macOS
[x] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Tools version:
node: v22.0.0
npm: 10.5.1
yarn: 1.22.22
Repro steps:
See https://github.com/lpsinger/nodejs-22-windows
Expected behavior:
Build should pass
Actual behavior:
Build fails. See this workflow run: https://github.com/lpsinger/nodejs-22-windows/actions/runs/8881922941/job/24385408488

Hello @lpsinger, Thank you for creating this issue and we will look into it :)

I believe I'm having the same issue here: https://github.com/express-rate-limit/express-rate-limit/actions/runs/8900764596/job/24445327662 - that commit was a documentation-only change and the previous build passed.

I'm having the same issue, any ideas on a eta to fix this will block all my windows builds that need to use node 22

This is a problem with Node itself https://github.com/nodejs/node/issues/52682

Looks like this is now fixed with node.js 22.1.0 and npm 10.7.0 - https://github.com/express-rate-limit/express-rate-limit/actions/runs/8900764596


add guestbook example

The example contains guestbook rc & svc, redis-master/slave rc & svc

On phone but you might be interested in some of the examples we're starting to flesh out: https://github.com/ksonnet/ksonnet-lib/tree/sigapps/ksonnet.beta.2

Ok, so, I'm thinking that probably we will want to not add more examples of beta.1 since we'd like to deprecate it in favor of beta.2. What are your thoughts on this?

@hausdorff yes thanks I will try the beta.2 with guestbook and give you feedback

closing due to inactivity


buffer shape incompatible with memoryview shape

This code fails to compile for me:
def test(double[a, object[double, ndim=2](:,:]) b):
    if a.shape != b.shape:
        print("shape differs")

Error compiling Cython file:
------------------------------------------------------------
def test(double[a, object[double, ndim=2](:,:]) b):
    if a.shape != b.shape:
       ^
------------------------------------------------------------
mvtest.pyx:2:8: Cannot convert 'Py_ssize_t [8]' to Python object

The error is that the shape field of the memory view is a C array that cannot be converted to a Python object in order to compare it to the shape of the buffer, which is a Python tuple.
The underlying problem is that Cython does not know that the shape field of a buffer is just a C array as well. Instead, it looks it up as a Python attribute and unpacks it as a Python tuple.
Migrated from http://trac.cython.org/ticket/780

I'll mark this as a duplicate of #4321.

I'll mark this as a duplicate of #4321.


[yasm-tool:x64-windows] build failure

Host Environment

OS: Windows 10 Home Build 19042
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install yasm-tool:x64-windows
Failure logs
Starting package 1/1: yasm-tool:x64-windows
Building package yasm-tool[core]:x64-windows...
CMake Error at scripts/cmake/vcpkg_fail_port_install.cmake:97 (message):
  The yasm-tool port is only intended to be built for x86 Windows

  Architecture 'x64' not supported by yasm-tool!

Call Stack (most recent call first):
  ports/yasm-tool/portfile.cmake:1 (vcpkg_fail_port_install)
  scripts/ports.cmake:142 (include)

Error: Building package yasm-tool:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: yasm-tool:x64-windows
  Vcpkg version: 2021-01-13-d67989bce1043b98092ac45996a8230a059a2d7e

Additional context
This error initially popped up when trying to install the gmp package and so I attempted to install yasm-tool:x64-windows to reproduce the error. Furthermore, attempting to install yasm-tool:x86-windows yields no errors

The same issue. When I try to install gmp:x64-windows, the vcpkg will try to install yasm-tool:x64-windows and fail. (and I have installed yasm-tool:x86-windows)

Duplicated to https://github.com/microsoft/vcpkg/issues/17584, but I prefer to track this issue here.

cc @BillyONeal

Are we still having issues with yasm?
Our environment shows:
yasm -a help
Available yasm architectures:
x86         x86 (IA-32 and derivatives), AMD64
lc3b        LC-3b

Are we still having issues with yasm?

It is still very flaky. @strega-nil was working on changing it to use host ports in #16478


Document Issues with Lua's length operator "#"

Added to the wiki here: https://github.com/Perryvw/TypescriptToLua/wiki/Differences-between-Lua-and-Javascript


precise_ip is incorrectly initialized

With gcc 7.3.1, I get the following error
../../../../src/tool/hpcrun/sample-sources/perf/perf-util.c: In function 'perf_util_attr_init':
rm -f libhpcrun_ga_wrap.a
../../../../src/tool/hpcrun/sample-sources/perf/perf-util.c:434:23: warning: 'precise_ip' may be used uninitialized in this function [-Wmaybe-uninitialized]
   attr->precise_ip    = precise_ip;

Below is the code. The compiler is correct. There is a problem for the PERF_EVENT_AUTODETECT_SKID case. Please fix and commit to master.
  u64 precise_ip;

  switch (precise_ip_type) {
    case PERF_EVENT_AUTODETECT_SKID:
            perf_skid_set_max_precise_ip(attr);
            break;
    case PERF_EVENT_SKID_ERROR:
    case PERF_EVENT_SKID_ARBITRARY:
            // check the HPCRUN_PRECISE_IP env variable
            precise_ip = perf_skid_get_precise_ip(attr);
            break;
    default:
            precise_ip = precise_ip_type;
  }

  attr->precise_ip    = precise_ip;

  return true;

Note: I see this compiler error on arm1.

You're right. I didn't see that.
I'll fix it.
Laksono Adhianto
On Tue, Oct 30, 2018 at 8:04 AM John Mellor-Crummey <
<EMAIL_ADDRESS>wrote:

With gcc 7.3.1, I get the following error
../../../../src/tool/hpcrun/sample-sources/perf/perf-util.c: In function 'perf_util_attr_init':
rm -f libhpcrun_ga_wrap.a
../../../../src/tool/hpcrun/sample-sources/perf/perf-util.c:434:23: warning: 'precise_ip' may be used uninitialized in this function [-Wmaybe-uninitialized]
attr->precise_ip    = precise_ip;
Below is the code. The compiler is correct. There is a problem for the
PERF_EVENT_AUTODETECT_SKID case. Please fix and commit to master.
u64 precise_ip;
switch (precise_ip_type) {
case PERF_EVENT_AUTODETECT_SKID:
perf_skid_set_max_precise_ip(attr);
break;
case PERF_EVENT_SKID_ERROR:
case PERF_EVENT_SKID_ARBITRARY:
// check the HPCRUN_PRECISE_IP env variable
precise_ip = perf_skid_get_precise_ip(attr);
break;
default:
precise_ip = precise_ip_type;
}
attr->precise_ip    = precise_ip;
return true;
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/HPCToolkit/hpctoolkit/issues/116, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIX86KbJFgPBoUO7OaP1aYYgEfqtqjC5ks5uqE5ggaJpZM4YB3qq
.


[Bug]: Caddy handle_path label doesn't strip the path

Error Message and Logs
According to the caddy documentation the handle_path directive should strip the path and handle directive should keep the path when reverse proxying request to containers but in my case it's working the reverse. I replaced the handle_path  labels with handle labels and it working fine. Isn't is opposite of what the Caddy documentation says? Or am I missing something.
Background
I've backend application deployed at the /api path as in www.example.com/api. I'm using the original container labels. Here is the snippet:
caddy_0.encode=zstd gzip
caddy_0.handle_path.0_reverse_proxy={{upstreams 3000}}
caddy_0.handle_path=/api/*
caddy_0.header=-Server

I already have /api path prefixed on my backend. Since the the path from proxy was not getting stripped off I had to use /api/api/[controller] to get to the APIs.
Steps to Reproduce

I'm using spring boot deployed at my domain at /api path
I'm leaving the container labels untouched

Example Repository URL
No response
Coolify Version
v4.0.0-beta.355
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
No response
Additional Information
No response

This should be fixed in the next update as soon as it is released, please retest this.


pen test subcommand without Test package

Close #710.

Codecov Report

Merging #714 (7d616f2) into main (724d973) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #714   +/-   ##
=======================================
  Coverage   85.83%   85.83%
=======================================
  Files         308      308
  Lines       28719    28719
=======================================
  Hits        24650    24650
  Misses       4069     4069

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 724d973...7d616f2. Read the comment docs.


Inline attr. macro docs and fix links

This makes cortex-m-rt-macros purely an implementation detail, so I've put a warning in place to reflect that.
This should close https://github.com/rust-embedded/cortex-m-rt/issues/138

r? @adamgreig
(rust_highfive has picked a reviewer for you, use r? to override)

bors r=therealprof


Add test bench type multi_set / multi_get

For our business, we found version 2.4 interface mutli_get & multi_get performance to be lower than 2.0.
So we need add bench type multi_get/multi_set test it.

how about adding a benchmark test in the CI pipeline?

how about adding a benchmark test in the CI pipeline?

+1, and we have to make sure the performance of the machine running CI is stable.


List desynchronization detected!

The thread it told me to go to was marked closed but I've had several crashes trying to use this program so far with this error. I have to save after every single image now, very frustrating. I don't think I did anything weird, just trying to add tags, but sometimes I fumble with the keybinds (my hand is getting sore from ctrl e).
(Not a bug but I also lost a lot of progress by UI confusion/user error before, I clicked 'set current tag to all images' thinking it would just ADD the actual currently selected SINGLE tag to all images' tag lists, instead it REPLACED all images' tags with ALL the tags on the current picture... and undo couldn't undo it cries)
ErrorData.json

Discussed in https://github.com/starik222/BooruDatasetTagManager/discussions/111

Originally posted by starik222 January 11, 2024
This topic was created to post logs created when the "List desynchronization detected!" error occurred. You need to attach the "ErrorData.json" file from the program folder and, if possible, describe what actions caused this error.

Are you using the latest version of the program? This error has been fixed and there have been no other error messages except yours. If you are indeed using the latest version of the program, please send me some more ErrorData.json, as I can't figure out the cause of the error yet.
If you find the current keyboard shortcuts inconvenient, you can reconfigure them for yourself in the settings menu.

Not confirmed.

Fixed in 2.3.1