July Cleanups

Starting a PR to address the comments on #136
Planning to hold this for additional cleanups that may be discovered while changes are on staging!

Things that are broken:

"Timeseries of Total and Labeled Trip Counts" -- all staging
Number of trips, etc on dfc-fermata (the survey responses look good though!)

errors found in logs:
sensed_algo_prefix is not defined while running the generic_timeseries notebook
--> missing parameter definition!!
generate_metrics: error: the following arguments are required: program in survey_metrics notebook
--> cause of missing charts on dfc-fermata

The only success I have had with reproducing the generate_metrics: error: the following arguments are required: program error was when I ran the command PYTHONPATH=.. python bin/generate_plots.py survey_metrics.ipynb  instead of PYTHONPATH=.. python bin/generate_plots.py survey_metrics.ipynb  default on the command line
But in the crontab file the correct command is present, so that is not the issue

generate_metrics: error: the following arguments are required: program in survey_metrics notebook
--> cause of missing charts on dfc-fermata

This seems unlikely to be the problem since the survey_metrics notebook generates the survey results and they seem fine. Are there any errors with the generic_metrics notebook?

Ah, I see! The survey_responses notebook is the one that generates the survey graphs. The default values are generated using survey_metrics. In our internal system that runs on AWS, we don't use the crontab, but AWS scheduled tasks, and the  generate_plots is in fact missing the program
python bin/generate_plots.py energy_calculations.ipynb default
python bin/generate_plots.py survey_responses.ipynb default
python bin/generate_plots.py survey_metrics.ipynb

Fixing it internally and tagging Abby

I've identified another bug that should be fixed here - every one of the tables in the text display of the survey responses is the same as the last one - I'm guessing I managed to overwrite the whole list every time instead of the correct position

I do wonder though, why are we showing the sensed modes and not the detected modes? I'm going to look into if we're ready to switch over to the detected modes ...

We're missing the 'ble_sensed_summary' in the test data that I have loaded, at least, is this mainstreamed in the data model yet?
It's in the code base! In server, admin dashboard, and the public dashboard
I at one point had this commented out, but have restored the code ... I can't find an example of it working yet though?
Is it just not in the data sample I have loaded? Dumping and reloading ...

After reloading the May 8th snapshot - bluetooth sensed modes are populating as expected -- most of the data at this point was collected before we were detecting the specific vehicle with bluetooth, so the large % of unknown makes sense.

Also updated the generic_metrics_sensed notebook to use the ble mode
ca-ebike does not use the ble mode:

dfc-fermata does use the ble mode:

I believe those are all the changes needed I will more completely this afternoon!

Tested on dfc-fermata - looks good
charts all generate
alt text is no longer overly duplicative

Tested on ca-ebike -- labeled trips are broken?

Tested on ca-ebike -- labeled trips are broken?

Totally fine in the notebook though ... clearing everything out and trying again
Just needed to reset my cached images!

@Abby-Wheelis just checking on whether this is done; I would like to merge and push to staging this weekend so that we can unblock the other changes

Yes, this should be ok to go to staging, sorry!


How to enable Swagger UI when using Conda

