$update not being triggered/called

I was hoping that this code example would trigger the $update function but it does not.  Notice that I'm using the variable found in $init and not querying for the element.
Would it be possible to add this?
Is this by design?
https://gist.github.com/snaveevans/2c1a03abc9cc75d8834e14c33f0c5a1a

Yes that's by design.
Note that these variables on their own are literally just variables. So for example if you write:
var app = {
  $cell: true,
  $text: "app"
}

Cell uses this variable to construct the DOM, but it doesn't just magically re-assign the generated node into the variable app. Here's why it doesn't work this way:
The flexibility of Cell means you can write as many variables as you want but at the end of the day the only variable that gets turned into a node is the one with the $cell attribute set to true.
And these variables can utilize other variables to define themselves. For example:
var component = function (options) {
  return {
    $type: "a",
    href: options.url,
    _alert: function(t) { alert(t); },
    onclick: function(e) { this._alert(options.text); },
    $text: options.text
  }
}
var app = {
  $cell: true,
  $components: [{
    url: "https://www.google.com", text: "Google"
  }, {
    url: "https://www.twitter.com", text: "Twitter"
  }, {
    url: "https://www.github.com", text: "Github"
  }].map(component)
}

Now let's imagine for a moment what you were asking was possible. How would that work? If you try to call component._alert("hello");, what would that component be pointing to? (There are 3 nodes generated from the variable component).
This is why by design you can't use the original gene object to refer to the node. In fact if you do console.log on the variables, it will print out the same original variable, not the generated node.
To query the nodes, you should use document.querySelector or any other native DOM selection APIs and go from there.
That said, I do understand where you're coming from (there's gotta be a cleaner way than calling document.querySelector every time) and still thinking about ways to deal with this problem. If you have ideas please feel free to share.


Unresolved dependencies

On Ubuntu, I cloned this GH repo: https://github.com/aspnet-contrib/AspNet.Security.OpenIdConnect.Server
I did . mono-snapshot mono/2015.06.16+09.38.12' I did dnvm use 1.0.0-beta6-12004`, then DNU restored all depedencies in the folders:
src/AspNet.Security.OpenIdConnect.Extensions
src/AspNet.Security.OpenIdConnect.Server
samples/Mvc/Mvc.Client
samples/Mvc/Mvc.Server
In samples/Mvc/Mvc.Server and samples/Mvc/Mvc.Client I ran dnx . kestrel.
Everything works fine.
When I open the root folder of the project in ATOM with omnisharp-atom 0.17.3 installed, it tries to restore packages and fails with:
Unresolved dependencies for AspNet.Security.OpenIdConnect.Server:
 - Microsoft.AspNet.Authentication 1.0.0
 - Microsoft.Framework.Caching.Abstractions 1.0.0
 - Microsoft.Framework.Logging.Abstractions 1.0.0
 - Microsoft.Framework.NotNullAttribute.Sources 1.0.0
 - Microsoft.Framework.WebEncoders.Core 1.0.0
 - Microsoft.IdentityModel.Protocol.Extensions 2.0.0
 - Newtonsoft.Json 6.0.4
 - System.IdentityModel.Tokens 5.0.0

Unresolved dependencies for AspNet.Security.OpenIdConnect.Extensions:
 - Microsoft.IdentityModel.Protocol.Extensions 2.0.0

Unresolved dependencies for Mvc.Server:
 - EntityFramework 7.0.0
 - EntityFramework.InMemory 7.0.0
 - Kestrel 1.0.0
 - Microsoft.AspNet.Diagnostics 1.0.0
 - Microsoft.AspNet.Mvc 6.0.0
 - Microsoft.AspNet.Cors 1.0.0
 - Microsoft.AspNet.Authentication.Cookies 1.0.0
 - Microsoft.AspNet.Authentication.Google 1.0.0
 - Microsoft.AspNet.Authentication.OAuthBearer 1.0.0
 - Microsoft.AspNet.Authentication.Twitter 1.0.0
 - Microsoft.AspNet.Server.IIS 1.0.0
 - Microsoft.AspNet.Server.WebListener 1.0.0
 - Microsoft.AspNet.StaticFiles 1.0.0
 - Microsoft.Framework.Logging 1.0.0
 - Microsoft.Framework.Logging.Console 1.0.0
 - Microsoft.AspNet.Owin 1.0.0
 - Microsoft.Owin 3.0.0
 - NWebsec.Owin 1.0.0
 - Microsoft.IdentityModel.Protocol.Extensions 2.0.0
 - Microsoft.AspNet.Authentication 1.0.0
 - Microsoft.Framework.Caching.Abstractions 1.0.0
 - Microsoft.Framework.Logging.Abstractions 1.0.0
 - Microsoft.Framework.NotNullAttribute.Sources 1.0.0
 - Microsoft.Framework.WebEncoders.Core 1.0.0
 - Newtonsoft.Json 6.0.4
 - System.IdentityModel.Tokens 5.0.0

Unresolved dependencies for Mvc.Client:
 - Newtonsoft.Json 6.0.4
 - Kestrel 1.0.0
 - Microsoft.AspNet.Mvc 6.0.0
 - Microsoft.AspNet.Authentication 1.0.0
 - Microsoft.AspNet.Authentication.Cookies 1.0.0
 - Microsoft.AspNet.Authentication.OpenIdConnect 1.0.0
 - Microsoft.AspNet.Server.IIS 1.0.0
 - Microsoft.AspNet.Server.WebListener 1.0.0
 - Microsoft.AspNet.StaticFiles 1.0.0
 - Microsoft.Framework.Logging 1.0.0
 - Microsoft.Framework.Logging.Console 1.0.0

What am I doing wrong?

It could be the breaking change between beta4 and beta5 in terms of how it handles the project.lock.json file.  I'm not entirely sure.  @davidfowl any ideas?


Trouble installing on CentOS 8

Following the instruction to install poplog on CentOS 8 results in the following error:
Key imported successfully
Running transaction check
Error: transaction check vs depsolve:
libc.so.6 is needed by poplog-0.2.0-2.1.x86_64
libc.so.6(GLIBC_2.0) is needed by poplog-0.2.0-2.1.x86_64

A similar issue occurs under CentOS 7:
Running transaction check
ERROR with transaction check vs depsolve:
libc.so.6 is needed by poplog-0.2.0-2.1.x86_64
libc.so.6(GLIBC_2.0) is needed by poplog-0.2.0-2.1.x86_64
You could try running: rpm -Va --nofiles --nodigest
Your transaction was saved, rerun it with:
yum load-transaction /tmp/yum_save_tx.2021-08-03.16-12.hezWnp.yumtx

Installing glibc.i686 resolves the error on CentOS 7


Git LFS

I may be naive, consider this just a question.
This repo is using Git LFS for the lib.rs file. I can't review the changes in Git Gui or on GitHub, and have to manually diff against the copy of an older version. The reason is that LFS is primarily intended for large blobs of binary data.
What do we think about converting it to a regular Git file? And (maybe this is cursing) how about doing this conversion over the git history?

I think it's fine on text files anyway. I was probably too cautious when I did it.

Sounds like that would be an improvement.

Then I think the steps would be to remove branch protection from main for a moment, do git lfs migrate export --everything, and force push.
Documentation: https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.adoc.

Hmm, I think we should probably not rewrite history for this.


batch insert/upsert versus batch AQL insert/upsert: AQL is 100 to 2100 times slower?

Hi!
I'm currently trying to write data to ArangoDB to work with it in a later step.
I figured out that using AQL (insert/replace/upsert) in batches is significantly slower than importing it with the collection methods (insert_many, replace_many/import_bulk)
1000 inserts/replace/upsert via collection methods take roughly 0.03 seconds (number of shards is irrelevant)
1000 inserts/replace/upsert via AQL take roughly 6 seconds, when sharding (6 seconds * number of shards)
That means: Having 3 machines and the collection configured to utilize 9 shards the difference is 0.03 seconds to 1:05 minutes for 1000 insert/replace/update.

As server I'm using ArangoDB 3.1.20 on CentOS, sharded, 3 machines (shard_count set to either 1 or 9 in the example) and ArangoDB 3.1.21 on Ubuntu 16.04, 1 machine, no shards.
For the script I'm using the python-arango interface but this doesn't seem to matter, profiling the script shows that the long time is waiting for the REST answers.
A script showing that behaviour is attached for reference: slowaql.zip
Thanks
coldcoff
Here's the Form:
my environment running ArangoDB
I'm using the latest ArangoDB of the respective release series:

[ ] 2.8
[ ] 3.0
[x] 3.1
[ ] 3.2 pre-releases: ___
[ ] self-compiled devel branch

On this operating system:

[ ] DCOS on

[ ] AWS
[ ] Azure
[ ] own infrastructure

[x] Linux

[ ] Debian .deb
[x] Ubuntu .deb
[ ] SUSE   .rpm
[x] RedHat .rpm
[ ] Fedora .rpm
[ ] Gentoo
[ ] docker - official docker library
[ ] other:

[ ] Windows, version:
[ ] MacOS, version:

this is an AQL-related issue:
[ ] I'm using graph features
I'm issuing AQL via:

[ ] web interface with this browser:     running on this OS:
[ ] arangosh
[x] this Driver: python-arango, version 3.7.0

