unable to publish even simple LUIS bots in bot composer V1.1.1

Hello there, my partner and I have run into an issue when trying to deploy our first bots.
After following the tutorial on Microsoft's web page (to make a weather bot) we have been unable to get it to publish. The Luis account works in composers emulator, but when we try to push in publishing it comes up with the error.
The log shows the same (or similar) error:
Publish starting... {   "status": "DEPLOY_INFO",   "message": "C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\interuption\\Cancel.en-us.lu loaded\n" } {   "status": "DEPLOY_INFO",   "message": "C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\interuption\\GetWeather.en-us.lu loaded\n" } {   "status": "DEPLOY_INFO",   "message": "C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\interuption\\help.en-us.lu loaded\n" } {   "status": "DEPLOY_INFO",   "message": "C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\interuption\\weatherbot.en-us.lu loaded\n" } {   "status": "DEPLOY_INFO",   "message": "C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\interuption\\weatherbot.en-us.lu no changes\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\weatherbot.en-us.lu.dialog\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\weatherbot.lu.dialog\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\Cancel.lu.qna.dialog\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\GetWeather.lu.qna.dialog\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\help.lu.qna.dialog\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\weatherbot.lu.qna.dialog\n" } {   "status": "DEPLOY_INFO",   "message": "Writing to C:\\Users\\Otter\\AppData\\Roaming\\BotFrameworkComposer\\publishBots\\5fc68681cb5057b653b63f12dd99d431\\azurefunctions\\ComposerDialogs\\generated\\luis.settings..westus.json\n" } {   "status": "DEPLOY_INFO",   "message": "lubuild succeed" } {   "status": "DEPLOY_INFO",   "message": "start publish luis" } {   "status": "DEPLOY_ERROR",   "message": "{\"name\":\"StatusCodeError\",\"statusCode\":400,\"message\":\"400 - \\\"{\\\\r\\\\n  \\\\\\\"error\\\\\\\": {\\\\r\\\\n    \\\\\\\"code\\\\\\\": \\\\\\\"BadArgument\\\\\\\",\\\\r\\\\n    \\\\\\\"message\\\\\\\": \\\\\\\"The source completed without providing data to receive.\\\\\\\"\\\\r\\\\n  }\\\\r\\\\n}\\\"\",\"error\":\"{\\r\\n  \\\"error\\\": {\\r\\n    \\\"code\\\": \\\"BadArgument\\\",\\r\\n    \\\"message\\\": \\\"The source completed without providing data to receive.\\\"\\r\\n  }\\r\\n}\",\"options\":{},\"response\":{\"statusCode\":400},\"stack\":\"StatusCodeError: 400 - \\\"{\\\\r\\\\n  \\\\\\\"error\\\\\\\": {\\\\r\\\\n    \\\\\\\"code\\\\\\\": \\\\\\\"BadArgument\\\\\\\",\\\\r\\\\n    \\\\\\\"message\\\\\\\": \\\\\\\"The source completed without providing data to receive.\\\\\\\"\\\\r\\\\n  }\\\\r\\\\n}\\\"\\n    at new StatusCodeError (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\build\\\\plugins\\\\azurePublish\\\\node_modules\\\\request-promise-core\\\\lib\\\\errors.js:32:15)\\n    at Request.plumbing.callback (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\build\\\\plugins\\\\azurePublish\\\\node_modules\\\\request-promise-core\\\\lib\\\\plumbing.js:104:33)\\n    at Request.RP$callback [as _callback] (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\build\\\\plugins\\\\azurePublish\\\\node_modules\\\\request-promise-core\\\\lib\\\\plumbing.js:46:31)\\n    at Request.self.callback (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\build\\\\plugins\\\\azurePublish\\\\node_modules\\\\request\\\\request.js:185:22)\\n    at Request.emit (events.js:210:5)\\n    at Request.<anonymous> (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\build\\\\plugins\\\\azurePublish\\\\node_modules\\\\request\\\\request.js:1154:10)\\n    at Request.emit (events.js:210:5)\\n    at IncomingMessage.<anonymous> (C:\\\\Program Files\\\\Bot Framework Composer\\\\resources\\\\app.asar.unpacked\\\\build\\\\plugins\\\\azurePublish\\\\node_modules\\\\request\\\\request.js:1076:12)\\n    at Object.onceWrapper (events.js:299:28)\\n    at IncomingMessage.emit (events.js:215:7)\\n    at endReadableNT (_stream_readable.js:1183:12)\\n    at processTicksAndRejections (internal/process/task_queues.js:80:21)\"}" } 400 - "{\r\n  \"error\": {\r\n    \"code\": \"BadArgument\",\r\n    \"message\": \"The source completed without providing data to receive.\"\r\n  }\r\n}"`
We figured this may be some sort of access issue to azure, but have tried from different access tokens (both generated in azure CLI and Azure Cloud Shell) and from both users (both have owner privileges) but this is an error we receive if we try to provision new resources, or use existing ones.
We have managed to publish bots using regex with no issues, it seem to be any we do with LUIS any help to shed light on this matter would be greatly appreciated!

@dmvtech can you investigate this issue? Thanks!

@philip-mc Do you have both authoring and prediction resources setup in Azure already? And are you providing keys for both of those in the publishing settings? Also be sure to make sure the LUIS region is correct.

hello and thanks for getting in touch. We have both authoring and prediction keys set up in azure both through manual npm install, node composer provisioner as per the tutorials as well as doing so manually as well. We have also tried a few different regions, Us west was the original default, but based on some contact with others in similar situations we did also try setting everything up in the same region as our tenant and still not working. we have tried generating access tokens through both my partner (azure owner) and myself (admin with privileges) and neither work.
We can do regex but as soon as we try for Luis it stops working.
Emulation works fine on local, contacting Luis and replying via Luis trace v3

@philip-mc Thank you. Very strange. Not sure what is going and I'm not able to reproduce.
@luhan2017 @cwhitten @tdurnford Any ideas here? I'm not familiar with the error the source completed without providing data to receive or what could causing it. Anything else to check for?

@philip-mc I've replied you through #4395, this error is caused by this API, https://westus.dev.cognitive.microsoft.com/docs/services/5890b47c39e2bb17b84a55ff/operations/5be313cec181ae720aa2b26c/console, if the access-token and authoring key are both correct, and it still not works, could you please help submit a ICM ticket to luis team referring to this doc? https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request. It is the best way to get their attention and have them prioritized for this.

I am closing this issue as it is related to LUIS and not Composer. Feel free to reopen if you determine that is not the case.

@philip-mc you were able to contact support?

yes, sorry for the long delay we have run into further errors non-related to this direct issue. Contacting the luis team (we had to upgrade to development help and support to send a ticket), they proceeded to trace our attempts to gather a token and it turns out all tokens where trying to generate through an old legacy subscription despite setting the subscription!
Upon further investigation it seems the old subscription we had "Access to azure active directory" was broken and we had no permissions to do anything with it. finding this link here - https://www.jasonfritts.me/2020/04/07/what-is-the-access-to-azure-active-directory-subscription-for/ we found it could possibly be removed from the subscription by contacting Microsoft support.
Whilst we await the subscriptions removal, I found that dropping my azure admin privileges to a contributor took me off the legacy tenant. For people with only one admin, possibly creating an extra account with 'contributor' and only access to the subscription you want may be of help, as it certainly was for us.
By having a user without access to the broken subscription we where able to generate an arm token and successfully publish a bot on azure.


config: Change default write mode to overwrite

This pull request is to get an idea of what the blockers are for trusting rustfmt to overwrite by default.

I think this is the way forward, but I don't think we should change from emitting backups to not doing so in one big step. Perhaps we should warn users with a message for a few weeks and then change? Not really sure about the best way to do it - any ideas?

One thing I've been thinking: introduce a global config similar to ~/.gitconfig, which can have a write-mode setting. Probably write-mode is the only thing that makes sense there so far: I don't like the idea of rustfmt formatting differently with the same project config file. Allowing formatting settings in there would let that happen.
The process could then be:

add facility to lookup global config, and respect any write-mode setting contained therein
start to warn users who do not have a global config with write-mode that it will change soon
switch default write-mode to overwrite

We could get inspiration from how git changed the push.default setting in 2.0:
warning: push.default is unset; its implicit value is changing in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the current behavior after the default changes, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

I think they keep the warning until you set the setting though, which we may not want to do.

re ~/.gitconfig, see also #837

I like the idea of this approach (following the git push change). I think that to start with the global/per-user config file should be separate from the per-project file, i.e., have completely separate options with different names and the file should have a different name. Then we don't need to worry about whether the per-user or per-project file takes precedence, etc. We can just use it for stuff like this.

Great! This PR has served its purpose with finding the way forward. I'm closing it and have opened #871.


fault tolerance

It is common to have multiple service providers for a service in a cluster. Some of these service providers may have a network, configuration, a long fullgc, a full thread pool, a hardware failure, etc. The long connection is alive but the program is not responding properly. This functionality demotes the service provider for this part of the exception. This feature solves the problem of service failures that continue to affect the business and avoids the avalanche effect. The long response time required by manual intervention can be reduced and the system availability can be improved.
The core logic of this function is referred to from sofa-rpc, which has been used in many large-scale scenarios with good results.

Codecov Report

Merging #1148 into master will decrease coverage by 0.40%.
The diff coverage is 15.81%.

@@            Coverage Diff             @@
##           master    #1148      +/-   ##
==========================================
- Coverage   56.15%   55.75%   -0.41%
==========================================
  Files         268      274       +6
  Lines       25415    25668     +253
==========================================
+ Hits        14272    14310      +38
- Misses       9779     9991     +212
- Partials     1364     1367       +3

Impacted Files
Coverage Δ

pkg/config/v2/filter.go
50.00% <ø> (ø)

...ream/faulttolerance/regulator/default_work_pool.go
0.00% <0.00%> (ø)

...olerance/regulator/invocation_dimension_factory.go
0.00% <0.00%> (ø)

...aulttolerance/regulator/invocation_stat_factory.go
0.00% <0.00%> (ø)

...r/stream/faulttolerance/regulator/measure_model.go
15.46% <15.46%> (ø)

...stream/faulttolerance/regulator/invocation_stat.go
22.03% <22.03%> (ø)

...ream/faulttolerance/regulator/default_regulator.go
54.54% <54.54%> (ø)

pkg/module/http2/server.go
81.70% <0.00%> (-0.15%)
:arrow_down:

pkg/module/http2/transport.go
78.47% <0.00%> (ø)

... and 5 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #1148 into master will increase coverage by 0.27%.
The diff coverage is 69.01%.

@@            Coverage Diff             @@
##           master    #1148      +/-   ##
==========================================
+ Coverage   56.19%   56.47%   +0.27%
==========================================
  Files         268      284      +16
  Lines       25415    26244     +829
==========================================
+ Hits        14281    14820     +539
- Misses       9772    10010     +238
- Partials     1362     1414      +52

Impacted Files
Coverage Δ

pkg/config/v2/filter.go
50.00% <ø> (ø)

...ilter/stream/faulttolerance/send_filter_factory.go
3.44% <3.44%> (ø)

...olerance/regulator/invocation_dimension_factory.go
23.52% <23.52%> (ø)

...stream/faulttolerance/regulator/invocation_stat.go
78.33% <78.33%> (ø)

pkg/filter/stream/faulttolerance/send_filter.go
81.48% <81.48%> (ø)

...ream/faulttolerance/regulator/default_regulator.go
81.81% <81.81%> (ø)

...aulttolerance/regulator/invocation_stat_factory.go
85.00% <85.00%> (ø)

...ream/faulttolerance/regulator/default_work_pool.go
88.63% <88.63%> (ø)

...r/stream/faulttolerance/regulator/measure_model.go
88.65% <88.65%> (ø)

...ilter/stream/faulttolerance/util/calculate_util.go
100.00% <100.00%> (ø)

... and 33 more

Continue to review full report at Codecov.

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


Fix bug create account roles with existing policies

Related: https://issues.redhat.com/browse/SDA-7656
Create managed account roles:

Create unmanaged account roles:

@zgalor @gdbranco PTAL

/lgtm


processing improvement

processing improvement.
it could be cool to have the same number of picture in processing background and number of taken picture.
Generate thumbnail and show in the processing screen
Describe the solution you'd like
perhaps we can make different background and call them.
it's just to be perfect. but it can be difficult with raspi
Many thanks for your hard work on pibooth

the same number of picture

Not sure this would work with only one picture

Generate thumbnail and show in the processing screen

My main worry would be that the Raspberry Pi is already working a lot at this screen, making is work on another thing that generating the picture would increase the processing time.
I have another idea though, maybe we could put in the processing screen the image generated previously, as they are already generated it may be possible to add them at a lower cost. What do you think @anxuae ?

It is possible to generate Thumbnail using PIL:
image = Image.open(data)
image.thumbnail((36,36), Image.NEAREST)

However, we designed pibooth to be an embedded software in  the raspberry-pi. Some tests could be done to ensure that the processing period is not too much extended. But my guess is that current version of raspberry pi is not enough powerful.

ok, perhaps we can generate thumbnail in background during waiting from main screen ?


Flutter Post request with headers and body not working properly ?

D/SharedPreferencesImpl( 9900): Time required to fsync /data/user/0/com.example.firebase_demo/shared_prefs/com.google.android.gms.measurement.prefs.xml: [<1: 0, <2: 0, <4: 0, <8: 1, <16: 0, <32: 0, <64: 0, <128: 0, <256: 0, <512: 0, <1024: 0, <2048: 0, <4096: 1, <8192: 0, <16384: 0, >=16384: 0]
I/flutter ( 9900): 404
I/flutter ( 9900): final error : jaym {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}

Code :
fetchDataFromServer() async {
    var body = {
      'per_page': 5,
      'since': 0,
    };
    var headers = {
      'content-type': 'application/json'
    };

    try {
      var response = await
      var response = await http.post("https://api.github.com/users",headers:headers,body: json.encode(body));
      print(response.statusCode);

      if (response.statusCode == 200) {
        print("body : ${response.body}");
        print("json : ${json.decode(response.body)}");
      } else{
        print("final error : jaym " +response.body);
      }
    } catch (error) {
      print("error : ${error}");
      print("error : ${error.toString()}");
    }
  }

@zoechi  I don't find any issue in my code. I have already checked many forums. Suggest a hint if possible.
Thanks.

hi,
you don't need  json.encode(body)
just pass the body

hi,
you don't need json.encode(body)
just pass the body

But, It says " type 'int' is not a subtype of type 'String' in type cast".

var body = {
'per_page': '5',
'since': '0',
};
you know what field is int and what is not. you can do the conversion on the server side

var body = {
'per_page': '5',
'since': '0',
};
you know what field is int and what is not. you can do the conversion on the server side

If i am doing you suggest still it gives me error code 404 with error "{"message":"Not Found","documentation_url":"https://developer.github.com/v3"}"

wrong url, https://api.github.com/user not users
you need also to authenticate

@superciccio i don't want particular user. I want the list of user. So this is the correct url for my requirements.

post is not allowed, get is.
:)

Please ask such questions on stackoverflow , because we unfortunately not able to give individual development support here.
This place is only for reporting bugs or suggesting new features.

Please ask such questions on stackoverflow , because we unfortunately not able to give individual development support here.
This place is only for reporting bugs or suggesting new features.

every newcomer facing the kind of problems. That's why It needs some documentation or FAQ pages for newcomers. It is not mature framework and people need more support. I don't mind @JayM96 and others use the GitHub repos as StackOverflow. This is a real problem day by day developers facing. It is not a type of question for example: "I need a create auth system but I don't know how to create it and so on.".

The same problem happened to me, in the Postman everything ok, but in flutter it was the error two days of loss that I could finally solve here I leave the example and it is ok in flutter
`import 'dart:convert';
import 'package:http/http.dart' as http;
Future suscribeAdd(String name, String email) async {
var client = http.Client();
try {
var url = "http://localhost:2200/suscribe";
var headers = {'Content-Type': 'application/json; charset=UTF-8'};
var body = {'name': name, 'email': email};
var response =
await client.post(url, headers: headers, body: json.encode(body));
return response.body;
} catch (error) {
return null;
}`

The same problem happened to me, in the Postman everything ok, but in flutter it was the error two days of loss that I could finally solve here I leave the example and it is ok in flutter
import 'dart:convert';
import 'package:http/http.dart' as http;
Future suscribeAdd(String name, String email) async {
var client = http.Client();
try {
var url = "http://localhost:2200/suscribe";
var headers = {'Content-Type': 'application/json; charset=UTF-8'};
var body = {'name': name, 'email': email};
var response =
await client.post(url, headers: headers, body: json.encode(body));
return response.body;
} catch (error) {
return null;
}


SPOI-6032 #resolve #comment when a method has no comments and only om…

…itFromUI tag than the super class method info was being used

@siyuanh
Please review and merge


Context precision with ground truth

#365 fixes

@yuukidach Hey, I would love to know your thoughts on my approach here.

@shahules786 It's really not easy to merge two PRs. I think we can directly adopt yours. I'll closed my PR.

In this PR, there is another metric for dataset with out gt. This makes prompt tuning more convenient
Since the prompt are simpler ans shorter, the running time can also be faster.

And for the evaluation of context_relevancy, I agree with your idea. There is a high probability that using GT/Answer can also improve the effect.
BTW, when tuning the prompt, I found that a suitable prompt is still very important in the evaluation process. Will Ragas consider let users to use our own prompts or provide a module that automatically tuning prompt like https://arxiv.org/abs/2309.03409


Doesn't work?

I don't know why, but if I run this method on a <div> with a bunch of unicode emoji in it, they don't change to images:

... That's in Internet Explorer. In Chrome on Mac, they appear as actual emoji (since that's supported) but don't change to <img> tags there either. — No errors appear in the console, so I don't know what's wrong. Is this supposed to work?

OK... I'll take that as a "no".
I can't get this to work in any modern browser.

Same here

Cannot get it to work full stop nothing happens.


feat: Standalone calldata test

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

note_successful_decrypting_time_in_ms (8): 619 (+66%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit e8936754 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
223,080
868,292
3,449,756

l1_rollup_execution_gas
867,189
3,746,345
23,306,521

l2_block_processing_time_in_ms
1,456 (+6%)
5,171 (+2%)
21,472 (+5%)

note_successful_decrypting_time_in_ms
:warning: 619 (+66%)
1,150 (+2%)
4,301 (+4%)

note_trial_decrypting_time_in_ms
28.2 (-69%)
37.2 (-29%)
141 (+1%)

l2_block_building_time_in_ms
14,956
59,528
238,917

l2_block_rollup_simulation_time_in_ms
10,612
42,163
170,304

l2_block_public_tx_process_time_in_ms
4,313 (+1%)
17,191 (+1%)
68,323 (+1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,273 (+1%)
28,983

note_history_successful_decrypting_time_in_ms
2,664 (-5%)
5,401

note_history_trial_decrypting_time_in_ms
83.8 (-3%)
144 (+1%)

node_database_size_in_bytes
3,615,374
3,714,174

pxe_database_size_in_bytes
29,923
59,478

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
210
44,709
25,561

private-kernel-ordering
137 (+1%)
30,953
14,809

base-rollup
1,074
128,374
881

root-rollup
82.7 (+1%)
4,088
889

private-kernel-inner
287
71,236
25,561

public-kernel-private-input
202
31,891
25,561

public-kernel-non-first-iteration
200 (+1%)
31,933
25,561

merge-rollup
9.80 (+1%)
2,608
881

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
15,487
31,879


I have to have a GPU, right?

Can I do a multi-video pipeline without a GPU?

If you want to use this project without using GPU,  need to rewrite InferInstance yourself
The example in project is TRT

@1461521844lijin
Forgive me for asking about your project without running it yet, but I was wondering if I could take the openvino model and integrate it into the multi-pipeline you have implemented.

@1461521844lijin Forgive me for asking about your project without running it yet, but I was wondering if I could take the openvino model and integrate it into the multi-pipeline you have implemented.

Yes, you can refer to the example of ‘YoloDetectionInfer.cpp’ in the project to rewrite an openvino instance.


Extension install is failing for multiple customers

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.68.1
OS Version: Windows

Steps to Reproduce:

Have VS code already running
Get update to the Jupyter extension
Extension does not install correctly

See these two issues:
https://github.com/microsoft/vscode-jupyter/issues/9967
https://github.com/microsoft/vscode-jupyter/issues/10629
I believe there have been other instances of this in the past. The install of the extension does not unzip everything for some reason.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

@Elisa-code184 Thanks for the logs.

[2022-07-10 17:23:33.497] [sharedprocess] [info] Extension installed successfully: ms-toolsai.jupyter

It seems extension got installed successfully

[error] [uncaught exception in sharedProcess]: Si è verificato un errore di sistema (ENOENT: no such file or directory, scandir
'C:\Users\Elisa\AppData\Roaming\Code\clp\c214013558c0237a1b875ec703f18888.it'): Error: ENOENT: no such file or directory, scandir 'C:\Users\Elisa\AppData\Roaming\Code\clp\c214013558c0237a1b875ec703f18888.it'

This error does not seem to be related to extension installation, what are you seeing in VS Code after installing the extension? Are you seeing any error prompt, do you see the installed extension in the extensions view?

When I start VSCode I have this message in red (sorry if in Italian, you can find the Google translation below):
Windows PowerShell
Copyright (C) Microsoft Corporation. Tutti i diritti riservati.

Prova la nuova PowerShell multipiattaforma https://aka.ms/pscore6

. : Impossibile caricare il file C:\Users\Elisa\Documents\WindowsPowerShell\profile.ps1. Il file C:\Users\Elisa\Documents\WindowsPowerShell\profile.ps1 non è
firmato digitalmente. Lo script non può essere eseguito nel sistema corrente. Per ulteriori informazioni sull'esecuzione di script e l'impostazione di criteri
di esecuzione, vedere about_Execution_Policies all'indirizzo https://go.microsoft.com/fwlink/?LinkID=135170.
In riga:1 car:3
+ . 'C:\Users\Elisa\Documents\WindowsPowerShell\profile.ps1'
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : Errore di protezione: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
Il caricamento dei profili personali e di sistema ha richiesto 2397 ms.

-------------------------------------------- Google traslation

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

.  The file C: \ Users \ Elisa \ Documents \ WindowsPowerShell \ profile.ps1 is not
digitally signed. The script cannot be run on the current system. For more information on scripting and policy setting
execution, see about_Execution_Policies at https://go.microsoft.com/fwlink/?LinkID=135170.
In row: 1 car: 3
+. 'C: \ Users \ Elisa \ Documents \ WindowsPowerShell \ profile.ps1'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~
    + CategoryInfo: Security Error: (:) [], PSSecurityException
    + FullyQualifiedErrorId: UnauthorizedAccess
Loading personal and system profiles took 2397 ms.

Also, if I run a code block (with just 'import numpy as np'), I find this message.
Non è stato possibile avviare il kernel.
Avvio del kernel non riuscito Python 3.9.7 64-bit'.
Per ulteriori dettagli, visualizzare Jupyter [log](command:jupyter.viewOutput). Cannot read properties of undefined (reading 'makeSettings')

-------------------------------------------- Google translation

The kernel could not be adopted.
Failed to boot kernel Python 3.9.7 64-bit '.
For more details, view Jupyter log. Unable to read properties of undefined (reading 'makeSettings')

Seems python related @rchiodo Can you please help the user?

That's the error that occurs because the install is incorrect. That 'makeSettings' function is not in @Elisa-code184's installation but it is normally.
Normally it's here:

But on @Elisa-code184's install that file is on 1KB, instead of 1033KB.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

@Elisa-code184 This issue got missed my notice, sorry about it. Can you please let me know if you are still able to reproduce it? If so, can you please try reproducing it using fresh user data dir and extensions dir. You can do that by launching VS Code from command line like this `code --user-data-dir  --extensions-dir

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Personal email visible in listing for other users

When configuring per user email imap sync, all mail will show up in the "my email > All Email" section for each user.
User A can see user B personal email listing (user A is not listed as to/cc/bcc..)
User B can see user A personal email listing (user B is not listed as to/cc/bcc..)
When user A clicks on an email which is shouldn't see, he do gets a
"You do not have permission to perform this action."

@ollieno , Thank you for reporting the issue!
We've already fixed this problem in platform versions 2.2.0, 2.1.3, 2.0.11 (and newer, respectively).
So, if version of your OroPlatform is earlier then mentioned above - please, make the upgrade.
If version of your OroPlatform is newer - please, provide an exact OroPlatfrom version, that you're using.
(You can find out the version on the page /platform/information of you Oro application)

Thx! I just noticed. Works like a charm!


Setting services.tailscale.useRoutingFeatures = "server" usually doesn't work

Describe the bug
Setting services.tailscale.useRoutingFeatures = "server" causes an error on systems where the proxyARP option is off for all interfaces, which is the default case. This is because the tailscale option is implemented as:
    boot.kernel.sysctl = mkIf (cfg.useRoutingFeatures == "server" || cfg.useRoutingFeatures == "both") {
      "net.ipv4.conf.all.forwarding" = mkDefault true;
      "net.ipv6.conf.all.forwarding" = mkDefault true;
    };

But network-interfaces.nix:1374 sets a conflicting default:
"net.ipv4.conf.all.forwarding" = mkDefault (any (i: i.proxyARP) interfaces);

The use of mkDefault for the tailscale option was requested by @RaitoBezarius in the original PR from @Enzime, but I'm not sure that this makes sense. First of all, if you want to enable "server routing features", then enabling IP forwarding is a requirement, not a default. If I set useRoutingFeatures = "server" and something else sets ip forwarding to false, that's when I'd want to see an error, rather than the issue being silently ignored. Secondly, I don't understand the original comment's claim that "it would prevent fine-grained net.ipv4.conf.$interface.forwarding = true". I don't know how the kernel handles the per-interface setting being different than the "all" setting, but it seems moot; we're talking here about defaults in the NixOS module system, not in sysctl.
So, I think the mkDefaults should be removed in the above code from tailscale.nix.
Steps To Reproduce

Set services.tailscale.useRoutingFeatures = "server" on a system where the proxyARP option is off for all interfaces (which is the default).
Receive this error when building the system closure:

error: The option `boot.kernel.sysctl."net.ipv4.conf.all.forwarding"' is defined multiple times.

       Definition values:
       - In `/nix/store/wh4nnz2ga9lpxl406ia1cnsi891xaa4x-source/nixos/modules/services/networking/tailscale.nix': true
       - In `/nix/store/wh4nnz2ga9lpxl406ia1cnsi891xaa4x-source/nixos/modules/tasks/network-interfaces.nix': false

Notify maintainers
I feel like it probably isn't necessary to page more maintainers right away? Let's start with the above; someone will know if we need more eyes.

Also, while I'm here, and since this option is so new ... Why did we decide to implement this with a single option of string type? Wouldn't two bools make more sense (one for client features, and one for server)?
That way, you could set e.g. services.tailscale.useRoutingFeatures.server = true in one module and services.tailscale.useRoutingFeatures.client = true in another module, and everything would just work. As it is, setting the option to "server" in one module and "client" in another is an error.

The use of mkDefault for the tailscale option was requested by @RaitoBezarius https://github.com/NixOS/nixpkgs/pull/201119#discussion_r1037123185 from @Enzime, but I'm not sure that this makes sense. First of all, if you want to enable "server routing features", then enabling IP forwarding is a requirement, not a default. If I set useRoutingFeatures = "server" and something else sets ip forwarding to false, that's when I'd want to see an error, rather than the issue being silently ignored. Secondly, I don't understand the original comment's claim that "it would prevent fine-grained net.ipv4.conf.$interface.forwarding = true". I don't know how the kernel handles the per-interface setting being different than the "all" setting, but it seems moot; we're talking here about defaults in the NixOS module system, not in sysctl.

It's not mandatory to set all interfaces as forwarding, usually, the forwarding domain on a Tailscale machine is not all interfaces but some subset of those interfaces, therefore, it should be possible to override the all and set it up on each interface to have a well-defined forwarding domain.
Enabling IP forwarding is a requirement, indeed, but enabling IP forwarding on ALL interfaces is not a requirement.
A good condition should be a assert to check if there's at least one IP forwarding domain enabled.

So, I think the mkDefaults should be removed in the above code from tailscale.nix.

I am not certain this should be the case.
It is unfortunate another module introduces a conflicting definition, but it should be managed through priority rather than enforcing it, otherwise someone else (e.g. me for example) will open an issue with a use case where it does not work because of enforcement.
If @Enzime you have some time to submit a PR increasing the option priority, it would be great.

I spent several hours yesterday struggling to understand that I was running into both tailscale#3310, and tailscale#4432.
This leaves me wondering why we could not introspect extraUpFlags, and extraSetFlags, instead of an useRoutingFeatures option, so that everything has a better chance to work out of the box? Or at least do the introspection and print appropriate warnings if useRoutingFeatures is not set?

I think that's a good idea, feel free to submit a PR, those options did not exist when I added services.tailscale.useRoutingFeatures


Remove import from ecs.php

This has already been done in develop, it will get pulled in on next release

I see.
This non-develop default branch make me dizzy sometimes 😵

Yeah, it seems to be more hassle than it's worth. I've set all the decodelabs library repos to use develop as the default branch so pull requests will target the correct branch by default.
Thanks for the additions to this library, it's appreciated.


[coap] partial matching of resource's URI

Is your feature request related to a problem? Please describe.
Currently, CoAP module matches the whole mUri value. Such behavior limits usages of a single resource instance for scenarios where multiple URIs share a fine portion of the path, e.g. device id's selector URI-Path: /device/<id>. With current implementation one must to have an otCoapResource instance for every  where much simpler approach would be to have a single structure instance regardless of a number of hypothetical devices.
Also, it totally blocks usage of URI-Query options, as in example URI /discover?version=1&type=thread&diag=true implementation cannot handle values provided by the other party and one would also need to handle every possible combination of these.
Describe the solution you'd like
I would like to propose a change with partial URI matching but I would like to know if such change is welcomed and also discuss if such partial matching should be a default behavior or it should be controlled by a flag.

Thanks, @konradderda. I think adding this feature could be beneficial.
As for whether to make partial URI matching the default behavior or control it with a flag, I suggest we base the decision on the size of the code change required to implement it. If the change is small, including it by default might make sense. If it introduces significant overhead, it might be better to put it behind a build flag.


Fix range value prop

@philolo1 This fixes an issue in Range component. The value prop was not working correctly... :(

@argelius it seems like a thing that should rather be fixed in the core or in SimpleWrapper. Is it not setting the value when it is changed in the dom?

@philolo1 Actually the value attribute of an input element is only used for initialization. It doesn't change the value when the attribute changes.

@argelius then we should mention this, maybe add it to the orginal example


how to calculate time and distance?

Hi , i am using api/reports/trips and i am getting data like:
        deviceId: 1,
        deviceName: xyz,
        distance: 1536.5099999997765,
        duration: 369000,
        ....other parameters!!

Now how to convert this duration into minutes ?? and distance into Km ?

Distance is in meters. Duration is in milliseconds.

Thanks.


Investigate other coverage tools

Several tests fail in strange ways when they are instrumented with blanket.  It looks like blanket particularly doesn't like the global inherit function we use.  There are a couple of alternative coverage reporters that might work:

istanbul
jscoverage

I like istanbul, but it will require moving to webpack so we don't have to instrument the sources manually.


llmq|init|test: Implement DKG data recovery / quorum verification vector sync

This PR implements DKG data recovery in 4d54892127a9d139e1e3042e90c1c520030de396 which allows a member of  LLMQx which looses it's required DKG data (quorum verification vector and secret key share) e.g. due to unexpected loss/corruption of the database to recover itself with the help of the other members of LLMQx and the P2P messages QGETDATA/QDATA. Before this PR such an invalid member would just stay invalid for the remaining "active time" of the LLMQ.
To solve a requirement of platform/tenderdash it also introduces quorum verification vector sync in eef2691defeb3e903db28eaf8afd247a7810961b which enables to configure a masternode to request the quorum verification vectors of all existing/new LLMQs with the type llmqType if the masternode itself is a member of any other active LLMQ with the type llmqType.
New command line parameter (hidden?):

-llmq-data-recovery - Enable 1, Disable 0 automated data recovery/qvvec requests.
-llmq-qvvec-sync - Defines from which LLMQ type the masternode should sync quorum verification vectors (Can be used multiple times with different LLMQ types.

New thread

dash-q-recovery This new thread can exist exactly one time for each quorum (llmqType, quorumHash) and its job is to query the missing DKG data from related quorum members. This is done in a loop like: Calculate the next masternode to try, connect to it, send the QGETDATA request and wait until the QDATA message comes in with a timeout of 10 seconds before we try the next member. This is continues until the required data has been received successfully or until all members of the quorum were asked without success.

The recovery threads are getting started by CQuorumManager::TriggerQuorumDataRecoveryThreads() if required which gets called with every block update in CQuorumManager::UpdatedBlockTip().
The masternode decides based on CQuourm::GetQuorumRecoveryStartOffset() and the sorted protx hashes from all members of the quorum to which member of the quorum it tries to connect first. It also sleeps offset * 100ms before it tries to connect to the next member. I implemented those two as attempt to balance the incoming requests equally for each member of the target quorum. This means if -llmq-qvvec-sync=llmq_100_67 is used on all masternodes by platform and a new llmq_100_67 quorum just formed we will have in worst case ~2400 nodes asking ~100 members for their quorum verification vectors which means each member will then in best case get 24 requests and then all nodes should have the verification vector. Should be just good or do i miss something?
Let me know your thoughts!
Based on #3953

Just added 744c8d0 with the last force push. This is an issue which comes from #3953 where recover=True for wait_for_quorum_data wasn't even used/needed. The recover parameter should have just not exist in that PR but that was obviously a mistake i made when i during development added a generalized version of wait_for_quorum_data to test_framework.py instead of having a specific version in p2p_quorum_data.py and feature_llmq_data_recovery.py. I guess we can just fix it in here?

Just added 744c8d0 with the last force push. This is an issue which comes from #3953 where recover=True for wait_for_quorum_data wasn't even used/needed. The recover parameter should have just not exist in that PR but that was obviously a mistake i made when i during development added a generalized version of wait_for_quorum_data to test_framework.py instead of having a specific version in p2p_quorum_data.py and feature_llmq_data_recovery.py. I guess we can just fix it in here?

And one more force push:

Rebased on develop to have #3971 included
Fixed some issues in feature_llmq_data_recovery.py
Added 92127d2 which is basically another #3953 fix in test_framework.py for the method test_mn_quorum_data.

And one more force push:

Rebased on develop to have #3971 included
Fixed some issues in feature_llmq_data_recovery.py
Added 92127d2 which is basically another #3953 fix in test_framework.py for the method test_mn_quorum_data.

See below or maybe UdjinM6@16a59e0 instead of suggestions in src/llmq/quorums.cpp

I like 16a59e0  👍 Partially picked it in 00434a9d36b3e924f43290f906007ade36bd01c0, not the cache thread related stuff though because that seemed unrelated to here? But imo it still makes sense in a separate PR unless you both feel we should still just push it in here, i can, let me know :D

See below or maybe UdjinM6@16a59e0 instead of suggestions in src/llmq/quorums.cpp

I like 16a59e0  👍 Partially picked it in 00434a9d36b3e924f43290f906007ade36bd01c0, not the cache thread related stuff though because that seemed unrelated to here? But imo it still makes sense in a separate PR unless you both feel we should still just push it in here, i can, let me know :D

if the masternode itself is a member of any other active LLMQ with the type llmqType.

This should probably be accessible via nodes connecting via qwatch no?
Additionally, could this be a dos vector? What happens if I repeatedly request from the same node?

if the masternode itself is a member of any other active LLMQ with the type llmqType.

This should probably be accessible via nodes connecting via qwatch no?

Can you explain a bit more what you mean here?

Additionally, could this be a dos vector? What happens if I repeatedly request from the same node?

Also here im not sure where your concerns are coming from since this PR doesn't change any behaviour of the underlying P2P messages, it just uses them. Can you explain your thoughts?


Robot: Proper scaling

Robot image should be scaled properly on the field

@mthiop Can this be closed?


How to compile build on Android

!!! Before submitting a new feature request, please ensure you have searched for any existing features and utilized
the Ask AI feature at https://ossrs.io or https://ossrs.net (for users in China). Duplicate issues or
questions that are overly simple or already addressed in the documentation will be removed without any
response.
What is the business background? Please provide a description.
Who are the users? How do they utilize this feature? What problem does this feature address?
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

你的问题不符合Issue的要求，请按Issue模版提Bug，不提供完整信息的Issue会被直接删除。
该Issue会被删除，请先阅读FAQ：#2716


[zh] Add a blog: 2024-09-17-sig-scheduling-spotlight

Add zh text to this blog:
content/zh-cn/blog/_posts/2024-09-17-sig-scheduling-spotlight.md

See preview

/lgtm

/lgtm


[Backport 1.x] Update nebula-publishing-plugin to 19.2.0 (#5704)

Description
This is a backport of #5704 to 1.x line.

need to backport https://github.com/opensearch-project/OpenSearch/pull/5600 first


Remove autocompletion section from the help page

Rationale for this is that the whole point of autocompletion is to be intuitive and show up naturally when starting to type something else. Helper for this is just extra noise user does not need.
For example, all commands start with /, so obviously starting to type a command will trigger autocomplete. This is true for channels as well.
Emoji are a bit particular because all systems that support emoji open their completion with :.
The only not-so-intuitive completion strategy is for nicks because it is not so common to start them with @ on IRC, but as long as we keep tab completion after any set of characters, this is fine. It will be even nicer once regular tab completion uses the same autocompletion dropdown.

I feel like this was merged too quickly. Only 1 approval feels odd for this, especially as I was assigned by @astorije, it feels odd for it to have been merged so suddenly.


Mocha stops before finishing all tests

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend avoiding the use of globally installed Mocha.

Description
Mocha isn't finishing all my tests!
This is the only file I currently have to run my tests: https://github.com/ArcticZeroo/carabiner/blob/master/test/test.js
As you can see, there are 7 "high level" categories described within "Carabiner". However, after the 5th (Client), mocha stops.
I thought that perhaps something may have gone wrong within the prior tests that would lock up mocha or something, or that perhaps mocha had a limit to the number of descriptions. So I tried to comment out other tests, including "Client", everything before "Client", etc and it's still stopping at Client.
And I have absolutely no idea why!
The version of mocha I have on my machine is 3.5, which I am aware is two major versions out of date. However, travis' version is 5.2.0 (latest I presume, since the command run is just npm i -g mocha) and it's running into the same issue.
Here is the travis build for it: https://travis-ci.org/ArcticZeroo/carabiner
Steps to Reproduce

Clone https://github.com/ArcticZeroo/carabiner
Run "npm i"
Get a slack token from somewhere. Doesn't matter where, because if you are able to reproduce my issue, you'll never even hit the testing environment where the contents of the organization actually matters.
Set this token to the env variable SLACK_TOKEN (set SLACK_TOKEN=yourtoken)
Run "npm test" (which just runs "mocha")
See that all tests in Carabiner up to client pass, and then mocha seems to think it's finished

Expected behavior: Mocha tests all 7 high level "descriptions" inside Carabiner
Actual behavior: Mocha tests the first 5
Reproduces how often: 100%
Versions
I don't think version is relevant here. As I said, it occurs on 5.2 and 3.5, along with node 7 and 8, on Windows and whatever Travis uses (some type of linux?)
Additional
Here's a screenshot of the current output on my machine, and it does exit once this is done
http://frozor.io/up/xLkVtV0.png
Ignore the experimental warning, that is a super recent thing that I am pretty sure is not related.

Further weirdness:
I was looking for why my Travis build was halting for 10m, and saw the FAQ thing about leaving sockets open. Which made me realize I was indeed leaving Slack RTM websockets open, and so I went to track down the cause.  I added debug to print a stacktrace each time an RTM socket was opened, and it appears that the "test slack organization" function is actually called... but mocha never seems to complete it? I'm not sure what's up.

Aha, I've tracked down the issue. The "Structures" not being called was 100% my issue, I never included an "it". However, I'm unsure why "describe" doesn't support async functions?


include query parameters in parameterOrder field

Discovery has a parameterOrder field. This is seemingly used to
document the order of parameters for use in client library
generation. Previously, we were only including path parameters, but we
need to include query parameters, so that the order is deterministic.

Codecov Report

Merging #113 into master will increase coverage by 0.08%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #113      +/-   ##
============================================
+ Coverage     79.59%   79.68%   +0.08%
- Complexity     1641     1643       +2
============================================
  Files           156      156
  Lines          5524     5523       -1
  Branches        707      706       -1
============================================
+ Hits           4397     4401       +4
+ Misses          849      846       -3
+ Partials        278      276       -2

Impacted Files
Coverage Δ
Complexity Δ

...e/api/server/spi/discovery/DiscoveryGenerator.java
87.56% <100%> (-0.07%)
51 <0> (ø)

...erver/spi/config/model/ApiSerializationConfig.java
82.75% <0%> (+6.89%)
9% <0%> (+1%)
:arrow_up:

...a/com/google/api/server/spi/BackendProperties.java
100% <0%> (+10.71%)
12% <0%> (+1%)
: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 8285cc5...73d3019. Read the comment docs.


✨Heuristic mapper fidelity preparation

Description

isolated the heuristic to HeuristicMapper::Node::updateHeuristicCost for less redundant code and easier expansion with further heuristic types (e.g. the planned fidelity aware approach)
removed redundant field HeuristicMapper::Node::totalCost (redundant to HeuristicMapper::Node::costFixed)
added consider_fidelity field to configuration classes

Checklist:

[x] The pull request only contains commits that are related to it.
[x] I have added appropriate tests and documentation.
[x] I have made sure that all CI jobs on GitHub pass.
[x] The pull request introduces no new warnings and follows the project's style guidelines.

That's right. Those can just be removed. Should be resolved now. Thank you.


Missing some SNPs in vcf , freebayes-parallel  with parameter --variant-input

I'm attempting run signal thread freebayes AND  multiple threads freebayes-parallel WITH parameter --variant-input VCF , in my VCF file i have 11578 SNPs. In signal thread mode freebayes output all of the 11578 SNPs AS i expected, but in multiple threads freebayes-parallel mode, the output vcf file have only 9665 SNPs of the 11578 SNPs. my commands is below.
signal thread mode:
freebayes --no-indel --no-mnps --no-complex -m 0 -q 20 -R 0 -S 0 -n 2
-f /dellfcsan/data/public/genome/maize/Zea_mays.AGPv3.22.fasta -L maize_12K_8sample.list
--variant-input /fcsan/projects/callsnp_mGPS_512/panel/maize_11578SNP_NA.vcf.gz  \

maize_12K_8samples_freebys_VCF_SNP_n2_strin_NA_MQ0.vcf

multiple threads:
freebayes-parallel
/dellfcsan/data/public/genome/maize/Zea_mays.AGPv3.22.100kbp.regions 36
--no-indel --no-mnps --no-complex -m 0 -q 20 -R 0 -S 0 -n 2 -f /dellfcsan/data/public/genome/maize/Zea_mays.AGPv3.22.fasta -L maize_12K_8sample.list
--variant-input /fcsan/projects/callsnp_mGPS_512/panel/maize_11578SNP_NA.vcf.gz  \

maize_12K_8samples_freebys_VCF_SNP_n2_strin_NA_MQ0_36threads.vcf

in multiple threads mode, I got the WARNING messeges as below.
WARNING(freebayes): Could not set the region of the variants input file to 1:0..100000
WARNING(freebayes): Could not set the region of the variants input file to 1:100000..200000
WARNING(freebayes): Could not set the region of the variants input file to 1:200000..300000
WARNING(freebayes): Could not set the region of the variants input file to 1:300000..400000
I exptect to get all of the 11578 SNPs in multiple threads mode as in  signal thread mode, but the output vcf file include 9665 SNPs only.
Thank you very much for explanation.
Best

this looks like a malformed .regions file, can you attach your Zea_mays.AGPv3.22.100kbp.regions  file

Zea_mays.AGPv3.22.100kbp.regions.txt
@Nheyer  the Zea_mays.AGPv3.22.100kbp.regions file has attached，thanks.

The regions file contains over 20K small connected regions for 10K SNPs:
1:3000000-3100000
1:3100000-3200000
1:3200000-3300000
1:3300000-3400000
1:3400000-3500000
1:3500000-3600000
etc

why would you want to do that? The parallel script chunks small regions this way and you are probably missing out on SNPs that are exactly on the border of a region. Not that that should happen, but it is pushing your luck ;).
Increase the chunk size so you get about 4x the chunks for the number of cores you want to use and see what happens.


Deneuralize wikilinks.js

The wikilinks.js file is insanely complex for what it does. It is obvious that an Ai wrote it.
It should be rewritten in a reasonable fashion and also preferably occur as a beforeHook and manipulate the md instead of the html dom.

in fact it was only half written by an AI ... I took an available wikilinks plugin and worked with the AI to "fix it"


Linux incompatibility

A user reported a crash on Linux. I am not that familiar with it but it seems like his distribution of Linux is missing something that others have.
Operating System: Linux (amd64) version 6.5.0-35-generic
Caused by: java.lang.IllegalStateException: Failed loading native PhysX libraries for platform LINUX
	at de.fabmax.physxjni.Loader.load(Loader.java:37)
	at physx.NativeObject.<clinit>(NativeObject.java:7)
	... 9 more
Caused by: java.lang.UnsatisfiedLinkError: /tmp/de.fabmax.physx-jni/2.3.2/libPhysXJniBindings_64.so: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by /tmp/de.fabmax.physx-jni/2.3.2/libPhysXJniBindings_64.so)
	at java.base/jdk.internal.loader.NativeLibraries.load(Native Method)
	at java.base/jdk.internal.loader.NativeLibraries$NativeLibraryImpl.open(Unknown Source)
	at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(Unknown Source)
	at java.base/jdk.internal.loader.NativeLibraries.loadLibrary(Unknown Source)
	at java.base/java.lang.ClassLoader.loadLibrary(Unknown Source)
	at java.base/java.lang.Runtime.load0(Unknown Source)
	at java.base/java.lang.System.load(Unknown Source)
	at de.fabmax.physxjni.NativeLib.load(NativeLib.java:49)
	at de.fabmax.physxjni.Loader.load(Loader.java:35)

Edit: The user fixed it by following the instructions here.

Can we bind Linux drivers in windows like touchpad driver audio driver etc


Adding .off() function

hi @paf31, as our conversation in slack, I would like to PR some of my small addition to the jquery function.

Looks great, thanks!


CodeLine Lex doesn't handle trailing if and unless

The assumption was that if and unless lines need to be paired with ends, but that's not true if it's trailing:
       +  end
       +  class Main
       +        @user_source_code = 'self' if @user_source_code == ''
       +    end
       +  end

irb(main):001:0> require 'ripper'
=> false
irb(main):002:0> pp Ripper.lex("puts 'lol' if foo")
[[[1, 0], :on_ident, "puts", CMDARG],
 [[1, 4], :on_sp, " ", CMDARG],
 [[1, 5], :on_tstring_beg, "'", CMDARG],
 [[1, 6], :on_tstring_content, "lol", CMDARG],
 [[1, 9], :on_tstring_end, "'", END],
 [[1, 10], :on_sp, " ", END],
 [[1, 11], :on_kw, "if", BEG|LABEL],
 [[1, 13], :on_sp, " ", BEG|LABEL],
 [[1, 14], :on_ident, "foo", CMDARG]]

I think that we can disambiguate a trailing end if it is a "BEG|LABEL" as a non-trailing end will just be a BEG
source = <<~EOM
  if bar; puts "lol"; end
EOM

pp Ripper.lex(source)
[[[1, 0], :on_kw, "if", BEG],
 [[1, 2], :on_sp, " ", BEG],
 [[1, 3], :on_ident, "bar", CMDARG],
 [[1, 6], :on_semicolon, ";", BEG],
 [[1, 7], :on_sp, " ", BEG],
 [[1, 8], :on_ident, "puts", CMDARG],
 [[1, 12], :on_sp, " ", CMDARG],
 [[1, 13], :on_tstring_beg, "\"", CMDARG],
 [[1, 14], :on_tstring_content, "lol", CMDARG],
 [[1, 17], :on_tstring_end, "\"", END],
 [[1, 18], :on_semicolon, ";", BEG],
 [[1, 19], :on_sp, " ", BEG],
 [[1, 20], :on_kw, "end", END],
 [[1, 23], :on_nl, "\n", BEG]]

source = <<~EOM
  foo = if bar; "lol"; end
EOM

pp Ripper.lex(source)
[[[1, 0], :on_ident, "foo", CMDARG],
 [[1, 3], :on_sp, " ", CMDARG],
 [[1, 4], :on_op, "=", BEG],
 [[1, 5], :on_sp, " ", BEG],
 [[1, 6], :on_kw, "if", BEG],
 [[1, 8], :on_sp, " ", BEG],
 [[1, 9], :on_ident, "bar", CMDARG],
 [[1, 12], :on_semicolon, ";", BEG],
 [[1, 13], :on_sp, " ", BEG],
 [[1, 14], :on_tstring_beg, "\"", BEG],
 [[1, 15], :on_tstring_content, "lol", BEG],
 [[1, 18], :on_tstring_end, "\"", END],
 [[1, 19], :on_semicolon, ";", BEG],
 [[1, 20], :on_sp, " ", BEG],
 [[1, 21], :on_kw, "end", END],
 [[1, 24], :on_nl, "\n", BEG]]


Sequence table for Maize

Please independently create the same table for Maize
Plastid
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/plastid.2.fasta
Mitochondrion
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/mitochondrion.2.fasta
RefSeq
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/GCF_902167145.1_Zm-B73-REFERENCE-NAM-5.0_protein.2.faa
B73_v5
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/Zm-B73-REFERENCE-NAM-5.0_Zm00001eb.1.protein.2.fa
W22
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/Zm-W22-REFERENCE-NRGENE-2.0_Zm00004b.1.protein.fa
UniProtKB
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/uniprot-proteome_UP000007305.2.fasta
ProFITS
curl -O -R ftp://ftp.peptideatlas.org/pub/PeptideAtlas/Proteomes/maize/ProFITS_TF_4a53_protein.2.remove.fasta

okay, I added 3 more files to the get_data.sh file for download, I think it is complete now. let's got with these titles and files in the order below:
B73_v5=Zm-B73-REFERENCE-NAM-5.0_Zm00001eb.1.protein.2.fa
B73_v4=Zm-B73-REFERENCE-GRAMENE-4.0_Zm00001d.2.protein.2.fa
UniProtKB=uniprot-proteome_UP000007305.2.fasta
RefSeq=GCF_902167145.1_Zm-B73-REFERENCE-NAM-5.0_protein.2.faa
B73_v3=Zea_mays.AGPv3.22.pep.all.remove.2.fa
W22_v2=Zm-W22-REFERENCE-NRGENE-2.0_Zm00004b.1.protein.fa
ProFITS=ProFITS_TF_4a53_protein.2.remove.fasta
AgriGO=agriGO_151.2.remove.fasta
Mitochondrion=mitochondrion.2.fasta
Plastid=plastid.2.fasta
Questions?

I checked the get_data.sh file from the maize folder, and I only see the original seven entries below:

I did a git pull to make sure and also checked in the repo. Maybe I am looking in the wrong file?

oops, you're right, I committed to the wrong branch!
Fixed now:
https://github.com/PlantProteomes/SeqComparison/blob/main/proteomes/maize/original/get_data.sh

Cool, thanks!

Here is my table:

Does anyone know why this bug keeps happening with my code? It's not recognizing my files locally at all even though they are there according to the directory. I'll also have a snippet of the table sent by tommorow

The error message shows that the open() statement is trying to open the whole parameter Title=Filename. You just want to open the Filename, not the Title=Filename


Bug: Non-dev bundle fails due to handling of Params

Description
Trying to run a bundle command without the --dev flag fails, due to the now undefined value of params.dev
How to reproduce
run bundle
What do you expect
For bundle to work the same way as bundle --dev
What happened instead
The build fails due to the __DEV__ variable.

node_modules/esbuild/lib/main.js:299:10: ERROR: Expected value for define "DEV" to be a string, got undefined instead

Software:

version: sdplus-support branch

Full backtrace
/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:299:10: ERROR: Expected value for define "__DEV__" to be a string, got undefined instead
    at failureErrorWithLog (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:1636:15)
    at /Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:953:16
    at responseCallbacks.<computed> (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:697:9)
    at handleIncomingPacket (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:752:9)
    at Socket.readFromStdout (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:673:7)
    at Socket.emit (node:events:512:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:190:23) {
  errors: [
    {
      id: '',
      pluginName: '',
      text: 'Expected value for define "__DEV__" to be a string, got undefined instead',
      location: [Object],
      notes: [],
      detail: Error: Expected value for define "__DEV__" to be a string, got undefined instead
          at validateStringValue (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:299:11)
          at pushCommonFlags (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:390:37)
          at flagsForBuildOptions (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:424:3)
          at buildOrContextContinue (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:1009:9)
          at buildOrContextImpl (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:993:5)
          at Object.buildOrContext (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:776:5)
          at /Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:2163:15
          at new Promise (<anonymous>)
          at Object.build (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:2162:25)
          at build (/Users/rdohms/dev/elgato/com.dms.streamdeck.github-prs/node_modules/esbuild/lib/main.js:2011:51)
    }
  ],
  warnings: []
}

Workaround that I found was to adjust this line and this line to be:
    define: {
      __DEV__: JSON.stringify(params.dev ?? true),
    },

This is because the default value is to be undefined, and something under the hood does not like that.


Confirmed working with Chitubox 1.9.0 and Debian 11 (Bullseye)

I have used this script to install the latest version of Chitubox (1.9.0) on Debian 11.
(Obviously, I had to modify the name of the install archive, in favour of 1.9.0.)
Thanks!

Similar here. 1 line edit in chitbox_install.sh to change to v1.9.0, and worked perfectly in Ubuntu 21.04 64bit with wayland


Added  Support for Automatic Templated File Search for Atmos Imports

what

Implementing automatic detection and import of templated files (.yaml.tmpl or .yml.tmpl) in Atmos
Adding fallback to regular .yaml or .yml files when templated versions aren't found
Simplifying import configuration by removing the need to explicitly specify .tmpl extensions
Maintaining backward compatibility with existing import configurations

why

Improves developer experience by reducing manual configuration overhead

Summary by CodeRabbit
Release Notes

New Features

Enhanced file import handling to support multiple YAML extensions, including templates.
Introduced new functions for improved configuration file pattern matching and searching.

Bug Fixes

Improved error handling for file searches and imports, providing clearer error messages when no matches are found.

Refactor

Updated existing functions to accommodate new file extensions and refined logic for file type detection.

Documentation

Clarified comments to reflect updated logic and functionality.

Please update the docs here: https://atmos.tools/core-concepts/stacks/imports#go-templates-in-imports


RuntimeError: bool value of Tensor with more than one value is ambiguous

❓ Questions & Help

Here's the code I'm trying to run, the tensor itself gets returned, but when I try to decode it I get the error above.
Any ideas?  Thanks!
`if name == 'main':
# main()
model_class, tokenizer_class = MODEL_CLASSES['gpt2']
tokenizer = tokenizer_class.from_pretrained('gpt2')
context_tokens = tokenizer.encode("My favorite first date idea is")
model = model_class.from_pretrained('gpt2')
model.to('cpu')
model.eval()

out = sample_sequence(
	model=model,
	context=context_tokens,
	length=140,
	temperature=0.9,
	top_k=1,
	top_p=0.9
)

text = tokenizer.decode(out)
print(text)`

Could you please provide more information, especially regarding the sample_sequence function and where it is coming from?

My goal is to wrap the GPT2 model interface in a function so I can input a prompt and output generated text.  I'm trying to adapt one of the examples, and I'm getting there, but I wasn't able to find anything on the error specific to Pytorch-Transformers.
Here's the sample_sequence function:
def sample_sequence(model, length, context, num_samples=1, temperature=1, top_k=0, top_p=0.0, device='cpu'): 	context = torch.tensor(context, dtype=torch.long, device=device) 	context = context.unsqueeze(0).repeat(num_samples, 1) 	generated = context 	with torch.no_grad(): 		for _ in trange(length): 			inputs = {'input_ids': generated} 			outputs = model(**inputs) 			next_token_logits = outputs[0][0, -1, :] / temperature 			filtered_logits = top_k_top_p_filtering(next_token_logits, top_k=top_k, top_p=top_p) 			next_token = torch.multinomial(F.softmax(filtered_logits, dim=-1), num_samples=1) 			generated = torch.cat((generated, next_token.unsqueeze(0)), dim=1) 		return generated

Your sample sequence function returns a torch.tensor([[int64]]), of shape [batch_size, sequence_length]. In your specific case it is of size [1, 146].
You cannot feed such an object to the tokenizer for decoding, as it only accepts a list of integers.
You can fetch the list of integers by calling the tolist() method on your output, and then feed it to the tokenizer for decoding:
out = sample_sequence(
	model=model,
	context=context_tokens,
	length=140,
	temperature=0.9,
	top_k=1,
	top_p=0.9
)

generated_list = out[0].tolist()
text = tokenizer.decode(generated_list)

print(text)

It worked!
This was very helpful, thank you!  Just getting familiar with this package, it's awesome!


SSL handshake failure

For some reasons, I am not able to get cowboy running with tls.
I use the following configuration:
  Routes = [{'_', [{"/test", test_handler,    #{}}]}],
  Dispatch = cowboy_router:compile(Routes),

  PrivDirectory = code:priv_dir(myapp),

  {ok, _} = cowboy:start_tls(myapp_tls,
                             [{certfile, PrivDirectory ++ "/server.crt"},
                              {keyfile, PrivDirectory ++ "/server.key"},
                              {port, 8443}
                             ],
                             #{env => #{dispatch => Dispatch}}),

  myapp_sup:start_link().

And when I send any request with curl or other, I always get something like:
curl --trace-ascii - -k https://<IP_ADDRESS>:8443/test
== Info:   Trying <IP_ADDRESS>...
== Info: TCP_NODELAY set
== Info: Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8443 (#0)
== Info: ALPN, offering h2
== Info: ALPN, offering http/1.1
== Info: ignoring certificate verify locations due to disabled peer verification
=> Send SSL data, 5 bytes (0x5)
0000: .....
== Info: TLSv1.2 (OUT), TLS handshake, Client hello (1):
=> Send SSL data, 237 bytes (0xed)
0000: ......cve........%E@.....{tc.."...L.k...h.,.0.........+./.....$.
0040: (.s.w.#.'.r.v.....................=...<...5.../.A...............
0080: k...g...9...3.E.....X......................3t.........h2.http/1.
00c0: 1........... ................................
<= Recv SSL data, 5 bytes (0x5)
0000: .....
== Info: TLSv1.2 (IN), TLS alert, Server hello (2):
<= Recv SSL data, 2 bytes (0x2)
0000: .(
== Info: error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
== Info: stopped the pause stream!
== Info: Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure

On the cowboy shell I get the following error: TLS server: In state hello at tls_handshake.erl:130 generated SERVER ALERT: Fatal - Handshake Failure - malformed_handshake_data. Both are running on my laptop and should be using the same version of openssl.
I am running OTP-21.0-rc1, OpenSSL 1.1.0h-fips  27 Mar 2018,
and I tested with both cowboy 2.3 and 2.4.

That's an OTP-21.0-rc1 issue, me and a few other people reported it. Please try master to see if it's fixed. I have not been able to test it yet, waiting for rc2.

@essen That's what I get for always wanting to try the latest shiny thing. Thank you anyway.


Crash while exporting element with long FQN

Building from the latest CIMI spec:
When the FQN of an element or extension exceeds ~64 characters, the FHIR-Exporter crashes. The only workaround right now is to reduce the length of the elements' names.

> Step 2: Building new IG
> FHIR Implementation Guide Publisher (3.0.1-11916) @ Friday, August 18, 2017 3:17:12 PM
> Detected Java version: 1.8.0_144 from /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre on x86_64 (64bit). 3641MB available
> Load Configuration from /Users/abhatnagar/Code/SHR/out/fhir/guide/shr.json       (00.0000sec)
> File log: /var/folders/1d/t7dd_tf55jvgz63lgk30dsvr0000gn/T/fhir-ig-publisher-tmp.log
> Root directory: /Users/abhatnagar/Code/SHR/out/fhir/guide                        (00.0058sec)
> Terminology Cache is at /Users/abhatnagar/Code/SHR/out/fhir/guide/txCache. 1 files in cache (00.0071sec)
> Load Validation Pack (internal)                                                  (00.0072sec)
> Definitions 3.0.1-11917                                                          (08.0786sec)
> Connect to Terminology Server at http://tx.fhir.org/r3                           (08.0788sec)
> Publishing Content Failed: Bad Resource Identity - should have the format [Type]/[id] where id is a valid FHIR id type:StructureDefinition/cimi-clinicaladverseeventreporting-AssociatedClinicalStudy-extension (09.0692sec)
>                                                                                (09.0693sec)
> Use -? to get command line help                                                  (09.0694sec)
>                                                                                (09.0695sec)
> Stack Dump (for debugging):                                                      (09.0696sec)
> java.lang.Exception: Bad Resource Identity - should have the format [Type]/[id] where id is a valid FHIR id type:StructureDefinition/cimi-clinicaladverseeventreporting-AssociatedClinicalStudy-extension
> 	at org.hl7.fhir.igtools.publisher.IGKnowledgeProvider.loadPaths(IGKnowledgeProvider.java:75)
> 	at org.hl7.fhir.igtools.publisher.IGKnowledgeProvider.<init>(IGKnowledgeProvider.java:53)
> 	at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:769)
> 	at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:299)
> 	at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:3589)
>

This is a limitation that's built into FHIR. The IG publisher won't accept long names.
From https://www.hl7.org/fhir/elementdefinition.html:

Warning: Element names should be simple alphanumerics with a max of 64 characters, or code generation tools may be broken
In other words, not our bug.


(wip): YJDH-61: Application page #117

Description :sparkles:
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #118 (86fb28a) into YJDH-25-ui-layout (ce4b5ed) will not change coverage.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           YJDH-25-ui-layout     #118   +/-   ##
==================================================
  Coverage              14.82%   14.82%
==================================================
  Files                     45       45
  Lines                    587      587
  Branches                  97       97
==================================================
  Hits                      87       87
  Misses                   486      486
  Partials                  14       14

Impacted Files
Coverage Δ

...react-query/get-default-react-query-test-client.ts
0.00% <ø> (ø)

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 ce4b5ed...86fb28a. Read the comment docs.


[42000][1064] get_applied_rowsets failed, tablet updates is in error state: actual row size changed after compaction

Hello,
I have created a table and I am loading it with some parquet files coming from azure delta lake storage. The load job completes successfully and the number of rows scanned is correct (around 300M). When I try to query the table I receive the following error:
[42000][1064] get_applied_rowsets failed, tablet updates is in error state: tablet:10104 actual row size changed after compaction 67133362 -> 58040099tablet:10104 #version:3 [1 2.1@2 2.1] #pending:0 backend:<IP_ADDRESS>
Steps to reproduce the behavior (Required)

create table signals (
IngestionId	STRING NOT NULL,
DeviceId INT,
VehicleId INT,
MessageId INT,
SignalId INT,
BusId INT,
ApplicationTypeId INT,
SignalTypeId INT,
RegisteredOn BIGINT,
RegisteredTimestamp DATETIME,
ConfigurationId	INT,
ConfigurationName STRING,
ConfigurationVersion INT,
ProductLineId INT,
PlatformId INT,
ProgramId INT,
SegmentId INT,
IngestedOn BIGINT,
MessageName STRING,
MessageAddress INT,
PGN INT,
SourceAddress INT,
DestinationAddress INT,
SignalName STRING,
BusName STRING,
SignalValue DOUBLE,
SignalUnit STRING,
SignalValueString STRING,
LoggerId INT,
LogInstanceId INT
)
ENGINE=OLAP
PRIMARY KEY(IngestionId, DeviceId, VehicleId, MessageId, SignalId, BusId, ApplicationTypeId, SignalTypeId, RegisteredOn )
DISTRIBUTED BY HASH(IngestionId)
PROPERTIES("replication_num" = "1");

LOAD LABEL sr.label_test
(
DATA<EMAIL_ADDRESS>INTO TABLE signals
FORMAT AS "parquet"
(IngestionId,
MessageId,
SignalId,
BusId,
ApplicationTypeId,
SignalTypeId,
RegisteredTimestamp,
ConfigurationId,
ConfigurationName,
ConfigurationVersion,
ProductLineId,
PlatformId,
ProgramId,
SegmentId,
RegisteredOn,
IngestedOn,
MessageName,
MessageAddress,
PGN,
SourceAddress,
DestinationAddress,
SignalName,
BusName,
SignalValue,
SignalUnit,
SignalValueString,
LoggerId,
LogInstanceId
)
COLUMNS FROM PATH AS (DeviceId, VehicleId)
)
WITH BROKER
(
"azure.adls2.storage_account" = "xxxxx",
"azure.adls2.shared_key" = "xxxxx"
)
3. select count(1) from signals;
Expected behavior (Required)
Return 313506982
Real behavior (Required)
Error:
[42000][1064] get_applied_rowsets failed, tablet updates is in error state: tablet:10104 actual row size changed after compaction 67133362 -> 58040099tablet:10104 #version:3 [1 2.1@2 2.1] #pending:0 backend:<IP_ADDRESS>
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()
3.1.2-4f3a2ee91b

I am using the all in 1 docker image
Thank you!

please provide the BE logs?

can you provide the BE logs?

usually, BE logs are in be/log/be.INFO.log.* , if they are to large, you can just grepp&send relevant logs
grep 10104 be.INFO.log.* > 10104.log

10102.log
This tablet number is different but is the same error.
Thank you very much