add databases interface to IDBFactory

Search Terms
indexDB
types
Suggestion
I would like to add to the IDBFactory interface the databases function
Use Cases
I was encountering an issue when I wanted to delete all the existing indexedDBs on my client application. For instance, if the user signs out, I want delete all the data and I don't want to hard code the name of the databases in the code. So I did something like this:
    const dbKeys = await (window.indexedDB as any).databases();
    for (let key of dbKeys) {
      indexedDB.deleteDatabase(key.name);
    }

Examples
in lib.dom.d.ts:
interface IDBFactory {
...
databases(name: string): IDBDatabase[];
}

interface IDBDatabase {
name: string;
version: number;
}

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

At this time, this feature seems to be an Editors Draft in w3c.
https://w3c.github.io/IndexedDB/#factory-interface
I'm not sure whether we should introduce it yet.
@RyanCavanaugh
What is the consensus on this?

According to this guidline

If it's at Working draft the additions available in all three of Firefox, Safari and Chromium

this feature isn't supported in FireFox yet, so it doesn't seems to be ready for adding it.

what about a @warning flag? Firefox might add it in the future?

Do you mean using JSDoc comment like this?
/** @warning: hello */
interface A{

}

I haven't seen declaring type in such way at lib.dom.d.ts.
Well, adding types from https://w3c.github.io/IndexedDB and creating a PR won't be such an  effort (10min will do), though I'm not sure they will accept it.

Changes to this repo can have pretty drastic ecosystem effects, because these types are included by default in TypeScript. Due to this, we tend to be quite conservative with our approach to introducing changes.
https://github.com/microsoft/TSJS-lib-generator#what-are-the-typescript-teams-heuristics-for-prs-to-the-dom-apis

yes like JSDoc. Of course if you not doing it like that, then we shouldn't use it like that.
I will create an issue and PR for that in the w3c repo.

Why do you have to create an issue in the w3c repo?
Editor’s Draft for Indexed Database API 3.0 (which includes implementation of IDBFactory#databases) already exists.
https://w3c.github.io/IndexedDB/#factory-interface
The only thing we have to do is to just wait for the Draft to be published as Candidate recommendation or the browsers implementation(FireFox and safari).
Or, if the TS team think this feature can be added to the lib.dom.d.ts even it is in Draft stage.

ah okay sorry, I misinterpreted your comment!

This got added

Yep, thanks; this is done.


Process the URI schemes properly

Schemes like http:// or https:// are being ignored completely by preparePath.
Let's try to fix it up by including a list of schemes.

If x-fragment has cross-origin src, we have a problem with sources in x-fragment files. We must set src with URL schemes and origins.


Cannot reset database because "supabase db reset" tries to possibly drop types in wrong order

Describe the bug
We cannot reset the database of our Supabase testing instance:
npx supabase db reset --linked --debug --create-ticket
Using connection pooler: postgres://...
Supabase CLI 1.163.2
Do you want to reset the remote database? [y/N]
y
Resetting remote database...

...

2024/04/24 13:31:55 PG Recv: {"Severity":"NOTICE","SeverityUnlocalized":"NOTICE","Code":"00000","Message":"truncate cascades to table \"mfa_amr_claims\"","Detail":"","Hint":"","Position":0,"InternalPosition":0,"InternalQuery":"","Where":"SQL statement \"truncate auth.sessions restart identity cascade\"\nPL/pgSQL function inline_code_block line 44 at EXECUTE","SchemaName":"","TableName":"","ColumnName":"","DataTypeName":"","ConstraintName":"","File":"tablecmds.c","Line":1826,"Routine":"ExecuteTruncateGuts","UnknownFields":null}
2024/04/24 13:31:55 PG Recv: {"Type":"ErrorResponse","Severity":"ERROR","SeverityUnlocalized":"ERROR","Code":"2BP01","Message":"cannot drop type our_enum_type[] because type our_enum_type requires it","Detail":"","Hint":"You can drop type our_enum_type instead.","Position":0,"InternalPosition":0,"InternalQuery":"","Where":"SQL statement \"drop type if exists public._our_enum_type cascade\"\nPL/pgSQL function inline_code_block line 64 at EXECUTE","SchemaName":"","TableName":"","ColumnName":"","DataTypeName":"","ConstraintName":"","File":"dependency.c","Line":828,"Routine":"findDependentObjects","UnknownFields":null}
2024/04/24 13:31:55 PG Recv: {"Type":"ReadyForQuery","TxStatus":"I"}
2024/04/24 13:31:55 PG Send: {"Type":"Terminate"}
ERROR: cannot drop type our_enum_type[] because type our_enum_type requires it (SQLSTATE 2BP01)

Our theory so far is, that the order in pg_type is responsible for this problem.
This is the part of the code which is executed by supabase db reset to drop all types:
for rec in
    select *
    from pg_type t
    where t.typnamespace::regnamespace::name = 'public'
loop
    execute format('drop type if exists %I.%I cascade', rec.typnamespace::regnamespace::name, rec.typname);
end loop;

When we just executed the select part of this statement:
select *
from pg_type t
where t.typnamespace::regnamespace::name = 'public'
AND t.typname LIKE '%our_enum_type%'

We found out that the order is different in our production, testing and local setup.
In production:

oid
typname
typsubscript
typelem
typarray

54252
our_enum_type
-
0
54251

54251
_our_enum_type
array_subscript_handler
54252
0

And in local:

oid
typname
typsubscript
typelem
typarray

17960
our_enum_type
-
0
17959

17959
_our_enum_type
array_subscript_handler
17960
0

But in testing:

oid
typname
typsubscript
typelem
typarray

204381
_our_enum_type
array_subscript_handler
204382
0

204382
our_enum_type
-
0
204381

(I omitted all columns I thought were not significant to this problem.)
In production and local the enum type our_enum_type comes before its array type. In testing the order is reversed.
We think that this might the root of the problem.
Therefore, a possible fix could be to specify the order when dropping the types:
for rec in
    select *
    from pg_type t
    where t.typnamespace::regnamespace::name = 'public'
    -- For example: order by t.typname DESC
    -- Or: order by t.typarray DESC
loop
    execute format('drop type if exists %I.%I cascade', rec.typnamespace::regnamespace::name, rec.typname);
end loop;

System information

Ticket ID: 7118bdd272ec476c9c08eb8ce9f759ae
Version of CLI: v1.163.2

I agree with your analysis. Ordering is indeed a problem. If you want to submit a PR, I'd be happy to merge it.

@sweatybridge, thanks for the quick feedback. Here is the PR with our proposed fix: https://github.com/supabase/cli/pull/2208

Could you also report the postgres version of your production and testing projects? I just want to rule out the possibility of version mismatch.

Production: Postgres version <IP_ADDRESS>
Testing: Postgres version <IP_ADDRESS>
This is the migration for the enum type:
CREATE TYPE our_enum_type AS ENUM ('a', 'b');

CREATE TABLE "public"."scan_configuration"
(
    "id" UUID DEFAULT "gen_random_uuid"() NOT NULL,
...
    "enum_type" our_enum_type NOT NULL,
...

    PRIMARY KEY ("id")
);

The type is not used in any other table, in no function, in no RLS policy, ...

Ic, thanks for clarifying. It seems like the underscore type is always created as a base type, which we can filter out with where typtype != 'b'.
It is not possible for users to create a base type on Supabase because it requires superuser. Hence, there's also no need to drop a base type.
The fourth form of CREATE TYPE creates a new base type (scalar type). To create a new base type, you must be a superuser. (This restriction is made because an erroneous type definition could confuse or even crash the server.)

Thank you @sweatybridge, the problem is fixed in the latest release v1.163.4


Fix handling nonvoid elements in markup blocks

Fixes #1186

@rynowak Please let me know if I'm misunderstanding how this should work. I think the self-closing logic from before was intended to shorten the markup rather than being fundamentally necessary.

Seems fine- and yes treating at as self-closing was an important detail


0.57.0 update appears to break python script providers

Hello, after upgrading to 0.57.0, both myself and a colleague with a completely different setup are seeing the following error when running test files which contain an external python provider:
 property 'parent' closes the circle
Stack Trace: TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'DerivedLogger'
    |     property '_readableState' -> object with constructor 'ReadableState'
    |     property 'pipes' -> object with constructor 'Console'
    --- property 'parent' closes the circle
    at JSON.stringify (<anonymous>)
    at runPython (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/python/wrapper.js:29:58)
    at PythonProvider.callApi (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/providers/pythonCompletion.js:40:59)
    at async Evaluator.runEval (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/evaluator.js:277:28)
    at async processEvalStep (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/evaluator.js:593:25)

Error: Error running Python script: Converting circular structure to JSON
    --> starting at object with constructor 'DerivedLogger'
    |     property '_readableState' -> object with constructor 'ReadableState'
    |     property 'pipes' -> object with constructor 'Console'
    --- property 'parent' closes the circle
Stack Trace: TypeError: Converting circular structure to JSON
    --> starting at object with constructor 'DerivedLogger'
    |     property '_readableState' -> object with constructor 'ReadableState'
    |     property 'pipes' -> object with constructor 'Console'
    --- property 'parent' closes the circle
    at JSON.stringify (<anonymous>)
    at runPython (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/python/wrapper.js:29:58)
    at PythonProvider.callApi (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/providers/pythonCompletion.js:40:59)
    at async Evaluator.runEval (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/evaluator.js:277:28)
    at async processEvalStep (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/evaluator.js:593:25)
    at runPython (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/python/wrapper.js:47:15)
    at PythonProvider.callApi (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/providers/pythonCompletion.js:40:59)
    at async Evaluator.runEval (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/evaluator.js:277:28)
    at async processEvalStep (/Users/alexclaydon/.nvm/versions/node/v21.7.3/lib/node_modules/promptfoo/dist/src/evaluator.js:593:25)
---

We're both using v21 Node - myself 21.7.3 and him 21.5.
Confirmed that rolling back to 0.56.0 fixes it for both of us!
Please let me know if this is reproducible for you and, if so, whether there's any additional information I can provide?
Cheers

Thanks for flagging, I have an idea why this may be happening. Probably #748

Fixed in 0.57.1!

Amazing - thank you so much for the incredible pace!


Data Annotation: duration

Discussed in https://github.com/blacksmithgu/obsidian-dataview/discussions/533

Originally posted by AtlacatlQ October 11, 2021
I'm trying to create an sleep tracker using the duration type as a "sleep" field, so i would like to know if:

can I combine different units of time in the same field?
Is there any method to work with durations or are planned for a future release?

I.e., allow parsing of "4 minutes 2 seconds" or "4 minutes, 2 seconds".


[FLINK-12736][coordination] Release TaskExecutor in SlotManager if no slot allocations after partition check

What is the purpose of the change
The ResourceManager looks out for TaskManagers that have not had any slots allocated on them for a while, as these could be released to safe resources. If such a TM is found, the RM checks via an RPC call whether the TM still holds any partitions. If no partition is held then the TM is released. However, in the RPC callback no check is made whether the TM is actually still idle. In the meantime a slot could have been allocated on the TM. Even if the slot has been freed, there can be newly allocated partitions not included in check result.
To make sure there was no resource allocation in between, we can mark the taskManagerRegistration.getIdleSince() time before starting the async 'no partition' check. The TM can be released only if the idle time after the check matches the previously marked one. Otherwise we discard the release and start over after the next timeout.
Brief change log

mark the TM idle time before canBeReleased check in SlotManager.checkTaskManagerTimeouts
check it after the canBeReleased check and release only if it coincides
modify SlotManagerTest.testTaskManagerNotReleasedBeforeItCanBe to check that TM is not released if there was allocation between triggering of canBeReleased check and completing it

Verifying this change
run SlotManagerTest.testTaskManagerNotReleasedBeforeItCanBe
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

@flinkbot attention @tillrohrmann

CI report for commit 9652eea4452fac16a48d2225b9fef2d492f2b36f: FAILURE Travis

Thanks for the review @tillrohrmann, I addressed the comments


Fix Invisible/Disappearing Parameters in GUI

The new graph subscription mechanism until now only observed actual parameter value changes and passed them to subscribers. This left out the set of parameter state changes regarding GUI visibility, implemented in the AbstractParamPresentation struct and used within the AbstractParam.
This PR moves the AbstractParamPresentation from a base class of the AbstractParam to a member variable, routing previously direct access to GUI presentation state of parameters through the accessor function AbstractParam.GuiPresentation() which in turn triggers the internal observer/callback function to notify the graph and subsequently subscribers like the frontend GUI not only of parameter value changes, but also of parameter GUI state changes (e.g. visibility).
AbstractParam.GuiPresentation() notifies graph subscribers when the parameter is non-const, while AbstractParam.GuiPresentation() const avoids triggering the subscriber callback to prevent a feedback loop inside the GUI code, when the GUI retrieves the GUI presentation state of a parameter. For this, access to the parameter presentation in the GUI is now guarded using const variables.
This is a breaking change which forces us to adjust parameter GUI visibility code in the whole code base, like this:
parameter_ptr->SetGUIVisibility(true); // old
parameter_ptr->GuiPresentation().SetGUIVisibility(true); // new

parameter_ptr->IsGUIVisible(); // old
parameter_ptr->GuiPresentation().IsGUIVisible(); // new

Summary of Changes

Move AbstractParamPresentation to AbstractParam gui_presentation member variable
Acces to gui_presentation through AbstractParam.GuiPresentation() triggers graph subscriber callback
Guard access to param presentation in GUI Service with const
Search+Replace parameter GUI state setter/getter use in code base according to new access method
Leave parameters in probe plugin untouched, breaking compilation of this plugin

Test Instructions
Load testspheres.lua and ensure that different render modes of sphere renderer are represented in different visibility of paramters in GUI.

/format


Incompatible with Paladin's Furniture oven & stove, also the Minecraft smoker

Describe the bug
If you place a oven or stove from Paladin's Furniture, open it via right click and then click on the recipe book, the game instantly crashes.
The normal furnace from MC did not has this behavoir, but the smoker also has!
Expected behavior
Normal open menu and expand recipe book, without crashing the game ;)
Logs
latest.log
crash-2023-04-30_20.25.58-client.txt
Environment:

