ValueError: setting an array element with a sequence.

While trying to train on my own data, I'm encountering some issues. I was able to trace back most, but am now stuck with the error below. Any suggestions on what might be the cause? Some sub-epochs run fine, while others crash. I'm still trying to find out if there is a correlation with specific scans/patients..
Images for subject loaded.
From current subject #19 extracting that many Segments centered on : Foreground=25 Background:25
End of the function that extracts segments. Segments extracted centered on: Foreground=25 Background=25
TIMING: Extracting all the Segments for next Training took time: 179.138042(s)
:=:=:=:=:=:=:=:=: Finished extracting Segments from the images for next Training. :=:=:=:=:=:=:=:=:
Loading Training data for subepoch #23 on shared variable...
Traceback (most recent call last):
  File "deepMedicRun", line 102, in <module>
    deepMedicTrain.deepMedicTrainMain(absPathToTrainConf, absPathToCnnModelGivenInCmdLine, cnnInstanceLoaded, filenameAndPathWhereNewlyCreatedModelWasSaved)
  File "/theano/deepmedic/deepmedic/frontEndModules/deepMedicTrain.py", line 440, in deepMedicTrainMain
    do_training(*trainSessionParameters.getTupleForCnnTraining())
  File "/theano/deepmedic/deepmedic/trainValidateTestVisualiseParallel.py", line 1311, in do_training
    arrayLesionLabelsForPATCHESOfTheImagePartsInGpUForSubepochTraining = np.asarray(lesionLabelsForPATCHESOfTheImagePartsInGpUForSubepochTraining, dtype='float32')
  File "/usr/lib/python2.7/dist-packages/numpy/core/numeric.py", line 460, in asarray
    return array(a, dtype, copy=False, order=order)
ValueError: setting an array element with a sequence.

p.s. Thanks a lot for sharing this tool, first results look very promising!

Hi Roelant,
Sorry for this. Seems like I should place some checks in these functions to start giving users some appropriate error messages. The functions are improved in some piece of code that I have somewhere, but merging will take some time as I need to do it controllably :-/
Could you please email me the trainingSession.txt log file? It will help me debug this. Please email it at<EMAIL_ADDRESS>In the mean time, please make sure that the ground-truth-labels for the subjects that break it do not have different dimensions (I do not remember for sure how it would behave if eg the nii for labels is 4-dimensional, with the 4th dimension empty. Which happens quite often in some people's niis.) and that the ground truth labels have values: 0,1,2,3...,Nclasses, without any values exceeding the Nclasses.
I suspect it could be the first case, with a 4-dimensional nii.
Thanks a lot for the feedback, keep me updated!
Kostas

Hi Kostas,
Thanks for your quick reply and suggestions, I'm going to look into your suggestions for the scans I've already excluded because of issues during loading.
After spending another evening hunting "the scan/segmentation to blame" and experiencing no crashes while training on small chunks of the dataset, I decided to try and run training on the entire dataset(~300 cases at this time) again. It's currently starting epoch 3 without any issues.. I'm not sure what has changed, but it seems to be working (for) now! Maybe it just ran out of memory or something like that. It's nice to have a multi-threaded implementation, but it can make debugging a bit more challenging.
Sorry for having bothered you with my frustrations. If it crashes again I'll sent you the log and config files.
Kind regards, keep up the good work!
Roelant


Discussion: Deprecate Forseti installer wizard

This issue is to gather discussion on a proposal to deprecate the existing Forseti installer in favor of the Terraform module.
The full proposal is captured in this document.

I think it's more efficient to standardize on terraform;
If we just use Terraform, would would we still have a path to offer a push button deployment from Google Cloud Marketplace?

If we just use Terraform, would we still have a path to offer a push button deployment from Google Cloud Marketplace?

I don't believe it's currently possible to install from the Marketplace with either installer, but it's something we could explore in the future.

Is GCP deprecating deployment-manager in favor of terraform generally?  As an enterprise customer, with my account team and Google Professional Services telling me to use Forseti, creating additional pre-reqs to installing and managing the tool is not very appealing.
(i don't have access to the document so only have the info in this issue.)

@nbards There are not plans to deprecate DM across the board, but maintaining two different installers is a substantial operational burden.
That being said, before deprecating the DM installer we plan to build a guided install experience in Cloud Shell (w/ Terraform pre-reqs installed) available—would that address your concerns?

@morgante I understand that.  I have substantial operational burdens using forseti in my enterprise, too.  Glad to discuss.  I'm happy to participate, and trial the "guided install experience".
Since Google is telling me as a paying customer to use forseti, who from Google could participate in the discussion as well?

@nbards Once we have the guided install, I'm happy to trial it with you. (I work at Google.)

Forseti has fully moved over to Terraform, no longer support DM.


Cordic api modify

Sorry for I wrong closed the PR, and I can not reopen it.

https://github.com/apache/nuttx/pull/10282
@raiden00pl @xiaoxiang781216

Response from the old PR https://github.com/apache/nuttx/pull/10282#issuecomment-1685518888

Yes, the numerical type for q1.15 is as a default here. I do this, because if I open for MATH_FFT, then math.c is compiled, so cordic.h is included and CONFIG_MATH_CORDIC_USE_Q31 is needed for cordic_num_t to be configed even in this case I don't need to care about cordic. So, CONFIG_MATH_CORDIC_USE_Q31 is "redundant" here, or a default cordic_num_t definition is need. And I remove it as a default one.

If you don't need cordic, then why just not guard all cordic logic with #ifdef CONFIG_MATH_CORDIC ? The same applies to the FFT.

Response from the old PR #10282 (comment)

Yes, the numerical type for q1.15 is as a default here. I do this, because if I open for MATH_FFT, then math.c is compiled, so cordic.h is included and CONFIG_MATH_CORDIC_USE_Q31 is needed for cordic_num_t to be configed even in this case I don't need to care about cordic. So, CONFIG_MATH_CORDIC_USE_Q31 is "redundant" here, or a default cordic_num_t definition is need. And I remove it as a default one.

If you don't need cordic, then why just not guard all cordic logic with #ifdef CONFIG_MATH_CORDIC ? The same applies to the FFT.

understood

squash the two commits into one.

please add commit message

Sorry for miss understanding, I have submmit two commits, and the first one is discarded. No more commit message needed.

@raiden00pl could you review again?


Bug: programmatically changing the log level fails

Expected Behaviour
When changing the log level of a Logger via code, the log level should be changed.
from aws_lambda_powertools import Logger
powertools_logger = Logger()
powertools_logger.setLevel("DEBUG")    # the log level should become DEBUG
powertools_logger.debug("Hello, world!")    # this should produce a log message

Current Behaviour
When changing the log level of a Logger via code, the log level is not changed.
from aws_lambda_powertools import Logger
powertools_logger = Logger()
powertools_logger.setLevel("DEBUG")    # the log level remains at the default, INFO
powertools_logger.debug("Hello, world!")    # no log message comes out

Code snippet
See above, also the linked repo below

Possible Solution
No response
Steps to Reproduce
See https://github.com/paulsuh/aws-powertools-logging-test-sam for detailed test cases and output.
AWS Lambda Powertools for Python version
latest
AWS Lambda function runtime
3.9
Packaging format used
Serverless Application Repository (SAR) App
Debugging logs
No response

Hey Paul, thank you so much for reporting this — could you tell me if
setting the log_level attribute to debug works?
powertools_logger.log_level = logging.DEBUG
If it does work, I suspect setLevel is changing the superclass and not
._logger as it should be.
Thanks a lot taking the time to report it, we should fix it — we welcome a
PR if you know your way around Python logging (logger.py file)
On Mon, 22 May 2023 at 19:52, boring-cyborg[bot] @.***>
wrote:

Thanks for opening your first issue here! We'll come back to you as soon
as we can.
In the meantime, check out the #python channel on our AWS Lambda
Powertools Discord: Invite link https://discord.gg/B8zZKbbyET
—
Reply to this email directly, view it on GitHub
https://github.com/awslabs/aws-lambda-powertools-python/issues/2303#issuecomment-1557649168,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZPQBGFL6I4NBC6OIV466TXHORWXANCNFSM6AAAAAAYKYVODM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Hi @heitorlessa and @paulsuh! I could reproduce the error and it's changing the superclass logging.Logger instead of changing the Powertools instance: ._logger in this case.
 If not, I can send the PR to fix this and give you the credits.
Thank you

Let me clone the repo and see what I can do

Hello @paulsuh! Can I help you write this fix? We are planning to release a new version today or tomorrow and it would be nice if we could include this fix.
No pressure here, we know everyone is busy with different things at work, I'm really here to offer help or even just write this and discuss the solution together when sending the PR.
Thank you so much!


kubectl completion takes 5s if default context is unreachable

What happened:
Each time I open a shell on macOS 12.4, it takes at least 5s (just for kubectl completion)
What you expected to happen:
New terminals should open quickly
How to reproduce it (as minimally and precisely as possible):

Set up a GKE kubernetes
Add a firewall rule that blocks access to the control plane from the internet (or at least where the user will be running kubectl completion ...)
Run time kubectl completion bash (or some other shell, the precise shell doesn't matter)

Here, I have a default context pointing to a GKE instance with a firewall that prevents me from accessing it:
time kubectl completion bash > /dev/null
I0724 10:21:38.912741   90049 versioner.go:56] Remote kubernetes server unreachable
kubectl completion bash > /dev/null  0.45s user 0.27s system 14% cpu 5.128 total

For reference, if I set the default context pointing to a localhost (rancher) that is running but isn't running Kubernetes, it's fast:
time kubectl completion bash > /dev/null
I0724 10:20:30.971567   90042 versioner.go:58] Get https://<IP_ADDRESS>:6443/version?timeout=5s: dial tcp <IP_ADDRESS>:6443: connect: connection refused
kubectl completion bash > /dev/null  0.08s user 0.06s system 60% cpu 0.242 total

Anything else we need to know?:
It's ok for commands beneath kubectl x to talk to the current context to get extra bits as part of dynamic completion, but it isn't ok to wait a full 5s as part of kubectl completion bash or similar.
Note that the times are equivalent for:
% time kubectl completion powershell > /dev/null
I0724 10:23:33.190086   90158 versioner.go:56] Remote kubernetes server unreachable
kubectl completion powershell > /dev/null  0.44s user 0.27s system 13% cpu 5.230 total
% time kubectl completion zsh > /dev/null
I0724 10:23:58.093916   90257 versioner.go:56] Remote kubernetes server unreachable
W0724 10:23:58.095636   90257 transport.go:243] Unable to cancel request for *exec.roundTripper
kubectl completion zsh > /dev/null  0.45s user 0.28s system 13% cpu 5.224 total

