Identifiers validation failed for dataset PCS Papua New Guinea, 2022-2023

Identifier validation failed for the dataset PCS Papua New Guinea, 2022-2023:

Crawler attempt: 2
Publishing organization: TotalEnergies
Publishing country: FRANCE
Installation: IPT GBIF France
Number of occurrences indexed for this dataset at the time of the issue: 18
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 660 total records; 660 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3503709/step

New IDs sample:

Old IDs sample:

554986f6-a0e4-11ee-8c90-0242ac120002
55498c28-a0e4-11ee-8c90-0242ac120002
55498e1c-a0e4-11ee-8c90-0242ac120002
55498fde-a0e4-11ee-8c90-0242ac120002
554991f0-a0e4-11ee-8c90-0242ac120002
554994c0-a0e4-11ee-8c90-0242ac120002
554999d4-a0e4-11ee-8c90-0242ac120002
55499c22-a0e4-11ee-8c90-0242ac120002
55499dda-a0e4-11ee-8c90-0242ac120002
55499f92-a0e4-11ee-8c90-0242ac120002

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the PCS Papua New Guinea, 2022-2023 : https://doi.org/10.15468/gbz4m4.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset PCS Papua New Guinea, 2022-2023:

Crawler attempt: 3
Publishing organization: TotalEnergies
Publishing country: FRANCE
Installation: IPT GBIF France
Number of occurrences indexed for this dataset at the time of the issue: 18
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 18 total records; 18 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3503714/step

New IDs sample:

Old IDs sample:

554986f6-a0e4-11ee-8c90-0242ac120002
55498c28-a0e4-11ee-8c90-0242ac120002
55498e1c-a0e4-11ee-8c90-0242ac120002
55498fde-a0e4-11ee-8c90-0242ac120002
554991f0-a0e4-11ee-8c90-0242ac120002
554994c0-a0e4-11ee-8c90-0242ac120002
554999d4-a0e4-11ee-8c90-0242ac120002
55499c22-a0e4-11ee-8c90-0242ac120002
55499dda-a0e4-11ee-8c90-0242ac120002
55499f92-a0e4-11ee-8c90-0242ac120002

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the PCS Papua New Guinea, 2022-2023 : https://doi.org/10.15468/gbz4m4.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset PCS Papua New Guinea, 2022-2023:

Crawler attempt: 4
Publishing organization: TotalEnergies
Publishing country: FRANCE
Installation: IPT GBIF France
Number of occurrences indexed for this dataset at the time of the issue: 18
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 18 total records; 18 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3503721/step

New IDs sample:

Old IDs sample:

554986f6-a0e4-11ee-8c90-0242ac120002
55498c28-a0e4-11ee-8c90-0242ac120002
55498e1c-a0e4-11ee-8c90-0242ac120002
55498fde-a0e4-11ee-8c90-0242ac120002
554991f0-a0e4-11ee-8c90-0242ac120002
554994c0-a0e4-11ee-8c90-0242ac120002
554999d4-a0e4-11ee-8c90-0242ac120002
55499c22-a0e4-11ee-8c90-0242ac120002
55499dda-a0e4-11ee-8c90-0242ac120002
55499f92-a0e4-11ee-8c90-0242ac120002

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the PCS Papua New Guinea, 2022-2023 : https://doi.org/10.15468/gbz4m4.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset PCS Papua New Guinea, 2022-2023:

Crawler attempt: 5
Publishing organization: TotalEnergies
Publishing country: FRANCE
Installation: IPT GBIF France
Number of occurrences indexed for this dataset at the time of the issue: 18
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 660 total records; 660 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3503724/step

New IDs sample:

Old IDs sample:

554986f6-a0e4-11ee-8c90-0242ac120002
55498c28-a0e4-11ee-8c90-0242ac120002
55498e1c-a0e4-11ee-8c90-0242ac120002
55498fde-a0e4-11ee-8c90-0242ac120002
554991f0-a0e4-11ee-8c90-0242ac120002
554994c0-a0e4-11ee-8c90-0242ac120002
554999d4-a0e4-11ee-8c90-0242ac120002
55499c22-a0e4-11ee-8c90-0242ac120002
55499dda-a0e4-11ee-8c90-0242ac120002
55499f92-a0e4-11ee-8c90-0242ac120002

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the PCS Papua New Guinea, 2022-2023 : https://doi.org/10.15468/gbz4m4.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

@SophiePamerlon on dirait bien que deux je de données sont concernées (et ils ont le même titre) sont-il des doublons?

@ManonGros Après vérification auprès du data publisher, ce sont bien deux jeux de données distincts collectés dans le même pays (les titres ont été modifiés pour plus de clarté) ; le souci d'indexation semble résolu après re-publication de leur part hier car je vois bien les occurrences sur leurs pages respectives ? https://www.gbif.org/dataset/6691704f-c380-43e0-95ea-1dfd346fa109 et https://www.gbif.org/dataset/2e488e38-63f1-4912-a9c8-f8574a200f1b

En effet, merci @SophiePamerlon !


Added on_close callback to client.rb

The em-twitter gem lets us check for a closed connection, but tweetstream does not. I fixed it.
Now I can check when Twitter connection closes. Tied to the 'close_callback' and 'on_close' method in the em-twitter gem's client.rb, plus to 'unbind' method in its connection.rb.

I’ve fixed the build in master. Please rebase your branch and all the RuboCop offenses should go away.

@rayning0 thanks for the pull request. Can you squash your commits and we'll get this merged. Thanks.

Ok @stve and @sferik, I just squashed all my commits and changed the gem version back to it's original 3. Please merge my code.

Ok @stve and @sferik, I squashed all my commits and changed the gem version back. Please MERGE!

@rayning0 Thanks!


fix build.rs: Use env RUSTC if present

Use env::var_os to obtain OUT_DIR since it could contains non utf-8 characters.
Improve write_host_rs readability using raw string.
Flush the out: File in write_host_rs before returning.

Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

I'm curious; have you ever seen a build environment with a non-Unicode directory name, or is var_os here just theoretical correctness?

Well, no, I haven't seen one, but given that it is possible to do that on Linux and the filesystem can accept any zero-terminated [u8], I think it's only time until some users try to build with non-utf8 characters in their directory name.
Since fixing this only involves one-line change to env::var_os, I think it won't hurt to fix this issue.

Indeed, it doesn't look like it will hurt in this instance. But similar things do hurt in several projects I'm involved in, so I'm always curious who actually needs non-Unicode paths and why, and whether all the complexity that we pass on to everyone for their benefit is worthwhile.

But similar things do hurt in several projects I'm involved in, so I'm always curious who actually needs non-Unicode paths and why, and whether all the complexity that we pass on to everyone for their benefit is worthwhile.

Can you provide me with a few example of these cases please?
I guess it's because having to use PathBuf instead of String adds complexity and forces people to learn yet another string-type, plus it's not compatible with String/str and all the other custom string types like CompactString.


[Suggestion] Can you try and add EndScene?

I've heard that EndScene draws over OBS's recording overlay. So uhh.. Can you try and add EndScene (with directd3ddevice9) / make OBS-Proof function or smn like that

+1


Scrollbar colour on history view

Description:
History view page shows white colour scrollbar on extreme right when scrolling up and down charts.
White colour on dark themed history view page is very prominent, should a different colour be used?

@sini-maaria should this be fixed?
Install latest build, rotate screen then scroll.

I think it's fine for now. Closing.


[Bug]: SQL security rule management for operation records not translated into English

ODC version
odc423
OB version

What happened?

What did you expect to happen?
Translate SQL security rule management into English
How can we reproduce it (as minimally and precisely as possible)?

Translate English
View operation records

Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 54b46a92db5de96bfe911eadd0809a3e1390ae18
------
xiaokang
Thu Dec 21 17:21:43 2023 +0800

pass


AX Exchange error: Error Domain=Accessibility Code=0

For apps that use MFMailComposerViewController or SFSafariViewController, we're seeing a spam of error messages:
AX Exchange error: Error Domain=Accessibility Code=0 "Remote service does not respond to _accessibilityMachPort" UserInfo={NSLocalizedDescription=Remote service does not respond to _accessibilityMachPort}
and it blocks testing as the test case just hangs.

Closing as this is a duplicate of https://github.com/google/EarlGrey/issues/108


Support a db.has(key) method for testing whether a key exists in the database

For context, I am using https://github.com/Level/classic-level/ but I decided to create this issue here because it should have value for all implementations.
Currently the best available method to test whether a record exists within the database for a particular key is to read the full value of the record using await db.get(key). You can instead iterate over db.keys(), but this is much slower.
It would be nice to have a more lightweight (and potentially even faster) method to assert the existence of a specific key like await db.has(key) which would return a boolean for whether a record exists with that key.

Duplicate of https://github.com/Level/community/issues/106

Sorry I did not notice this issue in the other repo backlog. Thanks for the redirect.


feat: Add gitHub actions for checking commit style and generate release

notes
fixes #253

@patrickpichler i corrected it just now , thank you :-)

Is the format we require the commits to be in document somewhere?

@patrickpichler good idea, I will add this Contributing Guide
what's your opinion ? is there a better place to put it to make it very obvious for anyone?

Yeah the CONTRIBUTING.md seems like the right place for this :+1:

sorry it took me forever to get to this...
A general question to this:
how does release-notary behave on the non-conventional commits we have in the repo so far? I assume we will have at least one release with both types of commits when this gets merged
Also as @patrickpichler mentions please make sure to document the use of conventional commits in CONTRIBUTING.md & also add a note of whether we want to use types in addition to the feat/fix of the spec (makes sense to me to use more)
Release-notary seems to support a limited additional set of:

chore
improvement
bug
and groups the rest as other (?) - we might want to use more types still - I'll move that back to the discussion ticket

@UnseenWizzard I reached out to the maintainer of release notary and informed me I can send a pull request with more Sections for him to review  if it makes sense to be added, if not then we'll need to think of another way

@CruzanCaramele can you maybe link the issue you opened on the commit change log generator repo?
(I assume it is an issue ^^)

@patrickpichler I reached out to him directly on Twitter direct messages to ask him, I can open an issue in the repo too.
By the way I do not understand why the Test Build is failing ?


Use Remote Image

How can I use a Remote Image in Avalonia?