Minecraft Version [1.19.3]
Fabric API fabric-api-0.76.1+1.19.3.jar
Mod Loader 0.14.19

Mods installed:
Cloth Config API (Fabric/Forge)
shedaniel
cloth-config-9.0.94-fabric.jar
Recipe Book is Pain
melontini
recipe-book-is-pain-0.9.2-1.19.3.jar
Paladin's Furniture
UnlikePaladin
paladin-furniture-mod-1.1.3-fabric-mc1.19.3.jar

The version recipe-book-is-pain-0.9.0-1.19.3.jar seems not having this problem with the Paladin's Funiture mod in my test profile, with only the few mods shown above active. In my main world with many, many mods, this version directly crashes MC at startup time, there just the latest version of your mod is able to start MC.

Fixed in latest CrackerUtil [CurseForge / Modrinth]
You can either install it separately or wait until I update RBIP.

Thanks for quick fixing!

The updated version of RBIP is out 🎉 thnx for fixing!


Write the instrument usage tutorial

Please check that this documentation improvement hasn't been requested before

[X] I searched previous documentation improvement requests here or here and didn't find any similar requests.

Documentation enhancement description
I haven't written the tutorial yet, but I needed to get the sequence of images comprising the tutorial embedded quickly for a lesson today. Need to complete it properly:
Possible solution

Embed images properly as figures with captions
Annotate images
Add alt text to each image
Caption each image
Write narrative tutorial

Still need to finish the data export section...

This is done now, and PDF export is working as well.


Failed to connect to ip address

I have tried several times with different IP addresses but still this problem is occurring.
After that I tried with the IP address of my mobile phone, yet this problem is occurring.
I scanned the IP address with the Nmap tool, the IP address is live as you can see in the picture

Congrats your device is not Vulnerable 😂😂😂

The first thing that you read the question carefully, I have said that, I used many IP addresses, I did not try only on my device
i also used many  ip addresses from shadon, who is live, please don't close the case without understanding the question
I have tried on atleast 28 plus IP addresses that means no one devices is is vulnerable?

I totally got the question right.. i was messin with you. I think you need to dig deep.

check your 5555 open port that is open or not .

check your 5555 open port that is open or not .

how will you check if its open


chore(deps): upgrade jenkins-x/jx3-versions to version 1.1.14

from: https://github.com/jenkins-x/lighthouse.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign ccojocar
You can assign the PR to them by writing /assign @ccojocar in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


get and set null on default values, because atldotnet handles "empty" values different

The method GetMetadataPropertyValue should return null, if the value contains the default value, because atldotnet handles it like this but it would be more accurate, if null is used for an unset metadata value.
See https://github.com/sandreas/DotnetLibAudioMetadata/blob/f32f10596a80aeb1e921aa56e3689e7077ebc280/Sandreas.AudioMetadata/AudioMetadata/IMetadataExtensions.cs#L101
This has to be verified, maybe this has unwanted side effects.

Default value for string is "", but the value could also contain a WANTED empty string
Same applies for int (0) etc.

FYI, ATL.Track has two ways of handling non-string values :

Using default values when the value is unset (0 for numbers and DateTime.MinValue for dates) (default behaviour)
Using null when the value is unset (optional behaviour; needs Settings.NullAbsentValues = true)

See https://github.com/Zeugma440/atldotnet/issues/109 and https://github.com/Zeugma440/atldotnet/releases/tag/4.01
Making strings nullable following the same switch should be easy enough. Let me know if that could help.

FYI, ATL.Track has two ways of handling non-string values :

Thank you very much...  I wish, I knew this before :-) This is something, I will definetely take advantage of in the future... I bet it was because <nullable> was not a thing in the days atldotnet started?
As I already said... I think:

absent values should always be null and existing values should be read as is
Same for writing values... null means: remove this value, if mandatory by spec, use default

I'm currently working on tonehub, a Web API that should allow audio indexing and streaming (similar to audiobookshelf but way less features). At the moment I'm handling this with this (IsEmpty).

See https://github.com/sandreas/tonehub/blob/main/tonehub/Metadata/AudioHashBuilder.cs
And https://github.com/sandreas/tonehub/blob/6c5dc7196aa49192a984b81052d02db85e82f9b8/tonehub/Metadata/HashBuilderBase.cs#L15


[SPARK-30902][SQL] Default table provider should be decided by catalog implementations

What changes were proposed in this pull request?

When CREATE TABLE SQL statement does not specify the provider, leave it to the catalog implementations to decide.
Why are the changes needed?

It's super weird if we set the default provider to parquet when creating a table in a JDBC catalog.
Does this PR introduce any user-facing change?

Yes, v2 catalog will not see a "provider" property in table properties if it's not specified in CREATE TABLE SQL statement. V2 catalog is new in 3.0.
How was this patch tested?

new tests

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23475/
Test PASSed.

cc @brkyvz @rdblue @imback82 @HyukjinKwon

Test build #118724 has started for PR 27650 at commit 06cb4bb.

Test build #118724 has finished for PR 27650 at commit 06cb4bb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118724/
Test PASSed.

