Docs - convert java snippets to c#

Requires: https://github.com/apache/lucenenet/issues/283

Once we have an idea about how this works https://github.com/apache/lucenenet/issues/283 we can start the snippet conversion. This could be broken down into smaller tasks and listed as up for grabs.

~15 hrs

This issue no longer depends on #283, since that issue was addressed by #396. So this issue is no longer blocked.
Here is a list of all of the documentation files that will require a review to update code examples. Note that links are a different issue that is being worked on in #300. So in this issue, we should focus on:

Updating Java code examples to C#. Make sure the examples will compile the way they are written after the conversion.
Updating references to Java technologies (types, JVM, class path, etc) to their .NET equivalents. Some of this will require some research. Note that some things like links over to Java-related wikipedia articles are probably best to leave alone and other things like types that exist in Java but don't in .NET and are still required to make the flow of the docs work might need to be clarified for the average .NET developer.
Make sure the formatting of the Markdown document is similar to how it was in Lucene - that is, make sure the numbered and unordered lists come up correctly, tables are legible, etc.
Look out for issues with usability and open issues about them if any are found.

NOTE: The main documents to focus on here are named overview.md and package.md. The rest could probably just use a cursory review.

[ ] src\dotnet\Lucene.Net.Replicator.AspNetCore\examples.md
[ ] src\dotnet\tools\lucene-cli\docs\analysis\index.md
[ ] src\dotnet\tools\lucene-cli\docs\analysis\kuromoji-build-dictionary.md
[ ] src\dotnet\tools\lucene-cli\docs\analysis\stempel-compile-stems.md
[ ] src\dotnet\tools\lucene-cli\docs\analysis\stempel-patch-stems.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\extract-reuters.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\extract-wikipedia.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\find-quality-queries.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\index.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\run.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\run-trec-eval.md
[ ] src\dotnet\tools\lucene-cli\docs\benchmark\sample.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\associations-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\distance-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\expression-aggregation-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\index.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\index-files.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\multi-category-lists-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\range-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\search-files.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\simple-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\demo\simple-sorted-set-facets.md
[ ] src\dotnet\tools\lucene-cli\docs\index.md
[ ] src\dotnet\tools\lucene-cli\docs\index\check.md
[ ] src\dotnet\tools\lucene-cli\docs\index\copy-segments.md
[ ] src\dotnet\tools\lucene-cli\docs\index\delete-segments.md
[ ] src\dotnet\tools\lucene-cli\docs\index\extract-cfs.md
[ ] src\dotnet\tools\lucene-cli\docs\index\fix.md
[ ] src\dotnet\tools\lucene-cli\docs\index\index.md
[ ] src\dotnet\tools\lucene-cli\docs\index\list-cfs.md
[ ] src\dotnet\tools\lucene-cli\docs\index\list-high-freq-terms.md
[ ] src\dotnet\tools\lucene-cli\docs\index\list-segments.md
[ ] src\dotnet\tools\lucene-cli\docs\index\list-taxonomy-stats.md
[ ] src\dotnet\tools\lucene-cli\docs\index\list-term-info.md
[ ] src\dotnet\tools\lucene-cli\docs\index\merge.md
[ ] src\dotnet\tools\lucene-cli\docs\index\split.md
[ ] src\dotnet\tools\lucene-cli\docs\index\upgrade.md
[ ] src\dotnet\tools\lucene-cli\docs\lock\index.md
[ ] src\dotnet\tools\lucene-cli\docs\lock\stress-test.md
[ ] src\dotnet\tools\lucene-cli\docs\lock\verify-server.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Ar\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Bg\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Br\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Ca\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\CharFilter\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Cjk\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Ckb\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Cn\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\CommonGrams\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Compound\Hyphenation\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Compound\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Core\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Cz\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Da\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\De\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\El\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\En\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Es\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Eu\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Fa\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Fi\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Fr\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Ga\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Gl\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Hi\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Hu\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Hunspell\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Hy\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Id\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\In\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\It\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Lv\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Miscellaneous\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\NGram\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Nl\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\No\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Path\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Pattern\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Payloads\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Position\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Pt\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Query\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Reverse\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Ro\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Ru\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Shingle\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Sinks\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Snowball\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Standard\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Standard\Std31\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Standard\Std34\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Standard\Std36\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Standard\Std40\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Sv\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Synonym\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Th\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Tr\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Util\package.md
[ ] src\Lucene.Net.Analysis.Common\Analysis\Wikipedia\package.md
[ ] src\Lucene.Net.Analysis.Common\Collation\package.md
[ ] src\Lucene.Net.Analysis.Common\Collation\TokenAttributes\package.md
[x] src\Lucene.Net.Analysis.Common\overview.md
[ ] src\Lucene.Net.Analysis.Common\Tartarus\Snowball\Ext\package.md
[ ] src\Lucene.Net.Analysis.Common\Tartarus\Snowball\package.md
[ ] src\Lucene.Net.Analysis.ICU\Analysis\Icu\package.md
[ ] src\Lucene.Net.Analysis.ICU\Analysis\Icu\Segmentation\package.md
[ ] src\Lucene.Net.Analysis.ICU\Analysis\Icu\TokenAttributes\package.md
[ ] src\Lucene.Net.Analysis.ICU\Collation\package.md
[ ] src\Lucene.Net.Analysis.ICU\Collation\TokenAttributes\package.md
[ ] src\Lucene.Net.Analysis.ICU\overview.md
[ ] src\Lucene.Net.Analysis.Kuromoji\Dict\package.md
[ ] src\Lucene.Net.Analysis.Kuromoji\overview.md
[ ] src\Lucene.Net.Analysis.Kuromoji\package.md
[ ] src\Lucene.Net.Analysis.Kuromoji\TokenAttributes\package.md
[ ] src\Lucene.Net.Analysis.Kuromoji\Util\package.md
[ ] src\Lucene.Net.Analysis.Morfologik\overview.md
[ ] src\Lucene.Net.Analysis.Morfologik\package.md
[ ] src\Lucene.Net.Analysis.OpenNLP\overview.md
[ ] src\Lucene.Net.Analysis.Phonetic\overview.md
[ ] src\Lucene.Net.Analysis.Phonetic\package.md
[ ] src\Lucene.Net.Analysis.SmartCn\Hhmm\package.md
[ ] src\Lucene.Net.Analysis.SmartCn\overview.md
[ ] src\Lucene.Net.Analysis.SmartCn\package.md
[ ] src\Lucene.Net.Analysis.Stempel\Egothor.Stemmer\package.md
[ ] src\Lucene.Net.Analysis.Stempel\overview.md
[ ] src\Lucene.Net.Analysis.Stempel\Pl\package.md
[ ] src\Lucene.Net.Analysis.Stempel\Stempel\package.md
[ ] src\Lucene.Net.Benchmark\ByTask\Feeds\package.md
[ ] src\Lucene.Net.Benchmark\ByTask\package.md
[ ] src\Lucene.Net.Benchmark\ByTask\Programmatic\package.md
[ ] src\Lucene.Net.Benchmark\ByTask\Stats\package.md
[ ] src\Lucene.Net.Benchmark\ByTask\Tasks\package.md
[ ] src\Lucene.Net.Benchmark\ByTask\Utils\package.md
[ ] src\Lucene.Net.Benchmark\overview.md
[ ] src\Lucene.Net.Benchmark\package.md
[ ] src\Lucene.Net.Benchmark\Quality\package.md
[ ] src\Lucene.Net.Benchmark\Quality\Trec\package.md
[ ] src\Lucene.Net.Benchmark\Quality\Utils\package.md
[ ] src\Lucene.Net.Benchmark\Utils\package.md
[ ] src\Lucene.Net.Classification\overview.md
[ ] src\Lucene.Net.Classification\package.md
[ ] src\Lucene.Net.Classification\Utils\package.md
[ ] src\Lucene.Net.Codecs\Appending\package.md
[ ] src\Lucene.Net.Codecs\BlockTerms\package.md
[ ] src\Lucene.Net.Codecs\Bloom\package.md
[ ] src\Lucene.Net.Codecs\DiskDV\package.md
[ ] src\Lucene.Net.Codecs\IntBlock\package.md
[ ] src\Lucene.Net.Codecs\Memory\package.md
[ ] src\Lucene.Net.Codecs\overview.md
[ ] src\Lucene.Net.Codecs\Pulsing\package.md
[ ] src\Lucene.Net.Codecs\Sep\package.md
[ ] src\Lucene.Net.Codecs\SimpleText\package.md
[ ] src\Lucene.Net.Demo\Facet\package.md
[ ] src\Lucene.Net.Demo\overview.md
[ ] src\Lucene.Net.Demo\package.md
[ ] src\Lucene.Net.Expressions\JS\package.md
[ ] src\Lucene.Net.Expressions\overview.md
[ ] src\Lucene.Net.Expressions\package.md
[ ] src\Lucene.Net.Facet\overview.md
[ ] src\Lucene.Net.Facet\package.md
[ ] src\Lucene.Net.Facet\Range\package.md
[ ] src\Lucene.Net.Facet\SortedSet\package.md
[ ] src\Lucene.Net.Facet\Taxonomy\Directory\package.md
[ ] src\Lucene.Net.Facet\Taxonomy\package.md
[ ] src\Lucene.Net.Facet\Taxonomy\WriterCache\package.md
[ ] src\Lucene.Net.Grouping\Function\package.md
[ ] src\Lucene.Net.Grouping\overview.md
[ ] src\Lucene.Net.Grouping\package.md
[ ] src\Lucene.Net.Grouping\Term\package.md
[ ] src\Lucene.Net.Highlighter\Highlight\package.md
[ ] src\Lucene.Net.Highlighter\overview.md
[ ] src\Lucene.Net.Highlighter\PostingsHighlight\package.md
[ ] src\Lucene.Net.Highlighter\VectorHighlight\package.md
[ ] src\Lucene.Net.Join\overview.md
[ ] src\Lucene.Net.Join\package.md
[ ] src\Lucene.Net.Memory\overview.md
[ ] src\Lucene.Net.Memory\package.md
[ ] src\Lucene.Net.Misc\Document\package.md
[ ] src\Lucene.Net.Misc\Index\package.md
[ ] src\Lucene.Net.Misc\Index\Sorter\package.md
[ ] src\Lucene.Net.Misc\Misc\package.md
[ ] src\Lucene.Net.Misc\overview.md
[ ] src\Lucene.Net.Misc\Store\package.md
[ ] src\Lucene.Net.Misc\Util\Fst\package.md
[ ] src\Lucene.Net.Queries\Function\DocValues\package.md
[ ] src\Lucene.Net.Queries\Function\package.md
[ ] src\Lucene.Net.Queries\Function\ValueSources\package.md
[ ] src\Lucene.Net.Queries\Mlt\package.md
[ ] src\Lucene.Net.Queries\overview.md
[ ] src\Lucene.Net.Queries\package.md
[ ] src\Lucene.Net.QueryParser\Analyzing\package.md
[ ] src\Lucene.Net.QueryParser\Classic\package.md
[ ] src\Lucene.Net.QueryParser\ComplexPhrase\package.md
[ ] src\Lucene.Net.QueryParser\Ext\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Builders\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Config\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Messages\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Nodes\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Parser\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Processors\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Core\Util\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Messages\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Precedence\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Precedence\Processors\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Standard\Builders\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Standard\Config\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Standard\Nodes\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Standard\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Standard\Parser\package.md
[ ] src\Lucene.Net.QueryParser\Flexible\Standard\Processors\package.md
[ ] src\Lucene.Net.QueryParser\overview.md
[ ] src\Lucene.Net.QueryParser\Simple\package.md
[ ] src\Lucene.Net.QueryParser\Surround\Parser\package.md
[ ] src\Lucene.Net.QueryParser\Surround\Query\package.md
[ ] src\Lucene.Net.QueryParser\Xml\Builders\package.md
[ ] src\Lucene.Net.QueryParser\Xml\package.md
[ ] src\Lucene.Net.Replicator\Http\package.md
[ ] src\Lucene.Net.Replicator\Http\replicator.md
[ ] src\Lucene.Net.Replicator\overview.md
[ ] src\Lucene.Net.Replicator\package.md
[ ] src\Lucene.Net.Sandbox\overview.md
[ ] src\Lucene.Net.Sandbox\Queries\package.md
[ ] src\Lucene.Net.Spatial\overview.md
[ ] src\Lucene.Net.Spatial\package.md
[ ] src\Lucene.Net.Spatial\Prefix\package.md
[ ] src\Lucene.Net.Spatial\Prefix\Tree\package.md
[ ] src\Lucene.Net.Spatial\Query\package.md
[ ] src\Lucene.Net.Spatial\Serialized\package.md
[ ] src\Lucene.Net.Spatial\Util\package.md
[ ] src\Lucene.Net.Spatial\Vector\package.md
[ ] src\Lucene.Net.Suggest\overview.md
[ ] src\Lucene.Net.Suggest\Spell\package.md
[ ] src\Lucene.Net.Suggest\Suggest\Analyzing\package.md
[ ] src\Lucene.Net.Suggest\Suggest\Fst\package.md
[ ] src\Lucene.Net.Suggest\Suggest\Jaspell\package.md
[ ] src\Lucene.Net.Suggest\Suggest\package.md
[ ] src\Lucene.Net.Suggest\Suggest\Tst\package.md
[ ] src\Lucene.Net.TestFramework\Analysis\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Asserting\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Bloom\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\CheapBastard\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Compressing\Dummy\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Compressing\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Lucene3x\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Lucene40\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Lucene41\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Lucene41Ords\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Lucene42\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\Lucene45\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\MockIntBlock\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\MockRandom\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\MockSep\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\NestedPulsing\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\package.md
[ ] src\Lucene.Net.TestFramework\Codecs\RAMOnly\package.md
[ ] src\Lucene.Net.TestFramework\Index\package.md
[ ] src\Lucene.Net.TestFramework\overview.md
[ ] src\Lucene.Net.TestFramework\Search\package.md
[ ] src\Lucene.Net.TestFramework\Store\package.md
[ ] src\Lucene.Net.TestFramework\Util\Automaton\package.md
[ ] src\Lucene.Net.TestFramework\Util\Fst\package.md
[ ] src\Lucene.Net.TestFramework\Util\package.md
[x] src\Lucene.Net\Analysis\package.md
[ ] src\Lucene.Net\Analysis\TokenAttributes\package.md
[ ] src\Lucene.Net\Codecs\Compressing\package.md
[ ] src\Lucene.Net\Codecs\Lucene3x\package.md
[ ] src\Lucene.Net\Codecs\Lucene40\package.md
[ ] src\Lucene.Net\Codecs\Lucene41\package.md
[ ] src\Lucene.Net\Codecs\Lucene42\package.md
[ ] src\Lucene.Net\Codecs\Lucene45\package.md
[ ] src\Lucene.Net\Codecs\Lucene46\package.md
[ ] src\Lucene.Net\Codecs\package.md
[ ] src\Lucene.Net\Codecs\PerField\package.md
[ ] src\Lucene.Net\Document\package.md
[ ] src\Lucene.Net\Index\package.md
[x] src\Lucene.Net\migration-guide.md
[x] src\Lucene.Net\overview.md
[x] src\Lucene.Net\package.md
[ ] src\Lucene.Net\Search\package.md
[ ] src\Lucene.Net\Search\Payloads\package.md
[ ] src\Lucene.Net\Search\Similarities\package.md
[ ] src\Lucene.Net\Search\Spans\package.md
[ ] src\Lucene.Net\Store\package.md
[ ] src\Lucene.Net\Util\Automaton\package.md
[ ] src\Lucene.Net\Util\Fst\package.md
[ ] src\Lucene.Net\Util\Mutable\package.md
[ ] src\Lucene.Net\Util\package.md
[ ] src\Lucene.Net\Util\Packed\package.md
[ ] websites\apidocs\apiSpec\core\Lucene_Net_Codecs.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_AssociationsFacetsExample.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_DistanceFacetsExample.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_ExpressionAggregationFacetsExample.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_MultiCategoryListsFacetsExample.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_RangeFacetsExample.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_SimpleFacetsExample.md
[ ] websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_SimpleSortedSetFacetsExample.md
[ ] websites\apidocs\index.md