Environment:

Kubernetes client and server versions (use kubectl version):

% time kubectl version
I0724 10:25:22.618328   90555 versioner.go:56] Remote kubernetes server unreachable
W0724 10:25:22.619033   90555 transport.go:243] Unable to cancel request for *exec.roundTripper
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.1", GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", GitTreeState:"clean", BuildDate:"2022-05-24T12:26:19Z", GoVersion:"go1.18.2", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.4
Unable to connect to the server: dial tcp ...:443: i/o timeout
kubectl version  0.79s user 0.46s system 3% cpu 35.807 total

Cloud provider or hardware configuration: GKE (I suppose?) + Firewall blocking access from my client IP
OS (e.g: cat /etc/os-release): 12.4 (21F79)

See my response in https://github.com/kubernetes/kubectl/issues/1248#issuecomment-1218291893 for the "why".
But I think this one may be something we can fix. My guess is that kubectl completion is triggering discovery which we should skip for this command.
/triage accepted
/priority backlog

The point that I don't understand in this case;
kubectl completion command does not send any request to apiserver and even does not use discovery https://github.com/kubernetes/kubernetes/blob/67e692d521a5904aaaea446fd1642d2696cab61f/staging/src/k8s.io/kubectl/pkg/cmd/completion/completion.go#L147
@jsoref  What is the output of; kubectl completion bash --v=99?

I wonder if this has something to do with the GKE auth plugin.
@jsoref what happens if you run your completion command, specifying a context that doesn't exist, like this?
time kubectl completion bash --context=foo

It should not make a difference since it is not supposed to communicate with the server, but I am curious what would happen in your case.
Also, this is strange:
I0724 10:21:38.912741   90049 versioner.go:56] Remote kubernetes server unreachable

I can't find any file called versioner.go.  I wonder if that is coming from the GKE auth plugin?

Here's a hit for it:
https://github.com/flavio/kuberlr/blob/a68d3cba285076ac6febb24037dc33ba693fa689/internal/finder/versioner.go#L56

Ok, sorry, so, this isn't a problem in kubectl, it's a problem w/ https://github.com/flavio/kuberlr...

Still, I am curious why kubectl feels like authentication needs to occur in order for completions to be generated 🤔


Add CustomData Property to SessionEventArgs

Doneness:

[x] Build is okay - I made sure that this change is building successfully.
[x] No Bugs - I made sure that this change is working properly as expected. It does'nt have any bugs that you are aware of.
[x] Branching - If this is not a hotfix, I am making this request against release branch (aka beta branch)

Allows state only known in BeforeRequest to be passed to BeforeResponse
Only red test was red before the change

I don't like having a property for this here. That's more of a developer problem.
We already have a Request Id property which can be used to do the same. Create a dictionary<Guid, object> using the Request Guid to share things across requests. I will add code to test project to demonstrate the same.

https://github.com/justcoding121/Titanium-Web-Proxy/blob/release/Examples/Titanium.Web.Proxy.Examples.Basic/ProxyTestController.cs#L126
Added example

Alright, fair enough. Didn't realise about the Request Id. Thanks


Provide fault-tolerant parsing (GH-3303)

Yeah, examples like this make it seem appealing to really improve the parser itself, rather than catching arbitrary errors.

Yeah, examples like this make it seem appealing to really improve the parser itself, rather than catching arbitrary errors.

The problem here is just that we have to guess the errors (and then we can handle it), so, if there's something we didn't anticipate, it'd break and provide nothing at all (which is far from ideal from an IDE perspective dealing with the AST).
Still, if this is an approach that you're comfortable with, it's definitely already better than never providing anything for any case.

Ok, I've tackled some more cases (so, it's ready to re-review).


do you have any progress?

Hi!
The code for the hybrid reconstruction is being written into this project, https://gitlab.lrz.de/IP/elsa
Some progress is made public in this MR, https://gitlab.lrz.de/IP/elsa/-/merge_requests/220
If this addresses the issue, feel free to close it.


Does not take effect without re-enabling

The package doesn't work on startup; I have to disable and re-enable it.

is the tree-view open on startup?

No, it is not for me.

+1
Works fine only for project folder.
If close/open other folders, tree width does not reduce.
Nice package, anyway
Thanks

@mlaco hi, this is still an issue for you?

It work now, thank you!


[Bug] Dial timepicker when input is empty

steps to reproduce:

open https://dhutaryan.github.io/ngx-mat-timepicker/
clear input in "Dial timepicker (24h format)"
open dial timepicker
click OK without changing anything

expected behaviour:
I expect the input will change to 8:41, but it is empty

"Input timepicker (24h format)" works as expected

Fixed: v16.0.1, v15.0.2


GPL-678 Verify PWGS pipeline model and backlog items and thier acceptance criteria

Description
GPL-678 | As a development team we need to understand the PWGS pipeline & check 3 backlog items and acceptance criteria
Who the primary contacts are for this work
Lesley S (NB anybody else as Lesley is also involved with Beckman?)
Knowledge or Stake holders
Additional context or information
Confluence doc: https://ssg-confluence.internal.sanger.ac.uk/x/W4meBg (includes process map)

Updated descriptions and added comments to following stories:

https://github.com/sanger/limber/issues/518
https://github.com/sanger/sequencescape/issues/2934
https://github.com/sanger/sequencescape/issues/2935

Closing as appears to be done.


[devtools] What's New In DevTools (Chrome 87)

Target Live Date: 2020-10-01

[x] This has been reviewed and approved by (@chybie )
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 27 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/10/devtools.md#L224 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/10/devtools.md#L24 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L26 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L35 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L41 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L45 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L52 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L54 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L58 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L73 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L87 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L96 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L103 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L108 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L117 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L143 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L147 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L160 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L169 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L186 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L191 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L195 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L204 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L209 - Line must be at most 100 characters

Whoops!
There were 43 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/10/devtools.md#L7 - Unknown tag 'chrome7' found, use an existing tag, or add it to 'src/data/commonTags.json'.
src/content/en/updates/2020/10/devtools.md#L224 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/10/devtools.md#L24 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L26 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L35 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L41 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L45 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L52 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L54 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L58 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L73 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L87 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L96 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L103 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L108 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L117 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L143 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L147 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L160 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L169 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L186 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L191 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L195 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L204 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L209 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L313 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L28 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L45 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L23 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L23 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L159 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L184 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L185 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L192 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L193 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L197 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L203 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L203 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L30 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/_shared/discover.md#L167 - Line must be at most 100 characters

Whoops!
There were 42 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/10/devtools.md#L7 - Unknown tag 'chrome7' found, use an existing tag, or add it to 'src/data/commonTags.json'.
src/content/en/updates/2020/10/devtools.md#L220 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/10/devtools.md#L24 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L26 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L35 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L41 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L45 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L52 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L54 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L58 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L73 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L87 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L96 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L104 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L113 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L127 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L139 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L143 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L156 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L165 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L182 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L187 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L191 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L200 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L205 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L313 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L28 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L45 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L23 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L23 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L159 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L184 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L185 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L192 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L193 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L197 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L203 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L203 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L30 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/_shared/discover.md#L167 - Line must be at most 100 characters

Whoops!
There were 43 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2020/10/devtools.md#L7 - Unknown tag 'chrome7' found, use an existing tag, or add it to 'src/data/commonTags.json'.
src/content/en/updates/2020/10/devtools.md#L220 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/10/devtools.md#L24 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L26 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L35 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L41 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L45 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L52 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L54 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L58 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L73 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L87 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L96 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L104 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L113 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L127 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L139 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L143 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L156 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L165 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L182 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L187 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L191 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L200 - Line must be at most 100 characters
src/content/en/updates/2020/10/devtools.md#L205 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L313 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L28 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L45 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L23 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L23 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L159 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L184 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L185 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L192 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L193 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L197 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L203 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L203 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L30 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/_shared/discover.md#L167 - Line must be at most 100 characters
src/content/en/updates/images/2020/10/devtools/07-lighthouse.png - Try to keep files below 500K, was 713K


Pass Frigate+ sublabel (amazon, fedex, ups) to HomeAssistant and add USPS

Is your feature request related to a problem? Please describe.
I would like to create alarms based on the sublabel of car. E.g. create an alert when Amazon arrives. Also, it'd be great to have USPS added as a sublabel.
Describe the solution you'd like
I would like to have an entity image.frontdoor_car_amazon, ceteris paribus for the other delivery services, on top of the standard image.frontdoor_car.
Describe alternatives you've considered
NA
Additional context
NA

This is covered by https://github.com/blakeblackshear/frigate/issues/8229

