Create a tools page

This wouldn't be hard to do, creating a new blank page doesn't take long, but it's more knowing what to put on it and how that information should be laid out that is the work.

Here are two directions that we could go:

A list of all the tools that exist (something simple and wikipedia-esque - broken out by filters like ... open source, free, subscription etc.

A set of reviews talking about what tools are available out there in the world. Something like what @lyzadanger created for Web Connected Devices

In either case we should have some language explaining that we aren't endorsing one tool over the other. Additionally, it would be super rad to eventually link to tool types from method pages so that we don't have to do the tedious task of suggesting all the potential tools for affinity diagrams (for example).

I'd love to do a synchronous card sort on tools content. It makes sense to
do this part of the design collaboratively. We can't really design a page
without a better idea of the content. I'd like to see a list of tools with
some listed strengths and constraints.
On Wed, Mar 22, 2017 at 11:19 AM, iamjessklein<EMAIL_ADDRESS>wrote:

Here are two directions that we could go:

A list of all the tools that exist (something simple and
wikipedia-esque https://www.wikipedia.org/ - broken out by filters
like ... open source, free, subscription etc.
2.
A set of reviews talking about what tools are available out there in
the world. Something like what @lyzadanger
https://github.com/lyzadanger created for Web Connected Devices
http://wcd-review.bocoup.com/
In either case we should have some language explaining that we aren't
endorsing one tool over the other. Additionally, it would be super rad to
eventually link to tool types from method pages so that we don't have to do
the tedious task of suggesting all the potential tools for affinity
diagrams (for example).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bocoup/opendesignkit/issues/238#issuecomment-288492558,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrJSfxUKGFQzxjWqxlYrQmPCAHQhxzDks5roWZDgaJpZM4MiriU
.

--
Pam Drouin
UX Designer @Bocoup


Increase QPS for persistent connection

Tested your QPS seemed very low 17K QPS on persistent connection .
I used ab - Apache Venchmark with switch -k , it uses HTTP 1.0 keep-alive , so I had to add support to your code .
It went from 11k to 17K , but it's still way lower then my stack based on Boost.asio.
As a side note , your Händlers know too much of HTTP response .
I am not advocating you to change it overnight , but it would be nice to have something like boost proposed in its samples .
You are welocome to visit my project where I utilize 50K QPS CRUD handlers .
https://github.com/venediktov/vanilla-rtb
If you look at CRUD directory you will see http restful handsets that currently do 50K QPS on 4 core 2.2 GHz AMD ubuntu Linux .
Please let me know if you care about this issue , i don't insist you fix it , but I was looking at my performance lately and got to see your stack by accident .
Cheers ,
Vladimir .

Which resource did you test against? The default resource in Simple-Web-Server includes file access and additionally is simplistically written to support large file downloads (for example purposes), which might greatly affect the result. Especially comparing to server resources that does not include file access.

I tested against simple resource ,  restful handler, not file system
server.resource["^/string$"]["POST"]=[](shared_ptr<HttpServer::Response> response, shared_ptr<HttpServer::Request> request) {
        auto content=request->content.string();

        *response << "HTTP/1.0 200 OK\r\nConnection: keep-alive\r\nContent-Length: " << content.length() << "\r\n\r\n" << content;
};

I have tested it with apache benchmark aka ab .
I had to change HTTP to 1.0 and add keep-alive and I added line in your code to support keep-alive
so it does not close connection when it gets in the header from ab  keep-alive instruction .
for(auto it=range.first;it!=range.second;it++) {
                            if(boost::iequals(it->second, "close")) {
                                return;
                            } else if (boost::iequals(it->second, "keep-alive")) {
                                this->read_request_and_content(response->socket);
                            }
                        }

If you add those changes and test with apache benchmark you can let me know what you get, I am getting 17K with persistent connection , but that's way below what Boost.asio can deliver .
I started adding benchmarks to my stack and you can maybe use google benchmark to identify the slow parts ? I am just trying to help .

17000 requests per second

Thank you, but it is quite lower than my own tests on Debian Testing as far as I remember. What g++ and boost versions do you have? That is, in case this would affect the results in some way. I'll look into this more next week. It might also help to know your Ubuntu version? And I take it you use g++ to compile, or do you use clang++ instead?

Hi Christian,
I test both my stack and your stack on the same compiler gcc 5.4 , boost 1.61 , ubuntu 16.04 , both
were built in Release mode , by default cmake creates -O3 optimization builds when you pass
-DCMAKE_BUILD_TYPE=Release
I don't see much difference in how you used Boost.asio vs. how it was utilized in my stack, however there is one settle difference :

use of shared_ptr ( those have impact in multi-threaded executions , it is used everywhere in your stack)
request parser ( multiple pass ? )  - CRUD uses is a single pass parser
async_read_until / async_read / stream_buf ( CRUD uses async_read_some only )

The rest seams fairly same as in CRUD . I can't tell you which piece made it slower then CRUD we
use in vanilla-rtb , we had request from a customer to pass through at least 50K QPS , initially it was
a problem for us too, now we fixed it.
Please let me know if you need more information from me.
Best,
Vladimir.

When compiling with -O3 I get around 63000 req/s using:
httperf --server=localhost --port=8080 --uri=/match/123 --num-conns=200 --num-calls=1000
Without -O3 I get around 18600, so there is a large difference between release and normal build.
With -O3 and ab -k -n 1000 -c 200 http://localhost:8080/match/123 I'm getting around 20000-25000 req/s. Not sure what is going on there. I applied your changes too, so it's not that. Might be some problem with the HTTP/1.0 keep alive-code I'm guessing, since httperf is using HTTP/1.1 by default. I'll look into it more when I got time.
Tested on Intel® Core™ i7-2600 Processor (4 core, 3.40 GHz).

Forgot to mention that the tests were run on Debian Testing with its default g++ (6.3.0).

Hi Christian,
So your tests with ab ( 20-25K ) correlates with mine e.g. 17K on my 4 core 2.2Ghz.
There is a settle difference in httperf and ab :
ab - stops sending request if it does not get responses
httperf - keeps sending requests even without getting response back
httperf is a good tool to stress test our stacks to see what happens when the load doubles, so I will probably add this tool to the suite of tools we use @venediktov/vanilla-rtb to tune up our stack.
One thing helped our team a lot was testing framework google benchmarks, you can see how vanilla-rtb project is utilizing it we have procided description in the README.md in benchmarks folder.
Thank you for your time in testing it out , we learn new things every day, that's what open-source community is good for.
Before I forget , if  in ab you use bigger number of requests -n 20000 you will get more stable results ( basically the QPS will not change much from one run to another ) , e.g.  will not show a big spread like 20K-25K.
Let me know how it goes,  in a meantime I will try out httperf with vanilla-rtb .
Thanks for sharing info.
Best,
Vlad.

I tested some more, and with the following:
ab -k -n 200000 -c 200 http://localhost:8080/match/123
I constantly get around 63000 req/s. Not sure why I get higher req/s with higher number of requests with ab though.
@venediktov I'll also commit your Connection keep-alive (server_http.hpp) code to master if its ok with you. I'll then add you as author of course.

Oh, then it's not an issue if you can get 63K QPS with more requests , on the fast machines I had to give more requests to ab , otherwise it can't calculate QPS correctly,  so the issue can be closed !
Yes,  it would be nice if your stack would support both 1.0 and 1.1 , you can add my name if you want of course .
Btw, If you are interested in technologies related to HTTP our stack depends heavily on HTTP protocol , but we also use UDP  and TCP/IP within our architecture for some models if/when our bidders read segmented ( unrelated ) data.
Currently we are assembling rapid-bidder based on vanilla-rtb stack , which should have complete cycle including bidding , win notifications, audit , campaign management and some management console .
Best,
Vladimir.

I'll close this issue then, thank you Vladimir.


Updated 2020 data

Based on email from Erica, update underlying 2020 acs data. Main check here is verifying

The script still works
The data is correctly for 2020, not 2010

I ran
python3 -m pipelines.acs_2020_manual_update -y 2020 -g 2010_to_2020

and got an output that doesn't look quite right? pop_1 has c=0 for citywide and all boroughs. census_geoid is always NaN. Am I running the wrong thing from the command line? If it's not an issue with the args passed I'm happy to help debug

I think that's the right args - i honestly hadn't finished running it, I figured there wouldn't be an issue since nothing was changing.

So I think census_geoid being always null is actually expected behavior -the column itself is only included to keep the shape of the csv the same. I'm not sure about the 0 for pop_1 citywide - that hasn't changed from previous runs of this script so it either represents a persistent bug or also expected behavior coming from the input script

Ok great. Looking at the source data, I think that "E" is estimate and it looks right. I forgot what each letter stood for


Header/.m/.mm order clean up

Suggestion to move .m and .mm files directly below header file for easier project navigation.
See screenshot below for before and after example.

Thanks
Adam

yeah we just need to right-click -> "sort by name"

@AdamRobertsEF wanna PR it?

@rnystrom yes :-)


Name is use defined now

As per today this documentation is no longer accurate. I have to fill in name and display name, but not plural display name.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 11bacb37-4743-1d0e-d13e-1d9b656c661f
Version Independent ID: 7b4d6192-4282-c5c1-01a2-a3ba065ed6e6
Content: Create a custom entity - PowerApps
Content Source: powerapps-docs/maker/common-data-service/data-platform-create-entity.md
Service: powerapps
GitHub Login: @Mattp123
Microsoft Alias: matp

Correction to my previous comment. It seems depends on the environment. After creating new environment this documentation reflects what user experience.

@leo9912 Thanks for taking time to provide feedback. Closing this issue now.


Fix software classification

It is strange to see "mailpile" in "others" - it is an email client
like others in the "software" list.
Similarly, it doesn't make sense to me that Schleuder is hidden down
into "other" as well, so move it along with the larger group.
An alternative to this would be to rename the "Other" section to
"Server software" which would allow a better regrouping of the
keyserver/webmail/mailing list software under one roof.
What do you think?

@anarcat could you pls change LEAP to LEAP nickserver while you're at it ? Thx!

On 2017-11-25 17:48:10, varac wrote:

@anarcat could you pls change LEAP to LEAP nickserver while you're at it ? Thx!

of course.
--
A genius is someone who discovers that the stone that falls and the
moon that doesn't fall represent one and the same phenomenon.
- Ernesto Sabato

i changed my mind and made #15 to rename the "other" section instead of moving everything to the already crowded "email" section.


[v2] Fix #436 View type missing optional id from response

Summary
This pull request is the v2 branch fix for #436 - cherry-picked from #437
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

@seratch instead of opening a second PR for the @slack/bolt@next branch, i think its easier to allow the PR to merge on master and then merge master into @slack/bolt@next.
@stevengill can you confirm this is how we want to handle this scenario?

Yes, either is fine to me. I just wanted to reduce y’all’s efforts on this considering this timing (last minute before v2 release)

agree with @aoberoi!
Any PR that needs to hit the 1.x branch should be going to master and merged into next from master.
Any PR that is next specific can go straight to next
Closing this PR.


Save on exit

If the service is terminated by SIGTERM, it needs to save all its state or else you lose everything up to the last SAVE_INTERVAL.

I'm honestly not sure this is possible; the crates I've found only work with non-Async closures, plus the handler has to be consumed by Serenity.
If you can figure it out good for you...


Mount theme directory for theme development

Allow easier theme development by exposing the theme directory to the host system.

@hrpatel have you had a chance to review this yet?

You'll need to rebase

Lets get this reviewed but wait to merge depending on what happens with the vendor pricing.. it might be a moot point if we decided to go with Virtual Slate


Refactor HyperShift integration tests for re-run

Summary
This refactoring should make it easier to re-run HyperShift specific tests, because it is no longer producing an error if the hostedcluster CRD is already installed.
A command like this to just run the test you are interested in: ./mage test:packageoperatorintegrationrun
TestHyperShift/ObjectSetOrphanCascadeDeletion
Change Type

Check List Before Merging

[x] This PR passes all pre-commit hook validations.
[x] This PR is fully tested and regression tests are included.
[x] Relevant documentation has been updated.

Additional Information

/approve
/lgtm


[translation] remove sample tests dependency on static storage acc

The sample tests for Document Translation depend on a persistent storage account which needs a container with two small files to test the scenarios in the live CI. We originally were using a static storage account for this in the test-resources.json, but I want to fix this because...

This isn't the right way to use static resources in our live tests
This complicates adding additional cloud configs, e.g. Dogfood. However, I don't think it makes sense to have a static storage account across clouds for just two small files.

The rest of the resources and containers needed for tests/samples can be be dynamically created and torn down as expected.
Live test run pass: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1226274&view=results

Hey @benbp wanted to get your opinion on this PR.
I want to add the Dogfood config to translation live tests, but realized that we currently have a static storage account defined in the test-resources.json which is used to run samples in the CI. All we really need to run samples successfully are two small files which exist locally in the repo. I'm wondering if this is appropriate usage of the test-resources-post.ps1 step to just upload these files to the container created in the template so we can run samples and then tear everything down at the end.
Let me know if there is another way you would recommend over this approach.

This is great. I'm totally behind removing static resources in favor of a reproducible/cloud independent approach.


Implementing Py42ActiveLegalHoldError

Description of Change
Added Py42ActiveLegalHoldError exception. Raised when attempting to deactivate user/device that is in an active legal hold.
Issues Resolved

Fixes #169

Testing Procedure

Use py42.sdk.devices.deactivate() or py42.sdk.users.deactivate() to deactivate a user in an active legal hold.
Observe message Cannot deactivate from user in an active legal hold.

Notes

Create draft PR as I suspect messaging for this exception will need to be updated, and I want to clarify the approach I've taken with this is acceptable before it's reviewed proper.

I changed this from a draft because I think it's pretty much complete.

I approved too soon! We need tests :)
Both users.deactivate() and devices.deactivate() should be tested to make sure that when the connection raises x error containing y text, than it raises this new error Py42ActiveLegalHoldError

