Design error when input is not valid for new import panel

In the current one:

sorry @xavijam , but I didn't understand the issue. What should be the correct design?
Also, if you enter an URL (starting with: http:) it works (synced tables)

lol, this is for @saleiva, not for yours... sorry mate!
:D

There we go.
Please not that the desired behaviour is that when typing the URL we hide with a fade out the bottom part that was about selecting a file. To see it back, user should clear the content of the URL input.

Sorry, correct version now uploaded

ok deal, closing this.


Update .yaml files to new form

I think it has been done already, in fact it was done more than once


Updated images for README.md

Using github instead of dropbox.... technically git has no dependency on github but github is still a better dependency than dropbox..

Updated in 74e3630dfba92a3ce092b508c099e9090e759ee2


Feature Request - Navigation (Menus)

This design is very nice.  I think this framework could really grow and be a major part of the vue family.  It really needs the basics like the information on grid/layout and navigation controls (menu).
Great work so far!

thank you very much friend that I hope, well I am in process in that aspect to deliver a complete job thank you very much for the support as soon as you finish notice by my twitter so you can try it and implement it


get_releases for Pagure

services.github.py already can list all releases. We need this for Pagure too.

We can mark this as a duplicate to #112.
I'll update the comment to support get_releases as well...


Initial docs for DockLayout

This PR complements CommunityToolkit/Maui#635 and provides documentation for DockLayout layout feature.

Learn Build status updates of commit f601e0d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/maui/layouts/DockLayout.md
:warning:Warning
View
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md

Line 3, Column 9: [Warning: author-not-found - See documentation] Invalid value for author: 'Thilo Viereck (profix898)' is not a valid GitHub ID.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@microsoft-github-policy-service agree

Learn Build status updates of commit 4b52050:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit a66b838:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 6f3009a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit e0b6ae8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 77a15be:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit e5e50d5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 185d40d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@bijington: Thanks for your comments and suggestions. It's kind of noisy/messy here with opbld32 and prmerger-automator stepping in after each commit, but I think I caught all requested changes or left a comment for you ;)

Learn Build status updates of commit c76ad3c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@bijington: Thanks for your comments and suggestions. It's kind of noisy/messy here with opbld32 and prmerger-automator stepping in after each commit, but I think I caught all requested changes or left a comment for you ;)

yeah sorry about those pesky bots, they make a load of noise sadly

Learn Build status updates of commit 5084ded:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 95bf847:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 0f075bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 77f66ee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 2e4f4fb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/images/layouts/DockLayout.svg
:white_check_mark:Succeeded
View

docs/maui/layouts/DockLayout.md
:white_check_mark:Succeeded
View

docs/maui/layouts/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Indentation of the third C# box ({ new Button { Text = "Center" } },) is off (too far left) in GitHub preview, but looks Ok locally.

Indentation of the third C# box ({ new Button { Text = "Center" } },) is off (too far left) in GitHub preview, but looks Ok locally.

Yeah that parts annoying, it's a diff between tabs and spaces but if it looks fine on the preview which Gerald posted and it does then it'll work fine on the site


Update README.md to remove zellij bug disclaimer as it has been fixed

Removed redundant notes about the inability to bind C-j in Zellij, referencing a known bug that has since been fixed. Also adjusted the flow of sentences for better comprehension.

Thanks!


Fix new user register with custom fields (RegisterController.php)

Get only active and displayed UserFields.
Current code UserField::all() generates an exception 'cause it tries to get all custom user fields even they are not displayed at register form or not active at all.

May closed #1219
(No details provided there but that error also may be related with this bug too)


Change polar cap boundary highlighting

PT: [#180335792]
Demo: https://tectonic-explorer.concord.org/branch/polar-boundary/index.html

So, I bet your issue that we talked about was related to plate re-rendering, right? Sorry I didn't catch it.

Yes, I spent a while debugging presumed problems in my highlighting code before figuring out that the highlighting code was working fine but all of the necessary plates weren't re-rendering.


AWS access denied when running download_plugins.sh

I would like to build docker images on my own for future contributions.
I can't download plugins using download_plugins.sh resulting with Access Denied.
Should I have some special permissions to the s3 bucket to download them?  I'm logged in on my personal credentials on AWS CLI.
$ bash download_plugin.sh
[..]
++ aws s3api list-objects --bucket artifacts.opendistroforelasticsearch.amazon.com --prefix downloads/elasticsearch-plugins/opendistro-sql/opendistro_sql-1.10.0 --query 'Contents[].[Key]' --output text
++ sort
++ tail -n 1

An error occurred (AccessDenied) when calling the ListObjects operation: Access Denied

Hi @irslon,
As of now, we have not decouple the scripts with our own credentials on AWS.
We are planning to do that in the future so everyone can create a distro by running these scripts.
Sorry about the inconvenience.
Thanks.

Hi @irslon,
It has been nearly a month since we last talk.
This issue will be closed for now, but please feel free to re-open if you have more questions to this topic.

Hello @peterzhuamazon
I have just created an issue in the opendistro forum on the same topic:
https://discuss.opendistrocommunity.dev/t/open-distro-build-with-plugins/4271
I am interested in a solution on how to build the docker images including plugins.
The two builds download_kibana_plugins.sh and download_plugins.sh do not work at the moment.
I would like a workaround so that the plugins are included in the build. Can you give me
a practical example for one plugin on where to copy the plugin source in the opendistro-build project ?
And then how it needs to be referenced in the project, for instance in a fille called
kibana/docker/build/kibana/plugins/plugins_kibana.list
Best regards.

Hi @nperon like we talked last time we are building a new solution for both us and users to build distros on their local.
However, this is a rather long term project as many of the structures/scripts/workflows require rewrite.
We are not having a defined date on the release of this. Please stay tune.
In the meantime, you are welcomed to directly create a new dockerfile based on our image and do modifications.
That should be a workaround before we introduce the new structure.
Sorry about the inconvinience you experience here.
Thanks.


pkg/meta: @visibleForCodegen

Example
// foo.dart.

@visibleForCodegen
final someField = new Foo();

// foo.g.dart

import 'foo.dart';

// Refer to `someField` without a warning.

Rationale
Without using partial files (part/part of ), it's impossible to use private (_) variables, which forces developers to write pseudo-public code so that it can be accessed by code generation. However, it serves no other use, and might not even be part of a fully tested public API suite.
@visibleForCodegen would mean:

An annotated class, field, or method may be referenced in the same Dart library.
An annotated class, field, or method may be referenced in a different library if it is generated

This can be by convention, i.e. foo.dart and foo.g.dart or foo.template.dart
Or explicit, i.e. another @generated annotation on the generated file

Alternatives
Something like @friendly, which means "public to the same package". This is ~the same as @visibleForTesting, except without any requirement for it to be only used in the test/ directory.
/cc @kevmoo @alorenzen

Language team:
I think it's rather telling that we have several requests for annotations to effectively broaden the visibility control within the language, things such as @protected, @visibleForOverriding, @visibleForTesting, and now @visibleForCodegen. Should we extend the language to cover some or all of these questions, or continue to add annotation-based checking to the analyzer?

The annotations story seems kinda just broken without mirrors.
When its possible to do
@MyAnnotation(_foo)

and the only non-deprecated way that that can be used in the browser is via codegen, which cannot access that value (_foo), and therefore will either produce broken code or have to (the author of each code generator must write this check) detect that '_foo' is private and raise a custom error, in either case the developer needs to make "_foo" public and add a special privacy annotation to it instead.
One possible solution is to make private disallowed inside annotations, which is a breaking change and not necessary for those using mirrors. (and has a lot of edge cases... @_foo, @x(() => _foo}), etc.)
I'd say the real solution is that annotations have been gutted too much, and either should be replaced (not seriously suggesting this) or a static, tree-shakable API for accessing annotation data and/or annotated data should be developed. Wherein you could simply say something like<EMAIL_ADDRESS>which would be the constant value of _someField, no privacy rule changes required, purely static so that all unused X.@Foo data is discarded by dart2js.
Maybe both of these things should be done at once? Decide what to do about annotations long term, while this privacy change thing is introduced temporarily?

