EDK docs site and basic tutorial

We should generate/deploy docs and a basic tutorial/walk through for the edk. Having this in place in time for tap-toberfest would be pretty nice.
/cc @tayloramurphy

@pandemicsyn think we could cop from the sdk site pretty easy? For a technical tool like this the readthedocs stuff seems pretty nice.

@pandemicsyn think we could cop from the sdk site pretty easy? For a technical tool like this the readthedocs stuff seems pretty nice.

@tayloramurphy yea I think this would be a pretty low weight. (like 2 for getting things setup, and maybe another 2 for writing up a tutorial/walkthrough)

The initial scaffolding should be live on readthedocs.org momentarily under https://edk.meltano.com. Just waiting for Route53 to propagate the dns entry and then for the SSL cert to be provisioned.


Jupyter Releaser setup

Keeping track of the list of tasks:

[x] Create the GitHub app for the QuantStack org
[x] Add workflows: https://github.com/QuantStack/yjs-widgets/pull/16
[x] Create the release environment and add APP_ID and APP_PRIVATE_KEY
[x] Add trusted publisher to the PyPI repo: https://pypi.org/project/yjs-widgets/
[x] Add NPM_TOKEN to the secrets (org secret)
[x] Make sure the npm package has a public publish config: https://jupyter-releaser.readthedocs.io/en/latest/faq/index.html#failed-to-publish-a-package-to-npm

https://github.com/QuantStack/yjs-widgets/blob/5010afdcec88fda5589b4ac677f3e952d40d815b/package.json#L94-L96

[x] Add quantstack-bot as a contributor to the package on npm: https://www.npmjs.com/~quantstack-bot - https://www.npmjs.com/package/yjs-widgets
[x] Init CHANGELOG.md: https://github.com/QuantStack/yjs-widgets/pull/18

I just released v0.3.8 with the jupyter-releaser, thanks!


Component Name dictionaries (possibly non-issue)

While playing with the adding components to a node I discovered (unsurprisingly) you had to match the name of the component exactly. It took me an embarrassingly long time to figure out 'Tesla_T4' and 'TeslaT4' could not be substituted for 'Tesla T4'. Perhaps in one of the user guides include a note that spaces are fine when assigning components.

Need a way to find resource type names.
Need a tool that can:
find_node_with(ram>32, GPU.any, ConnectX6=>2)

Need a "test_topology" function that provides very useful feedback.


Upgrade validator to 0.19.0

While trying to use package-provided validators and a few custom validators of my own, I've run into this error:
thread '<...>' panicked at <home>/.cargo/registry/src/index.crates.io-6f17d22bba15001f/validator-0.18.1/src/types.rs:185:13:
Attempt to replace non-empty ValidationErrors entry

This PR upgrades validator to 0.19.0 to get the corresponding fix for validating struct with multiple members, which was reported in https://github.com/Keats/validator/issues/319 and fixed in https://github.com/Keats/validator/pull/321.

Thank you for your contribution! Your PR has been now released in version 0.21.0.


Add remote device for BGP Sessions

Is your feature request related to a problem? Please describe.
Currently, to attach BGP sessions to a device, one would have to have 2 separate sessions defined, one for each end of the BGP session.
Describe the solution you'd like
Updating the device field to local device and adding a new field for remote device to link the BGP session to both devices inside of netbox.
Describe alternatives you've considered
The alternative that I can see is to add 2 unique sessions one for each device. It seems excessive to add 2 sessions when 90% of the information is duplicated between the 2 sessions.
Additional context
The scenario I am modeling is 2 routers who talk BGP to each other. I do not see a use case where BGP is only defined in a single router and not at the remote end.

Have you tried to add custom fields, especially remote_device --> dcim.devices ? Just a workaround suggestion

That would be a workaround. Also seems easy enough to add directly. It would be very rare you are not attaching 2 devices together with BGP, so including the second device field natively just makes sense to me.

Well, I'm torn between the network BGP session object itself and a view from the device that have the session object. You could use listen range and from the device perspective, the representation in the plugin works, but you won't list all dynamic sessions into the plugin.
There are too much parameters in BGP (password, redistribute, ecmp, next hop options, multi hop, allow as, bfd ...) that cannot be listed and implemented in the plugin for ease of use reasons (I think) and custom fields helps to add what's missing in each use case.
I don't know if the aim of the plugin is to represent a core object of a BGP session or the view of a device that owns a BGP session.

That would be a workaround. Also seems easy enough to add directly. It would be very rare you are not attaching 2 devices together with BGP, so including the second device field natively just makes sense to me.

Hey, your use case assumes sessions are all on devices you have in NetBox.  This wouldn't be the case for service providers whereas you might have IX / Transit peering, NNI peering, L3VPN peering whereas you wouldn't add a 3rd parties devices into NetBox as they're not directly owned/managed/configured etc by you.

That would be a workaround. Also seems easy enough to add directly. It would be very rare you are not attaching 2 devices together with BGP, so including the second device field natively just makes sense to me.

Hey, your use case assumes sessions are all on devices you have in NetBox. This wouldn't be the case for service providers whereas you might have IX / Transit peering, NNI peering, L3VPN peering whereas you wouldn't add a 3rd parties devices into NetBox as they're not directly owned/managed/configured etc by you.

Then let the parties be either a Device or an IP Address, akin to how either endpoint for a Circuit can be a Device or a Provider Network.


aya: maps + programs using RawFd could lead to fd leaking

As of Rust v1.63.0 new types OwnedFd and BorrowedFd were added so that rust can handle the lifetime of file descriptors using normal RAII and borrow rules. I think it'd benefit aya to move towards using these types as it can prevent some unforeseen errors or file descriptor leakage either by aya or by its users.
As a side note on this we may have to remove the implementation of Clone on some types, at the very least on Map and change it to a try_clone(). The current implementation is faulty in that it both ignores errors and the cloned file descriptor is not set to close on exec which afaict should generally be set. While in practice this may not be an issue 99% of the time it is still not good practice to ignore errors during duplication of a file descriptor. Rust's OwnedFd does the right thing on its try_clone() method.
I was contemplating working on this and making a PR but I wanted to make sure this is something that the maintainers of aya are ok merging before I start on it since it'd be a pretty hefty PR and it might have some breaking changes, including having to up the MSRV to v1.63.
To clarify, apart from the map clone issue above I am not claiming that there is currently a leakage or errors in the file descriptor handling. My wanting to move towards OwnedFd/BorrowedFd is from an abundance of caution to prevent possible errors either in the existing code or in the future as RawFds make it easier to have oopsies.

I was contemplating working on this and making a PR but I wanted to make sure this is something that the maintainers of aya are ok merging before I start on it since it'd be a pretty hefty PR and it might have some breaking changes, including having to up the MSRV to v1.63.

We've discussed this in the past and is definitely something we want, we just need someone to drive the effort. I think MSRV 1.63 would be fine.

This is almost done. We have two instances of held RawFd left:
https://github.com/aya-rs/aya/blob/0b6ea313ded3240715d1b30d3b247e2bc983659e/aya/src/programs/socket_filter.rs#L126-L127
https://github.com/aya-rs/aya/blob/0b6ea313ded3240715d1b30d3b247e2bc983659e/aya/src/programs/xdp.rs#L234
I'm not exactly sure what the semantics there are supposed to be. @dave-tucker ?

This is almost done. We have two instances of held RawFd left:
https://github.com/aya-rs/aya/blob/0b6ea313ded3240715d1b30d3b247e2bc983659e/aya/src/programs/socket_filter.rs#L126-L127
https://github.com/aya-rs/aya/blob/0b6ea313ded3240715d1b30d3b247e2bc983659e/aya/src/programs/xdp.rs#L234
I'm not exactly sure what the semantics there are supposed to be. @dave-tucker ?

Any LinkId type is just supposed to be a cookie 🍪 we exchange with a user to uniquely identify a specific attachment.
This is because Aya chooses to own the FD backing that attachment.
It's actually used as the key in the HashMap we use to track links:
https://github.com/aya-rs/aya/blob/0b6ea313ded3240715d1b30d3b247e2bc983659e/aya/src/programs/links.rs#L31-L34
Since it's used as a unique ID, hopefully, we can get rid of the need to use FDs here - i.e cast to i32 and hash together - since at this point they should never be used as FDs again.
However, these Link::Id cookies 🍪 can be used to detach a program:
https://github.com/aya-rs/aya/blob/0b6ea313ded3240715d1b30d3b247e2bc983659e/aya/src/programs/xdp.rs#L166-L171
Now comes the fun part.
Link calls detach on drop.
So any concrete Link type (NlLink and SocketFilterLink) need to be able to detach themselves.
Which of course leads to problems when they require the FD of the program they are attached to..
So TL;DR:
In both cases, when a link is created the kernel refcnt for a bpf program will be > 1.
In other words, the program will not disappear until the last link has gone (even if you explicitly unload it) - this might be a feature we can use to our advantage.
For XDP specifically:

We could borrow the ProgramFd under the same lifetime as the XdpProgram
Worst case, it's ok to dup and keep an OwnedFd to avoid lifetimes

For SocketFilter:

No SocketFilterLink can outlive the socket to which it's attached
sock_fd should be a BorrowedFd
prog_fd, like XDP, could be borrowed or owned

Sounds good. You interested in making that change?


Add templates for quickly creating new projects

cc @szg251 I cannot request your review for some reason, lmao


Abstract invoice

Abstracted Models, Views, Filters and Forms of Invoice to be inherited by Sales Invoice and Purchase Invoice

Fixed #7


HBASE-24555 Correct the description of hbase.hregion.max.filesize

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 26s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 10s
master passed

+0 :ok:
refguide
6m  0s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 17s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+0 :ok:
refguide
6m 15s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

+1 :green_heart:
asflicense
0m 29s
The patch does not generate ASF License warnings.

25m  7s

Subsystem
Report/Notes

Docker
Client=19.03.11 Server=19.03.11 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1895

Optional Tests
dupname asflicense refguide xml

uname
Linux 475fd6aecca5 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / fd5002d0da

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
66 (vs. ulimit of 12500)

modules
C: hbase-common . U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 58s
the patch passed

-0 :warning:
javadoc
0m 17s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 16s
root in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
160m 38s
root in the patch passed.

175m 23s

Subsystem
Report/Notes

Docker
Client=19.03.11 Server=19.03.11 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1895

Optional Tests
javac javadoc unit

uname
Linux cc9ad72d1e2e 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / fd5002d0da

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/testReport/

Max. process+thread count
6872 (vs. ulimit of 12500)

modules
C: hbase-common . U: .

 U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1895 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1895

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1895 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1895

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m  0s
Docker mode activated.

-1 :x:
patch
0m  3s
https://github.com/apache/hbase/pull/1895 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/1895

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/2/console

versions
git=2.17.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 23s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+0 :ok:
mvndep
0m 28s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 55s
master passed

+0 :ok:
refguide
5m 31s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 43s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
5m 46s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

_ Other Tests _

+1 :green_heart:
asflicense
0m 27s
The patch does not generate ASF License warnings.

22m 58s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1895

Optional Tests
dupname asflicense refguide xml

uname
Linux 2318d77d1490 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a4e5ccc798

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
66 (vs. ulimit of 12500)

modules
C: hbase-common . U: .

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 59s
the patch passed

-0 :warning:
javadoc
0m 18s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 16s
root in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
165m 40s
root in the patch passed.

179m 24s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1895

Optional Tests
javac javadoc unit

uname
Linux a04659e1b10b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a4e5ccc798

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/testReport/

Max. process+thread count
7138 (vs. ulimit of 12500)

modules
C: hbase-common . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+0 :ok:
mvndep
0m 38s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 28s
master passed

+1 :green_heart:
javadoc
2m 21s
master passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 21s
the patch passed

+1 :green_heart:
javadoc
2m 23s
the patch passed

_ Other Tests _

-1 :x:
unit
318m 56s
root in the patch failed.

334m 35s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1895

Optional Tests
javac javadoc unit

uname
Linux 43e7682e0262 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / a4e5ccc798

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/artifact/yetus-jdk8-hadoop3-check/output/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/testReport/

Max. process+thread count
5802 (vs. ulimit of 12500)

modules
C: hbase-common . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1895/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@wchevreuil Could you help to merge it, thanks.


FastAPI: Some requests are failing due to 10s timeout

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
The gunicorn configuration we are using:
"""gunicorn server configuration."""
import os

threads = 2
workers = 4
timeout = 60
keepalive = 1800
graceful_timeout = 1800
bind = f":{os.environ.get('PORT', '80')}"
worker_class = "uvicorn.workers.UvicornWorker"

Description
We have deployed a model prediction service in production that is using FastAPI and unfortunately, some of the requests are failing due to a 10s timeout. In terms of concurrent requests, we typically only load about 2/3 requests per second, so I wouldn't think that would be too much strain on FastAPI. The first thing we tried to do is isolate the FastAPI framework from the model itself, and when we performed some tracing, we noticed that a lot of time (6 seconds) was spent on this segment: starlette.exceptions:ExceptionMiddleware.__call__.
Would really appreciate some guidance on what the above segment implies and what is causing timeout issues for some requests under a not too strenuous load.

Wanted Solution
I would like to optimize my FastAPI application so that latency for all requests are consistent and there are no outliers that error out due to the 10s timeout.
Wanted Code
N/A

Alternatives
No response
Operating System
macOS
Operating System Details
No response
FastAPI Version
0.65.2
Python Version
3.7.10
Additional Context
No response

How many  concurrent requests when you test?
I guess the thread is full, new request need to wait new thread when release a thread.

Just 3 per second probably. We've been monitoring things and CPU usage is ok. I don't think it's any issue in terms of threads either. It's some application-level issue related to the middle-ware, perhaps?

Are you blocking the event loop by doing a substantial CPU bound task on the event loop ?

It's a Bert Model so yes, but there's middleware that sends metrics to Prometheus that seems to be taking a long time as well

You need to do your heavy processing outside of the event loop.
Async Python is Cooperative Multitasking, if one of your requests gets a hold of the event loop and doesnt call an await for a long period of time the other async tasks on the event loop will not make any progress (in your prometheus code for example).
Offload your CPU bound tasks to another process (people often use Celery ) so that you are not blocking the loop.


Update README.md with more community information

Added new information on how to get involved and where all of the various community functions and communications channels are happening.

that's news to me....


Remove -SNAPSHOT from version in pom.xml for v1.2.0

Looking back the operations happened when releasing v1.1.0 and following https://github.com/xspec/xspec/pull/415#issuecomment-455510906, I guess this is the last required change for v1.2.0 and to be merged immediately before tagging it.
Ccing @cmarchand just in case.

That's perfect.
Ok for me.


Add .vscode to .gitignore

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[-] Added tests.
[-] Updated documentation.
[-] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

Just in case this is bothering you with other repos, i find the global ignore useful https://github.com/pirj/dotfiles/blob/master/.config/git/ignore


Release: use non-EOLed JDK version

JDK version that we are using for enry-java release is oracle JDK 8 which EOLed 1 year ago (and e.g is not available on newer linux 16.04 CI images any more)
This issue is about:

[ ] update JDK to maintained LTS version e.g openJDK 11 (right now JDK 8 is used)
[x] update sbt version to 1.x, that works on newer JDK (current 0.13 does not)
[x] update sbt shell wrapper and plugin version, that support 1.0
[ ] update build.sbt, adjusting for plugin changes (fat-jar assembly fails by default)
[ ] make sure released version can be run on older JDK (one that Infra uses for the clusters)

Initial work was done under #221 but still a consensus on min JDK version is needed.

@bzz We're using JDK 8 for Apache Spark. I'm not sure what the status on JDK 11 is, see SPARK-24417.


Deploy to AWS Elastic Beanstalk

Mauro Di Iasio:

I only have a problem:
"targets": [
{
"type": "zip",
"name": "Sample.zip",
"description": "Example ZIP per AWS",
"target": "D:/desktop/Deploy"
}
]
When I deploy zip file on Elastic Beanstalk, it seems fine but don't do the upload!
Have I to use a different target ?

I am not sure: The zip target only creates a ZIP files in a "local" directory.
Can you (or someone else) explain how you upload/deploy a ZIP file (content) to AWS Elastic Beanstalk?

Thank you to reply me dear Marcel, I will try to explain you
To upload my Web app in AWS Amazon, in Visual Studio I simply do this: build -> Publish Web app (publish method: Web Deploy Package)
VS will create a zip folder in which is the complete package
Here is the guide: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/applications-sourcebundle.html
Creating a Source Bundle for a .NET Application
....
If you need to manually create a source bundle for your .NET application, you cannot simply create a Zip file that contains the project directory. You must create a web deployment package for your project that is suitable for deployment to Elastic Beanstalk. There are several methods you can use to create a deployment package:
How can I do this by your extension in Visual Code ?
Thanks in advance
Mauro

@FerrarisIV
I have released version 5.15.0 that is now albe to define a custom output filename for a ZIP file.
That should make it possible to create a ZIP file with the same name and use a webdeploy post operation:
{
    "deploy": {
        // ...

        "targets": [
            {
                "type": "zip",
                "name": "Sample.zip",
                "description": "Example ZIP per AWS",
                "target": "D:/desktop/Deploy"
                "fileName": "my_aws_app.zip",

                "deployed": [
                    {
                        "type": "webdeploy",
                        "exec": "C:/Program Files/IIS/Microsoft Web Deploy V3/msdeploy.exe",

                        "verb": "sync",
                        "source": "lm/w3svc/1",
                        "package": "D:/desktop/Deploy/my_aws_app.zip"
                    }
                ]
            }
        ]

        // ...
    }
}

This is only an example for the 1st example from here.
Please check out the required parameters and the path where msdeploy.exe is installed on your system.

Thanks again, I will try it next week!!


launchctl list pollution

launchctl list | grep Sparta
-	0	com.spartascience.SpartaConnect.111820
-	0	com.spartascience.SpartaConnect.111844
-	0	com.spartascience.SpartaConnect.136648
-	0	com.spartascience.SpartaConnect.136260
-	0	com.spartascience.SpartaConnect.136696
-	0	com.spartascience.SpartaConnect.111812
-	0	com.spartascience.SpartaConnect.136724
-	0	com.spartascience.SpartaConnect.136288

