Macros for TD

For convenience, it is proposed to add the ability to extend TD as follows:
// AppServiceProvider.php

TD::macro('bool', function () {

    $column = $this->column;

    $this->setRender(function ($datum) use ($column) {
        return view('bool',[
            'bool' => $datum->$column
        ]);
    });

    return $this;
});

// bool.blade.php

@if($bool)

@else

@endif

Usage
    /**
     * Grid View for post type.
     */
    public function grid(): array
    {
        return [
            TD::set('status')
                ->sort()
                ->bool(),
        ];
    }

Result:

This will allow for the expansion of TD by third-party packages and stimulate reuse without inheritance.

I would like to get rid of the need to specify:
$this->setRender()

Inside the handler, but at the time of execution, the $datum data is not available, it is possible, of course, to change what it would be like:
TD::macro('bool', function () {
    $this->template = 'bool';
    $this->render = \Closure;

    return $this;
});

But I do not think it is much better. If anyone has any suggestions, please feel free to.


UIL OTS > ILS

General information about the application:

To which research institute are you affiliated? one of the options should refer to Institute for Language Sciences (ILS) (replacing UiL OTS)
How is this study funded? direct government funding: replace UiL OTS by ILS
Participants
UiL OTS database > ILS database (adult and/or infant participants)
Intervention study
Specify where the data collection will take place: replace UiL OTS Labs by ILS Labs (including the Babylab)
Observational study
Specify where the data collection will take place: replace UiL OTS Labs by ILS Labs (including the Babylab)
Task-based research and interviews
Specify where the data collection will take place: replace UiL OTS Labs by ILS Labs (including the Babylab)

UiL-OTS still appears in two places:

The fixtures for institutions and such


[BUG] - Table.Body items(rows) rendering procedure in typescript cause 'No index signature'

Describe the bug
on my Next.js app using @nextui-org/react 1.0.0-beta9, I was trying to use the Table component using the Dynamic table example on NextUi website.
When I was trying to render table cells in rows at this part of the code:
const renderCell = (user: UserType, columnKey: React.Key) => {
    const cellValue = user[columnKey];
    switch (columnKey) {
       .
       .
       .
    }

Typescript complains and throws this error:
Element implicitly has an 'any' type because expression of type 'Key' can't be used to index type '<OBJECT_TYPE>'.
  No index signature with a parameter of type 'string' was found on type '<OBJECT_TYPE>'

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

create a new app with nextui-org/react and typescript installed
make a new component that uses Table
when Table.body wants to iterate over items passed to it and render Table. Row and Table.Cell, you can see the problem

Expected behavior
I expected the  Table component works without any type errors but it's not and makes complaints about types.
Screenshots or Videos

Operating System Version

OS: Windows

Browser
Chrome

Same here. Seems to make the Table control unusable in Typescript, unless I'm misunderstanding how to render dynamic table rows with this control.

@rshov
To provide a workaround that I've been using, you can explicitly cast the Key type as a key of the object in Typescript.
Example:
<Table.Body items={props.words}>
  {(w) => (
    <Table.Row key={w.id}>
      {(columnKey) => {
        return <Table.Cell>{w[columnKey as keyof typeof w]}</Table.Cell>;
      }}
    </Table.Row>
  )}
</Table.Body>

Hey please update to v2.0 https://nextui.org/blog/nextui-v2 due to v1 will not receive more updates.


Add Text-to-Speech backup if Elevenlabs fails

This is a free API that does not require a key. It uses the "Rocket" voice from TikTok

Looks and sounds great!


1

[Enter feedback here]

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

ID: 27f678d1-840c-d7d3-1e97-ca80666328c2
Version Independent ID: 2a0f90df-f8eb-d9e2-d5be-881734e72e21
Content: Create Commerce payment packaging for Finance and Operations deployment - Commerce | Dynamics 365
Content Source: articles/commerce/dev-itpro/payment-connector-package.md
Service: dynamics-365-commerce
Product: ****
Technology: ****
GitHub Login: @mugunthanm
Microsoft Alias: mumani

Thanks for responding to this topic; we appreciate your taking time to provide feedback. Unfortunately, your comment didn't come through. If you'll reenter your comment, we'll review it and act on it, if we can. Thanks again!


how to check whether a string contains some terms

I'm trying use mvel to evaluate a string contains expression

ParserContext context = ParserContext.create().stronglyTyped().withInput("$tag", String.class);
CompiledExpression expression = new ExpressionCompiler("$tag.contains('a') && !$tag.contains('b')", context).compile();
System.out.println(expression);

but, the compiledexpression was printed like this,

(null && $tag.contains('b'));

so, what should I do to check whether a string contains some terms or not? use regex pattern?

Hi firebat,  What about the scenario where one needs 'not contains'? $tag not contains 'b' would return a compilation  error? I can rewrite as !($tag contains 'b')  but life is easier if the not contains operator were available...Do you have any working examples of being able to use 'not coniains'


csharp travis failure

I do not know whether is reported anywhere yet.
partial log:
Tests run: 38, Errors: 0, Failures: 1, Inconclusive: 0, Time: 7.8991229 seconds
Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0
Errors and Failures:

Test Failure : Grpc.Core.Tests.ClientServerTest.UnknownMethodHandler
Expected: Unimplemented
But was:  Unknown

at Grpc.Core.Tests.ClientServerTest.UnknownMethodHandler () [0x00000] in :0
FAILED: Grpc.Core.Tests [ret=1, pid=8931]
FAILED: Some tests failed
travis_time:end:00f93757:start=1435100323144465590,finish=1435100357612111193,duration=34467645603

The command "./tools/run_tests/run_tests.py -l $TEST -t -j $JOBS -c $CONFIG -s 4.0" exited with 2.
Done. Your build exited with 1.

Full log: https://s3.amazonaws.com/archive.travis-ci.org/jobs/68068454/log.txt

Duplicate of https://github.com/grpc/grpc/issues/2146


[GH Actions] Update semantic versioning for Expensify.cash

Upwork posting: https://www.upwork.com/jobs/~011cb60c9e032b2c3b
If you haven’t already, check out our contributing guidelines for onboarding!

Problem
We use the following semver (semantic versioning) schema for Expensify.cash: MAJOR.MINOR.PATCH-BUILD. Right now, the bumpVersion action only ever increments the BUILD version, but we need to be able to increment other segments of the semver version, too.
Why is this important?
This is a requirement in order to deploy Expensify.cash mobile to production.
Solution
We need the following updates made to the existing bumpVersion action:

It should take a SEMVER_LEVEL input which must be one of: [MAJOR, MINOR, PATCH, BUILD]
Based on the SEMVER_LEVEL parameter, it must update the correct portion of the semver version. So if the current version were 1.0.1-444 and I execute the bumpVersion action w/ a SEMVER_LEVEL of BUILD, the new version should be 1.0.1-445.
Whenever you update a higher SEMVER_LEVEL, the lower levels should be reset to 0. For example, if the the current version were 1.0.2-444 and I execute the bumpVersion action w/ a SEMVER_LEVEL of MINOR, then the new version should be 1.1.0.
A BUILD level of 0 should not be included in the semantic version. So if the the current version were 1.0.1-444 and I execute the bumpVersion action w/ a SEMVER_LEVEL of PATCH, then the new version should be 1.0.2, not 1.0.2-0.
We also need this action to output the new version string to the workflow that executes it.
The maximum number for each SEMVER_LEVEL should be 999, and if the maximum is reached then it should automatically bump the next level up. For example, if the current version is 1.0.999 and I execute this action w/ a SEMVER_LEVEL of PATCH, then this action should update the version to 1.1.0, not 1.0.1000.
The existing functionality, which retries the npm version command in the event of a race condition/version conflict must be maintained.
Automated tests should be written to cover all the functionality of this action.

To be considered complete

Verify that all 8 of the above are satisfied
Document testing done for this action in a separate repo before we will merge a PR and QA it in Expensify.cash
Provide a set of automated tests
You must test that all build levels are updated as expected.
Verify that the action still properly handles the npm version race condition that can occur if two or more PRs are merged in quick succession. You can test this by:

Manually create a git tag in your repo for the highest existing version +1
Execute this action, and if it bumps the version to the level of the tag you created in the previous step +1, then it was a success.

Verify that the version generated by this action is successfully output to the workflow that executed it by echoing the version in the workflow.

The versioning should be maintained some where in dynamo db table or in Json file, whenever new MAJOR, MINOR, PATCH, BUILD will come the key value mapping should done and updated accordingly. with the increment. Index reset  should be applied once it will reach to 999.

The versioning should be maintained some where in dynamo db table or in Json file, whenever new MAJOR, MINOR, PATCH, BUILD will come the key value mapping should done and updated accordingly. with the increment. Index reset should be applied once it will reach to 999.

The versioning should be maintained some where in dynamo db table or in Json file

@nik0811 Thanks for your input, but first let me explain how we currently manage versions in Expensify.cash. The please re-read the issue description and provide a more detailed proposal.
The version number is stored in package.json. We use a Github Action to update the app version automatically when a pull request is merged, but before we deploy new code. So the data is stored in Github – we don't want to set up or use some external database just for the app version.
We have some custom logic to handle a race condition that can occur when two or more PRs are merged in quick succession.
However, that code currently only updates the BUILD version, and we need it updated such that it takes in a SEMVER_LEVEL and updates the MAJOR, MINOR, PATCH, or BUILD version accordingly.

Thanks for the update @roryabraham, I will look into it. Forking the repository for now.

Hi @roryabraham ,
I will extract the logic of the "bumping" out of the main function just to make things cleaner and easier to test.
I will simply increase the required level and then check if new number reaches 1000 if so increase the next one accordingly until the MAJOR since it should never get that high! =)
After this done it will be a matter of updating the newBuildNumber and running the appropriate function:
exec(`npm version ${newBuildNumber} -m "Update version to ${newBuildNumber}"`,
                            // eslint-disable-next-line no-shadow
                            (err, stdout, stderr) => {
                                console.log(stdout);
                                if (err) {
                                    console.log(stderr);
                                }
                            });