cc @viirya as well

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23536/
Test PASSed.

Test build #118784 has started for PR 27650 at commit f724968.

Test build #118784 has finished for PR 27650 at commit f724968.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/118784/
Test FAILed.

retest this please

Test build #119011 has started for PR 27650 at commit f724968.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23758/
Test PASSed.

Test build #119011 has finished for PR 27650 at commit f724968.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119011/
Test FAILed.

retest this please

Test build #119032 has started for PR 27650 at commit f724968.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23779/
Test PASSed.

Test build #119032 has finished for PR 27650 at commit f724968.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119032/
Test FAILed.

Test build #119047 has started for PR 27650 at commit 6685dc5.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23793/
Test PASSed.

Test build #119047 has finished for PR 27650 at commit 6685dc5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119047/
Test PASSed.

Merged to master and branch-3.0.


images: Fixes compose with custom packages when no custom repositories.

Fixes # THEEDGE-2144
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I run go fmt ./... to check that my code is properly formatted
[X] I run go vet ./... to check that my code is free of common Go style mistakes
[X] I run make lint to prints out coding style mistakes and fix them

/retest

/retest

/retest

/retest

Test results are available in Ibutsu. The test run IDs are:
f9690e69-cb01-4ccb-9b81-ea657606baa8
fc3b516f-2732-426c-bd38-a41ad0338f7f

/retest

/retest

@Mergifyio refresh

@Mergifyio rebase

/retest

@Mergifyio refresh

close PR to reopen the same because of ci.int.devshift.net problem


PageTests don't seem to work

Hi, I copied the two tests from PageTests.cs to a standalone executable for testing purposes, but query selector returns no results for some strange reason.
async static void RunScriptSelectorTest()
{
    var url = "http://html5test.com"; // same URL as in the test
    var sel = "#score > .pointsPanel > h2 > strong"; // same valid selector path as in the test
    var config = Configuration.Default
                .WithCss()
                .WithJavaScript()
                .WithDefaultLoader(setup => setup.IsResourceLoadingEnabled = true);
    var document = await BrowsingContext.New(config).OpenAsync(url);
    var elements = document.QuerySelectorAll(sel);
    // but no results (elements.Length is zero),
    // even though given selector has one match
}

Any ideas on what might be going wrong, as compared to the passing tests?

Yes, the JavaScript part is not executing correctly. However, the exact reason is unknown. I doubt its something language specific, rather some part of the DOM model is missing.
If you would find out what the exact problem is that would be super awesome. But be aware that debugging this will be quite hard, as with most other JS part.
You'll basically need to open up the JavaScript files used by HTML5Test and add parts one-by-one (first in larger blocks, then in smaller chunks to drill down). I've done it a couple of times for jQuery (e.g., previously jQuery 2.x worked fine while jQuery 1.x didn't - it turned out that jQuery 1.x needed CSS to be loaded) and it always was quite a pain.

Currently identified (i.e., potential) sources of the problem: #7, #12, #15, #21 #26.

Tried a few simpler local test pages with inline as well as external JS, and it seems to work in most cases, so it looks like the issue occurs with larger, more complex JS parsing and/or execution (by Jint maybe?).
I'll try to look into it further.

Well, I trust Jint so far that (since Sebastion also included a lot of ES5 official tests) I would rather see the problem in AngleSharp / AngleSharp.Scripting. After all the DOM is not complete (e.g., we have no renderer), where complete means: in the state where browsers use it. If a (JS) library author assumes he is working against "the browser" it may easily come to a conflict.
Yes, in small snippets this is usually no problem, but the larger chunks where lots of things happen are not as stable as I wish they would be.
I am currently finishing some other projects to get some more spare time such that I can come back to AngleSharp Scripting. I will try to implement #7 soon.

(I doubt that #7 will fix this issue, but its required sooner or later anyway; so any help from you on this issue would be greatly appreciated!)


add rating feature and leaderboard feature. Now after each match a ra…

…ting will be calculated for each player

So is this finished? Whats the status?

I fixed the issues on the commits. It should be ok, now, but waiting for @ark120202

@ark120202 all the changes are done now

@ark120202 I fixed the merge conflicts as well. The branch is ready to be merge.

(I have re-did the merge to keep it a single commit)


Allow editing of settings.toml

It looks like there is a function to define all dot files as text.  I assume to accommodate the previous .env web workflow configuration.
https://github.com/circuitpython/web-editor/blob/c36188587b5e4d46c985439676e86e2a879f4413/assets/js/common/file_dialog.js#L70
https://github.com/circuitpython/web-editor/blob/c36188587b5e4d46c985439676e86e2a879f4413/assets/js/common/file_dialog.js#L64-L66
Since .env files have been replaced with settings.toml, should the web editor have toml added to extensionMap and dot files removed?

Yes for sure on the .toml and probably yes on removing dot files.


This happened in the End, all loot as a result rolled without any affixes, just vanilla enchants.
During server startup these messages also show up, but I haven't been able to figure out how to fix them.
[23Oct2023 14:02:06.681] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category helmetRequired: 3; Provided: 2
[23Oct2023 14:02:06.681] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category bootsRequired: 3; Provided: 2
[23Oct2023 14:02:06.685] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category bowRequired: 5; Provided: 4
[23Oct2023 14:02:06.685] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category crossbowRequired: 5; Provided: 4
[23Oct2023 14:02:06.686] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category pickaxeRequired: 5; Provided: 4
[23Oct2023 14:02:06.686] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category shovelRequired: 5; Provided: 4
[23Oct2023 14:02:06.687] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category shieldRequired: 5; Provided: 4
[23Oct2023 14:02:06.688] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category helmetRequired: 4; Provided: 2
[23Oct2023 14:02:06.688] [main/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category bootsRequired: 4; Provided: 2
Originally posted by @DarkSolus in https://github.com/Shadows-of-Fire/Apotheosis/issues/682#issuecomment-1775771697
P.S. Rare, Uncommon and Common affixes generate as normal, only Mythic affixes are affected.

Have you modified anything via datapack or is this a stock installation?

Have you modified anything via datapack or is this a stock installation?

No datapacks modifying Apotheosis, no. I also reset the adventure.cfg config file just in case, however, that did not resolve the loot errors.

I think a few more affixes need to be added to certain pools, but this isn't a fatal error.

This issue seems to be causing people to crash in my server. We get logged out when getting close to a spell scroll from Iron's spellbooks.
This appears shortly after in the server console:
[INFO] .... [minecraft/MinecraftServer]: Louie365 left the game
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:uncommon/STAT/0.45!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:uncommon/STAT/0.45!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/STAT/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/ABILITY/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/STAT/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/ABILITY/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:uncommon/STAT/0.45!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/STAT/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/ABILITY/1.0!
[INFO] .... [minecraft/ServerLoginPacketListenerImpl]: com.mojang.authlib.GameProfile@2c03d69c[id=,name=Louie365,properties={},legacy=false] (/<IP_ADDRESS>:58890) lost connection: Disconnected
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:uncommon/STAT/0.45!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:uncommon/STAT/0.45!
[INFO] .... [minecraft/ServerLoginPacketListenerImpl]: UUID of player Machi1503 is 50e21463-60d9-4c51-a0be-b6fc6c5aacc2
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/STAT/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/ABILITY/1.0!
[ERROR] .... [Apotheosis : Adventure/]: Failed to execute LootRule irons_spellbooks:blaze_spell_book/apotheosis:rare/ABILITY/0.33!

I have such a mistake. The server crashes often, I don't know if it's related to this or not.
I have attached a file there are a lot of these errors. Here is an example. There are about 234 errors in the logs with this problem.
[Insufficient number of affixes to satisfy the loot rules (ignoring backup rules)]
Log 6.txt

I have such a mistake. The server crashes often, I don't know if it's related to this or not. I have attached a file there are a lot of these errors. Here is an example. There are about 234 errors in the logs with this problem. [Insufficient number of affixes to satisfy the loot rules (ignoring backup rules)] Log 6.txt

Your server crashing is likely due to https://www.curseforge.com/minecraft/mc-mods/apothic-curios
(This might have been resolved in the latest release a couple days ago)
If you want this message to go away, add more affixes to the entries logged

У меня такая ошибка. Сервер часто вылетает, не знаю связано это с этим или нет. Прикрепил файл, там много таких ошибок. Вот пример. В логах с этой проблемой около 234 ошибок. [Недостаточное количество аффиксов для удовлетворения правил добычи (игнорирование правил резервного копирования)] Журнал 6.txt

Сбой вашего сервера, вероятно, вызван https://www.curseforge.com/minecraft/mc-mods/apothic-curios (возможно, это было решено в последней версии пару дней назад)
Если вы хотите, чтобы это сообщение исчезло, добавьте дополнительные аффиксы к зарегистрированным записям.

Yes, it was I who contacted the developer at Discord. Yes, there was some kind of problem with the air tags. He released an updated version. But it's flying out now anyway. Of course I'll send it to him, maybe it's interconnected again.

[17Feb2024 16:27:21.981] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity mythic for category helmetRequired: 3; Provided: 2
[17Feb2024 16:27:21.981] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity mythic for category bootsRequired: 3; Provided: 2

[00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:ringRequired: 4; Provided: 3
5519 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:an_focusRequired: 4; Provided: 3
5520 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:necklaceRequired: 4; Provided: 3
5521 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:charmRequired: 4; Provided: 3
5522 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:beltRequired: 4; Provided: 3
5523 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:spellstoneRequired: 4; Provided: 3
5524 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:scrollRequired: 4; Provided: 3
5525 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:braceletRequired: 4; Provided: 3
5526 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:epic for category curios:talismanRequired: 4; Provided: 3
5527 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:ringRequired: 4; Provided: 3
5528 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:an_focusRequired: 4; Provided: 3
5529 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:necklaceRequired: 4; Provided: 3
5530 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:charmRequired: 4; Provided: 3
5531 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:beltRequired: 4; Provided: 3
5532 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:spellstoneRequired: 4; Provided: 3
5533 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:scrollRequired: 4; Provided: 3
5534 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:braceletRequired: 4; Provided: 3
5535 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:mythic for category curios:talismanRequired: 4; Provided: 3
5536 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category helmetRequired: 5; Provided: 4
5537 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category chestplateRequired: 5; Provided: 4
5538 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category leggingsRequired: 5; Provided: 4
5539 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category bootsRequired: 5; Provided: 4
5540 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category shieldRequired: 5; Provided: 4
5541 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:ringRequired: 5; Provided: 3
5542 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:an_focusRequired: 5; Provided: 3
5543 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:necklaceRequired: 5; Provided: 3
5544 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:charmRequired: 5; Provided: 3
5545 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:beltRequired: 5; Provided: 3
5546 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:spellstoneRequired: 5; Provided: 3
5547 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:scrollRequired: 5; Provided: 3
5548 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:braceletRequired: 5; Provided: 3
5549 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category curios:talismanRequired: 5; Provided: 3
5550 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category pickaxeRequired: 5; Provided: 4
5551 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheotic_additions:esoteric for category shovelRequired: 5; Provided: 4
5552 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category shieldRequired: 5; Provided: 4
5553 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:ringRequired: 5; Provided: 3
5554 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:an_focusRequired: 5; Provided: 3
5555 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:necklaceRequired: 5; Provided: 3
5556 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:charmRequired: 5; Provided: 3
5557 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:beltRequired: 5; Provided: 3
5558 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:spellstoneRequired: 5; Provided: 3
5559 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:scrollRequired: 5; Provided: 3
5560 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:braceletRequired: 5; Provided: 3
5561 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category curios:talismanRequired: 5; Provided: 3
5562 | [00:21:42] [Render thread/ERROR] [Apotheosis : Adventure/]: Insufficient number of affixes to satisfy the loot rules (ignoring backup rules) of rarity apotheosis:ancient for category bootsRequired: 4; Provided: 3

Looks like you need to provide more affixes for curios to get it to stop posting that in the log, base apotheosis doesn't do that.
Also, please don't just post server logs without actually defining an issue or providing any other information, there's not much to go off of from there.

Похоже, вам нужно предоставить больше аффиксов для curios, чтобы он перестал публиковать это в журнале, base apotheosis этого не делает. Также, пожалуйста, не публикуйте просто логи сервера без фактического определения проблемы или предоставления какой-либо другой информации, из этого не так много информации.

ok

Похоже, вам нужно предоставить больше аффиксов для curios, чтобы он перестал публиковать это в журнале, base apotheosis этого не делает. Также, пожалуйста, не публикуйте просто логи сервера без фактического определения проблемы или предоставления какой-либо другой информации, из этого не так много информации.

You probably think I know how to do this in terms of adding to curious. But I don't understand anything about it, I'm just a player)))))


