Updates for getInstalledRelatedApps

What's changed, or what was fixed?

Added info about OT in 73

Target Live Date: 2019-03-12

[ ] This has been reviewed and approved by (NAME)
[X] I have run npm test locally and all tests pass.
[X] I have added the appropriate type-something label.
[X] I've staged the site and manually verified that my content displays correctly.

@beverloo - FYI

:+1:

:+1:

This looks great, thanks! Just needs a link to the sign-up form, right?

:+1:

:+1:

Note that the Origin Trial is now enabled:
https://developers.chrome.com/origintrials/#/view_trial/855683929200394241

:tada: This has been pushed live to https://developers.google.com/web/


Getting error "protoc-gen-js: program not found or is not executable" when "npm run build:proto"

Description:
"npm run build:proto" makes error  "protoc-gen-js: program not found or is not executable" with protoc version 3.21.1.
After downgrade protoc version to 3.19.4, "npm run build:proto" makes no error. (refer https://github.com/protocolbuffers/protobuf-javascript/issues/105)
"npm run build" script in package.json need to be changed for work with the latest version of protocol or read.me should tell me the appropriate protocol version.
Why:
Can work with the latest version of protocol buffer.

Below is a guide to installing protoc-gen-js.
https://github.com/grpc/grpc-web#code-generator-plugin


[FR]: AWS EBS pre-processor

What would this feature improve or what problem would it solve?
Attaching and detaching of AWS EBS disks for AWS Kubernetes equivalent EKS
What is the feature you are proposing?
A google_cloud.py equivalent module with the preprocessor code to allow this to work.
Will also need to wait on the results of testing the chart in AWS
What alternatives have you considered?
No response

Minor comment that the attaching implementation should probably be in libcloudforensics and referenced from the new pre-processor in Turbinia.


Read count for the same sample varies in the qc_report

Describe the bug
When the same samples were used for two different runs, the number of reads before trimming and after trimming varies between the runs
Impact
The filtered read counts used for downstream alignment and the variant call will not be correct
To Reproduce
Ran the command to run mycosnp/nextflow and checked the qc_report.txt file.

Expected behavior
The qc_report for these samples from both the runs should be identical as the same reference was used.
Screenshots

qc_report_run1.txt
qc_report_run2.txt

Error is likely coming from lines
https://github.com/CDCgov/mycosnp-nf/tree/master/subworkflows/local/bwa-pre-process.nf
Lines 42/43:
DOWNSAMPLE_RATE(SEQKIT_PAIR.out.reads, reference[0], params.coverage)
SEQTK_SAMPLE(SEQKIT_PAIR.out.reads, DOWNSAMPLE_RATE.out.number_to_sample)
SEQTK_SAMPLE must join the downsample rate with the meta map id, it is currently mixing any downsample rate.


FEAT: Auto stash/pop for uncommitted changes to files

If files are changed but not committed, stash them (or otherwise preserve them) on branch change, and restore when switching back to that branch
I think this would be a killer addition to your excellent plugin!

It would be a nice opt-in setting to have, but by default I oppose having the extension perform any git operations.

+1


[SPARK-32381][CORE][SQL] Explore allowing parallel listing & non-location sensitive listing in core

What changes were proposed in this pull request?

This moves the parallel listing utilities from InMemoryFileIndex to Spark core so it can be reused by modules beside SQL.
Along the process this also did some cleanups/refactorings.
Why are the changes needed?

Currently the locality-aware parallel listing mechanism only applies to InMemoryFileIndex. By moving this to core, we can potentially reuse the same mechanism for other code paths as well.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Since this is mostly a refactoring, it relies on existing unit tests such as those for InMemoryFileIndex.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

cc @holdenk

Test build #127705 has started for PR 29471 at commit 5529047.

btw, we should better use Spark's PR template. But this is still in WIP, I suppose it will fill the template later.

Merged build finished. Test PASSed.

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

Test build #127705 has finished for PR 29471 at commit 5529047.

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

Merged build finished. Test PASSed.

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

Test build #127709 has started for PR 29471 at commit 6f5c7e5.

Merged build finished. Test PASSed.

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

Thanks @viirya - fixed the PR description.
@holdenk this is ready for review now. I removed the changes on WholeTextFileInputFormat to make this focusing on refactoring (i.e., moving the code from SQL to core). We can do follow-ups if later on we decide to swap the listing logic for Hadoop file input formats as well.
Other than that, a few fixes from the version I inherited from you:

fixed a NPE when BlockLocations is null - I think we should not convert FileStatus to LocatedFileStatus and initialize block locations with null.
changed ignoreDataLocality default to false, to match that in SQL
removed extra handling of FileNotFoundException which seems not necessary since the default behavior of FileSystem won't throw the exception, as mentioned offline.

Test build #127709 has finished for PR 29471 at commit 6f5c7e5.

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

Merged build finished. Test PASSed.

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

cc @steveloughran FYI from https://github.com/apache/spark/pull/29179

@HyukjinKwon @gengliangwang @viirya @zsxwing this PR is mostly a refactoring now. Could you take another look? Thanks!

Test build #127973 has started for PR 29471 at commit 86c2013.

Merged build finished. Test PASSed.

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

Test build #127973 has finished for PR 29471 at commit 86c2013.

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

Merged build finished. Test PASSed.

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

Test build #128051 has started for PR 29471 at commit bfa37cc.

Merged build finished. Test PASSed.

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

Test build #128051 has finished for PR 29471 at commit bfa37cc.

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

Merged build finished. Test PASSed.

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

BTW, wrote something up on listing.
https://github.com/steveloughran/engineering-proposals/blob/trunk/listing-performance.md
anywhere you do listStatus(path): List[FileStatus], switch to listStatusIterator, but, if the returned iterator is Closeable, make sure you close it after. Then I or a someone else will not only add the s3a and abfs speedups (alongside today's HDFS), I'll do the same for the local FS.

@sunchao Let's update PR title as well. This PR doesn't "expose" something but just moves the codes within the codebase. Also:

Along the process this also did some cleanups/refactorings.

Do you mind clarify the additional diffs this PR introduces? I took a cursory look. Seems there are some diffs above.

Also, let's make sure file s JIRA at https://github.com/apache/spark/pull/29471#discussion_r486626261 as @holdenk suggested. I agree with @viirya's comment there.

Thanks @HyukjinKwon and @holdenk for the review! I updated the PR title as well as description. Also created SPARK-32880 for the follow-up work.

Test build #128666 has started for PR 29471 at commit 2d8e64d.

Merged build finished. Test PASSed.

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

Test build #128666 has finished for PR 29471 at commit 2d8e64d.

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

Merged build finished. Test PASSed.

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

ping @HyukjinKwon @holdenk : anymore comments?

Looks like we've reached a lazy consesus here I'll merge this today :)

Ok I meant to merge this yesterday but I got distracted with the K8s stuff.

Merged to the current development branch :)

Thanks @holdenk for the merge, and all for the review comments!


SkyDNS2: service.ID is not valid DNS component

SkyDNS2 uses etcd paths to construct DNS names. Currently SkyDNS2 backend will use Service.ID in the path and this result in malformed DNS names. SkyDNS2 is fine registering them. However, it is hard to use them from DNS clients.
Here is an example of fully qualified DNS name for a docker container:
    d71d2242c6b1:mesos-da107fc7-8d16-4da3-bfb9-ee36680e8b7f:80.hello-world.igor.dev.

Clients will choke on ":" part.
With proposed change full DNS name will look like:
    d71d2242c6b1-mesos-da107fc7-8d16-4da3-bfb9-ee36680e8b7f-80.hello-world.igor.dev.

Full dig output:
[ec2-user@ip-10-214-18-116 ~]$ dig @<IP_ADDRESS> SRV hello-world.igor.dev

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.32.amzn1 <<>> @<IP_ADDRESS> SRV hello-world.igor.dev
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2817
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2

;; QUESTION SECTION:
;hello-world.igor.dev.		IN	SRV

;; ANSWER SECTION:
hello-world.igor.dev.	26	IN	SRV	10 50 31000 67bb0b671b66:mesos-b16baaab-5823-4ac0-95c3-5e38711fb3fb:80.hello-world.igor.dev.
hello-world.igor.dev.	26	IN	SRV	10 50 31000 d71d2242c6b1:mesos-da107fc7-8d16-4da3-bfb9-ee36680e8b7f:80.hello-world.igor.dev.

;; ADDITIONAL SECTION:
67bb0b671b66:mesos-b16baaab-5823-4ac0-95c3-5e38711fb3fb:80.hello-world.igor.dev. 29 IN A <IP_ADDRESS>
d71d2242c6b1:mesos-da107fc7-8d16-4da3-bfb9-ee36680e8b7f:80.hello-world.igor.dev. 26 IN A <IP_ADDRESS>

+1

Can you rebase so we can merge this in?

Closing in favor of #100


Added config option to change Terminal

Added config option to change Linux terminal from xterm to preferred one referred to "https://askubuntu.com/questions/46627/how-can-i-make-a-script-that-opens-terminal-windows-and-executes-commands-in-the" in how to use different terminals as reference.
I have only edited this 1 file, so if other files have similar cases (EX. gcc-make-run-view) i have no knowledge of it and i have not altered them to add this option.
Also done some preliminary testing to see if added config option works. (worked thus far in cases default "xterm" and "konsole")

