Attributes never returned are lost on creates and updates

Since we started never returning the password attribute via the return = "never" [1] mechanism [].
At https://github.com/RIPAGlobal/scimitar/blob/v2.7.1/app/models/scimitar/resources/mixin.rb#L420, ci_scim_hash no longer contains the password, but after all operations are applied, an all attributes update is done on https://github.com/RIPAGlobal/scimitar/blob/v2.7.1/app/models/scimitar/resources/mixin.rb#L494 using from_scim, targeting all attributes in the resource, including those never returned, and emptying them.
The included test case ilustrates the scenario.
[1] https://github.com/RIPAGlobal/scimitar/commit/413280a141f8987c4609b39b0b8503d2cfd6efa5
Fixes https://github.com/RIPAGlobal/scimitar/issues/105

This seem similar to what is being discussed in https://github.com/RIPAGlobal/scimitar/issues/6

@pond nothing really is an accident, but the thick of it is reverting this commit. While this commit and this commit add specs that are broken without the said revert. This PR is mostly an exploratory work to fix the issues presented on the specs added by the above commits, and I'm not suggesting we revert the mentioned commit, but that it's where the bug was introduced. Sorry about the confusion.

@xjunior I'm still a bit in the dark. https://github.com/RIPAGlobal/scimitar/pull/80 implements the password returning fix. All tests pass; v1 and main to this day pass every test, and always must else a PR cannot merge. I think you're trying to say that this PR here adds some tests to prove a bug and that's awesome, but just reverting #80 is definitely not a fix because it means the password attribute is being returned again.

I think you're trying to say that this PR here adds some tests to prove a bug and that's awesome:

Yes, that's what I said:

While this commit and this commit add specs that are broken without the said revert.

This PR adds these two commits, which proves that there's a bug while patching a resource with an attribute marked as 'return=never', in this case, User and password.

but just reverting https://github.com/RIPAGlobal/scimitar/pull/80 is definitely not a fix because it means the password attribute is being returned again.

I agree. This PR proves both: 1) there's a bug (and now a spec asserting that); 2) the bug was caused by that change.
This PR does not aim at solving both issues, but to expose one.

Yeah, I mean it needs fixing clearly (though it must be less urgent than I would expect, given the apparent severity, as this has gone unreported otherwise) but don't want to regress the non-returnable attributes PR in the process.
I'm trying to figure out how to fix it but the day has been constant interruptions and I'm really just doing nothing much but making mistakes now due to tiredness, annoyingly. Basically it comes down to as_json being the wrong place; it's to_scim, I think, that should be filtering. The trouble is, this only has schema access at the top level, then calls a private backend method for recursion through nested attributes and inside there, it has no visibility of the nested schema at each level. A custom schema that tried to not return something deeper than top-level wouldn't work.

...and the start of that is in https://github.com/RIPAGlobal/scimitar/compare/main...feature/fix-non-returnables, very much a WIP. The change to not return an attribute in the Name complex type is to prove the nesting failure (spec/models/scimitar/resources/mixin_spec.rb:163 passes but shouldn't).
Interestingly I think there was always a bug in spec/models/scimitar/resources/base_spec.rb at line 145, in the style of "how did that ever pass"; privateName is a returned: false attribute but line 153 expects it to be present in the PR 80 version of as_json. Surely, it should've expected that to be absent. Colour me confused.

Thanks for your further analysis on this, @pond! I have temporary fixes for the password on both create and patch, but wanted to bring this up here. I agree, it comes down to as_json. While working on this, one idea I had was to pass a reason for the SCIM serialization, that way we could render the returned=never attributes when rendering the SCIM model for writing purposes – but I despised this solution.
Sorry about the initial confusion on the description of this issue, I'm glad you could end up understanding the problem.

I had exactly the same idea initially - render because of a write op vs a read op, say - but I couldn't see a way to do it that didn't need controller changes and that'd break existing clients. Next, I thought about checking the action name but - euw, even worse. There shouldn't be any non-standard actions for SCIM but who knows, there might be in some cases. So that was a bad plan.
Anyway, the as-JSON / to-SCIM stuff gets used a lot. The gem's founding components have that strange split and some of it wasn't documented, so it's always been something of a guessing game. Part of the work I want to do here is to better document what you use and when. I'd rename as_json at this point except it's in use by client code so I can't; perhaps I'll add an alias instead; it's confusing, of course, since to_json is already a Thing and that's what you actually want most of the time.
TL;DR It made my head hurt. Much of what I got by building Scimitar from other implementations was very useful and constructed in ways I wouldn't have thought of, but some other areas are definitely not built how I'd have done it and were it not for a rush to get a SCIM implementation into our product (which of course was then never used as the client changed their minds! LOL) I might've taken more care there.

I had exactly the same idea initially - render because of a write op vs a read op, say - but I couldn't see a way to do it that didn't need controller changes and that'd break existing clients. Next, I thought about checking the action name but - euw, even worse. There shouldn't be any non-standard actions for SCIM but who knows, there might be in some cases. So that was a bad plan.
Anyway, the as-JSON / to-SCIM stuff gets used a lot. The gem's founding components have that strange split and some of it wasn't documented, so it's always been something of a guessing game. Part of the work I want to do here is to better document what you use and when. I'd rename as_json at this point except it's in use by client code so I can't; perhaps I'll add an alias instead; it's confusing, of course, since to_json is already a Thing and that's what you actually want most of the time.
TL;DR It made my head hurt. Much of what I got by building Scimitar from other implementations was very useful and constructed in ways I wouldn't have thought of, but some other areas are definitely not built how I'd have done it. Were it not for a rush to get a SCIM implementation into our product (which of course was then never used as the client changed their minds! LOL) I might've taken more care there.

I feel your pain, on both ways. I can think of ways to improve Scimitar too, starting by adding some abstractions on top of the mapping process.
One of the improvements I could be doing in the midterm, though, would be what I suggested in this issue: https://github.com/RIPAGlobal/scimitar/issues/107

I think this is looking decent:
https://github.com/RIPAGlobal/scimitar/compare/main...feature/fix-non-returnables

Please close this PR when that is open. Also, looks like it introduces a recursive attribute path, which can be useful here.

Closed in favor of https://github.com/RIPAGlobal/scimitar/pull/109


How to use the in clause in query builder class ?

What is your question?
Quoting previous question https://github.com/googleads/google-ads-java/issues/556 , I still need help with the third point on using the query builder class com.google.api.ads.admanager.lib.utils.QueryBuilder, the library doesn't contain an IN clause condition :/ .

Also with adwords selector I could use predefined enums for field names like ManagedCustomerField.CustomerId or ManagedCustomerField.Name etc what is the alternative to that for google ads
Thanks in advance

Hi,
The client library for the Google Ads API does not contain a query builder, but there is a Query Builder on our developer site to help you build queries interactively.
If you are looking for a way to retrieve the field names for a resource, you can use GoogleAdsFieldService as described in the guide and demonstrated in the GetArtifactMetadata example.
Thanks,
Josh


NuGet.Server ignores 'includeDelisted' query parameter

The command
.\nuget.exe list -IncludeDelisted

doesn't return delisted packages when EnableDelisting is set to true. Only the EnableDelisting configuration has currently an impact on the search but not the query parameter.
This method doesn't forward the 'includeDelisted' parameter to IServerPackageRepository. The interface needs an additional overload to take the parameter or the current method should be altered.

@patricksadowski , thanks for reporting the issue! We will add it to our backlog.
Our team is working on other features those days, and it will take us a while to get to this one... if you are interested in getting this fix in quickly, you are welcome to send us a pull request. We will review and merge promptly.

I've send you a pull request.

Thanks!

Merged, and released! Thanks, @patricksadowski
https://github.com/NuGet/NuGet.Server/releases/tag/3.1.2


Add deploy cli [WIP]

After talking with @bpmct  about how we could make code-server easier to install for our users, I came up with the idea to create a CLI for code-server. My first idea is to implement a deploy command like code-server deploy. I made a POC, and here is the DEMO video if you are interested. I would love to hear your feedback and thoughts.
https://www.loom.com/share/b29513055f874db8a6e41bbf94455d71
What needs to be done:

Add the build script pos install
Improve the copy if it is needed
Add some automated tests, at least on the basic functionalities
Add Prettier and ESLint

Add the build script pos install

What do you mean by this? Like another script to run after it is installed?

Improve the copy if it is needed

I think providing a link to generate a DigitalOcean Token (https://cloud.digitalocean.com/account/api/tokens) or we can even shorten, would help.

I'd love to ship something like this and write a blog post on it. Being able to customize the server name and region would also be 👌🏼
I'm happy to explore this, commander is an awesome library :)

I also noticed this just hangs... Any idea why?

What do you mean by this? Like another script to run after it is installed?

Yes, so we don't have to commit and push the build files.

I think providing a link to generate a DigitalOcean Token

Definitely, it is a good thing

@bpmct @jsjoeio  I publish it to test the release process, and you can run it on npx:
npx @coder/deploy-code-server

I think we can add the following features for a 0.2.0 version of the CLI:

Option to chose the region
Option to chose the machine type
Import the SSH key

Thoughts?

@bpmct @jsjoeio I publish it to test the release process, and you can run it on npx:
npx @coder/deploy-code-server

I think we can add the following features for a 0.2.0 version of the CLI:

Option to chose the region
Option to chose the machine type
Import the SSH key

Thoughts?

Amazing! Dude you shipped that so quick 🔥 I'll remember to share this with the next code-server release!
Those features for 0.2.0 sound great to me! I imagine they're not too difficult.


Fix privileged support

Fix privileged support.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

https://github.com/containerd/cri/pull/1349#issuecomment-563514786

Build execution time has reached the maximum allowed time for your plan (60 minutes).
hmm

This seems to be a appveyor issue. Containerd test is fine. Not sure whether it is golang version related. Try to update to 1.13.4 to be the same with containerd.

This seems to be a appveyor issue. Containerd test is fine. Not sure whether it is golang version related. Try to update to 1.13.4 to be the same with containerd.

time to move up anyway


Refactoring and multiple response_type support

Closes #29

I created the draft PR so far. Any ideas, suggestions are welcome :)