My bad. Could've sworn I added those. Just updated :)


memory-map/on-disk index support

Is your feature request related to a problem?
With limited memory resource, it is expensive to load the whole index file to memory and do the knn search
What solution would you like?
The Faiss backend natively support loading on-disk index in a memory-mapped way and do the search on the fly:
https://github.com/facebookresearch/faiss/wiki/Indexes-that-do-not-fit-in-RAM
I would like it to be implemented with open search , or is it already implemented?
What alternatives have you considered?
N/A
Do you have any additional context?
N/A

Hi @n0thing233, in general, I think leveraging disk based ANN approaches could be very beneficial.
There are a couple issues with supporting faiss's implementation:

We wouldnt be able to support it on all platforms. I dont believe it works on Windows
It requires that several smaller indices be merged together to form the on disk based index: https://github.com/facebookresearch/faiss/wiki/Indexes-that-do-not-fit-in-RAM#building-an-on-disk-index. This would be difficult to do for every segment file, unless we decided to create multiple faiss index files per segment.

All that being said, it is definitely worth looking into supporting some form of disk based ANN.

Please +1 if you are looking for this feature to help prioritize

Lets track in #1134


Can you tell me how to configure the overlay network in a non gce environment?

I get great information about how to install kubernetes cluster.
All other parts are well resolved, but the overlay network configuration of the manual is locked-in to gce.
Can you tell me how to configure an overlay network such as flanneld in a pure baremetal environment without cloud dependencies?
I can not use apt-get, yum repo because the internet is blocked.

The overlay networking configured by the kubenet CNI plugin (--network-plugin=kubenet)
I used this guide to create Bare-Metal cluster on private network.
You can find more here https://kubernetes.io/docs/concepts/cluster-administration/networking/ about other plugins...

I am trying to integrate flanneld into the k8s 1.6 installed with this guide, but it is not working.

With k8s v1.7.0-alpha.4 I successfully installed flannel on baremetal and working fine

@domix Could you advise me on my configurations?
Environmental Information
Vagrant + VirtualBox
Master&ETCD: <IP_ADDRESS>
Worker1, 2: <IP_ADDRESS>, <IP_ADDRESS>
docker.service (Worker1)
[Unit]
Description=Docker Application Container Engine
Documentation=http://docs.docker.io
[Service]
ExecStart=/usr/bin/docker daemon
--iptables=false
--ip-masq=false
--host=unix:///var/run/docker.sock
--log-level=error
--storage-driver=overlay
--bip=<IP_ADDRESS>/24
--mtu=1450
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.target
flanneld.service (Worker1)
[Unit]
Description=Flanneld overlay address etcd agent
After=network.target
After=network-online.target
Wants=network-online.target
After=etcd.service
Before=docker.service
[Service]
Type=notify
EnvironmentFile=-/etc/default/flanneld
ExecStart=/usr/bin/flanneld --public-ip=<IP_ADDRESS> -etcd-endpoints=http://<IP_ADDRESS>:2379 -etcd-prefix=/kubernetes-cluster/network $FLANNEL_OPTIONS
Restart=on-failure
[Install]
WantedBy=multi-user.target
RequiredBy=docker.service
kubelet.service (Worker1)
[Unit]
Description=Kubernetes Kubelet
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=docker.service
Requires=docker.service
[Service]
ExecStart=/usr/bin/kubelet
--api-servers=https://<IP_ADDRESS>:6443
--allow-privileged=true
--cluster-dns=<IP_ADDRESS>
--cluster-domain=cluster.local
--container-runtime=docker
--experimental-bootstrap-kubeconfig=/var/lib/kubelet/bootstrap.kubeconfig
--kubeconfig=/var/lib/kubelet/kubeconfig
--serialize-image-pulls=false
--register-node=true
--tls-cert-file=/var/lib/kubelet/kubelet-client.crt
--tls-private-key-file=/var/lib/kubelet/kubelet-client.key
--cert-dir=/var/lib/kubelet
--v=2
--node-ip=<IP_ADDRESS>
Restart=on-failure
RestartSec=5
[Install]
WantedBy=multi-user.target
ip addr show (Worker1)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet <IP_ADDRESS>/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 02:d8:e4:47:7a:33 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global enp0s3
valid_lft forever preferred_lft forever
inet6 fe80::d8:e4ff:fe47:7a33/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:48:2f:16 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global enp0s8
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:fe48:2f16/64 scope link
valid_lft forever preferred_lft forever
4: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
link/ether 56:7d:bf:97:b8:ee brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/32 scope global flannel.1
valid_lft forever preferred_lft forever
inet6 fe80::547d:bfff:fe97:b8ee/64 scope link
valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:45:f7:af:61 brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/24 scope global docker0
valid_lft forever preferred_lft forever

