download / upload speed display

Hi, great software but the speed values are a bit small, perhaps you can move it directly under the bigger windows for the network load perhaps with a fourth white window and larger font?! I have taken a screenshot to explain what I mean:
https://www.dropbox.com/s/0ezbfoxljgcxjt8/opennetmeter.jpg?dl=0
Thanks in advance and stay healthy!!

Hey @dayter1, thank you for the issue and i hope you are doing well.
Regarding the network speed location. If you notice the placement. Its actually embedded to the frame of the window.
Therefore, when switching the pages between summary, detailed and settings. The speed value and connection will always be visible.
In your suggestion, by moving it to your location. It will show up only under the summary page. I prefer having it where it currently is.
Do you have any other solutions in mind?
If its actually too small to read, i can add an option to have its font size bigger.

Guten Tag Ashfaaq Riphque,
am Samstag, 5. Februar 2022 um 09:47 schrieben Sie:

Hey @dayter1, thank you for the issue and i hope you are doing well.
Regarding the network speed location. If you notice the placement. Its actually embedded to the frame of the window.
Therefore, when switching the pages between summary, detailed and settings. The speed value and connection will always be visible.
In your suggestion, by moving it to your location. It will show up only under the summary page. I prefer having it where it currently is.
Do you have any other solutions in mind?
If its actually too small to read, i can add an option to have its font size bigger.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
Hi, I understand this problem!

Perhaps you can use a bigger font and if this is possible in the same colour scheme as the loed values perhaps with the up/down arrow!?

What do you think about that? And can you make the main window scalable and add the option to always stay on top?!

Many many thanks, stay healthy!!!

--
Mit freundlichen Grüssen
Detlev Sczesny
@.***
Telegram 0176 51603362

Perhaps you can use a bigger font and if this is possible in the same colour scheme as the loed values perhaps with the up/down arrow!?

Thats a great idea, ill try implementing this.

And can you make the main window scalable

I'm planning on adding this. there is already an issue regarding this #12

add the option to always stay on top?!

This one is a little tricky, i'll see if i can add this.
Thank you for your suggestions and you stay healthy as well!!!

Guten Tag Ashfaaq Riphque,
am Sonntag, 6. Februar 2022 um 07:36 schrieben Sie:

Perhaps you can use a bigger font and if this is possible in the same colour scheme as the loed values perhaps with the up/down arrow!?
Thats a great idea, ill try implementing this.
And can you make the main window scalable
I'm planning on adding this. there is already an issue regarding this #12
add the option to always stay on top?!
This one is a little tricky, i'll see if i can add this.
Thank you for your suggestions and you stay healthy as well!!!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
Great news, good luck :-)

Det

--
Mit freundlichen Grüssen
Detlev Sczesny
@.***
Telegram 0176 51603362

Hi Ashfaaq18,
Yes, I would also like to have this function in the OpenNetMeter.
The window is not high enough for me with "Detailed" window.
Width is good for me and the font size too.
If the window were higher or could enlarge with the mouse,
would just get all tasks displayed for me without making it bigger and bigger.
The windows are also not saved.

Hey @dayter1 and @merlin555 , just released v0.6.0 with scalable window and bigger download/upload font. Feel free to check it out.
Have to yet implement the windows always on top function. ill leave this issue open till then.

Hi Ashfaaq18,
I installed the new version 0.6.0.
Only the font size is still so small.
The window is not stored in place.
At the next start, the setting of the windows is gone again.
And I would like that if your program opens, the "Detailed" window opens.
You can set this so that just the last window, where to open, the program remember that.
Can you please fix that if you have "only" the speed in the bar,
that you can double-click with the left mouse button so that your program opens.
So far, this is just about the globe symbol.
Greetings..
Merlin

@merlin555 , thanks for the feedback. This issue refers to a different font size increase. Not the taskbar one you mentioned in #19. I did not fix that yet, I'll get to it in a few days.

The window is not stored in place.
At the next start, the setting of the windows is gone again.
And I would like that if your program opens, the "Detailed" window opens.
You can set this so that just the last window, where to open, the program remember that.
Can you please fix that if you have "only" the speed in the bar,
that you can double-click with the left mouse button so that your program opens.
So far, this is just about the globe symbol.

Btw, can you create a new issue regarding the above you've requested? it would be great if you could break them down to separate issues so its easier for me to work on.
Discussions in this thread is only about the download/upload speed display in the mainwindow panel.

Guten Tag Ashfaaq Riphque,
am Donnerstag, 3. März 2022 um 10:45 schrieben Sie:

Hey @dayter1 and @merlin555 , just released v0.6.0 with scalable window and bigger download/upload font. Feel free to check it out.
Have to yet implement the windows always on top function. ill leave this issue open till then.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
Hi, have another issue with the interface (see screenshots)!

Best regards and stay healthy!!

--
Mit freundlichen Grüssen
Detlev Sczesny
@.***
Telegram 0176 51603362

Hi, have another issue with the interface (see screenshots)!   Best regards and stay healthy!!

Hi @dayter1, I don't see the screenshots you've attached. Could you reattach and send it again?

Guten Tag Ashfaaq Riphque,
am Mittwoch, 16. März 2022 um 16:48 schrieben Sie:

Hi, have another issue with the interface (see screenshots)! Best regards and stay healthy!!
Hi @dayter1, I don't see the screenshots you've attached. Could you reattach and send it again?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
Here they are!

--
Mit freundlichen Grüssen
Detlev Sczesny
@.***
Telegram 0176 51603362

Guten Tag Ashfaaq Riphque,
am Mittwoch, 16. März 2022 um 16:48 schrieben Sie:

Hi, have another issue with the interface (see screenshots)! Best regards and stay healthy!!
Hi @dayter1, I don't see the screenshots you've attached. Could you reattach and send it again?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
Hi, after reboot your tool counts the traffic again :-)

But now I have a issue with "total usage" again (see screen)!

Best regards and stay healthy!!

--
Mit freundlichen Grüssen
Detlev Sczesny
@.***
Telegram 0176 51603362

Hi @dayter1, thanks for reporting.
I'm still facing the same problem @dayter1,

Here they are!

But now I have a issue with "total usage" again (see screen)!

I cant see any of the image attachments you've included.
You can try sending me the images to my mail address, it's available under my Github profile main page.
Or
upload them to dropbox and post the link here. Just like your first comment in this thread.
Thanks.

Guten Tag Ashfaaq Riphque,
am Sonntag, 24. April 2022 um 08:37 schrieben Sie:

Hi @dayter1, thanks for reporting.
I'm still facing the same problem @dayter1,

Here they are!
But now I have a issue with "total usage" again (see screen)!
I cant see any of the image attachments you've included.
You can try sending me the images to my mail address, it's available under my Github profile main page.
Or
upload them to dropbox and post the link here. Just like your first comment in this thread.
Thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
Cannot find your mail adress so I UL the shots to dropbox: https://www.dropbox.com/sh/gsn8hk53are9mqd/AAAQRuo3Vt1i2LXtN94m7Qyba?dl=0

--
Mit freundlichen Grüssen
Detlev Sczesny
@.***
Telegram 0176 51603362

Cannot find your mail adress so I UL the shots to dropbox: https://www.dropbox.com/sh/gsn8hk53are9mqd/AAAQRuo3Vt1i2LXtN94m7Qyba?dl=0

Thanks @dayter1, i can now view the images.
if possible, could you also include an image of the detailed view table of your ProtonVPN connection? Try to include all the processes in an image or multiple images. You can censor the process names column if necessary.


Use single pipeline

Changes to the task yamls are to allow the settings.xml to be stored in the OCI image as well thereby making it available to the deploy step. This will be useful when deploying to Indy.
tls workspace references been removed from the tasks as they aren't required (within JBS we're running with disableTLS currently so they are unused and wouldn't work in the new layout anyway).
For JBS, this normalizes to a single pipeline (note that not all of the code from the secondary pipeline added in #1597 and #1625 has been removed/reverted). I also isolated the storage for the verify step so that any testing does not affect the deploy step.

/retest


Provide way to silence warnings

We have a valid reason to not include  "mezzanine.core.middleware.SitePermissionMiddleware" in our MIDDLEWARE_CLASSES (we use an alternative implementation), but this produces a warning that we can't silence:
https://github.com/stephenmcd/mezzanine/blob/c7bc3e74d8487c6b23417ac099a46aa5c486c369/mezzanine/utils/sites.py#L75
It would be nice if Mezzanine used Django's checks framework for issues like this:
https://docs.djangoproject.com/en/1.7/topics/checks/
In this way, a developer could silence this warning individually.
I'm happy to write a patch if this idea is accepted. There are probably a few other places this could be done, although for things like deprecation warnings, there is no need - there is a right way to silence the warning, which is to fix your code.

Sounds good Luke, go for it.

Looks like #1734 fixes this one. Closing.


Update Live Demo address of zzhack

I have changed the routes of my website, so I  changed the address of the Live Demo of zzhack

cool site, thanks!


No blur effect in Firefox

firefox nightly 92.0a1 (2021-07-18) ↓

edge 91.0.864.70 ↓

Windows 10 21H1, i5 6500, RX570

Same situation on fiefox 85.0

Why Firefox is now less and less concerned :( , does open source software is no longer popular?

I am very well aware of this issue but unfortunately there isn't much I can do. Firefox doesn't support backdrop-filter and the workarounds are not good for the ui perhaps even worse. I will sure look more or maybe eliminate the blur throughly for firefox.
I'm always open for suggestions.
Ps: chromium is also an open source project.

I am very well aware of this issue but unfortunately there isn't much I can do. Firefox doesn't support backdrop-filter and the workarounds are not good for the ui perhaps even worse. I will sure look more or maybe eliminate the blur throughly for firefox.
I'm always open for suggestions.
Ps: chromium is also an open source project.

Thank you for your reply!
As far as I know, Firefox is fully open source, any line of code is, that's why I like Firefox, chromium seems to open source only the kernel? (I'm not so sure)
In addition about backdrop-filter, firefox is supported backdrop-filter (since firefox70.0, 2020), but this "feature" until today is closed by default, you need to about:config to manually open.
This is very strange I do not know why, I think for users who use firefox to open this site, maybe a pop-up window to tell the user that this thing is feasible.
Translated with DeepL (my English is poor)

As far as I know, Firefox is fully open source, any line of code is, that's why I like Firefox, chromium seems to open source only the kernel? (I'm not so sure)

