add OMS

need more details on OMS.  Max # workspaces, etc.

Hi @nluedeman, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@nluedeman : Thanks for your contribution to the Azure documentation! The author, @rothja, has been notified to review your proposed change.

@nluedeman Thanks for the suggestion. I can't merge this change in as-is, because it does not contain the limits obviously. But I can reach out to the owners of OMS and ask that they add information to this page. I'll try to do that now.

@nluedeman I can take this.  I don't think there is a maximum number of workspaces, but I'll pass this on to our Log Analytics writer.  What other details are you looking for?

I'm out on vacation. Discuss with Adrian Doyle and Brian Cutler, I submitted this based on yesterday's case bath.
Nicole<EMAIL_ADDRESS>Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone
-------- Original message --------
From: Brian Wren<EMAIL_ADDRESS>Date: 2/8/17  8:35 AM  (GMT-05:00)
To: Microsoft/azure-docs<EMAIL_ADDRESS>Cc: Nicole Welch<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/azure-docs] add OMS (#661)
@nluedeman I can take this.  I don't think there is a maximum number of workspaces, but I'll pass this on to our Log Analytics writer.  What other details are you looking for?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/Microsoft/azure-docs","title":"Microsoft/azure-docs","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/Microsoft/azure-docs"}},"updates":{"snippets":[{"icon":"PERSON","message":"@bwren in #661: @nluedeman I can take this.  I don't think there is a maximum number of workspaces, but I'll pass this on to our Log Analytics writer.  What other details are you looking for?"}],"action":{"name":"View Pull Request","url":"https://github.com/Microsoft/azure-docs/pull/661#issuecomment-278330115"}}}

@bwren Have you had a chance to look into this? I can leave this PR open to make the changes, or we can close it while you're investigating and you can open a new one with the changes.

@bwren @nluedeman Let me know how you want to proceed with this change request. I suggest we close this PR and submit the changes (once you know them) through a fresh PR. Thanks!

If someone is reviewing this PR with permissions, I suggest we close this. The work request has been sent to the right people and there is not a specific change here to approve or reject.

@nluedeman @rothja I'm closing this pull request. If you want to close a pull request yourself, add the appropriate comment, and automation will close the pull request. Thanks.


What you mean broken types

I think you are already fix it.
broken.md under generate crate

Included a version of the schema in the source tree now, albeit xz compressed because the original file is 3.2MB.
CI still creates an original from proxmox-ve sources, so it will detect differences that we do not account for.
BROKEN.md should cover the missing bits :) I have finally signed the CLA and plan on addressing the broken things found so far.


fix error status should not be overwritten in TabletStream

What problem does this PR solve?
Use AtomicStatus for TabletStream::_status to avoid concurrent issues.
Use AtomicStatus::update to avoid error status being overwritten by Status::OK()
Release note
None
Check List (For Author)

Test

[x] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[x] No.
[ ] Yes.

Does this need documentation?

[x] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall


docs(notes.txt): Add NOTES.txt to Chart spec, and describe chart documentation files

See #993
/cc @vaikas-google @technosophos

This change is

From my point of view, this looks good to go. Any thoughts on this, @vaikas-google ?

LGTM.


fix bug preventing from loading config.yaml

For automated jenkins job i18n was not able to load the config file
13:28:37 i18n_tool extract -vv 13:28:37 /edx/var/jenkins/jobs/translations/jobs/edx-platform-push_translations/workspace/ecommerce-scripts/edx-platform/conf/locale/config.yaml 13:28:37 Traceback (most recent call last): 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/bin/i18n_tool", line 11, in <module> 13:28:37     sys.exit(main()) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/i18n/main.py", line 60, in main 13:28:37     return module.main() 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/i18n/__init__.py", line 50, in __call__ 13:28:37     self.configuration = config.Configuration(filename=args.config, root_dir=root_dir) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/i18n/config.py", line 35, in __init__ 13:28:37     self._config = self.read_config(self._filename) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/i18n/config.py", line 67, in read_config 13:28:37     return yaml.load(stream) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/yaml/__init__.py", line 70, in load 13:28:37     loader = Loader(stream) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/yaml/loader.py", line 34, in __init__ 13:28:37     Reader.__init__(self, stream) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/yaml/reader.py", line 85, in __init__ 13:28:37     self.determine_encoding() 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/yaml/reader.py", line 124, in determine_encoding 13:28:37     self.update_raw() 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/site-packages/yaml/reader.py", line 178, in update_raw 13:28:37     data = self.stream.read(size) 13:28:37   File "/edx/var/jenkins/shiningpanda/jobs/21b7fcb9/virtualenvs/4418f485/lib/python3.5/encodings/ascii.py", line 26, in decode 13:28:37     return codecs.ascii_decode(input, self.errors)[0] 13:28:37 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1914: ordinal not in range(128)

Coverage remained the same at 72.448% when pulling d90dd8e0b0070e5cc800a001dee6717bb476c1ff on ensure-config-file-encoding into f4557393ccb872fe70da19ea97cab6e25927f2eb on master.

The change seems reasonable enough, but I also wonder why this is happening.

Coverage increased (+0.02%) to 72.473% when pulling 654af6b9a0c562ae6881bdeb532d9780726d4048 on ensure-config-file-encoding into f4557393ccb872fe70da19ea97cab6e25927f2eb on master.

@Ayub-Khan Any thoughts on our questions?

@nedbat  @amangano-edx  i18n-tools run in paver along with a lot of other dependencies installed. or any configuration setting for docker devstck may be involved in making sure that encoding is utf-8. Also looking for that exact thing might take a lot of time and we still end up updating our i18n-tools. Also not using using any encoding scheme makes this code system or python based. if system defines any other coding scheme it will fail. More on if some other org wants to use it and their system define encoding scheme is different this will fail. its a batter choice to specify the encoding.

@nedbat  @amangano-edx  i18n-tools run in paver along with a lot of other dependencies installed. or any configuration setting for docker devstck may be involved in making sure that encoding is utf-8. Also looking for that exact thing might take a lot of time and we still end up updating our i18n-tools. Also not using using any encoding scheme makes this code system or python based. if system defines any other coding scheme it will fail. More on if some other org wants to use it and their system define encoding scheme is different this will fail. its a batter choice to specify the encoding.

I agree this is a better change.  I was concerned about why it was failing for you and not for us: it points to some difference in our environements.

@nedbat  It is also working for me too in docker-devstack but it is not working in jenkins envirement. have you tried it locally with jenkins with my other pull requests code regarding edx-platform jenkins job. ?

Actually, I'm not doing translation work these days, so I should let @amangano-edx finish the review.

Coverage increased (+0.02%) to 72.473% when pulling 107bcb11a421a5443749504b1a676bf5875afc6c on ensure-config-file-encoding into f4557393ccb872fe70da19ea97cab6e25927f2eb on master.

Coverage increased (+0.02%) to 72.473% when pulling 85fdf82955d9d834113a3c26be9df525beb0d504 on ensure-config-file-encoding into f4557393ccb872fe70da19ea97cab6e25927f2eb on master.


"Details" action for every search result

After clicking "More" for particular search result a "Details" link should be available. When "Details" is clicked new tab/window should be open with full source code and each line author info.

Done [Preview] in 912bc2c72feef579a6ca77dd815e4eb1d1332063


add debian rules for libvlc

Follow up to #10959
Package pages:

https://packages.debian.org/jessie/libvlc-dev
https://packages.debian.org/jessie/vlc-nox
https://packages.debian.org/jessie/libvlc5

+1 (thanks)


Module crash on song skip

So I was able to crash the module by skipping a song quite a few times now by mistake but I can't repo it anymore.

You have somehow generated an empty 'this is playing' response from VLC. I've tried several times (including a 20x per second skip button repeat). I can't reproduce this but I did add a check to catch and ignore the error instead of crashing.

