v1.5.8 vCode 49 Pre-release

Pre-Release v3 SLS 1.5.8 vCode 49 pre-v11
As described in the link, the app has gone through some changes.
I need as many people as possible to help debug them for now.
Thanks,
Austin H.

On FireTV (v1), starting the app just flashes a white screen briefly and then it exits.

This is a somewhat unusual device for me.
Do you have any debug logs?

The main issue with non-standard android products is library dependencies and certain other things.
Did it work before?

I understand the problem of this non-standard device. If the app would work, that would be nice, but if that's too much work, also that is fully understandable.
Working before: Yes. And no. The app loaded, the settings could be adjusted, and relatively long it even scrobbled properly. Until after some OS update (I don't know anymore at which point) the scrobbling stopped. Still, the app didn't crash as the current pre-release does.
I'm not an SW-developer, but more on the algorithmic side. Still, if I can somehow help, I'm happy to do so. Do you have an idea where to look for the logs?

Amazon FireTV Debug
SLS Debugging

Could you share your Android Operating system version please too?

Log starting from opening the app and ending after the crash: https://hastebin.com/zocidifaga.makefile.
The logcat command from your instructions didn't work as expected, but dumped also various other information. This is probably related to this: https://forums.developer.amazon.com/questions/55585/firetv-crash-call-stack-are-not-available-in-adb-l.html
The OS is "Fire OS <IP_ADDRESS>", which was branched from Android 5, to my understanding.

Pre8 is reporting the last added music player after the colon instead of the active player.
The active player is pocketcasts.  The player being reported in the notification is Amazon music.
(url)https://photos.app.goo.gl/HqaqjWQeBBb54Zcu6

Thanks nswint and drobec,
I am currently looking into resolving both your considerations.
Thanks,
Austin H

@drjobec any chance you could try this .apk ?
sls-v1.5.8-vCode-49_v8.apk-debug.testing.zip

Looking slightly better.
The permission page opens, but the green/red buttons to control toggle the setting are on the right border of the screen and practically impossible to control (can't see where the selection currently is and even with some liberal button smashing I was able to toggle just one of them). Also, assuming that I managed to hit the "Continue", it didn't close the page. Smashing the back-button on the remote showed that the normal setting page is behind the permissions, but that's now blocking everything.

Did some read text appear for you on the bottom of the permissions pages?

@drjobec
https://github.com/simple-last-fm-scrobbler/sls/releases
Please install version 10 of the pre-release.
It will contain instruction on how to fix the problems.

On the permissions screen, "Notification Listener" is gray, while others are green. With some blind clicking (using a remote doesn't show where the cursor is at) displayed the red hint text about notifications ignore list. Checking the device settings still shows all notifications from SLS being allowed.

Sorry it's called "notification access".

Maybe I just didn't find it, but I found no way of controlling the app permissions in this version of FireOS. It can be because it's still based on so old Android API (v22). Instead, all permissions should be presented in the manifest in apk, and I didn't find BIND_NOTIFICATION_LISTENER_SERVICE listed there.
Could this be the issue?

Yes, this is exactly the issue unfortunately.
I am researching now.

I am sure you were thorough but did you look here ?
Settings > Sounds & Notifications > Manage notification listeners

That doesn't exist on this gen1 device. There are:

Settings > Notifications (displays current notifications)
Settings > Display & Sound (audio and video settings)
Settings > Applications > Manage Installed Applications (launch, force stop, uninstall, clear data, clear cache)
Settings > Preferences > Notification Settings (turn on/off Do not disturb, turn on/off notifications from individual apps)

It looks like they have removed this possibility of notification reading from their Operating System.

This means, like I said previously, device specific code and reading the old way for broadcasts.

I can add a disable notification listener button to the options list if you want?
The downside is that it will miss the new functionality offered.
Unfortunately the new functionality is required to try new music apps and hence Notification Listener.

@nswint I have your fix in a minute.  pre-v11

@nswint It's at the top there.

@nswint It's at the top there.

Thanks. pre-v11 is super broken now

I wasn't prompted for the new/updated listener permissions.  I reinstalled and saw the requests for the new permissions. (Reinstall gave me a host of new issues with session keys and authentication.)
After all 4 permissions are allowed the app automatically continues without out pressing the continue button
Last.fm give wrongs username/password/token errors.  I've cleared the username and session key.
I'm using the right username/password
Pocketcasts show empty now playing information.
Pocketcasts no longer scrobbles
Google Play music only scrobbles once and doesn't scrobble any more
Settings seem to persist now.  Are these saved locally in a folder or in google cloud now?

No scrobble information
https://photos.app.goo.gl/pysXrsRDjHPk4UmB9
Scrobble from 1.5 songs prior. The song reported 2 minutes prior that it scrobbled but I finished the song 6 minutes prior.  I have the setting to submit at 50% of the song so it should have scrobbed about 8 minutes prior.
https://photos.app.goo.gl/zJZvurQebzgukJJT9

I wasn't prompted for the new/updated listener permissions.  I reinstalled and saw the requests for the new permissions. (Reinstall gave me a host of new issues with session keys and authentication.)
reinstall sometimes affects shared preference keys (aka I cannot change that)

After all 4 permissions are allowed the app automatically continues without out pressing the continue button is expected behavior

Last.fm give wrongs username/password/token errors.  I've cleared the username and session key.
I'm using the right username/password
** Can you share a bit more information? If you're a developer a debug log dump could help me out.**

Pocketcasts show empty now playing information. this will happen if you are not logged in

Pocketcasts no longer scrobbles this will happen if you are not logged in

Google Play music only scrobbles once and doesn't scrobble any more  something is wrong

Settings seem to persist now.  Are these saved locally in a folder or in google cloud now?  locally

I wasn't prompted for the new/updated listener permissions.  I reinstalled and saw the requests for the new permissions. (Reinstall gave me a host of new issues with session keys and authentication.)
reinstall sometimes affects shared preference keys (aka I cannot change that)
if you set listener permissions once, you should be ok
After all 4 permissions are allowed the app automatically continues without out pressing the continue button is expected behavior
Last.fm give wrongs username/password/token errors.  I've cleared the username and session key.
I'm using the right username/password
Can you share a bit more information? If you're a developer a debug log dump could help me out.
Pocketcasts show empty now playing information. this will happen if you are not logged in
Pocketcasts no longer scrobbles this will happen if you are not logged in
Google Play music only scrobbles once and doesn't scrobble any more  something is wrong
Settings seem to persist now.  Are these saved locally in a folder or in google cloud now?  locally

What is an email address that I can mail you the link to the debug log?  Debug logs sometimes might contain some passwords and such and the number of bots that comb github for passwords and other credentials probably outnumber living humans.

<EMAIL_ADDRESS>

Ok I worked last night and this morning.
It seems that the notification controller is much more dense than I thought.
I was not issuing access to the media session correctly nor was I registering the callbacks correctly.
After the first callback the whole system fails to recognize the music players.
Apologies for the delay and issues therein.

https://github.com/simple-last-fm-scrobbler/sls/releases/tag/v1.5.8-pre-v12

I might as well restart the one week rule for pre-release.
That will mean waiting until September 9th or 10th until I release the final apk.

@nswint  Apologies if this question seems crass, yet I wonder if the new release is working well for you?

@drjobec  I think I need to add a special apk for your device or add a bypass option to the permissions system for legacy operating systems or special operating systems. I will create a new issue.

I leave it to your consideration if the extra effort is worth it. Personally, I would appreciate it, but such "old" systems are probably getting already quite rare. The reason I'm still using the Gen1 device is that it's still working, and to date it's the only FireTV with a separate digital audio-out allowing listening to music without the TV being on (without an AVR).
It would be the easiest, if the required permission could be granted somehow automatically during installation, but I know too little of Android apps and permissions to know if this is even possible.
Thanks anyway for your effort!

No it's okay. I'll make it happen.
Just give me some time.
Like I said. You can bypass the functionality, but you will need to rely on old broadcasts.
Android before Oreo will work.

So far so good.  No issues running on  Android 10.
On Wed, Sep 4, 2019, 10:50 AM Austin H<EMAIL_ADDRESS>wrote:

@nswint https://github.com/nswint Apologies if this question seems
crass, yet I wonder if the new release is working well for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/simple-last-fm-scrobbler/sls/issues/479?email_source=notifications&email_token=AAKWXVW6V7RA6TDFZFVBMSTQH7DMBA5CNFSM4IP3ZZK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD532X3A#issuecomment-527936492,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKWXVXPIUKHY3L4NSLILQ3QH7DMBANCNFSM4IP3ZZKQ
.

#508 @drjobec


Third Terraform Recipe - Kafka and Flink

What changed, and why it matters
resolves https://github.com/aiven/devportal/issues/883
Feedback requested:

Please run the Terraform code and ensure that it works (I did multiple times and works from my end)
source and sink names are used both for Kafka topics and Flink tables. Should we have distinct naming?
I tried to write the paragraph just below the code block to describe what's happening in this setup. Please let me know if you'd like this paragraph to be above the code block
The explanation of the setup - is it accurate or did I miss anything?
Did I miss anything according to the DevPortal style guide? I'm a bit confused with the Terraform resources which I wrote like literals with double-quotes inside "aiven_service_integration"
The learner might be confused to see data.aiven_project.dev-advocates.project and use the value without changing. Do you suggest I use something like data.aiven_project.[YOUR-PROJECT-NAME].project?
Anything else that you find would improve this recipe

Help Wanted
Testing
What sample data could we feed into the source topic to see this setup in working?
Aiven metric integration
Is there a way we can direct some Aiven metrics into the source topic and then have the Flink job filter metrics beyond a certain level to the sink topic? Looking for help on how to integrate Aiven metrics with this setup.

Ok, I had a look at it, I'll change few bits of the SQL in order to be compliant with https://github.com/aiven/fake-data-producer-for-apache-kafka-docker

Hi All! I changed the SQL so we can use the https://github.com/aiven/fake-data-producer-for-apache-kafka-docker to generate data! I also added a note on how to test it, hope it's ok!

@dewan-ahmed can you check if it all makes sense (and works)?

@dewan-ahmed can you check if it all makes sense (and works)?

Thanks Francesco; checking it shortly.

@ftisiot I checked and the fake data generates successfully. The only tweak I had to make is on the Flink job filter where I set the threshold to 85. This is because the original Python fake data metrics was already generating values over 70.
Thanks again.


Updating Entity Translation to fix XSS vulnerability

What's this PR do?
Changed the version of Entity Translation from dev to beta5 to fix an XSS security vulnerability
How should this be reviewed?
You can run ds build locally
Any background context you want to provide?
http://cgit.drupalcode.org/entity_translation/commit/?id=f813030

👍


RFC: Bpftrace Compiler and Runner

Bpftrace-Compiler
Bpftrace-Compiler is the counterpart to the bpftrace-aotrt tool in the debug container in EVE.
bpftrace-aotrt needs a compiled bpftrace script specific for the node architecture and EVE
version.
The bpftrace-compiler helps to do this by creating a specific virtual machine with the same
architecture and kernel and run bpftrace in it to compile your bpftrace script.
How it works

Step
Local Machine
Eve Node

1
Connect to EVE (ssh/http-debug)
Accept connection

2
Retrieve architecture, userspace container version
Answer with architecture, userspace container

and eve-kernel version
version and eve-kernel version

3
Create VM with architecture (arm64
amd64), userspace container

and eve-kernel

4
Run bpftrace on bpftrace script from 9p share in created VM

5
Shutdown the VM

6
Copy compiled bpftrace script to EVE
Retrieve file

7

Run bpftrace with provided file

8
Collect the output and show it to the user
Forward output of bpftrace

For more information see README.md in this PR.

Why eve-tools, not just tools? =)

Christoph, please take the trouble to add a description or the context of the problem you are trying to solve to this PR.

Why eve-tools, not just tools? =)

tools/ seems to be build tools ...

@christoph-zededa I saw your comments on the linuxkit repo, and how you use it kind of like a library surface here. What is it that this does, that it needs to read yaml files and process them?

Christoph, please take the trouble to add a description or the context of the problem you are trying to solve to this PR.

What is it that this does, that it needs to read yaml files and process them?

I added some more context to the Readme file: https://github.com/lf-edge/eve/pull/4150/files#diff-b023a85c31567758e69d525e407bad17acaadad243d1c592cc3f0b0b6a51cd9e

I have a few questions.
First, is this connecting remotely to eve and then executing some things? It would be the first time we do that. That was how I read this part of the README:
# How it works

1. Connect to EVE (either via SSH or Http-Debug)
2. Determine architecture and eve-kernel version
3. Create VM with specific architecture and eve-kernel
4. Run `bpftrace` on bpftrace script which is mounted inside via 9p
5. Shutdown the VM
6. Copy the compile bftrace script to EVE
7. Run `bpftrace-aotrt` on EVE
8. Collect output and show to user

Or did you mean, "you, user, go connect and then run the command", in which case this makes sense, might be worth making it a little more explicit in the README.
The README also says:
The `bpftrace-compiler` helps to do this by creating a specific virtual machine with the same
architecture and kernel and run `bpftrace` in it to compile your bpftrace script.

## How it works

1. Connect to EVE (either via SSH or Http-Debug)
2. Determine architecture and eve-kernel version
3. Create VM with specific architecture and eve-kernel
4. Run `bpftrace` on bpftrace script which is mounted inside via 9p
5. Shutdown the VM
6. Copy the compile bftrace script to EVE
7. Run `bpftrace-aotrt` on EVE
8. Collect output and show to user

So is this creating the VM? How do I create the VM? Which part of all of this is bpftrace-compiler?
Separately, I still don't understand why this needs to parse yaml files for linuxkit packages and build and such?

I have a few questions.
First, is this connecting remotely to eve and then executing some things? It would be the first time we do that.

Yes, it is exactly doing this.

So is this creating the VM?

Yes

How do I create the VM?

bpftrace-compiler does this for you automatically.
You can use bpftrace-compiler debug command to run it manually.

Which part of all of this is bpftrace-compiler?

Everything ;-)

