Fix webhook errors and add params to NLB

What this PR does / why we need it:
Fix webhook errors and add params to NLB
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

e2e output
[SynchronizedAfterSuite] PASSED [1.081 seconds]
[SynchronizedAfterSuite]
/home/ubuntu/go/src/github.com/oracle/cluster-api-provider-oci/test/e2e/e2e_suite_test.go:261

  Timeline >>
  STEP: Tearing down the management cluster @ 07/31/24 09:52:26.354
  << Timeline
------------------------------

Ran 7 of 28 Specs in 2643.687 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 21 Skipped

unit test
$ make test
GOBIN=/home/ubuntu/go/src/github.com/oracle/cluster-api-provider-oci/hack/tools/bin ./scripts/go_install.sh sigs.k8s.io/controller-runtime/tools/setup-envtest setup-envtest v0.0.0-20230131074648-f5014c077fc3
kube-builder assets: /home/ubuntu/.local/share/kubebuilder-envtest/k8s/1.24.2-linux-amd64
KUBEBUILDER_ASSETS="/home/ubuntu/.local/share/kubebuilder-envtest/k8s/1.24.2-linux-amd64" go test -coverprofile=coverage.out ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/metrics	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	54.338s	coverage: 23.2% of statements
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	0.045s	coverage: 14.8% of statements
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	0.004s	coverage: 19.6% of statements
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	235.175s	coverage: 76.1% of statements
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	0.243s	coverage: 61.1% of statements
ok  	github.com/oracle/cluster-api-provider-oci/controllers	26.745s	coverage: 58.7% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	13.462s	coverage: 15.3% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	0.016s	coverage: 4.8% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	0.446s	coverage: 56.3% of statements
go tool cover -func=coverage.out -o coverage.txt
go tool cover -html=coverage.out -o coverage.html

[SynchronizedAfterSuite] PASSED [1.202 seconds]
[SynchronizedAfterSuite]
/home/ubuntu/go/src/github.com/oracle/cluster-api-provider-oci/test/e2e/e2e_suite_test.go:261

  Timeline >>
  STEP: Tearing down the management cluster @ 08/06/24 05:51:12.293
  << Timeline
------------------------------

Ran 7 of 28 Specs in 2519.750 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 21 Skipped

unit test
 make test
GOBIN=/home/ubuntu/go/src/github.com/oracle/cluster-api-provider-oci/hack/tools/bin ./scripts/go_install.sh sigs.k8s.io/controller-runtime/tools/setup-envtest setup-envtest v0.0.0-20230131074648-f5014c077fc3
kube-builder assets: /home/ubuntu/.local/share/kubebuilder-envtest/k8s/1.24.2-linux-amd64
KUBEBUILDER_ASSETS="/home/ubuntu/.local/share/kubebuilder-envtest/k8s/1.24.2-linux-amd64" go test -coverprofile=coverage.out ./...
?   	github.com/oracle/cluster-api-provider-oci	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/config	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/metrics	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta1	55.702s	coverage: 23.4% of statements
ok  	github.com/oracle/cluster-api-provider-oci/api/v1beta2	0.051s	coverage: 14.7% of statements
ok  	github.com/oracle/cluster-api-provider-oci/cloud/ociutil	0.009s	coverage: 19.6% of statements
?   	github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/feature	[no test files]
?   	github.com/oracle/cluster-api-provider-oci/version	[no test files]
ok  	github.com/oracle/cluster-api-provider-oci/cloud/scope	235.571s	coverage: 76.1% of statements
ok  	github.com/oracle/cluster-api-provider-oci/cloud/util	0.138s	coverage: 61.1% of statements
ok  	github.com/oracle/cluster-api-provider-oci/controllers	26.764s	coverage: 58.7% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1	13.672s	coverage: 15.3% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2	0.016s	coverage: 4.8% of statements
ok  	github.com/oracle/cluster-api-provider-oci/exp/controllers	0.706s	coverage: 56.3% of statements
go tool cover -func=coverage.out -o coverage.txt
go tool cover -html=coverage.out -o coverage.html


fix: suggest bootstrap start command from template

What kind of change does this PR introduce?
supersedes https://github.com/supabase/cli/pull/2130
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

5 of 20 (25.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 57.73%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/bootstrap/bootstrap.go
4
9
44.44%

cmd/bootstrap.go
0
10
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
6378

Relevant Lines:
11048

💛  - Coveralls


Is this maintained?

@dcuddeback looking to file an unmaintained advisory against this but wanted to check in with you first.
The reason this is important is that libusb is building against an old version of bit-sec that has an invalid Cargo.toml that will no longer be recognized as of Cargo 1.79, breaking builds of libusb and everyone who depends on it (see rust-lang/cargo#13824)
Looking over this repo,

The last commit or release was in 2016
Looking through the issues and PRs, I didn't see any activity from @dcuddeback since 2017 or so
The proposed fixes for the aforementioned bit-set issues have not gotten attention (#15, #45)

Since the start of 2022, the only public activity for @dcuddeback 's profile is two commits to their dotfiles.
There was some activity on libusb-sys in 2021 that was never released.

rusb is a maintained fork, and my nusb crate is a pure-Rust rewrite that uses OS APIs directly instead of linking the C libusb library.


Proximity doesn't work on wools

What's the actual problem?

 Not being killed.

I didn't know that


fix(modules): update node to v20

Resolves the issue of nodejs_16 being EOL upstream in nixpkgs
It seems while https://github.com/nextcloud/recognize/issues/985 is open and possibly being worked on upstream in recognize, a user can work around this via the built-in option to define node location (the use of path will obviously be fragile here to nixpkgs updates, but for now it's working in my testing)
Current settings as per: /settings/admin/recognize

Happy to wait for upstream to resolve this with said, if that is the preference :+1:

I thought there wasn't a release with that fix published, yet but if that already works it's lovely. One less patch I need to carry around.


Applying filters for a csv loaded dataset

Also, having the ObservationStackingFilter support a VectorObservationSpace, by concatenating the stacked frames to the current observation (i.e. an observation vector of size O, would become of size O * N, where N is the number of frames stacked together).

@galnov @shadiendrawis Could you PTAL?


Changing robot to an center articulated four wheeled robot

Hi there Reinis, thankyou so much for writing such a complete deep learning ROS system, it was pretty fun to watch the pioneer3dx robot learn how to navigate, then come back a day later and it was happily finding its goal, so cool.
So, being inspired by that, I thought I would try to load my robot into the sim, which for the most part I have (see below), but I need to tweak a few things in your DRL code but I'm not sure quite how. Firstly my robot interprets angular velocity as steering angle (like TEB local planner cmd_angle_instead_rotvel, will this effect things much? Also steering is limited +-0.5rad. Also my robot can drive backwards and I cant quite find the right place allow this.
How would all these changes effect the actor and critic weights and so on? Also I note that min_laser feeds into the rewards as well, but my robot is a rectangle, so a radius value might not work that well, maybe? Again, thanks heaps.

Hi,

You should be able to use steering angle in principle. The TD3 code does not change, you should just change the execution command in the env file. The TD3 architecture is not tied to how the action is executed and it does not know what action values actually mean.
The actions are capped to ranges here: https://github.com/reiniscimurs/DRL-robot-navigation/blob/main/TD3/train_velodyne_td3.py#L344-L345
For backwards driving you probably need to use different sensor FOV. The current implementation is hardcoded to 180 degree view in the env file. But you can update this as you want.
For actor/critic weights short answer is - I don't know. I have not tried to train such robots and do not have insights there. Feel free to try out different parameters. I think at least in theory it all should work.
You could try updating min_laser based reward function. But if you are still using collision based on a single min_laser value, I think it would be unnecessary. What this reward enforces is for the robot to keep larger distance from obstacles. And even in your case it quite easily be a circle.

Hi there Reinis, sorry for the later reply to a closed topic. I'm not even sure I'm meant to post to a closed topic. But I'll keep it short just in case I'm not meant to post here.
I have been trying random things with just about every part of the TD3 code since posting my OG question to make it work with my robot geometry and none of my changes result in convergence. I wont dive into the details until I hear from you just in case I'm meant to start a new issue before hand. Thanks again, cheers.

Hi,
I do not think I have anything to add here that I did not mention in the comment above. Feel free to open a new issue and provide all the information, but please use the template when submitting the issue.


Add edgeCollections and vertexCollections traversal options.

Document the recently added vertexCollections and edgeCollections restrictions for traversal options.

@danielhlarkin
I created anonymous graph A/1 --[x/?]--> B/2 --[y/?]--> C/3 to see what happens if you restrict the edge collections using the new option in addition to specifying the edge collection set.
FOR v,e,p IN 0..10 OUTBOUND "A/1" x, y
OPTIONS { edgeCollections: ["x"], vertexCollections: ["A","B","C"] }
RETURN v._key

Looks like the option can be used to further restrict the traversal, which is fine. Just something we might want to document.
Something I noticed in the query explain:
Traversals on graphs:
 Id  Depth  Vertex collections  Edge collections  Options                                                            Filter / Prune Conditions
 2   0..10                      x                 uniqueVertices: none, uniqueEdges: path, vertexCollections: A,B,C

There are columns for vertex collections and edge collections, but only the edge collection "x" is listed the latter. The vertex collections are listed in the options column instead. Shouldn't it be like this?
Traversals on graphs:
 Id  Depth  Vertex collections  Edge collections  Options                                  Filter / Prune Conditions
 2   0..10  A,B,C               x                 uniqueVertices: none, uniqueEdges: path


kube::codegen::gen_helpers errors out with 'fatal: Invalid path' error

When I run the following code:
source kube_codegen.sh

kube::codegen::gen_helpers \
    --input-pkg-root <repo_name>/pkg/apis \
    --output-base "<base_directory>" \
    --boilerplate "./examples/hack/boilerplate.go.txt"

I get the following error:

fatal: Invalid path '<base_directory>/<repo_name>/pkg/apis/**': No such file or directory

I made sure that the directory exists and contains files that are annotated with // +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object
I tried crafting the git grep by hand. That worked, it might be something in the way of how you call git grep.
I tried varying the path but that didn't do anything.
I am running in a docker container on golang:1.20.4-buster
git version is 2.20.1
Am I doing something wrong or is this a bug?

I believe I've figured it out.
It's all in the paths.
You can use the sample controller as an example.
By digging around this part of the script you will realize that the path where the codegen will run depends on the parameters you set as --input-pkg-root, --output-base.
Long story short:

Assuming you cloned into the home directory, your directory structure should be like this: ${HOME}/${GO_PACKAGE_NAME}. So if your package is github.com/foo/bar, then the path should be /home/${USER}/github.com/foo/bar
The original script assumes that the package name has 2 parts divided by /, i.e. k8s.io/sample-controller. If your package (most likely) is called github.com/foo/bar, then the package name has 3 parts. This means you need to add one more .. to your output base: --output-base "$(dirname "${BASH_SOURCE[0]}")/../../.." -> "$(dirname "${BASH_SOURCE[0]}")/../../../.."

You can of course completely override the out base, but the path should still contain the github path.

Most of the path weirdness is now fixed.
/close


Automated cherry pick of #5657: Set net.ipv4.conf.antrea-gw0.arp_announce to 1

Cherry pick of #5657 on release-1.14.
#5657: Set net.ipv4.conf.antrea-gw0.arp_announce to 1
For details on the cherry pick process, see the cherry pick requests page.

/test-flexible-ipam-e2e
/test-all


chore:  and  usage

fixes #945,
originally created https://github.com/aeternity/superhero-wallet/pull/1093

before
after

@AtanasKrondev

Check if now is fine


Check import behaviour when a user reaches the limit on named map templates

Previously, we were detecting the 409 error which was explicitly returned from the Maps API when the limit on named map templates was reached.
See:

https://github.com/CartoDB/cartodb/pull/6315
https://github.com/CartoDB/Windshaft-cartodb/pull/356

With the current changes in cartodb/cartodb regarding Named Maps, the treatment of the exception that was setting an appropriate import error was removed. See import code error documentation here (look for 6670).
I'm opening this issue to review/discuss the current status of an import process whenever the user reaches the maximum of named map templates.
cc @gfiorav

I completely missed the part where we had a specific code for this!
Let's convey a specific raise for this and I'll make the api throw it up to you :)

I created previously CartoDB::NamedMapsWrapper::TooManyTemplatesError, so if you want you can use something similar :-) I don't really mind!

Yup, I remember CartoDB::NamedMapsWrapper::TooManyTemplatesError :)
I might bring it back, shouldn't have killed it. My bad!