Cheers, I was playing by just selecting a load of files and hitting play, I had it happen quite a few times but I can’t repo it now which is annoying.
From: John Knight Jr
Sent: 18 December 2020 02:16
To: bitfocus/companion-module-videolan-vlc
Cc: Peter; Author
Subject: Re: [bitfocus/companion-module-videolan-vlc] Module crash on songskip (#21)
You have somehow generated an empty 'this is playing' response from VLC. I've tried several times (including a 20x per second skip button repeat). I can't reproduce this but I did add a check to catch and ignore the error instead of crashing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

On further testing this is caused by just playing loads of individual files back to back

You can overwhelm VLC with commands and it sometimes gives empty responses. There is an update on the way that will ignore those without crashing. I've been tinkering with a 400 song playlist and VLC may crash, but companion stays running.

Fixed as part of #22


Enhancing ComputeUsageUnit, DiskSkuTypes, EncryptionStatus extensible enums

to follow how Region works

Can one of the admins verify this patch?


Don't delete in-memory raster (fixes #160)

Whoops, we were doing the same .. -> https://github.com/geopandas/contextily/pull/163

Thanks @jorisvandenbossche! Closing in favor of your PR.

Hmm, but apparently mine is not fixing it completely .. (one of the two travis builds is still crashing)

I see. Any objections to my PR?

With an additional fix it is now working (needed to use the VRT with a context manager as well). I think I prefer my PR because I don't think it is needed to keep the memory file object alive after the warping.
Thanks for the contribution, and sorry again for the overlap in work!


Avatars in Followers/Following Tabs Don't Do Anything

Clicking the avatar should go to a user's profile.
Follow should follow them.

I fixed the avatar issues on one of my branches, should be integrated soon.
@jjeffryes is going to have to get the follow/unfollow buttons working there since that is over my head.

Or @hoffmabc you could take a stab at it too.  If you're already following the user, it should display unfollow. I believe @drwasho had a bug open for this too.

Fixed.


Security Vulnerability: Unauthenticated Local File Inclusion

Issue
The extension exposes the Web UI instance to an unauthenticated Local File Inclusion vulnerability.
Example request:
GET /infinite_image_browsing/file?path=/proc/self/environ&t=2023-05-08%2017%3A55%3A10 HTTP/1.1
Host: redacted

An attacker could read the /etc/passwd file for example, /etc/hosts, /etc/resolv.conf to gain more information about the system.
An attacker could also read the /proc/self/environ variable to read the command line arguments used to execute Web UI and extract the username and password to login to the server.
Fix:

Ensure that the user is authenticated before allowing the API to be called.
Restrict the file paths and types that the browsing can access.

Next:
If you can replicate, please let me know. Trying to get a CVE assigned, thanks.
If you don't plan to fix please also let me know.

Have you seen this document? https://github.com/zanllp/sd-webui-infinite-image-browsing/blob/main/.env.example
.
Or, have you tried making sd-webui accessible to the public （--share）, and were you able to access sensitive files afterwards?

I found the issue when performing a security test previously. I do not have a SD Web UI set up unfortunately with the plugin correctly configured with the secret key to be able to replicate now.
Do you have an instance you can message me with so that I can replicate and test for you?
In general it did not appear that anything would stop the access to sensitive files because the Web UI I was testing was already password protected using --gradio-auth.

The design philosophy of IIB is to grant all permissions locally for easy user operation, and narrow down the allowed permissions by default when allowing public access. It switches based on different environments.

Do you have an instance you can message me with so that I can replicate and test for you?

Unfortunately, I don't use products like Colab, so I can't easily provide you with a test instance. However, if you have sd-webui installed, you just need to input any one of the following parameters, and IIB will automatically enable protection: --share, --ngork, --listen, --server-name.
https://github.com/zanllp/sd-webui-infinite-image-browsing/blob/38a04a4b93e057d887371c6ea6ca46c513d7f37e/scripts/iib/tool.py#L244-L262

In general it did not appear that anything would stop the access to sensitive files because the Web UI I was testing was already password protected using --gradio-auth. The IIB key, I do not recall having tested it specifically, but it's worth verifying to see if it would bypass the control.

If you pass in "gradio-auth" in the sd-webui CLI, IIB will also require you to enter a password.
https://github.com/zanllp/sd-webui-infinite-image-browsing/blob/38a04a4b93e057d887371c6ea6ca46c513d7f37e/scripts/iib/api.py#L79-L82
https://github.com/zanllp/sd-webui-infinite-image-browsing/blob/38a04a4b93e057d887371c6ea6ca46c513d7f37e/scripts/iib/tool.py#L235-L243

When was the secret key added? I tested this plugin around 3 weeks ago and it did not protect the app. Thanks!

The secret key feature was added early on.
However, the requirement to add a secret key after configuring gradio-auth was enforced in pull request #368. Perhaps you just happened to miss that particular pull request.


Support ENS (.eth) + IPFS resolution

When an .eth domain is entered into the url, it should resolve it's IPFS hash.
Resources:
ENS:
https://docs.ens.domains/
Checking the domain's resolver:
https://docs.ens.domains/contract-api-reference/ens#get-resolver
Resolver Content Hash support (EIP 1577):
https://eips.ethereum.org/EIPS/eip-1577

@sudoryan it mean currently the browser can't support ens resolvering?

where is Unstoppable API for blockchain domain name lookups


Revert "Include every IP address into a cert's SAN field"

Reverts voxpupuli/puppet-k8s#32
To copy what I said there;
It's causing issues as it's changing the SAN list - and therefore also triggering a recreation of the serving certs - every time a container starts or stops on the Kubernetes master nodes.
Additionally, it's also including link-local bindings as well as IPVS entries from kube-proxy into the certificates, which causes the SAN list to grow in size far too quickly. A simple test cluster with no active load is already up to 50 SANs, while our production cluster would have SAN lists with almost a thousand entries for each master.

I've also added an $addn_names parameter to k8s::server::etcd, so that additional IP addresses can be specified for the non-default address use-case. It's slightly less optimal than automatically generating the list, but at least it won't cause issues for the common use-case.


[YUNIKORN-1248] Support aarch64 and arm64 for ARM processors

What is this PR for?
The M1 MacBook does not identify as aarch64 but as arm64. Both aarch64
and arm64 are the same and are supported as such.
What type of PR is it?

[X] - Bug Fix

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-1248
How should this be tested?
Build locally on a M1 mac

LGTM.
It works on my mac containing M1 processor.


docs: separate streetlight examples for Kafka and MQTT

Main motivation of this was to provide a place to demonstrate
the new Kafka-specific security schemes introduced in
AsyncAPI 2.1.0. It was also a chance to remove the Kafka
bindings from the otherwise-MQTT sample.
The need for this was discussed in
https://github.com/asyncapi/spec/pull/502
Contributes to: #466
Signed-off-by: Dale Lane<EMAIL_ADDRESS>

Awesome stuff @dalelane
Thanks 🙏🏼
@fmvilas wanna have a look? I think we need to solve https://github.com/asyncapi/spec/issues/540 now or after release, it will be hard to review examples long term if we after all create new instances of those + it is kind of inconsistent, that spec is only latest but examples are there for all versions

@derberg indeed it's weird to have examples for all versions but only the latest version of the spec. I'd get rid of the examples of older versions.

@fmvilas I think we can merge and I'll create a followup cleanup


Deal better with the example application

Right now the example app is included on the package itself. I'm considering moving it to another repository.
Do you have a suggestion to keep it here but making a better separation? It is too coupled with the library.

Thanks @victorolinasc for the suggestion


validation_prompts are sampling twice ?

Hi there.
I wonder why there are 10 images in the sampling done with the validation_prompt prompts during the training (at X steps), when I only set 5 prompts for x step sampling.

It seems that the top pictures are (slowly) getting the concepts and following the prompts: for example, the first validation prompt is "a black and white photograph of..." and the second is "a red shirt.". (and the inference tests I do on the fully trained from scratch shows that it goes the right direction.)
But what are the five images in the second row ? The second one seem to follow the sampling prompt "a red shirt", but I don't understand the similarities of images 6,8,9 and 10 (bottom line).
Regards.

That's because 5 images are generated with a fixed seed, and the other 5 with random seed

Exactly correct answer.

Thank you @Muinez & @lawrence-cj .


use mac or osx instead of darwin as a bundle name in the release page

appreciate your great work!
it's hard to grasp immediately which one is the DL file for Mac OSX for newbies like me with your way of naming the files.  you should use mac or osx as a prefix. keep on your great work.

I agree with you. 👍
I will change the bundle name and add homebrew to the installation method.


How can I register custom language?

Hello,
Thanks for this great module. I have one to get help you. I want to register custom language, but how can i do this?
Hope to hear from you soon.
Thanks,

// Register a new language
monaco.languages.register({ id: 'mySpecialLanguage' });

what is the equivalent of this then ?

Is it possible to create a language that extends from another one? For example, I want to register MJML language and use the same syntax highlighting of HTML but change the completion.

Of course, for this you need to get the configurations of the existing language and apply to your.

AMD js example
(() => {
  const CUSTOM_LANG_ID = 'special_language';
  monaco.languages.register({ id: CUSTOM_LANG_ID });
  const js = await new Promise((resolve, reject) => {
    globalThis.require(['vs/basic-languages/javascript/javascript'], resolve, reject);
  });
  monaco.languages.setMonarchTokensProvider(CUSTOM_LANG_ID, js.language);
  monaco.languages.setLanguageConfiguration(CUSTOM_LANG_ID, js.conf);
})


Name Popularity Index

Assuming that multiple versions of country names become available, it would be nice to include a popularity index, e.g. http://www.google.com/trends/explore#q="Lithuania"%2C "Republic of Lithuania"&cmpt=q&tz=.
Knowing which name is more popular, together with language property, would be useful when determining which name to choose to display in which language. This index could be updated once a week or so using an automated script.
I am happy to contribute a library that would abstract querying of the data (assuming such does not exist already).

I'm starting to think that this is probably something that is outside the scope of the country-data module but that is obviously closely linked to it and would be very useful.
Having a module that could could take a country code like SV and then return Sweden as the popular name in English, or "Sverige" in Swedish would be great.
It would then also be able to do the reverse - for example map "Vietnam" to VN, despite the official name being "Viet Nam" (which I'm guessing is very rarely used).
If you were to create such a module I'd be very happy to point to it from the docs of country-data :)

I will look into how hard would it be to collect the data.

On Feb 17, 2015, at 12:49, Edmund von der Burg<EMAIL_ADDRESS>wrote:
I'm starting to think that this is probably something that is outside the scope of the country-data module but that is obviously closely linked to it and would be very useful.
Having a module that could could take a country code like SV and then return Sweden as the popular name in English, or "Sverige" in Swedish would be great.
It would then also be able to do the reverse - for example map "Vietnam" to VN, despite the official name being "Viet Nam" (which I'm guessing is very rarely used).
If you were to create such a module I'd be very happy to point to it from the docs of country-data :)
—
Reply to this email directly or view it on GitHub.


Add Alerta Output

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

This PR allows post events to Alerta (https://alerta.io/)
Special notes for your reviewer:
Alerta API reference: https://docs.alerta.io/api/reference.html#alerts

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

209c04d add alerta payload struct
78f17ad create alerta payload
9858190 passing unit tests

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.

Welcome @LivingInSyn! It looks like this is your first PR to falcosecurity/falcosidekick 🎉

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LivingInSyn
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LivingInSyn
To complete the pull request process, please ask for approval from issif after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Issif fixed alertmanager-> alerta issues, that's what I get for not waiting until the next morning to submit the PR, sorry about that

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

326b871 Update handlers.go

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.

I'm closing this PR due to discovered issues in Alerta and inconsistent rules in their API between versions and in their docs. I no longer think Alerta is stable enough to not break


Export of Python function to a .NET assembly file

Hy! My scenario is to use a rather simple Python function from .NET.
As far as I understood, this is what Pyjion does anyway: produces IL and saves a .NET assembly. Is it possible to obtain this assembly / clean way of calling it from C# / .NET? Does Pyjion provide an explicit API of exporting a Python function to a .NET assembly?
Thanks!

Should we just be able to dump m_il byte code to an assembly?
or maybe first create MethodInfo and then create an assembly just with one method?
a question: will pyjion jit methods called from the currently-jitted method? (including the python standard library)

I spent some time looking at the reverse. There are lots of issues to overcome.
Firstly, and most importantly, Pyjion only uses RyuJIT. We never initialise the managed .NET runtime. That in itself is a huge undertaking.
Secondly the object models are not compatible. Pyjion uses low level types for integers, floats, bool. Beyond that it doesn't implement any managed types/classes in CIL because they aren't compatible with Pythons objects, nor would there be any advantage to doing so.
Third, as you pointed out you need export more information into an assembly that can be imported and run from .NET. I started investigating it but decided it was too much work.

I see, understand it better now. Thank you!


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade" workflow

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @zxkane on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
8
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/24/2024, 00:57:48 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication


start_date not respected?

I've created  a DAG as shown:
dag = DAG('XYZ', default_args=default_args, start_date=datetime(2015, 9, 23, 23, 00), schedule_interval=timedelta(minutes=2))
But the DAG always starts at 2015-06-01. However subsequent executions rightly happen 2 mins later.
On a separate note, the UI shows this 2015-06-01 09:32:00 as Run time. Even if I change the Run time here, it doesn't save.
Also, can you please approve google group access? if you prefer i ask such questions in the group

It looks like if i use a different dag_id it works. Is there a cache?
I might have used the default for dag_id = 'XYZ' early on but then cancelled and changed the date to 2015-09-23. Now it doesn't respect the start date for the same  dag_id. Once i changed dag_id='abc', it worked fine

start_date is only used when "seeding" task (running for the first time), from that point on it adds the schedule_interval to the latest task instance.
From memory, the scheduler reloads the pipeline definition when it detects that the file has changed or every 10 runs.

Sure. I saw it reload. But shouldn't the scheduler pick up the new start_date on restart for the same dag_id?

Maybe it should skip ahead to the new start_date but that is not the current behavior. It's documented in both BaseOperator and The Scheduler.

I vote for skip ahead b/c I can't use the same dag_id anymore. your call.

Wait. You can clear the state (from the UI or CLI) and it will restart at start_date. You can also "mark success" on the run right before the one you want as your new start_date and the scheduler will pick it up from there.

oh ok. airflow clear dag_id from CLI works for me. In the UI, that dag is marked as success already.

Thanks CLI airflow clear solved it. unclear on the UI trick as that DAG is marked success already.

You could click each children and clear with include downstream, you could clear that task with include downstream and quickly mark success right after, before the scheduler has time to retrigger the task...

Click on one of the little square and click the Clear button from the
contextual menu. You can check all of "upstream/downstream/future/past"
prior to click clear to clear all
On Thu, Sep 24, 2015 at 10:38 AM, praveev<EMAIL_ADDRESS>wrote:

Thanks CLI airflow clear solved it. unclear on the UI trick as that DAG
is marked success already.
—
Reply to this email directly or view it on GitHub
https://github.com/airbnb/airflow/issues/456#issuecomment-142999520.

thanks

We found that if we want to have a new start_date, we need to do airflow clear first, followed by restarting the scheduler. The scheduler is not aware of the new start_date simply from loading the modified DAG file. Is this expected?


docs: 完善主题章节

👀 PR includes
🔧 Chore

[ ] Test case
[x] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description
完善主题章节
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self Check before Merge

[ ] Add or update relevant Docs.
[ ] Add or update relevant Demos.
[ ] Add or update relevant TypeScript definitions.

这一大坨可以删掉了吧？

 这一大坨可以删掉了吧？

别啊，我费老大劲更新完的。。

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add 2013 and 2014 neuropixels versions.

Hi All,
Some newer versions of NP probes (I think 'commercial 2B probes') have the metadata probe type as '2013' or '2014' rather than '21' or '24' as described here.
It seems the only changes are to the 'Reference IDs':
Type-2013,2014 reference ID values are {0=ext, 1=gnd, [2..5]=tip[0..3]}. On-shank reference electrodes are removed from commercial 2B probes.

I assume these are not relevant for neo as these reference channels are automatically set to off?
i.e. from here
You can mark a site used=0 if you know it is broken or disconnected. For imec probes, we automatically set used=0 for reference sites and those you have turned off (bad channels) in the IM Setup tab.

So, simply also accepting '2013' and '2014' probes seems to work, though it feels a little too good to be true 😅
I have a '2013' file to test against, happy to cut down and add to the testing repo. Currently I do not have a '2014' so this could be removed from this conditional in the case we want to test against it before rolling out.

The PR #1321  also made the same fix so we can close this.
Thanks Joe for poiting this.


fixadd if function signature for jsonb data type

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


android x86 not working

I am trying to run android x86 9.0-r2 but when I select a option it just goes back to the startup screen. I select vesa mode like it says, and I tried other modes too. anyone know what to do?

1.6 just takes awhile it eventually does attempt to boot that takes up to a hour or later

I was able to download the "vanilla" image off this page and boot it up in a few min using vesa mode. That'll be kitkat 4.4

I uploaded Android 4 here: https://copy.sh/v86/?profile=android4 It takes a long time to start and downloads at lot of data, so proceed with caution. Also updated the readme.
Since most versions of Android work (module SSE3 and other bits) I will close this issue.

I uploaded Android 4 here: https://copy.sh/v86/?profile=android4 It takes a long time to start and downloads at lot of data, so proceed with caution. Also updated the readme.
Since most versions of Android work (module SSE3 and other bits) I will close this issue.

Awesome!


working again, at least partially.  ignores NQPRoutine $meth now

i think this is a hack (or maybe it isn't?) but it makes both the tracer and debugger useable for the most part

hi @tony-o, have you found out which could go in there that are not ~~ Regex but are NQPRoutines?

@meisl I haven't looked at it anymore beyond making the module usable again


Difference in age bins between Chu's Matlab code and the updated Matlab code

In Chu's original Matlab code age bins were defined as ages 1 through 20 (with step size 1). However, a while ago it was found and confirmed by Chu that these age bins can miss out on older animals. It turns out that this is the case for the 2019 survey. For this reason, in the current Matlab code and also the current Python code we are defining the age bins as ages 1 through 22 (with step size 1). This allows us to capture all of the data.
For future reference, it should be noted that this will change the output (such as biomass) slightly. Additionally, it should be noted that the Matlab code produces length-age distributed data for the reports by hard coding the age bins. Thus, the updated Matlab code will be hard coded for age bins of 1 through 22.

@brandynlucca : pinging you here since this is something related to the current #168.

@brandynlucca : I think this is not an issue in your implementation, right? since now all age bins are included in the dataframes. If so, could you close this issue?


Workflow Fixes / General repo cleanup

Fixes workflow bugs by installing necessary dependencies. Not sure whose idea it was previously to have the CI jobs run on macos lol

All workflows are working nicely now.


Issue with mapping commas

Version Information:

Linux archlinux 5.16.2-arch1-1 #1 SMP PREEMPT Thu, 20 Jan 2022 16:18:29 +0000 x86_64 GNU/Linux
swhkd 1.0.0

Describe the bug:
I'm trying to map commas and having some problems. The map I'm trying to write is:
super + {comma, period}
	riverctl focus-output {previous, next}

But this won't work because swhkd appears to use the ascii character (",") instead of the keysym name ("comma") in mappings, which is fine, except:
super + {,, .}
	riverctl focus-output {previous, next}

Produces the error "[2022-02-27T17:32:13Z ERROR swhkd] Config Error: Unknown symbol at line 25" which is obvious given that {,,.} is clearly a syntax error.
However, I can't find a way to escape a comma inside curly braces.
Expected behavior:
I should be able to map commas using the keysym name or have a way to map them inside braces.
Actual behavior:
Launching swhkd with either of the above mappings will produce an error.
Additional information:
Fwiw, the first rule (super + {comma, period}) works in SXHKD.

@angelofallars @EdenQwQ Hi my dear config parsing coders ( 🤣 ).
@oncomouse thank you so much for the bug report , ^ they should get back to you soon. I did not write the config parser so sadly I can't be of much help at the moment.

Hi @oncomouse!
After examining our code, it seems that we do have comma correctly mapped. However, in your config:
super + {comma, period}
	riverctl focus-output {previous, next}

We currently do not have period mapped as of now. Instead, you can only use dot for now. I will add the period mapping right away.
For this mapping:
super + {,, .}
	riverctl focus-output {previous, next}

We haven't implemented escaping commas inside curly braces yet. I think we'll use backslash escapes for this one.
For now, you should use this mapping in swhkd 1.0.0:
super + {comma, dot}
	riverctl focus-output {previous, next}

Hope this helps.

@oncomouse
Update: I added handling to escape commas inside braces in PR #57, the syntax looks like this:
super + {\,, .}
	riverctl focus-output {previous, next}

You can escape commas inside braces with a leading backslash \. What are your thoughts on this?

@oncomouse please recompile from master branch, and let us know if that fixed it!

Yes, this is fixed. FWIW, I prefer the {comma, period} syntax. Thanks!


Improved handling of retina sprites

Added additional media queries for better coverage of when to use the retina sprite
Added sprite position for retina sprite

Had run into cases where the retina sprites positions were different from the non-retina sprite. Couldn't determine why it was out of order but didn't see any harm in adding background-position to the retina sprite either.
I have confirmed it's working as expected now for scss, the others I have not tested but attempted to updated based on the rest of the code. Didn't have a chance to update the tests either, which I assume will fail with the modified output.

Thanks for taking the time to open this PR. Currently, we are trying to use as little code as possible for our media queries/positioning to reduce the footprint of spritesmith. This means this PR would cause harm by adding unnecessary new info.
As a result (and to patch this bug properly), can you provide an example of the issue you are seeing (e.g. CSS flavor, browser, normal/retina spritesheets)?

Did some new research on the topic. It looks like we can switch to min-resolution over min-device-pixel-ratio but need to maintain -webkit-min-device-pixel-ratio for mobile browsers:
https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Media_queries
http://www.w3.org/blog/CSS/2012/06/14/unprefix-webkit-device-pixel-ratio/
http://caniuse.com/#feat=css-media-resolution

Sure. This is being used in a WordPress theme by way of grunt-spritesmith. I created a gist with the Gruntfile.js, package.json, and a few links to screenshots of the resulting sprites as well as a screenshot of my images dir. I think everything is setup right and it's really really simple, I just don't know why the two sprites have images in reverse order.

The problem you are encountering is due to lexicographical sorting by JS. It thinks that . is less than - so in the first array, logo.png is being sorted after logo-white.png. Whereas in the second, 2 is greater than w.
> var a = ['logo.png', 'logo-white.png'];
undefined
> a.sort();
[ 'logo-white.png', 'logo.png' ]
> var b = ['logo-2x.png', 'logo-white-2x.png'];
undefined
> b.sort();
[ 'logo-2x.png', 'logo-white-2x.png' ]

To fix your problem, I suggest renaming logo.png to logo-1x.png (and logo-white-1x for convention). That should fix up the sorting/ordering issues.
Aside from that, what was the reasoning for the new retina media queries?

Really it was just a "I'm already here and I use this in another mixin already, so I'll just drop it in" ... no "technical" reason beyond just assuming all the browsers "need" their own retina queries. No specific use case at the moment showing it isn't enough as is.
I'll update the file names and take it from there, also good to know now about the sorting and something to keep in mind in the future. I'll go ahead and close this - thanks for taking the time to write up an explaination!

Just confirming that renaming like you described worked out as expected.

Cool, glad to hear everything worked out =) I might update the media queries based on what I discovered (e.g. `min-device-pixel-ratio`` is deprecated)

Upon further review, it looks like we are already using the ideal combination. Yey =3

Awesome! If I find any cases where it doesn't seem to work, I'll be sure to let you know. Sounds like I'll have a hard time finding any though :)


Merge release 1.0.0 into master

Description
Merge release 1.0.0 into master
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: endgame
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

It must be squash because this repo currently does not allow merge commit.

Nevermind, I have permission to change the settings, so I did it.


FilterSystem JSDoc function signature

JSDoc comment doesn't match function signature: Fload32Array changed to: Float32Array

Codecov Report

Merging #7085 (1d387c0) into dev (1127bd7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #7085   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           17        17
  Lines          699       699
=========================================
  Hits           699       699

Continue to review full report at Codecov.

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


Adding Unicode Symbols to Macros

In the GUI's Macro Setup, is it possible to add unicode symbols (e.g., em dash — , degree °, section §) as macro hotkeys? I have tried using the symbols themselves and the "Alt+" codes (e.g., ALT+0151 for "—") without success.

I have found a workaround to make this work and have just pushed a new version of the pre-compiled GUI which should now work with "Alt+" codes in the following format:  e.g. for ° symbol use: "alt+num 2+num 4+num 8"
If you are not using the pre-complied .exe and running the source code you need to modify the keyboard library to get this to work. This can be done by finding the file "_canonical_names.py" and changing the lines that say:
num 0': '0',     to    num 0': 'num 0',
for 0-9.
This allows the keyboard library to send numpad numbers (by default this library just replaces these with non-numpad number) required for alt+ codes.
Let me know if you have any more issues

Fixed as per prev comment


Provide docker-compose.yml v3 in installing instructions

https://github.com/weaveworks/scope/blob/master/site/installing.md#using-docker-compose
&&
https://github.com/weaveworks/scope/blob/master/site/installing.md#using-docker-compose-with-weave-cloud
Reference https://docs.docker.com/compose/compose-file/

duplicate #2711


Renaming a field with a @Getter annotation prompts to rename the getter.

Consider a field such as:
@Getter private final JCTree decoratedTree;
Place the cursor on the field and push SHIFT+F6 to use IDEA's renaming function for this field.
IDEA will prompt: "A getter exists for decoratedTree - rename it as well?"
Presumably IDEA is detecting the lombok-generated getter that your plugin tells it to pretend exists.
The ideal behaviour in this case would be that your plugin would automatically tell IDEA "Yes" to this prompt - this would automagically update all calls to the Lombok-generated getter, which would be decidedly cool. Still, manually clicking a button isn't too hard as a workaround.

Closed as too old


Date interpretted as Unix File Path

On MacOS 13.1, using iTerm.
tailspin version 1.6.1
I use a black background in my terminal window and the blue in the time format was hard to read. I changed it to yellow in my ~/.config/tailspin/config.toml file as such:
...
[time]
time = { fg = "yellow" }
zone = { fg = "red" }
# To shorten the time, uncomment the line below
# shorten = { to = "␣", style = { fg = "blue" } }

Anyway, when I tried to view this log file, part of the date appears to be interpretted as a unix file path.
Also, I think the logic expects a . after the time but instead is seeing a : and interpretting it as something else.

$cat "com.flexibits.fantastical2.mac 2023-10-02--15-42-31-759.log"
2023/10/02 11:42:31:738  Location manager failed: Error Domain=kCLErrorDomain Code=0 "(null)"
2023/10/02 11:43:27:698  Location manager error: Error Domain=kCLErrorDomain Code=0 "(null)"
2023/10/02 11:47:39:850  Location manager failed: Error Domain=kCLErrorDomain Code=0 "(null)"

Thanks for opening this issue up with screenshots and detailed description to reproduce.
Unfortunately, the dates of the format yyyy/mm/dd are not currently supported. In this case, I think it would solve the issue because it would highlight the dates before the unix path highlighter got a chance to look at it.
I would like to add support for this, however it is a bit tricky because the regexes to highlight the dates are so different, they can't be reused.
I can't give a timeline to this yet, but support for this format is something that should be added at some point for sure.
For now, what locale are you using, if you don't mind me asking?

No problem. Happy to help.
I look forward to testing the next update.
I am in North America, EST if that helps.

Fixed in 3.0.0 🎉


Module not found

Hello,
thank you for this project! When I install  and run the CLI with
pipx install git+https://github.com/in03/proxima
I get the following error:
ModuleNotFoundError: No module named 'proxima'
Maybe I'm doing something wrong? I tried it on two machines with MacOS Ventura.
Thank you!

Hey @apvlv!
Sorry to hear you're having issues!
I pushed a fix. Tested and working on Ventura for me.
Let me know if it's working now for you.
Thanks for your interest!


Automate deploy

Continuous Deploy configuration was added on #56.
@viniciusalbuquerque do you think we can close this issue?


High-cardinality HTTP span names

The spans are GET /the/path/123 which are high-cardinality.
Instead, I suggest http.request:GET.

Spec states http spans specifically should be named after the method (GET, POST, etc) if the route name is not available. https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/data-http.md#name

Correct me if I am wrong but I'm under the impression that high cardinality is the point of tracing data?

Names are not meant to uniquely identify a trace, but a class of traces. for instance, GET /user/:id is a good name, but GET /user/123 is bad because you can't easily search for all traces for the same route.

@dyladan Using the route would require to the modify the span after it has been created (inside the express plugin for example).Correct me if i'm wrong but i believe there are no way to do that right now ?

That is the core issue at question in this issue https://github.com/open-telemetry/opentelemetry-specification/issues/468
It seems like they're leaning towards keeping updateName but with a different name.

I'm interested in picking up this issue, but just wanted to clarify the solution.
I think the change is going to be in the framework plugins (eg express/koa/hapi), having it call updateName on the parent span when it has the route name available.
Also, if that is correct and the change will be in the opentelemetry-js-contrib repo, should this issue be closed or moved over to that repo?

@gecgooden There are some code on the http plugin that should be removed too

Any progress on this? This is critical issue imho.
Are there any suggestions for implementation? Maybe add an option to disable adding path in the span name?

[Spec](Are there any suggestions for implementation? Maybe add an option to disable the path in the span name?) says

Instrumentation MUST NOT default to using URI path as span name

Assigning @morigs because he opened the PR


Create hello-world-actions.yml

on:
push:
branches: [main]
workflow_dispatch:

Thanks for contributing. What's the PR for?


Missing Queue Families

With vulkano the queue families method on the physical device only returns one queue family and one queue in that family (first one in the image). Using vulkan-caps-viewer, it shows that I have 2 queue families with the first having 1 queue and the other 8 queues. Is this intended behavior? This is on linux with an RX 480 using radv. On windows with the RX 480 I get multiple queues as I'd expected.

Could you show your code? It's not an intended behaviour.

 I simplified the code and now they all show up.


Switch to fs_err

Filesystem errors are unfortunately common but hard to debug currently. We should consider a switch to https://docs.rs/fs-err/latest/fs_err/ to make it better.

@morgante I have added a PR, hope this issue is open for external contribution.


external repository detection fix and usability improvements to exclude branches during clone/fetch

fixed bug in external repository detection
improved usability by

exposing ignore-not-init-branches to commandline
added ignore-branches-regex to more granularly control which branches to initialize during fetching and cloning

seems like I missed something in a unittest :/
Fixing it

Thanks a lot.
I think that it will pleased some users...


[regression][GPU]: 'func.func' op uses 81920 bytes of shared memory; exceeded the limit of 65536 bytes post 6ff00a8a008d06b604d4ca4e0ae6e601ae810b4f

What happened?
We have 100+ models failing in GPU which were earlier passing numeric and started post https://github.com/iree-org/iree/commit/6ff00a8a008d06b604d4ca4e0ae6e601ae810b4f
module {
  func.func @torch_jit(%arg1:!torch.vtensor<[1,128,4,256],f32>) -> !torch.vtensor<[1,257,4,256],f32    > attributes {torch.onnx_meta.ir_version = 7 : si64, torch.onnx_meta.opset_version = 21 : si64, torch.onnx_meta.producer_name = "pytorch", torch.onnx_meta.producer_version = "1.12.1"} {
    %1 = torch.operator "onnx.Constant"() {torch.onnx.value = dense_resource<_stages.2.1.transformer.0.attn.qkv_proj.weight> : tensor<257x128x1x1xf32>} : () -> !torch.vtensor<[257,128,1,1],f32>
    %2 = torch.operator "onnx.Constant"() {torch.onnx.value = dense_resource<_stages.2.1.transformer.0.attn.qkv_proj.bias> : tensor<257xf32>} : () -> !torch.vtensor<[257],f32>
    %3 = torch.operator "onnx.Conv"(%arg1, %1, %2) {torch.onnx.dilations = [1 : si64, 1 : si64], torch.onnx.group = 1 : si64, torch.onnx.kernel_shape = [1 : si64, 1 : si64], torch.onnx.pads = [0 : si64, 0 : si64, 0 : si64, 0 : si64], torch.onnx.strides = [1 : si64, 1 : si64]} : (!torch.vtensor<[1,128,4,256],f32>, !torch.vtensor<[257,128,1,1],f32>, !torch.vtensor<[257],f32>) -> !torch.vtensor<[1,257,4,256],f32>
    return %3 : !torch.vtensor<[1,257,4,256],f32    >
  }
}

command:
iree-compile model.torch_onnx.mlir --iree-hal-target-backends=rocm --iree-hip-target=gfx942 -o abc.vmfb

model.torch_onnx.mlir.txt
Steps to reproduce your issue

Go to '...'
Click on '....'
Scroll down to '....'
See error

What component(s) does this issue relate to?
Compiler
Version information
No response
Additional context
No response

Which 100 models? Please be specific in bug reports.

Here's the list of test failures: https://github.com/nod-ai/e2eshark-reports/blob/main/2024-12-17/ci_reports_onnx/rocm/combined-reports/yesterday_comparison.md#317-regressions-found. Lots in the "vit" family (vision transformers)

Good news: with the existing tests in https://github.com/iree-org/iree-test-suites/tree/main/onnx_models, I can reproduce a regression in a few models like mobilenet and resnet50 using --iree-hal-target-backends=rocm --iree-hip-target=gfx1100. So once I land PRs to get those tests running on multiple backends, we should have earlier signal for these sorts of regressions.

Repro using resnet from https://github.com/iree-org/iree-test-suites/pull/65:
# Setup
.\.venv\Scripts\activate.bat
cd onnx_models
pip install --upgrade -r requirements-iree.txt

# Run test that passes
pytest --log-cli-level=info -rA --durations=0 -k resnet --test-config-file=./configs/onnx_models_gpu_rocm_rdna3.json

# Switch to broken release, run again to see failure
pip install --find-links https://iree.dev/pip-release-links.html iree-base-compiler==3.1.0rc20241217
pytest --log-cli-level=info -rA --durations=0 -k resnet --test-config-file=./configs/onnx_models_gpu_rocm_rdna3.json

Once that PR and https://github.com/iree-org/iree/pull/19524 land we'll have that coverage on all IREE PRs.

I also noticed that this error spews a looooot of logs (multiple thousands of lines): https://github.com/iree-org/iree/blob/fb4d09470dc4be674de810dbfbf2d3764e2970ba/compiler/src/iree/compiler/Codegen/Common/GPU/GPUCheckResourceUsage.cpp#L85-L87
Maybe we don't need the entire context?


Text correction on "Send To" screen.

One "in" to be removed. Tested on dev app v2.0(345)

verified this issue on staging app v2.0(349)


Save filters in query params and apply them on load

Closes https://github.com/microsoft/bedrock/issues/761

@samiyaakhtar @edaena  I would suggest 2 reviewers on PRs


Nice work, but when i wanna run this code there is a mistake.

Traceback (most recent call last):
File "eval_mot.py", line 2, in
import cv2
ImportError: /lib/x86_64-linux-gnu/libz.so.1: version `ZLIB_1.2.9' not found (required by /home/adminroot/anaconda3/envs/zmh/lib/libpng16.so.16)
(zmh) adminroot@adminroot:~/zmh/MOTDT-master$ pip install zlib
Collecting zlib
Could not find a version that satisfies the requirement zlib (from versions: )
No matching distribution found for zlib
i try pip install ZLIB, but it fails, i donot know why, would you have some suggestions?

when i follow your steps one by one, but when i run 'python eval_mot.py' there is a mistake like:
(zmh) adminroot@adminroot:~/zmh/MOTDT-master$ python eval_mot.py
Traceback (most recent call last):
File "eval_mot.py", line 158, in
show_image=False)
File "eval_mot.py", line 93, in main
mkdirs(result_root)
File "eval_mot.py", line 17, in mkdirs
os.makedirs(path)
File "/home/adminroot/anaconda3/envs/zmh/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
File "/home/adminroot/anaconda3/envs/zmh/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
File "/home/adminroot/anaconda3/envs/zmh/lib/python3.6/os.py", line 210, in makedirs
makedirs(head, mode, exist_ok)
[Previous line repeated 2 more times]
File "/home/adminroot/anaconda3/envs/zmh/lib/python3.6/os.py", line 220, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/data'
then i think that it havn't


Purchase not showing up on "Orders" page

A purchase was made on the shop https://graphics-illustrations-crypto-shop.ogn.app/ but the orders page still shows "no orders yet".
For reference, the tx is: https://etherscan.io/tx/0xf944dfae1fc83e97a46939c0900285091cabcb93766ad40a11c1938de7e9930a

Re-ran the failed job and the order is now showing up in the graphics-illustration store.
Added more resiliency to our back-end in #913 so that this does not occur again.


Chat client connectivity problems after installing pfSense VPN/firewall

We recently installed a pfSense appliance for VPN, firewall and IDS (Snort) services. After doing this, the Keybase chat client stopped working on an ubuntu 16.04.3 PC (though it appears to still work on a Windows device). Not sure how to troubleshoot or address this.
The client reports: "Couldn't load all chat messages due to network connectivity. Retrying..."

FWIW, uninstalling and reinstalling the keybase client appears to have solved the problem.


Consider a blacklist approach for RequestContextCurrentTraceContext

An armeria app uses a tracing object that coexists with activity that is not request originated. Threads like these will result in the following message to be logged:
                logger.warn("Attempted to propagate trace context, but no request context available. " +
                            "Did you forget to use RequestContext.contextAwareExecutor() or " +
                            "RequestContext.makeContextAware()?", new NoRequestContextException());

The advice is totally invalid in these cases as for example a scheduled thread or reporting loop has no relevance (afaik).
One way out is to allow configuration of a pattern of threads that should be ignored as opposed to spawning this message. This will allow options besides wild hacks or worse killing the log message.
Ex this is how sleuth handles one of the places that are relatively hard to shut-up :)
https://github.com/spring-cloud/spring-cloud-sleuth/blob/558900155adb1ae4a732cf450c216e2ff04a3f90/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/instrument/rxjava/SleuthRxJavaSchedulersHook.java#L126
Another option is to introduce some sort of thread local which you can set to say "ignore". For example, I could set that in a thread factory in order to quiet the root thing I'm trying to do which is in some ways better than scary comments which may end up lying.
thoughts?

For those requests who aren't request originated, I think they will need a fallback implementation based on normal thread local, and we'd have to consider what happens when they eventually create a client call..

Yeah I've generally ignored the message knowing it's about spans like 'SET blah' to MySQL which I wish didn't exist in the first place :P
But it's true that there are probably background operation use cases that should have the fallback propagation. I think what we've found is depending on where a trace is started (or span? or some other unit) we want to be able to set a custom context propagation system. It might not even be started - I can't think of a use case, but I guess it's possible there is a trace started by something on top of Armeria, but once it hits BraveService, we want to make sure context continues propagation using RequestContext instead of a threadlocal to allow for asynchronous operations. So being able to switch propagation methods at points in the trace. Seems complicated, but something we should think about for Brave?

we could discuss in brave, just this is the only place we have such a
request context stealing so figured we would be in a better place to
discuss impact here.
another option could be to make a dummy request context as a seed value. my
wonder is if we had such we could simplify transitions to client contexts
later?
On Tue, Aug 6, 2019, 4:55 PM Anuraag Agrawal<EMAIL_ADDRESS>wrote:

Yeah I've generally ignored the message knowing it's about spans like 'SET
blah' to MySQL which I wish didn't exist in the first place :P
But it's true that there are probably background operation use cases that
should have the fallback propagation. I think what we've found is depending
on where a trace is started (or span? or some other unit) we want to be
able to set a custom context propagation system. It might not even be
started - I can't think of a use case, but I guess it's possible there is a
trace started by something on top of Armeria, but once it hits
BraveService, we want to make sure context continues propagation using
RequestContext instead of a threadlocal to allow for asynchronous
operations. So being able to switch propagation methods at points in the
trace. Seems complicated, but something we should think about for Brave?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/line/armeria/issues/1964?email_source=notifications&email_token=AAAPVVYVF3H32CBLKI6VZ4LQDD74PA5CNFSM4IJSEAYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3T2V7Q#issuecomment-518499070,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAPVV4BHLDTYJGTFM7QBLTQDD74PANCNFSM4IJSEAYA
.

Yeah think we can discuss here, just wondering if it makes sense to add the switching mechanism in Brave. Allowing threads to opt-out of the warning handles many use cases, but still stuck for my database threadpool since it's used both during request handling and also in the background with things like SET charset. Being able to specify the trace context propagation method when starting a trace, instead of globally, would help with that.

I agree it is worthwhile thinking through, if nothing else for brave 6. There have been cases especially around propagation policy (like which headers.. which is different than in-process) that need some rethought eventually. However, at the moment, trying to add a hook to the span about how you will look the same span up ends up contortionist I think (as currently any hints we store are inside the data in the thread local which we are currently discussing :P). That said each instrumentation could choose to do things differently, but we sortof already do because we never use thread locals in our code except crazy circumstances. regardless, feel free to raise a discussion on brave. tx!


Implement thread::scope

Is there an equivalent to std::thread::scope? I see that Loom also doesn't implement this.

Hi, no, std::thread::Scope and std::thread::scope does not exist. It shouldn't be all that difficult to implement, we just haven't had a need for scoped threads. Of course, contributions towards this would be more than welcome :).

Thanks!


Community Size - How to evaluate ?

I was thing of the number of questions on stack-overflow about the project but this means that a tag for the project exists, which may not be the case.
Furthermore, I would prefer not to completely disadvantage small projects.
Number of stars could be a way of getting that.
Ideas ?

Can't we use metrics from http://mvnrepository.com, https://rubygems.org, https://pypi.python.org/pypi ?
A simple way to deploy the rated project should be a minimum.

These could provide good metrics. However they imply that we support a finite number of langages and that it depends on their dependency management systems.
The advantage of using github only metrics is that we could be used for rating nearly every kind of project on github.
I guess the question really is: do we want to limit the number of langages to get more detailed data ?

The number of stars can also be used as bookmarks (awesome-*** repos) or as signs of approval.
The number of answered pull request could be a good sign.

I agree for the number of stars.
What do you mean for

The number of answered pull request

A pull request can be a sign that there are a lot of things to fix :). On the other hand it is also a sign of implications.

*Issues sorry
Le 24 mai 2015 23:43, "Nicolas Joseph"<EMAIL_ADDRESS>a écrit :

I agree for the number of stars.
What do you mean for
The number of answered pull request
A pull request can be a sign that there are a lot of things to fix :). On
the other hand it is also a sign of implications.
—
Reply to this email directly or view it on GitHub
https://github.com/callicles/github-rank-project/issues/5#issuecomment-105064123
.