Fix netcoreapp3.0

Fix some of the tests that started to fail after the move to netcoreapp3.0.

The VSTS failure is a known issue.

Superseded by #647.


chore: update workflow to only run once a day

Changes

update workflow to only run once a day to avoid intermittent rate limit issues with our other repos

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: b97b360e8afa119611becca759e9af86bf2d1802
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


tools: add option to gen_compilation_db for system clang

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

also worth mentioning - the reason i didnt move this to bazel already is im looking at shifting the clang-tidy part to using a bazel aspect
this would negate the need to run compdb first and almost certainly means we can run clang-tidy in presubmit/hooks/local formatting
this is kinda an aside as we still need to be able to generate compdb pref with pinned versions

On my Mac, the generated command always gives error Error: DEVELOPER_DIR not set. With this new flag, clangd works correctly.

With this new flag, clangd works correctly.

ok, cool - was flagging as i was already looking at this and trying to figure a better strategy

/retest


Two Devices on different ports?

Somehow I can't get two devices connected to the iobroker. One of them always keeps yellow state.
In the readme it says, that for two devices one of them needs to change the ports from default 54321 to something else. I changed to 54322 but it doesn't work.
Are there special ports that neeed to be used?
I have a Mi Robo (Gen 1) and a Roborock (Gen 2) does that make any difference concerning the ports?