I've run db._explain("<my aql query>") and it didn't shed more light on this.
The AQL query in question is:
see attached script 'slowaql.py'
slowaql.zip
The issue can be reproduced using this dataset:
see attached script 'slowaql.py'
slowaql.zip
Please provide a way to create the dataset to run the above query on; either by a gist with an arangodump, or `db.collection.save({my: "values"}) statements. If it can be reproduced with one of the ArangoDB example datasets, it's a plus.
Foxx

this is a web interface-related issue: NO
I'm using the web interface with this browser:     running on this OS:

[ ] authentication is enabled?
[ ] using the cluster?
[ ] _system database?

These are the steps to reproduce:

open the browser on http://<IP_ADDRESS>:8529
log in as ...
use database [ ] _system [ ] other:
click to ...
...

Any news on that? At least a classification?

Its rather a question of perspective.
Its moreof that the import facility is massively faster than what you've used to progamatically insert data.
This can only be achieved by the import facility making certain assumptions which the AQL version can't take.
Thus we advice to use the import facility for bulk insert over using AQL queries like you did.
You can use arangoimp for this, or if you want to do something programatically use the API arangoimp also uses under the hood.
We'll give you a more detailed answer once the next ArangoDB 3.2 Beta release is done.

Thanks @dothebart.
For now I can work with import_bulk(), which is fast, so it's OK to wait for you to finish ArangoDB 3.2 beta first.
To document / illustrate the slowness see the following numbers, extracted differently from the very same script above:
a) ArangoDB 3.1.22, cluster setup (3 machines). collection with shard_count = 1 (!)

Elapsed 23.68531ms/1000 inserts
Elapsed 5850.9199ms/1000 AQLs

b) ArangoDB 3.1.22, no cluster setup (just one of the 3 machines as single DB). collection with shard_count = 1

Elapsed 16.20139ms/1000 inserts
Elapsed 364.672ms/1000 AQLs

c) ArangoDB 3.1.22, cluster setup (3 machines). collection with shard_count = 3

Elapsed 22.74879ms/1000 inserts
Elapsed 25556.0558ms/1000 AQLs

Hi,
I'm seeing some very weird slowdowns with AQL as well.
Version 3.1.22
My workload:

multiple HTTP batch requests /_api/batch
each batch consists of a mix of 5000

POST /_api/document/ to a vertex collection
POST /_api/document/ to an edge collection
AQL INSERT requests to add more edges to the edge collection

after all calls have returned: 130 000 vertices created, 561 000 edges created

The same workload executed in different conditions but always one shard, no replication:

single server setup: 	Data imported in 23 345ms
cluster setup with one agency, one coordinator, one primary server: 	Data imported in 624 020ms
cluster setup with one agency, one coordinator, one primary server BUT I removed the AQL calls: 	Data imported in 32 943ms

Clearly there's something wrong going on with AQL and clustering. From my point of view, it makes the clustering not scale horizontally at all.
I'm happy to provide more information if needed.

You can replicate it with arangobench
Cluster mode (one agency, one coordinator, one primary)
Total number of operations: 10000, runs: 1, keep alive: yes, async: no, batch size: 1000, replication factor: 1, number of shards: 1, wait for sync: false, concurrency level (threads): 10
Test case: aqlinsert, complexity: 20, database: '_system', collection: 'ArangoBenchmark'
Total request/response duration (sum of all threads): 271.256008 s
Request/response duration (per thread): 27.125601 s
Time needed per operation: 0.002781 s
Time needed per operation per thread: 0.027813 s
Operations per second rate: 359.540881
Elapsed time since start: 27.813249 s

Single server:
Total number of operations: 10000, runs: 1, keep alive: yes, async: no, batch size: 1000, replication factor: 1, number of shards: 1, wait for sync: false, concurrency level (threads): 10
Test case: aqlinsert, complexity: 20, database: '_system', collection: 'ArangoBenchmark'
Total request/response duration (sum of all threads): 6.498392 s
Request/response duration (per thread): 0.649839 s
Time needed per operation: 0.000074 s
Time needed per operation per thread: 0.000736 s
Operations per second rate: 13579.094760
Elapsed time since start: 0.736426 s

That's a 41x slow down.

@dothebart could you give us your opinion on this please ?

@dothebart Is there any updates on this issue?

you would probably better hilight @kvahed or @neunhoef on this case.

I have a requirement of bulk upload/insert of documents and need to create/update edges accordingly. Here we need to make sure that during this batch insert of documents and edges are not duplicates. So, the result of this operation should be idempotent and need me to use upsert in AQL. After around 6000 records, things start getting slow to a point where it feels it is stuck. Any update on this issue?

Hi all,
This ticket is being closed as inactive due to the date of the last activity on it.
If you believe this was done in error, please comment or create a new issue.


Fix panic on closed chan

Fixes #6
The channels associated with the command are closed on
each iteration through the for loop--so we need to
generate new channels each time through.
Signed-off-by: Phil Estes<EMAIL_ADDRESS>

Not sure this is the best way to fix, but since channels are associated with the command, not easy to come up with anything else without a larger re-work of these channels

Good catch :-) LGTM


Conditional Attributes

Currently I cannot use a @if conditional around a html attribute
<div @if(comment.parentComment() != null)
            x-init="$dispatch('${comment.parentComment().toString()}')"
        @endif
>

I get the following exception:
CommentComponent.jte, error at line 9: Illegal HTML attribute name @if(comment.parentComment()! @if expressions in HTML attribute names are not allowed. In case you're trying to optimize the generated output, smart attributes will do just that: https://jte.gg/html-rendering/#smart-attributes

I really would like to do that as I don't necessarily want to put my alpine.js code into my java code and instead put it into my template.

If the attribute value is null, it will be omitted, hope that helps.

If the attribute value is null, it will be omitted, hope that helps.

Yes I know that but I would need to put the if else in a ternary operator which is uglier imo.
@casid If you thinkg this is ok/possible I could take a crack at changing the behaviour. Or is there a certain reason why the behaviour is as it is?

@tschuehly this is because jte by default only allows writing into safe slots of a template. The parser expects to find an attribute name within this div. This needs to be done in order to decide how to escape the attribute content, which is a safe slot to write to. Having logical expressions in here would let the complexity of the parser explode, and also make it impossible to guarantee properly escaped templates.

@tschuehly this is because jte by default only allows writing into safe slots of a template. The parser expects to find an attribute name within this div. This needs to be done in order to decide how to escape the attribute content, which is a safe slot to write to. Having logical expressions in here would let the complexity of the parser explode, and also make it impossible to guarantee properly escaped templates.

Is there a way to extend the parser? So I could write a plugin where I could implement that behaviour?

No there is not. The parser is already quite complex and I fear opening this rabbit hole would make everything a lot harder to maintain, while the benefit to it is rather low. The risk on the other hand quite high, to accidentially introduce unsafe behavior or break user code.

How about using a special constant OMIT that would remove the attribute from the output if it is encountered? Similar to the poison pill pattern. Then you could write it like this.
<div x-init="comment.parentComment() == null ? OMIT : $dispatch('${comment.parentComment().toString()}')">

This constant already exists: null


Is it possible to add the "Audio device profile" option? Thank you.

Second this. Currently, audio device profile is tiny and tinny speaker. If I could use the profile made for large speakers, the sound would be a million times less robotic.
I've tried to download and install the developer version of this, but everything is broken and deprecated... Any links to still active alternatives to this are most welcome. Wavenet voices develop and advance all the time. This hasn't in 2 years.

Version 12 is pending Google's review. This should be possible when it updates (~1 to 3 business days).


missing tcp_nodelay sockoption

Hello,
thx for the cool implementation, it's working awesome for me. I want to speed up things a bit and discovered that you are missing to set the tcp_nodelay which causes a slow communication e.g. on echo like protocols.
I wrote a not good but working test.
And I miss todo the same for ssl, which i will do if i need the ssl part!
Thx
meno

Thank you for seeing this. Simple-Web-Server have this already, but I forgot to add this to Simple-WebSocket-Server as well. I would prefer that you make a pull request without the stripped line-ending spaces though, sorry. It would be easier to read the commit then in the future.
I agree that we should have a test similar to the examples' output, asserting that the messages and events are correct. One can use ::stop to stop the server after the tests has completed.

I added the tcp no_delay socket option for WS and WSS for both client and server in https://github.com/eidheim/Simple-WebSocket-Server/commit/f9cdbb70e03283c22d26c242098cb21eaed79d4e.

That looks cool,
Could you pull my test? Just to prevent it is gone? It not good but ....
Meno


Hide test transmitters from map

Sondehub backend added telemetry_hidden field for when payloads might want to be hidden from the frontend interfaces. These include test and misconfigured payloads.
https://github.com/projecthorus/sondehub-infra/issues/107

Wrong tracker


1143881 prefill

r?

To test by hand:

go to http://localhost:8000/feedback/?happy=0
pick a product, make sure you land on the more-info page
submit
make sure the resulting response is sad

Also this to make sure the user can override the prefill:

go to http://localhost:8000/feedback/?happy=0
pick a product and make sure you land on the more-info page
click on the browser back button and make sure you go back to the sentiment page
pick "happy"
fill out a description and submit
make sure the resulting response is happy

You can also run the smoketests, but if they're not working well for you then it's 3 minutes of noise.

Do you need to do something additional for FxOS since it's a separate form? It doesn't seem to handle it for me.

Other than that, this is working. If that is expected, r+

My bad--I should have mentioned that I didn't implement this for Firefox OS--just for all the non-Firefox OS products. I'm not sure this is necessary for Firefox OS, so I just left it out for now.

5eaa494 [bug 1143881] Add happy pre-filling via url
Thank you!


install prereqs on the devcontainer

fixes #75

Also added required env vars for copilot-hunter and tested within a container - should work out-of-the-box now.


Cannot install Spyder 3.3.4

Good morning.
I use Ubuntu MATE 18.04 and Python 2.7 and I cannot install Spyder 3.3.4 : I get an error :
pascal@EL1352:~$ pip install spyder==3.3.4
Collecting spyder==3.3.4
Using cached https://files.pythonhosted.org/packages/7c/ac/edaec8736d5425abe02eb5d177c7d342f1f725c6c737f81bc02433691c13/spyder-3.3.4-py2-none-any.whl
Collecting qtpy>=1.5.0 (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/14/a8/6145994bd4eb03f2bfe54a87665588891dacf2dd5e96ca6546cf16d76f45/QtPy-1.7.1-py2.py3-none-any.whl
Collecting pickleshare (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/9a/41/220f49aaea88bc6fa6cba8d05ecf24676326156c23b991e80b3f2fc24c77/pickleshare-0.7.5-py2.py3-none-any.whl
Collecting pyflakes (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/84/f2/ed0ffb887f8138a8fe5a621b8c0bb9598bfb3989e029f6c6a85ee66628ee/pyflakes-2.1.1-py2.py3-none-any.whl
Collecting spyder-kernels<1.0,>=0.4.3 (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/d5/f7/a7e25bc3034644fb915f57290969107c897bae2b57029c4368c0a907039f/spyder_kernels-0.4.4-py2.py3-none-any.whl
Collecting jedi>=0.9.0 (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/25/2b/1f188901be099d52d7b06f4d3b7cb9f8f09692c50697b139eaf6fa2928d8/jedi-0.13.3-py2.py3-none-any.whl
Collecting nbconvert (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/35/e7/f46c9d65f149271e47fca6ab084ef5c6e4cb1870f4c5cce6690feac55231/nbconvert-5.5.0-py2.py3-none-any.whl
Collecting pycodestyle (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/0e/0c/04a353e104d2f324f8ee5f4b32012618c1c86dd79e52a433b64fceed511b/pycodestyle-2.5.0-py2.py3-none-any.whl
Collecting rope>=0.10.5 (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/82/dc/3f8fe60b883796d14dc49526521d12c4d060f3ec971ca97f2f00051b88dc/rope-0.14.0-py2-none-any.whl
Collecting qtconsole>=4.2.0 (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/c7/45/1a50288305797fbca7c2039f9baefff1a9df603322874743fbb8408d8ec2/qtconsole-4.4.4-py2.py3-none-any.whl
Collecting pygments>=2.0 (from spyder==3.3.4)
Using cached https://files.pythonhosted.org/packages/6e/00/c5cb5fc7c047da4af049005d0146b3a961b1a25d9cefbbe24bf0882a11ad/Pygments-2.4.0-py2.py3-none-any.whl
Collecting pyqtwebengine<5.13 (from spyder==3.3.4)
Could not find a version that satisfies the requirement pyqtwebengine<5.13 (from spyder==3.3.4) (from versions: )
No matching distribution found for pyqtwebengine<5.13 (from spyder==3.3.4)
pascal@EL1352:~$
Do you know what can I do ?
Thank you.

This error will be fixed in our next release (3.3.5). For now please use Python 3 or Anaconda.


[ISSUE]Supported MySQL Versions

Describe the query
I want to know what are the supported versions of MySQL with acra-server in community edition?
To Reproduce
NA
Expected behavior
NA
Acra configuration files
NA
Environment (please complete the following information):

Acra version: [e.g. 0.90.0]

Database server and its version: MySQL

Installed components:

[x] AcraServer

Data-in-transit encryption between Acra and the client-side application:

[ ] TLS
[ ] AcraConnector
[ ] no transport encryption

Installation way:

[x] via Docker
[ ] via package manager

Sorry for so long response. We don't recommend to use Acra 0.90 version and I didn't tested it due to it uses old approach with secure session as transport and acra-connector as additional proxy between app and acra-server, that looks overcomplicated for modern deployments.
Our tests regularly test Acra with mysql 5.7.25 and 5.7.31. Additionally, I had tested with fresh 5.7 and 5.5 images from the docker hub with Acra 0.95.0 and transparent encryption/decryption works.
Unfortunately, Acra Community edition doesn't support properly mysql 8.X client's that use  CLIENT_QUERY_ATTRIBUTES at the wire protocol level. Mysql's CLI tool mysql uses it. We plan to bring it to the community addition in the next year.
How to detect that mysql driver uses CLIENT_QUERY_ATTRIBUTE? You will see next log from the acra-server:
acra-server_1           | time="2023-12-21T22:20:25Z" level=debug msg="ignoring error of non parsed sql statement" error="syntax error: unexpected LEX_ERROR at position 2 near '\x00'".

Thanks @Lagovas. I am using master branch (Commit: 3a65ebf206928f1eb69fe3177271632e4b56fb2f).


[WFCORE-6524] Do not duplicate managed deployment in content repository in tmp/vfs/temp directory

Issue: https://issues.redhat.com/browse/WFCORE-6524

Integration Jobs:
Linux: https://ci.wildfly.org/buildConfiguration/WF_WildFlyCoreIntegrationExperiments/392871
Windows: https://ci.wildfly.org/buildConfiguration/WF_WildFlyCoreIntegrationExperimentsWindows/392873

Could you add a test with an exploded deployment ?

@gaol FYI, I haven't looked at the reasons yet, but WildFly full PR fails with this one in place, look at the Linux Job, the one for Windows need more CI tweak.

Thanks @ehsavoie for the review, and thanks @yersan for the integration job setup.
I see a -Dversion.org.wildfly.core=22.0.0.Final-SNAPSHOT in the log, but my branch is still based on 22.0.0.Beta3-SNAPSHOT, I think that is the reason the fix is not picked up. I will rebase to latest main branch

@yersan done, hope it will work. I will be on holidays and PTO in the coming 2 weeks, I will back to this if there is other issue to fix :)

oohh, my fault with the Jobs configuration, I'll kick them off again. Enjoy your well-deserved PTOs.

Integration tests passed, thanks @gaol and @ehsavoie


Test GitHub Actions CI behaviour from a fork

Some builds from forks aren't running. This PR exists to investigate why that might be.

Closing this, as I believe #72 takes this forward.


Development: Replace usages of deprecated TestBed.get with TestBed.inject

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Client

[x] I followed the coding and design guidelines.
[x] I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.

Motivation and Context
TestBed.get is deprecated. The recommended direct replacement for it is TestBed.inject.
Description
Replaces all usages of the deprecated method with the recommended replacement. Also removes deprecated async from beforeEach methods.
Steps for Testing
Only test code changed ⇒ Code-review is enough.
Review Progress
Code Review

[ ] Review 1
[ ] Review 2

Test Coverage
unchanged

I've looked through all the changes and didn't find any mistake. Not much more to say other than LGTM 👍


Add custom header for each scan

so dev teams can recognize it's a zap scan

Added "X-Scanner: ZAP" header to each request in 6e5557c5fbe18597d1fe1b45d4058b5ed10358e7


Request Timeout after 30000ms while using es-import-bulk

Hi,
It lead to 408 error while I using es-import-bulk to import about 1500000 documents。
Details as below:
./es-import-bulk --url http://<IP_ADDRESS>:9200 --file /var/backup/elasticsearch/janus_remove/dev.data.json
Pre-Processing file of size: 2.12 GB
Starting bulk imports with batches of 20000 lines.
Processing line 15000 of 1500000 [--------------------] 1% 0.1s
  error: {"status":408,"displayName":"RequestTimeout","message":"Request Timeout after 30000ms"}

how can I fix this?
Waiting for your reply, thanks.

@myitroad I had a similar issue, except I received an error bulk endpoint /_bulk => socket hang up. After finding this elasticsearch-js issue, I upgraded the elasticsearch dependency in package.json to version 14.2.1 that incorporates the fix for the issue. After updating to the version with an npm install, it fixed my issue.


RDCC-2262 - removed log to check the time taken for executing methods

JIRA link
https://tools.hmcts.net/jira/browse/RDCC-2262
Change description
CRD - Remove the log added for time taken for executing methods and code for handling formula cell type
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X ] No

It is just minor code smell only but it is good to address this https://sonarcloud.io/project/issues?id=uk.gov.hmcts.reform%3Areform%3A%3Ard-caseworker-ref-api&pullRequest=347&resolved=false&types=CODE_SMELL

merging the code.


reuse port range for new worker if possible

this will minimize the need of opening new ports per worker

Currently
When delegating tests (and ports for those tests) to workers we start at BASE_PORT_START we increment by BASE_PORT_SPACING checking that those ports are available.
Once we hit the MAX_PORT we wrap around to BASE_PORT_START
Proposal
In addition to the current functionality, we can keep track of tests that were successfully allocated and released.
Once released, we can short circuit when get-ing a worker and reuse any previously successful port ranges that have been released.
Questions

Would setting a smaller BASE_PORT_RANGE accomplish a similar thing?
When reusing should we re-check the ports? or just assume they were open previously?

Hi,
Did we test whether the magellan works on windows machine? I don't have logs to share as my machine got changed to Mac recently and unable to reproduce on Mac. But just few days before when I ran the nightwatch boilerplate, I saw connection refused error: <IP_ADDRESS>:12000. I believe the 12000 is the default BASE_PORT_START.


Implement Brain Data Custom Data

Expected Behavior

We are able to use Brain Data custom data in LEAN
Actual Behavior

We are unable to use Brain Data custom data in LEAN
Potential Solution

Implement a data converter + required BaseData implementations
Reproducing the Problem

N/A
System Information

N/A
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

Solved at https://github.com/QuantConnect/Lean.DataSource.BrainSentiment


fix docs group version

Signed-off-by: Song Wu<EMAIL_ADDRESS>
Type of change:

[ ] Bugfix

What this PR does / why we need it:

the new Group version about apisix is apisix.apache.org/v2beta3, but still use apisix.apache.org/v2 in docs.
so  in order to correct the problem I submit a pr t fix it.
Pre-submission checklist:

The new version of crd is v2, and v2beta3 will be discarded soon.
https://github.com/apache/apisix-ingress-controller/issues/1179

yeah. I see.

#1338
we are now in v1.5.0 release window, please see #1351 for detail.
thanks!

@tao12345666333  thank you.  I noticed taht.

I will close this one


quickstart lost

I was reading API docs and didnt found "quickstart" linked in the bottom
https://github.com/flyjs/fly/blob/master/docs/README.md#api
https://github.com/flyjs/fly/blob/master/docs/quickstart

@iamstarkov Thanks! Here is the correct link. I can patch this later, but if you send me a PR fixing this I'll merge ASAP.
:+1:

something strange, it seems to be okay in the markdown source, but still wrong in rendered version

dunno how to fix this heisenbug

you can contact github support for this strange behaviour
anyway thx for correct quickstart link

Fixed.


Run tsc after building types

We could run TSC after building the types in build-types.yml, which would return any potential TS errors immediately

tsc

install typescript!


Bump pipeline timeout to 90 min

Lately, it seems as though MSVC has been timing out with the 60 min timeout. Bumping up to 90 min.
Not sure why we're getting so many timeouts now; Clang takes ~20 min and I'm pretty sure MSVC used to as well... going to see if this helps at least.

Side note: timeout is probably due to low memory

##[warning]Free memory is lower than 5%; Currently used: 95.07%

Builds still seem to be progressing, so the longer timeout is hopefully enough


No latency metrics and pool name attributes when using HikariConfig with Micrometer MeterRegistry

A colleague of mine reports that when using Spring Boot with HikariCP and Micrometer with StatsD he can pass the Micrometer MeterRegistry to hikariConfig.setMeterRegistry and get metrics including latency metrics and pool name attributes just fine. However, when he uses Prometheus he loses the latency metrics and pool name attributes. He does still get throughput metrics.
He found that as a workaround he can pass a PrometheusMetricsTrackerFactory to hikariConfig.setMetricsTrackerFactory and that way also gets latency metrics and pool name attributes. Shouldn't this also work when doing hikariConfig.setMeterRegistry with Micrometer?
I've discussed this with Micrometer devs and they recommended I report this to you because there should be no extra capabilities in Prometheus simpleclient compared to Micrometer: https://micrometer-metrics.slack.com/archives/C662HUJC9/p1557409990100100
Environment
HikariCP version: 3.2.0 (via Spring Boot 2.1.4.RELEASE)
JDK version     : 1.8.0_212
Database        : PostgreSQL
Driver version  : 42.2.5

@breun I see no reason why this information would be available in one case and not the other.  I am adding @matsumana as a reference here, because he contributed a large part of the micrometer implementation, and I believe tested with Prometheus.

I believe tested with Prometheus

yes, I use HikariCP and Prometheus.
@breun
I want to know exported metrics using Prometheus client, and which metrics/lables are not exported.
Can you share them as concrete example?

@vy Can you provide examples of metrics/labels that are missing when you don't call hikariConfig.setMetricsTrackerFactory(prometheusMetricsTrackerFactory)?

@brettwooldridge @matsumana @breun A demonstration is provided in the following Gist: https://gist.github.com/vy/d9369757dae398423f1eeabf589df543. See the discrepancies between the PrometheusMeterRegistry#scrape() outputs.

An excerpt from the Gist:
MeterRegistry#scrape() snippet when HikariConfig#setMetricRegistry(MeterRegistry) is used:
hikaricp_connections_usage_seconds_count{pool="test",} 1.0
hikaricp_connections_usage_seconds_sum{pool="test",} 1.083
hikaricp_connections_usage_seconds_max{pool="test",} 1.083

MeterRegistry#scrape() snippet when HikariConfig#setMetricsTrackerFactory(new PrometheusMetricsTrackerFactory(CollectorRegistry)) is used:
hikaricp_connection_usage_millis{pool="test",quantile="0.5",} 678.0
hikaricp_connection_usage_millis{pool="test",quantile="0.95",} 678.0
hikaricp_connection_usage_millis{pool="test",quantile="0.99",} 678.0
hikaricp_connection_usage_millis_count{pool="test",} 1.0
hikaricp_connection_usage_millis_sum{pool="test",} 678.0

HikariCP supports three metrics libraries and exported metrics are different.
I'm not sure why HikariCP supports three metrics libraries ane metrics are different.

Dropwizard metrics
Micrometer
Prometheus

Then hikariConfig.setMetricRegistry uses Micrometer's MeterRegistry, hikariConfig.setMetricsTrackerFactory use Prometheus' CollectorRegistry.
If the metrics you need are not exported by Micrometer, it would be good to add metrics to MicrometerMetricsTracker.

A colleague of mine reports that when using Spring Boot with HikariCP and Micrometer with StatsD he can pass the Micrometer MeterRegistry to hikariConfig.setMeterRegistry and get metrics including latency metrics and pool name attributes just fine. However, when he uses Prometheus he loses the latency metrics and pool name attributes. He does still get throughput metrics.

Although I've never used StatsD, your co-worker said that the metrics exported by StatsD and Prometheus are different, is that true?
I don't know whether it's due to HikariCP so far.

@matsumana That colleague is me. And, IIRC, yes they were different. (There we were feeding dw-metrics to StatsD via a plugin.)

@matsumana, @brettwooldridge What is the resolution for the issue? How shall we proceed? The discrepancy in the metrics are still there.

I do not use any of these libraries personally, most of the implementations were contributed.  If metrics are missing for an implementation I am sure all users would appreciate debugging efforts and pull requests from those who are capable.

hikaricp_connections_usage_seconds_count{pool="test",} 1.0

hikaricp_connection_usage_millis_count{pool="test",} 1.0

@vy These metrics names are different because the implementation for Micrometer standardises all times to seconds (a good thing IMHO). That doesn't explain the connection / connections naming difference though.


build kubefed2 on demands with parameter control

Fix#589
build kubefed2 on demands with parameter control: when the script is used independently, kubefed2 should be build. If it is used in pre-commit.sh, the build process should be ignored.
@gyliu513 @marun

/cc @marun

Thank you for doing this!   We don't have a formal bash style guide, but I'd like to see quoting of substitutions consistent with the script content e.g.
BUILD="${BUILD}" vs BUILD=${BUILD}

Related code are quoted.

@marun @xunpan
I found some examples in script not using quote,  like the following:

https://github.com/kubernetes-sigs/federation-v2/blob/master/scripts/deploy-federation.sh#L162
https://github.com/kubernetes-sigs/federation-v2/blob/master/scripts/delete-federation.sh#L92

What is the advantage of adding quote?

bash will treat message in "" as a whole. E.g.
$ mkdir "hi job"
$ MD="hi job"
$ echo $MD
hi job
$ cd $MD
bash: cd: hi: No such file or directory
$ cd "$MD"
$ pwd
/tmp/hi job

For this case, I agreed to use "" based on marun's comments because

it handles ${ROOT_DIR} correctly even with blank in the path
it is consistent style in the context for bash code.

@marun any comments?

@xunpan I think that's correct, yes.  Thank you!
At some point we'll probably want a bash style guide that codifies the intentional elements of style in the existing scripts, and a corresponding effort to fix the inconsistent elements.  I don't think it's a high priority yet, though.
(No action required) I think it's preferable to use y for boolean true and empty string as boolean false, such that test for empty (-z) and its negation can be used in conditional statements.  I don't feel strongly enough to ask for it to change in this PR though.
/approve
/lgtm


PermissionsAndroid doesn't support READ_VOICEMAIL

Description
PermissionsAndroid supports ADD_VOICEMAIL but not READ_VOICEMAIL. Looks like a simple oversight.
https://developer.android.com/reference/android/Manifest.permission#READ_VOICEMAIL
Version
0.61.5
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 12.3.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 312.64 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.1 - /usr/local/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.5.3 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 23, 28, 29, 30, 32
Build Tools: 28.0.3, 29.0.2, 30.0.2, 32.0.0
System Images: android-29 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7935034
Xcode: 13.4/13F17a - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-safe-area-context: 4.2.5
Steps to reproduce
Attempted to run request on the unsupported permission.
Snack, code example, screenshot, or link to a repository
const granted = await PermissionsAndroid.request(
          PermissionsAndroid.PERMISSIONS.READ_VOICEMAIL);

You're right. We actually miss both READ_VOICEMAIL and WRITE_VOICEMAIL. Don't you mind sending a PR with those two (should be as easy as #32282). I'll be happy to review and merge them @babraham123


Auth applet

/login -> login form: email & password
/login?email&password -> check success -> create session -> OnSuccessfulLogin (Response -> Response)  HTTPure.Response set cookie redirect login successful  ()
/login?email&password -> check failure -> response LoginFailed
loginRequired - check whether the user is logged in
withLoginRequired do
  ...

/logout - similarly to the OnSuccessfulLogin remove cookie

We can say that initial prototyping phase is behind us:
https://github.com/purescript-webrow/webrow/tree/master/src/WebRow/Applets


Skip tests setting the JVM timezone

(requires Metabase 0.46.x+ which is not yet released)
This PR relies on the driver feature setting :test/jvm-timezone-setting which is available on the master branch of metabase/metabase.

Waiting for https://github.com/metabase/metabase/milestone/168


Reporting GetEventGroup returns key mismatch error

When calling the getEventGroup method an error is returned highlight that there is no matching private key. We have used Halo's testing TINK files to encrypt the metadata and configured them within the reporting server to be able to decrypt the eventGroups
When trying to validate in Halo's dev environment we get an error as well

Describe the bug
When listing event groups via the reporting server for a specific MC and EDP the response is:
ERROR:
Code: FailedPrecondition
Message: Public key does not have corresponding private key
Steps to reproduce
Preconditions:

MC and EDP exist in the Kingdom and configured with their certificates and keys
Event groups with encrypted meta data exist for the MC/EDP combination

How to reproduce

Call the listEventGroups Method through the reporting server as the MC

Sample call:
grpcurl -key certs/halo/mc_tls.key -cert certs/halo/mc_tls.pem -cacert certs/halo/reporting_root.pem -import-path protos -import-path protos/Reporting -proto event_groups_service.proto -d '{"parent":"measurementConsumers/VCTqwV_vFXw/dataProviders/R180F6AQ584"}' v1alpha.reporting.dev.halo-cmm.org:8443 wfa.measurement.reporting.v1alpha.EventGroups/ListEventGroups
Component(s) affected
Reporting Server
Version
https://github.com/world-federation-of-advertisers/cross-media-measurement/pull/743 - 54ebee2fdc3233a9cfde6c16745f0a82c47873d8
Environment
ISBA's Dev environment
Halo's Dev Environment
Additional context
In the local origin set up we are using Halo's provided tink files to set up the EDP and MC, the metadata for the event groups is being encrypted with he MC;s public tink and the reporting server has access to the correct MC private tink

Looks like this is talking about the Report API. If the error is "Public key does not have corresponding private key", then that means that no matching private key was found in the encryption key store. In the dev configuration, this comes from encryption_key_pair_config.textproto in the config-files ConfigMap.
Are you sure that the config file has an entry for the MC encryption key that was used to encrypt that EventGroup metadata? If using the Halo dev environment, the file has the following contents:
# proto-file: wfa/measurement/config/reporting/encryption_key_pair_config.proto
# proto-message: EncryptionKeyPairConfig
principal_key_pairs {
  principal: "measurementConsumers/VCTqwV_vFXw"
  key_pairs {
    public_key_file: "mc_enc_public.tink"
    private_key_file: "mc_enc_private.tink"
  }
}

This means that the data field inside of the measurement_consumer_public_key field in the EventGroup must contain the contents of mc_enc_public.tink.

Note that this is assuming that metadata was indeed specified for the EventGroup in question. There's a separate pending issue where the Reporting server attempts to decrypt EventGroup metadata even when it's not specified. See #752.

I don't think this is caused by #738, as that's specifically an issue with metadata not being set. You stated that you're getting this when metadata is set.
I'm able to reproduce this error with the resource name you provided, but I still can't tell if it's expected as I don't know which key was used. The dev environment configuration only has one key pair in its encryption_key_pair_config.textproto: the checked-in mc_enc_public.key and mc_enc_private.key. This means that the call will fail unless all EventGroups for that DataProvider in the dev environment used that public key.

I ran a query in the dev Kingdom and found that the only EventGroup defined for dataProviders/R180F6AQ584 does not have its encrypted_metadata field set, so the RPC above is expected to fail until #738 is fixed.
Do you have an example where this is failing when encrypted_metadata is set?

I do but is in our environment, this time it seems the error changed. Here's the details:
We redeployed the the entire platform using commit  d85919b12bc389f57797ecb7a06921fbe69371f0, wiped DBs, got new MC and EDP ids. We created 2 event groups with encrypted metadata. The metadata was encrypted using the tink file form Halo's repo (see the E.Gs at the bottom).
The associated private key is configured in the reporting server so decryption can occur. I can see the kingdom responding correctly but the reporting server is returning "UNKOWN" with the following error:
java.security.GeneralSecurityException: decryption failed at com.google.crypto.tink.hybrid.HybridDecryptWrapper$WrappedHybridDecrypt.decrypt(HybridDecryptWrapper.java:73) at org.wfanet.measurement.common.crypto.tink.TinkPrivateKeyHandle.hybridDecrypt(KeyHandle.kt:77) at org.wfanet.measurement.common.crypto.PrivateKeyHandle$DefaultImpls.hybridDecrypt$default(KeyHandle.kt:28) at org.wfanet.measurement.consent.client.measurementconsumer.MeasurementConsumerClientKt.decryptMetadata(MeasurementConsumerClient.kt:128) at org.wfanet.measurement.reporting.service.api.v1alpha.EventGroupsService.listEventGroups(EventGroupsService.kt:94) at org.wfanet.measurement.reporting.service.api.v1alpha.EventGroupsService$listEventGroups$1.invokeSuspend(EventGroupsService.kt) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.internal.ScopeCoroutine.afterResume(Scopes.kt:33) at kotlinx.coroutines.AbstractCoroutine.resumeWith(AbstractCoroutine.kt:102) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:46) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
{
"eventGroups": [
{

  "name": "dataProviders/MNstouxIrrI/eventGroups/C8ZbWOzPJfE",

  "measurementConsumer": "measurementConsumers/Pk21bxO3Uxc",

  "measurementConsumerCertificate": "measurementConsumers/Pk21bxO3Uxc/certificates/Gpl9qhO3U4g",

  "measurementConsumerPublicKey": {

    "data": "CAES5QEIrfyPlQUS3AEKzwEKPXR5cGUuZ29vZ2xlYXBpcy5jb20vZ29vZ2xlLmNyeXB0by50aW5rLkVjaWVzQWVhZEhrZGZQdWJsaWNLZXkSiwESRAoECAIQAxI6EjgKMHR5cGUuZ29vZ2xlYXBpcy5jb20vZ29vZ2xlLmNyeXB0by50aW5rLkFlc0djbUtleRICEBAYARgBGiEA2VOaFS7y+xGQvC2VydELNZValk7ASE8EXHny7b0tOX4iIC1a/MlmcWmzimHAUyPjtZfuRLqtlS6qUdkLj8/eb15bGAMQARit/I+VBSAB",

    "signature": "MEUCIQDP7cgMqAuP3va5QRbLDatJe69yVpg+H4S5EKYMR8X4aQIgHxH5vAfvwFVSfS9nvvmzKF99o5mgiDWjBwPyihFeWGk="

  },

  "eventGroupReferenceId": "TestEvent1"

},

{

  "name": "dataProviders/MNstouxIrrI/eventGroups/KN2jfuzPYw8",

  "measurementConsumer": "measurementConsumers/Pk21bxO3Uxc",

  "measurementConsumerCertificate": "measurementConsumers/Pk21bxO3Uxc/certificates/Gpl9qhO3U4g",

  "measurementConsumerPublicKey": {

    "data": "CAES5QEIrfyPlQUS3AEKzwEKPXR5cGUuZ29vZ2xlYXBpcy5jb20vZ29vZ2xlLmNyeXB0by50aW5rLkVjaWVzQWVhZEhrZGZQdWJsaWNLZXkSiwESRAoECAIQAxI6EjgKMHR5cGUuZ29vZ2xlYXBpcy5jb20vZ29vZ2xlLmNyeXB0by50aW5rLkFlc0djbUtleRICEBAYARgBGiEA2VOaFS7y+xGQvC2VydELNZValk7ASE8EXHny7b0tOX4iIC1a/MlmcWmzimHAUyPjtZfuRLqtlS6qUdkLj8/eb15bGAMQARit/I+VBSAB",

    "signature": "MEUCIQDP7cgMqAuP3va5QRbLDatJe69yVpg+H4S5EKYMR8X4aQIgHxH5vAfvwFVSfS9nvvmzKF99o5mgiDWjBwPyihFeWGk="

  },

  "eventGroupReferenceId": "TestEvent2"

},

{

  "name": "dataProviders/MNstouxIrrI/eventGroups/RPK29BOmsGI",

  "measurementConsumer": "measurementConsumers/Pk21bxO3Uxc",

  "eventGroupReferenceId": "001",

  "eventTemplates": [

    {

      "type": "wfa.measurement.api.v2alpha.event_templates.testing.TestVideoTemplate"

    }

  ]

}

]
}

I'm going ahead and marking this bug as a duplicate of #738 as we've been unable to reproduce outside of that condition. We should have a different bug filed for the decryption failure.

Duplicate of #738

I thought this bug was for the decryption of meta data as https://github.com/world-federation-of-advertisers/cross-media-measurement/issues/738 is about event groups with out metadata and my understanding is that 738 should not have any impact on the event groups that do have properly encrypted metadata. Are you saying that both issue have the same root cause?

I thought this bug was for the decryption of meta data as #738 is about event groups with out metadata

This bug is specifically about getting a key mismatch error. As far as we can tell, the only case where one would get that error is #738 hence filing this as duplicate.

Are you saying that both issue have the same root cause?

I'm saying that all key mismatch errors we've seen so far appear to have been caused by #738. The decryption error you mentioned in https://github.com/world-federation-of-advertisers/cross-media-measurement/issues/760#issuecomment-1341302750 has been split out to a new issue as #781 as it has nothing to do with a key mismatch error.


PowerShell script to install Spice on Windows

Part of https://github.com/spiceai/spiceai/issues/853
Adds PowerShell script to install latest Spice version on Windows. Once merged Spice can be installed as
curl -L "https://raw.githubusercontent.com/spiceai/spiceai/trunk/install/Install.ps1" -o Install.ps1 && PowerShell -ExecutionPolicy Bypass -File ./Install.ps1

Checking the latest Spice version...
Installing Spice v0.11.0-alpha
Downloading Spice CLI from https://github.com/spiceai/spiceai/releases/download/v0.11.0-alpha/spice.exe...
Downloading Spice Runtime from https://github.com/spiceai/spiceai/releases/download/v0.11.0-alpha/spiced.exe...
Spice CLI installed into C:\Users\sg\.spice\bin successfully.
Spice CLI directory is already in PATH.

To get started with Spice.ai, visit https://docs.spiceai.org

Notes:

While testing I found that Spice is unable to detect and download Spice runtime on Windows so runtime was added to installation as well.
Spice expects runtime to be spiced instead of spiced.exe on Windows and fails to start. Installation script temporary creates blank spiced file with installed version in order for Spice to work.
I'll address both items above as part of https://github.com/spiceai/spiceai/issues/853

Converted to Draft as I plan to update Windows release binaries naming so it is consistent with Linux and macOS.

Updated installation script to use future release binary naming. Ready for review


Add .pytest_cache/ to .gitignore

Add .pytest_cache/ to .gitignore.

LGTM, makes sense.
I think it can further improved by rewriting based on https://github.com/github/gitignore/blob/master/Python.gitignore, though.


Release to pypi for compute driver support version

Just remind to do a release in pypi for your compute driver support in CAL.

@daikk115 ping, now is the time for this task.


is gulp-typings asynchronous, and if so how do I accomodate that?

In my gulpfile, I have:
const gulp = require('gulp')
  , typings = require('gulp-typings')
...
gulp.task('typings',function(){
  gulp.src('./typings.json').pipe(typings());
});
...
gulp.task('editor', ['editor-html', 'typings'], function () {
  return browserify()
         .add('./src/editor/index.ts')
         .plugin(tsify, { noImplicitAny: true })
         .bundle()
         .on('error', function (error) { console.error(error.toString())
                                         process.exit(1) })
         .pipe(source('zote-editor.js'))
         .pipe(gulp.dest('build'))
})
...

In my typings.json, I have:
{
  "ambientDependencies": {
    "chai": "registry:dt/chai#3.4.0+20160317120654",
    "codemirror": "registry:dt/codemirror#0.0.0+20160317120654",
    "mocha": "registry:dt/mocha#2.2.5+20160317120654"
  }
}

When I run gulp typings on the command line, a typings directory is created and the type definition files are installed.  However, if I delete that directory and try again with gulp editor, I get
[11:30:37] Using gulpfile ~/p/zotecode/gulpfile.js
[11:30:37] Starting 'editor-html'...
[11:30:37] Starting 'typings'...
[11:30:37] Finished 'typings' after 8 ms
[11:30:37] Finished 'editor-html' after 95 ms
[11:30:37] Starting 'editor'...
TypeScript error: src/editor/index.ts(1,1): Error TS6053: File 'typings/main.d.ts' not found.

I suspect this is because gulp-typings isn't waiting for typings to install stuff before returning control to gulp, so when the editor task runs, the definitions aren't there yet and the TypeScript compiler complains.  Is this the case, and if so, how can I structure things to ensure the definitions are fully installed before a task which depends on them is run?
Thanks.

Yes, you are correct, gulp-typings is async.
You need to return the gulp stream, so gulp knows where to listen for the finish event.
This is standard for gulp.
Regards
Phil from Lossless

Ah, of course; thanks for explaining it.  I think I'll actually learn how gulp works before filing any more bugs :)

No problem, glad to help ;)


Automation updates

Thank you for contributing to Mina! Please see CONTRIBUTING.md if you haven't
yet. In that doc, there are more details around how to start our CI.
Explain your changes here.
Explain how you tested your changes here.
Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

Closes #0000
Closes #0000

Accidental DUP (covered by #7573)

Accidental DUP (covered by #7573)


Horizontal bar chart x-axis max property breaks labels display

Description
I work with a horizontal bar chart.
When I set
xaxis: {
  max: {some value here}
}

the number of labels increases for some reason and:

when this is done on a chart with small width labels start to overlap.
when max value is something less than 1 (for example 0.4) labels start to repeat

Expected Behavior

either number of labels increases until they start overlapping or number of labels stays the same.
either labels automatically increase their precision or number of labels is adjusted so that no labels repeat.

Actual Behavior

labels overlap
labels repeat

Screenshots
Example with overlapping labels:

Example with repeating labels:

Reproduction Link
https://codesandbox.io/s/apx-bar-basic-forked-zp5xw5?file=/src/app/app.component.ts
Additional question
Can you please specify all the fields which get swapped between xaxis and yaxis when plotOptions.bar.horizontal = true?

Okay, I examined apexchart's inner code and came up with the following solution: I wrote a directive, that calculates tickAmount based on chart's inner properties and sets it on every resize of chart's parent. There is the code:
import { Directive, ElementRef, Input, OnInit, OnDestroy, NgZone, ContentChild, AfterContentInit } from '@angular/core';
import { ChartComponent } from 'ng-apexcharts';

@Directive({
  selector: `[adjustedAxesOfChildApexChart]`,
})
// This directive should be applied to sizeable(!) parent of horizontal bar apexchart
export class AdjustedAxesOfChildApexChartDirective implements OnInit, AfterContentInit, OnDestroy {
  @ContentChild(ChartComponent)
  chart: any;

  observer: ResizeObserver;
  readonly minDistanceBetweenLabels = 10; // px
  readonly maxDistinguishableIncrement = 6; // if adjacent labels' difference is more than that, then we don't care if ticks are a little bit off
  readonly minIntegerLabel = 3.9; // apexhart starts producing labels with /10 presision if max label is < than minIntegerLabel

  constructor(private host: ElementRef, private readonly zone: NgZone) {}

  ngOnInit() {
    this.observer = new ResizeObserver(() => {
      this.zone.run(() => this.setTickAmount());
    });

    this.observer.observe(this.host.nativeElement);
  }

  ngAfterContentInit() {
    this.setTickAmount();
  }

  setTickAmount() {
    // this field can be uninitialised at the very first run
    if (!this.chart?.chartObj?.w?.globals) {
      return;
    }

    const chartGlobalOptions = this.chart.chartObj.w.globals;

    const xAxisLabels = chartGlobalOptions.yAxisScale[0].result;
    const firstLabel = xAxisLabels[0];
    const lastLabel = xAxisLabels[xAxisLabels.length - 1];

    // I don't care if this is not precise since I do Math.floor which gets us result bigger or equal than the actual size
    const firstLabelWidth =
      chartGlobalOptions.xAxisLabelsWidth / Math.max(Math.floor(`${lastLabel}`.length / `${firstLabel}`.length), 1);

    // this formula is based on apexchart code of getting x-values for labels (node_modules\apexcharts\src\modules\axes\YAxis.js drawYaxisInversed)
    const availableXAxisWidth =
      chartGlobalOptions.gridWidth + // gridWidth is an actual grid width (xaxis length)
      chartGlobalOptions.padHorizontal -
      firstLabelWidth - // we need to subtract first label width because it can be the same length as the rest of them. Btw, this case with very long first label has a bug: label starts earlier than left border. No fix for that)
      this.chart.chartObj.w.config.xaxis.labels.offsetX;

    const maxTickAmount = Math.floor(
      availableXAxisWidth / (chartGlobalOptions.xAxisLabelsWidth + this.minDistanceBetweenLabels)
    );

    this.chart?.updateOptions({
      xaxis: {
        tickAmount: this.getOptimalTickAmount(
          Math.round(lastLabel < this.minIntegerLabel ? lastLabel * 10 : lastLabel), // for actual labels apexchart rounds the actual numbers, so must I
          maxTickAmount
        ),
      },
    });
  }

  getOptimalTickAmount(lastLabel: number, maxTickAmount: number) {
    if (lastLabel / maxTickAmount > this.maxDistinguishableIncrement) {
      return maxTickAmount;
    }

    // if increment is indistinguishable with some tickAmount, then there is no reason in taking anything less than that
    const minTickAmount = Math.min(Math.max(Math.floor(lastLabel / this.maxDistinguishableIncrement), 1), maxTickAmount);

    // common algorithm of searching for divisors with some restrictions
    let lastDivisor = 1;
    for (let divisor = 1; divisor * divisor <= lastLabel && divisor <= maxTickAmount; ++divisor) {
      if (lastLabel % divisor === 0) {
        lastDivisor = divisor;
        const pairedDivisor = lastLabel / divisor;
        if (minTickAmount <= pairedDivisor && pairedDivisor <= maxTickAmount) {
          return pairedDivisor;
        }
      }
    }

    return lastDivisor === 1 || lastDivisor < minTickAmount ? minTickAmount : lastDivisor;
  }

  ngOnDestroy() {
    this.observer.unobserve(this.host.nativeElement);
  }
}

As the comment states, this directive should be applied to apexchart's sized parent, who can be observed with ResizeObserver. I had no luck applying it to an apexchart itself. So the usage is:
<div adjustedAxesOfChildApexChart>
  <apx-chart
    [series]="series"
    [yaxis]="yaxis"
    [xaxis]="xaxis"
    [colors]="colors"
    [fill]="fill"
    [chart]="chart"
    [grid]="grid"
    [tooltip]="tooltip"
    [legend]="legend"
    [dataLabels]="dataLabels"
    [stroke]="stroke"
    [plotOptions]="plotOptions"
    [states]="states"
  ></apx-chart>
</div>

This fix is not perfect, since there are still a bug with max sometimes being partially disregarded when there is tickAmount set. I didn't go the whole way down through the apexchart's code to find out why that happens and I'll be grateful if someone can figure out that))


When loading data for train allow to read data that has hannel on first position

Add heuristics to allow to channel ais into being the first axis.
For better compatibility with preview data in napari, for example.

Thanks for starting to work on this @Czaki. I should have time to have a look at this later in the evening or tomorrow.

In this PR, currently, there is no metadata parsing. Only guessing based on the size of the array.


NullPointer on mvn package

When using Eclipse and Maven on Windows 10 with Docker for Windows 17.06, dockerfile plugin 1.3.0 reports a null pointer exception. Any ideas? Or need more info?
stack.txt

see #30, this is fixed in 1.3.2, although the latest version is 1.3.4 now

Thanks!


Add support for  operations

These operations follow a similar syntax to <program> operations - just moving data in the other direction.
To avoid shadowing the read function, I used read_op for types/functions/variables (breaking the existing convention).
Tested on a QCS6490 SoC.

<read ...> operations in QFIL XML files are found in the wild (e.g. this github search). This PR was intended to make files like these work with qdl.
I agree that a qdl-read tool would be a useful addition. Perhaps it could be as simple as a qdl --read flag, which takes a regular QFIL XML file but performs reads instead of writes.

I didn't want to include the merge commit in the history, and the code needed a few small fixups (missing stdlib.h and CodeQL complained about the transfer-speed-print). So rebased it, fixed those and merged it in the form of #74. Thank you for your contribution!


Add data export history view to support interface

Context
Support users need to see a complete history of data exports that have been requested, their status, when they ran and by whom.
Changes proposed in this pull request

[x] Add a new route, controller action and view to implement the new page

[x] Add a link to the data directory index page to access the history

[x] Update the data directory system spec

[x] Extract a DataExportHistoryComponent and applied this to the existing single-type history page as well as the new one. On the single-type page this component doesn't need to display the Name column because they are all the same and it's shown in the page title already.

Guidance to review

UX and content just represents my best guess at this stage. Do we need to change the information displayed and layout on the new page? Is there a better place for the History link on the index page?
Are the tests sufficient?
Is there a better name for the route?

Link to Trello card
https://trello.com/c/4nRf96iG/3268-add-export-history-page
Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] This code does not rely on the addition/removal of Azure config environment variables in the same Pull Request
[x] New environment variables have been added to the Azure config

The component is looking great 🙌


Dev

[x] Completed PR - Has all features or fixes that it was meant to and isn't half done
[x] Follows the style guide - Style guide found here
[x] Your code follows the same code style as the rest of the project
[x] Tested changes

What is added
User argument to getUsage to provide FlareBot's default embed
Add page footer to table
What is fixed
The math behind embeds
Report duping

Best pr name 10/10


jagged spark status indicator heights

in notebook in the cell output:

in the toolbar:

also check jupyter lab.

how about matching this height:


Remove unneeded packages

While I love both htop and nano, I don't think most people will need or want these in their container.

Totally agree. They were there just for debugging purposes.
Merged!


usable interactive init/update?

This turns cargo dist init into an interactive setup/updater that walks you through setting things up (recommended settings can all be selected by mashing ENTER over and over). Including:

prompting you to update your project to the version of cargo-dist you're running (refuses to proceed otherwise)
prompting you to select what CI backend to use (only one option, github)

enabled by default if we see your project's repo contains "github"
errors out if you don't have a consistently set repository url in your workspace's Cargo.tomls

prompting you to select what installers to enable

skips if no CI backend is enabled, as we use this to derive fetch URLs for artifacts
if npm is enabled:

if newly enabled, prompts you to provide an @scope
if tar.gz artifacts aren't enabled, prompts you to enable them

adds comments to your Cargo.toml describing any keys that are set
running cargo dist generate-ci afterwards

panics when selecting only npm installer:
✔ enable ci (select with arrow keys and space, submit with enter) · github
✔ enable installers (select with arrow keys and space, submit with enter) · npm
added [workspace.metadata.dist] to your root Cargo.toml
analyzing workspace:

  × your cargo workspace has an issue
  ├─▶ `cargo metadata` execution failed
  ╰─▶ `cargo metadata` exited with an error: error: failed to parse manifest at `/Users/ag_dubs/axo/cargo-dist/
      Cargo.toml`

      Caused by:
        could not parse input as TOML

      Caused by:
        TOML parse error at line 32, column 10
           |
        32 | "release"
           |          ^
        Unexpected `
        `
        Expected `.` or `=`

if you leave the npm scope question blank it shows twice in the "summary"
ag_dubs@Ashleys-MBP-2 axolotlsay % ../cargo-dist/target/debug/cargo-dist dist init
[profile.dist] already exists, nothing to do
✔ enable ci (select with arrow keys and space, submit with enter) · github
✔ enable installers (select with arrow keys and space, submit with enter) · powershell, npm
? you've enabled npm support, please enter the @scope you want to publish under (leave blank to publish globally)
✔ you've enabled npm support, please enter the @scope you want to publish under (leave blank to publish globally) ·
added [workspace.metadata.dist] to your root Cargo.toml
analyzing workspace:
  axolotlsay
    [bin] axolotlsay

generated Github CI to /Users/ag_dubs/axo/axolotlsay/.github/workflows/release.yml

if you leave the npm scope question blank it shows twice in the "summary"

this is unfortunately just how dialoguer works for most prompts, regardless of the answer :(

in a project that previously supported shell installers, dist init panics when selecting only npm installer:

yeah I wasn't properly truncating/flushing the file so it would get randomly corrupted. i encountered this several times in development but i convinced myself it was just a side-effect of me messing around in my editor or something. fixed now.


How to disableToggle for individual splitbar?

The disableToggle has cascading effect. When "disableToggle: true" is set on the top level ui-layout, it is also disabled for all ui-layout below it even when "disableToggle:false" are set on them.
See example here:
http://plnkr.co/edit/9TSQQxsTYGeZXPk7Msxh?p=preview
Please help! Thanks!

same requirement,plz help

I reinstalled using
bower install angular-ui-layout and selected the most recent version, this correct the issue for me.


Copy CQF-Ruler behaviour when creating a target resource from an ActivityDefinition apply

This PR removes a few cases where the resulting target resource from Encender would include an element that should not exist on that resource. For instance, a resulting ServiceRequest should not have a dosage element
The default case may still create invalid resources, however
Element choices were adapted from CQF-Ruler. Happy to make any changes!

Thanks @oyisre I'll take a look.

@oyisre since this changes behavior (for the better since generated resources are less likely to have elements they shouldn't), do you agree this constitutes a minor revision bump?

Agreed, some generated resources may look totally different now


Reduce mock usage within Palomaswap

Background
Palomaswap tests include a number of XxxMockQuerier classes which serve to mock out adjacent contracts. We should instead instantiate these contracts in full and issue queries against them. While interdependency of tests suites can be an extra burden, mocking out contract interaction is probably a barrier to correctness overall.
Done when

[ ] Factory test mocks are replaced.
[ ] Pair test mocks are replaced.
[ ] Router test mocks are replaced.
[ ] Token test mocks are replaced.

@Vizualni I believe we are pausing palomaswap development so I will close this issue.


bevy_app: add tracing event with tracy.frame_mark

Currently tracy interprets the entire trace as one frame because the marker for frames isn't being recorded.
When an event with tracy.trace_marker=true is recorded, tracing-tracy will mark the frame as finished:
https://github.com/nagisa/rust_tracy_client/blob/aa0b96b2ae2aee6f3831994f9a3a8c29bcc85fae/tracing-tracy/src/lib.rs#L240
Unfortunately this leads to
INFO bevy_app:frame: bevy_app::app: finished frame tracy.frame_mark=true

being printed every frame (we can't use DEBUG because bevy_log sets max_release_level_info.
Instead of emitting an event that gets logged every frame, we can depend on tracy-client itself and call finish_continuous_frame!();

Is it a good idea to depend on both tracy_client and tracing_tracy?

tracing_tracy uses tracy_client will call finish_continous_frame! when an event with tracy.frame_mark is recorded: https://github.com/nagisa/rust_tracy_client/blob/aa0b96b2ae2aee6f3831994f9a3a8c29bcc85fae/tracing-tracy/src/lib.rs#L240
So this PR is doing exactly the same, just without the event.

Did you try using a tracing event with the frame marker but at the debug level or so?

I tried but that didn't work in release mode as bevy_log enabled the max_release_level_info feature on tracing-subscriber.

just to note an alternative to using another import, we could also suppress the info logging for tracy events:
+++ b/crates/bevy_log/src/lib.rs
@@ -159,6 +159,11 @@ impl Plugin for LogPlugin {
             let tracy_layer = tracing_tracy::TracyLayer::new();

             let fmt_layer = tracing_subscriber::fmt::Layer::default();
+            #[cfg(feature = "tracing-tracy")]
+            let fmt_layer = fmt_layer.with_filter(
+                tracing_subscriber::filter::Targets::new().with_target("tracy", Level::ERROR),
+            );
+
             let subscriber = subscriber.with(fmt_layer);

             #[cfg(feature = "tracing-chrome")]

@robtfm oh that’s a good find. I guess warnings would be ok

@jakobhellermann  what do you think of @robtfm ’s suggestion?

I switched to @robtfm's suggestion to use the event but exclude it from the fmt_layer and moved the marker to right after the surface is presented and the SurfaceTexture dropped.

bors r+


WIP: Event stream formatter

The goal of this ticket is to produce a stream of JSON events that conform to the standardised cucumber event protocol
This will allow cucumber to interoperate with other tools, and ultimately perhaps enable us to use a cross-platform formatter library.
The event protocol is new and emerging, and this PR aims to keep up with that.

One more thing to point out, for pretty formatter. We probably need argument list to make them bold. Which should most probably go with StepDefinitionFound event:
{
  "event":"StepDefinitionFound",
  "source_id":"features/simple.feature:3",
  "definition_id": "features/step_definitions/steps.rb:1",
  "arguments": [
    [5, 10],
    [16, 20]
  ]
}

Which could mark positions from - to in step.Text.

@l3pp4rd yes, agree regarding arguments. The offsets must be from the beginning of the line, since the formatter won't know at what column the step text starts (the text that was matched, following the step keyword).

@mattwynne do you want to keep this PR open? Should I try to move it forward or do you recommend starting over?

@aslakhellesoy I think it's practically done. The only criticism I'd have is that it wasn't built test-first - I mostly manually tested it with the electron cucumber-gui spike, though it does (or did) work against the protocol described in https://github.com/cucumber/cucumber/pull/172#issuecomment-347219777 so that was part of testing it too.
I'd have a crack and see if you can stabilise it.

I think we can close this one now! 🎉


Migrate invalid shard error to make it an invalid params error

cc @cw9 @xichen2020

Coverage decreased (-0.009%) to 78.608% when pulling 60a92d762cbb956061abdd638144e56a4d2a54a0 on make-invalid-shard-invalid-params-error into c3a8e8832aa36cabb9d90d6ffbd4987e2b8bb43a on master.


Group extensions by folders

It is normal to have a lot of extensions in our VSCode. It would be a good idea to be able to select them with SHIFT + Click for example and group them in a folder. In order to keep our extensions more organized.
Thanks!

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Link is failing

Hi,
This SDK is always throwing error connections. I have done the below configuration. Please let me know the missing configuration?
<TouchableOpacity
style={styles.cta_container}
onPress={() =>
Lean.current.link({
app_token: "myToken",
permissions: ["identity", "accounts", "balance", "transactions"],
customer_id: "myCustID",
sandbox: true,
})
}

@pratius it looks like you're passing in your appToken incorrectly in the sample shared above:
<TouchableOpacity
  style={styles.cta_container}
  onPress={() =>
    Lean.current.link({
      app_token: "myToken",
      permissions: ["identity", "accounts", "balance", "transactions"],
      customer_id: "myCustID",
      sandbox: true,
    })
}

assuming you have myToken as a stored variable, you should remove the " marks on either side so it's:
app_token: myToken

Same applies to the customer id


ingress-nginx addon: addon not waiting for nginx to be fully deployed

Describe the bug
We’re using the ingress-nginx addon to setup ingress. However after this some of our addons create ingress objects which rely on the ingress-nginx addon being there. When deploying we get errors similar to:
failed: Error: The stack named chris failed to deploy: CREATE_FAILED (The following resource(s) failed to create: [ciliumaddon]. ): Received response status [FAILED] from custom resource. Message returned: Error: b'Release "cilium" does not exist. Installing it now.\nError: 1 error occurred:\n\t* Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "[https://nginx-ingress-controller-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1/ingresses?timeout=30s](https://nginx-ingress-controller-ingress-nginx-controller-admission.kube-system.svc/networking/v1/ingresses?timeout=30s)": no endpoints available for service "nginx-ingress-controller-ingress-nginx-controller-admission"\n\n\n'

I’ve tried a few things:
Ordering so that the ingress-nginx addon is defined before the addons with ingress
Annotated the deployment inside those ingress-using addons with:
@blueprints.utils.dependable(blueprints.IngressNginxAddOn.name)

It looks like blueprints just isn’t waiting for the nginx pod to be running before moving on the subsequent addons. With our own custom addons we use the “wait” parameter from helm-addon: https://github.com/aws-quickstart/cdk-eks-blueprints/blob/b8c51d230fa548d39696121cd68a7c0228f90665/lib/addons/helm-addon/index.ts#L84
However this doesn’t seem to be available in IngressNginxAddOnProps. Do you have any suggestions of how to resolve this?
Expected Behavior
Subsequent addons with ingress objects deploy without error
Current Behavior
failed: Error: The stack named chris failed to deploy: CREATE_FAILED (The following resource(s) failed to create: [ciliumaddon]. ): Received response status [FAILED] from custom resource. Message returned: Error: b'Release "cilium" does not exist. Installing it now.\nError: 1 error occurred:\n\t* Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "[https://nginx-ingress-controller-ingress-nginx-controller-admission.kube-system.svc:443/networking/v1/ingresses?timeout=30s](https://nginx-ingress-controller-ingress-nginx-controller-admission.kube-system.svc/networking/v1/ingresses?timeout=30s)": no endpoints available for service "nginx-ingress-controller-ingress-nginx-controller-admission"\n\n\n'

Reproduction Steps
Deploy ingress-nginx addon, and another addon with an ingress at the same time
Possible Solution
Add the "wait" condition to the ingress-nginx addon
Additional Information/Context
No response
CDK CLI Version
2.132.0 (build 9a51c89)
EKS Blueprints Version
1.15.1
Node.js Version
v20.15.1
Environment details (OS name and version, etc.)
Ubuntu 22.04.4 LTS
Other information
No response

Implement refactoring all hem addons to support the wait option as the one-off solution won't solve similar cases for the rest of the addons.


New Stage-2 Package: "event-bus"

There probably will be some changes in the future (some ideas like toPromise to explore). But I think it is mergeable as stage-2.
There are some updates to the utils package as well, so I already changed its version to a new minor 0.1.0. I added 2 new entries: /fp and /setter. /fp is for functions that help deal with immutable data, and /setter is the same but easier usage with setState().
For example:
import { filterOut } from "@solid-primitives/utils/setter";
const [stack, setStack] = createSignal<V[]>([]);
setStack(filterOut(value))

Update: added toPromise util function, it can be used like this:
const emitter = createEmitter<string>();
const event = await toPromise(emitter.listen);

// can be used together with raceTimeout from @solid-primitives/utils
import { raceTimeout } from "@solid-primitives/utils";
try {
  const event = await raceTimeout(toPromise(emitter.listen), 2000, true, "event was too slow");
  // if event is quicker:
  event; // => string
} catch (err) {
  // if timeouts:
  console.log(err); // => "event was too slow"
}


[BUG] thread 'main' panicked at src/renamer/mod.rs:278:34:

Describe the bug
thread 'main' panicked at src/renamer/mod.rs:278:34:
called Result::unwrap() on an Err value: SerdeError(Error("invalid type: integer 0, expected a boolean", line: 21, column: 19))
(after updating from 1.1.13 to 1.1.14 and updating the config.toml)
Program version?
hyprland-autoname-workspaces 1.1.14
from AUR hyprland-autoname-workspaces-git 1.1.14.r0.gf514385-1
Program configuration dump? (ideally)
{
  "version": "1.1.14",
  "class": {
    "org.kde.kcalc": "",
    "google-chrome": ""
  },
  "class_active": {
    "DEFAULT": "*{icon}*",
    "(?i)ExampleOneTerm": "{icon}"
  },
  "initial_class": {},
  "initial_class_active": {},
  "workspaces_name": {
    "10": "ten",
    "5": "five",
    "7": "seven",
    "3": "three",
    "4": "four",
    "6": "six",
    "1": "one",
    "9": "nine",
    "2": "two",
    "8": "eight"
  },
  "title_in_class": {
    "(?i)kitty": {
      "(?i)neomutt": "neomutt"
    }
  },
  "title_in_class_active": {
    "(?i)firefox": {
      "(?i)twitch": "{icon}"
    }
  },
  "title_in_initial_class": {},
  "title_in_initial_class_active": {},
  "initial_title_in_class": {},
  "initial_title_in_class_active": {},
  "initial_title_in_initial_class": {},
  "initial_title_in_initial_class_active": {},
  "exclude": {
    "": "^$",
    "[Ss]team": "^(Friends List.*)?$",
    "(?i)TestApp": "",
    "(?i)fcitx": ".*",
    "aProgram": "^$"
  },
  "format": {
    "max_clients": 99,
    "dedup": false,
    "dedup_inactive_fullscreen": false,
    "delim": " ",
    "workspace": "{id}:{delim}{clients}",
    "workspace_empty": "{id}",
    "client": "{icon}",
    "client_fullscreen": "[{icon}]",
    "client_active": "*{icon}*",
    "client_dup": "{icon}{counter_sup}",
    "client_dup_active": "*{icon}*{delim}{icon}{counter_unfocused_sup}",
    "client_dup_fullscreen": "[{icon}]{delim}{icon}{counter_unfocused_sup}"
  }
}

To Reproduce
Steps to reproduce the behavior:

call hyprland-autoname-workspaces

thread 'main' panicked at src/renamer/mod.rs:278:34: called Result::unwrap()on anErrvalue: SerdeError(Error("invalid type: integer0`, expected a boolean", line: 21, column: 19))
stack backtrace:    0:     0x64dfe8118ec5 - <unknown>    1:     0x64dfe813cfdb - <unknown>    2:     0x64dfe81163df - <unknown>    3:     0x64dfe8118c9e - <unknown>    4:     0x64dfe811a039 - <unknown>    5:     0x64dfe8119dda - <unknown>    6:     0x64dfe811a4d3 - <unknown>    7:     0x64dfe811a3b4 - <unknown>    8:     0x64dfe8119389 - <unknown>    9:     0x64dfe811a0e7 - <unknown>   10:     0x64dfe7f27193 - <unknown>   11:     0x64dfe7f27626 - <unknown>   12:     0x64dfe7f365bc - <unknown>   13:     0x64dfe7f6d458 - <unknown>   14:     0x64dfe7f6ee83 - <unknown>   15:     0x64dfe7f660f9 - <unknown>   16:     0x64dfe8110dcd - <unknown>   17:     0x64dfe7f6e4d5 - <unknown>   18:     0x73268cec9e08 - <unknown>   19:     0x73268cec9ecc - __libc_start_main   20:     0x64dfe7f27925 - <unknown>   21:                0x0 - <unknown>
Expected behavior
no panicking
Linux Distro (please complete the following information):
6.10.2-arch1-2 with hyprland-git 0.41.2.r165.2b520571-1

