nwg-look: init at 0.1.2

Description of changes
Add nwg-look, a wayland / wlroots replacement for lxappearance and add myself to maintainers list.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

On further testing, the application fails because it can't write to ~/.config/gtk-3.0/settings.ini which is a symlink into the nix store. Not sure how to go about fixing that problem.

We've tested this and it's stuck at Building subPackage .

ah, no it's building gtk, and it's doing it on one core. that's wildly bad.

https://github.com/NixOS/nixpkgs/pull/246601


Relax lint checks on autogenerated protobuf packages

This was raised by a comment from @displague
Off the top of my head, the only linter I can think that this might impact is the gofumpt checker.

I lean towards not doing this. I'd rather have the go:generate step run goimports/gofumpt. I find it easier to avoid snowflakes.

If the make tasks (fmt,fix,gen?) do the right thing, and the contributing guides say as much, I don't think we would need to bog down the Go generator process.


plot() doesn't work.

Hi, i have tried simple plotting for SE3
but it dosent show anything.
from spatialmath import * import matplotlib.pyplot as plt X = SE3(1,2,3)*SE3.Rx(30, 'deg') print(X) X.plot()
this code print out the X but not the figure. and it doesn't show any error.
is there anything i missed?
my python version is 3.6.8

Maybe something in your Matplotlib config?  I'm using Python 3.8.5 and MPL 3.3.4

I check with several different computer with different python(3.6, 3.7, 3.8) but not sure about MPL versions, i will recheck and comback!

do you use MPL for other things?

In the code, no i only tried to plot the SE3(1,2,3)*SE3.Rx(30, 'deg').
`>>> from spatialmath import *

import matplotlib.pyplot as plt
X = SE3(1,2,3)*SE3.Rx(30,'deg')
print(X)
1         0         0         1
0         0.866    -0.5       2
0         0.5       0.866     3
0         0         0         1

X.plot()
`
and my MPL version is 3.3.4

In fresh python session try
>>> import matplotlib.pyplot as plt
>>> plt.plot(1,2,'ok')

Oh, i got it.
reading this

T = SE3(1,2,3) * SE3.Rx(30, 'deg')
T.print()
1         0         0         1
0         0.866025 -0.5       2
0         0.5       0.866025  3
0         0         0         1

T.printline()
t =        1,        2,        3; rpy/zyx =       30,        0,        0 deg

T.plot()

I thought plot() has plt.show() too but i guess i forgot to add plt.show()
sorry for bad issue.


Windows: Security warning based on server OS