For others that stumble upon this question. After quick investigation I guess you mean using our Image in a way similar to WPF (https://docs.microsoft.com/en-us/dotnet/api/system.windows.controls.image.source?view=netframework-4.8) and providing web based UriSource ?
And I think the answer here is - no. You can create Bitmap from a stream, so probably this would be a good initial solution.

Good example here


Install yarn package manager for nodejs

This PR is a : New feature

[x] Documentation is written
[x] Changelog was updated

In the idea of keeping the provisioning as fast as possible and since most people still use NPM as a default, I think this should be an option and defaults to false. Otherwise 👍

Good idea. I added the 'with_yarn' parameter. Default is False

@sephii fixed

Thanks! 🍟


[HTTP] Improve API to cover different concepts

Description:
For example functions like the following for commonly used http codes can be created.
Eg : _ = caller->created(); would respond with a 201 response
and
Eg : _ = caller->ok(); would respond with a 200 OK response

Fixed with https://github.com/ballerina-platform/ballerina-lang/pull/10448


Support ExtensionDtypes as type arguments.

Support ExtensionDtypes as type arguments by reusing NameTypeHolder for DataFrame's type annotation.
Also support to infer Spark DataType from the return type annotation with ExtensionDtypes.
Before:
>>> ks.Series[pd.Int32Dtype()]
Traceback (most recent call last):
...
TypeError: Parameters to generic types must be types. Got Int32Dtype().

After:
>>> ks.Series[pd.Int32Dtype()]
databricks.koalas.typedef.typehints.SeriesType[databricks.koalas.series.NameType]
>>> def a() -> ks.Series[pd.Int32Dtype()]:
...   pass
...
>>> infer_return_type(a)
SeriesType[IntegerType]

Codecov Report

Merging #2106 (1b5d084) into master (e38ac6d) will decrease coverage by 2.04%.
The diff coverage is 78.04%.

:exclamation: Current head 1b5d084 differs from pull request most recent head f27cca6. Consider uploading reports for the commit f27cca6 to get more accurate results

@@            Coverage Diff             @@
##           master    #2106      +/-   ##
==========================================
- Coverage   95.21%   93.17%   -2.05%
==========================================
  Files          60       60
  Lines       13460    13485      +25
==========================================
- Hits        12816    12564     -252
- Misses        644      921     +277

Impacted Files
Coverage Δ

databricks/koalas/series.py
95.96% <57.14%> (-0.91%)
:arrow_down:

databricks/koalas/frame.py
95.78% <100.00%> (-0.75%)
:arrow_down:

databricks/koalas/typedef/typehints.py
89.67% <100.00%> (-4.90%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
27.27% <0.00%> (-65.29%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
47.82% <0.00%> (-52.18%)
:arrow_down:

databricks/koalas/missing/series.py
62.66% <0.00%> (-37.34%)
:arrow_down:

databricks/koalas/missing/frame.py
76.56% <0.00%> (-23.44%)
:arrow_down:

databricks/koalas/__init__.py
80.26% <0.00%> (-11.85%)
:arrow_down:

databricks/koalas/missing/indexes.py
88.80% <0.00%> (-11.20%)
:arrow_down:

databricks/conftest.py
90.62% <0.00%> (-9.38%)
:arrow_down:

... and 14 more

Continue to review full report at Codecov.

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

The PR looks great to me. Thanks!

Thanks! Let me merge this now. Please feel free to leave comments if any. cc @HyukjinKwon @itholic

👍

Looks all clear to me. Thanks for the work!


[ᚬmaster] Rc/v0.18.0

TODO

[ ] Update CKB binary version

v0.18.0 (2019-08-10)
Features

Add new chain RPC method get_cellbase_output_capacity_details (85b2f8a)
Add new chain RPC methods get_header, get_header_by_number (0a9f7af)
Add new net RPC methods set_ban, get_banned_addresses (df4a7a5)

Codecov Report

Merging #133 into master will increase coverage by 0.01%.
The diff coverage is 98.33%.

@@            Coverage Diff            @@
##           master    #133      +/-   ##
=========================================
+ Coverage   97.78%   97.8%   +0.01%
=========================================
  Files          40      40
  Lines        1084    1139      +55
=========================================
+ Hits         1060    1114      +54
- Misses         24      25       +1

Impacted Files
Coverage Δ

Source/API/APIClient.swift
95.55% <ø> (ø)
:arrow_up:

Source/API/APIRequest.swift
100% <100%> (ø)
:arrow_up:

Source/API/APIClient+Chain.swift
100% <100%> (ø)
:arrow_up:

Source/API/APIClient+Indexer.swift
100% <100%> (ø)
:arrow_up:

Source/Types/Script.swift
100% <100%> (ø)
:arrow_up:

Tests/API/APIMockingTests.swift
100% <100%> (ø)
:arrow_up:

Source/API/APIClient+Net.swift
100% <100%> (ø)
:arrow_up:

Tests/API/APIClientTests.swift
97.98% <95.83%> (-0.42%)
:arrow_down:

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 2e19a82...fac6566. Read the comment docs.


Metrics usage example at application layer.

Codecov Report

Merging #35 into master will increase coverage by 2.79%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master     #35      +/-   ##
=========================================
+ Coverage   76.11%   78.9%   +2.79%
=========================================
  Files           6       6
  Lines         427     531     +104
=========================================
+ Hits          325     419      +94
- Misses        102     109       +7
- Partials        0       3       +3

Impacted Files
Coverage Δ

src/tr1d1um/tr1d1um.go
33.75% <0%> (-0.44%)
:arrow_down:

src/tr1d1um/http.go
93.04% <0%> (-6.96%)
:arrow_down:

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 c9bca9a...444d07e. Read the comment docs.


Let update command log executed SQL

Search first

[X] I searched and no similar issues were found

Description
I am using liquibase with SQLite. One constraint I have is that all migrations going to production should be sql files - that can be reviewed by people. That is why, I cannot directly use the update command against production and would like to use the update-sql command.
Steps To Reproduce
What I tried to do is using the update-sql command, which returns the needed sql for the migration. That could be tested, reviewed and then be deployed. This generally works well.
But for SQLite a lot of operations do not support the update-sql command, because they generateVolatileStatements - i.e. talking to the database while generating sql. When looking at the database access in question, it is about geting table metadata, for example getting the current columns of a table.
Expected/Desired Behavior
I would like to run the update command against a shadow database and let it output the generated sql in a digestible way (the current sql-logs are for human consumption). The migrations would then be automatically tested, manually reviewed and deployed. This would be safe, because I know that migrations are run in order and I know that the state of the shadow database schema corresponds exactly to the schema of the production database at the point of migration.
Liquibase Version
4.25.1
Database Vendor & Version
No response
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR (Thank you!)

Hi @cornerman,
From what we have been discussing with the team yesterday the metadata issue seems to be a SQLite limitation and fixing it would require a considerable amount of work. If we want to do this, it would be nice first to identify all the different change types having the same limitation, so that we know how much effort fixing this command will require.
Thanks,
Daniel.

Hi @MalloD12,
great and thanks for the answer. I guess, with metadata issues you mean that we need to get the required column information for a table when recreating tables for, e.g., drop-column, add-column, foreign keys and set-nullability.
While the first two are fixable with newer versions of sqlite (I am happy to PR a fix for these). The latter two will afaik still need this information. So, I am not sure, we can make them non-volatile.
Are you open to the proposal above that the update command can output the executed sql? Because that will work for these kind of cases.

Hi @cornerman,
Yeap, we are fine with your proposal addressing this issue in the way you described above. Feel free to create a PR for it, we will be happy to review it or assist you with any additional questions you have.
Thanks,
Daniel.


[#3] Fix date parsing on Android Hermes engine

Closes #3
Due to returning NaN when parsing Date:

https://github.com/facebook/hermes/issues/136
https://github.com/facebook/hermes/issues/84

I don't understand this sum:
date.setUTCMilliseconds(date.getUTCMilliseconds() + milliseconds);

I can see that the UTC milliseconds of the date var are always 0 because you don't pass a millisecond value to the UTC method. Am I missing something? This sum seems to be useless to me.

@info-bit Yeah, I also think it's useless to sum that zero. It was originally here from forked repo, I don't change it.
It's not related to the issue #3, we can remove that sum in another PR

@info-bit please approve/reject PR review, it's pending

I tested with and without Hermes and it worked fine.


pull request for e2e test at 01/03/2017 02:56:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Raise CLIErrors based on certain build statuses

When streaming logs, reads metadata from the Azure blob and raises CLIErrors for certain statuses. This causes the process to return 1 as an exit code which can be used by other people.
Fixes #121

I’ll defer to @northtyphoon  and you to make this decision on perf and structuring the status.  The main criteria is that we only return success if the build is successful.

@djyou can you merge your branch w/ dev


Warning for FourierOp for Cartesian data without CartesianSamplingOp

The FourierOp applies a FFT along Cartesian direction even if they have not previously been resorted correctly with the CartesianSamplingOp. This leads to wrong voxel size/dimensions.
Suggestion: Check in FourierOp  if FFT can be applied (centered k-space, correct sorting of data points) otherwise use NUFFT. Print warning to suggest that it might be faster to use CartesianSamplingOp before calling FourierOp
Challenge: How to figure out if FFT can be applied...

a) For devciding if FFT or NUFFT, the Fourieroperator should test if all differences between k-space points is 1.
For an FFT to work, we dont need the points to be on an integer grid.
We need that the difference between neighbouring points is constant and that the k-space center is either in the array center.
b)  I would like some function that sorts the Kdata and trajectory once if possible, avoiinding many sorts- and unsorts in CG.
So in the reconstruction method, we would call this function once, and if the data can be sorted, it would sort the KData.data and KTrajectory and we would continue with sorted KData in the reconstruction, Was there some issue with this approach I forgot about?

Add a) this is only true if the CartesianSamplingOp is not applied. If it is going to be applied or not is not known when we create the FourierOp so there is imo no way we can choose the nufft for unsorted Cartesian correctly.
Add b) presorting we discussed before with the challenges of (i) potentially very large datasets with lots of 0s and (ii) the need of a mask inside CG to select acquired kspace points.

Ah ok, so the Fourier operator should check if the k space data is consecutive. If not, it should use a composition of FFT and Sorting Op...
For presorting, we would need a function that also changes the Trajectory. It should be similar as the remove oversampling preprocessing..