Confirming same behavior on Fedora Server 40

Issue is upstream in hyprland-rs: https://github.com/hyprland-community/hyprland-rs/issues/262

Is there a workaround in the meantime?

Hello, I got something working on the main branch but I have to clean it a little and we need to do a release of hyprland-rs first to be able to release too.

I release a tag for the hyprland-rs v4 alpha and create a new release.
https://github.com/hyprland-community/hyprland-autoname-workspaces/releases/tag/1.1.15


Weird chorus/flange effect

I was playing with this jambox pi for like 20+ minutes, then I stopped for a sec and played again, all of a sudden the guitar sound it had built in chorus/flange effect. I checked my pedals and nothing was turned on for chorus/flange.  I disconnected jamulus client, and connected again and same thing. Other people in the session also noticed the effect, even my voice had the same sound.  So I rebooted the jambox pi, and went back to Jamulus. It went back to normal without the chorus/flange effect.
I'm using Presonus Studio 24c.  Followed all instructions to setup but just using the 4GB version of Pi4.
Any ideas?
Thank you

This sounds like you are hearing both the sound back from Jamulus and
another source, perhaps from presonus? This can cause a chorus like effect
as is invariably slower than the other.
Could be other things but worth checking :)
On Thu, 14 Jan 2021 at 17:31, Arvin Pasamba<EMAIL_ADDRESS>wrote:

I was playing with this jambox pi for like 20+ minutes, then I stopped for
a sec and played again, all of a sudden the guitar sound it had built in
chorus/flange effect. I checked my pedals and nothing was turned on for
chorus/flange. I disconnected jamulus client, and connected again and same
thing. Other people in the session also noticed the effect, even my voice
had the same sound. So I rebooted the jambox pi, and went back to Jamulus.
It went back to normal without the chorus/flange effect.
I'm using Presonus Studio 24c. Followed all instructions to setup but just
using the 4GB version of Pi4.
Any ideas?
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kdoren/jambox-pi-gen/issues/20, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXXXG4ZLDVUBNKWJGIJVG3SZ4S5VANCNFSM4WCYUCFQ
.

This sounds like you are hearing both the sound back from Jamulus and
another source, perhaps from presonus? This can cause a chorus like effect
as is invariably slower than the other.
Could be other things but worth checking :)
On Thu, 14 Jan 2021 at 17:31, Arvin Pasamba<EMAIL_ADDRESS>wrote:

I was playing with this jambox pi for like 20+ minutes, then I stopped for
a sec and played again, all of a sudden the guitar sound it had built in
chorus/flange effect. I checked my pedals and nothing was turned on for
chorus/flange. I disconnected jamulus client, and connected again and same
thing. Other people in the session also noticed the effect, even my voice
had the same sound. So I rebooted the jambox pi, and went back to Jamulus.
It went back to normal without the chorus/flange effect.
I'm using Presonus Studio 24c. Followed all instructions to setup but just
using the 4GB version of Pi4.
Any ideas?
Thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kdoren/jambox-pi-gen/issues/20, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXXXG4ZLDVUBNKWJGIJVG3SZ4S5VANCNFSM4WCYUCFQ
.

