[Discussion] download model archive on ecach process ?

is it normal that spleeter lkeeps downloading the model archive on each process ?
I anytime get :
INFO:spleeter:Downloading model archive https://github.com/deezer/spleeter/releases/download/v1.4.0/2stems.tar.gz
Cheers Marc

Well, I have the same problem after trying to
pip install spleeter
and do
spleeter separate -i spleeter/audio_example.mp3 -p spleeter:2stems -o output
After checking the process:
I found
96251 ttys010    0:04.12 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96254 ttys010    0:00.04 /Users/siyunhe/anaconda3/bin/python -c from multiprocessing.semaphore_tracker import main;main(7) 96255 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96256 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96257 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96258 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96259 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96260 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96261 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96262 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96263 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96264 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96265 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple 96266 ttys010    0:00.00 /Users/siyunhe/anaconda3/bin/python /Users/siyunhe/anaconda3/bin/spleeter separate -i spleeter/audio_example.mp3 -p sple
Does anyone know how long it takes for the model to download?

is it normal that spleeter lkeeps downloading the model archive on each process ?
I anytime get :
INFO:spleeter:Downloading model archive https://github.com/deezer/spleeter/releases/download/v1.4.0/2stems.tar.gz
Cheers Marc

Actually it is faster than I thought, around 6min with 300kb/s, better to have a process bar to
show the download procedure.

Hi @daslicht  @Franceshe
It should definitely not need to download the model more than once. This probably means it gets saved in a temporary folder that is cleaned after your execution. What's your setup ? are you executing in a docker ?

Is there a way to point spleeter to the folder of pretrained_models instead of having it download it and extract it every time?

nope just macos mojave here. anyway to determine where it gets downloaded ?

the model should be downloaded in a folder called pretrained_models by default.
You can change that (and actually avoid re-downloading) by explicitely setting the environment variable MODEL_PATH before calling spleeter.

Ok, it seams to download that folder in the same folder execute the process. For any conversion I get an output  and that pretrained_models folder

something like export MODEL_PATH=<path/to/pretrained_models/>

and this will be permanent or just for the session ?

Just for the session but you can also set it up permanently. Look on google how to depending on your OS and which terminal/shell you're using.

Got it, Thank you very much !

output cant be a path no ?


README / repository description is not clear.

Stage files for packaging

That's the only content phrase.
What is "staging"? What is "packaging"? Is it Git's staging of files for making a commit? Is it Cargo's packaging prior to publishing to crates.io?
There should be more text (especially about broader context), some example, maybe some diagram, maybe console output.
Module-level reference documentation is also not clear:

stager - This crate stages files for packaging
Modules:
action | Filesystem operations to stage files.
builder | High-level requirements for staging files.
de | Composable file format for staging files.

The downside of rushing to get a prototype of this and cargo-tarball out.  Hopefully #16 helps clarify.

Suggested repository description (which is not updated yet):
A tool to package executables from Rust-based project into a release bundle based on configuration file
(if I understood this correctly).
A sample of such configuration file and layount of the resulting archive (tar -tf ... output) is still missing.

projct

...

I've separately created #17 for documenting the schema.  cargo-tarball for now will be the best most complete example since it will be dog fooding itself.  It would be nice to add additional detail of how it is an example but I don't feel that is as pressing.


Script does not handle impact recording types

The script currently does not handle impact recording types ('I') which causes an exception when sorting the files after getting the list from the dashcam:
ERROR 'NoneType' object has no attribute 'datetime'
I think there will be more types of filenames according to: https://blackvue.com/major-update-improved-blackvue-app-ui-dark-mode-live-event-upload-and-more/.
The ones not metioned on that page are MNP.
The solution seems to be simple:
filename_re = re.compile(r"""(?P<base_filename>(?P\d\d\d\d)(?P\d\d)(?P\d\d)
_(?P\d\d)(?P\d\d)(?P\d\d))
_(?P[NEPM])
(?P[FR])
.(?Pmp4)""", re.VERBOSE)
Becomes:
filename_re = re.compile(r"""(?P<base_filename>(?P\d\d\d\d)(?P\d\d)(?P\d\d)
_(?P\d\d)(?P\d\d)(?P\d\d))
_(?P[MEATBOIRXGNP])
(?P[FR])
.(?Pmp4)""", re.VERBOSE)
And manual_event_sort_key gets updarted to something like:
def manual_event_sort_key(recording):
"""sorts by recording type, then datetime, then front/rear direction"""
return "MEATBOIRXGNP".find(recording.type), recording.datetime, "FR".find(recording.direction)
Thanks,

No problem, I'll give it a try when I can - seems like you, not sure when
I'll get chance next.
Thanks
On Sat, May 15, 2021 at 7:08 PM Alessandro Colomba @.***>
wrote:

Thank you for your report!
I made the necessary changes pretty much as you suggested.
I would appreciate it if you were able to test it out on a real cam and
let me know how that goes. (I tested this on the emulator, and it'll be a
bit before I drive.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/acolomba/blackvuesync/issues/3#issuecomment-841702773,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHK7GYKKHMPU3QG7NTY3LDTN22CTANCNFSM444MRZ7Q
.

I created a github account just to thank you both, and to let you know that this resolved the issue for me on my DR900x.
I've been using this script for a few months and then it broke yesterday - it may or may not have been due to upgrading to firmware 1.006.
Huge thanks to acolomba for writing this script, and thanks to ThinkSteve74 for fixing this issue!

Great, I believe I can close this issue then.
Thank you both very much!


Can't compile the "Realsense recorder example" from Open3D

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D400

Operating System & Version
Win10

Platform
PC.

SDK Version
2.50.0 }

Language
C++

Segment
Robot

Issue Description
Hi, is the Intel RealSense D455 compatible with Open3D Lib ? because i tried to compile this example : https://github.com/isl-org/Open3D/blob/master/examples/cpp/RealSenseRecorder.cpp
But it looks like the program doesn't recognize the D455 realsense since the program doesn't retrieve and display anything at all..
Is there any explanation for this issue ? thank you

Hi @Amayess  What are the resolution and FPS settings that you are using for the depth and color streams, please?
If depth and color were being set to 6 FPS then this would not work on D455 as that camera model uses 5 FPS as its minimum for depth and color instead.
You could also test for the possibility that the camera connection was being identified as being USB 2 instead of USB 3 by setting depth and color to 640x480 and 30 FPS.  Some resolution and FPS combinations are not supported on a USB 2 connection, but 640x480 at 30 FPS is.

Thanks for you answer @MartyG-RealSense, after commenting on these lines of code, the program seems to work correctly.
Do the results make sense? especially the intrinsic parameters.
thanks.


upgrade to latest generator-jhipster v8.4.0

This PR only upgrades the generator-jhipster version to v8.4.0.

@DanielFran / @mraible / @mshima can you please check this PR.


refactor(setup): place the setup in the readme

in a second step, once the FE is updated, we can remove setup.template.html
The README looks like:

The FE using it, looks like:

Can we remove setup.template.html ?

We can't the FE still requires it, but as soon as the changes are applied to all 4 SDKs and the FE merge request is deployed up to production, we can.

Thanks @daddykotex


build fails under ghc 7.10.1

A problem with overlapped instances in Parser.hs

6.10 is very old. Why is this important?

It's 7.10.1, my bad.

Ok, thanks for reporting. Fixed in <IP_ADDRESS>.

Thanks!


Twilio support

Is pretty much fully integrated.
Uses the listener + players to communicate with the models, similar to how the web platform did.
There are still optimizations to be made. Uses mark messages to wait to completion, clear message to stop the audio etc.

Further ideas here: #46


markApproved, markRejected, ... functions incompatible with models with attributes with array casts

I have a model with an array cast on one attribute foo.
protected $casts = [
        'foo' => 'array',
];

But the SQL type is VARCHAR.
When the any of markApproved, markRejected, markPostponed, markPending is called, it causes the attributes array to be changed from
$attributes = [
    ...
    'foo' => '["mango","pineapple","pawpaw"]'
    ...
]

to
$attributes = [
    ...
    'foo' => [
        "mango", "pineapple", "pawpaw"
    ]
    ...
]

which leads to unexpected value exceptions when trying to save the model

Ok I was able to fix it by changing the $new->attributesToArray() to $new->attributes in the Moderatable trait.
So the markApproved function for example changes to
public function markApproved()
{
    $new = (new static)->newQueryWithoutScope(new ModerationScope())->approve($this->id);
    return $this->setRawAttributes($new->attributes); // instead of $this->setRawAttributes($new->attributesToArray())
}

@hootlex Kindly test this and update. Thanks

I submitted a PR to fix it. #45


Getting involved in PostgREST development

Hi, I'm really excited about this project, I love the vision, I love the choice of language, and I love that the user land implementation is in SQL. I've been trying to move some of my production APIs to PostgREST, and because of this I want to invest back into the project.
I have a background in PHP and NodeJS. Recently I have also taken an interest in Haskell and functional programming. That said I will likely need a mentor to help introduce me to the world of Haskell and specifically this project's code base.
If anyone is willing to help get up to speed so I can start regularly contributing that would be awesome.
PS: It seems like issue #278 might be a simple first contribution (I have some experience in streaming APIs in node). I would need some initial help finding and parsing documentation for Hasql and Warp.

