White text on coloured background

Hi there,
is aocr able to read white text on coloured background?
Do you suggest to make images grayscale and/or invert when the text is not darker than the background?

There shouldn't be a problem with it, it all depends on how good your dataset is.
Some preprocessing could be beneficial, yes, but it all depends on your particular case, so just experiment. :)

On Saturday, Oct 26, 2019 at 10:59, Michele Fortunato<EMAIL_ADDRESS>(mailto:notifications@github.com)> wrote:
Hi there,
is aocr able to read white text on coloured background?
Do you suggest to make images grayscale and/or invert when the text is not darker than the background?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/emedvedev/attention-ocr/issues/152?email_source=notifications&email_token=AABDOQX4HCCLX7FDNFHVNR3QQP2F3A5CNFSM4JFMJQAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HUQZH3Q), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AABDOQRB6LQ23ZWKLXVH5IDQQP2F3ANCNFSM4JFMJQAA).

There shouldn't be a problem with it, it all depends on how good your dataset is. Some preprocessing could be beneficial, yes, but it all depends on your particular case, so just experiment. :)
…
On Saturday, Oct 26, 2019 at 10:59, Michele Fortunato @.*** @.***)> wrote: Hi there, is aocr able to read white text on coloured background? Do you suggest to make images grayscale and/or invert when the text is not darker than the background? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub (#152?email_source=notifications&email_token=AABDOQX4HCCLX7FDNFHVNR3QQP2F3A5CNFSM4JFMJQAKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HUQZH3Q), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AABDOQRB6LQ23ZWKLXVH5IDQQP2F3ANCNFSM4JFMJQAA).

How to get bounding box of the highlighted parts out of those GIF images??


Hapi 17

Any plans to update for Hapi 17 :) oauth2orize is the standard for NodeJS, this plugin is amazing too :)

I don't have any plans to update this, as I not longer actively help to maintain it, but i'd take a look at a PR!


[Task]: [GraphQL] [API Server] Check if we can use formData instead of pluginSpecifiedTemplates

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks

Ask here to figure out (and implement if viable) if we can use the new UQI schema's formData instead of pluginSpecifiedTemplates - so that we can save on a migration in future.

Closing since this is not possible without migrating REST API plugin as well.


one time correlation experimental data fitted with ISF equation

@tacaswell I rebased this branch , test are not passing because some lines are not covered (coverage issue)

http://nbviewer.ipython.org/github/sameera2004/my_ipy_notebook/blob/master/Time_Correlation/ISF_fitting_repeat.ipynb
Ready for review

Ipython notebook for one time correlation experimental data fitted with ISF equation
http://nbviewer.ipython.org/github/sameera2004/my_ipy_notebook/blob/master/Time_Correlation/XPCS_ISF_fitting_using_lmfit_model.ipynb

Thanks Tom

Is lmfit used in correlation.py? I didn't find it implemented yet, maybe in a new PR?