I have heard things like that if the USB interface isn't reliably sending/receiving its data in time (this can come and go).  The remedy in that case is to increase NPERIODS in /etc/jackdrc.conf   ("sudo leafpad /etc/jackdrc.conf" will bring up a GUI editor.).  In 1.2.0 release I increased NPERIODS to 8 to try to keep people out of trouble.  This should work with almost all interfaces, but if you decreased it (to lower latency) you may have lowered it a bit too much.
You could alternatively try setting PERIOD=128 and cutting NPERIODS in half or a bit higher, but I recommend 64 if your interface works with it (then you have the "small network buffers" option available in Jamulus).

I have heard things like that if the USB interface isn't reliably sending/receiving its data in time (this can come and go).  The remedy in that case is to increase NPERIODS in /etc/jackdrc.conf   ("sudo leafpad /etc/jackdrc.conf" will bring up a GUI editor.).  In 1.2.0 release I increased NPERIODS to 8 to try to keep people out of trouble.  This should work with almost all interfaces, but if you decreased it (to lower latency) you may have lowered it a bit too much.
You could alternatively try setting PERIOD=128 and cutting NPERIODS in half or a bit higher, but I recommend 64 if your interface works with it (then you have the "small network buffers" option available in Jamulus).

I believe this may have been caused by the use of the jack "-s" (softmode) argument in Jambox 1.3 and earlier versions. I removed this argument in Jambox 1.4 and later, which has fixed similar problems.


