[MXNET-99] Upgrade to cuda 9.1 cudnn 7

Description
This PR upgrades our CI from CUDA 8.0 to CUDA 9.1 and CuDNN from 5 to 7.
Checklist
Essentials

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

CUDA 8.0 -> 9.1
CuDNN 5 -> 7

Comments
This change requires an update on our slaves because CUDA 9.1 is not supported by nvidia-docker. It requires nvidia-docker2. This upgrade will be done as part of the auto scaling effort anyways, so we'll have to wait with this upgrade until then.

How about keeping both?

This would increase maintenance efforts and result in a lot more jobs and thus more costs. We should try to prevent mixing integration tests (in that extent) with PR validation.

We still need a way to track changes that break cuda/cudnn compatibility. For example, when depth-wise convolution was added, a low-level shuffle intrinsic was used in the implementation, which is not supported in sm_20 (as in the symbol doesn't exist for sm_20). This broke the build because sm_20 was still enabled at the time.
A good place to put verification is nightly test. Given that eventually the nightly test would be moved to the public CI, the maintenance efforts need to be put in sooner or later. It would be good if we take that into consideration.

It does in fact because 2.x architecture is deprecated with cuda 9. But I
agree, integration tests before a release would be the way to go here.

Hello, I have just finished working on this PR. It would be great if somebody could review and approve it. This would allow me to self-merge the PR while everybody in the US is asleep - that way, we won't have any interruption of development due to downtimes.


Ensure optional blobs in artifact manifest

Closing as confirmed that blobs can be null. (See https://github.com/oras-project/oras-go/blob/main/pack.go#L166-L168 and https://github.com/oras-project/oras-go/blob/main/content/graph.go#L85-L87)


:bug: Update the enabled check for the Analysis button

On the application table, update the analysis button's enable/disable check such that analysis is only allowed to be started when all of the tasks for the selected applications are in a terminal state (they are not in-flight/queued).
Fixes: #1976

##Screen Shots
Analysis button enabled when the selected app doesn't have a task:

Analysis button disabled when one of the selected apps has a queued task:

Analysis button enabled when selected an app whose previous task is complete:


Redesign set password and biometrics

For redesign UI Wireframe PassCode and Biometrics
What are the features added for compose?

Passcode (UI & settings preferences)
Biometrics (UI & settings preferences)
Dark Mode (UI & settings preferences)
Language Picker (UI & settings preferences)

This is not your wallet

@Getbook1 Please our team very hard. We don't tolerate trolls.  Please apologize

Sorry for the long delay....finally getting back in @josikie

It's ok @kcw-grunt


EventExecutorGroup lightweight progress metrics

Motivation:
EventExecutorGroup doesn't allow to monitor submitted and completed
tasks.
Modifications:
JCtools QueueProgressIndicators exposes lightweight progression metrics:
if an executor is using a proper tasks queue, it will expose such
metrics for free.
MultithreadedEventExecutorGroup can expose global metrics (collected
using children metrics) or fine-grain ones (per-child).
Result:
An external observer can easily monitor executors utilization
without affecting executor performance.

It is connected to https://github.com/netty/netty/pull/9025: the implementation must be refined and probably I need to add some tests, but I want to receive some feedback about this feature, given that is mostly for-free while adopting JCtools queues :+1:

I've prepared a simple reporting thread on BurstCostExecutorsBenchmark to show a possible usage and that's the output:
Duration 1001ms - Submitted 24,007,891 evt - Completed 24,007,879 evt
Duration 1001ms - Submitted 23,947,185 evt - Completed 23,947,314 evt
Duration 1001ms - Submitted 23,982,939 evt - Completed 23,982,888 evt
Duration 1000ms - Submitted 23,661,554 evt - Completed 23,661,474 evt
Duration 1001ms - Submitted 23,251,822 evt - Completed 23,251,874 evt
Duration 1001ms - Submitted 23,004,516 evt - Completed 23,004,467 evt
Duration 1001ms - Submitted 23,775,207 evt - Completed 23,775,221 evt
Duration 1001ms - Submitted 24,089,328 evt - Completed 24,089,317 evt

This is an interesting idea...
@vkostyukov WDYT ?

@netty-bot test this please

@normanmaurer I've introduced an API changes that should make the test to fail: this PR is mostly a WIP to understand if such metrics are interesting (given that are mostly for free :P)

We use pendingTasks to monitor the business of event-loops in. I'm trying to understand what additional insights these methods can bring to us - I'm not really seeing an immediate value at this point.
@franz1981 Any chance you can help me with the example? What are these could be used for where pendingTasks can not?

@vkostyukov pendingTasks will give you anothe metric: which tasks are being submitted but not yet executed (not really, but something like  (submitted - completed) and given that submitted tends to happen in bust, if you sample the pending tasks each seconds is likely to be near 0 most of the times.
These metrics instead provides additional insights as "in the period of time what is the throughput of the submissions" ie submitted(t) - submitted(t-1).
Not sure if the explanation make it clear how much is different.
It will helps to know which event loop receive more works and which ones are fast enough to completed them...

@franz1981 I think this is a great POC and wouldn't harm to add (with the inline comment caveat), however as commented on the related PR most useful imo would be to work backwards from the kinds of parameters that may make sense to tune (i.e. those which have most impact on the efficiency/perf) and from that determine which corresponding metrics would be most useful to capture/expose (which might end up being some derived combo based on these counts somehow for example). That could pave the way for possible adaptive config in future.
In other words, how would regular users use these numbers to concretely determine the number of event loops to have in their group(s), etc.

@njhill

In other words, how would regular users use these numbers to concretely determine the number of event loops to have in their group(s), etc.

Not easy to answer; probably allowing the user to inject telemetry in order to get:

task latencies distribution depending on task type (networking/scheduled/common tasks)
number of wakeups performed into the event loop and outside ie on task offer
latency distributions of wakeup time (from a select())
etc etc

The main idea is to provide callbacks to allow user to do what they want (while avoing Netty prj to contain external unnecessary dependencies) and at least provide some basic useful telemetry eg:

pending, submitted, completed events
TODO wakeup performed into the event loops
etc etc

I would let the users ingest the pills of seme heavyweight telemetry (in the form of some callback as onSleepCompleted(selectedKeys))

I can imagine this could be useful for measuring the "throughput" of your IO threads. Having just pending tasks wouldn't be enough for that.
I'm +1 for this we can keep it binary compatible.

I need to change this without affecting public API and add tests: will try to do it this week :+1:

@franz1981 what is the status of this one ?

@normanmaurer I still need to expose it without changing API and it could be reviewed. No idea which type of tests I can provide for this, need to think about it...
This week I have a huge backlog at work due to the long honeymoon, but will try to get some free cycles to work on this :+1:

Hi, this pr looks good. We are currently working on a Netty layer monitoring. In our scenario we need three types of data:

The pressure of the Reactor thread (it seems that this PR code can reflect this problem)
Reporting of resource leaks (Error log is not enough for us)
TCP channel back pressure

Often, there are a lot of things we have to doubt when troubleshooting a problem. This data can help us to rule out the anomalies that exist in the Netty layer. I hope that we can eventually have similar capabilities.

@carryxyh thanks! I still need to take care of not changing the public API: I'll try to work on it by the EOD (that's in 9 hours from now). Let me know If you've already tried this branch for your tests and if the API seems appropriate for your use case (that seems the motivation of this PR) :)

Hi, I haven't tried it yet. But the motivation for this pr is what we need. I am very much looking forward to its completion. :)

@vkostyukov @carryxyh If you wanna give it a try, it should be able to be used without directly modifying a public API (I've used a "dirty" trick I admit, let's see if is fine ;))
@nitsanw This is making use of something specific of JCTools: any objection/comment/proposal is welcome :)

@franz1981 LGTM, I would suggest making double sure that the interface works as expected for the relevant queues as it's not a commonly used one. I'll add some tests to JCTools just in case.

@njhill @normanmaurer I'm now looking if I should add some tests for this, although Nitsan has already added JCTools/JCTools@543ea11: let me know if you prefer better naming or other stuff :)

@njhill @normanmaurer
AFAIK now it shouldn't break any (broken) compatibility check and we already have some checks on JCTools re QueueProgressIndicators: the only thing that's lacking are tests, do you think are needed for this?

@franz1981 will review soon.. sorry for the delay.

@normanmaurer np I've taken lot of time as well to get here too :)
OT: when the PR of Nitsan re JCTools 3 will land I promise to start some experiment to see if there is some benefit using the new xadd qs on Netty ;)

@normanmaurer how it looks? I mean, it's breaking some compatibility now?
Probably need to add some test on this, if it got accepted :)

@franz1981 can you rebase it ?

Oh, seems this PR is stale. @franz1981 Would you mind to update it? Or I will be happy to help with it

Oh, seems this PR is stale. @franz1981 Do you have plans to update it? Or I will be happy to help with it

No plans yet and would be happy if you would like to pick it :)


[CLI] urllib3>=1.26.5 in the requirements.txt can't run in my computer

