I recommend always testing all three packages together

(PredictMD, PredictMDExtra, PredictMDFull)

bors r+

bors r+

bors r+


Prep some demo tags

Add a list of assets to use for demo/testing

Tags

0x3b3ee1931dc30c1957379fac9aba94d1c48a5405/69049

So some of these assets work, some do not.  This is frustrating but whatever, welcome to the world of 3d modeling and tools and proprietary formats.  I have a decent representative set now.  A bad model, a few good ones, and a few whatever average models.  Very representative of the NFT world.

Using this https://www.qr-code-generator.com/ to generate QRs for the label to put on tags.

This is now done, qr labels also done.


Add Catalan flag

Update IsoUtils, Flag image folder and txt file with flag list

Can you please squash the commits into one? Having the copy paste mistakes etc in the history is not really helpful.

Done

Thanks, merged.
I've not tried the squash and merge in the UI, but it doesn't help me with review and it won't write an appropriate commit message on its own, plus I do not like modifying other people's code if avoidable.
But yeah, if you had not replied I would have fixed it myself one way or another :)


Manually importing the FlagPhoneNumber/Source/ in Xcode 10.2 shows error

Describe the bug
Manually importing the FlagPhoneNumber/Source/ in Xcode 10.2 shows error inside FPNTextField.swift. Following are the error:
Invalid redeclaration of 'countryPicker.storage'
Use of undeclared type 'NBPhoneNumber'
Use of undeclared type 'NBAsYouTypeFormatter'
Use of undeclared type 'NBPhoneNumberUtil'
Use of undeclared type 'NBEPhoneNumberFormat'
Use of unresolved identifier 'NBAsYouTypeFormatter'

I'm seeing the same issue. There's no real way to rectify this and the library is completely unusable if trying to manual import


cannot import wsgiserver

Hi, I'm not able to make the validator running locally. Probably due to missing some of the dependencies, but I'm out of ideas what next must be installed.
Running the main.py I'm getting the following error:
$ python --version
Python 2.7.6
$ sudo python ./bottle-yang-extractor-validator/main.py
Bottle v0.12.13 server starting up (using CherryPyServer())...
Listening on http://<IP_ADDRESS>:8080/
Hit Ctrl-C to quit.

Traceback (most recent call last):
  File "./main.py", line 253, in <module>
    run(server='cherrypy', host='<IP_ADDRESS>', port=port)
  File "/usr/local/lib/python2.7/dist-packages/bottle-0.12.13-py2.7.egg/bottle.py", line 3127, in run
    server.run(app)
  File "/usr/local/lib/python2.7/dist-packages/bottle-0.12.13-py2.7.egg/bottle.py", line 2787, in run
    from cherrypy import wsgiserver
ImportError: cannot import name wsgiserver

I have tried it on Ubuntu 14.04 and 16.04 and on openSUSE with the same results. In all cases the cherrypy-wsgiserver (which seems to be connected with the error according to its name) is installed in version 0.1dev.

Hi Radek,
How did you install the validator? All requirements including cherrypy are spelled out in setup.py and should be pulled in accordingly. So if installing by setup.py or pip, this should not happen :-)

I have used the setup.py and installation was ok:
$ sudo python2 ./setup.py install
root's password:
running install
running bdist_egg
running egg_info
writing requirements to bottle_yang_extractor_validator.egg-info/requires.txt
writing bottle_yang_extractor_validator.egg-info/PKG-INFO
writing top-level names to bottle_yang_extractor_validator.egg-info/top_level.txt
writing dependency_links to bottle_yang_extractor_validator.egg-info/dependency_links.txt
reading manifest file 'bottle_yang_extractor_validator.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'bottle_yang_extractor_validator.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator
creating build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/views
copying build/lib/bottle-yang-extractor-validator/views/rest.tpl -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/views
copying build/lib/bottle-yang-extractor-validator/views/about.tpl -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/views
copying build/lib/bottle-yang-extractor-validator/views/result.tpl -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/views
copying build/lib/bottle-yang-extractor-validator/views/main.tpl -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/views
copying build/lib/bottle-yang-extractor-validator/main.py -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator
creating build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/static
creating build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/static/css
copying build/lib/bottle-yang-extractor-validator/static/css/pyangui.css -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/static/css
copying build/lib/bottle-yang-extractor-validator/__init__.py -> build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator
byte-compiling build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/main.py to main.pyc
byte-compiling build/bdist.linux-x86_64/egg/bottle-yang-extractor-validator/__init__.py to __init__.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying bottle_yang_extractor_validator.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bottle_yang_extractor_validator.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bottle_yang_extractor_validator.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bottle_yang_extractor_validator.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying bottle_yang_extractor_validator.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
creating 'dist/bottle_yang_extractor_validator-0.3-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing bottle_yang_extractor_validator-0.3-py2.7.egg
Removing /usr/lib/python2.7/site-packages/bottle_yang_extractor_validator-0.3-py2.7.egg
Copying bottle_yang_extractor_validator-0.3-py2.7.egg to /usr/lib/python2.7/site-packages
bottle-yang-extractor-validator 0.3 is already the active version in easy-install.pth

Installed /usr/lib/python2.7/site-packages/bottle_yang_extractor_validator-0.3-py2.7.egg
Processing dependencies for bottle-yang-extractor-validator==0.3
Searching for CherryPy==10.2.1
Best match: CherryPy 10.2.1
Adding CherryPy 10.2.1 to easy-install.pth file
Installing cherryd script to /usr/bin

Using /usr/lib64/python2.7/site-packages
Searching for xym==0.3
Best match: xym 0.3
Processing xym-0.3-py2.7.egg
xym 0.3 is already the active version in easy-install.pth
Installing xym script to /usr/bin

Using /usr/lib/python2.7/site-packages/xym-0.3-py2.7.egg
Searching for bottle==0.12.13
Best match: bottle 0.12.13
Processing bottle-0.12.13-py2.7.egg
bottle 0.12.13 is already the active version in easy-install.pth
Installing bottle.py script to /usr/bin

Using /usr/lib/python2.7/site-packages/bottle-0.12.13-py2.7.egg
Searching for six==1.9.0
Best match: six 1.9.0
Adding six 1.9.0 to easy-install.pth file

Using /usr/lib/python2.7/site-packages
Searching for portend==1.8
Best match: portend 1.8
Adding portend 1.8 to easy-install.pth file

Using /usr/lib/python2.7/site-packages
Searching for cheroot==5.3.0
Best match: cheroot 5.3.0
Adding cheroot 5.3.0 to easy-install.pth file

Using /usr/lib/python2.7/site-packages
Searching for requests==2.13.0
Best match: requests 2.13.0
Processing requests-2.13.0-py2.7.egg
requests 2.13.0 is already the active version in easy-install.pth

Using /usr/lib/python2.7/site-packages/requests-2.13.0-py2.7.egg
Searching for tempora==1.6.1
Best match: tempora 1.6.1
Adding tempora 1.6.1 to easy-install.pth file
Installing calc-prorate script to /usr/bin

Using /usr/lib/python2.7/site-packages
Searching for pytz==2015.2
Best match: pytz 2015.2
Adding pytz 2015.2 to easy-install.pth file

Using /usr/lib/python2.7/site-packages
Finished processing dependencies for bottle-yang-extractor-validator==0.3

Anyway, I'm getting the same error even when I try to install autowsgiserver which is based on cherrypy:
$ sudo pip install autowsgiserver
Collecting autowsgiserver
  Using cached autowsgiserver-0.1.26.zip
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-5oywplb0/autowsgiserver/setup.py", line 12, in <module>
        from autowsgiserver.info import NAME_SHORT, DESCR, VER_MAJOR, VER_MINOR
      File "/tmp/pip-build-5oywplb0/autowsgiserver/autowsgiserver/__init__.py", line 13, in <module>
        import cherrypy.wsgiserver
    ImportError: No module named 'cherrypy'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-5oywplb0/autowsgiserver/

so it seems to me that something is wrong with the cherrypy package. What distro are you using? I can try it in virtualbox.

Hi, it seems that CherryPy does not include wsgiserver in the latest versions -  cherrypy/cherrypy#1481. Possible solution is to use some older version of CherryPy:
pip install "cherrypy>=3.8.0,<9.0.0"

(Belated) thanks @rkrejci , I am updating the cherrypy requirement for the upcoming release.


Add Pan/Tilt/Zoom to View menu; change Tilt shortcut

Closes #1352
Closes #1365

Code looks good, @Keavon can you check the behaviour?

[ ] RMB abort doesn't appear to work. We also want LMB confirm (including that being added to the hint bar).

I also got to try this iteration of the updated keys where Alt+LMB is used for tilt and I realized this conflicts with Alt+LMB interaction with the viewport layers (e.g. to duplicate the dragged shape, to resize around the center of a bounding box, etc.), so I need to devise another iteration. Here it is:

MMB navigation family (ergonomic by only taking one modifier key, but requires the ability to MMB drag which might not be possible on all input devices like trackpads):

[ ] MMB drag -> pan
[ ] Alt+MMB drag -> tilt
[ ] Shift+MMB drag -> zoom

Space+LMB navigation family (for users who can only LMB drag with their input hardware, Space is a modifier that moves the shortcuts from working with MMB to LMB without conflicting with artwork editing):

[ ] Space+LMB drag -> pan
[ ] Space+Alt+LMB drag -> tilt
[ ] Space+Shift+LMB drag -> zoom

Each of these keeps Ctrl available for increment snapping and RMB available for abort. Unfortunately Space+Alt+Ctrl for snapping during a tilt is unergonomic but tilting is the most rare and increment snapping during the tilt is even rarer.
We probably should display the MMB navigation family's keyboard shortcuts by default in the hint bar and View menu, not the more verbose Space+LMB accessibility mode.
Lastly, we want the Navigate tool to also fit in consistently with this scheme. As its icon shows a zoom and tilt, we don't need to technically support pan meaning that operation will be the same as its global operation, but shown in the hint bar for teaching purposes.

