chore: aligning dependencies with the metamask-design-system

Description
This PR aligns the dependency versions and configuration files (TypeScript, ESLint, Prettier) in the design-tokens repository with those used in the metamask-design-system monorepo, as part of the migration process. This alignment addresses compatibility issues and ensures that the configurations between the repositories are consistent, making future maintenance more straightforward.
Related issues
Fixes: https://github.com/MetaMask/design-tokens/issues/746
Manual testing steps

Review dependency versions and configuration files (TypeScript, ESLint, Prettier) to ensure they are consistent with the metamask-design-system monorepo.
Verify that there are no errors or compatibility issues introduced by these changes. e.g yarn lint yarn build

Pre-merge author checklist

[x] I’ve followed MetaMask Coding Standards.
[x] I've clearly explained what problem this PR is solving and how it is solved.
[x] I've linked related issues.
[ ] I've included manual testing steps.
[ ] I've included screenshots/recordings if applicable.
[ ] I’ve included tests if applicable.
[ ] I’ve documented my code using JSDoc format if applicable.
[x] I’ve applied the right labels on the PR (see labeling guidelines).

Pre-merge reviewer checklist

[ ] I've manually tested the PR (e.g., pull and build branch, run the app, test code being changed).
[ ] I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and/or screenshots.

@SocketSecurity ignore-all

Acceptable risk as we will be protected against supply chain attack by lavamoat

As we are in the process of migrating we will not fix the announce storybook job


feat: designed new features section

Summary by CodeRabbit

New Features

Revamped the Features section with a new grid layout and added images to feature cards for a more visual experience.
Renamed the Features component to Home, reflecting its broader role on the website.

Enhancements

Updated the Home component to use Next.js's Image component for better performance and SEO.
Introduced unique IDs for feature items, enhancing accessibility and structure.

Style

Enhanced the visual appeal of the feature cards with updated styling and layout adjustments.
Adopted a section-based layout for improved semantic structure and readability.

Refactor

Transitioned to arrow function syntax for a more modern and concise codebase.
Extracted metadata and viewport configurations to their own exports for better modularity.

Documentation

Removed outdated "and many more!" text to streamline content presentation.

@iryanraushan Please fix the website deployment error.
Error :point_down:
[16:26:53.998] Failed to compile.
[16:26:53.998]
[16:26:53.998] ./app/Features.js
[16:26:53.999] 46:13  Error: Missing "key" prop for element in iterator  react/jsx-key
[16:26:53.999]
[16:26:53.999] ./app/Header.js
[16:26:53.999] 93:6  Warning: React Hook useEffect has a missing dependency: 'onScroll'. Either include it or remove the dependency array.  react-hooks/exhaustive-deps
[16:26:53.999]
[16:26:53.999] info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
[16:26:54.032] Error: Command "npm run build" exited with 1

@iryanraushan Also, can the background color of the Features' section be changed? What if we have a blue shade gradient? Would that look nice :thinking:? Any other colours or gradients can be there - please let me know what you think we can have.

Which icons used ??

@iryanraushan You will replace each of the icon elements in features named constant, with the html tag I mentioned in the earlier comment.
You are supposed to use FontAwesome Icons.

@iryanraushan Did you understand what change I requested?

i got it. But i can't use the icons which you used. I dont know why can u suggest me the full process because i tried so hard still no result. i also dont wanna use offline svg files. please sugget me what i can do ?

Hey i want to ask something please help. i am new in open source but i feel good to do this type of project. please help me to setup this project on my local machine.
all commands setup to un  ?

@iryanraushan Welcome to Open-Source :handshake:! I guess you have contributed to this project previously also.
Feeling good that you loved working on this project.
@iryanraushan Which part of the project do you want to setup? The Drifty application or the Website? I can help you out for sure :smile: :+1:.


[AutoRelease] t2-datafactory-2023-12-15-04702(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4833
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=987

issue link:https://github.com/Azure/sdk-release-request/issues/4833


Add images of sample reports/outcomes of the tool to the readme

Is your feature request related to a problem? Please describe.
This is a software package that is centered around reporting and visualizing issues in tables and graphs. Yet these graphs are nowhere to be found. A picture is worth more than a thousand pages of documentation about xml formats :)
Please make the "what you get" of this project a very "in your face" presentation. I checked the owasp page, documentation and github page and found nothing.
Describe the solution you'd like
A screenshot or two of two sample reports, with graphs and eye candy near the top of the readme file. So everyone that is remotely interested can easily see what they get.
Describe alternatives you've considered
Googling for images. This results in outdated images at low resolutions.
Additional context
I'm trying to add this tool to a presentation. Yet it's hard to show "what it can do" without any visualization. Making that easier, would make the product easier to recommend.
(sorry if i come off as strong, i think using more images is just a golden opportunity for the project. I always get a bit sad when somebody announces a project and has no screenshot of what it delivers. I've made that mistake myself too a few times 👍 )

ODC doesn't do "graphs and eye candy", best visual you get is a html page with the logo.
you can run the tool on any project you lke, github is full of them and when writing a presentation you should know how a tool works/what it can do.
that being said, below the results of running mvn org.owasp:dependency-check-maven:aggregate on a typical enterprise project
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] BRMO                                                               [pom]
[INFO] BRMO test-util                                                     [jar]
[INFO] BRMO RSGB datamodel                                                [pom]
[INFO] BRMO topnlparser                                                   [jar]
[INFO] BRMO BGT GML loader                                                [jar]
[INFO] BRMO loader                                                        [jar]
[INFO] BRMO initialisatie utilities                                       [jar]
[INFO] BRMO persistence                                                   [jar]
[INFO] BRMO taglibrary                                                    [jar]
[INFO] BRMO soap utilities                                                [jar]
[INFO] BRMO service                                                       [war]
[INFO] BRMO commandline                                                   [jar]
[INFO] BRMO proxyservice                                                  [war]
[INFO] BRMO soap bevragingsservice                                        [war]
[INFO] BRMO STUF BG 204                                                   [war]
[INFO] BRMO distributie                                                   [pom]
[INFO]
[INFO] Using the MultiThreadedBuilder implementation with a thread count of 4
[INFO]
[INFO] ----------------------------< nl.b3p:brmo >-----------------------------
[INFO] Building BRMO 1.6.4-SNAPSHOT                                      [1/16]
[INFO] --------------------------------[ pom ]---------------------------------
[INFO]
[INFO] --- dependency-check-maven:5.2.2:aggregate (default-cli) @ brmo ---
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-soap-util:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-init-util:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-persistence:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-soap-util:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-init-util:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-taglib:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-proxyservice:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-service:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-soap:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-stufbg204:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-commandline:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-soap-util:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:topnlparser:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:bgt-gml-loader:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-init-util:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Found snapshot reactor project in aggregate for nl.b3p:brmo-taglib:1.6.4-SNAPSHOT - creating a virtual dependency as the snapshot found in the repository may contain outdated dependencies.
[INFO] Checking for updates
[INFO] Skipping NVD check since last check was within 4 hours.
[INFO] Skipping RetireJS update since last update was within 24 hours.
[INFO] Check for updates complete (39 ms)
[INFO]

Dependency-Check is an open source tool performing a best effort analysis of 3rd party dependencies; false positives and false negatives may exist in the analysis performed by the tool. Use of the tool and the reporting provided constitutes acceptance for use in an AS IS condition, and there are NO warranties, implied or otherwise, with regard to the analysis or its use. Any use of the tool and the reporting provided is at the user’s risk. In no event shall the copyright holder or OWASP be held liable for any damages whatsoever arising out of or in connection with the use of this tool, the analysis performed, or the resulting report.

[INFO] Analysis Started
[INFO] Finished Archive Analyzer (5 seconds)
[INFO] Finished File Name Analyzer (0 seconds)
[INFO] Finished Jar Analyzer (2 seconds)
[INFO] Finished Python Distribution Analyzer (0 seconds)
[INFO] Finished Dependency Merging Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Created CPE Index (3 seconds)
[INFO] Finished CPE Analyzer (4 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
00:00  INFO: Vulnerability found: jquery below 1.9.0b1
00:00  INFO: Vulnerability found: jquery below 1.12.0
00:00  INFO: Vulnerability found: jquery below 1.12.0
00:00  INFO: Vulnerability found: jquery below 3.4.0
[INFO] Finished RetireJS Analyzer (1 seconds)
[INFO] Finished Sonatype OSS Index Analyzer (0 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Analysis Complete (17 seconds)
[WARNING]

One or more dependencies were identified with known vulnerabilities in BRMO:

dom4j-1.6.1.jar<EMAIL_ADDRESS>cpe:2.3:a:dom4j_project:dom4j:1.6.1:*:*:*:*:*:*:*) : CVE-2018-1000632
ha-api-3.1.12.jar<EMAIL_ADDRESS>cpe:2.3:a:eclipse:eclipse_ide:3.1.12:*:*:*:*:*:*:*) : CVE-2008-7271, CVE-2010-4647
javasimon-console-embed-4.1.4.jar: jquery.js<EMAIL_ADDRESS>: CVE-2012-6708, CVE-2015-9251, CVE-2019-11358