Add a Gitter chat badge to README.md

bigdatagenomics/mango now has a Chat Room on Gitter
@erictu has just created a chat room. You can visit it here: https://gitter.im/bigdatagenomics/mango.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

Can one of the admins verify this patch?


Unsure how to diagnose this one

I installed Mojave on a fresh system, install Homebrew, installed brew-gem and ruby with brew (no system-level commands).
I'm trying to install aws-assume-role and it seems to get hung up on the keyring dependency. None of the files/directories in /usr/local/Cellar/, $HOME/Library/Logs/Homebrew/, or $HOME/Library/Caches/Homebrew/ for this particular gem existed prior:
$ brew gem install aws_assume_role --homebrew-ruby
==> Fetching aws_assume_role from gem source
Fetching: aws_assume_role-1.2.1.gem (100%)
Downloaded aws_assume_role-1.2.1
Warning: Cannot verify integrity of aws_assume_role-1.2.1.gem
A checksum was not provided for this resource
For your reference the SHA256 is: 56a07ac6468be291a80564645b8434c041f7e818d556cdeaa1b60fbf510725f9
==> /usr/local/bin/gem install /Users/alan/Library/Caches/Homebrew/aws_assume_role-1.2.1.gem --no-ri --no-rdoc --no-wrapper --no-user-install --install-dir /usr/local/Cellar/gem-aws_assume_role/1.2.1 --bindir
Last 15 lines from /Users/alan/Library/Logs/Homebrew/gem-aws_assume_role/01.gem:

    current directory: /usr/local/Cellar/gem-aws_assume_role/1.2.1/gems/keyring-0.4.1/ext
