[feature request]Add linkedEditing LSP feature

Typescript already supports linkedEditing(not yet released, but available in v5.1.0-dev.20230409).

This is the server side support, right? coc.nvim already has linkedEditing support, you can enable it by setting coc.preferences.enableLinkedEditing to true.

I tried it, but didn't work. The coc-html works fine. I searched 'linkedediting' in coc-html, and found some relevant  codes. So I think there should be some adaptation work to be done.

Got your point, but that PR is for TypeScript, coc-tsserver is something like https://github.com/microsoft/vscode/tree/main/extensions/typescript-language-features and , let's see how VSCode handle this in typescript-language-features.

From vscode's April iteration plan, this feature will be released in early May. The maintainers of vscode are already working on it: https://github.com/mjbvz/vscode/commit/5babe30cb80fc6754614200017ea26d5fa0f2db7.


Add total_reads to output

I want to filter by the % of alt reads over total reads for a locus, but don't have a total_reads column to look at; supporting_variant_reads and total_variant_reads are both referring to reads with alt.

Fixed by https://github.com/hammerlab/isovar/pull/31


Caves?

Hi again,
Thank you for this repository. Can you do caves? The chunks are empty inside and only generates top area like hills, mountains.

You can use 3D Height Map that generates Caves. but I suppose you are looking for proper world generation something like minecraft. I do plan to add a world generation API that would support biomes and structures but at it's core it's just modifying the blocks array to get what you want. And there are multiple ways to achieve it

Thank  you for the reply.
Right now the inside blocks are all empty like a huge box. How to modify blocks array to have caves?


Fix ansible config of qe server

@dahorak added the reconfiguration you suggested, also I noticed I had a bug in the forks reconfiguration, so this got fixed as well


Fill in Limits Required by Wgpu

Now that wgpu has support for limits, the various gfx-hal backends need to make sure they are filling in at least all the limits required by wgpu. As of right now we max the limits with the default to force a minimum, but this isn't accurate to the hardware.
There is a decent amount of research that has to go into figuring out the exact values for all the backends as some backends (like dx12) some things don't have limits like vulkan does.

I just realized that this issue doesn't actually tell which limits are missing.

So at this point, both DX11 and DX12 are updated, so unless you think metal needs more work, we can close this, at least until GL is re-enabled.


MINOR: Update 3.8 documentation for Kafka Streams

All public interface changes should be briefly mentioned in the
upgrade guide.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ableegoldman @nicktelford @calmera We need to update the documentation based on your KIPs. Mostly I was able to copy the docs from the KIPs, so instead of pinging everyone individually, I did it myself. Feel free to leave comments.


Question x64 triplet

Hi,
I am building all my projects only with x64 platform.
The default one is x86, so every time I need to set my_project:x64-windows or set %VCPKG_DEFAULT_TRIPLET%.
My question is if there is a way to build my project without those both actions - without setting env var or :x64-windows? I've tried
x64-windows but I am not sure how does it works, because there still is "x86" on the paths:
Building package nvml:x86-windows...
-- CURRENT_INSTALLED_DIR=C:/Users/Administrator/Desktop/vcpkg/installed/x86-windows
-- DOWNLOADS=C:/Users/Administrator/Desktop/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=C:/Users/Administrator/Desktop/vcpkg/packages/nvml_x86-windows
And I got:
[...]
C:/Users/Administrator/Desktop/vcpkg/packages/nvml_x86-windows/bin/libpmemlog.dll
Expected x86, but was: x64
Found 2 error(s). Please correct the portfile:
C:\Users\Administrator\Desktop\vcpkg\ports\nvml\portfile.cmake
-- Performing post-build validation done
Error: Building package nvml:x86-windows failed with: POST_BUILD_CHECKS_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: my_project:x86-windows
Vcpkg version: 0.0.81-c5ac9898999b712b7bac2fbc497825882d5e9011

Hi @wlemkows,
First, to reconfirm your issue: you've added libraries to Vcpkg and they only support x64, which currently means that, by default, vcpkg install nvml will fail and you'd like to fix that?
The short answer is that (for now) you should add a check at the top of your portfile that will quickly tell the user that building for x86 is not allowed:
if(NOT VCPKG_TARGET_ARCHITECTURE STREQUAL x64)
  message(FATAL_ERROR "NVML only supports the x64 architecture.")
endif()

We're working on some way to add it to the CONTROL file and detect it even earlier, but that isn't available yet.
Could you expand on why setting %VCPKG_DEFAULT_TRIPLET% doesn't work for you?

Currently I am using solution with FATAL_ERROR message, as you wrote and %VCPKG_DEFAULT_TRIPLET% works fine for me too.
My question was for third solution, to do not ask the user for architecture at all (because we supports only one x64). I thought that  tag in project can resolve the issue, but it won't work too, because CURRENT_INSTALLED_DIR is detected earlier and contains default x86 architecture, right?

I don't think we have a plan to support this now, please use %VCPKG_DEFAULT_TRIPLET% instead currently.


DlpComp-chrisda to Master

Docs Build status updates of commit 3c6961f:
:clock10: Full build: the average full build time is 11 min(s) 49 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 3c6961f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 4f2cdd4:
:clock10: Full build: the average full build time is 11 min(s) 50 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 4f2cdd4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/policy-and-compliance-dlp/Get-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/New-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpCompliancePolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-dlp/Set-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Modified paths to reflect the linux OS.

I'm thinking that, like Charlie said, something along the lines of if $IsWindows = True would be the original paths, and = False would mean Mac or Linux, so should follow the unix file structure.

I am shocked that this script works without any other modifications besides the save paths.  That is completely unintentional.
This is how we can check automatically.
if ($IsWindows) {
$savepath = "c:\scripts"
} else if ($IsLinux) {
$savepath = "/scripts"
}
I'm not going to merge your changes. I will do some testing and then put it in the CognosDefaults-SAMPLE.ps1 using the above logic.

Yeah...  It was a very happy surprise.  I think you could change the if statement though.  I haven't tested it on a Mac (I can if you would like), but it uses the same paths as Linux, so you could probably change the else if to a straight-up else.
Let me know if you want me to do anything else.  I've already got the dependencies installed.

Thanks again for pointing this out. I can not believe this works. I added to the Readme the required dependencies for this and an example of save paths in the CognosDefaults.ps1.


Restore rgh-linkify-features and linkify-code in titles

Fixes #4129
Test URL's
This PR
Linkify issues:
https://github.com/mozilla/addons-linter/pull/76

I checked the listener that has been modified in https://github.com/sindresorhus/refined-github/pull/4089 and it appears to work correctly (i.e. it's run the right number of times)
Also I found which part still uses textContent until it receives the markdown version of the title:

Also I found which part still uses textContent until it receives the markdown version of the title:

Now I see it, is it an issue? Also we need to anyways wait for GitHub to format it since we need it to in <code/>

No, it can be merged as is. This is an issue on GitHub's part. We don't deal with titles anymore. Actually it's best to drop that selector from parse-backticks as soon as possible.

Actually it's best to drop that selector from parse-backticks as soon as possible.

Only .js-issue-title needed to be removed

Are you sure? That selector only matches the conversation title in lists, but conversation titles appear in all sorts of places with different selectors, like the newsfeed, right? We surely have more than one selector

Are you sure? That selector only matches the conversation title in lists, but conversation titles appear in all sorts of places with different selectors, like the newsfeed, right? We surely have more than one selector

We sure do. I thought you wanted me to drop only things related to the title.
If i have time I will do it tomorrow


Feature Request: Support for managing Teams in App Center CLI

It will be very helpful for us to manage Teams in the same way we do Distribution Groups in the App Center CLI. Any info on when that will be available? Thanks!

I'm closing this as a duplicate of https://github.com/microsoft/appcenter-cli/issues/503


Baseline must be a tuple?

I was wondering if forcing the baseline argument to be a tuple is necessary and/or added on purpose in #9210 (https://github.com/mne-tools/mne-python/blob/main/mne/baseline.py#L178). I usually tend to use lists, and this used to work before this change. Now, a tuple is required. @hoechenberger? cf https://github.com/cbrnr/mnelab/issues/381

We always explicitly requested baseline to be a tuple as per the API docs, so I suppose this change you mentioned is just to ensure that the output (in the .baseline attribute) equals the input provided by the user. I think it'd be good to support array-like of length 2 as input and cast to a tuple internally

Yes, I'd also prefer list-like with two elements if there is no strong reason to require a tuple. If everyone agrees I can submit a PR.

Works for me


Not able to force close a channel

I have channels which are inactive for some time, so I tried to clean up:
Trying to force-close:

[ERR] CNCT: ChannelArbitrator(fb34ceae72982ea7f0d485ad2b52b84b8e5b959d8ee83690aad99b3aae4422e4:0): unable to broadcast close tx: unmatched backend error: -26: mempool min fee not met, 545 < 9728 (code 66)

Okay, I think this i a known problem, closing fees have been negotiated some time ago and are not sufficient. But I wonder how I would retry if the fees would drop. Trying to force-close again results in:

2020-09-15 13:44:02.825 [INF] CNCT: Attempting to force close ChannelPoint(fb34ceae72982ea7f0d485ad2b52b84b8e5b959d8ee83690aad99b3aae4422e4:0)
2020-09-15 13:44:02.825 [ERR] RPCS: unable to force close transaction: channel is already in the process of being force closed
2020-09-15 13:44:02.825 [ERR] RPCS: [/lnrpc.Lightning/CloseChannel]: channel is already in the process of being force closed

So how would I convince lnd to try to rebroadcast the closing TX?

The closing transaction will be broadcast on restarts. Also, if any of the channels were using the new anchors protocol, then you could use the bumpclosefee command.

Also the node won't start again, if the fee is still too low :(

[ERR] LTND: unable to start server: unmatched backend error: -26: mempool min fee not met, 3818 < 5592 (code 66)
And in a new run:
unable to start server: unmatched backend error: -26: min relay fee not met, 545 < 15000000 (code 66)

A full log of starting up lnd is nopasted here:
https://nopaste.xyz/?8d3da7c52797ba55#BH92BkihURmSSGWs8hEitrpYpu44HY8sjUPmq6g8DkTe
So no chance of using "bumpclosefee" I guess.

Also the node won't start again, if the fee is still too low :(

Looks like you're setting a high value manually in your bitcoind's config?

a) not repeatedly trying to broadcast the TX, only and restarts which are not to be expected on normal operation

The wallet assumes the backend source will rebroadcast, and in this case bitcoind does rebroadcast it over time.