Separately, I still don't understand why this needs to parse yaml files for linuxkit packages and build and such?

Because the members of pkglib.Pkg are private and as far as I see can only be set by loading a yaml file. (https://github.com/linuxkit/linuxkit/blob/master/src/cmd/linuxkit/pkglib/pkglib.go#L78 )

Yes, it is exactly doing this.

So this is a tool that runs locally (my Mac/Linux/Win/whatever) and connects to a running eve to start a VM to run a bpf program?

Because the members of pkglib.Pkg are private and as far as I see can only be set by loading a yaml file.

I meant a little more basically. Why do we need to parse yaml files at all? Whey do we need to be doing anything at all in pkglib? If this is connecting to an EVE and starting a VM, isn't that basically, some ssh and some local commands?

So this is a tool that runs locally (my Mac/Linux/Win/whatever) and connects to a running eve to start a VM to run a bpf program?

No, this is a tool that runs locally  (my Mac/Linux/Win/whatever)  to start a VM to compile a bpf program and connects to a running eve to run a bpf program.
I see, I have to make that part in the Readme more clear.

Oh, yes, significantly easier to understand. So this tool basically does:

Discover info about the machine (version and arch)
Starts a local VM and does something local with it then exits (compile to arch/version-appropriate BPF bytecode?)
Transfers the compiled bytecode to the EVE device and runs it
Collects the output

Is that right? What does the local VM do? I guess it is more than compiling, because I can cross-compile eBPF programs using local tools. And it isn't likely to be running the eBPF program, since its value is running on the target EVE device.

Is that right?

Yes

What does the local VM do? I guess it is more than compiling, because I can cross-compile eBPF programs using local tools.

So, the pure eBPF program does not need to be cross-compiled (it is running in a VM after all), but for tracing it heavily depends on the architecture and the EVE kernel, especially /sys/kernel/tracing to read function arguments, struct members, function addresses, ...
In the future I want to add:

additional kernel headers, f.e. needed for https://www.gcardone.net/2020-07-31-per-process-bandwidth-monitoring-on-Linux-with-bpftrace/#the-full-program
userspace programs to be able to hook into userspace functions, f.e. https://github.com/bpftrace/bpftrace/blob/master/tools/sslsnoop.bt

but for tracing it heavily depends on the architecture and the EVE kernel, especially /sys/kernel/tracing to read function arguments, struct members, function addresses, .

Are you saying that it needs to be compiled in a VM, because it is doing tracing that is dependent on the actual kernel itself? Hence we run it in a local VM to get just the right kernel and arch matching what it will be running on in EVE? I didn't know that was necessary, learn something new every day.
That answers a lot of it, thanks for clarifying the README.

I still don't know why it needs to be reading linuxkit pkg yml files. What is it doing there?

Are you saying that it needs to be compiled in a VM, because it is doing tracing that is dependent on the actual kernel itself? Hence we run it in a local VM to get just the right kernel and arch matching what it will be running on in EVE? I didn't know that was necessary, learn something new every day.

Yes

I still don't know why it needs to be reading linuxkit pkg yml files. What is it doing there?

Is there a better way to provide the config than https://github.com/lf-edge/eve/pull/4150/files#diff-690b3bc82199ba931ce2c64173ef2b08142a8028cd6a24db47555d5dd2ae126cR156 ?

I think you are missing my point. Why does it need to provide a config at all? What this is doing:

Discover info about the machine (version and arch) - ssh, no need there
Starts a local VM and compile to arch/version-appropriate BPF bytecode - local, run some VM, no need there
Transfers the compiled bytecode to the EVE device and runs it - ssh, no need there
Collects the output - ssh, no need there

At what point does it need to start modifying linuxkit ymls or building packages?

At what point does it need to start modifying linuxkit ymls or building packages?

At 1.999999: Create VM image with architecture and eve-kernel

At 1.999999

It took me 3 reads to get what you meant by that. 😆

Create VM image with right architecture and eve-kernel

Aren't we creating a VM image locally on the user's desktop?
Oh, now I get it. You are using linuxkit to build a quick VM image and run it? Sort of the equivalent of lkt build vm.yaml and then lkt run vm? Maybe not exactly that, but that idea?

Aren't we creating a VM image locally on the user's desktop?
Oh, now I get it. You are using linuxkit to build a quick VM image and run it? Sort of the equivalent of lkt build vm.yaml and then lkt run vm? Maybe not exactly that, but that idea?

It is created on the user's desktop with linuxkit. Yes, kind of like that.

It is created on the user's desktop with linuxkit. Yes, kind of like that

OK, now I get it. That was the part I didn't understand, why you needed this at all. Now that I do, I can try and help with it.
A few questions:

Is there any reason not to hard-code the OS build yml right into the file, and then call linuxkit build? We do that in some other places.
Why do we need the pkglib? Aren't we just building an OS runnable image, so it just needs the equivalent of rootfs.yml, but a greatly simplified one? I am working on one right now for installer image, will do verification as well.

1. Is there any reason not to hard-code the OS build yml right into the file, and then call `linuxkit build`? We do that in some other places.

2. Why do we need the pkglib? Aren't we just building an OS runnable image, so it just needs the equivalent of `rootfs.yml`, but a greatly simplified one? I am working on one right now for installer image, will do verification as well.

The VM has to be created differently depending on the EVE version you want to run the bpftrace script on. Step 1 - https://github.com/lf-edge/eve/pull/4150#issuecomment-2298422083

You are saying that if we hard-code into the go code the following yaml:
kernel: lfedge/eve-kernel:123
init:
- lfedge/init:456

Then the number for kernel or some others might change, not just as we upgrade this bpftrace package, but for the same version of bpftrace package, when running against different versions and architectures of EVE?

lfedge/eve-kernel:123

Yes, especially the lfedge/eve-kernel:123 f.e. when you're using f.e. a development branch or some eve-kernel branch for a special arm device.

Yes, especially the lfedge/eve-kernel:123 f.e. when you're using f.e. a development branch or some eve-kernel branch for a special arm device.

So what is the process? You need to build a custom OS yaml, but shouldn't the images used in it already exist somewhere?

if it is a released eve version, then all of that is out there published
if it is a custom built eve version (i.e. development), then the developer knows how to create it and build it

Wouldn't that leave you just needing to build using the OS yaml, which is simpler?

So what is the process? You need to build a custom OS yaml, but shouldn't the images used in it already exist somewhere?

But https://github.com/lf-edge/eve/pull/4150/files#diff-afbbbf866537944cf44446b7e2b7bf2ab9510271cc8e0b3ad2b86559b5811387 does not exist yet.

* if it is a released eve version, then all of that is out there published

Published perhaps, but not composed.

* if it is a custom built eve version (i.e. development), then the developer knows how to create it and build it

That's a bit of wishful thinking, isn't it? ;-)
So, yes, the developer could create and build it, but it's better to make it not cumbersome.