Anyone knows which Java version the latest Lucene.Net maps to?
And why Lucene.Net has no stable version released for such a long time?

Anyone knows which Java version the latest Lucene.Net maps to?

Lucene 4.8.0 supports Java 4, 5, and 6.

And why Lucene.Net has no stable version released for such a long time?

Quite simply, because there haven't been enough people contributing, and we only recently got any sponsorship. There has been 5000+ hours contributed since 2014 on Lucene.NET 4.8.0, of which I have personally contributed about 4000 hours. Lucene.NET was pretty much ported in 2017, but we are now trying to finish up all of the dependencies that didn't exist in .NET (namely ICU4N and J2N), testing on different platforms and operating systems, and implement enough of the features of the test framework that we can be reasonably sure that we aren't getting false positives. There is also some research to do to work out how to implement some of the features properly on the .NET platform, quite a bit of cleanup work of the APIs, and more performance tuning to do. Not to mention chasing down bug reports and answering user inquiries that we could use help with.
There are around 1100-1200 hours of work left to complete Lucene.NET 4.8.0 to production with its dependencies. Microsoft has recently sponsored 200 hours, and is considering more funding. We are also getting some funding from iTextSharp. But, for a project of this size and complexity we are going to need more contributions, more funding, or both to see this through to the point it is enterprise-ready.
For anyone interested in sponsoring the project, either do so through our personal GitHub sponsors accounts or contact me via the email address on my profile and I will provide details on how to sponsor the project as a whole. Or, if you would like to make a contribution, do note that anything marked up-for-grabs is free for anyone to start working on - simply leave a message on the issue and we will assign it to you.

Thanks so much for your response. @NightOwl888

Anyone knows which Java version the latest Lucene.Net maps to?

Lucene 4.8.0 supports Java 4, 5, and 6.

Sorry, I mean the Java Lucene version. I am seeing that the latest Java Lucene is 8.6.0. Does Lucene.Net 4.8.0 match Lucene 4.8.0? I am asking because I cannot believe it falls behind so much.

And why Lucene.Net has no stable version released for such a long time?

Quite simply, because there haven't been enough people contributing, and we only recently got any sponsorship.

I didn't know that there are so few people contributing for such a complicated project. Thank you so much for your effort on this! I  hope you can find more contributors. This is really a wonderful project for .net developers.

Sorry, I mean the Java Lucene version. I am seeing that the latest Java Lucene is 8.6.0. Does Lucene.Net 4.8.0 match Lucene 4.8.0?

The core Lucene.Net project is based on 4.8.0. Most of the submodules including Lucene.Net.Analyisis.Common are based on 4.8.1. Some of the other analysis modules were ported from 7.2.0 and 8.2.0 (which were the latest at the time we ported them).

I am asking because I cannot believe it falls behind so much.

That is the battle we are fighting. People get the impression that we are far behind because of the number of years it has taken and the fact there are 4 major versions between Lucene.NET and Lucene.
Last I checked (I believe it was 8.3.0), there were exactly 7 new modules and about 12 new features of any consequence added since 4.8.0. That's it. Look at the source code if you don't believe it. There was a discussion back in 2018 that I wasn't part of where some people said they are withholding their support because we are not targeting the latest version. I am curious to know whether they realize:

Lucene.NET 4.8.0 is almost stable and has been since that conversation happened in 2018
We have been working on Lucene.NET's dependencies since then (that both 4.8.0 and 8.x require)
It would take around 1800 hours to upgrade from 4.8.0 to 8.x, not including the 1100-1200 hours we have yet to complete now
Changing gears now will rob the .NET community of a stable Lucene.NET 4.8.0 in 2021, and take at least an extra year to stabilize and roll out
We are planning to upgrade to 8.x after the release of Lucene.NET 4.8.0 is stable and we have secured enough funding to get started
8.x has only about 12 new features that 4.8.0 doesn't have that are of any consequence