This is for creating sensors related to sublabels in homeassistant.


ISB001 misfires on proxy fields that are disposed

        private ITerminalService terminalService;

        protected override void Dispose(bool disposing)
        {
            base.Dispose(disposing);
            foreach (var token in profferTokens)
                token?.Dispose();

            this.serviceBrokerClient?.Dispose();
            (this.terminalService as IDisposable)?.Dispose();
        }

The field is disposed, but the analyzer still emits this:
error ISB001: The proxy stored in "LinuxConnectionManagerPackage.terminalService" must be disposed by an IDisposable.Dispose or Dispose(bool) method on the "LinuxConnectionManagerPackage" type.

Luca also reported:
I hit this as well, had to explicitly suppress this warning in code, e.g.:
    internal class RenameRefactorCommand : IVsPreviewChangesEngine, IDisposable
    {
        line110: private readonly Microsoft.VisualStudio.Threading.AsyncLazy<ServiceBrokerClient> serviceBrokerClientLazy;

        void IDisposable.Dispose()
        {
            this.serviceBrokerClientLazy.DisposeValue();
        }
    }

C:\vs\src\vc\designtime\Managed\Rename.cs(110,90): error ISB001: The proxy stored in "RenameRefactorCommand.serviceBrokerClientLazy" must be disposed by an IDisposable.Dispose or Dispose(bool) method on the "RenameRefactorCommand" type. (https://github.com/microsoft/vs-servicehub/blob/3423437139210283925dbc2462d5637c9abad978/doc/analyzers/ISB001.md) [C:\vs\src\vc\designtime\Managed\dtmanaged_21vxelbh_wpftmp.csproj]


feat(a11y): add additional accessibility attributes on the contenteditable

This gives the editor a multiline textbox role, see https://www.w3.org/TR/wai-aria-1.1/#textbox.
It also allows specifying to additional view options (id and ariaLabeledBy) so that users can programmatically associate the editor box with its label or other elements.
For reference, this is necessary to fix item 726108 in the accessibility audit (WARP-71).
This PR does not include unit tests since the added functionality is just about modifying DOM elements. It does include e2e tests however.
I've added to additional view options, id and ariaLabeledby, but I'm also open to changing that to something like a generic attributes option if you prefer that.

I liked your suggestion of being able to set arbitrary attributes, so I went ahead and implemented that
in 8220dd6a3a317578b574a800f8b3dfbb65a0beb4 (to shorten back-and-forth comms here). You can use it via options.elementAttributes as follows:
new StacksEditor(..., {
    // ...
    elementAttributes: {
        id: "foo",
        ariaLabeledby: "bar",
    }
})

Please let me know if this is not a solution for your intended use case. Closing as implemented.

@balpha Ah, agreed on those a11y attributes. I forgot to do those in that commit - I'll add them in a separate commit today.

a11y attributes added in a3631201099c528b3995fed1df34577b96b042fe. Thanks for the reminder!


metric "certmanager_certificate_expiration_timestamp_seconds" is not exposed anymore in 0.11

Describe the bug:
After upgrading to 0.11 ( from 0.8 ) the metric certmanager_certificate_expiration_timestamp_seconds is not available anymore in prometheus .
Querying the /metrics url does not show it either
I can see the new certmanager_certificate_ready_status one
Expected behaviour:
Looking at the code here the metric should still be there
Steps to reproduce the bug:
Upgrade to 0.11 and curl on :9402/metrics
check if the the expiration timestamp is there
Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.10.2): 1.13.7
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): 0.11.0
Install method (e.g. helm or static manifests): static manifests

/kind bug

Looking at bit more at the code it seems to me that this metric was forgotten while upgrading to the new API
I can't see any reference to UpdateCertificateExpiry ever being called. Before it was called as part of the sync loop here
Compared to the UpdateCertificateStatus which is indeed caliing during sync.

Looks like this commit removes the call of UpdateCertificateExpiry : https://github.com/jetstack/cert-manager/commit/51bf98581e6b40a4c81bd41a11203a8fad3dc200#diff-d14e419095685c0725dd0282d442ae7d
@munnerz was there a reason for removing it or did it happen by accident?

The only stats I am seeing on v0.11.0 (when directly scraping the metrics endpoint with curl) are
# HELP certmanager_certificate_ready_status The ready status of the certificate.
# HELP certmanager_controller_sync_call_count The number of sync() calls made by a controller.

I was expecting to also see

certificate_expiration_timestamp_seconds
acme_client_request_count
acme_client_request_duration_seconds

@munnerz is there any chance for someone to look at this by 0.12 ?
I found myself stuck since i need 0.11 to be able to consume vault using serviceaccount but to do that i lost the ability to monitor expiration of certificates.
thanks!

@kevinscholz thanks for digging that out - you are correct, it was removed by accident as we switched over to the new CertificateRequest based implementation!
We need to get a PR prepared to re-add this call back into the Certificate controller. We are no longer supplying backports for v0.11 as v0.12 is out, but this would be a candidate for back porting into v0.12
@Nuru the I'm surprised to hear that the ACME client is also not recording metrics, as this area of code has not changed. Are you sure your instance of cert-manager has actually made some requests with an ACME server? IIRC, metrics are not displayed unless there has been at least one occurrence of them.
/milestone v0.12
/priority important-soon

@Nuru after doing some of my own testing, I can confirm that the ACME client metrics are present in v0.12, so I believe perhaps your controller just hasn't made any ACME client requests since starting 😄

Opened #2416 to address this!


Docs.MS Release Updates for azure-storage-common

Update docs metadata and targeting for release of azure-storage-common

Docs Build status updates of commit 6c2b219:
:clock10: Full build: the average full build time is 97 min(s) 49 sec(s), this is based on the last 823 build(s) for this repository.

Docs Build status updates of commit 6c2b219:
:warning: Validation status: warnings

File
Status
Preview URL
Details

legacy/docs-ref-autogen/overview/EventHubs/Client.yml
:warning:Warning
View (azure-java-legacy)
Details

docs-ref-services/storage-common-readme-pre.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

package.json
:white_check_mark:Succeeded

legacy/docs-ref-autogen/overview/EventHubs/Client.yml

[Warning-DuplicateUids] Uid(azure.java.sdk.landingpage.services.eventhub.Client) has already been defined in docs-ref-services/messaging-eventhubs-readme.md.

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


Fix TypeError in help command by handling mixed parameter types for sorting

Summary:
This PR addresses the issue where the st2 run action pack.action -h command fails with a TypeError: '<' not supported between instances of 'str' and 'int'. The error occurs when sorting action parameters that have a mix of names (strings) and positions (integers). In Python 3, comparing these types directly causes a failure.
Root Cause:
The sorting function attempts to sort action parameters by either the position attribute (if present) or the name. In some cases, position is an integer while name is a string, leading to a type comparison error in Python 3.
Fix:
The _get_parameter_sort_value method has been updated to:

Convert the position attribute to a string (if it exists) for consistent sorting.
Fallback to sorting by the name when position is not available.
Ensure Python 3 compatibility by avoiding mixed-type comparisons during parameter sorting.

Fixes #5130

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

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

@nzlosh @cognifloyd  can you check getting lint error again and again adjusted  the file according to black format still
logic is fine but because of lint check is failing

@amanda11 @nzlosh
@cognifloyd
Can you review this request ?

Converting position to string will change the sort order; for example "10" sorts before "2". So, I'm concerned about merging this solution.

@cognifloyd  made some changes but does it look like , is this change feasible to apply
if yes , then can discuss how to proceed further otherwise , we can close if the issue doesn't look like solving

The logic is now pretty much the same as before.
I think a clean way to solve this would be to create a custom object wrapper that handles sorting comparisons. The object would wrap either name or position (a str or int). When the objects are compared with each other, an int should be sorted before a str, and if the types are the same, use the standard python comparison.


Azure Certificate Issue

Hello,
I am stuck with an Azure certificate issue & not sure if I have a legitimate issue or if just user error.  If this is the wrong "forum" then please just redirect me.
My use case is I have SW running inside Docker containers.  I want one Vagrantfile that will let me provision VMs on local PC, AWS & Azure & then start the containers in the new VMs.  Right now I have the first two working with Vagrant, but can't seem to get the Azure one working.
I am stuck on a certificate issue... have tried multiple times to generate & rerun, but the console output is cryptic.
C:\Users\jonathan.m.hamilton\Desktop\Docker\Play\Azure>vagrant up --provider=azu
re
C:/Users/jonathan.m.hamilton/.vagrant.d/gems/gems/azure-0.6.4/lib/azure/base_man
agement/base_management_service.rb:48:in `rescue in initialize': Management cert
ificate not valid. Error: Neither PUB key nor PRIV key: nested asn1 error (Runti
meError)
        from C:/Users/jonathan.m.hamilton/.vagrant.d/gems/gems/azure-0.6.4/lib/a
zure/base_management/base_management_service.rb:35:in `initialize'

I ran the following steps... user error or defect?  Thanks in advance!

$ openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout myPrivateKey.key -out myCert.pem

$ openssl  x509 -outform der -in myCert.pem -out myCert.cer

Successfully uploaded myCert.cer to Azure Management Console

Created Vagrantfile (key lines included only)
Vagrant.configure(2) do |config|
config.vm.box = 'azure'
config.vm.provider :azure do |azure|
azure.mgmt_certificate = 'C:\Users\jonathan.m.hamilton\Desktop\Docker\Play\Azure\myCert.pem'
azure.private_key_file = 'C:\Users\jonathan.m.hamilton\Desktop\Docker\Play\Azure\myPrivateKey.key'
azure.certificate_file = 'C:\Users\jonathan.m.hamilton\Desktop\Docker\Play\Azure\myCert.cer'
end
end

