Upgraded to v3 api endpoint

Right now the gem is hard-coded to use the v2 api, but v3 is out.
According to mailgun, v3 is backwards compatible except for the bounces
endpoint, which the gem does not use (details here -
http://blog.mailgun.com/default-api-version-now-v3/).
This changes the (hard-coded) endpoint url from v2 to v3. Possibly
solving #34.

Thanks a lot @iainbeeston for the stream of contributions!

hey @iainbeeston I was thinking in adding you as a repo collaborator? Are you interested?

No thanks - I already contribute to many different gems, and I only use
mailgun occasionally. However I think this gem is a great idea (thanks for
making it available!)
On Wed, 1 Apr 2015 at 10:19 am, Jorge Manrubia<EMAIL_ADDRESS>wrote:

hey @iainbeeston https://github.com/iainbeeston I was thinking in
adding you as a repo collaborator? Are you interested?
—
Reply to this email directly or view it on GitHub
https://github.com/jorgemanrubia/mailgun_rails/pull/42#issuecomment-88409682
.

Could someone bump the version to 0.6.7 (or 0.7.0 considering the API
endpoint has changed to v3) and publish a release to rubygems?
On Wed, 1 Apr 2015 at 10:41 am, Iain Beeston<EMAIL_ADDRESS>wrote:

No thanks - I already contribute to many different gems, and I only use
mailgun occasionally. However I think this gem is a great idea (thanks for
making it available!)
On Wed, 1 Apr 2015 at 10:19 am, Jorge Manrubia<EMAIL_ADDRESS>wrote:

hey @iainbeeston https://github.com/iainbeeston I was thinking in
adding you as a repo collaborator? Are you interested?
—
Reply to this email directly or view it on GitHub
https://github.com/jorgemanrubia/mailgun_rails/pull/42#issuecomment-88409682
.

Done, version 0.7.0 released. Thaks!

Great, thank you!
On Fri, 3 Apr 2015 at 8:51 am, Jorge Manrubia<EMAIL_ADDRESS>wrote:

Done, version 0.7.0 released. Thaks!
—
Reply to this email directly or view it on GitHub
https://github.com/jorgemanrubia/mailgun_rails/pull/42#issuecomment-89207574
.


This may not be necessary because URLs are first output to a .sitemap.json file and someone could manually adjust that file.
But, it could be possible to allow passing in some sort of regex which would allow the user to decide which pages they'd want.

If we offered this, there's a question of:
should this modify the existing exported sitemap? Or should it create a new one?
there's a few ways this could go:
Option 1:

produce a full sitemap, as usual.
then filter the sitemap to a smaller one in memory
pass the new, smaller sitemap into the main config (it's set on the linkSet property)

option 2:

As we're producing the sitemap, check each url if it meets parameters
if it doesn't, don't add the url
so the sitemap is produced with fewer urls

option 3:

get sitemap
filter the sitemap and produce a smaller sitemap file
pass the smaller sitemap file into ... whatever.

Seems like regardless, the SiteCrawler class probably needs a filter function in there.
Other questions worth asking:

what is the name of the argument we sent in?
are we just gonna allow a regex?

Note:
There's a url pattern api now: https://developer.mozilla.org/en-US/docs/Web/API/URL_Pattern_API


Recommended conda instructions might leave user with older version

After following the official installation instructions for conda, @simium ended up with poliastro 0.9.1. This deserves a bit of investigation, but I suspect that having an old base environment and conda dependency solving played a role. We should either:

Recommend installing exact versions: `conda install -c conda-forge poliastro=0.14"
Recommend creating a new environment

Closed in #912.


OSD-12962 Migration to aws-sdk-go-v2

There were a bunch of enums added which is helpful, but funnily enough there's a bug with the VPCE state enums - https://github.com/aws/aws-sdk/issues/116. Otherwise it's mostly a bunch of object <--> pointer changes and a dedicated error-handling library "github.com/aws/smithy-go"
The suggested unit testing guidelines changed to (https://aws.github.io/aws-sdk-go-v2/docs/unit-testing/), so I updated those as well. Validated it does work on a stage cluster.

/lgtm


Country code for Greece is EL, not GR

Allows validation of Greek VAT numbers, which are all prefixed 'EL' rather than the more obvious 'GR'
https://www.quora.com/Why-is-Greeces-country-code-EL-in-the-European-Union-but-GR-everywhere-else

Thank you for the fast fix!
Cheers


worry pr，can't close

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (refactoring and improving code)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Description

Additional context

I accidentally clicked the pull request button, could you ignore and turn off this pr? Sorry, thank you


some renovate PRs are failing

Some of the renovate PRs for dependency updates in our repositories are failing in CI: https://github.com/pulls/review-requested
We need to check logs in CircleCI, find out what's wrong and try to solve the issues so that dependencies can be up to date.

giantswarm/athena fixed by updating  github.com/nats-io/nkeys to v0.4.6

Successfully managed all Renovate pull requests (PRs). Successfully addressed issues in approximately six PRs, primarily involving the API and Teleport, and merged these into their respective main branches.

Addressed major issues related to vulnerabilities and dependency conflicts.

Encountered a specific issue with the API branch's Renovate PRs failing due to vulnerability concerns. Temporarily resolved this by adding certain packages to the 'nancyignore' file. This is a provisional measure for two weeks, until new, secure versions of these packages are released.

Continuously monitoring for PR failures and addressing them as needed. Current status: all critical issues resolved.


Offline map doesn't load

Please note: issues related to or caused by osmbonuspack will be closed with a
suggestion to open an issue at https://github.com/MKergall/osmbonuspack
(feel free to delete whatever doesn't apply)
Issue Type
[x] Question
[ ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
Description and/or steps/code to reproduce the problem
After updating osmdroid-Android to version 6.1.8, the offline map stopped show up. Everything is fine on version 6.1.6. What am I doing wrong? I call " mapview.setTileSource (new XYTileSource ("ZIP archive name" 0, 18, 256, ".png", new String[]{}));"
Logcat writes to me " I / osmdroid: using tiles source: Mapnik".
Environment
If it's a bug, version(s) of android this affects:
All
Version of osmdroid the issue relates to:
6.1.8

I have this problem too!
#1631

"ZIP archive name" should be the base folder within the zip. i.e.
/
/Zip archive name
/Zip archive name/0
/Zip archive name/0/1
/Zip archive name/0/1/0.png

"ZIP archive name" should be the base folder within the zip. i.e.
/
/Zip archive name
/Zip archive name/0
/Zip archive name/0/1
/Zip archive name/0/1/0.png

That's the way it is and it worked fine before the update.

call Configuration.getInstance().getOsmdroidBasePath()
that's the location that's scanned for zip/sqlite offline archives.


Check ZooKeeper status using curl

High-level description
The original test for ZooKeeper status uses lsof. The lsof command is not available on all systems. Use the curl command that is installed by DC/OS instead.
Corresponding DC/OS tickets (required)

D2IQ-62292 Remove possibility of timeouts in systemd ExecStartPost

@mesosphere-mergebot request-review @jkoelker

@mesosphere-mergebot test all

@mesosphere-mergebot changelog-not-required fix to unreleased code


Adding bidirectionnal binding with ngModel

I had a problem using ui-tinymce with ngModel because i binded my tinyMCE with a string fetched from a webservice. I have noticed that when the webservice response after that tinyMCE have render, the string does not appear.
Then I noticed that the binding is unilateral : a change from tinyMCE will be reflected on the scope, but a change on the scope won't be reflected on tinyMCE.
I made this fixe, i am new with AngularJS so it is probably a poor solution.
I won't be surprise if you deny my pull request, but I wish you will fixe this bug.

This should now be fixed in master with the change to use a $formatter. Let me know if this is still an issue.

Hello wesleycho, sorry I have not see your answer until today. I have try the last version of tinyMCE and I still have this problem ! Adding my code from my pull request still fixing it also.

To be clear, you're using 0.0.9 currently?

Yes, I would do a plunker if you want.


updated make to support Visual Studio 2019

Thanks for the plugin, it seems to work fine with X-Plane 11


[CT-735] varchar column reduces in size on an incremental run which leads to "Value too long for character type" error

Describe the bug
I have an incremental model with the following properties:
materialized="incremental",
sort="date_col",
dist="date_col",
unique_key="user_id_date",
incremental_strategy="merge",
on_schema_change="sync_all_columns"

The first fresh run worked fine. One of the column named platform (which is built from a case-when statement) was detected automatically by dbt to be of type varchar(20).
On the next incremental run, platform column of the new portion of data only had strings of maximum 17 characters. This led to dbt trying to perform a column type change on redshift from varchar(20) to varchar(17), and got this error:

Value too long for character type

Steps To Reproduce

There's a platform column build from case-when in the incremental model
First fresh run works fine
First incremental run hits the error

Expected behavior
The new column type should be big enough to hold both new and old values
Screenshots and log output
From dbt log file:
In "tbl":
  Schema changed: True
  Source columns not in target: []
  Target columns not in source: []
  New column types: [{'column_name': 'platform', 'new_type': 'character varying(17)'}]

alter table "tbl" add column "platform__dbt_alter" character varying(17);
update "tbl" set "platform__dbt_alter" = "platform";
alter table "tbl" drop column "platform" cascade;
alter table "tbl" rename column "platform__dbt_alter" to "platform"

15:43:07.968169 [debug] [Thread-1  ]: Postgres adapter: Postgres error: Value too long for character type
DETAIL:
  -----------------------------------------------
  error:  Value too long for character type
  code:      8001
  context:   Value too long for type character varying(17)
  query:     13418344
  location:  string.cpp:247
  process:   query2_263_13418344 [pid=11812]
  -----------------------------------------------

System information
The output of dbt --version:
Core:
  - installed: 1.1.0
  - latest:    1.1.0 - Up to date!

Plugins:
  - bigquery:  1.1.0 - Up to date!
  - snowflake: 1.1.0 - Up to date!
  - redshift:  1.1.0 - Up to date!
  - postgres:  1.1.0 - Up to date!

The operating system you're using: MacOS 12.3.1
The output of python --version: Python 3.8.9

It sounds like on_schema_change logic here, or more likely the logic in diff_column_data_types here, is missing logic to the effect of: If the type is the same, and only the precision differs, don't treat that as a data type change. There are some Column methods we might be able to use to this effect.
If the precision has increased from the older data to the newer data, dbt should already be handling that during expand_target_column_types, which occurs right before schema changes are detected and processed.
I'm going to transfer this issue to the dbt-core repo, since that's actually where the code change should happen, in the default/global project macros.


Add max-sql-tem-disk-usage. Style fixes. Add Known limitation on Serverless clusters.

Fixes #11314, #11855.
Removes extraneous output.
In 21.2/explain-analyze.md:

Line 63 for max-sql-tem-disk-usage.
Line 280 for known limitation.

@rytaft I noticed that this feature was first developed here: https://github.com/cockroachdb/cockroach/pull/67702. I'm assuming that was for release 21.2 and it has a release note. But then it was backported to 21.1 and 20.2 where there are the release notes I have linked to above. Should it also appeared in the release notes for 21.2?


Pagination refactor proposal

Document new pagination approach https://github.com/nemtech/catapult-rest/issues/172 based on the conversations with the REST and SDK teams:

[x] Transaction Routes (base) #92
[x] Block Routes #93
[x] Account Routes #95
[x] Mosaic Routes #108
[x] Namespace Routes #107
[x] Receipt Routes #109
[x] Metadata Routes #142
[x] RestrictionAccount #193
[x] RestrictionMosaic #193
[x] Locks #187 and #188

all done


Screenshot crash

If you try to use the screenshot key on the game! Probably due to the format of the back plane not being compatible with the save.

Hum I don't have this issue on windows 11... (as this is taken by the system and not by the program). I can disable this feature...

Removed...


Replace MAXFLOAT with FLT_MAX

Fixes issue #212

Coverage remained the same at 58.496% when pulling 35c3f0d6fc57d1a608fdb44eb6981f2a60b7a6c9 on ringlej:issue/212 into c44edc0df4933aad31a58efbf14654742cf2509a on vlm:master.

Merged, thank you!

@vlm I'm not sure now that the code is using FLT_MAX, if the #if __STDC_VERSION__ >= 199901L is needed anymore or not...

@ringlej fixed, thanks!


HelloXR app running but no output

I have HelloXR running with Vulkan, but no output to the headset, says "waiting" on the headset. I was able to make it run before but something happened, not sure what, that made it behave this way. I noticed a new line in the console at the top that was not there before ... xrNegotiateLoaderRuntimeInterface bRunningInAppContainer: 0
Also there is this error ...  INFO: (INSTANCE 0x1eb8872e470) Failed to find vkGetDeviceProcAddr in layer "C:\VulkanSDK\1.3.280.0\Bin.\VkLayer_khronos_profiles.dll"
I am not sure how to interpret the lack of an output, is it coming from Vulkan functions not being found or getting bad function pointers?

I think that the problem is coming from the failure of XrCreateInstance ... here is the output from running the sample "HelloXR"
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
[13:54:50.363][Info   ] Press any key to shutdown...
Info [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : RuntimeManifestFile::FindManifestFiles - using environment variable override runtime file C:\Program Files (x86)\Steam\steamapps\common\SteamVR\steamxr_win64.json
Info [GENERAL |  | OpenXR-Loader] : RuntimeManifestFile::CreateIfValid - attempting to load C:\Program Files (x86)\Steam\steamapps\common\SteamVR\steamxr_win64.json
xrNegotiateLoaderRuntimeInterface bRunningInAppContainer: 0
Info [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : RuntimeInterface::LoadRuntime succeeded loading runtime defined in manifest file C:\Program Files (x86)\Steam\steamapps\common\SteamVR\steamxr_win64.json using interface version 1 and OpenXR API version 1.0
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateApiLayerProperties | OpenXR-Loader] : Entering loader trampoline
Verbose [GENERAL | xrEnumerateApiLayerProperties | OpenXR-Loader] : Entering loader trampoline
[13:54:50.463][Info   ] Available Layers: (2)
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Entering loader trampoline
Verbose [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Completed loader trampoline
Verbose [GENERAL | xrCreateInstance | OpenXR-Loader] : Entering loader trampoline
Info [GENERAL | xrCreateInstance | OpenXR-Loader] : ApiLayerInterface::LoadApiLayers succeeded loading layer XR_APILAYER_LUNARG_core_validation using interface version 1 and OpenXR API version 1.1
Verbose [GENERAL | xrCreateInstance | OpenXR-Loader] : Entering LoaderInstance::CreateInstance
Core Validation output type: text, first time = true
Verbose [GENERAL | xrCreateInstance | OpenXR-Loader] : Entering loader terminator
Verbose [GENERAL | xrCreateInstance | OpenXR-Loader] : Completed loader terminator
INTERNAL VALIDATION LAYER ERROR: Null handle passed to HandleInfoBase::insert()
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : LoaderInstance::CreateInstance chained CreateInstance call failed
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : LoaderInstance::CreateInstance chained CreateInstance call failed
Info [GENERAL |  | OpenXR-Loader] : ApiLayerInterface being destroyed for layer XR_APILAYER_LUNARG_core_validation
Info [GENERAL | xrCreateInstance | OpenXR-Loader] : RuntimeInterface::UnloadRuntime - Unloading RuntimeInterface
Info [GENERAL |  | OpenXR-Loader] : RuntimeInterface being destroyed.
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed
[13:54:50.496][Error  ] XrResult failure [XR_ERROR_INITIALIZATION_FAILED]
Origin: xrCreateInstance(&createInfo, &m_instance)
Source: C:\OpenXR\OpenXR-SDK-Source-1.1.38\src\tests\hello_xr\openxr_program.cpp:200
C:\OpenXR\OpenXR-SDK-Source-1.1.38\build\src\tests\hello_xr\Debug\hello_xr.exe (process 5984) exited with code 1.


%code% in message format doesn't work for LSP

Information
VIM version
VIM - Vi IMproved 8.1 (2018 May 18, compiled Jul 22 2018 05:24:30)
macOS version

Operating System: MacOS High Seirra
:ALEInfo

 Current Filetype:
Available Linters: []
  Enabled Linters: []
 Suggested Fixers:
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
 Linter Variables:

 Global Variables:

let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = v:null
let g:ale_command_wrapper = v:null
let g:ale_completion_delay = 100
let g:ale_completion_enabled = 1
let g:ale_completion_max_suggestions = 50
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '[%linter%] %code% %s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = v:null
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_lint_on_insert_leave = 0
let g:ale_linter_aliases = {}
let g:ale_linters = {}
let g:ale_linters_explicit = 0
let g:ale_list_window_size = v:null
let g:ale_list_vertical = v:null
let g:ale_loclist_msg_format = v:null
let g:ale_max_buffer_history_size = v:null
let g:ale_max_signs = v:null
let g:ale_maximum_file_size = v:null
let g:ale_open_list = v:null
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_set_balloons = 1
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = v:null
let g:ale_sign_error = v:null
let g:ale_sign_info = v:null
let g:ale_sign_offset = v:null
let g:ale_sign_style_error = v:null
let g:ale_sign_style_warning = v:null
let g:ale_sign_warning = v:null
let g:ale_statusline_format = v:null
let g:ale_type_map = v:null
let g:ale_use_global_executables = v:null
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

What went wrong
%code% is always the empty string when using lsp-based linters.
Reproducing the bug

Put %code% in your g:ale_echo_msg_format
Open a file using an LSP server
introduce an error
Expected: %code% to be replaced by the code from publishDiagnostics. Actual: %code% replaced with empty string

Cause
A .nr field is populated here:

https://github.com/w0rp/ale/blob/a7b8cb4fe32b43dbeeadc8cb94f378b4e2112723/autoload/ale/lsp/response.vim#L50
https://github.com/w0rp/ale/blob/a7b8cb4fe32b43dbeeadc8cb94f378b4e2112723/autoload/ale/lsp/response.vim#L73

Problems:

https://github.com/w0rp/ale/blob/a7b8cb4fe32b43dbeeadc8cb94f378b4e2112723/autoload/ale.vim#L255 does not check for .nr - it only checks for the code field, which is not documented in ale-loclist-format.
I'm uncertain if it's safe to do this: it looks like .nr is expected to be an int, however the LSP allows string error codes

Looks like you're half way to writing a pull request to fix this.

Hopefully, though waiting on internal approval before I can send PRs, so maybe not :(

I'm uncertain if it's safe to do this: it looks like .nr is expected to be an int, however the LSP allows string error codes

Can you clarify if .nr is expected to be an int, or strings are fine too?

I think nr is just numbers only, and that's a mistake. It should probably just be set in the code key.


Error deleting pre-existing post

Describe the bug
I am encountering an error whenever I click into a pre-existing post on the template. I would like to delete the post as it is unrelated to the website I am making but it will not let me and comes up with "1:1: Incorrectly eaten value: please report this warning on https://git.io/vg5Ft" when it is clicked
Screenshots

Two questions:

Is it giving the error when you open the entry or when you click delete?
Can you share the repo?

It happened when I clicked in to open the entry!
https://github.com/AimeexJB/marie-hogan-singer   <--- this is the repo
I had to deleted the page manually from the repo becuase I never found fix for it!


Autocomplete window stays active more than usual

When typing a line of code, I rely on the autocomplete feature, but a recent change has made it start popping up more often.  For example in the line of comments, I typed the // and then space and the autocomplete box popped up.  Is this configurable?  I rely on this for completing variable name and it is especially handy for qualified variables.
Thanks,
Howard

I guess it all boils down to the way I got used to it reacting.  In my mind, space means there is nothing left to try to autocomplete.  I got used to hitting Esc to make it stop in certain situations.  But the way I usually code I will get to the end of the line and press Enter.  If autocomplete is primed to react when I hit Enter, it adds appxClose on a lot of lines and I have to delete that before getting my next line.

Is it possible to make space being a trigger a configurable option????

@Hadkins2 I don't think there is a way to make it configurable with the way it works in the backend - though I have no problem removing the space as a trigger.
What do you think?

Leave it as it is now.  Looking through the discussions, I don't see anyone else having issues with the current behavior.  This is just something I need to adjust to.
Thanks for responding.
Howard

@Hadkins2 I really do appreciate this feedback.
vscode-rpgle has a big internal change this week (thus why this is happening) and your feedback is excellent.
Thank you!

Looking forward to the updates.  This product just keeps getting better and better.

Hey @Hadkins2 - sorry to bother you about this.
I am trying to show my higher ups that our users are active and like to provide feedback like this.
Whenever you get a moment, can you check this out and leave some feedback there? Thanks!
https://github.com/orgs/halcyon-tech/discussions/350

Done.  My pleasure to provide feedback


fix minor issues when working with custom csv files

Hi Vincent @vincentvanhees ,
I was setting up a data flow to use GGIR with our data in plain csv format with four columns and no headers, generated by a different brand not handled in this package. Luckily, GGIR has this function in mind already, with rmc.* arguments, as well as dformat=5 and mon=5 branches.
During the setup, I encountered and solved two errors before the data flow is running. I'm submitting this pull request to fix the following two issues:

In g.getmeta.R, the logic is only slightly changed, and in fact the changed logic now is the exact same as a counterpart in g.calibrate.R. Specifically, in this part:
else if (dformat == 4  | dformat == 5) {
if (dformat == 4 & P$header$hardwareType == "AX6")
if dformat==5 as the custom csv, it will still try to assess P$header$hardwareType == "AX6", raising error as there's no "header" in "P". this can be fixed in multiple ways, and I chose to make this logic consistent with the same one in g.calibrate.R.

in g.extractheadervars.R, there was a couple of obvious issues that towards the end in the csv file handling section, "BL" needed to change to "BodyLocation" and "SN" needed to change to "deviceSerialNumber" to be consistent with the object as output.

After I fixed these two issues, the package runs smoothly for the custom csv files we have.
Let me know if you find any issues with this pull request, or need any additional modifications.
Best,
Xiangnan

Codecov Report

Merging #283 into master will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #283      +/-   ##
==========================================
- Coverage   75.26%   75.24%   -0.02%
==========================================
  Files          63       63
  Lines        8220     8222       +2
==========================================
  Hits         6187     6187
- Misses       2033     2035       +2

Impacted Files
Coverage Δ

R/g.extractheadervars.R
66.66% <0.00%> (ø)

R/g.getmeta.R
62.69% <0.00%> (-0.20%)
:arrow_down:

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 3bdf96f...9cfcf9f. Read the comment docs.


Export ASGI app allowing for app.mount() instead of mount_chainlit()

Is your feature request related to a problem?
In order to include chainlit in a 3rd party FastAPI/ASGI/WSGI app, it's currently necessary to call mount_chainlit().
As this is not a common way to expose apps for mounting in other apps, it leads to confusion amongst developers. See #1166 and #1220.
Specifically, the current implementation requires that mount_chainlit() is called after any other endpoints are defined. As chainlit would be mounted on a subpath, this is not intuitive.
The current implementation also makes it impossible to mount chainlit multiple times (e.g. with different configuration, on different paths). Note that the current suggestion will not directly enable this, but it seems a logical step in the direction of supporting multiple chainlits.
Describe the solution you'd like
Having a chainlit app which can either be imported from a module or dynamically generated with a factory function (get_app()), as an independent and self-contained ASGI-app.
This would include using the request path to derive the root path (rather than passing it hardcoded from mount_chainlit() as is currently done). This also seems a cleaner approach.

While I don't have enough direct experience with asgi to comment on specifics, I'll give anything that makes chainlit less of a bully a thumbs up :)
It seems the underlying original philosophical notion is that CL is going to be the only thing running on a server...it wants to do auth...it wants to terminate SSL...and if I'm reading this and the related issues correctly, it wants to control routing. So, "Yes" to anything that makes CL play more nicely with others.
In my case, since I didn't see any mention of Flask in the docs (and didn't get any tips in discord), I resorted to loading CL in an iframe from a Flask template. Ugly (but isolated).

I'd like to upvote this issue please. After mounting my chainlit app on FastAPI I'm also not too sure how to invoke it from a FastAPI sub-application endpoint perspective (https://fastapi.tiangolo.com/advanced/sub-applications/#check-the-automatic-api-docs). But I have verified that running <IP_ADDRESS>:port_number opens the standard Chainlit frontend.

I really hope some serious thought is being given to breaking CL free from the pristine localhost prison that it is currently in. Hard for folks to adopt something that is only comfortable in one deployment scenario.
For people building production-grade products and trying to incorporate CL, it would be helpful for some kind of vision statement or at least status/comment from @willydouhard. I'm personally finding that the beautiful website, docs, and marketing doesn't match the reality by a wide gap, unfortunately....and finding this out has been costly in my case. I would never have guessed that something that worked perfectly locally would be effectively impossible to migrate to a remote server environment. I've just never seen this before, and I've been building stuff for a long time.
And, I'll say that it's a bit tragic because CL is a beautiful piece of work at its core. But having it wrapped and buried beneath layers of networking and server complexity and pseudo-security that virtually no existing business is going to need (as far as I can tell) is just a shame. Hobby projects might be in a different category though, so who is the audience? What is CL? What is its mission?
No pressure, but I still intend to get a production release of CL/Copilot done in the immediate term. The decision I have to make is how much hacking of 1.1.402 I'll need to do to produce an MVP and whether that is going to mean I've forked too far from main to feasibly heal the separation any time soon.
I've been asked to provide feedback on some specific issues, which I've done as requested...any response?

@dokterbob Any response?
In general, when you ask someone to provide feedback on an issue, it is considered a sign of courtesy and respect to respond to them after they do.

@dokterbob Bump. Thoughts? Some important questions have been raised on this issue, so it's important that the community understands what you think of them.


Gauge language runner / load problem

VSCode Version: 1.49.0
OS Version: Windows 10

Steps to Reproduce:

Have long complicated spec/step_implemetation/test_libraries
Start VS code with spec in window.

Does this issue occur when all extensions are disabled?: No, because it does not try to load gauge then
Receive errors:
Current gauge language runner is not compatible with gauge LSP. Some of the editing feature will not work as expected
unable to connect to runner : Timed out connecting to python
had no problems with Gauge this morning, but as soon as update hit for VS Code, the errors started occurring. This happened in the past, and was debugger related. Tried to update via pip-check and updates. was not related to those. I feel its related to timing on startup. Will continue to search for a solution as this is critical to our coding.
note: output for gauge shows:

--> request #1: gauge/getRunnerLanguage: null
<-- request #0: client/registerCapability: {"registrations":[{"id":"gauge-fileWatcher","method":"workspace/didChangeWatchedFiles","registerOptions":{"watchers":[{"globPattern":"c:/CompanyName/controls_test/**/*{.spec,.md,.cpt}","kind":5}]}}]}
<-- result #1: gauge/getRunnerLanguage: ""
--> result #0: client/registerCapability: null
<-- notif: window/logMessage: {"type":1,"message":"notif #0: initialized: current runner is not compatible with gauge LSP"}
[Error - 5:07:34 PM] notif #0: initialized: current runner is not compatible with gauge LSP

also note:

Debug is no longer there

Imanaged to get it to run from the command line outside of the VSCode via powershell. It still occasionally fails however when trying to link to python

Error ----------------------------------
[Gauge]
Failed to start gauge API: Timed out connecting to python
Get Support ----------------------------
Docs:          https://docs.gauge.org
Bugs:          https://github.com/getgauge/gauge/issues
Chat:          https://spectrum.chat/gauge
Your Environment Information -----------
windows, 1.1.4, c982558
html-report (4.0.12), json-report (0.3.5), python (0.3.11), screenshot (0.0.1)


Problems compiling example

Hello,
I am running on Ubuntu 20.04 (64-bit) and have just tried to compile up your examples using both Go v1.16 and v1.17 but get the same errors:
I get through these with no problems:
export GO111MODULE=auto
go install -buildmode=shared std
go build -linkshared -v github.com/pkujhd/godynamic/examples/loader

But then on the next step:
go install -v -buildmode=shared -linkshared github.com/pkujhd/godynamic/examples/ubase

Output:
/test$ go install -v -buildmode=shared -linkshared github.com/pkujhd/godynamic/examples/ubase
# /tmp/go-build180572587/b038/libgithub.com-pkujhd-godynamic-examples-ubase.so
panic: runtime error: makeslice: cap out of range

goroutine 1 [running]:
cmd/link/internal/loader.(*Loader).LoadSyms(0xc00058c000, 0x66f793)
        /home/lonnie/.gvm/gos/go1.17/src/cmd/link/internal/loader/loader.go:2210 +0x9f
cmd/link/internal/ld.(*Link).loadlib(0xc000140000)
        /home/lonnie/.gvm/gos/go1.17/src/cmd/link/internal/ld/lib.go:577 +0x46e
cmd/link/internal/ld.Main(_, {0x20, 0x20, 0x1, 0x7, 0x10, 0x0, {0x0, 0x0}, {0x678977, ...}, ...})
        /home/lonnie/.gvm/gos/go1.17/src/cmd/link/internal/ld/main.go:249 +0xd8b
main.main()
        /home/lonnie/.gvm/gos/go1.17/src/cmd/link/main.go:69 +0x1005

Not really sure what is happening here.
Can you please help?

@lonnietc  please tell me your golang version, like go.1.17.x
it seems a golang compiler bug, so I could not do more things

@pkujhd I can use just about an Go version, and tried multiple versions with the same result.
Just tried:
go version go1.16 linux/amd64

What version do you use on your side (latest version) and I will try it here.

As an update, I just tried it again with
Go v1.16.15
and got the same results so I am still researching the error message to see if I can pinpoint down where the panic is happening in the code.


Potentially slow fetching from Wikidata

This query does not work well for some categories because of the recursive pattern. Furthermore, there is really no reason for not getting all possible points in a bounding box. For example, Prague has ~35000 items with location. So, the amount of transferred data is comparatively small.
https://github.com/zhukovdm/smartwalk/blob/94fe28783a554c38792add14c2e1e2e57b8b4b24/data/wikidata-create/src/fetch.ts#L25-L46

Another interesting observation is that order of statements in SPARQL matters (at least for WDQS). A good idea here is to place wikibase:box before more general matchers.


Support Gradle 8.5

See:

https://github.com/microsoft/build-server-for-gradle/blob/a7712845a494de4fdf8f3f8340eb3e639ecf2275/server/src/main/java/com/microsoft/java/bs/core/internal/gradle/Utils.java#L153
https://docs.gradle.org/8.5-rc-1/userguide/compatibility.html

This should address: https://github.com/microsoft/vscode-gradle/issues/1420#issuecomment-1804781441

https://github.com/gradle/gradle/releases/tag/v8.5.0

@mozhuanzuojing Thank you for the reminder.


Topic recognition

This is a Triplet Siamese Classifier for the ADNI dataset to classifier Alzheimer's disease

This is an initial inspection, no action is required at this point
Difficulty: Hard
Readme: Poor

some information provided on the algorithm
some plots/figures provided with no context and minimal information
a triplet loss plot ir shown, but no plots for the classifier are presented
no discussion/interpretations on the results

Commit messages: OK, very few and very brief
Code:

minimal to no comments
design is ok

Functionality/Performance:

looking at the 2d manifold, the triplet doesn't seem to have learned anything at all(?)
classification accuracy is only 65%

General comments:

solves the problem apporpriately although performance is very poor

Marking
Good Practice (Design/Commenting, TF/Torch Usage)
Adequate design and implementation
Good spacing and comments
Header blocks missing -1
Recognition Problem
Solves problem, poor performance -1
Driver Script present
File structure present, but not in folder, may your own folder for project code -2
Shows Usage & Demo & Visualisation & Data usage, no classifier plot -1
Module present
Commenting minimal -1
No Data leakage
Difficulty: Hard
Commit Log
Meaningful commit messages
Progressive commits used
Documentation
ReadMe OK, no usage, no refs -2
Model/technical explanation, no architecture -1
Good Description and Comments
Markdown used and PDF submitted
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch)
Feedback required, move code into your own folder and restore repo README -2
Request Description good

Feedback marks possible +2 if the requested changes are made (see above).

No feedback attempt and no feedback marks granted.


More accurately reference CDN servers

https://github.com/CanastaWiki/Canasta/blob/b29b7120e3d8b792e22398106ffdcda5a723bea6/_sources/canasta/CanastaDefaultSettings.php#L69
$wgCdnServersNoPurge = [];
$wgCdnServersNoPurge[] = '<IP_ADDRESS>/8';     // <IP_ADDRESS> – <IP_ADDRESS>
$wgCdnServersNoPurge[] = '<IP_ADDRESS>/12';  // <IP_ADDRESS> – <IP_ADDRESS>
$wgCdnServersNoPurge[] = '<IP_ADDRESS>/16'; // <IP_ADDRESS> – <IP_ADDRESS>
The specified ranges are overly broad. This is preventing purges from being sent.

It really shouldn't matter if that setting is overly broad (other than the mild security risk if one of those servers are untrusted). What matters is that $wgCdnServers is set correctly.

That makes sense. Is it accurate to say that the title of the task is still correct, but the substance is that $wgCdnServers is not set, rather than $wgCdnServersNoPurge is too broad?

yes.
An argument could be made for not setting $wgCdnServersNoPurge to the entire private IP space like that, but its the $wgCdnServers setting that is critical.

Not as far as I know. I believe that @bawolff patched our instance by adding the following to CanastaDefaultSettings.php:
$wgCdnServers = [];
$wgCdnServers[] = "varnish:80";

I think it also involved setting $wgInternalServer to have an http protocol

It looks like a value of
$wgInternalServer = http://gateway.docker.internal
might do the trick. Does that look correct, @bawolff ?

It depends on how varnish is configured. The most likely correct value would be $wgServer except http instead of https. It should be whatever caddy is sending varnish as the hist value

On our instance, we have caddy disabled. In this case, the IP address for gateway.docker.internal matches that of varnish. It seems that gateway.docker.internal would be correct when used with caddy as well, while specifying varnish in that case (as originally patched in our instance) would not be correct. But, somebody would need to test to be sure that works in the default Canasta case (with caddy).

Or, are you saying that using the IP address rather than the hostname would not allow varnish to operate correctly?

The host name for wgInternalServer is used to determine what to purge on varnish. Unless the varnish vcl has host normalization code It has to match what the host is of incoming requests, or varnish will think the purges are for a different virtual host.


[renovate]Clean up old container images

As we always pulling the latest renovate image we need to make sure that old images are cleaned otherwise we will run out of disk space regularly.

/retest

I've deployed this version of the script to our runner now.


No kmods for RHEL 9.4

The kmod packages for 555.42.02, 550.90.07, 535.183.01 are on the way for kernel 5.14.0-427.20.1

The kmods were posted but there is now a new kernel 5.14.0-427.22.1.
The kmod packages for that one should be ready tomorrow.

Closing


One click mining not working with youtube

The one click mining feature does not work on youtube. When adding the note through yomitan, I get the error:
Enable audio recording: Click on the asbplayer action button in the top-right of the browser window to enable audio recording for this tab.
This might be user error. I am able to get recording working if I mine the old way, but not with the one click mining and the go ankiconnect proxy.

I'm also happy to help fix this if I can get some guidance on which files in the codebase I need to look at.

Hi, the behavior you're describing is intended because audio-recording permissions need to be acquired manually when not using keyboard shortcuts or the context menu items for mining.
However, if mining still does not work even after clicking the asbplayer icon in the top-right of the browser window then there is a bug. I have not been able to reproduce this behavior.

This is a demo of what is expected, including clicking on asbplayer's action icon to enable recording:
https://github.com/killergerbah/asbplayer/assets/2254858/ec89fae9-7909-4c2f-ac09-c020fa50bca7


My app Crashes after installing path_provder

Steps to reproduce

Create a simple Flutter App.
Install path_provider.
I can no longer compile / build my application.
I am taking a Flutter class on tutorials point to access SQL Databases. I have been trying to resolve this issue all day. see "actual results below". I hope this is a simple fix.

Expected results
Just compile and run the application.
Actual results
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
Running Gradle task 'assembleDebug'...
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':path_provider_android:compileDebugJavaWithJavac'.

Could not resolve all files for configuration ':path_provider_android:androidJdkImage'.
Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
Execution failed for JdkImageTransform: /Users/dmcleod/Library/Android/sdk/platforms/android-34/core-for-system-modules.jar.
Error while executing process /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/jlink with arguments {--module-path /Users/dmcleod/.gradle/caches/transforms-3/d9e926982c2c139ff9125eb7b6be4144/transformed/output/temp/jmod --add-modules java.base --output /Users/dmcleod/.gradle/caches/transforms-3/d9e926982c2c139ff9125eb7b6be4144/transformed/output/jdkImage --disable-plugin system-modules}

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

BUILD FAILED in 3s
Error: Gradle task assembleDebug failed with exit code 1
Code sample
Code sample

import 'package:flutter/material.dart';
import 'package:untitleduser_management_app/screens/home_screen.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      home: HomeScreen(),
    );
  }
}

### Screenshots or Video

<summary>Screenshots / Video demonstration</summary>
import 'package:flutter/material.dart';

class HomeScreen extends StatefulWidget {
  const HomeScreen({super.key});

  @override
  State<HomeScreen> createState() => _HomeScreenState();
}

class _HomeScreenState extends State<HomeScreen> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text("SQLite CRUD App"),
        centerTitle: true,
        backgroundColor: Colors.blueAccent,
        foregroundColor: Colors.white,
      ),
      body: Container(),
    );
  }
}

[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output

dmcleod@Denniss-Laptop untitleduser_management_app % flutter doctor -v
[✓] Flutter (Channel stable, 3.24.5, on macOS 15.1 24B83 darwin-arm64, locale
    en-US)
    • Flutter version 3.24.5 on channel stable at
      /opt/homebrew/Caskroom/flutter/3.24.3/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision dec2ee5c1f (6 days ago), 2024-11-13 11:13:06 -0800
    • Engine revision a18df97ca5
    • Dart version 3.5.4
    • DevTools version 2.37.3

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/dmcleod/Library/Android/sdk
    • Platform android-35, build-tools 35.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16B40
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2024.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 21.0.3+-79915917-b509.11)

[✓] IntelliJ IDEA Community Edition (version 2024.3)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 82.2.4
    • Dart plugin version 243.22562.3

[✓] VS Code (version 1.95.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.100.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)     • emulator-5554         • android-arm64  •
      Android 13 (API 33) (emulator)
    • macOS (desktop)                 • macos                 • darwin-arm64   •
      macOS 15.1 24B83 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         •
      macOS 15.1 24B83 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript •
      Google Chrome 131.0.6778.85

[✓] Network resources
    • All expected network resources are available.

• No issues found!
dmcleod@Denniss-Laptop untitleduser_management_app %

`

Hi @dkmcleod,
Try using the latest version of path_provider, which is ^2.1.5. After updating, run flutter clean to clear any cached files, and then run flutter pub get to fetch the updated dependencies.
This often helps resolve issues related to package conflicts or outdated caches.

@dkmcleod
The issue you are facing was originally reported https://github.com/flutter/flutter/issues/156304 and has been fixed and available in master and beta. A solution you can try is as mentioned https://github.com/flutter/flutter/issues/156304#issuecomment-2397707812. Make sure to be on AGP 8.2.1+.
Closing this as a duplicate.


hovering is not perfect in mountain chart

And in this chart, I can only hover US, Nigeria and China is unhoverable if I point in the chart directly (I can change hover them only if I point their lables on the left)
http://www.gapminder.org/tools/mountain#_ui_chart_manualSortingEnabled:false;;&state_entities_select@_geo=usa;&_geo=chn;&_geo=nga;;&opacitySelectDim=0.00;&marker_stack_which=none

When I click that link, China is not hoverable at all and there's a ghost india which only pops up when I hover over it...
http://recordit.co/SltQBqc3xT


Remove 1T related codes

Tick-tock, tick-tock...
If people want to use 1T-related codes, please go to the older straxen version.
Close: https://github.com/XENONnT/straxen/issues/1474
Since I removed fake_daq.py, I would let @cfuselli take a look of the codes.

coverage: 88.706% (-0.7%) from 89.384%
when pulling 2e7cf170f9209a4f674955ba270f97e8b0f51d39 on rm_1t
into 6a166b97501d249234d1975a5253f1aaf974af96 on master.


[6.1.0] Validation error bug

Following code brings validation error! There are no validation error on 6.0.x
function validate(values) {
  return {
    email: values.email ? null : messages.EMAIL_REQUIRED_ERROR,
    password: values.password ? null : messages.PASSWORD_REQUIRED_ERROR,
  };
}

If syncErrors has properties then it currently returns as not valid regardless of that properties value. As a work around you need to be selective about which fields you return.

no, the validate function returns an object with explicit value on properties, that says that there are and error on this property or not.

Yes that is what i said, but there is a bug.
if state has:
syncErrors: {
   email: null,
}

then it is going fail submitting as it is treating email as an errored field as it is clearly not checking the value,

@khakulov Check this behavior in v6.1.1
P.S:
See documentation

validate : (values:Object, props:Object) => errors:Object [optional]
a synchronous validation function that takes the form values and props passed into your component. If validation passes, it should return {}. If validation fails, it should return the validation errors in the form { field1: , field2:  }. Defaults to (values, props) => ({}).
See Synchronous Validation Example for more details.

If validation passes, it should return {}.

@ortex put it clearly.


What is the current version?

When I install it vía npm, always is installed version 0.14.1, but here in releases theres a 0.15.1 version

@sebrojas14 Make sure your package.json has the latest version before installing with npm. Take a look at npm update.
Also remember that for Ionic 1, you have to move the library into your www/lib folder: http://docs.ionic.io/setup.html#installation each time it's updated.


load_and_authorize_resource fails with module scope

I build mongoid classes on the fly. One class is called Contact. Since I build them on the fly, I place the class in a module so it doesn't conflict with a global class name. The problem is when the controller action is called, load_and_authorize_resource looks for Contact, not MyModule::Contact and fails. How can I pass a module into load_and_authorize_resource so it looks for the class in the module?

Would the class option help?
load_and_authorize_resource class: 'MyModule::Contact'

Or is the class name different every time?

What @anthonylewis said, that should fix the issue. Let us know if it doesn't.


Added CLI options to fix device scripts

Fixed and confirmed #185

Got a few moments only, unfortunately.

You shouldn't have let me add that code without --help arguments!  :-P
File a bug.

I'm claiming that the type field in add_argument might not be needed
if you provide a default - because it takes type from the type of the
default value - but I might be wrong.

On Sat, May 20, 2017 at 3:54 PM, Adam Haile<EMAIL_ADDRESS>wrote:

@adammhaile commented on this pull request.
In bibliopixel/main/all_pixel.py
https://github.com/ManiacalLabs/BiblioPixel/pull/191#discussion_r117609981
:

@@ -109,3 +109,5 @@ def run(args, settings):

def set_parser(parser):
parser.set_defaults(run=run)

parser.add_argument('--hardware-id', default='1D50:60AB', type=str)

Not sure what you mean by # 2
I'll add "help=" if you add it to your code ;)
From demo.py
def set_parser(parser):
parser.set_defaults(run=run)
parser.add_argument('name', nargs='?', default='')
parser.add_argument('--width', default=16, type=int)
parser.add_argument('--height', default=16, type=int)
parser.add_argument('--depth', default=16, type=int)
parser.add_argument('--simpixel', default=DEFAULT_SIMPIXEL_URL)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/191#discussion_r117609981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsjyUmZfoB0P64FxBzFzwAy46_8QCks5r7vCOgaJpZM4NhKTm
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Back with more time.
The time when you don't need the type= argument is if you have the
choices= argument
(which doesn't apply) or type='str' which does apply in one case!
This is probably the least important use of help= in the whole argument
system, but it's a shame I didn't do it from the start, because it's useful
for users...
If you wanna check it in, do it!
On Sun, May 21, 2017 at 9:11 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

Got a few moments only, unfortunately.

You shouldn't have let me add that code without --help arguments!  :-P
File a bug.

I'm claiming that the type field in add_argument might not be needed
if you provide a default - because it takes type from the type of the
default value - but I might be wrong.

On Sat, May 20, 2017 at 3:54 PM, Adam Haile<EMAIL_ADDRESS>wrote:

@adammhaile commented on this pull request.
In bibliopixel/main/all_pixel.py
https://github.com/ManiacalLabs/BiblioPixel/pull/191#discussion_r117609981
:

@@ -109,3 +109,5 @@ def run(args, settings):

def set_parser(parser):
parser.set_defaults(run=run)

parser.add_argument('--hardware-id', default='1D50:60AB', type=str)

Not sure what you mean by # 2
I'll add "help=" if you add it to your code ;)
From demo.py
def set_parser(parser):
parser.set_defaults(run=run)
parser.add_argument('name', nargs='?', default='')
parser.add_argument('--width', default=16, type=int)
parser.add_argument('--height', default=16, type=int)
parser.add_argument('--depth', default=16, type=int)
parser.add_argument('--simpixel', default=DEFAULT_SIMPIXEL_URL)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/191#discussion_r117609981,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsjyUmZfoB0P64FxBzFzwAy46_8QCks5r7vCOgaJpZM4NhKTm
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Everything has help text now.

Yowza!
:+1:
!!
On Sun, May 21, 2017 at 8:52 PM, Adam Haile<EMAIL_ADDRESS>wrote:

Everything has help text now.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/191#issuecomment-302955300,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdso8PwAC1kNplU7zgx4RnP3q-qUwpks5r8IfrgaJpZM4NhKTm
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com


Option for disable camera

Hi,
Can you add a prop to disable camera ?
thanks for your work.

Actually this can be implemented quit easy.
Just set a react state, for example, set a state named "showCamera", render WebCam only the state is true. Then if you want to disable camera, just set the state to false.


No lift-off when the mav_nonlinear_mpc controller is used

Hi,
I am on ROS Kinetic, and am trying to use the rotors-simulation package for some of my experiments. Initially, I am using the mav_trajectory_generation package to generate a trajectory through the desired points, and publishing this trajectory_msgs/MultiDOFJointTrajectory message on a topic. Then, I am making use of the mav_control_rw package, and specifically the non linear controller provided in that package to make my hummingbird UAV go through the desired points. But when I run the mav_nonlinear_mpc_sim.launch file, my UAV does not take off, and the rotors keep rotating. When I echo the /hummingbird/command/motor_speed topic, I notice that the motor speeds are around 400, which dosent seem to be sufficient to fly the UAV.
I am not able to resolve this issue. Any help from you guys will be greatly appreciated.
Thanks

Are you setting the correct MAV name to hummingbird? the default name is firefly which is hexacopter.


Can`t start mysql container

Hello everyone, help me pls https://stackoverflow.com/questions/78533065/laradock-cant-start-mysql-container

Hi, I also found this issue and have submitted a PR with a fix #3524

Hi, I also found this issue and have submitted a PR with a fix #3524

Hi, I cloned the project with your edits, but the result is the same

Hi, I also found this issue and have submitted a PR with a fix #3524

Thank you very much. I reinstalled the system, applied your solution and everything works great. Thank you!

it still doesn't work with the submitted PR. Here is what I've got:

2024-06-29 20:56:06 2024-06-30T00:56:05.012472Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-06-29 20:56:06 2024-06-30T00:56:05.964694Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-06-29 20:56:06 2024-06-30T00:56:05.995634Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.0) starting as process 1
2024-06-29 20:56:06 2024-06-30T00:56:06.010793Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-06-29 20:56:06 2024-06-30T00:56:06.014606Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-06-29 20:56:06 2024-06-30T00:56:06.081676Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-06-29 20:56:08 2024-06-30T00:56:08.471648Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-06-29 20:56:09 mysqld: Table 'mysql.plugin' doesn't exist
2024-06-29 20:56:09 2024-06-30T00:56:09.110163Z 0 [ERROR] [MY-010735] [Server] Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure.
2024-06-29 20:56:09 2024-06-30T00:56:09.110594Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.110841Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.111059Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.111731Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.111989Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.112143Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.112280Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.394802Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2024-06-29 20:56:09 2024-06-30T00:56:09.504588Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2024-06-29 20:56:09 2024-06-30T00:56:09.619139Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-06-29 20:56:09 2024-06-30T00:56:09.619590Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-06-29 20:56:09 2024-06-30T00:56:09.659776Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2024-06-29 20:56:09 2024-06-30T00:56:09.660263Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables
2024-06-29 20:56:09 2024-06-30T00:56:09.660495Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001146 - Table 'mysql.component' doesn't exist
2024-06-29 20:56:09 2024-06-30T00:56:09.660536Z 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-003543 - The mysql.component table is missing or has an incorrect definition.
2024-06-29 20:56:09 2024-06-30T00:56:09.661540Z 0 [ERROR] [MY-010326] [Server] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist
2024-06-29 20:56:09 2024-06-30T00:56:09.661605Z 0 [ERROR] [MY-010952] [Server] The privilege system failed to initialize correctly. For complete instructions on how to upgrade MySQL to a new version please see the 'Upgrading MySQL' section from the MySQL manual.
2024-06-29 20:56:09 2024-06-30T00:56:09.661699Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-06-29 20:56:10 2024-06-30T00:56:10.661296Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.0)  MySQL Community Server - GPL.
2024-06-29 20:56:10 2024-06-30T00:56:10.661338Z 0 [System] [MY-015016] [Server] MySQL Server - end.

It does not work for me either, macOS 14.5 with latest Laradock.
2024-07-04 00:16:11 2024-07-03 21:16:11+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.0-1.el9 started.
2024-07-04 00:16:11 2024-07-03 21:16:11+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-04 00:16:11 2024-07-03 21:16:11+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 9.0.0-1.el9 started.
2024-07-04 00:16:11 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2024-07-04 00:16:11 2024-07-03T21:16:11.530054Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-07-04 00:16:11 2024-07-03T21:16:11.668317Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-07-04 00:16:11 2024-07-03T21:16:11.669196Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.0.0) starting as process 1
2024-07-04 00:16:11 2024-07-03T21:16:11.669923Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-07-04 00:16:11 2024-07-03T21:16:11.670382Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for /var/lib/mysql/ is case insensitive
2024-07-04 00:16:11 2024-07-03T21:16:11.673091Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-04 00:16:11 2024-07-03T21:16:11.766166Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-07-04 00:16:11 2024-07-03T21:16:11.874985Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2024-07-04 00:16:11 2024-07-03T21:16:11.875028Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2024-07-04 00:16:11 2024-07-03T21:16:11.877186Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2024-07-04 00:16:11 2024-07-03T21:16:11.877851Z 0 [ERROR] [MY-000067] [Server] unknown variable 'mysql_native_password=on else echo default-authentication-plugin=mysql_native_password'.
2024-07-04 00:16:11 2024-07-03T21:16:11.878132Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-07-04 00:16:12 2024-07-03T21:16:12.937988Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 9.0.0)  MySQL Community Server - GPL.
2024-07-04 00:16:12 2024-07-03T21:16:12.938001Z 0 [System] [MY-015016] [Server] MySQL Server - end.

my friend @bestlong  did you test before merged? the error NOT FIX
2024-07-24 13:27:05 2024-07-24T11:27:04.732284Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-07-24 13:27:05 2024-07-24T11:27:05.047519Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-07-24 13:27:05 2024-07-24T11:27:05.050625Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1
2024-07-24 13:27:05 2024-07-24T11:27:05.052546Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-07-24 13:27:05 2024-07-24T11:27:05.063426Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-24 13:27:06 2024-07-24T11:27:06.024921Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases.
2024-07-24 13:27:06 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2024-07-24 13:27:06 2024-07-24T11:27:06.039137Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-07-24 13:27:03 2024-07-24 11:27:03+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-24 13:27:04 2024-07-24 11:27:04+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-24 13:27:04 2024-07-24 11:27:04+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-24 13:27:04 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2024-07-24 13:27:12 2024-07-24 11:27:12+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-24 13:27:13 2024-07-24 11:27:13+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-24 13:27:13 2024-07-24 11:27:13+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-24 13:27:13 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
2024-07-24 13:27:06 2024-07-24T11:27:06.039489Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-07-24 13:27:06 2024-07-24T11:27:06.039642Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-07-24 13:27:06 2024-07-24T11:27:06.042794Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2)  MySQL Community Server - GPL.
2024-07-24 13:27:06 2024-07-24T11:27:06.042851Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-07-24 13:27:13 2024-07-24T11:27:13.418688Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-07-24 13:27:13 2024-07-24T11:27:13.641755Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-07-24 13:27:13 2024-07-24T11:27:13.643890Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1
2024-07-24 13:27:13 2024-07-24T11:27:13.645249Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-07-24 13:27:13 2024-07-24T11:27:13.651278Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-24 13:27:14 2024-07-24T11:27:14.150702Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases.
2024-07-24 13:27:14 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2024-07-24 13:27:14 2024-07-24T11:27:14.159597Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-07-24 13:27:14 2024-07-24T11:27:14.159839Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-07-24 13:27:14 2024-07-24T11:27:14.159877Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-07-24 13:27:14 2024-07-24T11:27:14.161123Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2)  MySQL Community Server - GPL.
2024-07-24 13:27:14 2024-07-24T11:27:14.161163Z 0 [System] [MY-015016] [Server] MySQL Server - end.

my friend @bestlong did you test before merged? the error NOT FIX
2024-07-24 13:27:05 2024-07-24T11:27:04.732284Z 0 [System] [MY-015015] [Server] MySQL Server - start. 2024-07-24 13:27:05 2024-07-24T11:27:05.047519Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2024-07-24 13:27:05 2024-07-24T11:27:05.050625Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1 2024-07-24 13:27:05 2024-07-24T11:27:05.052546Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. 2024-07-24 13:27:05 2024-07-24T11:27:05.063426Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-07-24 13:27:06 2024-07-24T11:27:06.024921Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases. 2024-07-24 13:27:06 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - ) 2024-07-24 13:27:06 2024-07-24T11:27:06.039137Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-07-24 13:27:03 2024-07-24 11:27:03+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-24 13:27:04 2024-07-24 11:27:04+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 2024-07-24 13:27:04 2024-07-24 11:27:04+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-24 13:27:04 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' 2024-07-24 13:27:12 2024-07-24 11:27:12+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-24 13:27:13 2024-07-24 11:27:13+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 2024-07-24 13:27:13 2024-07-24 11:27:13+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-24 13:27:13 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock' 2024-07-24 13:27:06 2024-07-24T11:27:06.039489Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-07-24 13:27:06 2024-07-24T11:27:06.039642Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-07-24 13:27:06 2024-07-24T11:27:06.042794Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2) MySQL Community Server - GPL. 2024-07-24 13:27:06 2024-07-24T11:27:06.042851Z 0 [System] [MY-015016] [Server] MySQL Server - end. 2024-07-24 13:27:13 2024-07-24T11:27:13.418688Z 0 [System] [MY-015015] [Server] MySQL Server - start. 2024-07-24 13:27:13 2024-07-24T11:27:13.641755Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2024-07-24 13:27:13 2024-07-24T11:27:13.643890Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1 2024-07-24 13:27:13 2024-07-24T11:27:13.645249Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. 2024-07-24 13:27:13 2024-07-24T11:27:13.651278Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-07-24 13:27:14 2024-07-24T11:27:14.150702Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases. 2024-07-24 13:27:14 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - ) 2024-07-24 13:27:14 2024-07-24T11:27:14.159597Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-07-24 13:27:14 2024-07-24T11:27:14.159839Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-07-24 13:27:14 2024-07-24T11:27:14.159877Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-07-24 13:27:14 2024-07-24T11:27:14.161123Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2) MySQL Community Server - GPL. 2024-07-24 13:27:14 2024-07-24T11:27:14.161163Z 0 [System] [MY-015016] [Server] MySQL Server - end.

Try it
laradock File mysql/Dockerfile
If there is 1), then replace it, if not, then just insert 2) on the 18th line
1)
RUN if [ ${MYSQL_VERSION} > '8.4.0-0.000' ]; then \
 echo 'mysql_native_password=on' >> /etc/mysql/conf.d/my.cnf \
else \
 echo 'default-authentication-plugin=mysql_native_password' >> /etc/mysql/conf.d/my.cnf \
;

RUN version_gt() { \
 test "$(printf '%s\n' "$@" | sort -V | head -n 1)" != "$1"; \
 }; \
 mysql_version_trimmed=$(echo "$MYSQL_VERSION" | grep -oE '^[0-9]+\.[0-9]+'); \
 if version_gt "$mysql_version_trimmed" "8.3"; then \
 echo 'mysql_native_password=on' >> /etc/mysql/conf.d/my.cnf ; \
 else \
 echo 'default-authentication-plugin=mysql_native_password' >> /etc/mysql/conf.d/my.cnf ; \
 fi

laradock The mysql/my.cnf file
If there is this line, then delete it
default-authentication-plugin=mysql_native_password
run command:
docker compose build php-fpm workspace nginx mysql

ref: #3540
upgrade, then try docker compose build --no-cache --pull mysql

the problems persist :(
kachula-iva solution
2024-07-25 11:37:42 2024-07-25T09:37:42.370207Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-07-25 11:37:42 2024-07-25T09:37:42.587939Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-07-25 11:37:42 2024-07-25T09:37:42.591277Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1
2024-07-25 11:37:42 2024-07-25T09:37:42.592638Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-07-25 11:37:42 2024-07-25T09:37:42.598015Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-25 11:37:43 2024-07-25T09:37:43.118269Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases.
2024-07-25 11:37:43 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2024-07-25 11:37:43 2024-07-25T09:37:43.128342Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-07-25 11:37:43 2024-07-25T09:37:43.128765Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-07-25 11:37:43 2024-07-25T09:37:43.128808Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-07-25 11:37:43 2024-07-25T09:37:43.131465Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2)  MySQL Community Server - GPL.
2024-07-25 11:37:43 2024-07-25T09:37:43.131496Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-07-25 11:37:41 2024-07-25 09:37:41+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-25 11:37:42 2024-07-25 09:37:42+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-25 11:37:42 2024-07-25 09:37:42+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-25 11:37:42 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
bestlong solution
2024-07-25 11:55:02 2024-07-25T09:55:02.592726Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2024-07-25 11:55:02 2024-07-25T09:55:02.779752Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2024-07-25 11:55:02 2024-07-25T09:55:02.780512Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1
2024-07-25 11:55:02 2024-07-25T09:55:02.781304Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
2024-07-25 11:55:02 2024-07-25T09:55:02.785857Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-25 11:55:03 2024-07-25T09:55:03.240961Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases.
2024-07-25 11:55:03 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - )
2024-07-25 11:55:03 2024-07-25T09:55:03.248697Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2024-07-25 11:55:03 2024-07-25T09:55:03.248850Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2024-07-25 11:55:03 2024-07-25T09:55:03.248875Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-07-25 11:55:03 2024-07-25T09:55:03.249887Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2)  MySQL Community Server - GPL.
2024-07-25 11:55:03 2024-07-25T09:55:03.249909Z 0 [System] [MY-015016] [Server] MySQL Server - end.
2024-07-25 11:55:02 2024-07-25 09:55:02+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-25 11:55:02 2024-07-25 09:55:02+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-25 11:55:02 2024-07-25 09:55:02+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-25 11:55:02 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'

the problems persist :(
kachula-iva solution 2024-07-25 11:37:42 2024-07-25T09:37:42.370207Z 0 [System] [MY-015015] [Server] MySQL Server - start. 2024-07-25 11:37:42 2024-07-25T09:37:42.587939Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2024-07-25 11:37:42 2024-07-25T09:37:42.591277Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1 2024-07-25 11:37:42 2024-07-25T09:37:42.592638Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. 2024-07-25 11:37:42 2024-07-25T09:37:42.598015Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-07-25 11:37:43 2024-07-25T09:37:43.118269Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases. 2024-07-25 11:37:43 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - ) 2024-07-25 11:37:43 2024-07-25T09:37:43.128342Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-07-25 11:37:43 2024-07-25T09:37:43.128765Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-07-25 11:37:43 2024-07-25T09:37:43.128808Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-07-25 11:37:43 2024-07-25T09:37:43.131465Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2) MySQL Community Server - GPL. 2024-07-25 11:37:43 2024-07-25T09:37:43.131496Z 0 [System] [MY-015016] [Server] MySQL Server - end. 2024-07-25 11:37:41 2024-07-25 09:37:41+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-25 11:37:42 2024-07-25 09:37:42+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 2024-07-25 11:37:42 2024-07-25 09:37:42+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-25 11:37:42 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'
bestlong solution
2024-07-25 11:55:02 2024-07-25T09:55:02.592726Z 0 [System] [MY-015015] [Server] MySQL Server - start. 2024-07-25 11:55:02 2024-07-25T09:55:02.779752Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2024-07-25 11:55:02 2024-07-25T09:55:02.780512Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.2) starting as process 1 2024-07-25 11:55:02 2024-07-25T09:55:02.781304Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous. 2024-07-25 11:55:02 2024-07-25T09:55:02.785857Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-07-25 11:55:03 2024-07-25T09:55:03.240961Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases. 2024-07-25 11:55:03 mysqld: Can't open file: 'mysql.ibd' (errno: 0 - ) 2024-07-25 11:55:03 2024-07-25T09:55:03.248697Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine 2024-07-25 11:55:03 2024-07-25T09:55:03.248850Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed. 2024-07-25 11:55:03 2024-07-25T09:55:03.248875Z 0 [ERROR] [MY-010119] [Server] Aborting 2024-07-25 11:55:03 2024-07-25T09:55:03.249887Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.2) MySQL Community Server - GPL. 2024-07-25 11:55:03 2024-07-25T09:55:03.249909Z 0 [System] [MY-015016] [Server] MySQL Server - end. 2024-07-25 11:55:02 2024-07-25 09:55:02+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-25 11:55:02 2024-07-25 09:55:02+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' 2024-07-25 11:55:02 2024-07-25 09:55:02+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started. 2024-07-25 11:55:02 '/var/lib/mysql/mysql.sock' -> '/var/run/mysqld/mysqld.sock'

If you have the opportunity, try to remove laradock and containers, and install it again, taking into account my solution. Don't forget to save your settings and .conf files!

Hi @rivara
your problem now is cause by
2024-07-25 11:55:03 2024-07-25T09:55:03.240961Z 1 [ERROR] [MY-014061] [InnoDB] Invalid MySQL server downgrade: Cannot downgrade from 90001 to 80402. Downgrade is only permitted between patch releases.

new release .env.example default set MYSQL_VERSION=8.4
please check your .env  may chang to '9.0' for you need.
backup ~/.laradock/data/mysql
rm ~/.laradock/data/mysql
docker compose build --no-cache --pull mysql
docker compose up -d mysql
docker compose ps  check mysql continer is running.

@bestlong i tried
but service isnt starting
mysql_root_password is set with default 'root'

2024-07-26 10:57:59 2024-07-26 08:57:59+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [ERROR] [Entrypoint]: Database is uninitialized and password option is not specified
2024-07-26 10:58:00     You need to specify one of the following as an environment variable:
2024-07-26 10:58:00     - MYSQL_ROOT_PASSWORD
2024-07-26 10:58:00     - MYSQL_ALLOW_EMPTY_PASSWORD
2024-07-26 10:58:00     - MYSQL_RANDOM_ROOT_PASSWORD

@bestlong i tried but service isnt starting
mysql_root_password is set with default 'root'

2024-07-26 10:57:59 2024-07-26 08:57:59+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [ERROR] [Entrypoint]: Database is uninitialized and password option is not specified
2024-07-26 10:58:00     You need to specify one of the following as an environment variable:
2024-07-26 10:58:00     - MYSQL_ROOT_PASSWORD
2024-07-26 10:58:00     - MYSQL_ALLOW_EMPTY_PASSWORD
2024-07-26 10:58:00     - MYSQL_RANDOM_ROOT_PASSWORD

Confirm the setting contents, run cat .env | grep ^MYSQL

@bestlong i tried but service isnt starting
mysql_root_password is set with default 'root'

2024-07-26 10:57:59 2024-07-26 08:57:59+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.4.2-1.el9 started.
2024-07-26 10:58:00 2024-07-26 08:58:00+00:00 [ERROR] [Entrypoint]: Database is uninitialized and password option is not specified
2024-07-26 10:58:00     You need to specify one of the following as an environment variable:
2024-07-26 10:58:00     - MYSQL_ROOT_PASSWORD
2024-07-26 10:58:00     - MYSQL_ALLOW_EMPTY_PASSWORD
2024-07-26 10:58:00     - MYSQL_RANDOM_ROOT_PASSWORD

Confirm the setting contents, run cat .env | grep ^MYSQL

for me u doesnt need spend time for this mistake. I switch to mariadb -> worked fine ;)

cat .env | grep ^MYSQL
MYSQL_VERSION=8.4
MYSQL_DATABASE=default
MYSQL_USER=default
MYSQL_PASSWORD=secret
MYSQL_PORT=3306
MYSQL_ROOT_PASSWORD="root"
MYSQL_ENTRYPOINT_INITDB=./mysql/docker-entrypoint-initdb.d


Can we set max duration selection only to two hours ?

Can we set max duration selection only to two hours ?

There is a parameter for max selection duration. Just add
maxDuration: Duration(hours: 2)
That should do the trick


Autoware won't start on a downward slope

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
This is a problem I have observed on site so I wasn't sure what was the cause, but I could easily reproduce it with the planning simulator.
In this example, the vehicle has to cross a short hilly road:

When the vehicle starts from 0km/h on the upward slope, there is no problem. But if it has to start from the downward slope, then it will simply not move. There is no problem if the vehicle has some velocity.
I understand the longitudinal controller adjusts target acceleration based on the slope, but here the vehicle will simply not start at all. I remember that when this happened on our vehicle, the control command sent by Autoware to the vehicle was stuck at target velocity = 0.25, target acceleration = -0.4.
Considering the longitudinal controller is PID based, I would expect the vehicle to reach desired velocity/acceleration even if the slope compensation overshoots. Setting enable_slope_compensation: false in the pid.param.yaml config file fixes the issue (so it is related to slope compensation logic)
The video below shows the issue, reproduced with the planning simulator:
downward_slope-2023-10-24_14.28.44.webm
Expected behavior
Vehicle should be able to start from downward slope.
Actual behavior
Stuck
Steps to reproduce
Planning simulator + hilly lanelet
Versions
No response
Possible causes
No response
Additional context
No response

There is no gravity in planning_simulator, this should be the cause of this behavior in the planning simulator. Because while the vehicle in the slope, there is no force in the x direction.

@brkay54 I think it is a problem if the slope compensation may stop the vehicle forever. With the PID alone, the vehicle struggles to reach the desired acceleration, but at least it never get stuck.
A few weeks ago I also had the same issue on a different vehicle. There was a stop line on a road going slightly down. Autoware would often stop at the stop line and never restart. I never understood why autoware was sending negative acceleration values while it was supposed to accelerate. But now I think it was caused by the slope compensation.

@VRichardJP Thank you for the comment and sorry for the late reply.

@brkay54 I think it is a problem if the slope compensation may stop the vehicle forever. With the PID alone, the vehicle struggles to reach the desired acceleration, but at least it never get stuck.

Yes, I think it is a problem too. However, the problem you mentioned above (stucks in psim) is a different issue. This issue is the result of not implementing gravity in psim. Just I want to clarify it.

A few weeks ago I also had the same issue on a different vehicle. There was a stop line on a road going slightly down. Autoware would often stop at the stop line and never restart. I never understood why autoware was sending negative acceleration values while it was supposed to accelerate. But now I think it was caused by the slope compensation.

For the issue that arises in real vehicle tests, I also agree with you. We saw the same problem on our tests too. It is normal to send negative acceleration values in a downward slope but sometimes it can not move the vehicle.
To avoid this problem, what we did was increase the engage acceleration value. (here).
However, it was not a good solution. I think to avoid getting the vehicle stuck, we should add another functionality. This functionality should handle this getting stuck problem. IMO, we should add another state to pid_controller called starting (currently we have 4 state: stopped - stopping - driving - emengency). In the starting state, if everything is okay and the vehicle is not moving, it should force the vehicle to move smoothly.

I didn't check the current algorithm in details, but I think the PID controller should be able to compensate for overshot slope compensation, no?
For example, if target acceleration is +0.25m/s2, PID output +0.2 throttle and slope compensation adds a -0.4. Then initially the brakes are pushed. However if the vehicle does not move with that, then the difference between PID target and actual acceleration will quickly accumulate into the PID integral value. Eventually, the PID output will increase enough to compensate for the overshot slope compensation. But here it does not happen (so I guess the implementation is not exactly that).
Note that in this case, the PID controller should also be able to start the vehicle in the planning simulator. Actually, the simulator is a good example of slope compensation overshooting since there is no gravity.

However, the problem you mentioned above (stucks in psim) is a different issue. This issue is the result of not implementing gravity in psim

With regards to the PSIM, it currently supports pitch angle consideration from PR4941. But recently we found some bug, which should be solved with the following PR#5501.

However if the vehicle does not move with that, then the difference between PID target and actual acceleration will quickly accumulate into the PID integral value. Eventually, the PID output will increase enough to compensate for the overshot slope compensation. But here it does not happen (so I guess the implementation is not exactly that).

The topic was discussed in the Planning Control WG yesterday (meeting notes). TIER IV have decided to fix this issue, and we will open a discussion thread soon to present our solution.
on the side note, @VRichardJP, internally we dont really have a suitable map to test, therefore, is it possible to share your vector map with us, so that we can test our proposal later?

Thank you for reporting this issue @VRichardJP I have oppened an issue to discuss possible solutions here

@zulfaqar-azmi-t4
Unfortunately, I don't think I can share that map. But if you like I could create a hilly lanelet2 map on which the issue can be reproduced.

@zulfaqar-azmi-t4
You can use these maps LeoDrive created for test catalogs, some of them has precise slopes so might be useful:
https://drive.google.com/drive/folders/17a_99Gn6EdIrq8xrybN47hnKBPadECGj?usp=sharing

@VRichardJP this merged PR introduces a way to enable error integration, even if the ego vehicle is starting from a complete stop. The feature is disabled by default. But it can be enabled by setting the   enable_integration_at_low_speed parameter to true; you can also tune how long you want the PID to wait (while the vehicle does not move or moves at a very low speed) before integrating the error by changing the time_threshold_before_pid_integration. The parameters can be found here: https://github.com/autowarefoundation/autoware_launch/blob/main/autoware_launch/config/control/trajectory_follower/longitudinal/pid.param.yaml You can read more about it here: https://github.com/autowarefoundation/autoware.universe/blob/main/control/pid_longitudinal_controller/README.md#pid-control
I believe this feature should be enough to compensate for errors in the slope compensation. Please let me know if this solves the issue and the ticket can be closed.

@danielsanchezaran thanks for the PR.
I am curious what happens if the vehicle is kept stopped, not engaged. Does it fill the I term? Does it reset on vehicle engage? If so it means the vehicle may start suddenly when engaging the vehicle while autoware is in auto mode (is it possible?)

@danielsanchezaran thanks for the PR.
I am curious what happens if the vehicle is kept stopped, not engaged. Does it fill the I term? Does it reset on vehicle engage? If so it means the vehicle may start suddenly when engaging the vehicle while autoware is in auto mode (is it possible?)

@VRichardJP Do you mean: What happens if you set a start and a goal for the vehicle, but do not press the "Auto" button (or send the engage command)? In that case, the timer won't start. As you can see in this video: https://github.com/autowarefoundation/autoware.universe/pull/5549#issuecomment-1820449785 the timer only starts ticking when I press "Auto" (for the video example I set a time threshold of 5 seconds) and the integration does not start until the time threshold is reached.

@VRichardJP can we close this issue? I believe https://github.com/autowarefoundation/autoware.universe/pull/5549 solves the problem

Yes I think it is ok!