Make the NewX() monitoring variables safe to re-register

What does this PR do?
Fixes https://github.com/elastic/beats/issues/33125
Because this problem makes me a tad paranoid, I decided to implement the fix on a more global level. Specifically, this changes the behavior of the NewX() monitoring functions so they don't panic when a variable of the same name and type is re-registered. This fix is a tad opinionated, and I'd like to hear input from others on a few things:

Instead of panicking when a variable is re-registered, we return the existing variable. My concern is that this is a tad implicit, and code might be assuming that a call to NewX() will create a new monitoring variable with a zero value. Should we zero out the underlying metric, and then return?
If someone tries to re-register a variable with options, we just revert to a panic. I figured this was the most understandable behavior, as certain options, such as expvar exporting, can't really be modified. Should we attempt to merge or reset variables where possible?

Checklist

[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added an entry in CHANGELOG.md

:broken_heart: Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-10-05T22:00:55.282+0000

Duration: 9 min 11 sec

Test stats :test_tube:

Test
Results

Failed
2

Passed
697

Skipped
5

Total
704

Test errors
Expand to view the tests failures
Test / Matrix - PLATFORM = 'ubuntu-20.04 && immutable' / Test / TestTypeMismatch – github.com/elastic/elastic-agent-libs/monitoring

Expand to view the error details
 Failed

Expand to view the stacktrace
 === RUN   TestTypeMismatch
--- FAIL: TestTypeMismatch (0.00s)
panic: name safe_registry already used [recovered]
	panic: name safe_registry already used

goroutine 39 [running]:
testing.tRunner.func1.2({0x77d300, 0xc000183050})
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.linux.amd64/src/testing/testing.go:1389 +0x24e
testing.tRunner.func1()
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.linux.amd64/src/testing/testing.go:1392 +0x39f
panic({0x77d300, 0xc000183050})
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.linux.amd64/src/runtime/panic.go:838 +0x207
github.com/elastic/elastic-agent-libs/monitoring.panicErr(...)
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/registry.go:257
github.com/elastic/elastic-agent-libs/monitoring.(*Registry).Add(0xc000030500, {0x7df34e, 0x8d66fa}, {0x871ec0, 0xc000031d80}, 0x0)
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/registry.go:155 +0xda
github.com/elastic/elastic-agent-libs/monitoring.(*Registry).NewRegistry(0xc000030500, {0x7df34e, 0xd}, {0x0?, 0xa6e800?, 0xc000054f60?})
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/registry.go:94 +0x158
github.com/elastic/elastic-agent-libs/monitoring.TestTypeMismatch(0xc000176ea0)
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/metrics_test.go:51 +0x50
testing.tRunner(0xc000176ea0, 0x80fb58)
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.linux.amd64/src/testing/testing.go:1439 +0x102
created by testing.(*T).Run
	/var/lib/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.linux.amd64/src/testing/testing.go:1486 +0x35f

Test / Matrix - PLATFORM = 'windows-2019 && windows-immutable' / Test / TestTypeMismatch – github.com/elastic/elastic-agent-libs/monitoring

Expand to view the error details
 Failed

Expand to view the stacktrace
 === RUN   TestTypeMismatch
--- FAIL: TestTypeMismatch (0.00s)
panic: name safe_registry already used [recovered]
	panic: name safe_registry already used

goroutine 51 [running]:
testing.tRunner.func1.2({0x14ac780, 0xc0001c6fd0})
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.windows.amd64/src/testing/testing.go:1389 +0x24e
testing.tRunner.func1()
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.windows.amd64/src/testing/testing.go:1392 +0x39f
panic({0x14ac780, 0xc0001c6fd0})
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.windows.amd64/src/runtime/panic.go:838 +0x207
github.com/elastic/elastic-agent-libs/monitoring.panicErr(...)
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/registry.go:257
github.com/elastic/elastic-agent-libs/monitoring.(*Registry).Add(0xc00014e4c0, {0x150ec39, 0x1612f8b}, {0x15ae720, 0xc00014fd40}, 0x80)
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/registry.go:155 +0xda
github.com/elastic/elastic-agent-libs/monitoring.(*Registry).NewRegistry(0xc00014e4c0, {0x150ec39, 0xd}, {0x0?, 0x17af740?, 0xc00005df60?})
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/registry.go:94 +0x158
github.com/elastic/elastic-agent-libs/monitoring.TestTypeMismatch(0xc0001b6d00)
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/src/github.com/elastic/elastic-agent-libs/monitoring/metrics_test.go:51 +0x50
testing.tRunner(0xc0001b6d00, 0x1541a40)
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.windows.amd64/src/testing/testing.go:1439 +0x102
created by testing.(*T).Run
	C:/Users/jenkins/workspace/ger_elastic-agent-libs-mbp_PR-83/.gvm/versions/go1.18.6.windows.amd64/src/testing/testing.go:1486 +0x35f

Steps errors
Expand to view the steps failures

Running Go tests

Took 0 min 16 sec . View more details here
Description: gotestsum --format testname --junitfile junit-report.xml -- -v ./...

Running Go tests

Took 0 min 23 sec . View more details here
Description: gotestsum --format testname --junitfile junit-report.xml -- -v ./...

go test

Took 1 min 39 sec . View more details here
Description: go test -v ./...

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

@faec regarding logging, the main use case here is monitoring variables that get hit when elastic-agent reloads a beat component. So my thinking is that we would fill the logs with scary-looking but irrelevant log lines, but it might still be worth doing at a debug level?


lorawan: add build error for too small system workq stack

The LoRaWAN subsystem uses the system work queue internally and needs more than the default stack size of 1024 bytes. This is considered in the sample application, but may be forgotten by out of tree users.
Raising a compile-time error prevents users from accidentally getting hard to debug stack overflows.

Good suggestion @JordanYates. I didn't know that specifying depends on with a range is possible, but didn't want to specify a fixed value via Kconfig. A requirement with >= makes sense. Updated.


why use android.support.v7.app.AlertDialog in RationaleDialogConfig

If I use Activity not AppCompatActivity, could result the error:

This was fixed in #153 and will be included in the next release.

Released in version 1.0.0


Tweaks to documentation design

A few things could still be improved about the new docs design:

Issue
Image

Theme Switcher Button Colors

Tip Component Design

Tabs Design

Pagination Nav Hover State

Inline Code Contrast in Light Mode

Sidebar Menu Item Icon Color

@lauridskern any update on this?

Not yet. Will set aside some time this month


update a few show commands to swallow 404

The goal is to be consistent with the rest commands, that all show commands will output blank with zero exit code instead of error'ing out. (#5006 has the full context)
3 steps:

Find impacted command list, including az storage account show
For 2 releases, warn users that breaking change is coming
Update dev documents to call out that show should never throw on 404

//CC: @tjprescott @troydai @williexu

More information about the breakdown of the show commands at the moment:
-Show commands that catch CloudErrors with a 404 status code: 102
-Show commands that have no exception handling: 119
-Show commands that have an exception handler but may/may not catch 404: 83

Closing this due to: https://github.com/Azure/azure-cli/issues/6612


Emulator is booting up ... never disappear

The notification shows up and never disappear

I removed the message, there is no need for it. Fixed with the next release.

Thanks!


Need more description to run this script

Hi @NotTheStallion
I try to run your script but I get error from install your requirement.txt. Can you support me how to run this script in detail. I use only windows and dont have much knowledge about Python

Hello @wardensc2 ,
My code was made to support Linux machines.
I suggest you install Windows Subsystem for Linux (WSL) and then run the pip install -r requirements.txt.
Guide : https://learn.microsoft.com/en-us/windows/wsl/install

Sadly, i made this code because i couldn't find online service that does it for me.
In that case, i suggest you try to install the needed packages in the vscode terminal in hope it works.


VMBDALI support missing

Hi,
Is it possible to support the VMBDALI module introduced through the original repository ?
It is the only thing missing for me at this point to fully use HA for my entire home.
The lights are to be supported as dimmers.
My coding skills are absent, but I would be happy to support through testing vigorously!

The first step is that
https://github.com/StefCoene/moduleprotocol
needs to be updated, i asked stef to do this

Perfect. Let me know how I can help!

can you send us your velbuslink file?
that would help

@Cereal2nd , can I send this to you privately ? Would only the VMBDALI entities suffice?

Seems to be there now ! https://github.com/StefCoene/moduleprotocol/commit/1bcdc616bd949e5e9ef79d2b3dfc0dc3df3240dc

yes it is, but now we need to implement/test is there a way we can login onto your bus so we can run some scans/debug info?

Unfortunately not, but I would be very willing to run many things for you and provide you with the output.

can you clone the master branch of this repo?
setup the package and run the examples/read_bus.py tool and provide me the output?

@Cereal2nd , attached you can find the output of read_bus.py and load_modules.py.

Attached you can find outputs of read_bus.py and load_modules.py. I switched a few lights on/off during the read_bus run. Hope this helps!
read_bus.out.txt
load_modules.out.txt

You will need to remove the cached memory of the DALI module, and re-run the read_bus/load_module commands. The location depends on your setup, but it will probably be /home/dieter/.velbuscache/1.p

Oops, didn't know, but will forever take it into account.
Here you go, 2 fresh files with a lot of DALI movement.
read_bus.out.txt
load_modules.out.txt

The output looks good. To get this into Home Assistant, this repo needs a release, and the Home Assistant a version bump to use that release.

This is seen in one of the files need to investigate if this is related to the PR.
the load_modules.py is not finishing, we will need to increase the timeout for your install, so we can not confirm yet that it worked
DEBUG:velbus-protocol:RX: RawMessage(priority=fb, address=e0, rtr=False, command=242, data=b'f2 09 ff ff ff ff')
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-1501' coro=<VelbusProtocol._process_message() done, defined at /home/dieter/GIT/velbus-aio/velbusaio/protocol.py:167> exception=ParserError('ChannelNamePart3Message needs exactly one bit set in channel byte')>
Traceback (most recent call last):
  File "/home/dieter/GIT/velbus-aio/velbusaio/protocol.py", line 169, in _process_message
    await self._message_received_callback(msg)
  File "/home/dieter/GIT/velbus-aio/velbusaio/controller.py", line 55, in _on_message_received
    await self._handler.handle(msg)
  File "/home/dieter/GIT/velbus-aio/velbusaio/handler.py", line 93, in handle
    msg.populate(priority, address, rtr, data)
  File "/home/dieter/GIT/velbus-aio/velbusaio/messages/channel_name_part3.py", line 35, in populate
    self.needs_one_channel(channels)
  File "/home/dieter/GIT/velbus-aio/velbusaio/message.py", line 235, in needs_one_channel
    self.parser_error("needs exactly one bit set in channel byte")
  File "/home/dieter/GIT/velbus-aio/velbusaio/message.py", line 134, in parser_error
    raise ParserError(self.__class__.__name__ + " " + message)
velbusaio.message.ParserError: ChannelNamePart3Message needs exactly one bit set in channel byte

Based on the previous output, I concluded that the DALI module has address 1, so I ignored this Traceback.

@dverhelst what module is at address=e0?

That would be a VMBGP2-2 but with outdated firmware which I'm updating right now ( it's the latest addition to the bus ). Same as C8 which has been updated to the latest firmware already.