Description
As pointed out by this issue, the  wandb error (check_hostname requires server_hostname) occurs when urllib3>=1.26.5
Wandb features
I'm using PyTorch Lightning with wandb integration to log. And I also use the wandb.init() to do something else.
How to reproduce

Link to a reproducible script we can run to see the bug.

src_folders = [
    r'C:\SIM-Data\20210715\1',
    # r'C:\SIM-Data\20210715\2',
    # r'C:\SIM-Data\20210715\3',
    # r'C:\SIM-Data\20210715\4',
    # r'C:\SIM-Data\20210715\5',
]
image_num_every_sliceZ = 117

# wandb log
wandb.init(project="test20210701")  # logging experiment parameters
wandb.run.name = time.strftime("%Y-%m-%d-%H-%M-%S", time.localtime())
wandb.config.update({"src folders": src_folders,
                     "image nums per z slice": image_num_every_sliceZ,
                     })

Describe what we have to do in order to trigger the issue
Because urllib3=1.25.11 works well for me, I think it is supposed to be pointed out in the doc(or somewhere else) to prevent such error when urllib3>=1.26.5

Environment

OS: [e.g. window10]
Environment: [e.g. pycharm ]
Python Version: [eg. 3.8.10]

The question is  a proxy issue with urllib3, which didn't support HTTPS before v1.26 and would silently connect to the proxy via HTTP.
The answer is to change HTTPS_PROXY=https://<host> to be HTTPS_PROXY=http://<host>. For more details, please see here


Fix histogram zr handler

Description
Shortcut: 322439
[sc-322439]
HistogramWidget fix, broken after adding skeleton (missing ref in object when dealing with echart events, through ZRender lib)
Type of change

Fix

Acceptance
HistogramWidget doesn't break. You can move around the map and it correctly manages skeleton on-off
Basic checklist

Good PR name
Shortcut link
Changelog entry
Just one issue per PR
GitHub labels
Proper status & reviewers
Tests
Documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 7 (57.14%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 71.399%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/react-ui/src/widgets/HistogramWidgetUI/useHistogramInteractivity.js
3
4
75.0%

packages/react-ui/src/widgets/TimeSeriesWidgetUI/hooks/useTimeSeriesInteractivity.js
1
3
33.33%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
2210

Relevant Lines:
2861

💛  - Coveralls


Unable to push or pull duplicate rules starting with CLI version 50.1.1

Summary
Starring with the Winter '21 CLI update (50.1.1), we are unable to push or pull duplicate rules.
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc

Establish a scratch org per the steps in the dreamhouse readme file
Create a duplicate rule in the dreamhouse scratch org. Here are the values I used:

Execute the force:source:pull command

Expected result
The duplicate rule will be pulled into the project
Actual result
The duplicate rule is not pulled into the project:
> sfdx force:source:pull
=== Pulled Source
No results found

Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.76.1-f301d5641f darwin-x64 node-v12.18.3
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.1 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.4.3 (core)
alias 1.1.2 (core)
analytics 1.12.1 (core)
config 1.1.9 (core)
generator 1.1.3 (core)
salesforcedx 50.1.1 (core)
├─ templates 50.1.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
├─ custom-metadata 1.0.10 (core)
├─ apex 0.1.1 (core)
└─ salesforce-alm 50.1.1 (core)
sfdx-browserforce-plugin 1.7.3
sfdx-cli 7.76.1 (core)
sfdx-wry-plugin 0.0.11 (link) /Users/walkej/Documents/sfdx-wry-plugin

OS and version:
MacOS 10.15.6 (19G2021)

Thanks for the detailed report and reproducer.  We'll get it fixed.

Is there any workaround to fix this? @shetzel ?
@jwalke

Is there any workaround to fix this? @shetzel ?
@jwalke

We're using a previous version of the CLI / sfdx plugin in our pipelines until this gets resolved. Instructions for installing a previous version can be found in this article.

Thank you @jwalke, you saved us <3

@shetzel is there any ETA you can share for this fix?

@thvd - looks like it missed the cutoff for the current release candidate, which would make it an ETA of next week's RC and the following week's release (salesforcedx v50.5.0, Nov 12).

@jwalke @thvd @leonardopmacedo - Another workaround should be to add # .forceignore v2 to your .forceignore file so that only the new parser is used.  As it turns out, duplicate rule metadata is being ignored by a default forceignore rule with the old parser.  You will need to be on a later CLI version (or salesforcedx plugin) for this workaround to work.  Apologies for this regression!

@shetzel
Do you have already a date for the fix?
greetz,
Floris

@shetzel I was on v50.5.0 and it wasn't pulling duplicate rules so I rolled back to 49.13.0 but that isn't working either.  Any idea when the fix will be released?  Thanks

@edralph - we're trying to get the fix into the next RC (and we're behind schedule in getting that out), which would make it in production this coming Thursday.  However, adding # .forceignore v2 to your .forceignore file should definitely work around the issue (as should rolling back plugin versions) so if that's working for you then there's something else specific to your environment that is causing it to fail.  Temporarily moving the .forceignore file should also work, but obviously that has downsides too.

However, adding # .forceignore v2 to your .forceignore file
@shetzel Silly question... should I include the #?  Doesn't that just comment it out?

@edralph - yes, you include the #
You can try the fix by installing the current release candidate.  sfdx plugins:install salesforcedx@latest-rc

@shetzel  got this:
ErrorGettingContent: A request to url https://developer.salesforce.com/media/salesforce-cli/signatures/salesforcedx-50.6.0.sig failed with error code: [403]
Thanks for helping

I've never seen that error before.  I'd completely remove the CLI, re-install, then try again.

@edralph got the same error for salesforcedx@latest-rc but sfdx plugins:install<EMAIL_ADDRESS>worked for me

@edralph - actually the 403 error you saw when trying to install the latest-rc is a bug we need to fix with our plugin signing.  We're working on it.  The fix for this issue is in the latest production version though so closing this issue.  To get the fix for this issue you can just sfdx update

Just ran the update and it pulled the duplicate rule thank you!

I am getting the below error when creating package version..


Enable ppc64le/aarch64 builds

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

@conda-forge/core Gotta re-render issue on this one.

@dschreij FYI

Got it! Merged. Thanks @jayfurmanek


HELM-377: Remove Angular Code

Remove all Angular code from HELM.
Rename the React datasources and panels to not have React or -react.
External References

JIRA (Issue Tracker): https://opennms.atlassian.net/browse/HELM-377
Continuous Integration: CircleCI

Need to fix the SonarCloud items and then also rebase to get latest bug fixes.

@synqotik
Sonar's complaints about this are probably valid. What kind of thing are you trying to parse out with this?
    { name: FlowTemplateVariablesStrings.interfacesOnExporterNodeWithFlows, expression: /interfacesOnExporterNodeWithFlows\(\s*([^,]+).*\)/

...That's going to match 0 or more spaces, anything that's not a comma greedily, but then also anything else, greedily. Is it always gonna be something with more than one argument? (ie, at least one comma?)
If so, you could do this to make it a little less CPU-intensive:
    { name: FlowTemplateVariablesStrings.interfacesOnExporterNodeWithFlows, expression: /interfacesOnExporterNodeWithFlows\(\s*([^,]+),[^\)]+\)/

or, if it can either be a single argument or one with a comma, you probably need to do a bit more work.
Either way, for things that are matching foo(blahblah) I really like using [^\)]+ to match everything up to the closing paren. That limits the amount of work the regex engine has to do rather than looking for "anything" and trying to backtrack.

@synqotik
Sonar's complaints about this are probably valid. What kind of thing are you trying to parse out with this?

This wasn't code I touched, I suspect Sonar is analyzing it now since things have been renamed. I will take a look at your suggestion and make a fix.

@synqotik
Sonar's complaints about this are probably valid. What kind of thing are you trying to parse out with this?

This wasn't code I touched, I suspect Sonar is analyzing it now since things have been renamed. I will take a look at your suggestion and make a fix.

Ah, alright, well if sonar blocks merging, I can do it as an admin. Probably still worth fixing though. :D


Incorrect snippet !!template

Basic informations

OS: [Windows]
VSCode version: Latest
Extension version: Latest

Further Information
When trying to use a snippet !!template show errors in the public Plugin myinfo due to the use of ' ' and not " "
Before:

After:

To Reproduce

Try to use it !!template snippet
ВWe see errors in the public Plugin myinfo

Expected behaviour
Correct public Plugin myinfo block
Error messages
invalid character constant
One likely cause for this error is the occurrence of an unknown escape sequence, like “\x”. Putting multiple characters between single quotes, as in ’abc’ also issues this error message. A third cause for this error is a situation where a character constant was expected, but none (or a non-character expression) were provided.

Thanks for reporting but why did you close #235 ?

I was able to solve the problem. #237


Create genetic associations detail view

It will contain:

Table
Browser

Waiting for confirmation from @andrewhercules and @MichaelaEBI on what the table should look like

There was a preliminary discussion around combining the Common diseases and Rare diseases data tables. However, I think that given a recent Slack conversation, the two tables should remain distinct - see below:

I would also recommend that we leave the Common diseases data table as it currently is because there are few cases of n/a or unknown.
However, for the Rare diseases data table, I propose that we create two different tables depending on the source of the data:
Table 1: EVA, UniProt
Table 2: Gene2Phenotype, UniProt literature, Genomics England
Based on a cursory glance of the evidence, we do not get the mutation, mutation consequence, or clinical significance values for an evidence string from Gene2Phenotype, UniProt literature, or Genomics England. This leads to tables full of N/A and Curated evidence values.
For example, https://www.targetvalidation.org/evidence/ENSG00000213614/Orphanet_845?view=sec:genetic_association and https://www.targetvalidation.org/evidence/ENSG00000134460/EFO_0000540?view=sec:genetic_association.
@iandunham and @d0choa, would this make sense from a scientific perspective? Or would it preferable that the data remain in a single table?
Ian, in a recent FE meeting, you had mentioned that part of the reason behind N/A is that we may get that information from a data provider. Would this be the case for the three data providers that I have identified as suitable for a second, curated evidence Rare diseases data table (Gene2Phenotype, UniProt literature, Genomics England)?

@andrewhercules @d0choa @iandunham, I'd vote for the data to remain in a single table and the reasons are several fold (in no particular order)

We are not capturing rsID from Gene2Phenotype (G2P) or Genomic England PanelApp, hence N/A in the table

These two data sources are curated by clinicians who don't tend to work with rsIDs. But we could map the HGVS notation to rsID and display the rsID in the table and the functional consequence, dropping the "curated evidence" placeholder.
From one of links included by @andrewhercules, we can see that G2P provides one evidence for HEXA in Tay-Sachs disease.
From the G2P link, we can go to Decipher and get more info on the G2P variants:

The two variants above do not have a dbSNP notation e.g. rs123, rather a HGVS notation, which is popular among clinicians and diagnostic labs. So we have p.Arg137Ter, which translates into:stop codon Ter at amino acid position 137, where the reference codon is Arg. The variant (or mutation) truncates the protein and this is likely pathogenic.
Is there an rsID for p.Arg137Ter? Yes, there is:
http://grch37.ensembl.org/Homo_sapiens/Variation/Explore?db=core;g=ENSG00000213614;r=15:72635775-72668817;t=ENST00000268097;v=rs121907962;vdb=variation;vf=445749705
This means this variant (mutation in this case) should have an rsID (rs121907962) and a functional consequence (stop gain). Decipher gives a clinical significance as well, which could be pulled in by the Platform (clinical significance is available from ClinVar but G2P and Decipher as well, probably GEL too).
If the HGVS notation is provided in the G2P JSON file, we can use Ensembl VEP REST API endpoint to find the rsID and the functional consequence. Note G2P coordinates are for GRCh37. This'd mean that we will no longer have N/A and "curated evidence" in the table, but rs121907962 and stop gain instead.

rs123 does not mean the evidence is not curated
rs121907981 is an evidence for HEXA in Tay-Sachs disease that is curated by UniProt. The VEP says this variant is a missense variant, but it is still curated evidence.

I see the string 'Curated evidence' in our tables as a placeholder for when we don't have information on the functional consequence of the variant/mutation.

Data Download
If we were to split the rare diseases table into two, this would mean that users interested in that data would have to download two rather than one table.

Consistency
If we split rare diseases table in two, will we split Common disease table as well? How about other tables in the evidence page e.g. Somatic mutations? These could also have with different data sources and N/A in some rows e.g.

https://www.targetvalidation.org/evidence/ENSG00000139618/EFO_0000305?view=sec:somatic_mutation

UniProt versus UniProt literature
These two subtypes are available as filtering options in the associations page but not captured in the evidence page: we can filter for UniProt in the Evidence source column but we can't tell if it's UniProt literature.

Scrolling
Some users do miss the second table already due to the need to scroll further down. Splitting one table in two will require further scrolling. This can increase the chances of users missing relevant information.

I think that the reason that gene2phenotype exists is that the variant information cannot be viewed or download outside of the terms of access of Decipher. We can't display the variants in the platform, which would include reverse engineering by scraping data from DeCipher. What we could do if we don't already is to have a link back to the page.

'Curated evidence' means that the evidence we are displaying is a summary evidence generated by a curator which may have background supporting variants, but is aggregated over several variants. In the context of the functional consequence column of the table it means that the result is an aggregate over possibly multiple variants so there isn't a functional consequence at the variant level. We could try to get a summary consequence like we do for cancer gene census, but the data access is complex here.
So overall curated evidence means that there is either a person looking at the data or there is a pipeline aggregating the data to give a summary. In a sense this is higher quality than just observing a variant.
For Genomics England panels they have a crowd sourced summary of which genes should be looked at for a particular disease, without itemising variants, so agian it's a curated summary of mny views across clinicans


match_features: has_gps_info not reading gps info

I have a photoset that is georeferenced but am getting this warning when trying to run match_features:
WARNING:__main__:Not all images have GPS info. Disabling matching_gps_neighbors.
It comes from this part of the code:
https://github.com/mapillary/OpenSfM/blob/master/bin/match_features#L48
The call all(map(has_gps_info, exifs)) is returning false, even though all the photos have gps exif tags. I can't figure out exactly what is going on, but I think map() is not properly passing the exifs dictionary to has_gps_info

There was a bug on that line indeed. The map is iterating over the keys of the dict instead of the values. Just fixed it. Thanks!


dl should not be a required library on Windows

libdl doesn't exist on Windows (to the best of my knowledge)
https://github.com/cvanaret/Uno/blob/main/CMakeLists.txt#L149-L150

Indeed it seems that dlfcn.h is not used, so it make sense to remove this. Anyhow, just if someone finds this issue on github, there is a dl implementation for Windows at https://github.com/dlfcn-win32/dlfcn-win32 .

I now use CMAKE_DL_LIBS instead of looking for the dl library (and only for the uno_ampl target).
This should be fixed in commit 3bd2244.

Thanks @cvanaret, it fixed the issue on Windows :+1:
Can you also add the compilation flag -fPIC by default when you compile Uno please?


Running 'npm run electron &' errors out...

Hello guys!
me again :)
I am on the final steps here of setting up a full node + farmer + harvester + wallet on CentOS 8 (cloudlinux distro).
and I get this error when running the command:

chia-blockchain@ electron /chia-blockchain/chia-blockchain-gui
electron .

/chia-blockchain/chia-blockchain-gui/node_modules/electron/dist/electron: error while loading shared libraries: libatk-bridge-2.0.so.0: cannot open shared object file: No such file or directory
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! chia-blockchain@ electron: electron .
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the chia-blockchain@ electron script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!  It's basically due to missing dependencies. I tried to start GUI in an Ubuntu VM, and it was needed to install following packages:

libnss3
libatk1.0-0
libatk-bridge2.0-0
libgdk-pixbuf2.0-0
libgtk-3-0
libgbm-dev

I think it's matter of looking for equivalent package names for your distro.
At the end, it was not possible to launch GUI. Got this issue:

[1] 7356
chia@04c0cd323539:/chia-blockchain/chia-blockchain-gui$
> chia-blockchain@ electron /chia-blockchain/chia-blockchain-gui
> electron .

