Revert some editorconfig settings [skip ci]

The Issue
In

#4712

@gilbertsoft made some very reasonable improvements to the .editorconfig, but they've been causing some trouble in a number of places.

Embedded yaml in codeblocks in yaml gets 4-space (and ugly) indentation
Lots of failures are getting shown with existing stuff that gets edited and the editor magically removes trailing spaces.

How This PR Solves The Issue

Don't force the 4-space indentation
Stop the trailing space requirements

I haven’t had responded to this question yet because I think the best answer is a diligent one—not adopting or reverting the change but testing it carefully:

Taking inventory of the file types we have and how they’re formatted, making rules that are as specific as possible. Probably specifying four spaces for Markdown and PHP, and two spaces for YAML and JavaScript and JSON—but the answer should include everything we know about.
Applying the rule set in a commit, instead of seeing what happens as people submit PRs over a long period of time.

Reverting this change gets rid of the good it does skipping whitespace issues in PRs. Applying it creates new issues. I haven’t had time to take a careful run at it yet.

We can keep the trim_trailing_whitespace if we do a PR to fix all existing markdown files. Or maybe all files.

I swapped <br> elements for intentional line breaks and attempted to be more specific with file types over here, but the settings seem to be only spontaneously applied in VS Code.
I uninstalled Prettier to rule out interference, and while trailing spaces and empty lines are automatically cleaned up on save I still have a few problems:

Four-space YAML indentation is not fixed (to two spaces) in fenced code blocks.
Shell scripts (ending in .sh) can have a mixture of tabs, spaces, and 1-, 2-, 3-, or 4-space indentations—sometimes in the same file—without being fixed on save.
Nothing changes when I save docs/content/assets/extra.css.
Saving .go files automatically adds line breaks between some lists if imports, and I’m not sure if that’s a thing we want.

In same cases above, I can use SHIFT + ⌘ + P and choose “Reformat lines” to get the desired effect. Not always, though.
I installed and disabled the EditorConfig VS Code extension (even though editorconfig.org says no plugin is necessary), and tried setting it as my default formatter instead of none. No real change.
I’d like to apply the rules to all the files in the project to quantify the impact it has, but I’m struggling to apply the rules to individual files as a precursor.
Maybe my setup’s just a dumpster fire. Anybody else get consistent results with an updated config?

I suspect that we can apply settings to all markdown files with
markdownlint --fix <file> -c $ProjectFileDir$/.markdownlint.jsonc
find docs *.md -name "*.md" -exec markdownlint --fix {} \;

I've been intending to try it and add results to this PR.

That exact recipe doesn't work.

Ah, eclint
eclint fix

There are several editorconfig actions, all seem to be very poorly maintained. The one I tried doesn't have any option to limit the files or file types that it acts on.

Here are the 12,000 lines of errors from eclint check with our current config:
https://gist.github.com/rfay/dfc23c73b4c95c35f3eb662f5f80c57c
The problem with this is that editors that use it, when the file is visited, change more than the planned change, which makes PRs ugly and hard to comprehend.

There are so many, many unintended consequences of .editorconfig.
For example, this one:

cmd/ddev/cmd/commands_test.go
436:02 ❌ invalid indent style: space, expected: tab
(EditorConfig indent_style https://goo.gl/8Qkrbr)

The code it's complaining about is json embedded in golang:
	packageJSON := `
	{
	  "name": "junk",
	  "version": "1.0.0",
	  "description": "",
	  "main": "index.js",
	  "devDependencies": {},
	  "scripts": {
		"test": "echo \"Error: no test specified\" && exit 1"
	  },
	  "author": "",
	  "license": "ISC"
	}

It would be incorrect if indented with tabs.

This now only removes the indentation restriction, because mixed code doesn't work well with it (like yaml in markdown).
All of the markdown files have had all of their trailing spaces removed in this PR as well.
I'm not sure I like editorconfig anywhere (except for new code) because of the unintended edits some IDEs do as a result.

I don’t know of a great way to solve code consistency without sharing organization-wide IDE settings, repository configs, and linting tools that go all in on encouraging or enforcing a specific style.
Please give me a poke if you merge this so I can fix any intentional line breaks that get stripped out.


0xa727c953ffe3e461573736fde77d20cfdce9fca3

Related Safe Addresses
0xd380e5cfc216401ad47ad95ca7c2e09adf75d64e
0xdee200a49174356c6f471c1b1d2451bb634e6ebc
0x57a5d781ef981edac691a1435e35bb58bdc5fd02
0x6f94913b5799a658cf07976a82d0b91a85f1f41b
0xd8dcbc5bbca4ad21bb79dc3120a99741535654e6
0x14f7ed97b604cad78d5ec90d40d28b5bad6412ab
0x3e2c53b0166dc1af3092bd4b12fe65ffc3b3b71b
0xa5c7a5b0d04c9845bd1764529d17ebe7a2adcc18
0xf894fea045eccb2927e2e0cb15c12debee9f2be8
0x19b94b532c1f569120aded77237ea49e30e1e260
0xa963a46ef8d90cba23347def96632417beaf72a2
0x33e626727b9ecf64e09f600a1e0f5adde266a0df
0x709e4268c5b3240dae7b55174a6c163402539ff1
0x8e6440070409a9df5e14301c7440107990ae9b3d
0xfe4202c3f6de22068de5f3b463ae386dccab3e2a
0xc0b51d97c79132a1acd976ae3766c481c49630de
Reasoning
These safe accounts are all created by 0xa727c953ffe3e461573736fde77d20cfdce9fca3
Methodology
Execute at luabase.
with target as (
select *
from url('https://raw.githubusercontent.com/safe-global/safe-user-allocation-reports/main/safe_user_allocations_reworked.csv', CSVWithNames)
), transactions as (
select t1.*
from ethereum.transactions t1
join target t2
on t1.to_address = t2.safe_address
)
select distinct to_address
from transactions
where from_address = '0xa727c953ffe3e461573736fde77d20cfdce9fca3'

Please elaborate on why these are safes created for airdrop farming. Just the fact that 1 addresses created all of them doesn't qualify.
If e.g. a wallet uses a relayer to create Safes, the relayer would be the account that created all user Safes which is not airdrop farming per se.

We haven't received any further information on this ticket and therefore deemed this submission invalid.
Unfortunately just the pure fact that Safes...

were created by the same address
have the same owner
conducted the same transactions
received assets from the same address

... is not enough reasoning for a valid submission, as there are legit user behaviour leading to such as well (relayer, scripts, power users, exchanges)
This submission didn't provide sufficient indicators to convince the team that there is some targeted airdrop farming behind the provided addresses. As per the rules, when in doubt we will default in favor of the airdrop recipients in order to not risk any false positives when sorting out airdrop hunters.


So all developers may use page titles consistently, develop a title & title heuristics

Find best practices and write a small post about our decisions for how we write great page titles
This is the thing between the  tag, not a page element.

Along with the , make recommendations for FAVICON.ICO usage, title/crawl/bookmark and other meta data elements.

Title Tag Best Practices.docx

@jdkunesh  I attached the short article on the title best practices. Please review and let me know if this is what you were referring to.

Hi @alaeder16 this is awesome. Given this set of heuristics, what would a few recommendations for titles be for the City?
City of Chicago (no title)
[ page title ] - City of Chicago
[ keyword1, keyword2 ] - City of Chicago
or similar?

@jdkunesh I would say  [Page name] - [ Category] | [City of Chicago]. Where Page name should be different from the page title and consist of keyword 1 and 2. For example:
Dog Registration | Animal Care and Control | City of Chicago
Currently it is City of Chicago :: Dog Registration

@alaeder16 @mario-duran Please make it so, and let's include examples in:

[ ] stickersheet
[ ] prototype
[ ] codebase

@mario-duran can you make sure there's a good example in the design system site template for this page title? When done please close. Thanks!


New version: DiffEqProblemLibrary v4.14.0

Registering package: DiffEqProblemLibrary
Repository: https://github.com/SciML/DiffEqProblemLibrary.jl
Created by: @ChrisRackauckas
Version: v4.14.0
Commit: 4e1ded0c530c015e2b1aa7904957584857160b24
Reviewed by: @ChrisRackauckas
Reference: https://github.com/SciML/DiffEqProblemLibrary.jl/issues/47#issuecomment-986035338
Description: A library of premade problems for examples and testing differential equation solvers and other SciML scientific machine learning tools

@ChrisRackauckas please see the message above.  Once you fix the automerge issues you can register again the new revision without changing the version number and this pull request will be automatically updated.
[noblock]


[Parse] Fix end location of dummy top level code for code completion

Fix ASTVerifier error for end location of IfConfigDecl.
Previously, for:
#if CONDITION
// something
<COMPLETE>

End location of the dummy body of TopLevelCodeDecl was at the eof, but the end loc of the IfConfigDecl was at the code-completion token. That caused the ASTVerifier error "invalid IfConfigStmt end location".
https://bugs.swift.org/browse/SR-2364
rdar://problem/41217187

@swift-ci Please smoke test


[Improvement] Version manange for H2 database like MySQL

What would you like to be improved?
DDL and table definition have used version management in the MySQL database, H2 database should also add it.

How should we improve?
Change file schema-h2.sql to schema-0.6.0-mysql.sql and other necessary changes.

@yuqi1129 We will support the h2 database in version 0.6.0. I think we only needs to change the file schema-h2.sql to schema-0.6.0-mysql.sql, and there's no need for other upgrade operations.

I recall that you used the procedure to insert some data to MySQL. Is it not necessary for the H2 database?

@yuqi1129 We use procedure to initialize data in MySQL because there is already some existing metalakes in MySQL.
However, h2 only started supporting in version 0.6.0, there is no existing metalake in the database, so there is no need for initialization.

OK, please go ahead.

@lw-yang
Please refer to Apache Hive's handling of schema upgrades for derby.
https://github.com/apache/hive/tree/branch-3/metastore/scripts/upgrade/derby


After update to 5.0 cached dependencies are built/downloaded again

Before the upgrade to 5.0 nix-env -iA tests was a no-op because of the cache previously created in https://github.com/PostgREST/postgrest/actions/runs/7612462322/job/20730136624, after the upgrade it isn't anymore — https://github.com/PostgREST/postgrest/actions/runs/7614272320/job/20736483790#step:3:112.
Note that tar error messages are gone too. Does it mean the cache is unpacked somewhere else?

@develop7, sorry for a late response.

Note that tar error messages are gone too.

I asked tar to --skip-old-files. So, it doesn't try to overwrite existing files and doesn't print errors. I wonder if this approach swallows some important errors.
https://github.com/PostgREST/postgrest/actions/runs/7614272320/job/20736483790#step:3:78

Does it mean the cache is unpacked somewhere else?

As I've written in the README, please, try to run https://github.com/mxschmitt/action-tmate right after the cache-nix-action step and inspect the Nix store.

@develop7, I'll appreciate if you provide the steps to reproduce this behavior in a fork of postgrest.

Okay, I see this problem in workflows here.
Apparently, saving a cache works incorrectly.
#879 builds two derivations and saves a cache.
https://github.com/nix-community/cache-nix-action/actions/runs/8220989301/job/22480792618#step:6:13
 these 2 derivations will be built:
  /nix/store/iil2zlkjadz68ihx4ccl85rv6798idkq-install.drv
  /nix/store/hxsbw2mdgzawjb32r1xn58i4pw5ggvzv-install.drv

#880  restores the cache and builds the same derivations
https://github.com/nix-community/cache-nix-action/actions/runs/8221051128/job/22480932943#step:6:13
these 2 derivations will be built:
  /nix/store/iil2zlkjadz68ihx4ccl85rv6798idkq-install.drv
  /nix/store/hxsbw2mdgzawjb32r1xn58i4pw5ggvzv-install.drv

I re-ran one of the workflows.
https://github.com/nix-community/cache-nix-action/actions/runs/8222779566
In the build job, I restored the cache, installed nix 2.19.3 and connected to the runner via tmate.
I checked the current nix store.
ls /nix/store/ | grep '\-install$'

5qd02ybpcmqmr6vjz2c4bb8ivs8iz8yi-install
lw3yhss8q2fd6fhpc9c58357ba12yhm3-install

I saved the list of nix store paths to a file and sorted it.
ls /nix/store > a.cur
sort a.cur -o a.cur

Next, I ran the install script.
nix run .#install

Nix downloaded nixpkgs and other paths for some reason.
I saved the new list of nix store paths to a file and sorted it.
ls /nix/store > a.new
sort a.new -o a.new

I took a diff of two files and got no changes
diff a.cur a.new

I checked the results of running the write package.
Again, the store didn't change.
So, all necessary paths were in the store at the time of running the packages.
However, they weren't used.

Note that tar error messages are gone too.

I suspect nix keeps info about the store in certain files, and these files are in the cache.
However due to --skip-old-files, these files don't overwrite files that exist after a fresh Nix installation.
Hence, Nix doesn't know about some paths coming from the cache.
I don't know how to "repair" the store, though.
So, for now, I'll remove --skip-old-files and hide the restore logs, as you suggested (link).

In fact, I decided to ignore the existing /nix/store paths completely. Now, there are almost no warnings and cache restoration is slightly faster.

Hey @deemp thank you for looking into the issue; we've phased c-n-a out for our CI setup because caching nix store was actually slower than downloading artifacts from cache.nix.org.

Okay, I'm closing this issue then.

Indeed, the run times with and without caching are similar.

Indeed, the run times with and without caching are similar.

I mean, they could be better on real hardware or with more generous CPU and I/O quota for GA workers but oh well


config.json parameter "apiKey" does not be appear to be used with ollama provider

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windows 11
- Continue: v0.8.27
- IDE: VS Code

Description
We have Nginx doing SSL termination for ollama and forwarding to ollama_proxy_server for authentication, then to ollama.  When trying to use Continue in VS Code with the following config.json block:
{
      "title": "llama3-instruct",
      "provider": "ollama",
      "model": "llama3:instruct",
      "completionOptions": {},
      "apiBase": "https://<my_endpoint>",
      "apiKey": "user1:<my_key>"
},

I get HTTP 403 Unauthorized error from Continue plugin.  When analyzing the Nginx logs I see the requests coming in, but lacking any Bearer tokens:

Nginx logging config:
log_format headers '[$time_local] $remote_addr - $remote_user - $server_name to: $upstream_addr: $request - $http_authorization';
To reproduce
No response
Log output
No response

@troy256 we hadn't been using apiKey for Ollama because it doesn't have built-in auth, but I can see why it would make sense to do that now: https://github.com/continuedev/continue/commit/034754c5f44a25db5a61b6c7ca5a3e8434686f80
The fix will be in the next release, but in the meantime you can use "requestOptions.headers" in config.json like this:
"models": [{
  "title": "Ollama",
  ...
  "requestOptions": { "headers": { "Authorization": "Bearer xxx" } }
  }]


Fix SnapshotLastIndex update error

What changes are proposed in this pull request?
fix #14225
Why are the changes needed?
warn information display error
Does this PR introduce any user facing changes?
No

@ggezer Thanks for reviewing the code, please take a look again.

alluxio-bot, merge this please


changed from 0.7.0 to latest consul version

changed from 0.7.0 to latest consul version
added temporary consul config files to .gitignore

Looks good, thanks Mikhail!


Changing desired temperature

I was able to query the the heating without a problem thanks to your example code.
However I am wondering how I actually change the desired temperature?
Thanks!

https://github.com/Danielhiversen/pyAdax/blob/main/adax/__init__.py#L53

I have found that command aswel digging around in the code but I can't seem to get it to work.
I'm completely new to Python, could you perhaps provide me with an complete example?
Thank you!

https://github.com/home-assistant/core/blob/ce3d774222f62470b9c7f8e25f2194a92cc07b49/homeassistant/components/adax/climate.py#L98

This is code to a HomeAssistant integration?
I was thinking about an example like the one on the page of this repo.

from adax import Adax
import aiohttp
import asyncio
ACCOUNTID = ""  # get your account ID (6 digits) from the Account page in the Adax WiFi app
PASSWORD = "" # create a service password under "Remote Api" in the app
async def main():
async with aiohttp.ClientSession() as session:
heater= Adax(ACCOUNTID, PASSWORD, session)
for room in await heater.get_rooms():
print(room)
asyncio.run(main())

This actually works for me but I would just like to adjust the temp with a similar script.


Fix typo in rm-ocaml-switch send from client

Otherwise the server returns an error (which could be more explicit).

Indeed. Thanks!


[Feature request] Replicate on DB or Key level

Is your feature request related to a problem? Please describe.
In our setup we have different clusters where we can use Multi-master setup to replicate the data. In fact we need only one DB to be replicated but as we know it is not possible.
On the DB we are interested traffic is very low, but when we replicate all the data it generates a significant unneeded(for our just one DB) traffic for replication and also we should have same memory available on our cluster like on the source cluster, to be able to store the data we replicates. Sometimes we get OOM on the node just because it replicates all databases from the primary master which is high loaded.
Describe the solution you'd like
We should be able to specify DB list or DB/Key list to be replicated from the master
Describe alternatives you've considered
Right now we replicate all the data. As a workaround we considered to use different cluster with just one DB and it also involves additional load balancer.

This is interesting, I don't think filtering by key is a good idea, but perhaps by database is something we could look at.

This is interesting, I don't think filtering by key is a good idea, but perhaps by database is something we could look at.

Big +1 to nominating DBs for replication. This greatly simplifies some use cases.
Example: N nodes, local cache per node for ephemeral requests; global cache for small subset of data promoted from local cache.

Salvatore did say this: https://groups.google.com/g/redis-db/c/vS5wX8X4Cjg/m/8ounBXitG4sJ
Ability to exclude keyspaces from being replicated would be a good idea, if it doesn't introduce a lot of moving parts.

I've done an initial implementation in the replication_filter branch.  It works like this:
Add a line to your config file:
replication-db-disable "1 2 3 5-7"
The syntax is a string where you either explicitly list individual database numbers or ranges of databases which should not propagate.  Note that this design may change the branch is for demonstration purposes and to see if we're on the right track with the implementation.

I've done an initial implementation in the replication_filter branch. It works like this:
Add a line to your config file:
replication-db-disable "1 2 3 5-7"
The syntax is a string where you either explicitly list individual database numbers or ranges of databases which should not propagate. Note that this design may change the branch is for demonstration purposes and to see if we're on the right track with the implementation.

Looks reasonable. You might consider adding the inverse as well (replication-db-enable "1") since for many use cases there are more local than global dbs, and specifying explicitly is a good way to prevent accidental replication.

I’m thinking of adding a requirement that all nodes (with active rep) must have the same filter. With this design we’ll still receive queries for these databases and execute those. We just won’t transmit any of our own.

I’m thinking of adding a requirement that all nodes (with active rep) must have the same filter. With this design we’ll still receive queries for these databases and execute those. We just won’t transmit any of our own.

Makes sense.


Examples crash

Fixing issue #129
It seems like the Presolving of SCIP introduces some numerical errors, leading SCIP to hand back an infeasible solution.

I don't think we need the 5000 factor anymore. And the tolerance should now be fine at 1e-6 without presolving?


Unable to Edit Setting of a topic from kafka ui getting 404

Describe the bug (Actual behavior)

Getting 404 Error page when i click on Edit setting button for a topic.
Expected behavior

We should be allowed to update setting for the topic.
I tried to CLI was able to update the setting for the topic.
Set up

App version - V0.6.0
Helm chart version - 0.6.0

Steps to Reproduce

bring up kafka ui and crate a topic and try to edit setting for that topic from ui
1.
Screenshots

Additional context

Hi,
I'm not able to reproduce the issue, vid attached.
Please attach the similar one with steps to reproduce.
https://user-images.githubusercontent.com/1494347/228045696-0238d4f0-9019-415c-9ba5-1823fb39e756.mov

i observed issue us happening only for Kafka version 2.2.1 (MSK cluster) and not for later versions

@nadig-aditya can you do a screen record?

It looks like its because of message format version: https://github.com/provectus/kafka-ui/blob/master/kafka-ui-react-app/src/lib/constants.ts#L31
My kafka 2.1 cluster uses message.format.version: 2.1-IV2
which does not have max.compaction.lag.ms described in: https://github.com/provectus/kafka-ui/blob/master/kafka-ui-react-app/src/lib/constants.ts#L33


On delete we should handle not found as already destroyed if we can

Description
This bug was identified by the terraform smoke test on juju, on the ResourceIntegrationWithMultipleConsumers test.
This is the error:
=== RUN   TestAcc_ResourceIntegrationWithMultipleConsumers
    testing_new.go:90: Error running post-test destroy, there may be dangling resources: exit status 1

        Error: Client Error

        Unable to delete offer, got error: application offer
        "admin/tf-test-integration-2471435562652455485.a" not found
--- FAIL: TestAcc_ResourceIntegrationWithMultipleConsumers (168.39s)

This test seems to be flaky, so might be a timing/sequencing issue between deletes/reads?
Urgency
Casually reporting
Terraform Juju Provider version
0.10.1
Terraform version
v1.7.1
Terraform Configuration(s)
No response
Reproduce / Test
go test -timeout 40m -v -cover ./internal/provider/

Debug/Panic Output
No response
Notes & References
https://github.com/juju/juju/actions/runs/7745564317/job/21121856659?pr=16883

Need a reproducer for this, #446 tried and failed to reproduce.

As we have already discussed offline and on https://github.com/juju/terraform-provider-juju/pull/446, this is an intermittent bug (a race probably) either in the TF provider or juju itself. @hmlanigan had the idea to manually run the github runner somewhere where we have control over the node and run the CI test until it fails, then retrieve logs to investigate. Poke @hpidcock maybe you can help with doing this?

This happens to me all the time, and I am not sure how to get out of that state.
My plan looks like this: https://git.launchpad.net/~yellow/canonical-terraform-plans/+git/canonical-terraform-plans/tree/data-warehouse/modules/data-warehouse/main.tf?h=new-data-warehouse
I am not sure if the fact that I am creating them in a loop has smth to do with it, or the fact that this plan takes quite some time to destroy.


OSSI: Themes page from Link-in-bio page

@Swarnendu0123

Upon clicking view more themes in the end, user should be redirected to themes page.
Design

Carousel type theme cards which can be user customizable too
Tech Stack: React, Vite, TailwindCSS, TypeScript, NextUI/RadixUI libraries for enhanced UI

Follow the issue template. You have not followed the issue template.

You shouldn't mention anyone in the issue's description.

@Swarnendu0123 Made changes and updated.


Add qdrant read vector store implementation

PR https://github.com/grafana/grafana-llm-app/pull/33 can't really be merged until we open-source and package up vectorapi, so this commit adds a qdrant implementation and modifies the provisioning file to use it (and OpenAI) by default, rather than vectorapi.
Still a little hard to test without any way of synchronising data in there, I've been working on https://github.com/grafana/grafana-llm-app/compare/vector-service-qdrant...vector-sync-2?expand=1 to make it a bit easier to get data in and test it but it's not really ideal.

I noticed an issue with the payload marshalling due to the payload being stored in a bunch of nested gRPC structs. Should be fixed by https://github.com/grafana/grafana-llm-app/pull/43/commits/cba49f601c39c52935b0378ea1650a77e13babfc.


L5.5: Add support for in-browser Mailable previews

Since Laravel 5.5 Mailable templates can be previewed in the browser.
However, Dingo API currently throws an obscure error if you try and preview a Mailable:
sha1() expects parameter 1 to be string, object given {"exception":"[object] (ErrorException(code: 0): sha1() expects parameter 1 to be string, object given at /home/vagrant/Code/example/api/vendor/dingo/api/src/Routing/Router.php:566);

This is due to the Router attempting to format the Response content to json (or alternative format based on your API config):
https://github.com/dingo/api/blob/46cffad61942caa094dd876155e503b6819c5095/src/Routing/Router.php#L559
This fix simply sets the Response content to the rendered content of the Mailable instance.
I was unable to add any tests because Dingo API works on the back of the Lumen framework, which doesn't include the Mailable class.
This should obviously only be merged once Dingo API has support for Laravel 5.5.

True. Mailables should be rendered with the default router of the app.

API shouldn't render mail contents.

The request isn't via the API. This package hijacks all requests (including those in web.php) and sends them through Dingo's Router, hence the error.
https://github.com/dingo/api/blob/438f291e953501a4ec079766a3a937d704402fd6/src/Http/Middleware/Request.php#L103
To avoid this you'd have to explicitly call the default router:
// Route::get() would pass through Dingo's Router and throw an error
Illuminate\Routing\Router::get('/mailable', function () {
    return new ExampleMailable(App\User::first());
});

It would be better for Dingo to handle this scenario than require devs to implement hacky workarounds. If preferred the fix could be added to the Router rather than Response.

Ping @thilanga


[Evaluate] Explore the possibility of combining HPA and VPA for efficient scalability of API Server

Story

Explore the possibility of combining both HPA and VPA to efficiently scale API Server

Proposal

To be detailed

Acceptance Criteria

Based on the outcome of the evaluation adopt the proposal to control plane component API Server and to other relevant components

With #890 memory metrics is also included to scale kube-apiserver.
However, this issue #834 is to explore the possibility of using both HPA and VPA for better scalability of components like kube-apiserver

That's with Gaurav, right? Assigning it to him then. I hope that's OK. Maybe we should later move this ticket to this independent/new component.

Closing as HVPA got integrated as of #1421


Menu: why does it block on extension host being ready?

In my grid branch (ben/editor) I have adopted all of the editor toolbar entries to be commands going through the IMenuService mechanisms. For some reason, the actions do not show up until the extension host is ready which looks rather ugly on reload/startup:

I understand that we need to reload the actions once the extension host is ready do collect more actions, but the commands that are contributed out of the box should not wait for the extension host to be ready?
The waiting seems to happen here: https://github.com/Microsoft/vscode/blob/4a0ab3675617f9650ca8f254dd9493fb759d23b1/src/vs/platform/actions/common/menu.ts#L29

The menu registry has been populated by extensions exclusively in the beginning and therefore it waits for package.json-files being read (not extension host process startup) and therefore it has been designed like that. It needs an event on the registry


Add Ecosia to supported search engines

Thank's for this great browser extension, works perfect with Brave Search and DuckDuckGo!
It would be great if the plugin would also support Ecosia: https://www.ecosia.org/
While it's not that popular globally, Europeans and especially Germans really like it.
Thank you!

Will add in future release!

Included in 0.6.0


[BUG] Active window widget broken

The window title widget should be working by default, I assume, but it is not. Komorebi is correctly connected, the window title widget is enabled, and the options are set to their default values in config.yaml. We have no errors being printed by main.py, but some esoteric Qt warnings.
The widget fails to appear entirely, unless we set label_no_window, in which case it will flash briefly on startup before disappearing within 100ms or so.
I've tried running it in both a normal and elevated prompt.
As for reproduction, I'm not really sure since this is just running it exactly as it is on github, with all of the default settings, on Windows 11 and Komorebi 0.14
All of the fonts are installed correctly and every other widget is working as expected.
This is the output:
python src/main.py
Yasb - Yet Another Status Bar
Starting SystemEventListener...
Starting KomorebiEventListener...
Created named pipe yasb-5360e67d-98aa-11ed-a093-001a7dda7115
Waiting for Komorebi to subscribe to named pipe yasb-5360e67d-98aa-11ed-a093-001a7dda7115
Created file watcher for path C:\Users\amnesia\.yasb
Komorebi connected to named pipe: yasb-5360e67d-98aa-11ed-a093-001a7dda7115
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.
QWindowsWindow::setDarkBorderToWindow: Unable to set dark window border.

Hello,
I'm also experiencing this issue as well.

What fixed this for me was setting the the option monitor_exclusive to false within config.yaml:
widgets:
  active_window:
    type: "yasb.active_window.ActiveWindowWidget"
    options:
      label: "{win[title]}"
      label_alt: "[class_name='{win[class_name]}' exe='{win[process][name]}' hwnd={win[hwnd]}]"
      label_no_window: ""
      max_length: 48
      max_length_ellipsis: "..."
      monitor_exclusive: false


ghostscript is not found

The given ghostscript "/home/user/mambaforge/envs/meme/bin/gs" is not an executable file.
Warning: Cannot convert EPS file to PNG as no install of Image Magick or Ghostscript is usable.

Did you solve this problem yet?
Thanks


Added motion log entry for creating polls.

@normanjaeckel How can I add a motion log for poll update in MotionPollViewSet?

You must extend a method like
def update(self, *args, **kwargs):
    result = super().update(*args, **kwargs)
    # do something like poll = self.get_object(); poll.motion.write_log(...)
    return result

@normanjaeckel I added timezone support for motion log time and fixed your remark. Please review again.

Please review again.

Rebase an merge.

Rebased.


Clearer instructions for migrating to prometheus plugin

What does this PR do?

Motivation

The mapping from management cli to prometheus metrics led to a lot of confusion. Customers found the switch between raw prometheus metric names and datadog metric names for the legacy integration particularly confusing.
At the end of the day customers just wanted to know if a particular metric from the legacy integration was also present in the new integration. This question can be answered just as well by consulting the metadata.csv-generated table with metric descriptions.
This PR removes the confusing table and points the customers to metadata.csv with clear instructions what to look for.
Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

Current dependencies on/for this PR:

master

PR #14443   👈

PR #14444

This comment was auto-generated by Graphite.

Thanks @maycmlee suggestions applied!


Can't click anything (getting buffering cursor) on

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I set up (or tried to) TeslaMate according to this doc https://docs.teslamate.org/docs/guides/apache/ However I'm running Plesk on my WebServer so instead of the teslamate.conf step I created two subdomains (grafana and teslamate) and set up basic auth there by adding this:
# Reverse Proxy Configuration
ProxyPreserveHost On
ProxyPass / http://<IP_ADDRESS>:4000/
ProxyPassReverse / http://<IP_ADDRESS>:4000/

# Basic Auth Configuration
<Location />
	AuthType Basic
	AuthName "Restricted Area"
	AuthUserFile /path
	Require valid-user
</Location>

I can access the subdomains and it asks me for a password as expected. If I enter it I get to the TeslaMate interface however I can't click anything and the cursor turns into a buffering / loading circle like in issue #466 I tried with Firefox and Chrome (I'm on a Windows machine)
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
teslamate-1  | 2024-04-06 06:19:06.790 [info] create table states
teslamate-1  | 2024-04-06 06:19:06.858 [info] == Migrated<PHONE_NUMBER>0000 in 0.0s
teslamate-1  | 2024-04-06 06:19:06.901 [info] == Running<PHONE_NUMBER>0000 TeslaMate.Repo.Migrations.CreateChargingProcesses.change/0 forward
teslamate-1  | 2024-04-06 06:19:06.901 [info] create table charging_processes
teslamate-1  | 2024-04-06 06:19:06.961 [info] == Migrated<PHONE_NUMBER>0000 in 0.0s
teslamate-1  | 2024-04-06 06:19:06.988 [info] == Running<PHONE_NUMBER>0000 TeslaMate.Repo.Migrations.CreateCharges.change/0 forward
teslamate-1  | 2024-04-06 06:19:06.988 [info] create table charges
teslamate-1  | 2024-04-06 06:19:07.143 [info] == Migrated<PHONE_NUMBER>0000 in 0.1s
teslamate-1  | 2024-04-06 06:19:07.171 [info] == Running<PHONE_NUMBER>3117 TeslaMate.Repo.Migrations.CreateUpdates.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.171 [info] create table updates
teslamate-1  | 2024-04-06 06:19:07.244 [info] == Migrated<PHONE_NUMBER>3117 in 0.0s
teslamate-1  | 2024-04-06 06:19:07.271 [info] == Running<PHONE_NUMBER>3933 TeslaMate.Repo.Migrations.AddInsideTemp.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.271 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:07.272 [info] alter table trips
teslamate-1  | 2024-04-06 06:19:07.272 [info] == Migrated<PHONE_NUMBER>3933 in 0.0s
teslamate-1  | 2024-04-06 06:19:07.321 [info] == Running<PHONE_NUMBER>5227 TeslaMate.Repo.Migrations.AddBatteryHeaterFields.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.321 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:07.322 [info] alter table charges
teslamate-1  | 2024-04-06 06:19:07.322 [info] == Migrated<PHONE_NUMBER>5227 in 0.0s
teslamate-1  | 2024-04-06 06:19:07.354 [info] == Running<PHONE_NUMBER>0006 TeslaMate.Repo.Migrations.CreateAddresses.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.355 [info] create table addresses
teslamate-1  | 2024-04-06 06:19:07.496 [info] create index addresses_place_id_index
teslamate-1  | 2024-04-06 06:19:07.562 [info] == Migrated<PHONE_NUMBER>0006 in 0.2s
teslamate-1  | 2024-04-06 06:19:07.571 [info] == Running<PHONE_NUMBER>0705 TeslaMate.Repo.Migrations.AddAddressesToTrips.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.571 [info] alter table trips
teslamate-1  | 2024-04-06 06:19:07.574 [info] == Migrated<PHONE_NUMBER>0705 in 0.0s
teslamate-1  | 2024-04-06 06:19:07.613 [info] == Running<PHONE_NUMBER>2200 TeslaMate.Repo.Migrations.AddAddressToChargingProcess.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.613 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:07.614 [info] == Migrated<PHONE_NUMBER>2200 in 0.0s
teslamate-1  | 2024-04-06 06:19:07.638 [info] == Running<PHONE_NUMBER>5429 TeslaMate.Repo.Migrations.AddIndexesOnDates.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.638 [info] create index positions_date_index
teslamate-1  | 2024-04-06 06:19:07.722 [info] create index charges_date_index
teslamate-1  | 2024-04-06 06:19:07.782 [info] == Migrated<PHONE_NUMBER>5429 in 0.1s
teslamate-1  | 2024-04-06 06:19:07.832 [info] == Running<PHONE_NUMBER>5700 TeslaMate.Repo.Migrations.RenameSocFields.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.833 [info] rename column start_soc to start_range_km on table charging_processes
teslamate-1  | 2024-04-06 06:19:07.833 [info] rename column end_soc to end_range_km on table charging_processes
teslamate-1  | 2024-04-06 06:19:07.833 [info] == Migrated<PHONE_NUMBER>5700 in 0.0s
teslamate-1  | 2024-04-06 06:19:07.874 [info] == Running<PHONE_NUMBER>4003 TeslaMate.Repo.Migrations.AddFkeyIndexes.change/0 forward
teslamate-1  | 2024-04-06 06:19:07.875 [info] create index charges_charging_process_id_index
teslamate-1  | 2024-04-06 06:19:07.941 [info] create index charging_processes_car_id_index
teslamate-1  | 2024-04-06 06:19:08.000 [info] create index charging_processes_position_id_index
teslamate-1  | 2024-04-06 06:19:08.075 [info] create index charging_processes_address_id_index
teslamate-1  | 2024-04-06 06:19:08.165 [info] create index positions_car_id_index
teslamate-1  | 2024-04-06 06:19:08.242 [info] create index positions_trip_id_index
teslamate-1  | 2024-04-06 06:19:08.284 [info] create index states_car_id_index
teslamate-1  | 2024-04-06 06:19:08.326 [info] create index trips_car_id_index
teslamate-1  | 2024-04-06 06:19:08.434 [info] create index trips_start_address_id_index
teslamate-1  | 2024-04-06 06:19:08.494 [info] create index trips_end_address_id_index
teslamate-1  | 2024-04-06 06:19:08.536 [info] create index updates_car_id_index
teslamate-1  | 2024-04-06 06:19:08.578 [info] == Migrated<PHONE_NUMBER>4003 in 0.7s
teslamate-1  | 2024-04-06 06:19:08.605 [info] == Running<PHONE_NUMBER>2656 TeslaMate.Repo.Migrations.AddConversionFunctions.up/0 forward
teslamate-1  | 2024-04-06 06:19:08.605 [info] execute "CREATE FUNCTION convert_celsius(n double precision, unit text)\nRETURNS double precision\nAS $$\n  SELECT\n    CASE WHEN $2 = 'C' THEN $1\n         WHEN $2 = 'F' THEN ($1 * 9 / 5) + 32\n    END;\n$$\nLANGUAGE SQL\nIMMUTABLE\nRETURNS NULL ON NULL INPUT;\n"
teslamate-1  | 2024-04-06 06:19:08.606 [info] execute "CREATE FUNCTION convert_km(n double precision, unit text)\nRETURNS double precision\nAS $$\n  SELECT\n    CASE WHEN $2 = 'km' THEN $1\n         WHEN $2 = 'mi' THEN $1 / 1.60934\n    END;\n$$\nLANGUAGE SQL\nIMMUTABLE\nRETURNS NULL ON NULL INPUT;\n"
teslamate-1  | 2024-04-06 06:19:08.607 [info] == Migrated<PHONE_NUMBER>2656 in 0.0s
teslamate-1  | 2024-04-06 06:19:08.639 [info] == Running<PHONE_NUMBER>1314 TeslaMate.Repo.Migrations.FixTripEfficiency.up/0 forward
teslamate-1  | 2024-04-06 06:19:08.640 [info] == Migrated<PHONE_NUMBER>1314 in 0.0s
teslamate-1  | 2024-04-06 06:19:08.688 [info] == Running<PHONE_NUMBER>1523 TeslaMate.Repo.Migrations.CreateTokens.change/0 forward
teslamate-1  | 2024-04-06 06:19:08.688 [info] create table tokens
teslamate-1  | 2024-04-06 06:19:08.812 [info] == Migrated<PHONE_NUMBER>1523 in 0.1s
teslamate-1  | 2024-04-06 06:19:08.822 [info] == Running<PHONE_NUMBER>4452 TeslaMate.Repo.Migrations.CreateSettings.up/0 forward
teslamate-1  | 2024-04-06 06:19:08.822 [info] create table settings
teslamate-1  | 2024-04-06 06:19:08.917 [info] == Migrated<PHONE_NUMBER>4452 in 0.0s
teslamate-1  | 2024-04-06 06:19:08.964 [info] == Running<PHONE_NUMBER>2941 TeslaMate.Repo.Migrations.FixIncompleteChargingProcesses.up/0 forward
teslamate-1  | 2024-04-06 06:19:08.964 [info] == Migrated<PHONE_NUMBER>2941 in 0.0s
teslamate-1  | 2024-04-06 06:19:08.997 [info] == Running<PHONE_NUMBER>5216 TeslaMate.Repo.Migrations.UnitOfLengthAndTemperature.up/0 forward
teslamate-1  | 2024-04-06 06:19:08.998 [info] execute "CREATE TYPE length AS ENUM ('km', 'mi')"
teslamate-1  | 2024-04-06 06:19:08.999 [info] execute "CREATE TYPE temperature AS ENUM ('C', 'F')"
teslamate-1  | 2024-04-06 06:19:08.999 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:09.008 [info] == Migrated<PHONE_NUMBER>5216 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.047 [info] == Running<PHONE_NUMBER>1321 TeslaMate.Repo.Migrations.PersistSuspendSettings.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.047 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:09.048 [info] == Migrated<PHONE_NUMBER>1321 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.081 [info] == Running<PHONE_NUMBER>1901 TeslaMate.Repo.Migrations.CreateGeofences.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.081 [info] create table geofences
teslamate-1  | 2024-04-06 06:19:09.130 [info] create index geofences_address_id_index
teslamate-1  | 2024-04-06 06:19:09.181 [info] == Migrated<PHONE_NUMBER>1901 in 0.1s
teslamate-1  | 2024-04-06 06:19:09.223 [info] == Running<PHONE_NUMBER>1616 TeslaMate.Repo.Migrations.RenameTripsToDrives.up/0 forward
teslamate-1  | 2024-04-06 06:19:09.223 [info] rename table trips to drives
teslamate-1  | 2024-04-06 06:19:09.223 [info] rename column trip_id to drive_id on table positions
teslamate-1  | 2024-04-06 06:19:09.224 [info] execute "ALTER INDEX positions_trip_id_index RENAME TO positions_drive_id_index;"
teslamate-1  | 2024-04-06 06:19:09.224 [info] execute "ALTER TABLE positions RENAME CONSTRAINT positions_trip_id_fkey TO positions_drive_id_fkey"
teslamate-1  | 2024-04-06 06:19:09.224 [info] == Migrated<PHONE_NUMBER>1616 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.247 [info] == Running<PHONE_NUMBER>4320 TeslaMate.Repo.Migrations.FixIncompleteChargingProcessesV2.up/0 forward
teslamate-1  | 2024-04-06 06:19:09.247 [info] == Migrated<PHONE_NUMBER>4320 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.280 [info] == Running<PHONE_NUMBER>2810 TeslaMate.Repo.Migrations.IncreaseSuspendMin.up/0 forward
teslamate-1  | 2024-04-06 06:19:09.281 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:09.282 [info] == Migrated<PHONE_NUMBER>2810 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.305 [info] == Running<PHONE_NUMBER>5713 TeslaMate.Repo.Migrations.ExtendCarTable.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.306 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:09.480 [info] == Migrated<PHONE_NUMBER>5713 in 0.1s
teslamate-1  | 2024-04-06 06:19:09.514 [info] == Running<PHONE_NUMBER>0723 TeslaMate.Repo.Migrations.AddEstBatteryRangeKm.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.514 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:09.515 [info] == Migrated<PHONE_NUMBER>0723 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.547 [info] == Running<PHONE_NUMBER>3938 TeslaMate.Repo.Migrations.AddConstraints.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.548 [info] create index states_car_id__end_date_IS_NULL_index
teslamate-1  | 2024-04-06 06:19:09.591 [info] create check constraint positive_duration on table states
teslamate-1  | 2024-04-06 06:19:09.592 [info] create check constraint positive_duration on table updates
teslamate-1  | 2024-04-06 06:19:09.592 [info] == Migrated<PHONE_NUMBER>3938 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.634 [info] == Running<PHONE_NUMBER>5748 TeslaMate.Repo.Migrations.DropConsumptionColumns.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.634 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:09.635 [info] == Migrated<PHONE_NUMBER>5748 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.664 [info] == Running<PHONE_NUMBER>3437 TeslaMate.Repo.Migrations.AddSleepRequirements.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.664 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:09.665 [info] == Migrated<PHONE_NUMBER>3437 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.714 [info] == Running<PHONE_NUMBER>2828 TeslaMate.Repo.Migrations.FixIncompleteChargingProcessesV3.up/0 forward
teslamate-1  | 2024-04-06 06:19:09.714 [info] == Migrated<PHONE_NUMBER>2828 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.756 [info] == Running<PHONE_NUMBER>4708 TeslaMate.Repo.Migrations.AddBatteryRange.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.756 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:09.756 [info] == Migrated<PHONE_NUMBER>4708 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.789 [info] == Running<PHONE_NUMBER>4902 TeslaMate.Repo.Migrations.AddElevation.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.789 [info] rename column altitude to elevation on table positions
teslamate-1  | 2024-04-06 06:19:09.790 [info] == Migrated<PHONE_NUMBER>4902 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.848 [info] == Running<PHONE_NUMBER>2529 TeslaMate.Repo.Migrations.AddMToFtConversionHelper.up/0 forward
teslamate-1  | 2024-04-06 06:19:09.848 [info] execute "CREATE FUNCTION convert_m(n double precision, unit text)\nRETURNS double precision\nAS $$\n  SELECT\n    CASE WHEN $2 = 'm' THEN $1\n         WHEN $2 = 'ft' THEN $1 * 3.28084\n    END;\n$$\nLANGUAGE SQL\nIMMUTABLE\nRETURNS NULL ON NULL INPUT;\n"
teslamate-1  | 2024-04-06 06:19:09.848 [info] == Migrated<PHONE_NUMBER>2529 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.902 [info] == Running<PHONE_NUMBER>0058 TeslaMate.Repo.Migrations.DoNotRequireEfficiency.up/0 forward
teslamate-1  | 2024-04-06 06:19:09.902 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:09.903 [info] rename column version to trim_badging on table cars
teslamate-1  | 2024-04-06 06:19:09.903 [info] == Migrated<PHONE_NUMBER>0058 in 0.0s
teslamate-1  | 2024-04-06 06:19:09.931 [info] == Running<PHONE_NUMBER>1524 TeslaMate.Repo.Migrations.AddUniqueIndexOnVins.change/0 forward
teslamate-1  | 2024-04-06 06:19:09.931 [info] create index cars_vin_index
teslamate-1  | 2024-04-06 06:19:10.015 [info] == Migrated<PHONE_NUMBER>1524 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.048 [info] == Running<PHONE_NUMBER>5850 TeslaMate.Repo.Migrations.AddRangeEnum.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.048 [info] execute "CREATE TYPE range AS ENUM ('ideal', 'rated')"
teslamate-1  | 2024-04-06 06:19:10.048 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:10.049 [info] == Migrated<PHONE_NUMBER>5850 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.081 [info] == Running<PHONE_NUMBER>5011 TeslaMate.Repo.Migrations.AddRatedRangeToDrives.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.081 [info] rename column battery_range_km to rated_battery_range_km on table positions
teslamate-1  | 2024-04-06 06:19:10.082 [info] rename column start_range_km to start_ideal_range_km on table drives
teslamate-1  | 2024-04-06 06:19:10.082 [info] rename column end_range_km to end_ideal_range_km on table drives
teslamate-1  | 2024-04-06 06:19:10.082 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:10.083 [info] alter table charges
teslamate-1  | 2024-04-06 06:19:10.083 [info] rename column start_range_km to start_ideal_range_km on table charging_processes
teslamate-1  | 2024-04-06 06:19:10.084 [info] rename column end_range_km to end_ideal_range_km on table charging_processes
teslamate-1  | 2024-04-06 06:19:10.084 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:10.084 [info] == Migrated<PHONE_NUMBER>5011 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.173 [info] == Running<PHONE_NUMBER>5543 TeslaMate.Repo.Migrations.SetStartAndEndRatedRangeKm.up/0 forward
teslamate-1  | 2024-04-06 06:19:10.185 [info] == Migrated<PHONE_NUMBER>5543 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.214 [info] == Running<PHONE_NUMBER>2807 TeslaMate.Repo.Migrations.CreateGeoExtensions.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.214 [info] execute "CREATE EXTENSION IF NOT EXISTS cube"
teslamate-1  | 2024-04-06 06:19:10.222 [info] execute "CREATE EXTENSION IF NOT EXISTS earthdistance"
teslamate-1  | 2024-04-06 06:19:10.223 [info] create index geofences__earth_box_ll_to_earth_latitude__longitude___radius_index
teslamate-1  | 2024-04-06 06:19:10.303 [info] == Migrated<PHONE_NUMBER>2807 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.334 [info] == Running<PHONE_NUMBER>1034 TeslaMate.Repo.Migrations.CreateIndexOnAddressPositions.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.334 [info] create index addresses_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:10.395 [info] == Migrated<PHONE_NUMBER>1034 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.429 [info] == Running<PHONE_NUMBER>2253 TeslaMate.Repo.Migrations.AddGeofenceIdToAddresses.up/0 forward
teslamate-1  | 2024-04-06 06:19:10.429 [info] alter table addresses
teslamate-1  | 2024-04-06 06:19:10.431 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:10.432 [info] create index addresses_geofence_id_index
teslamate-1  | 2024-04-06 06:19:10.479 [info] == Migrated<PHONE_NUMBER>2253 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.508 [info] == Running<PHONE_NUMBER>5641 TeslaMate.Repo.Migrations.AddBaseUrlSetting.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.509 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:10.509 [info] == Migrated<PHONE_NUMBER>5641 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.542 [info] == Running<PHONE_NUMBER>0650 TeslaMate.Repo.Migrations.AddStartAndEndPositionToDrives.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.542 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:10.545 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:10.546 [info] alter table addresses
teslamate-1  | 2024-04-06 06:19:10.547 [info] create index positions_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:10.622 [info] == Migrated<PHONE_NUMBER>0650 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.651 [info] == Running<PHONE_NUMBER>2415 TeslaMate.Repo.Migrations.AddPositionIdsAndApplyGeofences.up/0 forward
teslamate-1  | 2024-04-06 06:19:10.652 [info] == Migrated<PHONE_NUMBER>2415 in 0.0s
teslamate-1  | 2024-04-06 06:19:10.684 [info] == Running<PHONE_NUMBER>5010 TeslaMate.Repo.Migrations.AddNewFkeyIndexes.change/0 forward
teslamate-1  | 2024-04-06 06:19:10.684 [info] create index drives_start_position_id_index
teslamate-1  | 2024-04-06 06:19:10.757 [info] create index drives_end_position_id_index
teslamate-1  | 2024-04-06 06:19:10.806 [info] create index drives_start_geofence_id_index
teslamate-1  | 2024-04-06 06:19:10.864 [info] create index drives_end_geofence_id_index
teslamate-1  | 2024-04-06 06:19:10.915 [info] drop index positions_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:10.915 [info] drop index addresses_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:10.916 [info] drop index geofences__earth_box_ll_to_earth_latitude__longitude___radius_index
teslamate-1  | 2024-04-06 06:19:10.916 [info] create index positions_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:10.917 [info] create index addresses_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:10.918 [info] == Migrated<PHONE_NUMBER>5010 in 0.2s
teslamate-1  | 2024-04-06 06:19:10.958 [info] == Running<PHONE_NUMBER>1431 TeslaMate.Repo.Migrations.FixLlToEarth.up/0 forward
teslamate-1  | 2024-04-06 06:19:10.958 [info] execute "CREATE OR REPLACE FUNCTION public.ll_to_earth(float8, float8)\nRETURNS public.earth\nLANGUAGE SQL\nIMMUTABLE STRICT\nPARALLEL SAFE\nAS 'SELECT public.cube(public.cube(public.cube(public.earth()*cos(radians($1))*cos(radians($2))),public.earth()*cos(radians($1))*sin(radians($2))),public.earth()*sin(radians($1)))::public.earth';\n"
teslamate-1  | 2024-04-06 06:19:10.958 [info] == Migrated<PHONE_NUMBER>1431 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.009 [info] == Running<PHONE_NUMBER>3836 TeslaMate.Repo.Migrations.AddEstTotalChargeEnergy.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.009 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:11.010 [info] == Migrated<PHONE_NUMBER>3836 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.051 [info] == Running<PHONE_NUMBER>0234 TeslaMate.Repo.Migrations.IncreaseDatetimePrecision.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.051 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:11.052 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:11.053 [info] alter table states
teslamate-1  | 2024-04-06 06:19:11.133 [info] alter table updates
teslamate-1  | 2024-04-06 06:19:11.134 [info] alter table charges
teslamate-1  | 2024-04-06 06:19:11.135 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:11.136 [info] == Migrated<PHONE_NUMBER>0234 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.159 [info] == Running<PHONE_NUMBER>4449 TeslaMate.Repo.Migrations.DropCpConfidenceAndInterval.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.160 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:11.160 [info] == Migrated<PHONE_NUMBER>4449 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.193 [info] == Running<PHONE_NUMBER>5925 TeslaMate.Repo.Migrations.PhaseCorrection.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.193 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:11.193 [info] == Migrated<PHONE_NUMBER>5925 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.226 [info] == Running<PHONE_NUMBER>5642 TeslaMate.Repo.Migrations.CalculateChargeEnergyUsed.up/0 forward
teslamate-1  | 2024-04-06 06:19:11.226 [info] == Migrated<PHONE_NUMBER>5642 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.267 [info] == Running<PHONE_NUMBER>2320 TeslaMate.Repo.Migrations.AddCostFieldToCharges.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.267 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:11.268 [info] == Migrated<PHONE_NUMBER>2320 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.275 [info] == Running<PHONE_NUMBER>3038 TeslaMate.Repo.Migrations.AddGrafanaUrl.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.276 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:11.334 [info] == Migrated<PHONE_NUMBER>3038 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.385 [info] == Running<PHONE_NUMBER>1307 TeslaMate.Repo.Migrations.CarSettings.up/0 forward
teslamate-1  | 2024-04-06 06:19:11.385 [info] create table car_settings
teslamate-1  | 2024-04-06 06:19:11.443 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:11.445 [info] drop constraint cars_settings_id_fkey from table cars
teslamate-1  | 2024-04-06 06:19:11.446 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:11.447 [info] create index cars_settings_id_index
teslamate-1  | 2024-04-06 06:19:11.534 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:11.535 [info] == Migrated<PHONE_NUMBER>1307 in 0.1s
teslamate-1  | 2024-04-06 06:19:11.576 [info] == Running<PHONE_NUMBER>2847 TeslaMate.Repo.Migrations.GeofenceSleep.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.576 [info] alter table car_settings
teslamate-1  | 2024-04-06 06:19:11.577 [info] create table geofence_sleep_mode_whitelist
teslamate-1  | 2024-04-06 06:19:11.703 [info] create table geofence_sleep_mode_blacklist
teslamate-1  | 2024-04-06 06:19:11.769 [info] == Migrated<PHONE_NUMBER>2847 in 0.1s
teslamate-1  | 2024-04-06 06:19:11.809 [info] == Running<PHONE_NUMBER>5130 TeslaMate.Repo.Migrations.RemovePhaseCorrection.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.809 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:11.810 [info] == Migrated<PHONE_NUMBER>5130 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.842 [info] == Running<PHONE_NUMBER>0527 TeslaMate.Repo.Migrations.RecalcEnergyUsed.up/0 forward
teslamate-1  | 2024-04-06 06:19:11.843 [info] == Migrated<PHONE_NUMBER>0527 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.896 [info] == Running<PHONE_NUMBER>3606 TeslaMate.Repo.Migrations.AddUsableBatteryLevel.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.896 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:11.896 [info] == Migrated<PHONE_NUMBER>3606 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.946 [info] == Running<PHONE_NUMBER>0926 TeslaMate.Repo.Migrations.ChargesAddUsableBatteryLevel.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.946 [info] alter table charges
teslamate-1  | 2024-04-06 06:19:11.947 [info] == Migrated<PHONE_NUMBER>0926 in 0.0s
teslamate-1  | 2024-04-06 06:19:11.976 [info] == Running<PHONE_NUMBER>0125 TeslaMate.Repo.Migrations.AddLanguage.change/0 forward
teslamate-1  | 2024-04-06 06:19:11.976 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:11.976 [info] == Migrated<PHONE_NUMBER>0125 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.030 [info] == Running<PHONE_NUMBER>2602 TeslaMate.Repo.Migrations.ReplacePlaceIdWithOsmid.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.030 [info] drop index addresses_place_id_index
teslamate-1  | 2024-04-06 06:19:12.030 [info] alter table addresses
teslamate-1  | 2024-04-06 06:19:12.031 [info] create index addresses_osm_id_osm_type_index
teslamate-1  | 2024-04-06 06:19:12.096 [info] execute "UPDATE drives SET start_address_id = NULL, end_address_id = NULL;"
teslamate-1  | 2024-04-06 06:19:12.096 [info] execute "UPDATE charging_processes SET address_id = NULL;"
teslamate-1  | 2024-04-06 06:19:12.097 [info] execute "DELETE FROM addresses;"
teslamate-1  | 2024-04-06 06:19:12.097 [info] execute "ALTER SEQUENCE addresses_id_seq RESTART;"
teslamate-1  | 2024-04-06 06:19:12.098 [info] == Migrated<PHONE_NUMBER>2602 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.201 [info] == Running<PHONE_NUMBER>0311 TeslaMate.Repo.Migrations.CascadeDelete.up/0 forward
teslamate-1  | 2024-04-06 06:19:12.201 [info] drop constraint cars_settings_id_fkey from table cars
teslamate-1  | 2024-04-06 06:19:12.202 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:12.204 [info] drop constraint charges_charging_process_id_fkey from table charges
teslamate-1  | 2024-04-06 06:19:12.204 [info] alter table charges
teslamate-1  | 2024-04-06 06:19:12.206 [info] drop constraint charging_processes_car_id_fkey from table charging_processes
teslamate-1  | 2024-04-06 06:19:12.207 [info] drop constraint charging_processes_address_id_fkey from table charging_processes
teslamate-1  | 2024-04-06 06:19:12.207 [info] drop constraint charging_processes_geofence_id_fkey from table charging_processes
teslamate-1  | 2024-04-06 06:19:12.208 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:12.211 [info] drop constraint if exists trips_car_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.211 [info] drop constraint if exists drives_car_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.212 [info] constraint "drives_car_id_fkey" of relation "drives" does not exist, skipping
teslamate-1  | 2024-04-06 06:19:12.212 [info] drop constraint drives_start_position_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.212 [info] drop constraint drives_end_position_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.213 [info] drop constraint if exists trips_start_address_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.213 [info] drop constraint if exists trips_end_address_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.213 [info] drop constraint if exists drives_start_address_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.213 [info] constraint "drives_start_address_id_fkey" of relation "drives" does not exist, skipping
teslamate-1  | 2024-04-06 06:19:12.213 [info] drop constraint if exists drives_end_address_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.214 [info] constraint "drives_end_address_id_fkey" of relation "drives" does not exist, skipping
teslamate-1  | 2024-04-06 06:19:12.214 [info] drop constraint drives_start_geofence_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.214 [info] drop constraint drives_end_geofence_id_fkey from table drives
teslamate-1  | 2024-04-06 06:19:12.214 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:12.218 [info] drop constraint positions_car_id_fkey from table positions
teslamate-1  | 2024-04-06 06:19:12.218 [info] drop constraint positions_drive_id_fkey from table positions
teslamate-1  | 2024-04-06 06:19:12.219 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:12.220 [info] drop constraint states_car_id_fkey from table states
teslamate-1  | 2024-04-06 06:19:12.220 [info] alter table states
teslamate-1  | 2024-04-06 06:19:12.272 [info] drop constraint updates_car_id_fkey from table updates
teslamate-1  | 2024-04-06 06:19:12.273 [info] alter table updates
teslamate-1  | 2024-04-06 06:19:12.274 [info] == Migrated<PHONE_NUMBER>0311 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.335 [info] == Running<PHONE_NUMBER>0529 TeslaMate.Repo.Migrations.LocationBasedChargeCost.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.335 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:12.335 [info] alter table car_settings
teslamate-1  | 2024-04-06 06:19:12.336 [info] == Migrated<PHONE_NUMBER>0529 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.385 [info] == Running<PHONE_NUMBER>1245 TeslaMate.Repo.Migrations.LocationBasedChargeCostIncreaseScale.up/0 forward
teslamate-1  | 2024-04-06 06:19:12.385 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:12.476 [info] == Migrated<PHONE_NUMBER>1245 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.510 [info] == Running<PHONE_NUMBER>1330 TeslaMate.Repo.Migrations.UseRatedAsDefaultPreferredRange.up/0 forward
teslamate-1  | 2024-04-06 06:19:12.510 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:12.511 [info] == Migrated<PHONE_NUMBER>1330 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.551 [info] == Running<PHONE_NUMBER>0654 TeslaMate.Repo.Migrations.AddVehicleConfigAttrbitues.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.552 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:12.552 [info] == Migrated<PHONE_NUMBER>0654 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.585 [info] == Running<PHONE_NUMBER>0218 TeslaMate.Repo.Migrations.UpdateCities.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.585 [info] execute "UPDATE addresses a\nSET city = (\n  SELECT trim(BOTH '\"' FROM COALESCE(\n    raw -> 'address' -> 'city',\n    raw -> 'address' -> 'town',\n    raw -> 'address' -> 'municipality',\n    raw -> 'address' -> 'village',\n    raw -> 'address' -> 'hamlet',\n    raw -> 'address' -> 'locality',\n    raw -> 'address' -> 'croft'\n  )::text)\n  FROM addresses\n  WHERE a.id = id\n) WHERE\n  raw -> 'address' -> 'village' IS NOT NULL OR\n  raw -> 'address' -> 'hamlet' IS NOT NULL OR\n  raw -> 'address' -> 'locality' IS NOT NULL OR\n  raw -> 'address' -> 'croft' IS NOT NULL;\n"
teslamate-1  | 2024-04-06 06:19:12.586 [info] == Migrated<PHONE_NUMBER>0218 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.635 [info] == Running<PHONE_NUMBER>3847 TeslaMate.Repo.Migrations.AddFlatFee.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.635 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:12.635 [info] == Migrated<PHONE_NUMBER>3847 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.660 [info] == Running<PHONE_NUMBER>4021 TeslaMate.Repo.Migrations.UseStreamingApi.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.660 [info] alter table car_settings
teslamate-1  | 2024-04-06 06:19:12.660 [info] == Migrated<PHONE_NUMBER>4021 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.718 [info] == Running<PHONE_NUMBER>0020 TeslaMate.Repo.Migrations.DropPowerAvg.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.718 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:12.719 [info] == Migrated<PHONE_NUMBER>0020 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.752 [info] == Running<PHONE_NUMBER>0940 TeslaMate.Repo.Migrations.RemoveSleepModeToggles.up/0 forward
teslamate-1  | 2024-04-06 06:19:12.752 [info] alter table car_settings
teslamate-1  | 2024-04-06 06:19:12.752 [info] drop table geofence_sleep_mode_whitelist
teslamate-1  | 2024-04-06 06:19:12.753 [info] drop table geofence_sleep_mode_blacklist
teslamate-1  | 2024-04-06 06:19:12.754 [info] == Migrated<PHONE_NUMBER>0940 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.802 [info] == Running<PHONE_NUMBER>1402 TeslaMate.Repo.Migrations.RemoveSleepModeRequirements.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.802 [info] alter table car_settings
teslamate-1  | 2024-04-06 06:19:12.803 [info] == Migrated<PHONE_NUMBER>1402 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.843 [info] == Running<PHONE_NUMBER>1923 TeslaMate.Repo.Migrations.EnableStreaming.up/0 forward
teslamate-1  | 2024-04-06 06:19:12.846 [info] == Migrated<PHONE_NUMBER>1923 in 0.0s
teslamate-1  | 2024-04-06 06:19:12.877 [info] == Running<PHONE_NUMBER>2005 TeslaMate.Repo.Migrations.DatabaseEfficiencyImprovements.change/0 forward
teslamate-1  | 2024-04-06 06:19:12.877 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:13.254 [info] alter table addresses
teslamate-1  | 2024-04-06 06:19:13.405 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:13.606 [info] alter table drives
teslamate-1  | 2024-04-06 06:19:14.043 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:14.132 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:14.345 [info] alter table charges
teslamate-1  | 2024-04-06 06:19:14.596 [info] alter table states
teslamate-1  | 2024-04-06 06:19:14.755 [info] alter table tokens
teslamate-1  | 2024-04-06 06:19:14.871 [info] alter table updates
teslamate-1  | 2024-04-06 06:19:14.998 [info] == Migrated<PHONE_NUMBER>2005 in 2.1s
teslamate-1  | 2024-04-06 06:19:15.035 [info] == Running<PHONE_NUMBER>0646 TeslaMate.Repo.Migrations.DropUnusedIndexes.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.035 [info] drop index if exists positions_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:15.036 [info] drop index if exists addresses_ll_to_earth_latitude__longitude_index
teslamate-1  | 2024-04-06 06:19:15.037 [info] == Migrated<PHONE_NUMBER>0646 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.063 [info] == Running<PHONE_NUMBER>3852 TeslaMate.Repo.Migrations.CostByMinute.up/0 forward
teslamate-1  | 2024-04-06 06:19:15.063 [info] execute "CREATE TYPE billing_type AS ENUM ('per_kwh', 'per_minute')"
teslamate-1  | 2024-04-06 06:19:15.063 [info] alter table geofences
teslamate-1  | 2024-04-06 06:19:15.064 [info] rename column cost_per_kwh to cost_per_unit on table geofences
teslamate-1  | 2024-04-06 06:19:15.064 [info] == Migrated<PHONE_NUMBER>3852 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.113 [info] == Running<PHONE_NUMBER>3223 TeslaMate.Repo.Migrations.RenameUnitEnums.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.113 [info] execute "ALTER TYPE length RENAME TO unit_of_length"
teslamate-1  | 2024-04-06 06:19:15.113 [info] execute "ALTER TYPE temperature RENAME TO unit_of_temperature"
teslamate-1  | 2024-04-06 06:19:15.113 [info] == Migrated<PHONE_NUMBER>3223 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.154 [info] == Running<PHONE_NUMBER>5158 TeslaMate.Repo.Migrations.OptimizeConversionHelpers.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.154 [info] execute "DROP FUNCTION IF EXISTS public.convert_km(double precision, text);"
teslamate-1  | 2024-04-06 06:19:15.155 [info] execute "CREATE OR REPLACE FUNCTION public.convert_km(n numeric(6,2), unit text)\nRETURNS numeric(6,2)\nLANGUAGE 'sql'\nCOST 100\nVOLATILE\nAS $BODY$\n  SELECT\n  CASE $2 WHEN 'km' THEN $1\n          WHEN 'mi' THEN $1 / 1.60934\n  END;\n$BODY$;\n"
teslamate-1  | 2024-04-06 06:19:15.155 [info] execute "DROP FUNCTION IF EXISTS public.convert_celsius(double precision, text);"
teslamate-1  | 2024-04-06 06:19:15.156 [info] execute "CREATE OR REPLACE FUNCTION public.convert_celsius(n numeric(4,1), unit text)\nRETURNS numeric(4,1)\nLANGUAGE 'sql'\nCOST 100\nVOLATILE\nAS $BODY$\n  SELECT\n  CASE $2 WHEN 'C' THEN $1\n          WHEN 'F' THEN ($1 * 9 / 5) + 32\n  END;\n$BODY$;\n"
teslamate-1  | 2024-04-06 06:19:15.156 [info] == Migrated<PHONE_NUMBER>5158 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.188 [info] == Running<PHONE_NUMBER>5119 TeslaMate.Repo.Migrations.ChangeSleepRequirementsDefault.up/0 forward
teslamate-1  | 2024-04-06 06:19:15.188 [info] alter table car_settings
teslamate-1  | 2024-04-06 06:19:15.188 [info] == Migrated<PHONE_NUMBER>5119 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.238 [info] == Running<PHONE_NUMBER>4838 TeslaMate.Repo.Migrations.UseVariableLengthTypeForTokens.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.238 [info] alter table tokens
teslamate-1  | 2024-04-06 06:19:15.238 [info] == Migrated<PHONE_NUMBER>4838 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.288 [info] == Running<PHONE_NUMBER>3700 TeslaMate.Repo.Migrations.CarPriorities.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.288 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:15.289 [info] == Migrated<PHONE_NUMBER>3700 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.321 [info] == Running<PHONE_NUMBER>3305 TeslaMate.Repo.Migrations.AddNotNullConstraintToDisplayPriority.up/0 forward
teslamate-1  | 2024-04-06 06:19:15.321 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:15.322 [info] == Migrated<PHONE_NUMBER>3305 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.371 [info] == Running<PHONE_NUMBER>3654 TeslaMate.Repo.Migrations.AddNotNullConstraintToStartDate.up/0 forward
teslamate-1  | 2024-04-06 06:19:15.371 [info] alter table charging_processes
teslamate-1  | 2024-04-06 06:19:15.372 [info] == Migrated<PHONE_NUMBER>3654 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.418 [info] == Running<PHONE_NUMBER>1732 TeslaMate.Repo.Migrations.EncryptApiTokens.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.418 [info] alter table tokens
teslamate-1  | 2024-04-06 06:19:15.419 [info] alter table tokens
teslamate-1  | 2024-04-06 06:19:15.419 [info] rename column encrypted_access to access on table tokens
teslamate-1  | 2024-04-06 06:19:15.420 [info] rename column encrypted_refresh to refresh on table tokens
teslamate-1  | 2024-04-06 06:19:15.420 [info] == Migrated<PHONE_NUMBER>1732 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.446 [info] == Running<PHONE_NUMBER>2017 TeslaMate.Repo.Migrations.AddMarketingNameToCar.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.446 [info] alter table cars
teslamate-1  | 2024-04-06 06:19:15.446 [info] == Migrated<PHONE_NUMBER>2017 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.496 [info] == Running<PHONE_NUMBER>0400 TeslaMate.Repo.Migrations.AddTirePressures.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.496 [info] alter table positions
teslamate-1  | 2024-04-06 06:19:15.497 [info] execute "CREATE OR REPLACE FUNCTION public.convert_tire_pressure(n numeric(6,2), character varying)\nRETURNS numeric(6,2)\nLANGUAGE 'sql'\nCOST 100\nVOLATILE\nAS $BODY$\nSELECT\nCASE $2 WHEN 'bar' THEN $1\n    WHEN 'psi' THEN $1 * 14.503773773\nEND;\n$BODY$;\n"
teslamate-1  | 2024-04-06 06:19:15.497 [info] == Migrated<PHONE_NUMBER>0400 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.543 [info] == Running<PHONE_NUMBER>5412 TeslaMate.Repo.Migrations.AddUnitOfPressureToGlobalSettings.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.543 [info] execute "CREATE TYPE unit_of_pressure AS ENUM ('bar', 'psi')"
teslamate-1  | 2024-04-06 06:19:15.543 [info] alter table settings
teslamate-1  | 2024-04-06 06:19:15.544 [info] == Migrated<PHONE_NUMBER>5412 in 0.0s
teslamate-1  | 2024-04-06 06:19:15.571 [info] == Running<PHONE_NUMBER>5712 TeslaMate.Repo.Migrations.AddCompositeIndexToPositions.change/0 forward
teslamate-1  | 2024-04-06 06:19:15.571 [info] create index positions_drive_id_date_index
teslamate-1  | 2024-04-06 06:19:15.707 [info] drop index positions_drive_id_index
teslamate-1  | 2024-04-06 06:19:15.707 [info] == Migrated<PHONE_NUMBER>5712 in 0.1s
teslamate-1  | 2024-04-06 06:19:16.934 [info] No tzdata release files found in custom data dir. Copying release file from tzdata priv dir.
teslamate-1  | 2024-04-06 06:19:16.995 [info] System Info: Erlang/OTP 26 (jit)
teslamate-1  | 2024-04-06 06:19:16.995 [info] Version: 1.28.5
teslamate-1  | 2024-04-06 06:19:17.029 [info] Running TeslaMateWeb.Endpoint with cowboy 2.10.0 at :::4000 (http)
teslamate-1  | 2024-04-06 06:19:17.030 [info] Access TeslaMateWeb.Endpoint at http://nicola.meisterkleister.ch
teslamate-1  | 2024-04-06 06:19:17.032 [info] MQTT connection has been established
teslamate-1  | 2024-04-06 06:19:20.475 [info] tzdata release in place is from a file last modified Fri, 22 Oct 2021 02:20:47 GMT. Release file on server was last modified Thu, 01 Feb 2024 18:40:48 GMT.
teslamate-1  | 2024-04-06 06:19:21.533 [info] Tzdata has updated the release from 2021e to 2024a
teslamate-1  | 2024-04-06 06:41:03.734 [info] GET /
teslamate-1  | 2024-04-06 06:41:03.738 [info] Sent 302 in 3ms
teslamate-1  | 2024-04-06 06:41:03.771 [info] GET /sign_in
teslamate-1  | 2024-04-06 06:41:03.775 [info] Sent 200 in 4ms
teslamate-1  | 2024-04-06 06:48:28.863 [info] GET /
teslamate-1  | 2024-04-06 06:48:28.865 [info] Sent 302 in 2ms
teslamate-1  | 2024-04-06 06:48:28.894 [info] GET /sign_in
teslamate-1  | 2024-04-06 06:48:28.898 [info] Sent 200 in 3ms
teslamate-1  | 2024-04-06 06:49:42.655 [info] GET /settings
teslamate-1  | 2024-04-06 06:49:42.662 [info] Sent 200 in 6ms
teslamate-1  | 2024-04-06 06:51:06.536 [info] GET /
teslamate-1  | 2024-04-06 06:51:06.538 [info] Sent 302 in 1ms
teslamate-1  | 2024-04-06 06:51:06.569 [info] GET /sign_in
teslamate-1  | 2024-04-06 06:51:06.573 [info] Sent 200 in 4ms
teslamate-1  | 2024-04-06 06:52:13.591 [info] GET /
teslamate-1  | 2024-04-06 06:52:13.592 [info] Sent 302 in 1ms
teslamate-1  | 2024-04-06 06:52:13.623 [info] GET /sign_in
teslamate-1  | 2024-04-06 06:52:13.625 [info] Sent 200 in 2ms
teslamate-1  | 2024-04-06 07:13:51.870 [info] GET /settings
teslamate-1  | 2024-04-06 07:13:51.875 [info] Sent 200 in 4ms

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.28.5

I did some more testing. I also get the error if I just add
ProxyPass /live/websocket ws://<IP_ADDRESS>:4000/live/websocket
ProxyPassReverse /live/websocket ws://<IP_ADDRESS>:4000/live/websocket
ProxyPass / http://<IP_ADDRESS>:4000/
ProxyPassReverse / http://<IP_ADDRESS>:4000/
Without this it would just load the standard plesk page for the subdomains I added

I figured it out. The problem was that Plesk uses a combination of Apache and nginx. For any other poor shmuck trying to set up TeslaMate with Basic Auth and Plesk here is what you have to do.

follow this tutorial: https://docs.teslamate.org/docs/guides/apache (but don't do the teslamate.conf step)

You can also leave out the let's encrypt line from the .env file

Instead, create two subdomains in plesk (for grafana and teslamate)

Secure them with an Let's Encrypt Certificate

For the teslamate subdomain go to "Hosting & DNS" and then "Apache & nginx"

under nginx settings turn off proxy mode to stop using apache and only rely on nginx.

then under addition nginx directives paste (make sure to replace domain with your domain and move the htpasswd file to that location... or use a different location and adjust accordingly=:
location / {
proxy_pass http://<IP_ADDRESS>:4000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
auth_basic "Restricted Content";
auth_basic_user_file /var/www/vhosts/domain/.htpasswd;
}

location /live/websocket {
proxy_pass http://<IP_ADDRESS>:4000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
auth_basic "Restricted Content";
auth_basic_user_file /var/www/vhosts/domain/.htpasswd;

}

for grafana go to "Hosting & DNS" and then "Apache & nginx"
under additional direvtices for https add (make sure to replace /path with the correct path to your htpasswd file):

Reverse Proxy Configuration
ProxyPreserveHost On
ProxyPass / http://<IP_ADDRESS>:3000/
ProxyPassReverse / http://<IP_ADDRESS>:3000/
Basic Auth Configuration

	AuthType Basic
	AuthName "Restricted Area"
	AuthUserFile /path
	Require valid-user

and that should be it... hope it helps someone bc I really could find barely anything about teslamate and plesk online :)

glad your solved your Plesk issue


Update API

Feature Request 🛍
Today, creating new types programmatically requires string manipulation. There is an internal AST for a Concerto definition, but it is not documented nor designed for manipulation.
Use Case

With an update API, a user could add a new declaration to an existing model, or even build models completely from scratch (e.g. from a graphical tool)
Possible Solution

As well as defining a public API for model manipulation, we should define a JSON DOM (similar to Cicero Mark DOM) of a model definition to allow efficient serialisation and deserialization.
Possible API signatures
modelFile.addConcept(name, properties, [superType]);
modelFile.updateConcept(name, [properties], [superType]);
modelFile.deleteConcept(name);
classDeclaration.addProperty(name, type, optional, validators);
classDeclaration.updateProperty(name, type, optional, validators);
classDeclaration.deleteProperty(name);

Context

Changing a model definition dynamically could lead to breaking changes in client code. We could chose to reject, warn, or allow breaking changes.
Detailed Description

@jeromesimeon @mttrbrts now that we have moved Concerto to the published metamodel I think we can close this.


Network::HeaderResponse does not contain hash

Component
network, json-rpc
What version of Alloy are you on?
alloy-network v0.6.0
Operating System
None
Describe the bug
With the recent changes in #1573, there is no longer a way to get the block hash from a generic alloy_network::Network response. The HeaderResponse now only contains the actual header, but no additional fields like the hash.
I expected that there would be a wrapper (similar to alloy_rpc_types_eth::Header) that would either store this hash directly, or if for some reason this is considered too Ethereum specific, at least some other_fields mechanism. Such behavior would also be consistent with the BlockResponse, and previous versions of alloy allowed direct access to the hash.

right, thanks for flagging.
imo @klkvr the easiest way to make this convenient is introducing a trait (HeaderResponse) or we can add some restriction to Sealed<&Self::Header>.
the former is likely easier


3X: Optimized bytecode backed context resolving [WIP]

The performance is notably better than the existing Javassist based bytecode backed symbol solver types... but JavaParser's source is incredibly messy and there is a lot of ugly static interdependence on utility classes. That sort of setup cannot be easily extensible, which makes it impossible as is to support all forms of resolution that the standard bundle does.


Reproducibility Issues

Hi Ryan,
I was trying to reproduce some of the results per the README and I've run into some issues. I would appreciate your help.
1.  SLiM syntax not up-to-date
I ran into some issues with the simulation using SLiM at the very beginning as the SLiM's syntax in the slim script seems to be outdated. Some examples would be: sim.generations,  sim.registerLateEvents, etc. If these could be appropriately updated, it would be great.
2.  Error with dry-run of snakemake
When I tried to execute the dry-run of snakemake, I got the following error:
FileNotFoundError in file /home/pshakya/sim_reproduce/lai-sim/workflow/rules/common.smk, line 5:
[Errno 2] No such file or directory: 'config/personal.simulations.tsv'

Since there were only test and revised tsv files in the config directory and I wanted to reproduce the simulations in the Flare paper, I copied and pasted the OLD/paper.*.tsv files into config directory and renamed them to personal.*.tsv files. After making this change and re-running the dry-run, I get the following errors:
Building DAG of jobs...
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:188: PerformanceWarning: indexing past lexsort depth may impact performance.
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:188: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:189: PerformanceWarning: indexing past lexsort depth may impact performance.
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:189: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:190: PerformanceWarning: indexing past lexsort depth may impact performance.
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:190: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:191: PerformanceWarning: indexing past lexsort depth may impact performance.
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:191: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
/data/pshakya/benchmarking_with_new_data_Frame/3way_browning/lai-sim/workflow/rules/la_and_vcf.smk:192: PerformanceWarning: indexing past lexsort depth may impact performance.
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/la_and_vcf.smk:192: FutureWarning: Series.__getitem__ treating keys as positions is deprecated. In a future version, integer keys will always be treated as labels (consistent with DataFrame behavior). To access a value by position, use `ser.iloc[pos]`
InputFunctionException in rule recap_and_mutate in file
/home/pshakya/sim_reproduce/lai-sim/workflow/rules/simulate.smk, line 36:
Error:
  AttributeError: 'Series' object has no attribute 'rec_map_path'
Wildcards:
  model_name=simple2pop
  sim_name=twopop_rep1
Traceback:
  File "/home/pshakya/sim_reproduce/lai-sim/workflow/rules/simulate.smk", line 45, in <lambda>
  File "/home/pshakya/sim_reproduce/lai-sim/env/lib/python3.11/site-packages/pandas/core/generic.py", line 6204, in __getattr__

3.  Other issue
I also noticed that there seems to be a SLiM script missing. When I glance at the paper.simulations.tsv file, this file workflow/scripts/sim/SLiM/AmericanAdmixture_4B11.LARGE.slim seems to be missing in the github repo.
Any feedback or updates to the repo so that the experiments could be reproduced would be of great help.
Thanks.

Hello and thanks for raising this issue.  Sorry for the delay in responding.
I just reran a small test analysis to confirm that the snakemake pipeline still works, at least for me.  I also provided a small update to the config files and the README to direct to a test analysis.  Some of these simulations where quite large and computationally intensive so I've focused on two analyses that can run on my personal computer.  I no longer have access to the computer cluster where the main study was conducted.
I will respond to each issue you raised below, but please feel free to follow up with any questions / concerns.
You will need to install the relevant programs into ./programs/, and make the sure the paths are in the file passed to snakemake with ' --configfile ./profiles/test/config.yaml'.  I don't have rights to distribute them here.
"1. SLiM syntax not up-to-date"
Yes, this project used SLiM version 3.x, while the current version of SLiM is 4.x.  Version 4.x allows more flexibility in a few simulation aspects, including decoupling generations and simulation 'ticks', and allows multi-species models.  I've adopted a few SLiM scripts from 3 to 4, that mostly just involved some small changes in the top-level 'sim' object.  But if I try to quickly change the SLiM scripts here there is a possibility of generation times or something else getting mixed up without a lot of checking, and I would not want that.  I would suggest using SLiM v3 with these SLiM scripts, or you can try to adapt them yourself, sorry to not be more helpful here.
"2. Error with dry-run of snakemake"
I've tried to update the readme and direct to the test analysis, which can be run with:
snakemake --configfile ./profiles/test/config.yaml --cores 11
just use as many cores as you want.
The specific error you received was because the current files like *.analysis.tsv file have more columns than the ones in the OLD folder you moved.
"3. Other issue" lack of SLiM script.
I see this file in the repo, here is a link

Hi Ryan,
Thank you for the reply. Apologies on my end as well for checking in late. I'm trying to reproduce the simulation and wanted to test it using just SLiM (v3.5), but I still get the following error (I tried to run the SLiM script that you linked):
Error on script line 124, character 13:
recmap = readCSV(filePath = slim_map, colNames = c("ends", "rates"), colTypes = "if", sep="\t");

So, could you be a little more specific about the SLiM version you used? Or, if you have any straightforward to replicate the 3-way admixture without using the snakemake pipeline?


Inconsistency in API log levels

Description:
Change log level of APi in an appropriate way while updating image, deleting image, deleting orgs and other hub invocation APIs
Suggested Labels:
Enhancement

Fixed by cellery-hub/158


[Bug] 2.0 Resizing leaves black background

Hi thanks for your work on this project! Upon integrating the 2.0 version, I noticed this behavior when resizing the frameless window. Indeed, the jitter is fixed, but the window now has a black background appearing quickly in the previous space the window occupied. The previous version didn't seem to have this behavior.
https://user-images.githubusercontent.com/10566658/165296112-feb8f653-220e-4093-8f01-f2f1680fd39d.mp4
Additional Information:
Graphics Backend:
qputenv("QT_OPENGL", "angle");
qputenv("QT_ANGLE_PLATFORM", "d3d9");

Windows:
Windows 10 Pro
19044.1645

Graphics Card / Driver:
NVIDIA GTX 1080 Ti
Driver: <IP_ADDRESS>.11

Looks like your are demenstrating a Qt Quick application. For Qt Quick applications, the whole user interface is rendered through 3D graphics API such as d3d11, opengl, vulkan and metal. The black background you observed is caused by the corresponding graphics API, not FramelessHelper. It will behave differently if you switch to a different graphics API. This issue is not fixable from the FramelessHelper side, and I also think it's beyond the ability of a frameless helper. If the previous 1.x version doesn't have this issue, it may be because the new implementation doesn't remove the whole window frame so Windows's internal rendering logic is different with before. The 1.x implementation will remove the whole window frame and thus causes flicker and jitter during window resizing, but it seems OpenGL can be more stable, the new implementation get rid the flicker and jitter by preserving the window frame, so looks like we can't have both advantages.

By the way, can you provide your Qt version? Thanks!

By the way, can you provide your Qt version? Thanks!

This is on Qt 6.3.0.

For Qt Quick applications, the whole user interface is rendered through 3D graphics API such as d3d11, opengl, vulkan and metal. The black background you observed is caused by the corresponding graphics API, not FramelessHelper. It will behave differently if you switch to a different graphics API.

For 6.0 it looks like everything goes through QRhi (https://www.qt.io/blog/graphics-in-qt-6.0-qrhi-qt-quick-qt-quick-3d). I think I'll be forced to use the default backend (rhi) for other reasons, so using the software backend isn't an option unfortunately. However, after I disabled the frameless helper, I just noticed the black bars remain during resizing, so looks like a Qt or graphics backend issue as you suggested. I noticed there is less jitter when resizing though (both with and without framelesshelper have some jitter though).
Have you tested this library on Qt 6+? I would be curious if you had any thoughts on the bit of jitter that's remaining.

I always use the latest stable version of Qt to do developing, so currently I'm using Qt 6.3.0 as well. But the information you provided makes me a little confused. You said you are using Qt6, however, you also set the QT_OPENGL and QT_ANGLE_PLATFORM environment variables. So looks like you want to use the ANGLE backend instead of the Desktop OpenGL. But this won't work in Qt6 because all ANGLE related code paths in Qt have been removed and the only choice is the Desktop OpenGL. But these two environment variables will work as expected in Qt5. And the issue you observed is very specific to the graphics card drivers. For example, I've tested FramelessHelper on Intel and AMD graphics cards and both of them don't have this issue at all. But you are using NVIDIA graphics cards so it may be a NVIDIA only issue, I guess. And I'm developing and testing on Windows 11, it may also have different result compared to Windows 10. This issue is quite complicated and to be honest fixing this kind of issues is really beyond the ability of a frameless helper.

I noticed there is less jitter when resizing though (both with and without framelesshelper have some jitter though).

This is because the most important code to reduce jitter have been merged into Qt itself sometime ago. The patch was contributed by me. It's merged after Qt 6.2.1 is released, so the first version that has the workaround is Qt 6.2.2. Qt 6.3 of course have that code as well, so the jitter is much more reduced for all Qt-based applications. The remaining jitter is because Qt's drawing system have some rounding issue internally, and it's not fixable from outside of Qt. I've seen several patches to improve the situation merged into QtBase and QtDeclarative sometime ago, maybe when Qt 6.4 is released, the jitter can be reduced more. Due to it's caused by internal Qt logic, we can't do anything to improve the situation.

Wait, I watched the screen recording you uploaded here for multiple times, and after some deeper thoughts, I think you are not using the OpenGL backend at all. From what I see from the video, the application should be using the Direct3D 11 backend. If you are using the OpenGL backend, there should be two differences: one is there will be a strange black bar on top of your homemade title bar, the other one is the black background during window resizing should not be visible. You should re-check your Qt RHI backend.
You can change your Qt RHI backend by calling QQuickWindow::setGraphicsApi() before any Qt Quick elements are created.

You said you are using Qt6, however, you also set the QT_OPENGL and QT_ANGLE_PLATFORM environment variables. So looks like you want to use the ANGLE backend instead of the Desktop OpenGL. But this won't work in Qt6 because all ANGLE related code paths in Qt have been removed and the only choice is the Desktop OpenGL. But these two environment variables will work as expected in Qt5.

Good point, I think this is just left over code from Qt5.

And the issue you observed is very specific to the graphics card drivers. For example, I've tested FramelessHelper on Intel and AMD graphics cards and both of them don't have this issue at all. But you are using NVIDIA graphics cards so it may be a NVIDIA only issue, I guess. And I'm developing and testing on Windows 11, it may also have different result compared to Windows 10. This issue is quite complicated and to be honest fixing this kind of issues is really beyond the ability of a frameless helper.

That's fair.

This is because the most important code to reduce jitter have been merged into Qt itself sometime ago. The patch was contributed by me. It's merged after Qt 6.2.1 is released, so the first version that has the workaround is Qt 6.2.2. Qt 6.3 of course have that code as well, so the jitter is much more reduced for all Qt-based applications. The remaining jitter is because Qt's drawing system have some rounding issue internally, and it's not fixable from outside of Qt. I've seen several patches to improve the situation merged into QtBase and QtDeclarative sometime ago, maybe when Qt 6.4 is released, the jitter can be reduced more. Due to it's caused by internal Qt logic, we can't do anything to improve the situation.

Understand. Thanks for that work as well, I can tell an improvement using Qt 6! Looking forward to seeing what you've done in Qt 6.4.
Thanks for your response, I'll close this issue since it's out of scope.


Improve startup

Review status: 0 of 3 files reviewed at latest revision, 1 unresolved discussion, some commit checks broke.

vaadin-components-gwt/src/main/webapp/vaadin-grid/demo.html, line 6 [r1] (raw file):
this change breaks demo in production mode

Comments from the review on Reviewable.io

tasks/gwt.js, line 90 [r2] (raw file):
This does not remove  from demo.html. Causing 404.

Comments from the review on Reviewable.io

tasks/gwt.js, line 90 [r2] (raw file):
does not remove src="sdm.js"**

Comments from the review on Reviewable.io

vaadin-components-gwt/src/main/webapp/vaadin-grid/demo.html, line 40 [r2] (raw file):
To avoid all refactors and extra lines, maybe we can keep this code as following:
function execute(id, cb) {
  HTMLImports.whenReady(cb(document.getElementById(id)));
}

Comments from the review on Reviewable.io

For some reason, master loading time is between 750ms and 900ms
After this modifications, it loads between 1100ms and 1250ms
All tests pass, except two are pending forever. But this is the case in master as well.

do you mean demo.html? or you are using some other examples?

Review status: 0 of 11 files reviewed at latest revision, 3 unresolved discussions, some commit checks broke.

vaadin-components-gwt/src/main/webapp/vaadin-grid/demo.html, line 6 [r1] (raw file):
done

vaadin-components-gwt/src/main/webapp/vaadin-grid/demo.html, line 40 [r2] (raw file):
This is intentional, I don't want to maintain execute, since there is a public API doing the same whenReady, also I wan't examples teach the final user what is the correct way in polymer to do something in this case whenReady

Comments from the review on Reviewable.io

Review status: 0 of 11 files reviewed at latest revision, 3 unresolved discussions, some commit checks pending.

tasks/gwt.js, line 90 [r2] (raw file):
Done

Comments from the review on Reviewable.io

Reviewed 9 of 11 files at r2, 2 of 2 files at r3.
Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks broke.

Comments from the review on Reviewable.io

This issue appears with demo.html but not with single Grid.

Comments from the review on Reviewable.io


Greenkeeper/happn wrapper 1.1.12

Coverage remained the same at 8.141% when pulling d5b7d765b5baac63eff086b3f8719c7f472f1bb2 on greenkeeper/happn-wrapper-1.1.12 into 937de9c7e0ad5a4117c432030c03d84ac6e7ab3e on master.


NuxtLink internal hash behavior

Environment

Operating System: Darwin
Node Version:     v20.9.0
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.7.2
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      css, vite, devtools, modules, runtimeConfig, algolia, stripe, experimental
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-3-g8ospn?file=pages%2Findex.vue
Describe the bug
I'm trying to use the power of target selector in css to show/hide a cart component.
For this I need to send the user to an url with a hash of the component id.
When I use the NuxtLink component with the value to="#cart" the url is updated but the component is not displayed. If I then use the external property, the component is displayed.
Vice versa, to hide the component I have to use the same property which results in reloading the page.
Additional context
No response
Logs
No response

This seems to be an issue when using plain Vue + Vue-Router already. Raised it there via https://github.com/vuejs/router/issues/2076


Data should not be stored in Github repo

Consider moving the data stored in demos/nfem_heat_equation/data to a proper data storage platform. Having to download 500MB of data just to get the main firedrake-to-pytorch linking code is pretty excessive and slow. The demo script can then check to see if the data is on disk before fetching it from a server, similar to how pytorch and tensorflow handle their datasets.

Thanks, this is a good point!