create template-info.yaml

As suggested here and in support of stack pull request #1988.

Shouldn't the descriptions be part of the template itself? This seems like recipe for confusion, having to do the mapping manually.

It would be nice to have the descriptions as part of the template files themselves, but would that not require downloading and parsing every template file, every time a user runs stack templates? Granted, they're small files, but I don't see that as being very desirable.

I guess I assumed stack already did download all the templates anyway. I don't actually know either way.

Yeah, cloning the template repo would be sensible for many reasons - https://github.com/commercialhaskell/stack/issues/1595.
I don't see much of a problem with having a metadata file like this, though.  It might make things clearer if something like template inheritance gets added https://github.com/commercialhaskell/stack/issues/1994

@mgsloan You have a much better sense of what's good in this case. I just like to keep things DRY and having to join these two "tables" adds complexity.

@3noch Yeah, the main issue with adding it to the template itself is that it'd be best to have compatibility with older stack versions.  So either way, we'll need to add new files.  We can either have a template-info file like this, or add a description file per template.

it'd be best to have compatibility with older stack versions.

@mgsloan For how young stack is, this requirement seems a bit hard to believe (again, you know better than I). I would imagine that stack'ss adoption rate is very good too.

We can't just silently make stack new fail for old stack versions.  There is no "template repo version check".  So our only option would be to make a new repo or a subdir or something.

There is no "template repo version check". So our only option would be to make a new repo or a subdir or something.

Hmm...perhaps that's the main problem?

Yes, something like that would be good for our various sources of data.  PRs appreciated

As discussed here, testing will now fail if there is any discrepancy between templates listed in template-info.yaml and the actual templates present in the repository.

@narrative Now that is a good idea!

Oops, forgot to merge this after the stack changes got merged.


Important question of Trie