What network is this on? It's surprising that your wallet tried to use such a low fee.

@Roasbeef It's on bitcoin mainnet. No parameters for minrelaytxfee or blockmintxfee were specified before, but mempool was limited to 3MB.
I see how bitcoind is the right place to look for rebroadcasts, but only if bitcoind accepted the TX in the first place.

but mempool was limited to 3MB.

This causes the issue to happen more often, as the limit will push lower fee transactions out of your mempool. Could you try removing this limit temporarily and restarting lnd?

@wpaulino I changed that as mentioned in https://github.com/lightningnetwork/lnd/issues/4616#issuecomment-693253459 - but still think this is a bug. As my issue is resolved, I'd be fine with closing this issue. Yet I'd still consider it a bug as mentioned above.

Agreed, we should ensure that we're able to start up and log (on the appropriate level) if this happens.

I have a similar issue
lncli closechannel --force c9ad0b642043dc6ebba79bb5512e8f4357797880dc882feb6d87c961ef655eaf 1
[lncli] rpc error: code = Unknown desc = channel not found
2020-10-17 23:49:32.528 [ERR] RPCS: [/lnrpc.Lightning/CloseChannel]: channel not found
my public key is 02e8882bc38ab89963cea0718335e7f33baf79a947590f6b9d80b6ffb4da82795d
https://1ml.com/node/02e8882bc38ab89963cea0718335e7f33baf79a947590f6b9d80b6ffb4da82795d/channels
you can see the txid on the channels.
I have restored my node, but did not back up my channel.back file.

@henhito if you restored your node and haven't restored a channel backup, then there won't be any channels present. If you don't have a channel backup at all and still have funds within the channel, you might be able to use chantools by @guggero to recover them.

thanks @wpaulino I will give that a go.

@Roasbeef @wpaulino we (Breez) had this issue (unmatched backend error) in production today causing our node to be down for a while.
Consider reopening this issue. IMHO, lnd should not stop not startup should be prevented in case a closing TX can't be broadcasted.  Cc: @yaslama

@kingonly could you open a new issue and include some more details (logs especially)? What bitcoind version were you running with? What was the bitcoind error?

@wpaulino It seems that restarting bitcoind helped because the mempool memory was almost empty when lnd retried to broadcast the transaction. This helped lnd to start. But this issue still need to be solved and it's not a new one. Perhaps https://github.com/btcsuite/btcwallet/blob/50978fcf79f8100eb62c185606c66367cc03b03e/wallet/wallet.go#L3463 needs also to be modified to handle the "mempool min fee not met" error received from bitcoind.
In any case, please consider reopening this issue, at least in order to increase the visibility of the workaround: increase the bitcoind mempool max memory using the -maxmempool parameter and/or restart bitcoind.

We're aware of the issue and have plans to address it soon due to the current state of the fee market. Another related issue case is https://github.com/lightningnetwork/lnd/issues/4912.

Gonna close this in favor of https://github.com/lightningnetwork/lnd/issues/7156


adding more support for ephemeral messages

Thank you for opening this repo!
Adding extra support for the chat.postEphemeral workflow which allows us to build posts similar to existing MsgOption... workflow.

Any chance we can get a quick review + merge on this PR? Would be great to have incorporated before year's end :D

This is great @sebito91. Any chance this could be reviewed/merged soon?
Thanks!

@dvdplm mind taking a look now? Reusing the majority of existing PostMessage functionality now.

@sebito91 looks lovely. LGTM.


site24x7_ssl_monitor and timeout

 ~ resource "site24x7_ssl_monitor" "xxx" {
      ~ timeout                   = 30 -> 15
    }

in Terraform we set 15 sec but it's always 30 sec
According API doc I see that timeout is required, but from UI there is no such attribute https://www.site24x7.com/help/api/#ssl-certificate
is it possible that there is problem in API documentation and we don't need to set timeout for SSL monitors?

@azhurbilo Thanks for raising the issue. You don't need to set timeout and it is internally handled for the SSL monitor.


The password provided is not sufficiently secure. Please try again.

Hello,
I was testing the password reset by email.
I tested quite a few possibilities with the instructions provided by Snapp.
First try:
$%vO8r0S9GV84Kr&8gVEVEK#73$MIzu&BpF*7xk1
Second try:
#by%U$!8w6$w8ApmF2i&
And the last try:
cPy%7F^0KKc*rRCe$4n%%aZ@53qG07M&Kxe3OEkibeAJAb
Can you confirm this is a bug or am I the bug? :)

To be completely honest, I should output the symbols included in the regex, as there appears to be a conflict with missing symbols in the 'allowed' set. In your case, the first and second passwords contain #, and the third contains ^, neither of which are permitted by the current regex.
i'm trying to formulate a better regex.

Very weird, I have the same issue with all other tests. Without #, ^.
I realize that none of the passwords work.

i think i found a better regex on regex101, it seems to comply with your password and basically the same requirements:
^(?=.\d)(?=.[A-Z])(?=.[a-z])(?=.[^\w\d])([^\s]){8,}$
https://regex101.com/
let me build <IP_ADDRESS> 😆

At your ease :+1:  Thanks!

yeah, no i mean that it requires 20 minutes, i just launched, and then if you will to try it i would really appreciate.
Also thank you for the massive debugging you took on your shoulder, this kind of feedback helps a lot to improve the app :)

Thank you for your interest in my application: looking forward to hearing your feedback!
i'll also take a look at the blog while waiting the build to complete. 💯

Version <IP_ADDRESS> should be live, and in the meantime, I discovered through your blog that my Proxmox had about 7 unused kernels left on the drive.

Let's go to try the new update :fire:
I discovered through your blog that my Proxmox had about 7 unused kernels
What an invasion! ;)

It was high time for a thorough cleaning. I'm kind of an enthusiast and consider this a hobby, don't judge me. 😆

I am no one to judge you, I am in a bad position. GORGEOUS! I can put whatever password I want.
I am finishing my article as complete as possible to detail all your work. The article will be released at midnight tonight.
Great, that was the last detail that gave me trouble explaining the password reset by email.
1009 words at the moment. I will now complete the tutorial. Thank you for your responsiveness! Moreover, it is specified in the article that it was nice to exchange with an attentive dev.

Thank you so much for your kind words! I'm glad I could help and that everything was clarified. I appreciate the recognition and enjoyed our exchanges as well. Looking forward to reading the article! 🚀

Tonight, midnight. Friendships from Belgium!
Now I find your application perfectly usable! Let's goooOooO!
See you soon :)

Sorry I'm two minutes late. :smile:
https://belginux.com/installer-snapp-avec-docker/
If you have a suggestion or comment, I'm all ears.


Blog light mode style has red subtext

Describe the bug
The blog's subhead styles in light mode appear as if they're error messages at first glance. I assume this is not intentional, given dark mode uses gray text for the subhead:

Reproduction
Visit https://svelte.dev/blog in light mode.
Logs
No response
System Info
MacOS

Severity
annoyance

closing since the site has been rewritten. please file an issue at https://github.com/sveltejs/svelte.dev if the issue persists


Adding some css styles in the page

Hi there,
It would be better to change the styling of the page to make matrix website more attractive. I want to change the alignment of the text, color, font style and want to add some padding. @roannav It would be better if you assign this to me so that I will try to make website more attractive. Please feel free to contact me.

Hi @charmee123,  That would be terrific, if you want to improve the style of the website!  What ideas do you have?  It's currently a dark theme with greenish highlights.   I considered changing the font of the large text to Orbitron - Google Fonts,  but there are other interesting fonts as well.  Please describe in more detail what you would like to do.  Thanks!

Thanks for replying @roannav . I want to change alignment of headings to the center, want to add little bit padding between character name and image so that it can look decent. And it would be also better to move image in the center with little bit of radius in the image. I also thinking to change heading font family to 'Arvo", cursive;'. I have noticed to change these things please let me know your ideas and what you think on these points. Thanks.

Hey @charmee123,   Your ideas sound good to me!  Arvo is an interesting font, better than the current one.   Were you planning to go with an italic or bold version of Arvo?  I'm thinking cursive-handwritten style doesn't match the vibe of the movie though.

Hi @roannav , Arvo bold with 700 font weight will be fine and heading should be written in capital so that it looks little classy.

I like bold and in capital letters.  Sounds great, @charmee123 Looking forward to seeing your changes in the website :smile:   Thank you for your help!

Thanks for assigning the issue @roannav . I am new to open source and it's my first contribution so want to confirm that I need to follow the steps that you have listed in readme file for contribution, right?

@charmee123 Yes, please follow the README.md steps.  They are a common pattern of fork-clone-branch that is done for open source contributions.
Please ask me questions if you run into any problems.
By the way, if you have already done the fork-clone-branch, before 1 hour ago, then you should grab the latest code from the repo, since it has changed in the last hour.
cd matrix-movies-website-hacktoberfest
git checkout main
git pull
git checkout <your-branch-name>
git merge main

This will grab the latest code from the main repo at GitHub and put into your branch on your computer.

If you haven't done the fork-clone-branch yet, then you don't need to do the additional steps.

Hi @roannav, I have modified style sheet and made a pull request (I am not sure if I done it write) Please look it once and merge it. Happy to contribute in this repo 😃

Hi @charmee123,  thank you for all the work you put into improving the design of the website.  It looks awesome!   I especially like the way the main title looks! 🥳


Save/retrieve .AUTHTOKEN in/from user's home directory

Hello there! Thanks a lot, but I believe this won't work on Windows, since Windows doesn't have a HOME environment variable. Source: http://stackoverflow.com/questions/14742064/python-os-environhome-works-on-idle-but-not-in-a-script.
How could we solve this?

Yes, it won't work on Windows. I didn't think of that at first. How about os.path.expanduser('~'), I think it should work fine.


Upgrade AspectJ plugin to 8.10.2

Since it contains a fix for Provider API migration branch.
See https://github.com/freefair/gradle-plugins/pull/1197

@bot-gradle test AST

I've triggered the following builds:

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

Build Scan

The following builds have been cancelled:

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

Build Scan

@bot-gradle test AST

I've triggered the following builds:

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

Build Scan

The following builds have passed:

All Smoke Tests for Pull Request Feedback (Trigger) (Pull Request Feedback)

Build Scan


Revert IBM / Red Hat merging

Until the IBM / Red Hat acquisition is complete, these are still 2
seperate companies. IBM currently does not own Red Hat.
Signed-off-by: Paul Belanger<EMAIL_ADDRESS>

