[New game]: Guitar Playing Game

🎮 Game Request
Game logic and basic description

Showing a guitar which produces sounds on click the strings of the guitar.
Slide the guitar more and more, sound will be more.
Create a tune will boost you skill and knowledge of guitar.

Point down the features
Game points

More tune will generate, more will your score
Enjoy and play the game with fun.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Avdhesh-Varshney !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @Avdhesh-Varshney ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


x/tools/gopls: poor performance and crash on google-cloud-go

gopls version: v0.12.0-pre.1 (go1.20.3)
gopls flags:
update flags: proxy
extension version: 0.38.0
go version: 1.20.3
environment: Visual Studio Code darwin
initialization error: undefined
issue timestamp: Tue, 09 May 2023 14:45:46 GMT
restart history:
Tue, 09 May 2023 14:43:43 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
gopls crashed while in google-cloud-go. I believe I was searching to open a file before this happened.
Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.
https://gist.github.com/codyoss/f19310e0db7499861e7f3d92ad056625
Failed to auto-collect gopls trace: unrecognized crash pattern.
Also got the following message post crash: extension-output-golang.go-#3-gopls (server): tokenization, wrapping and folding have been turned off for this large file in order to reduce memory usage and avoid freezing or crashing. and Connection to server got closed. Server will not be restarted.

The CLs above set up some benchmarks for this repo, and then fix the low hanging fruit mentioned above to optimize the time it takes to diagnose the workspace from ~1.5s->300ms.
I'll note that the initial workspace load on my machine went from 2<EMAIL_ADDRESS>(!!) to<EMAIL_ADDRESS>and the in-use memory went from 6-7GB to 1GB.  Gopls should perform significantly better overall on v0.12.0-pre.1, and in fact this is what I observe on my linux laptop.  I am curious to test more on Mac+VS Code.
I am very suspicious of system calls: I observed that even on linux, 20%+ of CPU was spent in system calls related to the file cache. I expect this could be much worse on darwin. As an experiment, I put a 100MB in-memory LRU cache in front of our file-based cache, in https://go.dev/cl/494100, which significantly reduces the system call overhead.  I'll test this on darwin tomorrow.

I am very suspicious of system calls: [...] even on linux, 20%+ of CPU was spent in system calls related to the file cache

That does seem like an awful lot, for Linux. We shouldn't be making that many filecache system calls in total, and there should be very little contention in flock (and whatever contention there is should be minimally CPU-bound: all it does is walk a very short linked list before going to sleep). It would be interesting to run gopls under perf in system mode with kernel symbols and see what shows up. (We could also compare against a rename(2)-based implementation of the cache, since it's atomic on Linux, but it really shouldn't be necessary to maintain a second implementation.)
For macOS, I could totally believe it because of #13841, a kernel bug which causes a frustrating profile skew towards system calls that do minimal CPU work (like open(2)).

@codyoss I have a few more thoughts about this, after reflecting on your description a bit more:

You should not have to open submodule roots: opening the repo root should work fine, thanks to your go.work file. Is this not what you see?
gopls performance should never cause vs code to freeze in the way you describe, as gopls runs as a separate process. However, I have an idea: sometimes when I am using gopls in VS Code I open the output window to the gopls logs, and I've noticed that after a short amount of time the VS Code UI becomes incredibly laggy, due to poor scaling of the output buffer, and the chattiness of the LSP. Is it possible that you opened this window when testing v0.12.0-pre.1, and left it open?

With the optimizations above, it would be great if you could try again using gopls@master, being sure not to leave the gopls logs open in the output window. It really should be faster than v0.11.0, and if it's not I'd love to jump on a VC to pair debug.
To install gopls@master, just check out go.googlesource.com/tools, cd tools/gopls && go install.

I may have been conflating things. As mentioned above we recently switched to go.work and that is why I no longer needed to open at sub-module roots. Sorry if that was not clear in the comment above. I can open at the repo root just fine now.
I don't think I did. But maybe it was another process on my computer that was causing the lockups. I have seen gopls in the past take 400% CPU usage in macs activity monitor.

Building from HEAD I saw little to no issue. I did have a minute or two where my editor, vscode, would not jump to refs or show things again. But after a period of time it started working again. gopls CPU usage does seem down quite a bit as well. In the past I was consistently noticed it as the top process, but no longer.
I will keep this version installed as it seems to be working well for my use cases. Thanks

Thanks for testing again! I'm going to close this issue as done for now, but please comment if you encounter problems again, and I'll reopen.

don't think I did. But maybe it was another process on my computer that was causing the lockups. I have seen gopls in the past take 400% CPU usage in macs activity monitor.

gopls will use a lot of CPU when building its indexes, particularly at startup but also after changes. However, such periods should be brief, and overall CPU usage should be down. It may be the case that gopls so successfully saturates CPUs that your computer freezes. In that case, please let us know. We may need to tweak gopls to use less parallelism.

@findleyr I did have another crash from my build of HEAD. The issue is the stacktrace is too long for vscode to capture in output to see that beginning important bit -- my terminal captured about 315k loc and that was not enough. Any suggestions  about how to get more info? Does gopls write a log anywhere or anything that would be useful to share?

Actually on subsequent startup I got another that was small enough: https://gist.github.com/codyoss/d21403933fe6c1f5802d3bf831424bd3

Thanks Cody. Huh, this looks like a runtime issue.
Could someone from @golang/runtime take a look at Cody's crash?
Cody: could you confirm that you're still on Go 1.20.3?

Perhaps I spoke too soon: as @adonovan points out there are ~4000 threads in our file cache blocked on opening a locked file, which is exhausting the file limit.
So this does look like a gopls bug. We have ideas for how to fix this.

Cody, if you have the patience please do try again with the latest source as the recently merged change should not only fix the crash but reduce the number of goroutines and the amount of I/O concurrency, which may have other performance effects. Thanks again for these very helpful bug reports.

Will do!

No crashes but I did have another really long pause on an operation. I was searching go.mod files in the repo and it took 3-5 minutes to get back the query -- during which time it seems gopls was very hungry and unresponsive:

@adonovan  another crash: https://gist.github.com/codyoss/866fe1c54ca191e40d6b6438bff8bb58

I still do believe there are perf issue with HEAD gopls + google-cloud-go's large codebase + using go.work -- at least on my machine. I reverted today to v0.11.0 and gopls does idle at much higher mem usuage(~12GB) but after a period of time everything seems to stabilize perf wise in my editor. On the latest gopls I still have consistent freeze ups where basic operations like searching the whole repo take a considerable amount of time to perform while it feels like gopls indexing of symbols or something and is causing other operations not to complete.
I think for now the solution for us is going to have to be removing our workspace files as they seems to tax gopls too much. I would like to eventually restore our these files because I do see an benefit of having them for other operations like syncing deps between all of our various modules, but I don't think it is currently worth the productivity hit in vscode.
I would be curious if other large workspace repos have experienced the same issues, but I don't personally know of other projects as large as google-cloud-go that are trying to use this feature.

Discussing with @codyoss, we believe this is related to our go mod tidy logic.
Historically, gopls has conservatively re-run go mod tidy when files are saved (because saved files may theoretically change the tidy result, before overlay support).
This runs for each go.mod file in the workspace, and eagerly parses Go files in the module to analyze the tidy result.
Mix in the VS Code setting that auto-saves files after a delay<EMAIL_ADDRESS>more aggressive eviction of parsed files, and the new google-cloud-go go.work file with 145 modules, and you have a recipe for disaster.
Fortunately, this is yet again easy to fix...


iOT project (raspberry pi 2 / 3) Scaffolding

Discussion 5 Sept

Sign up => sign up with username, with username as device's identifier / uuid, password as hard code / mac address / uuid / etc
Assume node.js application
Review if we should integrate with those platform's famous JS framework, it is because they should need to fetch some values from the hardware and pass it to skygear
Scaffolding should be able to generate ardunio / RasPi3 project

Updates:

Support raspberry pi 2 / 3
OS suggests https://archlinuxarm.org/platforms/armv7/broadcom/raspberry-pi-2 / https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3
Node.js example project with skygear loaded
Readme with instruction for deployment steps, files to change, etc.

https://github.com/skygear-demo/raspberrypi-example

Latest code pushed to the repos, feel free to leave comment and open issue there.


[v2.3.0] Not able to read files properly

version: 2.3.0
kafka-connect version: 6.2.0
kafka version: 6.2.0
zookeeper version: 6.2.0
I started a simple connector which reads text files from certain folder.
{
    "connector.class": "io.streamthoughts.kafka.connect.filepulse.source.FilePulseSourceConnector",
    "tasks.max": "1",
    "topic": "fucsv45",

    "fs.cleanup.policy.class": "io.streamthoughts.kafka.connect.filepulse.fs.clean.LogCleanupPolicy",
    "fs.listing.class": "io.streamthoughts.kafka.connect.filepulse.fs.LocalFSDirectoryListing",
    "fs.listing.directory.path": "/tmp/data/csv/check2",
    "fs.listing.recursive.enabled": "false",
    "fs.listing.interval.ms": "10000",
    "fs.listing.filters": "io.streamthoughts.kafka.connect.filepulse.fs.filter.RegexFileListFilter",
    "file.filter.regex.pattern": ".*txt$",

    "tasks.reader.class": "io.streamthoughts.kafka.connect.filepulse.fs.reader.LocalRowFileInputReader",

    "offset.attributes.string": "name+hash",
    "tasks.file.status.storage.bootstrap.servers": "broker:9092",
    "tasks.file.status.storage.topic.partitions": "1"
}