What is wrong with a little wishful thinking? 😬

Published perhaps, but not composed.

I don't understand. Can you put in place a sample OS yaml file here? Not for a package, but for an OS? Maybe that will help understand.

Published perhaps, but not composed.

I don't understand. Can you put in place a sample OS yaml file here? Not for a package, but for an OS? Maybe that will help understand.

Like this: https://github.com/lf-edge/eve/pull/4150/files#diff-7e68be30c8911b3d08261835dda8ac912821361527abe78b64ece1911d105e3d ?

Like this

I like how the filename is .yml  but the content is json 😁
{
  "kernel": {
    "image": "EVE_KERNEL",
    "cmdline": "console=null quiet vga=0x316"
  },
  "init": [
    "@pkg:./getty"
  ]
}```

What do you do then? Inject the `EVE_KERNEL` with the calculated version, and add things to `init`? And when do you build a package?

Like this

I like how the filename is .yml  but the content is json 😁

It is flow-style yaml: https://www.yaml.info/learn/flowstyle.html

What do you do then? Inject the EVE_KERNEL with the calculated version, and add things to init? And when do you build a package?

Yes, EVE_KERNEL is injected here: https://github.com/lf-edge/eve/pull/4150/files#diff-8f2e2320b87121bbe78b9650fa98f62523ad3a8580e86381afb156d7a4eae34aR30
So far nothing is added to init. The package gets build here: https://github.com/lf-edge/eve/pull/4150/files#diff-690b3bc82199ba931ce2c64173ef2b08142a8028cd6a24db47555d5dd2ae126cR33

I do understand what you are doing now. I don't have a particularly simpler way for you to do it. linuxkit wasn't really built with a library interface in mind. All of the options for building a package are pulled together in pkg_build.go, which is a cobra CLI interface.
We could extract those into a single library, to make it easier, but I am not 100% sure how much it would save you. If you can come up with one, go ahead and open a PR on it, and I will get it in.
Is this really easier than just calling out to the command-line with a fork/exec?
Either way, whatever works for you.

Is this really easier than just calling out to the command-line with a fork/exec?

During development it helps, because I can directly jump in my IDE from my code into the linuxkit code to see what it does. Otherwise I would have to go the detour via yaml parsing and command line parsing.

Ok whatever works for you. If you can think of a better library interface to linuxkit, suggest it, we can get it in.

Moar changes please

@rouming

I don't see where yetus fails ...

I don't see where yetus fails ...

yetus log shows
|  -1  |      perlcritic  |   0m  0s   | The patch generated 1 new + 0
|      |                  |            | unchanged - 0 fixed = 1 total (was 0)
and the yetus-scan.zip download has this in the perlcritic file:
eve-tools/bpftrace-compiler/import-custom-eve-kernel.pl source OK
So all good news! But perlcritic doesn't play nicely with yetus which presumably assumes that all output is bad news.
So you can ignore this yetus failure.

@christoph-zededa great stuff! Could you show the team how to use it in a live session? So more people are aware of the new facilities.

@christoph-zededa great stuff! Could you show the team how to use it in a live session? So more people are aware of the new facilities.

Yes, perhaps in one of the next TSC meetings?
I just hope to implement a simple caching method until then, because it is a bit slow - the tests take about 10 minutes to list available bpf probes and to compile a simple script (both for arm64 and amd64, i.e. those are 4 runs).

Yes, perhaps in one of the next TSC meetings?
I just hope to implement a simple caching method until then, because it is a bit slow - the tests take about 10 minutes to list available bpf probes and to compile a simple script (both for arm64 and amd64, i.e. those are 4 runs).

Good idea.
Do you want to implement the caching in the scope of this PR?

Good idea. Do you want to implement the caching in the scope of this PR?

No, I think this PR is already big enough.


please use complete sentences and not sentence fragments

THis is not a ppt presentation
check ENTIRE PAPER
here example:
Have used the python lib pandas to get tweets and clean it in required format. Used libary seaborn to represent the details in graph and taken the screenshots from it.

modified the sentences using grammerly


removed IsControlInGrace & SupportsAutoFix from csv, ADO_Organization_AuthZ_Review_Inactive_Users tabular output

Description

1.
Checklist

[ ] I have read the instructions mentioned in Contribute to Code.
[ ] I have read and understood the criteria described under submitting changes.
[ ] The title of the PR clearly describes the intent of the PR.
[ ] This PR does not introduce any breaking changes to the code.

creating new pr


Updated Skillbrains.Lightshot v<IP_ADDRESS>

Resolves #23757

PS C:\Users\Test> winget install -m "M:\Git\winget-pkgs\manifests\s\Skillbrains\lightshot\<IP_ADDRESS>"
Found Lightshot [Skillbrains.lightshot]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://app.prntscr.com/build/setup-lightshot.exe
  2.65 MB
Successfully verified installer hash
Starting package install...
Successfully installed

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I can't change l to L in the file name, okay, let's do this then.

Ah, okay.

Oof

Try closing and reopening the PR (Re-run the pipelines).

They really don't like the bots, do they 😅

URI: https://app.prntscr.com/, Validation result: Failed, Http status code: Forbidden
URI: https://app.prntscr.com/help.html, Validation result: Failed, Http status code: Forbidden
URI: https://app.prntscr.com/privacy.html, Validation result: Failed, Http status code: Forbidden
URI: https://prnt.sc/, Validation result: Failed, Http status code: Forbidden
URI: https://app.prntscr.com/license.html, Validation result: Failed, Http status code: Forbidden
URI: https://app.prntscr.com/license.html, Validation result: Failed, Http status code: Forbidden
URI: https://app.prntscr.com/build/setup-lightshot.exe, Validation result: Failed, Http status code: Forbidden

They can probably add a .validation for the url, but i don't think the bot is allowed to download the exe, so it will most likely hate this more than it hates calibre

They can probably add a .validation for the url, but i don't think the bot is allowed to download the exe, so it will most likely hate this more than it hates calibre...
Might be worth contacting Lightshot?

Yeah, I'll shoot them an email.

Yes, this isn't the sort of thing we can waive, since we can't even download the app to run antivirus against it. If the publisher could allow-list our bot, that would be great

Yes, this isn't the sort of thing we can waive, since we can't even download the app to run antivirus against it. If the publisher could allow-list our bot, that would be great

Alrighty, let's see what they say from my email that I sent earlier.

Still waiting on a reply from the email I sent.

/azp run

@wingetbot run


Add check for broken links

One of the most enjoying things with docs page is when links are broken.
To solve that lets implement a way of making sure that we never create one.
You can find a good example on how to solve it here:
https://github.com/cncf/kubernetes-community-days/blob/master/Makefile
They are using this underlying tool: https://github.com/wjdp/htmltest

Gave it a quick test.
DirectoryPath: build
IgnoreDirectoryMissingTrailingSlash: true
CheckExternal: false
IgnoreAltMissing: true

But i get the following errors:
htmltest started at 04:34:49 on build
========================================================================
docs/azure-devops-templates/index.html
  hash does not exist --- docs/azure-devops-templates/index.html --> #!
  hash does not exist --- docs/azure-devops-templates/index.html --> #!

This have something to do with how the import is done and how htmltest works.
I also saw that docusaurus have a checker to test at least broken local links. So this tool might not be as needed as on a hugo page.
Don't know how it works with external links though.
I need to read up more on how docusaurus works.

docusaurus is checking the links so we can close this one.


Net Core SDK 2.1.400 ignore _ViewStart on Areas views on publish

From @alca259 on August 18, 2018 19:6
After upgrade to VS 15.8.1 and Net Core SDK 2.1.400, the _ViewStart on Areas views are ignored, only then publish to folder.
Steps:

Create a project with one Area
Setup a dummy controller with a file _ViewStart.cshtml in the root of Views folder
Load a layout or write something in the log
Publish to local folder
Copy to a IIS Site with native code and the same SDK installed.
Access to dummy controller inside of the area

Sample log:

Users controller have specified layout on Index view
Roles controller not have specified layout on Index view, it take Layout from _ViewStart.cshtml

AttachedLog.txt
LogFirstCall.txt
Copied from original issue: aspnet/Home#3438

From @alca259 on August 20, 2018 14:23
I was did more test. The _ViewImports.cshtml, _ViewStart.cshtml and _Layout.cshtml inside of a Area are ignored on publish. Works well in visual studio in debug and release.

Can you share a repro app or the folder structure? Looking at the logs, it looks like these were all the views that MVC discovered under the areas directory:
dbug: Microsoft.AspNetCore.Mvc.Razor.Internal.RazorViewCompiler[3]
      Initializing Razor view compiler with compiled view: '/Areas/Diaries/Views/Diary/Index.cshtml'.
dbug: Microsoft.AspNetCore.Mvc.Razor.Internal.RazorViewCompiler[3]
      Initializing Razor view compiler with compiled view: '/Areas/Diaries/Views/Emotion/Index.cshtml'.
dbug: Microsoft.AspNetCore.Mvc.Razor.Internal.RazorViewCompiler[3]
      Initializing Razor view compiler with compiled view: '/Areas/Security/Views/Roles/Index.cshtml'.
dbug: Microsoft.AspNetCore.Mvc.Razor.Internal.RazorViewCompiler[3]
      Initializing Razor view compiler with compiled view: '/Areas/Security/Views/Users/Index.cshtml'.

Project structure

I create a new blank project and works well, but i don't know why, because i copy the files from my original project.

Does cleaning + rebuilding your original project work? If that doesn't work, could you run dotnet build /bl and attach the log file (msbuild.binlog)? That said, if the issue is resolved in a blank project, do you think it's still worthwhile investigating this further?

Ok, so sorry. It's not a bug. I don't know why my csproj is corrupted and remove views from compilation.


lag in powetoys run

there is a lot of issue when i use powertoy run i faced a lot of lag i recently used wox its pretty good easy and fast but it lags day by day
ℹ Computer information

PowerToys version 0.31.2:
PowerToy Utility admnistator:
Running PowerToys as Admin yes:
Windows build number: [run "winver"]: 19043.433

📝 Provide detailed reproduction steps (if any)

…
…
…

✔ Expected result
What is the expected result of the above steps?
❌ Actual result
What is the actual result of the above steps?
📷 Screenshots
Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

Does 0.35 have the same issue?  Can you share your logs via "Report Bug" in the systray as well as maybe try out the plugin manager and maybe disable a plugin one by one to see if the experience improves so we can be systematic here?
Right now this is hard to reproduce as we don't really have much data to go on


[Docs] Update section about mailing list and bug tracker

Summary
Reading https://setuptools.pypa.io/en/latest/setuptools.html there's a section at the bottom:

Mailing List and Bug Tracker
Please use the distutils-sig mailing list for questions and discussion about setuptools, and the setuptools bug tracker ONLY for issues you have confirmed via the list are actual bugs, and which you have reduced to a minimal set of steps to reproduce.

Clicking around shows the mailing list is now defunct. Happy to adjust the documentation, but I have no idea what the process is now? Straight to issues, search, then file if not found?
OS / Environment
No response
Additional Information
N/A
Code of Conduct

[X] I agree to follow the PSF Code of Conduct

Thank you very much for spotting that @ashemedai!
I think the discussions tab on GitHub are a good place to start, since it is specific to setuptools.
There are other channels, but this seems to be the more focused one in my opinion.

I can create a PR for the discussions pointer at least. Can integrate other suggestions as needed.


Allow Bray-Curtis to accept Relative Frequency Data

Improvement Description
Allow FeatureTable[RelativeFrequency] to be passed to bray_curtis (1, 2)
Current Behavior
Only FeatureTable[Frequency] is allowed.
Comments
IIRC, I ran into some unexpected test failures when initially trying to implement this. Tests showing that Bray-Curtis produces expected results with relative frequency data will be required in any PR that closes this issue.

addressing in #60


cargo run --features no_python --bin metta-repl before and after metta-repl

I do not know how much of a bug this is, but the user experience is suboptimal.
I just built the repo with cargo build.

If I launch metta-repl directly from target/debug, I get:

Fatal Error: ModuleNotFoundError: No module named 'hyperon'

If I then launch cargo run --features no_python --bin metta-repl, I get the REPL.

Then, if I launch metta-repl again, directly from target/debug, it works too.

The initialisation of the hyperon module from rust seems... weird.

Python module is used from REPL by default mostly because main users of MeTTa are using Python to integrate with neural net libraries. Thus if REPL is launched without "no_python" feature and Python part of the repo is not built and installed properly then REPL fails.

Then, if I launch metta-repl again, directly from target/debug, it works too.

After launching REPL with "no_python" property built binary is kept in target directory and second launch doesn't try loading Python part.
I agree that for pure Rust users it is surprising behavior and better way would be to replace "no_python" feature by "python" feature which enables using Python module. Also we have https://github.com/trueagi-io/hyperon-experimental/issues/432 which prevents REPL from starting in complex Python setup.

Well, I must say the build instructions to build from source are rather painful if you do not want to put a docker container in the middle. Such issues are, in my opinion, a byproduct of trying to build from source with the current instructions.

That said, I wouldn't be against changing the default to no_python either.

I don't have objections to python being bound to metta. My concern is merely buildability. Each time I come back to MeTTa, some weird uncanny aspect of the build instructions blow up. And, here, the presence of an unactivated python 3.6 in pyenv got me in these problems with python not bound to MeTTa.

@vsbogd This is very much unclear. Build from source out of docker and with pyenv, I experience the following pain points:

When I launch python in my pyenv shell 3.11.8, I'm indeed able to import the python module I've built from source. import hyperon followed by hyperon.__version__ works.

cargo build --features python.git still creates a metta-repl that says Fatal Error: ModuleNotFoundError: No module named 'hyperon'.

How do I get the python module to be picked up by metta-repl ? Because the built module is clearly accessible from the python REPL (managed by pyenv) but not from the metta-repl cli. How is that set up ?

The point of PR #751 is to make REPL start without integrating Python by default. I.e. one can clone repo and after that execute:
cargo run to run MeTTa REPL.
If you need Python inside REPL you need build and install MeTTa Python library under your pyenv environment first. Usually it the following list of commands should be enough:
mkdir build
cd build
cmake ..
make
cd ..
python3 -m pip install -e ./python[dev]
cargo build --features python

To debug your issue further could you please:

do the steps above under pyenv you mentioned starting from clean repo, use git clean -xfd to clean up it
if it doesn't work then post the result of the following commands:

which python
python --version
which python3
python3 --version
ldd target/debug/metta-repl

Here goes:
mini-me@virtucon ~/h/b/hephaestus> pyenv shell 3.11.8
mini-me@virtucon ~/h/b/hephaestus> pyenv version
3.11.8 (set by PYENV_VERSION environment variable)
mini-me@virtucon ~/h/b/hephaestus> git clone https://github.com/trueagi-io/hyperon-experimental.git hyperon-experimental-main
mini-me@virtucon ~/h/b/hephaestus> cd hyperon-experimental-main
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> mkdir build
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> cd build
mini-me@virtucon ~/h/b/h/h/build (main)> cmake ..
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- HYPERONC_INSTALL_PREFIX = /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/build/hyperonc-install
-- HYPERONC_BINARY_DIR = /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/build/hyperonc-prefix/src/hyperonc-build
-- HYPERONPY_BINARY_DIR = /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/build/hyperonpy-prefix/src/hyperonpy-build
-- Configuring done (1.2s)
-- Generating done (0.0s)
-- Build files have been written to: /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/build
mini-me@virtucon ~/h/b/h/h/build (main)> make
[  6%] Creating directories for 'hyperonc'
[ 12%] No download step for 'hyperonc'
[ 18%] No update step for 'hyperonc'
[ 25%] No patch step for 'hyperonc'
[ 31%] Performing configure step for 'hyperonc'
-- The C compiler identification is GNU 13.2.0
-- The CXX compiler identification is GNU 13.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
WARN: *** Conan 1 is legacy and on a deprecation path ***
[...]
-- Found optional-lite: 3.5.0 (found version "3.5.0")
-- Configuring done (7.2s)
-- Generating done (0.0s)
-- Build files have been written to: /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/build/hyperonpy-prefix/src/hyperonpy-build
[ 87%] Performing build step for 'hyperonpy'
[ 50%] Building CXX object CMakeFiles/hyperonpy.dir/hyperonpy.cpp.o
[100%] Linking CXX shared module /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/python/hyperonpy.cpython-311-x86_64-linux-gnu.so
[100%] Built target hyperonpy
[ 93%] Performing install step for 'hyperonpy'
Skipping install step.
[100%] Completed 'hyperonpy'
[100%] Built target hyperonpy
mini-me@virtucon ~/h/b/h/h/build (main)> cd ..
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> python -c "import sys; print(sys.executable)"
/home/mini-me/.pyenv/versions/3.11.8/bin/python
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> python3 -m pip install -e ./python[dev]
[...]
Successfully installed build-0.10.0 hyperon-0.2.0+g8c1b66d4 iniconfig-2.0.0 pluggy-1.5.0 pytest-7.3.2
WARNING: There was an error checking the latest version of pip.
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> python3
Python 3.11.8 (main, Feb 16 2024, 14:33:34) [GCC 12.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import hyperon
>>> hyperon.__version__
'0.2.0+g8c1b66d4'
>>>
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> cargo build --features python
[...]
   Compiling clap v4.5.10
   Compiling pep440_rs v0.3.12
   Compiling pyo3-macros v0.19.2
   Compiling metta-repl v0.2.0 (/home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/repl)
   Compiling hyperon v0.2.0 (/home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/lib)
   Compiling hyperonc v0.2.0 (/home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/c)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 24.08s
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> target/debug/metta-repl
Fatal Error: ModuleNotFoundError: No module named 'hyperon'
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> target/debug/metta-repl
Fatal Error: ModuleNotFoundError: No module named 'hyperon'
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main) [255]> which python
/home/mini-me/.pyenv/shims/python
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> python --version
Python 3.11.8
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> which python3
/home/mini-me/.pyenv/shims/python3
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> python3 --version
Python 3.11.8
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> python3 -m pip list | grep hyperon
hyperon                      0.2.0+g8c1b66d4     /home/mini-me/home/backyard/hephaestus/hyperon-experimental-main/python
WARNING: There was an error checking the latest version of pip.
mini-me@virtucon ~/h/b/h/hyperon-experimental-main (main)> ldd target/debug/metta-repl
        linux-vdso.so.1 (0x00007ffceb72b000)
        libpython3.11.so.1.0 => /lib/x86_64-linux-gnu/libpython3.11.so.1.0 (0x0000753633000000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x000075363393d000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000753632c00000)
        /lib64/ld-linux-x86-64.so.2 (0x0000753634142000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x0000753633852000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x0000753633833000)
        libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x0000753633806000)

I believe the libpython linkage information should instead point to ~/.pyenv/versions/3.11.8/lib/libpython3.11.so.

Right. The issue is REPL executable contains only library file name libpython3.11.so.1.0 not the absolute path. On the other hand PyEnv library is not located on the default system library loading path. Thus when REPL executable is loaded it is linked to the some library which is located on the system loading path. It is a duplicate of the https://github.com/trueagi-io/hyperon-experimental/issues/432 but here the system has same library version in a system path.
I would suggest closing this and continue discussion in https://github.com/trueagi-io/hyperon-experimental/issues/432.

EDIT: Using patchelf --replace-needed libpython3.11.so.1.0 /home/mini-me/.pyenv/versions/3.11.8/lib/libpython3.11.so target/debug/metta-repl did the trick. Though it's mighty ugly. And undocumented in the readme.

Yes, I think we need fixing #432 rather then mention this in README.md.

EDIT: Using patchelf --replace-needed libpython3.11.so.1.0 /home/mini-me/.pyenv/versions/3.11.8/lib/libpython3.11.so target/debug/metta-repl did the trick. Though it's mighty ugly. And undocumented in the readme.

Yes, I think we need fixing #432 rather then mention this in README.md.

I believe you could do both. I really lost months on that, with multitasking and all...


style(patterns): establish a naming convention for patterns

Right now with 1.0.0 beta branch we are using dc--whatever for patterns. (common modifiers that can be applied to every elements).
IHMO we could use also not BEM naming using for example dc-text-center but then it's not so obvious to distinguish between patterns and blocks (one of the good thing of BEM naming conventions is that watching the class names you are able to understand what is what).
So... IHMO we should use dc--.
Examples:
dc-text-center
dc-text-left
dc-truncate
dc-islands-75

to
dc--text-center
dc--text-left
dc--truncate
dc--islands-75

@gabrielhl @cjhowald @xonic @dami-gg WDYT?

I agree with using the double dash but what about if we also add the "is" keyword as we do for hidden, shown, etc...? i.e. dc--is-text-right


[BUG] If multiple mods add elements to the navbar, the KES icon gets pushed to the right with no padding

The navbar background does not span the apparent width of the page, causing the last element to abut the edge of the border:

This is not always the case, but is caused at certain combinations of zoom level, too many elements added to the navbar, and when the KES update icon is present. It is caused by the setting max-width: 1360px being applied to the .kbin-container selector, which applies to both the navbar container and the body container and is used to restrain the size to a centered, mobile-like view. It should be fixable by applying a custom rule localized to #header > .kbin-container specifically to set the max width, although this may have adverse effects in the mobile view.

Resolved by 8a6020a


The inclusion of mitigations=auto,nosmt as a kernel argument has started to cause peculiar behaviour on my system

Image: bluefin-dx-main-laptop-userns-hardened
CPU: AMD Ryzen™ 5 3500U with Radeon™ Vega Mobile Gfx × 8
Since about a week (at least since the 18th of February) I've noticed the following changes to how my system boots up:

After the password for LUKS has been filled in, it takes about 5-15 minutes of time before GDM shows itself. Before, this used to take about a minute maximum.
Right before GDM shows up, for about a second, Plymouth reveals itself and shows a bunch of text (mostly green) and goes away.
Furthermore, my system normally defaults to Wayland. However, together with the aforementioned issues, an X11 session is started instead and I have to log out in order to return to my Wayland session. Peculiarly, it seems as if the Wayland session is still the default; however it seems as if it simply resorts to X11 because the Wayland session couldn't be established the first time around.

I've waited a couple of days in hopes that it would be resolved eventually, but as a solution didn't come I tried to troubleshoot it myself. What I did:

rpm-ostree reset and reset the kernel arguments to their default values with rpm-ostree kargs --editor. With this, all the problems were resolved.
I added my layers with the rpm-ostree install ... command. The following packages were installed that way: bat corectrl gnome-shell-extension-caffeine gnome-shell-extension-dash-to-panel gnome-shell-extension-just-perfection gnome-shell-extension-pop-shell gnome-shell-extension-vertical-workspaces lsd stow tealdeer and zoxide. I rebooted and everything still functioned as it should.
Then I only added the kernel arguments that come with ujust set-kargs-hardening and right away the issue had shown itself again. After some back and forth, I eventually found the culprit; namely mitigations=auto,nosmt.
Finally, I reapplied all the kernel arguments that I had previously, but which I had removed initially for troubleshooting purposes. And even with all of them back, the system continued to work as it should.

So at this point, I'm positive that mitigations=auto,nosmt is at least part of the problem. Ideally, the troubleshooting efforts should be redone, but this time I should add the kernel arguments right after the rpm-ostree reset, so before any layers are added, in hopes of (potentially) finding a package that simply doesn't play nice with mitigations=auto,nosmt. Furthermore, I should check if mitigations=auto,nosmt still continues to work on my laptop with any of the upstream projects as the fault is likely to be found there. Perhaps I might return back to this, but I have some deadlines that have be met in the upcoming days. So, only after those have been dealt with.
For whatever it's worth, I didn't layer any new packages between the last known (pre-bad) good state (at the 15th of February) and the first known bad state (at the 18th of February).

So just to confirm, if you reapply mitigations=auto,nosmt, all of the behavior you listed comes back? And without it, it all goes away?

also, please confirm that this still happens on a silverblue or kinoite image. If it doesn't, this should be reported to bluefin instead.

So just to confirm, if you reapply mitigations=auto,nosmt, all of the behavior you listed comes back? And without it, it all goes away?

Exactly.

also, please confirm that this still happens on a silverblue or kinoite image. If it doesn't, this should be reported to bluefin instead.

Great catch! Will do.

I have a Thinkpad T495 with the same hardware. I can try to reproduce this but from external SSD as I will sell it.
I had strange things with kinoite too, and I think this may be related (something strange happening with sddm and gdm?)
On my side SDDM

doesnt show the user pictures anymore (I already switched themes, stayed the same)
has a different layout, not the "scroll through users horizontally" but username prefilled with a dropdown menu, password empty.
my BIOS output (boot logo or last messages) is shown right after I log in and SDDM disappears

Those happened a while ago and dont cause big issues like that, but I will test and remove that karg.
Also afaik, mitigations=auto,nosmt are two configs, you might test both seperately to get a closer scope (mitigations=auto, mitigations=nosmt)

Also afaik, mitigations=auto,nosmt are two configs, you might test both seperately to get a closer scope (mitigations=auto, mitigations=nosmt)

That is not correct. The only valid values for mitigations are off, auto, and auto,nosmt.
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html?highlight=auto,nosmt

Also, please do not clutter existing issues with unrelated bugs.

So..., I did some testing and the results can be found below.
In all cases (unless stated otherwise), the images didn't have any layered packages nor did they have any (additional) kernel arguments except for mitigations=auto,nosmt (it's literally just (so without comments) rd.luks.uuid=luks-... rhgb quiet root=UUID=... rootflags=subvol=root rw mitigations=auto,nosmt). Furthermore, if 'issues' are present, then all the issues found in the original 'post' are implied. Perhaps important to note, I also observed that the fans of the laptop make substantial more noise in the phase between filling in the LUKS-password and the appearance of GDM whenever the issues are present.
Up to the tests (in order of operation):

ostree-image-signed:docker://ghcr.io/secureblue/bluefin-dx-main-laptop-userns-hardened:latest : issues are present
ostree-image-signed:docker://ghcr.io/ublue-os/silverblue-main:39 : issues are absent
ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:39 : during first reboot; after LUKS-password was filled in, it "updated kargs" (which in reality meant that rd.luks.options=discard was added, a kernel argument that I usually have as well and which I didn't remove for subsequent tests). After it had "updated kargs", it did another reboot and issues are absent.
ostree-image-signed:docker://ghcr.io/secureblue/silverblue-main-laptop-userns-hardened:latest : issues are absent
ostree-image-signed:docker://ghcr.io/secureblue/bluefin-dx-main-laptop-userns-hardened:latest : (did a 360 and returned back to where I had initially started) issues are present

I think the results speak for themselves.

@throwaway43 The results are actually somewhat confusing. The issues are absent on other secureblue images like silverblue, and absent on the regular bluefin-dx image, but present on the secureblue bluefin image. This means that some package bluefin includes conflicts with some changes secureblue makes. This could be any number of things as Bluefin makes tons of changes compared to silverblue.

My apologies! Perhaps I should have put more thought on the chosen words. But, with "the results speak for themselves", I meant the implication that's also found in your most recent comment. So, while it didn't provide any directives to pinpoint the problem, it at least narrowed down the possibilities.
FWIW, I did some more testing (for completeness' sake): the issues persist on both ostree-image-signed:docker://ghcr.io/secureblue/bluefin-dx-main-userns-hardened:latest and ostree-image-signed:docker://ghcr.io/secureblue/bluefin-main-laptop-hardened:latest. Furthermore, as uBlue allows tagging days, it made sense to utilize that functionality in order to do a better job at pinpointing the location of the breaking point and this allowed the discovery of the following insight:

ostree-image-signed:docker://ghcr.io/secureblue/bluefin-dx-main-laptop-userns-hardened:20240216 : issues are absent
ostree-image-signed:docker://ghcr.io/secureblue/bluefin-dx-main-laptop-userns-hardened:20240217 : issues are present

Between these two upgrades, the following packages got an upgrade:
git-core 2.43.0-1.fc39 -> 2.43.2-1.fc39
git-core-doc 2.43.0-1.fc39 -> 2.43.2-1.fc39
python3-rpm 4.19.1-2.fc39 -> <IP_ADDRESS>-1.fc39
rpm 4.19.1-2.fc39 -> <IP_ADDRESS>-1.fc39
rpm-build-libs 4.19.1-2.fc39 -> <IP_ADDRESS>-1.fc39
rpm-libs 4.19.1-2.fc39 -> <IP_ADDRESS>-1.fc39
rpm-plugin-selinux 4.19.1-2.fc39 -> <IP_ADDRESS>-1.fc39
rpm-sign-libs 4.19.1-2.fc39 -> <IP_ADDRESS>-1.fc39

cockpit-machines 306-1.fc39 -> 307-1.fc39
kcli 99.0.0.git.202402152143.320dce8-0.fc39 -> 99.0.0.git.202402161852.c7fa6c6-0.fc39
raft 0.18.3-0.2.fc39 -> 0.22.0-0.1.fc39
tcpdump 14:4.99.4-2.fc39 -> 14:4.99.4-3.fc39
vim-common 2:9.1.031-1.fc39 -> 2:9.1.076-2.fc39
vim-data 2:9.1.031-1.fc39 -> 2:9.1.076-2.fc39
vim-enhanced 2:9.1.031-1.fc39 -> 2:9.1.076-2.fc39
vim-minimal 2:9.1.031-1.fc39 -> 2:9.1.076-2.fc39
I was able to downgrade the packages found above the horizontal line through rpm-ostree override replace ... (git and rpm respectively), but alas... it didn't matter. I tried the same for the latter half, but they didn't seem to be affected by it or (instead) the command gave an error; which occurred for vim.
Honestly, I'm a bit lost at this point. What would be the best course of action on my side of things?

I was able to downgrade the packages found above the horizontal line through rpm-ostree override replace ... (git and rpm respectively)

The "..." aren't replaced by git and rpm, but by their respective builds found on Koji. Wanted to make that clear*.

@throwaway43 It might not be a package upgrade. It could be a config change.
You should look through the bluefin change history and apply the changes relative to silverblue to try to identify the root cause. I'm not sure what else to recommend.

I have a Thinkpad T495 with the same hardware. I can try to reproduce this but from external SSD as I will sell it.

@trytomakeyouprivate Thank you for your considerations! I believe this is a vital step to determine if it's even reproducible on other devices. Because if that's not the case, then I don't see any reason why this issue should remain open.
@qoijjj Thank you for pointing that out! Yesterday, before posting my most recent comment, I did look into the change histories for both projects. And if memory serves me right, there were little to no changes reported for Secureblue and those that were didn't strike me as particularly interesting as so far as being the cause for the issues. For Bluefin(-dx), there were more substantial changes, but I wasn't able to find anything useful beyond that. It's worth noting that I'm just a pleb and thus my evaluations don't hold much value, if at all :sweat_smile:.
Unfortunately, I don't have an additional device to test if this issue is even reproducible on other devices. On that note, for whatever it's worth, if no one can demonstrate that the issue is reproducible on other devices, then I don't see any reason for this issue to remain open.
Finally, I've actually personally given up on further troubleshooting efforts for now; I will simply not rely on the use of mitigations=auto,nosmt on my laptop.

@throwaway43 you mentioned that the issue is present on 20240217
Did you check both auto,nosmt and auto for that build?

Did you check both auto,nosmt and auto for that build?

I actually hadn't checked auto for that build. Thanks for pointing that out! So I've just checked that now and mitigations=auto doesn't cause any issues.

Btw, am I correct to assume that the inclusion of mitigations=auto is strictly better than its absence? And thus, even if the issues with mitigations=auto,nosmt persists, this should not deter me from relying on mitigations=auto?

am I correct to assume that the inclusion of mitigations=auto is strictly better than its absence

No, it's the kernel default

Based on the previous comments, this is only reproducible on bluefin. This means that bluefin makes changes that are incompatible with auto,nosmt. Please open a ticket capturing this on the bluefin issues tracker: https://github.com/ublue-os/bluefin/issues


SR suddenly stopped working

The problem
The action suddenly stopped working. The action fails with the two errors below when retrying.
I've retried many times on different days expecting it solves as it broke, by itself.
Expected behavior
Pass or give a more explicative error. I have no clue what's happening,
Additional context
Run<EMAIL_ADDRESS>/usr/bin/docker run --name a5c76b2469776b98a9417d99bc9a3d6b496de2_a5ad47 --label a5c76b --workdir /github/workspace --rm -e "INPUT_GITHUB_TOKEN" -e "INPUT_REPOSITORY_USERNAME" -e "INPUT_REPOSITORY_PASSWORD" -e "INPUT_ADDITIONAL_OPTIONS" -e "INPUT_DIRECTORY" -e "INPUT_PYPI_TOKEN" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/data-store-client/data-store-client":"/github/workspace" a5c76b:2469776b98a9417d99bc9a3d6b496de2
debug: get_current_version_by_tag()
debug: get_last_version(, pattern='(\d+\.\d+\.\d+(-beta\.\d+)?)')
error: [Errno 32] Broken pipe

Run<EMAIL_ADDRESS>
/usr/bin/docker run --name c044287741a03b5aa4551a58f837e4452e9fd_53f388 --label 6c0442 --workdir /github/workspace --rm -e "INPUT_GITHUB_TOKEN" -e "INPUT_REPOSITORY_USERNAME" -e "INPUT_REPOSITORY_PASSWORD" -e "INPUT_ADDITIONAL_OPTIONS" -e "INPUT_DIRECTORY" -e "INPUT_PYPI_TOKEN" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/data-store-client/data-store-client":"/github/workspace" 6c0442:87741a03b5aa4551a58f837e4452e9fd
debug: get_current_version_by_tag()
debug: get_last_version(, pattern='(\d+\.\d+\.\d+(-beta\.\d+)?)')
error: SHA could not be resolved, git returned: b''

Hey @Vichoko - this looks like the same issue as https://github.com/python-semantic-release/python-semantic-release/issues/560, could you bump to v7.33.2 and try again please

That fixed it. Thanks!


Type macros may follow a different naming convention

https://github.com/rust-lang-nursery/api-guidelines/issues/135#issuecomment-343698387 suggests a nice one:

I've been using PascalCase! for macros that expand into types. (e.g. Array![i32; 5; 4; 3] which expands into [[[i32; 3]; 4]; 5])

I did not consider type macros when adding a case convention for macros in C-CASE. I have also never used a type macro myself. Will need to survey the ecosystem and see whether PascalCase! for type macros would be a good recommendation.

This seems like an amendment we'd want to make now. In the intervening years I think PascalCase has emerged as a standard for type macros (like syn::Token!).

@rfcbot fcp merge

@rfcbot fcp merge
This proposes amending our naming conventions to recommend type macros use PascalCase naming instead of snake_case.

Are there any type macros in the standard library already?

Yes, there's vec! and format_args!, both using snake case instead of pascal case.

Both of those macros expand into values, not types.


[gui] Show list of ahk2exe directives

The gui should have a second "expert" tab to show the ahk2exe directives found in script file.
As additional improvement it would be great ifvthe user can edit the directives and save them in the script.
The directives could be shown as list or table.
EXAMPLE

Directive
Properties

name1
values

name2
values

Thank you for your suggestion. We are not planning on implementing this enhancement at present but will keep it in mind for the future.

This task is more suited to a dedicated editor. There are no plans to implement this request.


functional components

###Highlights

[ ] Converted class components into functional Components.
[ ] Added prop types to make them pure functions.
[ ] No eslint errors.
[ ] No Stylelint errors.
[ ] Followed Gitflow.
[ ] Used best Practices.

Thank you much for approving my request.
On Fri, Jan 13, 2023 at 7:27 PM Yassine Omari @.***>
wrote:

@.**** approved this pull request.
Project Approved 🏆 🎉 🟢
Hi @tanveerisonline https://github.com/tanveerisonline
Your project is complete! You have done it exceptionally well. it's time
to merge it 💯
Congratulations! 🎉
To Highlight 👍
✔ No linters error.
✔ Details PR title and description.
✔ Good commit messages.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something
is not 100% clear.
Please, remember to tag me in your question so I can receive the
notification. You can also connect with me on slack
https://microverse-students.slack.com/team/U02FTTCCU2V
_As described in the Code reviews limits policy
https://microverse.zendesk.com/hc/en-us/articles/1500004088561 you have
a limited number of reviews per project (check the exact number in your
Dashboard). If you think that the code review was not fair, you can request
a second opinion using this form https://airtable.com/shrQAqnBwek5a0O0s.
—
Reply to this email directly, view it on GitHub
https://github.com/tanveerisonline/Math_Magicians/pull/4#pullrequestreview-1247679271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR65XUFIIMNYH2M5L5P4CTLWSFNK3ANCNFSM6AAAAAAT2N4AME
.
You are receiving this because you were mentioned.Message ID:
@.***>


Question using Nextra 3/4 for Dynamic Routes and ISR

Hello!  I'm trying to use Nextra for hosting multiple docs sites that are generated in a dynamic route for multiple subdomains, then use ISR for each of them:
Question: is it possible to host multiple dynamically generated Nextra sites in the same application route? let say we have a primary application that that will route subdomains apple and orange (or others outside of "www".site.com) to a dynamic catch all route [[...subdomain_docs]].
Is this a reasonable (or possible) strategy to present static docs that also use ISR?
Would we be able to use and apply dynamic theme as well? Many thanks, I'm new to Nextra :)

You're the goat thank you, also: should I only be installing one of nextra-theme-docs and/or nextra?
I imagine I'm supposed to install at: 4.0.0-app-router.34
But with both nextra and nextra-theme-docs using this package I keep running into this issue:
`Failed to compile
Next.js (14.2.6) is outdated (learn more) (turbo)
./node_modules/.pnpm/nextra@4.0.0-app-router.34_acorn@8.12.1_next@14.2.6_@opentelemetry+api@1.9.0_@playwright+test_khefrv2awh4q6u44w5mrhmsi54/node_modules/nextra/dist/client/components/search.js:13:27
Module not found
11 | import { InformationCircleIcon, SpinnerIcon } from "../icons/index.js";
12 | async function importPagefind() {

13 |   window.pagefind = await import(
|                           ^^^^^^^
14 |     /* webpackIgnore: true */
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
15 |     addBasePath("/_pagefind/pagefind.js")
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
16 |   );
| ^^^^
17 |   await window.pagefind.options({
18 |     baseUrl: "/"
19 |     // ... more search options

https://nextjs.org/docs/messages/module-not-found`

use next.js 15 or remove --turbo flag from next.js 14


Serverless / Automatic Annotation Installation Error (BUG)

My actions before raising this issue
hey, guys I just wondering about this error, is there a step that I'm missing while deploying the model using nuctl.

Expected Behaviour
20.07.17 12:05:23.377                     nuctl (I) Deploying function {"name": ""}
20.07.17 12:05:23.378                     nuctl (I) Building {"versionInfo": "Label: 1.4.8, Git commit: 238d4539ac7783896d6c414535d0462b5f4cbcf1, OS: darwin, Arch: amd64, Go version: go1.14.3", "name": ""}
20.07.17 12:05:23.590                     nuctl (I) Cleaning up before deployment
20.07.17 12:05:23.694                     nuctl (I) Function already exists, deleting
20.07.17 12:05:24.271                     nuctl (I) Staging files and preparing base images
20.07.17 12:05:24.274                     nuctl (I) Building processor image {"imageName": "cvat/openvino.omz.public.yolo-v3-tf:latest"}
20.07.17 12:05:24.274     nuctl.platform.docker (I) Pulling image {"imageName": "quay.io/nuclio/handler-builder-python-onbuild:1.4.8-amd64"}
20.07.17 12:05:27.432     nuctl.platform.docker (I) Pulling image {"imageName": "quay.io/nuclio/uhttpc:0.0.1-amd64"}
20.07.17 12:05:31.462            nuctl.platform (I) Building docker image {"image": "cvat/openvino.omz.public.yolo-v3-tf:latest"}
20.07.17 12:05:32.798            nuctl.platform (I) Pushing docker image into registry {"image": "cvat/openvino.omz.public.yolo-v3-tf:latest", "registry": ""}
20.07.17 12:05:32.798            nuctl.platform (I) Docker image was successfully built and pushed into docker registry {"image": "cvat/openvino.omz.public.yolo-v3-tf:latest"}
20.07.17 12:05:32.798                     nuctl (I) Build complete
20.07.17 12:05:35.452                     nuctl (I) Function deploy complete {"httpPort": 57308}
Current Behaviour

Steps to Reproduce (for bugs)
1.nuctl create project cvat
2.nuctl deploy --project-name cvat
--path serverless/openvino/dextr/nuclio
--volume pwd/serverless/common:/opt/nuclio/common
--platform local
3.step no 2 working fine
4.nuctl deploy --project-name cvat
--path serverless/openvino/omz/public/yolo-v3-tf/nuclio
--volume pwd/serverless/openvino/common:/opt/nuclio/common
--platform local
5. i got problem with step no 4
Context

Development working fine without models deploy , but I cant try the auto annotation which I think this is very usefull
Your Environment

Python 3.8
Nuclio 1.5.16
Docker 20.10.12
Ubuntu 20

@bsekachev

Same issue

Is there any update on this bug. I am facing the same issue with WSL2 on windows 11.
Openvino is giving an error while converting yolo to IR representation.


Make explicit close to streams.

Less aggressive Garbage Collectors may need this to free up open files

@mreyescdl , I think we should make a plan to get your changes into the core library.  It would be a good practice to close resources.
My recommendation would be to use a try(...) with resources block instead of adding the close in a finally block.
https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html

@mreyescdl , I think we should make a plan to get your changes into the core library.  It would be a good practice to close resources.
My recommendation would be to use a try(...) with resources block instead of adding the close in a finally block.
https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html

stream2File closes stream.
Pull request not needed.

stream2File closes stream.
Pull request not needed.


Fix crc32c CMake configuration directory.

The port was installing the CMake configuration files for Crc32c in
share/crc32c/Crc32c/Crc32cConfig.cmake, where find_package() cannot
find them.  They should be installed in share/crc32c/Crc32cConfig.cmake.

Thanks for the PR! I lowercased the share directory, based on our conventions (CMake will correctly find things in share/xyz/Xyz.cmake)

SGTM.  Just for my education, is there a good place to read about these conventions so I can follow them in other ports?
And is there something additional that could be done in the testing infrastructure to make sure these problems are caught earlier?


Enrollment Certificate stored on smart card not supported?

I believe that the best practice is to store the Enrollment Certificate on a smart card for security. It seems EnrollmentStation does not support this?
I have requested an Enrollment Certificate with the PIV Manager tool and saved it to some slot, say 9c or 9d. But when choosing the Agent certificate, "browse" button only displays the certificate on the local computer and not certificates from YubiKey.

Don't know what happened, now ES finds the certs on the Yubikey. Closing thus issue.

Oops - the certs are not found from Yubikey, instead it was just Windows updating the local computer certificate store.
The issue that Yubikey cannot open Agent certificate from Yubikey persists.

It is true that it would provide better security to have the enrollment agent certificate on a yubikey. Our main use case for this application was an offline scenario where the enrollment machine is turned off (and it has Bitlocker disk encryption) which provide better protection for the key than storing it on a yubikey.
If I remember correctly, the last time we researched this (about 2 years ago) there was no Cryptographic Service Provider (CSP) for reading the private key on the smart card. The solution back then was to install a third party provider that had limited support for yubikeys.
We will look into it and reevaluate support for this feature.

Thanks for the reply. Sounds possible that there is no CSP for reading a private key since usually private keys must not be exported from a smart card. I do not know enough of how it works to say why you would need to read the private key off it and not do some signing operation on it. I guess this issue can be closed then, no need to explain more in detail about the private key.

It is not reading the private key to export it. That would be very insecure as you rightly point out.
Yubikeys support PKCS11, which is a standard API for communicating with crytographic devices such as smart cards. However, most implementations have special adaptions to the protocol, and as such Microsoft implemented the CSP API, to which you implement a driver, and then Windows can seamless communicate with the smart card.
Windows is already using this API for signing operations when you use smart cards to log into Windows. However, it does not seem to recognize the Yubikey when doing other operations, which is why we are using the Yubikey API directly (using the libraries provided by Yubico) in ES. I have talked with the developers at Yubico on several occasions, and they want to provide support for Microsoft Windows CSPs out of the box - I'm just not sure where we stand in that regard at the moment, as this was several years ago.

As for the second issue, it would be nice if you created another ticket.

@bluikko could you try putting the agent certificate in slot 9a?
We use slot 9a for all our certs (iirc it's because of its intended use).
Also double check that, the windows certificate store detects your smartcard-agent certificate. So remove it from the users personal store first, then re-insert the yubikey and confirm that it appears again. (Windows will by default "install" any SmartCard certificate given to it, into the users personal store - in some cases it also installs any chain presented to it :|).

@bluikko another note here is that it will "never" work as it is now. You cannot have two yubikeys at the same time while working with the ES. The library we use from Yubico simply doesn't support selecting yubikeys (at least not when we made it - there are some things related to selecting Yubikeys, but we never could make it work reliably).
A better option is probably this: Use Windows 10 / Server 2016, and use Credential Guard on a machine with a TPM. Credential Guard will protect the LSASS process and virtualize it away to protect it from compromise. This goes well with another new feature: Virtual Smartcard which allows you to have a smart card on the TPM device. Using this, you can get the same security as a physical smart card would give you.


Greenfield AWS ref arch, rhel cert error

The greenfield AWS architecture playbooks fail at the TASK [etcd : Pull etcd container] step in the<EMAIL_ADDRESS>playbooks.
The symlink /etc/docker/certs.d/registry.access.redhat.com/redhat-ca.crt -> /etc/rhsm/ca/redhat-uep.pem doesn't work. I'm trying to deploy Origin on CentOS7, so I'm not surprised this symlink doesn't work.
From the aws reference architecture readme, I get the impression that I should be able to deploy Origin on CentOS7 with the tool.
I'm submitting the bug here because I have a hunch it's related to the parameters passed to the openshift-ansible playbooks (but I'm not certain).

BUG REPORT INFO
Environment

Cloud provider:  AWS

OS details (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

Linux 3.10.0-514.10.2.el7.x86_64 x86_64
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

Version of Ansible (ansible --version):

ansible <IP_ADDRESS>
  config file = /home/ec2-user/openshift-ansible-contrib/reference-architecture/aws-ansible/ansible.cfg
  configured module search path = Default w/o overrides
  python version = 2.7.5 (default, Aug  4 2017, 00:39:18) [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]

Version of Jinja (pip freeze | grep -i jinja):

You are using pip version 8.1.2, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Jinja2==2.9.6

Version of Shade (pip freeze | grep -i shade):  not installed

The openstack-ansible-contrib version (commit) (git rev-parse --short HEAD):  3857ac0

Copy of inventory files and custom variables used (please omit your secrets!):
Possible bug fixes:
[ec2-user@ip-172-31-8-46 aws-ansible]$ git diff
diff --git a/reference-architecture/aws-ansible/ansible.cfg b/reference-architecture/aws-ansible/ansible.cfg
index 0373b80..c53d1b7 100644
--- a/reference-architecture/aws-ansible/ansible.cfg
+++ b/reference-architecture/aws-ansible/ansible.cfg
@@ -10,7 +10,7 @@ remote_user = ec2-user
 gathering = smart
 retry_files_enabled = false
 nocows = true
-timeout = 30
+timeout = 600
 #lookup_plugins = ./playbooks/lookup_plugins
 #log_path = /tmp/ansible.log

diff --git a/reference-architecture/aws-ansible/playbooks/openshift-setup.yaml b/reference-architecture/aws-ansible/playbooks/openshift-setup.yaml
index 4ce075a..e59e90b 100644
--- a/reference-architecture/aws-ansible/playbooks/openshift-setup.yaml
+++ b/reference-architecture/aws-ansible/playbooks/openshift-setup.yaml
@@ -71,3 +71,5 @@
     openshift_logging_es_nodeselector: {"role":"infra"}
     openshift_logging_kibana_nodeselector: {"role":"infra"}
     openshift_logging_curator_nodeselector: {"role":"infra"}
+
+    openshift_disable_check: docker_image_availability,docker_storage

Command used to invoke ansible:
./ose-on-aws.py --keypair=mlauer-openshift2017 --public-hosted-zone=carlwebtest.com --deployment-type=origin --ami=ami-0c2aba6c --github-client-secret=<snip> --github-organization=carleton --github-client-id=<snip> --containerized=true --region=us-west-2

Configured values:
	stack_name: openshift-infra
	ami: ami-0c2aba6c
	region: us-west-2
	master_instance_type: m4.xlarge
	node_instance_type: t2.large
	app_instance_type: t2.large
	app_node_count: 3
	keypair: mlauer-openshift2017
	create_key: no
	key_path: /dev/null
	create_vpc: yes
	vpc_id: None
	private_subnet_id1: None
	private_subnet_id2: None
	private_subnet_id3: None
	public_subnet_id1: None
	public_subnet_id2: None
	public_subnet_id3: None
	byo_bastion: no
	bastion_sg: /dev/null
	console port: 443
	deployment_type: origin
	openshift_sdn: redhat/openshift-ovs-multitenant
	public_hosted_zone: carlwebtest.com
	app_dns_prefix: apps
	apps_dns: apps.carlwebtest.com
	containerized: true
	s3_bucket_name: openshift-infra-ocp-registry-carlwebtest
	s3_username: openshift-infra-s3-openshift-user
	github_client_id: *******
	github_client_secret: *******
	github_organization: carleton
	openshift_metrics_deploy: true
	openshift_metrics_storage_volume_size: 20Gi
	openshift_logging_deploy: true
	openshift_logging_storage_volume_size: 100Gi

Output of ansible run:

https://gist.github.com/laupow/00f71e604bb0039bdd506072b796089e
Anything else do we need to know:
I'm using the AWS  CentOS7 ami: CentOS Linux 7 x86_64 HVM EBS 1703_01 (ami-0c2aba6c)
This behavior is repeatable, at least for me :)

follow the setup and configuration steps in the aws reference architecture readme for a greenfield Origin deployment
checkout the release-36 branch for openshift-ansible on the control machine
run the ose-on-aws command above, and it dies.

add the following to the aws-ansible/playbooks/openshift-setup.yaml
osm_etcd_image: registry.fedoraproject.org/f26/etcd

Related -> https://github.com/openshift/openshift-ansible/issues/6018

Thanks, guys. I'll follow openshift/openshift-ansible#6018 for now and close this thread.


Feat::snake:Created views

Description
Please include a summary of the change and relevant motivation and context.
List any dependencies that are required for this change.
Created views for the project
All pull requests should be related to open issues. Indicate the issue(s) bellow and remove this line:
Fixes #(issue number 1) #(issue number 2 if applicable)
How Has This Been Tested?
Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code etc.
Screenshots (if applicable, else remove this line / section)
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added necessary inline code documentation
[ ] I have added tests that prove my fix is effective and that this feature works
[ ] New and existing unit tests pass locally with my changes

Nice work! However, it is suggested you make the following changes:
*The proper workflow is to merge your changes into backend branch locally before merging to fullstack remotely through pull request.

Project level urls.py is overpopulated with urls pattern from fullstack application alone.  As solution, create another urls.py in the application directory where your views.py resides and add all the url patterns for the fullstack application. You can then include the application level urls.py in urlpattern list in the project level urls.py as follows:

urlpattern = [
path(' ', include('fullstack.urls'))
]

Hello Mr Bello,
I hope this meets you well, I have duly noted your review and I will do so once I have juice on my pc to do so.
Kind regards.
Sent from my iPhone

On 26 May 2020, at 16:14, Shehu Bello<EMAIL_ADDRESS>wrote:
@belloshehu requested changes on this pull request.
Nice work! However, it is suggested you make the following changes:
*The proper workflow is to merge your changes into backend branch locally before merging to fullstack remotely through pull request.
Project level urls.py is overpopulated with urls pattern from fullstack application alone. As solution, create another urls.py in the application directory where your views.py resides and add all the url patterns for the fullstack application. You can then include the application level urls.py in urlpattern list in the project level urls.py as follows:
urlpattern = [
path(' ', include('fullstack.urls'))
]
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

Juice on your pc i do not understand be a little bit explicit
On Tue, May 26, 2020, 7:51 PM Emmanuel<EMAIL_ADDRESS>wrote:

Hello Mr Bello,
I hope this meets you well, I have duly noted your review and I will do so
once I have juice on my pc to do so.
Kind regards.
Sent from my iPhone

On 26 May 2020, at 16:14, Shehu Bello<EMAIL_ADDRESS>wrote:
@belloshehu requested changes on this pull request.
Nice work! However, it is suggested you make the following changes:
*The proper workflow is to merge your changes into backend branch
locally before merging to fullstack remotely through pull request.
Project level urls.py is overpopulated with urls pattern from fullstack
application alone. As solution, create another urls.py in the application
directory where your views.py resides and add all the url patterns for the
fullstack application. You can then include the application level urls.py
in urlpattern list in the project level urls.py as follows:
urlpattern = [
path(' ', include('fullstack.urls'))
]
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BuildForSDG/team-090-fullstack/pull/12#issuecomment-634112158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTR2QMQMNNLKBIKZGZN4DTRTPQO5ANCNFSM4NJCIXXA
.

My laptop is out of battery, I don’t have power to recharge my battery, I’d be able to turn on my generator much later in the day.
Sent from my iPhone

On 26 May 2020, at 16:54, ifelajulo<EMAIL_ADDRESS>wrote:
Juice on your pc i do not understand be a little bit explicit
On Tue, May 26, 2020, 7:51 PM Emmanuel<EMAIL_ADDRESS>wrote:

Hello Mr Bello,
I hope this meets you well, I have duly noted your review and I will do so
once I have juice on my pc to do so.
Kind regards.
Sent from my iPhone

On 26 May 2020, at 16:14, Shehu Bello<EMAIL_ADDRESS>wrote:
@belloshehu requested changes on this pull request.
Nice work! However, it is suggested you make the following changes:
*The proper workflow is to merge your changes into backend branch
locally before merging to fullstack remotely through pull request.
Project level urls.py is overpopulated with urls pattern from fullstack
application alone. As solution, create another urls.py in the application
directory where your views.py resides and add all the url patterns for the
fullstack application. You can then include the application level urls.py
in urlpattern list in the project level urls.py as follows:
urlpattern = [
path(' ', include('fullstack.urls'))
]
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BuildForSDG/team-090-fullstack/pull/12#issuecomment-634112158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTR2QMQMNNLKBIKZGZN4DTRTPQO5ANCNFSM4NJCIXXA
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


Remove lint ignore for R0914

[User Story]
Remove lint ignore for R0914

User Story Title
Remove lint ignore for R0914

T-shirt size: S(mall), M(edium), L(arge)
S

Story Points - Fibonacci (1,2,3,5,8,13)
3

User Story
[Value Statement] "As a developer on an open source project I want, clean code that adheres to python code-styles for easier development

Description
Remove the ignore for R0914 - too-many-local from setup.cfg.  If this seems impossible discuss with team and come to decision on whether to keep ignore or not.

Acceptance Criteria/Tests
The error is removed from the ignore in setup.cfg and code is fixed so linter passes

Definition of Done
passes linter

migrated to new tmobile/sawtooth-next-directory repo


Cross-distro (non-Debian) support

I have yet to determine whether it'll actually work (the bulb I bought turned out to be a dud, no flashing on switching it on, I'll swap it tomorrow), but I see no reason why Tuya Convert would only run on Debian (-based) distros. Personally, I'll be giving it a go on Fedora, and for completeness sake I could check OpenSUSE as well, as those are the distro's I run.
Would there be community effort in documenting it, and/or an attempt at making the scripts less directly dependant on Debian?

If it can be done in a way that doesn't significantly increase the maintenance burden, I'm all for it.
That said, it is not a priority. Accounting for all the differences possible in various environments is outside project scope.
Alternatively you are free to maintain a project for targeted to a specific environment. I believe there are Proxmox and Docker forks by community members.

Also see #233 #172

I think you're right about this not being a priority - supporting more distros means more work that doesn't go towards the actual flashing. As far as.I'm concerned, this issue can be closed, unless you want to keep it open for those.interested (which, seeing the activity on this issue, isn't a lot of.people 😃).

Why not use network manager - which is pretty cross distro (and these days actually usable) rather than wifi cli primitives which are a) hardware/distro specific and b) userspace dependant

I've created this script which does everything specified in the instructions (except installing docker, and modifying the config.txt file), it should be pretty universal (I've succesfuly run this in Arch, which the instructions are not designed for).
#!/usr/bin/env bash
set -e