@bwilkerson:

Language team:
I think it's rather telling that we have several requests for annotations to effectively broaden the visibility control within the language, things such as @protected, @visibleForOverriding, @visibleForTesting, and now @visibleForCodegen. Should we extend the language to cover some or all of these questions, or continue to add annotation-based checking to the analyzer?

Thanks for bringing this up. BTW, this is no way a "we must have this annotation", but rather just trying to used established mechanisms (analysis with a common annotation) to get around a problem folks have been reporting.
I personally think Dart should invest in actual visibility control, but beyond this thread maybe?
/cc @leafpetersen @floitschG @munificent

@MichaelRFairhurst: I think we should keep what the point of annotations are outside of this thread, I don't want to expand scope beyond this particular request and today's tooling.

I think it's rather telling that we have several requests for annotations to effectively broaden the visibility control within the language, things such as @protected, @visibleForOverriding, @visibleForTesting, and now @visibleForCodegen. Should we extend the language to cover some or all of these questions

Yes, I personally think we should consider more fine-grained access control modifiers. Keeping things simple is good, but it's possible to be too simple. My five-minute sketch would be to add:

Protected, which treats the identifier as public (i.e. not name mangled like private identifiers), but makes it a static error to invoke the member when the enclosing class is not a subclass of where the member is declared.
Given that privacy is library based, it might be worth considering making this more library based as well. Something like all protected identifiers in library A are visible inside the bodies of classes in library B as long as they subclass some class in library A. I think that might open up some interesting and useful patterns and give you something akin to "family protected".
We'd have to decide how this interacts with dynamic callsites. I'm not too picky since I don't consider those very important.

Friend libraries, which give other libraries access to a library's private identifiers. This would let you do white box testing by having your test library be a friend of the main library. It should also help with generated code.
I know it's anathema to some, but I would allow a library to declare itself to be a friend of some other library. This prevents a library from encapsulating itself, but it means a test can crack open a library without the main library having to mention its test libraries. I don't look at access control as a strict security system — you can always modify the source anyway — and more of a velvet rope indication "you aren't supposed to be here".
The semantics and syntax of this are really tricky though. You need some way of disambiguating private identifiers which may clash with the main library's.

@munificent:

I think it's rather telling that we have several requests for annotations to effectively broaden the visibility control within the language, things such as @protected, @visibleForOverriding, @visibleForTesting, and now @visibleForCodegen. Should we extend the language to cover some or all of these questions

Yes, I personally think we should consider more fine-grained access control modifiers. Keeping things simple is good, but it's possible to be too simple. My five-minute sketch would be to add:

Protected, which treats the identifier as public (i.e. not name mangled like private identifiers), but makes it a static error to invoke the member when the enclosing class is not a subclass of where the member is declared.
Given that privacy is library based, it might be worth considering making this more library based as well. Something like all protected identifiers in library A are visible inside the bodies of classes in library B as long as they subclass some class in library A. I think that might open up some interesting and useful patterns and give you something akin to "family protected".
We'd have to decide how this interacts with dynamic callsites. I'm not too picky since I don't consider those very important.

I don't consider dynamic call sites important, so +1 from me.

Friend libraries, which give other libraries access to a library's private identifiers. This would let you do white box testing by having your test library be a friend of the main library. It should also help with generated code.
I know it's anathema to some, but I would allow a library to declare itself to be a friend of some other library. This prevents a library from encapsulating itself, but it means a test can crack open a library without the main library having to mention its test libraries. I don't look at access control as a strict security system — you can always modify the source anyway — and more of a velvet rope indication "you aren't supposed to be here".
The semantics and syntax of this are really tricky though. You need some way of disambiguating private identifiers which may clash with the main library's.

It wouldn't really be private, right? It would be public except a static error to reference outside of certain libraries, and obviously tools like dartdoc could take advantage of this knowledge to avoid generating public APIs, etc.

It wouldn't really be private, right? It would be public except a static error to reference outside of certain libraries

I was thinking it would actually be private. That ensures you don't run into accidental name collisions when, say, inheriting from the class in a non-friend library. But, again, it's only a half-formed sketch. Making it more public-ish might be a better approach.


Criterion negation enhancements

Add explicit negation methods for many of the standard criterions. E.g. in(...) now has a notIn(...) counterpart, like(...) has notLike(...), etc. Each of these criterions will also generate more readable SQL when negated. Refs #116.

LGTM


Change title for "Cleaning Up Clusters" section

The section on Cleaning Up Clusters can use a different title. It's not about cleaning a cluster - it's about disconnecting a node from a Rancher-launched cluster and deleting all of the Kubernetes bits from it, returning it to a (mostly) clean node that can be used for something else.
It also needs a prominent warning at the top that this is about deleting Kubernetes from a node.
(See rancher/docs#2040 for overall context)

This issue is addressed by https://github.com/rancher/docs/pull/2133
The title of the section is now "Removing Kubernetes Components from Nodes."
The top of the section now says:

This section describes how to disconnect a node from a Rancher-launched Kubernetes cluster and remove all of the Kubernetes components from the node. This process allows you to use the node for other purposes.

I didn't make it a warning because the message now aligns with the title.


[Consolidated] Rewrote the dispatcher reconciler

Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>Fix #245

Proposed Changes

:broom: Now we reconcile one channel at the time, more than doing a global resync every time
:broom: Removed some bad concurrency patterns on the hot path
:broom: Implemented CleanupChannel in dispatcher

/retest

@slinkydeveloper seems like the race I was talking about is happening. This will show up when concurrent tests are running in parallel

seems like the race I was talking about is happening. This will show up when concurrent tests are running in parallel. You see in the test logs that they can't the channels they expect and I believe that's cause a previous "unsubscribe" deletes that channel somehow. Irrelevant channels disappear from the cache.

I guess the finalizer kind surface it right? What do you want me to do?

I guess the finalizer kind surface it right? What do you want me to do? May I help somehow? Should I go forward with this PR or not?

yeah, seems very nasty to me but I believe we need to fix it. Are you game to dig this one out? Maybe give it a shot and see if you'll be able to figure out where the race is?

@devguyio Ok will try

/assign
@slinkydeveloper lmk when I can review, I took an initial look

@devguyio You can start looking at it :smile: In my ideal world, e2e tests should pass :laughing:

I had a look and it seems fine.
I am working on KafkaChannel dispatcher since some time but I cannot review this PR properly. Pretty much everything changed.
There are fundamental changes but I trust your judgement. If the tests pass, I am fine with the PR.

I am working on KafkaChannel dispatcher since some time but I cannot review this PR properly. Pretty much everything changed.

I know, I'm sorry if I was drastical, but I saw no alternative to properly fix the whole dispatcher process which was racy and was leaving garbage...

I know, I'm sorry if I was drastical, but I saw no alternative to properly fix the whole dispatcher process which was racy and was leaving garbage...

As I wrote earlier, I trust your judgement. If the tests pass, I am fine with the PR.
Thanks!

/cherry-pick release-0.20
/cherry-pick release-0.21
/cherry-pick release-0.22

/cherry-pick release-0.21

/cherry-pick release-0.22

LGTM, leaving the approval to @devguyio

/lgtm
leaving approval for others

/hold
until other give approval

@slinkydeveloper there is a conflic w/ the 0.20 branch /cc @devguyio

/cherry-pick release-0.21

I will manually cherry pick for 0.21 and 0.20


Adding openmp image

https://advanced-micro-devices-demo--2323.com.readthedocs.build/en/2323/reference/openmp/openmp.html#openmp-toolchain

https://advanced-micro-devices-demo--2323.com.readthedocs.build/en/2323/reference/openmp/openmp.html

Would it be possible to have git friendly formats instead of binaries.
A vector format would be event better.
What about SVG?

@keryell Thank you for your feedback. Let me check and get back to you.


dev: main docker-compose file

What
Fix the main docker-compose file.
Why
The docker-compose file was failing to up the services because the Kafka service wasn't being referenced on the file.
Known limitations
N/A
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[ ] This PR adds tests for the new functionality or fixes.
[ ] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[ ] This is not a breaking change.
[ ] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr137.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr137.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr137.previews.kube001.services.stellar-ops.com


nginx proxy_log_format

In the nginx snippet the proxy_log_format is used. Would you mind  sharing that one too?
Thanks for your great work :)