Not implemented, users can use lmfit to fit the experimental data with the intermediate scattering factor(ISF) equation. In the ipython notebook I showed it as an example.
Before I used to put residual functions using lmfit  to get the experiment data and the model. using parameter class, (http://lmfit.github.io/lmfit-py/parameters.html).
After discussing with @danielballan, I took out those functions and only keep the model. (http://lmfit.github.io/lmfit-py/model.html#the-model-class)
@licode Therefore, following line in the correlation.py can be removed,
from lmfit import minimize, Model, Parameters

I see. Because in the first ipython notebook example, corr.fit_auto_corr was implemented as a fitting function in correlation.py, but I couldn't find that function.

@licode yes I took that out

Can you put in a PR against scikit-xray-examples with that ipython notebook?

@ericdill sure I will

It is better to define that function in ipython notebook if you took it out from source code, so users can understand which function is used for fitting. If that function is standard in the field, I suggest to include it in lineshapes.py.


fix: Start install with no new window

Running Playwright.Main(new [] { "install" }) shows console window in WPF app, which does not show in normal test. In normal test we are already running under existing conhost which is started as hidden so we don't show extra window. In WPF app that uses WinExe and has no existing conhost a new console is shown for playwright.cmd. This PR makes sure that the window is hidden.
Fixes #2462

Not sure how to write a test for this, without it being super heavyweight, you will have to believe me I guess:
BEFORE:

AFTER:

@mxschmitt  please advise on the driver failure. I guess I can just push the version up to 1.31.0? But is that something you see often?

Okay so apparently this would partially https://github.com/microsoft/playwright-dotnet/pull/2451, which in turn was breaking progress from installation (because it was not inteactive anymore), and would not correctly forward the output.
WindowStyle Hidden also does not work, becuase it has no effect.
So unless progress stops requiring interactive shell there is no solution.

WindowStyle Hidden also does not work, becuase it has no effect.

FWIW we added support for WindowStyle with UseShellExecute = false on https://github.com/dotnet/runtime/pull/82662.


When writter is nil, we should not ingest events

// WriteBlock writes a one or multiple blocks to the underlying writer.
func (s *Flusher) WriteBlock(blocks []block.Block, schema typeof.Schema) error {
	if s.writer == nil || len(blocks) == 0 {
		return nil
	}

	// Merge the blocks based on the specified merging function
	// buffer, err := s.merge(blocks, schema)
	// if err != nil {
	//     return err
	// }

	// Generate the file name and write the data to the underlying writer
	return s.writer.Write(s.generateFileName(blocks[0]), blocks)
}

In Flusher, we should return an error when the writer is nil, otherwise, the badgerDB data will be deleted without writing to any writter.
It would be better to keep them in badgerDB

How about having a Writer scoped Flusher?


Use LRU-limited hash map for memoization

To prevent extreme memory usage.

We're no longer using a map, and the Vec we now use has size O(n) in the number of characters in the input string. No extreme memory usage here...


New term request_suppression by virus of host ISGF3 complex

Term name: suppression by virus of host ISGF3 complex
Definition: any process in which a virus stops, prevents, or reduces the activity of the host ISGF3 complex, a transcription factor complex that consists of a Stat1-Stat2 heterodimer and the IRF9 protein.
Reference: PMID:15825084
Reported by: mammari
Original Ticket: geneontology/ontology-requests/11014

There are lots of terms along these lines
GO:0039562    suppression by virus of host STAT activity  10,205 annotations
GO:0039564    suppression by virus of host STAT2 activity  8,597 annotations
GO:0039563    suppression by virus of host STAT1 activity  1,608 annotations
GO:0039560    suppression by virus of host IRF9 activity  5 annotations
GO:0039557    suppression by virus of host IRF7 activity
are they really all different processes?

@pmasson55 wanted to keep these.
However the terms with complexes have been replaced by 'activity', for eg suppression by virus of host ISGF3 complex would be suppression by virus of host ISGF3 activity.
I'll obsolete the complexes.
Thanks, Pascale


The same image appears twice in the file, and the second image cannot be enlarged

The same image appears twice in the file, and the second image cannot be enlarged

I tried to fix this bug today, but it seems to be more difficult than I thought...

The problem is that Obsidian generates the exact same HTML nodes for each picture. Therefore we do not really - as far as I am aware - have a method to recognize which instance of the image was hovered over. In  this case we fallback to only modifying the first image.

I was trying to add a function to count identical files, and figure out which one is currently scaled.
Like "take all the pictures from the document, then filter out the ones that link to the one you just clicked, then go through the generated list looking for a matching picture"
However, since files can, in theory, be attached in different formats (lol, who would even do that?), it turned out to be not as easy to do with the current implementation as I expected.
Also, in addition to determining the total number of identical pictures, for the case where 2 or more pictures already have the same size set, you need to determine which one is trying to be enlarged. Which also causes difficulties, as the js only replaces the first occurrence, and doesn't allow to skip some number before it...
Ok, this seemingly simple problem turned out to be much more complicated... who would have thought.
I hope my reasoning will help in solving the problem


todo primegame

allow user to access scoreboard without having to play entire game
play again feature to let user play after submitting scoreboard
multi threaded server

Ranking client side fix
Server side text file


Named pipe mode for moloch-capture.

I've been working for some time on a project to integrate moloch with the suricata IDS.
My original plan was to use the offline monitor mode to read the pcap files exported from the individual moloch threads from tmpfs partitions.  The command being:
moloch-capture -R /var/tmp/pool --recursive -m --copy --delete
The /var/tmp/pool directory contains a subdirectory for each suricata thread; ./t1, ./t2, ./t3, etc.
Unfortunately, while moloch-capture does read the pcap files and copy/delete them, the ensuing stored session pcaps very often contain out of order packets.  Reviewing the session pcap in wireshark shows that the timestamp produced by suricata is correct, however the order of stored packets is incorrect.
This appears to happen regardless of number of the number of threads or size of the pcap files.
What I would like propose is to create a new option (--pipe) to replace --delete in this use case.  This treats the files in the directory as named pipes and then opens one thread per file to read it.  Moloch-capture is started first as a reader and then suricata is configured to write to each named pipe.
The maximum number of threads should be increased as well to allow for this particular configuration.  Hopefully this will address the out-of-order packet issue.
Of course, its possible I've missed something obvious in the config.ini, if that's the case please let me know.

Can you explain the goal?   Having both suricata and moloch read the packets from the kernel (using afpacket for example) will be better/more efficient then suricata reading and then writing the packets and then having moloch read the packets.
Or is suricata doing some kind of packet reduction/packet munging that you want to take advantage of?  If so probably still better to just reimplement in moloch.

I've had a long-time goal to develop an architecture that uses suricata to log packets off a 10-100G capture mechanism, sample enough packets from each flow to extract the metadata (e.g. 64kb); then pass it moloch for storage/indexing.  Suricata can also be configured to prune tls sessions so only the ssl handshake is stored.
I know moloch was moving in this direction in the past, but at the time I wasn't able to get both programs listening to the same interface.  However, it does appear moloch can now monitor the same af_packet interface that suricata does (if suricata is started first!).
I've done some experimenting and it looks like I can get a similar effect using a 64 packet bpf/session limit.  Moloch-capture also works well when pinned to the same cores/NUMA node that I'm using for RSS.

We've never had an issue of which is started first.  What are you seeing?

Bear in mind I'm on an older AMD Piledriver system, which lacks the advanced caching architecture of the newer Intel systems.  This seems to seriously impact performance on 10G deployments.
What happens is that moloch starts normally, however when suricata starts the moloch threads peg the cpu at 100% in kernel space (red in htop).  I didn't dig into the issue as it works fine when suricata is started first.


Added reg_key and reg_value attributes to Evidence Artifacts object.

Related Issue:
https://github.com/ocsf/ocsf-schema/issues/1077
Description of changes:
The requirement simply stated in the issue linked above was to add the pre-existing reg_key and reg_value attributes to the Evidence Artifacts object.
However, because these attributes are Windows extension attributes rather than core attributes, it is necessary to extend the Evidence Artifacts object as Windows Evidence Artifacts and then add the attributes to this object.
Note that this approach follows the pattern that was previously used to add Linux-specific attributes to the Process object.

Just an off-the-cuff thought here - I admittedly haven't spun this up yet on a server to play around with. But it may be possible to have the Windows Extension simply append the reg_key and reg_value attributes to the existing Evidence Artifacts objects when the Extension is applied. Have you considered trying that? If it works, it might help keep the dictionary clean while satisfying the use case.

Just an off-the-cuff thought here - I admittedly haven't spun this up yet on a server to play around with. But it may be possible to have the Windows Extension simply append the reg_key and reg_value attributes to the existing Evidence Artifacts object when the Extension is applied. Have you considered trying that? If it works, it might help keep the dictionary clean while satisfying the use case.

If you can figure out how to do that, please let me know because I can't. I tried something like that first and got verification errors, though I might have been doing something wrong. I then looked at how the problem was solved for other extension attributes, saw the example from the Linux extension, and figured it made sense - for consistency if nothing else - to do it the same way.

Just an off-the-cuff thought here - I admittedly haven't spun this up yet on a server to play around with. But it may be possible to have the Windows Extension simply append the reg_key and reg_value attributes to the existing Evidence Artifacts object when the Extension is applied. Have you considered trying that? If it works, it might help keep the dictionary clean while satisfying the use case.

If you can figure out how to do that, please let me know because I can't. I tried something like that first and got verification errors, though I might have been doing something wrong. I then looked at how the problem was solved for other extension attributes, saw the example from the Linux extension, and figured it made sense - for consistency if nothing else - to do it the same way.

I don't mind checking into it from my end a little. I think our Splunk extension accomplishes that somewhere within its schema definitions. Will get back to you on it once I get a chance to dig in!

Hi @davemcatcisco , I had a chance to look into this, and here is one way I was able to make this work by altering the Windows extension rather than the core schema:

In extensions/windows/objects, create an evidences_ex.json, with the following contents:

{
  "caption": "Evidence Artifacts",
  "description": "A collection of evidence artifacts associated to the activity/activities that triggered a security detection.",
  "extends": "evidences",
  "attributes": {
    "reg_key": {
      "requirement": "recommended"
    },
    "reg_value": {
      "requirement": "recommended"
    }
  }
}

Doing so adds the reg_key and reg_value attributes by way of the win extension. The end result looks like this on the schema server:

To spin up a server locally and test it out, you can use this syntax in the ocsf-server repo:

SCHEMA_DIR=../ocsf-schema-fork SCHEMA_EXTENSION=extensions/windows iex -S mix phx.server

Hi @davemcatcisco , I had a chance to look into this, and here is one way I was able to make this work by altering the Windows extension rather than the core schema:

In extensions/windows/objects, create an evidences.json, with the following contents:

{
  "caption": "Evidence Artifacts",
  "description": "A collection of evidence artifacts associated to the activity/activities that triggered a security detection.",
  "extends": "evidences",
  "attributes": {
    "reg_key": {
      "requirement": "recommended"
    },
    "reg_value": {
      "requirement": "recommended"
    }
  }
}

Hi @mikeradka. Thanks for looking at this. I'm a bit confused though. My proposal also just changes the Windows extension and doesn't touch the core schema. The only difference I can see in what you did and what I did is that I've also included constraints clause. Sorry if I'm missing some really obvious difference - it's late where I am.

Hi @davemcatcisco , I had a chance to look into this, and here is one way I was able to make this work by altering the Windows extension rather than the core schema:

In extensions/windows/objects, create an evidences.json, with the following contents:

{

"caption": "Evidence Artifacts",

"description": "A collection of evidence artifacts associated to the activity/activities that triggered a security detection.",

"extends": "evidences",

"attributes": {

"reg_key": {

  "requirement": "recommended"

},

"reg_value": {

  "requirement": "recommended"

}

}

}

Hi @mikeradka. Thanks for looking at this. I'm a bit confused though. My proposal also just changes the Windows extension and doesn't touch the core schema. The only differences I can see in what you did and what I did are that (a) I've also included constraints clause and (b) I've put a detection-specific description. Sorry if I'm missing some really obvious difference - it's late where I am. For reference, here's the contents of my extensions/windows/objects/evidences.json file:

{

  "caption": "Windows Evidence Artifacts",

  "description": "Extends the evidences object to add Windows specific fields",

  "extends": "evidences",

  "attributes": {

    "reg_key": {

      "description": "Describes details about the registry key that triggered the detection.",

      "requirement": "recommended"

    },

    "reg_value": {

      "description": "Describes details about the registry value that triggered the detection.",

      "requirement": "recommended"

    }

  },

  "constraints": {

    "at_least_one": [

      "reg_key",

      "reg_value"

    ]

  }

}

Ah, I see. For some reason I had the impression the Core object was modified. I think what you have is okay, with one follow up question - are those two constraints added to the existing core constraints, or do they replace them? I would imagine they are simply added as two additional constraints. If you can confirm that is the case, then this looks good to me.

Ah, I see @davemcatcisco . For some reason I had an impression the Core object was modified. I think what you have is okay, with one follow up question - are those two constraints added to the existing core constraints, or do they replace them? I would imagine they are simply added as two additional constraints. If you can confirm that is the case, then this looks good to me.

This is interesting. When I spin up ocsf-server with my modified schema, I see the following. It has correctly picked up the two new attributes but it is continuing to use the at_least_one constraint from the base object. I'm wondering if this might be a defect in the ocsf-server. I'd appreciate your input @rmouritzen-splunk if you have a minute.

Ah, I see @davemcatcisco . For some reason I had an impression the Core object was modified. I think what you have is okay, with one follow up question - are those two constraints added to the existing core constraints, or do they replace them? I would imagine they are simply added as two additional constraints. If you can confirm that is the case, then this looks good to me.

This is interesting. When I spin up ocsf-server with my modified schema, I see the following. It has correctly picked up the two new attributes but it is continuing to use the at_least_one constraint from the base object. I'm wondering if this might be a defect in the ocsf-server. I'd appreciate your input @rmouritzen-splunk if you have a minute.

I am glad you saw this! I witnessed the same yesterday but didn't get the chance just yet to post about it. I showed @rmouritzen-splunk, in a sync yesterday.
Schema-wise, I think your changes look good, but we should probably get this addressed on the server end. I also noticed that the caption didn't change, but perhaps that is by design?

Schema-wise, I think your changes look good, but we should probably get this addressed on the server end. I also noticed that the caption didn't change, but perhaps that is by design?

@mikeradka - Are you referring to the caption in the first column of the table in my screenshot, i.e. "Registry Key" and "Registry Value"? That is how I think it should be because the pre-existing attributes there just say "File", "Process", etc.

Schema-wise, I think your changes look good, but we should probably get this addressed on the server end. I also noticed that the caption didn't change, but perhaps that is by design?

@mikeradka - Are you referring to the caption in the first column of the table in my screenshot, i.e. "Registry Key" and "Registry Value"? That is how I think it should be because the pre-existing attributes there just say "File", "Process", etc.

No, I was referring to this one:
"caption": "Windows Evidence Artifacts",
Notice that it doesn't append the Windows. I think that is okay - I wouldn't want it to change to Windows Evidence Artifacts for the Evidence object.

@mikeradka , @floydtree , @Aniak5 , @mikeradka , @zschmerber - I've just updated this as discussed on the weekly call 10 mins ago, i.e. it is now exactly as requested. I'd appreciate your approval and merge if possible. Thanks.

Approved. For the long term, we should address the constraints overlap. For tracking, i've added this PR as a reference to @rmouritzen-splunk 's server issue regarding constraints, here: https://github.com/ocsf/ocsf-schema/pull/1078

Thanks, all!


ist8310.cpp: remove unused variable(Clean up)

We don't use _ctl_reg_mismatch.
It's also incorrect to put _ctl_reg_mismatch to the function(void IST8310::check_conf(void)) end.
https://github.com/PX4/Firmware/blob/master/src/drivers/magnetometer/ist8310/ist8310.cpp#L530
https://github.com/PX4/Firmware/blob/master/src/drivers/magnetometer/ist8310/ist8310.cpp#L527

Thanks, can you check the code style?
diff --git a/src/drivers/magnetometer/ist8310/ist8310.cpp b/src/drivers/magnetometer/ist8310/ist8310.cpp.pretty
index b9f406936b..2aa621909d 100644
--- a/src/drivers/magnetometer/ist8310/ist8310.cpp
+++ b/src/drivers/magnetometer/ist8310/ist8310.cpp.pretty
@@ -228,7 +228,7 @@ private:
 	/* status reporting */
 	bool			_sensor_ok{false};		/**< sensor was found and reports ok */
 	bool			_calibrated{false};		/**< the calibration is valid */
-
+
 	enum Rotation       _rotation;

 	sensor_mag_s   _last_report{};           /**< used for info() */

src/drivers/magnetometer/ist8310/ist8310.cpp bad formatting, please run "make format" or "./Tools/astyle/fix_code_style.sh src/drivers/magnetometer/ist8310/ist8310.cpp"
Makefile:330: recipe for target 'check_format' failed

@bkueng  have done :smiley:

Thanks, great cleanup!


Mac: RangeError: minimumFractionDigits value is out of range

Hello, everyone! I'm attempting to profile my program using samply record, but i've encountered an error stating, RangeError: minimumFractionDigits value is out of range. Does anyone know how to resolve this issue or suggest a possible workaround？
Error stack from chrome console:
react-dom.production.min.js:189 RangeError: minimumFractionDigits value is out of range.
    at new NumberFormat (<anonymous>)
    at format-numbers.js:30:10
    at index.js:29:25
    at Wt (format-numbers.js:80:24)
    at qt (format-numbers.js:218:10)
    at tn (format-numbers.js:402:10)
    at sn (committed-ranges.js:171:10)
    at HS.render (Selection.js:442:17)
    at Is (react-dom.production.min.js:204:189)
    at Bs (react-dom.production.min.js:203:149)

An unhandled error was thrown in a React component. RangeError: minimumFractionDigits value is out of range.
    at new NumberFormat (<anonymous>)
    at format-numbers.js:30:10
    at index.js:29:25
    at Wt (format-numbers.js:80:24)
    at qt (format-numbers.js:218:10)
    at tn (format-numbers.js:402:10)
    at sn (committed-ranges.js:171:10)
    at HS.render (Selection.js:442:17)
    at Is (react-dom.production.min.js:204:189)
    at Bs (react-dom.production.min.js:203:149)
    at HS (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:83775)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at aT (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:106796)
    at <anonymous> (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:117:15436)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at wT (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:116294)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at div
    at s (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:192:565429)
    at div
    at t (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:192:567076)
    at div
    at div
    at yk (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:133:27240)
    at MT (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:119676)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at EB (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:150118)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at mm (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:104:7034)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at div
    at OT (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:121755)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at Nf (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:111:15336)
    at Ff
    at de (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:16836)
    at ce (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:16794)
    at QB (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:169850)
    at c (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:23866)
    at at (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:2:22138)
    at Nf (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:111:15336)
    at Mf
    at rI (https://profiler.firefox.com/main.34c9f340aad26f45bf86.bundle.js:137:170942)

Machine: Mac, Apple Silicon, M3 Max
OS: Sonoma 14.1 (23B2073)
Chrome: Version 124.0.6367.119 (Official Build) (arm64)
Thanks for any help.

I have not seen this error before, but it probably indicates that the profile JSON contains some bad data. Can you reproduce this? Can you attach the corresponding profile.json file here?

Thanks for your response.
I encountered this error each time I run `samply record. And this is my profile.json.
profile.json.tar.gz

Is it an empty file? The tar.gz file shows me an error when I unpack it.

Sorry, my fault. Here is the correct version.
profile.json.tar.gz

Ah, yes, all the sample tables are empty. You can search for samples":{"length": in the JSON.
So for some reason samply wasn't able to capture any samples.
Is it possible that the app you're running is an x86_64 app that runs via Rosetta? samply cannot profile Intel binaries. I filed #201 about showing a useful error in that case.

I have the same issue attempting to profile a rust application on OSX.
Samply runs with no error and opens the browser at localhost.
The viewer then errors with RangeError: minimumFractionDigits value is out of range because no data was actually generated.

Confirmed in my case that it is a native apple silicon binary.

Interesting! How long does the profiled process run for? Maybe it shuts down before the first sample is gathered?

@mstange Ah ... that is an interesting point, will test.


NIFI-5267 Kafka support to replay by timestamp

JIRA: NIFI-5267 Kafka support to replay by timestamp
Kafka Processor maintain message timestamp and replay by timestamp
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[x] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@joewitt recreated this one with a single commit, @pushpavanthar review again, please

@bbende can you also help with this, there is build failure( test case failure), which is not related to my changes.

Don't worry about the build failure, 2/3 builds passed, and one was for an unrelated intermittent test failure.
I tested this out and it looks good. We just need to add the @ WritesAttribute to ConsumeKafkaRecord_1_0 and ConsumeKafkaRecord_2_0 and then it can be merged. Thanks.

@bbende thanks for review and feedback. made changes accordingly.

Thanks, looks good, will merge


feat: react sdk for shield

A SDK for shield

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 49.052%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4683

Relevant Lines:
9547

💛  - Coveralls


Research how to properly avoid statefulsets update errors on actions runs

We need to handle errors for stateful set deployments

 || echo "${file} Cannot be updated."


Preview of theme

Would be great if a preview of the theme could be in the readme

I think this is a good idea for all templates so I will add this to my to-do list. Thanks for the suggestion!


Minor fix check-rabbitmq-consumers

RabbitMQ sometimes return empty string for consumers variable and crash this Sensu check, this fix will replace empty value with 0.
Log:

Check failed to run: undefined method <=' for nil:NilClass, ["/etc/sensu/plugins/check-rabbitmq-consumers.rb:126:in block in run'", "/etc/sensu/plugins/check-rabbitmq-consumers.rb:115:in each'", "/etc/sensu/plugins/check-rabbitmq-consumers.rb:115:in run'", "/opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-plugin-1.4.2/lib/sensu-plugin/cli.rb:58:in `block in class:CLI'"]

PR merged with #55


Adding TVMLKit support

Apple TV has a JS runtime that allows you to built apps with Javascript.  There are some intricacies of it though. There is no window object and you need to access Storage with the getItem and setItem functions instead of directly accessing properties on the storage object.
This PR adds support for TVMLKit by simply checking if we are in a TVMLKit environment and returning the proper localStorage object and by using the item getter/setter calls for the debug value.
Just adding some docs related to the storage API and compatibility with getItem/setItem
https://developer.mozilla.org/en-US/docs/Web/API/Storage/LocalStorage
https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage

Coverage increased (+1.2%) to 75.0% when pulling 8c14d2116b352fcbabfd8ca9d16f575484a8322b on phase2:master into 22f993216dcdcee07eb0601ea71a917e4925a30a on visionmedia:master.

Ok, PR updated to remove window. from the reference to localStorage.


Slow performance with short words in search query

Still working on a more comprehensive list but these are a couple examples that were really slow:
Collapsin response mediator protein 2
Apolipoprotein A-I binding protein (AIBP)

I bet this is related: https://github.com/TranslatorSRI/NameResolution/issues/95

@YaphetKG That's probably not related to this issue, which is caused by sending /lookup a search phrase containing a small word (e.g. A or 17). Your issue appears to be caused by using the /reverse_lookup endpoint, which should be a very quick lookup operation on Solr. I am seeing some CPU throttling going on on the web frontend -- maybe that's what's causing your issue? I've increased the memory and CPU available to the NameRes Dev fontend: https://github.com/helxplatform/translator-devops/pull/909

I'm trying to poke on CPU/memory to see if I can fix the issue that way (spoiler: doesn't look like it): https://github.com/TranslatorSRI/NameResolution/issues/152


Event::Resize is never being sent

I'm trying to detect when a window is resized but I'm never getting the Resize event. I've set the window to be resizable and I can drag it around but I'm not getting any events. I tried to just check the window size each time in the app.wait() loop but the loop stops running while I'm resizing the window so I don't see the size change until I stop. Also, I'm rendering in this loop so rendering stops when I'm resizing too.

Hi
The Resize event is a hack since FLTK doesn't actually emit them. So the only way to detect them is in the handle or handle2 methods.
    window.handle(|ev| match ev {
        Event::Resize => {
            println!("Resized");
            true
        },
        _ => false,
    });

Ahh, that's perfect. Thank you!


Document QueryClient({ defaultOptions })

Not a code bug, but a documentation "bug": The defaultOptions you can pass in when creating a QueryClient doesn't seem to be documented anywhere. Can mostly be figured out of if using Typescript, but yeah. The following isn't very helpful, without a link to what exactly DefaultOptions looks like:

The type is currently this:
export interface DefaultOptions<TError = unknown> {
    queries?: QueryObserverOptions<unknown, TError>;
    mutations?: MutationObserverOptions<unknown, TError, unknown, unknown>;
}

So maybe documentation could just cover that and link to useQuery and useMutation for what QueryObserverOptions and MutationObserverOptions are (or wherever that's covered)?

It's actually QueryClient({ defaultOptions, queryCache, mutationCache }), all of which are optional. I agree that we can improve on the docs here :)

It's actually QueryClient({ defaultOptions, queryCache, mutationCache }), all of which are optional. I agree that we can improve on the docs here :)

If you're referring to the title, yeah, sorry, not the best title. Skipped the ones already kind of clear 😛

Have a look at the type definitions and take it from there:
https://github.com/tannerlinsley/react-query/blob/f2137dc4e4553256c4ebc1891b548fe35efe9231/src/core/types.ts#L547-L550
feel free to open the PR if you like


v0.0.2

[x] tests and linter show no problems (npm t)
[x] tests are added/updated for bug fixes and new features
[x] code is properly formatted (npm run fmt)
[x] description of changes is added in CHANGELOG.md
[x] update .d.ts typings

After all, please de composite your logic to some code blocks at least.
Like:
// logger.js
const createLogger = (...
module.exports = createLogger;

//files.js
const checkDir = (...


chore: upgrade to TS 4.7, compile with NodeNext

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[x] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

I had to add ambient declarations for a few packages (namely, eta and webpackbar) that have incompatible package.json manifest formats. I hope they can be fixed soon.
I also corrected the format of our own manifests to make sure they can be consumed by external projects compiled with NodeNext. I'm already having pain with this in my own projects.
This can be a step towards #6520.
Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

Holding off till new version of vfile is released with better type declaration

maybe the explicit pluginId is a bit overkill 🤷♂ we'll see later if it's worth keeping


incorrectly detects "v := false" as a loop var

I believe there's an issue in loop var detection, take this example:
	for i := range messages {
		// ...
		var text string
		foundText := false

gets reported as: The copy of the 'for' variable "false" can be deleted (Go 1.22+) (copyloopvar)
changing this to a var foundText bool silences the issue but I think this constitutes a bug.

@tmc
Thank you for reporting the bug!!!
I will fix it as soon as possible.


[LowPriority] References to old GPU driver is kept (with zero bytes) after upgrade or downgrade the drivers on host.

It's not a error but is something that I get to see some times.
I am using LXD/LXC containers and the last time I first launched the container, my host had the driver version nvidia-418.56.
After some time I had to downgrade my host nvidia drivers to an earlier version nvidia-410.104, and after build some other software inside the container the execution of ldconfig dumped the  following message:
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libvdpau_nvidia.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ifr.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvcuvid.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-encode.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.1 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.418.56 is empty, not checked.

So I checked to see if there was some files left behind and I found the following
(References from older drivers with zero bytes.).
lrwxrwxrwx  1 root   root           24 Apr 14 21:41 libEGL_nvidia.so.0 -> libEGL_nvidia.so.410.104
-rw-r--r--  1 nobody nogroup   1031584 Feb  6 04:55 libEGL_nvidia.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libEGL_nvidia.so.418.56
lrwxrwxrwx  1 root   root           30 Apr 14 21:41 libGLESv1_CM_nvidia.so.1 -> libGLESv1_CM_nvidia.so.410.104
-rw-r--r--  1 nobody nogroup     60200 Feb  6 04:54 libGLESv1_CM_nvidia.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libGLESv1_CM_nvidia.so.418.56
lrwxrwxrwx  1 root   root           27 Apr 14 21:41 libGLESv2_nvidia.so.2 -> libGLESv2_nvidia.so.410.104
-rw-r--r--  1 nobody nogroup    111400 Feb  6 04:54 libGLESv2_nvidia.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libGLESv2_nvidia.so.418.56
lrwxrwxrwx  1 root   root           23 Apr  1 09:17 libGLX_indirect.so.0 -> libGLX_nvidia.so.418.56
lrwxrwxrwx  1 root   root           24 Apr 14 21:41 libGLX_nvidia.so.0 -> libGLX_nvidia.so.410.104
-rw-r--r--  1 nobody nogroup   1274704 Feb  6 04:56 libGLX_nvidia.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libGLX_nvidia.so.418.56
lrwxrwxrwx  1 root   root           24 Apr 14 21:41 libnvidia-cfg.so.1 -> libnvidia-cfg.so.410.104
-rw-r--r--  1 nobody nogroup    179592 Feb  6 04:54 libnvidia-cfg.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-cfg.so.418.56
-rw-r--r--  1 nobody nogroup  47842480 Feb  6 05:14 libnvidia-compiler.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-compiler.so.418.56
-rw-r--r--  1 nobody nogroup  25283584 Feb  6 05:12 libnvidia-eglcore.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-eglcore.so.418.56
lrwxrwxrwx  1 root   root           27 Apr 14 21:41 libnvidia-encode.so.1 -> libnvidia-encode.so.410.104
-rw-r--r--  1 nobody nogroup    168184 Feb  6 04:54 libnvidia-encode.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-encode.so.418.56
-rw-r--r--  1 nobody nogroup    292840 Feb  6 04:55 libnvidia-fatbinaryloader.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-fatbinaryloader.so.418.56
lrwxrwxrwx  1 root   root           24 Apr 14 21:41 libnvidia-fbc.so.1 -> libnvidia-fbc.so.410.104
-rw-r--r--  1 nobody nogroup    123112 Feb  6 04:54 libnvidia-fbc.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-fbc.so.418.56
-rw-r--r--  1 nobody nogroup  27088008 Feb  6 05:12 libnvidia-glcore.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-glcore.so.418.56
-rw-r--r--  1 nobody nogroup    578872 Feb  6 04:55 libnvidia-glsi.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-glsi.so.418.56
lrwxrwxrwx  1 root   root           24 Apr 14 21:41 libnvidia-ifr.so.1 -> libnvidia-ifr.so.410.104
-rw-r--r--  1 nobody nogroup    206888 Feb  6 04:54 libnvidia-ifr.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-ifr.so.418.56
lrwxrwxrwx  1 root   root           23 Apr 14 21:41 libnvidia-ml.so.1 -> libnvidia-ml.so.410.104
-rw-r--r--  1 nobody nogroup   1528376 Feb  6 04:58 libnvidia-ml.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-ml.so.418.56
lrwxrwxrwx  1 root   root           27 Apr 14 21:41 libnvidia-opencl.so.1 -> libnvidia-opencl.so.410.104
-rw-r--r--  1 nobody nogroup  28467576 Feb  6 05:12 libnvidia-opencl.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-opencl.so.418.56
lrwxrwxrwx  1 root   root           31 Apr  1 09:17 libnvidia-opticalflow.so.1 -> libnvidia-opticalflow.so.418.56
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-opticalflow.so.418.56
lrwxrwxrwx  1 root   root           35 Apr 14 21:41 libnvidia-ptxjitcompiler.so.1 -> libnvidia-ptxjitcompiler.so.410.104
-rw-r--r--  1 nobody nogroup  12129448 Feb  6 05:01 libnvidia-ptxjitcompiler.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-ptxjitcompiler.so.418.56
-rw-r--r--  1 nobody nogroup     14480 Feb  6 04:54 libnvidia-tls.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libnvidia-tls.so.418.56
lrwxrwxrwx  1 root   root           26 Apr 14 21:41 libvdpau_nvidia.so.1 -> libvdpau_nvidia.so.410.104
-rw-r--r--  1 nobody nogroup    991552 Feb  6 04:55 libvdpau_nvidia.so.410.104
-rw-r--r--  1 root   root            0 Apr  1 09:17 libvdpau_nvidia.so.418.56

Could be a way to make those old references go away automatically without need to exclude each one by hand ?

Any update on this issue on how to resolve this?
I am currently using the deepstream-nvidia container (nvcr.io/nvidia/deepstream:5.0.1-20.09-triton).
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-encode.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvcuvid.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvoptix.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ifr.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.440.33.01 is empty, not checked.
Got this error.
When I am doing nvidia-smi.
NVIDIA-SMI 455.23.05    Driver Version: 455.23.05.
I got this. I am trying to install tensorrt-<IP_ADDRESS> long with cuda-11.1. Any help would be great.
Thanks in advance.

Any update on this issue on how to resolve this?
I am currently using the deepstream-nvidia container (nvcr.io/nvidia/deepstream:5.0.1-20.09-triton).
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-encode.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvcuvid.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvoptix.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ifr.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.440.33.01 is empty, not checked.
Got this error.
When I am doing nvidia-smi.
NVIDIA-SMI 455.23.05    Driver Version: 455.23.05.
I got this. I am trying to install tensorrt-<IP_ADDRESS> long with cuda-11.1. Any help would be great.
Thanks in advance.

His can happen if the container image itself is built with the nvidia container runtime in use.
Do you see this issue when running the deepops container directly, or only when you try and extend it and build a new image yourself?
I’ll need to check with the deepops team to make sure they build all of their containers with runc set as the runtime and not nvidia-container-runtime.

His can happen if the container image itself is built with the nvidia container runtime in use.
Do you see this issue when running the deepops container directly, or only when you try and extend it and build a new image yourself?
I’ll need to check with the deepops team to make sure they build all of their containers with runc set as the runtime and not nvidia-container-runtime.

I am using the below command to build the container
"docker run -it --net=host --gpus=all -v path:path  nvcr.io/nvidia/deepstream:5.0.1-20.09-triton"
I am using other container, nvcr.io/nvidia/tensorrt:20.12-py3 and I am facing such issues with this container.
How to solve the above issue?

I am using the below command to build the container
"docker run -it --net=host --gpus=all -v path:path  nvcr.io/nvidia/deepstream:5.0.1-20.09-triton"
I am using other container, nvcr.io/nvidia/tensorrt:20.12-py3 and I am facing such issues with this container.
How to solve the above issue?

@klueska
Facing same issue using by extending also,
Setting up libgssapi-krb5-2:amd64 (1.16-2ubuntu0.2) ... Setting up libpq5:amd64 (10.15-0ubuntu<IP_ADDRESS>) ... Setting up binutils (2.30-21ubuntu1~18.04.4) ... Setting up libpython3.6:amd64 (3.6.9-1~18.04ubuntu1.3) ... Setting up python3.6 (3.6.9-1~18.04ubuntu1.3) ... Setting up libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.12) ... Setting up libssh-gcrypt-4:amd64 (0.8.0~20170825.94fa1e38-1ubuntu0.7) ... Setting up libcurl4:amd64 (7.58.0-2ubuntu3.12) ... Setting up libcurl4-gnutls-dev:amd64 (7.58.0-2ubuntu3.12) ... Setting up gdb (8.1.1-0ubuntu1) ... Setting up curl (7.58.0-2ubuntu3.12) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-encode.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvcuvid.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvoptix.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ifr.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.440.33.01 is empty, not checked. Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ... Processing triggers for ca-certificates (20201027ubuntu<IP_ADDRESS>) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done.
My dockerfile:
`FROM nvcr.io/nvidia/deepstream:5.0.1-20.09-triton
RUN apt-get update
RUN DEBIAN_FRONTEND="noninteractive" apt-get -y install tzdata
RUN ln -fs /usr/share/zoneinfo/Asia/Kolkata /etc/timezone
RUN dpkg-reconfigure -f noninteractive tzdata
RUN apt-get install -y python3-pip
RUN apt-get install -y libgl1-mesa-glx
RUN apt-get install -y libglib2.0-0
RUN apt-get install -y git vim
RUN apt-get install -y libsm6 libxext6
RUN apt-get install -y libxrender-dev
RUN pip3 install --upgrade pip
RUN pip install scikit-build torch==1.4.0 torchvision==0.5.0 six pycocotools terminaltables opencv-python==<IP_ADDRESS>
CMD ["/bin/bash"]`

@klueska
Facing same issue using by extending also,
Setting up libgssapi-krb5-2:amd64 (1.16-2ubuntu0.2) ... Setting up libpq5:amd64 (10.15-0ubuntu<IP_ADDRESS>) ... Setting up binutils (2.30-21ubuntu1~18.04.4) ... Setting up libpython3.6:amd64 (3.6.9-1~18.04ubuntu1.3) ... Setting up python3.6 (3.6.9-1~18.04ubuntu1.3) ... Setting up libcurl3-gnutls:amd64 (7.58.0-2ubuntu3.12) ... Setting up libssh-gcrypt-4:amd64 (0.8.0~20170825.94fa1e38-1ubuntu0.7) ... Setting up libcurl4:amd64 (7.58.0-2ubuntu3.12) ... Setting up libcurl4-gnutls-dev:amd64 (7.58.0-2ubuntu3.12) ... Setting up gdb (8.1.1-0ubuntu1) ... Setting up curl (7.58.0-2ubuntu3.12) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-encode.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cbl.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glsi.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-eglcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvcuvid.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvoptix.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-rtcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-glvkspirv.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ifr.so.440.33.01 is empty, not checked. /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.440.33.01 is empty, not checked. Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.11-2) ... Processing triggers for ca-certificates (20201027ubuntu<IP_ADDRESS>) ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done.
My dockerfile:
`FROM nvcr.io/nvidia/deepstream:5.0.1-20.09-triton
RUN apt-get update
RUN DEBIAN_FRONTEND="noninteractive" apt-get -y install tzdata
RUN ln -fs /usr/share/zoneinfo/Asia/Kolkata /etc/timezone
RUN dpkg-reconfigure -f noninteractive tzdata
RUN apt-get install -y python3-pip
RUN apt-get install -y libgl1-mesa-glx
RUN apt-get install -y libglib2.0-0
RUN apt-get install -y git vim
RUN apt-get install -y libsm6 libxext6
RUN apt-get install -y libxrender-dev
RUN pip3 install --upgrade pip
RUN pip install scikit-build torch==1.4.0 torchvision==0.5.0 six pycocotools terminaltables opencv-python==<IP_ADDRESS>
CMD ["/bin/bash"]`

Hello Everybody, I don't use docker but in LXC I do just one thing to solve this. When I update the drivers in host computer I run a script that start the container without the NVIDIA runtime enabled then I delete everything related to the Previous NVIDIA DRIVER then I enable the NVIDIA runtime again. In this way the moment the container starts the new drivers will be inserted inside the container.

Hello Everybody, I don't use docker but in LXC I do just one thing to solve this. When I update the drivers in host computer I run a script that start the container without the NVIDIA runtime enabled then I delete everything related to the Previous NVIDIA DRIVER then I enable the NVIDIA runtime again. In this way the moment the container starts the new drivers will be inserted inside the container.

That is not the case for me. I have 455 installed on my server, but when I am running the docker container, I am facing this issue. When I do nvidia-smi, I can see that drivers are 455.
| NVIDIA-SMI 455.23.05    Driver Version: 455.23.05    CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla T4            On   | 00000000:12:00.0 Off |                    0 |
| N/A   66C    P0    31W /  70W |    254MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla T4            On   | 00000000:13:00.0 Off |                    0 |
| N/A   68C    P0    30W /  70W |   1448MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  Tesla T4            On   | 00000000:37:00.0 Off |                    0 |
| N/A   75C    P0    33W /  70W |   2337MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  Tesla T4            On   | 00000000:AF:00.0 Off |                    0 |
| N/A   60C    P0    30W /  70W |   7005MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
So I tried ignoring them and went forward to install other libraries(tensorrt 7.1 and cuda 11.1), but facing so many issues.
See this issue I posted on nvidia-developer-forum
I was not able to completely install cuda-11.1 from deb file. It is saying cuda-11.1 is not yet configured due to the broken packages. The root of all these errors is the above issue.

That is not the case for me. I have 455 installed on my server, but when I am running the docker container, I am facing this issue. When I do nvidia-smi, I can see that drivers are 455.
| NVIDIA-SMI 455.23.05    Driver Version: 455.23.05    CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla T4            On   | 00000000:12:00.0 Off |                    0 |
| N/A   66C    P0    31W /  70W |    254MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla T4            On   | 00000000:13:00.0 Off |                    0 |
| N/A   68C    P0    30W /  70W |   1448MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  Tesla T4            On   | 00000000:37:00.0 Off |                    0 |
| N/A   75C    P0    33W /  70W |   2337MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  Tesla T4            On   | 00000000:AF:00.0 Off |                    0 |
| N/A   60C    P0    30W /  70W |   7005MiB / 15109MiB |      0%      Default |
|                               |                      |                  N/A |
So I tried ignoring them and went forward to install other libraries(tensorrt 7.1 and cuda 11.1), but facing so many issues.
See this issue I posted on nvidia-developer-forum
I was not able to completely install cuda-11.1 from deb file. It is saying cuda-11.1 is not yet configured due to the broken packages. The root of all these errors is the above issue.

As I mentioned before, if you are trying to extend the container image (either directly with docker build or by running it, extending it, and saving it), you need to make sure you run it with normal runc - not the nvidia-container-runtime. This may require you to change your daemon.json to make runc the default runtime during builds if you have it set to nvidia otherwise.
If you don’t do this, then „ghost“ versions of the nvidia libraries (with 0 bytes) from what were injected during the build will hang around inside the container image after the build and cause problems later on.
This happens because of the way libnvida-container mounts these library files behind the back of docker, so docker doesn’t know they are bind mounted volumes and doesn’t clean them up properly when shutting the container down after building the the image.
It’s a limitation of the design of libnvidia-container and not something easily fixed without a rearchitecture of the Nvidia container stack (which we are in the process of doing now).

As I mentioned before, if you are trying to extend the container image (either directly with docker build or by running it, extending it, and saving it), you need to make sure you run it with normal runc - not the nvidia-container-runtime. This may require you to change your daemon.json to make runc the default runtime during builds if you have it set to nvidia otherwise.
If you don’t do this, then „ghost“ versions of the nvidia libraries (with 0 bytes) from what were injected during the build will hang around inside the container image after the build and cause problems later on.
This happens because of the way libnvida-container mounts these library files behind the back of docker, so docker doesn’t know they are bind mounted volumes and doesn’t clean them up properly when shutting the container down after building the the image.
It’s a limitation of the design of libnvidia-container and not something easily fixed without a rearchitecture of the Nvidia container stack (which we are in the process of doing now).

On LXC, I’m not sure exactly what is necessary to „disable“ the nvidia stack from being used during image builds, but the principle is the same.

On LXC, I’m not sure exactly what is necessary to „disable“ the nvidia stack from being used during image builds, but the principle is the same.

after ldconfig /usr/local/cuda-10.1/lib64
I got the following error information:
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-fatbinaryloader.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.418.56 is empty, not checked.
/sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.418.56 is empty, not checked.
Do you know, what is wrong? Thanks!

Save issue:
ldconfig
# /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.510.73.05 is empty, not checked.
# /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.510.73.05 is empty, not checked.
# /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.510.73.05 is empty, not checked.
# /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libcuda.so.510.73.05 is empty, not checked.
# /sbin/ldconfig.real: File /usr/lib/x86_64-linux-gnu/libnvidia-compiler.so.510.73.05 is empty, not checked.
cat /proc/driver/nvidia/version
# NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.85.02  Tue Jul 12 16:51:23 UTC 2022
# GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
ls /usr/lib/x86_64-linux-gnu/libcuda.so.*
# /usr/lib/x86_64-linux-gnu/libcuda.so.1  /usr/lib/x86_64-linux-gnu/libcuda.so.510.73.05  /usr/lib/x86_64-linux-gnu/libcuda.so.440.118.02  /usr/lib/x86_64-linux-gnu/libcuda.so.510.85.02


Randomness in Stdlib methods

Another thing I noticed while testing (#67) is that I can't use Randomness (#45) in calls like Array/randomElement(using:).
I could perhaps add some kind of adapter type to fix it:
extension Randomness {
    var stdlib: /* Adapter<Self> */ {
        get { ... }
        set { ... }
    }
}

var fuzzer = FuzzerInt(seed: 123)
var elements = [1, 2, 3]
ler random = elements.randomElement(using: &fuzzer.stdlib)!

Alternatively, perhaps I can better with an associated type or a protocol. An associated type would be nice insofar as it lets RandomInt vend SystemRandomNumberGenerator while it based on it. Fewer generic specializations, etc.

Hm. I'm just thinking out loud at this point. But, maybe something like this could work:
public protocol Interoperable {

    associatedtype Stdlib

    init(_ stdlib: consuming Stdlib)

    consuming func stdlib() -> Stdlib

}

extension Interoperable {

    @inlinable public var stdlib: Stdlib {
        mutating _read {
            let stdlib = self.stdlib()
            yield stdlib
            self = Self(stdlib)
        }

        mutating _modify {
            var stdlib = self.stdlib()
            yield &stdlib
            self = Self(stdlib)
        }
    }
}


Adding a Rego Policy Enforcer

The standard policy enforcer is a domain-specific logical language implemented in go over JSON. In the future, policy enforcement will need to increase in complexity and coverage. Instead of increasing the complexity of the DSL in turn to address these needs, it is preferable to use a policy language designed to express these constraints, such as Rego. This PR adds an alternate Rego policy enforcer which expresses the same logic as the StandardPolicyEnforcer entirely in Rego.
We've added a RegoPolicy which implements SecurityPolicyEnforcer in securitypolicyenforcer_rego.go and a full test suite in regopolicy_test.go. The main design idea is that there are three elements which are used for evaluating the policy:

Policy objects (i.e., containers) which are translated into Rego from our existing JSON format.
Policy behavior, which is Rego that is in source control (policy.rego) which translates the enforcement logic currently in securitypolicyenforcer.go.
Policy data (i.e., state) which is maintained over the course of enforcement and fed into the Rego during a query

There is an additional element, namely the Microsoft Policy Framework (in framework.rego) which contains the majority of the enforcement logic. While at the moment this is used by the static policy.rego file, in the future it can be made available to customers who can choose to author their own policies.
To add some details on the implementation, for each Enforce* method, we query the Rego policy with a set input. On success, we modify the data object. For a simple example, see how EnforceDeviceMount works:
func (policy *RegoEnforcer) EnforceDeviceMountPolicy(target string, deviceHash string) error {
	policy.mutex.Lock()
	defer policy.mutex.Unlock()

	input := map[string]interface{}{
		"name":       "mount_device",
		"target":     target,
		"deviceHash": deviceHash,
	}
	result, err := policy.Query(input)
	if err != nil {
		return err
	}

	if !result.Allowed() {
		input_json, err := json.Marshal(input)
		if err != nil {
			return fmt.Errorf("Unable to marshal the Rego input data.")
		}

		return fmt.Errorf("device mount not allowed by policy.\ninput: %s", string(input_json))
	}

	deviceMap := policy.data["devices"].(map[string]string)
	if _, found := deviceMap[target]; found {
		input_json, err := json.Marshal(input)
		if err != nil {
			return fmt.Errorf("Unable to marshal the Rego input data.")
		}

		return fmt.Errorf("device %s already mounted.\ninput: %s", target, string(input_json))
	}

	deviceMap[target] = deviceHash
	return nil
}

The corresponding Rego for this is:
default mount_device := false
mount_device := true {
    some container in data.policy.containers
    some layer in container.layers
    input.deviceHash == layer
}

We believe that this logic is much easier to reason about and maintain over time as opposed to the current system, while also allowing for a straightforward expansion in coverage over time.

Note
This PR was intended to be additive and non-invasive, but in order to add the Rego dependencies
multiple package revs appeared to be required. This is the source of the vast majority of the files
that have been touched (i.e., in the vendor directory).

@anmaxvl when did we decide we're going to work on splitting out stuff from pkg/securitypolicy that can live in internal instead?

@anmaxvl when did we decide we're going to work on splitting out stuff from pkg/securitypolicy that can live in internal instead?

we can do this right after all the Rego PRs are in - in a few weeks from now.

I've done a number of updates here, hopefully they dont cause a lot of cascading issues with work we've already done.
If they do, then for future PRs, I'd like to do save up the small nits and do after all the core feature PRs are in. I hope that is ok with everyone. Very happy to make changes, but unless they are hugely important, I'd like to do them later so they don't conflict with code that is already written and is waiting on branches.

I've done a number of updates here, hopefully they dont cause a lot of cascading issues with work we've already done.
If they do, then for future PRs, I'd like to do save up the small nits and do after all the core feature PRs are in. I hope that is ok with everyone. Very happy to make changes, but unless they are hugely important, I'd like to do them later so they don't conflict with code that is already written and is waiting on branches.

Thanks Sean, I think we can try to delay nits (such as formatting of error messages) to another PR, as long as we get that in soon. However, I'd prefer we address exporting of symbols here. The reason being that since pkg/securitypolicy is external, anything we export from there could be picked up and used elsewhere, which can make it harder to change code in the future.
That said, this package is still early, so I think we can get away with some API changes, but we should make an effort to not change exported symbols once they are introduced.
I'm pretty sure this change mostly doesn't need any exported symbols changes, but I did notice the following, can you comment on if these all need to be done (or need to be exported)?

Renamed ErrInvalidAllowAllPolicy to ErrInvalidOpenDoorPolicy
Removed SecurityPolicyEnforcer.EnforceMountPolicy
Changed args of SecurityPolicyEnforcer.EnforceCreateContainerPolicy
Added Mounts.Append
Added StringArray
Added a bunch of MarshalRego
Added EnvRuleArray

Renamed ErrInvalidAllowAllPolicy to ErrInvalidOpenDoorPolicy
This was done in consultation with Maksim, and I believe it best to have the error naming line up with the actual name of the policy enforcement class.
Removed SecurityPolicyEnforcer.EnforceMountPolicy
@SeanTAllen can speak to the details here, but this change needs to happen.
Changed args of SecurityPolicyEnforcer.EnforceCreateContainerPolicy
This is part of the change above, and they come together.
Added Mounts.Append
This doesn't need to be exported
Added StringArray
No need to be exported, we can make this change
Added a bunch of MarshalRego
We may be able to get away with not exporting this either, need to check a few things
Added EnvRuleArray
No need to export

@kevpar @anmaxvl @dcantah I believe all the comments have been addressed at this point. We'd appreciate another review with an eye to squash and merge tomorrow AM (GMT).


makeMakefile('fetch')

I think makeMakefile('fetch') works - at least, it seems OK on my computer.
To see/run the example: Check out `inst/testviz/viz.yaml'. Then run this in R:
vizlab::makeMakefile('fetch')

This creates vizlab/make/fetch.make and other directories that will be needed by the makefile, including cache, vizlab/make/log, and vizlab/make/timestamps. Then open a bash shell (e.g., alt-t-s) and run this:
cd inst/testviz
make -f vizlab/make/fetch.make

and watch the makefile first run everything, then (on rerun) only run the check for the sciencebase timestamp (Cuyahoga_timestamp) from there on out.
I also started working on makeMakefile('process'), and plan to eventually work on makeMakefile('visualize'), but I've run out of time. someone else (@jiwalker-usgs ? @jread-usgs ? @lawinslow ?) may have to take over for a while because I'm committed to other projects for the next two weeks.

Cool, lots of what we talked about is in here!  I'll push on with the makefile building for the other parts.


Currency acceptance

The Currency only accepts some pre-defined strings.

Never mind I checked your code and found the solution

kindly close the issue if the solution is found


add step to trigger mintlify workflow

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix Traffic Monitor to not require health.polling.url if poll type is noop

If health.polling.format and health.polling.type are noop, the health.polling.url isn't used, and therefore shouldn't be required.
But it isn't trivial to do right, because the monitorconfig manager which currently errors if the url doesn't exist, doesn't know what a noop poller is, or anything about poller or format types.
So, we'll probably need to push that error down to the poller. And figure out how to do so, while still erroring in an appropriate place, and flagging the cache as polled-but-unavailable so the service starts.

@rob05c can you put a severity label on this bug? minor, medium, major or critical?


Edit and Created Notification: Added assets are removed from the "Available parts"

As user
I want that in case parts is added to affected parts table the asset is not visible in available parts anymore
so that I have a clear understanding which parts are affected parts and which one are available parts
Hints / Details

...

Acceptance Criteria

[ ] GIVEN Edit or Create Notification Dialog is open WHEN adding assets from available parts to affected parts table the assets are removed from available parts table
[ ] GIVEN Edit or Create Notification Dialog is open WHEN removing parts from affected parts the assets are added to available parts table

Out of Scope

...

Duplicate to: https://github.com/eclipse-tractusx/traceability-foss/issues/834


[Automation] Fixed NPSP settings title check

Critical Changes
Changed  tag to current value on the NPSP settings page.
Changes
Issues Closed
Community Ideas Delivered
Features Intended for Future Release
Features for Elevate Customers
New Metadata
Deleted Metadata

there seem to be some payments tests failing with iframe error, can u check if the iframe name needs to be updated for those pages as well. I am seeing some failing tests in 2gp plan for iframe @schlossmj


Add support for custom stream queries for media_extractor

Description:
This PR adds support for custom stream queries per device and media type to media_extractor.
Example entry for configuration.yaml (if applicable):
media_extractor:
  default_query: worst
  customize:
    media_player.kd55x8507c:
      video: bestvideo
      music: bestaudio
      playlist: worstaudio[ext=mp4]

Default query if no settings provided is  best.
User can override default value or set custom query per device and media type.
Examples:

bestvideo - best video only stream
best - best video + audio stream
bestaudio[ext=m4a] - best audio stream with m4a extension
worst - worst video + audio stream
bestaudio[ext=m4a]/bestaudio[ext=ogg]/bestaudio - best m4a audio, otherwise best ogg audio and only then any audio

More about format queries https://github.com/rg3/youtube-dl/blob/master/README.md#format-selection
BUT:
My settings:
media_extractor:
  default_query: best
  customize:
    media_player.kd55x8507c:
      video/videoonly: bestvideo
      video/best: best
      audio/best: bestaudio[ext=m4a]

My chromecast device (Sony Bravia with Android TV) does not support these media content types https://home-assistant.io/components/media_player/#service-media_playerplay_media
It supports media_content_type attributes like:

video/blablabla
audio/blablabla

My service call data is:
{"entity_id": "media_player.kd55x8507c", "media_content_id": "https://www.youtube.com/watch?v=VZMfhtKa-wo", "media_content_type": "audio/best"}

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[ ] New dependencies are only imported inside functions that use them ([example][ex-import]).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Could you add a config schema for this component please?

Still getting soco.exceptions.SoCoUPnPException: UPnP Error 714 received: Illegal MIME-Type for Sonos, sadly. Potentially more hackery required, but as this stands it looks good :+1:

Is it possible to send any stream to Sonos from HA using media_player.play_media service?

I've done it before with a stream of PC audio, so it is possible, just not easy.

Could you provide service data?

Same as your example.

But what was the value of "media_content_type" with working example?

Ah, I mean the stream was setup outside of hass.

Looks like sonos support only MP3, AAC and WMA for that kind of streaming. And unfortunately youtube does not support these formats.( https://sonos.custhelp.com/app/answers/detail/a_id/80/~/supported-audio-formats

Gotcha, it's a shame we can't add support for transcoding without serving the stream through hass.

Can you check your sonos devices with this url - https://soundcloud.com/bruttoband/brutto-11 and audio/mp3: bestaudio[ext=mp3]

Can anyone rerun this build as it failed because of ConnectionResetError

@minchik restarted the build for you.
{"entity_id": "media_player.sonos_bedroom", "media_content_id": "https://soundcloud.com/bruttoband/brutto-11", "media_content_type": "audio/mp3"} worked for me.

As expect it depends on whether the owner of the media contains supported streams for your device

Thanks! :crocodile:

@minchik can you update the docs for this please? Provide a link to https://github.com/rg3/youtube-dl#format-selection

ok

https://github.com/home-assistant/home-assistant.github.io/pull/3012


Remove CKEditor Underline Plugin

Steps to Reproduce

Open a page for editing

Expected Behavior
No underline plugin
Actual Behavior
There it is:

Related Issues

#1084
https://mitodl.slack.com/archives/GQ89D0Z5M/p1662474240033869

Other comments
The underline plugin does not work, as noted in #1084. I suspect it was originally added accidentally.

@ChristopherChudzicki I can do this in conjunction with my PR, if you want

@Wassaf-Shahzad IMO we should do it separately; no need for them to be done together.


Bring up business structure prototype with tests

This WIP PR features a prototype of business logic with unit tests. There is no documentation, but refer to the unit tests, they are supposed to correspond to some of the use cases.
Featured functionality:

There can be activity requests and cancellation requests (that can cancel activities)
A storage class stores requests and it is able to return requests according to their type.
Request pool takes requests from storage and exposes time-relevant requests that have not been cancelled.
Requests filtered by the pool can be grouped together (partitioned).

I have divided the business logic stuff into multiple files and did some adjustments upon which we have agreed on the mentoring session.
I propose that this PR is merged as-is, so that others can start their own PRs from the merged master without delays. I am away and probably also off the grid for the weekend.


Passing backend in URL

From<EMAIL_ADDRESS>on March 13, 2011 04:27:15
Just a little enhancement. Attached is a patch, that allows for automatic loading from arbitrary backend (?backend=php-sqlite&keyword=xyz)
Attachment: backend-url.patch
Original issue: http://code.google.com/p/wwwsqldesigner/issues/detail?id=121

From ondrej.zara on March 14, 2011 00:18:25
Commited in rev. 118, thanks!
Status: Fixed


Update typeahead.directive.ts

allow the directive to be exported

Codecov Report

Merging #1783 into development will not change coverage.
The diff coverage is 100%.

@@             Coverage Diff              @@
##           development    #1783   +/-   ##
============================================
  Coverage        85.47%   85.47%
============================================
  Files               85       85
  Lines             2292     2292
  Branches           300      300
============================================
  Hits              1959     1959
  Misses             234      234
  Partials            99       99

Impacted Files
Coverage Δ

src/typeahead/typeahead.directive.ts
76.27% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

thanks


Document Manifest Options

The readme has a section on manifest options, but doesn't say how to actually use it in the first place. Is that a special file I put somewhere, or do I pass it to the API, or what? Please document it!

Think I was having a moment and realised it goes in the source directory's package.json ;P but adding a note might save someone some time in future


Facing issue during loading ssr net model

I have armnn binary which i have converted from tflite-binary using armnn converter . when i am running that armnn-binary using executeNetwork command it is working fine.
But when I run same model using same arguments in c code . During the load of model I am getting this error
fd_armnn: /home/darshan.p/armnn/pc_version/armnn/src/armnn/layers/ElementwiseBaseLayer.cpp:30: virtual std::vectorarmnn::TensorShape armnn::ElementwiseBaseLayer::InferOutputShapes(const std::vectorarmnn::TensorShape&) const: Assertion `input0.GetNumDimensions() == input1.GetNumDimensions()' failed.
Aborted (core dumped)
can you please help me with this
@MatteoArm @MatthewARM

Hi @paragikjain
This error message indicates that the two inputs to an elementwise layer (like an addition or multiplication layer) have a different number of dimensions. Is it possible that your input layers are getting mixed up in your c code? Can you share that code?
Best regards,
Mike

Hello Mike
Thanks for Reply. Please find my code below
`
int main(int argc, char** argv)
{

    long long frame_start = 0;
    long long frame_stop = 0;
    double total_frame_time = 0;
    long long inference_start = 0;
    long long inference_stop = 0;
    double total_inference_time = 0;
    double  inference_time = 0;
    double nPerfFreq = getFrequency();
    //-------------------------------------------------------------------------------------------------------------------------------------------

    frame_start = getCycleCount();
    int img_size=48*48*3;
    float * input;
    FILE *ifile = fopen ( "./data/img_591.raw" , "rb" );
    if (!ifile) {
        std::perror("Failed to open ./data/img_591.raw : ");
        return 1;
    }
    input = (float*) malloc (sizeof(float)*img_size);
    fread (input,1,img_size*4,ifile);
    TArmnnModel m_p2d;
    std::string modelpath = "./model/model.armnn";
    m_p2d.Load(modelpath,"input_2",{"pred_pose/mul_24"});
    std::vector<std::vector<float>> output1;
    for (int l=0;l<10;l++)
    {

        inference_start = getCycleCount();
        m_p2d.Run(input);
        inference_stop = getCycleCount();
        inference_time = (((double)inference_stop - (double)inference_start)/nPerfFreq);
        std::cout << inference_time <<std::endl;
    }

    free(input);
    fclose(ifile);
    return 0;
}

`

Hi @paragikjain
Sorry for the delay, I'm afraid I didn't get a lot from your code but before ExecuteNetwork runs the model we perform a series of optimizations on it. One of those optimizations runs on every ElementwiseBaseLayer and adds a Broadcast reshape layer if the inputs have different shapes (the code is in AddBroadcastReshapeLayer.hpp).
Are these optimizations being run by your method? If they're not then you might encounter that error message. Can you share your model.armnn?
Best regards,
Mike


[Feature #1127][Plugin]Add Spark Ignite Source

Purpose of this pull request
This pull request adds spark ignite source. #1127
Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in you PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

@CalvinKirs  if developer should update tools/dependencies/known-dependencies.txt or not ？

@CalvinKirs if developer should update tools/dependencies/known-dependencies.txt or not ？

yup, checklist has corresponding docs

I'll close it due to no feedback for a long time, if you make an update, leave a comment below and I'll reopen it

@CalvinKirs please reopen it ,thanks


how to get the pytorch model for face detection?

The fold "lffd-pytorch/face_detection/saved_model/configuration_10_560_25L_8scales_v1/" is none, How can I get this model?thanks

Had the same issue too, I had to retrieve both the saved_model and symbol_farm from the original repository: https://github.com/YonghaoHe/A-Light-and-Fast-Face-Detector-for-Edge-Devices. Hope that helps!

The demo file uses MXNet. Is there a demo file for PyTorch?


Improve documentation/docstrings

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (3c90e5d) 100.00% compared to head (6f6cd89) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #144   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines          284       284
  Branches        61        61
=========================================
  Hits           284       284

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


SAK-31668 - Move org.sakaiproject dependent code out of tsugi-util

@csev Is this ready to merge?

Yes - I merged it.  It should go back to the branch as well.