I am curious to know which of the 12 or so new features that people think are so important that they are withholding their support, and how they could ever think it would be worth it for us to derail the whole project for at least a year to try to reach that goal. Not to mention robbing the entire .NET community of a stable 4.8.0 while they wait for that work to be completed.
Our sponsors at Microsoft doesn't agree with those people. They don't even agree with us that it is worth it to upgrade to 8.x after the release of 4.8.0. Sure there are bug fixes and performance benefits in the new version, but the total benefit for the cost just isn't there.
Unfortunately the gap between the reality of the situation and the impression that people get about how far we are behind is a big one, and that situation isn't going to change until we either reach a stable 4.8.0 or the community provides enough funding for the extra 1800 hours of labor involved in re-targeting to 8.2.0.

@NightOwl888 Thank you for this response and succinct comparison of 4.8 vs 8.3 as well as highlighting the gap between perception and reality with regard to the differences between those to versions.  This is enlightening to me and explains a lot.  The strategy of getting 4.8 released before working towards the latest version makes perfect sense.  I truly wish I had some bandwidth to help contribute.  In the future I hope to get myself to a position where I can.  In my mind, there is no more worthy open source project in the .Net ecosystem then Lucene.Net to warrant developer contributions.  This code base and the functionality it provides is truly impressive.

@rclabo - Thanks for the kind words and support. As you might have noticed, I have changed my tune a little. We totally understand if people don't have the kind of bandwidth it takes to contribute, especially being that there is a bit of a learning curve before a contribution can even begin. In fact, when I lived in the U.S., I couldn't imagine how anyone could find the time to do open source work. But if that is indeed the case, we ask that those people show their support by making a small monetary contribution instead. We'd rather see this project crowdfunded by several hundred parties than have one or two companies carry the whole load on their backs, anyway.
https://github.com/sponsors/NightOwl888
https://github.com/sponsors/Shazwazza

@NightOwl888 - I think that's also a great approach.  If we could get a large community supporting the project with small monetary contributions that would be awesome.  Still, I also think we need to get more devs coding and supporting the project with their skills.  I truly hope to be a part of that down the road.

@Shazwazza
I have generated a list of the Markdown documents and tailored it to the API docs that we should review for this issue.
However, in the process I noticed that we have demo examples that have been copied into the docs:

websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_AssociationsFacetsExample.md
websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_DistanceFacetsExample.md
websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_ExpressionAggregationFacetsExample.md
websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_MultiCategoryListsFacetsExample.md
websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_RangeFacetsExample.md
websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_SimpleFacetsExample.md
websites\apidocs\apiSpec\demo\Lucene_Net_Demo_Facet_SimpleSortedSetFacetsExample.md

I don't know specifically how often we are going to need to update the demos, but having duplicate copies of them doesn't seem like a good idea maintenance-wise. And if we are going to copy them, we are missing the 2 main ones that are linked from the main "core" overview page:

IndexFiles.cs
SearchFiles.cs

Is there some reason why we need to duplicate this code into documents? Ideally, our docs would link to the state of these files at the tag of the release so we wouldn't have extra documents to maintain when the code changes.
Also, where are these documents linked from on the website? I couldn't find any references to them.


Issue with yankpad-category-descriptions in empty org file

Hi!
I have been scratching my head lately because any time I was trying to insert an org-mode snippet in an empty org file I would get:
org-back-to-heading: Before first headline at position 3 in buffer test.org

If you want to reproduce just create an empty org-mode file and call (yankpad-insert), really (yankpad-category-descriptions "") for the minimal reproduction step.
After some inspection of yankpad.el I found the possible culprit:
apparently yankpad-category-descriptions uses (org-narrow-to-subtree) which simply cannot work because an empty org-mode file has no subtree in it.
I wonder if you designed the function this way for a reason because I am not sure I get what yankpad-category-descriptions actually does.
Any chance you could ignore the errors like (ignore-errors (org-narrow-to-subtree))? Would that make sense to skip the narrowing if no org headline is in there?
Thanks for Yankpad!

Hi! For me it works fine to run (yankpad-insert) at the top of an empty org-mode file.
yankpad-category-descriptions shouldn't be executed from outside the yankpad-file, so that functions shouldn't be called in the context of your empty file. It could be something going on with your yankpad-file, or there might be some bug in my code (maybe both). If you could turn on M-x toggle-debug-on-error and post the result here, and maybe also your yankpad-file if it isn't private.

Ah! You are right, this was an issue on my side.
I checked again my yankpad.org and I found out that recently I deleted a
heading that I included in org-mode:
So my org-mode heading in the Yankpad file starts with:

org-mode
:PROPERTIES:
:INCLUDE:  something|something-else|not-existing-heading|even-more
:header-args: :noeval
:END:

When I removed the included heading that did not exist anymore,
everything worked fine again.
Sorry for the noise! And thanks for pointing out it could be on my side:
next time I will try to reproduce with a pristine Yankpad file before
submitting an issue :P
On Sun 30 Aug 2020 at 23:44, Erik Sjöstrand<EMAIL_ADDRESS>wrote:

Hi! For me it works fine to run (yankpad-insert) at the top of an empty org-mode file.
yankpad-category-descriptions shouldn't be executed from outside the yankpad-file, so that functions shouldn't be called in the context of your empty file. It could be something going on with your yankpad-file, or there might be some bug in my code (maybe both). If you could turn on M-x toggle-debug-on-error and post the result here, and maybe also your yankpad-file if it isn't private.


Initial automated testing suite

Beginning of the automated testing suite for the Grey Matter Fabric Dashboard. In order to run the tests, you will need to have Google Chrome installed, download the Chromedriver, and put the chromedriver binary in /opt/. You can then run the tests from the command line by navigating to the test-automation/ directory and running ./gradlew test. The test currently run against a local build fed by the mock SDS service, both of which will need to be running prior to starting the tests (the plan is to have multiple environments against which the tests can be run).

Closing this PR but retaining the feature branch pending refactor of Integration Testing into JavaScript.


Make --pulls mutually exclusive with --interactive.

You might want to remove this bit https://github.com/ros-tooling/ros-github-scripts/blob/403355b01b3782d4e3f21b5546b7368d39e054fb/ros_github_scripts/ci_for_pr.py#L373

Oh wait, that's if none of them are provided. Nevermind.


randomly not working at restart (more often than OK)

Hi,
after updating to 2023.3, I have a big issue : I cannot use this integration :

I installed a development environment in vscode + docker desktop, and I can reproduce this behaviour ... sort of.
I only need to restart the debug environment ( stop + F5 or click this icon :

)
and One time, it will work, next start it will not work ... on my production env (rpi4) it never works anymore. Seems to be a startup order issue but I cannot yet understand how to fix it, would you mind looking at it please ?

