CLI - Authorization failed  "Forbidden resource"

Hello all!

A bit of context:

At first I was solo on the project, and configured the database via Supabase dashboard, and the base is on Supabase, not local. Now that we are 2 on it, I want to be able to manage migrations, generate types from the DB etc... and most important, making that each of us can have our own db locally. (We are newbies, we don't want to mess with the data of the other)
Ran into Supabase CLI, and tried to link my project.

What I did

I installed Supabase Cli & init Supabase:
npx supabase init
Then I generated an access token from the dashboard and logged in using it: (or without the access token, result seems the same)
npx supabase login --token sbp_xxxxxxxxxxx
And got the following message:
You are now logged in. Happy coding!

What doesn't work (yet)

I then tried to link the supabase project to my local workspace with:
npx supabase link --project-ref "$PROJECT_REF" -p "$SUPABASE_DB_PASSWORD"
(Also tried with the project ref hardwritten, without the db password and typing it after etc) and all I got was that:
Authorization failed for the access token and project ref pair: {"message":"Forbidden resource"}

Question

What did I do wrong? Is this a bug from supabase or from between the chair and the keyboard?
Thank you to all of you that will take the time to help me!

Did you supabase login?

Hello, Yes I used login, and got the message
"You are now logged in. Happy coding!"
I can't find in the docs what could go wrong. I can't link to the project,
I can't use migrations. Each time it's a Forbidden Resource message error,
I double checked my credentials.
Le dim. 7 janv. 2024 à 20:12, Xquick @.***> a écrit :

Did you supabase login?
—
Reply to this email directly, view it on GitHub
https://github.com/supabase/cli/issues/1819#issuecomment-1880145390, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AX4TOCWEWKHYGV2KSXOYOBTYNLXRLAVCNFSM6AAAAABBPRDGD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGE2DKMZZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I think we need more context to debug. Could you run supabase link --create-ticket ...? Once you've done that, share the crash id here.

Closing due to staleness.
As a last resort, you can pass in the access token via var. For eg.
SUPABASE_ACCESS_TOKEN=sbp_**** npx supabase@latest link


Bug Buffering submission

Describe the bug
When we do a submission with the buffering submission we have lost the correlation between payload and taskId.
I tested when the MaxTasksPerBuffer is greater than 1 and we have the problem.
To continue the install of 2.10 I set It to 1.
To Reproduce
given :

We have multiple payloads with unique id in each
when :
We submit these payloads with the buffering submission
Then :
We receive a task.Id for each payload
in the grid we have task.Id=1 with payload.Id=1
in the client we have task.Id=1 with payload.Id=:x:2:x:

Expected behavior
given :

We have multiple payloads with unique id in each
when :
We submit these payloads with the buffering submission
Then :
We receive a task.Id for each payload
in the grid we have task.Id=1 with payload.Id=1
in the client we have task.Id=1 with payload.Id=:heavy_check_mark:1:heavy_check_mark:

Infra

Target (Local, AWS, Docker compose, etc..) : AWS
Queue (Activemq managed or not) : Activemq managed
DataBase (MongoDB) : MongoDB
Cache (Redis managed or not) : Redis managed
Infra Version : ?
Core Images and Version (if known) : 0.8.2
Worker Image and Version (if known) : 0.8.1

Hello @landdragon,
The issue is great but can you provide a little bit more information on your use case ? I suspect that you use one of our API to submit your tasks but can you tell us which one and which functions ? Do you have some code snippets that could help us reproduce the issue on our end ?
Those new informations would greatly help us to investigate and eventually solve your issue faster.
Thank you !

I use the unified API and we use  SubmitAsync.
I didn't finish the test to reproduce it.

test.zip
my test case to reproduce it

Thanks. We will test with our potential fix today


feat(file based bank persistence)

Adding (optional) persistence for yankbank entries, through the use of a pre-specififed file
This is not adding db-based persistence
Could be expanded with minimal effort to allow project-based persistence (similar to harpoon)

Partially addresses #4

File persistence is nearly working, the only thing that needs to be added now is reading from the bank file each time the popup is opened to provide a shared bank between simultaneous vim sessions.

Final persistence implementation is exclusively using sqlite since it works really well and is quite lightweight and can easily be installed sqlite.lua


Turn off OnClick for chart legend

When i clicked the legend of my chart, it will turn off the line that i clicked. I want to know how to turn off that onclick function, because i edited the tooltip so the column is like:
{type:'datetime', label:'Date', role: 'domain'},
{type: 'number', label:'Chat Count', role: 'data'},
{type: 'string', role: 'tooltip', p: {'html': true}},
{type: 'number', label:'Chat Growth', role: 'data'},
{type: 'string', role: 'tooltip', p: {'html': true}}
when i clicked the legends, i got this error : All series on a given axis must be of the same data type

Do you mean legend_toggle={false} ?
If not can you provide some code so that I can better see what you're trying to accomplish ?

I already tried the legend_toggle={false}, but it still working when i clicked the legend
here is the code i use:
<Chart chartType="LineChart"
rows={rows} columns={columns}
options={options}
graph_id="LineChart"
legend_toggle={false}
width={"100%"}/>

So with these props, clicking on the legend, hides the line or tells you "All
series on a given axis must be of the same data type"?
On Mon, 8 Aug 2016 at 12:03 Randi Chilyon<EMAIL_ADDRESS>wrote:

I already tried the legend_toggle={false}, but it still working when i
clicked the legend
here is the code i use:
rows={rows} columns={columns}
options={options}
graph_id="LineChart"
legend_toggle={false}
width={"100%"}/>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/RakanNimer/react-google-charts/issues/61#issuecomment-238180400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABNkfQyrwcffUkm0iio7ZyFut34ZYyH-ks5qdvDXgaJpZM4Je1Rp
.

yes, that's why i want to turn off the legend toggle

Did you try listening to the select event ?

Haven't tried it. How can i do that?

Check here. And replace onmouseover with select.


Investigate and fix redhat import failure

The redhat importer is still failing after the fix at https://github.com/nexB/vulnerablecode/pull/387.
From  the logs at https://pipelines.actions.githubusercontent.com/Ep9prel8NYELDl3abhBbfgiORCbX0JuViN8i8esKzVS8DdQt5i/_apis/pipelines/1/runs/151/signedlogcontent/3?urlExpires=2021-03-24T04%3A20%3A33.2100559Z&urlSigningMethod=HMACV1&urlSignature=7VXaMaJelaCEUG6EDzDbZKLAw%2BfWbGUypuHe164RCjE%3D
It seems there is problem at https://github.com/nexB/vulnerablecode/blob/bfa005ece230ada9032c3c0b4a7bab7b59673e0b/vulnerabilities/importers/redhat.py#L93.
To fix this:
1.Find the cause of 443
2.Add a workaround on non-json response .

I'm working on it

Update: I ran the importer for 6 hours straight and it wasn't responding after the fetching.
Either the amount of advisories is so high that it's taking lot of time to actually import   (https://github.com/nexB/vulnerablecode/issues/210) or it's something else.
I'll investigate further by Monday.

Update: The root cause is abusing the server with so many requests in such a short time. The server is replying with 502: Proxy Error and sometimes with 104: Connection reset. I'm implementing a requests helper to retry with sane back-offs on such situations.
I've also mailed<EMAIL_ADDRESS>to ask if there exists any scraping restrictions in a given time.

Update: Today I woke up to this and I'm happy :D


ceph-deploy.spec: remove %{pyver} references

The %{pyver} RPM macro is not present on Red Hat-based systems. It was removed for SUSE as a part of commit 83070c14f1682e3b6eb7f45f43ba6afda6f026a4. This pull request removes it for RHEL also.
This fixes a problem where rpm -qp --requires ceph-deploy-1.5.21-0.noarch.rpm would show that the binary RPM literally required python >= %{pyver}, since RPM did not interpolate the macro to any value.

Tests passed for this pull request.
Refer to this link for build results: http://jenkins.ceph.com/job/ceph-deploy-pull-requests/1426/

:+1:


Zero fill edge case for first step in StepMap

A number with many zeros should have a minimal first step.  Detect that and flip appropriate ones.
Since this will only happen once, and on the first time, we need to avoid conditional checks continuing.  To support this I propose adding additional types for the states of Digits produced.
UnSteppedDigits & SteppedDigits seem like a good type.
May actually need a completely different situational StepMap for the UnSteppedDigits.
This will be a breaking change for next_non_adjacent to accept either a UnSteppedDigits or a SteppedDigits as input instead of a Digits instance.

Intermediary fix can be detecting max_adjacent and doing succ until the max_adjacent isn't more than allowed adjacent

When allowed 1 adjacent 0000 should become 0010, 2222 should become 2232, and 9999 should become 10010.

Better yet we can have a new field in the main struct for whether an item is stepped or not.  This will save us from needing huge changes and is close to the desired performance with only 1 added bool/state check.
Of course this assume the next_non_adjacent will continue to be called with the same allowed adjacent value.  Hmmm... that may have tricky edge cases as well.

Another alternative is to create a sanitize_for_adjacent method which does the value changes as shown above and then does a minus one so the step maps first step will be a rule fulfilling step.

next_non_adjacent should call sanitize_for_adjacent, but for performance nuts like me the current behavior in next_non_adjacent should be moved to next_step_map.  So I won't be using next_non_adjacent as there is a performance hit to calling sanitize_for_adjacent.  I'll be manually calling sanitize_for_adjacent only once and the using next_step_map myself for all following steps.


Use console rather than Ember.Logger

The use of Ember.Logger was added to deprecations in ember 3.2. This
commit replaces any Ember.Logger calls with console.
ESlint rules were updated to avoid tests to fail.
This should fix #134.
Thsi PR contains changes that were requested in https://github.com/damiencaselli/ember-cli-sentry/pull/135#discussion_r216935884 by @Turbo87.

Closes #134


Edits to NB3

It looks like there are a bunch of deletions because the cells in this version of the notebook have not been executed. My kernel kept dying, even when I deleted that bin directory, and I decided to move on.
Thanks @joshday!

Thanks for all your help, @xorJane!  I ended up merging all of your stuff manually to avoid git/notebook incompatibility issues.  Sorry to not give you the credit/git blame!


Spin up an example community currency

In order to better understand the pain points of a web3 dev we should go through a work flow that includes many steps often done by a web3 dev.  We plan to create a community currency to "feel the pain" of setting it up.  From there we can better understand how modules be improve on the experiences.
The CC will have

An admin that is protected by multi-sig
an erc20
users

Closing this out as we have decided to pivot for our first step.  I will link the new ticket below


What's the proper way to generate three endash in a row?

Seems six -s will be recognized as two emdash in a row, which is ok by itself. However, i wonder for a djot-writer, what's the proper way to write djot if three endash is instead what one's intended output?

This would work but it's awkward:
--{%%}--{%%}--

(empty comments to separate)
Or, just use unicode en-dashes.

@jgm Please consider revisit this after #112 is resolved... I'd say something like allowing user to write :endash::endash::endash: for this purpose is cleaner from the ast perspective.


fix sqlite pragma to use config setting

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
add config setting back to pragma for sqlite plugin

What is the current behavior? (You can also link to an open issue here)
sqlite plugin somehow got set back to just use hard coded WAL pragma

What is the new behavior (if this is a feature change)?
sqlite will once again use setting from plugin config, or default to WAL if no config setting specified

Other information:

Sorry if we talked about this before, but:  can we add this option to the UI since it isn't present in the base config: https://github.com/askmike/gekko/blob/develop/web/routes/baseConfig.js
because of your check this wouldn't break in the UI, but it will be hard for people to configure this (since the config.sqlite.journalMode isn't present and needs to be added).