Description
This probably mostly comes down to unfamiliarity. I'm forced into using conda and the conda-forge channel because of some of my other dependencies instead of pypi. I can install connexion but I don't know how to install connexion[swagger-ui] as it is a pip extra and conda does not speak that language. (It's not directly possible, but there's something similar available in conda but I wouldn't know how to translate the pip extra to that)
I also can't install swagger_ui_bundle (a shot in the dark based on https://stackoverflow.com/a/60992592/17045052) because it's in the anaconda channel and conda is not finding it even though I'm listing in my conda environment file when I do conda env update -f ....
There are enough things I'm unfamiliar with here that I thought it might be better to ask directly:
What is the best way to get Swagger UI working with connexion when using conda (and conda-forge)?

Hi @dragorosson
You should be able to install packages in conda using pip. See the docs.
If you're still having issues, it's probably better to direct yourself to the conda community for help.


New validators

Added new validators
DigitRequired:
This validator ensures that the incoming data must contain a specified minimum number of digits.
:param min:
The minimum required digit in the string.
min default value is 1 digit at least.
:param message:
Error message to raise in case of a validation error.
UppercaseRequired:
This validator ensures that the incoming data must contain a specified minimum number of uppercase letters.
:param min:
The minimum required uppercase letter in the string.
min default value is 1 uppercase letter at least.
:param message:
Error message to raise in case of a validation error.
LowercaseRequired:
This validator ensures that the incoming data must contain a specified minimum number of lowercase letters.
:param min:
The minimum required lowercase letter in the string.
min default value is 1 lowercase letter at least.
:param message:
Error message to raise in case of a validation error.
SymbolRequired:
This validator ensures that the incoming data must contain a specified minimum number of symbols.
:param min:
The minimum required symbol in the string.
min default value is 1 symbol at least.
:param message:
Error message to raise in case of a validation error.

Thanks, but I don't plan to add these to the core library. You're welcome to turn these into your own PyPI package.

Thanks, but I don't plan to add these to the core library. You're welcome to turn these into your own PyPI package.


Unable to resolve dependency dotnet 3.5

Description
azure-arm.image:  - wixtoolset - Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
azure-arm.image: Running [#4]: choco install wixtoolset -y --force
azure-arm.image: Chocolatey v2.2.2
azure-arm.image: Installing the following packages:
azure-arm.image: wixtoolset
azure-arm.image: By installing, you accept licenses for the packages.
azure-arm.image: Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
azure-arm.image:
azure-arm.image: Chocolatey installed 0/1 packages. 1 packages failed.
azure-arm.image:  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
azure-arm.image:
azure-arm.image: Failures
azure-arm.image:  - wixtoolset - Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
azure-arm.image:  - wixtoolset - Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
azure-arm.image: Running [#4]: choco install wixtoolset -y --force
azure-arm.image: Chocolatey v2.2.2
azure-arm.image: Installing the following packages:
azure-arm.image: wixtoolset
azure-arm.image: By installing, you accept licenses for the packages.
azure-arm.image: Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
azure-arm.image:
azure-arm.image: Chocolatey installed 0/1 packages. 1 packages failed.
azure-arm.image:  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
azure-arm.image:
azure-arm.image: Failures
azure-arm.image:  - wixtoolset - Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
Is it regression?
No
Expected behavior
Expect image to be generated.
Actual behavior
azure-arm.image:  - wixtoolset - Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
azure-arm.image: Running [#4]: choco install wixtoolset -y --force
azure-arm.image: Chocolatey v2.2.2
azure-arm.image: Installing the following packages:
azure-arm.image: wixtoolset
azure-arm.image: By installing, you accept licenses for the packages.
azure-arm.image: Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
azure-arm.image:
azure-arm.image: Chocolatey installed 0/1 packages. 1 packages failed.
azure-arm.image:  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
azure-arm.image:
azure-arm.image: Failures
azure-arm.image:  - wixtoolset - Unable to resolve dependency 'dotnet3.5'. Source(s) used: 'https://community.chocolatey.org/api/v2/'.
Repro steps
Run the image generation script and it would fail as noted above.

HI All,
I downloaded code from two days ago and it failed similar error. Pls help this is stopping our builds for windows.
azure-arm.image: Running [#1]: choco install packer -y
azure-arm.image: Chocolatey v2.2.2
azure-arm.image: Installing the following packages:
azure-arm.image: packer
azure-arm.image: By installing, you accept licenses for the packages.
azure-arm.image: packer not installed. The package was not found with the source(s) listed.
azure-arm.image:  Source(s): 'https://community.chocolatey.org/api/v2/'
azure-arm.image:  NOTE: When you specify explicit sources, it overrides default sources.
azure-arm.image: If the package version is a prerelease and you didn't specify --pre,
azure-arm.image:  the package may not be found.
azure-arm.image: Please see https://docs.chocolatey.org/en-us/troubleshooting for more
azure-arm.image:  assistance.
azure-arm.image:
azure-arm.image: Chocolatey installed 0/1 packages. 1 packages failed.
azure-arm.image:  See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
azure-arm.image:
azure-arm.image: Failures
azure-arm.image:  - packer - packer not installed. The package was not found with the source(s) listed.
azure-arm.image:  Source(s): 'https://community.chocolatey.org/api/v2/'
azure-arm.image:  NOTE: When you specify explicit sources, it overrides default sources.
azure-arm.image: If the package version is a prerelease and you didn't specify --pre,
azure-arm.image:  the package may not be found.
azure-arm.image: Please see https://docs.chocolatey.org/en-us/troubleshooting for more
azure-arm.image:  assistance.

I even tried downloading code from five days ago https://github.com/actions/runner-images/tree/65efa8ca2d33fb499f6fa36f5dc16f43b4c2ee63 and i am now getting this error reported here but i am using windows 2022 : https://github.com/actions/runner-images/issues/9553
So, four attempts with last four commits and all fail with different errors. Hope that someone can help resolve one of these.

Hello @vamshisiram . Looks like problem was on 'choco' side. That's why checkout previous commits didnt helps. I tried to run manually on local machine choco install wixtoolsetand installation finished successfully.  Please, checkout latest commit frommain` branch and try again.
I am closing issue for now but if you have additional questions feel free to ask.

Hi,
I tried four different Commits.
I see latest commit from 15 mins ago. Is that the one you want me to try now?
Get Outlook for iOShttps://aka.ms/o0ukef

From: sergei-pyshnoi @.>
Sent: Monday, March 25, 2024 2:31:37 AM
To: actions/runner-images @.>
Cc: vamshisiram @.>; Mention @.>
Subject: Re: [actions/runner-images] Windows 2022 - Build - Unable to resolve dependency dotnet 3.5 and packer (Issue #9552)
Hello @vamshisiramhttps://github.com/vamshisiram . Looks like problem was on 'choco' side. That's why checkout previous commits didnt helps. I tried to run manually on local machine choco install wixtoolsetand installation finished successfully. Please, checkout latest commit frommain` branch and try again.
I am closing issue for now but if you have additional questions feel free to ask.
—
Reply to this email directly, view it on GitHubhttps://github.com/actions/runner-images/issues/9552#issuecomment-2017572463, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVU36WQTYZPA5XHR5KV6EVLYZ7VHTAVCNFSM6AAAAABFGFIOYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJXGU3TENBWGM.
You are receiving this because you were mentioned.Message ID: @.***>

hey, the error you see is not really connected with the state of the repo, but rather state of choco package manager itself, so while we always encourage using the latest commit from main, if this specific problem is there the commit won't change this situation

Thanks for the clarification.
I first tried the latest commit from main and got the dotnet error.
I just downloaded the latest commit from main from you and trying that now. If it fails again I will let you know.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Mikhail Koliada @.>
Sent: Monday, March 25, 2024 12:03:42 PM
To: actions/runner-images @.>
Cc: vamshisiram @.>; Mention @.>
Subject: Re: [actions/runner-images] Windows 2022 - Build - Unable to resolve dependency dotnet 3.5 and packer (Issue #9552)
hey, the error you see is not really connected with the state of the repo, but rather state of choco package manager itself, so while we always encourage using the latest commit from main, if this specific problem is there the commit won't change this situation
—
Reply to this email directly, view it on GitHubhttps://github.com/actions/runner-images/issues/9552#issuecomment-2018705239, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVU36WSWBF5AH2FPNPXJGMLY2BYI5AVCNFSM6AAAAABFGFIOYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJYG4YDKMRTHE.
You are receiving this because you were mentioned.Message ID: @.***>

@mikhailkoliada the latest from main branch still fails with same error. So, you are saying that the CDN for chocolatey is having issues and we just have to try again until it succeeds, is that the right way to put this? please let me know.


Remember the rain

Song Name
Lost x do You remember the rain
Artist Name
Crim3s
Source
Direct file download
Youtube Link
No response
Direct File Link
No response
Song ID
945695
Start Offset [ms]
No response
Extra
Slaughterhouse

Accept
El dom, 22 de sep. de 2024 18:40, auto-nong[bot] @.***>
escribió:

Thanks for contributing!
Someone will soon review your request.
Here is the JSON result for the reviewer:
{
"name": "Lost x do You remember the rain",
"artist": "Crim3s",
"source": "host",
"startOffset": 0,
"url": "",
"songs": [
945695
]
}
To accept the request, a reviewer needs to write "accept".
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/4331#issuecomment-2366976600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BLO2R4NSNYDDXQRER2LU2D3ZX42M5AVCNFSM6AAAAABOU5CW5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHE3TMNRQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

reject
"Source
Direct file download" 🔥🔥 (theres literally no links in this entire issue)


Application Error #2800 when trying to delete not selected snippet

When trying to delete a not selected snippet it appears a message saying "Please select at least one snippet to process", after click the "OK" button, it appears an error message saying:
"Application Error #2800 Invalid form security token. This could be caused by a session timeout, or accidentally submitting the form twice.
Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section."
If you click the "Go back one page" button on the browser it redirects to a page where it says the document has expired, here the complete message:
"Document Expired
This document is no longer available.
The requested document is not available in Firefox’s cache.
As a security precaution, Firefox does not automatically re-request sensitive documents.
Click Try Again to re-request the document from the website."
If you click reload page or refresh it, you will see again the Application Error #2800, if you click "Go back one page" button on the browser it will redirect to the snippet list page (https://www.mantisbt.org/bugs/plugin.php?page=Snippets/snippet_list), then now if you click again "Go back one page" button now it will successfully reload the snippet list page.

Submitting this issue accordingly to this note from Mantis bug tracking system
https://mantisbt.org/bugs/view.php?id=32836

The 2800 error often occurs because the PHP garbage collection killed the session. This is a known problem with MantisBT, and unfortunately can't be controlled by the software - it requires changing php.ini settings.
For more information, please read the manual.
Unfortunately, I have not been able to reproduce this, even when forcing session expiration so I don't know what to tell you... I this consistently repeatable on your end ?

Closed due to lack of feedback. Feel free to reopen.


Remove MOSAIK from Variation Service input form

This recipe keeps failing, so removing this option for now.  Also need to update the Tutorial and User Guide correspondingly.

Dawen will update the service input form, Ron will update the User Guide and Tutorial.

The form has been updated and PR submitted.

Ron, this fix is on alpha, feel free to update the user guide and tutorial.

App deployed on alpha, and removed from p3_docs repo.

verified this on production.


[Python] Fix "indentation is not a multiple of four"

As discussed with @gribozavr in https://github.com/apple/swift/pull/1287#issuecomment-183413580

Rebased :-)

@swift-ci Please test

These files were just imported, there is no useful history to preserve.


Implement MonitoredResourceDescriptor methods and tests

Coverage increased (+0.02%) to 84.117% when pulling 5abb3aded8301839b5dd223ffb56621272f6decd on mziccard:logging-resource-descriptor into 0bcca695f9cd3bc5649a5fa5854631df67889bbf on GoogleCloudPlatform:logging-alpha.

/cc @lesv

LGTM


Add redisClustervCommand

Hi,
I'm going to create a c++ wrapper.Would you like to add APIs like redisvCommand in hiredis then I could pass the va_list.
thanks.

HI,
I'm so sorry just to see your question.
I just updated the cluster api, and add three functions:
redisClustervCommand()
redisClustervAppendCommand()
redisClustervAsyncCommand()
Try it.

Thank you very much.


Logo proposal

Hello, i am a graphic designer and i would love to contribute a logo to your project, for free. Please Let me know if i can go ahead.

bereket derneği

aygün emlak thanks you bro


Move close bracket to only notify on Sell orders

Dirty hack to only notify on sell orders.
Would like to see this implemented as a config option :)

This is implemented as a config option in the new version

Guess I should have upgraded first, then looked at merging my changes lol


RuntimeError: Error(s) in loading state_dict for SyncNet_color:

train syncnet after
when i use hq_wav2lip_sam_train.py --syncnet_checkpoint_path .\checkpoints\syncnet\syncnet_checkpoint_384_64_000012032_2024-01-19.pth
tell me this error
RuntimeError: Error(s) in loading state_dict for SyncNet_color:
Unexpected key(s) in state_dict: "face_encoder.20.conv_block.0.weight", "face_encoder.20.conv_block.0.bias", "face_encoder.20.conv_block.1.weight", "face_encoder.20.conv_block.1.bias", "face_encoder.20.conv_block.1.running_mean", "face_encoder.20.conv_block.1.running_var", "face_encoder.20.conv_block.1.num_batches_tracked", "face_encoder.21.conv_block.0.weight", "face_encoder.21.conv_block.0.bias", "face_encoder.21.conv_block.1.weight", "face_encoder.21.conv_block.1.bias", "face_encoder.21.conv_block.1.running_mean", "face_encoder.21.conv_block.1.running_var", "face_encoder.21.conv_block.1.num_batches_tracked".
size mismatch for face_encoder.0.conv_block.0.weight: copying a param with shape torch.Size([16, 15, 7, 7]) from checkpoint, the shape in current model is torch.Size([32, 15, 7, 7]).
size mismatch for face_encoder.0.conv_block.0.bias: copying a param with shape torch.Size([16]) from checkpoint, the shape in current model is torch.Size([32]).
size mismatch for face_encoder.0.conv_block.1.weight: copying a param with shape torch.Size([16]) from checkpoint, the shape in current model is torch.Size([32]).
size mismatch for face_encoder.0.conv_block.1.bias: copying a param with shape torch.Size([16]) from checkpoint, the shape in current model is torch.Size([32]).
size mismatch for face_encoder.0.conv_block.1.running_mean: copying a param with shape torch.Size([16]) from checkpoint, the shape in current model is torch.Size([32]).
size mismatch for face_encoder.0.conv_block.1.running_var: copying a param with shape torch.Size([16]) from checkpoint, the shape in current model is torch.Size([32]).
size mismatch for face_encoder.1.conv_block.0.weight: copying a param with shape torch.Size([32, 16, 5, 5]) from checkpoint, the shape in current model is torch.Size([64, 32, 5, 5]).
size mismatch for face_encoder.1.conv_block.0.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.1.conv_block.1.weight: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.1.conv_block.1.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.1.conv_block.1.running_mean: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.1.conv_block.1.running_var: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.2.conv_block.0.weight: copying a param with shape torch.Size([32, 32, 3, 3]) from checkpoint, the shape in current model is torch.Size([64, 64, 3, 3]).
size mismatch for face_encoder.2.conv_block.0.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.2.conv_block.1.weight: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.2.conv_block.1.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.2.conv_block.1.running_mean: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.2.conv_block.1.running_var: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.3.conv_block.0.weight: copying a param with shape torch.Size([32, 32, 3, 3]) from checkpoint, the shape in current model is torch.Size([64, 64, 3, 3]).
size mismatch for face_encoder.3.conv_block.0.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.3.conv_block.1.weight: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.3.conv_block.1.bias: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.3.conv_block.1.running_mean: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.3.conv_block.1.running_var: copying a param with shape torch.Size([32]) from checkpoint, the shape in current model is torch.Size([64]).
size mismatch for face_encoder.4.conv_block.0.weight: copying a param with shape torch.Size([64, 32, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 64, 3, 3]).
size mismatch for face_encoder.4.conv_block.0.bias: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.4.conv_block.1.weight: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.4.conv_block.1.bias: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.4.conv_block.1.running_mean: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.4.conv_block.1.running_var: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.5.conv_block.0.weight: copying a param with shape torch.Size([64, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 128, 3, 3]).
size mismatch for face_encoder.5.conv_block.0.bias: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.5.conv_block.1.weight: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.5.conv_block.1.bias: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.5.conv_block.1.running_mean: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.5.conv_block.1.running_var: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.6.conv_block.0.weight: copying a param with shape torch.Size([64, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 128, 3, 3]).
size mismatch for face_encoder.6.conv_block.0.bias: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.6.conv_block.1.weight: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.6.conv_block.1.bias: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.6.conv_block.1.running_mean: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.6.conv_block.1.running_var: copying a param with shape torch.Size([64]) from checkpoint, the shape in current model is torch.Size([128]).
size mismatch for face_encoder.7.conv_block.0.weight: copying a param with shape torch.Size([128, 64, 3, 3]) from checkpoint, the shape in current model is torch.Size([128, 128, 3, 3]).
size mismatch for face_encoder.8.conv_block.0.weight: copying a param with shape torch.Size([128, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 128, 3, 3]).
size mismatch for face_encoder.8.conv_block.0.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.8.conv_block.1.weight: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.8.conv_block.1.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.8.conv_block.1.running_mean: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.8.conv_block.1.running_var: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.9.conv_block.0.weight: copying a param with shape torch.Size([128, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 256, 3, 3]).
size mismatch for face_encoder.9.conv_block.0.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.9.conv_block.1.weight: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.9.conv_block.1.bias: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.9.conv_block.1.running_mean: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.9.conv_block.1.running_var: copying a param with shape torch.Size([128]) from checkpoint, the shape in current model is torch.Size([256]).
size mismatch for face_encoder.10.conv_block.0.weight: copying a param with shape torch.Size([256, 128, 3, 3]) from checkpoint, the shape in current model is torch.Size([256, 256, 3, 3]).
size mismatch for face_encoder.11.conv_block.0.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([512, 256, 3, 3]).
size mismatch for face_encoder.11.conv_block.0.bias: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.11.conv_block.1.weight: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.11.conv_block.1.bias: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.11.conv_block.1.running_mean: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.11.conv_block.1.running_var: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.12.conv_block.0.weight: copying a param with shape torch.Size([256, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([512, 512, 3, 3]).
size mismatch for face_encoder.12.conv_block.0.bias: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.12.conv_block.1.weight: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.12.conv_block.1.bias: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.12.conv_block.1.running_mean: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.12.conv_block.1.running_var: copying a param with shape torch.Size([256]) from checkpoint, the shape in current model is torch.Size([512]).
size mismatch for face_encoder.13.conv_block.0.weight: copying a param with shape torch.Size([512, 256, 3, 3]) from checkpoint, the shape in current model is torch.Size([512, 512, 3, 3]).
size mismatch for face_encoder.14.conv_block.0.weight: copying a param with shape torch.Size([512, 512, 3, 3]) from checkpoint, the shape in current model is torch.Size([1024, 512, 3, 3]).
size mismatch for face_encoder.14.conv_block.0.bias: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.14.conv_block.1.weight: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.14.conv_block.1.bias: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.14.conv_block.1.running_mean: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.14.conv_block.1.running_var: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.15.conv_block.0.weight: copying a param with shape torch.Size([512, 512, 3, 3]) from checkpoint, the shape in current model is torch.Size([1024, 1024, 3, 3]).
size mismatch for face_encoder.15.conv_block.0.bias: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.15.conv_block.1.weight: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.15.conv_block.1.bias: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.15.conv_block.1.running_mean: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.15.conv_block.1.running_var: copying a param with shape torch.Size([512]) from checkpoint, the shape in current model is torch.Size([1024]).
size mismatch for face_encoder.16.conv_block.0.weight: copying a param with shape torch.Size([1024, 512, 3, 3]) from checkpoint, the shape in current model is torch.Size([1024, 1024, 3, 3]).
size mismatch for face_encoder.19.conv_block.0.weight: copying a param with shape torch.Size([1024, 1024, 3, 3]) from checkpoint, the shape in current model is torch.Size([1024, 1024, 1, 1]).

is slove
change head import
from models import SyncNet_color_384 as SyncNet


Why is the cluster-autoscaler cmd option gone in 0.14.X?

Thanks for maintenance for great products 🙂
I'm trying to try 0.14.0-rc1 right now, but cluster-autoscaler cmd option is gone.
https://github.com/kubernetes-incubator/kube-aws/blob/v0.14.x/builtin/files/plugins/cluster-autoscaler/manifests/deployment.yaml
This option is in 0.12.x. Can you confirm..?
https://github.com/kubernetes-incubator/kube-aws/blob/v0.12.x/core/root/config/templates/cluster.yaml#L1366

The setting looks to be there in the controller-userdata file...
                    - ./cluster-autoscaler
                    - --v=4
                    - --stderrthreshold=info
                    - --cloud-provider=aws
                    - --skip-nodes-with-local-storage=false
                    - --skip-nodes-with-system-pods=false
                    - --expander=least-waste
                    - --node-group-auto-discovery=asg:tag=k8s.io/cluster-autoscaler/enabled,kubernetes.io/cluster/{{.ClusterName}}
                    {{- range $flag, $value := .Addons.ClusterAutoscaler.Options }}
                    - --{{ $flag }}={{ $value }}
                    {{- end }}

It's also there in the addons options config...
type ClusterAutoscalerSupport struct {
	Enabled          bool              `yaml:"enabled"`
	Options          map[string]string `yaml:"options"`
	ComputeResources ComputeResources  `yaml:"resources"`
	UnknownKeys      `yaml:",inline"`
}

Oh I see - right - you are comparing the new plugin to the old settings.  Both are still available so you can still use the old one.  It wouldn't be hard to add the setting to the plugin - do you care to raise a PR for it?

you are comparing the new plugin to the old settings.

Yes, I thought I was not able to use the old one...

Both are still available so you can still use the old one.

if old settings for cluster-autoscaler is available, so PR is unnecessary. Thank you for your consideration.


Gravity bug for RTL languages.

I know that Google recommend using END and START for gravity instead of LEFT and RIGHT, but actually there is a bug in some android versions that cause gravity fail setting when text is RTL.
So, could you please add LEFT and RIGHT Gravity to GravityEnum for RTL languages?
An image from android 4.1.1 on Genymotion emulator and device:

and this image same app and code when on android 4.4.4 on Genymotion emulator and device:

You can reproduce this bug, using this code :
                new MaterialDialog.Builder(MainActivity.this)
                        .titleGravity(GravityEnum.END)
                        .contentGravity(GravityEnum.END)
                        .title("چقدر عجله داری بابا!")
                        .content("این ویژگی در نسخه‌ی بعدی فعال خواهد شد! برو بعدن بیا!")
                        .positiveText("باشه. :(")
                        .negativeText("چه بهد")
                        .typeface("iran_sans_bold","iran_sans")
                        .callback(new MaterialDialog.ButtonCallback() {
                            @Override
                            public void onPositive(MaterialDialog dialog) {
                                Log.wtf("+","shod");
                            }

                            @Override
                            public void onNegative(MaterialDialog dialog) {
                                Log.wtf("-","shod");
                            }
                        })
                        .show();

and both images will be in opposite direction while using GravityEnum.Start.

Android 4.1 doesn't fully support RTL. It sounds like you want to work around this Android 4.1 limitation by using Gravity.END for RTL languages on 4.1 (which is exactly the same as RIGHT on 4.1) and Gravity.START on > 4.1.
Using Gravity.RIGHT everywhere would sacrifice non-RTL languages

Hmm, I thought 4.1 was the first API level to start full RTL support but
maybe I'm wrong. But yeah my intention was to not support explicit right
and left gravities since devs need to be conscious of RTL support these
days.
On Fri, Apr 10, 2015, 11:49 AM Kevin<EMAIL_ADDRESS>wrote:

Android 4.1 doesn't fully support RTL. It sounds like you want to work
around this Android 4.1 limitation by using Gravity.END for RTL languages
on 4.1 (which is exactly the same as RIGHT on 4.1) and Gravity.START on >
4.1.
Using Gravity.RIGHT everywhere would sacrifice non-RTL languages
—
Reply to this email directly or view it on GitHub
https://github.com/afollestad/material-dialogs/issues/434#issuecomment-91618092
.

But actually I had no difficulties for RTL texts in my apps since API 8 by using Right and Left Gravity (Except some HTC Models), but after android 4.0.0 , I haven't seen any problem in RTL Text, when using Left and Right Gravity. But now, I notices that using Gravity END and START does not work on some android distribution (and not only 4.1, I've seen this issue in a device with android 4.2 too)
So, what you guess is a good solution?
And by the way, it's so hard to be a developer in ME countries! Apart from RTL Problem, we also face date and currency conversion problem in different android version, other than sanction and ... :|

We fall back to left and right on old devices that don't support start and
end. The library automatically does this for you.
On Fri, Apr 10, 2015, 12:06 PM Reza Rg<EMAIL_ADDRESS>wrote:

But actually I had no difficulties for RTL texts in my apps since API 8 by
using Right and Left Gravity (Except some HTC Models), but after android
4.0.0 , I haven't seen any problem in RTL Text, when using Left and Right
Gravity. But now, I notices that using Gravity END and START does not work
on some android distribution (and not only 4.1, I've seen this issue in a
device with android 4.2 too)
So, what you guess is a good solution?
And by the way, it's so hard to be a developer in ME countries! Apart from
RTL Problem, we also face date and currency conversion problem in different
android version, other than sanction and ... :|
—
Reply to this email directly or view it on GitHub
https://github.com/afollestad/material-dialogs/issues/434#issuecomment-91623109
.

Great.
Waiting for update!
Thanks. :)

What? This is current behavior.
On Fri, Apr 10, 2015, 12:12 PM Reza Rg<EMAIL_ADDRESS>wrote:

Great.
Waiting for update!
Thanks. :)
—
Reply to this email directly or view it on GitHub
https://github.com/afollestad/material-dialogs/issues/434#issuecomment-91624716
.

I misunderstood your comment, and I thought a fix would be provided. So, the only solution is that myself add LEFT and RIGHT Gravity for my situation?

I read GravityEnum.java  and DialogInit.java  codes again, and I guess I found where the bug is.
As you mentioned the library automatically change END and START Gravity to RIGHT and LEFT based on if android version is lower than 4.2 or not using this code :
        private static final boolean HAS_RTL = Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN_MR1;

public int getGravityInt() {
    switch (this) {
        case START:
            return HAS_RTL ? Gravity.START : Gravity.LEFT;
        case CENTER:
            return Gravity.CENTER_HORIZONTAL;
        case END:
            return HAS_RTL ? Gravity.END : Gravity.RIGHT;
        default:
            throw new IllegalStateException("Invalid gravity constant");
    }
}

it should be working, but problem occurs in DialogInit.java  after setting Gravity, when trying to set text alignment using this code:
        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN_MR1) {
            //noinspection ResourceType
            dialog.content.setTextAlignment(builder.contentGravity.getTextAlignment());
        }

Why should set TextAlignment, when without it Gravity works fine for both RTL and LTR Languages?
For example, when text is RTL and Gravity is END in all version text should be on Right (and text is on right side before setting textAlignment), but after setting text alignment, text goes to Left side (which should not).
Right?

I also read this issue #256 and it seems you had problem with textAlignment before, I guess it's the same problem and revert using textAlignment would solve it! :)

resolve this problem?

@Reza-Rg
I wrote this code to solve the problem:
`
public static boolean isRTL() {
return isRTL(Locale.getDefault());
}
public static boolean isRTL(Locale locale) {
	final int directionality = Character.getDirectionality(locale.getDisplayName().charAt(0));
	return directionality == Character.DIRECTIONALITY_RIGHT_TO_LEFT ||
			directionality == Character.DIRECTIONALITY_RIGHT_TO_LEFT_ARABIC;
}
public void showLogoutDialog(){

	boolean HAS_RTL = Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN_MR1;

	GravityEnum dir,btnDir;

	if (HAS_RTL){
		if (isRTL()) {
			dir = GravityEnum.START;
			btnDir = GravityEnum.START;
		} else {
			dir = GravityEnum.START;
			btnDir = GravityEnum.END;
		}
	}else {
		dir = GravityEnum.END;
		btnDir = GravityEnum.END;
	}
	new MaterialDialog.Builder(this)
			.titleGravity(dir)
			.contentGravity(dir)
			.buttonsGravity(btnDir)

...
}
`


documentation

documentation

Coverage remained the same at 82.113% when pulling cad8432d751bd0ffadba48af4ef84855b035f885 on yanji1221:master into b38ac590f50780a274783f68167d86fa2e86cd5b on CS2103AUG2017-W10-B4:master.


Create an iPywidget for tracebacks

In Jupyter notebooks and lab, it might be useful to have a custom iPywidget to have all the information available in a collapsed form. This would allow to no longer recommend the "controversial" * import.

This presumable complements https://github.com/friendly-traceback/friendly/issues/3 which is suggests a simple collapsible heading that states the error message as the heading with the traceback folded beneath it with a more elaborate ipywidget. The ipywidget framework supports two way callbacks between Python and Javascript environments and as such can be used to implement simple applications. What might such  widget do / look like?
Perhaps related or useful to help guide thinking about what sorts of interaction or UI are possible are tools such as as nbtutor as well as notebook variable inspectors and debuggers?

What I have in mind is inspired by Thonny's assistant

However, the expandable elements would correspond to friendly's what(), where(), why(), as well as the traceback, all headed by the error message.  There would be no need of two-way communications: everything would be computed at once and presented in a collapsed state, ready for expansion.

I have implemented something which is not an iPywidget but works essentially as I was hoping it would. Unfortunately, it does not currently work with the dark theme and I cannot figure out why. More explanations can be found on a blog post I just published.

After reading (again) the documentation about ipywidgets, especially about installing them, I note the following:

Most of the time, installing ipywidgets automatically configures Jupyter ...

Users of friendly are generally not expected to be experienced. Installing friendly should "just work", not simply most of the time, but all the time.
So, I will continue to work on an html-based solution, and should explore how rich deals with jupyter in an attempt to create a more robust solution.

Other than for an extra (annoying) vertical space that I cannot seem to be able to get rid of, I am happy with the result shown on https://twitter.com/andre_roberge/status/1420733729497038848

Looks useful. My preference would be to reveal the text below, rather than above, the button. With text revealed above, the button moves, with text revealed below the button stays in the same place, (so in the latter case there is less distracting motion).

Ok, I am quite sure I can do this.

Closing this issue as I consider the implementation to be satisfactory.


[sailfish-crypto] Trigger collection unlock flow for crypto operations. Contributes to JB#40058

If a collection which contains a key is currently locked (due to the
unlock semantic being AccessRelock, for example), then if a client
attempts to use that key (e.g. to encrypt/decrypt/sign/verify) the
user should be prompted to unlock the collection in order to allow
the key to be retrieved in order to perform the operation.
This commit ensures that this occurs, where previously the operations
would have failed with a CollectionLocked error.
Contributes to JB#40058

The test for this is just the manual-test.sh script, as it creates keys in AccessRelock collections (thus when performing sign, verify, encrypt or decrypt steps with stored (or imported) keys, it should prompt the user to unlock the collection prior to performing those operations).

WIP, still fixing unit tests etc

This is now ready for review.

LGTM

I'd like to get @Venemo 's review as well.

It is a public holiday in Hungary today, so I don't think Venemo will be working.  We really cannot afford to delay this PR any longer... It is blocking j-doge's testing, and we need as much testing and validation as possible before the release...

Merging now, as per discussion on IRC.


The color of the title should change in bright theme

We can change the "Annoying Submit button" text color from yellow to something else as it is hard to see the text in a bright theme.
You can assign this to me. I can improve it.

Kindly assign it to me


Recommended reproduction command ignores arguments

When running the fuzzer with specific sanitizer, time or memory settings and an issue is found then the output for reproduction is not complete. In particular the recommended command line for reproducing the issue misses any of these parameters as well as the used cargo version. Abbreviated example below.
$ cargo +nightly fuzz run some_fuzzer -sanitizer=memory
# ...
SUMMARY: MemorySanitizer: use-of-uninitialized-value (...)
Exiting
# ...
Reproduce with:

    cargo fuzz run some_fuzzer fuzz/artifacts/parser/crash-hash

When it should instead print:
Reproduce with:

    cargo +nightly fuzz run some_fuzzer -sanitizer=memory fuzz/artifacts/parser/crash-hash

Thanks for reporting! Here's the code that needs to change:
https://github.com/rust-fuzz/cargo-fuzz/blob/2fb3bd85c0dd57ea7f3d5c29174c26a5550d0aa8/src/project.rs#L426-L436
We need to incorporate the arguments into the output.

Thanks for reporting! Here's the code that needs to change:
https://github.com/rust-fuzz/cargo-fuzz/blob/2fb3bd85c0dd57ea7f3d5c29174c26a5550d0aa8/src/project.rs#L426-L436
We need to incorporate the arguments into the output.

I think the things we actually need here are from the BuildOptions. args holds things like -runs but not which sanitizers were used.
Unsure so far how to get the +nightly bit, I'll take a closer look at that tomorrow.

+nightly comes from rustup wrapper, so I suspect its going to be out-of-scope for cargo-fuzz. But we can probably add a note to that effect? Like "note: if you're using rustup, you may need to specify +nightly to the cargo command".

That's probably the easiest way to do it.
Alternatively it looks like when you call rustup +toolchain <...> it sets the RUSTUP_TOOLCHAIN variable based on what your override was. I don't see that documented though so maybe we don't want to depend on that.


Best practice for operating on slices of data and keeping context

We currently receive a large JSON object that defines a list of steps, we validate them differently based on the type of step that is received, so we do multi-step JSON decoding with json.RawMessage and validation logic is different based on the type of field. So we didn't want to have to inline all the validation for every type.
The problem is that without inlining, with the current interface, we don't necessarily have a established method of passing context down, or adding context to the error messages. The comment for Error.Message indicates the intention of being able to say there is an issue with the 41st object in a slice of 100.
I can think of a few methods, wondering if anyone else had worked through this. We could utilize the context stored on req.Context.
var items []binding.Validator
for i, item := range items {
    errs = item.Validate(req, errs)
}

Thanks for any insight.

Can you provide a fuller example of your current approach and exactly what it is you want to be able to access from with the Validate method?

Important to note, the below does not currently make full use of the binding API to do the validation, but we're moving towards it.
type CreateEncodingProfile struct {
	Name          string        `json:"name"`
	TextTracks    []string      `json:"text_tracks"`
	Data          *EncodingData `json:"data" binding:"required"`
	DigitalRights Rights        `json:"digital_rights"`
	Type          string        `json:"type"`
	Locked        bool          `json:"locked"`
	Default       bool          `json:"-"`
}

Current Valid method
func (e *CreateEncodingProfile) Valid() (bool, Errors) {
	errs := Errors{}

	switch e.Name {
	case "":
		errs.Add([]string{"name"}, "invalid", "Profiles must have a name.")
	default:
		if !SafeNamingRegex.MatchString(e.Name) {
			errs.Add([]string{"name"}, "invalid", "Profile names must only contain alphanumeric characters, whitespace, and dashes.")
		}
	}

	errs = e.Data.Validate(nil, errs)

	if errs.Len() == 0 {
		return true, nil
	}

	return false, errs
}

Inside EncodingData is a EncodingVariant
// EncodingVariant is an object that represents a collection of renditions
// that all are related, and should be delivered together for adaptive playlists
type EncodingVariant struct {
	Name           string `json:"name"`
	ByteRange      bool   `json:"byte_range"`
	IFramePlaylist bool   `json:"iframe_playlist"`
	Renditions     []int  `json:"renditions"`
	Version        int    `json:"version"`
}

// Validate checks if this variant is able to be used
func (ev EncodingVariant) Validate(req *http.Request, errs Errors) Errors {
	switch ev.Name {
	case "":
		errs.Add([]string{"variant.name"}, "invalid", "Variants must have a name.")
	default:
		if !SafeNamingRegex.MatchString(ev.Name) {
			errs.Add([]string{"variant.name"}, "invalid", fmt.Sprintf("Variant names (%s) must only contain alphanumeric characters, whitespace, and dashes.", ev.Name))
		}
	}

	return errs
}

Right now, each of these objects have something that can uniquely identify them and we could change the field name to be like variant[variant.Name].name, but preferably, we would reference the index in the array of variants, so the name would be variant[1].name.
This particular object goes about one more layer deep, in that there is EncodingRendition, which contains both Audio and Video objects and a large portion of validation occurs there. Similarly in this case, where say a video setting is incorrect, we would want to backreference up the stack, rendition[1].video.width.
One solution would be to pull all the validation logic up onto the top-level CreateEncodingProfile call, but that would end up being an extremely large function, and not very composable, for example we would need to rewrite the entire function when handling PATCH requests, etc.
Thank you for any assistance, or in helping solve this context problem.

Add an unexported field on your type to hold the contextual values you need, and set its value before validating.

Thank you, that makes sense.


[e2e]: generic push main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/10626096602
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Fri Aug 30 03:06:39 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/10641899213
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Sat Aug 31 03:07:39 UTC 2024
Tests are passing now. Closing this issue.


BlueROV2 Sinks to Bottom of World

When I first implemented these files, the ROV fell right through the bottom of the world. After adding some collision to it, it now just sinks to the bottom of the world. I saw the other issue posted about needing to calculate the actual hydrodynamic parameters of the ROV. I am wondering if that has been done and someone has successfully got the ROV working in Gazebo, or if my problem may be stemming from something else.

Hi, there issue is that the underwater object plugin is incorrectly named:
diff --git a/bluerov2_description/robots/bluerov2_default.xacro b/bluerov2_description/robots/bluerov2_default.xacro
index e7e2c6c..8fd6a44 100644
--- a/bluerov2_description/robots/bluerov2_default.xacro
+++ b/bluerov2_description/robots/bluerov2_default.xacro
@@ -12,7 +12,7 @@

 <plugin name="uuv_plugin" filename="libunderwater_object_ros_plugin.so">

 <plugin name="uuv_plugin" filename="libuuv_underwater_object_ros_plugin.so">
   <fluid_density>1028.0</fluid_density>
   <flow_velocity_topic>hydrodynamics/current_velocity</flow_velocity_topic>
   <debug>$(arg debug)</debug>

Thank you for this suggestion. I have made these changes to the bluerov2_default.xacro file, but the same behavior seems to be happening. I have tried typing random letters into the filename to make it invalid, but the simulation runs anyway and just makes the bluerov2 sink. This makes me unsure of if the files are importing this plugin at all. Any other help would be appreciated.

If the plugin doesn't load, the robot will sink since there will be zero buoyancy to hold it up. Check your gazebo terminal log whether it is loaded correctly.


“Games” section is seen cropped on Dapps page when user access it from the Hamburger menu.

Frequency: 100%
Repro on build version: Android Internal Release Build V 1.25.2 , Android Alfajores build V.1.25.2, Test Flight Release Build V 1.25.2, Test flight Alfajores build V.1.25.2
Repro on devices: iPhone 7(13.3), Samsung Galaxy A8+(8), Google Pixel 2XL(11.0), iPhone 12(14.7.1)
Pre-condition:
1] User must have installed the application & completed the onboarding flow
2] User must be on the Homepage.
Repro Steps:
1] Tap on Hamburger menu and select the "Dapps" section.
2] Scroll down and observe.
Bug: “Games” section is seen cropped on the Dapps page when user access it from the Hamburger menu.
Expected Behavior: “Games” section should not be cropped on the Dapps page when user access it from the Hamburger menu.
Investigation:
1] Previously we were only able to see Ubeswap, Moola and Bidali, however we are able to see multiple other things as well.
2] NFTs section is seen blank.
Impact: Bad user impact.
Attachment: iOS behaviour.mp4
Android.jpg

