Resolve gradient mismatches in benchmarks

For several utilities, benchmarking suggests that different backends given different gradients. This should be investigated as it may indicate performance issues.

Is the difference between all options or is Zygote the outlier? Reverse diff with compiled tape is known to have these problems with logical branches in the code.

That makes sense... The improvement path here is track down the "wrong" branch(es) that are getting compiled.

z

Where is this benchmark?

I think we can also use instabilities in our benchmarks (i.e https://github.com/CDCgov/Rt-without-renewal/pull/400#issuecomment-2250988929) to indicate where problems are. It would be useful to think if there is a more formal way of checking this that requires less tracking across PRs.
(i.e here it suggests that observation error models are problematic).

#414 localised some issues to the NegativeBinomialError model. It would be good to investigate this further to see if it common across all error models or just the negative binomial.
See: https://github.com/CDCgov/Rt-without-renewal/pull/414#issuecomment-2263521390

Running some more repititions I see the following throwing gradient issues (due to compiled reverse diff):

Warnings from Model{typeof(generate_observations), (:obs_model, :y_t, :Y_t), (), (), Tuple{Ascertainment{NegativeBinomialError{HalfNormal{Float64}}, AbstractTuringLatentModel, var"#88#89", String}, Vector{Int64}, Vector{Int64}}, Tuple{}, DefaultContext}(EpiAware.EpiAwareBase.generate_observations, (obs_model = Ascertainment{NegativeBinomialError{HalfNormal{Float64}}, AbstractTuringLatentModel, var"#88#89", String}(NegativeBinomialError{HalfNormal{Float64}}(HalfNormal{Float64}(μ=0.01)), PrefixLatentModel{FixedIntercept{Float64}, String}(FixedIntercept{Float64}(0.1), "Ascertainment"), var"#88#89"(), "Ascertainment"), y_t = [100, 100, 100, 100, 100, 100, 100, 100, 100, 100], Y_t = [100, 100, 100, 100, 100, 100, 100, 100, 100, 100]), NamedTuple(), DefaultContext()):
┌ Warning: `ad.compile` where `ad` is `AutoReverseDiff` has been deprecated and will be removed in v2. Instead it is available as a compile-time constant as `AutoReverseDiff{true}` or `AutoReverseDiff{false}

Warnings from Model{typeof(generate_observations), (:obs_model, :y_t, :Y_t), (), (), Tuple{Ascertainment{NegativeBinomialError{HalfNormal{Float64}}, AbstractTuringLatentModel, var"#82#83", String}, Vector{Int64}, Vector{Int64}}, Tuple{}, DefaultContext}(EpiAware.EpiAwareBase.generate_observations, (obs_model = Ascertainment{NegativeBinomialError{HalfNormal{Float64}}, AbstractTuringLatentModel, var"#82#83", String}(NegativeBinomialError{HalfNormal{Float64}}(HalfNormal{Float64}(μ=0.01)), PrefixLatentModel{FixedIntercept{Float64}, String}(FixedIntercept{Float64}(0.1), "Ascertainment"), var"#82#83"(), "Ascertainment"), y_t = [100, 100, 100, 100, 100, 100, 100, 100, 100, 100], Y_t = [100, 100, 100, 100, 100, 100, 100, 100, 100, 100]), NamedTuple(), DefaultContext()):

Warnings from Model{typeof(generate_observations), (:obs_model, :y_t, :Y_t), (), (), Tuple{Ascertainment{NegativeBinomialError{HalfNormal{Float64}}, AbstractTuringLatentModel, var"#64#65", String}, Vector{Int64}, Vector{Int64}}, Tuple{}, DefaultContext}(EpiAware.EpiAwareBase.generate_observations, (obs_model = Ascertainment{NegativeBinomialError{HalfNormal{Float64}}, AbstractTuringLatentModel, var"#64#65", String}(NegativeBinomialError{HalfNormal{Float64}}(HalfNormal{Float64}(μ=0.01)), PrefixLatentModel{FixedIntercept{Float64}, String}(FixedIntercept{Float64}(0.1), "Ascertainment"), var"#64#65"(), "Ascertainment"), y_t = [100, 100, 100, 100, 100, 100, 100, 100, 100, 100], Y_t = [100, 100, 100, 100, 100, 100, 100, 100, 100, 100]), NamedTuple(), DefaultContext())

Warnings from Model{typeof(generate_observations), (:obs_model, :y_t, :Y_t), (), (), Tuple{NegativeBinomialError{HalfNormal{Float64}}, Vector{Float64}, Vector{Float64}}, Tuple{}, DefaultContext}(EpiAware.EpiAwareBase.generate_observations, (obs_model = NegativeBinomialError{HalfNormal{Float64}}(HalfNormal{Float64}(μ=0.01)), y_t = [10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0], Y_t = [10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0, 10.0]), NamedTuple(), DefaultContext())

Something of a pattern I think! Running a few more and will summarise a bit more clearly than this once done.

I think with #442 and #415 these are now all handled so closing.


Atom uploading user data without explicit permission

Hi
It seems like atom is sending "crash" data from my system to an online system without me configuring it to.
I think that is a vulnerability. There should be settings for a user to either accept or reject data being
sent to an online system. I should also be able to see what is being sent. I cannot find any in atom.
/Applications/Atom.app/Contents/Frameworks/Electron Framework.framework/Resources/crashpad_handler --database=/tmp/Atom Crashes --url=http://<IP_ADDRESS>:1127/post --handshake-fd=41

There was a recent discussion about Atom’s EULA here :point_down: and it mentions how Atom sends data to our servers:
https://github.com/github/legal/pull/542/files#diff-21816317faa283273c70717397bdce9aR26
In the meantime, I will ask the team if there's a way to disable this in any way (such as building Atom from source yourself) and label this issue as an enhancement.

Am appauled that you are callous enough to simply dismiss the issue as "read the eula" and then close the issue.
I should be asking myself why the heck am i using atom in the first place with this kind of nonchalant attitude to user data.

@akissa Sorry, the issue was closed by mistake (that happens) and we just wanted to explain that it's something we want to communicate more clearly in an EULA in the future. Not trying to be dismissive here -- thanks for bringing this up. I do think it would be useful if it was possible to disable that.
Also, just wondering if you could explain which information exactly in the crash report you're concerned about sharing the most? Thanks again.

@akissa: Apologies for that and I truly didn't mean to sound callous. I've just joined Atom recently and learning the ins & outs of working through issues and learning when to keep things open/closed for further details/discussion.

@akissa There actually is a way for you to disable that now, though - you can disable the exception-reporting package (go to Settings > Packages > search for exception-reporting and click disable)

@izuzak This issue is i do not know what is being sent and why it is being sent as well as why it is being sent in sneaky way, i have been using this for months and did not know until i looked at my process list. All other crash processing systems request the user for permission to upload their data to a different location.
In the EU it may (stand to be corrected) actually be ilegal to transfer data to a differnet country / continent since as i see the data is being sent to an Amazon AWS server which would most likely be in the US.

@amytruong No prob, i understand

@akissa I agree. As I said, I think it's something that should be improved. Thanks for caring about privacy :heart:
I believe that crash reporting functionality is in Electron, the framework Atom is built upon, specifically here. And the information that's sent is listed here. Does that help?

@mnquintana disabling the exception-reporting package does not disable the process it is still running even after restarting atom.

The metric package then ?

@jeancroy I don't think this has anything to do with Atom.  The process seems to be coming from Electron.

the metric package is disabled, anyway in a world awash with free code editors i am not going to waste any more of my time with an editor that spys on me by default.
@50Wliu Electron is installed on my system by Atom so it is an Atom problem not an Electron problem.

@50Wliu Electron is installed on my system by Atom so it is an Atom problem not an Electron problem.

Yes, it has to be installed, since Atom runs on Electron.  That being said it is not an Atom issue, as we cannot control what Electron is doing.

@50Wliu ???? -> https://github.com/atom/electron/blob/fe214e08068a36e4f98febecd62b31011de474af/atom/common/api/lib/crash-reporter.coffee#L24 of course you can. There is an option to not auto submit

In that case, I'm wrong.  Sorry for the misinformation :(.

But if you look at that piece of code the process get started regardless of autoSubmit.
So it's possible the process act local only, even if it does have remote IP in command line.
Do you have a communication of that process with the autosubmit set to off ?

@jeancroy atom does not set the flag, it could even check if the user does not want reporting and not startup the process https://github.com/atom/atom/blob/ff812749e67ed55518f91fa9d56286f8f3ce4ed6/src/browser/main.coffee#L56

I have experienced this first hand and i am not okay with this. Without any warning, without any confirmation , it uploaded data online . Who thought this is a good idea ? Are devs high on smack ?

This still isn't fixed.

I would like to add my voice to this as well, I just stopped using this editor after realizing what was going on behind the doors. Now you might not care about individuals like me, given that it is a free editor but overall implementing proper privacy controls will bring more positive attitude towards your application.

FYI we no longer auto-submit crash reports (https://github.com/atom/atom/blob/09ab7d68634c1603854acf03fd4b31926aeb450a/src/crash-reporter-start.js#L7), nor is the crash reporter URL even operational (last time I checked).
Other metrics data is now only submitted with user consent.

@50Wliu t might've taken you a year+ but good to hear it. I'll install the new version and let you know if I see anything.

@50Wliu
Everytime I start Atom it starts with a separate crashreporter process.
See yourself please
atom.exe --reporter-url=https://crashreporter.atom.io --application-name=Atom --v=1

Yes, I never said it doesn't get started, but does it actually do anything?  At most it's collecting the crash reports since we're not auto submitting and it has nowhere to submit to.
At least that's my thinking, which is why I asked others to confirm.

Also, a clarification about why we bother to start a crash reporter if it doesn't report the crashes.  There's two main reasons:

Without a crash reporter active, crash reports don't get saved to disk.  This is undesirable because when Atom crashes, we sometimes ask people to upload their reports so that we can get since insight into why Atom crashed.
I believe the eventual goal is to set up submitting so that it asks for consent first, but no one's done that yet.

Disclaimer: I am not a GitHub employee, so please do not take what I wrote as absolute fact.

@50Wliu
Thanks for clarification,
My desktop does not have internet so I personally do not care if it tries to uplload or not but my position is based on the fact that the user permission at least acknowledgement should be established before going forward with any of this stuff.
I understand that GIthub has great interest in collecting as much info as possible about programmers, gain even deeper insignth into every programmers mind (like they are tracking everything I write here, the speed of typing, amount of undos I use etc, check ther js in the page), that is their issue but the user consent is a requirement, otherwise it is a form of mental rape if you ask me.
ANyway I do not want to drag this issue further. I agree crash reports are important to product quality, but it would be nice this is made clear from the start.


[PR] The proj files have been updated to enable SourceLink

CSProj files have been updated to enable SourceLink in your nuget
[This pull request was created with an automated workflow]
I noticed that your repository and Nuget package are important for our .NET community, but you still haven't enabled SourceLink.
We have to take 2 steps:

Please approve this pull request and make .NET a better place for .NET developers and their debugging.
Then just upload the .snupkg file to https://www.nuget.org/ (now you can find the snupkg file along with the .nuget file)

You can find more information about SourceLine at the following links
https://github.com/dotnet/sourcelink
https://www.hanselman.com/blog/ExploringNETCoresSourceLinkSteppingIntoTheSourceCodeOfNuGetPackagesYouDontOwn.aspx
If you are interesting about this automated workflow and how it works
https://github.com/JTOne123/GitHubMassUpdater
If you notice any flaws, please comment and I will try to make fixes manually

We already support SourceLink by including this file into our .csproj files:
https://github.com/grpc/grpc/blob/be153dcb712c5e9d42c20be9b216117c9da80a2b/src/csharp/Grpc.Core/SourceLink.csproj.include
Instead of generating the snupkg packages separately, we decided to add the pdb file into the nugets directly, because it works the same and makes things simple (and the increase in size of the nugets is negligible).


Update dependency versions in book

Bumps CAPI, k8s version, Rancher and other dependencies in docs to align with recent changes in https://github.com/rancher/turtles/pull/658 and https://github.com/rancher/turtles/pull/663

Forgot to update CAPA versions, sorry.


(inkscape) package name error due to "Dotted and dotless I letter"

Chocolatey Version
0.12.1
Chocolatey License
No response
Package Version
1.1.2
Current Behaviour
Doing a choco upgrade all -y gives this failure message for inkscape in Windows OS using Turkic languages:
`Failures

ınkscape - ınkscape not installed. The package was not found with the source(s) listed.
Source(s): 'https://community.chocolatey.org/api/v2/'
NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify --pre,
the package may not be found.
Please see https://docs.chocolatey.org/en-us/troubleshooting for more
assistance.`

Expected Behaviour
"choco upgrade all -y" command should not give "ınkscape" error. The latest inkscape is already installed with chocolatey.
Steps To Reproduce

choco install inkscape -y
choco upgrade all -y
`Failures

ınkscape - ınkscape not installed. The package was not found with the source(s) listed.
Source(s): 'https://community.chocolatey.org/api/v2/'
NOTE: When you specify explicit sources, it overrides default sources.
If the package version is a prerelease and you didn't specify --pre,
the package may not be found.
Please see https://docs.chocolatey.org/en-us/troubleshooting for more
assistance.`

Notice: in the chocolatey error message "ınkscape" word is also written with a dotless "I", not "i")

Environment
- Operating System: Microsoft Windows NT 10.0.22000.0
- PowerShell Version: 5.1.22000.282
- Shell:

Chocolatey Log
https://gist.github.com/hkdemiralp/8943e8bb26d4cd3418de92795f60adf1

Anything else?
I believe the problem is the package naming which exhibits the "Dotted and dotless I" problem. In Turkic languages, Dotted "İ i" and dotless "I ı" are distinct letters. If the name of the package would have been written in lovercase letters like "inkscape", instead of "InkScape", it would work just fine. Installing inkscape works but upgrading all packages gives the error message.

This sounds more like a problem in the choco codebase at the moment than a problem with the package itself.

If the name of the package would have been written in lovercase letters like "inkscape", instead of "InkScape", it would work just fine. Installing inkscape works but upgrading all packages gives the error message.

While that would possibly fix this issue, it, unfortunately, wouldn't be right to do that right now either.
The identifier InkScape is used on purpose now due to historical reasons.
The first time the package was introduced to CCR that was the casing that was in use, and because of a bug that is believed to be in the underlying framework used by choco, we need to continue to use the same casing that the first version submitted used.
See https://github.com/chocolatey/choco/issues/1040

As it is a problem with the conversion between upper case and lower case characters done by Chocolatey, can you please open up an issue about that over at https://github.com/chocolatey/choco/issues so it can be looked into?

As it is a problem with the conversion between upper case and lower case characters done by Chocolatey, can you please open up an issue about that over at https://github.com/chocolatey/choco/issues so it can be looked into?

Thanks. I opened up an issue as you said at https://github.com/chocolatey/choco/issues/2601
I don't know if I should close the issue here. Please feel free to close, if it is the way it shoul be.

Thanks @hkdemiralp. I'll go ahead and close this now.


Emitter / tractor beams

(issue made to keep track for the milestone, see #1 for details)

@Achati, should I close this issue?

no since they are far from finished..
just in a more or less stable state that I could merge back into master

Ah, I see.


Removing unnecessary locators when detecting intraprocess only usecase  [7042]

This is a port of #917 from 1.9.x

Build status:

Linux
Mac
Windows


Enable POWER and s390x support for federation

The current federation only support running on amd64 but no POWER and s390x , we should enable federation can also run on those two platforms to enlarge its adoption.
root@gyliu-c11:~# manifest-tool inspect quay.io/kubernetes-multicluster/federation-v2:canary
quay.io/kubernetes-multicluster/federation-v2:canary: manifest type: application/vnd.docker.distribution.manifest.v1+json
      Digest: sha256:248a66787482da0638e1a5500aa0e89e2632436ff288bdc750553399236212a7
Architecture: amd64
          OS: linux
    # Layers: 0

FYI @xunpan

Thanks @marun . I got some requirement in KubeCon Shanghai that someone (Non IBM) want to test federation V2 on POWER and s390x because they have a mixed Kubernetes environment: POWER, x86 and POWER machines, and each architecture in a different cluster.
I told them they can make the x86 cluster as the host cluster and manage POWER and s390x cluster, they agree with this solution for now. But I was thinking, we may still need to consider the case if someone only has POWER clusters or only has s390x clusters, it would be great if we can support those major architectures OOB, so that the end users can download the related arch image from community and do the test directly.
I found that Kubernetes already support those major architectures https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.10.md#server-binaries for every release, can we follow same way as Kubernetes to release federation v2 with different architectures?

I'm guessing that Kubernetes didn't always support multiple architectures.  It's a mature product now, and we're still in alpha.  However, it might be worth investigating whether moving to test-infra ci infrastructure would give us the means to develop and test against other architectures.  I'm still not convinced it's a useful near-term priority, but we will want to get there eventually.
Given that you work for IBM, can you find out who is behind the support of the architectures in question?

Yes, +1 that this is not a near-term priority, and we can probably enable this after enter Beta. For now, I can enable POWER and s390x support internal first.
And regarding who is behind the support, as I work for systems group, it is also my responsibility to enable different architecture support for federation.

It was fixed at https://github.com/kubernetes-sigs/kubefed/pull/1039


fixed missing padding-top in serverlist

i noticed this issue only recently. the serverlist misses its top padding, glueing the container to the top of the window, unlike all other borders of this or any other container of the app.

before
after

the blue strip at the top in the "before" is my desktop background, to show the glue to window border
Disclaimer: I'm using the theme in vencord, not betterdiscord. I have not checked if this issue arises in betterdiscord too. if this is an issue for me / vencord only, and not in betterdiscord, feel free to deny the PR. otherwise, i'd be happy about a merge :)

Just realized that this is only an issue on Vesktop when the discord titlebar is disabled. I suppose that means this PR can be disregarded. I'll leave it up to you.

I'd like to fix this because I think it also impacts macos.

I've pushed a fix that fixes this problem. Your code doesn't work because it will mess up the margin when using a normal discord titlebar.


Nayabranch

please check the new assignment from this week.Thank you!

@angkamilama Good work on the assignment.  👍
Going good with learning 😄


uib-accordion: is-open is not linked to the outer scope as expected

I used the is-open attribute of the uib-accordion directive. I expected that the variable, I pass in there, will be updated by uib-accordion. That is not the case. Is this the correct behavior?
Story around: I wanted to use the variable of is-open and manipulate it from external. Inside the accordion is a search mask, which should be closed after a successful search. If I change the variable in is-open, after the successful search, the uib-accordion reacts as expected. The problem occurs, if the user clicks on the accordion header. The variable is not updated anymore and can therefore not correctly directed from outside anymore.
I added a plunkr, where you see, that the variable is not updated on a click on the header of the accordion (opening/closing accordion).
http://plnkr.co/edit/YTX7LTdiFlqn5yIn9t1x?p=preview

Yea, this is a bug.  We should be toggling the is-open attribute when the user clicks the header.  Good catch.  Please feel free to submit a clean PR with appropriate functional test(s).

This is not an issue.
The rule is always always always have a dot in your expressions. That way, you avoid the issues with inner scopes.
Check this: http://plnkr.co/edit/ITVUu4oLTiLZRUMvdeF1?p=preview

Thank you. That info solved my bug.


Automated Package Upgrade

:tada: This PR is included in version 7.7.160 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Consider implementing an extension for paginated responses

It would be a good idea to add an extension for paged responses, for example in your request you implement pagedRequest and the response pagedResponse. So that in the request you can define page size and page number
public class PagedResponse<T> : Response<IEnumerable<T>>
{
    public virtual int PageNumber { get; set; }
    public int PageSize { get; set; }
    public int TotalPages { get; set; }
    public int TotalRecords { get; set; }
}

Tell me if you like it and I can help with that, or do you think it is not necessary for the tamplate

@hectorrhg  Sounds good, go ahead added. 👍🏻

@CerealKiller97  see [#6 ]


perf(docker): radical reduce the image size

Docker Image Size
Hello its me again :)
Its weekend which means time to clean up all the mess i done over the week :)
I radical cleaned up the Docker Image to end up with a smaller image size.
Cheers Maik

@ellerbrock thanks for this, but we need to keep the "vendored version" of this Docker file.

hi @bep,
first at all thanks for your awesome work on hugo, nice to talk to you as person.
but i guess in this case you are wrong because i build and run this container already in production. you can see and test it here:

Docker Hub: https://hub.docker.com/r/ellerbrock/alpine-hugo/
Dockerfile: https://hub.docker.com/r/ellerbrock/alpine-hugo/~/dockerfile/
Build Details: https://hub.docker.com/r/ellerbrock/alpine-hugo/builds/b3jjfeaxv45l3vbee8xvj7x/

Run Example (to get hugo --help):
docker run ellerbrock/alpine-hugo
Cheers Maik

Or do i miss something?

Yes. Without vendoring it may work, but you have no idea what library versions Hugo uses, so it may break or do the unexpected at any moment.

hi @bep,
i see, yeah thats should not be a problem ...
let me change that and test and then i push a updated version ...


GIF picker configuration settings docs still refer to Gfycat (which was replaced by Giphy)

Gfycat was replaced by Giphy in the GIF picker, but the documentation still refers to Gfycat.
https://docs.mattermost.com/configure/integrations-configuration-settings.html#gif-beta

Also remove Beta label: https://mattermost.atlassian.net/browse/MM-56830


[Feature] Linux support

Is your feature request related to a problem? Please describe.
The feature is not related to a problem
Describe the feature you'd like
I would like the ability to install and use BetterDiscord on Linux.
Additional context

The link is in the readme.


Axios SSRF vulnerability

A recent vulnerability was detected in Axios: https://www.npmjs.com/advisories/1594/versions
Is this compatible with the 0.21.1 patch that was recently released?

Just saw that dependabot has created a PR to bump it up.

Just saw that dependabot has created a PR to bump it up.

Just saw that dependabot has created a PR to bump it up.

Just saw that dependabot has created a PR to bump it up.


Require token in addition to userid on any ajax change request

Include user token with response when logging in with password
Add active token to the CookieJar as a session level (non-persistent) cookie
Update any current queries that update info on the server to require both active userid and active token

currently, only queries that are affected are the user profile updates


Update README.md

Added missing negative operator from handleMinus function and missing parentheses

What happens when I copy/paste to Vim :disappointed:.
Thanks!


SVLEN for SV in VCF not considered by intersect / multiinter

Hi,
I was trying to compare multiple SV using VCF files. To my understanding bedtools uses the SVLEN from the INFO field to calculate the length of the variant. This also worked in one case.
In a different case I am presenting here, two variants should be overlapping, however multiinter seems to only consider the POS-field +1. Similarly, intersect does not return any result.
I kept the VCF file as simple as possible to rule out any misformattings, but still I did not get the issue sort. Thanks for any help!
-Fritjof
A.vcf
##fileformat=VCFv4.0
##fileDate=2015-04-10 13:47
##source=breakdancer
##reference=Uma
##INFO=<ID=SVTYPE,Number=1,Type=String,Description="Type of structural variant">
##INFO=<ID=SVLEN,Number=1,Type=Integer,Description="Length of structural variant">
##INFO=<ID=END,Number=1,Type=Integer,Description="End position of the variant described in this record">
#CHROM  POS ID  REF ALT QUAL    FILTER  INFO    A.bam
scaffold1   28133   .   .   <DEL>   24  PASS    SVTYPE=DEL;SVLEN=-125;END=29131
scaffold1   33493   .   .   <DEL>   15  PASS    SVTYPE=DEL;SVLEN=-112;END=34562
scaffold1   49259   .   .   <DEL>   23  PASS    SVTYPE=DEL;SVLEN=-212;END=50618
scaffold1   52805   .   .   <DEL>   17  PASS    SVTYPE=DEL;SVLEN=-196;END=53904

B.vcf
##fileformat=VCFv4.0
##fileDate=2015-04-10 13:47
##source=breakdancer
##reference=Uma
##INFO=<ID=SVTYPE,Number=1,Type=String,Description="Type of structural variant">
##INFO=<ID=SVLEN,Number=1,Type=Integer,Description="Length of structural variant">
##INFO=<ID=END,Number=1,Type=Integer,Description="End position of the variant described in this record">
#CHROM  POS ID  REF ALT QUAL    FILTER  INFO    B.bam
scaffold1   28201   .   .   <DEL>   17  PASS    SVTYPE=DEL;SVLEN=-128;END=29129
scaffold1   33264   .   .   <DEL>   44  PASS    SVTYPE=DEL;SVLEN=-109;END=34222
scaffold1   48995   .   .   <DEL>   26  PASS    SVTYPE=DEL;SVLEN=-211;END=50686
scaffold1   52785   .   .   <DEL>   43  PASS    SVTYPE=DEL;SVLEN=-194;END=53982

$bedtools multiinter -i A.vcf B.vcf

scaffold1   28132   28133   1   1   1   0
scaffold1   28200   28201   1   2   0   1
scaffold1   33263   33264   1   2   0   1
scaffold1   33492   33493   1   1   1   0
scaffold1   48994   48995   1   2   0   1
scaffold1   49258   49259   1   1   1   0
scaffold1   52784   52785   1   2   0   1
scaffold1   52804   52805   1   1   1   0

Unfortunately, the new VCF parsing code underlying the intersect tool has not yet made its way to the multiinter tool.  We will try to address in the next release or the one after that.  Sorry for this.

This is best handled with vcfanno


[Bug] Wrapper does not work for CREATE and UPDATE

Bug report
Applying styles to CREATE and UPDATE through 'wrapper' doesn't work
What I did
CRUD::addField([
           'name'      => 'status',
           'label'     => 'To status',
           'type'      => 'radio',
           'options'   => CommonHelper::getFurtherStatuses($this->crud->getCurrentEntry()->status),
           'inline'    => true,
           'wrapper' => [
               'element' => 'span',
               'class' => function ($crud, $column, $entry, $related_key) {
                               return CommonHelper::getStatusColor($column);
                          },
           ],
       ]);

What I expected to happen
The options for the 'radio' should have been changed according to the style applied through the wrapper.
What happened
Error while running
Too few arguments to function app\Http\Controllers\Admin\MaterialCrudController::app\Http\Controllers\Admin\{closure}(), 3 passed in /home/srigurubyo/work/laravel/usip/storage/framework/views/abe1029fcf60c5304a40f480b0fe73be4c6245f8.php on line 7 and exactly 4 expected (View: /home/srigurubyo/work/laravel/usip/vendor/backpack/crud/src/resources/views/crud/fields/inc/wrapper_start.blade.php)
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.3 (cli) (built: May 26 2020 12:24:22) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.3, Copyright (c), by Zend Technologies
LARAVEL VERSION:
v7.17.2@d16ff3a0a66d98e04163456b39c4b7302cf50a40
BACKPACK VERSION:
4.1.11@acc4df836505a612d1dd15a39ce02be87e36577d

I just realized that there is a reddit channel to ask questions, so closing this here.
https://www.reddit.com/r/BackpackForLaravel/comments/hig88h/wrapper_does_not_work_for_create_and_update/

Hello @srigurubyo
The problem is that you are adding a field and using a column wrapper definition.
For fields is a little bit different:
=> function ($crud, $field, $entry )
Remember that in fields the wrapper apply to the whole field, not by option as in some columns like select.
Best,
Pedro

You mean to say, I can not use below syntax ?
                    if ($field['key'] == USIPConstants::$STATUS_REJECTED) {
                        return 'badge badge-danger';
                    }

If so, is there a way I can differentiate between the various options to make it visible to user (GREEN and RED example)?


⚠ Processors has degraded performance

In 905db93, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 115 ms

Resolved: Processors performance has improved in dfe04e9.


Set SWDCLK and fix jtag_reset bug

Fixed bug where stlink_jtag_reset in stlink_open_usb() was never being called because the STLINK version was being checked before it had been initialized
Added support for stlink_set_swdclk() to adjust the SWD clock speed.  For example, to set at 4Mhz, 1.8Mhz, 900Khz, etc similar to in the official ST-LINK utility.  NOTE: The default when STLINK is powered appears to be 1.8Mhz (looked at scope traces) but it retains whatever was set before.

Thank you for this feature and fix!


Reviewing Codebase

Feedback for commit: 06bcdf04daa654d9ea4baf879b5095e23e77d75f
Repository Structure:

Why is everything inside lib? Is this idiomatic? Maybe makes sense for a src directory too.
Lacking a Util module? Possibly useful
Lacking a logging module. Definitely useful, should let users disable logging, enable logging and pipe logs to their own systems if they want to, is simple ash too. dprint from Board.luau:102 and SmartAssert from Board.luau:116 for example I would move here.
General thing, promises + threads sounds like debugging hell.
Sharding looks great

Board.luau:

Please add a comment explaining what the file does at the top
Explain what Shards are in the file ideally (Where you write ShardCounts, "Modify to match your MAU")
Board.luau:92, is this global state?
Board.luau:[101-181], this seems like a mix of Util and Shard utility functionality, should be in its own files imo
Board.luau:306, does this wait for all the actions of threads to complete before killing them? Can this cause inconsistent states? See the thread spawned in the constructor, Board.luau:203.

Compression.luau:

Again a file comment would be good.
math.log is only defined for positive numbers, as long as this is OK with your Leaderboards it should be fine.
Compression.luau:11, small optimisation, just pop the num~=0 check to outside the floor, and the function should be the same but just faster.

init.luau:

init.luau:12, make this multiplication explicit for maintainability, rather than this wild number.
init.luau:163, smartAssert returns! seriously just pop this to a nice util file
init.luau:441, again check for data races when this is destroyed. Just make sure everything is consistent before tasks are cancelled.

MemoryShard.luau:

MemoryShard.luau:13, this will lead to desynch between this and actual calendar months, this is obvs intentional, but might be worth supporting actual calendar months as well?

Retrospective comments:

It is a bit hard to understand responsibility from reading just the code, this is where adding comments to the top of each file will be super useful.
Reading docs, I am still a bit confused with the distinction between Leaderboards and Boards. Some more explanation here would be good.

Thanks for the great feedback!
In the new commit: bd183505107ce7ffb830cbb5bf36fa893aa8d8d5 lots of the feedback you suggested has been added. Will be adding comments in each of the modules over the next couple of days so people can better understand their respective "owners" and how they play into the core modules.


Sell Keybase to the highest bidder regardless of reputation, ethics, and views on privacy

Looks like this has already been actioned so by all means go ahead and close this issue.

Extremely disappointed.

Did you guys even consider the optics of this move? Brutal.

this isn't really fair imo. it's easy to jeer from the peanut gallery but this could very well be the path to securing communications for hundreds of millions who would not have it otherwise
@imawhale what have you built exactly? besides hilarious github issues

@atecce Say what you will about the criticism, precedent speaks for itself.

@trev-dev you’re right. undoing wrongheaded precedents takes something drastic, like, i dunno, acquiring an entire new team of engineers to solve pitfalls of your legacy systems who clearly have intrinsically motivated experience in the domain of secure communications

this acquisition made a lot of sense if you go two inferences passed the small-brain Stallman puritanical OSS take. Zoom had no ecosystem and no security, Keybase had no video chat

Zoom seems fairly good at video chat fwiw. they do one thing well

such is the Way of Unix

For me the argument has little to do with small-brain "purity". Many of the people I deal with on Keybase are like me and see the good the platform has done without being properly open source to begin with. Selling out to a company with questionable trust such as Zoom is the issue.  For myself, it is a sign of Keybase moving far enough toward the "dark side" than I'm comfortable with.
Why Zoom as a video prospect? Why not any of the other open source solutions?
Why a purchase? Why not a premium level of service instead? I would've happily written off Keybase as an expense.
Why not sell consultation to Zoom as they do need help rebuilding trust and securing their platform(?)
Open source needs further adoption, not assimilation. Free software is part of the foundation of trust that we signed up for and it's being crapped on.

it sounds like Zoom is allowing new entrants to come in and renegotiate the arch of their video service after hearing external criticisms of it. i've rarely heard of such a radical thing in an org with software. usually they simply hire bureausticrats to apologize for their lowest common denominator cruft for the rest of time while they pile on top of it and never look back. people are entirely misreading this

I really do hope you're right.

it sounds like Zoom is allowing new entrants to come in and renegotiate the arch of their video service after hearing external criticisms of it. i've rarely heard of such a radical thing in an org with software. usually they simply hire bureausticrats to apologize for their lowest common denominator cruft for the rest of time while they pile on top of it and never look back. people are entirely misreading this

this acquisition made a lot of sense if you go two inferences passed the small-brain Stallman puritanical OSS take. Zoom had no ecosystem and no security, Keybase had no video chat

@trev-dev you’re right. undoing wrongheaded precedents takes something drastic, like, i dunno, acquiring an entire new team of engineers to solve pitfalls of your legacy systems who clearly have intrinsically motivated experience in the domain of secure communications

tl;dr I get it, you invested in Zoom, congratulations.
This is a slam dunk win for Zoom (and Zoom investors) and quite obviously utterly terrible for Keybase users, products, and open source.
This is why we need Federated open source protocols, not black box VC pump and dump horse ****.

but quite obviously utterly terrible for Keybase users, and the future of Keybase products and open source initiatives.

You're incredibly naive about how acquisitions work and how this is likely to pan out if you disagree.

what a fantastic chain of reasoning! i can tell you were a killer in debate club. you go right passed the inferences to the conclusion

selling their [...] private information

you wanna substantiate this? or are you just happy baselessly slandering people because you're mad on the internet?

We need Federated open source protocols, not black box VC pump & dump horse**** .

that sounds great! go make it. or get out of the arena

but quite obviously utterly terrible for Keybase users, and the future of Keybase products and open source initiatives.

You're incredibly naive about how acquisitions work and how this is likely to pan out if you disagree.

what a fantastic chain of reasoning! i can tell you were a killer in debate club. you go right passed the inferences to the conclusion

selling their [...] private information

you wanna substantiate this? or are you just happy baselessly slandering people because you're mad on the internet?

We need Federated open source protocols, not black box VC pump & dump horse**** .

that sounds great! go make it. or get out of the arena

@atecce
https://theintercept.com/2020/04/03/zooms-encryption-is-not-suited-for-secrets-and-has-surprising-links-to-china-researchers-discover/

MEETINGS ON ZOOM, the increasingly popular video conferencing service, are encrypted using an algorithm with serious, well-known weaknesses, and sometimes using keys issued by servers in China, even when meeting participants are all in North America, according to researchers at the University of Toronto.
The researchers also found that Zoom protects video and audio content using a home-grown encryption scheme, that there is a vulnerability in Zoom’s “waiting room” feature, and that Zoom appears to have at least 700 employees in China spread across three subsidiaries. They conclude, in a report for the university’s Citizen Lab — widely followed in information security circles — that Zoom’s service is “not suited for secrets” and that it may be legally obligated to disclose encryption keys to Chinese authorities and “responsive to pressure” from them.
Zoom could not be reached for comment.
Generating Encryption Keys in China
Earlier this week, The Intercept reported that Zoom was misleading users in its claim to support end-to-end encryption, in which no one but participants can decrypt a conversation. Zoom’s Chief Product Officer Oded Gal later wrote a blog post in which he apologized on behalf of the company “for the confusion we have caused by incorrectly suggesting that Zoom meetings were capable of using end-to-end encryption.” The post went on to detail what encryption the company does use.
Based on a reading of that blog post and Citizen Lab’s research, here is how Zoom meetings appear to work:
When you start a Zoom meeting, the Zoom software running your device fetches a key with which to encrypt audio and video. This key comes from Zoom’s cloud infrastructure, which contains servers around the world. Specifically, it comes from a type of server known as a “key management system,” which generates encryption keys and distributes them to meeting participants. Each user gets the same, shared key as they join the meeting. It is transmitted to the Zoom software on their devices from the key management system using yet another encryption system, TLS, the same technology used in the “https” protocol that protects websites.
Depending on how the meeting is set up, some servers in Zoom’s cloud called “connectors” may also get a copy of this key. For example, if someone calls in on the phone, they’re actually calling a “Zoom Telephony Connector” server, which gets sent a copy of the key.
Some of the key management systems — 5 out of 73, in a Citizen Lab scan — seem to be located in China, with the rest in the United States. Interestingly, the Chinese servers are at least sometimes used for Zoom chats that have no nexus in China. The two Citizen Lab researchers who authored the report, Bill Marczak and John Scott-Railton, live in the United States and Canada. During a test call between the two, the shared meeting encryption key “was sent to one of the participants over TLS from a Zoom server apparently located in Beijing,” according to the report.
The report points out that Zoom may be legally obligated to share encryption keys with Chinese authorities if the keys are generated on a key management server hosted in China. If the Chinese authorities or any other hypothetical attacker with access to a key wants to spy on a Zoom meeting, they also need to either monitor the internet access of a participant in the meeting, or monitor the network inside the Zoom cloud. Once they collect the encrypted meeting traffic, they can use the key to decrypt it and recover the video and audio.
Encryption Flaws: The Worst of AES
Citizen Lab flagged as worrisome not only the system used to distribute Zoom encryption keys but also the keys themselves and the way they are used to encrypt data.
Zoom’s keys conform to the widely used Advanced Encryption Standard, or AES. A security white paper from the company claims that Zoom meetings are protected using 256-bit AES keys, but the Citizen Lab researchers confirmed the keys in use are actually only 128-bit. Such keys are still considered secure today, but over the last decade many companies have been moving to 256-bit keys instead.
Furthermore, Zoom encrypts and decrypts with AES using an algorithm called Electronic Codebook, or ECB, mode, “which is well-understood to be a bad idea, because this mode of encryption preserves patterns in the input,” according to the Citizen Lab researchers. In fact, ECB is considered the worst of AES’s available modes.
Here’s why: It should be impossible to tell the difference between properly encrypted data and completely random data, such as static on a radio, but ECB mode fails to do this. If there’s a pattern in the unencrypted data, the same pattern shows up in the encrypted data. This Wikipedia page has a useful illustration to visualize this:
Once it has been poorly encrypted in this manner, video and audio data is distributed to all participants in a meeting through a Zoom Multimedia Router server. For most users, this server runs in Zoom’s cloud, but customers can choose to host this part on-premises. In this case, Zoom will generate, and thus have access to, the AES key that encrypts the meeting but shouldn’t have access to the meeting content itself, so long as none of the aforementioned “connector” servers (for phone calls and so forth) are participating in the meeting. (In its blog post, Zoom said self-hosting customers will eventually be able to manage their own encryption keys.)
Meeting hosts can set their meetings to have virtual “waiting rooms,” making it so that users do not directly enter the meeting when they log on with Zoom but instead must wait to be invited in by a participant. The Citizen Lab researchers discovered a security vulnerability with this feature while conducting their encryption analysis. They said in their report that they have disclosed the vulnerability to Zoom but that “we are not currently providing public information about the issue to prevent it from being abused.” In the meantime, the researchers advised Zoom users who desire confidentiality to avoid using waiting rooms and instead set passwords on meetings.
Corrective Moves By Zoom
The newly uncovered flaws in Zoom’s encryption may be troubling for many of the company’s customers. Since the coronavirus outbreak started, Zoom’s customer base has surged from 10 million users to 200 million, including “over 90,000 schools across 20 countries,” according to a blog post by Zoom CEO Eric Yuan. The U.S. government recently spent $1.3 million on Zoom contracts as part of its response to the pandemic, according to a review of government contracts by Forbes, and the U.K. government has been using Zoom for remote Cabinet meetings, according to a tweet from Prime Minister Boris Johnson.
Among those who should be concerned about Zoom’s security issues, according to Citizen Lab, are “governments worried about espionage” and “businesses concerned about cybercrime and industrial espionage.”
Despite a recent flood of security and privacy failures, Yuan, Zoom’s CEO, appears to be listening to feedback and making a real effort to improve the service. “These new, mostly consumer use cases have helped us uncover unforeseen issues with our platform. Dedicated journalists and security researchers have also helped to identify pre-existing ones,” Yuan wrote in his blog post. “We appreciate the scrutiny and questions we have been getting — about how the service works, about our infrastructure and capacity, and about our privacy and security policies.”
In addition to promptly fixing several security issues that were reported, the company removed an “attendee attention tracker” feature, a privacy nightmare which let meeting hosts track whether participants had the Zoom window — or some other app’s window — in focus during a meeting. It has also invested in new training materials to teach users about the security features like setting passwords on meetings to avoid Zoom-bombing, the phenomenon where people disrupt unprotected Zoom meetings.
Because Zoom’s service is not end-to-end encrypted, and the company has access to all encryption keys and to all video and audio content traversing its cloud, it’s possible that governments around the world could be compelling the company to hand over copies of this data. If Zoom does help governments spy on its users, the company claims that it hasn’t built tools specifically to help law enforcement: “Zoom has never built a mechanism to decrypt live meetings for lawful intercept purposes,” Gal, Zoom’s chief product officer, wrote in the technical blog post, “nor do we have means to insert our employees or others into meetings without being reflected in the participant list.”
Unlike some other tech companies, Zoom has never released any information about how many government requests for data it gets, and how many of those requests it complies with. But after the human rights group Access Now’s open letter urging Zoom to publish a transparency report, Yuan also promised to do just that. Within the next three months, the company will prepare “a transparency report that details information related to requests for data, records, or content.” Access Now has commended Zoom on committing to publish a transparency report.

i see your clipboard works. you're still going to have to think for yourself a bit here. don't be scared :D

this acquisition made a lot of sense... Zoom had no ecosystem and no security, Keybase had no video chat

@atecce I agree it made sense for Zoom. But I would frame it differently: Keybase had security and an ecosystem, Zoom had video chat. Only one of those 3 things is true now. It is a slam dunk win for Zoom (and Zoom investors) but quite obviously utterly terrible for Keybase users, and the future of Keybase products and open source initiatives.
You're incredibly naive about how acquisitions work and how this is likely to pan out if you disagree.

it sounds like Zoom is allowing new entrants to come in and renegotiate the arch of their video service after hearing external criticisms of it. i've rarely heard of such a radical thing in an org with software. usually they simply hire bureausticrats to apologize for their lowest common denominator cruft for the rest of time while they pile on top of it and never look back. people are entirely misreading this

undoing wrongheaded precedents takes something drastic, like, i dunno, acquiring an entire new team of engineers to solve pitfalls of your legacy systems who clearly have intrinsically motivated experience in the domain of secure communications

Not to mention the false pretenses under which people were lured to Keybase. Chris @malgorithms Coyne literally said they are happy to never sell another company and would never do anything unethical, like, hmm, selling their user base and private information to a company which is effectively a proxy for a foreign government, after a user expressed this specific concern to him.
Don't worry guys -- the engineers are intrinsically motivated! And you call me the puritan...
We need Federated open source protocols, not black box VC pump & dump horse**** .
I was a fan of Keybase and had been recommending it to others.
GG

federated msg is a hype. It's harder to make a secured federation system. Keybase's current model is the best. it bring the best of security to the mass. agree or not, it's the best.

Zoom seems fairly good at video chat fwiw

WebRTC isn't hard to implement and it works just as good for P2P chat or even password protected chat rooms ...

i see your clipboard works. you're still going to have to think for yourself a bit here. don't be scared :D

You're right, I was wrong to doubt you, forgive me.

Would like to point out that I find it amusing that Zoom CEO left Webex after they rejected his smartphone video conferencing idea (which they now have AFAIK).
Meanwhile, FaceTime encryption is pretty good. Hangouts/Meet probably is as well. Haven't seen major media coverage of security issues with those.
As much as we might give Zuckerberg flak, Messenger or Whatsapp have a well respected encryption policy, for the most part.
Then Verizon just acquired Bluejeans in April for far less than what Zoom is supposedly worth...
All in all, Zoom is pure marketing hype. We've basically generated the colloquial "Zoom me" as compared to "Google it", meanwhile there's other search engines that take your security more seriously than improving Google SEO (Duckduckgo).
If y'all seriously hate Zoom, delete your accounts, tell your friends and family to boycott it until they are more transparent with their development status.
Meanwhile, good luck trying to get people to switch to something else, because I know for a fact that my family refuses to listen to me or anyone else concerned about online privacy

WebRTC isn't hard to implement and it works just as good for P2P chat or even password protected chat rooms ...

one example i'm directly familiar with: the company Invision (which is completely remote) uses Zoom for their all hands meetings, which contain hundreds of individuals, with no problems. my Teams meetings start struggling at about 5. again, if you think you can do better than that with an implementation of WebRTC, go build it, but it's not surprising to me while optimizing perf another system aspect was neglected. this acquisition seems to be a recognition of that fact

Would like to point out that I find it amusing that Zoom CEO left Webex after they rejected his smartphone video conferencing idea (which they now have AFAIK).

Then Verizon just acquired Bluejeans in April for far less than what Zoom is supposedly worth...

having used both BlueJeans and WebEx they are complete mediocre garbage. nobody who actually interacts with these systems thinks they are well done. they are the paradigmatic example of what "Enterprise" software usually is, cruft that decision makers force on their white collar wage slaves. they would never survive in a consumer environment. as a matter of fact, it sounds to me like that is exactly why the CEO of Zoom started his own company. he knew he could do better

Meanwhile, FaceTime encryption is pretty good. Hangouts/Meet probably is as well. Haven't seen major media coverage of security issues with those.

As much as we might give Zuckerberg flak, Messenger or Whatsapp have a well respected encryption policy, for the most part.

i generally trust aapl's professed commitment to privacy, but you should read more about FaceTiime. it turns out these problems are just hard, even when the incentives and intentions are aligned. it's almost like you need an entire team of people to evaluate systems from that specific perspective
as for Hangouts and WhatsApp. just lol. Google is Evil. Facebook makes the world more closed and divided. Google attempts to reconstruct my entire browsing history because they think they own the web now that they've monopolized the interface to it. Facebook balkanizes us into sets of labels their machine learning algorithms can target for marketers. they are both totalitarian surveillance state run by Orwellian shills. they have no business model outside of that and everyone knows it. at least Zoom can collect ARR from orgs

Zoom seems fairly good at video chat fwiw

WebRTC isn't hard to implement and it works just as good for P2P chat or even password protected chat rooms ...

Nobody says it's hard to implement. Just that currently the webrtc solutions out there isn't capable of handling large number of users in single conference as efficient as zoom. you gotta give zoom some credit in this area.

exactly. they focused on doing one thing well. such is the Way of Unix

The Way of Unix is good for the tool's development.  I started with Skype. Used Lync in undergrad. Using Slack and Discord now...
If Twitch and YouTube can do real-time streaming, then how hard can it truly be to do decentralized, secure p2p  video calling?
I'm a software engineer, but please eli5

And Skype IS encrypted. Although has a limit of somewhere between 32 and 50
https://support.skype.com/en/faq/FA31/Does-Skype-use-encryption?

@OneCricketeer you don't know what you don't know. ¯_(ツ)_/¯

If Twitch and YouTube can do real-time streaming, then how hard can it truly be to do decentralized, secure p2p video calling?

You can always develop your own app to prove how easy it is.

@OneCricketeer fair point about UUOC

Lol @ Everyone telling me to make it myself.
I have my own interests that are completely unrelated to the longevity of Zoom, Inc. or video conferencing

yeah that's totally reasonable. the point is, if you're going to impugn someone with malice like OP you should at least have some skin in the game or know what you're talking about or gtfo
i don't know how Zoom's stack is so much more effective than its competitors atm (including WebRTC). that's kind of why they are worth 50b rn

yeah that's totally reasonable. the point is, if you're going to impugn someone with malice like OP you should at least have some skin in the game or know what you're talking about or gtfo
i don't know how Zoom's stack is so much more effective than its competitors atm (including WebRTC). that's kind of why they are worth 50b rn

lwow you know how the stock market works too? Do you have a blog?

know what you're talking about or gtfo

Freedom of speech, brah

Speaking of stock market, anyone else have a short position in that 50b market?

you should absolutely do that if you liked this issue. somehow i doubt those people have the courage of their convictions

Nope. Haven't liked. The title doesn't me want to like it.

I'm honestly not sure what we are debating now.
This is a keybase issue. It is that simple.
All I can gather from this thread @atecce is that you want to defend Zoom's decision for whatever reason, yet I cannot find a logical explanation for you doing so unless you happy to have a large stake in the company's equity... Did you time at Fidelity teach you how to sniff out a good buy and hold strategy?

you should absolutely do that if you liked this issue. somehow i doubt those people have the courage of their convictions

You immediately turned this into a personal attack, rather than deconstructing the issue, which is a strong signal that you're not acting in good faith.
As for Zoom being "worth" $50B, how do you arrive at that figure? STOCK PRICE BRO?

eh? i’m defending Keybase’s decisions on the technical merits. i am also trolling pathetic spectators totally absent from the arena of these decisions

eh? i’m defending Keybase’s decisions on the technical merits. i am also trolling pathetic spectators totally absent from the arena of these decisions

How is selling to Zoom going to improve Keybase's technology?

Well, at least you admit to trolling. Congrats. We can keep this going too.

eh? i’m defending Keybase’s decisions on the technical merits. i am also trolling pathetic spectators totally absent from the arena of these decisions

Confirmed troll. GTFO

gg

How is selling to Zoom going to improve Keybase's technology?

because Zoom’s video streaming is excellent you incorrigible philistine

Dude. No one is calling you names.
Please prove how Zoom is seriously better than Slack video, for example.

already answered this. Slack can’t handle hundreds of clients at once. i have no qualms about anything i call OP given the genesis of this thread

And no one asked you to comment, so thanks for being part of the peanut gallery. Feel free to wipe the shells off as you excuse yourself.

can’t wait to see your implementation of WebRTC :D

The market is too crowded. Zoom works, but so do others.
I'm sorry you have to sit on a call with hundreds of people at a time.

 You'll do great things with your degree
https://atec.pub/resume.pdf

i like what i do. i try and make meaningful things with text. polemic is one form of that

also genuinely think the existence of this issue is unfair so i’m not really sorry about it

https://github.com/keybase/client/issues/24105
this is a much more constructive one imo and quite frankly i don’t trust my intuitions on it
maybe we should move the conversation there :D

Zoom Acknowledges It Suspended Activists' Accounts At China's Request
https://www.npr.org/2020/06/12/876351501/zoom-acknowledges-it-suspended-activists-accounts-at-china-s-request

this isn't really fair imo. it's easy to jeer from the peanut gallery but this could very well be the path to securing communications for hundreds of millions who would not have it otherwise
@imawhale what have you built exactly? besides hilarious github issues

https://www.macrumors.com/2020/06/19/zoom-end-to-end-encryption-available-to-all/
thanks @maxtaco!


DCOS-44502: DC/OS UI crashes after attempting to edit config of marathon-lb

When attempting to writeErrors we check that the formData is an object,
but if so we assume the schema has properties. But if the formData is an
Array then its an object and the schema does not have any properties.
Added a check that the schema has properties before iterating over
formData keys. To resolve this issue.
Testing

See COPS-3907

Trade-offs

This was the simplest fix. We could also check the schema.type === "object"
Dependencies

None
Screenshots

None

It works, but wouldn't it make sense to check here: https://github.com/dcos/dcos-ui/pull/3454/files#diff-e9f792f5f3db4a89c3a6c506697ad36eR150  -  if (schema == null || !schema.properties)?

We agreed to only require one review for backports, but I guess we made it to only require one review for merging to older versions (some of which aren't backports, like this one for example).

@GeorgiSTodorov  if we added the check to if (schema == null) then the code to write errors on line 166 would never get called.

@nLight 👍, tests added

@DanielMSchmidt maybe, I'll give it a try and see what the LOE is on the migration.

@TattdCodeMonkey Fair enough ;)

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


bad_alloc/sigabort on malformed apng file

The decoder may lead to a premature termination caused by a very large frameCount being passed to make_unique. In the example below frameCount is 520486912. Maybe this relates to #73 as well.
Output:
libpng warning: sBIT: CRC error
libpng warning: acTL: CRC error
libpng warning: fcTL: CRC error
libpng warning: size in first frame's fcTL must match the size in IHDR
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x0000007ff7bb58e8 in __GI_abort () at abort.c:79
#2  0x0000007ff7e7ab28 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#3  0x0000007ff7e788ac in ?? () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#4  0x0000007ff7e788f8 in std::terminate() () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#5  0x0000007ff7e78bb0 in __cxa_throw () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#6  0x0000007ff7e790e8 in operator new(unsigned long) () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#7  0x0000000000409360 in std::make_unique<std::shared_ptr<apng_drawable::ApngFrame> []> (__num=520486912)
    at /usr/lib/gcc/aarch64-linux-gnu/8/../../../../include/c++/8/bits/unique_ptr.h:837
#8  apng_drawable::ApngImage::ApngImage (this=0x846f90, width=4294962472, height=0, frameCount=<optimized out>, loopCount=0) at ApngImage.cpp:30
#9  0x0000000000406ad0 in apng_drawable::ApngDecoder::decode (source=std::unique_ptr<class apng_drawable::StreamSource> = {...}, result=<optimized out>)
    at ApngDecoder.cpp:223
#10 0x0000000000402c14 in main (argc=<optimized out>, argv=<optimized out>) at main.cpp:19

Testcase: crash.apng.zip

It should be fixed with #91. Please re-open this issue if you still meet the same error.


Hi updates!

Hi, I like to pull a request!

See how to clone and pull a repository:

https://try.github.io/levels/1/challenges/1
https://www.youtube.com/watch?v=rgmDhNLQ3yU
https://www.youtube.com/watch?v=73I5dRucCds

Thank you!


[WIP] Feat/s3 plugin tokens support

Could you do few things before we move this on?

document this PR
add a change set (check the contributors guidelines)

Once all steps above is done we can merge.

Never mind, since I created this PR I actually wrote a new NPM server with all the user/token/teams/organizations functionality that I need: https://github.com/taskforcesh/nandu


Update itemCount of WheelPickerController

Hello,
I would like to update the wheel picker widget based on another wheel picker. Concretely I want to have two wheels where one is the number (e.g. 1-10) and the other one is the unit (e.g. days, weeks, months). I would like to be able to change the itemCount of the number wheel picker depending on the state of the unit wheel picker. For that I would need to update the itemCount after the initialization of the WheelPickerController. Is that possible today? Or is it possible to implement this?

Hi @Madnex,
I understand the need for it and will work on it soon, I'll update you when I release it 👍

Great, thanks a lot! Much appreciated 😎

Hi @Madnex,
Happy to let you know that the new version is now out with support for reactive itemCount.
You can set the itemCount directly in the wheel picker using a variable or through the controller. Then, trigger a UI update (e.g., using setState) to dynamically change it.
I wrote a small widget that uses your example:

class WheelPickerExample extends StatefulWidget {
  const WheelPickerExample({super.key});

  @override
  State<WheelPickerExample> createState() => _WheelPickerExampleState();
}

class _WheelPickerExampleState extends State<WheelPickerExample> {
  static const Map<String, int> unitNumberMap = {
    "Days": 28,
    "Weeks": 4,
    "Months": 1,
  };

  final _unitWheel = WheelPickerController(itemCount: unitNumberMap.length);
  int _days = unitNumberMap.values.first;

  @override
  Widget build(BuildContext context) {
    const textStyle = TextStyle(fontSize: 26.0, height: 1.5);
    final wheelStyle = WheelPickerStyle(
      size: 200,
      itemExtent: textStyle.fontSize! * textStyle.height!, // Text height
      squeeze: 1.25,
      diameterRatio: .8,
      surroundingOpacity: .25,
      magnification: 1.2,
    );

    return Row(
      mainAxisAlignment: MainAxisAlignment.spaceEvenly,
      crossAxisAlignment: CrossAxisAlignment.center,
      children: [
        Expanded(
          child: WheelPicker(
            builder: (context, index) {
              index = index % unitNumberMap.length;
              return Text(unitNumberMap.keys.toList()[index], style: textStyle);
            },
            controller: _unitWheel,
            looping: false,
            selectedIndexColor: Colors.white,
            onIndexChanged: (index) {
              setState(() => _days = unitNumberMap.values.elementAt(index));
            },
            style: wheelStyle,
          ),
        ),
        Expanded(
          child: WheelPicker(
            builder: (context, index) {
              return Text("${index + 1}".padLeft(2, '0'), style: textStyle);
            },
            itemCount: _days,
            looping: false,
            selectedIndexColor: Colors.blueAccent,
            style: wheelStyle,
          ),
        ),
      ],
    );
  }

  @override
  void dispose() {
    _unitWheel.dispose();
    super.dispose();
  }
}

Now, when the wheel picker updates its itemCount, it defaults to resetting the current index to its initialIndex if possible, or staying within the bounds closest to that number.
If you prefer to keep the current index unchanged, you can use this example where I do the same thing using a controller.

class WheelPickerExample extends StatefulWidget {
  const WheelPickerExample({super.key});

  @override
  State<WheelPickerExample> createState() => _WheelPickerExampleState();
}

class _WheelPickerExampleState extends State<WheelPickerExample> {
  static const Map<String, int> unitNumberMap = {
    "Days": 28,
    "Weeks": 4,
    "Months": 1,
  };

  final _unitWheel = WheelPickerController(itemCount: unitNumberMap.length);
  final _daysWheel = WheelPickerController(
    itemCount: unitNumberMap.values.first,
  );

  @override
  Widget build(BuildContext context) {
    const textStyle = TextStyle(fontSize: 26.0, height: 1.5);
    final wheelStyle = WheelPickerStyle(
      size: 200,
      itemExtent: textStyle.fontSize! * textStyle.height!, // Text height
      squeeze: 1.25,
      diameterRatio: .8,
      surroundingOpacity: .25,
      magnification: 1.2,
    );

    return Row(
      mainAxisAlignment: MainAxisAlignment.spaceEvenly,
      crossAxisAlignment: CrossAxisAlignment.center,
      children: [
        Expanded(
          child: WheelPicker(
            builder: (context, index) {
              index = index % unitNumberMap.length;
              return Text(unitNumberMap.keys.toList()[index], style: textStyle);
            },
            controller: _unitWheel,
            looping: false,
            selectedIndexColor: Colors.white,
            onIndexChanged: (index) {
              setState(() {
                _daysWheel.itemCount = unitNumberMap.values.toList()[index];
                _daysWheel.setCurrent(_daysWheel.selected);
              });
            },
            style: wheelStyle,
          ),
        ),
        Expanded(
          child: WheelPicker(
            builder: (context, index) {
              return Text("${index + 1}".padLeft(2, '0'), style: textStyle);
            },
            controller: _daysWheel,
            looping: false,
            selectedIndexColor: Colors.blueAccent,
            style: wheelStyle,
          ),
        ),
      ],
    );
  }

  @override
  void dispose() {
    _unitWheel.dispose();
    _daysWheel.dispose();
    super.dispose();
  }
}

I hope this update suits your needs. If you notice anything that's not quite right or have suggestions for improvements, please don't hesitate to reach out.

Thanks a lot! Indeed it is working perfectly 👍 🎉


[Story]: No serving platforms available view

Goal
Create a view to display when there are no serving platform available selected
Dependency issue

https://github.com/opendatahub-io/odh-dashboard/issues/1913
https://github.com/opendatahub-io/odh-dashboard/issues/1941

Itemized goals

Detect that neither kserve and modelmesh are available to select in the cluster
Display a view to prevent the user to select a serving platform

Aspects continued elsewhere
No response
Mocks
[TBD]

@vconzola I've added this to keep track of the state of not having any platform selected.

This will be covered in https://github.com/opendatahub-io/odh-dashboard/issues/2010, closing this in favor of that issue.

If neither KServe nor ModelMesh is selected in the cluster settings when a new project is created, we should display this empty state in the project's Models and model servers section. https://www.sketch.com/s/113593f8-5970-49d6-a352-709b07639127/v/Arobq4/a/uuid/036B63EC-0D57-44CF-8A9F-63DF6B4F0BAC


FRONTEND WITH FRAMEWORK: REACT- 1.2 Introduction to Babel

Contributors are required to include

what is Babel
about babel
why babel
its relation to React and anything relevant to the framework should be included.

Also make sure -
Avoid copy/paste, We will be checking.
Changes should be made inside the Frontend_Web_Development_React_Angular_Vue/ dir inside Frontend_Web_Development_React_Angular_Vue branch.
Task will be assigned on first come first serve
Check out Contributing Guidelines and Code Of Conduct

Can I contribute on this?
Himanshi Gupta Batch-6 Frontend-Framework

Sure @Himanshi1805 go for it . Good luck!

@mukeshmjn Can I work on this issue documentation.

I would like to work on this issue. @mukeshmjn if this issue s reassigned, please do consider me for it.

I would like to work on this issue. @mukeshmjn if this issue s reassigned, please do consider me for it.

Sure :)


feat: added no search result found text to event fragment

added showNoEventText dunction and called it inside evenetViewModel.events observer when list is empty
added noEventLL to fragment_event
ScreenShot

feat: #857

@iamareebjamal please review it

Squash your commits. One PR should contain 1 commit


bump expiry date for Alerting

Propose extending the guidance for six months, the guidance also needs updating.

I've pushed some changes which address the main issues I had with this page.

I think this guidance will need a full review, but let's get the date extended and this tweak in.
@danielroseman could you approve this?


Null rotation states should appear as "Unknown" not blank

Right now, on the service instance details page, the node popovers render null rotation states as blank. This can be confusing for users. In one case the node was Enabled, and two of the three ports were Disabled. The third port was blank, but the user didn't notice, and questioned why the aggregate rotation status was showing up as Unknown instead of Disabled. (If all ports are Disabled, then the aggregate rotation state should be disabled.) Making the blank render as "Unknown" would solve this.

Fixed


[Bug]: Tags not properly updated to 1.21

What happened?
As part of 1.21, Mojang changed the directories for various tags to use singular names instead of plural.
Your mod uses tags in one or more of the old directories that was changed! This means those tag files will no longer load in 1.21 unless you update the directories!
The affected directories and their new counterparts are:

tags/blocks -> tags/block
tags/items -> tags/item
tags/entity_types -> tags/entity_type
tags/fluids -> tags/fluid
tags/game_events -> tags/game_event

Please ensure that any of these that you are using is updated to the new name in all namespaces (including your own, minecraft, and c).
Modloader
Fabric
Mod Version
1.3.0
Minecraft Version
1.21
Logs
No response
Other Info
No response

Whoops, thought I got all the tags, but seems I didn't. Fixed in latest version.


🌐 Update Portuguese translation for docs/pt/docs/alternatives.md

Reviewed alternatives.md, as there have been minor changes since its translation
the main change was to switch requests to httpx

Cool! Thanks @ceb10n :sunglasses: :rocket:
And thanks for the reviews @cassiobotaro @nazarepiedady :partying_face:


issues 1563 , Need to be repaired again

// https://github.com/gogf/gf/issues/1563
func Test_Struct_Issue1563(t *testing.T) {
	type User struct {
		Pass1 string `c:"password1"`
	}
	gtest.C(t, func(t *gtest.T) {
		for i := 0; i < 100; i++ {
			user := new(User)
			params2 := g.Map{
				"password1": "111",
				"PASS1":     "222",
				"Pass1":     "333",   //new line
			}
			if err := gconv.Struct(params2, user); err == nil {
				t.Assert(user.Pass1, `111`)
			}
		}
	})
}

Thank you very much,  but , this isn't over yet.
Originally posted by @shou55 in https://github.com/gogf/gf/issues/1563#issuecomment-1047479361

@shou55 Done


Custom operator matchers and date/datetime matchers

Introducing extended operators with custom matchers and standard date and datetime matchers.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Don't want to block you any longer, and though I have ideas, this is the safest way of doing this (unfortunately 😔).
Wish we could make it clear what changes we make can count as "backwards-compatible" in the TypeScript world, because almost any type change, additive or subtractive, has the potential to break downstream users. For generics, TypeScript's type parameter inference is clever while it works, but isn't great if you want to introduce that inference in a backwards compatible way (e.g. microsoft/TypeScript#26242 or, idk, microsoft/TypeScript#26349).

Thanks! We did already have a revert due to the clever use of generics: https://github.com/cloudscape-design/collection-hooks/commit/a9d72bb03480ecb0c4312e84799c829162cff3fa
Unfortunately, having some of these anys does seem as the only safe backward-compatible change.


Updated SimpleBackgroundTransfer Image URL

The download was failing because the original image url no longer exists.
I updated the image url to a working url that also uses https to abide by iOS App Transport Security

@brminnick this is awesome, thanks!


Added Undo Button

Hi @kaal-coder, i have raised this PR for issue #10 . kindly review it .
Thanks.

Please update the branch and then make a PR

@kaal-coder "Please update the branch" can you explain this.

@kaal-coder "Please update the branch" can you explain this.

Go to your repository
In the drop-down, you'll see option to Update Branch


Way to use this lib while piping the output to another lib.

Hi thanks for your work!
I'm using a setup built with https://github.com/jaredpalmer/backpack and it uses this library like many other build systems for webpack.
I use https://github.com/trentm/node-bunyan for server side logging since it outputs json which is easy to transport around. But for pretty printing it on the console I need to pipe the output to it, which solves the bunyan pretty printing problem but decolorizes the output of webpack/backpack. Any ideas on how to support both at the same time?
Standard Setup

With piping
// package.json
  "scripts": {
    "dev": "backpack | bunyan -o short",  // <-- this step
  }

I solved my issue by not having a raw json output that pipes to bunyan. By using a custom stream with prettycli to match the output of bagpack and bunyan.


Names of objects created by pvc-migrate should be DNS friendly

Any intermediary kube object created by pvc-migrate should have DNS friendly name

Fixed through #79
The new changes now remove any added suffices from the Pod and Service names making the names consistent with the names on the Source cluster. Another change addresses the problem with the invalid pathnames in volume mounts.


[ic-card] clickable cards do not use current link styling

Summary of the bug
Global link styles have recently been updated, but the cards component does not seem to have been updated in accordance.
🧐 Expected behaviour
Cards (clickable) use a link as the card title. This should be updated to match the other link styling throughout the site.
📸 Screenshots or code

Work being done in #245


Provide a warning for CUDA compute capabilities less than 3.5 when building.

PR for issue #23951. Let me know of any changes that are required, and I'll be happy to make them.

Thanks for working on this. @gunan can correct me if I'm wrong, but configure.py already has a small warning when the compute capability provided is less than 3.*. You could probably get rid of warning_flag and replace the whole construct with something like this:
ver = float(m.group(0))
if ver < 3.5:
  print('ERROR: TensorFlow only supports Cuda compute capabilities 3.5 or higher. '
          'Please re-specify a list of compute capabilities, excluding version {}.'.format(ver))
  all_valid = False

There's no warning in the prompt for a compute capability either. Can you change it to this?
...build time and binary size, and that TensorFlow only supports compute capabilities > 3.5.

Thanks for working on this. @gunan can correct me if I'm wrong, but configure.py already has a small warning when the compute capability provided is less than 3.*. You could probably get rid of warning_flag and replace the whole construct with something like this:
ver = float(m.group(0))
if ver < 3.5:
  print('ERROR: TensorFlow only supports Cuda compute capabilities 3.5 or higher. '
          'Please re-specify a list of compute capabilities, excluding version {}.'.format(ver))
  all_valid = False

This is what I had concluded after looking at the original issue...

capabilities < 3.0: TensorFlow cannot be build.
3.0 < capabilities < 3.5: TensorFlow can be build but would not work.
capabilities >= 3.5 TensorFlow can be build and works as expected.

Actually, by looking at the discussions in the issue thread, I thought that we still want to allow the ability to build TensorFlow if (3.0 < compute_capabilities < 3.5) but we simply wanted to include a warning saying "Hey, you can build with this capability, but it would not be useful". This code is in accordance with that.
I agree with what you have suggested. I don't see the point of allowing to build for capabilities less than 3.5 if TensorFlow is ultimately not usable with them. Should I proceed to make the appropriate changes?

There's no warning in the prompt for a compute capability either. Can you change it to this?
...build time and binary size, and that TensorFlow only supports compute capabilities > 3.5.

Alright, I'll include this as well.

@angersson, I have made the required changes, does the patch look okay?

FYI - as mentioned in  #26394 - it looks like TF could be build with compute capability < 3.0 if XLA is not enabled.


feat: add giot.light.v8ssm

Thanks!

https://github.com/AlexxIT/XiaomiGateway3/releases/tag/v4.0.6


Compatibility with asynchronous loading?

Hello there :)
As I'm working on a Quasar project I've been facing an issue while trying to use the library.
Quasar's particularity is to offer some SSR render, so I had to make a small tweak to load the component with defineAsyncComponent (as a basic import would break the server side).
Here's the simple component I've made up for basic testing:

<template>

  <q-no-ssr>

    <EmojiPicker :native="true" @select="onSelectedEmoji" />

    <template v-slot:placeholder>
      <q-skeleton height="48px" style="margin-top: 1rem; border-radius: 0.75rem;"/>
    </template>
  </q-no-ssr>

</template>

<script>
import {ref, defineComponent, defineAsyncComponent} from 'vue'

export default defineComponent({
  name: 'ChatInput',
  components: {
    EmojiPicker: defineAsyncComponent(() => import('vue3-emoji-picker'))
  },
  setup () {

    const onSelectedEmoji = (emoji) => {
      console.log(emoji)
    }
    return {
      onSelectedEmoji,
    }
  },
})
</script>
<style lang="scss">
// $
@import 'node_modules/vue3-emoji-picker/dist/style';
</style>

This is resulting in the component being "semi-rendered" as I see in HTML <picker-root type="" text=""></picker-root>, and I also have those two warnings in console :
[Vue warn]: provide() can only be used inside setup().
[Vue warn]: resolveComponent can only be used in render() or setup().

Would you have any idea about why it occurs, or how to load the component asynchronously?
I've also tried to setup a server-only boot file for Quasar like the following (but it didn't help either, giving the same result/warning):
import { boot } from 'quasar/wrappers'

export default boot(async ({ app }) => {
  const EmojiPicker = require('vue3-emoji-picker').default
  app.component('EmojiPicker', EmojiPicker)
})

Thanks in advance for any piece of help and have a great day!

@Nincha did you solve your problem? i current having a problem in nuxt, where the whole app breaks in production with this lib. I have tried using , kind of your , but no success

Same here


Inconsistent results from ASAP across application restarts

I've encountered an issue with the ASAP (As-Sampled-As-Possible) smoothing algorithm implemented in JavaScript. The algorithm produces different results each time the application is restarted, despite being given the same input data. This inconsistency is not observed with other smoothing methods like Savitzky-Golay. :/ I also read your paper but what I understand is it should behave deterministic and source code https://github.com/stanford-futuredata/ASAP/blob/master/ASAP-optimized.js doesn't use some randomness.
any ideas?
Steps to Reproduce

Initialize application with a fixed dataset
Apply ASAP smoothing to the dataset (by using smooth )
Record the output
Close and restart the application
Repeat steps 2-3
Compare outputs from different runs

Expected Behavior
The ASAP smoothing algorithm should produce consistent results given the same input data, regardless of application restarts.
Any ideas? I m just using it like that:
const applySmoothing = useCallback((inputData: ReadonlyArray<number>, targetRes: number): number[] => {
  try {
    return smoothFunction(Array.from(inputData), targetRes);
  } catch (error) {
    console.error('Error in smoothing:', error);
    return Array.from(inputData);
  }
}, []);

const [dataSet1, dataSet2, label1, label2, metric, axisRange, pageCount] = useMemo(() => {
  const sourceData = useUnprocessedData && fullData ? fullData : processedData;
  let d1: number[], d2: number[] | null, l1: string, l2: string, m: number | null, range, total: number;

  // ... (switch case for different modes)

  if (useUnprocessedData && fullData) {
    // ...
  } else {
    const targetRes = 100;
    d1 = applySmoothing(d1, targetRes);
    if (d2) d2 = applySmoothing(d2, targetRes);
    total = 1;
    setStartIndex(0);
    if (currentMode === "comparisonMode") {
      m = calculateCorrelation(sourceData.subject1.metric, sourceData.subject2.metric);
    } else {
      m = null;
    }
  }
  range = calculateAxisRange(d1, d2);
  return [d1, d2, l1, l2, m, range, total];
}, [processedData, fullData, useUnprocessedData, currentMode, currentPage, itemsPerPage, calculateAxisRange, applySmoothing]);

my fault :-(
I had my doubts whether this filter was detereministic or not, as there was some order confusion when loading the huge DB! I did very detailed tests and it passed them all!
I'm still happy that these tests revealed problems in my main code haha.
cheers!!

Thanks for your interest and glad to hear that you resolved the problem. Have fun =)

Thanks for your interest and glad to hear that you resolved the problem. Have fun =)

Thank youuu! And for your contributions to making this complex thing as open source, it really helps a lot!!


Menu Items not accessible

The menu items (ie. MenuLabel, MenuButton etc) of a menu is not accessible, is this on purpose? How am i supposed to change menu content dynamically? Am i missing something, or is it just not implemented yet?

@Frede1012  do you mean like this?
MenuLabel playerMenuLabel = new MenuLabel("Categories", true);
playerMenuLabel.UnderlineColor = Color.LimeGreen;
My problem is "MenuToggle" don't remember there current state and always default to OFF am i missing something here?

P.S if MenuButton and MenuToggle could take functions with parameters would neaten up code alot.

I added ListMenu for dynamically generated menus
I will add properties for accessing the value of elements and more ways of passing actions. Thanks for the suggestion.
But I want to know what you guys think, is direct access to Menu's elements needed? Or should ListMenu do the job?

You could just use lambda expressions, store it in an Action and there you go.
Credits to @StijnBrouwer.

@StijnBrouwer Gimme a sec, i have been working a bit on it. Let me test, commit and then i'll comment here again :)

@Frede1012 Okay, nice.

Does the tweening when removing a specific menu work too?
Oh, and change those variable names! The m prefix is only for private members.

@StijnBrouwer Check my fork (newest commit). https://github.com/Frede1012/scripthookvdotnet/commits/master
I cleaned up the public menu properties :)

Looks good, have you tested it yet?

Yes, it seems to work absolutely fine. However, i seem to have some graphical problems with the menus on my pc. I guess they aren't supposed to be flashing and purple? :P

Did they flash before you made the changes?

@StijnBrouwer Yep, they have been acting weird all along.

Okay, then it's fine.
RIP your graphics card though

@StijnBrouwer What do you mean?

@Frede1012 Flickering textures and those kind of things are often a sign that your graphics card is dying. But I don't know if that's the case. Really weird...

@StijnBrouwer This graphics card is fairly new, and nothing else is flashing :P I hope its not that..
Anyway, i will submit a pull request and add it in a few, ok?

@Frede1012 Go ahead

Issue is fixed in #89 (waiting for approval)

I have made some changes in https://github.com/StijnBrouwer/scripthookvdotnet/tree/properties that add value accessors to MenuItems and an update function to Menu. (because just an accessor for the Menu's item list, like it is currently, obviously doesn't work)

I'm going to test it first before pull requesting though, so it might take some time.

@StijnBrouwer Can't we remove the UpdateText function completely and update the text on Draw()?

My idea was to keep UpdateText, but make it private and automatically called when data gets changed.

@StijnBrouwer Thats a good idea as well :P


remove trailing '/' from repo url for baseFolderName

Fixes #75574
Problem:
When using the git clone command, if a given repository URL has a trailing '/', the repository baseFolder name would get set to default ("repository"). In determining the folder name, a series of regex replaces is done to remove all but the repository name from the URL. If the trailing '/' is present, the first replace will remove the entire string, thus defaulting the folder name.
Solution:
Remove all trailing '/' before we do the other regex removals. This ensures we get a repository name for valid repository URLs that have a trailing '/'.

Isn't better to reduce regex as much as possible and simply use this approach?
let url = 'github.com/microsoft/vscode/';
if (url.endsWith('/')) {
  url = url.slice(0, -1); // == github.com/microsoft/vscode
}

@svipas Regex is awesome. Besides being performant it is concise and expressive.

@ozyx Thanks! :beers:


Possibility to define additional containers

Is your feature request related to a problem? Please describe.
We are operating emqx broker together with a companion container for cloudsql-proxy.
Describe the solution you'd like
Because of this, it would be very useful to be able to specify additional containers in the EmqxBroker crd.
Describe alternatives you've considered
Can't think of an alternative atm.

Hi, @mariusstaicu Thanks for your feedback, maybe we can add containers for .spec in emqx custom resources, what do you think?

yes, would be great

Cool, we will finish it

amazing, thanks


Allow when user has only a subnet route

[x] read the CONTRIBUTING guidelines
[x] raised a GitHub issue or discussed it on the projects chat beforehand
[x] added unit tests
[ ] added integration tests
[ ] updated documentation if needed
[ ] updated CHANGELOG.md

Fixes #1604

Looks reasonable, one nit.


[CELEBORN-569] Update netty version to 4.1.92.

What changes were proposed in this pull request?
Update Netty version to 4.1.92. According to Netty's release note, this shall introduce some performance benefits.
Why are the changes needed?
Ditto.
Does this PR introduce any user-facing change?
NO.
How was this patch tested?
UT.

Regression is successful.

Is it back-compatible with 4.1.77.Final? Client side might use the older version.


Remove ignored dataset.eager() calls

When calling dataset.eager().first, the eager call is ignored by sequel.
Eager loading is intended for loading multiple objects. One can make use
of eager loading also for a single object, but this makes limited sense
(i.e. same amount of SQL queries) unless there is a callback passed to
customize the eagerly loaded dataset. To use eager loading on a single
object, one has to call dataset.eager().all.first.
Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

An explanation of the use cases your change solves

Links to any other associated PRs

[ ] I have reviewed the contributing guide

[ ] I have viewed, signed, and submitted the Contributor License Agreement

[ ] I have made this pull request to the main branch

[ ] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

Thanks for cleaning these up.


3-arity of map-columns fails

(-> (ds/->>dataset {:a [0 1]
                               :b [1 2]})
    (map-columns :y  (fn [x y] (+ x y))))

-> Exception
How am I supposed to use the 3-arity form of map-columns ?
No column selector can only mean all columns ,does it ?
If yes, an arity-2 map function should work

3-arity map-columns maps only one selected column. (map-columns ds :y f) is the same as (map-columns ds :y :y f).
For your case you should call (map-columns ds :y :all f)

Thanks for info. I guess we can close it.


fix(TDI-39006) : correct behavior for dedupeEnabled

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-39006
What is the new behavior?
Correct behavior when dedupeEnabled is checked.
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:

Why unit test is missing for this modification ?

Pull request test result: success :star:

UTs not so easy with REST/SOAP clients but IT already exists on the subject. As they're disabled (ITs) didn't catch that case.


container to reuse dom elements

Reusing dom elements make the them compatible with previous events and bindings

This really helped a lot! Thanks!


Simplify Readme / Build / Quickstart

Issue type
Readme.md isn't ideal
Akash version
N/A
What happened
The build did not build :)
What did you expect to happen
How to reproduce it
Uncertain, might have been go env related, but fact is it's going to be more reliable for people to git clone then make

#1223
Might not fully close this, but it's a good start.

Should add some deploy snippets and try to get deploys made easier, perhaps by wrapping the existing deploy tooling.

PR has been merged, thanks for the contribution


Adding "DevelOne Coin" Token

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:FTLXmxXJBNaDcuRSqbCP5PVAwvy98keY6un5zFugVh8a
Token Name:DevelOne Coin
Token Symbol:DEVO
Logo: https://github.com/MaxVegtam/develcoin/raw/main/a.png
Link to the official homepage of token:www.develone.com
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 can help refer this zakimzf/profile#1
PS: if you don't need my help.. please ignore this!


[WiP] Update axios,ajv, primjs,urijs

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