@dverhelst can you run a new load_modules but let it run a lot longer, we do not have all the data in there

Here you go!
load_modules.out.txt

this looks great
@niobos i'll release a new version so you can make the PR in hass

For reference: https://github.com/home-assistant/core/pull/80510

@ dverhelst today a new RC was released for hass, would you be able to check it out?
to see how the vmbdali reacts?

@Cereal2nd , I ran a quick test from the dev-branch last Friday and all looked quite ok !
There was 'something' with the status of the lights sometimes not being reflected back, but I plan to test some more over the weekend.
I was very happy to see all the lights functioning well!

ok, then we close this ticket, if something else pops-up we can alwasy create a new one


Now, I just need to compare the two environments.

I have fixed python=3.8. Latest results:

run all: pytest tests - segfault
run core tests: pytest tests/core - regrid tests fail (?)

can be fixed by referencing .data in:

clisops/core/regrid.py:513: in grid_reformat
ds_ref = xr.Dataset(
- run only core subset tests: tests pass

The order the tests are run in seems to affect the result:

No segfault with:

pytest tests/core/test_average.py tests/core/test_regrid.py tests/core/test_subset.py tests/ops/test_average.py tests/ops/test_subset.py tests/ops/test_xarray_mean.py tests/ops/test_regrid.py tests/test_config.py tests/test_dataset_roll.py tests/test_file_namers.py tests/test_output_utils.py tests/test_roll.py tests/test_utils/test_dataset_utils.py

Segfault with:

pytest

Segfault with:

pytest tests/test_config.py tests/test_dataset_roll.py tests/test_file_namers.py tests/test_output_utils.py tests/test_roll.py tests/core/test_average.py tests/core/test_regrid.py tests/core/test_subset.py

and
pytest tests/test_config.py tests/test_dataset_roll.py tests/test_file_namers.py tests/test_output_utils.py tests/test_roll.py tests/core/test_subset.py

Does python -m pytest make any difference? No, it doesn't.

So, to summarise...
FAILS:
pytest tests/test_file_namers.py tests/core/test_subset.py

SUCCEEDS:
pytest tests/test_file_namers.py
pytest tests/core/test_subset.py
pytest tests/core/test_subset.py tests/test_file_namers.py

ASSUMED REASON:

an interaction is causing the seg fault, between the two test modules when run in this order:

tests/test_file_namers.py
tests/core/test_subset.py

@cehbrecht: please can you try to reproduce the problem outlined here. The first part of this issue explains how to set up the environment. Please confirm that you get a segfault that matches my experience above...
FAILS:
pytest tests/test_file_namers.py tests/core/test_subset.py

SUCCEEDS:
pytest tests/test_file_namers.py
pytest tests/core/test_subset.py
pytest tests/core/test_subset.py tests/test_file_namers.py

I can reproduce the segfault error in a Debian docker container. Well, it works on my mac ;)
On my dev branch I can avoid the segfault by removing the regrid import:
https://github.com/roocs/clisops/blob/996bf9e65748fcb35a912191a668abca2c8f4386/clisops/core/__init__.py#L1
and use the direct import of regrid:
https://github.com/roocs/clisops/blob/996bf9e65748fcb35a912191a668abca2c8f4386/clisops/ops/regrid.py#L7-L8
With these changes, the tests are working:
pytest tests
pytest tests/test_file_namers.py tests/core/test_subset.py

you can also switch subset and regrid imports:
https://github.com/roocs/clisops/blob/50a10941ad7bd1658ad565fb6840d7c23cdd3482/clisops/core/__init__.py#L1-L11

This final fix works, as long we use: pangeo-xesmf==0.6.0
But there are tests failing. Need to now look into these...

Hi @cehbrecht, I've made some progress on this stuff. Can you remember why we/you set the rules for which GitHub Actions are allowed to fail in this workflow:
https://github.com/roocs/clisops/blob/master/.github/workflows/main.yml#L26-L42

I think it is a copy+paste thing. There is no py37-xarray env in tox.ini. We can probably change the env py37-xarray to py37 and it should not fail:
https://github.com/roocs/clisops/blob/1280f278b5017d1e1d8c938b95b1dc25508398b1/.github/workflows/main.yml#L34-L36
ping @Zeitsperre

@Zeitsperre I think we got the different CI environments from xclim initially. We now have these various allowed_to_fail options. Do you think it is okay for any of these to fail? I have lost track whether some of them always will because of dependencies used in the subsetting by shape/polygon. Thanks

@cehbrecht There should be less of a likelihood of segmentation faults now that read operations are separated by worker and cache as of #345. Closing this.


missing scipy import

I cannot find a scipy import statement in the code base, though scipy is listed as an installation requirement. I used the following command:
find . -type f | xargs grep scipy | grep import

Hi,
It seems that you are perfectly correct, I've fixed it!
Thanks


File extension is outputted twice when saving a file created using DocumentManager.createUntitledDocument.

Prerequisites

[ ] Can you reproduce the problem with Debug -> Reload Without Extensions?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?
[x] Did you read the Troubleshooting guide?

Description
Brackets v1.9.0 added support for creating untitled files with extensions (along with the ability to change language types in untitled files). See Brackets 13086. When using DocumentManager.createUntitledDocument(count, ext);, everything works as expected until you save. The bug is that when you save an untitled file with an extension, the filename outputted into the save-as dialog treats the untitled documents extension as part of its filename and appends the extension again. In other words, the save-as dialogs filename has the extension twice.
Steps to Reproduce

Create an untitled document with an extension using the DocumentManager.

To expedite this step, you can use my plugin AnyTemplate (which creates an untitled file with an extension).

Save the file.

Expected behavior: The untitled files name should not include the extension twice.
Actual behavior: The untitled files name includes the extension twice when saving. It outputs like this: Untitled-1.js.js.
Versions

OS: macOS Sierra 10.12 (16A323)
Brackets: Release 1.9 build 1.9.0-17312 (release 189f6d39a)

This issue occurs on both Mac and Windows.

Hi @Grafluxe,
thanks for the detailed report! Would you be interested in fixing it in the Brackets core?

You're welcome @petetnt. I wouldn't mind fixing it. Anything I need to know that I can't find on the dev page?
I'm a huge fan of Brackets and use it daily.

Cool!
See the article How to hack on Brackets to get started with the Brackets codebase which should cover all the basics. If you have any questions, feel free to post them here! We also have a Slack channel for day-to-day communication. (You can join by sending a mail to<EMAIL_ADDRESS>with the subject line slack registration request specifying the email addresses you would like to register).
After you have a fix, send in a PR which we will then review and merge after any requested changes 🙌 !

Hey @petetnt,
I updated my local repo with the fix for this issue, but am running into a problem when attempting to unit test. PhantomJS is failing:
$ npm test

><EMAIL_ADDRESS>test /Users/lsilva/Desktop/adobe/brackets
> grunt test cla-check-pull

Running "eslint:grunt" (eslint) task

Running "eslint:src" (eslint) task

Running "eslint:test" (eslint) task

Running "jasmine:src" (jasmine) task
Testing jasmine specs via phantom

Running PhantomJS...ERROR
>> 0 [ '' ]
Warning: PhantomJS exited unexpectedly with exit code null. Use --force to continue.