From Apple Developer Forums:
https://developer.apple.com/forums/thread/120782

launchctl list
shows bundle identifiers of running application, there is a number after that what is it?
With regards the number after the bundle ID, you see that for processes that are not part of the normal launchd lifecycle management (that is, things other than launch daemons, launch agents and XPC Services).  It’s a unique ID that’s used to distinguish between multiple processes with the same bundle ID.  It has no documented meaning that you can rely on.

launchctl list com.spartascience.SpartaConnect.136288
{
	"LimitLoadToSessionType" = "Aqua";
	"Label" = "com.spartascience.SpartaConnect.136288";
	"OnDemand" = true;
	"LastExitStatus" = 0;
	"Program" = "/tmp/SpartaConnect-1019600858.app/Contents/MacOS/SpartaConnect";
	"ProgramArguments" = (
		"/tmp/SpartaConnect-1019600858.app/Contents/MacOS/SpartaConnect";
		"-moveToApplicationsFolderAlertSuppress";
		"YES";
	);
};

It's looks like harmless ended processes during UI tests.
Not sure why launchctl would keep them around for long.
Should be fixed by https://github.com/sparta-science/connect/commit/6b54bc4d0ecbea99920c46193f1243ef962b79a6
and will keep an eye on it.


Fix flaky "[ref_id:1182]Probes for readiness should succeed [test_id:1202]with working HTTP probe and http server, no ip family is specified"

What this PR does / why we need it:
Currently the network readiness probes tests flow:

Creating a VM with TCP/Network readiness probe.
Wait for the VM to start.
Start TCP/HTTP probe server inside VM.
Assert on virt-launcher pod and VM not ready state;
both virt-launcher pod have Condition PodReady==False
or Condition Ready absence.
Assert on virt-launcher pod and VM ready state;
both virt-launcher pod and VM has Condition Ready==True.

Asserting pod and VM not-ready state after invoking probe
server is start command might introduce flakes to those tests.
There might be a race between the time the probe server
inside the VM is ready and the assertion on the pod/VM
Condition Ready sampling.
This commit changes the flow of these tests by moving
the pod and VM not ready state assertion to be checked
before invoking probe server start command.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #5316
Special notes for your reviewer:
Release note:

NONE

/cc @EdDev @AlonaKaplan @maiqueb

/sig-network

/retest

/test pull-kubevirt-e2e-k8s-1.19-sig-network

/test pull-kubevirt-e2e-k8s-1.19-sig-network

/retest

/retest

/retest

/test pull-kubevirt-unit-test

@EdDev could you please take another look?