[Concept Exercises]: Small Formatting, Typo, & Link Fixes

Did a pass through all the markdown docs for the concept exercises:

[x] Ran Prettier
[x] Looked for spelling errors/typos
[x] Reviewed Reference Link formatting
[x] Double-checked admonition formatting after prettier formatting

The vast bulk of these were removal or addition of white space.  Most links were fine, and there were only two stray typos.

LGTM. (the "speficic" looks like one of my typos, i'm glad i'm not alone)
Do we use the British or American spelling of "initialization"?

Allegedly American. But as an American, I can say that I often can't see the difference. 😂   So I probably missed that one!!
And the only reason I caught "speficic" is because my editor highlighted it....my brain has learned and embedded the incorrect spelling there, and there is nothing I can do about it. 😆

Going to push the big green button on this so that I can pull these changes down and do a sweep of the newer practice exercises.


Change = in galaxy.j2 template to ==

I thought single equal was right for this but ansible templating failed.  It worked when changed to == and the resulting file on dev looks right

That makes sense


Fix bridge driver panic in CreateNetwork

Bridge driver panics in CreateNetwork if called without
a prior Config call. This causes issues in dnet which
tries to create network using default driver configuration.
It should be valid to call CreateNetwork without a prior
Config call in which case we need to assume default driver
config.
Fixed this by properly initializing the driver config pointer.
Also introduced a configured bool to make sure that still
Config is called exactly once for the instance of the bridge
driver.
Signed-off-by: Jana Radhakrishnan<EMAIL_ADDRESS>

@mrjana In my comment I was in fact suggesting this change as a possible one.
But I opted for the other change which fails the network creation if driver config was missing. I guess the restriction I was adding is not acceptable. I will close that PR.
Regarding this PR, shouldn't we set some default values in the config ?
Also can you please remove the d.config != nil check in CreateNetwork() which is no longer needed.

@aboch Ah didn't realize that you had another PR on the same issue with a different solution. But I think we should solve that problem by allowing a default config rather than always forcing callers to call Config.
I also agree that we should have default values. But I though a false value for all the 3 bool values are the default values. Do you have a different default value in mind for any of these 3 values?
I'll remove the d.config != nil check.

LGTM

@mrjana I dont think you intend to push the godep changes in libkv in this PR. or atleast I dont understand the reason for that. if it is a mistake, can you pls remove them ?

@mavenugo I did intend to push the libkv godep change as part of this PR because the libkv version is really out of sync with the version mentioned in Godeps.json file and it has caused me lot of grief while trying to make dnet work. It should not really be out of sync if not for a mistake by a committer that we failed to catch because we don't have proper tests to catch that mistake. All the commits that I am pushing as part of this PR are for fixing our tests properly so we can catch those mistakes before it gets committed. The commit message has all the context.

@mrjana okay. i failed to notice the commit message. it makes sense now & LGTM.


Possible to change character for untracked files?

There's one discrepancy from git status --short that annoys me, and that is that untracked files are marked with ?? in the status, but with a grey A in git-radar. I understand that that is because there's a relation between untracked and added files, but I'd rather have the output resemble what I see in git status --short, which matches my mental model better. Is there a way to change the individual symbols?

? probably makes more sense actually. :+1:

+1


Add implementation for file_system_buffer filter

Commit Message: Add implementation for file_system_buffer filter
Additional Description: Integration test follows in the next PR.
Risk Level: None, not yet used.
Testing: 100% coverage.
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

/assign mattklein123

Accidentally mis-rebased before push, sorry about the force-pushes to fix it.

/retest

/retest


ESLint updates

Update to eslint 5.2.0, which has some new default rules.
Disable no-self-assign in Cesium tests, this new rule is useful but not in our specs.
Allow ES 2017 in node code, this includes async/await, which we have started using in Cesium-related Node projects
Add no-var and prefer-const as rules for Node code, we've already have been using them with success in other projects.
Bump eslint-config-cesium to 6.0.0 and update CHANGES so I can release once this is merged.

Thanks for the pull request @mramato!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

CC @tfili since we were talking about these new changes yesterday.

OK, sounds like this is ready.

Looks good, thanks @mramato!


add type hints for base_generator

#291

Codecov Report

Merging #292 into 2.0 will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff         @@
##            2.0   #292   +/-   ##
===================================
  Coverage   100%   100%
===================================
  Files        25     25
  Lines       637    638    +1
===================================
+ Hits        637    638    +1

Impacted Files
Coverage Δ

matchzoo/engine/base_generator.py
100% <100%> (ø)
:arrow_up:

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 86ed0d0...39d96b7. Read the comment docs.


Documentation is AWOL