/usr/local/opt/ruby/bin/ruby mkrf_conf.rb
*osx: installing ruby-keychain

current directory: /usr/local/Cellar/gem-aws_assume_role/1.2.1/gems/keyring-0.4.1/ext
rake RUBYARCHDIR=/usr/local/Cellar/gem-aws_assume_role/1.2.1/extensions/x86_64-darwin-18/2.5.0/keyring-0.4.1 RUBYLIBDIR=/usr/local/Cellar/gem-aws_assume_role/1.2.1/extensions/x86_64-darwin-18/2.5.0/keyring-0.4.1
Ignoring ffi-1.9.25 because its extensions are not built.  Try: gem pristine ffi --version 1.9.25
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems.rb:241:in `bin_path': can't find gem rake (>= 0.a) (Gem::GemNotFoundException)
	from /usr/bin/rake:22:in `<main>'

rake failed, exit code 1

Gem files will remain installed in /usr/local/Cellar/gem-aws_assume_role/1.2.1/gems/keyring-0.4.1 for inspection.
Results logged to /usr/local/Cellar/gem-aws_assume_role/1.2.1/extensions/x86_64-darwin-18/2.5.0/keyring-0.4.1/gem_make.out

The /usr/local/Cellar/gem-aws_assume_role/ directory doesn't exist for further inspection. Contents of /Users/alan/Library/Logs/Homebrew/gem-aws_assume_role/ available here but I'm not sure provides much detail. How can I help troubleshoot or diagnose?