k8s-1.19 lane
[sig-network] [Serial][rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking Multiple virtual machines connectivity using bridge binding interface should be able to reach [test_id:1539]the Inbound VirtualMachineInstance expand_more6m5s | [sig-network] [Serial][rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking Multiple virtual machines connectivity using bridge binding interface should be able to reach [test_id:1539]the Inbound VirtualMachineInstance expand_more | 6m5s
-- | -- | --
[sig-network] [Serial][rfe_id:694][crit:medium][vendor:cnv-qe@redhat.com][level:component]Networking Multiple virtual machines connectivity using bridge binding interface should be able to reach [test_id:1539]the Inbound VirtualMachineInstance expand_more | 6m5s
[sig-network] [Serial][rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy when three cirros VMs with default networking are started and serverVMI start an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked by Default-deny networkpolicy [test_id:1511] should fail to reach serverVMI from clientVMI expand_more | [sig-network] [Serial][rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy when three cirros VMs with default networking are started and serverVMI start an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked by Default-deny networkpolicy [test_id:1511] should fail to reach serverVMI from clientVMI expand_more
[sig-network] [Serial][rfe_id:150][crit:high][vendor:cnv-qe@redhat.com][level:component]Networkpolicy when three cirros VMs with default networking are started and serverVMI start an HTTP server on port 80 and 81 and connectivity between VMI/s is blocked by Default-deny networkpolicy [test_id:1511] should fail to reach serverVMI from clientVMI expand_more

On both tests VMI's did not created on time, their status was Scheduling/Pending
/retest

I would also suggest adding a note about what is lost here: We do not check that the probe with IPv6 is showing the right state when the service is not up.
However, we do have other tests that check it (I think), so you can reason why it is fine to drop it.

@EdDev Well for IPv6 tests it seems it never checked that the probe show the right state when the service is not up.
First we create the probe backend pod, which is basically a pod that runs tcp/http service that always report ready.
Then we create the VMI with a probe targeted to the backend pod service, as long the backend pod is alive
the VMI state reported as ready.
With this implementation there is no scenario where the VMI and probe backend are up but the service isnt -> VM reports not ready
I can push another commit or on a follow-up PR, to change the probe service implementation so we could control
when the service is up from the tests.
Then we could test the the VM report the right state according to the IPv6 probe service state.

tests, network probes: Remove blankIPFamily tests

There are several typos in the commit: basicity, en. Please check all your commits for typos.
You also repeat yourself in the commit.

Moreover having both tests while CI isn't in its best shape
cause more flakiness, the test:
[test_id:1202]with working HTTP probe and http server, no ip family is specified
is quarantined while the IPv4 version inst.

I do not think we need to confuse the future readers with this. It is enough to say we are not interested to check a single test twice. I would drop this section.

Sorry for this the commit message was messed up I fixed it.

/sig network

/cc @AlonaKaplan could you pls take a look? thx!

/approve

/test pull-kubevirt-unit-test


Too long words went broken with colors

Code snippet:
const chalk = require('chalk');
const yosay = require('yosay');

const toBeColored = 'something iloveunicornsiloveunicornsiloveunicornsiloveunicornsiloveunicornsiloveunicorns';
const str = `Welcome to the polished ${chalk.red(toBeColored)} generator!`;

console.log(yosay(str));

Actual result:
rns is not in red color.

Expected result
Colored sentences should always be in the defined color.

Can replicate that with Node 6.9.5 on OS X


blitz: remove package

This is very out of date, is pinned to an old version of boost, and the last
update was 2.5 years ago marking it as broken. Since no one has fixed it or
upgraded to the least version, it seems a strong indication it's no longer
used/wanted/maintained and should be removed.

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/january-2020-in-nixos/5771/1


Add support for dotnet CLI

Update KoreBuild to support dotnet.
If we want to minimize the disruption, we should consider creating a new package with a new name instead of KoreBuild. What do you think @Eilon @muratg?

Yes, let's keep the current KoreBuild as is, since we will be porting the repos one by one, and in the meantime, we would need the existing KoreBuild to build repos that are not ported yet.

Do we still intend to use Sake?

AFAIK yes. Would you prefer something else?

Oh I just noticed most of the other .NET Core repos were usin xplat MSBuild...

We can certainly discuss the options within the engineering team. Brice, feel free to start a discussion, and include Victor if you do :)

@bricelam nice one :smile:

+1 for anything that's C# based
-1 for anything XML based
How about plain C# console apps? :)

@victorhurdugaci that's under consideration as well.

What are the plans to support DNX web projects? As it stands now, when running KoreBuild with a web project, it just does a "dnu pack" on it. I'm wondering how we will "dnu publish" the web projects.
I just did some quick testing, modifying the makefile.shade file to perform a "dnu publish", but there is no bower installed. Visual Studio works fine, it seems to be using some internal bower version. I imagine we will also have an issue with gulp/grunt not being recognized when executing the project.json's scripts.
Is this still a WIP? Is there another issue tracking this project type?

KoreBuild is a what we use to build ASP.NET 5. It's not the recommended way to use Sake to build and publish web projects. Thus, it doesn't have support for many dnx features. There's no work item to add support for more than what we need to build ASP.NET.
That being said, your change to the makefile looks okay. If you need bower, you have to install it as a separate step and then make it accessible to the build script by adding it to the PATH.
This particular work item is just to make the existing functionality work with dotnet CLI.

Hmm, that is interesting. I have been seeing KoreBuild used on other projects (even Web ones, like here and here) that have nothing to do with the web stack. I understand there is no documentation, but it seemed that this would be future of building .NET projects in general.
Looks like there is an opportunity here then for the community to create sets of commands that can be used in their build.
I'm curious why the #restore-bower-components was created then. Which library of the stack is using this?

There's 2 different components here:

KoreBuild
Sake

I expect that we'all move away from sake at some point when something better comes along. KoreBuild on he other hand will live on. It's an opinionated way to build projects. It relies on a certain directory structure but that's about it. If you can live with those opinions then it'll work great for your projects.

I'm curious why the #restore-bower-components was created then. Which library of the stack is using this?

Either and mvc sample or music store

One more datapoint to consider: we currently depend on Mono to run Sake on osx/linux. We have several compatibility issues with Mono, Nuget, and Entity Framework. Can we use coreclr to run Sake instead?

Sake doesn't run (yet?) on CoreCLR

In that case, +1 for MSBuild, -1 for Sake.

Sake doesn't run (yet?) on CoreCLR

Last I looked, Sake ran fine on Core CLR. However aspnet/dnx#2566 (dnu build , dnu pack can't build for another framework when using Core) leads to a need to run many commands w/ Mono anyhow.

How do you run it on CoreCLR? It seems to only have an exe in it

Sake ran fine on Core CLR

@dougbu could you mean "Sake can launch CoreCLR"? KoreBuild executes Sake using mono.

@natemcmaster I meant it's possible to change KoreBuild to use Core CLR by default from .shade files. The "compatibility issues" you mentioned are primarily about what gets launched.

But Sake itself doesn't run on CoreCLR, right?

@victorhurdugaci correct, Sake.exe is executed against the full CLR (or mono), not CoreCLR.

cc @loudej

What benefit would you get making it a DNX project? It is a command line build tool. I can't imagine people will ever be using sake as a project.json command.

@theonlylawislove the benefit of having it a DNX project is not needing mono at all. You can just have CoreCLR

The work is happening here in case anyone needs the KoreBuild-dotnet package

Do the new commands require environment variables to be already established (via running dnvm use)? Or, does every command take a "use" command, and the application will internally load the appropriate dnx runtime?

dotnet run -f <framework> will run an application from sources on the specified framework. E.g: dotnet run -f dnxcore50
If you run dotnet compile, you'll have executables for each framework

https://github.com/aspnet/common now builds with dotnet

If anyone wants to try to upgrade their repo to dotnet, use this as a reference: https://github.com/aspnet/Common/commit/2137b669f9323498547d6b0d415f4fbdaaeb0b00

I tried to upgrade sqlite, but Mono 4.2.1 + nuget.exe do not agree. Are we making progress on removing our dependency on Mono to build and run?

Use Mono 4.0.5, we know that 4.2.1 is buggy and you'll hit a lot of issues.
Delete the cached NuGet so it can pick the latest version: https://github.com/aspnet/Universe/blob/dev/build-template-dotnet/build.sh#L16-L27

Use Mono ... you'll hit a lot of issues.

A chronic problem. On EF we just avoid mono altogether as Mono seems to be forever-broken. Can we create an x-plat build script that does not depend on Mono and use dotnet completely?

The only thing we'll use mono for is running tests. The cli and nuget will be xplat and self contained

@piotrpMSFT

xunit runner issue (https://github.com/dotnet/cli/issues/18) seems to have something to test with now. @victorhurdugaci When can we test this?

FWIW, dnx testing is no longer working for EF. DNX has not kept up with changes in corefx and on OSX El Capitan, parts of the BCL don't work on "dnxcore50" anymore. We can't test on x-plat until we get an xunit runner to replace dnx

I think someone said this morning that @anurse has a DNX change to remedy this?

https://github.com/aspnet/dnx/pull/3327 - I haven't had a chance to finish it and get it in. If someone wants to take it up, it should basically be working, just needs some quick testing and merging.

MVC is done!  /cc @pranavkm

BAM! Closing this because it is done


Added ability to use milti-pages reports

@savvinsergey,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


chore(l10n): [de] update locale

Added new keys.
projects:toast:loading unity from unity hub
projects:manage:n packages selected
projects:manage:n packages selected
projects:manage:dialog:packages installed in the following directories will be removed
packages:repositories
vpm repositories:tooltip:remove curated or official repository
vpm repositories:dialog:id duplicated
vpm repositories:dialog:url duplicated
settings:button:reload unity from unity hub
settings:tooltip:reload unity from unity hub

Added
"projects:dialog:proceed k/n"
"projects:button:backup and migrate"

I will add the china-unity specific keys at a later date, it is unlikely to see that as german user.
Ready to merge.

OK, Thank you for quick response.


Command "app register --type source --name....." was found but is not currently available

Hi ,Contributors
@mstine @royclarkson @jstrachan @rmorgan @jvalkeal
I deploy the 1.2.2.RELEASE on kubernetes cluster and metadata is stored in MySQL,and use the 1.2.2.RELEASE shell for client.
1.Login with shell.
server-unknown:>dataflow config server --username admin --password admin --uri http://<IP_ADDRESS>
Successfully targeted http://<IP_ADDRESS>

2.Register stream App .
dataflow:>app register --type sink --name log --uri docker://springcloudstream/log-sink-rabbit:1.2.0.RELEASE --metadata-uri maven://org.springframework.cloud.stream.app:log-sink-rabbit:jar:metadata:1.2.0.RELEASE

But the shell got error info like that:
Command 'app register --type sink --name log --uri docker://springcloudstream/log-sink-rabbit:1.2.0.RELEASE --metadata-uri maven://org.springframework.cloud.stream.app:log-sink-rabbit:jar:metadata:1.2.0.RELEASE' was found but is not currently available (type 'help' then ENTER to learn about this command)
But when i change the metadata from MySQL to H2, it will be Okay!
I have no idea about this is a bug or my misconfig,please give me some advises.
Very much looking forward to your reply.

You would get that error if your shell isn't configured with the url for the server. Could you try issuing a dataflow config info command before the app register command and capture the terminal content of that so we can get a better idea of what's happening.

Hi, @ganshanshan. If you can avoid tagging individuals directly on the issues, that'd help prevent noise. Also, 1) They are not directly involved in the project 2) We actively monitor the backlog, so we will respond to the issues.
Thanks for your interest in SCDF!

Thanks for your reminder ,@sabbyanandan .
Next time I will pay attention to this matter.

Hi, @trisberg .
Must clarify that i deploy the SCDF on Openshfit.At the beginning,I think the deployment on the k8s is the same to Openshfit. Yes later i notice the READ.adoc from Spring Cloud Data Flow that

There are also community maintained Spring Cloud Data Flow implementations for Hashicorp’s Nomad and RedHat’s Openshift.

I make a mistake, but i hope that you can support the Openshift officially,also, if you have other advise,please do not hesitate to tell me.
Thanks for your time.

I'm having a similar issue with Kubernetes 1.7.2 and Minikube 21.0
dataflow:>dataflow config info
╔═════════════════╤═══════════════════════════════════════════════════════╗
║     Target      │              http://<IP_ADDRESS>:30426              ║
╟─────────────────┼───────────────────────────────────────────────────────╢
║     Result      │   Successfully targeted http://<IP_ADDRESS>:30426   ║
╟─────────────────┼───────────────────────────────────────────────────────╢
║                 │Analytics Enabled: true                                ║
║    Features     │  Streams Enabled: true                                ║
║                 │    Tasks Enabled: true                                ║
╟─────────────────┼───────────────────────────────────────────────────────╢
║                 │spring-cloud-dataflow-server-kubernetes: 1.2.2.RELEASE ║
║    Versions     │            Spring Cloud Data Flow Core: 1.2.3.RELEASE ║
║                 │               Spring Cloud Dataflow UI: 1.2.1.RELEASE ║
╟─────────────────┼───────────────────────────────────────────────────────╢
║                 │         Authenticated: true                           ║
║                 │Authentication Enabled: true                           ║
║    Security     │ Authorization Enabled: true                           ║
║                 │            Form Login: true                           ║
║                 │              Username: admin                          ║
╟┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┼┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈╢
║      Roles      │                      ROLE_MANAGE                      ║
║                 │                       ROLE_VIEW                       ║
╟─────────────────┼───────────────────────────────────────────────────────╢
║                 │Deployer Implementation Version: 1.2.2.RELEASE         ║
║                 │                  Deployer Name: KubernetesAppDeployer ║
║                 │           Deployer Spi Version: 1.2.2.RELEASE         ║
║                 │                   Java Version: 1.8.0_111-internal    ║
║  App Deployer   │           Platform Api Version: v1                    ║
║                 │        Platform Client Version: unknown               ║
║                 │          Platform Host Version: unknown               ║
║                 │                  Platform Type: Kubernetes            ║
║                 │            Spring Boot Version: 1.5.4.RELEASE         ║
║                 │                 Spring Version: 4.3.9.RELEASE         ║
╟┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┼┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈╢
║Platform Specific│ namespace: default                                    ║
║                 │master-url: https://kubernetes.default.svc/            ║
╟─────────────────┼───────────────────────────────────────────────────────╢
║                 │Deployer Implementation Version: 1.2.2.RELEASE         ║
║                 │                  Deployer Name: KubernetesTaskLauncher║
║                 │           Deployer Spi Version: 1.2.2.RELEASE         ║
║                 │                   Java Version: 1.8.0_111-internal    ║
║  Task Launcher  │           Platform Api Version: v1                    ║
║                 │        Platform Client Version: unknown               ║
║                 │          Platform Host Version: unknown               ║
║                 │                  Platform Type: Kubernetes            ║
║                 │            Spring Boot Version: 1.5.4.RELEASE         ║
║                 │                 Spring Version: 4.3.9.RELEASE         ║
╟┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┼┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈╢
║Platform Specific│ namespace: default                                    ║
║                 │master-url: https://kubernetes.default.svc/            ║
╚═════════════════╧═══════════════════════════════════════════════════════╝

Some commands work, others dont:
dataflow:>app register
Command 'app register' was found but is not currently available (type 'help' then ENTER to learn about this command)
dataflow:>stream destroy
Command 'stream destroy' was found but is not currently available (type 'help' then ENTER to learn about this command)
dataflow:>stream list
╔══════════╤═══════════════════════════════════════════════════════════════════════════════════════════╤═════════════════════════════════════════════════════════════════════╗
║  Stream  │                                     Stream Definition                                     │                               Status                                ║
║   Name   │                                                                                │                                                                     ║
╠══════════╪═══════════════════════════════════════════════════════════════════════════════════════════╪═════════════════════════════════════════════════════════════════════╣
╚══════════╧═══════════════════════════════════════════════════════════════════════════════════════════╧═════════════════════════════════════════════════════════════════════╝

I tried to delete and recreate the server, but that did not help. I will recreate the cluster now and see how that helps.

The admin user has limited access rights. Try authenticating with the user account, the default password for this account is password.

In fact that seems to be the problem. With the default credentials I'm able to use the commands while with the admin I do not. Thanks for pointing out.


Minor fixes in the CP migration TM tests

How to categorize this PR?

/area control-plane-migration testing
/kind bug
What this PR does / why we need it:
Minor fixes in the CP migration TM tests
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

/retest-required

/retest-required


Remove branch specification from dependent container build workflows [SAME VERSION]

What this PR does / why we need it:
Upon creating a release, our workflows that are dependent on the Build Production Rust Code workflow are not triggered due to the main branch specification.

Removing the 'main' restriction will trigger it on forks as well. How about adding another condition on release

Actually I just noticed this only executes only when the other workflow completes and the other one has the on release trigger.


Mongodb -> Postgres :: unsupported type mejson

Directions
I am using transporter to migrate MongoDB data to Postgres. One issue I've run into is when I have a JSON array stored in Mongo. For this particular piece of data, I would like to store it as JSON in Postgres as well but get the following error.
ERROR: write message error (sql: converting Exec argument $5 type: unsupported type mejson.S, a slice of interface)  path="source-mongo/9d6e36b4-5e08-4ecf-5f19-4ab91de10d08/c2efc68a-8883-441d-4f08-69203041bd36/sink-postgres"

Example of the value it errors on:
[
  {
    "data": "https://localhost/venue/12345/header.jpg",
    "name": "header"
  }
]

System info:

Transporter version
v0.2.1

OS
Mac OSX (Sierra)

DB version(s)
Mongodb v2.6.3
Postgres v9.5.5

Proposal:
Add support for JSON in the Postgres adapter.

@remotevision thanks for the details in the issue report. it looks like you're also using 2 JS transformer functions. Can you provide the pipeline.js and the JS transformer functions being used?

absolutely. Here you go.
pipeline.js
Source({name:"source-mongo", namespace:"production.venues"})
.transform({ filename: "venue-remove-fields.js", namespace: "venues." })
.transform({ filename: "venue-rename-fields.js", namespace: "venues." })
.save({name:"sink-postgres", namespace:"venues./.*/"})

venue-remove-fields.js (stuff at the bottom is for troubleshooting)
module.exports = function(msg) {
  delete msg.data._id;
  delete msg.data.__v
  delete msg.data.displayName;
  delete msg.data.categories;
  delete msg.data.tags;
  delete msg.data.markets;
  delete msg.data.location;
  delete msg.data.hoursOfOperation;
  delete msg.data.twitterHashtags;
  delete msg.data.instagramHashtags;
  delete msg.data.facebookPage;
  delete msg.data.contacts;
  delete msg.data.privateNotes;
  delete msg.data.comments;

  // temp
  // delete msg.data.images;
  console.log(JSON.stringify(msg.data.images));
  delete msg.data.barcodeTypes;
  delete msg.data.phone;
  delete msg.data.partner;

  return msg;
};

venue-rename-fields.js
module.exports = function(msg) {

  msg.data.siteUrl = msg.data.siteurl;
  delete msg.data.siteurl;

  msg.data.pin_number = msg.data.pinNumber;
  delete msg.data.pinNumber;

  msg.data.barcode_types = msg.data.barcodeTypes;
  delete msg.data.barcodeTypes;

  msg.data.media = msg.data.images;
  delete msg.data.images;

  msg.data.partner_id = msg.data.partner;
  delete msg.data.partner;

  msg.data.updated_at = msg.data.modified;
  delete msg.data.modified;

  msg.data.created_at = msg.data.created;
  delete msg.data.created;

  return msg;
};

ok, I think I see the problem, not sure I'll have time to get anything pushed up this weekend but will get to it for sure on Monday.

@remotevision I just published v0.2.2 to see if it addresses your issue, please grab a binary from https://github.com/compose/transporter/releases/tag/v0.2.2.

Awesome, I'll try it out tonight. Thanks for the quick response!

@jipperinbham thanks for the quick turnaround! just wanted to let you know this worked and everything is good to go.

@remotevision awesome! glad things are working as expected for you now.
just a heads up, we just put out v0.3.0 which was a major overhaul to running transporter, you may want to take a look at the new native transformers (omit and rename).

great to see these added to v0.3.x. I'm having an issue getting my same pipeline setup with the v0.3 version however. digging in more before opening an issue.


Feature/search page clear all options

#1306
Checklist

[x] the [contributor license agreement][] is signed
[x] commit message follows [commit guidelines][]
[ ] tests are included
[x] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
Added a new button to perform a new search with default search options. As the Search bar and Date range selector use their own states to control value, added useEffect to help update their states correctly.
In addition, the test for this button uses react-testing-library so you will see a new describe block. And some warnings were addressed.


Add functionality to feedback flat button

use flutter_email_sender package
https://pub.dev/packages/flutter_email_sender/example

Can I work on this issue ?


Add a demo data bucket : does not exists

in page : https://docs.influxdata.com/influxdb/cloud/query-data/execute-queries/query-demo-data/#add-a-demo-data-bucket
Proposal:
Short summary of the feature.
"Click Add Demo Data, "
Current behavior:
There is no button "add demo data"
Desired behavior:
have it if possible
Alternatives considered:
Describe other solutions or features you considered.
may be the doc is not uptodate
Use case:
Why is this important (helps with prioritizing requests)?
if you want we start easily !

I'm facing the same issue. It used to be the button but not it's gone:

Just saw the RN from November, they remove the feature
It would be nice to have something like the NOAA with a small amount of info and we can create a task to pull the info if we want more :)


Parse HandshakeResponse

Issue: https://github.com/aspnet/SignalR/issues/2621
Properly parsing the handshake response.

The HandshakeResponse being a sub class of HubMessage in C# kind of threw off my thinking of how this should look. I'm going to re work it

Updated

This is updated with a refactored MockTransport.

I realize we're all busy with the hackathon but it would be awesome if I could get a last review and get this in, because I could also merge https://github.com/aspnet/SignalR/pull/2660 and then have a another pr ready  for when we're back on our regular work schedules 😄


redpanda/fix: Fix the conditions for the values of console

Fix #833
I suppose the conditions of .Values.console are opposite.

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

Fix #833
I suppose the conditions of .Values.console are opposite.

This isnt doing what you think it is doing. The overrides here are to determine if we create those for you, based on the values file of redpanda, or if you rather have the defaults deployed. It is confusing, i grant you that point. I am reviewing your original   issue and i may have some solutions. For now I think we should close this PR.


For Each HashMap Item

I have a map of type: HashMapStructure<string, number>
How can I iterate through it?
Can't find any docs or intructions.

Hey there, yeah the docs are lacking at this points. There are a few ways you can iterate through entries:
import * as HashMap from '@collectable/map`;

const map = getMyHashMapSomehow();

// The HashMap structure actually implements [Symbol.iterator]:
for (let [key, value] of map) {
  // ...
}

// The above internally just makes the following call:

const iterator = HashMap.entries(map);
const first = iterator.next();
const [key, value] = first.value;

// There are also methods for keys and values:

const keysIterator = HashMap.keys(map);
const valuesIterator = HashMap.values(map);

// And of course you can always make an array out of any of these:

const keys = Array.from(HashMap.keys(map));
const values = Array.from(HashMap.values(map));
const entries = Array.from(map);

For a list of available functions and their signatures, check out:
https://github.com/frptools/collectable/tree/master/packages/map/src/functions

If I try to do:
for (let [key, value] of map) {
      console.log(key);
}

I get this error:

error TS2495: Type 'HashMapStructure<string, number>' is not an array type or a string type.

Oh, that's TypeScript being lame. It is actually valid, but TypeScript is failing to recognise the [Symbol.iterator] property. I'm not sure what your compiler settings are, but maybe this will help. Alternatively, try casting it to any and then to Array<[K, V]> where K and V are your key and value types.

I just ran the following quick tests in JavaScript and had no issues:
// Test when constructing from an array

const map1 = HashMap.fromArray([
  ['foo', 10],
  ['bar', 20],
  ['baz', 30],
]);

for (let [key, value] of map1) {
  console.log(key, value);
}

// Test when constructing from an object

const map2 = HashMap.fromObject({
  foo: 10,
  bar: 20,
  baz: 30,
});

for (let [key, value] of map2) {
  console.log(key, value);
}

// Test when adding items manually

let map3 = HashMap.empty();
map3 = HashMap.set('foo', 10, map3);
map3 = HashMap.set('bar', 20, map3);
map3 = HashMap.set('baz', 30, map3);

for (let [key, value] of map3) {
  console.log(key, value);
}

// Test adding a lot of items

const map4 = HashMap.empty(true);
for (let i = 0; i < 1000; i++) {
  HashMap.set(i, `#${i}`, map4);
}

for (let [key, value] of map4) {
  console.log(key, value);
}

Closing this as it appears to be a non-issue.


Migrate azure-storage-file-share to azure-json and azure-xml

Description
Migrates azure-storage-file-share to azure-json and azure-xml and removes all usages of Jackson. Shares has both JSON and XML which is why it is migrating to both libraries.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

/azp run java - storage - tests

/check-enforcer override

Overriding check enforcer as live tests validated no regressions, failing due to flaky tests that were happening before the PR. code-quality-reports was also failing before this PR.

@alzimmermsft maybe you can help me here. Since this change I am having trouble when compiling native with quarkus.
With the update to com.azure:azure-storage-file-share:12.22.0 (which includes this change) the directory client keeps returning an empty list when calling listFilesAndDirectories even if there is data. It does work as expected when executing the application as jar. I kind of would have expected an exception when running it nativley or anything like that. But there is none, which makes this problem quite hard to debug. SO currently I am still puzzled. That is where I hope that you might be able to give me a hint 🙏
With the change to azure-xml/json, are there any classes (services) which need to be registered for reflection which are not obvious? Anything special to watch out when compiling native?

@HerrDerb could you please share a quarkus sample to repro this issue? With migration to azure-xml/json, the use of reflection to serialize/deserialize has significantly reduced. So, I am not sure if that is causing an issue. It would be helpful to see sample code.


presence and absence are switched

Nest hasn't been set to away at all.
Those 11 hours should be Presence hours.
http://i.imgur.com/SwrdS6W.png

Same as issue https://github.com/gchenuet/nest-datagraph/issues/5
I'll dig around later, think this can be closed.

Hi,
I'm currently working on this problem.
I'll fix the problem and modify the design by percentage instead of hours, for a better comprehension.
Is it ok for you ?

Awesome. Maybe you can show the hours in a tooltip when you hover over the percentages?

Hi,
I just pushed a new version with pourcentage and hours  when you hover over the pourcentage.
More info


updateauth not recorded by v1 history plugin if account does not exist when referenced

It appears one of the history tables isn't getting updated when an account does not exist but is referenced in an updateauth call:
Example, two accounts both having been delegated a linked permission: one shows no trace in either the block explorer or the get_controlled_accounts endpoint and other does:
curl -s -XPOST http://testnet.fio.dev/v1/history/get_controlled_accounts -d '{
  "controlling_account": "gjkdwmtx2tse"
}'
...
{
  "controlled_accounts": [
    "l35p5swqgvoo"
  ]
}

vs.
curl -s -XPOST http://testnet.fio.dev/v1/history/get_controlled_accounts -d '{
  "controlling_account": "voterxbrq3vw"
}'
...
{
  "controlled_accounts": []
}

The difference is that the first account was created via newaccount after a trnsfiopubky. The second account was linked before the account had been created.
It may be a good idea to either 1) reject updateauth referencing a public key without an entry in the accountmap table for fio.address, or 2) modify the v1 history plugin to index the event. I'm guessing option 1 is much less work.
Neither account show traces of the activity when calling get_actions, though I'm not certain this behavior differs from eos' v1 history plugin and I suspect that's ok - indexing that would require inspecting the action details since the account is neither the receiver or actor.