See the dependency-check report for more details.

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for BRMO 1.6.4-SNAPSHOT:
[INFO]
[INFO] BRMO ............................................... SUCCESS [ 38.992 s]
[INFO] BRMO test-util ..................................... SKIPPED
[INFO] BRMO RSGB datamodel ................................ SKIPPED
[INFO] BRMO topnlparser ................................... SKIPPED
[INFO] BRMO BGT GML loader ................................ SKIPPED
[INFO] BRMO loader ........................................ SKIPPED
[INFO] BRMO initialisatie utilities ....................... SKIPPED
[INFO] BRMO persistence ................................... SKIPPED
[INFO] BRMO taglibrary .................................... SKIPPED
[INFO] BRMO soap utilities ................................ SKIPPED
[INFO] BRMO service ....................................... SKIPPED
[INFO] BRMO commandline ................................... SKIPPED
[INFO] BRMO proxyservice .................................. SKIPPED
[INFO] BRMO soap bevragingsservice ........................ SKIPPED
[INFO] BRMO STUF BG 204 ................................... SKIPPED
[INFO] BRMO distributie ................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  39.756 s (Wall Clock)
[INFO] Finished at: 2019-10-12T10:12:27+02:00
[INFO] ------------------------------------------------------------------------


RUMM-1052 Remove the SDK Benchmark data

What does this PR do?
Remove the SDK Benchmark data. If need be, those information will stay available upon demand (contact the support team).

Codecov Report

Merging #487 (2b2d3c1) into master (2d92c61) will increase coverage by 0.34%.
The diff coverage is n/a.


⚠ Jenkins Plugins Artifactory has degraded performance

In f1196c4, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1187 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 4b87ebd after 18 minutes.


update ppdiffusers pipelines

PR types

New features
PR changes

Models & Docs
Description

ppdiffusers pipelines文档修改升级，新增任务展示，针对ppdiffusers能力进行整理输出
新增audio diffusion推理脚本和权重
新增paint by example推理脚本和权重

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhangxu44 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Sweep ICAv2 OpenAPI 204 empty content

See why I sweep it!
204 No Content ditto https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204
https://github.com/umccr-illumina/libica/blob/adf04937d50000c838c317955b57c3152ca31cea/sweep.py#L4-L10


Documentation is limited

Wondering what would be the proper procedure to follow to get vialer up and running.
I have installed docker and ran:
/path/to/vialer-middleware/docs/ci.sh
everything gets installed and tested just fine (No errors reported)
then I tried running:
/path/to/vialer-middleware/deploy/run.sh
/path/to/vialer-middleware/deploy/run.sh mysql localhost 3306
but it fail to connect to the database as there is not database for  vialer created ( I was assuming that  ci.sh would take care of that.
Is there something that I'm missing?

Hello Ron Luna,
Thanks for opening this issue.
The project can be ran with docker-compose. In the root folder execute the following commands:
docker-compose build
docker-compose up
After that it still needs some configuration for which we will create the documentation. Keep in mind though that this project (in it's current state) will never work as a drop in solution. The source-code is open to give insight on how we solved some problems and contains code that only will work in our situation.
I will add some documentation to the roadmap on what code to remove/adjust to make it a solid base that can be used by anyone.
If you have any further questions let me know.


Avoid cloning in TreeNode.children_nodes() implementations where possible using Cow

Avoid cloning in TreeNode.children_nodes() implementations where possible using Cow

Although there is test failure:
SELECT TIMESTAMPTZ '2022-01-01 01:10:00 America/Los_Angeles' as ts_geo
[Diff] (-expected|+actual)
    2021-12-31T14:10:00Z
-   2021-12-31T19:10:00Z
+   2021-12-31T18:10:00Z
    2021-12-31T23:10:00Z
    2022-01-01T09:10:00Z
at test_files/timestamps.slt:1730

But I cannot reproduce it locally. Maybe it is flaky or due to forked repo setting? 🤔 Seems an unrelated failure.

Although there is test failure:
SELECT TIMESTAMPTZ '2022-01-01 01:10:00 America/Los_Angeles' as ts_geo
[Diff] (-expected|+actual)
    2021-12-31T14:10:00Z
-   2021-12-31T19:10:00Z
+   2021-12-31T18:10:00Z
    2021-12-31T23:10:00Z
    2022-01-01T09:10:00Z
at test_files/timestamps.slt:1730

But I cannot reproduce it locally. Maybe it is flaky or due to forked repo setting? 🤔 Seems an unrelated failure.

Oh, I didn't notice the failures.
But, that's weird. I don't see them locally either.
And there is this clippy error too:
error: unused import: `exec_err as _exec_err`
   --> datafusion/common/src/error.rs:561:9

but I didn't touch that file.

Let me merge this first and see how CI works in DataFusion repo.


media-types: Fix broken links

Related to https://github.com/distribution/distribution/pull/4101, This PR move spec/manifest-v2-2.md to content/spec/manifest-v2-2.md

updated according to @sudo-bmitch 's suggestions.


Statistic issue

Hey , all right done with miningcore , and it's running :D
but on ste page , the statistic is
Network's Hash Rate
0 H/s
but in
Network Difficulty
3.23494 P
here is the json output :
0 |
-- | --
id | "eth1"
coin |
type | "ETH"
algorithm | "Dagger-Hashimoto"
ports |
3072 |
listenAddress | "x.x.x.x"
difficulty | 0.1
varDiff |
minDiff | 0.05
targetTime | 15
retargetTime | 90
variancePercent | 30
3073 |
listenAddress | "x.x.x.x"
difficulty | 5000
paymentProcessing |
enabled | true
minimumPayment | 0.01
payoutScheme | "PPLNS"
payoutSchemeConfig |
factor | 2
minimumPaymentToPaymentId | 5
keepUncles | false
keepTransactionFees | false
clientConnectionTimeout | 600
jobRebroadcastTimeout | 0
blockRefreshInterval | 500
poolFeePercent | 0.65
address | "wallet"
addressInfoLink | "https://etherscan.io/address/wallet"
poolStats |
connectedMiners | 0
poolHashrate | 0
validSharesPerSecond | 0
networkStats |
networkHashrate | 0
networkDifficulty |<PHONE_NUMBER>746226
lastNetworkBlockTime | "2018-03-21T21:34:46.240364"
blockHeight | 5297414
connectedPeers | 1
topMiners |
0 |
miner | "wallet"
hashrate | 298629739.7739987
sharesPerSecond | 0.18427676510598837
totalPaid | 0
you can see : networkHashrate | 0

Please use the issue template:
Description
[Description of the issue]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior
[What you expect to happen]
Actual behavior
[What actually happens]
Reproduces how often
[What percentage of the time does it reproduce?]
Version
If you are using released version, please state your version.
If you are using clone from dev branch, please state current commit hash.
Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, log, configuration or data that might be necessary to reproduce the issue.

Network diff for Ethereum based chains is not available from the coin daemon itself. The only option is to fetch the value from external sources at the UI level.


Race condition / bad initialization order during game start vs chunk generation

This just happened as I was trying to test in a Heightmap world with the Sample module enabled, so nothing particularly unusual. The chunk I started in and a bunch around me failed to generate as a chunk generator thread died. Based on logs it appears like chunk gen started before all blocks were registered? Might specifically be an OakTrunk from a tree attempting to generate. That seems sort of odd and prone to problems if something in or near the starting chunk needs a block that hasn't finished registering yet.
Log snippet:
22:55:55.748 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:stone with id 25
22:55:55.755 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:water]
22:55:55.755 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:water with id 26
22:55:55.758 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Ice]
22:55:55.758 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Ice with id 27
22:55:55.764 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Sand]
22:55:55.764 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Sand with id 28
22:55:55.767 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Grass]
22:55:55.767 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Grass with id 29
22:55:55.771 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Snow]
22:55:55.772 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Snow with id 30
22:55:55.774 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Dirt]
22:55:55.774 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Dirt with id 31
22:55:55.941 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:OakTrunk]
22:55:55.941 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:OakTrunk with id 32
22:55:55.969 [Chunk-Generator-4] ERROR o.t.u.concurrency.TaskProcessor - Error in thread Chunk-Generator-4
java.lang.NullPointerException: null
    at org.terasology.world.block.loader.BlockFamilyDefinitionData.<init>(BlockFamilyDefinitionData.java:44)
    at org.terasology.world.block.loader.BlockFamilyDefinition.getData(BlockFamilyDefinition.java:67)
    at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.createBaseData(BlockFamilyDefinitionFormat.java:311)
    at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.deserialize(BlockFamilyDefinitionFormat.java:139)
    at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.deserialize(BlockFamilyDefinitionFormat.java:130)
    at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
    at com.google.gson.Gson.fromJson(Gson.java:879)
    at com.google.gson.Gson.fromJson(Gson.java:817)
    at org.terasology.world.block.loader.BlockFamilyDefinitionFormat.load(BlockFamilyDefinitionFormat.java:95)
    at org.terasology.world.block.loader.BlockFamilyDefinitionFormat.load(BlockFamilyDefinitionFormat.java:69)
    at org.terasology.assets.module.UnloadedAssetData$AssetSourceResolver.load(UnloadedAssetData.java:292)
    at org.terasology.assets.module.UnloadedAssetData.load(UnloadedAssetData.java:180)
    at org.terasology.assets.module.ModuleAssetDataProducer.getAssetData(ModuleAssetDataProducer.java:228)
    at org.terasology.assets.AssetType.lambda$reload$1(AssetType.java:356)
    at org.terasology.assets.AssetType$$Lambda$73/330551672.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.terasology.assets.AssetType.reload(AssetType.java:354)
    at org.terasology.assets.AssetType.getNormalAsset(AssetType.java:383)
    at org.terasology.assets.AssetType.getAsset(AssetType.java:262)
    at org.terasology.assets.management.AssetManager.getAsset(AssetManager.java:223)
    at org.terasology.world.block.internal.BlockManagerImpl.loadFamily(BlockManagerImpl.java:266)
    at org.terasology.world.block.internal.BlockManagerImpl.getBlockFamily(BlockManagerImpl.java:248)
    at org.terasology.world.block.internal.BlockManagerImpl.getBlock(BlockManagerImpl.java:306)
    at org.terasology.core.world.generator.trees.TreeGeneratorLSystem.generate(TreeGeneratorLSystem.java:71)
    at org.terasology.core.world.generator.rasterizers.TreeRasterizer.generateChunk(TreeRasterizer.java:57)
    at org.terasology.world.generation.WorldImpl.rasterizeChunk(WorldImpl.java:64)
    at org.terasology.world.generation.BaseFacetedWorldGenerator.createChunk(BaseFacetedWorldGenerator.java:65)
    at org.terasology.world.chunks.localChunkProvider.LocalChunkProvider$1.run(LocalChunkProvider.java:634)
    at org.terasology.utilities.concurrency.TaskProcessor.run(TaskProcessor.java:50)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