Sure, here it is:
log_format proxy_log_format '[$time_local] $remote_addr - $remote_user - $server_name  to: $upstream_addr: $request upstream_response_time $upstream_response_time msec $msec request_time $request_time';

I will also add it to the nginx snippet in the repo :)


Add eslint and prettier workflows

I think adding a linter and prettier would be fruitful in the long run as the codebase grows. It will also help keep the code uniform for all the contributors and maybe even introduce first-timers to these concepts.
We can add Github Actions workflows as well.

I thought of that, too. that's a good idea!

Sounds great!
@JapneetSingh5 do you want to grap this one and pass the #16 to another person or do you want to pass this one here to someone else?

Yeah sure, no problem!

Very good ideia, @JapneetSingh5! I'm on it! Thanks for this opportunity!

Awesome!
The issue is yours, @eduardomrodrigues .!
Tell me if you need any special access on the repo to make this configurations.
@JapneetSingh5 would you like to point any particular projects as references?

I follow this gist myself, I generally use the airbnb style guide.
https://gist.github.com/bradtraversy/aab26d1e8983d9f8d79be1a9ca894ab4

The project has this eslint-config-react-app, I learn about it and, for me,  it's sufficient, can be configurable and we don't have to eject the project.
This Prettier and Style guided are awesome.
I'll put this all together and make a proposition for you


Data is not loading from service.

sport.ts
export interface Sport { 	id: number; 	name: string; }
sportservice.ts
export class SportService {   getSport(): Promise<Sport[]> {     return Promise.resolve(SPORTS);   }  }
component.ts
options: Sport[] =[]; config: any = {        create: true,      maxItems: 5,     plugins:["dropdown_direction","remove_button"]   }; placeholder: string = 'Search Sports'; getSports() {        this.sportservice.getSport().then(results=> this.options = results); } call getSports() in OnInit()
component.html
<ng2-selectize [config]="config" [options]="options" [placeholder]="placeholder" [(ngModel)]="sports" name="sports" ngDefaultControl></ng2-selectize>

Hi @theromie, i'll take a look at this and let you know soon

@theromie I couldn't reproduce any issues with this, seemed to work ok as far as I could tell. I committed the example to https://github.com/NicholasAzar/ng-selectize-demo/commit/7d284b7d03b963f00b21b059d3da0eddc3f8a461 if you want to compare yours against it. Closing this for now.


Include PodSpec.nodeName as a label in goldpinger_peers_response_time_s_* metrics

Hey guys!
Happy New Year!!! 🎉
Super cool project, we've recently deployed this in our clusters and it's proving to be super useful.
I was wondering if it would be possible to add a nodeName label to these (goldpinger_peers_response_time_s_*) metrics so it would be easier to identify the target nodes being probed.
the node name should be available in the PodSpec.nodeName

Super cool project, we've recently deployed this in our clusters and it's proving to be super useful.

Glad we could help !
I don't see why not - it would put some extra strain on Prometheus with the extra time series, but it would indeed make for better graphs and alerts.
👍

👍
seeing at the source, it seems the code only care about HostIP of ping targets (at least in the prometheus metrics). I believe it'd be more useful when debugging issues if we can somehow give more context of the target nodes.
In the monitoring dashboard/alerting, instead of this

"node A and B are reporting that some other unknown nodes are down"

this would be better

"node X and Y are reported down by 2 nodes"

Hey @seeker89 :smile:
Do you think this is something you would consider implementing in the near future? we particularly feel the this is missing for alerting, where we know some node(s) are unhealthy but can't pinpoint from the metrics.

Hey @dannyk81 !
Now, that we've merged https://github.com/bloomberg/goldpinger/pull/53 in I think we can add some more context to the metrics.
So, just to make sure I understand what your use case is - what extra labels on which metrics do you need ?

Great news!
I'll try and summarize our current experience:

goldpinger_peers_response_time_* - these metrics have the pod_ip and host_ip labels of the pod being probed, but not the host_name.

goldpinger_nodes_health_total - this metric is useful, however currently very difficult to use (for alerting and troubleshooting), since it provides a way to alert when nodes are misbehaving but the challenge is how to identify that node? actually, right now we have an alert in one of our clusters but we can't deduct from the metrics which node is actually misbehaving, we just know that one node is unhealthy (this relates to @akhy's comment I believe)

wdyt @seeker89?
I tried going through the code yesterday to see if I could work out how to implement this, but to be honest getting a bit lost... it seems like the podIPs (and hostIPs) are used as primary identifiers almost everywhere and passed around in ad-hoc maps, I suppose we'll need to define a struct for that and use it throughout the code?
Generally, I think it would be great if we could substitute pod IPs with pod names and host IPs with host names (probably keeping the IP data as well though, but make it secondary) because having just the IP addresses displayed is rather confusing.
It would be (at least in my pov) so much more human friendly if the metrics and the UI (graph, heatmap, etc..) referenced the pod names + host(node) names, instead of plain IPs.
Sorry if I'm going out of scope here.

Some good points here. I'll have a look when I get some free bandwidth. 👍

@seeker89 just curious if you had a chance to look into this? :pray:

Sorry, not yet. I did set some time for goldpinger next week, might be able to get into this.

This tells you if a node is fubar:
    - alert: goldpinger-node-down
      expr: |
        sum(goldpinger_peers_response_time_s_sum{job="goldpinger"})
        BY (pod, goldpinger_instance, host_ip) > 0.5
      for: 1m
      annotations:
        description: |
           Goldpinger pod {{ "{{ $labels.pod }}" }} on node {{ "{{ $labels.goldpinger_instance }}" }} cannot reach remote node at IP {{ "{{ $labels.host_ip }}" }} in less than 500 ms!
        summary: Node {{ "{{ $labels.host_ip }}" }} either fubar or down!
      labels:
        severity: critical

An example latency check that works well!
    - alert: goldpinger-node-latency
      expr: |
        sum (rate(goldpinger_peers_response_time_s_sum{call_type="ping"}[1m]))
        by (goldpinger_instance, host_ip, pod) > 0.040
      for: 1m
      annotations:
        description: |
           Goldpinger pod {{ "{{ $labels.pod }}" }} on node {{ "{{ $labels.goldpinger_instance }}" }} cannot reach remote node at IP {{ "{{ $labels.host_ip }}" }} in less than 40 ms!
        summary: Node {{ "{{ $labels.host_ip }}" }} likely fubar.  Overlay network latency should be less than 40ms!
      labels:
        severity: critical

Any update?


tests: Make few non-ztest tests match the standard testsuite output

We have a few tests in the testsuite which don't use ztest framework for various reasons. However, make them produce output compatible with ztest output. This is useful for automated CI systems (which e.g. use regexes to validate test output).

Issue e.g. seen with Linaro LAVA which uses regexes to parse test output and fails to detect testcases in this test: https://staging.validation.linaro.org/scheduler/job/287314 .

Having ideas for even more refactors, converting to draft for now.

Found another case of output format mismatch, so made deeper refactors to make it consistent.

@nordic-krch

note that no-multithreading test is converted to ztest in #34279.

Didn't know, thanks for the pointer. So, would you prefer me to remove it from this PR, or there's a chance that it might not fit into 2.6, so this one can stay and you'll rebase later?

@pfalcon keep it, if my PR goes in it will basically replace it. It was just a note.


libopenblas

Installed pymaster with conda-forge "successfully" but then received this at import:
ImportError: libopenblas.so.0: cannot open shared object file: No such file or directory
Linux Ubuntu 18.0
Did this:
sudo apt-get install libopenblas-dev
and all seems happy again.  Just thought I'd share.