closed issues then ?

Yes.


Tests: Move to spec folder

:+1: - will the folder test/rules be removed?

Yeah, git doesn't track empty directories.


fix: override importmap in PR

Please review this PR as soon as possible,  it affects the preview of all PRs.


Error on first deploy to Azure Functions and not deployed.

Version
Python: 3.11
Core tools: 4.0.5907
Description
The following error occurs during the first deploy to Azure Functions and it is not deployed.
Execute the same command again and the deployment will succeed.
First deployment
$ func azure functionapp publish func-test
Local python version '3.8.10' is different from the version expected for your deployed Function App. This may result in 'ModuleNotFound' errors in Azure Functions. Please create a Python Function App for version 3.8 or change the virtual environment on your local machine to match 'Python|3.11'.
Getting site publishing info...
[2024-09-04T10:09:33.768Z] Starting the function app deployment...
Removing WEBSITE_CONTENTAZUREFILECONNECTIONSTRING app setting.
Removing WEBSITE_CONTENTSHARE app setting.
Creating archive for current directory...
Performing remote build for functions project.
Deleting the old .python_packages directory
Uploading 1.3 KB [################################################################################]
Remote build in progress, please wait...
Sequence contains no elements
$

Second deployment
$ func azure functionapp publish func-test
Local python version '3.8.10' is different from the version expected for your deployed Function App. This may result in 'ModuleNotFound' errors in Azure Functions. Please create a Python Function App for version 3.8 or change the virtual environment on your local machine to match 'Python|3.11'.
Getting site publishing info...
[2024-09-04T10:09:33.768Z] Starting the function app deployment...
Creating archive for current directory...
Performing remote build for functions project.
Deleting the old .python_packages directory
Uploading 1.3 KB [################################################################################]
Remote build in progress, please wait...
Updating submodules.
Preparing deployment for commit id '6b8baeb5-1'.
PreDeployment: context.CleanOutputPath False
PreDeployment: context.OutputPath /home/site/wwwroot
Repository path is /tmp/zipdeploy/extracted
Running oryx build...
Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.11 -p packagedir=.python_packages/lib/site-packages
Operation performed by Microsoft Oryx, https://github.com/Microsoft/Oryx
You can report issues at https://github.com/Microsoft/Oryx/issues

Oryx Version: 0.2.20230210.1, Commit: a49c8f6b8abbe95b4356552c4c884dea7fd0d86e, ReleaseTagName: 20230210.1

Build Operation ID: 1aa8c03afbb27e30
Repository Commit : 6b8baeb5-1733-418b-a1e3-493df532aef4
OS Type           : bullseye
Image Type        : githubactions

Detecting platforms...
Detected following platforms:
  python: 3.11.8
Version '3.11.8' of platform 'python' is not installed. Generating script to install it...

Source directory     : /tmp/zipdeploy/extracted
Destination directory: /home/site/wwwroot

Downloading and extracting 'python' version '3.11.8' to '/tmp/oryx/platforms/python/3.11.8'...
Detected image debian flavor: bullseye.
Downloaded in 1 sec(s).
Verifying checksum...
Extracting contents...
performing sha512 checksum for: python...
Done in 8 sec(s).

image detector file exists, platform is python..
OS detector file exists, OS is bullseye..
Python Version: /tmp/oryx/platforms/python/3.11.8/bin/python3.11
Creating directory for command manifest file if it does not exist
Removing existing manifest file

Running pip install...
Done in 22 sec(s).

...

Creating placeholder blob for linux consumption function app...
SCM_RUN_FROM_PACKAGE placeholder blob scm-latest-func-test.zip located
Uploading built content /home/site/artifacts/functionappartifact.squashfs for linux consumption function app...
Resetting all workers for func-test.azurewebsites.net
Deployment successful. deployer = Push-Deployer deploymentPath = Functions App ZipDeploy. Extract zip. Remote build.
Remote build succeeded!
[2024-09-04T10:16:23.626Z] Syncing triggers...
Functions in func-test:
    test - [httpTrigger]
        Invoke url: https://func-test.azurewebsites.net/api/test
$

Steps to reproduce
Deploy locally using Core tools.

Hi @Shotaro-Yoshinaga-sti  Thanks for reporting  will check and update you.

can you try once again .it seems working.

Thank you very much! I have confirmed that it is deployed successfully.

Sorry, I accidentally closed it.


standalone-cinder-provisioner fails to allocate PersistentVolumeClaim

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
What happened:
standalone-cinder-provisioner failed to allocate claim from a standalone Cinder instance (stuck in Pending state).
I can see the standalone-cinder-provisioner pickup the pvc create request:
I0515 19:48:28.573000       1 controller.go:492] Starting provisioner controller f04d44f3-5878-11e8-ad2a-b65d335b448a!
I0515 19:51:50.381817       1 controller.go:1167] scheduleOperation[lock-provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:51:50.383588       1 controller.go:1167] scheduleOperation[lock-provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:51:50.393835       1 leaderelection.go:156] attempting to acquire leader lease...
I0515 19:51:50.398264       1 leaderelection.go:178] successfully acquired lease to provision for pvc default/myclaim
I0515 19:51:50.398350       1 controller.go:1167] scheduleOperation[provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:51:56.545811       1 controller.go:900] volume "pvc-68960194-5879-11e8-9631-7cfe903a4aff" for claim "default/myclaim" created