It reads first file fine, but after that shows this on logs
connect      | [2021-09-29 12:05:13,726] INFO Scheduled files still being processed: 1. Skip filesystem listing while waiting for tasks completion (io.streamthoughts.kafka.connect.filepulse.fs.DefaultFileSystemMonitor)
connect      | [2021-09-29 12:05:13,727] INFO Completed filesystem monitoring iteration in 1 ms (io.streamthoughts.kafka.connect.filepulse.source.FileSystemMonitorThread)
connect      | [2021-09-29 12:05:19,382] INFO WorkerSourceTask{id=fucsv45-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask)
connect      | [2021-09-29 12:05:23,691] INFO Scheduled files still being processed: 1. Skip filesystem listing while waiting for tasks completion (io.streamthoughts.kafka.connect.filepulse.fs.DefaultFileSystemMonitor)
connect      | [2021-09-29 12:05:23,692] INFO Completed filesystem monitoring iteration in 1 ms (io.streamthoughts.kafka.connect.filepulse.source.FileSystemMonitorThread)
connect      | [2021-09-29 12:05:29,349] INFO WorkerSourceTask{id=fucsv45-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask)
connect      | [2021-09-29 12:05:33,695] INFO Scheduled files still being processed: 1. Skip filesystem listing while waiting for tasks completion (io.streamthoughts.kafka.connect.filepulse.fs.DefaultFileSystemMonitor)
connect      | [2021-09-29 12:05:33,695] INFO Completed filesystem monitoring iteration in 0 ms (io.streamthoughts.kafka.connect.filepulse.source.FileSystemMonitorThread)
connect      | [2021-09-29 12:05:39,351] INFO WorkerSourceTask{id=fucsv45-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask)
connect      | [2021-09-29 12:05:43,697] INFO Scheduled files still being processed: 1. Skip filesystem listing while waiting for tasks completion (io.streamthoughts.kafka.connect.filepulse.fs.DefaultFileSystemMonitor)
connect      | [2021-09-29 12:05:43,697] INFO Completed filesystem monitoring iteration in 0 ms (io.streamthoughts.kafka.connect.filepulse.source.FileSystemMonitorThread)
connect      | [2021-09-29 12:05:49,352] INFO WorkerSourceTask{id=fucsv45-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask)
connect      | [2021-09-29 12:05:53,663] INFO Scheduled files still being processed: 1. Skip filesystem listing while waiting for tasks completion (io.streamthoughts.kafka.connect.filepulse.fs.DefaultFileSystemMonitor)
connect      | [2021-09-29 12:05:53,663] INFO Completed filesystem monitoring iteration in 0 ms (io.streamthoughts.kafka.connect.filepulse.source.FileSystemMonitorThread)
connect      | [2021-09-29 12:05:59,318] INFO WorkerSourceTask{id=fucsv45-0} flushing 0 outstanding messages for offset commit (org.apache.kafka.connect.runtime.WorkerSourceTask)

Seems like it has not compelted that first file, although in filepulse-status topic, it seems to have updated all stages on file processing
 connect-file-pulsefucsv45.{"name":"text2.txt","hash":"2906419869"}
 {"metadata":{"uri":"file:/tmp/data/csv/check2/text2.txt","name":"text2.txt","contentLength":172,"lastModified":1632916808000,"contentDigest":{"digest":"2906419869","algorithm":"CRC32"},"userDefinedMetadata":{"system.inode":33399915,"system.hostname":"connect"}},"offset":{"position":-1,"rows":0,"timestamp":1632916889595},"status":"SCHEDULED"}
connect-file-pulsefucsv45.{"name":"text2.txt","hash":"2906419869"}
 {"metadata":{"uri":"file:/tmp/data/csv/check2/text2.txt","name":"text2.txt","contentLength":172,"lastModified":1632916808000,"contentDigest":{"digest":"2906419869","algorithm":"CRC32"},"userDefinedMetadata":{"system.inode":33399915,"system.hostname":"connect"}},"offset":{"position":0,"rows":0,"timestamp":1632916889639},"status":"STARTED"}
connect-file-pulsefucsv45.{"name":"text2.txt","hash":"2906419869"}
 {"metadata":{"uri":"file:/tmp/data/csv/check2/text2.txt","name":"text2.txt","contentLength":172,"lastModified":1632916808000,"contentDigest":{"digest":"2906419869","algorithm":"CRC32"},"userDefinedMetadata":{"system.inode":33399915,"system.hostname":"connect"}},"offset":{"position":172,"rows":3,"timestamp":1632916890283},"status":"COMPLETED"}
connect-file-pulsefucsv45.{"name":"text2.txt","hash":"2906419869"}
 {"metadata":{"uri":"file:/tmp/data/csv/check2/text2.txt","name":"text2.txt","contentLength":172,"lastModified":1632916808000,"contentDigest":{"digest":"2906419869","algorithm":"CRC32"},"userDefinedMetadata":{"system.inode":33399915,"system.hostname":"connect"}},"offset":{"position":172,"rows":3,"timestamp":1632916890283},"status":"CLEANED"}
connect-file-pulsefucsv45.{"name":"text2.txt","hash":"2906419869"}
 {"metadata":{"uri":"file:/tmp/data/csv/check2/text2.txt","name":"text2.txt","contentLength":172,"lastModified":1632916808000,"contentDigest":{"digest":"2906419869","algorithm":"CRC32"},"userDefinedMetadata":{"system.inode":33399915,"system.hostname":"connect"}},"offset":{"position":172,"rows":3,"timestamp":1632916890283},"status":"COMMITTED"}

What I maybe doing wrong ?

2.4.0 worked fine. Thanks.


allow async parse function

I'm not completely sure in possible performance hits because of this, in theory, it could be possible to do something like this:
const parseResult = parseQuery(query, parse);
document = parseResult instanceof Promise ? await parseResult : parseResult;

And it's not going to await if the parse function is not async, but it will have an extra check in the process

Thanks for the PR. This is now available in 1.4.0


Expose "quick pick" menu to Extensions API

Type: Feature Request
I would like to be able to grab the selected item and it's context from the quick pick menu via an extension. This is currently not possible with the Extensions API.
Here's a relevant thread in the VS Code's Extensions QA Forum where I asked about this: https://github.com/microsoft/vscode-discussions/discussions/1736
VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Windows_NT x64 10.0.19045
Modes:

Can you elaborate on why you want to do this? Take me through the scenario.


Objects

This adds support for adding nested properties. These are modeled as top-level messages (called 'Objects' in the schema) since that's how proto / OpenAPI would model them.
I'm expecting a lot of comments on this PR since it's both messy and needs to do a lot of refactoring.

Looks like test issue is just because the outputs aren't fully idempotent.


Finish Typing

this PR builds on #276.
it adds remaining typing, configures mypy and marks the package as typed.

coverage: 97.261% (-1.4%) from 98.68%
when pulling 3dbbc4d94432b6d8530d464b292897ee6a058e13 on betaboon:typing
into 9cfad4cdb4fcec787114f0a9cb36afac274722fd on mindflayer:main.

coverage: 97.261% (-1.4%) from 98.68%
when pulling 3dbbc4d94432b6d8530d464b292897ee6a058e13 on betaboon:typing
into 9cfad4cdb4fcec787114f0a9cb36afac274722fd on mindflayer:main.

coverage: 97.261% (-1.4%) from 98.68%
when pulling 3dbbc4d94432b6d8530d464b292897ee6a058e13 on betaboon:typing
into 9cfad4cdb4fcec787114f0a9cb36afac274722fd on mindflayer:main.

I'm sorry, this went a "little" overboard 🙈

Now I fully understand your comment ^^

yep.
I'd suggest: let's ignore this PR for now, as it just builds on top of the other to finish up the typing.
let's use the other PR to discuss if and what we want to do with it.


Any plans to add this package to the Wally registry?

I'm sure you must know about Wally. It'd be nice if this package was able to be installed and updated using Wally.

Hey - no, sadly ClientCast wasn't exactly designed to be a package in mind initially. ClientCast controls script behavior by injecting modules dynamically for easier UX, but as a result falls a bit outside of just being a package. In order to make ClientCast a package I'd have to rewrite the code to not automatically inject scripts, but rather to allow the developer able to manually require the module on both contexts.


[Community] add @ciyongch as a new committer

Description
Please join me in welcoming Ciyong Chen (@ciyongch) as our new committer. He is our 1.7.0 release manager and he helped work through many issues during the release process and towards the end he shared very useful summary on how we could improve our release process in #19029. Prior to that, Ciyong has contributed to important components related to MKLDNN integration, along with several other operator implementations and bug fixes.
PRs: https://github.com/apache/incubator-mxnet/pulls?q=is%3Apr+author%3Aciyongch+
Issues he participated: https://github.com/apache/incubator-mxnet/issues?q=is%3Aissue+involves%3Aciyongch+
Code reviews: https://github.com/apache/incubator-mxnet/pulls?q=is%3Apr+reviewed-by%3Aciyongch+
Changes

[x] add Ciyong Chen as a new committer

Congratulations @ciyongch
Well deserved!

Congrats @ciyongch!
Great Job!!


"Upgrade Available" option shown for a template that does not satisfy minimum version check.

Rancher Version: v1.1.0-dev5-rc5
K8 catalog from - https://github.com/rancher/qa-catalog/
Steps to reproduce the problem:
Add catalog "library" with url  https://github.com/rancher/qa-catalog/
Create a kubernetes environment.
Kubernetes environment gets created with the correct template ( image rancher/k8s:v1.2.4-rancher6) .

But UI shows "Upgrade Avaialble" option for Kubernetes stack.

@vincent99 I have added the support for the filter for individual template version, to catalog-service

Version - 1.1.0-rc3
Verified fixed