Thanks! I hadn't encountered this before. I'll add it to the docs.


See the overview of products/Models in a grid

User story

As a User
I need to see all the products/models and their pictures
So that I can select my desired product/model

Acceptance criteria

I see all the products of the category that I have chosen in a grid
Grid items have a picture

Since we have only one model for each product we are going to only show the products yet

In the future, if there are more models we will implement a dropdown menu where user can choose the model

We could maybe use https://material-ui.com/components/grid-list/ to do so

However I tend towards using https://material-ui.com/components/grid/ and the /grid-list Since I already worked with those (especially the layout tags are quite familiar to me)

Regarding #29:
Material-UI also provides a customizable Table (MIT Licenced)
https://material-ui.com/components/data-grid/

Thanks for the info that you have provided. I thought we could use image card components. We could also use this one as well  https://material-ui.com/components/grid-list/. Lets have a look at them both. Thanks for exchanging info.

for instance ,https://material-ui.com/components/cards/. We can also easily add the dropdown box there at the bottom


Upgrade to FHIR DSTU3 3.0.0

Will this be upgraded to latest FHIR spec? :
https://www.hl7.org/fhir/directory.html

Yes. We're working on it. We're upgrading to 3.0.1 on the fhir_3 branch which hasn't been merged yet.

@jawalonoski That's great.  When do you think it will be ready to be merged?  Great project.

+1
No pressure but I am desperately waiting for that as well. ;-)

We have a branch with STU3... I just need to review it and merge it into master. Probably this week.


complete chinese translation

Coverage remained the same at 82.165% when pulling 3408b83847a0a9efaa2782062152cd277500fdf2 on tcloudata:master into 7d276928286687e528318532a9a26ceb597203b5 on airbnb:master.

Coverage remained the same at 82.165% when pulling 49a52296d42f9b0a3e720090288c4780b6ef2b4f on tcloudata:master into 7d276928286687e528318532a9a26ceb597203b5 on airbnb:master.

Also I'm not quite sure why this broke the build... maybe rebasing would help?

Build fails. Please re-open a clean PR when ready.


Buy firo cleanup

Removed some exchanges that has gone down.
Added NodeHub.io to the masternode guide list.

Did not see nodehub.io when scrolling through the list. My eyes deceived me.


Additional Error Handling and Tracing for failures

Update Nuget libraries
Add MS-CorrelationId and MS-RequestId headers to help with tracing issues
Add more printouts on error including the CorrelationId and RequestId
Update wait logic to complete when a 'signedPackage' is ready instead of looking for specific string states

Approved.


Block count for an account

Chance to get the number of blocks for each account, without using "chain" call which return hash too.

Yes, this would be easy and make it more efficient.  A new RPC and test that takes in an account number or hash and counts the number of previous-links until the open block; the RPC would return the count.

6dc7d236761c4b519066c575ec8da08be5e646ff


Ability to set meta terms and filter by them in the React app

Related #2203

I have completed UI related changes for meta terms. I did the development with mock APIs.
I need below meta term APIs
API to fetch all existing meta terms
{
name: "mt1"
id: "mt1"
children: [
{
name : "mt1 - child",
id: "mt1-child",
children: [...]
}
],
...
}
Existing submission API should return the linked meta terms
meta_terms: [
{
'id': meta_term.id,
'name': meta_term.name,
'parent': meta_term.get_parent().name,
'parent_id': meta_term.get_parent().id
},
...
]
An API to update metaterms of a submisson
POST body
[id1, id2, ...]

feature/add-meta-terms-react is the branch name which has UI changes


Revert to put widget_class in the data portion of comm message

Resolves #522

@SylvainCorlay and @jasongrout I think this is what you guys meant with keeping it symmetric. Both sides are now using the data portion of the comm message to share widget-class during the comm_open.

@lbustelo I am 👍 on this change generally, and I would like to push out a 5.0.1 or 5.1.0 pretty quickly with that change so that you guys can iterate.
@jdfreder @jasongrout it is time to say something !

@SylvainCorlay: I have this to say. Can we please merge my 6.x branch to master? :)
This looks okay to me, but I haven't thought a lot about ramifications, nor have I tested it.

I think this is okay, as long as the information is available on comm open.

I tested the changes with R and Scala and with this I'm able to continue adding the declarativewidgets support in top of the widgetnbextension by just supporting the new comm target_name.


Low-level Error: Cannot specify logical size for multiple piece join

Describe the bug
I am trying to decompile some functions in a file. However, a lot of them fail and give me the error "Low-level Error: Cannot specify logical size for multiple piece join"
Expected behavior
I expected the code to be decompiled as it has been for many other functions within the same file.
Attachments
libil2cpp.zip
One problematic function:
Name: PlayerScript$UpdateFast | Address: 00d0eb78 | Size: 11212
Environment (please complete the following information):

OS: Windows 10 22H2
Java Version: 20
Ghidra Version: 10.2.3
Ghidra Origin: Official Github

Can you supply some function addresses that produces the error?  I'm not seeing any with random clicking.

Also, if you wouldn't mind, could you try out Ghidra 10.3.1?  That's what I was going to start with.

Hello, I did supply a function address, aswell as the function size (possibly could find it in the function list?). I do not know if the file I shared contains the function names so I will try and do that later. I will try using the suggest version and see if that does anything, will share my results later!

I updated to version 10.3.1 and it solved the issue. Thanks!!


links the timeout docs to each other

Was talking in chat about futures timeouts, and apparently folks missed we had two different timeout functions. This links them to each other so if you find one, you also become aware of the other. Thanks!

bors r+


new simmate release(s)

@SWeav02 I just saw your repo's new README saying to do a dev install of simmate. Not ideal for new users 😅
@scott-materials and @SWeav02 -- if you two are willing to help "test" the dev versions, we can make new Simmate releases whenever you'd like. The release itself is very quick (~5-10min of work), so I wouldn't mind a weekly release.
The only reason my releases are so spread out is because (1) it takes me a long time to run the full test suite on my laptop and (2) if I make a new release with minor bugs, then I have to run the test suite all over again. The test suite is literally just running all the workflows with small structures and checking that they work, and I currently use this script here. It's just a bunch of VASP workflows, which can take up to 24hrs to run on my 4 cores 😭
... however, if you two are willing to run the test suite on your beefed up computers, I can make a release whenever. This should be easy now that you two know how to do a dev install. I will just a need a "the workflows have been tested and everything looks good" (just open a new issue)-- then I'll make the release for you.
I know @becca9835 has asked for a new release recently, and it's just waiting on a test suite run. Let me know if any of you are willing to help! 😄

I would be very happy to do this. Honestly the main thing that kept me from suggesting adding the new code to a release is that I haven't written a good test script for the updated BadELF code. But I should be able to just add the warrenapp s3 workflows and a new section for badelf workflows.  I'll work on updating the script and running it today.
There are also a couple of things that overlap between the main fork of simmate and my own, mostly related to the old badelf workflows. I think I'll probably remove those since they work a bit differently than the updated version and also store info in a different database table which would be confusing for users.

Ok I've opened a PR draft. I'm making a new env on WarWulf to run the test suite so that I can use a whole node and keep using my desktop . There are already some user warnings in the code, but I'm planning on making some more in depth docs this week.

Ok while I'm getting set up for running the test script, pytest is throwing some errors that look like this:
FAILED src/simmate/website/workflows/test/test_workflows_views.py::test_workflow_detail_view[StaticEnergy__Warren__Pbe] - assert 429 == 200
FAILED src/simmate/website/workflows/test/test_workflows_views.py::test_workflow_detail_view[StaticEnergy__Warren__PbeMetal] - assert 429 == 200
FAILED src/simmate/website/workflows/test/test_workflows_views.py::test_workflow_detail_view[StaticEnergy__Warren__Pbesol] - assert 429 == 200
FAILED src/simmate/website/workflows/test/test_workflows_views.py::test_workflow_detail_view[StaticEnergy__Warren__PrebadelfHse] - assert 429 == 200
FAILED src/simmate/website/workflows/test/test_workflows_views.py::test_workflow_detail_view[StaticEnergy__Warren__PrebadelfPbesol] - assert 429 == 200
FAILED src/simmate/website/workflows/test/test_workflows_views.py::test_workflow_detail_view[StaticEnergy__Warren__Scan] - assert 429 == 200