ah yes, cant forget about the ui config! ok its done, thanks!

:+1: thanks :)


[Bug]: [ Adapter V:3.3.2 createObjects ] Error creating all states: TypeError: Cannot read properties of null (reading 'length')

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Habe von der vorherigen Version geupgraded.
Es werden Tankstellen bis Station 4 erstellt. danach kommt der fehler:
[ Adapter V:3.3.2 createObjects ] Error creating all states: TypeError: Cannot read properties of null (reading 'length') und es wird nichts mehr geparsed
EDIT: Habe es nochmal einzeln probiert... Es hängt immer ab StationID 4!
EDIT2!!!:
Scheint an der Tankstelle zu hängen:
{
"id": "0fc41d90-7a45-4d5b-8f3f-52305d365514",
"name": "OIL! Tankstelle Offenbach",
"brand": "OIL!",
"street": "Sprendlinger Landstr. 173",
"house_number": "",
"post_code": 63069,
"place": "Offenbach",
"lat": 50.0853,
"lng": 8.74583,
"isOpen": true
},
eventuell Sonderzeichen?
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Adapter version
3.3.2
Environment
- Node: 16.19.0
- npm: 8.19.3
- JS-Controller: 4.0.24
- Operating system: piOS 64bit

What browsers are you seeing the problem on?
No response
Screenshots & Log