Hmm... I think your myCert.pem only contains the public side of the management cert.
Please run cat  myCert.pem myPrivateKey.key > mgmt_certificate.pem. Then set your azure.mgmt_certificate = {location of mgmt_certificate.pem}.
If you cat mgmt_certificate.pem, you should see:
-----BEGIN CERTIFICATE-----
{pub key}
-----END CERTIFICATE-----
-----BEGIN RSA PRIVATE KEY-----
{private key}
-----END RSA PRIVATE KEY-----

Thanks so much!  That was it!  I still get some sort of provisioning error, but I can close this and research it... cheers!
C:\Users\jonathan.m.hamilton\Desktop\Docker\Play\Azure>vagrant up --provider=azu
re
==> default: Attempting to read state for aswpoc1 in aswpoc1-service-jwkqr
Bringing machine 'default' up with 'azure' provider...
==> default: Attempting to read state for aswpoc1 in aswpoc1-service-jwkqr
==> default: Determining OS Type By Image
==> default: OS Type is Linux
==> default: Attempting to read state for aswpoc1 in aswpoc1-service-jwkqr
==> default: {:vm_name=>"aswpoc1", :vm_user=>"vagrant", :image=>"b39f27a8b8c64d5
2b05eac6a62ebad85__Ubuntu-14_04_1-LTS-amd64-server-20140927-en-us-30GB", :passwo
rd=>"masked", :location=>"Central US"}
==> default: {:cloud_service_name=>"aswpoc1-service-jwkqr", :storage_account_nam
e=>"aswpoc1storagesffgg", :private_key_file=>"C:\\Users\\jonathan.m.hamilton\\De
sktop\\Docker\\Play\\Azure\\myPrivateKey.key", :certificate_file=>"C:\\Users\\jo
nathan.m.hamilton\\Desktop\\Docker\\Play\\Azure\\myCert.cer", :ssh_port=>"22", :
vm_size=>"Small"}
ResourceNotFound : The hosted service does not exist.
==> default: Add Role? - false
not enough data
Server not created. Error is: not enough data

Hi Skelethan,
Im currently getting the same error as you did (Server not created. Error is: not enough data), did you manage to fix it?

Hi Tim,  Unfortunately I did not ever get this resolved.  I haven't had a chance to come back to it either.  I'm pasting my scrubbed Vagrantfile in case it's helpful
# -*- mode: ruby -*-
# vi: set ft=ruby :

# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant.configure(2) do |config|
  config.vm.box = 'azure'

    config.vm.provider :azure do |azure|
      azure.mgmt_certificate = 'C:\Users\jonathan.m.hamilton\Desktop\Docker\Play\Azure\mgmt_certificate.pem'
      azure.mgmt_endpoint = 'https://management.core.windows.net'
      azure.subscription_id = '<subscription_id'
      azure.storage_acct_name = '<storage_name>' # optional. A new one will be generated if not provided.

      #azure.vm_image = '5112500ae3b842c8b9c604889f8753c3__OpenLogic-CentOS-65-20140926'
      #azure.vm_image = 'b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_1-LTS-amd64-server-20140927-en-us-30GB'
      azure.vm_image = 'b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-14_04_1-LTS-amd64-server-20150123-en-us-30GB'
      azure.vm_user = '<username>' # defaults to 'vagrant' if not provided
      azure.vm_password = '<userpwd>' # min 8 characters. should contain a lower case letter, an uppercase letter, a number and a special character

      azure.vm_name = '<vm_name>' # max 15 characters. contains letters, number and hyphens. can start with letters and can end with letters and numbers
      azure.cloud_service_name = '<service_name>' # same as vm_name. leave blank to auto-generate
      #azure.deployment_name = '<deployname>' # defaults to cloud_service_name
      azure.vm_location = 'West US' # e.g., West US
      azure.private_key_file = 'C:\Vagrant\Azure\myPrivateKey.key'
      azure.certificate_file = 'C:\Vagrant\Azure\myCert.cer'

      # Provide the following values if creating a *Nix VM
      azure.ssh_port = '22'
      # Open HTTP port
      #azure.tcp_endpoints = '80,8000'
    end

  config.ssh.username = '<username>' # the one used to create the VM
  config.ssh.password = '<userpwd>' # the one used to create the VM
end


Abstract build functionality into a neon-build module

Right now the neon cli serves as both the utility for starting new neon modules (the boilerplate) and the cargo build tool. I'm suggesting that we separate the cargo build functionality into it's own module neon-build.
Separating the build functionality into a neon-build dependency means neon modules don't have to depend on the entire neon-cli, reducing the dependency tree for neon modules and consumers of neon modules.
Additionally this can help get us closer to a npm scripts style workflow (rather than expecting neon to be on the path globally). Mentioned in #34 and https://github.com/neon-bindings/neon/pull/126.
We can achieve this without breaking changes to neon-cli by using the new neon-build module internally. We could probably just replace the require statement for ./opts/neon_ build.js, or something similarly simple.

This issue was moved to neon-bindings/neon#239


[REVIEW] Explicit cast for atomicAdd operand

Added explicit casts to the value 1 in the atomicAdd that is used for the Count aggregator.
Without this, there seems to be a compiler error reported by some users.

LGTM

rerun tests


How to uninstall the existing app in all devices at the same time while running spoon

I am looking for a way to remove existing app in all devices before running spoon. Is there any config in spoon which does that ?
I usually use gradle spoon  to test .
gradle uninstallAll doesnt run in parallel.

AFAIK Spoon does not provide such an option. And there is no such option in this plugin as well.


Semgrep- JWT Token Expose

JWT Token must be hidden or encrypted.
Tracking issue for:

[x] https://github.com/Hellixaz/juice-shop/security/code-scanning/34

False positive.
Jest test.


Speed up typeof(Foo) and Object.GetType by 50+%

This adds a general purpose concept of "writable data" to the EEType data structure. This points to a block of memory whose purpose is defined by the class library (we can potentially cache all sorts of stuff there).
The writable data is used to hold a GC handle to the runtime System.Type instance associated with the EEType. This bypasses the hashtable lookup that has been used before.
I'm seeing more than 50% TP improvement against best case scenarios with the hashtable (best case defined as "the thing we're looking for is the first entry in the hashtable bucket").
Both CoreCLR and Mono use a similar approach. CoreRT was lagging in perf because of the hashtable lookup: this brings us much closer. We're still not as fast as CoreCLR, but getting faster than this would have impacts elsewhere (in terms of working set and size on disk). The implementation I chose for CoreRT (optional relative pointer field) has minimal working set impact.

"Well sure let's debug this Mac specific issue."

Boots into macOS after not touching it for a while
git says "dyld: Symbol not found _OBJC_IVAR_NSTextViewIvars.sharedData"
Try to open xcode "Xcode cannot be opened because of a problem"
Try to update Xcode: You need macOS 10.15.2, hahaha

Michal, can you fix the mac build?

Michal, can you fix the mac build?

😤
This was a bug in ObjectWriter. Also had to turn off warnings as errors when building the fixed ObjectWriter because building LLVM we use for the ObjectWriter library generates warnings with the latest Xcode tools.

Should probably mention that the only reason why I'm even doing this pull request is the discussion around https://github.com/dotnet/corert/pull/7962#discussion_r373850627. Finally the saga is coming to an end.


I have issue regarding cursor. Every time I open up a new file there is a block cursor which acts as an eraser, to get normal cursor, I have to press 'S'

I am not able to explain my problem correctly as I don't know how it started. I tired uninstalling vs code and reinstalling also set default setting of cursor with all the extension disable still the problem is not solved.
I can show it using video but unable to upload video directly so i will to share a drive link in the description.
Drive Link - ( https://drive.google.com/file/d/10bTyQSvRvy38Xw2m7dzh4d8pjTvh-6kw/view?usp=drivesdk )

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:  1.88.1
OS Version: MacOS 14.4.1 (23E224)

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Have you perhaped installed the vim extension? Could you attempt to disable it?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


love 11.x support

I have tried to run grid-sdk, which is wonderful with love 0.10.2.
As love as released 11.x in 2018, it is better that upgrade grid-sdk with love 11.x.

There's a build of Grid currently on LÖVE 11 which has not yet been released. I'll schedule this for deployment tonight. It's probably time I get it out in the open.

Resolved in v8.0.0.


Added Santhosh Sundaram's final GSoC report

This is my submission for the GSoC 2024 final report on my project pybamm-cookie.

Thanks, @santacodes! Please confirm if this is ready for merging?

After this, could you open a separate PR to add a link to it to https://pybamm.org/gsoc/#project-reports?

Thanks, @santacodes! Please confirm if this is ready for merging?

Yeah, I think so, I have checked the contents from my side but if you see anything wrong feel free to point it out! Or else it is good to merge. Thanks :)

After this, could you open a separate PR to add a link to it to https://pybamm.org/gsoc/#project-reports?

Sure!

After this, could you open a separate PR to add a link to it to https://pybamm.org/gsoc/#project-reports?

How about we do it in the same PR, I think we may anticipate the report url before this PR gets merged?

I just wanted to preserve linear history by squashing the PR

I just wanted to preserve linear history by squashing the PR

I see, sounds good to me then


Tests: Fix always succeeding XCTAssertAsyncNoThrow

The autoclosure expression { throw error } just creates a closure that won't be executed. It leads to the test always succeeding even if the expression throws an error.
Fortunately, I didn't find any issue to enable the assertion except for a single case (https://github.com/swiftlang/swift-package-manager/pull/8026/commits/ab1e7849216aba671ed031993972c03f643649cf)