Based on where the errors are being thrown, I assume this is a Django views issue, but I'm not sure what the best way to fix it would be.  Any thoughts @jacksund?
In the meantime, I'm assuming this won't interfere with the test script running workflows so I'm going to go ahead and get that started.

thanks for doing that! Let me know when you're ready for a review of that PR
as for the failed tests you're seeing, I'll respond over in your PR thread (and you post any other questions over there too!)

One more question (this one is related to the test script so I'm leaving it here :grin:). I ran the test script by submitting a slurm job with a line like this: python path/to/test/script/test_all_workflow_runs.py. I left it without checking much and it looks like its no longer running about 3hr later which means to me it either finished or I ran it incorrectly. The output of the slurm run is just this:
2023-12-19 15:04:07 INFO     Configuring database and workflows 🛠
2023-12-19 20:04:14 INFO     Configuration complete 🚀

I assume if it had failed it would have given me some sort of output at the assert missing_failed_flows == [] line, but I also had assumed that if it would give me some output while it was running the workflows. Does this mean it finished fine or I'm missing something simple?

python path/to/test/script/test_all_workflow_runs.py

This isn't the command to run the script as that python file only defines the test 😅. You need to run it using pytest and also enable logging to help. I'll write a quick guide for this script tomorrow -- and maybe add a PR so that it's easier to run for you

I'm working on running the test suite and got the the point where I reset the database and use the prebuilt. When I run simmate database update I get this error:
InconsistentMigrationHistory: Migration workflows.0001_initial is applied before its dependency core_components.0002_alter_fingerprint_id_alter_fingerprintpool_id on database 'default'.

I'm assuming this means I'll need to rebuild the prebuilt database. I'll start the process as described here. Since I know downloading the databases takes quite a while, I'll come back to this tomorrow to run the tests.

the prebuilt is still pointing to the old database & migrations (i.e. I was using django incorrectly for everything <= v0.14.0). The new prebuilt is actually being made right now -- its been running for the last 5 hrs or so. I would wait until I merge #548 before going through it. I'll ping you when its ready 👍

the database prebuild is still running, but I've uploaded a temporary empty "prebuild" and then merged the PR. You can give this guide a try now: https://jacksund.github.io/simmate/contributing/maintainer_notes/#the-full-test-suite
Just do this for the official main branch. We will handle adding the warren_lab and badelf apps to the test suite as a 2nd step (and potentially a 2nd release).

Sounds good! I'm going through the test suite guide you sent now. Thanks for doing that :smile:

I just uploaded the new prebuilt database for you to try. If you already downloaded the temporary one, just delete the folder at ~/simmate/sqlite-prebuilds and then rerun the database reset command -- that will grab the new db I just added. It should be a 1.5gb download and then unpacks to ~9gb now.
Let me know if there are any issues!

Sounds good! I just reset now since I wasn't too far into the tests anyways. They're running now.

Yeah a new release would be super helpful. That way I can change the instructions for use on my warrenapp repo page to have users install simmate through conda/pip rather than doing a dev install.

sweet! I'm busy with errands for the rest of today, but I'll make a release for us tomorrow!

@SWeav02 I'm making a new minor release today (v0.15.1) for your updates. Give it some testing over the next week or two and try to iron out any bugs with your apps. Be sure to make a new env and test with the package on conda-forge to replicate your users env too.
Your fixes plus my larger changes (in the simmate config files, the new docs, etc.) will then be a couple weeks later (v0.16.0)

I'm hoping to have the v0.16.0 release out by the end of next week (the 26th). After which, I need to pivot my focus back to private apps, and then any follow-up releases will be when you need them 😄
I'll close this issue with the v0.16.0 release too. You can open a new issue whenever a new release is needed.

I'm hoping to have the v0.16.0 release out by the end of next week (the 26th). After which, I need to pivot my focus back to private apps, and then any follow-up releases will be when you need them 😄
I'll close this issue with the v0.16.0 release too. You can open a new issue whenever a new release is needed.

Sounds good. I've been working on vectorizing the badelf algorithm andI'm almost done. It should just effect the badelf class. I'll try and get it in a pull request before the 26th. so that it can be in v0.16.0


New Sample expand collapse content

Q
A

Bug fix?
no

New sample?
yes

Related issues?

What's in this Pull Request?
The following sample provide a format that display content based on expand/collapse effect using support column and option "setValue".
Guidance
Thanks for your contribution! Sharing is caring.

Awesome stuff again @aaclage. Super cool! 🔥🤩👏👏


Understanding various timestamps

Required Info

Camera Model
D400 rea

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu 20.04

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
2.38.1

Language
python

Segment
Robot

Issue Description
I was referring to this github issue. This post states following:

There are following four types of timestamps:

SENSOR_TIMESTAMP - time at the middle of exposure
FRAME_TIMESTAMP - time when first data chunk is sent towards host
BACKEND_TIMESTAMP - time when data is copied from USB controller to OS kernel (i.e. kernel space transmission)
TIME_OF_ARRVAL - time when frame buffer reaches librealsense (i.e. user space tramsmission

The relations hold:
(A) SENSOR_TIMESTAMP << FRAME_TIMESTAMP
(B) BACKEND_TIMESTAMP << TIME_OF_ARRIVAL
The clocks of the first pair of timestamps and the second pairs are not related.

I have following doubts:
Q1. Is it that the frame is first sent to kernel and then to librealsense thats why BACKEND_TIMESTAMP << TIME_OF_ARRIVAL?
Q2. Why there is no relation between (A) and (B)?
These are some quick screenshots form realsense viewer:

As you can see in first screenshot, BACKEND_TIMESTAMP << TIME_OF_ARRIVAL << FRAME_TIMESTAMP, whereas in second time stamp FRAME_TIMESTAMP << BACKEND_TIMESTAMP << TIME_OF_ARRIVAL. Second screen shot was taken by removing and reconnecting realsense.
I am trying to capture the timestamps using python script:
import pyrealsense2 as rs
import time

def print_first_frame_info():
    # Create a pipeline object
    pipeline = rs.pipeline()

    # Configure a streaming configuration
    config = rs.config()
    config.enable_stream(rs.stream.color, 640, 480, rs.format.bgr8, 30)  # Adjust resolution and format as needed

    # Start streaming
    profile = pipeline.start(config)

    i = 0

    try:
        while i < 5:
            i += 1

            frames = pipeline.wait_for_frames()

            color_frame = frames.get_color_frame()
            if not color_frame:
                print("Color frame not acquired")
                return

            info = {
                color_frame.get_frame_metadata(rs.frame_metadata_value.frame_timestamp)/1000./1000. : 'frame_ts',
                color_frame.get_frame_metadata(rs.frame_metadata_value.backend_timestamp)/1000 : 'backend_ts',
                color_frame.get_frame_metadata(rs.frame_metadata_value.time_of_arrival)/1000 : 'arrival_ts',
                color_frame.get_timestamp()/1000 : 'global_ts',
                time.time() : 'start'
            }

            sorted_info = sorted(info.items())
            sorted_ts = [value for key, value in sorted_info]
            sorted_ts_val = [key for key, value in sorted_info]
            print(sorted_ts)
            print(sorted_ts_val)
            print("----------------------------------------------")

    finally:
        # Stop streaming
        pipeline.stop()

if __name__ == "__main__":
    print_first_frame_info()

This outputs:
['frame_ts', 'backend_ts', 'global_ts', 'arrival_ts', 'start']
[1250.934548,<PHONE_NUMBER>.676,<PHONE_NUMBER>.6769912,<PHONE_NUMBER>.707,<PHONE_NUMBER>.7113307]
----------------------------------------------
['frame_ts', 'backend_ts', 'global_ts', 'arrival_ts', 'start']
[1250.967907,<PHONE_NUMBER>.709,<PHONE_NUMBER>.7107406,<PHONE_NUMBER>.74,<PHONE_NUMBER>.7416039]
----------------------------------------------
['frame_ts', 'backend_ts', 'global_ts', 'arrival_ts', 'start']
[1251.001267,<PHONE_NUMBER>.744,<PHONE_NUMBER>.7445257,<PHONE_NUMBER>.774,<PHONE_NUMBER>.7747688]
----------------------------------------------
['frame_ts', 'backend_ts', 'global_ts', 'arrival_ts', 'start']
[1251.034627,<PHONE_NUMBER>.776,<PHONE_NUMBER>.7781365,<PHONE_NUMBER>.807,<PHONE_NUMBER>.8081524]
----------------------------------------------
['frame_ts', 'backend_ts', 'global_ts', 'arrival_ts', 'start']
[1251.067987,<PHONE_NUMBER>.809,<PHONE_NUMBER>.8117464,<PHONE_NUMBER>.84,<PHONE_NUMBER>.8413043]
----------------------------------------------

As you can see in all above frames: BACKEND_TIMESTAMP << FRAME_TIMESTAMP  << TIME_OF_ARRIVAL.
So, I can see that really (A) and (B) are not related. But I want to know exactly why? May be I am not able to understand why from the definitions of these timestamps.
Q3. Is it correct to use FRAME_TIMESTAMP for syncing with other hardware especially when the description says its the time when first data chunk is sent towards host, but not when the frames are actually captured?

Hi @MaheshAbnave  Thanks very much for your questions!

My understanding is that if hardware timestamps are available then get_timestamp() provides the frame_timestamp, which designates the beginning of UVC frame transmission (the first USB chunk sent towards host) and readout begins after exposure is completed.  So SENSOR_TIMESTAMP would come before FRAME_TIMESTAMP because SENSOR_TIMESTAMP marks the middle of sensor exposure, whilst FRAME_TIMESTAMP requires exposure to have been completed.

The first pair (SENSOR_TIMESTAMP and FRAME_TIMESTAMP) are generated by the camera's firmware driver, whilst the second pair (BACKEND_TIMESTAMP and TIME_OF_ARRIVAL) are instead based on the computer's host clock.

If hardware metadata support is enabled in librealsense then the SDK automatically uses hardware timestamps.  If metadata support is not enabled then the SDK uses software timestamps produced with the computer host clock.

If you wish to sync RealSense data with data from a non-RealSense camera then in https://github.com/IntelRealSense/librealsense/issues/2186 a RealSense user found that the TIME_OF_ARRIVAL timestamp worked for them.

Hi @MaheshAbnave  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


hashtags are missing for Twitter button

Awesome library!! This is exactly what I was looking for. However, I have noticed that one can not add hashtags while sharing it on Twitter. As per twitter web intent docs hashtags should be part of the query filter to enable them. It would be great if you can add that missing props. That will make things easier for me.

Adding docs for reference https://developer.twitter.com/en/docs/twitter-for-websites/tweet-button/guides/web-intent

Adding docs for reference https://developer.twitter.com/en/docs/twitter-for-websites/tweet-button/guides/web-intent


cannot start an async pipe with a tap

The recent changes to pipeP/composeP behavior broke a common pattern I was using:
function validateString(v)
{
  if (typeof v != "string")
    throw new Error("err");
}

var promiseValueFor = R.pipeP(
  R.tap(validateString),
  () => Promise.resolve(null)
);

promiseValueFor("p");

// => TypeError: (intermediate value).then is not a function

The only workaround I could think of (except something silly like promiseValidate) is mixing pipe and pipeP this way. That's quite ugly and makes pipeP much less appealing as a general way to deal with promises pipelines.

Note that the old behavior is not the only way to support such pattern. pipeP/compose could force the Last function to return a promise, so that if my tap functions throws, the resulting function would actually return a rejected promise (rather than throw synchronously as it did until 0.15.1).

Upgrading to 0.17.1 today (from 0.15.1), this turned out to be remarkably painful. First, a lot of our pipeP usage surrounds REST API wrapping, almost always with some post-processing (which wasn't affected), but more often than not, with some pre-processinng as well. e.g.:
var promiseThoseObjectsByIds = pipeP(
  uniq,
  ids => agent.get({ ...}),
  ...post-processing...
);

For a simple case like this, I had to merge uniq into the first step.
More complex pattern, involves 'map' and Promise.all
var promiseThoseObjectByIds = pipeP(
   map(promiseThatObjectById),
   ::Promise.all,
   ...post-processing...
);

Here I had to nest pipeP-pipes into a "parent" pipe.
Another pattern that came up:
  var promiseThatObjectById = pipeP(
    createMapEntry("id"),
    promiseThatObject,
    ...
 );

Here I had to manually call Promise.resolve in the first step, loosing point-free goodness.

If you're willing to wrap the initial value in a Promise, you can compose sequences like this just by reducing them (plus some syntax modifcations to make sure the starting point comes last and the list of operations can be passed as a list of arguments): http://bit.ly/1Wu2GWo


Invalidating cache for remote Pydap dataset?

I have a remote server where data is continuously being written to a file that is served by Pydap. I'd like to monitor the file on my local computer. Is there a way that I can load up the dataset using xarray, do some calculations, and then at some point ask to download the newest datapoints? I believe that OpenDap servers sends a hash to the client to let the client know if their cache is current, and the clients can choose to redownload all or some of the data if necessary.

Is this still relevant?

I no longer use pydap in my day-to-day workflow. Feel free to close.


background of svg image

When creating svg from the signature the background of it is always transparent. Is it possible to make it for example white?

https://stackoverflow.com/questions/41697124/nativescript-angular2-create-image-programmatically-and-share/41723368#41723368


bls pub key enhancements build

#576  👈
feature/proof-of-stake

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @lazynina and the rest of your teammates on  Graphite


Button for archiving cells

Once a deployment is done (as is the case with Bill's deployment), we are not actively monitoring the cell data but still want to retain the data. An "archive" button that removes the cells from the list would help to only show relevant data which would prevent confusion.

Duplicate of #225


Add regions and peaks to designspace.

Outline all the regions and their peaks for the active axes in the designspace view.
This was written to make it easier to see overlapping intermediate regions, though it is also somewhat useful for simpler variable regions as well.

Thanks for this 👍 It’s very much appreciated. However I actually have a colour visualization of Regions coming soon, which will work a bit differently, so I won’t merge this one.

Sounds good, just didn't want this to get lost (I wrote this mostly so I could get a better feel for what my own mechanically created fonts were actually doing). Feel free to use anything that looks interesting from this. Good to hear that something like it is in the works.
What I learned from writing this

the edges of intermediate regions tend to fall in the same place so the outlines tend to overlap, obscuring the edges. So should probably stroke only the inside edges of the rects to avoid overlap (not implemented in this PR).

it's really nice to know the positions of the peaks and which are active. This makes it really obvious that as one moves toward a point there will be more delta from that point.

highlighting the active regions makes it really obvious where the deltas for an active peak will drop off to zero. However when many active regions overlap one wishes for more of a diagonal hatch of their colors than the muddy brown one eventually ends up with using opacity. This is probably rather expensive and difficult to achieve.

See issue #62

See issue #62


Check if object is JSON object

I would like to be able to check if json[key] is a JSON object.
The REST API I'm interacting with may embed a string for a key where circular embeds would happen. For instance:
"user": {
  "id": "dasoghweoghw",
  "account": {
    "id": "3285usodahg",
    "service": "twitter",
    "owner": "dasoghweoghw"
  },
  ...
}

My serialization method expects user.account.owner to be of type User, but because the API avoids embedding circular data, it crashes every time.
A workaround I've used in the past:
if let owner = json["owner"].string {
  println("Nothing to serialize...")
} else {
  self.owner = User(json: json["owner"])
}

Another idea:
if let json["owner"].string == nil {
  self.owner = User(json: json["owner"])
}

Any suggestions on how to handle this?

if let a = Optional.Some(json["aoeua"]) where a.string == nil {
}

This issue has been inactive for a while so I'm gonna go ahead and consider it fixed. Please let us know if you want to reopen it.


use latest metac that has fixes to advanced selector

Using metac v0.2.1 that has fixes to advanced selector


fix: change local artifact validation logic from tag to if blocks

disable the SilenceErrors option, so the error from each cmd can surface
change artifact local fieldfile tag to filepath, only validate the file path, not existence
check file existence in codebase, and surface more readable error

Codecov Report
Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (76e265f) 38.21% compared to head (e31bd7b) 37.91%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #183      +/-   ##
===========================================
- Coverage    38.21%   37.91%   -0.30%
===========================================
  Files           16       16
  Lines         1285     1295      +10
===========================================
  Hits           491      491
- Misses         689      699      +10
  Partials       105      105

Files
Coverage Δ

pkg/config/baremetal.go
0.00% <ø> (ø)

pkg/cluster/baremetal/create.go
0.00% <0.00%> (ø)

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


Error on running tests

I'm getting the following error;
Thread 1: Fatal error: 'try!' expression unexpectedly raised an error: web3swift.Web3Error.inputError(desc: "Wrong provider - should be Web3HttpProvider with endpoint scheme http or https")
All I did was download the repo and run the tests...

Hello.
There are also some tests that require Infura setup. As I remember I disable it in smoke tests.
there were some updates since this issue. can you please kindly check the status now?

Fixed in #347


cell.Value property gives the Name property instead (MSAA proxy)

Hey,
I'm working with a winforms application created with devexpress, so the properties i use are the ones I get from the MSAA proxy provider generated by UIA (correct?). I'm working with a lot of grids and I'm trying to assert the value of a particular cell.
I'm still fairly new to the programming of automated tests and to FlaUI so I might be doing something wrong.
I will try to post the relevant info from the microsoft inspect tool:

""table (the grid)
ControlType:	UIA_TableControlTypeId (0xC374)
LocalizedControlType:	"table"
LegacyIAccessible.Role:	table (0x18)
IsGridItemPatternAvailable:	false
IsGridPatternAvailable:	false
IsLegacyIAccessiblePatternAvailable:	true
ProviderDescription:	"[pid:8264,providerId:0x1511C6 Main:Nested [pid:16040,providerId:0x1511C6 Main(parent link):Microsoft: MSAA Proxy (unmanaged:uiautomationcore.dll)]; Hwnd(parent link):Microsoft: HWND Proxy (unmanaged:uiautomationcore.dll)]"
All the other patterns displayed are false.
"Data Panel"
Does not show ControlType or Localized control type.
LegacyIAccessible.Name:	"Data Panel"
LegacyIAccessible.Role:	client (0xA)
LegacyIAccessible.State:	normal (0x0)
LegacyIAccessible.Value:	""
IsLegacyIAccessiblePatternAvailable:	true
ProviderDescription:	"[pid:16040,providerId:0x0 Main(parent link):Microsoft: MSAA Proxy (unmanaged:uiautomationcore.dll)]"
"Row 1"
Does not show ControlType or Localized control type.
LegacyIAccessible.Name:	"Row 1"
LegacyIAccessible.Role:	row (0x1C)
LegacyIAccessible.State:	selected,focused,read only,focusable,selectable (0x300046)
IsLegacyIAccessiblePatternAvailable:	true
"Name row 0" (this is the cell)
Name:	"Name row 0"
ControlType:	UIA_DataItemControlTypeId (0xC36D)
LocalizedControlType:	"item"
LegacyIAccessible.Name:	"Name row 0"
LegacyIAccessible.Role:	cell (0x1D)
LegacyIAccessible.State:	focused,read only,focusable,selectable (0x300044)
LegacyIAccessible.Value:	"Tor Browser"
Value.IsReadOnly:	true
Value.Value:	"Tor Browser"
IsGridItemPatternAvailable:	false
IsGridPatternAvailable:	false
IsInvokePatternAvailable:	true
IsItemContainerPatternAvailable:	false
IsLegacyIAccessiblePatternAvailable:	true
IsValuePatternAvailable:	true
ProviderDescription:	"[pid:16040,providerId:0x0 Main(parent link):Microsoft: MSAA Proxy (unmanaged:uiautomationcore.dll)]"
Here is my code:
`
public static void ButtonNewRuleFromSelected()
    {
        using (var app = Application.Attach("disadmin.exe"))
        {
            using (var automation = new UIA3Automation())
            {
                var softwareWindow = app.GetMainWindow(automation);
                var grid = softwareWindow.FindFirstDescendant(cf => cf.ByAutomationId("1380806")).AsGrid();
                var gridData = grid.FindFirstChild(cf => cf.ByName("Data Panel")).AsDataGridView();
                var row = gridData.FindChildAt(1).AsGridRow();
                var cell = row.FindFirstChild(cf => cf.ByName("Name row 0")).AsGridCell();
                Assert.That(cell.Value == "Tor Browser", cell.Value);
            }
        }
    }

`
This gives me a failed test with the info
Message:   Name row 0
Expected: True
But was:  False
I put the cell.Value as the message just to display what the "value" is.
I've also done a cell.Click(); and this works, making the program click on the right cell.
In advance
Thanks

Hi
Can you check with FlaUInspect what it shows for a cell? Especiall what it shows for the ValuePattern.Value.
Best is to select the cell in FlaUInspect and post a screenshot here.

Hey,
thanks for the reply, here is a screenshot with FlaUInspect 1.2:

and the rest of it:

Ok, as you see the ValuePattern contains the correct value.
The current implementation of the GridCell only returns the Name property as Value.
What you can do now is use cell.Patterns.Value.Pattern.Value.Value.
I know, this reads strange but makes sense.

cell is the element you have
Patterns is a container with all patterns
Value is the pattern we want
Pattern returns the pattern object
Value is the Value property object of the pattern
Value is the effective value of the property

Hey,
this worked after a few tries, thank you! I managed to make the the PC run out of memory the first few times... The grids I work with contains several hundred thousand rows, so I need to be very specific, or the program will look through the entire grid (?) and eat up all the memory I guess.

Great
Yes, working with grids can be a bit difficult. Especially FindFirstDescendant or FindChildAt can need to search thru the entire grid.
You can have a look at the methods in the GridPattern that might help you navigate the grid cells without going thru the entire grid.

Thanks for the tip! I had a feeling FindFirstDescendant worked that way, but I thought FindChildAt was safer so I will keep that in mind. Ill try my hands at the methods in GridPattern then.

Also check out https://github.com/Roemer/FlaUI/wiki/Caching


introduce test cases for this project

test log:
FAIL  test/jointQuery.test.ts (18.901 s)
● Console
console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the total order count group by color of cars"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the total order count group by color of cars and sex of customer"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the count of cars that are green"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

● Joint Query › show me the total order count group by color of cars
expect(received).toEqual(expected) // deep equality

- Expected  - 3
+ Received  + 3

- SELECT cars.color, SUM(order.count) as total_order_count FROM cars
+ SELECT color, COUNT(order_id) AS total_order_count FROM cars
- JOIN order ON cars.car_id = order.car_id
+ JOIN order ON cars.id = order.car_id
-  GROUP BY cars.color;
+ GROUP BY color;

  15 |         const case1: TestCase = { inputText, sql};
  16 |         const result = translateToSQL(case1.inputText, process.env.OPENAI_API_KEY, tableSchema);
> 17 |         expect(await result).toEqual(case1.sql);
     |                              ^
  18 |     });
  19 |     it("show me the total order count group by color of cars and sex of customer",async () => {
  20 |         const inputText = "show me the total order count group by color of cars and sex of customer";

  at test/jointQuery.test.ts:17:30
  at step (test/jointQuery.test.ts:33:23)
  at Object.next (test/jointQuery.test.ts:14:53)
  at fulfilled (test/jointQuery.test.ts:5:58)

● Joint Query › show me the total order count group by color of cars and sex of customer
expect(received).toEqual(expected) // deep equality

- Expected  - 1
+ Received  + 5

- SELECT COUNT(*) FROM cars;
+ SELECT color, sex, COUNT(order_id) AS total_order_count
+ FROM cars
+ INNER JOIN order ON cars.id = order.car_id
+ INNER JOIN customer ON order.cus_id = customer.cus_id
+ GROUP BY color, sex;

  22 |         const case1: TestCase = { inputText, sql};
  23 |         const result = translateToSQL(case1.inputText, process.env.OPENAI_API_KEY, tableSchema);
> 24 |         expect(await result).toEqual(case1.sql);
     |                              ^
  25 |     });
  26 |     it("show me the count of cars that are green",async () => {
  27 |         const inputText = "show me the count of cars that are green";

  at test/jointQuery.test.ts:24:30
  at step (test/jointQuery.test.ts:33:23)
  at Object.next (test/jointQuery.test.ts:14:53)
  at fulfilled (test/jointQuery.test.ts:5:58)

● Joint Query › show me the count of cars that are green
expect(received).toEqual(expected) // deep equality

- Expected  - 5
+ Received  + 1

- SELECT cars.color, customer.sex, SUM(order.count) as total_order_count
- FROM cars
- JOIN order ON cars.car_id = order.car_id
- JOIN customer ON order.cus_id = customer.cus_id
- GROUP BY cars.color, customer.sex;
+ SELECT COUNT(*) FROM cars WHERE color = 'Green';

  29 |         const case1: TestCase = { inputText, sql};
  30 |         const result = translateToSQL(case1.inputText, process.env.OPENAI_API_KEY, tableSchema);
> 31 |         expect(await result).toEqual(case1.sql);
     |                              ^
  32 |     });
  33 | });

  at test/jointQuery.test.ts:31:30
  at step (test/jointQuery.test.ts:33:23)
  at Object.next (test/jointQuery.test.ts:14:53)
  at fulfilled (test/jointQuery.test.ts:5:58)