22:55:55.977 [Chunk-Generator-2] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Cactus]
22:55:55.977 [Chunk-Generator-2] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Cactus with id 33
22:55:55.991 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:RedLeaf]
22:55:55.992 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:RedLeaf with id 34
22:55:56.002 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:PineTrunk]
22:55:56.003 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:PineTrunk with id 35
22:55:56.005 [Chunk-Generator-3] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:OakTrunk]
22:55:56.005 [Chunk-Generator-3] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:OakTrunk with id 36
22:55:56.014 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:DarkLeaf]
22:55:56.014 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:DarkLeaf with id 37
22:55:56.047 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:GreenLeaf]
22:55:56.047 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:GreenLeaf with id 38
22:55:57.498 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:chest]
22:55:57.498 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.LEFT with id 39
22:55:57.498 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.RIGHT with id 40
22:55:57.499 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.FRONT with id 41

Screenie:

Edit: Linking to PR #2074 as I figure this might end up relating to how we go from the main menu to in-game (fully load and register things as part of the preview/configure stage?)

Happened again, or something very similar (shapes?), this time on starting an Island World from the PolyWorld module. Again appears like chunk generation started too early before everything had finished registering:
21:31:34.389 [main] WARN  o.t.rendering.nui.asset.UIFormat - Field 'crosshairIcon' not recognized for interface org.terasology.rendering.nui.UIWidget in {"type":"UICrosshair","id":"crosshair","crosshairIcon":"engine:gui#crosshair","chargeStages":["engine:gui#crosshairCharge1","engine:gui#crosshairCharge2","engine:gui#crosshairCharge3","engine:gui#crosshairCharge4","engine:gui#crosshairCharge5","engine:gui#crosshairCharge6","engine:gui#crosshairCharge7","engine:gui#crosshairCharge8"],"layoutInfo":{"use-content-width":true,"use-content-height":true,"position-horizontal-center":{},"position-vertical-center":{}}}
21:31:34.556 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:stone]
21:31:34.556 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:stone with id 10
21:31:34.563 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:water]
21:31:34.563 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:water with id 11
21:31:34.567 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Ice]
21:31:34.567 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Ice with id 12
21:31:34.575 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Sand]
21:31:34.575 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Sand with id 13
21:31:34.577 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Grass]
21:31:34.578 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Grass with id 14
21:31:34.581 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Snow]
21:31:34.581 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Snow with id 15
21:31:34.585 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Dirt]
21:31:34.585 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Dirt with id 16
21:31:34.587 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[engine:air]
21:31:34.587 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block engine:air with id 17
21:31:34.595 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:TallGrass1]
21:31:34.596 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:TallGrass1 with id 18
21:31:34.598 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:TallGrass2]
21:31:34.599 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:TallGrass2 with id 19
21:31:34.600 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:TallGrass3]
21:31:34.601 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:TallGrass3 with id 20
21:31:34.603 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Dandelion]
21:31:34.603 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Dandelion with id 21
21:31:34.605 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Glowbell]
21:31:34.606 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Glowbell with id 22
21:31:34.608 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Iris]
21:31:34.608 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Iris with id 23
21:31:34.611 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Lavender]
21:31:34.611 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Lavender with id 24
21:31:34.614 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:RedClover]
21:31:34.614 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:RedClover with id 25
21:31:34.617 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:RedFlower]
21:31:34.617 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:RedFlower with id 26
21:31:34.620 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Tulip]
21:31:34.620 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Tulip with id 27
21:31:34.623 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:YellowFlower]
21:31:34.623 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:YellowFlower with id 28
21:31:34.626 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:BigBrownShroom]
21:31:34.626 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:BigBrownShroom with id 29
21:31:34.629 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:BrownShroom]
21:31:34.629 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:BrownShroom with id 30
21:31:34.632 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:RedShroom]
21:31:34.632 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:RedShroom with id 31
21:31:34.878 [main] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=-168 y=-197 w=168 h=197) in 166ms.
21:31:34.944 [main] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=-474 y=0 w=474 h=405) in 46ms.
21:31:34.974 [main] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=0 y=-168 w=888 h=168) in 18ms.
21:31:34.987 [main] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=0 y=0 w=474 h=102) in 5ms.
21:31:35.701 [Chunk-Generator-7] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Cactus]
21:31:35.704 [Chunk-Generator-7] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Cactus with id 32
21:31:35.755 [Chunk-Generator-1] ERROR o.t.u.concurrency.TaskProcessor - Error in thread Chunk-Generator-1
java.lang.NullPointerException: null
	at org.terasology.world.block.shapes.BlockShapeImpl.doReload(BlockShapeImpl.java:79)
	at org.terasology.world.block.shapes.BlockShapeImpl.doReload(BlockShapeImpl.java:44)
	at org.terasology.assets.Asset.reload(Asset.java:98)
	at org.terasology.assets.AssetType.loadAsset(AssetType.java:530)
	at org.terasology.assets.AssetType.lambda$reload$1(AssetType.java:358)
	at org.terasology.assets.AssetType$$Lambda$73/1663888181.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.terasology.assets.AssetType.reload(AssetType.java:354)
	at org.terasology.assets.AssetType.getNormalAsset(AssetType.java:383)
	at org.terasology.assets.AssetType.getAsset(AssetType.java:262)
	at org.terasology.assets.management.AssetManager.getAsset(AssetManager.java:223)
	at org.terasology.assets.management.AssetManager.getAsset(AssetManager.java:203)
	at org.terasology.assets.management.AssetManager.getAsset(AssetManager.java:187)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$AssetTypeAdapterFactory$1.read(BlockFamilyDefinitionFormat.java:371)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$AssetTypeAdapterFactory$1.read(BlockFamilyDefinitionFormat.java:354)
	at com.google.gson.Gson.fromJson(Gson.java:879)
	at com.google.gson.Gson.fromJson(Gson.java:944)
	at com.google.gson.Gson$1.deserialize(Gson.java:138)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.setObject(BlockFamilyDefinitionFormat.java:302)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.deserializeSectionDefinitionData(BlockFamilyDefinitionFormat.java:219)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.deserialize(BlockFamilyDefinitionFormat.java:147)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat$BlockFamilyDefinitionDataHandler.deserialize(BlockFamilyDefinitionFormat.java:130)
	at com.google.gson.TreeTypeAdapter.read(TreeTypeAdapter.java:58)
	at com.google.gson.Gson.fromJson(Gson.java:879)
	at com.google.gson.Gson.fromJson(Gson.java:817)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat.load(BlockFamilyDefinitionFormat.java:95)
	at org.terasology.world.block.loader.BlockFamilyDefinitionFormat.load(BlockFamilyDefinitionFormat.java:69)
	at org.terasology.assets.module.UnloadedAssetData$AssetSourceResolver.load(UnloadedAssetData.java:292)
	at org.terasology.assets.module.UnloadedAssetData.load(UnloadedAssetData.java:180)
	at org.terasology.assets.module.ModuleAssetDataProducer.getAssetData(ModuleAssetDataProducer.java:228)
	at org.terasology.assets.AssetType.lambda$reload$1(AssetType.java:356)
	at org.terasology.assets.AssetType$$Lambda$73/1663888181.run(Unknown Source)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.terasology.assets.AssetType.reload(AssetType.java:354)
	at org.terasology.assets.AssetType.getNormalAsset(AssetType.java:383)
	at org.terasology.assets.AssetType.getAsset(AssetType.java:262)
	at org.terasology.assets.management.AssetManager.getAsset(AssetManager.java:223)
	at org.terasology.world.block.internal.BlockManagerImpl.loadFamily(BlockManagerImpl.java:264)
	at org.terasology.world.block.internal.BlockManagerImpl.getBlockFamily(BlockManagerImpl.java:246)
	at org.terasology.world.block.internal.BlockManagerImpl.getBlock(BlockManagerImpl.java:304)
	at org.terasology.core.world.generator.trees.TreeGeneratorCactus.generate(TreeGeneratorCactus.java:34)
	at org.terasology.core.world.generator.rasterizers.TreeRasterizer.generateChunk(TreeRasterizer.java:57)
	at org.terasology.world.generation.WorldImpl.rasterizeChunk(WorldImpl.java:64)
	at org.terasology.world.generation.BaseFacetedWorldGenerator.createChunk(BaseFacetedWorldGenerator.java:65)
	at org.terasology.world.chunks.localChunkProvider.LocalChunkProvider$1.run(LocalChunkProvider.java:634)
	at org.terasology.utilities.concurrency.TaskProcessor.run(TaskProcessor.java:50)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