Pull-request updated, HEAD is now 941ec67484356079177b22f0d7ebe996c4cf2d7e

LGTM, but I can't accept this contribution until you've signed the Adobe CLA.

Ah, see that now. Closing / reopening.

Thank you for the PR!


e2e flake: timeout creating a cluster

e2e logs:
00:15:22.641 --- FAIL: TestClusterRestore (168.83s)
00:15:22.641     --- FAIL: TestClusterRestore/restore_cluster_from_backup (0.00s)
00:15:22.641         --- FAIL: TestClusterRestore/restore_cluster_from_backup/restore_from_a_different_name_cluster (51.65s)
00:15:22.641         	util.go:408: 2017-02-12 03:47:42.378348431 +0000 UTC created etcd cluster: test-etcd-qm0wx
00:15:22.641         	util.go:408: 2017-02-12 03:47:42.517843134 +0000 UTC waiting size (3), etcd pods: names ([]), nodes ([])
00:15:22.641         	util.go:408: 2017-02-12 03:47:52.512081966 +0000 UTC waiting size (3), etcd pods: names ([]), nodes ([])
00:15:22.641         	util.go:408: 2017-02-12 03:48:02.513929454 +0000 UTC waiting size (3), etcd pods: names ([]), nodes ([])
00:15:22.641         	util.go:408: 2017-02-12 03:48:12.516104959 +0000 UTC waiting size (3), etcd pods: names ([]), nodes ([])
00:15:22.641         	util.go:408: 2017-02-12 03:48:25.431914888 +0000 UTC waiting size (3), etcd pods: names ([test-etcd-qm0wx-0000]), nodes ([gke-jenkins-default-pool-a62a38df-d715])
00:15:22.641         	util.go:408: 2017-02-12 03:48:33.893625821 +0000 UTC waiting size (3), etcd pods: names ([test-etcd-qm0wx-0000 test-etcd-qm0wx-0001]), nodes ([gke-jenkins-default-pool-a62a38df-d715 gke-jenkins-default-pool-a62a38df-sq0h])
00:15:22.641         	restore_test.go:77: failed to create 3 members etcd cluster: still failing after 6 retries

operator logs:
9:47:42.000
time="2017-02-12T03:47:42Z" level=info msg="creating cluster with Spec (spec.ClusterSpec{Size:3, Version:\"3.1.0\", Paused:false, Pod:(*spec.PodPolicy)(nil), Backup:(*spec.BackupPolicy)(0xc4200c53c0), Restore:(*spec.RestorePolicy)(nil), SelfHosted:(*spec.SelfHostedPolicy)(nil)}), Status (spec.Cluste...
19:48:18.000
time="2017-02-12T03:48:18Z" level=info msg="backup replica set and service created" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:18.000
time="2017-02-12T03:48:18Z" level=info msg="cluster created with seed member (test-etcd-qm0wx-0000)" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:27.000
time="2017-02-12T03:48:27Z" level=info msg="running members: test-etcd-qm0wx-0000" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:27.000
time="2017-02-12T03:48:27Z" level=info msg="cluster membership: test-etcd-qm0wx-0000" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:27.000
time="2017-02-12T03:48:27Z" level=info msg="added member (test-etcd-qm0wx-0001)" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:35.000
time="2017-02-12T03:48:35Z" level=info msg="running members: test-etcd-qm0wx-0000,test-etcd-qm0wx-0001" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:35.000
time="2017-02-12T03:48:35Z" level=info msg="cluster membership: test-etcd-qm0wx-0000,test-etcd-qm0wx-0001" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:35.000
time="2017-02-12T03:48:35Z" level=error msg="fail to add new member (test-etcd-qm0wx-0002): etcdserver: unhealthy cluster" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:35.000
time="2017-02-12T03:48:35Z" level=error msg="failed to reconcile: etcdserver: unhealthy cluster" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:43.000
time="2017-02-12T03:48:43Z" level=info msg="running members: test-etcd-qm0wx-0000,test-etcd-qm0wx-0001" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:43.000
time="2017-02-12T03:48:43Z" level=info msg="cluster membership: test-etcd-qm0wx-0001,test-etcd-qm0wx-0000" cluster-name=test-etcd-qm0wx pkg=cluster
19:48:43.000
time="2017-02-12T03:48:43Z" level=info msg="added member (test-etcd-qm0wx-0002)" cluster-name=test-etcd-qm0wx pkg=cluster

Weird thing:

it took 36s to finish setup() . We need more metrics to better understand what happened.

So I have more clue what caused this.
See https://github.com/coreos/etcd-operator/pull/786#issuecomment-280457489 .
Somehow we have updateStatus() blocking reconciling. Status update has 30s timeout.

We need more metrics. Ref: #737

Too old.. Our code has changed a lot. And some metrics has been added.


GitHub cleanup | accounts + teams

Activity suggestion for codeshare or a dedicated meeting:
Go through our projects, update who is on projects & link to "teams" whenever possible.

Closing because it's been a year with no activity.
This work typically happens ad hoc and in the Engineering Coda


unstableGitUpdater produces version numbers that do not comply with version naming guidelines

Describe the bug
the package naming rules say in no uncertain terms "The version attribute must start with a digit".
however, a very large number of packages do not follow this naming guideline.  almost all of these have a version starting with unstable-.  on one occasion i was even instructed to change a version starting with a digit to a version starting with unstable-
either common practice is wrong, or the documentation is wrong.
my suggested fix would be to tweak the documentation to match common practice: versions must begin with a number, or the string unstable- followed by a YYYY-MM-DD date.

Add a :+1: reaction to issues you find important.

Should be fixed by #280501


taxon restriction "wnt signaling pathway"

never in fungi (have no wnt, or frizzled)
( SGD  and 57 other fungi have one annotation from PAINT)

It is already only in metazoa.

I see annotation in Amigo, presumably that shouldn't happen?


make some doc comments not doc tests