No it's also fully open source here. The Google distributed version just contains a telemetry and a few settings preset.


Improve schema formatting & uniqueness check

Problem definition
Currently, whatever service tries to register as its schema, is directly stored in DB
https://github.com/pipedrive/graphql-schema-registry/blob/master/src/database/schema.ts#L259
The problem is that

performance. Doing comparison of medium text (schema as input) against medium text (stored schema) seems like a costly operation in mysql.. especially if you have a lot of schemas registered over time.
sometimes there are extra whitespaces & tabs that make schema not well formatted
if service changes even a whitespace character, then it is considered as new schema
3.1 if we would add another variable column (lets name it meta with type JSON to the schema) that could contain extra data, like query cost or access controls, then uniqueness check would become even more complex

Suggested solution

add UUID column that would be a hash of unique features (type_defs, meta etc), calculate value by hashing type_defs
add SDL schema formatting (print(parse(type_defs))
this will likely need a change in migration, so that we do JS migration, not just SQL

Related Issues

#106

solved in https://github.com/pipedrive/graphql-schema-registry/releases/tag/5.4.0


Unclear error when loading unsupported HDF5 file

Backstory - I created some H5 files with h5py containing large 3D arrays (not python dataframes). Then I forgot this and tried to load with Pandas. Since they didn't contain real dataframes the load understandably  failed. However the error thrown was:
TypeError: cannot create a storer if the object is not existing nor a value are passed
(line 1148 in pandas.io.pytables) which apart from being awkward grammar (rather cannot create a storer if the object does not exist nor a value given) doesn't suggest anything about the h5 file not being supported.
Since passing around h5 files is fairly common and sometimes they contain tables and sometimes not, it would be nice if Pandas warned you clearly that the object you are trying to load isn't a pandas-compatible table.

certainly willing to take a PR to make the error message more clear.
Unfortuntately reading h5py is pretty out of scope as its a non-easily interpretable format and doesn't have much meta data.
That said, you can use into to do this, something like
into('hdfstore:file.hdf','h5py:file.h5') will do the conversion

I agree there's no need to read h5py directly, just a more clear error. Will have a look if I get time...
-----Original Message-----
From: "jreback"<EMAIL_ADDRESS>Sent: 24/02/2015 21:26
To: "pydata/pandas"<EMAIL_ADDRESS>Cc: "mangecoeur"<EMAIL_ADDRESS>Subject: Re: [pandas] Unclear error when loading unsupported HDF5 file (#9539)
certainly willing to take a PR to make the error message more clear.
Unfortuntately reading h5py is pretty out of scope as its a non-easily interpretable format and doesn't have much meta data.
That said, you can use into to do this, something like
into('hdfstore:file.hdf','h5py:file.h5') will do the conversion
—
Reply to this email directly or view it on GitHub.


[FEATURE] REVERSE string function not available in SQL/PPL

Is your feature request related to a problem?
reverse string function is not available in the SQL parser engine.
What solution would you like?
SQL example:
SELECT reverse(\"abcd\") FROM calcs

PPL example:
source=calcs | eval `test` = reverse(\"abcd\")| fields test

What alternatives have you considered?
n/a
Do you have any additional context?
n/a

Can be closed.  This is fixed by https://github.com/opensearch-project/sql/pull/1154


[Multiple Hardwares] [Device Plugin] Read computing devices from layout.yaml

Coverage remained the same at 33.999% when pulling 7334fbde5b004fc40180396d3d7ce9d4c20add45 on zhiyuhe/fix_device_plugin into f0d9d1928750b624519758f5a1e58f0409c5e5b7 on master.

Coverage remained the same at 33.999% when pulling 7334fbde5b004fc40180396d3d7ce9d4c20add45 on zhiyuhe/fix_device_plugin into f0d9d1928750b624519758f5a1e58f0409c5e5b7 on master.


Remove webpack artefacts from the repository

Just a small QoL change to remove the build artefacts from the repo, which will minimise the diff in each future PR.
Based on the steps outlined in this page, I've also added a heroku-postbuild script to ensure those files are rebuilt after each Heroku deployment before the server is started.

Hello @crob1140 and thank you very much for your PR, I didn't even know this was possible. 😮


Invoice list page mobile view updated

Notion card
https://www.notion.so/saeloun/Mobile-responsive-page-Invoice-List-page-9f0c4e2bbb95470cb688efb98b46b8c6
https://www.notion.so/saeloun/Mobile-Responsive-Invoice-page-Menu-options-7e1f72e15cf547bc862c880c3ad23766
https://www.notion.so/saeloun/Mobile-responsive-Invoice-filter-panel-64a0d600d87a44b0adc0a656f14dcd15
Summary

Invoice list page updated according to designs (mobile view)
Filters updated according to mobile view
More options updated.
Summary dashboard common component created.
Pagination bug fiixed.

Preview

https://www.loom.com/share/f7e9b4d7eab142d9a76c0d5b5d5c110e
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactor (non-breaking and retains same functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Tested on responsive screens

Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[x] I have annotated changes in the PR that are relevant to the reviewer
[ ] I have added automated tests for my code

@Shruti-Apte The summary section is looking like this on Iphone12 pro/SE/14 . Please check and fix it

@Shruti-Apte The summary section is looking like this on Iphone12 pro/SE/14 . Please check and fix it

@Shruti-Apte Is this not fixed yet? I am getting the same results

@Shruti-Apte The summary section is looking like this on Iphone12 pro/SE/14 . Please check and fix it

@Shruti-Apte Is this not fixed yet? I am getting the same results

@AkashKale Please connect with Shruti and confirm this

@Shruti-Apte The summary section is looking like this on Iphone12 pro/SE/14 . Please check and fix it

@Shruti-Apte Is this not fixed yet? I am getting the same results

@AkashKale Please connect with Shruti and confirm this

Discussed with Shruti. It is working fine for devices with width as low as 373px which covers most of the devices. It's okay if the third data point (Amount in draft) shifts to next line for rare cases which have lesser width.
cc: @supriya3105


Explicitly confirm informers have synced with timeout

Signed-off-by: Monis Khan<EMAIL_ADDRESS>

Closing this since it's pretty bit-rotted, but I filed https://github.com/vmware-tanzu/pinniped/issues/654 for followup.


Cannot add 5th node to cluster

Adding 5th node to my microk8s cluster causes some problems that prevents the services from running. I have tried to uninstall, and reinstall several times to no avail.
I have attached the tarball.gz inspection report from my Raspberry Pi 8GB 4B+ arm64 running Ubuntu 20.04LTS.
When i enter join token command on cluster is when everything stops working on the node. Any help would be appreciated. Thanks in advance.
inspection-report-20210202_122759.tar.gz

Hi @RyzeNGrind. Could you also attach a microk8s.inspect tarball taken from the node you are trying to join to?
Could you also provide the contents of /var/snap/microk8s/current/var/kubernetes/backend/cluster.yaml? You should make sure the IP of the new node is not in that file. Thanks.

Hello @ktsakalozos Thanks for the prompt response. It seems the IP of the new node is already in the aforementioned cluster.yaml file.
I have attached the files as requsted. Should I remove the IP of the 5th node <IP_ADDRESS>? Thanks.
inspection-report-20210204_211526.tar.gz
Contents of the cluster.yaml file on pc0 (master node):
`- Address: <IP_ADDRESS>:19001
ID:<PHONE_NUMBER>608546238
Role: 0

Address: <IP_ADDRESS>:19001
ID:<PHONE_NUMBER>6949860614
Role: 0
Address: <IP_ADDRESS>:19001
ID:<PHONE_NUMBER>705267048
Role: 0
Address: <IP_ADDRESS>:19001
ID:<PHONE_NUMBER>5925992099
Role: 1
Address: <IP_ADDRESS>:19001
ID:<PHONE_NUMBER>2849221058
Role: 1`

I tried to remove the IP in the cluster.yaml file, but everytime I save and recheck the file the entry is already automatically inserted in to the file. Not sure how I can proceed. Any advice would be greatly appreciated.

@ktsakalozos Hi any updates regarding this issue?

@RyzeNGrind I missed this thread, sorry. Could you try to remove the node with microk8s.remove-node --force ?
I am also interested to know of a way to reproduce this.


Trying to modify buckets for existing http_request_latency_seconds_bucket

Currently, i have been leveraging prometheus's http_request_latency_seconds_bucket to see my web app's latency. I'm seeing latency assigned to these buckets: https://github.com/soundcloud/prometheus-clj/blob/f56c78c6dbc3feb7c4974327d93ed78173faa7d1/src/prometheus/core.clj#L13
However, these buckets don't work for my case, as many requests often exceed 5 seconds. I would need to add additional buckets greater than 5. Is there an easy way to do this?

Resolved: using :latency-histogram-buckets in iapetos.ring/initialize


Access to googlevideo.com was denied HTTP ERROR 403

This is the video that i try to download.
https://www.youtube.com/watch?v=8Wg1MYjOguI
Thanks advance.

It should be fixed in 2.9.2. Test it please

@masihyeganeh  Access deny.
please help.


SamlResponse.validateDestination() does not work with query-parameters

Hi, I'm currently writing a connector that has an query-parameter in it's assertion consumer service url. For example "https://myserver/myapp/connector?mode=acs".
This is perfectly working when strict-mode is off.
Having strict-mode on, the validation fails ("processResponse error. invalid_response") because the "validateDestination()" method compares the destination-url of the SAML message with "requestURL" of "HttpRequest" which does not contain query-parameters.
So the comparison of "https://myserver/myapp/connector?mode=acs" with "https://myserver/myapp/connector" always fails ("The response was received at https://myserver/myapp/connector instead of https://myserver/myapp/connector?mode=acs").

Any option to add the query-parameters to the HttpRequest object?
See https://github.com/onelogin/java-saml/blob/master/toolkit/src/main/java/com/onelogin/saml2/servlet/ServletUtils.java#L34
https://github.com/onelogin/java-saml/blob/master/core/src/main/java/com/onelogin/saml2/http/HttpRequest.java#L76

Well, I'm not sure what you mean ... the query-parameter are part of the HttpRequest object!
As you linked to, "makeHttpRequest()" puts them into the field "parameters" of HttpRequest. But "validateDestination()" does not take them into account.
It may be complicating, that amongst "my" parameter ("mode" in the example), there are several SAML-message parameters from the identity provider like "SAMLResponse" or "RelayState", ...
I think the most decent approch may be that "validateDestination" parses the configured acs-url ("onelogin.saml2.sp.assertion_consumer_service.binding" in "onelogin.saml.properties") and separate this into "base-url" and parameters und compare both of them seperately.
As there may be more parameters in the "actual" url they may needed to compared based on the configured acs-url.
For example the configured url has the "mode" parameter with a value of "acs", so the actual request has to have the identical parameter "mode=acs". But additional parameters like "SAMLResponse" should not be checked.
Sounds a bit complicated, but I hope you know what I mean.

I encountered the same issue previously. I gave up on using the query parameters for all SP side urls (ACS, SLO etc). Instead I used the URL paths with UUID to differentiate different SPs. Previously there are several issues. Here is the one I have opened before for your reference: https://github.com/onelogin/java-saml/issues/212. But I don't have time really working on it 😞

I see ... what I was wondering about was if it would be possible to "detect" what kind of SAML-request / -response the actual request is. This way it would be possible to only have one service-url that can switch to the necessary "Auth.processXYZ()" method.


Dropping artifacts that this branch produces

Since this is our dev branch for the form tex -> pdf/markdown, I'm dropping the committed md and pdf from this branch for clarity

I'm going to temporarily reject this merge request until we've got the tex file working completely.  That way we'll have something to compare against.


Always configure koji_promote when koji configured

When koji is configured, the koji_promote plugin should always be configured.
Currently osbs.build.build_request treats koji_promote as only being required for automated rebuilds. Instead, it should be treated as a necessary part of any koji-aware configuration. This means changing ProductionBuild.adjust_for_triggers().
Additionally, when using v2 but not v1, we should not set 'metadata_only', ie. we still want the 'docker save' output to be imported for that case (ProductionBuild.adjust_for_registry_api_versions()).
This change is part of the new scheme for Koji integration, in which the Koji Build object is always created by CG import from atomic-reactor.
See also

https://github.com/projectatomic/osbs-client/issues/367
https://github.com/projectatomic/atomic-reactor/issues/435
https://github.com/release-engineering/koji-containerbuild/issues/27

CC @maxamillion

Fixed via #378.


Implement @parameterVisibility and @returnVisibility in TypeSpec core

Implementation issue for https://github.com/Azure/typespec-azure/issues/3214
Add the following decorators:

[ ] TypeSpec.@parameterVisibility that applies to operations
[ ] TypeSpec.@returnVisibility that applies to operations
[ ] [Potentially breaking] Update HTTP getRequestVisibility to use this.
[ ] Update OpenAPI3 emitter to make use of this.
[ ] Update Autorest emitter to make use of this.
[ ] Update AzureCore.ResourceCreateOrUpdate template to use @parameterVisibility to fix 3214.

Feels like we should have the resource operation decorators set a default for these (which would likely resolve the issue in the current Azure.Core ResourceCreateOrUpdate template without having to add these decorators explicitly.
https://github.com/microsoft/typespec/blob/main/packages/rest/lib/rest-decorators.tsp#L61-L121

I think @parametersVisibility (plural).
I also think @returnTypeVisibility. Verbose but, I think rarely used.

est: 8


The meaning expressed by CudaSlice::device_ptr_mut is imprecise.

let input_data_arr: [*mut std::ffi::c_void; 2] = unsafe {
    [
        std::mem::transmute(*input_data_device.device_ptr()),
        std::mem::transmute(*output_data_device.device_ptr_mut()),
    ]
};
let cu_stream = device.cu_stream();
let ok = context.enqueue_v2(&input_data_arr, cu_stream.cast());
println!("infer ok: {}", ok);

I think it would be better if device_ptr_mut directly returns sys::CUdeviceptr.

I see what you're saying. However this is definitely a breaking change, and I'm not sure if the gains would be worth that?

Mark the old method using #[deprecated].
How about this approach?
use std::ops::{Deref, DerefMut};

struct DeviceSlice {
    ptr: std::ffi::c_ulonglong,
}

impl DeviceSlice {
    fn device_ptr(&self) -> DevicePtr {
        DevicePtr {
            raw: self.ptr,
            _marker: Default::default(),
        }
    }

    fn device_ptr_mut(&self) -> DeviceMutPtr {
        DeviceMutPtr {
            raw: self.ptr,
            _marker: Default::default(),
        }
    }
}

#[derive(Debug)]
#[repr(transparent)]
struct DevicePtr<'a> {
    raw: std::ffi::c_ulonglong,
    _marker: std::marker::PhantomData<&'a ()>,
}

impl Deref for DevicePtr<'_> {
    type Target = std::ffi::c_ulonglong;

    fn deref(&self) -> &Self::Target {
        &self.raw
    }
}

impl DevicePtr<'_> {
    fn cast<T>(&self) -> *const T {
        unsafe { std::mem::transmute(self) }
    }
}

#[derive(Debug)]
#[repr(transparent)]
struct DeviceMutPtr<'a> {
    raw: std::ffi::c_ulonglong,
    _marker: std::marker::PhantomData<&'a mut ()>,
}

impl Deref for DeviceMutPtr<'_> {
    type Target = std::ffi::c_ulonglong;

    fn deref(&self) -> &Self::Target {
        &self.raw
    }
}

impl DerefMut for DeviceMutPtr<'_> {
    fn deref_mut(&mut self) -> &mut Self::Target {
        &mut self.raw
    }
}