Since nothing on the current flow will really change, it should work as expected. I will write unity tests for the added functions and make the test in:

Verify that the action still properly handles the npm version race condition that can occur if two or more PRs are merged in quick succession. You can test this by:
Manually create a git tag in your repo for the highest existing version +1
Execute this action, and if it bumps the version to the level of the tag you created in the previous step +1, then it was a success.

To check if the racing condition logic is still working as expected.
Let me know your thought, I will also apply for this issue in upwork.
Thanks,

@FredericoGauz Your proposal looks good! You'll need to also ensure that you update the action metadata file to take in a SEMVER_LEVEL as input and output the new version (after it has been successfully created). You can interface with the Github Action data (inputs and outputs) using the @actions/core package that's already included. You may also find it helpful to check out the README for our Github workflows and actions.
Note: don't forget to recompile your actions using npm run gh-actions-build 😁

@roryabraham  That's great, I will start working on it right now!
OK, I will do that and build the index.js with ncc as well =)

Hi @roryabraham I hope you are having a good day. I made a pull request with the changes required. It took a little longer because it is my first work with you and as it seem to be an important issue for your team I made lots for test in my forked (and before on my cloned) repository to make sure it would work as expected.
It took a little bit of time to get used to some details of the project. I hope this is what you are looking for.
I can also see that you made some changes to the files I was supposed to update. Please let me know how you want to proceed.
Thanks,
Frederico

This issue is already resolved and thus should be closed.

Thanks @parasharrajat


SQForm Radio Buttons

Build a Radio Buttons/Group component for the SQForm library.
Here's the blueprint which is the official example from Formik Radio Group Example

:tada: This issue has been resolved in version 3.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Implement dhtcrawler.save_failed option to save failed torrents

Persisting to DB can fail due to various reasons so to make it easier to debug those allow saving failed torrents to disk for further inspection. This will make it easier to fix issues like #127 and you won't lose torrent data because once bug is fixed these could be redriven back (needs additional import support).
For now to inspect these files can use fastbencode like this
$ python -c 'import sys,pprint,fastbencode; pprint.pp(fastbencode.bdecode(sys.stdin.buffer.read()))' < infohash.torrent

Hi, if some torrents are failing to persist then that's a defect that we can raise an issue for. I don't think adding this extra behaviour in the core workflow to aid debugging the issue is the right solution.
In your case I think it's due to the safe_pieces and save_files_threshold settings you have and that the app hasn't been well tested with the configs the way you have them.
Having these settings on greatly increases the amount of data you're having to save. This is done in batches, and those batch sizes are currently fixed.
So here's what I think might help for you, :
https://github.com/bitmagnet-io/bitmagnet/blob/main/internal/dhtcrawler/factory.go#L86
persistTorrents: concurrency.NewBatchingChannel[infoHashWithMetaInfo](
	1000,
	1000,
	time.Minute,
),
persistSources: concurrency.NewBatchingChannel[infoHashWithScrape](
	1000,
	1000,
	time.Minute,
),

The arguments to that NewBatchingChannel function are:
func NewBatchingChannel[T any](capacity int, maxBatchSize int, maxWaitTime time.Duration)

So I think you should be dialing down the second argument, maxBatchSize, maybe to around 100 in your case, and I think you should see a drop-off in errors (but of course everything will still be working harder than under the default settings).
Are you able to get any reduction in errors doing this? If you can gather any info then we can build it into better supporting the settings you're using...

but I'm not sure this should be added as part of the core behaviour.

I don't see any other way and it's behind option so I don't see issue with this. The goal of this PR is to never lose any torrent data. There can be multiple reasons when that happens, for example currently if DB is down or you restart it, you will lose data. Also if there is some "weird/interesting/unexpected" torrent  it also could fail and I don't want to lose those either.

Are you still seeing https://github.com/bitmagnet-io/bitmagnet/issues/127 after upgrading or any other errors?

Together with this PR I actually patched out encoding checks and let them intentionally fail and get saved for further inspection. So with this I don't care about any of those errors as I will be able to look into it more. I still care even for corrupt/wrong/damaged torrents.

but I'm not sure this should be added as part of the core behaviour.

I don't see any other way and it's behind option so I don't see issue with this. The goal of this PR is to never lose any torrent data. There can be multiple reasons when that happens, for example currently if DB is down or you restart it, you will lose data. Also if there is some "weird/interesting/unexpected" torrent it also could fail and I don't want to lose those either.

Are you still seeing #127 after upgrading or any other errors?

Together with this PR I actually patched out encoding checks and let them intentionally fail and get saved for further inspection. So with this I don't care about any of those errors as I will be able to look into it more. I still care even for corrupt/wrong/damaged torrents.

I don't think we should add a separate workflow for corrupt torrents. Either the torrent can be saved in a valid state, or it's discarded. If there's a specific issue stopping valid torrents being saved it can be addressed (or debugged by modifying the source locally), but the use case you've described isn't the focus of this app.


XML element ordering

Hello,
is it possible to make the alphabetical XML element ordering optional?
(referres to XMLSerializer.java line 942:  Arrays.sort( names );)
thanks

If there's no option in XMLSerializer to configure this behavior then the answer is no.
This can be fixed by adding a new config flag to the serializer.

Yes, there is no option to configure this. Is it possible to add this flag in the next release?


Colab?

Has anyone figured out how to get this to work on colab? Currently getting issues.

Hi, yesterday I have managed to successfully run both image and video tests (CPU only so far) in Colab. I will share the final notebook in GitHub tomorrow.

A Colab notebook (inference on CPU) is available here: https://github.com/virtualramblas/python-notebooks-repo/tree/main/Colab/MobileFaceSwap

Hi, yesterday I have managed to successfully run both image and video tests (CPU only so far) in Colab. I will share the final notebook in GitHub tomorrow.

You can try run it on GPU by installing paddlepaddle-gpu==2.2.2 instead of paddlepaddle==2.1.2

Hi, yesterday I have managed to successfully run both image and video tests (CPU only so far) in Colab. I will share the final notebook in GitHub tomorrow.

You can try run it on GPU by installing pip install paddlepaddle-gpu==2.2.2 instead of paddlepaddle==2.1.2

Thanks @netrunner-exe. I focused on the CPU version mostly as I was curious about performance in a perspective of running in devices with lesser computational power and I can say that the results of this work are quite impressive not using a GPU. The authors of MobileFaceSwap did an amazing job.


"error bootstrapping venv" encountered after upgrading to rye 0.13 and attempting rye sync

Steps to Reproduce
I don't really know how to determine if this is reproducible. This is what I'm experiencing:

Have a working rye installation on Windows 10, with rye version 0.11
Upgrade to rye 0.12 (didn't test things after that)
Upgrade to rye 0.13
Execute "rye sync" on a project folder

Thanks!
Expected Result
Rye would sync
Actual Result
rye sync

detected outdated rye internals. Refreshing
Bootstrapping rye internals
Found a compatible python version<EMAIL_ADDRESS>Upgrading pip
Installing internal dependencies
error: could not sync because bootstrap failed
Caused by:
0: tried to symlink python shim
1: Cannot create a file when that file already exists. (os error 183)

Version Info
rye 0.13.0
commit: 0.13.0 (8e011231e 2023-08-29)
platform: windows (x86_64)
self-python<EMAIL_ADDRESS>symlink support: false
Stacktrace

Stack backtrace:
0:
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13: BaseThreadInitThunk
14: RtlUserThreadStart

@mitsuhiko
Done and seems to be working now. Thanks for the help!

I will close this for now. There might be something that when interrupted at the wrong moment breaks.


Empty dashboard

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

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

Superset version
23.3
I built from d57d2557b79b791a6cad43f638e2bd6eb3632264
Expected results
I expect the slice to appear on the dashboard.
Actual results

Steps to reproduce
Build a chart (slice). When saving choose add to new dashboard. Navigate to that dashboard. Its empty.  For now I'd recommend folks to hold until 0.23.4 or 0.24.0.

Think this could be access rights related? @timifasubaa ?

@SpyderRivera do you see the same problem on master?

@SpyderRivera What access permissions does the user have?

I can try on master. My user is admin/alpha

This is fixed when building from master


Description

Hello,
Just found this repo, and I would love to learn more about it, especially: how does this compare to the autoreload extension available with ipython ?
Thank you

Thanks for the question! I've added a comparison section to the README which addresses the topic of how Limeade differs from contemporary approaches.


CurseForge

Please consider publishing your mod to CurseForge for added exposure and to allow modpacks to include this more easily :)

