BigIp Software version

What version of Big IP software are you running this against ?? We are running version 13.x, have behavioral ddos enabled, but keeping getting the "variable not found" message when looking for the admdb.debug.traffic.sample variable "tmsh modify sys db admdb.debug.traffic.sample value enable"

What version of Big IP software are you running this against ?? We are running version 13.x, have behavioral ddos enabled, but keeping getting the "variable not found" message when looking for the admdb.debug.traffic.sample variable "tmsh modify sys db admdb.debug.traffic.sample value enable"

Hi, i have the same error!
Thank's
roberto

Hi @akruman
this is my bigip version

[root@bigip1:Active:Standalone] config # tmsh show sys version

Sys::Version
Main Package
  Product     BIG-IP
  Version     13.0.0
  Build       0.0.1645
  Edition     Final
  Date        Tue Jan 31 17:52:56 PST 2017

[root@bigip1:Active:Standalone] config # tmsh modify sys db admdb.debug.traffic.sample value enable
01020036:3: The requested database variable (admdb.debug.traffic.sample) was not found

Hi @chingru,
when using the app for older version, there is no instruction to enable the traffic sample.
please install this one:
https://github.com/f5devcentral/f5-bados-app/tree/evergreen
traffic sampling is not implemented in your version yet.


aditya chaki portfolio

@RITEKROUNAK kindly review my PR under hacktoberfest 2022.

Good work. I am merging your PR.
Do give us a star by hitting the star button of this repo!


Benchmark faster hash functions

We are interested in overall performance for index construction, i.e. both pure hashing speed and collisions amount are important. Note that there are at least 2 kinds of t1ha function: t1ha0 (the fastest) and t1ha1 (portable).
We should also measure t1ha2 and t1ha3 since they should have less collisions.
https://github.com/PositiveTechnologies/t1ha

These functions could be the fastest, too:

xxh3
wyhash

Double-check with https://rurban.github.io/smhasher/

Here are some hash functions that are worth benchmarking:

[x] CRC32 (Basecase)
[ ] t1ha0
[x] Google Highway -> https://github.com/ARK-Builders/arklib/tree/hash_highway
[x] xxHash  -> https://github.com/ARK-Builders/arklib/tree/hash_xxh3
[x] wyhash -> https://github.com/ARK-Builders/arklib/tree/hash_wyhash
[ ] Meow hash
[ ] aesni
[ ] FarmHash32

Note that "FarmHash" is not portable and is too machine-specific, as it operates differently on 64-bit and 32-bit systems.

From the preliminary results (very limited data) on these benchmarks:

Index construction (folder of just 2 files: 780KB and 126KB)
Plain hashing (1MB of data)

I could rank the functions like this:

ghxash
wyhash
t1ha0
farmhash
highway
xxh3
crc32

@tareknaser how could we approach more realistic benchmarking? Something like 10K of files from 100K to 2MB each? Does it make sense generate such a test dataset? I'll also run the benches against my own real data (using the branches you've created).