https://napari.org/docs/ -> 404
(same for https://napari.org/napari-tutorials/)

Thanks for the report @stefanv!

https://napari.org/docs/ -> 404

It seems that the following line properly copies the contents of html directly to the current folder on MacOS but not on linux (it shows up in https://napari.org/docs/html) 😒
https://github.com/napari/napari/blob/3950dba6ced8a7f477877149df1d920f3502a647/.cirrus.yml#L255

(same for https://napari.org/napari-tutorials/)

This has been renamed to https://napari.org/tutorials. Do you think I should put in a redirect?

@kne42 I guess the homepage needs updating also, as it links to both those addresses. Not sure exactly where it lives.


Fixed optional mjpeg still image to default to None

Description:
Fixed optional still_image_url to default to None.
Related to PR https://github.com/home-assistant/home-assistant/pull/5440
Fixes
17-01-23 00:51:59 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform mjpeg
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_component.py", line 146, in _async_setup_platform
    entity_platform.async_add_entities, discovery_info
  File "/usr/src/app/homeassistant/components/camera/mjpeg.py", line 48, in async_setup_platform
    yield from async_add_devices([MjpegCamera(hass, config)])
  File "/usr/src/app/homeassistant/components/camera/mjpeg.py", line 74, in __init__
    self._still_image_url = device_info[CONF_STILL_IMAGE_URL]
KeyError: 'still_image_url'

Strange, that should be None with default. I think we fix it with use device_info.get(CONF_STILL_IMAGE_URL). Can you change your PR?

When it's optional, the key will not be added to the output dict unless a default is specified.
Using device_info.get(…) is indeed the correct solution.


Failed to compile smart contracts with zksolc: Cannot get source files: Could not get solc: Unknown version provided

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
No response
Operating System
macOS (Apple Silicon)
Describe the bug
Failed to compile smart contracts with zksolc: Cannot get source files: Could not get solc: Unknown version provided

@zhangninghai are you still getting this issue. Could you provide an example to reproduce it?

This issue has grown stale, and without any other information provided we'll be closing it. Feel free to reopen the issue if you have new information for us.


JavaLogger javadoc and test updates

Update javadoc with new class name.
Rename test class name to match the class it's testing.

Hello,
Thanks for your help.
Your changes were committed to Apache Ignite repository (git://git.apache.org/incubator-ignite.git).

Thank you.


restrict vespamalloc attributes

only "name tokens' allowed

@tokle please review
@baldersheim FYI

note: we probably want to restrict from "xsd:string" to NMTOKEN or similar other places in the rnc files, too.


Black screen after login

Environment

Device: ThinksPad T440 (i5-4200U w/ GT720M)
OS: ArchLinux w/ latest updates
Software Version: 0.5.2-2 from aur/ly
Window Manager: i3-wm 4.19.2-1
Kernel Version: Linux ArchPad 5.13.12-arch1-1 #1 SMP PREEMPT
Graphic Driver: nvidia-390xx-dkms 390.144-1
X.Org Version: 1.20.13-2

Description

Expected Behavior: i3 swarms and shows logged-in desktop w/ i3bar in the bottom
Actual Behavior: got a black screen in tty2 w/o problems switching to other ttys
Step to reproduce:

Type in user name and password
Press Enter to confirm login
Login portal disappeared w/ X.Org logs flashing through
Tty2 silents in an eternal dark screen

I noticed ly launched two sub processes: Xorg :1 vt2 and i3. However, it doesn't help with the black screen condition.

I can't see any meaningful errors from the Xorg logs. Not sure why this happens.

I noticed a display_setup.sh script in my lightdm config folder which is not out-of-box and found it initially from the arch wiki. However, my version of the script is kind of modified:
[tjm@ArchPad ~]$ cat /etc/lightdm/display_setup.sh
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
xrandr --dpi 96
[tjm@ArchPad ~]$

So I made a hard link from /etc/lightdm/display_setup.sh to /etc/X11/xinit/xinitrc.d/30-display_setup.sh. And then the black screen disappeared. I believe the black screen is caused by configure file /etc/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf from the arch wiki. However, it shows like /etc/X11/xorg.conf on my system ¯_(ツ)_/¯


✨ Apply ignore patterns from Directory argument in dagger call

With https://github.com/dagger/dagger/pull/7744 we can define ignore patterns to apply when loading a default directory from the context. See:

https://github.com/dagger/dagger/issues/7647

However, if you specify a directory explicitly with dagger call, those patterns won’t be applied. Module authors need to continue setting views and tell end users to specify it next to the path.
If there are ignore patterns for a Directory type, the CLI can use them. If a view is passed, use it. But if not, use the ignore patterns from the argument.
I’m assuming that when a module author specifies ignore patterns in a directory argument it’s always desirable to apply those patterns to any directory. An example of that is a function that lints Python code. There’s only very specific file extensions that you’d want to filter here, as any others would unnecessarily invalidate the cache or upload more than it needs to.
If not, there’s the views escape hatch, however I’m not sure if views should continue to exist since they were created as a stopgap to enable filtering local directories, provided as input to the CLI. If we do remove views, then we need to think a bit more if there’s a need for an escape hatch or not.

Can we split out a separate issue for passing directories from a module to another module? Just so we have a place to track this?


AddRange() for CompositeDisposable

I think it would be nice even if it is a trivial extension method.
The consensus in chat was that it would be bloat.
Asking what you think before writing a PR.

What is the expected signature and behavior with this extension. Does this have to be in Rx.NET?

A signature like:
public void AddRange(IEnumerable<IDisposable> collection)

Probably makes sense.
Keeping it similar to List<T>.AddRange(). Been a while since I had a need for this so I'm happy to close the issue.

I see. I'd say PR welcome.

Closing due to lack of interest or follow-up PR.


Trello is undefined

Hi @acidstudios !
Thank you for this librairy!
I got the error "Trello is undefined" that I solved adding

on my index.html.
The best fix would be to avoid to have to add the scripts in the index.html.
An alternative solution would be to add the lines in your readme.
Or am I missing something?
Thank you

Hello @nicgirault!
Well, the library automatically add the trello API when is loaded.
Can you send me a screenshot of your console pls.

The screenshot does not say a lot unless Trello is not defined. My analysis is the following:
My code
app.config (TrelloApiProvider) ->
  TrelloApiProvider.init
    key: '...'
    secret: '...'
    scopes:
      read: true
      write: true
      account: true
    AppName: '...'

is called before the 'trello' module "run" block (where you load the Trello variable). Am I right?

It runs before Trello API its loaded, the problem was fixed.


Add list blocks command to CLI

I've added an ls command to the tsdb cli for listing blocks in the DB (https://github.com/prometheus/tsdb/issues/107). It uses github.com/ryanuber/columnize for printing tabular.
Example output of tsdb ls:
BLOCK ULID                  MIN TIME  MAX TIME  NUM SAMPLES  NUM CHUNKS  NUM SERIES
01BVCQAJVXZA5DFKWV6DRYE9W3  0         7200000   35900000     300000      100000
01BVCQAT7894QCN38QV8DVGPWJ  7200000   14400000  36000000     300000      100000
01BVCQB11494K3ZS7MDXDPRP4B  14400000  21600000  36000000     300000      100000

The Go stdlib has a package for writing tabular columns, did you consider
using that?
https://golang.org/pkg/text/tabwriter/
On Sun, 1 Oct 2017, 21:29 BasPH<EMAIL_ADDRESS>wrote:

I've added an ls command to the tsdb cli for listing blocks in the DB (
#107 https://github.com/prometheus/tsdb/issues/107). It uses
github.com/ryanuber/columnize http://url for printing tabular.
Example output of tsdb ls:
BLOCK ULID                  MIN TIME  MAX TIME  NUM SAMPLES  NUM CHUNKS  NUM SERIES
01BVCQAJVXZA5DFKWV6DRYE9W3  0         7200000   35900000     300000      100000
01BVCQAT7894QCN38QV8DVGPWJ  7200000   14400000  36000000     300000      100000
01BVCQB11494K3ZS7MDXDPRP4B  14400000  21600000  36000000     300000      100000

You can view, comment on, or merge this pull request online at:
https://github.com/prometheus/tsdb/pull/156
Commit Summary

Add list blocks command to CLI

File Changes

M cmd/tsdb/main.go
https://github.com/prometheus/tsdb/pull/156/files#diff-0 (8)
M db.go https://github.com/prometheus/tsdb/pull/156/files#diff-1
(20)

Patch Links:

https://github.com/prometheus/tsdb/pull/156.patch
https://github.com/prometheus/tsdb/pull/156.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/tsdb/pull/156, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEJbsNjzTz1y4C-yQFtkk0byecVQRD3bks5sn_ZAgaJpZM4PqBTp
.

I looked at the Kubernetes code and they're using the tabwriter. There was a TODO in the code to replace with something like columnize. With columnize printing tables is a one-liner, with the tabwriter it's a little more code. Is there a preference for using stdlib/external packages?

Some preference if possible, since @TheTincho has to package every new dep up for Debian and we are constantly causing him troubles :)
If you can write a 10 line helper function and save a dep in return, that's certainly better.

Thanks for the changes. Having the printing as a direct method to DB itself is not ideal. A getter like DB.Block() would probably be better. The formatting and printing can then all be handled independently in the main.go.

Thanks. DB.Blocks() already exists :) Agree that handling printing is better in main.go, so I'll move it there.

Thanks 👍

Thanks @fabxc for thinking of me, really appreciate that! <3


ARROW-218: Add optional API token authentication option to PR merge tool

You can use an API token with extremely limited privileges (i.e., only access to public GitHub repos), but this helps avoid rate limiting issues on shared outbound IP addresses.

+1


Handle empty list of predicates in _predicateWrap

Math.max on an empty array returns -Infinity, causing things to go wrong. Instead, I reduce the list of lengths with max as iterator function and 0 as default value.
I'd love to hear back from you. If there is anything I can improve, let me know.
Fixes #1298

It would probably be worthwhile adding similar tests to anyPass along with this change as well:
it('returns false for an empty predicate list', function() {
  assert.strictEqual(R.anyPass([])(3), false);
});

:herb:

:cow2:


Add org.opencontainers.image.* labels to Dockerfiles

Why? What?

This should ultimately help for image-to-code back references.
org.label-schema.* labels are now deprecated, in favour of org.opencontainers.image.* labels.
See also: https://github.com/opencontainers/image-spec/blob/master/annotations.md#back-compatibility-with-label-schema
Git revision (git rev-parse HEAD) is now injected at docker build time.
MAINTAINER is deprecated, in favour of the maintainer label, which can be added once #823 has been merged, alongside with:

org.opencontainers.image.vendor and
org.opencontainers.image.authors.

Testing
$ docker inspect quay.io/weaveworks/cortex-alertmanager
[
    {
        [...]
        "ContainerConfig": {
            [...]
            "Labels": {
            "Labels": {
                "org.opencontainers.image.revision": "05830bf3a6bd0186b4ad444241084b526a7df25c",
                "org.opencontainers.image.source": "https://github.com/weaveworks/cortex/tree/master/cmd/alertmanager",
                "org.opencontainers.image.title": "alertmanager"
            }
[...]

Out of interest, are there any tools that actually consume these labels?

@tomwilkie, there at least the one I'm working on at the moment.

Looks cool!


Update README.md

Add some mandatory pre-steps before building the docker image

/assign @elgnay

@kim-fitness
please avoid adding your local binaries in the PR.

Thanks, please squash the commit and signoff.

btw, I would suggest to add _output into .gitignore.

@kim-fitness
please avoid adding your local binaries in the PR.

Oops, that's my fault, let me reset this commit then, thanks for the heads-up!

Since the modification of file .gitignore is not related with the original issue, I'll leave it as a separate commit.
If it is not the practice of this project, please let me know and squash them up then. Thanks.

that is fine, would you squash this to one commit and we are good to go.

/approve
/lgtm


[Bug]: Extremly Outdated Package in yapa.json

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
yapa
Expected/Current Behaviour
YAPA is no longer maintened, for further updates and new releases check out YAPA 2.0
Steps to Reproduce
-

Possible Solution
Either replace with YAPA2 or remove completely and include the new, better and more polished alternatives:

JakubGluszek/intentio in Rust
ayoisaiah/focus for command-line written in Go

Scoop and Buckets Version
-

Scoop Config
-

PowerShell Version
-

Additional Softwares

@HUMORCE should the package yapa be removed from this bucket?

Do you think should the package yapa be removed from this bucket, or should it be moved to the depracted folder inside this bucket?

Copy to versions/yapa1 and then Update extras/yapa to 2.x
OR created extras/yapa2 only.

I don't think Intentio can be added due to low stars, unless the members want to make an exception for the app.

@cvladan I added it to my personal bucket, you are welcome to try it.
To add this bucket, run
scoop bucket add MyScoop 'https://github.com/Zliced13/MyScoop'

To install, do
scoop install intentio


feature: meltano config set default should be --interactive

Feature scope
CLI (options, error messages, logging, etc.)
Description
When setting configurations I end up typing out meltano config tap-monday set --interactive a lot (great feature!)
It would be nicer if instead of meltano config tap-monday set returning
visch@DESKTOP-9BDPA9T:~/git/tap-monday$ meltano config tap-monday set
2023-05-16T17:58:53.673276Z [info     ] The default environment 'test' will be ignored for `meltano config`. To configure a specific environment, please use the option `--environment=<environment name>`.
/home/visch/.local/pipx/venvs/meltano/lib/python3.8/site-packages/meltano/cli/interactive/config.py:390: RuntimeWarning: Unknown setting ''
  value, metadata = settings.set_with_metadata(
Need help fixing this problem? Visit http://melta.no/ for troubleshooting steps, or to
join our friendly Slack community.

not enough values to unpack (expected at least 1, got 0)

It would run --interactive by default!

Related:

https://github.com/meltano/meltano/issues/6861#issuecomment-1545903562

@visch this is probably a duplicate of #6861

Duplicate of https://github.com/meltano/meltano/issues/6861


Update sys.types views

Description

Removed duplicate entries for timestamp.
Changed is_nullable column value from 1 to 0 for timestamp and sysname datatypes.

Performance Testing
With Changes
select  tbl.name AS [Name] , clmns.name , usrt.name as tname from sys.tables AS tbl inner join sys.all_columns as clmns on clmns.object_id = tbl.object_id inner join sys.types as usrt on usrt.user_type_id = clmns.user_type_id
(24492 rows affected)
8637 ms
Without changes
select  tbl.name AS [Name] , clmns.name , usrt.name as tname from sys.tables AS tbl inner join sys.all_columns as clmns on clmns.object_id = tbl.object_id inner join sys.types as usrt on usrt.user_type_id = clmns.user_type_id
(24492 rows affected)
8589 ms
Issues Resolved
[List any issues this PR will resolve]
Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Your description does not mention why you require this change and how its going to resolve it

Changed is_nullable column value from 1 to 0 for timestamp and sysname datatypes.

There are is_nullable columns in other views as well, how are we making sure that we are fixing them as well?

In all, if you take into consideration all of my comments - we wont require change in sys.types


[?] fix ridiculous length of form_order decimals, update guidance

We don't need more than 5 decimal places at most for this??

Saw this and wrote a Python script that can go in and adjust form order numbers: https://github.com/uwlib-cams/map_storage/blob/main/py/adjust_form_order.py

Thank you @mcm104 !
You've edited quite a few implementation_sets at this point. Do you have any thoughts about how many decimal places we might want to allow for readjusting form_order values as needed?
For the monographs Work template, I've been adding form_order values in increments of 5. (Top PT in the RT has 0.0000000005, next has 0.0000000010, next 0.0000000015, etc.) Thinking that leaving space in this way can accommodate future property additions or rearrangements without having to edit lots of form_orders.
But even so, I don't think we need a full 10 decimal places...

I'm not sure we need anything beyond just one (0.1, 0,2, etc.).
At least in my work, I never had to change which property came first in the form order -- 0.0000000001 was pretty safe. I only ever had to change form order values when I had to introduce a new property between two properties that had already been numbered -- and in these cases, all the zeros were useless; I had to add more digits after. e.g., if I had property A at 0.0000000002 and property B at 0.0000000003 and want to put property C between them, those first nine 0's don't matter. If I don't want to change everything that comes after (B) 0.0000000003, I would have to do something like (A) 0.00000000021, (C) 0.00000000022, and (B) 0.0000000003. There's really no difference between this and 0.21, 0.22, and 0.3, which is much clearer for a human editor to read.
Then if we hypothetically did need to swap out the first property, that could also be done with adding an extra digit on the end, i.e. 0.1 becomes 0.12 and the new first property becomes 0.11.
And if we wanted to use the Python script, whatever mess we make would get sorted out there. e.g. if we have 0.111111, 0.111112, and 0.111115, the Python script would just update these to 1, 2, and 3. (But the Python script could also easily be edited to start on 0.1 and increase by 0.5 each PT, or whatever values we prefer.)

Coming back to this after editing the work prop set:
Your form order got much larger than mine! I have to imagine that the work RT will have the most properties, so since that made it into triple digits, I'm thinking three digits (0.001) should be enough. (I also disagree with myself for originally saying just one when my own property sets got into double digits...)
For now, I'll update the Python script to start at 0.001 and increase by increments of 0.005.

Script is not editing this property for whatever reason... Need to investigate, reverting to old form order numbers for now

Update: it was an issue with two properties in the same RT having the same form order value -- it's been fixed and the Python script updated to print an error message if it happens again.


table's data title not getting translated using conditional operator .

Subject of the issue
unable to translate based on conditional operator .
data-title="{{(installedPillars.indexOf('LM') != -1 && installedPillars.indexOf('TM') == -1) ? 'JOB_MANAGER_FIELD_JOB_CODE' | translate : 'JOB_MANAGER_JOB_ID' | translate }}"

Your environment

version of angular-translate
version of  angular 1.4.12
all browsers

Expected behaviour
the values should get translated .
Actual behaviour
Tell us what happens instead
No value gets displayed .

Why don't you write
{{(installedPillars.indexOf('LM') != -1 && installedPillars.indexOf('TM') == -1)?'JOB_MANAGER_FIELD_JOB_CODE':'JOB_MANAGER_JOB_ID' | translate }}

??

AngularJS expression fix provided, but not an issue with translate actually.
Case closed.


PC crashes when looking at that house

l'm using a radeon driver on lubuntu 14.04, when l look back to a house, it stops and l need to kill Terasology somehow or restart my pc.
l looked there and quickly hit ctrl+alt+F6 to get to a console, messages looking like following appeared:
[  226.602696] radeon 0000:01:00.0: ring 0 stalled for more than 23388msec
l executed $ kill -SIGKILL $(pgrep java) to stop it.
lt also crashed when l didn't enable that high end settings.
Here's an excerpt of $ dmesg:
[   52.515542] audit: type=1400 audit(1451659786.091:49): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=4360 comm="apparmor_parser"
[  170.574618] radeon 0000:01:00.0: ring 0 stalled for more than 10016msec
[  170.574657] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002d9f on ring 0)
[  171.075505] radeon 0000:01:00.0: ring 0 stalled for more than 10516msec
[  171.075580] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002d9f on ring 0)
[  171.576284] radeon 0000:01:00.0: ring 0 stalled for more than 11016msec
[  171.576357] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da0 on ring 0)
[  172.077046] radeon 0000:01:00.0: ring 0 stalled for more than 11516msec
[  172.077123] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da1 on ring 0)
[  172.577856] radeon 0000:01:00.0: ring 0 stalled for more than 12016msec
[  172.577933] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da1 on ring 0)
[  173.078632] radeon 0000:01:00.0: ring 0 stalled for more than 12516msec
[  173.078711] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da1 on ring 0)
[  173.579401] radeon 0000:01:00.0: ring 0 stalled for more than 13016msec
[  173.579481] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da2 on ring 0)
[  174.080246] radeon 0000:01:00.0: ring 0 stalled for more than 13516msec
[  174.080278] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da2 on ring 0)
[  174.580998] radeon 0000:01:00.0: ring 0 stalled for more than 14016msec
[  174.581072] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da3 on ring 0)
[  175.081833] radeon 0000:01:00.0: ring 0 stalled for more than 14516msec
[  175.081905] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da4 on ring 0)
[  175.582570] radeon 0000:01:00.0: ring 0 stalled for more than 15016msec
[  175.582642] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da4 on ring 0)
[  176.083356] radeon 0000:01:00.0: ring 0 stalled for more than 15516msec
[  176.083428] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da4 on ring 0)
[  176.584199] radeon 0000:01:00.0: ring 0 stalled for more than 16016msec
[  176.584272] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da5 on ring 0)
[  177.084981] radeon 0000:01:00.0: ring 0 stalled for more than 16516msec
[  177.085055] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da6 on ring 0)
[  177.585719] radeon 0000:01:00.0: ring 0 stalled for more than 17016msec
[  177.585790] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da6 on ring 0)
[  178.086502] radeon 0000:01:00.0: ring 0 stalled for more than 17516msec
[  178.086573] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da6 on ring 0)
[  178.587293] radeon 0000:01:00.0: ring 0 stalled for more than 18016msec
[  178.587365] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da7 on ring 0)
[  179.088075] radeon 0000:01:00.0: ring 0 stalled for more than 18516msec
[  179.088146] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  179.588913] radeon 0000:01:00.0: ring 0 stalled for more than 19016msec
[  179.590135] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  180.089698] radeon 0000:01:00.0: ring 0 stalled for more than 19516msec
[  180.091267] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  180.590437] radeon 0000:01:00.0: ring 0 stalled for more than 20016msec
[  180.591969] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  181.091213] radeon 0000:01:00.0: ring 0 stalled for more than 20516msec
[  181.092715] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  181.592009] radeon 0000:01:00.0: ring 0 stalled for more than 21016msec
[  181.593439] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  182.092785] radeon 0000:01:00.0: ring 0 stalled for more than 21516msec
[  182.094117] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da8 on ring 0)
[  182.593588] radeon 0000:01:00.0: ring 0 stalled for more than 22016msec
[  182.594903] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002da9 on ring 0)
[  183.094419] radeon 0000:01:00.0: ring 0 stalled for more than 22516msec
[  183.095724] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  183.595146] radeon 0000:01:00.0: ring 0 stalled for more than 23016msec
[  183.596442] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  184.095946] radeon 0000:01:00.0: ring 0 stalled for more than 23516msec
[  184.097236] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  184.596726] radeon 0000:01:00.0: ring 0 stalled for more than 24016msec
[  184.598022] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  185.097508] radeon 0000:01:00.0: ring 0 stalled for more than 24516msec
[  185.098793] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  185.598294] radeon 0000:01:00.0: ring 0 stalled for more than 25016msec
[  185.599588] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  186.099078] radeon 0000:01:00.0: ring 0 stalled for more than 25516msec
[  186.100361] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  186.599868] radeon 0000:01:00.0: ring 0 stalled for more than 26016msec
[  186.601157] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  187.100652] radeon 0000:01:00.0: ring 0 stalled for more than 26516msec
[  187.101938] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  187.601492] radeon 0000:01:00.0: ring 0 stalled for more than 27016msec
[  187.602766] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002daa on ring 0)
[  188.102230] radeon 0000:01:00.0: ring 0 stalled for more than 27516msec
[  188.103509] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002dab on ring 0)
[  188.603065] radeon 0000:01:00.0: ring 0 stalled for more than 28016msec
[  188.603076] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002db4 on ring 0)
[  189.103805] radeon 0000:01:00.0: ring 0 stalled for more than 28516msec
[  189.103816] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002db4 on ring 0)
[  189.604586] radeon 0000:01:00.0: ring 0 stalled for more than 29016msec
[  189.604591] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002db4 on ring 0)
[  190.105301] radeon 0000:01:00.0: ring 0 stalled for more than 29516msec
[  190.106249] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002d9b last fence id 0x0000000000002db4 on ring 0)
[  190.620397] radeon 0000:01:00.0: Saved 791 dwords of commands on ring 0.
[  190.620432] radeon 0000:01:00.0: GPU softreset: 0x00000009
[  190.620438] radeon 0000:01:00.0:   GRBM_STATUS               = 0xF0001828
[  190.620443] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x80000003
[  190.620447] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  190.620452] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  190.620456] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[  190.620461] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  190.620465] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x40040000
[  190.620470] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00048006
[  190.620474] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80268647
[  190.620479] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  190.620728] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[  190.620784] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[  190.621938] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[  190.621942] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[  190.621946] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  190.621951] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  190.621955] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[  190.621959] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  190.621964] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[  190.621968] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[  190.621972] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[  190.621977] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  190.622014] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[  190.644836] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[  190.647983] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
[  190.648073] radeon 0000:01:00.0: WB enabled
[  190.648076] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880218d01c00
[  190.648078] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880218d01c0c
[  190.649541] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90011632118
[  190.665695] [drm] ring test on 0 succeeded in 2 usecs
[  190.665706] [drm] ring test on 3 succeeded in 6 usecs
[  190.841638] [drm] ring test on 5 succeeded in 2 usecs
[  190.841648] [drm] UVD initialized successfully.
[  190.852357] [drm] ib test on ring 0 succeeded in 0 usecs
[  190.852437] [drm] ib test on ring 3 succeeded in 0 usecs
[  191.511578] [drm] ib test on ring 5 succeeded
[  208.574426] radeon 0000:01:00.0: ring 0 stalled for more than 10388msec
[  208.576320] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  209.075215] radeon 0000:01:00.0: ring 0 stalled for more than 10888msec
[  209.077113] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  209.576000] radeon 0000:01:00.0: ring 0 stalled for more than 11388msec
[  209.577808] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  210.076812] radeon 0000:01:00.0: ring 0 stalled for more than 11888msec
[  210.078636] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  210.577526] radeon 0000:01:00.0: ring 0 stalled for more than 12388msec
[  210.579298] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  211.078255] radeon 0000:01:00.0: ring 0 stalled for more than 12888msec
[  211.079870] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  211.579089] radeon 0000:01:00.0: ring 0 stalled for more than 13388msec
[  211.580569] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  212.079880] radeon 0000:01:00.0: ring 0 stalled for more than 13888msec
[  212.081218] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  212.580578] radeon 0000:01:00.0: ring 0 stalled for more than 14388msec
[  212.581067] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  213.081455] radeon 0000:01:00.0: ring 0 stalled for more than 14888msec
[  213.082639] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  213.582234] radeon 0000:01:00.0: ring 0 stalled for more than 15388msec
[  213.583411] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  214.083023] radeon 0000:01:00.0: ring 0 stalled for more than 15888msec
[  214.084244] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  214.583811] radeon 0000:01:00.0: ring 0 stalled for more than 16388msec
[  214.585087] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  215.084655] radeon 0000:01:00.0: ring 0 stalled for more than 16888msec
[  215.088331] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  215.585429] radeon 0000:01:00.0: ring 0 stalled for more than 17388msec
[  215.587312] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  216.086223] radeon 0000:01:00.0: ring 0 stalled for more than 17888msec
[  216.088067] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  216.587011] radeon 0000:01:00.0: ring 0 stalled for more than 18388msec
[  216.588799] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  217.087797] radeon 0000:01:00.0: ring 0 stalled for more than 18888msec
[  217.089555] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  217.588574] radeon 0000:01:00.0: ring 0 stalled for more than 19388msec
[  217.590172] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  218.089264] radeon 0000:01:00.0: ring 0 stalled for more than 19888msec
[  218.091085] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  218.590105] radeon 0000:01:00.0: ring 0 stalled for more than 20388msec
[  218.593176] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  219.090953] radeon 0000:01:00.0: ring 0 stalled for more than 20888msec
[  219.092928] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  219.591659] radeon 0000:01:00.0: ring 0 stalled for more than 21388msec
[  219.594345] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  220.092509] radeon 0000:01:00.0: ring 0 stalled for more than 21888msec
[  220.095134] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  220.593254] radeon 0000:01:00.0: ring 0 stalled for more than 22388msec
[  220.595869] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  221.094085] radeon 0000:01:00.0: ring 0 stalled for more than 22888msec
[  221.096646] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  221.594827] radeon 0000:01:00.0: ring 0 stalled for more than 23388msec
[  221.597225] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  222.095597] radeon 0000:01:00.0: ring 0 stalled for more than 23888msec
[  222.097571] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  222.596401] radeon 0000:01:00.0: ring 0 stalled for more than 24388msec
[  222.598999] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd4 on ring 0)
[  223.097235] radeon 0000:01:00.0: ring 0 stalled for more than 24888msec
[  223.099802] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd5 on ring 0)
[  223.597965] radeon 0000:01:00.0: ring 0 stalled for more than 25388msec
[  223.600565] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  224.098754] radeon 0000:01:00.0: ring 0 stalled for more than 25888msec
[  224.101377] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  224.599538] radeon 0000:01:00.0: ring 0 stalled for more than 26388msec
[  224.602109] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  225.100341] radeon 0000:01:00.0: ring 0 stalled for more than 26888msec
[  225.102894] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  225.601109] radeon 0000:01:00.0: ring 0 stalled for more than 27388msec
[  225.603685] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  226.101952] radeon 0000:01:00.0: ring 0 stalled for more than 27888msec
[  226.104489] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  226.602696] radeon 0000:01:00.0: ring 0 stalled for more than 28388msec
[  226.605300] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd6 on ring 0)
[  227.103470] radeon 0000:01:00.0: ring 0 stalled for more than 28888msec
[  227.106081] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd7 on ring 0)
[  227.604203] radeon 0000:01:00.0: ring 0 stalled for more than 29388msec
[  227.606790] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd8 on ring 0)
[  228.105048] radeon 0000:01:00.0: ring 0 stalled for more than 29888msec
[  228.107633] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000002dc8 last fence id 0x0000000000002dd8 on ring 0)
[  228.247439] radeon 0000:01:00.0: Saved 503 dwords of commands on ring 0.
[  228.247474] radeon 0000:01:00.0: GPU softreset: 0x00000009
[  228.247480] radeon 0000:01:00.0:   GRBM_STATUS               = 0xF0001828
[  228.247486] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x80000003
[  228.247491] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  228.247495] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  228.247500] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[  228.247504] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  228.247509] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x40040000
[  228.247513] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00048006
[  228.247517] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80268647
[  228.247522] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  228.247763] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[  228.247819] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[  228.248973] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[  228.248978] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[  228.248982] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  228.248986] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  228.248990] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[  228.248995] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  228.248999] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[  228.249003] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[  228.249008] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[  228.249012] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  228.249049] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[  228.273154] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[  228.276296] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
[  228.276387] radeon 0000:01:00.0: WB enabled
[  228.276390] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880218d01c00
[  228.276392] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880218d01c0c
[  228.277856] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90011632118
[  228.294008] [drm] ring test on 0 succeeded in 2 usecs
[  228.294019] [drm] ring test on 3 succeeded in 6 usecs
[  228.469946] [drm] ring test on 5 succeeded in 2 usecs
[  228.469956] [drm] UVD initialized successfully.
[  228.478529] [drm] ib test on ring 0 succeeded in 0 usecs
[  228.478612] [drm] ib test on ring 3 succeeded in 0 usecs
[  229.126737] [drm] ib test on ring 5 succeeded
[  841.797143] radeon 0000:01:00.0: ring 0 stalled for more than 10000msec
[  841.797154] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  842.297619] radeon 0000:01:00.0: ring 0 stalled for more than 10500msec
[  842.297630] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  842.798051] radeon 0000:01:00.0: ring 0 stalled for more than 11000msec
[  842.798063] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  843.298471] radeon 0000:01:00.0: ring 0 stalled for more than 11500msec
[  843.298478] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  843.799091] radeon 0000:01:00.0: ring 0 stalled for more than 12000msec
[  843.799102] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  844.299491] radeon 0000:01:00.0: ring 0 stalled for more than 12500msec
[  844.299503] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  844.800051] radeon 0000:01:00.0: ring 0 stalled for more than 13000msec
[  844.800063] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  845.300564] radeon 0000:01:00.0: ring 0 stalled for more than 13500msec
[  845.300575] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  845.801060] radeon 0000:01:00.0: ring 0 stalled for more than 14000msec
[  845.801071] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cd7 last fence id 0x0000000000006cdd on ring 0)
[  846.252533] radeon 0000:01:00.0: Saved 183 dwords of commands on ring 0.
[  846.252568] radeon 0000:01:00.0: GPU softreset: 0x00000009
[  846.252574] radeon 0000:01:00.0:   GRBM_STATUS               = 0xE5700828
[  846.252579] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0xFC000001
[  846.252584] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  846.252588] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  846.252593] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[  846.252597] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  846.252602] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00010800
[  846.252606] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00028006
[  846.252611] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x80038647
[  846.252616] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  846.252861] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B
[  846.252917] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100
[  846.254072] radeon 0000:01:00.0:   GRBM_STATUS               = 0x00003828
[  846.254077] radeon 0000:01:00.0:   GRBM_STATUS_SE0           = 0x00000007
[  846.254082] radeon 0000:01:00.0:   GRBM_STATUS_SE1           = 0x00000007
[  846.254086] radeon 0000:01:00.0:   SRBM_STATUS               = 0x200000C0
[  846.254090] radeon 0000:01:00.0:   SRBM_STATUS2              = 0x00000000
[  846.254095] radeon 0000:01:00.0:   R_008674_CP_STALLED_STAT1 = 0x00000000
[  846.254099] radeon 0000:01:00.0:   R_008678_CP_STALLED_STAT2 = 0x00000000
[  846.254103] radeon 0000:01:00.0:   R_00867C_CP_BUSY_STAT     = 0x00000000
[  846.254108] radeon 0000:01:00.0:   R_008680_CP_STAT          = 0x00000000
[  846.254113] radeon 0000:01:00.0:   R_00D034_DMA_STATUS_REG   = 0x44C83D57
[  846.254150] radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[  846.278089] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[  846.283042] [drm] PCIE GART of 1024M enabled (table at 0x0000000000274000).
[  846.283141] radeon 0000:01:00.0: WB enabled
[  846.283146] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880218d01c00
[  846.283150] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c and cpu addr 0xffff880218d01c0c
[  846.284607] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000072118 and cpu addr 0xffffc90011632118
[  846.300779] [drm] ring test on 0 succeeded in 2 usecs
[  846.300792] [drm] ring test on 3 succeeded in 6 usecs
[  846.476864] [drm] ring test on 5 succeeded in 2 usecs
[  846.476882] [drm] UVD initialized successfully.
[  856.811849] radeon 0000:01:00.0: ring 0 stalled for more than 10328msec
[  856.811860] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000006cdb last fence id 0x0000000000006cde on ring 0)
[  856.811960] [drm:r600_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35).
[  856.812009] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on GFX ring (-35).
[  879.768996] lxsession[2628]: segfault at 0 ip<PHONE_NUMBER>40a2d0 sp 00007fff4f81ae40 error 4 in lxsession[400000+35000]

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29518822-pc-crashes-when-looking-at-that-house?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github).