tankerkoenig.0
2023-01-02 15:40:25.964
warn
State "tankerkoenig.0.stations.8.diesel.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.959
warn
State "tankerkoenig.0.stations.8.diesel.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.954
warn
State "tankerkoenig.0.stations.8.diesel.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.947
warn
State "tankerkoenig.0.stations.8.diesel.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.935
warn
State "tankerkoenig.0.stations.8.diesel.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.928
warn
State "tankerkoenig.0.stations.8.diesel.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.923
warn
State "tankerkoenig.0.stations.8.diesel.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.907
warn
State "tankerkoenig.0.stations.8.diesel.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.903
warn
State "tankerkoenig.0.stations.8.diesel.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.885
warn
State "tankerkoenig.0.stations.8.diesel.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.880
warn
State "tankerkoenig.0.stations.8.diesel.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.876
warn
State "tankerkoenig.0.stations.8.diesel.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.871
warn
State "tankerkoenig.0.stations.8.diesel.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.864
warn
State "tankerkoenig.0.stations.8.diesel.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.849
warn
State "tankerkoenig.0.stations.8.e10.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.844
warn
State "tankerkoenig.0.stations.8.e10.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.840
warn
State "tankerkoenig.0.stations.8.e10.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.836
warn
State "tankerkoenig.0.stations.8.e10.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.832
warn
State "tankerkoenig.0.stations.8.e10.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.825
warn
State "tankerkoenig.0.stations.8.e10.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.821
warn
State "tankerkoenig.0.stations.8.e10.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.816
warn
State "tankerkoenig.0.stations.8.e10.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.811
warn
State "tankerkoenig.0.stations.8.e10.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.807
warn
State "tankerkoenig.0.stations.8.e10.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.803
warn
State "tankerkoenig.0.stations.8.e10.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.796
warn
State "tankerkoenig.0.stations.8.e10.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.785
warn
State "tankerkoenig.0.stations.8.e10.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.773
warn
State "tankerkoenig.0.stations.8.e10.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.767
warn
State "tankerkoenig.0.stations.8.e5.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.763
warn
State "tankerkoenig.0.stations.8.e5.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.758
warn
State "tankerkoenig.0.stations.8.e5.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.754
warn
State "tankerkoenig.0.stations.8.e5.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.750
warn
State "tankerkoenig.0.stations.8.e5.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.745
warn
State "tankerkoenig.0.stations.8.e5.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.740
warn
State "tankerkoenig.0.stations.8.e5.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.735
warn
State "tankerkoenig.0.stations.8.e5.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.730
warn
State "tankerkoenig.0.stations.8.e5.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.725
warn
State "tankerkoenig.0.stations.8.e5.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.721
warn
State "tankerkoenig.0.stations.8.e5.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.717
warn
State "tankerkoenig.0.stations.8.e5.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.711
warn
State "tankerkoenig.0.stations.8.e5.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.705
warn
State "tankerkoenig.0.stations.8.e5.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.700
warn
State "tankerkoenig.0.stations.8.diesel.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.696
warn
State "tankerkoenig.0.stations.8.diesel.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.691
warn
State "tankerkoenig.0.stations.8.diesel.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.677
warn
State "tankerkoenig.0.stations.8.diesel.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.673
warn
State "tankerkoenig.0.stations.8.diesel.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.667
warn
State "tankerkoenig.0.stations.8.diesel.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.663
warn
State "tankerkoenig.0.stations.8.diesel.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.658
warn
State "tankerkoenig.0.stations.8.diesel.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.654
warn
State "tankerkoenig.0.stations.8.diesel.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.650
warn
State "tankerkoenig.0.stations.8.diesel.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.645
warn
State "tankerkoenig.0.stations.8.e10.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.639
warn
State "tankerkoenig.0.stations.8.e10.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.635
warn
State "tankerkoenig.0.stations.8.e10.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.630
warn
State "tankerkoenig.0.stations.8.e10.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.626
warn
State "tankerkoenig.0.stations.8.e10.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.622
warn
State "tankerkoenig.0.stations.8.e10.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.618
warn
State "tankerkoenig.0.stations.8.e10.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.604
warn
State "tankerkoenig.0.stations.8.e10.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.600
warn
State "tankerkoenig.0.stations.8.e10.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.596
warn
State "tankerkoenig.0.stations.8.e10.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.591
warn
State "tankerkoenig.0.stations.8.e5.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.585
warn
State "tankerkoenig.0.stations.8.e5.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.580
warn
State "tankerkoenig.0.stations.8.e5.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.575
warn
State "tankerkoenig.0.stations.8.e5.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.570
warn
State "tankerkoenig.0.stations.8.e5.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.565
warn
State "tankerkoenig.0.stations.8.e5.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.560
warn
State "tankerkoenig.0.stations.8.e5.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.556
warn
State "tankerkoenig.0.stations.8.e5.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.552
warn
State "tankerkoenig.0.stations.8.e5.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.548
warn
State "tankerkoenig.0.stations.8.e5.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.542
warn
State "tankerkoenig.0.stations.8.overrides" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.538
warn
State "tankerkoenig.0.stations.8.openingTimes" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.534
warn
State "tankerkoenig.0.stations.8.wholeDay" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.530
warn
State "tankerkoenig.0.stations.8.longitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.524
warn
State "tankerkoenig.0.stations.8.latitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.519
warn
State "tankerkoenig.0.stations.8.houseNumber" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.514
warn
State "tankerkoenig.0.stations.8.postCode" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.510
warn
State "tankerkoenig.0.stations.8.city" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.505
warn
State "tankerkoenig.0.stations.8.fullStreet" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.501
warn
State "tankerkoenig.0.stations.8.street" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.495
warn
State "tankerkoenig.0.stations.8.discount" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.492
warn
State "tankerkoenig.0.stations.8.discounted" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.487
warn
State "tankerkoenig.0.stations.8.status" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.482
warn
State "tankerkoenig.0.stations.8.station_id" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.477
warn
State "tankerkoenig.0.stations.8.name" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.386
warn
State "tankerkoenig.0.stations.7.diesel.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.380
warn
State "tankerkoenig.0.stations.7.diesel.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.375
warn
State "tankerkoenig.0.stations.7.diesel.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.370
warn
State "tankerkoenig.0.stations.7.diesel.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.366
warn
State "tankerkoenig.0.stations.7.diesel.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.362
warn
State "tankerkoenig.0.stations.7.diesel.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.358
warn
State "tankerkoenig.0.stations.7.diesel.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.352
warn
State "tankerkoenig.0.stations.7.diesel.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.348
warn
State "tankerkoenig.0.stations.7.diesel.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.343
warn
State "tankerkoenig.0.stations.7.diesel.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.339
warn
State "tankerkoenig.0.stations.7.diesel.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.334
warn
State "tankerkoenig.0.stations.7.diesel.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.329
warn
State "tankerkoenig.0.stations.7.diesel.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.324
warn
State "tankerkoenig.0.stations.7.diesel.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.319
warn
State "tankerkoenig.0.stations.7.e10.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.313
warn
State "tankerkoenig.0.stations.7.e10.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.308
warn
State "tankerkoenig.0.stations.7.e10.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.300
warn
State "tankerkoenig.0.stations.7.e10.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.295
warn
State "tankerkoenig.0.stations.7.e10.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.291
warn
State "tankerkoenig.0.stations.7.e10.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.287
warn
State "tankerkoenig.0.stations.7.e10.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.281
warn
State "tankerkoenig.0.stations.7.e10.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.277
warn
State "tankerkoenig.0.stations.7.e10.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.272
warn
State "tankerkoenig.0.stations.7.e10.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.268
warn
State "tankerkoenig.0.stations.7.e10.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.261
warn
State "tankerkoenig.0.stations.7.e10.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.256
warn
State "tankerkoenig.0.stations.7.e10.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.251
warn
State "tankerkoenig.0.stations.7.e10.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.247
warn
State "tankerkoenig.0.stations.7.e5.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.241
warn
State "tankerkoenig.0.stations.7.e5.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.235
warn
State "tankerkoenig.0.stations.7.e5.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.231
warn
State "tankerkoenig.0.stations.7.e5.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.227
warn
State "tankerkoenig.0.stations.7.e5.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.221
warn
State "tankerkoenig.0.stations.7.e5.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.215
warn
State "tankerkoenig.0.stations.7.e5.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.211
warn
State "tankerkoenig.0.stations.7.e5.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.207
warn
State "tankerkoenig.0.stations.7.e5.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.202
warn
State "tankerkoenig.0.stations.7.e5.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.196
warn
State "tankerkoenig.0.stations.7.e5.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.192
warn
State "tankerkoenig.0.stations.7.e5.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.187
warn
State "tankerkoenig.0.stations.7.e5.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.181
warn
State "tankerkoenig.0.stations.7.e5.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.176
warn
State "tankerkoenig.0.stations.7.diesel.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.173
warn
State "tankerkoenig.0.stations.7.diesel.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.169
warn
State "tankerkoenig.0.stations.7.diesel.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.163
warn
State "tankerkoenig.0.stations.7.diesel.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.159
warn
State "tankerkoenig.0.stations.7.diesel.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.155
warn
State "tankerkoenig.0.stations.7.diesel.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.150
warn
State "tankerkoenig.0.stations.7.diesel.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.145
warn
State "tankerkoenig.0.stations.7.diesel.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.141
warn
State "tankerkoenig.0.stations.7.diesel.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.136
warn
State "tankerkoenig.0.stations.7.diesel.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.131
warn
State "tankerkoenig.0.stations.7.e10.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.125
warn
State "tankerkoenig.0.stations.7.e10.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.120
warn
State "tankerkoenig.0.stations.7.e10.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.112
warn
State "tankerkoenig.0.stations.7.e10.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.106
warn
State "tankerkoenig.0.stations.7.e10.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.099
warn
State "tankerkoenig.0.stations.7.e10.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.094
warn
State "tankerkoenig.0.stations.7.e10.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.089
warn
State "tankerkoenig.0.stations.7.e10.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.084
warn
State "tankerkoenig.0.stations.7.e10.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.079
warn
State "tankerkoenig.0.stations.7.e10.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.071
warn
State "tankerkoenig.0.stations.7.e5.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.065
warn
State "tankerkoenig.0.stations.7.e5.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.060
warn
State "tankerkoenig.0.stations.7.e5.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.055
warn
State "tankerkoenig.0.stations.7.e5.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.048
warn
State "tankerkoenig.0.stations.7.e5.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.043
warn
State "tankerkoenig.0.stations.7.e5.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.038
warn
State "tankerkoenig.0.stations.7.e5.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.033
warn
State "tankerkoenig.0.stations.7.e5.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.027
warn
State "tankerkoenig.0.stations.7.e5.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.023
warn
State "tankerkoenig.0.stations.7.e5.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.018
warn
State "tankerkoenig.0.stations.7.overrides" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.012
warn
State "tankerkoenig.0.stations.7.openingTimes" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.007
warn
State "tankerkoenig.0.stations.7.wholeDay" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:25.003
warn
State "tankerkoenig.0.stations.7.longitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.999
warn
State "tankerkoenig.0.stations.7.latitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.992
warn
State "tankerkoenig.0.stations.7.houseNumber" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.987
warn
State "tankerkoenig.0.stations.7.postCode" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.982
warn
State "tankerkoenig.0.stations.7.city" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.977
warn
State "tankerkoenig.0.stations.7.fullStreet" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.973
warn
State "tankerkoenig.0.stations.7.street" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.967
warn
State "tankerkoenig.0.stations.7.discount" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.962
warn
State "tankerkoenig.0.stations.7.discounted" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.957
warn
State "tankerkoenig.0.stations.7.status" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.939
warn
State "tankerkoenig.0.stations.7.station_id" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.935
warn
State "tankerkoenig.0.stations.7.name" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.768
warn
State "tankerkoenig.0.stations.6.diesel.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.764
warn
State "tankerkoenig.0.stations.6.diesel.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.744
warn
State "tankerkoenig.0.stations.6.diesel.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.739
warn
State "tankerkoenig.0.stations.6.diesel.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.734
warn
State "tankerkoenig.0.stations.6.diesel.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.729
warn
State "tankerkoenig.0.stations.6.diesel.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.724
warn
State "tankerkoenig.0.stations.6.diesel.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.718
warn
State "tankerkoenig.0.stations.6.diesel.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.711
warn
State "tankerkoenig.0.stations.6.diesel.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.704
warn
State "tankerkoenig.0.stations.6.diesel.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.698
warn
State "tankerkoenig.0.stations.6.e10.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.694
warn
State "tankerkoenig.0.stations.6.e10.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.689
warn
State "tankerkoenig.0.stations.6.e10.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.676
warn
State "tankerkoenig.0.stations.6.e10.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.671
warn
State "tankerkoenig.0.stations.6.e10.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.666
warn
State "tankerkoenig.0.stations.6.e10.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.662
warn
State "tankerkoenig.0.stations.6.e10.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.658
warn
State "tankerkoenig.0.stations.6.e10.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.653
warn
State "tankerkoenig.0.stations.6.e10.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.648
warn
State "tankerkoenig.0.stations.6.e10.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.642
warn
State "tankerkoenig.0.stations.6.e5.minmax.combined_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.638
warn
State "tankerkoenig.0.stations.6.e5.minmax.short_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.633
warn
State "tankerkoenig.0.stations.6.e5.minmax.3rd_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.629
warn
State "tankerkoenig.0.stations.6.e5.minmax.feed_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.625
warn
State "tankerkoenig.0.stations.6.e5.minmax.lastUpdate_min" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.621
warn
State "tankerkoenig.0.stations.6.e5.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.615
warn
State "tankerkoenig.0.stations.6.e5.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.611
warn
State "tankerkoenig.0.stations.6.e5.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.604
warn
State "tankerkoenig.0.stations.6.e5.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.598
warn
State "tankerkoenig.0.stations.6.e5.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.588
warn
State "tankerkoenig.0.stations.6.overrides" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.581
warn
State "tankerkoenig.0.stations.6.openingTimes" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.575
warn
State "tankerkoenig.0.stations.6.wholeDay" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.570
warn
State "tankerkoenig.0.stations.6.longitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.565
warn
State "tankerkoenig.0.stations.6.latitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.561
warn
State "tankerkoenig.0.stations.6.houseNumber" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.556
warn
State "tankerkoenig.0.stations.6.postCode" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.551
warn
State "tankerkoenig.0.stations.6.city" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.544
warn
State "tankerkoenig.0.stations.6.fullStreet" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.539
warn
State "tankerkoenig.0.stations.6.street" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.524
warn
State "tankerkoenig.0.stations.6.discount" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.519
warn
State "tankerkoenig.0.stations.6.discounted" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.514
warn
State "tankerkoenig.0.stations.6.status" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.509
warn
State "tankerkoenig.0.stations.6.station_id" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.505
warn
State "tankerkoenig.0.stations.6.name" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.494
warn
State "tankerkoenig.0.stations.5.diesel.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.489
warn
State "tankerkoenig.0.stations.5.diesel.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.484
warn
State "tankerkoenig.0.stations.5.diesel.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.478
warn
State "tankerkoenig.0.stations.5.diesel.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.474
warn
State "tankerkoenig.0.stations.5.diesel.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.467
warn
State "tankerkoenig.0.stations.5.diesel.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.462
warn
State "tankerkoenig.0.stations.5.diesel.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.457
warn
State "tankerkoenig.0.stations.5.diesel.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.450
warn
State "tankerkoenig.0.stations.5.diesel.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.434
warn
State "tankerkoenig.0.stations.5.diesel.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.427
warn
State "tankerkoenig.0.stations.5.e10.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.414
warn
State "tankerkoenig.0.stations.5.e10.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.408
warn
State "tankerkoenig.0.stations.5.e10.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.402
warn
State "tankerkoenig.0.stations.5.e10.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.396
warn
State "tankerkoenig.0.stations.5.e10.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.388
warn
State "tankerkoenig.0.stations.5.e10.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.382
warn
State "tankerkoenig.0.stations.5.e10.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.376
warn
State "tankerkoenig.0.stations.5.e10.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.369
warn
State "tankerkoenig.0.stations.5.e10.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.361
warn
State "tankerkoenig.0.stations.5.e10.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.354
warn
State "tankerkoenig.0.stations.5.e5.minmax.combined_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.347
warn
State "tankerkoenig.0.stations.5.e5.minmax.short_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.339
warn
State "tankerkoenig.0.stations.5.e5.minmax.3rd_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.328
warn
State "tankerkoenig.0.stations.5.e5.minmax.feed_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.313
warn
State "tankerkoenig.0.stations.5.e5.minmax.lastUpdate_max" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.305
warn
State "tankerkoenig.0.stations.5.e5.combined" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.299
warn
State "tankerkoenig.0.stations.5.e5.short" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.293
warn
State "tankerkoenig.0.stations.5.e5.difference" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.286
warn
State "tankerkoenig.0.stations.5.e5.3rd" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.279
warn
State "tankerkoenig.0.stations.5.e5.feed" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.269
warn
State "tankerkoenig.0.stations.5.overrides" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.263
warn
State "tankerkoenig.0.stations.5.openingTimes" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.257
warn
State "tankerkoenig.0.stations.5.wholeDay" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.250
warn
State "tankerkoenig.0.stations.5.longitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.244
warn
State "tankerkoenig.0.stations.5.latitude" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.237
warn
State "tankerkoenig.0.stations.5.houseNumber" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.232
warn
State "tankerkoenig.0.stations.5.postCode" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.225
warn
State "tankerkoenig.0.stations.5.city" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.219
warn
State "tankerkoenig.0.stations.5.fullStreet" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.212
warn
State "tankerkoenig.0.stations.5.street" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.206
warn
State "tankerkoenig.0.stations.5.discount" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.200
warn
State "tankerkoenig.0.stations.5.discounted" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.193
warn
State "tankerkoenig.0.stations.5.status" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.188
warn
State "tankerkoenig.0.stations.5.station_id" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:24.181
warn
State "tankerkoenig.0.stations.5.name" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.739
warn
State "tankerkoenig.0.stations.8.diesel.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.732
warn
State "tankerkoenig.0.stations.7.diesel.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.725
warn
State "tankerkoenig.0.stations.6.diesel.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.716
warn
State "tankerkoenig.0.stations.5.diesel.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.681
warn
State "tankerkoenig.0.stations.8.e10.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.671
warn
State "tankerkoenig.0.stations.7.e10.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.639
warn
State "tankerkoenig.0.stations.6.e10.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.622
warn
State "tankerkoenig.0.stations.5.e10.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.574
warn
State "tankerkoenig.0.stations.8.e5.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.565
warn
State "tankerkoenig.0.stations.7.e5.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.557
warn
State "tankerkoenig.0.stations.6.e5.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.550
warn
State "tankerkoenig.0.stations.5.e5.cheapest" has no existing object, this might lead to an error in future versions

