Error while installing bower via maven

Hi
I am trying to build lumify and failed while installing one of the dependency .
Error as following. Kindly help .  Recent browserify uses https://github.com/feross/buffer
==> demo: >> npm
==> demo: >>
==> demo: >> WARN excluding symbolic link lib/index.js -> jade.js
==> demo: >> npm
==> demo: >> WARN EPACKAGEJSON<EMAIL_ADDRESS>No license field.
==> demo: >> npm
==> demo: >> ERR! Linux 2.6.32-573.7.1.el6.x86_64
==> demo: >> npm ERR! argv "/usr/local/bin/node" "/usr/bin/npm" "install" "-q"
==> demo: >> npm ERR! node v4.2.1
==> demo: >> npm ERR! npm
==> demo: >> v3.3.9
==> demo: >> npm ERR! path ../esprima/bin/esparse.js
==> demo: >> npm ERR! code EPROTO
==> demo: >> npm ERR!
==> demo: >> errno -71
==> demo: >> npm ERR! syscall symlink
==> demo: >>
==> demo: >> npm ERR! EPROTO: protocol error, symlink '../esprima/bin/esparse.js' -> '/vagrant/web/war/src/main/webapp/libs/PathFinding.js/node_modules/.bin/esparse'
==> demo: >> npm ERR!
==> demo: >> npm ERR! If you need help, you may report this error at:
==> demo: >> npm ERR!     <https://github.com/npm/npm/issues>
==> demo: >> npm
==> demo: >> ERR! Linux 2.6.32-573.7.1.el6.x86_64
==> demo: >> npm ERR! argv "/usr/local/bin/node" "/usr/bin/npm" "install" "-q"
==> demo: >> npm ERR! node v4.2.1
==> demo: >> npm ERR! npm  v3.3.9
==> demo: >> npm
==> demo: >> ERR! path npm-debug.log.92cb5c502c5cc7dea5fd32a8eafd6a97
==> demo: >> npm ERR! code ETXTBSY
==> demo: >> npm ERR! errno -26
==> demo: >> npm ERR! syscall
==> demo: >> rename
==> demo: >> npm ERR! ETXTBSY: text file is busy, rename 'npm-debug.log.92cb5c502c5cc7dea5fd32a8eafd6a97' -> 'npm-debug.log'
==> demo: >> npm
==> demo: >> ERR!
==> demo: >> npm
==> demo: >> ERR! If you need help, you may report this error at:
==> demo: >> npm ERR!     <https://github.com/npm/npm/issues>
==> demo: >> npm
==> demo: >> ERR! Please include the following file with any support request:
==> demo: >> npm ERR!     /vagrant/web/war/src/main/webapp/libs/PathFinding.js/npm-debug.log
==> demo: >> Exited with code: 185.
==> demo: Warning: Task "exec:buildPathFinding" failed. Use --force to continue.
==> demo: Aborted due to warnings.
==> demo: [INFO] ------------------------------------------------------------------------
==> demo: [INFO] Reactor Summary:
==> demo: [INFO]
==> demo: [INFO] Lumify: Web: War ................................... FAILURE [23:52 min]
==> demo: [INFO] Lumify: Web: Plugin: Social Authentication ......... SKIPPED
==> demo: [INFO] Lumify: Web: Plugin: Username/Password Authentication SKIPPED
==> demo: [INFO] Lumify: Web: Plugin: X509 Authentication ........... SKIPPED
==> demo: [INFO] Lumify: Web: Plugin: x509/LDAP Authentication ...... SKIPPED
==> demo: [INFO] Lumify: Web: Plugin: Geo-coder: Bing ............... SKIPPED
==> demo: [INFO] Lumify: Web: Plugin: Google Analytics .............. SKIPPED
==> demo: [INFO] Lumify: Web: Plugin: Change Password ............... SKIPPED
==> demo: [INFO] Lumify: Web: Client API: Code Generator ............ SKIPPED
==> demo: [INFO] Lumify: Dev ........................................ SKIPPED
==> demo: [INFO] Lumify: Dev: Jetty Server .......................... SKIPPED
==> demo: [INFO] Lumify: Dev: GraphPropertyWorker: Local ............ SKIPPED
==> demo:
==> demo: [INFO] Lumify: Dev: Tomcat Server ......................... SKIPPED
==> demo: [INFO] Lumify: Dev: Import ................................ SKIPPED
==> demo: [INFO] Lumify: Integration Test ........................... SKIPPED
==> demo: [INFO] Lumify: Benchmarks ................................. SKIPPED
==> demo: [INFO] Lumify: Migrations ................................. SKIPPED
==> demo: [INFO] ------------------------------------------------------------------------
==> demo: [INFO] BUILD FAILURE
==> demo: [INFO] ------------------------------------------------------------------------
==> demo: [INFO] Total time: 24:24 min
==> demo: [INFO] Finished at: 2015-10-26T15:54:15+00:00
==> demo: [INFO] Final Memory: 55M/114M
==> demo: [INFO] ------------------------------------------------------------------------
==> demo: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (WebApp Dependencies and Minification) on project lumify-web-war: Command execution failed. Process exited with an error: 3 (Exit value: 3) -> [Help 1]
==> demo: [ERROR]
==> demo: [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
==> demo:
==> demo: [ERROR] Re-run Maven using the -X switch to enable full debug logging.
==> demo: [ERROR]
==> demo:
==> demo: [ERROR] For more information about the errors and possible solutions, please read the following articles:
==> demo: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Can you post the npm-debug.log file from the failed install?

@sunnytham - Are you still having this issue with you Maven build? If you can supply the npm-debug.log, that would be very helpful in getting this resolved for you.

Closing for no feedback


The file {0} being validated does not exist.

Hi,
thanks for this plugin.
I hope to get help with following issue:
[ant:deploy] CWWKM2013I: Die validierte Datei C:\Apps\FIDE\wlp\usr\servers\defaultServer\logs\console.log ist nicht vorhanden.

It translates to:
CWWKM2013I: The file {0} being validated does not exist.

My gradle.build:
apply plugin: 'java'
apply plugin: 'war'
apply plugin: 'liberty'

repositories {
    jcenter()
}

buildscript {
    dependencies {
        classpath files('C:\\Apps\\FIDE\\gradle-2.5\\wlp-plugin\\wlp-anttasks.jar')
        classpath files('C:\\Apps\\FIDE\\gradle-2.5\\wlp-plugin\\liberty-gradle-plugin.jar')
        classpath files('C:\\Apps\\FIDE\\wlp\\bin\\tools\\ws-server.jar')
    }
}

liberty {
    wlpDir = 'C:\\Apps\\FIDE\\wlp'
    serverName = 'defaultServer'
    deploy {
    	file = 'C:/Data/git/Experiments/Experiment/build/libs/Experiment.war'
    }
    packageLiberty{
        archive = "MyServerPackage.zip"
        include = "usr"
    }
    dumpLiberty{
        archive = "C:/Temp/Dump.zip"
        include = "heap, system"
    }
    javaDumpLiberty{
        archive = "JavaDump.zip"
        include = "system"
    }
}

Best regards.

Hi, did you start the server before make the deploy?

Hi,
thank you for the answer.
I tried both. Starting the server and then call gradle deploy and call gradle deploy without starting the server. In both cases I get the error message and then a timeout at the end.
However, it seems when I start the server first then the deployment works but I have to wait for the timeout.
Best regards.

I cannot find the console.log file in folder:
C:\Apps\FIDE\wlp\usr\servers\defaultServer\logs

There is only a messages.log file.
The logging configuratin in my wlp server.xml is as follows:
<logging consoleLogLevel="INFO" copySystemStreams="true"/>

There seems to be a difference between starting the server using the terminal with
server start

command and starting the server using eclipse (with the WebSphere Application Server Liberty Profile Development Tools installed). In the latter the console.log file gets not created. It's a pity.
Deploying works when starting the wlp in the terminal.

Last message on this issue :-)
As a workaround for eclipse, the server can be configured like this:
<logging consoleLogLevel="INFO" copySystemStreams="true" messageFileName="console.log"/>

Then deploying in terminal with
gradle deploy

works.


Translation of method 'string.ToString' failed