Add delete and check-functions for MongoDB stored Items

Hello Joachim, the PR looks very small and tidy, I like that! There is nothing I would really change.


ConsulRegistry keeps the first service url discovered in cache

Brief
We found a bug in ConsulRegistry that the registry cache (in AbstractRegistry) keeps the first service url discovered, which is not sync with the Consul service registration changes happen after.
Symptom
When a service (e.g. Consumer Proxy) subscribe a service through ConsulRegistry, it does get notified when new service instance becomes available or offline. If all service instances gets deregistered, however, ConsulRegister still remembers the first service url discovered. If any request comes in at this time, the consul client will "discover" that outdated service url as a result.
If any new service becomes available after, consul client can discovery the new service url, but will keep "discover" the original url when no service available again.
This behaviour can also be verified through the debug logs from LightCluster in this scenario.
Investigation
ConsulRegistry has its own cache that holds the result of previous service discoveries. The cache is maintained by its own notification listener which keep the discovery result sync with the changes in Consul registry.
LightCluster's discover method call the subscribe and discover methods in the Registry interface when there is no service url found in its own cache (Line # 103-108).
The problem is the  implementation of the subscribe and discover method called by LightCluster are implemented in base class AbstractRegistry, which has its own cache for the discovery result (i.e. subscribedCategoryResponses). Unlike ConsulRegistry, this cache does not get updated when service registration changes in Consul.
Solutions

In LightCluster, do not call subscribe or discover method from the Registry interface.
This seems to solve the issue, but also breaks some existing unit tests. I think the calling for discover method is required for other Registry implementation like DirectRegistry
When LightCluster subscribe the service, do not call the "notify" method which is implemented in the AbstractRegistry class. So that the unmanaged cache in AbstractRegistry will not be populated with any value and no outdated content will be stored as a result. This solution passes current unit tests.

I will create a PR using the second solution.

@jsu216 Nice findings and good analysis. In hindsight, we shouldn't make the service registry and discovery this complicated. The original idea is to support others like zookeeper and etcd, etc. But now, only Consul is being used widely.

@yibogithub Is this the same issue your project was faced?

It is correct that the first URL in the discovered list is the one which was cached.
However, some time ago, we made a change where a dropped connection would result in a "re-discover", therefore resulting in a new list. A problem remains if the refreshed list has the same URLs and returns them in the same order.

 ConsulRegistry keeps the first service url discovered in cache 1.6.x

 ConsulRegistry keeps the first service url discovered in cache master

@ddobrin @yibogithub Is this the same issue your project was faced?

I believe our problem was only about our own usage of LightCluster. Did not know there was problem with LightCluster and ConsulRegistry. I was testing with the mock registry.

@ddobrin @yibogithub Thanks a lot for the clarifications. Let's treat it as a separate issue then. I just want to make you aware this PR might have an impact on your issue potentially.


Automated Package Upgrade

:tada: This PR is included in version 7.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add a property for the version of browser compatability

Add a property for the version of browser compatability

good read:
https://stackoverflow.com/questions/6771258/what-does-meta-http-equiv-x-ua-compatible-content-ie-edge-do

The implementation makes little sense. It is always good to emulate the latest version of the browser / internet explorer


Change the type of the ConnectivityServiceEndPoint layerProtocol

To support technology specific attributes for the ConnectivityServiceEndPoint, it is proposed to change the type of the layerProtocol attribute of ConnectivityServiceEndPoint from LayerProtocolName to LayerProtocol.

It would be worthwhile having the description of some use cases and/or examples where we need to configure layerProtocol technology-specific attributes

TAPI Call 6/6/2017:  Agreed - It was also noted that this issue and related use cases are described in the ONF contribution onf2017.037.xx which was presented/discussed at the ONF Heidelberg interim meeting (Feb 2017) as well as subsequent TAPI calls. As a result of those discussions, the group agreed to add the LayerProtocol attribute to the ConnectivityServiceEndPoint to enable specification of layer-specific information in the ConnectivityService request.


Usage without firebaseAdminInitConfig object in the config raises app/invalid-credential error

Describe the bug
When using the package without service account credentials, and without firebaseAdminInitConfig object in the config, firebase admin raises an error when /api/login is called.
  errorInfo: {
    code: 'app/invalid-credential',
    message: 'Failed to determine project ID: Error while making request: getaddrinfo ENOTFOUND metadata.google.internal. Error code: ENOTFOUND'
  },

I think it might have with the fact that we spread firebaseAdminInitConfig here but we do not reuse the project id. https://github.com/gladly-team/next-firebase-auth/blob/77a6280133d95aa0cbce01f293d0267e35d9fc0b/src/initFirebaseAdminSDK.js#L16-L23
Maybe we could add a projectId entry to the package config that is then passed to both admin and client config objects ?
Versions
next-firebase-auth version: v1.0.0-canary.7
Firebase JS SDK: 9.6.6
Next.js: 12.0.10
To Reproduce
I will create an example repo later this week
Expected behavior
setAuthCookie calls do not fail

Note : adding
firebaseAdminInitConfig: {
  projectId: "some-project-id"
}

in initAuth helps working around this issue

Thanks for the issue!
Is there Firebase documentation about needing a project ID when initializing with default credentials? I don't see it in the docs. However, a project ID is needed when testing with gcloud credentials. Is that where you're running into the problem?

Closing until there's more info.


update https://openpolicynetwork.org/resources/meetings/ with 2016 meeting times

https://openpolicynetwork.org/meetings/


Error trying to signup on the website

Attempting to check out this project and I can't signup to try out the software.
Whenever I attempt to register an account on the mypods website linked from the official website, I get the following error:
Service 'auth.account.create' is not found

Heyho, thanks for opening the issue and nice to hear that you are interested in the project :)
Sorry for the late reply, we are on summer break a bit.
Regarding https://mypod.store there was an issue with the server which prevented the backend from restarting correctly. I just fixed it and the server is up again.
If there is anything else, let me know here or open a new issue :)


Infinite loop in checkpoint_test.py

Causes timeout when running Python tests on TravisCI: https://travis-ci.org/lukeyeager/caffe2/jobs/240150765
It's super easy to reproduce locally:
pytest -v caffe2/python/checkpoint_test.py

This test is pretty convoluted. I tried to dig in and figure out what the test is supposed to be doing, but I'm going to give up and let the authors of this code figure it out.
/cc @boryiingsu

Thanks for reporting. I am looking into this problem. Will update once this problem is solved.

Appears to be fixed by https://github.com/caffe2/caffe2/commit/14bda514f78abcc5a4dfe1d5d232f203dfd53a1b and https://github.com/caffe2/caffe2/commit/2f49ef3729abe009ddd458ddf613bd15f86a363d. Thanks!


Is there any desrializer assoiciated with this ?

I saw your post and it was an eye opener for me. I wanted to understand, how can I regenerate the original document from the inverted index and if really can't do the indexes in some of the fields then wouldn't it be better to just compress those via Gzip etc.

I actually can't remember, I haven't touched MongoDB in 5+ years. You'd need to map to and from the more concise structures in the app layer, and need to strike a balance between operations you can perform in the app and in the database. The main point I was trying to make was that you can make design tradeoffs between document structure and size, leaving some of the features (e.g. indexing) in play along the way, and you can do so much better than resorting to cryptic attribute names. Compressing the document with gzip is the furthest you can go in this direction , you lose all ability to index/query the document and need to do everything in the app layer.


Suggestion on migration messages in console

Do migration when not shut down the current running Harbor with showing message 'MySQL is not running' is not clearly and friendly.

Agree I will see how to fix it

Fixed in #1024


Allow additional imports with natalie-imports.json

@krzyzanowskim
Here's a proposed fix for https://github.com/krzyzanowskim/Natalie/issues/37, as per phimage's suggestion.
This commit modifies natalie.swift so it can take a second argument imports_file_json. This JSON file must contain an array of all the framework names to import and that natalie might not be able to autodetect (see original issue).
For example, in natalie-imports.json:
["FlatUIKit"]

and then:
$ natalie.swift <path_to_project> natalie-imports.json

which will add import FlatUIKit right before custom module imports.
A couple notes:

In a perfect world I would love natalie-imports.json to be automatically detected in projectdir, but since the documentation says that the path should be projectdir/projectname we'd have to go one directory up and that seems a bit hacky.
Having a long argument like --additional-imports natalie-imports.json would be best, but I didn't want to add too much code without your approval (since we'd need to hack around Process.argv)

Let me know what you think about this solution and how to possibly improve it.

To be automatically detected in our perfect world you can put the file near the storyboard with specific extension, as I do with my PR https://github.com/krzyzanowskim/Natalie/pull/48/files
Without that XNatalie or a generic launcher will not add the additional command parameter

what is wrong with specyfying module in storyboard? this is the easiest way to handle it. Configuration file introduce complication how to deal with the file, where to store etc. I'd like to realy avoid that as long as possible.

you can't specify module for objective-c framework, this is what I understand in the corresponding issue

@phimage --additional-imports or any option would be good to have for this.

Yes option is far better than adding an extra argument behind the file path
But option

break XNatalie (or need to ask options, register it by project) or other launch shortcut
more codes and dev , except if third party command line parser is included in Natalie

I prefer configuration files by storyboard because

Natalie generade code for multiple storyboards and each storyboard have its own issue and could be generated alone for test (and option could be forgotten)
No need to change generic command line, launcher, etc...
Easy to add other configuration options for other issues

that's why I make "plist" into PR #48
then plist VS json, the two are easy to read, but in Xcode I prefer create and edit plist file

As a side note, if a solution is found to the issue #64 I just opened where I ask for a feature to have Natalie parse an xcodeproj file to generate target specific files, Natalie could automatically find out which frameworks each target is linked with.

@phimage I like the solution of a configuration file next to the storyboard. Not really a big fan of the plist format but at least it's consistent with what apple uses.
@hartbit Agreed that your solution would be best, maybe we could iterate by merging https://github.com/krzyzanowskim/Natalie/pull/48 and https://github.com/krzyzanowskim/Natalie/issues/64 when it's code-ready?

hello, I want merge this change, can you please rebase to current codebase ? :+1:
This feature need documentation in README too.


Update ansi

This PR:

merges changes from upstream
adds no_alloc feature disable all things that need allocator
syncs up ansi module with a reference implementation in alacritty_terminal crate