Benchmarks using this data:
$ ncdu
--- /mnt/data/test_all --------------------------------------------------------------------
    4.8 GiB [#############] /test2
    4.5 GiB [############ ] /test

$ find test | rg -v .ark | wc -l
12276

$ find test2 | rg -v .ark | wc -l
28

main branch:
Benchmarking index_build/index_build//mnt/data/test_all/: Collecting 100 samples in estimatindex_build/index_build//mnt/data/test_all/
                        time:   [5.2732 s 5.2812 s 5.2897 s]

Found 3 outliers among 100 measurements (3.00%)
  2 (2.00%) high mild
  1 (1.00%) high severe

Collisions: 0

hash_gxhash branch:
Gnuplot not found, using plotters backend
Benchmarking index_build/index_build//mnt/data/test_all/: Collecting 100 samples in estimatindex_build/index_build//mnt/data/test_all/
                        time:   [4.4865 s 4.4969 s 4.5073 s]

Collisions: 0

I'm a bit confused about these 2 points:

Indexing with gxhash is just 15% faster, more time spent on something else like putting into tree structure?
Zero collisions, this could be a bug somewhere...

Looks that we need profiles, too:

#81

Looking at the benchmark results, here's what I think:
For gxhash:

crc32 uses a smaller hash (u32) compared to gxhash (u64). This difference can slow down lookups in ResourceIndex.
Bigger hashes like u64 usually have fewer collisions, which is good. But getting zero collisions with gxhash seems strange, let's double-check that.

For blake3:

It's already slower than gxhash, as expected. Benchmarks online might not be helpful here since we do more than just hashing.
Using its larger hash ([u8; 32]) for lookups adds extra work.

We should think about the trade-off between fewer collisions and faster lookups when choosing hash sizes.
We can also consider other cryptographic hash functions and see how they compare to blake3.

how could we approach realistic benchmarking?

Our current benchmarks index the tests/ directory, which is a good starting point but isn't ideal for performance evaluations. In CI, we try to provide quick feedback on potential issues rather than comprehensive performance assessments because of resource limitations.
Profiling can help identify performance bottlenecks within arklib. Benchmarks tell us "how fast", profiling tells us "why".
However, if we opt for large datasets for benchmarks, we can store them separately from the project code on GitHub. Then, use tools like wget or  reqwest to fetch datasets during benchmark execution.

wyhash: 5.35 sec
t1ha0: 5.1 sec

@tareknaser

crc32 uses a smaller hash (u32) compared to gxhash (u64). This difference can slow down lookups in ResourceIndex

Do you think this could be the reason on 64-bit architecture?

Bigger hashes like u64 usually have fewer collisions, which is good. But getting zero collisions with gxhash seems strange, let's double-check that.

Totally. And CRC-32 has zero collisions, too. But if I remember correctly, for test_all/test folder I had something like at least 1 collision per 1,000 resources. I would expect around 10 collisions total for main branch. Probably it's worth to check indexing code and also fix this command (at the moment it seems to not print the collisions number).

Benchmarks online might not be helpful here since we do more than just hashing. Using its larger hash ([u8; 32]) for lookups adds extra work.

Agree. But the strange part here is that difference in hashing performance between CRC-32 and Blake-3 is the same as the difference in indexing performance...

We should think about the trade-off between fewer collisions and faster lookups when choosing hash sizes.

Agree.

We can also consider other cryptographic hash functions and see how they compare to blake3.

Do you think there are faster cryptographic functions? We could try, but let's first implement this for easier experimentation:

#75

Our current benchmarks index the tests/ directory, which is a good starting point but isn't ideal for performance evaluations. In CI, we try to provide quick feedback on potential issues rather than comprehensive performance assessments because of resource limitations.

That's all correct. I just think we need also some heavy automated indexing test which will be run only manually. We could also collect some huge dataset and store it in some cloud storage provider, but generating random data might be quicker for arbitrary person that download the dataset from the cloud. What do you think?

Do you think this could be the reason on 64-bit architecture?

I think it contributes, yes. But maybe not the sole reason.

but generating random data might be quicker for arbitrary person that download the dataset from the cloud. What do you think?

I think that generating random data would be more straightforward to implement and maintain. But using the same dataset is better for benchmarking as it provides a more accurate representation of real-world data.
Generating random data would be the better choice for now. we can always switch to a fixed dataset later.

Apparently, aHash is not supposed to be used in our case
AHash does not have a fixed standard for its output


Create CRC

Class Responsibility Collaborator (CRC) documentation.

Done. This document may change as we build the app.


Illegal instruction is not fixed

When running sudo howdy add or sudo howdy test the only output is Illegal instruction.

I've searched for similar issues already, and my issue has been reported, but closed without solution in current release:
#101
#330
Linux distribution (if applicable): openSUSE Leap 15.2
Howdy version (sudo howdy version): Howdy 2.6.1

I can't use the provided python3-dlib rpm. I've installed now the current release with pip3 install dlib.
First with pip3 install --user dlib to get a wheel.
Afterwards sudo pip3 install .cache/pip/wheels/bd/46/7c/d...ce/dlib-19.22.0-cp36-cp36m-linux_x86_64.whl and pip3 uninstall dlib.
Seems to work now. Maybe update your documentation and try to catch this error with a meaningful error message!

I'm guessing that it crashes Howdy on cv2 import, might not be a catchable error but i'll look into it

Hi,
I've got this same problem when sudo howdy -U myusername add
Please look straight into the camera
Illegal instruction
But the howdy test works perfectly though.
Ubuntu 22.04 and HP Pavilion dv3000.
Regards,
Jean-Claude

I've found some time to look into this...
dlib is using some CPU architecture instructionset features like SSE4 or AVX.
In precompiled binaries (on modern hardware) this defaults to enabled AVX instructions.
When running this dlib on older hardware these are illegal instructions for the CPU.
But when installing/compiling dlib on the local hardware with pip, cmake is detecting the correct available instructionset and uses right features for compiling dlib. So e.g. using SSE4 instead of AVX or disabling both and using slower generic machine instructions.
It is also possible to set this by hand:
https://github.com/davisking/dlib/blob/1bebccfb8728f6112d6142ba24f2dd65970ff6a2/setup.py#L20-L22
To exclude certain options in the cmake config use --no:
    for example:
    --no USE_AVX_INSTRUCTIONS: will set -DUSE_AVX_INSTRUCTIONS=no

In dlib is also a check for the instruction sets...
https://github.com/davisking/dlib/blob/1bebccfb8728f6112d6142ba24f2dd65970ff6a2/dlib/simd/simd_check.h#L153-L171
    inline void warn_about_unavailable_but_used_cpu_instructions()
    {
#if defined(DLIB_HAVE_AVX2)
        if (!cpu_has_avx2_instructions())
            std::cerr << "Dlib was compiled to use AVX2 instructions, but these aren't available on your machine." << std::endl;
#elif defined(DLIB_HAVE_AVX)
        if (!cpu_has_avx_instructions())
            std::cerr << "Dlib was compiled to use AVX instructions, but these aren't available on your machine." << std::endl;
#elif defined(DLIB_HAVE_SSE41)
        if (!cpu_has_sse41_instructions())
            std::cerr << "Dlib was compiled to use SSE41 instructions, but these aren't available on your machine." << std::endl;
#elif defined(DLIB_HAVE_SSE3)
        if (!cpu_has_sse3_instructions())
            std::cerr << "Dlib was compiled to use SSE3 instructions, but these aren't available on your machine." << std::endl;
#elif defined(DLIB_HAVE_SSE2)
        if (!cpu_has_sse2_instructions())
            std::cerr << "Dlib was compiled to use SSE2 instructions, but these aren't available on your machine." << std::endl;
#endif
    }

This gets called by the python module here:
https://github.com/davisking/dlib/blob/1bebccfb8728f6112d6142ba24f2dd65970ff6a2/tools/python/src/dlib.cpp#L42
I've opened https://github.com/davisking/dlib/issues/2675

Awesome work @kolbma! Hopefully the dlib people can look at it soon


Add optee-os, opted-client, tee-supplicant (untested rebase of PR #237613)

This is a DRAFT PR that is an untested rebase of PR #237613. It is solely for comparison and discussion purposes.
I am hoping to revive that PR, so any comments should probably be made there.

The conflicts have been resolved in PR #362293. Closing.


Selected object doesn't get exported when its parent is not selected

I work on a scene, and I wanted to export only a specific mesh from it for testing, so I selected the option selected objects in the exporter settings. I noticed that it produced a "corrupt" glb file, which is too small to be valid. The following errors are shown in the validator:

If I select all of the object's ancestors as well, it gets exported flawlessly. Here's the test scene, if anyone wants to try:
test.zip

I've seen this too.  And worse, if you place an object inside a collection, and use "only selected", the selected object won't export because it has a parent, namely the collection itself.

I looked into this. At the moment, the exporter starts with root objects and iterates over them filtering out the stuff that doesn't match selection filters.  So if a root object isn't selected, then none of its children will ever be evaluated even if they themselves are selected.
This is also related to my 'Export active collection' issue (https://github.com/KhronosGroup/glTF-Blender-IO/issues/192)  which I had to implement in a hacky way.
Basically I think the code needs rearchitecting so that it doesn't start with root nodes and filter out the stuff that's not needed.

If 'Selected objects' is checked, then it should retrieve an array of all selected objects in the view.
If 'Active collection' is checked then it should retrieve all objects in the active collection.  This is done with bpy.context.view_layer.active_layer_collection.collection.all_objects

The downside is that parent-child relationships will need to be rebuilt - because now we have a flat array of objects instead of iterating up the hierarchy.
This is the way the FBX exporter does it, and it seems to be quite well written for 2.80
https://developer.blender.org/diffusion/BA/browse/master/io_scene_fbx/export_fbx_bin.py$3046
I'm happy to help with this but I'm going to need some guidance because this is my first venture into Python and Blender internals.

export all objects that are both selected and visible (even if parents are not selected and/or not visible).

I assume this means that if a parent has a child that is selected or visible, the parent is also exported?

I assume this means that if a parent has a child that is selected or visible, the parent is also exported?

I think such objects should become children of the glTF scene.
There's a more complex possibility, where a grandparent and grandchild are both selected for export, but there's a de-selected object in between.  Not sure what to do with the grandchild there.

I think the hidden parents can be skipped, and the selected children should become children of the glTF scene.

We'd have to resolve world transforms differently, and that's going to give very unpredictable results with animation. I'd prefer to say that inclusion of a child implies inclusion of its parents. Maybe if the parent is a mesh, camera, or light, the parent node is written but the referenced mesh/camera/light is not.

I'm having some issues filtering my export in a good way, i'm not really happy with either the export selected, export visible or export layers solutions. I have a pipeline that exports my scene every time i save the blend file. I save often and want quick feedback on the changes i've made so i don't want to configure the file for export every time i save and i don't want to include all objects in the export.
my options now is to keep all exportable assets in one layer or to make a script select a predefined subset of my scene. The second option however seems to also export all scenes which imo should be its own setting.
With my use case i would like to have the option to only export "renderable" assets. To me it seems like a good analogy that you only export the visible in render rather than whats visible in the viewport. That way the scene can contain variants and references that should be visible but the output is only what would also be visible in the final render.
in short: filter on the "hide_render" property of collections and objects.

Note that there was support for optionally only exporting from layer 0, but it was removed in 1ea67904175854feeebd70cec20d7222f8b4aa97 + 9520626f856ae7390f644c5b6908bb88a760c6f6 — not sure why. Optionally only exporting things with !hide_render seems like a good idea to me and should be simple — not sure what others think. Either way still runs into the issue of what to do when a parent is filtered out but the children aren't.

Either way still runs into the issue of what to do when a parent is filtered out but the children aren't.

I'd suggest replacing the parent with an empty Object3D with the parent name and transformation matrix.

OK, just wanted to post a bug report, too.
Makes it quite hard to reliably export specific objects, especially as in the current state of Blender 2.80's outliner set to "View Layer" it's impossible to see if an object has parents or not.

Fixed in #1126 (for Blender 2.91)


Failed to set LoaderSystemToken EFI variable: Invalid argument

Describe the bug
If I do nixos-rebuild switch or nixos-rebuilt boot, the build succeeds and I change generations, but in either case on reboot, my changes are gone. This is a continuation of this discourse thread.
To Reproduce
Steps to reproduce the behavior:
0. See that zsh is not in /etc/shells

nixos-rebuild switch
verify that zsh is now in /etc/shells
reboot
see that zsh is now gone from /etc/shells

Expected behavior
The generation should persist past reboot.
Additional context
From this comment, I thought it might be worth trying sudo nixos-rebuild boot --install-bootloader which gives the following error:
Created "/boot/EFI/Linux".
Copied "/nix/store/qjnhav18gi6ry63cbkni4fh36kq13v32-systemd-243/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/nix/store/qjnhav18gi6ry63cbkni4fh36kq13v32-systemd-243/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".
Created "/boot/c34158abdaad4e9e9f785ef7ce6a84d1".
Random seed file /boot/loader/random-seed successfully written (512 bytes).
Failed to set LoaderSystemToken EFI variable: Invalid argument
Traceback (most recent call last):
  File "/nix/store/bmb1711cnkd2m8pzbgwgib70075jycjz-systemd-boot-builder.py", line 240, in <module>
    main()
  File "/nix/store/bmb1711cnkd2m8pzbgwgib70075jycjz-systemd-boot-builder.py", line 197, in main
    subprocess.check_call(["/nix/store/qjnhav18gi6ry63cbkni4fh36kq13v32-systemd-243/bin/bootctl", "--path=/boot", "install"])
  File "/nix/store/drr8qcgiccfc5by09r5zc30flgwh1mbx-python3-3.7.5/lib/python3.7/subprocess.py", line 363, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/nix/store/qjnhav18gi6ry63cbkni4fh36kq13v32-systemd-243/bin/bootctl', '--path=/boot', 'install']' returned non-zero exit status 1.

I found this bug report from an arch user, but no resolution. Not sure if related to my situation.
There's plenty of space on my disks:
> df -h
devtmpfs                  6.3G     0  6.3G   0% /dev
tmpfs                      63G     0   63G   0% /dev/shm
tmpfs                      32G  9.8M   32G   1% /run
tmpfs                      63G  624K   63G   1% /run/wrappers
/dev/disk/by-label/nixos  203G  119G   75G  62% /
tmpfs                      63G     0   63G   0% /sys/fs/cgroup
/dev/sdb1                 916G  520G  350G  60% /data
/dev/sda2                 511M  200M  312M  40% /boot
tmpfs                      13G     0   13G   0% /run/user/175
tmpfs                      13G   12K   13G   1% /run/user/1000

Metadata
I am building against 3140fa89c51233397f496f49014f6b23216667c2 (Dec 5 unstable)

Is this problem isolated to changing shells? Your issue's title suggests that nixos-rebuild switch is not persisting changes when rebooting, but your examples are only about changing the shell. What about other changes? Do they not persist as well?

No, generations are not changing in grub. Originally I didn’t notice as I use home-manager for most things. I’ve done “nix-collect-garbage -d” and “sudo nix-collect-garbage -d”, yet 53 generations still show in grub. All give a kernel panic as they’ve been deleted now so key files are missing. I do have one generation tagged using -p that can still boot.
My hardware-configuration.nix is nearly identical to another computer that works fine and has /boot specified by label. This seems like an EFI problem per the error above about installing the boot loader

In my experience, when I run
`sudo nix-collect-garbage -d` the deleted generations remain in the bootloader. Running `nixos-rebuild boot` cleans them up.
It seems like you're trying to change bootloaders. Hmm...
I once got that same bootctl error when installing NixOS. I worked around it my running the command manually. See if that works.
-------- Original Message --------
On Dec 11, 2019, 11:17 AM, tbenst <<EMAIL_ADDRESS>wrote:

No, generations are not changing in grub. Originally I didn’t notice as I use home-manager for most things. I’ve done “nix-collect-garbage -d” and “sudo nix-collect-garbage -d”, yet 53 generations still show in grub. All give a kernel panic as they’ve been deleted now so key files are missing. I do have one generation tagged using -p that can still boot.
My hardware-configuration.nix is nearly identical to another computer that works fine and has /boot specified by label. This seems like an EFI problem per the error above about installing the boot loader
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm now reinstalling NixOS from scratch on this computer.
$ sudo nixos-install -j 12
building the configuration in /mnt/etc/nixos/configuration.nix...
[145 built]
copying channel...
installing the boot loader...
setting up /etc...
Initializing machine ID from random generator.
Created "/boot/EFI".
Created "/boot/EFI/systemd".
Created "/boot/EFI/BOOT".
Created "/boot/loader".
Created "/boot/loader/entries".
Created "/boot/EFI/Linux".
Copied "/nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/BOOTX64.EFI".
Created "/boot/8e8e53b83f1b4bb290731b2563c95389".
Random seed file /boot/loader/random-seed successfully written (512 bytes).
Failed to set LoaderSystemToken EFI variable: Invalid argument
Traceback (most recent call last):
  File "/nix/store/6bqqzi5sqgi7djfrhmb437a0gv7xf7x5-systemd-boot-builder.py", line 240, in <module>
    main()
  File "/nix/store/6bqqzi5sqgi7djfrhmb437a0gv7xf7x5-systemd-boot-builder.py", line 197, in main
    subprocess.check_call(["/nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/bin/bootctl", "--path=/boot", "install"])
  File "/nix/store/4c3z5r6yxsf2cxwwyazhdn92xixn4j5b-python3-3.7.5/lib/python3.7/subprocess.py", line 363, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/bin/bootctl', '--path=/boot', 'install']' returned non-zero exit status 1.

So tried manual:
$ sudo /nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/bin/bootctl --path=/mnt/boot install
Copied "/nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/lib/systemd/boot/efi/systemd-bootx64.efi" to "/mnt/boot/EFI/systemd/systemd-bootx64.efi".
Copied "/nix/store/v1fq42g0vlv7sh3jpfk4ga3lqfwdkg3b-systemd-243.3/lib/systemd/boot/efi/systemd-bootx64.efi" to "/mnt/boot/EFI/BOOT/BOOTX64.EFI".
Created "/mnt/boot/1d79bdb024a04e0c93db8dbba5925210".
Random seed file /mnt/boot/loader/random-seed successfully written (512 bytes).
Failed to test system token validity: No data available

I'll reboot and report back if this worked.

This did not work. What did, however, was reformatting the /boot partition and ensuring boot.loader.efi.canTouchEfiVariables = false; is set. I guess it's a firmware issue on this computer. EFI boot is now working properly!

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/installer-fails/22653/2


Add Water Survey Canada Data to CDOGS Template - WALLY (Step 2 for #707)

Describe the task
Add Water Survey Canada (WSC) data to CDOGS template. (Screenshot below).
Purpose
This is the second step needed to complete ticket #707.
Acceptance Criteria

[ ] Understand how the EFN data is brought into the front end
[ ] Compare how CDOGS is exporting the EFN data
[ ] Set up function that adds WSC data to CDOGS template

Additional context

SAMPLE REPORTS WITH WSC DATA
2021-10-06_WALLY_Bertrand.xlsx
2021-10-07_WALLY_Fishtrap_Creek.xlsx
<EMAIL_ADDRESS>2022-02-01_WALLY_Fitzsimmons_Creek.xlsx
SAMPLE REPORTS WITH NO WSC DATA FOR COMPARISON
2021-10-07_WALLY_Frosst_Creek.xlsx
2021-11-10_WALLY_Little_Campbell_River.xlsx
2022-01-07_WALLY_Whistler_Creek.xlsx
2022-06-16_Duncan_Slough.xlsx

Awaiting the template example from WALLY Service Owner to change CDOGS export before moving forward.

July 21 - Requested sample document of what the report looks like after WALLY user (Jacquelyn) manually adds the Water Survey Canada data. CC'd in Sustainment Team mailbox.

Requested reports provided and have been attached to this ticket.

Is it possible to get a current report? The provided attachments are 18 months old so data does not match what we are seeing currently in the app.


Navigator: Add optional navigationBarPosition prop

When passing a custom navigationBar, like ToolbarAndroid, we need a way to ensure the toolbar is rendered at the top of the page. This makes sure we don't need any CSS tricks or hacks to render it.
Test plan (required)
Default is still bottom, which means no tests should be affected.
It's a simple change, navigationBar is rendered before the View in Navigator, to ensure it shows up at the top.

@arvindch updated the pull request - view changes

@arvindch updated the pull request - view changes

Instead of doing this, you can use absolute positioning to make sure the header is displayed above the navigator. Set the height, and, {position: 'absolute', top: 0, left: 0, right: 0}

@ericvicenti - Yes, I've tried that. It results in the navbar overlapping content at the top.
Seeing as how react-native is supposed to be cross-platform, and Android uses navbar at the top, shouldn't this be an obvious feature? I don't the the code changes I proposed are intrusive or major in any way, either.

Please reopen this. It seems un-intuitive to abstract away the physical positioning of react components. I don't necessarily like the 'binary' idea of providing either 'top' or 'bottom' to fix this conundrum, so I've placed my suggestion below.
My suggestion is to instead create an alternate 'higher-level' render prop to the  component.
For example:

<Navigator
   renderScene={(route, navigator) => <Text>Test</Text>}
   navigationBar={<MyCustomNavbar />}
   renderNavigatorScene={(Navbar, Scene) => {
       return (
           <View>
              {/* Customize component order and insert your own additional components at this level. */}
              <Navbar /> {/* Component with injected navigator, navState props */}
              <Scene /> {/* Component with injected route, navigator props */}
           </View>
       )
   }}
/>


Double delimiter when no optional component

Tool version
3.1.1
Describe the bug
When not populating an optional component, two delimiters are present in the generated name instead of one.
To Reproduce
Steps to reproduce the behavior:
I have two custom components added to my name.

Parent Resource (Optional) - Open ended text

Resource Name - Open ended text

Go to Generate

Choose item and populate all fields, except optional.

Click Generate

See that output has two delimiters where the optional component would be, had it been populated.

Expected behavior
I would expect the system to recognize I did not populate the optional field, and only insert one delimiter.
Screenshots
If applicable, add screenshots to help explain your problem.

Installation Method
FTP upload to Azure Web app

Hi @koalajama,
Thank you for your feedback. In looking at the screenshot, it seems as if your "Parent Resource" has a blank value (which I'm not sure how that is even possible. Because of that, the tool is interpreting the "blank" in the name as a valid value, therefore it is wrapping it with the delimiter. When entering a component option, a name/short is required, so I'm not sure how it allowed that as an option.
If possible, can you export your "Parent Resource" config and provide it here?  Be sure to remove any sensitive information before posting.
Thank you!
-Bryan

CORRECTION - I see that the field is an "Open text" type, which explains the blank value. I will continue to research.
-Bryan

OK, I found the issue in the Generate page logic. This will be fixed in the next release.

Bryan


Fix loading of 4-bit .ico files

biBitCount is used on line 761 to infer the default palette size if biClrUsed is zero, but is set to 8 here for no apparent reason. Of course a 16-color image doesn't have a 256-color palette. It seems the bug has existed forever.
Example 4-bit .ico file that fails to load before but loads with this patch:

PR'd to release-2.6.x branch out of optimism that this fix could make it into a future 2.x release; I don't know your backport policy. Can rebase if needed.

Please rebase it to main, and we'll backport to the release branch.
Thanks!

Merged, thanks!


Add jitter for constant backoff

As you're answering questions, I've created this small PR for the jitter requirement.
Currently, it's adding a random time (<= MAX) to the given backoff time.
We can discuss if you want a different way for this.

cc @rShetty

@pravj Do you also want to add this jitter functionality for exponential backoff ?

Also we need to the update the documentation of this change, thanks

@rShetty @pravj  raised the PR for the Jitter functionality in the exponential backoff.

@pravj @timusg Merging this. Will be adding documentation separately


Software Engineering: Client <---> RPi connection slowdowns

[ ] Create communication tables in database
[ ] Create routes that allow access to database
[ ] Test routes to ensure database operations are sound

Some new way will need to be discovered about connecting the client directly to RPi via server without saving messages onto the server so that client and RPi can communicate efficiently. Searching for alternatives.

Searching how multiplayer web games work on Google revealed something called WebSockets. This type of connection allows direct contact to server without the HTTP bulkhead.

WebSockets are available for browser JavaScript and for server-side Node.js. However, keep in mind that libraries are slightly different for both. Currently writing client-side websocket code.

Just like HTTP, WebSockets are insecure as well. The server will need to validate the ATC command received by the client.

To keep app simple, security will be maintained by limiting distribution of the website to others. People will be verified personally to ensure app is not abused in amy way.


feat(cli-plugin-vitest): add new plugin to generate project with vitest

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

v5.1.0
GitHub release

Your semantic-release bot :package::rocket:


github, cairo, version: Minor fixes

This PR contains 3 minor fixes which I faced during the configuration of polybar.

Thanks


Better Documentation as a whole package for newcomers

I am a newbie in F# with strong Python background, trying to do some real-world projects to get a good feel of F#.
When I started learning F#, it wasn't a smooth experience. The reason I think are the scattered learning resources and there was no clear path to learn all the basic language constructs.
I have tried some sites suggested in https://fsharp.org/learn.html and they are cluttered and assume that the learner is from C# ecosystem. The books are outdated(using VS and not .NET Core). Other modern languages have great documentation in its main website itself. It gears up the great learning feel.
For example

Rust
ReasonML
Nim
& even Python

everything in one place up-to-date and serves as a reference whenever needed during the initial phases of learning curve.
Here I really like the docs of ReasonML which clearly have organized all the topics. I think many people have felt the same and off-putting to learn F#.
Is it possible to clearup the current documentation of the site? I will be more than happy to work on new pages and would translate from ReasonML for F#. But I am no expert in F# as I mentioned before.

Thanks for the feedback! The fsharp.org site is actually the site of the F# Software Foundation, and although it's currently undergoing a redesign, it is not something we at Microsoft control or produce content for.
Documentation on getting started with F# is available officially here: https://docs.microsoft.com/en-us/dotnet/fsharp/
Those docs are all linked to the backing GitHub repository, so if you find specific issues or have suggestions the feedback tool will create an issue for you.

Thanks for the clarification. I am recreating the issue there.


Added CONDUCT.md (fixes #3)

Hey thanks for this project. Please consider this PR.

Thanks for the contribution! It may be a little while before I can review it, but it's on my radar and I won't forget about it.


Unable to get the desired output from advanced-bot-framework-composer-example1

Hello,
While trying to perform the exercise in my own environment. I'm unable to get a proper response from the bot. I instead get the following code instead of the adaptive card :

Note that I am using the free trial of the Power virtual agents and the latest Bot framework composer app.
I double-checked the code that is being pasted under the Bot-responses section. But it's still the same. Am I missing something here? Please help.
Thanks and Regards.

Hi @junnhssn, thanks for your report!
I think the issue may be that you've placed the response in the response editor, instead of the code editor.
❌Response editor:

✔Code editor:

The instructions don't make this super obvious, so I'll look into improving that.
Let me know if this solves your problem!

Hey, thanks for the quick response.  The issue was indeed the one you have mentioned above. I was able to get it working by placing the code in code editor. I'll be closing the issue now, thanks again.


[RFC] lib: libspdm_rsp_capabilities: fixup spec conformance

Overview [RFC]
When chunking is not supported, MaxSPDMmsgSize shall equal DataTransferSize in a GET_CAPABILITIES request. However, this is only specified in the SPDM 1.3 spec,  but libspdm enforces it for >= 1.2 spec.
This change
A requester implementing 1.2 >= version < 1.3 may not conform to this as it is not specified in the 1.2 or 1.2.1 specification for a GET_CAPABILITIES request. So only enforce this if the version used is 1.3.
Context
I was testing the ongoing effort for the Linux Kernel SPDM requester implementation. When it's sending a get_capabilities request using 1.2, without chunking, the kernel implementation does not set MaxSPDMmsgSize=DataTransferSize. So such a request would be responded to with an SPDM_ERROR (0x7F) by a libspdm based responder.

SpdmSendResponse[0]: msg SPDM_ERROR(0x7f), size (0x4):
0000: 12 7f 01 00
Platform port Transmit command: 00 00 00 01
Platform port Transmit transport_type: 00 00 00 02
Platform port Transmit size: 00 00 00 0c
Platform port Transmit buffer:
    01 00 01 00 03 00 00 00 12 7f 01 00

TODO
Is there a more appropriate solution to this?

If an endpoint does not support chunking, and it sets MaxSPDMmsgSize > DataTransferSize, then what is it conveying to the peer endpoint? Presumably if chunking is not supported then, from the peer's perspective, there is only one buffer whose size is MaxSPDMmsgSize == DataTransferSize.

If an endpoint does not support chunking, and it sets MaxSPDMmsgSize > DataTransferSize, then what is it conveying to the peer endpoint? Presumably if chunking is not supported then, from the peer's perspective, there is only one buffer whose size is MaxSPDMmsgSize == DataTransferSize.

This makes sense and although I agree,  does it need to be enforced with an error if the doesn't explicitly state as such? It's possible that a non-libspdm responder doesn't follow this given that it's not a part of the spec right?

We could have a flag, LIBSPDM_DISABLE_STRICT_CHECKS, that disables checks that are inferred from, but not explicitly stated in the specification. However I would consider endpoints that violate those checks to be buggy.
Note that (CHUNK_CAP == 0) -> (MaxSPDMmsgSize == DataTransferSize) as well as clarifications around ResponseTooLarge will be in the 1.2.2 specification.

We could have a flag, LIBSPDM_DISABLE_STRICT_CHECKS, that disables checks that are inferred from, but not explicitly stated in the specification. However I would consider endpoints that violate those checks to be buggy.
Note that (CHUNK_CAP == 0) -> (MaxSPDMmsgSize == DataTransferSize) as well as clarifications around ResponseTooLarge will be in the 1.2.2 specification.

Great, I think this particular case we can wait for the 1.2.2 spec and just patch the kernel implementation.
As far as LIBSPDM_DISABLE_STRICT_CHECKS, sounds like a good idea also. Perhaps worth adding if we run into more cases like this... not sure if there already are many other places where things are inferred...are there?

not sure if there already are many other places where things are inferred...are there?

Some of the capabilities checks are inferred from the specification. But again, if an endpoint violates them then it's buggy / misconfigured.

not sure if there already are many other places where things are inferred...are there?

Some of the capabilities checks are inferred from the specification. But again, if an endpoint violates them then it's buggy / misconfigured.

I see, thanks!


Create MAPL.profiler logger

Description

This PR creates a new MAPL.profiler logger and moves some current writes to use logger:

Model throughput
Per-component timers
Global timers

For GEOS, this will create pretty much the same log output as long as:
   MAPL.profiler:
       handlers: [console_plain]
       propagate: FALSE
       level: WARNING
       root_level: INFO

is in logging.yaml. As such, an PR will be needed for GEOSgcm_App (see https://github.com/GEOS-ESM/GEOSgcm_App/pull/391)
Related Issue

Closes #1930
Motivation and Context

This will allow users to have most of MAPL at WARNING LEVEL but have the timers always output.
How Has This Been Tested?

Tested with GEOS. Zero-diff.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Trivial change (affects only documentation or cleanup)

Checklist:

[x] I have tested this change with a run of GEOSgcm (if non-trivial)
[x] I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
[x] I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

@tclune Please take a look at this. It was a pretty one-for-one swap of writes to logger. But perhaps I'm now violating how logger should be used with things like logger-on-one-process:
      if (my_rank == 0) then
         report_lines = reporter%generate_report(t_p)
         lgr => logging%get_logger('MAPL.profiler')
         call lgr%info('Report on process: %i0', my_rank)
         do i = 1, size(report_lines)
            call lgr%info('%a', report_lines(i))
         end do
      end if

Looks good to me! Thanks for putting this together.


Make lookupSandboxID() reliable

it is supposed to be called after lookupContainerID()
but the latter is not guaranteed to succeed and in
case of connection error will return what was passed
to it.
So in order to be able to operate with both long and short
container ids in case of lookupContainerID() failure,
always search by partial-container-id

Signed-off-by: Alessandro Boch<EMAIL_ADDRESS>

LGTM

LGTM


Lightbox on iOS fails to show uploaded images

This is similar to #2618 , but affects an additional part of the UI, and only on iOS.
To reproduce:

On iOS, log into an org on zulipchat.com, or possibly any other server running a recent release and on Xenial. (Not chat.zulip.org, which is on Trusty.)
Find a conversation with a user-uploaded image in it. (Or just upload one.)
Tap the image, bringing up the lightbox.
The image doesn't appear. We just have the lightbox's black background, and its top and bottom bars.

I just tested this with 13.4.88 on iOS 10. With 13.5.89 (which differs only in one unrelated bugfix) on Android, it works fine.
Given that this happens on a Xenial but not a Trusty server, it's almost certainly related to our feature to require authentication to see uploaded files (which doesn't work on Trusty and is disabled there.) We're either not passing the authentication info, or not following the redirect, or both.

This problem is still present in the latest iOS 12.
Unable to enlarge images from the chat is a major issue for our organization. Any guess when this could be fixed?

I'm claiming this.
(@zulipbot is disabled for this repository at the moment)

Cross-referencing here what we learned in d873e22fc, which fixed this: the underlying issue here was
https://github.com/alwx/react-native-photo-view/issues/101 , in the library we use for displaying the image. It was fixed upstream in April, but upstream hasn't made a release since last year; we fixed by upgrading to the version from Git that has the fix.

Following up for @a-b and anyone else watching this thread: the fix went out to all users a few days ago in 17.1.98.


Code for pre-training ToD-BERT

Hi, how can I pre-train ToD-BERT by myself? What are the hyperparameters? How to reproduce the evaluation results?
Thanks!

@zqwerty Please check the update repo.


Rename the Identity Client interface

What would you like to be added:
We should rename the identity.Client interface to something like IdentityClient
Why is this needed:
This will keep our client interfaces consistent like the ComputeClient

Starting to work on this and it looks like we should change all the other clients to be more like identity.Client that seems like the more idomatic go way (Name starts with the package name).
https://go.dev/blog/package-names

Avoid repetition. Since client code uses the package name as a prefix when referring to the package contents, the names for those contents need not repeat the package name. The HTTP server provided by the http package is called Server, not HTTPServer. Client code refers to this type as http.Server, so there is no ambiguity.


[QUESTION] Height and Width

Hello, is there a way to adjust the width so that the gray does not appear? or get the height and width of the original image from cropper.

thanks,
I can't get the image to cover the entire width without showing the gray on the sides.

Thanks


k is not defined installing plugins

Problem:
I get a k is not defined error when attempting to add a plugin.
Steps to reproduce:

run yarn global add renative@latest
run rnv app create
I used "test" for name and picked ios and android as the targets
cd test/ (the name of the app)
run rnv plugin add
I tried 20 and 22, both throw the error

Error:
Installing:
- react-native-svg v(9.4.0)

readline.js:1020
            throw err;
            ^

ReferenceError: k is not defined
    at /Users/n0148094/.config/yarn/global/node_modules/renative/rnv-cli/dist/cli/plugin.js:1:3554

Versions
Node: v8.12.0
rnv: 0.22.0-alpha.4

@Kikketer thx for the bug report! fixed in 0.22.0-alpha.5


Power failure = all programmings including lights from homebridge-hue are gone

So apart from the other open topic I just had a power failure in my house which triggered the general fuse of the house. Nothing serious, turned it back on but then horror: all my automations in homekit were gone, all my 20 wireless switches with multiple buttons each programmed with a function: gone. All my room allocations of every light (also about 20 of them): gone. Multiple hours of work just GONE.. Is this normal for homekit just to erase everything the moment the power goes out?
Everything which was added via MQTT is still there so it is an issue with homebridge-hue in specific.. This must be a mistake from my part on the programation or settings or whatever right? I can't be losing everything the moment the power goes out? The moment the power went back on, all devices showed back up but all in the same room and all linked programations errased... This is going to take me half a day at least to get everything back how it was.. How can I prevent this in the future from happening again?

Extra: Everthing from the plugin Homebridge Evohome had the same problem (heaters etc)

This is caused by the old plugin design (using static platform accessories) that Homebridge Hue is still using (see #4), in combination with a bug in deCONZ, causing it to start without exposing the lights.  Create a lightest resourcelink to workaround this issue.  See https://github.com/ebaauw/homebridge-hue/issues/471.

This is caused by the old plugin design (using static platform accessories) that Homebridge Hue is still using (see #4), in combination with a bug in deCONZ, causing it to start without exposing the lights.  Create a lightest resourcelink to workaround this issue.  See https://github.com/ebaauw/homebridge-hue/issues/471.

Thanks for the reply, but the ph lightlist thing is something I already did. I used to have the same problem when just rebooting the device, which I no longer have since I did the lightlist. But now with the general power failure, it happened. But all devices came back in HomeKit after the reboot when the power came back with their names and everything, they just were no longer shown in the right room and lost all automations linked to it. Same with motion sensors, all automations linked to motion sensors are gone..
I'm considering buying a UPS for the RPI

But now with the general power failure, it happened. But all devices came back in HomeKit after the reboot when the power came back with their names and everything, they just were no longer shown in the right room and lost all automations linked to it. Same with motion sensors, all automations linked to motion sensors are gone..

That means that Homebridge was started at least once without exposing the accessories.  How many bridges/gateways to you have?  Does Homebridge Hue discover these, or did you specify them under hosts in config.json?

I'm considering buying a UPS for the RPI

Checkout: https://github.com/ebaauw/homebridge-rpi/wiki/Raspberry-Pi-UPS

What do you mean by bridges/gateways?

How many Hue bridges and/or deCONZ gateways do you expose using Homebridge Hue?

Again I'm not sure what you mean by a bridge? Is the conbee 2 stick considered a bridge? I don't know the terminology. In that case just 1, everything is connected to the conbee 2. I do have about 10 wired Aqara light switches that act as some kind of Zigbee bridge but I'm not sure that's what you are referring to

https://www.philips-hue.com/en-us/starter-kits
Do you specify the deCONZ gateway under hosts, or does Homebridge Hue discover it?  Best to specify it under hosts, so Homebridge Hue skips discovery, and delays Homebridge startup until the gateway has been found.
It's a bit suspicious that you see the same for the other plugin.  Also, I've never seen issues with sensors not being exposed (deCONZ restores them differently from lights).  Could also be caused some sort of Homebridge reset (maybe lost the IdentifierCache in persist directory?).

https://www.philips-hue.com/en-us/starter-kits
Do you specify the deCONZ gateway under hosts, or does Homebridge Hue discover it? Best to specify it under hosts, so Homebridge Hue skips discovery, and delays Homebridge startup until the gateway has been found.
It's a bit suspicious that you see the same for the other plugin. Also, I've never seen issues with sensors not being exposed (deCONZ restores them differently from lights). Could also be caused some sort of Homebridge reset (maybe lost the IdentifierCache in persist directory?).

Sorry, I was away for the weekend. So I have no bridges other than the Conbee2 stick.
Regarding this question: "Do you specify the deCONZ gateway under hosts, or does Homebridge Hue discover it? Best to specify it under hosts, so Homebridge Hue skips discovery, and delays Homebridge startup until the gateway has been found."
Honestly, I have no idea, I just followed standard setup procedure so I'm not sure if it is under "hosts", I have no idea how to check it.. I just installed everything needed as per instructions, linking all the devices happens through phoscon in a web browser, after restarting homebridge, the devices show up in homekit.. That's all I know. I do see a device in homekit called "phoscon-GW", not sure if that answers your question in any way.
Regarding your second question about the identifiercashe: I have a feeling I'm not much of a help again since I have no clue what you are talking about.
It is clear that the whole conbee2/phoscon is nowhere near a good user friendly solution since half off the stuff you are asking about is something I can't answer. I'm not sure how I should proceed from here to be honest. It works wonderfully when in works, but once it doesn't, I lose half a day or longer to reset everything with constant concern when it will happen again...

As I mentioned above, hosts is a key in config.json, the config file for Homebridge.  The IdentifierCache is created by Homebridge.  Neither have anything to do with deCONZ.
Bottom line: somehow Homebridge was started without exposing your devices, causing HomeKit to delete them.  I have no clue how this happened and without proper logs, there’s no way for me to find out.  This should be prevented by using the lightlist resourcelink and by specifying the gateway under hosts in config.json.
After a restart Homebridge once again exposes your devices, but HomeKit sees them as new devices, having lost any associations with HomeKit rooms, groups, scenes, and automations.

I've had two or three instances over the last year, @ebaauw, where following a power failure homebridge hue has come up and I've lost all of my device configurations from HomeKit. This happened to me again today. Note that the pi itself did not go down as it's connected to a ups, but due to whatever else is happening out on the network, it works itself into such a state that I chose to restart HomeBridge. In doing so, homebridge-hue didn't correctly (??) initialize to deConz, and ended up letting home bridge start even though the lightlist wasn't found.
Needless to say, I would be very excited if homebridge-hue were made to support dynamic accessories. But since that doesn't seem to be happening very fast, I wonder if it would help to try to dissect the logs I have in order to perhaps put more bandaids on the current status quo to prevent this situation. I can post saved logs from homebridge that show some of what happened. Would you like me to add to this issue, or create a new one?
Here's some of the log that seems relevant. Note that I have a conbee ii; it's not listed in hosts. It does seem to be recognized here, but from this point on, until homebridge is restarted, we just get lots of errors.
Thanks for any suggestions and insights!
`[10/25/2020, 12:01:06 PM] [Hue] no bridges or gateways found - retrying in 30 seconds
[10/25/2020, 12:01:19 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:01:36 PM] [Hue] searching bridges and gateways
[10/25/2020, 12:01:39 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:01:41 PM] [Hue] Phoscon-GW: dresden elektronik deCONZ gateway v2.5.86, api v1.16.0
[10/25/2020, 12:01:41 PM] [Hue] Phoscon-GW: warning: not using recommended deCONZ gateway version 2.5.84
[10/25/2020, 12:01:41 PM] [Hue] Philips hue: Philips BSB002 bridge v1941056000, api v1.41.0
[10/25/2020, 12:01:41 PM] [Hue] Phoscon-GW: /resourcelinks/1: /lights/1: not available
[10/25/2020, 12:01:41 PM] [Hue] Phoscon-GW: gateway not yet initialised - wait 1 minute
[10/25/2020, 12:01:41 PM] [Hue] Philips hue: 2 accessories
[10/25/2020, 12:01:59 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:02:19 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:02:39 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:02:41 PM] [Hue] Phoscon-GW: /resourcelinks/1: /lights/1: not available
[10/25/2020, 12:02:41 PM] [Hue] Phoscon-GW: gateway not yet initialised - wait 1 minute
[10/25/2020, 12:02:59 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:03:19 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:03:39 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/25/2020, 12:03:44 PM] [Hue] Phoscon-GW: gateway request 5: get /
[10/25/2020, 12:03:44 PM] [Hue] Phoscon-GW: gateway communication error: <IP_ADDRESS>:80: cannot connect: EHOSTUNREACH
[10/25/2020, 12:03:44 PM] [Hue] Phoscon-GW: <IP_ADDRESS>:80: cannot connect: EHOSTUNREACH
[10/25/2020, 12:03:44 PM] [Hue] Phoscon-GW: 1 accessories
[10/25/2020, 12:03:44 PM] [Hue] masked debug info dumped to /var/lib/homebridge/homebridge-hue.json.gz
[10/25/2020, 12:03:44 PM] Initializing platform accessory 'Phoscon-GW'...
[10/25/2020, 12:03:44 PM] [Hue] Phoscon-GW: 2 services
[10/25/2020, 12:03:44 PM] Initializing platform accessory 'Philips hue'...
[10/25/2020, 12:03:44 PM] [Hue] Philips hue: 2 services
[10/25/2020, 12:03:44 PM] Initializing platform accessory 'Daylight'...
Setup Payload:
X-HM://0024P8OBMCO39
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ XXX-XX-XXX  │
└────────────┘

[10/25/2020, 12:03:45 PM] Homebridge is running on port 51426.
[10/25/2020, 12:03:45 PM] [Hue] heartbeat 0, drift 396
[10/25/2020, 12:03:47 PM] [Hue] heartbeat 2, drift 297
[10/25/2020, 12:03:49 PM] [Hue] hue: bridge request 3: get /sensors
[10/25/2020, 12:03:49 PM] [Hue] hue: bridge communication error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:03:49 PM] [Hue] Philips hue: heartbeat error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:04:18 PM] [Hue] hue: bridge request 4: get /sensors
[10/25/2020, 12:04:18 PM] [Hue] hue: bridge communication error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:04:18 PM] [Hue] Philips hue: heartbeat error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:04:48 PM] [Hue] hue: bridge request 5: get /sensors
[10/25/2020, 12:04:48 PM] [Hue] hue: bridge communication error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:04:48 PM] [Hue] Philips hue: heartbeat error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:05:18 PM] [Hue] hue: bridge request 6: get /sensors
[10/25/2020, 12:05:18 PM] [Hue] hue: bridge communication error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:05:18 PM] [Hue] Philips hue: heartbeat error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:05:48 PM] [Hue] hue: bridge request 7: get /sensors
[10/25/2020, 12:05:48 PM] [Hue] hue: bridge communication error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH
[10/25/2020, 12:05:48 PM] [Hue] Philips hue: heartbeat error: <IP_ADDRESS>:443: cannot connect: EHOSTUNREACH`

From what I can tell from this log, you have no devices on your Hue bridge.  Homebridge Hue is waiting for deCONZ to expose the lights, but the communication with deCONZ breaks during that time.  By the looks of it, the error causes the wait loop to break prematurely.  I don’t think I’ve seen this situation before; I’ll have to check the code to understand why this is happening.
I’m running deCONZ and Homebridge Hue on the same Raspberry Pi to prevent any network issues between them, but I suppose this might still happen when deCONZ is quit (or crashes) while Homebridge Hue is still initialising.
You might want to specify both deCONZ and the Hue bridge under hosts in config.json.  If Homebridge Hue would discover only one of them, it would proceed without knowing there was another gateway.

Yes, you're correct that I have no devices on my Hue Bridge. I also do run deCONZ and Homebridge Hue on the same pi. There seem to be at least two issues at play here:

Whatever causes deCONZ (I believe) to eventually fail during a power outage, despite the pi staying up. I haven't looked into this much to understand what happens; there may be some clues in the log I saved that would at least confirm this, but I need to look at it some more.
The issue shown in the log above where Homebridge Hue, as you note, escapes its wait loop and proceeds when confronted with some errors in its communication with deCONZ, leading to removal of devices from HomeKit.

Thanks for your suggestions. I will add deCONZ to the hosts list, and perhaps the Hue bridge as well. Is the ip address all that's required?

Is the ip address all that's required?

Yes, if you use the default port.  Better specify deCONZ as <IP_ADDRESS> when running on the same Pi.
Ad 1.  I'm at a loss here.  I use a USB powerbank with pass-through charging as UPS for my Raspberry Pi, running deCONZ and Homebridge.  It powers the Pi for some 18 hours, and during my last test, deCONZ continued running.
Ad 2. Above commit fixes this.
[10/26/2020, 7:50:45 PM] [Hue] pi5: dresden elektronik deCONZ gateway v2.5.85, api v1.16.0
[10/26/2020, 7:50:45 PM] [Hue] pi5: warning: not using recommended deCONZ gateway version 2.5.84
[10/26/2020, 7:50:45 PM] [Hue] pi5: gateway request 1: get /
[10/26/2020, 7:50:45 PM] [Hue] pi5: gateway request 1: ok
[10/26/2020, 7:50:45 PM] [Hue] pi5: gateway request 2: get /groups/0
[10/26/2020, 7:50:45 PM] [Hue] pi5: gateway request 2: ok
[10/26/2020, 7:50:45 PM] [Hue] pi5: /resourcelinks/1: 5 lightlist entries
[10/26/2020, 7:50:45 PM] [Hue] pi5: /resourcelinks/1: /lights/5: not available
[10/26/2020, 7:50:45 PM] [Hue] pi5: gateway not yet initialised - wait 1 minute
[10/26/2020, 7:50:46 PM] [Config] Homebridge Config UI X v4.30.0 is listening on :: port 8080
[10/26/2020, 7:51:05 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:51:25 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:51:45 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:51:45 PM] [Hue] pi5: gateway request 3: get /
[10/26/2020, 7:51:45 PM] [Hue] pi5: gateway request 3: ok
[10/26/2020, 7:51:45 PM] [Hue] pi5: gateway request 4: get /groups/0
[10/26/2020, 7:51:45 PM] [Hue] pi5: gateway request 4: ok
[10/26/2020, 7:51:45 PM] [Hue] pi5: /resourcelinks/1: 5 lightlist entries
[10/26/2020, 7:51:45 PM] [Hue] pi5: /resourcelinks/1: /lights/5: not available
[10/26/2020, 7:51:45 PM] [Hue] pi5: gateway not yet initialised - wait 1 minute
[10/26/2020, 7:52:05 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:52:25 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:52:45 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:52:45 PM] [Hue] pi5: gateway request 5: get /
[10/26/2020, 7:52:45 PM] [Hue] pi5: gateway request 5: get /
[10/26/2020, 7:52:45 PM] [Hue] pi5: gateway communication error: <IP_ADDRESS>:8008: cannot connect: ECONNREFUSED
[10/26/2020, 7:52:45 PM] [Hue] pi5: /resourcelinks/1: 5 lightlist entries
[10/26/2020, 7:52:45 PM] [Hue] pi5: /resourcelinks/1: /lights/5: not available
[10/26/2020, 7:52:45 PM] [Hue] pi5: gateway not yet initialised - wait 1 minute
[10/26/2020, 7:53:05 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:53:25 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:53:45 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:53:45 PM] [Hue] pi5: gateway request 6: get /
[10/26/2020, 7:53:45 PM] [Hue] pi5: gateway request 6: ok
[10/26/2020, 7:53:45 PM] [Hue] pi5: gateway request 7: get /groups/0
[10/26/2020, 7:53:45 PM] [Hue] pi5: gateway request 7: ok
[10/26/2020, 7:53:45 PM] [Hue] pi5: /resourcelinks/1: 5 lightlist entries
[10/26/2020, 7:53:45 PM] [Hue] pi5: /resourcelinks/1: /lights/5: not available
[10/26/2020, 7:53:45 PM] [Hue] pi5: gateway not yet initialised - wait 1 minute
[10/26/2020, 7:54:05 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:54:25 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:54:45 PM] [Hue] homebridge-hue is taking a long time to load and preventing Homebridge from starting.
[10/26/2020, 7:54:45 PM] [Hue] pi5: gateway request 8: get /
[10/26/2020, 7:54:45 PM] [Hue] pi5: gateway request 8: ok
[10/26/2020, 7:54:45 PM] [Hue] pi5: gateway request 9: get /groups/0
[10/26/2020, 7:54:45 PM] [Hue] pi5: gateway request 9: ok
[10/26/2020, 7:54:45 PM] [Hue] pi5: 00212EFFFF03D4A7: dresden elektronik deCONZ gateway "pi5"

In beta v0.11.78-1, if you want to test it.


Update dependencies

We want to keep the provider up to date with the latest version of the dependencies.
Also resolves https://github.com/1Password/terraform-provider-onepassword/security/dependabot/34

Good question.
Here are the steps that I made:

go get -u ./...
go mod tidy && go mod vendor

I've updated the PR description with the steps as well.


Does this api still work?

Hi,
I installed and set up everything as instructed, however, when I run the sample code I receive the error
if (response.status_code is not 200): raise Exception("Bad response from the CryptoControl API")
Exception: Bad response from the CryptoControl API

I see the website is still up and running, however, I'm assuming the python API is not. If I'm wrong please let me know because I'd love to use this repo.

I don't think it still working. Please if you come across any working one similar to this, kindly drop it here.

I don't think it still working. Please if you come across any working one similar to this, kindly drop it here.

No it's not working


Minor notification description fixes

Story details: https://app.clubhouse.io/augur/story/17075

Coverage increased (+0.04%) to 63.211% when pulling 8c03f369a7a44614b3cad624be686a23bcc97607 on adrake/ch17075/remove-reference-to-mailbox-in-notification into cc7e94da6ec7a0c097af88a9f281aa0615923ea3 on master.


Can someone please provide syntax of setting.json file

I am a new user of this extension,
Can someone provide me the syntax for MySQL connection?
"database.connections": []

Here is an example of the User Settings file without any settings besides the vscode-database. Options for the type settings are mysql or postgres.
{
    "database.connections": [
        {
            "type": "postgres",
            "name": "your name",
            "user": "your user",
            "host": "example.com:5432",
            "password": "your-password",
            "database": "your_database"
        }
    ]
}

Thanks! Would be nice to add that to the readme.

How to setup postgres and mysql database in workspace setting

You can use command SQL: Save current server. In future i add icon to save this setting ;)

The workspace setting above didn't work for me,
Where do i execute the SQL: Save current server command ?  I cant figure out how to save server
settings in a workspace.  I keep having to connect manually.
I also tried a keyboard shortcut to exectute saveConfig but it didnt seem to do anything either. I'm really new to vscode and postgres so any help would be appreciated.

You can use command SQL: Save current server. In future i add icon to save this setting ;)

A button would be great for this.

@Ben-Cox Use shortcut (Ctrl + Shift + P) and find SQL: Save current server command.

A button would be great for this.

You right! I created issue #77


Can't see any data in Grafana

Hello, first of all BIG thanks to you for making your ChaosMesh observable through Grafana!
I added the Datasource according to the tutorial and Grafana accepted and saved it. But when I try to add the first panel, it looks like Grafana isn't able to fetch any data from it. I can't even choose a namespace. See below picture.
Do you have any tips to debug this? Maybe I'm just missing something.

It seems to be an API URL configuration problem.
For example, in my local machine, I have already port-forward a chaos mesh service by kubectl port-forward -n chaos-testing svc/chaos-dashboard 2333:2333, so I need to fill the http://localhost:2333 as below screenshot:

And also, for the current implementation, whether it is installed via helm or install.sh, you need to configure the timezone to fit your browser timezone 😢.
Like: helm install chaos-mesh helm/chaos-mesh --namespace=chaos-testing --set dashboard.create=true,dashboard.securityMode=false,timezone=Asia/Shanghai
This is a bug, the problem is even you choose a different timezone in the Grafana time range, it still keeps in the browser timezone.
I will plan to rewrite the datasource plugin to prevent these problems. In fact, there is no need to manually set the timezone when install, because the server can uniformly convert different time zones into UTC time for processing.

It seems to be an API URL configuration problem.
For example, in my local machine, I have already port-forward a chaos mesh service by kubectl port-forward -n chaos-testing svc/chaos-dashboard 2333:2333, so I need to fill the http://localhost:2333 as below screenshot:

And also, for the current implementation, whether it is installed via helm or install.sh, you need to configure the timezone to fit your browser timezone 😢.
Like: helm install chaos-mesh helm/chaos-mesh --namespace=chaos-testing --set dashboard.create=true,dashboard.securityMode=false,timezone=Asia/Shanghai
This is a bug, the problem is even you choose a different timezone in the Grafana time range, it still keeps in the browser timezone.
I will plan to rewrite the datasource plugin to prevent these problems. In fact, there is no need to manually set the timezone when install, because the server can uniformly convert different time zones into UTC time for processing.

Thanks @g1eny0ung for the answer! I think he already covered all cases.
@torblerone  For the URL, when you configured the data source, the URL you entered should be correct, otherwise there will be some error saying the data source is wrong.
Btw It would be great to support timezone converting!

Thanks @g1eny0ung for the answer! I think he already covered all cases.
@torblerone  For the URL, when you configured the data source, the URL you entered should be correct, otherwise there will be some error saying the data source is wrong.
Btw It would be great to support timezone converting!

get a same issue

@zhuwenxing I'm already rewriting the data source plugin in https://github.com/g1eny0ung/grafana-chaos-mesh-datasource. This plugin fixes a few issues and supports the feature of variables.
Currently, it's still in the grafana plugin repository pipeline. Before it publishes, you can go to the releases to download the production zip and have a try.
If you find some problems after trying, welcome to our slack channel (#project-chaos-mesh) to discuss with us, or you can also open an issue to the repo to describe your problem.

@g1eny0ung Any plan to move your plugin to this repo?

@g1eny0ung Any plan to move your plugin to this repo?

I once thought about overwriting the files in this repo to make changes, but because there are many changes, I chose to push to my own repo first.
If I choose, I prefer to archive this repo? This can prevent some problems, like version conflicts, etc.

@zhuwenxing I'm already rewriting the data source plugin in https://github.com/g1eny0ung/grafana-chaos-mesh-datasource. This plugin fixes a few issues and supports the feature of variables.
Currently, it's still in the grafana plugin repository pipeline. Before it publishes, you can go to the releases to download the production zip and have a try.
If you find some problems after trying, welcome to our slack channel (#project-chaos-mesh) to discuss with us, or you can also open an issue to the repo to describe your problem.

sure,  I will try it later!

@g1eny0ung Any plan to move your plugin to this repo?

I once thought about overwriting the files in this repo to make changes, but because there are many changes, I chose to push to my own repo first.
If I choose, I prefer to archive this repo? This can prevent some problems, like version conflicts, etc.

After discussion with @yeya24, we have already moved the new implementation into this repo.

Close due to the new datasource plugin finally being published. (Note that the latest plugin is only available for Chaos Mesh version 1.x. We will continue to update it to support 2.0)


Non-Matrix changes of #46

cherry-picked, I think

turns out most of the code here isnt actually chery-pickable into the 0.4.x-deno branch so ill just switch the base back to main and deal with the conflicts in #44

afaik most of this stuff landed in 0.5.x anyways and there's a fair number of merge conflicts so unless i missed anything, this may be able to be closed


fix: local very_good create doesn't use imported templates

Description
While working with the local very_good_cli and very_good_templates I ran into the issue that the very_good_cli doesn't use the modified very_good_core_bundle.dart and therefore very_good create flutter_app doesn't create a customized app.
Steps To Reproduce
Prerequires

Using Ubuntu 22.04
Installing Flutter 3.24.3
Clone very_good_cli
Clone very_goog_templates
Activating mason_cli
Activating very_good_cli with the code locally

Steps to reproduce unexpected behavior

Customize very_good_core template in the the very_good_templates:
(very_good_templates/very_good_core/brick/{{project_name.snakeCase()}})
1.1 Adding an additional File
1.2 Adding additional dependencies in the pubspec.yaml
Bundle the existing very_good_core brick mason bundle . -t dart -o /path/to/export/
Copy the created very_good_core_bundle.dart and replace it in the very_good_cli directory:
(very_good_cli/lib/src/commands/create/templates/very_good_core/)
(Format the code inside the very_good_core_bundle.dart that it's recognizable by the language styling of dart)
Create a new flutter app with the modified local very_good_cli very_good create flutter_app AppName
See that no additional file is present as well as no customized dependencies in the pubspec.yaml

Expected Behavior
very_good create flutter_app AppName creates a flutter app while using the very_good_core template, including the modified very_good_core_bundle.dart
Additional Context
I haven't changed any code in the cli, besides mentioned below, so I would assume that if the filename of the very_good_core_bundle.dart is correct, it should be used and my changes become created/implemented when I create a new app.
Am I missing an implementation step somewhere or is this what I'm trying to use your projects for even possible?
I can verify the following things:

I'm using the local very_good_cli:
To confirm that I'm using my local cli, I changed the comment block after when an app gets created in the very_good_core_template.dart in the cli project.
The changes I've made in the very_good_core template are there:
With a base64 decoder I can see from the pubspec.yaml string that my modifications are inside the bundle. Not to mention the new lines of my additional file.
As I'm getting no errors whatsoever I assume that there shouldn't be any issues.

This may be a duplicate of #1078

On the first glance my problem looks very much like #4295, which is mentioned inside #1078, that the local cli is not used, even if it was activated with the proper command and also successfully shown in the terminal.
But as I mentioned in my additional context, when I activate the local cli and create a flutter_app, the very_good_core_templates.dart is used - which I would expect to actually include the very_good_core_bundle.dart.
Therefore, it looks to me as if my local cli is being used on the one hand, but on the other hand, since the very_good_core_bundle.dart is not included/used, that the online version is being used there?
If my very_good_core_templates.dart wasn't used while creating an app with the local activated cli I would confirm that it is a duplicate of #1078.
Maybe I expect dart to work differently here than it does.
So I'm a little unsure.
I also tried as mentioned in #4295 to activate my local cli after I cleaned / deleted my pub-cache folder but with no success.

From matthew-carroll: I've discovered that if I delete all the references I can find in my Pub cache for this package, then I can get Pub to truly activate my local version.

Hi @SareXx, thanks for opening this issue and the explanation.
Overall I don't see this as an issue on the CLI package and more of a local setup issue overall. The update process for our bundles is working as expected. As was noted before, we do know of some issues with the pub cache when installing packages but this isn't something that we can fix inside of this package. Also we can't provide support for people forking our repo just given our staffing. If this is something you feel like you can work on and provide a PR for please let us know.
Given this I'm going to close this out as a won't fix as I don't see a need for a change/update on the CLI package.


Is the order of replies to watch requests strict ?

i.e. if I pass multiple watch requests in same http/2 stream, is the order of replies guarantied ?
Answer to this question must be highlited in documentation. It is very important for getting right watch_id for each request if watches are created in parallel.

i am not exactly sure what do you mean. can you clarify?

Etcd watch API requires us to use stream-steram GRPC API. This mean that creation of two watchers will look like sending two requests of watcher creation in SINGLE http/2 stream. After that, two responses (about successful watcher creation) will be sent by etcd inside that HTTP/2 stream. I'm asking about order of these replies. I'm asking if order of replies strictly match order of requests. In other words, is it possible to have next situation:
-> create watch on key "xxx"
-> create watch on key "yyy"
<- watch on "yyy" created with watch_id=2
<- watch on "xxx" created with watch_id=1

or even worse (note different order of watch_id)
-> create watch on key "xxx"
-> create watch on key "yyy"
<- watch on "yyy" created with watch_id=1
<- watch on "xxx" created with watch_id=2

the current implementation does guarantee about this ordering. however, it might change later on.
what we suggested is to create watch one by one none concurrently, or wait for https://github.com/coreos/etcd/pull/8662 to land.

Please reopen issue. This fact must be specified in documentation.

where in the doc says the ordering is guaranteed?
https://github.com/coreos/etcd/pull/8662 is well covered the fact. if you think the doc needs to be improved, please open an issue/pr to fix it. thank you.

docs does not say anything about order. Why not to fix docs (specify that order is strict) using this issue number ?

the doc improvement is here: https://github.com/coreos/etcd/pull/8662/files#diff-c60cc9a0d9c8fe4cdedc8b5944475568R676
i am not sure what you want. i would suggest you to read through the issue i provided, and the pr to fix it. if you need anything more, make a pr.


Unexpected version number in 'available' attribute for non-specific platform '*'

Hi, I'm using NVActivityIndicatorView in Xcode to 10.2.1 and Swift 4.2using Cocoapods and I'm getting a few warnings.
In public final class NVActivityIndicatorView: UIView line 435I'm getting the following warning.

Unexpected version number in 'available' attribute for non-specific platform '*'

In public extension NVActivityIndicatorViewable where Self: UIViewController line 57 and 88 I'm seeing the following warning.

'public' modifier is redundant for instance method declared in a public extension

What can I do to fix these warnings?
The fix for the first warning is described here:
https://stackoverflow.com/questions/55721287/warning-unexpected-version-number-in-available-attribute-for-non-specific-pl
They both look like easy fixes but I'm not sure how to handle this since I'm using Cocoapods and I'm afraid to break something if I try to manually fix them.
Can someone be so kind and help me resolve these warnings?
By the way, NVActivityIndicatorView is a great library, keep up the good work.
Thanks a lot!

@fstigre: Hmm seems they have been resolved in #274. Let's try with 4.7.0 first, though it should be for Swift 5

So, what you're saying is that it was resolved in the latest version (4.7.0 / Swift 5)? Thanks.

@fstigre: Let me know if it helps.

Thanks.


fix(model-server): provide a valid operative spec

Fixes the missing response specification for a healthy /health reply.
To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

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


test: add vite5 integration test for react

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (83d71c3) 86.37% compared to head (49d3aab) 86.31%.
Report is 20 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6443      +/-   ##
==========================================
- Coverage   86.37%   86.31%   -0.06%
==========================================
  Files          87       87
  Lines        2877     2880       +3
  Branches      802      802
==========================================
+ Hits         2485     2486       +1
- Misses        328      329       +1
- Partials       64       65       +1

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


[W5.11][F09-A3]Ryan Ang Jia Yong

Added "sortedList" command - Works just like the "list" command, but names are sorted in alphabetical ordering.
Added case insensitivity to "find" command - Works just like the original "find" command except that "find bob" also returns "Bob", "bOb", etc.

You might want to remove those unwanted code that is commented. Overall it is well written


Make "bundlesize" a dev dependency

"bundlesize" has an the following dependencies: "brotli-size" > "iltorb".
"iltorb" crashes often when trying to compile, but that's not the problem.
The problem is that "bundlesize" should be a dev dependency and not a normal one. That means it shouldn't even be downloaded by 90% of users.

@hisk It would be great if you could merge this.

This is causing #53

@winktim Awesome! Thanks for your contribution and sorry for the delay. We'll include this in the 3.0.0 version.


Add

Adding mention to the color input component, as suggested by @fzaninotto (#1).

I'd prefer that you create a "Third-party components" section between <TextInput> and "Writing you own component", where you just mention the name and purpose in a single line, then link to your README (kind of like the third-party REST clients section).


Fix docker service handler for non root users.

Added become to service handler for non root user.

The instructions we are working on requires that non root users are granted password less sudo capabilities  on the deployer so no other changes are required.

Interesting. I wonder how having passwordless sudo users instead of root improves security, but thats for architects/security engineers to talk about. Thanks for the update!


Nothing happens

I'm trying to link Fullmetal Alchemist Brotherhood (atsa release) but when i hit unlink it just returns with the message "The unlinking is complete!" almost instantly but there is no file.
nothing in the output log.

Hi,
You probably didn't setup the dependencies properly. Did you follow the
setup guide. Including CPAN modules?
If so, please state OS.
On Jul 4, 2016 5:49 PM, "shogunreaper"<EMAIL_ADDRESS>wrote:

I'm trying to link Fullmetal Alchemist Brotherhood (atsa release) but when
i hit unlink it just returns with the message "The unlinking is complete!"
almost instantly but there is no file.
nothing in the output log.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/hilts-vaughan/UnlinkMKV-GUI/issues/17, or mute the
thread
https://github.com/notifications/unsubscribe/ABB3p7jKA1JA_6AVzNpfZMCps3EIYxP0ks5qSX_RgaJpZM4JEqin
.

i have Strawberry Perl, mkvtoolnix ffmpeg and .net installed.

Did you follow the part about installing the Perl modules? You can find it
in the README
On Jul 4, 2016 5:52 PM, "shogunreaper"<EMAIL_ADDRESS>wrote:

i have Strawberry Perl, mkvtoolnix ffmpeg and .net installed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/hilts-vaughan/UnlinkMKV-GUI/issues/17#issuecomment-230357710,
or mute the thread
https://github.com/notifications/unsubscribe/ABB3p1VhuAya-78rkxQwsHNxVK4CZHE2ks5qSYCWgaJpZM4JEqin
.

okay i just did that
it created a file this time but gave me errors
UnlinkMKV    processing G:/Anime/Fullmetal Alchemist Brotherhood/Fullmetal_Alchemist_Brotherhood_01v2_[BD_720p][AtsA][76A5BD6E].mkv       checking if file is segmented          "G:/Anime/Fullmetal Alchemist Brotherhood/Fullmetal_Alchemist_Brotherhood_01v2_[BD_720p][AtsA][76A5BD6E].mkv" contains segmented chapters       generating chapter file          loading chapters             Checking for editions...             non-default chapter dropped             Done checking for editions...          writing chapter temporary file          looking for segment parts          checking that all required segments were found          extracting attachments          creating splits          setting parts          extracting subs          making substyles unique          mashing unique substyles to all parts          remuxing subtitles          building file          fixing subs, again... (maybe an mkvmerge issue?)          moving built file to final destination UnlinkMKV    processing G:/Anime/Fullmetal Alchemist Brotherhood/Fullmetal_Alchemist_Brotherhood_ED1v2_Clean_[BD_720p][AtsA][97CB5EEE].mkv       checking if file is segmented          "G:/Anime/Fullmetal Alchemist Brotherhood/Fullmetal_Alchemist_Brotherhood_ED1v2_Clean_[BD_720p][AtsA][97CB5EEE].mkv" does not contain segmented chapters UnlinkMKV    processing G:/Anime/Fullmetal Alchemist Brotherhood/Fullmetal_Alchemist_Brotherhood_OP1v2_Clean_[BD_720p][AtsA][39C599D1].mkv       checking if file is segmented          "G:/Anime/Fullmetal Alchemist Brotherhood/Fullmetal_Alchemist_Brotherhood_OP1v2_Clean_[BD_720p][AtsA][39C599D1].mkv" does not contain segmented chapters

Hi,
Did you recently just install mkvtoolnix? Looks like you're on Windows -- there is a bug with the newest version that prevents it from working with automation (it spawns a GUI by default WTF)
You can try overwriting your copy of winport.pl that came with the release with this version: https://raw.githubusercontent.com/hilts-vaughan/UnlinkMKV-GUI/bbb7e1af9ea39285371a963968a9cad54a977cbe/UnlinkMKV-GUI/UnlinkMKV-GUI/winport.pl
If this fixes it for you, let me know and I can drop a new release. Thanks for the patience.

it seems checking ignore default flag allows it to go through.

Cool -- try the above as well if you have issues. If your files look as expected, please let me know.
Thanks!

they seem to work fine.
thanks for your help

a sorry one last thing
can you make it so we can change the temp directory?
i have an ssd and don't really like all the writing its doing when i'm putting them on another drive

I will make an option for it in the interface.
On Jul 4, 2016 6:22 PM, "shogunreaper"<EMAIL_ADDRESS>wrote:

a sorry one last thing
can you make it so we can change the temp directory?
i have an ssd and don't really like all the writing its doing when i'm
putting them on another drive
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hilts-vaughan/UnlinkMKV-GUI/issues/17#issuecomment-230359743,
or mute the thread
https://github.com/notifications/unsubscribe/ABB3p_HESHPCPOeqbIRl1iVArjYIJwVXks5qSYecgaJpZM4JEqin
.

Please open a seperate issue, though. You can get around this by using a
symbolic link for now. You should note a modern SSD is very durable though,
you likely have nothing to worry about.
On Jul 4, 2016 6:23 PM, wrote:

I will make an option for it in the interface.
On Jul 4, 2016 6:22 PM, "shogunreaper"<EMAIL_ADDRESS>wrote:

a sorry one last thing
can you make it so we can change the temp directory?
i have an ssd and don't really like all the writing its doing when i'm
putting them on another drive
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hilts-vaughan/UnlinkMKV-GUI/issues/17#issuecomment-230359743,
or mute the thread
https://github.com/notifications/unsubscribe/ABB3p_HESHPCPOeqbIRl1iVArjYIJwVXks5qSYecgaJpZM4JEqin
.

You can get around this by using a symbolic link for now.

what is that?

You should note a modern SSD is very durable though, you likely have nothing to worry about.

yeah but i'd rather avoid writing hundreds of gb at a time to it.

Please open a seperate issue, though.

you want me to open a new topic about it?

yes, open a new topic. This one is closed.
Google "junction points". It allows you to move folders to other drives
without moving them physically, in a sense.
On Jul 4, 2016 6:27 PM, "shogunreaper"<EMAIL_ADDRESS>wrote:

Please open a seperate issue, though.
you want me to open a new topic about it?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/hilts-vaughan/UnlinkMKV-GUI/issues/17#issuecomment-230360108,
or mute the thread
https://github.com/notifications/unsubscribe/ABB3pyUv8J1Ny1CRk1d6rMwcE-TTrFxHks5qSYjhgaJpZM4JEqin
.


[BUG] Constantly scale down KCM when shoot is waken up just after a hibernation

Describe the bug:
Since quite some time I am observing in my local setup that if try to wake-up a shoot cluster that has been just hibernated, it stuck on wait the nodes to join. Further analysis shows that kube-controller-manager is scaled down, so there is no controller to approve the CSR sent by the node and then track the node status.
If I try to manually scale-up the KCM, after a few seconds it is again scaled down,
3m15s       Normal    SuccessfulDelete               replicaset/kube-controller-manager-5f44699448                     Deleted pod: kube-controller-manager-5f44699448-222cf
3m9s        Normal    SuccessfulCreate               replicaset/kube-controller-manager-5f44699448                     Created pod: kube-controller-manager-5f44699448-zwn6s
2m45s       Normal    SuccessfulDelete               replicaset/kube-controller-manager-5f44699448                     Deleted pod: kube-controller-manager-5f44699448-zwn6s
116s        Normal    SuccessfulCreate               replicaset/kube-controller-manager-5f44699448                     Created pod: kube-controller-manager-5f44699448-vvqm2
105s        Normal    SuccessfulDelete               replicaset/kube-controller-manager-5f44699448                     Deleted pod: kube-controller-manager-5f44699448-vvqm2
96s         Normal    SuccessfulCreate               replicaset/kube-controller-manager-5f44699448                     Created pod: kube-controller-manager-5f44699448-s9hst
75s         Normal    SuccessfulDelete               replicaset/kube-controller-manager-5f44699448                     Deleted pod: kube-controller-manager-5f44699448-s9hst
50s         Normal    SuccessfulCreate               replicaset/kube-controller-manager-5f44699448                     Created pod: kube-controller-manager-5f44699448-jqsnq
45s         Normal    SuccessfulDelete               replicaset/kube-controller-manager-5f44699448                     Deleted pod: kube-controller-manager-5f44699448-jqsnq
50s         Normal    ScalingReplicaSet              deployment/kube-controller-manager                                Scaled up replica set kube-controller-manager-5f44699448 to 1
45s         Normal    ScalingReplicaSet              deployment/kube-controller-manager                                Scaled down replica set kube-controller-manager-5f44699448 to 0

Before and during the hibernation the kube-apiserver is working just as expected, during the wake up it also starts from the first time - so it is unexpected to me to see DWD scaling down the KCM. Eventually after 10 to 20 minutes of failures, the KCM will be let to scale up.
Expected behaviour:
To let the Gardener wake-up hibernated shoot without unnecessary scaling down of KCM.
How To Reproduce (as minimally and precisely as possible):

Create a shoot.
Hibernates the shoot.
Wait a minute or two.
Wake up the shoot.
See the shoot reconciliation is failing with

conditions:
  - lastTransitionTime: '2020-06-01T21:46:27Z'
    lastUpdateTime: '2020-06-01T22:27:04Z'
    message: Shoot cluster has been hibernated.
    reason: ConditionNotChecked
    status: 'True'
    type: APIServerAvailable
...
lastOperation:
  description: 'Flow "Shoot cluster reconciliation" encountered task errors: [task
    "Waiting until shoot worker nodes have been reconciled" failed: Error while waiting
    for Worker shoot--li311840--local-aws/local-aws to become ready: extension encountered
    error during reconciliation: Error reconciling worker: Failed while waiting for
    all machine deployments to be ready: ''timed out waiting for the condition'']
    Operation will be retried.'
  lastUpdateTime: '2020-06-01T22:27:31Z'
  progress: 85
  state: Error
  type: Reconcile

Logs:
dependency-watchdog-probe
I0601 22:19:19.759181       1 scaler.go:219] Starting probes for namespace: shoot--foo--bar
I0601 22:19:19.759219       1 scaler.go:238] Starting the probe in the namespace shoot--foo--bar: &{shoot-kube-apiserver 0xc00007b0c0 [0xc00007b080]}
I0601 22:19:19.759394       1 multicontext.go:60] Registering the context for the key: shoot--foo--bar
I0601 22:19:24.959749       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers). Will retry...
 Will retry...
I0601 22:19:44.961624       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers). Will retry...
I0601 22:19:50.059506       1 prober.go:240] shoot-kube-apiserver/shoot--foo--bar/internal: probe succeeded
I0601 22:19:50.059531       1 prober.go:255] shoot-kube-apiserver/shoot--foo--bar/internal: probe result: &scaler.probeResult{lastError:error(nil), resultRun:1}
I0601 22:19:54.961916       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: net/http: request canceled (Client.Timeout exceeded while awaiting headers). Will retry...
I0601 22:19:54.961946       1 prober.go:255] shoot-kube-apiserver/shoot--foo--bar/external: probe result: &scaler.probeResult{lastError:(*url.Error)(0xc00057b920), resultRun:2}
I0601 22:19:54.963340       1 prober.go:240] shoot-kube-apiserver/shoot--foo--bar/internal: probe succeeded
I0601 22:19:54.963358       1 prober.go:255] shoot-kube-apiserver/shoot--foo--bar/internal: probe result: &scaler.probeResult{lastError:error(nil), resultRun:3}
I0601 22:20:00.059849       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers). Will retry...
 Will retry...