@ValoraQA can you please retest 1.26.0 and close if no longer reproducible.

Hey @MuckT We have verified the above issue on latest Android Internal release build V:1.26.0 and latest iOS testflight release build V:1.26.0 and observed that issue is fixed.
Observation : Games section is not seen cropped and also all the categories are seen on Dapps page
Attachment : Dapps.mp4
Devices : iPhone 12(14.7.1) ,Google Pixel(11.0)
Thanks..!!


Prometheus cleanup steps do not remove StorageClass

We need to add that to the cleanup.

i update the lab and the clean up section in #998
tx


chore: Add github issue templates

Fixes #
Description
Copies over the same github issue templates used in github.com/aws/karpenter.
How was this change tested?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 76.388%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
5587

Relevant Lines:
7314

💛  - Coveralls


Make transport error simpler and just proxy for the source error

Motivation
Fixes #213
Solution
Makes the tonic::transport::Error type much simpler. It just forwards what's in the source error now. It was previously opaque anyway so a user of the library could not match on the ErrorKind or anything like that anyway.
However, this just solves the problem of the error not having redundant information in it. The library still uses a lot of opaque Box<dyn Error> internally. I personally think it would be nicer if tonic exposed a proper hyper::Error where the error comes from hyper etc. But I did not feel that was in scope for getting this part done.