FAIL  test/singleQuery.test.ts (19.299 s)
● Console
console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me all the cars that are red"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the count of cars"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the count of cars that are green"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the customer that age older than 20 years"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

console.log
  Translate this natural language query into SQL without changing the case of the entries given by me:

  "show me the total order count that date between '2023-03-01' AND '2023-03-31'"

  Use this table schema:

  CREATE TABLE cars (id INT, make TEXT, model TEXT, year INT, color TEXT);CREATE TABLE customer (cus_id INT, name TEXT, sex INT, age INT);CREATE TABLE order (order_id INT, car_id INT, cus_id INT, number INT, price DOUBLE, date DATE);

  SQL Query:

  at src/translateToSQL.ts:6:11

● Single Query › show me the total order count that date between '2023-03-01' AND '2023-03-31'
expect(received).toEqual(expected) // deep equality

Expected: "SELECT sum(count) FROM order WHERE date BETWEEN '2023-03-01' AND '2023-03-31';"
Received: "SELECT COUNT(order_id) FROM order WHERE date BETWEEN '2023-03-01' AND '2023-03-31';"

  43 |         const case1: TestCase = { inputText, sql};
  44 |         const result = translateToSQL(case1.inputText, process.env.OPENAI_API_KEY, tableSchema);
> 45 |         expect(await result).toEqual(case1.sql);
     |                              ^
  46 |     });
  47 | });

  at test/singleQuery.test.ts:45:30
  at step (test/singleQuery.test.ts:33:23)
  at Object.next (test/singleQuery.test.ts:14:53)
  at fulfilled (test/singleQuery.test.ts:5:58)