21:31:36.388 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:chest]
21:31:36.388 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.LEFT with id 33
21:31:36.388 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.RIGHT with id 34
21:31:36.388 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.FRONT with id 35
21:31:36.388 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:chest.BACK with id 36
21:31:36.392 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:companion]
21:31:36.392 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:companion with id 37
21:31:36.408 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:brick:engine:stair]
21:31:36.408 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:brick:engine:stair.LEFT with id 38
21:31:36.408 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:brick:engine:stair.RIGHT with id 39
21:31:36.409 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:brick:engine:stair.FRONT with id 40
21:31:36.409 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:brick:engine:stair.BACK with id 41
21:31:36.413 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Tnt]
21:31:36.413 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Tnt with id 42
21:31:36.436 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:brick]
21:31:36.436 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:brick with id 43
21:31:36.440 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Plank]
21:31:36.440 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Plank with id 44
21:31:36.453 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:lava]
21:31:36.453 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:lava with id 45
21:31:36.475 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Torch]
21:31:36.475 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Torch.TOP with id 46
21:31:36.475 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Torch.LEFT with id 47
21:31:36.475 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Torch.RIGHT with id 48
21:31:36.475 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Torch.FRONT with id 49
21:31:36.476 [main] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Torch.BACK with id 50
21:31:36.620 [Chunk-Generator-3] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=-1024 y=-1024 w=856 h=1024) in 137ms.
21:31:37.191 [Chunk-Generator-7] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=0 y=-920 w=888 h=752) in 95ms.
21:31:37.196 [Chunk-Generator-4] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=-168 y=-1024 w=168 h=827) in 214ms.
21:31:37.831 [Chunk-Generator-5] INFO  o.t.p.graph.GraphFacetProvider - Created graph for (x=0 y=102 w=588 h=922) in 58ms.
21:31:38.666 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:OakTrunk]
21:31:38.666 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:OakTrunk with id 51
21:31:38.670 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:GreenLeaf]
21:31:38.671 [Chunk-Generator-0] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:GreenLeaf with id 52
21:31:41.545 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:PineTrunk]
21:31:41.545 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:PineTrunk with id 53
21:31:41.548 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:DarkLeaf]
21:31:41.548 [Chunk-Generator-4] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:DarkLeaf with id 54
21:31:41.611 [Chunk-Generator-5] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:RedLeaf]
21:31:41.611 [Chunk-Generator-5] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:RedLeaf with id 55
21:32:39.116 [Engine-Task-Pool] INFO  o.t.rendering.opengl.PostProcessor - Screenshot 'Terasology-160802213238-1152x720.jpg' saved!
21:32:42.100 [main] INFO  o.t.p.i.ReadWriteStorageManager - Saving - Creating game snapshot

Rest of the world was fine but the initial dead chunks didn't come back even after making distance to let the area unload then coming back:

After game restart the world loaded fine with the affected chunks regenerated and fully visible again.

I encountered this once, too. I did not investigate further, but it's good to see this issue as a note.

Hey, since I'll be out for days, note something here, hope it helpful for others who want to fix this bug. Here is the TimeLine before game began :

Class LoadPrefabs

main registered some blocks like Core:DoorTop.LEFT

Class InitialiseWorld :

chunkGenerator initialized, but these threads didn't work since there were no task in taskQueue
main registered block engine:unloaded

Class InitialiseWorldGenerator

main registered some blocks like engine:air, core:TallGrass3

Class SetupLocalPlayer

main added tasks to taskQueue
chunkGenerator began to work, they registered blocks

Class AwaitCharacterSpawn

main registered some blocks like core:chest.FRONT,core:Tnt
chunkGenerator still registered two block before game began

It seems that the blocks causing bug could only be in AwaitCharacter ? Maybe this TimeLine didn't corresponde to the bug case since I did not encountered  the bug :-(
Problems :

What's class AwaitCharacter for ? Is the blocks registered there needed to generate chunk ?
If we can detect that the block needed for chunk haven't been registered, we can ask the thread to wait, the problem is how to detect ? :-(
Or maybe we can try : when catch this error, put this task back to taskQueue (really ugly solution, may cause other problems)

20:35:07.518 [Chunk-Generator-6] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:Cactus]
20:35:07.518 [Chunk-Generator-6] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:Cactus with id 32
20:35:07.553 [Chunk-Generator-7] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:OakTrunk]
20:35:07.554 [Chunk-Generator-7] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:OakTrunk with id 33
20:35:07.585 [Chunk-Generator-2] ERROR o.t.u.concurrency.TaskProcessor - Error in thread Chunk-Generator-2
java.lang.NullPointerException: null
	at org.terasology.world.block.Block.setCollision(Block.java:629)
	at org.terasology.world.block.internal.BlockBuilder.constructCustomBlock(BlockBuilder.java:123)
	at org.terasology.world.block.internal.BlockBuilder.constructTransformedBlock(BlockBuilder.java:104)
	at org.terasology.world.block.family.HorizontalBlockFamilyFactory.createBlockFamily(HorizontalBlockFamilyFactory.java:53)
	at org.terasology.world.block.loader.BlockFamilyDefinition.createFamily(BlockFamilyDefinition.java:57)
	at org.terasology.world.block.internal.BlockManagerImpl.loadFamily(BlockManagerImpl.java:278)
	at org.terasology.world.block.internal.BlockManagerImpl.getBlockFamily(BlockManagerImpl.java:246)
	at org.terasology.world.block.internal.BlockManagerImpl.getBlock(BlockManagerImpl.java:304)
	at org.terasology.core.world.generator.trees.TreeGeneratorCactus.generate(TreeGeneratorCactus.java:34)
	at org.terasology.core.world.generator.rasterizers.TreeRasterizer.generateChunk(TreeRasterizer.java:57)
	at org.terasology.world.generation.WorldImpl.rasterizeChunk(WorldImpl.java:64)
	at org.terasology.world.generation.BaseFacetedWorldGenerator.createChunk(BaseFacetedWorldGenerator.java:65)
	at org.terasology.world.chunks.localChunkProvider.LocalChunkProvider$1.run(LocalChunkProvider.java:620)
	at org.terasology.utilities.concurrency.TaskProcessor.run(TaskProcessor.java:50)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
20:35:07.587 [Chunk-Generator-7] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:GreenLeaf]
20:35:07.587 [Chunk-Generator-7] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:GreenLeaf with id 34
20:35:07.951 [Chunk-Generator-2] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:PineTrunk]
20:35:07.952 [Chunk-Generator-2] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:PineTrunk with id 35
20:35:07.956 [Chunk-Generator-2] INFO  o.t.w.b.internal.BlockManagerImpl - Registered BlockFamily[core:DarkLeaf]
20:35:07.956 [Chunk-Generator-2] INFO  o.t.w.b.internal.BlockManagerImpl - Registered Block core:DarkLeaf with id 36

Is that the same bug ?  Encountered that in Heightmap world with the Sample module enabled. After that, game got stuck in the game loading interface(not crash, so no CR appeared).

That does look pretty similar, yeah. Block registration still going after the crash.
I missed the earlier comment but after the complexities of this situation have kept piling up I wonder if it is a fix better saved for when we expand the stages between the main menu and appearing in-game.
Right now possibly too much stuff is happening at once - registration jumbled in with chunk generator threads. Part of GSOC item #2774 involves better segregating these stages so you'd probably have several UI steps like so:

Pick your modules (exists)
Pick your world based on what's available in the modules (exists)
Load up a preview environment (can be skipped + existing world preview is buggy)
Register all blocks etc that might be used during world generation*
Register all world configuration options (like frequency of caves, height of mountains ..)
Generate a 2D preview map of the world, allowing the user to tweak at config and regen
Start generating actual chunks as the player readies for entering the world (optional: checkbox to enter world automatically when ready)
Spawn the player and start playing