This looks great! Thank you! Looks like you just need to run cargo fmt and CI will be happy :)


error tailwindcss [not found] when generating a controller

Works well for scaffolding, but breaks when generating views for just a controller
My setup:
rubRails 7.0.0.alpha2
ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux]

Also, when you hover on submit, mouse cursor does not change to pointer

Also it looks like <h1> tags don't work... other tags do

I have the same error error  tailwindcss [not found] when  generating a controller - the view is never created
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux]
Rails <IP_ADDRESS>

I am getting this error when generating view_component. I saw that @dixpac just pushed a fix that was merged an hour ago and so I tried updating to main but, I'm still seeing the error.
I created a bare minimum reproduction rails app with only the tailwindcss-rails and view_component here.

@rmontgomery429 version 0.2.1 solves this issue

I also got this issue when generating a "resource"
  create    app/controllers/<resource>_controller.rb
   error    tailwindcss [not found]

I am using 7.0.0.alpha2
ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin20]
tailwindcss-rails 0.5.0


Performance tuning

generate better sql:

Simplify (SELECT ... FROM foo as t0 WHERE ((True))) AS t0 to just foo AS t0
Simplfy policies like (SELECT True FROM foo AS t0t1 WHERE (t0.RID = t0t1.RID) AND (t0t1.x = 'x') LIMIT 1) to just t0.x = 'x'