and I can see this pass through to stand alone Cinder (blockbox) and actually create the volume:
2018-05-15 20:51:50.688 23 DEBUG cinder.volume.manager [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] Task 'cinder.volume.flows.manager.create_volume.CreateVolumeFromSpecTask;volume:create' (c84bdd51-ca03-47a2-a185-1820c2c20aa7) transitioned into state 'RUNNING' from state 'PENDING' _task_receiver /var/lib/openstack/local/lib/python2.7/site-packages/taskflow/listeners/logging.py:194
2018-05-15 20:51:50.689 23 INFO cinder.volume.flows.manager.create_volume [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] Volume b994c226-3c98-433c-9b0f-2b86d7003074: being created as raw with specification: {'status': u'creating', 'volume_size': 1, 'volume_name': u'volume-b994c226-3c98-433c-9b0f-2b86d7003074'}
2018-05-15 20:51:50.690 23 DEBUG oslo_concurrency.processutils [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] Running cmd (subprocess): env LC_ALL=C lvcreate -T -V 1g -n volume-b994c226-3c98-433c-9b0f-2b86d7003074 cinder-volumes/cinder-volumes-pool execute /var/lib/openstack/local/lib/python2.7/site-packages/oslo_concurrency/processutils.py:372
2018-05-15 20:51:50.872 23 DEBUG oslo_concurrency.processutils [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] CMD "env LC_ALL=C lvcreate -T -V 1g -n volume-b994c226-3c98-433c-9b0f-2b86d7003074 cinder-volumes/cinder-volumes-pool" returned: 0 in 0.182s execute /var/lib/openstack/local/lib/python2.7/site-packages/oslo_concurrency/processutils.py:409
2018-05-15 20:51:50.874 23 DEBUG cinder.volume.manager [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] Task 'cinder.volume.flows.manager.create_volume.CreateVolumeFromSpecTask;volume:create' (c84bdd51-ca03-47a2-a185-1820c2c20aa7) transitioned into state 'SUCCESS' from state 'RUNNING' with result '{'status': u'creating', 'volume_size': 1, 'volume_name': u'volume-b994c226-3c98-433c-9b0f-2b86d7003074'}' _task_receiver /var/lib/openstack/local/lib/python2.7/site-packages/taskflow/listeners/logging.py:183
2018-05-15 20:51:50.875 23 DEBUG cinder.volume.manager [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] Task 'cinder.volume.flows.manager.create_volume.CreateVolumeOnFinishTask;volume:create, create.end' (280c3617-e162-4ea7-a5d8-6b36e3ead972) transitioned into state 'RUNNING' from state 'PENDING' _task_receiver /var/lib/openstack/local/lib/python2.7/site-packages/taskflow/listeners/logging.py:194
2018-05-15 20:51:50.881 23 INFO cinder.volume.flows.manager.create_volume [req-c0f6ac39-2685-4daa-95f8-cb052ee55c76 admin admin - - -] Volume volume-b994c226-3c98-433c-9b0f-2b86d7003074 (b994c226-3c98-433c-9b0f-2b86d7003074): created successfully