docstrings/sphinx: Support cross-refs for types in "Receives" sections

Is your feature request related to a problem? Please describe.
The goal is to have a common set of features between all parsers.
Describe the solution you'd like
The Sphinx parser should be able to parse the types in "Receives" section in order to enable automatic cross-references.
from griffe.docstrings.utils import parse_annotation

# annotation is a string
annotation = parse_annotation(annotation, docstring)
# annotation is unchanged, or becomes a Name or Expression! cross-refs enabled

Closing for cleanup, but if you'd like to work on this, just ask and I'll reopen!


Memory usage increases gradually on Jetson-nano

Hello everyone, i'm having an issue with memory usage in Jetson-nano.
I'm using ODC without docker with rasberry Pi camera Module v2 and yolov3-tiny.
Once I start ODC, my memory usage increases gradually till saturation.

Any idea how to resolve this.

Hi ! Yes, this is a know issue, please continue the discussion here: https://github.com/opendatacam/opendatacam/issues/95


Addition to Authorization Server Setup page

Added comment on needed Keycloak configuration to resolve client IPs behind Apache Proxy

Additional commits to fork add clarifications to "Node to Authorization Server Interactions" page


Options and arguments not working

I have the following code:
argument('nogulp', InputArgument::OPTIONAL, 'Skip gulp install.');

task('gulp', function () {
    $nogulp = input()->hasArgument('nogulp') && input()->getArgument('nogulp') != null;
    if (!empty($nogulp)) {
        echo 'Skipping gulp ...';
    } else {
        echo 'Running gulp ...';
        cd("/home/ubuntu/mycode");
        if (env('nogulp') == 0) {
            run("gulp");
            run("gulp assemble");
        }
        run("gulp asset");
    }
})->desc('Run gulp tasks when required');

The purpose is to skip gulp tasks when not required. However, it always runs. I did it from the documentation here:
http://deployer.org/docs/tasks
Is there something im missing?

What's your command you're running? Are you trying to make it work on parallel? There's a bug for parrallel with no parameters. Try dep gulp production -p --nogulp=1

Thanks!


feat: Use null value to evaluate behavior in publicNetworkAccess instead of empty string - avm/res/cognitive-services/account

Description

Request addresses the conditional statement logic for network access status based on the values of publicNetworkAccess and networkAcls. The expression ensures that if publicNetworkAccess is not empty, that value is used; otherwise, if networkAcls is not empty, the status is considered enabled; otherwise, it’s disabled. This aligns with the intended behavior of prioritizing publicNetworkAccess over networkAcls for determining network access status.
This change makes it so that an empty string passed to the module, will fail the deployment. If the value is not passed, then a null value will be interpreted as the default 'Disabled' behavior. This can only be overridden by explicitly passing 'Enabled'.
Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utlities (Non-module effecting changes)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[x] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[ ] I have run Set-AVMModule locally to generate the supporting module files.
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings

Hi @jceval,
Thanks for your contribution!
Are you able to add a workflow status badge, more details see here.

@jceval In addition to the pipeline badge mentioned in the previous comment, you will need to run the Set-AVMModule utility in your local branch to generate the necessary ARM template file and README updates. More info here.

@jceval In addition to the pipeline badge mentioned in the previous comment, you will need to run the Set-AVMModule utility in your local branch to generate the necessary ARM template file and README updates. More info here.

@jceval would you have some time to drive this PR to closure?
Please reach out to the team if you need support on this one

Hi @jceval,
Thanks for your contribution! Are you able to add a workflow status badge, more details see here.

@ChrisSidebotham I have added the mentioned badge.
@ilhaan  I also updated the template and readme

Impressive - this didn't work for the longest time due to a Bicep bug and could be fixed across a range of other modules that all needed the empty string as an interims allowed value :)

@jceval The pipeline badge needs to show a run for the jceval:jaceval/cognitive-services-public-network-access branch but I only see main branch runs on there.

@jceval The pipeline badge needs to show a run for the jceval:jaceval/cognitive-services-public-network-access branch but I only see main branch runs on there.

That's true. The pipeline badge would be this one:

Please note @jceval that you can select the branch you want to have the badge for in the window where you create it :)

Doesn't change the fact though that the workflow did 'apparently' not run for the branch 😄 It happens. I do see however @jceval that your workflow is slightly outdated in that it still contains the cron scheduler. A few weeks back we removed the automated scheduling to save you your hard earned Azure credits. I recommend to temporarily disable all actions, pull latest main (also into your branch), enable actions again and the run the (https://github.com/jceval/bicep-registry-modules/actions/workflows/platform.toggle-avm-workflows.yml)[https://github.com/jceval/bicep-registry-modules/actions/workflows/platform.toggle-avm-workflows.yml] workflow once to disable any unintended triggering of workflows through changes to files in main.

Got it working ! 😁

Thank you @jceval!


[BUG] Plot disappearing : zooming , smoothing & minimizing Data Series Section

Bug Description
After Zooming the plot and doing some smoothing, I minimized Data Series section.
The plot disappeared. Tested it a few times and it seems to happen when I use the smoothing feature in Zoom and min/max Data Series.
If I restart VSCode the plot reappears.
DVC VSCODE v==1.0.54
https://github.com/iterative/vscode-dvc/assets/24204714/e8bd7621-6ee6-4c47-b4e6-c63f76d87673
Expected Behaviour
Not disappearing plot

Thanks for the report. I'll take a look next week.


make cmake

Hi Gijs, thanks for working on the code! You are preparing the code to be used in science case 4? Some comments on your changes:

if you switch to cmake (no problem), please remove the current 'Makefile'
Why are you linking to Cuda? I dont think it hurts (slows down) the code, but we're not depending on it