just adding a note that the reason for this is that without these changes, postgres doesn't subset queries with group by / order by / limit until after doing all the left joins.

I think recent commits addressed these concerns (at least as well as we're going to be able to for now).


Use of internal package not allowed

When I try to test or run my app, I get the following error:
../../../github.com/awslabs/aws-xray-sdk-go/xray/segment.go:19:2: use of internal package not allowed
This is after simply getting the package, then adding it to a single endpoint:
http.Handle("/status/check", xray.Handler(xray.NewFixedSegmentNamer("IYFSlackBot"), http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
fmt.Fprint(w, "<p style="color:green;">Connection to Integrations API Healthy")
}))))

@mikkergimenez, thank you for reaching out to us about your question.  It seems like your provided example is similar to what we wrote in README and I was unable to reproduce your issue.

Hello luluzhao,
I believe this is related to the following line
https://github.com/aws/aws-xray-sdk-go/blob/master/xray/segment.go#L19
As go 1.4 seems to have added a rule about importing packages with the name internal:
https://stackoverflow.com/questions/41571946/internal-packages-in-go
https://golang.org/doc/go1.4#internalpackages
I'm not sure why others aren't experiencing this.  My addition of the xray Handler was pretty basic, I just included into an app that was using http as a status check endpoint.

@mikkergimenez , could you tell me which go version are you currently using?