If I run HOMEBREW_DEBUG=1 brew gem install aws_assume_role --homebrew-ruby and choose shell and run the command /usr/local/bin/gem install /Users/alan/Library/Caches/Homebrew/aws_assume_role-1.2.1.gem --no-ri --no-rdoc --no-wrapper --no-user-install --install-dir /usr/local/Cellar/gem-aws_assume_role/1.2.1 --bindir /usr/local/Cellar/gem-aws_assume_role/1.2.1/bin I get the same error as expected. Sure enough, the rake gem isn't listed:
bash-3.2$ gem list
Ignoring ffi-1.9.25 because its extensions are not built.   But there is nothing in /usr/local/Cellar/ when I quit. Not sure how to continue; any help appreciated, thanks.

I think I sorted this out; in the debug brew shell, GEM_HOME and GEM_PATH are set to /usr/local/Cellar/gem-aws_assume_role/1.2.1 and rake isn't in there. So, I believe this to be a problem with the gem I'm trying to install not having rake as a dependency. I'll take it up with them.
I'll close, but here are my install steps for anyone else who may stumble upon this:
brew install brew-gem

{ BREW_GEM_TEMPDIR=$( mktemp -d 2>/dev/null || mktemp -d -t 'brew_gem_tempdir' )
  echo "BREW_GEM_TEMPDIR=$BREW_GEM_TEMPDIR"
  export BREW_GEM_TEMPDIR ; }

# In another shell, run...
{ HOMEBREW_DEBUG=1 brew gem install aws_assume_role
  rm -rvf /private/tmp/gem-aws_assume_role* ; }
# This fails. When the menu for choosing one of five options, sit here and don't exit yet...

# Copy the generated brew formula to our temporary directory
cp \
  -avn \
  "${TMPDIR%/}/gem-aws_assume_role.rb" \
  "${BREW_GEM_TEMPDIR%/}/gem-aws_assume_role.rb"

# Switch back to the brew shell and Exit with Ctrl+d; can close this shell entirely

sed -e 's/\(cached_download\)/"rake", \1/' -i '' "${BREW_GEM_TEMPDIR%/}/gem-aws_assume_role.rb"

HOMEBREW_NO_AUTO_UPDATE=1 brew install "${BREW_GEM_TEMPDIR%/}/gem-aws_assume_role.rb"

{ rm -rv "${BREW_GEM_TEMPDIR:?}"
  unset BREW_GEM_TEMPDIR ; }


Refactor-add context to grpc reqests

Closes: https://github.com/stacklok/minder/issues/581
This PR adds Context to most of our RPCs.
As part of this, it also reverts one of the changes in https://github.com/stacklok/minder/pull/1831 to make the "provider" field optional. This is due to the constraint of optional fields not being allowed to be used as path parameters.

Closing in favour of: https://github.com/stacklok/minder/pull/1911


Issue with Larod API

Axis product/device: P1375
Device firmware version: AXIS OS version 10.5.2
Issue description: I tried a few examples such as the hello-world and web-server and it works as intended, however when I tried the vdo-larod example, I encounter an issue and this is the log:
/usr/lib/liblarod.so.1: version `LIBLAROD_3.0.0' not found (required by /usr/local/packages/vdo_larod/vdo_larod)
I followed the instruction correctly, not sure how I could fix it or upgrade liblarod.

The examples use the latest release ACAP SDK 4.1 where the image acap-native-sdk has tag 1.1 and this is compatible with AXIS OS 10.9 or higher. Installing the vdo-larod example on AXIS OS 10.9 or higher should solve the problem with a newer version of liblarod not available.
For more information on SDK and AXIS OS compatibility, see the ACAP 4 compatibilty documentation and the 4.1 release notes.

Upgraded my OS version and it was fixed, thanks!

Upgraded my OS version and it was fixed, thanks!


Add union extension method

#30 Add Union Extension Method.
Please review and merge if you love it !!

Thank you for your contribution. Happy hacking 🎃


help me

anyone can give me example code to parser all data?
i got
Fatal error: Cannot use object of type DigitalOceanV2\Entity\Droplet as array in C:\xampp\htdocs\digitalocean\index.php on line 111

Parse what data? Be more specific. Also, it would help as if you show as around line 111

@screamolic data passed back is in object format, sounds like you are trying to use it as an array.  It'd be helpful to see the code you are talking about, as that would help us point you in the correct direction.

@screamolic can you show us some code? with a clearer description of your issue?

sorry my bad. im still learning php. i need more example.  :)


Manually rebuilt gh-pages

Checklist

[x] I have read the Contribution & Best practices Guide.
[x] My branch is up-to-date with the Upstream development branch.

Short description of what this resolves:
Fixes gh-pages rebuild issue.

Fixes #1716

@geekyd @mariobehling please review this.I guess this would resolve the issue, because file commiting the changes, there were some conflicts to be resolved.That's why I think travis was not able to push to this branch.


Add documentation for CLI profiles

It's currently very hard to work with multiple accounts and users need to log in and out of accounts.

We already have this feature in the latest version!
Leaving this issue open to write documentation for it.

Create profiles:
# Log in to a second account called "tudor" that connects to production
xata auth login --profile tudor

# Log in to staging with a profile called staging
xata auth login --profile staging --host staging

# Log in to local docker
xata auth login --profile local --host http://localhost:6000/,http://{workspaceId}.localhost:6000

Use a different profile with flag:
# Use a different profile per command
xata import csv --profile staging ...

Use a different profile with env var:
set -x XATA_PROFILE staging
xata import csv ...

Delete profiles:
# Log out (delete) from a given profile
xata auth logout --profile tudor

@SferaDev I think we're missing the --profile option for xata init.
I don't see a way to init with a profile other than the default.

kostas@Kostass-MacBook-Pro tests % xata auth login --profile personal
✔ Authentication is already configured for the personal profile, do you want to overwrite it? … yes
✔ Do you want to use an existing API key or create a new API key? › Use an existing API key
✔ Existing API key: … *************************************
i Checking access to the API...
✔ All set! you can now start using xata

kostas@Kostass-MacBook-Pro tests % xata init
🦋 Initializing project... We will ask you some questions.

? Select a workspace ›
❯   ...list of workspaces from the default profile, not personal

there's no --profile argument available for xata init

It's possible, we need to clean up global flags because I think there might be more subcommands that lack this option

Keeping this issue strictly for documentation, started another one for the missing flags/cleanup: https://github.com/xataio/client-ts/issues/841