@swift-ci test

@swift-ci test

@grynspan This assertion activation revealed that SWIFT_TESTING_ENABLED is set to "0" only on macOS and not set on other platforms. (introduced by this change)
Is this intentional behavior or should we set the env variable regardless of the target platform?

It has no effect on other platforms. We set it on macOS so that XCTest doesn't try to host Swift Testing from within Xcode, like it would if you were using Xcode instead of SwiftPM.
It's a bit of an inelegant hack and we may remove it in a future Xcode update.

Ok, then skip the test on non-macOS platforms

@swift-ci test


feat: plume with poseidon2 hashes

As discussed with @yush_g we wanted to try PLUME with poseidon hashes, this is the PR. Still pending:

[ ] Noir bigcurve has a pending PR to update bignum to 0.4.2
[ ] I guess changes to the ERC itself, but we can merge this to a "poseidon" branch in the meantime

I also have no idea how to update the SAGE scripts to use poseidon, I suppose it's too much to ask for a SAGE implementation of it :D @NikitaMasych any idea how could we get around this?

Hey, nice to see this PR; I'll take an extensive look a bit later, but at the first glance looks legit 🙂

I also have no idea how to update the SAGE scripts to use poseidon, I suppose it's too much to ask for a SAGE implementation of it :D @NikitaMasych any idea how could we get around this?

I'll see that I can do; sage is merely an exemplary in this repository, so this shouldn't be a burden to deliver this feature

Thanks @NikitaMasych the reason I'm picking this up is mostly to learn, as I am playing around with Stealthdrop on the phone and thus felt the need to make it less costly. Stealthdrop is also one of the noir examples and the existent version is very outdated (and unsafe), so I'd like to update that too


[VL] Build gluten on aarch64 with VCPKG

Problem description
I'm trying to build gluten and velox on aarch64 architecture. I'm running the script ./dev/builddeps-veloxbe.sh --enable_vcpkg=ON --spark_version=3.5 . I get the error below. I see that these options -mavx2 -mfma -mavx -mf16c -mlzcnt -mbmi2 are only for x86_64, so they won't work on aarch64. Do you know how I can build gluten for aarch64 please? (In version 1.1.x.x., we were able to build for both aarch64 and x86_64).
I see vcpkg init.sh has VCPKG_TRIPLET=x64-linux-avx https://github.com/apache/incubator-gluten/blob/c82af60a635fb52bf1314cd831f5915dd37d910d/dev/vcpkg/init.sh#L10. It makes sense that the x64 and the avx parts of this triplet will cause errors running on aarch64. I see it got changed in https://github.com/apache/incubator-gluten/commit/f00e4536bc7ccc56a2eee5800084319130cbf806#diff-4a8a09cebf7ed92cb7321136b9ef223c4653757270e77e942fd6fe2dca30793e -  do you recommend that we should cherry-pick that commit (and a few more commits that it depends on)?
CMake Error at /usr/local/share/cmake-3.28/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "/usr/bin/cc"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: '/home/circleci/project/dev/vcpkg/.vcpkg/buildtrees/detect_compiler/x64-linux-avx-rel/CMakeFiles/CMakeScratch/TryCompile-9obttD'

    Run Build Command(s): /usr/bin/ninja -v cmTC_32844
    [1/2] /usr/bin/cc   -fPIC -mavx2 -mfma -mavx -mf16c -mlzcnt -mbmi2 -o CMakeFiles/cmTC_32844.dir/testCCompiler.c.o -c /home/circleci/project/dev/vcpkg/.vcpkg/buildtrees/detect_compiler/x64-linux-avx-rel/CMakeFiles/CMakeScratch/TryCompile-9obttD/testCCompiler.c
    FAILED: CMakeFiles/cmTC_32844.dir/testCCompiler.c.o
    /usr/bin/cc   -fPIC -mavx2 -mfma -mavx -mf16c -mlzcnt -mbmi2 -o CMakeFiles/cmTC_32844.dir/testCCompiler.c.o -c /home/circleci/project/dev/vcpkg/.vcpkg/buildtrees/detect_compiler/x64-linux-avx-rel/CMakeFiles/CMakeScratch/TryCompile-9obttD/testCCompiler.c
    cc: error: unrecognized command line option ‘-mavx2’
    cc: error: unrecognized command line option ‘-mfma’
    cc: error: unrecognized command line option ‘-mavx’
    cc: error: unrecognized command line option ‘-mf16c’
    cc: error: unrecognized command line option ‘-mlzcnt’
    cc: error: unrecognized command line option ‘-mbmi2’
    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:11 (enable_language)

System information
Velox System Info v0.0.2
Commit: 69a6bb9602c97050cc3459a09c846b84182ecb9c
CMake Version: 3.28.3
System: Linux-5.15.0-1070-aws
Arch: aarch64
CPU Name: Model name:                           Neoverse-N1
C++ Compiler: /usr/bin/c++
C++ Compiler Version: 9.4.0
C Compiler: /usr/bin/cc
C Compiler Version: 9.4.0
CMake Prefix Path: /usr/local;/usr;/;/usr/local;/usr/local;/usr/X11R6;/usr/pkg;/opt
\nThe results will be copied to your clipboard if xclip is installed.
CMake log
No response

do you recommend that we should cherry-pick that commit (and a few more commits that it depends on)?

@z-anderson, I guess that commit will not fix this issue.
With VCPKG_TRIPLET=x64-linux-avx, vcpkg will use a custom triplet file we created, see https://github.com/apache/incubator-gluten/blob/main/dev/vcpkg/triplets/x64-linux-avx.cmake. You can see some flags are set for x86_64.
To support arm64, I recommend you to create another triplet file with proper flags set, e.g. set(VCPKG_TARGET_ARCHITECTURE arm64)(see reference link). Then, in Gluten script, set VCPKG_TRIPLET to this new custom triple instead of x64-linux-avx when target architecture is arm64 (we may make target architecture a configurable build option).

Thank you!

@z-anderson, could you create a pr to fix it?

@z-anderson would you like to create the PR and maintain it? We currently don't have any ARM CI tests actually. There are several guys submitting PRs on ARM. Maybe you all can work together and contribute.

Sounds good. Yes, I'll put up a PR with my changes to https://github.com/apache/incubator-gluten/blob/main/dev/vcpkg/init.sh for this.

I put up a draft https://github.com/apache/incubator-gluten/pull/7687 . This PR gets past that error, but I'm still working on getting it to build completely (at least for my set up).

I don't have permission to create a new github runner (with ARM). Could someone else create the new runner, please? Then I'll use it in https://github.com/apache/incubator-gluten/blob/main/.github/workflows/build_bundle_package.yml

@z-anderson, could you first validate your fix in your arm64 environment? Currently, our CI resources are near to the limitation. We can add new jobs on arm in the future when some resources are freed up.

In my arm64 environment, it actually finds the community triplet (so it doesn't use the new triplet file). Using the community triplet does correctly get it to start building for arm64 instead of amd.

I don't have permission to create a new github runner (with ARM). Could someone else create the new runner, please? Then I'll use it in https://github.com/apache/incubator-gluten/blob/main/.github/workflows/build_bundle_package.yml

You may track the UT internally firstly. We may plan to add the ARM runner in future.

So will we continue the PR, but not do CI tests with an ARM runner for now?

So will we continue the PR, but not do CI tests with an ARM runner for now?

@z-anderson, yes, we can land this pr as long as it is verified on your side.


moment('1398-02-29').format()

moment('1398-02-29').format()
"Invalid date"

Hello,
It seems there is no 29 February of the year 1398. It works using moment('1398-02-28').format()
src

Hello,
No, this is history in Iran.
Link

I may have misread but the source you provided just said that February in 1398 for your country has only 28 days.

I agree with @sefam-vbastien .
Please re-open if you still have issues.


ROX-20473: Make kuttl tests more consistent

Description
WiP. TODO: steps 80 and on
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test help

/test gke-operator-e2e-tests
/test ocp-4-10-operator-e2e-tests
/test ocp-4-13-operator-e2e-tests
/test ocp-4-14-operator-e2e-tests

/test gke-operator-e2e-tests
/test ocp-4-10-operator-e2e-tests
/test ocp-4-13-operator-e2e-tests
/test ocp-4-14-operator-e2e-tests

/test gke-operator-e2e-tests
/test ocp-4-10-operator-e2e-tests
/test ocp-4-13-operator-e2e-tests
/test ocp-4-14-operator-e2e-tests

/test gke-operator-e2e-tests
/test ocp-4-10-operator-e2e-tests
/test ocp-4-13-operator-e2e-tests
/test ocp-4-14-operator-e2e-tests

/test gke-operator-e2e-tests
/test ocp-4-10-operator-e2e-tests
/test ocp-4-13-operator-e2e-tests
/test ocp-4-14-operator-e2e-tests

/retest


tsp, upgrade TCGC version to 0.44.2

code: 88f6c1cd86704f2069ae124824ed6bdc31dbbcc0
logics change mainly on:

built in types change
multipart form data handling logic change

Multipart is handled in this pr, I will fix CI and merge this.

code LGTM
I forgot multipart also has behavior break (on the isMulti and its type)... If it is close to work, you can finish it. If it seems still having problem, I can take the rest of the PR.


Crashes when trying to enter something in the model number field.

Using an Android phone. Samsung galaxy A03 running one UI 5 core rooted.

same here
samsung s22+   A13
i cant do anything from app, always  crashing
Log_2023-02-06_05-42-08.txt

same here
samsung s22+   A13
i cant do anything from app, always  crashing
Log_2023-02-06_05-42-08.txt

This version seems pretty much broken. Downgrading works.

Should be fixed with https://github.com/zacharee/SamloaderKotlin/releases/tag/1.13.1

Should be fixed with https://github.com/zacharee/SamloaderKotlin/releases/tag/1.13.1

Sure thanks.


lib skeleton

Description of change

Pull-Request Checklist

[ ] Code is up-to-date with the main branch
[ ] npm run lint passes with this change
[ ] npm run test passes with this change
[ ] This pull request links relevant issues as Fixes #0000
[ ] There are new or updated unit tests validating the change
[ ] Documentation has been updated to reflect this change
[ ] The new commits follow conventions outlined in the conventional commit spec

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@947a9f9). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage        ?   43.75%
=======================================
  Files           ?        2
  Lines           ?       16
  Branches        ?        0