should have noted, the expected result for the second get_controlled_accounts api call should include rssuh33ljdbm

We need to explicitly index the entry when an an account that was just created with newaccount is involved in subsequent inline actions, we're doing this for a few others already and I suspect there could be a few more. I'm already working in history.cpp at the moment so I will take a peek.
Option 2 is more uniform with current logic and I think should be included, we should explore option 1 in more detail.

On second though, option 1 probably isn't desirable because when using updateauth (but only when exclusively using keys as the authority) the controlled account pays the fees for a linked action. There is some utility in this scenario, as it is only signature validation--an account isn't needed because the actor and permission are both tied to the controlled account.
For example, the following sequence (assuming the pubkey in the updateauth has no existing account) works:
clio -u http://dev:8889 set account permission o2ouxipw2rt4 nonexist '{
    "threshold": 1,
    "keys": [
      {
        "key": "FIO8mu91eebrTHhesDw1fDf3MgPqDTVveFmynQYQkyqke1UZHftUU",
        "weight": 1
      }
    ],
    "accounts": [],
    "waits": []
  }
'<PHONE_NUMBER> active -p o2ouxipw2rt4

clio -u http://dev:8889 set action permission o2ouxipw2rt4 fio.address regaddress nonexist 400000000 -p o2ouxipw2rt4