I have the feeling that #278 is actually more tricky than it looks like but if there is already some development going on, I guess it would be really educative to participate.
Note that in the list of future features, there is watching endpoint changes with sockets and Postgres pubsub. This is probably simpler; we need to use postgresql-libpq and get a good streaming interface. I was actually planning to give it a go, by-passing hasql-postgres (that does not implement or plan to implement notify (see https://github.com/nikita-volkov/hasql-postgres/issues/17).
I am more and more convinced that list-tis not the way to go for streaming and I would be personally interested in using the new streamingpackage for this.

Being able to see the diffs between the current source and the postgresql-libpq source could be super helpful in understanding how the source works. As it touches all of the points where the database is queried.
Do you think this is a simple enough task for a Haskell newbie to tackle (no new features so I would just need to ensure tests keep passing). Or would it be better for me to observe?
Again super excited to learn more about the Haskell community and help this project grow.

Love your enthusiasm @calebmer! Issue #290 would be a great place to start for learning to build the project, run the test suite and add your own test. Certainly the project chat room is a helpful spot to ask questions along with the Haskell IRC channel on freenode. Also @bitemyapp enjoys helping people get started coding Haskell and would be a good person to talk to.
If you've got some postgrest changes you'd like to share just open a pull request even if things aren't 100% finished. That will provide a nice way to chat about the code as we go. I'm on vacation for most of this week but I'll check online every so often to see if I can help.

@calebmer @begriffs howdy. Just email me if you have questions, need pointed in the right direction, w/e.
Fair warning, I know jack and nada about postgrest other than what it does. I can mostly offer advice/help with Haskell, OSS, teaching, learning, etc.
If you want code review, just PR (if @begriffs doesn't mind) and cc me on the PR.


TUTORIAL: Assets from hello world not available

The assets for the hello world section of the React Viro documentation are no longer available.
https://docs.viromedia.com/docs/tutorial-ar

We are aware of this 😄 The docs are currently being migrated from the docs.viromedia.com to a community hosted domain


setup.py: set proper python requirements

Only py3.5+ is supported
Signed-off-by: Martin Bašti<EMAIL_ADDRESS>

Because of missing python requirements in setup.py, release 0.1 is downloadable by pip from PyPI on py2. It should be probably removed from pypi and replaced by new release to avoid messing with py2.
podman run -ti --rm python:2 bash
root@dfbc76b4fa22:/# pip install wfepy   # should error here with no available for py2 error
....
root@dfbc76b4fa22:/# python2 -m wfepy
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/runpy.py", line 163, in _run_module_as_main
    mod_name, _Error)
  File "/usr/local/lib/python2.7/runpy.py", line 111, in _get_module_details
    __import__(mod_name)  # Do not catch exceptions initializing package
  File "/usr/local/lib/python2.7/site-packages/wfepy/__init__.py", line 3, in <module>
    from .workflow import *     # noqa: F401, F403
  File "/usr/local/lib/python2.7/site-packages/wfepy/workflow.py", line 4, in <module>
    import enum
ImportError: No module named enum


Support for Dell Precision 3541

I want to use Nix-Os on a Dell Precision 3541 which is not added in nixos-hardware yet.
I will open an MR following this issue, which partially supports this laptop. I will be waiting for your comments.
Missing from the MR: NVIDIA enable configuration. The laptop has a Quatro P620 NVIDIA card which is not supported by the latest NVIDIA driver.

There are also some older nvidia drivers in nixpkgs: https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/nvidia-x11/default.nix


Will the PyPI package be renamed to qiskit-addon-mthree?

Just a question.

Not that I am aware of, nor does it yield any benefit to the end-user to do so.


Snapcraft Licence

📋 Description
Snapcraft
License | AGPL 1.0 or later
🔗 Data
IDK, however it is that the existing Snapcraft version badge works.
🎤 Motivation
It's like the other Licence badges.

Example call:
curl "https://api.snapcraft.io/v2/snaps/info/thunderbird" --header "Snap-Device-Series: 16" | jq .snap.license

This property is exposed at snap level so does not need to support track / risk params

Hi @chris48s  I've created a PR to add this badge #10520 🙇


sasjs build should base64 encode files to ensure the JSON is fully self contained

With the work we did for streaming apps, the JSON produced by sasjs build was updated to enable files to be uploaded to both SAS 9 and Viya
The issue is that this was implemented using file path pointers, which means the JSON file is no longer portable
This is a problem when deploying the build JSON as part of a web pack bundle
To fix this, as part of sasjs build we should base64 encode files into the JSON file itself, making a single portable file for deployments.
A test for this should be included within the adapter repo (or sasjs-tests)

Closed in https://github.com/sasjs/cli/pull/855


LoadError: UndefVarError: info not defined

I have two installations of Julia 1.0.2: one in MacOS, another in Windows 7x64.
Usage of build_app_bundle() in MacOS is successful, whereas in Windows compilation of the same source code fails with message: "<..> LoadError: UndefVarError: info not defined <..>\src\bundle.jl:16".
It seems, something related to @info macro works differently in Windows.

Thanks a lot! It seems I have old version with info() inspite of the fact I've installed it by ] add ApplicationBuilder about 3 and a half hours ago. Sorry for misleading.
Development version works in Windows.


Corenlp typeerror

If I change the doctest from 9 to 10, the test goes through just fine. I don't know if this is just my setup or not, so I am avoiding changing the doctest.
Failed example:
    next(
        parser.raw_parse(
            "The broader Standard & Poor's 500 Index <.SPX> was 0.46 points lower, or "
            '0.05 percent, at 997.02.'
        )
    ).height()
Expected:
    9
Got:
    10

Anyway, originally I got TypeErrors when I run CoreNLPServer and I fixed it.

So, it seems like it was on my end.
Gotta love mystery environment issues.

Regarding the doctest, could you see what the parse tree is. It might be because of a newer corenlp model.

After trying to use the thing, I agree people shouldn't be using it in any practical matter.
Maybe init should print an warning against using corenlpserver outside of isolated cases. An written docstring is definitely needed.


Micropython post update

Fixed SymbolButton example.
Added explanation about lambda and Closure on the Action Callback example

Much clearer, thank you!


OutOfRangeError (see above for traceback): RandomShuffleQueue '_2_shuffle_batch/random_shuffle_queue' is closed and has insufficient elements (requested 1, current size 0)

Hi !
At first, sorry for that I uploaded this problem as 'requests' at noon, I didn't notice the mistake when I wrote it.
I want to run this code, train it and see the results, but when I start training , the code will automatically quit after this:
OutOfRangeError (see above for traceback): RandomShuffleQueue '_2_shuffle_batch/random_shuffle_queue' is closed and has insufficient elements (requested 1, current size 0)
[[Node: shuffle_batch = QueueDequeueManyV2[component_types=[DT_FLOAT, DT_FLOAT], timeout_ms=-1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](shuffle_batch/random_shuffle_queue, shuffle_batch/n)]]
How could this happen and how to do?

Even I got the same error
python -m cyclegan.main     --to_train=1     --log_dir=cyclegan/output/cyclegan/exp_01     --config_filename=cyclegan/configs/exp_01.json
WARNING:tensorflow:From /home/deependra/GANresearch/cyclegan/main.py:93: get_or_create_global_step (from tensorflow.contrib.framework.python.ops.variables) is deprecated and will be removed in a future version.
Instructions for updating:
Please switch to tf.train.get_or_create_global_step
Model/d_A/c1/Conv/weights:0
Model/d_A/c1/Conv/biases:0
Model/d_A/c2/Conv/weights:0
Model/d_A/c2/Conv/biases:0
Model/d_A/c2/instance_norm/scale:0
Model/d_A/c2/instance_norm/offset:0
Model/d_A/c3/Conv/weights:0
Model/d_A/c3/Conv/biases:0
Model/d_A/c3/instance_norm/scale:0
Model/d_A/c3/instance_norm/offset:0
Model/d_A/c4/Conv/weights:0
Model/d_A/c4/Conv/biases:0
Model/d_A/c4/instance_norm/scale:0
Model/d_A/c4/instance_norm/offset:0
Model/d_A/c5/Conv/weights:0
Model/d_A/c5/Conv/biases:0
Model/d_B/c1/Conv/weights:0
Model/d_B/c1/Conv/biases:0
Model/d_B/c2/Conv/weights:0
Model/d_B/c2/Conv/biases:0
Model/d_B/c2/instance_norm/scale:0
Model/d_B/c2/instance_norm/offset:0
Model/d_B/c3/Conv/weights:0
Model/d_B/c3/Conv/biases:0
Model/d_B/c3/instance_norm/scale:0
Model/d_B/c3/instance_norm/offset:0
Model/d_B/c4/Conv/weights:0
Model/d_B/c4/Conv/biases:0
Model/d_B/c4/instance_norm/scale:0
Model/d_B/c4/instance_norm/offset:0
Model/d_B/c5/Conv/weights:0
Model/d_B/c5/Conv/biases:0
Model/g_A/c1/Conv/weights:0
Model/g_A/c1/Conv/biases:0
Model/g_A/c1/instance_norm/scale:0
Model/g_A/c1/instance_norm/offset:0
Model/g_A/c2/Conv/weights:0
Model/g_A/c2/Conv/biases:0
Model/g_A/c2/instance_norm/scale:0
Model/g_A/c2/instance_norm/offset:0
Model/g_A/c3/Conv/weights:0
Model/g_A/c3/Conv/biases:0
Model/g_A/c3/instance_norm/scale:0
Model/g_A/c3/instance_norm/offset:0
Model/g_A/r1/c1/Conv/weights:0
Model/g_A/r1/c1/Conv/biases:0
Model/g_A/r1/c1/instance_norm/scale:0
Model/g_A/r1/c1/instance_norm/offset:0
Model/g_A/r1/c2/Conv/weights:0
Model/g_A/r1/c2/Conv/biases:0
Model/g_A/r1/c2/instance_norm/scale:0
Model/g_A/r1/c2/instance_norm/offset:0
Model/g_A/r2/c1/Conv/weights:0
Model/g_A/r2/c1/Conv/biases:0
Model/g_A/r2/c1/instance_norm/scale:0
Model/g_A/r2/c1/instance_norm/offset:0
Model/g_A/r2/c2/Conv/weights:0
Model/g_A/r2/c2/Conv/biases:0
Model/g_A/r2/c2/instance_norm/scale:0
Model/g_A/r2/c2/instance_norm/offset:0
Model/g_A/r3/c1/Conv/weights:0
Model/g_A/r3/c1/Conv/biases:0
Model/g_A/r3/c1/instance_norm/scale:0
Model/g_A/r3/c1/instance_norm/offset:0
Model/g_A/r3/c2/Conv/weights:0
Model/g_A/r3/c2/Conv/biases:0
Model/g_A/r3/c2/instance_norm/scale:0
Model/g_A/r3/c2/instance_norm/offset:0
Model/g_A/r4/c1/Conv/weights:0
Model/g_A/r4/c1/Conv/biases:0
Model/g_A/r4/c1/instance_norm/scale:0
Model/g_A/r4/c1/instance_norm/offset:0
Model/g_A/r4/c2/Conv/weights:0
Model/g_A/r4/c2/Conv/biases:0
Model/g_A/r4/c2/instance_norm/scale:0
Model/g_A/r4/c2/instance_norm/offset:0
Model/g_A/r5/c1/Conv/weights:0
Model/g_A/r5/c1/Conv/biases:0
Model/g_A/r5/c1/instance_norm/scale:0
Model/g_A/r5/c1/instance_norm/offset:0
Model/g_A/r5/c2/Conv/weights:0
Model/g_A/r5/c2/Conv/biases:0
Model/g_A/r5/c2/instance_norm/scale:0
Model/g_A/r5/c2/instance_norm/offset:0
Model/g_A/r6/c1/Conv/weights:0
Model/g_A/r6/c1/Conv/biases:0
Model/g_A/r6/c1/instance_norm/scale:0
Model/g_A/r6/c1/instance_norm/offset:0
Model/g_A/r6/c2/Conv/weights:0
Model/g_A/r6/c2/Conv/biases:0
Model/g_A/r6/c2/instance_norm/scale:0
Model/g_A/r6/c2/instance_norm/offset:0
Model/g_A/r7/c1/Conv/weights:0
Model/g_A/r7/c1/Conv/biases:0
Model/g_A/r7/c1/instance_norm/scale:0
Model/g_A/r7/c1/instance_norm/offset:0
Model/g_A/r7/c2/Conv/weights:0
Model/g_A/r7/c2/Conv/biases:0
Model/g_A/r7/c2/instance_norm/scale:0
Model/g_A/r7/c2/instance_norm/offset:0
Model/g_A/r8/c1/Conv/weights:0
Model/g_A/r8/c1/Conv/biases:0
Model/g_A/r8/c1/instance_norm/scale:0
Model/g_A/r8/c1/instance_norm/offset:0
Model/g_A/r8/c2/Conv/weights:0
Model/g_A/r8/c2/Conv/biases:0
Model/g_A/r8/c2/instance_norm/scale:0
Model/g_A/r8/c2/instance_norm/offset:0
Model/g_A/r9/c1/Conv/weights:0
Model/g_A/r9/c1/Conv/biases:0
Model/g_A/r9/c1/instance_norm/scale:0
Model/g_A/r9/c1/instance_norm/offset:0
Model/g_A/r9/c2/Conv/weights:0
Model/g_A/r9/c2/Conv/biases:0
Model/g_A/r9/c2/instance_norm/scale:0
Model/g_A/r9/c2/instance_norm/offset:0
Model/g_A/c4/Conv2d_transpose/weights:0
Model/g_A/c4/Conv2d_transpose/biases:0
Model/g_A/c4/instance_norm/scale:0
Model/g_A/c4/instance_norm/offset:0
Model/g_A/c5/Conv2d_transpose/weights:0
Model/g_A/c5/Conv2d_transpose/biases:0
Model/g_A/c5/instance_norm/scale:0
Model/g_A/c5/instance_norm/offset:0
Model/g_A/c6/Conv/weights:0
Model/g_A/c6/Conv/biases:0
Model/g_B/c1/Conv/weights:0
Model/g_B/c1/Conv/biases:0
Model/g_B/c1/instance_norm/scale:0
Model/g_B/c1/instance_norm/offset:0
Model/g_B/c2/Conv/weights:0
Model/g_B/c2/Conv/biases:0
Model/g_B/c2/instance_norm/scale:0
Model/g_B/c2/instance_norm/offset:0
Model/g_B/c3/Conv/weights:0
Model/g_B/c3/Conv/biases:0
Model/g_B/c3/instance_norm/scale:0
Model/g_B/c3/instance_norm/offset:0
Model/g_B/r1/c1/Conv/weights:0
Model/g_B/r1/c1/Conv/biases:0
Model/g_B/r1/c1/instance_norm/scale:0
Model/g_B/r1/c1/instance_norm/offset:0
Model/g_B/r1/c2/Conv/weights:0
Model/g_B/r1/c2/Conv/biases:0
Model/g_B/r1/c2/instance_norm/scale:0
Model/g_B/r1/c2/instance_norm/offset:0
Model/g_B/r2/c1/Conv/weights:0
Model/g_B/r2/c1/Conv/biases:0
Model/g_B/r2/c1/instance_norm/scale:0
Model/g_B/r2/c1/instance_norm/offset:0
Model/g_B/r2/c2/Conv/weights:0
Model/g_B/r2/c2/Conv/biases:0
Model/g_B/r2/c2/instance_norm/scale:0
Model/g_B/r2/c2/instance_norm/offset:0
Model/g_B/r3/c1/Conv/weights:0
Model/g_B/r3/c1/Conv/biases:0
Model/g_B/r3/c1/instance_norm/scale:0
Model/g_B/r3/c1/instance_norm/offset:0
Model/g_B/r3/c2/Conv/weights:0
Model/g_B/r3/c2/Conv/biases:0
Model/g_B/r3/c2/instance_norm/scale:0
Model/g_B/r3/c2/instance_norm/offset:0
Model/g_B/r4/c1/Conv/weights:0
Model/g_B/r4/c1/Conv/biases:0
Model/g_B/r4/c1/instance_norm/scale:0
Model/g_B/r4/c1/instance_norm/offset:0
Model/g_B/r4/c2/Conv/weights:0
Model/g_B/r4/c2/Conv/biases:0
Model/g_B/r4/c2/instance_norm/scale:0
Model/g_B/r4/c2/instance_norm/offset:0
Model/g_B/r5/c1/Conv/weights:0
Model/g_B/r5/c1/Conv/biases:0
Model/g_B/r5/c1/instance_norm/scale:0
Model/g_B/r5/c1/instance_norm/offset:0
Model/g_B/r5/c2/Conv/weights:0
Model/g_B/r5/c2/Conv/biases:0
Model/g_B/r5/c2/instance_norm/scale:0
Model/g_B/r5/c2/instance_norm/offset:0
Model/g_B/r6/c1/Conv/weights:0
Model/g_B/r6/c1/Conv/biases:0
Model/g_B/r6/c1/instance_norm/scale:0
Model/g_B/r6/c1/instance_norm/offset:0
Model/g_B/r6/c2/Conv/weights:0
Model/g_B/r6/c2/Conv/biases:0
Model/g_B/r6/c2/instance_norm/scale:0
Model/g_B/r6/c2/instance_norm/offset:0
Model/g_B/r7/c1/Conv/weights:0
Model/g_B/r7/c1/Conv/biases:0
Model/g_B/r7/c1/instance_norm/scale:0
Model/g_B/r7/c1/instance_norm/offset:0
Model/g_B/r7/c2/Conv/weights:0
Model/g_B/r7/c2/Conv/biases:0
Model/g_B/r7/c2/instance_norm/scale:0
Model/g_B/r7/c2/instance_norm/offset:0
Model/g_B/r8/c1/Conv/weights:0
Model/g_B/r8/c1/Conv/biases:0
Model/g_B/r8/c1/instance_norm/scale:0
Model/g_B/r8/c1/instance_norm/offset:0
Model/g_B/r8/c2/Conv/weights:0
Model/g_B/r8/c2/Conv/biases:0
Model/g_B/r8/c2/instance_norm/scale:0
Model/g_B/r8/c2/instance_norm/offset:0
Model/g_B/r9/c1/Conv/weights:0
Model/g_B/r9/c1/Conv/biases:0
Model/g_B/r9/c1/instance_norm/scale:0
Model/g_B/r9/c1/instance_norm/offset:0
Model/g_B/r9/c2/Conv/weights:0
Model/g_B/r9/c2/Conv/biases:0
Model/g_B/r9/c2/instance_norm/scale:0
Model/g_B/r9/c2/instance_norm/offset:0
Model/g_B/c4/Conv2d_transpose/weights:0
Model/g_B/c4/Conv2d_transpose/biases:0
Model/g_B/c4/instance_norm/scale:0
Model/g_B/c4/instance_norm/offset:0
Model/g_B/c5/Conv2d_transpose/weights:0
Model/g_B/c5/Conv2d_transpose/biases:0
Model/g_B/c5/instance_norm/scale:0
Model/g_B/c5/instance_norm/offset:0
Model/g_B/c6/Conv/weights:0
Model/g_B/c6/Conv/biases:0
2019-03-30 14:58:39.544914: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2
('In the epoch ', 0)
Saving image 0/20
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/deependra/GANresearch/cyclegan/main.py", line 458, in
main()
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/home/deependra/GANresearch/cyclegan/main.py", line 452, in main
cyclegan_model.train()
File "/home/deependra/GANresearch/cyclegan/main.py", line 293, in train
self.save_images(sess, epoch)
File "/home/deependra/GANresearch/cyclegan/main.py", line 198, in save_images
inputs = sess.run(self.inputs)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 895, in run
run_metadata_ptr)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1128, in _run
feed_dict_tensor, options, run_metadata)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1344, in _do_run
options, run_metadata)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 1363, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.OutOfRangeError: RandomShuffleQueue '_1_shuffle_batch/random_shuffle_queue' is closed and has insufficient elements (requested 1, current size 0)
[[Node: shuffle_batch = QueueDequeueManyV2[component_types=[DT_FLOAT, DT_FLOAT], timeout_ms=-1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](shuffle_batch/random_shuffle_queue, shuffle_batch/n)]]
Caused by op u'shuffle_batch', defined at:
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/home/deependra/GANresearch/cyclegan/main.py", line 458, in
main()
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/deependra/.local/lib/python2.7/site-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/home/deependra/GANresearch/cyclegan/main.py", line 452, in main
cyclegan_model.train()
File "/home/deependra/GANresearch/cyclegan/main.py", line 249, in train
True, self._do_flipping)
File "cyclegan/data_loader.py", line 80, in load_data
[inputs['image_i'], inputs['image_j']], 1, 5000, 100)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/training/input.py", line 1287, in shuffle_batch
name=name)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/training/input.py", line 838, in _shuffle_batch
dequeued = queue.dequeue_many(batch_size, name=name)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/ops/data_flow_ops.py", line 475, in dequeue_many
self._queue_ref, n=n, component_types=self._dtypes, name=name)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/ops/gen_data_flow_ops.py", line 2445, in _queue_dequeue_many_v2
component_types=component_types, timeout_ms=timeout_ms, name=name)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 3160, in create_op
op_def=op_def)
File "/home/deependra/.local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1625, in init
self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access
OutOfRangeError (see above for traceback): RandomShuffleQueue '_1_shuffle_batch/random_shuffle_queue' is closed and has insufficient elements (requested 1, current size 0)
[[Node: shuffle_batch = QueueDequeueManyV2[component_types=[DT_FLOAT, DT_FLOAT], timeout_ms=-1, _device="/job:localhost/replica:0/task:0/device:CPU:0"](shuffle_batch/random_shuffle_queue, shuffle_batch/n)]]