@domix
I wrote my setup information in the body.
Could you advise me on my configurations?

I solved the problem.
The cause was the virtualbox network interface.
The problem was solved by putting "-iface=enp0s8" as the flanneld option.


Updation of and refactoring code in theme to suite Jekyll 3.x

It has been a long time since you have updated the code of the theme to suite the latest editon of jekyll. Ever since Jekyll was upgraded to version 3.x many problems have arisen in your theme. The fact that it now doesn't even build is just one of the many problems which a person currently using the latest version of the theme has to face. Also note that in case you are not interested with changing the code, I would certainly like to fork your code, but only with your permission.
-A true fan of Mickey

Hi. I would really like to use this theme, however as @Devdutt-Shenoi said, there seems to be issues with the latest versions of Jekyll and other packages. I'm not sure how to troubleshoot, but would be happy to give you debug outputs if you'll guide me on what to do.
Hope to hear from someone soon.

I actually am running this theme on my blog, but I vastly simplified it and removed a lot of the "bulk"? Technically it's still the same theme but with a couple of UI improvements.
Check it out here: http://harshbaid.com/blog/

@cinnapple Thanks!


Fix Hardhat compile error when public variables are used to implement interface functions

When modifying solc input to extract namespaced storage layouts, interface functions are kept (because constants might refer to their function selectors), but we effectively remove state variables (by converting them to dummy enums).
If an interface has a function, which is implemented using a state variable to provide a public getter, then this causes a compile error because the modified solc input (with state variable converted to dummy enum) would no longer have the public getter.
We can resolve this by converting all contracts in the modified solc input to abstract.
Fixes https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/1053

Immutables are also effectively removed.  Since we are converting contracts to abstract now,

Immutables are also effectively removed.  Since we are converting all contracts to abstract now, removing immutables also avoids the following from being an issue:
contract DeploysContractToImmutable {
    MyContract public immutable myContract = new MyContract();
}


Added missing vb sample.

Thank you for adding a Visual Basic version of this example, @Youssef1313. Extensions methods, though, must be in modules, where the Shared keyword is not supported.

Thanks, I've committed your change :)

Thanks for the additional change, @Youssef1313. I'll merge your PR now.


tabbar goes up with softkeyboard

hi AdilSoomro , I use your tab widget pretty smooth until I add a search dialog for one activity
, the tabbar was lifted by the softkeyboard , the tabcontent has a listview ,
after I remove the listview , the tabbar was covered by the softkeyboard , its normal . but I really dont understand why a listview make the tabbar goes up , I tried a lot , none of them works
a simple layout  in one of the tab content

<EditText
    android:layout_width="fill_parent"
    android:layout_height="fill_parent" />

<ListView
    android:layout_width="wrap_content"
    android:layout_height="wrap_content" >
</ListView>

its fixed .. my bad

That's good. And just for your information never use layout_height="wrap_content" for a ListView
see this answer's first comment


[to #51174671]feat:FS add OTS onlinestore support

 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.千枫 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


ROX-23952: Add compliance report manager

This PR adds compliance report manager to
-queue requests
-read from queue and submit job for report generation
-fixes bug with stop routine(ROX-24185)
Testing Done
Added unit tests
E2E tests in CI have passed

//test gke-qa-e2e-tests

/test gke-qa-e2e-tests

/retest

/test gke-qa-e2e-tests


[Youtube] unable to extract player URL

Checklist

[ ] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=XYV8Zt2k0RQ']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python 3.10.12 (CPython x86_64 64bit) - Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35 - OpenSSL 3.0.2 15 Mar 2022 - glibc 2.35
[debug] exe versions: ffmpeg 4.4.2, ffprobe 4.4.2, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] XYV8Zt2k0RQ: Downloading webpage
[youtube] XYV8Zt2k0RQ: Downloading API JSON
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
WARNING: unable to extract player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
ERROR: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/home/lj/.local/lib/python3.10/site-packages/youtube_dl/YoutubeDL.py", line 825, in wrapper
    return func(self, *args, **kwargs)
  File "/home/lj/.local/lib/python3.10/site-packages/youtube_dl/YoutubeDL.py", line 846, in __extract_info
    ie_result = ie.extract(url)
  File "/home/lj/.local/lib/python3.10/site-packages/youtube_dl/extractor/common.py", line 535, in extract
    ie_result = self._real_extract(url)
  File "/home/lj/.local/lib/python3.10/site-packages/youtube_dl/extractor/youtube.py", line 2119, in _real_extract
    self._sort_formats(formats)
  File "/home/lj/.local/lib/python3.10/site-packages/youtube_dl/extractor/common.py", line 1375, in _sort_formats
    raise ExtractorError('No video formats found')
youtube_dl.utils.ExtractorError: No video formats found; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

This occurs randomly with all youtube video urls for me. Sometimes the download works, but sometimes the above error happens.

Yes, I get this problem often. However when I get this problem and I terminate the download by CTRL C, remove the partial download and start again, the problem disappears.
Today as soon as I started to download using the youtube link with “-f 22” option, I get the same/similar problem consistently and the problem is repeatable. However the download works fine.
yt-dlp_linux -f 22 https://www.youtube.com/watch?v=0w_ZHcvfm4U
If I use the same youtube link and do not specify any option (without -f 22), I do not get any warning or error. I do not get any error if I use -f 18 option too.
yt-dlp_linux -f 18 https://www.youtube.com/watch?v=0w_ZHcvfm4U
yt-dlp_linux https://www.youtube.com/watch?v=0w_ZHcvfm4U
The above commands works just fine without any warning/s.
This is the output of executing the above command with “-vU” option.
<========================================================>
$ yt-dlp_linux -vU -f 22 https://www.youtube.com/watch?v=0w_ZHcvfm4U
[debug] Command-line config: ['-vU', '-f', '22', 'https://www.youtube.com/watch?v=0w_ZHcvfm4U']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b532a3481] (linux_exe)
[debug] Python 3.10.12 (CPython x86_64 64bit) - Linux-5.4.0-42-generic-x86_64-with-glibc2.31 (OpenSSL 3.1.1 30 May 2023, glibc 2.31)
[debug] exe versions: ffmpeg 4.2.7, ffprobe 4.2.7, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.05.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1855 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 0556fff82db6c942a5dfbb9583e2896013847b28b95186b3800f730a8d5e0c0a
yt-dlp is up to date<EMAIL_ADDRESS>[youtube] Extracting URL: https://www.youtube.com/watch?v=0w_ZHcvfm4U
[youtube] 0w_ZHcvfm4U: Downloading webpage
WARNING: [youtube] unable to extract initial player response; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
[youtube] 0w_ZHcvfm4U: Downloading ios player API JSON
[youtube] 0w_ZHcvfm4U: Downloading android player API JSON
[youtube] 0w_ZHcvfm4U: Downloading iframe API JS
[youtube] 0w_ZHcvfm4U: Downloading player 3cd2d050
[youtube] 0w_ZHcvfm4U: Downloading web player API JSON
[youtube] 0w_ZHcvfm4U: Downloading m3u8 information
WARNING: [youtube] unable to extract yt initial data; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
WARNING: [youtube] Incomplete data received in embedded initial data; re-fetching using API.
[youtube] 0w_ZHcvfm4U: Downloading initial data API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[info] 0w_ZHcvfm4U: Downloading 1 format(s): 22
[debug] Invoking http downloader on "https://rr5---sn-aigzrnss.googlevideo.com/videoplayback?expire=1691884765&ei=fcjXZMzCOO2vmLAPgteD-A0&ip=<IP_ADDRESS>&id=o-ACq51BIshId_IZahA5qFHdd_tTDgmZhoO4koTzChNfvB&itag=22&source=youtube&requiressl=yes&mh=C6&mm=31%2C26&mn=sn-aigzrnss%2Csn-5hne6nsk&ms=au%2Conr&mv=m&mvi=5&pl=22&initcwndbps=1318750&spc=UWF9f9XcPZzOqh1Hd2FlNRC7Le7_TJE&vprv=1&svpuc=1&mime=video%2Fmp4&cnr=14&ratebypass=yes&dur=2092.303&lmt=1691730524679558&mt=1691862796&fvip=4&fexp=24007246%2C24363391&beids=24350018&c=ANDROID&txp=3308224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Ccnr%2Cratebypass%2Cdur%2Clmt&sig=AOq0QJ8wRgIhAMDr8CoGFvuIGQqwN6KKDCR430XGhUSs1ZcKWD-dlOEKAiEAsoy1wj3fcQUvffy2SFpUSTjOHqXB4QhnNJyXwua-bTE%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRgIhAKXk7v38c_xGNHeuGKnUgvIhuuuc0-CvB_stBcU9zws8AiEAjyZJzGXKhz321frhs2hG5rsqIlzfHT1zbXZQAcyICsM%3D"
[download] Destination: Se multiplican los AVISTAMIENTOS DE NAVES NO HUMANAS en el mundo [0w_ZHcvfm4U].mp4
[download] 100% of  384.38MiB in 00:01:32 at 4.17MiB/s