Add 4 important questions of the trie data structure. (#85 )
Please add my file to your repository with the label hacktoberfest.

Okay Sir.

Our Team Found that you haven't followed.
Follow me on github.
Before 12PM if not found you labelled as SPAM


addLabel() doesn't add $this->getCharsetString()

Is there a particular reason why encoding isn't added to LABEL? On Windows this causes Problems with Umlauts.

Hi there, nice catch.
I just added it for you.

New release https://github.com/jeroendesloovere/vcard/releases/tag/1.7.3

:heart: Thank you!


Custom DNS API for txt record results in "No value for the record provided"

The context for this is im trying to setup acme on pfsense to create a wildcard cert using the DNS-MailinaBox method, but its failing. But that is just the context of where im hitting this issue i understand that is external to power-mailinabox
However, in the Custom DNS panel, at the bottom it shows an example of how this should work, where a command such as curl -X POST --user "username@mydomain.tld:my awesome passphrase" -d "some text here" https://box.mydomain.tld/admin/dns/custom/_subdomain.mydomain.tld/txt should result in the text record created. But instead i get the error message No value for the record provided.
This is the same error message i get from acme when i try to use the staging account to create a test wildcard certificate. Again i know that part is out of scope but it shows im getting the same error with two different methods. The log shows it hitting the same endpoint.
[Sat Mar 25 23:33:46 AEST 2023] Adding txt value: somelongstring for domain:  _acme-challenge.mydomain.tld
[Sat Mar 25 23:33:46 AEST 2023] Using miab challange add
[Sat Mar 25 23:33:46 AEST 2023]<EMAIL_ADDRESS>[Sat Mar 25 23:33:46 AEST 2023] MIAB_Password='my awesome passphrase'
[Sat Mar 25 23:33:46 AEST 2023] MIAB_Server='box.mydomain.tld'
[Sat Mar 25 23:33:46 AEST 2023] _api_path='zones'
[Sat Mar 25 23:33:46 AEST 2023] _url='https://box.mydomain.tld/admin/dns/zones'
[Sat Mar 25 23:33:46 AEST 2023] _credentails='somelongstring'
[Sat Mar 25 23:33:46 AEST 2023] _httpmethod='GET'
[Sat Mar 25 23:33:46 AEST 2023] GET
[Sat Mar 25 23:33:46 AEST 2023] url='https://box.pavocracy.dev/admin/dns/zones'
[Sat Mar 25 23:33:47 AEST 2023] ret='0'
[Sat Mar 25 23:33:47 AEST 2023] response='["mydomain.tld"]'
[Sat Mar 25 23:33:47 AEST 2023] _test_domain='mydomain.tld'
[Sat Mar 25 23:33:47 AEST 2023] _sub_domain='_acme-challenge'
[Sat Mar 25 23:33:47 AEST 2023] _api_path='custom/_acme-challenge.mydomain.tld/txt'
[Sat Mar 25 23:33:47 AEST 2023] _url='https://box.mydomain.tld/admin/dns/custom/_acme-challenge.mydomain.tld/txt'
[Sat Mar 25 23:33:47 AEST 2023] _credentails='somelongstring'
[Sat Mar 25 23:33:47 AEST 2023] _httpmethod='POST'
[Sat Mar 25 23:33:47 AEST 2023] POST
[Sat Mar 25 23:33:47 AEST 2023] _post_url='https://box.mydomain.tld/admin/dns/custom/_acme-challenge.mydomain.tld/txt'
[Sat Mar 25 23:33:47 AEST 2023] body='somelongstring'
[Sat Mar 25 23:33:48 AEST 2023] _ret='0'
[Sat Mar 25 23:33:48 AEST 2023] response='No value for the record provided.'

This is a brand new debian 11 VPS and is otherwise working where i can send and receive emails and access the mail and admin panels, and manually create DNS entrys. FWIW my domain is with godaddy and i changed the default nameservers to be ns1.box.mydomain.tld and ns2.box.mydomain.tld that both resolve to the public IP address of my VPS, so all the dns entries for my domain should be coming from the maib server.
Any help with this issue would be greatly appreciated.

Do i need to setup an alias for this subdomain for it to work? I may just be confused how these custom domain works with miab. What im trying to do is use custom domains to forward to an nginx server i have with other services running, since i gave up that ability at a DNS level because i switched my name servers to be using the dns on this box.
Do i need an alias for every subdomain i want to setup with miab?

https://discourse.mailinabox.email/t/solved-but-a-bug-miab-dns-added-new-custom-dns-did-not-work/5550
Is this related at all? Is this an actual bug hanging around? What is the correct way to setup custom DNS entries on a MIAB server? As i said all i want to do is create a sub domain using an CNAME record that points to my other domains (eg homelab.mydomain.tld) and a txt record for the acme challenges to work to get certificates from lets encrypt for that homelab domain from external to the MIAB.

Hello!
I don't think this is a bug, rather than a feature I've introduced a few releases ago (#28) made the documentation incorrect :sweat_smile:
Since curl submits POST data as a x-www-form-urlencoded you'll want to prepend value= before the actual value you want (this is valid for all record types!)
So for your case:
curl -X POST --user "username@mydomain.tld:my awesome passphrase" -d "value=some text here" https://box.mydomain.tld/admin/dns/custom/_subdomain.mydomain.tld/txt

Thanks for the clarification. Would be awesome to get the docs updated at some stage. But thanks for posting the correct method to solve my issues :)

@ddavness, can we update the documentation to reflect this please?

Also, would you mind clarifying for me, @ddavness, please?  It looks like the API to add a TXT record in Power-Mailinabox now differs from that for Mailinabox?  I have updated the acme.sh project's dns_miab.sh file to reflect this change, but now it seems that MIAB users are getting an error.
If this is indeed only a change for P-MIAB, then I will have to create a separate dns update script for Power-Mailinabox in acme.sh.


[cxx-interop] Instantiate templated operator== for iterator types

[cxx-interop] Instantiate templated operator== for iterator types
C++ iterator types are often templated, and sometimes declare operator== as a non-member templated function. In libc++, an example of this is __wrap_iter which is used as an iterator type for std::vector and std::string.
We don't currently import templated non-member operators into Swift, however, we still want to support common C++ iterator patterns.
This change adds logic to instantiate templated non-member operator== for types that define iterator_category and are therefore likely to be valid iterator types.
rdar://97915515

(not going to merge this right now, just assessing the fallout)

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test macOS


feat: gpg handling composite version of action

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Slight performance overhead can be saved by using Random.nextDouble i…

…nstead of Math.random for any instance of Math.random.
Description
Though this is not the only instance of Math.random in the codebase, any instance of it can be replaced by Random.nextDouble. Though not performance critical, this can reduce performance overhead when done across all instances of Math.random.

Added import for java.util.Random
Replaced the instance of Math.random with Random.nextDouble

I have a list of every applicable Math.random -> Random.nextDouble instance and will share such list if it is okay to move forward with such modifications.
Motivation and Context
Though not performance critical, this can reduce performance overhead when done across all instances of Math.random.
Types of changes

Reduced overhead in performance

Checklist:

[ x ] My code follows the code style of this project.
[ x ] I have updated the documentation accordingly. (Documentation did need to be updated)

Codecov Report

Merging #457 into trunk will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##              trunk     #457      +/-   ##
============================================
+ Coverage     61.19%   61.19%   +<.01%
- Complexity    11462    11463       +1
============================================
  Files          1220     1220
  Lines         77974    77975       +1
  Branches       7527     7527
============================================
+ Hits          47717    47719       +2
+ Misses        27556    27555       -1
  Partials       2701     2701

Impacted Files
Coverage Δ
Complexity Δ

...s/org/apache/jmeter/timers/PoissonRandomTimer.java
73.68% <100%> (+0.71%)
9 <0> (ø)
:arrow_down:

...c/core/org/apache/jmeter/reporters/Summariser.java
86.25% <0%> (+0.76%)
19% <0%> (+1%)
: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 f69f66e...f4e1cf9. Read the comment docs.

Thanks for your contribution.
I have used ThreadLocalRandom as it should be even better performing, when multiple threads are using the timer.


Routers: fix lix to github source code

Hi, this PR fix some broken links to github source code in the routers documentation.
Here is link to test:
https://deploy-preview-359--react-navigation.netlify.com/docs/en/routers.html
https://deploy-preview-359--react-navigation.netlify.com/docs/en/2.x/routers.html
https://deploy-preview-359--react-navigation.netlify.com/docs/en/1.x/routers.html

thanks!


Documentation doesn't make it clear there could be a disconnect between config.tab.item 'choice_displayed' and 'valid_entries'

Fixed in README


Support new Set(...) on Android (J2V8)

This happens when using JavaScript new Set([]) from inside a manticore engine in Java.
07-15 11:18:04.435 7005-7005/com.paypal.merchant.client.debug E/RetailSDK: Internal Error
                                                                           java.util.concurrent.ExecutionException: undefined:12443: ReferenceError: Set is not defined
                                                                                var members = new Set(g.members);
                                                                                ^
                                                                           ReferenceError: Set is not defined

Babel does not affect new Set() when converting from ES6, so the conclusion is that J2V8 doesn't support Set.  The native Objc engine seems to support Set.

Making a note here to look into the polyfill for that platform


Compiling ClientApi.ts fails due to include of unavailalble class DefaultService

Description
When upgrading from 0.45.1 to 0.46.3 I encountered the following compile error:
.openapi-typescript-codegen/ClientApi.ts:6:10 - error TS2305: Module '"./services.gen"' has no exported member 'DefaultService'.

6 import { DefaultService } from './services.gen';
           ~~~~~~~~~~~~~~

According to the migration docs it should be like:
import * as DefaultService from './services.gen';

Or do I get something wrong ?
Note: Sticking with asClass works fine.
OpenAPI specification (optional)
No response
Configuration
No response
System information (optional)
No response

@sepek sounds like you figured it out? Is there anything that needs to be fixed?

@mrlubos thanks for the feedback!
Sorry for not being clear about my point. This file is generated by @hey-api/openapi-ts and so I consider it a bug if it produces code which results in compile errors

This problem got introduced in 0.46.0

I hit this on upgrading from openapi. The default behaviour (without setting a configuration option) should probably not be to generate code that does not compile..

Had to go from 0.48 to 0.45 as a temporary solution.

@anatolii-yemets does it not work with services.asClass = true?

@mrlubos I would respectfully suggest this bug is fixed sooner rather than later. Generating code that fails to compile gives a bad impression of an otherwise good tool. If asClass is the solution, it should be on by default and the other mode should be deprecated, to ensure users do not hit this problem.
We have a workaround, but many users will probably just give up and look for some other library if "it generates code that doesn't compile" is their first impression.

@hallvors As far as I can tell, this is when using the (deprecated) name parameter? Assuming yes, it's not documented anywhere so I'd expect you to be upgrading from a prior version. And in that case, there are the migration docs. Maybe it should be clearer there? My intent is not to support name. I'm curious what use cases there are that prevent people from moving away from that setting?

@mrlubos first of all: Praise the migthy developers which bring us this nify tool. Keep up the excellent work :)
Two cents for potential improvements:
For me it was not clear from the migration instructions of 0.46 that the usage should be adpoted for me it sounded more like another way to use the library which is now the default.
Also it was not clear to me that the --name paramater is not supposed to be used as it's at least documented with --help.