Test Suites: 2 failed, 2 total
Tests:       4 failed, 4 passed, 8 total
Snapshots:   0 total
Time:        20.693 s
Ran all test suites.

@jack-kwok80 you commited your own API key, you might want to remove that one

@jack-kwok80 you commited your own API key, you might want to remove that one

Done

Hi @whoiskatrin, Can this request be merged?

@jack-kwok80, but you closed this PR a week ago or so. I'm a bit confused.

Sorry, but can we merge this PR when closed, or I have to reopen it


initial commit to add in a dependabot.yml file

Signed-off-by: CEHENKLE<EMAIL_ADDRESS>Description
adding dependabot.yml file to enable automatic scanning for issues in dependencies.
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dblock I'm thinking we might want to pull out the test gradle build files.  What do you think?

@dblock I'm thinking we might want to pull out the test gradle build files. What do you think?

I don't think so. We should be upgrading test dependencies the same. We get endless vulnerability reports for those by automated software and have to spend a lot of time digging through the dependency tree to finally find out that they are only used in tests. Furthermore developer machines can be compromised through a dev/test dependency.
Is the list of gradle files here basically the list of all gradle files in the project? As a stretch goal we could automate updating this file with a GH workflow that opens a PR every time there's a change.

https://github.com/opensearch-project/OpenSearch/issues/1355