@vince-666

yt-dlp_linux -vU -f 22 Se multiplican los AVISTAMIENTOS DE NAVES NO HUMANAS en el mundo
[debug] Command-line config: ['-vU', '-f', '22', 'https://www.youtube.com/watch?v=0w_ZHcvfm4U']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[b532a3481] (linux_exe)

You are not using youtube-dl... 😉
But yt-dlp is supposed to have fixed this issue in the nightly build. 🙂
You can use yt-dlp_linux --update-to nightly if you have at least yt-dlp 2023.03.03 installed.
yt-dlp_linux -vU -f 22 https://www.youtube.com/watch?v=0w_ZHcvfm4U
[debug] Command-line config: ['-vU', '-f', '22', 'https://www.youtube.com/watch?v=0w_ZHcvfm4U']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[339c339fe] (linux_exe)
[debug] Python 3.10.12 (CPython x86_64 64bit) - Linux-5.4.0-155-generic-x86_64-with-glibc2.31 (OpenSSL 3.1.2 1 Aug 2023, glibc 2.31)
[debug] exe versions: ffmpeg N-111711-gd295b6b693-Nico-20230808 (fdk,setts), ffprobe N-111711-gd295b6b693-Nico-20230808, phantomjs 2.1.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.07.22, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1860 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 2da48d4646431e8a8d2871f180e36dad6a83b0e548d8758023f516918b949aef
yt-dlp is up to date<EMAIL_ADDRESS>[youtube] Extracting URL: https://www.youtube.com/watch?v=0w_ZHcvfm4U
[youtube] 0w_ZHcvfm4U: Downloading webpage
[youtube] 0w_ZHcvfm4U: Downloading ios player API JSON
[youtube] 0w_ZHcvfm4U: Downloading android player API JSON
[youtube] 0w_ZHcvfm4U: Downloading m3u8 information
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[info] 0w_ZHcvfm4U: Downloading 1 format(s): 22
[debug] Invoking http downloader on "https://rr3---sn-5hnednsz.googlevideo.com/videoplayback?expire=1691927652&ei=BHDYZP-7It_Cx_AP1tOVqAo&ip=<IP_ADDRESS>yt-dlp_linux -vU -f 22 https://www.youtube.com/watch?v=0w_ZHcvfm4U
[debug] Command-line config: ['-vU', '-f', '22', 'https://www.youtube.com/watch?v=0w_ZHcvfm4U']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[339c339fe] (linux_exe)
[debug] Python 3.10.12 (CPython x86_64 64bit) - Linux-5.4.0-155-generic-x86_64-with-glibc2.31 (OpenSSL 3.1.2 1 Aug 2023, glibc 2.31)
[debug] exe versions: ffmpeg N-111711-gd295b6b693-Nico-20230808 (fdk,setts), ffprobe N-111711-gd295b6b693-Nico-20230808, phantomjs 2.1.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.18.0, brotli-1.0.9, certifi-2023.07.22, mutagen-1.46.0, sqlite3-2.6.0, websockets-11.0.3
[debug] Proxy map: {}
[debug] Loaded 1860 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 2da48d4646431e8a8d2871f180e36dad6a83b0e548d8758023f516918b949aef
yt-dlp is up to date<EMAIL_ADDRESS>[youtube] Extracting URL: https://www.youtube.com/watch?v=0w_ZHcvfm4U
[youtube] 0w_ZHcvfm4U: Downloading webpage
[youtube] 0w_ZHcvfm4U: Downloading ios player API JSON
[youtube] 0w_ZHcvfm4U: Downloading android player API JSON
[youtube] 0w_ZHcvfm4U: Downloading m3u8 information
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, size, br, asr, vext, aext, hasaud, id
[info] 0w_ZHcvfm4U: Downloading 1 format(s): 22
[debug] Invoking http downloader on "https://rr3---sn-5hnednsz.googlevideo.com/videoplayback?expire=1691927652&ei=BHDYZP-7It_Cx_AP1tOVqAo&ip=<Redacted>&id=o-AM99deF8HbAu2Xtl_jM_zPsEjLOYMUuQ8dvX6hnKYQ8d&itag=22&source=youtube&requiressl=yes&mh=C6&mm=31%2C26&mn=sn-5hnednsz%2Csn-4g5e6nz7&ms=au%2Conr&mv=m&mvi=3&pl=14&initcwndbps=2652500&spc=UWF9f8Hoy1j_u4dM7aCmBKGv1VCdAys&vprv=1&svpuc=1&mime=video%2Fmp4&cnr=14&ratebypass=yes&dur=2092.303&lmt=1691730524679558&mt=1691905757&fvip=1&fexp=24007246%2C51000023&beids=24350018&c=ANDROID&txp=3308224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Ccnr%2Cratebypass%2Cdur%2Clmt&sig=AOq0QJ8wRAIgVIbR3Tvc_fnkDd4uosFL7mLX2kBa25n2Id2BLYWssQMCICKmCOffoj2iRItJgBcnJvdVu_9-MlxHbd3q3w0Vw18W&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRQIgPhkqStNnn2fuvt2phiPNw6iPOh3xpqKkSF9LV6dcvq8CIQCEWfGK2FErmYAzZ5gyC9i5QdNfZ8cCTKrmZvImAFG9Xw%3D%3D"
[download] Destination: Se multiplican los AVISTAMIENTOS DE NAVES NO HUMANAS en el mundo [0w_ZHcvfm4U].mp4
[download] 100% of  384.38MiB in 00:00:37 at 10.27MiB/s
36&id=o-AM99deF8HbAu2Xtl_jM_zPsEjLOYMUuQ8dvX6hnKYQ8d&itag=22&source=youtube&requiressl=yes&mh=C6&mm=31%2C26&mn=sn-5hnednsz%2Csn-4g5e6nz7&ms=au%2Conr&mv=m&mvi=3&pl=14&initcwndbps=2652500&spc=UWF9f8Hoy1j_u4dM7aCmBKGv1VCdAys&vprv=1&svpuc=1&mime=video%2Fmp4&cnr=14&ratebypass=yes&dur=2092.303&lmt=1691730524679558&mt=1691905757&fvip=1&fexp=24007246%2C51000023&beids=24350018&c=ANDROID&txp=3308224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cspc%2Cvprv%2Csvpuc%2Cmime%2Ccnr%2Cratebypass%2Cdur%2Clmt&sig=AOq0QJ8wRAIgVIbR3Tvc_fnkDd4uosFL7mLX2kBa25n2Id2BLYWssQMCICKmCOffoj2iRItJgBcnJvdVu_9-MlxHbd3q3w0Vw18W&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRQIgPhkqStNnn2fuvt2phiPNw6iPOh3xpqKkSF9LV6dcvq8CIQCEWfGK2FErmYAzZ5gyC9i5QdNfZ8cCTKrmZvImAFG9Xw%3D%3D"
[download] Destination: Se multiplican los AVISTAMIENTOS DE NAVES NO HUMANAS en el mundo [0w_ZHcvfm4U].mp4
[download] 100% of  384.38MiB in 00:00:37 at 10.27MiB/s

Also, it is advised to update your ffmpeg (and ffprobe of course).
You can get daily builds here.

The consent issue is #32499.

I can confirm yt-dlp version<EMAIL_ADDRESS>works for me with
python Python 3.11.5 (CPython x86_64 64bit) - macOS-13.4.1-x86_64-i386-64bit (OpenSSL 3.1.2 1 Aug 2023)
ffmpeg ffmpeg 6.0 (setts), ffprobe 6.0, rtmpdump 2.4
macOSX Ventura 13.4.1 (c)
but not
youtube-dl version 2021.12.17.
Both installed with brew

The website for python version is just down