Codecov Report

Merging #30 (6d6c7bc) into master (c74fe17) will decrease coverage by 1.61%.
The diff coverage is 90.00%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage   99.28%   97.66%   -1.62%
==========================================
  Files          15       13       -2
  Lines         557      557
  Branches       56       66      +10
==========================================
- Hits          553      544       -9
- Misses          3        7       +4
- Partials        1        6       +5

Impacted Files
Coverage Δ

src/aioauth/models.py
94.44% <63.63%> (-5.56%)
:arrow_down:

src/aioauth/server.py
93.42% <90.56%> (-6.58%)
:arrow_down:

src/aioauth/grant_type.py
100.00% <100.00%> (ø)

src/aioauth/requests.py
100.00% <100.00%> (ø)

src/aioauth/response_type.py
100.00% <100.00%> (ø)

src/aioauth/responses.py
100.00% <100.00%> (ø)

src/aioauth/types.py
100.00% <100.00%> (ø)

src/aioauth/utils.py
95.50% <100.00%> (ø)

Continue to review full report at Codecov.

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


Should git-tips list be sorted alphabetically?

Closed due to non-feasibility and lack of interest.

Closed due to non-feasibility and lack of interest.


Update to Matrix to provide flexibility

Added functionality below:

Can use an existing instance
Check if bundle installed
Check if instance is running and start it
Does not clean up existing devices, only new instances
Can set the report output to either HTML or JSON
deviceFlavor and deviceOS not required if using an existing instance
Bypass for 'punycode' deprecation warning

Instead of ignoring the punycode deprecation, upgrade to a suitable replacement. https://stackoverflow.com/questions/68774489/punycode-is-deprecated-in-npm-what-should-i-replace-it-with might have some good ideas. This is important to avoid leaving security vulnerabilities unchecked.

Also need to ensure we have eslint and the usual suspects tied to a git hook to catch these issues.


Update Translator.php

Detail here:
https://laravel.io/forum/04-23-2015-langget-replaced-error?page=1

Please close this and send a PR to the correct repo.


MINOR: fixing JavaDocs and other cleanup

Thing IntelliJ highlighted...

@mjsax Could you please fix the conflicts?


libLAS: build with LASzip support

Motivation for this change
Things done

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

[ ] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build libLAS

Success on x86_64-linux (full log)
Attempted: libLAS
Partial log (click to expand)
shrinking /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin/las2col
shrinking /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin/las2pg
shrinking /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin/lasblock
shrinking /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin/ts2las
shrinking /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin/las2txt
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/lib  /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin
patching script interpreter paths in /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1
/nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1/bin/liblas-config: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/if0ad0zn3rzjqcp0821i4r7xr27ppqxg-libLAS-1.8.1...

Success on x86_64-darwin (full log)
Attempted: libLAS
Partial log (click to expand)
-- Installing: /nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/share/cmake/libLAS/liblas-depends.cmake
-- Installing: /nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/share/cmake/libLAS/liblas-depends-release.cmake
post-installation fixup
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/lib  /nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/bin
patching script interpreter paths in /nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1
/nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/bin/liblas-config: interpreter directive changed from "/bin/sh" to "/nix/store/r8bx3qf1bpncb14i9gzma4vr089pc3pv-bash-4.4-p19/bin/sh"
/nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/lib/liblas_c.2.4.0.dylib: fixing dylib
/nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1/lib/liblas.2.4.0.dylib: fixing dylib
/nix/store/k59z3js3rgj1rbnkr02zg3x16ya3c88h-libLAS-1.8.1

Failure on aarch64-linux (full log)
Attempted: libLAS
Partial log (click to expand)
   (int32 vgid, intn attrindex, int32 *offset, int32 *length);
    ^~~~~
    int
/build/hdf-4.2.13/hdf/src/tbbt.h:289:11: error: unknown type name 'VOID'
 HDFLIBAPI VOID        tbbtfree
           ^~~~
building of '/nix/store/i5jnsjnjf02gn92g3k89z9khb58wg2s4-hdf-4.2.13.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/yqwjb71n7criz7fxwhhq1k7bwcdni3wj-gdal-2.2.4.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/vrfqidnw2jwli71d6qygq5wys4520q3g-libLAS-1.8.1.drv': 1 dependencies couldn't be built
error: build of '/nix/store/vrfqidnw2jwli71d6qygq5wys4520q3g-libLAS-1.8.1.drv' failed


Online rendering of statisical maps in NeuroVault

@chrisfilo and the NeuroVault development team are also exploring visualisation tools through the NeuroVault platform.
You can easily create 3D (pial, inflated or flattened) figures using pycortex when you upload your maps to NeuroVault as well as interactive volume visualisation using papaya.

An example of a volume visualisation from http://neurovault.org/images/16208

Corresponding surface visualisation from http://neurovault.org/images/16208/pycortex

You can also generate glass brain images for each map, such as this one:

@chrisfilo: I absolutely adore these visualisations, but I'd like to have a discussion (with maybe some expert and non-expert NeuroVault-ers) around the barriers that people may meet regarding using them.
To give an example, if I were in the middle of doing analyses (rather than finished and sharing the final maps) I'm not sure I'd want to bother uploading all my maps just to make a figure to share with my research group at our next informal meeting.
What do you think? Are there ways of streamlining this process?

The advantage of putting "work in progress" maps on NeuroVault is that you can easily share them with collaborators who are not necessarily in the same room (think of emailing a link). Additionally, maps are stored on NeuroVault servers so it easier to recover them if something happens to your computer. On top of that we have formal reverse inference tools such as neurosynth decoding and image search which can help you interpret your findings in the context of existing literature. Collections can also be private if you don't want others to (yet) see your maps. Summing up I think there are some great advantages of using NeuroVault even for analyses that are still ongoing.
Nonetheless, you are right that if all you want is a static image uploading an image could be seen as a burden. It would not be that hard to provide papaya as a client side viewer with no need for uploading files (but maintaining the advantage of no need for installing software), but it's not really the long term mission of NeuroVault. We want people to share their maps and giving them tools to visualise and decode them is an incentive to start using NeuroVault early in the lifespan of the study so when the manuscript will be submitted/published maps will already be on NeuroVault (because you submitted them earlier to share them with collaborators, visualise them or decode them).
I hope this helps!

I'm convinced! I think the only visualisation that I'd like to see for offline use is the glass brain one. But I think your point about sharing the link with collaborators etc is a really good one.
Is there documentation in NeuroVault that promotes this use case of uploading early but not making public for a while? If not then I think we could make some as part of this project :smile:

You are right - we should describe this "workflow" more explicitly in the
documentation!
On Sat, Apr 16, 2016 at 8:56 AM, Kirstie Whitaker<EMAIL_ADDRESS>wrote:

I'm convinced! I think the only visualisation that I'd like to see for
offline use is the glass brain one. But I think your point about sharing
the link with collaborators etc is a really good one.
Is there documentation in NeuroVault that promotes this use case of
uploading early but not making public for a while? If not then I think we
could make some as part of this project [image: :smile:]
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/KirstieJane/BrainsForPublication/issues/6#issuecomment-210845866

Good stuff - ok - lets make that one of the goals for this project (rather than changing any code from NeuroVault for offline use) and if the documentation looks good then it can be merged into NeuroVault too :smiley:

Sounds like a plan! I will not be at the hackathon, but I can contribute
this ahead of time.
On Sat, Apr 16, 2016 at 9:22 AM, Kirstie Whitaker<EMAIL_ADDRESS>wrote:

Good stuff - ok - lets make that one of the goals for this project (rather
than changing any code from NeuroVault for offline use) and if the
documentation looks good then it can be merged into NeuroVault too [image:
:smiley:]
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/KirstieJane/BrainsForPublication/issues/6#issuecomment-210849303

Brilliant - I've made an issue asking for feedback on where the best place for documentation is (#3) so feel free to push is in whatever direction best suits you as a remote contributor!
Any bits of instructions that you can contribute would be great, but don't worry about it too much - I'm sure there will be someone willing to put the directions together from all the current NeuroVault documentation.


Update internal db storage

What has been done
With this PR, the performance of the in and update operations has been improved by replacing list with set in the recognition module.
How to test
make lint && make test

Secondly, do we have any stats about the improvement? The question is that will it be worth?

@serengil There are three reasons:

Converting set to list is time consumption, but not neccessary operation;
There are a few places when membership checking occurs: here and here. If old_images includes a huge amount of images (n), as well as representations includes another huge amount of images (m), total time complexity will be O(nm) if old_images is a list. Instead, if old_images is a set, total time complexity will be O(m);
It is guaranteed that there is no re-processing of the same images.

LGTM


Cron job updates

Description
Contributions

Closes #314
Added similar check in auto update process.

Checklist

[x] I added one or multiple labels which best describes this PR.
[x] I have tested the changes locally.
[x] This PR has a reviewer on it.
[x] I have validated my changes in a docker container and on Ubuntu. (Only needed for Odin or Docker Changes)