cool~ :+1:
however not all terminal emulator use the same command line options :thinking:
i will modify it to terminal start command on top of this change

however not all terminal emulator use the same command line options 🤔

I  have not thus far encountered situation on Linux where command would not work because i use "X" terminal...
But i am new at Linux so there is that...


Add DOM module

Add DOM module that translates to document functions

Maybe it's better to have a DOM library that accesses the virtual DOM instead

https://github.com/bryanjos/elixirscript/pull/89

Decided against adding it here.


About SEO optimization for generating page source code

Describe the feature
After the page is run and generated, a window will be generated when the page source code is generated__ A section of code for NUXT__=, hoping to open a functional port to hide this section of code. This section of code can be configured in the vue renderers.js dependency package, and the specific configuration can be changed in the APP+=<script>${serializedSession}</script> line.
Additional information

[X] Would you be willing to help implement this feature?
[X] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Would you explain more about what you want? This section of code is required for Nuxt to successfully hydrate on the client side.


update custom visualization to use count endpoint, fixed the total co…

…unt of the returned object

Fixed a bug when the total attribute of the returned object causes internal server error (credit to @alipski )
Changed the sample endpoint of the main page to enrollment to better suit the needs for actual data
Used the recently-built /count endpoint to render custom visualization.
Added a global helper countRequest that returns a Promise for future reuse of the endpoint.

Codecov Report

Merging #91 into develop will not change coverage.
The diff coverage is 33.33%.

@@           Coverage Diff            @@
##           develop      #91   +/-   ##
========================================
  Coverage    80.14%   80.14%
========================================
  Files           37       37
  Lines        14681    14681
  Branches      1469     1469
========================================
  Hits         11766    11766
  Misses        2437     2437
  Partials       478      478

Impacted Files
Coverage Δ

ga4gh/server/frontend.py
65.33% <33.33%> (ø)
: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 4a22b1b...0226160. Read the comment docs.


Allow for separation of read and write indices/aliases

It'd be nice if there was a way to specify what index (alias) a model should write from separately from the one to read from. This would be very helpful when doing a bulk reindex so that I could have a model read from the old alias while reindexing but write to an alias that points to both the new and the old index to make sure that no writes are lost. Could this be supported?

+1 for this feature

:+1:

:+1:

@karmi do you know if this is on the roadmap?  Alternatively, can you suggest good workarounds for zero-downtime reindexing following a schema change?
For anyone else following this, this documentation describes the issue quite well: https://www.elastic.co/blog/changing-mapping-with-zero-downtime

@alexlitvak13 I'm starting to be more and more convinced that this actually doesn't belong to this gem at all. It's more about "index management" strategies, and the correct approach on the Elasticsearch level is to set up aliases (as Clinton Gormley explains in the article), and that is not tied to any model integration.
One solution would be to have some set of helper classes / DSL methods in the elasticsearch-extensions or elasticsearch-dsl gem, which would abstract all those acrobatics when setting up the aliases.

I gave it some more thinking, and now I'm 100% convinced that the right way how to approach would be:

Write an article for the Elastic blog about this topic, with concrete, working code examples how to achieve that
Mirror that article in the repository Wiki, so people can find it at Github as well
Put all the accompanying code into a Gist for easy access

This not only solves the issue itself, but educates users about possibilities and patterns when using the gem. This is actually very similar to the problem posed by #288, and in the ideal scenario we end up with a nice collection of "recipes" for using the libraries, instead of a huge amount of options for this and that particular problem.

@karmi thanks for your response.  I still think we have a need to allow separate read/write aliases.  Hopefully, I'm missing something and you can help point that out.
Scenario:
Say we have index N1 and alias A.  We reindex the data into N2 and repoint A.  Zero downtime, but the reindexing took time.  During that time, N1 was live and being updated via the Gem (by customer activity for example).  When we repoint A at N2, N2 is already outdated because it never saw those updates.
In addition to alias A, we can create alias AA to point at both N1 and N2.  If we then continue reading from A but write to AA, we keep both indexes up-to-date during the reindexing process.
At the moment, I don't see a way to configure the Gem to read from A but write to AA.

At the moment, I don't see a way to configure the Gem to read from A but write to AA.

Yeah, and that might be because you're too focused on something like Article.new(title: "test").save. And thus on something like search_index_name and index_index_name or read_index_name and write_index_name. (Notice how silly the names sound, and that's an inidication we aren't on a right track, in my eyes.)
But in reality, that code shouldn't happen in a reasonably sized application, if only because of executing the actual indexing HTTP request in background. So, in the case where we would have eg. a Sidekiq based indexer module (check out the example application templates), it could store the document into a completely unrelated index.

Minor note:

If we then continue reading from A but write to AA, we keep both indexes up-to-date during the reindexing process.

If I'm not missing something obvious, it's not entirely true -- you need to synchronize the indices anyhow (replaying the operations from a queue or something like that), if you want to end up with one, single index. But of course, you might point the A alias to multiple indices, and just keep on growing like that.

@karmi Has any work or more thought been put into this? It's a definite issue.

@karmi I went through this reindexing process using elasticsearch-rails recently. I wrote up a blog post about my process and how to keep things up to date during reindexing. I hope this helps others.
https://summera.github.io/infrastructure/2016/07/04/reindexing-elasticsearch.html

@summera Nice writeup!  We do something very similar but create the new index by pulling from the master datastore (relational db).  This has the added benefit of correcting any db-es sync issues that may have accumulated since the full reindex.
I'm still disappointed that we need to explicitly handle something that could (should?) have been accounted for at the gem layer and/or with elasticsearch aliases.

@alexlitvak13 Thanks!
Cool. How many records do you pull from your master datastore and how long does it take?

We maintain a couple indexes for a total of about 130M records.  It can take a full day to reindex and the bottleneck is entirely in Rails/ActiveRecord object serialization.  We've accelerated by running multiple chunks in parallel and can get a full reindex done in several hours.

Hi guys(@sgringwe, @karmi ) , surprisingly, there is so much on reindexing, and no one asks about working time-based indices? Maybe you can point me to the right direction?
it is general practice to have time-based indices like this:
docs-2017-06-05
docs-2017-06-04
docs-2017-06-03

and aliases:
docs_read => docs-*
docs_write => docs-2017-06-05

For now it seems like we cannot do this with the repository/model abstraction out of the box . What do you think is the right way here?