项目启动不起来，缺少依赖

1.主要存在以下几个子项目springboot，springcloud-nacos-seata,springcloud-nacos-eureka
2.能否在springboot-mybatis里面添加fegin替换原生的RestTemplate使用

@cyh03 Please do not import root of seata-samples.You need to select a explicit module to import to your IDE.
For your second question,there is a another sample "springcloud-eureka-feign-mybatis-seata",you can refer to it.


Dart HTTP PUT VS POST in REST requests: The PUT verb does not work

I'm writing a client REST in Flutter/Dart that should manage some data from a REST Server (Java server). The client works fine if compiled for Android , no problem at all. But when it is compiled for Chrome ( Javascript ) there are many problems, like this: when I try to make an HTTP PUT request the client seems to take an unknown error without sending the request to the server.
The strange thing is that this problem is only on the verb PUT, the verb POST works fine (but I stil not tried with PATCH/ DELETE). So it seems a bug on the internal http library when used the verb PUT instead of POST. http: 0.10.0
Here the code:
 void _sendRequest() async {
       try {
          print('Send Request : ');
          //   String url = "http://<IP_ADDRESS>:8080/v2/account";
          String url = "http://localhost:8080/v2/account";
          Map<String, String> headers = new HashMap();
          headers['Accept'] = 'application/json';
          headers['Content-type'] = 'application/json';

          Http.Response response = await Http.put(url,
              headers: headers,
              body: jsonEncode({
              "description": "string",
              "id": 25,
              "name": "11112",
              "password": "seesfs"
           }),
           encoding: Encoding.getByName('utf-8'));

          print('Response status: ${response.statusCode}');
          print('Response body: ${response.body}');
       }catch(error) {
         print("${error?.toString()}");
       }
      }

As you can see, I use the localhost address when I use the web client, and <IP_ADDRESS> when I use the android VM. The same code works when compiled with android and does not when javascript. Any idea? Do you have encountered the same problem?
Here follows the sample test project:
name: accounts_client_http description: A new Flutter project.

version: 1.0.0+1

environment: sdk: ">=2.1.0 <3.0.0"

dependencies: http:^0.12.0+4 flutter: sdk: flutter

dev_dependencies: flutter_test: sdk: flutter

flutter: uses-material-design: true

Here follows the flutter doctor
 flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.14.6, on Linux, locale it_IT.UTF-8)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Community Edition (version 2019.3)
[✓] VS Code (version 1.43.0)
[✓] Connected device (2 available)

• No issues found!

You cannot send requests to a localhost+port from the web, that violates web security policies. Instead just use /v2/account

Hi, the server and the client have not the same origin.
The server is a java based server, thus I think "v2/account/ would  not work.
In any case it is not a security issue.
The server can accept CORS.
Anyway, the error message is :
For a more detailed help message, press "h". To quit, press "q".
Debug service listening on ws://<IP_ADDRESS>:46443/5MG8ohHyem4=
Send Request :
XMLHttpRequest error.
while the android version is ok.
I have no other info about the error.
It seems that the server does not exist, but it is not true.

You'll need to look in the chrome console/network tab for more information then

Thank you @jonahwilliams  !
it hadn't occurred to me!
The problem is now solved!

So, the problem was, again, the CORS mapping!
The problem is solved in this way: in the server side I added the method allowed:
    @Configuration
    public class WebConfig implements WebMvcConfigurer {

        @Override
        public void addCorsMappings(CorsRegistry registry) {
            registry.addMapping("/**").allowedMethods("PUT", "GET", "POST", "PATCH");
        }
    }

Finally, this issue is related to:
cors-issue-occures-only-when-put
The problem is that the Method PUT is not allowed by Access-Control-Allow-Methods in preflight response.
as described here:
cors-issue-occurs-only-when-put
Thank you!


OrtResult: Store scan results "by provenance"

This PR changes OrtResults internal representation to store scan results by provenance, which eliminates redundancies in case multiple packages share the same provenance. It keeps OrtResults API as-is. That is, client code using OrtResult.getScanResults() or OrtResult.getScanResults(id) remains as-is, thereby hiding the complexities of the new internal representation completely. Also, information about the sub-repository structure is now available for all packages in OrtResult.
Breaking change:

"old" ORT files containing a ScannerRun won't de-serialize anymore.
The scanner cannot output package verification codes anymore. This will be fixed again, by computing
these codes on-the-fly from file lists which are not present yet but will be added soon.

Fixes #5950.

@mnonnenmacher I've made a final manual test, I compared scan results of main and this branch and verified that

static HTML reports are identical
output of the list licenses command is identical for some selected package IDs

I've done two scans:

Our orthw example mime types scan
This sub-repositoy case: https://github.com/fviernau/test-data.git


Update types to include status object

As stated in the title.
Better for auto complete and typechecking.

Thanks for this!


[PDF] Show labels outside of graph

Show labels in PDF exports on the outside of the graph for improved readability, as they were before. See #5.

Not quite right lol

PDF IS NO LONGER SUPPORTED HOORAY I DON'T HAVE TO FIGHT THIS DAMN THING ANYMORE


Return empty array if there is no record

WHY
When accessing to GET /users/ endpoint and there is no user record, API server returns null instead of []. This is not an appropriate response.
WHAT
Return [] if there is no records.

LGTM!! Thx!!


Request: Add Alliance Help Time

Hello,
Can you add the "Alliance Help Times" and "Resources Gathered" information to the data collection?
Thank you very much you are doing a great job

Hello,
There is some feedback regarding these specific information. Seems there are people that need to gather that kind of information. They will be added in a future version.
Thank you for supporting the tool.


Start collecting metrics during runtime

It could be all sorts of metrics

JSON RPC request rates, response times, failures
Gateway response times
Block interval
Block import times, verification times, failures
Db read/write counts, delays

see https://prometheus.io/docs/guides/go-application/

and eventually display them in grafana

hey @omerfirmak, would like to contribute to this feature. Can you assign it to me?

https://github.com/NethermindEth/juno/pull/814

Closing this optimistically since we have some metrics now. If we need a tracking issue for specific metrics, we can create one. But I think adding metrics as-needed is probably the best approach.


standalone lib for use with vanilla js in the browser

This PR adjusts the Makefile to export the SonicServer, SonicSocket and SonicCoder under a global Sonicnet object attached to window. This is in addition to the dependency manager hooks which browserify exposes. See details about --standalone flag.
This fixes lib/api-test.html and makes it practical to consume the library in a browser in the absence of a dependency manager.
I wasn't able to find a solution to configure browserify to export the individual objects directly to window without explicitly changing lib/main.js as attempted in @mildmojo's PR.
This changes only the build in lib/. The Makefiles for the demos are left unchanged.

+1

@FalconerTC : Did you manage to make the plugin work ? I'm still having some trouble.

@Astriel I did work for me too. What is the issue you are having?


docs: fix incorrect docker run options in distributed training employment chapter

This fix is patched to distributed training employment chapter.

 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.

@HermitSun

非常感谢你的贡献，很抱歉没有及时review
飞桨快乐开源活动暖冬来袭，https://aistudio.baidu.com/aistudio/activitydetail/1503019026 ，在2023年1月15日之前，完成PR合入，即可收到新年礼物。感兴趣可以报名。


Security concern using v1/chain/get_raw_abi

The SDK uses the chain http request v1/chain/get_raw_abi to get abi bytes for a given Map. This is vulnerable to man-in-the-middle attacks, it would make more sense to provide an empty interface, and have all users use local byte writing from https://github.com/EOSIO/eosio-java-android-abieos-serialization-provider

@samkirton Thanks for your concern. We don't quite understand your statement so we would love to have more detail about it.
BTW:

We provide empty interfaces for serialization provider and ABI Providers  to serialize transaction if you don't want to use get_raw_abi and https://github.com/EOSIO/eosio-java-android-abieos-serialization-provider.
Any network call is vulnerable to main-in-the-middle attacks if client does not have protection technique like Certificate Pinning.
EOSIO also has eosio.assert to prevent men-in-the-middle-attacks but you have to use get_raw_abi.

@samkirton: As @DanteNguyen1008 mentioned, eosio.assert is a proposed solution to these types of attacks. It is a contract that EOSIO chains, such as mainnet, could deploy that would allow developers to include the the hash of the ABI they received in the transaction and the chain would verify that it matches the hash of the one actually on the chain.
In that scenario, if a call to get abis from a chain were MITM attacked and the ABI changed, when the transaction actually gets broadcast to the chain, the chain would reject it.
Just keep in mind that it's a recent proposal and isn't actually deployed to any chain yet, that we're aware of.
More information on the eosio.assert contract can be found here: https://medium.com/eosio/eosio-labs-release-the-assert-manifest-security-model-cdd296a58710