Didn't want to wait for the review? 😄
Looks good. Thanks for the quick fix.


Fine-tune the ordering for received

https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/flavors/at.rs#L51
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/flavors/at.rs#L89
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/flavors/at.rs#L120
I believe that using a Release operation in swap and an Acquire operation in load can effectively synchronize with the writing of the message to memory. Using SeqCst is not necessary in this context.
(glad to make a pull request if this seems sensible)

Similarly, in wake.rs, using SeqCst is unnecessary. Using Acquire/Release would be sufficient.
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L202
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L213
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L221
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L223
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L228
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L241
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L252
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L263
https://github.com/crossbeam-rs/crossbeam/blob/95d0bd04624473b546826fdb97f10abe849443e4/crossbeam-channel/src/waker.rs#L271

The SeqCst throughout crossbeam-channel is necessary to establish a total order between send/recv and is_empty. Without it the optimistic check in https://github.com/crossbeam-rs/crossbeam/blob/master/crossbeam-channel/src/waker.rs#L222 would be incoherent.


Youtube uploader is now the channel title

Hi guys, first I would like to thank you for uploading this repository, it is really useful for me.
In this PR you will find two new methods in both services Youtube and Vimeo:

parseVIdFromURL: Returns the video id from the original video url.
getVideoRawData: Returns the original API response. The function getVideoDetail is really nice but eventually you may want to get something else.

I also edited the uploader key in the Youtube Service, from my POV youtube doesn't want us to see uploaders as a single user but as a channel.
'uploader'        => $data->items[0]->snippet->channelTitle

Let me know what you think!
Cheers

thank you for PR but i don't understand your sentence

I also edited the uploader key in the Youtube Service, from my POV youtube doesn't want us to see uploaders as a single user but as a channel.

Let me try to clear this up.
If you check this line you will see that in the key:value array for the youtube video information, the value for the key uploader is now the channelTitle. Before it was null.
I did this because in the API response they provide the channeltitle not the username or email.


metadata.size is undefined in version 0.21.0

I'm using "sharp": "^0.21.0" from npm and this property doesn't seem to exist when i read from the filesystem at least:
 sharp('image_path')
    .metadata()
    .then(metadata=>{
        console.log(metadata.size); // undefined
    });

Related: #695

Hello, did you see the docs for metadata?

"size: Total size of image in bytes, for Stream and Buffer input only"

The benefit of the size property is mainly for Stream-based input as fs.stat is already available for the filesystem.

Apologies i did read the docs but somehow i missed that! Thanks!


[pull-kubevirt-e2e-k8s-1.21-sig-network] macvtap e2e test setup is flaky on CI

/kind bug
What happened:
macvtap e2e test setup is flaky on CI
Occurrences are rare (once a week): https://search.ci.kubevirt.io/?search=Macvtap+VMI+migration+with+live+traffic+should+keep+connectivity+after+a+migration&maxAge=336h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job
Example:
 13:24:28: • Failure in Spec Setup (BeforeEach) [236.303 seconds]
13:24:28: [sig-network] [Serial]Macvtap
13:24:28: tests/network/framework.go:27
13:24:28:   VMI migration
13:24:28:   tests/network/vmi_multus.go:1286
13:24:28:     with live traffic
13:24:28:     tests/network/vmi_multus.go:1308
13:24:28:       should keep connectivity after a migration [BeforeEach]
13:24:28:       tests/network/vmi_multus.go:1367
13:24:28:
13:24:28:       should have managed to figure out the IP of the server VMI
13:24:28:       Unexpected error:
13:24:28:           <*errors.errorString | 0xc00038ad00>: {
13:24:28:               s: "timed out waiting for the condition",
13:24:28:           }
13:24:28:           timed out waiting for the condition
13:24:28:       occurred
13:24:28:
13:24:28:       tests/network/vmi_multus.go:1360

Ref: https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/6488/pull-kubevirt-e2e-k8s-1.21-sig-network/1443556290562363392#1:build-log.txt%3A2877
What you expected to happen:
Not seeing this unstable error.
How to reproduce it (as minimally and precisely as possible):
Unknown
Anything else we need to know?:
Environment:
Current master, on the pull-kubevirt-e2e-k8s-1.21-sig-network job.

/sig network

This seems to be a low priority issue as it occurs only once a week and on an experimental CNI (macvtap).


Reference for group in Html component

Hi, thank you for your awesome library. I was wondering if it is possible to pass the ref to the  component.
My use case is manually passing through some of the events from html to konva. Right now I stick to konva._eventhandlername.
https://github.com/konvajs/react-konva-utils/blob/190fbf4d11ec709d711a889b8f0483f5cbdb6346/src/html.tsx#L36

Can you explain why do you need it?

Can you explain why do you need it?

For example one of the use cases included dragging html elements containing text rendered through this library. I was wondering if I could directly pass the mouse/pointer down event from html to konva group. Because right now if im not mistaken when I pass the event to bare konva with konva._eventhandlername it recalculated the position or stuff. I just thought it would be easier to pass the events manually and directly to the node I intend.

Sorry, I still don't understand it. Please create a demo.


Expose waveform saving options

"""
!!! By default, waveforms are extracted on a subset of the spikes !!!
Extracts waveform on paired Recording-Sorting objects.
Waveforms can be persistent on disk (mode="folder") or in-memory (mode="memory").  By default, waveforms are extracted on a subset of the spikes (max_spikes_per_unit)
and on all channels (dense). If the sparse parameter is set to True, a sparsity is
estimated using a small number of spikes (num_spikes_for_sparsity) and waveforms are
extracted and saved in sparse mode.
"""

#39


[bug]: dasing is failed in swamp tests

We should fill blocks with dummy data because empty blocks could not be reconstructed and error occurs:
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 0, "x": 0, "y": 1, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 0, "x": 1, "y": 0, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 0, "x": 0, "y": 0, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 1, "x": 1, "y": 1, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 1, "x": 1, "y": 0, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 0, "x": 1, "y": 1, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	DEBUG	ipld	ipld/retriever.go:155	requesting quadrant	{"axis": 1, "x": 0, "y": 0, "size": 1}
2022-05-23T14:51:48.988+0300	WARN	ipld	ipld/retriever.go:70	not enough shares to reconstruct data square, requesting more...	{"err": "failed to solve data square"}
2022-05-23T14:51:48.988+0300	ERROR	share	share/full_availability.go:35	availability validation failed	{"root": "e1eLNRsbC71wuzUAGevJZMRKFAo373FbVSp/jzFazRk=", "err": "merkledag: not found"}
2022-05-23T14:51:48.988+0300	ERROR	das	das/daser.go:234	sampling failed	{"height": 20, "hash": "ABA806CCA9BC5C58437F27A14A65270259D8D6476C593074A7EB265DB1D7D054", "square width": 2, "data root": "e1eLNRsbC71wuzUAGevJZMRKFAo373FbVSp/jzFazRk=", "err": "da: data not available"}

After slowing down block generation in swamp tests, DASing works. Closing issue.


overrides not work for inet

Version
1.27.0
What happened?
version: "2"
sql:
  - schema: ["sql/schema/*.sql"]
    queries: ["sql/query/*.sql"]
    engine: "postgresql"
    database:
      uri: ${DB_URL}
    gen:
      go:
        out: "model"
        emit_interface: true
        emit_json_tags: true
        emit_pointers_for_null_types: true
        overrides:
          - db_type: "inet"
            go_type: "net/netip.Addr"

for field:
  ip_address inet,

generated:
	IpAddress  pqtype.Inet   `json:"ip_address"`

Relevant log output
No response
Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
No response
What operating system are you using?
macOS
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

I tried
overrides:
          - db_type: "inet"
            go_type: "string"

still failed.

@i11010520 Unless your inet is also NOT NULL in the schema, you want nullable: true in your override
IOW
        overrides:
          - db_type: "inet"
            go_type: "net/netip.Addr"
            nullable: true

@i11010520 Unless your inet is also NOT NULL in the schema, you want nullable: true in your override IOW
        overrides:
          - db_type: "inet"
            go_type: "net/netip.Addr"
            nullable: true

:)
It seems that net/netip.Addr does not match with inet well.
I decided to define IP field as TEXT finally.


Fixed Firestore collections samples

Checklist
Only documentation fix.
Description
Two samples in the Docs are using wrong variable names.

Thanks for the fix


Yoimiya's Firework Flare-Up normal atk. dmg doesn't change when Vaporize or Melt is toggled

As title says. The damage number doesn't change when toggling Vape or Melt. Nothing changes this, teammates, buffs or artifact sets/requirements.

You need to enable her infusion on the Talents tab. Optimizer does not assume her infusion is enabled by default


cannot read property split of undefined