impl DeviceMutPtr<'_> {
    fn cast<T>(&mut self) -> *mut T {
        unsafe { std::mem::transmute(self) }
    }
}

I've thought about it, and the approach mentioned above is equivalent to using reference, but the latter is more concise, which makes it a better choice. Therefore, I think there is no need for any changes.


bottle_publisher: fix bottle info accessor

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

The old BottleInfo has been removed in https://github.com/Homebrew/brew/pull/5758/files#diff-de3bb69738cf9f6002692059922a16fbL533, the bottle_info is now a Hash.

Thanks @ lembacon ! I was just looking into this myself but you beat me at writing the PR.
This bug slipped through.
That part of the code has not much tests, though I increased the coverage in my refactoring. I hope I'll find time one day to add more tests here :)


HTML fragment

Does haddock accept HTML fragments?
In the numhask haddock, I have an svg image in the docs, and haddock renders:
![nh](docs/other/nh.svg)

as
<img src="docs/other/nh.svg" title="nh">

The image would be clickable and link to the codebase if I could say:
<object data="docs/other/nh.svg" type="image/svg+xml"></object>

If this is not possible at the moment, would it be difficult to develop a solution?

Hey, I don't think it is possible at the moment, unfortunately

I imagine it being a subset of the markdown enhancements given that arbitrary html is part of most markdown standards.

Oh yes we are definitely getting this for free once Markdown is supported


Thanos Receive - High memory usage

Thanos, Prometheus and Golang version used:
thanos, version 0.13.0 (branch: HEAD, revision: adf6facb8d6bf44097aae084ec091ac3febd9eb8)
build user:       root@ee9c796b3048
build date:       20200622-09:49:32
go version:       go1.14.2

Object Storage Provider:
S3
What happened:
We have 2 load balanced thanos receive instance with 16go of memory
Memory is continuously increasing and take 100% or RAM. Stopping receive frees the memory but problem occurs

We have recently updated 0.12.2 to 0.13.0.
We haven't this problem before but some metrics have been added
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
When memory is full, logs prints a lot of internal server error with no more explications
level=error ts=2020-06-26T07:01:54.991169587Z caller=handler.go:282 component=receive component=receive-handler err="context canceled" msg="internal server error"

Anything else we need to know:
thanos receive command line
/usr/bin/thanos receive --http-address <IP_ADDRESS>:19904 --grpc-address <IP_ADDRESS>:19903 --remote-write.address <IP_ADDRESS>:19291 --label=thanos_replica="q1thanos01" --tsdb.path=/projet/data/thanos/receive --tsdb.retention=1d --objstore.config-file=/etc/thanos/objstore.yaml
objstore definition
type: S3
config:
  bucket: "thanos-qual"
  endpoint: "storagegrid.xxxxxx:8082"
  region: "yyyyy"
  access_key: "zzzz"
  secret_key: "******"
  insecure: false
  signature_version2: true
  encrypt_sse: false
  put_user_metadata: {}
  http_config:
    idle_conn_timeout: 90s
    response_header_timeout: 2m
    insecure_skip_verify: true
  trace:
    enable: false
  part_size: 134217728

We have also seen some problems with blocks being cut, @krasi-georgiev is investigating this. For us restarting the process fixes the problem for now, but you may need to do this every couple of days until the problem is resolved.

Is it a 0.13.0 issue ?
Can i downgrade version ?

have this problem too, @mxmorin did you downgrade to 0.12.2?

No. I stayed in 0.13.0 because of OOM when restarting with 0.12.2
I kill the process every day by crontab for workaround

Hi, We fixed major leaks in storeAPI.Series that also impacted write and compact and resulted in high memory use. Fix: https://github.com/thanos-io/thanos/pull/2866
See also a related issue: https://github.com/thanos-io/thanos/issues/2823
We also improved our suite so it will be easier to catch those on our PRs :hugs:
I would recommend giving try to  master-2020-07-09-60ede4c1
We just roll this to production and we see that go routines leak are starting to look better so far:

I am marking this as done :hugs: If still not fixed on prod let's reopen. Thanks for reporting!