It sounds like eosio.assert is the answer to MITM then, @DanteNguyen1008 certificate pinning isn't an option for fully decentralised wallets or apps that can communicate with any node. I still think it makes more sense to only provide IABIProvider with this repository, and remove ABIProviderImpl, or only implement it with sample apps. In my opinion, a default implementation in a core module should not have any security caveats.

Any network call is vulnerable to main-in-the-middle attacks if client does not have protection technique like Certificate Pinning.
@DanteNguyen1008 Signing locally written abi bytes and posting them with push_transaction is not vulnerable to MITM. However, the response of get_raw_abi can be intercepted, spoofed, unknowingly signed by the device, and pushed to the network (assuming eosio.assert isn't used).

@samkirton We're still trying to understand where you're coming from fully. Are you proposing that (absent eosio.assert) apps should use their own, trusted, ABIs instead of fetching them from a chain? For many apps that only operate with a known subset of contracts, that is probably the safest way to proceed. But for a wallet that might want to sign any transaction a user sends to them, that wouldn't work. New contracts are deployed all the time.
If you truly want to be able to sign transactions for any contract on the chain, you have to fetch the ABIs from somewhere, don't you? Where else would you get those from than an RPC call to a node?
For that app that wants to provide their own ABIs for the sake of security, they can easily instantiate the core EOSIO SDK for Java transaction with their own ABI provider.

FWIW, eosjs also gets ABIs from nodes via RPC, by default. It, too, can be overridden with a dev-provided ABI Provider.

Ahh sorry I was getting confused with abi_json_to_bin


[feat]: Upgrade monaco-editor from 0.46.0 to 0.51.0

See the snyk PR generated - this upgrade breaks something and needs to be fixed post 1.0
https://github.com/axonops/axonops-workbench/pull/483

@millerjp  we shouldn't do that for now, this upgrade has caused all rendered editors to be fully broken, and after many tests, the error is mostly about compatibility issues with Electron, so I recommend sticking with the latest stable version we've found.
We already have upgraded from v0.34.1 to v0.46.0, we'll keep an eye on the upcoming versions and upgrade when it's compatible.

@mhmdkrmabd we will need to have a look at this in 1.1 and assess it there


IPClusterStop fails

The error reported here occurs only sporadically, and is independent of the inputs to the pipeline.  (IOW, given two runs with identical inputs, the error may occur in one, and not in the other.)
At the end of this message I copy the relevant section of the diagnostic output.
Please let me know what other information would be useful to you.
[2016-06-09T00:32Z] node2071: Combining count files into /path-to-basedir/work/sailfish/co\
mbined.sf.
2016-06-08 20:37:13.339 [IPClusterStop] Using existing profile dir: u'/path-to-basedir/wor\
k/log/ipython'
2016-06-08 20:37:13.356 [IPClusterStop] Stopping cluster [pid=13555] with [signal=2]
2016-06-08 20:37:16.601 [IPClusterStop] Using existing profile dir: u'/path-to-basedir/wor\
k/log/ipython'
2016-06-08 20:37:16.613 [IPClusterStop] CRITICAL | Could not read pid file, cluster is pro\
bably not running.
[2016-06-09T00:37Z] node2071: Did not stop IPython cluster correctly
Traceback (most recent call last):
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/ipython.py",\
 line 91, in stop
    ipython_cluster.stop_from_view(view)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/cluster_helper/cluster.py", li\
ne 849, in stop_from_view
    _stop(view.clusterhelper["profile"], view.clusterhelper["cluster_id"])
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/cluster_helper/cluster.py", li\
ne 855, in _stop
    subprocess.check_call(args)
  File "/path-to-bcbio/anaconda/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['/path-to-bcbio/anaconda/bin/python', '-E', '-c', 'import re\
source; cur_proc, max_proc = resource.getrlimit(resource.RLIMIT_NPROC); target_proc = min(\
max_proc, 10240) if max_proc > 0 else 10240; resource.setrlimit(resource.RLIMIT_NPROC, (ma\
x(cur_proc, target_proc), max_proc)); cur_hdls, max_hdls = resource.getrlimit(resource.RLI\
MIT_NOFILE); target_hdls = min(max_hdls, 10240) if max_hdls > 0 else 10240; resource.setrl\
imit(resource.RLIMIT_NOFILE, (max(cur_hdls, target_hdls), max_hdls)); from ipyparallel.app\
s.ipclusterapp import launch_new_instance; launch_new_instance()', 'stop', '--cluster-id=c\
93d0aeb-1705-4518-ab68-70da05ad235d', '--profile-dir=/path-to-basedir/work/log/ipython']' \
returned non-zero exit status 11

0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
2 Engines running
Sending a shutdown signal to the controller and engines.

0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
18 Engines running
Sending a shutdown signal to the controller and engines.

0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
3 Engines running
Sending a shutdown signal to the controller and engines.

0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
0 Engines running
10 Engines running
Sending a shutdown signal to the controller and engines.
Traceback (most recent call last):
  File "/opt/bcbio/centos/bin/bcbio_nextgen.py", line 226, in <module>
    main(**kwargs)
  File "/opt/bcbio/centos/bin/bcbio_nextgen.py", line 43, in main
    run_main(**kwargs)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line \
51, in run_main
    fc_dir, run_info_yaml)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line \
87, in _run_toplevel
    for xs in pipeline(config, run_info_yaml, parallel, dirs, samples):
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/main.py", line \
250, in rnaseqpipeline
    samples = rnaseq.quantitate_expression_parallel(samples, run_parallel)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/rnaseq.py", lin\
e 76, in quantitate_expression_parallel
    samples = sailfish.combine_sailfish(samples)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/bcbio/rnaseq/sailfish.py", lin\
e 192, in combine_sailfish
    df.pivot("id", "sample", "tpm").to_csv(tx_out_file, sep="\t")
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/frame.py", line 13\
43, in to_csv
    formatter.save()
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/format.py", line 1\
550, in save
    self._save()
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/format.py", line 1\
651, in _save
    self._save_chunk(start_i, end_i)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/format.py", line 1\
665, in _save_chunk
    quoting=self.quoting)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/internals.py", lin\
e 1403, in to_native_types
    return formatter.get_result_as_array()
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/format.py", line 2\
170, in get_result_as_array
    formatted_values = format_values_with(float_format)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/format.py", line 2\
156, in format_values_with
    for val in values.ravel()[imask]])
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/format.py", line 2\
107, in base_formatter
    return str(v) if notnull(v) else self.na_rep
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/common.py", line 3\
35, in notnull
    res = isnull(obj)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/common.py", line 1\
76, in isnull
    return _isnull(obj)
  File "/path-to-bcbio/anaconda/lib/python2.7/site-packages/pandas/core/common.py", line 1\
81, in _isnull_new
    return lib.checknull(obj)
KeyboardInterrupt

Hi Gabriel,
The last error looks like the job was manually interrupted via the keyboard. For the first error, it looks like sometimes the job is getting killed before we manually try to shut it down. We could definitely fix that to emit a warning by catching the CalledProcessError exception there.

I pushed a fix to catch the exception and emit a message rather than fail when we try to stop an already-stopped cluster. Thanks!

This job was running in the background as part of a bsub (LSF) submission, so I think it is unlikely that it was killed manually via the keyboard.  (I was the user who submitted the job, and I certainly did not kill it.)  Such jobs are usually killed through the bkill utility, but, again, I did not issue that command.  It is possible that a sysadmin issued a bkill for this job, but, again I find this possibility unlikely, because: 1) whenever such a job gets killed by a sysadmin (as opposed to being killed automatically, e.g. by LSF), I receive an email written by the sysadmin responsible for killing the job explaining his/her rationale; and 2) as I said in my original email, the error occurs sporadically, therefore it would be odd that a sysadmin would decide to kill only some of these jobs and not others, and offer no explanation for doing so.
Therefore, the KeyboardInterrupt message notwithstanding, I very much doubt that the job was killed manually.  That said, I will submit a ticket to the sysadmins inquiring whether this job was indeed killed manually.  I will report the answer I get either way.
My suggestion would be to instrument the code around the place responsible for the diagnostic
CRITICAL | Could not read pid file, cluster is probably not running

as follows:

Put the attempt to read the pid file in a loop for multiple attempts (say 5), with a 1-second sleep between attempts; fail only after all attempts have been exhausted;
Include more information about why it was not possible to read the pid file; in particular, is the file missing altogether, or does it exist but is unreadable?
If possible, confirm that the cluster is not running by some other means.

Also it would be very helpful if the process that is supposed to be killed by IPClusterStop caught the signal that killed it, and logged it before exiting.
Lastly, I would suggest using a special-purpose signal (SIGUSR1 or SIGUSR2) rather than SIGINT to kill the cluster.  The code for the target process would probably need to be instrumented to respond appropriately to such a signal.  If, before exiting, the target process logs the signal (as suggested above), then it becomes straightforward to distinguish between internally- and externally-initiated kills.