That would completely avoid this issue if you thus get block registration out of the way before generating a single chunk plus improve the overall process IMHO. You could also engage options like pre-generating a far larger part of the world before dropping in the player, if for instance you have a slow server and don't want a ton of lag while moving around.
However one * - I am unsure how our lazy assigning of block ids factor into this. Not every possible block combination gets an id right away, since with the amount of shapes we support that could overflow the block id even as a short pretty easily. Maybe the issue here isn't that block registration is still pending, but that new block combos have been found as part of world generation, and before those are fully registered an available chunk generator has attempted to rasterize a chunk into blocks.
Maybe we need to involve better BlockFamilies as well, so you might prepare all possible Blocks by name but not give out ids to every possible shape combo until needed.


scripts: extract_dts_includes : Changes to prepare for code generation

2 changes required to prepare extract_dts_includes solution for code generation

Codecov Report

Merging #9256 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9256   +/-   ##
=======================================
  Coverage   52.35%   52.35%
=======================================
  Files         201      201
  Lines       25290    25290
  Branches     5286     5286
=======================================
  Hits        13240    13240
  Misses       9965     9965
  Partials     2085     2085

Continue to review full report at Codecov.

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


remove the netplan config

Latest version of netagent 2 no longer requires setting the NLB IP on the host, hence the netplan config should be removed.

Removed netplan config in v1.0.5


Effect abbreviations are not properly checked

We are trying to define an effect that allows only one kind of exception to be thrown:
module Raising

open FStar.Pervasives
open FStar.Exn

// inferred type: Raises : ex:Prims.exn -> a:Type0 -> Prims.Tot Effect
effect Raises (ex:exn) (a:Type)  =
    Exn a (requires True)
        (ensures (function
                | (V _) -> True
                | (E e) -> e == ex
                | _ -> False
        ))

exception Bad
exception ReallyBad

val u : nat -> Raises Bad nat
let u i = if i > 10
    then i
    else raise Bad                  // expected to work
    // else raise ReallyBad         // expected to fail type checking

Checking this in the tutorial system produces:
Raising(18,8-18,29): (Error 12) Expected type "Type"; got type "Prims.exn"
Raising(20,9-20,10): (Error 188) Expected expression of type "Raising.Bad"; got expression "i" of type "Prims.nat" (see also Raising(19,6-19,7))
2 errors were reported (see above)

I can see that the second error message might be a consequence, in a strange way, of the misunderstanding underlying the first.
But I cannot understand the first error message at all, especially since its range indicates the whole type expression nat -> Raises Bad nat, which should rather obviously be a Type and not a Prims.exn.

Even though I didn't prove false, I'm marking this as an unsoundness since this is very scary:
module Bug1370

effect Ouch (a:Type) = False

let x () : Ouch unit = () (* a proof of False? *)

Probably worth discussing at the all hands.

Part of the culprit is the logic in solve_c, which succeeds in subtyping Tot unit to Ouch unit only because Ouch is marked with the Total cflag. Removing the special-casing for Total, the definition of x fails. I'm not sure I know what each cflag exactly represents, so not touching for now.

We decided today to forbid this kind of effect declarations, by enforcing that the first argument on the LHS is used as the return type in the RHS. This case would fail since a is not False. Nik will work on it.

You're now forced to write:
effect Ouch (a:Type) = Tot False

making the computation type on the RHS explicit.
And then, further, this fails with
(Error 316) Result type of effect abbreviation `a` does not match the result type of its definition `Prims.l_False`

Can we close this now? @mtzguido

Yes, updating the test cases and closing soon.


Dataset Not available at link

Hi
Dataset mentioned is not available at link.
https://archive.ics.uci.edu/ml/machine-learning-databases/00442/
Kindly share correct dataset path and also what folders are expected in this dataset.
Does https://archive.ics.uci.edu/static/public/442/detection+of+iot+botnet+attacks+n+baiot.zip will work or not?

Hey,
The link seems to be broken, thanks for pointing this out. I think the link you are suggesting works. I updated the readme.


Combine canvases

Can multiple markers be combined to one canvas? Making an individual canvas for each marker lags a lot when you have many markers.

It is a good idea, to keep a single canvas open across the map and translate geocoordinates to x/y points on that canvas. I mean that's what leaflet itself does.
Would be a fun exercise for a rainy day!

Sorry, but I am not sure I understood the answer.


Resolves #126 - Equality on JsonValue should not differentiate betwee…

…n Short and String

Cheers!


发现一个关于confirm提交的问题

你们提供的2.5.1的版本的confirm中我发现一个bug，弹出的confirm框如果用tab键将确定按钮选中再点击enter按键来提交的话，会被提交两次！这个问题有解决方法吗？

代码是这样子的：

测试confirm的bug
function test(){
	$.confirm({
		keyboardEnabled: true,
		title: 'confirm bug 测试',
		content: '请先使用Tab键将submit选中，然后点击键盘enter键：',
		//confirmKeys: [13],//return
		cancelKeys: [27],//escape
		confirmButton: 'submit',
		cancelButton: 'cancel',
		confirm: function(){
			$(".main-content").append("dkfsadfjsdh---");
		}
	});
}

v2.5.1 is really old, current is 3.1.0, i would suggest you to please update.
The problem here is, the button is getting triggered twice, once from the button click, and other from the keys event.
turn off the keys event, remove the enter button key for confirm confirmKeys: []
this will solve the problem for you.

Yes,you really got it rightly.But in fact,you could not really correct it just turn off the the enter button key for confirm confirmKeys: [].Why?I really like the keys event,at least the cancle key event:cancelKeys:[]. Whether cna I correct this problem by reserve the cancel key event but not totally turn off the key event at v2.5.1

I can't think of a workaround this, you'll have to prevent adding 'enter' and 'space' keys event, as those click buttons too.

The bug exists in the latest version too,
http://jsfiddle.net/craftpip/k7sxL4dv/
not with enter button, but with space button.

If upgrading to v3 is not feasible for you, i would recommend you to build a wrapper function for the newer version, which will take in v2 arguments, alter them and pass it on to the v3 function

yeah, i also think i need to upgrade to the latest version,thanks for your answer. if any other problem i meet in the future，i will come here to look for help. thanks a lot anyway!


CI: Do not build, but do update, repos when pulling them

Without a '-d' on the 'go get', the script ties to build the repos,
and for repos that do not work under 'go build', this leaves errors
in the CI logs. We don't need a build at this stage as we invoke the
repo specific builds later on.
Also, some CIs do not clean out their build trees between builds, and
thus have repos already present - so add an 'update -u' flag as well.
Fixes: #887
Signed-off-by: Graham Whaley<EMAIL_ADDRESS>

lgtm
But I see these errors on the ci-metrics Job:
05:42:26 hacking our file ownerships
05:42:26  Fetch the tests repo
05:42:26 # cd /srv/jenkins/workspace/workspace/clear-containers-tests-16.04-PR/go/src/github.com/clearcontainers/tests; git pull --ff-only
05:42:26 There is no tracking information for the current branch.
05:42:26 Please specify which branch you want to merge with.
05:42:26 See git-pull(1) for details.
05:42:26
05:42:26     git pull <remote> <branch>
05:42:26
05:42:26 If you wish to set tracking information for this branch you can do so with:
05:42:26
05:42:26     git branch --set-upstream-to=origin/<branch> PR_886
05:42:26
05:42:26 package github.com/clearcontainers/tests: exit status 1

Yeah, I've not gotten to dig into those errors yet. To note then, currently the metrics CI is a bare metal Jenkins that is not clearing out its build trees between jobs. That may thus have an effect here, particularly if we are rebuilding a PR, as that could be trying to re-use the same branch name.
It is pretty easy for me to switch the config to delete the build trees between runs - it will cost us some download time per run should be all.

same error happening on #895

The Error:
10:27:16  Fetch the tests repo
10:27:16 # cd /srv/jenkins/workspace/workspace/clear-containers-tests-16.04-PR/go/src/github.com/clearcontainers/tests; git pull --ff-only
10:27:16 There is no tracking information for the current branch.
10:27:16 Please specify which branch you want to merge with.
10:27:16 See git-pull(1) for details.
10:27:16
10:27:16     git pull <remote> <branch>
10:27:16
10:27:16 If you wish to set tracking information for this branch you can do so with:
10:27:16
10:27:16     git branch --set-upstream-to=origin/<branch> PR_886
10:27:16

looks like it comes from this fragment of the Jenkins script:
# nominally, as we are about to test the tests repo, maybe we don't
# need this...
echo " Fetch the tests repo"
go get -d -u ${TESTS_REPO_NAME}

I'm thus wondering if the got get -d -u cannot handle the non-fast-forward branch. I could inject a git reset in the script before that line - what do you think @jcvenegas ?

lgtm

A note/update on this then. This is likely:

related to the metrics Jenkins build bots being bare-metal machines
that currently do not delete their build trees between builds
and our git mangling in the scripts are not written to cope with potentially 'dirty' git trees right now

Something I saw locally was if I canceled a Jenkins job whilst it was doing some git work, which left me with a somewhat 'dirty' git repo. Subsequent CI runs then complained that they could not FF that git repo (which seems to be what we have above).
Quick short/mid term fix is for me to tell Jenkins to delete the build trees after each build. This has a number of up/downsides:

Gives us a cleaner build env (good...)
Will have to download everything each build (not so good)
Will therefore take a little longer to run each build (also not so good)