clio wallet import --private-key 5JXMDmoU8..........................................

clio -u http://dev:8889 push action fio.address regaddress '{
  "fio_address": "shouldthisbeallowed@dapixdev",
  "owner_fio_public_key": "FIO6G9pXXM92Gy5eMwNquGULoCj3ZStwPLPdEb9mVXyEHqWN7HSuA",
  "max_fee":<PHONE_NUMBER>0,
  "actor": "o2ouxipw2rt4",
  "tpid": ""
}' -p o2ouxipw2rt4@nonexist

This isn't entirely different than using a signing key for block production, it's just a signature and there is no "accounting" involved for the key, hence no need for an account.
If a client were to derive the pubkey from the signature, and assumed a 1:1 relationship between a public key and account--as is normally the case in FIO, it could cause some confusion, though I think the utility of using arbitrary keys with linkauth overrides this, and I think it's an edge case where a client go through the effort to derive the pubkey from the signature, then convert it to an account instead of looking at the authority provided in the transaction.
It is noteworthy that attempting updateauth using the accounts vector (ie msig) does fail when the account does not exist.
TL;DR you are right, this is solely a history issue.

Added updateauth to chain history plugin so actions get added to the chain log as per the PR above. Closing.


sort percentages in ascendant way

It would be nice if we could sort the percentages ascendant:

If I am not mistaken (tagging @nmercadeb to correct me) the order of rows is taken from the summarise_result. So it would be nice if we can do this in the postprocess of the results @martaalcalde

Yes, I think it is as you described!

This affects tableClinicalRecords() function.

sort percentages internally in tableClinicalRecords before calling the visOmopResults::visOmopTable function


[Dashboard] Include locked and unlocked to shared filtering

#14386
This PR includes:

Setting locked param to undefined to enable locked and unlocked maps or datasets in the shared filtering.

Remove duplicated filters.js settings.

I have just checked it in acceptance and works great! :)


[Google Bard] ...

Extension
https://www.raycast.com/EvanZhouDev/raycast-bard-ai
Description
Hi
Doesnt seem to work. I've copied the cookie details correct (and on Safari).
Steps To Reproduce

Enter cookie details upon installation.
Activate bard (e.g explain)
Unable to reach Bard.

Current Behaviour
No response
Expected Behaviour
No response

Have you tried going to bard.google.com, clearing cookies, and getting a new PSID?
Also, if its still not working, use the extension for the official Bard API: https://www.raycast.com/EvanZhouDev/raycast-google-palm


Add arm64 Docker image.

Since you're offering so many different binaries have you thought about offering an arm64 Docker image?

I've looked around a bit but I'm not sure how to serve multiple architectures on Docker. I'll keep it in mind and look around more.
There's so many os/architecture combos offered because Go is inherently cross-platform so I can just build all of the variants with 1 command.

You typically do that with Docker tags.


Move definition of number of lanes per sequencer into database from SequencingProcess

It appears that currently the number of lanes for each kind of sequencer is hard-coded into the labman.db.process.SequencingProcess class at
https://github.com/jdereus/labman/blob/3cd014c1039a65542bce0f7e127d7db65699a66d/labman/db/process.py#L2408-L2410
I believe the kind names here are (a subset of the) values from the description field of the qiita.equipment_type table, which is populated in labman.db.support_files.db_patch_manual.sql, lines 39-45:
-- Populate the equipment type table
INSERT INTO qiita.equipment_type (description) VALUES
    ('echo'), ('mosquito'), ('EpMotion'), ('King Fisher'),
    ('tm 1000 8 channel pipette head'), ('tm 300 8 channel pipette head'),
    ('tm 50 8 channel pipette head'), ('HiSeq4000'), ('MiniSeq'), ('NextSeq'),
    ('HiSeq3000'), ('HiSeq2500'), ('HiSeq1500'), ('MiSeq'), ('NovaSeq'),
    ('Not applicable');

I worry that in the future, someone will add a new sequencer to the equipment table but forget to update the hardcoded lane values.

Good point @AmandaBirmingham - the idea was to provide a GUI to add values to those tables (and ask for all the required information) but was low in priority since new sequencers is not something that happens pretty often :)

As @AmandaBirmingham pointed out, a method for adding new sequencers should be present by full launch.

Not sure this issue is an actual requirement for full launch, to put it in perspective: how often do we add a new sequencer and when do we expect to add a new one?

@antgonza I feel like if and when it does happen, we'll totally forget to update this, if it's just buried in the code, but that is just my $0.02.