psrdada is linked to cuda:
[ 83%] Building C object CMakeFiles/fake.dir/src/fake.c.o
[100%] Linking C executable fake
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcutil_cuda.o): In function `ipc_alloc_cuda':
(.text+0x80): undefined reference to `cudaSetDevice'
(.text+0xe2): undefined reference to `cudaIpcOpenMemHandle'
(.text+0x12e): undefined reference to `cudaMalloc'
(.text+0x13f): undefined reference to `cudaIpcGetMemHandle'
(.text+0x14a): undefined reference to `cudaGetErrorString'
(.text+0x183): undefined reference to `cudaGetErrorString'
(.text+0x1e3): undefined reference to `cudaGetErrorString'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcutil_cuda.o): In function `ipc_disconnect_cuda':
(.text+0x245): undefined reference to `cudaIpcCloseMemHandle'
(.text+0x25b): undefined reference to `cudaGetErrorString'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcutil_cuda.o): In function `ipc_dealloc_cuda':
(.text+0x297): undefined reference to `cudaSetDevice'
(.text+0x29f): undefined reference to `cudaFree'
(.text+0x2b3): undefined reference to `cudaGetErrorString'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcutil_cuda.o): In function `ipc_zero_buffer_cuda':
(.text+0x2ea): undefined reference to `cudaMemset'
(.text+0x303): undefined reference to `cudaGetErrorString'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcutil_cuda.o): In function `__cudaUnregisterBinaryUtil()':
(.text+0x8): undefined reference to `__cudaUnregisterFatBinary'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcutil_cuda.o): In function `__sti____cudaRegisterAll()':
(.text.startup+0xc): undefined reference to `__cudaRegisterFatBinary'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcio.o): In function `ipcio_write':
(.text+0x71f): undefined reference to `cudaMemcpy'
(.text+0x72c): undefined reference to `cudaDeviceSynchronize'
(.text+0x803): undefined reference to `cudaSetDevice'
(.text+0x812): undefined reference to `cudaGetErrorString'
(.text+0x876): undefined reference to `cudaGetErrorString'
/usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/libpsrdada.a(ipcio.o): In function `ipcio_read':
(.text+0xf6a): undefined reference to `cudaMemcpy'
(.text+0xf77): undefined reference to `cudaDeviceSynchronize'
(.text+0x1033): undefined reference to `cudaGetErrorString'
(.text+0x10a3): undefined reference to `cudaSetDevice'
(.text+0x10b2): undefined reference to `cudaGetErrorString'
collect2: error: ld returned 1 exit status
CMakeFiles/fake.dir/build.make:95: recipe for target 'fake' failed
make[2]: *** [fake] Error 1
CMakeFiles/Makefile2:141: recipe for target 'CMakeFiles/fake.dir/all' failed
make[1]: *** [CMakeFiles/fake.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

Ok, that is a good reason. Not sure who is using psrdada-cuda; maybe we can drop it there, too.

What happened to the compiler flags? Originally i had
CFLAGS += -O3 -g0 -march=native -fstrict-aliasing which is needed for decent performance. Will cmake pick these up from the environment during build?
Please add a note to the README on this.

Ok, nice i didn't know that. Can you add that explanation to the README ?

i'm not sure if that is a useful, since this is  just default cmake behavior. I prefer not to replicate the cmake documentation :)
I think just adding CMAKE_BUILD_TYPE=release to the doc might be helpful.

I still prefer making the compiler flags explicit. On my system (fedora), it defaults to -O2, without the -march=native. Worst case, that disables all SIMD / AVX / SSE instructions and that could mean a significant performance hit for some of the pipeline. Although, this code (ringbuffer) does not do floating point math or large memcpy's so the impact here will be less..

there you go


Why videojs-ima does not work on safari responsive design mode - iphone 8

Tested advanced example on real iphone safari => works perfectly
Tested advanced example on safari responsive design mode - iphone 8 => player just bricks and ad is not played
https://googleads.github.io/videojs-ima/examples/advanced/
vast tag:  https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/124319096/external/single_ad_samples&ciu_szs=300x250&impl=s&gdfp_req=1&env=vp&output=vast&unviewed_position_start=1&cust_params=deployment%3Ddevsite%26sample_ct%3Dskippablelinear&correlator=
Test on safari => responsive design mode => iphone 8
Safari 14

Hello @damjan25 ,
When testing your ad tag in the advanced example, I see the following error:
videojs.ima.js:1521 Ad error: AdError 200: The provided ad type: skippablevideo is not supported.
video.min.js:12 VIDEOJS: adserror (Preroll)

Is this the same error you are seeing?
This guide on skippable ads on mobile has more information. Using the following code, may be a solution for you.
google.ima.settings.setDisableCustomPlaybackForIOS10Plus(true);

Thank you,
Jackson
IMA SDK team

Hey, thank you for checking this.
Yes I am getting exactly the described error.
Will try with that solution, hope it solves the issue :)

@damjan25 did that modify do the trick?
Because I'm seeing the exact error, but setDisableCustomPlaybackForIOS10Plus doesn't change.
Thanks for your time.

unfortunately no :(
Safari response design mode is just acting weird.


exec in Nimscript does not work

I don't know if this is related to this lib or if it's a limitation in the nim VM.
However, there are several procs that don't work as expected inside nimscripts.
import nimscripter

const script = """
proc build*(): bool =
  echo "building nim... "
  exec "sleep 10"
  echo getCurrentDir()
  echo "done"
  true

when isMainModule:
  discard build()
"""

addCallable(buildpackModule):
  proc build(): bool
const addins = implNimscriptModule(buildpackModule)
discard loadScript(NimScriptFile(script), addins, modules = ["system/nimscript"])

When I run the contents of script as a file with nim e the script outputs "building...", waits for 10 seconds, then outputs the current directory.
When I run my main.nim file, I would expect it to do the same. But the script outputs "building...", then immediately prints an empty line before exiting without failures.
It seems like the exec command is being ignored.
It also looks like the getCurrentDir() proc just returns an empty string.
I also tried running echo 'hello' using gorgeEx inside the nimscript. It returned no output and exitcode 0.
Any idea if it's possible to do what I'm trying to do?

Those procedures are exported by the Nim compiler to the interpreter it runs, if you want to expose them as well you will need to implement them using exportTo. It's not ideal, but if one wanted to make it easy to implement they could make a template that does it all so then you could do exportStdlibTo(moduleName).

Looking into how the compiler implements those operations I have decided to just make a template to implement them and avoid the nimscript module. You can see the file that adds them https://github.com/beef331/nimscripter/blob/master/src/nimscripter/vmops.nim here. An example of them in use is here. https://github.com/beef331/nimscripter/blob/master/tests/tvmops.nim

Thanks for the quick fix!
I have a concern with your implementation of exec though. Since you're wrapping the exec in a try/catch it won't behave as expected.
According to https://nim-lang.org/docs/nimscript.html#exec%2Cstring

If the external process terminates with a non-zero exit code, an OSError exception is raised.

However, this:
import nimscripter
import nimscripter/vmops

const script = """
proc build*(): bool =
  echo "building nim... "
  exec "exit 1"
  echo "done"
  true
when isMainModule:
  discard build()
"""
addVmops(buildpackModule)
addCallable(buildpackModule):
  proc build(): bool
const addins = implNimscriptModule(buildpackModule)
discard loadScript(NimScriptFile(script), addins)

will print
building nim...
done

But when I run the content of the script with nim e it will result in
building nim...
stack trace: (most recent call last)
~/Documents/monorepo-manager/pkgs/mono/src/test.nims(7, 16)
~/Documents/monorepo-manager/pkgs/mono/src/test.nims(3, 8) build
~/.choosenim/toolchains/nim-1.6.2/lib/system/nimscript.nim(273, 7) exec
~/.choosenim/toolchains/nim-1.6.2/lib/system/nimscript.nim(273, 7) Error: unhandled exception: FAILED: exit 1 [OSError]

as expected.

Thanks for the quick fix, however, I still have some concerns.
According to https://nim-lang.org/docs/nimscript.html#exec%2Cstring

If the external process terminates with a non-zero exit code, an OSError exception is raised.

However, this:
import nimscripter
import nimscripter/vmops

const script = """
proc build*(): bool =
  echo "building nim... "
  exec "exit 1"
  echo "done"
  true
when isMainModule:
  discard build()
"""
addVmops(buildpackModule)
addCallable(buildpackModule):
  proc build(): bool
const addins = implNimscriptModule(buildpackModule)
discard loadScript(NimScriptFile(script), addins)

Outputs this:
building nim...
done

When I run the contents of the scripts variable with nim e, I get this:
building nim...
stack trace: (most recent call last)
~/Documents/monorepo-manager/pkgs/mono/src/test.nims(7, 16)
~/Documents/monorepo-manager/pkgs/mono/src/test.nims(3, 8) build
~/.choosenim/toolchains/nim-1.6.2/lib/system/nimscript.nim(273, 7) exec
~/.choosenim/toolchains/nim-1.6.2/lib/system/nimscript.nim(273, 7) Error: unhandled exception: FAILED: exit 1 [OSError]

as expected.
Also, gorgeEx does not work.
This:
import nimscripter
import nimscripter/vmops

const script = """
proc build*(): bool =
  echo "building nim... "
  echo gorgeEx "exit 1"
  echo "done"
  true
when isMainModule:
  discard build()
"""
addVmops(buildpackModule)
addCallable(buildpackModule):
  proc build(): bool
const addins = implNimscriptModule(buildpackModule)
discard loadScript(NimScriptFile(script), addins)

outputs this:
building nim...
(output: "", exitCode: 0)
done

While I would expect the exit code to be 1.

To implement all the Nimscript procedures https://github.com/nim-lang/Nim/blob/devel/compiler/scriptconfig.nim#L29 needs to be invoked, before our script is loaded, which will require a PR to the createInterpreter procedure the compiler API exposes.

I'd like to argue that it's better to follow the documented behavior since that's what people would expect. If the developer is loading unknown scripts that might fail they should use a try/catch to prevent their program from crashing.
At the very least, the nimscript should not continue running after the exec returns with an error. Since that should lead to potentially unwanted and unexpected behaviors.
In my case, I'm trying to build a task runner based on nimscripts. I'm using this library to load configuration values directly from the scripts. I'm also running procs as tasks.
If someone was to use an exec statement to do a crucial command, they would expect their script to stop execution if the command fails.
I'm submitted a PR with some changes and other features I've implemented for myself. Feedback is welcome 😄

try/catch to prevent their program from crashing

That's the issue you cannot wrap the native code in a try catch from Nimscript since the error occurs inside the Nim code
import nimscripter

proc doThing(): int = raise newException(ValueError, "hello")
exportTo(myImpl, doThing) # The name of our "nimscript module" is `myImpl`
const
  scriptProcs = implNimScriptModule(myImpl) # This emits our exported code
  ourScript = NimScriptFile"""
try:
  discard doThing()
except CatchableError as e:
  echo e.msg"""
let intr = loadScript(ourScript, scriptProcs) # Load our script with our code and using our system `stdlib`(not portable)

Will crash the binary due to an unhandled exception.

No, i mean that the main program has to use a try/catch when loading the script. I do something like this in my application
import nimscripter

proc doThing(): int = raise newException(ValueError, "hello")
exportTo(myImpl, doThing)
const
  scriptProcs = implNimScriptModule(myImpl)
  ourScript = NimScriptFile"""
  discard doThing()
"""
try:
  let intr = loadScript(ourScript, scriptProcs)
except:
  echo "an error happened when loading script"

That way, the script will not continue execution when exec errors, and the exception can be caught in the main application.

Ah I see, perhaps it's fine.


PIN code room

Hi
I'm using Janus as gateway, and it works perfectly with Jangouts (and thanks for that).
Now; i got a test room configured with a PIN:
[12341]
description = pin test
pin = 12345
publishers = 6
bitrate = 128000
fir_freq = 10
record = false
When trying to go to this room through Jangouts; there is a popup with following message :
Missing element (pin)
Is there any way to implement the PIN code access into room ?
Thanks a lot !

@ancorgs I want to work on this. Can you please guide me a bit on this???

Fixed by #182


Additional UI Framework Templates

Investigating what it would take to modify the bootstrap template or add templates for all components to use another UI framework i.e. Semantic UI or @angular/material. Mixing and matching UI component and layout frameworks is obviously not ideal just to implement the form viewer. Different frameworks wrap various components differently to apply formatting. The most obvious choice would be to do an ngx-formio-material template addition or fork since the material components are native ngx.
What files in addition to those in the template definitions and component html would need to be modified?
Is there a possible path to make a selectable component template depending on UI framework choice?
<formio [template]="'bootstrap' | 'semantic' | 'material' | 'custom'"></formio>

This may mean:

simply having forks of ng2-formio for each framework
Just make the main project not dependent on a single UI framework (have multiple framework template definitions included), but be able to select at run-time a framework for which templates exist and let developers embedding include the appropriate framework styles as a third party dependency.

Hello @amccubbin
I am thrilled to see this come from the community. This library was actually developed to support multiple dynamic templates, which you can see from the templates folder.
This file https://github.com/formio/ng2-formio/blob/master/src/templates/bootstrap.templates.tpl.ts serves as the "template" that the library uses to load the template, which can also utilize custom dependencies.  The idea is to implement it like it is here https://github.com/formio/ng2-formio/blob/master/src/index.ts where to use Material you would say something like.
import { ModuleWithProviders } from '@angular/core';
import { FormioBaseModule } from './formio';
import { FORMIO_MATERIAL } from './templates/material.templates';
FormioBaseModule.setTemplate(FORMIO_MATERIAL);
export const FormioModule = FormioBaseModule.forRoot();

This would then load the material template into the core renderer and it would use that instead. I did run into an issue though with the forRoot() declarations like Datetimepicker (which is bootstrap specific. Here is the issue for that which will need to get resolved to keep the core agnostic of template. https://github.com/angular/angular/issues/14022. Until that is fixed, I had to do something ugly like this to get it to not throw errors.  https://github.com/formio/ng2-formio/blob/master/src/formio.ts#L20
Let me know if this points you in the right direction.  My goal is to have this library support all the major UI frameworks.
Thanks!
Travis.

Great, that helps a lot. I'll poke around and try to scope out the time it would take to make this work. Since I'm not using bootstrap, having alternative templates would be quite helpful.

How do the recent changes to the underlying renderer affect templating? Will integrating material design directly be possible, or will we be forced to use bootswatch for styling?

@travist — links from your previous answer aren't working anymore. Can you please suggest what is current recommended solution for applying Material to Form.io?

HI.  Is there any update to using different templates (eg Material) ?  The link above is broken...

same issue, please suggest.

The angular-formio library is now a wrapper around our Vanilla JS renderer @ https://github.com/formio/formio.js. The unfortunate thing is that templating is not as easy with the VanillaJS renderer than the previous angular version.
What will be needed is the ability to control the class names that are created within this renderer so that any CSS framework can be applied to it.

@travist Could you please confirm if angular/material can be applied on formio and if so, what needs to be done to get the formio working with angular/material.

@travist : We have the same question as @vipinc38, our project also requires to mix Angular/Material with form.io

We are working on a new solution to wrap the existing angular-material to create a new Form.io renderer around that framework. This is coming, but it may be the end of the year before it is ready for production.

thanks for the quick response @travist it's helpful to know.

Closed due to no activity


Incorrect byte swapping with gcc 11.2 and certain compiler options

Hi Chad,
thanks a lot for making and maintaining this package. I deeply appreciate your work.
Last week I stumbled over a very surprising problem in a specific combination of gcc version and compiler flags. It is affecting (at least, not sure if only) reading of float64 mseed files. The problem manifests when the compiler aggressively optimizes ms_gswap8a().
To reproduce the problem, try

gcc 11.2.0 (arch linux ships this as the default since about 2 weeks)
libmseed 2.19.6
CFLAGS="-O3 -flto"  make
make test should now show FAILED Test pack-Float64-encoded.test, Compare pack-Float64-encoded.test.ref pack-Float64-encoded.test.out

The problem does NOT occur when I do either of the following:

downgrade the compiler, or
add -fno-strict-aliasing, or
prevent gcc from optimizing ms_gswap8a by embedding it in

  #pragma GCC push_options
  #pragma GCC optimize ("O0")
  void ms_gswap8a(...) {...}
  #pragma GCC pop_options

use -O1 or remove -flto, or
let the code call ms_gswap8 instead of ms_gswap8a.

I am not sure what is the right way to fix the problem, what do you think?
Best regards
Sebastian

Hi @emolch.  Thanks for this report, that's a weird error, impressed you found it.
The byte swapping routines were replaced in PR #75 by @QuLogic.  Can you try the develop branch and tell me if the issue is resolved?
thanks in advance!

This is exactly the problem #74 and #75 are intended to fix.

I'm going to assume this issue is resolved with the changes in #74.  Please re-open if not the case.


How to go through results in local search with return

Check for existing issues

[X] Completed

Describe the feature

If I do search above and press return, it will do this:

It will still have search open but jump to result.
Instead I want what VSCode has.
I do search, I can press return inside the search to jump between results. Then I can press escape to actually select the result I want.

Hey @nikitavoloboev it looks like you may have vim mode enabled (from some of your other bug reports). In Vim mode we emulate vim's keyboard bindings for search:

/ opens the search (or cmd-f)
<enter> runs the search and focuses the first result
n and N to go forward and backward

If you'd prefer to use enter for this, and don't use vim's default <enter> binding (move to the first character on the next line) you could try adding this to your key bindings file:
[
  {
    "context": "Editor && vim_mode == normal && !VimWaiting",
    "bindings": {
      "enter": "search::SelectNextMatch",
      "shift-enter": "search::SelectPrevMatch"
    }
  }
]

Ok this is close to what I want.
The thing I actually want is to be able to use return in search results like what I get with
[
  {
    "context": "Editor && vim_mode == normal && !VimWaiting",
    "bindings": {
      "enter": "search::SelectNextMatch",
      "shift-enter": "search::SelectPrevMatch"
    }
  }
]

With above setting added.
But ALSO want to be able to use enter in vim as I do now.
Can I do this?

Unfortunately I don't think we include in the keymap context whether or not search is open (but that seems like a very reasonable request, thank you!)


RPC Overhaul (WIP)

This is a WIP and thought i'd post an issue so people can chime in and know what will be happening over the next while as i'm in between bug diagnostics and fixes as well and improvements overall. some will increase performance as well. I been in bitcoin code learning about all the improvements etc they have made in this field.
Improvements:

Remove the LOCK for cs_main pwalletMain->cs_wallet from the RPC caller itself
Removing these locks from there and placing the locks in the rpc calls the same way bitcoin did improved performance there and eliminate unnecessary locking when incorrect amount of parameters were set thus throwing the json runtime. Its not necessary and counterproductive to lock to throw the help when incorrect amount of parameters are entered. Currently if there was a delay waiting for a lock you could wait for the runtime error reply this should not be the case.
Added categories to help rpc command to sort all the rpc functions into appropriate categories.
Fixed and add proper ConvertTo for parameter types and missing conversions as well. (ex listtransactions was missing bool etc)
Adding locks to the rpc functions itself also allows better control and shorten the scopes of the locks in turn freeing them sooner then later.
Also improves from locking both cs_main and pwalletMain->cs_wallet when only one of the locks are required. (Keep in mind gridcoin has some differences in commands and i will keep both locks when necessary)
Move the execute and list functions to RPC calls without the need for list and execute.
If any locks are required in the previous execute or list functions they will be added
If any conversions are needed they from execute and list they will be added properly to use the RPC as it was intended.
Help command will display help information with categories so user can go help wallet etc
All original RPC functions will not be affected they will still be entered the same
Fixing some broken RPC calls and eliminating any duplicates
Adding debug flag for rpc response times for dev testing

This is WIP and im working on it when i can thou been tied up lately. I'm about 40% complete and its running smoothly and looks nice. Will update this and let everyone know of more information when I have time and available.
If there are any requests as to additions etc do comment and make me aware.
@denravonska thought I should post this as some were asking what kind of improvements they will see. Please add the enhancement tag and if u feel the need to add bug fix for the missing conversions and broken rpc calls. this will be a good improvement for the wallet RPC.

Why is this an issue, not a PR?
You are great, bu picking up on this.
To be clear, I am strongly  against including into the next release, maybe the one after.

Wouldn't be an enhancement tag etc. Issue is also to allow input as well as requests that could be helpful for users and rpc.

Now I think i get it. This is summary of what you are going to do.

yes summary of work in progress i'm partially done just been on hold
XD

Does this update #527 in any way?

#1065 improves the machine friendliness of the polling rpc commands.

no clue i plan some clean up in how data is shown and grouped.

yes we are and @TheCharlatan took on the other parts. closing


Scaling keypoints

Thanks for the great repo. Id like to try to apply it to a custom dataset.
I noticed that the keypoints in the JHMDB dataset files are in a different scale. How can i normalize my keypoints similarly before passing it in through the dataloader?

I have been away from this field for a long time so I don't remember details.


Support config v3

See Upgrading to Hasura migrations config v3

Hey this Action is awesome!
Need to update Metadata SDK to v3

@GavinRay97, yeah that would certainly be helpful!
I started poking at this a bit and asked in Discord: Do you all have recommendations to programmatically interact with config v3 (i.e. resolving the !include syntax, making updates / writing back to the new directory structure, etc)?

Nick, sorry this got buried in my inbox I think =/
So that !include syntax is something we have built in-house, and to further muddy things a bit it isn't a universal directive. And by that I mean, for whatever reason it only works for tables and functions at the moment.
There's likely not a better way than manually traversing the JSON, and using a file read + parse on every item that contains !include =/
We may write some tooling around this at some point, though it'll wind up being the same thing I imagine (just that we've done the work already)

On another note, I've scheduled end of this week to try to update the Metadata SDK (time permitting) 🙂

There's likely not a better way than manually traversing the JSON, and using a file read + parse on every item that contains !include =/

No worries! And yeah, it wasn't bad to handle this in a file system context.


[FEAT] dsl support specialized queries (distance, rank,script, etc.

several of these are supported now. Add per query type issues if you need them.


Come to vote, brothers!

Vote, brothers!
@fancys @Aton5859 @LsKeke @wangpenghuix @MRJiaoWL @okzhangyu


Touchless Messaging

An often requested feature is the ability to consume messages from MassTransit without having a MassTransit dependency in the application domain. It's been requested several times, and is clearly a way that companies can create their own interfaces for message handling and use those interfaces to register consumers in MassTransit.
Consider the class below.
public class OrderProcessingService :
    IHandler<ProcessOrder>,
    IHandler<ProcessPremiumOrder>,
    IObservable<OrderReceived>,
    IObservable<OrderProcessed>
{
    IReadOnlyDictionary<string, object> _headers;

    public OrderProcessingService(IReadOnlyDictionary<string, object> headers)
    {
        _headers = headers;
    }

    public Task Handle(ProcessOrder message)
    {
    }

    public Task Handle(ProcessPremiumOrder message)
    {
    }
}

The class is a handler, defined by the domain-specific (and developer defined) IHandler<T> interface. The only constraint on the interface is that it has a single generic argument (the message type) and has a specific method used to handle the message.
public interface IHandler<T>
{
    Task Handle(T message);
}

To connect the handler to a receive endpoint, the bus configuration would be able to specify those types to allow the configuration engine to complete all the bindings.
endpoint.Service<OrderProcessingService>(context => new OrderProcessingService(context.Headers),
     x => x.ConsumeUsing(typeof(IHandler<>), "Handle"));

If the class has a constructor dependency of IDictionary<string, object>, the message headers will be passed as a parameter to that constructor. Any other constructor dependencies will be resolved by the consumer factory at creation time, which can delegate to whatever type of container is being used.
interface ProcessOrder
{
    DateTime Timestamp {get;}
    string OrderId {get;}
}

Once the consumer is created, if there are any IObservable interfaces on the consumer type, an observer will be subscribed to each one. In the event that any events are published, those events will be published on the bus.
interface OrderProcessed
{
    DateTime Timestamp {get;}
    string OrderId {get;}
}

So there is an initial pass at this going in develop: e34462ab9a01a44966c0727ae0c6509466adfd2b

Hi,
would this handle also other type of Marker types?
For example,  Fault<T> is coupled with MassTransit and is used to specify that the consumer is interested in faults generated while processing a particular message type.
It would be nice to have a way to specify a mapping between the MassTransit model (any type that MassTransit use as a convention marker) and the application domain model.
I am pretty sure this could be already done by implementing a custom filter, but a built in mechanism would be nice.
Something like:

    sbc
        .UseGlobalConventions(x => x.MapFaultTo(typeof(ApplicationDomain.Fault<>));

Or

    sbc
        .UseGlobalConventions(x => x.Map(typeof(Fault<>), typeof(ApplicationDomain.Fault<>));

I think that's taking it a bit too far versus mapping the types yourself. You're welcome to try but I'm not going to spend time on that one. The convention types were enough and I'll come back to them later to make them a little easier without all the boilerplate code perhaps.


secret(s) leak with headers of ReactiveHttpRequest.toString()

with the release of 3.2.4 to add toString that includes request headers has potentially exposed logging of secrets like oAuth tokens that are passed in as headers. See:
https://github.com/PlaytikaOSS/feign-reactive/compare/3.2.3...3.2.4
Class ReactiveHttpRequest, method: toString
https://github.com/PlaytikaOSS/feign-reactive/blame/develop/feign-reactor-core/src/main/java/reactivefeign/client/ReactiveHttpRequest.java#L96
@Override
public String toString() {
return "ReactiveHttpRequest{" +
", uri=" + uri +
", headers=" + headers + //this line logs the oAuth header...potential security vulnerability
", target=" + target +
"}";
}
The request makes sense to add target in toString() but not headers, thoughts?

please check 3.2.10


Make the Live Preview Better

The live preview page https://mkasberg.github.io/jplayer-flat-audio-theme/ should look a little nicer.
Don't go overboard - it should remain relatively simple as an example.
Consider:

Move Player to Center of screen.
Add a simple (non-white) background.
Add a nice button for the Github link.

I'll give this a shot.

If no one minds, I'll pop up with my solution too.

Prepared:

Created PR as well. Wanted to ask, for mobile devices there's no progress bar. Is it ok?

Wow, both of these look great!

@dearkathie Thanks for the comment about the volume slider on mobile. Opened #6 to address it. I believe the problem is unaffected by either of these themes.


text visibility and js related to local storage improved

Description
Improved visibility and solved bugs in js

Motivation and Context
The visibility of text in input and textarea improved. Controlled a possible bug in Local Storage.

How Has This Been Tested?
It was tested on different devices with different inputs and it stood upto expectations.

Screenshots (if appropriate):

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.

@its-puneet  kindly merge the pr with hacktoberfest 2022 tags


Fully Support Null Fields when Using Custom ObjectSerializer

Description
Fixes #28610
Resolves a gap in functionality where a custom ObjectSerializer would be used to convert a customer owned type into a Map<String, Object> which would be serialized by JacksonAdapter to be sent to the service. This didn't handle null key-value pairs properly as JacksonAdapter is configured, and will continue to be configured, to ignore null values, but this defeated the purpose of the custom ObjectSerializer to allow for custom handling to be applied to customer owned types.
Now, if an ObjectSerializer is included in the SearchClient it will be used to convert the document into a JSON string and be injected directly into the serialized JSON, giving full control of document serialization to a customer if they choose, or need, to use it. This should also add small performance improvement as before documents would be converted to JSON to be converted into a Map<String, Object> and would then later be converted back to JSON when sending the final request. Customers not using ObjectSerializer will continue to see the same runtime behaviors as before where null field values aren't included in the document sent to the service.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - search - tests

API change check
API changes are not detected in this pull request.


Reservations for External networks

Is your feature request related to a problem? Please describe.
Yes, the problem arises when working with multiple cloud providers that use different IPAM solutions. This can become a challenge, especially for organizations that do not have a dedicated IPAM solution. The Azure IPAM solution has been a valuable tool for documenting external networks. However, it currently lacks the ability to request a reservation for these external networks.
Describe the solution you'd like
I propose the addition of a feature that allows users to request IP reservations for external networks directly within the Azure IPAM solution. This feature would greatly enhance the functionality of the Azure IPAM solution and streamline the process of managing IP addresses across multiple cloud providers.
It could be as simple as providing a reservation flag for external networks. In the event of the reservation being for an external network, it would be marked it as "fulfilled" and possibly settled.
Describe alternatives you've considered
I've tried the following workaround:

Create a reservation to get both the address space as its ID.
Delete the reservation using the ID.
Create an external network using the provided address space from step 1

Unfortunately, the reservation gets marked as "cancelledByUser" and when trying to assign the external network the same address space as the reservation there's a 400 error:  "Block contains unfulfilled reservation(s) which overlap the target external network.".

Good morning @luisarnauth, and thank you for a wonderful suggestion.
The good news is that I'm literally working on something very similar as we speak for another customer. Would you like me to reach out for you when the test code is ready so that you can provide some feedback before it goes GA?

Sure, I'm available to test it against my use case and help you out on others

Excellent! If you'd like to have a quick sync call to see the plan of what I'm building, please feel free to drop me an email at<EMAIL_ADDRESS>and we can schedule 10/15 minutes to make sure this will meet all of your needs.

Hi @luisarnauth, thanks for the live conversation on Teams. I believe we are aligned that the current updates I'm already working on should meet your needs here.
I'm estimating to be complete with the changes by the end of the month. Thank for your patience, I'll reach out once everything is ready for your feedback and approval.
Have a good one!

Hi @luisarnauth, all of the new managed external network features have been incorporated into the latest release (v3.2.0) which were brought in from PR #279.
I hope everything is working to your expectations, please let me know if you have any questions/comments/concerns.
Thanks so much!


[BUG] Swagger model starting with "Map" produces invalid .swagger.dart api

Describe the bug
An endpoint which return a schema/model with a name that starts with Map breaks code generation. Renaming the MapXxx-model to MyMapXxx resolves the issue.
The generated swagger_broken.swagger.dart looks like this:
Future<chopper.Response<MapImage>> restMapImageGet({String? xApiVersion}) {
    return _restMapImageGet(xApiVersion: xApiVersion);
  }

To Reproduce
I have created a repository with a minimal example: https://github.com/mgj/flutter_openapi_generator_issue

Clone it
Run flutter pub get
Run flutter packages pub run build_runner build

Observe that the generated swagger_broken.swagger.dart is incorrect while swagger_works.swagger.dart is correct.
Expected behavior
The generated swagger_works.swagger.dart should instead looks like this:
Future<chopper.Response<MyMapImage>> restMapImageGet({String? xApiVersion}) {
    generatedMapping.putIfAbsent(MyMapImage, () => MyMapImage.fromJsonFactory);

    return _restMapImageGet(xApiVersion: xApiVersion);
  }

Swagger specification link
Working: https://github.com/mgj/flutter_openapi_generator_issue/blob/main/generator_issue/lib/rest/openapi/swagger_works.json
Broken: https://github.com/mgj/flutter_openapi_generator_issue/blob/main/generator_issue/lib/rest/openapi/swagger_broken.json
Library version used:
swagger_dart_code_generator: 2.10.1
Additional context
No additional context but please let me know if there is any more information I can provide to help resolve this issue.

Hi @mgj , thanks for patience. Issue is fixed!. Will be available in 2.10.3 in a day or two!


Hi Jared,
I think I made a mistake when running nanopolish and was hoping for your input.
I started by creating a nanopolish directory where I would put all the various Nanopolish outputs. Rather than moving my Nanopore reads.fq.gz file into that space, I symlinked the file to that new nanopolish directory. For example, the original fasta file might live here:
$HOME/nanopore/fastq/reads.fastq.gz

But my Nanopolish work was going to all live here:
$HOME/nanopolish

Thus my first file in that new Nanopolish directory was the symlinked file:
[me] $ cd $HOME/nanopolish
[me] $ ls
lrwxrwxrwx 1 me mylab   82 Sep  5 15:52 reads.fastq.gz -> $HOME/nanopore/fastq/reads.fastq.gz

I then proceed to run nanopolish index and the resulting information all lived within that Nanopolish directory. The job completed without issue so far as I can tell:
-rw-r--r-- 1 me mylab 613M Sep  6 08:44 reads.fq.gz.index.readdb
-rw-r--r-- 1 me mylab 358M Sep  5 21:11 reads.fq.gz.index.fai
-rw-r--r-- 1 me mylab 6.9M Sep  5 21:11 reads.fq.gz.index.gzi
-rw-r--r-- 1 me mylab 8.1G Sep  5 21:06 reads.fq.gz.index
-rw-r--r-- 1 me mylab  15M Sep  5 18:22 reads.sorted.bam.bai
-rw-r--r-- 1 me mylab  32G Sep  5 18:15 reads.sorted.bam
-rw-r--r-- 1 me mylab 4.2K Sep  5 17:09 npolish-mapping.log
lrwxrwxrwx 1 me mylab   82 Sep  5 15:52 reads.fastq.gz -> $HOME/nanopore/fastq/reads.fastq.gz

As a sanity check, if I look into the .fai file I can see all the normal read IDs and corresponding information. Things look normal to me.
I then ran nanopolish variants, but because I'm dealing with a big genome I had to use your suggested parallel command (which, thanks for correcting the typo). This resulted in about 30,000 .vcf files.
The command was something along these lines (it was a bigger shell script to work with our Slurm program, but I've abbreviated that here):
READSFILE=$HOME/nanopore/reads/reads.fastq.gz
BAMFILE=$HOME/nanopolish/reads.sorted.bam
DRAFTFILE=$HOME/someassembler/scaffolds.fasta
NPOLISHPYPATH=path/to/nanopolish/scripts/nanopolish_makerange.py
NANOPOLISH=path/to/bin/nanopolish/nanopolish

python3 $NPOLISHPYPATH $DRAFTFILE | parallel --results nanopolish.results -P 6 \
    $NANOPOLISH variants --consensus -o polished.{1}.vcf -w {1} -r $READSFILE -b $BAMFILE -g $DRAFTFILE -t 4 --min-candidate-frequency 0.1

A few (20!) days later, the job finished up, producing about 30,000 polished.xxxxx.vcf files, all which contained lots of information. There was also a nanopolish.results/1 directory created within  my $HOME/nanopolish parent directory, consisting of 30,000 subdirectories named for the .vcf chunks that nanopolish variants produced. And inside those subdirectories were always just 3 files: seq, stderr, and stdout. If I was to imagine what tree would have produced on that parent $HOME/nanopolish directory, I think the abbreviated version would look something like this:
$HOME/nanopolish
| --- polished.contig_1:0-50000.vcf
| --- polished.contig_2:0-50000.vcf
| --- polished.contig_3:0-50000.vcf
| --- nanopolish.results
       | --- contig_1:0-50000
                | --- seq
                | --- stderr
                | --- stdout
       | --- contig_2:0-50000
                | --- seq
                | --- stderr
                | --- stdout
       | --- contig_3:0-50000
                | --- seq
                | --- stderr
                | --- stdout

I carried on with the last part of the process by trying to combine the .vcf files present in the $HOME/nanopolish directory, but I get a long list of the same kind of error:
error: could not detect polishing window from input file polished.contig_10000:0-50000.vcf_polished.fa_polished.fa
error: could not detect polishing window from input file polished.contig_1000:0-50200.vcf_polished.fa_polished.fa
error: could not detect polishing window from input file polished.contig_1000:100000-150200.vcf_polished.fa_polished.fa

I'm wondering if the error is due to my directory structure. Maybe the .vcf files are in the wrong place and the vcf2fasta file can't find them?
I wonder if it's possible to use bcftools consensus to create a fasta file instead? I know there is plenty of information in these .vcf files - is there something unique about the vcf2fasta script that I should be aware of which may have an equivalent parameter in the bcftools consensus program?
Thanks for your advice!

Hello, Jared
I got the same problem here.
After running nanopolish variants in parallel as you suggested, I got the result:

[post-run summary] total reads: 1722, unparseable: 0, qc fail: 0, could not calibrate: 0, no alignment: 0, bad fast5: 0

And my vcf2fasta command is as following:
nanopolish vcf2fasta -g draft.fasta polished.*.vcf > polished_genome.fasta
I got one line of error

error: could not detect polishing window from input file polished.tig00000002:2000000-2050200.vcf

What to do?
Yiyi

Yes, the consensus sequence would only be partially polished. I suggest you
re-run the part that failed.
Jared
On Wed, Dec 5, 2018 at 1:28 AM yiyi11zhong<EMAIL_ADDRESS>wrote:

If I ignore the .vcf files that cannot be detected, what is the
consequence? A partially polished consensus sequence???
Yiyi
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jts/nanopolish/issues/463#issuecomment-444374204, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAXxn4Nr3bM_cZUiwi3IWs8lNOm58jz1ks5u12eVgaJpZM4Wner1
.

Thank you for your advice, it did work. And I also re-did the nanopolish index step to make sure everything went right. Though the no. of contigs remains the same as that before nanopolish, the SNPs and indels were corrected in some extent.
Thanks again.
Yiyi

Great


reload: Continually attempt to reload page.

This will continually attempt to reload the page every 5s to
try and compensate for the behavior in Chrome where it appears that
the tab has to be active or semi-active for location.reload to be
respected, which means that it should just continually try until
the page is active again, in which case the location.reload func
will work and reload the page.
Fixes: #6821.

The solution doesn't sound to be chrome-specific. Does this affect all browsers or Chromium-based browsers only?

In theory the solution can be a blanket solution, because if any browser is caught still existing 5000ms after a location.reload was called, it needs this fix as well.

Merged with a few small tweaks, thanks @brockwhittaker!


HADOOP-17179. [JDK 11] Fix javadoc error in Java API link detection

JIRA: https://issues.apache.org/jira/browse/HADOOP-17179
Skip Java API link detection

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 16s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
22m 48s
trunk passed

+1 :green_heart:
compile
0m 20s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
compile
0m 19s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
mvnsite
0m 23s
trunk passed

+1 :green_heart:
shadedclient
40m 22s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 18s
trunk passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
0m 18s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 14s
the patch passed

+1 :green_heart:
compile
0m 11s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javac
0m 11s
the patch passed

+1 :green_heart:
compile
0m 11s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
0m 11s
the patch passed

+1 :green_heart:
mvnsite
0m 13s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
16m 42s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 16s
the patch passed with JDK Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1

+1 :green_heart:
javadoc
0m 18s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

_ Other Tests _

+1 :green_heart:
unit
0m 15s
hadoop-project in the patch passed.

+1 :green_heart:
asflicense
0m 33s
The patch does not generate ASF License warnings.

65m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2186/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2186

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 45466476c30b 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / ab2b3df2de1

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.8+10-post-Ubuntu-0ubuntu118.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2186/1/testReport/

Max. process+thread count
414 (vs. ulimit of 5500)

modules
C: hadoop-project U: hadoop-project

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2186/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


[Launcher] On first launch, text box should be in focus

When using launcher for the first time, launcher should be in focus and shouldn't have to click using mouse in the search box. We should verify there's no debugger attached.

@alekhyareddy28 @ryanbodrug-microsoft this issue is up for grabs :) if you're going to look at this, please remove the other person from the assignees label. Thank you!

I'll start looking at it. Thanks @jyuwono

How I repro this:

Exit PowerToys (right-click and exit on PT)
Delete Cache folder from C:\Users<user>\AppData\Roaming\PowerLauncher
Run PowerToys
Execute alt+space. The search box is not in focus.

How I repro this:

Exit PowerToys (right-click and exit on PT)
Delete Cache folder from C:\Users<user>\AppData\Roaming\PowerLauncher
Run PowerToys
Execute alt+space. The search box is not in focus.

@jyuwono Is the repro 100% for you with these steps?

How I repro this:

Exit PowerToys (right-click and exit on PT)
Delete Cache folder from C:\Users\AppData\Roaming\PowerLauncher
Run PowerToys
Execute alt+space. The search box is not in focus.

@jyuwono Is the repro 100% for you with these steps?

yes

lets see if we can't do a quick flip here for just the text box

@jyu


files named as .env1, .env2 should get proper DOTENV_PRIVATE_KEY generated name

currently for .env1 or .env2, it is usingDOTENV_PUBLIC_KEY_DEVELOPMENT. expected DEVELOPMENT2

when solving this, also solve for .env files that are named not named .env - for example secrets.txt, etc

released as 1.6.1


ibus-engines.libpinyin: 1.9.3 -> 1.10.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/ibus-libpinyin/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.10.0 with grep in /nix/store/4ya0a61mnwzvlphi2a39q3wz8srak0g5-ibus-libpinyin-1.10.0
directory tree listing: https://gist.github.com/920acb2f5a3bfd5b8d50bff07772754e

cc @ericsagnes for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: ibus-engines.libpinyin
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: ibus-engines.libpinyin
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0
shrinking /nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0/libexec/ibus-engine-libpinyin
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0/libexec
patching script interpreter paths in /nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0
/nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0/libexec/ibus-setup-libpinyin: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0...
/nix/store/5xwakphilf2warm88ji2bxbbqw4r3zk5-ibus-libpinyin-1.10.0

Success on aarch64-linux (full log)
Attempted: ibus-engines.libpinyin
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0
shrinking /nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0/libexec/ibus-engine-libpinyin
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0/libexec
patching script interpreter paths in /nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0
/nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0/libexec/ibus-setup-libpinyin: interpreter directive changed from "/bin/sh" to "/nix/store/adw9jx59wnrh5659wz43nbjya3m4b3gl-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0...
/nix/store/8bm2z09pd6nr8isz7c9gpm35x33n3vqs-ibus-libpinyin-1.10.0


SAML authentication support

Support SAML authentication to login in cloudstack through identity federations.

Configure simulator to be used with Google's SAML (ask Vitaliy or Sergey Shestopalov for help). Implement SAML-based login.

This is a research issue:

Configure simulator to be used with Google's SAML
Investigate how the UI behaves
Create mockups to validate with PM and PO

After mockups and user cases are validated, requirements must be described @ershovaelena


Helm chart to deploy solana_wallet_exporter

Do you have a helm chart to deploy solana_wallet_exporter in kubernetes?
Thanks!

to fix your trouble check this fix, i see it in another issue,
https://github.com/aravinda-gamage/x86_64-win64-ranlib/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


rocmPackages.rocdbgapi: 6.0.2 -> 6.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.rocdbgapi is: Debugger support for control of execution and inspection state
meta.homepage for rocmPackages.rocdbgapi is: https://github.com/ROCm/ROCdbgapi
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.1.0 in filename of file in /nix/store/sm53g0sl8sygx6i1dlf909x066cksfwh-rocdbgapi-6.1.0

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
rocmPackages.rocdbgapi
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent
rocmPackages_6.rocdbgapi
rocmPackages_6.rocprofiler
rocmPackages_6.rocr-debug-agent

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/sm53g0sl8sygx6i1dlf909x066cksfwh-rocdbgapi-6.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.rocdbgapi https://github.com/r-ryantm/nixpkgs/archive/475c391db0087fa38af3809f8a268a14964fe4f1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/475c391db0087fa38af3809f8a268a14964fe4f1#rocmPackages.rocdbgapi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/sm53g0sl8sygx6i1dlf909x066cksfwh-rocdbgapi-6.1.0
ls -la /nix/store/sm53g0sl8sygx6i1dlf909x066cksfwh-rocdbgapi-6.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages marked as broken and skipped:

rocmPackages.rocdbgapi
rocmPackages.rocdbgapi.doc
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.rocdbgapi is: Debugger support for control of execution and inspection state
meta.homepage for rocmPackages.rocdbgapi is: https://github.com/ROCm/ROCdbgapi
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.2.0 in filename of file in /nix/store/w5z6jzzqbis2g4slfnyniww0dav252q2-rocdbgapi-6.2.0

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.rocdbgapi
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent
rocmPackages_6.rocdbgapi
rocmPackages_6.rocgdb
rocmPackages_6.rocprofiler
rocmPackages_6.rocr-debug-agent

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/w5z6jzzqbis2g4slfnyniww0dav252q2-rocdbgapi-6.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.rocdbgapi https://github.com/r-ryantm/nixpkgs/archive/591cf7e790ded09b5137b9d66e5182a64a64d9bd.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/591cf7e790ded09b5137b9d66e5182a64a64d9bd#rocmPackages.rocdbgapi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/w5z6jzzqbis2g4slfnyniww0dav252q2-rocdbgapi-6.2.0
ls -la /nix/store/w5z6jzzqbis2g4slfnyniww0dav252q2-rocdbgapi-6.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages marked as broken and skipped:

rocmPackages.rocdbgapi
rocmPackages.rocdbgapi.doc
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.rocdbgapi is: Debugger support for control of execution and inspection state
meta.homepage for rocmPackages.rocdbgapi is: https://github.com/ROCm/ROCdbgapi
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.2.1 in filename of file in /nix/store/j8nlwhl0qgzy7rnwyd7gm6cw7kznb6sk-rocdbgapi-6.2.1

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.rocdbgapi
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent
rocmPackages_6.rocdbgapi
rocmPackages_6.rocgdb
rocmPackages_6.rocprofiler
rocmPackages_6.rocr-debug-agent

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j8nlwhl0qgzy7rnwyd7gm6cw7kznb6sk-rocdbgapi-6.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.rocdbgapi https://github.com/r-ryantm/nixpkgs/archive/67e5a821b7e17564da6089505d912671b0c1e8e6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/67e5a821b7e17564da6089505d912671b0c1e8e6#rocmPackages.rocdbgapi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j8nlwhl0qgzy7rnwyd7gm6cw7kznb6sk-rocdbgapi-6.2.1
ls -la /nix/store/j8nlwhl0qgzy7rnwyd7gm6cw7kznb6sk-rocdbgapi-6.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages marked as broken and skipped:

rocmPackages.rocdbgapi
rocmPackages.rocdbgapi.doc
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.rocdbgapi is: Debugger support for control of execution and inspection state
meta.homepage for rocmPackages.rocdbgapi is: https://github.com/ROCm/ROCdbgapi
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.3.0 in filename of file in /nix/store/55yp6lf3iyq76cdq3lx2p8vjrgmal4bi-rocdbgapi-6.3.0

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.rocdbgapi
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent
rocmPackages_6.rocdbgapi
rocmPackages_6.rocgdb
rocmPackages_6.rocprofiler
rocmPackages_6.rocr-debug-agent

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/55yp6lf3iyq76cdq3lx2p8vjrgmal4bi-rocdbgapi-6.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.rocdbgapi https://github.com/r-ryantm/nixpkgs/archive/bda3761e009ed413361312e9d831ec9462e6ac6c.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bda3761e009ed413361312e9d831ec9462e6ac6c#rocmPackages.rocdbgapi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/55yp6lf3iyq76cdq3lx2p8vjrgmal4bi-rocdbgapi-6.3.0
ls -la /nix/store/55yp6lf3iyq76cdq3lx2p8vjrgmal4bi-rocdbgapi-6.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:fast_forward: 5 packages marked as broken and skipped:

rocmPackages.rocdbgapi
rocmPackages.rocdbgapi.doc
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

WARNING: Package has meta.broken=true; Please manually test this package update and remove the broken attribute.

meta.description for rocmPackages.rocdbgapi is: Debugger support for control of execution and inspection state
meta.homepage for rocmPackages.rocdbgapi is: https://github.com/ROCm/ROCdbgapi
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.3.1 in filename of file in /nix/store/4df0rz6rry0p3sw3nip3q2a9wd9458p8-rocdbgapi-6.3.1

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath

rocmPackages.rocdbgapi
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent
rocmPackages_6.rocdbgapi
rocmPackages_6.rocgdb
rocmPackages_6.rocprofiler
rocmPackages_6.rocr-debug-agent

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/4df0rz6rry0p3sw3nip3q2a9wd9458p8-rocdbgapi-6.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rocmPackages.rocdbgapi https://github.com/r-ryantm/nixpkgs/archive/2751e75fba2b3e7f4156ed4c0f51cb8f5c3f97a6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2751e75fba2b3e7f4156ed4c0f51cb8f5c3f97a6#rocmPackages.rocdbgapi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4df0rz6rry0p3sw3nip3q2a9wd9458p8-rocdbgapi-6.3.1
ls -la /nix/store/4df0rz6rry0p3sw3nip3q2a9wd9458p8-rocdbgapi-6.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:fast_forward: 5 packages marked as broken and skipped:

rocmPackages.rocdbgapi
rocmPackages.rocdbgapi.doc
rocmPackages.rocgdb
rocmPackages.rocprofiler
rocmPackages.rocr-debug-agent

Maintainer pings
cc @Madouura @Flakebi @mschwaig for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Fabric deploy script docs/patterns/fabric.rst does not work (for me)

I was trying to get deployment with fabric and distribute done like explained in the docs. However the deployment script always aborted with this error message
warning: manifest_maker: standard file 'setup.py' not found

So I tried for hours to find the problem and it seems that I have found it (although it is possible that the documented script works fine on other installations - I can only talk about my).
This is how the source code looks in the deploy function right now:
#...
with cd('/tmp/yourapplication'):
    run('tar xzf /tmp/yourapplication.tar.gz')
# now setup the package with our virtual environment's
# python interpreter
run('/var/www/yourapplication/env/bin/python setup.py install')
#...

I had to change it like this to make the script work:
#...
with cd('/tmp/yourapplication'):
    run('tar xzf /tmp/yourapplication.tar.gz')
# You have to be inside the folder where 'setup.py' resides
# in order to make it work
with cd('/tmp/yourapplication/%s' % dist):
    # now setup the package with our virtual environment's
    # python interpreter
    run('/var/www/yourapplication/env/bin/python setup.py install')
#...

Plus I changed run('mkdir /tmp/yourapplication') to run('mkdir -p /tmp/yourapplication') because after a failed deployment the dir has not been removed and the next deployment attempt prematurely ended "because the directory already existed"

I was seeing these same issues, and this change worked for me.


Parse Issue

This statement is valid JS (in Firefox & Chrome at least) but JSLint can't parse it:
var reExp = /(^( )?(if|for|else|switch|case|break|{|}))(.*)?/g;
yields this using the online tool:
0.16
Expected '\s' and instead saw ' '.
var reExp = /(^( )?(if|for|else|switch|case|break|{|}))(.*)?/g;
0.50
Expected ')' and instead saw '{'.
var reExp = /(^( )?(if|for|else|switch|case|break|{|}))(.*)?/g;
0.51
Expected a regexp factor and instead saw '{'.
var reExp = /(^( )?(if|for|else|switch|case|break|{|}))(.*)?/g;

I didn't write it but downloaded it.

Change your space to \s like it advised.

And escape the braces.

Thank you, this works. And it appears to work for me in the web page.
I was confused mostly, I think, by "JSLint was unable to finish"
Thank you once again.


fix(Header): Clean up obsolated actionTray code

Clean up obsoleted code remained when taken out actionTray under mobile view.
On the other hand, I'm trying to fix the logic of hide hamburger menu on mobile view when the following conditions are both fulfilled:

Hide Navigation is set: hideNavMenu assigned, and
Login is unavailable: loginAvailable={false}

BREAKING CHANGE:
actionTrayProps and activeTab will be void from now on.

Other than the menu hiding thing, looking good 👍