I'll go tick that box now so we can get a more stable metrics CI system, at the cost of speed and bandwidth...
And then I'll nudge a rebuild (or potentially two to get rid of the tree on the first one and do a full clean build on the second)...

Project is frozen. Work has moved over to: https://github.com/kata-containers
closing.


[Q] Cannot login to Wandb (SockClient bug??)

here is my full error at first when wandb login
Traceback (most recent call last):
  File "/home/yhn/.conda/envs/yh/bin/wandb", line 8, in <module>
    sys.exit(cli())
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/cli/cli.py", line 97, in wrapper
    return func(*args, **kwargs)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/cli/cli.py", line 236, in login
    wandb.setup(settings=login_settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 312, in setup
    ret = _setup(settings=settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 307, in _setup
    wl = _WandbSetup(settings=settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 293, in __init__
    _WandbSetup._instance = _WandbSetup__WandbSetup(settings=settings, pid=pid)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 106, in __init__
    self._setup()
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 234, in _setup
    self._setup_manager()
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 266, in _setup_manager
    _use_grpc=use_grpc, settings=self._settings
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_manager.py", line 128, in __init__
    svc_iface._svc_connect(port=port)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/service/service_sock.py", line 30, in _svc_connect
    self._sock_client.connect(port=port)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/lib/sock_client.py", line 102, in connect
    s.connect(("localhost", port))
socket.gaierror: [Errno -2] Name or service not known
wandb: While tearing down the service manager. The following error has occured: 'SockClient' object has no attribute '_sock'

I tried updating wandb with pip install wandb -U
and now it shows this
wandb: ERROR Find detailed error logs at: /tmp/debug-cli.yhn.log
Error: Connection to wandb service failed.
wandb: Encountered an error while tearing down the service manager: 'SockClient' object has no attribute '_sock'

and this is what I get from the debug-cli log
2024-07-22 02:41:40 ERROR Traceback (most recent call last):
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_manager.py", line 116, in _service_connect
    svc_iface._svc_connect(port=port)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/service/service_sock.py", line 30, in _svc_connect
    self._sock_client.connect(port=port)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/lib/sock_client.py", line 102, in connect
    s.connect(("localhost", port))
socket.gaierror: [Errno -2] Name or service not known

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/cli/cli.py", line 108, in wrapper
    return func(*args, **kwargs)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/cli/cli.py", line 247, in login
    wandb.setup(settings=login_settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 325, in setup
    ret = _setup(settings=settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 318, in _setup
    wl = _WandbSetup(settings=settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 303, in __init__
    _WandbSetup._instance = _WandbSetup__WandbSetup(settings=settings, pid=pid)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 114, in __init__
    self._setup()
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 250, in _setup
    self._setup_manager()
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_setup.py", line 283, in _setup_manager
    self._manager = wandb_manager._Manager(settings=self._settings)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_manager.py", line 158, in __init__
    wandb._sentry.reraise(e)
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/analytics/sentry.py", line 155, in reraise
    raise exc.with_traceback(sys.exc_info()[2])
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_manager.py", line 156, in __init__
    self._service_connect()
  File "/home/yhn/.conda/envs/yh/lib/python3.7/site-packages/wandb/sdk/wandb_manager.py", line 131, in _service_connect
    ) from e
wandb.sdk.wandb_manager.ManagerConnectionError: Connection to wandb service failed.

(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ wandb login
wandb: ERROR Find detailed error logs at: /tmp/debug-cli.yhn.log
Error: Connection to wandb service failed.
wandb: Encountered an error while tearing down the service manager: 'SockClient' object has no attribute '_sock'
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ ping localhost
ping: localhost: Name or service not known
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ ping https://wandb.ai
ping: https://wandb.ai: Name or service not known
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ ping google.com
PING google.com (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from hkg12s28-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=1 ttl=114 time=74.2 ms
64 bytes from hkg12s28-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=2 ttl=114 time=54.6 ms
64 bytes from hkg12s28-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=3 ttl=114 time=54.6 ms
64 bytes from hkg12s28-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=4 ttl=114 time=54.5 ms
64 bytes from hkg12s28-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=5 ttl=114 time=54.9 ms
^C
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 54.524/58.558/74.179/7.811 ms
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ ping wandb.ai
PING wandb.ai (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>.bc.googleusercontent.com (<IP_ADDRESS>): icmp_seq=1 ttl=109 time=8.75 ms
64 bytes from <IP_ADDRESS>.bc.googleusercontent.com (<IP_ADDRESS>): icmp_seq=2 ttl=109 time=8.96 ms
64 bytes from <IP_ADDRESS>.bc.googleusercontent.com (<IP_ADDRESS>): icmp_seq=3 ttl=109 time=8.93 ms
^C
--- wandb.ai ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 8.752/8.878/8.958/0.090 ms
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ export WANDB_BASE_URL=https://api.wandb.ai
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ wandb login
wandb: ERROR Find detailed error logs at: /tmp/debug-cli.yhn.log
Error: Connection to wandb service failed.
wandb: Encountered an error while tearing down the service manager: 'SockClient' object has no attribute '_sock'
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ rm -rf ~/.wandb
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ wandb login
wandb: ERROR Find detailed error logs at: /tmp/debug-cli.yhn.log
Error: Connection to wandb service failed.
wandb: Encountered an error while tearing down the service manager: 'SockClient' object has no attribute '_sock'
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ wandb --version
wandb, version 0.17.5
(yh) yhn@rami-4:~/TPS/RL_Agent/PPO_LSTM_v4$ python --version
Python 3.7.15

these are what I did except for uninstalling wandb.
I'm currently coding via remote development so I don't think the network is the problem.

pip uninstall wandb pip install wandb
I don't know why but this command deleted pip itself and I had to reinstall the pip.
anyways, I installed wandb and wandb login still don't work.
also I tried rebooting the system.

The problem was in the server hostname
closing the issue


Suggestion : Make it compatible with Carousel Combat Tracker

Hi, loving the timer module. Being able to set custom timer for each player has really improved the overall time management during our fights. I was thinking though that it would be cool if there was a way for it to be integrated into carousel combat tracker, to be able to see the timer in the carousel if the combat tracker is closed

I haven't used that module before, but I'll take a look at it and see if it's something that could be reasonably added.

Nice xD please let me know if you find a way to make it work, if it's too much trouble but you have an idea on how it'd work I can try and make a fork to implement compatibility if you're too busy ^^

You're free to fork as you see fit, but it's also something I'll likely work on within the week.  Would that suffice for your use case, or are you looking for something more integrated with that specific module?

Oh that's perfect thank you very much ^^

Sorry this took as long as it did, I had a bit of complications but the popout timer should now be implemented and hopefully fulfills the needs you had. Let me know if you encounter any issues with it or have suggestions for improvements.


[Bug]: Overlay of tabs view in Apache Hop GUI

Apache Hop version?
2.9.0
Java version?
java 22.0.2 2024-07-16
Operating system
Windows
What happened?
When we open more than 3 tabs and rearrange their order by dragging, sometimes the names get swapped. If we save at this point, we overwrite the pipeline with the new name. Additionally, if we switch to another tab and then return, the pipeline changes to the newly overwritten one, and the original pipeline disappears.
Issue Priority
Priority: 2
Issue Component
Component: Hop Gui

We should disable the ability to move a tab for the time being. We would then have to reorganize tab management in the DataOrch perspective.


Do not generate object array thunk for byref-like signatures

The object array thunk can't be generated for delegates with signatures that have byref-like types in them.

@davidwrighton PTAL
This was generating compilation warnings for a delegate with System.__DTString type in CoreLib. That is very familiar to TFS bug 509366 assigned to you on the Project N side.


@siteData?

if (//@siteData/.test(id)) {
这行代码报错

I have encountered the same issue as you and I noticed that you have submitted this issue. May I ask if it has been resolved?
[plugin:vite-plugin-vitepress-auto-sidebar] ENOENT: no such file or directory, scandir 'D:\work\h7ml\github\h7ml\code\docs'
/@siteData
    at Object.readdirSync (node:fs:1451:3)

I found that the plugin generates the path incorrectly. My path is "code\src" but it is looking for "code\docs". The main issue is that I don't even have a "docs" directory.

I think that in this line of code: https://github.com/QC2168/vite-plugin-vitepress-auto-sidebar/blob/main/src/index.ts#L142, you should retrieve the path from the "vitepress dev [path]" command in the "dev" script of the example's package.json file: https://github.com/QC2168/vite-plugin-vitepress-auto-sidebar/blob/main/example/package.json#L7. Instead of hardcoding the path as "docs", you should dynamically retrieve it from the command.

build error
Run pnpm build

><EMAIL_ADDRESS>build /home/runner/work/codeinterviewpro/codeinterviewpro
> vitepress build docs

  vitepress v1.0.0-alpha.60

- building client + server bundles...
[auto-sidebar] injected sidebar data successfully
[vite:build-import-analysis] Cannot destructure property 'line' of 'locate(...)' as it is undefined.
file: /@siteData
✖ building client + server bundles...
build error:
TypeError: Cannot destructure property 'line' of 'locate(...)' as it is undefined.
    at augmentCodeLocation (file:///home/runner/work/codeinterviewpro/codeinterviewpro/node_modules/.pnpm/rollup@3.1[9](https://github.com/h7ml/codeinterviewpro/actions/runs/4428076744/jobs/7766630834#step:6:10).1/node_modules/rollup/dist/es/shared/node-entry.js:2137:17)
    at Object.error (file:///home/runner/work/codeinterviewpro/codeinterviewpro/node_modules/.pnpm/rollup@3.19.1/node_modules/rollup/dist/es/shared/node-entry.js:23382:25)
    at Object.transform (file:///home/runner/work/codeinterviewpro/codeinterviewpro/node_modules/.pnpm/vite@4.1.4_sass@1.59.3/node_modules/vite/dist/node/chunks/dep-ca2[12](https://github.com/h7ml/codeinterviewpro/actions/runs/4428076744/jobs/7766630834#step:6:13)28b.js:43545:[22](https://github.com/h7ml/codeinterviewpro/actions/runs/4428076744/jobs/7766630834#step:6:23))
 ELIFECYCLE  Command failed with exit code 1.
Error: Process completed with exit code 1.```

I have encountered the same issue as you and I noticed that you have submitted this issue. May I ask if it has been resolved?
[plugin:vite-plugin-vitepress-auto-sidebar] ENOENT: no such file or directory, scandir 'D:\work\h7ml\github\h7ml\code\docs'
/@siteData
    at Object.readdirSync (node:fs:1451:3)

the plugin allows users to provide customization options, if your docs folder name is not docs, you need to provide the path parameter
in package.json
"scripts": {
  "dev": "vitepress dev src",
  "build": "vitepress build src"
}

in .vitepress/config.js
import AutoSidebar from "vite-plugin-vitepress-auto-sidebar";

export default {
  lang: "en-US",
  title: "VitePress",
  description: "Vite & Vue powered static site generator.",
  vite: {
    plugins: [AutoSidebar({
      path:'/src',
    })],
  },
  themeConfig: {
     nav: [{ text: "note", link: "/note/index" }],
  },
};


Simplify Hiero tag workflow

Currently, it is a really involved process to add all the correct tags to the shots.
Let's do the same approach as the prototype we made for Resolve. Using a simply GUI to set all the needed attributes for the shots. It will be a lot quicker on the timeline and also for the user.

implemented by https://github.com/pypeclub/pype/pull/648

implemented by https://github.com/pypeclub/pype/pull/648


X, S, Y, Z, N, A etc. class filter

Filter by class type if in laguna or manila, CCS class, CLA class, GCOE class, etc.

Guide


Add integration test

Add an integration test that sends metrics to a real statsd instance running locally (docs) in AppVeyor or Travis, and verifies that the values sent to the server are correct by using the admin endpoint on port 8126 (docs).
A unique random prefix is used so that if you run these tests locally the values don't clash.

Nice!


Module namespaces as thenables:  Add non-normative spec text

The conclusion to https://github.com/tc39/proposal-dynamic-import/issues/47 was that it is indeed intentional that the promise instance's final [[PromiseResult]] returned from import():

May not always be the module's namespace object

...in the case where it has been "overridden" by an export named "then"

May vary on each call to import() for a given specifier

...in the case where the "then"-named export is not idempotent

May not be accessible via the existing non-dynamic import syntax

Whilst this is well-specified intentional behavior, reviewers have seemed surprised by this discovery.  The capabilities it allows were not mentioned in the original motivations or use-cases.  Public educational pieces written on this proposal have not mentioned this capability.  The spec wording for Runtime Semantics: HostImportModuleDynamically talks only about consistent results:

if the host environment takes the success path once for a given referencingScriptOrModule, specifier pair, it must always do so, and the same for the failure path"

To increase awareness of this behavior, I'd like to request a spec note be added to emphasize the fact that FinishDynamicImport's step 2.f means the caller of import() does not have the subjectively-intuitive equivalent guarantees of consistency.
As I am new to spec contributions, I will proposal some loosely suggested wording at the end of Runtime Semantics: HostImportModuleDynamically that I hope others may massively refine and reword:

NOTE 1: Even if the success path is consistently taken for a given referencingScriptOrModule, specifier pair, the module can still arbitrarily override the final [[PromiseState]] and [[PromiseResult]] of the promise instance returned by each import() call if the module exports a Promise executor function named "then".  This is a natural consequence of FinishDynamicImport calling promiseCapability.[[Resolve]] with the module's [[Namespace]].

Please say if there is some existing policy on the conditions under which we allow/desire non-normative text to be added to the spec.

I don't think we should do this, because we'd end up doing it for every promise-returning API on the platform.

@domenic My understanding is that this note would only be needed if the API exports a then variable, so it shouldn't need the note on every Promise-returning API.

No, it'd be needed for any API that returns a promise for an arbitrary developer-controlled value.

@domenic But the note is specifically about module resolution: it mentions referencingScriptOrModule, specifier pair and import()
Perhaps it would be useful to have a different note for other Promise-returning APIs (like IndexedDB), but this specific note is only for module resolution.
It's not an API specification, it's just an informative note, so consensus across all APIs is not needed.
If other specifications want to, they can add a similar note, but they don't need to. The note is still useful even if it only applies to import()

We're not at the stage of talking about specific note wording yet. We're discussing whether a note should exist at all.

No, it'd be needed for any API that returns a promise for an arbitrary developer-controlled value.

I disagree.  The reason import() is special and worthy of a special note is that users arrive with a strong expectation that importing modules is an idempotent action that provides an idempotent result.  That's pretty much the module system's reason-to-exist.
In related material, https://github.com/tc39/ecma262/pull/916 makes it clear that browsers and Node prefer idempotent errors, citing various reasons.

It is crucial for browsers (and, so I've heard, for Node) that errors are cached so that telemetry can be used to identify repeatedly-encountered problems in a page.

So when the spec goes against the generally expected intuition of how a module system should work, I think it appropriate to highlight this in the spec.

Well, I guess we'll just have to agree to disagree then. As I've stated repeatedly, I don't think import() is any different from other promise-returning data-retrieval functions---all of which are idempotent unless faced with unusual thenables.
The related material you cite is fairly orthogonal; it's about the module system itself, and the impact of different states of the graph on future parsing/instantiation/evaluation. It's not about a function like import() which is called by a developer.
If you think import() is truly special in this manner compared to e.g. IndexedDB, then I think we are at an impasse, as I don't think so, and no new arguments have been presented that have worked to change my position. I suggest we close this issue, in that case.

I'm confused; in IndexedDB, you can extract things that have a "then" function? I thought it was JSON.

IndexedDB is structured clone so it doesn't apply to that, although I understand the general argument.
However this is actually the first (in ECMA262) Promise-returning construct where you can't box the object before it gets resolved into a Promise (programmatically) so it's probably at least worth having a note that typical strategies of "boxing" a Promise will have to be done before importing.
It's pretty likely .thenable modules will be fairly rare so it's almost certainly easy enough to inject an intermediate module that boxes it:
// --- Injected module
import isBoxed from "./isBoxedSymbol.js"
import * as thenableModule from "./thenableModule.js"

export default {
    [isBoxed]: true,
    module: thenableModule
}

// ---- Importer
import isBoxed from "./isBoxedSymbol.js"

// Get a boxed module regardless of whether the module is thenable or not
import('./injectedModule.js').then(obj => {
    if (!obj[isBoxed]) {
        return { [isBoxed]: true, module: obj }
    } else {
        return obj
    }
}

While this solution does mean adding another virtually identical file for every possibly thenable module, under the assumption thenable modules in practice will be quite rare I don't think it's a terrible workaround.

I'm going to close this on the basis that there are other points in the spec that re-resolve and cause plain objects to be assimilated as thenables.  See await and this thread.  Likewise there are pre-existing cases of synchronous magic export names properties: toString, valueOf.  I regard all these "features" as hazards in the context of module namespace objects, and it would be nice to have a safety-hatch/strict-mode to disable them - but that would be a separate proposal.
So I'm going to interpret dynamic import as being a new point of exposure of what was a pre-existing hazard.  @Jamesernator demonstrates a build-time protection against this hazard.  For now, the burden will be on JS educators and users to learn about this hazard.
Interestingly it sounds like IndexDB is special, but that's just a technicality.

@robpalme When I said IndexedDB is structured clone so it doesn't apply I don't mean recursive thenable assimilation doesn't apply, it's simply not possible to store a function object using structured clone so I'm not sure what the points about IndexedDB that were mentioned were intending to mean. I'd expect that if IndexedDB could store functions (whatever it would mean to store a function in a database) it would necessarily be subject to recursive thenable assimilation too.

@Jamesernator Yes, I think you were clear.  IndexDB was discussed because @domenic wanted to know why dynamic import should be regarded differently to IndexDB.  And it turns out that IndexDB is different; this hazard cannot arise in that context.  But, big picture, I'm saying that doesn't matter because there are non-IndexDB cases in the spec.  So let's not discuss IndexDB anymore ;-)

ModuleRecords aren't just plain objects; I think this should be reopened and discussed at the September TC39 meeting.

@ljharb I sympathize and think that a proposal to prevent module namespace objects being treated as thenables would have merit, but I don't see why dynamic import is the place to do that. The hazard equally applies to calling Promise.resolve() on a namespace.

It might not be the place; but such a proposal would have to block this one to ensure that it could land without being a breaking change.
ModuleRecords aren't namespaces; they're conceptually different.

(Assuming such a proposal was the direction the committee decided to go, of course)

A Module record is a spec concept that is never exposed.
All that is ever exposed is the namespace object.
Changing its behavior would already be a breaking change (Promise.resolve(ns)) so indeed is orthogonal to this proposal.

That's a fair point. However, I think the ergonomics and expectations of import() are such that it's worth discussing as part of this proposal, even if the direction ends up being "not blocking, separate proposal".

I'd rather such a discussion not be related to import (), because it is not really related.


Hook typings

I encountered the following problems when typing my hooks:

the id field is missing form HookProps
the return types of the hook id Promise<any> | void but in the documentation it is specified that a hook object can be returned.

Is there a reason for this? or is it simple typings problem? In which case I would be happy to help.
Thanks!

According to the Hook objects doc, there are a few other missing properties, including service, path, and error. These cause an issue when migrating the CLI-generated logger hook to TypeScript, as path and error don't exist on the HookProps interface.
/cc @j2L4e

indeed, I added those to #169

Closed via #169


DOC: formatting changes

made some final modifications for formatting purposes
testing updates to rtd settings for automatic rtd previews for opened PRs and for generating docs from master branch

Codecov Report

Merging #234 (bbab88b) into master (635d091) will decrease coverage by 16.05%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #234       +/-   ##
===========================================
- Coverage   53.85%   37.80%   -16.06%
===========================================
  Files          78       67       -11
  Lines        5960     5044      -916
===========================================
- Hits         3210     1907     -1303
- Misses       2750     3137      +387

Impacted Files
Coverage Δ

pyluna-common/tests/luna/common/test_utils.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...yluna-common/tests/luna/common/test_ensure_byte.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...ology/tests/luna/pathology/cli/dsa/test_dsa_viz.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...ogy/tests/luna/radiology/common/test_preprocess.py
0.00% <0.00%> (-100.00%)
:arrow_down:

.../tests/luna/radiology/unpack_images/test_unpack.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...tests/luna/pathology/cli/test_infer_tile_labels.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...sts/luna/pathology/common/test_annotation_utils.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...gy/point_annotation/refined_table/test_generate.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...refined_table/regional_annotation/test_generate.py
0.00% <0.00%> (-100.00%)
:arrow_down:

pyluna-common/tests/luna/common/test_config.py
0.00% <0.00%> (-98.77%)
:arrow_down:

... and 19 more

Continue to review full report at Codecov.

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


Menu bar independent of ImageJ

Curtis had some suggestions on how to make sure it also works within ImageJ, but first let's just get it working in standalone.

Using a different menuRoot, no?

@ctrueden thank you for the reminder/pointer!

As long as you aren't coding your own JMenuBar / JMenu / JMenuItem. If I see you doing that, I will feel 😿 . I really hope the MenuService is good enough for your needs! If not, we can discuss how to improve it.

Closed via c45fe8e2fc9e869ff324fe7fe49db52abb8b8439 and c4c0b16a85dd0d0245a452e0d593482ed141829a.
To achieve this, we ended up switching to a JavaFX container, since it gave us the ability to include additional UI elements beyond the SceneryPanel itself.


Look into data ownership relationships in Edge Db to better support cascading delete

I think it would be good if we had clear 'ownership' relationships between objects in Edge Db.
For instance - the Consent statements of a patient belong to a Patient - so don't make much sense if they are retained after a patient is deleted. I believe it is possible to express some of this in the edge db schemas.
I think the end goal is that data can be systematically removed from a db - with broad delete statements. So for instance - if there was a 'bad run' noticed (sequencer machine was contaminated say and this was discovered a month later).
We might say that the operations are the delete/alter any Dataset using those Artifacts.
Then delete the Run itself.
With the expectation that all files uploaded by the run are also cascade deleted.

This might be a good ticket to do immediately after we go to native Edgeql queries.
Because part of the 'db-test' layer I think will be to execute a bunch of native edgeql queries to confirm they work.
And at the same time we could road test some cascade delete tests - and confirm that things are really removed

Part of this might be to draw a bunch of object ownership heierarchies? In draw.io for keeping in the repo? I know I did an Lucidchart of the initial edgedb tables - but perhaps we can represent alternatively in draw io?

What is the idea of representing this? Something like a UML diagram?
Or something simple as below.

Yes something like a UML (I mean UML has the concepts of aggregation/composition etc - which is kind of like 'ownership').
I mean your diagram is simple enough and I would be happy with something like that (though it is wrong?) - I mean the relationship between DatasetCase and Dataset is not at all the same as the relationship between Release and Dataset (or were you just showing an example of the diagram and not the content?)

Yeah just a draft on the idea of how it would look like.

Excellent - yeah something simple like that.. no need for actual 'fields' in the boxes.. just high level Class names for the moment.. and proper aggregation and composition etc.


Add -enable-experimental-feature X for experimental features.

Introduce a simpler declarative approach to describing experimental features, where each feature has its own feature identifier (e.g., VariadicGenerics). The feature can be enabled with the -enable-experimental-feature FeatureName flag, and detected with #if $FeatureName. This metaprograms away the need to add new language options and compiler options each time we stage in a new experimental feature. Experimental features can only be enabled in non-production (+Asserts) builds.
Adopt this mechanism for a number of experimental features: variadic generics, static asserts, named opaque types, move-only, one-way closure parameters, and associated type witness inference via type witness systems.
Map the existing "experimental" flags over to the new system, but don't remove them just yet.

@swift-ci please smoke test

Looking forward to applying this to interop too! Thanks for the patch :)


Searching for news ordered by publish time descendingly takes forever when earliest-publish-date is not present

If I do this https://api.worldnewsapi.com/search-news?api-key=<key>&number=10&sort=publish-time&sort-direction=desc
it takes a very long time to load.
Especially compared to adding a earliest-publish-date filter like
https://api.worldnewsapi.com/search-news?api-key=<key>&number=10&sort=publish-time&sort-direction=desc&earliest-publish-date=2024-01-01%2000:00:00
which loads instantly.
Ideally the first query should load equally fast.
After all, it corresponds to a SQL query that has a clause like ORDER BY publish_time DESC LIMIT 10.
This would be very fast (if there's an index on the publish_time column, which there should be), and it would only load 10 records from the DB.
BUT: It seems the backend only includes the ORDER BY publish_time and not the LIMIT 10, then loads the whole set from the DB and applies the limit as a post-processing step, maybe in order to be able to calculate the available value from this set (?)
It would be faster to run two queries, one with limit and one count(*) to get available.
Then both URLs would load equally fast.
Apart from idealism, the reason why it would be better if the first query also loads fast is, to not have to make up a suitable value for earliest-publish-date, to allow users to paginate arbitrarily far back in time.

We have improved the sorting time for queries with a lot of results. Also it is required to send at least one filtering parameter, i.e. https://api.worldnewsapi.com/search-news?api-key=<key>&number=10&sort=publish-time&sort-direction=desc is no longer allowed, it must be filtered by text, language or anything else but not getting all news (of which there are millions) and sort them by time.


N Markers example is laggy with 2000 markers

It would be awesome if there was a way to display a large number of markers without affecting performance, maybe using webgl or canvas would help. As soon as the number of markers makes too many dom elements it becomes laggy.

Yep internally we had canvas drawer (on other map lib) it allowed to draw up to 4-5k markers. And used mix of React markers over to emulate hovers etc. Will add example when Ill have some free time.


parentSelector variable with 'undefined' failed to check

I found a problem when trying using propeller with jquery 3.2.1 & 3.3.1
maybe is not about jquery version, because i check with jquery 1.12.4 is working

The problem seems from propeller.js in commons.attachParentSelector function.
It seem failed while trying to evaluate parentSelector which has undefined value
My simple fix is, just added some new conditionals while evaluate parentSelector value
if (parentSelector &&       parentSelector !== '' && parentSelector.length > 0)
This 'parentSelector' conditional will guarantee that parentSelector for this value

null
undefined
NaN
empty string ("")
0
false

https://stackoverflow.com/questions/5515310/is-there-a-standard-function-to-check-for-null-undefined-or-blank-variables-in

@jewijaya Thank you for bringing it to our notice. We will check it and make the necessary changes.

Thx, thats works


Add support for Rune Knight buffs

Relevant data:

Skill Name
Skill ID
Effect Name
Effect ID
Validated in Ragna4th?

Placeholder
12345
PLACEHOLDER
54321
no

Relevant skills:

Enchant Blade

Source: https://irowiki.org/wiki/Rune_Knight


Image Preview not working

It's not possible to preview an image (in discord as long as I tested) but it detects the image width and height

It is because Discord preview cachers are presented with the "this site is hosted with localtunnel" page. The IP of the cacher changes every single time since, well, Discord has thousands of cachers.
The only way to remove this is to send some kind of user request header, I don't really know. Making an issue about this.