Failed to move to new namespace: PID namespaces supported, Network namespace supported, but failed: errno = Operation not permitted
/chia-blockchain/chia-blockchain-gui/node_modules/electron/dist/electron exited with signal SIGTRAP
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! chia-blockchain@ electron: `electron .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chia-blockchain@ electron script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/chia/.npm/_logs/2021-05-07T03_08_23_174Z-debug.log

[1]+  Exit 1                  npm run electron

![Screenshot from 2021-05-13 21-11-38](https://user-images.githubusercontent.com/72054890/118206142-d7af8900-b42f-11eb-9618-3b48648343a1.png
I am having a similar issue where I have installed everything. The application launches only once after install.
I have reinstalled Ubuntu 20.04 at least 5 times, maybe 8. Each reinstall the Chia GUI launches, runs for about 12 hours, then the application stops. It does not freeze, the CPU stops processing the plots. When I kill the program and try to relaunch I get the following error messages. Thoughts?


RPKI initialisation with multiple TALs does not work correctly

The documentation is wrong, too (appears to permit single TAL to be provided outside of a generator, which doesn't work).


docs: Provide release plan governance

Provide release plan governance that talks about when we ship, what our release cadence is, etc.
Discussion around a fixed release cycle was started in #24
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Fixes #23

PTAL and share if you agree on this @zroubalik @jeffhollan @ahmelsayed

We have a majority vote!


Slow Connecting...

I have the server running on a dual core and 4 GO RAM, but the problem is the time that it takes to connect to the proxy is too much, sometimes the ping is 3xxx ms. but after connecting, the speed is charming.
I have even tried to set
FAST_MODE = True
But no luck, the server is super fast at ping running other MTproto server implementations.
Anyone with the same problem or a tip?

Small workaround, you can set CLIENT_KEEPALIVE = 60*60 in config.py.
It will increase memory use and  not help with initial connect, but should increase speed of connection after.

Could you try to ping several telegram servers from your host and post the ping times. The list of telegram servers can be found on https://core.telegram.org/getProxyConfig

some ping Results:
Reply from <IP_ADDRESS>: bytes=32 time=103ms TTL=54

some ping results :
Reply from <IP_ADDRESS>: bytes=32 time=10ms TTL=56
Reply from <IP_ADDRESS>: bytes=32 time=103ms TTL=54
Reply from <IP_ADDRESS>: bytes=32 time=10ms TTL=55
Reply from <IP_ADDRESS>: bytes=32 time=173ms TTL=52

it seems the ping times are ok. The additional delay should be about 0.01-0.2 sec. May be the problem is in the ping time between the client and the proxy? Also you can increase the buffer sizes by writing TO_CLT_BUFSIZE = 163840 and TO_TG_BUFSIZE = 655360 to config.py. It should became faster at cost of memory

wow  TO_TG_BUFSIZE = 655360  did the job
now the ping is about 120 130 ms, very well, thanks :)

could you, please, send the proxy log and the data about cpu load

this should be fixed in the latest version


Adding tunables LWRP

Hello,
I created a LWRP to manage generic tunables commands ioo, vmo and schedo.
Here a example output when running the example I provided in README :
root@adxlpar1(/tools/chef)# chef-solo -c solo.rb -j test.json
[2015-08-24T17:54:30+02:00] WARN: Please install an English UTF-8 locale for Chef to use, falling back to C locale and disabling UTF-8 support.
Starting Chef Client, version 12.4.1
Compiling Cookbooks...
Converging 4 resources
Recipe: aix::default
  * aix_tunables[reset schedo values] action reset_all
    - schedo : resetting all
  * aix_tunables[change vpm_throughput_mode] action update
    - schedo: setting tunable vpm_throughput_mode=2
  * aix_tunables[change posix AIO servers] action update
    - ioo: setting tunable posix_aio_minservers=6
    - ioo: setting tunable posix_aio_maxservers=36
  * aix_tunables[tune minperm%] action update
    - vmo: setting tunable minperm%=6

Running handlers:
Running handlers complete
Chef Client finished, 4/4 resources updated in 6.027071 seconds

Running it again :
root@adxlpar1(/tools/chef)# chef-solo -c solo.rb -j test.json
[2015-08-24T17:54:48+02:00] WARN: Please install an English UTF-8 locale for Chef to use, falling back to C locale and disabling UTF-8 support.
Starting Chef Client, version 12.4.1
Compiling Cookbooks...
Converging 4 resources
Recipe: aix::default
  * aix_tunables[reset schedo values] action reset_all
    - schedo : resetting all
  * aix_tunables[change vpm_throughput_mode] action update
    - schedo: setting tunable vpm_throughput_mode=2
  * aix_tunables[change posix AIO servers] action update (up to date)
  * aix_tunables[tune minperm%] action update (up to date)

Running handlers:
Running handlers complete
Chef Client finished, 2/4 resources updated in 5.837877 seconds

Say if you want me to change anything in it.
Regards,
Alain

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@adejoux

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

@adejoux Is there anything that differ between no and ioo,vmo and schedo. If not I think we need to merge my no LWRP with this one. No need to have no for one and tunables for others.

@chmod666org Hello. Nothing. Commands parameters are identical.  I used your no module to understand how to create a LWRP so I didn't want to replace it :)

@adejoux Ok, we can keep both as both are working, users will decide what they want.
@juliandunn Is there any possibility to allow one of us managing this cookbook, we are a couple of guys working on it and we really want to contribute to this cookbook ... I think you'll have more and more pull request and we need reactivity. What do you think about it ?

@chmod666org I think we can probably do that (hand out a commit bit) and it looks like you have way more AIX experience than I :-) I am asking internally on the procedure for doing so & I'll let you know.

@chmod666org thanks but it's my first pull request and first lwrp. So I prefer to skip on managing the cookbook :) Let see if my pull request is good for now ^^
@juliandunn I am not sure if it's a good practice to define methods inside a LWRP provider. It's working here but not sure if it's something I should do.

You can define methods inside a provider but it's best to make them private.

@juliandunn OK awesome ! Thank you !
@adejoux Have methods in some of mine. Best practice is to use foodcritic before commit. (Have a look here http://acrmp.github.io/foodcritic/)

@chmod666org Thanks. I didn't know about foodcritic :) Will use it now. I didn't have any issue found in my code :)

@chmod666org I added you to the collaborators list on this cookbook and transferred it to chef-cookbooks which is where we are consolidating all cookbooks. Send me your supermarket.chef.io username and I will also add you as a maintainer so you can upload new versions.

@juliandunn Thank you for your quick answer. Just joined the organization.
My supermarket.chef.io username is chmod666org

@chmod666org ok, you can also release new versions on Supermarket.

@juliandunn Great thank you
@adejoux Will check you code asap


Is it possible to have custom status messages?

I have a shortcut that switches on and off a remap rule, it would be good to show the status of the toggle, I couldn't find any documentation on this.
My other plan originally was to use multiple profiles, where in one the remap rule is on and the other is off. Then I would enable showing the profile name in the menu bar but this was already getting too complicated since I'd probably have to use quicksilver too.

How about using notification center?
https://github.com/tekezo/Karabiner/blob/version_10.15.0/src/core/server/Resources/vkopenurldef.xml#L340-L341

Thank you for your help again, is it possible to change the message depending on whether a vk_config is enabled or not? i.e. I want the message to say "X is Enabled" and "X is Disabled" depending on the status?

I think you can use command line interface.
Please use the changed argument to determine specific config is enabled or not.
https://pqrs.org/osx/karabiner/document.html.en#commandlineinterface
For example, checking remap.mouse_keys_mode_2 state.
  <vkopenurldef>
    <name>KeyCode::VK_OPEN_URL_SHELL_my_notification</name>
    <url type="shell">
      <![CDATA[
        if /Applications/Karabiner.app/Contents/Library/bin/karabiner changed | grep 'remap.mouse_keys_mode_2=1'; then
          /usr/bin/osascript -e 'display notification "Mouse Keys Mode v2 is Enabled" with title "Karabiner"';
        else
          /usr/bin/osascript -e 'display notification "Mouse Keys Mode v2 is Disabled" with title "Karabiner"';
        fi
      ]]>
    </url>
  </vkopenurldef>

Thank you! Works

Hi suddenly this doesn't work anymore?


cant use plotter

I use: PlatformIO Core, version 6.1.7
Did this:
Windows usage with Version Core 6.1.5·Home 3.4.3
In Gui go to PLatforIO sidebar -> Select New Terminal in quick access at the bottom In the Terminal window run the following -> pip install arduplot Close the terminal or type exit
Edit the platform.ini file (with VS or your preference) add or ammend (add ,plotter if the entry line already exists) plotter to the monitor filter flag -> monitor_filters = plotter
Got this:
Executing task: C:\Users\user\AppData\Local\Programs\Python\Python311\Scripts\platformio.exe device monitor
Warning! Skipping unknown filters plotter. Known filters are colorize, debug, default, direct, hexlify, log2file, nocontrol, printable, send_on_enter,  time
--- Terminal on COM7 | 115200 8-N-1
--- Available filters and text transformations: colorize, debug, default, direct, hexlify, log2file, nocontrol, printable, send_on_enter, time
--- More details at https://bit.ly/pio-monitor-filters
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H
added folder monitor to my project folder:

@Depech101
I guess there might be some change on the PlatformIO which shows this problem of not recognizing the filter. I need to plan my time to look into this.
Meanwhile, please use arduplot command instead. Thanks.

Thank You for Your fast reaction!
But unfortunaly after moving files to folder is You said i got this:
--- serial_plotter is starting
Error: Traceback (most recent call last):
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio_main_.py", line 102, in main
cli()  # pylint: disable=no-value-for-parameter
^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1130, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1055, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\cli.py", line 70, in invoke
return super().invoke(ctx)
^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 760, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\command.py", line 152, in device_monitor_cmd
start_terminal(options)
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\terminal.py", line 54, in start_terminal
term = new_terminal(options)
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\terminal.py", line 102, in new_terminal
term = Terminal(
^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\terminal.py", line 28, in init
super().init(*args, **kwargs)
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\tools\miniterm.py", line 403, in init
self.update_transformations()
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\tools\miniterm.py", line 456, in update_transformations
self.tx_transformations = [t() for t in transformations]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\tools\miniterm.py", line 456, in
self.tx_transformations = [t() for t in transformations]
^^^
File "C:\Users\user\Documents\PlatformIO\Projects\Termorelay\monitor\filter_plotter.py", line 52, in call
self.plot = subprocess.Popen([self.arduplot, '-s', str(PORT)])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 1022, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 1491, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [WinError 2] The system cannot find the file specified
============================================================
An unexpected error occurred. Further steps:

Verify that you have the latest version of PlatformIO using
pip install -U platformio command

Try to find answer in FAQ Troubleshooting section
https://docs.platformio.org/page/faq/index.html

Report this problem to the developers
https://github.com/platformio/platformio-core/issues

============================================================

@Depech101
I installed the VSCode and PIO fresh to plan my time to work on this issue, and concluded the arduplot is working fine even with the new Python11. So fortunately the the change is not affecting the arduplot.
And looking through your reply, I found you're running the Windows default Python not the PIO bundled Python.
If you want to run the arduplot with the Windows default Python, then you need to install arduplot to that environment as well.
I guess you already know, but just to document, PIO uses a virtual Python environment. And you had installed the arduplot on to this venv.
Would you check this and let me know? Thanks.

Ok, i will do it, and I truly value your involvement! But I need to understand this things about env and so on.
As variant You can have access to my computer trough AnyDesk app.

Or give me a link for pio and stuff I will try understand with help of chatGPT it worth nothing)

It looks like you have more than two Python versions on your PC, for example, Python 3.11 installed on the Windows system wise, and Python3.9 under ~/.platformio/penv/bin for PIO(PlatformIO). Your first posting on this issue showed you installed the arduplot  on the Python3.9 environment.
So you need to open the Terminal from the VSCode project and run it. i.e.  pio device monitor -f plotter
Or open a Command Prompt from Windows start menu, install arduplot again to Python 3.11 system wise environment, and run arduplot.
Additional info:

PIO(PlatformIO) Web Site : https://platformio.org
venv stands for 'virtual environment' and it's a virtual environment for the Python. You can create many virtual environment for the Python so you can have many isolated Python environment. For example you can install library A, B, C on one environment where you run a Python script, and A, D, and older version of B on a different environment to run a different Python script since this one needs older version.

Microsoft Windows [Version 10.0.19044.2965]
(c) Microsoft Corporation. All rights reserved.
C:\Users\user>cd C:\Users\user\Documents\PLATFORMIO\PROJECTS\Termorelay
C:\Users\user\Documents\PLATFORMIO\PROJECTS\Termorelay>pio device monitor -f plotter
--- serial_plotter is starting
Error: Traceback (most recent call last):
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio_main_.py", line 102, in main
cli()  # pylint: disable=no-value-for-parameter
^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1130, in call
return self.main(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1055, in main
rv = self.invoke(ctx)
^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\cli.py", line 70, in invoke
return super().invoke(ctx)
^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1657, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\click\core.py", line 760, in invoke
return __callback(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\command.py", line 152, in device_monitor_cmd
start_terminal(options)
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\terminal.py", line 54, in start_terminal
term = new_terminal(options)
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\terminal.py", line 102, in new_terminal
term = Terminal(
^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\platformio\device\monitor\terminal.py", line 28, in init
super().init(*args, **kwargs)
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\tools\miniterm.py", line 403, in init
self.update_transformations()
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\tools\miniterm.py", line 456, in update_transformations
self.tx_transformations = [t() for t in transformations]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\site-packages\serial\tools\miniterm.py", line 456, in
self.tx_transformations = [t() for t in transformations]
^^^
File "C:\Users\user\Documents\PLATFORMIO\PROJECTS\Termorelay\monitor\filter_plotter.py", line 52, in call
self.plot = subprocess.Popen([self.arduplot, '-s', str(PORT)])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 1022, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\user\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 1491, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [WinError 2] The system cannot find the file specified
============================================================
An unexpected error occurred. Further steps:

Verify that you have the latest version of PlatformIO using
pip install -U platformio command

Try to find answer in FAQ Troubleshooting section
https://docs.platformio.org/page/faq/index.html

Report this problem to the developers
https://github.com/platformio/platformio-core/issues

============================================================
C:\Users\user\Documents\PLATFORMIO\PROJECTS\Termorelay>

Got this:
Executing task: C:\Users\user\AppData\Local\Programs\Python\Python311\Scripts\platformio.exe device monitor
How can I change it to Python3.9?

In order to use the PIO bundled Python, you need to open the terminal from the VSCode with the Project open. That is

start VSCode
open the PIO project
open the terminal by clicking the terminal icon as below.

Then, you can run either arduplot or pio device monitor -f plotter
And if you want to know which version of Python you're running, just type pip -V, then you will see the actual pip that matches the Python
Hope this helps.

Thank you! Here what i got:

@Depech101
Close the terminal, and open a terminal again with the VSCode status bar icon and see if it change.
The proper one should look like
C:\User\user\.platformio\penv\lib\python3.9\site-packages\pip (python 3.9)
Otherwise please take a look at the PIO document and reinstall VSCode and PIO.

PS C:\Users\user\Documents\PlatformIO\Projects\Termorelay> py -0p
-V:3.11 *        C:\Users\user\AppData\Local\Programs\Python\Python311\python.exe
-V:3.10          C:\Users\user\AppData\Local\Programs\Python\Python310\python.exe
-V:3.9           C:\Users\user\AppData\Local\Programs\Python\Python39\python.exe

Close the terminal, and open a terminal again with the VSCode status bar icon and see if it change.
why should it change if I didn't changed it?
The proper one should look like
C:\User\user.platformio\penv\lib\python3.9\site-packages\pip (python 3.9)
Otherwise please take a look at the PIO document and reinstall VSCode and PIO.

Please refer to the documentation of a python and the PIO.

Oh thank you, I will


typeid failed on fused types

# cython: language=c++
# cython: language_level=3str
from libcpp.typeinfo cimport type_info
from cython.operator cimport typeid
cdef fused C:
   int
   object
cdef const type_info* i32 = &typeid(int)
cdef f(C x):
    cdef const type_info* a = &typeid(C)
    return a  == i32

def g(x):
   return (x, f(x))

It's generally helpful in bug reports to also show the error message that results, as well as other relevant information, such as the code that was generated. Providing this information reduces the time that others need to plan to invest in order to investigate the issue. Basically, when I have limited time and an issue seems more costly to look into than what I currently can (or want to) invest, I look at other issues first.

Okay, will do this


use consts for Fx8 1 / 2, and use Fx8 for hitbox

use the newly useful (https://github.com/microsoft/pxt-common-packages/pull/1015) constants in physics, and also store hitbox as Fx8 instead of going back and forth all the time

Good to go!


Ensure that manifest.yml uses the app_domain property instead of the system domain to deploy the notifications app to CF

Greetings,
We are currently deploying Notifications in a CF environment that has a distinct domain for the system (api, etc) and another domain for apps.  It seems that the template for manifest.yml was using the system domain to try and deploy the app, and caused the application deploy to fail.  All we have to do is just change manifest.yml so it uses the app_domain property.
Let me know if you have any questions / concerns - Thanks!
Jeremy

Good catch. Thanks!


version update 1.0.0

Should we also remove the beta section from the readme?
https://github.com/adobe/aepsdk-edge-ios/blob/73489cbef9e520b3d6021fff5bd2c4e7237d7562/README.md#beta

Should we also remove the beta section from the readme?
https://github.com/adobe/aepsdk-edge-ios/blob/73489cbef9e520b3d6021fff5bd2c4e7237d7562/README.md#beta

I thought we can keep it until the release date

I thought we can keep it until the release date


Installation

I am interested in packaging datetime-fortran for Arch.
It would be useful if the Makefile had an 'install' rule, and a 'pc' file that would allow library locations to be picked up "automagically". I am more than willing to supply patches if you're ammenable to the idea, and we can reach a solution that is acceptable to both of us.
Please let me know if you're interested.

I don't know much about packaging for distros, what is a 'pc' file?

A 'pc' file solves the problem of telling downstream consumers of your library the compiler flags needed to link to it.
So typing, for example,
pkg-config --cflags datetime-fortran
might return
-I/usr/lib
Gnu's autotools uses pkg-config to know how to set its flags. But even if you don't use autotools, pkg-config can still be used in a Makefile:
FFLAGS = $(shell pkg-config --cflags datetime-fortran)
This will set FFLAGS to -I/usr, or -I/usr/lib, depending on where things are installed. This is very useful, because I can then have in one of my Makefile rules
gfortran $((FFLAGS) foo.f90
This saves consumers of your library the problem of hardcoding paths and flags to it.
Can I ask how you currently link to your library?

Hi blippy, what you propose sounds great to me. I am not familiar with Arch either. Would you mind forking the repo, applying your changes in a new branch and making a pull request?

Sure. That'll be fine.
Can I ask what operating systems and compilers everyone is using?
Also, can I ask how you currently link the datetime-fortran library in with your projects?

I'm using CentOS and Fedora. datetime's tests pass for both 32-bit and 64-bit systems with gfortran.  Also tested with Cray, Intel, and PG compilers but these are probably not the ones you are looking for. Never tested on Windows as far as I know.
For linking I just use -L/path/to/datetime-fortran -ldatetime to link to a static library created by datetime's make.

I've been chewing things over, trying to work out the best way to proceed.
Hard-coding the links as you have done is the easiest from your point of view, but makes it more difficult for people to create a packaged library.
Do you have admin privileges, and would you be prepared to go down the Gnu Autotools route? I'm pretty much a newbie when it comes to Autotools myself, but I'm willing to do the conversion. It will allow people to go down the standard route of
configure && make && [sudo] make install
Let me know what you think, and whether you're happy with that idea. Perhaps I could try an experimental branch and see how it goes.

Do you have admin privileges, and would you be prepared to go down the Gnu Autotools route? I'm pretty much a newbie when it comes to Autotools myself, but I'm willing to do the conversion. It will allow people to go down the standard route of
configure && make && [sudo] make install

Yes, this is my preference as well! The only reason I didn't do it is because I am not familiar with autotools - I know how to use them, but not how to set them up for a new project, and my time was consumed otherwise. Thank you so much for you help with this!

No problemo. I'll look into it.
I had made my own project using autotools using Fortran before. It's difficult to know if it was the "poper" way of doing it, though.

There's also CMake... which can be equally daunting, but I find to be a more enjoyable alternative to autotools.
Ah yes, I know pkg-config, wasn't familiar with the shorthand, pc

zbeekman, I tried both, each one time only.  What I found is that Autotools seemed to be "massive brain damage", where things seemed to work by luck rather than judgement. CMake did seem to do things without me having to cajole the system.
So CMake does seem like a viable option, and seems quite a popular build tool.

:thumbsup: for CMake if you can make it happen! :smile:

CMake it is, then :)

If you get stuck, @blippy let me know and I'll take a look. No promises since CMake is an awkward, dark art that is oh-so-very poorly documented, but I have done enough head pounding to be somewhat proficient...

@blippy One more question comes to mind: I have been in the process of re-structuring the source code into multiple files in my local development branch, following the "one class per module" style. Will this impact your CMake implementation given that the source files will soon be tucked away in a common src/lib and src/tests directory structure?

FoBiS can do this with FoBiS build, simply, :smiley:

@milancurcic I think I should still be able to make it work.

The peculiar thing is, I've tried experimenting with both Autotools and CMake. I've managed to get a good build and install and uninstall using Autotools, butnot with  CMake.
Would you be prepared to go the Autotools approach?
I was surprised at how easy ("?") it was to set things up using Autotools, and it does have a fairly intuitive source Makefile.am.

@blippy Please pick the easiest route for you to implement. Autotools and
CMake are not mutually exclusive, so we will be able to have multiple build
systems supported if we decide to.
On Sunday, January 24, 2016, blippy<EMAIL_ADDRESS>wrote:

The peculiar thing is, I've tried experimenting with both Autotools and
CMake. I've managed to get a good build and install and uninstall using
Autotools, butnot with CMake.
Would you be prepared to go the Autotools approach?
I was surprised at how easy ("?") it was to set things up using Autotools,
and it does have a fairly intuitive source Makefile.am.
—
Reply to this email directly or view it on GitHub
https://github.com/milancurcic/datetime-fortran/issues/20#issuecomment-174334859
.

I have made excellent progress on the conversion to autotools, BTW, Everything seems to build right and install/uninstall as it should.

@blippy Amazing! Would you mind opening a pull request from your forked repo? Also please add yourself to the CONTRIBUTORS list. Thank you!

After these changes take effect, I'll create a Homebrew Formula for this lib too. (Probably can't do this before the autotools install is merged and you mint a new release, however.)

@zbeekman :+1: :clap: :tada:

Yes. I just noticed that you made a recent commit, so some reworking will be required on my part.
Before adding a pull request, I think it is a good idea that I make the autotools work with the new master.
It will be fun trying to get everything to sync up.

OK. I've synced your recent commits with autotools. I'll make a pull request imminently.
Please be sure to save your work in case anything goes wrong!

I'll also write a "beginners guide" on how the autotools should work and how users of the project can incorporate it. Stay tuned.

Ah. Sorry I messed up in my browser, so I may be repeating some messages.

I've put together some tips on autotools, including details of how consumers can make use of the module:
http://www.markcarter.me.uk/programming/fortran/calendrical.htm

I'll also mention that when configured, you can create a distribution (which includes configure) by issuing the command:
make dist
That will create a tarball for you, containing everything anyone needs to build and install the package. Note that you will need to set configure.ac's version number in the line:
AC_INIT([datetime-fortran], [1.3.0T])
I've just called it 1.3.0T for now, for testing purposes.

How do you bootstrap the project to generate the ./configure.sh script? I just took a look at #22 and saw your comment there. Maybe update your blog post to include the tip about autoreconf -i?

@zbeekman
Webpage contains info on 'autoreconf -i'.
The curious thing is that you can often tinker with Makefile.am files, and 'make' will still do the right thing. In the past, I had rerun 'autoreconf -i' whenever I made any changes to Makefile.am. That appears to be unnecessary. I presume that the generated Makefile is somehow linked to Makefile.am in some way.
You'd never need to regenerate configure if all you did was modify the source files. 'make' should pick up those changes as a matter of course.

In retrospect, I should have cloned @milancurcic dev branch rather than master branch.

So it seems we are just shy of the "popularity quotient" for being accepted into Homebrew:
$ brew audit --online --strict datetime-fortran
==> brew style datetime-fortran

1 file inspected, no offenses detected

==> audit problems
datetime-fortran:
 * GitHub repository not notable enough (<10 forks, <10 watchers and <20 stars)

Error: 1 problem in 1 formula

Please encourage anyone you know to watch, fork and star the repo to get us over the threshold.


Microservices

Is this where I should put stuff?

To Do: Move libraries over to this git repo... might be a bit of a chicken/egg problem

Breaking into multiple PRs :)


Open new tab when testing image[s]

Open a new browser tab when you click on Classify One, Classify Many, Test One or Test Many.

Waiting for #249 (more important) to be merged, and then I'll rebase this on top of that.

Rebased. @gheinrich, you can merge this now if you like to make way for #188, unless you have any suggestions/critiques.

Thanks for the feedback - commit updated.


impl GetSockOpt for nix::sys::socket::sockopt::SockType causes UB with unknown socket type

Description
I noticed that the implementation of GetSockOpt for nix::sys::socket::sockopt::SockType simply assumes that the socket type returned by the kernel is one of those defined in enum nix::sys::socket::SockType without checking. If that assumption is violated, you get undefined behavior.
Linux has at least one such socket type already (SOCK_PACKET), and operating systems are free to add new ones at any time.
Other socket options probably suffer from a similar problem, but I haven't tested that.
Alternative
socket2::Type deals with this problem by being a newtype wrapper around a c_int instead of an enum.
Proof of concept
This works on Linux only.
use nix::sys::socket::{getsockopt, sockopt};
use std::process::ExitCode;

fn main() -> ExitCode {
	let sockfd = unsafe { libc::socket(libc::AF_PACKET, libc::SOCK_PACKET, 0) };

	if sockfd == -1 {
		eprintln!("Error opening socket: {}", nix::Error::last());
		return ExitCode::FAILURE;
	}

	let socktype = match getsockopt(sockfd, sockopt::SockType) {
		Ok(ok) => ok,
		Err(error) => {
			eprintln!("Error getting socket type: {error}");
			return ExitCode::FAILURE
		}
	};

	eprintln!("The socket's type is: {socktype:?}");
	ExitCode::SUCCESS
}

Output:
$ target/debug/nix-ub
The socket's type is: Segmentation fault

Note that creating a SOCK_PACKET socket is a privileged operation, so the executable needs to be granted that privilege first:
$ cargo build
$ sudo setcap CAP_NET_RAW+eip target/debug/nix-ub

Good catch.


Correct relationship choices

What is the context of this PR?
The relationship choices were using an outdated list of relationships.
This corrects this.
How to review
Make sure the new relationship is as:
Slide
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

Potentially get this merged then pull into https://github.com/ONSdigital/eq-survey-runner/pull/1853?


layout breaking on mobile

this layout break was noticed on mobile devices after the merge of https://github.com/LukeberryPi/phived/pull/41
i suspect it happens because of the following:

there is no storedWidth registered
the inline styles evaluate to width: 2px
the min-width takes action, setting it to at least 20% of the viewport
resize is inactive on devices < 768px, so it's unfixable

this happens only on actual mobile devices accessing the website. chrome inspect shows no sign of this bug.
i have rolled back to a previous deploy on production.
you can grab this if you want to @YuriSamp, otherwise i'll fix it some other day.
please note that production is currently running https://github.com/LukeberryPi/phived/commit/7ac7b7081e08d37abfd708d2240766da7b2cc4f9.
to debug this you will have to access https://github.com/LukeberryPi/phived/commit/439ac3eab49522e840dabff22f65b4ae6cc61093 locally.

I don't get it. When I click at the form border, i'm suposed to be able to resize it?

the issue with resize + localStorage persists, the width seems to updated at uncertain times, generating some unexpected behavior. production currently has the reorder feature and i will hone that before we implement resize again. i will close this issue now and reopen a new one to address this soon.


Generate a detailed changelog

Is your feature request related to a problem? Please describe.
Right now we dont have well defined changelog
Describe the solution you'd like
A changelog where we have issue description, commit title, details about the commit , the commiter etc

:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Properly handle compiler versions

Atm compiler versions are only handled as strings. We need to properly convert them to integer-tuples to allow comparison, and also support compiler-specific compiler flags to be added.
This is the current way of how LFRic makefiles do compiler version comparison. I have converted this into Python:
compiler_version_comparison = ''.join(f"{int(version_component):02d}" for version_component in compiler.get_version().split('.'))

if compiler_version_comparison >= '190000':
    runtime_flags = ...
else: ...

So current get_version() returns a string 1.20.0. It is converted to string 012000 and then compared with string 190000

I've implement this initial change of just making get_version return a tuple instead of a string (and updated other things that depend on it)
https://github.com/hiker/fab_new/compare/bom_master...hiker:fab_new:version_tuples
It now returns an empty tuple if the compiler exists but doesn't have a valid version string. This is to support the hash function. It would be good if we could say that a compiler with no version is not valid and so it doesn't need to be hashed, but I don't know if that's safe.

Second possible component of this:

ATM, there is one method that handles both intel and gfortran. I think these should be moved into the corresponding derived classes (gcc/gfortran/icc/ifort further down in that file), and check that it is indeed the right compiler (e.g. atm we could say have an alias for icc that invokes gcc, and it would not be detected). So test for the right gnu/intel strings in the output. The background here is that I am adding compiler wrapper (like mpif90), so if a user requests intel-mpif90, the wrapper needs to make sure that mpif90 indeed calls the intel compiler. And atm the available check is based on the version number (and we want to minimise the number of times we call the compiler to identify it and make sure it works - so ideally we can deduce this all from one version call). I would hope (??) that the strings for the C and Fortran compiler of the same vendor are close enough to be handled by the same function?? So maybe a mixin??  Note that in general we try to avoid having global functions (which would of course be the other solution)

Looks good. Once you have done the second part, please do a PR - my compiler wrapper needs this (we need to make sure that e.g. mpif90 does indeed invoke the right compiler). A compiler without version is indeed not valid - well, more precisely it will be marked as not available (for a compiler having a version string makes it available), and a tool that is not available, cannot be added to the ToolBox, which means it cannot be used (and we therefore won't need a checksum).

Fixed in PR #9.


[BUG] OutOfDirectoryMemoryError

Describe the bug
Broker end up with OutOfDirectoryMemoryError with KOP.
To Reproduce

start pulsar with KOP
use kafka-producer-perf-test.sh to produce message

Expected behavior
Pulsar broker should not be end up with unexpected OutOfDirectoryMemoryError .
Screenshots

Additional context
I have do some searching for this, it seems the ByteBuf here   and here  coverted from kafka records is not released after published.
I think we should release the ByteBuf when future complete.

Thanks @aloyszhang Are you interested to provide a fix for this issue?

@jiazhai I'll fix it later


Events table is not locked while writing on an aggregate

As a admin I want to be able to manipulate multiple aggregates concurrently without locking each other, so we are able to handle more data / improve performance.
Acceptance criteria

[ ] Sequence is aggregate based and not instance based
[ ] I am able to manipulate two aggregates in the same instance at the same time
[ ] When writing to an aggregate all other aggregates are not locked
[ ] "Benchmark results with Prewarmed connection pool" is improved

Risks

[ ] We know which implementation of the poc works best before implementing

Link to phase: https://docs.google.com/document/d/1mBq610lxduM0kD1H3PrG7ESBVSYtv_bAq0uYT5alIJw/edit#heading=h.6sp2pay2tybc

1 Day for looking at the risk, result should be to know which implementation works best

Document: https://docs.google.com/document/d/1mBq610lxduM0kD1H3PrG7ESBVSYtv_bAq0uYT5alIJw/edit?usp=sharing
The decision is to implement an evetstore based on sequences per aggregate id.

@hifabienne this is my proposal for the epic:
eventstore epic
As a developer i want to get the best performance out of the storage layer of ZITADEL.
Background information
The storage layer of ZITADEL is split into 3 parts.

Query side: all the read traffic hits this part of the storage layer. It doesn't want to make any changes and depending on the use case the data must be more or less actual
Command side: all the write traffic this this par of the storage layer. It wants to make manipulations, for that it might read data to update field of an object
Eventstore: All the traffic hits this layer. the command side might hit it twice first for reading last for writing and the query side for updating stale data

The focus of this epic is to optimise response latency for each storage layer. This can be achieved by optimising all the layers.
eventstore
The eventstore framework has currently several missasuptions from the past which have to be corrected. Further readings here
The following tasks are based on the document mentione the line before.
Phase 1 prepare current query side

[ ] queries only consider data older than the timestamp they hit the api (existing user story)
[ ] events are returned sorted by creation date AND sequence
[ ] spoolers query events by creation date instead of sequence
after that point the linking columns (previous_aggregate_sequence, previous_aggregate_type_sequence) are not needed anymore

Phase 2 correct eventstore model

[ ] remove the unnecessary columns from the events table and the eventstore implementation
[ ] add new event field event_version which describes the field definition of an event
[ ] change the query and command side to version the event version instead of an object/aggregate
[ ] remove the aggregate_version field from the eventstore

Phase 3 heart bleeding

[ ] implement eventstore implementation according to https://github.com/zitadel/zitadel/tree/eventstore-bench/internal/eventstore/v5

includes remove of instance sequence
create new indexes
drop old indexes

[ ] drop sql sequences

Phase 4 optimise by id queries
This phase needs further investigation because we need to know if we need an additional caching layer
Phase 5 optimise search queries
This phase needs further investigation because we need to know if we need an additional caching layer, and if we should react on created events
Phase 6 rethink current aggregates
There might be aggregates we have to redesign. project/application for example

Will close this epic for now, as the open tasks are only clean up tasks and can be done at any point


Update to IdentityModel latest 5.2.x

We want to stay up to date with latest changes in https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet

It looks like we're still compiling against 5.2.0. @brentschmaltz I noticed this version is unlisted on nuget.org. Is there a reason? Should we update to the latest 5.2.x release?

@natemcmaster 5.2.4 is our current release

Ok. We'll do this in 2.2 preview2

ok

Re-opening so we can track this work.

@HaoK - is this sorta the same as https://github.com/aspnet/Security/issues/1843?

Yeah I'll dupe 1843 against this

@HaoK we set the version to 5.3.0 (we have a breaking change in JsonWebToken). Nothing you use yet.
POR is to publish today (9/19)

Fixed via https://github.com/aspnet/Universe/pull/1482
Updated to 5.3 and the AD package to 3.19.8


Does puslar-admin support lookup partitioned topic?

Command
$ pulsar-admin topics lookup topic

can only search brokerUrl for non-partitioned topic.
For partition topic we have to use a loop to search each partition which is not convenient
$ for i in $(seq 0 8); do bin/pulsar-admin topics lookup public/default/test-partition-$i; done

Is there any way to search all brokerUrls for patitioned topic by pulsar-admin tool?
If not,  I think we should add support for it.

@sijie Any suggestions about this?

That is a great feature to add! +1

I'll work on it.


feat(addon-doc): add copy button out-of-the-box

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Tests related changes
[ ] Documentation content changes

What is the new behavior?

@vladimirpotekhin fixed


update R cygnet file to point to new download URL. Intel support added

Added MAALI_URL to point to another R repository.  Current CSIRO address doesn't have the latest versions of R.

need to remove ivybridge reference


[FLINK-33666][table] Use the same constraint name in MergeTableLikeUtil and Schema

What is the purpose of the change
The purpose of this change is to make the constraint generation mechanism the same in MergeTableLikeUtil and Schema
Brief change log

Change the constraint generation in MergeTableLikeUtil to be the same as in Schema
Fix the related tests

Verifying this change
This change is already covered by existing tests, such as MergeTableLikeUtilTest
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency):  no
The public API, i.e., is any changed class annotated with @Public(Evolving):  no
The serializers: no
The runtime per-record code paths (performance sensitive):  no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

Hi @twalthr could you please review this PR?


How to compile for 32 bits?

Probably silly question, how can I compile for 32 bits? Currently my GTD/IDT/ISRs are for 32 bits so a 64 bit build doesn't work properly.
When I run QEMU (yes it's a qemu-system-i386 the screen says:

Code:

Full code can be found here
limine.cfg found here
linker.ld found here

Anything else can be found in the many Makefiles.

Hi. The Limine boot protocol does not support 32-bit kernels.


Update sbt-wartremover, wartremover to 3.2.2

About this PR
📦 Updates

org.wartremover:sbt-wartremover
org.wartremover:wartremover

from 3.1.8 to 3.2.2
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.wartremover" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.wartremover" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #2046.


Update mechatronics.yml

To add Gianluca Milani and Enrico Valli to mechatronics repository

Ok thanks @pattacini for the hint.

cc @marcellosavoldi for reference.

@pattacini I made changes using the browser, and I had only 2 choices:

Did your hint refer to another way?

Did your hint refer to another way?

Yes! You ought to fork the repo first.
Here's some doc on forks and pull-requests.


Multi select Button label without number

Hey, I am trying to set the vue-multi-select button label to just display the name without the calculated select item amount, it can't seem to do that.
<vue-multi-select                           v-model="venueValues"                           :options="options"                           :filters="venueFilters"                           :btn-label="venueBtnLabel"                           :select-options="venueData" />
and venueBtnLabel: "venues"
With this code I still see the calculated item value in the label.

Hi btnLabel is a function (with value as params),
https://codepen.io/IneoO/pen/BevoVw?editors=11
Did you try like this ?

@iNeoO with this, I get the following error
vue.js:634 [Vue warn]: Invalid prop: type check failed for prop "btnLabel". Expected String with value "function testLabel(values) {
        return "A simple vue multi select";
      }", got Function

found in

---> <MultiSelect>
       <Root>

Please update to 4.5.0

Got ya', thanks.
Is there a way to include version 4.5.0. from CDN within a <script> tag?

Yeah simply use plugin via CDN:

Unpkg is provided by nodejs

I did try doing it this way, but it seems that it might be the wrong file, as I get the following error:
vue-multi-select.common.js:1 Uncaught ReferenceError: module is not defined
    at vue-multi-select.common.js:1

Sry, it's this one<EMAIL_ADDRESS>

That works, thank you very much!


sqlsmith: Generate multiple input formats: Protobuf, AVRO, JSON

Motivation

Tests source parsing and reading.
We have encountered various bugs from source parser recently, this will help us catch bugs early.

Requirements

Able to generate complex nested schema.
Able to configure nesting depth.
Able to generate mix of data types, including array.
Main use is to test for correctness, but perhaps it can be used for performance testing in the future?

Background
Originally posted here: https://github.com/risingwavelabs/risingwave/issues/5164 by @neverchanje :

Source reading/parsing
The parsing part will be more deterministic than the rest. We need to generate random data in a specific format (with a probability of generating false data, the expected behavior is to drop it) and verify the correctness of the parsed output.

[ ] MockSource x Protobuf
[ ] MockSource x JSON https://github.com/risingwavelabs/risingwave/pull/5512
[ ] MockSource x Debezium JSON
[ ] MockSource x Avro

Offline discussion with @neverchanje :

The goal is to stabilize of protobuf and avro, which typically have complex nested schema. For testing, we need to ensure that a protobuf file with multiple nested levels and a mix of various data types (including array) can be correctly parsed.

cc @jon-chuang @neverchanje @tabVersion

I propose to make datagen connector support generating multiple formats including native chunk, while nexmark only supports native.

I propose to make datagen connector support generating multiple formats including native chunk, while nexmark only supports native.

+1 for this.

FYI we can do this in next-release. Don't want to block https://github.com/risingwavelabs/risingwave/pull/7612.

cc. @tabVersion

FYI we can do this in next-release. Don't want to block https://github.com/risingwavelabs/risingwave/pull/7612.

time to start?


feat: add jsx-a11y/html-has-lang lint rule

This pull request implements the jsx-a11y/html-has-lang lint rule, enforcing that <html> JSX elements have a lang attribute.
References #341

Thank you! This looks great.


Move os.getpid() inside _MmapedValue (#130)

Related to issue #130
uwsgi imports all python script in master process and after that forks children, so we need move os.getpid() call inside function

We don't currently support that mode of operation, each child needs to be fork+execd. So this won't work.

It should work in both ways

Do you mean that whole module will not work? Do you have some vars/classes that need to init in child and not in master process?

Yes, it depends on the child initting separately.

Closing in favour of #169


Dependancy Issue with ASDF

There's a dependency issue with ASDF. I overwrote the files and both Homeshick and ASDF seem to work fine. However, maybe something to look into? Maybe should also be reported to ASDF?
brew install homeshick
==> Installing homeshick
==> Downloading https://github.com/andsens/homeshick/archive/v1.1.0.tar.gz
Error: The `brew link` step did not complete successfully
The formula built, but is not symlinked into /usr/local
Could not symlink lib/commands/help.sh
Target /usr/local/lib/commands/help.sh
is a symlink belonging to asdf. You can unlink it:
  brew unlink asdf

To force the link and overwrite all conflicting files:
  brew link --overwrite homeshick

To list all files that would be deleted:
  brew link --overwrite --dry-run homeshick

Possible conflicting files are:
/usr/local/lib/commands/help.sh -> /usr/local/Cellar/asdf/0.6.2/lib/commands/help.sh
/usr/local/lib/commands/list.sh -> /usr/local/Cellar/asdf/0.6.2/lib/commands/list.sh
==> Caveats
To enable the `homeshick cd <CASTLE>` command, you need to
  `export HOMESHICK_DIR=/usr/local/opt/homeshick`
and
  `source "/usr/local/opt/homeshick/homeshick.sh"`
in your $HOME/.bashrc

Bash completion has been installed to:
  /usr/local/etc/bash_completion.d

zsh completions have been installed to:
  /usr/local/share/zsh/site-functions

fish functions have been installed to:
  /usr/local/share/fish/vendor_functions.d
==> Summary
🍺  /usr/local/Cellar/homeshick/1.1.0: 24 files, 54.4KB, built in 2 seconds

Also reported to Homebrew https://github.com/Homebrew/homebrew-core/issues/35588


cpeng: fix API functions to use correct registers

Fix the following API functions to reference the shadow
registers/fields:

hps_kernel_verify()
hps_ssbl_verify()

Signed-off-by: Rodrigo Rojo<EMAIL_ADDRESS>

Coverage increased (+0.02%) to 63.612% when pulling 7f4c8e31b693e6fa421f0c2a5204153031296977 on rrojo/cpeng-fix-shdw into 340fab3075eb176c53d09690805c2c5c64233a02 on master.


fix(Call): Fix flash talk indicator

What this PR does 📖
This pull request introduces several enhancements and bug fixes to the src/lib/media/Voice.ts file, including the addition of voice activity detection, improvements to relay server testing, and updates to audio handling. Additionally, there are updates to the package.json and vite.config.js files to support these changes.
Voice Activity Detection:

Added the voice-activity-detection library to detect when a user is speaking and update the media state accordingly. [1] [2]

Relay Server Testing:

Introduced a method to test the connectivity of relay servers and update the list of available relays dynamically. [1] [2]

Audio Handling:

Simplified audio constraints by removing specific audio settings such as echo cancellation and noise suppression.
Added handling for receiving tracks from peers and logging the events.

Configuration Updates:

Updated package.json to include the voice-activity-detection library.
Modified vite.config.js to include voice-activity-detection in optimized dependencies.

Which issue(s) this PR fixes 🔨

Resolve #821

Special notes for reviewers 🗒
Additional comments 🎤

Hey Lucas! So during testing Sara, Luis and I have found that friending is not working on this pr. Due to this its not possible to test the talking indicator
We tried old accounts and new accounts, and made sure to do npm i
User A sends UserB a friend request User B accepts request User A appears on User B side but User B does not appear on User A side
We tried moving to different page, refreshing browser and nothing gets User B to appear on User A side
I also tried 2 new accounts before testing this and 2 new accounts before verifying on dev that friending still worked so clean builds before attempting both
Your branch:
Screen_Recording_2024-11-08_at_5.50.39_PM.mov

Dev branch:

Hello @lgmarchi just wanted to add that the automated tests are failing against this branch for the same reason mentioned above by Phil. I have not seen this error presented in the latest runs of automation tests against dev or any other prs

I see that friend requests are working again within latest commit

that is correct

chrome, macOS
private browser yes

we approved for now, maybe we can improve in the future


encoding double 0.0 generates an EncodedNumber with exponent -1057

In javallier version 0.5.0, the encoding of the double value 0.0 is an EncodedNumber with a significant of 0 and an exponent of -1057. And although this is a valid encodoing of zero, it will lead quite quickly to overflows in the Paillier arithmetic. I suggest setting the exponent to 0.

addressed in commit 0968333f53e966d94e48b987672d419bd9a8c047


Evolution of Area definition

Derived from discussion in #24
So far (as of v0.1.0), we have 3 properties to define the area, which is always a circle centered in (latitude, longitude) with radius accuracy:
    latitude:
      $ref: '#/components/schemas/Latitude'
    longitude:
      $ref: '#/components/schemas/Longitude'
    accuracy:
      $ref: '#/components/schemas/Accuracy

In order to support more areas, we can consider Area as a polymorphic object, for example:
Area:
  description: The geometrical area considered for device location
  oneOf:
    - $ref: '#/components/schemas/Circle'
    - $ref: '#/components/schemas/Polygon'
    - $ref: '#/components/schemas/PostCode'
  discriminator:
    propertyName: type

Apart from the current Circle, there are proposals to support Polygon (Orange) and PostCode (Telefónica)

Very strange @maxl2287 - I cannot assign you to this issue !

I've discussed with people familiar with this topic and they pointed me to : https://geojson.org/
Seems good materiel to start with something and not far to what we have.

I can take care of this task @bigludo7. Good to have some standard to look into.
I will make a first PR just adding support for a new object Area, which by now it can only be a Circle. This can be then reference in the Subscriptions PR, and we can work later on expanding other sub-types of Area in separate tracks.

Closing issue as new Polymorphic model for Area is already merged