Hello,
getting this weird error.
D:\GitHub\work>node cron\scrape.js
Unhandled rejection TypeError: Cannot read property 'split' of undefined
    at D:\GitHub\work\node_modules\snoowrap\dist\request_handler.js:232:37
    at tryCatcher (D:\GitHub\work\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (D:\GitHub\work\node_modules\bluebird\js\release\promise.js:510:31)
    at Promise._settlePromise (D:\GitHub\work\node_modules\bluebird\js\release\promise.js:567:18)
    at Promise._settlePromise0 (D:\GitHub\work\node_modules\bluebird\js\release\promise.js:612:10)
    at Promise._settlePromises (D:\GitHub\work\node_modules\bluebird\js\release\promise.js:691:18)
    at Async._drainQueue (D:\GitHub\work\node_modules\bluebird\js\release\async.js:138:16)
    at Async._drainQueues (D:\GitHub\work\node_modules\bluebird\js\release\async.js:148:10)
    at Immediate.Async.drainQueues (D:\GitHub\work\node_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:649:20)
    at tryOnImmediate (timers.js:622:5)
    at processImmediate [as _immediateCallback] (timers.js:594:5)

Here is the code I am using:
const config = require('../config');
const snoowrap = require('snoowrap');
const subreddits = [
  'Laptop'
]
const r = new snoowrap(config.reddit);
r.getSubreddit(subreddits[0]).getNew({time: 'year'}).then(console.log);

pretty straight forward stuff.
any ideas why this is happening?
node v7.2.0 win 10m latest snoowrap lib

weird so I had my app as a "web app". change it to "script" and now it works. weird error still though.

Thanks, I'm glad you managed to figure it out.
For future reference, what was in your config file? (You can omit things like credentials, of course -- I'm just interested in what type of authentication you used that caused the confusing error.)

It was the fact that my Reddit application type was set to web app  it I was using username/password combo.

I had the same error as above and changing the Reddit application type to script fixed the issue as well.
I was using nodeJS.


Couldn't Complete the Tutorial

I hit a roadblock and couldn't get very far. "On the Project pane, go to Assets\AzureSpatialAnchors.SDK\Resources." I couldn't find the SDK. Doesn't seem to be in the project.
Also, some of the screen are outdated.
Vinnie Tieto
Technical Writer, MS Mixed Reality Team
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 123315ce-4945-a613-4cb6-cbfe22ef9d42
Version Independent ID: 17ef871c-3aa5-f67b-5c97-fcce3fb7df85
Content: Quickstart: Create a HoloLens app with Unity - Azure Spatial Anchors
Content Source: articles/spatial-anchors/quickstarts/get-started-unity-hololens.md
Service: azure-spatial-anchors
GitHub Login: @craigktreasure
Microsoft Alias: crtreasu

@vtieto - Thank you for your query , our team will review and get back to you at the earliest.

Hello @vtieto
I have assigned the issue to the content author for further review and update the doc as appropriate.

@SatishBoddu-MSFT Please re-assign to @msftradford. Thanks!

Hi @vtieto, I'm happy to take a look at this with you. We're going to go ahead and leave this issue open (internal #30720836) and have it serve as a reminder to update the outdated screencaps in the document.
For helping with your specific issue, can you give us an idea of what you do see in your Project pane? Hopefully, you see "Favorites", "Assets", and "Packages". If you have an "Assets" directory, can you expand it and send us a screen cap of the contents? Thanks!

@vtieto can you close this issue? (or show me how to close it)

@msftradford + @vtieto don't know who else to tag. This issue has been resolved and can be closed.

Closing as per instructions from Patrick Misteli.


tr.simpleRequests is not a function

const TestRail = require('testrail-promise'),
      tr       = new TestRail(URL, LOGIN, PASSWORD);

tr.simpleRequests();

Make an error

Thank you for noticing this. I accidentally named the function and a variable the same thing.

Looks like fixed.
Thank you a lot!


No idea if this is the right method to let you know ...

I am the person behind mySocialFeeds.com and trying to support as many Social Rss Feed methods as possible. A few methods and scripts based on your project are used by myself too but besides that I wrote +40 extra Rss Bridges [some totally new, and some based on existing ones].
Currently I do not have a lot of experience with GitHub and how to put my own sources together with your resources. Maybe some of you like to see which ones I created.
If possible it will be nice someone is able to help me to share my sources with your team. If anyone is interested.
Thank you in advance,
Tom Dings

Hello,
Thanks for contacting us ! I think it would be great if we managed to implement at least some of these bridges upstream (I couldn't check which one you have created, your site seems down).
If you are interested, I could help you in the process of merging your sources upstream.

@MrCoding Any update on this? If you can send me a zip file of your bridges directory, I can help with the getting this merged (email in profile).

@MrCoding According to GitHub you can also just upload a ZIP file to this issue (just drag-n-drop to the write area): https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/
Let us know if you are still interested in sharing your files.

@MrCoding Is this topic still relevant?

mySocialFeeds dot com is now a spam domain. I think this can be closed.

Indeed. Thanks for the heads-up.


Keep the latest version of ORACLE APEX & ORDS in sync

This version of APEX is out of date. I need this image to keep up with the latest version of APEX on OCI. The latest version of ORACLE APEX in OCI at this moment is 23.2.4

Any specific feature you need from newer version of APEX. Free container image may be few months behind what;s in the ADB-S cloud. If you need the latest APEX, using ADB free in the cloud may be another option. What's blocking with container image being on lower version. You can still export and import app to Cloud, right?

@spanchum I cannot import things from the cloud into the adb-free's APEX lower version. I need to be on the same patch release to be able to develop locally, commit to git, and then push to the cloud, and repeat the process. We have a big team and we move fast. I want the development lifecycle to be fast and simple. I was able to apply my db's schema's objects into this version of 19c. The only thing I need, is for it to be on the latest patch release of APEX. It could be a huge productivity game changer with little effort.

@spanchum. Do you know when this image will be updated to 23.2? This docker image is exactly what we need. I understand "Current model is mainly to develop app in container and exporting to cloud". The thing is that I found this image a few months after I started developing the app on the cloud. We need some new components from 23.2, so that is why we are on 23.2. I tried the other oracle container registry images, but it is impossible to get the same setup.  This image is vital for our development!

@aosingh 23.2 is a big growth driver for apex. All of the new OCI/APEX developers will start out using APEX 23.2. It makes sense for ORACLE to upgrade this image, so new developers in enterprise teams can develop!

Hi @alexesca  We are working a next version of the image. We expect to publish in 3-4 weeks.

@spanchum @aosingh how is the next version of the image going? I really need it. I have been developing on 23c, but deploying on 19c and we are running into issues that are hard to fix. Please, let me know as soon as you push the image!

We are close to getting it out. Will keep you posted

@alexesca
We have pushed the next version of adb-free image
docker pull ghcr.io/oracle/adb-free:<IP_ADDRESS>

Please check the updated documentation


[Bug]: No available block found in 60 second.

Your current environment

The output of `python collect_env.py`
Collecting environment information...
 However, no error occurs when task="embedding" is not set. Additionally, when task="embedding" is set, no error occurs when using python -u -m vllm.entrypoints.openai.api_server --task embedding --pipeline-parallel-size 8.
from vllm import LLM
from vllm.config import PoolerConfig
llm = LLM(
        model="./Llama-3.1-Nemotron-70B-Reward-HF",
        task="embedding",
        tensor_parallel_size=8,
        pipeline_parallel_size=1,
        trust_remote_code=True,
        dtype='bfloat16',
        enable_chunked_prefill=False,
        enable_prefix_caching=True,
        disable_custom_all_reduce=True
)

prompt = "What is 1+1?"
output = llm.encode(prompt)

INFO 11-26 12:54:37 config.py:1854] Downcasting torch.float32 to torch.bfloat16.
INFO 11-26 12:54:44 config.py:1025] Defaulting to use mp for distributed inference
WARNING 11-26 12:54:44 arg_utils.py:1030] The model has a long context length (131072). This may cause OOM errors during the initial memory profiling phase, or result in low performance due to small KV cache space. Consider setting --max-model-len to a smaller value.
INFO 11-26 12:54:44 llm_engine.py:249] Initializing an LLM engine (vdev) with config: model='./Llama-3.1-Nemotron-70B-Reward-HF', speculative_config=None, tokenizer='./Llama-3.1-Nemotron-70B-Reward-HF', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, override_neuron_config=None, tokenizer_revision=None, trust_remote_code=True, dtype=torch.bfloat16, max_seq_len=131072, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=8, pipeline_parallel_size=1, disable_custom_all_reduce=True, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), observability_config=ObservabilityConfig(otlp_traces_endpoint=None, collect_model_forward_time=False, collect_model_execute_time=False), seed=0, served_model_name=./Llama-3.1-Nemotron-70B-Reward-HF, num_scheduler_steps=1, chunked_prefill_enabled=False multi_step_stream_outputs=True, enable_prefix_caching=True, use_async_output_proc=False, use_cached_outputs=False, mm_processor_kwargs=None, pooler_config=PoolerConfig(pooling_type=None, normalize=None, softmax=None, step_tag_id=None, returned_token_ids=None),compilation_config=CompilationConfig(level=0, backend='', custom_ops=[], splitting_ops=['vllm.unified_flash_attention', 'vllm.unified_flash_infer', 'vllm.unified_v1_flash_attention'], use_inductor=True, inductor_specialize_for_cudagraph_no_more_than=None, inductor_compile_sizes={}, inductor_compile_config={}, inductor_passes={}, use_cudagraph=False, cudagraph_num_of_warmups=0, cudagraph_capture_sizes=None, cudagraph_copy_inputs=False, pass_config=PassConfig(dump_graph_stages=[], dump_graph_dir=PosixPath('.'), enable_fusion=True, enable_reshape=True), compile_sizes=<function PrivateAttr at 0x7fe4fb5aeb90>, capture_sizes=<function PrivateAttr at 0x7fe4fb5aeb90>, enabled_custom_ops=Counter(), disabled_custom_ops=Counter())
WARNING 11-26 12:54:45 multiproc_gpu_executor.py:56] Reducing Torch parallelism from 96 threads to 1 to avoid unnecessary CPU contention. Set OMP_NUM_THREADS in the external environment to tune this value as needed.
INFO 11-26 12:54:45 custom_cache_manager.py:17] Setting Triton cache manager to: vllm.triton_utils.custom_cache_manager:CustomCacheManager
(VllmWorkerProcess pid=1634044) INFO 11-26 12:54:46 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634044) INFO 11-26 12:54:46 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=1634045) INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634045) INFO 11-26 12:54:47 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=1634047) INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634047) INFO 11-26 12:54:47 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=1634052) INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634052) INFO 11-26 12:54:47 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=1634049) INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634049) INFO 11-26 12:54:47 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634055) INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634055) INFO 11-26 12:54:47 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=1634058) INFO 11-26 12:54:47 selector.py:120] Using Flash Attention backend.
(VllmWorkerProcess pid=1634058) INFO 11-26 12:54:47 multiproc_worker_utils.py:215] Worker ready; awaiting tasks
(VllmWorkerProcess pid=1634044) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=1634052) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=1634058) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=1634044) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634045) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634052) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634045) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634058) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634049) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=1634055) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=1634047) INFO 11-26 12:54:55 utils.py:961] Found nccl from library libnccl.so.2
(VllmWorkerProcess pid=1634055) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634049) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
(VllmWorkerProcess pid=1634047) INFO 11-26 12:54:55 pynccl.py:69] vLLM is using nccl==2.21.5
INFO 11-26 12:54:59 shm_broadcast.py:236] vLLM message queue communication handle: Handle(connect_ip='<IP_ADDRESS>', local_reader_ranks=[1, 2, 3, 4, 5, 6, 7], buffer=<vllm.distributed.device_communicators.shm_broadcast.ShmRingBuffer object at 0x7fe596a0f550>, local_subscribe_port=60787, remote_subscribe_port=None)
(VllmWorkerProcess pid=1634047) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
(VllmWorkerProcess pid=1634045) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
(VllmWorkerProcess pid=1634055) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
(VllmWorkerProcess pid=1634044) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model .Llama-3.1-Nemotron-70B-Reward-HF...
(VllmWorkerProcess pid=1634052) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
(VllmWorkerProcess pid=1634058) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
(VllmWorkerProcess pid=1634049) INFO 11-26 12:54:59 model_runner.py:1072] Starting to load model ./Llama-3.1-Nemotron-70B-Reward-HF...
Loading safetensors checkpoint shards:   0% Completed | 0/62 [00:00<?, ?it/s]
Loading safetensors checkpoint shards:   2% Completed | 1/62 [00:09<09:09,  9.01s/it]
Loading safetensors checkpoint shards:   3% Completed | 2/62 [00:13<06:35,  6.59s/it]
Loading safetensors checkpoint shards:   5% Completed | 3/62 [00:18<05:44,  5.84s/it]
Loading safetensors checkpoint shards:   6% Completed | 4/62 [00:23<05:17,  5.47s/it]
Loading safetensors checkpoint shards:   8% Completed | 5/62 [00:28<05:02,  5.30s/it]
Loading safetensors checkpoint shards:  10% Completed | 6/62 [00:34<04:55,  5.28s/it]
Loading safetensors checkpoint shards:  11% Completed | 7/62 [00:39<04:49,  5.26s/it]
Loading safetensors checkpoint shards:  13% Completed | 8/62 [00:44<04:47,  5.33s/it]
Loading safetensors checkpoint shards:  15% Completed | 9/62 [00:49<04:40,  5.29s/it]
Loading safetensors checkpoint shards:  16% Completed | 10/62 [00:55<04:36,  5.32s/it]
Loading safetensors checkpoint shards:  18% Completed | 11/62 [01:00<04:26,  5.23s/it]
Loading safetensors checkpoint shards:  19% Completed | 12/62 [01:05<04:16,  5.13s/it]
Loading safetensors checkpoint shards:  21% Completed | 13/62 [01:10<04:09,  5.10s/it]
Loading safetensors checkpoint shards:  23% Completed | 14/62 [01:15<04:02,  5.06s/it]
Loading safetensors checkpoint shards:  24% Completed | 15/62 [01:24<04:54,  6.26s/it]
Loading safetensors checkpoint shards:  26% Completed | 16/62 [01:32<05:20,  6.96s/it]
Loading safetensors checkpoint shards:  27% Completed | 17/62 [01:41<05:38,  7.52s/it]
Loading safetensors checkpoint shards:  29% Completed | 18/62 [01:50<05:48,  7.93s/it]
Loading safetensors checkpoint shards:  31% Completed | 19/62 [01:55<05:02,  7.03s/it]
Loading safetensors checkpoint shards:  32% Completed | 20/62 [02:01<04:38,  6.63s/it]
Loading safetensors checkpoint shards:  34% Completed | 21/62 [02:06<04:13,  6.19s/it]
Loading safetensors checkpoint shards:  35% Completed | 22/62 [02:15<04:41,  7.03s/it]
Loading safetensors checkpoint shards:  37% Completed | 23/62 [02:23<04:49,  7.42s/it]
Loading safetensors checkpoint shards:  39% Completed | 24/62 [02:28<04:14,  6.70s/it]
Loading safetensors checkpoint shards:  40% Completed | 25/62 [02:34<03:53,  6.31s/it]
Loading safetensors checkpoint shards:  42% Completed | 26/62 [02:39<03:33,  5.93s/it]
Loading safetensors checkpoint shards:  44% Completed | 27/62 [02:44<03:16,  5.63s/it]
Loading safetensors checkpoint shards:  45% Completed | 28/62 [02:53<03:51,  6.80s/it]
Loading safetensors checkpoint shards:  47% Completed | 29/62 [02:58<03:28,  6.31s/it]
Loading safetensors checkpoint shards:  48% Completed | 30/62 [03:05<03:29,  6.54s/it]
Loading safetensors checkpoint shards:  50% Completed | 31/62 [03:14<03:42,  7.19s/it]
Loading safetensors checkpoint shards:  52% Completed | 32/62 [03:19<03:16,  6.57s/it]
Loading safetensors checkpoint shards:  53% Completed | 33/62 [03:28<03:29,  7.22s/it]
Loading safetensors checkpoint shards:  55% Completed | 34/62 [03:33<03:02,  6.52s/it]
Loading safetensors checkpoint shards:  56% Completed | 35/62 [03:34<02:16,  5.07s/it]
Loading safetensors checkpoint shards:  58% Completed | 36/62 [03:44<02:46,  6.39s/it]
Loading safetensors checkpoint shards:  60% Completed | 37/62 [03:53<02:59,  7.18s/it]
Loading safetensors checkpoint shards:  61% Completed | 38/62 [03:58<02:36,  6.52s/it]
Loading safetensors checkpoint shards:  63% Completed | 39/62 [04:03<02:20,  6.09s/it]
Loading safetensors checkpoint shards:  65% Completed | 40/62 [04:08<02:05,  5.71s/it]
Loading safetensors checkpoint shards:  66% Completed | 41/62 [04:13<01:55,  5.51s/it]
Loading safetensors checkpoint shards:  68% Completed | 42/62 [04:22<02:11,  6.59s/it]
Loading safetensors checkpoint shards:  69% Completed | 43/62 [04:31<02:18,  7.29s/it]
Loading safetensors checkpoint shards:  71% Completed | 44/62 [04:36<02:00,  6.71s/it]
Loading safetensors checkpoint shards:  73% Completed | 45/62 [04:46<02:06,  7.46s/it]
Loading safetensors checkpoint shards:  74% Completed | 46/62 [04:51<01:48,  6.79s/it]
Loading safetensors checkpoint shards:  76% Completed | 47/62 [04:56<01:32,  6.19s/it]
Loading safetensors checkpoint shards:  77% Completed | 48/62 [05:01<01:23,  5.96s/it]
Loading safetensors checkpoint shards:  79% Completed | 49/62 [05:11<01:31,  7.04s/it]
Loading safetensors checkpoint shards:  81% Completed | 50/62 [05:15<01:16,  6.39s/it]
Loading safetensors checkpoint shards:  82% Completed | 51/62 [05:21<01:07,  6.15s/it]
Loading safetensors checkpoint shards:  84% Completed | 52/62 [05:26<00:57,  5.78s/it]
Loading safetensors checkpoint shards:  85% Completed | 53/62 [05:31<00:51,  5.70s/it]
Loading safetensors checkpoint shards:  87% Completed | 54/62 [05:37<00:45,  5.65s/it]
Loading safetensors checkpoint shards:  89% Completed | 55/62 [05:46<00:46,  6.63s/it]
Loading safetensors checkpoint shards:  90% Completed | 56/62 [05:55<00:43,  7.23s/it]
Loading safetensors checkpoint shards:  92% Completed | 57/62 [06:03<00:38,  7.62s/it]
Loading safetensors checkpoint shards:  94% Completed | 58/62 [06:08<00:27,  6.90s/it]
Loading safetensors checkpoint shards:  95% Completed | 59/62 [06:13<00:19,  6.34s/it]
Loading safetensors checkpoint shards:  97% Completed | 60/62 [06:16<00:10,  5.38s/it]
Loading safetensors checkpoint shards:  98% Completed | 61/62 [06:22<00:05,  5.42s/it]
Loading safetensors checkpoint shards: 100% Completed | 62/62 [06:27<00:00,  5.32s/it]
Loading safetensors checkpoint shards: 100% Completed | 62/62 [06:27<00:00,  6.25s/it]