Hmmmm... that's a first for me. Looks like a pretty low-level issue, right down to the way a shader is being executed by the GPU. At first sight it looks like an obscure shader problem or an obscure driver issue. Are there other situations in which this occurs?

Hmmmm... that's a first for me. Looks like a pretty low-level issue, right down to the way a shader is being executed by the GPU. At first sight it looks like an obscure shader problem or an obscure driver issue. Are there other situations in which this occurs?

Hi @HybridDog and neat logging! And waaay beyond my limited knowledge of 3d wizardry.
Did you use any unusual blocks in building the house and how did you build it without triggering the issue? Does it only happen at a certain range from it, being able to look at and thus render more objects at once? Do you have any extra modules enabled etc?
@emanuele3d might know a thing or two about GPU logging, but I wonder how we can tie the error in the log there to any actual game code / content.

Hi @HybridDog and neat logging! And waaay beyond my limited knowledge of 3d wizardry.
Did you use any unusual blocks in building the house and how did you build it without triggering the issue? Does it only happen at a certain range from it, being able to look at and thus render more objects at once? Do you have any extra modules enabled etc?
@emanuele3d might know a thing or two about GPU logging, but I wonder how we can tie the error in the log there to any actual game code / content.

Are there other situations in which this occurs?

l just got this problem when playing with the new terasology. The older version (the one with the test the nui button) worked.