I0601 22:20:10.060187       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers). Will retry...
I0601 22:20:14.964020       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers). Will retry...
I0601 22:20:20.060516       1 prober.go:243] shoot-kube-apiserver/shoot--foo--bar/external: probe failed with error: Get https://api.bar.foo.internal.dev.k8s.ondemand.com/version?timeout=10s: context deadline exceeded (Client.Timeout exceeded while awaiting headers). Will retry...
I0601 22:20:20.060545       1 prober.go:255] shoot-kube-apiserver/shoot--foo--bar/external: probe result: &scaler.probeResult{lastError:(*url.Error)(0xc00089e9c0), resultRun:1}
I0601 22:20:20.061664       1 prober.go:240] shoot-kube-apiserver/shoot--foo--bar/internal: probe succeeded
I0601 22:20:20.061688       1 prober.go:255] shoot-kube-apiserver/shoot--foo--bar/internal: probe result: &scaler.probeResult{lastError:error(nil), resultRun:2}
I0601 22:20:24.356736       1 multicontext.go:63] Unregistering the context for the key: shoot--foo--bar
I0601 22:20:24.356763       1 multicontext.go:68] Cancelling older context for the key: shoot--foo--bar

Screenshots (if applicable):
Anything else we need to know?:
Version: 0.4.0