@ambarishgurjar  Same to you. Have you deal with it?

It was really frustrating, I tried downgrading the tensorflow version and it still didn't work.
Finally I downloaded another implementation of the same project
https://github.com/architrathore/CycleGAN/
It is the same algorithm but slightly simplified.
You may encounter some problems in this one too
For that you will need to change size() to size at lines 99 and 104 I think if you get some error of int not being a callable object. And secondly you will need to initialize both global and local variables before the TF session.run(init). Lastly you might need to replace the download_datasets.sh file by the file in this repository. It will then work.
If you need the exact changes in code then I will give it to you once I go to my office on Monday. All my data is stored in the work PC

@ambarishgurjar   Thanks a lot !!

I'm having the same type of error even without shuffling. Problem is i really need this specific implementation because I'm trying to run an implementation that adds attention capabilities to the GAN and is based off of this one.

I solved the issue. "create_cyclegan_dataset.py" creates .csv files that end with this sequence of characters to separate lines : "\r\r\n" and that causes errors during parsing that lead to files not being loaded at all thus making the queues empty. If this sequence of characters is replaced with a simple "\n" character in any text editor, the csv is parsed correctly and everything is back to working order.

@ambarishgurjar Hi,I have met the same issue as you
OutOfRangeError (see above for traceback): RandomShuffleQueue '_1_shuffle_batch/random_shuffle_queue' is closed and has insufficient elements (requested 1, current size 0)
[[node shuffle_batch (defined at E:\Python exercise\generalizaton\domain\CycleGAN-1-master\data_loader.py:76) ]]
Have you figured it out ?I am really confused,thanks a lot