Closed because of PR in upstream


Use graphql-java 4.2; Move away from deprecated API use

Hi @jcrygier , there seems to be a bunch of changes at https://github.com/cchiaverini/graphql-jpa and I wonder if it makes sense to merge those changes to here so everyone benefits of combined effort. Maybe suggest a pull request?

The changes in my branch are somewhat fluid right now based upon the needs of my prototype project.  While I'm thrilled that people are interested in them, I haven't submitted a pull request back to the main repository because I don't consider them ready for public consumption.  There are still outstanding issues regarding the N+1 problem, nested filtering, etc. that should be addressed.  I've also been working in a silo, so my changes/needs may conflict with @jcrygier 's vision.

@cchiaverini completely understand and makes sense your approach. Just want to spread awareness and make connections so we can collectively move this project forward. Thanks to @jcrygier for starting it and yourself for spending time evolving it.

@cchiaverini I've also got some changes that I'm not sure about creating a pull request for and it would be good to discuss somewhere. Maybe a Github issue is a good place to start


TECBase and classes inheriting from it should no longer subclass dict or access their attributes like dict.

They should access attributes like a normal class. For example
t = TECBase(...) # Initialize object
t.emitter # Should return the `Electrode` object which is `t`'s emitter

as opposed to
t = TECBase(...) # Initialize object
t["Emitter"]

Since the refactor as of release 1.0.0-0.1.0, this issue is closed.


Merge config-seed into edgex-go

#517
This PR contains work to merge the config-seed service into the edgex-go repo as has been discussed on the Core WG calls. There are several points to note w/r/t this PR:

The PR looks bigger than it is due to all of the application.properties files that had to be brought over. This is so that we can avoid config file duplication between two repos.
As described on the calls, the goal was to achieve functional parity with the existing core-config-seed-go service. No functionality for Config V2 has been added yet.
Today the config-seed is not run unless one wishes to exercise EdgeX via docker containers, so I have not added it to the make run command. It IS present in make build. You can run the service via

cd cmd/config-seed
./config-seed