And the volume can be listed with 'cinder list':
ubuntu@k8s-master-0:~$ cinder list
+--------------------------------------+-----------+---------------------------------------------------------+------+-------------+----------+-------------+
| ID                                   | Status    | Name                                                    | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+-----------+---------------------------------------------------------+------+-------------+----------+-------------+
| b994c226-3c98-433c-9b0f-2b86d7003074 | attaching | cinder-dynamic-pvc-6899dcc8-5879-11e8-ad2a-b65d335b448a | 1    | -           | false    |             |
+--------------------------------------+-----------+---------------------------------------------------------+------+-------------+----------+-------------+

But then there appears to be some sort of timeout or miscommunication reported by the standalone-cinder-provisioner, and the cinder volume is then subsequently automatically deleted:
I0515 19:52:20.465708       1 leaderelection.go:204] stopped trying to renew lease to provision for pvc default/myclaim, timeout reached
I0515 19:52:26.558231       1 controller.go:921] failed to save volume "pvc-68960194-5879-11e8-9631-7cfe903a4aff" for claim "default/myclaim": Timeout: request did not complete within allowed duration
I0515 19:52:28.584805       1 controller.go:1167] scheduleOperation[provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:52:36.564608       1 controller.go:921] failed to save volume "pvc-68960194-5879-11e8-9631-7cfe903a4aff" for claim "default/myclaim": persistentvolumes "pvc-68960194-5879-11e8-9631-7cfe903a4aff" already exists
I0515 19:52:43.585004       1 controller.go:1167] scheduleOperation[lock-provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:52:43.593096       1 leaderelection.go:156] attempting to acquire leader lease...
I0515 19:52:43.595853       1 leaderelection.go:178] successfully acquired lease to provision for pvc default/myclaim
I0515 19:52:43.595902       1 controller.go:1167] scheduleOperation[provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:52:46.569739       1 controller.go:921] failed to save volume "pvc-68960194-5879-11e8-9631-7cfe903a4aff" for claim "default/myclaim": persistentvolumes "pvc-68960194-5879-11e8-9631-7cfe903a4aff" already exists
I0515 19:52:56.574953       1 controller.go:921] failed to save volume "pvc-68960194-5879-11e8-9631-7cfe903a4aff" for claim "default/myclaim": persistentvolumes "pvc-68960194-5879-11e8-9631-7cfe903a4aff" already exists
I0515 19:52:58.585145       1 controller.go:1167] scheduleOperation[provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:53:06.581022       1 controller.go:921] failed to save volume "pvc-68960194-5879-11e8-9631-7cfe903a4aff" for claim "default/myclaim": persistentvolumes "pvc-68960194-5879-11e8-9631-7cfe903a4aff" already exists
I0515 19:53:13.585304       1 controller.go:1167] scheduleOperation[provision-default/myclaim[68960194-5879-11e8-9631-7cfe903a4aff]]
I0515 19:53:13.656399       1 leaderelection.go:204] stopped trying to renew lease to provision for pvc default/myclaim, timeout reachedE0515 19:53:16.581166       1 controller.go:931] Error creating provisioned PV object for claim default/myclaim: persistentvolumes "pvc-68960194-5879-11e8-9631-7cfe903a4aff" already exists. Deleting the volume.