tankerkoenig.0
2023-01-02 15:40:22.207
info
Start first request

tankerkoenig.0
2023-01-02 15:40:21.203
error
[ Adapter V:3.3.2 createObjects ] Error creating all states: TypeError: Cannot read properties of null (reading 'length')

Poste mal ein Screenshot von der Station 5 in der UI

Poste mal ein Screenshot von der Station 5 in der UI

mit dieser geht es NICHT

über trage mal die Hausnummer in das richtige Feld und versuche es dann erneut

über trage mal die Hausnummer in das richtige Feld und versuche es dann erneut

das geht...

lustigerweise geht es bei der normal

probire es mal

ja klappt! vielen Dank.
wie gesagt: komischerweise geht es bei der anderen :D

Ja die stationen liefern manchmal keine hausnummer sondern "" das gibt dan probleme und mache liffern auch noch " " das geht dan

ich bin da schon dran eine Prüfung direkt beim Start einzubauen, das er dann immer eine Warnmeldung rau gibt, wo was fehlt

Perfekt Danke!
Das mit dem "" und " " gibt durchaus Sinn! VIELEN DANK vor allem für den schnellen Support


Introduces optional Graphics Extras Package

Overview
This introduces a new package: @pixi/graphics-extras to provide some convenience drawing functions for various shapes. Ideally this would've been the place where drawStar was included too.
This PR was inspired by some draw experiments I did over the past year with Graphics. I thought these would be useful as a package. I added this package as opt-in (i.e., not included in the default bundles pixi.js or pixi.js-legacy).
Demos
Regular Polygon:
https://jsfiddle.net/bigtimebuddy/rqpbnj6d/
Torus:
https://jsfiddle.net/bigtimebuddy/mzq0yLv8/
Fillet and Chamfer Rectangles:
https://jsfiddle.net/bigtimebuddy/jzsgep42/
Links
Documentation
https://pixijs.download/dev-graphics-extras/packages/graphics-extras.js

