"Ga" prefix added to components' name

I'm still working on it but just in case you prefer to make any change at this point tell me. I have to change the formatting too.
I'm going to change the examples to fit this components renaming, what do you think?

I have to make some changes and do the Fork/Pull worklfow better.


Error building 3.0 from source on Debian

Hey, thank you for your continued work on Riak!
I'm getting the following error when trying to build from source:
===> Compiling riak
===> Running cuttlefish schema generator
===> Starting relx build process ...
===> Resolving OTP Applications from directories:
          /home/riak/_build/deb/lib
          /home/riak/apps
          /usr/local/lib/erlang/lib
===> Resolved riak-3.0
===> rendering builtin_hook_wait_for_vm_start hook to "/home/riak/_build/deb/rel/riak/bin/hooks/builtin/wait_for_vm_start"
===> rendering builtin_hook_pid hook to "/home/riak/_build/deb/rel/riak/bin/hooks/builtin/pid"
===> rendering builtin_hook_wait_for_process hook to "/home/riak/_build/deb/rel/riak/bin/hooks/builtin/wait_for_process"
===> Including Erts from /usr/local/lib/erlang
===> release successfully created!
===> Unable to read vars file (debian/vars.config) for overlay due to: enoent
Schema parse error near line number 19: syntax error before: '}'
Error parsing schema: /home/riak/_build/deb/rel/riak/share/schema/23-riak_repl.schema

Could you point me in the right direction to get it working? Thank you 🙏

Can you confirm which tag or branch you're trying to build, and which debian version.  Is this from running make rel, or a different make command?

Hi Martin, thank you for the quick reply! 😄
I'm using the develop-3.0 branch and Debian 10.5.
I've managed to get past the error above by changing this line:
- {overlay_vars, "debian/vars.config"},
+ {overlay_vars, "rel/pkg/deb/debian/vars.config"},

However, when I try to run riak start I get an error about missing /etc/riak/riak.conf file, which I can fix by adding one.
But then when I try to run riak admin test, I get the following error:
/home/riak/rel/riak/bin/riak: 961: /home/riak/rel/riak/bin/riak-admin: /erl: not found

So I guess I must be missing something? Sorry if this is a n00b mistake!
I'm using make rel-deb, but I also get the same error with make rel.
Thank you for your help! 🙏

I've not used make rel-deb, and it is not something anyone tested for 3.0.  Unfortunately there's a few fragments of stuff which have been left lying around, that if they're not covered by the standard test set used within the development process may not work - this includes the riak admin test script.
If you use make rel then everything will be created under the rel/ folder in the folder you cloned into.  This should include the riak.conf in rel/riak/etc/riak.conf (e.g. /home/riak/rel/riak/etc/riak.conf in your case).  You can the run rel/riak/bin/riak start and rel/riak/bin/riak ping should return a pong.  Make sure you have a supported version of erlang up and running.
At the moment make package, make devrel (which is used in riak_test) and make rel are the only things we use in development.  If you want to have riak setup correctly as a service, under a riak user, then create the package using make package, and then install the created package using dpkg.
If you continue to have problems, I will try and have a play around to recreate ... but that might not be until Tuesday.

Ah I see, sorry my misunderstanding. Thank you for clarifying! 😄
Yes, if I use make rel or make package, and then riak ping I'm returned pong. So everything looks good there.
Thank you for you help! I'm excited to use (and hopefully contribute to) 3.0!


feat: add keyboard navigation and focus-ring

Based on the work by @anezthes, mostly a copy-paste from vaadin-list-mixin and vaadin-item-mixin.
The PR needs tests and will fail because of coverage until they are added.

I tried building tests for these today. Didn't go so well. Got so far to have these calls.
function arrowDown(target) {
  keyDownOn(target, 40, [], 'ArrowDown');
  keyUpOn(target, 40, [], 'ArrowDown');
}

where target is a single message, which I have done target.dispatchEvent(new CustomEvent('focus', { composed: true, bubbles: true })); on. The problem was that after arrowDown(target), I had two elements focused at once, the old and the next one. With only keyDownOn().., the next element did not get a focus. Feels also a bit clumsy to respecify the  "target" element continuously in the test.
I'll give this another shot later...

Multiple items can become focused at the same time right now. it is not so visible when using mouse only as focus ring is not shown, but it is still an issue when building the tests and doing something with the keyboard that doesn't cause navigation.
How to reproduce.

Click on a single item with a mouse. No focus rings are visible but you can see in the inspector that two elements are focused.

alt+tab out of the browser
alt+tab back to the browser.

Alt+tab is registered as keyboard navigation, and focus ring becomes visible.


[resolves #739] Ignore paths exported from org.wildfly.camel.extras

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/527/
Test FAILed.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/528/
Test PASSed.


ci: test new rhel-bootc snapshot with bootc-0.1.9 installed

I don't understand how that file does anything?

I don't understand how that file does anything?

The file does nothing, just a new file for PR create and run test with /test-rhel9y-snapshot.


@aspnet/signalr not working IE11

Please include as much of the following as you can in your bug report

Versions of Client-Side NuGet/NPM Packages:

 "@angular/animations": "^5.1",
    "@angular/common": "^5.1",
    "@angular/core": "^5.1",
    "@angular/forms": "^5.2.4",
    "@angular/platform-browser": "^5.1",
    "@angular/platform-browser-dynamic": "^5.1",
    "@angular/router": "^5.2.9",
    "@aspnet/signalr": "^1.0.0-preview2-final",
    "@camco/common": "^1.0.0",
    "@turf/turf": "^5.1.6",
    "@types/d3": "^5.0.0",
    "@types/materialize-css": "^1.0.1",
    "@types/ol": "^4.6.1",
    "core-js": "^2.5.3",
    "d3": "^5.0.0",
    "keysim": "^2.0.0",
    "materialize-css": "1.0.0-alpha.4",
    "ol": "^4.6.4",
    "rxjs": "^5.5.6",
    "zone.js": "^0.8.20"

Are you using the C# client or the JavaScript client:
javascript client
The Server you are using (Kestrel/HttpSysServer/IIS/IIS Express/Azure Web App/etc.):
Kestrel
The Operating System on the Server (Windows/Linux/macOS):
Windows
The Operating System on the Client (Windows/Linux/macOS):
Windows
The Browser on the client, if using the JavaScript client (IE/Chrome/Edge/Firefox/etc.):
IE

While developing an application using the Angular CLI (version 5), the application does not seem to start in Internet Explorer while working perfectly fine in Firefox and Chrome.
When attempting to run the application in Internet Explorer 11 after including @aspnet/signalr throws a syntax error (see screenshots below):

The code used to include SignalR is shown below:
import { HubConnection } from '@aspnet/signalr';

export class Hub {

	protected connection: HubConnection;

	constructor(url: string) {
		this.connection = new HubConnection(url);
	}

	public connect(reconnect: () => void, onConnectionSucces: () => void, setConnected: (connected: boolean) => void, retry: number) {
		this.connection.onclose(() => {
			setConnected(false);
			setTimeout(reconnect, retry);
		});

		this.connection.start()
			.then(() => {
				onConnectionSucces();
				setConnected(true);
			})
			.catch(() => {
				setConnected(false);
				setTimeout(reconnect, retry);
			});
	}

	protected on(eventName: string, callback: (...msg: any[]) => void) {
		this.connection.on(eventName, callback);
	}
}

Try upgrading to rc1 or later

IE 11 requires using the ECMAScript 5 build. In Preview 2, the "module" version (which you are using via import) required ECMAScript 6. In RC1 we made all builds of the package ES5.

Is there a way to switch to the ES5 build on preview 2 without upgrading to the RC1 build, which also requires upgrading the .NET framework etc (which is currently not exactly a viable option for me)?

@dealloc staying on preview2 isn't a viable option either. I'm not sure what you're expecting here. What's your actual plan to get bug fixes past preview2 there are LOTS of them?

We don't want to upgrade our back-end at the moment, this would mean we need to upgrade multiple projects and we did this just last month. Our plan is to upgrade when we have more time. How do you use the ES5 build for preview2?

I'm going to close this issue as there isn't something to fix for our next release (since our most recent release supports IE 11 fully). We can continue discussing things in this issue, I just want to make sure our issue tracking is up-to-date.
You can reference the ES5 version directly from an ECMAScript/TypeScript Module using this syntax: import { ... } from "@aspnet/signalr/dist/browser/signalr".
As @davidfowl indicated though, this is definitely not a viable option in any production deployment. There are many issues in Preview 2 that were fixed in RC1. Upgrading should be as simple as updating package versions, and if it's more complicated than that, we'd love to hear about any issues you're hitting!

Understandable; it's not for production at the moment we're in the stage of building a POC and updating the versions every couple days isn't really boosting productivity :)
Though I don't think it'll be as simple as simply updating a package since I'm assuming the backend would need to be updated as well and if SignalR versioning is following the .NET versioning that would mean we have to retarget to the newer .NET versions and update the backend, which is obviously a lot more work than "just" updating a NPM package.
If I'm wrong in assuming so however, and it's really just updating the NPM package then please do correct me :)