What you expected to happen:
I am trying to build a baremetal Kubernetes cluster that uses a stand alone instance of Cinder (now Keystone integration based on blockbox) as the backend volume manager serving lvm volumes.  I would expect the standalone-cinder-provisioner to  allocate the PersistentVolumeClaim and attach storage to appropriate node available for dependent Pod.
How to reproduce it (as minimally and precisely as possible):
Install stand alone Cinder (blockbox) as described in https://thenewstack.io/deploying-cinder-stand-alone-storage-service/, and https://github.com/openstack/cinder/blob/master/contrib/block-box/docker-compose.yml .
Configure k8s as described here https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/#running-cloud-controller-manager including setting up and enabling Initializers and disabling PersistentVolumeLabel.
Deploy standalone-cinder-provisioner as described https://github.com/kubernetes/cloud-provider-openstack/blob/master/manifests/provisioner/deployment.yaml, with the configuration modified for stand alone Cinder:
       ...
        - name: OS_CINDER_ENDPOINT
          value: http://{{ cluster_api_address }}:8776/v3
        - name: CINDER_ENDPOINT
          value: http://{{ cluster_api_address }}:8776/v3
        - name: CINDERCLIENT_BYPASS
          value: http://{{ cluster_api_address }}:8776/v3
        - name: OS_AUTH_SYSTEM
          value: noauth
        - name: OS_VOLUME_API_VERSION
          value: "3.44"
        - name: OS_USERNAME
          value: admin
        - name: OS_PROJECT_ID
          value: admin