The requested feature could ease the straight forward usage of the library provided
We should have 2 repos, first with stubbed reads, second with stubbed out writes. And manage it in our code.
There is a right way i`m missing?


feat: add clusterIP override for headless svc and add ClusterDomain(cluster.local) override

👍

@AntiTyping any chance to review it?

@allthatjazzleo looking


#30 [5.x branch] Add a possibility to define the search query when adding visualizations

Added only to the 5.x branch.

Thank you for help me improve this plugin, I will look on this PR in the next days

I just merge the changes.
If you like this repository, please give a star
thanks

I will update the 5.6.0 version release and above in the next days, I will let you know


⚠ Bofrost.at has degraded performance

In 44ee0a7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1384 ms

Resolved: Bofrost.at performance has improved in a5fe2e8.


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[ ] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the starchain UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL: https://starnetwork.site/
JustList Name: Starchain
Link to the official homepage of the JustList manager:https://starnetwork.site/

Sorry, your issue will be closed as you did not submit your information in the correct format.


S3 Private Link

Describe the feature
SEP: seps/accepted/shared/s3-privatelink.md
Use Case
Required for GA
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

Determined that this customization is not needed once Endpoints 2.0 is supported by a SDK. Closing.


to_i64 takes very long to release-compile

Environment:

$ crystal -v
Crystal 0.35.1 [5999ae29b] (2020-06-19)

LLVM: 8.0.0
Default target: x86_64-unknown-linux-gnu

Compile option: time crystal build --release --no-debug

Observed:

gets.not_nil!.to_i

takes around 11 seconds to compile. But
gets.not_nil!.to_i64

takes around 33 seconds to compile. I think previously this was not happening.

Expected:

The latter (to_i64) should also compile similar time (to_i) to the former.

--stats option describes which part of compilation takes time:
[momonga@elma ~ x86_64]$ crystal eval --release --stats 'gets.not_nil!.to_i64'
Parse:                             00:00:00.000073166 (   0.25MB)
Semantic (top level):              00:00:00.692509122 (  45.54MB)
Semantic (new):                    00:00:00.002251068 (  45.54MB)
Semantic (type declarations):      00:00:00.055071657 (  45.54MB)
Semantic (abstract def check):     00:00:00.014118366 (  45.54MB)
Semantic (ivars initializers):     00:00:00.019376271 (  45.54MB)
Semantic (cvars initializers):     00:00:00.290701988 (  76.72MB)
Semantic (main):                   00:00:00.127858996 (  76.72MB)
Semantic (cleanup):                00:00:00.015213651 (  76.72MB)
Semantic (recursive struct check): 00:00:00.002209866 (  76.72MB)
Codegen (crystal):                 00:00:00.389143089 (  76.78MB)
Codegen (bc+obj):                  00:00:10.157504508 (  76.78MB)
Codegen (linking):                 00:00:00.077172808 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused
100
[momonga@elma ~ x86_64]$ crystal eval --release --stats 'gets.not_nil!.to_i'
Parse:                             00:00:00.000078505 (   0.25MB)
Semantic (top level):              00:00:00.664702044 (  45.54MB)
Semantic (new):                    00:00:00.002223303 (  45.54MB)
Semantic (type declarations):      00:00:00.053093154 (  45.54MB)
Semantic (abstract def check):     00:00:00.015838700 (  45.54MB)
Semantic (ivars initializers):     00:00:00.018744152 (  45.54MB)
Semantic (cvars initializers):     00:00:00.270165809 (  76.72MB)
Semantic (main):                   00:00:00.122609172 (  76.72MB)
Semantic (cleanup):                00:00:00.014394756 (  76.72MB)
Semantic (recursive struct check): 00:00:00.002078072 (  76.72MB)
Codegen (crystal):                 00:00:00.369789819 (  76.78MB)
Codegen (bc+obj):                  00:00:06.535286662 (  76.78MB)
Codegen (linking):                 00:00:00.075627428 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused
100
[momonga@elma ~ x86_64]$ crystal -v
Crystal 0.35.1 ()

LLVM: 10.0.0
Default target: x86_64-unknown-linux-gnu

I cannot reproduce this issue. The timings could be affected by a variety of factors. Make sure to clean the cache (~/.cache/crystal) before measuring.

I have this stats:
$ rm -rf ~/.cache/crystal && crystal eval --release --stats 'gets.not_nil!.to_i'
Parse:                             00:00:00.000033321 (   0.25MB)
Semantic (top level):              00:00:00.284489562 (  45.54MB)
Semantic (new):                    00:00:00.001281893 (  45.54MB)
Semantic (type declarations):      00:00:00.017540037 (  45.54MB)
Semantic (abstract def check):     00:00:00.005079098 (  45.54MB)
Semantic (ivars initializers):     00:00:00.005611963 (  45.54MB)
Semantic (cvars initializers):     00:00:00.092519776 (  76.72MB)
Semantic (main):                   00:00:00.038549817 (  76.72MB)
Semantic (cleanup):                00:00:00.004147029 (  76.72MB)
Semantic (recursive struct check): 00:00:00.000683779 (  76.72MB)
Codegen (crystal):                 00:00:00.381705459 (  76.78MB)
Codegen (bc+obj):                  00:00:11.464713278 (  76.78MB)
Codegen (linking):                 00:00:00.142163408 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused
1
$ rm -rf ~/.cache/crystal && crystal eval --release --stats 'gets.not_nil!.to_i64'
Parse:                             00:00:00.000023485 (   0.25MB)
Semantic (top level):              00:00:00.227755626 (  45.54MB)
Semantic (new):                    00:00:00.001445818 (  45.54MB)
Semantic (type declarations):      00:00:00.016583849 (  45.54MB)
Semantic (abstract def check):     00:00:00.004330381 (  45.54MB)
Semantic (ivars initializers):     00:00:00.005551524 (  45.54MB)
Semantic (cvars initializers):     00:00:00.095030432 (  76.72MB)
Semantic (main):                   00:00:00.042350488 (  76.72MB)
Semantic (cleanup):                00:00:00.004409815 (  76.72MB)
Semantic (recursive struct check): 00:00:00.000779521 (  76.72MB)
Codegen (crystal):                 00:00:00.373667444 (  76.78MB)
Codegen (bc+obj):                  00:00:33.554118575 (  76.78MB)
Codegen (linking):                 00:00:00.103622910 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused
1

The bc+obj time for @lugia-kun is more or less twice the time for to_i64 compared to to_i. The magnitude is similar for @cielavenir . Maybe your system is just slow, what's your CPU?

It can be poorly optimized for the officially distributed compiler: crystal-0.35.1-1-linux-x86_64.tar.gz
[momonga@elma ~ x86_64]$ rm -rf .cache/crystal && ./crystal-0.35.1-1/bin/crystal eval --release --stats 'gets.not_nil!.to_i64' </dev/null
Parse:                             00:00:00.000023906 (   0.25MB)
Semantic (top level):              00:00:00.213184473 (  45.54MB)
Semantic (new):                    00:00:00.001222640 (  45.54MB)
Semantic (type declarations):      00:00:00.016582822 (  45.54MB)
Semantic (abstract def check):     00:00:00.003959927 (  45.54MB)
Semantic (ivars initializers):     00:00:00.006416105 (  45.54MB)
Semantic (cvars initializers):     00:00:00.096440364 (  76.72MB)
Semantic (main):                   00:00:00.043317692 (  76.72MB)
Semantic (cleanup):                00:00:00.005042655 (  76.72MB)
Semantic (recursive struct check): 00:00:00.000791469 (  76.72MB)
Codegen (crystal):                 00:00:00.339030335 (  76.78MB)
Codegen (bc+obj):                  00:00:25.886882478 (  76.78MB)
Codegen (linking):                 00:00:00.081542084 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused
Unhandled exception: Nil assertion failed (NilAssertionError)
Error while trying to dump the backtrace: Arithmetic overflow (OverflowError)
[momonga@elma ~ x86_64]$ rm -rf .cache/crystal && ./crystal-0.35.1-1/bin/crystal eval --release --stats 'gets.not_nil!.to_i' </dev/null
Parse:                             00:00:00.000024877 (   0.25MB)
Semantic (top level):              00:00:00.201950076 (  45.54MB)
Semantic (new):                    00:00:00.001416522 (  45.54MB)
Semantic (type declarations):      00:00:00.016278520 (  45.54MB)
Semantic (abstract def check):     00:00:00.004202345 (  45.54MB)
Semantic (ivars initializers):     00:00:00.006098250 (  45.54MB)
Semantic (cvars initializers):     00:00:00.095066752 (  76.72MB)
Semantic (main):                   00:00:00.044211634 (  76.72MB)
Semantic (cleanup):                00:00:00.005056823 (  76.72MB)
Semantic (recursive struct check): 00:00:00.000728720 (  76.72MB)
Codegen (crystal):                 00:00:00.328815816 (  76.78MB)
Codegen (bc+obj):                  00:00:09.226124645 (  76.78MB)
Codegen (linking):                 00:00:00.087035636 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused
Unhandled exception: Nil assertion failed (NilAssertionError)
Error while trying to dump the backtrace: Arithmetic overflow (OverflowError)
[momonga@elma ~ x86_64]$ ./crystal-0.35.1-1/bin/crystal -v
Crystal 0.35.1 [5999ae29b] (2020-06-19)

LLVM: 8.0.0
Default target: x86_64-unknown-linux-gnu

I have investigated the built binaries. The compiler instantiated more methods and constants, and 3 symbols left not inlined:
$ diff -u <(nm to_i.o | cut -c 18-) <(nm to_i64.o | cut -c 18-)

--- /dev/fd/63	2020-08-04 20:27:22.994397405 +0900
+++ /dev/fd/62	2020-08-04 20:27:22.994397405 +0900
@@ -142,6 +142,7 @@
 t *String#inspect_char<Char, (UInt8 | Nil), String::Builder>:(String::Builder | Nil)
 t *String#starts_with?<Char>:Bool
 t *String#to_i:Int32
+t *String#to_u64_info<Int32, Bool, Bool, Bool, Bool, Bool, Bool>:String::ToU64Info
 t *String#underscore:String
 t *String::Builder#to_s:String
 t *String::Builder#write<Slice(UInt8)>:Nil
@@ -154,6 +155,7 @@
 t *String::interpolation<String, (Bool.class | Int32.class | Int64.class | Nil.class | Slice(UInt8).class | String.class | UInt16.class | UInt32.class | UInt64.class | UInt8.class), String>:String
 t *String::interpolation<String, (Bool.class | Int32.class | Int64.class | Slice(UInt8).class | String.class | UInt16.class | UInt32.class | UInt64.class | UInt8.class), String>:String
 t *String::interpolation<String, (String | Nil), String>:String
+t *String::interpolation<String, Int32>:String
 t *String::interpolation<String, Signal>:String
 t *String::interpolation<String, String, String, String>:String
 t *String::interpolation<String, String, String>:String
@@ -339,6 +341,7 @@
 b Signal::sigset
 b Signal::sigset:init
 b String::CHAR_TO_DIGIT
+b String::CHAR_TO_DIGIT62
 b String::CHAR_TO_DIGIT62:init
 b String::CHAR_TO_DIGIT:init
 b String::TYPE_ID:init

So, it can be normal to take more time to compile the to_i64 version.

It's funny because both methods rely on more or less the same underlying methods. So when you do to_i it actually calls something like to_i64.to_i. Just so you know :-)

On my machine it's 6s for to_i vs 9s for to_i64.
That said, the compiler is doing what it needs to do. Optimizing these things is mostly impossible. The time is spent in the bc+obj phase which is basically LLVM. We don't control what LLVM does there.
What we can do is generate more efficient LLVM code, and that will affect all things more or less equally. But if to_i64 needs to do more stuff compared to to_i, then it'll be slower to compile.

Another thing: if you compile an empty program, it seems String#to_i is already compiled by default. You can check this with this diff and then using bin/crystal:
diff --git a/src/string.cr b/src/string.cr
index e9b70b1e3..e9b1cf967 100644
--- a/src/string.cr
+++ b/src/string.cr
@@ -515,6 +515,7 @@ class String
       {% end %}
       info.value.to_{{method}}
     end
+    {% puts method %}
   end

   private def to_u64_info(base, whitespace, underscore, prefix, strict, leading_zero_is_octal, unsigned)

So when you write:
gets.not_nil!.to_i64

this is actually compiling to_i and to_i64. When you do:
gets.not_nil!.to_i

it's just compiling to_i.
In essence, we are comparing the time of doing nothing vs. the time of compiling to_i64. Of course there will be a significant difference!

I suggest to close this issue.

@j8r my CPU is Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz

The original issue was reported to me by @yuki2006 .
His CPU is Intel(R) Xeon(R) CPU @ 2.30GHz and crystal is:
Crystal 0.35.1 [5999ae29b] (2020-06-19)
LLVM: 8.0.0
Default target: x86_64-unknown-linux-gnu

stat:

to_i

Parse:                             00:00:00.000032629 (   0.25MB)
Semantic (top level):              00:00:00.291828662 (  44.45MB)
Semantic (new):                    00:00:00.001687647 (  44.45MB)
Semantic (type declarations):      00:00:00.021765071 (  44.45MB)
Semantic (abstract def check):     00:00:00.004676018 (  44.45MB)
Semantic (ivars initializers):     00:00:00.070696369 (  44.45MB)
Semantic (cvars initializers):     00:00:00.082283203 (  75.26MB)
Semantic (main):                   00:00:00.047436322 (  75.26MB)
Semantic (cleanup):                00:00:00.006083323 (  75.26MB)
Semantic (recursive struct check): 00:00:00.000825238 (  75.26MB)
Codegen (crystal):                 00:00:00.453231645 (  91.32MB)
Codegen (bc+obj):                  00:00:10.657633725 (  91.32MB)
Codegen (linking):                 00:00:00.083715307 (  91.32MB)
Codegen (bc+obj):
 - no previous .o files were reused

to_i64

Parse:                             00:00:00.000031968 (   0.25MB)
Semantic (top level):              00:00:00.294110739 (  44.45MB)
Semantic (new):                    00:00:00.001677529 (  44.45MB)
Semantic (type declarations):      00:00:00.021939479 (  44.45MB)
Semantic (abstract def check):     00:00:00.004600512 (  44.45MB)
Semantic (ivars initializers):     00:00:00.070553723 (  44.45MB)
Semantic (cvars initializers):     00:00:00.084688932 (  75.26MB)
Semantic (main):                   00:00:00.048132542 (  75.26MB)
Semantic (cleanup):                00:00:00.006218824 (  75.26MB)
Semantic (recursive struct check): 00:00:00.000831249 (  75.26MB)
Codegen (crystal):                 00:00:00.453403316 (  91.32MB)
Codegen (bc+obj):                  00:00:30.041210954 (  91.32MB)
Codegen (linking):                 00:00:00.078673201 (  91.32MB)
Codegen (bc+obj):
 - no previous .o files were reused

But the story does not finish. He has old disk snapshot, which has Crystal 0.33.0 [612825a53] (2020-02-14).

to_i

Parse:                             00:00:00.000023330 (   0.25MB)
Semantic (top level):              00:00:01.559084943 (  45.82MB)
Semantic (new):                    00:00:00.001092173 (  45.82MB)
Semantic (type declarations):      00:00:00.019076632 (  45.82MB)
Semantic (abstract def check):     00:00:00.004930274 (  45.82MB)
Semantic (ivars initializers):     00:00:00.005639646 (  45.82MB)
Semantic (cvars initializers):     00:00:00.131596631 (  61.10MB)
Semantic (main):                   00:00:00.042042104 (  77.10MB)
Semantic (cleanup):                00:00:00.005940622 (  77.10MB)
Semantic (recursive struct check): 00:00:00.000603709 (  77.10MB)
Codegen (crystal):                 00:00:00.412113621 (  77.16MB)
Codegen (bc+obj):                  00:00:08.906839599 (  77.16MB)
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/librt.so when searching for -lrt
/usr/bin/ld: skipping incompatible /usr/lib/libdl.so when searching for -ldl
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
Codegen (linking):                 00:00:02.185809997 (  77.16MB)
Codegen (bc+obj):
 - no previous .o files were reused

to_i64

Parse:                             00:00:00.000030702 (   0.25MB)
Semantic (top level):              00:00:00.276066559 (  45.99MB)
Semantic (new):                    00:00:00.001086318 (  45.99MB)
Semantic (type declarations):      00:00:00.019087112 (  45.99MB)
Semantic (abstract def check):     00:00:00.003854486 (  45.99MB)
Semantic (ivars initializers):     00:00:00.005610338 (  45.99MB)
Semantic (cvars initializers):     00:00:00.129068388 (  61.32MB)
Semantic (main):                   00:00:00.041045604 (  77.32MB)
Semantic (cleanup):                00:00:00.005255247 (  77.32MB)
Semantic (recursive struct check): 00:00:00.000704764 (  77.32MB)
Codegen (crystal):                 00:00:00.403326771 (  77.38MB)
Codegen (bc+obj):                  00:00:08.916179773 (  77.38MB)
/usr/bin/ld: skipping incompatible /usr/lib/libm.so when searching for -lm
/usr/bin/ld: skipping incompatible /usr/lib/libpthread.so when searching for -lpthread
/usr/bin/ld: skipping incompatible /usr/lib/librt.so when searching for -lrt
/usr/bin/ld: skipping incompatible /usr/lib/libdl.so when searching for -ldl
/usr/bin/ld: skipping incompatible /usr/lib/libc.so when searching for -lc
Codegen (linking):                 00:00:00.085900883 (  77.38MB)
Codegen (bc+obj):
 - no previous .o files were reused

You can see that in 0.33.0 bc+obj time does not change among to_i and to_i64. Could you explain?

FWIW Compile times for this (and other things I imagine) have been getting slower over time.
0.25.0 to 0.30.0
docker run -it crystallang/crystal:0.25.0 crystal eval --release --stats --progress 'gets.not_nil!.to_i64'
Parse:                             00:00:00.000035786 (   0.25MB)
Semantic (top level):              00:00:00.107019171 (  32.83MB)
Semantic (new):                    00:00:00.001337179 (  32.83MB)
Semantic (type declarations):      00:00:00.011553308 (  32.83MB)
Semantic (abstract def check):     00:00:00.001130660 (  32.83MB)
Semantic (ivars initializers):     00:00:00.000878728 (  32.83MB)
Semantic (cvars initializers):     00:00:00.088217028 (  58.45MB)
Semantic (main):                   00:00:00.019033643 (  58.45MB)
Semantic (cleanup):                00:00:00.002707035 (  58.45MB)
Semantic (recursive struct check): 00:00:00.000723621 (  58.45MB)
Codegen (crystal):                 00:00:00.105389099 (  74.45MB)
Codegen (bc+obj):                  00:00:03.349342286 (  74.45MB)
Codegen (linking):                 00:00:00.049109274 (  74.45MB)

Codegen (bc+obj):
 - no previous .o files were reused

0.30.0 to 0.34.0
docker run -it crystallang/crystal:0.34.0 crystal eval --release --stats --progress 'gets.not_nil!.to_i64'
Parse:                             00:00:00.000021629 (   0.25MB)
Semantic (top level):              00:00:00.164409635 (  45.54MB)
Semantic (new):                    00:00:00.001612343 (  45.54MB)
Semantic (type declarations):      00:00:00.014134920 (  45.54MB)
Semantic (abstract def check):     00:00:00.003582688 (  45.54MB)
Semantic (ivars initializers):     00:00:00.004992114 (  45.54MB)
Semantic (cvars initializers):     00:00:00.071873382 (  76.72MB)
Semantic (main):                   00:00:00.032214647 (  76.72MB)
Semantic (cleanup):                00:00:00.003966003 (  76.72MB)
Semantic (recursive struct check): 00:00:00.000790823 (  76.72MB)
Codegen (crystal):                 00:00:00.256457828 (  76.78MB)
Codegen (bc+obj):                  00:00:06.584822815 (  76.78MB)
Codegen (linking):                 00:00:00.062545097 (  76.78MB)

Codegen (bc+obj):
 - no previous .o files were reused

0.35.0
docker run -it crystallang/crystal:0.35.0 crystal eval --release --stats --progress 'gets.not_nil!.to_i64'
Parse:                             00:00:00.000022659 (   0.25MB)
Semantic (top level):              00:00:00.173586168 (  44.92MB)
Semantic (new):                    00:00:00.001235234 (  44.92MB)
Semantic (type declarations):      00:00:00.012906685 (  44.92MB)
Semantic (abstract def check):     00:00:00.003277784 (  44.92MB)
Semantic (ivars initializers):     00:00:00.004992250 (  44.92MB)
Semantic (cvars initializers):     00:00:00.069826035 (  75.89MB)
Semantic (main):                   00:00:00.032201420 (  75.89MB)
Semantic (cleanup):                00:00:00.003961809 (  75.89MB)
Semantic (recursive struct check): 00:00:00.000684551 (  75.89MB)
Codegen (crystal):                 00:00:00.284120471 (  91.95MB)
Codegen (bc+obj):                  00:00:22.515643632 (  91.95MB)
Codegen (linking):                 00:00:00.061558175 (  91.95MB)

Codegen (bc+obj):
 - no previous .o files were reused

FWIW Compile times for this (and other things I imagine) have been getting slower over time.

Of course, the runtime is getting bigger and bigger.
Again, guys, you are comparing to_i vs. to_i64 when in reality you are comparing void to to_i64. You are doing the wrong comparison.

Of course, the runtime is getting bigger and bigger.

I could see a few seconds here and there, but ~7x longer?  That's a bit extreme don't you think?

Try --single-module --emit llvm-ir with both versions, then compare the size of the generated .ll files and let me know the difference (I don't have time to try it right now).

Also, LLVM gets slower and slower every release. What LLVM is used in your case for 0.25.0 compared to 0.35.0?

Note that the time that goes up is mostly bc+obj: that's LLVM. The other stages take more or less the same time.
Again, it's an LLVM problem, not ours. There's nothing we can do about it. And people here are comparing the wrong stuff.

@asterite Let's treat it as an inquiry as to what could be done, if anything, to keep the compilation time down.

then compare the size of the generated .ll files

0.30.0 - 4.2M
0.31.0 - 5.7M
0.35.0 - 6.5M

As @lugia-kun firstly tested LLVM10, I compiled crystal from source-code and did the same benchmark:

sorry (bad keyboard...)

well, is it possible to upgrade LLVM in official distribution? with LLVM10, the issue is less affected.

@cielavenir I updated the test I ran as part of https://github.com/crystal-lang/crystal/issues/9654#issuecomment-668701731, which 0.36.0 and 0.36.1.  It seems 0.36.1 is quite a bit more performant than last few versions.  After upgrading to it I'd see if this is still a problem.

@yuki2006 said that the issue was gone. Thank you so much @Blacksmoke16


Binary installation on Ubuntu 24.04 doesn't seem to work

Environment

OS Version: Ubuntu 24.04
Source or binary build? Binary, Harmonic

Description
I used the installation steps described here. Step sudo apt-get install gz-harmonic gives E: Unable to locate package gz-harmonic.

Expected behavior: find and install gz-harmonic on Ubuntu 24.04
Actual behavior: Unable to locate package

Steps to reproduce

Fresh install of Ubuntu 24.04 and ROS2 Jazzy
Installation steps of gazebo from here
sudo apt install gz-harmonic

Ubuntu 24.04 just came out so we haven't built the binaries for it yet on packages.osrfoundation.org. It should be available in the coming few weeks. cc @j-rivero
If you're installing Jazzy, you can just install ros-jazzy-ros-gz and it will install Gazebo Harmonic from packages.ros.org via the gz vendor packages (documentation to come soon).

Does binaries coming soon? We are still waiting sir.

Does binaries coming soon? We are still waiting sir.

You can install the binaries from the ROS buildfarm as indicated above
sudo apt install ros-jazzy-ros-gz

https://community.gazebosim.org/t/gazebo-harmonic-packages-available-on-ubuntu-noble/2772

@mjcarroll Where is the ROS buildfarm?
I tried:
sudo sh -c 'echo "deb [arch=$(dpkg --print-architecture)] http://packages.ros.org/ros2/ubuntu $(lsb_release -cs) main" > /etc/apt/sources.list.d/ros2-latest.list'
curl -s https://raw.githubusercontent.com/ros/rosdistro/master/ros.asc | sudo apt-key add -
sudo apt-get update
sudo apt install ros-jazzy-ros-gz
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package ros-jazzy-ros-gz


Unceasing top, banish, and surround

Mod version: 1.5.0
Reported in the wanderer-feedback channel by Discord user Guy#7517
Describe the bug

Unceasing Top...  ceased?? I was in the middle of topdecking Top cards. Then I drew and played Ritual Dagger against the spear. It exhausted. The shield, btw, is banished atm. And Top just failed to draw me another card. Not sure if Wanderer bug or...

https://cdn.discordapp.com/attachments/638464764863053851/683380191648546871/SlayTheSpire.log
https://cdn.discordapp.com/attachments/638464764863053851/683380665655230472/SlayTheSpire_202002291827_1.log.zip

Unceasing Top not drawing is simply a symptom of the issue. The root cause is banish + continual attempts at applying the back attack buff to spire shield.
Whenever CardGroup::refreshHandLayout is called, if the player has the Surround power, the game attempts to apply the back attack power. In this case, since the shield is banished, the power cannot be applied. Seems like there's a loop of

fail to apply back attack because banished
refreshHandLayout
add apply back attack to action queue
The same call for refreshHandLayout will also trigger Unceasing Top. Unfortunately, top has a condition for checking if there's something in the action queue already before drawing a card. Since the ApplyPowerAction is always added before Top gets invoked, Top can never draw the card.

Steps to reproduce:

Get Unceasing Top relic
Enter Shield and Spear fight
Banish either creature
Target the other
Notice that the logs keep spouting "publish on post power apply"
Play all the cards in hand
Expect to draw a card. Do not actually draw a card.


[BUG] Space in knn_vector index type index.mapping property name prevents subsequent snapshot to be taken

Describe the bug
Discovered that second and all subsequent snapshots could not be taken for an index with type: knn_vector, presumably because of incorrect escaping.
OpenSearch complains with an error: org.opensearch.OpenSearchParseException: missing or invalid physical file name [_0_2011_my vector.hnswc if mapping property name contain space, e.g. my vector (my_vector would work fine).
Was able to replicate on OpenSearch 2.15 release on GCP and S3.
Full stack trace:
Jul 11 13:02:01 os-knn-test-1 opensearch[87]: [2024-07-11T13:02:01,536][WARN ][o.o.r.b.BlobStoreRepository] [os-knn-test-1] [opensearch-20240711t125920832386z-frequent/IjyRjHELRT-9SQYOUCq5nQ] failed to delete shard data for shard [knn-index][0] org.opensearch.OpenSearchParseException: missing or invalid physical file name [_0_2011_my vector.hnswc]|        at org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshot$FileInfo.fromXContent(BlobStoreIndexShardSnapshot.java:344) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshots.fromXContent(BlobStoreIndexShardSnapshots.java:298) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.ChecksumBlobStoreFormat.deserialize(ChecksumBlobStoreFormat.java:144) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.ChecksumBlobStoreFormat.read(ChecksumBlobStoreFormat.java:119) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.BlobStoreRepository.buildBlobStoreIndexShardSnapshots(BlobStoreRepository.java:3587) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.BlobStoreRepository$3.doRun(BlobStoreRepository.java:1388) [opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:941) [opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.15.0.jar:2.15.0]|        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]|        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]|        at java.base/java.lang.Thread.run(Thread.java:840) [?:?]|

Related component
Storage:Snapshots
To Reproduce

Configure object storage repository

Create index with knn_vector

curl -X PUT 'http://localhost:9200/knn-index/' -H 'Content-Type: application/json' -d '
{
  "settings": {
    "index": {
      "knn": true,
      "knn.algo_param.ef_search": 100
    }
  },
  "mappings": {
    "properties": {
      "my vector": {
        "type": "knn_vector",
        "dimension": 2
      }
    }
  }
}
'

Add some data

curl -X POST 'http://localhost:9200/_bulk' -H 'Content-Type: application/json' -d '{ "index": { "_index": "knn-index", "_id": "1" } }
   { "my vector": [1.5, 2.5], "price": 12.2 }
   { "index": { "_index": "knn-index", "_id": "2" } }
   { "my vector": [2.5, 3.5], "price": 7.1 }
   { "index": { "_index": "knn-index", "_id": "3" } }
   { "my vector": [3.5, 4.5], "price": 12.9 }
   { "index": { "_index": "knn-index", "_id": "4" } }
   { "my vector": [5.5, 6.5], "price": 1.2 }
   { "index": { "_index": "knn-index", "_id": "5" } }
   { "my vector": [4.5, 5.5], "price": 3.7 }\n
'

Search for data

curl -X GET 'http://localhost:9200/knn-index/_search' -H 'Content-Type: application/json' -d '{
  "size": 2,
  "query": {
    "knn": {
      "my vector": {
        "vector": [2, 3],
        "k": 2
      }
    }
  }
}'

Create first snapshot. Should be fine

curl -X GET 'http://localhost:9200/_snapshot/my-s3-repository/my-first-snapshot'

Create second snapshot. Failure.

curl -X GET 'http://localhost:9200/_snapshot/my-s3-repository/my-second-snapshot'

Observe error in logs, snapshot could not be taken with "missing or invalid physical file name" error:

Jul 11 13:02:01 os-knn-test-1 opensearch[87]: [2024-07-11T13:02:01,536][WARN ][o.o.r.b.BlobStoreRepository] [os-knn-test-1] [opensearch-20240711t125920832386z-frequent/IjyRjHELRT-9SQYOUCq5nQ] failed to delete shard data for shard [knn-index][0] org.opensearch.OpenSearchParseException: missing or invalid physical file name [_0_2011_my vector.hnswc]|        at org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshot$FileInfo.fromXContent(BlobStoreIndexShardSnapshot.java:344) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.index.snapshots.blobstore.BlobStoreIndexShardSnapshots.fromXContent(BlobStoreIndexShardSnapshots.java:298) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.ChecksumBlobStoreFormat.deserialize(ChecksumBlobStoreFormat.java:144) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.ChecksumBlobStoreFormat.read(ChecksumBlobStoreFormat.java:119) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.BlobStoreRepository.buildBlobStoreIndexShardSnapshots(BlobStoreRepository.java:3587) ~[opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.repositories.blobstore.BlobStoreRepository$3.doRun(BlobStoreRepository.java:1388) [opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:941) [opensearch-2.15.0.jar:2.15.0]|        at org.opensearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:52) [opensearch-2.15.0.jar:2.15.0]|        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]|        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]|        at java.base/java.lang.Thread.run(Thread.java:840) [?:?]|

Expected behavior
All subsequent snapshots should be taken regardless space in the mappings property name or space should be forbidden to use in the property names.
Additional Details
No response

@axeoman thanks for pointing. As a workaround could you avoid having space in the field name. Let us know if you are willing to contribute or we can take up this issue in future release

@vamshin thanks, yeah, this is exactly the recommendation we gave our customer.
Can't say we have free hands to contribute at the moment, so whoever ready to take this into work - please do :)

Hi @axeoman
I'm working on fixing the bug, and you can track it in here
Thank you

Catch All Triage - 1, 2, 3


Show color background for Labels related to the notification subject

I was not able to find working android TagView library with support for background color during #75 implementation. So I have to recheck later for this library.

This library looks promissing https://github.com/robertlevonyan/materialChipView

And this may be handy to find right color of the text in colored background https://stackoverflow.com/questions/1855884/determine-font-color-based-on-background-color

Layout to show chips in https://github.com/google/flexbox-layout

Labels viewing uses component from the material design library now, which supports colors, so it is used.


C++ize proxy mapper

This is part of the effort to C++ize gRPC core

This still needs to be done.

This was fixed in #21207.


Review need for "MUSICA name" for reactions

linking disparate parts of a model by a user supplied name is always problematic. Review options for eliminating the "MUSICA name" field. How can rates/rate constants for photolysis, emissions, and loss be provided without the need for a user supplied name?

This is a question for https://github.com/open-atmos/MechanismConfiguration/issues/10


Need your help

Hello JakeWharton ，I have been paying attention to you since 16 years, witnessing your growth and achievements. I'm proud of you. I've been doing Andro for more than three years now. With the increase of my work and age, I'm a little confused. Please give me some valuable opinions on the planning of future program career and future technology stack. Thank you.

With honest ,the futrue is hard to say especially for devs who lives in CN.
Which class you want to get, and what price you can pay.
It NOT courage words, but the simply reality.
If you're the average like me, you need pay your pain instead of your gain.
Every youth is a lonely boat on the sea, there are few islands, maybe only one.
So is now or never, never second.


Publish documentation

Whatever is currently on https://kgraphql.io/ is still in the repository but we need to find a new home, possibly GitHub pages.

GitHub pages sounds good to me :)


No prebuilt binaries available for arm64 windows

Windows release has published only x64 binaries.
I am not able to install and run this package on arm64 windows binaries and the corresponding binaries are missing. I am getting the following error for this package on arm64 windows.
[10:34:35 am] [ERROR] Error: No native build was found for platform=win32 arch=arm64 runtime=electron abi=125 uv=1 armv=8 libc=glibc node=20.16.0 electron=31.4.0
    loaded from: C:\karthick\highlight\node_modules\.pnpm\electron-app-universal-protocol-client<EMAIL_ADDRESS>
Is it possible to publish a release with binaries for arm64 windows?

Hi,
The issue has been resolved in 2.x.x: https://github.com/witcher112/electron-app-universal-protocol-client/releases/tag/v2.0.0 (although 2.0.1 is the first 2.x.x version due to CI failure)
Thanks for using the package :D!
Best regards,
Tomasz

Thank you very much!


Contradiction regarding GRS availability and durability.

https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy#redundancy-in-a-secondary-region is misleading/contradictory.
"For applications requiring high availability, you can choose to additionally copy the data in your storage account to a secondary region that is hundreds of miles away from the primary region. If your storage account is copied to a secondary region, then your data is durable even in the case of a complete regional outage or a disaster in which the primary region isn't recoverable."
Durability is not the same as availability.  GRS offers no more availability automatically than LRS.  You can failover over manually but this comes at a cost of potentially losing 15mins of data that wasn't replicated (vs RA-* replication.  The table at the bottom of the doc is pretty clear, but this could lead people to believe that GRS is a recommended availability strategy.

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

ID: f618f40d-ae53-5c3b-d8bf-0e80614f66d3
Version Independent ID: 93083407-8f1e-b3e2-6a62-e30be5e1fbcb
Content: Data redundancy - Azure Storage
Content Source: articles/storage/common/storage-redundancy.md
Service: storage
Sub-service: common
GitHub Login: @tamram
Microsoft Alias: tamram

Thanks for the feedback! We are currently investigating and will update you shortly.

@maggar I have assigned the issue to the content author to investigate further and update the document as appropriate.

@maggar - Thanks for your feedback! I've updated the article to use the two terms more precisely.
#please-close


Update OAV

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-node

https://github.com/Azure/azure-rest-api-specs/pull/4035

Can one of the admins verify this patch?


MSID: 91150 Version: 1 DOI: 10.1101/2<IP_ADDRESS>2827

MSID: 91150
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2827
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91150
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2827

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91150v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2827
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91150/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

error: xref element contains a junk character '□' which should be replaced or deleted.
error: fn element contains a junk character '□' which should be replaced or deleted


Go To Heading: In folder: Open switcher command crashes Obsidian

Obsidian 1.5.4
Plugin ver 0.2.2

When I execute the Go To Heading: In folder: Open switcher command, my entire vault just freezes and I have to force quit Obsidian. What is the intention of this command, and any idea why it crashes? I can use the other Go To Heading: Open switcher command without issue.

Ah, I looked at the code and I see, it opens a list of heading for the current folder. I use a monovault with over 10K notes in the same folder, probably >100K headings all together, so it just overwhelms the system to calculate all of it. I will avoid the command! Maybe there is a way to automatically break out of the function if it appears to be taking >10 seconds to display etc.


Cannot find module '@graphql-tools/delegate' or its corresponding type declarations.

Hi. I am getting following error when trying to build my project. I am using the latest middleware version 6.0.0.
➜  project git:(master) ✗  npm run build && npm run test

><EMAIL_ADDRESS>build /home/rok/project
> rm -rf dist && tsc

node_modules/graphql-middleware/dist/types.d.ts:2:31 - error TS2307: Cannot find module '@graphql-tools/delegate' or its corresponding type declarations.

2 import { StitchingInfo } from '@graphql-tools/delegate';
                                ~~~~~~~~~~~~~~~~~~~~~~~~~

Found 1 error.

Hey 👋,
Could you share a small reproduction repository so we can better help you with your issue?

I think i figure it out. Graphql-shield is still using an older version. If I use 4.0.0 of the middleware then it works.
Here is the reproduction repo if you want to try it out.
https://github.com/cernicc/temp

Thank you. I am closing this issue.

I also have this issue on my side, I think we have this problem because the module @graphql-tools/delegate is not a dependency of graphql-middleware. That's why we don't have any reference to it.

I also have this issue on my side, I think we have this problem because the module @graphql-tools/delegate is not a dependency of graphql-middleware. That's why we don't have any reference to it.

@cernicc https://github.com/maticzav/graphql-middleware/releases/tag/v6.0.1

@cernicc https://github.com/maticzav/graphql-middleware/releases/tag/v6.0.1


please tell users that they need a log file/dir instead of silently exiting.

pleeeeeeeeeeeeeeeeeeeeeeease.
i had to do
process.once( 'uncaughtException', function(err){
  console.log("process error",err);
  queue.shutdown( 1000, "", function(err2){
    console.log("queue.shutdown", err2);
    process.exit( 0 );
  });
});

to figure out that i needed a ./var dir after hours of not knowing why my process was exiting.

you should know that uncaughtException is not a safe gaurd in your code, since a potential for a swallowed error is always on with it.
I will try to explain this in the related section :) renaming the issue if you don't mind


QT Desktop wallet.  Show that some balance is not confirmed

At the wallet balance we want to show that not all coins are confirmed, so user should understand that amount is not finalized.
We can show the balance in green if there are any received and still not confirmed balance available.

Here are design proposal that we will have.
vek — 03/15/2021
I don't like how highlighting solve this issue, it's not clear for the user perspective whether why it will be in green or not, and what's the amount involved to have the amount in orange intuitively without getting a look to the account state (spendable - locked - unconfirmed) imo. I think the best would be to show confirmed balance and unconfirmed or dissociate both in the total and show only confirmed balance but i don't like it because it can be confusing to not see the balance in the top left updated when you receive some amount even if it's unconfirmed.
Maybe @privateidentity @MrT could give some through on this to get a better user experience on this issue
MrT — Yesterday at 2:18 PM
Bitpay for example just shows the total amount including unconfirmed.
It's only indicated on the tx itself by saying "incoming" instead of "received", but that's in the tx section of the screen.
Due to the difference in mw I agree that it would be nice to easily see the amount of unconfirmed funds tho, or to at least get a hint.
I think @vek 's suggestion of printing the unconfirmed Amount below just differently formated is nice (maybe with some "wait" icon infront instead of the unconfirmed text, and/or a bit smaller and maybe a bit grey-ish)
Only thing I'd change is to include the unconfirmed amount above instead of subtracting it so the "main" number still behaves as it does now.
This would (at least in my brain) mean "the big fat number is the total I "got" with the smaller bit below beeing 'still incoming' "
If we don't wan't to risk the confusion having 2 numbers there maybe a "waiting/syncing icon" below the total amount with some hover over text would suffice too to inform about unfinalized amounts. (behaving as a button taking u to the first unfinalized tx it finds if possible)
vek — Yesterday at 3:18 PM
good idea :thumbsup:

Verified, hence closing this ticket.


Make seed input a set of discrete input boxes

In both address gen flow and restore flow, when asking a user to input seed words, make the user enter each word in a different box. This way, missing/extra space user errors can be eliminated. the inputs can be trimmed, validated against word list, etc., and can be used inside the app to derive the actual seed phrase

Additionally the way it works now to enter the seed is very convenient and works for me as ma matter of fact I love the simplicity.
However people will lose their funds with this. As they will enter 2022 and think it's the password for the wallet. when it is actually the seed.

@CHMEX you mean that the current UI is good for you. but, you think that newbies might get confused and will lose money right?

Yes correct for myself its perfect just to enter the wif and it works.
However new people will think its a password to protect the wallet so they
use 2020 with is the seed.
Same we had in agama where 300k was deposited a famous address seed was
pretty weak.....
On Sat, Jul 31, 2021, 11:25 gcharang @.***> wrote:

@CHMEX https://github.com/CHMEX you mean that the current UI is good
for you. but, you think that newbies might get confused and will lose money
right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TokelPlatform/tokel_app/issues/113#issuecomment-890318544,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH7AI5SFEUO3KUNBR5WICNLT2O6QBANCNFSM5BESGEEQ
.

ah good point, didnt think about this kind of use case at all. Thx for mentioning it.


Support Windows LTSC

See https://techcommunity.microsoft.com/t5/windows-it-pro-blog/ltsc-what-is-it-and-when-should-it-be-used/ba-p/293181.
The summary is that the LTSC edition of Windows gets updated less often, and contains fewer components than a regular Windows install - generally meaning a faster install and lower resource usage (disk, CPU, etc).
For instance, you can obtain an install image for LTSC here: https://www.microsoft.com/en-gb/evalcenter/evaluate-windows-10-enterprise
Does quickemu support downloading a Windows edition like LTSC?

Anyone wanting to run Windows LTSC can do by downloading the ISO manually and creating a suitable Windows VM configuration 🙂
The LTSP can't be automated, as far as I am aware, so I won't be adding it Quickemu. If I'm wrong about that 👈 then pull requests are welcome!

Could you clarify what you mean by automated? I just installed Windows 10 using quickemu, and the installation process still included some manual steps.
As far as I know, the LTSC version is a regular old install ISO, so it should work the same as regular install ISOs. I can give it a try later if that sounds useful in terms of verifying.


[Bottom navigation bar] does not work with frames

If the demo apps cannot help and there is no issue for your problem, tell us about it
I want to simulate the same behaviour of the  Bottom Navigation with tabs and Frames inside it.
i build GrindLayout containers around frames, to show or hide the frames, but the frames are not changing.
Code at bottom
Which platform(s) does your issue occur on?

Android/ iOS (not checked)
emulator or device. Pixel 5

Please, provide the following version numbers that your issue occurs with:

CLI: 8.0.2
Cross-platform modules:  "~8.0.0"
Runtime(s) :8.0.0
Plugin(s):

"dependencies": {
    "@nativescript-community/ui-material-bottomnavigationbar": "^5.3.5",
    "@nativescript/core": "~8.0.0",
    "@nativescript/theme": "~3.0.1",
    "nativescript-vue": "~2.9.0",
    "vuex": "^3.6.2"
  },
  "devDependencies": {
    "@nativescript/android": "8.0.0",
    "@nativescript/webpack": "beta",
    "nativescript-vue-template-compiler": "~2.9.0",
    "sass": "^1.32.8"
  },

Please, tell us how to recreate the issue in as much detail as possible.
Just run the code.
Is there any code involved?
<template>
    <Page :actionBarHidden="true">
        <GridLayout rows="*, auto">
            <StackLayout class="page" row="0">
                <GridLayout v-if="currentTab === 0">
                    <Frame>
                        <Page backgroundColor="aqua">
                            <StackLayout>
                                <Label class="h1 text-center" text="1" horizontalAlignment="center" verticalAlignment="center" />
                            </StackLayout>
                        </Page>
                    </Frame>
                </GridLayout>
                <GridLayout v-else-if="currentTab === 1">
                    <Frame>
                       <Page backgroundColor="aqua">
                            <GridLayout>
                                <Label class="h1 text-center" text="2" horizontalAlignment="center" verticalAlignment="center" />
                            </GridLayout>
                        </Page>
                    </Frame>
                </GridLayout>
                <GridLayout v-else-if="currentTab === 2">
                    <Frame>
                        <Page backgroundColor="blue">
                            <GridLayout>
                                <Label class="h1 text-center" text="3" horizontalAlignment="center" verticalAlignment="center" />
                            </GridLayout>
                        </Page>
                    </Frame>
                </GridLayout>
            </StackLayout>
            <MDBottomNavigationBar
                ref="bottomBar"
                row="1"
                @tabSelected="onBottomNavigationTabSelected"
            >
                <MDBottomNavigationTab title="First" icon="res://ic_menu" />
                <MDBottomNavigationTab title="Second" icon="res://ic_menu" />
                <MDBottomNavigationTab title="Third" icon="res://ic_menu" />
            </MDBottomNavigationBar>
        </GridLayout>
    </Page>
</template>
<script>
export default {
    name: 'BottomNavigationBar',
    data() {
        return {
            currentTab: 0
        };
    },
    methods: {
        onBottomNavigationTabSelected(args) {
            this.currentTab = args.newIndex;
        },
        navigateHome() {
        }
    }
}
</script>

<style scoped lang="scss">
bottomnavigationbar {
    active-color: red;
    inactive-color: #000;
    background-color: #ddd;
}
</style>

@bunower this is not related to this plugin. You need to "debug" to see why it is not working. Mostly code intelligence related


publish a SLSA provenance in Rating

Investiate slsa provenance generation https://slsa.dev/provenance/v1

Tekton chains https://tekton.dev/blog/2023/04/19/getting-to-slsa-level-2-with-tekton-and-tekton-chains/
slsa framework verifier https://github.com/slsa-framework/slsa-verifier


check if user is connected to the right network

remove init logic from LoginGuard, and use a centralized module to watch network/account changes


Where is the custom related data saved?

N-Sidebar is a great feature and I really like this feature.
In addition, I want to know where the Custom Categories and Templates set in the N-Sidebar are stored.
Because I want to be able to use this custom data when changing devices or sharing it with friends.
Support for import and export is even better.

Hi, it's in the /custom_nodes/ComfyUI-N-Sidebar/app/settings.json

Hi, it's in the /custom_nodes/ComfyUI-N-Sidebar/app/settings.json

Thank you very much.
When I opened this JSON file, I took a look at it, but it was ignored because there was no data in it.
I think sb_templateNodeMap should have a separate JSON file to manage it.

single settings export implemented! 2c08bb7


drag & drop between container with overflow scroll or hidden

currently dragging element not visible
http://recordit.co/vKjUsWIqyo
possible solution is to create shadow element in body
(like you did here clonedNode  https://github.com/mattlewis92/angular-resizable-element/blob/master/src/resizable.directive.ts)

why you didn't use html5 d&d?

Ah damn, that's annoying, yeah I think you're right, the only way to get around this is by making the element absolute and removing it from the document flow as you drag the element. Would you like to make a pull request?
My reasoning for not using html5 drag and drop was because I needed support for snap grids which isn't possible with native drag and drop.

Is there a solution for this?

I saw the cloned node solution. the cloned node is added by parent node. In case, the item is dragged across components then the drag image is still hidden. How about if the ghost element is placed in body tag. Does it violate Angular application?

If it helps anyone, this is how I worked around this.

If it helps anyone, this is how I worked around this:
component.html
<li
    *ngFor="let drill of skill.drills"
    id="drill-{{drill.info.id}}"
    mwlDraggable
    [dropData]="{event: drill.event}"
    (click)="drillInfo(drillinfo,drill.info)"
    class="dropclass"
    (dragStart)="startDragging('drill-' + drill.info.id)"
    (dragEnd)="endDragging('drill-' + drill.info.id)"
    [style.background]="skill.color">
    {{ drill.title }}
</li>

component.ts
  startDragging(drillTag) {
    let drill = document.getElementById(drillTag);
    let domRect = drill.getBoundingClientRect();
    drill.style.position = 'fixed';
    drill.style.top = domRect.top + 'px';
    drill.style.left = domRect.left + 'px';
  }

  endDragging(drillTag) {
    let drill = document.getElementById(drillTag);
    drill.style.position = 'relative';
    drill.style.top = 'unset';
    drill.style.left = 'unset';
  }

While dragging, the position is fixed and aligned to its original viewport position.  After dragging, we make it relative again and unset the top and left properties.

Thanks for the pointer @justin-sleep, I've combined that with the solution suggested by @volser. I'm going to do a bit more testing with it before pushing it to npm to everyone. You can try it out in the meantime with:
npm i angular-draggable-droppable@alpha

Please let me know if there are any problems 😄


Update dynamic-data-masking.md

The serveradmin system role can't see unmasked data because it does not have enough permission to databases. So, I removed it.

@VanMSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Thanks, @MideMSFT!
Hi @Madhumitatripathy - Can you please review this PR? Thanks!

@MideMSFT Thanks for checking this and the change will be committed.

#sign-off

#sign-off


GQL generation should be remove from the directory and move to the dockerfile.

While using the multi-branch, it creates merge conflict in generated.go and it is not easy to solve.

cc: @gdsoumya

Can I get this assigned to me?


V1.xy - collect bonuses and videos from the widget (no move of the widget)

init the widget

adapt the code if it's a bonus or a video

wait part, if no button is green ( dependendly fot a screen shot of the times)

widget will auto sort the bonuses / videos in 2 sec interval

Author of the issue #16

daca trecerea de clickuri rail nation, a fost mai mare de ~ 6 sec
=> a fost cel putin un buton verde
altfel
=> nu a fost -> face capture la toate numerele(cu scroll), si intra in standby


[Spotify Player] ... Can we get "scrolling" option in menubar?

Extension
https://www.raycast.com/mattisssa/spotify-player
Description
The Spotify Menu Bar Player is awesome. I just wish it would scroll to show entire song title/artist if the length exceeds max text length.
Who will benefit from this feature?
Everyone!
Anything else?
No response

See https://github.com/raycast/extensions/issues/7450

Didn't see that -- thanks Erics118!

Thanks for bringing this up. It appears that this is a duplicate of issue https://github.com/raycast/extensions/issues/11292, so I'll mark it as such.


Support for @apply tailwind operator

Hi,
Is there is a way we can reuse styles as TailwindCss does with @apply key
More: https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply

see https://github.com/antfu/unocss#shortcuts

thats exactly not the same though. @apply allows you to include the utility classes inside your own class. Shortcuts in unocss are rather used for grouping and you cannot incude them in your css classes

Yes - @apply feature will be much appreciated. Aside from it being a useful feature, it will also enable to port existing tailwind classes

https://github.com/antfu/unocss#non-goal
It is possible you'd see apply in the next windi, it is a non goal of unocss.

Closing in favor of https://github.com/unocss/unocss/pull/630


i can't run it in my local machine

when i use npm run dev. it will have some error.

Have you installed the project dependencies using pnpm? You should first install dependencies using this command:
pnpm install

Afterwards, you can launch the development server using:
pnpm dev

I have not tried using NPM as package manager. It should possibly work as well if you installed dependencies via npm install.


Fix Backward Compatibility Issue in TopicPartitionOffset Constructor

Fix a backward compatibility issue in the TopicPartitionOffset constructor by reintroducing the original constructor and overloading it to separately accommodate the optional parameters.

Reintroduces the original constructor.
Adds an overloaded constructor for additional parameters.

Referring - https://github.com/confluentinc/confluent-kafka-dotnet/pull/2061 and fixes #2060

Testing
Integration tests

https://github.com/confluentinc/confluent-kafka-dotnet/pull/2027/files also introduced a breaking change to the IConsumer interface by adding TopicPartitionOffset PositionTopicPartitionOffset(TopicPartition partition); in 2.1

I opened this PR to replace the new interface method with an extension method on the IConsumer type; though it might be better to just keep the new method private.


Fix referenceable fields.

Description
Looks like the way to specify whether a field is referenceable differs a bit.
We have fields that have the property referenceable, e.g. acme:
{
  "token": {
    "referenceable": true,
    "type": "string"
  }
},

See https://github.com/fabianrbz/kong-plugins-docs-toolkit/blob/main/schemas/acme/3.2.x.json#L269-L274
Other fields, mostly of type array mark their elements as referenceable, e.g. request-transformer-advanced:
{
  "body": {
    "default": [

    ],
    "type": "array",
    "elements": {
      "type": "string",
      "referenceable": true
    },
    "description": "List of parameter `name:value` pairs. Rename the parameter name if and only if content-type is\none of the following: [`application/json`, `multipart/form-data`, `application/x-www-form-urlencoded`]; and parameter is present."
  }
},

See https://github.com/fabianrbz/kong-plugins-docs-toolkit/blob/main/schemas/request-transformer-advanced/3.2.x.json#L78-L88
In both cases, we should display them as referenceable.
Fixes https://github.com/Kong/docs.konghq.com/issues/5626
Testing instructions
Netlify link: https://deploy-preview-5638--kongdocs.netlify.app/hub/kong-inc/request-transformer-advanced/configuration/
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

@fabianrbz could you also adjust the table on this page to pick up the fields from the schema? https://deploy-preview-5638--kongdocs.netlify.app/gateway/latest/kong-enterprise/secrets-management/#referenceable-plugin-fields


ALL-2059 ADA required tatum api key fix. UX improvements of KMS. Para…

…meter to set env file by path

Task linked: ALL-2059 KMS command getaddress for ADA - Error


Update JobCard to Display Job Type

Description:
Modify the JobCard component to display the job type (e.g., Full-time, Contract). This enhancement provides users with more detailed job information at a glance.

Tasks:

[ ] Update the JobCard component to include job type
[ ] Ensure the job type is displayed correctly for all job listings
[ ] Test for visual consistency and responsiveness

Ideas for Elevation:

[ ] Add color-coded badges for different job types
[ ] Allow sorting and filtering by job type
[ ] Display additional icons for remote or on-site positions

This is already solved with #8


Took Out Described-By Attribute

The aria-described-by attributes make the page fail WAVE testing. This patch removes them.

+1 on this!

Dope! Thanks

@leggomuhgreggo Hey! I have used the latest with this pr merged in. I want to point out that the minified js version is still the old one. Then everything works without aria errors! :)


Not currently logged in

I have installed the plugin on LibreELEC 9.0.1 (Kodi 18.1). However navigating to any of the menu items within the plugin displays a generic error message on screen, and the message 'Not currently logged in' is output to the log file.
What is the recommended way to login to BitChute for the plugin?
The full log output from selecting 'Subscription Activity' from kodi.log is as follows:
2019-06-08 13:22:49.462 T:1497572208   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.ValueError'>
                                            Error Contents: Not currently logged in.
                                            Traceback (most recent call last):
                                              File "/storage/.kodi/addons/plugin.video.bitchute/main.py", line 686, in <module>
                                                router(sys.argv[2][1:])
                                              File "/storage/.kodi/addons/plugin.video.bitchute/main.py", line 666, in router
                                                listSubscriptionVideos(int(params.get('page', '1')))
                                              File "/storage/.kodi/addons/plugin.video.bitchute/main.py", line 505, in listSubscriptionVideos
                                                subs = fetchLoggedIn(baseUrl + "/subscriptions")
                                              File "/storage/.kodi/addons/plugin.video.bitchute/main.py", line 278, in fetchLoggedIn
                                                raise ValueError("Not currently logged in.")
                                            ValueError: Not currently logged in.
                                            -->End of Python script error report<--
2019-06-08 13:22:49.678 T:1505964912   ERROR: GetDirectory - Error getting plugin://plugin.video.bitchute/?action=subscriptionActivity
2019-06-08 13:22:49.680 T:1936954016   ERROR: CGUIMediaWindow::GetDirectory(plugin://plugin.video.bitchute/?action=subscriptionActivity) failed

Thanks!

At present the plugin only works if you login to a Bitchute account.  You can enter your Bitchute username and password in the settings for the plugin.  In Kodi you can right-click on the plugin and choose settings.
Hope that helps.

Okay so it turned out he settings menu was missing from the plugin because the resources directory was empty in the installation (under .kodi/addons/plugin.video.bitchute).
I had installed the plugin by cloning the git repo and then creating a ZIP file and then installing the ZIP file from the Kodi interface, so I'm not sure what caused the installation to fail copying in the resources.
Manually copying the files into the resources directory and restarting Kodi allowed me to input my login details and solved the issue.
Thanks!

I have the same error.  I installed it by downloading an archive from GitHub, uploading it to one of my LibreELEC boxes, and selecting "install from zipfile."  I checked under ~/.kodi/addons/plugin.video.bitchute and found everything:
.kodi/addons/plugin.video.bitchute/:
.           .gitignore  Readme.md   icon.png    resources
..          LICENSE     addon.xml   main.py

.kodi/addons/plugin.video.bitchute/resources:
.             ..            language      settings.xml

.kodi/addons/plugin.video.bitchute/resources/language:
.        ..       English  Hebrew

.kodi/addons/plugin.video.bitchute/resources/language/English:
.           ..          strings.po

.kodi/addons/plugin.video.bitchute/resources/language/Hebrew:
.           ..          strings.po

I've set my username and password in the plugin's settings.  I just logged into BitChute on my computer to make sure the account still worked.  It still won't log in, though, and produces the same error as above.


Direct journal transforms in v2 migration

This PR moves to directly deserializing the old journal rows and manually constructing the new rows. We can take this simpler path as we know that akka proto serialization was used before and after, so we don't need the complexity introduced by the general akka serde.

closing the PR. However the branch is not deleted.


Add "dump all" button to empty all folders

This would be helpful for sharing graphs to be pasted into folders.
Not sure where this button would go. It would make sense to place it next to the "delete all" button (an action on the whole graph), but there's not much space there.

This is not so useful now that graphs with folders can be pasted into a graph.


Introduce Metadata to the config.yaml

Metadata is meant to store specific information about what type of system this configuration should apply to, namely GPU information. This is a better and more maintainable heuristic for system profiles as we scale the amount of systems we want to automatically apply configurations to

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Functional tests have been added, if necessary.
[ ] E2E Workflow tests have been added, if necessary.

force merging due to known issue in CI: https://github.com/instructlab/instructlab/issues/2753. Overriding because we need this in 0.21.2

@Mergifyio backport release-v0.21