Sorry all, just revisiting this. Did this ever get resolved with any of the latest releases? Still an issue?

Sorry all, just revisiting this. Did this ever get resolved with any of the latest releases? Still an issue?

Uh fancy, indeed it did! I followed all the changes but didn't notice that one. Thanks for coming back to it!
What I did:

Remove asClass definition from my config
Rebuild the API code
Run the app
Be happy

Thank you very much!


[IO] initial commit

Pull Request Test Coverage Report for Build 572176142

0 of 139 (0.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-5.7%) to 94.307%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Psl/IO/Exception/BlockingException.php
0
1
0.0%

src/Psl/IO/Exception/ExceptionInterface.php
0
1
0.0%

src/Psl/IO/error.php
0
3
0.0%

src/Psl/IO/input.php
0
3
0.0%

src/Psl/IO/output.php
0
3
0.0%

src/Psl/IO/Internal/open.php
0
5
0.0%

src/Psl/IO/Internal/ResourceHandle.php
0
58
0.0%

src/Psl/IO/Reader.php
0
65
0.0%

Totals

Change from base Build 571224268:
-5.7%

Covered Lines:
2319

Relevant Lines:
2459

💛  - Coveralls


Prebuilt mozjpeg binary doesn't work with 7.0.0 on Ubuntu