@vpnachev Thanks for reporting this. I will try to reproduce the issue.

@rfranzke, this sounds like the issue you were sharing with me today?

@ialidzhikov No, in my case the KCM was running completely fine - it simply didn't react on CSRs created by new kubelets that tried to join the cluster.

I also hit this issue in my local setup with v0.4.1.

The problem is this
https://github.com/gardener/dependency-watchdog/blob/fc3bd3dd3972024d9a52f01e76f85e3aa4d9e6a0/pkg/scaler/prober.go#L255-L262
It tries to execute 3 times client.Discovery().ServerVersion() without any backoff period nor waiting
https://github.com/gardener/dependency-watchdog/blob/fc3bd3dd3972024d9a52f01e76f85e3aa4d9e6a0/pkg/scaler/prober.go#L266-L286

@mvladev But this is only one iteration of the probe. It takes 3 or more consecutive failed iterations. And each iteration happens at a period of 30s.
I am not saying that a delay between the retries won't help. Just pointing out that there is in fact another level of retries and delays on top of this. The tight loop of retries was just to avoid some transient errors)

@vpnachev @mvladev @ialidzhikov I tried to reproduce this issue multiple times but the cluster woke up normally each time. Is it more reproducible with https://github.com/gardener/gardener/pull/2406?

I am struggling since several months and I have never run Gardener with the SNI feature.