=======================================
  Hits            ?        7
  Misses          ?        9
  Partials        ?        0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


How do I rewrite url before proxying

Original url  /n/test.html
Backend url /test.html

I don't think we implemented URL rewriting in this project.

Thanks.


make on develop fails - error in stan/lib/stan_math/make/libraries

Summary:
updated to latest develop, all make commands are failing
Description:
history:
  505  git checkout develop
  506  git pull
  507  make clean-all
  508  make stan-update

~/github/stan-dev/cmdstan (develop)> make stan-update
stan/lib/stan_math/make/libraries:108: *** "Need to set TBB_CXX_TYPE for non-standard compiler other than gcc or clang.".  Stop.

Reproducible Steps:
see above.
Current Output:
The current output. Knowing what is the current behavior is useful.
Expected Output:
Describe what you expect the output to be. Knowing the correct behavior is also very useful.
Additional Information:
Provide any additional information here.
Current Version:
v2.24.0

Is this for mac? Is there anything in your make/local? @wds15 can you try this when you get a minute? We can revert the optim stuff if we want to release tmrw CET

don't have a make/local for cmdstan.
I checked out develop branch of math, and there make clean-all works fine, also make clean-all is OK for repo stan, using develop branch of math.  has anything in cmdstan makefile changed?

Is this for mac?
yes

has anything in cmdstan makefile changed?

Yeah so I just reverted the changes to the cmdstan makefile in #934. We were adding lto something must have goofed up

thanks.
my bad for not paying attention to CmdStan makefiles.  those changes need some work - happy to help debug/refactor.

checked out latest - it's working, but complains:
~/github/stan-dev/cmdstan (develop)> make clean-all
rm -f -r test
make: *** No rule to make target `clean-libraries', needed by `clean-all'.  Stop.
make: *** Waiting for unfinished jobs....
....


Upgrade to netstandard 2.0

.NET Core 2.0 is out, let's upgrade this one as well.

Why upgrade to a higher version of the standard when a lower one will work just fine?  This change removes support for people that are not using Net Standard 2.0 yet.

In general, we recommend you to target the lowest version of .NET Standard possible.
https://docs.microsoft.com/en-us/dotnet/standard/net-standard

It causes troubles in following scenario:

Have service hosting executable ServiceHost.exe that loads and runs Service.dll
Have that Service.dll referencing Microsoft.Extensions.Logging 2.0.0
Use this log4net extension in code in Service.dll

What happens is that ServiceHost.exe.config does not contain assembly redirect for Microsoft.Extensions.Logging because ServiceHost.exe does not use it. One who uses it is Service.dll but since it's a DLL and runs in other process it's own assembly redirections are not used. Then in runtime when you call AddLog4Net it fails with MethodNotFoundException. The reason is that this library was not built with Microsoft.Extensions.Logging 2.0.0 and since Microsoft.Extensions.Logging is strong-named runtime not accept it when matching method signature. Only when assembly redirection is in place it works with Microsoft.Extensions.Logging 2.0.0.

The same issue as with this package exists for some others as well so I'll have to solve it differently. Closing this PR as not needed.


Update Component Versions

Update components as follows:
GCC - 11
Conan 1.39.0
CMake 3.21.1

GCC-11 package is not currently available in ubuntu-20.04. Removing requirement for now.


Weighted Average Cost of Capital (WACC) Calculator

Description
used to determine a company's cost of capital, which is the average rate of return it needs to pay its investors for using their capital.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 can you assign this to me

@mahek0620  I have a few questions. Please answer them.

What all inputs are you going to take from the user?
Will this give the output for they would have to pay in the future or is it an instant kind of a thing?
Will it consider the other things such as some benefits or already given returns in the past while giving the output?
Will it give some kind indication if the return is too high or low?

@jessicachawla Inputs
Cost of Equity (Re): The return required by equity investors.
Cost of Debt (Rd): The effective rate the company pays on its borrowed funds.
Market Value of Equity (E): The total value of the company's equity.
Market Value of Debt (D): The total value of the company's debt.
Corporate Tax Rate (Tc): The company's tax rate.
Features and Functionalities
Instant Calculation: The WACC is calculated instantly based on the provided inputs.
Output: The calculator will provide the weighted average cost of capital, which represents the company's overall cost of financing.
Historical Considerations: The calculator will not consider past benefits or returns; it will focus on current values and inputs.
Return Indication: The calculator can include a feature to indicate whether the WACC is too high or too low based on industry standards or user-defined thresholds.

@Rakesh9100 can you assign this to me

What is the point if it's not counting the benefits/other things?
The calculation will be off then


Optimize Word Jet CMR calculation

@uncomputable This is a draft PR.  I don't want it reviewed yet.  I only posted it because you asked to see it.

@real-or-random This might be harder to review, so let be know if you have any questions.


Map data of streets of Rosario,Santa Fe, Argentina

I found a public set with the streets and number of the city of Rosario, Santa Fe, Argentina
http://datos.rosario.gob.ar/sites/default/files/nomenclador_de_calles.gml
I don't know where to put it
Regards
Diego

Thank you @eldie1984! I’ve started a branch for this under migurski/add-rosario-ar. Looks like the data format is long linestrings?

These might not necessarily be appropriate for OpenAddresses, because I'm not sure how to derive address points from this data.

I am not sure this dataset has address info, but there are several other possible sources listed in issue https://github.com/openaddresses/openaddresses/issues/3003 (which seems to have gone unnoticed...).


Hydraulic Schema Releases

Pry isn't quite right yet - but wanted to get in the mix to see what happens

You got those filenames backwards...
Your current filenames in Released folders:
.ecschema..xml
It should be:
..ecschema.xml


Add more exceptions to 'no-unbound-method'

PR checklist

[X] Addresses an existing issue:  #2128
[X] New feature, bugfix, or enhancement

[X] Includes tests

[ ] Documentation update

What changes did you make?

Allow property access.
Allow binary expression (except ||).