Anything else we need to know?:
standalone-cinder-provisioner image version:
k8scloudprovider/cinder-provisioner                                         latest              5aa7587eb628        5 days ago          29.2MB
stand alone Cinder (blockbox) was built from master at commit https://github.com/openstack/cinder/commit/f6cad81789d5816a2a0aa78da0a9b7c2ebf0fa33
I am unsure what other information I need to provide, so please ask if something else is required.  Thanks in advance for any help or advice.
Environment:

openstack-cloud-controller-manager version:
OS (e.g. from /etc/os-release): 16.04.4 LTS (Xenial Xerus)
Kernel (e.g. uname -a): Linux k8s-master-0 4.4.0-96-generic #119-Ubuntu SMP Tue Sep 12 14:59:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Install tools: kubeadm
Others:
Kubernetes:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:22:21Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:10:24Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

cc @j-griffith @flaper87 @edisonxiang @aglitke


Add (&&&) and (***)

These two little utility functions are quite useful and harmless, I thought it would be practical to add them!

These exists in http://pursuit.purescript.org/packages/purescript-profunctor/0.3.1/docs/Data.Profunctor.Strong#v:-42--42--42-

Oh sorry, I missed that one.


[draft] improve compile times

This PR aims to improve compile times of DAPHNE itself. Improving the compilation times of a fully fresh build, including dependencies is not the goal of this PR.
To establish some baselines, on my machine a fresh DAPHNE build normally takes about 2min 35s.
Before ~2min 35s
Here we can see a profiled run the current state (9a1b93e4fea27e91d14c18821be2c940adf63bf4)

I've made some changes, mainly splitting up the kernels.cpp file that is being generated by genKernelInst.py into compilation units per kernel. This improves parallelization as each translation unit can be built by itself. Yes, this does introduce some overhead in parsing the same headers in multiple translation units but for now the results are way better than before. I've also tried splitting into fewer translation units and splitting the kernels each into a translation unit provided the fastest compile times.
Modifying and recompiling a single/couple headers now also only takes a few seconds as they only need to recompile the changed translation units instead of all the kernels.
Additionally, I've made the libAllKernels an OBJECT library. This enables parallel compilation of the kernels library and the compiler parts.
Current ~1min 30s
With that, compilation times come down to about 1min 30s. The result can be seen here.

There still are some heavy hitters, the biggest offenders being the files that depend on MLIRDaphne and include daphne.h and the EigenCal.h kernel, which brings in the Eigen dependency.
Removing these 4 kernels from compilation would reduce the compilation time down to 1min. IMO we should move these few kernels out of the AllKernels target to decouple the kernel runtime from the compiler infrastructure.
Including daphne.h introduces a significant amount of overhead in multiple translation units and is included all over the codebase. I think decoupling some of the MLIR related parts from daphne.h would improve overall compilation times and should be done in the future as this PR concerns itself only with the kernels library.
Open issues:

[ ] probably better to generate object files with the actual kernel name instead of the increasing index
[ ] duplicate symbols when compiling tests
[ ] split kernel also for CUDA compilation, although I have to look more

Nice progress with this issue :ok_hand:
In general it is more beneficial for compile times to split declarations from definitions to create more parallelism. We're doing that here and there but it's rather up to the individual developer. As with the code formatting this is an effect of not having the discussion about coding style.
I've seen quite some time spent while linking. Using the LLVM linker didn't improve things too dramatically. It seems that this is also greatly improved with these changes from what I gathered from the images above (how did you generate those btw?).

The CUDA kernels don't have so much impact as there are fewer of them, but they can also benefit of this imho. In general I'm positive towards more granularity in compilation and reduce the weight of libAllKernels.

I don't want to hijack the discussion here but take the opportunity to raise attention to #474 where I never received feedback. Running build.sh from scratch does not only take a lot of time and resources for building but also the git checkout of the LLVM mono repo is a matter of a few minutes. Using a snapshot (which I'm mostly doing as the feature is implemented, but I didn't want to change defaults without discussion) speeds this up considerably. :speedboat:

Nice progress with this issue 👌
In general it is more beneficial for compile times to split declarations from definitions to create more parallelism. We're doing that here and there but it's rather up to the individual developer. As with the code formatting this is an effect of not having the discussion about coding style.
I've seen quite some time spent while linking. Using the LLVM linker didn't improve things too dramatically. It seems that this is also greatly improved with these changes from what I gathered from the images above (how did you generate those btw?).

Mhm from what I've seen linking shouldn't take too long, are you sure cmake is using lld? How did you measure that?
The images are generated by parsing the build/.ninja_log file with ninjatracing and viewing here. See #516 for more.

lld is linking Clang 19 (1.56 GiB) and  Chromium 124 (1.35 GiB) in ~5 seconds, can't imagine it being a huge part in DAPHNE. Also not sure what other options we have besides mold which is from the same person as lld.

Nice progress with this issue 👌
In general it is more beneficial for compile times to split declarations from definitions to create more parallelism. We're doing that here and there but it's rather up to the individual developer. As with the code formatting this is an effect of not having the discussion about coding style.
I've seen quite some time spent while linking. Using the LLVM linker didn't improve things too dramatically. It seems that this is also greatly improved with these changes from what I gathered from the images above (how did you generate those btw?).

I was relying on the configuration in our main CMakeLists to use LLD. I didn't do a study on it. I just didn't see a lot of speedup after this was introduced and also, at the end of the compilation process there's a single core on 100% for minutes. I thought LLD can do some some magic there without further looking into it :see_no_evil:

Mhm from what I've seen linking shouldn't take too long, are you sure cmake is using lld? How did you measure that?
The images are generated by parsing the build/.ninja_log file with ninjatracing and viewing here. See #516 for more.

:+1:

Nice progress with this issue 👌
In general it is more beneficial for compile times to split declarations from definitions to create more parallelism. We're doing that here and there but it's rather up to the individual developer. As with the code formatting this is an effect of not having the discussion about coding style.
I've seen quite some time spent while linking. Using the LLVM linker didn't improve things too dramatically. It seems that this is also greatly improved with these changes from what I gathered from the images above (how did you generate those btw?).

I was relying on the configuration in our main CMakeLists to use LLD. I didn't do a study on it. I just didn't see a lot of speedup after this was introduced and also, at the end of the compilation process there's a single core on 100% for minutes. I thought LLD can do some some magic there without further looking into it 🙈