That was mentioned in many topics on forums and here

Codecov Report

Merging #6613 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6613   +/-   ##
=======================================
  Coverage   82.34%   82.34%
=======================================
  Files          38       38
  Lines        1903     1903
=======================================
  Hits         1567     1567
  Misses        336      336

Continue to review full report at Codecov.

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


'bash' is not recognized as an internal or external command, operable program or batch file.

*A brief description:
Failed to compile a simple C code (https://goo.gl/XE5QC6) through the Script package using Atom.
What I have tried after facing the error:

Installing Cygwin
Installing bash through Windows Command Prompt after enabling Developer access (type bash -> Enter); Followed this as guide: https://goo.gl/H2N10K

Error still persist.

*Expected results:
For the code to compile.
*Actual results (with terminal output if applicable):
'bash' is not recognized as an internal or external command, operable program or batch file.
(See here: https://goo.gl/b3szOj)
*Your Windows build number:
Windows 10 ver. 1607 Build 14393.576
*Steps / All commands required to reproduce the error from a brand new installation:

Install Atom
Install the [atom-beautify 0.29.16] & [script 3.14.0] packages
Obtain simple C code (https://goo.gl/cGRV80) and insert text in file in Atom
Save file as *.c file
Run Script
(If required: Install Cygwin, then this: https://goo.gl/H2N10K)

Thanks in advance.

Have you enabled the Windows optional feature?

Yes @ Windows Subsystem for Linux (Beta)
Is/are there anything else that I need to enable?

and running bash.exe from cmd gives you the 'bash' is not recognized as an internal or external command, operable program or batch file. error?  Is there a bash.exe in C:\Windows\System32?

Uh no, I can run bash @ cmd.
That error happens when I tried to compile a C code using Atom; kindly note here: http://i.imgur.com/794yJBA.png
And yes there is a bash.exe @ C:\Windows\System32

Could you please give me some more complete reproduction instructions?  How you're installing Atom, what build script you're using, etc?

*How you're installing Atom

Downloaded the Windows installer here: https://atom.io/
Installed

*what build script you're using
script 3.14.0
*etc
Sorry, could you be specific?

The actual command you are using to compile?

*The actual command you are using to compile?
https://goo.gl/cGRV80
or
#include <stdio.h>

int main()
{
  int a;

  printf("Enter an integer\n");
  scanf("%d", &a);

  printf("Integer that you have entered is %d\n", a);

  return 0;
}

Homie. It's at C:\Windows\Sysnative\bash.exe.
It's because bash is not in SysWOW64.
@benhillis you should just symlink bash.exe in SysWOW64.  This is the 8th time I've seen this Q on either here or StackOverflow.

@fpqc Mine is at C:\Windows\System32\bash.exe though. See for yourself: https://goo.gl/P12SuP
But yes, you're right, it isn't @ SysWOW64.
I'm still unsure on how symlink works. So did you mean this?

Run Command Prompt
mklink /J "C:\Windows\System32\bash.exe" C:\Windows\SysWOW64\bash.exe

@skyferia You are calling the script from a 32bit program, so bash.exe lives in C:\Windows\Sysnative. Open a 32bit command prompt and try it.

@fpqc I don't have Sysnative folder in my C:\Windows\ (see here: https://goo.gl/0h4nN9)
What exactly should I try? If you meant opening Atom and running the code: I tried with the same error as the outcome.

It is a virtual folder. It exists only from the perspective of 32 bit programs.

@Skyferia:
Since your 64-bit OS needs to be able to run 32-bit programs without confusing them with new paths, some paths are redirected to different folders depending on whether a 32-bit or 64-bit application looks at them. The same applies to some registry keys. Check out the articles about "Registry Redirector" and "File System Redirector" here to learn more.
Basically, if you open explorer (a 64-bit program), you will see these folders:
C:\Windows\System32 << your 64-bit system folder
C:\Windows\SysWOW64 << your 32-bit system folder
(Yes, the numbers appear to be exactly the other way round, for reasons too complicated to explain right now.)
However: When a 32-bit program, such as Atom, looks at your Windows folder, it will see these folders instead:
C:\Windows\System32 << your 32-bit system folder (!!!)
C:\Windows\Sysnative << your 64-bit system folder
This ensures that under the path C:\Windows\System32, all applications, be it 32 or 64 bit, will find the system files with the correct bitness which fits to the applications themselves - 64-bit applications will find 64-bit files there, file 32-bit applications will find 32-bit files there.
The way to access files with the "other" bitness (32-bit from 64-bit applications and 64-bit from 32-bit applications) is to access the C:\Windows\SysWOW64 and C:\Windows\Sysnative paths, respectively.
Because bash.exe exists only as 64-bit file, it is located in the C:\Windows\System32 folder from a 64-bit application's perspective (such as from Explorer), *but in C:\Windows\Sysnative from a 32-bit appliaction's perspective (such as from Atom).
Since C:\Windows\Sysnative is not in the path by default, you need to tell Atom to specifically look in that folder, by specifying the full path C:\Windows\Sysnative\bash.exe.
By the way, you can easily check the different perspectives by trying to explore your Windows folder from 64-bit cmd.exe (which you normally get) and also 32-bit cmd.exe which you will find in Explorer in C:\Windows\SysWOW64\cmd.exe.

Lol @CherryDT Annoying you had to write that magisterial essay.  I saw no benefit to me or him in spelling it out, but I admire your willingness to actually do fhis dirty and unforgiving work.

@fpqc: Oh, you are right, I was in a Stack Overflow mindset I guess. Sorry if this was considered spam...

@CherryDT I wasn't being sarcastic lol.

@CherryDT I don't think it's spam since you're answering the question accordingly. Thanks for that and thanks for helping me understand better. I'm not really well-versed in computing, like [tell Atom to specifically look in that folder], I do not know how to do that.
But seeing as how certain parts of my questions were ignored (such as: Plus you said this is the 8th time, then were the past 7 times with solution? If so, could you kindly link me to any one as I could not find any?), I probably have to find out how to do that on my own plus testing through trial and error.
Thanks though to you and @fpqc and @benhillis.

@Skyferia I gave you the answer I gave on SO. Change the path to bash.exe to that sysnative path.  This is because you are calling bash.exe from a 32-bit application (whatever is processing the script you're running, namely the Atom editor or one of its extensions).
Change the script to call from the sysnative path.  It will definitely work.  Please and stop demanding a further explanation.  @CherryDT has already gone to a lot of trouble to explain it, and it is also well-documented on MSDN (WOW64).

@Skyferia: About the symlink issue: You are almost right, you just need to omit /J because that's for junction points (which is for directories only), and you need to swap the order of the two paths in your command (it's linkPath targetPath, unlike Linux' ln), i.e. mklink C:\Windows\SysWOW64\bash.exe C:\Windows\System32\bash.exe - however I normally prefer not to mess with the system files because this kind of stuff can easily break during an update (or can even break the update), but maybe I'm overcautious there.

@CherryDT Yep that's why I asked the devs to add the symlink maybe.

[you evidently still have not tried it]
Yes, I have not, as I still am finding out how to direct Script's path. By your tone, I seem to have offended you. I'm so sorry for that.
@CherryDT You're really nice, thanks! Your explanations really help add more to my knowledge. About this: Wherever it is you are configuring the bash command inside Atom
Thing is, I do not know the exact 'where'. What I got so far is this (Script's configure): https://goo.gl/AqUf3A
They all are alien to me so I'm finding out based on both cross searching around the net and info you both provided. It's taking time, that was why I didn't respond sooner.

@Skyferia This isn't really a WSL question then.

Sorry for the late response.
Thanks for replying @fpqc and guiding me accordingly. Will continue with asking there then.

Write one line - fix it:
npm config set script-shell "C:\Program Files\git\bin\bash.exe"
source: https://medium.com/@dSebastien/fixing-bash-is-not-recognized-as-an-internal-or-external-command-when-used-within-npm-scripts-on-61614391e417


Backend/db restructure

This PR lays the groundwork for changes to the overall database structures and how the database works with module stores. None of the existing modules have been changed to use the system yet, but instead will be trialled with the map backend before slowly migrating others.
The main motivation for the changes are:

Make it easier to migrate away from firestore via a better 'abstract' middle database layer and consistent naming convention
Make database operations efficient in terms of what is retrieved online vs from a cache, adding Dexie as a wrapper for indexeddb to remove reliance on firestore for caching.
Provide options for caching larger queries online for efficient retrieval (e.g. all map pins) - adding firebase realtime database for now as a solution for this (or something like redis in the future).
Use a single database throughout the site instead of calling new database objects from each store
Allow stores to share information with each other in a tidier way (e.g. the current logged in user)

Changes:
package.json
Add Dexie database, which is a wrapper for the browser indexeddb database and will be used to cache data offline. Previously this had been handled by firestore's own indexeddb methods however dexie provides a lightweight, more flexible solution
src/index.ts
The way stores are injected has been modified slightly, so that instead of separate stores for every module there is one 'root' store which has all other stores within it. This makes it easier to share information between stores, or have a single database open and made available to all stores. This pattern is recommended by Mobx here: https://mobx.js.org/best/store.html

i.e., if the HowtoStore wanted to access information about the user it could request
this.rootStore.stores.userStore.user

Or access to the database would be via
this.rootStore.db

(instead of instantiating a new database object inside of every store, which get's messy when dealing with indexeddb in particular)
src/stores/...
All stores have had their constructor methods changed to allow the injection of the root store. Currently this does not change how any of the stores behave, but in the future will allow for stores to access the newer database structures
src/stores/database/index.ts
This is home to the new database system. It is not currently in use by any of the stores but will be in the future. The main index.ts file provides the database class for the platform to interact with. It sits between specific database clients (such as firestore), and offers what should be a simple and type-safe way to interact with the database. The main methods will be described in separate documentation, but consists mostly of collection and doc objects, and methods to read (once via get(), or in realtime via stream()), query or write.
An example to retrieve a list of all howTos (checking first cache and then online), and continuing to emit and cache updates as they happen would be:
db.collection('v2_howtos').stream()`

Or accessing a particular user profile would be
db.collection('v2_users').doc('chris-m-clarke').get()

Or getting a document(s) with a specific field-value, such as a howTo by slug
db.collection('v2_howtos').getWhere('slug','==','my-first-howto')

Some extra logic is in place for handling calls to cache vs live database, which again will be outlined in separate documentation
src/stores/database/types
This is the start of a better system of documentation for the overall database, so that instead of lots of inline comments a specific set of guidance and examples can be made available with code completion in vscode, or auto-generated documentation. E.g., hovering over DBClients gives more details:

src/stores/database/clients
This provides bindings for specific database clients, in a consistent way to make it easier to add different databases in the future. Currently there are bindings for firestore, firebase realtime db, and dexie.  An example for Dexie is:

(The references to T or T & IDBDoc are simply placeholders in case a user wants to specify the type of data expected at a given database endpoint (replacing T with IHowTo for example), and informing the user that they will get that type of data back with additional metadata populated by the database)
Any other databases can be added by providing similar bindings for the core CRUD methods, which are then utilised by the main Database object.
There are also a few small utils functions to help with some common logic, database initialisation etc.

The v2 stuff was all part of pull #539, where all the data had to be changed to remove firebase firestamps and replace with regular string dates. But it would definitely be worth adding some docs as to when/why you might need to do this (basically a cheap way to handle breaking changes, instead of lots of if(typeof date === 'string')... etc., easier to just have a fresh data source to work from. Its also worth mentioning how Dexie indexes work (by default firestore creates indexes on every field to allow quick searching, but dexie requires manual indexes so that data can quickly be ordered by, for example, date modified of value of the slug field)

Thanks @catx23 , not sure exactly what you mean by shortening - are we talking easy case removing the word 'store' or something else (e.g. default exports)? Or using a better system of generators to create on the fly perhaps? I've never gotten around to learning/understanding functional programming, I feel like it's a powerful paradigm but one that definitely takes a shift in mindset. I know mobx as the tool for stores/state management is built on functional programming design principles but I don't know much about architecture for pairing with functional components.... one day...

@chrismclarke , yup; as i remember; the suffix 'store' should be removed; eg: by the stores/index import; should be clear enough though.
I think I left a few links on Discord but it's all gone somehow but essentially I think it's good idea to start blending in slowly on the side (FB promotes that too), at any cost. There is lots of code you don't need to write; despite it's just script though anyways. For instance the default constructors, if you look at Angular or more recent TS code, there is no need for 'this.var = arg ? arg : default' in the constructor. I messed my code for a while like this too til they made this work without. Possibly this sort of mistakes can be avoided with a general font-end vision document ...
Anyways, peanuts & cosmetics though , keep going, just saying that around 10-30 % of the code could be removed :-)


Support RTL layout

Hi,
The ntfy Web UI is not yet supporting RTL RightToLeft. May be it could be added later for example for arabic, farsi and hebrew.
For now, the layout is LTR LeftToRight only.

This is a reasonable request.
I would assume that this involves associating a direction with a language, and then using that in all sorts of web elements like so dir={prefs.getDir()}. It doesn't seem hard, albeit a little tedious.

Hello
This is my request too, Please add RTL supporting.

ntfy automatically change direction based on language set


Keymaps are being set

I'm using the following configuration:
    use {
        'hkupty/iron.nvim',
        config = function()
            local iron = require("iron.core")
            iron.setup {
                config = {
                    should_map_plug = false,
                    scratch_repl = true,
                },
                keymaps = {}
            }
        end,
    }

It's my understanding that this should result in no keymaps being set by iron.nvim. However, according to :nmap, the following keymaps are set by iron:
n  cl            <Plug>(iron-clear)
n  cq            <Plug>(iron-exit)
n  cst           <Plug>(iron-interrupt)
n  c<CR>         <Plug>(iron-cr)
n  cp            <Plug>(iron-repeat-cmd)
n  ctr           <Plug>(iron-send-motion)

I'd like to set these myself, is this a bug, or this there a way to disable this that I missed?

Damn, i forgot to remove the vim file counterparts. I'll update it shortly

I merged the PR, should be working now. Let me know how it goes and if I should close it. Thanks

Thank you so much for the quick response, it seems to be working fine now!


Using with SPI  modules

It's possible to use this library with Lora modules (SX1276) which uses SPI protocol and not UART?

What development board are you using with that module?

I'm using Arduino Uno + RFM95

Alright, I've added this to our roadmap.
We'll look into the SX1276 and RFM95.


Add warnings for duplicate installation

Closes #3552

Now uses importlib.metadata instead of pkg_resources. Note that this check is nop for Python 3.7 or earlier.

Jenkins, test this please.

Jenkins CI test (for commit 6456a1ee550ea20e7f630e0cfeda535c60b20737, target branch master) failed with status FAILURE.

pfnCI, test this please.

Jenkins CI test (for commit 6456a1ee550ea20e7f630e0cfeda535c60b20737, target branch master) succeeded!


Remove DELETE task method

Tasks can not be deleted, once submitted. Hence, remove the DELETE task method from the Python client.
Metriq client method is here: https://github.com/unitaryfund/metriq-client/blob/3504b73e282864671e7227ad5796468872d1844d/metriq/client.py#L56

https://github.com/unitaryfund/metriq-client/pull/62


Edge fix

This pull request updates Edge download to use the currently stable version (98.0.1108.62) as the latest and fixes the download problem.

Please fix the conflicts


HBASE-25051 test to reproduce the broken auth problem

Just a UT change, used to confirm that without the changes in HBASE-25051, the UT will fail.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 17s
Docker mode activated.


Update README.md

In order not to go into package.json and read what scripts are, I updated README.md and added the necessary information.

Thanks!


Widget: Total pedestrians injuries on a specific street by injury severity and year

Name
Query for pedestrians injuries count at a specific street and by injury severity and year
Title
pedestrians injuries at _street __ , city ___ (years)
נפגעים בתאונות עם הולכי רגל ברחוב ____ , בעיר (טווח השנים)
Visualization

Visualization explanation
stacked bar chart
Use case
When this infographic should be displayed
SQL query
query on redash

Modified parameters:
street1_hebrew
street2_hebrew
accident_yishuv_name
Additional context

@DorAdam looks great!
@MichalOren can you review the query before we send this to implementation in the BackEnd? Any comments?

@DorAdam looks great!
@MichalOren can you review the query before we send this to implementation in the BackEnd? Any comments?

Hi,
1.Is this infographic is ment to be general to pedestrian severity of injury at any street and city.... or we would like to show ציר המוות and infloence of road separatior?
There is mismatch between the infographic and query results.
In the infographic years are limited to 2009-2015 the query generate results for 2008-2020

Hi,
1.Is this infographic is ment to be general to pedestrian severity of injury at any street and city.... or we would like to show ציר המוות and infloence of road separatior?
There is mismatch between the infographic and query results.
In the infographic years are limited to 2009-2015 the query generate results for 2008-2020

in the sample redash query:

where accident_yishuv_name  like {{yishuv name}}  and injured_type = 1 and (street1_hebrew like {{street name}} or street2_hebrew like {{street name}}) parameter representing a street name: "street name".
However, in the specification of "Modified parameters" there exist 2 parameters: street1_hebrew and street2_hebrew. Which is it?
2. invoking the API request: I've found the following API request to actually invoke InjuredAccidentsWithPedestriansWidget: http://localhost:8080/api/infographics-data?news_flash_id=1&street1_hebrew="a"&street2_hebrew="a"&accident_yishuv_name="a"&road_segment_name="a", but it seems more of a hack and resulted in various failures along the way. The question is, how is this API request supposed to be invoked in production?


Announcing a data migration solution from Elasticsearch to OpenSearch latest version and OpenSearch Serverless

Describe the blog post your would like to write
A clear and concise description of what subject the blog post will cover.
What is the title of the blog post?
Who are the authors?
@kartg @setiah
What is the proposed posting date?
Provide the date which you wish this post to go live

Hello @setiah - let us know when you have a draft CC: @pajuric

@setiah @kartg - Checking to see when you might have a draft of this ready for review? Please advise.

@pajuric the draft for this one would be available around mid-october near the time for release.

@setiah - Please provide an update regarding the blog draft.

@setiah @dagneyb  - Please provide an update re when this draft will be ready to publish.

@sumobrian - reassigning this blog to you per our discussion. If you'd like to tweak the title or content, please feel free. Just let me know what time frame you'd need to publish.

Closing this for now. Please reopen @sumobrian if you plan to go forward with this blog.


Update marathon.sh

Alephone changed the app name of Marathon from Marathon.app to "Classic Marathon.app". This addresses #1495
Log attached of the output of sudo utils/assemble.sh marathon DEBUG=0
marathonlog.txt

Thank you!


[BUG] Rancher installation using helm instead of docker fails in ipxe-examples

Describe the bug
The new feature which was introduced by https://github.com/harvester/ipxe-examples/pull/80 seem not to work. Before that change i was able to setup several clusters successfully.
TASK [install Rancher v2.8.2] **********************************************************************************************************************************************************
fatal: [localhost]: FAILED! => changed=true
  cmd: |-
    vagrant up rancher
  delta: '0:00:31.769079'
  end: '2024-03-20 13:04:54.623567'
  msg: non-zero return code
  rc: 1
  start: '2024-03-20 13:04:22.854488'
  stderr: |-
    Ansible failed to complete successfully. Any error output should be
    visible above. Please fix these errors and try again.
  stderr_lines: <omitted>
  stdout: |-
    Bringing machine 'rancher' up with 'libvirt' provider...
    ==> rancher: Checking if box 'generic/debian10' version '4.3.12' is up to date...
    ==> rancher: Creating image (snapshot of base box volume).
    ==> rancher: Creating domain with the following settings...
    ==> rancher:  -- Name:              vagrant-pxe-harvester_rancher
    ==> rancher:  -- Description:       Source: /home/vot/git/ipxe-examples/vagrant-pxe-harvester/Vagrantfile
    ==> rancher:  -- Domain type:       kvm
    ==> rancher:  -- Cpus:              2
    ==> rancher:  -- Feature:           acpi
    ==> rancher:  -- Feature:           apic
    ==> rancher:  -- Feature:           pae
    ==> rancher:  -- Clock offset:      utc
    ==> rancher:  -- Memory:            4096M
    ==> rancher:  -- Base box:          generic/debian10
    ==> rancher:  -- Storage pool:      default
    ==> rancher:  -- Image(vda):        /var/lib/libvirt/images/vagrant-pxe-harvester_rancher.img, virtio, 128G
    ==> rancher:  -- Disk driver opts:  cache='default'
    ==> rancher:  -- Graphics Type:     vnc
    ==> rancher:  -- Video Type:        cirrus
    ==> rancher:  -- Video VRAM:        256
    ==> rancher:  -- Video 3D accel:    false
    ==> rancher:  -- Keymap:            en-us
    ==> rancher:  -- TPM Backend:       passthrough
    ==> rancher:  -- INPUT:             type=mouse, bus=ps2
    ==> rancher: Creating shared folders metadata...
    ==> rancher: Starting domain.
    ==> rancher: Domain launching with graphics connection settings...
    ==> rancher:  -- Graphics Port:      5904
    ==> rancher:  -- Graphics IP:        <IP_ADDRESS>
    ==> rancher:  -- Graphics Password:  Not defined
    ==> rancher:  -- Graphics Websocket: 5704
    ==> rancher: Waiting for domain to get an IP address...
    ==> rancher: Waiting for machine to boot. This may take a few minutes...
        rancher: SSH address: <IP_ADDRESS>:22
        rancher: SSH username: vagrant
        rancher: SSH auth method: private key
        rancher:
        rancher: Vagrant insecure key detected. Vagrant will automatically replace
        rancher: this with a newly generated keypair for better security.
        rancher:
        rancher: Inserting generated public key within guest...
        rancher: Removing insecure key from the guest if it's present...
        rancher: Key inserted! Disconnecting and reconnecting using new SSH key...
    ==> rancher: Machine booted and ready!
    ==> rancher: Setting hostname...
    ==> rancher: Configuring and enabling network interfaces...
    ==> rancher: Running provisioner: ansible...
    Vagrant gathered an unknown Ansible version:

    and falls back on the compatibility mode '1.8'.

    Alternatively, the compatibility mode can be specified in your Vagrantfile:
    https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
        rancher: Running ansible-playbook...

    PLAY [Setup Rancher] ***********************************************************

    TASK [Gathering Facts] *********************************************************
    ok: [rancher]

    TASK [setup k3s] ***************************************************************
    fatal: [rancher]: FAILED! => changed=false
      msg: 'Unsupported parameters for (ansible.legacy.command) module: warn. Supported parameters include: _raw_params, _uses_shell, argv, chdir, creates, executable, removes, stdin, stdin_add_newline, strip_empty_ends.'

    NO MORE HOSTS LEFT *************************************************************

    PLAY RECAP *********************************************************************
    rancher                    : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0
  stdout_lines: <omitted>

PLAY RECAP *****************************************************************************************************************************************************************************
localhost                  : ok=26   changed=8    unreachable=0    failed=1    skipped=3    rescued=0    ignored=0

To Reproduce
Steps to reproduce the behavior:
Check out latest main branch, enable Rancher installation in settings.yml and run ./setup_harvester.sh.
Expected behavior
It should work :-)
Support bundle

Environment

OS: Ubuntu 23.10
Vagrant 2.4.1
Installed Ansible

$ dpkg -l | grep ansible
ii  ansible                                       7.7.0+dfsg-1                               all          Configuration management, deployment, and task execution system
ii  ansible-core                                  2.14.9-2                                   all          Configuration management, deployment, and task execution system

Close alongside with https://github.com/harvester/ipxe-examples/pull/81.
Test run pass.


bad image links

Description
image is internal

after

Page URL
https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-9.0?branch=main&branchFallbackFrom=pr-en-us-31789&view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-9.0.md
Document ID
4e75ad25-2c3f-b28e-6a91-ac79a9c683b6
Article author
@Rick-Anderson

Fixed in #31794


[DNM] Make notes.user_id column not nullable

Do not merge - Needs out of hours deployment
This migration locks the notes table when applying the column change. It's not a table with frequent writes but deployment should be done out of hours as a precaution.
Context
The association of Notes to users should mean that notes.user_id cannot be null in the db.
We need to add this db constraint.

Changes proposed in this pull request

Adds a check constraint on notes.user_id and validates it
Changes column notes.user_id to NOT NULL
Removes the check constraint

Guidance to review
Please run this migration locally to ensure it does what we expect.

Link to Trello card

Things to check

[x] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

update: feel free to merge, not a blocker to use AR methods