docker build --cache-from "tuya:latest" -t "tuya:latest" .

cleanup () {
  echo "========================="
  echo "Stopping docker container"
  docker stop "tuya"
}

trap cleanup EXIT

docker run \
  -d \
  --name="tuya" \
  --rm \
  --privileged=true \
  --network="host" \
  --volume="$(pwd)/backup:/usr/bin/tuya-convert/backups" \
  --env-file "config.txt" \
  "tuya:latest"

docker exec -it tuya start

Hope this helps

I've got a fork of this using lsb_release to check the distro type, then branching to whichever startup script is required (only tested with Fedora at the moment, as it's the only one I have available right now). I can start a pull request if there's any interest. There weren't many changes outside the install_prereq.sh script.

There is the Universal Base Image (free as an beer and free as in speech)
rhel8 Image.
Upside being if you target it as the container image base you can if you
like get support for it.
I didn't rebasee the images but did a bit of work to make things work
nicely with the CNI tools (buildah,podman,skopeo) rather than docker.
On Thu, 13 Feb 2020, 7:52 am zarecor60<EMAIL_ADDRESS>wrote:

I've got a fork of this using lsb_release to check the distro type, then
branching to whichever startup script is required (only tested with Fedora
at the moment, as it's the only one I have available right now). I can
start a pull request if there's any interest. There weren't many changes
outside the install_prereq.sh script.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ct-Open-Source/tuya-convert/issues/416?email_source=notifications&email_token=AACF5LZOPXC42ADCTXL27V3RCRAOJA5CNFSM4JRBAIGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELR6MIQ#issuecomment-585360930,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACF5L2IH6XUMDINUFS63JTRCRAOJANCNFSM4JRBAIGA
.


GH-34610: [Java] Fix valueCount when loading NullVector

Rationale for this change
This is a follow up of https://github.com/apache/arrow/pull/34611 (thanks @sunchao)
We should set valueCount when loading NullVector. Unfortunately there's no nullCount field.
What changes are included in this PR?

valueCount added to NullVector
name added to NullVector's TransferPair

Are these changes tested?
Yes. unit tested.
Are there any user-facing changes?
Yes, a NullVector with a non-null name will maintain the name when transferred via TransferPair instead of defaulting to the default name $data$.

Closes: #34610

Yes, a NullVector with a non-null name will maintain the name when transferred via TransferPair instead of defaulting to the default name $data$.

Is this what's tested in the added test?

Is this what's tested in the added test?

Yes, the test is naming the null vector "v", which was failing without the changes to TransferPairImpl. The roundtrip helper test function invokes the transfer apis.

Thanks, @pitrou !


Add syntax highlighting to README [skip ci]

Also minor fixes: spelling, grammar, and capitalization

Wonderful, many thanks.


Fix spelling of dimensionRation -> dimensionRatio (#671)

Summary: Looks like there was a typo here. This may be a breaking change (requires code change for users), but should be a simple and obvious fix for any users of the library. Fixes issue #671.
Test Plan: Looks like test coverage is minimal for this code, but test gradle task within the anko-constraint-layout project was run as well as the test task within the robolectricTests project.

Thanks for the contribution


additional PR for PR 142 on guvnor repository

http://github.com/droolsjbpm/drools-wb/commit/dcda7fc5a


Add "Created At" field in story description

More info at https://userstory.eosdesignsystem.com/story/60e6df9180886200152e34b9

Can I work on this issue?

PR #113 has been created for this issue.


Correct homepage and licence SPDX identifier

Thanks for the fixes, @domcleal. Merged and released a new version of the gem.


"Save to your computer" button on the "Save as image" dialog does not work in IE11

Reported by user, confirmed on my machine.

Try this: https://github.com/eligrey/FileSaver.js/


Update all String conversions to and from byte[] to use the java-util StringUtils functions

Speedup of GroupBy with javaScript filters by ~10%
Requires https://github.com/metamx/java-util/pull/15

Requires 2.6.11 of java-util before merging

CI is expected to fail because java-util has not been updated yet.

java-util is updated. Closing and opening for CI rebuild


Allowing some rpc restrictions to be lifted up with ="0" args

Describe the change
After reading https://blog.merkle.io/blog/run-a-reth-node some people lift up default restrictions since they run their own loadbalancers to restrict public requests.
Would be great to support some "0" style args for other restriction flags like this PR
https://github.com/paradigmxyz/reth/commit/0449c5eca6e4a9d0e15cc8700e457425629838c0#diff-e488c1982272a23faac85301fe3e41d24bdd27539df3526fb1ae634476b70d05R4
Additional context
No response

which ones specifically?
I think we should also support "max" value

@mattsse Means that we should change the previous commit as well?

yeah, I'm leaning towards that actually, treating 0 as max just feels wrong.

Sure, why not? Just hoping that it wouldn't confuse users with Geth but with a proper documentation I think it is good

good point, I'm not sure where geth treats 0 as max, but most of these values are only reth specific.
since we have a few different types like u32,u64,usize, we likely want a generic solution for the wrapper type, unfortunately there's no std solution to get the max value of a type so we need to find another way, I guess a simple helper trait would do it

we have this now


Cut a new release to include the branch label to workflow metrics changes

Hello there,
Are you planning to cut a new release to include issue #164 along with other improvements? We would greatly appreciate a new release, as it would allow us to discontinue using our fork
Thanks,

hello, i will review the repo and see what needs to be update and lets plan a release for next week maybe, if i have time this week i will do