Every couple of days? The rc1 build just came out and this is one of the issues we fixed.
You need to update both server and client to rc1 of asp.net Core. If that’s too much for your POC then maybe you should wait for the RTM since there are other known bugs that might bite you.

Also, the APIs have changed between preview2 and the rc so you’ll need to account for that too.


download_sra searches by project ID not accession

The workflow asks for an accession, but the code ultimately retrieves using the provided accession as an uID.
There probably needs to be an esearch step to search the bioproject DB by accession to get the uID, then retrieve the project.

This is entirely correct, thank you for noting this. I had forgotten about this particular bug in the code, but it rings a bell now that you mention it. I think this may have been too challenging for me to tackle, initially.

Closed by 1e201d09fbc0195eee770af1ea907b87adc5255c


image's link "http://localhost/cdn..." on production

After deploying my app on production server, all image links stopped working.
Links look like http://localhost/cdn/storage/Images/zwf7bGsqbGzA/original/zwf7pcabGzA.jpg.
But if i manually change it to http://mysite.com/cdn/storage/Images/zwf7bGsqbGzA/original/zwf7pcabGzA.jpg, such link viewed as expected.
I get them by:
<img src="{{imageFile id}}"
from helper:
imageFile(id) {
    let imgFile = Images.findOne({_id:id});
    if (imgFile) return imgFile.link();
  }

in local dev app all images viewed also ok,
maybe you have thought over this case?

Hi @valorloff
Have you set ROOT_URL=http://mtsite.com env.var ?

@valorloff also you don't need to create a helper, there one defined for you - {{fileURL file}}, read more - https://github.com/VeliovGroup/Meteor-Files/wiki/Template-Helper

@valorloff is this solved on your end?

Yes!
Big thank for your help and wiki!
Is it true that the maximum number of files in storagePath should not exceed 10k?

for the purpose of move to "fileURL" i changed my helper to:
imageRef() {
   return Images.findOne();
 }

in template:
<img src="{{fileURL imageRef 'thumb'}}"
don"t show image, what's wrong?

Is it true that the maximum number of files (for performance reasons) in storagePath should not exceed 10k?

Where this statement came from? This is depends form FileSystem, read this SO thread
If you think you might hit the limits, there is two options:

Use 3rd party storage, like in DB GridFS or AWS, etc.;
Check this answer where I give a solution to build deep folder structure.

Hello @valorloff ,
Can we close this issue? Is it solved on your end?

Closed due to silence at issue owner end.


Make the footer section more interactive with CSS Styling and Animations

The footer section looks static and less responsive and providing a less dynamic user experience.
@Harshdev098
I would like to make the footer section more interactive and dynamic by adding more CSS Styling and Animations. Making sure to make it more responsive and user friendly for the website. Something similar like this--

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

Hey @Harshdev098 could you assign me this issue. if it is not attempted and still open.


entrypoint script?

How would I run an entrypoint script from Dockerfile using goruntime?
When I try, I get error exec: "/bin/sh": stat /bin/sh: no such file or directory

You can't run entrypoint scripts because it doesn't include a shell. You'll need to use the ENTRYPOINT ["/bin"] syntax which doesn't need a shell.

Thanks. I ended up doing this instead: CMD ["/usr/bin/busybox","ash","/entrypoint.sh"]


chore(sequence): Adding both parallel/serial sequence in all pod-level experiments

Signed-off-by: shubhamchaudhary<EMAIL_ADDRESS>
container-kill in docker :heavy_check_mark:
container-kill in containerd :heavy_check_mark:
disk-fill :heavy_check_mark:
network-chaos docker :heavy_check_mark:
network chaos containerd :heavy_check_mark:
pod-delete :heavy_check_mark:
cpu pumba :heavy_check_mark:
mm pumba :heavy_check_mark:
pod-io-stress :heavy_check_mark:

/run-e2e


Remove Error for sequences < 20000 bp

Hi,
I'm trying to run Phigaro in batch from custom scripts, but I am failing because it gives me the following message:
Error! Your fasta file contains at least one sequence length < 20000.  The short sequences are:

Do you want to start Phigaro without these sequences? [Y/n]

This is causing me to have to filter these sequences prior to running Phigaro. Would it be able to implement an argument to the main Phigaro CLI script to simply ignore this error? Any workarounds are appreciated :)
Thank you for any assistance you can provide,
V

At version 2.1.9 you can find the parameter -d or --delete-shorts that allows you to exclude short sequences automatically.


voyager:install --with-dummy fails on [zh_CN] locale

voyager:install --with-dummy fails on [zh_CN] locale #3497

I haven't seen any other complaints about this, nor am I overly fond of this "solution".  I'm going to close this for now.  If it's still a problem and there's enough interest, we can revisit it then


Reduce code duplication on layouts default and with_twitter_card

The two layouts are virtually the same, with the exception of the part dedicated to twitter metadata.
If I find a way of reusing it in a backwards compatible way (my feeling tells me it would be hard, but maybe not) I will post here and possibly send a PR.

Fancy getting part of the Github jekyll-octopod team?

Sounds like a nice idea, I'm in.


Exporting LLama2-7B isn't  working.

System Info
Here is the info on GPU drivers and cuda:

+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 545.23.08              Driver Version: 545.23.08    CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA A100-SXM4-80GB          Off | 00000000:00:05.0 Off |                    0 |
| N/A   27C    P0              56W / 400W |    139MiB / 81920MiB |      0%      Default |
|                                         |                      |             Disabled |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      1156      G   /usr/lib/xorg/Xorg                           73MiB |
|    0   N/A  N/A      1950      G   /usr/bin/gnome-shell                         36MiB |
|    0   N/A  N/A      2529      G   /usr/libexec/gnome-initial-setup              6MiB |
+---------------------------------------------------------------------------------------+

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Fri_Nov__3_17:16:49_PDT_2023
Cuda compilation tools, release 12.3, V12.3.103
Build cuda_12.3.r12.3/compiler.33492891_0

Here are the library versions:
torch: '2.1.2+cu121'
transformers: '4.36.1'
onnx: 1.15.0

What all I install?
torch
optimum[exporters]
optimum[onnxruntime]
optimum

### Who can help?

@JingyaHuang @echarlaix

### Information

- [X] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction (minimal, reproducible, runnable)

I ran this script:

```bash
optimum-cli export onnx \
--model "$LLAMA_HF_MODEL_DIR" --task text-generation-with-past --framework pt \
--opset 17 --sequence_length 1024 --batch_size 1 --device cuda --fp16 \
"$LLAMA_ONNX_MODEL_DIR" > /dev/null

Where inside LLAMA_HF_MODEL_DIR includes the following file:
models/llama-2-7b-hf
├── config.json
├── generation_config.json
├── model-00001-of-00002.safetensors
├── model-00002-of-00002.safetensors
├── model.safetensors.index.json
├── pytorch_model-00001-of-00002.bin
├── pytorch_model-00002-of-00002.bin
├── pytorch_model.bin.index.json
├── special_tokens_map.json
├── tokenizer_config.json
├── tokenizer.json
└── tokenizer.model

Running the above produced the following output:
Virtual environment '/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv' created.
Loading checkpoint shards: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████| 2/2 [00:02<00:00,  1.17s/it]
Using the export variant default. Available variants are:
    - default: The default ONNX variant.
Using framework PyTorch: 2.1.2+cu121
Overriding 1 configuration item(s)
        - use_cache -> True
/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/transformers/modeling_attn_mask_utils.py:114: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if (input_shape[-1] > 1 or self.sliding_window is not None) and self.is_causal:
/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/exporters/onnx/model_patcher.py:299: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if past_key_values_length > 0:
/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:150: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if seq_len > self.max_seq_len_cached:
/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/transformers/models/llama/modeling_llama.py:714: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
  if attention_mask.size() != (bsz, 1, q_len, kv_seq_len):
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
In-place op on output of tensor.shape. See https://pytorch.org/docs/master/onnx.html#avoid-inplace-operations-when-using-tensor-shape-in-tracing-mode
Traceback (most recent call last):
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/bin/optimum-cli", line 8, in <module>
    sys.exit(main())
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/commands/optimum_cli.py", line 163, in main
    service.run()
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/commands/export/onnx.py", line 246, in run
    main_export(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/exporters/onnx/__main__.py", line 551, in main_export
    _, onnx_outputs = export_models(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/exporters/onnx/convert.py", line 753, in export_models
    export(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/exporters/onnx/convert.py", line 856, in export
    export_output = export_pytorch(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/optimum/exporters/onnx/convert.py", line 573, in export_pytorch
    onnx_export(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/utils.py", line 516, in export
    _export(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/utils.py", line 1596, in _export
    graph, params_dict, torch_out = _model_to_graph(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/utils.py", line 1139, in _model_to_graph
    graph = _optimize_graph(
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/utils.py", line 677, in _optimize_graph
    graph = _C._jit_pass_onnx(graph, operator_export_type)
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/utils.py", line 1940, in _run_symbolic_function
    return symbolic_fn(graph_context, *inputs, **attrs)
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/symbolic_helper.py", line 306, in wrapper
    return fn(g, *args, **kwargs)
  File "/home/paperspace/workspace/benchmarks/bench_onnxruntime/venv/lib/python3.9/site-packages/torch/onnx/symbolic_opset14.py", line 197, in scaled_dot_product_attention
    raise ValueError(
ValueError: Unsupported type for attn_mask: 5

Expected behavior
Although it did make a folder and inside that the following files were there:
models/llama-2-7b-onnx/
├── config.json
├── generation_config.json
├── special_tokens_map.json
├── tokenizer_config.json
├── tokenizer.json
└── tokenizer.model

Expected behaviour was along with those files, there should be an onnx file present.

Even I ran this command:
optimum-cli export onnx --model daryl149/llama-2-7b-chat-hf --device cuda --fp16 --no-post-process llama2_onnx

As mentioned in issue #1248
However, I got the same error, as mentioned above.

I've got the same problem with some models (TinyLlama-1.1B) and the recent updates, but works with previous version of ORT and transformers and PT

I've got the same problem with some models (TinyLlama-1.1B) and the recent updates, but works with previous version of ORT and transformers and PT

Hey can you please mention the specifics for the versions you were using in which it works.

Thank you @Anindyadeep @claeyzre this is a missing feature in PyTorch, which as of 2.1 specifically can not export to ONNX the scaled_dot_product_attention operator to ONNX on CUDA device using fp16, see: https://github.com/pytorch/pytorch/issues/109336
transformers>=4.36 now by default uses SDPA, hence the issue.
I checked, this is indeed fixed using pytorch nightly (hopefully included in pytorch 2.2).

I see, thank you @fxmarty for the update. Will try with 2.2.


DFP-34X-2C2 stuck in O5/Initial Status

First, thanks, Anime4000, for your work in reverse engineering PON sticks and for the amazing amount of documentation you wrote.
I am a seasoned Linux sys and net admin, but I am new to the PON ecosystem.
I'm trying to configure a DFP-34X-2C2 as a replacement for Huawei HG8010Hv3 for the French internet provider Bouygues Telecom. I have somewhat documented the process (in French) on https://lafibre.info/remplacer-bbox/routeur-sfp-pour-remplacer-bbox-fibre-ont/msg1046274/#msg1046274
I reached the point where the stick reports ONU State: O5, LOID Status: Initial Status.

As far as I understand from MIB 131, the stick has established a connection with the remote OLT:
# omcicli mib get 131
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
OltG
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
=================================
EntityId: 0x00
OltVendorId: 0x48575443
EquipId:
Version: 10
ToDInfo:
	Sequence number of GEM superframe: 0x0
	Timestamp: secs 0, nanosecs 0
=================================

I started to examine omcilog with Wireshark using the Lua dissector found on https://wiki.wireshark.org/Contrib#Protocol_Dissectors. However, I don't know where to go from there. What should I look for? What would be the next steps in diagnosing my issue?
FWIW, here are a few pieces of information I gathered regarding my ISP:

Authentication is through PLOAM password
ONU is in bridge mode
On the LAN side, the traffic is wrapped in VLAN 100. WAN-side, I don't know.

O5 means connection with OLT is fine. You can proceed with PPPoE connection or whatever your provider use.
In case of PPPOE wrapped in VLAN: omcicli mib get 84 to get VLANs.
You can find VLAN map table on original router.

Thanks for the reply, rndm2.
I was puzzled by the message [tt]Initial Status[/tt].
Since my initial message, I read more about OMCI in https://wiki-archive.opencord.org/attachments/1966449/2557137.pdf
According to MIB 256 "CredentialsStatus", I am in the "Initial State, status indeterminate":
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Ontg
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
=================================
EntityID: 0x00
VID: HWTC
Version: 17C6.A
SerialNum: HWTCa1a867a0
TraffMgtOpt: 2
AtmCCOpt: 0
BatteryBack: 1
AdminState: 0
OpState: 0
OnuSurvivalTime: 0
LogicalOnuID:
LogicalPassword:
CredentialsStatus: 0
ExtendedTcLayerOptions: 0x0
OntState: 1
=================================

As far as I understand, I have not yet been authenticated with the OLT. Otherwise, CredentialStatus should be 1 ("successful authentication").
Is my understanding correct? Do you know how to trigger the authentication? Or should this be triggered when I initiate the PPPoE connection?

What MIB 84 says now?
In my case (I am in Spain) I don’t need to authenticate. O5 is enough.

7 déc. 2023 00:38:06 rndm2 @.***>:

This is what I have now:
`
omcicli mib get 131
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
OltG
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
EntityId: 0x00
OltVendorId: 0x414c434c
EquipId:
Version:
ToDInfo:
Sequence number of GEM superframe: 0x0
Timestamp: secs 0, nanosecs 0
omcicli mib get 256
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Ontg
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
EntityID: 0x00
VID: RTKG
Version: RTL960x
SerialNum: RTKG11111111
TraffMgtOpt: 2
AtmCCOpt: 0
BatteryBack: 0
AdminState: 0
OpState: 0
OnuSurvivalTime: 0
LogicalOnuID:
LogicalPassword:
CredentialsStatus: 0
ExtendedTcLayerOptions: 0x0
OntState: 1
omcicli mib get 84
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
VlanTagFilterData
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
EntityID: 0x1102
FilterTbl[0]: PRI 0,CFI 0, VID 1370
FwdOp: 0x10
NumOfEntries: 1
=================================
EntityID: 0x1103
FilterTbl[0]: PRI 0,CFI 0, VID 6
FwdOp: 0x10
NumOfEntries: 1
=================================
EntityID: 0x1104
FilterTbl[0]: PRI 0,CFI 0, VID 3
FwdOp: 0x10
NumOfEntries: 1
=================================
EntityID: 0x110b
FilterTbl[0]: PRI 0,CFI 0, VID 3
FilterTbl[2]: PRI 0,CFI 0, VID 6
FwdOp: 0x10
NumOfEntries: 2
`
In my case internet in VLAN 1370
—
Reply to this email directly, view it on GitHub[https://github.com/Anime4000/RTL960x/issues/218#issuecomment-1843861258], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAMZ47QGZVPLMFICQCJGIWTYID6VZAVCNFSM6AAAAABAJSATUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTHA3DCMRVHA].
You are receiving this because you authored the thread.[Image de pistage][https://github.com/notifications/beacon/AAMZ47Q6I6HJBQUOS77BQ4DYID6VZA5CNFSM6AAAAABAJSATUCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTN44LQU.gif]

Thanks for those pieces of information. I found that document (for a different RTL960x-based ONU, I think) that also suggests "LOID Status 在 Initial Status" is good enough: @.***/SJUEdj6oq
I will try to find some time today to experiment in that direction.
Regards,
–Sylvain

What MIB 84 says now? In my case (I am in Spain) I don’t need to authenticate. O5 is enough.

Here is MIB 84 as of yesterday:
MIB: 00084

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
VlanTagFilterData
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
=================================
EntityID: 0x01
FilterTbl[0]: PRI 0,CFI 0, VID 10
FwdOp:  0x04
NumOfEntries: 1
=================================
=================================
EntityID: 0x02
FilterTbl[0]: PRI 0,CFI 0, VID 100
FwdOp:  0x04
NumOfEntries: 1
=================================
=================================
EntityID: 0x03
FilterTbl[0]: PRI 0,CFI 0, VID 10
FilterTbl[2]: PRI 0,CFI 0, VID 100
FwdOp:  0x04
NumOfEntries: 2
=================================

Presumably, the Internet is on VLAN 100 (same as LAN-side).
I haven't seen the VLAN 10 mentioned anywhere for Bouygues Telecom. I wonder what it could be.

Try to look for PPPoE on VLAN 100 or run DHCP client depending on how your provider works.


Bump SDK version and Juno v7 -> v8

We got stung by this bug during an upgrade:
https://github.com/cosmos/cosmos-sdk/issues/11707
The fix appears to land in 0.45.6 of the SDK - https://github.com/cosmos/cosmos-sdk/pull/12264
So we need to upgrade to 0.45.6, and increment Juno version from v7 to v8, as this is a consensus breaking change.

I will let CI finish then smash the merge button since we've got 3 approving reviews.


Gemnasium badge fails (sometimes)

Every now and then the Gemnasium badge shows a gray "invalid".
This is sometimes working, and sometimes not. Saw it as "invalid" more than once.
This is the URL I am using:

Saw this issue was mentioned and closed in the past in #591

Hi, we found a node of our cluster responding with 502 errors, and not being detected after several days, causing some badges to fail rendering. It was fixed, and you should not see intermittent "invalid" badges now. I think you can close this, and reopen if the problem occurs again.
Thanks, and sorry for that!

Excellent, thanks.


add encoding as parameter

It needs an extra parameter to set encoding in load_userdict().
The default encoding of open() in Python depends on system (or shell); it may be utf-8 on Linux while ANSI on Windows (cmd.exe).
Sometimes it will cause an error.
For example, if there is a file encoded in UTF-8, then it cannot open by fool.load_userdict() on Windows.

have you test on linux ?

Yes.


feat: add course_key to block dictionary (FC-0033)

This adds course_key to course_block_names_dict and course_block_names so that this table may easily be joined to course_names

Thanks for the pull request, @SoryRawyer!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@SoryRawyer 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


Tag releases

You have a single tag for an old release -- it would be really useful if each release (or at least the current and all future releases) had a tag.

This is fixed now.  I added tags/releases for all the versions I could dig up and I'll keep doing so going forward


Upgrade ruff to v0.1.7

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (b5b592d) 77.12% compared to head (2baa809) 77.12%.

Additional details and impacted files
@@              Coverage Diff               @@
##           release/0.0.x     #201   +/-   ##
==============================================
  Coverage          77.12%   77.12%
==============================================
  Files                 45       45
  Lines               2348     2348
==============================================
  Hits                1811     1811
  Misses               537      537

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


Installation Issue

I am trying to install the latest version of this plugin on Bolt 2.2.23, and am unable to do it.  Here is the information composer is sending back:
Composer Error

Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for bolt/members v2.1.2 -> satisfiable by bolt/members[v2.1.2].
    - bolt/members v2.1.2 requires bolt/clientlogin >=2.0.0,<2.2.0 -> no matching package found.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see this link for more details.

Read this link for further common problems.

Can you help me with this?

The library that ClientLogin ran under was so badly broken. So it had to go bye-bye :smile:
Short version, there is no version that will run on Bolt 2. The dev-master version of Members we use a bit now, and it is running the extensions marketplace site's author identity management and login. But requires Bolt 3 due to some rather major internal improvements.

Thank you very much.  Since I am starting to develop the website,  I will use Bolt 3 and your dev-master.  Thank you for your help and fast reply. :-)

Just a heads up, docs are light, I just haven't had the time :disappointed:

No problem.  I totally know the feeling.


Hangs after receiving charging-set-amps CMD when car is not home

I've used the BLE MQTT Docker with a Model 3 since its conception and it's been rock solid. A couple of weeks ago I replaced the Model 3 with a Model Y and since then I have experienced multiple "hangs" of the server.
When it is hanged it does not detect car presence (always OFF) nor reponds to MQTT commands.
After reviewing the logs from a couple of hangs, I believe this is what happens:

Car is home. Everything works.
Car leaves home. Presence OFF just as it should.
While the car is gone, the server receives an MQTT charging-set-amps command. (Obviously a bug in my automation system, but hey, it shouldn't cause any trouble?)
Server enters a loop trying to wake the car.
After about 30 minutes, the server stops trying to wake the car.
At this time the server is "hanged". When car comes home, presence is still OFF. When sending MQTT commands, server does not respond.

Here are my logs for the last time this happened.
#
# Car is home and everything is OK
#
2024-12-28T11:54:58.270465011Z vin:XXXXXXXXXXXXXXX ble_ln:xxxxxxxxxxxxxxxxxxx match:(xxxxxxxxxxxxxxxxxxx|XX:XX:XX:XX:XX:XX) presence detected
2024-12-28T11:57:08.689426194Z vin:XXXXXXXXXXXXXXX ble_ln:xxxxxxxxxxxxxxxxxxx match:(xxxxxxxxxxxxxxxxxxx|XX:XX:XX:XX:XX:XX) presence detected
2024-12-28T11:59:19.107579824Z vin:XXXXXXXXXXXXXXX ble_ln:xxxxxxxxxxxxxxxxxxx match:(xxxxxxxxxxxxxxxxxxx|XX:XX:XX:XX:XX:XX) presence detected
2024-12-28T12:01:29.524649071Z vin:XXXXXXXXXXXXXXX ble_ln:xxxxxxxxxxxxxxxxxxx match:(xxxxxxxxxxxxxxxxxxx|XX:XX:XX:XX:XX:XX) presence detected
#
# Car leaves home
#
2024-12-28T12:03:39.941065548Z vin:XXXXXXXXXXXXXXX ble_ln:xxxxxxxxxxxxxxxxxxx presence not expired
2024-12-28T12:05:50.357973012Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:08:00.796911236Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:10:11.226176503Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:12:21.655454838Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:14:32.084902503Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:16:42.514437730Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:18:52.988929567Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:21:03.422406496Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:23:13.851375179Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:25:24.279953304Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:27:34.708008779Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:29:45.138534771Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:31:55.566005066Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:34:05.994961370Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:36:16.428326689Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:38:26.855834889Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:40:37.286944052Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:42:47.717762499Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:44:58.146458432Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:47:08.575259238Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:49:19.002206277Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:51:29.438974742Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:53:39.875217083Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:55:50.309143360Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T12:58:00.738579712Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:00:11.167666345Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:02:21.595129916Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:04:32.032660869Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:06:42.463248430Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:08:52.893397127Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:11:03.325021445Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:13:13.755417150Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:15:24.184643551Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:17:34.614514791Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:19:45.043526621Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:21:55.473417834Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:24:05.911243328Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:26:16.340535180Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:28:26.766529447Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:30:37.201658074Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:32:47.632243788Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:34:58.059401534Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:37:08.491658119Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:39:18.960713117Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:41:29.389706604Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:43:39.819020935Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:45:50.248640446Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:48:00.677674754Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:50:11.106053669Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:52:21.534559015Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:54:31.962783840Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:56:42.392383700Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T13:58:52.823373627Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:01:03.255498068Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:03:13.685746865Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:05:24.118040980Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:07:34.546038260Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:09:44.975820630Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:11:55.404318633Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:14:05.834610854Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:16:16.264842238Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:18:26.693886639Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:20:37.122248106Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:22:47.550921516Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:24:57.985577767Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:27:08.415393539Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:29:18.844881469Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:31:29.282098581Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:33:39.717718047Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:35:50.147703977Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:38:00.575670378Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:40:11.004489386Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:42:21.432704468Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:44:31.870495218Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:46:42.301444552Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:48:52.729516382Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:51:03.160186253Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:53:13.590372486Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:55:24.020628255Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:57:34.451206870Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T14:59:44.921423134Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:01:55.361091024Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:04:05.790106105Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:06:16.220468810Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:08:26.650030186Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:10:37.080528925Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:12:47.516937492Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:14:57.946683527Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:17:08.377054462Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:19:18.808457700Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:21:29.235593456Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:23:39.665097552Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF

#
# Spurious command received from my home automation system.
#

2024-12-28T15:23:48.090973665Z Received MQTT message; topic:tesla_ble/XXXXXXXXXXXXXXX/charging-set-amps msg:7 vin:XXXXXXXXXXXXXXX cmd:charging-set-amps
2024-12-28T15:23:48.091505646Z Attempt 1/5 sending Set charging Amps to 7 to vin:XXXXXXXXXXXXXXX command:charging-set-amps 7
2024-12-28T15:24:08.101629410Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:24:08.101668132Z Vehicle might be asleep
2024-12-28T15:24:08.101675725Z Trying to wake up car then launch the command again
2024-12-28T15:24:08.102273205Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:24:28.116981485Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:24:28.117031596Z Vehicle might be asleep
2024-12-28T15:24:28.117039911Z Trying to wake up car then launch the command again
2024-12-28T15:24:28.117664743Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:24:48.133910712Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:24:48.133954546Z Vehicle might be asleep
2024-12-28T15:24:48.133962472Z Trying to wake up car then launch the command again
2024-12-28T15:24:48.134910970Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:25:08.151840834Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:25:08.151892408Z Vehicle might be asleep
2024-12-28T15:25:08.151901371Z Trying to wake up car then launch the command again
2024-12-28T15:25:08.152623462Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:25:28.169501538Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:25:28.169552649Z Vehicle might be asleep
2024-12-28T15:25:28.169561649Z Trying to wake up car then launch the command again
2024-12-28T15:25:28.170602277Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:25:48.181094241Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:25:48.181139334Z Vehicle might be asleep
2024-12-28T15:25:48.181147037Z Trying to wake up car then launch the command again
2024-12-28T15:25:48.182947257Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:25:50.089103667Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:26:08.191300345Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:26:08.191358364Z Vehicle might be asleep
2024-12-28T15:26:08.191371327Z Trying to wake up car then launch the command again
2024-12-28T15:26:08.192083918Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:26:28.198770039Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:26:28.198818409Z Vehicle might be asleep
2024-12-28T15:26:28.198826465Z Trying to wake up car then launch the command again
2024-12-28T15:26:28.200272574Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:26:48.208797704Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:26:48.208840055Z Vehicle might be asleep
2024-12-28T15:26:48.208848241Z Trying to wake up car then launch the command again
2024-12-28T15:26:48.209586128Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:27:08.218169365Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:27:08.218224809Z Vehicle might be asleep
2024-12-28T15:27:08.218233624Z Trying to wake up car then launch the command again
2024-12-28T15:27:08.218814234Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:27:28.235727084Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:27:28.235775102Z Vehicle might be asleep
2024-12-28T15:27:28.235784991Z Trying to wake up car then launch the command again
2024-12-28T15:27:28.237003212Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:27:48.245036125Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:27:48.245091570Z Vehicle might be asleep
2024-12-28T15:27:48.245101218Z Trying to wake up car then launch the command again
2024-12-28T15:27:48.245790606Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:28:00.513496808Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:28:08.261435506Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:28:08.261486302Z Vehicle might be asleep
2024-12-28T15:28:08.261493247Z Trying to wake up car then launch the command again
2024-12-28T15:28:08.262268227Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:28:28.277896200Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:28:28.277947941Z Vehicle might be asleep
2024-12-28T15:28:28.277957367Z Trying to wake up car then launch the command again
2024-12-28T15:28:28.280255512Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:28:48.285433757Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:28:48.285490998Z Vehicle might be asleep
2024-12-28T15:28:48.285503572Z Trying to wake up car then launch the command again
2024-12-28T15:28:48.286420756Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:29:08.298194788Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:29:08.298246492Z Vehicle might be asleep
2024-12-28T15:29:08.298254288Z Trying to wake up car then launch the command again
2024-12-28T15:29:08.299874397Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:29:28.309876655Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:29:28.309924951Z Vehicle might be asleep
2024-12-28T15:29:28.309934266Z Trying to wake up car then launch the command again
2024-12-28T15:29:28.311643671Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:29:48.327861236Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:29:48.327947902Z Vehicle might be asleep
2024-12-28T15:29:48.327961735Z Trying to wake up car then launch the command again
2024-12-28T15:29:48.328926160Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:30:08.335876146Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:30:08.335924535Z Vehicle might be asleep
2024-12-28T15:30:08.335962276Z Trying to wake up car then launch the command again
2024-12-28T15:30:08.336590738Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:30:10.938369509Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:30:28.345763076Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:30:28.345815909Z Vehicle might be asleep
2024-12-28T15:30:28.345823168Z Trying to wake up car then launch the command again
2024-12-28T15:30:28.346506186Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:30:48.363246591Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:30:48.363298109Z Vehicle might be asleep
2024-12-28T15:30:48.363306905Z Trying to wake up car then launch the command again
2024-12-28T15:30:48.364095238Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:31:08.382407865Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:31:08.382458495Z Vehicle might be asleep
2024-12-28T15:31:08.382468976Z Trying to wake up car then launch the command again
2024-12-28T15:31:08.383283457Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:31:28.389934179Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:31:28.389985383Z Vehicle might be asleep
2024-12-28T15:31:28.389995087Z Trying to wake up car then launch the command again
2024-12-28T15:31:28.390819752Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:31:48.406503022Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:31:48.406551744Z Vehicle might be asleep
2024-12-28T15:31:48.406561151Z Trying to wake up car then launch the command again
2024-12-28T15:31:48.407305965Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:32:08.426752012Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:32:08.426804420Z Vehicle might be asleep
2024-12-28T15:32:08.426814253Z Trying to wake up car then launch the command again
2024-12-28T15:32:08.428119084Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:32:21.361284065Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:32:28.442534942Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:32:28.442578757Z Vehicle might be asleep
2024-12-28T15:32:28.442584701Z Trying to wake up car then launch the command again
2024-12-28T15:32:28.443329941Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:32:48.459703894Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:32:48.459759561Z Vehicle might be asleep
2024-12-28T15:32:48.459771061Z Trying to wake up car then launch the command again
2024-12-28T15:32:48.460617615Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:33:08.468444735Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:33:08.468493235Z Vehicle might be asleep
2024-12-28T15:33:08.468501235Z Trying to wake up car then launch the command again
2024-12-28T15:33:08.469371919Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:33:28.485122040Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:33:28.485175355Z Vehicle might be asleep
2024-12-28T15:33:28.485184133Z Trying to wake up car then launch the command again
2024-12-28T15:33:28.485907187Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:33:48.497908166Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:33:48.497956314Z Vehicle might be asleep
2024-12-28T15:33:48.497963702Z Trying to wake up car then launch the command again
2024-12-28T15:33:48.498965256Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:34:08.507775717Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:34:08.508517993Z Vehicle might be asleep
2024-12-28T15:34:08.508554271Z Trying to wake up car then launch the command again
2024-12-28T15:34:08.508833993Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:34:28.516001540Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:34:28.516054781Z Vehicle might be asleep
2024-12-28T15:34:28.516063540Z Trying to wake up car then launch the command again
2024-12-28T15:34:28.517583908Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:34:31.785706164Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:34:48.523792075Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:34:48.523841020Z Vehicle might be asleep
2024-12-28T15:34:48.523856983Z Trying to wake up car then launch the command again
2024-12-28T15:34:48.525044259Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:35:08.541658416Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:35:08.541711730Z Vehicle might be asleep
2024-12-28T15:35:08.541822804Z Trying to wake up car then launch the command again
2024-12-28T15:35:08.542207470Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:35:28.557766485Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:35:28.557815577Z Vehicle might be asleep
2024-12-28T15:35:28.557825503Z Trying to wake up car then launch the command again
2024-12-28T15:35:28.558524502Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:35:48.574396220Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:35:48.574446831Z Vehicle might be asleep
2024-12-28T15:35:48.574456776Z Trying to wake up car then launch the command again
2024-12-28T15:35:48.575788625Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:36:08.592461860Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:36:08.592502175Z Vehicle might be asleep
2024-12-28T15:36:08.592509119Z Trying to wake up car then launch the command again
2024-12-28T15:36:08.593314822Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:36:28.608936277Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:36:28.608975314Z Vehicle might be asleep
2024-12-28T15:36:28.608982166Z Trying to wake up car then launch the command again
2024-12-28T15:36:28.609350813Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:36:42.209332387Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:36:48.615575648Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:36:48.615629259Z Vehicle might be asleep
2024-12-28T15:36:48.615636407Z Trying to wake up car then launch the command again
2024-12-28T15:36:48.617225219Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:37:08.623727954Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:37:08.623790880Z Vehicle might be asleep
2024-12-28T15:37:08.623801435Z Trying to wake up car then launch the command again
2024-12-28T15:37:08.624845674Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:37:28.639221110Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:37:28.639280536Z Vehicle might be asleep
2024-12-28T15:37:28.639325369Z Trying to wake up car then launch the command again
2024-12-28T15:37:28.640078312Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:37:48.649223042Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:37:48.650598947Z Vehicle might be asleep
2024-12-28T15:37:48.650638965Z Trying to wake up car then launch the command again
2024-12-28T15:37:48.650646965Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:38:08.665985765Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:38:08.666096117Z Vehicle might be asleep
2024-12-28T15:38:08.666113246Z Trying to wake up car then launch the command again
2024-12-28T15:38:08.666902653Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:38:28.682486938Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:38:28.682541512Z Vehicle might be asleep
2024-12-28T15:38:28.682549901Z Trying to wake up car then launch the command again
2024-12-28T15:38:28.683562917Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:38:48.699228168Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:38:48.699265039Z Vehicle might be asleep
2024-12-28T15:38:48.699271279Z Trying to wake up car then launch the command again
2024-12-28T15:38:48.699718594Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:38:52.643288205Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:39:08.709633984Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:39:08.709676187Z Vehicle might be asleep
2024-12-28T15:39:08.709682428Z Trying to wake up car then launch the command again
2024-12-28T15:39:08.711362185Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:39:28.717425433Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:39:28.717476433Z Vehicle might be asleep
2024-12-28T15:39:28.717485470Z Trying to wake up car then launch the command again
2024-12-28T15:39:28.719134486Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:39:48.735654050Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:39:48.736525622Z Vehicle might be asleep
2024-12-28T15:39:48.736561956Z Trying to wake up car then launch the command again
2024-12-28T15:39:48.737557658Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:40:08.745930657Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:40:08.745991453Z Vehicle might be asleep
2024-12-28T15:40:08.746001564Z Trying to wake up car then launch the command again
2024-12-28T15:40:08.746775397Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:40:28.763667212Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:40:28.764549451Z Vehicle might be asleep
2024-12-28T15:40:28.764572692Z Trying to wake up car then launch the command again
2024-12-28T15:40:28.766156078Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:40:48.773845568Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:40:48.774075142Z Vehicle might be asleep
2024-12-28T15:40:48.774127864Z Trying to wake up car then launch the command again
2024-12-28T15:40:48.774794345Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:41:03.069248306Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:41:08.792274109Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:41:08.792325424Z Vehicle might be asleep
2024-12-28T15:41:08.792341017Z Trying to wake up car then launch the command again
2024-12-28T15:41:08.793194941Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:41:28.808820591Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:41:28.808870091Z Vehicle might be asleep
2024-12-28T15:41:28.808880461Z Trying to wake up car then launch the command again
2024-12-28T15:41:28.810912921Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:41:48.825944617Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:41:48.825994968Z Vehicle might be asleep
2024-12-28T15:41:48.826002228Z Trying to wake up car then launch the command again
2024-12-28T15:41:48.826920189Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:42:08.843753558Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:42:08.843810373Z Vehicle might be asleep
2024-12-28T15:42:08.843823188Z Trying to wake up car then launch the command again
2024-12-28T15:42:08.844547686Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:42:28.854957424Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:42:28.855002238Z Vehicle might be asleep
2024-12-28T15:42:28.855011461Z Trying to wake up car then launch the command again
2024-12-28T15:42:28.856318181Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:42:48.863352930Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:42:48.863556670Z Vehicle might be asleep
2024-12-28T15:42:48.863565818Z Trying to wake up car then launch the command again
2024-12-28T15:42:48.863673133Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:43:08.873401753Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:43:08.873454439Z Vehicle might be asleep
2024-12-28T15:43:08.873462642Z Trying to wake up car then launch the command again
2024-12-28T15:43:08.874414807Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:43:13.493958203Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:43:28.892199920Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:43:28.892252549Z Vehicle might be asleep
2024-12-28T15:43:28.892260123Z Trying to wake up car then launch the command again
2024-12-28T15:43:28.893042863Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:43:48.909931944Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:43:48.909983296Z Vehicle might be asleep
2024-12-28T15:43:48.909991777Z Trying to wake up car then launch the command again
2024-12-28T15:43:48.911082313Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:44:08.927594230Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:44:08.927646193Z Vehicle might be asleep
2024-12-28T15:44:08.927655878Z Trying to wake up car then launch the command again
2024-12-28T15:44:08.929101747Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:44:28.945406592Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:44:28.945453074Z Vehicle might be asleep
2024-12-28T15:44:28.945461222Z Trying to wake up car then launch the command again
2024-12-28T15:44:28.946153276Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:44:48.956840835Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:44:48.956893095Z Vehicle might be asleep
2024-12-28T15:44:48.956901169Z Trying to wake up car then launch the command again
2024-12-28T15:44:48.958443555Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:45:08.974542533Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:45:08.974589014Z Vehicle might be asleep
2024-12-28T15:45:08.974597755Z Trying to wake up car then launch the command again
2024-12-28T15:45:08.975156884Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:45:23.917983223Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:45:28.990822380Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:45:28.990876602Z Vehicle might be asleep
2024-12-28T15:45:28.990888750Z Trying to wake up car then launch the command again
2024-12-28T15:45:28.991698878Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:45:49.011732478Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:45:49.011777070Z Vehicle might be asleep
2024-12-28T15:45:49.011784311Z Trying to wake up car then launch the command again
2024-12-28T15:45:49.012167792Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:46:09.023786681Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:46:09.024467624Z Vehicle might be asleep
2024-12-28T15:46:09.024493883Z Trying to wake up car then launch the command again
2024-12-28T15:46:09.026311362Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:46:29.043793777Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:46:29.043838925Z Vehicle might be asleep
2024-12-28T15:46:29.043847332Z Trying to wake up car then launch the command again
2024-12-28T15:46:29.044687590Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:46:49.062231594Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:46:49.062286520Z Vehicle might be asleep
2024-12-28T15:46:49.062294501Z Trying to wake up car then launch the command again
2024-12-28T15:46:49.062587667Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:47:09.069772053Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:47:09.069861534Z Vehicle might be asleep
2024-12-28T15:47:09.069874738Z Trying to wake up car then launch the command again
2024-12-28T15:47:09.070769422Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:47:29.087366308Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:47:29.087417216Z Vehicle might be asleep
2024-12-28T15:47:29.087425253Z Trying to wake up car then launch the command again
2024-12-28T15:47:29.088110141Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:47:34.343150144Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:47:49.097638589Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:47:49.097688496Z Vehicle might be asleep
2024-12-28T15:47:49.097715700Z Trying to wake up car then launch the command again
2024-12-28T15:47:49.099201939Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:48:09.108404826Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:48:09.108445530Z Vehicle might be asleep
2024-12-28T15:48:09.108452437Z Trying to wake up car then launch the command again
2024-12-28T15:48:09.108661215Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:48:29.119498131Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:48:29.119552372Z Vehicle might be asleep
2024-12-28T15:48:29.119563223Z Trying to wake up car then launch the command again
2024-12-28T15:48:29.120239463Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:48:49.136841253Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:48:49.136886050Z Vehicle might be asleep
2024-12-28T15:48:49.136894235Z Trying to wake up car then launch the command again
2024-12-28T15:48:49.137817826Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:49:09.155243016Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:49:09.155288609Z Vehicle might be asleep
2024-12-28T15:49:09.155296035Z Trying to wake up car then launch the command again
2024-12-28T15:49:09.155679867Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:49:29.166252746Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:49:29.166302413Z Vehicle might be asleep
2024-12-28T15:49:29.166312932Z Trying to wake up car then launch the command again
2024-12-28T15:49:29.167046616Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:49:44.767120189Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:49:49.186469103Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:49:49.186508973Z Vehicle might be asleep
2024-12-28T15:49:49.186517751Z Trying to wake up car then launch the command again
2024-12-28T15:49:49.188033360Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:50:09.198006204Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:50:09.198053704Z Vehicle might be asleep
2024-12-28T15:50:09.198062445Z Trying to wake up car then launch the command again
2024-12-28T15:50:09.198840796Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:50:29.215829066Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:50:29.215876399Z Vehicle might be asleep
2024-12-28T15:50:29.215883121Z Trying to wake up car then launch the command again
2024-12-28T15:50:29.216583602Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:50:49.232204143Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:50:49.232252069Z Vehicle might be asleep
2024-12-28T15:50:49.232261180Z Trying to wake up car then launch the command again
2024-12-28T15:50:49.233378308Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:51:09.241952110Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:51:09.242078240Z Vehicle might be asleep
2024-12-28T15:51:09.242091129Z Trying to wake up car then launch the command again
2024-12-28T15:51:09.243184849Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:51:29.259334576Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:51:29.259378780Z Vehicle might be asleep
2024-12-28T15:51:29.259387613Z Trying to wake up car then launch the command again
2024-12-28T15:51:29.260566611Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:51:49.270947688Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:51:49.270984725Z Vehicle might be asleep
2024-12-28T15:51:49.270991466Z Trying to wake up car then launch the command again
2024-12-28T15:51:49.272052094Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:51:55.191178408Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:52:09.287923356Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:52:09.288778503Z Vehicle might be asleep
2024-12-28T15:52:09.288805448Z Trying to wake up car then launch the command again
2024-12-28T15:52:09.289999853Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:52:29.300165594Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:52:29.300212131Z Vehicle might be asleep
2024-12-28T15:52:29.300221983Z Trying to wake up car then launch the command again
2024-12-28T15:52:29.302030054Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:52:49.308525160Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:52:49.308583104Z Vehicle might be asleep
2024-12-28T15:52:49.308593364Z Trying to wake up car then launch the command again
2024-12-28T15:52:49.309385159Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:53:09.326499422Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:53:09.326552256Z Vehicle might be asleep
2024-12-28T15:53:09.326560089Z Trying to wake up car then launch the command again
2024-12-28T15:53:09.327164922Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:53:29.344114267Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:53:29.344173045Z Vehicle might be asleep
2024-12-28T15:53:29.344199545Z Trying to wake up car then launch the command again
2024-12-28T15:53:29.344689248Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:53:49.361623138Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:53:49.361673786Z Vehicle might be asleep
2024-12-28T15:53:49.361682842Z Trying to wake up car then launch the command again
2024-12-28T15:53:49.363359265Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:54:05.615792162Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:54:09.371660971Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:54:09.371703786Z Vehicle might be asleep
2024-12-28T15:54:09.371713841Z Trying to wake up car then launch the command again
2024-12-28T15:54:09.373005024Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:54:29.380086351Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:54:29.380135499Z Vehicle might be asleep
2024-12-28T15:54:29.380149110Z Trying to wake up car then launch the command again
2024-12-28T15:54:29.381024942Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:54:49.387861348Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:54:49.387896978Z Vehicle might be asleep
2024-12-28T15:54:49.387903422Z Trying to wake up car then launch the command again
2024-12-28T15:54:49.388113162Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:55:09.396882257Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:55:09.396921460Z Vehicle might be asleep
2024-12-28T15:55:09.396929219Z Trying to wake up car then launch the command again
2024-12-28T15:55:09.397934051Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:55:29.412928085Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:55:29.412972400Z Vehicle might be asleep
2024-12-28T15:55:29.412981270Z Trying to wake up car then launch the command again
2024-12-28T15:55:29.414755416Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:55:49.431934785Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:55:49.431987526Z Vehicle might be asleep
2024-12-28T15:55:49.431997859Z Trying to wake up car then launch the command again
2024-12-28T15:55:49.432629155Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:56:09.448441050Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:56:09.448503068Z Vehicle might be asleep
2024-12-28T15:56:09.448511994Z Trying to wake up car then launch the command again
2024-12-28T15:56:09.449069697Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:56:16.039983468Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:56:29.466197705Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:56:29.466245613Z Vehicle might be asleep
2024-12-28T15:56:29.466255242Z Trying to wake up car then launch the command again
2024-12-28T15:56:29.467353519Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:56:49.484193014Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:56:49.484235348Z Vehicle might be asleep
2024-12-28T15:56:49.484243200Z Trying to wake up car then launch the command again
2024-12-28T15:56:49.484626199Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:57:09.492886268Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:57:09.492937046Z Vehicle might be asleep
2024-12-28T15:57:09.492945583Z Trying to wake up car then launch the command again
2024-12-28T15:57:09.493647323Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:57:29.504354226Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:57:29.504415004Z Vehicle might be asleep
2024-12-28T15:57:29.504424485Z Trying to wake up car then launch the command again
2024-12-28T15:57:29.505050781Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:57:49.519980590Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:57:49.520034071Z Vehicle might be asleep
2024-12-28T15:57:49.520043867Z Trying to wake up car then launch the command again
2024-12-28T15:57:49.521154607Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:58:09.528670301Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:58:09.528721894Z Vehicle might be asleep
2024-12-28T15:58:09.528730875Z Trying to wake up car then launch the command again
2024-12-28T15:58:09.529397504Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:58:26.464925519Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T15:58:29.537937423Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:58:29.537980609Z Vehicle might be asleep
2024-12-28T15:58:29.537987627Z Trying to wake up car then launch the command again
2024-12-28T15:58:29.538544515Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:58:49.554326632Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:58:49.554362706Z Vehicle might be asleep
2024-12-28T15:58:49.554369151Z Trying to wake up car then launch the command again
2024-12-28T15:58:49.554705410Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:59:09.570579141Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:59:09.570634585Z Vehicle might be asleep
2024-12-28T15:59:09.570645363Z Trying to wake up car then launch the command again
2024-12-28T15:59:09.571583658Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:59:29.581482957Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:59:29.581515254Z Vehicle might be asleep
2024-12-28T15:59:29.581522161Z Trying to wake up car then launch the command again
2024-12-28T15:59:29.581773957Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T15:59:49.598290360Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T15:59:49.598352471Z Vehicle might be asleep
2024-12-28T15:59:49.598364693Z Trying to wake up car then launch the command again
2024-12-28T15:59:49.599481840Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:00:09.607256112Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T16:00:09.607312482Z Vehicle might be asleep
2024-12-28T16:00:09.607322704Z Trying to wake up car then launch the command again
2024-12-28T16:00:09.608791332Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:00:29.623824614Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T16:00:29.623881707Z Vehicle might be asleep
2024-12-28T16:00:29.623892207Z Trying to wake up car then launch the command again
2024-12-28T16:00:29.624800150Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:00:36.887587705Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T16:00:49.642176635Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T16:00:49.642244006Z Vehicle might be asleep
2024-12-28T16:00:49.642256395Z Trying to wake up car then launch the command again
2024-12-28T16:00:49.642261728Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:01:09.660861158Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T16:01:09.660918529Z Vehicle might be asleep
2024-12-28T16:01:09.660937621Z Trying to wake up car then launch the command again
2024-12-28T16:01:09.660958825Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:01:29.677062558Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T16:01:29.677114855Z Vehicle might be asleep
2024-12-28T16:01:29.677122225Z Trying to wake up car then launch the command again
2024-12-28T16:01:29.677897391Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:01:49.686906915Z teslaCtrlSendCommand; Error: context deadline exceeded
2024-12-28T16:01:49.686960433Z Vehicle might be asleep
2024-12-28T16:01:49.686972137Z Trying to wake up car then launch the command again
2024-12-28T16:01:49.687164378Z Attempt 1/5 sending Wake up vehicule to vin:XXXXXXXXXXXXXXX command:-domain vcsec wake
2024-12-28T16:02:47.319251221Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T16:04:57.742884383Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T16:07:08.174243188Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T16:09:18.598995271Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
2024-12-28T16:11:29.021228647Z vin:XXXXXXXXXXXXXXX presence has expired, set presence OFF
...
#
# The server is now "hanged". It goes on setting presence to OFF every 2 minutes, but it does not detect the car
# returning home, nor react to further MQTT commands.
#

Useful information thanks.
According to comments in the code it might be possible to get stuck like this. I'm currently working on a new release which will add reading of state functionality. I might not get time for a while to look at this issue. @baylanger Pierre do you have time to look at it?
Why it happens on your new car not your old is a mystery.

Why it happens on your new car not your old is a mystery.

Might very well be my own mistake. When switching cars I also reconfigured a lot in Home Assistant. Might (even likely when I think about it) be that this scenario (sending charging-set-amps when not home) never occurred before.
I'll work around by fixing "my" bug in HA. Just wanted you to know so you can make your server resilient to this scenario.


ts/env/docker migration

[✔] typescript
[❌] env file
[❌] docker
[❌] tested

Make sure to remove dist/ for this commit


dependencies not install. get same error every time.

Describe the bug
npm ERR! Unterminated string in JSON at position 1832600 (line 1 column 1832601)
npm ERR! A complete log of this run can be found in: /home/.npm/_logs/2024-10-19T15_52_14_340Z-debug-0.log
~/project 3m 12s
above error massage coming in every time i use the application
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-yyj3qa
Steps to reproduce
"i need github markdown file generator app. user give input and this application output the markdown text."
give above text for the input of bolt ai. then it produce this error
Expected behavior
i think this is a programming  problem. this AI use the programming languages without knowing proper idea.
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 43188350,
  "usedJSHeapSize": 40553802,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = KAXUN01
Chat ID = 9070d40cb174

Additional context
No response

Appreciate the feedback! We are aware of this issue and are tracking it here: #2021


Adding the feature to exclude resource groups from the reports.

Connected to: https://github.com/schubergphilis/azureenergylabelerlib/pull/19

Fails linting


Added support for dynamic URL routing.

example
router.get '/hoge/:id' do
  request.params['id']
end

Routing is searched in the order defined and call block args.
=begin
Bad :-1
Dynamic URL is bound first and fuga cannot be executed
=end

router.get '/hoge/:id' do
  request.params['id']
end

router.get '/hoge/fuga' do
  'fuga'
end

=begin
Good :+1
=end
router.get '/hoge/fuga' do
  'fuga'
end

router.get '/hoge/:id' do
  request.params['id']
end

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3b9afcd). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master      #22   +/-   ##
=========================================
  Coverage          ?   98.66%
=========================================
  Files             ?       30
  Lines             ?      899
  Branches          ?        0
=========================================
  Hits              ?      887
  Misses            ?       12
  Partials          ?        0

Impacted Files
Coverage Δ

spec/router_spec.rb
100% <100%> (ø)

spec/application_spec.rb
100% <100%> (ø)

lib/makanai/application.rb
84.84% <100%> (ø)

lib/makanai/request.rb
100% <100%> (ø)

lib/makanai/router.rb
100% <100%> (ø)

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 3b9afcd...99a5d8e. Read the comment docs.


Update components schema

What content needs to be created or modified?

The components schema is out of date (e.g. missing several properties such as auth and scopes).
Describe the solution you'd like

Current (as of v1.11) properties should be added to the schema.
Where should the new material be placed?

The existing schema doc should be updated.
The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

https://github.com/dapr/dapr/pull/6728
Additional context

@philliphoff - Where can we find the latest information.

The CRD that describes the schema (which is generate from type information in the Dapr runtime source files) is: https://github.com/dapr/dapr/blob/26e83522689cbb5cf3dd60eb25133e8f818d4412/charts/dapr/crds/components.yaml#L14-L15


[main] Update actions

including version numbers -dprotaso
/cc knative-sandbox/eventing-writers
/assign knative-sandbox/eventing-writers
Produced by: knative-sandbox/knobots/actions/update-actions
Details:

/lgtm
/approve


Label changes after expanding delete corrections

Coverage remained the same at 97.469% when pulling 36e4414301b6ccedcbdfd684ee1143205a093649 on mhines-usgs:AQCU-1773 into 8c30fbc083fceee8e4e6bbcf83b94b5c1ac63c0c on USGS-R:master.