Did you use any unusual blocks in building the house and how did you build it without triggering the issue? Does it only happen at a certain range from it, being able to look at and thus render more objects at once? Do you have any extra modules enabled etc?

l didn't build the house, city was selected by default when l created a new world.
l don't think the house is the reason for the crash and l didn't enable extra modules, l used the default configuration.

Ahhh! Okay, that helps. So you're playing the default gameplay template, which is Light & Shadow, that uses the "City World" and starts you in a city with lots of buildings.
Could you attach / link to the game log files as well? Maybe there'll be a clue during startup or world loading if you crash immediately as the world loads. Do you get to see the world displaying around you for any amount of time before you crash?
And the current Omega works, while just one release back it didn't? That's a good thing to know if so, narrows down the options a good amount.

Just a random guess - name plates.

@MarcinSc doesn't sound so random! :-) Cities does start you right under the city's name tag.
@HybridDog try the plain "Core" gameplay template? No name tags and very little unusual stuff

So you're playing the default gameplay template, which is Light & Shadow, that uses the "City World" and starts you in a city with lots of buildings.

Yes, about 2 houses are not lots of buildings in my opinion.

Do you get to see the world displaying around you for any amount of time before you crash?

Yes, l can walk around a bit but when l look back to where the sun shines bright from, it stops. The game actually doesn't quit, it just stops my graphics and l need to force kill it (if l can).