(VllmWorkerProcess pid=1634052) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
(VllmWorkerProcess pid=1634047) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
(VllmWorkerProcess pid=1634058) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
(VllmWorkerProcess pid=1634049) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
(VllmWorkerProcess pid=1634044) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
(VllmWorkerProcess pid=1634055) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
(VllmWorkerProcess pid=1634045) INFO 11-26 13:01:28 model_runner.py:1077] Loading model weights took 16.4605 GB
Processed prompts:   0%|                                                                                | 0/1 [00:00<?, ?it/s, est. speed input: 0.00 toks/s, output: 0.00 toks/s]/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
/home/weteliang/.mamba/envs/vllm/lib/python3.10/site-packages/vllm/connections.py:8: RuntimeWarning: Failed to read commit hash:
No module named 'vllm._version'
  from vllm.version import __version__ as VLLM_VERSION
(VllmWorkerProcess pid=1634052) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634044) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634047) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634058) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634049) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634055) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634045) WARNING 11-26 13:02:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634052) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634044) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634047) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634058) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634049) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634055) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634045) WARNING 11-26 13:03:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634052) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634044) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634047) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634058) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634049) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634055) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634045) WARNING 11-26 13:04:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634052) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634044) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634047) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634058) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634049) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634045) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634055) WARNING 11-26 13:05:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634052) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634044) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634047) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634058) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634045) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634049) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634055) WARNING 11-26 13:06:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634052) WARNING 11-26 13:07:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634044) WARNING 11-26 13:07:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634047) WARNING 11-26 13:07:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634058) WARNING 11-26 13:07:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634049) WARNING 11-26 13:07:36 shm_broadcast.py:391] No available block found in 60 second.
(VllmWorkerProcess pid=1634045) WARNING 11-26 13:07:36 shm_broadcast.py:391] No available block found in 60 second.

Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

