Stack Overflow in Main

Does anyone else face stackoverflow when we run Main?

Yup I have the same issue. I narrowed it down to something being wrong with my seed.get(), but I'm not sure what's going on with that. Also noticed it only happens on the 5th iteration, when n is 10^6

I change my attribute from supplier to int and problem solved, while it means I should not write any supplier at all

Wa but that's quite a major change... I think we'll be penalised quite heavily?

Same issue here, was due to supplier as well

Yep, had the same issue. It's because in your next method when you chain the supplier each time with something like reassigning to () -> this.supplier.get() the number of recursive calls keep increasing. I got around it by just changing the next method to unwrap the value inside and pass a new supplier, something like
int s = seed.get();   return new Rand(() -> s, ...)
Though depending how you wrote your methods maybe just changing next won't be enough, not too sure.

Yep, had the same issue. It's because in your next method when you chain the supplier each time with something like reassigning to () -> this.supplier.get() the number of recursive calls keep increasing. I got around it by just changing the next method to unwrap the value inside and pass a new supplier, something like
int s = seed.get(); return new Rand(() -> s, ...)
Though depending how you wrote your methods maybe just changing next won't be enough, not too sure.

thanks a lot bro !!! I will try to fix it

Yep, had the same issue. It's because in your next method when you chain the supplier each time with something like reassigning to () -> this.supplier.get() the number of recursive calls keep increasing. I got around it by just changing the next method to unwrap the value inside and pass a new supplier, something like
int s = seed.get(); return new Rand(() -> s, ...)
Though depending how you wrote your methods maybe just changing next won't be enough, not too sure.

I was facing the exact same issue here and I got stuck for quite a while; but this solution here of seed.get() did help to resolve it for me (and the difference was quite drastic in terms of reducing the overflow) so kudos to Huzaifa for this!
For anyone else who uses Supplier in their implementation and is facing the stack overflow issue, do try this solution and it should help.


[SWARM-1913] Removing the redundant assembly

retest this please

Run the openshift-it locally against Minishift, it passes


Ledger updates materialized view skips transactions

When an output is spent in the same milestone as it was created, we only at one entry for the spent output into the LedgerUpdatesCollection instead of both. This is because the $match statement uses $or on the indexes.
We should add this as a particular test case too, once we fix this.

Closed by #763


Setup tests for assumptions of flowStats.R functions.

The flowStats functions...

only accept data frames as input.
argument flowTS must have numeric column for streamflow called "flow".
argument flowTS must have numeric column with a 4-digit year called "year".
return a data frame with a new column called "flow_pk", "flow_med", or "flow_low".

added tests for flow_stats function