"how to install an operator" using out of date OLM CRD/CR.

This refers to installing the CRDs/CRs for a basic OLM install under the "How do I get Operator Lifecycle Manager?" section, but these are woefully out of date.  These actually point to v0.18.3 of OLM.  Evidently OLM switched to a goreleaser config which instead captures the artifacts with tagged releases.
So this should be migrated to a way that looks like the scripted steps
curl -L https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.26.0/install.sh -o install.sh
chmod +x install.sh
./install.sh v0.26.0

c.f. https://github.com/operator-framework/operator-lifecycle-manager/releases/latest

/remove-lifecycle stale


Tutorial example

New example to match the current Yoga tutorial

@n1ru4l I ended up merging it into the hackernews example.
I intentionally split it into 2 commits:
The first one is without the final stage, second is the complete thing - as the codegen "magic" in the last tutorial step makes stuff less upfront and harder to navigate.
Maybe worth mark it as a bonus step and remove the last commit? what do you think?


Remove node-pre-gyp from bundled dependencies

It seems like the intent was to remove node-pre-gyp from the 1.x branch, but it's still present in bundledDependencies. Remove from there as well so dependencies that can't yet upgrade from 1.x stop getting security audit failures.

I think this was intentional. Perhaps without it fsevents won't build at all machines.

1.2.12 is out w updated deps

@paulmillr: thanks so much. That 1.2.12 release fixes so many audit failures!


Add set_secret function to the module

This pull request add a write_secret execution function, as noted in #1

Thanks!


tiny change

I actually had the python syntax highlighting in there a while back. The issue is that it is valid markdown syntax on GitHub, but it is not a part of the markdown specification. I use pandoc in the projects setup.py file to convert markdown to restructured text format when I deploy to pypi. Unfortunately if I include the GitHub style syntax highlighting the page fails to render properly in pypi (https://pypi.python.org/pypi/ChatterBot).

Oh I see. Ok, thats fine then.


Search: make departments facet more prominent

As a user, I'd like to filter by department and I don't see the option.
Acceptance Criteria:

[ ] Move Department to the first facet, above Level
[ ] collapse all facets by default
[ ] include a screenshot with the PR

I updated the description, removing "only display the first 5 options" and adding "collapse all facets by default"


DP-3 - DistributedLog Operation Primitives

This is the master ticket for tracking new dlog primitivies:

[ ] Introduce LogStatus structure
[ ] Implement GetLogStatus API
[ ] Implement RenameLog API
[ ] Implement ListLogs API

I am trying to pick up the DP-3 to work on.


feat(linter): improve no_redeclare rule implementation

Current dependencies on/for this PR:

main

PR #2084   👈

This stack of pull requests is managed by Graphite.

We still get a 4% performance improvement in the pdf.js benchmark

Can you test this in other codebases?
I assume you have a folder of codebases to test lint rules :-), if not:
https://github.com/oxc-project/oxc/blob/main/MAINTENANCE.md#release-linter
oxlint -D no-redeclare

Feel free to merge once you have tested this PR in real codebases.

The https://github.com/oxc-project/oxc/pull/2010 caused a panic.

I have tested it, and the report message is expected. I think we can good to merge it.


Cork Exception on HTTP1.1 - POST method

Dear @alexhultman
I am using the library for HTTP/1.1 (no ssl) server to handle my client requests
For TPS load test, I just create the simple curl client to send post requests with 20 async threads to the server (around 100,000 requests) , but server crashes randomly and it is randomly throw the exception below:
Error: Cork buffer must not be acquired without checking canCork!
terminate called without an active exception

is there any suggestion ?


ERROR: Failed building wheel for transformer-engine

I am trying to install TransformerEngine using following :
pip install git+https://github.com/NVIDIA/TransformerEngine.git@stable
facing following error
      RuntimeError: Error when running CMake: Command '['/tmp/pip-req-build-wpw9pxi1/.eggs/cmake-3.28.3-py3.11-linux-x86_64.egg/cmake/data/bin/cmake', '-S', '/tmp/pip-req-build-wpw9pxi1/transformer_engine', '-B', '/tmp/tmps_krasnv', '-DCMAKE_BUILD_TYPE=Release', '-DCMAKE_INSTALL_PREFIX=/tmp/pip-req-build-wpw9pxi1/build/lib.linux-x86_64-cpython-311', '-Dpybind11_DIR=/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/pybind11/share/cmake/pybind11']' returned non-zero exit status 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for transformer-engine
  Running setup.py clean for transformer-engine
Failed to build transformer-engine
ERROR: Could not build wheels for transformer-engine, which is required to install pyproject.toml-based projects

It looks like there's a compilation error when building the core C++ library. Can you provide more of the error message so we can figure out where the error is coming from? I wonder if it's that same as https://github.com/NVIDIA/TransformerEngine/issues/694.

`Collecting git+https://github.com/NVIDIA/TransformerEngine.git@stable
Cloning https://github.com/NVIDIA/TransformerEngine.git (to revision stable) to /tmp/pip-req-build-fgxtbhtl
Running command git clone --filter=blob:none --quiet https://github.com/NVIDIA/TransformerEngine.git /tmp/pip-req-build-fgxtbhtl
Running command git checkout -b stable --track origin/stable
Switched to a new branch 'stable'
Branch 'stable' set up to track remote branch 'stable' from 'origin'.
Resolved https://github.com/NVIDIA/TransformerEngine.git to commit 5b90b7f5ed67b373bc5f843d1ac3b7a8999df08e
Running command git submodule update --init --recursive -q
Preparing metadata (setup.py) ... done
Requirement already satisfied: pydantic in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from transformer-engine==1.3.0+5b90b7f) (2.6.3)
Requirement already satisfied: torch in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from transformer-engine==1.3.0+5b90b7f) (2.2.1)
Collecting flash-attn!=2.0.9,!=2.1.0,<=2.4.2,>=2.0.6 (from transformer-engine==1.3.0+5b90b7f)
Using cached flash_attn-2.4.2-cp311-cp311-linux_x86_64.whl
Requirement already satisfied: einops in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from flash-attn!=2.0.9,!=2.1.0,<=2.4.2,>=2.0.6->transformer-engine==1.3.0+5b90b7f) (0.7.0)
Requirement already satisfied: packaging in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from flash-attn!=2.0.9,!=2.1.0,<=2.4.2,>=2.0.6->transformer-engine==1.3.0+5b90b7f) (23.2)
Collecting ninja (from flash-attn!=2.0.9,!=2.1.0,<=2.4.2,>=2.0.6->transformer-engine==1.3.0+5b90b7f)
Using cached ninja-<IP_ADDRESS>-py2.py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl.metadata (5.3 kB)
Requirement already satisfied: annotated-types>=0.4.0 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from pydantic->transformer-engine==1.3.0+5b90b7f) (0.6.0)
Requirement already satisfied: pydantic-core==2.16.3 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from pydantic->transformer-engine==1.3.0+5b90b7f) (2.16.3)
Requirement already satisfied: typing-extensions>=4.6.1 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from pydantic->transformer-engine==1.3.0+5b90b7f) (4.10.0)
Requirement already satisfied: filelock in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (3.13.1)
Requirement already satisfied: sympy in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (1.12)
Requirement already satisfied: networkx in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (3.2.1)
Requirement already satisfied: jinja2 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (3.1.3)
Requirement already satisfied: fsspec in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (2024.2.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (12.1.105)
Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (12.1.105)
Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (12.1.105)
Requirement already satisfied: nvidia-cudnn-cu12==<IP_ADDRESS> in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12==<IP_ADDRESS> in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cufft-cu12==<IP_ADDRESS> in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-curand-cu12==<IP_ADDRESS> in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusolver-cu12==<IP_ADDRESS> in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cusparse-cu12==<IP_ADDRESS> in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-nccl-cu12==2.19.3 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (2.19.3)
Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (12.1.105)
Requirement already satisfied: triton==2.2.0 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from torch->transformer-engine==1.3.0+5b90b7f) (2.2.0)
Requirement already satisfied: nvidia-nvjitlink-cu12 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from nvidia-cusolver-cu12==<IP_ADDRESS>->torch->transformer-engine==1.3.0+5b90b7f) (12.3.101)
Requirement already satisfied: MarkupSafe>=2.0 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from jinja2->torch->transformer-engine==1.3.0+5b90b7f) (2.1.5)
Requirement already satisfied: mpmath>=0.19 in ./anaconda3/envs/NeMo/lib/python3.11/site-packages (from sympy->torch->transformer-engine==1.3.0+5b90b7f) (1.3.0)
Using cached ninja-<IP_ADDRESS>-py2.py3-none-manylinux1_x86_64.manylinux_2_5_x86_64.whl (307 kB)
Building wheels for collected packages: transformer-engine
Building wheel for transformer-engine (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [163 lines of output]
/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/init.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!
          ********************************************************************************
          Requirements should be satisfied by a PEP 517 installer.
          If you are using pip, you can try `pip install --use-pep517`.
          ********************************************************************************

  !!
    dist.fetch_build_eggs(dist.setup_requires)
  running bdist_wheel
  /home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/torch/utils/cpp_extension.py:500: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
    warnings.warn(msg.format('we could not find ninja.'))
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-cpython-311
  creating build/lib.linux-x86_64-cpython-311/transformer_engine
  copying transformer_engine/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/float8_tensor.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/utils.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/constants.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/attention.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/transformer.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/numerics_debug.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/jit.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/te_onnx_extensions.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/distributed.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/softmax.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/export.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/cpu_offload.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  copying transformer_engine/pytorch/fp8.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/common
  copying transformer_engine/common/utils.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/common
  copying transformer_engine/common/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/common
  copying transformer_engine/common/recipe.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/common
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/utils.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/constants.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/recompute.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/cpp_extensions.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/profile.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/fp8_buffer.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/distributed.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  copying transformer_engine/paddle/fp8.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/sharding.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/layernorm.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/cpp_extensions.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/fused_attn.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/dot.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/mlp.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/softmax.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  copying transformer_engine/jax/fp8.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/layernorm_linear.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/_common.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/linear.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/layernorm.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/rmsnorm.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/layernorm_mlp.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  copying transformer_engine/pytorch/module/base.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/module
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/transpose.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/normalization.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/fused_attn.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/cast.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/activation.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  copying transformer_engine/pytorch/cpp_extensions/gemm.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/pytorch/cpp_extensions
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/attention.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/layernorm_linear.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/linear.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/layernorm.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/transformer.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/softmax.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/layernorm_mlp.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  copying transformer_engine/paddle/layer/base.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/paddle/layer
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/jax/praxis
  copying transformer_engine/jax/praxis/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax/praxis
  copying transformer_engine/jax/praxis/module.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax/praxis
  copying transformer_engine/jax/praxis/transformer.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax/praxis
  creating build/lib.linux-x86_64-cpython-311/transformer_engine/jax/flax
  copying transformer_engine/jax/flax/__init__.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax/flax
  copying transformer_engine/jax/flax/module.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax/flax
  copying transformer_engine/jax/flax/transformer.py -> build/lib.linux-x86_64-cpython-311/transformer_engine/jax/flax
  running build_ext
  Building CMake extension transformer_engine
  Running command /tmp/pip-req-build-fgxtbhtl/.eggs/cmake-3.28.3-py3.11-linux-x86_64.egg/cmake/data/bin/cmake -S /tmp/pip-req-build-fgxtbhtl/transformer_engine -B /tmp/tmpfzxgbal5 -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/tmp/pip-req-build-fgxtbhtl/build/lib.linux-x86_64-cpython-311 -Dpybind11_DIR=/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/pybind11/share/cmake/pybind11
  -- The CUDA compiler identification is unknown
  -- The CXX compiler identification is GNU 11.4.0
  CMake Error at CMakeLists.txt:15 (project):
    No CMAKE_CUDA_COMPILER could be found.

    Tell CMake where to find the compiler by setting either the environment
    variable "CUDACXX" or the CMake cache entry CMAKE_CUDA_COMPILER to the full
    path to the compiler, or to the compiler name if it is in the PATH.

  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: /usr/bin/c++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Configuring incomplete, errors occurred!
  Traceback (most recent call last):
    File "/tmp/pip-req-build-fgxtbhtl/setup.py", line 353, in _build_cmake
      subprocess.run(command, cwd=build_dir, check=True)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/subprocess.py", line 569, in run
      raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['/tmp/pip-req-build-fgxtbhtl/.eggs/cmake-3.28.3-py3.11-linux-x86_64.egg/cmake/data/bin/cmake', '-S', '/tmp/pip-req-build-fgxtbhtl/transformer_engine', '-B', '/tmp/tmpfzxgbal5', '-DCMAKE_BUILD_TYPE=Release', '-DCMAKE_INSTALL_PREFIX=/tmp/pip-req-build-fgxtbhtl/build/lib.linux-x86_64-cpython-311', '-Dpybind11_DIR=/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/pybind11/share/cmake/pybind11']' returned non-zero exit status 1.

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-req-build-fgxtbhtl/setup.py", line 626, in <module>
      main()
    File "/tmp/pip-req-build-fgxtbhtl/setup.py", line 611, in main
      setuptools.setup(
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/__init__.py", line 103, in setup
      return distutils.core.setup(**attrs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 185, in setup
      return run_commands(dist)
             ^^^^^^^^^^^^^^^^^^
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
      dist.run_commands()
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
      self.run_command(cmd)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/dist.py", line 989, in run_command
      super().run_command(command)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/wheel/bdist_wheel.py", line 364, in run
      self.run_command("build")
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/dist.py", line 989, in run_command
      super().run_command(command)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/command/build.py", line 131, in run
      self.run_command(cmd_name)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/dist.py", line 989, in run_command
      super().run_command(command)
    File "/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/tmp/pip-req-build-fgxtbhtl/setup.py", line 383, in run
      ext._build_cmake(
    File "/tmp/pip-req-build-fgxtbhtl/setup.py", line 355, in _build_cmake
      raise RuntimeError(f"Error when running CMake: {e}")
  RuntimeError: Error when running CMake: Command '['/tmp/pip-req-build-fgxtbhtl/.eggs/cmake-3.28.3-py3.11-linux-x86_64.egg/cmake/data/bin/cmake', '-S', '/tmp/pip-req-build-fgxtbhtl/transformer_engine', '-B', '/tmp/tmpfzxgbal5', '-DCMAKE_BUILD_TYPE=Release', '-DCMAKE_INSTALL_PREFIX=/tmp/pip-req-build-fgxtbhtl/build/lib.linux-x86_64-cpython-311', '-Dpybind11_DIR=/home/shabs/anaconda3/envs/NeMo/lib/python3.11/site-packages/pybind11/share/cmake/pybind11']' returned non-zero exit status 1.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for transformer-engine
Running setup.py clean for transformer-engine
Failed to build transformer-engine
ERROR: Could not build wheels for transformer-engine, which is required to install pyproject.toml-based projects
`