And the current Omega works, while just one release back it didn't?

No by "the new version of terasology" l meant TerasologyOmega.

try the plain "Core" gameplay template? No name tags and very little unusual stuff

It crashed again.

Could you attach / link to the game log files as well?

l put a compressed (7z) version here to not spam so much:
open a terminal, mark following code, then run $ xsel -o | base64 -d > tmp.7z
[encoded data, 9564 characters]

Hehe, nice, that must be the first in-line compressed error log we've received! Sadly I'm just on good ole Windows and 7zip doesn't seem to want to cooperate :-)
Usually we suggest one of the pasting sites like pastebin or even using a Gist here on GitHub.
And yeah two houses isn't much of a city, that sounds like a rare find, I've never seen them that small.
What actual GPU do you have? It does seem likely that something in it or its driver doesn't get along with one of our shaders, probably one related to lighting effects. IIRC the railgun creates some puffs of smoke that are also lit up and can get too bright in some case.
While there's no current fix being worked on for the brightness issue I wonder if resolving it would help this. So possibly related: #1527, #957, #899, #667
With that in mind I have one last curious experiment: Have you tried fast-forwarding time (F3 + arrow keys) to night where there are fewer intensely bright effects going on? Or maybe disabling bloom / enabling light clamping in the graphic options?