okay, but only the latest version, is it ok?

Sure, that's fine.

Published. https://www.curseforge.com/minecraft/mc-mods/concentration
but there is a little bug suddenly appeared (#37 ) and i dont have any idea how to fix it. it may have some impact on user's experience.

Could you also consider enabling this? That would allow non-CF launchers to smoothly download it (e.g. Prism and GDLauncher)

done


[New game]: Pokemon game

🎮 Game Request
Game logic and basic description
A pokemon game to play with action packed fights and wild pokemon. Gotta catch 'em all!
Point down the features
Game points
Interactive, Responsive site, fun to play
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @SoarinSkySagar , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#1558

Hey @SoarinSkySagar ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @SoarinSkySagar !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign


add reactive search

Hi guys,
Hope you are all well !
Better than Kibana, add https://github.com/appbaseio/reactivesearch#4-live-demos for custom faceted search...
Cheers,

Hi @lucmski
thank you for writing me
Unfortunately the guy that did the desktop app in React is gone. I don't know react and for now I don't aim to learn it
Basically I'll most probably not touch this working code
Regards


No pre-trained cnn and vae model

I want to know where these libraries are called because I didn't see any models file

same issue, have you solved this?


[VITA-BOOTANIM] GIF loops forever

As the title suggests, gif loops indefinitely, presumably even after bootup is complete (short pressing power button turns screen off but turning it back on still just shows the gif)

duplicate of https://github.com/SKGleba/VitaTools/issues/3

try the latest version (requires recompiling the animation or changing priority in boot animation settings)


python310Packages.qdarkstyle: 2.8.1 -> 3.0.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.qdarkstyle is: "A dark stylesheet for Python and Qt applications"
meta.homepage for python310Packages.qdarkstyle is: "https://github.com/ColinDuquesnoy/QDarkStyleSheet"
meta.changelog for python310Packages.qdarkstyle is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin/.qdarkstyle-wrapped passed the binary check.
/nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin/qdarkstyle.example passed the binary check.
/nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin/qdarkstyle passed the binary check.
/nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin/.qdarkstyle.example-wrapped passed the binary check.
/nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin/qdarkstyle.utils passed the binary check.
/nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin/.qdarkstyle.utils-wrapped passed the binary check.
4 of 6 passed binary check by having a zero exit code.
4 of 6 passed binary check by having the new version present in output.
found 3.0.3 with grep in /nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3
found 3.0.3 in filename of file in /nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3

Rebuild report (if merged into master) (click to expand)

15 total rebuild path(s)

8 package rebuild(s)

8 x86_64-linux rebuild(s)
7 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
cq-editor
electron-cash
electrum
electrum-ltc
python310Packages.qdarkstyle
python39Packages.qdarkstyle
python39Packages.stytra
vorta

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.qdarkstyle https://github.com/r-ryantm/nixpkgs/archive/bb2aa206e786904ae9d56d5129fc1f19e485d470.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3
ls -la /nix/store/n3g28qm0r8gq2xllp2vanm4r5a4schpw-python3.10-qdarkstyle-3.0.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

cq-editor

3 packages failed to build:

electron-cash
electrum
electrum-ltc

4 packages built:

python310Packages.qdarkstyle
python39Packages.qdarkstyle
python39Packages.stytra
vorta

Maintainer pings
cc @nyanloutre for testing.

Done by 20edb5a8c0c38dfacfc22161ce7929e4ce3a5487.


Add 2.0.0~beta1

A few days ago 2.0.0~beta1 is public
https://www.elastic.co/blog/logstash-2-0-0-beta1-released

LGTM
/cc @tianon

LGTM


Update cloud-generating-documentation.md

https://www.notion.so/Update-cloud-generating-documentation-md-5f60a98aece744709e60f980d3655376

closing as this was for testing purposes only


⚠ BroadcasTheNet has degraded performance

In 88a4f88, BroadcasTheNet ($BTN) experienced degraded performance:

HTTP code: 200
Response time: 7194 ms

Resolved: BroadcasTheNet performance has improved in b3ebd76 after 9 minutes.


Add support for PSR-4

Can you please update this PHP REST API to support the PSR-4 standard?

Hello. Thank you for your request. We will look into this.

How is it going with the PSR-4 support? :)

Hello! Sorry for the delay on this. The person responsible for the sample codes development was away. It should be done in the next week.

Hello. Unfortunately this still needs some time to be finished.
Thanks for your patience

Any news regarding this improvement?

Hi. We are really sorry for the delay here.
Unfortunately there was other projects that required our full attention.
This improvement will be next in line. We will keep you posted.

Any updates on this?

In addition, a composer package would be great.

I've already implemented a composer.json, but it's not yet official added: https://packagist.org/packages/paysafecard/paysafecard-rest_api-php
However: It's using the official code from paysafecard.


Ignore Navigation Active breaks voice command button longpress focus

After aplying the patch when doing a long push on the steering wheel voice command button AndroidAuto does not get in focus any more.
The input of the voice comand itself works as usual but the jump to the AA interface was also a nice feature...especialy if google got something wrong.
I have MHI2_ER_VWG13_K4525_MU1367. After removal of the patch the longpress focus thing works again.
I was able to decompile the JAR with quiltflower but for someone who did some basic C several years ago Java is some unreadable jibbrisch...at least to me.
But im willing to volunteer for testing!
Else thanks for the great work and effort!

 It's like it is when you install the patch

Okay, this was not clear to me.
Please mark it as a "feature" somewhere.
Have not found anny info yet.

Yeah this issue hadn't been noticed before so thanks for bringing it up.
The patch basically works by breaking some of the interlocks between the mib and AA system so it doesn't surprise me this is knocked out too.
Fixing this case might be technically possible but likely very difficult. Would need to use trace logging and added stack traces to identify the code path being run when the button if pressed and try to find where it hits one of the patched points. Then add an extra flag to a class somewhere that can be set when the button is pressed that can be checked at the point the existing patch works.  I'm not likely to have time to work on this myself though sorry.

The manu for chosing trace types (Navigation, Speech or smartphone etc.) I found already. Also a point in the menü where I could select SD card. But it does not seem to store anything on the card. Maybe I have not put in the right words into google yet but what do I have todo to get the traces written on the SD card?

Sorry yeah logging and trace isn't quite that simple. While I've managed to get that built in trace system logging to SD in the past, I'm not sure exactly what steps were required. It didn't help because that trace log is in a proprietary binary format that I was never able to decide.
When I mentioned stack traces I meant adding chunks of extra code into the Java to print out a stack trace once that piece of code it hit. This then only helps if you have a way to view the logs printed by java - depending on how they're printed you can sometimes see then on the mmx uart port wired to the back of the unit.
PS. You don't need to decompile my jar for this patch, the source is published already https://gitlab.com/alelec/mib2-lsd-patching
I've got some other hacks to redirect the Java logs to a temp file but haven't properly documented it yet. I've put some notes on it here: https://gitlab.com/alelec/mib2-lsd-patching/-/wikis/home

Okay, luckylie I did the patching "by foot" for the first time when these neat toolboxes where not availible yet -> I have a wiring setup where I can acces the mmx uart port on my desk.
When I have some time I will have a look into the last way you mentioned because out of my perception this is the most convinient - if it works.
Could then be addet as a feature to the toolbox that alters the startup.sh to turn logging on and off.


add code inspection by code climate

This should now generate a testing score via CodeClimate. I wanted to see if it was the same as CodeCov. If it starts to work I might later add a badge.
Made some small modifications to requirements.txt like removing Poetry which I no longer use.

Some checks fail because the project still has the wrong version of a library called coverage.
Push the new reqs and this will disappear.


berry json module load HEX error

https://github.com/arendst/Tasmota/issues/16390
issue
run 1
import json
var s = "{\"abc\":16}"
var j = json.load(s)
print(j)

output:
{'abc': 16}

run 2
import json
var s = "{\"abc\":0x10}"
var j = json.load(s)
print(j)

output:
nil

run 3
import json
var s = "{\"abc\":{\"hex\":16}}"
var j = json.load(s)
print(j)

output
{'abc': {'hex': 16}}

run 4
import json
var s = "{\"abc\":{\"hex\":0x10}}"
var j = json.load(s)
print(j)