@Alwiz79 the own port should be different for both devices (but the same default robot's port)


[BUG] Heat interface settings cannot be modified

Describe the bug
Heat interface settings cannot be modified.
To Reproduce

Go on https://teoxoy.github.io/factorio-blueprint-editor
Place heat interface.
Try to open it.

Expected behavior
Heat interface settings can be changed by opening it.
Desktop

OS: Windows 10
Browser: Firefox 67.0.4

Track the progress on this issue here: #73


Improve TrackLocal error handling

Return error to user when remote doesn't support codecs
Assert that a unadded track returns an error on Write
Assert that a added track doesn't error even when disconnected

Relates to #1526

@OrlandoCo @at-wat @lherman-cs @jeremija
With this I feel good calling the 'V3 Track API' good for v3.0.0 ! I covered all the tests that I colud think of.
I wasn't able to make TrackRemote work as an interface. Getting it to fit into OnTrack required casting, which felt like a danger to me.


Account blocked due to too many login attempts

Hi!
Has anyone ever had their account blocked due to "too many login attempts"? Did you do any changes in your workflow or code to prevent it from happening?
Sometimes during development, I end up running my scripts several times in a row (debugging mode, making small changes and running it again, etc). Every time I run the script, I'm effectively logging in with:
api_client = TradingAPI(credentials=credentials)
api_client.connect()

From time to time, I think I do it too often and then my account gets blocked. If I try to log in from the browser, I get a message saying "account blocked due to too many login attempts, please call support". After calling support, they ask a few security questions and then unblock my account.
To try to mitigate that, recently I started to use requests-cache just to cache the api_client.connect() step. By now my code should only be calling https://trader.degiro.nl/login/secure/login/totp once every 30 minutes (my cache TTL), and I tested that it is working as I intended, but I still got blocked again recently.
My main questions are:

Did anyone ever have their account blocked?
Do you use any type of caching to prevent too many login attempts?

For extra context: I have 2FA enabled and I'm using totp_secret_key on my Credentials().
Related ticket: https://github.com/Chavithra/degiro-connector/issues/89. But I decided to create a new thread because I've had this issue even before 1st of October, so although related, I would say it's not exactly the same concern.

Ah, that was my mistake, sorry. My cache actually prevents me from having this issue. My problem was that I had my code deployed in a "stage" environment that I forgot and from there it was behaving unexpectedly (trying to log in using old credentials, which would bypass the cache and then exceed the DeGiro limits). Since I have fixed my "stage" environment, I haven't had my account blocked again.
By the case, in case it might be useful for someone else, that's how I enabled cache for this case (using the requests_cache library):
        api_client = TradingAPI(credentials=credentials)

        with requests_cache.enabled(
                hours=0.5, allowable_methods=["GET", "HEAD", "POST"], ignored_parameters=["oneTimePassword"]
        ):
            api_client.connect()


update cov_exp_quad (and other matern kernels) to take in matrix input

Summary:
Currently, we only have support for vector[N] x[M]. I want to support Matrix[N M] input for the kernels, as this is constistent with GPstuff, and a very large majority statistics literature for a matrix of covariates. So function header will be:
gp_function_cov(const Eigen::Matrix<double, Eigen::Dynamic, Eigen::Dynamic> &x ,const T_p &parameter1)
For 3.0.0 (or whatever upcoming version # is), I remember reading we were going to deprecate the "vector of vector" syntax anyway, so I can take care of this as I implement them.
Current Version:
v2.17.0

@syclik @bob-carpenter mind having a quick discussion about what I should test, so I can run with this? I can hopefully implement prim pretty quickly for the ones I have PRs open for...

I'm going to close this issue, it's not really necessary. It has also already been discussed in more detail.


Added dependencies for psutil and cpuinfo

I added two more dependencies for psutil and cpuinfo components.
cpuinfo is throwing and exception during the setup fase but it seems to be a raspberry pi related issue and not a general issue .

Thanks


failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1

Bug description
I am running docker on Mac OS(M3)
Cloned fresh repository.
Ran the command "docker compose up"
Ran into error
How to reproduce the bug
[+] Building 92.7s (29/132)                                                                                docker:desktop-linux
 => [superset-init internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 7.11kB                                                                                0.0s
 => [superset internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 7.11kB                                                                                0.0s
 => [superset-worker-beat internal] load metadata for docker.io/library/python:3.10-slim-bookworm                                                                                3.3s
 => [superset-worker-beat internal] load metadata for docker.io/library/node:18-bullseye-slim                                                                                2.3s
 => [superset-worker internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 7.11kB                                                                                0.0s
 => [superset-worker-beat internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 7.11kB                                                                                0.0s
 => [superset-init internal] load .dockerignore                                                                                0.0s
 => => transferring context: 1.26kB                                                                                0.0s
 => [superset-worker internal] load .dockerignore                                                                                0.0s
 => => transferring context: 1.26kB                                                                                0.0s
 => [superset-worker-beat internal] load .dockerignore                                                                                0.0s
 => => transferring context: 1.26kB                                                                                0.0s
 => [superset internal] load .dockerignore                                                                                0.0s
 => => transferring context: 1.26kB                                                                                0.0s
 => [superset-init] importing cache manifest from apache/superset-cache:3.10-slim-bookworm                                                                                3.6s
 => => inferred cache manifest type: application/vnd.oci.image.index.v1+json                                                                                0.0s
 => [superset-worker superset-node  1/12] FROM docker.io/library/node:18-bullseye-slim@sha256:19f9bdb1890bcb6cc5e91f1c786984ab42bde48cf3f9f040d889d00830b756dc                                                   0.0s
 => [superset-worker-beat internal] load build context                                                                                1.0s
 => => transferring context: 84.07MB                                                                                1.0s
 => [superset-worker lean  1/14] FROM docker.io/library/python:3.10-slim-bookworm@sha256:38ced5e623fb8a6b256826a9f1bbcf5247a05123d6b6cb3847c9cd6ba46ef9ac                                                        0.0s
 => [superset-init internal] load build context                                                                                1.6s
 => => transferring context: 84.07MB                                                                                1.5s
 => [superset internal] load build context                                                                                1.5s
 => => transferring context: 84.07MB                                                                                1.4s
 => [superset-worker internal] load build context                                                                                1.6s
 => => transferring context: 84.07MB                                                                                1.5s
 => CACHED [superset-worker-beat superset-node  2/12] RUN apt-get update -qq     && apt-get install         -yqq --no-install-recommends         build-essential         python3                                 0.0s
 => CACHED [superset-worker-beat superset-node  3/12] RUN --mount=type=bind,target=/frontend-mem-nag.sh,src=./docker/frontend-mem-nag.sh     /frontend-mem-nag.sh                                                0.0s
 => CACHED [superset-worker-beat superset-node  4/12] WORKDIR /app/superset-frontend                                                                                0.0s
 => CACHED [superset-worker-beat superset-node  5/12] RUN --mount=type=bind,target=./package.json,src=./superset-frontend/package.json     --mount=type=bind,target=./package-lock.json,src=./superset-frontend  0.0s
 => CACHED [superset-worker-beat superset-node  6/12] COPY superset-frontend /app/superset-frontend                                                                                0.0s
 => ERROR [superset-worker-beat superset-node  7/12] RUN npm run build                                                                                84.6s
 => CACHED [superset-worker-beat lean  2/14] WORKDIR /app                                                                                0.0s
 => CACHED [superset-worker-beat lean  3/14] RUN mkdir -p /app/pythonpath superset/static requirements superset-frontend apache_superset.egg-info requirements     && useradd --user-group -d /app/superset_hom  0.0s
 => CACHED [superset-worker-beat lean  4/14] COPY --chown=superset:superset pyproject.toml setup.py MANIFEST.in README.md ./                                                                                0.0s
 => CACHED [superset-worker-beat lean  5/14] COPY --chown=superset:superset superset-frontend/package.json superset-frontend/                                                                                0.0s
 => CACHED [superset-worker-beat lean  6/14] COPY --chown=superset:superset requirements/base.txt requirements/                                                                                0.0s
 => CACHED [superset-worker-beat lean  7/14] RUN --mount=type=cache,target=/root/.cache/pip     apt-get update -qq && apt-get install -yqq --no-install-recommends       build-essential     && pip install --u  0.0s
------
 > [superset-worker-beat superset-node  7/12] RUN npm run build:
0.898
0.898 ><EMAIL_ADDRESS>build
0.898 > cross-env NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production BABEL_ENV="${BABEL_ENV:=production}" webpack --mode=production --color
0.898
1.594 [Superset Plugin] Use symlink source for @superset-ui/chart-controls @ ./packages/superset-ui-chart-controls
1.595 [Superset Plugin] Use symlink source for @superset-ui/core @ ./packages/superset-ui-core
1.596 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-calendar @ ./plugins/legacy-plugin-chart-calendar
1.596 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-chord @ ./plugins/legacy-plugin-chart-chord
1.597 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-country-map @ ./plugins/legacy-plugin-chart-country-map
1.597 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-event-flow @ ./plugins/legacy-plugin-chart-event-flow
1.597 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-heatmap @ ./plugins/legacy-plugin-chart-heatmap
1.598 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-histogram @ ./plugins/legacy-plugin-chart-histogram
1.598 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-horizon @ ./plugins/legacy-plugin-chart-horizon
1.599 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-map-box @ ./plugins/legacy-plugin-chart-map-box
1.599 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-paired-t-test @ ./plugins/legacy-plugin-chart-paired-t-test
1.599 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-parallel-coordinates @ ./plugins/legacy-plugin-chart-parallel-coordinates
1.600 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-partition @ ./plugins/legacy-plugin-chart-partition
1.600 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-rose @ ./plugins/legacy-plugin-chart-rose
1.600 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-sankey @ ./plugins/legacy-plugin-chart-sankey
1.601 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-sankey-loop @ ./plugins/legacy-plugin-chart-sankey-loop
1.601 [Superset Plugin] Use symlink source for @superset-ui/legacy-plugin-chart-world-map @ ./plugins/legacy-plugin-chart-world-map
1.601 [Superset Plugin] Use symlink source for @superset-ui/legacy-preset-chart-deckgl @ ./plugins/legacy-preset-chart-deckgl
1.602 [Superset Plugin] Use symlink source for @superset-ui/legacy-preset-chart-nvd3 @ ./plugins/legacy-preset-chart-nvd3
1.602 [Superset Plugin] Use symlink source for @superset-ui/plugin-chart-echarts @ ./plugins/plugin-chart-echarts
1.603 [Superset Plugin] Use symlink source for @superset-ui/plugin-chart-handlebars @ ./plugins/plugin-chart-handlebars
1.603 [Superset Plugin] Use symlink source for @superset-ui/plugin-chart-pivot-table @ ./plugins/plugin-chart-pivot-table
1.603 [Superset Plugin] Use symlink source for @superset-ui/plugin-chart-table @ ./plugins/plugin-chart-table
1.604 [Superset Plugin] Use symlink source for @superset-ui/plugin-chart-word-cloud @ ./plugins/plugin-chart-word-cloud
1.604 [Superset Plugin] Use symlink source for @superset-ui/switchboard @ ./packages/superset-ui-switchboard
1.604
1.954 <s> [webpack.Progress] 0%
1.954
1.954 <s> [webpack.Progress] 1% setup before run
1.954 <s> [webpack.Progress] 1% setup before run NodeEnvironmentPlugin
1.954 <s> [webpack.Progress] 1% setup before run
1.954 <s> [webpack.Progress] 2% setup run
1.955 <s> [webpack.Progress] 2% setup run webpack-cli
1.955 <s> [webpack.Progress] 2% setup run ForkTsCheckerWebpackPlugin
1.955 <s> [webpack.Progress] 2% setup run WebpackManifestPlugin
1.955 <s> [webpack.Progress] 2% setup run
1.956 <s> [webpack.Progress] 4% setup normal module factory
1.956 <s> [webpack.Progress] 4% setup normal module factory
1.956 <s> [webpack.Progress] 5% setup context module factory
1.956 <s> [webpack.Progress] 5% setup context module factory
1.957 <s> [webpack.Progress] 6% setup before compile
1.957 <s> [webpack.Progress] 6% setup before compile ProgressPlugin
1.957 <s> [webpack.Progress] 6% setup before compile
1.957 <s> [webpack.Progress] 7% setup compile
1.957 <s> [webpack.Progress] 7% setup compile ExternalsPlugin
1.957 <s> [webpack.Progress] 7% setup compile ExternalsPlugin
1.957 <s> [webpack.Progress] 7% setup compile
1.959 <s> [webpack.Progress] 8% setup compilation
1.959 <s> [webpack.Progress] 8% setup compilation CopyPlugin
1.959 <s> [webpack.Progress] 8% setup compilation mini-css-extract-plugin
1.960 <s> [webpack.Progress] 8% setup compilation ArrayPushCallbackChunkFormatPlugin
1.960 <s> [webpack.Progress] 8% setup compilation JsonpChunkLoadingPlugin
1.960 <s> [webpack.Progress] 8% setup compilation StartupChunkDependenciesPlugin
1.960 <s> [webpack.Progress] 8% setup compilation ImportScriptsChunkLoadingPlugin
1.960 <s> [webpack.Progress] 8% setup compilation FetchCompileWasmPlugin
1.960 <s> [webpack.Progress] 8% setup compilation FetchCompileAsyncWasmPlugin
1.960 <s> [webpack.Progress] 8% setup compilation WorkerPlugin
1.960 <s> [webpack.Progress] 8% setup compilation SplitChunksPlugin
1.961 <s> [webpack.Progress] 8% setup compilation ResolverCachePlugin
1.961 <s> [webpack.Progress] 8% setup compilation HtmlWebpackPlugin
1.961 <s> [webpack.Progress] 8% setup compilation HtmlWebpackPlugin
1.961 <s> [webpack.Progress] 8% setup compilation WebpackManifestPlugin
1.961 <s> [webpack.Progress] 8% setup compilation
1.961 <s> [webpack.Progress] 9% setup compilation
1.961 <s> [webpack.Progress] 9% setup compilation ProvidePlugin
1.961 <s> [webpack.Progress] 9% setup compilation DefinePlugin
1.964 <s> [webpack.Progress] 9% setup compilation ProgressPlugin
1.964 <s> [webpack.Progress] 9% setup compilation mini-css-extract-plugin
1.964 <s> [webpack.Progress] 9% setup compilation ForkTsCheckerWebpackPlugin
1.964 <s> [webpack.Progress] 9% setup compilation ChunkPrefetchPreloadPlugin
1.964 <s> [webpack.Progress] 9% setup compilation SourceMapDevToolPlugin
1.965 <s> [webpack.Progress] 9% setup compilation JavascriptModulesPlugin
1.965 <s> [webpack.Progress] 9% setup compilation JsonModulesPlugin
1.965 <s> [webpack.Progress] 9% setup compilation AssetModulesPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation EntryPlugin
1.965 <s> [webpack.Progress] 9% setup compilation RuntimePlugin
1.965 <s> [webpack.Progress] 9% setup compilation InferAsyncModulesPlugin
1.965 <s> [webpack.Progress] 9% setup compilation DataUriPlugin
1.965 <s> [webpack.Progress] 9% setup compilation FileUriPlugin
1.966 <s> [webpack.Progress] 9% setup compilation CompatibilityPlugin
1.966 <s> [webpack.Progress] 9% setup compilation HarmonyModulesPlugin
1.966 <s> [webpack.Progress] 9% setup compilation AMDPlugin
1.966 <s> [webpack.Progress] 9% setup compilation RequireJsStuffPlugin
1.966 <s> [webpack.Progress] 9% setup compilation CommonJsPlugin
1.966 <s> [webpack.Progress] 9% setup compilation LoaderPlugin
1.966 <s> [webpack.Progress] 9% setup compilation LoaderPlugin
1.966 <s> [webpack.Progress] 9% setup compilation NodeStuffPlugin
1.966 <s> [webpack.Progress] 9% setup compilation APIPlugin
1.967 <s> [webpack.Progress] 9% setup compilation ExportsInfoApiPlugin
1.967 <s> [webpack.Progress] 9% setup compilation WebpackIsIncludedPlugin
1.967 <s> [webpack.Progress] 9% setup compilation ConstPlugin
1.967 <s> [webpack.Progress] 9% setup compilation UseStrictPlugin
1.967 <s> [webpack.Progress] 9% setup compilation RequireIncludePlugin
1.967 <s> [webpack.Progress] 9% setup compilation RequireEnsurePlugin
1.967 <s> [webpack.Progress] 9% setup compilation RequireContextPlugin
1.967 <s> [webpack.Progress] 9% setup compilation ImportPlugin
1.967 <s> [webpack.Progress] 9% setup compilation ImportMetaContextPlugin
1.967 <s> [webpack.Progress] 9% setup compilation SystemPlugin
1.967 <s> [webpack.Progress] 9% setup compilation ImportMetaPlugin
1.967 <s> [webpack.Progress] 9% setup compilation URLPlugin
1.967 <s> [webpack.Progress] 9% setup compilation DefaultStatsFactoryPlugin
1.967 <s> [webpack.Progress] 9% setup compilation DefaultStatsPresetPlugin
1.967 <s> [webpack.Progress] 9% setup compilation DefaultStatsPrinterPlugin
1.968 <s> [webpack.Progress] 9% setup compilation JavascriptMetaInfoPlugin
1.968 <s> [webpack.Progress] 9% setup compilation EnsureChunkConditionsPlugin
1.968 <s> [webpack.Progress] 9% setup compilation RemoveEmptyChunksPlugin
1.968 <s> [webpack.Progress] 9% setup compilation MergeDuplicateChunksPlugin
1.968 <s> [webpack.Progress] 9% setup compilation FlagIncludedChunksPlugin
1.968 <s> [webpack.Progress] 9% setup compilation SideEffectsFlagPlugin
1.968 <s> [webpack.Progress] 9% setup compilation FlagDependencyExportsPlugin
1.968 <s> [webpack.Progress] 9% setup compilation FlagDependencyUsagePlugin
1.968 <s> [webpack.Progress] 9% setup compilation InnerGraphPlugin
1.968 <s> [webpack.Progress] 9% setup compilation MangleExportsPlugin
1.968 <s> [webpack.Progress] 9% setup compilation ModuleConcatenationPlugin
1.969 <s> [webpack.Progress] 9% setup compilation NoEmitOnErrorsPlugin
1.969 <s> [webpack.Progress] 9% setup compilation RealContentHashPlugin
1.969 <s> [webpack.Progress] 9% setup compilation WasmFinalizeExportsPlugin
1.969 <s> [webpack.Progress] 9% setup compilation DeterministicModuleIdsPlugin
1.969 <s> [webpack.Progress] 9% setup compilation DeterministicChunkIdsPlugin
1.969 <s> [webpack.Progress] 9% setup compilation DefinePlugin
1.969 <s> [webpack.Progress] 9% setup compilation CssMinimizerPlugin
1.969 <s> [webpack.Progress] 9% setup compilation TerserPlugin
1.972 <s> [webpack.Progress] 9% setup compilation TemplatedPathPlugin
1.972 <s> [webpack.Progress] 9% setup compilation RecordIdsPlugin
1.972 <s> [webpack.Progress] 9% setup compilation WarnCaseSensitiveModulesPlugin
1.972 <s> [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin
1.972 <s> [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin
1.972 <s> [webpack.Progress] 9% setup compilation AddBuildDependenciesPlugin
1.972 <s> [webpack.Progress] 9% setup compilation IgnoreWarningsPlugin
1.972 <s> [webpack.Progress] 9% setup compilation WebpackManifestPlugin
1.972 <s> [webpack.Progress] 9% setup compilation
1.972 <s> [webpack.Progress] 10% building
1.972 <s> [webpack.Progress] 10% building 0/1 entries 0/0 dependencies 0/0 modules
2.051 <s> [webpack.Progress] 10% building import loader ./node_modules/thread-loader/dist/cjs.js
2.055 <s> [webpack.Progress] 10% building import loader ./node_modules/babel-loader/lib/index.js
2.142 <s> [webpack.Progress] 10% building import loader ./node_modules/ts-loader/index.js
2.162 <s> [webpack.Progress] 10% building 0/8 entries 8/8 dependencies 0/5 modules
3.496 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
3.496     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
3.496     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
3.497 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
3.497     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
3.497     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
3.501 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
3.501     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
3.501     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
3.506 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
3.506     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
3.506     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
3.507 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
3.507     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
3.507     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
3.507 <s> [webpack.Progress] 10% building 0/8 entries 8/9 dependencies 0/5 modules
3.525 <s> [webpack.Progress] 10% building import loader ./node_modules/mini-css-extract-plugin/dist/loader.js
3.526 <s> [webpack.Progress] 10% building import loader ./node_modules/css-loader/dist/cjs.js
3.608 <s> [webpack.Progress] 10% building import loader ./node_modules/less-loader/dist/cjs.js
3.613 <s> [webpack.Progress] 10% building 0/8 entries 11/13 dependencies 0/8 modules
3.649 <s> [webpack.Progress] 10% building import loader ./node_modules/react-hot-loader/webpack.js
3.659 <s> [webpack.Progress] 10% building 0/8 entries 14/74 dependencies 0/9 modules
4.237 <s> [webpack.Progress] 10% building 0/8 entries 80/179 dependencies 2/45 modules
4.822 <s> [webpack.Progress] 10% building 0/8 entries 177/266 dependencies 4/100 modules
5.555 - Processing: packages/superset-ui-chart-controls/src/components/CertifiedIconWithTooltip.tsx
5.901 \ Processing: packages/superset-ui-chart-controls/src/components/ColumnOption.tsx
5.963 | Processing: packages/superset-ui-chart-controls/src/components/ColumnTypeLabel/ColumnTypeLabel.tsx
6.022 / Processing: packages/superset-ui-chart-controls/src/components/ControlHeader.tsx
6.054 <s> [webpack.Progress] 10% building 0/8 entries 192/300 dependencies 4/113 modules
6.073 - Processing: packages/superset-ui-chart-controls/src/components/ControlSubSectionHeader.tsx
6.091 \ Processing: packages/superset-ui-chart-controls/src/components/Dropdown.tsx
6.114 | Processing: packages/superset-ui-chart-controls/src/components/InfoTooltipWithTrigger.tsx
6.139 / Processing: packages/superset-ui-chart-controls/src/components/Menu.tsx
6.161 - Processing: packages/superset-ui-chart-controls/src/components/MetricOption.tsx
6.201 \ Processing: packages/superset-ui-chart-controls/src/components/SQLPopover.tsx
6.241 | Processing: packages/superset-ui-chart-controls/src/components/Select.tsx
6.277 / Processing: packages/superset-ui-chart-controls/src/components/Tooltip.tsx
6.303 - Processing: packages/superset-ui-chart-controls/src/components/labelUtils.tsx
6.323 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
6.323     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
6.323     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
6.323 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
6.323     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
6.323     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
6.327 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
6.327     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
6.327     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
6.328 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
6.328     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
6.328     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
6.328 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
6.328     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
6.328     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
6.348 \ Processing: packages/superset-ui-chart-controls/src/constants.ts
6.379 | Processing: packages/superset-ui-chart-controls/src/fixtures.ts
6.414 / Processing: packages/superset-ui-chart-controls/src/index.ts
6.432 - Processing: packages/superset-ui-chart-controls/src/operators/boxplotOperator.ts
6.453 \ Processing: packages/superset-ui-chart-controls/src/operators/contributionOperator.ts
6.465 | Processing: packages/superset-ui-chart-controls/src/operators/flattenOperator.ts
6.477 / Processing: packages/superset-ui-chart-controls/src/operators/histogramOperator.ts
6.497 - Processing: packages/superset-ui-chart-controls/src/operators/index.ts
6.516 \ Processing: packages/superset-ui-chart-controls/src/operators/pivotOperator.ts
6.536 | Processing: packages/superset-ui-chart-controls/src/operators/prophetOperator.ts
6.553 / Processing: packages/superset-ui-chart-controls/src/operators/rankOperator.ts
6.566 - Processing: packages/superset-ui-chart-controls/src/operators/renameOperator.ts
6.585 \ Processing: packages/superset-ui-chart-controls/src/operators/resampleOperator.ts
6.601 | Processing: packages/superset-ui-chart-controls/src/operators/rollingWindowOperator.ts
6.628 / Processing: packages/superset-ui-chart-controls/src/operators/sortOperator.ts
6.651 - Processing: packages/superset-ui-chart-controls/src/operators/timeCompareOperator.ts
6.667 \ Processing: packages/superset-ui-chart-controls/src/operators/timeComparePivotOperator.ts
6.683 | Processing: packages/superset-ui-chart-controls/src/operators/types.ts
6.692 / Processing: packages/superset-ui-chart-controls/src/operators/utils/constants.ts
6.706 - Processing: packages/superset-ui-chart-controls/src/operators/utils/extractExtraMetrics.ts
6.720 \ Processing: packages/superset-ui-chart-controls/src/operators/utils/getMetricOffsetsMap.ts
6.733 | Processing: packages/superset-ui-chart-controls/src/operators/utils/index.ts
6.744 / Processing: packages/superset-ui-chart-controls/src/operators/utils/isDerivedSeries.ts
6.749 `isModuleDeclaration` has been deprecated, please migrate to `isImportOrExportDeclaration`
6.749     at isModuleDeclaration (/app/superset-frontend/node_modules/@babel/types/lib/validators/generated/index.js:2748:35)
6.749     at PluginPass.Program (/app/superset-frontend/node_modules/babel-plugin-lodash/lib/index.js:102:44)
6.760 - Processing: packages/superset-ui-chart-controls/src/operators/utils/isTimeComparison.ts
6.774 \ Processing: packages/superset-ui-chart-controls/src/operators/utils/timeOffset.ts
6.793 | Processing: packages/superset-ui-chart-controls/src/sections/advancedAnalytics.tsx
6.827 / Processing: packages/superset-ui-chart-controls/src/sections/annotationsAndLayers.tsx
6.830 <s> [webpack.Progress] 10% building 0/8 entries 300/589 dependencies 7/179 modules
6.844 - Processing: packages/superset-ui-chart-controls/src/sections/chartTitle.tsx
6.864 \ Processing: packages/superset-ui-chart-controls/src/sections/echartsTimeSeriesQuery.tsx
6.882 | Processing: packages/superset-ui-chart-controls/src/sections/forecastInterval.tsx
6.896 / Processing: packages/superset-ui-chart-controls/src/sections/index.ts
6.908 - Processing: packages/superset-ui-chart-controls/src/sections/sections.tsx
6.927 \ Processing: packages/superset-ui-chart-controls/src/sections/timeComparison.tsx
6.948 | Processing: packages/superset-ui-chart-controls/src/shared-controls/components/RadioButtonControl.tsx
6.968 / Processing: packages/superset-ui-chart-controls/src/shared-controls/components/index.tsx
6.979 - Processing: packages/superset-ui-chart-controls/src/shared-controls/components/types.ts
6.995 \ Processing: packages/superset-ui-chart-controls/src/shared-controls/customControls.tsx
7.034 | Processing: packages/superset-ui-chart-controls/src/shared-controls/dndControls.tsx
7.064 / Processing: packages/superset-ui-chart-controls/src/shared-controls/index.ts
7.083 - Processing: packages/superset-ui-chart-controls/src/shared-controls/mixins.tsx
7.131 \ Processing: packages/superset-ui-chart-controls/src/shared-controls/sharedControls.tsx
7.192 | Processing: packages/superset-ui-chart-controls/src/types.ts
7.245 / Processing: packages/superset-ui-chart-controls/src/utils/D3Formatting.ts
7.259 - Processing: packages/superset-ui-chart-controls/src/utils/checkColumnType.ts
7.274 \ Processing: packages/superset-ui-chart-controls/src/utils/columnChoices.ts
7.291 | Processing: packages/superset-ui-chart-controls/src/utils/defineSavedMetrics.ts
7.302 / Processing: packages/superset-ui-chart-controls/src/utils/displayTimeRelatedControls.ts
7.315 - Processing: packages/superset-ui-chart-controls/src/utils/expandControlConfig.tsx
7.341 \ Processing: packages/superset-ui-chart-controls/src/utils/getColorFormatters.ts
7.381 | Processing: packages/superset-ui-chart-controls/src/utils/getStandardizedControls.ts
7.405 / Processing: packages/superset-ui-chart-controls/src/utils/getTemporalColumns.ts
7.420 - Processing: packages/superset-ui-chart-controls/src/utils/index.ts
7.435 \ Processing: packages/superset-ui-chart-controls/src/utils/mainMetric.ts
7.442 <s> [webpack.Progress] 10% building 0/8 entries 587/638 dependencies 12/314 modules
7.449 | Processing: packages/superset-ui-chart-controls/src/utils/selectOptions.ts
7.470 / Processing: packages/superset-ui-core/src/api/types/core.ts
7.485 - Processing: packages/superset-ui-core/src/chart/clients/ChartClient.ts
7.529 \ Processing: packages/superset-ui-core/src/chart/components/ChartDataProvider.tsx
7.560 | Processing: packages/superset-ui-core/src/chart/components/FallbackComponent.tsx
7.586 / Processing: packages/superset-ui-core/src/chart/components/NoResultsComponent.tsx
7.631 - Processing: packages/superset-ui-core/src/chart/components/SuperChart.tsx
7.680 \ Processing: packages/superset-ui-core/src/chart/components/SuperChartCore.tsx
.
.
.
.
.
.
.
.
.
.
.
.

59.52 <s> [webpack.Progress] 92% sealing asset processing
59.52 <s> [webpack.Progress] 92% sealing asset processing copy-webpack-plugin
59.61 <s> [webpack.Progress] 92% sealing asset processing PersistentChildCompilerSingletonPlugin
59.61 <s> [webpack.Progress] 92% sealing asset processing CssMinimizerPlugin
59.64 \ Processing: src/explore/components/controls/HiddenControl.tsx
59.84 | Processing: src/explore/components/controls/MetricControl/AdhocMetricEditPopover/AdhocMetricEditPopover.test.tsx
60.03 / Processing: src/explore/components/controls/MetricControl/AdhocMetricEditPopoverTitle.test.tsx
60.13 - Processing: src/explore/components/controls/MetricControl/AdhocMetricEditPopoverTitle.tsx
60.24 \ Processing: src/explore/components/controls/MetricControl/AdhocMetricPopoverTrigger.tsx
60.33 | Processing: src/explore/components/controls/MetricControl/AggregateOption.test.tsx
60.40 / Processing: src/explore/components/controls/MetricControl/MetricDefinitionOption.test.tsx
60.58 - Processing: src/explore/components/controls/MetricControl/types.ts
60.59 \ Processing: src/explore/components/controls/OptionControls/OptionControls.test.tsx
60.62 | Processing: src/explore/components/controls/OptionControls/index.tsx
60.67 / Processing: src/explore/components/controls/SelectAsyncControl/SelectAsyncControl.test.tsx
60.69 - Processing: src/explore/components/controls/SelectAsyncControl/index.tsx
60.78 \ Processing: src/explore/components/controls/SliderControl.stories.tsx
60.79 | Processing: src/explore/components/controls/SliderControl.tsx
60.88 / Processing: src/explore/components/controls/TextControl/TextControl.test.tsx
60.90 - Processing: src/explore/components/controls/TextControl/index.tsx
60.93 \ Processing: src/explore/components/controls/TimeOffsetControl.tsx
60.96 | Processing: src/explore/components/controls/TimeSeriesColumnControl/TimeSeriesColumnControl.test.tsx
61.06 / Processing: src/explore/components/controls/ViewQuery.tsx
61.10 - Processing: src/explore/components/controls/ViewQueryModal.tsx
61.12 \ Processing: src/explore/components/controls/ViewQueryModalFooter.tsx
61.19 | Processing: src/explore/components/controls/VizTypeControl/FastVizSwitcher.tsx
61.25 / Processing: src/explore/components/controls/VizTypeControl/VizTypeControl.test.tsx
61.31 - Processing: src/explore/components/controls/VizTypeControl/VizTypeGallery.tsx
61.39 \ Processing: src/explore/components/controls/VizTypeControl/index.tsx
61.42 | Processing: src/explore/components/controls/XAxisSortControl.tsx
61.45 <s> [webpack.Progress] 92% sealing asset processing TerserPlugin
61.57 / Processing: src/explore/components/controls/withAsyncVerification.test.tsx
61.63 - Processing: src/explore/components/controls/withAsyncVerification.tsx
61.65 \ Processing: src/explore/components/optionRenderers.tsx
61.67 | Processing: src/explore/components/useExploreAdditionalActionsMenu/DashboardsSubMenu.test.tsx
61.70 / Processing: src/explore/components/useExploreAdditionalActionsMenu/DashboardsSubMenu.tsx
61.79 - Processing: src/explore/constants.ts
61.83 \ Processing: src/explore/controlPanels/sections.tsx
61.87 | Processing: src/explore/controlUtils/controlUtils.test.tsx
61.90 / Processing: src/explore/controlUtils/getColumnKeywords.test.tsx
61.91 - Processing: src/explore/controlUtils/getColumnKeywords.tsx
61.93 \ Processing: src/explore/controlUtils/getControlConfig.ts
61.99 | Processing: src/explore/controlUtils/getControlState.ts
62.04 / Processing: src/explore/controlUtils/getControlValuesCompatibleWithDatasource.test.ts
62.07 - Processing: src/explore/controlUtils/getControlValuesCompatibleWithDatasource.ts
62.09 \ Processing: src/explore/controlUtils/getFormDataFromControls.ts
62.12 | Processing: src/explore/controlUtils/getFormDataFromDashboardContext.test.ts
62.17 / Processing: src/explore/controlUtils/getFormDataWithDashboardContext.ts
62.25 - Processing: src/explore/controlUtils/getSectionsToRender.ts
62.33 \ Processing: src/explore/controlUtils/index.ts
62.42 | Processing: src/explore/controlUtils/standardizedFormData.test.ts
62.54 / Processing: src/explore/controlUtils/standardizedFormData.ts
62.86 - Processing: src/explore/exploreUtils/formData.test.ts
62.93 \ Processing: src/explore/exploreUtils/formData.ts
62.96 | Processing: src/explore/exploreUtils/getChartDataUri.test.ts
63.11 / Processing: src/explore/exploreUtils/getChartKey.test.ts
63.16 - Processing: src/explore/exploreUtils/getExploreUrl.test.ts
63.20 \ Processing: src/explore/exploreUtils/getHostName.test.ts
63.27 | Processing: src/explore/exploreUtils/getLegacyEndpointType.test.ts
63.31 / Processing: src/explore/exploreUtils/getParsedExploreURLParams.test.ts
63.40 - Processing: src/explore/exploreUtils/getParsedExploreURLParams.ts
63.46 \ Processing: src/explore/exploreUtils/getSimpleSQLExpression.test.ts
63.49 | Processing: src/explore/exploreUtils/getURIDirectory.test.ts
63.68 / Processing: src/explore/exploreUtils/shouldUseLegacyApi.test.ts
63.72 - Processing: src/explore/fixtures.tsx
63.78 \ Processing: src/explore/reducers/datasourcesReducer.ts
64.24 | Processing: src/explore/types.ts
64.40 / Processing: src/features/alerts/AlertReportModal.test.tsx
65.00 - Processing: src/features/alerts/AlertReportModal.tsx
65.74 \ Processing: src/features/alerts/buildErrorTooltipMessage.test.tsx
65.84 | Processing: src/features/alerts/buildErrorTooltipMessage.tsx
65.89 / Processing: src/features/alerts/components/AlertReportCronScheduler.tsx
65.99 - Processing: src/features/alerts/components/AlertStatusIcon.tsx
66.06 \ Processing: src/features/alerts/components/NotificationMethod.test.tsx
66.15 | Processing: src/features/alerts/components/NotificationMethod.tsx
66.24 / Processing: src/features/alerts/components/NumberInput.tsx
66.26 - Processing: src/features/alerts/components/RecipientIcon.test.tsx
66.29 \ Processing: src/features/alerts/components/RecipientIcon.tsx
66.34 | Processing: src/features/alerts/components/StyledPanel.tsx
66.42 / Processing: src/features/alerts/components/ValidatedPanelHeader.tsx
66.50 - Processing: src/features/alerts/types.ts
66.57 \ Processing: src/features/allEntities/AllEntitiesTable.tsx
66.80 | Processing: src/features/annotationLayers/AnnotationLayerModal.tsx
66.91 / Processing: src/features/annotationLayers/types.ts
67.09 - Processing: src/features/annotations/AnnotationModal.tsx
67.21 \ Processing: src/features/annotations/types.ts
67.27 | Processing: src/features/charts/ChartCard.tsx
67.47 / Processing: src/features/cssTemplates/CssTemplateModal.tsx
67.54 - Processing: src/features/cssTemplates/types.ts
67.58 \ Processing: src/features/dashboards/DashboardCard.test.tsx
67.67 | Processing: src/features/dashboards/DashboardCard.tsx
67.78 / Processing: src/features/dashboards/types.ts
67.82 - Processing: src/features/databases/DatabaseModal/DatabaseConnectionForm/CommonParameters.tsx
67.95 \ Processing: src/features/databases/DatabaseModal/DatabaseConnectionForm/EncryptedField.tsx
68.03 | Processing: src/features/databases/DatabaseModal/DatabaseConnectionForm/TableCatalog.tsx
68.08 / Processing: src/features/databases/DatabaseModal/DatabaseConnectionForm/ValidatedInputField.tsx
68.14 - Processing: src/features/databases/DatabaseModal/DatabaseConnectionForm/index.tsx
68.21 \ Processing: src/features/databases/DatabaseModal/ExtraOptions.tsx
68.46 | Processing: src/features/databases/DatabaseModal/ModalHeader.tsx
68.52 / Processing: src/features/databases/DatabaseModal/SSHTunnelForm.tsx
68.60 - Processing: src/features/databases/DatabaseModal/SSHTunnelSwitch.test.tsx
68.63 \ Processing: src/features/databases/DatabaseModal/SSHTunnelSwitch.tsx
68.69 | Processing: src/features/databases/DatabaseModal/SqlAlchemyForm.tsx
68.79 / Processing: src/features/databases/DatabaseModal/index.test.tsx
69.18 - Processing: src/features/databases/DatabaseModal/index.tsx
69.46 \ Processing: src/features/databases/DatabaseModal/styles.ts
69.55 | Processing: src/features/databases/UploadDataModel/ColumnsPreview.tsx
69.57 / Processing: src/features/databases/UploadDataModel/StyledFormItemWithTip.tsx
69.61 - Processing: src/features/databases/UploadDataModel/UploadDataModal.test.tsx
69.96 \ Processing: src/features/databases/UploadDataModel/index.tsx
70.17 | Processing: src/features/databases/UploadDataModel/styles.ts
70.24 / Processing: src/features/databases/state.ts
70.29 - Processing: src/features/databases/types.ts
70.37 \ Processing: src/features/datasets/AddDataset/DatasetPanel/DatasetPanel.stories.tsx
70.44 | Processing: src/features/datasets/AddDataset/DatasetPanel/DatasetPanel.test.tsx
70.52 / Processing: src/features/datasets/AddDataset/DatasetPanel/DatasetPanel.tsx
70.60 - Processing: src/features/datasets/AddDataset/DatasetPanel/MessageContent.tsx
70.78 \ Processing: src/features/datasets/AddDataset/DatasetPanel/fixtures.ts
70.89 | Processing: src/features/datasets/AddDataset/DatasetPanel/index.tsx
84.10 / Processing: src/features/datasets/AddDataset/DatasetPanel/types.ts
84.13 - Processing: src/features/datasets/AddDataset/EditDataset/EditDataset.test.tsx
84.20 \ Processing: src/features/datasets/AddDataset/EditDataset/UsageTab/UsageTab.test.tsx
84.32 | Processing: src/features/datasets/AddDataset/EditDataset/UsageTab/index.tsx
84.40 / Processing: src/features/datasets/AddDataset/EditDataset/index.tsx
------
failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1

Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
[ ] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

This is almost certainly docker running out of memory. Try bumping it to something like 16MB and let us know if that resolves it. This is something that @mistercrunch is looking at solving systemically with a resource check script that will let you know if your settings are sufficient before hitting this wall.

It was indeed a memory issue, a simple fix for this that worked for me was changing the build variable under scripts in package.json to "build": "export NODE_OPTIONS=--max_old_space_size=4096 && webpack --config webpack.config.js"

I have also fixed this issue by increasing my WSL memory. However, I encounter this issue where I get stuck at "[webpack.Progress] 94% sealing after seal".

Does it crash/gets killed? Seems memory-related too or more inderectly swapping if it's just coming to a crawl.
We'll need a way to control/diminish memory usage when building. Not sure what our options are there. Some options or things to look into:

allocate more memory, use a host with more memory
some webpack config tweaks? out of my wheelhouse but there's probably a lot that's possible there
improve docker layer caching hit rate, if you're using an official release or even a common SHA on master, the dockerhub cache should just work (but doesn't always for reasons that are beyond me)
?

I'm using Windows 11 and Docker Desktop with WSL2. I have already set the memory to 12GB (even tried up to 16GB) but I still get stuck at that part. It doesn't crash, it's just get stuck at "[webpack.Progress] 94% sealing after seal".

Guessing that has to do with virtualization being super slow and/or swapping. 16GB should be enough. One thing to note is that this step is super IO intensive while dealing with 250k files in node_modules/, and I'm guessing windows virtualization of filesystem may act as some sort of bottleneck (?)

Curious-  @brantian are you on Windows too?

@brantian I wasn't able to run it on Windows. I was able to run it on my Mac with Docker Desktop and resources settings of CPU=8core, memory/ram=8GBm, and swap=4.

@mistercrunch yes, I'm on Windows.
I deleted the repo locally and cloned it again, and now the docker-compose startup works
However, this is what I see after logging in:

I'm guessing superset-node is not done building the assets, either failed or is taking forever (?) Would look something like that ->
, though on my Mac that takes like a minute.
You could try BUILD_SUPERSET_FRONTEND_IN_DOCKER=false and build locally if npm/webpack works on windows (?)

After a few attempts, I was able to make it work by:

Switching to the 4.0.2 tag instead of using the main branch
Running both Docker as admin

Sounds like all is solved here, so I'll close this out :)

NOTE: In CI, to limit memory consumption, I sequentialize building docker layers by running a command that builds the superset-node docker "target" first, and then build the lean or dev after, sequentially. Otherwise what happens is docker builds superset-node and python-base in parallel. That can help a bit with build memory consumption where memory-constrained.
Anyhow, in all cases, you should either reuse published images if/when you can (simple docker pull from Docker Hub), or meet the mem requirement if you want to build.


(feature) add privacy policy

link from footer
add feature specs to very cookie and policy page linking

 Add privacy policy


Modle error

Hello author, I want to run your code on my own dataset, it seems like there are some files missing in your code?

ImportError: cannot import name 'ResNeXt101'
And which file is your proposed model？
Thanks！

You can use the offical ResNeXt101 of pytorch.