Usually we suggest one of the pasting sites like pastebin or even using a Gist here on GitHub.

http://paste.ubuntu.com/14398135/
l'm using radeon on lubuntu 14.04.3 LTS, so l can't use the newest driver from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
I use this ppa and updated a few packages but as it's mentioned there, it doesn't work on my version, so l couldn't update every package.
Updating those packages did nth l think. l assume synaptic would have told an error if there were incompatibilities with the packages l updated, too.
l don't need to update my java version, do l?

$ java -showversion
openjdk version "1.8.0_20-internal"
OpenJDK Runtime Environment (build 1.8.0_20-internal-b20)
OpenJDK 64-Bit Server VM (build 25.20-b23, mixed mode)

Have you tried fast-forwarding time (F3 + arrow keys) to night where there are fewer intensely bright effects going on? Or maybe disabling bloom / enabling light clamping in the graphic options?

l did it, it crashed. l saw that there are more than 2 houses.

Thanks for the log, helps to have. The few points of interest in there look good.
Your Java is a little old but the game runs so that shouldn't be it. Wouldn't hurt to update just in case and for general utility :-)
Being that you have an unusual driver setup and we have the initial log above showing a deep crash in GPU land it is probably your combination of driver and GPU. It is possible a newer or proprietary driver would work, or it could be a more fundamental issue with the GPU. We've had occasional reports in the past where a Linux user on open source driver would crash yet be able to run the game with proprietary drivers.
I don't think we can dig much deeper at the moment with the crash being in driver land :( It may be that future game changes or driver updates will resolve the issue.

It may be that future game changes or driver updates will resolve the issue.

l don't want to use the proprietary driver because it doesn't support hardware acceleration for X and l can't update to that newer driver. Someone uses both drivers in combination, but l think then the proprietary one would get loaded when booting which makes it take longer l assume.

Understandable. Pros and cons etc :-)
If you figure anything out feel free to report back, otherwise I hope we either fix something one day or see you again with some alternative hardware/software. Good luck!


Clarify meaning of sensitive header values

While the documentation mentions that header values can be marked as sensitive in order to inform outside components that these header values may require special treatment, it was unclear to me whether doing that affects the behavior of this crate.
In fact, the only place in this crate that makes a distinction between regular and sensitive header values is the Debug trait implementation of HeaderValue, which masks sensitive values in the output.
This adds a short note to the documentation to clarify this and to avoid that users think that there might be, for example, a security benefit on the protocol level.

There is a protocol level benefit, it's just not used in this crate because it doesn't implement a client or server.
But the h2 crate uses the sensitive flag to signal the header value shouldn't be saved in the hpack dynamic table, as one example.

Thanks for clarifying, @seanmonstar! I guess I should have researched more.
I’m still thinking whether the documentation could be improved to make it a bit clearer what exactly the benefit of marking header values as sensitive is. I was thinking of something like this:

Sensitive data could represent passwords or other data that should not be stored on disk or in memory. By marking header values as sensitive, components using this crate can be instructed to treat them with special care for security reasons. For example, caches can avoid storing sensitive values, and HPACK encoders used by HTTP/2.0 implementations can choose not to compress them.
Note that sensitivity is not factored into equality or ordering.

I’m not sure it’s a big improvement, but I think it would have made the security benefits of the sensitivity flag more obvious to me. But if you think this isn’t worth changing, I totally wouldn’t mind closing this pull request :slightly_smiling_face:.

What you just proposed sounds great to me!

Thanks for the feedback :+1:! I made the changes I suggested above and updated the commit message.
I thought it couldn’t hurt to point out that the Debug trait implementation masks sensitive values—as long as I don’t make it sound that this is that flag’s main purpose—so I added back a sentence about that.


Facebook video plays in low quality

Please, add posibility to play Facebook videos in higher quality. Currently only 360p plays while there are also 4k sources available.
Thanks

With the new version 7.10.0 of Cast Kodi, the URL of the HD video will be sent to Kodi.


Use number plate abbreviations for state code

It is not the case for:

Uttarakhand (uses UT instead of UK),
Chhattisgarh (uses CT instead of CG),
Telangana (uses TG instead of TS), and
Dadra and Nagar Haveli and Daman and Diu (uses DN instead of DD)

Also, the DD abbreviation is redundantly associated with Daman and Diu despite the merger of Union territories being reflected.

Changing now will break many existing applications which are already dependent on the current abbreviation.

Changing now will break many existing applications which are already dependent on the current abbreviation.

Oh okay, understandable.
Though, hard-coding abbreviations instead of full state name when it is available is anyways a bad practice.

If that's the case, ids shouldn't be used anywhere. Full names are present almost always but still we need an unique identifier.

State Codes are based on this ISO standard :  https://en.wikipedia.org/wiki/ISO_3166-2:IN and not based on the Motor Vehicle Department codes.
Case of DD & DNH is very recent and it was decided to use DN state code.

Alright


feat: adding link HasValue extension

What this PR does / why it's submitted / why we need it:
This PR contains the Link extension HasValue

Checklist:

[x] My PR has a descriptive title (not a vague title like Needed this)
[x] Title and all the commits follow commitlint guidelines
[x] My PR targets the develop branch or appropriate release branch

@aochmann this was closed because is already merged, somehow github was still showing it as not merged


mixin: Fix typo in ThanosCompactHalted alert

Signed-off-by: Pedro Araujo<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Fixed typo in the ThanosCompactHalted alert summary, in the mixin; updated examples with make examples and make docs.
Verification

Not needed.

Thanks, could you run make check-docs to fix the test?
We will make that a bit easier soon https://github.com/thanos-io/thanos/issues/5282

Thanks, could you run make check-docs to fix the test? We will make that a bit easier soon #5282

@wiardvanrij in my initial commit I only ran make examples because it was what the the mixin docs mentioned. When the documentation check failed, I saw that I also needed to run make docs, which I did. The docs check for that commit seemingly failed on network requests, not sure why:
error: 3 errors:
		docs/governance.md:160: "https://thanos.io/tip/thanos/integrations.md/" not accessible even after retry; status code 0: Get "https://thanos.io/tip/thanos/integrations.md/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2 errors:
		CHANGELOG.md:474: "https://thanos.io/v0.15/components/query-frontend.md/" not accessible even after retry; status code 0: Get "https://thanos.io/v0.15/components/query-frontend.md/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
		CHANGELOG.md:1043: "https://thanos.io/" not accessible even after retry; status code 0: Get "https://thanos.io/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
2 errors:
		README.md:23: "https://thanos.io/tip/thanos/getting-started.md/" not accessible even after retry; status code 0: Get "https://thanos.io/tip/thanos/getting-started.md/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)
		README.md:24: "https://thanos.io/tip/thanos/design.md/" not accessible even after retry; status code 0: Get "https://thanos.io/tip/thanos/design.md/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