here is a startup log where it fails :
vscode ➜ /workspaces/core (as_rest_template_resource) $  cd /workspaces/core ; /usr/bin/env /usr/local/bin/python /home/vscode/.vscode-server/extensions/ms-
python.python-2022.16.1/pythonFiles/lib/python/debugpy/adapter/../../debugpy/launcher 34909 -- -m homeassistant --debug -c config
2023-03-26 14:17:05.726 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration custom_filters which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-03-26 14:17:05.733 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration rest which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-03-26 14:17:06.073 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
2023-03-26 14:17:06.078 INFO (MainThread) [homeassistant.bootstrap] Setting up frontend: {'frontend'}
2023-03-26 14:17:06.120 INFO (MainThread) [homeassistant.setup] Setting up device_automation
2023-03-26 14:17:06.122 INFO (MainThread) [homeassistant.setup] Setup of domain device_automation took 0.0 seconds
2023-03-26 14:17:06.201 INFO (MainThread) [homeassistant.setup] Setting up lovelace
2023-03-26 14:17:06.224 INFO (MainThread) [homeassistant.setup] Setting up http
2023-03-26 14:17:06.242 INFO (MainThread) [homeassistant.setup] Setup of domain lovelace took 0.0 seconds
2023-03-26 14:17:06.272 INFO (MainThread) [homeassistant.setup] Setup of domain http took 0.0 seconds
2023-03-26 14:17:06.315 INFO (MainThread) [homeassistant.setup] Setting up api
2023-03-26 14:17:06.323 INFO (MainThread) [homeassistant.setup] Setup of domain api took 0.0 seconds
2023-03-26 14:17:06.324 INFO (MainThread) [homeassistant.setup] Setting up auth
2023-03-26 14:17:06.330 INFO (MainThread) [homeassistant.setup] Setup of domain auth took 0.0 seconds
2023-03-26 14:17:06.333 INFO (MainThread) [homeassistant.setup] Setting up config
2023-03-26 14:17:06.354 INFO (MainThread) [homeassistant.setup] Setting up diagnostics
2023-03-26 14:17:06.373 INFO (MainThread) [homeassistant.setup] Setting up repairs
2023-03-26 14:17:06.377 INFO (MainThread) [homeassistant.setup] Setup of domain repairs took 0.0 seconds
2023-03-26 14:17:06.598 WARNING (MainThread) [asyncio] Executing <Task finished name='Task-91' coro=<async_setup.<locals>.setup_panel() done, defined at /workspaces/core/homeassistant/components/config/__init__.py:42> result=None created at /usr/local/lib/python3.10/asyncio/tasks.py:337> took 0.198 seconds
2023-03-26 14:17:06.668 INFO (MainThread) [homeassistant.setup] Setting up file_upload
2023-03-26 14:17:06.670 INFO (MainThread) [homeassistant.setup] Setup of domain file_upload took 0.0 seconds
2023-03-26 14:17:06.676 INFO (MainThread) [homeassistant.setup] Setup of domain config took 0.3 seconds
2023-03-26 14:17:06.682 INFO (MainThread) [homeassistant.setup] Setup of domain diagnostics took 0.3 seconds
2023-03-26 14:17:06.792 INFO (MainThread) [homeassistant.setup] Setting up image_upload
2023-03-26 14:17:06.803 INFO (MainThread) [homeassistant.setup] Setting up websocket_api
2023-03-26 14:17:06.805 INFO (MainThread) [homeassistant.setup] Setup of domain websocket_api took 0.0 seconds
2023-03-26 14:17:06.820 INFO (MainThread) [homeassistant.setup] Setup of domain image_upload took 0.0 seconds
2023-03-26 14:17:06.847 INFO (SyncWorker_2) [homeassistant.loader] Loaded group from homeassistant.components.group
2023-03-26 14:17:06.875 INFO (SyncWorker_1) [homeassistant.loader] Loaded device_tracker from homeassistant.components.device_tracker
2023-03-26 14:17:06.908 INFO (MainThread) [homeassistant.setup] Setting up search
2023-03-26 14:17:06.909 INFO (MainThread) [homeassistant.setup] Setup of domain search took 0.0 seconds
2023-03-26 14:17:08.327 INFO (MainThread) [homeassistant.setup] Setting up analytics
2023-03-26 14:17:08.343 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component analytics' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:256> wait_for=<Task pending name='Storage load core.analytics' coro=<Store._async_load() running at /workspaces/core/homeassistant/helpers/storage.py:124> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 1.433 seconds
2023-03-26 14:17:08.353 INFO (MainThread) [homeassistant.setup] Setting up person
2023-03-26 14:17:08.366 INFO (MainThread) [homeassistant.setup] Setup of domain analytics took 0.0 seconds
2023-03-26 14:17:08.404 INFO (MainThread) [homeassistant.setup] Setup of domain person took 0.1 seconds
2023-03-26 14:17:08.422 INFO (SyncWorker_1) [homeassistant.loader] Loaded hassio from homeassistant.components.hassio
2023-03-26 14:17:08.427 INFO (MainThread) [homeassistant.setup] Setting up onboarding
2023-03-26 14:17:08.435 INFO (MainThread) [homeassistant.setup] Setup of domain onboarding took 0.0 seconds
2023-03-26 14:17:08.468 INFO (MainThread) [homeassistant.setup] Setting up frontend
2023-03-26 14:17:08.482 INFO (MainThread) [homeassistant.setup] Setup of domain frontend took 0.0 seconds
2023-03-26 14:17:08.499 INFO (MainThread) [homeassistant.bootstrap] Setting up recorder: {'recorder'}
2023-03-26 14:17:08.507 INFO (MainThread) [homeassistant.setup] Setting up recorder
2023-03-26 14:17:08.529 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //workspaces/core/config/home-assistant_v2.db was shutdown cleanly
2023-03-26 14:17:08.594 INFO (MainThread) [asyncio] <Server sockets=(<asyncio.TransportSocket fd=12, family=AddressFamily.AF_INET6, type=SocketKind.SOCK_STREAM, proto=6, laddr=('::', 8123, 0, 0)>, <asyncio.TransportSocket fd=13, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('<IP_ADDRESS>', 8123)>)> is serving
2023-03-26 14:17:08.596 INFO (MainThread) [homeassistant.components.http] Now listening on port 8123
2023-03-26 14:17:08.626 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=69 from 2023-03-26 14:16:45.261280)
2023-03-26 14:17:08.663 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.2 seconds
2023-03-26 14:17:08.673 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 1: {'dhcp', 'websocket_api', 'zeroconf', 'ssdp', 'api', 'webhook', 'network', 'cloud', 'http', 'usb', 'bluetooth'}
2023-03-26 14:17:08.710 INFO (MainThread) [homeassistant.setup] Setting up webhook
2023-03-26 14:17:08.713 INFO (MainThread) [homeassistant.setup] Setup of domain webhook took 0.0 seconds
2023-03-26 14:17:08.821 INFO (MainThread) [homeassistant.setup] Setting up dhcp
2023-03-26 14:17:08.823 INFO (MainThread) [homeassistant.setup] Setup of domain dhcp took 0.0 seconds
2023-03-26 14:17:08.853 INFO (MainThread) [homeassistant.setup] Setting up network
2023-03-26 14:17:08.856 INFO (MainThread) [homeassistant.setup] Setup of domain network took 0.0 seconds
2023-03-26 14:17:08.881 INFO (MainThread) [homeassistant.setup] Setting up usb
2023-03-26 14:17:08.883 INFO (MainThread) [homeassistant.setup] Setup of domain usb took 0.0 seconds
2023-03-26 14:17:08.906 INFO (SyncWorker_0) [homeassistant.loader] Loaded google_assistant from homeassistant.components.google_assistant
2023-03-26 14:17:08.909 INFO (SyncWorker_2) [homeassistant.loader] Loaded alexa from homeassistant.components.alexa
2023-03-26 14:17:08.934 INFO (SyncWorker_2) [homeassistant.loader] Loaded camera from homeassistant.components.camera
2023-03-26 14:17:09.070 INFO (MainThread) [homeassistant.setup] Setting up zeroconf
2023-03-26 14:17:09.078 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component zeroconf' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:256> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()] created at /usr/local/lib/python3.10/asyncio/tasks.py:665> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 0.132 seconds
2023-03-26 14:17:09.158 INFO (MainThread) [homeassistant.setup] Setting up ssdp
2023-03-26 14:17:09.174 INFO (MainThread) [homeassistant.setup] Setup of domain zeroconf took 0.1 seconds
2023-03-26 14:17:09.324 INFO (MainThread) [homeassistant.setup] Setting up bluetooth
2023-03-26 14:17:09.338 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component bluetooth' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:256> wait_for=<Task pending name='Storage load bluetooth.remote_scanners' coro=<Store._async_load() running at /workspaces/core/homeassistant/helpers/storage.py:124> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 0.134 seconds
2023-03-26 14:17:09.346 INFO (SyncWorker_1) [homeassistant.loader] Loaded media_player from homeassistant.components.media_player
2023-03-26 14:17:09.355 INFO (MainThread) [homeassistant.components.zeroconf] Starting Zeroconf broadcast
2023-03-26 14:17:09.389 INFO (MainThread) [asyncio] <Server sockets=(<asyncio.TransportSocket fd=18, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('<IP_ADDRESS>', 40000)>,)> is serving
2023-03-26 14:17:10.053 INFO (MainThread) [homeassistant.setup] Setting up cloud
2023-03-26 14:17:10.057 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component cloud' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:256> wait_for=<Task pending name='Storage load cloud' coro=<Store._async_load() running at /workspaces/core/homeassistant/helpers/storage.py:124> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 0.661 seconds
2023-03-26 14:17:10.114 INFO (MainThread) [homeassistant.setup] Setup of domain bluetooth took 0.8 seconds
2023-03-26 14:17:10.121 INFO (MainThread) [homeassistant.setup] Setup of domain ssdp took 1.0 seconds
2023-03-26 14:17:10.196 INFO (MainThread) [homeassistant.setup] Setup of domain cloud took 0.1 seconds
2023-03-26 14:17:10.238 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'blueprint', 'onboarding', 'script', 'conversation', 'tag', 'input_datetime', 'homeassistant_alerts', 'schedule', 'counter', 'person', 'custom_filters', 'sun', 'trace', 'config', 'my', 'auth', 'input_text', 'media_source', 'input_number', 'image_upload', 'default_config', 'zone', 'device_automation', 'application_credentials', 'system_health', 'analytics', 'logbook', 'scene', 'input_select', 'mobile_app', 'lovelace', 'map', 'radio_browser', 'history', 'timer', 'tts', 'met', 'repairs', 'energy', 'search', 'automation', 'input_button', 'diagnostics', 'hardware', 'input_boolean', 'file_upload'}
2023-03-26 14:17:10.397 INFO (MainThread) [homeassistant.setup] Setting up blueprint
2023-03-26 14:17:10.399 INFO (MainThread) [homeassistant.setup] Setup of domain blueprint took 0.0 seconds
2023-03-26 14:17:10.414 INFO (MainThread) [homeassistant.setup] Setting up tag
2023-03-26 14:17:10.421 INFO (MainThread) [homeassistant.setup] Setting up input_datetime
2023-03-26 14:17:10.430 INFO (MainThread) [homeassistant.setup] Setting up homeassistant_alerts
2023-03-26 14:17:10.433 INFO (MainThread) [homeassistant.setup] Setup of domain homeassistant_alerts took 0.0 seconds
2023-03-26 14:17:10.448 INFO (MainThread) [homeassistant.setup] Setting up schedule
2023-03-26 14:17:10.457 INFO (MainThread) [homeassistant.setup] Setting up counter
2023-03-26 14:17:10.463 INFO (MainThread) [homeassistant.setup] Setting up sun
2023-03-26 14:17:10.466 INFO (MainThread) [homeassistant.setup] Setup of domain sun took 0.0 seconds
2023-03-26 14:17:10.467 INFO (MainThread) [homeassistant.setup] Setting up trace
2023-03-26 14:17:10.469 INFO (MainThread) [homeassistant.setup] Setup of domain trace took 0.0 seconds
2023-03-26 14:17:10.478 INFO (MainThread) [homeassistant.setup] Setting up input_text
2023-03-26 14:17:10.488 INFO (MainThread) [homeassistant.setup] Setting up input_number
2023-03-26 14:17:10.519 INFO (MainThread) [homeassistant.setup] Setting up zone
2023-03-26 14:17:10.535 INFO (MainThread) [homeassistant.setup] Setting up scene
2023-03-26 14:17:10.536 INFO (MainThread) [homeassistant.components.scene] Setting up scene.homeassistant
2023-03-26 14:17:10.542 INFO (MainThread) [homeassistant.setup] Setting up input_select
2023-03-26 14:17:10.726 INFO (MainThread) [homeassistant.setup] Setting up history
2023-03-26 14:17:10.730 INFO (MainThread) [homeassistant.setup] Setup of domain history took 0.0 seconds
2023-03-26 14:17:10.731 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component history' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:289> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 0.177 seconds
2023-03-26 14:17:10.734 INFO (MainThread) [homeassistant.setup] Setting up timer
2023-03-26 14:17:10.747 INFO (MainThread) [homeassistant.setup] Setting up input_button
2023-03-26 14:17:10.754 INFO (MainThread) [homeassistant.setup] Setting up input_boolean
2023-03-26 14:17:10.983 INFO (MainThread) [homeassistant.setup] Setting up my
2023-03-26 14:17:10.985 INFO (MainThread) [homeassistant.setup] Setup of domain my took 0.0 seconds
2023-03-26 14:17:10.999 INFO (MainThread) [homeassistant.setup] Setting up media_source
2023-03-26 14:17:11.043 INFO (MainThread) [homeassistant.setup] Setting up application_credentials
2023-03-26 14:17:11.047 INFO (MainThread) [homeassistant.setup] Setting up system_health
2023-03-26 14:17:11.182 INFO (MainThread) [homeassistant.setup] Setting up logbook
2023-03-26 14:17:11.220 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component logbook' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:256> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()] created at /usr/local/lib/python3.10/asyncio/tasks.py:665> cb=[set.remove(), <1 more>, Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 0.135 seconds
2023-03-26 14:17:11.224 INFO (MainThread) [homeassistant.setup] Setup of domain scene took 0.7 seconds
2023-03-26 14:17:11.228 INFO (MainThread) [homeassistant.setup] Setting up map
2023-03-26 14:17:11.230 INFO (MainThread) [homeassistant.setup] Setup of domain map took 0.0 seconds
2023-03-26 14:17:11.236 INFO (MainThread) [homeassistant.setup] Setting up energy
2023-03-26 14:17:11.239 INFO (MainThread) [homeassistant.setup] Setup of domain energy took 0.0 seconds
2023-03-26 14:17:11.242 INFO (MainThread) [homeassistant.setup] Setting up automation
2023-03-26 14:17:11.266 INFO (MainThread) [homeassistant.setup] Setup of domain tag took 0.9 seconds
2023-03-26 14:17:11.279 INFO (MainThread) [homeassistant.setup] Setting up script
2023-03-26 14:17:11.378 INFO (MainThread) [homeassistant.setup] Setting up custom_filters
2023-03-26 14:17:11.380 INFO (MainThread) [homeassistant.setup] Setup of domain custom_filters took 0.0 seconds
2023-03-26 14:17:11.426 INFO (MainThread) [homeassistant.setup] Setting up conversation
2023-03-26 14:17:11.429 INFO (MainThread) [homeassistant.setup] Setup of domain conversation took 0.0 seconds
2023-03-26 14:17:11.480 INFO (SyncWorker_2) [homeassistant.loader] Loaded sensor from homeassistant.components.sensor
2023-03-26 14:17:11.528 INFO (MainThread) [homeassistant.setup] Setup of domain media_source took 0.5 seconds
2023-03-26 14:17:11.530 INFO (MainThread) [homeassistant.setup] Setup of domain system_health took 0.5 seconds
2023-03-26 14:17:11.531 INFO (MainThread) [homeassistant.setup] Setup of domain logbook took 0.3 seconds
2023-03-26 14:17:11.578 INFO (MainThread) [homeassistant.setup] Setup of domain counter took 1.1 seconds
2023-03-26 14:17:11.608 INFO (MainThread) [homeassistant.setup] Setup of domain timer took 0.9 seconds
2023-03-26 14:17:11.741 INFO (MainThread) [homeassistant.setup] Setting up radio_browser
2023-03-26 14:17:11.743 INFO (MainThread) [homeassistant.setup] Setup of domain radio_browser took 0.0 seconds
2023-03-26 14:17:11.744 WARNING (MainThread) [asyncio] Executing <Task pending name='setup component radio_browser' coro=<_async_setup_component() running at /workspaces/core/homeassistant/setup.py:289> cb=[set.remove(), Task.task_wakeup()] created at /workspaces/core/homeassistant/core.py:526> took 0.117 seconds
2023-03-26 14:17:11.804 INFO (MainThread) [homeassistant.setup] Setup of domain automation took 0.6 seconds
2023-03-26 14:17:11.832 INFO (MainThread) [homeassistant.setup] Setup of domain script took 0.6 seconds
2023-03-26 14:17:11.882 INFO (MainThread) [homeassistant.setup] Setup of domain zone took 1.4 seconds
2023-03-26 14:17:11.894 INFO (MainThread) [homeassistant.setup] Setting up sensor
2023-03-26 14:17:11.897 INFO (MainThread) [homeassistant.setup] Setup of domain sensor took 0.0 seconds
2023-03-26 14:17:11.911 INFO (MainThread) [homeassistant.setup] Setup of domain application_credentials took 0.9 seconds
2023-03-26 14:17:11.916 INFO (MainThread) [homeassistant.setup] Setup of domain input_datetime took 1.5 seconds
2023-03-26 14:17:11.957 INFO (MainThread) [homeassistant.setup] Setup of domain schedule took 1.5 seconds
2023-03-26 14:17:12.000 INFO (MainThread) [homeassistant.setup] Setup of domain input_text took 1.5 seconds
2023-03-26 14:17:12.027 INFO (MainThread) [homeassistant.setup] Setup of domain input_number took 1.5 seconds
2023-03-26 14:17:12.104 INFO (SyncWorker_0) [homeassistant.loader] Loaded google_translate from homeassistant.components.google_translate
2023-03-26 14:17:12.117 INFO (MainThread) [homeassistant.setup] Setting up met
2023-03-26 14:17:12.118 INFO (MainThread) [homeassistant.setup] Setup of domain met took 0.0 seconds
2023-03-26 14:17:12.139 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.energy
2023-03-26 14:17:12.165 INFO (MainThread) [homeassistant.setup] Setup of domain input_select took 1.6 seconds
2023-03-26 14:17:12.186 INFO (MainThread) [homeassistant.setup] Setup of domain input_button took 1.4 seconds
2023-03-26 14:17:12.207 INFO (MainThread) [homeassistant.setup] Setup of domain input_boolean took 1.5 seconds
2023-03-26 14:17:12.230 INFO (MainThread) [homeassistant.setup] Setting up hardware
2023-03-26 14:17:12.359 INFO (SyncWorker_2) [homeassistant.loader] Loaded notify from homeassistant.components.notify
2023-03-26 14:17:12.366 INFO (MainThread) [homeassistant.setup] Setup of domain hardware took 0.1 seconds
2023-03-26 14:17:12.395 INFO (MainThread) [homeassistant.setup] Setting up tts
2023-03-26 14:17:12.453 INFO (MainThread) [homeassistant.setup] Setting up mobile_app
2023-03-26 14:17:12.484 INFO (MainThread) [homeassistant.setup] Setup of domain mobile_app took 0.0 seconds
2023-03-26 14:17:12.496 INFO (MainThread) [homeassistant.setup] Setting up notify
2023-03-26 14:17:12.498 INFO (MainThread) [homeassistant.setup] Setup of domain notify took 0.0 seconds
2023-03-26 14:17:12.509 INFO (MainThread) [homeassistant.setup] Setup of domain tts took 0.1 seconds
2023-03-26 14:17:12.615 INFO (MainThread) [homeassistant.components.notify] Setting up notify.mobile_app
2023-03-26 14:17:12.627 INFO (MainThread) [homeassistant.setup] Setting up default_config
2023-03-26 14:17:12.634 INFO (SyncWorker_1) [homeassistant.loader] Loaded backup from homeassistant.components.backup
2023-03-26 14:17:12.846 WARNING (MainThread) [asyncio] Executing <Task pending name='config entry setup Home met abb89bc4684eb6f201efe2e6aee1d121' coro=<ConfigEntry.async_setup() running at /workspaces/core/homeassistant/config_entries.py:383> wait_for=<_GatheringFuture pending cb=[Task.task_wakeup()] created at /usr/local/lib/python3.10/asyncio/tasks.py:665> cb=[gather.<locals>._done_callback() at /usr/local/lib/python3.10/asyncio/tasks.py:720] created at /usr/local/lib/python3.10/asyncio/tasks.py:337> took 0.196 seconds
2023-03-26 14:17:12.858 INFO (MainThread) [homeassistant.setup] Setting up backup
2023-03-26 14:17:12.862 INFO (MainThread) [homeassistant.setup] Setup of domain backup took 0.0 seconds
2023-03-26 14:17:12.874 INFO (SyncWorker_1) [homeassistant.loader] Loaded weather from homeassistant.components.weather
2023-03-26 14:17:12.881 INFO (MainThread) [homeassistant.setup] Setup of domain default_config took 0.3 seconds
2023-03-26 14:17:12.891 INFO (MainThread) [homeassistant.setup] Setting up weather
2023-03-26 14:17:12.893 INFO (MainThread) [homeassistant.setup] Setup of domain weather took 0.0 seconds
2023-03-26 14:17:12.917 INFO (MainThread) [homeassistant.components.weather] Setting up weather.met
2023-03-26 14:17:12.964 INFO (MainThread) [homeassistant.bootstrap] Home Assistant initialized in 7.29s
2023-03-26 14:17:12.966 INFO (MainThread) [homeassistant.core] Starting Home Assistant