Interesting case with forEach. It and other array methods that take this reference as last parameter  provide similar functionality.
However as I can see from typings in lib.d.ts it is not possible to distinguish such methods from other :(

@andy-hanson thanks!


Header file not found error

I am using ROS noetic to run this simulation. I received error during catkin_make
In file included from /usr/include/cppad/ipopt/solve.hpp:405,
                 from /home/abc/ROS_ws/src/multi_robot_traj_planner/multi_robot_traj_planner/include/prioritized_traj_optimization.hpp:44,
                 from /home/abc/ROS_ws//src/multi_robot_traj_planner/multi_robot_traj_planner/src/prioritized_traj_planner.cpp:18:
/usr/include/cppad/ipopt/solve_callback.hpp:16:11: fatal error: coin/IpIpoptApplication.hpp: No such file or directory
   16 | # include <coin/IpIpoptApplication.hpp>
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/include/cppad/ipopt/solve.hpp:405,
                 from /home/abc/ROS_ws//src/multi_robot_traj_planner/multi_robot_traj_planner/include/coupled_traj_optimization.hpp:42,
                 from /home/abc/ROS_ws//src/multi_robot_traj_planner/multi_robot_traj_planner/src/coupled_traj_planner.cpp:18:
/usr/include/cppad/ipopt/solve_callback.hpp:16:11: fatal error: coin/IpIpoptApplication.hpp: No such file or directory
   16 | # include <coin/IpIpoptApplication.hpp>
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
compilation terminated.
make[2]: *** [multi_robot_traj_planner/multi_robot_traj_planner/CMakeFiles/prioritized_traj_planner.dir/build.make:63: multi_robot_traj_planner/multi_robot_traj_planner/CMakeFiles/prioritized_traj_planner.dir/src/prioritized_traj_planner.cpp.o] Error 1
make[2]: *** [multi_robot_traj_planner/multi_robot_traj_planner/CMakeFiles/coupled_traj_planner.dir/build.make:63: multi_robot_traj_planner/multi_robot_traj_planner/CMakeFiles/coupled_traj_planner.dir/src/coupled_traj_planner.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:2687: multi_robot_traj_planner/multi_robot_traj_planner/CMakeFiles/prioritized_traj_planner.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/Makefile2:2336: multi_robot_traj_planner/multi_robot_traj_planner/CMakeFiles/coupled_traj_planner.dir/all] Error 2
[ 95%] Linking CXX executable /home/abc/ROS_ws/devel/lib/multi_robot_traj_planner/random_map_generator
[ 97%] Linking CXX executable /home/abc/ROS_ws/devel/lib/multi_robot_traj_planner/warehouse_map_generator
[ 97%] Built target random_map_generator
[ 97%] Built target warehouse_map_generator
make: *** [Makefile:141: all] Error 2
Invoking "make -j20 -l20" failed

The same issue, may I ask if it has been resolved?


Can't run a drush sql-dump - Database dump failed because Table '/tmp/#sql_1_0.MAI' is read only

I'm using the docker4drupal resources to build me a labserver for drupal-sites, with the site-files residing outside of the docker-containers.
I've tried this for both Drupal 7 & Drupal 8 and get the same issue in both - inside a running site, I can modify data without any problems, using drush sqlc I can do things like "truncate table XXX;" but when I execute "show fields from XXX;" from drush sqlc I get this same error:
I'm trying to get a database-dump (or a drush ard) through drush using
docker-compose exec --user 82 php drush -r ./web/ sql-dump
but I get the error at the bottom - I'm including my current docker-compose.yml, I have similar setups for Drupal 7 site (with PHP5.6) and I've tried it with externally hosted db-datafiles and in-container db-datafiles, always the same result.
`version: "2"
services:
mariadbrefsite:
image: wodby/mariadb:10.1-2.1.0
environment:
MYSQL_ROOT_PASSWORD: password
MYSQL_DATABASE: siterefsite
MYSQL_USER: siterefsite
MYSQL_PASSWORD: drupal
networks:
- backend
volumes:
- /home/fedict/db/refsite/mariadb-init:/docker-entrypoint-initdb.d # Place init .sql file(s) here.
php:
image: wodby/drupal-php:7.1-2.1.0
environment:
PHP_SENDMAIL_PATH: /usr/sbin/sendmail -t -i -S mailhog:1025
DB_HOST: mariadbrefsite
DB_USER: siterefsite
DB_PASSWORD: drupal
DB_NAME: siterefsite
DB_DRIVER: mysql
networks:
- backend
volumes:
- /home/fedict/www/refsite/:/var/www/html
nginx:
image: wodby/drupal-nginx:8-1.10-2.1.0
depends_on:
- php
environment:
NGINX_STATIC_CONTENT_OPEN_FILE_CACHE: "off"
NGINX_ERROR_LOG_LEVEL: debug
NGINX_BACKEND_HOST: php
NGINX_SERVER_ROOT: /var/www/html/web
networks:
- web
- backend
volumes:
- /home/fedict/www/refsite/:/var/www/html/
labels:
- 'traefik.port=80'
- 'traefik.frontend.rule=Host:refsite.drulab.bosa.be'
- 'traefik.docker.network=traefik_webgateway'
volumes:
codebase:
networks:
web:
external:
name: traefik_webgateway
backend:
driver: bridge
`

Host OS: RHEL 7.3
Docker version: 17.03.1-ce
Logs output:
` docker-compose exec --user 82 php drush -r ./web/ sql-dump
-- MySQL dump 10.16  Distrib 10.1.21-MariaDB, for Linux (x86_64)
--
mysqldump: Error: 'Table '/tmp/#sql_1_2.MAI' is read only' when trying to dump tablespaces
-- Host: mariadbrefsite    Database: mariadbrefsite

-- Server version       10.1.22-MariaDB
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT /;
/!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS /;
/!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION /;
/!40101 SET NAMES utf8 /;
/!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE /;
/!40103 SET TIME_ZONE='+00:00' /;
/!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 /;
/!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 /;
/!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' /;
/!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;
--
-- Table structure for table batch
DROP TABLE IF EXISTS batch;
/*!40101 SET @saved_cs_client     = @@character_set_client /;
/!40101 SET character_set_client = utf8 /;
CREATE TABLE batch (
bid int(10) unsigned NOT NULL COMMENT 'Primary Key: Unique batch ID.',
token varchar(64) CHARACTER SET ascii NOT NULL COMMENT 'A string token generated against the current user''s session id and the batch id, used to ensure that only the user who submitted the batch can effectively access it.',
timestamp int(11) NOT NULL COMMENT 'A Unix timestamp indicating when this batch was submitted for processing. Stale batches are purged at cron time.',
batch longblob COMMENT 'A serialized array containing the processing data for the batch.',
PRIMARY KEY (bid),
KEY token (token)
mysqldump: Couldn't execute 'show fields from batch': Table '/tmp/#sql_1_0.MAI' is read only (1036)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COMMENT='Stores details about batches (processes that run in…';
/!40101 SET character_set_client = @saved_cs_client */;
Database dump failed       `

I'm having the exact same issue. I am running a project on my Mac and exported the database to a 'production' environment on a CentOS 7 server.
I can do all sorts of selects but in a few cases i get issues with a 'read only' tmp table. I have checked if i can write to the /tmp directory within the mariadb container when logging in as the mysql user (uid 100).
One of the queries that gives me the error is:
SELECT DISTINCT b.* FROM block b LEFT JOIN block_role r ON b.module = r.module AND b.delta = r.delta
I am clueless at this point.

I fixed my problem for now by reverting back to an old version of MariaDB (wodby/drupal-mariadb:1.0.0).

Rolling back to wodby/mariadb:2.0.0 does fix it - the wodby/drupal-mariadb repo seems like it's an old one that isn't updated any more?

I didn't have time to look closely into this issue but try to use the latest non-tagged image wodby/mariadb:10.1

My first guess would be that is has something to do with updating mariadb to 10.1.22-r0. I'll try to compare the versions and see if it changes anything.

Going to the non-tagged version doesn't help, rolling back to wodby/mariadb:10.1:2.0.0 does.

I've just rebuilt a non-tagger version to 10.1.22-r1 (alpine 3.6). Try it out. Also, we had a lot of changes in mariadb config (performance tuning) in the last versions but I think it was after 2.1.0.

Tried with the latest non-tagged version, but the error remains:
mysqldump: Error: 'Table '/tmp/#sql_1_2.MAI' is read only' when trying to dump tablespaces mysqldump: Couldn't execute 'show fields from actions': Table '/tmp/#sql_1_0.MAI' is read only (1036) Database dump failed

Could you please attach the SQL file that can be used to reproduce the issue. Perhaps we should post a bug report to mariadb or alpine team.

It happens even on a basic Drupal installation like this one:
0000.sql.gz
I managed to get a sql-dump by rolling back to the 2.0.0 image without deleting the database files.

Yes, it's still alpine-based, does anyone have the issue with wodby/mariadb:10.1-3.1.2 (we also have 10.2 now)?

@csandanov the issue is reproducible since mariadb 10.1.22 on kernels below 4.4
So either upgrade kernel or downgrade mariadb

What is your docker storage driver? If it's reproducible with a certain version of kernel there's a good chance it could be fixed by changing the driver, overlay2 proved itself as quite stable with kernel 4.x


use $HOSTNAME env variable instead of hostname command in new Oracle based mysql container

As per the issue #35432, hostname command is no longer available as mysql:5.7 is now based on Oracle.
For the command on line 27 to work, it is sufficient to use the $HOSTNAME variable which is set in the container,
for it to work effectively.

/assign @tengqm

Looks reasonable, didn't test it manually.
/lgtm

/approve


On first boot, asked to create new user

FIRST_USER_NAME='pi' in config so I would think that the first user would be pi with no password required.

Wasn't asked to create new user at boot. Maybe due to user config settings in RaspPi Imager?

From README

FIRST_USER_NAME (Default: pi)

Username for the first user. This user only exists during the image creation process. Unless DISABLE_FIRST_BOOT_USER_RENAME is set to 1, this user will be renamed on the first boot with a name chosen by the final user. This security feature is designed to prevent shipping images with a default username and help prevent malicious actors from taking over your devices.

From README

FIRST_USER_NAME (Default: pi)

Username for the first user. This user only exists during the image creation process. Unless DISABLE_FIRST_BOOT_USER_RENAME is set to 1, this user will be renamed on the first boot with a name chosen by the final user. This security feature is designed to prevent shipping images with a default username and help prevent malicious actors from taking over your devices.


Uncorrected mapping with NCmesh

Hi all,
I'm incorporating Remhos into my code to remap the L2 fields after remeshing.
I believe the remapping is functioning correctly with the conforming mesh, but I'm encountering some issues with a non-conforming mesh.
In the case of a conforming mesh, the mesh simply moves, and the field does not move because they are advected together. However, with a non-conforming mesh, the shape of the field is altered, leading to incorrect mapping (see attached image).

This is obvious when I use the example of Remhos.
I typed mpirun -np 8 remhos -m ./data/cube01_hex.mesh -p 10 -rs 1 -o 2 -dt 0.02 -tf 0.8 -ho 1 -lo 4 -fct 2 but I modified element attributes of 1st and 2nd element to two and Remhos like this way. You can see non-conforming mesh and final remapped field is highly distorted. I think advection is prohibited between coarse- and fine-mesh regions.
mesh->EnsureNCMesh(true);
Array<int> refs;

for (int i = 0; i < mesh->GetNE(); i++)
{
if(mesh->GetAttribute(i) >= 2)
{
refs.Append(i);
}
}

mesh->GeneralRefinement(refs, 1);
refs.DeleteAll();
mesh->Finalize(true);

Any comments would be greatly appreciated.
Sungho

Hi @sungho91 the methods -lo 4 and -lo 5 are not implemented for NC meshes and won't work.
We haven't tested Remhos with NC meshes, but I expect some combinations to work. I'll try and let you know soon.
You can also try by simplifying the setup (disable the monotonicity), and then go back incrementally. For example -ho 3 -lo 0 -fct 0 and if that works, try some -lo options, and then finally try -fct options.

@vladotomov
According to my quick couple of tests, introducing a low-order solver prohibits advection between coarse- and fine-mesh regions. -ho 2 or -ho 3  without -lo and -fct works but the solution from them seems to need improvement.

I'm on travel this week, but I'll take a look when I come back.

@sungho91 seems that the -ho 3 and -lo 5 (simplest LO solver) work with the code in master, I tried these:
mpirun -np 4 remhos -m ./data/amr-quad.mesh -p 14 -rs 2 -dt 0.001 -tf 0.4 -ho 3 -lo 5 -fct 2
mpirun -np 4 remhos -m ./data/amr-quad.mesh -p 14 -rs 2 -dt 0.001 -tf 0.4 -ho 3 -lo 5 -fct 4


After activation, if I hit return, Postgres launches and takes focus

It's the strangest thing. I hit sol's activator, the window prompt comes up, I hit enter/return and expect it to either do nothing or to disappear but instead it launches the Mac app Postgres. I close it, repeat, it launches it again. Mostly curious but I guess I'm also reporting a bug, and am curious if you end up finding the reason.
M1 running Sonoma 14.2.1

Ah yeah, the return listener is still active in the minimized form. Thanks for noticing, I will take care of it.

Fix is released in 2.1.16


feat(endo): Add command line

This change provides a preliminary command line for endo, mostly because it is convenient for ad-hoc testing, though it will likely grow into something else.
Usage:
# run an application
$ endo path/to/module.js

# write an archive
$ endo -w mod.agar path/to/module.js

# run an archived application
$ endo -x mod.agar

This is entirely open for discussion.

@michaelfig recommended reserving -w for “watch” and @dtribble (I think) recommended parity with tar, so -c instead.


Investigate screenshot problems introduced in v1.6.0

[ ] https://github.com/DevExpress/testcafe-browser-provider-saucelabs/issues/53
[ ] https://github.com/DevExpress/testcafe/issues/4440
[ ] https://github.com/DevExpress/testcafe/issues/4475

I am also facing the same issue of not being able to take a screenshot  with v1.6.0 specifically with "testcafe-browser-provider-puppeteer": "1.4.0",

I'll close it after
https://github.com/DevExpress/testcafe/issues/4475

Anyway you could release this fix for testcafe? Maybe as next channel on npm?

Hi @weyert
We are going to release the alpha version of TestCafe this week. The released version will include the necessary fix.

Awesome, thank you very much! :)