Before doing the PR I did skim through the CONTRIBUTING guidelines but didn't saw anything specific to mixins/docs so I just followed the afore-linked mixin docs.


Resharper 7.1 support?

Hi
I have Resharper 7.1 which I use with VS 2012.
I am not able to use the new xunit 2.1.0 with Resharper as the xunit plugin is expecting xunit.dll which is no longer present in the new xunit 2.1.0
Can someone guide me on what plugin supports both Resharper 7.1 and xunit 2.1.0
Thanks

Sorry, there isn't a version of the plugin for 7.1 that runs xunit 2. The first version that supported xunit 2 was for 8.2.


[FABN-1626] update dependencies

@harrisob @bestbeforetoday I believe this PR is now ready to go into master


version.model should return None if no model

Description
There should be no instance where version.model should return a model type class when there is no valid model present.
Fixing this issue: https://roboflow.slack.com/archives/C056ZUJPK08/p1719359598748219
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How has this change been tested, please provide a testcase or example of how you tested the change?
Locally
and here: https://colab.research.google.com/drive/1rnYv49x4oVWt--O3alw2wg6pr2qNapEO?usp=sharing
Any specific deployment considerations
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs

[ ] Docs updated? What were the changes:

Thanks @LinasKo !

What I cannot evaluate is whether prior behavior, creating the model object without a matching model on the api, is valid use case somewhere.

I strongly believe that creating a model object when there is no model present is invalid behavior because the object it creates, a child of an InferenceModel, and its methods predict and load_model will fail because it doesn't exist. Doing so also makes it impossible to determine from the package that a model does or does not exist.

One other request: there's a test.py, which I think was included by accident.

Yup, I need to revoke my key too. Thanks for catching!

Sorry, fixed a failing test. @LinasKo can you re-approve?

M'afraid test.py snuck its way into the commit again :wink:
What I'm seeing is - the model may not exist, but that's valid only in a project version where it's not been trained yet. Is that right?

M'afraid test.py snuck its way into the commit again 😉
You would think i would learn, but no.

the model may not exist, but that's valid only in a project version where it's not been trained yet. Is that right?
Yes, where it's not been trained. (or uploaded, but the same thing)


Incorrect presentation of Oracle date 2020-12-27 when using DBeaver format d/MM/YYYY

System information:

Operating system (distribution) and version: Windows 7 Pro 64 bit
DBeaver version 7.1.3
Additional extensions: None

Connection specification:

Database name and version: Oracle 11g
Driver name: Oracle
Do you use tunnels or proxies (SSH, SOCKS, etc)? : No

Describe the problem you're observing:
select to_date('2020-12-27','YYYY-MM-DD') from dual; when executed with native timestamp formatting turned off is displayed as 27/12/2021, ie has the wrong year.
Steps to reproduce, if exist:

Execute query select to_date('2020-12-27','YYYY-MM-DD') from dual; with native date/time format ticked, observe result date is correct (in my case this is displayed as 2020-12-27 00:00:00 but it depends on your local NLS setup)

Observe is correct date:

Change DBeaver timestamp format to d/MM/YYYY: (note that although we are formatting a DATE, it has to be entered in the TIMESTAMP format section due to bug #8673 )

Execute same query, observe date is incorrect (has wrong year):

Thank you for the report. I've added 1 more step to reproduce:

"Execute query select to_date('2020-12-27','YYYY-MM-DD') from dual; with native date/time format ticked, observe result date is correct (in my case this is displayed as 2020-12-27 00:00:00 but it depends on your local NLS setup)"
"Change DBeaver timestamp format to d/MM/YYYY: (note that although we are formatting a DATE, it has to be entered in the TIMESTAMP format section due to bug #8673 )"
Disable use native date/time format function
Execute same query and see the date in ResultSet

Actual result: the date is incorrect (has wrong year):

@mark2016   So. In DBeaver in Data Formats settings we use Java date patterns, where the pattern case of letters is also important.
https://stackoverflow.com/a/32847390/14220989
Use "yyyy" in pattern instead "YYYY'.

Ah fantastic didn't realise DBeaver used the Java date format patterns to format dates.  Is this in the DBeaver documentation, I can't find this fact that it uses Java date format patterns mentioned anywhere. eg https://github.com/dbeaver/dbeaver/wiki/Managing-Data-Formats makes no mention of what date format pattern to use.  I assume you mean Java Simple Date format patterns?  In which case, what is a good reference for these please (Sorry but I am totally unfamiliar with Java!)

@mark2016 Well noted, we will add this to DBeaver documentation.


configure assumes ldconfig can be called and that CuDNN is installed in a system library location

The configure script calls "ldconfig" to locate the CuDNN library but this makes 2 assumptions that can be wrong:

It assumes that "ldconfig" can be called. However, on some GNU/Linux systems such as openSUSE Leap 42.1, only root has it in their path. (On Leap 42.1, normal users get the desired output from "/sbin/ldconfig -p".)
It assumes that the CuDNN library is installed in a system library location that is searched by ldconfig. However, users may install it in their home directory and use LD_LIBRARY_PATH to load it for various reasons. I, for example, was not fully satisfied from reading the licence terms that I am allowed to share the library with other users of the system and therefore did not install it system-wide as root.

Severity is low as normally the CuDNN library location should be auto-detected from the CuDNN library path before "ldconfig" is tried.
How to reproduce:

git clone this repo on a system with ldconfig not in your PATH
cd tensorflow and run ./configure
when asked for the CuDNN path, enter a valid and readable path (to avoid other errors), for example /usr/bin, that does not contain CuDNN
Error message: ./configure: line 337: ldconfig: command not found

Workaround options:

First double check the CuDNN library path (the default path suggests that the last component "lib64" or "lib" should be omitted) and verify that standard folder names are used under this location for library and header files, for example "lib64" and "include".
If you can call /sbin/ldconfig and if CuDNN is in a standard system library location the user can temporarily add /sbin to their PATH before running "./configure"
Edit the "configure" script to provide the location manually, for example CUDNN_PATH_FROM_LDCONFIG="$HOME/local/cuda/lib64/libcudnn.so"

A fix should test whether "ldconfig" can be called before trying to call it. Also try /sbin/ldocnfig. Given that the library should normally be found already earlier in the code using the user-provided CuDNN path, a simple solution may be to set CUDNN_PATH_FROM_LDCONFIG to the empty string if ldconfig cannot be called.
If you like to automate the locating of the library as much as possible, you could furthermore check all locations in LD_LIBRARY_PATH.

Thanks for bringing this to our attention. It would be nice if the configure script was smarter about discovering this library. As for ldconfig, wouldn't it work if it was just changed to /sbin/ldconfig? Where else could it be?
Please be advised that OpenSUSE isn't in our support matrix. Our goal is to support Ubuntu Linux 14 LTE to 16. Mac OS X El Capitan. CentOS 7 and above. So it might be best if we marked this contributions welcome.

TLDR: A solution may be to set PATH="$PATH":/sbin at the start of the configure script. This way, if the system or the user has a preferred "ldconfig" somewhere else it will be used and if not the script will automatically fall back to /sbin/ldconfig.
The FHS http://www.pathname.com/fhs/pub/fhs-2.3.html only mentions "ldconfig" in the /sbin section. From this point of view, it should be safe to assume that "ldconfig" is always in /sbin (if it is installed at all -- the FHS says it's optional). However, it's best practise to respect the preferences expressed in PATH.
My first thought was that "ldconfig" cannot be in /sbin on the supported platforms as otherwise the "configure" script would not work on these platforms because normal users don't have /sbin in their PATHs. However, most Ubuntu users have sudoer rights. That's probably why this issue hasn't been noticed before.

That makes sense. In that case, we'd be grateful if you joined the ranks of TensorFlow contributors and sent us the one line change you proposed. CC me and I'll review it.

Trivial code change #6848 rejected as drpngx insists on Google's Contributor License Agreement to be signed and I don't have time to review it and the documents it refers to.
Anybody with CLA please take the 30 seconds to implement "temporarily add /sbin to PATH for ldconfig call" in your own way and contribute a patch (total time <5 minutes). (Don't copy my solution. Even though I would be ok with you copying it as I think it is trivial code, a Google bot may detect that it is identical or similar to a previously rejected pull request and reject it on these grounds.)

drpngx was only following Google policy. The policy is designed to protect the interests of the TensorFlow community. It's applied evenly and uniformly to all contributions. So I hope you'll reconsider. I could easily make the change myself. I just feel that since you were able to identify an issue with TensorFlow along with its solution, you deserve to be able to take public credit as the person who solved it.


add ability to start node from a snapshot

after a new node accepts an invite to join the chain they should be able to fast forward their sync by bootstrapping with a snapshot

@smondet pointed out that you need a source of truth to validate that the last block of the snapshot is legit

Done


PnpWebpackPlugin  non-existent

PnpWebpackPlugin  non-existent
I need to use PnpWebpackPlugin to process files outside the directory

Hey @lifetin,
Sorry for the delay, it should work per the instructions in Webpack. Try adding it and see if it works.
Regards


refactor(mempool_infra): create an alias to all trait bounds in remote server

Stack:

#939
#938 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.