Yes, we could get away with going to full launch without this ... but we DO need to do it at some point.  I mean, we can put it off till the next milestone after full launch (what is that, by the way?) but we can't just dump it to "nice to have" bc as @charles-cowart points out, there is a strong chance we'll forget about it if it isn't standing in the way of achieving some milestone.

See https://github.com/jdereus/labman/issues/507#issue-442364742 re related issues to be fixed at same time as this.


Compatibility with kubernetes 1.26

I'm currently running webhook-desec with kubernetes 1.25 and the logs shows the following deprecations:
2022-11-26 17:32:38 | W1126 16:32:38.400630       1 warnings.go:70] flowcontrol.apiserver.k8s.io/v1beta1 PriorityLevelConfiguration is deprecated in v1.23+, unavailable in v1.26+; use flowcontrol.apiserver.k8s.io/v1beta2 PriorityLevelConfiguration
2022-11-26 17:31:23 | W1126 16:31:23.592937       1 warnings.go:70] flowcontrol.apiserver.k8s.io/v1beta1 FlowSchema is deprecated in v1.23+, unavailable in v1.26+; use flowcontrol.apiserver.k8s.io/v1beta2 FlowSchema

The deprecated apis will disappear in versión 1.26.
Seems that cert-manager example project has updated depencencies.
I'm going to try to do a PR updating dependencies, even though my knowledge of go is negligible, i'll try.

I created a PR with updates to go and api versions, based on original cert-manager-webhook-example.
I have currently running on kubernetes 1.25 and didn't show any deprecation warnings.

Hi, is your stuff still up and running with the newer version? If yes, could you release your changes, maybe in a fork?

I have it working with kubernetes 1.26 without problems, but with warnings about deprecations in future versions:
2023-03-29 10:42:19 | W0329 08:42:19.438919       1 warnings.go:70] flowcontrol.apiserver.k8s.io/v1beta2 FlowSchema is deprecated in v1.26+, unavailable in v1.29+; use flowcontrol.apiserver.k8s.io/v1beta3 FlowSchema
2023-03-29 10:35:51 | W0329 08:35:51.434751       1 warnings.go:70] flowcontrol.apiserver.k8s.io/v1beta2 PriorityLevelConfiguration is deprecated in v1.26+, unavailable in v1.29+; use flowcontrol.apiserver.k8s.io/v1beta3 PriorityLevelConfiguration

and some warnings in kubernetes-api about rate limited requeue.
I'm not an expert in kubernetes dev, and have very basic knowledge in go, that's why I haven't been brave enough to release a fork.
I think the best solution is desec.io implements RFC2136, with is supported directly by cert-manager  and kubernetes external-dns, but I don't know if this will ever happen.

@kmorning if you are in any way unhappy with the self-promotion below, please let me know and I will delete my comment.
If anyone is still looking for an updated version of this hook, I have created another solver for desec which can be deployed via helm. It's available at irreleph4nt/cert-manager-webhook-desec-http.


Updated for most recent PEP compliant assert statements

Description
There has been a PEP update which means that our lint CI is now failing. This is a relatively straightforward change, which touches a lot of the tests, but otherwise does little, changing
assert(...) to assert ...
Checklist:

[X] I have performed a self-review of my own code
[X] My code is PEP8 compliant (flake8 anesthetic tests)
[X] My code contains compliant docstrings (pydocstyle --convention=numpy anesthetic)
[X] New and existing unit tests pass locally with my changes (python -m pytest)
[ ] I have added tests that prove my fix is effective or that my feature works