reboot...
patch
diff --git a/lib/libesp32/berry/src/be_strlib.c b/lib/libesp32/berry/src/be_strlib.c
index 23fdf978f..2c5424634 100644
--- a/lib/libesp32/berry/src/be_strlib.c
+++ b/lib/libesp32/berry/src/be_strlib.c
@@ -263,6 +263,9 @@ BERRY_API bint be_str2int(const char *str, const char **endstr)
         while ((c = be_char2hex(*str++)) >= 0) {
             sum = sum * 16 + c;
         }
+        if (endstr) {
+            *endstr = str - 1;
+        }
         return sum;
     } else {
         /* decimal literal */

This is as designed. {"abc":{"hex":0x10}} is not valid json. Json does not support hex integers. You can double check with jsonlint.com
If you want hex, you need to wrap into a string. Yet Berry can transparently convert to an int using int(). If you force conversion to int it will work in both cases.
import json
var s = '{"abc":{"hex":"0x10","dec":16}}'
var j = json.load(s)
print(j)
# {'abc': {'hex': '0x10', 'dec': 16}}
print(int(j['abc']['hex']))
# 16
print(int(j['abc']['dec']))
# 16

JSON5 exists as a proposed unofficial extension to JSON, including support for hex data. But it seems to be a fork without mainstream acceptance, and not great for compatibility.

When I tested the modbus bridge function, I found that entering the hex value will cause the motherboard to reboot
There will be hex in json because, when debugging, it is introduced for the convenience of debugging faults.
This bug occurs only with json parsing
But the error is caused by the basic function be_str2int.
Personally, considering the versatility of be_str2int, regardless of the json rules.
This patch is still necessary.

There is no bug. No patch is necessary.
You are just using invalid JSON, and I'd call it an error to break compatibility with standard JSON. Sure, extending the format may be convenient for your specific use case, but that does not make it reasonable, unless you aim for full JSON5 support, which I'm not completely convinced of being a good plan either.

Hmmmm.... There may be two questions here. One is the focus on hex data in JSON being a syntax error which should fail, meaning that run 2 is "ok, but not easy to debug". Friendliness of how the error shows up can be a consideration, but causing a crash is a bad way. It was not very clear if this was what the "reboot..." in your original description (run 4) meant?

I can reproduce the crash and this is definitely wrong. Thanks for the fix, let me check a thing or two before integrating it.

Aha. The patch you provided solves the crash, but also makes accidentally the parsing of hex working.  I suppose we will have to live with that, Berry accepting hex numbers although they are invalid JSON.

This was merged?


[tool_crash] _CastError: (#0      new WebPlugin.fromYaml (package:flutter_tools/src/platform_plugins.dart:548:34))

Command
flutter --no-color run --machine --track-widget-creation --device-id=emulator-5554 --start-paused --dart-define=flutter.inspector.structuredErrors=true lib/main.dart

Steps to Reproduce

...
...
...

Logs
_CastError: (#0      new WebPlugin.fromYaml (package:flutter_tools/src/platform_plugins.dart:548:34))
#0      new WebPlugin.fromYaml (package:flutter_tools/src/platform_plugins.dart:548:34)
#1      new Plugin._fromMultiPlatformYaml (package:flutter_tools/src/plugins.dart:142:21)
#2      new Plugin.fromYaml (package:flutter_tools/src/plugins.dart:78:21)
#3      _pluginFromPackage (package:flutter_tools/src/flutter_plugins.dart:63:17)
#4      findPlugins (package:flutter_tools/src/flutter_plugins.dart:88:28)
<asynchronous suspension>
#5      refreshPluginsList (package:flutter_tools/src/flutter_plugins.dart:1080:32)
<asynchronous suspension>
#6      FlutterProject.ensureReadyForPlatformSpecificTooling (package:flutter_tools/src/project.dart:357:5)
<asynchronous suspension>
#7      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1412:7)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1257:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:283:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:64:9)

[✓] Flutter (Channel stable, 3.7.1, on macOS 13.1 22C65 darwin-arm64, locale en-UZ)
    • Flutter version 3.7.1 on channel stable at /Users/mac/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7048ed95a5 (7 days ago), 2023-02-01 09:07:31 -0800
    • Engine revision 800594f1f4
    • Dart version 2.19.1
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/mac/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Users/mac/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/mac/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.74.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 13 (API 33) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.1+2
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: f1875d570e39de09040c8f79aa13cc56baab8db1
Plugins
flutter_keyboard_visibility-5.3.0
flutter_keyboard_visibility_web-2.0.0
isar_flutter_libs-2.5.0
path_provider-2.0.11
path_provider_android-2.0.20
path_provider_ios-2.0.11
path_provider_linux-2.1.7
path_provider_macos-2.0.6
path_provider_windows-2.0.7
shared_preferences-2.0.15
shared_preferences_android-2.0.13
shared_preferences_ios-2.1.1
shared_preferences_linux-2.1.1
shared_preferences_macos-2.0.4
shared_preferences_web-2.0.4
shared_preferences_windows-2.1.1
sqflite-2.0.3+1
url_launcher-6.1.5
url_launcher_android-6.0.19
url_launcher_ios-6.0.17
url_launcher_linux-3.0.1
url_launcher_macos-3.0.1
url_launcher_web-2.0.13
url_launcher_windows-3.0.1

Closing this as a duplicate of https://github.com/flutter/flutter/issues/115738


Update integration workflow to capture crashdump on timeout

The workflow template was updated here: https://github.com/charmed-kubernetes/.github/pull/2
Just bringing the update in to this repo.

Job failed successfully? Kind of? I got a crashdump but it came late in the teardown, after kube-ovn had already been removed. I'll look into this more tomorrow.

I removed the timeout on the tox -e integration step because that was preventing pytest-operator from collecting crashdumps as part of cleaning up models. The most recent failure includes a crashdump captured before the model teardown started; success! I think this is ready to go.


Added hover effect on links and made website responsive

Added hover cursor pointer effect on links

Improved button spacing for responsive design

@Pranshu1902

I didn't assign you this issue.
I didn't ask for the hover cursor pointer effect in the issue.
All you did was add a link tag on items which purposely don't have one simply because Allops is not on these platforms yet.
you lied about adding button spacing for responsiveness( it was already arranged in that way on allops ) and even if you did then, I don't know how it helps in making the website responsive.

Maintainers can see what changes you've made!
This type of invalid and spammy PRs are strongly discouraged in the open source community
So please don't make such mistakes😇 and focus on making some quality contributions✨

@Sidd2024
Sorry, I saw my profile under participants of the issue and confused it with the list of assigned.
Will try to make better contributions, sorry again


FileNotFoundError: [Errno 2] No such file or directory for smbus.SMBus(_SMBUS_DEV)

Great program, thank you!
I was getting this error when starting the argonone service:
Sep 21 12:37:40 raspberrypi argonone[9701]: INFO: Loading config file from /etc/argonone.yaml
Sep 21 12:37:40 raspberrypi argonone[9701]: Traceback (most recent call last):
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/bin/argononed", line 11, in <module>
Sep 21 12:37:40 raspberrypi argonone[9701]:     load_entry_point('argon1==0.1', 'console_scripts', 'argononed')()
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/lib/python3/dist-packages/argonone/cmdline.py", line 175, in argondaemon_main
Sep 21 12:37:40 raspberrypi argonone[9701]:     daemon = ArgonDaemon()
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/lib/python3/dist-packages/argonone/__init__.py", line 541, in __init__
Sep 21 12:37:40 raspberrypi argonone[9701]:     self._argon_board = ArgonOneBoard(initial_speed=0, bus_mutex=Lock())
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/lib/python3/dist-packages/argonone/__init__.py", line 78, in __init__
Sep 21 12:37:40 raspberrypi argonone[9701]:     self._bus = smbus.SMBus(_SMBUS_DEV)
Sep 21 12:37:40 raspberrypi argonone[9701]: FileNotFoundError: [Errno 2] No such file or directory

The smbus python module gave this error because the i2c kernel modules were not loaded. The raspi-config program offers a nice way to have them automatically loaded and then the service runs without issue.
I don't know if it is appropriate for the deb package installation to take care of this but otherwise maybe the README could mention it.

Thanks, glad you find useful. Yes, .DEB (but not setup.py, I believe its
not meant for that) creates special user for daemon and adds it to i2c
group, so under "normal" use this should not happen. But it does not hurt
to check..
On Mon, Sep 21, 2020, 7:05 AM ptalbert<EMAIL_ADDRESS>wrote:

Great program, thank you!
I was getting this error when starting the argonone service:
Sep 21 12:37:40 raspberrypi argonone[9701]: INFO: Loading config file from /etc/argonone.yaml
Sep 21 12:37:40 raspberrypi argonone[9701]: Traceback (most recent call last):
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/bin/argononed", line 11, in
Sep 21 12:37:40 raspberrypi argonone[9701]:     load_entry_point('argon1==0.1', 'console_scripts', 'argononed')()
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/lib/python3/dist-packages/argonone/cmdline.py", line 175, in argondaemon_main
Sep 21 12:37:40 raspberrypi argonone[9701]:     daemon = ArgonDaemon()
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/lib/python3/dist-packages/argonone/init.py", line 541, in init
Sep 21 12:37:40 raspberrypi argonone[9701]:     self._argon_board = ArgonOneBoard(initial_speed=0, bus_mutex=Lock())
Sep 21 12:37:40 raspberrypi argonone[9701]:   File "/usr/lib/python3/dist-packages/argonone/init.py", line 78, in init
Sep 21 12:37:40 raspberrypi argonone[9701]:     self._bus = smbus.SMBus(_SMBUS_DEV)
Sep 21 12:37:40 raspberrypi argonone[9701]: FileNotFoundError: [Errno 2] No such file or directory
The smbus python module gave this error because the i2c kernel modules
were not loaded. The raspi-config program offers a nice way to have them
automatically loaded and then the service runs without issue.
I don't know if it is appropriate for the deb package installation to take
care of this but otherwise maybe the README could mention it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spapadim/argon1/issues/7, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBFUGYWA7EP33OEDLG7Z53SG4XODANCNFSM4RUMTTPQ
.


delete 's'  tag will added 's}' in markdown

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
i wrote some chinese in markdown file, and i prepare to delete some words which pronunciation started with 's'  ,there is something wrong ,it will add 's}' after i delete
Environment
Macos Monterey
MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports)
If applicable, add mockups / screenshots to help explain present your vision of the feature
https://user-images.githubusercontent.com/24662311/227152219-3819dfc8-c190-448d-a305-62ebef14d1bb.mov
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

I got the same issue like you.

Same issue

I'm going to close this issue as a duplicate of https://github.com/zed-industries/community/issues/877, but I am bringing it up as an issue with the team.


disk_block_cache: clean out working set cache regularly

Modify the background cleanout of the sync cache to also cleanout the working set cache.

retagging review per song's request

👍🏼


Release: Version v0.5.8 RC

:package: :rocket:

Builds ready [9195c68]builds: chrome, firefox, opera
bundle viz: background, ui, portal-inpage, portal-contentscript, ui-libs, bg-libs, phishing-detect
dep viz: background
all artifacts


Whitespace text ignored at DOM root

local SLAXML = require 'slaxdom'
SLAXML:dom("<!--a-->\n<r/>", {simple=true})
--> {
-->   type="document",
-->   name="#doc",
-->   kids={
-->     {type="comment", name="#comment", value="a"},
-->     {type="element", name="r", attr={}, kids={}}
-->   }
--> }

Without stripWhitespace=true, we would expect to see a text node between the comment and the root, i.e.
--> {
-->   type="document",
-->   name="#doc",
-->   kids={
-->     {type="comment", name="#comment", value="a"},
-->     {type="text", name="#text", value="\n"},
-->     {type="element", name="r", attr={}, kids={}}
-->   }
--> }

I was previously explicitly ignoring all text nodes in the document. This might be more convenient most of the time, but it's makes round-tripping xml->dom->xml worse. It's legal to have whitespace-only nodes outside the root element.


$ionicNavBarDelegate.showBackButton() always returns false

The showBackButton() function in the ionNavBar directive controller returns !!($scope.hasBackButton && $scope.backButtonShown). From what i can see $scope.hasBackButton is no longer used, and as such is always undefined. This results in false being returned from $ionicNavBarDelegate.showBackButton() regardless of actual back button state.
See this CodePen:
http://codepen.io/SpenceDiNicolantonio/pen/zracD

Greetings @SpenceDiNicolantonio!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


New pages are prerendered as Cannot GET

🐞 Bug report
Description
A while ago I experienced this problem, that when I create a new page in my angular app, scully fails to prerender it. First the new routes are not picked up by scully at all. I have to delete node_modules and reinstall it, then scully finds the new routes but again fils to prerender because it fails to open it from an angular app with a message like Cannot GET /terms-and-conditions. After this I need to restart my machine and then it works again. The problem about this is that I get this issue every single time I add pages to my app and it even happened on the CI once (I guess because I didn't clear the caches).
Running scully --killServer didn't do any change. Only methods I described above helped me so far.
Here is an example of how such page gets prerendered:
<!DOCTYPE html><meta name="generator" content="Scully 0.0.86">
<meta charset="utf-8">
<title>Error</title>

Cannot GET /terms-and-conditions

🔬 Minimal Reproduction
To reproduce it you should create an app, add some routes and prerender it. Then add new routes and try to prerender again. In my case only the new routes are affected by this issue
💻Your Environment
Angular Version:

Angular CLI: 9.0.2
Node: 12.14.0
OS: linux x64

Angular: 9.0.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.2
@angular-devkit/build-angular     0.900.2
@angular-devkit/build-optimizer   0.900.2
@angular-devkit/build-webpack     0.900.2
@angular-devkit/core              9.0.0-rc.8
@angular-devkit/schematics        9.0.0-rc.8
@angular/cdk                      9.0.0
@angular/cli                      9.0.2
@ngtools/webpack                  9.0.2
@schematics/angular               9.0.0-rc.8
@schematics/update                0.900.2
rxjs                              6.5.4
typescript                        3.6.4
webpack                           4.41.2

Scully Version:

"@scullyio/init": "0.0.13",
"@scullyio/ng-lib": "0.0.22",
"@scullyio/scully": "0.0.86",

The actual Scully strategy is to reduce the time needed to run npm run scully by not scanning the routes of the project if a scully-routes.json file already exists inside src/assets (created the first time you run npm run scully).
In order to discover new routes, you need to add --scan option when running npm run scully :
npm run scully --scan

It's included inside the docs but it might need to be more visible without having to dig inside it.
I'll consider finding a way to make it more visible for new users.

@geromegrignon thank you for your response. I will try it next time. Thing is that I am using scully for around 2-3 months now and I don't follow all the updates and changes and I think back then it did not work this way.

@BlindDespair I was puzzled by this too, and I wrote this ;) Today we are going to beta, and breaking changes like this, will get proper documentation!
Closing this, as it works as expected


Investigate implementing Firebase-UI equivalent controls across the board

Lists already exist, though only for Realtime Database; try to see if it's possible to swap backend for Firestore as well (make them interchangeable through an interface if possible).

@BearDooks/@fenix-hub - we should investigate building a generic login control here that can just be dropped in and configured and make it so people can just automatically add it to their games very easily.

@BearDooks/@fenix-hub - we should investigate building a generic login control here that can just be dropped in and configured and make it so people can just automatically add it to their games very easily.

Transferring to Firebase-UI.

Transferring to Firebase-UI.


Handle absence of ui-select-no-choice

Removed the template's ui-select-no-choice from the default template when not specified by user.
The extra element that was not removed was causing issues as it was always present on the dom. If I do add a ui-select-no-choice element, it is hidded by a ng-show added by the ui-select-no-choice directive. See https://github.com/angular-ui/ui-select/issues/1753#issuecomment-238061191

You've yet to provide a plunkr or screenshot of the problem this actually causes though? Ie. What problem is caused by it remaining in the DOM, please provide an example.

Closing due to lack of response.


generateReactComponentId fails in Firefox while browsing CodeSandbox examples

While checking out the example pages, I get the following error in Firefox (but not Chrome):
TypeError
can't access property "toUpperCase", fn[0] is undefined
generateReactComponentId/_a<@https://b5upgd.codesandbox.io/node_modules/
zedux/react/dist/cjs/classes/IdGenerator.js:83:13
generateReactComponentId@https://b5upgd.codesandbox.io/node_modules/
zedux/react/dist/cjs/classes/IdGenerator.js:78:14
useReactComponentId/<@https://b5upgd.codesandbox.io/node_modules/
zedux/react/dist/cjs/hooks/useReactComponentId.js:16:62
mountMemo
https://b5upgd.codesandbox.io/node_modules/react-dom/cjs/react-dom.development.js:17225:19

The Live Sandbox examples in the docs work fine, however: https://omnistac.github.io/zedux/docs/walkthrough/quick-start
A bit of triage indicates that it's likely because DEV mode is on while in Firefox in CodeSandbox, although I wasn't able to glean insights into why

Yoo thanks for reporting @cswendrowski!
Looks like this is gonna be due to SpiderMonkey generating stack traces a little differently. TMK Zedux hasn't been tested at all yet in anything but V8. In theory, everything should be cross-platform compatible. This generateReactComponentId code is definitely an exception - it does some hacky stuff in DEV to figure out a human-readable identifier for the graph.
I'll get a fix for this today and will definitely try to get examples running on SpiderMonkey and JavaScriptCore at least soon - just to make sure there's nothing else.


epkowa: add plugin for Perfection V550 Photo

Description of changes
This PR adds support for the Epson Perfection V550 Photo scanner to the epkowa driver. I archived the upstream proprietary package and wrote the plugin derivation based off the already existing V500 entry.
I've been dogfooding this change and the scanner is working as expected.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

thank you!


Empty atributes

Hello!
I have 1000 NFTs in my collection, I want to put one of the attributes only on 100 NFTs. Is it possible?

Set the asset to 10% and it will roughly only be on 10% etc...

Hi!
Its completely random so if you say I want this items appears 100 times the randomization can create 80 nfts or 120 nfts with that item.
The Best way to do this is set the number of the items that the sum be equal to the total nfts!
For example you have a 1000 collection and 3 items.
100-item_1.png
400-item_2.png
500-item_3.png
So you have 3 items that you say you want to appear 100,400 and 500 (the sum is equal to 1000) so the random can create nfts with items distributed near to the number of the items.
This will only work if you have a good amount of posibilities for ur nfts!

You probably did not understand me.
I have 1000 NFTs, I want a certain attribute to be only 100 NFTs, and the remaining 900 NFTs were completely without this attribute

I tried to specify an amount less than 1000, but it put items on each NFT

I understood you, I done the same thing by adding all my traits and setting them to sum total of 100:
10-Hat1 (10%)
20-Hat2
20-Hat3
25-Hat4
25-Hat5
And out of a 2222 collection it generated 226 items with (Hat1)

1000 NFT
Atribute: Hat
5% - Rare Item
3% - Very Rare Item
2% - Legendary Item
90% - Nothing

Okay, I have to use an empty png file in the remaining amount of NFTs, I thought there is a more convenient way

If you were wanting only 10 of nfts to have a hat make the varieties equal 10, then create a blank labelled none with 90

This looks like a really good add-on! ATM You can do that creating a full alpha layer called Notrait (with the number of how many Notrait you want) For example in a 1000 mint collection you want just 100 Hats you can create a item with 900-Notrait.png And the program when see a Notrait Item don't add that into the metadata ! SO if the Notrait appears will not be added and you will have less traits


Port further reference implementations

Port of the reference implementations from pystiche.papers and the replication scripts to pystiche_papers.
li_wand_2016
ulyanov_et_al_2016
gatys_et_at_2017

@jbueltemeier could you please split up this PR into multiple separate so that they are easier to review. At first glance I propose 4:

li_wand_2016
ulyanov_et_al_2016
gatys_et_al_2017
fix that you introduced to johnson_alahi_li_2016


Add test for cleanupServiceDiscovery

Unit test for the cleanupServiceDiscovery,
follow up of PR: #1985
Signed-off-by: Flavio Crisciani<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b5cc5c5). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1991   +/-   ##
=========================================
  Coverage          ?   38.03%
=========================================
  Files             ?      137
  Lines             ?    27362
  Branches          ?        0
=========================================
  Hits              ?    10406
  Misses            ?    15685
  Partials          ?     1271

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 b5cc5c5...52a9ab5. Read the comment docs.

LGTM


Has a doc about dev wellcommerce？

@benyang2015 Not yet. We're preparing next beta (only fixes) and then we'll start with few tutorials about extending WellCommerce with own modules (forms, datagrids, datasets, Doctrine enhancers).


Implement something like "user favourites / start-up profile" in Stroom

Each day when I log into Stroom I often spend the first few minutes loading up the same few dashboards/other collateral.
Would be nice if I could just set this as my default view and modify as required.
Maybe something for v7.2 release?

Would it be acceptable to just restore previously open panes?


FIX mark a successful login attempt when completing a password reset

Description
See issue #10100
Manual testing steps

Lock yourself out of a site (5 password fails)
Reset your password via 'Forgot Password'
Password reset fails as user is 'Locked out'

Issues

#10100

Pull request checklist

[x] The target branch is correct

See picking the right version

[x] All commits are relevant to the purpose of the PR (e.g. no debug statements, unrelated refactoring, or arbitrary linting)

Small amounts of additional linting are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.

[x] The commit messages follow our commit message guidelines
[x] The PR follows our contribution guidelines
[x] Code changes follow our coding conventions
[x] This change is covered with tests (or tests aren't necessary for this change)
[x] Any relevant User Help/Developer documentation is updated; for impactful changes, information is added to the changelog for the intended release
[x] CI is green

@GuySartorelli Looking at that, if you make it conditional then you would still hit the issue if you had login_recording set to false, but lock_out_after_incorrect_logins set to true.

I'm okay with it being conditional against both of those, if that's the case. Though my understanding is that this bug can't happen if login_recording is set to false, because it won't be writing any login attempt records at all.

@GuySartorelli updated accordingly!


[Bug] Certs won't be renewed (not automatically nor manually)

Current Behavior
Certs won't be renewed automatically.
Expected Behavior
Certs will be renewed automatically
Steps To Reproduce
Just running NPM as a docker container on unraid server running latest version. I am not so familiar run docker containers, so I might haven't enough information to troubleshoot. Pls guide me to provide all relevant information.

Docker container itself seem sto work fine. Verion should be up to date. I can reach the web UI but I want to have automatic renew of certs in place.
Any idea what I could try to get this fixed?
Environment

OS: unraid
OS version: 6.12.4
CPU: Intel® Core™ i5-6400T CPU @ 2.20GHz
Docker version: 20.10.24
Device model:
Browser/OS:

Container creation
default settings. No changes done
Container log
[10/11/2023] [2:10:59 PM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --preferred-challenges "dns,http" --disable-hook-validation
Failed to renew certificate npm-1 with error: Some challenges have failed.
Failed to renew certificate npm-2 with error: Some challenges have failed.
Failed to renew certificate npm-21 with error: Some challenges have failed.
Failed to renew certificate npm-22 with error: Some challenges have failed.
Failed to renew certificate npm-4 with error: Some challenges have failed.
Failed to renew certificate npm-7 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
  /etc/letsencrypt/live/npm-2/fullchain.pem (failure)
  /etc/letsencrypt/live/npm-21/fullchain.pem (failure)
  /etc/letsencrypt/live/npm-22/fullchain.pem (failure)
  /etc/letsencrypt/live/npm-4/fullchain.pem (failure)
  /etc/letsencrypt/live/npm-7/fullchain.pem (failure)
6 renew failure(s), 0 parse failure(s)

    at ChildProcess.exithandler (node:child_process:402:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1100:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

Container inspect
root@Tower:~# docker inspect Nginx-Proxy-Manager-Official
[
    {
        "Id": "43f9d9490cb361dd2c9dee4ab78ee89ae7fed49f220716ccf9951c6c75a24f06",
        "Created": "2023-08-16T10:27:15.572601527Z",
        "Path": "/init",
        "Args": [],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 14383,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2023-09-03T07:06:54.717732879Z",
            "FinishedAt": "2023-09-03T06:38:25.985558634Z"
        },
        "Image": "sha256:9c3f57826a5d0a82720533269d1996931d471f8130a0edb58d4a6602a0a13a8c",
        "ResolvConfPath": "/var/lib/docker/containers/43f9d9490cb361dd2c9dee4ab78ee89ae7fed49f220716ccf9951c6c75a24f06/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/43f9d9490cb361dd2c9dee4ab78ee89ae7fed49f220716ccf9951c6c75a24f06/hostname",
        "HostsPath": "/var/lib/docker/containers/43f9d9490cb361dd2c9dee4ab78ee89ae7fed49f220716ccf9951c6c75a24f06/hosts",
        "LogPath": "/var/lib/docker/containers/43f9d9490cb361dd2c9dee4ab78ee89ae7fed49f220716ccf9951c6c75a24f06/43f9d9490cb361dd2c9dee4ab78ee89ae7fed49f220716ccf9951c6c75a24f06-json.log",
        "Name": "/Nginx-Proxy-Manager-Official",
        "RestartCount": 0,
        "Driver": "btrfs",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/mnt/user/appdata/Nginx-Proxy-Manager-Official/data:/data:rw",
                "/mnt/user/appdata/Nginx-Proxy-Manager-Official/letsencrypt:/etc/letsencrypt:rw",
                "/tmp/Nginx-Proxy-Manager-Official/var/log:/var/log:rw"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {}
            },
            "NetworkMode": "br0",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": false,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "CapAdd": null,
            "CapDrop": null,
            "CgroupnsMode": "private",
            "Dns": [],
            "DnsOptions": [],
            "DnsSearch": [],
            "ExtraHosts": null,
            "GroupAdd": null,
            "IpcMode": "private",
            "Cgroup": "",
            "Links": null,
            "OomScoreAdj": 0,
            "PidMode": "",
            "Privileged": false,
            "PublishAllPorts": false,
            "ReadonlyRootfs": false,
            "SecurityOpt": null,
            "UTSMode": "",
            "UsernsMode": "",
            "ShmSize": 67108864,
            "Runtime": "runc",
            "ConsoleSize": [
                0,
                0
            ],
            "Isolation": "",
            "CpuShares": 0,
            "Memory":<PHONE_NUMBER>,
            "NanoCpus": 0,
            "CgroupParent": "",
            "BlkioWeight": 0,
            "BlkioWeightDevice": [],
            "BlkioDeviceReadBps": null,
            "BlkioDeviceWriteBps": null,
            "BlkioDeviceReadIOps": null,
            "BlkioDeviceWriteIOps": null,
            "CpuPeriod": 0,
            "CpuQuota": 0,
            "CpuRealtimePeriod": 0,
            "CpuRealtimeRuntime": 0,
            "CpusetCpus": "",
            "CpusetMems": "",
            "Devices": [],
            "DeviceCgroupRules": null,
            "DeviceRequests": null,
            "KernelMemory": 0,
            "KernelMemoryTCP": 0,
            "MemoryReservation": 0,
            "MemorySwap": -1,
            "MemorySwappiness": null,
            "OomKillDisable": null,
            "PidsLimit": null,
            "Ulimits": null,
            "CpuCount": 0,
            "CpuPercent": 0,
            "IOMaximumIOps": 0,
            "IOMaximumBandwidth": 0,
            "MaskedPaths": [
                "/proc/asound",
                "/proc/acpi",
                "/proc/kcore",
                "/proc/keys",
                "/proc/latency_stats",
                "/proc/timer_list",
                "/proc/timer_stats",
                "/proc/sched_debug",
                "/proc/scsi",
                "/sys/firmware"
            ],
            "ReadonlyPaths": [
                "/proc/bus",
                "/proc/fs",
                "/proc/irq",
                "/proc/sys",
                "/proc/sysrq-trigger"
            ]
        },
        "GraphDriver": {
            "Data": null,
            "Name": "btrfs"
        },
        "Mounts": [
            {
                "Type": "bind",
                "Source": "/mnt/user/appdata/Nginx-Proxy-Manager-Official/data",
                "Destination": "/data",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/mnt/user/appdata/Nginx-Proxy-Manager-Official/letsencrypt",
                "Destination": "/etc/letsencrypt",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            },
            {
                "Type": "bind",
                "Source": "/tmp/Nginx-Proxy-Manager-Official/var/log",
                "Destination": "/var/log",
                "Mode": "rw",
                "RW": true,
                "Propagation": "rprivate"
            }
        ],
        "Config": {
            "Hostname": "43f9d9490cb3",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "443/tcp": {},
                "80/tcp": {},
                "81/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "TZ=Europe/Berlin",
                "HOST_CONTAINERNAME=Nginx-Proxy-Manager-Official",
                "TCP_PORT_443=443",
                "TCP_PORT_3000=3000",
                "HOST_OS=Unraid",
                "HOST_HOSTNAME=Tower",
                "TCP_PORT_81=81",
                "TCP_PORT_80=80",
                "DB_SQLITE_FILE=/data/database.sqlite",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt",
                "OPENRESTY_VERSION=<IP_ADDRESS>",
                "CROWDSEC_OPENRESTY_BOUNCER_VERSION=0.1.7",
                "CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt",
                "SUPPRESS_NO_CONFIG_WARNING=1",
                "S6_BEHAVIOUR_IF_STAGE2_FAILS=1",
                "S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0",
                "S6_FIX_ATTRS_HIDDEN=1",
                "S6_KILL_FINISH_MAXTIME=10000",
                "S6_VERBOSITY=1",
                "NODE_ENV=production",
                "NPM_BUILD_VERSION=2.10.4",
                "NPM_BUILD_COMMIT=fe93cb3",
                "NPM_BUILD_DATE=2023-08-14 23:19:12 UTC"
            ],
            "Cmd": null,
            "Healthcheck": {
                "Test": [
                    "NONE"
                ]
            },
            "Image": "jc21/nginx-proxy-manager",
            "Volumes": {
                "/data": {},
                "/etc/letsencrypt": {}
            },
            "WorkingDir": "/app",
            "Entrypoint": [
                "/init"
            ],
            "OnBuild": null,
            "Labels": {
                "maintainer": "Jamie Curnow<EMAIL_ADDRESS>                "net.unraid.docker.icon": "https://nginxproxymanager.com/icon.png",
                "net.unraid.docker.managed": "dockerman",
                "net.unraid.docker.webui": "http://[IP]:[PORT:81]",
                "org.label-schema.cmd": "docker run --rm -ti jc21/nginx-proxy-manager:latest",
                "org.label-schema.description": "Docker container for managing Nginx proxy hosts with a simple, powerful interface ",
                "org.label-schema.license": "MIT",
                "org.label-schema.name": "nginx-proxy-manager",
                "org.label-schema.schema-version": "1.0",
                "org.label-schema.url": "https://github.com/jc21/nginx-proxy-manager",
                "org.label-schema.vcs-url": "https://github.com/jc21/nginx-proxy-manager.git"
            }
        },
        "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "f56be7b623d1185adefb5652e34b4e6949c9019afaa9fa98c5b559aa6fb40bac",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {},
            "SandboxKey": "/var/run/docker/netns/f56be7b623d1",
            "SecondaryIPAddresses": null,
            "SecondaryIPv6Addresses": null,
            "EndpointID": "",
            "Gateway": "",
            "GlobalIPv6Address": "",
            "GlobalIPv6PrefixLen": 0,
            "IPAddress": "",
            "IPPrefixLen": 0,
            "IPv6Gateway": "",
            "MacAddress": "",
            "Networks": {
                "br0": {
                    "IPAMConfig": {},
                    "Links": null,
                    "Aliases": [
                        "43f9d9490cb3"
                    ],
                    "NetworkID": "7b6f4f51755cda4cb201e22faf948ce81fcf41ab45af4889ec29efff3fd7ca76",
                    "EndpointID": "619f1699fd979c9ea84d5283b00e39bdfab7299909d6004c5d24c636700214b1",
                    "Gateway": "<IP_ADDRESS>",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 24,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "",
                    "DriverOpts": {}
                }
            }
        }
    }
]
root@Tower:~#