⚠ Bofrost.be has degraded performance

In 4fcaaa3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 976 ms

Resolved: Bofrost.be performance has improved in 2d073dc.


Naming of sample_with_mcmc

the argument sample_with_mcmc is SNPE-specific. SNL and SRE always use MCMC anyway. We should reflect this in the name and only have the argument be used if SNPE is the used algorithm.

I am leaning towards not renaming this argument. The reason is that in sample, we check for sample_with_mcmc:
https://github.com/mackelab/sbi/blob/a6792755a3e396ded20131c9ded5f0d462ca5249/sbi/inference/posteriors/sbi_posterior.py#L291
SNL and SRE also jump into this if-case. So if we rename the argument it will just get full-blown confusing imo.


Overlay radial profile annuli on RateMap/Image

This would be quite useful for paper figures for instance, but also links to my work on issue #240, as it will make it easier to see what data is going into each annulus.

I can now display annuli drawn as artists on top of the imshow call of the view method of the Image class (what a mouthful), as seen below:

However, this doesn't really convey the truth of exactly what happens, especially at small radial scales, because you can't make perfect circles like that out of the pixels sizes I'm working with. As such I would like to add a flag that switches between idealised annuli painted on (like these), and what actually happened when masks were made (which will no doubt need some sort of polynomial artist). As such I am not closing this issue yet.

I don't know that tracing the pixels exactly would be particularly helpful, so I actually will close this now


Rav1dTileState: Make into Vec and give interior mutability

Fixes the ts field of https://github.com/memorysafety/rav1d/issues/713 and closes https://github.com/memorysafety/rav1d/issues/713.

Oh, it looks after the changes in #952 we're still able to get a mutable reference to the Rav1dFrameData in rav1d_decode_frame_init_cdf. I was expecting to only be able to get a shared reference, which required making all of the fields atomic. If we can get a mutable reference in that function we can make some of the fields non-atomic, which would simplify the code somewhat. I'll do that now.

Oh nice!


Support Kibana 6.3.1

Please!

Download the latest release from https://github.com/sivasamyk/logtrail/releases/download/v0.1.29/logtrail-6.3.1-0.1.29.zip :)


Camera Access

I'm having trouble figuring out how to access the camera while picking images.
In the original example there was an enableCamera property, but that doesn't seem to an option now.
I found hasCameraInPickerPage within AndroidOptions, but nothing for iosOptions yet.

Replace enableCamera with hasCameraInPickerPage.

error:
The named parameter 'hasCameraInPickerPage' isn't defined.
Try correcting the name to an existing named parameter's name, or defining a named parameter with the name 'hasCameraInPickerPage'.dartundefined_named_parameter

The IOS side uses the BSImagePicker plugin, which has removed the setting that allows the use of cameras in its latest version. If you want to use this setting, you can fork a version and replace it with the old version.