I solved this issue by simply use this command
git submodule update --init --recursive

Under the TransformerEngine dir, I hope this might help you.

Make sure the symlinks /usr/local/cuda and /usr/local/cuda-12 are pointing to your installation (like /usr/local/cuda-12.5) instead of /etc/alternatives/cuda or some other location.
sudo rm -rf /usr/local/cuda
sudo rm -rf /usr/local/cuda-12
sudo ln -s /usr/local/cuda-12.5 /usr/local/cuda
sudo ln -s /usr/local/cuda-12.5 /usr/local/cuda-12

Also set up your env variables. Edit ~/.bashrc and add:
export PATH=/usr/local/cuda-12.5/bin${PATH:+:${PATH}}
export CUDA_PATH=/usr/local/cuda-12.5
export CUDA_HOME=/usr/local/cuda-12.5
export LD_LIBRARY_PATH=/usr/local/cuda-12.5/lib64:$LD_LIBRARY_PATH
export CUDACXX=/usr/local/cuda-12.5/bin/nvcc
export PATH=/usr/local/cuda-2.5/bin/nvcc:$PATH

I  fixed  this bugs by  add export PATH=/usr/local/cuda/bin:$PATH to .bashrc .
That cost me one afternoon.

For future reference, https://github.com/NVIDIA/TransformerEngine/issues/700#issuecomment-1979377899 provides instructions on installing CUDA so it is available to CMake. I'll close this issue so this guidance is easier for other users to find.


feat added arm64 to ArchConfig of operator

I built multi arch images (amd64 & arm64) for istio https://github.com/querycap/istio
but without arm64 arch config, i could not install istio by istioctl with simple command.
istioctl install --dry-run --set hub=querycapistio --set values.global.arch.arm64=2

now I have to overwrite affinity like
https://github.com/querycap/istio/blob/master/deploy/istio-operator.yaml#L13
         affinity: &affinity
            # important overwrites.
            nodeAffinity:
              requiredDuringSchedulingIgnoredDuringExecution:
                nodeSelectorTerms:
                  - matchExpressions:
                      - key: beta.kubernetes.io/arch
                        operator: In
                        values:
                          - arm64
                          - amd64

This pr will fix this.
I hope arm64 version could be merged to istio,
but some issues may be resolved as i list https://github.com/istio/istio/issues/26652#issuecomment-714858976
[ ] Configuration Infrastructure
[ ] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[x] Does not have any changes that may affect Istio users.

Hi @morlay. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@morlay: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
04624ae6451dbde2b226bb1b746b98209f6f4e59
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Yes. but now still use global.values.arch to render affinity.
There have no flags of istioctl to disable it.

/retest protoc results fix

@morlay: The /retest command does not accept any targets.
The following commands are available to trigger jobs:

/test unit-tests_istio
/test release-test_istio
/test benchmark_istio
/test integ-pilot-k8s-tests_istio
/test integ-security-k8s-tests_istio
/test integ-telemetry-k8s-tests_istio
/test integ-telemetry-mc-k8s-tests_istio
/test integ-multicluster-k8s-tests_istio
/test integ-distroless-k8s-tests_istio
/test integ-ipv6-k8s-tests_istio
/test integ-operator-controller-tests_istio
/test integ-pilot-multicluster-tests_istio
/test integ-external-istiod-mc-tests_istio
/test integ-security-multicluster-tests_istio
/test integ-helm-tests_istio
/test install-cni-test_istio
/test analyze-tests_istio
/test lint_istio
/test gencheck_istio
/test release-notes_istio

Use /test all to run the following jobs:

unit-tests_istio
release-test_istio
integ-pilot-k8s-tests_istio
integ-security-k8s-tests_istio
integ-telemetry-k8s-tests_istio
integ-multicluster-k8s-tests_istio
integ-distroless-k8s-tests_istio
integ-ipv6-k8s-tests_istio
integ-operator-controller-tests_istio
integ-pilot-multicluster-tests_istio
integ-external-istiod-mc-tests_istio
integ-helm-tests_istio
install-cni-test_istio
analyze-tests_istio
lint_istio
gencheck_istio
release-notes_istio

In response to this:

/retest protoc results fix

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test gencheck_istio

@morlay: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
897b2282bc612ac5e6c529fdbeda8a00beba126b
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morlay: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

gencheck_istio
897b2282bc612ac5e6c529fdbeda8a00beba126b
link
/test gencheck_istio

integ-pilot-k8s-tests_istio
897b2282bc612ac5e6c529fdbeda8a00beba126b
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Provide automated license scans on releases

Situation
At the moment 3RD_PARTY_LICENSES.txt is maintained manually at releases.
Wanted
This must be automated in github workflow for releases. See https://github.com/company-jcup/fort/blob/master/.github/workflows/scan.yml for example (black duck integration).
The output file shall be automatically update the 3RD_PARTY_LICENSES.txt file in master  branch on remote repository

Hi @de-jcup Is this issue still relevant, might be able to support you with the Implementation.


Heterogeneous cross-company defect prediction by unified metric representation and CCA-based transfer learning