I having the same issue too.


CI: Fix failure for PRs from fork

fixes #48

There is no attempt to create a deployment comment (which is desired as the PR is raised from a fork) and the CI passes. It seems to work. Please possibly review and please share feedback.

doubt: Since, there is no development/preview deployment taking place when the PR is raised from a fork. Please, could someone possibly share how we can view/test the changes? How do we know if the changes work and/or if the site builds?

I don't know. I think for now we can just develop from the main repository.
The workflow I am imagining is that anybody can send a PR, and the CI runs and builds a preview somehow.

I think for now we can just develop from the main repository.

Dr. Ondrej, please, could you possibly share if we shall close this PR or continue and/or merge this.
The changes in this PR avoid the CI from failing when pull requests from a fork are created. The previewing of PRs raised from a fork is not yet supported.

Thank you for the approval.


Update save_load_variables_en.rst

对齐save_load_variables_en.rst英文文档

follow:
https://github.com/PaddlePaddle/FluidDoc/pull/801

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

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


Is this "fake" or can this actually open a websocket?

it's not fake, it just simulates the basics of Bash such as "echo", "cat", "chmod", "mkdir" etc as a plugin you can use in your own games.
It will also come with a simplified Assembler language called "M99".
It is a work-in-progress school project that I will make open-source and available on a website once it's finished.


Helped optimize the code

The code is optimized by reducing one for loop and and one hash table. Thus making the optimum use of memory! I hope you will like it.

@Rohinsri
I Appreciate your efforts but please raise PRs for new problems too.
Thanks


Bug reading raw BrainVision data

Description of the problem
Got this error randomly:
"RuntimeError: Incorrect number of samples (0 != 36566600), please report this error to MNE-Python developers"
Second time I tried opening the same dataset it worked. Decided to report it anyway because the error message told me to...
Steps to reproduce
raw = mne.io.read_raw_brainvision(vhdr_file, preload=True)

Link to data
No response
Expected results
0
Actual results
0
Additional information
0

Thanks for the report! That's odd behavior. If it comes up again feel free to share the file and hopefully someone else can reproduce the issue. For now I'm going to close because it sounds like it might already be fixed/working.


NPM does not proxy?

Checklist
YES - Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
NO - Are you sure you're not using someone else's docker image?
YES - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
Describe the bug
With the proxy hosts enabeld i get no connection to the site. When i disable the proxy hosts i see the default congratulations from NPM.
So the dns points correct.
Ports are opend correct (port 80 and 443)

What version of Nginx Proxy Manager is reported on the login page?
V 2.3.1

To Reproduce
Steps to reproduce the behavior:

Go to test.sieliakus.nl (http and https) --> do not enforce ssl (yet)
Go to home.sieliakus.nl (only http)
Both pointed to the same ip.

Expected behavior
See a nginx welcome page.

Yes, you see the cloudflare IP adresses, not my home address.
But both pointing at the same ip wit a different outcome.

If you're strictly allowing traffic only from Cloudflare, then that would explain why LetsEncrypt is unable to reach <IP_ADDRESS>.

Wel, tested it with another domain name not behind cloudflare.
test.jeanineburgers.nl (point internal to nginx site)
test2.jeanineburges.nl (no rule made for yet)
both http.
BTW, the letsencrypt certificate is given, so communication is happening. only npm is not 'forwarding'

Excuse me, i had UFW installed blocking everything. Turned it off now it works. Sorry for the screwup MYBAD...


Updated validations.py Python Script