Signed-off-by: John Howard<EMAIL_ADDRESS>@swernli @duglin @tiborvass
This PR is part of the proposal described in docker/docker issue 10662 to port the docker daemon to Windows. This fixes the problem whereby the Windows client always output a security message about file permissions on the basis that the daemon was running on Linux. As we now have a Windows daemon up and running, the daemon now returns it's OS on the build call. That is parsed by the client, and if the daemon isn't Windows (to also allow for FreeBSD...), only then does it output the security message.
Note: As a result of this change, the daemon will return a Server HTTP header such as "Docker/1.7.0-dev (Linux)" mirroring HTTP standards (http://en.wikipedia.org/wiki/List_of_HTTP_header_fields#Response_fields)

I think having the daemon return this info (per https://github.com/docker/docker/pull/13740/files#r31722051 ) could be useful to people. Likewise, I think we may want to consider, in a different PR, including the GOOS in the User-Agent header that the CLI sends.

Design +1

LGTM

Rebased

Rebased

LGTM

LGTM


rototrans matmul

Hi,
I think I'm doing something wrong but when I use matmul on rototrans object, the results is a scalar.

I found a solution (not the best) to correct this bug using numpy Einstein Summation
from pyomeca import Rototrans
import numpy as np

rt_1=Rototrans.from_random_data()
rt_2=Rototrans.from_random_data()

rt_1.shape #out :(4,4,100)

rt_2.shape #out :(4,4,100)

rt_12=np.einsum("ijt,jkt->ikt",rt_1,rt_2)
rt_12.shape #out :(4,4,100)

Hi @SebastienCordillet
This is indeed a good solution. I thought I already implemented this Einstein sum in Pyomeca, but it may have been removed when we refactor for the 2.0 version. In any case, this is what I would have had added to the Rototrans class, so good solution ;)
If you feel wild, you can add it to Pyomeca and open a pull request on this!


iFrameResizer not working in iOS.

I tried to view my company's site at http://www.itup.pt but what I get is the following:

The server hosting this already has the most recent version (3.5.1) installed. Here is the javascript we have:
`
        iFrameResize({
            log                     : true,                  // Enable console logging
            enablePublicMethods     : true,                  // Enable methods within iframe hosted page
            resizedCallback         : function(messageData){ // Callback fn when resize is received

            },
            messageCallback         : function(messageData){ // Callback fn when message is received

            },
            closedCallback         : function(id){ // Callback fn when iFrame is closed

            },
            heightCalculationMethod : 'max'
        });

    `

The site displays fine in mobile size in Chrome Windows. If I missed any options I should be using/trying, I would appreciate anyone pointing that out. Any other clues appreciated.
Thanks
Pedro Remedios

I have the same problem. Did you find any solutions?

I found out what was wrong. Apparently I had to tell iFrameResizer who big the screen was as it seems it's not doing very well. These are the options that I used for that:
maxWidth: screen.width,
minWidth: screen.width,
sizeWidth: 'true'
Hope this helps.

@premedios
Thanks, Your solution is working for me.
` var screenWidth = screen.width;
if (browser.iPad) { screenWidth = screenWidth - 300;}
if (browser.iPhone) { screenWidth = screenWidth - 50;  }
S = {
------
maxHeight: 1 / 0,
maxWidth: screenWidth,
minHeight: 0,
minWidth: 0,
resizeFrom: "parent",
scrolling: !1,
sizeHeight: !0,
sizeWidth: true,
------------------
};`

Thank you so much for the help.
It really worked for me.

I was having a problem on mobile browsers (both android/iOS) that when the iframe loaded, the height kept on increasing and increasing and increasing. So When I used this, it resolved the issue.
iFrameResize({ log:true,  interval:1,  tolerance: 1,  resizeFrom : 'parent',  heightCalculationMethod: heightResizeMethod,  resizedCallback: function(messageData){  iframeResizerLoaded = true;  } });


increase the threshold for OSDCPULoadHigh

alert was getting triggered in normal workloads, so we've increased the threshold

@weirdwiz DCO failing

/cherry-pick release-4.15

/retest

/override ci/prow/ocs-operator-bundle-e2e-aws
No point running it on this PR since this test doesn't test alert files.

/retest

/retest

/cherry-pick release-4.15


Error installing 'patcher;v4

I'm using version @v2 with cmdline-tools;7.0.
When I start the setup, I run sdkmanager --list_installed and 'patcher;v4' is not shown.
Running the command sdkmanager --install "patcher;v4", an error appears (Warning: Failed to find package 'patcher;v4') and the action stops.
Does anyone know or have experienced this?

Hello Paulo. Why are you using 7.0? Is it for legacy project support? Would you care to try and use v3 version of this action with a current version of cmdline-tools?

OK, so the patcher is missing from all sdk versions. Still unsure why

There's no patcher on my dev box either if I do a clean install. What are you using it for? Is it possible that was deprecated?


[chart-fees-earned] Add command

Add the chart-fees-earned command

https://github.com/niteshbalusu11/lndboss/pull/14


Incomplete. Volume on S2D deleted using this method is not fully deleted and does not free space

This is incomplete.
Deleting a volume on a S2D pool does not free the corresponding space. Deleted volume is not displayed anymore in the WAC console. But the overall free space does not increase by the amount of the deleted volume.
Using the old Server Manager, File Server, Storage pool : the previously deleted volume can still be seen there, with a status "unknown". You have to delete it there, too. Then, the corresponding disk space is freed, and the deletion is complete.

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

ID: 22d8c3d3-7d23-0372-8912-bd0f969a7fe0
Version Independent ID: d1a1589c-2cd2-af6a-0eb3-e28178a3e2b7
Content: Deleting volumes in Storage Spaces Direct
Content Source: WindowsServerDocs/storage/storage-spaces/delete-volumes.md
Product: windows-server
Technology: storage-spaces
GitHub Login: @iangpgh
Microsoft Alias: jgerend

I no longer work on this team (v-iap)

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


macOS: iTerm crash, UI elements gone

I used pywal on my MacBook and have a significant problem now. First, iTerm crashed, then the desktop wallpapers went black and all the OS elements like the dock and the ability to switch between apps with Cmd-Shift etc. or the window overview (F3) are gone resp. don't work anymore. I also can't set any wallpaper with the settings app.
iTerm seems to be connected to the problem. It wanted to do something like a benchmark or similar when it crashed (I couldn't really read it, but it said something like "CPU test" or similar.) Anyway, if I start iTerm now, it doesn't work, no window shows up.
I already logged out and back in, nothing changed.
Does anyone have an idea what process could be connected? I already tried killall dock and it says "no process found". I also restarted the WindowServer by sudo killall -HUP WindowServer, but no change.
I ask here, because someone might know with which processes pywal communicates when changing the wallpaper in OSX.
Thanks

What version of MacOS are you running?

I used Mojave (10.14.4) and I found that the issue was already discussed here: https://github.com/dylanaraps/pywal/issues/330
So, the solution was to delete this file:
rm ~/Library/Application Support/Dock/desktoppicture.db

For copy-pasters, the command is missing a slash:
rm ~/Library/Application\ Support/Dock/desktoppicture.db


Compatibility with IntelliJ IDEA 2023.3.+

Would it be possible for the plugin to be published to support the newer versions of Jetbrains IDEs?

some details from the logs:
Plugin 'Structurizr DSL Language Support' (version '0.3.2') is not compatible with the current version of the IDE, because it requires build 232.* or older but the current build is IU-233.11799.300

I really don't want to rollback to a previous version.  Can we get a quick bump on this?

My apologies for the delay, I haven't really gotten around to giving this plugin some much needed attention. Unfortunately, my unit testing setup led to recurring compatibility issues when upgrading to newer IntelliJ versions. So to update the plugin to IntelliJ 2023.3 wasn't as easy as changing a few Gradle properties.
I've now reverted my unit testing setup to the default setup, as per the Platform plugin template, so future updates should be a lot less painful 😄.

I'm going to publish the updated version today. As every version needs approval from JetBrains, I expect the new version to be available in a few days maximum.