./miri test --doc will run doctests even if we have them disabled (that's a cargo quirk: https://github.com/rust-lang/cargo/issues/13668). This fixes that command to not fail.

@bors r+

:pushpin: Commit 278869b1729e99b140c3b72401773b8799f04088 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 278869b1729e99b140c3b72401773b8799f04088 with merge 7bec2dbcff8d8095b773d39e49d8b6f882fbc44a...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 7bec2dbcff8d8095b773d39e49d8b6f882fbc44a to master...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 7bec2dbcff8d8095b773d39e49d8b6f882fbc44a to master...


lib: remove length field from SharedArrayBuffer

Fixes #40857
I didn't find instructions on adding tests for lib, if a test is required please give me some code pointer, thanks.

It looks like this was intended to go in SharedArrayBufferConstructor, can you please move the declaration down to the next interface? Thanks!

@RyanCavanaugh Looks like if an interface has a new(): T declaration, it will automatically inherits Function can get all Function's properties.
interface Foo {
  value: string;
}

interface FooConstructor {
  new(value: string): Foo;
}

declare const Foo: FooConstructor;
Foo.length; // number

Playground Link
If you need I can type it as 1 to reflect its real value.

@yume-chan can you create a test in tests/cases/compiler/?
You'll need // @lib: es2017 as the first line I think.
Then just use length in the incorrect way and make sure it the baseline generates an .errors.txt file, or if the inherited property means that there's no error, make sure that the .types file has the type you expect.

I found some already existed tests for SharedArrayBuffer in "tests/cases/conformance/es2017/" folder, and strangely, "useSharedArrayBuffer5.ts" and "useSharedArrayBuffer6.ts" have exactly same content.
So I just edited "useSharedArrayBuffer6.ts" to be some new tests.


scripts: west_commands: Remove deprecated west.log

The global state west.log is deprecated, replace with WestCommand logging.
There are still more usages in tree, but those require more effort.

I see nothing wrong but can you please "divide and conquer" this a bit?

I've kept the trivial ones in this PR and will create separate ones for those with a larger "body".

Git conflict now (upvote https://github.com/orgs/community/discussions/4335 )

Ping @marc-hb

Ping @marc-hb

I try to help with west on my "spare time" and I've been spending a significant amount of time already. This API change LGTM but I know nothing about any of the scripts still in this PR. If there's no owner and reviewer for any of these scripts, not even for such a simple change, then I'm afraid these scripts have a maintenance problem bigger than this cleanup?

Ping @marc-hb

I try to help with west on my "spare time" and I've been spending a significant amount of time already. This API change LGTM but I know nothing about any of the scripts still in this PR. If there's no owner and reviewer for any of these scripts, not even for such a simple change, then I'm afraid these scripts have a maintenance problem bigger than this cleanup?

Reviewers are slim for these areas, I appreciate the efforts, but I do understand your argument as well.

@pdgendt, for 4.0 we are only merging bug fixes and doc updates. Can this PR wait till after the release?

@pdgendt, for 4.0 we are only merging bug fixes and doc updates. Can this PR wait till after the release?

Sure


[hmac/dv/xcelium] test fails for hmac=1

when running the hmac test it fails for any seed that sets the hmac=1 parameter
if I manipulate the test to never set hmac=1 the test passes.
the error is a unix interrupt signal being raised
command used:
make TEST_NAME=hmac_sanity SEED=1 SIMULATOR=xcelium
xmsim: *F,SIGUSR: Unix Signal SIGSEGV raised from user application code.

@msfschaffner not sure if changes in the hmac code or system changes on our workstations. but the issue seem to have dissappeared.. which always scares me when that happens without any apparent reason!

That is great news. I recently cleaned up some Xceilum warning. Could be
related to that? https://github.com/lowRISC/opentitan/pull/805
On Mon, Nov 11, 2019 at 3:10 PM rasmus-madsen<EMAIL_ADDRESS>wrote:

@msfschaffner https://github.com/msfschaffner not sure if changes in
the hmac code or system changes on our workstations. but the issue seem to
have dissappeared.. which always scares me when that happens without any
apparent reason!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/241?email_source=notifications&email_token=ACXPOOJFEBACOIGHFYRNJD3QTHQ6HA5CNFSM4IZJLBF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDYOQJI#issuecomment-552658981,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXPOOK4FXBOOTJYR333ZFDQTHQ6HANCNFSM4IZJLBFQ
.

since it's gone, maybe we can close this issue.


Add logo

Please note: This repository is being rebuilt to accept the new volume of token additions and modifications. PR merges will be delayed.

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
This repository is managed using an auto merge action. Please ensure your PR has no deleted lines, and it will be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Auto merge requirements
Your pull request will be automatically merged if the following conditions are met:

Your pull request only adds new tokens to the list. Any modification to existing
tokens will require manual review to prevent unwanted modifications.

Your pull request does not touch unrelated code. In particular, reformatting changes to unrelated
code will cause the auto merge to reject your PR.

Any asset files added correspond to the token address you are adding. Asset files
must be PNG, JPG or SVG files.

Your change is valid JSON and conforms to the schema. If your change failed validation,
read the error message carefully and update your PR accordingly.

No other tokens shares the same name, symbol or address.

For example, this change would be rejected due to unrelated changes:

The bot runs every 60 minutes and bulk-merges all open pull requests to prevent conflicts.
This means that you need to wait up to 60 minutes for your pull request to be merged or reprocessed.

I have same issue ,
Do you have any idea how to fix it ?

No, and can't find anything online. Going to add question to issues

I am also having the same issue.

https://github.com/solana-labs/token-list/pull/11247#issuecomment-1002735975
I found this but didn't work for me

So we need to commit the logo first without json changes then add the json and commit again. Thx for the comment. I'll give it a try and let you guys know.

So we need to commit the logo first without json changes then add the json and commit again. Thx for the comment. I'll give it a try and let you guys know.

Do not have idea how to do
Please let me know if it works for you

added in https://github.com/solana-labs/token-list/commit/c9b052ba03a735bb6558837e1af75402736972f3

So we need to commit the logo first without json changes then add the json and commit again. Thx for the comment. I'll give it a try and let you guys know.

Do not have idea how to do Please let me know if it works for you

Hey @testsystemca,
I believe I find the issue. When you fork the project, go to its directory and install the packages via npm install @solana/spl-token-registry then make your changes like add your token in the JSON array and create a folder then called it with your token address. Add the token logo png inside that folder then move that folder into token-list/assets/mainnet. On this point you can commit your changes and push it. Open a PR. I believe it should work.

So we need to commit the logo first without json changes then add the json and commit again. Thx for the comment. I'll give it a try and let you guys know.

Do not have idea how to do Please let me know if it works for you

Hey @testsystemca,
I believe I found the issue. It's actually my mistake to not install the packages. When you fork the project, go to its directory and install the packages via npm install @solana/spl-token-registry then make your changes like add your token in the JSON array and create a folder then called it with your token address. Add the token logo png inside that folder then move that folder into token-list/assets/mainnet. On this point you can commit your changes and push it. Open a PR. I believe it should work.

So we need to commit the logo first without json changes then add the json and commit again. Thx for the comment. I'll give it a try and let you guys know.

Do not have idea how to do Please let me know if it works for you

Hey @testsystemca,
I believe I find the issue. When you fork the project, go to its directory and install the packages via npm install @solana/spl-token-registry then make your changes like add your token in the JSON array and create a folder then called it with your token address. Add the token logo png inside that folder then move that folder into token-list/assets/mainnet. On this point you can commit your changes and push it. Open a PR. I believe it should work.

Hm I confuse,  where should I run    npm install @solana/spl-token-registry  this  code , could you please send me screenshot if you have it

So we need to commit the logo first without json changes then add the json and commit again. Thx for the comment. I'll give it a try and let you guys know.

Do not have idea how to do Please let me know if it works for you

Hey @testsystemca,
I believe I find the issue. When you fork the project, go to its directory and install the packages via npm install @solana/spl-token-registry then make your changes like add your token in the JSON array and create a folder then called it with your token address. Add the token logo png inside that folder then move that folder into token-list/assets/mainnet. On this point you can commit your changes and push it. Open a PR. I believe it should work.

Hm I confuse, where should I run npm install @solana/spl-token-registry this code , could you please send me screenshot if you have it

You can run that piece of code on your terminal. Open your terminal, cd directory where you clone the project. Mine is on Desktop/SOLTokenList/token-list. You will have different path than mine. Then you can run the code.


Textarea autosize does not work with SSR such as Next.js

Which package has an issue?
@yamada-ui/react
Package Version
1.2.5
Description
When set autosize to Textarea, useAutosize uses getComputedStyle of window, which causes an error in SSR.
Link to Reproduction
No response
Steps to Reproduce

Set autosize to Textarea.
See error

Browser
Chrome
Operating System

[X] macOS
[X] Windows
[X] Linux

Do you know how to fix the issue?
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix?
Yes
Additional Information
No response

@sreeragdas
Sorry, I did #740.


Doesn't seem like it, it relies on os.tmpdir as well and will fall over in the same way v8flags currently does already :/

@tkellen okay, but these are kind of config files, why don't we use a module that stores config files in the user's home directory instead?

That's a fantastic idea. Do you know of any widely used and reliable modules for that?

https://www.npmjs.com/package/configstore is what yeoman uses

derp, that uses yml files, could probably just use https://www.npmjs.com/package/xdg-basedir to get the config directory

Well, unless anyone has any objections, I'm going to publish this and see if it does any better.

(I've updated it to use user-home)

let me review, didn't see the update

Roger.  Just updated the error message.


training

I have used your model and trained with tensorflow style, but when I restored with ckpt file, it can't restore the weights to keras model, could u please tell me how can I train keras model with tensorflow style?

I don't really get why do you want to train keras model with tensorflow style, when you can use original TF repo from paper's authors


vimPlugins.vim-colorschemes have hash mismatch

Steps To Reproduce
:; nix-build -A vimPlugins.vim-colorschemes
these 2 derivations will be built:
  /nix/store/03k8iyms9hadvk2a8csalqhnlr3s7nb3-source.drv
  /nix/store/8ifriy2q0mymvs2iip7pwmziqqd3iqyg-vimplugin-vim-colorschemes-2020-05
-15.drv
building '/nix/store/03k8iyms9hadvk2a8csalqhnlr3s7nb3-source.drv'...

trying https://github.com/flazz/vim-colorschemes/archive/fd8f122cef604330c96a6a6
e434682dbdfb878c9.tar.gz
trying https://github.com/flazz/vim-colorschemes/archive/fd8f122cef604330c96a6a6
e434682dbdfb878c9.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
                                 Dload  Upload   Total   Spent    Left  Speed
100   164  100   164    0     0   1197      0 --:--:-- --:--:-- --:--:--  1205
100   164  100   164    0     0   1197      0 --:--:-- --:--:-- --:--:--  1205
100 1216k    0 1216k    0     0  1547k      0 --:--:-- --:--:-- --:--:-- 2826k
100 1216k    0 1216k    0     0  1547k      0 --:--:-- --:--:-- --:--:-- 2826k
unpacking source archive /build/fd8f122cef604330c96a6a6e434682dbdfb878c9.tar.gz
unpacking source archive /build/fd8f122cef604330c96a6a6e434682dbdfb878c9.tar.gz
hash mismatch in fixed-output derivation '/nix/store/2r0hrjgnhb8nyf5zh0gn8xwyqxa
zrg9f-source':
  wanted: sha256:0kpsf6j20fgblc8vhqn7ymr52v2d1h52vc7rbxmxfwdm80nvv3g5
  got:    sha256:1cg8q7w0vgl73aw1b9zz0zh5vw5d2pm8pm54fhfzva4azg56f416
cannot build derivation '/nix/store/8ifriy2q0mymvs2iip7pwmziqqd3iqyg-vimplugin-v
im-colorschemes-2020-05-15.drv': 1 dependencies couldn't be built
error: build of '/nix/store/8ifriy2q0mymvs2iip7pwmziqqd3iqyg-vimplugin-vim-color
schemes-2020-05-15.drv' failed

This problem seems to no longer exist on master however it is interesting that the hash (and only the hash) has been oscillating between 0kpsf6j20fgblc8vhqn7ymr52v2d1h52vc7rbxmxfwdm80nvv3g5 and 1cg8q7w0vgl73aw1b9zz0zh5vw5d2pm8pm54fhfzva4azg56f416.
Result from git log -L7328,7338:generated.nix on master(f403d1f7913da888ace330636315a766cf6ac5dc)

2021-05-28: (9afcc52f0d2c29a01060050399384c7b23118c30) the plugin was updated to 2020-05-15 and its has was 1cg8....
2021-05-27: (d4de973c917d4bdc74dd2eff3ac027c03a3b3b72) it was changed to 0kps...
2021-06-03: (e317f994d2ffbeaca1bd7b1d6decf942b9c19880) it was changed to 1cg8...
2021-11-12: (af115051b8cb3fed175bdfefca0e95efe76966d2) it was changed to 0kps...
2021-11-16: (2284d771dba1b1ca96059ae9d28effe2da5a13c3) it was changed to 1cg8...
2021-12-15: (2edd8e6c73e79844714915798772c6f4b7b4a9e4) it was changed to 0kps...
2021-12-18: (5dd8c8cb1c1867a8a79bf602c978ba3ec8a4f8fc) it was changed to 1cg8...

(this is concerning)

closing in favour of the linked issue that has more information.


Respect configured log level for startup message

Quick patch that disables the "mock server started" message if logLevel is not set to "info". Feel free to disagree with the implementation, though there should be some option to disable the message. The message could also be more congruent with the Vite logger, but I haven't looked into Vite internals at all and don't know how easy that is.
Thanks for this neat package! Saved me a lot of time ;)

Changing the current default behavior is not a good idea. I added the printStartupLog parameter in version 1.3.0, which you can set to false to disable printing the startup log.


Add Hedgey Finance

Revision checks

[x] Used smart contracts were audited.
[x] Your Safe App include a manifest.json file at the root with the required data.
[x] The app can be loaded as a custom Safe App in the Apps section of https://app.safe.global.
[x] The app auto-connects to the Safe.
[x] You are able to trigger and execute one transaction with a Safe.
[x] RPC requests are optimized (not triggering many requests in a very short time period).

Name/Description

Hedgey Time-Locked Token Distributions
Lock and distribute tokens to one or multiple people with custom parameters
Hedgey Escrowless Token Swaps
Swap your token with any other address for any other token. You pick the parameters and execute it without an escrow
Hedgey Token Distributions to Investors
Distribute time-locked tokens to your investors with custom cliffs and unlock schedules

Type

New additions x3
We have 3 separate apps that are all part of the same codebase.
I wasn't sure if these should be submitted as a single issue or three separate issues.

Compatible Networks
- Mainnet
- Goerli
- Polygon
- Avalanche
- BSC
- Harmony
- Celo
- Boba
- xDai
- Arbitrum
- Optimism
- Evmos
- OEC

Audit document
https://github.com/hedgey-finance/NFT_OTC_Core/tree/main/audits
https://github.com/hedgey-finance/HedgeyDAOSwap/blob/Audit_Added/Hedgey_24082022_SCAudit_Report.pdf
Code for review
https://github.com/hedgey-finance/hedgey-app
App URL

https://app.hedgey.finance/time-locked-token-distributions
https://app.hedgey.finance/escrowless-token-swaps
https://app.hedgey.finance/token-distributions-to-investors

Team information

Project logo: Hedgey Logo
Project landing page: https://hedgey.finance
Team or discord contact: https://discord.gg/7jvvgSgTdz
Twitter link: https://twitter.com/hedgeyfinance
Github link: https://github.com/hedgey-finance

hey, so far everything looks good :) do I get it right that https://github.com/hedgey-finance/hedgey-app is a private repo? if yes, could you please invite me to the repo to do a quick sanity check?

The apps are now live :)