Navigate tool family (which exists to provide a way to navigate without the ability to MMB or RMB drag for users who need to learn the shortcuts from the hints bar instead of using the global modes):

Space+LMB drag -> pan (actually just the global navigation, but shown in hints bar)
Alt+LMB drag -> tilt
Shift+LMB drag -> zoom (should also support LMB drag, without Shift, as an alias but hints should show Shift+LMB drag for learning purposes to match with the global modes)
LMB click -> zoom in (unique to the Navigate tool)
Shift+LMB click -> zoom out (unique to the Navigate tool)

Switching this back to a draft for now while awaiting those comments to be addressed, thanks @Ezbaze. As always, let me know if you have questions or need any help.

this should be closed as of merging #1419


Can't change language by changing the URL

I'm on the Nextra Docs theme. I have content with multiple languages on the website. I have a dropdown on the site where I can change the language to any. But it seems like the language change can only be done by that dropdown.
Is it possible to fix that?  Like if a Spanish user (who previously set his language to Spanish (es) enters /ar/some-blog on the URL, I want to take him to the Arabic version of the blog...not redirect him to his previously settled language /es/some-blog.
Why is this bug/error happening? How to fix it?
Heres a video replication of the error:
https://youtu.be/CzOUIWCZkTM

Any Help/Insight? @B2o5T @promer94 @shuding ?

I've updated my nextra package, and the issue seems to be gone. Current I'm on version 2.3.0


Integration of version numbers from the native code

In my SQLite3MultipleCiphers-NuGet @bricelam made quite some effort to

Add information about the used versions of SQLite3 Multiple Ciphers and SQLite to the package description automatically
Verify in the test procedure that the corresponding versions were really used

Is there a way to add this version information to the SQLitePCLRaw packages, too? IMHO it would be useful for users of the packages to easily find out which versions are bundled with the NuGet packages.
Originally posted by @utelle in https://github.com/ericsink/SQLitePCL.raw/issues/566#issuecomment-1807101451

I would have to look at what Brice did in the other repo and figure out how to integrate it here.  I do agree it would be helpful for people to be more easily see the version information of the underlying native code assets.


Receiving the error " Object reference not set to an instance of an object." when the trainer encounters a Pokemon. is effecting 100% of all my scripts that involve attacking that previously worked.  Scripts that catch pokemon and run away from the rest are uneffected.

Object reference not set to an instance of an object
THIS IS NOT DUE TO SCRIPTING.
https://proshine-bot.ml/viewtopic.php?id=905
As you can see someone reffered me to come here after working out that it is NOT the SCRIPT that is causing this bug.

This is not 'No action executed'.
This is Object reference not set to an instance of an object.
This effects me and 3 other people. We can use scripts that work for other people, but they will not work for us.

The previous issue can be reopened with more information on how to reproduce the bug.
Do not create duplicate as it only reduce the readability of the tickets.


[BUG] the topic can not remove after the producer and consumer finished

Describe the bug
the topic can not remove after the producer and consumer finished.
To Reproduce
1, create a partitioned topic
pulsar-admin persistent create-partitioned-topic t-kop/ns-kop/lookup2 --partitions 30
2, produce 100 message using the created topic
3, consume all produced messages.
4, delete the used topic lookup2 with pulsar command
./bin/pulsar-admin topics delete-partitioned-topic  t-kop/ns-kop/lookup2
5, See error:
Failed to perform http delete request: javax.ws.rs.ClientErrorException: HTTP 412 Precondition Failed Topic has active producers/subscriptions
Expected behavior
the topic can remove after the producer and consumer finished.
Screenshots

Yeah, it's an existed issue for a long time because the OffsetAcker holds consumers for acknowledgement. I think there's a better way to do it.

added comments in the PR


Support alternate format for Utf8 unparsing (CHAR)

Which issue does this PR close?
PR addresses Utf8 unparser issue producing invalid CAST(col AS TEXT) SQL for MySQL.
Rationale for this change
MySQL cast function does not support TEXT and requires CHAR for CAST (automatically returns VARCHAR, TEXT, LONGTEXT)

CHAR[(N)] [charset_info]
Produces a string with the VARCHAR data type, unless the expression expr is empty (zero length), in which case the result type is CHAR(0). If the optional length N is given, CHAR(N) causes the cast to use no more than N characters of the argument. No padding occurs for values shorter than N characters. If the optional length N is not given, MySQL calculates the maximum length from the expression. If the supplied or calculated length is greater than an internal threshold, the result type is TEXT. If the length is still too long, the result type is LONGTEXT.

Example query:
 select * from customer where c_custkey = 'building

Before this change (fails in MySQL)
SELECT `customer`.`c_custkey`, ... FROM `customer` WHERE (CAST(`customer`.`c_custkey` AS TEXT) = 'building')

After this change (works in MySQL)
SELECT `customer`.`c_custkey`,  ... FROM `customer` WHERE (CAST(`customer`.`c_custkey` AS CHAR) = 'building')

What changes are included in this PR?
PR introduces configurable use_char_for_utf8_cast dialect parameter that controls whether CHAR vs TEXT/VARCHAR is   used for Utf8 unparsing.
Are these changes tested?
Yes, added unit tests + manual testing
Are there any user-facing changes?
CustomDialectBuilder now supports use_char_for_utf8_cast that can be used to specify whether CHAR vs TEXT/VARCHAR data type should be used for Utf8 unparsing.

I had a suggestion on the API -- let me know what you think

@alamb - 👍 I was thinking about this as well, but was unable to come up with other good potential types for string unparsing (asf data types) so decided to proceed with this approach. As we have more people thinking that we should better to return the type here I'll update my PR.
Note - as we have different types for Utf8 and LargeUtf8 there will be two functions/settings.


use path for config file

What
Fix issue caused by bad removal of rebase
Command should use /tmp/ folder not config_file_dir

Verified locally. The script now prompts the user with the license


Allow underscores and commas in numbers

Commas are maybe questionable? But I use underscores a fair bit.

Underscores make sense, but commas I'm not so sure about, in some locales they are used as decimal separators:
https://en.m.wikipedia.org/wiki/Decimal_separator
I think errors are preferable for now, it might cause confusion for users of these locales to enter "9,99" expecting 9.99, but instead getting 999.

Yup, makes sense. I got rid of comma support.


Make test case use snippetcompiler_clean fixture

Description
The test case test_version_snapshot was using the snippetcompiler fixture while it should use the snippetcompiler_clean fixture. This PR resolved that problem.
Self Check:

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Merged into branches master in 9b82547c3a3746f4552b07480c41b816667ac5c8

Processing #4691.

Processing #4691.


Update to windows 0.43

A new windows-rs version came out so we all have to upgrade again.

False alarm, looks like only windows-rs got updated, not windows-sys


Make trts functions explicit

This also normalizes the trts crate to use the common SGX builder.rs
functionality.

Current dependencies on/for this PR:

develop

PR #45

PR #49   👈

This comment was auto-generated by Graphite.


[SPARK-17636] Parquet filter push down doesn't handle struct fields

What changes were proposed in this pull request?
Changes DataSourceStrategy#translateFilter to operate on a NamedExpressions rather than just and Attribute, as it switches off of the name property, defined in NamedExpressions. GetStructField now implements NamedExpression.
How was this patch tested?
Testing thus far is manual, using debugger, explain plan output, and logging from the ElasticSearch connector. This patch includes no test changes; please advise on where/how to add test coverage.

Can one of the admins verify this patch?

Hi @ndimiduk, it seems failed to build. Extending NamedExpression seems breaking ResolveAliases.
I tested this with the codes below:
Seq(Tuple1(Tuple1(1) :: Nil)).toDF.selectExpr("_1[0]._1")

BTW, even if we push the dot-separated names, this would not support the push-down in Parquet because ParquetFilters itself does not handle nested columns (see https://github.com/apache/spark/blob/7730426cb95eec2652a9ea979ae2c4faf7e585f2/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFilters.scala#L187-L234).
As it checks the field names in the schema, it pushs down nothing. Also, I think we definitely need a test.

See https://github.com/apache/spark/blob/7730426cb95eec2652a9ea979ae2c4faf7e585f2/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFilters.scala#L158-L160 too.

Thanks for having a look @HyukjinKwon. I agree a test is needed. I'm new to Spark code base, so please direct me -- I assume there's an existing suite or suites that I can extend with coverage for this case. Also, please track the history I refer to on the ticket -- my use-case is not parquet, but the Elastic Search connector. This patch is enough to push necessary information down to ES, at least with my basic testing.
My original ticket was closed as a dupe of the Parquet issue; notice also my comment requesting SPARK-17636 be renamed so as to not be Parquet-specific. Would it be better to re-open my original ticket and address the catalyst changes there? After that, 17636 can make subsequent changes to get fixes into Parquet.

For adding a test, I usually go to the blame button and check where the tests were added in the recent commits. It seems FilteredScanSuite is the right place assuming from https://github.com/ndimiduk/spark/commit/7bc9a8c6249300ded31ea931c463d0a8f798e193.
Yes, I saw that JIRA was closed. I think anyone definitely can re-open the JIRA if anyone is pretty sure and it could be fixed separately as a coherent unit. I think that's fine.

@ndimiduk Let's close this for now if it is going to be inactive. I am not sure of the current way due to the test failure and we can continue to discuss this in the JIRA. If you think the JIRA should be re-open, please re-open with leaving a comment to explain why it should be re-open.

Close the PR you mean? That's fine, I'm afraid I won't be able to make this a priority in the near term. Please don't close the JIRA though -- this is a big problem.

Yes, I meant closing this PR if you don't have a better idea for now or some time to try another approach soon. Feel free to reopen or make another one whenever you are willing to. Yes, I would not. Thank you.

https://github.com/apache/spark/pull/16578 PR should solve this

No, this is filter push down whereas that one is column pruneing.

Does that one deal with nested filter access as well we nested column pruning?


chore(ui): Delete unused ESLint disable directives

Description
Follow up upgrades in #13164
Especially delete comments that are copy-paste of integration forms by contributors from other teams to reduce potential confusion.
Find in Files eslint-disable after deletions

ui/apps/platform/cypress folder has 2 results in 2 files
ui/apps/platform/src folder has 210 results in 154 files

User-facing documentation

[x] CHANGELOG update is not needed
[x] documentation PR is not needed

Testing and quality

[x] the change is production ready: the change is GA or otherwise the functionality is gated by a feature flag
[ ] CI results are inspected

Automated testing

[x] updated lint configuration
[ ] added unit tests
[ ] added e2e tests
[ ] added regression tests
[ ] added compatibility tests
[ ] modified existing tests

How I validated my change

npm run lint

ui-e2e-tests failure:

Exception Management - Approved False Positives Table should be able to navigate to the Request Details page by clicking on the request name: should be able to navigate to the Request Details page by clicking on the request name

Timed out retrying after 4000ms: Expected to find element: h1:contains("UU-241111-9"), but never found it.


0.30.5 aws community edition update

Hello,
The latest version of meilisearch is 0.30.4 on aws community edition in frankfurt region.  Which has critical document duplication  bug on search.  Is is possible to update the latest version to 0.30.5?
Thanks,
Özgür.

Hi @ozgurhangisi,
Sorry for the inconvenience. Yes, the new version should be published soon I will try to do it this week. I'll let you know when it's done.

Hi @ozgurhangisi,
The AMI is published so I will close this issue. Feel free to reopen it if there is a problem.


Content-Length modification after body write

Add an header after the response was sent is not possible. (https://github.com/containous/oxy/blob/ad5bdb606fa9c64db267f0e43d63834908bdb05e/forward/fwd.go#L204)
@emilevauge  did the fix a year ago in https://github.com/containous/oxy/commit/183212964e13e7b8afe01a08b193d04300554a68
But he had to rollback it to fix an empty response issue in traefik https://github.com/containous/traefik/pull/476
Need to be fixed

/cc @tcolgate

The code has changed and this doesn't exists anymore (we use httputil.ReverseProxy)


CLOUD-59542 create unit tests for salt orchestrator

@keyki @doktoric pls review

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2673/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/164/


.md-overlay-container added out of app container

Looks like

inserted into markups BODY tag childrens, instead of adding it to the list of app root element children.
For example looks at markup I get after click on menu button:

  <jmc-admin ng-version="2.4.1" _nghost-aod-23="">

  </jmc-admin>

This behavior broke style association: all styles automatically prefixed with "_nghost-aod-23" attribute by angular compiler, but md-overlay-container is out of the app container and selectors like ".md-overlay-container[_ngcontent-aod-23]" does not match it.
Plunker: http://plnkr.co/edit/qDCkFvodD5wBqFoZIdRC?p=preview
As you see, element added out of app scope. It rendered well just because application is not compiled with angular AoT compiler.

This is working as intended. The overlay container is added directly to the body in order to prevent overlays from being clipped by a containing element. The current recommendation is to style overlays using a CSS file loaded via <link> element in your index.html.

@jelbourn  hi, i have one problem that i want to remove this overly container, and the dialog's position can custom. this idea can achieve? if not ,have you some good suggestions? thank u very much.


Bower support for multiple apps

Brunch's support for multiple apps is working like a charm, but ideally it would also support multiple Bower instances:
backend/
    assets/
    scripts/
    styles/
    vendor/
    bower_components/
    bower.json
frontend/
    assets/
    scripts/
    styles/
    bower_components/
    bower.json
server/
    ...
public/
config.coffee
package.json

Right now, my_app/bower_components gets picked up by the compiler, but the content isn't run through read-components.
Please correct me if I'm wrong, or if there's a workaround way to solve this.

At the moment Brunch is not really designed to support multiple apps. The support is for multiple build environments. So your options are to either give each of your apps their own brunch-config and run them separately or combine your bower.jsons into one at the parent level and use the environment config to include/ignore the correct ones for each app.
One other possibility is to leverage the as-yet-unreleased preCompile hook (#928) to copy the appropriate (per environment flag) bower.json file to the parent level before Brunch kicks off its pipeline.

So your options are to either give each of your apps their own brunch-config and run them separately

Thanks @es128, that's my current setup, and it works fine. Just thought I'd voice the idea, since there at least used to be an interest in multiple app support (#281).

Yes, appreciate your thoughts.
I consider multiple apps support to be in scope for Brunch 2.0, but the high-level design needs to be determined before worrying about the kind of detail you're calling out here. What I've thought about so far is that each app will have its own brunch-config, but the new feature would be that a single CLI command could kick off several watch and/or build cycles at once with unified logging and possibly some degree of resource sharing (like the watcher instance) if it can be done in a way that increases efficiency.

Since there's already brilliant support for multiple app dirs (distributed assets/, vendor/ etc), it might be easiest to give read-components a flexible starting point, like conventions.assets?
Anyway, perhaps this is indeed an edge case. Looking forward to 2.0, and I'll ping if I manage to come up with something more concrete.

Has this been implemented? If so, where can one find more information on how to use this feature?

@KrishnaPG no, this has not been implemented

Thank you @es128
In the current version, is it possible to make brunch work recursively (e.g., parent folder has a brunch config that specifies the include paths of children brunch configs in their own directories, and when build is run on the parent, all children will be built recursively) ?
Any plugin or workaround will also be helpful.


'cellid' File?

Whenever I enter a steam guard code to initially verify an account, this file is created:
https://gyazo.com/3a1ae145ccdc9d4a7fe0578c790e71d9
Can you explain what this file does?

It's supposed to be the datacenter/cluster/LAN/whatever's overarching ID in Valve's network that your account is on if I recall correctly.

My goal with node-steam-user is to provide as much parity with the official Steam Client as possible. There have been instances in the past where unofficial clients all broke due to a backend change that didn't affect the official client. For example, a few months ago, clients were barred from logging on if they didn't send a well-formed machine ID in their login request. That change was reverted within about a half hour due to incompatibilities with the official Linux client, but there's nothing saying that something similar couldn't happen again.
After you log on, the CM sends you a "cell ID". Steam divides the world into regions, called "cells". There's a list here. The official client saves this ID, and sends it back in subsequent login requests.
To provide parity, node-steam-user does the same.


Roman

removing /workbench and adding extension repo link to composer

@aligajani who has right access ?

Howdy @romanzpolski.
I assume this was not intended to be sent to this repository. This is the home of the Flarum software. Merging this would mean that all our users would enjoy your changes, whereas you probably only meant to have them for your own installation. :wink:
Thus, I am closing this merge request.

@franzliedke lols thanks for this :)


Extensions Supported by Microsoft

Are the Extensions listed on this page supported by Microsoft. i.e. if we run into issues can we raise a support ticket to get someone from Microsoft to take a look at it or is it a "use at own risk component where the standard Microsoft legal terms don't apply? https://azure.microsoft.com/en-au/support/legal/

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 08d2543f-f47a-e9dc-1f80-1ac5ad7a71ad
Version Independent ID: cc5f4337-01f7-4774-6c26-fda65fadbdbf
Content: Extensions - Azure Database for PostgreSQL - Single Server
Content Source: articles/postgresql/concepts-extensions.md
Service: postgresql
Sub-service: single-server
GitHub Login: @sunilagarwal
Microsoft Alias: sunila

@pnarsi Thank you for the feedback. For different version of Postgres different extensions are supported and these are listed in the document already. If you face any problem/issue while implementing them you can surely raise the support ticket as they are already mentioned in MS documentation, or post your query on Microsoft Q&A forum.
However if any feature or service is out of support, Microsoft publishes it well in advance and then the support will not be able to serve the request.

Thanks for clarifying @AnuragSharma-MSFT


xgboost hangs on ncclAllReduce

Reproducible on ppc, haven't see in on x86_64
More details https://github.com/h2oai/h2o4gpu/issues/773
nccl: v2.4.2-1 installed from sources
Looks similar to https://github.com/dmlc/xgboost/issues/4107

Also happens on x86_64 and nccl 2.4.7
@trivialfis any ideas?

Will look into this.

@sh1ng @pseudotensor I factored out:
https://github.com/h2oai/h2o4gpu/blob/master/tests/python/open_data/gbm/test_xgboost.py
and
https://github.com/h2oai/h2o4gpu/blob/master/tests/python/open_data/gbm/test_gpu_prediction_pickledmodel.py
Compiled nccl v2.4.7-1 on Ubuntu 18.10 x86_64.  Ran above tests 5 times each with n_gpus set to 2, and haven't see seen any issue so far.

One cause of this can be an unexpected number of threads in the team for omp. For example if there are two GPUs but only one thread available the thread will call nccl and then wait for the other GPU to sync, but there is no other thread concurrently running. You could do some diagnostics using omp functions to see how many threads are active.

@trivialfis I've seen it on x86_64(centos docker container) only once, but it's easily reproducible on ppc
@RAMitchell thanks for the hint

Bu default sklear wrapper uses 1 thread https://github.com/dmlc/xgboost/blob/master/python-package/xgboost/sklearn.py#L244
and the parameter sets global openmp settings
v0.9
https://github.com/dmlc/xgboost/blob/v0.90/src/common/device_helpers.cuh#L1047
will definitely hang
It's fixed in master
https://github.com/dmlc/xgboost/blob/master/src/common/device_helpers.cuh#L1175

@sh1ng Thanks!  Let me add a check.

If it's confirmed, are you going to release a patch for v0.9?

@sh1ng I can backport a patch for you to apply it.  But currently @hcho3 is unavailable so I don't think we can make a new release.

I've fixed it in our fork.


Handle an LSP to Nova range no-newline-at-EOF case

When a file in Nova has no newline at the end, and gopls formatting decides to append one, it sends an LSP range one past the end of the Nova line array.
This manifests by deleting your document on format because the default Nova range is [0, document.length].

A bit wonky to discover and reproduce what was wrong because gopls seems a little inconsistent about whether it wants to put a newline at the end. Compare with this nugget in my own mothballed go extension, so I apparently ran into this in the past.

Good catch.


fix sorted() call

this is a PR to fix #124

@liorbenhorin  thanks for the PR! I will check it and merge ASAP! 😄


platform: only use English locale

Any other locale will be rejected by the NLP server as we don't
have a model for it.
Closes #57

LC_ALL=C flatpak run edu.stanford.Almond doesn't seem to solve the issue though...


Cucumber inSet: Data generator emits multiple null rows if null is specified in the set

Bug Report
An inSet request was made that included a set value of null. When the data was generated two null rows were created instead of the expected one.

Scenario: Running an 'inSet' request that includes a null entry (null) characters should be successful
Given there is a field foo
And foo is in set:
| null |
| 1    |
Then the following data should be generated:
| foo  |
| null |
| 1    |

Steps to Reproduce:

Run the above test (or InSet.feature test file)
See that Scenario: Running an 'inSet' request that includes a null entry (null) characters should be successful fails
Look at the resulting error message

Expected Result:
Field foo should generate the values 1 and null
Actual Result:
a duplicate null value was created for the field from outside of the set, as seen in the below error:

java.lang.AssertionError:
Expected: [null], [1]
but: [null], [null], [1]
missing:
counts: expected 2, but got 3
at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
at org.junit.Assert.assertThat(Assert.java:956)
at org.junit.Assert.assertThat(Assert.java:923)
at com.scottlogic.deg.generator.cucumber.steps.GeneralTestStep.theFollowingDataShouldBeGenerated(GeneralTestStep.java:105)
at ✽.the following data should be generated:(C:/DataGenerator/data-engineering-generator/generator/src/test/java/com/scottlogic/deg/generator/cucumber/InSet.feature:467)

Environment:
IntelliJ running branch Interesting-values in full generation mode.
Additional Context:
inSet has been amended to append null for all requests, it appears it does not check to see if null has already been defined.

@cakehurstryan see #353 which will disallow null to be part of a set constraint; please update these tests as appropriate.

Test is now passing as expected. Issue closed.


[Feature request] parse SQL to generate list of columns

In a similar vein to https://github.com/z3z1ma/dbt-osmosis/issues/57, I'm looking for ways to run this without needing to connect to the data warehouse.
My understanding of the current implementation is that we either pull columns from the warehouse, or rely on them being manually generated ahead of time. What I would like to see additionally is an option to parse the compiled SQL, derive the names of the columns outputted by the model, and scaffold those into the yaml files - with appropriate upstream descriptions if applicable.
Presumably this would be added somewhere here, and controlled through a CLI flag. We can require a manifest, similar to the catalog option, to avoid parsing dbt during runtime.
This would enable fully self-contained generation and propagation of documentation, without the need for large manual data entry or connections to external systems.
I'm happy to take a stab at this if you think it makes sense to include?

Thats a cool idea. Implementation wise, its not an easy task. Its fraught with edge cases. Star expansions, lexical scoping, etc. Not to mention dbt SQL is not valid sql since it has jinja markup so we cannot generate an AST. The best bet for making this successful would be to use the compiled SQL. Compilation can be done without a connection to the DWH I think? Unless there are introspective queries ofc. So maybe we start there and do a best effort?

There is built-in DBT macro get_columns_in_query

In a similar vein to https://github.com/z3z1ma/dbt-osmosis/issues/57, I'm looking for ways to run this without needing to connect to the data warehouse.

get_columns_in_query defeats the purpose since it needs to connect to the DWH and also we use the same mechanism under the hood basically.


GitHub Actions should not be the default output template

This is more of an observation, than an issue. We use gotestfmt on CircleCI, but this is true for pretty much all other CIs and command-line usage.
gotestfmt should not default to GitHub actions output. What would be great is if .gotestfmt/package.gotpl had ::group:: and ::endgroup:: tags removed, and GitHub action for gotestfmt had a template switch for GitHub.

Then we could also use gotestfmt in our tests, as a test prettifier in terminal, win-win! 🥳
Great job, anyway! Really fun stuff!
And yes, I've read about .gotestfmt folder, I just wanted to point out reliance on GitHub Actions by default, rather as an opt-in :)

Hey @Holek, you are right. The tool has been written with my very specific needs in mind. If you'd be up for contributing a template for CircleCI, I'd be very happy about a PR. You can add the template to .gotestfmt/circleci/*.tpl in this repo, and I can add the code to detect running on CircleCI. I'll move the GitHub code to the github folder then.

Released as version v1.1.0.


Question: PBKDF2 in Earlier Safari?

I ran into this project while trying to figure out what the best way of doing pbkdf2 on safari was since the chrome code I had tried to use obviously failed.
I'm just wondering if the pbkdf2 parts will work in earlier versions of safari, and whether you know how far back it would work?

As far as I know, no version of Safari 7 supports any of the WebCrypto bits. A pure javascript library like SJCL would be your only option. Safari 8+ has support for HMAC, so you can implement a relatively fast PBKDF2 (about 5 or so times slower than native) relatively easily. (code for this is in simplecrypto)
WebKit bug for full PBKDF2 support is at https://bugs.webkit.org/show_bug.cgi?id=143458

Safari 7 has window.crypto.webkitSubtle, but its pretty hard to tell what it actually supports.
I managed to get it to do native sha1 digests and import AES-CBC keys, but it did not want to generate or load SHA-1 HMAC keys for me, but it's hard to tell if I'm just doing it wrong or if there's really no way.

I would try getting generate or importKey working in Safari 8 first. If both Safari 7 and 8 don't work, link me the piece of code you are using and I'll check it out.
If it works in Safari 8, but not in Safari 7, you should check the webkit unit test history @ https://github.com/WebKit/webkit/tree/master/LayoutTests/crypto/subtle . I don't know what version of webkit Apple is using in Safari 7 these days, but the tests for all version should be there.
Keep in mind that you might go crazy, since Apple is using older draft on WebCrypto, nothing really works as it should and there is no decent documentation.


Chaos Typing Universe

Issue: #226
https://github.com/user-attachments/assets/6cbe73c7-3096-42dd-9e3f-e1e5aaac67af

@vansh-codes Could you please review the PR

@vansh-codes ??


[TASK] Handling remaining event related to Jobs for tangle-mainnet

There are some events in tangle-mainnet that are not handled yet: JobResultSubmitted, DKGPhase2, ZkSaaSPhase2, ValidatorReward (this goes with JobResultSubmitted), this can only be handled later once the gadget is integrated
Remove Pending Jobs event as it's not necessary
Related: #170

Working on adding an example for submitting the result.

@shekohex, @vutuanlinh2k2 is telling me that this script fails. Can you confirm what steps need to be taken to make this process work?

Got error Not enough signers for threshold error when submitting Job Result

@shekohex let me know when you start working on this!

This script fails in the latest tangle for some reason that is related to signature recovery, ecdsa recovers a different key, even though it recovers to the correct key in js.
I mentioned rewriting the script in rust using webb SDK and sp_{core, io} for getting the same result as the one we do on-chain.

Let me know when you start working on this @shekohex

What is the status of this @vutuanlinh2k2?  Let me know if you need any help finishing it.

@salman01zp your help here would be appreciated. You can take over.


Fix Aggregation push down NPE issue

We need to resolve the TiColumnRef after creating them from pushdownAggregates.
Should fix https://github.com/pingcap/tispark/issues/162

@birdstorm PTAL

@birdstorm Updated according to comment.


Abstraction ready for V2

@CathPag just noticed there are conflicts in the PR -  please @ me when addressed for (re)review. Content as shown looks good.

@murillodigital not seeing the conflicts. Can you point me to them?


http attributes

This is to ensure our express plugin is compliant with the new spec https://opentelemetry.io/blog/2023/http-conventions-declared-stable/

https://github.com/rocket-connect/graphql-debugger/blob/main/plugins/express/src/attributes.ts#L2


[release-1.4] Fix sds static config for Pilot, Galley

Fix SDS bootstrap config for Pilot, Galley, and Mixer. Prior to this, even if sds is used, aforementioned components would still use file mount certs. This will break Istio if the control plane is set to use an SDS-based CA (pods like ingress gateway will fail to connect to Pilot, etc. due to having different root certs).

Configure the Mixer checker server to use sidecar for MCP connections to align with the rest of Istio control plane components.

This will be available only in 1.4.x.

@pitlv2109: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lintmodern_installer_release-1.4
fc6aa15e850e3da7b00a7fe41fc46a1591eb96dc
link
/test lintmodern_installer_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer_release-1.4
686fcca0060569575566170adf97399072dd9f07
link
/test demo_installer_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer_release-1.4
686fcca0060569575566170adf97399072dd9f07
link
/test demo_installer_release-1.4

base_installer_release-1.4
686fcca0060569575566170adf97399072dd9f07
link
/test base_installer_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

demo_installer_release-1.4
686fcca0060569575566170adf97399072dd9f07
link
/test demo_installer_release-1.4

base_installer_release-1.4
0f06c130e1ce4760b800a65f4047b0f867d76157
link
/test base_installer_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@pitlv2109: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

base_installer_release-1.4
0f06c130e1ce4760b800a65f4047b0f867d76157
link
/test base_installer_release-1.4

demo_installer_release-1.4
0f06c130e1ce4760b800a65f4047b0f867d76157
link
/test demo_installer_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Car_id selector missing in Locations Dashboard

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I have a CAR_id selector in all Dashboard, except in the Locations Dashboard
In the Variables section of that Dashboard is also a mark along the car_id Variable stating it is not referred ...

Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
docker-teslamate-1  | 2023-03-31 18:50:57.842 car_id=2 [info] Start / :offline
docker-teslamate-1  | 2023-03-31 18:50:57.848 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-03-31 18:55:39.713 car_id=1 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-03-31 19:00:20.687 car_id=1 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-03-31 19:10:21.704 car_id=1 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-03-31 19:16:24.175 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1493025668492014/vehicle_data -> 408 (82.850 ms)
docker-teslamate-1  | 2023-03-31 19:16:34.322 car_id=1 [info] Start / :asleep
docker-teslamate-1  | 2023-03-31 19:16:34.328 car_id=1 [info] Disconnecting ...
docker-teslamate-1  | 2023-03-31 19:18:14.891 car_id=1 [info] Start / :online
docker-teslamate-1  | 2023-03-31 19:18:14.898 car_id=1 [info] Connecting ...
docker-teslamate-1  | 2023-03-31 19:35:11.315 [info] Refreshing access token ...
docker-teslamate-1  | 2023-03-31 19:35:11.637 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (321.591 ms)
docker-teslamate-1  | 2023-03-31 19:35:11.640 [info] Scheduling token refresh in 6 h
docker-teslamate-1  | 2023-03-31 21:40:27.030 [warning] Streaming API: Tokens expired
docker-teslamate-1  | 2023-03-31 21:40:27.031 car_id=1 [info] Creating new connection …
docker-teslamate-1  | 2023-03-31 21:40:27.031 car_id=1 [info] Disconnecting ...
docker-teslamate-1  | 2023-03-31 21:40:27.044 car_id=1 [info] Connecting ...
docker-teslamate-1  | 2023-03-31 23:33:13.348 car_id=1 [warning] Received stale stream data: %TeslaApi.Stream.Data{elevation: 5, est_heading: 56, est_lat: 50.983556, est_lng: 3.64925, est_range: 161, heading: 56, odometer: 18229.2, power: 0, range: 196, shift_state: nil, soc: 66, speed: nil, time: ~U[2023-03-31 23:33:11.503Z]}
docker-teslamate-1  | 2023-03-31 23:54:18.149 car_id=1 [warning] Received stale stream data: %TeslaApi.Stream.Data{elevation: 5, est_heading: 56, est_lat: 50.983556, est_lng: 3.64925, est_range: 160, heading: 56, odometer: 18229.2, power: 0, range: 195, shift_state: nil, soc: 66, speed: nil, time: ~U[2023-03-31 23:54:16.226Z]}
docker-teslamate-1  | 2023-04-01 00:57:31.717 car_id=1 [warning] Received stale stream data: %TeslaApi.Stream.Data{elevation: 5, est_heading: 56, est_lat: 50.983556, est_lng: 3.64925, est_range: 159, heading: 56, odometer: 18229.2, power: 0, range: 194, shift_state: nil, soc: 66, speed: nil, time: ~U[2023-04-01 00:57:29.737Z]}
docker-teslamate-1  | 2023-04-01 01:35:11.642 [info] Refreshing access token ...
docker-teslamate-1  | 2023-04-01 01:35:11.986 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (344.210 ms)
docker-teslamate-1  | 2023-04-01 01:35:11.991 [info] Scheduling token refresh in 6 h
docker-teslamate-1  | 2023-04-01 03:35:38.865 [warning] Streaming API: Tokens expired
docker-teslamate-1  | 2023-04-01 03:35:38.866 car_id=1 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 03:35:38.866 car_id=1 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 03:35:38.872 car_id=1 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 03:52:43.560 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 03:52:43.570 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 03:54:44.858 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 216, latitude: 51.096469, longitude: 3.375278, native_latitude: 51.096469, native_location_supported: 1, native_longitude: 3.375278, native_type: "wgs", power: 5, shift_state: "R", speed: 4, timestamp:<PHONE_NUMBER>254}
docker-teslamate-1  | 2023-04-01 03:54:44.858 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 04:14:00.562 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (168.951 ms)
docker-teslamate-1  | 2023-04-01 04:14:01.066 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (502.107 ms)
docker-teslamate-1  | 2023-04-01 04:14:01.074 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 160, latitude: 51.21017, longitude: 3.442801, native_latitude: 51.21017, native_location_supported: 1, native_longitude: 3.442801, native_type: "wgs", power: 2, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>360}
docker-teslamate-1  | 2023-04-01 04:14:01.074 car_id=2 [info] Driving / Ended / 21 km – 19 min
docker-teslamate-1  | 2023-04-01 04:14:01.074 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 04:16:56.113 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9086.521 ms)
docker-teslamate-1  | 2023-04-01 04:16:56.113 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 04:16:56.114 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:17:25.205 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9090.908 ms)
docker-teslamate-1  | 2023-04-01 04:17:25.205 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 04:17:25.206 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:17:54.476 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9269.069 ms)
docker-teslamate-1  | 2023-04-01 04:17:54.476 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 04:17:54.476 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:18:14.693 [warning] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 540 (215.962 ms)
docker-teslamate-1  | 2023-04-01 04:18:14.694 [warning] TeslaApi.Error / {"error": "Get \"http://localhost:7654/vehicle_data?slow_query_time=15&headers%5BX-Request-Timeout%5D=5&let_sleep=true&user_command=true\": EOF"}
docker-teslamate-1  | 2023-04-01 04:18:14.694 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:18:37.104 [warning] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 540 (2410.184 ms)
docker-teslamate-1  | 2023-04-01 04:18:37.104 [warning] TeslaApi.Error / vehicle error: it is online but not responsive
docker-teslamate-1  | 2023-04-01 04:18:37.104 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:18:59.546 [warning] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 540 (2439.634 ms)
docker-teslamate-1  | 2023-04-01 04:18:59.546 [warning] TeslaApi.Error / vehicle error: it is online but not responsive
docker-teslamate-1  | 2023-04-01 04:18:59.547 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:19:10.683 [notice]     :alarm_handler: {:set, {TeslaMate.Vehicles.Vehicle_2_api_error, :fuse_blown}}
docker-teslamate-1  | 2023-04-01 04:19:19.744 [warning] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 540 (196.722 ms)
docker-teslamate-1  | 2023-04-01 04:19:19.744 [warning] TeslaApi.Error / {"error": "Get \"http://localhost:7654/vehicle_data?slow_query_time=15&headers%5BX-Request-Timeout%5D=5&let_sleep=true&user_command=true\": EOF"}
docker-teslamate-1  | 2023-04-01 04:19:19.745 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:19:41.071 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 04:19:41.071 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 04:19:41.071 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 04:19:41.077 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 04:26:03.867 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 04:26:03.867 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 04:26:03.867 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 04:26:03.872 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 04:26:10.690 [notice]     :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_2_api_error}
docker-teslamate-1  | 2023-04-01 04:27:43.319 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1493025668492014/vehicle_data -> 408 (9153.269 ms)
docker-teslamate-1  | 2023-04-01 04:27:43.319 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 04:27:43.319 car_id=1 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 04:32:27.496 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 04:32:27.496 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 04:32:27.496 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 04:32:27.501 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 04:34:43.609 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 04:41:10.681 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 04:43:29.918 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 04:43:29.918 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 04:43:29.918 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 04:43:29.924 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 04:55:11.101 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 04:55:11.101 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 04:55:11.101 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 04:55:11.107 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 05:11:23.192 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 05:11:23.192 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 05:11:23.192 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 05:11:23.198 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 05:25:34.961 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 05:25:34.961 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 05:25:34.961 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 05:25:34.966 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 05:39:46.120 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 05:39:46.121 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 05:39:46.121 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 05:39:46.126 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 05:52:26.921 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 05:52:26.921 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 05:52:26.921 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 05:52:26.927 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 06:07:39.554 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 06:07:39.554 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 06:07:39.554 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 06:07:39.560 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 06:21:21.727 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 06:21:21.727 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 06:21:21.727 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 06:21:21.733 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 06:36:13.447 [info] Start of drive initiated by: %TeslaApi.Stream.Data{elevation: 5, est_heading: 173, est_lat: 51.210199, est_lng: 3.442788, est_range: 150, heading: 349, odometer: 97089.5, power: 4, range: 231, shift_state: "R", soc: 74, speed: 3, time: ~U[2023-04-01 06:36:11.262Z]}
docker-teslamate-1  | 2023-04-01 06:36:13.447 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 06:41:26.223 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (196.553 ms)
docker-teslamate-1  | 2023-04-01 06:41:26.699 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (474.125 ms)
docker-teslamate-1  | 2023-04-01 06:41:26.707 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 39, latitude: 51.203285, longitude: 3.441072, native_latitude: 51.203285, native_location_supported: 1, native_longitude: 3.441072, native_type: "wgs", power: 3, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>767}
docker-teslamate-1  | 2023-04-01 06:41:26.707 car_id=2 [info] Driving / Ended / 3 km – 5 min
docker-teslamate-1  | 2023-04-01 06:41:26.708 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 06:42:35.692 [info] Start of drive initiated by: %TeslaApi.Stream.Data{elevation: 7, est_heading: 39, est_lat: 51.203285, est_lng: 3.441072, est_range: 146, heading: 39, odometer: 97091.5, power: 7, range: 227, shift_state: "D", soc: 73, speed: 0, time: ~U[2023-04-01 06:42:33.741Z]}
docker-teslamate-1  | 2023-04-01 06:42:35.692 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 06:50:38.375 car_id=1 [warning] Received stale stream data: %TeslaApi.Stream.Data{elevation: 5, est_heading: 56, est_lat: 50.983557, est_lng: 3.649252, est_range: 155, heading: 56, odometer: 18229.2, power: 0, range: 189, shift_state: nil, soc: 64, speed: nil, time: ~U[2023-04-01 06:50:35.708Z]}
docker-teslamate-1  | 2023-04-01 06:55:18.144 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (143.054 ms)
docker-teslamate-1  | 2023-04-01 06:55:18.661 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (515.639 ms)
docker-teslamate-1  | 2023-04-01 06:55:18.678 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 306, latitude: 51.316406, longitude: 3.307632, native_latitude: 51.316406, native_location_supported: 1, native_longitude: 3.307632, native_type: "wgs", power: 3, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>717}
docker-teslamate-1  | 2023-04-01 06:55:18.678 car_id=2 [info] Driving / Ended / 17 km – 13 min
docker-teslamate-1  | 2023-04-01 06:55:18.678 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 06:55:22.386 [info] Start of drive initiated by: %TeslaApi.Stream.Data{elevation: 1, est_heading: 306, est_lat: 51.316406, est_lng: 3.307632, est_range: 128, heading: 306, odometer: 97101.8, power: 8, range: 208, shift_state: "D", soc: 67, speed: 0, time: ~U[2023-04-01 06:55:20.491Z]}
docker-teslamate-1  | 2023-04-01 06:55:22.386 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 07:07:25.062 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (178.216 ms)
docker-teslamate-1  | 2023-04-01 07:07:25.549 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (485.553 ms)
docker-teslamate-1  | 2023-04-01 07:07:25.559 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 245, latitude: 51.354593, longitude: 3.299792, native_latitude: 51.354593, native_location_supported: 1, native_longitude: 3.299792, native_type: "wgs", power: 3, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>587}
docker-teslamate-1  | 2023-04-01 07:07:25.559 car_id=2 [info] Driving / Ended / 6 km – 12 min
docker-teslamate-1  | 2023-04-01 07:07:25.559 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 07:07:56.163 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 250, latitude: 51.354588, longitude: 3.299775, native_latitude: 51.354588, native_location_supported: 1, native_longitude: 3.299775, native_type: "wgs", power: 4, shift_state: "R", speed: 0, timestamp:<PHONE_NUMBER>170}
docker-teslamate-1  | 2023-04-01 07:07:56.163 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 07:08:08.762 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 249, latitude: 51.354591, longitude: 3.299789, native_latitude: 51.354591, native_location_supported: 1, native_longitude: 3.299789, native_type: "wgs", power: 3, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>431}
docker-teslamate-1  | 2023-04-01 07:08:08.762 car_id=2 [info] Driving / Ended / 0 km – 0 min
docker-teslamate-1  | 2023-04-01 07:08:08.762 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 07:08:48.104 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9076.843 ms)
docker-teslamate-1  | 2023-04-01 07:08:48.105 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 07:08:48.105 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 07:11:32.344 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:14:15.992 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:19:23.947 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:21:11.226 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:24:34.322 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9131.184 ms)
docker-teslamate-1  | 2023-04-01 07:24:34.322 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 07:24:34.322 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 07:26:31.110 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:30:55.687 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1493025668492014/vehicle_data -> 408 (9089.695 ms)
docker-teslamate-1  | 2023-04-01 07:30:55.687 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 07:30:55.688 car_id=1 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 07:32:00.176 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:35:11.992 [info] Refreshing access token ...
docker-teslamate-1  | 2023-04-01 07:35:12.314 [info] POST https://auth.tesla.com/oauth2/v3/token -> 200 (321.922 ms)
docker-teslamate-1  | 2023-04-01 07:35:12.319 [info] Scheduling token refresh in 6 h
docker-teslamate-1  | 2023-04-01 07:36:32.518 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:38:26.118 [warning] Disconnected! Connection Error: :timeout | 2
docker-teslamate-1  | 2023-04-01 07:39:56.761 car_id=2 [warning] Received stale stream data: %TeslaApi.Stream.Data{elevation: 5, est_heading: 249, est_lat: 51.354591, est_lng: 3.299789, est_range: 120, heading: 249, odometer: 97105.3, power: 2, range: 197, shift_state: "P", soc: 63, speed: nil, time: ~U[2023-04-01 07:39:54.700Z]}
docker-teslamate-1  | 2023-04-01 07:45:17.906 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:51:24.311 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 07:57:20.193 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 08:03:48.730 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 08:06:06.918 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 08:06:06.918 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 08:06:06.918 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 08:06:06.926 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 08:19:21.376 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 08:19:21.376 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 08:19:21.376 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 08:19:21.382 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 08:27:09.881 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 248, latitude: 51.354589, longitude: 3.299788, native_latitude: 51.354589, native_location_supported: 1, native_longitude: 3.299788, native_type: "wgs", power: 4, shift_state: "D", speed: 0, timestamp:<PHONE_NUMBER>802}
docker-teslamate-1  | 2023-04-01 08:27:09.881 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 08:32:28.571 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9118.484 ms)
docker-teslamate-1  | 2023-04-01 08:32:28.571 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 08:32:28.571 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 08:32:47.660 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9087.890 ms)
docker-teslamate-1  | 2023-04-01 08:32:47.661 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 08:32:47.661 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 08:33:06.746 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/1492931810975501/vehicle_data -> 408 (9083.453 ms)
docker-teslamate-1  | 2023-04-01 08:33:06.746 [warning] TeslaApi.Error / %{"error" => "{\"error\": \"timeout\"}", "error_description" => "", "response" => nil}
docker-teslamate-1  | 2023-04-01 08:33:06.746 car_id=2 [error] Error / :unknown
docker-teslamate-1  | 2023-04-01 09:02:19.374 car_id=1 [warning] Received stale stream data: %TeslaApi.Stream.Data{elevation: 5, est_heading: 56, est_lat: 50.983556, est_lng: 3.64925, est_range: 151, heading: 56, odometer: 18229.2, power: 0, range: 184, shift_state: nil, soc: 62, speed: nil, time: ~U[2023-04-01 09:02:16.519Z]}
docker-teslamate-1  | 2023-04-01 09:02:50.693 [warning] MQTT connection has been dropped
docker-teslamate-1  | 2023-04-01 09:02:51.224 [error] Postgrex.Protocol (#PID<0.2388.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
docker-teslamate-1  | 2023-04-01 09:02:51.226 [error] Postgrex.Protocol (#PID<0.2392.0>) disconnected: ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  | 2023-04-01 09:02:51.227 [error] GenStateMachine :"2" terminating
docker-teslamate-1  | ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/schema.ex:756: Ecto.Repo.Schema.apply/4
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/schema.ex:369: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
docker-teslamate-1  |     (teslamate 1.27.2) lib/teslamate/vehicles/vehicle.ex:447: TeslaMate.Vehicles.Vehicle.handle_event/4
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) gen_statem.erl:1205: :gen_statem.loop_state_callback/11
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
docker-teslamate-1  | 2023-04-01 09:02:51.379 [error] GenStateMachine :"2" terminating
docker-teslamate-1  | ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:151: Ecto.Repo.Queryable.one/3
docker-teslamate-1  |     (teslamate 1.27.2) lib/teslamate/vehicles/vehicle.ex:157: TeslaMate.Vehicles.Vehicle.init/1
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) gen_statem.erl:812: :gen_statem.init_it/6
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
docker-teslamate-1  | 2023-04-01 09:02:51.381 [error] GenStateMachine :"2" terminating
docker-teslamate-1  | ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:151: Ecto.Repo.Queryable.one/3
docker-teslamate-1  |     (teslamate 1.27.2) lib/teslamate/vehicles/vehicle.ex:157: TeslaMate.Vehicles.Vehicle.init/1
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) gen_statem.erl:812: :gen_statem.init_it/6
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
docker-teslamate-1  | 2023-04-01 09:02:51.386 [error] Postgrex.Protocol (#PID<0.2389.0>) disconnected: ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  | 2023-04-01 09:02:51.387 [error] Postgrex.Protocol (#PID<0.2387.0>) disconnected: ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  | 2023-04-01 09:02:51.388 [error] GenStateMachine :"2" terminating
docker-teslamate-1  | ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:151: Ecto.Repo.Queryable.one/3
docker-teslamate-1  |     (teslamate 1.27.2) lib/teslamate/vehicles/vehicle.ex:157: TeslaMate.Vehicles.Vehicle.init/1
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) gen_statem.erl:812: :gen_statem.init_it/6
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
docker-teslamate-1  | 2023-04-01 09:02:51.389 [error] Postgrex.Protocol (#PID<0.2382.0>) disconnected: ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  | 2023-04-01 09:02:51.392 [error] GenStateMachine :"2" terminating
docker-teslamate-1  | ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:913: Ecto.Adapters.SQL.raise_sql_call_error/1
docker-teslamate-1  |     (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
docker-teslamate-1  |     (ecto 3.9.4) lib/ecto/repo/queryable.ex:151: Ecto.Repo.Queryable.one/3
docker-teslamate-1  |     (teslamate 1.27.2) lib/teslamate/vehicles/vehicle.ex:157: TeslaMate.Vehicles.Vehicle.init/1
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) gen_statem.erl:812: :gen_statem.init_it/6
docker-teslamate-1  |     (stdlib <IP_ADDRESS>) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
docker-teslamate-1  | 2023-04-01 09:02:51.398 [error] Postgrex.Protocol (#PID<0.2381.0>) disconnected: ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  | 2023-04-01 09:02:51.398 [error] Postgrex.Protocol (#PID<0.2391.0>) disconnected: ** (DBConnection.ConnectionError) tcp recv (idle): closed
docker-teslamate-1  | 2023-04-01 09:02:51.531 [error] Postgrex.Protocol (#PID<0.2389.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.533 [error] Postgrex.Protocol (#PID<0.2391.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.534 [error] Postgrex.Protocol (#PID<0.2387.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.535 [error] Postgrex.Protocol (#PID<0.2381.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.540 [error] Postgrex.Protocol (#PID<0.2388.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.541 [error] Postgrex.Protocol (#PID<0.2392.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.542 [error] Postgrex.Protocol (#PID<0.2382.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is shutting down
docker-teslamate-1  | 2023-04-01 09:02:51.872 [info] Starting logger for 'Heidi's Y'
docker-teslamate-1  | 2023-04-01 09:02:51.873 [error] Postgrex.Protocol (#PID<0.2385.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
docker-teslamate-1  | 2023-04-01 09:02:51.876 [error] Postgrex.Protocol #PID<0.2385.0> could not cancel backend: tcp connect: connection refused - :econnrefused
docker-teslamate-1  | 2023-04-01 09:02:51.878 [error] Postgrex.Protocol (#PID<0.2385.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (database:5432): connection refused - :econnrefused
docker-teslamate-1  | 2023-04-01 09:02:52.119 [error] Postgrex.Protocol (#PID<0.2390.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
docker-teslamate-1  | 2023-04-01 09:02:52.119 [error] Postgrex.Protocol (#PID<0.2386.0>) disconnected: ** (Postgrex.Error) FATAL 57P01 (admin_shutdown) terminating connection due to administrator command
docker-teslamate-1  | 2023-04-01 09:02:52.241 [info] Starting logger for 'Heidi's Y'
docker-teslamate-1  | 2023-04-01 09:02:53.358 [error] Postgrex.Protocol (#PID<0.2391.0>) failed to connect: ** (Postgrex.Error) FATAL 57P03 (cannot_connect_now) the database system is starting up
docker-teslamate-1  | 2023-04-01 09:02:53.657 [info] Starting logger for 'TMCO.be'
docker-teslamate-1  | 2023-04-01 09:02:54.047 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 09:02:54.081 car_id=1 [info] Start / :online
docker-teslamate-1  | 2023-04-01 09:02:54.149 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 09:02:54.150 [info] Start of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 150, latitude: 51.099681, longitude: 3.327793, native_latitude: 51.099681, native_location_supported: 1, native_longitude: 3.327793, native_type: "wgs", power: 3, shift_state: "D", speed: 43, timestamp:<PHONE_NUMBER>888}
docker-teslamate-1  | 2023-04-01 09:02:54.150 car_id=2 [info] Driving / Start
docker-teslamate-1  | 2023-04-01 09:02:54.157 car_id=1 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 09:02:55.201 [error] Postgrex.Protocol #PID<0.2390.0> could not cancel backend: tcp connect: connection refused - :econnrefused
docker-teslamate-1  | 2023-04-01 09:02:55.201 [error] Postgrex.Protocol #PID<0.2386.0> could not cancel backend: tcp connect: connection refused - :econnrefused
docker-teslamate-1  | 2023-04-01 09:02:55.728 [warning] MQTT publishing failed: :timeout
docker-teslamate-1  | 2023-04-01 09:02:56.028 [info] MQTT connection has been established
docker-teslamate-1  | 2023-04-01 09:08:05.168 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (212.012 ms)
docker-teslamate-1  | 2023-04-01 09:08:05.659 [info] GET https://nominatim.openstreetmap.org/reverse -> 200 (486.520 ms)
docker-teslamate-1  | 2023-04-01 09:08:05.668 [info] End of drive initiated by: %TeslaApi.Vehicle.State.Drive{gps_as_of:<PHONE_NUMBER>, heading: 217, latitude: 51.096429, longitude: 3.375199, native_latitude: 51.096429, native_location_supported: 1, native_longitude: 3.375199, native_type: "wgs", power: 2, shift_state: "P", speed: 0, timestamp:<PHONE_NUMBER>633}
docker-teslamate-1  | 2023-04-01 09:08:05.668 car_id=2 [info] Driving / Ended / 5 km – 5 min
docker-teslamate-1  | 2023-04-01 09:08:05.669 car_id=2 [info] Start / :online
docker-teslamate-1  | 2023-04-01 09:10:09.922 car_id=2 [info] Received stream data: :inactive
docker-teslamate-1  | 2023-04-01 09:11:54.361 car_id=2 [info] Suspending logging
docker-teslamate-1  | 2023-04-01 09:15:50.036 car_id=2 [info] Fetching vehicle state ...
docker-teslamate-1  | 2023-04-01 09:21:00.274 [info] GET /
docker-teslamate-1  | 2023-04-01 09:21:00.309 [info] Sent 200 in 34ms
docker-teslamate-1  | 2023-04-01 09:21:05.203 [info] GET /settings
docker-teslamate-1  | 2023-04-01 09:21:05.216 [info] Sent 200 in 12ms
docker-teslamate-1  | 2023-04-01 09:21:55.165 [warning] Too many disconnects from streaming API
docker-teslamate-1  | 2023-04-01 09:21:55.165 car_id=2 [info] Creating new connection …
docker-teslamate-1  | 2023-04-01 09:21:55.165 car_id=2 [info] Disconnecting ...
docker-teslamate-1  | 2023-04-01 09:21:55.170 car_id=2 [info] Connecting ...
docker-teslamate-1  | 2023-04-01 09:23:43.387 [error] Vehicle Error: Vehicle is offline

D:\Users\Jan Van Hyfte\OneDrive - TMCO.be\Source\Docker>

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
1.27.2

In other panels is see:

In locations I don't see the selector

Added it via https://github.com/teslamate-org/teslamate/commit/9ca838e431f3405eabdc017e9f660ec4970057c6

Added it via 9ca838e

solved


Support brew install for desktop version.

Hello,
great  applications.
I think it' ll be nicer it support homebrew install . Could you consider adding this part ?

brew install -- cask netnewswire
works on macOS with Homebrew installed


Add overrides for FileSystemUtils

In some orderings, the context's FileSystemUtils was picking up the actual platform instead of the fake platform.  See https://cirrus-ci.com/task/4530993889542144?command=main#L2934

For #47963

Going to land this to kick infra - the tree is actually green right nwo for master, but dev is red.


Document component reference rules and update component references

Rules:
Component names in titles should be title case e.g. Form Field, Salt Provider
Component names in technical documentation should be PascalCase e.g. FormField, SaltProvider

Question for the content team: Would it make sense to also require technical documentation to format the PascalCase component names in a monospace font (i.e. wrap them in backticks in markdown or <code> element in HTML). E.g. FormField, SaltProvider? Might help further differentiate the different usages.


Place the current zalando.github.io content in ost/projects and restyle

We need to retain the content at zalando.github.io but make it the project subfolder of the new website. Should be restyled using dress code.

Observations / Notes:

This is a private repo https://github.com/zalando/zalando.github.io
The content into zalando.github.io comes from this repository https://github.com/zalando-incubator/zalando.github.io-dev

Users are encouraged to open Pull Requests into the above repository

The following lines from this file take care of pushing the compiled web application into the main repository.

Next steps:

[ ] Tweak the gulp configuration file

Add a hook into this file to be able to push the compiled web application into the /projects folder of this OST repository.


Add Chinese translations for the docs: zh

Generate a new translation directory for Chinese translations.

Awesome, thank you @RunningIkkyu ! :rocket: :speech_balloon:


Handle Confluent Cloud tags

Ns4Kafka should provide the ability to tag resources (topics and schemas) with Confluent Cloud tags: https://docs.confluent.io/cloud/current/api.html#tag/Types-(v1)/operation/createTagDefs.
Possible implementation
Users
Users should be able to tag their resources (schemas and topics) when deployed on Confluent Cloud only. The main solution is adding a new field in the resource metadata that contains all the tags split by a comma:
---
apiVersion: v1
kind: Topic
metadata:
  name: myPrefix.topic
  tags: tag1,tag2,tag3
spec:
...

The list of possible tags for a namespace should be defined by admins, and validated at namespace level:
---
apiVersion: v1
kind: Namespace
metadata:
  name: myNamespace
  cluster: myCluster
  labels:
    contacts<EMAIL_ADDRESS>spec:
  topicValidator:
  connectValidator:
  tagValidator:
      tags:
        validation-type: ValidString
        validStrings:
          - tag1
          - tag2
          - tag3

A dedicated executor for tags might need to be implemented to handle both schema tags and topic tags.
Admin
Tags might need to be declared in the Confluent Cloud before getting attached to a resource. In this case, 3 possible solutions:

Tags might be created beforehand outside of Ns4Kafka (like Confluent Cloud service accounts).
Tags might be created by admins from Ns4Kafka by running such kind of command: kafkactl apply -f tag.yml. In this case, a new admin resource might be created:

---
apiVersion: v1
kind: Tag
metadata:
  name: tag1
spec:
  description: This is a wondeful tag

This option may not make sens in Ns4Kafka as it is unrelated to namespaces at this point.

Tags are created in Confluent Cloud at the first time a user links it to one of its resource.

The validation at namespace level could be omitted. All namespaces should have the right to use all the CCloud tags.
A remote validation against Schema Registry API during topic/schema deployment to check that the defined tags are compliant should be performed

https://github.com/michelin/ns4kafka/pull/321


added support for the Swedish locale

This date parsing for Swedish (sv_se) seems to work fine for my fairly extensive message archive.
(Also, thanks for this project! 👌)

Awesome, thanks! :+1:


Have focusTrap action focused on a specific element using tabIndex

Describe the feature in detail (code, mocks, or screenshots encouraged)
After discussing this on discord with @endigo9740 :
Let users implement their own tabindex attributes, so they retain full control and encourage best practices
By default, focusTrap should default to the first focusable element in the array
If specified, focusTrap should target the tabindex supplied by the user (I'll discuss how we pass this below)
Update modals/dialogs to accept an optional tabindex, which is passed to the embedded version of focusTrap. Which triggers the above result.
Per the interface for providing the tabindex to the focusTrap, we're unfortunately a bit limited due to the current implementation accepting only a single boolean value:
<form use:focusTrap={someBoolValue}>
First instinct is to do something like this - however this would be a breaking change and is not possible until the next major release:
<form use:focusTrap={{state: someBoolValue, tabindex: 2}}>
But what we'll likely need to do is use a data attribute as a temporary solution. This is optional and non-breaking:
<form use:focusTrap={someBoolValue} data-tabindex={2}>
I'm demonstrating tabindex as a number here, but string might be more appropriate.
We should likely keep the existing logic around a default selection (first focusable). This keeps parity with the existing functionality (prevents a breaking change again), as well as provides a nice fallback if users don't specify tabindex values in their content as expected.
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response

Limiting the data-tabindex to only form elements may not be the best solution, btw.
tabindex attributes can be added to any HTMLElement:
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/tabindex

And after reading a bit more, having tabIndexes > 0 is not recommended (even if they use examples > 0 in the doc)

Hmm, that does complicate things a bit. In that case, I'd suggest using data attributes:
<button data-tabindex="0">...</button>
<button data-tabindex="1">...</button>

...

This provides a similar interface, but still gives the focusTrap a specific target that's easily queried.

Wouldn't it be easier to have only one data attribute ?
Because if we don't use tabindex, then there is no order to take into consideration, only one element to focus on:
<button>...</button>
<button data-focus="true">...</button>

...

Actually yes, that seems much better. Good call!

I like the simplicity of that, but my concern would obviously be what if that needs to change. What if a condition is in place that requires you to select element A instead of B.
I'm not sure the specific implementation for ModalSettings yet, but imagine something like this:
function triggerModal(someBool: boolean) {
  const modal: ModalSettings = {
    // ...
    tabindex: someBool ? 0 : 2
  };
  modalStore.trigger(modal);
}

In this case, it might be nice to quickly be able to jump from selecting the data-tabindex="0" or data-tabindex="2" based on the condition here.
Again, this does require some setup ahead of time by the user, but it provides a simpler implementation here. Seems more flexible, right?

To me, it's the same. We can put some logic inside the component template, or in the ModalSettings :-)
I'm just concerned about the "tabindex" property in case of ModalSettings.
I would rather use this:
function triggerModal(someBool: boolean) {
  const modal: ModalSettings = {
    // ...
    focus: someBool ? id1 : 'd2
  };
  modalStore.trigger(modal);
}

with id1 and id2 being just elementId. This way we don't mess with tabIndexes > 0 :-)

But I prefer the data-focus="true"; I don't see how we can't condition this:
<button>...</button>
<button data-focus="{condition}">...</button>

...

Another detail, ModalSettings has nothing to do with focusTrap action :-)
If we narrow the changes to focusTrap only, it will adapt to other / future utilities that will implement focusTrap !

Typically the goal of your template markup is to provide a definition of the visual and non-visual data (read: attributes) for your component HTML. While you certain can put more of your logic in the template, the questions is if this is the most pragmatic solution. In this case I think most folks would prefer the logic be handled in the Javascript, rather than in the template itself. Keep the template slim and "dumb". Let Javascript do it's job.
I'd also encourage you to think beyond a simple boolean example here. Imagine scenarios that have maybe 5-10 items that could dynamically be selected. The requirements for condition within the template grows with your data-focus method, but the upfront requirements are very simple with the data-tabindex approach.
data-focus approach:
<button data-focus={focusedCond === 1}>...</button>
<button data-focus={focusedCond === 2}>...</button>
<button data-focus={focusedCond === 3}>...</button>
<button data-focus={focusedCond === 4}>...</button>
<button data-focus={focusedCond === 5}>...</button>

data-tabindex approach:
<button data-tabindex="0">...</button>
<button data-tabindex="1">...</button>
<button data-tabindex="2">...</button>
<button data-tabindex="3">...</button>
<button data-tabindex="4">...</button>

Another detail, ModalSettings has nothing to do with focusTrap action :-)
If we narrow the changes to focusTrap only, it will adapt to other / future utilities that will implement focusTrap !

Correct, the initial implementation is modifying the focusTrap - but the end goal is to allow this new forcusTrap feature to work with modals/drawers/etc. We should not ignore this goal when designing this feature. That would be very short sighted.

Makes sense. I'll see how to be smart about this 😁

For now, I'm passing ModalSettings.tabIndex to focusTrap, so I had to change:
function focusTrap(node: HTMLElement), enabled: boolean) {}

to
type FocusTrapSettings = { enabled: boolean; tabIndex?: number };
function focusTrap(node: HTMLElement, focusTrapSettings: FocusTrapSettings) {}

I understand it would be a major change and you don't want that, correct ?

I understand it would be a major change and you don't want that, correct ?

Correct, any change that's not backwards compatible with the current implementation would be considered "breaking". We cannot provide breaking changes in minor updates to the library. We would have many upset users if we did :)
I would actually be fine if you want to hold off on modifications to the Modal and Drawer right now. Keep it in mind, but let's talk through that next and separately. I'll likely need to dive into the code and refresh how everything is implemented to provide a suggestion for how we should implement. Unfortunately my time is limited today.
Per the changes to the focusTrap, we need to keep:
function focusTrap(node: HTMLElement), enabled: boolean) {}

Then use the node to query for data-tabindex items within it. We do something similar with the Table of Contents action, which scans for header elements:
https://github.com/skeletonlabs/skeleton/blob/master/packages/skeleton/src/lib/utilities/TableOfContents/crawler.ts#L35
Something like:
const focusableElems = node.querySelectorAll('[data-tabindex]);

You then have an array of elements that use this data attribute, and should be able to locate which matches the desired index value - then set focus on that.

In the future, we can refactor the focusTrap to our standard args format like so:
type FocusTrapArgs= { enabled: boolean; tabIndex?: number };

function focusTrap(node: HTMLElement, args: FocusTrapArgs) {}

In the future, before our next major release, we can refactor the focusTrap to our standard args format like so:
type FocusTrapArgs= { enabled: boolean; tabIndex?: number };

function focusTrap(node: HTMLElement, args: FocusTrapArgs) {}

Actually, I'm alreay on it with this:
type FocusTrapArgs = boolean | { enabled: boolean; tabIndex?: number };

function focusTrap(node: HTMLElement, args: FocusTrapArgs) {}

I took the idea in the Clipboard action ^^
So it doesn't break anything and nobody will be upset :-)

I was considering something like this. I might still recommend we put a // TODO: comment or something similar to clue us into the fact this may need a minor refactor in the future. But I think that's a good happy medium for now. Good call!


feat: mvp cds-navigation

adds default layout (vertical)
custom expand/collapse icons for root navigation and navigation groups
navigation groups
arrow and home and end key navigation + a11y enhancements

Signed-off-by: Matt Hippely<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?
MVP For CdsNavigation compoent.

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?
Core does not have navigation.

Issue Number: N/A
What is the new behavior?
Core has a navigation with a default (vertical) layout.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@hippee-lee  Can we change the commit message to feat(core:navigation): mvp cds-navigation?

@hippee-lee Can we change the commit message to feat(core:navigation): mvp cds-navigation?

@bbogdanov - I will amend the commit when I squash.


[1.12] Dynamite doesn't explode with Intended Radius

Minecraft version & Mod Version: 1,12 (All The Mods 3 Modpack)
Single player or Server: Singleplayer
Describe problem (what you were doing / what happened):
Using Dynamite VI in creative mode.  Doesn't explode with intended radius UNLESS player is in close proximity to explosion center.  GIF details the issue.

What version of  cyclic is in the modpack? This sounds familiar so i think maybe i fixed it? ill try it out in my world
Also were you in overworld in that gif or a different dimension? That should not affect anything but maybe

Version 1.6.0 is in the pack, and this was in an RFTools Dimensions world.  It may have something to do with a dropped entity bug that I noticed, where any thrown/dropped entities keep teleporting (you can notice it in the above GIF with the dirt blocks.)  If this is the case, it may not be Cyclic's problem.

I wonder if this is related to tick speed delay / lag in the game.  It seems like its exploding before it hits the ground, so if the ground is at 60, its exploding at 64, because of some sort of delay or desync.
I downloaded the ATM3 modpack and i didnt see this happening, at least not in the overworld, i didnt try RF dimensions.

Closed due to no replication, no activity, and no cause found within this mod


add basic systemd service unit example

adds a simple systemd unit example for Linux so that librespot can be started automatically on boot

Thanks


Function parameters accept type inference with null default value

Godot version
3.5.2-rc2
System information
Manjaro Linux (6.0.2-2-MANJARO x86_64) Vulkan, GTX 2060 SUPER with proprietary drivers
Issue description
Godot 3 throws an error when doing var a := null but fails to throw it when doing func foo( a:= null) and causes the function to accept args of any type and convert them to null.
This is fixed in Godot 4
Steps to reproduce
Run a scene with the following code
extends Node

func foo ( a:= null):
	prints(a, typeof(a))

func _ready():
	foo(1)  # no error, prints Null
	foo("bar") # no error, prints Null
	foo([2,3,3]) # no error, prints Null
	foo(Sprite.new()) # no error, prints Null

This throws a parser error in Godot 4.0-rc1 but is allowed in Godot 3.5.2-rc2. Furthermore, you can pass arguments of any type and they will all be converted to null without any errors or warnings.
Minimal reproduction project
InferredNullError.zip

Can confirm this bug is still present in 3.5.2.stable.official


Update aws-core, http-client-spi, ... to 2.17.145

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

from 2.17.104 to 2.17.145.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #84.


swap TinkerGraph for OverflowDB, simplify codegen

This is green and using a released version of overflowdb now. I'll prepare the downstream PRs and will merge together.