[Feature]Alter lake table add partition

What type of PR is this：

[ ] bug
[x] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Can't set status; build succeeded.

[FE PR Coverage Check]
:disappointed: fail : 28 / 79 (35.44%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
0
8
00.00%
[20, 21, 22, 26, 27, 30, 31, 35]

:large_blue_circle:
com/starrocks/persist/EditLog.java
0
7
00.00%
[225, 226, 227, 228, 229, 1101, 1102]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
0
4
00.00%
[52, 53, 54, 112]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
0
1
00.00%
[36]

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
1
8
12.50%
[249, 250, 251, 252, 253, 254, 255]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
26
46
56.52%
[1085, 1086, 1087, 1088, 1089, 1090, 1091, 1092, 1093, 1111, 1112, 1113, 1114, 1115, 1116, 1118, 1119, 1133, 1134, 1135]

Should clear tablet and shard when add partition failed.

Add more UT.

[FE PR Coverage Check]
:disappointed: fail : 53 / 87 (60.92%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
1
8
12.50%
[249, 250, 251, 252, 253, 254, 255]

:large_blue_circle:
com/starrocks/persist/EditLog.java
2
7
28.57%
[225, 226, 227, 228, 229]

:large_blue_circle:
com/starrocks/catalog/CatalogRecycleBin.java
2
5
40.00%
[933, 934, 935]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
5
8
62.50%
[30, 31, 35]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
3
4
75.00%
[112]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
38
49
77.55%
[1117, 1118, 1119, 1120, 1121, 1122, 1124, 1125, 1139, 1140, 1141]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
1
1
100.00%
[]

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 53 / 87 (60.92%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
1
8
12.50%
[249, 250, 251, 252, 253, 254, 255]

:large_blue_circle:
com/starrocks/persist/EditLog.java
2
7
28.57%
[225, 226, 227, 228, 229]

:large_blue_circle:
com/starrocks/catalog/CatalogRecycleBin.java
2
5
40.00%
[933, 934, 935]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
5
8
62.50%
[30, 31, 35]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
3
4
75.00%
[112]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
38
49
77.55%
[1117, 1118, 1119, 1120, 1121, 1122, 1124, 1125, 1139, 1140, 1141]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
1
1
100.00%
[]

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 53 / 87 (60.92%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
1
8
12.50%
[249, 250, 251, 252, 253, 254, 255]

:large_blue_circle:
com/starrocks/persist/EditLog.java
2
7
28.57%
[225, 226, 227, 228, 229]

:large_blue_circle:
com/starrocks/catalog/CatalogRecycleBin.java
2
5
40.00%
[933, 934, 935]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
5
8
62.50%
[30, 31, 35]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
3
4
75.00%
[112]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
38
49
77.55%
[1117, 1118, 1119, 1120, 1121, 1122, 1124, 1125, 1139, 1140, 1141]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
1
1
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 64 / 87 (73.56%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
1
8
12.50%
[249, 250, 251, 252, 253, 254, 255]

:large_blue_circle:
com/starrocks/persist/EditLog.java
2
7
28.57%
[225, 226, 227, 228, 229]

:large_blue_circle:
com/starrocks/catalog/CatalogRecycleBin.java
2
5
40.00%
[933, 934, 935]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
5
8
62.50%
[30, 31, 35]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
3
4
75.00%
[112]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
49
49
100.00%
[]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 72 / 87 (82.76%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/persist/EditLog.java
2
7
28.57%
[225, 226, 227, 228, 229]

:large_blue_circle:
com/starrocks/catalog/CatalogRecycleBin.java
2
5
40.00%
[933, 934, 935]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
5
8
62.50%
[30, 31, 35]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
8
8
100.00%
[]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
49
49
100.00%
[]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 71 / 85 (83.53%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/analysis/PartitionDesc.java
0
1
00.00%
[91]

:large_blue_circle:
com/starrocks/journal/JournalEntity.java
0
3
00.00%
[236, 237, 238]

:large_blue_circle:
com/starrocks/persist/EditLog.java
2
7
28.57%
[225, 226, 227, 228, 229]

:large_blue_circle:
com/starrocks/catalog/CatalogUtils.java
1
2
50.00%
[37]

:large_blue_circle:
com/starrocks/persist/AddPartitionsInfoV2.java
5
8
62.50%
[30, 31, 35]

:large_blue_circle:
com/starrocks/server/LocalMetastore.java
48
49
97.96%
[1209]

:large_blue_circle:
com/starrocks/catalog/RangePartitionInfo.java
8
8
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/SingleItemListPartitionDesc.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/persist/PartitionPersistInfoV2.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/persist/RangePartitionPersistInfo.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/analysis/MultiItemListPartitionDesc.java
1
1
100.00%
[]

run starrocks_admit_test

run starrocks_admit_test


Enable de-obfuscation for DataDog Logs

Is your feature request related to a problem? Please describe.
It would be really useful to see de-obfuscated logs after mapping.txt is uploaded, do you have plan to enable de-obfuscation also for DataDog logs.

Would it better de-obfuscated for DataDog RUM for any tracking view , I believe the class name it will become obfuscated if enable proguard.

Hi @miroslav404 , and thanks for opening this feature request. So far we only support deobfuscating stacktraces from Errors reported through RUM, and deobfuscating logs is not on our immediate roadmap but we'll keep you updated if we eventually do it.

We at Visma Dinero would also really like deobfuscation to work in the logs.
Its essential for crash reporting to be able to be able to see the stack trace. Our 'workaround' is to use Crashlytics....

Android stacktrace de-obfuscation is now supported for errors in Logs.
If your application doesn't have flavors, you can continue using the current Datadog SDK version in your application.
If your application has flavors, please make sure to upgrade Datadog SDK to the freshly release version 1.14.0-beta2 and correctly specify variant property of Credentials object during the SDK configuration (should be the same value as BuildConfig.FLAVOR by default).

It works - thanks, I'm very happy :-)


add lubbock to Contributors list

第一次，学习提交pull request，谢谢

I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added Facebook share and tweet feature to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Automatically enable Codacy for all branches

Is there a way to do this? Currently we only seem to analyze master and branches that are manually set. In other branches it seems to fail with "Codacy was unable to analyse your pull request."

It seems that this works now. For eg Codacy check completed for https://github.com/commons-app/apps-android-commons/pull/2488


Launch help using javafx browser

Modified the action taken for "help" command to launching the default web browser of the pc and navigating to the webpage of the user guide.
This PR shares the checkstyle issue with #76 .

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/main/java/seedu/address/ui/UiManager.java
0.00%
3 Missing :warning:

src/main/java/seedu/address/ui/MainWindow.java
0.00%
2 Missing :warning:

src/main/java/seedu/address/MainApp.java
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ
Complexity Δ

src/main/java/seedu/address/MainApp.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

src/main/java/seedu/address/ui/UiManager.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

... and 25 files with indirect coverage changes


Powertech - Shield Tech CanNotBeDetermined

Shield Tech discipline is still coming up as CanNotBeDetermined

Guessing this is kinda the mirror to the vanguard shield specialist so it's the same "bug"? cause it's been a long time since the vanguard was reported....

Yes, this turned out to be something we can't easily fix other than how we're doing it in the rotation factory: https://github.com/BosslandGmbH/BuddyWing.DefaultCombat/blob/master/src/DefaultCombat/Core/RotationFactory.cs#L21
If you could give me the class/advanced class combinations for those two, we could possibly solve it that way.

Main 	-> Advanced    -> Spec
Trooper -> Commando    -> AssaultSpecialist
-> CombatMedic
-> Gunnery
Trooper -> Vanguard	-> Plasmatech
-> ShieldSpecialist
-> Tactics
BountyHunter -> Mercenary	        -> Arsenal
-> Bodyguard
-> InnovativeOrdnance
BountyHunter -> PowerTech	        -> AdvancedPrototype
-> Pyrotech
-> ShieldTech
I guess that is what you want?

@Markeeen Yes, thanks. That's one part we use for "correcting" some of the values obtained by the bot's internals. For Shield Tech and Shield Specialist, we're currently using the following spell nodes to identify them:
{16141009404323093105, CharacterDiscipline.ShieldTech}, // Jet Charge
{16141074151321389691, CharacterDiscipline.ShieldSpecialist}, // Storm

If those are proven wrong (which they obviously are, since you're getting CanNotBeDetermined), we can work around that with the class/advanced class/unique spell for discipline combination like we do for some other classes:
        if (HasAbility("Flaming Fist") && advancedClass == AdvancedClass.Powertech)
        {
            discipline = CharacterDiscipline.Pyrotech;
            return true;
        }

This could work for all classes which are currently not determined properly.

Shield Tech (Bounty Hunter) does have the spell FireStorm but i guess that won't cause problems i guess?
Maybe use the level 10 spells that each specialization gets? They are unique to each spec and will be present as soon as you choose the discipline.
Shield Tech (Bounty Hunter -> Power Tech) = Oil Slick
Shield Specialist (Trooper -> Vanguard) = Riot Gas

@Markeeen Thanks, that should do! I've added the following to the BW core:
if (HasAbility("Oil Slick") && advancedClass == AdvancedClass.Powertech)
{
	discipline = CharacterDiscipline.ShieldTech;
	return true;
}

if (HasAbility("Riot Gas") && advancedClass == AdvancedClass.Vanguard)
{
	discipline = CharacterDiscipline.ShieldSpecialist;
	return true;
}

And I'll get a new build of the bot out shortly with the combat routine improvements. I'll leave the issue open until we can confirm it's fixed.

@Mazriel Can you confirm this is either still an issue or has been resolved in version 1.0.1256.821? Thanks!

It's not the "cannotbedetermined" spec anymore :D, looks like it 's working
2016-01-11 09:41:56,731 [7] INFO  Log - User is a BountyHunter
2016-01-11 09:41:58,349 [7] INFO  Log - Advanced Class: Powertech / Discipline: ShieldTech
2016-01-11 09:41:58,349 [7] INFO  Log - Routine Path: Routines
2016-01-11 09:41:59,831 [7] INFO  Log - Medpac  Created!
2016-01-11 09:41:59,863 [7] INFO  Log - [DefaultCombat] Level: 65
2016-01-11 09:41:59,864 [7] INFO  Log - [DefaultCombat] Class: BountyHunter
2016-01-11 09:41:59,864 [7] INFO  Log - [DefaultCombat] Advanced Class: Powertech
2016-01-11 09:41:59,899 [7] INFO  Log - [DefaultCombat] Discipline: ShieldTech
2016-01-11 09:41:59,935 [7] INFO  Log - [DefaultCombat] [Hot Key][F7] Toggle AOE
2016-01-11 09:41:59,935 [7] INFO  Log - [DefaultCombat] [Hot Key][F8] Load UI
2016-01-11 09:41:59,936 [7] INFO  Log - [DefaultCombat] [Hot Key][F12] Set Tank
2016-01-11 09:41:59,936 [7] INFO  Log - [DefaultCombat] Rotation Selected : PowerTech Shieldtech

Great, I'll close the issue then! :+1:


Add OpenSearch API

Bring Explorer at par with Resto by adding an Open-Search API
{"stac_version":"1.0.0-beta2","id":"catalogs","title":"Footprints","description":false,"capabilities":["resto-core","tag","gazetteer","hashtag","shapefileuploader","stacplus"],"planet":"earth","links":[{"rel":"self","type":"application/json","title":"Footprints","href":"https://resto.dev.dea.ga.gov.au"},{"rel":"service-desc","type":"application/json","title":"OpenAPI 3.0 definition endpoint","href":"https://resto.dev.dea.ga.gov.au/api"},{"rel":"service-doc","type":"text/html","title":"OpenAPI 3.0 definition endpoint documentation","href":"https://resto.dev.dea.ga.gov.au/api.html"},{"rel":"conformance","type":"application/json","title":"Conformance declaration","href":"https://resto.dev.dea.ga.gov.au/conformance"},{"rel":"data","type":"application/json","title":"Collections","href":"https://resto.dev.dea.ga.gov.au/collections"},{"rel":"root","type":"application/json","title":"Footprints","href":"https://resto.dev.dea.ga.gov.au"},{"rel":"search","type":"application/json","title":"STAC search endpoint","href":"https://resto.dev.dea.ga.gov.au/search"},{"rel":"child","title":"Classifications","type":"application/json","href":"https://resto.dev.dea.ga.gov.au/catalogs/classifications/catalog.json"},{"rel":"child","title":"Hashtags","type":"application/json","href":"https://resto.dev.dea.ga.gov.au/catalogs/hashtags/catalog.json"},{"rel":"child","title":"Themes","type":"application/json","href":"https://resto.dev.dea.ga.gov.au/catalogs/themes/catalog.json"}]}

What does making it an open-search API mean?
Is it this? https://www.opensearchserver.com/documentation/api_v2/README.md
In my view, bringing the STAC API up to speed even more, so we can index off it, for example, is a better effort.
The STAC API is a OGC API for Features implementation, so it's an open standard.

Resto provides both STAC and OpenSearch API's which are required for the Rocket client for STAC to function. This functionality will allow Explorer to act as a Rocket backend.

Oh, it uses both APIs does it? Dang.


HiFiGAN recipe using LibriTTS

Summary
This PR adds detailed implementation of HiFi-GAN recipe using LibriTTS.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.64%. Comparing base (c38df15) to head (cd3a005).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #177      +/-   ##
==========================================
+ Coverage   81.61%   81.64%   +0.03%
==========================================
  Files         169      171       +2
  Lines       15344    15371      +27
==========================================
+ Hits        12523    12550      +27
  Misses       2821     2821

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


fix: Searchbar Nft Search not working

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #7255

wrong query

this is used to get the collection nft floor price

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI;

Copilot Summary

🤖 Generated by Copilot at 016f329
Refactored the gallery view to remove the shopping cart feature and unused code. Removed the floor field from the nftListWithSearch query and the shopping cart related code from ItemsGrid.vue.

🤖 Generated by Copilot at 016f329

No more floor, no more cart, we don't need them anymore
We strip away the excess, we refine our core
We rebel against the bloat, we resist the feature creep
We simplify the gallery, we make it sleek and deep

lul first one

@hassnian thank you for both the issue and the PR

ref feat: mass listing #7076

Thank you for identifying the source 🕵

pay 30 usd

😍 Perfect, I’ve sent the payout
💵 $30 @ 4.02 USD/DOT ~ 7.463 $DOT
🧗 13QUj3pZyFNfYj4AM336hRdyLQbevj5H3sR4PKmLEXLdwZhh
🔗 0x0a1773c4695436d05f0478871fcdb1895a8b0a42989287da6a5c765557d84938
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


error: panic: invalid height: 2; expected: 3

I thought last night that this error was specific to lazy aggregation, but it is happening with lazy aggregation off too. it produces 2 blocks, then errors: panic: invalid height: 2; expected: 3
repro details: https://github.com/rollkit/rollkit/issues/802#issuecomment-1486430360
https://app.warp.dev/block/UfQ2rKEZRsgOd4XAwNisbQ full logs

Weird, not happening now. Will reopen if it happens again

Replicated with v0.8.0-rc2 of celestia-node in https://github.com/jcstein/local-celestia-devnet
Video of crash: https://www.loom.com/share/4ac5744feb1f437397c8ed9eff69f14c

Run on Blockspace Race using a light node
i’m not sure what’s up with this. it doesn’t work on upgraded container for local-celestia-devnet, but works on the BSR network (logs). i’m positive i’ve cleared chain history and re-initing the chain when on local network

Odd, still occuring on v0.8.0 of node on local-celestia-devnet: https://app.warp.dev/block/NaTXL9AoKvKeDolNfPCkZI
Logs of local devnet: https://app.warp.dev/block/LlA6ILiSv41zgbqauezZ7D

However, it works when posting to Blockspace Race testnet on v0.8.0
Rollup logs: https://app.warp.dev/block/wnwC6o71JbNWqKFbW9iMdK


fix(glide.yaml): ignore k8s.io/kubernetes

Currently, the Go kubernetes client library transitively depends on a k8s.io/kubernetes package. This ignores that dependency. This patch can be removed if https://github.com/kubernetes/client-go/issues/33 is resolved by removing the transitive dependency.
cc/ @krancour

Current coverage is 38.06% (diff: 100%)

Merging #13 into master will increase coverage by 1.93%

@@             master        #13   diff @@
==========================================
  Files            31         31
  Lines           880        880
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            318        335    +17
+ Misses          536        520    -16
+ Partials         26         25     -1

Powered by Codecov. Last update 514df17...4f9c718

@arschles that dependency is critical... steward-framework and steward-cf won't compile without it. 😦

@krancour guess we'll need to wait and see if https://github.com/kubernetes/client-go/issues/31 fixes. Closing and replacing with #41


⚠ Samsung has degraded performance

In 76c460f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2349 ms

Resolved: Samsung performance has improved in 9ed4910.


usage of reqwest rustls-tls-webpki-roots

Is your feature request related to a problem? Please describe.
I'm looking at packaging this for Debian, and noticed the usage of reqwest/rustls-tls-webpki-roots, this collides with our packaging policies as it duplicates the ca-certs into the binary, so that the binary have to be rebuilt if there is an update to the ca-certs.
Describe the solution you'd like
Use reqwest/rustls-tls-native-roots instead.
Describe alternatives you've considered
I can just patch the crate to use reqwest/rustls-tls-native-roots myself, but I thought that I should also bring this up here, in order to keep the diff between
Additional context
Technically this should maybe be a security issue, since it will be a security problem if a ca-cert gets compromised and the binary isn't rebuilt. But since it's so theoretical and other debate about the usage of webpki-roots is public I don't think there is a need to keep this secret.
Also see this comment for an analysis of the situation: https://github.com/rust-lang/rustup/issues/3400#issuecomment-1683762630

Disable default features and enable native-certs


HA 2023.3 might make the integration unusable

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 14:20:49 (1 occurrences)
Last logged: 14:20:49
Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for ecoflow using this method at custom_components/ecoflow/init.py, line 429: hass.config_entries.async_setup_platforms(entry, _PLATFORMS)

Do you have a beta version?
This is the Current Version and Everything works

…will check when home

2023.2.3
HA works perfect with DP from the bedinning in August last year. Since than I didn‘t update my DP any more. Still using FW <IP_ADDRESS>

2023.3.0 - everything works perfectly with Delta Pro.
The warning above is still just a warning in 2023.3. and the fix is quite easy though.

Hey there, does it still work under HA 2023.4.5 ?
Thanks!

I'm using 2023.4.0 - works without any issues


test-branch/execute-job/quoted-authorization/5f2aadac-7061-4d68-b35a-fdf4dfa2e167

PR for testing fb2d4747ce5877b911c0e49068ece36d4bc7db81

/canonical/self-hosted-runners/run-workflows fb2d4747ce5877b911c0e49068ece36d4bc7db81


Fix display of locked vs. unlocked STX balances

They appear to have regressed, perhaps due to UI library work:

This was broken before style updates but I will fix it 👍

Closing as dupe of https://github.com/leather-wallet/extension/issues/4851


dyld: Symbol not found: ___chkstk_darwin

How frequently does the bug occur?
All the time
Description
App crash when I run on iOS 12. version.
dyld: Symbol not found: ___chkstk_darwin   Referenced from: /private/var/containers/Bundle/Application/3EEB008F-D7CB-4AF3-A0AC-E6DCAC71C9C0/ProjectOn_iOS13.app/Frameworks/libswift_Concurrency.dylib (which was built for iOS 13.0)   Expected in: /usr/lib/libSystem.B.dylib  in /private/var/containers/Bundle/Application/3EEB008F-D7CB-4AF3-A0AC-E6DCAC71C9C0/ProjectOn_iOS13.app/Frameworks/libswift_Concurrency.dylib
Stacktrace & log output
`dyld: Symbol not found: ___chkstk_darwin
  Referenced from: /private/var/containers/Bundle/Application/3EEB008F-D7CB-4AF3-A0AC-E6DCAC71C9C0/ProjectOn_iOS13.app/Frameworks/libswift_Concurrency.dylib (which was built for iOS 13.0)
  Expected in: /usr/lib/libSystem.B.dylib
 in /private/var/containers/Bundle/Application/3EEB008F-D7CB-4AF3-A0AC-E6DCAC71C9C0/ProjectOn_iOS13.app/Frameworks/libswift_Concurrency.dylib
`

Can you reproduce the bug?
Yes, always
Reproduction Steps

Download Carthage.xcframework.zip v10.20.2 from https://github.com/realm/realm-swift/releases
Drag to Frameworks, Libraries, and Embedded Content
Cmd + Run on device iPhone 5s (12.5.3)

Version
v10.20.2
What SDK flavour are you using?
Local Database only
Are you using encryption?
No, not using encryption
Platform OS and version(s)
12.5.3
Build environment
Xcode version: Version 13.2.1 (13C100)
swift-driver version: 1.26.21 Apple Swift version 5.5.2 (swiftlang-13<IP_ADDRESS> clang-13<IP_ADDRESS>)
Target: x86_64-apple-macosx12.0

Your issue looks related to https://github.com/realm/realm-swift/issues/7562

We're currently having to build our app with Xcode 13.1 if we want to maintain support for iOS 12 in conjunction with recent versions of Realm (v10.20.2 at the time of writing). Others are suggesting using Realm v10.14 or earlier. Both solutions are less than ideal.
Either:

Realm needs to be updated to work with the latest versions of Xcode and iOS 12, or
The minimum deployment target raised to 13+ so that the crash does not occur in the wild when devs have not tested on iOS 12.

It is a Xcode bug, need to be fixed by Apple

Closed due to this being an Xcode issue. Please use the latest XCode release.


TabLine, TabLineSel, and TabLineFill are not set

When creating tabs in neovim (:tabnew) the resulting tab bar does not match the color scheme. I was able to fix this by setting the relevant highlight groups as follows:
-- ~/.config/nvim/after/plugin/color.lua
vim.cmd.colorscheme('night-owl')

local c = require('night-owl.palette')
local hl = vim.api.nvim_set_hl

hl(0, "TabLine", { fg = c.fg, bg = c.dark2 })
hl(0, "TabLineSel", { fg = 'none', bg = c.blue3 })
hl(0, "TabLineFill", { fg = 'none', bg = c.bg })

I'm not sure if these are the exact colors used in the VSCode tabs, but they seem close enough.

Thanks so much for reporting this! I was able to match VSCode colors and now it looks like this:

@all-contributors please add @nanyaDev for bug


How to store bigger geographic datasets

What should we do with the bigger geographic packages, where should we store them?
My country-levels full planet extracts have a 72 MB, 92 MB and a 169 MB version, uncompressed. Compressed, these are 11, 17 and 35 MBs respecitvely.
As more and more county level data arrives, I'm sure it'll be dozens of similarly sized packages at the end.
What should we do about them?
The easiest and most reliable way to handle these would be yarn add github_url. That checks out the whole repo into node_modules. In my case the 3 versions together.
The other way would be to download a release zip file from GitHub and extract it into a folder in runtime. For example I was working on downloading the medium version of country-levels and extracting it to /vendor/country-levels. It'd be gitignored then.
What path should we go? I think this very much depends on the lambda limitations, what do you say @ryanblock.
I think writing a function which checks and downloads a given url into a folder is quite easy. My idea was to store the version or url inside the folder, then we can check it trivially. For example:
if (readJSON('vendor/country-levels/__cache__.json') === url) return

or something similar.
Downloading and unzipping is also quite trivial. The point of this one would be that nothing would be included in the package, it'd be downloaded at runtime.
But again, I don't know the lambda specific parts of it, if we'd download everything on each function call for all scrapers might not be the best.
What are the limitations, how much can we include via package.json?

https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html
Bunch of limits for lambdas. The one I normally hit is the 50mb limit for the bundle of code to run on the lambda.

So I guess we are almost hitting that with the vendor folder already (28 MB)? I guess the direction then is to download zip files.
And is it possible to make them cache so that not every single run needs to download from GitHub?

Couple things:

50MB compressed, 250MB uncompressed
We get a decent amount of disk if we need to temporarily persist anything (512MB)
We will have 3GB of RAM if we want to read anything out of S3 into memory and operate on it there, which I'd strongly suggest

How soon do we need this functionality?

Right now I'd need to store those GeoJSON files somewhere. I definitely not want to store them in Git, as they are big and numerous. Including in package.json is also not a good idea, as it'd load the whole dataset.
Basically that zipToFolder seems to be the best idea for me, at least it takes the smallest amount of space and doesn't pollute Git or package.json / node_modules.

We get a decent amount of disk if we need to temporarily persist anything (512MB)

That sounds like the perfect solution in my opinion. Can we just unzip to src/shared/vendor now and change it to that temp folder later on?

Solved with yarn + tar.gz


Document ({ /* arbitrary Rust code */ })

I wasn't able to find anything in the Maud documentation about the fact that splices can contain arbitrary Rust code, including compound expressions. I did stumble on #11, which contains a comment referencing ${ ... } before I created a bug about type inference, but it would be useful if the documentation had an example of this kind of thing. For instance:
p ({
  let user:User = try![database.lookup(userid)];
  user.name
})

This is also an example of the kind of thing that can fail when using Maud @let directives: they don't accept type annotations, so I sometimes get "the type of this value must be known in this context" errors.

You can use
@let ...;
@if let...;

This style I supported but refused.
@ {
   // Arbitrary code here.
}

The documentation can be found at https://github.com/lfairy/maud-book. I'm too swamped with work at the moment to edit it myself, but if you have the time then I'd welcome a pull request.
I think @let not supporting type annotations is a bug. I've filed that as #73.

Thanks! I've created lfairy/maud-book#1.

I believe @trombonehero's PR closes this issue.


Upgraded jsonschema version

Proposed changes:

Updated jsonschema version
This PR will close #4512

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

Thanks for the PR, we'll give it a review as soon as possible.


ignore empty configuration files in legacy check

motivation: make legacy file warning less noisy if the file is empty
changes: check to see if the configuration file in the legacy location is empty before migrating it and emitting the warning

@swift-ci smoke test


[KYUUBI #5575][KYUUBI #5611][AUTHZ] Check path privilege should use correct action type

_Why are the changes needed?
To close #5575 #5611
Check path privilege should use correct action type
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Was this patch authored or co-authored using generative AI tooling?
No

ping @yaooqinn

Codecov Report

Merging #5618 (07049a5) into master (51dd31c) will decrease coverage by 0.08%.
Report is 2 commits behind head on master.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #5618      +/-   ##
============================================
- Coverage     61.47%   61.39%   -0.08%
  Complexity       23       23
============================================
  Files           603      603
  Lines         35619    35621       +2
  Branches       4869     4869
============================================
- Hits          21896    21870      -26
- Misses        11347    11373      +26
- Partials       2376     2378       +2

Files
Coverage Δ

...he/kyuubi/plugin/spark/authz/PrivilegeObject.scala
95.74% <100.00%> (ø)

.../kyuubi/plugin/spark/authz/PrivilegesBuilder.scala
92.12% <100.00%> (+0.06%)
:arrow_up:

...e/kyuubi/plugin/spark/authz/serde/Descriptor.scala
76.72% <100.00%> (+0.20%)
:arrow_up:

... and 16 files with indirect coverage changes
:mega: Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

Thanks, merged to master


Routing.

I'm not family with the structure and design of this generator as it's very different from regular Angular 1 projects. I'm wondering how routing is handled here. I've haven't found any documentation for that around and the Angular 2 styleguide wasn't much help.

As we use the component concepts, you should use Angular 1 component router which is based on Angular 2 router. Here is the documentation https://docs.angularjs.org/guide/component-router

You can also use angular UI router with the following syntax:
.state('state.component', {
  url: "/route",
  template: '<mycomponent></mycomponent>'
})

thanks 👍


Incorrect schema

In the README.md file there's a following piece of schema for node:
 |-- tags: array
 |    |-- element: struct
 |    |    |-- key: string
 |    |    |-- value: string

whereas, after converting pbf to parquet, loading it to spark and printing schema it is:
 |-- tags: array (nullable = true)
 |    |-- element: struct (containsNull = true)
 |    |    |-- key: binary (nullable = true)
 |    |    |-- value: binary (nullable = true)

The difference is between the type of key and value fields - string vs binary. Is this an inconsistency or am I somehow mistaken?
Also, if these fields have binary type can I issue a PR where it will be changed to string? I how no idea when these fields can be useful in the binary format.

Oh, I se that a similar issue has already been raised here. Sorry for bothering and thanks for your awesome work.


fix(runtime-core): use stack to store instance

If a component is in setup and another component is rendered, the onMounted method of this component cannot be executed, because the currentInstance is lost. Also, the correct instance cannot be obtained after rendering.
I use the stack to save the historical instance, and take out the previous instance after the instance is used up, and solve this problem

Related to #7021

There is a same PR in vue2 https://github.com/vuejs/vue/pull/12866

Thanks for the PR! Pushing and popping into an array every time a component mounts is likely to have a negative impact on performance.
Let's wait until we can confirm #7021 is indeed a bug

Push and pop is very fast in javascript's array, also I think this is indeed a bug, and the developers may get stuck because of this.

There are not many cases of using the stack, it is only used when the current stack needs to be suspended, not every time of mounting

Unfortunately, the push is called every time setCurrentInstance() is called, so it might be even more...
Keep in mind this is not about push being fast, it's about adding an extra call that could be avoided (the push) to a code that happens very often and therefore is perf sensitive

Actually, push is only called when currentInstance has a value, that means only in the case of the example and a small number of cases will occur. I know that is perf sensitive, but I feel like it should be fixed if it's a bug, so I hope to reconsider

Thanks for the PR! Pushing and popping into an array every time a component mounts is likely to have a negative impact on performance.
Let's wait until we can confirm #7021 is indeed a bug

@posva hello, is there any progress?

I think this problem may have been fixed in 3.4.7 by this commit:

https://github.com/vuejs/core/commit/7976f7044e66b3b7adac4c72a392935704658b10

I'm not able to access the original reproduction for #7021 to confirm. I made a Playground to try to replicate the issue based on the description, and it starts working from 3.4.7 onwards:

Playground

Thanks again @skirtles-code 🙌 . I can't access the old repro either. It seems to allow mounting over and over too


A typo in evaluate_famous_models.py

Line 13 : print("%s | %s | %s" % ("Model", "Params(M)", "FLOPs(G)"))
I doubt that "FLOPs(G)" here should be "MACs(G)".

Thanks for the reminder. Could you scratch a PR to help fix? I am travelling and might be unable to code,

Roger that.
I will do it.


Any frontend UI without needing to login?

What happened?
I can't open a question, so writing here instead
How to reproduce the bug
N/A
Package Version
0.2.0-alpha.5
PHP Version
8.2
Laravel Version
10
Which operating systems does with happen with?
No response
Notes
No response

This is is specific to filament authenticated users

I can contribute to make this possible. I need to output a floating chat widget, with a preselected user/agent, so I think I can help build that logic.
In my scenario, this widget will be loaded in a mobile app as well as on a website, and the selected user will receive all the conversations that show up.

wonderful that's exactly what I was asking for!


Remove debug logging from reproducible build test

Summary

Nitpick fix to https://github.com/paketo-buildpacks/php-httpd/pull/12 but I merged it in and noticed we should remove the debug logging from the test for clarity's sake.
Use Cases

Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

nvm! debug logging is helpful in the case where the test fails


Orthographic projection in 3D and Columbus view

Sandcastle examples for testing: http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Apps/Sandcastle/index.html

This isn't ready for a code review. I want to have more people try this and report any problems when moving the camera around or if they have any suggestions for improvement.
There is a new widget to switch between orthographic and perspective projection. It is on by default, but will be disabled when this is ready to be merged.

[x] Limit terrain/ imagery requests on the horizon.
[x] Fix morphs
[x] Add new tests
[ ] Update CHANGES.md
[ ] Fix ground primitives
[ ] Default new widget to hide

After merge:

[ ] Merge to 3d-tiles
[ ] Update 3d-tiles screen space error in for orthographic projections

Fixes #2069.

CC @pmconne

I dig the new widget.

When switching models, should the icons rotate?  The scene mode widget does this to sync with the morph, but, for example, the imagery picker does not.
Should this widget be shown by default?  I would think no since it won't be widely used and uses screen real estate.
Can we gray this out in 2D and also throw a reasonable exception when someone programmatically switches projection in 2D.  Right now it is:

Part of #4678

Do you get these artifacts in the 3D models Sandcastle example?

Run the 3D models Sandcastle example
Switch to ortho
Hit the Home button, and get this exception:

Is this the correct behavior when zooming in ortho when just in front of the balloon model?

Run the G&A Sandcastle example and switch to ortho.  A lot of the primitives turn black:

Run the Ground Clamping Sandcastle example
Select Draw Polygon
Zoom in near the edge

There are artifacts likely due to near plane clipping in the shader.

Will this also be an issue anywhere else, e.g., polylines?

Run the Star Burst Sandcastle example
Switch to ortho
Click on the facility to expand the star burst
Move the mouse

The following exceptions appear in the console:
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)
Uncaught DeveloperError: Expected right to be typeof object, actual typeof was undefined
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/DeveloperError.js:44:19)
    at Object.Check.typeOf.object (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Check.js:151:19)
    at Function.Cartesian2.subtract (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js:484:22)
    at updateStarBurst (<anonymous>:220:40)
    at <anonymous>:36:5
    at handleMouseMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:255:13)
    at handlePointerMove (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:651:13)
    at HTMLCanvasElement.listener (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/ScreenSpaceEventHandler.js:70:13) (on line 166 of http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Source/Core/Cartesian2.js)

@bagnell this is a good start, but I think it is worth going through each Sandcastle example and switching to ortho for testing.

Do you get these artifacts in the 3D models Sandcastle example?

Yes, that's the terrain being clipped by the near plane. I'm not sure how to fix that beside limiting the camera tilt more and more the farther the camera gets away from the target. I think it would be best to not do that and even disable collision with the terrain. Users who will use the orthographic projection will want to see models from the bottom.
Any suggestions?

Is this the correct behavior when zooming in ortho when just in front of the balloon model?

I haven't been able to reproduce that.  Do you have steps to reproduce? I was:

Loading the 3D model example
Selecting the hot air balloon
Switch to orthographic
Zooming in and out then a mix of zooming and rotating

I enabled fog to see what it looks like and its not as bad as I thought it would be. Let me know what you think. For the camera view below:
fog | disabled | enabled
Perspective | 161 | 94
Orthographic | 498 | 207
These are the orthographic views with and without fog:

If I enable culling based on fog, the tiles in fog in the above view are culled. The number of tiles rendered in that view would be 43. If I tilt the camera so more terrain is visible, the number of tiles rendered is 199. I committed the change that adds fog and culling based on fog.

Looks like enabling fog and fog culling by default in orthographic is the way to go.
Let me know when this PR is ready for another review.

@pjcozzi This is ready for another look including code review. Though I'm still looking into the ground primitive artifact.

As I mentioned above, https://github.com/AnalyticalGraphicsInc/cesium/pull/5021#issuecomment-281541059, should the widget be shown by default?

The widget won't be shown by default. I have it that way for testing until ground primitives are fixed.

What was the verdict with the cracking artifacts when looking straight down in ortho 3D?

What was the verdict for horizon views?  I thought we were adjusting the camera?  Or did we decide to leave this artifact:

Given artifacts like below (which we can't reasonably get around, right?), can we mention in the reference doc that the target use case for ortho is CAD 3D tilesets and glTF models.  Terrain and imagery are supported but may have artifacts in the foreground and background.

Off the coast north of San Fran:

Run http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Apps/Sandcastle/index.html?src=3D Models Coloring.html&label=Showcases
Turn the model's alpha all the way to zero, note that the silhouette shows up, but it does not show up in ortho.

Run any Sandcastle example
Switch to ortho
Switch to 2D (not that the ortho icon stays but is grayed out)
Switch back to 3D
It automatically switches to perspective view.  Should it?  If not, perhaps the morph just happens in perspective, then jumps to ortho?

Run http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Apps/Sandcastle/index.html?src=Camera Tutorial.html&label=Showcases
Switch to ortho, hold w for a bit to zoom in.  The position change isn't really noticeable.
Switch back to perspective.  The user is much closer to the globe.

The behavior seems reason when the opposite happens: the users zooms in with perspective than switches to ortho.

Run http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Apps/Sandcastle/index.html?src=Camera.html&label=Showcases
Select "Fly in a City"
While the flight is in progress, switch to ortho
The view goes black

Run http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Apps/Sandcastle/index.html?src=Camera.html&label=Showcases
Switch to ortho
Select Camera changed event
Rotate the globe, and get a NaN:

Run http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/ortho-3d/Apps/Sandcastle/index.html?src=Cardboard.html&label=Showcases
Switch to ortho
The view goes black

In general, will VR support ortho?

Fix ground primitives

Please submit a separate issue for this and document this limitation/artifact in the reference doc.
If/when this turns out to be an issue for 3D Tiles classification, we can investigate again.

No significant code comments.  @lilleyse did you want to look at this?
Does anyone else want to review the new widget?

Turn the model's alpha all the way to zero, note that the silhouette shows up, but it does not show up in ortho.

Silhouettes are also very thin in 2d/CV, mostly likely there's a common cause.

No significant code comments. @lilleyse did you want to look at this?

Sure I'll take a look.

What was the verdict with the cracking artifacts when looking straight down in ortho 3D?

This was only happening for compressed terrain vertices. The vertices were slightly off from the error introduced from the translation/scale and noticeable only with an orthographic projection. Since the skirts were being dropped straight down, I extended them slightly outward from the mesh.

What was the verdict for horizon views? I thought we were adjusting the camera?

Given artifacts like below (which we can't reasonably get around, right?), can we mention in the reference doc that the target use case for ortho is CAD 3D tilesets and glTF models.

There was no reasonable way to get around either of these. We can't limit the camera angle because that would limit how a user could view a CAD model. I suspect users will not even want to enable terrain collision so they can view the model from below. We can't turn the fog off because we would request way too many tiles.

Turn the model's alpha all the way to zero, note that the silhouette shows up, but it does not show up in ortho.

Silhouettes are also very thin in 2d/CV, mostly likely there's a common cause.

Silhouettes are missing for me in 2D as well. I think it's a separate issue.

What was the verdict with the cracking artifacts when looking straight down in ortho 3D?

This was only happening for compressed terrain vertices. The vertices were slightly off from the error introduced from the translation/scale and noticeable only with an orthographic projection. Since the skirts were being dropped straight down, I extended them slightly outward from the mesh.

Do these completely go away for you?  I still see them.

Silhouettes are missing for me in 2D as well. I think it's a separate issue.

Submitted https://github.com/AnalyticalGraphicsInc/cesium/issues/5082

In general, will VR support ortho?

No, I don't think VR makes sense without a perspective projection.

In general, will VR support ortho?

No, I don't think VR makes sense without a perspective projection.

Can you gray out the VR widget in ortho?  And gray out the ortho widget in VR?  And also throw an exception (in scene.render or friends) if both are enabled at once?  Instead of the exception, ortho could also just be ignored, but I don't know that is ideal behavior...whatever you think.

It automatically switches to perspective view. Should it? If not, perhaps the morph just happens in perspective, then jumps to ortho?

I wasn't sure about this. Switching from 3D/CV to 2D automatically switched to ortho and switched back to perspective by default. We could keep track of what projection was last used in 3D/CV and use that for the morph. What if the scene starts out in 2D?

What was the verdict with the cracking artifacts when looking straight down in ortho 3D?

This was only happening for compressed terrain vertices. The vertices were slightly off from the error introduced from the translation/scale and noticeable only with an orthographic projection. Since the skirts were being dropped straight down, I extended them slightly outward from the mesh.

Do these completely go away for you?  I still see them.

They did when zooming in with the mouse, but, if I use the geocoder, I see them.

It automatically switches to perspective view. Should it? If not, perhaps the morph just happens in perspective, then jumps to ortho?

I wasn't sure about this. Switching from 3D/CV to 2D automatically switched to ortho and switched back to perspective by default. We could keep track of what projection was last used in 3D/CV and use that for the morph.

Sounds good.

What if the scene starts out in 2D?

Default to perspective.

DebugCameraPrimitive (enabled with Show Frustum Planes in Cesium Inspector) is broken when toggled while in orthographic, it looks like this is because it is trying to invert the frustum's projection matrix.

I'm getting some weird results when moving the camera around.
There are same horizon views where the camera gets completely stuck. There are also some views where the fog has extreme colors, or the empty foreground becomes red. The crashing is pretty consistent when moving to a horizon-type view from far enough away. In general I am noticing more problems when zoomed far enough out, while views close to the surface are pretty good.

Switching from ortho to 2D or CV has issues, it appears blank until I move the camera.

@pjcozzi @lilleyse This is ready for another review.
@pjcozzi This is the change I mentioned offline: https://github.com/AnalyticalGraphicsInc/cesium/pull/5021/commits/e13bc3d9628a768700f84216f14ca30df9599da3#diff-6298b280e4e0977bedd881b65b769863R993 If the camera is above a certain height then we zoom when rotating to avoid artifacts.

Adjusting the terrain skirts also fixes #3710.

@lilleyse can you please do a final review and testing (and close and notify all the users in #3710)?
I would like to have this in master for a bit before we ship 1.32.

There are still some situations where the camera can get stuck (it's possible I'm below the max height that is set). Like in this demo: http://localhost:8080/Apps/Sandcastle/index.html?src=CZML Colors.html&label=CZML usually I just rotate backwards completely, and then try to rotate forwards, but it end up getting stuck, though zooming still works.
Otherwise, the new code changes and fixes look good.

Default new widget to hide

Will this one be updated right before merging?

@lilleyse This is ready for another look. When you get stuck, you can click space to rotate the view to look back at the ground just like if you get stuck looking up at terrain.

Default new widget to hide

Will this one be updated right before merging?

Yes, I updated it. To test, create a viewer with:
var viewer = new Cesium.Viewer('cesiumContainer', { projectionPicker : true });

Alright this is ready to go then.

Adjusting the terrain skirts also fixes #3710.

For some reason I'm not noticing any of the cracking issues linked in that issue in earlier versions of cesium, I'll check on my laptop tomorrow.

I could only reproduce using the second link @hpinkos posted and going to 110 45 with the geocoder.


View comments fails to load (last 24 hrs)

Hi,
I have been using the app for a while and it's great but in the last 24 hours the main list loads but whenever I want to view comments it says "Failed to load" with the retry button.
When I visit news.ycombinator.com in a browser on the same device viewing comments work fine.
Using v1.11.1 and I don't see any updates in the play store.
Any ideas?

Same here.

Device restart fixed it for me, no idea why.

This is due to the Algolia API being down, it usually goes back up after a little while but I am in the process of adding better messaging for this.


Buttons are swapped

see recording, "open files..." does "learn more" and vice versa
https://user-images.githubusercontent.com/1794099/165493459-110d2305-a440-4d84-8132-b738eea961b9.mov

Yeah thanks I fixed this today!


Track method missing events in source debugger

Hello,
Following the documentation I'm using @segment/analytics-node: 1.1.0 on my node server, the problem I face is if my track method gets called 15 times in segment dashboard / sourced / debugger, sometimes are 10 events other times 15 or fewer depending, I can't find a pattern or a way to fix this issue. I'm not sure if this issue is only on my side but it's very frustrated and I didn't find yet a solution for this.
Having a function inside of it I have the track method.
const { segmentProperties, eventName, payload } = data;
const { teamId, anonymousId, userId, ...rest } = segmentProperties || {};

analytics.track({
      anonymousId,
      userId: userId.toString(),
      event: eventName,
      properties: payload,
      context: {
          ...(rest || {}),
          ...(teamId && { group: { id: teamId.toString() } }),
      },
  });

The Segment sdk initialization is outside of the function context to be initialized once for all the calls.
const analytics = new Analytics({
    writeKey: configContents.segment.apiKey,
});

I've tried the batch with big number or with 1 or default, flush queue with a long time with less time or default, many options combined or tested but without any luck.
As a note I've tried also an old version analytics-node 6.0.0 but with the same behavior.

Could someone guide me if I missed something or could be an issue?
The module I use: @segment/analytics-node: 1.1.0

@aleczratiu the debugger is just a sampling of events.

@aleczratiu the debugger is just a sampling of events, it doesn't contain every event. If you want to view every event, see your data warehouse.
https://segment.com/docs/connections/sources/debugger/

Many thanks @silesky for your time! Much clearer and makes sense now.


Key-value Input

Package
filament/forms
Package Version
3.0-stable
Laravel Version
10.x
Livewire Version
3.x
PHP Version
8.1
Problem description
i do add key value input and when trying to add a new row it's adding it and deletes it at the same time
Expected behavior
the expected is to add new row without deleting it like when add new row it should show and stay in the form
Steps to reproduce
follow the Key-value docs in filament docs that what i did
Reproduction repository
https://github.com/hussainabuhajjaj/Verona-Rentakar/blob/main/app/Filament/Resources/CarResource.php
Relevant log output
No response

Could you please test if this is still an issue on the latest stable versions of Filament and Livewire, @hussainabuhajjaj?

I've test this with the following versions and I think it's already fixed
filament/filament (v3.0.37)
laravel/framework (v10.21.0)
livewire/livewire (v3.0.1)
Screencast from 08-31-2023 10:29:04 AM.webm

Thanks for checking and the clear video, @valpuia!


Multi-GPU support

MultiGPU support has been implemented in cutorch (and by extension all torch cuda libraries like cunn, cudnn etc.).

Switch the device on the fly with cutorch.setDevice(devID)
All cuda calls are asynchronous, and can be synchronized with cutorch.synchronize()

Example usage for tensors:
-- Let us do matrix addition for matrices sitting on two different GPUs
cutorch.setDevice(1)
matrix1 = torch.CudaTensor(10):fill(1)
print(matrix1) -- printing is a synchronous call, so you dont have to explicitly call cutorch.synchronize()
cutorch.setDevice(2)
matrix2 = torch.CudaTensor(10):fill(2)
print(matrix2)
matrix2:add(matrix1) -- matrix1 is seamlessly copied onto GPU2 and added to matrix2
print(matrix2)

if you want to do data-parallel training of neural nets (including convnets), your training loop can run like this:
For each mini-batch:
1. load data (preferably using multiple threads, for example using [threads-ffi](https://github.com/torch/threads-ffi))
2. loop over GPUs (the loop below will be completely anynchronous, so will run parallely)
  2.1. model[gpuX]:forward
  2.2. criterion[gpuX]:forward
  2.3. criterion[gpuX]:backward
  2.4. model[gpuX]:backward
3. cutorch.synchronize()
4. accumulate GPUx's gradParameters to GPU1's gradParameters
5. do SGD on GPU1
6. copy back GPU1's parameters to GPUx
7. cutorch.synchronize() and print accuracy etc.

Loop back to 1 for next mini-batch
Also, to train ConvNets using multiple GPUs, I recommend using CuDNN for the convolution layers, as I've tested that they are completely asynchronous (meaning that the processing runs parallely on multiple GPUs)
Comments below describe the technical details of changes made. If you just want to use Multi-GPU, you can stop reading now.

Error happens when I run the  example: it seems the math operations are not "seamless" as declared:
th> cutorch.setDevice(1)
th> matrix1 = torch.CudaTensor(10):fill(1)
th> print(matrix1)
cutorch.synchronize()
1
1
1
1
1
1
1
1
1
1
[torch.CudaTensor of size 10]
th> cutorch.setDevice(2)
th> matrix2 = torch.CudaTensor(10):fill(2)
th> print(matrix2)
2
2
2
2
2
2
2
2
2
2
[torch.CudaTensor of size 10]
th> matrix2:add(matrix1)
[string "matrix2:add(matrix1) -- matrix1 is seamlessly..."]:1: Assertion `THCudaTensor_checkGPU(state, 3, self_, src1, src2)' failed.  at /tmp/luarocks_cutorch-scm-1-6658/cutorch/lib/THC/THCTensorMathPointwise.cu:82
stack traceback:
[C]: in function 'add'
[string "matrix2:add(matrix1) -- matrix1 is seamlessly..."]:1: in main chunk
[C]: in function 'xpcall'
/home/shugao/torch/install/share/lua/5.1/trepl/init.lua:648: in function 'repl'
...ugao/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:185: in main chunk
[C]: at 0x00406670

@algred the only operation that is allowed cross-GPU is the copy operation. All other operations are checked with assertions to make sure what you are doing is not possible. To get good performance, you'll have to copy matrix1 onto matrix2's GPU and then do the mathematical operation.
If you dont like this setting, you can simply disable these assertions by adding the define DISABLE_CHECK_GPU and reinstalling cutorch.
https://github.com/torch/cutorch/blob/master/lib/THC/THCTensor.c#L761

@soumith Thank you very much for replying!
So this means to enable the Multi-GPU support as described above, the first thing need to do is DISABLE_CHECK_GPU and reinstalling cutorch? I am quite new to Torch, and can you give me some hints on how to reinstall after I change the code (i.e. adding the define)?

Does this PR support GPU Direct RDMA? Or are additional lower-level modifications necessary to run on a multi GPU Mellanox/GTX Titan X cluster?

If i do data parallel training, how does the minibatch data are split over the multi GPUs, do they split evenly by the scheduler, or just split the minibatch manually

evenly

@darksigma try looking at nccl.torch for that.

@soumith For mini-batch splitting, is there any shuffle before it? Or just split the batch evenly according to the original order of samples in the batch.

No shuffle, split evenly


Update aws-java-sdk-kinesis, ... to 1.11.768

Updates

com.amazonaws:aws-java-sdk-kinesis
com.amazonaws:aws-java-sdk-s3
com.amazonaws:aws-java-sdk-sqs

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

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

labels: library-update, semver-patch

Codecov Report

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

@@           Coverage Diff           @@
##           master     #279   +/-   ##
=======================================
  Coverage   46.57%   46.57%
=======================================
  Files          24       24
  Lines         277      277
=======================================
  Hits          129      129
  Misses        148      148

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 d4b1a04...168b4b4. Read the comment docs.


How to set the Result column?

Hi,
I noticed there is a Result column in sacredboard. How can I set the value for my experiments?

Hi!
The result is the value that your experiment main method returns.
For instance,
@ex.automain
def my_main():
    return 42

will set the result field of the experiment to 42 :-) I hope this helps.

Thank you for your prompt reply!
Great tool by the way : )

Thanks! :)


Channel order tracker

There have been a few cases of exec accidentally reordering channels, without noticing. To mitigate this, have Apollo check this order, and notify (exec) on a change.
Note: having Apollo automatically undo the change would be a problem for purposeful changes

Automatic undo is probably more of a faff than it's worth to implement. Provided the notification is descriptive enough, should be easy for exec to revert. Discord API exposes the position of a channel as a number - could work out its neighbours before and then say "between #channel-1 and #channel-2" fairly easily.
On Wed, 6 Jul 2022, at 14:11, ericthelemur wrote:

There have been a few cases of exec accidentally reordering channels, without noticing. To mitigate this, have Apollo check this order, and notify (exec) on a change.
Note: having Apollo automatically undo the change would be a problem for purposeful changes
—
Reply to this email directly, view it on GitHub https://github.com/UWCS/apollo/issues/104, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI6M5R7F3LRSPZEKKQKHLETVSWAZTANCNFSM52ZXAY4A.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


calling render with null data results in 'malloc pointer being freed was not allocated'

here is the test that replicates the issue
describe 'test-SCSS_Compiler',->

  it 'throws malloc error', (done)->
    sass = require('node-sass');
    options =
      data: null,
      outputStyle: 'compressed',
      success: done
    sass.render options

  return

which results in
node ./node_modules/mocha/bin/mocha --compilers coffee:coffee-script/register --recursive -R list tests

  1) test-SCSS_Compiler throws malloc errpr
node(9602,0x7fff7c770300) malloc: *** error for object 0x103c88e44: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6

Screenshot of error

This also occurs if data is a buffer which—it would seem—hasn't always been the case.


BUG: Some extra line are coming on hover in "HOW IT WORKS FOR TAILORS ?" section

Is there an existing issue raised for this?

[X] I have searched the existing issues

What happened?
I am exploring the web app when I found that some extra line are coming on hovering in "HOW IT WORKS FOR TAILORS ?"  section
after some time I figure out that on hovering in the line .
We get this effect ( you can see it in screenshot section )
Which is not looking good and overall is a bug in design .
I would like to work on this issue.
Please assign it to me.
Add ScreenShots

What browser are you seeing the problem on?
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'23 contributor
[X] I want to work on this issue

I would like to work on this issue if no one else is working on it currently. PLS assign it to me when possible


default theme and accent not working

Changing the flags isDark , darkAccent, and lightAccent does not seem to work.
Note: once some theme or some accent is manually selected, the manual selection works, but otherwise the default values are not set, the accents are all black and the theme is dark, which results in black on black.

Right, I can see why the default accent colors didn't load. It was a mistake on my side, for some reason the # were removed from them at some point.
About changes not being applied, I wasn't able to reproduce that. Mind sharing the config?

config-wise, here's what i tried:
OS: (1) MacOS Monterey 12.6 - Apple M1 e (2) Intel
Browser: (A) Safari Version 16.0 (176<IP_ADDRESS>.10, 17614),  (B) Firefox 111.0.1 (64-bit)
I tried (1) + (A) , (1) + (B) and (2) + (A)
I built the website with: hugo v0.101.0+extended darwin/arm64 BuildDate=unknown
are there more infos that can be useful?
I can't upload my config.toml so here it is:
baseURL = "https://squera.github.io"
languageCode = "en-us"
title = "Marco Patrignani"
theme = "color-your-world"

isDark = false

darkAccent   = "#1dbc91"
lightAccent  = "#1f676b"
presets = [ "#1f676b", "#f3a530", "#902b37", "#1dbc91", "#754e85", "#7fc121", "#a8314a", "#ff7433", "#3e6728", "#c063bd" ]

enableEmoji = true
enableInlineShortcodes = true

[params]
 logo = "/images/avatar-64.png"
 custom_css = "stylesheets/custom.css"

[markup]
  [markup.goldmark]
    [markup.goldmark.renderer]
      unsafe = true
  [markup.tableOfContents]
  	endLevel = 2
    ordered = false
    startLevel= 2

indeed, that does the trick, thanks!


Error handling when a page is deleted

In the case where a page on confluence gets deleted, but the corresponding note still exists in the obsidian vault, a 404 error results, with no further indication of what to do.  This could be a problem, if a team mate deletes a page, because you wouldn't necessarily know which page was deleted in order to delete it from your own vault.  More importantly, you might not want to delete the content from your vault, just because someone else removed it from the confluence instance.
recommend introducing an additional frontmatter tag, let's say: connie-removed-upstream.  This tag could be added automatically to a note, when a 404 error results.
when present, it means it the note will be skipped during the publishing process.

It can get set to Connie-publish: false which will exclude it from being picked up for publishing.
Will add to the list of things for  next version.

I think I'm getting this error as well.  I was testing the workflow and deleted some pages from confluence.  Now I can't upload them again.  Is there a way to manually recover from this?
Here's what the client is outputting:
❯ npx @markdown-confluence/cli
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "AxiosError: Request failed with status code 404".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Node.js v18.16.0

If you deleted them on confluence, and you want to upload them back there, you can try deleting the connie-page-id tag and re-publishing it.

I purged the files from the trash, will this remove the tags?  I couldn't find any reference to tags in the confluence documentation.  Sorry, I'm not super familiar with how confluence works and much prefer Markdown, hence why I want to use this tool.

Never mind, I found it as front matter on the markdown file.  I never thought to look there.

@cwmccann All working okay now?
Need to update the CLI results to be better at letting you know what has happened.
Started a discussion if you could put some thoughts down would be appreciated https://github.com/orgs/markdown-confluence/discussions/267

Yeah, it's working now!  Thanks.

@jvsteiner Can you test this out with the latest in main? https://github.com/markdown-confluence/markdown-confluence/commit/33dde014ccc24368f065eec0a92dba3755644fc8 should handle this. I need to do some more testing myself but so far tested in CLI and Obsidian seems to be good :)

LGTM

Awesome :) will close this off and release


g:gutentags_generate_on_new not documented

There is no mention of g:gutentags_generate_on_new in the documentation.

Fixed with 8ae5b65ebec50dd9e5eec1e5a2a407512dce244d, thanks!


Quick assist to change between if/else if/else tree and switch (in both directions)

Sometimes I have code like:
if(count==1){
  return foo();
} else if (count==2){
  return bar();
} else{
 throw ArgumentError("$count isn't a valid count");
}

And I think the code would be more concise as:
switch (count){
  case 1: return foo();
  case 2: return bar();
  default: throw ArgumentError("$count isn't a valid count");
}

It would be great if I would have a quick assist option to change both the first into the second and the second into the first (as sometimes I decide I want ifs after already having written switch statements. Of course when the if tree has a form that can't simply be converted into a switch statements no quick assist option would be shown.

Today for the switch there is already an assist:

Maybe this could now be simpler since it would only need to convert the if == to case and the current assist could do the rest.


Compute 'source_directory' default value when requested

This change is made in order to fix a bug when 'xcov' gem is used
as a dependency and 'source_directory' is not explicitly defined.
This resolves #52.

Awesome, thanks @thelvis4 👍

I've just released 0.12.1 including the fix. Thanks for the contribution and welcome! :)

@nakiostudio Thank you! 😊


add display_source field to news-flash output

Signed-off-by: Adva Klinger<EMAIL_ADDRESS>

@advak great work, added a small comment :)

The PR is good and straight forward, and could be merged as is 😃 .
I got a few suggestion that might be worth considering:

news_flash Is already a huge function. I think that any functionality added to it should be in auxiliary function, Once we will have such function it will be a lot easier to test the added functionality.
I think you should handle KeyError when going through the mapping.

Great comments, @advak what do you think?

@idosavion, thanks for your comments. I agree that the more functionality we have in news-falsh it will be better to divide it to some auxiliary functions. Regarding the KeyError, do you mean to add try, except logic when getting the source mapping? I can implement it in this commit

@advak note there is a conflict in anyway/constants.py

@atalyaalon , it's fixed


Run all voting tests against staking contract.

This creates a general purpose testing package in packages/testing
and uses that package to run all of our voting logic against our
staking contract as well as our cw20_balances_voting contract.
Followup work will add tests for our cw4 style voting as well.
From the perspective of the proposal module this sort of testing is
important because the method via which voting power is determined
should never impact the results of a vote.
In the process this PR also updates all of our cosmwasm
dependencies to their latest versions so that we can make sure to test
against the same code we'll be running.

Build error with conflicting versions of cosmwasm dependencies. Will follow up with a commit for that soon.

Build now failing for weird reasons only in cargo wasm and not in the docker container. Will investigate tomorrow. :)

Closing this in favor of another PR as the git conflicts here aren't worth the time.


Investigate background-image issues

https://github.com/brainly/html-sketchapp/pull/109 gave us basic support for background-image's and it works great on most pages:
before:

after:

but there are still a few cases where it fails e.g.

brainly.com footer

google.com search by voice icon

@mxmul maybe you'll have some ideas and some spare time to look into it ;) My guess is that background-size, that we are not taking into account, is messing things up, but I haven't got time to look into it yet.

It looks like all these issues were related to lack of background-size support which I fixed: https://github.com/brainly/html-sketchapp/issues/17


Document how to use TestCafe in WSL

We should add the following content to our docs:
https://github.com/DevExpress/testcafe/issues/1640#issuecomment-510491429
For the Chrome Linux option, there are several ways to enable GUI testing:
<EMAIL_ADDRESS>https://devblogs.microsoft.com/commandline/whats-new-in-the-windows-subsystem-for-linux-september-2020/#gui-apps

on windows
choco install vcxsrv

run xlaunch from you desktop keep all the defaults except make sure the Disable Access Control is checked
make note of the routing in the system tray.

Important to remember whatever the last bit is.  Mine was :437:0
open up your wsl shell, I was using ubuntu
sudo apt update
sudo apt upgrade -y
nano .bashrc

install whatever browsers you want to test
add the following lines to the bottom note on the DISPLAY line this is where I added the :437:0
I've only tested this with edge and chrome
alias chrome='google-chrome "$1" &> /dev/null'
alias chrome:headless='google-chrome --disable-gpu --headless "$1" &> /dev/null'
alias edge='microsoft-edge-dev "$1" &> /dev/null'
alias edge:headless='microsoft-edge-dev --disable-gpu --headless "$1" &> /dev/null'
export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):437.0

test out that you can launch chrome or whatever installed browser you are using.
chrome

If the browser doesn't launch most likely it is a firewall issue and you will need to change the windows firewall to allow public for this app.
Note if you want the edge browser to work you will need to modified the alias.js in /node_modules/testcafe-browser-tools/lib/alias.js
Add the following line under the edge browser detection
linuxBinaries: ['microsoft-edge-dev']

install edge
sudo apt install microsoft-edge-dev

test that the browser is detected
testcafe -b

if it all worked then you should see edge in the output

Great instruction! One thing, I would rather add you still need to install google chrome on wsl:
sudo apt update && sudo apt -y upgrade && sudo apt -y autoremove
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo apt -y install ./google-chrome-stable_current_amd64.deb

We should add the following content to our docs: [#1640 (comment)]

Hello, is this already added to your docs? I can't find anything about using WSL in your doc...

hello @AndreyBelym,  sometimes the remote browser does not work, the browser gets stuck on the "connected..." page.
and one problem with the vcxsrv solution is, that at least the "t.maximizeWindow()" does not work. one must also install a window manager to get it working.
i am now using kali-linux on wls2 where all things are already wired up after the installation of win-kex (their embedded vcssrv version). after exporting the DISPLAY variable, one can also use the windows terminal or VS Code console to launch a browser, but i tend to use the kali-linux terminal. just remember to install kali-linux from microsoft store app and dont try "wsl install" ... the later is not up-to-date


config example

Hello,
trying to deploy locally, but fails with
Error: Cannot find module './development.conf.json'

What could be an example development.conf.json file?

Thanks for the response!


WIP: Serve the autoyast content even when a SCC/SMT connection error happens

The service unavailable http error code (503) will only be returned now
until the first page of the setup is completed (so we have the dashboard
address to serve the autoyast profile).
When one of the following exceptions happens:

Missing registration code
Missing credentials for SCC/SMT
Any HTTP error while connecting to SCC/SMT

We will still serve the autoyast content with a comment explaining why
the system cannot be registered. The returned http error code will be
success (200), but the XML will contain a comment stating why the system
cannot be registered.
Fixes: bsc#1049948

Marking as WIP since this is a 1.0/update candidate. If we believe is not, we can just close this one.


undefined references to `sys_rand32_get'

Describe the bug
I get undefined references to sys_rand32_get'` after building a zephyr app with qemu_cortex_m3 or qemu_x86, while the same setup seems working for nrf52840_pca10056.
To Reproduce
Steps to reproduce the behavior:

https://github.com/AnyLedger/anyledger-wallet, commit 8fb0247e1ac3d61d20802eaf2f81c2511039174e
zephyr build instructions, with zephyr version picked using:

git clone https://github.com/zephyrproject-rtos/zephyr.git
DATE='Nov 7 2018'
git rev-list -1 --before="$DATE" master | xargs -Iz git checkout z

cmake -GNinja -DBOARD=qemu_cortex_m3 -DBUILD_XCOMPILE=1 ../
ninja
See error

Expected behavior
ninja completing the build
Screenshots or console output
libapp.a(compat.c.obj): In function `random32':
/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/samples/anyledger/anyledger-wallet/build/../zephyr/compat.c:26: undefined reference to `sys_rand32_get'
zephyr/libzephyr.a(coap.c.obj): In function `coap_next_token':
/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/subsys/net/lib/coap/coap.c:1484: undefined reference to `sys_rand32_get'
/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/subsys/net/lib/coap/coap.c:1485: undefined reference to `sys_rand32_get'
zephyr/libzephyr.a(slip.c.obj): In function `slip_iface_init':
/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/drivers/net/slip.c:488: undefined reference to `sys_rand32_get'
zephyr/subsys/net/ip/libsubsys__net__ip.a(net_context.c.obj): In function `find_available_port':
/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/subsys/net/ip/net_context.c:98: undefined reference to `sys_rand32_get'
zephyr/subsys/net/ip/libsubsys__net__ip.a(net_if.c.obj):/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/subsys/net/ip/net_if.c:2008: more undefined references to `sys_rand32_get' follow
collect2: error: ld returned 1 exit status
%
ninja: build stopped: subcommand failed.

Environment (please complete the following information):

OS: MacOS
ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
-GNUARMEMB_TOOLCHAIN_PATH="~/opt/gcc-arm-none-eabi-7-2018-q2-update/"

Additional context
It works with
cmake -GNinja -DBOARD= nrf52840_pca10056 -DBUILD_XCOMPILE=1 ../
while it doesn't work for
cmake -GNinja -DBOARD= qemu_x86 -DBUILD_XCOMPILE=1 ../

Try to set these in prj.conf file
CONFIG_ENTROPY_GENERATOR=y
CONFIG_TEST_RANDOM_GENERATOR=y

Thanks @jukkar.
1- This indeed fixes the qemu_cortex_m3 ninja. How did you figure out about those config options? Where can I get more info on how to identify which config=y I need?
2- qemu_x86 is still failing. I think that the problem is the toolchain that I'm using.
FAILED: zephyr/CMakeFiles/offsets.dir/arch/x86/core/offsets/offsets.c.obj
ccache /Users/lorenzo/opt/gcc-arm-none-eabi-7-2018-q2-update/bin/arm-none-eabi-gcc -DKERNEL -D_FORTIFY_SOURCE=2 -D__ZEPHYR__=1 -I../../../../kernel/include -I../../../../arch/x86/include -I../../../../soc/x86/ia32 -I../../../../soc/x86/ia32/include -I../../../../soc/x86/include -I../../../../boards/x86/qemu_x86 -I../../../../include -I../../../../include/drivers -Izephyr/include/generated -I../../../../lib/libc/minimal/include -I../../../../ext/lib/fnmatch/. -I../../../../subsys/net/lib/coap/.
Already on 'master'
Your branch is up to date with 'origin/master'.
Submodule 'tests/wycheproof' (https://github.com/google/wycheproof) registered for path 'tests/wycheproof'
Cloning into '/Users/lorenzo/gitHubRepo/nov7zephyr/zephyr/samples/anyledger/anyledger-wallet/build/thirdparty/trezor-crypto/tests/wycheproof'...
Submodule path 'tests/wycheproof': checked out '2904be69e9d666bf3064fdc15093747e695cfae6'
ninja: build stopped: subcommand failed.

I think that the problem is the toolchain that I'm using.

You can't compile qemu_x86 with a gcc-arm-none-eabi-7-2018-q2-update compiler.

How did you figure out about those config options?

I just looked existing networking samples for clues, and these two options were used in many places when compiling for qemu.

I see. I hoped there was a simpler way.
I will open a feature request. It would be useful to know which config options are needed for given functions.

FYI: I get this error on current master when building google mqtt demo for nucleo_f756zg target.


Bump to tekton v0.11.0 package

Idea:
We still running on a v0.10.1 package, which is not a latest release. We should bump to the first tekton pipeline beta release, see https://github.com/tektoncd/pipeline/releases/tag/v0.11.0

Agreed!

@routerhan for your info! If you can pick up this one once you have time, pls

@routerhan I will be working on this, while we need this asap


No resolution found at all for condition

Hey there, I have written and angular2 app that has a structure /src/app where my main.ts file is. I am using grunt to  to copy compiled files to a .tmp folder for dev (I symlink the jspm_packages folder). I am using grunt for this. At one point I was able to bundle correctly, but now I cant. I can serve the app fine but now when I try to do this jspm build app ../dist/main.sfx.js I get No resolution found at all for condition npm:reflect-metadata@0.1.3/#:crypto. Reflect-metadata happens to be the first line of my main.ts file. I have tried this command from both the root and .tmp directory.
Here are the config files, index, main etc. Any ideas?
jspm.config.js
SystemJS.config({
    packages: {
        "app": {
            "main": "main.js",
            "defaultExtension": "js"
        }
    },
    map: {
        "@angular/router": "npm<EMAIL_ADDRESS>    }
});

SystemJS.config({
    packageConfigPaths: [
<EMAIL_ADDRESS>        "npm:*.json",
        "github:*/*.json"
    ],
    map: {
        "@angular/router-deprecated": "npm<EMAIL_ADDRESS>        "@angular/common": "npm<EMAIL_ADDRESS>        "@angular/compiler": "npm<EMAIL_ADDRESS>        "@angular/core": "npm<EMAIL_ADDRESS>        "@angular/http": "npm<EMAIL_ADDRESS>        "@angular/platform-browser": "npm<EMAIL_ADDRESS>        "@angular/platform-browser-dynamic": "npm<EMAIL_ADDRESS>        "@angular/upgrade": "npm<EMAIL_ADDRESS>        "angular2-in-memory-web-api"<EMAIL_ADDRESS>        "angular2-uuid"<EMAIL_ADDRESS>        "bootstrap"<EMAIL_ADDRESS>        "buffer"<EMAIL_ADDRESS>        "css"<EMAIL_ADDRESS>        "d3"<EMAIL_ADDRESS>        "es6-shim"<EMAIL_ADDRESS>        "fs"<EMAIL_ADDRESS>        "json"<EMAIL_ADDRESS>        "lodash"<EMAIL_ADDRESS>        "os"<EMAIL_ADDRESS>        "process"<EMAIL_ADDRESS>        "reflect-metadata"<EMAIL_ADDRESS>        "rxjs"<EMAIL_ADDRESS>        "systemjs"<EMAIL_ADDRESS>        "typescript"<EMAIL_ADDRESS>        "zone.js"<EMAIL_ADDRESS>    },
    packages: {
<EMAIL_ADDRESS>{
            "map": {
                "buffer-browserify"<EMAIL_ADDRESS>            }
        },
<EMAIL_ADDRESS>{
            "map": {
                "os-browserify"<EMAIL_ADDRESS>            }
        },
<EMAIL_ADDRESS>{
            "map": {
                "@angular/core": "npm<EMAIL_ADDRESS>                "@angular/http": "npm<EMAIL_ADDRESS>                "es6-shim"<EMAIL_ADDRESS>                "reflect-metadata"<EMAIL_ADDRESS>                "rxjs"<EMAIL_ADDRESS>                "zone.js"<EMAIL_ADDRESS>            }
        },
<EMAIL_ADDRESS>{
            "map": {
                "jquery"<EMAIL_ADDRESS>            }
        },
<EMAIL_ADDRESS>{
            "map": {
                "base64-js"<EMAIL_ADDRESS>                "ieee754"<EMAIL_ADDRESS>                "isarray"<EMAIL_ADDRESS>            }
        },
<EMAIL_ADDRESS>{
            "map": {
                "when"<EMAIL_ADDRESS>            }
        }
    }
});

src/index
<!DOCTYPE html>
<html lang="en">

<head>
    <base href="/">
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
    <title>DS Portal</title>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <!-- build:css style.min.css -->
    <link rel="stylesheet"<EMAIL_ADDRESS>    <link rel="stylesheet" href="styles/styles.css">
    <!-- /build -->

    <link rel="icon" href="favicon.png">

    <!-- build:js system.min.js -->
    <script src="node_modules/zone.js/dist/zone.js"></script>
    <script src="jspm_packages/system.js"></script>
    <script src="jspm.browser.js"></script>
    <script src="jspm.config.js"></script>
    <!-- /build -->

    <script>
        System.import('app').catch(function(err) {
                console.error(err);
            });
    </script>
</head>

<!-- 3. Display the application -->

<body>
    <my-app>
        <loading></loading>
    </my-app>
</body>

</html>

src/app/main
import 'reflect-metadata';

import {bootstrap} from '@angular/platform-browser-dynamic';
import {AppComponent} from './app.component';
import {ROUTER_PROVIDERS} from '@angular/router-deprecated';
import {AuthService} from "./shared/auth.service";
import {HTTP_PROVIDERS, Http} from "@angular/http";
import {provide} from "@angular/core";
import {environment} from './config/app.config';

//The enviornment (app.config) config will be copied from the grunt build process from the root config folders
//to this central location based on the build type.

//test this again
let ConfigProvider = provide('CONFIG', {useValue: environment});
bootstrap(AppComponent, [ROUTER_PROVIDERS, HTTP_PROVIDERS, AuthService, ConfigProvider])

@DrClick quick question for you. I just started having this problem on the latest jspm@beta. Since i wasn't on the previous versions i tried to re-install those and no matter what i get the same error.

I can confirm that this is working with the latest conditional updates in SystemJS builder coming in the next release.

Released in 0.15.17.

@guybedford Thank you! Also, using jspm 0.17 has been a great experience. Thank you for that as well!


Cannot upload video to Twitter

I tried uploading video captured by Kap to Twitter, but cannot. Twitter says: The media you tried to upload was invalid.
Also cannot be played in VLC.

We're aware of the VLC issue, this sounds like it is part of that, even tho Twitter are rather specific about what kind of videos they like
We have a possible solution that we're still experimenting with, and hope to ship it with v1!