Installing<EMAIL_ADDRESS>logs mozjpeg pre-build test passed successfully, using<EMAIL_ADDRESS>logs:
  ⚠ The `/.../node_modules/mozjpeg/vendor/cjpeg` binary doesn't seem to work correctly
  ⚠ mozjpeg pre-build test failed
  ℹ compiling from source
  ✖ Error: autoreconf -fiv && ./configure --disable-shared --disable-dependency-tracking --with-jpeg8  --prefix="/.../node_modules/mozjpeg/vendor" --bindir="/.../node_modules/mozjpeg/vendor" --libdir="/.../node_modules/mozjpeg/vendor" && make -j8 && make install -j8
Command failed: ./configure --disable-shared --disable-dependency-tracking --with-jpeg8  --prefix="/.../node_modules/mozjpeg/vendor" --bindir="/.../node_modules/mozjpeg/vendor" --libdir="/.../node_modules/mozjpeg/vendor"
configure: error: no nasm (Netwide Assembler) found

For any reason My ubuntu was missing some packages to compile, I firs had to add a new gpg key:
wget -qO - https://raw.githubusercontent.com/yarnpkg/releases/gh-pages/debian/pubkey.gpg | sudo apt-key add -
then sudo apt-get install  autoconf libtool pkg-config nasm build-essential
and now it compiles the module

sudo apt-get install libpng16-dev

Is the dependency upon libpng16-dev intentional or incidental?
On our build servers we cannot install libpng16-dev because libpng12-dev is already present. This is currently holding us back from upgrading packages that rely on imagemin-mozjpeg.
Does anyone have a suggestion on how to solve this? I might, for example, be able to compile libpng16-dev from source, but how can I instruct imagemin-mozjpeg to use that compiled version?
Any help would be greatly appreciated!

I'm also having same issue and can be fixed just by apt install nasm since autoconf libtool pkg-config nasm build-essential are already installed on my Ubuntu 16.04 (WSL).
><EMAIL_ADDRESS>postinstall /path/to/project/node_modules/mozjpeg
> node lib/install.js

  ⚠ The `/path/to/project/node_modules/mozjpeg/vendor/cjpeg` binary doesn't seem to work correctly
  ⚠ mozjpeg pre-build test failed
  ℹ compiling from source
  ✔ mozjpeg built successfully