Don't work on mac

Right click menu and search, the search bar don't show the file name.
Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:33:47.663Z (2 wks ago)
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

@zszen
Sorry for the late update. Please upgrade the extension to v0.0.5. It should be working correctly again.


Can I back-propagate the already calculated gradients w.r.t the outputs to all the parameters, and then apply the gradients to the whole network?

I can get the gradients w.r.t the outputs of the network(calculated by python or other ways), Can I just back-propagate the gradients w.r.t the outputs to all the parameters, and then apply them to the whole network?

We recommend posting on Stack Overflow for community-driven support. We try to keep this issue tracker focused on bugs and feature requests.


Create a section to feature our YouTube videos.

Description
Feature our YouTube videos using youtube API.
Channel: https://www.youtube.com/c/SauravMukherjee44/videos
Screenshots
No response

Hey, I want to contribute to it. Can you explain the requirement?

I want to contribute..

@Nainish-Rai Check out the description

@SauravMukherjee44 Kindly assign me so that i can start working on it.

Hey! I want to work on this issue kindly assign me

I am a hacktoberfest 2022 participant. Can u assing this to me??

Hello! I would like to work on this issue. please assign it to me.

Hi! I would like to work upon this issue, I have experience using APIs . I think I can fulfill the above requirement. Can you assign this to me?

heyy!! I have created a section as per description and created a pull request #412
kindly assign it to me @SauravMukherjee44

I would like to contribute to this issue. Can you assign me this?

I would like to work on this project. Please assign it to me.

@SauravMukherjee44 Can u please provide me your channel URL after customizing channel.

@aditi018 Go for it! For support join our discord community: https://discord.com/servers/codein-community-831388874118660156

Channel URL: https://www.youtube.com/c/SauravMukherjee44/videos

Channel URL: https://www.youtube.com/c/SauravMukherjee44/videos

Pull request has been created. You can check it.

I want to contribute to this issue.
Kindly assign me


Add NixOS module: xidlehook

Motivation for this change
xautolock has been unmaintained since 2007 and has bugs.  xidlehook is the new hotness.  This module is intended to be a drop-in replacement for xautolock -- users can just replace all occurrences of xautolock with xidlehook in their configs & be switched over†.
† (And delete nowlocker, which has no counterpart, but was typically just the same thing as locker.)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @WilliButz @Ma27

Release note: Done.
module-list.nix: Done.
Test: Done.
Default in config to avoid documentation rebuilds: Done.
Why uniq?: I added a note.

I don't think that we want to have the drop-in options forever. I haven't found a simple way to mark options as deprecated, but I'd mark those as deprecated (at least by noting this in the description).

