Closes #362 Added libwebp package

I've followed this guide
step by step carefully. Yes

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/mchiasson/hunter/build/1.0.1
https://travis-ci.org/mchiasson/hunter/builds/????

I have submitted CI configs to https://github.com/ingenue/hunter targeting pkg.template branch,
see this merged pull request https://github.com/ingenue/hunter/pull/203

My change will resolve this "New package" request: https://github.com/ruslo/hunter/issues/362

Thanks, will be good to add this to OpenCV.
By the way, I think you are meant to change those Yes/No to Yes or No and remove the parts that aren't relevant from the template.

@xsacha yup! OpenCV and also SDL_image, which also can make use of WebP. ;-)
Yes, I will change the Yes/No soon. It is my very first contribution to hunter, and I will make sure to do it all by your standards.

Note to self:  Missing hunter/docs/packages/pkg/WebP.rst

Here is the links to the Travis/AppVeyor with status "All passed"

I don't see any job with status "Passed", they all failed.

sorry @ruslo I'm still trying to figure out how to setup my travis-ci and AppVeyor here.. something is misconfigured on my end.

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3421
https://travis-ci.org/ingenue/hunter/builds/352327079?utm_source=github_status&utm_medium=notification

Uploading:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.3425
https://travis-ci.org/ingenue/hunter/builds/352346134?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.20.17


Improoved Docs

Hi All
I added some documentation:

Explicit magic constant
Remove the last warning while running the tests
Document the development with rustup

Best,
Stefan

So it turns out that libc < 0.2.40 require rust 1.13.0 or later.
@frewsxcv Should we up our requirements too?

Yeah, I think it's fine to bump to 1.13.0

Also FYI, I just gave you 'owner' privileges for this GH Org

Perfect.
Thank you for the access :)
bors r+


Added value to TransactionReceipt

Adding the value to the TransactionReceipt class. Since this is part of a receipt, users could need it when for example constructing a transaction overview page. Not only addresses are needed, but also the value being sent within the tx. Please leave feedback if there is anything wrong.

the change look good. I'll propagate the change to propeller ethj & web3j so that the mapping is done right there


Add GitHub resources

This moves clickops management of GitHub resources into terraform.

Resolves #70.

👏🏼 Thanks @davidkelliott. I've already imported them 👍🏼


Re-enable dust threshold checks

for https://github.com/lbryio/lbrycrd/issues/25
undos https://github.com/lbryio/lbrycrd/commit/a6984a9d72f9231ff850050b0193342a1ce8c043

lowering dust threshold to 1, to not break lbrynet and still have some spam protection

This should not be merged until lbrynet has been modified so that it will never try to create a txout with a value of 0.

https://github.com/lbryio/lbry/ related issue: https://github.com/lbryio/lbry/issues/138

These changes LGTM; merging.


I just made a goal

make mob no only avoid the specified entity

you can try to use this goal
this.goalSelector.addGoal(2, new AvoidAndApproachTargetGoal(this, 1.2f, 90, 45, 7.5));

for example:
iceologer cannot avoid guard (guard villager)
use it goal :
iceologer can avoid guard (guard villager)


Correction for raw affiliation Claude Bernard Lyon 1 University, CNRS UMR 5239 ENS – HCL, Lyon-Sud Medicine Faculty, Lyon, France

Correction needed for raw affiliation Claude Bernard Lyon 1 University, CNRS UMR 5239 ENS – HCL, Lyon-Sud Medicine Faculty, Lyon, France
raw_affiliation_name: Claude Bernard Lyon 1 University, CNRS UMR 5239 ENS – HCL, Lyon-Sud Medicine Faculty, Lyon, France
new_rors: 01502ca60;029brtt94;02feahw73;01bj4fd12
previous_rors: 01502ca60;029brtt94;02feahw73
works_examples: W2068851836
contact: 36fa46520b206c7d243da614e9836b6b:c291c8628a42b57f2dd822dee44f @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


All Rigs Price and Price per Slot Blank

Fixed! This was likely due to our scanners needing to be leveled before going online for this patch


Added “Notable” to the list of users

Thanks for merging 👍 I'll probably send a second PR for changing the url if that's not too much trouble, as I'm in the process of launching the actual website of the app.


docs(example): Add an example to persist theme with MUI and HTTP cookie

Using Remix to create a persistent MUI theme switcher with HTTP cookie.

Hi! We do have a Dark Mode example in the works and it's pretty extensive: #688
If you want to make a simple MUI example that would be fine. I just think including all the dark mode/cookie stuff is duplicate work here. Would you like to simplify this?

Yes, that makes sense, I wasn't aware of the dark mode example being in the works so I hacked this one together. You guys are doing an awesome job, just love Remix, haven't used web standards with React before lol. It's new and exciting!!

Thank you for understanding! We're so happy that folks like you are willing to contribute. It makes the whole community better. Thanks for taking part!


Static method attribute missing from jitclasses inside jitted functions

A static method inside a jitclass can't be accessed as a class attribute inside a jitted function (outside of the class definition)
import numba as nb

@nb.experimental.jitclass
class Fraction:
    numerator: int
    denominator: int

    def __init__(self, numerator, denominator):
        self.numerator = numerator
        self.denominator = denominator

    @staticmethod
    def from_int(val):
        return Fraction(val, 1)

@nb.jit(nopython=True)
def test():
    return Fraction.from_int(3)

test()

produces
TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Unknown attribute 'from_int' of type jitclass.Fraction#7f36cff038d0<numerator:int64,denominator:int64>

File "../../../../../../tmp/ipykernel_12883/2473870322.py", line 4:
<source missing, REPL/exec in use?>

During: typing of get attribute at /tmp/ipykernel_12883/2473870322.py (4)

File "../../../../../../tmp/ipykernel_12883/2473870322.py", line 4:
<source missing, REPL/exec in use?>

Interesting, I can reproduce this. If I use an instance however it works, but I guess that defies the point of having a staticmethod.
@nb.jit(nopython=True)
def test():
    return Fraction(23, 42).from_int(3)

print(test())


Clicking on "CRLF" does not change line endings

Atom 1.0.19 for Windows:
When I click on "CRLF" in the status bar, a small pop-up opens, which lets me choose between LF and CRLF, but even when I click on LF, the line ending style sticks to LF.
In this way, the editor is unusable, because many Unix-programs can not process textfiles with CRLF endings.

but even when I click on LF, the line ending style sticks to LF.

So when you click LF in the pop-up menu, the line-endings should change to LF. Is this not what you are seeing?

On Tue, Oct 13, 2015, at 18:35, Max Brunsfeld wrote:

but even when I click on LF, the line ending style sticks to LF.

So when you click LF in the pop-up menu, the line-endings should change
to LF. Is this not what you are seeing?

Exactly. However, I have narrowed down the bug a bit: This erroneous
behaviour occurs only, when the document is still "untitled". If I open
an existing document, the line ending style can be changed.
Aside from this, I find it pretty inconvenient to explicitly set the
line ending style for every document. By far the majority of our files
have LF endings, and it would make sense to have the possibility to
define this as a default value.
Ronald

@rovf I believe this has just been addressed, via https://github.com/atom/line-ending-selector/pull/7!
In the next release of Atom, there will be a new setting line-ending-selector.defaultLineEnding that you can set to either LF, CRLF, or OS Default.

@rovf After the next release, please let me know if this feature does not solve your problem, and we can reopen this issue.

On Wed, Oct 14, 2015, at 18:22, Max Brunsfeld wrote:

@rovf I believe this has just been addressed, via
https://github.com/atom/line-ending-selector/pull/7!
In the next release of Atom, there will be a new setting
line-ending-selector.defaultLineEnding that you can set to either LF,
CRLF, or OS Default.

I think we have two unrelated issues here:

One is the (important) feature, that we want to control the default
line ending for new documents; this is addressed by pull request 7

The other one is the bug, that we can not change the default line
ending of a "untitled" document. This is the one which was addressed by
my issue.

This means that even with pull request 7 implemented, I would still face
a problem when I want to create a new document with line endings which
are different from the default. I would have to save it first with the
default line ending, and only then I could change the endings.
Ronald


GEOSRelate_r exceptions handled gracefully. Fix for #294.

This PR addresses issue #294. GEOSRelate_r returns a NULL pointer on exception, which isn't currently caught by Shapely resulting in a segmentation fault when an attempt is made to access the result. A wrapper has been added around the existing errcheck function, which checks for this and raises a TopologicalError if needed.

I'm all in favor of this. Thanks, @snorfalorpagus!

Yup, these were essentially the changes I was thinking of.

@snorfalorpagus my fault for branching before merging this, but can you open a new PR from your branch with maint-1.5 as the target branch? I'll merge it as soon as you do.


Add additional_information in the QR-Code

Hi @mitosch ,
Thank you for your great Gem!
I would like to add the additional_information in the QR-Code. I saw that it is in the open list in the TODOs.md file. Is there any technical difficulty in doing this? I would like to provide a PR on this. But before I start, I would like to understand if there is a technical reason why this is not done in the current version?

Here is my proposition to add unstructured message and bill information (both are additional information): https://github.com/mitosch/prawn-swiss_qr_bill/pull/2

Hi @noefroidevaux
Thank you for your message and the pull request, I'll look into it. Honestly, I did not read deep into the specifications of the additional_information, there was something about one-two liner's if I remember correctly.
I will check the pull-request and test some QR's in the validation portal.

Hi @mitosch ,
Thanks to you for this Gem!


python3Packages.build: specify mainProgram

Description of changes
Old and busted:
$ nix shell nixpkgs#python3Packages.build -c pyproject-build --version

