Does not handle restarting of nrpe on changes

If I deploy new checks using this role, those new checks won't be available through the nrpe daemon initially because this role doesn't handle refreshing that daemon. I could also call this role before calling the main nrpe role, but then this role would fail if the correct directories are not yet in place, right?
Things do work correctly on the first go if you first call the nrpe role and then this role, as then the handler for restarting nrpe will be run after this role has deployed plugins. But when you make subsequent changes that only affect plugins deployed using this role then this issue happens.
I'm not sure what the best way to handle this would be. The easiest way would be to add a handler in this role as well for refreshing nrpe, but then you would have that handler in two places. Another option might be to combine the two roles?

I think it would be quite nice to just define https://github.com/CSC-IT-Center-for-Science/ansible-role-nrpe  as a dependency in the meta file. Then it will get executed before this nrpe-plugins role. I haven't done extensive testing with those dependencies but it works with 1.9.4 and I'd probably want to define it like in here: https://github.com/CSC-IT-Center-for-Science/ansible-role-slurm/blob/master/meta/main.yml

Setting the dependency is fine, but the issue I was trying to describe still remains. It has to do with how the two roles work together. Even if you use both, you can still end up in a situation where the checks are not properly updated, because this role does not have a handler for the nrpe daemon.
Consider this scenario:

Everything is initially configured correctly with monitoring using the main nrpe role and nrpe-plugins
You add an extra check using nrpe-plugins, but make no other changes to your code

What you would expect to happen is that the new check would be usable immediately after the Ansible run, but it won't be. You have to restart the nrpe daemon for the changes to take place, because the change made only in the config of nrpe-plugins won't be picked up by the handler in the main nrpe role.

The way the roles are made right now it's not enough to only install an extra plugin in nrpe-plugins
This role just installs the check via get_url, pip or copy.
One still has to add it to the nagios_plugins list for the nrpe role to configure nrpe to use it (and configuring that will restart nrpe/opsview).
The nrpe service is not restarted when a check is updated. But that seems to not needed.
I don't think we need to change anything here.
Maybe documentation could be updated to be clearer on this?
https://github.com/CSC-IT-Center-for-Science/ansible-role-nrpe-plugins/blob/master/README.md


rails_upgrader go should ask before overwriting

Before modifying each model/controller, there should be a y/n prompt that asks for your permission to overwrite each file.
There should also be a rails_upgrader go -y option which overwrites every file, automatically answering y to every prompt (without showing the prompt, exactly as it works now).

Hey @kaysiz, can you take a look a this, please?


Need to implement a L2 Pooling layer

In PyTorch, there is LPPool2d.
I think simply implement L2 Pooling is enough for moust use cases.

I think if we write L2 Pooling then LP will be just a few steps away so might as well. We won't need to handle P=infinity because we already have max pooling


feat: buy button in the header for mobile

Description

Displays a "Buy" button in the Header for mobile/low resolution, available on all pages.

Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #3491
Risk

Testing
On low width viewports/mobile verify the presence and function of the new Buy button.

Engineering
☝

Operations
☝

Screenshots (if applicable)
English

French (active state while on the Buy page)

@reallybeard @firebomb1

can you coordinate on this plz?

@reallybeard @firebomb1

can you coordinate on this plz?

Guess we gotta match the same button size as the wherever thing --- or we make the wherever one small.

Guess we gotta match the same button size as the wherever thing --- or we make the wherever one small.

I'm fine with a larger Buy button personally, I only made it small to match your mockup but didn't realize there was a new button next to it now :D