Hello,
Since version 1.2.1 the query generated by Castle added a call to ToString() to string fields which LINQ to SQL cannot translate, so now we can't use the library to query the database with EF like we used to with version 1.2.0.
Is there a workaround we can use? We can't call ToList, we need the filter to be translated to SQL.
System.InvalidOperationException: The LINQ expression 'DbSet()
.Where(a => a.Description != null && a.Description.ToString().ToLower().Contains("abc"))' could not be translated. Additional information: Translation of method 'string.ToString' failed. If this method can be mapped to your custom function, see https://go.microsoft.com/fwlink/?linkid=2132413 for more information. Either rewrite the query in a form that can be translated, or switch to client evaluation explicitly by inserting a call to 'AsEnumerable', 'AsAsyncEnumerable', 'ToList', or 'ToListAsync'. See https://go.microsoft.com/fwlink/?linkid=2101038 for more information.
at Microsoft.EntityFrameworkCore.Query.QueryableMethodTranslatingExpressionVisitor.g__CheckTranslated|15_0(ShapedQueryExpression translated, <>c__DisplayClass15_0& )
at Microsoft.EntityFrameworkCore.Query.QueryableMethodTranslatingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression)
at Microsoft.EntityFrameworkCore.Query.QueryableMethodTranslatingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression)
at Microsoft.EntityFrameworkCore.Query.QueryableMethodTranslatingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression)
at Microsoft.EntityFrameworkCore.Query.QueryCompilationContext.CreateQueryExecutor[TResult](Expression query)
at Microsoft.EntityFrameworkCore.Storage.Database.CompileQuery[TResult](Expression query, Boolean async)
at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.CompileQueryCore[TResult](IDatabase database, Expression query, IModel model, Boolean async)
at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.<>c__DisplayClass12_01.<ExecuteAsync>b__0()    at Microsoft.EntityFrameworkCore.Query.Internal.CompiledQueryCache.GetOrAddQuery[TResult](Object cacheKey, Func1 compiler)
at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.ExecuteAsync[TResult](Expression query, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Query.Internal.EntityQueryProvider.ExecuteAsync[TResult](Expression expression, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteAsync[TSource,TResult](MethodInfo operatorMethodInfo, IQueryable1 source, Expression expression, CancellationToken cancellationToken)    at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteAsync[TSource,TResult](MethodInfo operatorMethodInfo, IQueryable1 source, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.CountAsync[TSource](IQueryable`1 source, CancellationToken cancellationToken)

@liacolo Gotcha, didn't consider the EF use case in this context - it can't materialize a query from it. I'd revert to 1.2.0 for the moment. I'll revert the change and work out something else for GUIDs (the reason we added the .ToString()) and push a new build in a couple of days.

great, thank you @tghamm

@liacolo this should be corrected in 60c2fd3 (1.2.3) - sorry for the trouble and appreciate you bringing it to my attention.  Let me know if there are still any issues.


Tests from one Suite are run in different proccesses

Hi all!
i'm experiencing the following problem:
I've got autotests for Magento 2, they are divided in testsuites, each test in suite is located in its own file,
In phpunit.xml suites are defined like this:
  <testsuite name="MainMenu">
            <directory suffix="Test.php">tests/app/MainMenu/</directory>
        </testsuite>
        <testsuite name="SocialLogin">
            <directory suffix="Test.php">tests/app/SocialLogin/</directory>
        </testsuite>

I'm running tests with the following command:
vendor\bin\paratest.bat --processes="2" --phpunit vendor\bin\phpunit.bat --configuration .\phpunit.xml
What I expect to see: tests from each suite are executed in separate process.
What I've got: Tests from one suite are executed in different processes in parallel.
how can I run tests from one suite (even if they are defined each in personal class) in one process?

I don't think thats implemented.
What you're talking about is per-testsuite-parallelization (discussed here a while ago).
Afaik paratest only supports per-testcase-, per-testmethod-, and per-dataset-parallelization (without -f, with -f, -f + --max-batch-size... in that order).
Do you have inter test dependencies?
Then @depends should work to make one testmethod depend on another and make them execute in the same process. ("Should" because I have never used or seen them between different Classes.)

@julianseeger Thank you for your answer. You're right, paratest can't help me with parallel execution of testsuites.
I solved this problem with running my tests via ant builder.
I'm closing the question.


Dependencies update

hi,
i think this pull request is more in line
with your initial work, far better.
would you mind to pull this?
thanks
btw excellent ERD tool!

Just to confirm, it works fine in 5.6 to 5.8 ?

i did only full test the install and working with 5.8
this leads me to think this does work with 5.6 and 5.7 as well
drop me a note if you want me to check 5.6 and 5.7 as well.

Iftekhar,
thank you merging.
and please have a look at my issue question about src/resources:
https://github.com/Agontuk/schema-builder/issues/7
o btw, did use your schema-builder in
https://github.com/noud/seo#entity-relationship-diagram


jenssegers/mongodb migrations for creating unique index on multiple fields

I need to create a Laravel migration for a unique key on multiple fields. The Mongodb command i want to map is something like this:
db.collection.ensureIndex( { a: 1, b: 1 }, { unique: true })

Is it possible with jenssegers/mongodb or with another package?

Schema::create('collection', function ( $collection ) {
$collection->unique(array( 'a', 'b' ));
});

InsertMany with 'ordered' false not working. Means ignore duplicate and continue to insert not working.


群发接口增加 send_ignore_reprint 和 client_msg_id 参数

https://mp.weixin.qq.com/wiki?t=resource/res_main&id=mp1481187827_i0l21

Codecov Report

Merging #349 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #349   +/-   ##
=======================================
  Coverage   72.97%   72.97%
=======================================
  Files          74       74
  Lines        2601     2601
=======================================
  Hits         1898     1898
  Misses        703      703

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 6af2a5a...431d58d. Read the comment docs.


@codegenie/serverless-express has not been release to npm

npm install @codegenie/serverless-express
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@codegenie%2fserverless-express - Not found
npm ERR! 404
npm ERR! 404  '@codegenie/serverless-express@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!      /Users/johndoe/.npm/_logs/2023-12-14T10_14_09_226Z-debug-0.log
✕ 1

https://www.npmjs.com/package/@codegenie/serverless-express -> 404 Not Found

You caught me in the middle of transferring! It's published now.

sorry wasn't my intention :-D


Broken import with NumPy 1.26

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Your input system relies on the numpy.__config__.get_info function, which isn't present in version 1.26. On import I get the following exception:
from deepmd.infer import DeepPot
  File "/storage/home/vlc79/vlc79784/.conda/envs/mamba/lib/python3.10/site-packages/deepmd/__init__.py", line 32, in <module>
    set_mkl()
  File "/storage/home/vlc79/vlc79784/.conda/envs/mamba/lib/python3.10/site-packages/deepmd/env.py", line 244, in set_mkl
    if "mkl_rt" in np.__config__.get_info("blas_mkl_info").get("libraries", []):
AttributeError: module 'numpy.__config__' has no attribute 'get_info'

In an environment with NumPy 1.25:
>>> import numpy
>>> numpy.__config__.get_info
<function get_info at 0x7fb91ccefec0>

With NumPy 1.26:
>>> import numpy
>>> numpy.__config__.get_info
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: module 'numpy.__config__' has no attribute 'get_info'

Installed packages
N/A

Environment info
N/A

I can repost on your main development repo if desired, but as it stands your current conda package is broken given the recipe used here.

Many thanks for the quick fix, much appreciated.


Comment on the responsibility of the wallet

It's more a comment rather a PR that needs to be merged.

Hi, @skounis. I wanted to show that there are a couple of different aspects in which a wallet could be used in this journey. Specifically, using it to purchase the ticket, which in turn requires that the ticket is stored in the wallet. We definitely could break the purchase use case into two separate use cases.

Purchase Ticket
Save Ticket

The purchase ticket use case would then in turn utilize the save ticket use case to store the ticket in the wallet. I will work on making that change.


Build mox release

According to the README.md file, I can either build mox with the command GOBIN=$PWD CGO_ENABLED=0 go install github.com/mjl-/mox@latest or download it from beta.gobuilds.org where an other build command is given (GO19CONCURRENTCOMPILATION=0 GO111MODULE=on GOPROXY=https://proxy.golang.org/ CGO_ENABLED=0 GOOS=linux GOARCH=amd64 GOTOOLCHAIN=go1.23.0 go1.23.0 install -trimpath -ldflags='-buildid=' -- github.com/mjl-/mox@v0.0.11);
According to the Docker.release file, the command CGO_ENABLED=0 GOOS=$goos GOARCH=$goarch go install -mod mod -trimpath github.com/mjl-/mox@$moxversion is used to build mox, the result is then copied to the Docker image.
And according to the Makefile, the command make build builds mox twice, builds a nodejs frontend and runs some shell scripts.
So, I'm wondering what is the proper way to build a mox release and what are the differences between methods listed above.

Ah yes, that's quite some variation. (:
The basic way to compile the latest mox release would be go install github.com/mjl-/mox@latest. That fetches the mox code as Go module through the Go module proxy, resolving "latest" to the current latest version (git tag).
The command in the README adds GOBIN=$PWD so the binary ends up in the working directory instead of the Go default of writing it to $HOME/go/bin. For Go developers, that default probably makes sense, but for non-Go-developers compiling mox themselves it's not helpful if the binary goes to some other location.
CGO_ENABLED=0 is added everywhere to prevent linking with C libraries. Compilation works fine without. But then the binary may depend on a local libc, and may prevent the binary from working on other machines with other libc's. The Go runtime may use the libc DNS resolver for some lookups (those that aren't going through the adns library, with CGO_ENABLED=0 they go through the Go stdlib resolver). This is in all the versions of the commands to compile, so it's probably not causing confusion.
The command shown on beta.gobuilds.org has more options to make the compilation reproducible, resulting in the exact same binary (identical bytes). The command has become a bit obscure, so I think it's not worth the obscurity to put the same command in the mox README. Details about the flags and env vars in the command on beta.gobuilds.org:

-trimpath removes absolute file system paths from the binary (as shown in stack traces). Without this, the binary contains paths of the directory where the binary was built, making it harder to reproduce the identical binary.
`ldflags='-buildid=' removes the buildid from the resulting binary. The buildid contains 4 hashes, mostly of the input code and versions. I think one of the hashes depends on the path the toolchain is installed, that's why it is stripped, to make reproducing the binary easier. But this could be an outdated assumption.
GO19CONCURRENTCOMPILATION=0 is a workaround for an old "bug" (long since fixed) in the Go toolchain that caused builds in some cases to be non-reproducible (this issue was found by gobuilds.org while verifying against other gobuild instances!).
GO111MODULE=on is for older Go toolchains to force Go module mode. This has been the default for the Go toolchain for a long time now, not actually required for current builds. But gobuilds.org can (in theory) build with old toolchains too.
GOPROXY=https://proxy.golang.org/ forces all downloads to go through the Go module proxy, not going directly to the source. This is good for the gobuilds.org service, not for local builds.
GOTOOLCHAIN=go1.23.0 sets an explicit toolchain version, preventing any automatic toolchain updates, important for the gobuilds.org service, not for local builds. Same for the explicit version in the Go command.
<EMAIL_ADDRESS>has the explicit version number (instead of latest) because the gobuilds.org page is for that specific version.

The Docker.release file has -trimpath for reproducibility (and the resulting docker image doesn't have the source anyway). The Go toolchain path is the same, so removing the buildid isn't needed. The -mod mod ensures the local vendor/ directory (with all dependencies) isn't used, but all dependencies are downloaded. This is how go install github.com/mjl-/mox@latest would build mox (the mox code is fetched from the Go module proxy, which does not include the vendor/ directory), and it's how the gobuilds.org service builds code. So it's to be closer to those builds.
The Makefile indeed builds twice: After the first build commands, the resulting binary is used to generate help output and API JSON & TS/JS files, and those are included in the binary in the second build. Those generated files are committed to git, so for building using "go install" we don't need to do a second build.
I consider the binaries from gobuilds.org to be the most authoritative releases. The binaries are reproducible, and it's the easiest way to get a binary for the most recent Go toolchain release (its runtime is included in the resulting mox binary). Building it locally is fine too, but there's a small risk that people have a somewhat older local Go toolchain/runtime installed.


file corruption when moving non-markdown files to folders currently visible in Projects

What happened?
simple file corruption
I first noticed this after rearranging some files while using a Projects view focused at the root of my vault with subfolders enabled.
I did some file rearranging, then added a boolean property to files in my library with the + Add field button.
I later noticed that non-markdown files in folders that were recently moved were not opening. Viewing them in notepad showed that the properties section was appended to the top of these files. Editing this out unfortunately did not fix the file.

the more uncertain one
I also later noticed that moving one of these larger folders would cause my entire obsidian app to freeze up on me. From what I can tell no notes were lost, but looking at some of the corrupt non-.md files in this folder, over 13k+ lines of junk were appended to the files, causing Projects to freeze up as soon as this file was detected by a view. I don't know how the junk actually ended up in the header of this file, and was not able to reproduce.

What did you expect to happen?
I expected either:

for non-.md files to always be invisible to Projects views,
for non-.md files to be visible to Projects views, but have their property rows grayed out,
(stretching) for non-.md files to show some non-.md file metadata, such as photo locations/dates, song tracknames, etc.

How can we reproduce it (as minimally and precisely as possible)?
I was able to reproduce the added properties header from a new vault by doing the following:

Enable the option "files and links" -> "detect all file extensions". (i haven't tested without this option)
Install the Projects plugin.
Create any type of non-markdown file and save it to your new vault (I tested both a .png and .pdn file.)
Create a new folder.
Create a view looking at this folder, or create a view looking at root and turn subfolders on.
Move the non-.md file into the folder.
The non-markdown file should now be visible in your view.
From this point, adding a new property or editing a property next to this file will cause file corruption, as a --- {property} --- section is appended to the file.

I don't actually know what exactly caused the corruption that put 13k lines of junk in one of the files...
Anything else we need to know?
that i appreciate y'all for making and maintaining this plugin, have a nice day!
Plugin version
1.17.2
Obsidian version
1.5.8
OS
Windows

Oh I see, many thanks! Can reproduce this and will fix. Let's handle the most fatal one first, preventing the non-md file from broken.
Possible solutions

Ban fs listener recognizing non md files
Ban folder datasource and the writing api for non md files


md_journal: don't convert local squashes to new squash branch

This avoids squashing previous squashes into new squashes, by skipping them during branch conversion.  This allows the journal to have a mix of merged and unmerged entries, which complicates some of the journalMDOps logic, but it doesn't seem too bad.
Also, the unflushedPathCache reinitialization logic had to change a bit since a branch resolve doesn't necessarily clear the whole branch, so we have to keep around the revisions that were earlier than resolution revision.
Issue: KBFS-1653

By the way, I don't have any DSL tests for this because getting a deterministic test would require instrumenting the tlfJournal code to avoid resuming background work after a ResolveBranch call, and I couldn't see a clean way of doing that after thinking about it for quite a while.  I tested it extensively by hand and my unit tests have decent coverage.

Ran a simple benchmark that copied an ~85 MB .git directory into KBFS, both with and without coalescing.  Here are the numbers for mdv3:
With coalescing (mdv3):

real	1m1.847s
user	0m0.036s
sys	0m0.136s

    "RevisionStart": 5033,
    "RevisionEnd": 5044,
    "BlockOpCount": 10415,
    "UnflushedBytes": 2869408,

real	0m52.014s
user	0m0.028s
sys	0m0.156s

    "RevisionStart": 5407,
    "RevisionEnd": 7663,
    "BlockOpCount": 19555,
    "UnflushedBytes": 462790345,

So, coalescing ran a little more slowly in realtime because it's pausing periodically to re-write the journal, but saves two orders of magnitude in unflushed bytes!

Thanks, ready for another look.

Thanks @akalin-keybase, ready for another look.  d303eaa and e614274 are the new commits.

(Note that this now merges into a branch that unreverts the first part of KBFS-1653.)

Ok, moved the filtering.  New commits fcc187f and 556f05a.  Please take another look!


Doxygen Error

Summary: Run through doxygen warnings raised in github and fix any warning found in current codebase
Type: Feature
Test Plan: Tested via the doxygen-build github action in the doxygen_errors.yml file
Jira: RIALTO-62

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: root:x: skyshaha1root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

https://jenkins.code.rdkcentral.com/job/github-triggered/26179/ started

https://jenkins.code.rdkcentral.com/job/build-component/62491/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18461/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30806/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134898/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134899/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134902/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134903/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134905/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/134904/

https://jenkins.code.rdkcentral.com/job/github-triggered/26217/ started

https://jenkins.code.rdkcentral.com/job/build-component/62569/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18488/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30861/ started.

build-brcm-va Console Log uploaded to Gist URL: https://gist.github.com/689b291bf98bb31f4a044f58868da0b1

build-brcm-refboard Console Log uploaded to Gist URL: https://gist.github.com/224a07e4db649a75d6a75d5ddeca0f73

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135003/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135004/

https://jenkins.code.rdkcentral.com/job/github-triggered/26240/ started

https://jenkins.code.rdkcentral.com/job/build-component/62612/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26243/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18508/ started

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135079/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135080/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135087/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135088/

https://jenkins.code.rdkcentral.com/job/github-triggered/26260/ started

https://jenkins.code.rdkcentral.com/job/build-component/62666/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18519/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30949/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26262/ started

https://jenkins.code.rdkcentral.com/job/build-component/62668/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18521/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30951/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26264/ started

https://jenkins.code.rdkcentral.com/job/build-component/62673/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18523/ started

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135151/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135152/

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30956/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26266/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18525/ started

https://jenkins.code.rdkcentral.com/job/build-component/62675/ started.

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30958/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26268/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18526/ started

https://jenkins.code.rdkcentral.com/job/build-component/62678/ started.

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30961/ started.

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135153/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135154/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135155/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135156/

https://jenkins.code.rdkcentral.com/job/github-triggered/26270/ started

https://jenkins.code.rdkcentral.com/job/build-component/62679/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18528/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30963/ started.

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135158/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135157/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135159/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135160/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135161/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135162/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135163/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135164/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135167/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135165/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135168/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135169/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135170/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135172/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135171/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135175/

https://jenkins.code.rdkcentral.com/job/github-triggered/26271/ started

https://jenkins.code.rdkcentral.com/job/build-component/62686/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18530/ started

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135181/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135182/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135183/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135184/

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30969/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26273/ started

https://jenkins.code.rdkcentral.com/job/build-component/62687/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18532/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30970/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26275/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18534/ started

https://jenkins.code.rdkcentral.com/job/build-component/62688/ started.

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135189/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135186/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135187/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135188/

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30971/ started.

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135194/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135192/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135193/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135191/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135207/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135208/

https://jenkins.code.rdkcentral.com/job/github-triggered/26277/ started

https://jenkins.code.rdkcentral.com/job/build-component/62689/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18536/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30973/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26279/ started

https://jenkins.code.rdkcentral.com/job/build-component/62691/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18537/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30974/ started.

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135214/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135213/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135215/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135216/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135217/

https://jenkins.code.rdkcentral.com/job/github-triggered/26281/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18539/ started

https://jenkins.code.rdkcentral.com/job/build-component/62692/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135221/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135220/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135222/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135218/

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30975/ started.

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135223/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135224/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135226/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135227/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135229/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135228/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135233/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135232/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135235/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135236/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135237/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135239/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135238/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135241/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135234/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135240/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135243/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135242/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135245/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135244/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135246/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135249/

https://jenkins.code.rdkcentral.com/job/github-triggered/26283/ started

https://jenkins.code.rdkcentral.com/job/build-component/62696/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18541/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30978/ started.

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135252/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135256/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135257/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135255/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135258/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135260/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135261/

https://jenkins.code.rdkcentral.com/job/github-triggered/26292/ started

https://jenkins.code.rdkcentral.com/job/build-component/62713/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18548/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30993/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26294/ started

https://jenkins.code.rdkcentral.com/job/build-component/62716/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18550/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30996/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/26296/ started

https://jenkins.code.rdkcentral.com/job/build-component/62717/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18552/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30997/ started.

https://jenkins.code.rdkcentral.com/job/build-component/62718/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18554/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/30998/ started.

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135290/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135288/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135289/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135287/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135292/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135295/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135294/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135297/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135296/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135300/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135301/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135303/

https://jenkins.code.rdkcentral.com/job/github-triggered/26300/ started

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18556/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/31000/ started.

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135304/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135305/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135306/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135307/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135308/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135309/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135310/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135311/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135314/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135315/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135320/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135321/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135322/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135325/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135324/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135326/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135327/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135328/

'['build-rpi-hybrid-refapp2']' Smoke test FAILURE, investigation pending.
Flash RefApp [SUCCESS]
RefApp - Video Test [FAILURE]
RefApp UI Home Screen Video Test [FAILURE]
RefApp Movie Session Mgr VoD Test [SUCCESS]
RefApp Channel Change Video Tests [SUCCESS]
https://jenkins.cmf.code.rdkcentral.com/job/test-raspberrypi-refapp-flow/27816/

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18565/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/26309/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/26310/ started

https://jenkins.code.rdkcentral.com/job/build-component/62732/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18566/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/31008/ started.

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/31010/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18567/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/26311/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/31013/ started.

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135344/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135345/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135343/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135346/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135347/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135348/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135349/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135350/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135355/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135357/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135356/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135360/

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135361/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135365/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135363/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135364/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135362/

https://jenkins.code.rdkcentral.com/job/github-triggered/26313/ started

https://jenkins.code.rdkcentral.com/job/build-component/62746/ started.

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/18569/ started

https://jenkins.cmf.code.rdkcentral.com/job/build-component-platform/31018/ started.

Smoke tests for ['build-rpi-hybrid-wpe-dunfell'/'build-rpi-mc-wpe-dunfell'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135384/

Smoke tests for ['build-rpi-hybrid-refapp2'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135383/

Smoke tests for ['build-aml-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135389/

Smoke tests for ['build-aml-reftv'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135390/

Smoke tests for ['build-brcm-refboard'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135391/

Smoke tests for ['build-brcm-va'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/135392/


passthrough-v2

This is an updated version of https://github.com/librespot-org/librespot/pull/327. It adds, per maintainer's request, seek for the passthrough option so that there is no feature difference with a normal decoder, except position which of course does not make sense here.
I had to add a tiny modification to https://github.com/RustAudio/ogg so that I can have access to a mutable inner object. I've submitted a PR but meanwhile, I've added a full version of that modified PacketWriter in case @est31 does not accept it. If he does, we can simply remove the file and the "mod".
This is my first real experience with Rust, so pardon some naive implementation. I hope you'll accept this as it will help the Spotty project for LMS.

This PR seems to include some files from my BSD licensed crate. It doesn't seem to comply with the BSD license.

This PR seems to include some files from my BSD licensed crate. It doesn't seem to comply with the BSD license.

This PR seems to include some files from my BSD licensed crate. It doesn't seem to comply with the BSD license.

I think I just copied the writer.rs, renamed it ogg_writer.rs, added the inner_mut fn and that's all. Happy to change anything else that I might have forgotten

This PR seems to include some files from my BSD licensed crate. It doesn't seem to comply with the BSD license.

I think I just copied the writer.rs, renamed it ogg_writer.rs, added the inner_mut fn and that's all. Happy to change anything else that I might have forgotten

@philippe44 the issue is that the LICENSE file referenced at the head of the file is different. You should create a LICENSE-BSD with this as the content and then change it to LICENSE-BSD, at least for that file you copy.

@philippe44 the issue is that the LICENSE file referenced at the head of the file is different. You should create a LICENSE-BSD with this as the content and then change it to LICENSE-BSD, at least for that file you copy.

What I still don't get: why not

move out the PacketWriter by doing mem::swap with a dummy one
call into_inner on the moved out PacketWriter
manipulate the internal Vec to your choosing
create a new PacketWriter from that Vec and mem::swap it into place

What I still don't get: why not

move out the PacketWriter by doing mem::swap with a dummy one
call into_inner on the moved out PacketWriter
manipulate the internal Vec to your choosing
create a new PacketWriter from that Vec and mem::swap it into place

@philippe44 the issue is that the LICENSE file referenced at the head of the file is different. You should create a LICENSE-BSD with this as the content and then change it to LICENSE-BSD, at least for that file you copy.

That part is done

@philippe44 the issue is that the LICENSE file referenced at the head of the file is different. You should create a LICENSE-BSD with this as the content and then change it to LICENSE-BSD, at least for that file you copy.

That part is done

What I still don't get: why not

move out the PacketWriter by doing mem::swap with a dummy one
call into_inner on the moved out PacketWriter
manipulate the internal Vec to your choosing
create a new PacketWriter from that Vec and mem::swap it into place

That what I did at the beginning, but I was losing the rest of the context of the PacketWriter (the hasmap) when I was pushing it back and so the file was incorrectly coded

What I still don't get: why not

move out the PacketWriter by doing mem::swap with a dummy one
call into_inner on the moved out PacketWriter
manipulate the internal Vec to your choosing
create a new PacketWriter from that Vec and mem::swap it into place

That what I did at the beginning, but I was losing the rest of the context of the PacketWriter (the hasmap) when I was pushing it back and so the file was incorrectly coded

That what I did at the beginning, but I was losing the rest of the context of the PacketWriter (the hasmap) when I was pushing it back and so the file was incorrectly coded.

Fair point!

Don't get me wrong, I'm a Rust rookie so I've probably made some non-elegant choices, but I tried that to start with. Maybe not correctly.

It's ok. I hope I'm not annoying you :).
As we've established that re-building a PacketWriter loses context, what about this different idea: usage of a wrapper struct like WrappedWriter(Rc<RefCell<Vec<u8>>) that you impl the Write trait on. Then you can keep the Rc around and manipulate it freely.

That what I did at the beginning, but I was losing the rest of the context of the PacketWriter (the hasmap) when I was pushing it back and so the file was incorrectly coded.

Fair point!

Don't get me wrong, I'm a Rust rookie so I've probably made some non-elegant choices, but I tried that to start with. Maybe not correctly.

It's ok. I hope I'm not annoying you :).
As we've established that re-building a PacketWriter loses context, what about this different idea: usage of a wrapper struct like WrappedWriter(Rc<RefCell<Vec<u8>>) that you impl the Write trait on. Then you can keep the Rc around and manipulate it freely.

It's ok. I hope I'm not annoying you :).

Not at all, that's a learning moment for me!

As we've established that re-building a PacketWriter loses context, what about this different idea: usage of a wrapper struct like WrappedWriter(Rc<RefCell<Vec<u8>>) that you impl the Write trait on. Then you can keep the Rc around and manipulate it freely.

So, I'll have to dig into Rc & RefCell which I did not do yet - I just started Rust 3 days ago :-). I looked at these and I was already struggling with the borrow-checker and lifetimes and concepts/syntax in general, so I left that part for later. I will look at it tomorrow (it late for me now)
Thanks!

It's ok. I hope I'm not annoying you :).

Not at all, that's a learning moment for me!

As we've established that re-building a PacketWriter loses context, what about this different idea: usage of a wrapper struct like WrappedWriter(Rc<RefCell<Vec<u8>>) that you impl the Write trait on. Then you can keep the Rc around and manipulate it freely.

So, I'll have to dig into Rc & RefCell which I did not do yet - I just started Rust 3 days ago :-). I looked at these and I was already struggling with the borrow-checker and lifetimes and concepts/syntax in general, so I left that part for later. I will look at it tomorrow (it late for me now)
Thanks!

Well ... there is always something else. I've managed to use Rc & RefCells with a wrapper, per @est31's suggestion like that
pub struct WrappedWriter {
    data :Rc<RefCell<Vec<u8>>>,
}

impl WrappedWriter {
    pub fn new(data : Rc<RefCell<Vec<u8>>>) -> Self {
        return WrappedWriter {
            data,
        };
    }
}

impl Write for WrappedWriter {
    fn write(&mut self, buf: &[u8]) -> Result<usize, Error> {
        let mut data = self.data.borrow_mut();
        data.write(buf)
    }
    fn flush(&mut self) -> Result<(), Error> {
        let mut data = self.data.borrow_mut();
        data.clear();
        Ok(())
    }
}

Just to be hit by the next problem with is that player.rs spawns (and move) the player's context so although everything actually moves and it's thread-safe, Rust compiler refuses to compile because of use of Rc. So I don't have any other solution for now
(sigh)

Well ... there is always something else. I've managed to use Rc & RefCells with a wrapper, per @est31's suggestion like that
pub struct WrappedWriter {
    data :Rc<RefCell<Vec<u8>>>,
}

impl WrappedWriter {
    pub fn new(data : Rc<RefCell<Vec<u8>>>) -> Self {
        return WrappedWriter {
            data,
        };
    }
}

impl Write for WrappedWriter {
    fn write(&mut self, buf: &[u8]) -> Result<usize, Error> {
        let mut data = self.data.borrow_mut();
        data.write(buf)
    }
    fn flush(&mut self) -> Result<(), Error> {
        let mut data = self.data.borrow_mut();
        data.clear();
        Ok(())
    }
}

Just to be hit by the next problem with is that player.rs spawns (and move) the player's context so although everything actually moves and it's thread-safe, Rust compiler refuses to compile because of use of Rc. So I don't have any other solution for now
(sigh)

@philippe44 you can try using an Arc instead of an Rc. That should be enough.

@philippe44 you can try using an Arc instead of an Rc. That should be enough.

@philippe44 you can try using an Arc instead of an Rc. That should be enough.

Unfortunately the same error happens with RefCell

@philippe44 you can try using an Arc instead of an Rc. That should be enough.

Unfortunately the same error happens with RefCell

Hmm then maybe a Mutex is needed instead of the RefCell.... sad that it can't be all moved over in one go. I think this is some limitation of the Rust type system...

Hmm then maybe a Mutex is needed instead of the RefCell.... sad that it can't be all moved over in one go. I think this is some limitation of the Rust type system...

... well using Arc<Mutex<Vec>> worked ... this is a real pain and probably a lot of un-needed consumption of mutexes & al. At least, I had a crash course on Rc, RefCell, Arc, RwLock and Mutex in Rust

... well using Arc<Mutex<Vec>> worked ... this is a real pain and probably a lot of un-needed consumption of mutexes & al. At least, I had a crash course on Rc, RefCell, Arc, RwLock and Mutex in Rust

Yeah it's not an optimal solution.... I think I'll just merge your PR. This solution should be good in the meantime though.
Also it might be a good idea to squash the PR as it reduces its noise. And remove the LICENSE-BSD file :).

Yeah it's not an optimal solution.... I think I'll just merge your PR. This solution should be good in the meantime though.
Also it might be a good idea to squash the PR as it reduces its noise. And remove the LICENSE-BSD file :).

Yeah it's not an optimal solution.... I think I'll just merge your PR. This solution should be good in the meantime though.
Also it might be a good idea to squash the PR as it reduces its noise. And remove the LICENSE-BSD file :).

Re LICENSE-BSD, some of the passthrough-decoder comes a bit from the "writer.rs", so I can do as you prefer

Yeah it's not an optimal solution.... I think I'll just merge your PR. This solution should be good in the meantime though.
Also it might be a good idea to squash the PR as it reduces its noise. And remove the LICENSE-BSD file :).

Re LICENSE-BSD, some of the passthrough-decoder comes a bit from the "writer.rs", so I can do as you prefer

Thanks! Consider my case with the LICENSE-BSD file rested.

Thanks! Consider my case with the LICENSE-BSD file rested.

Thanks!

Thanks!

@sashahilton00 @plietar - this patch is now ready for consideration. I can update it if you want to integrate the latest version of @est31 https://github.com/RustAudio/ogg who kindly incorporated my patch, but it's not mandatory, I've found a workaround using Rc/Arc+RefCell/Mutex/FwLock.
That would be really great to have that option native to help the Spotty project!
Thanks

@sashahilton00 @plietar - this patch is now ready for consideration. I can update it if you want to integrate the latest version of @est31 https://github.com/RustAudio/ogg who kindly incorporated my patch, but it's not mandatory, I've found a workaround using Rc/Arc+RefCell/Mutex/FwLock.
That would be really great to have that option native to help the Spotty project!
Thanks

@sashahilton00 - any opinion on this new "Ogg Direct" implementation? Any chance to get it merged?
The tests might need some tweaking.

@sashahilton00 - any opinion on this new "Ogg Direct" implementation? Any chance to get it merged?
The tests might need some tweaking.

I'm happy to merge this, but someone needs to test it to make sure it's all ok, since I have nothing that uses pass through. Additionally, now that the ogg patch has been merged upstream, it would be good if that were used instead, since we're trying to minimise the amount of audio related logic that happens within librespot itself.

I'm happy to merge this, but someone needs to test it to make sure it's all ok, since I have nothing that uses pass through. Additionally, now that the ogg patch has been merged upstream, it would be good if that were used instead, since we're trying to minimise the amount of audio related logic that happens within librespot itself.

I've done tests on my side prior submitting PR. I'm happy to use the updated Ogg version, as long as it is synchronized with librespot (pointing to that version). I'll also commit to maintain & support these changes

I've done tests on my side prior submitting PR. I'm happy to use the updated Ogg version, as long as it is synchronized with librespot (pointing to that version). I'll also commit to maintain & support these changes

Sounds good, feel free to make the necessary changes and update the PR. It looks like you might need to rebase or otherwise update the Cargo.lock file, since it's failing CI tests currently

Sounds good, feel free to make the necessary changes and update the PR. It looks like you might need to rebase or otherwise update the Cargo.lock file, since it's failing CI tests currently

Ok, will do. I've contacted @est31 to see if he agrees to tag a new release so that we can point "officially" at it

Ok, will do. I've contacted @est31 to see if he agrees to tag a new release so that we can point "officially" at it

@philippe44 new release is out!

@philippe44 new release is out!

Closed for the benefit of https://github.com/librespot-org/librespot/pull/569

Closed for the benefit of https://github.com/librespot-org/librespot/pull/569

@philippe44 new release is out!

Thx!

@philippe44 new release is out!

Thx!


not working error segmentation fault

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x61972b]
goroutine 56 [running]:
main.getParams({0xc0000e8000, 0x8b}, 0x5, {0x6788da, 0x1}, {0x6788da, 0x1})
/root/tools/Jeeves/jeeves.go:183 +0x4eb
main.main.func1()
/root/tools/Jeeves/jeeves.go:114 +0x28c
created by main.main
/root/tools/Jeeves/jeeves.go:91 +0x29d

hey man
could you send me a screenshot of your usage?

cat txt | Jeeves --payload-time 5
On Sun, Apr 17, 2022, 8:25 PM ferreiraklet @.***> wrote:

hey man
could you send me a screenshot of your usage?
—
Reply to this email directly, view it on GitHub
https://github.com/ferreiraklet/Jeeves/issues/4#issuecomment-1100944430,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFT6C5TWGZ257T3KTLTK2GDVFRXSNANCNFSM5TUKY7GA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I did a little changing in main.go, can you reinstall it and try again?

not working yet, same error

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x61962b]
goroutine 12 [running]:
main.getParams({0xc0001623c0, 0x94}, 0x5, {0x6788da, 0x1}, {0x6788da, 0x1})
/root/tools/Jeeves/jeeves.go:183 +0x4eb
main.main.func1()
/root/tools/Jeeves/jeeves.go:114 +0x28c
created by main.main
/root/tools/Jeeves/jeeves.go:91 +0x29d

Hey, i would like to discuss the issue in discord, could we do that?
I want to solve this issue as soon as possible
Thank you for your report

Sorry for any troubles guys
I now what is happening, im solving this issue ok?
Will be back with some information later.

Ok, I just posted a new main.go
I ask you guys for please test again
But keep in mind: Jeeves does not http probing, he cant do requests to urls that does not contain protocol ( http://, https:// )


how to achieve aliasMapping?

Since aliasMapping is deprecated, how does one make an "alias" for a directory? For example, previously you could do the following:
{
  app: {
    src: [
      'app/**/*.js'
    ],
      dest: 'public/site.js'
    },
    options: {
      aliasMappings: [{
        cwd: 'app/',
        src: [ '**/*.js' ],
        dest: 'app/'
      }]
    }
  }
}

now with aliasMappings gone, when I try to build I get errors like >> Error: module "app/router" not found from - What is the correct way to do this in the latest version of grunt-browserify?

@kacinskas I need to upgrade browserfiy at this point... I've tried your solution but I'm getting:
>> Error: write after end
Warning: Error running grunt-browserify. Use --force to continue.

any ideas why this might happen?

@mikepuerto this is a problem with remapify and Browserify >7. I'm working on a fix https://github.com/joeybaker/remapify/issues/24

@mikepuerto I had to fix on package versions.
Im now on old versions of<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I did not tryied what last working versions are, so cant advice, probably - Browserify >7 and remapify>1.4.3

@kacinskas what version of grunt-browserify are you using? I tried downgrading the packages to the versions you mentioned above but grunt-browserify is apparently still using browserify 8 internally.
Thanks!

@kacinskas I actually went back to v3.2.1 and it seems better... still running into issues though(too many open files), would you mind sharing one of your target config sections?

@mikepuerto yes<EMAIL_ADDRESS>regarding "too many open files" - is from your system's ulimit open files setting, https://github.com/gruntjs/grunt-contrib-watch see FAQ


[9.4.x] ISPN-12471 Fix CI OOM

https://issues.redhat.com/browse/ISPN-12471

The tests haven't finished yet, but the distribution was already built. Integrating, thanks Pedro!


Update names of the different groups of CDH

Change Digital Humanities Lab and Utrecht Data School to Research Software Lab and Data School, respectively.

I don't think these are mentioned within the Ethics portal ...


Another option to solve [COOK-4434]

don't update the motd-tail every run

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

@jassinpain

Please sign the CLA here.

Apologies for the late reply to your pull request @jassinpain. We appreciate your contribution. We've gone ahead and modified the cookbook template to not add a timestamp which resolved [COOK-4434] so we won't be accepting this pull request. Thanks so much!


suggestions submenu obstructs selection

While typing in the field of a website forum, the suggestion menu of previous entries will pop below, obstructing half of the field area. Furthermore it's obstructing any ability to mouse over and select any of the typed text.
I would suggest dropping it lower 8-16px

It's a complicated issue because there's invisible padding around the menu to allow the use of a drop shadow (Firefox's menus, popups, and panels are handled differently to other elements and can't have visible overflow so the conventional drop-shadow doesn't work without applying it to a child and padding out the parent by the shadow radius). This invisible padding is blocking mouse events but I don't think pointer-events: none resolves the issue.
I can probably offset the menu so that it at least doesn't visually obstruct the text but there may still be problems due to it blocking point events in the drop-shadow area.

this can obscure things. It would be great if it could at least be moved below dropdown box :3


chore: bump dep versions

Description
Takes care of:

#71
#81
#83

Closing for now as all of the dependency are intimately related to ref-fvm and the work is not a priority for now


Add CodeTriage badge

Fixes #31 by adding CodeTriage badge in Readme.

@PierrePIRONIN  thanks for your contribution


Average time

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes issue https://github.com/roocs/rook/issues/193

[x] Tests for the changes have been added (for bug fixes / features)
[x] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)

What kind of change does this PR introduce?:
Adds average_time in clisops.core and clisops.ops and tests.

Does this PR introduce a breaking change?:
No

Only a question ... do we want to remove average_over_dims in the next release? Or is it useful on its own?

@cehbrecht @agstephens I think we said to remove it at some point, I can do that in a new PR if we are ready to remove it?


[WIP] Feature cra boomerang template

Add Boomerang CRA template
New
Added it

Close in favor of https://github.com/boomerang-io/webapp-packages/pull/22


Gateway API new-user

In Gateway API
Acceptance Criteria
POST /new-user -> with email and password
On success returns {SpotObject}
Approach

Use superagent within the gateway API to create ReST API calls to the other API

@rouge888 @vincent12322 Sprint due 4/11

#94

#94


ci.yaml validation is hanging for too long.

flutter engine PRs are only run through handful of checks now - only one build_and_test_linux_unopt_debug is run versus over 20 build runs just a few days ago.
See https://github.com/flutter/engine/pull/34226 for example.

I am seeing this issue on many framework and engine PRs, so bumping this to P0 since everything is blocked.

Cocoon has been switched to an earlier version. An empty commit push should unblock the PRs.

The culprit is https://github.com/flutter/cocoon/pull/1917, which incorrectly used default builder url instead of build url for builds related RPCs.
BuildBucketException: [501]: Not Implemented

#0      BuildBucketClient._postRequest (package:cocoon_service/src/service/buildbucket.dart:80:5)
<asynchronous suspension>
#1      BuildBucketClient.batch (package:cocoon_service/src/service/buildbucket.dart:118:36)
<asynchronous suspension>
#2      LuciService.getBuilds (package:cocoon_service/src/service/luci.dart:190:41)
<asynchronous suspension>
#3      LuciService.getBuildsForBuilderList.<anonymous closure> (package:cocoon_service/src/service/luci.dart:121:49)
<asynchronous suspension>
#4      RetryOptions.retry (package:retry/retry.dart:131:16)
<asynchronous suspension>

Earlier version is in use, and forward fix is in: https://github.com/flutter/cocoon/pull/1927


Growth of the que_jobs_args_gin_idx index

Hi! 👋
We're seeing an uncontrolled growth of the que_jobs_data_gin_idx index and wonder if anyone else has seen this or has remedies.
We're using que within Rails, wrapped with ActiveJob on Postgres 10.7.
This weekend we performed VACUUM FULL of our que_jobs table as que_jobs_args_gin_idx grew up to 4GB and we noticed autovacuum was struggling. The autovacuum would run for 25 minutes, take a minute nap and then run again. By the time it would run again it would already have thousands of dead rows to clean up.
The VACUUM FULL has helped a lot: the autovacuum seems to run fast enough (I can't see how fast it's running, suddenly it doesn't appear in logs, but I can see that the timestamp of last autovacuum updates frequently). There are only hundreds of dead rows now to clean up.
The table is now at the stable size (around 1.8MB), but the que_jobs_args_gin_idx index seems to grow daily. 15h after VACUUM FULL it grew to 14MB, morning after it was already 30MB and 4 days later it's at 74MB. The que_jobs_data_gin_idx is only 120kB.
I'm starting to believe this could be a PG bug and doesn't have anything to do with que. I guess I'm still curious if anyone else has seen this happen in their setup and if there's a remedy?
We're considering to rebuild the index nightly, or even dropping it completely, as index is 10 times the size of the table itself in less then 24h so nightly rebuilds might not have any effect.

Hi @sidonath -
I haven't experienced this before or heard of anyone experiencing it. It's possible that it's a PG bug, or that PG's gin indexes just don't handle the insert/delete churn as well as the b-tree indexes do, and you could be the first to run into this because you're a very high throughput user?
A few ideas:

PG offers a gin_clean_pending_list function, I forget the invocation details but I believe you could call it in Postgres like SELECT gin_clean_pending_list('que_jobs_args_gin_idx'::regclass). If the index bloat is coming from row churn inflating the GIN pending list, then running that regularly might help you with your bloat.
Quickly scanning the docs on that index type, it seems like if that works you could also try disabling the fastupdate option on those GIN indexes. That disables the pending list optimization, so that writes to the job table would be (probably not noticeably) slower, but you wouldn't have to run that function repeatedly.
If that doesn't help then depending on what you're doing, you could just consider dropping those two indexes. They're meant to speed up queries for jobs with certain args/tags, but Que doesn't execute any queries like that just by working jobs - they're for if you're using the by_args and by_tag query helpers to query the jobs table. But if you're not doing that then there's not really any point in keeping them.

Let me know how it works out!

Hi @chanks, thanks for the prompt response!

PG offers a gin_clean_pending_list function,

Right, I actually tried this, but it returned "4" (number of pages removed from the pending list) and there was no visible change in the index size.

Quickly scanning the docs on that index type, it seems like if that works you could also try disabling the fastupdate option on those GIN indexes.

Haha, I was planning to that as an experiment! Thanks for validating the idea 😄 Then again, after not seeing a benefit in calling gin_clean_pending_list, I got a bit more skeptical.

but Que doesn't execute any queries like that just by working jobs

Excellent! We might just do that, then!
I'll try to upgrade to Postgres 11 first, will see if that helps in any way and report here.
Thank you very much for the ideas!

I just wanted to follow-up on this: we've upgraded to PG11, but that didn't seem to prevent waste growth. We've turned off fastupdate, but 72h after that the waste is already at 175MB.
When the waste accumulates (and we've had up to 4GB waste recently) the queries to schedule jobs start timing out (we've got 250ms statement timeout configured). We're going to drop this index, as we don't use it at all.


Error when files get staged

Description
Getting the following error when files are staged (via fugitive):
Error executing vim.schedule lua callback: ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:75: The coroutine failed with this message: ...pack/packer/start/gitsigns.nvim/lua/gitsigns/manager.lua:296: Fa
iled to rename buffer
stack traceback:
        [C]: in function 'nvim_buf_set_name'
        ...pack/packer/start/gitsigns.nvim/lua/gitsigns/manager.lua:296: in function 'handle_moved'
        ...pack/packer/start/gitsigns.nvim/lua/gitsigns/manager.lua:340: in function <...pack/packer/start/gitsigns.nvim/lua/gitsigns/manager.lua:304>
stack traceback:
        [C]: in function 'error'
        ...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:75: in function <...e/pack/packer/start/gitsigns.nvim/lua/gitsigns/async.lua:70>

Neovim version
NVIM v0.7.0
Operating system and version
macOS 12.4
Expected behavior
No errors
Actual behavior
Errors
Minimal config
vim.o.packpath = '/tmp/nvim/site'

local plugins = {
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/pack/test/start/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

Steps to reproduce
Not really sure here, happens after some amount of work and then staging files. My assumption is some files have either been deleted or renamed and that triggers this
Gitsigns debug messages
No response

This will be difficult to resolve without repro steps.
I've looked into the Neovim source and this error mostly only happens when a BufFilePre autocmd runs, either if it changes the current buffer, or another error occurs. Another case this error happens is when the filename we are changing to already exists.

Recently I got this error frequently, I was refactoring several scripts, and every time I had deleted or moved files. It happens exatly when you press s to stage the file.
Error executing vim.schedule lua callback: ...nvim/site/pack/all/start/gitsigns/lua/gitsigns/async.lua:67: The coroutine failed with this message: ...im/site/pack/all/start/gitsigns/lua/gitsigns/manager.lua:297: Failed to rename buffer
stack traceback:
        [C]: in function 'nvim_buf_set_name'
        ...im/site/pack/all/start/gitsigns/lua/gitsigns/manager.lua:297: in function 'handle_moved'
        ...im/site/pack/all/start/gitsigns/lua/gitsigns/manager.lua:341: in function <...im/site/pack/all/start/gitsigns/lua/gitsigns/manager.lua:305>
stack traceback:
        [C]: in function 'error'
        ...nvim/site/pack/all/start/gitsigns/lua/gitsigns/async.lua:67: in function <...nvim/site/pack/all/start/gitsigns/lua/gitsigns/async.lua:62>

Its kind of annoying, so I'll try to find a way to reproduce it.

Its tricky, but I somehow understood the conditions for this bug to happen.

The buffer of a file that was deleted or moved must be still open in nvim AND not updated (showing the old contents)
Stage/unstage a file using the :G window from vim-fugitive

Once you raise the error, you can repeat it endlessly by repeatedly unstaging and staging from :G window.
Steps:
git init
echo "some text" > file1
nvim file1  # Do nothing, just quit
<Ctrl + Z>
git add . && git commit -m "first commit"
mv file1 file2
fg

Then keep both file1 and file2 in different windows. It is important that file1 is still opened and that the old contents are still being shown (do not :e on it).
Press :G and stage/unstage the files.

Note: When I raised this error in my refactoring, the deleted file's window wasn't really open, but vim keeps the buffer opened even if it is not being shown in a window, so... If programming for a long time and you removed some files that are still open in nvim, you will see the error.

I just tried the above steps and was unable to reproduce.

I recorded a GIF reproducing the bug.
https://i.imgur.com/mXi6rFW.gifv

Sorry, but the gif isn't very helpful.
Please provide a minimal config and exact steps as outlined by the issue template.

OK here we go.
This is a detailed step-by-step with a minimal configuration.
1. Clean configuration
Cleaned all the nvim configuration I have.
rm -f ~/.config/nvim/init.vim
rm -rf ~/.local/share/nvim/site/*
rm -rf ~/.config/nvim/*

2. Clone vim-fugitive and gitsigns.nvim
mkdir -p ~/.local/share/nvim/site/pack/all/start
cd ~/.local/share/nvim/site/pack/all/start
git clone https://github.com/tpope/vim-fugitive.git
git clone https://github.com/lewis6991/gitsigns.nvim.git

3. Add gitsigns.nvim config
mkdir ~/.local/share/nvim/site/plugin
nvim ~/.local/share/nvim/site/plugin/gitsigns.lua

gitsigns.lua content:
require('gitsigns').setup({})

Then go repeat the steps I described in https://github.com/lewis6991/gitsigns.nvim/issues/571#issuecomment-1147239899 and showed in the GIF.

That is not a minimal config, that is just your config.

Please provide a minimal config and exact steps as outlined by the issue template.

Place your minimal config here by following the instructions in the comments.
vim.o.packpath = '/tmp/nvim/site'

local plugins = {
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/pack/test/start/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE

And provide steps that involve the above config (edited with what is required) which can then be run with nvim --clean -u minimal.lua.

I was about to send the configuration now, sorry for not noticing you wanted in that format.
You wrote it already and it is probably unnecessary, but I just reproduced the bug with this config:
vim.o.packpath = '/tmp/nvim/site'

local plugins = {
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  vimfugitive = 'https://github.com/tpope/vim-fugitive'
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/pack/test/start/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
}

Thank you for taking your time to fix this bug. Hope you have a good day.

I've attempted to fix this in #672. @Yutsuten could you please test this?


Fix saving stl

STL files were not saved under right path
save_stl was passing file path to stl save_func and was using filename as file path
I've also renamed filename to path to avoid confusing it with name written into files

Thanks for your contributing


Gondola is not Finnish enough

Description
pls help, i have problem :DDDDD
i are become gondola to bartiotism (🇫🇮🇫🇮) bud id is silenced
dis issue is for tracking burboses and needs no ebin gamer attention :DDDDDDD
Reproduction

speak

Screenshots
N/A
Additional context
Fixable by adding an intermediate gondola accent for when you eat any gondola meat (to mimic SS13 behavior, but with some spice). The mechanic doesn't yet exist but it's part of the issue anyway.

:DDDDDDDDDDDDDDDDD

what


Uncaught Error: dlopen(/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom....

[Enter steps to reproduce:]

...
...

Atom: 1.54.0 x64
Electron: 6.1.12
OS: Unknown macOS version
Thrown From: Atom Core
Stack Trace
Uncaught Error: dlopen(/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app.asar.unpacked/node_modules/keyboard-layout/build/Release/keyboard-layout-manager.node, 1): image not found
At electron/js2c/asar.js:138

Error: dlopen(/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app.asar.unpacked/node_modules/keyboard-layout/build/Release/keyboard-layout-manager.node, 1): image not found
    at process.func (electron/js2c/asar.js:138:31)
    at process.func [as dlopen] (electron/js2c/asar.js:138:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:828:18)
    at Object.func (electron/js2c/asar.js:138:31)
    at Object.func [as .node] (electron/js2c/asar.js:147:18)
    at Module.load (internal/modules/cjs/loader.js:645:32)
    at Function.Module._load (internal/modules/cjs/loader.js:560:12)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:16:16)
    at customRequire (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:1:696987)
    at get_KeyboardLayoutManager (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:14:2796761)
    at get_manager (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:14:2796863)
    at Object.getCurrentKeyboardLayout (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:14:2796989)
    at e.keystrokeForKeyboardEvent (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:14:1057808)
    at KeymapManager.keystrokeForKeyboardEvent (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:11:1228079)
    at KeymapManager.handleKeyboardEvent (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:11:1226064)
    at WindowEventHandler.handleDocumentKeyEvent (/private/var/folders/8n/8wj39j3x0gx6h_w8lfczmj7h0000gn/T/wzQL.V2m3vl/Atom.app/Contents/Resources/app/static/<embedded>:11:284879)

Commands
     -2:00.1.0 application:reopen-project (div#add-projects-view.)
     -0:49.9.0 core:save (ul.list-inline.tab-bar.inset-panel)
     -0:38.6.0 application:add-project-folder (ul.list-inline.tab-bar.inset-panel)
  2x -0:22.8.0 core:paste (ul.list-inline.tab-bar.inset-panel)

Non-Core Packages

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/21285. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


IPs or SIPs?

Requirement 16.	 If the “submission” folder contains one or several sub-folders, the sub-folders MUST contain IPs.

Should it be IPs or SIPs?

Here it is IP because it must be an information package which is compliant with the common specification, it does not have to be an SIP according to the SIP specification.


Clean up redundant code

Removes unused using statements in deprecated code files.
Removes unnecessary implementations of Set(Color).
General clean-up of redundant code.

Looks nice and clean, good stuff. :+1:


[RCD-46] fix Prefiltering not ignoring txIds from Inputs

Porting input-output-hk/cardano-sl#3855.
Have not been able to run Daedalus to verify anything yet.
Checklist

[x] I've kept this PR simple, on-the-spot, free of cosmetic changes.
[x] I have reviewed my commit messages and history.
[x] I've assigned a reviewer.
[x] I acknowledge my changes may require an update in the wiki.
[ ] I have added a reference to this PR to the corresponding issue.

[ ] I've checked the checklist

Pull Request Test Coverage Report for Build 85

15 of 21 (71.43%)  changed or added relevant lines in 1 file are covered.
8 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.02%) to 49.943%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Cardano/Wallet/Kernel/PrefilterTx.hs
15
21
71.43%

Files with Coverage Reduction
New Missed Lines
%

src/Cardano/Wallet/API/V1/Types.hs
2
32.79%

src/Cardano/Wallet/Kernel/PrefilterTx.hs
6
82.42%

Totals

Change from base Build 81:
0.02%

Covered Lines:
3969

Relevant Lines:
7947

💛  - Coveralls

The code from PrefilterTx has become quite chaotic (worry not, this PR isn't only in cause)

Yes, I felt that and that I didn't help either :) (Didn't understand enough of it to know what could be done though)

and would deserve some thoughts and refactoring

👍


Fix: Use appropriate sections for Travis configuration

This PR

[x] uses appropriate sections to run things during the Travis build

💁♂ Also adds a bit of vertical whitespace for enhanced legibility! For reference, see https://docs.travis-ci.com/user/job-lifecycle/#the-job-lifecycle.

Thanks @localheinz!

Thank you, @iluuu1994!


updating Netskope Data Connector to migrate from v1 API to v2 API

Required items, please complete
Change(s):

Updating Netskope Data Connector to support V2 API over Deprecated V1 API
Updated Az Module used and PWSH version/function runtime support for current versions in Azure
updated the references for logtype for consistency

Reason for Change(s):

Netskope V1 API is deprecated and its tokens only have 90d lifetime causing maintenance headachs

Version Updated:

N/A

Testing Completed:

Yes
Running against a production tenant, validated no change in data coming into sentinel vs old API
Tested in a clean Sentinel Instance with no other configs except the Netskope solution installed

Checked that the validations are passing and have addressed any issues that are present:

See guidance below
Yes

@microsoft-github-policy-service agree


Update init containers example from alpha to beta

The doc wording and the example are inconsistent.

This change is

I signed it!


Load variables in chunks

This PR adds support for the variable paging capability.
Large numbers of child variables (typically long lists, vectors etc.) are not shown all at once, but in chunks of 100 variables that are loaded only if requested.
Currently attributes and normal child variables are treated equally, in the future it might make sense to treat these differently to always show attributes and only load list elements in chunks.

Thanks for working on this. It works nicely in most cases.
I find it a little misleading in the following case though:

The metadata (attributes) look like some elements of the object too.
And sometimes, expanding a chunk will result in the following error:
Error in if (id > 0) { : missing value where TRUE/FALSE needed

The metadata (attributes) look like some elements of the object too.

Yeah I've noticed that, too. I think I know how to fix this, I'll update the PR when I figure it out (or give up on it)

And sometimes, expanding a chunk will result in the following error:

Thanks for the note, I'll look into it. I haven't encountered this error yet, so if you know how to reproduce it please let me know!

Thanks for the note, I'll look into it. I haven't encountered this error yet, so if you know how to reproduce it please let me know!

Can't reliably reproduce it at the moment. It occurs occasionally when I expand a chunk and I wait for too long and then the error message shows up.


[Feature] Address Search

The abiliy to search for an address to determine whether it belongs to your wallet would be useful.

Ideally across all accounts within a wallet e.g. Deposit, Premix, Postmix & Bad Bank
Ideally partial searches

+1
Electrum has an indexed search of every address and TXID.


cf test runs "inx.txt" instead of my code

Hi, thanks for this great tool! On Archlinux, I copy cf into my ~/bin. Then do cf config add and add my template (python). Then cf parse 456 a and cd 456/a. Manually create pr.py file. And on cf test it fails with this:
[art@arch-pc a]$ ls
ans1.txt  in1.txt  pr.py

[art@arch-pc a]$ cf test
  File "<stdin>", line 2
    1 2
      ^
SyntaxError: invalid syntax
Runtime Error #1 ... exit status 1

Config: cat ~/.cfconfig:
[art@arch-pc a]$ cat ~/.cfconfig
{
  "username": "xxx",
  "password": "xxxx",
  "template": [
    {
      "alias": "py",
      "lang": "31",
      "path": "/home/art/.codeforces/template.py",
      "suffix": [
        "py"
      ],
      "before_script": "",
      "script": "python3",
      "after_script": ""
    }
  ],
  "default": 0
}

Template:
[art@arch-pc a]$ cat ~/.codeforces/template.py
#!python3

from collections import deque, Counter
import array
from itertools import combinations, permutations
from math import sqrt
import unittest

def read_int():
    return int(input().strip())

def read_int_array():
    return [int(i) for i in input().strip().split(' ')]

######################################################

Thanks for your feedback~
You can found the reason in usage
Script in template:
  Template will run 3 scripts in sequence when you run "cf test":
    - before_script   (execute once)
    - script          (execute the number of samples times)
    - after_script    (execute once)
  You could set "before_script" or "after_script" to empty string, meaning not executing.
  You have to run your program in "script" with standard input/output (no need to redirect).

  You can insert some placeholders in your scripts. When execute a script,
  cf will replace all placeholders by following rules:

  $%path%$   Path to source file (Excluding $%full%$, e.g. "/home/xalanq/")
  $%full%$   Full name of source file (e.g. "a.cpp")
  $%file%$   Name of source file (Excluding suffix, e.g. "a")
  $%rand%$   Random string with 8 character (including "a-z" "0-9")

You should put a placeholder into your configuration.
Just modify your ~/.cfconfig  like this:
"script": "python3 $%full%$",

Solved! Thanks :)


Adapt the install script for Raspi4 USB mass storage boot, and regenerate the image

I'm trying to use the installer with a Raspberry 4B, and I want to install and run the OS on a SSD drive connected to USB (no SD card inserted).
Before September 2020, the process was complex and not all the SSD were supporter, but after September, a change in the Raspi4 EEPROM simplified a lot the process (source)
The current raspberrypi-ua-netinst release v2.4.0+ (caf7423), only takes into account the USB mass storage boot for devices up to Raspi3B.
In fact:

I had to manually run update.sh script to download latest .elf .img and .dat files, with a kernel supporting these EEPROM changes and more updated drivers for wifi
I created a new release of raspberrypi-ua-netinst, using the build.sh script, to use these new files
I transferred all the files on a SD card as usual, and set usbboot=1 and usbroot=1 in the installer-config.txt
I rebooted the Raspi4 with the SD inserted and the SSD connected to USB, and launched the install process. Everything works as expected, but unfortunately the install.sh script fails, as line 776 checks if the device can boot from USB using the command "vcgencmd otp_dump", that is not supported on Raspi4.
If I comment all the lines in install.sh from 776 to 790, the installer works as expected and copies both boot and root files in the SSD.

Prior of doing that, I manually updated the EEPROM of my Raspi4 to past Aug 20 2020 version, and configured it to boot from USB using these instructions (installed Raspberry Pi OS 2020-08-20 or newer, performed a apt full-upgrade, run rpi-config and selected SD/USB (default) as boot mode), to be sure to have USB boot enabled and working.

Can you help by checking an upcoming release candidate?