I just installed this integration, hoping it would help me turn strings into lists or dictionaries but I experienced the same issue than aschor and despite several restarts could not never get listify to work (TemplateAssertionError: No filter named 'listify').
This is unfortunate as this integration would have helped me a lot.

I too am getting the TemplateAssertionError.  I was really hoping this worked so I could add my own filter to it.

@bigramonk @uSlackr -- this should be resolved with the most recent updates from my merge request. Please let me know if it's working for you after updating.
@zvldz  -- please resolve this (#5) and #2 !

@bigramonk @uSlackr -- this should be resolved with the most recent updates from my merge request. Please let me know if it's working for you after updating.
@zvldz -- please resolve this (#5) and #2 !

Sorry, it still does not work for me, I get the same error

@bigramonk @uSlackr -- this should be resolved with the most recent updates from my merge request. Please let me know if it's working for you after updating.
@zvldz -- please resolve this (#5) and #2 !

Working OK now, thanks!!

Same problem here with 0.9.20

Same problem here with 2023.9.0. It worked for me in previous versions, however only with the described restart problem as well. Now with 2023.9.0 it doesn't seem to work at all.
The only related line in the logs (searching for "custom_filters") seems to be this one:
2023-09-07 17:06:24.907 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration custom_filters which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
It would be great if anyone could look into this!

Adding to my previous post, I now experienced that in the developer tools, the expression {{ shuffle(['A','B','C']) }} returns a valid result, however when I try to use the same expression in a script, it produces the error "UndefinedError: 'shuffle' is undefined". Very strange...


Why use @throttledPlayAudio instead of @playAudio.play().

Label:question
Hello, inside power-editor.coffee, there are some functions that are called by @throttled
I'm wondering what is the reason for use @throttledPlayAudio() instead of @playAudio.play() directly.
It do the same and quicker.
if @getConfig "playAudio.enabled"
#@throttledPlayAudio()
@playAudio.play()
Also I tried to create my own function using the @throttled call method but I got a error
"Uncaught TypeError: this.getConfig is not a function" I recive that error because I didn't include the
function: getConfig: (config) -> inside my file.
which return: atom.config.get "activate-power-mode.#{config}"
if some one can explain me the functionality of @throttled call methord, I will thank you.
Thanks for the help.

This is the documentation for that function https://lodash.com/docs/4.17.4#throttle
Basically is used to avoid calling a function too many times, for performance reasons in the case of the screen shake.
If you need to use @ (this) inside a throttled function you need to bind it: .bind(this)

Thanks @lexcast


Update expensify-common to support italic style for @here mention

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/19857
PROPOSAL: https://github.com/Expensify/App/issues/19857#issuecomment-1571631459
Tests

Go to a chat
Add a comment

Below are here mentions
@here
@here abc
_@here_
*@here*
~@here~
@here*
@here~
@here#
@here@
@here$
@here^
@here(

Below aren’t here mentions
@here_123
@here_abc
@here123
@hereabc
[@here](https://google.com)

Verify that the first group are all rendered as @here mentions but the second group aren’t.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Same as test

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.3.27-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.3.27-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Avoid deleting .next directory on build

To minimize service downtime, is it possible to avoid removing the .next directory on build? I get a good 1 minute of “Internal Server Error” when deploying, depending on the server.
https://github.com/zeit/next.js/blob/master/server/build/index.js
https://github.com/zeit/next.js/blob/master/server/build/clean.js
The current (now old) state of the app should be able to stay active until the new state is ready to be started. Would it be an idea to compile the resources into .next-enifu723, and then, when ready, rename it to replace .next? That way it won't affect the current directory, which may be used in the current app.

I think I don't fully understand how you deploy your apps, but usually you should just swap your servers with new ones, then deleting .next should not be a problem and there is no downtime.

In this scenario I'm using pm2 to deploy and manage my application. On deploy, an execution script fires that looks something like:
next build && pm2 restart client

Yet, during the time it is building the new version, the current one stops working because it removes some required dist/ files and such.

Avoiding deleting .next directory wouldn't help since your app might load building state of .next anyway.
I think you should change how to deploy your app.

No? If next.js built the new resources in a separate directory, this approach would work just fine.

Ah, that would work in most cases but I think there is downtime between moving two folders and restarting servers.  btw I'm assuming the problem occurs because next.js server dynamically load files according to page requests. I'm not sure if it's worth to support that.

Downtime while renaming the two folders <<<<<<<<< downtime while building the new state.

I'll do a PR on this, I guess, where next build builds the new state in a separate directory (.next-12313) before replacing .next.

@nkzawa Maybe this makes the problem I'm outlining more clear: https://github.com/zeit/next.js/pull/1139

Merged. https://github.com/zeit/next.js/pull/1139#event-962264425


Implications of Modern Standby on SCCM Power Management

It appears based on logging that systems enabled for Modern Standby (Sleep State S0) are not able to be managed by power plans in SCCM. The PwrProvider.log reports this message:
The "Required idleness to sleep" setting (<GUID>) is not supported on this operating system.  This setting will be ignored.
It may be helpful to add a note here regarding Modern Standby and the SCCM client's relation to this sleep state.

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

ID: 5fd918fb-7d8a-cc92-f8d9-339c2db98cb1
Version Independent ID: 9cb416d9-1927-eb95-4e3f-ef9f9684b14b
Content: Create and apply power plans - Configuration Manager
Content Source: sccm/core/clients/manage/power/create-and-apply-power-plans.md
Product: configuration-manager
Technology: configmgr-client
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks for the feedback. I made a change to add a note for this. The issue will auto close when my change merges. It will then go live with the next daily publishing cycle.


Cannot view images

General Troubleshooting

[x] I have checked for similar issues.
[x] I have updated to the latest JDA version.
[x] I have checked the branches or the maintainers' PRs for upcoming bug fixes.

Bug Report

The images aren't appearing, and when I try to open it in a new tab, I see "Cannot proxy the given URL".
Expected Behavior
I should see the image

Code Example or Reproduction Steps

Open Tutorials/Java/Getting_Started_With_JDA.md
Observe

Exception or Error
Cannot proxy the given URL

Contact github support.


_content/doc: use mysql.NewConfig() instead of mysql.Config{}

The zero values for mysql.Config is not good for default.
See https://pkg.go.dev/github.com/go-sql-driver/mysql#Config

If a new Config is created instead of being parsed from a DSN string, the NewConfig function should be used, which sets default values.

This tutorial confuses users.
https://github.com/go-sql-driver/mysql/issues/1256


[Feature]Support hudi connector

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #7681
Problem Summary(Required) ：

run starrocks_fe_unittest

[FE PR Coverage check]
:disappointed: fail : 102 / 174 (58.62%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/external/hive/HiveMetaCache.java
3
19
15.79%

:large_blue_circle:
com/starrocks/catalog/HiveTable.java
1
2
50.00%

:large_blue_circle:
com/starrocks/catalog/HudiTable.java
28
51
54.90%

:large_blue_circle:
com/starrocks/connector/hudi/HudiMetadata.java
13
22
59.09%

:large_blue_circle:
com/starrocks/external/HiveMetaStoreTableUtils.java
36
56
64.29%

:large_blue_circle:
com/starrocks/connector/hudi/HudiConnector.java
13
16
81.25%

:large_blue_circle:
com/starrocks/sql/ast/CreateCatalogStmt.java
1
1
100.00%

:large_blue_circle:
com/starrocks/external/hive/Utils.java
3
3
100.00%

:large_blue_circle:
com/starrocks/connector/hudi/HudiConnectorFactory.java
3
3
100.00%

:large_blue_circle:
com/starrocks/connector/ConnectorMgr.java
1
1
100.00%

@adzfolc please check sonar alert, have some good advices.


Wrong error message when executing a SELECT query.

Hi everyone,
I'm trying to run a simple SELECT query from my database but it fails with following error message:
influxdb.exceptions.InfluxDBClientError: 403: {"error":"error authorizing query: my_user not authorized to execute statement 'SELECT * FROM \"measurements\"', requires READ on True"}
I  know that my user have the required permissions because when connecting to the DB with a CLI I can execute the query. On top of that I checked the permissions with SHOW GRANTS and I could see that all requirements are satisfied (the user actualy does have all privileges).
I saw some simillar issues already (for instance in this issue) however this does not fit my case since I'm quoting the query.
My code:
results = influx_db_client.query('SELECT * FROM "measurements"')
What looks weird to me is that in the error message the qutoes around table are escaped.

InfluxDB version: 1.8.0
InfluxDB-python version: 5.3.1
Python version: 3.6.8
Operating system version: CentOS 7

Anyone else facing this issue ?

I am facing exactly the same issue

Hi @babaMar,
I wasn't able to solve the issue. However, when I wrote the code in Java I was able to run my query. Hence, I had the assumption that their might be an issue with the python API of influxdb.
If you can use a different language I would recommend to do so (Cause as mentioned for me when swtiching to Java it worked straight ahead).
However, I'm still curious to find out the actual cause of the issue.

Hi @babaMar,
I wasn't able to solve the issue. However, when I wrote the code in Java I was able to run my query. Hence, I had the assumption that their might be an issue with the python API of influxdb.
If you can use a different language I would recommend to do so (Cause as mentioned for me when swtiching to Java it worked straight ahead).
However, I'm still curious to find out the actual cause of the issue.

I think I found the problem on my side. Most likely you're passing something else instead of the DB, and even if it doesn't exist it raises that error

Too bad that I do not have the code base anymopre but good to know that the issues wasn't on the API but in my code base. Thx for the update


TAJO-1892: Remove '_' as an identifier

Use of '_' as an identifier might not be supported in releases after java se 8.
so, we must check code in whole project.

@dkhwangbo Thank you for your work. But, asm module is a thirdparty package. So, we don't need to touch this source code. Instead, we should keep asm package using 1.7. For it, I'll add the following configuration in #778.
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
          <source>1.7</source>
          <target>1.7</target>
        </configuration>

Could you close this ticket?

@hyunsik Thanks for your reply. I act on your comment.


How to show "the label GeoJSON shapes (pink)" on output .tiff? How to apply masking to the data, as on lines 113-120 before the join?

Hi,
I have accepted your suggestions on https://github.com/locationtech/rasterframes/issues/539, and modified the codes of "supervised machine learning", however my output ".tiff" is a little difference from yours on "https://github.com/locationtech/rasterframes/issues/539".
Moreover, I have uploaded my output ".tiff" on my repo, in comparison with the output result on "https://github.com/locationtech/rasterframes/issues/539", which is here.

I feel the difference with the above two ".tiff" show is mine lost the "the label GeoJSON shapes (pink)". As on "https://github.com/locationtech/rasterframes/issues/539", you say that "A further refinement would be to apply masking to the data, as on lines 113-120 before the join.", but I am so confused about how to modify the codes?
So, could you pls give me some suggestions? Thanks!

The image with the pink GeoJSON shapes is simply showing the GeoJSON and the GeoTIFF together in QGIS.   The GeoTiff i wrote out is attached here: unsupervised.zip

The image with the pink GeoJSON shapes is simply showing the GeoJSON and the GeoTIFF together in QGIS.   The GeoTiff i wrote out is attached here: unsupervised.zip


Read Class with Word and String

Hello,
I have created a class with some words, real, and dwords and a string.
I try to read a class see picture for definitions
All numeric values are correct but the string remains null on read
Can anybody help?

I think you have to read the string as an array of bytes and then convert it. In the last version it's possible to read arrays from ReadClass.


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Codecov Report

Merging #65 into master will increase coverage by 2.39%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #65      +/-   ##
==========================================
+ Coverage   31.32%   33.72%   +2.39%
==========================================
  Files           1        1
  Lines          83       86       +3
  Branches        8        8
==========================================
+ Hits           26       29       +3
  Misses         57       57

Impacted Files
Coverage Δ

src/module.js
33.72% <0%> (+2.39%)
: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 d56189c...6892079. Read the comment docs.


Map between AWS profiles and browser profiles

I'm a bit bewildered by your docs https://docs.commonfate.io/granted/configuration/#using-specific-browser-profiles and SSOBrowserLaunchTemplate config
Be good to please have bash completion!
❯ granted completion -s bash
[i] We don't have completion support for bash yet, check out our docs to find out how to let us know you want this feature https://granted.dev/autocompletion

I wrote a blog about how I'm using granted currently: https://dabase.com/blog/2024/aws-sso/
My expectation is that the config is something more sane like:
[ProfileMapping]
  "Admin-123" = "Profile 4"
  "Admin-321" = "Profile 12"

Please tell me there is a simpler way. Thank you!

Thankyou for sharing the blog post @kaihendry! And fair point on the docs for this, it seems like we can make this clearer.
Profile mapping isn't supported but we'd like to add it, would the solution proposed in #771 work for you?

Oh yeah, https://github.com/common-fate/granted/issues/771 looks good!


Register a mime type for ModSecurity audit log format with IANA

MODSEC-73: I'd like to get a mime type registered w/IANA for the ModSecurity audit log format.
http://www.iana.org/assignments/media-types/
Perhaps: {{application/vnd.breach.modsecurity.auditlog}}

Since the audit are JSON, such registration is no longer needed.


Update metadata: oxygendioxide.Deepvocal-Hitsuboku-Kumi-CHN-dv1 version 1.1.0

Description

Add "Boxstar.DeepVocal" as PackageDependencies
Resolve #133393

Checks

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-09 07:50:03.168 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000 2024-01-09 07:50:03.169 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFA5341A465: (caller: 00007FFA5341AD01) Exception(1) tid(18f8) 80190193 Forbidden (403). 2024-01-09 07:52:51.477 [FAIL] Installer failed security check. Url: https://github.com/oxygen-dioxide/hitsuboku-kumi-chn-deepvocal/releases/download/v1.1.0/Hitsuboku-Kumi-Chinese-deepvocal-1.1.0-dvtb1.exe Result: 0x80004005

(Automated response - build 541.)

Hi @Dragon1573,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.
(Automated response - build 541.)

Try to validate the manifest in GitHub Workflows. It's able to install unattendedly. See Dragon1573/winget-test Validation Pipeline #7

/AzurePipelines run

Automatic Validation ended with:

Installation failed with exit code -1978335187 2024-01-10 09:18:12.022 [CORE] DeliveryOptimization error: 0x80190193, extended error: 0x00000000 2024-01-10 09:18:12.023 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!00007FFB6DAFA465: (caller: 00007FFB6DAFAD01) Exception(1) tid(12e4) 80190193 Forbidden (403). 2024-01-10 09:20:34.697 [FAIL] Installer failed security check. Url: https://github.com/oxygen-dioxide/hitsuboku-kumi-chn-deepvocal/releases/download/v1.1.0/Hitsuboku-Kumi-Chinese-deepvocal-1.1.0-dvtb1.exe Result: 0x80004005

(Automated response - build 549.)

It's wierd ... 😕
How previous version of the manifests passed the pipeline and have been approved? I can't get it ...

Related https://github.com/microsoft/winget-pkgs/pull/115971

Due to current state of this pull request, both moderators, contributors and I can't handle failures in Azure Pipelines.
This pull request is labeled with https://github.com/microsoft/winget-pkgs/labels/Blocking-Issue and https://github.com/microsoft/winget-pkgs/labels/Validation-Defender-Error, so maybe it's time to stop investigating on this problem and close the pull request without being merged.


#57: separate format in displayFormat and returnFormat (closes #57)

:+1: looks good, but consider this is the first time I read any of the lines changed here


Add instructions for building CLI executable

Related: https://github.com/google/prefab/issues/60

/gcbrun


Override TableRow onClick() when running onClick() for button in TableCell

Hey guys,
I have a Table where each row has an onClick() event. Each row also contains a button that has a seperate onClick() event. I have noticed that if I click on the button, both the onClick() events are executed. Is there a way to only run the button's onClick when its clicked?
Thank you.

@sandeshakya  Please provide a full reproduction test case. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!

@eps1lon . I've made a quick example here. https://codesandbox.io/s/m3qlylm9qj. Just some console logs show that clicking the button runs the button's event handler first and then the row's event handler. I want only the button's event handler to run.
Thank you.

Alright, I figured it out guys. Adding an <event>.stopPropagation() fixes the issue. lol.
Thank you.


pam_ibmacf Handle blank serial number

This enhances the pam_ibmacf module authentication function to recognize a serial number of 7 blanks as an UNSET serial number.
Tested: Partially
Tested with an empty serial number and non-blank serial number.
Not tested with the 7-blanks serial number.
Signed-off-by: Joseph Reynolds<EMAIL_ADDRESS>

are you wanting to check for exactly 7 whitespace characters or  all (0 to n) characters are whitespace?

What I meant by that question is could you have say 3-blanks and nothing else? Or will serial number always be 7 characters?

Received verbal confirmation (SoS) that serial number will be --> 7 <-- blanks.


Change XML API URL

While looking at https://github.com/hobbyquaker/XML-API/blob/master/README.md#use, I think this should be changed.
I am completely new to home-assistant and homematic, so sorry if I might be wrong.

What this article refers to is something different than the XML-RPC API. So the basic functionality is not related to this.
What we do with the XML-API (addon) is fetching the device names from the CCU. That's only optional though, and I actually don't think anybody uses the XML-API for that. If you can use the addon, then you have a CCU. And with a CCU you always can use the JSON-RPC API, which is supported as well.
The API-URL in the link you have posted indeed is different than the one we have implemented. It was like it is in the current code once. If they have changed it it could be changed in pyhomematic as well. But then we would need to support two possible endpoints, and that only for resolving names, which can be done via JSON-RPC already. So if they really broke the API-URL I want to just leave it as it is. It's not worth the effort for a useless (duplicate) function.


[#167641844] Add OpenAPI specification file

This PR aims to add to the repository an OpenAPI specification file to describe the endpoints available for the client

Affected stories

🌟 #167641844: Creazione contratto OpenAPI fra backend e frontend

  Generated by :no_entry_sign: dangerJS against 6b845342dd56cb7ad76028962e2229cdd9762048


MA-1615: analytics time utils

Summary
https://konghq.atlassian.net/browse/MA-1615
Konnect Deploy Preview: https://pr-4927--khcp-ui.cloud-preview.konghq.tech/
(for PR pulling in this temp package: https://github.com/Kong/khcp-ui/pull/4927)
PR Checklist

[ ] Naming & Structure: the files and package structure use the conventions outlined in the Creating a Package docs.
[ ] Tests pass: check the output of all package unit and/or component tests.

[ ] If this PR is the result of a bug, test coverage was added accordingly.

[ ] Functional: all changes do not break existing APIs, but if so, a BREAKING CHANGE commit is in place to bump the major version.
[ ] Conventional Commits all commits follow the conventional commit standards outlined in the main README.
[ ] Docs: includes a technically accurate README, and the docs have been updated accordingly based on the changes in this PR.

@adamdehaven Updated the docs structure to contain 4 top level files, instead of one. Figured it was easier to maintain this way:

My only concern here is the maintenance of the docs as the package changes, e.g. if someone makes updates to all of the underlying types but doesn't take the time to update these files accordingly.

May I add typedoc as a peer dependency to this repo?

Question: does it require any sort of config, or you just run it and it works in your package? I have a couple ideas, but maybe we try it out in a separate PR?

Yup, separate PR please :)
https://konghq.atlassian.net/browse/MA-1623

@adamdehaven added what you suggested. Works like a charm.

@adamdehaven added Documentation section to main README:


enable scorecard to override image pull policy

Feature Request
in scorecard today, IfNotpresent is the default pull policy for test images, it would be useful to let users override this within the scorecard config.yaml file to specify for example a pull policy of Always.
https://github.com/operator-framework/operator-sdk/blob/master/internal/scorecard/testpod.go#L54
Describe the solution you'd like.
retain the default perhaps, but allow this value to be overrode within the config.yaml
something like this:
kind: Configuration
apiversion: scorecard.operatorframework.io/v1alpha3
metadata:
  name: config
stages:
- tests:
  **- imagePullPolicy:  Always**
  - image: quay.io/operator-framework/tekton-scorecard-image:dev
    entrypoint:
    - tekton-scorecard-tests
    - customtest1
    labels:
      suite: tekton
      test: customtest1

@jmccormick2001, @theishshah and I think it would be a good idea to switch the default to "Always" to avoid potential bugs if the user is unaware of caching, on top of adding a configurable policy. Thoughts?
/assign @theishshah

@jmccormick2001, @theishshah and I think it would be a good idea to switch the default to "Always" to avoid potential bugs if the user is unaware of caching, on top of adding a configurable policy. Thoughts?
/assign @theishshah

one thing to note here, if you have say 10 tests, and an imagePullPolicy of Always, it will mean the test image will get pulled down 10 times as each test Pod is created...so, this default choice might impact runtime, something to be aware of.  As long as the end user can override the default to something other than Always, they can get the effect they want, but its worth noting I think as to the impact of switching to Always as the default.

one thing to note here, if you have say 10 tests, and an imagePullPolicy of Always, it will mean the test image will get pulled down 10 times as each test Pod is created...so, this default choice might impact runtime, something to be aware of.  As long as the end user can override the default to something other than Always, they can get the effect they want, but its worth noting I think as to the impact of switching to Always as the default.

Looks like the PR was merged so I'm gonna close this.

This was not actually fixed, see https://github.com/operator-framework/operator-sdk/pull/4762#discussion_r616041362

Blocked by https://github.com/operator-framework/operator-sdk/pull/5191

Pushing this ticket out by 1 release. Needs further discussion as our KIND in CI does not support the ability to drop in "Always" as the pull policy - regardless of busybox/ubi. If we decide we want to ship to users with "Always" a configuration path needs to be built to allow a modified version to be run in CI KIND environments.

PR #5054 was an attempt at the drop-in replacement, I will work on the configuration path model on this branch for those interested.


[reboot] button: border-radius: 0; destroys native styling

https://github.com/twbs/bootstrap/blob/d79ffeceeaef6c829dee1bd4bc87bd8febae243a/scss/_reboot.scss#L401-L407
messing with border* (and sometimes background*) properties of form controls usually causes them to become un-styled. the above code which fixes a minor annoyance in macOS causes far bigger problems in at least Firefox and Chrome on Windows and Chrome on Android. i've had to work around this by adding button {border-radius: revert} to undo the damage, but obviously this is not an ideal situation.
still scratching my head how this made it past QA ¯\(ツ)/¯
repro: https://jsfiddle.net/hLuj1xp4/
Windows 10, Firefox:

Windows 10, Chrome:

Android 7.1, Chrome:

With Bootstrap 4 you can use the btn and rounded classes, which works on all supported browsers:
<button class="btn btn-primary rounded-0">Button</button>
https://getbootstrap.com/docs/4.5/utilities/borders/#border-radius

the only part of bootstrap which i use is reboot (as a css reset), so that's not gonna work. i have no issues with adding the revert rule in my code. my point is that border-radius: 0 needs to move out of reboot and into perhaps the base .btn class.

Reboot intentionally resets many elements to a preferred styling ahead of Bootstrap's components, layout, and more. I don't see a reason to remove this at this time.

Thoughts @twbs/css-review?

Might we only drop it when $enable-rounded is false—like we do for text-decoration on links?

i'm split on this. can see the rationale that reset should not change too much of the stuff outside of bootstrap-specific classes. but then again, it is more a normalisation than a simple reset. would also say that it's rare that designers actually want the platform/browser specific styles, unless they're very specifically aiming to blend in/make it look pseudo-native (though browsers themselves don't always adhere to platform conventions themselves, so they get weird results either way).
i'd say since reset has always done more than merely reset/paper over some very odd quirks, and instead sets a baseline level of (idiosyncratic in their own right) styles, we should probably leave it as is now. and not switch it based on $enable-rounded either, as the jump from "yes i want round corners" to "now the corners are not round, and OMG what's that windows 95 looking chunky button with giant 3D bevel?" is a bit too big.

another option is to set some minimal additional border and background properties that are at least less windows 95 and also more normalized than simply allowing the non-uniform uncontrolled uglification to take place.

Does adding border: 1px solid (without a color) solve the issue enough? I’d prefer not to add too many extra properties since we have our .btn styles.

Does adding border: 1px solid (without a color) solve the issue enough? I’d prefer not to add too many extra properties since we have our .btn styles.

Closing as a won’t fix for now.


Create alyxclocknw.app.js

Hi! I noticed you added the different files for the app in different pull requests. Could you add all files to this, your patch-1 branch, so they show up on this PR together? Please say if you want some help :)

Hi again @ChameleonNinja I'll close this now. Please feel free to open a new PR when you want to contribute the app.


[Task]: Add Firefly (desktop) to Microsoft store

Task description
We would like to add firefly to the Microsoft app store, so that we can improve the security of the downloads.
Requirements
// TODO
Acceptance criteria
Desktop app is downloadable from the app store, and we can easily manage future releases.
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Electron docs: Windows Store Guide
https://www.electronjs.org/docs/latest/tutorial/windows-store-guide
Microsoft Docs: Publish Windows apps and games
https://docs.microsoft.com/en-us/windows/uwp/publish/


24.01 two error messages appear again

24.01 has same issue as previous 23.11:
https://github.com/MediaArea/MediaInfo/issues/782
23.11.1 fixed it

We forgot to merge https://github.com/MediaArea/MediaInfo/pull/783 😨🤦♀.

v24.01.1 released.


new package: libconfig 1.7.2

Description of package
Checklist

[x] Latest upstream version.
[x] I agree to maintain this package (required).
[x] I agree to notify KISS if I can no longer maintain this package (required).

ready


Shortcut to move focus to commit message input

I've been playing around with the extension to find my optimal workflow. First, I switched to a global shortcut to open quickstage so that I don't need extra keypresses to focus the git sidebar.
Once I've staged the relevant files, my next step is always to write a commit message. I would love to have a shortcut that was active when QuickStageVisible that would show scm view if hidden and focus on the commit message input. (I have a minimalist setup that only shows one sidebar view at a time, and with my global shortcut, there's no need for scm to be visible in order to stage files with quickStage.)
For what it's worth, I believe the tool you're building should be native functionality!

Thank you! I also agree that the SCM sidebar should pretty much have this type of keyboard functionality by default.
This feature should be simple enough to add, I already had it focus the SCM view in a previous version, but I like the idea of having a dedicated shortcut for it. I have the options in the list for stage all and unstage all that can be run by selecting them with (space) or (enter) OR by pressing the keybinding. Do you think it would be worth having a similar item for the commit message? or just the keybinding? I personally press the keybinding more often, but i think it's nice to have that visual reminder of what the keybinding is.
cmd+c or cmd+g what do you think? lol

So i added a few new features with this most recent update 0.3.3
i swapped enter with space as you suggested. so enter now stages the files and space will diff the file.
I added some more user customizable settings, trying to fit as many use cases as i could.
QuickStage will now focus the SCM view automatically on exit, you can turn this off in the settings if you don't like it.
there are also 2 settings for the diff previews
I think the behavior you are looking for is
"quickStage.previewDiff": true,
"quickStage.closePreviewOnExit: false,
"quickStage.focusScmSidebarOnExit: false,

I think this is what you were wanting, but maybe try out the autoFocus and see if you like it without using the extra keybinding to open SCM.
My user story is:

open QuickStage
preview a file and stage it
press 'Esc' and move to SCM to write commit message.
The preview Diff that was open closes, leaving my workspace uncluttered.

you can read more on these in the readme, but you'll probably also want to set "scm.autoReveal": false, to make sure the SCM view always focuses the commit box!

So i actually had a bit more of a think on this, and I removed the focus SCM keybinding from the extension.
Simply because it already exists. the default keybinding to focus the SCM view is cmd+ctrl+g and you can change it to whatever you want.
  {
    "key": "your+keybinding",
    "command": "workbench.view.scm",
    "when": "workbench.scm.active"
  },

this along with "scm.autoReveal": false, will give you the functionality you were looking for here. and it will open the commit message at any time whether quickStage is open or not.
if you want it to only work when quickStage is open you can use this when statement.
"when": "workbench.scm.active && QuickStageVisible",
hope that helps!

Looking great! Thanks a lot for taking my suggestion about enter vs space. Is quickStage.focusScmSidebarOnExit still an active setting? It gets greyed out in my settings.json as if it's not recognized. I do have a keybinding set for workbench.view.scm.
With regards to focusing the commit input, there's a weird native quirk that is also present when using quickStage. When I use my workbench.view.scm or press Esc from inside quickStage, there are times that commit input is focused and other times it's not. Specifically, it looks like if the most recent SCM focus is on an element within the scm view (such as on a file like in this first screenshot), the focus returns to that item by the keybinding or Esc:

However, if the most recent focus is on the view as a whole (as in this 2nd screenshot), the commit input is focused on keypress:

Actually, it appears that the focus is passed to each file in scm view when traversing files in quickStage, so the commit input is not focused if quickStage has been utilized. Hopefully it's an easy fix. And no worries if not! Let me know if you'd like me to create a separate issue. For the record, here are the quickStage settings I've set (the 2nd of which does not appear to be recognized):
"quickStage.previewDiff": true,
"quickStage.closePreviewOnExit": false

I have 0.3.5 installed on my machine, the settings should all be there. does focusScmSidebarOnExit appear in the settings GUI?

i believe the behavior you are experiencing is "scm.autoReveal" this is what is moving the focus to the specific file.
set this to false and see if it fixes it!

just a heads up i added a global keybinding for Quick Stage in 0.3.7 so you may need to change it in your settings again to make sure it doesn't conflict with the keybinding you already set.

Here's what I'm getting when exiting quickStage with Escape on v0.3.7 with "scm.autoReveal": false. You can also see my settings at the end of the clip:
Screen Recording 2024-11-06 at 11.42.53 PM.webm
I'm only seeing one quickStage setting in the GUI:

The 2 keybindings don't appear to have a different behavior, but I'm actually hoping not to rely on it anyway since it doesn't consistently focus the commit message.

here's a video of it focusing the input box. I commented out all of my settings and only set "scm.autoReveal": false
seems to be working for me here.
https://github.com/user-attachments/assets/4e4cefff-9a6b-4bf9-b931-c996d899a472

ok cool! glad it is working.
I see the behavior you are talking about. unfortunately there is not a command that allows us to directly focus the commit input box, so we can only open the view and use the native functionality to direct where the focus goes.
On my machine it actually only seems to focus back to the list of changes if i open QuickStage, DO NOTHING, and then close it. If i stage a file using Quick Stage, then close it, it focuses the input box correctly even if i was just previously focused on the list of changes.
i'm gonna go ahead and close this as it seem like the functionality is about as good as we can get it, and it works as intended most of the time. please let me know if you have more issues or suggestions! i appreciate the help with this!


Adding a license?

Hey, I noticed that there is no license, could you please add a license? More explicitly, are we free to redistribute your dataset? Thanks!

Thank you for your interest in our work. We have added a MIT license in the repository.


fix(ngMock): Change ErrorAddingDeclarationLocationStack prototype

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
fix to angular-mocks for ErrorAddingDeclarationLocationStack error to change its prototype to Error.prototype
What is the current behavior? (You can also link to an open issue here)
Testing frameworks and other libraries interacting with angular cannot correctly detect this error with instanceof
What is the new behavior (if this is a feature change)?
This Error is correctly inherited from Error. ErrorAddingDeclarationLocationStack instanceof Error === true.
Does this PR introduce a breaking change?
No, in fact it only changes one line.
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[X] Tests for the changes have been added (for bug fixes / features)

Other information:
Apologies for ridiculous branch name. I hope this was all done correctly, I am still new to git/GitHub :octocat:
change prototype to Error.prototype so test frameworks can catch it properly
#13821

Fix for issue #13821

@peabnuts123 Did you ever get around to updating this PR?

Unfortunately I've been pretty busy and have been unable to update this. I still intend to, as this fix is something I need in my project. Currently just using my own fork in our build...

I've changed the unit test to utilise the real Jasmine toThrowError as mentioned in the previous comments. Apologies it took so long. All the builds work on my end, and I've confirmed everything works against master branch AND is still a necessary change.
The Travis build appears to have failed unrelated to anything I've changed? Can this be confirmed / re-run?

Travis is green now :+1:


Update for RFC 9457

There's an update to the Api-Problem spec: https://datatracker.ietf.org/doc/rfc9457/
See if there are any changes needed, or at least update the README. 😄

Done in the latest release.


Fix typo in perun_app_channels.md

accomodate -> accommodate

 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.