I have added a docker target for creating the relevant image. I have tested this locally and verified Consul population.
No accounting has been made for Snap deployment here. I was discussing my approach with @tonyespy last week and sent him the included Dockerfile. Feedback is TBD.
For the legacy application.properties files, I put these in the local .config-seed/res/properties directory. This seemed the easiest to me and this directory will be removed after Edinburgh. (This was shown on last week's Core WG call)
For the Go services, TOML is assumed. If not running the services via local cmd line, then one needs to use the "--cmd" command line property to specify where the edgex/cmd directory lives (this includes via GoLand IDE)
Approval/merge of this PR is a pre-requisite for continuing on with the Config V2 work

I look forward to any comments/input you may have.

@drasko As I said, I'm trying to achieve functional parity with the current config-seed-go which uses ";". When we get to config V2, the need to use ";" will go away. I need this PR to be accepted first.

@tsconn23 OK then - approved.

https://github.com/edgexfoundry/ci-management/pull/209 should be merged before this is merged.


Add comment to each PR displaying position in stack

Similar to ghstack or spr or graphite, it is hard to keep track of what is going on if there isn't a comment on each PR showing the relationship of each PR in the stack and the order in which they reside.
Something like this for illustration:

Hey @mattd-tg thanks for reporting this issue. That specific functionality works  as after you create an account and configure Aviator API token.
See for instance:
https://github.com/jain-av/mq-demo/pull/1890

Ah I see, didn't have the token set up. Thanks!


My feature

The PR diff shows changes across multiple files in the project. Here are the modified and new files:
Modified Files:

src/core/MusicPlayerCore/index.ts
src/core/VueMiniPlayerCore/index.ts

New Files:

src/core/VueMiniPlayerCore/index_2.ts
src/core/VueMiniPlayerCore/new-index.ts

According to the given coding standards, several issues and improvement suggestions are outlined below:
Issues:

Non-descriptive variable names. For example, variable name changed to a from WrapperID and b from app.
Some variable and method names are not following the camelCase convention as specified in the coding standards. For example, Prev-Song, SONGinfoLIST and Wrapper-ID.
Single letter variable name j is used in the for-in loop, which goes against the standard of avoiding single-letter variable names (except for loop counters).
Inconsistent use of spaces and indentation was noticed in some places.
The triple equality "===" may have been used mistakenly instead of double equality "==" or assignment "=".

Recommendations:

Use descriptive variable names that describe their purpose or usage.
Maintain usage of lower camelCase convention for variable names and upper CamelCase for class names.
Make sure to use spaces and indentation uniformly for better readability.
Correct the likely mistaken usage of triple equality "===".
Add more comments or docstrings to new functions for clarity.


Minor typo

"After the it is created," should be "After it is created" or "After the account is created"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 65ef452c-ff25-a2ec-feba-5dafa56cb918
Version Independent ID: 733a3a55-e899-5c1d-9bcc-34c2d7e17d27
Content: Getting started with SQL queries in Azure Cosmos DB
Content Source: articles/cosmos-db/sql-query-getting-started.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @timsander1
Microsoft Alias: tisande

@misterspeedy Thank you for the feedback. We are actively investigating and will get back to you soon.

@misterspeedy thank you I fixed the issue in the above PR. In the future, if you see any issues, you are welcome to contribute to docs. Please click on the edit button on the page and submit a PR.
We will close this issue now.
#please-close


pressing F7 does nothing Forge 1.16.5.

still investigate though in case i did put it back and didn't forget to put it in my mods


ion-tabs (Color tab and badgeColor) Not Working Beta.13

Bug Report
Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
Ionic:

   ionic (Ionic CLI)          : 4.1.2 (C:\Users\PC\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.13
   @angular-devkit/core       : 0.7.5
   @angular-devkit/schematics : 0.7.5
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : not installed
   @ionic/schematics-angular  : not installed

Cordova:

   cordova (Cordova CLI) : 8.1.1<EMAIL_ADDRESS>   Cordova Platforms     : android 7.1.1
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.0, (and 4 other plugins)

System:

   NodeJS : v8.12.0 (C:\Program Files\nodejs\node.exe)
   npm    : 6.4.1
   OS     : Windows 10

Describe the Bug
in the update they mention that the beagle thing is working and it still does not work.

I attach the section, tabs: badgeColor works again (3d98587), closes #15559 #14840

I also detected that with the update the color of the ion-tabs does not change anymore, neither the position top and bottom
Related Code
BadgeColor:

I use this: badgeColor="success"

Ion-Tabs:

I use this: tabbarPlacement="top" color="danger"

Expected Behavior
I hope you can check and if it is failing or if something is damaged when I made the update.
thanks.

Thank you for the issue! I'm going to close this as a duplicate of #15942. I know it doesn't mention badge color in the original issue, but please refer to my comment here: https://github.com/ionic-team/ionic/issues/15942#issuecomment-433429959
In 4.0.0-beta.14 badge color will be set by adding an <ion-badge> into the tab button with a color property. Thanks!


Handle RuntimeError raised by uvloop on closed transport

Fixes #17

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #18   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         139    139
=====================================
  Hits          139    139

Impacted Files
Coverage Δ

aiologstash/base_handler.py
100% <100%> (ø)
:arrow_up:

aiologstash/__init__.py
100% <100%> (ø)
:arrow_up:

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 f540e8b...346b4cc. Read the comment docs.


ShaderCacheMode,2 lets amdgpu-pro Vulkan driver write shader cache to disk twice

amdgpu-pro Vulkan driver has on-disk shader cache enabled by default for some time now, it stores them at ~/.cache/AMD/VkCache. But when you set ShaderCacheMode,2 in amdPalSettings.cfg, it additionally also creates ~/.cache/AMD/ScpcCache and stores cached shaders there as well. This is redundant and one of the paths shouldn't be used.
At this occasion, it would be nice to enable the on-disk shader cache by default also for the amdvlk-open driver to get it in line with the -pro/Windows driver. Especially since the shader compile times with the open compiler take longer.

Hi @aufkrawall,
As far as I know, amdgpu-pro Vulkan driver has two cache mechanisms, one is pipeline cache and the other one is shader cache. So as you mentioned, ~/.cache/AMD/VkCache is for pipeline cache and ~/.cache/AMD/ScpcCache is for shader cache.
For amdvlk-open driver, the pipeline cache has been enabled by default.
Thanks,
Kai

Hi @aufkrawall,
As far as I know, amdgpu-pro Vulkan driver has two cache mechanisms, one is pipeline cache and the other one is shader cache. So as you mentioned, ~/.cache/AMD/VkCache is for pipeline cache and ~/.cache/AMD/ScpcCache is for shader cache.
For amdvlk-open driver, the pipeline cache has been enabled by default.
Thanks,
Kai

Is there any difference in practice between pipeline and and shader cache in amdvlk? With amdvlk-pro, shader compile stutter is definitely eliminated by the data stored by default in VkCache. amdvlk-open doesn't store any data by default in ~/.cache/AMD. It only does so when explicitly setting ShaderCacheMode,2. Without this option set, games played with amdvlk-open show bad loading times and shader compile stutter every time they are restarted, as shader cache is only stored in RAM (also PAL docs say that). This is different with amdvlk-pro.

Is there any difference in practice between pipeline and and shader cache in amdvlk? With amdvlk-pro, shader compile stutter is definitely eliminated by the data stored by default in VkCache. amdvlk-open doesn't store any data by default in ~/.cache/AMD. It only does so when explicitly setting ShaderCacheMode,2. Without this option set, games played with amdvlk-open show bad loading times and shader compile stutter every time they are restarted, as shader cache is only stored in RAM (also PAL docs say that). This is different with amdvlk-pro.

Ok, I stand corrected: Like you said, also recent amdvlk-open releases indeed cache shaders inside VkCache by default and pipeline caches stored in LlpcCache and ScpcCache are indeed just tiny. In fact, they seem to be just empty 0 byte files with amdvlk-pro.
Thanks for turning shader cache on by default!

Ok, I stand corrected: Like you said, also recent amdvlk-open releases indeed cache shaders inside VkCache by default and pipeline caches stored in LlpcCache and ScpcCache are indeed just tiny. In fact, they seem to be just empty 0 byte files with amdvlk-pro.
Thanks for turning shader cache on by default!


Option to not allocate the default gateway

Output of docker version:
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   9894698
 Built:
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   9894698
 Built:
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 10
Images: 289
Server Version: 1.9.1
Storage Driver: btrfs
 Build Version: Btrfs v4.2.2
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.3.6-coreos
Operating System: CoreOS 899.9.0
CPUs: 4
Total Memory: 7.655 GiB
Name: media-srv-1.lungo.co.uk
ID: ANSS:L2RV:YMWL:ZS3X:VYHV:GGQC:HGXQ:YUZS:LGFT:4OXN:QC4P:63G4

Provide additional environment details (AWS, VirtualBox, physical, etc.):
Physical
List the steps to reproduce the issue:

Use brctl or any other means to create a bridge to an existing network, in my case the bridge is called br-services
Run docker network create -o com.docker.network.bridge.name=br-services --subnet <IP_ADDRESS>/20 --ip-range <IP_ADDRESS>/23 --gateway <IP_ADDRESS> services to create a bridge network using the existing bridge device.

Describe the results you received:
Network is created and <IP_ADDRESS> is allocated to the bridge device on the host.
Describe the results you expected:
There should be an option to not allocate the default gateway address to the host machine. In my case I have created the bridge to a vlan network which has a router running on <IP_ADDRESS> which I would like to be used as the default gateway.
Provide additional info you think is important:
Enabling such option should automatically set com.docker.network.bridge.enable_ip_masquerade to false.
Let me know if you need any more details.

This functionality was eventually also requested in https://github.com/docker/docker/issues/20758.

Seems to be requesting the same functionality, this may be closed as duplicate if deemed so.

Yes, let's close this one to keep the conversation in a single location, thanks!


I can't see audio formats :(

Hello sir, I can't see video formats. Like 2.0 - 5.1, pls fix it.

It works for me, both on my Linux desktop and my Macbook. Are you loading the extension correctly? If you load it as an unpacked extension, you need to checkout/download the patch-1 branch, not the master branch.

with 1.21.1 it's working, thanks so much, sir :) win10 cent browser.

at series dubbing and audio formats window opens every time :(, can you fix ?

No, it's supposed to close automatically, but if it doesn't you can simply hit Shift+Ctrl+Alt+S to close it.

This happens every time :(

What can I say, except that you are the only person to ever report this. I can't reproduce your issue and there is nothing in the code that would open that window so it's probably a conflict with some other extension you have installed. Maybe try disabling all extensions and then re-enable them one at a time to get to the real culprit.

The bitrate menu issue has been fixed in version 1.23.0.


When is Attach called?

Playing around with the MIEngine implementation has given some insight. It looks like when the SDM calls IDebugEngineLaunch2::ResumeProcess, the code natvigates to a IDebugPortNotify2 instance and adds the program node. The implementation of IDebugPortNotify2::AddProgramNode calls Attach before it returns.
https://github.com/Microsoft/MIEngine/blob/master/src/MIDebugEngine/AD7.Impl/AD7Engine.cs#L677
This obviously depends heavily on who is implementing the debug process and the port. If the debug process is coming from a custom port implementation (i.e. a process running on a remote machine), does the implementer have to also implement the IDebugDefaultPort2 and IDebugPortNotify2 interfaces? If so, how do those implementations force the SDM to call Attach?
Thanks!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9bec0601-d4d8-f75e-a52a-af41718a241e
Version Independent ID: a341eb85-a6a1-7324-c0d2-ebf7e9e5e68b
Content: IDebugEngine2::Attach - Visual Studio
Content Source: docs/extensibility/debugger/reference/idebugengine2-attach.md
Product: visual-studio-dev15
GitHub Login: @gregvanl
Microsoft Alias: gregvanl

@jordan83 Thanks for your feedback; we appreciate it. To make sure that this is logged in the right place, please use the Report a Problem tool to report the issue. When you do this, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.


NuGet.Jobs - Refactor JobArgumentNames.cs

Refactor JobArgumentNames.cs so that NuGet.Jobs.Common only holds common argument names. Job-specific argument names should be moved into their respective job.
https://github.com/NuGet/NuGet.Jobs/blob/19b7d028bb69d1ccf16e221aeda5fe6b98cc66e3/src/NuGet.Jobs.Common/Configuration/JobArgumentNames.cs

Not sure this is still relevant.


Failed to lookup sumbol 'poseidon_hash2':dlsym

Release mode on iOS
Tested on iPad/iPhone
Repository to test: https://github.com/bibash28/polygon-id-test
Command: flutter run --release
Implemented as per readme instruction
Screenshot:

Hi @bibash28 just tested on release mode your project and you need to do the following to fix the issue. Open Xcode xcworkspace of your project, go to Runner target -> Build Settings and set "Dead Code Stripping" value to NO.

Comment from Romauld:  We can't set "dead code stripping" to false. With this configuration we can't build our app because other SDKs are getting duplicate symbols. Any suggestions @rauljareno ?

Hey @bibash28 , you already followed these steps as suggested in the link:
Stripping iOS symbols:
In Xcode, go to Target Runner > Build Settings > Strip Style.
Change from All Symbols to Non-Global Symbols.

Hey @otto-mora,
No, I have not followed. Let me try.

Hey @otto-mora,
Thank you , this solved the issue..

Hey @otto-mora,
Sorry, I was not testing in release mode..

Hey @bibash28 did it work in the end? Can you confirm please or let us know any other errors you might be seeing?

Hey @otto-mora, it is not working on our side... Same issue from start...

@bibash28 just added a fix to develop branch, could you please check again? thanks!

Not solved... @rauljareno @otto-mora

@bibash28 thanks for the feedback, I added new fix to develop branch also for that symbol and the rest that might be missing, could you please check? thanks!

working now. Thank you.


quotes=preferSingle/preferDouble behave more like forceSingle/forceDouble

I have YAML like:
some_string: "This isn't working"

If I set quotes=preferSingle, the formatter outputs:
some_string: 'This isn''t working'

Even though the docs say that the opposite quote style is used to avoid extra escapes:

"preferDouble" - Use double quotes as possible. However if there're escaped characters in strings, quotes will be kept as-is. (Recommended) (Default)
"preferSingle" - Use single quotes as possible. However if there're \ char or " char in strings, quotes will be kept as-is.

Current behavior: https://dprint.dev/playground/#code/G4QwNgrgpgXABAcgBJTGA9gQgQWAFD6iRQBM8ARACoAWAlgM5wMB2CALnCHALZT30gA5lAB05IA/config/N4WAUABBBEAOBOBLAdgFwOqICaoBbQC4IAOABgBpwpoBXAZwFMAVAQwCM7CIAzFgG0aVIMFFgZpMOfEQBMQ6nxQMAQvAYsA1l2h9u0eTACONAPaoGnInDXcG8AMooA5nwb6qMVPBaJFyJwDCJgC2wSxcXjQMBtDcJvBhqEGh4qiWPPyCHtCiqcp8JgDGGvYMxuKFDACSyACyLLAR8FExbN6V9rAshc5NLdlt3RoMqJ3dvUS8AtHZXojBTN6+zui4iOZ0XZXpkTPC0HMLS35OAFp2JlxTWfuITsjxDMnBqQAiiGqFqIgAbm5WCBGqAAngBaYEsYJ8UF3B5qaDgAC+4CAA/plugin/pretty_yaml
What I would expect (e.g. prettierish): https://prettier.io/playground/#N4Igxg9gdgLgprEAuEA3AhgGwK5yQAgHIAJOTTCAQkIB0o6Mc4AmAmkAFQAsBLAZ3z8ohGPnT4AtnD590AczgA6diAA0ICAAcYPaH2Sh0AJyMQA7gAVjCfSixn0AT33qARkfRgA1nBgBldCkAGR4oOGQAMyw+ODcPb18-TU9QuWQYI1x1GIkedMzYkDgAD004Ix4pWCwOcqhjHmlI6MK+VMw4AEVsCHh8rJAAKz5iv3aunr6kKMwY9QBHSbgLU01bEHQ+AFowuAATfbUQDPQeTFSAYQgJCXRkDfIjtqg5DoBBGAyeV2x4C3KQmFmrNClwYBJMAB1XjwPjJMBwPw2Hg6VAoxz3MAyI6oXAASSgB1gfjAFW0b0Jfhgjg6wLmIE0phikI8mnujOk5VQ4XUoRiRhgK3ktzphWSRn590cgUwR0ZoRgkJ4exgXGQAA4AAzqIxwRY8XVCuQi6YtdQwdCuJUqtVIZjqbAxDiW2wzelwCSufYHPZBdAvbDyOAAMQgRlun1S93QvwgIAAvvGgA
A code example: https://github.com/microsoft/TypeScript/compare/main...jakebailey:TypeScript:pretty-yaml

Sounds reasonable. I'm going to change the behavior of preferSingle/preferDouble and add alwaysSingle/alwaysDouble options, but the default option value will still be preferDouble.

Thanks! Yes, "always" is probably the right term.

Released v0.5.0.

Thank you!


Parsing failure when omitting name of associated value in enum

Tailor Version: v0.11.1
Swift Version: 3.0.1
Platform (Mac/Linux/Windows/CI): Mac
Installation Method: Homebrew
Steps to Reproduce Issue

Make a new file with

`enum DataState {
case empty
case any(data: T)
}
enum TableViewState<T: String> {
case data(_: DataState)
case error
}`
Expected Behavior
File parsed
Actual Behavior
Parsing failed:
line 8:12 mismatched input '_' expecting ')'

@valerianb, thanks for reporting.  We are looking into it.

@valerianb, I apologize for the delayed response.  It looks like the code snippet you shared does not compile.
I removed : String from the sample code you shared and tailor appears to parse it correctly.

Would you be able to provide an example that compiles and illustrates the parsing failture you are experiencing?

No worries for the delay.
Here's the original code:
enum TableViewDataState<T> {
  case empty(infoViewContent: InfoViewContent, data: T)
  case any(data: T)
}

enum TableViewErrorState {
  case offline(infoViewContent: InfoViewContent)
  case error(infoViewContent: InfoViewContent)
}

enum TableViewState<T: DateableResult> {
  case data(_: TableViewDataState<T>)
  case error(_: TableViewErrorState)
  case placeholder

}

protocol DateableResult {
  var age: Date { get }
}


What's new in Windows app SDK 1.5 experimental 1?

Describe the bug
What's new in Windows app SDK 1.5 experimental 1?
Windows app sdk 1.5 experimental 1 更新了什么？
At present, the Windows app SDK 1.5 experimental 1 has provided an installation package in nuget, but no changelog has been provided, and we hope to release a changelog soon
目前 Windows app sdk 1.5 experimental 1 已经在nuget中提供了安装包，但是还没有提供更新日志，希望能尽快发布一份更新日志
Steps to reproduce the bug
None
Expected behavior
See describe
Screenshots

NuGet package version
Windows App SDK 1.4.3: 1.4.231115000
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 22H2 (22621, 2022 Update)
IDE
Visual Studio 2022
Additional context
None

Hi @Gaoyifei1011, sorry for the delay in getting the release notes out. You can check out the list of new and modified experimental APIs here:
https://learn.microsoft.com/windows/apps/windows-app-sdk/experimental-channel#version-15-experimental-150-experimental1


no recycler emag

About the PR

nobody likes emagged recyclers, it round removes tons of people and isn't fun
this PR removes the ability for recyclers to be emagged
Why / Balance

Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

this is a hard cope tbh
emag recycler is fun, dont be sending yourself down disposals randomly and you wont die to it

this is a hard cope tbh emag recycler is fun, dont be sending yourself down disposals randomly and you wont die to it

Indeed, major skill issue

No, and also I was told not to merge anything that doesn't pass all of the checks...


Fix for issue #1781.

Cost per user in chart label set to 0 when user has no pricing data.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


swig/python detected a memory leak of type 'ws2811_t *', no destructor found

Hi , I'm working on a CM4 + IO Board.
Model: Raspberry Pi Comput Model 4 Rev 1.1
Revision: d03141
The file 'lowlevel.py' in the examples folder is working fine, and also 'SK6812_lowlevel.py', but my own code using PixelStrip is not working. I also checked the strandtest.py file that uses the same class and it didn't work either.
The error I keep getting is:
Traceback (most recent call last):
File "/home/pi/rpi-ws281x-python/examples/SK6812_strandtest.py", line 89, in <module>
strip = PixelStrip(LED_COUNT, LED_PIN, LED_FREQ_HZ, LED_DMA, LED_INVERT, LED_BRIGHTNESS, LED_CHANNEL, LED_STRIP)
File "/usr/local/lib/python3.9/dist-packages/rpi_ws281x/rpi_ws281x.py", line 59, in __init__     super(PixelStrip, self).__init__(self._channel, num)
TypeError: object.__init__() takes exactly one argument (the instance to initialize)
swig/python detected a memory leak of type 'ws2811_t *', no destructor found.
There's a way of fixing that problem? it occurred after I had another problem regarding Hardware revision not supported but I fixed it using the method in https://github.com/jgarff/rpi_ws281x/issues/483 and then this problem started happening.

Are you running v5.0.0 from https://github.com/rpi-ws281x/rpi-ws281x-python/pull/92?
You can try installing it from https://test.pypi.org/project/rpi-ws281x/

Are you running v5.0.0 from #92?
You can try installing it from https://test.pypi.org/project/rpi-ws281x/

I was on 4.3.4 and updated it now to 5.0.0, It worked! Thank you!

That's good news. I suppose I should properly release v5.0.0 then!


Implement any agreed feature toggling

Chore
What we need to achieve and who for
Tasks

[ ] Agree what we can do
[ ] Implement it

Notes

Wont do this ... feature toggles can be included as standard as long as they're user facing and not centrally controlled.
Therefore just take on case by case basis as new features are built.


Current docker based build is broken

Building within the docker-image i get
/home/git/zimbra/zm-mailbox/build.xml:13: The following error occurred while executing this line:
/home/git/zimbra/zm-mailbox/build-common.xml:576: Directory does not exist: /root/.ivy2/cache

Should be at least reproduceable when running a Zimbra 10.0.5 build

What OS are you attempting to build for?  Ubuntu 18.04 and 20.04 builds work.  Someone had this with Ubuntu 16.04 which I no longer support.  See: https://github.com/ianw1974/zimbra-build-scripts/issues/15 if it is related to Ubuntu 16.04.
It works for currently for Alma, CentOS, Oracle, Rocky, Ubuntu 18.04 + 20.04 as this is how I build for these on my website.

Running on 20.04

Just running it now to check/verify, since this was working beginning of November when I built 10.0.5.

Built using podman without problems, and didn't even need to add this fix:
zcs-10.0.5_GA_0423.UBUNTU20_64.20231117085611.tgz

Are you sure you haven't edited my scripts or something that have caused this to fail, because it works perfectly fine with the current scripts in my repo and the Dockerfile.
Testing Docker so will update shortly if it's a docker thing.

Just built on my docker host as well:
zcs-10.0.5_GA_0423.UBUNTU20_64.20231117091323.tgz

I cannot replicate this problem, which means the script and Dockerfile I provide do work as intended.  If they have been changed/modified in anyway since downloading, then this could be the reason why yours isn't working.
I can add the fix, rather to my build script, so:
mkdir -p ~/.ivy2/cache

doing this way means it will create in the home directory of the user that is building Zimbra - be it root, or a normal user account.  Hard-coding to /root/.ivy2/cache would be wrong, since not everyone would build as root.  Obviously the Docker container does build as root which isn't so important since the container is destroyed afterwards and isn't going to affect a working system.  On a normal VPS or server that will remain running, then building as a normal user is preferred.
I would much prefer to find out what is causing the problem, rather than just introduce a workaround.  This shouldn't happen at all with either Ubuntu 18.04 or 20.04.  It does occur with Ubuntu 16.04 but then that is no longer supported so I didn't address that issue especially for that reason.
Even Ubuntu 18.04 has gone EOL now, although the script still supports it for the time being.  But that may change in the future.
If you can provide more info as to why this problem occurs for you - was something changed in the original Dockerfile, or what at your end is different that could cause this problem?  I for one, cannot replicate it anyway as I've just made two builds for 10.0.5 without any problems at all.

I keep it vanilla
name: docker

on:
  push:

env:
  IMAGE_FQDN: ghcr.io/kontextwork/zimbra-builder
  # actually that's the distro to build ON and FOR
  TARGET_DISTRO: ubuntu:20.04

jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout us
        uses: actions/checkout@v4
        with:
          path: builder
      - name: Checkout zimbra-build-scripts
        uses: actions/checkout@v4
        with:
          repository: ianw1974/zimbra-build-scripts
          ref: main
          path: zimbra-build-scripts
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v2
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v2
      - name: Login to GHCR
        uses: docker/login-action@v2
        with:
          registry: ghcr.io
          username: ${{ github.repository_owner }}
          password: ${{ github.token }}
      - name: Build builder
        uses: docker/build-push-action@v3
        with:
          context: zimbra-build-scripts
          platforms: linux/amd64
          push: true
          build-args: |
            # actually that's the distro to build ON and FOR
            RELEASE=${{ env.TARGET_DISTRO }}
          tags: |
            ${{ env.IMAGE_FQDN }}:latest

and then
    - run: |
          set -e
          cd /home/git/zimbra-build-scripts/
          ./zimbra-build-helper.sh --build-zimbra

depening on #60 i for sure simply can share the entire project

I expect this problem is due to using CI/CD.  You run ubuntu-latest, shouldn't this be specifying ubuntu:20.04?
You aren't using the Dockerfile at this point, since you are running the script inside a docker container running ubuntu-latest.  I think you should be using:
jobs:
  docker:
    runs-on: ubuntu:20.04

Alternatively you can do:
    - run: |
          set -e
          mkdir -p ~/.ivy2/cache
          cd /home/git/zimbra-build-scripts/
          ./zimbra-build-helper.sh --build-zimbra

where I added the mkdir command here for the directory you are missing.  But I expect it's due to using ubuntu-latest.

Actually, you can now look it up yourself:
https://github.com/KontextWork/zimbra-builder/blob/main/.github/workflows/build-release.yml#L12
so i run the steps within the containrer.
And yes i do hotfix it with https://github.com/KontextWork/zimbra-builder/blob/main/.github/workflows/build-release.yml#L15 anyway and do not rely on you merging this.
Building the builder without any modifications either https://github.com/KontextWork/zimbra-builder/blob/main/.github/workflows/build-docker.yml#L35
So well, it is not big issue for me, it works nevertheless. So if you cannot reproduce it, fair enough for me, close the issue and the PR, no hard feelings

The Dockerfile was intended for using docker/podman from the command line.  The issue seems to be with the way CI/CD is being ran here, and so something doesn't match.
If the host is running Ubuntu 20.04, then the script works fine (eg: building on a VM/VPS/physical server).  If we use Docker/Podman as explained in README.md in my repository, then the container runs Ubuntu 20.04 and builds fine.  When using the script as it was intended, be it running the script, or using the Dockerfile as intended with docker/podman then all is fine.
This is why I don't want to introduce something to the scripts that is based on the way CI/CD is being ran.  I believe if CI/CD was actually loading an Ubuntu 20.04 image, and then running the script, it would work fine.  It could also be whatever the source is of that Ubuntu image, is not the one as intended in my Dockerfile - so it could be a variation of Ubuntu 20.04 or something else hence the problems.
To run ./zimbra-build-helper.sh, you need to be running Ubuntu 20.04 and not ubuntu-latest as in your CI/CD.  Otherwise it is running on a platform not supported by Zimbra.

The CI runs the build inside the image that i build based on your docker file. There is no file and this is the normalized way to control the build env. I do not build on the ubuntu-latest baremetal.

That's strange, since the actual build process when all the java stuff runs, creates that directory anyway.  This is why I don't understand why it works for docker/podman with zero additions, and yet with the container image you built and use has problems.  Certainly sounds environment related.
I would have to debug it.  I generally use CI/CD on my own personal Gitlab instance with a Gitlab runner, so I can check/test it here easily enough to try and find out what the problem is.    But as mentioned, the build process should create those directories anyway, so I expect that something doesn't match right, potentially java-related or the packages related to ivy in a version mismatch for some reason.

i do not think it is worth the effort, this issue is not that impactful, IMHO

Yeah probably right, I just have a thing about finding out why to ensure it works as intended.  I could just add it to the script and just create it anyway irrespective or whether it's needed or not for everyone else.  But I kind of feel that's more a hack fix, than finding the correct solution even if it does take me more effort and time.  But that's just how I am :)

Do not merge my PR, since the reason behind it is unclear.
I can explain what it potentially is (it is related to the GH runner itself), but i'am neither interested in picking it apart for the GH runner (i only use gh actions for OS low level things and tend to not care too much about it).
So IMHO, close the issue, close the PR and if it does not come up again or bother us in a different way, i would duck it due to 'not worth the effort'.

Fixed here: b4821749dce48d68df22f37fbd16b8917ecead83


Testing for rs-kinfu

Hey, after months of research i didnt find any suitable solution for 3d reconstruction using realsense. Can u please test the rs-kinfu codes and provide me with suitable one

Hi @TheNemo05  I am not able to test rs-kinfu on my computer.  There is also unfortunately not much that can be added to the information that was provided in your earlier 3D reconstruction issues at https://github.com/IntelRealSense/librealsense/issues/11547 and https://github.com/IntelRealSense/librealsense/issues/11571 other than the new suggestions below.
Pyntcloud for the Python language is RealSense compatible and has an MIT Licence, meaning that you can freely modify and distribute it so long as you include the original author's copyright message in the code.
https://github.com/daavoo/pyntcloud
You could also use PCL instead of Open3D to register a series of pointclouds together.
https://pcl.readthedocs.io/en/latest/pairwise_incremental_registration.html

Hello @TheNemo05, from our experience best results can be achieved with a mixed point cloud / photogrammetry approach:

Don't take a video, but multiple pictures from still positions to avoid blurriness, rolling shutter (on D415), etc..
Enhance captured data with location and camera metadata
Combine multiple point of view, for example by adding smartphone pictures to your dataset
We suggest mounting the Realsense over a phone holder / tripod and use a remote control and take Realsense/Smartphone pictures at the same time
Use a sfm (structure from motion) software, for example Metashape, Reality Capture, Meshroom, etc.. for an offline 3d reconstruction. Metshape is able to import color/depth images as laser scanner. Use point cloud confidence filters to cleanup your point cloud and build a 3D mesh with textures.

Smartphone pictures can be used for a better high-resolution texture and to refine the point cloud confidence. They help with the reconstruction too and can better reconstruct black / reflective surfaces. With sfm softwares you can add GCP (Ground Control Points) over your scan area to achieve a solid accuracy.
We just released the open source RS Photo Converter that can help you with these steps. It works with an Android app (tested on Android 9 for now, but more devices will be tested soon) that greatly simplify this workflow and automatically optimize RS parameters (ex. Z Units, etc..) for accurate results.

Thanks so much @majinsoft for your highly detailed advice for @TheNemo05   :)

Thanks so much @majinsoft, a few question:

Has this ever been implemented before using the pcd software mentioned, if yes a few tutorials would be appreciated.
As i ll be using D455 underwater, in a housing placed on Rpi, The smartphone option is not possible.
I ve been using cloud compare for analysis.

Hello @TheNemo05,

The workflow described doesn't require programming, the reconstruction is done by a sfm software (commercial or open source)
Never tested underwater. If you only have a D455 and you can't add any other camera, you can't apply it.
On Linux systems you can record .bag files, use rs-convert to extract frames and manually add metadata for sfm softwares.
Point cloud confidence is created by the sfm software, when the same points are "seen" by multiple camera. In these softwares you can set a threshold to filter points with few confirmations.
Cloud Compare is a great software, can be used for further refinements. I can suggest you the use the Statistical Outlier Filter after the processing in the sfm software.
No, the main takeaway is that a D455 camera alone is not enough and you need at least an high-resolution camera, if you are looking for photorealistic 3D results. Have a look at sketchfab.com and search for "underwater metashape" to see some professional 3D reconstructions. You may find some tutorial on youtube about underwater photogrammetry.
The workflow I described combines photogrammetry and depth sensors for denser results. But remember that depth sensors (ex. D455) are someway still very noisy for accurate results. A professional, accurate laser-scanner can easily costs 60k for a reason.
To have and measure accuracy you need some "truth" positions (GCP) and distances (scale bars). Some used in the reconstruction and some as control data. Standard real-time algorithms (Kinect-fusion like) completely miss this part.

As i need to calculate surface area of underwater object, i was planning if depthmap could help ? any solution for this

From the points you have discussed. Here's what i ve understood.

i ve checked the suggested sfm softwares & decided to use meshroom as it is opensource.
after recording of .bag file the frames can be exported to .png and later uploaded to meshroom.
The meshroom will convert the frames into a 3D reconstructed surface.

I ve tried to keep it short.,

Hello @TheNemo05, what's the size of the object you want to measure and what accuracy are you looking for?

Accuracy is not a worry at the moment, right now we are considering a unspecified object

Hi @TheNemo05  Do you have an update about this case that you can provide, please?  Thanks!

Umm,

I don't think there is accurate open source solution for 3D reconstruction using Intel Cameras.
Intel needs to develop its own 3D reconstruction solution which will help to solve a lot of depth detection & pointcloud issues.
Commercial software are very expensive & are not beneficial for research purpose.

For scanning a scene in real-time and progressively building up an image with a RealSense camera, commercial 3D scanning software is the only alternative to the open-source rs-kinfu example unless ROS is used with SLAM navigation to build up a pointcloud and save the data to file.  Intel have a ROS1 tutorial for this at the link below.
https://github.com/IntelRealSense/realsense-ros/wiki/SLAM-with-D435i
This tutorial requires a RealSense camera that is equipped with an IMU component such as D435i, D435if or D455.

I am using a D455, i ll try the above procedure with ros & update on the issue.

@TheNemo05

There is a reason for the winding down of the Realsense division. If Intel Cameras were "accurate enough", there was no need to develop an advanced workflow involving commercial software, GCP, additional cameras, etc..

A 3D reconstruction solution alone won't solve these issues. For good results you need clean, valid, high resolution data. I think that Intel should remove the use case "3D Scanning" and the claim "Tightly integrated RGB and depth streams for better quality scanning." from the Realsense website, because this is "too much marketing" in my opinion and people complain because they had higher "quality" expectations.

Many commercial softwares are a standard in research and can benefit heavily discounted prices for accademic users. For an example look for "Metashape" on Google Scholar. There is an opensource project called Meshroom, but requires a lot of Computer Vision knowledge, I don't recommended it too much for now.

Thanks @majinsoft  I will just add that online tech press reports of RealSense 'winding down' were inaccurate, with Intel's official response posted on the librealsense front page at the link below.  Rather than a wind-down, some product categories such as lidar (L515) and face recognition (F455) were retired to focus completely on the 400 Series stereo depth camera range, which has continued.
https://github.com/IntelRealSense/librealsense#update-on-recent-changes-to-the-realsense-product-line

By going on the GitHub Insights / Contributors there is a pretty flat chart from December 2022 on this repository

So I was thinking there were only few people supporting and developing the current camera serie. Thank you for the clarification, I hope to see soon a great new camera!

Hey i am trying to use ROS package , this error was occured .

You are very welcome  :)
There is a large amount of new development work that goes on continually and is merged into to the development branch of librealense, which is 641 commits ahead of the master branch at the time of writing this.
https://github.com/IntelRealSense/librealsense/tree/development
Work on the next version of librealsense is done on the development branch, and when this branch is released it becomes the next master branch version.

@TheNemo05  That error may occur if the RealSense ROS2 wrapper is being used, as opensource_tracking.launch is a ROS1 wrapper launch file.

the package is now usable, but as i am using D455, it looses its orientation after capturing a particular sets of points.

@TheNemo05  If you are referring to the ROS SLAM guide, its documentation has a note about loss of orientation.

The built-in IMU can only keep track for a very short time.  Moving or turning too quickly will break the sequence of successful point cloud matches and will result in the system losing track.
It could happen that the system will recover immediately if stopped moving but if not, the longer the time passed since the break, the farther away it will drift from the correct position.  The odds for recovery get very slim, very quickly.  The parameters set in the launch file are most likely not ideal but this is a good starting point for calibrating.

At the link below, a RealSense user created an adaptation of the SLAM guide that added localization with RTABMAP and obtaining the relative position from a recorded pointcloud map.
https://shinkansan.github.io/2019-UGRP-DPoom/SLAM

If you are referring to launch/opensource_tracking_tk_online.launch from the link you provided. The launch file is not available else the website is broken

I tracked down a working link to the launch file.
https://github.com/shinkansan/2019-UGRP-DPoom/blob/a88e44b0a3eff80e93c12319af427b5cea05b798/SLAM/launch/opensource_tracking_tk_online.launch
In case the link cannot be accessed, I have posted the full contents of the launch file below.
<launch>
    <arg name="offline"          default="false"/>
    <include unless="$(arg offline)"
        file="$(find realsense2_camera)/launch/rs_camera.launch">
        <arg name="align_depth" value="true"/>
        <arg name="linear_accel_cov" value="1.0"/>
        <arg name="unite_imu_method" value="linear_interpolation"/>
    </include>

    <node pkg="imu_filter_madgwick" type="imu_filter_node" name="ImuFilter">
        <param name="_use_ma" type="bool" value="false" />
        <param name="_publish_tf" type="bool" value="false" />
        <param name="_world_frame" type="string" value="enu" />
        <remap from="/imu/data_raw" to="/camera/imu"/>
    </node>

    <include file="$(find rtabmap_ros)/launch/rtabmap.launch">
        <arg name="args" value="--delete_db_on_start --RGBD/LoopClosureReextractFeatures true
--Vis/MinInliers 10"/>
        <arg name="rgb_topic" value="/camera/color/image_raw"/>
        <arg name="depth_topic" value="/camera/aligned_depth_to_color/image_raw"/>
        <arg name="camera_info_topic" value="/camera/color/camera_info"/>
        <arg name="depth_camera_info_topic" value="/camera/depth/camera_info"/>
        <arg name="rtabmapviz" value="true"/>
        <arg name="rviz" value="false"/>
    </include>

    <include file="$(find robot_localization)/launch/ukf_template.launch"/>
    <param name="/ukf_se/frequency" value="300"/>
    <param name="/ukf_se/base_link_frame" value="camera_link"/>
    <param name="/ukf_se/odom0" value="rtabmap/odom"/>
    <rosparam param="/ukf_se/odom0_config">[true,true,true,
                                            true,true,true,
                                            true,true,true,
                                            true,true,true,
                                            true,true,true]
    </rosparam>
    <param name="/ukf_se/odom0_relative" value="true"/>
    <param name="/ukf_se/odom0_pose_rejection_threshold" value="10000000"/>
    <param name="/ukf_se/odom0_twist_rejection_threshold" value="10000000"/>

    <param name="/ukf_se/imu0" value="/imu/data"/>
    <rosparam param="/ukf_se/imu0_config">[false, false, false,
                                           true,  true,  true,
                                           true,  true,  true,
                                           true,  true,  true,
                                           true,  true,  true]
    </rosparam>
    <param name="/ukf_se/imu0_differential" value="true"/>
    <param name="/ukf_se/imu0_relative" value="false"/>
    <param name="/ukf_se/use_control" value="false"/>
    <!-- <param name="/ukf_se/odom0_config" value="{true,true,true,}"/> -->
</launch>

The original opensource_tracking.launch code & the one you provided are completely same.

It would be the same.  The new link that I provided is a replacement for the link that you quoted that does not work any more.

great this method is working. Just stuck at overlapping of points. any suggestions ?

Hello @TheNemo05
Can you post any screenshoot of the result you got?

Thanks very much again @majinsoft for your assistance to @TheNemo05   :)

surei ll be posting screenshots along with the generated pointcloud. a question to @MartyG-RealSense can we map depth pointcloud using Rtabmap & realsense.

Also from my observations,  whenever I try to map my pointcloud in rviz it looses its orientation. But in rtabmapviz it is comparatively stable,

Hi @TheNemo05  The Intel D435i SLAM guide and the DPoom adaptation of it from earlier in this discussion are the best available guides for ROS1 that I am aware of for mapping a depth poiintcloud with RealSense and rtabmap_ros.
As mentioned earlier at https://github.com/IntelRealSense/librealsense/issues/11753#issuecomment-1545596582 the D435i SLAM guide provides a warning about loss of IMU orientation.
If the opensource_tracking.launch ROS1 launch file is used then setting rviz to false and rtabmapviz to true has been reported by some RealSense ROS users to provide improved stabilty.
https://github.com/IntelRealSense/realsense-ros/blob/ros1-legacy/realsense2_camera/launch/opensource_tracking.launch#L23-L24
SLAM navigation in ROS2 can be more complicated than with ROS1.  RealSense ROS2 users who have attempted it typically use a combination of slam_toolbox and depthimage_to_laserscan, like in https://github.com/IntelRealSense/realsense-ros/issues/2387

Hello there,
i do have a solution for capturing pointclouds. but the thing is the pointcloud generated in Rtabmapviz is consists of noise. any filter you would suggest.

@TheNemo05  If your pointcloud is being generated with rtabmap then the advice about noise reduction at https://github.com/introlab/rtabmap/issues/414 may be helpful.

 This, with the water diffraction, can cause distortions that mess-up everything. You may need a special camera calibration for that environment.

Hi @TheNemo05  Do you have an update about this case that you can provide after the advice of @majinsoft above, please?  Thanks!

Hi @TheNemo05  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


Unwanted Space in Stack and HStack Components with Conditional Rendering

Description
I am encountering an issue with the Stack and HStack components in the React Native Ficus UI library where an unwanted space is left in the layout, even when a conditionally rendered component evaluates to false. This issue creates a visual offset in the UI, which is particularly noticeable when using the !!emoji condition.
Example Code
<HStack flexDirection="row" alignItems="center" spacing="md" {...rest}>
  {!!emoji && <Text fontSize="sm">{emoji}</Text>}
  <Text variant="h4" {...titleProps}>
    {children}
  </Text>
</HStack>

In this example, when !!emoji evaluates to false, there is an unexpected space before the second Text component, causing alignment issues. This problem seems to be a general issue with the way Stack and HStack handle conditional rendering.
Expected Behavior
No space should be left in the Stack or HStack layout when a conditionally rendered component evaluates to false. The layout should adjust accordingly without any visual offset.

Fixed on version 1.0.0


Merge release of v2.38.0-rc.0 back into main

Cut Prometheus v2.38.0-rc.0

Signed-off-by: Julius Volz<EMAIL_ADDRESS>
Include new docs PRs in the changelog

Signed-off-by: Julius Volz<EMAIL_ADDRESS>
Add "Scrape:" prefix to changelog entry

Co-authored-by: Levi Harrison<EMAIL_ADDRESS>Signed-off-by: Julius Volz<EMAIL_ADDRESS>Signed-off-by: Julius Volz<EMAIL_ADDRESS>Co-authored-by: Levi Harrison<EMAIL_ADDRESS>

The ui_build_and_release CI check is failing with:
Run ./scripts/ui_release.sh --check-package "v0.38.0-rc.0"
version of react-app is not the correct one
expected one: 0.38.0-rc.0
current one: 0.37.0
please use ./ui_release --bump-version 0.38.0-rc.0
Error: Process completed with exit code [1](https://github.com/prometheus/prometheus/runs/7795273062?check_suite_focus=true#step:5:1).

...but, since @Nexucis is on vacation and he told me I can ignore the new npm library release for now (since make ui-bump-version wasn't working for me earlier), I'm going to ignore that check for now here.


use daylight colours

Coverage remained the same at 86.792% when pulling 0efae8af281c6a10c3eaddf947d370eab85d76a7 on useDaylightColours into efa05088aef14e550e02105606599e6a46e924cb on master.


validating openapi document on controller generation (or client)

I am using operation.ExtensionData in the Controller.liquid template to generate some extra code.
(see https://github.com/RicoSuter/NSwag/issues/1436 for more details).
if an openapi operation contains the same extension twice, nswag will just set the value to the last entry.
for example when the document contains:
/action
get:
x-property: a
x-property: b
the liquid file will get the property value as "b".
when using https://editor.swagger.io/ to edit the file, it flags the duplicate as error.
but nswag doesn't throw an exception on this.
while debugging nswag I noticed that YamlDotNet already returns just the last entry, without doing any validations.
i'm not sure if this is valid in Yaml or not (maybe it's just invalid in openapi).
is there a plan to validate the openapi document?
if not, I will have to find another tool to do this.

I found the same issue in the YamlDotNet repository:
https://github.com/aaubry/YamlDotNet/issues/536


Crash during update with SD

I have this error when i start the update at 0:00 AM and the error disappear until 12:00 PM
ERRO[2018-10-28T00:27:08-04:00] could not complete guide updates: error when updating schedule for provider 2: error getting lastModifieds from schedules direct: status code was 400, expected 2XX-3XX. received content:
400 Bad Request

400 Bad Request

Thanks!

Some more details?  What version of telly, other config details, how you "start the update"?  Does this error just appear in the log, or is there a user-visible effect?

Well... the problem disappear when i restart telly but appear again later... i use 1.5 version the latest... and the update is start via the web ui


CLI platform improvements

Added Dir and Env modules
Fixed File.readUtf8 and File.readBytes
Expanded file.roc CLI example

Huh, I have no idea why that might be...do you have another distro you can try it on?
Also, if you're familiar with lldb, a backtrace would be helpful 🤔

You know what, I should be doing all of this on my macbook anyways because the guest of honor tomorrow is on a macbook. Goodnight, framey!

@JanCVanB cool - does that mean it's ready to merge? 😄

@rtfeldman should the CLI platform's main function allow any Errs in the Task? I see that examples/interactive/file.roc swallows all of its own Errs so that none are returned in the final return value, but should this be required?

I'm trying a simpler test app:
app "test"
    packages { pf: "../examples/interactive/cli-platform/main.roc" }
    imports [pf.File, pf.Path, pf.Task]
    provides [main] to pf

main =
    input <- File.readUtf8 (Path.fromStr "test_input.txt") |> Task.await
    File.writeUtf8 (Path.fromStr "test_output.txt") input

and it's failing to typecheck because it has Err potential, it seems. I can imagine this being intentional and good, but I just want to check.
jan@mackey roc % roc try-file-io/test.roc

── TYPE MISMATCH ─── try-file-io/../examples/interactive/cli-platform/main.roc ─

Something is off with the type annotation of the main required symbol:

2│      requires {} { main : Task {} [] * }
                             ^^^^^^^^^^^^

This #UserApp.main value is a:

    Task {} [FileReadErr Path.Path File.ReadErr,
    FileReadUtf8Err Path.Path [BadUtf8 Utf8ByteProblem Nat]*,
    FileWriteErr Path.Path File.WriteErr]a [Read [File]*,
    Write [File]*]b ?

But the type annotation on main says it should be:

    Task {} [] [Read [File]*, Write [File]*]b ?

── TYPE MISMATCH ─── try-file-io/../examples/interactive/cli-platform/main.roc ─

Something is off with the body of the mainForHost definition:

8│  mainForHost : Effect (Result {} []) as Fx
9│  mainForHost = InternalTask.toEffect main
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^

This InternalTask.toEffect call produces:

    Effect.Effect (Result {} [FileReadErr Path.Path File.ReadErr,
    FileReadUtf8Err Path.Path [BadUtf8 Utf8ByteProblem Nat]*,
    FileWriteErr Path.Path File.WriteErr]a) ?

But the type annotation on mainForHost says it should be:

    Fx ?

Tip: Type comparisons between an opaque type are only ever equal if
both types are the same opaque type. Did you mean to create an opaque
type by wrapping it? If I have an opaque type Age := U32 I can create
an instance of this opaque type by doing @Age 23.

────────────────────────────────────────────────────────────────────────────────

2 errors and 0 warnings found in 16 ms.

You can run the program anyway with roc run try-file-io/test.roc
jan@mackey roc %

I suppose that even if that's a mistake, we can handle it in a later PR.

should the CLI platform's main function allow any Errs in the Task?

I think it should be up to the application author to decide how to handle errors; if they want it to (for example) print an error message and then exit with a nonzero exit code, then they should do that rather than leaving that up to the platform!
That said, I could see an argument for it being something like Task I32 [] * instead of Task {} [] * so you explicitly return the error code (instead of having to Process.exit, which isn't implemented yet, but let's assume it exists for the sake of argument).

I see that examples/interactive/file.roc swallows all of its own Errs so that none are returned in the final return value, but should this be required?

Ordinarily they should be handled by reporting them to the user, but the example doesn't do that yet. I think that's what we really want: reporting them to the user in the application.