Closes:#1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!
From<EMAIL_ADDRESS>Sent: Sunday, November 22, 2020 12:03 AM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [google/it-cert-automation-practice] Updated validations.py Python Script (#9869)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA datahttps://cla.developers.google.com/clas and verify that your email is set on your git commitshttps://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoothttp://go/cla#troubleshoot (Public versionhttps://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA datahttps://cla.developers.google.com/clas and verify that your email is set on your git commitshttps://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must also be attached to your GitHub accounthttps://github.com/settings/emails.

ℹ Googlers: Go herehttps://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fgoogle%2Fit-cert-automation-practice%2Fpull%2F9869 for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/google/it-cert-automation-practice/pull/9869#issuecomment-731618183, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQREO4AT6XSMQBPEQKFDED3SRABZHANCNFSM4T56HXFQ.


[Chat Bug] /gymbans List - Titan

Only for Titan
/gymbans
The ban List for gym mons with print in chat when the command is run, but it is not clickable and doesnt let you view the link
It does work on Orion and Atlas.

Fixed, thanks for reporting


black screen on android devices

hello, I have successfully configured the project on a mac, when I enter an android device the screen image looks black but if I do any action on the black screen is reflected in the cell phone.
Do you have any idea why the black image is seen and how to fix it?

Is the device by any chance running on Android 14? Because Google introduced some changes in the APIs I am using to create the video stream and I havent got around to fixing it yet :( If it's lower than 14 then maybe something is wrong with the GADS-stream setup on the device. You can disconnect the device from the host, open Settings>Apps on the phone and do Force stop on the GADS-stream app. Then manually tap on the GADS-stream icon, you should see a popup asking for recording permissions, allow them, press the Home button and in the device notification bar you should see something like GADS-stream is recording this device screen. Then reconnect the device to the host and wait for it to become available and try again :)

I followed the steps you mentioned and it worked, I am testing on an android 13 device, thanks for your help

You got it! In theory setup of the stream should happen automatically but sometimes it fails with no obvious reason and I am not sure why :( I got a lot of improvements done but they are still on develop and I am not sure when they'll reach main. Nevertheless if you encounter other issues let me know :)

That was handled

Actually that was not handled - the problem is with the stream app itself - if the device is locked then the activity and stream do not start properly.. 😅 as long as your device is unlocked it should reliably start


Add bevy_xpbd_2d_f64 and bevy_xpbd_3d_f64 crates

A drawback of substepping is that it does not damp out high
frequency vibrations due to reduced numerical damping. This can
yield visual jittering. However, numerical damping can easily be
reintroduced by adding true physical damping. Also, for small time
steps, double precision floating point numbers are required. While
doubles are as fast as floats on CPUs, they currently still reduce the
performance on GPUs. Updating constraint directions after each
projection might cause instabilities when simulating tall stacks or
piles of objects. Investigating this problem is one of our directions
of future work.

Had a go at making crates with different precision levels, since it seems there are good reasons to prefer f64.
What do you think? It adds a bit of complexity to the crate, though... perhaps it's better to just scrap the f32 versions, like in @Aceeri's https://github.com/Jondolf/bevy_xpbd/compare/main...Aceeri:bevy_xpbd:doubles?expand=1 ?

We should definitely make f64 an option, but I think it'd be better to keep f32 as the default since it's what bevy and most crates use, and it's also a bit more efficient in terms of space and SIMD.
I'm not entirely sure what the best approach would be, but intuitively I'd say that we should just add an f64 feature and use #cfg(not(feature = "f64")) and #cfg(feature = "f64") to make a distinction between f32 and f64. In my opinion this would be simpler than having both f32 and f64 features and two additional crates for f64.
With this approach we probably won't be able to have examples where you can choose the type, so we would either have to choose a default (probably f32) or opt for some other way to implement examples. Would there be any other drawbacks to this approach that I'm missing?

cargo features are supposed to be additive, the reasoning being that if something depends on bevy_xpbd_2d and one of your dependencies (let's call it foo) depend on bevy_xpbd_2d as well, your dependency should be able to safely require extra features for bevy_xpbd_2d.
If that feature is f64, it will most likely break your app. On the other hand, if the dependency just uses another crate, everyone will be happy.
However, I'm not sure how common this scenario would be, but that's why I felt it was kind of "dirty" to have it bee the same crate.
Same reason why 2d and 3d are different crates, no?

Yeah, I can understand the feature additivity argument as well. Simultaneously having one physics world based on f32 and another based on f64 feels like a pretty uncommon scenario though, and there would probably be some workarounds for those cases as well.
I was also on the fence regarding 2D and 3D, but ended up making them into separate crates since it felt like there was a decently large and concrete difference in both implementation and usage. Also, it made it easy to make separate 2D and 3D examples.
I'm still not entirely sure which approach is better though; both have their pros and cons.

Yeah, lets go with only two crates for now.

Yeah, i made two of the examples work on both kinds of precision, by using the Vector and Scalar types, but they are worse examples aa a result (cubes and move_marbles)

Closing in favor of #20


Support location search

Is your feature request related to a problem? Please describe.

Currently we do not support search for locations
Describe the solution you'd like

Support search for location
Additional context

https://www.hl7.org/fhir/search.html#special
Would you like to work on the issue?

yes

I'm still trying to work out the math. There are a few methods to find the distance between two points on the earth however I am not sure how we can use indexes with them. All the methods I've come across would require a Full table scan.

@epicadk , have you been able to move ahead with this?

@epicadk , have you been able to move ahead with this?

Not really, I still can't figure out a way that provides high accuracy and would make use of the index. I will open a pr today with what I've tried so far

I tried adding the tests and realized what I'd done wasn't correct. I'll still try working on this but unassigning myself so that if someone has a better idea they can send a pr.

For these issue, I have come across an intresting description of using a bounded search that will help in looking up the index in the database.
This is a combination of calculating boundaries and using the database to filter the results within the bounds. Implementing the search on co-ordinates using an R-Tree index is the most efficient implementation on spatial indexes, SQLITE looks to be supporting the R-Tree index


reading the request data

Hello, rust newbie here. I haven't found a way to read the data from the requested and thus added the following patch. Am i missing something?
diff --git a/src/request.rs b/src/request.rs
index a74d022..25cdb85 100644
--- a/src/request.rs
+++ b/src/request.rs
@@ -43,6 +43,10 @@ impl Request {
     fn slice(&self, slice: &Slice) -> &[u8] {
         &self.data.as_slice()[slice.0..slice.1]
     }
+
+    pub fn data(&self) -> &str {
+        str::from_utf8(self.data.as_ref()).unwrap()
+    }
 }

 impl fmt::Debug for Request {

Are you thinking the body of the HTTP request? Right now self.data is just the actual HTTP request itself, so you'd just be getting out the same data as the other methods all return

Yeah, thinking about the body of the http request. Thanks for hint about self.data. Anyway am i right assuming is best to take a look at hyper instead of poking with minihttp as a foundation?

Ah ok yeah the "mini" part here in this crate is that it doesn't support HTTP bodies (it's a very small crate). For that I'd recommend hyper, yeah, as it correctly supports far more HTTP features than minihttp here.


Scaling doesn't seem to trigger on .net 6 dotnet-isolated function app

We've been struggling with getting our Azure Function apps to scale up. It's a function app consisting of an HTTP trigger, running on Elastic Premium. To test, I've created a function that just does a lot of work, and calling that from multiple threads. Maximum burst instances is set to max.
Here's what I've found so far:

If I deploy a function app that does NOT run dotnet-isolated, using the Microsoft.NET.Sdk.Functions NuGet, then the app scales up just fine.
If I deploy a function app that have "DotNet-Isolated|6" set in siteConfig/windowsFxVersion in the ARM template (this property is set automatically with Terraform if deployed with use_dotnet_isolated_runtime=true), then the function app doesn't scale beyond a single instance. It doesn't seem to make a difference if FUNCTIONS_WORKER_RUNTIME is set to dotnet-isolated (which happens automatically if deploying from Visual Studio), or just leave that setting out.
For some reason, if I create the function app through the Azure Portal, then the siteConfig/windowsFxVersion property is NOT set. Then I can deploy my dotnet-isolated app, set the appsetting FUNCTIONS_WORKER_RUNTIME="dotnet-isolated", and it seems to scale just fine.

I've tested with the latest version of the NuGets:

Microsoft.Azure.Functions.Worker version 1.10.0
Microsoft.Azure.Functions.Worker.Sdk version 1.7.0

I found an issue that looks familiar here: https://github.com/Azure/azure-functions-dotnet-worker/issues/792 however this is closed because apparently the solution was to upgrade the Microsoft.Azure.Functions.Worker.Sdk NuGet package to the latest version which I have done. I've also tested with the specific version mentioned for Microsoft.Azure.Functions.Worker.Sdk (1.2.0) - to no avail.
I do have a support ticket open for this as well, where we have given the function app name and so on if you can/need to check any details. The ticket ID is<PHONE_NUMBER>001094.
Is this a bug? What would the advise be here to get this working properly?

@hallgeir-osterbo-visma thanks for reporting this.
The behavior you've reported in your second bullet above, when using Terraform, is indeed invalid. I wouldn't expect that to prevent scaling, but setting that value with what you have defined will lead to unexpected behavior (like what we're seeing).
Tagging @kulkarnisonia16 to look at the Terraform behavior and work with the appropriate folks to have this corrected.

Thanks @fabiocav for the update here!
What would the correct value be for the windowsFxVersion attribute? Is the correct value basically blank, like it is when I create a function app manually through the portal? If I can know this, then I can probably work around it with using the azapi terraform provider instead.
Just some more info - If I deploy with the regular "dotnet" runtime (in-process), then everything scales perfectly. In that case, Terraform sets windowsFxVersion to DotNet|6, when use_dotnet_isolated_runtime  is set to false.
In Terraform, this value is controlled by the following block (azurerm provider version 3.37.0):
  site_config {
    application_stack {
      dotnet_version              = "6"
      use_dotnet_isolated_runtime = true # true => windowsFxVersion=DotNet-Isolated|6, false => windowsFxVersion=DotNet|6
    }

@kulkarnisonia16 have you had a chance to look into this? Can we transfer the issue to your team?

I have an update on this actually. We got some assistance on this from MS support in the ticket. It turned out that apparently, the issue was that when the function app is created, and sees an existing secret/key in its storage account, it will try decrypting it. If that fails, it will store a *.snapshot.json file for that secret, and create a new one. If the function app runtime sees 10 or more of those snapshot.json files, the function host will shut down (whatever that means -- at least it seems to have consequences for scaling). In this case we had been experimenting and recreating the function app several times.
The solution proposed by support was either to regularly delete these snapshot files, or migrate to using Azure Key Vault for secrets, which doesn't have this issue apparently. We've migrated to key vault, and that seems to have solved the issue.

Closing as using KV resolved the issue. If this is still a major problem let us know and we'll be happy to help investigate further.


Form input rendering issue after upgrading to version 4.5.0 and purging with PurgeCSS

I have just updated to Bootstrap 4.5.0. Everything works fine but when using it with PurgeCSS (v. 2.2.0) I got strange rendering issues:

Consider that nothing breaks on 4.4.1.

This is a tough one since we don't officially provide PurgeCSS support, and I don't believe our custom forms have changed much between v4.4.1 and v4.5.0. Anything stick out to you here? https://github.com/twbs/bootstrap/compare/v4.4.1...v4.5.0
Perhaps there's something to adjust on PurgeCSS's options?

Mmm.. It looks like the problem is PurgeCSS version > 1.3.0. Downgrading to 1.3.0 fix my problems. I have mistakenly blame Bootstrap 4.5.0. Sorry for that :)
For the record I'll post my postcss.config.js (pretty simple):
const purgecss = require('@fullhuman/postcss-purgecss')({
    content: [
        './**/*.html',
    ],
    keyframes: true,
    whitelistPatterns: [
        /popover/,
        /tooltip/,
        /modal/,
        /fade/,
        /show/,
        /hide/,
        /alert/,
    ],
});

const cssnano = require('cssnano')({
    preset: ['default', {
        discardComments: {
            removeAll: true
        },
    }],
});

module.exports = {
    plugins: [
        require('autoprefixer')(),
        ...process.env.NODE_ENV === 'production'
            ? [cssnano, purgecss]
            : []
    ]
};


[WIP] Mixed precition DFT

Done templating

Wave_functions
Beta_projectors
K_point
Hamiltonian
Q- and D- operators

The FP32 code should be conditional. I propose this change in all similar cases. From
   void update()
    {
        /* update k-points */
        for (int ikloc = 0; ikloc < spl_num_kpoints().local_size(); ikloc++) {
            int ik = spl_num_kpoints(ikloc);
            kpoints_[ik]->update();
#ifdef USE_FP32
            kpoints_float_[ik]->update();
#endif
        }
    }
    ```
    to
    ```
       void update()
    {
        /* update k-points */
        for (int ikloc = 0; ikloc < spl_num_kpoints().local_size(); ikloc++) {
            int ik = spl_num_kpoints(ikloc);
            kpoints_[ik]->update();
#ifdef USE_FP32
            if (ctx_.cfg().parameters().precision() == "fp32") {
                 kpoints_float_[ik]->update();
           }
#endif
        }
    }
    ```

    or even better
    ```
     if (ctx_.cfg().parameters().precision() == "mixed" || ctx_.cfg().parameters().precision() == "fp64")  {
        call_double_code();
     }
    if (ctx_.cfg().parameters().precision() == "mixed" || ctx_.cfg().parameters().precision() == "fp32")  {
       call_float_code();
   }

the .get() method of K_point_set needs more template magic. Now I have
error: cannot convert 'std::unique_ptr<sirius::K_point<float> >::pointer' {aka 'sirius::K_point<float>*'} to 'sirius::K_point<double>*' in return

In SDDK/hdf5_tree.hpp , we are missing the type_wrapper for std::complex but I can not find which H5T type would fit it in this context
template<>
struct hdf5_type_wrapper<float>
{
    static hid_t type_id()
    {
        return H5T_NATIVE_FLOAT;
    }
};

template<>
struct hdf5_type_wrapper<double>
{
    static hid_t type_id()
    {
        return H5T_NATIVE_DOUBLE;
    }
};

template<>
struct hdf5_type_wrapper<std::complex<double>>
{
    static hid_t type_id()
    {
        return H5T_NATIVE_LDOUBLE;
    }
};

The FP32 code should be conditional. I propose this change in all similar cases. From
   void update()
    {
        /* update k-points */
        for (int ikloc = 0; ikloc < spl_num_kpoints().local_size(); ikloc++) {
            int ik = spl_num_kpoints(ikloc);
            kpoints_[ik]->update();
#ifdef USE_FP32
            kpoints_float_[ik]->update();
#endif
        }
    }

to
       void update()
    {
        /* update k-points */
        for (int ikloc = 0; ikloc < spl_num_kpoints().local_size(); ikloc++) {
            int ik = spl_num_kpoints(ikloc);
            kpoints_[ik]->update();
#ifdef USE_FP32
            if (ctx_.cfg().parameters().precision() == "fp32") {
                 kpoints_float_[ik]->update();
           }
#endif
        }
    }

or even better
    if (ctx_.cfg().parameters().precision() == "mixed" || ctx_.cfg().parameters().precision() == "fp64")  {
       call_double_code();
    }
   if (ctx_.cfg().parameters().precision() == "mixed" || ctx_.cfg().parameters().precision() == "fp32")  {
      call_float_code();
  }

For this change, Should we consider to store a separate K_point_base class in K_point_set class, so that the weight, coordinates, etc. can be obtained even if the fp64 type K_point_class is not constructed in the K_point_set class?

For HDF5: it doesn't support complex types. Complex is packed as two consecutive doubles by the host code

There is now merge conflict and more deep issues with fp32/fp64 k-point energies. I'm going to move the band energies into k_point_set class and make them only fp64. When Davidson returns eigen-values, they will be copied to fp64 values.

@manhin321 I started to put some order in the code.

all non-performance critical variables, such as atom positions, G+k vector coordinates, k-point coordinates, weights, band energies and occupancies should remain in fp64
only performance critical objects should have fp32 support. For now this are the wave-functions and Hamiltonian

Stand-alone function for Davidson iterative solver should be a next step

@haampie
We crash clang
722    clang: error: unable to execute command: Segmentation fault (core d
            umped)
  >> 723    clang: error: clang frontend command failed due to signal (use -v t

bors try

@haampie is there a way to update clang on the CI/CD?

Yeah, let me just bump the base images to ubuntu 20.04, then we have clang 10

Why clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)

@haampie sirius<EMAIL_ADDRESS>it's Clang of spack which is 6.0

Yeah, it's the default system clang version on ubuntu 18.04. I've added https://github.com/electronic-structure/SIRIUS/commit/2b07af779d2f9669b193332631ff4d374178de8a that drops all mentions of compiler versions, but unfortunately spack doesn't autodetect a fortran compiler for clang by default, so rebuilding dependencies failed: https://gitlab.com/cscs-ci/electronic-structure/build-spack-images/-/jobs/1434876395#L1905 :(. Let me fix that now.

bors try

bors try

@manhin321 the Davidson diagonalization seems to be working for real systems. I tried test01 (SrVO3) and was able to converge it with accuracy parameters, adjusted for fp32

I have no objection so far.


Add tests for extract_requires on export types

Additional tests for https://github.com/facebook/jest/pull/4079

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e8ed43e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #4080   +/-   ##
=========================================
  Coverage          ?   60.43%
=========================================
  Files             ?      196
  Lines             ?     6773
  Branches          ?        6
=========================================
  Hits              ?     4093
  Misses            ?     2677
  Partials          ?        3

Continue to review full report at Codecov.

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

Thank you!


NBGL Nano: Check onActionCallback validity

Description
In nbgl_step actionCallback, onActionCallback was called without being checked, leading to crash if the callback is NULL. This commit adds the relevant checks.
(cherry picked from commit 263df08179b45216c63808e3653e50abd49bbc09)
Changes include

[x] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (API_LEVEL_22@598aafa). Learn more about missing BASE report.

Additional details and impacted files
@@               Coverage Diff               @@
##             API_LEVEL_22     #825   +/-   ##
===============================================
  Coverage                ?   35.76%
===============================================
  Files                   ?       13
  Lines                   ?     1591
  Branches                ?        0
===============================================
  Hits                    ?      569
  Misses                  ?     1022
  Partials                ?        0

Flag
Coverage Δ

unittests
35.76% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Remove OS::can_draw() remnants

Moving OS::can_draw() is part of #16863. Most of it was done as part of #37317 and the subsequent implementations of DisplayServer for the various platforms, but some remnants remain. This PR removes those remnants.

Thanks!


List resources that setup script creates

In Set up Azure resources, there is a script that creates several resources. Would be great to have a list of the resources that are created and what they are used for. That would provide a better understandign of what we're doing.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8c6611e1-23a3-48b0-d7e9-b7034bc3be9e
Version Independent ID: b05e4e17-70e7-59eb-3c75-d54efea6aa75
Content: Get started with Live Video Analytics on IoT Edge - Azure - Live Video Analytics on IoT Edge
Content Source: articles/media-services/live-video-analytics-edge/get-started-detect-motion-emit-events-quickstart.md
Service: media-services
Sub-service: lva-edge
GitHub Login: @Juliako
Microsoft Alias: juliako

@tiagonmas Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

This has now been added to the docs: https://docs.microsoft.com/en-us/azure/media-services/live-video-analytics-edge/get-started-detect-motion-emit-events-quickstart#set-up-azure-resources
See the list of resources under point 4.
We can close this issue.

This has now been added to the docs: https://docs.microsoft.com/en-us/azure/media-services/live-video-analytics-edge/get-started-detect-motion-emit-events-quickstart#set-up-azure-resources
See the list of resources under point 4.
We can close this issue.


Link throws 404

The link to get bcdboot examples does not work

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a288353c-cce4-82dc-1285-6857758b0166
Version Independent ID: dfb4d079-d860-d4fd-b93c-47bbcdc0fb85
Content: bcdboot
Content Source: WindowsServerDocs/administration/windows-commands/bcdboot.md
Product: windows-server
Technology: manage-windows-commands
GitHub Login: @coreyp-at-msft
Microsoft Alias: coreyp

Thank you for reporting the 404. I noticed that the link contains a typo and it works when corrected:

https://docs.microsoft.com/en-gb/previous-versions/windows/it-pro/windows-8.1-and-8/hh824874(v=win.10)

Then again, the page says: "We’re no longer updating this content regularly. Check the Microsoft Product Lifecycle for information about how this product, service, technology or API is supported."
There is also this other link with the exact same page title, but in a different section of the docs.microsoft.com library:

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di

I am going to open a PR to have the typo resolved, where I will also ask if it will be more useful to point to the Windows / Manufacture / Desktop manufacturing section instead, since that page does not display the warning about the topic not being regularly updated.
May I trouble you with taking a moment to compare those 2 pages and see if any useful information will be lost by choosing the newer and more updated page, in favor of the old Windows 8 page?

thank you for the update @illfated
makes sense to only have one copy or to redirect to a single source of truth

makes sense to only have one copy or to redirect to a single source of truth

Thank you for the reply. I would like to point out that my suggestion was to choose between the 2 pages, but I have also mentioned that as an additional note in my PR, as a question to the MS Server Docs team.


Two clicks sometimes needed to play ad ad on iOS 12 and Brightcove Player 5.28.1

IC reported the following issue on behalf of a customer when using Brightcove Player 5.281.:  iPhone, iOS 12, Safari: Autoplay not working. When I click on play, the same video player page opens but the ad/content doesn’t play. I have to click on play again to see 1 sec of the content followed by the ad. Skip button is missing just like on iOS 11.4.1
The missing Autoplay and missing SKIP button is expected behavior on that platform.

Internal JIRA ticket:  VIDLA-4448

duplicate of https://github.com/prebid/prebid-js-plugin-brightcove/issues/52;  closing


Nice job

Quality updates you legend!

Wondering, if it is an issue... :)

Hey how to update pod file with jukebox swift3 version. I converted session to swift 3 so many errors.
Using Jukebox (0.1.5)

Like how to access the swift 3 pod branch? like in this example http://stackoverflow.com/questions/39606935/how-to-update-pods-to-swift-3-0

Oh i figured it out just needed to update pods to iOS 10 duh! incase anyone else has a brain fart like me: Podspec below
`source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '10.0'
use_frameworks!
target "Momentum" do
pod 'HMSegmentedControl', '~> 1.5.2'
pod 'Jukebox'
pod 'MarqueeLabel/Swift'
pod 'CBZSplashView', '~> 1.0.0'
end`


Questions: Production builds & supporting component(name)

Thanks for this addon, looks great. I have a few questions if you don't mind.

How is this currently included in a project? If I add it to my project will this appear in the production vendor.js assets? If it does, can it be configured to only appear in development and testing?
I notice you don't currently support component(name), was there a reason for this and if not, would you be happy for me to submit a PR to support it?

re: components.
I think it would probably nice to take a selector and return an array of needing in addition to using an id or DOM. I often find myself doing something like devTools.view($('.ember-select')[3])