New hotness:
$ nix run .#python3Packages.build -- --version
build 0.10.0 (/nix/store/i96f8azwspp9c5ya6m35ihdy62mk8j8g-python3.10-build-0.10.0/lib/python3.10/site-packages/build)

Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
23.05 Release Notes (or backporting 22.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.

Result of nixpkgs-review pr 230919 run on x86_64-linux 1

Thank you!


add the attribute repository to the Ros package model

superseded by https://github.com/ipa320/ros_model_parser/pull/28


Added check for duplicate dataframe columns

[x] Addresses https://github.com/ioam/holoviews/issues/2476
[x] Adds unit test

Ready to merge.

Some issues with test data, seems some bad data was captured or merged at some point causing a bokeh elements test to fail, going to rebuild and merge this to keep other stuff moving. I've addressed all the comments and it's not a controversial PR.


Is it possible to add more transactions into a bundle?

// max per bundle is 5 transactions
txns := make([]*solana.Transaction, 0, 5)

No, this is decided by Jito. However you are free to pass as many instructions as you want in a tx.


BibUpload: creation_date based on incoming 005

Adjusts creation_date based on incoming 005 tag.
(closes #1604)

Signed-off-by: Samuele Kaplun<EMAIL_ADDRESS>

Have to amend regression tests

OK. Done.

Applied your suggestions related to naming things. Let's see if this is good :-)

Reviewed-by: Tibor Simko<EMAIL_ADDRESS>Thanks, amended commit log message and merged as 38bc4c38a3d827024964108aff18c3b5911c89c6.


Unknown virtual env/environment (venv) is being queried for by Jupyter extension

Discussed in https://github.com/microsoft/vscode-python/discussions/20431

Originally posted by drorata December 25, 2022
When opening a py file I see in the logs:
Experiment 'pythonaacf' is active
Experiment 'pythonSurveyNotificationcf' is active
LSP Notebooks experiment is enabled
LSP Notebooks interactive window support is enabled
Python interpreter path: ~/.poetry_envs/foo-cv-BPVTkgqj-py3.11/bin/python
> poetry env list --full-path
cwd: .
> ~/.pyenv/versions/3.10.4/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.pyenv/versions/3.11.1/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> conda info --json
> ~/.pyenv/versions/3.7.13/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.pyenv/versions/3.9.13/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> . ~/.poetry_envs/foo-cv-BPVTkgqj-py3.11/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/printEnvVariables.py
> ~/.poetry_envs/username-cv-lqqRfM4F-py3.11/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.poetry_envs/fast-api-sql-example-hJw5i7sx-py3.11/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.poetry_envs/foo-cv-BPVTkgqj-py3.11/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.poetry_envs/kumsitz-lib-iVmOjJvt-py3.10/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.poetry_envs/pyspark-playground-Dg6oNfQx-py3.10/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.poetry_envs/stocks-playground-bIdRsd_o-py3.10/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> /usr/bin/python3 ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> /opt/homebrew/bin/python3 ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> /opt/homebrew/bin/python3.11 ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
> ~/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
[ERROR 2022-11-23 8:14:35.526]: [Error: Command failed: /Users/username/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
/bin/sh: /Users/username/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python: No such file or directory

	at ChildProcess.exithandler (node:child_process:408:12)
	at ChildProcess.emit (node:events:526:28)
	at maybeClose (node:internal/child_process:1092:16)
	at Socket.<anonymous> (node:internal/child_process:451:11)
	at Socket.emit (node:events:526:28)
	at Pipe.<anonymous> (node:net:687:12)] {
  killed: false,
  code: 127,
  signal: null,
  cmd: '/Users/username/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py'
}
Starting Pylance language server.
Extension search path: /Users/username/.vscode/extensions
> ~/.poetry_envs/foo-cv-BPVTkgqj-py3.11/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/linter.py -p flake8 /opt/homebrew/bin/flake8 --max-line-length=120 ./foo_cv/__init__.py
cwd: .
##########Linting Output - flake8##########

> ~/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
[ERROR 2022-11-23 8:14:37.540]: [Error: Command failed: /Users/username/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py
/bin/sh: /Users/username/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python: No such file or directory

	at ChildProcess.exithandler (node:child_process:408:12)
	at ChildProcess.emit (node:events:526:28)
	at maybeClose (node:internal/child_process:1092:16)
	at ChildProcess._handle.onexit (node:internal/child_process:302:5)] {
  killed: false,
  code: 127,
  signal: null,
  cmd: '/Users/username/.local/share/virtualenvs/test-project-GV0hGqPR/bin/python /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/get_output_via_markers.py /Users/username/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/interpreterInfo.py'
}
> /opt/homebrew/bin/black --diff --quiet ./foo_cv/__init__.py.fcaa6f612d7121d453663cbc59080266.tmp
cwd: .
Extension search path: /Users/username/.vscode/extensions
> ~/.poetry_envs/foo-cv-BPVTkgqj-py3.11/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/linter.py -p flake8 /opt/homebrew/bin/flake8 --max-line-length=120 ./foo_cv/__init__.py
cwd: .
##########Linting Output - flake8##########

> ~/.poetry_envs/foo-cv-BPVTkgqj-py3.11/bin/python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear tests
cwd: .

I totally don't understand where and why vscode uses the environment /Users/username/.local/share/virtualenvs/test-project-GV0hGqPR? It might be related to the bug reported here https://github.com/microsoft/pylance-release/issues/3784.

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to verbose
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel.

Thanks for the suggestion @DonJayamanne. I inspected the logs and I made me do the following:
In the logs, I found something like Updating cache with Local kernels startUsingLocalKernelSpec which made me look for the old virtual environment in the Jupyter's directory. I found reference to this old environment in ~/Library/Jupyter/kernels/test-project/kernel.json. Next I deleted the whole directory ~/Library/Jupyter/kernels/test-project/.
Otherwise, I scanned all the locations indicated by jupyter --paths and found no further mentioning of the virtual environment test-project-GV0hGqPR.
After that, I restarted vscode and opened a notebook. The logs still contain a reference to the environment. You can find the new logs in this gist.

@drorata
Please could you try the following:

Add a setting into your user settings file as follows
"jupyter.development": true,
Reload VS Code
Look for the command Jupyter (Dev): Clear Cache
Try that a few times and reload vscode
Check the logs again, and if the issue persists please could you share the logs again

I fail to do what you ask. When trying to adjust the setting it looks like so:

Note, it is is "pale".
When looking then, after reload for some "cache" related command, all I see are:

Sorry, you are right that will not work.
Could you instead please try the following:

Add the following setting into your settings file

"notebook.kernelPicker.type": "mru",

Reload VC Code
Go into the kernle picker, and select Select Another Kernel -> Local Jupyter Kernel
On the top right hand corner of the quick pick click the Refresh icon
Wait for everything to get updated,
Reload VS Code and then let me know if that still appears in the logs
If it still appears there, pelase upload the new logs (after refreshing and re-loading vscode)

Step 1: I added "notebook.kernelPicker.type": "mru", to my user's settings.json and then reloaded (=quit and open again).
Step 2: I opened a notebook and clicked the Select Another Kernel. In there I didn't have the option Local Jupyter Kernel; the closest is Local Kernel Specs...

I clicked this option.
Step 3: In there, the offending kernel was present:

It was still there also after refreshing the list.
Step 4: Here are the new logs.

Thanks again for the logs and for your patience,
please could you install VS Code insiders and the latest pre-release version of the Jupyter extension.
And try that once again.
I believe this issue should be resolved in the latest pre-release version (which currently only runs in vscode insiders).

I installed the insider version, installed the Jupyter extension. Closed and opened the editor, open the Jupyter output and opened a notebook. The offending virtual environment was not to be found in the logs!

The offending virtual environment was not to be found in the logs!

Thanks for getting back, this confirms the bug has been fixed and will be shipped with the next release.


Removes operatorkit dependency

Closes https://github.com/giantswarm/roadmap/issues/3731
Checklist

[x] Update changelog in CHANGELOG.md.

okay merging here (i'm not going to release), ping me if there's anything else i can help with. thanks! <3


dart_vm_initializer.cc fails with No element when taking snapshot

When run from macos DevTools exception looks like this:
flutter: [ERROR]: [zoneGuarded]: Bad state: No element
flutter: [ERROR]: [PlatformDispatcher]: Bad state: No element
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Bad state: No element
#0 ListMixin.reduce (dart:collection/list.dart:223:22)
https://github.com/flutter/devtools/pull/1 DerivedData._setSelections
diff_pane_controller.dart:423
https://github.com/flutter/devtools/pull/2 DerivedData._updateValues
diff_pane_controller.dart:349
https://github.com/flutter/devtools/pull/3 DiffPaneController.takeSnapshot
diff_pane_controller.dart:78

Repro:

Run attached application on macos
Connect DevTools on macos to the app
Take snapshot using Memory > Diff Snapshots
Observe exception in the DevTools debug console

dart_developer_timeline.zip

Peer issue in DevTools: https://github.com/flutter/devtools/issues/5510

It seems it's native dart problem


Add atexit() handler to unmount the filesystem on fatal X error

A couple of our guys log out of their remote sessions every night, rather than simply disconnecting and reconnecting.
I'd had reports that when this is done, the chansrv process can exit without unmounting the FUSE filesystem. When the user logs in again, the FUSE system cannot be mounted over the old one so the user loses remote drives and copy-paste.
Since this is fairly common, I attached a debugger to chansrv and set a breakpoint on _exit. Here's what I got (CentOS 7.4):-
#0  0x00007f7a1d8df4f0 in _exit () from /lib64/libc.so.6
#1  0x00007f7a1d858a2b in __run_exit_handlers () from /lib64/libc.so.6
#2  0x00007f7a1d858ab5 in exit () from /lib64/libc.so.6
#3  0x00007f7a1de65ee5 in _XDefaultIOError () from /lib64/libX11.so.6
#4  0x00007f7a1de6611e in _XIOError () from /lib64/libX11.so.6
#5  0x00007f7a1de63acd in _XEventsQueued () from /lib64/libX11.so.6
#6  0x00007f7a1de555dd in XPending () from /lib64/libX11.so.6
#7  0x00005563dd22927a in xcommon_check_wait_objs ()
#8  0x00005563dd2130bd in channel_thread_loop ()
#9  0x00007f7a1ee4ee25 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f7a1d91834d in clone () from /lib64/libc.so.6

So this is clearly a fatal X error.
I've had a poke-around and there was a handler which could have been used to pick up on this which was removed by @jsorg71  in commit e11dce79dc8708cd86a8917c16c16c9bf4beb45b back in 2009 when the code was much simpler!
Since the original X Error handler was removed for what were good reasons at the time, I've gone for another approach and used the standard C library atexit() call to add a handler to unmount the filesystem at exit if for some reason it's still mounted.
The approach works in my testing, but I'm not completely happy with it because of the commit referred to above. Maybe a better approach might be to re-instate the standard X11 error handler and see what happens now that nearly a decade has passed.

@speidy what do you think of this? LGTM

I'm not sure i like the atexit handler.
moreover, its interesting to catch those crashes,
@jsorg71 why did u remove XSetIOErrorHandler in  e11dce7 ?

No enough time to test, let's merge after release.

I can quite remember why I removed them.  I think because chansrv would not exit if the Xserver exited.  We can return them as long as everything gets cleaned up ok.

I'm also not keen on using atexit() if a better approach is available.
I'll rejig the patch to re-instate the XSetIOErrorHandler() call, and callback to a handler in chansrv.c. That can do any deallocating it needs to.

Patch now uses a callback from xcommon.c to chansrv.c when the X server fails to allow chansrv.c to cater for this specific event.
Tested on CentOS 7.4 with an explicit kill of the X server.

Looks better.

Let's merge and test.

rebased and squashed for merge.

wonderful, thank you!


Add RISC-V Advanced Core Local Interruptor support

The RISC-V ACLINT is backwards compatible with the RISC-V CLINT, but the device tree properties are different.

@antonblanchard - Looks good as a starting point for AIA and it's nice that it's mostly backward compatible.
The only additional thing I would request here is to ensure that some platform (maybe qemu_virt_riscv64?) includes riscv,aclint-mtimer somewhere in the DT and that some testsuite runs with it enabled.
No single test is really jumping out at me, but given that we also anticipate seeing APLIC, AIPIs and so on, maybe a new one under tests/arch/riscv/advanced_interrupt_archictecture?


Incompatibility with create - com.unascribed.fabrication.mixin.i_woina.no_experience.MixinEnchantmentScreen

it says
[11:22:15] [Render thread/WARN] (Fabrication) [com.unascribed.fabrication.support.injection.FabInjector#apply] [Fabrication] FabInjector failed to find injection point for net/minecraft/class_486;method_2389(Lnet/minecraft/class_332;FII)V	Lnet/minecraft/class_746;field_7520:I
 located in com.unascribed.fabrication.mixin.i_woina.no_experience.MixinEnchantmentScreen
[11:22:15] [Render thread/WARN] (Fabrication) [com.unascribed.fabrication.support.injection.FabInjector#apply] [Fabrication] ! Force-disabling *.no_experience
[11:22:15] [Render thread/WARN] (Fabrication) [com.unascribed.fabrication.support.injection.FabInjector#apply] [Fabrication] FabInjector failed to find injection point for net/minecraft/class_486;method_2389(Lnet/minecraft/class_332;FII)V	Lnet/minecraft/class_332;method_25302(Lnet/minecraft/class_2960;IIIIII)V
 located in com.unascribed.fabrication.mixin.i_woina.no_experience.MixinEnchantmentScreen
[11:22:15] [Render thread/WARN] (Fabrication) [com.unascribed.fabrication.support.injection.FabInjector#apply] [Fabrication] ! Force-disabling *.no_experience
[11:22:15] [Render thread/INFO] (create_new_age) [org.antarcticgardens.newage.CreateNewAge#onInitialize] Hello 1.20.1 Create!

https://gist.github.com/stunlocked1/c79def4a5c77c01b8e4811ad8ce9f483
and doesnt crash when I remove fabrication

Please reproduce the crash with the absolute minimum amount of mods insalled.
Since installing just Create, Fabric API and Fabrication does not cause the crash

Please re-open if you figure out exactly what mods cause it


Update Stage URL for describe to console.dev.redhat.com

This PR makes a small change to update the URL for Staging Clusters in describe command to console.dev.redhat.com as qaprodauth.redhat.com is deprecated

/close


Red knot test unix::symlinked_module_search_path fails locally

One of the tests for red knot fails locally for me - MBP running Sonoma 14.5. Can anyone help me debug this? I assume it's not reproducible for the maintainers otherwise the tests would not be passing... Apologies in advance if I've done something silly.
Steps taken:

Pull down main.

Backtrace level 1 here

running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
running 20 tests
test move_file_to_trash ... ok
test move_file_to_workspace ... ok
test add_search_path ... ok
test hard_links_in_workspace ... ok
test directory_moved_to_workspace ... ok
test hard_links_to_target_outside_workspace ... ok
test changed_file ... ok
test unix::symlink_target_outside_watched_paths ... ignored, FSEvents doesn't emit change events for symlinked directories outside of the watched paths.
test directory_moved_to_trash ... ok
test deleted_file ... ok
test new_file ... ok
test new_ignored_file ... ok
test directory_renamed ... ok
test directory_deleted ... ok
test remove_search_path ... ok
test rename_file ... ok
test unix::changed_metadata ... ok
test unix::symlink_inside_workspace ... ok
test search_path ... ok
test unix::symlinked_module_search_path ... FAILED
failures:
---- unix::symlinked_module_search_path stdout ----
thread 'unix::symlinked_module_search_path' panicked at crates/red_knot/tests/file_watching.rs:49:14:
Expected watch changes but observed none.
stack backtrace:
0: rust_begin_unwind
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:652:5
1: core::panicking::panic_fmt
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:72:14
2: core::panicking::panic_display
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:262:5
3: core::option::expect_failed
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/option.rs:1995:5
4: core::option::Option::expect
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/option.rs:898:21
5: file_watching::TestCase::stop_watch
at ./tests/file_watching.rs:48:9
6: file_watching::unix::symlinked_module_search_path
at ./tests/file_watching.rs:1210:23
7: file_watching::unix::symlinked_module_search_path::{{closure}}
at ./tests/file_watching.rs:1150:42
8: core::ops::function::FnOnce::call_once
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
9: core::ops::function::FnOnce::call_once
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
failures:
unix::symlinked_module_search_path
test result: FAILED. 18 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 10.24s

Full backtrace here

running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
running 20 tests
test deleted_file ... ok
test hard_links_to_target_outside_workspace ... ok
test add_search_path ... ok
test changed_file ... ok
test hard_links_in_workspace ... ok
test directory_moved_to_workspace ... ok
test directory_renamed ... ok
test unix::symlink_target_outside_watched_paths ... ignored, FSEvents doesn't emit change events for symlinked directories outside of the watched paths.
test directory_deleted ... ok
test rename_file ... ok
test new_ignored_file ... ok
test move_file_to_workspace ... ok
test new_file ... ok
test move_file_to_trash ... ok
test directory_moved_to_trash ... ok
test remove_search_path ... ok
test unix::symlink_inside_workspace ... ok
test unix::changed_metadata ... ok
test search_path ... ok
test unix::symlinked_module_search_path ... FAILED
failures:
---- unix::symlinked_module_search_path stdout ----
thread 'unix::symlinked_module_search_path' panicked at crates/red_knot/tests/file_watching.rs:49:14:
Expected watch changes but observed none.
stack backtrace:
0:        0x100854edc - std::backtrace_rs::backtrace::libunwind::trace::h6196ef3b0a4e77ef
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5
1:        0x100854edc - std::backtrace_rs::backtrace::trace_unsynchronized::hac375eab426f00dd
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2:        0x100854edc - std::sys_common::backtrace::_print_fmt::h2a4f1f15852b7d46
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:68:5
3:        0x100854edc - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h205eab4daa59a56a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:44:22
4:        0x100873004 - core::fmt::rt::Argument::fmt::h391b30ab7a26d7be
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/fmt/rt.rs:165:63
5:        0x100873004 - core::fmt::write::ha28d0fbf1a1eeba9
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/fmt/mod.rs:1168:21
6:        0x100851a18 - std::io::Write::write_fmt::hdb161f22835a409d
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/io/mod.rs:1835:15
7:        0x100854d34 - std::sys_common::backtrace::_print::hfe43851cb14e36df
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:47:5
8:        0x100854d34 - std::sys_common::backtrace::print::hb748761a345859f9
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:34:9
9:        0x100856358 - std::panicking::default_hook::{{closure}}::h6cb9ca91838de054
10:        0x100855f6c - std::panicking::default_hook::h83345dc5126de57b
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:295:9
11:        0x1002b3e20 - <alloc::boxed::Box<F,A> as core::ops::function::Fn>::call::h85507dacc99e5a3f
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/alloc/src/boxed.rs:2077:9
12:        0x1002b3e20 - test::test_main::{{closure}}::hcc5ce573e6a37758
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/test/src/lib.rs:137:21
13:        0x100856c2c - <alloc::boxed::Box<F,A> as core::ops::function::Fn>::call::h31310631bda73223
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/alloc/src/boxed.rs:2077:9
14:        0x100856c2c - std::panicking::rust_panic_with_hook::h9305dc63490c537b
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:799:13
15:        0x100856640 - std::panicking::begin_panic_handler::{{closure}}::h0d6c6c01f5801c1a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:664:13
16:        0x100855360 - std::sys_common::backtrace::__rust_end_short_backtrace::h2ace9f7ada66a76a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:171:18
17:        0x1008563b0 - rust_begin_unwind
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:652:5
18:        0x1008a4ff4 - core::panicking::panic_fmt::hf3031f82c202a80d
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:72:14
19:        0x1008a4fc8 - core::panicking::panic_display::h7da8db29ac24753f
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panicking.rs:262:5
20:        0x1008a4fc8 - core::option::expect_failed::hadb2936a80a68c9a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/option.rs:1995:5
21:        0x100257e5c - core::option::Option::expect::h4c0708994c2aebf8
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/option.rs:898:21
22:        0x100249344 - file_watching::TestCase::stop_watch::hbb551b3e9d6f1b65
at /Users/dmbp/Documents/dev/contrib/ruff/crates/red_knot/tests/file_watching.rs:48:9
23:        0x1002701ec - file_watching::unix::symlinked_module_search_path::hc717146df6c92744
at /Users/dmbp/Documents/dev/contrib/ruff/crates/red_knot/tests/file_watching.rs:1210:23
24:        0x1002802e4 - file_watching::unix::symlinked_module_search_path::{{closure}}::hce6a9bbdce7e82e1
at /Users/dmbp/Documents/dev/contrib/ruff/crates/red_knot/tests/file_watching.rs:1150:42
25:        0x100274bac - core::ops::function::FnOnce::call_once::h965249ecfe5650cd
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
26:        0x1002b7adc - core::ops::function::FnOnce::call_once::h6288de1275a81f7e
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
27:        0x1002b7adc - test::__rust_begin_short_backtrace::h2a106babef6b70ed
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/test/src/lib.rs:625:18
28:        0x1002b7418 - test::run_test_in_process::{{closure}}::hcf2705e41b3d0d01
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/test/src/lib.rs:648:60
29:        0x1002b7418 - <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once::had2dc500529c8ec1
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panic/unwind_safe.rs:272:9
30:        0x1002b7418 - std::panicking::try::do_call::h55845621067c8dc2
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:559:40
31:        0x1002b7418 - std::panicking::try::h40ce094ada304bf3
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:523:19
32:        0x1002b7418 - std::panic::catch_unwind::h8d4bb94e8f7797ec
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panic.rs:149:14
33:        0x1002b7418 - test::run_test_in_process::hb7392a758f6c858a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/test/src/lib.rs:648:27
34:        0x1002b7418 - test::run_test::{{closure}}::h0b3dae94fb1e3623
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/test/src/lib.rs:569:43
35:        0x100289998 - test::run_test::{{closure}}::h349b61f0e92bb544
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/test/src/lib.rs:599:41
36:        0x100289998 - std::sys_common::backtrace::rust_begin_short_backtrace::h255ef5cb8f07346b
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys_common/backtrace.rs:155:18
37:        0x10028db6c - std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}::h9d83ff3086d2a361
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/thread/mod.rs:542:17
38:        0x10028db6c - <core::panic::unwind_safe::AssertUnwindSafe as core::ops::function::FnOnce<()>>::call_once::hfbc6f1752590fbce
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/panic/unwind_safe.rs:272:9
39:        0x10028db6c - std::panicking::try::do_call::h39bf94ad14a8e34a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:559:40
40:        0x10028db6c - std::panicking::try::h8605b5055f4f5eba
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panicking.rs:523:19
41:        0x10028db6c - std::panic::catch_unwind::he873874fb889dc4a
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/panic.rs:149:14
42:        0x10028db6c - std::thread::Builder::spawn_unchecked::{{closure}}::h5cd58b11a9c427ba
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/thread/mod.rs:541:30
43:        0x10028db6c - core::ops::function::FnOnce::call_once{{vtable.shim}}::h02bb5b23eebe928d
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/core/src/ops/function.rs:250:5
44:        0x10085bcb0 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once::h602281de57923cf1
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/alloc/src/boxed.rs:2063:9
45:        0x10085bcb0 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce>::call_once::hd3a85b6b9254c879
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/alloc/src/boxed.rs:2063:9
46:        0x10085bcb0 - std::sys::pal::unix::thread::Thread::new::thread_start::h9e081ad7dac4e4c5
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library/std/src/sys/pal/unix/thread.rs:108:17
47:        0x184552f94 - __pthread_joiner_wake
failures:
unix::symlinked_module_search_path
test result: FAILED. 18 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 10.32s

I think there's just a lot of nuance to these tests across different systems. Doubt you did anything wrong!
\cc @MichaReiser

https://github.com/astral-sh/ruff/pull/12634 is up to fix this! Sorry for the bother, we'll have it sorted soon

No problem at all - thanks!

Yes sorry for the inconvenience and thanks for raising it.
Those tests are driving me crazy. I very much hope that my last PR finally gets them into a non-flaky state where they pass on (all?) platforms.


zh-trans: add docs/reference/federation/_index.html

@chenrui333 is this PR against the wrong directory? I see en not just in the PR label but also in the file path, but there's localized content in the file itself.
/hold

@Bradamant3 For Chinese localization, we always use release-1.12 as base branch.

/hold cancel

/remove-language en

/lgtm
/approve
The PR doesn't have to include a change to the English content. Please avoid this next time.


Unequal durations of notes in a chord

From craigsapp on May 21, 2013 11:46:31
Coding standard-of-practice to add to documentation: If a <chord> contains notes with unequal score durations (@dur), then the <chord> parent element should have @-dur giving the intended duration of the chord in the graphic music notation.
Example:
<chord dur="4">
<note dur="4">
<note dur="2">
</chord>
The attached example demonstrates a musical example which needs this convention (measure 14).
Attachment: chordduration.pdf
Original issue: http://code.google.com/p/music-encoding/issues/detail?id=157

From<EMAIL_ADDRESS>on May 30, 2014 08:53:45
Labels: Component-Docs

From andrew.hankinson on September 12, 2014 04:39:02
The MEI Guidelines define a chord as: "A simultaneous sounding of two or more notes in the same layer with the same duration."
The same effect can be achieved by using a different <layer />, with specific stem directions.
I'm going to close this issue. Re-open if there are objections.
Status: WontFix


[DOC] updating the README for the 2.0 release

This PR updates the README for the 2.0 release:

2.0 code snippets
updated community and contribution links
updated documentation references

Codecov Report
Patch coverage has no change and project coverage change: -0.44% :warning:

Comparison is base (84a7e27) 71.44% compared to head (444d325) 71.01%.
Report is 2 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   71.44%   71.01%   -0.44%
==========================================
  Files          93       91       -2
  Lines        4956     4861      -95
  Branches      898      800      -98
==========================================
- Hits         3541     3452      -89
- Misses       1180     1188       +8
+ Partials      235      221      -14

see 7 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Logger::Logfile::Error: Log File at '/root/Backup/log/backup.log' is not writable

What went wrong?
Starting with an existing backup.log file, I get the following error
[2021/09/30 11:30:11][error] CLI::Error
[2021/09/30 11:30:11][error] --- Wrapped Exception ---
[2021/09/30 11:30:11][error] Logger::Logfile::Error: Log File at '/root/Backup/log/backup.log' is not writable
[2021/09/30 11:30:11][error] CLI::Error
[2021/09/30 11:30:11][error] --- Wrapped Exception ---
[2021/09/30 11:30:11][error] Logger::Logfile::Error: Log File at '/root/Backup/log/backup.log' is not writable

If I delete the log file, I get the following error:
~/Backup/log # backup perform -t backup_scada -c /root/Backup/config.rb
[2021/09/30 11:30:29][info] Performing Backup for 'Backup DB SCADA (backup_scada)'!
[2021/09/30 11:30:29][info] [ backup 5.0.0.beta.3 : ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux-musl] ]
[2021/09/30 11:30:29][info] Database::PostgreSQL Started...
[2021/09/30 11:30:29][info] Using Compressor::Gzip for compression.
[2021/09/30 11:30:29][info]   Command: '/bin/gzip'
[2021/09/30 11:30:29][info]   Ext: '.gz'
[2021/09/30 11:30:30][info] Database::PostgreSQL Finished!
[2021/09/30 11:30:30][info] Packaging the backup files...
[2021/09/30 11:30:30][info] Running system utility 'tar'...
[2021/09/30 11:30:30][info] tar:STDOUT: tar (busybox) 1.33.1
[2021/09/30 11:30:30][info] Packaging Complete!
[2021/09/30 11:30:30][info] Cleaning up the temporary files...
[2021/09/30 11:30:30][info] Storage::Local Started...
[2021/09/30 11:30:30][info] Storing '/root/dbbackup/backup_scada/2<IP_ADDRESS>.30.29/backup_scada.tar'...
[2021/09/30 11:30:30][info] Cycling Started...
[2021/09/30 11:30:30][info] Storage::Local Finished!
[2021/09/30 11:30:30][info] Cleaning up the package files...
[2021/09/30 11:30:30][info] Backup for 'Backup DB SCADA (backup_scada)' Completed Successfully in 00:00:01
Traceback (most recent call last):
        14: from /usr/local/bundle/bin/backup:23:in `<main>'
        13: from /usr/local/bundle/bin/backup:23:in `load'
        12: from /usr/local/bundle/gems/backup-5.0.0.beta.3/bin/backup:5:in `<top (required)>'
        11: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'
        10: from /usr/local/bundle/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
         9: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
         8: from /usr/local/bundle/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
         7: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/cli.rb:182:in `perform'
         6: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger.rb:101:in `clear!'
         5: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger.rb:165:in `start!'
         4: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger.rb:165:in `each'
         3: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger.rb:166:in `block in start!'
         2: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger.rb:166:in `new'
         1: from /usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger/logfile.rb:80:in `initialize'
/usr/local/bundle/gems/backup-5.0.0.beta.3/lib/backup/logger/logfile.rb:106:in `setup_logfile': Logger::Logfile::Error: Log File at '/root/Backup/log/backup.log' is not writable (Backup::Logger::Logfile::Error)

After this, the logfile is created with only the first part of the last message:
[2021/09/30 11:30:29][info] Performing Backup for 'Backup DB SCADA (backup_scada)'!
[2021/09/30 11:30:29][info] [ backup 5.0.0.beta.3 : ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux-musl] ]
[2021/09/30 11:30:29][info] Database::PostgreSQL Started...
[2021/09/30 11:30:29][info] Using Compressor::Gzip for compression.
[2021/09/30 11:30:29][info]   Command: '/bin/gzip'
[2021/09/30 11:30:29][info]   Ext: '.gz'
[2021/09/30 11:30:30][info] Database::PostgreSQL Finished!
[2021/09/30 11:30:30][info] Packaging the backup files...
[2021/09/30 11:30:30][info] Running system utility 'tar'...
[2021/09/30 11:30:30][info] tar:STDOUT: tar (busybox) 1.33.1
[2021/09/30 11:30:30][info] Packaging Complete!
[2021/09/30 11:30:30][info] Cleaning up the temporary files...
[2021/09/30 11:30:30][info] Storage::Local Started...
[2021/09/30 11:30:30][info] Storing '/root/dbbackup/backup_scada/2<IP_ADDRESS>.30.29/backup_scada.tar'...
[2021/09/30 11:30:30][info] Cycling Started...
[2021/09/30 11:30:30][info] Storage::Local Finished!
[2021/09/30 11:30:30][info] Cleaning up the package files...
[2021/09/30 11:30:30][info] Backup for 'Backup DB SCADA (backup_scada)' Completed Successfully in 00:00:01

The log file is indeed writable, so I don't know why I'm getting the error message after the first backup.
What steps did you follow?

gem install backup --version 5.0.0.beta.3
backup check
backup perform -t backup_scada -c /root/Backup/config.rb

How is your copy of backup configured?
I'm using a clean config file with the header for version 5 (# Backup v5.x Configuration)
Tell us about the computer that runs the backup gem
Running inside a docker container.
ID=alpine
VERSION_ID=3.14.2
PRETTY_NAME="Alpine Linux v3.14"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://bugs.alpinelinux.org/"

ruby 2.7.4p191 (2021-07-07 revision a21a3b7d23) [x86_64-linux-musl]
Tools or services used by backup: Postgresql v13.4

I've found the problem. Don't know why, but I was creating the docker image with docker 20.10.8 and the system running that image is using docker 19.xx.... I upgraded to docker 20.10.8 and everything works correctly.
I'm closing this issue as is not related to this gem.


chore: Update all dependencies

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


id is not necessary for the upsert operation

source code link
id is not necessary for a upsert operation and id is not used.

done in PR https://github.com/Microsoft/spring-data-cosmosdb/pull/117


Global ban issue

So, I still get this error after all of your changes in this plugin:
[Exception] GlobalBan >> Exception in Execute: System.NullReferenceException: Object reference not set to an instance of an object
at unturned.ROCKS.GlobalBan.CommandBan.Execute (Rocket.Unturned.Player.RocketPlayer caller, System.String[] command) [0x00000] in :0

Please report this at https://github.com/unturnedROCKS/GlobalBan, this is not an rocket issue

oh, sorry


Graceful Shutdown - Open TCP Connection Handling is not working properly - APIM 4.0.0

Description
When there is a live traffic to the node and when performing a graceful shutdown while there is a load, the server will not properly close the active connection threads and throwing the Send Timeout error and the server shutdown process is getting hanged until the EP timeout is reached.
Steps to Reproduce

Start the pack and go to the publisher portal.
Create an API. (Endpoint Timeout should be around 60 seconds)
Configure a mock backend which was a delay around 10 seconds to send the response.
Invoke the API.
Immediately after invoking the API, try to do a graceful shutdown. (after 2-3 seconds from the API invocation) and able to see that the server is waiting to cleanup the active connection on the 8243 port.

TID: [-1234] [] [2023-08-28 20:20:17,195]  INFO {org.wso2.carbon.core.init.CarbonServerManager} - Shutdown hook triggered....
TID: [-1234] [] [2023-08-28 20:20:17,197]  INFO {org.wso2.carbon.core.init.CarbonServerManager} - Gracefully shutting down WSO2 API Manager...
TID: [-1234] [] [2023-08-28 20:20:17,223]  INFO {org.wso2.carbon.core.ServerManagement} - Starting to switch to maintenance mode...
TID: [-1234] [] [2023-08-28 20:20:17,223]  INFO {org.apache.synapse.transport.passthru.PassThroughHttpListener} - Stopping Pass-through HTTP Listener..
TID: [-1234] [] [2023-08-28 20:20:17,224]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pausing  IO Reactor bind for port 8280
TID: [-1234] [] [2023-08-28 20:20:17,225]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Shutting down IO Reactor bind for port 8280
TID: [-1234] [] [2023-08-28 20:20:17,226]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - HTTP-Listener I/O dispatcher Listener shutdown.
TID: [-1234] [] [2023-08-28 20:20:17,227]  INFO {org.apache.synapse.transport.passthru.PassThroughHttpMultiSSLListener} - Stopping Pass-through HTTPS Listener..
TID: [-1234] [] [2023-08-28 20:20:17,227]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Pausing  IO Reactor bind for port 8243
TID: [-1234] [] [2023-08-28 20:20:17,228]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Waiting to cleanup active connections on port 8243: 1

When sending the response from the backend to the gateway after 10 seconds delay, be able notice the below exception.

TID: [-1234] [] [2023-08-28 20:20:25,828] DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << HTTP/1.1 200 OK
TID: [-1234] [] [2023-08-28 20:20:25,829] DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Content-Type: application/json; charset=utf-8
TID: [-1234] [] [2023-08-28 20:20:25,829] DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Content-Length: 3874
TID: [-1234] [] [2023-08-28 20:20:25,830] DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Date: Mon, 28 Aug 2023 14:50:25 GMT
TID: [-1234] [] [2023-08-28 20:20:25,830] DEBUG {org.apache.synapse.transport.http.headers} - http-outgoing-1 << Connection: keep-alive
TID: [-1234] [] [2023-08-28 20:20:25,849] ERROR {org.apache.synapse.transport.passthru.TargetHandler} - Exception occurred while processing response java.util.concurrent.RejectedExecutionException: Task org.apache.axis2.transport.base.threads.NativeWorkerPool$1@5d5ed837 rejected from org.apache.axis2.transport.base.threads.Axis2ThreadPoolExecutor@694a2f7c[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 2]
	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379)
	at org.apache.axis2.transport.base.threads.NativeWorkerPool.execute(NativeWorkerPool.java:169)
	at org.apache.synapse.transport.passthru.TargetHandler.responseReceived(TargetHandler.java:536)
	at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:255)
	at org.apache.synapse.transport.http.conn.LoggingNHttpClientConnection.consumeInput(LoggingNHttpClientConnection.java:115)
	at org.apache.synapse.transport.passthru.ClientIODispatch.onInputReady(ClientIODispatch.java:83)
	at org.apache.synapse.transport.passthru.ClientIODispatch.onInputReady(ClientIODispatch.java:41)
	at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
	at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
	at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:591)
	at java.lang.Thread.run(Thread.java:750)
TID: [-1234] [] [2023-08-28 20:20:25,853] ERROR {org.apache.synapse.transport.passthru.TargetHandler} - Unexpected error.

After this error, the gateway paused the shutdown process until the EP timeout (60 seconds) reach and after that, the server continue the shutdown process as below. In this step, the gateway returned the 500 Internal Server Error with the Send Timeout error to the client side even the backend returned the 200 response.

TID: [-1234] [] [2023-08-28 20:21:30,784]  WARN {org.apache.synapse.core.axis2.TimeoutHandler} - Expiring message ID : urn:uuid:14432c0d-b5a2-4b6b-bb4d-80b499d117b9; dropping message after ENDPOINT_TIMEOUT of : 60 seconds for Endpoint [TEST_API--v1.0.0_APIproductionEndpoint], URI : http://localhost:3000/users, Received through API : TEST_API:v1.0.0Correlation ID : 10c7b09f-0188-4ad2-804a-09391245f288
TID: [-1234] [] [2023-08-28 20:21:30,786]  INFO {org.apache.synapse.endpoints.EndpointContext} - Endpoint : TEST_API--v1.0.0_APIproductionEndpoint with address http://localhost:3000 has been marked for SUSPENSION, but no further retries remain. Thus it will be SUSPENDED.
TID: [-1234] [] [2023-08-28 20:21:30,787]  WARN {org.apache.synapse.endpoints.EndpointContext} - Suspending endpoint : TEST_API--v1.0.0_APIproductionEndpoint with address http://localhost:3000 - current suspend duration is : 30000ms - Next retry after : Mon Aug 28 20:22:00 IST 2023
TID: [-1234] [] [2023-08-28 20:21:30,788]  INFO {org.apache.synapse.mediators.builtin.LogMediator} - {api:TEST_API:v1.0.0} STATUS = Executing default 'fault' sequence, ERROR_CODE = 101504, ERROR_MESSAGE = Send timeout
TID: [-1234] [] [2023-08-28 20:21:30,791] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << HTTP/1.1 500 Internal Server Error
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << activityid: 10c7b09f-0188-4ad2-804a-09391245f288
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Access-Control-Expose-Headers:
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Access-Control-Allow-Origin: *
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Access-Control-Allow-Methods: GET
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Access-Control-Allow-Headers: authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction,apikey,Internal-Key,Authorization
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Content-Type: application/json; charset=UTF-8
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Date: Mon, 28 Aug 2023 14:51:30 GMT
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Transfer-Encoding: chunked
TID: [-1234] [] [2023-08-28 20:21:30,792] DEBUG {org.apache.synapse.transport.http.headers} - http-incoming-2 << Connection: close
TID: [-1234] [] [2023-08-28 20:21:31,242]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - Shutting down IO Reactor bind for port 8243
TID: [-1234] [] [2023-08-28 20:21:31,243]  INFO {org.apache.synapse.transport.passthru.core.PassThroughListeningIOReactorManager} - HTTPS-Listener I/O dispatcher Listener shutdown.
TID: [-1234] [] [2023-08-28 20:21:31,243]  INFO {org.wso2.carbon.core.ServerManagement} - Stopped all transport listeners
TID: [-1234] [] [2023-08-28 20:21:31,243]  INFO {org.wso2.carbon.core.ServerManagement} - Waiting for request service completion...
TID: [-1234] [] [2023-08-28 20:21:31,249]  INFO {org.wso2.carbon.core.ServerManagement} - All requests have been served.
TID: [-1234] [] [2023-08-28 20:21:31,249]  INFO {org.wso2.carbon.core.ServerManagement} - Waiting for deployment completion...
<SHUTDOWN LOGS WILL PRINT AFTER THIS>

Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

Hi Team,
Highly appreciate if we can get a hotfix on top of the U2 level 218 to provide to the customer to verify the fix since the support case is already in the SLA violated state.
Thanks and Regards,
Sumudu W.

Closing this issue as it is fixed by https://github.com/wso2/carbon-kernel/pull/3661.


How to make sure data in each batch not same.

Thanks for this good project.
However, when I used the following code
        self.dataset = (
            SizedWebDataset(all_urls, length=self.num_samples, batch_size=self.batch_size, resampled=True)
            .decode("pil")
            .shuffle(1000)
            .to_tuple("jpg;png;jpeg", "txt")
            .batched(self.batch_size)
            .map_tuple(self.preprocess_image_fn, self.preprocess_image_text_fn)
            .map(self.tuple_to_dict)
        ).with_epoch(10000)

I find sometimes one batch may contain same data. Since I adopt contrastive loss during training with multi node, how to ensure one batch never see same data.
I also find .shuffle with larger number will down the repeated sampling probiality.

Hi @FingerRec, how did you solve it? Thanks.

@FingerRec  Yeah how did you solve it? 😅


Create patches for umi-tools

This PR is a hotfix for the 3.11 release candidate to add additional process labels to umi_tools extract (process long) and umi_tools dedup (process high_memory) as a temporary solution to fix errors during pipeline execution until a more appropriate process label has been added to the modules.
PR checklist

[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs- [ ] If necessary, also make a PR on the nf-core/rnaseq branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Sure, but how?
If we change the module, we might want to revert it to process_medium or even add new, more atomic labels? I don't think that this is a good permanent solution, actually...

You would create a PR to nf-core/modules with exactly the same changes and then use nf-core modules install to install in the pipeline.

If we change the module, we might want to revert it to process_medium or even add new, more atomic labels? I don't think that this is a good permanent solution, actually...

Are the current label definitions breaking for you on dev? If so, maybe we do need to update. If not, then I think we can leave things as they are and update in a future release.

Yes, the release candidate version of the pipeline is failing for me with the uppmax profile on a small human sample: umi_tools extract exceeds the runtime and umi_tools dedup the memory limits of process_single as we have defined it in the base.config. This was the reason for my proposal on Slack you have already commented on.

Obsolete, as the required changes were directly done to the modules instead of applying patches.


[New implementation] Consider concatenating index files into a single blob on remote storage

This may be an optional feature, which reduces the number of PUT and LIST operations (and hence costs). However, the costs should be considered, it may bring back little value if LIST is not performed.

Won't do: LIST is not that expensive (since up to 1k objects are returned per request) and PUT are performed once per file.


Code for integrating audio

Dear author, I need to ask you again because your work is fantastic. I would greatly appreciate it if you could provide the code file for the fused audio of xd-violence dataset.

Thank you for your attention to our work. We only perform simple concatenation of audio data during the initial input. You can try modifying the dataset reading process, and I believe this is a simple task.

Thanks,for your reply

Have you completed this task? After integrating the audio, what experiments need to be done? Which part of the dataset should be used?

Thanks,for your reply

Have you completed this task? After integrating the audio, what experiments need to be done? Which part of the dataset should be used?


T.A. Marryshow Community College

@kerrongordon First stage of verification passed, official domain for T.A. Marryshow Community College is tamcc.edu.gd as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@kerrongordon Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


[plugin|tiling] Focus monitor fails on empty monitors

FocusMonitor is currently not able to give focus to monitors that do not have any open windows.
This is because we rely on being able to give an existing window focus, to activate said monitor.
This is because macOS only has a concept of a key-window, and the active monitor is simply the monitor that holds the key-window.
We are unable to actually give focus to the macOS finder desktop window (that you focus when you click on your wallpaper, basically).
We can support this by doing a sophisticated check to see whether the monitor has open windows or not. If the monitor is empty, we synthesize a left-mouse-down event in the center of the monitor.
If the monitor has open windows, but chunkwm are unable to interact with said windows, we do NOT synthesize a left-mouse-down event, to prevent accidentally clicking some ui-element.

So with this the monitor wraparound does not work on an empty space when trying to go to the next or previous window. I believe this is the case because currently, asking chunkwm to focus the next or previous window with no window focused on the active space will instead try to focus the first or last node in the tree respectively, which obviously fails.

fixed on master.

This still seems to break when using chunkc tiling::monitor -f <prev/next> to switch monitors, which will cause the focus to jump back if the selected monitor is empty.
Directly focusing with monitor id seems to work correctly.


Add option to show multiple days event only on the current day

As a User wrote:
"I'm currently testing your very nice Calendar Widget.
I would like to propose three things however:
Events over multiple days are shown at the first day only or via the setting on every day extra. This is very intrusive in especially with multiple concurrent events.
A better approach would be showing the event only for today, but for every today as long as the event lasts. If the current day lies in the middle of the event show start and end date.
I would suggest adding this as option"

I like having a recurring event show up every day it's scheduled so that each day stands autonomous from another. That's that my calendar app does, and it's what I'd see if I went back to an archaic paper calendar. Otherwise, I risk the adage "out of sight, out of mind" by forgetting to go back to "today" to see those recurring events and event periods. That's how the widget performed before, so that suggested enhancement should be optional, not default.

@mjt543 is right. A multiple days event should show up on all days. That should be the default. Otherwise there is no need to put them in the calendar anyway.

As two users commented, they actually need to have a feature that we do have now:
"Event details" -> "Fill all day events".


Exiting a Blackjack game will put you in the wall sometimes.

Depending on where the exit marker is during the exiting phase, you might end up stuck inside a wall. The NPC is the exit marker in the case of dialogue.

As great as it would be to fix this, I have no idea how we would go about doing so. Not to mention this bug is pretty rare, would you want to consider labelling this a wontfix? Simply because there is not really a good way to fix this problem with the framework we have, but this problem can be prevented by the player.

I haven't seen this happen more than once ever so maybe closing this for now would be okay. Though it doesnt seem appropriate to mark an issue with potential to break the game as something we "wont fix". We dont even fully know why this occurs in the first place. Im not ready to give up that easy. Closing for now seems okay. Just re-open this if it becomes a problem.


CudaText

I would like someone to make a theme for CudaText, because i'm not good at it

Is this the same base for CudaText? github.com/jackdp/Dracula-CudaText

Это та же база для CudaText? Ссылка на сайт

Yes, this is it, but the theme is different from Dracula, there are differences in syntax highlighting, maybe also in the color design of the program itself. Perhaps this is due to an outdated version of the theme itself

Here's what else I found: SourceForge or GitHub. But the theme is different in color, for example, it is dimmer


Make large numbers more readable.

Issue Number
Related to #779.
Overview
Just a tiny PR to make some large numbers more readable.

bors r+

bors retry


electricCurrent duplicate key - child bridge wont load

Hi Ebaauw,
I have a duplicate key error which appears to be causing my homebridge_deconz to fail and restart:
[25/08/2023, 18:55:14] [deCONZ] Phoscon-GW: error: SyntaxError: electricCurrent: duplicate key
at Outlet.addCharacteristicDelegate (/var/lib/homebridge/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/ServiceDelegate/index.js:229:13)
at Function.addResource (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzService/Power.js:27:15)
at Outlet.addResource (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzService/index.js:80:41)
at Light.createService (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/index.js:177:17)
at new Light (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Light.js:44:14)
at Gateway.addAccessory (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:619:25)
at Gateway.analyseFullState (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:1112:20)
at Gateway.poll (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:956:18)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at Gateway.heartbeat (/var/lib/homebridge/node_modules/homebridge-deconz/lib/DeconzAccessory/Gateway.js:352:9)
[25/08/2023, 18:55:14] [deCONZ] Phoscon-GW: initialised
[25/08/2023, 18:55:14] [deCONZ] waiting for 2 jobs
[25/08/2023, 18:55:14] [deCONZ] job 1/2: done
[25/08/2023, 18:55:14] [deCONZ] job 2/2: done
[25/08/2023, 18:55:14] [deCONZ] 1 gateways
[25/08/2023, 18:55:14] [deCONZ] flush cachedAccessories
[25/08/2023, 18:55:14] [deCONZ] created debug dump file /var/lib/homebridge/homebridge-deconz.json.gz
/var/lib/homebridge/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/CharacteristicDelegate.js:397
return callback()
^
Error: This callback function has already been called by someone else; it can only be called one time.
at /var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:12:13
at CharacteristicDelegate._onSet (/var/lib/homebridge/node_modules/homebridge-deconz/node_modules/homebridge-lib/lib/CharacteristicDelegate.js:397:14)
at ConfiguredName.emit (node:events:525:35)
at /var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2596:16
at new Promise ()
at ConfiguredName. (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2594:14)
at step (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:193:27)
at Object.next (/var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:174:57)
at /var/lib/homebridge/node_modules/homebridge/node_modules/tslib/tslib.js:167:75
at new Promise ()
I've had homebridge_deconz for a while now without any issues (thanks for the great work!) and am currently running version v1.0.0 on node.js 18.16.0, I also run Home Assistant (docker) Deconz integration which seems to be unaffected by the duplicate key so I can get by at the moment
I've had a look through the log files and the errors are from 2 double sockets with individual energy monitoring, at first I thought it wasn't critical as it didn't crash and i'd read this issue:  Aqara Smart Plug: electricCurrent duplicate key error #142 - but now I cant get it to load at all
Could you advise me as to how I could trouble shoot this issue please?
homebridge.log(2).txt
homebridge-deconz.json.gz

The child bridge loads alright, but it crashes due to the "This callback function has already been called by someone else; it can only be called one time." error.  The error is actually thrown by HAP-NodeJS, but caused by a bug in Homebridge deCONZ.  Not happy the HAP-NodeJS terminates the process (rather than just ignoring the superfluous callback function call).  I'll need to guard the callback to prevent the crash.
The duplicate key error is caused by the Aurora DoubleSocket50AU having two ZHAPower resources, which Homebridge deCONZ doesn't expect nor handle.  For the devices in #142, this clearly is an error in the deCONZ REST API plugin, exposing superfluous ZHAConsumption and ZHAPower resources.
Looking at the uniqueid values, and at the fact the the state attributes on both resources are actually populated with different valid values, it would seem that the Aurora actually reports current consumption (power) per socket?  This the first device, for which I've seen this (apparently already back in 2020, see https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2292, but I completely forgot about that).
I think the fatal error is caused by Homebridge deCONZ setting up two characteristic delegates for the same characteristic.  The difference with the devices in #142 is that they only use a single /lights resource.
I think the Aurora smart plug would need to be exposed as two separate HomeKit accessories, each with a single Outlet service including the corresponding electrical measurement attributes, and a History service.

Could you please try beta v1.0.1-0?  It should no longer crash, but will still log errors for the duplicate key and the callback already been called.  I'm sorry, but I don't have any device similar to the Aurora smart plug, to test this myself.
If indeed, the beta version no longer crashes, could you please check in Eve (or another deCONZ HomeKit app) whether both Outlet services carry characteristics for current consumption (power), voltage and current?

Thanks for the quick reply and useful info on this issue. I've just tried the beta and can confirm it no longer crashes, but still throws duplicate key error as expected
Thanks for your help, let me know if you need any further log files or to test any updates you make regarding this issue

For Eve, one double socket shows no consumption or energy monitoring at all, the other shows consumption but appears to alternate between the values of the two outlets (regardless of whether i look at outlet A or outlet B)

Thanks, that confirms that there's two delegates setup for the same characteristic.  I will come back with an enhancement to expose the plug as two devices, but I need some time to figure out how best to achieve this.

No problem, thanks for your help


Grappelli / Mezzanine not properly saving page keywords

When keywords are entered for a page, they are not saved. (This is true for ppa-django and derrida-django).

will be resolved with #97


MacOS support?

I have the older core wallet and it will not connect to peers. It is version <IP_ADDRESS> for the Mac.
I am hoping to access my BTX. Is there a newer Mac wallet that can access my current wallet.dat?

We are working on fixing the problem.

Please try it with version <IP_ADDRESS>
https://github.com/bitcore-btx/BitCore/releases/tag/<IP_ADDRESS>


chore: revert website gomod change

Fixes #N/A
Description
reverting a change made to update the website go.mod that broke some things in the website
How was this change tested?
Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 82.489%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
4918

Relevant Lines:
5962

💛  - Coveralls

Yep - using the latest version of docsy is going to require fixing some things since the major update to bootstrap 5. See support doc on docsy.


Request for new filters to hide works

Hello!
I love the extension, and it's already a big help, especially the "Hide works based on language" one. Since I read in two of the most represented languages in my preferred fandoms, it's quicker to hide the works in other languages than to filter by one language, then the other.
Since it's so helpful, I wanted to suggest the option to hide works based on fandom, exactly the same way.
When I search by tag, I get works from every other fandoms, and the AO3 interface isn't very good at filtering every work except those that belong to my fandoms, especially when they aren't well-known ones. I can try to filter the ones I don't want out, but the site gets overwhelmed after a certain number of requests.

Fixed in v0.5.
See https://github.com/jsmnbom/ao3-enhancements/releases/tag/v0.5.4.


Fix Memory leaks in PMesh

face_nbr_el_to_face may be newd and is not deleted in the dtor
sfaces_tbl is newd and assigned to a local variable but never deleted

This was caught by our leak-sanitizer build

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2655
@tomstitt
@pazner
@mlstowell + @YohannDudouit
11/10/21
⌛due 11/24/21
⌛due 12/01/21

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

Merged in next for testing...


Introduce metric to measure the length of the SLAM queue

@wally-the-cartographer merge

Merge requested by authorized user cschuet. Merge queue now has a length of 1.


Bump babel to 6.5.2

Hey @theogravity
I think this is what you are looking for.  I've moved to babel 6.5.2 or higher.  I also removed the unnecessary babylon dependency as it comes from babel.

Don't forget to update the changelog then :ship:  and publish.
Thanks!

Fixes https://github.com/theogravity/react-styleguide-generator-alt/issues/9

:+1: All set.  Published 3.3.0

Thanks!


luci-mod-network: "VLAN port state" the '-' is a non-ascii encoded character

I found that the WEB page shows that "VLAN port state" the '-' is a non-ascii encoded character, is this intentional?
I added a comment on this commit
https://github.com/openwrt/luci/commit/eeef38d53412a78f185f0bb53153ecb3fe9e8838

Yes, it is intentional.


ARM is now default.

Ran updates with watchtower, and got this output:
exec /run.sh: exec format error
Looks like it's now pulling the ARM64 image instead of amd64.

Aaaaaaaah, I’ve changed to an m3 Mac, which would make sense. I’ll see what
I can do to get an intel image up
Matt Rayner
http://www.mattrayner.co.uk/
On Sat, 6 Apr 2024 at 14:55, GRJ3KHKX @.***> wrote:

Ran updates with watchtower, and got this output:
exec /run.sh: exec format error
Looks like it's now pulling the ARM64 image instead of amd64.
—
Reply to this email directly, view it on GitHub
https://github.com/mattrayner/docker-lamp/issues/139, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2XGNVEMHOIAPMHJI7SVETY375F7AVCNFSM6AAAAABF2O33W6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDSMRVGUZDKMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

same problem :
docker: image with reference docker.io/mattrayner/lamp:latest-2004-php8 was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64.


first needed modifications to support react

Explanation About What Code Achieves:

It will support a html component as a parent which is needed for react.
It will store the generated css into a file that it can be used within react

Steps To Test:

Use branch and create "basic" react component as described in #24.
Import and use this component and check if the chart is rendered corretly

TODOs:

We should discuss if we want to support React per default -> package.json main should point on a non rollupjs file

So we've gone ahead and kept the commonjs module in main, in addition to adding in the es6 module and the iife for browser use (ref #35)
Apart from that, we'd be happy to merge once rebased :)

@pratu16x7 thank you! :)
Yes makes sense, should be ok now?


Service Principal - Remove keyCredential 403

Describe the bug
'v1.0/servicePrincipals/{servicePrincipal-id}/removeKey' does not seem to work. No combination of request body or permissions on Graph Explorer help.
Prerequisites

keyCredential and passwordCredential were setup following Configure a custom signing key.
The correct Permissions are given delegated and with admin consent as described in 'Modify Permissions'.

To Reproduce
Steps to reproduce the behavior:

Go to 'https://developer.microsoft.com/en-us/graph/graph-explorer'
Enter POST, 'https://graph.microsoft.com/v1.0/servicePrincipals/{servicePrincipal-id}/removeKey'
Add correct SP ID
Add a payload, such as example

{
   "keyId": "f0b0b335-1d71-4883-8f98-567911bfdca6",
   "proof":"eyJ0eXAiOiJ..."
}

All attempts and combinations return a 'Forbidden - 403'

Expected behavior
The request completes with a 204 or some more specific error describing what is missing/wrong.
Additional context
Additionally attempting to remove the passwordCredentail associated with the keyCredential results in a 500 error.
I see there is also a PowerShell command Remove-AzureADServicePrincipalKeyCredential, maybe this would work, it does not require a 'proof'.

Since the call was successful but the results are unclear, it is likely an issue with the API. Please feel free to contact support


Add mypy job

Add mypy playbook, role and job definition for use in other Repos
Mypy is used for automatic Python type checking

[ ] TODO: requirements.txt needs to be installed before mypy is run

What repo do you plan to run this job in? Doing a random test I get:
osism/python-osism$ python3 -m mypy --ignore-missing-imports --install-types --non-interactive .
error: --install-types failed (no mypy cache directory)

What repo do you plan to run this job in? Doing a random test I get:
osism/python-osism$ python3 -m mypy --ignore-missing-imports --install-types --non-interactive .
error: --install-types failed (no mypy cache directory)

We are working on the osism-flavor-manager, where the exact call stated in the ansible.command should work already.
The "no mypy cache directory" is probably related to this: https://github.com/python/mypy/issues/10600

Seems to have worked for the flavor manager repo https://github.com/osism/openstack-flavor-manager/pull/37/checks?check_run_id=15009303753 :+1:


When generating the job folder name, some characters are removed

When generating the job folder name, some characters are especially removed to make sure the name does not conflict with how the OS handle its files/folders. However, this means that two jobs' folder name will collide if they only differ by some characters that will be removed even though the jobs produce different commands.
For example, the following commands will generate the same folder name:
smart_dispatch.py -x -q test -C 1 -t 1:00 -p 2 launch script [-option1\ value1 -option1\ value2]
smart_dispatch.py -x -q test -C 1 -t 1:00 -p 2 launch script "[-option1\ value1 -option1\ value2]"
They produce the same folder name: script__option1_value1__option1_value2/
but their commands are different (respectively)
script -option1
script value1
script -option1
script value2

and
script -option1 value1
script -option1 value2

The best way to handle that is probably to use UIDs for the batch folders, generated from the escaped string that is after the launch param.
We should also add a file to that folder with the complete original string given to smart_dispatch.

This means we won't support named batch folders anymore, right? I know @laulysta that you liked having name containing what params/values were used, but as soon as we'll have a basic job viewer I'm sure you'll be fine.

Well if we have a proper viewer it really doesn't matter.
On Tue, Mar 3, 2015 at 10:12 PM, Marc-Alexandre Côté <
<EMAIL_ADDRESS>wrote:

This means we won't support named batch folders anymore, right? I know
@laulysta https://github.com/laulysta that you liked having name
containing what params/values were used, but as soon as we'll have a basic
job viewer I'm sure you'll be fine.
—
Reply to this email directly or view it on GitHub
https://github.com/SMART-Lab/smartdispatch/issues/79#issuecomment-77089728
.


Show the SMS rates warning even without ToS/PP

See #1559

@lsirac pinged me to say LGTM since he is locked out of GitHub.


[SF] Get rid of unnecessary closures

There are some places with a high number of closures in lambdas leading to a lot of allocation (e.g. in PropertyManagementClientWrapper.GetPropertyAsync). Let's get rid of them.

Pre-triage: It's a nice to have optimization, but nothing crucial. Moving to backlog.


Add output writer plugin for Sourcetrail DB format

Add an output writer plugin (that is optional/requires extra install step) that uses https://github.com/CoatiSoftware/Sourcetraildb (or that looks at the SQLite schema that the library writes to) to output relationships in a file that can be loaded by Sourcetrail for visualization. See https://github.com/quarkslab/pyrrha?tab=readme-ov-file#visualization-with-sourcetrail for an idea of how relationships could be mapped to the Sourcetrail format.

See https://github.com/quarkslab/numbat for writing Sourcetrail DB file.

This issue was addressed by merging #236


Failing tests on the fixed version

Hi,
It seems there are some (unexpected) failing test cases on the fixed version of, e.g., Express-1f.  Here is the step-by-step to reproduce this issue.
My system:
$ sw_vers
ProductName:		macOS
ProductVersion:		13.0.1
BuildVersion:		22A400

$ git --version
git version 2.38.1

$ python3 --version
Python 3.10.8

$ node --version
v18.11.0

$ npm --version
8.19.2

# Get BugsJS
$ rm -rf /tmp/bugsjs-issue-11
$ git clone https://github.com/BugsJS/bug-dataset.git /tmp/bugsjs-issue-11
$ cd /tmp/bugsjs-issue-11

# Run `test` on Express-1f
$ python3 main.py -p Express -b 1 -t test -v fixed -o Express-1f-test/

which produces the following log
Cloning into 'express'...
remote: Enumerating objects: 30151, done.
remote: Counting objects: 100% (2/2), done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 30151 (delta 0), reused 0 (delta 0), pack-reused 30149
Receiving objects: 100% (30151/30151), 8.56 MiB | 8.51 MiB/s, done.
Resolving deltas: 100% (17015/17015), done.
Note: switching to 'tags/Bug-1-full'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 8e0080e1 Bug-1 full
/bin/sh: n: command not found
npm WARN deprecated<EMAIL_ADDRESS>'native-or-bluebird' is deprecated. Please use 'any-promise' instead.
npm WARN deprecated<EMAIL_ADDRESS>Deprecated, use jstransformer
npm WARN deprecated<EMAIL_ADDRESS>Please update to at least constantinople 3.1.1
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to v7.0.2+ of superagent.  We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing.  See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Critical security bugs fixed in 2.5.5
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: https://bit.ly/2ZEqIau
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Mocha v2.0.x is no longer supported.
npm WARN deprecated<EMAIL_ADDRESS>This module is no longer maintained, try this instead:
npm WARN deprecated   npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.

added 173 packages, and audited 174 packages in 12s

1 package is looking for funding
  run `npm fund` for details

38 vulnerabilities (1 low, 6 moderate, 21 high, 10 critical)

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
(node:95589) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:95589) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
Number of tests: 737
	passes: 718
	failures: 21
	pending: 0
/bin/sh: istanbul: command not found

21 failing tests.  Given it I'm running test on the fixed version I was expecting 0 failures.  Please find attached the resulting test_results.json.zip file.  Is this somehow expected?
Miscellaneous
A couple of errors I noticed in the log which may or may not be the reason for the 21 failing tests:

/bin/sh: n: command not found which is thrown by this line of code.
/bin/sh: istanbul: command not found which is thrown by the code-coverage step.  I've tried to add
sp.call("npm install istanbul", shell=True) to the run_npm_install function to somehow force the installation of istanbul, but it didn't work.

--
Best,
Jose

After analyzing the provided docker and reproducing the installation steps, I've managed to easily address the miscellaneous issues.

The /bin/sh: n: command not found can be addressed by running npm install -g n.  (I was not aware of the n package to manage different versions of node.)
The /bin/sh: istanbul: command not found can be addressed by running npm install -g istanbul.  (It seems that -g (i.e., global) did the trick.)

And I'm now down to 11 failing tests: 8 unit tests and 3 acceptance tests.

Well, according to the Projects/Express/Express_bugs.csv file, there are a total number of 732 tests on Express-1: 721 pass and 11 fail, and I'm now getting those exact numbers with the test command.  For the record, here's the list of failing tests on Express-1b and Express-1f.

Test
JS file

"should restore req.params after leaving router"
test/app.router.js

"should be invoked instead of auto-responding"
test/res.format.js

"should respond with html"
test/res.redirect.js

"should escape the url"
test/res.redirect.js

"should respond with text"
test/res.redirect.js

"should encode the url"
test/res.redirect.js

"should set body to \"\""
test/res.send.js

"should invoke the callback on 404"
test/res.sendFile.js

"should succeed with proper cookie"
test/acceptance/auth.js

"should fail without proper password"
test/acceptance/auth.js

"should succeed with proper credentials"
test/acceptance/auth.js

Point is, if I've the same set of failing tests on the fixed (aka non-buggy) and buggy version, which tests truly trigger the buggy behavior?  I would say none, but I might be missing something here.

Hmm, I think I finally managed to understand the issue.  There are 11 failing tests on the fixed and on the buggy version, and 12 failing tests on the fixed-only-test-change version.  The 11 tests could be considered broken tests (i.e., they fail due to any other reason than the Express-1 bug) and the extra one is the one that triggers the buggy behavior.

  Otherwise, how would one be able to compute accurate code coverage or mutation score of a suite that has 11 failing tests?
PS: A message to my future self, the fixed-only-test-change version corresponds (roughly) to the buggy version on Defects4J.


add support for other angle units

Fixes #5.
Not that I simplified unitless-rad() by using native native fixed unit conversion. This was suggested to me in https://github.com/xi/sass-planifolia/issues/1.
Note that invlid input like unitless-rad(2em) will still produce warnings: "Incompatible units: 'em' and 'rad'."

Sorry, I failed to check #6 which implements the exact same method. I will keep this open for the test code.

@xi @yukulele Really really sorry for may very late reply 🙇
I didn’t know this native operation feature. It looks perfect.
Thanks for your contribution!

Thanks for the merge!

thanks!


adding julia

Docs Build status updates of commit 64b5b1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/index.html.yml
:white_check_mark:Succeeded
View

advocates/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


ReiNX/Atmosphere?

ReiNX has sig patches, and works fine. Using rajkosto's hekate, and/or ReiNX sig patches, atmosphere also has sig patches. ReiNX isn't fully done (no support for 1.0.0 and 3.0.2, and atmosphere isn't done either), but it works great on the working firmwares. Atmosphere is basically the same, and since it has layeredfs support, it is a viable alternative. Both of these are quite stable, so when would they be added in the guide??

As I have said previously, I'm waiting for some stuff to stabilize a bit (hopefully whenever atmosphere releases) before recommending anything more than just homebrew launcher to regular users. Stuff like Hekate/ReiNX is only really good for people who are ready to constantly be updating all of their stuff all of the time (which some people enjoy, but those people also are the type to read forum/reddit posts constantly to stay up-to-speed and don't need a guide).

#51
they are other cfw's also, there's no point in being picky about which ones to  put on the guide, if they all work.


msbuild path has changed in vs2019 release to use 'Current' instead o…

…f the version number.
Also changing the default version to 16 if not supplied as parameter when building.
If you only have VS2019 installed - it would never try to use 16.

So... I have merged but with numeric tools version. Hope it's OK else ... change it again ;-)
Uploading 0.2.10 to MyGet in a few.

Dammit, then it won't build - ToolVersion has to be Current... ok, re-fixing

We found that as well.. lol 🤦♂