Hi Gabriel,
Thanks for the nice suggestions. We're not actually generating the signal to kill the cluster, just calling out to ipython cluster stop which does everything else. The error messages and what not are generated there too-- the IPython folks might have some reasoning about why they chose the signal they sent to kill the cluster, we're just wrapping what they did so your good ideas might be better shifted there. Thanks!


Add linter and plugin.yml

This brings this plugin into the standard line. The one thing is though, the plugin linter refuses to allow this plugin to validate without a usage example in the readme.
Is it possible to use this as an actual plugin these days? Or is still just hooks that need to be sourced from an agent? If so, maybe we shouldn't call it a plugin?

Technically you could use it as a plugin @toolmantim, but given most folks need it before checkout (to get SCM credentials to do the actual checkout), I'm not sure how much use it is.

I think it would be fine to add back an example, with the caveat around chicken and egg:
"If you already have credentials for source code checkout in place, you can use s3-secrets as a normal plugin to provide extra env or credentials to a job".

Okay cool, we can probably figure out the wording.
Environment hooks aren’t supported in plugins tho, so perhaps we’d need to add a new hook to this? I think the pre-exit will Just Work tho.

Oh yeah, good point. In that case it totally won't work at all. Maybe we should make this an -example rather than a -plugin?

Hrmm, to get this up to scratch as a plugin I reckon we'd need to:

Move a bunch of code from environment to pre-command
Don't run all the git ssh-key stuff in the pre-command, only the build-specific secrets stuff
Fix up the readme docs for the pipeline case
Rework the readme to make it clearer how to use it in both circumstances (on an agent, vs in a pipeline)

I kinda like this being a patient zero for an "agent plugin". Maybe that's a separate concept altogether? s3-secrets-buildkite-agent-plugin vs s3-secrets-buildkite-plugin?

I'm only using it in the Elastic CI Stack.

Thanks @jeremiahsnapp!
@lox I think if nobody is using this outside of Elastic CI Stack, perhaps we move it to a hooks example, or back into the elastic stack? And then when/if we extract it out into a proper plugin, we bring this back to life?

Yeah, I think I agree @toolmantim. The one piece of info that is relevant is that several teams have used it to build a windows elastic stack, which is exactly why I extracted it. I'm loath to put it in an example repo, but maybe buildkite/s3-secrets-hooks or something?

Hrmm, in that case why not make it buildkite/elastic-ci-stack-s3-secrets-hooks?

That way, it's not an example, but just an actual thing that's been extracted out and useful in and of itself. Just not as a plugin.

I wonder what it will break if I transfer this repo?

I think GitHub should all the right git clone redirects.

Okay, I've moved this over! Elastic CI Stack PR is open here: buildkite/elastic-ci-stack-for-aws#414

Thanks @toolmantim, I'll make the updates to elastic stack.


yarn start command not working

The following command gives an  "error Command failed with exit code 127." Could you please help on how to resolve the issue. Thank you

Please attach screenshot of cmd/terminal.

![Uploading Screenshot 2020-02-25 at 3.31.39 PM.png…]()


tf.norm not accurate in Tensorflow 2.7.0

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: no
TensorFlow installed from (source or binary): pypl
TensorFlow version (use command below): v2.7.0
Python version: 3.8.10
Bazel version (if compiling from source): not required
GCC/Compiler version (if compiling from source): not required
CUDA/cuDNN version: 11.0 (from docker image of TF 2.7.0)
GPU model and memory: 2080ti

Describe the current behavior
We are using tf.norm to make a vector be unit vector.
This is quite simple and we use the following code in TF 2.2.0.
vec = np.array([4.6463e-03, -4.8086258e+01], dtype="float32")
amount = tf.norm(vec, ord=2, axis=-1)

The amount is <tf.Tensor: shape=(), dtype=float32, numpy=48.086258> in TF 2.2.0.
Thus the normalizing is correct and we get an unit vector by vec / amount.
But in TF 2.7.0, the amount will be <tf.Tensor: shape=(), dtype=float32, numpy=48.086254>, which is incorrect.
We also found that this situation only happened when the tensor is computed on GPU.
In other word, if we set os.environ["CUDA_VISIBLE_DEVICES"] = "-1", we could get correct value in TF 2.7.
Describe the expected behavior
The norm value should be <tf.Tensor: shape=(), dtype=float32, numpy=48.086258> in both CPU or GPU.

@Janus-Shiau ,
In order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here.

I think using the code block above can reproduce the problem.
But I can also provide more if you need.
import numpy as np
import tensorflow as tf

if not tf.__version__ == "2.7.0" or not tf.test.is_gpu_available():
    return

vec = np.array([4.6463e-03, -4.8086258e+01], dtype="float32")
amount = tf.norm(vec, ord=2, axis=-1)

print(amount)

In my case, this is enough to reproduce the issue.

@Janus-Shiau ,
I was facing different error while trying to execute the mentioned code.Please find the gist of it here.

@tilakrayal delete the if and the return and you see the problem.

Thank you @bersbersbers. Your example is quite clear!
The if statement is aim to make sure the TF version is correct and GPUs are utilized.

This problem has two parts, offering two workarounds:

Part of the problem is that GPU TensorFlow is computing, by default, using float32, while CPU TensorFlow is doing float64 computations (as do numpy and Python's math module):
import math
import numpy as np
import tensorflow as tf

x = 99.0
a = np.array(x)
a32 = np.array(x, dtype=np.float32)
a64 = np.array(x, dtype=np.float64)
t = tf.constant(x)
t32 = tf.constant(x, dtype=tf.float32)
t64 = tf.constant(x, dtype=tf.float64)

print(np.sqrt(a32))
print(tf.sqrt(t).numpy())
print(tf.sqrt(t32).numpy())

print(math.sqrt(x))
print(np.sqrt(a))
print(np.sqrt(a64))
print(tf.sqrt(t64).numpy())

Output:
9.949874
9.949874
9.949874
9.9498743710662
9.9498743710662
9.9498743710662
9.9498743710662

You see that a behaves like a64, while t behaves like t32. You can avoid the problem using float64.

But this is not the whole story. Yes, it's similar for tf.norm:
import numpy as np
import tensorflow as tf

x = 48.086258
a = np.array(x)
a32 = np.array(x, dtype=np.float32)
a64 = np.array(x, dtype=np.float64)
t = tf.constant(x)
t32 = tf.constant(x, dtype=tf.float32)
t64 = tf.constant(x, dtype=tf.float64)

print(tf.norm(t).numpy())
print(tf.norm(t32).numpy())

print(np.linalg.norm(a))
print(np.linalg.norm(a32))
print(np.linalg.norm(a64))
print(tf.norm(t64).numpy())

Output:
48.086254
48.086254
48.086258
48.086258
48.086258
48.086258

But you also see that this time, numpy computes correctly in float32. Interestingly, the same is true in TF using the alternative code commented out here:
https://github.com/tensorflow/tensorflow/blob/c256c071bb26e1e13b4666d1b3e229e110bc914a/tensorflow/python/ops/linalg_ops.py#L759-L763
import tensorflow as tf
from tensorflow.python.ops import math_ops

x = 48.086258
t32 = tf.constant(x, dtype=tf.float32)

print(math_ops.sqrt(math_ops.reduce_sum(t32 * math_ops.conj(t32))).numpy())
print(math_ops.reduce_euclidean_norm(t32).numpy())

Output:
48.086254
48.086258

So another workaround is to use math_ops.reduce_euclidean_norm, and you can stick to your float32 data type.

I guess the TF team should switch to math_ops.reduce_euclidean_norm according to the TODO comment.

@jvishnuvardhan ,
I was able to reproduce the issue in tf v2.5,v2.7 and nightly.Please find the gist here.

@bersbersbers @Janus-Shiau Looks like this was resolved. Can you please check this gist. Please let me know if i am missing anything. Thanks!

@bersbersbers @Janus-Shiau Disregard my last comment. I ran it on CPU which works well as you mentioned earlier.
This is throwing wrong results on GPU. Thanks

Excuse my ignorance, but it looks to me like https://github.com/tensorflow/tensorflow/commit/18937a7232d8c66559b44afb99da2743f907da5a exactly reverted https://github.com/tensorflow/tensorflow/commit/d5a0174ddd279c1dd8ee434aa05edea4e0afaaf0. Should this issue be re-opened?

Was able to reproduce the issue with tf-nightly-2.11.0-dev20220829. Please find the attached gist here. Thank you!

@bersbersbers yes, it was reverted.
The issue is that the change to always use the EuclideanNorm op from within tf.norm breaks many workflows that rely on the existing norm function, since it introduces a new op that isn't supported on all devices.
The only workable solution is that if you need the higher accuracy, then use tf.math.reduce_euclidean_norm directly.
Internally, it uses a more stable way of computing the norm that less prone to overflow and precision issues.


Create issue templates

Creating a bug-report template. This is just a simple modification of the default template.

I'm actually okay with the open format for our issues this past year. I think at this scale, I prefer it over this boilerplate. Revisit  next year?

Please see previous comment. @GabeDeBacker feel free to reopen.


Refactor power chassis alert with new event format

@iceiilin @pengz1 @anhou

:+1:

BUILD on-tasks #1933 : FAILURE

** BUILD build-config-setup  #1117: SUCCESS

** BUILD unit-tests  #11259: SUCCESS

** BUILD on-taskgraph #1992: FAILURE

** BUILD build-config-setup  #1118: SUCCESS
** BUILD unit-tests  #11260: FAILURE


Cursor doesn't skip to the end of input box when all is selected and left arrow clicked.

Godot version:
3.2 alpha build 2
OS/device including version:
Windows 10 64 bit
Issue description:
When you click on any input box, all is selected. When all is selected and arrow key is pressed, it deselects (which is correct behaviour) but the cursor doesn't jump to end of input box.
Example of correct behaviour in Firefox: https://www.youtube.com/watch?v=8Si9YmlCUsM&feature=youtu.be
Exapmle of incorrect behaviour in Godot: https://youtu.be/lzOm7-Uu0j8
Steps to reproduce:
Make the cursor skip to the end when all is selected

To do what you want you must press Control + Left or Right, on Mac it's probably Command instead of Control.
It might make sense to change the behaviour but I think this is not the only thing that needs to be changed.
For example on Firefox if you select the whole text with Control+A and then press Shift+Right nothing happens, but if you press Shift+Left, you deselect the rightmost selected character, the same happens if you select by dragging over the text from left to right.
But this changes if you select by draggin from right to left, in this case Shift+Left does nothing, but Shift+Right deselect the leftmost selected character.
This probably needs to be discussed before being implemented.

Can't reproduce in current master - solved?

It's reproducible in 3.2.3-stable, but seems fixed in master indeed, so closing.


request review of metadata

Please review and comment on the metadata implementation here:
https://github.com/os-climate/wri-gppd-ingestion-pipeline/blob/master/notebooks/WRI-gppd-ingest.ipynb
Relates to: https://github.com/os-climate/os_c_data_commons/issues/48

I have now moved the metadata implementation to DBT pipelines - as OpenMetadata is able to ingest metadata from catalog.json which is generated and versioned when generating DBT documentation

I just reviewed the notebook and see that it is unchanged since October 2021.  It needs a complete overhaul in terms of credentials.env variable names, use of osc-ingest-tools, among other things.  What's the best way to both true up this notebook to modern standards and true up to new DBT+OpenMetadata?

I suggest deprecating the older notebook as I am essentially rebuilding the pipeline from scatch. But keep it around so you can have a look when I complete the end-to-end flow, as you may want to make some functional changes (note: most of the data processing that was in the notebook should be in DBT now).


feat: acceptance test for basic usability of integrations

This can be used for acceptance tests for new environments and auth types, verification of connection UIs and flows, misc Python bug reproductions, etc.
It is meant to be simpler and quicker than running all the samples one after the other - a single deployment, trivial API calls without runtime parameters, and no extra logic in triggers. In other words, is checks that the rest of the projects are ready to be tested.
It's not meant to offer the same functionality coverage or educational value as other projects in this repo.
FYI, some functionalities are currently broken in the cloud platform, but are working in on-prem servers (e.g. #774 and #779 not deployed in prod, and ENG-1680).

Replaced by https://github.com/autokitteh/autokitteh/pull/784


Husky set up

husky set up for pre commit check for linting and cargo fmt done

new branch created to clean up the messy commits, and git issues.


refactor Avatar component

What it does, and why

Add a thorough explanation of what the code in this PR does in this section.

Checklist

Please go through following checklist before requesting review and fix issues listed there. If your code touches the files with the below in question, please address them.

Workflow

[ ] Are you writing documentation/comments for the bits of code with complex changes?
[ ] Are you writing tests (Storybook/Unit testing)

Jira Tickets

If this PR implements changes related to one or more Jira tickets please add them here:

UI Changes

If this PR introduce some interaction or animation change please also add GIF with how it behaves. Don't forget that this change should be possible to simulate in storybook.
You can use this tool to record your screen and convert it to a GIF.

 Here is an overview of what got changed by this pull request:

Clones added
============
- packages/orcs-design-system/lib/components/Avatar/index.js  1

See the complete overview on Codacy


Automatically add enable/disable app as attribute

Closing this since we added a better way to enable and disable apps


Add MacOS AllControls sample

This is great. We can merge once CI is green
As an aside, we should do some work to to get these looking "beautiful" by default on both mobile and MacOS.

You're missing a trailing slash on a directory name:
build_output/AllControls.MacOS.exe
build_outputAllControls.MacOS.exe

in

Copying file from "obj/Debug/AllControls.MacOS.exe" to "/Users/travis/build/fsprojects/Elmish.XamarinForms/build_output/AllControls.MacOS.exe".

MMP : error MM0007: The root assembly '/Users/travis/build/fsprojects/Elmish.XamarinForms/build_outputAllControls.MacOS.exe' does not exist [/Users/travis/build/fsprojects/Elmish.XamarinForms/Samples/AllControls/AllControls.MacOS/AllControls.MacOS.fsproj]

@nosami I notice the image isn't working, perhaps you didn't give it time to download http://upload.wikimedia.org/wikipedia/commons/thumb/f/fc/Papio_anubis_(Serengeti%2C_2009).jpg/200px-Papio_anubis_(Serengeti%2C_2009).jpg

You're missing a trailing slash on a directory name:

Not sure how that path is being generated, I don't think it is something I have done.

@nosami I notice the image isn't working in the screenshot, though perhaps you didn't give it time to download http://upload.wikimedia.org/wikipedia/commons/thumb/f/fc/Papio_anubis_(Serengeti%2C_2009).jpg/200px-Papio_anubis_(Serengeti%2C_2009).jpg

I'm not sure what is going wrong there. I just tried it again and left it for a minute. No joy! I'll look into it.


[BUG] Memory growth when using PyGWalker with Streamlit

Describe the bug
I observe RAM growth when using PyGWalker with Streamlit framework. The RAM usage constantly grow on page reload (on every app run). When using Streamlit without PyGWalker, RAM usage remain constant (flat, does not grow).  It seems like memory is never released, this was observed indirectly (we tracked growth locally, see reproduction below, but we also observe same issue in Azure web app and RAM usage never decline).
To Reproduce
We tracked down the issue with isolated Streamlit app with PyGwalker and memory profile (run with python -m streamlit run app.py):
# app.py
import numpy as np
np.random.seed(seed=1)
import pandas as pd
from memory_profiler import profile
from pygwalker.api.streamlit import StreamlitRenderer

@profile
def app():
    # Create random dataframe
    df = pd.DataFrame(np.random.randint(0, 100, size=(100, 4)), columns=list("ABCD"))
    render = StreamlitRenderer(df)
    render.explorer()
app()

Observed output for a few consequent reloads from browser (press R, rerun):
Line #    Mem usage    Increment  Occurrences   Line Contents
    13    302.6 MiB     23.3 MiB           1       render.explorer()
    13    315.4 MiB     23.3 MiB           1       render.explorer()
    13    325.8 MiB     23.3 MiB           1       render.explorer()

Expected behavior
RAM usage to remain at constant level between app reruns.
Screenshots
On screenshot you may observe a user activity peaks (cause CPU usage) and growing RAM usage (memory set).

On this screenshot a debug app memory profiling is displayed.

Versions
streamlit 1.38.0
pygwalker <IP_ADDRESS>
memory_profiler (latest)
python 3.9.10
browser: chrome 128.0.6613.138 (Official Build) (64-bit)
Tested locally on Windows 11
Thanks for support!

Hi @ChrnyaevEK , Thanks for your feedback.
Using pygwalker latest version, and try to cache StreamlitRenderer, it may avoid memory growth.
from pygwalker.api.streamlit import StreamlitRenderer
import pandas as pd
import streamlit as st

@st.cache_resource
def get_pyg_renderer() -> "StreamlitRenderer":
    df = pd.read_csv("xxx")
    return StreamlitRenderer(df)

renderer = get_pyg_renderer()

renderer.explorer()

There are several reasons why pygwalker memory grows:

StreamlitRenderer(df) will parse the dataframe and infer the data type.
render.explorer() It will render the ui using html iframe(<IP_ADDRESS> version has used the streamlit custom component to render pygwalker ui. The streamlit component has optimized this part of the memory overhead)
For data calculation communication, the calculated data needs to complete http communication through the customized tornado endponit.(This will also be optimized in future versions)

In the next period of time, pygwalker will optimize the user experience of the streamlit component. Thank you again for your feedback.


Don't call cloud api when creating Container()

Avoid unnecessary api calls: https://github.com/appscode/stow/blob/master/google/location.go#L81

I think this is not that big of a deal. This is done once for a Bucket.