http://dl.acm.org/ft_gateway.cfm?id=2786813&ftid=1615537&dwn=1&CFID=725641379&CFTOKEN=87982003

In their experiment they have used 14 publicly available datasets from four different companies: NASA, SOFTLAB, ReLink and AEEEM as the test data, but there is no link to the actual datasets in one place as they have been collected from different places:
Datasets from SOFTLAB and NASA are obtained from PROMISE repository (http://promisedata.org/repository, 2007)
AEEEM dataset is collected by D’Ambros et al [24]
ReLink dataset is collected by Wu et al. [23]


The ortResultRule class does not support issue() calls, only error(), warning(), and hint()

The ortResultRule class does not support issue() calls [1], like PackageRule[2] and LicenseRule[3] do.
Instead it only allows error(), warning(), and hint() as "issue types".
However, the example rules suggest  [4], that issue() is the right/clean way to set the Severity of an issue.
I personally would prefer this as well.
Also it could be argued that all "issue types" should be defined only once, instead of redundant like it is done now [1] [2] [3].
Which is also likely the reason, why this inconsistency happend in the first place.
[1] https://github.com/oss-review-toolkit/ort/blob/f506303e98c8d4d672d025e9c785c9c425d26678/evaluator/src/main/kotlin/OrtResultRule.kt#L40-L65
[2] https://github.com/oss-review-toolkit/ort/blob/f506303e98c8d4d672d025e9c785c9c425d26678/evaluator/src/main/kotlin/PackageRule.kt#L178-L194
[3] https://github.com/oss-review-toolkit/ort/blob/f506303e98c8d4d672d025e9c785c9c425d26678/evaluator/src/main/kotlin/PackageRule.kt#L254-L270
[4] https://github.com/oss-review-toolkit/ort/blob/f506303e98c8d4d672d025e9c785c9c425d26678/examples/evaluator-rules/src/main/resources/example.rules.kts#L240

@pepper-jk Thanks for pointing out the inconsistency, I have created a PR to add an issue function.


APT source whitelist request for ppa:terry.guo/gcc-arm-embedded

This replaces travis-ci/travis-ci#4208.
The original text by @farcaller follows

We require gcc-arm-none-eabi available through ppa:terry.guo/gcc-arm-embedded.

+1. I would migrate to containers if I can hit this source. I am using it to build ARM Cortex-M firmware for an open-source software-defined radio.

+1, previous issue is https://github.com/travis-ci/apt-source-whitelist/issues/34

+1

+1

+1


Clearlydefined curation freeze

Hi,
I've got some issue with ClearlyDefined curation.
I've this configuration in my "ort.yml" :
  packageCurationProviders:
    - name: DefaultFile
    - name: DefaultDir
    - name: File
      config:
        path: '/project/curations.yml'
        mustExist: true
    - name: File
      config:
        path: '/project/ort-config/curations-dir'
        mustExist: false
    - name: OrtConfig
      enabled: true
    - name: ClearlyDefined
      config:
        serverUrl: 'https://api.clearlydefined.io'
        minTotalLicenseScore: 80

Some times (not at each audit), the analyzis phase is blocked and I get this error in the log :
18:18:45  17:18:44.413 [DefaultDispatcher-worker-1] INFO  org.ossreviewtoolkit.analyzer.Analyzer - Finished NPM analysis.
18:18:58  17:18:56.051 [OkHttp https://api.clearlydefined.io/...] ERROR org.ossreviewtoolkit.utils.ort.OkHttpClientHelper - HTTP request to 'https://api.clearlydefined.io/definitions' failed with an exception: StreamResetException: stream was reset: CANCEL
18:18:58  17:18:56.051 [OkHttp https://api.clearlydefined.io/...] ERROR org.ossreviewtoolkit.utils.ort.OkHttpClientHelper - HTTP request to 'https://api.clearlydefined.io/definitions' failed with an exception: StreamResetException: stream was reset: CANCEL
18:18:58  17:18:56.051 [OkHttp https://api.clearlydefined.io/...] ERROR org.ossreviewtoolkit.utils.ort.OkHttpClientHelper - HTTP request to 'https://api.clearlydefined.io/definitions' failed with an exception: StreamResetException: stream was reset: CANCEL
18:18:58  17:18:56.051 [OkHttp https://api.clearlydefined.io/...] ERROR org.ossreviewtoolkit.utils.ort.OkHttpClientHelper - HTTP request to 'https://api.clearlydefined.io/definitions' failed with an exception: StreamResetException: stream was reset: CANCEL
18:18:58  Exception in thread "DefaultDispatcher-worker-9" kotlinx.serialization.json.internal.JsonDecodingException: Unexpected JSON token at offset 9859456: Expected start of the object '{', but had ':' instead at path: $['npm/npmjs/-/eslint-plugin-tsdoc/0.2.2'].files[11].facets
18:18:58  JSON input: .....58654d8b0467d1998c6"},"facets":["tests"]},{"path":"package/l.....
18:18:58  	at kotlinx.serialization.json.internal.JsonExceptionsKt.JsonDecodingException(JsonExceptions.kt:24)
18:18:58  	at kotlinx.serialization.json.internal.JsonExceptionsKt.JsonDecodingException(JsonExceptions.kt:32)
18:18:58  	at kotlinx.serialization.json.internal.AbstractJsonLexer.fail(AbstractJsonLexer.kt:530)
18:18:58  	at kotlinx.serialization.json.internal.AbstractJsonLexer.fail$default(AbstractJsonLexer.kt:528)
18:18:58  	at kotlinx.serialization.json.internal.AbstractJsonLexer.fail$kotlinx_serialization_json(AbstractJsonLexer.kt:224)
18:18:58  	at kotlinx.serialization.json.internal.AbstractJsonLexer.unexpectedToken(AbstractJsonLexer.kt:207)
18:18:58  	at kotlinx.serialization.json.internal.StringJsonLexer.consumeNextToken(StringJsonLexer.kt:74)
18:18:58  	at kotlinx.serialization.json.internal.StreamingJsonDecoder.beginStructure(StreamingJsonDecoder.kt:97)
18:18:58  	at org.ossreviewtoolkit.clients.clearlydefined.Facets$$serializer.deserialize(Definition.kt:154)
18:18:58  	at org.ossreviewtoolkit.clients.clearlydefined.Facets$$serializer.deserialize(Definition.kt:154)

I think it's may be an format issue in the json from clearlydefined, but it will be great if ORT could not fail/freeze in this case and just write some logs and go on the process.

Which revision of ORT are you using? I believe this should have already been fixed in https://github.com/oss-review-toolkit/ort/pull/6337/commits/be1675f35a44d0fc8157a268a7f716501e2871c1 as part of https://github.com/oss-review-toolkit/ort/pull/6337.

I believe this should have already been fixed in be1675f as part of #6337.

Ah, no, it's not. I'll have a look.

Thanks for reporting this @fb33. While investigating, I uncovered another bug that might have cause many (NPM) curations to be missed in the past :worried:

Hi, I'm using an ORT image build on the 16 january around 11h45 am.
Thanks for your reactivity ! :+1:


parameter setting problem

hello! prof.Hu
I'm having some problems when  using your code.
The instructions I use are as follows
sh build.sh
cd build
ninja install

the errors are as follows:
ninja -v
[1/12] /usr/bin/g++ --sysroot=//sysroot  -DH2O_DATA_DIR=\"/home/lml/Desktop/Ranger-master/data/\" -I../src/ext/fusion_cxx -isystem /home/lml/Desktop/mosek/9.1/tools/platform/linux64x86/h -g   -std=gnu++14 -MD -MT src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o -MF src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o.d -o src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o -c ../src/ext/fusion_cxx/BaseModel.cc
FAILED: src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o
/usr/bin/g++ --sysroot=//sysroot  -DH2O_DATA_DIR=\"/home/lml/Desktop/Ranger-master/data/\" -I../src/ext/fusion_cxx -isystem /home/lml/Desktop/mosek/9.1/tools/platform/linux64x86/h -g   -std=gnu++14 -MD -MT src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o -MF src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o.d -o src/ext/fusion_cxx/CMakeFiles/fusion_cxx.dir/BaseModel.cc.o -c ../src/ext/fusion_cxx/BaseModel.cc
In file included from /usr/include/x86_64-linux-gnu/c++/9/bits/c++config.h:528,
                 from /usr/include/c++/9/cstdlib:41,
                 from /usr/include/c++/9/stdlib.h:36,
                 from /home/lml/Desktop/mosek/9.1/tools/platform/linux64x86/h/mosek.h:21,
                 from ../src/ext/fusion_cxx/BaseModel.cc:1:
/usr/include/x86_64-linux-gnu/c++/9/bits/os_defines.h:39:10: fatal error: features.h: No such file or directory
   39 | #include <features.h>
      |          ^~~~~~~~~~~~
compilation terminated.

I tried to copy the feature.h and stdc-predef.h  in /usr/include/ to /usr/include/x86_64-linux-gnu/ according to the online method, but it does't work.
I think this parameters below which are $CONDA_PREFIX and $CONDA_PREFIX/$HOST/sysroot in build.sh need to be modified, but I haven't found relevant information about them.
cmake -GNinja \
      -DCMAKE_PREFIX_PATH=$CONDA_PREFIX \  # 参数一
      -DCMAKE_SYSROOT=**$CONDA_PREFIX/$HOST/sysroot\  # 参数二
      -DCMAKE_BUILD_TYPE=Debug \
      -DMosek_INCLUDE_DIR=/home/lml/Desktop/mosek/9.1/tools/platform/linux64x86/h \
      -DMosek_LIBRARY_RELEASE=/home/lml/Desktop/mosek/9.1/tools/platform/linux64x86/bin/libmosek64.so \
      -DMosek_LIBRARY_DEBUG=/home/lml/Desktop/mosek/9.1/tools/platform/linux64x86/bin/libmosek64.so \
      ../

Do you have a solution?

I prefer to use conda virtual environment to isolate the compiler and library issue. You should create a anaconda environment and install compiler in the conda environment. I think no further dependencies (except for Mosek) is required for the demo.


[PG]: Test and document SSL encrypted connection for DBs

https://www.postgresql.org/docs/9.5/static/libpq-connect.html#LIBPQ-CONNECT-SSLMODE
https://www.postgresql.org/docs/9.5/static/libpq-ssl.html
https://www.postgresql.org/docs/9.5/static/ssl-tcp.html (not needed, since we terminate at the HAProxy)

This issue was moved to kubedb/project#62


NavigationView MenuButton Foreground

I can change the foreground color of the NavigationView Items with a Page.Resources section in the page XAML, but the hamburger button stays the same color. I have tried targetting 'Button' and 'PaneToggleButton' but this doesn't work. How can I  change the foreground of the hamburger button (called 'Menu Button' in the article on Navigation View)?

HI @BillCowell -- which page in our docs were you referring to? This will help me route your question to the correct author. Thanks!

Hi Gina,
The page I was referring to was  ‘Navigation View (Preview Version)’ at
https://docs.microsoft.com/en-us/windows/uwp/design/controls-and-patterns/navigationview
My app is loosely based on the example in this page. I have customised the NavigationView  by adding the following code to MainPage.xaml which contains the NavigationView
<Page.Resources>

</Page.Resources>
This changes all the controls except the hamburger button, which I haven’t found a way of accessing. I’m sure it must be easy, but any help would be appreciated. Many thanks.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Gina P<EMAIL_ADDRESS>Sent: Monday, September 10, 2018 5:13:52 PM
To: MicrosoftDocs/windows-uwp
Cc: BillCowell; Mention
Subject: Re: [MicrosoftDocs/windows-uwp] NavigationView MenuButton Foreground (#969)
HI @BillCowellhttps://github.com/BillCowell -- which page in our docs were you referring to? This will help me route your question to the correct author. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-uwp/issues/969#issuecomment-419970362, or mute the threadhttps://github.com/notifications/unsubscribe-auth/An9hlrHAlmIzZFAe9T0QuWKc9PV3_x29ks5uZo_AgaJpZM4Wf7ka.

Thanks @BillCowell !

No response after 14 days. I would still appreciate an answer. Thank you.

Hi @BillCowell, thanks for your patience.
To change all the navigation items and the menu button, you can override the Foreground brushes as shown here.
If you want to change only the menu button, you can override the PaneToggleButtonStyle as shown in the commented code.
<controls:NavigationView x:Name="NavView">
    <controls:NavigationView.Resources>
        <SolidColorBrush x:Key="NavigationViewItemForeground" Color="White"/>
        <SolidColorBrush x:Key="NavigationViewItemForegroundPointerOver" Color="Green"/>
        <SolidColorBrush x:Key="NavigationViewItemForegroundPressed" Color="LightGreen"/>
        <SolidColorBrush x:Key="NavigationViewItemForegroundSelected" Color="Red"/>
        <SolidColorBrush x:Key="NavigationViewItemForegroundSelectedPointerOver" Color="Blue"/>
        <SolidColorBrush x:Key="NavigationViewItemForegroundSelectedPressed" Color="Pink"/>
    </controls:NavigationView.Resources>

    <!--<controls:NavigationView.PaneToggleButtonStyle>
        <Style TargetType="Button" BasedOn="{StaticResource PaneToggleButtonStyle}">
            <Setter Property="Foreground" Value="White"/>
        </Style>
    </controls:NavigationView.PaneToggleButtonStyle>-->
</controls:NavigationView>

That works. Many thanks.

Tried this again and the only colors that seem to be overwritten are for the footer ViewItem. Any ideas why?


CODERUB: Fix Folder Hierarchy Unit Tests

Closes #48

Change the name of this to CODE RUB

There no changes here. closing this PR.


Get processed asset by simple url

Hi Jan!
I need to get whole processed asset content by url.
But url must be simler than http://my-domain.com/asset/18d9939d83/foo.js
like http://my-domain.com/assets/foo.js (skip checksum)
Is there an any documented or known way to solve the problem?
Thanks.

Oh, now solved by route cb:
 $app->routes->route('/assets/*name')->via(qw(HEAD GET))
    ->name('assetpack by name')->to(cb => \&_serve_by_name);

sub _serve_by_name {
  my $c        = shift;
  my $helper   = $c->stash('assetpack.helper');
  my $self     = $c->$helper;
  my $topic = $c->stash('name');

   if (my $assets = $self->{by_topic}{$topic}) {
    $c->stash('checksum' => $assets->[0]->checksum);
    return &Mojolicious::Plugin::AssetPack::_serve($c);
  }

  $c->render(text => "// No such asset '$topic'\n", status => 404);
}

That is really not the way to fix it. You're way too deep into the internals of AssetPack.
First I need to inform you that doing what you want will cause caching issues for browsers.
Second, here is how you can do it:
$app->routes->route('/assets/*name')
  ->via(qw(HEAD GET))
  ->name('assetpack by name')
  ->to(cb => sub {
    my $c      = shift;
    my $topic  = $c->stash('name');
    my $assets = $c->asset->processed($name);

    return $c->render(text => $assets->map('content')->join) if $assets;
    return $c->render(text => "// No such asset '$topic'\n", status => 404);
  });

Your application should already know the helper name. assetpack.helper is a private variable, which may very well be renamed in the future
You should also never poke around in the hash variables in AssetPack, such as $self->{by_topic}{$topic}.
In https://github.com/jhthorsen/mojolicious-plugin-assetpack/blob/master/t/css.t#L51 I use the processed() method to inline the javascript inside the markup.
See also https://metacpan.org/pod/Mojolicious::Plugin::AssetPack#processed

Ok, thanks.
I wrote pipe combine content of assets to cache file here
# in process pipe
# instead of Mojolicious::Plugin::AssetPack::Asset->new(...)->...->content($joined_content)
$assetpack->store->save(\$joined_content, ...);

# and then serve content by topic
my $asset = $assetpack->store->load(...);
$assetpack->store->serve_asset($c, $asset);

I would like that asset is Mojo::Asset::File instead of Mojo::Asset::Memory
--
Regards

Your pipe also use internals in AssetPack...
Why do you need to change this?
https://github.com/mche/Mojolicious-Plugin-AssetPack-Che/blob/master/lib/Mojolicious/Plugin/AssetPack/Pipe/CombineFile.pm#L9
https://github.com/mche/Mojolicious-Plugin-AssetPack-Che/blob/master/lib/Mojolicious/Plugin/AssetPack/Pipe/CombineFile.pm#L10 should just be:
$self->app->routes(...)

Why do you need to change this?
https://github.com/mche/Mojolicious-Plugin-AssetPack-Che/blob/master/lib/Mojolicious/Plugin/AssetPack/Pipe/CombineFile.pm#L9

I need combine html files but you remove mapping:
https://github.com/jhthorsen/mojolicious-plugin-assetpack/blob/master/lib/Mojolicious/Plugin/AssetPack/Store.pm#L22

https://github.com/mche/Mojolicious-Plugin-AssetPack-Che/blob/master/lib/Mojolicious/Plugin/AssetPack/Pipe/CombineFile.pm#L10 should just be:
$self->app->routes(...)

Can't locate object method "app" via package "Mojolicious::Plugin::AssetPack"

I wonder why I delete those type mappings... I'll take a PR for getting them back.
You're combining and serving HTML..? How? Why..?
Can't locate object method "app" via package "Mojolicious::Plugin::AssetPack": You're doing something wrong. The method is there: https://github.com/jhthorsen/mojolicious-plugin-assetpack/blob/master/lib/Mojolicious/Plugin/AssetPack/Pipe.pm#L16 I'm even using it in existing pipes, like here: https://github.com/jhthorsen/mojolicious-plugin-assetpack/blob/master/lib/Mojolicious/Plugin/AssetPack/Pipe/Riotjs.pm#L29

Why..?

There is project with javascript framework with so called "component" style. Each of components have self js controller and one or more small html templates. Now my AssetPack pipe joins lot of htmls and on client side asset split to  separate templates.

$self->app->routes(...)

Works, sorry


Bazel build failed to detect clang compiler

Environment

gcc: 4.9.2
clang: 8.0.0
bazel: 3.3.1
abseil commit id: 38db52adb2eabc0969195b33b30763e0a1285ef9

Expected
The target leak_check_api_enabled_for_testing defined as following:
cc_library(
    name = "leak_check_api_enabled_for_testing",
    testonly = 1,
    srcs = ["leak_check.cc"],
    hdrs = ["leak_check.h"],
    copts = select({
        "//absl:llvm_compiler": ["-DLEAK_SANITIZER"],
        "//conditions:default": [],
    }),
    linkopts = ABSL_DEFAULT_LINKOPTS,
    visibility = ["//visibility:private"],
    deps = [
        "//absl/base:config",
    ],
)

Building it, I expected -DLEAK_SANITIZER in clang command.
bazel build --action_env="a=1" -s //absl/debugging:leak_check_api_enabled_for_testing

Actual
bazel build --action_env="a=2" -s //absl/debugging:leak_check_api_enabled_for_testing
INFO: Build option --action_env has changed, discarding analysis cache.
INFO: Analyzed target //absl/debugging:leak_check_api_enabled_for_testing (3 packages loaded, 59 targets configured).
INFO: Found 1 target...

INFO: Build completed successfully, 2 total actions

Is llvm the default compiler for the build? Does building with "--compiler=llvm" do anything different?
My best guess is whatever environment you are running into doesn't default to the llvm compiler, which is why it wouldn't choose the select() path that adds that define.

Is llvm the default compiler for the build? Does building with "--compiler=llvm" do anything different?
My best guess is whatever environment you are running into doesn't default to the llvm compiler, which is why it wouldn't choose the select() path that adds that define.

The default compiler in my environment (aka. /usr/bin/cc) is not clang. However, I already exposed CC=clang CXX=clang++ to the environment variables.
Here's the logs building with --compiler=clang (toolchains renamed from llvm to clang in higher version of bazel):
bazel build --compiler=clang --action_env="a=2" -s //absl/debugging:leak_check_api_enabled_for_testing

INFO: Build option --compiler has changed, discarding analysis cache.
INFO: Analyzed target //absl/debugging:leak_check_api_enabled_for_testing (0 packages loaded, 59 targets configured).
INFO: Found 1 target...

INFO: Build completed successfully, 2 total actions

Abseil relies on the compiler string being llvm. At one point Bazel simply set the compiler string to compiler, so for testing we set an environment variable BAZEL_COMPILER=llvm. From my experimentation, it looks like Bazel is now setting this string to clang when clang is used, and it is setting it to compiler when gcc is used. We may have to adjust this.
For now, try working around this using BAZEL_COMPILER=llvm bazel build ..., although this won't work if your project relies on the compiler string being clang somwhere.

Abseil relies on the compiler string being llvm. At one point Bazel simply set the compiler string to compiler, so for testing we set an environment variable BAZEL_COMPILER=llvm. From my experimentation, it looks like Bazel is now setting this string to clang when clang is used, and it is setting it to compiler when gcc is used. We may have to adjust this.
For now, try working around this using BAZEL_COMPILER=llvm bazel build ..., although this won't work if your project relies on the compiler string being clang somwhere.

@derekmauro Thanks for your explanation. Unfortunately, the workaround didn't work on Bazel 3.3.1.
$ env BAZEL_COMPILER=llvm bazel build --compiler=clang --action_env="a=1" -s //absl/debugging:leak_check_api_enabled_for_testing
Starting local Bazel server and connecting to it...
ERROR: /data00/home/zhangshuai.ds/.cache/bazel/_bazel_zhangshuai.ds/28cefa5c67f76607bf7aac94fe5b35b3/external/local_config_cc/BUILD:47:19: in cc_toolchain_suite rule @local_config_cc//:toolchain: cc_toolchain_suite '@local_config_cc//:toolchain' does not contain a toolchain for cpu 'k8' and compiler 'clang'.
ERROR: While resolving configuration keys for //absl/debugging:leak_check_api_enabled_for_testing: Analysis of target '@local_config_cc//:toolchain' failed
ERROR: Analysis of target '//absl/debugging:leak_check_api_enabled_for_testing' failed; build aborted: Analysis of target '@local_config_cc//:toolchain' failed
INFO: Elapsed time: 3.685s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (14 packages loaded, 42 targets configured)

$ bazel build --compiler=llvm --action_env="a=1" -s //absl/debugging:leak_check_api_enabled_for_testing
INFO: Build option --compiler has changed, discarding analysis cache.
ERROR: /data00/home/zhangshuai.ds/.cache/bazel/_bazel_zhangshuai.ds/28cefa5c67f76607bf7aac94fe5b35b3/external/local_config_cc/BUILD:47:19: in cc_toolchain_suite rule @local_config_cc//:toolchain: cc_toolchain_suite '@local_config_cc//:toolchain' does not contain a toolchain for cpu 'k8' and compiler 'llvm'.
ERROR: While resolving configuration keys for //absl/debugging:leak_check_api_enabled_for_testing: Analysis of target '@local_config_cc//:toolchain' failed
ERROR: Analysis of target '//absl/debugging:leak_check_api_enabled_for_testing' failed; build aborted: Analysis of target '@local_config_cc//:toolchain' failed
INFO: Elapsed time: 1.271s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 42 targets configured)

Abseil relies on the compiler string being llvm. At one point Bazel simply set the compiler string to compiler, so for testing we set an environment variable BAZEL_COMPILER=llvm. From my experimentation, it looks like Bazel is now setting this string to clang when clang is used, and it is setting it to compiler when gcc is used. We may have to adjust this.
For now, try working around this using BAZEL_COMPILER=llvm bazel build ..., although this won't work if your project relies on the compiler string being clang somwhere.

I got the point. I can patch //absl/compiler_config_setting.bzl in my environment to workaround it.
diff --git a/absl/compiler_config_setting.bzl b/absl/compiler_config_setting.bzl
index 6696229..c03301c 100644
--- a/absl/compiler_config_setting.bzl
+++ b/absl/compiler_config_setting.bzl
@@ -26,7 +26,7 @@ def create_llvm_config(name, visibility):
         native.config_setting(
             name = name,
             flag_values = {
-                "@bazel_tools//tools/cpp:compiler": "llvm",
+                "@bazel_tools//tools/cpp:compiler": "clang",
             },
             visibility = visibility,
         )

Could we detect the Bazel version and make another else-if branch for this issue?


Add separate function for Watterson's theta

sgkit-allel has functionality to calculate Watterson's theta but in sgkit it is calculated implicitly in Tajima's D function. For some applications direct access to Watterson's theta would be of practical use.

I could draft a PR since I think this is a pretty straightforward code refactoring operation.


FloorFliter: silence exception when floorManager is not set

The scope of this issue is to make sure that an exception is not thrown and the app does not crash if the GeoModel used to create it doesn't have the floorManager. The failure should eventually be handled by a callback, but that will be handled in a different issue.
Changes

Replace error throwing with return.

@ruiqima we will likely merge our feature branch into v.next soon. Can this PR target v.next instead?

@ruiqima the change looks good, but as @mikewilburn said you will probably have to create another PR that is based on v.next to have a clean commit history.


Update downloading-configuration.md

On the page https://dynatrace-oss.github.io/dynatrace-monitoring-as-code/configuration/configTypes_tokenPermissions the configuration for the Endpoint /api/config/v1/alertingProfiles is "alerting-profile" and not "alerting-profiles"

this improvement was incorporated into #673
thanks for your contribution @kverreth! :rocket:


docs: Add Windows install instructions.

Signed-off-by: John Harris<EMAIL_ADDRESS>

 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.John Harris seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Can not open uploaded file

Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Describe the bug
I ran ./weed master and ./weed volume -dir="./tmp" -max=5 -mserver="localhost:9333" -port=8080 on my machine followed by
curl -X POST http://localhost:9333/dir/assign
Then I put a file by
curl -X PUT -F<EMAIL_ADDRESS>http://<IP_ADDRESS>:8080/5,01b3767907
However when I tried
wget  http://localhost:8080/5,01b3767907 -o test.png
When I tried to open in, I got
It may be damaged or use a file format that Preview doesn’t recognize.
System Setup
macOS 10.13.6 with latest binary
Expected behavior
I expect to see the picture a put
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

use HTTP POST, not HTTP PUT, when uploading files.
 curl -F<EMAIL_ADDRESS>http://<IP_ADDRESS>:8080/5,01b3767907


Settings editor doesn't respect ctrl+up and ctrl+down

Testing #188536
Not sure if the settings editor is intended to support this, but it seems very similar to the other places that do support it.

@alex I'll try to fix that, if he should support it

@alexr00 I'll try to fix that, if it should be supported


List down the availbale local roles to be selected in role mapping of SP creation UI

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


MB-16000: Ensure roles/permissions returns empty list for swagger

Jira ticket
Summary
The current response for /internal/logged_in can return null for both permissions and roles, but the swagger definitions says they should not be null.
Return the empty list if the user has no roles or permissions
Setup to Run the Code

Instructions for starting storybook
Instructions for starting the MilMove application
Instructions for running tests

How to test
make server_test

Messages

:book:
:link: MB-16000

  Generated by :no_entry_sign: dangerJS against d84c768918a8bb24f8f411db11891349a897b6fb


Fixed NavView in ContentDialog crash

Description
When NavView is shown in a ContentDialog, there is a scenario where the SplitView tries to add children to the popup root while it is being measured (which causes a crash since NavView itself is in the popup root). Due to the fact that this SplitView API call (updating the DisplayMode property) modifies elements in the tree outside of itself, we should defer that call, whenever it comes from OnApplyTemplate, to be executed in the OnLoaded callback.
Motivation and Context
Fixes #2713
How Has This Been Tested?
Added interaction test

/azp run

@ojhad you have some visual verification failures

/azp run

more visual verification issues, as @Felix-Dev noted, i think the pipeline is broken. hopefully @kmahone can take a look when he gets back.

more visual verification issues, as @Felix-Dev noted, i think the pipeline is broken. hopefully @kmahone can take a look when he gets back.

There was an issue in the processhelixfiles.ps1 script.


Refactor region error handler

Currently, the region error is handled in a long long function onRegionError and the retry policies of different error types are mixed. It makes the code hard to maintain and read.
This PR refactors the region error and makes handler for each type of region error.

@you06 @crazycs520
Is this to be continued/reused or closed?

I've tried to make some abstractions here, which is similar to this PR.


[WIP] Big refactor of TABTestKit

Still a WIP and need to verify a lot of stuff (which I'll do by beefing up the example automation/app).
The drive behind this is to:

Make it harder for people to make mistakes
Make it easier for new people to pick up
Make devs write as little code as possible

This refactor has lost a few of the helper functions, but we can always add those back as functions on Element or some other appropriate protocol.
There are a lot of protocol extensions which aim to make it so people can just make their custom elements conform to the protocols and get most behaviour for free.

@zacoid55 we can sit down and go through the code when I've got it tidied up

All checks have passed, merrrrgggginggggg


add instruction to upgrade to specific version

/assign @sarahmaddox

This change is

Thanks!
/lgtm
/approve


offline node doesn't judge as offline after new elected root leader

After the root leader node is shut down, another node can be elected as the new root leader.
It will rebuild memory liveness after a heartbeat tick, but the old root node cannot be accessible but doesn't set entry in memory map, so it will be judged as online node in liveness and we can observe allocator still try transfer replica into offline node

judged as online node in liveness and we can observe allocator still try transfer replica into offline node

Yes, all memory states should be dropped once the leadership is transfered.


Deserializing/converting Value to a specific type

I have a use case where I don't know to which type it should deserialize while reading the (yaml) file.
The solution I thought of was:

First deserialize it as a Value
When I know the type: convert the Value to a struct that derives Deserialize

Is this plausible? If so, it would be useful to have it in the docs.

My bad. I can use the from_value method. https://docs.rs/serde_yaml/0.8.13/serde_yaml/fn.from_value.html