Might want to check this issue out: https://github.com/aws/aws-sdk-go/issues/340


useResource and content-negociation

useResource fails to load my WebID profile at https://champin.net/#pa, because my server returns HTML unless an RDF content-type is explicitly requested.
If useResource is primarily used to feed the underlying dataset, then it should accept RDF content-types explicitly (currently, it seems to send accept: */*.
More generally (and regardless of the point above), it would be nice if UseResourceOptions provided a way to customize (at least some) HTTP headers, so that the accept header could be customized.

You were right, the headers were not "text/turtle," this should be fixed, though I did test it on your webId, and your webId doesn't seem to return link headers, so there's still a problem. I'll check to see if the Solid spec REQUIRES link headers.

Indeed, the accept header is now fixed, and (get/use)Resource("https://champin.net/") now gets turtle content in the response.
And indeed, this then creates an error about the absent link. This calls for a new issue :sweat_smile:

You actually don't need to return link headers under the Solid spec, so that's my bad. I've removed that requirement in https://github.com/o-development/ldo/pull/44


Pact consumer should give more relevant error message when failing to start mock provider.

Hi,
I thought it may be good to make the consumer throw relevant error messages when failing to start the mock provider. I had a case where I was unable to start up the mock provider due to port conflict, the error message thrown by the test however is something like:

java.lang.AssertionError: expected: but was:<Pact verification failed for the following reasons: The following requests were not received:

It took me a while to realize the actual problem as I thought the problem is related to the request/response itself.
IMHO, I think it would be good to throw more relevant error messages in this case, something like:
"Failed to initiate mock provider, root cause: could not bind port 2345" and etc, as it was a generic TCP level failure and has little to do with the actual pact verification. This will make troubleshooting much easier.
Cheers

With this change, you will now get:

Failed to start mock server: Address already in use
au.com.dius.pact.consumer.MockServerException: Failed to start mock server: Address already in use

This has been released with version 3.3.2


[BUG] Performance issues on very large folders

need to investigate this. is rather slow on folders with 10000+ files.

probably due to sha256 calculations on all those files. MD5 will not be used as it is considered collision prone by modern standards and provides very little . while it takes a little bit longer on large folder structures it is still considered safer to use sha256 and is normal behaviour especially with everything running in  a single tread / process

closing for now. will reopen and investigate this if the need arises


0.4.0 does not include relationships

Upgrading from 0.3.3 to 0.4.0 broke my acceptance tests that use objects with belongsTo relationships. My tests fail when trying to navigate through the belongsTo because the relationships were not included.  For example, with a bill model that has meter: belongsTo('meter'), bill.meter.id is undefined, because the meter relationship was not included in the response.
I tried Mirage Boilerplate Twiddle but got an alert that "The gist is missing or secret"
My bill model looks like this:
  meter: DS.belongsTo('meter'),
  initial: DS.attr('date),

My real API and Mirage 0.3.3 (_getResourceObjectForModel) return data like this:
{
    "type": "bill-summary",
    "attributes": {
        "initial": "2014-07-02"
    },
    "id": "4170595602188",
    "relationships": {
        "meter": {
            "data": {
                "type": "meter",
                "id": "1971049867684"
            }
        }
    }
}

With 0.4.0, there are no relationships included because _maybeAddRelationshipsToResourceObjectForModel includes them only if hasLinksForRelationship, alwaysIncludeLinkageData, or this._relationshipIsIncluded  Data returned by Mirage 0.4.0:
{
    "type":"bill-summary",
    "id":"1",
    "attributes": {
        "initial": "2014-07-02"
    }
}

My real API does not add links or include relationships for this model, and alwaysIncludeLinkageDatais defaults to false
I think this changed here: https://github.com/samselikoff/ember-cli-mirage/commit/ab87ac40747d1f46e8b5d6fa22bcfa133271a07f  I expect can work around this by setting alwaysIncludeLinkageData on every model with belongsTo relationships, but I'd rather that my Mirage API responses match my real API responses as much as possible.

I have it too. When I create a "foo" that has FK to "bar" then with 0.4.0 foo.bar will be undefined and tests will fail.
let bar = erver.create('bar', { name: 'A bar' });
server.create('foo', { slug: 'abc', bar });

I am seeing this as well. hasMany relationships seem to be included no problem, but only belongsTo relationships are failing to be included in responses.

I can confirm that @seansellek above fix works for me and I was able to get to 0.4.0.

I spent so many hours trying to fix the relationship issues and finally this thread saves my day!!
@seansellek solution is working from my side too!

I've addressed this in a blog post: http://www.ember-cli-mirage.com/blog/2018/02/01/changing-mirages-default-linkage-data-behavior/
and it was also added to the CHANGELOG.
Sorry again for the confusion + thanks for raising this issue everyone!

@samselikoff after further looking last night I was able to figure out my issue was related to a hasMany on a model with irregular pluralization https://github.com/samselikoff/ember-cli-mirage/issues/1258, maybe there's already a way to handle that?

@samselikoff Is the alwaysIncludeLinkageData property omitted from the serializer documentation by intent?
It is only mentioned in your blogpost. Took me a while to run into the blogpost in a serendipitous way, others might not be so lucky.

Nope it’s not, we need to document it. I’ve just fallen behind
On Sun, Jul 22, 2018 at 2:38 PM George van Vliet<EMAIL_ADDRESS>wrote:

@samselikoff https://github.com/samselikoff Is the
alwaysIncludeLinkageData property omitted from the serializer
documentation by intent?
It is only mentioned in your blogpost. Took me a while to run into the
blogpost in a serendipitous way, others might not be so lucky.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/samselikoff/ember-cli-mirage/issues/1204#issuecomment-406887445,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACyXCnmrEATV__4awfc_i7-f16n2lR6cks5uJMaMgaJpZM4QLUJA
.


VM Provisioning failing with following errors

VM provisioning is failing at the worker-1 VM with following errors. Deleted VM several times and got the same errors
worker-1: # Executing docker install script, commit: 26ff363bcf3b3f5a00498ac43694bf1c7d9ce16c
worker-1: +
worker-1: sh
worker-1:  -c
worker-1:  apt-get update -qq >/dev/null
worker-1: + sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
worker-1: + sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key add -qq - >/dev/null
worker-1: Warning: apt-key output should not be parsed (stdout is not a terminal)
worker-1: + sh -c echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable" > /etc/apt/sources.list.d/docker.list
worker-1: + sh -c apt-get update -qq >/dev/null
worker-1: +
worker-1: [ -n  ]
worker-1: + sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
worker-1: E
worker-1: :
worker-1: Failed to fetch https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/amd64/containerd.io_1.2.13-2_amd64.deb  Hash Sum mismatch
worker-1:    Hashes of expected file:
worker-1:     - SHA512:4261d170fe1962df2f73efffb5f438b93cd3cbd050f02a66171e55f2b323799814c4ecb464b582a28ace1a7fc5a3b3470643bfe718c1a72008a21462f79a6808
worker-1:     - SHA256:e5fd0f73fe2a83b0030af490ba5b26eec79483059a7ff7873c47948ff3fbb864
worker-1:     - SHA1:38cc415af5a03198a2f83bd49307ad329b45ff06 [weak]
worker-1:     - MD5Sum:84488c696235a78a5be963c13ed2aadf [weak]
worker-1:     - Filesize:21400958 [weak]
worker-1:    Hashes of received file:
worker-1:     - SHA512:5d410623bdc9f12117e89825fa596e649d643aec26414216beb7e21a3b537c81073eca77b77e9eed69e102e5eb44826847d16b0666d24a161ac13e7ecc929462
worker-1:     - SHA256:d756eaf0d64719b45948a568a7c4ea7bf2aa58d0e7d6b6b916cdaade9cb460a9
worker-1:     - SHA1:706524b05a70ee4c05ce9e06f087d85cda322cc4 [weak]
worker-1:     - MD5Sum:b4a4bcea3d5db295971aab9d6d4dfb2e [weak]
worker-1:     - Filesize:21400958 [weak]
worker-1:    Last modification reported: Fri, 15 May 2020 03:16:17 +0000
worker-1: E: Failed to fetch https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/amd64/docker-ce-cli_19.03.12~3-0~ubuntu-bionic_amd64.deb  Hash Sum mismatch
worker-1:    Hashes of expected file:
worker-1:     - SHA512:41bbdc739281b5bd0dca419f1947292094cb0adb855f039249ac20705ead259299635e00724a277de50fc0b84d69ba7a6cd8889cd6a5982749b707b0a592dc96
worker-1:     - SHA256:8764cce6b7d366d1c4bd2ddb8fa27081fa3626a1a545e288612019d968b61eef
worker-1:     - SHA1:0ba870c5ed1fc849b7bf6160380f40471ced6032 [weak]
worker-1:     - MD5Sum:5ffd2439e52efed2483e1e240a1a2765 [weak]
worker-1:     - Filesize:41183314 [weak]
worker-1:    Hashes of received file:
worker-1:     - SHA512:0824022dc997ec906a354ecc8e0a2865562e30f3c26c05624044439bf1b4b8a86443046b1d89771cefca0a0c607fea7b49cd2550bdd2b02ce5feb04757dfeb0c
worker-1:     - SHA256:6c643cfb73f27d98457e3101c41f9a82cb190472aba8056bd83c3d56c707f540
worker-1:     - SHA1:51dcf87ea90a17b3c463dcd5c6c2a5d602172137 [weak]
worker-1:     - MD5Sum:b40cef07a6c8e042ccee47b37256ccd8 [weak]
worker-1:     - Filesize:41183314 [weak]
worker-1:    Last modification reported: Tue, 23 Jun 2020 01:50:46 +0000
worker-1: E: Failed to fetch https://download.docker.com/linux/ubuntu/dists/bionic/pool/stable/amd64/docker-ce_19.03.12~3-0~ubuntu-bionic_amd64.deb  Hash Sum mismatch
worker-1:    Hashes of expected file:
worker-1:     - SHA512:b744c7401a7c4acf30a45bc9eec8fb8fded115c6c83eee808c5672d912b156dfad78e5439588e3db7bfcc7a66d47a1d346aa4797d1939734c19e6ce77bc6bef3
worker-1:     - SHA256:3faca0c8a8299d8f138354eebc9a3fd84fa07e1e7566632014716bc9ac3ca57c
worker-1:     - SHA1:09e0def531dafd8dad324a87c0dfe73a8e2a78b6 [weak]
worker-1:     - MD5Sum:bd4c9cabe06da80458e2850c4cb916ea [weak]
worker-1:     - Filesize:22530546 [weak]
worker-1:    Hashes of received file:
worker-1:     - SHA512:80375ff424d7efb9f1705c2cdd7efd8b712a3cba63ed7accedab40e432a85436546e5f66a6d258d0b39d5643d558fcf6cf1b05ca440699950a4973d3ade9e44e
worker-1:     - SHA256:d4bc58c10ea5c99b12a8a780f594550f13e029a612b4fd3de8c2c34a565be7d7
worker-1:     - SHA1:a83f7232c93cf0dc7c065ee40cc45b26804302f8 [weak]
worker-1:     - MD5Sum:cb43954ad4829657da56cad4c98f5b4c [weak]
worker-1:     - Filesize:22530546 [weak]
worker-1:    Last modification reported: Tue, 23 Jun 2020 01:50:46 +0000
worker-1: E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

@fekezue Which VirtualBox version do you use?
I'm using VirtualBox 6 it keeps crashing in Windows 10, then install VirtualBox 5 and it's work now.

Hi @fekezue  @misbahulard
Please try our new upgraded version of this which is upgraded to 1.24. Since 1.24 no longer uses docker as the CRI, all the above has been removed - along with other bugs fixed.
Please try it now with latest virtualbox and vagrant, and feel free to raise further issues.
Thanks.


feat: Celery support and asynchronous draft submission API

This rather large pull request adds support for Celery asynchronous task handling and uses this to implement an asynchronous draft submission API.
The new API has two endpoints. Most of it is in api_submission(), which is a refactored and slightly renamed api_submit(). The other piece is api_submission_status(), which provides a way to check whether a submission is still in the new validating state.
For development, docker containers for rabbitmq and the celery worker are started up alongside the app and db containers. The celery container is currently pulled from the github package repo under the painless-security fork, to be changed when this is merged. That docker image is based on the existing test image.

I've added instructions for deploying updates that should keep the container up to date. I've also added support for the "replaces" field, which resolves #3286.


data config, opportunity kfold

Kirils save_all_recordings, engine, printing, path
conf_matrix overrides not longer
invention DataConfig class: goal is, that we can change dataset, with one line and all functions work generic, same globals, choice of the right loading
Needed: Refactoring of Franz experiment on sonar data

what are the concrete consequences of this? maybe you can explain in daily tmr


Update dependencies

Updated Next.js in hopes of getting hot refresh for the next.config.js file. Unfortunately not one of the files they added this functionality to.
Short of that, everything seems to be working. Should be merge-safe.

{
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start -p $PORT"
},
"cacheDirectories": [
".next/cache"
],
"dependencies": {
"@helium/http": "^3.47.0",
"@supercharge/promise-pool": "^2.0.0",
"base-64": "^1.0.0",
"classnames": "^2.3.1",
"date-fns": "^2.25.0",
"ioredis": "^4.28.0",
"lodash": "^4.17.21",
"next": "^12.3.0",
"react": "^17.0.2",
"react-countdown": "^2.3.2",
"react-dom": "^17.0.2",
"react-qr-code": "^2.0.2",
"swr": "^1.0.1"
},
"devDependencies": {
"autoprefixer": "^10.2.6",
"dotenv": "^10.0.0",
"postcss": "^8.3.5",
"tailwindcss": "^2.2.4"
}
}

{
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start -p $PORT"
},
"cacheDirectories": [
".next/cache"
],
"dependencies": {
"@helium/http": "^3.47.0",
"@supercharge/promise-pool": "^2.0.0",
"base-64": "^1.0.0",
"classnames": "^2.3.1",
"date-fns": "^2.25.0",
"ioredis": "^4.28.0",
"lodash": "^4.17.21",
"next": "^12.3.0",
"react": "^17.0.2",
"react-countdown": "^2.3.2",
"react-dom": "^17.0.2",
"react-qr-code": "^2.0.2",
"swr": "^1.0.1"
},
"devDependencies": {
"autoprefixer": "^10.2.6",
"dotenv": "^10.0.0",
"postcss": "^8.3.5",
"tailwindcss": "^2.2.4"
}
}

Approve


Testing

This PR adds testing support for different testing dumps and adds some additional Frontend tests to progress #197. It solves #117.

Currently, all the tests were moved to an outer context/describe. Is there a way that github does not track these files for review?


Fix Fedora based image

SSIA

@pkubatrh Please review and merge.

otherwise lgtm

[test][test-openshift]

@pkubatrh For this repo there is still waiting invitation to @centos-ci user, so status from CentOS CI infrastructure can't be displayed in github PR UI.
Before I fixed your comment, CI was passing. Now the infrastructure has problems with allocating new machines, so currently CI fails.

CI is now passing, see:
https://ci.centos.org/view/SCLo-images/job/SCLo-container-devtoolset-rh-fedora/10/
https://ci.centos.org/view/SCLo-images/job/SCLo-container-devtoolset-rh/94/
https://ci.centos.org/view/SCLo-images/job/SCLo-container-devtoolset-rh-openshift/4/

lgtm, thanks!


Jailbreak success but screen unresponsive after jailbreak using tethered iOS downgrade without blob (sunst0rm)

can please check this problem?. for A10 ip7. however A9 & below worked well

That’s a sunst0rm issue, not a Taurine issue.


I need advise on PROFIT_THRESHOLD and AGE_THRESHOLD

are the configurations blow okay for 10 BNB Investment
"PROFIT_THRESHOLD": 0.20,
"AGE_THRESHOLD": 50,

PROFIT_THRESHOLD is expressed as a percent and therefore the base currency won't matter. Higher values will filter out more opportunities, and lower values will include less profitable trades. It's configurable to set as you see fit. Be sure to account for trading fees that will happen on each of the three trades involved.
AGE_THRESHOLD of 50 is good. You need to make sure you have a good enough connection (ping) to the exchange or a value so low will exclude all possible trades. Higher values are not really feasible because the market will have shifted too much since the calculations were done


Fix ruby warnings

It has been over a year. Would you please merge and release a fixed version?

We forgot about it. Currently tests are failing. We will release new version after we fix them.

Released 1.5.4 with fixed warnings


Share trip on global bulletin

Considerations:

probably involves making a new collection that stores ids of all shared trips
When trip is deleted, should cascade to this new collection
Should have a flag for enabling / disabling sharing to global?
Requires "anyone with the link can view" to be on

let's not do this bc it's not one of our goals anymore


useMsalAuthentication acquireTokenSilent logic fails if using prompt other than none

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.26.0
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
1.4.2
Description
This change (https://github.com/AzureAD/microsoft-authentication-library-for-js/pull/4280) introduced logic to the useMsalAuthentication hook that tries to call acquireTokenSilent.
It takes the authenticationRequest passed to the hook, with some minor logic surrounding scopes, and passed the resulting object to acquireTokenSilent.
acquireTokenSilent expects a SilentRequest (no prompt).
If a user is not passing in a prompt type of none, they will get an error. (https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-browser-v2.26.0/lib/msal-browser/src/interaction_client/SilentIframeClient.ts#L45)
Relevant code here: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/60c4aafa5/lib/msal-react/src/hooks/useMsalAuthentication.ts#L111
My initial thought here is to simply spread prompt: none into the argument for acquireTokenSilent.
Error Message
No response
Msal Logs
No response
MSAL Configuration
const config = {
  auth: {
    authority: `https://login.microsoftonline.com/${environment.msalTenant}`,
    clientId: environment.msalClientID
  },
  cache: {
    cacheLocation: "localStorage",
    storeAuthStateInCookie: true
  }
};

Relevant Code Snippets
const { error, login } = useMsalAuthentication(
    InteractionType.Redirect,
    {
      scopes,
      prompt: 'select_account'
    }
  )

Reproduction Steps

Call useMsalAuthentication hook with prompt not equal to none while logged in to an account.

Expected Behavior
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/msal-browser-v2.26.0/lib/msal-browser/src/interaction_client/SilentIframeClient.ts#L45 error is not thrown.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge, Safari, Internet Explorer
Regression
No response
Source
External (Customer)

Looking at this a bit more, really the issue comes down to casting PopupRequest|RedirectRequest|SsoSilentRequest to SilentRequest, and then for the fallback, passing login SilentRequest where PopupRequest|RedirectRequest|SsoSilentRequest is expected.

@ckeboss I've been unable to reproduce this error so far. Are you able to reproduce this behavior in one of our samples?

@jo-arroyo I can write a test for this if that helps?

@ckeboss Yes, that would be helpful, thank you.


Question: Why is pconsume always 0?

Hey,
thanks for writing this great addon. I do have a usability question: After exposing all relevant fields I always get 0 for psoncume. Is that as it should be? How would I get the correct current grid usage?
Cheers,
Matthias

I have figured it out, it was a misunderstanding from my part. The value was zero because there was no additional energy needed by the grid, because of my solar panels.


@fullcalendar not working

https://esm.sh/@fullcalendar/daygrid fails to load, you should check all @fullcalendar plugins though, I think it's because import css statement

@evromalarkey thanks, will fix it later

fixed: https://esm.sh/@fullcalendar/daygrid, built css: https://esm.sh/@fullcalendar/daygrid?css


Fix embedding documents containing named indexes

Q
A

Type
bug

BC Break
no

Fixed issues
fixes #1344

Summary
This fixes an issue when embedding a document containing a named index multiple times. Since the index had a name, this caused an exception with MongoDB since the index would already exist when creating it for the second embed use (see test case). With this change we're prefixing indexes pulled up from embedded documents with the name of the property that's embedding them. While this can cause exceptions when an index name becomes too long, the current solution gives more control to the user.
One option would be to add an indexPrefix option to embedded relationships and using that instead of the field name. Since that would be a new feature, I will not include it in the bugfix for 1.2.x.

could you please add it and note that indexes on embedded documents will have a prefix?

Yeah, prefix should be documented regardless of previous docs. I'll add a chapter later today.

Documentation added, mind taking another look @malarzm?

From what I remember maximum index name length in MongoDB should be 125 characters. It isn't specified in MongoDB docs, but is mentioned multiple times in MongoDB issue tracker (https://jira.mongodb.org/browse/DOCS-1820 for example) and on some other sites. I'd say mention of this limit might be added to that documentation note?
ODM might also check for index name length in the future?

From what I remember maximum index name length in MongoDB should be 125 characters. It isn't specified in MongoDB docs

The index name length documentation explains this in more detail:

Fully qualified index names, which includes the namespace and the dot separators (i.e. ..$), cannot be longer than 128 characters.

We can check this at schema creation, but I believe any attempt to truncate index names can just cause issues down the road, so I prefer if the original exception was shown to the user. As mentioned previously, I believe it’s more sensible allowing users to configure this index prefix in future versions than trying to add more magic to the prefix.

It'd be great to add name to the list of optional attributes

I somehow completely missed the fact that the name wasn’t in the options. This should indeed be properly documented. 👍

My intention would not be to truncate or otherwise transform the index name, but rather prevent the attempt to create such an index or wrap exception with Doctrine's own one with some helpful message about how it can be resolved, and maybe what field it was about.
But that is wayyy out of scope :) Thank you @alcaeus

@malarzm added a link to the indexes chapter to the annotation mapping, as the options are explained in more detail there. I've also added the note about index prefixing there so it won't get lost.
@Steveb-p let's fix the first issue - the reason I'm not really keen on doing too much with the exception is because either way, the user will be presented with a difficult problem: they have to either rename the index, the fields contained in the index path (as they are prefixed to the name), the collection name or even the database name.
Even without our exception, the error message provided by MongoDB will contain all necessary information:

namespace name generated from index name "doctrine_odm_tests.GH1344TooLongIndexName.$embedded1_this_is_a_really_long_name_that_will_cause_problems_for_whoever_tries_to_use_it_whether_in_an_embedded_field_or_not" is too long (127 byte max)

Regardless, I've added a test case to cover this case to make sure we're always giving users at least the index name.


Change game cancel command

Currently push the button 3 times to cancel the game.
But this operation is easy to mistake so it is better to change.
Candidates:

Press and hold 3 seconds
More times (5 or 6?)

Change to press and hold 3 seconds.
https://github.com/katsuster/target-6-client/commit/7ee1f15d4d00b6a83c10e036b44bd34cd4c055b3

Done.


local variable 'img_shape' referenced before assignment

When cfg.DATA_CONFIG.FOV_POINTS_ONLY is false, local variable 'img_shape' will be referenced before assignment in line 437 of kitti_dataset.py.

Thanks! It has been fixed in commit 826faec. By the way, please do not set FOV_POINTS_ONLY=False since the codes don't support this feature currently.


Don't wait forever for dead nodes to recover

After a brief timeout (~1-2 minutes), it should be assumed that a deadJournalNode/etc. is not coming back and that another one should be started elsewhere. Otherwise, a machine failure will cause the framework to hang.

@adam-mesos, can we close this with the latest PR since we are no longer hanging forever and have a timeout? Perhaps you can open a new PR related to removing the timeout entirely for datanodes.

Resolved by https://github.com/mesosphere/hdfs/pull/94


Document default SSH credentials for rancher/vm-centos

Could you please document the user id / passwd for the rancher/vm-* ?

This would be nice, I can't seem to find it either.
@SuhasAnand - Did you happen to find them?
Thanks,

@qrpike nope I ended up creating my own base image for centos.

Me also can't find them.
What about ubuntu vm? No credentials too or it has been specified somewhere?
Sorry for bad english :(

For Ubuntu its :  ubuntu/ubuntu

@SuhasAnand Thank you!

CentOS:
root / password

It's documented here


Bad error message while using kubectl expose service without specifying port

I tried to create a service from another service using kubectl expose, without specifying the port and here is the error message I got:
error: it is not possible to get ports from

The command I ran:
./cluster/kubectl.sh expose service frontend --name=frontend2

The error is expected since I didnt specify a port (which is required), but the error message can be better.

cc @bgrant0607

FWIW, creating a service from rc works without specifying the port (even tough it is required as per https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/user-guide/kubectl/kubectl_expose.md)
Running:
kubectl expose rc frontend

works fine.

Discussed with @bgrant0607 We should fix the error message in 1.0.
Later, we should allow "kubectl expose myservice --name=newservice" (without specifying port), but that will be post 1.0


Auto-stagger signed API updates to throttle API calls optimally

The pusher needs to call an API to get data, potentially once for every template for which signed data is being pushed. In the event that these calls are done concurrently, it's possible for the API to rate-limit or drop these. Currently, we have a rate limiting functionality in the pusher config to limit the number of such concurrent calls. This is not ideal because this is one more parameter to tune per API, and works by holding off on sending API calls.
Ideally, the pusher would automatically stagger its signed API updates over time, which means it would automatically rate limit in an optimal manner without necessarily holding back on sending any API calls as it does with rate limiting. The current config schema doesn't allow this. Consider the following config
"triggers": {
    "signedApiUpdates": [
      {
        "signedApiName": "localhost",
        "templateIds": [
          "0xcc35bd1800c06c12856a87311dd95bfcbb3add875844021d59a929d79f3c99bd"
        ],
        "fetchInterval": 5,
        "updateDelay": 0
      },
      {
        "signedApiName": "localhost",
        "templateIds": [
          "0x086130c54864b2129f8ac6d8d7ab819fa8181bbe676e35047b1bca4c31d51c66"
        ],
        "fetchInterval": 15,
        "updateDelay": 0
      },
      {
        "signedApiName": "localhost",
        "templateIds": [
          "0x1d65c1f1e127a41cebd2339f823d0290322c63f3044380cbac105db8e522ebb9"
        ],
        "fetchInterval": 15,
        "updateDelay": 0
      }
    ]
  }

Each item in triggers.signedApiUpdates requires an API call, and it's not obvious how one would auto-stagger three API calls of which one needs to happen every 5 seconds and two needs to happen every 15 seconds.
A simple yet non-complete solution would be to (remove rate limiting and) fuzz fetchInterval every time it is used so that concurrent API calls is a rare and unfortunate coincidence that we don't need to worry about.

A simple yet non-complete solution would be to (remove rate limiting and) fuzz fetchInterval every time it is used so that concurrent API calls is a rare and unfortunate coincidence that we don't need to worry about.

Yeah. I like that. I propose every to schedule the loop every fetchInterval + Math.random() * fetchInterval / 10 (add at maximum 10% delay).

A larger change would be to split the "data fetching" and "pushing" phase into two. This would be beneficial because data would need to be fetched only with one configuration (with the maximum frequency necessary). We would still do the pre/post processing trick to save RPC calls but there could be multiple "pushing" configurations created (e.g. with different delays) for the same template.

My main goal with the unified "Call API to get the data, push it to the signed API" flow was to avoid the slack caused by two separate loops. We want to do <=1 second lag (not for Airseeker but for the pull oracle use case). When you have two loops with a fetch interval of 1 second and update interval of 1 second, the mean lag will be 1.5 seconds, which is a big hit.
This is not easily doable in Airseeker which needs to support multiple providers/chains (and we don't care about the additional lag all that much), so that has two loops.

Yeah, the two loops will suffer this problem if they are disjoint. A possibility would be to have a "middle ground" where we would fetch endpoint data with maximum frequency, but trigger the updates directly (we can easily check if a particular signedApiUpdates wants to push the data).
That said, this is out of scope of that issue. The benefit is more optimized data provider calls, which might be worth it but I think we should continue discussion in a separate issue.

Created https://github.com/api3dao/signed-api/issues/110 because this issue will be closed by the respective (linked) PR.


Chess: Move A2 to A3

Please do not change the title. Just click "Submit new issue". You don't need to do anything else :D

@BengalPirate done! Successfully played move a2a3 for current game.
Thanks for playing!