I just saw that DWD has scaled up KCM when a shoot was hibernated.

I just saw that DWD has scaled up KCM when a shoot was hibernated.

The watchdog doesn't understand hibernation. It just looks if the shoot apiserver probe succeeds (internally and externally). If the shoot probe succeeds, it would scale up KCM. Not sure why the probe succeeded. That would mean apiserver was up even when the cluster status was saying hibernated.

It looks like gardener scaled down KCM first and apiserver next. It might be a good idea to scale down apiserver first, wait until it is scaled down fully and only then scale down KCM. Otherwise, there will be window where KCM is scaled down but apiserver is still running where the watchdog might interfer.
https://github.com/gardener/gardener/blob/master/pkg/operation/botanist/controlplane.go#L322-L331

This is because the normal reconciliation flow is used for the hibernation/wake-up as well. The kube-apiserver is usually deployed before any other component that needs to talk to it.
Can't the DWD simply respect the hibernation setting and do nothing in this case?

Can't the DWD simply respect the hibernation setting and do nothing in this case?

Yes. That makes sense. I merely stating what was happening. To check if the cluster is hibernated, should it check the Cluster resource?

Hm, yes, I think that's the only place where to get the information.

Fixed with #23


Implement SET_TEXT_DROPSHADOW in ScaledText

SET_TEXT_DROPSHADOW allows you to make a more customizable drop shadow than SET_TEXT_DROP_SHADOW.

I noticed this issue now, but you assumed wrong. SET_TEXT_DROPSHADOW just does the same thing as SET_TEXT_DROP_SHADOW unless a non-positive value is passed as the 1st argument. The 2nd to 5th argument is marked as UNUSED_PARAM in commands_hud.cpp and the native implementation doesn't even use none of them. If the 1st arg is not positive, the drop shadows is removed for the next text draw.
I wish I noticed the wrong assumption before releasing any stable releases tbh...

Oh, I didn't checked commands_hud.cpp before committing, I used Dot's NativeDB.