Hey @heleibin have you tried removing the characters at the end of the line? It worked for me as i said up there in my last comment.

@FTC55 ，Hey, thanks for your answer,but i had tried as you said,but it didnot work.
I then tried another version tensorflow implementation of CycleGAN,it worked perfectly!
Thanks for your advice!

Which is what I asked you guys to do initially anyway
On Tue, Dec 24, 2019, 9:43 PM He Leibin<EMAIL_ADDRESS>wrote:

@FTC55 https://github.com/FTC55 ，Hey, thanks for your answer,but i had
tried as you said,but it didnot work.
I then tried another version tensorflow implementation of CycleGAN,it
worked perfectly!
Thanks for your advice!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/4Catalyzer/cyclegan/issues/5?email_source=notifications&email_token=AIIR4WZQJTIG5MPXSUJZPODQ2LCGVA5CNFSM4HCG5XYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHTZPHI#issuecomment-568825757,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIIR4WZ2MMGISXRNNYD7QDDQ2LCGVANCNFSM4HCG5XYA
.


v5.31.3 update

Try to get Python 3.10 versions building.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

closes #45
closes #46
closes #47
closes #48

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: ipfshttpclient=0.8.0a2 must contain a space between the name and the pin, i.e. ipfshttpclient =0.8.0a2
requirements: run: protobuf=3.19.5 must contain a space between the name and the pin, i.e. protobuf =3.19.5

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

There's a reason why this is not updated, it needs other packages first. Once I am done with those, this will build as well.

Hey, I just merged 5.31.4 with support for python 3.10. Should be available shortly. Version requirements from web3.py made this a major pain though. 6.0.0 will follow shortly, though this also needed a pre-release version of something. Oh and so I am gonna close this (or do you really need 5.31.3 instead of 5.31.4?), but if you would like to become co-maintainer please let me know, I could add you in the 6.0.0 update or a later one.


GreyNoise Analyze shows incorrect results based on discrepancies between stats and quick endpoints

Given the following list of IPs:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

There are 20 IPs total
The noise ration is calculated by the quick endpoints, which age data off after 30 days:
╔═══════════════════════════╗
║          Analyze          ║
╚═══════════════════════════╝
Summary:
- IP count: 20
- Noise IP count: 15
- Not noise IP count: 5
- Noise IP ratio: 0.75

Queries:
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>
- <IP_ADDRESS>

ASNs:
- AS14061  2
- AS16276  2
- AS23650  2
- AS134238 1
- AS136600 1
- AS28573  1
- AS32098  1
- AS36352  1
- AS38365  1
- AS4134   1
- AS45090  1
- AS45758  1
- AS45899  1
- AS64022  1
- AS8048   1

Categories:
- hosting  9
- isp      8
- business 1

Classifications:
- malicious 15
- unknown    3

Countries:
- China         7
- France        2
- United States 2
- Brazil        1
- Canada        1
- Hong Kong     1
- Mexico        1
- Thailand      1
- Venezuela     1
- Vietnam       1

Operating systems:
- Linux 3.11+    11
- Linux 2.2-3.x   2
- Linux 3.1-3.10  2
- Windows 7/8     1
- Windows XP      1

Organizations:
- AS Number for CHINANET jiangsu province backbone      2
- DigitalOcean, LLC                                     2
- OVH SAS                                               2
- Beijing Baidu Netcom Science and Technology Co., Ltd. 1
- Beijing Fengniao Network Technology Co., Ltd          1
- CANTV Servicios, Venezuela                            1
- CHINANET Jiangx province  IDC network                 1
- CHINANET-BACKBONE                                     1
- CLARO S.A.                                            1
- ColoCrossing                                          1
- Kamatera, Inc.                                        1
- Shenzhen Tencent Computer Systems Company Limited     1
- Transtelco Inc                                        1
- Triple T Internet/Triple T Broadband                  1
- VNPT Corp                                             1

Tags:
- SSH Bruteforcer 15
- SSH Scanner     14
- FTP Scanner      1
- MSSQL Scanner    1
- SMB Scanner      1

This is fixed now that all endpoints are using a unified data store


Images normalization using too much cpu during inference

I am working on model optimization on mmdetection. We found that normalization of pictures using too much cpu during inference.  We have rewritten this module and move it to gpu. Then CPU utilization has dropped significantly by about 4 times(Inf time: 20fps).
torch.from_numpy(img_rescale.astype(np.float32)).to(self.device).sub_(self.mean).mul_(self.stdinv)

However, the whole images preprocessing has to be reconstructed. Is there any plan to add an official support?

Hi @Mabinogiysk ,
Thanks for your kind suggestion. This result is very valuable for us. For now, the image preprocessing is still preferred to be conducted on CPU. But we may move the normalization process into the model for acceleration.

Hi @Mabinogiysk ,
Thanks for your kind suggestion. This result is very valuable for us. For now, the image preprocessing is still preferred to be conducted on CPU. But we may move the normalization process into the model for acceleration.


feat(@angular/cli): add environment option to global styles & scripts

closes #4288

There are workarounds for this feature, and we require a design phase for all new features. Let's talk on the issue itself for the moment. Closing this in the meantime. Thanks.


API Connection needs to support 'kind' property