Mhm from what I've seen linking shouldn't take too long, are you sure cmake is using lld? How did you measure that?
The images are generated by parsing the build/.ninja_log file with ninjatracing and viewing here. See #516 for more.

👍

There should be an early message output saying Using lld. Otherwise I'm not really sure, I don't seem to have that problem :')

I was relying on the configuration in our main CMakeLists to use LLD. I didn't do a study on it. I just didn't see a lot of speedup after this was introduced and also, at the end of the compilation process there's a single core on 100% for minutes. I thought LLD can do some some magic there without further looking into it 🙈

There should be an early message output saying Using lld. Otherwise I'm not really sure, I don't seem to have that problem :')

I guess this does not work as it is saying both -- Using lld and before that -- Linker detection: GNU ld and link times stay slow.

I just tested these changes and can report an improvement from 2m47 -> 1m17 :1st_place_medal: :tada: :rocket:

Results from running in the container: Build reports success but libAllKernels.so is not there. Therefore, running anything fails.

That should only have happened if you didn't pull updates in this PR as this has been fixed in 6532eaa9651c30e61a30e913761b16ac891b67a3 . Could that be the case? For GPU to work you'd need the up to date PR.

Oh the PR is still in draft state. Further changes planned for this?

Oh the PR is still in draft state. Further changes planned for this?

Actually it's no longer in draft, maybe I shouldn't put that in the title :)

Tests are running fine now with and without CUDA. I'd merge it in once the mystery of 20 and 104 is resolved.

Thanks a lot for testing this with CUDA @corepointer !

Oh the PR is still in draft state. Further changes planned for this?

Actually it's no longer in draft, maybe I shouldn't put that in the title :)

my bad to jump to conclusions :see_no_evil:

LGTM - ran the test suite once again locally and fine tuned the commit message a bit while merging ;-)
Thx for your efforts @philipportner


[NEW]: French surgeon attempts to sell Bataclan victim's X-ray as NFT

Date
2022-01-22
Description

A senior French surgeon faces legal action and a possible disciplinary charge after attempting to sell an X-ray of a concertgoer who was shot during the 2015 attack on the Bataclan music hall in Paris.
Orthopaedic surgeon Emmanuel Masmejean, who practises at the Georges Pompidou public hospital in south-west Paris, was first reported by the Mediapart website on Saturday (Jan 22) to be selling an image of the X-ray as a digital artwork, without the patient's consent.
The picture shows a forearm containing a Kalashnikov bullet and was on sale for US$2,776 on the OpenSea website, which specialises in so-called NFT digital images.
Asked for comment by Mediapart, Dr Masmejean acknowledged that the sale was "an error" and said he regretted not having sought permission from the patient.
The patient is not identified, but is described as a young woman whose boyfriend was killed in the Bataclan attack, which was part of a wave of shootings and bomb attacks in the French capital by Islamic State in Iraq and Syria gunmen who claimed 130 lives.

all items are quotes pulled from the English article
Links
English article (The Straits Times)
Original French article (Mediapart)
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
No response
Personal link
No response

Thank you! https://web3isgoinggreat.com/?id=2022-01-22-2


Create a new user object in WhosPcRpl if it does not exist yet

This should increase reliability with hopefully no side effects. All user information should be in the WhosPcRpl message and thus creating users at this stage should be safe.

Upon further checks, the user object should be created upon the NamReply message. This change becomes redundant and the original behaviour might even be useful as a bug check.
I'll leave this open for now, it's probably best to investigate the proper chain of messages before acting on this. The issue originally linked had a deeper bug.


Create an 'Instrumentation Joyride'

Feature Request
Currently, the frontend/webstore component doesn't really give people much information about what's actually happening in terms of backend instrumentation. Errors and latency that are induced by failure scenarios simply occur, without much to indicate what's happening or why. To improve the interactivity of the demo environment, and to help draw connections between user interactions and backend services/instrumentation, we should create some sort of joyride (aka, guided tour) to educate users about available dashboards, queries, alerts, etc. being generated by the demo.
Open Questions

How would this interact with BYOC/non-bundled observability backends? We can obviously link into Grafana dashboards we create, but we would also need the ability to swap out those links for forks.
This seems like a pretty big lift, is it worth pursuing?

Oh, this is nice!
Not sure about the amount of effort we would need in here, but I totally agree that we need to improve the scenarios we have in the demo.
When enabling the FF I would expect getting errors, crashes and long response times in the frontend.


ci: Add bugs to project is broken

What

Invalid workflow file: .github/workflows/github-projects-pr.yml#L11
The workflow is not valid. .github/workflows/github-projects-pr.yml (Line: 11, Col: 9): Unexpected symbol: '&'. Located at position 68 within expression: github.event.pull_request.head.repo.full_name == github.repository & github.actor != 'dependabot[bot]'

has been fixed for a while, closing


Unexpected entry type for HD mint key in wallet dump file

Actual behaviour
Current it show as change=1.
Desired behaviour
It should be other value to be able to identify it is HD mint key.
Steps to reproduce
Just invoke dumpwallet RPC and take a look in the output file.

@ultimaweapon, let us know which type you are plan to use. And do not forget fix regression (=

My idea is sigma=1.

Agree


Nil value for packetbeat_version because packetbeat isn't installing first

Getting an agent error when trying to apply this in a packetbeat manifest:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Facter: error while resolving custom fact "packetbeat_version": undefined method `[]' for nil:NilClass
It seems that this is being called before packetbeat is even installed:
https://github.com/corey-hammerton/puppet-packetbeat/blob/3dc3ee3f18f630f6e6479378f3f3c8e50b70d39a/lib/facter/packetbeat_version.rb#L6
Anyone have an idea why this is happening? I'm not an expert at Puppet, but I've gotten the metricbeat module installed using this same method and it works fine without this type of issue.

Facter runs prior applying the manifest. On first-runs this means this fact is null because Packetbeat is not installed yet.


[API] Default group not getting removed after

Description
If I do like this:
user.data().clear();
luckPerms.getUserManager().saveUser(user);
luckPerms.getUserManager().cleanupUser(user);

User still remains visible in the lp editor's database with group.default, happens only if user had group that inherits default group.

I want to delete the user completely. (user is "offline")
Reproduction Steps

Give the user 'vip' group (group that inherits default group).
Using api execute this code (you need to get the offline user and luckPerms):
user.data().clear();
luckPerms.getUserManager().saveUser(user);
luckPerms.getUserManager().cleanupUser(user);
open the lp editor, you should see something like this:

Expected Behaviour
User gets completely wiped out, deleted.
Server Details
git-Purpur-1964 (MC: 1.19.4)*
LuckPerms Version
'net.luckperms:api:5.4' (gradle), 5.4.71 on server
Logs and Configs
No logs.
Extra Details
I want to completely delete and wipe out the user, but with those who have group that inherits default group, it does not work and they still have default group in result and I can't delete it then. I need to delete the user completely, otherwise lp editor users will get trashed up by random users.

Duplicate of #3663


Add Data4Democracy, though it's national?

Yeah, I think it would make sense to add it.
If we don't have it already I think a "national orgs & resources" section would be a good idea.

@owy1 added a link to data for democracy, so closing this.


Add support for segmentio/terraform-docs

Hello,
Now that this issue appears to be resolved, maybe we can run terraform-docs withouth the hacky awk workaround :)

I'm testing this on my fork for few days, but it requires terraform-docs built from master branch.

FYI, I'm the in the process of cutting a RC release of terraform-docs, in the following days.

RC has been released :)
https://github.com/segmentio/terraform-docs/releases/tag/v0.8.0-rc.1


Benefit override outcome recording

When the benefit override flow completes, it should record the outcome of the benefit override in the application itself.
It previously wasn't doing this, but with this PR it will.
The reason I picked this up is because I started work on a feature which would allow the users to remove the applications which are waiting for on the dashboard.

This looks good. As discussed, we should probably add a task to update existing records without an outcome set.

Nice, go for merge once green! :+1:


TypeError  Cannot read property 'split' of undefined

I think it affects https://github.com/sebhildebrandt/systeminformation/blob/b22befe18e46acca8304f67940aeef4695c046a2/lib/users.js#L264-L268
https://sentry.iobroker.net/share/issue/030fa63a272b49ca986041548fb8002d/
TypeError: Cannot read property 'split' of undefined
  File "C:\Program Files\iobroker\SmartHome\node_modules\iobroker.info\node_modules\systeminformation\lib\users.js", line 304, col 49, in null.<anonymous>
    let users = parseWinUsers(data[2].split(/\n\s*\n/));
  ?, in runMicrotasks
  File "internal/process/task_queues.js", line 95, col 5, in processTicksAndRejections

Fixed parsing issues (windows). Version 5.11.5 just released


How to stream video and return them back?

Hello all, (this is a very helpful project. please keep up the good work! :) )
I am currently trying to get hololens's camera stream and receive images from PC side and do a bit of processing and return the result to hololens for viewing.
I have read the documents and tested the unity project but I was wondering if you could give me the gist of how to use webrtc in such a scenario?

Hi- I guess you want to add a local video track to send the PV camera, and on the PC side you want to use an ExternalVideoTrackSource to send back the custom processed video.

I failed to mention that im using the unity integrated version of webrtc.
I believe that ExternalVideoTrackSource is not accessible from unity integration...

It is accessible, but you probably want to use a custom component derived from CustomVideoSource<T> instead for convenience.

I think you answered my old question.
The new question is that customvideosource.cs and scenevideosource.cs in the master branch but not in 1.0.3. version. But the master branch has issue with building unity version library. So, is the custom input not compatible at the moment?

The external video source feature is only available on master indeed.
What's the issue with building the Unity library? I tried recently, this should work. But you need to also build the native plugin and C# assembly from master, because the ones from the NuGet packages are built from the release/1.0 branch and use the old API where the external video source doesn't exist yet. See Building from sources for details. Note that there was a change recently and Microsoft.MixedReality.WebRTC.Native.dll was renamed to mrwebrtc.dll; there is a pending PR to fix some issue left after this rename, maybe that was the issue you hit?