Anything else?
No response

I seem to be having a similar issue with a similar OS. The certs maybe seem to be updating automatically now but any time I try to renew them manually or test the site I get an error and NPM crashes.
  Can you provide more details about the errors ?

Sure thing @jlesage
The error first occurred in October sometime and it was fine before then. It seems like a few other people were having similar issues around then both here in github and on the unraid form.
I noticed that when I tried to navigate to my page through the URL I get a 502 error:

My set up is cloudflare>duck DNS>nginx PM>various docker containers. It seems like the issue is with nginx PM since I can reach the dockers on the loacl network fine and I haven't changed anything in cloudflare or anywhere else.
At first the logs were giving me a renew cert error of some kind but that seems to be resolved in the logs I shared.
When I open up NGINX PM I can click around fine but when I go to the SSL tab and try to test connections it gives me the error 'Communication with the API failed, is NPM running correctly?' Then the entire docker container stops.
Renewing certificates or creating new certificates give me the error 'Internal Error' but does not shut down the container.
A weird bit is I installed the official NGINX docker container  and it gives the same errors.
I'm not great at all this sys admin stuff so I'm sorry if that's too much or too little info. But if you or someone can give me some direction if it's not actually a bug it would be much appreciated. I've exhausted all my knowledge and troubleshooting ability.