API Connections in Azure can be either V1 or V2. Yet we can't specify this property using bicep:
resource tableStorageConnection 'Microsoft.Web/connections@2016-06-01' = {
  name: 'tablestorage'
  location: resourceGroup().location
  kind: 'V2'
  properties: {
...

/env/step1.bicep(95,3) : Error BCP037: The property "kind" is not allowed on objects of type "Microsoft.Web/connections". Permissible properties include "dependsOn", "etag".

ARM outputs for an API connection deployed via portal vs one deployed via bicep:
Portal
        {
            "type": "Microsoft.Web/connections",
            "apiVersion": "2016-06-01",
            "name": "[parameters('connections_azuretables_name')]",
            "location": "westus2",
            "kind": "V2",
            "properties": {
                "displayName": "tablestorage",
                "customParameterValues": {},
                "api": {
                    "id": "[concat('/subscriptions/xxx/providers/Microsoft.Web/locations/westus2/managedApis/', parameters('connections_azuretables_name'))]"
                }
            }
        },

Bicep
            "type": "Microsoft.Web/connections",
            "apiVersion": "2016-06-01",
            "name": "[parameters('connections_tablestorage_name')]",
            "location": "westus2",
            "kind": "V1",
            "properties": {
                "displayName": "[parameters('connections_tablestorage_name')]",
                "customParameterValues": {},
                "api": {
                    "id": "/subscriptions/xxx/providers/Microsoft.Web/locations/westus2/managedApis/azuretables"
                }
            }
        },

if I bicep build my file  and augment the JSON to add "kind" : "V2" to my connection, it deploys exactly as I expect.
    {
      "type": "Microsoft.Web/connections",
      "apiVersion": "2016-06-01",
      "name": "tablestorage",
      "location": "[resourceGroup().location]",
      "kind": "V2",
      "properties": {
...

when I bicep build and update the json to deploy with V2 I see the following error in the portal. Any idea why i might be seeing this one?
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"ConnectionV2KindMismatch","message":"The 'kind' property in api connection '' cannot be changed from 'V1' to 'V2'."}]}

is there another way to create an API Connection in V2 without the kind: V2 property?
this is a real blocker of my customer. Thanks for your help

The REST API spec still does not have the kind property declared, but it is only emitting a warning in bicep, not an error. So the bicep issue should not be blocking.
@hichamveo -- in this case, it looks like the issue is that the microsoft.web/connection resource already exists with kind set to V1 and it is not allowed to be updated. This would be true whether you are using Bicep or any other tool to manage this resource. If you are creating a new connection you should be able to use V2.

you are right @alex-frankel and thanks a lot for your help. I deleted the V1 and now works good. I dont know if it's possible with Bicep to create an "Access policy" on the API connection for my Logic Apps:

This would be a good question for Discussions (cc @brwilkinson who would know more)

you are right @alex-frankel and thanks a lot for your help. I deleted the V1 and now works good. I dont know if it's possible with Bicep to create an "Access policy" on the API connection for my Logic Apps:

I was able to get the access policies using the following module. Of course, this has to be called after the connection and the object that needs access. In my case, it was a single-tenant logic app. @alex-frankel it should be noted that this accessPolicies module throws a warning due to types not being available.
Warning BCP081: Resource type "Microsoft.Web/connections/accessPolicies@2016-06-01" does not have types available.
param connection_Name string
param systemAssignedIdentityTenantId string
param systemAssignedIdentityObjectId string
resource accessPolicy 'Microsoft.Web/connections/accessPolicies@2016-06-01' = {
name: '${connection_Name}/${systemAssignedIdentityObjectId}'
location: resourceGroup().location
properties: {
principal: {
type: 'ActiveDirectory'
identity: {
tenantId: systemAssignedIdentityTenantId
objectId: systemAssignedIdentityObjectId
}
}
}
}
To get around the kind warning I use a module that is an arm template for the web connections instead of bicep. But as Alex pointed out it does still work if you don't mind seeing the warning.


Improve Presentation of search results

When I search in Bookstack, the result Pages/Chapters etc. are shown with a teaser text, which is always the beginning of complete text of the Page (or other type) regardless of what I searched for or where the search hits are.
It would be very great if the teaser would already show search hits highlighted. This would make navigation within the pages much easier.
I have for example ip addresses scattered in some pages. When I search "ip address" I would get page hits and the teaser would already show me some addresses with context. I would have a complete overview and maybe I wouldn`t even have to klick on the result page to get the information I want. Now in the current state I would have to click every single result to see which ip address is in the text.
It would be useful in any other search to have the search result with some context. That`s why every internet search engine does this (not neccesserily with higlights though).

Thanks for the request @gronfuzius.
This has already been requested on issue #997 so I'm going to close this off as a duplicate.


ARTEMIS-2804 Human readable timestamp is incorrectly parsed in web console

The web console displays the day of the week instead of the day of the month in the timestamp column while browsing a queue from the web console.

The commits should be squashed and the comment should be removed and added to the commit message as it only makes sense in the context of the change.

@avi5kdonrh, can you update the commit message to follow the pattern outlined in the hacking guide?

@avi5kdonrh, don't worry about the commit message. I fixed it during merge. Thanks for the fix!

@jbertram, @franz1981  Thank you very much. Next time I'll keep the guidelines in mind.


Added Bastion-ELB support, includes security enhancements to bastion nodes.

resolves: https://github.com/samsung-cnct/k2/issues/735

ELB created pointing to each bastion
Cleaned cloud init for bastion node, should only contain bastion info and nothing else
Bastions are more configurable, now you can change ssh port, changes occur on each node and elb configured correctly
Bastion has been promoted to be a type of node, allowing us to configure it further for security concerns.
ELB can be launched at specific subnets that are in the same subnet as bastions, or not.

example output of this:
ssh_config
Host etcd-1
  User core
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
  ProxyCommand ssh<EMAIL_ADDRESS>-p 22 -W <IP_ADDRESS>:22
Host etcdEvents-1
  User core
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
  ProxyCommand ssh<EMAIL_ADDRESS>-p 22 -W <IP_ADDRESS>:22
Host master-1
  User core
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
  ProxyCommand ssh<EMAIL_ADDRESS>-p 22 -W <IP_ADDRESS>:22
Host clusterNodes-1
  User core
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
  ProxyCommand ssh<EMAIL_ADDRESS>-p 22 -W <IP_ADDRESS>:22

bastion_ssh_config (in each bastion node)
Host etcd-1
  HostName ip-10-7-128-118.us-west-2.compute.internal
  User core
  Port 22
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
Host etcdEvents-1
  HostName ip-10-7-128-119.us-west-2.compute.internal
  User core
  Port 22
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
Host master-1
  HostName ip-10-7-128-33.us-west-2.compute.internal
  User core
  Port 22
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
Host clusterNodes-1
  HostName ip-10-7-128-145.us-west-2.compute.internal
  User core
  Port 22
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null
Host bastion-1
  HostName ip-10-7-1-81.us-west-2.compute.internal
  User core
  Port 22
  StrictHostKeyChecking no
  UserKnownHostsFile=/dev/null

fyi, different e2e tests keep failing.

@alejandroEsc a. at this moment all of the checks have passed and b. we only require that the check 'all-but-e2e' passes.  the e2e tests are too flaky for PRs right now.
the overall change, which I should have mentioned during my last readout, is that we require the reviewer to make a judgement call if the e2e tests are required for a specific PR.  In this case, adding a type of bastion node, I would assume that e2e tests are not required.  I say 'assume' because I haven't reviewed the PR yet.


Increase the MSRV to 1.53.0

Also upgrades the prost and spiffe version to remove cargo audit
vulnerabilities. Removes the ignored ones.
Un-comment the CI checks that were commented before.
Fix #514

Ahh, fuzz checks still failing, I think a cargo update is needed in the fuzz folder

I think it's because it's using the client before the PR we made today that fixes the issue there


containerlab connects the management IP incorrectly

I recently upgraded my lab and am seeing an issue where some containers are getting wired incorrectly. It appears that clab-tes-lab-spine2 is getting attached to <IP_ADDRESS> and <IP_ADDRESS>
 » cat containerlab
all:
  children:
    ceos:
      hosts:
        clab-tes-lab-oob-agg1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-oob-agg2:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine2:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine3:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine4:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-tes-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-tes-spine2:
          ansible_host: <IP_ADDRESS>
    oob_agg:
      hosts:
        clab-tes-lab-oob-agg1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-oob-agg2:
          ansible_host: <IP_ADDRESS>
    spines:
      hosts:
        clab-tes-lab-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine2:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine3:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine4:
          ansible_host: <IP_ADDRESS>
    upstream_spines:
      hosts:
        clab-tes-lab-tes-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-tes-spine2:
          ansible_host: <IP_ADDRESS>

» ssh<EMAIL_ADDRESS>Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
spine2>show version
 cEOSLab
Hardware version:
Serial number:
Hardware MAC address: 001c.7397.5b78
System MAC address: 001c.7397.5b78

Software image version: 4.26.1F-22602519.4261F (engineering build)
Architecture: x86_64
Internal build version: 4.26.1F-22602519.4261F
Internal build ID: 1eca5f74-3ced-441a-9137-c966e8f0319d
Image format version: 01.00

cEOS tools version: 1.1
Kernel version: 4.15.0-151-generic

Uptime: 0 weeks, 0 days, 0 hours and 25 minutes
Total memory: 8068908 kB
Free memory: 651652 kB

» ssh<EMAIL_ADDRESS>spine2#show version
 cEOSLab
Hardware version:
Serial number:
Hardware MAC address: 001c.7397.5b78
System MAC address: 001c.7397.5b78

Software image version: 4.26.1F-22602519.4261F (engineering build)
Architecture: x86_64
Internal build version: 4.26.1F-22602519.4261F
Internal build ID: 1eca5f74-3ced-441a-9137-c966e8f0319d
Image format version: 01.00

cEOS tools version: 1.1
Kernel version: 4.15.0-151-generic

Uptime: 0 weeks, 0 days, 0 hours and 25 minutes
Total memory: 8068908 kB
Free memory: 649868 kB

spine2#exit
Connection to <IP_ADDRESS> closed.

scollins@griffin:~$ docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
7ed82c97bec8   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine3
8931ba70e280   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine1
e0912a074fe8   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine2
68ab24f43394   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-tes-spine1
cb5c8317ad36   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-oob-agg2
e06c88e1ecb0   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-tes-spine2
fc68aaea4da4   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-oob-agg1
3ac6adeca493   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine4

scollins@griffin:~$ docker exec -it 3ac6adeca493 Cli
spine4>show version
 cEOSLab