Updating to<EMAIL_ADDRESS>allowed us to successfully build on our Ubuntu server. Will this be part of a version update soon?

Can confirm ~6.0.0 works for me too, ~7.0.0 binary doesn't work and I am not able to install the various build tools etc. Thanks @JimmyMultani

I think it's fixed in 8.0.0. I've tested it today, it works for me. Build fails with 6.0.0 and 7.0.0 right now but works fine in 8.0.0


Market place error in VS extension upload

Describe the bug
When uploaded on the website or from the CLI, I get this error message: The package contains an invalid VSIX manifest file. This VSIX does not apply to any product installed on this machine. The problem could be that the VSIX manifest's format is not recognized, or that the manifest has been corrupted.
I've tried with two of my extensions that worked fine just a few days ago when I last updated them.
To Reproduce
Steps to reproduce the behavior:

Upload any extension extension

@pratikgawali-msft Could you take a look at this please?

Yes, we are working to resolve the issue as quickly as we could.

The issue is resolved. Now the VS extension upload should work fine.
Thanks for reporting the issue so quickly.

What was the issue?

This is an issue in the backend, I will talk to Munish and send out analysis over email


Add support for private repos

Today I tried to backup my github staff in a personal gitea and I found your project super handy.
However I saw in the log that some of my repos were copied over and over, but those repos were missing in gitea.
It turns out that those are my private repos, so I modified your project to support them!

Love it! Thanks for your contribution!


feat(#235): Fix Code Duplication Bewtween instructions and commands

Remove code duplication beween XmlMethod#instructions() and XmlMethod#commands() methods.
Closes: #235.

History:

feat(#235): replace some instruction invokations
feat(#235): remove redundant code
feat(#235): remove one more redundant method
feat(#235): remove duplicated method
feat(#235): remove the puzzle for 235 issue
feat(#235): fix all qulice suggestions

PR-Codex overview
This PR focuses on refactoring the XML representation of bytecode instructions in the JEO library.
Detailed summary:

Renamed XmlInstruction to XmlCommand.
Updated method and variable names to be more descriptive.
Added new methods and interfaces to improve code readability and maintainability.
Updated method signatures to use XmlCommand instead of XmlInstruction.
Removed unused methods and code.
Improved comments and documentation.

The following files were skipped due to too many changes: src/main/java/org/eolang/jeo/representation/xmir/XmlMethod.java

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here


[Bug] Setting up offline hotword detection leads to unexpected results.

Whenever I run npm run setup:offline-hotword it says "Offline hotword detection installed, then it spews a big block of red text that is giving errors
Steps To Reproduce

Step 1
Run npm run setup:offline-hotword
Step 2
Wait
Step 3
It spews a large red block of text

The current behavior
it errors out after install
The expected behavior
it "just works"
Screenshot attached:

I see the same issue as well.


How to customize the theme

Make sure these boxes are checked before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[ ] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version
Expected results
Actual results
Steps to reproduce

You essentially need to fork and make your own builds.
This is a good place to start:
https://github.com/apache/incubator-superset/blob/master/superset/assets/stylesheets/less/cosmo/variables.less
We serve a display page for the theme you can use while you tweak it: /superset/theme/

@mistercrunch does it make sense to have global CSSTemplates?
We can flag a CSS template as global and load it at "superset/basic.html" so it applies always. It allows basic theming without having to maintain a separate repository.

Then at the end of the head section:
{% for entry in global_css %}
        <style>
          {{ entry }}
        </style>
    {% endfor %}

Feels like it shouldn't live in the database, it would mean an extra query to the DB all the time. The best here is probably to make your own build in your own fork. To avoid conflict you copy/paste the folder with the theme and alter the code to import that instead of the current theme.
Otherwise, and assuming you don't want to alter the Python package, maybe a new config key EXTRA_CSS_FILES = [] (would load on top of current theme), or CUSTOM_BOOTSTRAP_THEME = 'https://mydomain.com/mytheme.css' which would  prevent loading the current theme from loading and load yours?