could not compile uefi

~/desktop/basic$ cargo kimage
    Updating crates.io index
    Finished dev [unoptimized + debuginfo] target(s) in 0.52s
     Running `cargo run --package simple_boot -- target/x86_64-custom/debug/basic_example --no-run`
   Compiling json v0.12.4
   Compiling locate-cargo-manifest v0.2.2
   Compiling bootloader-locator v0.0.4
   Compiling simple_boot v0.1.0 (/home/luyi/桌面/basic/simple_boot)
    Finished dev [unoptimized + debuginfo] target(s) in 1.37s
     Running `target/debug/simple_boot target/x86_64-custom/debug/basic_example --no-run`
error[E0432]: unresolved import `core::ops::FromResidual`
 --> .cargo/registry/src/github.com-1ecc6299db9ec823/uefi-0.11.0/src/result/status.rs:4:24
  |
4 |     ops::{ControlFlow, FromResidual, Try},
  |                        ^^^^^^^^^^^^ no `FromResidual` in `ops`

error[E0437]: type `Output` is not a member of trait `Try`
   --> .cargo/registry/src/github.com-1ecc6299db9ec823/uefi-0.11.0/src/result/status.rs:179:5
    |
179 |     type Output = Completion<()>;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not a member of trait `Try`

error[E0437]: type `Residual` is not a member of trait `Try`
   --> /.cargo/registry/src/github.com-1ecc6299db9ec823/uefi-0.11.0/src/result/status.rs:180:5
    |
180 |     type Residual = StatusResidual;
    |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ not a member of trait `Try`

error[E0407]: method `branch` is not a member of trait `Try`
   --> .cargo/registry/src/github.com-1ecc6299db9ec823/uefi-0.11.0/src/result/status.rs:182:5
    |
182 | /     fn branch(self) -> ControlFlow<Self::Residual, Self::Output> {
183 | |         match NonZeroUsize::new(self.0) {
184 | |             Some(r) => ControlFlow::Break(StatusResidual(r)),
185 | |             None => ControlFlow::Continue(Completion::from(self)),
186 | |         }
187 | |     }
    | |_____^ not a member of trait `Try`

error[E0407]: method `from_output` is not a member of trait `Try`
   --> .cargo/registry/src/github.com-1ecc6299db9ec823/uefi-0.11.0/src/result/status.rs:189:5
    |
189 | /     fn from_output(output: Self::Output) -> Self {
190 | |         output.status()
191 | |     }
    | |_____^ not a member of trait `Try`

error: aborting due to 5 previous errors

Some errors have detailed explanations: E0407, E0432, E0437.
For more information about an error, try `rustc --explain E0407`.
error: could not compile `uefi`

To learn more, run the command again with --verbose.
error: build failed
thread 'main' panicked at 'assertion failed: cmd.status()?.success()', src/bin/builder.rs:112:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'build failed', simple_boot/src/main.rs:63:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Try updating your nightly. The uefi crate depends on a nightly feature that recently changed.

thanks


read ground truth depth map

When I read the depth map in *_depth.7z, I found the depth values at most pixels are inf.
Used code:
`float float_inf = std::numeric_limits::infinity();
std::ifstream gt_depth_file(input_depth_path, std::ios::in | std::ios::binary);
std::vector gt_depth(num_col*num_row, 0);
int non_inf_count = 0;
if (!gt_depth_file.is_open()) {
std::cout << "cannot open the gt depth map" << input_depth_path << std::endl;
}
gt_depth_file.read((char*)&gt_depth[0], sizeof(float)num_colnum_row);
for (int i = 0; i < gt_depth.size(); i++) {
if (gt_depth[i] < float_inf)
{
non_inf_count++;
}
}
gt_depth_file.close();`
Did I miss something?

Since from most perspectives the resolution of the DSLR camera will be higher than the resolution of the laser scanner, it is to be expected that most pixels don't have a depth value on the original DSLR resolution. So I don't think there is an issue here. Do the depth images look plausible otherwise?


Create New Hampshire statewide.json

Located a statewide parcel layer. 500,000+ parcels.

578,233 features downloaded. Nice!


Add the Nutri-Score in the "Products to be completed" activity by refactoring it

[ ] Add the Nutri-Score in the "products to be completed" activity so that power users can see which new products have a Nutri-Score, and which ones don't have one
[ ] Get the occasion to standardize the activity with the other list activities that already show the Nutri-Score