Then the entire docker container stops.

Can you share the container's log when this happens ?

When I navigate to the SSL Certificate page, click the 3 dots, then click 'Renew Now' the log outputs the following:
[app         ] [12/10/2023] [9:57:46 PM] [SSL      ] › ℹ  info      Renewing Let'sEncrypt certificates for Cert #7: nextcloud.jessecloud.club
[app         ] [12/10/2023] [9:57:46 PM] [SSL      ] › ℹ  info      Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-7" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
[app         ] [12/10/2023] [9:58:19 PM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --work-dir "/tmp/letsencrypt-lib" --logs-dir "/tmp/letsencrypt-log" --cert-name "npm-7" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation
[app         ] Saving debug log to /tmp/letsencrypt-log/letsencrypt.log
[app         ] Failed to renew certificate npm-7 with error: Some challenges have failed.
[app         ] All renewals failed. The following certificates could not be renewed:
[app         ]   /etc/letsencrypt/live/npm-7/fullchain.pem (failure)
[app         ] 1 renew failure(s), 0 parse failure(s)
[app         ] Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/letsencrypt-log/letsencrypt.log or re-run Certbot with -v for more details.

When I test server reach ability on that same page, just before it crashes the log looks like this:

Once it crashes the log closes so I couldn't copy the text.

Ok so there are 2 different problems.
Clicking Test Server Reachability causes a crash, but this is an isolated issue that doesn't affect normal functionality of NPM.
For the renew issue, did you check at /tmp/letsencrypt-log/letsencrypt.log (inside the container) to see the details about the problem ?

Thank you for the help! It looks like it's not an issue with Nginx.

Thank you for the help! It looks like it's not an issue with Nginx.

You are talking about the renew failure ?

Yes. I posted in the let's encrypt form and they stated it's an issue with some issue Cloudflare not being configured:
Or maybe it's saying that my server isn't configured correctly 😮💨 in which case I'm back to troubleshooting Niginx I guess.
Either way though I think you can close this bug report, thank you.
https://community.letsencrypt.org/t/proxy-manager-worked-for-weeks-then-one-day-stopped-certificates-wont-renew-lets-encrypt-error-111-connection-refused/209935/2


insecure defaults are not a good default.

The git source `git://github.com/pry/pry.git` uses the `git` protocol,
which transmits data without encryption. Disable this warning with
`bundle config git.allow_insecure true`, or switch to the `https`
protocol to keep your data secure.

It shouldn't be opt-in. It should be the default.
Gemfile:
gem "pry", github: "pry/pry"

We're unable to change the GitHub url in bundler 1 due to strict backwards compatibility. In bundler 2 we're removing the github option in favour of the gitoption or you can define your own GitHub option with (which you can currently do in bundler 1):
git_source(:github) do |repo_name|
  repo_name = “#{repo_name}/#{repo_name}” unless repo_name.include(“/“)
  “https://github.com/#{repo_name}.git"
end

Thanks. In the end I used the long form URL (https://..) but I think this was a bad choice, even with backwards compatibility in mind. It makes MITM attacks a real possibly with bundler + git. It feels like bundler and rubygems in general do not want to move away from a centralised platform (rubygems). Well, here is hoping for the future.

By the way, the "centralised platform" thing is an issue because of the difficultly in removing code from there. Once it's added, it's an uphill battle to remove it. That's why I generally do not use it. Anyway, not relevant here. Thank you for the update.


chore: separate namespace for new sidekick

Avoid confusing side effects between the current and new sidekick.

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


Stopping and leaving

People should be able to stop the game. It shouldn't require restarting the app to stop the game.
Also, people should be able to leave the game, so that they don't hold up the game when they don't respond.

From the directions:

To end a game, @<your-bot-name>: quit game

Agreed that players should be able to leave, definitely a good enhancement.


Adding extra URL properties

Adding extra URL properties  according to https://developer.mozilla.org/en-US/docs/Web/API/URL
I also check on Chrome and everything matches.
tests were added to the tests/dom/URL.js file
Let me know if I should remove the website/docs/flow-state.gif changes from this diff, it just kept poping as changed, I'm not sure what changed it.

What's up with the flow-state.gif change?

@samwgoldman I have no idea, it kept showing up, I thought there was some kind of script that updated it after a test run.
I'll remove it from the PR.

updated

@facebook-github-bot import

Thanks for importing. If you are an FB employee go to Phabricator to review.


Bad Escape character Error

I got this error from trying to run another repository of yours ( voicebox )
I got this error
  File "/root/work/code/mw_speech_synthesis/speech_synthesis/training/voicebox/voicebox_pytorch/__init__.py", line 1, in <module>
    from voicebox_pytorch.voicebox_pytorch import (
  File "/root/work/code/mw_speech_synthesis/speech_synthesis/training/voicebox/voicebox_pytorch/__init__.py", line 1, in <module>
    from voicebox_pytorch.voicebox_pytorch import (
  File "/root/work/code/mw_speech_synthesis/speech_synthesis/training/voicebox/voicebox_pytorch/voicebox_pytorch.py", line 28, in <module>
    from spear_tts_pytorch import TextToSemantic
  File "/root/.miniforge/envs/vb/lib/python3.10/site-packages/spear_tts_pytorch/__init__.py", line 1, in <module>
    from spear_tts_pytorch.spear_tts_pytorch import (
  File "/root/.miniforge/envs/vb/lib/python3.10/site-packages/spear_tts_pytorch/spear_tts_pytorch.py", line 27, in <module>
    from x_clip.tokenizer import tokenizer
  File "/root/.miniforge/envs/vb/lib/python3.10/site-packages/x_clip/tokenizer.py", line 169, in <module>
    tokenizer = SimpleTokenizer()
  File "/root/.miniforge/envs/vb/lib/python3.10/site-packages/x_clip/tokenizer.py", line 77, in __init__
    self.pat = re.compile(
  File "/root/.miniforge/envs/vb/lib/python3.10/re.py", line 251, in compile
    return _compile(pattern, flags)
  File "/root/.miniforge/envs/vb/lib/python3.10/re.py", line 303, in _compile
    p = sre_compile.compile(pattern, flags)
  File "/root/.miniforge/envs/vb/lib/python3.10/sre_compile.py", line 788, in compile
    p = sre_parse.parse(p, flags)
  File "/root/.miniforge/envs/vb/lib/python3.10/sre_parse.py", line 955, in parse
    p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
  File "/root/.miniforge/envs/vb/lib/python3.10/sre_parse.py", line 444, in _parse_sub
    itemsappend(_parse(source, state, verbose, nested + 1,
  File "/root/.miniforge/envs/vb/lib/python3.10/sre_parse.py", line 555, in _parse
    code1 = _class_escape(source, this)
  File "/root/.miniforge/envs/vb/lib/python3.10/sre_parse.py", line 350, in _class_escape
    raise source.error('bad escape %s' % escape, len(escape))
re.error: bad escape \p at position 59

The source is this line
self.pat = re.compile(
            r"""<\|startoftext\|>|<\|endoftext\|>|'s|'t|'re|'ve|'m|'ll|'d|[\p{L}]+|[\p{N}]|[^\s\p{L}\p{N}]+""",
            re.IGNORECASE)

@wassimseif ah darn, i thought the re did everything regex did
ok, i've reverted a recent change


Remove unnecessary comments from Caesars Cipher

Closing because the commit was no good. Changed/removed extra comments but did not remove unnecessary declared variables per the requirements.

@samanthamed If you do decide to submit another PR please read over our contributing guidelines first. Thanks and happy coding!


How to sanitize HTML for passing it to 'dangerouslySetInnerHTML'

I tried to sanitize HTML in the following JSX code:

with DOMPurify module but it's not isomorphic so it didn't work for both client and server-side rendering. Any solution?

Something like https://www.npmjs.com/package/html-escape might work. This is not a Next.js issue 😄


Add GH action for deleting dangling review apps

Description
Adding a scheduled Github action to delete dangling review apps.
Sometimes the one/off delete (triggered by PRs being merged/closed) fails, leaving the review app alive without any use.
At some point the number of unused review apps becomes quite big and having to check them and manually delete them is a pain. So this Github action deals with it.
Current schedule: Every night at 1am.
PSD review apps before cleaning action run
ACTIVE_PRS:
psd-pr-921 psd-pr-920 psd-pr-919 psd-pr-918 psd-pr-917 psd-pr-913 psd-pr-908 psd-pr-906 psd-pr-870 psd-pr-861 psd-pr-816
REVIEW_APPS:
psd-pr-447 psd-pr-482 psd-pr-489 psd-pr-508 psd-pr-524 psd-pr-564 psd-pr-565 psd-pr-576 psd-pr-586 psd-pr-617 psd-pr-623 psd-pr-626 psd-pr-630 psd-pr-635 psd-pr-638 psd-pr-666 psd-pr-673 psd-pr-731 psd-pr-749 psd-pr-769 psd-pr-785 psd-pr-800 psd-pr-803 psd-pr-805 psd-pr-809 psd-pr-810 psd-pr-811 psd-pr-816 psd-pr-861 psd-pr-870 psd-pr-895 psd-pr-906 psd-pr-908 psd-pr-913 psd-pr-917 psd-pr-918 psd-pr-919 psd-pr-920
DANGLING_REVIEW_APPS:
psd-pr-447 psd-pr-482 psd-pr-489 psd-pr-508 psd-pr-524 psd-pr-564 psd-pr-565 psd-pr-576 psd-pr-586 psd-pr-617 psd-pr-623 psd-pr-626 psd-pr-630 psd-pr-635 psd-pr-638 psd-pr-666 psd-pr-673 psd-pr-731 psd-pr-749 psd-pr-769 psd-pr-785 psd-pr-800 psd-pr-803 psd-pr-805 psd-pr-809 psd-pr-810 psd-pr-811 psd-pr-895
PSD review apps after cleaning action run
ACTIVE_PRS:
psd-pr-921 psd-pr-920 psd-pr-919 psd-pr-918 psd-pr-917 psd-pr-913 psd-pr-908 psd-pr-906 psd-pr-870 psd-pr-861 psd-pr-816
REVIEW_APPS:
psd-pr-816 psd-pr-861 psd-pr-870 psd-pr-906 psd-pr-908 psd-pr-913 psd-pr-917 psd-pr-918 psd-pr-919 psd-pr-920 psd-pr-921
DANGLING_REVIEW_APPS:

I wonder why https://github.com/UKGovernmentBEIS/beis-opss-psd/blob/master/.github/workflows/review-apps-delete.yml is not doing this already.
CF v7 API is stable now so we can change all cf7 usage to cf.

The one/off deletion is currently working, but if it fails once/for a while the rev-apps stay there for the eternity...
I guess at some point we can just leave the schedule search & clean to avoid duplication.