:grep assert( -r: search for assert('s across all files
qqf(%x``r nq: record macro q which removes brackets
100@q run this macro 100 times on the current file
:cnf cycle changelist to next file and repeat the above step. Strongly recommend Practical Vim.

Strongly recommend Practical Vim.

This is actually my bathroom literature...^^


Add link with some 5a-75b hacking

In https://zeromips.org/posts/2022-05-29-5a-75b I have documented my modification of the 5a-75b board. I suppose this could be helpful/encouraging for others. As this github repo is the de facto standard documentation, maybe you could add a link to my post here.

I'll gladly add a link, but would you kindly file a PR? :)

Thanks, done.

Thank you!


chore(types): make Props param in ShorthandValue and ShorthandCollection required

This PR makers P in ShorthandValue<P> required, this will allow to get better autocomplete, improve types and generate better prop definitions.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


docs: add db connection instructions

Changes in this PR
Update documentation to include DB connection instructions

No longer required. Docs already have instructions for DB


Settings don't save

Title says it all :)
No matter what I change, everything is reverted when I click OK :(
The "Apply" button is also never enabled, perhaps that's related?
IntelliJ IDEA 2022.2.1 (Ultimate Edition)
Build #IU-222.3739.54, built on August 16, 2022
Runtime version: 17.0.3+7-b469.37 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 8
Kotlin: 222-1.7.10-release-334-IJ3739.54

Hi, thanks for your report.
It seems that there is some issue with settings page integration. I'll try to look into it.
In the mean time, feel free to use settings window from toolbar or context menu - when editing file via BinEd plugin.

Seems that page has to be reported as modified so that save/apply method is called :-/
Updated current development build:
https://bined.exbin.org/download/?bined-intellij-plugin.zip


fix: remove unwrap from address derive

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

merged with this pr: https://github.com/MystenLabs/sui/pull/14055


App Hub Application Stopped Working,  it was deployed to Teams in February 2024 when it worked flawlessly untill July 2024

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[X] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
VS Code,

Node : 16.20.2
NVM : 1.1.12
Build tools version: 3.18.1
SPFx,
Teams Toolkit,
Project app-hub version:0.0.2
SharePoint Online

Describe the bug / error
The app rendered the SharePoint list with the use of  TypeScript/JavaScript/jQuery, into a graphical representation of the list of linkages logged in the SharePoint List.

This was working perfectly until the first week of July and since then it has stopped rendering the links and looks like this.

Sorry, something went wrong
Can't load the application on this page. Use the browser Back button to retry. If the problem persists, contact the administrator of the site and give them the information in Technical Details.
TECHNICAL DETAILS
Error details: Error: Error initializing application. Error: TypeError: Cannot read properties of undefined (reading 'componentType')
[Troubleshoot issues with Microsoft SharePoint Foundation.](javascript:HelpWindowKey('WSSEndUser_troubleshooting'))
Correlation ID: 564d43a1-c08c-9000-a2f1-704aad0a5276
Date and Time: 8/5/2024 6:09:19 AM
The warning indicates that there is an issue connecting to the SharePoint resource. I have opened the web version of Teams to investigate further, in the developer's tools I found the following.
Errors:

Warnings:

Information:

There are authorized connections using tokens being displayed.
Which makes me question the connections being made to the SharePoint site to retrieve the data.
There are 3 errors from Precompiled-web-work…js, flowed by a 403 error which is a connection to graph.microsoft.com which I assume is a denial of connection to the SharePoint API, which I use in the TypeScript code:

The next error Refused to compile or instantiate Web Assembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'nonce-R+g9VdMVCZC/eeynejoLZg==' 'report-sample' 'self' https://statics.teams.cdn.office.net/
Details a Policy instructing the denial of connection followed by 4 SharePoint JSON [Object Object] validation error because the code is returning a blank key: value pair array.
Assuming that a further “handshake” was required (either an access token or initiation using SSO) I tried to re-authenticate and tokenize the SharePoint connection request, this failed due to a CORS violation and late finding out that it was not required and a simple spHttpClient request would suffice to facilitate the REST API. However other people are having a 403 connection error to SharePoint Lists
Steps to reproduce
The  Production App

Click on Icon
page would have loaded
Error loads

The Dev

Click On Environment local.
Same error page loads.

if you open Terminal and run gulp serve
the images in the application load
Expected behavior
The App is meant to look like this:

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ]  💥 Internet Explorer
[x]  💥 Microsoft Edge
[x]  💥 Google Chrome
[x]  💥 FireFox
[ ]  💥 Safari
[ ]  mobile (iOS/iPadOS)
[ ]  mobile (Android)
[ ]  not applicable
[ ]  other (enter in the "Additional environment details" area below)

Additional environment details
VS Code,

Node : 16.20.2
NVM : 1.1.12
Build tools version: 3.18.1
SPFx,
Teams Toolkit,
Project app-hub version:0.0.2
SharePoint Online

Describe the bug / error
The app rendered the SharePoint list with the use of TypeScript/JavaScript/jQuery, into a graphical representation of the list of linkages logged in the SharePoint List.

This was working perfectly until the first week of July and since then it has stopped rendering the links and looks like this.

Sorry, something went wrong Can't load the application on this page. Use the browser Back button to retry. If the problem persists, contact the administrator of the site and give them the information in Technical Details. TECHNICAL DETAILS Error details: Error: Error initializing application. Error: TypeError: Cannot read properties of undefined (reading 'componentType') Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: 564d43a1-c08c-9000-a2f1-704aad0a5276 Date and Time: 8/5/2024 6:09:19 AM The warning indicates that there is an issue connecting to the SharePoint resource. I have opened the web version of Teams to investigate further, in the developer's tools I found the following. Errors:

Warnings:

Information:

There are authorized connections using tokens being displayed. Which makes me question the connections being made to the SharePoint site to retrieve the data. There are 3 errors from Precompiled-web-work…js, flowed by a 403 error which is a connection to graph.microsoft.com which I assume is a denial of connection to the SharePoint API, which I use in the TypeScript code:

The next error Refused to compile or instantiate Web Assembly module because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'nonce-R+g9VdMVCZC/eeynejoLZg==' 'report-sample' 'self' https://statics.teams.cdn.office.net/ Details a Policy instructing the denial of connection followed by 4 SharePoint JSON [Object Object] validation error because the code is returning a blank key: value pair array.
Assuming that a further “handshake” was required (either an access token or initiation using SSO) I tried to re-authenticate and tokenize the SharePoint connection request, this failed due to a CORS violation and late finding out that it was not required and a simple spHttpClient request would suffice to facilitate the REST API. However other people are having a 403 connection error to SharePoint Lists
Steps to reproduce
The Production App

Click on Icon
page would have loaded
Error loads

The Dev

Click On Environment local.
Same error page loads.

if you open Terminal and run gulp serve the images in the application load
Expected behavior
The App is meant to look like this:

Issue has been resolved. Seems that the issue was caused by SPFx package which was not activated at the tenant level for the Teams experience to pick it up.


Can not access to customClaims object into firestore security rules auth.token.customProp.

Moving issue here from Firestore Node SDK: https://github.com/googleapis/nodejs-firestore/issues/97

Hello, I am also having trouble accessing my customClaims in my Cloud Firestore rules. The claims are being set, but request.auth.token doesn't have them when accessed inside my Firestore rules. The Firestore rules are difficult to debug, so I am not sure what I am doing wrong.
Firebase Function setting the claim:
functions.firestore.database().document('/some/{schoolId}/path/{email}').onWrite(async event => {
....
   const email: string = event.params.email;
   const schoolId: string = event.params.schoolId;
   const newSchoolPermissions = event.data.data();
   const user = await auth.getUserByEmail(email);
   const newClaims = { ...existingClaims, [schoolId]: newSchoolPermissions };
   await auth.setCustomUserClaims(user.uid, newClaims);
....
}

Example Firestore rule function:
function isSchoolAdmin(schoolId) {
      return isSignedIn() &&
        request.auth.token[schoolId] != null &&
        request.auth.token[schoolId].isAdmin == true;
    }

Ignore me, it does work, I just had to log my user out and then in again!

Forcing token refresh should suffice, after you the custom claims are set. In web: firebase.auth().currentUser.getIdToken(true).


Smooth seekbar for video_player

I wish I can make the seekBar of video_player smoother.
Tested on iOS:
https://user-images.githubusercontent.com/60294318/160267816-66399cad-2aed-4e3c-9997-0b1672d0373f.MOV
I used .addListener() of the video player to update the state of the video player controller. I simply declared a variable that stores VideoPlayerValue, then I made a seekBar widget (the long bar that users can seek around the video) using the position value provided in there. I was expecting the widget to be rebuilt as the videoPlayerValue changes, and it did! However, there was one problem, that the movement of the seekBar seemed to be laggy, especially when the video was short.
<what i tried (failed)>
It seemed like the listener func was getting a constant-changing position value with a lag in purpose, for the performance it smth. So, I tried to make a stream that gets the position value every 1000/60ms. However, the position value was still not being updated smoothly; instead, it was updated approximately every 500ms no matter the what duration I choose to update the state.
Btw, i wrote this in my phone, so tell me if I've made any mistakes.
I couldn't find any similar solution in Stack Overflow.

Use case

Proposal

Duplicate of https://github.com/flutter/flutter/issues/90080


[Bug] Inconsistency between scoring in the single-label case for zero-shot classification of text vs. images

Describe the bug
With the zero-shot text classification, if you pass a single label, then it seems that you get back a similarity score instead of a probability-like score that's relative to the other labels.
I tried changing multi_label to false, based on a Github issue, but that didn't change anything.
I'm guessing the way that this is handled depends on the way that the Python library handles it, and I an into an error while testing that:

https://github.com/huggingface/transformers/issues/24008

How to reproduce
import { pipeline } from 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>
let textClassifier = await pipeline('zero-shot-classification');
console.log("multi-label text:", await textClassifier("houston, we have a problem with the thruster", ["astronaut", "forest cabin", "rabbit and lion"], { multi_label: true }));
console.log("single-label text:", await textClassifier("houston, we have a problem with the thruster", ["astronaut"], { multi_label: false }));

let imageClassifier = await pipeline('zero-shot-image-classification');
console.log("multi-label image", await imageClassifier("https://i.imgur.com/fYhUGoY.jpg", ["astronaut", "forest cabin", "rabbit and lion"], { multi_label: true }));
console.log("single-label image", await imageClassifier("https://i.imgur.com/fYhUGoY.jpg", ["astronaut"], { multi_label: false }));

Expected behavior
There should be some sort of single-label mode that returns a similarity score rather than a value that's relative to the other labels. This appears to be the case already with the zero-shot text classification pipeline, but that may be a bug.
The idea of having a multi_label option seems to be a good idea - so you have to explicitly opt in to getting the similarity score instead of the relative score.
Logs/screenshots

Environment

Transformers.js version: 2.1.1
Browser (if applicable): Chrome

Right, so, the reason behind this is because the original transformers code doesn't include a multi_label attribute for zero-shot image classification. See here.
However, I might be missing something, so, if you can provide the corresponding python code for it, I can make sure the JS version matches the output.

Python code is here:

https://github.com/huggingface/transformers/issues/24008

But as mentioned in that issue, the single-label call to the zero-shot image classification pipeline results in an error, so maybe we'll have to wait and see what the Python maintainers say RE whether that's kind of the expected behavior (i.e. if it's 'invalid'). But it'd be strange if that were invalid given that it's valid for the text pipeline.
But also, the multi_label option doesn't seem to affect the zero-shot text classification in the single-label case above. I'm guessing that if multi_label is set to true and you only give a single label, then it should have a score of 1? Currently that is not the case - it returns the same value regardless of the multi_label value (in the case where a single label is given, to be clear). Or maybe I misunderstand.

Just wanted to provide closure for this issue:

so maybe we'll have to wait and see what the Python maintainers say RE whether that's kind of the expected behavior (i.e. if it's 'invalid').

As stated here, it now just returns 1 in such cases (which is indeed the case here).
From your test-cases, I've compared the output the the python version, and the outputs are exactly the same for 1 and 2, with only minor differences for 3 and 4 due to different image processing in JS:

✅ zero-shot-classification + multi-label text + multi_label: true
✅ zero-shot-classification + single-label text + multi_label: false
✅ zero-shot-image-classification + multi-label text + multi_label: true
✅ zero-shot-image-classification + single-label text + multi_label: false


docs: improve description of export properties

What?
This pull request aims to improve Directory.export, Container.export and File.export description.
Why?
Closes #8706

Ping @marcosnils for review


How to show fragment from MaterialSectionListener

Hello.
Is there a possibility to show fragment from listener?
I want to do something like this:
        sectionMonitored = this.newSection("Section", new MaterialSectionListener() {
            @Override
            public void onClick(MaterialSection materialSection) {
                Bundle agruments = new Bundle();
                agruments.putBoolean("key", true);
                DetailsFragment detailsFragment = new DetailsFragment();
                // how to show detailsFragment?
            }
        });

Generally speaking, sometimes we have to perform some action and decide what to show.

You could unprivate method setFragment on MaterialNavigationDrawer. It will give us more flexibility.

Yes, It will be public from the next release

now the setFragment is public


base skeleton component setup

mostly just looked at how linear-gradient was setup for this PR.
Goal is just to get all of the initial package setup done with.
Following PRs will implement functionality.
For this feature, I plan on merging the entire stack once the feature is complete. If you LGTM, I wouldn't merge until we have a working skeleton component.

Current dependencies on/for this PR:

master

PR #1867   👈

This stack of pull requests is managed by Graphite.

Yah, sound good
Get Outlook for iOShttps://aka.ms/o0ukef

From: Stephen Laughton @.>
Sent: Monday, November 13, 2023 7:06 PM
To: tamagui/tamagui @.>
Cc: benjamin @.>; Mention @.>
Subject: Re: [tamagui/tamagui] base skeleton component setup (PR #1867)
@stephenlaughton commented on this pull request.

In packages/tamagui/src/index.tshttps://github.com/tamagui/tamagui/pull/1867#discussion_r1391830719:

@@ -28,6 +28,8 @@ export * from @./select'
export * from @./separator'
export * from @./shapes'
export * from @./sheet'
+// Will uncomment when we have a skeleton component

what does everyone think about standardizing on // TODO: todo item..... format for any todo comments for easy searchability? @natewhttps://github.com/natew @benschachttps://github.com/benschac
—
Reply to this email directly, view it on GitHubhttps://github.com/tamagui/tamagui/pull/1867#pullrequestreview-1728473014, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AATDCI2UCSL3S2GVJ3PIICDYEKYXHAVCNFSM6AAAAAA7JK5VV2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMRYGQ3TGMBRGQ.
You are receiving this because you were mentioned.Message ID: @.***>

closing these unfinished ones you can re-open as a big one