Adapting partial code(file name start with P #2) to the sonar cloud rule

https://github.com/apache/incubator-dolphinscheduler/pull/2213

Codecov Report

Merging #2260 into dev will decrease coverage by 1.52%.
The diff coverage is 28.43%.

@@             Coverage Diff              @@
##                dev    #2260      +/-   ##
============================================
- Coverage     31.95%   30.42%   -1.53%
- Complexity     1511     1663     +152
============================================
  Files           311      337      +26
  Lines         15402    17828    +2426
  Branches       1864     2237     +373
============================================
+ Hits           4922     5425     +503
- Misses         9968    11846    +1878
- Partials        512      557      +45

Impacted Files
Coverage Δ
Complexity Δ

...heduler/alert/manager/EnterpriseWeChatManager.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...duler/alert/template/impl/DefaultHTMLTemplate.java
77.55% <ø> (ø)
13.00 <0.00> (+1.00)

...inscheduler/alert/utils/EnterpriseWeChatUtils.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...apache/dolphinscheduler/alert/utils/FuncUtils.java
91.66% <ø> (ø)
5.00 <0.00> (ø)

...che/dolphinscheduler/api/ApiApplicationServer.java
33.33% <ø> (ø)
1.00 <0.00> (ø)

...scheduler/api/controller/AlertGroupController.java
3.57% <0.00%> (-0.52%)
2.00 <0.00> (ø)

...heduler/api/controller/DataAnalysisController.java
5.40% <0.00%> (ø)
2.00 <0.00> (ø)

...scheduler/api/controller/DataSourceController.java
2.19% <0.00%> (ø)
2.00 <0.00> (ø)

...inscheduler/api/controller/ExecutorController.java
6.25% <0.00%> (ø)
2.00 <0.00> (ø)

...uler/api/controller/ProcessInstanceController.java
2.43% <0.00%> (ø)
2.00 <0.00> (ø)

... and 139 more

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 8085e93...a1ece12. Read the comment docs.


Add video MIME types

https://github.com/Elyx0/react-native-document-picker/blob/e4c03667a87ffba54832563b11e00c6e5dd183e0/index.js#L62
In the list of available types there's no option for video. Seems in master there's support for that, is there any reason why it isn't for v3?

Available in master, clossing.


Add .eb as Python like filetype

The hpcugent/easybuild-framework is a python framework for installation of applications on HPC envirnments. The actual package build description are written in python but having .eb as extension.

:+1:

Please see the guidelines to add support for a new extension to Linguist. In particular, notice the requirement on in-the-wild usage.

In-the-wild usage

Thanks @jlec!
Any particular reason you excluded files containing the EditBox and easybuild keywords?
.eb files look more like data/config files. Perhaps we should add it as a type: data language in the Python group?

@pchaigno EditBox uses .eb for something else and easybuild is the main repo. I thought you would like to see everything outside the main repo.

EditBox uses .eb for something else and easybuild is the main repo. I thought you would like to see everything outside the main repo.

Okay, it's fine if we count the main repository :-)
There are only 66 EditBox .eb files so I don't think we'll have to add support for that.

What is the difference when adding it as type: data?

.eb files will be highlighted as Python but won't be counted in statistics.

.eb files will be highlighted as Python but won't be counted in statistics.

Makes sense, let me fix this later.

@pchaigno Any idea why the travis jobs fail?

Any idea why the travis jobs fail?

Yep, #3470 fixes it. The issue should disappear with your next push.

@pchaigno Sorry for the long delay. Was your idea to have a something like
Python:
  type: data
  extensions:
    - ".eb"
...

or
Easybuild:
  type: data
  group: Python
...

The second one. However, since we'd be adding it as a data language, I don't think the group is actually useful (if I remember correctly it's only useful for statistics).

The second one. However, since we'd be adding it as a data language, I don't think the group is actually useful (if I remember correctly it's only useful for statistics).

The second one. However, since we'd be adding it as a data language, I don't think the group is actually useful (if I remember correctly it's only useful for statistics).

The docs says, that group counts it into the parent rather it's own statistics.

Yes, but since we add it as a data language, it won't be counted in statistics anyway.

I was thinking to add it as programming. The Gentoo Ebuild is exactly the same type of file, just written in bash and added as programming into the Shell group. What do you think?

I'm thinking it's probably a mistake (for Gentoo Ebuild I mean) :p

@boegel Is there any TextMate compatible grammar for easybuild?

Is there any TextMate compatible grammar for easybuild?

You said the build descriptions are written in Python, right?
If so, you can just use Python's grammar for syntax highlighting. =)

@jlec No, not that I'm aware of...

@boegel I don't think you'll need one. ;-) It looks fine with the Python highlighter.

@Alhadis +1, it does look fine, and .eb files are indeed pure Python

@Alhadis Thanks for clarification
I think we are good to go now.

I don't understand why Travis is failing... @lildude @Alhadis Any idea?

@pchaigno cos...
  1) Failure:
TestLanguage#test_all_languages_have_grammars [/home/travis/build/github/linguist/test/test_language.rb:359]:
The following languages' scopes are not listed in grammars.yml. Please add grammars for all new languages.
If no grammar exists for a language, mark the language with `tm_scope: none` in lib/linguist/languages.yml.
Easybuild text.easybuild

... and sure enough, the new Easybuild section getting added in this PR doesn't have a tm_scope attribute nor is a new grammar being added specially for it.
@jlec to get the tests pushing, you'll need to add a tm_scope entry to the languages.yml. As this is essentially python, tm_scope: source.python should do the trick.

@lildude thanks for the hint.


WICKET-6587 make CheckBoxSelector extensible

Why not add a lookup to CheckBoxSelector instead:
public CheckBoxSelector(String id, CheckBox... boxes)
{
	super(id);

	connectedCheckBoxes = boxes;
}

/**
 * Override if you need want the boxes to be collected dynamically.
 */
protected List<Check> getCheckBoxes() {
    return Arrays.asList(connectedCheckBoxes);
}

@Override
protected CharSequence getFindCheckboxesFunction()
{
	return String.format("Wicket.CheckboxSelector.getCheckboxesFunction(%s)",
		buildMarkupIdJSArrayLiteral(getCheckBoxes()));
}

No need to hold references to all checkboxes, with the possibility of leakage when one is removed.

That is a possibility, yes, though in your example you do hold on to the connectedCheckBoxes. My main idea was to keep it simple, by providing addCheckBox() users can just add checkboxes in a loop, e.g. in ListView#populateItem.
Any checkboxes that are removed from the component hierarchy are cleared from connectedCheckBoxes by the attached behavior, so there shouldn't be a leak.
But I'm not heavily invested in this design, if you prefer a lookup method, I can do that.

Ah, I didn't notice your cleanup behavior. That's an improvement to the old solution already +1.
I just think that a dynamic lookup with an overriden #getCheckBoxes() would be more flexible. Why not do both: Add the cleanup all checkboxes passed in the constructor and let users override the lookup method if they want/need to.


vimPlugins.harpoon: 2023-05-28 -> 2023-10-10

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This one should fix it
There is an error of invalid 'event' that was fixed in the latest commit

This one should fix it There is an error of invalid 'event' that was fixed in the latest commit

Exactly, I notice that my last comment was a bit confusing, sorry.  What I wanted to say is that current nixpkgs harpoon is broken, and this PR fixes it, I'd like to get it merged ASAP.

it seems like this was fixed with #260408 a431eef36f3ec5dde105bfb874089454d235b89f

https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/vim/plugins/generated.nix#L4062
https://github.com/NixOS/nixpkgs/pull/260408/files#diff-54bef7a6c9c5497e77086f7935fbfe5c45e285f36f12f15b7044f42430e8e3ebR4062

Yeah. Seems like it. Closing this now. Thank you!


Design handshake between CN and BN to determine what Block to start streaming from.

Design a basic protocol for CN (or simulator) to initiate a stream to a BN that ensures the BN does not have any gaps in the block stream.
Initial Strawman
Block Node Connect

CN, on connect, sends block header, this contains block number.

If next block, no problem, start streaming.
If less than last block, respond with "DuplicateBlock"

Response includes last known block, so CN can perhaps do its own catch up or reconnect.
This REQUIRES CN to check and resend block header, or end the stream and restart.

If greater than next block, we missed block(s)

Respond with "Behind"

This includes last known block number.
CN will send from block after that block, or send "EndOfStream" and retry with exponential backoff.
CN will include earliest known block with end of stream, so we have an idea of the range to catch up.

This is advisory, and will almost certainly change before we finish "catching up".

If CN retries before we "catch up", we record the offered block number, and continue trying to "catch up" to that. Response is still "Behind" with last known block number.

This allows CN to jump in to "catch us up" directly if we're behind, but close enough.

We probably need a failure detection if the required target block doesn't get "closer" with each connection from CN.

If CN ends stream, need to catch up from other BN

Query BN "status" API, get last available block

If greater than or equal to block number CN sent

Ask for range, last-known-block+1 to last-available-block.
Hopefully catch up before next CN connection.

If less than block number CN sent

Either ask for stream last-known-block+1 to "infinite" and quit when caught up OR ask another BN, in case all needed blocks available elsewhere.

Each CN connect will send a block header, repeat above process until we get a matched block number or CN can finish catching us up.

Note, we can (re)enter connect any time we get a next block from CN that isn't what we expect. This simplifies logic for working out when to retry or reset a stream.

Error Handling

If CN detects an error at any time

Next BlockItem will be an EndStream item with an appropriate error code.
Block Node will drop any in-progress unproven block from that CN, and, if
no remaining active incoming streams, notify all subscribers with an
EndStream item specifying "source error".
Block Node will continue streaming from other incoming stream sources, if
any, or await a restarted stream if no other incoming stream sources.

If a BN detects an error at any time

BN will send an EndStream response to all incoming streams, with appropriate
status code.

CN, on receiving the end stream, will retry publishing the stream; and will
use exponential backoff if the BN failure continues.

If CN has multiple "downstream" BN options, a CN may connect to an alternate
BN for reliability and mark the failed BN as a backup.

BN will send EndStream to all subscribers with appropriate status code.
BN will either recover or await manual recovery.

This is an unlikely corner case but what's the behavior if the connect "next block" happens to be a missing block in the middle of the contiguous saved blocks? I imagine the BN needs to find missing gaps in the blocks it has stored. If the CN tries to send a block that happens to be less than the latest but is also missing, then it would respond with "DuplicateBlock" and the BN would send the latest block to start from. In a separate thread, it would backfill the missing block?

BN should not ever have an interstitial gap fillable from consensus node, if it does it should be requesting that block from another Block Node. Consensus Node should never send an old block when the Block Node has newer blocks, and the Block Node should refuse such streams with an appropriate error (likely "DuplicateBlock").
I'll add this specific case to the protocol above in the same duplicate block section.


Added AVC444 chroma support to shadow server.

Added full AVC444 modes to shadow server.
Primitive always send chroma mode, more bandwidth used but better image quality
Supports AVC444v1 and AVC444v2

@hardening Fixed your comments. Sorry for pushing the wrong commit before that.

LGTM


Error during installation: nix-data-0.0.2, no corresponding git dependency

Fresh Ubuntu WSL with nix installled with nix-installer
Log:
❯ nix profile install github:snowfallorg/snow --show-trace
error:
       … while calling the 'derivationStrict' builtin

         at /builtin/derivation.nix:9:12: (source not available)

       … while evaluating derivation 'snow-0.0.2'
         whose name attribute is located at /nix/store/f6jk9gi6i92ngcbkcz8z2d7gvkksciw1-source/pkgs/stdenv/generic/make-derivation.nix:286:7

       … while evaluating attribute 'cargoDeps' of derivation 'snow-0.0.2'

         at /nix/store/f6jk9gi6i92ngcbkcz8z2d7gvkksciw1-source/pkgs/build-support/rust/build-rust-package/default.nix:106:10:

          105| } // {
          106|   inherit buildAndTestSubdir cargoDeps;
             |          ^
          107|

       … while evaluating derivation 'cargo-vendor-dir'
         whose name attribute is located at /nix/store/f6jk9gi6i92ngcbkcz8z2d7gvkksciw1-source/pkgs/stdenv/generic/make-derivation.nix:286:7

       … while evaluating attribute 'buildCommand' of derivation 'cargo-vendor-dir'

         at /nix/store/f6jk9gi6i92ngcbkcz8z2d7gvkksciw1-source/pkgs/build-support/trivial-builders.nix:87:14:

           86|       enableParallelBuilding = true;
           87|       inherit buildCommand name;
             |              ^
           88|       passAsFile = [ "buildCommand" ]

       … from call site

         at /nix/store/f6jk9gi6i92ngcbkcz8z2d7gvkksciw1-source/pkgs/build-support/rust/import-cargo-lock.nix:71:22:

           70|   # individually.
           71|   gitShaOutputHash = lib.mapAttrs' (nameVer: hash:
             |                      ^
           72|     let

       … while calling 'mapAttrs''

         at /nix/store/f6jk9gi6i92ngcbkcz8z2d7gvkksciw1-source/lib/attrsets.nix:458:5:

          457|     # Attribute set to map over.
          458|     set:
             |     ^
          459|     listToAttrs (map (attr: f attr set.${attr}) (attrNames set));

       error: A hash was specified for nix-data-0.0.2, but there is no corresponding git dependency.

I think that exception appears because of migrating to snowfallorg.

Should be fixed in bb99e674ed04e4d1b27c2e60957579eef1cb5500


Help Required

Im trying to use MediatR across multiple class libraries as the following :
- Project 1 >> Raise INotification<EventTest>
- Project 2 >> Handle INotificationHandler<EventTest>
- Project 3 >> Handle INotificationHandler<EventTest>

if i create handler withing the same class library it works well, however Project 2 and 3 handlers are never triggered, i register all the above using Microsoft DI and Scrutor
any help plz ?

Most likely you are not scanning project 2 or 3 during start up.  Please share the code you are using to register your handlers.

@lilasquared
services.AddMediatR();
            services.Scan(scan => scan
             .FromAssembliesOf(typeof(IMediator), typeof(TestEvent), typeof(TestCommand)
             , typeof(TestEventHandler))
             .AddClasses()
             .AsImplementedInterfaces());

i call all the required assemblies here FromAssemblies

Doesn't the AddMediatR method accept assemblies to scan as parameters? Have you tried that?  If you are using the MicrosoftDI MediatR extension it should handle registering the handlers for you.

@lilasquared Yes it does tried both cases actually, as the following:
services.AddMediatR(typeof(IMediator), typeof(TestEvent), typeof(TestCommand), typeof(TestEventHandler));
services.AddScoped<IRequestHandler<TestCommand>, TestCommandHandler>();

all projects are referenced to this one and this is being called on Startup

It's going to be hard to help out with this without more info about the project.  Are you able to create a small sample project that replicates the behavior that you can share?

@lilasquared here is a sample project MediatRTest

I think this is in the wrong repository, if you're using the DI extension.


Removed xccheckout and xcscmblueprint from Swift/Objc/Xcode

I believe it should not be encouraged to ignore .xccheckout and .xcscmblueprint files in Xcode project/workspaces. They are a shared resource, which should be committed into the git repository, just like the project file and schemes. It does makes sense to ignore user-specific files, like the state of the user interface, but this is not the case.
Ignoring these files can cause issues when multiple people are using CI tools like Xcode Server across one team. That's why I believe this should be removed from the standard .gitignore for these languages/IDE.

@czechboy0 apologies for not getting back to this sooner. Are you interested in resolving the merge conflict here, or should I close this out?
Also cc @Coeur who proposed this rule - I'd love to see if you agree with the above comments.

@shiftkey, I did not propose the rule, as far as I can remember. I've just harmonized the three .gitignore files.
But there is a major issue with those two Xcode files, so allow me to quote myself:
http://stackoverflow.com/questions/31584297/xcode-7-ignore-xcscmblueprint-in-repository/31644396#comment57794663_32707458

You should always .gitignore .xccheckout. From stackoverflow.com/questions/18340453/…: "It looks like xccheckout contains keys and names which are specific to each developer's machine... As soon as I run xcode it changes some keys in the file [...]. If this file is supposed to be shared, then Apple have done a pretty poor job." – Cœur Jan 27 at 10:38

Those files will be automatically modified by whoever opens Xcode last, resulting in being added to every commit if you don't ignore them. On the other hand, I've never heard of issues regarding ignoring those files, so I believe we should keep ignoring them.

@Coeur apologies, I should have seen that it was a merge commit.
It looks like this goes back further, all the way to #703 which was from 2013. As that original PR indicated, and @Coeur says above, this file has sensitive information in it. I'd love to see if there's any official guidance about whether these files should be version-controlled at all.

That's not the case, there's no confidential information in those files, those keys are generated based on the project, so all developers should get the same ones for the same project. That's why it's in shared files in the project.
I haven't seen it being modified, can you please provide any up to date evidence?
Again, I'm for removing these files from gitignore for the reasons I've outlined above.

For what it is worth... ignoring the .xccheckout file does cause problems (as I've found several times using the .gitignore master branch).  I was actually going to go create a merge request before I saw this one sitting here.
If you have a workspace that pulls in projects from multiple repositories (can even mix/match git and svn), Xcode has the ability to pull in those other dependencies.  But only if your shared .xccheckout file is present.  If it isn't, then you have to manually go check each one out yourself (which is a pain because you have to make sure you get the right sources and put them in the exact same folder paths).  So, it is a lot better if that .xccheckout file version controlled.
Details for how this works can be found in WWDC 2013 Session #414 .  The relevant topic is "Advanced checkout" and starts at about 14:50 in.

Alright, barring any further objections I'm happy to take this in.
@czechboy0 apologies for this taking so long - it seems like there's a merge conflict now :broken_heart:

@shiftkey No worries, I'm glad we ended up agreeing. Okay let me resolve it.

@shiftkey Done

@czechboy0 thanks!

Maybe it does help for @jolson474 for his edge case of multiple repositories, but a load of people on StackOverflow were complaining, as I linked above 16 days ago: "It looks like xccheckout contains keys and names which are specific to each developer's machine." You will likely see PR in the future from people wishing to revert this change for sanity.

@Coeur I've heard people spreading that, but can you point me at any evidence of that? Those are not keys, but hashes as far as I understand, and they are designed to be dependent on the server/project, not the developer machines (from observation). If you have any evidence on the contrary, I'd love to see it.
Because again, these files are in the shared data section of Xcode project, hinting that they should be checked in.

An interesting answer, http://stackoverflow.com/a/20633780/1033581:

if you are using SVN, you DO NOT want to ignore .xccheckout
if you are using GITHUB, you DO want to ignore .xccheckout

Hmm, the answer you linked says that YES you should check it in. Only don't check it in if every member of your team has a separate fork, thus a different remote.

Maybe this can reproduce an instable .xccheckout:

computer A is using HTTPS for the git repository
computer B is using SSH for the git repository

Yes it could, but Xcode doesn't change the files once they're checked in AFAIK. But the checkout files are used mainly for Xcode Server anyway and there the remote is just a field, it has unique identifiers to tell remotes apart.
Anyway, I think it's important we keep it the way Xcode was designed, so I'm glad this is gone. But, to top it all off, I think the checkout files are getting phased out anyway.

A simple way of proving what @Coeur says is as follows:

developer A clones a repo, and gives it a custom name (in my case I changed the destination directory from "MyProject" to "my_project" on my local machine, and proceed to cloning it to that directory.
developer B also clones it and does the same thing, except he names his local directory "some_other_name_project".
they both work on their stuff, and then the .xcscmblueprint is always changed when they pull from each other's code or from a branch pushed to origin by the other developer.

at least, this is the case for my own experience, and if there's dev-specific info on that file, it would be best to ignore it. as for the specific case of .xccheckout, I can't offer evidence on the subject right now


Craft 3 Support

Hi,
Are you looking to add Craft 3 support soon?

It's started, just need to get around to finishing it.


Firebase.Functions.FunctionsException: UNAUTHENTICATED even after successful firebase auth and i am holding auth reference to Firebaseauth Defaultinstance

[READ] For Firebase Unity SDK issues, please report to Firebase Unity open-source
Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.
[REQUIRED] Please fill in the following fields:

Unity editor version: 2021.3.9f
Firebase Unity SDK version: 9.6.0
Source you installed the SDK: FirebaseFunctions(.unitypackage or Unity Package Manager)
Problematic Firebase Component: FirebaseFunctions
Other Firebase Components in use: FirebaseFunctions ,Auth
Additional SDKs you are using:
Platform you are using the Unity editor on: Windows
Platform you are targeting:Android
Scripting Runtime:  IL2CPP

[REQUIRED] Please describe the issue here:
Firebase.Functions.FunctionsException: UNAUTHENTICATED
at Firebase.Functions.HttpsCallableReference.b__9_0 (System.Threading.Tasks.Task`1[TResult] task) [0x00000] in <00000000000000000000000000000000>:0
I m trying to user firebase functions with unity. I have added firebase auth that is working perfectly. After auth I am calling my firebase function using this code below
void FirebaseFucntionTest()
{
    var data = new Dictionary<string, object>();
    Debug.Log("Calling");
    FirebaseFunctions functions = FirebaseFunctions.DefaultInstance;
    Debug.Log(FirebaseAuth.DefaultInstance.CurrentUser.DisplayName);

    var function = functions.GetHttpsCallable("testunity");
   function.CallAsync(data).ContinueWith((task) =>
   {
       if (task.IsFaulted)
       {
           foreach (var inner in task.Exception.InnerExceptions)
           {
               if (inner is FunctionsException)
               {
                   var e = (FunctionsException)inner;
                   var code = e.ErrorCode;
                   var message = e.ToString();
                   Debug.Log(message);
                   Debug.Log(code);
               }
           }
       }
       else
       if (task.IsCompleted)
       {
           Debug.Log((string)task.Result.Data);
       }
   });

}
I am holding a reference to auth using:  auth = FirebaseAuth.DefaultInstance;  and after this I am calling my function that runs the cloud  function, as you can see in the debug statement at the start of the method I getting the currentusername successfully, but after code moves to cloud function call it is giving me exception of unauthenticated:

Hi @bazinga007,
Could you post your output log? Does this problem also occur with the quickstart example?
Also the exception output varies about from our quickstart which has:
var task = func.CallAsync(data).ContinueWithOnMainThread((callTask) => {
        if (callTask.IsFaulted) {
          // The function unexpectedly failed.
          DebugLog("FAILED!");
          DebugLog(String.Format("  Error: {0}", callTask.Exception));
          return;
        }
       ...
}

I only bring this up becuase we'd love the output of whichever is more informative. It would be nice to have data from all of the Exceptions, not just the inner ones.
Thanks!


docs: updated the right path for integrations page

Description: Updated the right path for Integrations Page to resolve 404 Not Found issue on the website,

Issue: #14998 ,
Dependencies: No dependencies required,
Twitter handle: @vardhaman722

I think this was already handled!


Only run the UserIdleProcessor while pipeline is running

Please describe the changes in your PR. If it is addressing an issue, please reference that as well.
In response to issue https://github.com/pipecat-ai/pipecat/issues/741

@aconchillo it might be worth looking at https://github.com/pipecat-ai/pipecat/issues/741 more closely. Perhaps this PR isn't needed.

@aconchillo this is ready for review.

LGTM!


Build doesn't show any violation.

Hi, could you please help me find out why I don't get any violation using this plugin?
Here is my configuration:
<plugin>
                <groupId>org.jacoco</groupId>
                <artifactId>jacoco-maven-plugin</artifactId>
                <version>0.8.6</version>
</plugin>
<plugin>
                <groupId>com.github.surpsg</groupId>
                <artifactId>diff-coverage-maven-plugin</artifactId>
                <version>0.3.3</version>
                <configuration>
                    <diffSource>
                        <git>refs/remotes/origin/develop</git>
                    </diffSource>
                    <violations>
                        <failOnViolation>true</failOnViolation>
                        <minCoverage>0.9</minCoverage>
                    </violations>
                </configuration>
                <executions>
                    <execution>
                        <goals>
                            <goal>diffCoverage</goal>
                        </goals>
                    </execution>
                </executions>
</plugin>

Then I created a new method in one of my service classes, ran mvn clean test diff-coverage:diffCoverage and got this message:
[WARNING] Fail on violations: true. Found violations: 0.
The whole output :
[INFO] --- diff-coverage:0.3.3:diffCoverage (default-cli) @ TE_CORPBANK.portfolio-reporting-api ---
[INFO] diff content saved to 'C:\Projects\TE_CORPBANK.portfolio-reporting-api\target\site\diff.patch'
[WARNING] Fail on violations: true. Found violations: 0.

The build completes successfully. I tried to specify the git branch like "develop" and "origin/develop", specified other configurations rather than minCoverage, modifying the 0.9 ratio also, nothing changes.
Thank you in advance.

Hi, Irina,
Please, check the content of the generated file:
[INFO] diff content saved to 'C:\Projects\TE_CORPBANK.portfolio-reporting-api\target\site\diff.patch'

I think the diff file is empty. But it would nice to confirm my assumption.

If the assumption is true then try to commit your code and recheck

Hi, yes the file is empty. Should I push the changes in pom.xml to the remote branch?

Hi @IrinaStaicova
Suppose we hame two branches: main and feature. The feature is created from main.
And suppose we have the plugin is configured in the next way:
<configuration>
    <diffSource>
        <git>refs/remotes/origin/main</git>
    </diffSource>
</configuration>

Then the plugin will generate a diff like:
git diff refs/remotes/origin/main

The changes should be committed, but it's not required to be pushed.
--
Also, you can configure the plugin in the next way:
<properties>
      <diff.source>refs/remotes/origin/main</diff.source> <!-- default -->
</properties>

<build>
        <plugins>
            <plugin>
                <groupId>com.github.surpsg</groupId>
                <artifactId>diff-coverage-maven-plugin</artifactId>
                <configuration>
                    <diffSource>
                        <git>${diff.source}</git>
                    </diffSource>
                </configuration>
            </plugin>
        </plugins>
</build>

then run:
./mvnw clean install -Ddiff.source="HEAD"

So, in this case we will get diff between your staged changes and the current branch head.
--
Have you enabled build failure on violation?
                <configuration>
                    <violations>
                        <failOnViolation>true</failOnViolation>
                        <minCoverage>0.9</minCoverage>
                    </violations>
                </configuration>

example
--
Could you please provide your configuration of the plugin?

Hi,
Thank you for support, I confirm that the plugin works in this way.
Here is my full configuration:
<plugin>
                <groupId>com.github.surpsg</groupId>
                <artifactId>diff-coverage-maven-plugin</artifactId>
                <version>0.3.3</version>
                <configuration>
                    <diffSource>
                        <git>refs/remotes/origin/master</git>
                    </diffSource>
                    <violations>
                        <failOnViolation>true</failOnViolation>
                        <minCoverage>1.0</minCoverage>
                    </violations>
                    <dataFileIncludes>../target/jacoco.exec</dataFileIncludes>
                </configuration>
                <executions>
                    <execution>
                        <phase>verify</phase>
                        <goals>
                            <goal>diffCoverage</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>


Problem with compile on Raspberry Pi on Ubuntu 22.10

Describe the bug
Compiling of OTBR almost done, but failed in compiling web server code
To Reproduce
main branch commit fbbb62fafce55cdd8c0fa2352b2e27d30c2d2192
Expected behavior
Success compilation
Console/log output
[447/451] Building CXX object src/web/CMakeFiles/otbr-web.dir/web-service/web_server.cpp.o
FAILED: src/web/CMakeFiles/otbr-web.dir/web-service/web_server.cpp.o
/usr/bin/c++ -DMBEDTLS_CONFIG_FILE="/home/pi/ot-br-posix/third_party/openthread/mbedtls-config.h" -DOTBR_ENABLE_BACKBONE_ROUTER=1 -DOTBR_ENABLE_BORDER_AGENT=1 -DOTBR_ENABLE_BORDER_ROUTING=1 -DOTBR_ENABLE_BORDER_ROUTING_COUNTERS=1 -DOTBR_ENABLE_DBUS_SERVER=1 -DOTBR_ENABLE_DNSSD_DISCOVERY_PROXY=1 -DOTBR_ENABLE_FEATURE_FLAGS=1 -DOTBR_ENABLE_NAT64=1 -DOTBR_ENABLE_NOTIFY_UPSTART=1 -DOTBR_ENABLE_REST_SERVER=1 -DOTBR_ENABLE_SRP_ADVERTISING_PROXY=1 -DOTBR_ENABLE_SRP_SERVER_AUTO_ENABLE_MODE=1 -DOTBR_ENABLE_VENDOR_INFRA_LINK_SELECT=0 -DOTBR_MESHCOP_SERVICE_INSTANCE_NAME=""OpenThread BorderRouter"" -DOTBR_PACKAGE_NAME="OpenThread_BorderRouter" -DOTBR_PACKAGE_VERSION="0.3.0-fbbb62fafc" -DOTBR_PRODUCT_NAME="BorderRouter" -DOTBR_SYSLOG_FACILITY_ID=LOG_USER -DOTBR_VENDOR_NAME="OpenThread" -DWEB_FILE_PATH="/usr/share/otbr-web/frontend" -I/usr/include/jsoncpp -I/home/pi/ot-br-posix/third_party/Simple-web-server/repo -I/home/pi/ot-br-posix/include -I/home/pi/ot-br-posix/src -I/home/pi/ot-br-posix/build/otbr/third_party/openthread/repo/etc/cmake -I/home/pi/ot-br-posix/third_party/openthread/repo/etc/cmake -I/home/pi/ot-br-posix/third_party/openthread/repo/include -I/home/pi/ot-br-posix/third_party/openthread/repo/src/posix/platform/include -I/home/pi/ot-br-posix/third_party/openthread/repo/src -I/home/pi/ot-br-posix/third_party/openthread/repo/third_party/mbedtls/repo/include -Wall -Wextra -Werror -Wfatal-errors -Wuninitialized -Wno-missing-braces -Wno-deprecated-declarations -Wno-unused-lambda-capture -std=c++11 -MD -MT src/web/CMakeFiles/otbr-web.dir/web-service/web_server.cpp.o -MF src/web/CMakeFiles/otbr-web.dir/web-service/web_server.cpp.o.d -o src/web/CMakeFiles/otbr-web.dir/web-service/web_server.cpp.o -c /home/pi/ot-br-posix/src/web/web-service/web_server.cpp
In file included from /home/pi/ot-br-posix/src/web/web-service/web_server.cpp:42:
/home/pi/ot-br-posix/third_party/Simple-web-server/repo/server_http.hpp: In instantiation of ‘SimpleWeb::ServerBase<socket_type>::Request::Request(const socket_type&) [with socket_type = boost::asio::basic_stream_socketboost::asio::ip::tcp]’:
/home/pi/ot-br-posix/third_party/Simple-web-server/repo/server_http.hpp:460:74:   required from here
/home/pi/ot-br-posix/third_party/Simple-web-server/repo/server_http.hpp:117:57: error: member ‘SimpleWeb::ServerBase<boost::asio::basic_stream_socketboost::asio::ip::tcp >::Request::streambuf’ is used uninitialized [-Werror=uninitialized]
117 |             Request(const socket_type &socket): content(streambuf) {
|                                                         ^~~~~~~~~
compilation terminated due to -Wfatal-errors.
cc1plus: all warnings being treated as errors
[448/451] Building CXX object src/dbus/server/CMakeFiles/otbr-dbus-server.dir/dbus_thread_object.cpp.o
ninja: build stopped: subcommand failed.
Additional context
gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)

See #1664

This should be fixed with #1667.

Resolved by #1667.


Properties Window Starts Minimized

Description
If I open the properties of ANY file the properties window starts off minimized and you have to click on taskbar to select and open.
Steps To Reproduce

Right-Click any file (I was working on .pdf files) select the wrench
nothing seems to happen - check the taskbar the properties window is there, minimized.
click on properties window to open.
This only started happening since the last (Windows Store) update.

Requirements
Fix Properties window starts off hidden/minimized.
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.4529
Log File
debug.log

Thanks for the feedback, We're tracking this in #13697. You can check there or click subscribe in the right sidebar for updates.


Remove cleanup artifacts script

This was a hidden point of maintenance (long ignored) and is actually somewhat harmful: when we prod sign binaries, we want to prod sign the unsigned binaries, not the test signed binaries. Therefore the original versions of these files should be kept intact.

Just curious what would happen if we prod sign an already test signed binary?

Just curious what would happen if we prod sign an already test signed binary?

That's what had happened in the past: the files were all double signed: one sig from the prod cert, and one sig from the test cert. The latter is effectively ignored, but kind of ugly.

Just curious what would happen if we prod sign an already test signed binary?

That's what had happened in the past: the files were all double signed: one sig from the prod cert, and one sig from the test cert. The latter is effectively ignored, but kind of ugly.

Hah, I didn't know a file can be double signed.


Question about pycolmap.incremental_mapping

Hello, I would like to ask a question about pycolmap.incremental_mapping. Can I fix the known image pose for colmap 3D reconstruction in pycolmap.incremental_mapping. In the process, the map points are just triangulated and optimized, at the meantime the pose of query images and fixed.

To optimize only existing 3D points, you can use pycolmap.bundle_adjustment as
pycolmap.bundle_adjustment(reconstruction, {'refine_extrinsics': False})

If you want to also refine a subset of poses, this is currently only possible by building your own BA problem with pyceres (example here) but we will soon have a much simpler way of doing so by binding the BundleAdjuster (cc @B1ueber2y)

Sorry, maybe I misspoke what I mean.  I want to use the Hloc pipeline,  such as the pipeline of "disk+lightglue+netvlad". and then I use Pycolmap to perform 3D reconstruction to generate sparse 3D models. The coordinate system of the image and map points in the model must be consistent with the original image coordinate system. How can I do this? Thank you.
I guess if I can perform as:
options = {"num_threads": min(multiprocessing.cpu_count(), 16),  "fix_existing_images": true, **options}
pycolmap.incremental_mapping(database_path, image_dir, models_path, options=options)

Is this plan feasible? Looking forward to your reply!

If you want to retain the camera poses and intrinsic parameters and simply need a sparse 3D model, you can perform triangulation:
pycolmap.triangulate_points(reconstruction, database_path, image_path, output_path, ...)

You can optionally later refine the parameters with pycolmap.bundle_adjustment.


Is it safe to replace _apply_partitionwise with map_partitions?

I'm not understanding why this code is here:
https://github.com/dask/dask-ml/blob/90fbe69771926b7e43a5bef99d81e268dad63e7e/dask_ml/wrappers.py#L504-L522
My guess is that it resolves some deficiency in map_partitions.  Is that still true?

From
https://github.com/dask/dask-ml/pull/132#discussion_r166096031

Is this something that we would want to push upstream into Dask?

We were blocked by map_partitions returning an array. We should be able to use it now.
It's funny how consistent humans can be :)

I think this was resolved in #400 and this issue can now be closed

Yes, thanks.


[Fixes #225] Password strength indicator

Use IdentityOptions to add a Password strength indicator on the setup screen.

@agriffard Waiting for you to review before merging


Adding LVS update to allow multiple file extension for netlist.

Adding LVS update to allow multiple file extension for netlist.

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

@FaragElsayed2 We need to add this to the LVS moved to the pv repo.


Section A.3.1.1. FIA_X509_EXT.1/ITT - Use of bullet/italics/numbered bullets

Under “Application Note 39”:  The 3 paragraphs below “The validation of X.509v3 leaf certificates comprises several steps:” are being treated as paragraphs and not listed items.
For better readability, should be bulletized, numberized or listed such as:
a)
b)
c)

This issue is a problem with the PDF rendering only. The ASCIIDOC version on Github is marked-up to show these items as an ordered list (a, b, c).


UI edits to schema selection and edits saving in Wikibase extension

This has been mentioned in previous PRs and issues, but starting a new issue to track all the final adjustments needed in more detail. This is a request to improve the following UI features:

I think this text is not needed - it's too clunky in the layout; it's information experienced users know and don't need to see at all times; it's also something new users should learn from tutorials / documentation; new users (as shown during user testing) tend not to read small text anyway, and just click around until they find the solution to go forth, or just go and watch a tutorial;
Save schema should be called "Save schema progress".
Save schema progress / Discard changes should move below the main schema editing area (see wireframes).
This should probably just say "Select..."
"Save new" is potentially confusing if users just want to save and override an existing schema. Another idea was to keep the button to say only "Save", but I think this will make it potentially confusing next to the dropdown in case users decide they are just saving their selection choice. I propose we call this button "Save schema edits" and we move it to the right of the screen (see wireframes).

Proposed solution
Proposed redesign:

For more context see complete design wireframes accessible via this link: https://docs.google.com/document/d/1uWkrid1UJwM3FCak_fI4VUY2EUabVUUFk9z6OeWtzKs/edit?usp=sharing
Alternatives considered
Several previous iterations can be seen in the wireframe versions in the link above. The naming of the "Save" button and the schema vs schema template was discussed in more detail in previous PRs, e.g. https://github.com/OpenRefine/OpenRefine/pull/5303
Additional context
The need to adjust this was discussed during the final round of user testing for the Commons extension project carried out Sept / Oct 2022.

This issue is already a design proposal on its own, so I do not think there is much left to design @OloladeOdus. Perhaps it is worth picking another issue where the desired behaviour and appearance is not clear yet?


Tests for limitation of address-spaces (by credits)

smaller tasks created:
https://github.com/EnMasseProject/enmasse/issues/918
https://github.com/EnMasseProject/enmasse/issues/919
https://github.com/EnMasseProject/enmasse/issues/920
https://github.com/EnMasseProject/enmasse/issues/921


feature: inside sbt, allow ctrl-C to interrupt tests without killing the JVM

according to https://github.com/sbt/sbt/issues/228, sbt supports this, though it's not clear if it's received much use/testing
this is the number one reason I end up having to restart sbt (killing my nice warm JITted compiler)

+1

+1

+1

+1

+1

+1

+1

+1000

:+1:

:+1:

+1

+1

+1

+1

+1

+1
It looks like with following config I could cancel test without exits the JVM per latest sbt:
cancelable in Global := true


How to list out static contents hosted in a subdomain in the goaccess report?

I have this domain nucuta.com and my images are hosted in cdn.nucuta.com. I enabled access_log directory  in both files in nginx. so, even though in the access.log file it shows the requests to images are logged, it doesn't show in the goaccess report in "STATIC REQUESTS" section. so how I am gonna list the requests to static contents hosted this cdn.nucuta.com in goaccess report? thanks.!

Can you please post a few lines from your access.log that contain static requests and not showing in goaccess? Thanks.

Strangely these records don't show, but static contents served from the main domain appear in the report, and they are exactly like these except the directory starts with wp-content.
then again I am not sure it's a problem with these records or because I enabled logging of that subdomain today. yeah I forgot to enable logging of cdn.nucuta.coma subdomain, but I enabled it today and sent the requests to these static files and then generated the report but they don't appear still. I dunno why. this problem is quite strange, because I don't see any difference between the following records, and the records of wp-content folder.
[x.x.x.x - - [24/Sep/2017:23:37:14 +0530] "GET /2017/08/google-drive-logo-new-551x300.png HTTP/2.0" 200 21821 "-" "Mozilla/5.0 (Win
dows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36"
x.x.x.x - - [24/Sep/2017:23:37:54 +0530] "GET /2017/05/watch-397227_1920-e1495719751424-640x480.jpg HTTP/2.0" 404 647 "-" "Mozilla
/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36"
x.x.x.x - - [24/Sep/2017:23:37:59 +0530] "GET /2017/06/HomeKitLogo-e1498174778783-272x182.png HTTP/2.0" 200 23335 "-" "Mozilla/5.0
(Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36"](url)
When the file is in wp-content folder.
x.x.x.x  - - [24/Sep/2017:23:44:01 +0530] "GET /wp-content/uploads/2017/07/Cucoin600px.png HTTP/2.0" 200 253000 "-" "Mozilla/5.0 (W
indows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36"

GoAccess shows the top 365 records or 50 in the real-time report, so it's possible these static files don't account to make it to the top list. One thing you could do is to check how many instances of one of these static files there are, e.g., grep '/2017/06/HomeKitLogo-e1498174778783-272x182.png' cnd.log | wc -land see if there are enough hits to make it to the top. You can also extract these hits and check if goaccess is putting them in the right panel.

It says when typing the exact command.
:~# grep '/2017/06/HomeKitLogo-e1498174778783-272x182.png' cnd.log | wc -l
grep: cnd.log: No such file or directory
0

cnd.log was the example filename, in your case, please use your access log that contains all the records from the cdn  domain.

Oh yeah xD right. It returned this one.
grep '/2017/08/google-drive-logo-new-551x300.png' /var/log/nginx/access.log | wc -l
7

I guess that explains the culprit then.  Thanks.!


Make sure that mriqc can analyze multiband data on ls5

Memory requirements of multiband data combined with specific submit restriction of ls5 can be problematic and require new execution modes.

I will assign this to @wtriplett if he is happy with it :)

I'm happy with it! :)

So right off the bat the anatomical workflow is too much for a lonestar5 node when it starts fast, unless the number of threads are restricted in multiproc. Seems like 15 threads is about the max it can take with each fast at just under 4 GB, but even that's making me a little nervous. Cheaper than iTunes, though!

The functional workflow only was run on a single LS5 node with 24 CPUs (48 hyperthreaded). No --nthreads option was specified, allowing MultiProc to use all available CPU including the hyperthreaded ones.
Start time: 160319-22:55:47
End time: 160320-03:07:43
Memory usage was moderate to high during the times I checked. The workflow failed during the execution of the measures node with the below two crash files. I re-ran the workflow and watched the CPU usage during various stages of execution, and noticed that the mriqc processes was consuming between 1.4 and 4.4 GB each, possibly all trying to run measures at the same time. The crash files from the unsupervised mriqc run are below. Let me know if I can provide additional info -- I still have the work folder on TACC in my $SCRATCH.
File: crash-20160320-030612-wtriplet-measures.a116.pklz
Node: fMRIQC.measures.a116
Working directory: /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/_data_sub-01.ses-083.task-rest_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-083..func..sub-01_ses-083_task-rest_run-001_bold.nii.gz/measures

Node inputs:

direction = all
ignore_exception = False
in_epi = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/_data_sub-01.ses-083.task-rest_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-083..func..sub-01_ses-083_task-rest_run-001_bold.nii.gz/mean/sub-01_ses-083_task-rest_run-001_bold_calc_resample_volreg_tstat.nii.gz
in_hmc = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/fMRI_HMC/_data_sub-01.ses-083.task-rest_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-083..func..sub-01_ses-083_task-rest_run-001_bold.nii.gz/motion_correct_A/sub-01_ses-083_task-rest_run-001_bold_calc_resample_volreg.nii.gz
in_mask = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/fMRIBrainMask/_data_sub-01.ses-083.task-rest_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-083..func..sub-01_ses-083_task-rest_run-001_bold.nii.gz/afni_msk/sub-01_ses-083_task-rest_run-001_bold_calc_resample_volreg_mask.nii.gz
in_tsnr = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/_data_sub-01.ses-083.task-rest_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-083..func..sub-01_ses-083_task-rest_run-001_bold.nii.gz/compute_tsnr/tsnr.nii.gz

Traceback:
Traceback (most recent call last):
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/plugins/multiproc.py", line 19, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/engine/nodes.py", line 392, in run
    self._run_interface()
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/engine/nodes.py", line 502, in _run_interface
    self._result = self._run_command(execute)
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/engine/nodes.py", line 628, in _run_command
    result = self._interface.run()
  File "/home1/03872/wtriplet/software/nipype/nipype/interfaces/base.py", line 1032, in run
    runtime = self._run_wrapper(runtime)
  File "/home1/03872/wtriplet/software/nipype/nipype/interfaces/base.py", line 989, in _run_wrapper
    runtime = self._run_interface(runtime)
  File "/home1/03872/wtriplet/software/mriqc/mriqc/interfaces/qc.py", line 226, in _run_interface
    self._results['dvars'] = dvars(hmcdata, mskdata).mean(axis=0)[0]
  File "/home1/03872/wtriplet/software/mriqc/mriqc/qc/functional.py", line 159, in dvars
    dvars_nstd = func_diff.std(axis=0)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/numpy/core/_methods.py", line 124, in _std
    keepdims=keepdims)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/numpy/core/_methods.py", line 101, in _var
    x = asanyarray(arr - arrmean)
MemoryError:
Interface FunctionalQC failed to run.

and
File: crash-20160320-030613-wtriplet-measures.a135.pklz
Node: fMRIQC.measures.a135
Working directory: /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/_data_sub-01.ses-095.task-objects_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-095..func..sub-01_ses-095_task-objects_run-001_bold.nii.gz/measures

Node inputs:

direction = all
ignore_exception = False
in_epi = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/_data_sub-01.ses-095.task-objects_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-095..func..sub-01_ses-095_task-objects_run-001_bold.nii.gz/mean/sub-01_ses-095_task-objects_run-001_bold_calc_resample_volreg_tstat.nii.gz
in_hmc = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/fMRI_HMC/_data_sub-01.ses-095.task-objects_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-095..func..sub-01_ses-095_task-objects_run-001_bold.nii.gz/motion_correct_A/sub-01_ses-095_task-objects_run-001_bold_calc_resample_volreg.nii.gz
in_mask = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/fMRIBrainMask/_data_sub-01.ses-095.task-objects_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-095..func..sub-01_ses-095_task-objects_run-001_bold.nii.gz/afni_msk/sub-01_ses-095_task-objects_run-001_bold_calc_resample_volreg_mask.nii.gz
in_tsnr = /scratch/03872/wtriplet/ds031.qcpwrk/fMRIQC/_data_sub-01.ses-095.task-objects_run-001...home1..03872..wtriplet..openfmri..HISTORICAL_DATA_TO_BIDS..999_AllUncompressed..ds000031..ds031..sub-01..ses-095..func..sub-01_ses-095_task-objects_run-001_bold.nii.gz/compute_tsnr/tsnr.nii.gz

Traceback:
Traceback (most recent call last):
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/plugins/multiproc.py", line 19, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/engine/nodes.py", line 392, in run
    self._run_interface()
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/engine/nodes.py", line 502, in _run_interface
    self._result = self._run_command(execute)
  File "/home1/03872/wtriplet/software/nipype/nipype/pipeline/engine/nodes.py", line 628, in _run_command
    result = self._interface.run()
  File "/home1/03872/wtriplet/software/nipype/nipype/interfaces/base.py", line 1032, in run
    runtime = self._run_wrapper(runtime)
  File "/home1/03872/wtriplet/software/nipype/nipype/interfaces/base.py", line 989, in _run_wrapper
    runtime = self._run_interface(runtime)
  File "/home1/03872/wtriplet/software/mriqc/mriqc/interfaces/qc.py", line 193, in _run_interface
    hmcdata = np.nan_to_num(hmcnii.get_data())
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/nibabel/spatialimages.py", line 582, in get_data
    data = np.asanyarray(self._dataobj)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/numpy/core/numeric.py", line 525, in asanyarray
    return array(a, dtype, copy=False, order=order, subok=True)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/nibabel/arrayproxy.py", line 144, in __array__
    raw_data = self.get_unscaled()
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/nibabel/arrayproxy.py", line 139, in get_unscaled
    mmap=self._mmap)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/site-packages/nibabel/volumeutils.py", line 517, in array_from_file
    n_read = infile.readinto(data_bytes)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/gzip.py", line 268, in read
    self._read(readsize)
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/gzip.py", line 320, in _read
    self._add_read_data( uncompress )
  File "/work/03872/wtriplet/lonestar/anaconda/lib/python2.7/gzip.py", line 338, in _add_read_data
    self.extrabuf = self.extrabuf[offset:] + data
MemoryError:
Interface FunctionalQC failed to run.

Thanks a lot @wtriplett, this is really good material to work on.

Hi @chrisfilo, after looking deep into this I realized where the problem is. When I included checking matrix size, pixel spacing, tr and number of time points, I implemented it using nibabel.
This is the typical MemoryError when you try to open very large, gzipped, nifti files with nibabel. I can't tell if this particular errror that @wtriplett found is because the files are too large themselves or because of the fact that it would be trying to open 48 files at the same time.

We should do some memory profiling on a Linear run to figure this out.
BTW it's not just checking matrix size and pixel dimensions which caused
this particular MemoryError. It was reading the data itself:
https://github.com/poldracklab/mriqc/blob/f951560886c63305cfa5d782c1f81288fd85857d/mriqc/interfaces/qc.py#L193
On Fri, Mar 25, 2016 at 9:57 AM, Oscar Esteban<EMAIL_ADDRESS>wrote:

Hi @chrisfilo https://github.com/chrisfilo, after looking deep into
this I realized where the problem is. When I included checking matrix size,
pixel spacing, tr and number of time points, I implemented it using nibabel.
This is the typical MemoryError when you try to open very large, gzipped,
nifti files with nibabel. I can't tell if this particular errror that
@wtriplett https://github.com/wtriplett found is because the files are
too large themselves or because of the fact that it would be trying to open
48 files at the same time.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/poldracklab/mriqc/issues/35#issuecomment-201362654

True, I did not observe this. Then this is a big issue :(

Memory profiling on Linear:
(see: https://github.com/wtriplett/mem_ps_sampler_example)
Run on one ls5 node against a simple single subject data set with 1 anatomical (0.8 mm3 resolution) and 1 functional (multi band):
sub-023/anat/sub-023_T1w.nii.gz int16 [256, 256, 256] 0.80x0.80x0.80   sform
sub-023/func/sub-023_task-training_run-03_bold.nii.gz float32 [ 96,  96,  64, 329] 2.40x2.40x2.40x1.16   sform

Sampling the output of ps uawww every second during execution provides this report:

Maybe this is a start, and then we can see what could be added or improved about the sampling. I think trying to join this with the log from the mriqc stdout would be a good next step, but maybe it clear what's going on without needing to do that.

This is very useful! 3dresample and 3dcalc are things that probably coulb
be easily optimised.
On Sun, Mar 27, 2016 at 11:28 AM, William Triplett<EMAIL_ADDRESS>
wrote:

Memory profiling on Linear:
(see: https://github.com/wtriplett/mem_ps_sampler_example)
Run on one ls5 node against a simple single subject data set with 1
anatomical (0.8 mm3 resolution) and 1 functional (multi band):
sub-023/anat/sub-023_T1w.nii.gz int16 [256, 256, 256] 0.80x0.80x0.80   sform
sub-023/func/sub-023_task-training_run-03_bold.nii.gz float32 [ 96,  96,  64, 329] 2.40x2.40x2.40x1.16   sform
Sampling the output of ps uawww every second during execution provides
this report:
[image: rplot]
https://cloud.githubusercontent.com/assets/1926804/14066882/4388f35e-f40b-11e5-8dd7-3a11f98a154e.png
Maybe this is a start, and then we can see what could be added or improved
about the sampling. I think trying to join this with the log from the mriqc
stdout would be a good next step, but maybe it clear what's going on
without needing to do that.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/poldracklab/mriqc/issues/35#issuecomment-202117234

The overall memory footprint doesn't seem unreasonable really. Trying to run 48 instances of this in parallel on a single LS5 node w/ 65GB physical ram and no swap might be asking a bit much though.
It would be great to find a way to spread the work out across multiple nodes on ls5, but it seems that LS5's configuration of providing whole-nodes per job and its max jobs per queue limit rule out slurmgraph (although slurmgraph plugin does work well otherwise on LS5!)
Having an estimate of the worst case memory usage per subject can help me better set --nthreads and give a balance between parallelization and successful workflow execution (hopefully!). Also submitting --skip-functional to one node and --skip-anatomical to another also can cut the time roughly in half.

Sherlock, +1

Hi, for completness I attach a profile of multiproc threads = 48 run on the full dataset with --skip-anatomical. (60 subjects, 8 fMRI runs each).
The dark plot symbols are the program's memory usage. The colored lines are system memory partitions. The vertical dotted lines indicate crashed programs (using the timestamp from crash pickles). Its cool how the system starts digging into the cached mem when things get tight.

Out of curiosity - what did you use for profiling?
On Wed, Mar 30, 2016 at 7:49 AM, William Triplett<EMAIL_ADDRESS>wrote:

Hi, for completness I attach a profile of multiproc threads = 48 run on
the full dataset with --skip-anatomical. (60 subjects, 8 fMRI runs each).
The dark plot symbols are the program's memory usage. The colored lines
are system memory partitions. The vertical dotted lines indicate crashed
programs (using the timestamp from crash pickles). Its cool how the system
starts digging into the cached mem when things get tight.
[image: rplot]
https://cloud.githubusercontent.com/assets/1926804/14146099/53672754-f64b-11e5-9141-8188fd2feea1.png
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/poldracklab/mriqc/issues/35#issuecomment-203469524

A combination of cat /proc/meminfo and ps -jFl -u wtriplet -U wtriplet sampled continuously in the background during execution. The code and such is here, although i'm afraid its not too well organized at the moment: https://github.com/wtriplett/mem_ps_sampler_example

What do you think if I close this issue, and get a docker version ready for @wtriplett to test? We probably want to move to a subject&session paradigm and then merge all them together with EoD (End-of-Day), as we were speaking the other day. Is that correct, @chrisfilo ?

sounds good to me (although docker will not work on ls5, but I get your
point)
On Wed, Apr 13, 2016 at 3:40 PM, Oscar Esteban<EMAIL_ADDRESS>wrote:

What do you think if I close this issue, and get a docker version ready
for @wtriplett https://github.com/wtriplett to test? We probably want
to move to a subject&session paradigm and then merge all them together with
EoD (End-of-Day), as we were speaking the other day. Is that correct,
@chrisfilo https://github.com/chrisfilo ?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/poldracklab/mriqc/issues/35#issuecomment-209678292

Yes, the idea is to get direct access to the docker runners in TACC and start the benchmarking there.

I would not count on gaining access to docker runner, but this issue is
independent of sending one job per subject (which can be done with and
without docker).
On Wed, Apr 13, 2016 at 3:44 PM, Oscar Esteban<EMAIL_ADDRESS>wrote:

Yes, the idea is to get direct access to the docker runners in TACC and
start the benchmarking there.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/poldracklab/mriqc/issues/35#issuecomment-209678912

Well, it is connected to sending one job per subject, right? The bottleneck is when it tries to open several fmri datasets at the same time in one multiproc job, isn't it?

When I said "this issue" I was referring to not being able to access Docker
runners directly. All is good.
On Apr 13, 2016 3:55 PM, "Oscar Esteban"<EMAIL_ADDRESS>wrote:

Well, it is connected to sending one job per subject, right? The
bottleneck is when it tries to open several fmri datasets at the same time
in one multiproc job, isn't it?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/poldracklab/mriqc/issues/35#issuecomment-209682124


[QUESTION] Typer w/ asyncio

First check

[ ] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the Typer documentation, with the integrated search.
[X] I already searched in Google "How to X in Typer" and didn't find any information.
[ ] I already searched in Google "How to X in Click" and didn't find any information.

Description
Is it possible to get Typer to play nicely with asyncio? I would like to use Typer to create a utility that calls into a WebAPI service like FastAPI (thanks for that, BTW). I have options parsing and validating properly from a separate function, but Typer appears to exit directly instead of continuing.
Additional context
The relevant bits:
def parse_cli(
    hostValue: str = typer.Option(..., '--host', '-h', callback=validateHostValue, help='The DNS hostname (or IP address) of the WebAPI server'),
  ):

  return hostValue # ??? Would be really swell

async def main():
  print('Awaiting a GET response...') # Never gets to here

if __name__ == '__main__':
  print('START...')
  result = typer.run(parse_cli)
  print(f"RESULT TYPE {type(result)}") # Never gets to here

  asyncio.set_event_loop_policy(asyncio.WindowsProactorEventLoopPolicy())
  result: str = asyncio.get_event_loop().run_until_complete(main())
  if (result is not None) and (len(result) != 0):
    print(result)

Thanks for the guidance.

@JosXa
Sincd python 3.7, you can use asyncio.run to call an asyncio method from synchronous code.
Example:
import asyncio
import my_module_with_async_methods

@app_typer.command()
def hello() -> None:
    typer.echo(asyncio.run(my_module_with_async_methods.an_async_method()))

Thanks for the discussion here everyone! 👏  🙇
Thanks for coming back to close the issue @RobW3LGA  👍

Sorry for the long delay! 🙈  I wanted to personally address each issue/PR and they piled up through time, but now I'm checking each one in order.


async-profiler not working with alpine based containers running on graviton instances

I am trying to profile an application from inside a kubernetes pod.
Pod is running on aws graviton instances. We are using alpine base image for containers.
/app # uname -r
5.10.210-201.852.amzn2.aarch64
/app #
/app # cat /etc/alpine-release
3.17.5

When I run, i get following error:
tmp/async-profiler-3.0-linux-arm64 # cd bin/
/tmp/async-profiler-3.0-linux-arm64/bin # ./asprof 1
Target JVM failed to load /tmp/async-profiler-3.0-linux-arm64/bin/../lib/libasyncProfiler.so

java -agentpath:/tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so=start,summary,flat -version gives following output
/tmp/async-profiler-3.0-linux-arm64/bin # java -agentpath:/tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so=start,summary,flat -version
Picked up JAVA_TOOL_OPTIONS: -XX:+ExplicitGCInvokesConcurrent -Xms4G -Dkotlinx.coroutines.scheduler=off
Error occurred during initialization of VM
Could not find agent library /tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so in absolute path, with error: Error loading shared library libstdc++.so.6: No such file or directory (needed by /tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so)

After adding libstdc++.so.6, running into following error:
/tmp/async-profiler-3.0-linux-arm64/bin # java -agentpath:/tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so=start,summary,flat -version
Picked up JAVA_TOOL_OPTIONS: -XX:+ExplicitGCInvokesConcurrent -Xms4G -Dkotlinx.coroutines.scheduler=off
Error occurred during initialization of VM
Could not find agent library /tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so in absolute path, with error: Error loading shared library ld-linux-aarch64.so.1: No such file or directory (needed by /tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so)

/tmp/async-profiler-3.0-linux-arm64/bin # ls /lib/
apk/                    ld-musl-aarch64.so.1    libc.musl-aarch64.so.1  libssl.so.3             libz.so.1.2.13          modules-load.d/
firmware/               libapk.so.3.12.0        libcrypto.so.3          libz.so.1               mdev/                   sysctl.d/
/tmp/async-profiler-3.0-linux-arm64/bin # ls /lib/ld-musl-aarch64.so.1
/lib/ld-musl-aarch64.so.1

Tried adding gcompat, but it did not help.
/tmp/async-profiler-3.0-linux-arm64/bin # apk add gcompat
(1/3) Installing musl-obstack (1.2.3-r0)
(2/3) Installing libucontext (1.2-r0)
(3/3) Installing gcompat (1.1.0-r0)
OK: 318 MiB in 22 packages
/tmp/async-profiler-3.0-linux-arm64/bin # ls /lib/
apk                     ld-linux-aarch64.so.1   libapk.so.3.12.0        libcrypto.so.3          libssl.so.3             libucontext_posix.so.1  libz.so.1.2.13          modules-load.d
firmware                ld-musl-aarch64.so.1    libc.musl-aarch64.so.1  libgcompat.so.0         libucontext.so.1        libz.so.1               mdev                    sysctl.d
/tmp/async-profiler-3.0-linux-arm64/bin # java -agentpath:/tmp/async-profiler-3.0-linux-arm64/lib/libasyncProfiler.so=start,summary,flat -version
Picked up JAVA_TOOL_OPTIONS: -XX:+ExplicitGCInvokesConcurrent -Xms4G -Dkotlinx.coroutines.scheduler=off
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00000000000053a0, pid=279, tid=280
#
# JRE version:  (<IP_ADDRESS>+9) (build )
# Java VM: OpenJDK 64-Bit Server VM (<IP_ADDRESS>+9-LTS, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-aarch64)
# Problematic frame:
# C  0x00000000000053a0
#
# Core dump will be written. Default location: /tmp/async-profiler-3.0-linux-arm64/bin/core.279
#
# An error report file with more information is saved as:
# /tmp/async-profiler-3.0-linux-arm64/bin/hs_err_pid279.log
#
#
Aborted (core dumped)

How can I fix this issue? Any help is much appreciated.

Alpine/AArch64 binaries are not provided, but you may build them yourself: install g++, make and openjdk packages, then run make in the project directory.

Thank you, it helped.


Migrate CI to GH actions

Short Description and Why It's Useful
Few days ago we migrated from travis-ci.org to travis-ci.com to fix issues with hours-long CI jobs delays. Unfortunately two days ago TravisCI announced changes to plan for OSS, limiting it to 1000 minutes for Linux jobs (this can be extended on case-by-case basis, however it's unclear that are the criteria).
This PR migrates our CI jobs to GitHub Actions for better integration and with some improvements and better caching it reduces build time to about 5 minutes.
Which Environment This Relates To

[ ] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[X] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)
[ ] I've updated the Upgrade notes and Changelog on how to port existing Vue Storefront sites with this new feature

I've created similar pr for vsf1 (@filipsobol please check it :pray:) https://github.com/DivanteLtd/vue-storefront/pull/5129 Maybe we can remove travis at all :shrug: ?


Fix: Speaker's color changes when searching

Fixes #2348
Changes: Images (bitmaps) without a "vibrant" image profile will return null, and originally the background color of the speaker was never set.
Now, it tries to get a "vibrant" image profile. If it fails, it will try to get a "dark muted" image profile. I chose "dark muted" because the text of the speaker info is white and requires a darker color.
If there is still no "dark muted" profile, the bg color will be set to a default color, which is a shade of dark red.
Screenshots for the change:

Originally the first two speakers did not have a "vibrant" image profile thus their colors kept changing.
When searching:

@iamareebjamal Do help me to review, thank you!

@iamareebjamal Is it okay to use color primary dark?


Add incoming message poll frequency to settings

closes #289

Hey, sorry if we wasted your time. I did a complete server UI rewrite, and as part of it, I included this feature. If you'd like to check it out, im offering an alpha download of the new server + UI in the Discord. Join if you please :)
Either way, this is already implemented, so im closing this


add PnP

🚀 The feature, motivation and pitch
Refer to OpenCV PnP, a PnP module is often needed in SLAM problems. This PnP solver may also leverage the RANSAC module.
Alternatives
No response
Additional context
No response

Design slides: https://docs.google.com/presentation/d/1c2_mSIdkwsmpVjRHa8qjlNaMmJivRnXH3rX9bejMpVE/edit?usp=sharing

Is this problem solved?

@LueYinny it is in development and will release after an intensive test.

closed as #184 merged


Wrong coloration using videotoolbox with Dolby Vision

I'm having a heck of a problem with certain types of input that have Dolby Vision, specifically profile 8.1.
I don't think this is a bug with other-transcode, but more likely either ffmpeg, or videotoolbox. I apologize if this forum isn't appropriate, but I'm hoping we have enough expertise here that someone has some insights.
When I transcode the video, which is UHD and has DV profile 8.1, and I use --vt, the reds are washed out and appear orange. Additionally, many scenes flicker between a washed-out orange and a really-washed-out yellowish.
If instead do software encoding using --x265, things look as expected (to my untrained eye).
I have other dolby vision source material using other DV profiles that doesn't appear to have any problems (again, to my untrained eye).
I've reproduced the problem using some of Dolby's sample videos, such as this one:
https://media.developer.dolby.com/DolbyVision_Atmos/mp4/P81_GlassBlowing2_3840x2160%4059.94fps_15200kbps_fmp4.mp4
If I use ffprobe to compare the video stream of the hardware- and software-encoded outputs, here's the diff:
diff --git a/glassblowing_stream0_hardware.json b/glassblowing_stream0_software.json
index 1ca8e15..4c4a950 100644
--- a/glassblowing_stream0_hardware.json
+++ b/glassblowing_stream0_software.json
@@ -12,7 +12,7 @@
   "coded_height": 2160,
   "closed_captions": 0,
   "film_grain": 0,
-  "has_b_frames": 0,
+  "has_b_frames": 2,
   "sample_aspect_ratio": "1:1",
   "display_aspect_ratio": "16:9",
   "pix_fmt": "yuv420p10le",
@@ -21,7 +21,7 @@
   "color_space": "bt2020nc",
   "color_transfer": "smpte2084",
   "color_primaries": "bt2020",
-  "chroma_location": "left",
+  "chroma_location": "topleft",
   "field_order": "progressive",
   "refs": 1,
   "r_frame_rate": "19001/317",
@@ -29,7 +29,7 @@
   "time_base": "1/1000",
   "start_pts": 50,
   "start_time": "0.050000",
-  "extradata_size": 112,
+  "extradata_size": 2552,
   "disposition": {
     "default": 1,
     "dub": 0,
@@ -53,13 +53,13 @@
   "tags": {
     "HANDLER_NAME": "Bento4 Video Handler",
     "VENDOR_ID": "[0][0][0][0]",
-    "ENCODER": "Lavc60.31.102 hevc_videotoolbox",
-    "BPS": "8132415",
+    "ENCODER": "Lavc60.31.102 libx265",
+    "BPS": "8099559",
     "DURATION": "00:02:55.008683333",
     "NUMBER_OF_FRAMES": "10490",
-    "NUMBER_OF_BYTES": "177904713",
+    "NUMBER_OF_BYTES": "177185965",
     "_STATISTICS_WRITING_APP": "mkvpropedit v83.0 ('Circle Of Friends') 64-bit",
-    "_STATISTICS_WRITING_DATE_UTC": "2024-03-13 17:21:17",
+    "_STATISTICS_WRITING_DATE_UTC": "2024-03-13 17:35:30",
     "_STATISTICS_TAGS": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES"
   },
   "side_data_list": [

Here's ffprobe's report of the input video stream:
{
  "index": 0,
  "codec_name": "hevc",
  "codec_long_name": "H.265 / HEVC (High Efficiency Video Coding)",
  "profile": "Main 10",
  "codec_type": "video",
  "codec_tag_string": "hev1",
  "codec_tag": "0x31766568",
  "width": 3840,
  "height": 2160,
  "coded_width": 3840,
  "coded_height": 2160,
  "closed_captions": 0,
  "film_grain": 0,
  "has_b_frames": 3,
  "sample_aspect_ratio": "1:1",
  "display_aspect_ratio": "16:9",
  "pix_fmt": "yuv420p10le",
  "level": 153,
  "color_range": "tv",
  "color_space": "bt2020nc",
  "color_transfer": "smpte2084",
  "color_primaries": "bt2020",
  "chroma_location": "topleft",
  "refs": 1,
  "id": "0x1",
  "r_frame_rate": "60000/1001",
  "avg_frame_rate": "60000/1001",
  "time_base": "1/60000",
  "start_pts": 3003,
  "start_time": "0.050050",
  "duration_ts": 10500490,
  "duration": "175.008167",
  "bit_rate": "15138826",
  "extradata_size": 23,
  "disposition": {
    "default": 1,
    "dub": 0,
    "original": 0,
    "comment": 0,
    "lyrics": 0,
    "karaoke": 0,
    "forced": 0,
    "hearing_impaired": 0,
    "visual_impaired": 0,
    "clean_effects": 0,
    "attached_pic": 0,
    "timed_thumbnails": 0,
    "non_diegetic": 0,
    "captions": 0,
    "descriptions": 0,
    "metadata": 0,
    "dependent": 0,
    "still_image": 0
  },
  "tags": {
    "language": "und",
    "handler_name": "Bento4 Video Handler",
    "vendor_id": "[0][0][0][0]",
    "encoder": "HEVC Coding"
  },
  "side_data_list": [
    {
      "side_data_type": "DOVI configuration record",
      "dv_version_major": 1,
      "dv_version_minor": 0,
      "dv_profile": 8,
      "dv_level": 9,
      "rpu_present_flag": 1,
      "el_present_flag": 0,
      "bl_present_flag": 1,
      "dv_bl_signal_compatibility_id": 1
    }
  ]
}

Like I said, I feel like this is probably a bug in either ffmpeg or videotoolbox itself, but I'm hoping someone has some insights here and possibly ideas for workarounds
ffmpeg version: 6.1.1
other-transcode version: 0.12.0
macOS version:
ProductName:		macOS
ProductVersion:		14.2
BuildVersion:		23C64

I wonder whether your ffmpeg version is too old or that you aren't using the latest version (12 or "0.12.0") of other_video_transcoding. Anyway, I ran the following on your linked sample (with name shortened to "GlassBlowing.mp4").  The output looked splendid and the file size was reduced from 345 to 142 megabytes.
other-transcode --mp4 --target 4000 ~/Downloads/GlassBlowing.mp4

Oh sorry, I should have put my version information earlier in the post. Here it is again:
ffmpeg version: 6.1.1
other-transcode version: 0.12.0
macOS version:
ProductName: macOS
ProductVersion: 14.2
BuildVersion: 23C64
Did you encode it with videotoolbox, using the --vt option?
Here's the command I'm using:
other-transcode --crop auto --debug --vt --hevc --10-bit glassblowing.mp4

I wonder whether your ffmpeg version is too old or whether you aren't using the latest version (12 or "0.12.0") of other_video_transcoding. Anyway, I ran the following on your linked sample (with name shortened to "GlassBlowing.mp4"). The output looked splendid and the file size was reduced from 345 to 142 megabytes.
other-transcode --mp4 --target 4000 ~/Downloads/GlassBlowing.mp4

Ah, I see what happened in your case. The above command uses h264_videotoolbox and resizes down to 1080p. So no wonder it looks good for you. Unfortunately this means the output isn't UHD and has no HDR or dolby vision

I was thinking that you wanted .mp4, but I must have imagined that. When I use mpv (installed using --cask option for Homebrew) for playback, the mkv output of your "--crop auto --debug --vt --hevc --10-bit" other-transcode command looks just like the .mp4 original. But the latest version of IINA omm just displays a black window, but does display a minimal preview in the transport window when I manipulate the slider, which strikes me as very odd. Usually IINA and mpv can play the kitchen sink, but IINA gives me the same black window for the mp4 original, although it does not show the preview in the transport window. Sorry I couldn't provide more help. Maybe Sean or Lisa or someone else can.

To the best of my knowledge, ffmpeg doesn't support passing through the Dolby Vision metadata with videotoolbox. :-(

To the best of my knowledge, ffmpeg doesn't support passing through the Dolby Vision metadata with videotoolbox. :-(

I wonder if this documented somewhere that you know of (ffmepg's documentation can be hit or miss)? The reason I ask is that it raises even more questions
As far as I know videotoolbox has handled Dolby Vision just fine with my profile 7 content. I'm only encountering issues with profile 8.1
If true, I'm curious if it's a shortcoming in ffmpeg or in videotoolbox itself. And if the issue ffmepg, I wonder if there's an issue tracking it.
For now I can stick with x265. I'm fortunate enough to have a 2019 Intel Mac Pro but even with 32 threads, it only transcodes at around 0.45x for UHD :-(


chore: release new serverless gateway integration :tada:

Summary
What's changed?

Updated to be compatible with the latest gateway release
Update the documentation to prepare for v1.2.0 release

Why do we need this?

To release integration with the new gateway

How have you tested it?

Integration tests

Checklist

[x] I have reviewed this myself
[ ] There is a unit test covering every change in this PR
[ ] I have updated the relevant documentation

Details

The failing test is just some annoying logic where we try to download the same version of the API framework which fails if you bump the version without releasing it.


Allow custom git locations

Hey, thank you for this! I wanted to modify this package to install from a custom git repository, not just https://github.com/TimothyJones/github-cognito-openid-wrapper
There are several reasons why someone might want to do this. Here are mine:

I modified the behavior of the original wrapper (I needed to map a custom attribute)
I am developing on an M1 Mac and one of the dev dependencies of the wrapper is incompatible Apple Sillicon, therefore I removed it so that I can run cdk locally

So I believe this is a very legitimate use case. I am happy to modify my changes to make them to your liking.

Hi @lzrscg
This is a legitimate use case indeed, I'll merge this :)
Thanks for your contribution !

Released as v0.0.7


Upgrade dependencies

Coverage remained the same at 41.811% when pulling 9d0a49377b5863e4583dbec6ff6a465c20b73d0c on bjornreppen:fetch into 041bd21b831a0fc1476e833325d83d719f8cb195 on Artsdatabanken:master.


Update DOI notification box to be centered

💡 Description

When I submit a DOI for reserve, and it is successful, the output message should be centered on the page.

closing this as invalid for time being. not sure if it is fixed or not, but not a huge deal


fix(project-info): routes for case-id that should be blocked return 404 correctly

Ticket: https://pins-ds.atlassian.net/browse/ASB-1754
Routes used to return 500 instead of 404.

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


feat(Algebra/Module): presentation of the tensor product

Given presentations of two A-modules M₁ and M₂, we obtain a presentation of M₁ ⊗[A] M₂.

[x] depends on: #18408

Retrying...
bors merge


Missing support for domainservices 2021-03-01 and 2021-05-01

Service Package Request

The latest version of domainservices supported by the SDK is 2020-01-01. There are two newer versions available: 2021-03-01 and 2021-05-01
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/domainservices/resource-manager/Microsoft.AAD/stable/2021-03-01
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/domainservices/resource-manager/Microsoft.AAD/stable/2021-05-01

Related: https://github.com/terraform-providers/terraform-provider-azurerm/pull/10782

Hi @manicminer thanks for this issue!
We will work with the corresponding service team to release these new packages as soon as possible.


Parse model hooks for refs (#1957)

Fixes #1957
Add a parse pass for model hooks, parse them like models, attach the hook refs as if they were on the model.
Add a test exercising refs in model hooks.

Good point! I hadn't considered that.

Hello! How can i know if this PR was merged into master and to which Release?


Updates of the Gateway address in inbound-queue pallet make the bridge stuck

Removing the set_gateway extrinsic, making the config static and immutable.
Resolves: SNO-640
Cumulus Companion: https://github.com/Snowfork/cumulus/pull/61

Then would suggest deploying GatewayProxy with create2 in a more invariable and predictable way.

So updating the Gateway contract on Ethereum would require an upgrade on the Polkadot side as well?

Yes, it's hard coded in asset_hub here

So updating the Gateway contract on Ethereum would require an upgrade on the Polkadot side as well?

Yes it would. But because we use the proxy upgrade pattern this will only ever need to happen once.

Then would suggest deploying GatewayProxy with create2 in a more invariable and predictable way.

We will first deploy with a zero address and then runtime upgrade to update the address.

We will first deploy with a zero address and then runtime upgrade to update the address.

With create2 the address is fully predictable(as the proxy code is pretty simple and will not change) so there is no need for a runtime upgrade.

We will first deploy with a zero address and then runtime upgrade to update the address.

With create2 the address is fully predictable(as the proxy code is pretty simple and unlikely to change) so there is no need for a runtime upgrade. Another benefit it will be the same address across multiple networks(e.g. goerli and mainnet).

The create2 option does come with various drawbacks that complicate operations. For example, the deployed bytecode needs to be the same across all networks. And when we deploy the gateway proxy, we also need to deploy an implementation contract, and need to upgrade it even though the BridgeHubs don't exist yet.
So I am not too keen on using create2 for these reasons.


[MM-809]: fix the issue of getting errors when using github api with revoked/invalid token

Summary

Fixed the issue of getting errors when using GitHub API with revoked/invalid tokens.
Created a wrapper function and used it on all the githubClient calls, in case of invalid token error, disconnected the user and DMed him to reconnect

Created a PR on mattermost remote with all these changes hence closing this one


Add Styleguide

Add a mountable styleguide that can be mounted with mount MountainView::Engine => "/mountain_view".
It depends on all components having a <component>.yml file defining examples and properties.

+1 Go ahead


DepolarizingChannel tries to depolarize measurements and also fails at it

Injects a gate after the measurement. Probably shoudn't do any at all.
Also it should perhaps be called DephasingChannel.

I think the issue is still relevant, but that it should be delayed because of the new work on noise. It will be properly obsoleted at a later time.

@Strilanc Does the recent work on noise obsolete this?

This is obsolete, although oddly prescient of running into the same issue with the new models. But there's already a bug for that.


✨ Branch w/ Slither & Solhint?

https://github.com/foundry-rs/forge-template/pull/49/files
https://github.com/FrankieIsLost/forge-template/blob/cdea5d32c03a4c29030ed851830c55c82300b1ed/.github/workflows/CI.yml#L25

would need a good solhint config (ignoreConstructors, etc)


GH-1101: Message Listener Micrometer Timers

Resolves https://github.com/spring-projects/spring-amqp/issues/1101

BTW, I originally had it working as an advice - but it was a bit involved and I wasn't happy with the implementation; this ended up simpler.
I can push that branch if you want to look at it.

Well, I'm fine with simpler solution 😄
Thanks


The accuracy of my current training is not up to the accuracy in your paper

The accuracy of my current training is not up to the accuracy in your paper, I have trained it in full twice, the first time in A800 R@1: 87.4, R@5: 93.8, R@10: 94.5, R@20: 95.4, R@100: 97.0,the second time in RTX3090 R@1: 84.5, R@5: 91.5, R@10: 93.2, R@20. 93.8, R@100: 95.5
Is this the dataset you used?

Can you describe your experiment setting? For example, which script did you run? Did you modify anything in the code?

I used the experiment setting you provided, I used the train_global_retrieval.sh first to get a global retrieval model for rerank resume. Then I use train_reranking.sh and I did not change anything.

Except for the batchsize size, because I don't have that much memory

You should be able to get the same result if you are not using an extremely small batch size and follow all the instructions carefully. The learning rate must be tuned if you are using a very different batch size from our paper. There is no way for me to figure out the issue if the hyper-parameters (including package versions) and logs are not given.
There are several steps that you should take to debug:

download the pretrained model and use test.sh. See if you can get R@1 around 89.7.
use train_global_retrieval.sh and see if you can get R@1 over 79.
use the first command of train_reranking.sh and see if you can get R@1 around 88.4.
use the second command of train_reranking.sh and see if you can get R@1 around 89.7.
If you want to train it end-to-end. You can directly run train_end_to_end.sh and the R@1 should be around 87.3.

I can get R@1 around 89.7
2.I use train_global_retrieval.sh and get R@1 74.5
Maybe need I to change the learn rate for train_global_retrieval.sh, or may you provide a finetune model for global retrieval?And the msls_v2_deits.pth is no finetune model for global retrieval?

Please read the instructions carefully. The global retrieval model is provided as "msls_v2_deits.pth" on the ReadMe page.

Ok, Thanks for your reply!


update time before validator creation in web monitor

Simple problem, simple fix. Epochs before validators are allowed to create accounts has been increased (const EPOCHS_UNTIL_ACCOUNT_CREATION: u64 = 13; in TowerState.move), but this change has not been reflected in the web monitor.

Thanks @jamesmeijers ! We already have a PR for this issue: https://github.com/OLSF/libra/pull/853
But I do think that we need to change de global constant EPOCHS_UNTIL_ACCOUNT_CREATION to 14 and make the appropriate condition check using >= instead of > here:

https://github.com/OLSF/libra/blob/main/language/diem-framework/modules/0L/TowerState.move
I'll be glad to review your changes on that :)

Ah, glad to see it's taken care off. I'll submit a PR for the other thing.


Move functionality from toplevel.cpp to toplevel.py (more control flow of PnR in python)

[x] Enable placement flow in python
[x] Enable top-down route in python
[x] Enable individual routing stages in python

I think this is ready to check in (once the CI finishes.)
We can now control the PnR code using Python, including the routing.


Remove Dockerfile copying from Standard Staging

Docker context does not make any sense for standard/compat staging where you use appengine-web.xml because you cannot specify runtime: custom there.
This is a followup to #92.

@loosebazooka
Disregard, because runtime:custom is automatically written into the app.yaml during translation from appengine-web.xml to app.yaml when a Dockerfile is detected in the staging directory.


Fix timeline inconsistency

Update the paper review timeline so it matches what was said in this post on Piazza

I forgot the official policy TBH. But this will work ;-)


Horrible Documentation

I was trying to use the Firestore google APIs for pure Dart server, and the documentation in the code is not at all helping. It's like it was written not to be used. I know this issue would be deleted but wanted to make sure someone would see it. Please let me know how can we help in adding better examples.

The documentation within each API is automatically generated from the source JSON. Not much we can do there.
Can you like to a specific case where something is confusing?

Recently I was working with Firestore API, and I wanted to write in batch. The document classes and methods did not help much I understand how it could be used. Then after digging into the package code, I realized that it is an implementation of REST API. This gave me better clarity. But I had to spend a whole day to understand what was missing and what was wrong.

We're limited to what's available here, sadly: https://firestore.googleapis.com/$discovery/rest?version=v1


Potential Bug of MultiDataAspectRatioBatchSampler in the mmdet v3.2.0

In the lastest upadate, mmdet introudces MultiDataAspectRatioBatchSamplerhttps://github.com/open-mmlab/mmdetection/blob/fe3f809a0a514189baf889aa358c498d51ee36cd/mmdet/datasets/samplers/batch_sampler.py#L120. It is a great feature that makes it possible for multiple dataset training.
However, when I use it in my own project, I found that it may introduce bugs under the DDP training. Specifically, in different ranks, the number of batch may be different and thus makes the whole job hanging.
The bug may be caused by the following code snippet:
https://github.com/open-mmlab/mmdetection/blob/fe3f809a0a514189baf889aa358c498d51ee36cd/mmdet/datasets/samplers/batch_sampler.py#L164-L173
Suppose that we have 2 datasets both with 100 samples. They are splitted into 4 ranks. Each rank will have 50 samples. If the batchsize on both datasets are 2, it is expected each rank will have 25 batches (if 24-26 samples for two datasets). However, if drop_last is enabled and we have 25-25 samples for each datasets on a specific rank, the number of batches for each datasets will be 12 (the remaining 1 sample will be dropeed). The number of batches will be 24.
I wonder if anyone else has encountered this situation while using the MultiDataAspectRatioBatchSampler?
kindly @ryylcc

A potential solution might be all_reduce the number of batch to get the minumum batches among ranks and drop the remaining samples. But this may drastically reduce the number of samples for each rank when the number of rank is large.
num_batch = torch.tensor(len(self), device='cpu')
rank, world_size = get_dist_info()
if world_size > 1:
    group = get_default_group()
    backend_device = get_comm_device(group)
    num_batch.to(device=backend_device)
    torch_dist.all_reduce(num_batch, op=ReduceOp.MIN, group=group)

Update:
The fix works in our project. But I am not very clear if there's a better solution, such as the cooperation between Sampler and BatchSampler.


Reorganization of the code in views and store subdirectories

Motivation
As suggested by Mathieu Baudet, the change is done. It allows a little bit more of clarity.
Proposal
The following changes were done:

Creation of store and putting there the memory, DynamoDb, RocksDb and ScyllaDb related codes.
Creation of the views subdirectory and insertion of the _view.rs codes.
The views.rs code is renamed as view.rs. The trait declaration should be on the top level in my opinion.

Test Plan
The CI should take care of it.
Release Plan
There should be little impact there.
Links

reviewer checklist

This PR is closed since there was some misunderstanding about what needed to be done.


Add new content case expression

Adding a new content for case expression:

This PR is awesome! I like the example given here! 😁