Aborted due to warnings.
npm ERR! Test failed.  See above for more details.

How should I proceed?

@Grafluxe For running tests you can go to Debug->Run Tests, then under All tab search for DocumentManager and DocumentCommandHandlers and click on it. Since you are changing document manager and document command handler only, so there is no need to run any other tests.

Thanks @saurabh95. I just submitted a PR.
https://github.com/adobe/brackets/pull/13426

Great!


Make type_params optional everywhere

Codecov Report

Merging #432 (6203b60) into main (ecb71b5) will decrease coverage by 0.03%.
The diff coverage is 79.52%.

@@            Coverage Diff             @@
##             main     #432      +/-   ##
==========================================
- Coverage   80.19%   80.17%   -0.03%
==========================================
  Files          58       58
  Lines       20013    20048      +35
==========================================
+ Hits        16049    16073      +24
- Misses       3964     3975      +11

Impacted Files
Coverage Δ

crates/crochet_infer/src/util.rs
72.61% <46.15%> (-0.34%)
:arrow_down:

crates/crochet_infer/src/scheme.rs
93.84% <71.42%> (+0.55%)
:arrow_up:

crates/crochet_dts/src/parse_dts.rs
71.69% <72.72%> (+0.52%)
:arrow_up:

crates/crochet_ast/src/types/lam.rs
70.83% <75.00%> (-16.35%)
:arrow_down:

crates/crochet_infer/src/visitor.rs
48.61% <80.00%> (+1.38%)
:arrow_up:

crates/crochet_codegen/src/d_ts.rs
71.89% <81.81%> (-0.03%)
:arrow_down:

crates/crochet_infer/src/expand_type.rs
65.05% <83.33%> (ø)

crates/crochet_infer/src/infer_expr.rs
79.35% <85.00%> (-0.84%)
:arrow_down:

crates/crochet_ast/src/types/obj.rs
78.62% <100.00%> (-0.94%)
:arrow_down:

crates/crochet_dts/src/util.rs
90.57% <100.00%> (ø)

... and 13 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Mealob.com not bypassing

Domain
https://<IP_ADDRESS>/
Link
mealob.com/?id=VeryVeryVeryLongRandomIDHere
Version
0.2025
What browsers are you seeing the problem on?
Firefox
What OS are you seeing the problem on?
Windows
Anything else?
Version 0.2025 · Bypass definitions 0245857
pls fix it is not working on downloading links of https://<IP_ADDRESS>

Can you provide a working example link so that we can take a look?


Emoji Reactions

The idea is to have some emoji or thumbs up floating up from behind users avatar when that user presses the reaction key.
In yesterdays discussion we found that It would be great to have this feature as a kind of virtual nod of approval to the current speaker without having to interrupt him or wait for him to finish before giving him a feedback on what he is currently saying.
Something like this animation, but probably shorter and fading away:
https://www.youtube.com/watch?v=Mz04HQl7cTo&ab_channel=NadzSamson

I'm about to deploy emojis to chat and I think this might cover some of this use case. Feel free to reopen after trying if you still like a reaction thingy


Transparency of dashed/dotted lines not maintained in PDF

export_pdf does a great job of maintaining transparency for solid lines when exporting to PDF, but doesn't appear to work for dashed and dotted lines for some reason.
MWE:
imagesc(hadamard(64));
line(xlim, ylim, 'LineWidth', 10, 'LineStyle', '--', 'Color', [0 0 0 0.5]);
line(xlim, flip(ylim), 'LineWidth', 10, 'LineStyle', '-', 'Color', [0 0 0 0.5]);
export_fig('testfig.pdf');

Fixed


Run werewolf_game error

Hi, developers:
I run the latest version metagpt script examples/werewolf_game/start_game.py and got error as follows. How can I get this error repaired.
`2024-06-11 15:46:52.484 | ERROR    | metagpt.utils.common:wrapper:631 - Exception occurs, start to serialize the project, exp:
Traceback (most recent call last):
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 50, in call
result = await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/ext/werewolf/actions/common_actions.py", line 238, in run
rsp_json = log_and_parse_json(self.name, rsp)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
json.decoder.JSONDecodeError: Expecting value: line 1 column 73 (char 72)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/utils/common.py", line 640, in wrapper
return await func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/huangyichi/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/roles/role.py", line 550, in run
rsp = await self.react()
^^^^^^^^^^^^^^^^^^
tenacity.RetryError: RetryError[<Future at 0x138a0b510 state=finished raised JSONDecodeError>]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/huangyichi/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/utils/common.py", line 626, in wrapper
result = await func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/team.py", line 131, in run
await self.env.run()
Exception: Traceback (most recent call last):
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 50, in call
result = await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/ext/werewolf/actions/common_actions.py", line 238, in run
rsp_json = log_and_parse_json(self.name, rsp)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/ext/werewolf/actions/common_actions.py", line 18, in log_and_parse_json
rsp_json = json.loads(json_blocks[0])
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/init.py", line 346, in loads
return _default_decoder.decode(s)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 73 (char 72)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/utils/common.py", line 640, in wrapper
return await func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/roles/role.py", line 550, in run
rsp = await self.react()
^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/roles/role.py", line 519, in react
rsp = await self._react()
^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/roles/role.py", line 474, in _react
rsp = await self._act()
^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/ext/werewolf/roles/base_player.py", line 101, in _act
await Reflect().run(
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 88, in async_wrapped
return await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 47, in call
do = self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/init.py", line 326, in iter
raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x138a0b510 state=finished raised JSONDecodeError>]
Traceback (most recent call last):
File "/Users/Desktop/openai/metagpt/examples/werewolf_game/start_game.py", line 75, in
fire.Fire(main)
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 466, in _Fire
component, remaining_args = _CallAndUpdateTrace(
^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 681, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Desktop/openai/metagpt/examples/werewolf_game/start_game.py", line 60, in main
asyncio.run(
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 190, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/Users/Desktop/openai/metagpt/examples/werewolf_game/start_game.py", line 47, in start_game
await game.run(n_round=n_round)
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/utils/common.py", line 632, in wrapper
self.serialize()  # Team.serialize
^^^^^^^^^^^^^^^^
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/team.py", line 62, in serialize
write_json_file(team_info_path, serialized_data)
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/site-packages/metagpt/utils/common.py", line 581, in write_json_file
json.dump(data, fout, ensure_ascii=False, indent=indent, default=to_jsonable_python)
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/init.py", line 179, in dump
for chunk in iterable:
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/encoder.py", line 432, in _iterencode
yield from _iterencode_dict(o, _current_indent_level)
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/encoder.py", line 406, in _iterencode_dict
yield from chunks
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/encoder.py", line 406, in _iterencode_dict
yield from chunks
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/encoder.py", line 406, in _iterencode_dict
yield from chunks
[Previous line repeated 1 more time]
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/encoder.py", line 326, in _iterencode_list
yield from chunks
File "/Users/opt/anaconda3/envs/metagpt/lib/python3.11/json/encoder.py", line 439, in _iterencode
o = _default(o)
^^^^^^^^^^^
pydantic_core._pydantic_core.PydanticSerializationError: Unable to serialize unknown type: <class 'pydantic._internal._model_construction.ModelMetaclass'>`
I used the config/config2.yaml as follows:
llm:   api_type: "zhipuai"     model: "glm-4"    base_url: "https://open.bigmodel.cn/api/paas/v4/"     api_key: "XXXXX"   repair_llm_output: true

I have the same issue.

I have the same issue.

I suspect it's a problem with the LLM, as I'm not using the OpenAI model.

I have the same issue.

I suspect it's a problem with the LLM, as I'm not using the OpenAI model.

JSON output in Werewolf game is quite demanding. The OpenAI models have been specifically optimized for JSON, so they perform well. However, if you use non-OpenAI models , they are prone to outputting incorrect JSON formats, leading to JSONDecodeError.

maybe you can check the response of _achat_completion_stream.
If it retrurns 404, then maybe you can modify the parameters to fit your llm-api in metagpt/provider/ollama_api.py:
@register_provider(LLMType.OLLAMA) class OllamaLLM(BaseLLM):     """     Refs tohttps://github.com/jmorganca/ollama/blob/main/docs/api.md#generate-a-chat-completion`
"""
def __init__(self, config: LLMConfig):
    self.__init_ollama(config)
    self.client = GeneralAPIRequestor(base_url=config.base_url)
    self.config = config
    self.suffix_url = ""
    self.http_method = "post"
    self.use_system_prompt = False
    self.cost_manager = TokenCostManager()