Hardware version:
Serial number:
Hardware MAC address: 001c.73ea.ff02
System MAC address: 001c.73ea.ff02

Software image version: 4.26.1F-22602519.4261F (engineering build)
Architecture: x86_64
Internal build version: 4.26.1F-22602519.4261F
Internal build ID: 1eca5f74-3ced-441a-9137-c966e8f0319d
Image format version: 01.00

cEOS tools version: 1.1
Kernel version: 4.15.0-151-generic

Uptime: 0 weeks, 0 days, 0 hours and 27 minutes
Total memory: 8068908 kB
Free memory: 637548 kB

scollins@griffin:~$ containerlab version

                           _                   _       _
                 _        (_)                 | |     | |
 ____ ___  ____ | |_  ____ _ ____   ____  ____| | ____| | _
/ ___) _ \|  _ \|  _)/ _  | |  _ \ / _  )/ ___) |/ _  | || \
( (__| |_|| | | | |_( ( | | | | | ( (/ /| |   | ( ( | | |_) )
\____)___/|_| |_|\___)_||_|_|_| |_|\____)_|   |_|\_||_|____/

    version: 0.16.0
     commit: 4d15005
       date: 2021-08-03T09:03:15Z
     source: https://github.com/srl-labs/containerlab
 rel. notes: https://containerlab.srlinux.dev/rn/0.16/

Hi
Check /etc/hosts and remove potential duplicate entries which are not
enclosed in CLAB-labname-START/END markers
On Wed, 4 Aug 2021 at 18:06, Sean M. Collins @.***>
wrote:

I recently upgraded my lab and am seeing an issue where some containers
are getting wired incorrectly. It appears that clab-tes-lab-spine2 is
getting attached to <IP_ADDRESS> and <IP_ADDRESS>
» cat containerlab
all:
children:
ceos:

  hosts:

    clab-tes-lab-oob-agg1:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-oob-agg2:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine1:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine2:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine3:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine4:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-tes-spine1:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-tes-spine2:

      ansible_host: <IP_ADDRESS>

oob_agg:

  hosts:

    clab-tes-lab-oob-agg1:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-oob-agg2:

      ansible_host: <IP_ADDRESS>

spines:

  hosts:

    clab-tes-lab-spine1:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine2:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine3:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-spine4:

      ansible_host: <IP_ADDRESS>

upstream_spines:

  hosts:

    clab-tes-lab-tes-spine1:

      ansible_host: <IP_ADDRESS>

    clab-tes-lab-tes-spine2:

      ansible_host: <IP_ADDRESS>

» ssh @.***
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
spine2>show version
cEOSLab
Hardware version:
Serial number:
Hardware MAC address: 001c.7397.5b78
System MAC address: 001c.7397.5b78
Software image version: 4.26.1F-22602519.4261F (engineering build)
Architecture: x86_64
Internal build version: 4.26.1F-22602519.4261F
Internal build ID: 1eca5f74-3ced-441a-9137-c966e8f0319d
Image format version: 01.00
cEOS tools version: 1.1
Kernel version: 4.15.0-151-generic
Uptime: 0 weeks, 0 days, 0 hours and 25 minutes
Total memory: 8068908 kB
Free memory: 651652 kB
» ssh @.***
Warning: Permanently added '<IP_ADDRESS>' (ECDSA) to the list of known hosts.
spine2> show version
cEOSLab
Hardware version:
Serial number:
Hardware MAC address: 001c.7397.5b78
System MAC address: 001c.7397.5b78
@.***:~$ docker ps
CONTAINER ID   IMAGE          COMMAND                  CREATED          STATUS          PORTS     NAMES
7ed82c97bec8   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine3
8931ba70e280   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine1
e0912a074fe8   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-spine2
68ab24f43394   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-tes-spine1
cb5c8317ad36   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-oob-agg2
e06c88e1ecb0   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-tes-spine2
fc68aaea4da4   ceos:4.26.1F   "/sbin/init systemd.…"   28 minutes ago   Up 28 minutes             clab-tes-lab-oob-agg1
3ac6adeca493   ceos:4.26.1F   "/sbin/init systemd.…"
Reply to this email directly, view it on GitHub
https://github.com/srl-labs/containerlab/issues/569, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLKV5MYQNEV3DYGTAZ3PLDT3FQQZANCNFSM5BRPKYSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

<IP_ADDRESS> localhost
<IP_ADDRESS> griffin
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
<IP_ADDRESS>	clab-tes-lab-spine4
2001:172:101:100::7	clab-tes-lab-spine4
<IP_ADDRESS>	clab-tes-lab-tes-spine1
2001:172:101:100::4	clab-tes-lab-tes-spine1
<IP_ADDRESS>	clab-tes-lab-spine2
2001:172:101:100::5	clab-tes-lab-spine2
<IP_ADDRESS>	clab-tes-lab-spine1
2001:172:101:100::6	clab-tes-lab-spine1
<IP_ADDRESS>	clab-tes-lab-spine3
2001:172:101:100::3	clab-tes-lab-spine3
<IP_ADDRESS>	clab-tes-lab-tes-spine2
2001:172:101:100::2	clab-tes-lab-tes-spine2
<IP_ADDRESS>	clab-tes-lab-spine1
2001:172:20:20::7	clab-tes-lab-spine1

<IP_ADDRESS>	clab-tes-lab-spine4
2001:172:20:20::9	clab-tes-lab-spine4
<IP_ADDRESS>	clab-tes-lab-spine3
2001:172:20:20::8	clab-tes-lab-spine3
<IP_ADDRESS>	clab-tes-lab-spine1
2001:172:20:20::2	clab-tes-lab-spine1
<IP_ADDRESS>	clab-tes-lab-tes-spine2
2001:172:20:20::3	clab-tes-lab-tes-spine2
<IP_ADDRESS>	clab-tes-lab-spine2
2001:172:20:20::5	clab-tes-lab-spine2
<IP_ADDRESS>	clab-tes-lab-oob-agg1
2001:172:20:20::6	clab-tes-lab-oob-agg1
<IP_ADDRESS>	clab-tes-lab-oob-agg2
2001:172:20:20::7	clab-tes-lab-oob-agg2
<IP_ADDRESS>	clab-tes-lab-tes-spine1
2001:172:20:20::4	clab-tes-lab-tes-spine1
###### CLAB-tes-lab-START ######
<IP_ADDRESS>	clab-tes-lab-spine3
<IP_ADDRESS>	clab-tes-lab-spine1
<IP_ADDRESS>	clab-tes-lab-spine2
<IP_ADDRESS>	clab-tes-lab-tes-spine1
<IP_ADDRESS>	clab-tes-lab-oob-agg2
<IP_ADDRESS>	clab-tes-lab-tes-spine2
<IP_ADDRESS>	clab-tes-lab-oob-agg1
<IP_ADDRESS>	clab-tes-lab-spine4
2001:172:20:20::3	clab-tes-lab-spine3
2001:172:20:20::6	clab-tes-lab-spine1
2001:172:20:20::4	clab-tes-lab-spine2
2001:172:20:20::7	clab-tes-lab-tes-spine1
2001:172:20:20::8	clab-tes-lab-oob-agg2
2001:172:20:20::9	clab-tes-lab-tes-spine2
2001:172:20:20::5	clab-tes-lab-oob-agg1
2001:172:20:20::2	clab-tes-lab-spine4
###### CLAB-tes-lab-END ######

So, I think we need to have containerlab clean itself up better, if it is putting things in /etc/hosts

OK, next time I promise to RTFM :)

I think we still have an issue, even after clearing out the /etc/hosts file:
ssh admin@clab-tes-lab-tes-spine1
The authenticity of host 'clab-tes-lab-tes-spine1 (2001:172:20:20::4)' can't be established.
ECDSA key fingerprint is SHA256:G48iqwIpNaiUiicRId06H1Ct94VFdubWDW1y2jOdikg.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'clab-tes-lab-tes-spine1,2001:172:20:20::4' (ECDSA) to the list of known hosts.
Password:
spine4>

###### CLAB-tes-lab-START ######
<IP_ADDRESS>	clab-tes-lab-spine1
<IP_ADDRESS>	clab-tes-lab-spine3
<IP_ADDRESS>	clab-tes-lab-spine2
<IP_ADDRESS>	clab-tes-lab-oob-agg1
<IP_ADDRESS>	clab-tes-lab-tes-spine1
<IP_ADDRESS>	clab-tes-lab-oob-agg2
<IP_ADDRESS>	clab-tes-lab-spine4
<IP_ADDRESS>	clab-tes-lab-tes-spine2
2001:172:20:20::2	clab-tes-lab-spine1
2001:172:20:20::3	clab-tes-lab-spine3
2001:172:20:20::9	clab-tes-lab-spine2
2001:172:20:20::7	clab-tes-lab-oob-agg1
2001:172:20:20::4	clab-tes-lab-tes-spine1
2001:172:20:20::6	clab-tes-lab-oob-agg2
2001:172:20:20::8	clab-tes-lab-spine4
2001:172:20:20::5	clab-tes-lab-tes-spine2
###### CLAB-tes-lab-END ######

all:
  children:
    ceos:
      hosts:
        clab-tes-lab-oob-agg1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-oob-agg2:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine2:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine3:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine4:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-tes-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-tes-spine2:
          ansible_host: <IP_ADDRESS>
    oob_agg:
      hosts:
        clab-tes-lab-oob-agg1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-oob-agg2:
          ansible_host: <IP_ADDRESS>
    spines:
      hosts:
        clab-tes-lab-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine2:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine3:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-spine4:
          ansible_host: <IP_ADDRESS>
    upstream_spines:
      hosts:
        clab-tes-lab-tes-spine1:
          ansible_host: <IP_ADDRESS>
        clab-tes-lab-tes-spine2:
          ansible_host: <IP_ADDRESS>

I suggest you redeploy the lab, since it looks like your nodes picked the IP addresses from the previous lab state
it is better if you do containerlab dep -t <topo> --reconfigure.
Now since ceos is not smart enough to use the docker assigned IPs, it will use whatever IPs were defined in the config file, and since docker can assign different addresses on second deployment run, you will have address deviation

the configs will have IPs from previous run
and a newly run lab will have new IPs assigned by docker

this is a recipe for disaster
For that reason, we documented the peculiarities about the ceos configs here https://containerlab.srlinux.dev/manual/kinds/ceos/#configuration-persistency

OK, so, since my configuration is 100% built with ansible and I don't care about persisting the configuration (which I assumed was the point of destroy)... it sounds like I just have to sudo rm -fr clab-tes-lab? which I did, but then got issues when rebuilding...
scollins@griffin:~$ sudo containerlab deploy -t containerlab_topology.yaml
INFO[0000] Parsing & checking topology file: containerlab_topology.yaml
INFO[0000] Creating lab directory: /home/scollins/clab-tes-lab
INFO[0000] Creating docker network: Name='clab', IPv4Subnet='<IP_ADDRESS>/24', IPv6Subnet='2001:172:20:20::/64', MTU='1500'
INFO[0000] Creating container: spine1
INFO[0001] Creating container: spine4
INFO[0001] Creating container: spine2
INFO[0001] Creating container: spine3
INFO[0001] Creating container: oob-agg1
INFO[0001] Creating container: tes-spine2
INFO[0001] Creating container: tes-spine1
INFO[0001] Creating container: oob-agg2
ERRO[0060] failed to run postdeploy task for node spine3: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/fa3c4215219ca1cbd8e4c04651b30f41f92676eb9c37c00d3f2c024c06c0be0f/start": context deadline exceeded
ERRO[0060] failed to run postdeploy task for node spine1: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/e9ef6936bfc961a5ba6eccc86f36307232d686eaf4e011a0c53527081a758c90/start": context deadline exceeded
ERRO[0061] failed to run postdeploy task for node tes-spine2: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/ccca81a631c00c3cc87aec6cec473afb57d57f351a2e2a35058cac55dbd91b6b/start": context deadline exceeded
ERRO[0061] failed to run postdeploy task for node oob-agg1: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.41/containers/d7dd9fbf0b3247428fd7acc33eb9a6b3a59999a7bfefdccaf7ac483864f262bb/start": context deadline exceeded
INFO[0061] Creating virtual wire: spine1:eth2 <--> tes-spine2:eth1
INFO[0061] Creating virtual wire: oob-agg2:eth2 <--> tes-spine2:eth6
INFO[0061] Creating virtual wire: spine1:eth5 <--> spine4:eth3
INFO[0061] Creating virtual wire: spine3:eth2 <--> tes-spine2:eth3
INFO[0061] Creating virtual wire: spine3:eth5 <--> spine4:eth5
INFO[0061] Creating virtual wire: spine2:eth2 <--> tes-spine2:eth2
INFO[0061] Creating virtual wire: spine1:eth4 <--> spine3:eth3
INFO[0061] Creating virtual wire: spine2:eth1 <--> tes-spine1:eth2
INFO[0061] Creating virtual wire: spine2:eth5 <--> spine4:eth4
INFO[0061] Creating virtual wire: spine4:eth1 <--> tes-spine1:eth4
INFO[0061] Creating virtual wire: spine3:eth1 <--> tes-spine1:eth3
INFO[0061] Creating virtual wire: spine1:eth3 <--> spine2:eth3
INFO[0061] Creating virtual wire: spine2:eth4 <--> spine3:eth4
INFO[0061] Creating virtual wire: spine1:eth1 <--> tes-spine1:eth1
INFO[0061] Creating virtual wire: oob-agg1:eth2 <--> tes-spine2:eth5
INFO[0061] Creating virtual wire: spine4:eth2 <--> tes-spine2:eth4
INFO[0061] Creating virtual wire: oob-agg1:eth1 <--> tes-spine1:eth5
INFO[0061] Creating virtual wire: oob-agg2:eth1 <--> tes-spine1:eth6
ERRO[0061] failed to Statfs "/proc/5215/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5215/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5215/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5507/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5215/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5507/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5400/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5400/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5507/ns/net": no such file or directory
ERRO[0062] failed to Statfs "/proc/5630/ns/net": no such file or directory
ERRO[0063] failed to Statfs "/proc/5630/ns/net": no such file or directory
ERRO[0063] failed to Statfs "/proc/5630/ns/net": no such file or directory
ERRO[0063] failed to Statfs "/proc/5215/ns/net": no such file or directory
ERRO[0063] failed to Statfs "/proc/5507/ns/net": no such file or directory
INFO[0063] Adding containerlab host entries to /etc/hosts file

Ok, looks like everything is happy now after blowing everything away. I promise to RTFM next time.

The true destroy is destroy --cleanup which will remove all the state a
lab has
On Wed, 4 Aug 2021 at 19:23, Sean M. Collins @.***>
wrote:

Closed #569 https://github.com/srl-labs/containerlab/issues/569.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/srl-labs/containerlab/issues/569#event-5112625539,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLKV5NG52Y63P3ZXODIWBLT3FZPNANCNFSM5BRPKYSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


How to install freerdp under linux 11SP3

Hi All,
I tried to install freerdp under linux 11SP3 but got many dependency packages there, and didn`t find corrent dependencies package, how can i install it properly:
linux:~ # rpm -ivh freerdp-nightly-2.0-0+0-20161020033818.252-1.gitf5a6645.x86_64.rpm
error: Failed dependencies:
libc.so.6(GLIBC_2.14)(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libc.so.6(GLIBC_2.15)(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libcrypto.so.1.0.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libgsm.so.1()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libgstapp-1.0.so.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libgstbase-1.0.so.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libgstreamer-1.0.so.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libgstvideo-1.0.so.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libjpeg.so.8()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libjpeg.so.8(LIBJPEG_8.0)(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libpulse.so.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libpulse.so.0(PULSE_0)(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
libssl.so.1.0.0()(64bit) is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64
rpmlib(TildeInVersions) <= 4.10.0-1 is needed by freerdp-nightly-2.0-0+0~20161020033818.252~1.gitf5a6645.x86_64

@deity6473 I'm sorry but the nightly packages don't support SLES. You will need to build/package it on yourself.


Formalize rule regarding benchmark lifecycle

Address comment https://github.com/mlcommons/policies/pull/171#issuecomment-2102731288

@mlcommons/policies - could you please review this?
@mrasquinha-g - could you please review the same in the inference WG as it applies to both training and inference?

Moved to Training policies - https://github.com/mlcommons/training_policies/pull/550


random_seed for qiskit-aqua/qiskit/ml/datasets/ad_hoc.py

The feature of random seed specification is expected in generation of dataset in qsvm.
While it is important to reproduce result in machine learning typically by fixing random seed, the current module ad_hoc.py does not have feature to fix random seed of generating data.
What is the expected enhancement?
It will be nice to be able to specify the seed when one call ad_hoc_data
#  <Current Usage>
from qiskit.ml.datasets import ad_hoc_data

sample_Total, training_input, test_input, class_labels = ad_hoc_data(
    training_size=20,
    test_size=10,
    n=2, gap=0.3, plot_data=True
)

I propose as following
#  <Proposed Usage>
from qiskit.ml.datasets import ad_hoc_data

seed = 2020
sample_Total, training_input, test_input, class_labels = ad_hoc_data(
    training_size=20,
    test_size=10,
    n=2, gap=0.3, plot_data=True, random_seed = seed
)

Hi, the datasets in Aqua ML use the aqua_globals random generator instance which is seeded via aqua globals. Seeding this https://github.com/Qiskit/qiskit-aqua/blob/616cd80b0526c872760c0c6392e8976478cabbc5/qiskit/aqua/aqua_globals.py#L45 will thus seed the random generation in the ML dataset.

Since the seed can be set as described as above, in the absence of any further feedback I am closing this.


windows live login integration auth/live folder not found in iis express

Server Return This Information as error : when windows live login integration ...

IIS 10.0 Detailed Error - 404.0 - Not Found

please replay.....


Improvements for Local Reads

To query a local node today one needs to call two methods to obtain the data:
rs, _ := node.ReadIndex(clusterID, 10 * time.Second)
rr := <-rs.CompletedC
encodedData, _ := node.ReadLocalNode(rs, encodedQuery)

There are a couple of improvements I would like to discuss:
It seems to me that there is no way to call ReadLocalNode without ever calling ReadIndex first. Wouldn't it make sense to allow applications to read from the local node without linearizability guarantees?
I would suggest to provide a method signature that more reflects the eventual usage e.g. ReadLocal(query []byte, linear bool) ([]byte, error). The methods can be split up if it makes sense that other computation is done between the two calls.
Since ReadLocal would always read from the local node and never query a machine over the network the encoding of the query seems unnecessary. Would it be possible to change the signature to something like ReadLocal(query interface{}, linear bool) (interface{}, error) (applying the previous change as well)?
With these changes the performance could be increased significantly in scenarios where local data is read with and without the need for linearizability. The later could potentially also be implemented today by accessing the underlying state machine directly. However, I think dragonboat should provide an interface for this, as it will allow manage the requested in the future to prevent collisions or other issues.

@256dpi
A custom factory function with one of the following signatures is passed into the StartCluster method when starting the node -
func(uint64, uint64) sm.IStateMachine
func(uint64, uint64) sm.IOnDiskStateMachine
The returned sm.IStateMachine and sm.IOnDiskStateMachine instances are created by user code, users thus have full access to them. They can keep a reference to those instance and call its Lookup method directly to achieve what you described above - direct local read without linearizability guarantee.
I am trying to make sure that NodeHost's interface is dedicated to one thing and one thing only - provide linearizable access to user data. When people choose to use NodeHost but don't want linearizability in certain valid use cases, they can use the above mentioned approach by completely bypassing the NodeHost interface.
For your proposal to use interface{} as both the input and output of the local read method, I am leaning towards to do it, will get back to you soon.
btw, thanks for all the inputs, more suggestions wanted! ;)

I think it makes sense for this library to only focus on linearizable access. However, the chosen approach to provide a factory for the state machine creates a mental conflict. It appears to one that the NodeHost is managing the instance and thus it might be gone without further notice. If it is only created once we might just pass in the already constructed state machine? That would also suggest that one can keep a reference to it and use it for fast non-linear reads.
Thanks for considering the interface{} intput and output instead of []byte. What do you think about combining the ReadIndex and ReadLocalNode methods?

btw, thanks for all the inputs, more suggestions wanted! ;)

I'm happy to help, I think this project is on the way of becoming a really important building block for many projects. :-)

There are good reasons to require the factory method to be passed in. For example, it allows further optimizations relate to how state machines are recovered from snapshots. So yes, in future releases, the factory method might be called multiple times for the same state machine.
I think I will definitely allow interface{} to be used as input/output of those read related methods. Using interface{} will cause extra allocations, I am fine with such extra allocations itself as long as there are other methods for performing similar read without requiring extra allocations, the problem is what is the best public APIs to provide.
Please also note that there is already a method named SyncRead that performance a linearizable read in one method call.

The signature of the Lookup method has been changed to
Lookup(interface{}) (interface{}, error)

as I believe it is far more flexible for average cases. NodeHost APIs have been updated accordingly to accommodate the above change.
An optional NALookup([]byte) ([]byte, error) can be implemented to retain the old interface/no extra heap allocation behaviour. NAReadLocalNode has been added to the NodeHost API to query local node using the optional NALookup method. NAReadLocalNode returns an statemachine.ErrNotImplemented when the optional NALookup is not implemented.
Benchmark results comparing the updated Lookup method and the new NALookup method are provided below -
BenchmarkLookup-12         20000000	        85.3 ns/op	      65 B/op	       3 allocs/op
BenchmarkNALookup-12    100000000	        19.9 ns/op	       0 B/op	       0 allocs/op

I've also added a new NodeHost API called StaleRead to allow direct read to the state machine without linearizability guarantee. As clearly indicated by its name, data returned by this new method should be regarded as stale read results.

Thanks for implementing the changes!
I can understand the motivation to also provide NALookup for performance reasons. But the benchmarks seem not to be 100% accurate. The NoOP.Lookup() function is allocating a slice while NoOP.NALookup() just returns the key. In real life bot would allocate some memory to return a result. If the lookup would be allocation free, it would not return any data and makes no sense anyway...?
Also, the NALookup would only be faster if the user would pass in a byte slice taken directly from the client and forward that to the state machine (to be truly allocation free). Again, in real life I'm 100% sure a requests (maybe a JSON body) gets decoded first then checked if it is valid and then forwarded. In that case, the new Lookup would always be more performant even with the allocation due to the usage of interface{}.
Based on that I would recommend to not add the NALookup method as it adds complexity without bringing much value.

I tried out the changes and got the following panic:
// Lookup queries the state machine.
func (s *OnDiskStateMachine) Lookup(query interface{}) (interface{}, error) {
	if !s.opened {
		panic("Lookup called when not opened")
	}
	return s.sm.Lookup(query)
}

It's caused by StaleRead being executed while the state machine has not yet been opened. I think this should be legal and therefore the function should return an error instead of causing a panic.

Micro benchmarks are never meant to be 100% accurate, it gives people a rough and quick idea on what is going on. In the provided benchmark results, even without the make([]byte, n) you mentioned, there are still 2 extra allocs/op caused by using interface{}.
For NALookup, it doesn't need any allocation if the result is written into the input byte slice. The bottom line is users have full control of all allocations in such case. The same can not be said for the updated Lookup method.
The JSON example you described is common but not generic. You are assuming that for many applications the input is some kind of explicit Go struct instances unmarshaled from a []byte. It is common, that is why the default interface has been updated to accommodate that. That being said, it doesn't represent all use cases, e.g. my applications only use the NALookup interface.
Please also note that NALookup is an optional method no one has to implement/look at. It only needs to be implemented when people does need to avoid those 2 unwanted allocs/op.

For the panic issue, yes, an error should be returned in that case.

Thanks for fixing and the panic. I haven't considered reusing the input byte slice as the output. Seems to be a valid scenario for the additional NALookup interface. 👍


Load pyenv automatically without ~/.bash_profile

Hi,
I'm trying to install pyenv. I've done this command curl -L https://raw.githubusercontent.com/yyuu/pyenv-installer/master/bin/pyenv-installer | bash
Then after what I should do in order to load pyenv automatically ? Because I'm using Xubuntu 14.04 and I don't have any ~/.bash_profile (but I have ~/.profile).
Should I add it to ~/.profile ?
Thanks

You are using bash right? When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if it exists.
After reading that, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists.
So, you may want to use ~/.profile if you use other shells such as zsh, or create a /.bash_profile and add it there if you just use bash.
I would add it to ~/.profile.

~/.bash_profile would be the best place to put bash only configuration. See bash(1).

@Nairolf21 In case the comment above doesn't make sense, bash(1) refers to the man page for bash. Just type man bash in your console.


hosts paginated list

Required backend side PR-18

Attaching a screenshot for reference:

With more records -

adding @karelhala into loop for review.

Codecov Report

Merging #16 (e6072f4) into main (e695fa9) will decrease coverage by 1.35%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##            main     #16      +/-   ##
========================================
- Coverage   9.56%   8.20%   -1.36%
========================================
  Files         19      19
  Lines        115     134      +19
  Branches      11      11
========================================
  Hits          11      11
- Misses        95     114      +19
  Partials       9       9

Impacted Files
Coverage Δ

src/Components/RosTable/ExpandedRow.js
0.00% <ø> (ø)

src/Components/RosTable/redux/actions.js
0.00% <0.00%> (ø)

...c/Components/RosTable/redux/systemsTableReducer.js
0.00% <0.00%> (ø)

src/Routes/RosPage/RosPage.js
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e695fa9...e6072f4. Read the comment docs.

@karelhala,
Updated changes as per your suggestions. Also used shared components i.e PrimaryToolbar, TableToolbar.
Please request to review updated changes.

Backend side PR https://github.com/RedHatInsights/ros-backend/pull/18 is merged.

Thank you so much @karelhala & @terezanovotna for review and suggestions.


feat(dockerfile) support multiple files

This PR adds the support of multiple files for the resources of kind dockerfile (conditions and targets).
Use cases:

It is an additional feature to help for #1026.
Also, on the Jenkins project, we have cases were we want to update the same instruction to multiple files: https://github.com/jenkinsci/docker-agent/blob/1182cad9d14ece000ab38433eee05daf1872a993/updatecli/updatecli.d/remoting.yaml#L37-L81

Test
To test this pull request, you can run the following commands:
cd pkg/plugins/resources/dockerfile
go test

Please note that a new e2e test as added for dockerfile which tests the current file (for non regression) and the new files.
I've tested this E2E test locally with a diff and an apply. The only untested part is when using with an SCM.
Additional Information
Tradeoff
Using autodiscovery would help, of course but we want to control the list of files for now.
Potential improvement
N.A.

Associated documentation PR: https://github.com/updatecli/website/pull/1207


buildsystems directory is .gitignored

The build*/ line in the .gitignore file is excluding too much.
I expected scripts/buildsystems/vcpkg.cmake to be available.

Good catch, thanks for noticing!


Some edits to chapters 7, 10

Some changes:
Nonconvex_scalar:

Removed the section on Linear Degeneracy as out of place (and expanded the discussion of this in Euler and Shallow_tracer)
Improved the discussion some place, in particular of convex hull

Euler:

Added titles to some plots generated in exact_solvers codes, and changed interactive Riemann solver for Euler so it has different data than Sod, and so it's clear what these data are in the call to euler_demo1, to improve what shows up in the pdf file.
Changed lots of bold text to italics to better match what we do in other chapters, where bold is rarely used.
Reorganized definitions of genuinely nonlinear and linearly degenerate to discuss more in more generality.
Added a bit of discussion to the last two sections on vacuum states.

One question in Euler: do we really want to write out the full 3D Euler equations, as we do in this notebook?  We don't do this for any other problem, although we could for acoustics, SWE, etc.  Maybe it's useful to see but perhaps just distracting since we don't discuss it further.

These changes look good to me.  I think we should remove the 3D Euler equations, since we don't even talk about shear waves in the Riemann solution, and interested readers can go to the other books we cite.

I removed 3D Euler and slightly reworked the paragraph around the 1D equations, and eliminated one section heading.


Fixing link to blog scale up vs. scale out

Hey @binhnguyennus,
awesome list!
I've fixed a broken link to brianjgraf.com:
old: https://www.brianjgraf.com/2013/05/17/scalability-scale-up-scale-out-care/
new: https://www.brianjgraf.com/scalability-scale-up-scale-out-care/
Cheers,
Peter

Hi @spekulatius
Thank you so much! Have a good weekend, bro!
Cheers,
Binh

Hey @binhnguyennus,
no problem! Happy to help out! I hope you have a good weekend too!
Cheers,
Peter


Set Designate API TLS cert secret

This patch provides the cert secret to the Designate API TLS field.
Depends-On: openstack-k8s-operators/designate-operator#184

recheck

oops, manual rebase got really wrong. I will create a new PR.