I will take up this issue


Warning on Home Assistant 2023.2

Version of the custom_component
0.2.0
Logs
I get this line each time Home Assistant is started:
2023-02-08 15:22:42.707 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.powerpal_live_consumption (<class 'custom_components.powerpal.sensor.PowerpalLiveConsumptionSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total_increasing', 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

Thanks! Been a while since I've looked at the logs...
Let me fix this up this week!

I get it too.
Logger: homeassistant.components.sensor
Source: components/sensor/init.py:497
Integration: Sensor (documentation, issues)
First occurred: 10:11:58 AM (1 occurrences)
Last logged: 10:11:58 AM
Entity sensor.powerpal_live_consumption (<class 'custom_components.powerpal.sensor.PowerpalLiveConsumptionSensor'>) is using state class 'measurement' which is impossible considering device class ('energy') it is using; expected None or one of 'total_increasing', 'total'; Please update your configuration if your entity is manually configured, otherwise report it to the custom integration author.

Yep will publish an updated version shortly


Changing cell tags invalidates cache even if these don't impact execution

Describe the problem
I noticed that removing or adding remove-input tag invalidates cache, despite not influencing the execution. This causes unnecessary re-execution of the code.
This likely happens because jupyter-cache currently doesn't filter cell metadata upon computing the notebook key. The functionality for filtering is, there, but as far as I can tell it isn't used.
Link to your repository or website
No response
Steps to reproduce

Configure the repo to use jupyter-cache.
Create a myst-markdown file with any cell.
Build the docs, observe that the notebook executes
Rebuild the docs, observe that the execution is skipped.
Add :tags: [remove-input] to the cell.
Build the docs, observe that the notebook is executed.

The version of Python you're using
No response
Your operating system
No response
Versions of your packages
No response
Additional context
No response

By the way, because myst-nb does execution already on event.env-get-outdated and before the sources are even read by sphinx, it seems rather hard to implement a workaround using an extension.


Switch away from bindata for vm resources

This switch to use the schema for NetworkConfigurationPolicy,
NetworkAttachmentDefinition and VirtualMachine instead of the
previous used bindata templates.
For NetworkConfigurationPolicy and NetworkAttachmentDefinition
to use dynamic client + ssa as CreateOrUpdate can not be used
because NetworkConfigurationPolicy is non namespaced.
This just changes the current implementation to use the above.
This is reqired to make it easier to enabled support for
network isolation where a dynamic list of
NetworkAttachmentDefinition needs to be created depending on
the used OSP network list.
With this change it is now also possible to modify vm resources
by changing the CR parameters, e.g. it is now possible to change
configuration parameters, like CPU/memory/... for the controllers.
When changed the controller pod needs to be recreated.
(virtctl stop/start controller-0)

/retest

/lgtm


Use relative dates

I don’t want to waste terminal space on todays date. It is today. I know that. Give me back 10 charactes (i.e. 15%) of my terminal area.

Hi Alex, thanks for the suggestion! I agree that screen space is precious and that this is a good way to save some characters. Can't give a timeline at the moment, but this is a useful feature to have.

Hi again @alexec ,
I thought we could re-visit this topic. Could you perhaps describe more in detail what input and output you wish to see in a feature like this?

Just trim the date part of the output.

Hi! To chime in (b/c I think this is would be awesome 😄)
# (if current time is 8:42:00)

> spin -tf x.log
2023-10-06T08:41:13.886 helix_view::editor [ERROR] editor error: No definition found.
2023-10-06T08:40:50.852 helix_view::editor [ERROR] editor error: Async job failed: None

> spin --rel-date -tf x.log
47sec ago helix_view::editor [ERROR] editor error: No definition found.
2 min ago helix_view::editor [ERROR] editor error: Async job failed: None

A challenge here is how to keep them updated... in --follow we might have a buffer to play with? (not sure how it's built). Might be nice to have configurable tick, but ~5s might be good to prevent bunch of unnecessary updates? (The easy-cheesy way would be updating on each new input 😅)
# Idea: configurable tick rate?
> spin --rel-date --rel-tick 5 -tf x.log

Hi again,
An option to disable the date highlighting was added in 1.6.0. Relative dates conversion is a bit problematic to implement at the moment, as it comes with too many caveats. Will close this for now.


ESD tag processor

OpenStack Release
Mitaka
Description
Enhancement required for ESD tag processor.  This enhancement will create a mapping between a valid tag and the bigip resource type and will check if the esd tag that user created exists on bigip.

Pull request #633 did not reference this issue correctly to close it automatically.  Merge observed in master.


feat: create WebSocket Reverse Proxy

This is just a utility to help develop the client code for Shadowsocks over Websockets.

Any thoughts?

Ping


ERROR QUESTION ON RUNNING IMAGE CAPTIONING CODE (using Deep Learning (CNN and LSTM) in PyTorch)

Thanks for your error report and we appreciate it a lot.
Hi,
Please, help to find the solution to this unknown error  : UnpicklingError: unpickling stack underflow
while I run the train.py file of image captioning (https://www.analyticsvidhya.com/blog/2018/04/solving-an-image-captioning-task-using-deep-learning/ )

It is irrelevant to this repo.


strictness.lua is now strict !

Your strict module was not so strict ;-)

Nice catch! Thanks, @tst2005, and sorry it took a while, I lost track of this.


Looking for to Integrate an ICal Feed in SharePoint Online which is Link Based || SharePoint Calendar

I am looking for a way to integrate an ICal Calendar Feed in SharePoint Online Which will Keep Synchronizing with SharePoint using the ICal feed.
Originally the feed belongs from a Third Party Human Resource Software, Using this I am trying to keep the calendar synched with the updates for e.g. Holidays!
Can someone help me with how this could be achieved!
Thank you

Please, can someone help with this? Thank you

@tejasthite the React Calendar Feed web part sample will retrieve iCal feeds and present them as if they were native events in SharePoint. However, it does not sync with local SharePoint content.
If you want to sync content, I would suggest that you try using Flow instead and create a scheduled flow to regularly sync the content.
Let me know if you aren't familiar with Flow, I'd be happy to help.

Yes, I would need help with this, how can I get this accomplished? thank you

I tried the steps from the Readme.md File, I am getting the following errors || any help will be appreciated!
Thank you
C:\Users\tejast>npm install
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><=0.13 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

Then When i try the npm audit fix - I get the Below || Please can someone help
Thank you
C:\Users\tejast>npm audit fix
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated<EMAIL_ADDRESS>Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
npm WARN deprecated<EMAIL_ADDRESS>I wrote this module a very long time ago; you should use something else.

<EMAIL_ADDRESS>install C:\Users\tejast\node_modules\deasync
node ./build.js

win32-x64-node-10 exists; testing
Binary is fine; exiting

<EMAIL_ADDRESS>postinstall C:\Users\tejast\node_modules\babel-register\node_modules\core-js
node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

<EMAIL_ADDRESS>postinstall C:\Users\tejast\node_modules\babel-runtime\node_modules\core-js
node scripts/postinstall || echo "ignore"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): EPERM: operation not permitted, rmdir 'C:\Users\tejast\node_modules\fsevents\node_modules'
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><17.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

<EMAIL_ADDRESS><EMAIL_ADDRESS>added 313 packages from 120 contributors, removed 282 packages, updated 196 packages and moved 14 packages in 340.523s
fixed 9448 of 11201 vulnerabilities in 682936 scanned packages
1746 vulnerabilities required manual review and could not be updated
1 package update for 7 vulns involved breaking changes
(use npm audit fix --force to install breaking changes; or refer to npm audit for steps to fix these manually)

@hugoabernier - i was successfully able to load the Web part and attach the URL for my iCal Calendar Feed but for some reason it keeps me saying - "Oops, something went wrong! We can't display your events at the moment. Please try again later."
Any help would be appreciated? Thank you

@hugoabernier it would be great if you could help with this. Thank you!

@tejasthite do you mind sharing the iCal URL so that I can try to diagnose the issue?

@hugoabernier is there a way I could send you a Private Message with the Link? Thank you

Yes send me a direct message on my Twitter account

@hugoabernier dropped you the link on twitter, Thank you

@hugoabernier Thank you Very Much, I will give it a try and update.

@hugoabernier  - Wil I need to reclone the WebPart Sample after which the changes you have made recently? Thank you

@hugoabernier - I have been able to Pull the Events Now Thank you Very Much for your help, How do I now integrate this with My SharePoint Online Calendar?

That's great @tejasthite ! Do you have access to Flow? If so, may I suggest that you close this issue and we'll continue this one offline via Twitter DM? I'll come back later and update this issue with our resolution so that anyone else who needs this type of solution can benefit from it.

@hugoabernier - Yes I do have Flow. It would be always great to have the solution for the solution proposed with React Calendar Feed asap, I truly need this as well.

But at the same time if Flow is going faster right now then I am happy to implement that as well.
Thank you very much again. "let me how to proceed Further"?

@hugoabernier , Please could you update on the above? Thank you

@hugoabernier, Thank you very much for the Time from Your End - and the Microsoft Flow, Excellent work with this. I appreciate all your help. Using Flow it works Perfect.
Thank you

@tejasthite I'm glad it worked out. If anyone is looking for the solution we used, we documented the approach in this blog post and provided the step-by-step instructions in this one


black screen

I installed the extension but when I open the menu item for kubescape there are no results and if I hit scan it still returns no results.
This is on lens version 5.4.6

Hi,
Thanks for your feedback.
We'll concertedly look into that issue next week.
In the mean time, it will be best if you can supply more information:

What operating system are you using? (Windows, MAC, Linux, etc.)
Did you get proper information about your cluster in other Lens menus? (like other workload information)
Did you happen to run Kubescape cli and got different results?
What Kubescape version is being used by Lens?
(if everything was setup currently you can see the version in the upper section of Kubescape page
by hovering over the info icon.

Also, a screenshot will also be helpful.
David.

files.zip
Here they are.

Thanks @jason-hobbs !
From the files you sent me I can see that kubescape was able to finish a scan successfully.
Only the imt cluster (out of 5 clusters scanned) contains results.
I am able to see your failed controls for that cluster with the same Lens version you mentioned, running on M1 Mac though (Unfortunately I don't have access to an Intel Mac, but I'm not sure it's part of the issue in this case)

Regarding the blank screen you are getting, is it for the imt cluster?
If the answer is no, do you see anything for the imt cluster?
If the answer is yes, would you mind opening Dev Tools (Command + Option + I) and report if you see any errors in the Console?

fwiw - I'm on a M1 mac and seeing identical results. Scan runs but the page is completely blank, when I look in dev tools (at least for me) there are a couple errors

BrowserConsole.js:47 The user aborted a request. AbortErrormessage: "The user aborted a request."type: "aborted"stack: "AbortError: The user aborted a request.\n    at abort (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/node-fetch/lib/index.js:1440:16)\n    at AbortSignal.abortAndFinalize (/Applications/Lens.app/Contents/Resources/app.asar/node_modules/node-fetch/lib/index.js:1455:4)\n    at AbortSignal. (http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:522080:18)\n    at AbortSignal. (http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:522080:18)\n    at http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:598643:28\n    at http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:249106:25\n    at http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:266994:15\n    at Array.forEach ()\n    at NonInjectedClusterOverview.runDisposersOnWillUnmount (http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:266988:66)\n    at http://f1c19b5e62bef0c4eab32009190e56df.localhost:63924/build/Lens.js?f70a45f383f4c27c63bd:266597:12"[[Prototype]]: Errorconstructor: ƒ AbortError(message)name: "AbortError"[[Prototype]]: Object
webpack_modules.1246.BrowserConsole.log @ BrowserConsole.js:47
BrowserConsole.js:47 The user aborted a request. AbortError
webpack_modules.1246.BrowserConsole.log @ BrowserConsole.js:47
BrowserConsole.js:47 The user aborted a request. AbortError
webpack_modules.1246.BrowserConsole.log @ BrowserConsole.js:47

I am now seeing results in the imt cluster but not any other clusters.

I have the exact same problem running OpenLens with lens-kubescape on Linux.
OpenLens 5.5.4-latest.1654886499012
Kubescape v2.0.154
lens-kubescape 0.1.4
After the scan finishes (without any visible errors), the list stays empty. The file kubescape-report-store.json in ~/.config/Lens/extension-store/@kubescape/lens-extension does not include any data:
{
        "scanResults": [
                {
                        "clusterId": "533ed26c3ef6d71a44b5e4db2a377016",
                        "clusterName": "Dev",
                        "controls": [],
                        "frameworks": [],
                        "isScanning": false,
                        "time":<PHONE_NUMBER>667
                }
        ]
}

Don't know if the preferences look correct:
{
        "isInstalled": true,
        "kubescapeConfig": {
                "version": "v2.0.144",
                "baseDirectory": "/home/user/.config/Lens/extension_data/ecd8e19a25c4ecc596021f9eff47dcc3bc5ed5d5f4cd31745488e222e9569844/bin",
                "scanFrameworks": [
                        "allcontrols",
                        "armobest",
                        "devopsbest",
                        "mitre",
                        "nsa"
                ],
                "frameworksDirectory": "/home/user/.config/Lens/extension_data/ecd8e19a25c4ecc596021f9eff47dcc3bc5ed5d5f4cd31745488e222e9569844/bin",
                "requiredFrameworks": []
        }
}

When I run the command manually from command line, I get a bunch of data in my results file
user@nb [~/.temp/kubescape]
-> % kubescape scan framework nsa --exclude-namespaces kube-system,kube-public --format junit --output results.xml
[info] ARMO security scanner starting
[warning] Kubernetes cluster nodes scanning is disabled. This is required to collect valuable data for certain controls. You can enable it using  the --enable-host-scan flag
[info] Downloading/Loading policy definitions
[success] Downloaded/Loaded policy
[info] Accessing Kubernetes objects
[success] Accessed to Kubernetes objects
[info] Scanning. cluster: dev
[success] Done scanning. cluster: dev
[success] Scan results saved. filename: results.xml

Overall risk-score (0- Excellent, 100- All failed): 38

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Scan results have not been submitted: run kubescape with the '--submit' flag
Sign up for free: https://portal.armo.cloud/account/sign-up?utm_source=GitHub&utm_medium=CLI&utm_campaign=no_submit
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

🕵  Run with '--verbose'/'-v' flag for detailed resources view

user@nb [~/.temp/kubescape]
-> % ll
total 396K
drwxr-xr-x 2 user users 4.0K Jun 23 10:35 .
drwxr-xr-x 4 user users 4.0K Jun 23 10:35 ..
-rw-r--r-- 1 user users 388K Jun 23 10:36 results.xml
user@nb [~/.temp/kubescape]
-> %

Do you see why it is not working for me?
Thanks in advance!

@jason-hobbs, @maxnitze @cloudmatt
A new version 0.1.5 was released which I believe would fix the blank screen issue.
It seems that clicking on the "Uninstall" extension button from the Lens app does not remove the extension data (to be discussed with Lens), so just to be on the safe side, I advise you to follow the instructions below if the extension is already installed with a previous version:

Uninstall the extension from the "Installed extensions" section in Lens extension page

Remove the contents of the following directories:

Mac:
~/Library/Application Support/Lens/extension-store/@kubescape/lens-extension
~/Library/Application Support/Lens/extension_data/<YOUR_EXTENSION_ID>/bin (Contains Kubescape binary and framework JSONs)
Linux:
~/.config/Lens/extension-store/@kubescape/lens-extension
~/.config/Lens/extension_data/<YOUR_EXTENSION_ID>/bin  (Contains Kubescape binary and framework JSONs)

Install the new version

Keep me posted if it solves your issue.

In my original comment I accidentally looked into the wrong config folder. It should be ~/.config/OpenLens/... instead of Lens (I switched a couple of days ago and did not delete the config folder then). But looking at the OpenLens folder, it contained the same files with the same content (the scanFrameworks are mixed up, but otherwise the same).
Unfortunately I have the same issue there with plugin version 0.1.5.
I uninstalled the plugin and deleted all plugin-related files and folders (~/.config/OpenLens/extension-store/@kubescape and ~/.config/OpenLens/extension_data/* (I only have this one extension installed)). After starting the application again I installed the plugin again (0.1.5 was installed). When I clicked on the "Kubescape" menu entry in my "Dev" cluster the scan immediately started. But afterwards the same result: The list as well kubescape-report-store.json has no entries :cry:

@maxnitze thanks for updating.
I have pushed a new version with some more debug logs.
In order to see the logs you to perform the installation and scan operations while Lens is opened from the command line. (the logs are printed to the terminal window).
Unfortunately, I have no access to a Linux machine at the moment to confirm if Lens would work the same way as it works on my mac.

Don't forget to remove the existing extension beforehand, like you already did.

It would be great if you could provide me the logs that are printed to the terminal so I can investigate this issue.
Thanks,
Amir

i have the same problem on Windows. Ihave the latest cluster and lens
{
"isInstalled": true,
"kubescapeConfig": {
"version": "v2.0.150",
"baseDirectory": "C:\Users\maylo\AppData\Roaming\Lens\extension_data\984bbf56d4b42a2c06906eecd3d8bb268815311d11522a8d698b252fa2c1df9d\bin",
"scanFrameworks": [
"allcontrols",
"armobest",
"devopsbest",
"mitre",
"nsa"
],
"frameworksDirectory": "C:\Users\maylo\AppData\Roaming\Lens\extension_data\984bbf56d4b42a2c06906eecd3d8bb268815311d11522a8d698b252fa2c1df9d\bin",
"requiredFrameworks": []
}
}
{
"scanResults": [
{
"clusterId": "a3fd82baee93c33feb0f226807a2db75",
"clusterName"<EMAIL_ADDRESS>"controls": [],
"frameworks": [],
"isScanning": false,
"time":<PHONE_NUMBER>622,
"rawResult": {}
}
]
}

with the new version the problem is gone, thanks @amirmalka

@jason-hobbs is it windows OS ?

I am on Mac Monterey version 12.4

@jason-hobbs @jasonhobbsIMT thanks for collaborating with us on the issue.
We have fixed the following bugs you encountered in version 0.1.10:

kubeconfig location which contained spaces was passed incorrectly to the kubescape command
Renamed cluster display name in Lens caused kubescape to scan the wrong context

@maxnitze Currently Lens extension works with the old output format of kubescape. In the new format we have minimized the size drastically, however it would take me some time to support the new format.
Just to confirm that your issue is related with the size of the output, I would like to ask you to run kubescape independently on your cluster from the terminal
"/home/user/.config/OpenLens/extension_data/383a4e8840bbbfd977f58c81e55c82406aa33786bc6ba705501c8d5a3369494b/bin/kubescape" scan --use-artifacts-from "/home/user/.config/OpenLens/extension_data/383a4e8840bbbfd977f58c81e55c82406aa33786bc6ba705501c8d5a3369494b/bin" framework allcontrols,armobest,devopsbest,mitre,nsa --kube-context dev --format json > output_v1

"/home/user/.config/OpenLens/extension_data/383a4e8840bbbfd977f58c81e55c82406aa33786bc6ba705501c8d5a3369494b/bin/kubescape" scan --use-artifacts-from "/home/user/.config/OpenLens/extension_data/383a4e8840bbbfd977f58c81e55c82406aa33786bc6ba705501c8d5a3369494b/bin" framework allcontrols,armobest,devopsbest,mitre,nsa --kube-context dev --format json --format-version=v2 > output_v2

What is the size of output_v1 and output_v2?

@maxnitze it's been a while, but we have release a new version of the extension which works with files instead of stdout. As well as with new format version, which uses less space. Would you mind give it a try and report if your cluster can be scanned?

Yep, seems to work now!
I deleted everything again and re-installed the extension.
The first scan took around 10 minutes. The report-store.json grew to 65 MB.
Everything was a bit bumpy first. Lens froze. Then after a couple of minutes it reconnected to the cluster. That took some minutes. Also connecting to other clusters took some time. But after I restarted everything seems to be working. Maybe not as fast as it was before. But I can open the report, after a couple of seconds the list of affected Resources is shown, etc.
Thanks for following up on this!

@maxnitze Thanks for the feedback!


FIX: patch_environment restores pre-existing environment variables when finished

What does this PR do?

Resolves #1832
This fixes a bug in patch_environment that currently leads to pre-existing items being deleted completely from the environment variables, when they were temporarily modified by patch_environment, once the context has finished. Now, the env vars are restored to their previous values.
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[x] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[x] Did you write any new necessary tests?

Who can review?
@muellerzr

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


build(oxygen): add-on v3.1.3

This v3.1.3 add-on has the bug fix in #2027, which motivated this release. The v3.1.3 add-on also has several changes that were merged onto the master branch since the start of v3.2 development. The only one I think is worth mentioning is the SchXslt upgrade.
I tested this change in Oxygen 26.1 build<PHONE_NUMBER> using https://github.com/galtm/xspec/raw/v3.1.3/oxygen-addon.xml . I checked the subbullets under "Test the add-on 3.1.3 with latest Oxygen" in #2031 and noticed no problems.
Branch Notes
This PR is seeking to merge to the v3.1.3-release branch, not the master branch.
In a separate pull request, I will push the Oxygen commit to the master branch as well. I'll wait until after this PR is merged, just in case anything changes between now and then.

Using the URL https://github.com/xspec/xspec/raw/v3.1.3-release/oxygen-addon.xml, Oxygen offered the upgrade from v3.1.2 after I selected "Enable automatic updates checking" in Options > Preferences > Add-ons. The v3.1.3 add-on is working fine in Oxygen 26.1 build<PHONE_NUMBER>.
I also checked that the installed add-on in .../com.oxygenxml/extensions/v26.1/frameworks/io.xspec.xspec/xspec-38920bd0a7c1fbbb397acd689c00979dc79a59a2/ includes the change in #2027 which is the PR corresponding to the SHA that I used for this add-on.


Add option for expected results from a DNS query.

📑 I have found these related issues/pull requests
N/A
🏷 Feature Request Type
Change to existing monitor
🔖 Feature description
If someone were to perform a query such as "dig domain.com txt", there could be one to many results.  The current mechanism for this checks just verifies that there is a return, but does not have the ability to monitor of an expected result.  For example, if I wanted to make sure my SPF record hasn't changed, I could monitor for:
"v=spf1 include:mailserver.com ~all"
If that result doesn't match (e.g. changed, deleted), then it would alert.
✔ Solution
Include a field / option to monitor for an expected result, similar as to the "HTTP(s) - Keyword".
As well, this should not just apply to TXT records.  It would be equally important for A, AAAA, MX, SOA, etc.
❓ Alternatives
N/A
📝 Additional Context
N/A

Checking the content of dns queries is tracked in https://github.com/louislam/uptime-kuma/issues/432 and the PR to resolve this will be https://github.com/louislam/uptime-kuma/pull/3919, but it will be a while before it gets implemented.
=> closing as a duplicate


chore(main): release 1.1.39

:robot: I have created a release beep boop
1.1.39 (2023-07-21)
Bug Fixes

deps: update dependency openai-edge to v1.2.1 (#140) (919bc7a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/icoretech/airbroke/releases/tag/v1.1.39 :sunflower:


adding custom close button to examples/ modal header/ fixing typo bug

[x] Bug fix
[x] New feature
[ ] Chore
[ ] Breaking change
[x] There is an open issue which this change addresses
[x] I have read the CONTRIBUTING document.
[trying to] My commits follow the Git Commit Guidelines
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

fixing these issues
https://github.com/reactstrap/reactstrap/issues/990
https://github.com/reactstrap/reactstrap/issues/869

Any idea of when this will be released?


prerelease tags being set on the wrong commits

I have a strange situation since upgrading from 2.29.3 to 4.2.0.
We are using conventional commits and I made a fix: commit in a library which is a dependency of other libraries and apps in our monorepo.
In Gitlab the CI/CD pipeline runs semver on all affected to determine and set the next tag. This seems to correctly identify which projects should be tagged and also the tags determined by semver are correct.
The library is tagged correctly on the commit where I made the change. However, the tags for the projects that depend on the library are all over the place. The pattern seems to be that the last commit that made any changes to each project is tagged. My expectation would be that all projects are tagged on the commit I made with the change to the library which affects all these projects.
I've read the documentation about 10 times, looked for breaking changes, found out that trackDeps has changed slightly so I updated our nx.json accordingly but nothing I tried so far is fixing this issue. Am at my whits end, hope someone is familiar with this issue and is able to help.

After upgrading to 5.2.2 with nx at 19.2 one of the problems went away. Old commits are no longer re-tagged. Currently only the directly changed projects are tagged but other projects depending on the changed projects are still not tagged. They show up in the output with the message Nothing changed since last release

So I guess this is now a duplicate of https://github.com/jscutlery/semver/issues/785


Fix for #4184, avoid creating nested  elements

Description
Update topicpull to avoid attempting to create a lower-level <desc> element inside higher-level <desc> element. This can occur when:

An <xref> or <link> element points to topic 1.
Topic 1 contains a <shortdesc> with a link to topic 2.
Topic 2 contains a <shortdesc>.

Motivation and Context
Fixes #4184.
How Has This Been Tested?
I ran the testcase from #4184. I also ran gradlew test, gradlew integrationtest, and gradlew e2etest.
Type of Changes

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

A tunneling parameter is set to true() when creating content in a <desc> element. Further attempts to create a <desc> element inside this scope will return an empty sequence.
An interesting technical note here is that the tunneling parameter is applied to and checked within different templates.
The risk of breaking an existing processing flow is low. All changes are contained within the single mode="topicpull:get-stuff_get-shortdesc" template. If a user overrides this template, the changes would not affect their processing.
Documentation and Compatibility
No documentation update is needed.
A release notes entry could be something like this:

When topic <shortdesc> descriptions contained cross-reference links in circular reference loops across topics, an infinite-recursion stylesheet loop could result. Now, <shortdesc> descriptions in referenced elements are processed only one level deep.

Checklist

My code follows the code style of this project.

https://github.com/dita-ot/dita-ot/wiki/XSLT-Coding-Conventions

I would appreciate if this could be included in DITA-OT 4.1. This issue blocks a schema update we would like to roll out (converting our specialized topic-summary elements into <shortdesc> elements).

Thank you @jelovirt!


Add Tidal-hifi support

Is your feature request related to a problem? Please describe.
Tidal-hifi app is not supported and the media control does not appear.
Describe the solution you'd like
I would like that media controls have support for the Tidal-hifi app: https://github.com/Mastermindzh/tidal-hifi

The extension supports all apps which have the MPRIS interface.
Did you switch on the MPRIS interface ?


Bugfix/egork/all row ids out of range

Fixing issue https://github.com/allenai/mmda/issues/191

can you add a test case that captures what this PR is supposed to fix?

can you add a test case that captures what this PR is supposed to fix?

Hello @kyleclo I think it is ready now

@kyleclo I've added 2 more test cases with empty-non-empy and non-empty-empty pages, please take a look.


LimeSuite should build both Dynamic and Static libraries by default

Currently its only possible to build Dynamic or  Static at a time. Ideally the default compilantion should generate both .so and .a files for both static linking and dynamic linking, keeping the choice of the target compiled program.
So far I can archieve that by running two compilations:
# Compile Static
cmake .. -DBUILD_SHARED_LIBS=OFF
make -j8
sudo make install

# Build Dynamic
cmake .. -DBUILD_SHARED_LIBS=ON
make -j8
sudo make install

That leaves both libLimeSuite.a and libLimeSuite.so at /usr/lib/.
PS: I will check if I can do that in CMakeLists, but looks like a lot of code is bound to LIME_DLL define.

I don't think this is an actual issue as there is an option to compile static library so you can compile it if necessary. Dynamic library is usually preferred so it is compiled by default. In my opinion pros/cons of compiling dynamic versus compiling both by default are debatable so it is not worth putting time into changing it.
Also, I have not investigated what the standard practice is, but taking a quick look at couple of projects that I have lying on my PC (uhd and wxwidgets) revealed that both of them also compile dynamic libraries only by default.
In short, the current behaviour is not worth changing. Closing. Won't implement.

Most of the linux LGPL libraries compiles both shared and static. Since LimeSuite is apache, it should provide both and let the developer decide at compile time of its program which one to use it. Even libstdc and glibc has dynamic and static. That also affects for example this: https://github.com/myriadrf/limedrv
Golang by default should use static versions of the library and cannot issue any build command as dep, this make a hassle when compiling a golang program.

@IgnasJarusevicius reopening. I think we need to consider this.

If it is necessary to build static library just (re)run library compilation with 'BUILD_SHARED_LIBS' set to OFF. It is one of common ways to do thing and is even documented in CMAKE https://cmake.org/cmake/help/v3.0/variable/BUILD_SHARED_LIBS.html
So it is not like this is a bug or actual problem, just one of perfectly valid ways of doing things.
As far as SDRs goes, probably, the most used SDR library UHD behaves the same way in this regard.
Also, I don't buy that most of the LGPL libraries compile both static and dynamic by default as my experience is otherwise (I am yet to encounter a library that builds both by default but I don't compile from source much) and it makes more sense to decide what is build by default based on common usage scenario and not on license. So it makes sense that some core library like libstdc would build both by default as its practically part of compiler and both are needed to function properly. On the other hand all of the GUI libraries that I have ever compiled from source (wxWidgets, Qt, FLTK) build only one by default as they probably see it as a common usage scenario (and I have checked that Qt and FLTK are listed as LGPL).
So why invest time in changing what is a valid way of doing things and dealing with potential caveats? There is option to compile static library so if you need static library just use the option and compile it.

Building both static and dynamic libs at the same time ain't going to happen. On windows that would result in filename conflicts, would need changing library names or directories. Also it would double compilation times when developing, which is undesirable when compiling on embedded systems. Basically such request adds too much problems for little benefit, which can already be achieved by just building library twice.