I don't want the  xautolock-compatibility options to ever be more-deprecated than xautolock itself is; I want the path from xautolock -> xidlehook-with-compat-options -> xidlehook-trigger-list to be monotonically encouraging.  Also, separately, I have a lot of sympathy for people being busy & not wanting to mess with config that is working for them, & thus I wouldn't mind the xautolock-compatibility options sticking around for many years.  It's a bit weird that xautolock would leave a legacy imprint on xidlehook configuration even after it is long gone, but it doesn't seem terrible.
... Other than the seconds vs. minutes inconsistency in the threshold options.  That part is terrible.  But I feel so excited about making the path from xautolock to xidlehook as smooth as possible that I'm reluctant to introduce even the modest extra step of "Oh, now convert your notify threshold from seconds to fractional minutes (or convert your lock and kill times to seconds) so that they're all in consistent units."  It makes sense to me to defer that churn to later -- maybe along with the removal of the xautolock module after its deprecation.
(Responses to review comments are visible as separate commits here: https://github.com/chkno/nixpkgs/commits/nixos-module-xidlehook-review-responses )
Thanks!


New version: JetBrains.FleetLauncher.Preview version 1.33.90

Created by 🥟 Dumplings in workflow run #4308.
Logs
Updated: 1.33.88 → 1.33.90
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\JetBrains.FleetLauncher.Preview__DefaultSource\fleet.exe returned exit code: 1
Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\fleet.exe returned exit code: 1

(Automated response - build 876.)


An error with launching "run_exploration_mode_ros2.sh"

Hi, I am in trouble with an error with launching "run_exploration_mode_ros2.sh" .
The operation environment is as follow:
1.Autoware PC
OS : Ubuntu 20.04
CPU : Intel Core i9
RMA : 32Gbytes
GPU : NVIDIA GeForce RTX2060 SUPER
2.CARLA PC
OS : Ubuntu 18.04

I would appreciate your cooperation.
Thanks in advance.

I ran into the same error. My workaround was to comment out line 530-532 in the script op_ros2_agent.py:
# check if stack is still running
# if self.stack_process and self.stack_process.poll() is not None:
#        raise RuntimeError("Stack exited with: {} {}".format(
#        self.stack_process.returncode, self.stack_process.communicate()[0]))

@yuting-fu
Thanks for your advice.
I tried. I didn't get any errors, but the process never ended and nothing happened.

@yuting-fu Thanks for your advice. I tried. I didn't get any errors, but the process never ended and nothing happened.

Did you also launch autoware using the launch file or script stated in Hatem's tutorial? The op_ros2_agent.py is only the agent between CARLA simulator and Autoware. The autoware modules (perception, planning, control, etc.) have to be launched in ROS2.
If everything is running properly, you should be able to manually send a routing request in RVIZ and see the car moving automatically along the planned trajectory, just like what Hatem showed in the tutorial video. The autoware might get stuck in initializing state in RVIZ. Then just relaunch everything a couple of times and it will work.
Good Luck.

For everyone who gave me advice
I was able to solve the problem and run.
Thank you.
I changed python version from 3.8 to 3.7.
If I get stuck again, please help me.
Thank you.

Hi @naokiadachi0219 I am facing the same issue could you please take a quick look at my issue: https://github.com/hatem-darweesh/op_bridge/issues/8#issuecomment-1319258106
I had the same issues as you with Python 3.8. However I have accidentally removed it from my system and broke Ubuntu!
I would like to know how did you use Python3.7? In a virtual environment? Could you pass the tutorial you have installed it? And the steps which you took to use successfully to run the script?
Thanks in advance

Hi @marcusvinicius178
Sorry.
I may not be able to meet your expectations.
First , I deployed without using a virtual machine.
I used this tutorial.
https://www.youtube.com/watch?v=EFH-vVxn180
https://www.youtube.com/watch?v=dxwwNacez7o
However, the change in the version is not mentioned in the video.
I changed the version on my own.
Installed in Python3.7,The script is executed in Python3.8.

@marcusvinicius178
Thank you for waiting.
Here are the versions:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05    Driver Version: 520.61.05    CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  On   | 00000000:02:00.0  On |                  N/A |
| 37%   37C    P8     7W / 175W |    308MiB /  8192MiB |      1%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
I hope this helps you.


Callbacks for invited missing

@scambra I noticed that here you have callbacks wrapping the accept_invitation! method. Are you interested in similar callbacks wrapping invite!?
I'd find it useful for something I'm working on, but I realize it's somewhat similar to something like a after_create :callback_method, if: invitation_created_at _not_nil callback on the invitable model. However, I think it would be nice that the callback would be the one true source for running callbacks before and after an invite is sent.
If you're interested, let me know, and I'll open a PR.

nice, I could merge that PR


Obsolete use of CP_ iris and replace by CL_ instead to avoid future clashes?

 Just to avoid bad things happening when the Core Process Ontology (CP) will be registered at OBO :P

These 'CP' terms were created years ago to capture cellular phenotypes.  The CP prefix has never been registered with OBO foundry, nor is there an actual CP ontology, though we once thought of doing one.  In retrospect, this is just an ugly hack, and I agree we should obsolete these terms and replace with terms from a more appropriate source, perhaps PATO.

If they are cellular phenotypes, maybe we should align them with uPheno phenotypes as well? Here three options:

Obsolete all CP terms and replace by fresh CL ids. Apply uPheno patterns instead of the now incompatible bearer-of pattern.
Move CP terms as they are to a new ontology called cellular phenotype ontology. Use uPheno patterns. There are likely to emerge more cellular phenotypes!
Extent CMPO. I am not exactly sure, about worldview and biology issues, but wouldnt this be a more suitable home?

@addiehl @dosumis @simonjupp @cmungall

I'd be happy to split these terms into a separate, imported file - but I don't think this would be a phenotype ontology.
All these terms are GO cell components, subclassed by their qualities, so they might better be considered as extensions to GO CC than phenotypes.  If they were made into phenotypes following uPheno, then they couldn't fullfill their current role in defining cell types  (at least not without a change in axiomatization). The one potentially problematic case is 'increased nucleus size'. - as this appears to be  comparative (and so more phenotype-y?).  However, looking at the definition, I think the chosen quality is wrong:
"A nucleus size quality which is relatively high compared to the amount of cytoplasm present in the same cell."
From this, it sounds like we need a new (categorical) PATO term, something like:
"A quality inhering in a cell whose nuclear volume is relatively high compared to the amount of cytoplasm present in the same cell."
We could then use this to define the CP term, renames as something like 'oversized nucleus'.
@addiehl  - would that make sense to you?
Longer term - maybe they should just be requested as GO terms?

I believe these terms would be most appropriately moved to CMPO, since they all describe cellular phenotypes that are observed via microscopy.
Does anyone actively maintain CMPO?

CMPO isn't in OBO. @matentzn @dosumis do you know if there is interest at EBI in maintaining it?
https://www.ebi.ac.uk/cmpo/
or is this subsumed by upheno? we could just put in as class expressions, no? original constraints due to obof

CMPO isn't in OBO. @matentzn @dosumis do you know if there is interest at EBI in maintaining it?
https://www.ebi.ac.uk/cmpo/
or is this subsumed by upheno? we could just put in as class expressions, no? original constraints due to obof

I think this is up to us. https://github.com/EBISPOT/CMPO has not been updated in a while, we could take it over, or do something else. Whatever works to maintain the concept of "cellular phenotypes" I guess!

I think this is up to us. https://github.com/EBISPOT/CMPO has not been updated in a while, we could take it over, or do something else. Whatever works to maintain the concept of "cellular phenotypes" I guess!

Its not been subsumed by uPheno!

Its not been subsumed by uPheno!

we should think about modularization. is CMPO species neutral? what are its
boundaries with uPheno? Does it automatically subsume e.g. the majority of
FYPO (which is species specific, and inherently all "cellular phenotypes"
by nature of the organism)
On Sat, Jan 16, 2021 at 4:13 AM Nico Matentzoglu<EMAIL_ADDRESS>wrote:

I think this is up to us. https://github.com/EBISPOT/CMPO has not been
updated in a while, we could take it over, or do something else. Whatever
works to maintain the concept of "cellular phenotypes" I guess!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/obophenotype/cell-ontology/issues/572#issuecomment-761553995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOKDCK4WBDZK2PFJF3DS2F7IBANCNFSM4H6VE3OA
.

we should think about modularization. is CMPO species neutral? what are its
boundaries with uPheno? Does it automatically subsume e.g. the majority of
FYPO (which is species specific, and inherently all "cellular phenotypes"
by nature of the organism)
On Sat, Jan 16, 2021 at 4:13 AM Nico Matentzoglu<EMAIL_ADDRESS>wrote:

I think this is up to us. https://github.com/EBISPOT/CMPO has not been
updated in a while, we could take it over, or do something else. Whatever
works to maintain the concept of "cellular phenotypes" I guess!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/obophenotype/cell-ontology/issues/572#issuecomment-761553995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOKDCK4WBDZK2PFJF3DS2F7IBANCNFSM4H6VE3OA
.

My intention was always to submit CMPO to OBO as an uber cellular phenotypes. I tried to keep the modelling as close as possible to uPheno using the SUBQ pattern. We were working with a bunch of phenotype observation from a number of different microscopy datasets that all needed to be annotated with pre-composed terms.  This meant we ended up with some strange terms like this http://www.ebi.ac.uk/cmpo/CMPO_0000378, that isn't a cellular phenotype, but an observation about a bunch of phenotypes in a population of cells. The curators wanted these terms, but I was never really sure about how best to handle these in a pre-composed way.
I once did a little experiment to see how much of FYPO I could classify beneath CMPO - with a bit of axiom rewriting this kind of worked. It would be great to see some or all of CMPO integrated into OBO and properly aligned with uPheno.

My intention was always to submit CMPO to OBO as an uber cellular phenotypes. I tried to keep the modelling as close as possible to uPheno using the SUBQ pattern. We were working with a bunch of phenotype observation from a number of different microscopy datasets that all needed to be annotated with pre-composed terms.  This meant we ended up with some strange terms like this http://www.ebi.ac.uk/cmpo/CMPO_0000378, that isn't a cellular phenotype, but an observation about a bunch of phenotypes in a population of cells. The curators wanted these terms, but I was never really sure about how best to handle these in a pre-composed way.
I once did a little experiment to see how much of FYPO I could classify beneath CMPO - with a bit of axiom rewriting this kind of worked. It would be great to see some or all of CMPO integrated into OBO and properly aligned with uPheno.

I don't think that a phenotype ontology is the right home for these classes.  Some relevant discussion on a closed ticket from late last year: https://github.com/obophenotype/cell-ontology/issues/734#issuecomment-694964148
These terms are used to define various cell types  - they typically refer to entities rather than their qualities, e.g. see basophilic cytoplasm here:
'basophilic erythroblast' EquivalentTo erythroblast
  and ('has part' some 'basophilic cytoplasm')
  and ('has part' some heterochromatin)
  and ('has plasma membrane part' some 'transferrin receptor protein 1')

I think a lot of this can be fixed by having the relevant qualities in PATO.  I already made a ticket for these
'has part' some 'basophilic cytoplasm'
->
'has part' some ('cytoplasm  and 'bearer of' some basophilic) # We could suggest these as types of cytoplasm in GO but a doubt they'd take them.
I already made a ticket for histological qualities in PATO:  https://github.com/pato-ontology/pato/issues/342
Here's the complete list of CP terms:
'acidophilic cytoplasm' http://purl.obolibrary.org/obo/CP_0000027
'banded nucleus' http://purl.obolibrary.org/obo/CP_0000039
'basophilic cytoplasm' http://purl.obolibrary.org/obo/CP_0000028
'cartwheel heterochromatin' http://purl.obolibrary.org/obo/CP_0000043
'increased nucleus size' http://purl.obolibrary.org/obo/CP_0000037
'lobed nucleus' http://purl.obolibrary.org/obo/CP_0000025
'neutrophillic cytoplasm' http://purl.obolibrary.org/obo/CP_0000000
'polychromatophilic cytoplasm' http://purl.obolibrary.org/obo/CP_0000035
'reniform nucleus' http://purl.obolibrary.org/obo/CP_0000040
The only one that sounds like a QE phenotype is 'increased nucleus size', but having looked into what this is used for, I this is better expressed in terms of nuclear/cytoplasmic ratio.  PATO ticket here:
https://github.com/pato-ontology/pato/issues/343. (Nicole has already made a start at adding).

I don't think that a phenotype ontology is the right home for these classes.  Some relevant discussion on a closed ticket from late last year: https://github.com/obophenotype/cell-ontology/issues/734#issuecomment-694964148
These terms are used to define various cell types  - they typically refer to entities rather than their qualities, e.g. see basophilic cytoplasm here:
'basophilic erythroblast' EquivalentTo erythroblast
  and ('has part' some 'basophilic cytoplasm')
  and ('has part' some heterochromatin)
  and ('has plasma membrane part' some 'transferrin receptor protein 1')

I think a lot of this can be fixed by having the relevant qualities in PATO.  I already made a ticket for these
'has part' some 'basophilic cytoplasm'
->
'has part' some ('cytoplasm  and 'bearer of' some basophilic) # We could suggest these as types of cytoplasm in GO but a doubt they'd take them.
I already made a ticket for histological qualities in PATO:  https://github.com/pato-ontology/pato/issues/342
Here's the complete list of CP terms:
'acidophilic cytoplasm' http://purl.obolibrary.org/obo/CP_0000027
'banded nucleus' http://purl.obolibrary.org/obo/CP_0000039
'basophilic cytoplasm' http://purl.obolibrary.org/obo/CP_0000028
'cartwheel heterochromatin' http://purl.obolibrary.org/obo/CP_0000043
'increased nucleus size' http://purl.obolibrary.org/obo/CP_0000037
'lobed nucleus' http://purl.obolibrary.org/obo/CP_0000025
'neutrophillic cytoplasm' http://purl.obolibrary.org/obo/CP_0000000
'polychromatophilic cytoplasm' http://purl.obolibrary.org/obo/CP_0000035
'reniform nucleus' http://purl.obolibrary.org/obo/CP_0000040
The only one that sounds like a QE phenotype is 'increased nucleus size', but having looked into what this is used for, I this is better expressed in terms of nuclear/cytoplasmic ratio.  PATO ticket here:
https://github.com/pato-ontology/pato/issues/343. (Nicole has already made a start at adding).

There are clearly phenotypes in CMPO which look like they could be useful here - e.g. https://www.ebi.ac.uk/ols/ontologies/cmpo/terms?iri=http%3A%2F%2Fwww.ebi.ac.uk%2Fcmpo%2FCMPO_0000117&viewMode=All&siblings=false
But it is not clear to me how we can use terms defined using QE to fill slots in CL defs - whereas the EQ versions clearly do.

There are clearly phenotypes in CMPO which look like they could be useful here - e.g. https://www.ebi.ac.uk/ols/ontologies/cmpo/terms?iri=http%3A%2F%2Fwww.ebi.ac.uk%2Fcmpo%2FCMPO_0000117&viewMode=All&siblings=false
But it is not clear to me how we can use terms defined using QE to fill slots in CL defs - whereas the EQ versions clearly do.

All agreed that we should fix following EQ (not QE) formalism as compound entity - ask described above.

[ ] Add all relevant terms to PATO
[ ] Retofit.

All agreed that we should fix following EQ (not QE) formalism as compound entity - ask described above.

[ ] Add all relevant terms to PATO
[ ] Retofit.

This issue is not solved, but for future reference, i propose to just get rid of the CP namespace for now by incorporating the terms #1311 and you can deal with the issue curation wise as you see fit when you get to it. I just want to move the ID cleanup forward.
So, whoever takes this issue on: the terms, in case #1311 gets merged, now have regular CL ids.

I think we're close to solving it.   Needs:

This PATO issue fixing: https://github.com/pato-ontology/pato/issues/342
(These PATO terms have already been added) https://github.com/pato-ontology/pato/commit/0ac2938138d4c8faeccf245d09bc78e14520844e)

Updates to CL terms that reference CP terms to change to compound entity reference.

Actually - we might have most of the PATO terms already (I think they need to be moved, but that's a secondary issue)

So all 10 CP terms will be obsoleted?

@shawntanzk  - can you have a go at quickly cleaning this up.
Example:
acidophilic cytoplasm
is used to defined these terms:

Each should be changed to:
has_part some (cytoplasm and 'bearer of'* some PATO:acidophilc) ...

Added to agenda for tomorrow's CL call

I'll hold off making changes on this till after tomorrow's CL call discussing this - don't want to break OBO products before discussing how to handle it

might also need a PATO release after new terms gets passed to fully complete this


Multiple keybase volumes showing up in finder with KBFS

Keybase GUI Version: 1.0.14-20160303170019+d7c1ca4
I just noticed this today. Multiple keybase volume entries being created in OS X Finder. I have noticed the GUI client fail at login a couple of times over the last few days, presumably when doing and auto-update.  May be related.

Looks like duplicate of https://github.com/keybase/client/issues/2169
Sorry.  Will try to remove and update as suggested there.

A meta-meta duplicate

I removed finder shortcuts after quitting keybase client, and then running keybase update client.
@maxtaco I no longer have duplicates.  But I also don't have any keybase volume shortcut in the finder either.
Expected?

Expected, we've had to postpone that feature.  CC: @gabriel

ok, will close this issue.  Thx.


guide curve conversion

Unfortunately, with the latest commit 814a55b046fcabc4c3c19c38ad2dca6a70285eab, this PR depends on DLR-SC/tixi@a581bdf64a48f70a53142c335ad84ff4c3f517da (resp. the PR DLR-SC/tixi#114). So once the tixi-PR is merged we need to update the conda packages again before we merge this PR.


Apply time calib simtel

This is a follow up to #1463
Here, I get the required time shift from the simtel laser calibration object and fill it appropriately into the dl1 calibration container.
I simulated flat field events using simtelarray prod5 la palma baseline, on 100 flat field events (times 19 telescopes) the standard deviation of the pulse time goes from 0.56 to 0.15 ns, using this simple script:
from ctapipe.io import SimTelEventSource
from ctapipe.calib import CameraCalibrator
from ctapipe.image.extractor import LocalPeakWindowSum
from collections import defaultdict
import numpy as np
from ctapipe.containers import EventType

path = '../simtel_prod5/Data/sim_telarray/cta-prod5-lapalma/0.0deg/Data/gamma_20deg_180deg_run4___cta-prod5-lapalma_desert-2158m-LaPalma-dark.simtel.zst'

source = SimTelEventSource(path, skip_calibration_events=False)
calib = CameraCalibrator(source.subarray, image_extractor=LocalPeakWindowSum(source.subarray))

times = []

for e in source:
    if e.trigger.event_type != EventType.FLATFIELD:
        continue

    calib(e)
    for tel_id, dl1 in e.dl1.tel.items():
        times.append(dl1.peak_time)

times = np.array(times)

print(np.std(times - np.mean(times, axis=1)[:, np.newaxis]))

On the master:
0.5593064

Here:
0.15312754

should this be optional?

should this be optional? Or rather: should maybe the hole time shift business in the CameraCalibrator be optional?

I guess it's good to check if we should be applying this to MCs or not: are they really simulated with a distribution of times per pixel or module? or is this just a measure of the uncertainty due to discrete sampling? (in the second case, I think you would not want to subtract it, since it's statistical not systematic)

@kosack No this is not the question. We checked the docs of simtel array, see discussion here #1463.
It is correct and should always be correct. Might be nice to be able to disable this correction (in general, not just for the simtel event source) though.

I support an option (via trait) to turn off the shifting entirely

I'm hesitant to approve this without some benchmarking to demonstrate its impact. I am also curious why it hasn't previously been used in other analysis chains...

The simple check is that the std of the peak times got a lot smaller (from 500 to 150 ps).
I think applying this correction is the correct thing to do, it is certainly intended this way by sim_telarray.
The question as always then remains how realistic the current values in the simulation are for the telescopes, but this we can only find out by comparing to observed data.
@GernotMaier Do you apply this correction in EventDisplay?

@watsonjj the corrections can now be disabled using the boolean options introduced in #1492


how to set CPM_DOWNLOAD_ALL?

I'm a new in cmake and cpm.
I don't know where to set it.
I don't know how to set it.
I just wanna reuse sources and builds.
readme.md does not cover all caes I don't know.
So would you explain it to me?Thank you.

Thank you,I'll have a try


Link vscode extension in kedro docs and website

[x] https://github.com/kedro-org/kedro-website/issues/190
[ ] https://github.com/kedro-org/kedro/pull/3898

Opened a new one for kedro-website: https://github.com/kedro-org/kedro-website/issues/190
A PR on kedro: https://github.com/kedro-org/kedro/pull/3898

The PR in kedro's repo is now merged. There is already a separate issue for kedro-website, can this issue be closed?

Both PRs have been merged indeed, closing!


chore: remove log rocket

Not sure it's worth the wor. It's just an extra data-private on some HTML tags and we might use it again if we implement another solution like sentry or posthog
Until cloud is on 1.5.x we are going to need two branches, we sync them regularly though
Should be fixed not :+1:


Is there  plane segmentation  result ?

I tried the demo, the plane seems well segmented, like walls, windows, cainets etc. I'm wondering is there any plane segmentation result from SUNCG or mattport3d data.

@huangkuns can you clarify what you mean by plane segmentation? Do you mean the semantic segmentation mask indicating category labels for the objects?

@msavva  Thanks for replying. By plane/surface segmentation, I mean areas that  belong to the same plane/surface. For example, windows/doors are on the same plane as one side of wall. Ceiling and wall are on two orthogonal plane.

We do not currently have a plane segmentation mode.  However, you can probably use the surface normal sensor to extract planar segments.  You can enable this sensor by using the --sensor normal command line argument, or by manually setting normal: True in the observations parameter.

@huangkuns did this information answer your question? If so, let's mark the issue as resolved.

Please re-open issue if additional information is required.


Collapsing update requests in the Consumer leads to update reordering

Requests picked up from the incoming Kafka queue are processed in KafkaCrossDcConsumer.pollAndProcessRequests. In case of UPDATE requests before they are sent to the target Solr they are first "collapsed", i.e. data from multiple update requests is appended to a single outgoing UpdateRequest, as long as other request parameters match the first request.
However, this must lead to reordering of updates, because Solr always processes all "add" ops first when processing an UpdateRequest. The original ordering of incoming ops is lost in the single collapsed outgoing request.
Imagine the following scenario:

Input:

add(A), add(B)
del(A)
add(A') // modified A with the same id
End result: A', B

Collapsed output:

add(A), add(B), add(A')
del(A)
End result: B

Perhaps in some environments this is very unlikely to happen but cannot be assumed to work in general. I propose to add an option to turn it off, set to OFF by default.

One possible way to address this would be to accumulate the add ops only until we encounter any delete op. At this point we first emit the accumulated request with add-only ops, and then keep sending individual requests (without collapsing) as long as they have any delete ops. Then on the first pure add-only request we switch back to accumulating.

Fixed in PR #97 .


[doc] Fix a param name in DisplayServer's global_menu_add_multistate_item()

Heh, I noticed that one, but thought that it may be worth do get a few of those together. The ones that require changing the binding code lines as well as the docs.

😄 I mentioned it in #64331 - I just didn't want to forget it.
While we're talking about the binding stuff - we have mentioned at least three things that should probably be added to the guidelines:

index vs. idx
arg_name vs. argname
consistent use of enable/disable throughout (or enabled/disabled if you so choose)

The guidlines also need to be updated for [param foo] and [constant bar].

Yeah, guidelines and the BBCode reference need some updating to include a few of the newer things.
Regarding the naming standards, we'll need to discuss this with other maintainers to confirm the rules, though there was at least some support for moving away from shortened names.

at least some support for moving away from shortened names.

Hopefully it will be more than some support!
In the very first paragraph:

Users come from all around the world. Some of them are young, and many aren't native English speakers. That's why we must all write using a clear and a common language.

😄

Closing, as this change already is in master/4.0. Thanks for contributing!


Change provider_config.server_name priority

I think env[:machine].provider_config.server_name should be prior than env[:machine].name. This is becase server_name description is documented in README.md. So, ordinay people (me!) are expexted to set server name with this option.

Sure.  Thanks!


throttle api

Laravel Version: Laravel Framework 8.11.2
PHP Version: 7.4
Database Driver & Version:

Jetstream / Inertia
Description:
    protected $middlewareGroups = [
        'api' => [
            EnsureFrontendRequestsAreStateful::class,
            'throttle:api',
            \Illuminate\Routing\Middleware\SubstituteBindings::class,
        ],
    ];

by default throttle:api enabled in api section. When I doing axios.get(/api/user) or any other api route, I got answer delay 3-4 sec and huge load on server (CPU) even if I request this route 1 time per 3 sec. Even if in route just closure which return immediatly.
Route::middleware('auth:sanctum')->get('/user', function (Request $request) {
    return 1;
});

Why this happens? If I disabling 'throttle:api' - all works fine and I got answer from endpoint in 80-100ms

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


BGR vs RGB error when creating image for iOS inference?

https://github.com/csharpseattle/tensorflowiOS/blob/17101b75dec2b8b53496a3e45878f86e53f3b32a/objC/Tensorflow/TensorflowGraph.mm#L298
Tensorflow trains using images based on the image pixel tuples being in Blue/Green/Red (BGR) order. But on iOS the image pixel buffer at this point is in Red/Green/Blue (RGB) order. And this code is just copying straight over. So reds are being converted to blues and vice versa before inference is being run on the pixels.
I started having better accuracy on my iPhone when I changed this to copy red-to-red and blue-to-blue like this:
destPixel[tensorChannels - c - 1] = srcPixels[c];

Interesting find.   I request a BGR Pixel Buffer in CameraPreviewView but a increase in accuracy is always welcome.
 NSDictionary *newSettings = @{ (NSString *)kCVPixelBufferPixelFormatTypeKey :@(kCVPixelFormatType_32BGRA) };
I'll take a look and report back.

Hmm, ok you might be right. I've heavily changed this code and stopped
using the camera in my use case, instead relying on images from the Photo
Library. So now you have me pretty much convinced that the bug is in my
code where I'm reading in images in RGB order though the code implicitly
assumed BGR. I'll dig further on my end.
On Wed, Sep 26, 2018 at 1:31 PM CSharp<EMAIL_ADDRESS>wrote:

Interesting find. I request a BGR Pixel Buffer in CameraPreviewView but a
increase in accuracy is always welcome.
NSDictionary *newSettings = @{ (NSString
*)kCVPixelBufferPixelFormatTypeKey :@(kCVPixelFormatType_32BGRA) };
I'll take a look and report back.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/csharpseattle/tensorflowiOS/issues/10#issuecomment-424822666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Am1lujXYaFLEQsikBA6cJHl5lKLS74Fxks5ue8fsgaJpZM4W7Oex
.

I am aware of a case where the copy you refer to might not be entirely correct.  Ideally there would be a selective copy of pixel based on the orientation of the pixel buffer.  I think this comes into play when you start in landscape and rotate to portrait.  What really should happen is a square around the center of the buffer should be copied so that there is no distortion of the image going into the model.
However, I believe this is a different bug and not what your are seeing.  Might improve accuracy though.

Sorry for the false report. Mea culpa. I now see that the code is using BGR options on the camera. And several comments in the code that make this clear. I'm 100% positive that the problem is me passing RGB images to a function that expects BGR. Thus I'm closing this since the onus is on me to pass the images as BGR to this code.


Failure due to a shape mismatch by inference.py

I executed the following command in a container created from the provided Dockerfile:
micromamba run -n diffdock python -m inference --config default_inference_args.yaml --protein_ligand_csv data/testset_csv_2.csv --out_dir results/user_predictions_small

The testset_csv_2.csv used for inference contains the following data:

complex_name,protein_path,ligand_description,protein_sequence
0,data/PDBBind_processed/6qqw/6qqw_protein_processed.pdb,data/PDBBind_processed/6qqw/6qqw_ligand.mol2,

In addition, I've made a modification to the inference_utils.py script to ensure proper handling of the complex_name column in the CSV file. Initially, I encountered an error when the complex_name values were integers. To resolve this, I edited the line 159 in inference_utils.py to labels.extend([str(complex_names[i]) + '_chain_' + str(j) for j in range(len(s))]).
However, I encountered a tensor shape mismatch error during the computation, as detailed in the output below:

DiffDock will run on cuda
Generating ESM language model embeddings
/home/appuser/micromamba/envs/diffdock/lib/python3.9/site-packages/torch/cuda/init.py:155: UserWarning:
NVIDIA H100 80GB HBM3 with CUDA capability sm_90 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_70 sm_75 sm_80 sm_86.
If you want to use the NVIDIA H100 80GB HBM3 GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/
Processing 1 of 1 batches (2 sequences)
HAPPENING | confidence model uses different type of graphs than the score model. Loading (or creating if not existing) the data for the confidence model now.
/home/appuser/micromamba/envs/diffdock/lib/python3.9/site-packages/torch/jit/_check.py:181: UserWarning: The TorchScript type system doesn't support instance-level annotations on empty non-base types in __init__. Instead, either 1) use a type annotation in the class body, or 2) wrap the type in torch.jit.Attribute.
Size of test dataset:  1
0it [00:00, ?it/s]@> 6214 atoms and 1 coordinate set(s) were parsed in 0.03s.
/home/appuser/DiffDock/datasets/parse_chi.py:91: RuntimeWarning: invalid value encountered in cast
Y = indices.astype(int)
@> 6214 atoms and 1 coordinate set(s) were parsed in 0.03s.
Failed on tensor([0]) shape mismatch: value tensor of shape [196] cannot be broadcast to indexing result of shape [88]
1it [00:00,  1.62it/s]
Failed for 1 complexes
Skipped 0 complexes
Results are in results/user_predictions_small

I'm seeking help to resolve the tensor shape mismatch issue. Any advice on how to adjust the input data or modify the inference settings to prevent this error would be greatly appreciated.
Thank you for your support!

Hi @yukisoya could you check whether the issue is still there with the fixes of the recent commits?

Dear Gabriele,
I hope this message finds you well. I am encountering issues while running the DiffDock-L model, which seem similar to the problem described in Issue #189. Below is a summary of the errors I am facing:
/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/site-packages/torch/cuda/init.py:155: UserWarning:
NVIDIA H100 with CUDA capability sm_90 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_37 sm_50 sm_60 sm_70 sm_75 sm_80 sm_86.
If you want to use the NVIDIA H100 GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/
warnings.warn(incompatible_device_warn.format(device_name, capability, " ".join(arch_list), device_name))
^M0it [00:00, ?it/s]/home/aolgac/Programs/DiffDock/datasets/parse_chi.py:91: RuntimeWarning: invalid value encountered in cast
Y = indices.astype(int)
--- Logging error ---
Traceback (most recent call last):
File "/home/aolgac/Programs/DiffDock/inference.py", line 260, in main
data_list, confidence = sampling(data_list=data_list, model=model,
File "/home/aolgac/Programs/DiffDock/utils/sampling.py", line 108, in sampling
crop_beyond(batch, tr_sigma * 3 + model_args.crop_beyond, model_args.all_atoms)
File "/home/aolgac/Programs/DiffDock/utils/utils.py", line 405, in crop_beyond
subgraph(residues_to_keep, complex_graph['receptor', 'rec_contact', 'receptor'].edge_index, relabel_nodes=True)[0]
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/site-packages/torch_geometric/utils/subgraph.py", line 105, in subgraph
node_idx[subset] = torch.arange(subset.sum().item(), device=device)
RuntimeError: shape mismatch: value tensor of shape [217] cannot be broadcast to indexing result of shape [133]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 1083, in emit
msg = self.format(record)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 927, in format
return fmt.format(record)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 663, in format
record.message = record.getMessage()
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 367, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/aolgac/Programs/DiffDock/inference.py", line 318, in
File "/home/aolgac/Programs/DiffDock/inference.py", line 302, in main
logger.warning("Failed on", orig_complex_graph["name"], e)
Message: 'Failed on'
Arguments: (['1a0q'], RuntimeError('shape mismatch: value tensor of shape [217] cannot be broadcast to indexing result of shape [133]'))
^M1it [00:00,  1.71it/s]--- Logging error ---
Traceback (most recent call last):
File "/home/aolgac/Programs/DiffDock/inference.py", line 260, in main
data_list, confidence = sampling(data_list=data_list, model=model,
File "/home/aolgac/Programs/DiffDock/utils/sampling.py", line 116, in sampling
tr_score, rot_score, tor_score = model(mod_complex_graph_batch)[:3]
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1194, in call_impl
return forward_call(*input, **kwargs)
File "/home/aolgac/Programs/DiffDock/models/cg_model.py", line 318, in forward
rec_edge_index, rec_edge_attr, rec_edge_sh, rec_edge_weight = self.embedding(data)
File "/home/aolgac/Programs/DiffDock/models/cg_model.py", line 290, in embedding
rec_node_attr = self.rec_emb_layers[l](rec_node_attr, data['receptor', 'receptor'].edge_index, edge_attr, rec_edge_sh, edge_weight=rec_edge_weight)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/aolgac/Programs/DiffDock/models/tensor_layers.py", line 311, in forward
raise ValueError("No edges and no nodes")
ValueError: No edges and no nodes
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 1083, in emit
msg = self.format(record)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 927, in format
return fmt.format(record)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 663, in format
record.message = record.getMessage()
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 367, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/aolgac/Programs/DiffDock/inference.py", line 318, in
main(_args)
File "/home/aolgac/Programs/DiffDock/inference.py", line 302, in main
logger.warning("Failed on", orig_complex_graph["name"], e)
Message: 'Failed on'
Arguments: (['1a0q'], RuntimeError('shape mismatch: value tensor of shape [217] cannot be broadcast to indexing result of shape [133]'))
^M1it [00:00,  1.71it/s]--- Logging error ---
Traceback (most recent call last):
File "/home/aolgac/Programs/DiffDock/inference.py", line 260, in main
data_list, confidence = sampling(data_list=data_list, model=model,
File "/home/aolgac/Programs/DiffDock/utils/sampling.py", line 116, in sampling
tr_score, rot_score, tor_score = model(mod_complex_graph_batch)[:3]
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1194, in call_impl
return forward_call(*input, **kwargs)
File "/home/aolgac/Programs/DiffDock/models/cg_model.py", line 318, in forward
rec_edge_index, rec_edge_attr, rec_edge_sh, rec_edge_weight = self.embedding(data)
File "/home/aolgac/Programs/DiffDock/models/cg_model.py", line 290, in embedding
rec_node_attr = self.rec_emb_layers[l](rec_node_attr, data['receptor', 'receptor'].edge_index, edge_attr, rec_edge_sh, edge_weight=rec_edge_weight)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
return forward_call(*input, **kwargs)
File "/home/aolgac/Programs/DiffDock/models/tensor_layers.py", line 311, in forward
raise ValueError("No edges and no nodes")
ValueError: No edges and no nodes
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 1083, in emit
msg = self.format(record)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 927, in format
return fmt.format(record)
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 663, in format
record.message = record.getMessage()
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/logging/init.py", line 367, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/aolgac/Softwares/venvs/diffdock/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/aolgac/Programs/DiffDock/inference.py", line 318, in
main(_args)
File "/home/aolgac/Programs/DiffDock/inference.py", line 302, in main
logger.warning("Failed on", orig_complex_graph["name"], e)
Message: 'Failed on'
Arguments: (['1a0q_custom'], ValueError('No edges and no nodes'))
^M2it [00:01,  1.92it/s]^M2it [00:01,  1.89it/s]
[2024-Nov-28 13:17:40 CET] WARNING -
Failed for 2 / 2 complexes.
Skipped 0 / 2 complexes.
I have verified that my installation aligns with the guidelines provided in the DiffDock documentation, but the errors persist.
Moreover, I noticed that a similar problem was reported in Issue #237, particularly the "No edges and no nodes" error, which might be related.
I am currently using an NVIDIA H100 GPU (sm_90) with DiffDock 1.1.3.
Would you be able to confirm whether these errors might share the same underlying cause as described in this issue? If so, could you provide guidance on resolving them or point to any recent updates addressing similar problems?
Thank you for your time and support. I appreciate your efforts in developing and maintaining this excellent solution. I would like to mention that I have achieved remarkable results using DiffDock in my research. Its capabilities have significantly contributed to my work, and I am currently preparing manuscripts that I hope to publish soon. Thank you for creating such an impactful tool for the community!


compinit:473: bad output format specification

I am getting following error which comes before 3-4 days.. any guess??
compinit:473: bad output format specification

Can you give us more information on this?

When does it happen? Does it happen during zsh startup?
What operating system are you running?
Is anything else breaking?

Yes, it happens when zsh starts
OS: Linux Mint 14
oh-my-zsh not working properly. if i remove oh-my-zsh, zsh works well without error(compinit:473: bad output format specification).

Try deleting ~/.zcompdump* files and restarting the terminal.

mcornella, it's working.. Thank you.

Great! Remember to close this issue.


Notebook outputs

This adds support for browsing notebooks outputs as data https://github.com/jupyterlab/jupyterlab-data-explorer/issues/16

I am going to merge this and open a few new issues for errors, https://github.com/jupyterlab/jupyterlab-data-explorer/issues/33, https://github.com/jupyterlab/jupyterlab-data-explorer/issues/34, https://github.com/jupyterlab/jupyterlab-data-explorer/issues/35,
https://github.com/jupyterlab/jupyterlab-data-explorer/issues/36


chart: Autodiscover master nodes

Pull Request

[X] Make sure you have followed Kube-OVN Code Style.

What type of this PR
Examples of user facing changes:

Features

This PR introduces automatic discovery for MASTER_NODE nodes and calculates their correct number.
Thus if MASTER_NODES unspecified Helm will take internal IPs of nodes with kube-ovn/role=master label.
Specifying replicaCount parameter will make no effect since now
Which issue(s) this PR fixes
Fixes #(issue-number)
WHAT
copilot:summary
copilot:poem
HOW
copilot:walkthrough

Makefile targets kind-install-chart and kind-upgrade-chart should be updated.

@zhangzujian thanks for pointing out, PR rebased