`

Make sure your request API supports streaming.
For example, I used 'ollama' as an LLM. And my request endpoint should be http://localhost:11434/v1/chat/completions.

Then jumps to https://github.com/geekan/MetaGPT/issues/1340


Different effects from video

First off, this is incredible, I'm very impressed this can all be pushed so fast over the network - really nice work.
I have a similar yet different issue to the other post, video here: https://www.youtube.com/watch?v=KS-C76DlhUA
I can't quite place my finger on what's wrong, but it's flickering a lot through random colors, and doesn't "burst" out from the center as in the demo video. Is this correct? Or is my audio analysis thing misbehaving? It does seem to focus on the center rather than show a full range. I'm using "Loopback" for OSX for a virtual audio pipe, but it was the same when I tried with a microphone.
I tried the led.py test, and it mostly seemed fine .. RGB pixel travelling down the strip, albeit with some white flickrs before and after it.
Using NodeMCU12E, standard 30led/m WS2812B strip with external psu.
thanks!

so.. looking at the other person's issue, mine appears to be on the software side rather than hardware, with the colour values display not pulsing out to the edges.

so.. looking at the other person's issue, mine appears to be on the software side rather than hardware, with the colour values display not pulsing out to the edges.

Oh, sorry, i didn't realise that - just the default. Is this what the default should be showing then?

Oh, sorry, i didn't realise that - just the default. Is this what the default should be showing then?

Thanks for the feedback, it's great to see that people are using this project!
The default effect is the energy effect and as @joeybab3 mentioned you won't see the other effects unless you uncomment them in visualization.py.
I'm not very happy with this method of effect selection because it requires you restart Python every time you want to change the effect. I also didn't explain this in the README so I don't think you are the only person who is going to be confused by this.
Based on your feedback, I've pushed a new update (commit c725d39) which adds a ComboBox to the GUI window. With the latest version of the code, you can now change the effect while the visualization is running and without having to restart Python or comment/uncomment anything. The new update looks like this:

I'd like to add more more improvements to the GUI in the future. I think it would be great to have more features like the ability to adjust settings such as frequency range and decay constants. I want the project to be accessible to non-programmers as well as programmers, and having a decent GUI would be a good first step.

Thanks for the feedback, it's great to see that people are using this project!
The default effect is the energy effect and as @joeybab3 mentioned you won't see the other effects unless you uncomment them in visualization.py.
I'm not very happy with this method of effect selection because it requires you restart Python every time you want to change the effect. I also didn't explain this in the README so I don't think you are the only person who is going to be confused by this.
Based on your feedback, I've pushed a new update (commit c725d39) which adds a ComboBox to the GUI window. With the latest version of the code, you can now change the effect while the visualization is running and without having to restart Python or comment/uncomment anything. The new update looks like this:

I'd like to add more more improvements to the GUI in the future. I think it would be great to have more features like the ability to adjust settings such as frequency range and decay constants. I want the project to be accessible to non-programmers as well as programmers, and having a decent GUI would be a good first step.

Oh, wow, YES - that's awesome, thanks Scott!
I'll keep a close eye on this project, and thank you for giving me a reason to finish putting up strings of LEDs around every room ;)

Oh, wow, YES - that's awesome, thanks Scott!
I'll keep a close eye on this project, and thank you for giving me a reason to finish putting up strings of LEDs around every room ;)


Not good reconstructed image when using custom data

Hello, thank you for the awesome work!!:)
My Mip-NeRF 360 training results are not good.
Could you suggest what to do to get good results?
Current Experiment Method
Usage data

180 images sampled from a 1-minute video taken in a botanical garden
Repeatedly moving from side to side for about 5 steps, keeping the camera in the forward direction and shooting while changing only the camera height
Camera : iphone 12 pro
Example

Experiment method
Followed multinerf Readme Using your own data. part.
360.gin used.
(Does not modify code or config files)
Result

Attempts to solve

When visualizing the camera pose extracted by colmap, it was confirmed that the camera pose results were similar to my actual camera position.
Changed the Camera Model when running colmap or tried using "sequential" in Feature matching, but similar results
The result of changing near/far/forward_facing/batch size/render_camtype/render_dist_percentile in 360.gin is also not good.

I use my own raw data set for training, and the rendered image is not only blurred, but also very strange in color.
Is the "ColorMatrix2" parameter of the json file arranged in the wrong way? Or is the pose calculated by colmap（bash scripts/local_colmap_and_resize.sh ${DATA_DIR}） wrong?What is the problem?
the render image：

the origin image （rgb）（for see）：


suggest to handler the IOException

Suggest to handler the IOException on MapperAnnotationBuilder#loadXmlResource().
In my case, there is existed Mapper.xml files, but it is failure resolve the XML.
On the end, I got the error like "Mapped Statements collection does not contain value for....."

Hi @hank0chan , Thanks for your contribution. However i don't know that your fix is reasonable. At first, could you explain issue detail and a root cause that not found existed mapper xml file on your application ? If you cannot explain it, could you provide a repro project  and execution environment information ?

Hi @kazuki43zoo ,It could be my project got one problem during build jar. Please ignore this suggestion. This is my mistake, I am sorry

I've closed this PR. If there is problem, please reopen.


Integration of f3rm with NerfBridge

Hi, I'm working on a project called NerfBridge which does continuous NeRF training from a ROS image stream. I'm really excited about your work, and am hoping to integrate some of your code into my project to do live f3rm feature field training. I think for maintenance and compatibility reasons I would like to copy a few specific files from your code into my repository. Would that be okay with all of you? Obviously, I'd put references to your repo and paper at the top of the copied files as well as a citation in the README of NerfBridge and any papers that get published and use that code.
https://github.com/javieryu/nerf_bridge
Cheers,
Javier

Hi Javier,
Yes, that's fine. I've seen NerfBridge before, really cool work! Excited to see what can be done with live feature fields.
Will

Great! Will update you when we make progress on this!


[REG2.067] Issue 14556 - can't instantiate struct that has constructor and static array of enum

https://issues.dlang.org/show_bug.cgi?id=14556

Auto-merge toggled on


[AIRFLOW-2377] Improve Sendgrid sender support

Make sure you have checked all steps below.
JIRA

[X] My PR addresses the following [AIRFLOW-2377]

Description

[X] Here are some details about my PR, including screenshots of any UI changes:
Support for passing sender email and name as parameters

Tests

[X] My PR adds the following unit tests:
Additional unit test and fix of existing tests

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[X] In case of new functionality, my PR adds documentation that describes how to use it.

Code Quality

[X] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3266 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3266      +/-   ##
==========================================
- Coverage   75.78%   75.76%   -0.03%
==========================================
  Files         197      197
  Lines       14699    14699
==========================================
- Hits        11140    11137       -3
- Misses       3559     3562       +3

Impacted Files
Coverage Δ

airflow/jobs.py
82.56% <0%> (-0.27%)
:arrow_down:

Continue to review full report at Codecov.

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

Can you please verify again? It was developed and tested with Python 3 and tests on Travis pass. The log seems like the tests are running against code that doesn't have the change. Looking at your execution path, it might be importing from package library.

You're right. It works. My bad... +1


Usage of bluebird-retry with webpack

Hi,
I'm having an issue building with webpack using pogobuf because it relies on bluebird-retry which seems to make the app crash.
Here is the warning I got on my OS console:
WARNING in ./~/bluebird-retry/browser/bluebird-retry.js
Critical dependencies:
1:486-493 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
 @ ./~/bluebird-retry/browser/bluebird-retry.js 1:486-493

And the issue logged in my browser:
bluebird-retry.js:108Uncaught Error: Parse error at line 1: unexpected '<'

Any guess ?

It would not work in the browser anyway. Are you building webpack for electron?

I think this would be an issue for bluebird-retry, no?

Webpack is used to bundle files for browser, there's no need todo that for node.js

In any case I'm pretty sure this is bluebird-retry related and not pogobuf so I'll close this.

For anyone who comes across this issue. If you want to build pogobuf for electron using webpack, in your configuration you can add this to have it stop compiling these dependencies. You must deliver these dependencies to your user when packaging your binary instead.
  externals: [
    'pogobuf',
    'node-pogo-protos'
  ],

If you wanted to explicitly tell it to stop parsing bluebird-retry, you would do this instead, but I don't think that is what you want.
  module: {
    noParse: [
      /node_modules\/bluebird-retry\/browser\/bluebird-retry.js/
    ],

    loaders: [...]
  },

Why is the library only usable with node, and thus not to power a webapp directly?

If by webapp you're referring to a regular browser opening a website, that's not going to work due to same-origin policy. The app wouldn't be able to make any requests to Niantic's servers.
But if that's not an issue in your environment then I don't see why it shouldn't work in a web app as long as you have a suitable module loader since the library and all of its dependencies are completely pure JS.


Arabic Source (Rewayat Club)

Source name
Rewayat Club - نادي الروايات
Source link
https://rewayat.club/
Language
Arabic
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Duplicate of #78


credstash: add standalone Python application

Motivation for this change
I want to use the credstash command-line application, but credstash is currently only offered as a Python library.
In order for this to work, I needed to remove the copy of the library that's placed in $out/bin and marked executable during the install phase. Other than the patched shebang and executable bit, it's identical to the library that's installed to $out/lib/python3.7/site-packages.
Before postFixup has run wrapPythonPrograms, bin/ contains two Python files -- credstash and credstash.py -- where bin/credstash is the executable you'd expect a user to invoke from the command-line and bin/credstash.py contains the credstash module, which bin/credstash imports.
After wrapPythonPrograms has run, bin/credstash is a shell wrapper around the bin/.credstash-wrapped python entrypoint, and bin/credstash.py is shell wrapper around the bin/.credstash.py-wrapped python module. Invoking bin/credstash execs bin/.credstash-wrapped, which attempts to import the credstash module from bin/credstash.py (now a shell script), rather than either bin/.credstash.py-wrapped or lib/python3.7/site-packages/credstash.py.
This leads to an error:
$ credstash get mykey
Traceback (most recent call last):
  File "/nix/store/hk6yma716w6141lcdh509d6qyyi7zm0i-python3.7-credstash-1.15.0/bin/.credstash-wrapped", line 8, in <module>
    from credstash import main
  File "/nix/store/hk6yma716w6141lcdh509d6qyyi7zm0i-python3.7-credstash-1.15.0/bin/credstash.py", line 2
    export PATH='/nix/store/6lm4gi5iv8fbf1b1mm6g3gfnnv63f1gn-python3-3.7.1/bin:/nix/store/hk6yma716w6141lcdh509d6qyyi7zm0i-python3.7-credstash-1.15.0/bin:/nix/store/2n13gf1zdr39ir5dynxlkqndxgy36g08-python3.7-setuptools-40.4.3/bin:/nix/store/mhnqwpa4y1l81zi4cwx989i8h8z9g67l-python3.7-jmespath-0.9.0/bin:/nix/store/qc6q3a2nv4211wyh7q319v6zzd3ab6pc-python3.7-docutils-0.14/bin'${PATH:+':'}$PATH
              ^
SyntaxError: invalid syntax

I was able to resolve this by removing bin/credstash.py before the postFixup phase has a chance to wrap anything. Now the executable imports the library correctly:
(shell wrapper)
 bin/credstash
       │      (python executable)
       └─> bin/.credstash-wrapped
                  │                        (python library)
                  └─> lib/python3.7/site-packages/credstash.py

I tried using dontWrapPythonPrograms as an alternative solution, but that leads to a different error because runtime dependency lookups fail:
$ credstash get mykey
Traceback (most recent call last):
  File "/run/current-system/sw/bin/credstash", line 7, in <module>
    from credstash import main
  File "/nix/store/8rmldlvlv1z1xl7w02dy7f5qhkzdrg8z-python3.7-credstash-1.15.0/bin/credstash.py", line 26, in <module>
    import boto3
ModuleNotFoundError: No module named 'boto3'

Fixes #47751
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

What is not clear to me is why this is even in pythonPackages? Isn't this only ever used on the command line nd never via Python's import?

@dotlambda credstash can also be used via Python's import. We're currently using it at work in this way.

Same here. We have some internal tools that use the library to interact with credstash.


global: Reenable dynamic JSON-Schemas.

Problem:
Not all services have their JSON Schemas coming from files or one JSON Schema per type of PID.
However with the last modification enabling "multiple deposits per site" we started tying together endpoints and JSON Schemas.
Who needs it:
B2Share as it has only one endpoint but multiple JSON Schemas, one per community. The last changes should not impact B2Share for now as it does not use the UI, but this is a dangerous direction for us.

The schema is used only as default. You can always override the template. I don't see the problem here.

As we don't have specifications, code is the specifications.
Current code says that there is a deposit type and this type defines the JSON-Schemas.
If this is used in the REST API later, we can't derive the JSON-Schema from the provided metadata anymore. Thus it is not blocking us now as we don't use the UI, but it is a dangerous specification if extended to the REST API.
Maybe we could provide functions instead which would be in charge of retrieving the JSON-Schema. They would retrieve request.values.get('type') themselves.


Angular example stays at Loading

As shown in: https://plnkr.co/edit/wJM9InkTxdDn3GIVS4yy?p=preview

Thanks, I updated it to a stackblitz demo.


fix: upgrade to version 3.0.542

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign ccojocar
You can assign the PR to them by writing /assign @ccojocar in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test gsm

vault
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test gsm

vault
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test vault

gsm
9f9a494efbb8f98f21ab243f71a54311a321e70b
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


fix(deps): update all

This PR contains the following updates:

Package
Update
Change

aquasecurity/tfsec
minor
v1.20.0 -> v1.21.0

golangci/golangci-lint
minor
v1.45.2 -> v1.46.1

gruntwork-io/terragrunt
minor
v0.36.10 -> v0.37.0

Release Notes

aquasecurity/tfsec
v1.21.0
Compare Source
What's Changed

feat: Improved syntax highlighting via chroma in defsec by @liamg in https://github.com/aquasecurity/tfsec/pull/1724
feat: Add customisable code themes by @liamg in https://github.com/aquasecurity/tfsec/pull/1725

Full Changelog: https://github.com/aquasecurity/tfsec/compare/v1.20.2...v1.21.0
v1.20.2
Compare Source
What's Changed

chore(deps): bump docker/login-action from 1 to 2 by @dependabot in https://github.com/aquasecurity/tfsec/pull/1720
fix(ignores): handle parameter based ignores in a foreach by @owenrumney in https://github.com/aquasecurity/tfsec/pull/1723

Full Changelog: https://github.com/aquasecurity/tfsec/compare/v1.20.1...v1.20.2
v1.20.1
Compare Source
What's Changed

chore: Update defsec to v0.54.0 by @liamg in https://github.com/aquasecurity/tfsec/pull/1715
fix(parsing): Symlink resolution fix by @owenrumney in https://github.com/aquasecurity/tfsec/pull/1722

Full Changelog: https://github.com/aquasecurity/tfsec/compare/v1.20.0...v1.20.1

golangci/golangci-lint
v1.46.1
Compare Source

updated linters:

execinquery: bump from v0.6.0 to v0.6.1

documentation:

add missing linters

v1.46.0
Compare Source

new linters:

execinquery: https://github.com/lufeee/execinquery
nonamedreturns: https://github.com/firefart/nonamedreturns
nosprintfhostport: https://github.com/stbenjam/no-sprintf-host-port
exhaustruct: https://github.com/GaijinEntertainment/go-exhaustruc

updated linters:

bidichk: from 0.2.2 to 0.2.3
deadcode: bump to HEAD
errchkjson: from 0.2.3 to 0.3.0
errname: from 0.1.5 to 0.1.6
go-critic: from 0.6.2 to 0.6.3
gocyclo: from 0.4.0 to 0.5.1
gofumpt from 0.3.0 to 0.3.1
gomoddirectives: from 0.2.2 to 0.2.3
gosec: from 2.10.0 to 2.11.0
honnef.co/go/tools: from 0.2.2to 0.3.1 (go1.18 support)
nilnil: from 0.1.0 to 0.1.1
nonamedreturns: bump from 1.0.0 to 1.0.1
predeclared: from 0.2.1 to 0.2.2
promlinter: bump to v0.2.0
revive: from 1.1.4 to 1.2.1
tenv: from 1.4.7 to 1.5.0
thelper: from 0.5.1 to 0.6.2
unused: fix false-positive
varnamelen: bump to v0.8.0
wrapcheck: from 2.5.0 to 2.6.1
exhaustivestruct: This linter is deprecated use exhaustruct instead.

documentation:

Update "Shell Completion" instruction on Linux
Update FAQ page

misc:

log: enable override coloring based on CLICOLOR and CLICOLOR_FORCE

gruntwork-io/terragrunt
v0.37.0
Compare Source
Updated CLI args, config attributes and blocks

remote_state [BACKWARD INCOMPATIBLE]

Description

Updated logic for handling remote_state to enforce what is defined in the block of config, the change affects default encryption settings, public access blocking, bucket policy (enforce SSL only), access logging, and versioning

Fixed behavior for enforcing EnforcedTLS to not overwrite already configured RootAccess policy

Migration guide

If is required to disable new behavior, can be defined config attribute disable_bucket_update=true in remote_state

Special thanks
Special thanks to the following users for their contribution!

@leonardobiffi

Related links

https://github.com/gruntwork-io/terragrunt/pull/2063

v0.36.11
Compare Source
Description
Upgraded go-getter dependency to 1.5.11 with CVE-2022-29810 fixes
Special thanks
Special thanks to @dependabot for their contribution!
Related links

https://github.com/gruntwork-io/terragrunt/pull/2095

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Testing with personal token - closing and will allow PR to be opened by a function ID user


failed call to cuInit: CUDA_ERROR_INVALID_DEVICE: invalid device ordinal

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution: Ubuntu 18.04
TensorFlow installed from (source or binary): pip install tensorflow-gpu==2.0.0-alpha0
TensorFlow version (use command below): 2.0.0-alpha0
Python version: 3.6.8
CUDA version: 10
GPU model and memory: GeForce GTX 1050 / 4Gb

Describe the current behavior
Tensorflow does not detect my GPU (it used to - I don't know what changed).
Code to reproduce the issue
import os
import tensorflow as tf

os.environ["CUDA_VISIBLE_DEVICES"] = "0"

a = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[2, 3], name='a')
b = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[3, 2], name='b')
c = tf.matmul(a, b)

print(c)

Output:
2019-05-24 10:16:30.726799: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2019-05-24 10:16:30.740369: I tensorflow/stream_executor/platform/default/dso_loader.cc:42] Successfully opened dynamic library libcuda.so.1
2019-05-24 10:16:30.777178: E tensorflow/stream_executor/cuda/cuda_driver.cc:318] failed call to cuInit: CUDA_ERROR_INVALID_DEVICE: invalid device ordinal
2019-05-24 10:16:30.777232: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:166] retrieving CUDA diagnostic information for host: joao-Yoga730
2019-05-24 10:16:30.777242: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:173] hostname: joao-Yoga730
2019-05-24 10:16:30.777331: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:197] libcuda reported version is: 410.48.0
2019-05-24 10:16:30.777364: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:201] kernel reported version is: 410.48.0
2019-05-24 10:16:30.777371: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:308] kernel version seems to match DSO: 410.48.0
2019-05-24 10:16:30.799754: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-05-24 10:16:30.801312: I tensorflow/compiler/xla/service/service.cc:162] XLA service 0x55e937b11800 executing computations on platform Host. Devices:
2019-05-24 10:16:30.801384: I tensorflow/compiler/xla/service/service.cc:169]   StreamExecutor device (0): <undefined>, <undefined>
tf.Tensor(
[[22. 28.]
 [49. 64.]], shape=(2, 2), dtype=float32)

Process finished with exit code 0

Other info / logs
nvidia-smi
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.48                 Driver Version: 410.48                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1050    Off  | 00000000:3B:00.0 Off |                  N/A |
| N/A   52C    P0    N/A /  N/A |    509MiB /  4042MiB |     33%      Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID   Type   Process name                             Usage      |
|=============================================================================|
|    0      1474      G   /usr/lib/xorg/Xorg                           301MiB |
|    0      1650      G   /usr/bin/gnome-shell                         148MiB |
|    0      2107      G   ...uest-channel-token=16113907172495644879    56MiB |
|    0      4229      G   /snap/pycharm-community/128/jre64/bin/java     2MiB |
+-----------------------------------------------------------------------------+

p.s. I have tried doing sudo apt install nvidia-modprobe. It didn't work.

I have verified with TensorFlow : 2.0.0-alpha0, GPU : Tesla T4  and Quadro K1200. It is working fine. Can you check with latest nightly build for 2.0 version and let us know if that resolves the error. Thanks!

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


Removes pk argument on model relations

Test schema becomes:
type BerryFruit {
  id: ID!
  name: String!
  nameUpper: String!
  nameLower: String!
}

type Group {
  id: ID!
  name: String!
  users: [User!]
}

type Query {
  user(pk: ID): User!
  users: [User!]!
  group(pk: ID): Group!
  groups: [Group!]!
  berries: [BerryFruit!]!
}

type User {
  id: ID!
  name: String!
  group: Group
}

Solves #40

I agree with you that it does not make sense to have pk filtering with foreign key or one to one relation.
Thanks for your contribution.


Fix off-by-one error in cron extensions evaluation of DOW

weekdays are being evaluated as 2-6 rather than 1-5.

Thanks for both finding this and providing the fix. It will roll into the 2.8.1 release sometime soon.

No trouble, I'm proud I could contribute something useful, it's my first
github pull request!
There's another issue with the cron, but I don't have to fix it to
accomplish my immediate sprint goals, so I'll put it off.
I don't have a deep experience with cron expressions, either, so maybe I'm
wrong. But the expression */15 * * * *  (every fifteen minutes every day)
throws an exception, and 0/15 * * * *  comes out as "daily at midnight,
repeat every *hour *for 23 hours" instead of every fifteen minutes.
Currently, I don't need anything more frequent than daily, so I can't put
the time in to fix it right now, but I'll make a issue for it to track it,
and if I can get to it in this project I will (I probably will :))
Regards,
Michael

On Tue, Mar 13, 2018 at 11:41 AM, David Hall<EMAIL_ADDRESS>wrote:

Thanks for both finding this and providing the fix. It will roll into the
2.8.1 release sometime soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dahall/TaskScheduler/pull/60#issuecomment-372710825,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKUxj7NZDbRHWCuWPKC2Qs_-P3eN0Eyks5td-irgaJpZM4So3dT
.


Only running at ~60fps

Please follow the general troubleshooting steps first:

[x] I carefully followed the instructions in the README and completed successfully the setup wizard.
[x] I read the ALVR Wikis here and here

Bug reports:
Applications are only running at ~60fps, despite ALVR being set to 90fps. I have it set to h264@100mbit/s using UDP as a transport although the issue still occurs in every configuration (that I've tried).
SteamVR shows the following:

logcat returns the following:
...
07-01 17:30:33.672  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121847, Received 121850
07-01 17:30:33.686  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:33.687  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:33.687  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:33.695  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121851, Received 121856
07-01 17:30:33.715  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121857, Received 121861
07-01 17:30:33.732  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121862, Received 121867
07-01 17:30:33.753  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121868, Received 121873
07-01 17:30:33.771  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121874, Received 121877
07-01 17:30:33.789  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121878, Received 121882
07-01 17:30:33.805  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121883, Received 121888
07-01 17:30:33.823  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121889, Received 121892
07-01 17:30:33.844  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121893, Received 121897
07-01 17:30:33.863  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121898, Received 121902
07-01 17:30:33.879  6968  7724 I VrApi   : FPS=55/90,Prd=68ms,Tear=0,Early=4,Stale=38,VSnc=1,Lat=1,Fov=0,CPU4/GPU=2/2,1171/441MHz,OC=FF,TA=0/70/0,SP=N/F/N,Mem=1353MHz,Free=1199MB,PLS=0,Temp=29.7C/0.0C,TW=1.51ms,App=1.61ms,GD=0.00ms,CPU&GPU=20.21ms,LCnt=1,GPU%=0.24,CPU%=0.11(W0.11),DSF=1.00
07-01 17:30:33.885  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121903, Received 121907
07-01 17:30:33.887  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:33.887  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:33.887  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:33.904  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121908, Received 121912
07-01 17:30:33.925  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121913, Received 121918
07-01 17:30:33.943  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121919, Received 121923
07-01 17:30:33.963  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121924, Received 121929
07-01 17:30:33.981  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121930, Received 121934
07-01 17:30:33.999  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121935, Received 121939
07-01 17:30:34.012   714  1031 D soundtrigger: audio_extn_sound_trigger_get_parameters input string<snd_device_in=>
07-01 17:30:34.012   734   734 I hash_map_utils: key: 'snd_device_in' value: ''
07-01 17:30:34.013   714  1031 D soundtrigger: audio_extn_sound_trigger_get_parameters input string<snd_device_out=>
07-01 17:30:34.013   734   734 I hash_map_utils: key: 'snd_device_out' value: ''
07-01 17:30:34.015  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121940, Received 121944
07-01 17:30:34.033  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121945, Received 121949
07-01 17:30:34.049  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121950, Received 121954
07-01 17:30:34.065  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121955, Received 121958
07-01 17:30:34.083  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121959, Received 121962
07-01 17:30:34.088  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.088  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:34.088  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.097  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121963, Received 121967
07-01 17:30:34.115  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121968, Received 121971
07-01 17:30:34.131  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121972, Received 121976
07-01 17:30:34.150  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121977, Received 121980
07-01 17:30:34.167  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121981, Received 121984
07-01 17:30:34.185  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121985, Received 121990
07-01 17:30:34.204  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121991, Received 121994
07-01 17:30:34.226  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 121995, Received 121999
07-01 17:30:34.244  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122000, Received 122004
07-01 17:30:34.260  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122005, Received 122010
07-01 17:30:34.275  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122011, Received 122014
07-01 17:30:34.288  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.289  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:34.289  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.294  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122015, Received 122019
07-01 17:30:34.312  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122020, Received 122023
07-01 17:30:34.333  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122024, Received 122028
07-01 17:30:34.354  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122029, Received 122031
07-01 17:30:34.375  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122032, Received 122039
07-01 17:30:34.395  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122040, Received 122045
07-01 17:30:34.415  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122046, Received 122050
07-01 17:30:34.431  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122051, Received 122056
07-01 17:30:34.453  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122057, Received 122061
07-01 17:30:34.471  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122062, Received 122066
07-01 17:30:34.487  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122067, Received 122071
07-01 17:30:34.489  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.489  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:34.489  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.504  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122072, Received 122076
07-01 17:30:34.520  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122077, Received 122081
07-01 17:30:34.536   830  7706 I [CT]    : CONSTELLATION: R: Detected IMU motion => Leaving static state.
07-01 17:30:34.537  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122082, Received 122086
07-01 17:30:34.544   830  7706 I [CT]    : Behavior:AtRest: [Left] deactivated
07-01 17:30:34.544   830  7706 I [CT]    : ControllerMotionModel: [Left] t = 10.972s, behavior transition: AtRest -> None
07-01 17:30:34.548   830  7706 D TrackingService: [HANDTRACKING] Controller 8076a674737945d7 in hand: Y, valid: Y
07-01 17:30:34.557  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122087, Received 122090
07-01 17:30:34.574  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122091, Received 122094
07-01 17:30:34.581  6968  7784 I ALVR Native: Sending timesync.
07-01 17:30:34.590  6968  7784 I ALVR Native: TimeSync: server - client = -3599392369 us RTT = 8770 us
07-01 17:30:34.595  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122095, Received 122099
07-01 17:30:34.613  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122100, Received 122104
07-01 17:30:34.635  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122105, Received 122110
07-01 17:30:34.650  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122111, Received 122115
07-01 17:30:34.666  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122116, Received 122120
07-01 17:30:34.682  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122121, Received 122125
07-01 17:30:34.689  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.689  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:34.689  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.700  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122126, Received 122129
07-01 17:30:34.721  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122130, Received 122133
07-01 17:30:34.743  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122134, Received 122139
07-01 17:30:34.757  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122140, Received 122144
07-01 17:30:34.773  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122145, Received 122149
07-01 17:30:34.794  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122150, Received 122154
07-01 17:30:34.812  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122155, Received 122158
07-01 17:30:34.832  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122159, Received 122163
07-01 17:30:34.854  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122164, Received 122168
07-01 17:30:34.868  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122169, Received 122174
07-01 17:30:34.882  6968  7724 I VrApi   : FPS=53/90,Prd=68ms,Tear=0,Early=2,Stale=53,VSnc=1,Lat=1,Fov=0,CPU4/GPU=2/2,1171/441MHz,OC=FF,TA=0/70/0,SP=N/F/N,Mem=1353MHz,Free=1207MB,PLS=0,Temp=29.7C/0.0C,TW=1.55ms,App=1.62ms,GD=0.00ms,CPU&GPU=20.81ms,LCnt=1,GPU%=0.24,CPU%=0.18(W0.27),DSF=1.00
07-01 17:30:34.882  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122175, Received 122179
07-01 17:30:34.886  2647  3077 D [OAO] VrNotificationFeedManager: Notification feed fetch success callback, scheduling next feed call now.
07-01 17:30:34.890  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.890  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:34.890  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:34.901  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122180, Received 122183
07-01 17:30:34.919  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122184, Received 122188
07-01 17:30:34.936  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122189, Received 122193
07-01 17:30:34.956  1503  2748 I [CT]    : MIXEDREALITY: MrServiceView: renderIteration: (every 10 seconds), screen is: ON, PT is: OFF, ID is: OFF
07-01 17:30:34.956  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122194, Received 122198
07-01 17:30:34.971  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122199, Received 122202
07-01 17:30:34.991  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122203, Received 122207
07-01 17:30:35.013  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122208, Received 122212
07-01 17:30:35.032  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122213, Received 122217
07-01 17:30:35.052  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122218, Received 122222
07-01 17:30:35.062  6968  7784 I ALVR Native: Got frame=7 33, Codec=0
07-01 17:30:35.074  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122223, Received 122228
07-01 17:30:35.087  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122229, Received 122233
07-01 17:30:35.090  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:35.090  2486  2830 I chatty  : uid=10069(com.oculus.guardian) GuardianSystem identical 2 lines
07-01 17:30:35.090  2486  2830 E [CT]    : SpatialAnchorPipeline: checkStateEq:getActiveGuardian Called in an invalid state. 1
07-01 17:30:35.104  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122234, Received 122238
07-01 17:30:35.125  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122239, Received 122242
07-01 17:30:35.140   830  7706 I [CT]    : CONSTELLATION: R: Detected static IMU, no button event and has tracked position => Applying constant controller pose.
07-01 17:30:35.145  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122243, Received 122247
07-01 17:30:35.164  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122248, Received 122253
07-01 17:30:35.182   830  7706 I [CT]    : Behavior:AtRest: [Left] activated
07-01 17:30:35.182   830  7706 I [CT]    : ControllerMotionModel: [Left] t = 11.611s, behavior transition: None -> AtRest
07-01 17:30:35.183  6968  6990 W VrApi   : ovr_SubmitFrameInternal: FrameIndex discontinuity: Expected 122254, Received 122258

Environement
CPU: i7 4790k
GPU: GTX 970
Windows Version: 21H1 (OS Build: 19043.928)
SteamVR Version: 1.17.16
ALVR Version: 15.2.1
WiFi: 802.11ac

Switching to h265 and foveated rendering gets it up to 70fps. It's definitely not a bandwidth problem since air link has no problem with a fixed 150mbit/s

Can you show the stats graph and logs in the dashboard?

try turn off vsync in game setting

Your encoder is probably overloaded, try lowering the resolution or increasing foveated encoding strength

Your encoder is probably overloaded, try lowering the resolution or increasing foveated encoding strength

@sctanf increasing the foveated rendering strength fixes it, although interestingly enough reducing the resolution to 75% has no affect.


add collection

add collection

move attributes inside meta object

please add collection

attributes go inside of meta, also delete extra meta.json1

please add collection

delete extra file


Add support for escaping all request variables

Hi 👋 .
First of all, thanks for this plugin. It saved me quite a bit of research time 👍
The proposed changes are relatively simple. I introduced a couple of macros to reduce the boilerplate and defined logchunks for all remaining request variables. I think the latter is quite useful since pretty much all of the request variables can be set to arbitrary values by clients, e.g. curl -X 'F"OO' ....

Hi @iborko and @tlevani. Any interest in merging this?

Hi @neuroid, thank you for your contribution and sorry about a late reply. It's been a really busy time for both me and @iborko. We've seen the PR and yes, we are definitely interested in merging this as at a first glance it looks like a good and reasonable improvement, but we must find the time to test it out before merging. If I'm being realistic, this probably won't happen in September, but we will try to make it happen as soon as possible.

I've checked the code, tried it, tested it on some examples, and everything looks great! I'll merge it.


Proposal to change the @uniqueItems protocol tests

I see @uniqueItems protocol tests have been restored: https://github.com/awslabs/smithy/issues/1541.
Currently the tests look like:
https://github.com/awslabs/smithy/blob/b2b952a4b6d9f77f4c3dc143b9ad5abdd37c2544/smithy-aws-protocol-tests/model/restJson1/validation/malformed-uniqueItems.smithy#L32-L61
Previously, tests reflected input values, which was beneficial for debugging, but I recognize may result to some  (not me) to have security implications.
https://github.com/awslabs/smithy/blob/a7a16dfd13426f712934108f46cce3a3bb9d61b4/smithy-aws-protocol-tests/model/restJson1/malformedRequests/malformed-uniqueitems.smithy#L37-L58
The previous format had downsides though:

The elements may be big (complex structures); smithy-typescript truncates them. The caller might thus not even get to see the repeated elements.
The caller does not know how many times each duplicate element occurred.
The caller does not know in which positions each duplicate element occurred.

I think a better error message is to just return the indices of the duplicate elements: so, the list:
["a", "b", "a", "b", "c"]

Would return:
[0, 1, 2, 3]

An even better representation would be to return groups of indices (with size >= 2), one per equivalence class:
[[0, 2], [1, 3]]

However, this latter representation comes at a non-negligible (?) performance cost, namely, the allocation of one vector per equivalence class. Judging by how many clients are really interested in parsing these (none?), perhaps it's sufficient to just return the "flattened" indices.

I had lost track of #1541 and forgot to upstream the protocol tests I added in smithy-rs, which return the indices of the repeated elements.

Without the actual values in the error message, returning indices doesn't seem that useful IMO. This ["a", "b", "a", "b", "c"] yielding [0, 1, 2, 3] implies you have to backtrack to previous positions after reading. I'd expect it to yield just the indices that were detected to duplicate previous indices [2, 3] (e.g., create a set, iterate over the list and add elements to the set, if the element already exists in the set it gets added to the conflicting indices list).

I had lost track of https://github.com/smithy-lang/smithy/issues/1541 and forgot to upstream the protocol tests I added in smithy-rs, which return the indices of the repeated elements.

If you want to upstream your changes, that sounds good to me, though I'm curious about your thoughts on [0, 1, 2, 3] vs [2, 3]. Divergent protocol tests across implementations is something we should avoid.

though I'm curious about your thoughts on [0, 1, 2, 3] vs [2, 3]

Personally I think the most useful representation is returning groups of indices: [[0, 2], [1, 3]].

Thinking more about this, and I think the simple approach of just saying that the list wasn’t unique is enough for the error message. Today it says: Member must have unique values. It’s simple, it’s informative enough to know what validation failed, it doesn’t echo values, and it’s trivial to implement.
Requiring the error message to indicate anything other than that the list contains non-unique values could have far reaching consequences on how this implemented.  I also think sets and unique items was a misfeature, so I don’t want implementations having to write complex validation for it.

I don't think implementing any of the proposals suggested above entails any of these though. We just need to decide on a format.
Implementation of unique items involves a sorted vector or a set/map as a data structure. Reporting duplicate indices does not involve a rearchitecture, is trivial enough, and should not noticeably affect performance.


fix: ros-melodic-cpu paramiko fix and protobuf

Fixes to melodic CPU to create a docker image see #14
Paramiko needs libffi6 and libffi-dev to install
Removed the pip < 21 dependency because today there is no version less than 22
Added Protobuf <= 3.17.3 the last version with PYthon 2.7 support
Note: there is no CD/CI test so hard to tell if this works
Also recommend you create a turlucode account on docker hub and link and push to it

we are moving to v3 which is a new tool


Update use-log-compaction.md

Remove stale information.

#sign-off
Kasun is the PM for Event Hubs


Adding CodeSimplifier to code generation process

#Updated:

(Commit 1) autorest.gen.cmd to call CodeSimplifier.exe after using AutoRest.

Adding:

(Commit 2) CodeSimplifier src, which takes a folder of .cs files and uses Roslyn to reduce fully qualified names when possible

Most relevant: Program.cs

(Commit 3) CodeSimplifier.exe in tools folder

For some reason, Github isn't expanding all of the diffs for some reason. Check out https://github.com/tbombach/azure-sdk-for-net/tree/code-simplifier/tools/CodeSimplifier/src/CodeSimplifier to browse the files in my fork

Hi @tbombach, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (tbombach). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@tbombach  Thanks!  What is the rationale behind checking in the binaries rather than building as part of building the repo?  Also, can you clarify if current generate.cmd files would not work to regenerate code, and what modifications need to be made to allow correct generation (I believe this is just updeting the autorest version).  Can we document the change in the README>md for the repo.

@markcowl Thanks for the feedback! I added some steps to Readme.md, that explain how using generate.cmd will result in simplified names in generated code. Current generate.cmd files will continue to work for code, and I've updated the instructions to include which nightly AutoRest they should use to get the full benefit of name reduction.
As for checking in the CodeSimplifier binary, here's my rationale:
If we want the CodeSimplifier project to be built on-demand, we would have to add a msbuild step to autorest.gen.cmd (since build.proj only builds during a PR, not when an author is generating their client code). I think it's preferable that autorest.gen.cmd just uses the executable, rather than doing a project build every time the client needs to be regenerated. The tradeoff is that any changes to the CodeSimplifier src also require updating the binary as an extra step. I'm open to either way, but I'd lean towards only rebuilding the binary when we need CodeSimplifier changes (which shouldn't be very often). If we're okay with that approach, I'll also add instructions for copying the executable for CodeSimplifier.

Closing this PR, since the changes will be made to AutoRest


Update rocksdb

Update from pingcap/rocksdb:release with two commits:
https://github.com/pingcap/rocksdb/commit/f38277da0dcf762056669a116bc3db327c7bc84a
https://github.com/pingcap/rocksdb/commit/ba20fcf0470ed84abccc57eff1ddcb3737ba4201

Please add description.

LGTM


[infra-proxy-service] Role API uniform response objects

:nut_and_bolt: Description: What code changed, and why?

Remove expanded run-list attributes from GetRole API.
Added GetRoleEnvironments API to fetch the associated role environments.
Added GetRoleExpandedRunlist API to fetch the expanded run list.

:chains: Related Resources
Fixes: https://github.com/chef/automate/issues/4893
:+1: Definition of Done

GetRole api not returning expaded runlist attribute.
Infra service added with two new API GetRoleEnvironments & GetRoleExapndedRunList APIs.

:athletic_shoe: How to Build and Test the Change

rebuild components/infra-proxy-service
rebuild components/automate-gateway

Steps to test:

To add data using 3rd internal steps https://github.com/chef/automate/blob/master/dev-docs/adding-data/adding_test_data.md#adding-data-to-infra-views
GetRole API

curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/roles/chef-load-role-499187700?pretty

{
  "name": "chef-load-role-499187700",
  "chef_type": "role",
  "description": "auto generated role",
  "default_attributes": "{}",
  "override_attributes": "{}",
  "json_class": "Chef::Role",
  "run_list": [
    "recipe[audit::default]",
    "recipe[chef-client::default]"
  ]
}

API to fetch Role environments

curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/roles/chef-load-role-499187700/environments?pretty

{
  "environments": [
    "_default"
  ]
}

API to get the expanded run list based on environment

curl -sSkH "api-token: $(get_admin_token)" https://a2-dev.test/api/v0/infra/servers/chef-server-dev-test/orgs/chef-org-dev/roles/chef-load-role-499187700/runlist/_default?pretty
{
  "id": "_default",
  "run_list": [
    {
      "type": "recipe",
      "name": "audit::default",
      "version": "",
      "skipped": false,
      "position": 0,
      "error": "",
      "children": [
      ]
    },
    {
      "type": "recipe",
      "name": "chef-client::default",
      "version": "",
      "skipped": false,
      "position": 0,
      "error": "",
      "children": [
      ]
    }
  ]
}

:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[x] Tests added/updated?
[ ] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

In the "How to Build and Test the Change" section, you specify the role: chef-load-role-499187700, which does not exist for me when i followed the instructions.. I used one that did exist: chef-load-role-663568800 and was able to see data in the same structure as you have listed

Please resolve conflicts before merge.


Add team to segment creation API

#1587  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nick-statsig and the rest of your teammates on  Graphite

🚀 Deployed on https://664682a05b0c791bf63265a8--cozy-fox-0defec.netlify.app


add maven to requirements

Hey,
I noticed that I had to install maven for the theme build to work. Thought it might be a good hint in the docs.

Thank you! I messed up the readme.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.10.26 to before v5.10.43",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1c20e9040f49687ba2ccc2ffd4411351a6c2ebff",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0b2a990e5d2f76d020cb840c456e6ec5f0c27530"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "1c20e9040f49687ba2ccc2ffd4411351a6c2ebff",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "0b2a990e5d2f76d020cb840c456e6ec5f0c27530",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "io_uring: fix link timeout refs\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.43 by commit 0b2a990e5d2f76d020cb840c456e6ec5f0c27530, it was introduced in version v5.10.26 by commit 1c20e9040f49687ba2ccc2ffd4411351a6c2ebff. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000770


list() and create() calls fail in Node.js with ReferenceError: fetch is not defined

Expected Behavior
Tableland calls ( list and create) should successfully execute in nodejs
Actual Behavior
Tableland calls (list and create) fail with the error ReferenceError: fetch is not defined
Steps to Reproduce the Problem

setup nodejs app
npm i @tableland/sdk
implement https://docs.tableland.xyz/javascript-sdk for Node.js(require)

Specifications

Version: 3.0.0
Platform: nodejs on windows

My workaround
Fetch is not natively supported in Node.js as such it fails with reference error.
I added node-fetch module globally  to index.js
const fetch = require("node-fetch");

if (!globalThis.fetch) {
    globalThis.fetch = fetch;
}

@narteysarso thanks for posting.  node.js >= 16.5  does support fetch natively, but you may need to use the --experimental-fetch flag.
If you want to use an older version of node.js your workaround should work well


Status: Network error: Not Found

I had enabled a public link on the webUI so a friend could try it, now, even after disabling the public link configs, krita plugin can't find my webui server
Steps to reproduce the behavior:

add --listen to the webui-user.sh
change the line in webui.py to "share=true"
Utilize the public link
revert changes
See error

as seen here the server is running with all changes reverted, but the plugin does not connect
https://i.imgur.com/KlXCtuP.png
Desktop (please complete the following information):

OS: Linux Endeavour OS
Commit hash: 98947d173e3f1667eba29c904f681047dea9de90

Its a separate issue, likely as the extension auto-updated while you were switching back. See #51, but in short, you have to update AUTOMATIC1111's webUI.

ok ill be sure to do that then


LocalHost support gone?

Hi, since a recent update (the second to last most recent one I believe. I have lost the functionality to open directly into localhost on my browser. I have localhost ticked in the settings and have my path set to what it was beforehand but it never works.
Any fixes for this? It's useless to me right now.

How to View from local host?
Maintain "proj.json" file in the root directory of the project root folder. The file name can be configured from settings, but has to be in the root folder.
Here is sample structure of the file
{
"localhost": {
"url": "http://localhost:8000",
"folder": "C:/Users/admin/myproj/public"
}
}
There are 2 parameters:
url: This is base url against which the file path will be shown. Just maintaining url would make the file path being added to end of the maintained url.
folder: folder directory will be compared with the path of the file being displayed and will be replaced for eg. in the above case if you view a file under the root directory
/public/view/hello.html
would be shown as
http://localhost:8000/view/hello.html
This can be maintained differently for each project under each project's root directory.


Stabilize simplest possible driver

This is my suggestion for how to implements #12. What do you think? Sorry if I'm rushing ahead before you even commented on the issue. I just wanted to see how the API could turn out and then I felt I should share what I had tested out.
At the time of posting this PR it also contains the commits from #11. But if that PR is merged first this can be rebased.

Great. I'll look into it when I have the time. Likely not today.

Fixed.

I spoke too soon :sweat_smile: Now I fixed it for all features I did not test locally :P


Quick Toggle Filters

Right now, there is an option in the context menu for schemas, tables, etc, an option to clear the filter.  I think it would be much more helpful to be able to toggle the filter (like you can with the checkbox in the dialog box), so that you can quickly re-enable it later.  If I have a big filter set up, sometimes I need to turn it off for a minute to get to something I normally don't want to see, but I then want to turn the filter back on.  If I could do that without having to open the filter dialog, that would be nice.

In other words, "Clear Filter" should be "Disable (or Enable) Filter".

Filter toggle command will be added in the next version.
No keyboard shortcut is defined by default but you can assign one in preferences.


docs(readme): add a migration section in readme

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


K8s autoextend division by zero exception

Description
These two lines cause division by zero exception when the cpu or memory utilization is zero.
"cpu": {"used": cpu_mill, "total": cpu_mill / cpu_percentage,},
"memory": {"used": memory_usage, "total": memory_usage / memory_percentage},

Fixed in the PR closing the issue https://github.com/threefoldtech/js-sdk/issues/2455


Update references from Notary v2 to Notation

This repo is Notation library, we should update references from Notary v2 to Notation.
Here is a search Notary v2 in this repo https://github.com/notaryproject/notation-go/search?q="Notary+v2"&type=code
Fix the references in code only

I'll take this one.