In English it's ok, it's a tighter fit in French (as usual... 🙄). For even narrower width the logo gets pushed to the left with no overlap (unless it's an unrealistically small width).


Very Slow After Long Time Used on Highend computer

Issue Type: Bug
In fact, this happen in my highend computer and laptop.
maybe this happens in other computers.
after using vs code long time (maybe 20~40 hours ? including power saving mode of computer), it become very slow. very.. (very many lags)
after restart Vs code, the problem solved.
but I don't want it happen.
VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:23:51.859Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz (4 x 2304)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.87GB (3.04GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

snapshot-tools
asv
0.2.2

npm-intellisense
chr
1.3.0

vscode-eslint
dba
1.6.1

es7-react-js-snippets
dsz
1.8.7

vscode-wasm
dts
1.2.1

gc-excelviewer
Gra
2.1.26

r
Iku
1.0.0

graphql-for-vscode
kum
1.12.1

vscode-language-pack-ko
MS-
1.28.2

python
ms-
2018.9.1

polacode
pnp
0.2.2

rust
rus
0.4.10

Please see https://github.com/Microsoft/vscode/wiki/Performance-Issues for creating actionable performance problem issues.


What is the plan for commands beyond cite?

Just wondering, how are you planning to support citation commands beyond the default \cite?
I see your reasonable discussion of this in the manual, but there is still room for additional options.
For example, citet/textcite can be supported now, and is in some other implementations (pandoc, org, etc). To do it conceptually is basically "author + suppress author".
The support planned for 1.1 is really so that one can define different author rendering in text, and in parentheses (as is required in APA actually).
But FWIW, citeproc-el, which is used in the new org-mode csl processor, has added some additional rendering options.
https://github.com/andras-simonyi/citeproc-el
After going through this with the org-mode citation design, I do think commands are a bit of a rabbit hole, however; it's hard to know what the right balance is.
Conceptually, CSL is designed around an approach similar to the biblatex high-level ("style-independent") commands, like autocite. Perhaps one option is to take a handful of biblatex (and/or natbib; not sure) commands that fit with CSL's design? Maybe textcite, fullcite, nocite to start?
PS - does this mean you've looked at CSL 1.1? Do you see any problem with supporting it in the future?

I've added the narrative \textcite and \citet commands as well as the author-only \citeauthor. It takes quite some time because I have to rewrite a large part of the Lua engine to support special citation forms (author-only, suppress-author and composite).

Conceptually, CSL is designed around an approach similar to the biblatex high-level ("style-independent") commands, like autocite. Perhaps one option is to take a handful of biblatex (and/or natbib; not sure) commands that fit with CSL's design? Maybe textcite, fullcite, nocite to start?

It's true that biblatex provides a lot more citation commands but I doubt the other ones are as useful as \textcite and \citeauthor (Perhaps \footcite is also useful). I'll add whichever is really needed.

Is there any current support for a \fullcite equivalent? I don't see anything located within the documentation. If I misunderstood the documentation, I apologize.

The \fullcite isn't provided yet. What is the usage scenario of this command?

Is there any current support for a \fullcite equivalent? I don't see anything located within the documentation. If I misunderstood the documentation, I apologize.

The \fullcite isn't provided yet. What is the usage scenario of this command?

A CV.

Thank you for your response. In my case I need to create an annotated bibliography using APA 7 formatting. It requires me to use the \fullcite command.


Allow gateway transit and Use remote gateways in globally peered virtual networks

In the Create a peering section, under Allow gateway transit and Use remote gateways, it says "You cannot enable this option if you're peering virtual networks in different regions"; however, in the Requirements and Constraints section, it says "You can use remote gateways or allow gateway transit in globally peered virtual networks and locally peered virtual networks."
Can you kindly help confirm whether you can enable gateway transit and use of remote gateways if you're peering virtual networks in different regions? Thank you in advance!

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

ID: 4e439c62-035c-47f0-a03d-c70e66f2887b
Version Independent ID: d745a499-f6bf-ca46-f378-c64535df626f
Content: Create, change, or delete an Azure virtual network peering
Content Source: articles/virtual-network/virtual-network-manage-peering.md
Service: virtual-network
GitHub Login: @KumudD
Microsoft Alias: anavin

@maryannlim the "Use Remote Gateways" option will work in different regions, unless you are peering with a classic Virtual Network.

Got it, thank you for the quick confirmation, @TravisCragg-MSFT!


Query :: repeated joins between Includes and nav props

When we apply Include and also access navigation property on the entity that was included, we generate JOINs for to the same table twice. We could potentially be smart about it and only do it once.
e.g.
ctx.As.Include(a => a.B).Where(a => a.B.Name == "Foo")

@maumar @anpete I see we have some possible overlap or duplication between this bug, #4900, #3816 and #3419.
Could you please figure out if we can consolidate into a smaller set of orthogonal bugs without loosing information?

@maumar - Can you do a quick check if this is fixed after new include compiler ?

Yes, that is indeed fixed, closing


PHP Beautification not working for PHP-CS-Fixer

Description
I set the paths to the executables but when I click for beautification "Beautification in Progress" message shows for sec and then nothing happens. No errors are shown (using Windows).
Debug
Here is a link to the debug.md Gist: https://gist.github.com/asafm7/2348641507843ab1113ce19501f51e85

Thanks, I think i tried everything.
I get no errors but no results.
Actually the only thing that does happen is an empty line added in the end of the file...
It seems like everything is running but no roles applied...
Is there anything else I can do?
Thanks,
Asaf

@issue-manager duplicates?

Please rename your Gist to debug.md not debug,md (note the period instead of comma) 😛. This will allow us to use the Markdown links.
In the logs I see the following:
2017-05-14T10:51:10.299Z - debug: [beautifiers\beautifier.coffee] spawn C:\php\php.EXE 0=C:\xampp-5.6.30\php\php-cs-fixer, 1=fix, 2=--allow-risky=no, 3=--using-cache=no, 4=C:\Users\asafm\AppData\Local\Temp\temp117414-5980-32bpg0.hvzfqadcxr
2017-05-14T10:51:10.460Z - debug: [beautifiers\beautifier.coffee] spawn done 1  Could not open input file: C:\xampp-5.6.30\php\php-cs-fixer

2017-05-14T10:51:10.461Z - verbose: [beautifiers\beautifier.coffee] spawn result 1 Could not open input file: C:\xampp-5.6.30\php\php-cs-fixer

Can you confirm C:\xampp-5.6.30\php\php-cs-fixer is:

the correct path (i.e. exists)
a PHP file

Hi,
Here is a new debug file:
https://gist.github.com/asafm7/c0c1a6c41c73684a108cc9d96aab16d5
The path to the php-cs-fixer is:
C:\Users\asafm\AppData\Roaming\Composer\vendor\bin\php-cs-fixer.phar
Thanks again,
Asaf

I see in your new debug file you have changed the configured php-cs-fixer path: https://github.com/Glavin001/atom-beautify/blob/master/docs/options.md#php-cs-fixer-path
In the logs it shows:
2017-05-15T06:36:51.581Z - debug: [beautifiers\beautifier.coffee] spawn C:\php\php.EXE 0=C:\Users\asafm\AppData\Roaming\Composer\vendor\bin\php-cs-fixer.phar, 1=fix, 2=--allow-risky=no, 3=--using-cache=no, 4=C:\Users\asafm\AppData\Local\Temp\temp117415-6564-1mvn53.50fuyds4i
2017-05-15T06:36:52.335Z - debug: [beautifiers\beautifier.coffee] spawn done 0 Loaded config default.

Fixed all files in 0.259 seconds, 5.250 MB memory used

2017-05-15T06:36:52.336Z - verbose: [beautifiers\beautifier.coffee] spawn result 0
Fixed all files in 0.259 seconds, 5.250 MB memory used
 Loaded config default.

It appears to be working as expected now, from Atom-Beautify's perspective, as the message shown -- Fixed all files in 0.259 seconds, 5.250 MB memory used  -- is generated by PHP-CS-Fixer.
However, it looks like the indentation is still off. This would suggest an issue with PHP-CS-Fixer's handling of your file. Have you tried using PHP-CS-Fixer manually via CLI? See https://github.com/FriendsOfPHP/PHP-CS-Fixer#usage for details.

I did. It outputs:
$ php php-cs-fixer.phar fix test.php
Loaded config default.

Fixed all files in 0.251 seconds, 5.250 MB memory used

But again, no beautification is taking place...
Any ideas?
Does all beautification rules are within the php-cs-fixer.phar? Can you send me a php-cs-fixer.phar file known to work?

But again, no beautification is taking place...

Then this must be a bug with PHP-CS-Fixer itself. I recommend you create an issue over at https://github.com/FriendsOfPHP/PHP-CS-Fixer to ask for help.

When I run: php-cs-fixer fix <filepath>.php on any CLI in my Windows, everything works fine, but inside Atom, using atom-beautify, nothing happens.

Hello, I just did a test and the result was same as @odahcam 's observation. It would be good if you can check again. Thank you so much!

Win10x64.
The fix for me was to simply rename the downloaded php-cs-fixer to php-cs-fixer.phar and update the path in Atom accordingly.


Need full screen width option

Items are truncated at half the screen width:
This gives you lines like:
Station Selector:

   http://streams.kut.org/4430_192.mp3?
   http://streams.kut.org/4428_192.mp3?
=> http://stream1.early1900s.org:8080

I'd rather see:
Station Selector:

=> http://streams.kut.org/4430_192.mp3?aw_0_1st.playerid=tmx-free
   http://streams.kut.org/4428_192.mp3?aw_0_1st.playerid=kutx-free
   http://stream1.early1900s.org:8080

Maybe an option to control max_x and max_y?

Hi, after #128, the screen text should not be trancated now. And that change is contained in v2.4.0b1. Thank you for report!


Firefox version 2.2.0 on addons.mozilla.org is broken

CSS styles are not loaded when I install https://addons.mozilla.org/en-US/firefox/addon/keyword-blocker/ in Firefox. This seems to be due to the bug described in README: "Due to a bug in html-webpack-plugin injected paths to the stylesheets will have a backslash instead to a forward slash. This will lead to problems when running the plugin on firefox."
Current version uploaded to addons.mozilla.org is not usable.

Thanks for submitting this issue. I'll make a new build and fix this tonight (together with your link fix pr thank you!).

I've submitted v2.2.1 for review and I hope this fixes the problems on firefox!

Just updated. It is fixed, thanks!


Menu cut off on scrolling (iOS)

While having the menu open and scrolling down the page, the menu overlay is rendered too short when browser navigation bars shrink (See image below).
Tested on iOS 10 Safari (and Chrome)

thanks, would be nice to receive a pull request

It seems like Safari is not rendering the parts off the element which is fix positioned.
Tested my fix in Xcode Beta with iOS 10 SDK. After testing in Xcode Stable with iOS SDK and on iPhone I get the same behaviour as @marionebl.

@Dangoo Are you still on this?

Yepp, but will take some time.

I've tested this on IOS 10.3 on both Safari and Chrome. I think they might have fixed this behavior as the navigation will just snap back to the desired height right after the scrolling stops. Or is this the same behavior as before?


Build step is not copying fields.json file to the generated build directory

@helio-frota exactly, this is what's going wrong with it right now.
My suggestion is to go with option no.3
Solution 3: Copy json files separately (recommended)

You can add a cpy-cli or copyfiles step to your build process to copy all .json files into the dist/ folder, after tsc has finished.

This assumes you do your builds with npm run build or something similar.

For example:

$ npm install --save-dev cpy-cli

// To copy just the json files, add this to package.json
"postbuild": "cpy --cwd=src --parents '**/*.json' ../dist/",

// Or to copy everything except TypeScript files
"postbuild": "cpy --cwd=src --parents '**/*' '!**/*.ts' ../dist/",
Now npm run build should run tsc, and afterwards run cpy.

Disadvantages: It requires an extra devDependency. And you must make this part of your build process.

That being said I do think moving the .json file(s) into a separate directory is a good idea. (away from the source code)

That being said I do think moving the .json file(s) into a separate directory is a good idea. (away from the source code)

makes sense since we are going to copy, it is not required to live in src/util/

Cool, so I'll assign to my self

Cool, I'll assign it to myself


Unclean Pull request flow

The pull request is being done incorrectly

Hi, what do you mean with that?

Read the comments that had been added by the team in Git before doing a pull request.


Is there a way to use v2 the same way as v1?

I'm struggling with propagating headers to subgraphs in v2. Previously, I used graphqlDataSource.Configuration with headers passed to graphqlDataSource.FetchConfiguration.
Now, we want to enable subscriptions and build a gateway based on the example folder. However, graphqlDataSource.Configuration has been replaced with engine.SubgraphConfiguration, where I no longer have control over headers.
After a few hours of debugging, I discovered that FederationEngineConfigFactory.Compose() sets custom header propagation (CustomGraphql.Fetch.Header) as an empty value.
Question: Is there any way to configure header propagation in v2?

Hi @Aenimus,
Thank you for your suggestion. However, Cosmo Router doesn't quite fit our needs since we can't use it just as a handler—it requires running as a full server. Additionally, we're encountering issues configuring subgraphs without a control plane. We prefer to use graphql-go-tools directly.
Is there a way to configure header propagation in v2 using graphql-go-tools?
Thanks for your help.


growing memory in netCDF library?

@epourmal reported that netCDF has some memory problem, where memory use grows over time.
I don't want to forget to look into this important issue. Elena, can you provide any more info?

This is described in HDF5 Forum at https://forum.hdfgroup.org/t/investigating-memory-growth-with-hdf5-netcdf-4/6187

Down toward the bottom is the following result:

close and reopen dataset instead of keeping them all open – This had a large affect. The peak for the “smaller” model was dropped from 114 MiB down to 31 MiB (83 MiB decrease). In this case, the execution time increased by about 1.5X. However, on a larger model, the peak dropped from 172 MiB down to 99 MiB (73 MiB decrease) and the execution time decreased by about 10%.

This seems to be a good option to investigate with the NetCDF 4 developers. My current hack is just to close and immediately reopen right after the H5Dwrite call which probably isn’t the best implementation, but does show the different behavior.

I haven’t tried any of the metadata cache options yet.

Here is a patch showing the hack referenced in previous comment.
dataset-close-open.patch.txt

Hi Ed,
I believe I pointed you to HDFFV-10915. Can you see the issue? Please let me know if you still cannot see JIRA issues and do not have access to our repo.

Unfortunately I do not have a good test for this. My memory checking during tests is not showing the problem.
Does anyone have a simple C program that can demonstrate the memory growth?

OK, sorry for the delay, but I finally had a chance to take a better look at this and come up with a reproducer.  This isn't fixed by #1634
There should be two files.  close.txt and open.txt.  Both of these are from valgrind --tool=massif' and show the memory use during the running of my modified tst_vars.c.  As a summary, the max memory use inopen.txt` which is from the current NetCDF master pull (de4c487) is 10.8 MByte.
The max memory use in close.txt which is from a modified version is 2.6 MByte.  The change between the two is that I close the HDF5 dataset between writes.  In my sample code, I close and then immediately reopen the dataset, but a better fix would probably close and then defer the reopen until the next write.  The patch is also attached.
In a more complicated example using one of my applications, the corresponding difference is 101.4 MByte vs 16.6 MByte.
The difference is related to chunking since if I don't enable chunking (via the shuffle filter), the memory use between the two options is the same.
The disadvantage of this change is that it does slow down the execution for small runs; for large runs, it seems to be faster (this is mentioned in previous comments above)
open.txt
close.txt
close_dataset.patch.txt

@epourmal

And the forgotten reproducer...
tst_vars.c.txt

@gsjaardema are you still seeing this in current master? I thought I had fixed it...

Yes, it is a different issue than what you fixed.

OK, I will take another look once I get my backlog of changes merged to master...


Enable readthedocs

@nudles  ready to merge

May be you can also add this badge to README:
[![Documentation Status](https://readthedocs.org/projects/apache-singa/badge/?version=latest)](https://apache-singa.readthedocs.io/en/latest/?badge=latest)

Please don't forget the Apache license header in this file.


fix/ndarray: remove reversed axes check

Pull Request Template
Checklist

[x] Confirmed that run-checks all script has been executed.
[x] Made sure the book is up to date with changes in this PR.

Related Issues/PRs
fix #1053
Changes
Remove reversed axes layout check to allow column major tensor to be reshaped into row major.
Testing
Ran cargo test under burn-ndarray and run-checks all
NOTE:  Although the shape() bug can be fixed by this, there is still some weird logic in ndarry::concatenate(...) function to compute new strides for empty tensors where they prefer to producing column major layout. Maybe we should call reshape(...)  in NdArrayOps::cat(...) too and add some tests against the cat result.

@AuruTus I think it would be valuable to add the code snippet from this issue https://github.com/tracel-ai/burn/issues/1053 as a test before merging. The test should be generic over the backend in burn-tensor/src/tests

@AuruTus I think it would be valuable to add the code snippet from this issue #1053 as a test before merging. The test should be generic over the backend in burn-tensor/src/tests

Sure, I add it under stack 's unit tests. That reshaping after stacking test can cover all backends now.


Request answers to some doubts about running the code process

Hello, excuse me. I would like to ask you a few questions.
First question: Running Python train_ When flow.py -- category car | chair | airplane, do I need to choose one of the car | chair | airplane options? Because I see in the code that one of the options is selected, rather than selecting all three at the same time.
Second question: train_ Flow.py, sample_ Flow.py, train_ Reflow. py, train_ Do I need to finish running the previous program before running the next program for these four programs?
Finally, may I ask if the train code needs to run 20000epoch, 10000epoch, 10000epoch, and 10000epoch respectively? I am running at a particularly slow speed, so I would like to ask if it is necessary to run so many epochs?
Looking forward to your reply and wishing you success in your work!

Thanks for being interested in our project.
For the first question, by default, you can choose one or just leave it blank. You can also make it a list to train all the classed in the list.
Second, yes, they are depend on the previous checkpoint so you need to run them one by one.
Final question, no, you can run it for a shorter epochs, for example 500-1000, I remember it is enough to see some reasonable results. 20000 is just for marching other works and getting a best number during evaluation.

Hello, after running 100epoch, I will generate the epoch_ Add 99.pth to sample_ When running 'parser. add_argument (' -- model ', default='./output/train_flow/2023-08-28-08-01-24/epoch_99. pth ', help=' path to model (to continue training) 'in flow.py, an error occurred as follows: What is the reason for this?
(wxpy38) wangxin@wangxin-IdeaCentre-GeekPro-17IAB:~/1_code/cvpr2023_PSF$ python sample_flow.py
Directory missing : ./data/ShapeNetCore.v2.PC15k/02691156/train
Traceback (most recent call last):
File "sample_flow.py", line 699, in
main()
File "sample_flow.py", line 618, in main
train_dataset, _ = get_dataset(opt.dataroot, opt.npoints, opt.category)
File "sample_flow.py", line 420, in get_dataset
tr_dataset = ShapeNet15kPointClouds(root_dir=dataroot,
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 250, in init
super(ShapeNet15kPointClouds, self).init(
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 100, in init
self.all_points = np.concatenate(self.all_points)  # (N, 15000, 3)
File "<array_function internals>", line 200, in concatenate
ValueError: need at least one array to concatenate

Hello, thank you for your enthusiastic answer earlier. After running the program 'train_flow. py' to the 99th epoch, my program stopped due to 'out of memory' and generated the weight 'epoch_99. pth'. Then, I added 'epoch_99. pth' to 'sample_flow. py' to train and run the program, but the following error occurred: What is the reason for this?
(wxpy38) wangxin@wangxin-IdeaCentre-GeekPro-17IAB:~/1_code/cvpr2023_PSF$ python sample_flow.py
Directory missing : ./data/ShapeNetCore.v2.PC15k/02691156/train
Traceback (most recent call last):
File "sample_flow.py", line 699, in
main()
File "sample_flow.py", line 618, in main
train_dataset, _ = get_dataset(opt.dataroot, opt.npoints, opt.category)
File "sample_flow.py", line 420, in get_dataset
tr_dataset = ShapeNet15kPointClouds(root_dir=dataroot,
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 250, in init
super(ShapeNet15kPointClouds, self).init(
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 100, in init
self.all_points = np.concatenate(self.all_points) # (N, 15000, 3)
File "<array_function internals>", line 200, in concatenate
ValueError: need at least one array to concatenate

Hi, I think this mainly because the data directory is set in a wrong way. Like the error message said: Directory missing : ./data/ShapeNetCore.v2.PC15k/02691156/train
in fact, sample step does not need a data input, but I reuse some of the code, so please at least set a valid dataset directory( maybe same as train_flow) then it should be ok.

I initially forgot to change the location of the dataset, but after correcting the dataset path in 'sample_flow. py', I still reported the same error as before. Can you guide me?
(wxpy38) wangxin@wangxin-IdeaCentre-GeekPro-17IAB:~/1_code/cvpr2023_PSF$ python sample_flow.py
Directory missing : ./datasets/ShapeNetCore.v2.PC15k/ShapeNetCore.v2.PC15k/02691156/train
Traceback (most recent call last):
File "sample_flow.py", line 699, in
main()
File "sample_flow.py", line 618, in main
train_dataset, _ = get_dataset(opt.dataroot, opt.npoints, opt.category)
File "sample_flow.py", line 420, in get_dataset
tr_dataset = ShapeNet15kPointClouds(root_dir=dataroot,
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 250, in init
super(ShapeNet15kPointClouds, self).init(
File "/home/wangxin/1_code/cvpr2023_PSF/datasets/shapenet_data_pc.py", line 100, in init
self.all_points = np.concatenate(self.all_points)  # (N, 15000, 3)
File "<array_function internals>", line 200, in concatenate
ValueError: need at least one array to concatenate

I still see the error message
Directory missing : ./datasets/ShapeNetCore.v2.PC15k/ShapeNetCore.v2.PC15k/02691156/train.
could you have a double check for this directory?


Unreached code

I think the code inside if ($this->persistentId !== null) {} in \Yiisoft\Cache\Memcached::addServers can never be executed https://github.com/yiisoft/cache/blob/master/src/Memcached.php#L88.
addServers() method is called only from constructor and $this->persistentId is always null in this case.
The same is for the following blocks https://github.com/yiisoft/cache/blob/master/src/Memcached.php#L114
https://github.com/yiisoft/cache/blob/master/src/Memcached.php#L118
getMemcached() is called from the constructor and then $this->cache is never null.

This is probably leftover after removing init() method and moving related code to constructor. There were already similar bugs found in the past and I would expect much more of them in other places too.

@rob006 is correct. Either these checks could be removed or there are missing arguments for constructor.

@alexkart was this one covered in PR?

Yes


InvPrompt for nsfw (nudity)

Hi there,
Could you provide InvPrompt for nudity? I'm considering using Ring-A-Bell attack to assess the safetyness of a T2I model, but optimizing it via genetic algorithm seems to be quite time-consuming...
BTW, Congratulations on your acceptance to ICLR 2024, and thanks for your fantastic work!

@enkeejunior1
Hello,
I didn't share InvPrompt for nudity due to concerns about explicit content.
Could you please send me an email? I will provide the file to you.
Thank you!

Thanks for getting back to me quickly.
Here's my email<EMAIL_ADDRESS>Thanks in advance.


Update loadbalancing documentation to detail the various Route53 tasks

Description
Currently installation-route53-loadbalancer.adoc details how to create Route53 loadbalancers using various *.sh scripts directly. As we provide Route53 tasks in our provision/cross-dc/Taskfile.yaml, we should update the documentation to use these as it simplifies the steps required.
Discussion
No response
Motivation
No response
Details
No response

We've moved to AWS Global Loadbalancers, and we don't plan to update Route 53 things so much and eventually remove them. So I'd argue this doesn't add much value, therefore closing it.


Files listed in bookfile not found?

If a file specified in the .book file is not actually there, what should happen? Terminate the program with a useful error message (or abort and proceed to loop if in --watch mode), presumably.

Turns out we were already skipping missing files, but doing so silently. Add a warning.


Error while running in macosx

I get the following exception when running on macosx with node v0.10.24:
alert: [steward] exception diagnostic=Cannot find module 'node-blink1'
alert: [steward] exception stack=[{"fileName":"module.js","lineNumber":338,"functionName":"Function.Module._resolveFilename","typeName":"Function","methodName":"Module._resolveFilename","columnNumber":15,"native":false},{"fileName":"module.js","lineNumber":280,"functionName":"Function.Module._load","typeName":"Function","methodName":"Module._load","columnNumber":25,"native":false},{"fileName":"module.js","lineNumber":364,"functionName":"Module.require","typeName":"Module","methodName":"require","columnNumber":17,"native":false},{"fileName":"module.js","lineNumber":380,"functionName":"require","typeName":"Object","methodName":null,"columnNumber":17,"native":false},{"fileName":"/Users/arcturus/dev/git/community/steward/steward/devices/devices-lighting/lighting-blink1-led.js","lineNumber":4,"functionName":"","typeName":"Object","methodName":null,"columnNumber":19,"native":false},{"fileName":"module.js","lineNumber":456,"functionName":"Module._compile","typeName":"Module","methodName":"_compile","columnNumber":26,"native":false},{"fileName":"module.js","lineNumber":474,"functionName":"Object.Module._extensions..js","typeName":"Object","methodName":"Module._extensions..js","columnNumber":10,"native":false},{"fileName":"module.js","lineNumber":356,"functionName":"Module.load","typeName":"Module","methodName":"load","columnNumber":32,"native":false},{"fileName":"module.js","lineNumber":312,"functionName":"Function.Module._load","typeName":"Function","methodName":"Module._load","columnNumber":12,"native":false},{"fileName":"module.js","lineNumber":364,"functionName":"Module.require","typeName":"Module","methodName":"require","columnNumber":17,"native":false}]
uncaught exception: Error: Cannot find module 'node-blink1'
Press ^C to exit or wait 10 seconds to restart

Had to manually add the package node-blink1

npm install should have installed node-blink1.  Are you using the homebrew version of node?

I'm using node installed via nmv.

Can you try installing blink-1 manually, and let me know how steward reacts?

Yep, that was I did (see 2nd commend). Installing manually works ok and let's steward start

Your right, my bad.
Can you send me the versions of node and npm you are using, as well as git rev-parse HEAD?

Running node 4.2.0
With commit c000d65f1f431727e54bf0959c521ef359323cb6


Why im getting this type error??

Im using NextJS with Typescript and its showing me this error..!!

What version of TypeScript are you using?
Works fine in versions 3.8.3 and above https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbwK4GcCmBlaMCGAjAGzQF84AzKCEOAcgAEATAOwYFoBrYGAehW3yI0A3ACgRZJEwDGMYBCZwAKmhQwAFAEpEIuLtSZ+hNGoTAGALlowVMGsQ2jiQA

I got the same error but it fixed after restarting vscode. I think this happens when you install @dnd-kit/sortable before installing @dnd-kit/core.


Flexi vep build

Makes the VEP build path (for handling the Loftee plugin) reactive to the installed environment.
Adds a secondary argument VEP_CONDA, so that PERL5LIB can be set accurately (even if it means having to build the image a second time to get the path correct 😞)
I think this can be assigned using --build-arg VEP_CONDA=1 in the image-building workflow job, please correct me if this isn't possible!

@lgruen I had a play around locally - shell expansion worked great for completing the paths (deletion/copying), but appending that same path to .profile or .bashrc was done literally, and I'm not sure if * will be expanded when PERL5LIB is read. Prior to that, I'm not entirely sure those files would be loaded when the container is run.
There's another issue that elsewhere in the codebase, paths are hard coded which might make the effort to perfect this a wasted effort e.g. here
I'm worried about the number of cludgey hacks required to get this working in its current form... Maybe entering this PERL5LIB/LOFTEE path as a config entry, and reading in the VEP job code would be more versatile

appending that same path to .profile or .bashrc was done literally

You'll have to use something like this for the shell wildcard expansion to work:
RUN echo export PERL5LIB=$(echo /root/micromamba/share/ensembl-vep-*) >> ~/.bashrc

As long as the entrypoint for the container is bash, .bashrc should get evaluated and hence the environment variable should be set.

paths are hard coded which might make perfecting this a wasted effort e.g. here

That looks more problematic. Thanks for spotting this! I see two options:

Use a uniform path in the Docker container (which itself is already versioned), so the path in the code is version independent.
Use wildcard expansion at this place, too.

@lgruen I've tried to do something similar to your latest suggestion... I'm symlinking the whole installation folder (found using wildcard expansion) to a generic name, and adding that generic name as the .bashrc contents. I'm also throwing the LOFTEE_PLUGIN_PATH environment variable in there too, so we can remove the hard coded version from the VEP call

that double echo call to complete the expansion works great as an alternative

I'm also throwing the LOFTEE_PLUGIN_PATH environment variable in there too, so we can remove the hard coded version from the VEP call

Awesome, thanks a lot!

I've squashed the latter 3 RUN calls into a single RUN partitioned visually with comments

(Proposed slight formatting changes in https://github.com/populationgenomics/images/pull/70.)


Maybe --max-filsize is missing the mark

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2023.07.06 (update instructions) or later (specify commit)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
So, I was running yt-dlp lately and I searched through the README to find some new interesting options to try out.
The --max-filesize option seemed really nice because it made me think :
Okay, if the video is larger than X it would just skip the download of it and continue the process.
It kinda does so, but only if it has already downloaded the specified amount of data and that seems unnecessary to me.
Is there another way to make yt-dlp directly skip a video if the download is larger than X so without downloading anything?
Maybe I just did not read well enough.
Thanks in advance
PS:
I did not use the verbose command, but as you can see it downloaded to like 58.9% and than stopped because the --max-filesize option was set to 300M.
I think it would be better to change that so that it would even attempt the download at all.
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[youtube] Extracting URL: https://www.youtube.com/watch?v=maJXAwc-zT0
[youtube] maJXAwc-zT0: Downloading webpage
[youtube] maJXAwc-zT0: Downloading ios player API JSON
[youtube] maJXAwc-zT0: Downloading android player API JSON
[youtube] maJXAwc-zT0: Downloading player 2363d0d2
[youtube] maJXAwc-zT0: Downloading m3u8 information
[info] maJXAwc-zT0: Downloading 1 format(s): 303+251
[download] Destination: G:\yt_dlp_autohotkey_gui_files\download\temporaryStorage\Why The TF2 Mercenaries are Amazing Characters.f303.webm

[Downloading...] [  0.0% of  495.75MiB at  Unknown B/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of  495.75MiB at    4.91MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of  495.75MiB at    7.60MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of  495.75MiB at    6.85MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of  495.75MiB at    7.77MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.1% of  495.75MiB at    7.12MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.1% of  495.75MiB at    9.83MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.2% of  495.75MiB at   10.44MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.4% of  495.75MiB at   10.71MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.8% of  495.75MiB at   10.82MiB/s. Time passed : 00:00:00]
[Downloading...] [  1.6% of  495.75MiB at   10.91MiB/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at   10.94MiB/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:00]
[Downloading...] [  1.9% of  495.75MiB at    8.87MiB/s. Time passed : 00:00:00]
[Downloading...] [  2.0% of  495.75MiB at    7.12MiB/s. Time passed : 00:00:01]
[Downloading...] [  2.0% of  495.75MiB at    7.57MiB/s. Time passed : 00:00:01]
[Downloading...] [  2.1% of  495.75MiB at    9.62MiB/s. Time passed : 00:00:01]
[Downloading...] [  2.3% of  495.75MiB at    9.74MiB/s. Time passed : 00:00:01]
[Downloading...] [  2.7% of  495.75MiB at   10.61MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.5% of  495.75MiB at   10.11MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at   10.84MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    4.88MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    7.57MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    7.76MiB/s. Time passed : 00:00:01]
[Downloading...] [  3.9% of  495.75MiB at    9.23MiB/s. Time passed : 00:00:01]
[Downloading...] [  4.0% of  495.75MiB at    9.89MiB/s. Time passed : 00:00:01]
[Downloading...] [  4.1% of  495.75MiB at   10.36MiB/s. Time passed : 00:00:02]
[Downloading...] [  4.3% of  495.75MiB at   10.50MiB/s. Time passed : 00:00:02]
[Downloading...] [  4.7% of  495.75MiB at   10.75MiB/s. Time passed : 00:00:02]
[Downloading...] [  5.5% of  495.75MiB at   10.86MiB/s. Time passed : 00:00:02]
[Downloading...] [  5.9% of  495.75MiB at   10.90MiB/s. Time passed : 00:00:02]
[Downloading...] [  5.9% of  495.75MiB at  Unknown B/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    1.48MiB/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    3.44MiB/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    4.91MiB/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    7.60MiB/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    6.17MiB/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    7.77MiB/s. Time passed : 00:00:03]
[Downloading...] [  5.9% of  495.75MiB at    8.87MiB/s. Time passed : 00:00:03]
[Downloading...] [  6.0% of  495.75MiB at    9.97MiB/s. Time passed : 00:00:03]
[Downloading...] [  6.1% of  495.75MiB at    9.99MiB/s. Time passed : 00:00:03]
[Downloading...] [  6.3% of  495.75MiB at   10.50MiB/s. Time passed : 00:00:04]
[Downloading...] [  6.7% of  495.75MiB at   10.30MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.5% of  495.75MiB at   10.61MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at   10.60MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at  Unknown B/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at    4.89MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at    7.58MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.8% of  495.75MiB at    7.76MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.9% of  495.75MiB at    9.23MiB/s. Time passed : 00:00:04]
[Downloading...] [  7.9% of  495.75MiB at    9.99MiB/s. Time passed : 00:00:04]
[Downloading...] [  8.0% of  495.75MiB at   10.42MiB/s. Time passed : 00:00:04]
[Downloading...] [  8.2% of  495.75MiB at   10.70MiB/s. Time passed : 00:00:05]
[Downloading...] [  8.6% of  495.75MiB at   10.82MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.4% of  495.75MiB at   10.89MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at   10.93MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at  996.04KiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at    3.44MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at  123.33KiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at  252.80KiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at  509.59KiB/s. Time passed : 00:00:05]
[Downloading...] [  9.8% of  495.75MiB at    1.00MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.9% of  495.75MiB at    1.84MiB/s. Time passed : 00:00:05]
[Downloading...] [  9.9% of  495.75MiB at    3.15MiB/s. Time passed : 00:00:05]
[Downloading...] [ 10.0% of  495.75MiB at    4.91MiB/s. Time passed : 00:00:06]
[Downloading...] [ 10.2% of  495.75MiB at    6.59MiB/s. Time passed : 00:00:06]
[Downloading...] [ 10.6% of  495.75MiB at    8.11MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.4% of  495.75MiB at    9.41MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.7% of  495.75MiB at    9.66MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.7% of  495.75MiB at  Unknown B/s. Time passed : 00:00:06]
[Downloading...] [ 11.7% of  495.75MiB at  Unknown B/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at  Unknown B/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at   15.16MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at    7.77MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at    8.60MiB/s. Time passed : 00:00:06]
[Downloading...] [ 11.8% of  495.75MiB at    9.80MiB/s. Time passed : 00:00:06]
[Downloading...] [ 12.0% of  495.75MiB at   10.31MiB/s. Time passed : 00:00:06]
[Downloading...] [ 12.2% of  495.75MiB at   10.59MiB/s. Time passed : 00:00:07]
[Downloading...] [ 12.6% of  495.75MiB at    9.31MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.4% of  495.75MiB at   10.85MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at   10.79MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at  998.88KiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at    1.46MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at    4.88MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at   10.09MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.7% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.8% of  495.75MiB at    7.76MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.8% of  495.75MiB at    8.62MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.8% of  495.75MiB at    9.63MiB/s. Time passed : 00:00:07]
[Downloading...] [ 13.9% of  495.75MiB at   10.27MiB/s. Time passed : 00:00:07]
[Downloading...] [ 14.1% of  495.75MiB at   10.62MiB/s. Time passed : 00:00:07]
[Downloading...] [ 14.5% of  495.75MiB at   10.78MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.3% of  495.75MiB at    9.71MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at   10.88MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at  Unknown B/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at  Unknown B/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at   10.11MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at    6.32MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.7% of  495.75MiB at    7.88MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.8% of  495.75MiB at    4.47MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.8% of  495.75MiB at    6.26MiB/s. Time passed : 00:00:08]
[Downloading...] [ 15.9% of  495.75MiB at    7.95MiB/s. Time passed : 00:00:08]
[Downloading...] [ 16.1% of  495.75MiB at    9.23MiB/s. Time passed : 00:00:08]
[Downloading...] [ 16.5% of  495.75MiB at   10.01MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.3% of  495.75MiB at   10.42MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at   10.53MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at  Unknown B/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at    1.46MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at    3.41MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at    7.32MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.6% of  495.75MiB at    6.17MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.7% of  495.75MiB at    7.77MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.7% of  495.75MiB at    8.91MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.7% of  495.75MiB at    9.99MiB/s. Time passed : 00:00:09]
[Downloading...] [ 17.8% of  495.75MiB at   10.42MiB/s. Time passed : 00:00:09]
[Downloading...] [ 18.0% of  495.75MiB at   10.70MiB/s. Time passed : 00:00:09]
[Downloading...] [ 18.4% of  495.75MiB at    9.55MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.2% of  495.75MiB at   10.91MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.6% of  495.75MiB at   10.94MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.6% of  495.75MiB at  Unknown B/s. Time passed : 00:00:10]
[Downloading...] [ 19.6% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.6% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.6% of  495.75MiB at    4.86MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.7% of  495.75MiB at    7.57MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.7% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.7% of  495.75MiB at    7.76MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.7% of  495.75MiB at    8.90MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.7% of  495.75MiB at    9.79MiB/s. Time passed : 00:00:10]
[Downloading...] [ 19.8% of  495.75MiB at   10.31MiB/s. Time passed : 00:00:10]
[Downloading...] [ 20.1% of  495.75MiB at   10.64MiB/s. Time passed : 00:00:10]
[Downloading...] [ 20.5% of  495.75MiB at   10.38MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.3% of  495.75MiB at    9.46MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at   10.94MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at  249.50KiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at  599.16KiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at    1.37MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at    2.44MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at    5.04MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at    4.74MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at    6.53MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.6% of  495.75MiB at    8.31MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.7% of  495.75MiB at    9.43MiB/s. Time passed : 00:00:11]
[Downloading...] [ 21.8% of  495.75MiB at   10.20MiB/s. Time passed : 00:00:11]
[Downloading...] [ 22.0% of  495.75MiB at   10.21MiB/s. Time passed : 00:00:11]
[Downloading...] [ 22.4% of  495.75MiB at   10.59MiB/s. Time passed : 00:00:11]
[Downloading...] [ 23.2% of  495.75MiB at   10.76MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at   10.84MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at  Unknown B/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at  Unknown B/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at  Unknown B/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.5% of  495.75MiB at    6.84MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.6% of  495.75MiB at    8.28MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.6% of  495.75MiB at    7.55MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.6% of  495.75MiB at    8.92MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.7% of  495.75MiB at    9.80MiB/s. Time passed : 00:00:12]
[Downloading...] [ 23.9% of  495.75MiB at    7.79MiB/s. Time passed : 00:00:12]
[Downloading...] [ 24.3% of  495.75MiB at   10.34MiB/s. Time passed : 00:00:12]
[Downloading...] [ 25.1% of  495.75MiB at   10.81MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at   10.75MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at   71.50KiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at  214.50KiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at  467.13KiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at  938.44KiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at    1.78MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at    2.68MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at    4.14MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.5% of  495.75MiB at    5.48MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.6% of  495.75MiB at    7.62MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.7% of  495.75MiB at    9.05MiB/s. Time passed : 00:00:13]
[Downloading...] [ 25.9% of  495.75MiB at    9.88MiB/s. Time passed : 00:00:13]
[Downloading...] [ 26.3% of  495.75MiB at   10.41MiB/s. Time passed : 00:00:13]
[Downloading...] [ 27.1% of  495.75MiB at    9.80MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at   10.71MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at  Unknown B/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at  Unknown B/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at    4.91MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at    7.60MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at    6.17MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.5% of  495.75MiB at    7.77MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.6% of  495.75MiB at    9.24MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.6% of  495.75MiB at    9.99MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.7% of  495.75MiB at   10.42MiB/s. Time passed : 00:00:14]
[Downloading...] [ 27.9% of  495.75MiB at   10.67MiB/s. Time passed : 00:00:14]
[Downloading...] [ 28.3% of  495.75MiB at   10.82MiB/s. Time passed : 00:00:14]
[Downloading...] [ 29.1% of  495.75MiB at   10.91MiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at   10.94MiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at  497.01KiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at    1.46MiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at    2.27MiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at  154.77KiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at  112.43KiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at  227.65KiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.5% of  495.75MiB at  457.30KiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.6% of  495.75MiB at  918.21KiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.6% of  495.75MiB at    1.62MiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.7% of  495.75MiB at    2.85MiB/s. Time passed : 00:00:15]
[Downloading...] [ 29.9% of  495.75MiB at    4.53MiB/s. Time passed : 00:00:15]
[Downloading...] [ 30.3% of  495.75MiB at    6.42MiB/s. Time passed : 00:00:15]
[Downloading...] [ 31.1% of  495.75MiB at    8.11MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.4% of  495.75MiB at    8.48MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.4% of  495.75MiB at  500.51KiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.4% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at    4.89MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at    3.65MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at    5.54MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.5% of  495.75MiB at    7.28MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.7% of  495.75MiB at    8.73MiB/s. Time passed : 00:00:16]
[Downloading...] [ 31.9% of  495.75MiB at    6.44MiB/s. Time passed : 00:00:16]
[Downloading...] [ 32.3% of  495.75MiB at    8.08MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.1% of  495.75MiB at   10.04MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at   10.23MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at  Unknown B/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at  Unknown B/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.4% of  495.75MiB at    6.84MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.5% of  495.75MiB at    6.90MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.5% of  495.75MiB at    9.23MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.5% of  495.75MiB at    5.20MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.6% of  495.75MiB at    7.04MiB/s. Time passed : 00:00:17]
[Downloading...] [ 33.8% of  495.75MiB at    8.59MiB/s. Time passed : 00:00:17]
[Downloading...] [ 34.2% of  495.75MiB at    9.65MiB/s. Time passed : 00:00:17]
[Downloading...] [ 35.0% of  495.75MiB at   10.22MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at   10.39MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at  Unknown B/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    2.29MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    4.91MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    7.60MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    6.17MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    7.84MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.4% of  495.75MiB at    8.96MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.5% of  495.75MiB at    8.08MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.6% of  495.75MiB at    7.58MiB/s. Time passed : 00:00:18]
[Downloading...] [ 35.8% of  495.75MiB at    8.94MiB/s. Time passed : 00:00:18]
[Downloading...] [ 36.2% of  495.75MiB at    9.86MiB/s. Time passed : 00:00:18]
[Downloading...] [ 37.0% of  495.75MiB at   10.36MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at   10.49MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at  988.52KiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    1.46MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    4.87MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    7.55MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    5.60MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.3% of  495.75MiB at    1.95MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.4% of  495.75MiB at    1.92MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.5% of  495.75MiB at    2.95MiB/s. Time passed : 00:00:19]
[Downloading...] [ 37.7% of  495.75MiB at    5.83MiB/s. Time passed : 00:00:19]
[Downloading...] [ 38.1% of  495.75MiB at    9.71MiB/s. Time passed : 00:00:19]
[Downloading...] [ 38.9% of  495.75MiB at   10.30MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at   10.43MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at  988.52KiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at    2.90MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.2% of  495.75MiB at    6.84MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.3% of  495.75MiB at    8.28MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.3% of  495.75MiB at    8.31MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.3% of  495.75MiB at    9.42MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.4% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:20]
[Downloading...] [ 39.6% of  495.75MiB at   10.48MiB/s. Time passed : 00:00:20]
[Downloading...] [ 40.0% of  495.75MiB at   10.73MiB/s. Time passed : 00:00:20]
[Downloading...] [ 40.8% of  495.75MiB at   10.85MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at   10.90MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at  Unknown B/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at  Unknown B/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at    3.40MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at    7.28MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at   10.05MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at    6.16MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at    7.75MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.2% of  495.75MiB at    9.23MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.3% of  495.75MiB at    9.99MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.4% of  495.75MiB at   10.42MiB/s. Time passed : 00:00:21]
[Downloading...] [ 41.6% of  495.75MiB at   10.53MiB/s. Time passed : 00:00:21]
[Downloading...] [ 42.0% of  495.75MiB at   10.73MiB/s. Time passed : 00:00:21]
[Downloading...] [ 42.8% of  495.75MiB at   10.85MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at   10.33MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at  Unknown B/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at  Unknown B/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at  Unknown B/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at  288.76KiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at  585.51KiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at    1.16MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at    2.30MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.2% of  495.75MiB at    3.72MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.3% of  495.75MiB at    5.61MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.4% of  495.75MiB at    7.20MiB/s. Time passed : 00:00:22]
[Downloading...] [ 43.6% of  495.75MiB at    8.71MiB/s. Time passed : 00:00:22]
[Downloading...] [ 44.0% of  495.75MiB at    9.70MiB/s. Time passed : 00:00:22]
[Downloading...] [ 44.8% of  495.75MiB at   10.28MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at   10.42MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at    6.84MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at    6.95MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.1% of  495.75MiB at    8.63MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.2% of  495.75MiB at    9.82MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.3% of  495.75MiB at    9.81MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.5% of  495.75MiB at    7.61MiB/s. Time passed : 00:00:23]
[Downloading...] [ 45.9% of  495.75MiB at    9.40MiB/s. Time passed : 00:00:23]
[Downloading...] [ 46.7% of  495.75MiB at   10.88MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at   10.92MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at    1.47MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at    4.89MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at    6.15MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at    7.75MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.1% of  495.75MiB at    8.90MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.2% of  495.75MiB at    9.99MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.3% of  495.75MiB at    7.58MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.5% of  495.75MiB at    8.89MiB/s. Time passed : 00:00:24]
[Downloading...] [ 47.9% of  495.75MiB at    9.81MiB/s. Time passed : 00:00:24]
[Downloading...] [ 48.7% of  495.75MiB at   10.00MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at   10.50MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at  Unknown B/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at   15.04MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at    5.60MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at    7.29MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.1% of  495.75MiB at    8.30MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.2% of  495.75MiB at    9.42MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.3% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.5% of  495.75MiB at   10.53MiB/s. Time passed : 00:00:25]
[Downloading...] [ 49.9% of  495.75MiB at   10.76MiB/s. Time passed : 00:00:25]
[Downloading...] [ 50.7% of  495.75MiB at   10.82MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at   10.81MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at  501.89KiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at 1004.22KiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at    2.29MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at    3.68MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at    7.60MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at    6.85MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.0% of  495.75MiB at    7.76MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.1% of  495.75MiB at    1.98MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.1% of  495.75MiB at    1.96MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.2% of  495.75MiB at    2.81MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.4% of  495.75MiB at    4.79MiB/s. Time passed : 00:00:26]
[Downloading...] [ 51.8% of  495.75MiB at    6.66MiB/s. Time passed : 00:00:26]
[Downloading...] [ 52.6% of  495.75MiB at    8.30MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    8.70MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at  987.13KiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    2.89MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    3.39MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    7.26MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    7.58MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    6.15MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    7.30MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.0% of  495.75MiB at    8.90MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.1% of  495.75MiB at    9.79MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.2% of  495.75MiB at   10.31MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.4% of  495.75MiB at   10.64MiB/s. Time passed : 00:00:27]
[Downloading...] [ 53.8% of  495.75MiB at    8.98MiB/s. Time passed : 00:00:27]
[Downloading...] [ 54.6% of  495.75MiB at   10.81MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at   10.92MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at  989.46KiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at    2.90MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at    3.42MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at   10.10MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at    6.84MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at    8.27MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.0% of  495.75MiB at    9.23MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.1% of  495.75MiB at   10.09MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.2% of  495.75MiB at   10.47MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.4% of  495.75MiB at   10.73MiB/s. Time passed : 00:00:28]
[Downloading...] [ 55.8% of  495.75MiB at   10.83MiB/s. Time passed : 00:00:28]
[Downloading...] [ 56.6% of  495.75MiB at   10.44MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at   10.40MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at  Unknown B/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at  Unknown B/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at  Unknown B/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at    7.38MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at   10.15MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at    4.10MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at    7.30MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.0% of  495.75MiB at    7.33MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.1% of  495.75MiB at    8.09MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.2% of  495.75MiB at    9.83MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.4% of  495.75MiB at   10.27MiB/s. Time passed : 00:00:29]
[Downloading...] [ 57.8% of  495.75MiB at   10.63MiB/s. Time passed : 00:00:29]
[Downloading...] [ 58.6% of  495.75MiB at   10.72MiB/s. Time passed : 00:00:30]
[Downloading...] [ 58.9% of  495.75MiB at   10.80MiB/s. Time passed : 00:00:30]
[download] File is larger than max-filesize (316575240 bytes > 314572800 bytes). Aborting.

[download] Destination: G:\yt_dlp_autohotkey_gui_files\download\temporaryStorage\Why The TF2 Mercenaries are Amazing Characters.f251.webm

[Downloading...] [  0.0% of   23.59MiB at  333.62KiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of   23.59MiB at  753.29KiB/s. Time passed : 00:00:00]
[Downloading...] [  0.0% of   23.59MiB at    1.72MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.1% of   23.59MiB at    2.94MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.1% of   23.59MiB at    2.53MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.3% of   23.59MiB at    3.42MiB/s. Time passed : 00:00:00]
[Downloading...] [  0.5% of   23.59MiB at    4.60MiB/s. Time passed : 00:00:00]
[Downloading...] [  1.1% of   23.59MiB at    6.56MiB/s. Time passed : 00:00:00]
[Downloading...] [  2.1% of   23.59MiB at    8.19MiB/s. Time passed : 00:00:00]
[Downloading...] [  4.2% of   23.59MiB at    9.35MiB/s. Time passed : 00:00:00]
[Downloading...] [  8.5% of   23.59MiB at   10.11MiB/s. Time passed : 00:00:00]
[Downloading...] [ 17.0% of   23.59MiB at   10.42MiB/s. Time passed : 00:00:00]
[Downloading...] [ 33.9% of   23.59MiB at   10.69MiB/s. Time passed : 00:00:00]
[Downloading...] [ 40.9% of   23.59MiB at   10.81MiB/s. Time passed : 00:00:00]
[Downloading...] [ 40.9% of   23.59MiB at  333.78KiB/s. Time passed : 00:00:00]
[Downloading...] [ 40.9% of   23.59MiB at 1001.35KiB/s. Time passed : 00:00:00]
[Downloading...] [ 41.0% of   23.59MiB at    1.72MiB/s. Time passed : 00:00:00]
[Downloading...] [ 41.0% of   23.59MiB at    3.68MiB/s. Time passed : 00:00:00]
[Downloading...] [ 41.1% of   23.59MiB at    2.76MiB/s. Time passed : 00:00:00]
[Downloading...] [ 41.2% of   23.59MiB at    3.42MiB/s. Time passed : 00:00:00]
[Downloading...] [ 41.5% of   23.59MiB at    4.01MiB/s. Time passed : 00:00:01]
[Downloading...] [ 42.0% of   23.59MiB at    5.42MiB/s. Time passed : 00:00:01]
[Downloading...] [ 43.0% of   23.59MiB at    7.24MiB/s. Time passed : 00:00:01]
[Downloading...] [ 45.2% of   23.59MiB at    8.70MiB/s. Time passed : 00:00:01]
[Downloading...] [ 49.4% of   23.59MiB at    9.71MiB/s. Time passed : 00:00:01]
[Downloading...] [ 57.9% of   23.59MiB at   10.11MiB/s. Time passed : 00:00:01]
[Downloading...] [ 74.8% of   23.59MiB at   10.64MiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.6% of   23.59MiB at   10.71MiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.6% of   23.59MiB at  500.45KiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.7% of   23.59MiB at 1006.55KiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.7% of   23.59MiB at    1.94MiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.7% of   23.59MiB at    4.17MiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.8% of   23.59MiB at    2.24MiB/s. Time passed : 00:00:01]
[Downloading...] [ 81.9% of   23.59MiB at    3.32MiB/s. Time passed : 00:00:01]
[Downloading...] [ 82.2% of   23.59MiB at    4.51MiB/s. Time passed : 00:00:01]
[Downloading...] [ 82.7% of   23.59MiB at    6.31MiB/s. Time passed : 00:00:01]
[Downloading...] [ 83.8% of   23.59MiB at    7.99MiB/s. Time passed : 00:00:01]
[Downloading...] [ 85.9% of   23.59MiB at    9.24MiB/s. Time passed : 00:00:02]
[Downloading...] [ 90.1% of   23.59MiB at   10.04MiB/s. Time passed : 00:00:02]
[Downloading...] [ 98.6% of   23.59MiB at   10.40MiB/s. Time passed : 00:00:02]
[Downloading...] [100.0% of   23.59MiB at   10.55MiB/s. Time passed : 00:00:02]
[Downloading...] [100.0% of   23.59MiB at 10.14MiB/s. Time passed : 00:00:02]

Honestly, idk either why that option exists either. But it has always behaved like that in youtube-dl and I'm not gonna change it in case someone depends on that behavior.
What you want for your case is either https://github.com/yt-dlp/yt-dlp#filtering-formats or --match-filter

Yeah you are right. If there is an option to do what I described by using the format filtering option you really helped me anyway.


Import local packages with location

This PR fixes #244, by changing how local packages are specified in the packages.dhall (yes this is a breaking change, because the old local syntax will now error out)
Taking the README example, we go from this:
let additions =
  { foobar =
      mkPackage
        (../foobar/spago.dhall).dependencies
        "../foobar"
        "local-fix-whatever"
  }

to this:
let additions =
  { foobar = ../foobar/spago.dhall as Location }

This means a couple of things:

the issue from #244 is fixed because Dhall will adjust the relative path properly
but since it won't resolve the file, it's now possible to have a single shared packages.dhall, that will contain e.g. all the packages in your repo (this wasn't possible before as you'd have circular imports in your Dhall file)

Things missing:

[ ] handle all the various errors with nice error messages
[ ] wait for a new dhall-lang release
[ ] wait for a new dhall-haskell release
[ ] wait for #289 to be merged
[ ] add tests for building with local packages
[ ] add tests for the list-packages command
[ ] update the README
[ ] add a proper "monorepo" section

@f-f Thanks for this, I'll try it with our monorepo. Excited that it also properly supports a single packages.dhall - we've been factoring out spago-deps.dhall files to avoid the circular imports and it's a pain!

@f-f Still hitting circular import errors on this branch, I'm afraid. Our setup is:
- lib
  - purescript
    - packages.dhall
    - lib1
      - spago.dhall
    - lib2
      - spago.dhall
    - lib3
      - spago.dhall
app1
  - spago.dhall
app2
  - spago.dhall

packages.dhall is our shared single packages file and imports the libs as
let additions =
  { lib1 = ./lib1/spago.dhall as Location
  , lib2 = ./lib2/spago.dhall as Location
  , lib3 = ./lib3/spago.dhall as Location
  }

Each lib has a pretty trivial spago.dhall that includes packages = ../packages.dhall and similarly app1/spago.dhall includes packages = ../lib/purescript/packages.dhall.
When I spago install inside app1 I get
spago: The following packages have circular dependencies:
  - lib1
  - lib2
  - lib3

@elliotdavies wow great catch! I can reproduce the issue locally, and it's not due to circular dependencies per se, but it's because the imports in lib1/spago.dhall are resolved relatively to the folder you're calling Spago from.
So e.g. if you are in app1 and you have a deps.dhall both in lib1 and in app1, you'll get the latter one, which most likely contains lib1 as a dependency, causing the circular deps problem.
So the root cause is the kinda-hacky implementation (but I cannot think of many other possible ones, so we'll keep this one) of local packages resolution here:
https://github.com/spacchetti/spago/blob/cfa28d7142cc45a7415dde7f1faaa68b51e3c3c7/src/Spago/Config.hs#L76-86
What's happening here is that we:

pattern match on a as Location import in line 76
read the raw AST (i.e. not resolved yet, so it contains imports and everything) in line 81
transform the AST so that it goes from a config like { packages = .., dependencies = .. } to just whatever the content of dependencies is, in line 85
then resolve the expression in line 86 (relative to our current directory)

So if the expression is pure no problem, if it contains relative imports then they are not going to be correct.
Two possible solutions here:

the quick one is that we just forbid imports inside dependencies for local packages
the right one (but the one with more potential corner cases) is to just set the relative path to the imported package

Right, I recalled there was a nice way to plug this in, so it was an easier fix than I expected.
b12ea08 fixes the issue for me locally, @elliotdavies could you try it?

@f-f Yep, that's done it! (After a brief moment of panic when Spago just said "aaa" - eventually I realised I'd hit this TODO error case 😂) Glad you were able to find a nice fix.
I might have some time Sunday or Monday if you'd like a hand ticking off some of the TODO items for this?

@elliotdavies thanks, some help would be lovely! There are in fact some independent changes that should be merged in master before this goes in, and that you could pick up:

adding tests with output fixtures for spago list-packages and spago list-packages --json (since I got very close to breaking them in this PR, so I'd like to have tests merged before to ensure I'm not breaking their behaviour)
adding tests for spago build involving local packages (we don't have any) and your current monorepo setup (it'd be a nice demonstration of this feature to go from having to split out the dependencies in separate files to just having them in the spago.dhall)

cc @Dretch: since in this branch I'm shuffling code for the Config (mainly going from Either to IO as the base monad to make things less wrapped, since we error out immediately anyways) in bf71f813955dfe5435556f2f30c3baa992d7e35a I'm also absorbing the PublishConfig into the Config to have less parsing code

cc @Dretch: since in this branch I'm shuffling code for the Config parsing (mainly going from Either to IO as the base monad to make things less wrapped, since we error out immediately anyways) in bf71f81 I'm also absorbing the PublishConfig into the Config to have less parsing code

It all looks sensible as far as I can see. :+1:


Model Checking Pane empty in VSCode online because of unsafe-inline

main.js:441 Refused to load the stylesheet 'https://4651e61d-b770-415f-8cbc-cbbc176dae2d.vscode-webview-test.com/26076a4de974ead31f97692a0d32f90d735645c0/vscode-resource/file///home/vsonline/.vscode-remote/extensions/alygin.vscode-tlaplus-1.3.1/resources/check-result-view.css' because it violates the following Content Security Policy directive: "style-src 'unsafe-inline' https://*.vscode-webview-test.com/26076a4de974ead31f97692a0d32f90d735645c0". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

(anonymous) @ main.js:441
setTimeout (async)
(anonymous) @ main.js:438

main.js:441 Refused to load the script 'https://4651e61d-b770-415f-8cbc-cbbc176dae2d.vscode-webview-test.com/26076a4de974ead31f97692a0d32f90d735645c0/vscode-resource/file///home/vsonline/.vscode-remote/extensions/alygin.vscode-tlaplus-1.3.1/resources/check-result-view.js' because it violates the following Content Security Policy directive: "script-src https://*.vscode-webview-test.com/26076a4de974ead31f97692a0d32f90d735645c0". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

(anonymous) @ main.js:441
setTimeout (async)
(anonymous) @ main.js:438

Something appears to have changed in VSCode online, because version 1.1 and 1.2 - which I remember to work correctly - show the same error.

You're right, the usafe-inline is the root cause here. I'll have a look at it.

@lemmy, could you, please, try this build?
vscode-tlaplus-1.3.2.vsix.zip

Awesome, it work!

v1.3.2 with this fix has been published. Thanks for helping with this one.


Pull in the analytics update into the latest release (i.e. default github.io page)

This change cherry-picks the analytics change in https://github.com/microsoft/MixedRealityToolkit-Unity/pull/8532 into the latest release.
So the reason we have to do this is interesting:
Prior to last month-ish, the default branch that showed up on our github.io was mrtk_development, which meant that the previous change would have worked about a month ago. We recently made a change to switch our default github.io branch (https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/GettingStartedWithTheMRTK.html) to point to the latest release (i.e. right now, 2.4), which means that the previous change didn't actually show up in the default/root folder.
In order to make this change show up, we need to cherry pick the change and then rebuild the docs (which will happen automatically once this gets submitted)

/azp run mrtk_docs


add xnaas.info

The HTML and CSS are ~1.86KB transferred (~2KB before compression), the massive favicon.ico
is the bulk of the site at 12.12KB transfered (32.21KB before compression).

I took an alternative approach to the favicon and it's now only 2.03KB.

How did you reduce the favicon? my 32x32 is clocking in at a massive 3.4 kB!

@boehs: I talked about my process a little bit here on tildes.net.

Awesome! I love to see that there is even some conversation about the page sizes happening!
Welcome to the 250kb Club!

Welcome to the 250kb Club!

Thanks! Next up: a 25kb club and a 5kb club and an elitist 1kb and/or 0kb club! 😜

Awesome! I love to see that there is even some conversation about the page sizes happening!

Wait until you see people sick of the web entirely who are all circlejerking each other on Gemini. 😉


Implement Batch Processing

Description

Implemented batch processing by creating a directory structure that mirrors val_data and storing the images generated by the face recognizer in it.
Related Issue

Fixes #2
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Motivation and Context

Checklist:

[x] I have registered myself at Contrihub website.
[x] My code follows the code style of this project.
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Sure, go ahead.

Make a new issue for this task. Refer Url to this comment on that issue.
The tasks for issue would be:
You need to check the functionality of each system now and check if it's working as expected. (main.py, security_system.py, train_model.py and tests)
Attach screenshots of outputs.
Report any bugs.
If you feel any thing at any place can be improved, you can mention that as well in your issue's comments as well.
If it's a minor bug, you can go and fix them yourself.
For a major bug make a issue for it. (I don't think we'll encounter any major bugs)
Refractor the code while you're going through code.

Refer docs if you need.
To claim your points for all this, make a PR with your changes and also update the project structure mentioned in README and technical_documentaion.


New AWS Edge Location in Lagos, Nigeria

Hello,
I am writing to inform you that Amazon Web Services (AWS) has announced a new edge location in Lagos, Nigeria. This location was launched on June 15, 2023, and it is expected to provide a 20% improvement in latency, on average, for data delivered in Nigeria1.
RTEdge.net

Here is the JSON object for this new location, which adheres to the format used in the aws-edge-locations repository:
{
  "code": "LOS",
  "city": "Lagos",
  "state": null,
  "country": "Nigeria",
  "countryCode": "NG",
  "count": 1,
  "latitude": 6.5773701668,
  "longitude": 3.321160078,
  "region": "Africa",
  "pricingRegion": "Africa"
}

The code for the new edge location is "LOS50-P1"2, and the latitude and longitude of the Murtala Muhammed International Airport in Lagos are given above, matching speed.cloudflare.com/locations!
I kindly request that you consider adding this information to the aws-edge-locations repository.
Thank you for your attention to this matter.
Best regards,
Cetin Sert
Elefunc, Inc.

Visit RTEdge.net/? to see how we add it on-the-fly to the data from this repo and use on our multi-cloud network map.

Closed via https://github.com/tobilg/aws-edge-locations/commit/98bf50643e5a57da8ed20e523cbc59d3b23d7c0d New version 0.4.16 was just published.


Compile PBES2 in PKCS5 only if ASN1 is enabled

Description
This PR superseeds https://github.com/ARMmbed/mbedtls/pull/680. The changes provides an empty implementation of mbedtls_pkcs5_pbes2() whenever MBEDTLS_ASN1_PARSE_C is not enabled. This makes it possible to compile and use PBES2 in PKCS5 without satisfying all the dependencies for PBES2.
Status
READY
Requires Backporting
Yes
Which branch?
Mbed TLS 2.7: https://github.com/ARMmbed/mbedtls/pull/1524
Mbed TLS 2.1: https://github.com/ARMmbed/mbedtls/pull/1525

@mpg: Thanks for the review. I took a very similar approach for the testing.


grizzly-jersey and undertow-jersey: MySQL deadlock part 2

Lowering the JDBC pooled connections to 192 haven't resolved the problem. Next steps to try:

Lower the thread count in the worker pool;
Lower the pooled connections value;

But how the code manages to make 200+ waiting writing transactions with 192 connections?

The mystery is no mystery anymore: I've missed the fact that there IS really a transaction deadlocks. See PR №5239 in the parent repository.


is rethinkdb-elixir production ready?

can we use rethinkdb-elixir in production? when can we expect rethinkdb-elixir 1.0 release?

@ashwinreddymekala FWIW i've been using it in production in two apps with great results 👍

@AdamBrodzinski It's good to hear that you are using in production with great results.
as README says The goal for 1.0.0 is to be stable. is version 0.4.0 unstable?

@ashwinreddymekala it is stable, its waiting for its last API change from its current response structure to :ok and :error tuple

Thanks for all your responses guys I don't see any reason to still open this issue.


CIAB: Dynamically choose the first mid server

Which issue is fixed by this PR? If not related to an existing issue, what does this PR do?
This PR would enable renaming the default Mid Server by removing the hard coded name CDN_in_a_Box_Mid. It now calls the API until a cachegroup exists. If there are more than one cachegroups, the first is selected.
Which TC components are affected by this PR?

[ ] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[ ] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[x] CDN in a Box

What is the best way to verify this PR? Please include manual steps or automated tests.
(If no tests are part of this PR, please provide explanation as to why no tests are included.)
Change the name in 060-ciabMid.json, parentCachegroupName in 070-ciabEdge.json and start CIAB. The default Mid server should have the new name.
Check all that apply

[ ] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[x] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Can one of the admins verify this patch?

After #3413 gets merged, $CDN has to be renamed to $CDN_NAME .

mid server should use MID_LOC cachegroup so you can not randomly choose one.

I agree with @Shihta , I don't think assigning the mid server to the cache group of the first server randomly enrolled/returned by the API is a good idea.

Sorry, I honestly did not check the full response of /api/1.3/servers. Do you think a random mid server would be sufficient? If yes, we could just add ?type=MID. If no, should the default be defined inside variables.env?

That won't work at all. Before the mid the server is enrolled, you shouldn't be able to find a mid server, so it'll just loop endlessly.

For me, I would like adding a parameter rather than random choice.
Even you specified the type, directly picking the first one is still a random selection method.
If you want to reuse the same mid container for larger system (more than 1 mid server/cachegroup), uncontrollable random selection method should not be a good idea.

It worked once, but there were probably some volumes not removed or containers still running. In the end, I used a variable that defined the name. Thank you for your comments.


packages in the pkg dir should not reference anything in internal

packages in pkg are intended to be available for external modules to use.


Remove link to kubernetes-client/community

Point directly to the file that the kubernetes/community link was
pointing to
ref: https://github.com/kubernetes-client/community/issues/6

/approve

Codecov Report

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

@@           Coverage Diff           @@
##           master      #83   +/-   ##
=======================================
  Coverage   91.85%   91.85%
=======================================
  Files          11       11
  Lines         994      994
=======================================
  Hits          913      913
  Misses         81       81

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 07ef626...c037d14. Read the comment docs.

/lgtm


How get upstream responses whole body，not only header or statusCode

Issue description
How get upstream responses whole body，not only header or statusCode
Environment

your apisix-java-plugin-runner version

Hope to provide function
PostFillter
postRequest.getUpstreamResponseBody()

No support yet. We need to wait for APISIX to complete this feature before we can support it.

response-rewrite lua has method " local body = core.response.hold_body_chunk(ctx)" get response body。but i only do Java.

response-rewrite has nothing to do with the plugin runner, they are not the same thing.

0.3.0版本还是没有支持获取上游响应的body，我也需要这个功能

this
when APISIX  complete this feature？

need too. At the same time, it is necessary to support body rewriting before the request reaches the upstream

Already supported, refer to: https://github.com/apache/apisix-java-plugin-runner/blob/main/docs/en/latest/development.md#get-the-upstream-response-and-process