On 19 Nov 2019, at 08:43, Mikhail Losev<EMAIL_ADDRESS>wrote:

Hi @weyert
We are going to release the alpha version of TestCafe this week. The released version will include the necessary fix.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


perf(cmark): introduce more inout params to save some allocations

Blocked on https://github.com/moonbitlang/core/issues/1361.

Pull Request Test Coverage Report for Build 126
Details

48 of 55 (87.27%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 74.569%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/cmark/inline_struct.mbt
40
43
93.02%

src/cmark/alias.mbt
4
8
50.0%

Totals

Change from base Build 125:
0.02%

Covered Lines:
1428

Relevant Lines:
1915

💛  - Coveralls


added fields to certificate request types

@ninataneja Please add description to the PR.
/hold

@ninataneja Could add a short description of the changes you made and why?

/hold cancel

/lgtm


PEAR-1983 - Update Case Summary Page for Other Clinical Attributes

Description
+ Broke up Diagnoses and FollowUps into their own components
Checklist

[x] Added proper unit tests
[x] Left proper TODO messages for any remaining tasks
[x] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

Functionality looks good to me. 👍
Noticed some styling-related things, which I'll defer to @cemile-ctds:

I think the "No  Found" text font should be Noto-Sans. Actually, the "No Other Clinical Attributes Found." and "No Molecular Tests Found." text seems to be in a different style from, e.g. "No Family Histories Found." text. I'm not sure if we should make them more similar or something. This case should show the difference: http://localhost:3000/cases/164eeaa7-4229-493f-ae77-0843f36af6b8
Does the new badge with number in the subtables need to be nearer to the name of the node?

Hey @cemile-ctds, did you have any feedback on the styling for this ticket?

The 'No Found' text font should be Noto Sans.
We need to ensure consistent font styling for the 'No Found' text. Please refer to the mockup for the correct styling.
Additionally, the  headings have extra margin. It would be better to remove it.

Looks good on my side.


Fix how batch tables choose sentinel values

This PR fixes how batch tables choose noData values when upgrading to EXT_structural_metadata. Specifically,

For signed ints, the order of checks in getSentinelValue prevented -1 from being chosen as a sentinel value if 0 was taken. The order has been changed to account for this.
Unsigned ints will be upgraded to the next biggest signed int (if possible) if 0 cannot act as a sentinel value. This allows -1 to be used as its sentinel value instead.
If no sentinel value is available for a property that has null, explicitly force it to a string property.

Without these checks, there is some unpredictable behavior because some of the code assumes a valid sentinel value exists, leading to dereferenced nullopts 😬

Thanks @j9liu!


chore: update forc to 0.51.1

Short and sweet!

Setting to draft because it's apparently not short and sweet. I thought pnpm pretest ignores the cache and rebuilds when forc versions change. Everything succeeded locally (with forc 0.50.0-built binaries), but it failed in the CI.

Setting to draft because it's apparently not short and sweet. I thought pnpm pretest ignores the cache and rebuilds when forc versions change. Everything succeeded locally (with forc 0.50.0-built binaries), but it failed in the CI.

Not short and sweet at all 😆.
I've tried to use Forc 0.51.1 on https://github.com/FuelLabs/fuels-ts/pull/1764 to verify if some errors will go away but it turns out there were some updates related to encapsulations that resulted in some Sway projects not building.


Does a multi-region EKS deployment work?

What did you do?
I want to deploy a mulit-datacenter cluster across multiple regions within EKS, what issues should we be aware of (particularly any cross-region networking issues) and can we document that?
┆Issue is synchronized with this Jira Task by Unito
┆Issue Number: K8SSAND-929
┆Priority: Medium

Documentation here in this issue is sufficient to start, and then we can later translate that into the full docs package.


patch embeddings always 0?

I was reading the paper and checking the code and I can't see when you add value to the patch embbedings, I was debugging the code and in this part I only see you create a zero tensor and after on forward you only add this tensor.
In which moment you give a value to the patch embeddings?
line 157 https://github.com/TACJu/TransFG/blob/master/models/modeling.py#L157
self.position_embeddings = nn.Parameter(torch.zeros(1, n_patches+1, config.hidden_size))
Line    173     embeddings = x + self.position_embeddings

Sorry , this question go into https://github.com/jeonsworld/ViT-pytorch
thanks for your effort and sorry


Nuget Version

Hey Matt,
Any change of a NuGet version of this?
:-D
Thanks
Nik

Yes!
https://www.nuget.org/packages/Mw.UmbracoForms.Rte/


Runtime: Unable to use a serviceId for a service client

This configuration should be valid for a service client in a Runtime app:
  "clients": [
    {
      "path": "./clients/persons-service",
      "serviceId": "persons-service"
    }
  ]

Related feature PR: support passing explicit client IDs in service clients

But it causes the following error:
[20:53:04.673] ERROR (books-service/94632): error reloading the configuration
    err: {
      "type": "Error",
      "message": "must have required property 'url' {\"missingProperty\":\"url\"}",
      "stack":
          Error: must have required property 'url' {"missingProperty":"url"}
              at ConfigManager.parseAndValidate (/Users/simonplend/dev/github/platformatic/platformatic/packages/config/index.js:230:13)
              at async FileWatcher.<anonymous> (/Users/simonplend/dev/github/platformatic/platformatic/packages/config/index.js:73:9)
    }

This is because the clients subschema in @platformatic/service is incorrect (source):
const clients = {
  type: 'array',
  items: {
    type: 'object',
    properties: {
      serviceId: {
        type: 'string'
      },
      path: {
        type: 'string',
        resolvePath: true
      },
      url: {
        type: 'string'
      }
    },
    additionalProperties: false,
    required: ['path', 'url']
  }
}

path should be the only required property
Either url or serviceId should be set, but not both

@cjihrig I ran in to this bug when testing the new clients serviceId setting in main.

path should be the only required property
Either url or serviceId should be set, but not both

FWIW, this doesn't seem correct to me. path and url are required for previous use cases of clients. The serviceId is currently only used by the runtime, and if it is not present, it falls back to using path to load the client's package.json.


refactor(frontend): rename prop of IcTransaction

Motivation
We rename the prop transactionType to type, for consistency.
Furthermore, elsewhere in the code, in the util mapIcrcTransaction, the type is defined as
const type: IcTransactionType = nonNullish(fromNullable(approve))
  ? 'approve'
  : nonNullish(fromNullable(burn))
    ? 'burn'
    : isMint
      ? 'mint'
      : source.incoming === false
        ? 'send'
        : 'receive';

Meaning that we can simply use type === 'send' in the same way that we use incoming === false

[OISY-130]


145/show sshkeys stored

closes #145
changes proposed in the pull request:

Create sshKeyItem Component
Show added sshkeys

@thetonymaster

Coverage increased (+0.1%) to 94.681% when pulling e2c48f70d86ae61908b8cc32e95b60c0ed0f271e on 145/show-sshkeys-stored into 8a428937e82f339adfce6431bceeac2d5f4d0387 on master.

@thetonymaster looks better?

Coverage increased (+0.1%) to 94.681% when pulling 24609497c6ca2aed07270898263266d7d407e799 on 145/show-sshkeys-stored into 8a428937e82f339adfce6431bceeac2d5f4d0387 on master.


Discover hidden files and directories

Would it be possible to make onefetch look through hidden directories inside a repository?
I have a directory in one of my repositories that is hidden (starts with a dot .system) and onefetch doesn't find any code in the repository, however, if I unhide that directory mv .system system it finds all the code inside.
Which is why I'm assuming the issue is with hidden items.

Looks like there's a tokei config option for that. If you would like to make a PR, here's where hidden is set to false (via default) 🙂

I'll gladly make a PR when I've got a bit of time, thank you!